-
Notifications
You must be signed in to change notification settings - Fork 74
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
Retry firmware query if payload seems implausibly small #16
Conversation
3f2f4db
to
7d9ebd3
Compare
7d9ebd3
to
43a727c
Compare
Showing the retry in action...
|
In relation to discussion over on Issue #9 Linux PC
|
Made both of these changes and updated the timeout from 0.2 to 0.5 and still get failures every other read when running Just investigating, the regularity of it made me call hardware into question, checking dmesg it shows brownout on each successful read, subsequently returning rubbish. Will confirm with new PSU. __ Update: Output modified as I don't need all the bumf, but.... |
@bucklevision Could you mention the specific Temper USB model and the output of |
Sure, sorry, not very helpful! It seems to happen with successive calls within 2ish seconds. Give it 5 and most of the time it's OK. lsusb: output of /sys/kernel/debug/usb/devices It's one of these: However it was purchased from Amazon. |
@bucklevision I filed Issue #20 to follow up for TEMPerV1.4 and RPi3 B+. There is a workaround, so far. |
Update info on DOCKER and fix docker-compose config
In relation to Issue #9
Bus 003 Dev 006 413d:2107 V3.3 Error: Unknown firmware V3.3: b'800108984e200000'
I had some success with TEMPer1F 413d:2107 that was alternating between TEMPerX_V3.3 and V3.3 as the firmware version.
This change tries ten times to read the firmware while 0 < length < 9
See the issue for further diagnostics.