I lent my VP1 updater to a friend in town . He wanted to update a spare console with the latest Davis daylight time updates. I used it and it worked fine. However, when he went to use it today he got a solid yellow light on the updater which means The fuse bits did not program correctly.
Now neither of us are progammers and kind of wondering if anyone has a clue what that might mean and a solution.
I am wondering if each update has to be uploaded in sequential order rather than having an update with all the previous features or corrections like Windy does .
I went to the Davisnet site and the information there doesn’t tell anything.
It just means that part of the programmable memory in the console didn’t take the update for some reason. It was a VP console, not a VP2 - right? I assume you are able to load the latest firmware into the updater so I guess I would reload the updater and give it another try.
Google “fuse bits” and “atmel” (who make the microprocessor) for more techie info than you could ever use. Before flash and other non-volatile memories came along, there were real fuses that were blown on the chip to store the program.
just got an email from Dana who has the problem and you bring an interesting point. He bought an extra console when the VP1 was going out of style and I am wondering if it is the wrong console…
Interestingly, model numbers on the two consoles differ. The space is
model #6310, the other is 6150. Both are product #6310. Have a feeling
this is related to the problem.
No, those are both VP’s. They get labelled with different numbers if sold separately, or as part of a station. 6310 is a stand alone, and 6150 is a whole VP station.
the update worked on my two consoles, but with Dana’s console and now with his Envoy… didn’t upload to the console correctly. I am not sure what happened. Initially I thought maybe he loaded in something to the updater such as for the vp2 instead. Although… I had already had the update loaded.
Not sure what is happening, but I feel terrible about this… I have never had any problems with the console updates. I just was wondering if anyone else had a similar problem in the past.
Isn’t it a different firmware file for the Envoy?
Is the one where the update failed now dead?
he reloaded the updater for the console and when that didn’t take, loaded the update for the Envoy in the updater and that didn’t take. That is strange
that is what Dana said, killed them both. I guess he is sending them to Davis for a fix.
