On Sunday, 13 November 2016 00:52:40 UTC+10, mwall wrote: > > > i suspect that different versions of libusb assemble the errors > differently. afaict, some of the strerror messages are coming from the > operating system, not libusb. i do not yet know a reliable way to extract > the error intent using pyusb. > > Yes, from what I could understand of the pyusb source, the exceptions are purely those provided by the underlying backend, and, of those, some seem to be mapped to specific English strings and some to system error messages - I guess out of the underlying libc.
> > > when you test, please set debug in weewx.conf: > > debug=1 > ... > > [WMR300] > ... > debug_rain = 1 > debug_decode = 1 > > Ah, that is useful - I was wondering where those values came from, other than hard-coding them into the driver. On that topic, which parameter take priority? the debug flag in the weewx.conf, or DEBUG_RAIN in the driver? -- 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.
