I currently have a pretty old Vantage Vue with a USB logger. I’m still in the dark ages with regards to weather recording, and I’m afraid I’m quite happy there😁! I don’t want to upload to the web or run dedicated equipment continuously. I’ve just started with WD, and decided to upgrade my equipment. I’ve got a Vantage Pro 2 which I’m going to have to return, my fault as I hadn’t realised it was so big and it’s going to be very difficult to site easily, especially as the anemometer has to be ultimately connected to the rest of the unit.
My next question is whether there is anything else I can use. I’ve looked at ecowitt as they have sensors which can be located anywhere and added to if required. But I think, if I understand correctly, the HP2553 doesn’t act as a ‘logger’ from which you can periodically download data, I’d have to have the GW1000 also which would need to be continuously connected to communicate with WD. I’d be very grateful if someone could confirm this, and that basically if I wish to remain unconnected and totally independent I’ll have to stay with the Davis logger and Vue? Thanks very much.
Yes there is a differentiation between what Davis calls a logger and how Ecowitt stations work in what they call either a console/gateway device.
The Davis logger, well it logs and keeps a certain amount of archive data depending what logging interval you configure. The Davis loggers will then keep this data that can be used to catch up or update other destinations such as WD software (or other software) and Weatherlink.com. What is required is that the logger needs power in order to keep logging.
The Ecowitt hardware constantly receives live data and it will immediately make that data available various destinations of your choosing. This can be a computer running WD or other software or it can upload to online services. If these destinations are not kept running or accessible then the moment passes and that data didn’t get saved.
A lot of Davis users make a big deal about the advantage of having a logger that logs and keeps this data. I see the appeal on one hand, but having an Ecowitt station and creating a means of continually capturing and saving that data is almost like building your own logger. Its like the combination of the Ecowitt hardware with your WD software system together makes a logger. All you need to do is keep power running and you wont miss data. The Davis logger needs power just as well. Granted I believe the Davis logger can run on batteries whereas the Ecowitt doesn’t run on batteries…but you can add a UPS (battery backup) to your Ecowitt console/gateway device and to your WD computer and keep it running. Still I understand the extra level of security that is provided by the Davis method of their logger and perhaps running on battery provides a longer more energy efficient run time than a decent UPS could. I would say though that running WD or other software on a Raspberry Pi is a way to require very little power and a decent size UPS could probably run your WiFi, the Ecowitt hardware, and the Pi for a decent amount of time…maybe sufficent or maybe the Davis would still outlast it…I’m not sure. But the point is that there are safeguards you can take with the Ecowitt to ensure continued logging into WD or into other software.
The Ecowitt HP2553 (HP2551-C) console does have an SD card slot that will log as long as that console is kept powered up. With a bit of .csv file header manupulation I’m sure you could easily import that data into WD or into other software. So the Ecowitt display console is a logger as it can have the storage to become a logger. It is just not an automatic thing to pull that data out later…as it takes a bit of manual work.
I also believe in sending you data to more than one place. If you value the data this much then just sending it to WD is just putting all faith in that system. Even if it is a Davis system. For that reason uploading to WU is not a bad idea. I know people that ran other software that has now been discontinued and they’ve wanted to migrate the data to some new software like WD only to find out that there are gaps in their data that they though they had all along. Turns out that since they were also uploading to WU that this becomes a secondary backup of their data that then can then pull down and import into their new software to fill the gaps. I hear you don’t want to upload your data online anywhere but it does provide some benefits.
But uploading to WU isn’t your only means to secondary data location. With the right hardware and software you could end up saving your data to two different locations. That could be two different systems both running WD or you could use the opportunity to run WD along with some other software. Then if your WD system goes down or if for example Windows or macOS decides to do an update that then prevents WD from starting up…etc…you’d then still have the data on that other system. With proper planning you can accomplish that with either Davis or Ecowitt.
Thank you very much for a swift and detailed reply, much appreciated.
From your last paragraph then, I could, with some work on my behalf, run the console ‘dumb’ logging to the SD card, create a .csv file to mimic an already existing format then import it into WD.
I need to think about how I really want/need to proceed. I’ve been currently uploading the logger data to WeatherLink (PC) and a program called wswin both of which I regularly back up, but I take your point that this isn’t the most efficient way of doing things. Thanks once again.
I would only consider the SD card in the Ecowitt display console as an emergency backup of the weather data. By all means do get the display console and put an SD card in it but I highly recommend that you also invest in the Ecowitt GW1000 which will allow you to feed WD software live data. Then just keep your WD system up and running 24/7 and put a nice UPS on it (and also on your WiFi).
I do now remember why some people like the Davis loggers…they can power down their computers and as long as they power them up once before the logger is full they turn on their computer and pull all the data that the logger has accumulated. But these days investing in a small space and resource light Raspberry Pi and keeping that powered 24/7 should be a minimal concern…and they are quite reliable (as long as you rely on external storage).
You may wish to look into the Ecowitt HP3500B or HP3501. These are data-logging consoles, but are not currently compatible with WD.
I prefer the HP2551 display console that also does SD card logging to .csv format.
Just to let you know, I have an HP2553 plus GW1000 on order. Hopefully the totally separate sensors will allow easy placement In the garden and I’ll worry about the logging when I have the station set up. I’d still prefer the Davis Logger option as it runs happily off the battery if needed, but I’ll see how I get on with the SD card too. Thanks for all of your help and interest.
I found the documentation lacking for the use of the SD card with the HP2553 (HP2551-C) console. It appears as though the card must be removed, and inserted into another device to retrieve the data from it. The HP3500/HP3501B will send the file directly to your computer. This is why I’m focusing on the HP3500/HP3501B.