Nonin Medical Port Devices Driver

Posted on  by



Virtual COM port (VCP) drivers cause the USB device to appear as an additional COM port available to the PC. Application software can access the USB device in the This page contains the VCP drivers currently available for FTDI devices. For D2XX Direct drivers, please click here. If you have to manually install a driver for the device — perhaps the driver is already installed on your system — you can use the Update Driver button in the device’s Properties window. Serial com device driver download for windows. If the device driver is already installed on your system, click the “Browse my computer for driver software” link and choose an installed driver. HID Class Driver IOCTLs. The HID class driver handles IOCTLs to support for top-level collections. Although user applications can communicate with the HID class driver by using HidDXxx HIDClass support routines, kernel-mode drivers must send the corresponding device control requests described in this section. PROFOX software works with a variety of pulse oximeters and respiratory oximeters including, Nonin 3100 Wristox, 3150 WristOx2, Masimo Radical, Nonin 9600 Avant, BCI, Respironics 920M, Minolta Pulsox, Nellcor.

Nonin Technical Service is here to help you with warranty and non-warranty repairs, product troubleshooting, replacement parts, software downloads, manuals/instructions, drivers, cleaning recommendations, and discontinued product information.
For technical support, repair requests and questions, please use the Support button in the lower right corner of the page.

Contact Technical Support

Technical Support for North America, Latin America, and Asia Pacific:

Toll-Free: (800) 356-8874 (U.S. and Canada only)

Phone: +1 763-553-9968

Technical Support for Europe, Middle East, Africa, India, and Indian Subcontinent:

Phone: +31 (0)13 – 45 87 130

Online Support Articles

Warranty & Non-Warranty Repairs

Nonin Medical Port Devices Drivers

Nonin Medical offers unmatched technical service and support beyond the initial point of sale. Nonin Technical Services is here to help you with warranty and non-warranty repairs, product troubleshooting, replacement parts, software downloads, manuals/Instructions, drivers, cleaning recommendations, and discontinued product information.

Nonin Medical maintains the highest quality standards. All repairs are performed by qualified technicians. Devices are restored to their fully functioning, original specifications.

  • Warranty repairs are performed at no charge unless damaged, misused and/or abused
  • Non-warranty repairs are performed at a flat rate that includes parts and labor
  • Nonin also will perform any applicable device updates

To Obtain a Return Authorization Number (RAN) for Product Repair

Contact Technical Support:
Toll-Free: (800) 356-8874 (U.S. and Canada only)

Phone: +1 763-553-9968

Phone: +31 (0)12 – 79 99 040 (Europe, Middle East, Africa, India, and Indian Subcontinent)

If you need a Nonin product repaired, please follow these steps:

  • Step 1: Please complete the troubleshooting procedures for your device. Troubleshooting guides are found in the product support articles. If you have already completed the troubleshooting procedure and your problem still exists, continue to Step 2.
  • Step 2: Please complete this Request for Repair Quote form below. Nonin will then provide you, within two business days, an emailed estimate for repair.
  • Step 3: If you choose to go ahead with the repair based on the Nonin estimate provided, Technical Service will provide a link to our Repair Payment Authorization e-form. Please complete and submit this form to request a Return Authorization Number. Within two business days, Nonin will contact you with a Return Authorization Number.
-->

Versions supported

  • Windows 10
  • Windows 8.1

Applies to

  • Device manufacturers of CDC Control devices
Port

Microsoft-provided in-box driver (Usbser.sys) for your Communications and CDC Control device.

In Windows 10, the driver has been rewritten by using the Kernel-Mode Driver Framework that improves the overall stability of the driver.

  • Improved PnP and power management by the driver (such as, handling surprise removal).
  • Added power management features such as USB Selective Suspend.

In addition, UWP applications can now use the APIs provided by the new Windows.Devices.SerialCommunication namespace that allow apps to talk to these devices.

Usbser.sys installation

Nonin Medical Port Devices Driver Updater

Load the Microsoft-provided in-box driver (Usbser.sys) for your Communications and CDC Control device.

Note

If you trying to install a USB device class driver included in Windows, you do not need to download the driver. They are installed automatically. If they are not installed automatically, contact the device manufacturer. For the list of USB device class driver included in Windows, see USB device class drivers included in Windows.

Nonin Medical Port Devices Driver

Windows 10

In Windows 10, a new INF, Usbser.inf, has been added to %Systemroot%Inf that loads Usbser.sys as the function device object (FDO) in the device stack. If your device belongs to the Communications and CDC Control device class, Usbser.sys is loaded automatically.You do not need to write your own INF to reference the driver. The driver is loaded based on a compatible ID match similar to other USB device class drivers included in Windows.

USBClass_02

USBClass_02&SubClass_02

  • If you want to load Usbser.sys automatically, set the class code to 02 and subclass code to 02 in the Device Descriptor. For more information, see USB communications device class. With this approach, you are not required to distribute INF files for your device because the system uses Usbser.inf.
  • If your device specifies class code 02 but a subclass code value other than 02, Usbser.sys does not load automatically. Pnp Manager tries to find a driver. If a suitable driver is not found, the device might not have a driver loaded. In this case, you might have to load your own driver or write an INF that references another in-box driver.
  • If your device specifies class and subclass codes to 02, and you want to load another driver instead of Usbser.sys, you have to write an INF that specifies the hardware ID of the device and the driver to install. For examples, look through the INF files included with sample drivers and find devices similar to your device. For information about INF sections, see Overview of INF Files.

Note

Microsoft encourages you to use in-box drivers whenever possible. On mobile editions of Windows, such as Windows 10 Mobile, only drivers that are part of the operating system are loaded. Unlike desktop editions, it is not possible to load a driver through an external driver package. With the new in-box INF, Usbser.sys is automatically loaded if a USB-to-serial device is detected on the mobile device.

Windows 8.1 and earlier versions

In Windows 8.1 and earlier versions of the operating system, Usbser.sys is not automatically loaded when a USB-to-serial device is attached to a computer. To load the driver, you need to write an INF that references the modem INF (mdmcpq.inf) by using the Include directive. The directive is required for instantiating the service, copying inbox binaries, and registering a device interface GUID that applications require to find the device and talk to it. That INF specifies 'Usbser' as a lower filter driver in a device stack.

The INF also needs to specify the device setup class as Modem to use mdmcpq.inf. Under the [Version] section of the INF, specify the Modem and the device class GUID. for details, see System-Supplied Device Setup Classes.

For more information, see this KB article.

Configure selective suspend for Usbser.sys

Starting in Windows 10, Usbser.sys supports USB Selective Suspend. It allows the attached USB-to-serial device to enter a low power state when not in use, while the system remains in the S0 state. When communication with the device resumes, the device can leave the Suspend state and resume Working state. The feature is disabled by default and can be enabled and configured by setting the IdleUsbSelectiveSuspendPolicy entry under this registry key:

To configure power management features of Usbser.sys, you can set IdleUsbSelectiveSuspendPolicy to:

  • '0x00000001': Enters selective suspend when idle, that is, when there are no active data transfers to or from the device.

  • '0x00000000': Enters selective suspend only when there are no open handles to the device.

That entry can be added in one of two ways:

  • Write an INF that references the install INF and add the registry entry in the HW.AddReg section.

  • Describe the registry entry in an extended properties OS feature descriptor. Add a custom property section that sets the bPropertyName field to a Unicode string, 'IdleUsbSelectiveSuspendPolicy' and wPropertyNameLength to 62 bytes. Set the bPropertyData field to '0x00000001' or '0x00000000'. The property values are stored as little-endian 32-bit integers.

    For more information, see Microsoft OS Descriptors.

Develop Windows applications for a USB CDC device

If you install Usbser.sys for the USB CDC device, here are the application programming model options:

  • Starting in Windows 10, a Windows app can send requests to Usbser.sys by using the Windows.Devices.SerialCommunication namespace. It defines Windows Runtime classes that can use to communicate with a USB CDC device through a serial port or some abstraction of a serial port. The classes provide functionality to discover such serial device, read and write data, and control serial-specific properties for flow control, such as setting baud rate, signal states.

  • In Windows 8.1 and earlier versions, you can write a Windows desktop application that opens a virtual COM port and communicates with the device. For more information, see:

    Win32 programming model:

    • .NET framework programming model:

Nonin

Related topics