Virtual VP and VpLive logs with warnings and errors etc...

[BigD]

Anyone else's logs look like these:

21:10:11:608 Bug          - TVpCom.BeatNotify: Get Live Sensor Data command timed out, but there is something in the InBuff
21:10:11:608 Warning      - VpConsole: No response after several retries for Get Live Sensor Data
22:40:07:096 Warning      - VpConsole: No response after several retries for Wake Up Console
22:41:37:306 Warning      - VpConsole: No response after several retries for Wake Up Console
22:41:37:446 Warning      - VpConsole: Far too long since last loop = 7.841, last command= Get Live Sensor Data
22:41:50:074 Warning      - VpConsole: Far too long since last loop = 6.490, last command= Get Live Sensor Data
23:31:54:124 Warning      - VpConsole: No response after several retries for Wake Up Console
23:31:54:494 Warning      - VpConsole: Far too long since last loop = 8.232, last command= Get Live Sensor Data
00:00:02:452 Warning      - VpConsole: No response after several retries for Wake Up Console
00:30:06:516 Bug          - TVpCom.BeatNotify: Wake Up Console command timed out, but there is something in the InBuff
00:30:06:526 Warning      - VpConsole: No response after several retries for Wake Up Console
00:30:07:137 Warning      - VpConsole: Far too long since last loop = 5.478, last command= Get Live Sensor Data
00:30:08:949 Warning      - VpConsole: No response after several retries for Wake Up Console
01:40:07:587 Warning      - VpConsole: No response after several retries for Get Live Sensor Data
01:40:08:007 Warning      - VpConsole: Far too long since last loop = 6.089, last command= Get Live Sensor Data
03:03:14:618 Warning      - VpConsole: No response after several retries for Get Live Sensor Data
05:10:12:612 Warning      - VpConsole: No response after several retries for Get Live Sensor Data
06:05:20:688 Warning      - VpConsole: Far too long since last loop = 5.078, last command= Get Live Sensor Data

Here's VP Live:

10/27/2009 22:07:48:261 Info         - *** Program starting up: VPLive 1.1.10.14 VPLive ***
10/27/2009 22:07:48:291 Info         - Windows version = Windows XP (v. 5.1.2600 Service Pack 3)
10/27/2009 22:08:08:510 Warning      - No response to Stop Stream Mode (Timed out)
10/27/2009 22:08:08:530 Warning      - Console: No response after several retries for Stop Stream Mode
10/27/2009 22:08:11:955 Warning      - No response to Get EEPROM Data binary (Timed out)
10/27/2009 22:08:11:955 Warning      - Console: No response after several retries for Get EEPROM Data binary
10/27/2009 22:08:14:869 Warning      - No response to Get Time (Timed out)
10/27/2009 22:08:14:890 Warning      - Console: No response after several retries for Get Time
10/27/2009 22:08:18:104 Warning      - No response to Get Console Diagnostics (Timed out)
10/27/2009 22:08:18:104 Warning      - Console: No response after several retries for Get Console Diagnostics
10/27/2009 22:08:23:161 Warning      - No response to Get Barometer Data (Timed out)
10/27/2009 22:08:23:171 Warning      - Console: No response after several retries for Get Barometer Data
10/27/2009 22:08:23:171 Error        - Console: Several consecutive failures of console to respond. Will try to reconnect.
10/27/2009 22:08:23:602 Warning      - No response to Start VirtualVP Fast Loop Mode (Timed out)
10/27/2009 22:08:23:612 Warning      - Console: No response to Start VirtualVP Fast Loop Mode
10/27/2009 22:08:29:581 Warning      - Console: Did not receive expected Live Sensor Data packet
10/27/2009 22:08:34:728 Warning      - Console: Did not receive expected Live Sensor Data packet
10/27/2009 22:08:41:157 Warning      - Console: Did not receive expected Live Sensor Data packet
10/28/2009 00:10:06:603 Warning      - No response to Get Barometer Data (Timed out)
10/28/2009 00:10:06:603 Warning      - Console: No response after several retries for Get Barometer Data
10/28/2009 03:30:06:769 Warning      - No response to Get Barometer Data (Timed out)
10/28/2009 03:30:06:769 Warning      - Console: No response after several retries for Get Barometer Data
10/28/2009 03:43:05:679 Warning      - No response to Get Barometer Data (Timed out)
10/28/2009 03:43:05:679 Warning      - Console: No response after several retries for Get Barometer Data
10/28/2009 03:50:05:182 Warning      - No response to Wake Up Console (Timed out)
10/28/2009 03:50:07:746 Warning      - No response to Get Barometer Data (Timed out)
10/28/2009 03:50:07:746 Warning      - Console: No response after several retries for Get Barometer Data
10/28/2009 06:40:05:960 Warning      - No response to Get Barometer Data (Timed out)
10/28/2009 06:40:05:960 Warning      - Console: No response after several retries for Get Barometer Data
10/28/2009 06:50:08:436 Warning      - No response to Get Barometer Data (Timed out)
10/28/2009 06:50:08:436 Warning      - Console: No response after several retries for Get Barometer Data
10/28/2009 09:01:05:995 Warning      - No response to Get Barometer Data (Timed out)
10/28/2009 09:01:05:995 Warning      - Console: No response after several retries for Get Barometer Data
10/28/2009 09:30:06:147 Warning      - No response to Get Barometer Data (Timed out)
10/28/2009 09:30:06:147 Warning      - Console: No response after several retries for Get Barometer Data

I have all the default log options checked, No Info or verbose.

[tweatherman]

I'm starting to have problems with vplive also showing CRC errors when trying to download every hour.

Tim

[tinplate]

Errors at midnight are normal, as the console stops responding for a little while when the internal end of day processing occurs (the console does not multi-task). You can also cause these error by pressing the Forecast button on the console. While the forecast message is scrolling, the console completely ignores the communications with the PC. The same thing also happens if you put the console into setup mode. So some of these sorts of errors are innocuous, although there's no way for VVP or VPLive to know if a glitch in the communications is normal (like the forecast thing), or a problem. They just keep trying until they can get communication re-established.

If you're sure these normal causes are the culprit, then it may be a problem if you see more than one or two of these little drops every day.

Steve
SoftWx

[tweatherman]

Make sure you don't have a bad wlk file in your folder that's what I discoverd on my end with wrong date that happened around daylight savings time change.

Tim

[BigD]

Thanks guys for the tips, I browsed through the .wlk files they all look good,

The system still works fine  just reports allot of what appear to be "issues" "Error" and "bug" in the logs.

I may try the WL5.90 again and steve's new VVP and see if that helps.