On Sunday, September 11, 2016 at 11:44:15 AM UTC-4, Allan H wrote: > > Den 11-09-2016 kl. 16:33 skrev Allan: > > > Well, without the resets, it doesn't seem to load here. > > Follow-up: > > I just tried to uncomment line 1562 to get the reset back, and the > driver immediately started to work again >
well that is annoying. apparently the reset is required on some systems, but on other systems it causes the driver to fail. allan, the logs you posted show bus= driver=, i.e., no value for bus or driver, but that was with an error of undefined symbol. when the driver is working, do you see values for bus and driver? it looks like we are in a version quagmire - some combinations of udev, libusb, and pyusb work, but others do not. and the usb reset seems to trigger it. i think we now have a unit test: - which operating system and version? - which version of libusb? - which version of pyusb? - which version of udev? - which version of te923 driver (use 0.19 if possible) with reset un-commented: - what happens when you run the driver directly for --readings? - what happens when you run the driver directly for --records=5? - what happens when you run weewxd directly? - what happens when you run weewx as daemon? - what happens whey you run weewx as daemon at system startup? then the same again with reset commented. for each os/libusb/udev configuration it would also be nice to know whether te923tool runs properly. m -- 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.
