-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fata error> USB read failed #1
Comments
My gut feeling(!) is that this is due to the USB device somehow misbehaving and being reset and reenumerated. I have seen ordinary devices like keyboards and webcams run without any problem for weeks with no problem at all. With the temper, I could not get even one straight week of service without such a glitch. Even worse: sometimes it returns but always return 0-values. That detail may well be due to this driver (I did not and do not fully understand the interaction pattern that it implements). My conclusion: restart daily using a corn job to cleanup stuck devices and do not use more than one per raspi. |
To shed some more light, I've used temper.py and now pcsensor.c and both have shown this type of behavior in my custom python script. When running pcsensor in terminal with the loop (-L) option, at no point does it hang up. I've run two simultaneous terminals hitting both Temper sensors and it still runs great. When I run my custom python script and use pcsensor, that's when the collision seems to happen. I'm less inclined to think there is an issue with your driver.
|
Hi, Same problem here, but I can add some details. I hope it can help to locate the problem, even if I think the problem is inside the sensor.
Let me know if you need some other details. One last question : you said "restart daily using a corn job to cleanup stuck devices". Can you explain that? What do you restart? The raspi? Thank you for reading and sorry for my poor English ^^ |
Same here
With the following device:
|
confirming this as well, I see the same after exactly 16 reads when using the python script, see padelt/temper-python#6 |
I can read from the sensor (usb device) once and then not again until I take it out and insert it again. wojci@build: |
@wojciiii , I have no real idea why that is happening. That said, I do not think much about this C-version of pcsensor-temper as I exclusively use the python-version here: https://github.com/padelt/temper-python I do have one idea though: A year ago, @amorphic added a reset of the USB device after each read cycle. You can see the relevant code change in temper-python here: padelt/temper-python@a9c8b68#diff-19c78b0104bf03153b342369297c254dR157 That may still be missing in pcsensor-temper and may help with this situation. |
Fixes a bug on some/newer systems/kernels where after one invocation always the following error occurs: USB interrupt read: Resource temporarily unavailable Fatal error> USB read failed Idea from padelt/pcsensor-temper#1 (comment) resp. padelt/temper-python@a9c8b68#diff-19c78b0104bf03153b342369297c254dR157
I added a call to See my fork here: https://github.com/stefansundin/pcsensor-temper |
When I use this driver, it successfully reads two devices but with the occasional error.
USB interupt read: Resource temporarily unavailable
Fatal error> USB read failed
This results in the n0 and n1 device switching. I'm unsure if the issue lies with this driver or Linux. OS is Raspbian Wheezy. I've used other drivers which also result in this interrupt error.
The text was updated successfully, but these errors were encountered: