Topic: VP2 - Corrupted Firmware

[Jvietri]

Hello,

Today I tried to update my firmware to the latest version and once the process started it got to updating page 8 of 504 and then i got a communication error.  I tired it again, it went a little higher (like page 14) but same thing. 

Now my console seems to be bricked.  I unplugged it for over an hour.  I plugged it back in and all i get is a single beep and a totally blank screen.  I can still see the weather station on my network (can even ping it) but it does not appear to be working.  Not sure what to do here so any advice or trouble shooting tips would be greatly appreciated by anyone here.  I am afraid i need to buy a new console.. 

[johnd]

1. Make absolutely sure that you're using the correct F/W version for your console;
2. Check that your console is not too old for the update you're attempting to use;
3. Power the console down completely (ie no batteries either) & ensure that the logger is _fully_ home on its pins & not loose at all. Repower and check that you hear the correct number of beeps.
4. Keep trying the update;

[miraculon]

In addition to johnd's suggestions, if this is a WLIP and you can still access the GUI interface, I would also try disabling uploads to weatherlink.com.
I would think that this would be disabled during a firmware update, but it might be good to eliminate the possibility. If you get it all working again, remember to re-enable the uploads.

Greg H.

[Jvietri]

Thanks for the suggestions, tried them all, nothing works.  Just getting one beep when I plug it in and a blank screen.  Still see it on my network but no weather data.  I should have just stuck with my current firmware.  Kicking myself...

[miraculon]

Try contacting Davis. Maybe they have a suggestion.

When I was still working, our microcontroller-based products had a boot loader that was in a protected area of memory. Maybe there is some way to force the console into a boot-loader mode that will allow the reflash. Or, maybe Davis can do it at their facility.

Greg H.

[johnd]

Thanks for the suggestions, tried them all, nothing works.  Just getting one beep when I plug it in and a blank screen. 

You're not providing enough information for us to know what's going on. What sort of console is it, what sort of logger? Guessing it's an IP logger if you're talking about network? Definitely running on AC mains adapter?

How many beeps with and without logger (with network disconnected)?

Probably needs reflashing with an updater. But TBH sounds like there's something more going on here.

[Jvietri]

Sorry,

Here is some more information.  It is a VP2 manufactured in 2008 so it is updatable from what I read.  The data logger is WeatherLink IP.  It beeps only once with the data logger plugged in.  It beeps only once also without the data logger. 

And running on AC only. 

What is the process of refalishing with the updater?

[AWL]

Have a wired VP2 that has been sitting on the shelf for a couple of years now with a blank screen still all hooked up. Use a wireless for my stuff now. Anyway was looking at it today and got to wondering what was wrong. Pulled the batteries and AC and still nothing but a blank screen. Just got one beep when I powered back up. Was just going to give up when I pressed and held the "Done" button and all came up working just fine. May not fix your problem but you might try this if you haven't already. Sometimes it's the simple things.

Doug

[Jvietri]

Thanks Doug,

I sure wish it would have worked.   No dice.. 

[johnd]

Here is some more information.  It is a VP2 manufactured in 2008 so it is updatable from what I read.  The data logger is WeatherLink IP.  It beeps only once with the data logger plugged in.  It beeps only once also without the data logger. 

And running on AC only. 

OK, I assume that when you say 'It is a VP2' then you mean a standard VP2 display console and not an Envoy? Then one beep without logger means that the console is not initialising correctly. Guess that could be the previous F/W update gone wrong or a fault that's developed coincidentally with the main console PCBA.

Assuming that's confirmed then difficult to see how you can avoid a return to Davis, either to replace the PCBA or to force an update via the updater. Updaters are no longer being sold by Davis and were quite costly anyway. It's not difficult to run an update with the updater but you do need to find one somewhere.

[Phil23]

More info needs to be available on firmware upgrades and recovery.

For 1 what mode does it boot to if firmware fails? Is there a TFTP mode, either by default or with a boot sequence.

But even if there is a TFTP mode, then where do you get the binary firmware image.

Having that single exe to update with annoys me, would rather see an updater app accompanied by a separate binary file with an alternate publicly published way of getting it there.

[JudinNorman]

You're wacked in head.
The firmware works fine for us consumers and we don't need the crazies like you spewing nonsense.
Move on if you don't like Davis

More info needs to be available on firmware upgrades and recovery.

For 1 what mode does it boot to if firmware fails? Is there a TFTP mode, either by default or with a boot sequence.

But even if there is a TFTP mode, then where do you get the binary firmware image.

Having that single exe to update with annoys me, would rather see an updater app accompanied by a separate binary file with an alternate publicly published way of getting it there.

[johnd]

More info needs to be available on firmware upgrades and recovery.

TBH I can't see anything changing on the firmware front at this stage - it is what it is.

The reality is that very few users seem to have problems doing an update - the process typically works as advertised. If a problem does occur then  it's usually because the wrong update file has been chosen or instructions & caveats (eg console too old) otherwise not followed. But this can generally be fixed by retrying - 2 or 3 times if necessary - the update with the correct firmware. True, very occasionally more serious issues like console lock-ups may occur but it is genuinely rare and may be a sign of a pre-existing problem with the console/logger anyway.

[saratogaWX]

You're wacked in head.
The firmware works fine for us consumers and we don't need the crazies like you spewing nonsense.
Move on if you don't like Davis

More info needs to be available on firmware upgrades and recovery.

For 1 what mode does it boot to if firmware fails? Is there a TFTP mode, either by default or with a boot sequence.

But even if there is a TFTP mode, then where do you get the binary firmware image.

Having that single exe to update with annoys me, would rather see an updater app accompanied by a separate binary file with an alternate publicly published way of getting it there.

JudinNorman, this is an inappropriate and hostile response.  Do not engage in personal attacks that denigrate other posters.  You are free to disagree, but do so civilly without aspersions on their mental state/health.

[Brientim]

Can you please confirm your weather infrastructure I.e do you upload to WeatherLink or do you have only devices or software connecting to your console?

1. I would recommend that you set the WeatherIP to a static IP address.

2. Connect the computer directly to the WeatherLink IP and configure network as appropriate.

3. When you execute the firmware update use the IP address and not device ID.

When you are stating you cannot see the weather, is the displaying data and if not have you reinstated a search to connect again?

[johnd]

1. I would recommend that you set the WeatherIP to a static IP address.

My advice would be strongly NOT to do this. It's rarely necessary or beneficial and can often cause considerable problems at a later date if you change router, location etc.

[Mattk]

1. I would recommend that you set the WeatherIP to a static IP address.

My advice would be strongly NOT to do this. It's rarely necessary or beneficial and can often cause considerable problems at a later date if you change router, location etc.

It was a recommendation, and I would second that and for those that have the ability and knowledge to handle this it really is the best approach. This should always be clarified 

[mcrossley]

1. I would recommend that you set the WeatherIP to a static IP address.

My advice would be strongly NOT to do this. It's rarely necessary or beneficial and can often cause considerable problems at a later date if you change router, location etc.

It was a recommendation, and I would second that and for those that have the ability and knowledge to handle this it really is the best approach. This should always be clarified

Perhaps a better option for those who know how would be to add a DHCP reservation to their router?

[Brientim]

The intent of the static IP address in this scenario is to enable a direct connection between the WeatherLink IP and the computer executing the firmware update and therefore reducing the chances of network disconnections or interruption.

As to whether or not you or other set up static ip or reservations is a personal choice and dependant on your knowledge, skills and confidence.

[Mattk]

1. I would recommend that you set the WeatherIP to a static IP address.

My advice would be strongly NOT to do this. It's rarely necessary or beneficial and can often cause considerable problems at a later date if you change router, location etc.

It was a recommendation, and I would second that and for those that have the ability and knowledge to handle this it really is the best approach. This should always be clarified

Perhaps a better option for those who know how would be to add a DHCP reservation to their router?

That can be a little more confusing and complicated for most.

[Jvietri]

Yes, I have done this, connecting with a static IP address works every time.  It just every time I go to do the update, it starts and gets to anywhere between page 8 and 28 of 504 and then I get a communication error typically.  I have tried it at least 20 time and it is the same result each time.  That said this is all being done via WiFi however and wonder if that is the issue. 

[Mattk]

WiFi ??? arh give me a break, just go back to basics, all this BT and WiFi stuff is starting to become a nightmare

[Brientim]

Yes, I have done this, connecting with a static IP address works every time.  It just every time I go to do the update, it starts and gets to anywhere between page 8 and 28 of 504 and then I get a communication error typically.  I have tried it at least 20 time and it is the same result each time.  That said this is all being done via WiFi however and wonder if that is the issue.

Do you have any other software or devices polling the Console?  I definitely would not be attempting this over Wifi. Keeps us informed on the outcome.

[Jvietri]

No nothing else is polling.  I will try direct connection next. 

[Brientim]

No nothing else is polling.  I will try direct connection next.

Good luck and hopefully success this time.