Author Topic: Vantage Vue stopped sending archive data 'no new data' (Read 1862 times)

tonyh · « **on:** February 26, 2018, 11:01:53 AM »

Hello,

Since this morning I have had problems with my Vue data. Everthing has been fine data wise for the past 6 years since I installed the weather station then a few days ago I decided to update the console to v 4.18.
I use Cumulus to upload to Wunderground and utilise Weatherlink periodically for archive data and graphs. Noticed this morning it would not upload data stating 'no new data' even though there should have been several hours worth.

I have been looking into this all day to no avail as I cannot find a similar issue. I have tried clearing the archive, creating a new weather station in WL and powering off the console to no avail. I then connected the console to my other laptop which gave the same result. I remembered I had an old Envoy from ebay and took the data logger from that and tried that in the console still 'no new data'. I then put the original data logger in the envoy which did transfer data so all this suggests to me that the problem is with the console since its update.

Any ideas appreciated, thank you.

Bushman · « **Reply #1 on:** February 26, 2018, 12:04:33 PM »

Search for "Green dot logger".

tonyh · « **Reply #2 on:** February 26, 2018, 12:45:52 PM »

Did that non the wiser.
What would that mean with respect to my issue? The console still works and provides real time to WL and cumulus but I can no longer download archive data. Sorry if I seem technologically impaired

johnd · « **Reply #3 on:** February 26, 2018, 01:01:43 PM »

Quote from: Bushman on February 26, 2018, 12:04:33 PM

Search for "Green dot logger".

Should immediately give an 'Incompatible logger' message, so unlikely. Check through all of:

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

tonyh · « **Reply #4 on:** February 26, 2018, 01:04:33 PM »

Managing to make some sense of this conundrum , does this mean my updating the console has rendered the logger obsolete (in so much as it will no longer archive my data)? Is it possible to roll back the firmware if thats the case or any other solutions? I certainly am not shelling out £150 plus for a new logger and shall just have to keep the laptop on 24/7 and obtain my data and graphs from Cumulus/ Wunderground! Thanks.

tonyh · « **Reply #5 on:** February 26, 2018, 01:05:25 PM »

Thanks John yes thats what I went through.

dalecoy · « **Reply #6 on:** February 26, 2018, 01:27:59 PM »

Did you try:
Remove all power from the console (battery and AC)
Remove the logger. Wait a few seconds. Re-insert the original logger.
Restore all power to the console.
(Make sure the date/time on the console and on the computer are identical).

Note: removing the power is essential to prevent possible difficulty.

dalecoy · « **Reply #7 on:** February 26, 2018, 01:48:36 PM »

Quote from: tonyh on February 26, 2018, 01:04:33 PM

I certainly am not shelling out £150 plus for a new logger and shall just have to keep the laptop on 24/7 and obtain my data and graphs from Cumulus/ Wunderground! Thanks.

Does this imply that you have the IP logger? You haven't provided that information.

tonyh · « **Reply #8 on:** February 26, 2018, 01:51:17 PM »

Oh no Dale I I have a serial DL.

dalecoy · « **Reply #9 on:** February 26, 2018, 01:54:51 PM »

Quote from: tonyh on February 26, 2018, 01:51:17 PM

Oh no Dale I I have a serial DL.

...and you don't leave the PC on all the time?

Model number of the console?

Firmware version before the upgrade?

tonyh · « **Reply #10 on:** February 26, 2018, 02:10:40 PM »

No I usually put it off overnight to rest the aging laptop.
I think the firmware was 3.0.
Model no 6250UK
Product no 6351UK.

Many thanks

johnd · « **Reply #11 on:** February 26, 2018, 03:35:07 PM »

Quote from: tonyh on February 26, 2018, 01:05:25 PM

Thanks John yes thats what I went through.

Are you _sure_ that you've checked all the points there - there's quite a few? If you definitely have then the logger is probably faulty. But I suspect that's very unlikely. You haven't said how many beeps you hear on reboot?

tonyh · « **Reply #12 on:** February 26, 2018, 04:04:51 PM »

Yes did them all. Cant be the logger as it worked in the envoy surely?
Beeps twice on reboot.

johnd · « **Reply #13 on:** February 26, 2018, 04:21:23 PM »

Quote from: tonyh on February 26, 2018, 04:04:51 PM

Beeps twice on reboot.

What, in the Vue console? Then that's an immediate problem flag - should be 4 beeps. How many with the logger out?

What's the Mfg Code?

tonyh · « **Reply #14 on:** February 26, 2018, 04:53:37 PM »

3 beeps both with and without logger (one shorter quiet beep followed by two louder longer ones).

I guess this is the logger MFG code: C120326B073
There is also this which is preumably to do with the model: 6510SER DH.

Thanks.

johnd · « **Reply #15 on:** February 26, 2018, 04:59:12 PM »

OK, the console is not seeing the logger correctly.

Sorry, I was asking about the console Mfg Code, though the logger one is useful also.

Mattk · « **Reply #16 on:** February 26, 2018, 05:03:16 PM »

FW 4.18? What is the Mfg code of the console? Must be MB... or higher

tonyh · « **Reply #17 on:** February 26, 2018, 05:06:15 PM »

Console MFg code G120719D051, yes firmware update 4.18 had no idea it may be harmful!

dalecoy · « **Reply #18 on:** February 26, 2018, 07:39:31 PM »

Quote from: tonyh on February 26, 2018, 04:53:37 PM

3 beeps both with and without logger (one shorter quiet beep followed by two louder longer ones).

... but no message on the console display about 'Incompatible logger' ?

johnd · « **Reply #19 on:** February 27, 2018, 03:14:12 AM »

Quote from: tonyh on February 26, 2018, 05:06:15 PM

Console MFg code G120719D051, yes firmware update 4.18 had no idea it may be harmful!

Not this one, immediately underneath the download link (albeit with a typo in the warning)?

'NOTE: This firmware is only for with a Mfg Code of MB or higher (e.g. MB, MC, etc.) (#6351, 6351M).'

I don't think this is a green dot logger issue, probably more one of firmware incompatibility with the console hardware; but difficult to know for sure since the symptoms of the wrong F/W aren't spelled out in detail anywhere that I know of.

Worth trying a downgrade to the 3.0 F/W to see if that solves the problem, assuming that the older F/W can be reinstalled OK - hopefully there'll be no problem.

tonyh · « **Reply #20 on:** February 27, 2018, 03:21:33 AM »

But mine is product #6351 thats why I thought it the correct update, very misleading and unclear from Davis. Hopefully they will be able to help me, I have contacted Davis support. Its not on if an update renders an expensive piece of equipment virtually useless. Thanks.

tonyh · « **Reply #21 on:** February 27, 2018, 03:23:09 AM »

Have not been able to locate the 3.0 for a roll back, anyone know if that is a possibility? Thanks.

tonyh · « **Reply #22 on:** February 27, 2018, 03:36:33 AM »

No Dale did not have that message it says 'thanks for choosing Davis..'

johnd · « **Reply #23 on:** February 27, 2018, 03:37:27 AM »

Quote from: tonyh on February 27, 2018, 03:21:33 AM

But mine is product #6351 thats why I thought it the correct update, very misleading and unclear from Davis.

How could they make it much clearer? Isn't the warning in my post above enough?

Quote

Its not on if an update renders an expensive piece of equipment virtually useless.

It does happen with many upgradeable electronic devices if you choose to apply the wrong update.

Re v3: I don't know where you're looking for information, but isn't this page from Davis support clear enough?

[ You are not allowed to view attachments ]

NB We don't know that reversion to v3 will fix the problem - it could be something else. But right now it looks like the next best thing to try.

tonyh · « **Reply #24 on:** February 27, 2018, 03:40:38 AM »

Ok John I must be just dumbass not to understand it if it was so clear, apologies!

News:

Author Topic: Vantage Vue stopped sending archive data 'no new data' (Read 1862 times)