(→USB Serial Drivers)
|
(→USB Serial Drivers)
|
Line 8: | |||
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. 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#. | 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. 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#. | ||
- | A quick method for testing data transmission is to open the file corresponding to your device with the "cat" utility, then scanning some barcodes. 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 will 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 barcodes. 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. |
It's also possible to use tools like ttylog to wedge keyboard data into a terminal from a serial port. | It's also possible to use tools like ttylog to wedge keyboard data into a terminal from a serial port. |