I just spoke with Davis tech support and they said the new firmware version IS backwards compatible with existing data loggers.

Note that the new version is 3.12

Did you perhaps ask for details? There are several possible interpretations of "compatible". For instance:

A. Version 3.12 firmware no longer checks for the logger version, so it works with anything.B. 3.12 Installer checks for logger version, and installs "non-checking" firmware for old Davis logger, but not for 3rd party loggers.C. 3.12 Installer checks for "new logger" and installs "non-checking" firmware if it's not a new logger.D. 3.12 Installer will install through an old logger on an old console, but then firmware will not work (or will work) without new logger.E. Various alternatives if the console already has 3.0 firmware, but it's an old logger (perhaps this is impossible).F. I can think of other permutations.....

Clearly, without some statement from Davis, we'll be waiting for several tests.

Dale, I specifically asked about the datalogger compatibility issue the Davis rep said and I quote: "it's complicated" he really didn't want to get into specifics, and without elaborating said that old "DAVIS" loggers will work with fine the new firmware version.

So, for whatever it's worth, I went ahead and gave it a shot and upgraded.

I have an "old" 6510 serial logger and can announce that it works fine with the 3.12 firmware.

Upgraded from 1.91.

The only thing anyone will need to do is if currently using a COM port above port 9, you would have to reset the port to 9 or lower in your device manager, otherwise the davis firmware updater will not be able to find the datalogger.

The only reason I went ahead and upgraded was if it did crap out, I was planning on taking my station down to ship it out for the $100 refurb anyway.

Dale, I specifically asked about the datalogger compatibility issue the Davis rep said and I quote: "it's complicated" he really didn't want to get into specifics, and without elaborating said that old "DAVIS" loggers will work with fine the new firmware version.

I'll be darned. Sounds to me like they saw the error in their ways with the "It's complicated" response, did the right thing, and dropped the logger check. Good stuff!!! My guess is the heat put on by the bad press and reverse engineering effort here probably didn't hurt.

I felt the need.... Just completed the upgrade on my VP2 console. No issues in upgrading process or operations of the console. Just re-verified operations of the console and system all appearsOK. I have the newer Davis USB weatherlink installed on the console communicating serially on Comm 3.Seems the forecast requires 3 hours of data to begin predicting again! Cumulus, WU and my FTP site all working fine!

I've been following that thread myself with interest, as I'm considering upgrading to a Davis.

My understanding: Davis apparently introduced the problem (where the console would stop responding for a minute or more) in version 3.0 and have apparently fixed it in version 3.12. The problem apparently affected Cumulus because of the way it speaks to the console, using the Davis VantagePro.dll.

I upgraded both my ip logger console and my serial to usb envoy . I disconnected each when I upgraded the other one so as not to have the upgrade accidently go to the wrong instrument. It went as planned and I have no difficulty.

The only odd thing is for me that the consoles didn't auto reboot and I had to do that manually, wait out the resync, but the update did work fine for me. The real important thing is to be sure to download and double check that you are updating the right item with the right update and then just let it update on its own, no surfing the net while the update goes.

Obvious question: what happens if I'm using an old Davis logger, and install this firmware?

Don't know - won't have a chance to try it until tomorrow.

However: I surmise from the lack of warnings posted that there will be no adverse experiences with older loggers. Just my guess of course.

John, I want you to know that I really appreciate your efforts to communicate with us, and to supply us with the best information that you have. You have been extremely careful to state what you know, and to quote what you have been told, and to identify your thoughts and assumptions.

Occasionally you're going to have incomplete (or slightly misleading) information from Davis. And you (or we or both) will perhaps draw slightly incorrect conclusions. That's not our (collective) fault.

The same is true of people who ask questions of Davis support, and report the answers here.

It appears, from experimental evidence reported here, that there is no major functional difference between old and new VP2 consoles, nor between old and new loggers. That is, all consoles will accept firmware version 3.12, and with that firmware version, will work with all loggers (including 3rd party loggers). [Yes, I'm aware that the total set of permutations has not yet been reported, so I'm jumping to a conclusion].

If someone has a VP2 console that is running Firmware Version 3.00; andIf they have an old (non-green-dot) logger or a 3rd party logger......and therefore, the combination is not functional because the console won't communicate with the logger....