For a), we'll hopefully find out more with debug=1. Haven't seen this with my own station so far.
For b) ... I am not sure yet. I am a noob at Python, there are still many things I don't fully understand properly, including error handling :( All I can say for now is that: - in _get_raw_data, the driver first tries to send a command to the station (_write_usb), then it tries to read the results (_read_usb). - one of those operation fails for some reason. Here again, we will hopefully know more with debug=1 - in the worst case scenario, (ie. we cannot figure out what's wrong and how to fix this), we could simply modify the driver to ignore the failure and hopefully prevent a complete crash. But first question: did you increase the timeout *both* for read and write? What value are you using? I honestly don't know what would be reasonable value, 1000 might still not be enough on Raspberry. Back when I first investigated the issue for Raspberry, I came across a lot of links mentioning issues with USB devices on Raspberry. In one of those, you can see that somebody solved the issue by increasing the timeout to 10000... https://github.com/jim-easterbrook/pywws/issues/38 https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=53832 -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
