What driver should I use for a a virtual COM port (to access the device the same as an RS-232 serial device)?
One option is to use Windows’ Communications driver. The firmware should define the device as CDC/ACM (Communications Device Class/Abstract Control Model). The device uses endpoint zero and bulk IN and bulk OUT endpoints. In the INF file, set Class=Ports. For Windows 2000 and Windows XP, describe the hardware driver (usbser.sys) as a functional driver, not as a lower filter driver. For Windows 98 and Windows Me, declare “usbser.sys,ccport.sys” as the device drivers. Reports are that the Windows driver is slow (640Kbit/sec) and the WM_DEVICECHANGE notifications don’t work properly on Windows 2000. More information. For better performance, use a dedicated-function controller whose vendor provides a virtual COM port driver.
Related Questions
- I want to run my Win32 protected application and I get error "RNBOVDD.DLL: Virtual device driver failed to initialize" under WinNT. What should I do ?
- The CH-1 only provides one RS-232 serial port. What do I do if I need more than one RS-232 serial port for multiple changers or external control?
- What driver should I use for a a virtual COM port (to access the device the same as an RS-232 serial device)?
