PortLynq™ Advanced Serial Drivers for USB
Hot-plug without headaches
On Windows, the situation is particularly complex; applications must respond to Windows plug-and-play messages immediately. If a device is removed, the application must close any handle they have open to the device, whether it’s convenient or not. Because the removal may happen completely asynchronously to other application activities, this can greatly complicate both design and test.
On Linux and macOS, the situation is not quite as complicated; because there are no plug-and-play messages to be processed. However, any existing connection to the device becomes useless; if the device is plugged back in, the application must detect the return of the device, and re-open the file handle. Again, the independent activity on the USB port complicates application design and test.
Since 2005, MCCI’s PortLynq drivers (US patent 8,346,981) have supplied a simple alternative. PortLynq drivers create a virtual device entry that remains present on the system even when the underlying device is not present. When the device is removed, the application doesn’t see any difference, because the virtual device takes on the responsibility of managing hot plug on behalf of the application.
PortLynq serial drivers are most used with serial port emulation drivers, but PortLynq technology can be used with any driver class where the application communicates directly with a USB or other external device where the device can be disconnected from and connected to the system by the user.
Interested in using PortLynq drivers to simplify your application? Contact MCCI for more info!