USB scanner stops working with DIO connected

[rbMado]

We have several RevPi Connect SE 32 GB (PR100370) devices with RevPI DIO 14IO (PR100197) modules.
For our application we need a handheld scanner reading barcodes connected to RevPi.

As long as we use the scanner with RevPi and without DIO, the scanner is working fine.
We have tested that with a Zebra DS2208 handheld using text editor to read a barcode.
We also checked the same scanner and same barcode on other devices such as other PC with different hardware and OS and text editors – always ok.

As soon as we attach the DIO module to RevPi and activate it in pictory, the readout from the scanner is randomly missing 1 or 2 different characters most of the time.
Example below:
157900024922555075
5790002492555075
15700024922555075
157900024922555075
15790024922555075
157900024922555075
157900024922555075
157900024922555075
1579002922555075
15790002492255507
It seems the attached DIO module is somehow interrupting the readout and is responsible for missing characters.

Can you help us find the solution?

[dirk]

Hello rbMado, thank you for the detailed description of the error pattern. Problems in connection with USB devices and the drivers used are manifold. Significantly, however, this is probably together with the connected DIO module to an error.
Can you create an SOS report for us?
https://kunbus-gmbh.atlassian.net/servi ... 2036400208

[rbMado]

I provide the sos report in the link below:
https://drive.google.com/drive/folders/ ... drive_link

[rbMado]

Hi dirk, did you manage to look into the file?
Were you able to reproduce this case?
As an additional info I might add, that I suspect the same happens with a regular USB keyboard not only handheld scanners.

[dirk]

Hello rbMado, thank you very much for your patience and the information you provided. I have analysed your SOS report with the SOS parser and was able to determine that your kernel (Linux version 6.1.46-rt13-v7l, February 2024) is upgradeable. Please update your system to kernel "6.1.46-rt13-v8" April 2024.
By the way - the firmware of your RevPi DIO module is the current version 1.5, so no update is necessary. Good luck, I hope that this solves the problem.

[rbMado]

Hi Dirk,

I did load the following image: https://packages.revolutionpi.de/bullse ... -armhf.zip
It seems to be the latest, 2024-04-25.
After apt update and upgrade the version still shows Linux 6.1.46-rt13-v7l armv7l
Can you point me to version v8?

Also just to make sure, did you manage to replicate the problem on v7l and did it stop on v8?

[rbMado]

Good luck, I hope that this solves the problem.

Hi Dirk, as I described, the problem is not solved and still persist.
Please let me know if you were able to replicate and any possible solution.

[tboehler]

Hi rbMado.

Sorry for the confusion - the v7l and v8 suffixes of the linux kernel package shipped on bullseye show the architecture the kernel was built for; you seem to have been on the latest version when you posted about your issue here last year.

As it has been some time since the last post, I have to ask again what state your system is in. If it's still on bullseye I'll ask if you could update this to bookworm by flashing the newest image found in the download section on the Revolution Pi website (currently 250528-revpi-bookworm-arm64). We've made quite some improvements to the software, it could be that this already fixes your issue.
If you're unable to switch to bookworm please do tell us why as we're interested in making it possible for everyone to switch over to bookworm, and make sure you upgrade your system running bullseye with "sudo apt update && sudo apt upgrade".

If this also doesn't solve your problem, try using the xhci USB controller by setting "otg_mode=1" in the "[all]" section in your "/boot/config.txt" file. Don't replace the file's contentss, just add the line to the section "[all]".

Code: Select all

[all]
otg_mode=1

I hope this helps!

Cheers
Thomas