what station do you have? and what data logger do you have?
I have a davis and I am able to sort of scroll through the console as well as I use weathercat on occasion. I essentially use both programs to generate weather data for me then I put it on a spreadsheet.
By scrolling on the date and time on the console, there is a graph of sorts it shows and I can see some of the information. Using other software I can see if it is the logger or software.
That being said, if you exit weatherdisplay and restart it, does it reload your data logger the same
Is there a time trend there , that is so many days or at certain times of the day. I am guessing that Weatherdisplay is reading the data in the logger. I am guessing it is in the logger reading the same data try purging the logger archive and see if it gets better. (kind of like take a tall glass of prune juice, three capfuls of Miralax in it and seeing how the day goes, not that I have done that, I did 2 caps)
This and the last 2 or 3 I THINK were around 9pm - not sure if that means anything.
On some of them (including last night) I checked program event log and saw some kind of access violation. I will post that when I get home. I didn’t think too much of that on the others because I think they happened after the flat line. I think they happened after the 6am where it resets the coldest night. Thus I assumed not related. Plus I think I have gotten those before.
Is there any troubleshooting that I can do on my end?
Btw once again hook up to davis VP and all the data is restored !!!
I am actively working on WD mac version at the moment
to get the data flowing again, what do you need to do?
i.e go to the com port setup?
(i.e if you go there and click on OK, does the connection get reconnected? i.e the more information you can provide, the better)
Thanks… when this happens I usually don’t notice it until the next am. So I go into my time machine backup and restore the WDIsplay.ini WDISPlayftp.ini and log file - then restart WD all is fine
Never tried what you suggested… Doing that I would not get the historical data from the time of the flat line until I notice it (like I said usually the next day)
I guess I could try that just to see if it reconnects and then also restore the files as mentioned above to get the missing data
you can still get history data
but setting the time/date to get the data from
under control panel, data logger setup
then restart WD
wether you get the usb data flowing again or not
if you get get the data flowing again via just going to the com port setup and clicking on OK
then that would be good
but I could also change the way the program gets the data to the way the new ported linux version does it. it might be more stable
yes
but what I was wanting to know is if you can get the data flowing again (before trying to get the missing data)
by simply going to the comport setup and clicking to open the com port there
but we could try this different way of getting the data
Gotcha… Sorry about that. I will give that a try. Often times I notice it 5am when I get up and am out the door in minutes so usually rush it. But I will make every effort to try that out next time
I did try to open the com port to see if that helped - it did not.
Another thing I noticed which I never did before and would explain the flat line - the record count at the bottom of the screen was not incrementing
Thanks to you I used the data logger option to reset the time and get all the data back - HUGE time savings vs. TM Backup. However, the graph times
were all messed up - but don’t suspect that matters. I have a screen shot but forgot to send it to myself before I left. I can attach later, but I think you know what I mean.
what is means is that WD was not getting any more data
re the record count not increasing
that is the sort of detailed information that I need
was the data received light flashing?
was there any errror under view, program event log?
also when setting the time to get the data from and then restarting WD,you would need to have deleted the flat line data from the logfile first so that after you could convert the logfile to data file
I could add to WD to check for the flat line and so to then stop logging the same data all the time…and to also stop updating when WD was not runnning…so a restart it would get the missing data and all would be good
for some reason your usb data is stopping
we could try this other method of getting the data (that I use with the linux version, as well as adding the above flat line check)