Hi Gary,

OK.... I thought the uvradiation field from the sensor corresponded to the radiation field in the DB given luminosity was a separate field in its own right.

I'll go make those changes to see what I get. I'll  move the PM2.5 sensor back to ch1 and see if the data appears in the DB.

I'll also do the debug thing and report.

thanks

Tim


On 22/9/20 12:24 am, gjr80 wrote:
Tim,

The GW1000 driver does not provide WeeWX field radiation, those folks that want radiation from th GW1000 are deriving radiation from WeeWX field luminosity. This is done through the WeeWX StdCalibrate service by placing an entry in weewx.conf under [StdCalibrate] [[Corrections]] as follows:

[StdCalibrate]
    ....
[[Corrections]]
        ....
radiation = luminosity/126.7 if luminosity is not None else None

Interesting regarding uvradiation disappearing after sun down. The GW1000 driver just decodes and provides the data/obs returned by the GW1000 API. If uvradiation data is available from the GW1000 the API response includes an identifying code and the data, if there is no uvradiation data the identifying code and data are absent. Whilst the GW1000 driver knows broadly what sensor suites are present it does not know exactly what individual sensors are present at any point in time, so the driver takes the view that if uvradiation data is not included in the API response then a uvradiation field should not be included in the emitted loop packet. (However, if the API included uvradiation data that was in fact 0 when the sun was down then the loop packet emitted by the driver would contain a uvradiation field that is 0).

You could run the driver directly with the --live-data and --debug=3 options to obtain the raw API response. If you could do a run when the sun is up and again later when the sun is down and if you post the log output from each I could confirm that the uvradiation data is not in the sun down response. The command you would need to run is:

$ PYTHONPATH=/usr/share/weewx python3 -m user.gw1000 --live-data --debug=3

This should result in a number of entries in your WeeWX log that include numerous hex digit pairs.I especially need to see the line starting 'sensor data is'.


--
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].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/439a5c39-6674-bae4-11b4-9d6da54c71bb%40skybase.net.

Reply via email to