WXforum.net
Weather Station Hardware => Davis Instruments Weather Stations => Topic started by: weatheroz on April 21, 2018, 06:56:13 PM
-
Just noticed since yesterday that I'm no longer connecting to my Weatherlink IP, and even going directly to it via browser, I'm failing to connect.
I'm assuming it has died all of a sudden, for reasons unknown.
Nothing else has died on my local network, so I'm for now assuming it died of 'natural causes'.
This is rather disappointing for it to fail this way, so I'm wondering if anyone else has had their Weatherlink IP fail like this ?
-
Interestingly I've pulled the old serial data logger out of my old VP2, done the uninstall/install routine, and it comes up as an incompatible datalogger !!
I've also tried another Weatherlink IP I had accidentally ordered a few years ago, and still can't get my weather data.
Is there a default IP address that these WL IP's come up with? ... I would have thought they'd go DHCP , but nothing is showing up there for me.
-
I would suspect more to do with the network/router than the WLIP at this stage. Do you know how your WLIP is configured on the network, Static or DHCP? Do you have Weatherlink software? If so have you tried to find the logger under the Communications Port>Local Port ID> Find?
Two things you could try first is re-booting your router, if no changes then remove all power from the console, reseat logger then repower
-
I would suspect more to do with the network/router than the WLIP at this stage. Do you know how your WLIP is configured on the network, Static or DHCP? Do you have Weatherlink software? If so have you tried to find the logger under the Communications Port>Local Port ID> Find?
Two things you could try first is re-booting your router, if no changes then remove all power from the console, reseat logger then repower
I'm running a static IP to the weatherlink IP, and have also tried to find it using that same method without any luck.
I've power cycled my network switch that it runs through, as well as removing all power from console, removed the logger, even replaced it with another one without any luck. :(
-
Would you have another console to prove it's not the console?
-
Would you have another console to prove it's not the console?
Okay, just tried that.
appears to have killed my old console now.... the display is full of corrupted data. :(
Although after powering it off for a few minutes has rectified it.
Even the main console I have been using, I plugged in a brand new weatherlink IP, and still couldn't see it on my network.
Okay, now I've tried a brand new weatherlink IP in to my old console, and it still can't be seen.... seems like not so much weatherlink ip, but something awfully screwy on my network
-
Try replacing your Ethernet cables, try different port on router/switch/hub etc.
-
Try replacing your Ethernet cables, try different port on router/switch/hub etc.
One of the first things I tried was both changing cables and ports. :(
Just makes no sense it has stopped without any changes being made to my network.
disabled firewall on the machine as well, in case that was it.
-
Too late now I know, but I really don't recommend using a static IP address unless unavoidable due to local policies - it often ends up causing tricky problems. Best to stick to DHCP if at all possible.
If you run a network scanner like AngryIP can you see an IP address for your logger?
I assume that you have rebooted your console - again if necessary - that the console is definitely running on mains power, not battery power and that no changes have been made to the private IP address range your router is using?
It may be worth trying to download and run the IP logger firmware update tool from the Davis site. This only has a limited chance of working - if the updater tool can't see the logger then it obviously can't work. But sometimes it does fix this sort of problem.
-
Too late now I know, but I really don't recommend using a static IP address unless unavoidable due to local policies - it often ends up causing tricky problems. Best to stick to DHCP if at all possible.
If you run a network scanner like AngryIP can you see an IP address for your logger?
The IP is showing up as red rather than blue, so it's getting no response.
I assume that you have rebooted your console - again if necessary - that the console is definitely running on mains power, not battery power and that no changes have been made to the private IP address range your router is using?
Yes, definately running from mains power, not just batteries.
I actually have public address range coming down my link.
I haven't changed anything here though.
It may be worth trying to download and run the IP logger firmware update tool from the Davis site. This only has a limited chance of working - if the updater tool can't see the logger then it obviously can't work. But sometimes it does fix this sort of problem.
Didn't know there was an update. I'll go look now for it, unless you have a link I could try for it.
-
Didn't know there was an update. I'll go look now for it, unless you have a link I could try for it.
The update itself is probably of no consequence, unless your logger is quite old. But reflashing is just one way of clearing any possible corruption in the logger that may have occurred. I'm not very optimistic that it will work because the update utility obviously needs to be able to talk to the logger across the network, but always worth a try. Other thoughts:
Do you definitely get the right number of beeps at reboot? (3 for a regular VP2 console, but maybe you have a Vue or Envoy?)
If still no luck can you take the unit eg to a friend's house with a different network and see if that helps at all?
-
update couldn't find it..... got the 3 beeps with a pause between them for my vp2 console.
Don't have a crossover cable, but I'm sure I could find a switch/hub and a laptop tomorrow to try something similar to see if that makes a difference.
So frustrating that it suddenly happened.
-
And just to clarify, you have added/connected absolutely nothing to this network?
-
what about resetting the router
-
And just to clarify, you have added/connected absolutely nothing to this network?
nothing new ... have rebooted router too, but no change.
Might be time to disconnect stuff one by one to see if something else is hammering it.
-
I have had an IP data logger die on me before
-
Latest news is that I can ping it on my network, but can not access it.
The activity led is happily flashing away on it.
I've put in my spare WL IP (I accidentally ordered it when I ordered the 6163 station several years ago), and it is now running on my vp2.
The older WL IP is now in my older VP2, with the activity led flashing away, but not pingable, let alone accessible
I've flashed it to 1.12 firmware, from a laptop that was not on my network.
-
http://wiki.trixology.com/index.php?title=How_to_setup_the_Davis_WeatherLinkIP%E2%84%A2_data_logger (http://wiki.trixology.com/index.php?title=How_to_setup_the_Davis_WeatherLinkIP%E2%84%A2_data_logger)
http://www.wxforum.net/index.php?topic=17689.0 (http://www.wxforum.net/index.php?topic=17689.0)
https://www.weather-watch.com/smf/index.php?topic=33060.0 (https://www.weather-watch.com/smf/index.php?topic=33060.0)
IF you put in the IP address of your IP logger do you get this , but for your logger. here is my IP logger that goes to my WL2.0
-
OK then where did FW 113 come from, has that been released yet or is this a very new WLIP?
-
What operating system(s) and version(s) are your computers using?
Was there an update just prior to noticing the problem?
(For instance - there was/is a problem with the latest Windows 7 update, that affected networks.
-
What operating system(s) and version(s) are your computers using?
Was there an update just prior to noticing the problem?
(For instance - there was/is a problem with the latest Windows 7 update, that affected networks.
Windows 7 here.... initially could only access a new one on winxp, then later could do it on Win7.
However that original WLIP is still not accessible, although it was for a while visible to the updater software, but not from anything else.
-
I'm guessing that the "nothing" that changed, was one or more Windows 7 updates.
What are the static IP addresses of the WLIPs? And what are the IP addresses of the Windows XP and the Windows 7 computers?
-
I'm guessing that the "nothing" that changed, was one or more Windows 7 updates.
What are the static IP addresses of the WLIPs? And what are the IP addresses of the Windows XP and the Windows 7 computers?
They are all on the same network, and are all publically addressable IP's too... gateway is .129 , WLIP's are .136 and .169 , the Win 7 box is .133
The WinXP box was disconnected from the rest of the network, and connected to the WLIP by switch that wasn't connected up to the rest of the network, just the WLIP's.
The WLIP that I was having the issues was then visible to WL updater, but not otherwise visible.
In response to Aardvark's
IF you put in the IP address of your IP logger do you get this , but for your logger. here is my IP logger that goes to my WL2.0
Not with the original WLIP which started this all off, however with my other WLIP, it does.
-
wake up today, and WLIP is not connecting.... this is the new one I put in the other day.
using a browser to the IP that it is on, won't bring up the configuration page anymore.
Can ping it fine from this computer.
I can't afford to buy another WLIP as they are just short of $400 each to buy over here.
This is really doing my head in, I've contacted Davis themselves via email, but have yet to get an email response back from them since this problem first started.
-
wake up today, and WLIP is not connecting.... this is the new one I put in the other day.
And I see it's back in operation.
(The Jimboomba box image in your signature seems to be present if it's working, and absent if it isn't). Do you suppose that might be a clue? I don't know, of course.
The problem is with your network and/or the NIC card settings on your computer. Davis can't help. We can't help with the limited information available. It has been suggested that you get rid of the static IP settings on the WLIPs. That might or might not help.
-
wake up today, and WLIP is not connecting.... this is the new one I put in the other day.
And I see it's back in operation.
(The Jimboomba box image in your signature seems to be present if it's working, and absent if it isn't). Do you suppose that might be a clue? I don't know, of course.
The problem is with your network and/or the NIC card settings on your computer. Davis can't help. We can't help with the limited information available. It has been suggested that you get rid of the static IP settings on the WLIPs. That might or might not help.
The weather tag is done in ImageSalsa, and part of it is data from WD, but time of day and date is added by IS.
Well I would if I could... I can't change the settings in WLIP now because I can't get back in to it.... I wish I could.
The old WLIP was running Static IP address for years without an issue, but now it no longer works.
-
I think you should be focusing your attention to the network/routers/cables/ISP and "other", just because the "WLIP" doesn't appear to be working doesn't mean it's a WLIP issue. By the way you don't have a Meteobridge do you?
-
The old WLIP was running Static IP address for years without an issue, but now it no longer works.
The WLIP works. You just can't access it.
wake up today, and WLIP is not connecting.... this is the new one I put in the other day.
(The Jimboomba box image in your signature seems to be present if it's working, and absent if it isn't). Do you suppose that might be a clue? I don't know, of course.
The weather tag is done in ImageSalsa, and part of it is data from WD, but time of day and date is added by IS.
So?
Why does it sometimes appear as part of your signature in this forum, and sometimes does not appear? Perhaps that's related to your network problems?
-
still no luck.
I can ping the IP address of both weatherlink IP's, but am unable to access either of them.
I've been bouncing emails to Davis themselves, but it's like extractiing teeth with them, as apparently they are short staffed at the moment... takes about a week to get an email responded to.
So not particulary happy.... sadly my old datalogger to my old Davis vp2 is incompatible with my new vp2, so can't even go the serial route, and I just can not afford to buy a third data logger at this point of time.
-
3rd party data logger option maybe?
E. G the new Wi-Fi one?
-
.... sadly my old datalogger to my old Davis vp2 is incompatible with my new vp2....
Very very annoying that situation isn't it :mad:
-
3rd party data logger option maybe?
E. G the new Wi-Fi one?
Didn't realise there was a new wifi version available now.
-
.... sadly my old datalogger to my old Davis vp2 is incompatible with my new vp2....
Very very annoying that situation isn't it :mad:
Certainly is, otherwise my weather station would be back on the air now.
I just don't have another $300 to throw away on a new one if I were to buy one over here, and then I've still got two non-working IP ones, which are currently set to a static IP address.
-
I would also check your power adapter. I had a similar incident last year and after consultations with Davis Australia, they indicated to check the power supply and new batteries.
The final outcome was the power supply was failing and as soon as it was replaced I have had no issues.
-
I just don't have another $300 to throw away on a new one if I were to buy one over here, and then I've still got two non-working IP ones, which are currently set to a static IP address.
It would be good if someone with some network skills could document a way of recovering these loggers. I suspect that there's a good chance that the loggers are still working OK, but that there are network issues that are preventing adequate communications to reset the loggers. Don't things like the ARP or RARP commands offer some prospect of finding out what's going on?
But this does remind me that assigning static IP addresses to IP loggers does not seem to be a good idea.
-
I just don't have another $300 to throw away on a new one if I were to buy one over here, and then I've still got two non-working IP ones, which are currently set to a static IP address.
It would be good if someone with some network skills could document a way of recovering these loggers. I suspect that there's a good chance that the loggers are still working OK, but that there are network issues that are preventing adequate communications to reset the loggers. Don't things like the ARP or RARP commands offer some prospect of finding out what's going on?
But this does remind me that assigning static IP addresses to IP loggers does not seem to be a good idea.
There should be no issues with assigning a static IP address as long as it is not within the DHCP range.
It was only last night when doing the firmware update to console to 3.80 that I reverted to DHCP reservation.
-
There should be no issues with assigning a static IP address as long as it is not within the DHCP range.
Of course there shouldn't be. But that doesn't alter the fact that the difficult-to-fix problems seen with IP loggers are often associated with people unthinkingly setting static IP addresses. So in practice, my advice always is that unless you have a strong reason for choosing static then it's always best left at the default dynamic address. A lot fewer support calls that way!
-
I would also check your power adapter. I had a similar incident last year and after consultations with Davis Australia, they indicated to check the power supply and new batteries.
The final outcome was the power supply was failing and as soon as it was replaced I have had no issues.
Now that's an interesting idea, but this is happening with two different vp2's and two wlIP data loggers.
I really hope this is the problem, but Davis USA haven't suggested that one yet, and this is going back over 3 weeks now.
Don't suppose you happen to know the appropriate voltage and current required ?
-
I just don't have another $300 to throw away on a new one if I were to buy one over here, and then I've still got two non-working IP ones, which are currently set to a static IP address.
It would be good if someone with some network skills could document a way of recovering these loggers. I suspect that there's a good chance that the loggers are still working OK, but that there are network issues that are preventing adequate communications to reset the loggers. Don't things like the ARP or RARP commands offer some prospect of finding out what's going on?
But this does remind me that assigning static IP addresses to IP loggers does not seem to be a good idea.
Is this "do not do static IP" due to people assigning static IP's out of a DHCP range ? or is there another reasoning ?
I considered some network issues myself, and ran up a lap top to switch to datalogger using the same IP's, but totally isolated from the rest of the network, all via ethernet cabling, no wireless. Sadly didn't make any difference. :(
Any one know how to put a WLIP back to factory defaults? flashing it doesn't do it.
-
oh, yes, it could very well be the power supply
I have had problems with that before come to think of it now
-
Is this "do not do static IP" due to people assigning static IP's out of a DHCP range ? or is there another reasoning ?
Yes, but a bunch of other things too, like people getting a new router or simply forgetting the IP address or simply having an upload failure and then asking how to troubleshoot it on a different network (sometimes with a completely different private IP range). Quite often, the users are not very network savvy and for whatever reason thought that static was a good way to go.
Overall, it's just an association of intractable problems with IP loggers and using a static IP address.
-
I would also check your power adapter. I had a similar incident last year and after consultations with Davis Australia, they indicated to check the power supply and new batteries.
The final outcome was the power supply was failing and as soon as it was replaced I have had no issues.
Now that's an interesting idea, but this is happening with two different vp2's and two wlIP data loggers.
I really hope this is the problem, but Davis USA haven't suggested that one yet, and this is going back over 3 weeks now.
Don't suppose you happen to know the appropriate voltage and current required ?
No it was so long ago but I just had a look on the site below which at least has more guidance towards managing the device then Davis themselves.
http://www.davisinstruments.com.au/troubleshooting
-
I'm facing a similiar situation since yesterday. I tried to update firmware version, as Davis recommended, and I realised that my VP2 was offline. Today I did all process to reboot everything, without success. WLIP have a static IP, IP is active and I can ping to it with success, however the station is offline and I can't access the configuration page. I brought the WLIP to my home to swap with the WFL I have running. Lets see if it will work. When you talk about power source, should be AC adaptar replaced for one with more amperes?
-
I was never able to get either of my WLIP to work again.
I eventually got myself one of those wireless ones from the UK, that has worked fine since.
Sorry for you, but glad to see I wasn't the only one to suffer a WLIP failure.
-
I was never able to get either of my WLIP to work again.
I eventually got myself one of those wireless ones from the UK, that has worked fine since.
Sorry for you, but glad to see I wasn't the only one to suffer a WLIP failure.
If it will not work again, will be the second WLIP to die since 2013.
-
weather link live has now replaced the IP data logger
-
Fortunataly, today aftert 4 days disconnected from console, I connected again WLIP and connected my laptop via cable at the same network and could update WLIP firmware, download data and it's online again. I don't know if it was because WLIP was many days disconnected or what, but, it's working again!
-
Fortunataly, today aftert 4 days disconnected from console, I connected again WLIP and connected my laptop via cable at the same network and could update WLIP firmware, download data and it's online again. I don't know if it was because WLIP was many days disconnected or what, but, it's working again!
I have experienced exactly this behavior in the past, years ago. Running perfectly since:
http://farrera.atmos.cat
-
Same problem here. My WLIP keeps going silent - stops responding and is inaccessible via IP. Only way to restore operation is to remove it from the console and plug it back in again - which is a pain as it is at a remote site 250 miles away!
Is there a better way to get an IP data feed from my Vantage Pro set up? The WLIP sends data to a Mac running WeatherCat that then creates the charts for my website. Was thinking a Meteobridge Pro Red - removing the need for the console? Now the WLIP is discontinued what are the alternatives for uploading weather data to my own server?
-
Now the WLIP is discontinued what are the alternatives for uploading weather data to my own server?
There's no obvious reason why your WLIP should be regularly misbehaving unless it's an interaction with your router's DHCP service, eg too short an IP lease? (Or is the WLIP actually a bit loose in its socket?)
Yes, MB Pro Red is one good option, or eg Nano or Nano SD, though WiFi Logger would be a drop-in replacement for the WLIP.
That said, many users are switching to Weatherlink Live and taking the annual subscription to achieve archive storage in the cloud. But if you need graphs to be uploaded to your own website then you would need to run some local software like CumulusMX in addition to WLL itself.
-
Thanks John - have tried assigning it a fixed IP or using ‘Bind IP to Mac’ on my router so it never needs to refresh it’s IP address. Same issue persists - it is as though it ‘crashes’ if that is possible. Hadn’t thought of Nano but will take a look - my idea was to bypass the console so I can remotely reboot the system if needed (cannot do that with the console because of the battery backup, or needing to configure after power outage). Am I right in thinking the console provides barometric pressure data - and calculations such as wind chill? If so do I lose these if I opt for the Meteobridge Red Pro approach?
I have a website used by the local sailing club with tide data etc so have no wish to pay Davis for a Weatherlink subscription.
-
Hmm, WLIP loggers are usually pretty reliable. If there is any issue with needing a reboot it's usually something like
* Some interaction with the router causing a non-sticky IP address;
* A logger that's not tightly held in its socket;
* Running firmware that's not up-to-date;
Of course, it's impossible to rule the possibility of a failing logger, but that genuinely is pretty rare. It almost sounds like you need a remote reboot facility using something like https://www.openxtra.co.uk/aviosys-ip-power-9255-with-single-uk-socket-ip9255uk.html (NB I've not used this at all so it's just an idea rather than a recommendation.) If you're running up-to-date VP2 console firmware then the console should automatically exit set-up mode after something like 10-15 minutes - can't recall the precise time.
Any logger that fits into the console like Nano or WFL is going to face potentially the same reboot issue, though as above that is potentially solvable.
Weatherlink Live could potentially pass data to a local Raspberry Pi running (free) software like CumulusMX if you still wanted graph generation.
MB Pro Red is also a good solution and does contain its own pressure sensor.
-
My WLIP is working, I did the firmware upgrade required, but my historical data is not available on Weatherlink APP and I can't make web download since this episode...strange.
-
My WLIP is working, I did the firmware upgrade required, but my historical data is not available on Weatherlink APP and I can't make web download since this episode...strange.
Well, maybe your WLIP is only working for current data and not archive data - that's what it sounds like? But this is probably just a solvable problem that might just need a reboot of the WLIP console, or checking console date, ie the usual checks.
-
Well, maybe your WLIP is only working for current data and not archive data - that's what it sounds like? But this is probably just a solvable problem that might just need a reboot of the WLIP console, or checking console date, ie the usual checks.
Yes, just current data. Console data is right, I gonna try reboot. Should I disconnect WLIP, all that process?
-
What remove the logger from the console? Personally I wouldn't bother, at least not in the first instance. Just fully (ie no batteries) power down the console, leave off for a minute or two and then repower. Remember that archive data is only uploaded once per hour, so leave it at least an hour before checking the archive data again.
-
Now the WLIP is discontinued what are the alternatives for uploading weather data to my own server?
There's no obvious reason why your WLIP should be regularly misbehaving unless it's an interaction with your router's DHCP service, eg too short an IP lease? (Or is the WLIP actually a bit loose in its socket?)
Yes, MB Pro Red is one good option, or eg Nano or Nano SD, though WiFi Logger would be a drop-in replacement for the WLIP.
Sadly there seem to be more and more WLIP that are failing for reasons unknown.
I took 3 months back and forth with Davis about mine, and they really didn't have a clue as to why it was failing.
Got the WiFi logger, and it's been working fine for me since then.