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)
Flashing light: didn’t think to check (sorry it was 5am) but suspect not
Program Event log: again didn’t check, but in past instances I saw access violations - not sure if they are the same. I have other screen shots of those if you want me to send from the other times this happens. It could be coincidental
Reference deleting the data from logfile. Didn’t think to do that. That I guess is kinda why I always restored the logfile wdisplayini and wdsisplayftp. is there any harm in doing what I did. If so when I get home I will restore the data from prior to the flat line. If not a problem I will leave as is
Really appreciate your help. This has been a big frustration for me since it happens up to 2x a week sometimes more.
what do you mean try another method of getting the data? How else would you get the data??
So do you want me to send you the screen shots of prior access violations?
Do you suspect a memory/resource issue? Ive got 16GB of mem
I restart WD every 2-3 or there abouts days as is. I think yesterday when I got home approx 6pm I restarted. The flat line started about 930pm. The flat lines as I recall have been around 9pm. That seems odd since there are no WD processes that kick in at 9pm.
So I will try to restart WD every day or so for now and keep an eye on memory (sometimes i have many tabs of Safari I keep open - which I know can hog memory).
As I do this are you looking into this from a wd/coding perspective as well?
Btw I’m soon to buy a new Imac. I plan on loading that with alot more memory. My current one btw is only 3 years old so i’m curious this could be a resource issue.
its probably some hard to find and obscure bug in the code that is causing the problem
if you can find a pattern to when the access violations occur that would be great
if you could .zip and email me your settings files then I will try and see if I can duplicate and find out where the access violation error is occuring and why etc
Thanks, when you say settings… assuming you mean WDisplay.ini wdisplayftp.ini - any others? oh and a log file of course
In program event log, when I see the access violations, there is no time stamp. However, in some they seem to be before the resetting warmest night setting - so that would be before 6am.
From recollection many of them are around the 9pm time frame if that helps.
Will send settings and screen shots
I agree finding the violator will be tough so thanks so much in advance
Oh btw I’m on build 285. I saw there was a 288 avail - do you think that will help?
I see that you have not set a time zone (hours) in the sun moon rise/set
(note that west of GMT is postive for this setup)
try setting that
and yes use the latest version as I am improving things all the time
and I see you have that set to be created and uploaded every 5 minutes
that is over kill
the live data comes from the clientraw.txt file
that testtag file takes alot of processing
the live data comes from the clientraw file
the rest of the info only changes less often , so you really only need to have that file updated and uploaded say every hour
try that too (i.e the special file conversion)
similar for extra moon and moon icon
you have that set to be created and uploaded every 5 minutes
and yet the moon info is only going to change daily
so change that to be updated/uploaded daily only