Classic has been hung!?

[cybermaus]

With all these beta builds flying about, admittingly most seem to be about other stuff, could someone please reevaluate an opinion/advice on this question please?

[Resthome]

With all these beta builds flying about, admittingly most seem to be about other stuff, could someone please reevaluate an opinion/advice on this question please?

Stick with the Production release of the firmware, but you do need to keep the Classics up to date. It's important for bug fixes as well as new features. Oh and read the Readme file with the firmware download to see what changes or fixes were made. Betas are not normally a problem and it you live next to your Classic pretty safe as you can always roll it back. If your Classic is remote and you are not there all the time I would stick to the Production firmware.  Just my $.02

Midnite is great at responding here or by contacting them if you have any issues. So don't hesitate to ask questions here. Lots of knowledgeable folks here.

[toothy]

What fun now one of mine is doing this and making a noise like a baby rat in the jaws of a constrictor!

[cybermaus]

Like mentioned and like solved in this thread?
http://midniteforum.com/index.php?topic=1668.0

[toothy]

I've tried all the stuff mentioned in this thread and it still won't work.

Reverted to 1769
defeated vmm right 2 buttons found 255

Still nothing
After pushing charging source it see's 12V on a 48V system.

A few more pushes and it goes to sending data/4136   502    255 below and just stays there.

It's putting out some watts according to the local App and shows the firmware as 1769 that I reverted to. Also only 1 of the 3 Classics show BTS.

I thought maybe a jumper VMM but can't find the exact procedure.

Thanks
Wade

[boB]

I've tried all the stuff mentioned in this thread and it still won't work.

Reverted to 1769
defeated vmm right 2 buttons found 255

Still nothing
After pushing charging source it see's 12V on a 48V system.

Wade, when the Classic reboots after unpowering and re-powering it, do the LEDs inside the Classic behind the air vent flash back and forth as well as the fans revving up for a moment ?  That would mean that it actually booted up.

If the VMM hangs, that could just be because the 1769  2-13-2014 version does not have as many modbus registers as the 2-17-2014 date software.

If the Local App really shows that it is producing some power, or its battery voltage and other numbers look correct, then it is probably actually running and the reverting back to older code has does its job.

If it has done its job and the Classic itself is actually "running" and clicking and being happy (not hung), maybe the MNGP just needs to be reverted or updated ?

You could also try reverting to an even earlier Classic software revision but so far, all of the few customers that have had this problem have been resolved by going back to 1769  and then they were able to go up to 1775 or whatever the latest was.   I think I have a newer fix that will take care of this but I don't want to let it out until I verify it is not going
to hang anymore.

Sorry.

boB

boB

[toothy]

Hello boB

Led’s and fans are as normal.

MNGP is firmware 1775 from 02/17/2014

I went back to 1779, same stuff. It is charging and the local App is correct, but when I plug in the MNGP it won’t VMM or show correct battery voltage.

I got here because after I updated last monday or so to 1772, I think, my bts wasn’t working in follow me and my WBJR was incorrectly showing 1100 +/- Ah at 100% in float when the local App had 1350 AH, the correct amount, in the correct spot.

This Is the Classic lite to which the WBJR is connected.

I would say it was beer thirty, but after this stuff I may have to go talk to the Wild Turkey!

Thanks
Wade

[Resthome]

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.

Verified Zoneblue's observation on the closing of the DOS window. It takes another 2+ minutes after you get the "Classic successfully updated" message for the box to close. Not sure if there are any other cleanup work taking place or not. The Win 7 firmware instructions tell you this firmware update process should take between 5-15 minutes and the box will go away when it is complete,  but doesn't tell you how long to wait. The readme file just says:

  UPDATE NOTE:    When updating the Classic, PLEASE WAIT until
   you see both of these messages....

   "Transferring... 100% done."

   (followed about 1 minute later by this message...)

      "Classic successfully updated"

So should we always wait for the DOS (Black Box) to close? If so it would be good to update the instructions with some estimated time. 

[Resthome]

Looks like they've issued a fix for the above issue. I guess the mngp was trying to set Wb registers that didn't 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)


I can verify that a firmware update from 1609/1608 directly to the 1779 (2-20-2014) firmware went without any hangs. Great job Midnite on resolving this so quickly.    I had a short window of opportunity to get the Classic updated this past weekend. Still have some questions in regards to % SOC and Net Amp Hours but will start another thread for that.