(→USB Serial Drivers for USB-COM Mode)
|
(→USB Serial Drivers for USB-COM Mode)
|
Line 6: | |||
If two way communication is necessary (i.e. send scanned data or receive commands from the host), then the scanner needs to be placed in USB-VCP mode and then two way communication is performed through the creation of a virtual COM port. | If two way communication is necessary (i.e. send scanned data or receive commands from the host), then the scanner needs to be placed in USB-VCP mode and then two way communication is performed through the creation of a virtual COM port. | ||
==USB Serial Drivers for USB-COM Mode== | ==USB Serial Drivers for USB-COM Mode== | ||
- | There are two ways that Opticon's devices can be accessed in Linux while in USB-COM (Virtual COM Port mode). Our 1D devices (in USB-COM mode) do not need a separate driver for serial communication (Linux has the proper device driver). As well, our 2D products and some 1D use a generic CDC/ACM driver for serial communication. Since this is also well-supported in Linux, all of our products are supported. | + | There are two ways that Opticon's devices can be accessed in Linux while in USB-COM (Virtual COM Port mode). Our 1D devices (in USB-COM mode) do not need a separate driver for serial communication (Linux has the proper device driver). As well, our 2D products and some 1D use a generic CDC/ACM driver for serial communication. Since this is also well-supported in Linux, most of our products are supported. |
* The typical method for accessing our 1D laser products is to open the <b>/dev/ttyUSB#</b> file, where the # is a number, starting from 0 and counting up. | * The typical method for accessing our 1D laser products is to open the <b>/dev/ttyUSB#</b> file, where the # is a number, starting from 0 and counting up. |