August-24th-2018, 10:03 AM
(This post was last modified: August-24th-2018, 10:03 AM by Armin@netPI.)
Thank you for your fast reaply.
I followed to what you configured and everything is fine.
I googled a little bit about Zebra Scanner for example. What I found out was that USB it not always USB under Linux ... and how devices are supported by a kernel driver when the are connected to a USB even if they are based on a simple serial communication is not always the same under Linux.
Especially with a focus on Zebra I found out that this device is not mapped as ttyUSB device but as hidraw device (Human Interface Device) as stated here https://www.kernel.org/doc/Documentation/hid/hidraw.txt
Here comes now the point where I have doubts. You should start with the Zebra device only for a test because I don't know if netPI Linux kernel has included the hidraw kernel module driver included or not. But it is worth it to test. So start netPI with Zebra only, map /dev/bus and /dev/hidraw0 and see what happens then.
Thx
Armin
I followed to what you configured and everything is fine.
I googled a little bit about Zebra Scanner for example. What I found out was that USB it not always USB under Linux ... and how devices are supported by a kernel driver when the are connected to a USB even if they are based on a simple serial communication is not always the same under Linux.
Especially with a focus on Zebra I found out that this device is not mapped as ttyUSB device but as hidraw device (Human Interface Device) as stated here https://www.kernel.org/doc/Documentation/hid/hidraw.txt
Here comes now the point where I have doubts. You should start with the Zebra device only for a test because I don't know if netPI Linux kernel has included the hidraw kernel module driver included or not. But it is worth it to test. So start netPI with Zebra only, map /dev/bus and /dev/hidraw0 and see what happens then.
Thx
Armin
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)