Updated firmware on classic 150. Successful with confirmation using another display. After multiple attempts, no luck updating MNGP, black screen persists. Any ideas?
Did you try resetting the power to the Classic first ? and if that doesn't work do a VMM ( hold left and right arrows in on MNGP while turning it on) or alternatively you can do the jumper reset as described on the Midnite firmware update page.
Otherwise the Classic update went okay ?
You MNGP was working okay before the update and just went blank after the update ?
Larry WT9M
Yep, classic updated fine. Blank screen after first attempt to update mngp. Still blank. Used w10 updater
Hi Watt,
I have a bit of a strange question for you;
Was the MNGP CONNECTED, correctly, to the Classic while you were trying to Update it? Sometimes, for convenience, we might set aside the face of the Classic, with its MNGP, while Updating the Classic and the MNGP. This does not work so well while trying to Update the MNGP.
Just a wonderment. Good luck, Vic
Yes, connected correctly, even moved the mngp to another clasic to attempt an update. Hence no grip of a cable error.
OK Watt, sorry, but it SO easy to set aside the face of the Classic, and Update away, though I'd ask.
Yesterday, did try to find the previous Thread about this issue on this Forum, but could not.
Later, will look further.
Had this same issue several years ago, and needed to do the Hardware Reset, with the shorting block on the Terminals on the lower right of the Classic, and then needed to Update the MNGP, then re-update the Classic. Thad did the trick.
If you have not tried the Hardware Restore, here are the details from the MN Solar Software for Classics page,
"The way to do the hardware version of the factory restore (VMM)is as follows. There are 4 sets of jumpers directly above the blue terminal block. For the purpose of this we will call the left most jumper JP1 and the right most JP4 (actually labeled "Boot") •Step 1- Turn the PV and Battery power off to the Classic and remove the front cover
•Step 2- Locate the 2 jumpers JP1 and BOOT (JP4). Take the actual jumpers and keep them in your hand
•Step 3- Turn the Battery power on to the classic
•Step 4- within 1 minute place jumper JP4 on its two pins and then place jumper JP1 on its two pins. at this point the 3 leds on the top of the circuit board should flash back and forth for about 60 seconds.
•Step 5- After the flashing stops power down the classic and remove JP1 and JP4 and stow them back on a single pin like they where.
•Step 6- Put the front cover on and power up the Classic Lite. If you have the MNLP set to Custom you will need to go to the local app and reset the battery voltage and setpoints etc."
Good Luck, (Welcome to the Forum, BTW) and please let us know how you are doing. Vic
Yes, did a vmm. No luck. Thanks for your help, vic.
Yes, but there is the VMM for Classics with the MNGP, and one that does a direct Hardware Restore (Reset) on the Classic, using that shorting block on the pins on the lower right of the Classic's control board.
Did you do the VMM on the MNGP, or using that noted procedure, using the shorting block??
Thanks, Vic
Vic, i have been on this site for years as Watt. Could not reset password as the email address associated with watt is no longer availabile. Anyway. I had followed the procedure above to the t. As far as the mngp, i fasten the left top of the cast cover to the right top of the classic during such procedures. The cable was connected during all procedures. As far as mngp separately or alone to do a vmm? No procedure noted. The only thread i can find regarding this is the one havinginstructions updating with a obsolete procedure. All other threads indicate a blank or empty flash. Yes, i followed the procedure for the classic with mngp.
Watt,
1. The way that I read your reference to how you did the VMM, it was only via the MNGP, so am copying the "procedure" in Post #5 above was the Hardware Restore, using the shorting block on the Classic PCB terminals, it follows ...:
"The way to do the hardware version of the factory restore (VMM)is as follows. There are 4 sets of jumpers directly above the blue terminal block. For the purpose of this we will call the left most jumper JP1 and the right most JP4 (actually labeled "Boot") •Step 1- Turn the PV and Battery power off to the Classic and remove the front cover
•Step 2- Locate the 2 jumpers JP1 and BOOT (JP4). Take the actual jumpers and keep them in your hand
•Step 3- Turn the Battery power on to the classic
•Step 4- within 1 minute place jumper JP4 on its two pins and then place jumper JP1 on its two pins. at this point the 3 leds on the top of the circuit board should flash back and forth for about 60 seconds.
•Step 5- After the flashing stops power down the classic and remove JP1 and JP4 and stow them back on a single pin like they where.
•Step 6- Put the front cover on and power up the Classic Lite. If you have the MNLP set to Custom you will need to go to the local app and reset the battery voltage and setpoints etc."
2. Sorry for the "Welcome" ... had thought that there had been a Watt, or watt previously, BUT, noted that there were 3 Posts at the time, so thought that I had recalled the wrong case ... or ... sorry.
3. Have little to add, Good Luck, FWIW, Vic
No worries vic. Just did not want a noob impression. You've helped tremendously to insure i followed procedure. Thank you.
Watt, just re-read the Threads on Update problems.
Am sure that you also saw the recommendation from HC Ryan that only do the VMM or terminal hardware reset AFTER both the MNGP and Classic have been updated.
Also to W A I T until the LEDs at the top of the PCB of the Classic have stopped flashing -- perhaps up to one minute when doing the terminal Hardware reset (this Hardware - terminal reset was THE thing that got my two bricked Classic MNGPs Updatable) ... am sure that you have done that as well. Believe that the MNGP VMM is ineffective if there is not good FW loaded into the MNGP.
Have not used the Win 10 Updater, but believe that waiting for the Updater to automatically close is not required with the Win 10 one.
These things seemed most notable with bricked MNGPs.
Good Luck, Redundant Vic
Vic, i will go through all prodecdures again. Who knows, any error is possible. Thanks
Still no mngp. Followed all procedures again. Nothing. No reply to my ticket i opened regarding this, either.
Please email me ryan@midnitesolar.com and I will see this is taken care of today
Sorry to hear of your blank screen, Watt.
Ryan will get you fixed up.
Weird. I am guessing that the update got as far as erasing the flash memory and
stopped before it was fully updated for some reason.
Typically if it works at all the update will complete and not stop part-way through.
boB
Quote from: boB on July 19, 2016, 12:52:13 PM
Sorry to hear of your blank screen, Watt.
Ryan will get you fixed up.
Weird. I am guessing that the update got as far as erasing the flash memory and
stopped before it was fully updated for some reason.
Typically if it works at all the update will complete and not stop part-way through.
boB
Some where here on the forums there is a thread on the WIN10 updater having this or similar problems when updating the MNGP. If IRMC there was no solution even from the coder that did the WIN10 updater. There was mention of another WIN10 updater being worked on but I have never seen it. I've updated the Classic with the Win10 updater but have never tried the MNGP because it was already at the correct firmware version. Note some people reported no problems with the WIN10 updater but a few did with a blank MNGP.
Believe there was a comment to make sure you had the MS Visual C++ 2015 redistributable installed on the PC. So you might check to see if that is installed and then give it a try.
Okay found one of the links about this blank screen on MNGP using Win10.
http://kb1uas.com/mnsforum/index.php?topic=2663.msg27731#msg27731 (http://kb1uas.com/mnsforum/index.php?topic=2663.msg27731#msg27731)
RestHome, thank you kindly. I will give it heck when I get in later tonight. Have a great day.
Ryan, I apologize, It's been very busy and I have only had a chance to check in, just now. I will email you tomorrow after this suggestion. Thank you.
Resthome, would you suggest, after the C++ redistribute install, I re-update the Classic as well as the MNGP? restart Then, VMM?
Quote from: Watt on July 19, 2016, 10:21:44 PM
Resthome, would you suggest, after the C++ redistribute install, I re-update the Classic as well as the MNGP? restart Then, VMM?
It wouldn't hurt to do them in that order. Make sure the VMM is done after you finish both the Classic and MNGP update and not in between them. And once you see the successful message wait before doing the MNGP and wait after the MNGP successful, I believe the updater will close after a few minutes then power off Classic and power on with the VMM buttons. Hopefully that works.
Used a second w10 laptop, resthome, with 2015 C++ redistribution applied, no luck. Just so you know, w10 updater complete prompt does not disappear even after a half hour. Unless ok is pressed on prompt, complete waits indefinitely.
I wonder if i should have done each firmware as they were released? 1849 revision prior to the classic update this week. I picked what was available.
Notice the dates, those boogers never would stay programmed, nor would the voltages for eq, absorb and float on the 150 (what an ongoing hassle).
There is a brightside. With the 150 updated to 2096, the eq, absorb and float voltages are saved even after reboot.
Anyway resthome, who knows why the mngp is blank. I gladly trade a mngp for variable storage.
I have decided not to update the other classic at this time.
watt@raspberrypi:~/Classic $ ./newmodbus -p 192.168.2.120
Watt 200 Display Panel 1.0.19, RossW
State Resting because Not enough power available
Firmware 1849
ClassicTime 07:02:28 10/00/2000
0 Watts out
50.5 Volts (Battery)
65.1 Volts (PV)
0.0 Amps (Battery)
9.9 kWh today (180 amphours)
watt@raspberrypi:~/Classic $ ./newmodbus -p 192.168.2.119
Watt 150 Display Panel 1.0.19, RossW
State Resting because Not enough power available
Firmware 2096
ClassicTime 00:59:41 11/00/2012
0 Watts out
50.1 Volts (Battery)
53.9 Volts (PV)
0.0 Amps (Battery)
12.0 kWh today (215 amphours)
watt@raspberrypi:~/Classic $
I just heard today from Jose in production I think it was that there was a new updater that is working way better !
Maybe this is finally the updater to end all updaters ? We can but hope !
That would be great.
boB
We ought to get away from a Windows based updater... hint hint.... boB
Quote from: Watt_ on July 21, 2016, 02:59:45 AM
We ought to get away from a Windows based updater... hint hint.... boB
From the peanut gallery:
Yeah, if it was for a PC it might be useful to build a mini Linux dedicated base install users can write to a USB stick or whatever. Boot the stick and let the updater automatically do what it does. [sorry Apple users]
Maybe that is a bit over the top but, frankly, Linux seems to be less likely to break your installer than M$ updates. Just a solid environment to do installs of your firmware. No internet, No fancy graphics, mouse. No buzzers and bells just a ncurses or other text environment that has you confirm the actions and reports success or failure. You could just change the firmware update file in the installer file system and name each "installer system" with the version of the firmware when the firmware changes.
Anyway, just had that rant come into my head. :o
Tom
May be unrealistic but might actually work
Quote from: Watt_ on July 20, 2016, 10:14:52 PM
Used a second w10 laptop, resthome, with 2015 C++ redistribution applied, no luck. Just so you know, w10 updater complete prompt does not disappear even after a half hour. Unless ok is pressed on prompt, complete waits indefinitely.
Watt ,,, Are you saying you never see a Success message? It's been a while but I thought there was at least a Success message. Maybe not, sorry that isn't working.
boB has said that they have another loader for WIN10, I've heard that before but it hasn't been made available to us.
Resthome, complete is " completed successfully " prompt.
As i said, it does not disappear until a " ok " dialog is clicked.
It appears the updater has changed since your last use. Might check it out.
Ryan emailed and has a solution in the works. Thanks everyone.
Quote from: TomW on July 21, 2016, 10:04:26 AM
Quote from: Watt_ on July 21, 2016, 02:59:45 AM
We ought to get away from a Windows based updater... hint hint.... boB
From the peanut gallery:
Yeah, if it was for a PC it might be useful to build a mini Linux dedicated base install users can write to a USB stick or whatever. Boot the stick and let the updater automatically do what it does. [sorry Apple users]
Maybe that is a bit over the top but, frankly, Linux seems to be less likely to break your installer than M$ updates. Just a solid environment to do installs of your firmware. No internet, No fancy graphics, mouse. No buzzers and bells just a ncurses or other text environment that has you confirm the actions and reports success or failure. You could just change the firmware update file in the installer file system and name each "installer system" with the version of the firmware when the firmware changes.
Anyway, just had that rant come into my head. :o
Tom
May be unrealistic but might actually work
Ross mentioned your using a linux based updater. I've been searching since.
Quote from: Watt_ on July 21, 2016, 05:40:07 PM
Resthome, complete is " completed successfully " prompt.
As i said, it does not disappear until a " ok " dialog is clicked.
It appears the updater has changed since your last use. Might check it out.
Ryan emailed and has a solution in the works. Thanks everyone.
Thanks Watt
Let us know what Ryan's solution is and how well it works for you, so we can all learn.
Quote from: Watt_ on July 21, 2016, 05:41:48 PM
Ross mentioned your using a linux based updater. I've been searching since.
Yeah, it was a perl script and was pretty good I thought,
Theoretically Perl should be cross platform if you tweak the device name / path whatever.
I wouldn't know as I only use Ubuntu and IOS on my phone. I used that updater running on my Raspberry Pi to upgrade at least 3 Classics.
I might have a copy of that script but it should be available from Midnite someplace. I can't remember who wrote it? Andrew maybe?
If I find it I will post it.
Tom
Quote from: boB on July 20, 2016, 10:25:26 PM
I just heard today from Jose in production I think it was that there was a new updater that is working way better !
Maybe this is finally the updater to end all updaters ? We can but hope !
That would be great.
boB
since July 1 they have infected one tracking W10 box , used only to track updates .
They are charging the suppliers of stuff to be compliant , not the end user as Us , but Midnite for the licence code .. TIME to buss windoz .
kb:3035583 is an important one
copy and paste the rest one at a time or use a .bat file :)
some new updates have been released since this list was compiled
Code:
wusa /uninstall /kb:3035583 /norestart
wusa /uninstall /kb:2952664 /norestart
wusa /uninstall /kb:2976978 /norestart
wusa /uninstall /kb:3021917 /norestart
wusa /uninstall /kb:3044374 /norestart
wusa /uninstall /kb:2990214 /norestart
wusa /uninstall /kb:3083711 /norestart
wusa /uninstall /kb:3083710 /norestart
wusa /uninstall /kb:3022345 /norestart
wusa /uninstall /kb:3068708 /norestart
wusa /uninstall /kb:3075249 /norestart
wusa /uninstall /kb:3080149 /norestart
wusa /uninstall /kb:3112343 /norestart
wusa /uninstall /kb:3123862 /norestart
YMMV & TAUW
VT
Quote from: TomW on July 22, 2016, 09:30:09 PM
Quote from: Watt_ on July 21, 2016, 05:41:48 PM
Ross mentioned your using a linux based updater. I've been searching since.
Yeah, it was a perl script and was pretty good I thought,
Theoretically Perl should be cross platform if you tweak the device name / path whatever.
I wouldn't know as I only use Ubuntu and IOS on my phone. I used that updater running on my Raspberry Pi to upgrade at least 3 Classics.
I might have a copy of that script but it should be available from Midnite someplace. I can't remember who wrote it? Andrew maybe?
If I find it I will post it.
Tom
Thsnk you for the info, Tom. I'll be on the look out.
USB updater. Take a page from the Schneider Electric playbook, to update the firmware, I load a file onto a thumbdrive, and plug it in. The gear senses the USB drive, runs the installer and reboots.
No OS required, just copy the firmware file to the thumbdrive and plug it in.
late night edit-
above described is the process to run a script to do maintenance on the system. (flush ROM, backup settings...)
Firmware is also installed on a thumb drive, and then the user interface in the Combox (think of a turbocharged router) is directed to load the firmware from the USB drive to the selected gear.
Ryan, got the MNGP and we have installed it. Works like a dream, thank you sir.
Do you think I should wait for a while on updating the other MNGP?
Quote from: Watt on July 26, 2016, 06:40:25 PM
Ryan, got the MNGP and we have installed it. Works like a dream, thank you sir.
Do you think I should wait for a while on updating the other MNGP?
I'd wait until they provide what ever uploaded they are using in production with Win10. Of course we have been waiting months for this and Win 10 has been out a year now. Seem like multiple people have had this issue with the MNGP using the current Win 10 updater.
Just my $.02.
Resthome, I ask because of another reason. It appears, by the majority feedback of the thread, this was end user error... IE.. me. So, if I did err, I should be ok with another attempt so long as I follow directions properly..... I sent other MNGP back yesterday.... So, maybe I should just wait.
most replacement units come from the factory with the latest FW versions loaded.
Best to see what comes to you before shooting in the dark... as there has been a update while this thread was active. You never know till it arrives...
Quote from: Westbranch on July 27, 2016, 08:46:42 PM
most replacement units come from the factory with the latest FW versions loaded.
Best to see what comes to you before shooting in the dark... as there has been a update while this thread was active. You never know till it arrives...
Well, sadly, hardware does not have a "Sell By" date. ;D
If a unit sits on the reseller's shelf a couple months it could be well out of date when you open the box. That is the down side of equipment from a company that is conscientious about post sale firmware improvements. Unlike a couple of my IP Cameras that tout the ability to upgrade but have nothing new from this century :o
Just an early A.M. thought.
Tom
Quote from: Westbranch on July 27, 2016, 08:46:42 PM
most replacement units come from the factory with the latest FW versions loaded.
Best to see what comes to you before shooting in the dark... as there has been a update while this thread was active. You never know till it arrives...
Thanks bud but, the unit I'm wondering if I ought to update is about 2 years out of the factory.
Did you not get it direct from MN? If so contact the person who sent it to you and ask...
Quote from: Westbranch on July 28, 2016, 09:15:15 PM
Did you not get it direct from MN? If so contact the person who sent it to you and ask...
Westbranch i think there may be some confusion. There are two classics mentioned in this thread. There are also two MNGPs. One classic and one MNGP were updated but the MNGP didn't boot afterwards. Ryan sent me a MNGP to replace this one that failed. Now, both classics are operational as the second classic was only used for testing. I asked, though, if i should wait to update the second classic .
I did not receive an item broke or nonfunctional. Also, the two year out of factory device has been mounted to my midnite epanel for the 2 years. When i received it it worked, just wouldn't keep its time stored or keep its voltages set. BoB, via irc, was aware and i explained i could work around it. So, no problems.
I have just had this exact problem updating a Classic 200. Can you fill me in on the solution? I followed all instructions to the T but still have a blank screen.
Thanks
Even though it's an older thread I think it is worth it to update. I issued a Support Ticket this morning at 7:30AM and was sent an MSI installer for Windows 10 by noon. Ran the new updater (which included newer firmware) and was back up and running in minutes! Everything running great. If anyone has the same problem you can issue a support ticket but I expect this fix will be included in the next firmware release.
Pretty happy with my choice of controller so far!
Yeah this Windows 10 updating has been a pain the ol backside, For some strange reason only certain pcs cause the "black screen of Death" as we call it. Matt has been working over time trying to resolve this in his new updater and I think he is about ready to roll it out. I apologize for the headaches this is causing
Any thoughts on a linux updater ? Will the win 10 updater also run win 8.1 or do I keep the XP laptop around for updates?
Quote from: Halfcrazy on November 30, 2016, 06:40:25 AM
Yeah this Windows 10 updating has been a pain the ol backside, For some strange reason only certain pcs cause the "black screen of Death" as we call it. Matt has been working over time trying to resolve this in his new updater and I think he is about ready to roll it out. I apologize for the headaches this is causing
Ha, no apologies necessary for me that's for sure. I design and write specs for technical systems for a living (not solar) so it's second nature for me to evaluate and select products based on specs, cost and functionality (as I did for the Classic). But the variable in the mix is always after sales service and how well the manufacturer supports their product. Since I don't deal with solar products in my work this was a total unknown for me so I'm very happy this happened because the support I received through the ticket system (and this forum) has been excellent. It makes me more confident with my selection especially considering I will need to add 2 more Classics to complete my system.
I'm sure I will become a regular on this forum!
So I uploaded the new updater to the website that will stop the black screen of death on windows 10, or at least engineering tells me it will ::)
http://www.midnitesolar.com/firmwareReport.php?firmware_ID=17&firmwareProduct_ID=1&act=edit
I do have engineering working on a linux updater also, Stay tuned.
Quote from: Halfcrazy on December 01, 2016, 10:44:29 AM
.....
I do have engineering working on a linux updater also, Stay tuned.
Awesome. I can boot with a live CD, update firmware, and then reboot back to windows 8.1 I hope. That's my intent, I hope I don't have to download a boatload of exotic library and patches each time I boot from a CD
Ryan ,
When is the new firmware with talking features for the Classic due to be released ?
Larry