The usermanual of the Davis WeatherLinkIP datalogger suggests that the data logger (I’m connected to the WeatherEnvoy) should come back on-line (green light) after a power failure whilst leaving the ethernet connection in place. However, it is my continuing experience that under these circumstances, the data logger LOCKS-UP. The only way to get it working again is by disconnecting the data logger from the router/switch, restore power and after the two beeps, re-connect data logger ethernet port. For a remote site this is an obvious annoyance.
I would like to learn from other Davis Weatherlink IP users whether they experience the same and availability of any remedial solution.
Obviously, the issue has been brought to the attention of DAVIS Technical support, but I’m yet to receive any response.
Rgds
Dick Wismeijer
I think the best overall solution in this scenario is to run the Envoy from a chunky UPS.
But, do you have batteries in the Envoy? Does the power outage take the Envoy offline completely, ie so that the problem you’re seeing is that the WLIP is not reinitialising correctly after a complete power outage. Or is it that the batteries are not providing enough power to run the WLIP? (Or maybe that even with batteries in place, a mains outage still always drops the Ethernet connection?)
One problem with the WLIP is that it consumes a lot more power than the standard logger (I have seen 100x the power quoted). So even with the standard console there’s only back-up battery power available for not much more than a day. With the Envoy, the batteries are obviously substantially smaller. I’ve never seen an actual figure quoted for Envoy battery life with WLIP fitted, but I’d guess that it might be just a few hours. And if you’re starting out with batteries that are perhaps partially discharged then maybe they can’t sustain the voltage that the WLIP needs for more than a brief time.
John, thanks for your quick reply to which the following applies. The WeatherEnvoy with IP datalogger runs from a Belkin UPS. However, the power outage suffered extended beyond the time available from the UPS. Indeed, the power outage took all equipment off-line, i.e. main power supply failure due to fallen trees knocking down overhead power lines. A situation which did not inhibit WHS and router to come back on-line after power restoration but the WLIP failed to re-initialize, despite passing the two “beeps”. I do not have batteries installed in the Envoy. I’m yet uncertain whether these should be ordinary Alkaline bateries or re-chargeable ones.
Though installing batteries (which ones?) may have avoided the current (remote-)fallout, it does not eliminate the observation that the WLIP performs differently than described in the manual which could be attributed to a firmware mismatch. An issue I wish to see being acknowledged or denied to gain confidence in the equipment performance.
The batteries should be the best-quality alkaline ones you can get, in order to get maximum battery life. (I’m not sure about lithium non-rechargeable ones, which I know you can get. I can’t think of any obvious reason why they shouldn’t work OK and maybe they would give better life still, but I haven’t seen any official guidance from Davis on this.) AFAIK the consoles don’t have any capability to recharge the batteries and it is officially recommended not to use rechargeables, I think mostly on the basis that they have less capacity than good alkaline.
On the principle that the WLIP should come back online automatically, I don’t disagree at all with this. But it’s perhaps worth remembering that the WLIP is still a relatively new product and there may still be bugs in particular circumstances that still haven’t been fully ironed out. Presumably you are using the v1.04 firmware? Davis are generally a good company when it comes to support, but there’s no doubt that if you have a problem that frontline support don’t have a detailed answer for, then it is often more difficult to establish a dialogue with the software/firmware engineers. You can send in a fault/bug report but beyond perhaps an acknowledgement of your email, there won’t necessarily be any further feedback until some months later if/when a bug-fix is released.
Dick,
My IP logger is installed in the Davis console, not in a WeatherEnvoy. In my Portugal house we have several times short power disturbs in a week and the logger is always stating up without any problems. I use Duracell alkaline battery’s in the console and change theme every half year. An UPS is not installed because of a power fail also the phone lines are dead.
Henk
Henk, this is encouraging news. It looks like that my ignorence not to install batteries has resulted in a self inflicted problem. However, in a recent communication with Davis I have been advised that indeed they have found necessary modifications to the firmware resulting now in Beta release 1.06 whilst I’m running 1.04. Their website though only provides download of firmware version 1.04 So its everyone’s guess what entails version 1.05 and 1.06 releases in such a short term.
Just to make sure I understand you correctly, your console is normally connected to the mains supply and you have installed the Alkaline batteries or ar you running just from Alkaline batteries.
Rgds
Dick
Yes, the console is powered by the mains adapter and fitted with alkaline batteries but I did not test the console and the IP logger on batteries, next time when I am in Portugal I will check if the console and logger are running only on the batteries in the console.
Hi I am new to this forum, but I have just notice the same problem with my VP1 envoy after a power failure, which I find very frustrating. If any one knows of a solution it would be much appreciated. The only way I can get the Envoy back on line is to remove the new batteries and the power cord. Also I have notice that my dew point recording with weatherunderground is -73 after re-powering.
I have always believed using a UPS with the weather station and computer. I have mine plugged into my APC UPS and get some extra time when the power goes out. Ideally I would like to use one just for the weather console and I have one, but I need the floor space. When the power goes out, it still runs onthe UPS after the auto shut down for the computer kicks in. The modem … router are also running and then the batteries kick in on the console.
Not sure, but the problem with needing the reset might be to protect the data circuit … perhaps you could write the tech support dept at Davis and ask them then post what they tell you as to what causes it and what is the solution.
I have the IP unit and have made it through a power failure when the UPS ran out of juice. and it came back on line and we were fine. But I also had a logger fail as well within in a week… I think it was a flawed unit. Maybe yours is flawed and needs to be replace. I would contact Davis really…
I have tested my IP Data logger just shutting down the power. I have none of these problems. It’s online by it’s self.
I have the Vantage Pro 2 - Weatherlink IP using firmware 1.0.4
the IP logger will pull power from the console big time and drain the batteries in short notice. So that is why Davis wants the console AC powered, not relying on the backup batteries.
I think you have a defective unit… Contact Davis and have them send you an exchange. They did it for me when mine did that. I had to multiple time unplug it from the router, then from the console and put it back and repower until one day it gave it up. I called Davis tech support and they immediately said that they would exchange mine with a new one from them. so far it works.
The 1.06 is out on davis’ site: http://www.davisnet.com/support/weather/download/WeatherLinkIP_firmware_v106.exe
By the way, a friend of mine just received a cabled console with a 1.80 firmware (current on the site is 1.75a). So stay tuned
Jean-Marc,
Thanks for the info about the update, hope this will help to solve some of the regular data loss due communication trouble.
I downloaded it and it install flawlessly. I haven’t had much trouble with mine since the first time … the first one died… froze up and then burned out. the second still is running fine… (well it doesn’t run, it stays on the wall… didn’t want anyone to think it actually ran #-o)(