On Friday, November 11, 2016 at 11:47:26 PM UTC-5, Cameron D wrote:
>
> I copied in wrm300.py v0.15rc2, as described above, and, running
> PYTHONPATH=. python weewx/drivers/wmr300.py
>
> I now get:
>
>> Nov 12 13:55:19 x wmr300[13744]: wmr300: driver version is 0.15rc2
>> Nov 12 13:55:19 x wmr300[13744]: wmr300: Found station at bus= device=
>> Nov 12 13:55:19 x wmr300[13744]: wmr300: usb failure: [Errno 110] 
>> Operation timed out
>>
>
> The null entries for bus and filename look to be from usb.legacy, where 
> they are simply populated with empty strings.
> Note, the timeout (and exit) is almost immediate - always the same second.
>

cameron,

if you try starting a second time, does everything work?

on a test system i sometimes see the timeout when starting weewx for the 
very first time, i.e., when there has been no communication with the 
station for some time (an hour? a day? a week?).  but a subsequent start 
works.  i suspect it is a case of getting the station to start spitting out 
data on the usb - the driver must not be using the right protocol to get 
communication started.  but once the station is spitting out data, the 
driver works fine - there is a heartbeat command that keeps communication 
going.

could you sniff the usb when running the windows software to communicate 
with the hardware?  we need a capture that covers this:

1) station is already plugged in to usb
2) start the windows software
3) record one or two intervals of current data

i also suspect that we are dealing with two issues here - one is the 
driver's check for 'No error' and 'No data available' (that would be 
affected by localization) and the other is the timeout failures (due to 
startup/initialization protocol).

of course, this is all reverse engineering a system for which we get zero 
help from the manufacturer or vendor, so i could be completely wrong.

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.

Reply via email to