Topic: Vantage Vue console not detected by PC

[cjwhome]

I have a Vantage Vue weather system, and a Vantage Vue Console with a data logger to read the data into the Weatherlink software on a PC.  I bought the system in 2011, and it worked successfully until the middle of 2024, when the PC stopped seeing the data logger, and therefore did not read in any further data.

I tested the system as advised by Davis - power down the console, unplug the datav logger, plug it in again, power up, and see if it does 4 beeps.  If yes, it is working properly, if no it is not working.

I got the 4 beeps, but the PC still said "device not found".

I bought a new data logger, and got exactly the same problem.

I tried with

1) two different USB cables

2) two different USB sockets on the same PC

3) two different computers

4) two different data loggers

all to no avail.

At that point, I gave up, and opened a Weatherlink account so I could continue to see the data, in both numerical and graphical form

However, I now realise that the old PC version is much nicer to use -  much easier to move through different dates and to select/deselect different datasets. It also gives a variety of reports at the click of the mouse

NOAA this month
NOAA Sunmmarise month
NOAA this year
NOAA summarise year
Yearly rainfall

I couldn't find these on the web system though maybe I have missed them.

I thought I would have one last try, and bought a second-hand Vantage Vue console on ebay.  Alas, this didn't work either.  There is an additional problem in that the new data logger is registered by the replacement Console as "Incompatible" even though the two consoles have the same model number as do the two data loggers.

I wonder if there is anything else anyone can suggest that I try, to get the data to download to a PC?   I wonder if it is a Windows problem - some update which is not compatible with the software? Both computers are using Windows 10.  I tried to install the software on my new laptop which is using Windows 11 and it failed - is the old Weatherlink software incompatible with Window 11?  I could try installing Windows 7 (if it is gettable!) on an old PC and see what happens.

If not, maybe I need to think again about trying to convert the data from the web to a form which the old Weatherlink software can read????

Or maybe I am flogging a dead horse....

Any suggestions/advice welcome.

[johnd]

I could write a long answer, but the background information is all here:

https://www.manula.com/manuals/pws/davis-kb/1/en/topic/green-dot-loggers

https://www.manula.com/manuals/pws/davis-kb/1/en/topic/understanding-wl-comms-issues

and various other pages on the knowledgebase.

On weatherlink.com you need the Pro subscription to retrieve historical data, including monthly summaries. An annual summary is on the roadmap for the future I believe but not yet implemented.

[cjwhome]

I bought the system from Prodata in either late 2010 or the beginning of 2011 - weather station, console and data logger.  I'm not sure I have the receipt but I can look!  But it is well out of warranty so I'm sure you are not obliged to help!

Just to clarify:

Console 1 and datalogger 1 worked from 2011 to 2024 without any problem and then stopped working. - the PC said "Device not found.  Please connect device".  The console otherwise still works fine.

I bought a new data logger  which I will call data logger 2 from Davis Instruments in July 2024 hoping this would rectify the problem but it didn't - I got the same error.  Note that data logger 2 was compatible with Console 1 ( at least I didn't  get a message to the contrary)

I tried a different USB cable, a different USB port and a different PC, but the same thing happened.

I then gave up on the PC, and set up a PRO SWeatherlink account so I could see graphs etc.  I uploaded all the old data from the  PC so I can view my data back to the beginning in 2011.

However, I recently decided I prefer the old PC based software, so bought a second hand Console from ebay - Console 2.  It also works fine except again the PC does not see it. It is happy with the data logger 1, but says that data logger 2 in incompatible.  I get the same message as before on the PC - "device not detected".  So I maybe have two dodgy consoles.  or two dodgy data loggers - nexcept one was brand new.

Or there is a problem with both PCs,  Or both PC operating systems.

PS I couldn't find a relevant forum - could you direct me to this?

And thanks to everyone for trying to help.

[johnd]

please read the links i sent. All the information to understand and fix the problem is there.

[cjwhome]

johnd

Thank you.  I've read those links.

My  original data logger, bought in 2011,  has a manufacturing code C.  it is compatible with my original console (also bought in 2011), manufacturing code D

It is not compatible with my second console (second hand) manufacturing code MF, which ties in with the information in the first article.

My second data logger, bought new last year, has a manufacturing code E and is compatible with both consoles, as again fits in with that article.

I have four possible combinations of console and logger.

C! + D1 - compatible
C! + D2 - compatible
C2 + D1 - incompatible
C2 + D2 - compatible

C1 + D1 worked fine for 13 years, and then stopped working. 

Two of the other three combinations, whihc shoujld work, now show the same fault as the first.  This suggests that the fault is not a data logger or a console problem.  Replacing the cable, using a different USB port, or a different PC gives the same fault so unlikely to eb any of these either.

I've looked at the second article but don't see anything there that could be causing the problem.    The set up is the same as it was from 2011 to 2024.

But thanks for you advice.

[johnd]

Have you really been through the checklist at:

https://www.manula.com/manuals/pws/davis-kb/1/en/topic/communications-troubleshooting

If a USB logger appears to stop working then it's often because the USB mode has somehow changed unexpectedly (ie USB to serial or vice versa) and needs to be corrected, or that the console baud rate has changed away from the default 19200.

Loggers are also not immune from going faulty especially if there might have been a nearby lightning strike or a major mains spike for some reason, but it is pretty rare. Most likely is that the logger has just flipped to the wrong mode.

[cjwhome]

I did a lot of checks when the fault happened first.  Followed all the instructions I could find and nothing worked.

Baud rate is 19200.  All 3 working systems give 4 beeps when rebooted.

The fault occurs with a new data logger as well as the old one, so not a lightining strike!

Not a cable, port or PC problem as I've tried replacing all three.

The "Communications port" on the PC software doesn't detect the console, so I can't test or alter anything there.

Dead horse???

[johnd]

Yes, but you're not answering the question of whether you have checked the USB/serial mode setting and corrected it if necessary.

[cjwhome]

Johnd

Time for a grovelling apology.

I thought I had gone through all these things after I bought the new data logger.

Have tried now and results as follow:

Old Console  + old data lgger - fails on both Serial and USB
Old Console + New data logger -fails on Serial, WORKS on USB
New Console  + old data looger  - not compatible
New Console + new data logger - fails on Serial WORKS on USB

So it looks as if the old data logger had failed, and the new data  logger only works on USB and I didn't try doing this when I bought it.  Nor since....

So grovelling apololgy again and Mega thank you, as I now have a working PC weatherlink.

Also, while I didn't need to buy a new console, I did need to buy a new data logger (I think....)

 

[johnd]

OK, that's good news. And it's always a complication trying to explain about the serial and USB settings - I wish Davis had never introduced the USBX option TBH - it's caused countless problems over the years, and all for no real benefit AFAICS. But that's ancient history now.

But I wouldn't give up on the old logger just yet. Of course it's possible that eg the memory chip has gone faulty or some such, but the fact that you hear 4 beeps on booting the console is a positive sign. Personally I would have a go at running the utility to force the logger into Serial/VCP mode - you might just strike lucky. I have known USB loggers getting stuck in a way that they don't respond to either USB or serial interfaces but it's been possible to revive them with this utility. You should then be able to switch between USB mode (USB button the Weatherlink comms port setting) and Serial (Must be done via the utility) at will.

[cjwhome]

Following the old saying "If it aint broke, dont fix it", I will stick to old console, new data logger for now, and keep the old logger and the newer console for future breakdowns. 

I do think the the Davis system is pretty good. Mine has been working well for 14 years. The rain sensor became faulty a couple of years ago, and I was able to get a replacement at a reasonable cost.  The data logger may have failed or possibly not, but other than that it has been problem free.

I have another question on a differnt, but related matter.  I am missing about six months of data on my PC Weatherlink. I can download this from the web-based Weatherlink as I ahve a PRO account..  I would like to try to convert this to the .wlk format.  Do you know of any useful information about the .wlk format.  I can try to write a Python program to do the conversion - might have to climb some learning curves but always happy to have a go.  I know its a bit like trying to write with a quill pen instead of a keyboard, but I really do much prefer the functionality of the PC system.

And thank you again!

[johnd]

OK 2 parts to this answer. Read part 2 as well before doing anything:

Part 1 The format of the Weatherlink data files is described in the Serial Tech Ref document downloadable from:

https://support.davisinstruments.com/article/rbzgl0rh6k-vantage-pro-pro-2-and-vue-communications-reference-2-6-1-any-os

Downloading data from weatherlink.com is best done using the v2 API described at: https://weatherlink.github.io/v2-api/

Part 2 But digging through all this documentation is quite time-consuming and arduous if you've never done it before (unless you want a winter project!). And you probably don't need to do it. What I would do (assuming you're running the last v6.0.5 version of local Weatherlink):

1. Create a new station in Weatherlink for Windows to hold data temporarily.
2. Use the Web Download option in the Communications Port settings. Enter the Device ID of your upload device (probably easiest to copy this from the relevant field at weatherlink.com) and the password for your wl.com account.
3. Download data into your new temporary station. Browse through the data and see how much there is and if it looks OK. Then copy whichever monthly files you're missing into your main station. Remember that you can only copy complete monthly files so you may have to take a decision about any month that might be split across 2 files. If you don't get enough data in the first download then try again a second time. Sometimes you can get more data the second time.

NB The suggestion is to use a new station for this so that you don't inadvertently mess up your main station record. Don't move data across until you've had a good look at it.

[PaulMy]

I have another question on a differnt, but related matter.  I am missing about six months of data on my PC Weatherlink. I can download this from the web-based Weatherlink as I ahve a PRO account..  I would like to try to convert this to the .wlk format.

Would jruys WLKReaderWriter https://www.wxforum.net/index.php?topic=10144.msg97016#msg97016 be helpful with this?
I know Jerry doesn't directly support this anymore but it is still around.

Enjoy,
Paul

[johnd]

Would jruys WLKReaderWriter https://www.wxforum.net/index.php?topic=10144.msg97016#msg97016 be helpful with this?

If he can get Web Download working then that would undoubtedly be the simplest option. WLKRW would be pretty tedious to create a whole bunch of records I think, but might be useful to merge two monthly fragments for the same month (if that issue were to crop up).

[cjwhome]

johnd

2) sounded like a perfect solution.  However, it doesn't seem to work.  I set up a new Weatherlink account on a different PC and created a new station, set the port configuraiton to TCP/IP, input the device ID and password, went onto File, and selected Download.  It said "there is no new data to download".  Directly trying to download gave the same response. So it seems to accept that there is a station there, but doesn't see any data.

Now I wonder if it is because I am sending data to the web via a Weatherlink LIve rather than from the console/logger - I've read that this doesn't work.  I can't remember why I thought I needed to get a Weather live and use it to send the data, and can't see a way of checking on the web Weatherlink if this is actually the case.

So if I cant download  using (2), it looks as if I might have to go for (1).  A 2025 project I think!! 

Or leave the spaces  empty....

But at least they are filling up again now!!!

Thanks again.


PS. PaulMY  If all else fails, and I still want to fill in my gaps, I will look at that software.  Thanks.

[johnd]

Oh sorry, my mistake, i was thinking you were uploading via Vue/USB. No it won’t work with WLL uploads - that uses v2 API exclusively, not the v1 API. I know you did mention it in the first post but so much talk about Vue/USB that I forgot.

[cjwhome]

I will probably dabble a bit bit if it gets too messy,  I will not bother.

It would be nice to fill the gaps but no real need.

And thanks again for all you help.

 

[johnd]

I will probably dabble a bit bit if it gets too messy,  I will not bother.

It's quite doable as a project and straightforward in principle, plus you can obviously do it in 2 stages (ie get the wl.com download working first and then make the wlk files) but there's a lot of detail to get exactly right. The download will be formatted as JSON and then the relevant fields need to be extracted and converted to binary and packed into the wlk file in the right order/structure - you need to choose exactly the right binary variable types for each data field, as per the tables in the Serial Tech Ref document.

Good luck if you do try it.

[cjwhome]

I will let you know if I complete it.

It is an interesting challenge and at my age, challenging the brain cells can only do good (I hope....)