On Wednesday, January 18, 2017 at 7:24:16 PM UTC-5, David Morgan wrote: After getting it running, I found I can use Wireshark to look at the > serial interface (after enabling a kernel module), would have been nice to > know that earlier. >
there are a few threads in this forum, as well as the weewx-development forum, about sniffing usb, serial, or network traffic in order to figure out what the hardware is doing. the protocol for the acurite hardware is pretty straightforward - the trickiest part was figuring out the temperature/pressure encoding, but george cracked that one when he found the spec sheet for the HP03S sensor they were using. then it took awhile to figure out the firmware bugs and hardware variants after the initial 01035/01036 models. if you want to hack on your station, you might try to make reading of history records reliable (the R3 messages). acurite consoles do not have much memory, and it is rather pointless for older hardware, but could be useful for newer hardware that defaults to having usb comms enabled after power cycling. > > The barometric pressure is way wrong on the console, and there is some > disagreement between the console and the WeeWx display. I am curious if > anyone knows yet what sensors are used. I have resisted peeking so far, > but that may change. > take a look at the comments in the driver file, acurite.py it explains pretty much everything we know about acurite hardware, including the reason for the console barometer readings. other driver files contain similar information about their respective hardware. there have been many contributions from many different people! 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.
