Statistics DavisVP2+ are not given by webtags API

[HansR]

Using the webtag API to display the Davis VP2+ statistics it displays none.
Using logging I can determine the values are not given by the API. It used to work.
Seems to have stopped with build 3093 (not sure).
Below the corresponding debug/Data logging. If you need more, let me know. The data is in the console, I checked the statistics screens.
And it does not work either when using a file testT.txt (attached) and have it processed by CMX.
(no hurry )

Code: Select all

2020-09-08 07:21:00.081 Writing log entry for 8-9-2020 07:21:00
2020-09-08 07:21:00.081 max gust: 12,1
2020-09-08 07:21:00.083 Written log entry for 8-9-2020 07:21:00
2020-09-08 07:21:00.087 Writing today.ini, LastUpdateTime = 8-9-2020 07:21:00 raindaystart = 516 rain counter = 516,2
2020-09-08 07:21:00.497 LOOP: Data - 3: 4C-4F-4F-00-00-1E-06-89-75-B9-02-41-51-02-03-01-99-00-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-5D-FF-FF-FF-FF-FF-FF-FF-00-00-00-05-00-00-00-FF-FF-01-00-64-00-15-0A-06-00-2D-00-F5-07-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-2F-03-06-2C-8F-02-D4-07-0A-0D-16-CC
2020-09-08 07:21:00.497 LOOP: 3 - Data packet is good
2020-09-08 07:21:02.491 LOOP: Data - 4: 4C-4F-4F-00-00-1E-06-89-75-B9-02-41-51-02-03-01-99-00-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-5D-FF-FF-FF-FF-FF-FF-FF-00-00-00-05-00-00-00-FF-FF-01-00-64-00-15-0A-06-00-2D-00-F5-07-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-2F-03-06-2C-8F-02-D4-07-0A-0D-16-CC
2020-09-08 07:21:02.492 LOOP: 4 - Data packet is good
2020-09-08 07:21:04.488 LOOP: Data - 5: 4C-4F-4F-00-00-1E-06-89-75-B9-02-41-51-02-03-01-99-00-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-5D-FF-FF-FF-FF-FF-FF-FF-00-00-00-05-00-00-00-FF-FF-01-00-64-00-15-0A-06-00-2D-00-F5-07-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-2F-03-06-2C-8F-02-D4-07-0A-0D-16-CC
2020-09-08 07:21:04.488 LOOP: 5 - Data packet is good
2020-09-08 07:21:06.472 LOOP: Data - 6: 4C-4F-4F-00-00-1E-06-89-75-B9-02-41-51-02-03-01-99-00-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-5D-FF-FF-FF-FF-FF-FF-FF-00-00-00-05-00-00-00-FF-FF-01-00-64-00-15-0A-06-00-2D-00-F5-07-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-2F-03-06-2C-8F-02-D4-07-0A-0D-16-CC
2020-09-08 07:21:06.472 LOOP: 6 - Data packet is good
2020-09-08 07:21:08.496 LOOP: Data - 7: 4C-4F-4F-00-00-1E-06-89-75-B9-02-41-52-02-03-01-99-00-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-5D-FF-FF-FF-FF-FF-FF-FF-00-00-00-05-00-00-00-FF-FF-01-00-64-00-15-0A-06-00-2D-00-F5-07-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-2F-03-06-2C-8F-02-D4-07-0A-0D-01-DD
2020-09-08 07:21:08.496 LOOP: 7 - Data packet is good
2020-09-08 07:21:10.143 API tag: Processing API JSON tag request
2020-09-08 07:21:10.143 API tag: Input string = ?version&build&ProgramUpTime&NewBuildAvailable&NewBuildNumber&CpuCount
2020-09-08 07:21:10.153 API tag: Output string = {"version":"3.8.3","build":"3093","ProgramUpTime":"0 days 19 hours","NewBuildAvailable":"0","NewBuildNumber":"3093","CpuCount":"4"}
2020-09-08 07:21:10.492 LOOP: Data - 8: 4C-4F-4F-00-00-1E-06-89-75-B9-02-41-52-02-04-01-99-00-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-5D-FF-FF-FF-FF-FF-FF-FF-00-00-00-05-00-00-00-FF-FF-01-00-64-00-15-0A-06-00-2D-00-F5-07-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-2F-03-06-2C-8F-02-D4-07-0A-0D-A9-6C
2020-09-08 07:21:10.492 LOOP: 8 - Data packet is good
2020-09-08 07:21:12.488 LOOP: Data - 9: 4C-4F-4F-00-00-1E-06-89-75-B9-02-41-52-02-04-01-99-00-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-5D-FF-FF-FF-FF-FF-FF-FF-00-00-00-05-00-00-00-FF-FF-01-00-64-00-15-0A-06-00-2D-00-F5-07-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-2F-03-06-2C-8F-02-D4-07-0A-0D-A9-6C
2020-09-08 07:21:12.488 LOOP: 9 - Data packet is good
2020-09-08 07:21:14.484 LOOP: Data - 10: 4C-4F-4F-00-00-1E-06-89-75-B9-02-41-52-02-04-01-99-00-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-5D-FF-FF-FF-FF-FF-FF-FF-00-00-00-05-00-00-00-FF-FF-01-00-64-00-15-0A-06-00-2D-00-F5-07-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-2F-03-06-2C-8F-02-D4-07-0A-0D-A9-6C
2020-09-08 07:21:14.485 LOOP: 10 - Data packet is good
2020-09-08 07:21:16.490 LOOP: Data - 11: 4C-4F-4F-00-00-1E-06-89-75-B9-02-41-52-02-04-01-99-00-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-5D-FF-FF-FF-FF-FF-FF-FF-00-00-00-05-00-00-00-FF-FF-01-00-64-00-15-0A-06-00-2D-00-F5-07-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-2F-03-06-2C-8F-02-D4-07-0A-0D-A9-6C
2020-09-08 07:21:16.490 LOOP: 11 - Data packet is good
2020-09-08 07:21:18.495 LOOP: Data - 12: 4C-4F-4F-00-00-1E-06-89-75-B9-02-41-51-02-03-01-99-00-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-5D-FF-FF-FF-FF-FF-FF-FF-00-00-00-05-00-00-00-FF-FF-01-00-64-00-15-0A-06-00-2D-00-F5-07-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-2F-03-06-2C-8F-02-D4-07-0A-0D-16-CC
2020-09-08 07:21:18.496 LOOP: 12 - Data packet is good
2020-09-08 07:21:20.488 LOOP: Data - 13: 4C-4F-4F-00-00-1E-06-89-75-B9-02-41-51-02-04-01-94-00-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-5D-FF-FF-FF-FF-FF-FF-FF-00-00-00-05-00-00-00-FF-FF-01-00-64-00-15-0A-06-00-2D-00-F5-07-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-2F-03-06-2C-8F-02-D4-07-0A-0D-D2-19
2020-09-08 07:21:20.488 LOOP: 13 - Data packet is good
2020-09-08 07:21:20.556 API tag: Processing API JSON tag request
2020-09-08 07:21:20.557 API tag: Input string = ?DavisTotalPacketsReceived&DavisTotalPacketsMissed&DavisMaxInARow&DavisNumCRCerrors&DavisFirmwareVersion&DavisNumberOfResynchs&battery&txbattery
2020-09-08 07:21:20.557 API tag: Output string = {"DavisTotalPacketsReceived":"0","DavisTotalPacketsMissed":"0","DavisMaxInARow":"0","DavisNumCRCerrors":"0","DavisFirmwareVersion":"1.73","DavisNumberOfResynchs":"0","battery":"4,78","txbattery":"1-ok 2-ok 3-ok 4-ok 5-ok 6-ok 7-ok 8-ok"}
2020-09-08 07:21:22.483 LOOP: Data - 14: 4C-4F-4F-00-00-1E-06-89-75-B9-02-41-51-02-04-01-92-00-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-5D-FF-FF-FF-FF-FF-FF-FF-00-00-00-05-00-00-00-FF-FF-01-00-64-00-15-0A-06-00-2D-00-F5-07-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-2F-03-06-2C-8F-02-D4-07-0A-0D-AA-26
2020-09-08 07:21:22.484 LOOP: 14 - Data packet is good
2020-09-08 07:21:22.814 Realtime[251]: Start cycle
2020-09-08 07:21:22.815 Realtime[251]: Creating realtime.txt
2020-09-08 07:21:23.914 Realtime[251]: End cycle
2020-09-08 07:21:24.469 LOOP: Data - 15: 4C-4F-4F-00-00-1E-06-89-75-B9-02-41-51-02-04-01-92-00-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-5D-FF-FF-FF-FF-FF-FF-FF-00-00-00-05-00-00-00-FF-FF-01-00-64-00-15-0A-06-00-2D-00-F5-07-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-2F-03-06-2C-8F-02-D4-07-0A-0D-AA-26
2020-09-08 07:21:24.470 LOOP: 15 - Data packet is good

[mcrossley]

Have you enabled fetching reception stats in the config?

[HansR]

Have you enabled fetching reception stats in the config?

Yes I have.
And it's not only with me btw.
I checked some other cutils sites as well and e.g. Conligwx's site.
All no stats.
No big deal, needs to be done sometime.

[ConligWX]

Have you enabled fetching reception stats in the config?

Yes I have.
And it's not only with me btw.
I checked some other cutils sites as well and e.g. Conligwx's site.
All no stats.
No big deal, needs to be done sometime.

You mean these ones?

Code: Select all

Total Data Packets received	0	 
Total Data Packets missed	0	 		
Number of Console to ISS resynchs	0	 		
Number of Packets with CRC errors	0

yep these were usually low if not zero on my end when I installed the WLL. Marks site shows zeros too at this time.

[mcrossley]

Whilst I'm away, you could try <#DavisTotalPacketsReceived tx=0>
The VP2 stats are all on tx=0 - which should be the default if you do not supply a tx=n parameter, but!...

The WLL records the stats per transmitter ID, so if you have a WLL then you need to specify the tx=n parameter for each transmitter you have configured.
The VP2 only records the stats for the ISS transmitter, which I save to tx=0 for backwards compatibility.

[HansR]

I tried, did not work with the testT.txt file.
Will try it in cutils but to be honest, that is basically the same: just through the interface.
So assume no luck unless reported otherwise.
Thanks anyway

[mcrossley]

I tried this on my debug build with a VP2 console and the stats show OK.
Tried on an old 3.7.2 build I'd left running on pi zero, and it is working OK there too - different VP2 console obviously.

Code: Select all

http://192.168.50.135:8998/api/tags/process.json?DavisTotalPacketsReceived&DavisTotalPacketsMissed&DavisMaxInARow&DavisNumCRCerrors&DavisNumberOfResynchs

Code: Select all

{"DavisTotalPacketsReceived":"16629","DavisTotalPacketsMissed":"185","DavisMaxInARow":"614","DavisNumCRCerrors":"47","DavisNumberOfResynchs":"0"}

¯\_(ツ)_/¯

[mcrossley]

Ah, I spoke too soon, I see sometimes it is not getting the response it expects and sets the values to zeros instead of ignoring or retrying. More looking required...

[HansR]

Ok.
Btw: i use 'localhost'.
Can't be, can it?

[ConligWX]

I tried this on my debug build with a VP2 console and the stats show OK.
Tried on an old 3.7.2 build I'd left running on pi zero, and it is working OK there too - different VP2 console obviously.

Code: Select all

http://192.168.50.135:8998/api/tags/process.json?DavisTotalPacketsReceived&DavisTotalPacketsMissed&DavisMaxInARow&DavisNumCRCerrors&DavisNumberOfResynchs

Code: Select all

{"DavisTotalPacketsReceived":"16629","DavisTotalPacketsMissed":"185","DavisMaxInARow":"614","DavisNumCRCerrors":"47","DavisNumberOfResynchs":"0"}

¯\_(ツ)_/¯

3.8.3 on mine shows:

Code: Select all

{"DavisTotalPacketsReceived":"0","DavisTotalPacketsMissed":"0","DavisMaxInARow":"0","DavisNumCRCerrors":"0","DavisNumberOfResynchs":"0"}

[mcrossley]

I have found an issue, it surfaces particularly if the option to enable barometer reads is enabled (which is shouldn't be for 99% of Davis users I suspect).
I have rewritten the functions that get reception stats, get the firmware version, and force the baro update to use some common code that should be more robust than the byte counting used originally.

[HansR]

I have found an issue, it surfaces particularly if the option to enable barometer reads is enabled (which is shouldn't be for 99% of Davis users I suspect).
I have rewritten the functions that get reception stats, get the firmware version, and force the baro update to use some common code that should be more robust than the byte counting used originally.

OK. We'll see. Don't understand the baro issue btw.
Hope you had a nice holiday

[mcrossley]

I'm still on holiday - off again tomorrow, but doing a bit of poking around tonight.

Baro thing is...

ForceVPBarUpdate=0

[HansR]

Ah, that's for the 1 minute update versus the 15 minute update?
But how do I know if I should use that?

Anyway, thanks. Saw the new release.
Enjoy the rest of the holidays

[freddie]

Ah, that's for the 1 minute update versus the 15 minute update?
But how do I know if I should use that?

It's a VP firmware version thing. Older versions only did a barometer read every 15 min but you could force more frequent reads by using this ini file switch. Newer firmware versions read the barometer more often. If you search the forum you will find the firmware version before which you would need to use the switch.