On Friday, September 9, 2016 at 8:00:11 AM UTC-4, Marco Tibaldi wrote: > > Matt, just to understand: > with your driver is sufficient to map the output of the sensors and make them > coincide with the database tables? > and, > with this method it is possible to map unknown sensors ? > >
the [[sensor_map]] associates the observations with database fields. so i think that is a 'yes' to your first question. the answer to the second is more complicated. any driver has the following steps: 1) obtain data from the hardware 2) parse/decode the data 3) do unit conversions 4) do transformations, e.g., rain_total to rain_incremental; aggregations 5) map data from hardware naming to database fields the uploaders in weewx provide additional steps 6) do transformations, e.g., cumulative power to incremental power; aggregations 7) map data from database fields to destination fields in some cases, steps 1-5 degenerate to one or two steps, depending on the hardware. in the case of the SDR driver, every step is involved, and it is complicated by the fact that the SDR receiver gets data from not just a single device. as a result, it must also filter. this is done implicitly in step 5. in normal operation, the SDR driver will silently ignore data from sensors that you do not care about. use the log_unknown_sensors option to make it log the output from sensors for which the SDR driver has no parser. use the log_unmapped_sensors to make it log the output from sensors that you have not requested in the sensor_map. 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.
