I didn’t check it from the command prompt. I checked it internally from WD. And yes…when this happened previous times, I checked the weatherlink account and the logger was updating that account. I feel like there is a setting in WD that either changed by some desperation to troubleshoot the original issue which was a bad humidity sensor.
Two things changed (actually 3). To troubleshoot the humidity problem, I upgraded to the latest version of WD. That was while I was waiting to get my logger and console back from Davis where they updated the firmware of my (wired) logger which goes to my router over to my WD pc. They also updated the firmware of the Davis console.
first try changing the ethernet cable between the router and pc
if you have the wd backup run look for the month before you started changing things zip file in the data back folder and unzip shut down wd note the time you shut it down, then look for these files in the zip, wdisplayftp.reg file and double click it and click ok then look for the wdisplay.ini you need to edit this use notepad++ and look for Davis download using search as below
and change the date and time to the noted time of the shut down you just did then save then copy the wdisplay.ini to the main wd folder to replace the existing one you can then restart wd should only need to download any missing minutes since the shutdown
if you still have issues then the try unplugging and plugging the ethernet plugs a few times incase the ethernet sockets are tarnished also run the trouble shooter for the network card on the pc has the network card driver been update recently if so try rolling it back
that’s all the things I can think of
You might need to contact Brian by email to see if he can offer any suggestions.
I’m no network maniac. This is what I got from the ping test on the WD pc. No idea what any of it really means. But the thing just disconnected again and I tried to ping while disconnected.
And yes, I have been reseating cables all over the place all along. I haven’t tried replacing any cables as of yet.
Well…this problem has me all twisted up in knots. The issue is that it takes a day or three to wait to see if the changes made will work.
So this is what I did so far. I made a new cable because I have the crimpers to do it. I also bought a Klein Tools cable tester to verify ALL my cables.
I also bypassed the network switch. So it goes direct to the PC from my router.
I tested the cable from the data logger.
I tried a different port on my router.
Cleaned all connectors with contact cleaner.
I have yet to eliminate the PC itself and/or the data logger.
I have an aftermarket logger from METEO Pi. Which I’m not sure how to setup as of yet.
So that leaves 3 components left that I have yet to swap.
So based on what I done, any other ideas? Could it be the ethernet card in the PC? Could it actually be the current logger? That logger has recently had the firmware updated by Davis. And it would seem like that was when this all started…after I got the logger and console back from Davis. Could it be Win7? I have a Win7 laptop that hasn’t been used in literal years that I hesitate to try. I’m stuck, I guess you could say.
EDIT: Got the new logger up and running..we shall see.
You’ve done lots of diagnostics and I can’t think of anything else to try at the moment. Some thoughts…
- Probably not the Ethernet card. They’re pretty robust these days and you’d probably see other issues if it wasn’t working well. You could try looking at network stats to see if there are lots of dropped packets though.
- Your comment about the problem only being apparent after the logger firmware was updated sounds valid to me. Maybe the new firmware works sufficiently differently to the old version that it’s not behaving as nicely. Also, what was the reason for upgrading? Were you seeing problems which prompted you to upgrade, or was it just a case of “there’s a newere version so I should upgrade?”
I know it’s difficult to sift through these long threads. But the reason I sent the logger and console in in the first place was my weather diplay graphs were going wonky. Turns out the humidity sensor was causing it. I wanted them to check the logger for wonky readings. For 80 bucks they did a basic check and upgrade of firmware and replaced some of the console parts that have broken or fallen off over the years. Kind of a tune up if you will. I eventually got a new humidity sensor and the graphs went back to normal. So it was a bad call on my part right from the start. The new logger is still running fine but it’s only been a day.
Sorry - I recall reading the reason now. I did look back up the thread and didn’t spot it. Hopefully the new logger works better. I use a WeatherLink Live box now, but before that I used a MeteoBridge logger. Is that what you’re using at the moment?
Right now I have a MeteoPi and it already dropped off line today. When I first hooked it up, it worked almost right out of the box. Then I tried connecting to Weatherlink. Couldn’t connect to that even after talking to tech support. But since I never look at weatherlink, I didn’t really care.
So What I noticed in WD, is that one of my setting was set to release connection every minute for weatherlink. Today I unchecked that box and disconnected completely from the internet. Seems to be running smoother now as I look at the data received green block steadily flashing for the most part. There’s a conflict somewhere I guess.
How do I completely disable weatherlink in WD. Is that possible? So it quits trying to export to the internet? It’s been so long since I set this stuff up so I can’t remember how I got connected to weatherlink. And last night while laying in bed, I noticed the blue light on the logger repeatedly shutting off. But now it’s solid on since I unchecked that release connection box.
So right now my WD setings are :
Rolled back to build 101 my last working version
Internet main = off
Release connection for Weatherlink = unchecked
Weahterlink.com account deleted.
from memory the ip logger had a software switch to turn the link to weather link on/off you need the DID and key to hand then browse the ip address of the logger and login and look for the tick box to send data to weatherlink and uncheck it my old brain cant remember anymore on how the login works
the ref to WD
in order for the logger to upload to weatherlink the WD connection had to be released so can be unchecked if you have disabled the upload in the datalogger
Are you referring to the Davis logger or the MeteoPi? I connected to weatherlink with the Davis logger. This meteoPi logger seems to not work at all with weatherlink and that’s ok with me. I’m just wondering what to uncheck in WD so it stops trying to connect and screwing me up. I went into the Davis tab in control panel/station type and settings. It appears to be already unchecked and if that’s the case it’s always been unchecked because I never touched it when I had the Davis logger in. As far as the Meteo Pi setup page, I did see a setting to enter DID and key. I could not get the key to save my life so I disabled it. The only reason I used the weatherlink connection was for troubleshooting my original connection problem. I would just like whatever it is to stop trying to upload. Even with my weatherlink account deleted, it could still be trying to upload and screwing me up. Is there any other settings in WD that would cause this?
Suggest you deactivate the upload in the Davis logger anyway as is classed as active and the meteopi may not work as intended the console may also think it’s still got a Davis logger on and still trying to send data even with the meteopi plugged in and no account
I think you have checked all the WD setting I can think of
I don’t think WD uploads to WD. I think with the Davis data logger this is what’s happening…
- WD connects to the logger to download data
- Every minute WD drops the connection
- The logger sees the dropped connection and sends data to WeatherLink
- Goto 1
So as the MeteoBridge logger doesn’t update WeatherLink, there’s no need for step 2 to happen because there’s no step 3. The option you’ve disabled in WD has done all that’s needed by turning step 2 off.
Not sure what you mean by that. The Davis logger is not connected…the MeteoPi is right now. Are you saying there is a setting in the console I should change?
what i am saying is there may be a flag setting in the console setup by the logger hence the deactivation requirement
uncheck the upload to
weatherlink.com put the key in the righthand box and save configuration
note i have remove the DID
Ok..after some thought, I think I see what you are getting at. In other words, disconnect the Meteo and reconnect the Davis logger to the console. At that point call up the IP address of the Davis logger and I should find a setup page, maybe? Then uncheck anything that has to do with Weatherlink. Ok…I’m not going to try that now since thew meteo is still up and running. But if the Meteo should drop again, I will give that a try. Am I correct in this interpretation of your post?
screen shot in my last post
yes wait till it plays up to do it
Ok got it…we must have cross posted 
Welp…we had yet another power outage in my third world section of the grid over here. The Meteo did not reconnect after power was restored. And I had an opportunity to connect up the Davis logger. The weatherlink box was still checked. So I unchecked the box, but I don’t know if the setting stuck. Seems each time I hit save, it would complain about wrong inputs in the blank fields. So I left the box unchecked and hit save and let it complain. I then removed the logger. So I don’t know what that means. Had a heck of a time connecting the Meteo until I rebooted the logger from the setup page. It’s back up and running. Just an FYI
