I just noticed that on the 30/1 I had a high UV-I reading of 7.0 @ 10:35
The correct high reading should be 1.1 @ 12:00 (from the January log file).
At 10:34:34 I stopped MX 3016
At 10:34:43 I started MX 3016, realised I had something set wrong and immediately Ctrl-C'd it at 10:34:46, the diags show it was still processing the logger data at that point.
At 10:35:12 I started MX 3016 again, no indication of any errors, the midnight roll-over shows it writing the days high UV-I of 7.0
It looks like the last run caused the problem, I've never seen a bad UV reading before (or any other on the VP2). Maybe a one off, maybe due to the previous aborted run, but logged for reference.
Welcome to the Cumulus Support forum.
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Cumulus MX V4 beta test release 4.0.0 (build 4018) - 28 March 2024
Legacy Cumulus 1 release v1.9.4 (build 1099) - 28 November 2014 (a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Cumulus MX V4 beta test release 4.0.0 (build 4018) - 28 March 2024
Legacy Cumulus 1 release v1.9.4 (build 1099) - 28 November 2014 (a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
Oddball UV reading
Moderator: mcrossley
- mcrossley
- Posts: 12695
- Joined: Thu 07 Jan 2010 9:44 pm
- Weather Station: Davis VP2/WLL
- Operating System: Bullseye Lite rPi
- Location: Wilmslow, Cheshire, UK
- Contact:
Oddball UV reading
You do not have the required permissions to view the files attached to this post.
- steve
- Cumulus Author
- Posts: 26702
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: Oddball UV reading
Yes, it got the 7.0 reading from the 10:35 logger entry, you can see it in the WU and WOW 'catchup' uploads. Perhaps I have the archive data decode wrong for UV - presumably you don't often need to use logger data?
Steve
- steve
- Cumulus Author
- Posts: 26702
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: Oddball UV reading
The field I'm using is the one described in the spec as follows:
The given units don't inspire confidence, but that's typical of the Davis documentation. My code looks OK, AFAICT. Perhaps you could try loading a few archive entries with data logging turned on in the latest build, so we can see if it happens again and what the raw data looks like?
Code: Select all
Field Offset Size Dash Value Explanation
High UV Index 32 1 0 Highest UV Index value over the archive period. Units are (Watts / m2)
Steve
- mcrossley
- Posts: 12695
- Joined: Thu 07 Jan 2010 9:44 pm
- Weather Station: Davis VP2/WLL
- Operating System: Bullseye Lite rPi
- Location: Wilmslow, Cheshire, UK
- Contact:
Re: Oddball UV reading
OK, it will have to wait until I finish some plumbing and get the water back on, and until the sun comes out. I don't know which be first
- steve
- Cumulus Author
- Posts: 26702
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: Oddball UV reading
Ah, hold on, I bet I know what the problem is. What the spec should actually say is that the field is in tenths of a unit. The figure you got was actually 0.7.
Steve