rob, you might want to browse these pages to get some ideas about architecture:
https://github.com/weewx/weewx/wiki/intake-strategies https://github.com/weewx/weewx/wiki/dashboards and of course the customization guide has the details about how to it. if you already have the sensors working and spitting out data to a serial port, then you *could* just write a weewx driver that reads data from that serial port. then let weewx and all of the weewx extensions take care of everything else. use one of the serial drivers as an example, such as ws1 or twi. this would probably be shortest path to a solution. if you're keen to do a little bit of network coding, then i would second vince's suggestion about the weatherflow approach - broadcast the sensor data to the local network, then write a weewx driver that captures the broadcast data. use the weatherflow driver for guidance on that approach. imho, none of the commercial weather stations have the 'perfect' protocol. so learn from them, but don't try to match them exactly unless you are trying to leverage tools specific to that station. definitely do not imitate oregon scientific or fine offset. definitely study the way davis did it and the way weatherflow does it. you might look at some of the industrial protocols like sdi12 or modbus or nmea2000 or even seatalk, even if you intend to do a serial or tcp/ip implementation. in the end, you're probably better off to write your own driver - that way you control all of the bugs :) 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.
