Classic has been hung!?

[dapdan]

Midnite,

Why didn't I leave well enough alone? Anyways I decided to update my classic 150, last update was Aug 2013. So I uninstalled the last set of files and delete what was left. DL the new files. Updated MNGP and classic, everything was going well. I performed the vulcan mind blend and was going through setup then it is hung up on " sending data/ 4136  502". I have done the vmm at least twice and still the same message.

How do I resolve this people. I am now wary of trying to upgrade the two other classics lites.

Cheers...
Damani

[Halfcrazy]

Here is Mikes steps for getting out of a "Stuck in VMM" condition

1. So, First up is that it is stuck in what we call the Vulcan Mind Meld, basically the setup screen. Luckily we made a way around that screen for when this happens. So powerup the classic and when the Midnite logo appears press and hold the upper right key and the main menu key on the keypad. Must be done when the logo appears and not before. Now it should say VMM Defeated and take you to the status screen.


2. Most likely there will be all 0s for the numbers and it will say got comm in the lower right. If after a few seconds it does display the Battery and Input voltage got step 3. If not then
HOLD the LEFT arrow key and then tap the DOWN arrow key, in the top center the screen should say 9, repeat until it goes down to 255. If you pass it simply press the UP arrow key. Now leaving it at the 255 address the status information should should show up after about 5-20 seconds. Now it will communicate normally.

3. So turn the classic off and back on and press and HOLD the LEFT and RIGHT arrow keys until it says SOLAR, WIND, HYDRO. You are now back in the Setup screen. Note that you must go through this setup or the classic will not be setup for the proper battery voltage.

[dapdan]

Roger that Ryan. Will do post haste.

Cheers...
Damani

[dapdan]

Ok Ryan,

I got as far as all zeros on status screen and then had to select the unused address 255 and it stays there. It does not go back to status screen and resume communication. I performed a vmm and it just get hung up again at the sending data screen. Repeated at least trice and same result.

Cheers...
Damani

[Halfcrazy]

Hm. Let me ask Mat what the next step is. I think I will go re update all 4 of mine to test.

[dapdan]

Thanks Ryan.

Cheers...
Damani

[Halfcrazy]

Do you remember if you updated the MNGP first? Or the Classic code first? I have successfully created your issue here and am now trying to find a solution

Also can you tell me if the fans still rev up on power up or are they dead too?

[dapdan]

Ryan,

I tried the classic first, but I am not sure if the mngp or the classic was accepted first because I did it a few times thinking I was doing t wrong (since I did not do it on a while). I can tell you though that the status screen only shows that the mngp has been updated to the latest while the line by the classic is blank. So it seems as though the update didn't "take" with the classic.

Cheers...
Damani

[dapdan]

Oh yeah,

Thenfans don't rev up when booting up the classic.

Cheers...
Damani

[Halfcrazy]

Damani
That unit is bricked you will need to email Mat for a resolution. mat@midnitesolar.com

Ryan

[Resthome]

Ryan..

I plan on doing an update this weekend. Since you were able to duplicate this, I don't want to brick my controller. Is there a way to avoid this issue. I normally update the Classic first and then the MNGP. Is this the proper sequence or does it matter? In other words how do I proceed without encountering this issue?

[Halfcrazy]

Damani
Can you try this. Can you install this code in just the classic and see if it works: http://fusion.midnitesolar.com/MidNiteSolarUpdate_1769_2-13-2014_v4.22.exe

If it does then try going back to this code on just the classic: http://fusion.midnitesolar.com/MidNiteSolarUpdate_1775_2-17-2014_v4.24.exe

[Halfcrazy]

Ryan..

I plan on doing an update this weekend. Since you were able to duplicate this, I don't want to brick my controller. Is there a way to avoid this issue. I normally update the Classic first and then the MNGP. Is this the proper sequence or does it matter? In other words how do I proceed without encountering this issue?

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

[dapdan]

Oh man,

I have been bricking controllers all week...first the kid now the classic 😊😊😢 😕.

Cheers...
Damani

[dapdan]

Well at least there should be less bricked classic as a result of this issue. I don't like being the guinea pig though.

Cheers...
Damani