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
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.
Roger that Ryan. Will do post haste.
Cheers...
Damani
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
Hm. Let me ask Mat what the next step is. I think I will go re update all 4 of mine to test.
Thanks Ryan.
Cheers...
Damani
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?
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
Oh yeah,
Thenfans don't rev up when booting up the classic.
Cheers...
Damani
Damani
That unit is bricked you will need to email Mat for a resolution. mat@midnitesolar.com
Ryan
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?
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 (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 (http://fusion.midnitesolar.com/MidNiteSolarUpdate_1775_2-17-2014_v4.24.exe)
Quote from: Resthome on February 20, 2014, 12:52:10 PM
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
Oh man,
I have been bricking controllers all week...first the kid now the classic 😊😊😢 😕.
Cheers...
Damani
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
Quote from: Halfcrazy on February 20, 2014, 01:10:16 PM
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
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
Lol Resthome.
Cheers...
Damani
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
Quote from: dapdan on February 20, 2014, 02:09:27 PM
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.
Resthome,
The link says 1775, but the controller says 1774
Cheers...
Damani
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.
Quote from: dapdan on February 20, 2014, 02:45:13 PM
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
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
Quote from: Halfcrazy on February 20, 2014, 02:56:34 PM
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.
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.
Quote from: zoneblue on February 20, 2014, 03:26:04 PM
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.
Quote from: dapdan on February 20, 2014, 02:45:13 PM
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
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:
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?
Quote from: zoneblue on February 20, 2014, 09:37:57 PM
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:
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.
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 (http://midniteforum.com/index.php?topic=1680.msg14945#msg14945) please?
Quote from: cybermaus on February 21, 2014, 01:22:02 AM
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 (http://midniteforum.com/index.php?topic=1680.msg14945#msg14945) 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.
What fun now one of mine is doing this and making a noise like a baby rat in the jaws of a constrictor!
Like mentioned and like solved in this thread?
http://midniteforum.com/index.php?topic=1668.0
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
Quote from: toothy on February 22, 2014, 06:34:56 PM
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
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
Quote from: zoneblue on February 20, 2014, 03:26:04 PM
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.
Quote from: zoneblue on February 20, 2014, 09:37:57 PM
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:
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.