I can no longer use the stored data in the data logger with b306

After installing version 306. I can no longer use the stored data in the data logger. I closed WD and all dependent programs. Then installed 306. I did not let WD restart. I then restarted the computer. When WD v306 started up. It hung on getting data from the USB logger. I cancelled that operation. And WD continued to load and run. No other software updated were done.

Mark

Doing checking of time zone calculation
Daylight saving not in use
Loaded all time records
connected OK to com port 4
restarting timer
connected OK to com port 4
*sending DMPAFT
Asking for archived data download
Davis VP Retrieving data from: day 20 month 12 year 2015
Retrieving data from: hour 15 minute 0
ask for time/date of record...
1 6 1
1 1 2
1 2 3
1 0 4
1 0 5
1 24 6
1 212 7
Sending OK...
Aborted
All data downloaded or did not sync correct!
formating the VP data
vp data read in 1
Weather station type number 31



TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
Doing checking of time zone calculation
Daylight saving not in use
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
dodownloadupload2
doftpdown
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
doanythingweather
dohamweather
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
dodownloadupload2
doftpdown
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
doanythingweather
dohamweather
dodownloadupload2
doftpdown
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
dodownloadupload2
doftpdown
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
doanythingweather
dohamweather
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
dodownloadupload2
doftpdown
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
doanythingweather
dohamweather
dodownloadupload2
doftpdown
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA
TED power accessing http://ted5000/api/LiveData.xml:80/DASHBOARDDATA

try doing a complete reset of the data logger
(i.e power down the console, remove batteries, remove data logger for 5 minutes)
then power it all back up
then use weatherlink to set the time/date on the data logger and set data logging interval to 1 minute

I’m up to doing that. But I just got the system back from a refurbishing. No batteries were in it. But they did supply a fresh set of "C"s. I thought that was a nice touch. It’s only been in service about two weeks.
Do you still think it is necessary? It’s a lot of work to get everything set back to were I have it. I could roll back to the version of WD I was using before. Would that be any good?
Mark

its up to you to use my advice
but I stand by my advice to you

I tried your suggestion. It didn’t work. WD hung on getting the data from the logger. After I hit abort. WD then started normally. Minus the 20 minutes of missing data.

Thank you for trying.
Mark

that is odd
as I don’t have any other reports of this particular problem and it works OK here
it could be a settings issue in WD

if you could .zip and email me your settings files then I will test/check here with my Davis station

Sorry for the delay. Power and internet outage. Due to the ice storm. You want the ini and reg files correct?

Mark

While I was waiting for the power to come back on. I took the batteries out and let the display “die”. Still no joy.

there is now a youtube video on how to send me the settings files
http://www.weather-display.com/youtubevideos.php
as well as that being in the FAQ section of the forum

I would also use weather link to delete the archive memory and set/reset the interval to 1 minute

using your settings its works OK here with my Davis Data logger

do you see any error under view,program event log, on restart?

Power just went back on 30 minutes ago. Ice is playing havoc with the trees. I did notice the anemometer is spinning again :slight_smile:
I’ll go back out and try your suggestions.

Thank you
Mark

Tried your suggestions. Still no joy.

I decided to install some windows updates. It has been a bit since I’ve done that. Weird when I restarted the computer after updating it. WD got the data from the logger. Could one of those updates be needed by WD to retrieve stored data?

Mark

more likely a driver issue

I had this same anomoly on my first power up after updating to v306, but it has since cleared.

CHECK THAT YOUR COMPORT is set correct. If no joy there, clear the logger (note data will be lost) then reboot WD. I did this and rebooted WD and things worked fine from there. No problem since. However, almost 12 hours of data was lost - cannot explain it but made no issue of it since it is polling correctly now after the above fix. I just chalked it up to a lost 1/2 day of data.