Help! VirtualVP V1.2.3 hanging "Could not read archive page nn"

It started a bit ago… the connection to the Davis VP1 console (serial → Belkin serial/USB port) would suddenly stop working. It thought it might be my B&B 9POP4 serial optoisolator, but that’s been replaced.

On startup of VirtualVP 1.2.3, the ‘Reading Archive data’ screen pops up, indicates 96% reception, has 5 bars filled in, and just stops. I’ve deleted the archiveCache.dat and archiveCache.dat.tmp files, with the same result.

Also tested with WeatherLink directly connected (not through VirtualVP) and it reads the datalogger fine.

The log.txt for VirtualVP shows

12/12/2009 21:50:09:042 Warning - VpConsole: No response after several retries for Get Archive Page
12/12/2009 21:50:09:042 Warning - Archive page packet failed CRC check, requesting again
12/12/2009 21:50:09:136 Error - Could not read archive page 56
12/12/2009 21:50:15:948 Warning - VpConsole: No response after several retries for Get Archive Page
12/12/2009 21:50:15:948 Warning - Archive page packet failed CRC check, requesting again
12/12/2009 21:50:15:964 Error - Could not read archive page 56
12/12/2009 21:50:22:277 Warning - VpConsole: No response after several retries for Get Archive Page
12/12/2009 21:50:22:277 Warning - Archive page packet failed CRC check, requesting again
12/12/2009 21:50:22:277 Error - Could not read archive page 56
12/12/2009 21:50:29:152 Warning - VpConsole: No response after several retries for Get Archive Page
12/12/2009 21:50:29:152 Warning - Archive page packet failed CRC check, requesting again
12/12/2009 21:50:29:214 Error - Could not read archive page 56
12/12/2009 21:50:30:480 Warning - VpConsole: No response after several retries for Wake Up Console
12/12/2009 21:50:36:683 Warning - VpConsole: No response after several retries for Get Archive Page
12/12/2009 21:50:36:683 Warning - Archive page packet failed CRC check, requesting again
12/12/2009 21:50:36:699 Error - Could not read archive page 56
12/12/2009 21:50:37:871 Warning - VpConsole: No response after several retries for Wake Up Console
12/12/2009 21:50:44:027 Warning - VpConsole: No response after several retries for Get Archive Page
12/12/2009 21:50:44:027 Warning - Archive page packet failed CRC check, requesting again
12/12/2009 21:50:44:121 Error - Could not read archive page 56
12/12/2009 21:50:45:387 Warning - VpConsole: No response after several retries for Wake Up Console
12/12/2009 21:50:51:606 Warning - VpConsole: No response after several retries for Get Archive Page
12/12/2009 21:50:51:606 Warning - Archive page packet failed CRC check, requesting again
12/12/2009 21:50:51:652 Error - Could not read archive page 56
12/12/2009 21:50:52:902 Warning - VpConsole: No response after several retries for Wake Up Console
12/12/2009 21:50:59:012 Warning - VpConsole: No response after several retries for Get Archive Page
12/12/2009 21:50:59:012 Warning - Archive page packet failed CRC check, requesting again
12/12/2009 21:50:59:028 Error - Could not read archive page 56
12/12/2009 21:51:00:309 Warning - VpConsole: No response after several retries for Wake Up Console
12/12/2009 21:51:06:543 Warning - VpConsole: No response after several retries for Get Archive Page
12/12/2009 21:51:06:543 Warning - Archive page packet failed CRC check, requesting again
12/12/2009 21:51:06:559 Error - Could not read archive page 56
12/12/2009 21:51:07:747 Warning - VpConsole: No response after several retries for Wake Up Console
12/12/2009 21:51:07:747 Error - VpConsole: Too many consecutive failures of console to respond. Will continue trying periodically.
12/12/2009 21:51:08:465 Error - Could not read archive page 56
12/12/2009 21:51:35:247 Error - Access violation at address 004A8271 in module ‘VirtualVP.exe’. Read of address 00000008
12/12/2009 21:51:35:247 Error - Access violation at address 004AD283 in module ‘VirtualVP.exe’. Write of address 00000388

Virtualvp.ini has

[Localize]
Language=1
[Preferences]
SerialNo=
AutoConnect=1
ReadMeAtStart=0
MinimizeAtStart=0
MinArchiveReception=50
AnimateTraffic=1
UpdateSpeed=1
ShowDisabled=1
AlertAscending=0
LogFileLevel=6
[Communications]
VpIsSerial=1
VpPort=3
VpBaud=19200
ComUsbFix=0
ComUsbDevice=USB\vid_10c4&Pid_ea60
VpAddress=
VpIpPort=22222
VpReleaseIp=0
VpIpExtraTime=1000
AllowFastLoop=1
VirtMode1=2
VirtName1=WeatherLink
VirtTCPAddress1=127.0.0.1
VirtTCPPort1=5511
VirtTCPRunHW1=0
VirtTCPHWPort1=6
VirtVCOMPort1=15
VirtProtect1=1
VirtMode2=2
VirtName2=WeatherDisplay
VirtTCPAddress2=127.0.0.1
VirtTCPPort2=5512
VirtTCPRunHW2=0
VirtTCPHWPort2=7
VirtVCOMPort2=16
VirtProtect2=1
VirtMode3=2
VirtName3=VWS
VirtTCPAddress3=127.0.0.1
VirtTCPPort3=5513
VirtTCPRunHW3=0
VirtTCPHWPort3=8
VirtVCOMPort3=17
VirtProtect3=1
VirtMode4=2
VirtName4=Cumulus
VirtTCPAddress4=127.0.0.1
VirtTCPPort4=5514
VirtTCPRunHW4=0
VirtTCPHWPort4=9
VirtVCOMPort4=18
VirtProtect4=1
VirtMode5=0
VirtName5=Virtual Console5
VirtTCPAddress5=127.0.0.1
VirtTCPPort5=5511
VirtTCPRunHW5=0
VirtTCPHWPort5=3
VirtVCOMPort5=0
VirtProtect5=0
VirtMode6=0
VirtName6=Virtual Console6
VirtTCPAddress6=127.0.0.1
VirtTCPPort6=5512
VirtTCPRunHW6=0
VirtTCPHWPort6=3
VirtVCOMPort6=0
VirtProtect6=0
VirtMode7=0
VirtName7=Virtual Console7
VirtTCPAddress7=127.0.0.1
VirtTCPPort7=5513
VirtTCPRunHW7=0
VirtTCPHWPort7=3
VirtVCOMPort7=0
VirtProtect7=0
VirtMode8=0
VirtName8=Virtual Console8
VirtTCPAddress8=127.0.0.1
VirtTCPPort8=5514
VirtTCPRunHW8=0
VirtTCPHWPort8=3
VirtVCOMPort8=0
VirtProtect8=0
[Forms]
TFormMainLeft=632
TFormMainTop=624
TFormMainWidth=620
TFormMainHeight=370

console.txt has


Firmware=Nov 20 2006 (Rev B)
Model=VP 2
BarCal=0.078
Latitude=37.3
Longitude=-122
Elevation=374
DaylightSavingsMode=Auto
DaylightSavings=Off
TimeZoneMode=TimeZoneIndex
TimeZoneIndex=4
GMTOffset=-8
UseTX=01
RetransmitTX=02
Station0=Unrecognized (16) (0)
Station1=No Station (255)
Station2=No Station (255)
Station3=No Station (255)
Station4=No Station (255)
Station5=No Station (255)
Station6=No Station (255)
Station7=No Station (255)
UnitBits=00
UnitBitsComp=FF
AMPM=0
AMOn=0
DateFormat=0
WindCupSize=1
RainCollectorType=0
RainCollectorSize=0.01
LatitudeHem=N
LongitudeHem=W
RainSeasonStartMonth=7
ArchivePeriod=5

The alerts.txt file is empty.

Any help would be appreciated … as it is, my station is offline until this can be resolved.

Best regards,
Ken

Just the obvious questions, not that I can help but might assist with trouble shooting.

What OS
Virus Scanner running?

What happens if you clear the VP data logger?

H.

Windows XP Pro SP3 latest patches
AV - McAffee

It seems that direct connect from WeatherLink 5.9.0 to the station also fails after a while with a 'Computer gave up waiting for a response from the station. Check port settings and connections."

This happens with or without the optoisolator installed. Without the optoisolator, I get a 112/114 mph wind reading due to a ground-loop … hence the need for the 9POP4 optoisolator :slight_smile:

I’m wondering if the datalogger in the VP could be failing somehow… it is 5 yrs old and has been in continuous service.
I’m lothe to just reset the datalogger (thereby causing a ‘hole’ in my WD data), but I’d appreciate any other guidance folks may have.

I’m still using VP 1.1.4 Guess I am behind a bit.

I would try a complete power down and removal of the data logger for a while
to reset it

when re powering it up, then you will need to set the time/date, 1 minute logging interval

yes you will then miss data for that period of time though

also try just running WD , i.e not through virtualvp, as a test?

has the console had a firmware update recently?

The 5.9.0 version of WeatherLink seems to have much tighter timeout values. The error WeatherLink is showing is what it shows when it keeps timing out. If both WeatherLink and VVP are having communication issues talking to the datalogger, I would look first at your connections. You probably know the routine, but try unplugging and replugging both ends of the serial connectors several times.

I’m not familiar with the optoisolator. Is that a new addition, or have you had that on and had everything working before?

Did this start with v.1.2.3?

I would try a few things before resetting the archive and losing that data.

Can you email me a copy of the archiveCache.dat file?

Steve
SoftWx

Hi

I have exactly the same problem and i used both latest versions of Virtual VP.

Any updates for the problem ?

Nikolas

I spent a fair amount of time trying to accomodate WeatherLink 5.9’s less forgiving timeouts, and had it working well in my tests, so I thought I had succeeded. There are a few things you can try. One is trying 5.9.1, a beta version of WeatherLink that is supposed to fix some of the problems in 5.9.0. Another is to try configuring WeatherLink to talk to VirtualVP via IP instead of a com port. In my testing it seemed that WeatherLink allowed much more generous timeouts for IP connections than for serial connections. The third, though admittedly less desirable thing to try is running the previous version of WeatherLink (5.8.x) which doesn’t seem to have the timeout issue.

Steve
SoftWx

Hi Steve

I unistall all and reinstall again. It the beginning seemed Ok but after some tasks started again.

Espesially when i use Toms WXSIM weather programm. In away creates a problem to Virtual VP.

But i guess not only his software. I guess that maybe any programm that runs behind it and the performance of the cpu goes very high…or if at the same time you do other work also

In my other pc in a remote location , i have just the alert about …VPconsole Far too long since last loop 5,531 last command Live sensor data…but other than that it works ok. In that pc i am running also 3 web cameras with the Blue Iris software and the CPUs performance is high also

On the other hand maybe its not very convinient just to have a pc dedicate for weather also.

Maybe you can find a away so Virtual VP wont hang up so easily…

Thanks

Nikolas