Blank dark screen after 2096 firmware update

[boB]

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

[Resthome]

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

[Watt]

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.

[Watt]

Resthome, would you suggest, after the C++ redistribute install, I re-update the Classic as well as the MNGP? restart  Then, VMM? 

[Resthome]

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.

[Watt_]

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 $

[boB]

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

[Watt_]

We ought to get away from a Windows based updater... hint hint.... boB

[TomW]

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. 

Tom

May be unrealistic but might actually work

[Resthome]

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.

[Watt_]

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.

[Watt_]

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. 

Tom

May be unrealistic but might actually work

Ross mentioned your using a linux based updater. I've been searching since. 

[Resthome]

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.

[TomW]

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

[CDN-VT]

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