Page 1 of 1

VVP known issue?

Posted: Sun 11 Aug 2013 12:53 am
by BigOkie
In the diags files, I see a lot of these while running VVP:

Code: Select all

08/07/2013 14:15:00.715 : Writing today.ini, LastUpdateTime = 08/07/2013 2:15:00 PM raindaystart = 6.11999988555908 rain counter = 6.11999988555908
08/07/2013 14:18:21.543 : VP2: LoadCurrentVantageData_V, error = -32701
08/07/2013 14:19:02.824 : VP2: LoadCurrentVantageData_V, error = -32701
08/07/2013 14:19:23.511 : VP2: LoadCurrentVantageData_V, error = -32701
08/07/2013 14:20:00.590 : Writing today.ini, LastUpdateTime = 08/07/2013 2:20:00 PM raindaystart = 6.11999988555908 rain counter = 6.11999988555908
08/07/2013 14:22:48.918 : VP2: LoadCurrentVantageData_V, error = -32701
08/07/2013 14:24:07.215 : VP2: LoadCurrentVantageData_V, error = -32701
08/07/2013 14:24:32.480 : VP2: LoadCurrentVantageData_V, error = -32701
08/07/2013 14:25:00.043 : Writing today.ini, LastUpdateTime = 08/07/2013 2:25:00 PM raindaystart = 6.11999988555908 rain counter = 6.11999988555908
I do note where you see this happening on occasion; it just started happening for me. It never gets to the point where it messages me on the console. So I just shut it down and switched back to direct connections via the USB serial port.

My question is simply this .... is this a known issue and has anyone figured out a way around it if so?

If not, no big deal. I can just dump VVP for now and run direct.

Thanks.

Re: VVP known issue?

Posted: Sun 11 Aug 2013 8:04 am
by steve
The two issues that I know about with VVP when used with the Davis DLL which Cumulus uses are that when sending logger data it sometimes sends 'garbage' entries, and that reads of data sometimes fail, similar to what you're seeing. I had thought that the latter only happened when reading logger data, but it's a long time ago since I looked at it, and I may be misremembering. I think the problem was something to do with the reads of EEPROM data which the DLL does. If you turn on the diagnostic logging in VVP you should see exactly what command the DLL is sending just before the error.

Both of the problems that I found were acknowledged to exist by the author of VVP when he investigated, but he was unable to do anything about them. Davis weren't being particularly helpful to him, I seem to remember.