i am using a USB-3104 on a raspberrypi 4 (Debian 12, 64 bit).
Unfortunately, if (and only if) I am connected to other I/O devices via USB i stochastically get Error 8 (bad device).
I managed to reproduce the error using "AOut" from /libuldaq-1.2.1. Unfortunately, reproducing the setup (my other devices) will be very hard.
I can confirm that the problem also occurs with other usb cables and and other usb ports, with and without usb hub. It should also not be a power problem, i am using active hubs.
Hence, first some general questions:
* Can we exclude that the device if faulty?
* Are there timeouts set in libuldaq, if yes where in the code?
* Do you have any other ideas how to debug the USB stack? Obviously the problem could be at any level from the linux kernel upwards (no output in dmesg however). It is very worrying that there is "crosstalk" with other devices.
All the best,
PS: I now attach usb debugging output, the error occurs around line 686
Christian
------------
~/libs/libuldaq-1.2.1/examples $ ./AOut
------------
Active DAQ device: USB-3104 (0209CCA9)
Enter a value between -10.000000 and 10.000000 volts (or non-numeric character to exit): 2
2
Error Code: 8
Error Message: Device no longer responding
Question
ChristianW
Dear MCC team,
i am using a USB-3104 on a raspberrypi 4 (Debian 12, 64 bit).
Unfortunately, if (and only if) I am connected to other I/O devices via USB i stochastically get Error 8 (bad device).
I managed to reproduce the error using "AOut" from /libuldaq-1.2.1. Unfortunately, reproducing the setup (my other devices) will be very hard.
I can confirm that the problem also occurs with other usb cables and and other usb ports, with and without usb hub. It should also not be a power problem, i am using active hubs.
Hence, first some general questions:
* Can we exclude that the device if faulty?
* Are there timeouts set in libuldaq, if yes where in the code?
* Do you have any other ideas how to debug the USB stack? Obviously the problem could be at any level from the linux kernel upwards (no output in dmesg however). It is very worrying that there is "crosstalk" with other devices.
All the best,
PS: I now attach usb debugging output, the error occurs around line 686
Christian
------------
~/libs/libuldaq-1.2.1/examples $ ./AOut
------------
Active DAQ device: USB-3104 (0209CCA9)
Enter a value between -10.000000 and 10.000000 volts (or non-numeric character to exit): 2
2
Error Code: 8
Error Message: Device no longer responding
----------
usb-debug.txt
Edited by ChristianWattached usb debug output
Link to comment
Share on other sites
1 answer to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now