Classic has been hung!?

[Resthome]

The issue as I am able to recreate it:
A- Classic has older code (Maybe 10-4-13 or older)
B- Update MNGP
C- Update Classic

This seems to work every time. If I do the Classic first and then the MNGP all seems well. More to come

Ryan

Thanks Ryan

Okay if I understand correctly I have the 1609/1608 from 10/4/13 so as long as I update the Classic first and then the MNGP and then do the VMM I should be good. Or do I need to do a firmware update that is in between?

I know you are currently working the issue, just need to get an update before I leave for the lake tomorrow morning around 7AM PST.

Thanks Damani - hopefully one last brick for MN to fix

[dapdan]

Midnite,

You guys are geniuses. The fw 1769 loaded and the classic has recommenced normal operation. I will now try to load on the lasted forward 1775.

Cheers...
Damani

[dapdan]

Lol Resthome.

Cheers...
Damani

[dapdan]

Midnite, Ryan,

It has all been resolved...the classic is back in business. This is just another testament to the great and excellent customer service from Ryan and the midnite crew. If only I could un-brick the Kid in a similar fashion. I have placed the LEDs on blinky mode in celebration of this occasion.

Oh yeah, I was successful in updating to fw1774. This was the cause of the celebration.

Cheers...
Damani

[Resthome]

Oh yeah, I was successful in updating to fw1774. This was the cause of the celebration.

Cheers...
Damani

Was the final firmware 1774 or 1775 ?

Also where did you download the 1769 firmware from? Like to take it with me just as a precaution. Ah see it in Ryan's post above.

Thanks to all the great folks at Midnite for working on a solution.

[dapdan]

Resthome,

The link says 1775, but the controller says 1774

Cheers...
Damani

[Halfcrazy]

Yeah sorry about all the hassle. We pushed harder than we should to get the WBjr stuff implemented and did not Beta test as much as I would have liked.

[Resthome]

Resthome,

The link says 1775, but the controller says 1774

Cheers...
Damani

Yeah from the readme notes it looks like the Classic is 1774 and the MNGP is 1775.

Thanks again, think I got it all now. Do 1769 first then the 1775

[TomW]

Maybe they need to use the term "beta" for updates until a few field installs are accomplished?

That way folks will understand things may not go completely smoothly.

Just off the top of my head.

Tom

[Resthome]

Yeah sorry about all the hassle. We pushed harder than we should to get the WBjr stuff implemented and did not Beta test as much as I would have liked.

Ryan,

To be honest I think I might have had this issue with the 1609/1608 beta but worked around it some how and never wrote it down or reported it. Seem to remember something strange about the classic update closing the DOS window which I usually just wait for the Successfully updated message and the window stays open. Wasn't watching it as close as I usually do so don't know if the Successfully updated message was there or not. When I came back the DOS box was closed. I then did the MNGP and got the Successfully update message. On the VMM I seem to remember it hanging when it doing the writes

But once Damani mentioned it started coming back to me. However, in my case I was able to get out of it some how so never though about it any more. I checked the version numbers in the status windows and because they were correct didn't think anything more about it.

Anyway, great detective work.  Might want to post a warning on the firmware download page once you have finished the investigation.

[zoneblue]

I have actually timed the behavior of the dos box: here on XP it goes as follows:

-"100%" , wait 1 minute
- "classic updated sucessfully", wait 2 minutes
- dos window closes.

Would be nice if this could be tweaked to report and behave more intuitively, but ive always waited and never had any trouble after at least a dozen updates. However sounds like the OP issue relates to a temporary mismatch between MNGP code and classic code.

Interesting. +1 for longer beta phase.

[Resthome]

I have actually timed the behavior of the dos box: here on XP it goes as follows:

-"100%" , wait 1 minute
- "classic updated successfully", wait 2 minutes
- dos window closes.

Would be nice if this could be tweaked to report and behave more intuitively, but ive always waited and never had any trouble after at least a dozen updates. However sounds like the OP issue relates to a temporary mismatch between MNGP code and classic code.

Interesting. +1 for longer beta phase.

Zoneblue,  I'll check that out this time. Just may have not waited long enough after the Classic successfully updated message.  Almost 1 1/2 years of update and never had an install issue until the 1609/1608 and I was in a rush to get it done before the winter as we usually close up until spring. Looks like my previous firmware was 1401 before updating to 1609/1608.

+1 for longer beta phase also.

[boB]

Resthome,

The link says 1775, but the controller says 1774

Cheers...
Damani

That number will show the highest number of either MNGP or Classic.  Sometimes the MNGP is the highest
build number and sometimes the Classic has the highest build number.

Sometimes the date is the best number to use when referring to a particular download revision.
They are both in there as well as the actual .exe file which will be something like  4.21 or 4.24  etc...

boB

[zoneblue]

Looks like theyve issued a fix for the above issue. I guess the mngp was trying to set Wb registers that didnt currently exist if the MNGP was updated first. Current prod is 1779, readme:

Code Select Expand


2-17-2014
Build 1774  Does NOT change date to 2003 every boot unless the year is less than 2014
MNGP  1775  VMM QuickSet defaults Aux2 to Whizbang Junior (WB Jr.) mode
2-20-2014
Classic build 1779 should keep users from having to downgrade to 1769 and then
back to 1774 (sometimes the Classic would stop functioning after that update)


Just a suggestion on the rev numbering. Maybe it would be better to use a single tag revision for both both classic and mngp, either load both sets of code into the same CVS or just go with the greater of the two.  Even though they are two independent sets of code for twoseperate uPs, they in effect work as one. Might save some confusion. Unless there is actually some good  reasons to run specific arbitrary versions in MNGP and controller at times?

[Resthome]

Looks like theyve issued a fix for the above issue. I guess the mngp was trying to set Wb registers that didnt currently exist if the MNGP was updated first. Current prod is 1779, readme:

Code Select Expand


2-17-2014
Build 1774  Does NOT change date to 2003 every boot unless the year is less than 2014
MNGP  1775  VMM QuickSet defaults Aux2 to Whizbang Junior (WB Jr.) mode
2-20-2014
Classic build 1779 should keep users from having to downgrade to 1769 and then
back to 1774 (sometimes the Classic would stop functioning after that update)


Thanks for the Heads Up !  Put it on my LT tonight.