Version Differences for Linux - Opticon Technical Support Portal

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-VCP Mode==

+

==USB Serial Drivers for USB-COM Mode==

-

There are two ways that Opticon's devices can be accessed in Linux while in USB-VCP (Virtual COM Port) mode. Our 1D devices (in USB-VCP mode) do not need a separate driver for serial communication (Linux has the proper device driver). As well, our 2D products 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, all of our products are supported.

-

* The typical method for accessing our 1D products is to open the /dev/ttyUSB# 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 /dev/ttyUSB# file, where the # is a number, starting from 0 and counting up.

-

* Our 2D products are accessed through a similar device file, with the exception that since they use the CDC drivers they are accessed through /dev/ttyACM#.

+

* Our 2D products (and 1D CCD products) are accessed through a similar device file, with the exception that since they use the CDC drivers they are accessed through /dev/ttyACM#.

-

A quick method for testing data transmission is to open the file corresponding to your device with the "cat" utility, then scanning some bar codes. For example, if your 1D scanner is the only USB-VCP device on the system, it can be accessed by typing "cat /dev/ttyUSB0" into the terminal. You may need adequate permissions on the device file in order to open it, but it should work once you have them.

+

A quick method for testing data transmission is to open the file corresponding to your device with the "cat" utility, then scanning some bar codes. For example, if your 1D scanner is the only USB-COM device on the system, it can be accessed by typing "cat /dev/ttyUSB0" into the terminal. You may need adequate permissions on the device file in order to open it, but it should work once you have them.

It's also possible to use tools like ttylog to wedge keyboard data into a terminal from a serial 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-VCP Mode==
+								==USB Serial Drivers for USB-COM Mode==
-								There are two ways that Opticon's devices can be accessed in Linux while in USB-VCP (Virtual COM Port) mode. Our 1D devices (in USB-VCP mode) do not need a separate driver for serial communication (Linux has the proper device driver). As well, our 2D products 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, all of our products are supported.
-								* The typical method for accessing our 1D 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.
-								* Our 2D products are accessed through a similar device file, with the exception that since they use the CDC drivers they are accessed through <b>/dev/ttyACM#</b>.
+								* Our 2D products (and 1D CCD products) are accessed through a similar device file, with the exception that since they use the CDC drivers they are accessed through <b>/dev/ttyACM#</b>.
-								A quick method for testing data transmission is to open the file corresponding to your device with the <b>"cat"</b> utility, then scanning some bar codes. For example, if your 1D scanner is the only USB-VCP device on the system, it can be accessed by typing <b>"cat /dev/ttyUSB0"</b> into the terminal. You may need adequate permissions on the device file in order to open it, but it should work once you have them.
+								A quick method for testing data transmission is to open the file corresponding to your device with the <b>"cat"</b> utility, then scanning some bar codes. For example, if your 1D scanner is the only USB-COM device on the system, it can be accessed by typing <b>"cat /dev/ttyUSB0"</b> into the terminal. You may need adequate permissions on the device file in order to open it, but it should work once you have them.
 It's also possible to use tools like <b>ttylog</b> to wedge keyboard data into a terminal from a serial port.