I updated firmware on the Classic 150 today. When it was done updating I did a factory restore. I selected solar then 48V then voltage charge setting then time and hit enter. From there it says sending data and there is a red light to the left of the display. It freezes in this condition so I can't use the controller. Any idea what I can do? I tried several times to reinstall both the mngp and the Classic firmware with the same results. Firmware udated with windows 8.1.
Hi WX..,
Have you successfully updated the Classic FW in the past, using that same computer?
At about reply #7 in this Thread there is some discussion of FW installation failures, FWIW:
http://midnitesolar.com/Forum/index.php?topic=2269.0
Good Luck, Vic
On my first and second attempt today it was on a new computer. Then I went back to the older computer that has completed a firmware update successfully many times. I'm now on my 3rd or 4th attempt with that computer with the same failed results each time. Each time I deleted the firmware before downloading it again.
OK, thanks for the info WX,
Have never used any other Windoze operating system other than Win7 HPE.
Have you tried the Jumper Hardware Reset yet? It was mentioned in the Thread that was linked above.
I had a very similar situation to what you are experiencing, and it seemed that I needed to do the Jumper Reset, and a reload (in my case, reverted to the previous Production FW Rev).
Also, just make certain that when the MNGP FW is being updated, that it is plugged into its correct connector on the Classic .. this sounds very basic, but have heard of someone setting aside the Classic's face with MNGP attached to the face with NO CONNECTION to the MNGP while trying to update it ... This works very poorly!
All, FWIW ... Good Luck! Vic
I tried Windows 7 and 8 with no luck.
I wasn't aware that the hardware reset was for the regular Classic also, I thought it was only for the Lite but I guess not. There is a process on how to do it on the website and it talks about jumper #'s but is there a diagram that shows which jumper is which?
How do you revert back to the old firware? I would love to do that and didn't even want to install the new firmware but Midnite suggested it as a possible fix to my over voltage charging situation.
Quote from: Wxboy on May 16, 2015, 04:41:39 PM
I tried Windows 7 and 8 with no luck.
I wasn't aware that the hardware reset was for the regular Classic also, I thought it was only for the Lite but I guess not. There is a process on how to do it on the website and it talks about jumper #'s but is there a diagram that shows which jumper is which?
How do you revert back to the old firware? I would love to do that and didn't even want to install the new firmware but Midnite suggested it as a possible fix to my over voltage charging situation.
Hi again WX,
Please read the Thread on this Forum, that was linked in my first reply;
The Jumper reset narrative that you mentioned tells exactly how the Jumpers are numbered, and exactly how to sequence the power and install the jumpers. Please follow this exactly.
Also in that Thread, is a reference to the 'fusion" site that has historic Classic FW.
And, had commented on your "overvoltage" issue with your AGMs (IIRC this is what you are referring to) previously. This seems a not-uncommon feature of AGMs. It has been widely reported on the OB Forum, over a number of years, from those using OB MX and FM CCs with AGM batteries.
One of the OB Engineers mentioned that he was convinced that this was, basically, a Surface Charge effect of AGM batteries, and in his opinion, if was not detrimental ... I know nothing of this effect from direct experience, as have not used AGMs, ever.
Back to work, Good Luck, Vic
Thanks for the direction Vic. From your experience if I want to go back to the old firmware do I still need to do the hardware restore?
One more thing...on the over voltage situation, the Classic is ouputting current when the batteries go over voltage even though the charger shows no output. This was confirmed with a clamp meter. I made a video and sent it to Midnite.
There is nothing special to go back a version. Just de-installed the current version and reinstall the previous version on your computer and then do the updates.
How many versions were you behind? That has caused issues in the passed and also the sequence in which you install. I believe IIRC that the MNGP should be updated first, but check the sequence in the instructions.
I was only one version behind.
My Classic only has jumpers on JP2 and JP3 so I guess I won't be doing a hardware reboot.
Installed FW version 1849 and all is well. Not sure why it didn't like the new firmware but I'm not doing that again any time soon. What a nightmare.
Thanks for the help Vic.
Hi Wxboy,
Glad that you are back up and running. I have not yet tried to reload the latest FW. May try it again soon.
I still have no idea of just what was the issue with my update failure. It is frustrating to take a working system, and turn it into a broken one -- kind of a panicky feeling.
On your Over volt issue ... had forgotten that the batteries were drawing some charge current. Wonder how much that current happens to be, on average.
And John, I could not find any recommendation on the required order of FW updates to the Classic and MNGP ... have always Updated the Classic first, and then the MNGP, and that has always worked, except for this last time (before reversion to 1849).
OK, thanks, Vic
Vic
I had always used that sequence for the updates also Classic then the MNGP. But when I switch to a laptop with Win 8.1 I believe the instructions said to do the MNGP first and then the Classic.
Okay the Win 7 instructions tell you to do the Classic then the MNGP.
The Win 8 instructions are opposite and tell you to do the MNGP first then the Classic.
"Step27
Find the Midnite updater icon on the desktop and double click it. This should open up the Midnite
Updater. Now you need to select the MNGP first if this is a standard classic"
OK, Ryan is there a preferred order for the updates? Seems to me since Lites don't have MNGP that doing the Classic first would be correct but that is not what the win 8 instruction say.
There was an issue a while back about the update hanging when you where behind a few versions. I'll try to find the thread.
Here is the thread. This had to do with additional modbuss registers. Don't think that is the case with the original posters issue.
http://midnitesolar.com/Forum/index.php?topic=1687.msg14986#msg14986 (http://midnitesolar.com/Forum/index.php?topic=1687.msg14986#msg14986)
Quote from: Resthome on May 17, 2015, 01:16:08 AM
Vic
I had always used that sequence for the updates also Classic then the MNGP. But when I switch to a laptop with Win 8.1 I believe the instructions said to do the MNGP first and then the Classic.
Okay the Win 7 instructions tell you to do the Classic then the MNGP.
The Win 8 instructions are opposite and tell you to do the MNGP first then the Classic ...
Hey John, thanks for the info that Win 8.. notes a reverse UD order ... have never looked at the Win 8. instructions, as am trying very hard to AVOID that version.
Appreciate your help. Will try one more time with the latest Production FW Update, perhaps on a different Classic.
Thanks, Vic
no the order should not matter at all. I tend to prefer to do the MNGP first as it is usually the one that gives problems if either one is going to. That way if you get the MNGP the Classic should go no issue.
Of course the MNGP has to be plugged in to update (YES I have been there and done that witht he MNGP on the bench and me swearing why wont this blankedy thing update ::) )
Quote from: Halfcrazy on May 19, 2015, 11:18:04 AM
no the order should not matter at all. I tend to prefer to do the MNGP first as it is usually the one that gives problems if either one is going to. That way if you get the MNGP the Classic should go no issue.
Of course the MNGP has to be plugged in to update (YES I have been there and done that witht he MNGP on the bench and me swearing why wont this blankedy thing update ::) )
Thanks for the clarification on this. I suspected that was the case but good to know.