So today I was installing MM2 code and having a hell of a time getting 2 Classics to update. Tried 20 times or so each and NO GO. Feeling massive frustration I happened to be talking to an Engineering buddy of mine on the Ham Radio at the same time and he said "You do know the Ethernet is pretty noisy right?"
SO I unplugged my switch to kill the Ethernet and WALLAH!!!!!!!!!! They all update the first try every time.
Not saying this is a guarantee but if you are having issues getting the Classic boot loader to see the PC when you turn it on try shutting down the LAN
Ryan
Quote from: Halfcrazy on August 26, 2015, 08:58:26 AM
So today I was installing MM2 code and having a hell of a time getting 2 Classics to update. Tried 20 times or so each and NO GO. Feeling massive frustration I happened to be talking to an Engineering buddy of mine on the Ham Radio at the same time and he said "You do know the Ethernet is pretty noisy right?"
SO I unplugged my switch to kill the Ethernet and WALLAH!!!!!!!!!! They all update the first try every time.
Not saying this is a guarantee but if you are having issues getting the Classic boot loader to see the PC when you turn it on try shutting down the LAN
Ryan
Interesting, always worth a try next time it occurs. Will see what happens next week when we return to the boat.
Question is have you had the problem before or was it just with this MM2 update? I only had an occasional update problem until 2050 came along and then it was like you it went on for an hour or so trying to get the Classic to connect. It appears that the PC is ready and waiting and that when the Classic powers back on and the USB shows connected on Com8 that what ever handshake is suppose to take place doesn't happen. Guessing it seems like a timing problem. Does the code keep trying to communicate or is it one time only and then waits?
I have always had some issues and had to retry several times on the power up cycle. this worked every time this AM
and he said "You do know the Ethernet is pretty noisy right?"
Is it possible this is the source of constant disconnects of the Local App also???
eg. Lately, last 2 weeks, with a new laptop, wireless connection, I had drop outs and no reconnects , sometimes within minutes, < 5 it seemed, but with an older CPU (was XP now W7) hardwired to the wifi router, the drops were hours apart..if any before I signed off....
Quote from: Halfcrazy on August 26, 2015, 06:20:41 PM
I have always had some issues and had to retry several times on the power up cycle. this worked every time this AM
Will be an interesting experiment to try. My Router and Wi Fi are within a foot of the Classic. But the Classic generates more noise when charging than anything else. Marine band 68 can not squelch the noise 20 ft away from the Classic. ::)
I tried to do the update on my two classics 150, they not only do not meet a com8 but are now blocked despite factory reboot. .
here I have tried the same thing ie unplug the internet and this is ok.
Thanks
Quote from: Resthome on August 26, 2015, 07:45:11 PM
Quote from: Halfcrazy on August 26, 2015, 06:20:41 PM
I have always had some issues and had to retry several times on the power up cycle. this worked every time this AM
Will be an interesting experiment to try. My Router and Wi Fi are within a foot of the Classic. But the Classic generates more noise when charging than anything else. Marine band 68 can not squelch the noise 20 ft away from the Classic. ::)
Well with Win10 i can no longer get the Classic to do updates. Tried unplugging the router and that made no difference. Tried reinstalling the Midnite driver and set it to COM 8 - Update said that "COM8 is busy or does not exist." Multiple tries results in no connections with the 2056 update.
So i am at a dead end until Midnite responds to update instructions for WIN10.
As I mentioned windows 10 has causes us a lot of issues, The Local app not working is one. I will add it to my to do list but I suspect the updater may not work in windows 10. The good news is 2056 really only applies to Classic SLs so there is no real value in updating to it on a regular Classic
Quote from: Halfcrazy on September 30, 2015, 06:35:18 AM
As I mentioned windows 10 has causes us a lot of issues, The Local app not working is one. I will add it to my to do list but I suspect the updater may not work in windows 10. The good news is 2056 really only applies to Classic SLs so there is no real value in updating to it on a regular Classic
Thanks Ryan. With MS updating all Win7 and Win 8.1 computers to Win10 I hope this moves to the top of the list.
Strange the Local App has been working for me under Win10. Is there a particular issue with the LA that does not work under WIN10? I did have Norton 360 stop the LA from running, it said it had detected suspicious network activity or something close to that.
Quote from: Halfcrazy on August 26, 2015, 08:58:26 AM
So today I was installing MM2 code and having a hell of a time getting 2 Classics to update. Tried 20 times or so each and NO GO. Feeling massive frustration I happened to be talking to an Engineering buddy of mine on the Ham Radio at the same time and he said "You do know the Ethernet is pretty noisy right?"
SO I unplugged my switch to kill the Ethernet and WALLAH!!!!!!!!!! They all update the first try every time.
Not saying this is a guarantee but if you are having issues getting the Classic boot loader to see the PC when you turn it on try shutting down the LAN
Ryan
Just for the record I tried unplugging the Ethernet router and unplugging it from the Classic. In my case this did nothing to help connect the laptop to the classic on COM8 for firmware updates.
W7 machine used for previous update... hair pulling time again HPTA!!
OK, I loaded the new GUI etc and have deleted and reloaded said program 5 times so farrrrr......NADA
I plug PC into the Classic and wait for the message about com8 which is not on my PC anywhere and NADA!!
I have also tried using the GUI and it gives 2 Command screens and then tells me Com8 is not loaded...
I tried the "Wizbandit Sticky" process and also NADA????
where have I gone wrong, have been following the manual to a "T".... thanks Resthome, it worked last time but not now???
Erik
Try looking in the Device Manager with the USB cable plugged in from the Classic to the Computer under Port you should see the MidNite drive it has to be on COM8. Do you have that?
yes, thanks John, got it to load FW and NetW ! 8)
I am suspecting a loose connection... I rechecked all connections ,again, and it worked.. maybe a partial touch on one of the several copper wires? If it happens next update time I will swap out both cables (2 Classics) just to eliminate that possibility. next would be the PC socket, as I used a different one (choice of 3) when I succeeded... so I'm now not sure if it was one or the other.. duh...
Note to self: Remember, only change one variable at a time! ::) ::)
I had a heck of a time with an update today, to the latest and greatest. It crashed the panel and I had to do the jumper reboot.... but for two hours, i was really panicking, as the controller is our source of juice now that we're off-grid.
The VMM was useless....
and I am now fearful of turning the controller off (not that it's off very often.)
Vern, what did you use to do the install?
I had a bearcat of a time for awhile, but once I got the first install of V 2074 in, loose wire?
the folllow-up installls (suspected bad install) went smoothly...including VMM's ....now narrowed down to the power board and it is to be replaced soon...
ADD: in BLUE
Quote from: Vern Faulkner on December 05, 2015, 07:19:08 PM
I had a heck of a time with an update today, to the latest and greatest. It crashed the panel and I had to do the jumper reboot.... but for two hours, i was really panicking, as the controller is our source of juice now that we're off-grid.
The VMM was useless....
and I am now fearful of turning the controller off (not that it's off very often.)
Define "crashed the panel". Did the MNGP stop with a bunch of number showing or what?
Also what version where you updating from?
Quote from: Westbranch on December 05, 2015, 07:53:09 PM
Vern, what did you use to do the install?
I had a bearcat of a time for awhile, but once I got the first install of V 2074 in, loose wire?
After I couldn't get the installer to function in wine (under Ubuntu linux), I assembled the energy-pig windows vista tower of my other halfs, the same machine used to do previous installs... and did everything as I have done before. I even uninstalled the latest and tried to backgrade to a previous version (a stable one from 2014 that had been on the Classic for a year and change).... no dice.
Changed cables, did it with no other electonics in the area (ethernet off, etc.) .....
Quote from: Resthome on December 05, 2015, 08:24:20 PM
Quote from: Vern Faulkner on December 05, 2015, 07:19:08 PM
I had a heck of a time with an update today, to the latest and greatest. It crashed the panel and I had to do the jumper reboot.... but for two hours, i was really panicking, as the controller is our source of juice now that we're off-grid.
The VMM was useless....
and I am now fearful of turning the controller off (not that it's off very often.)
Define "crashed the panel". Did the MNGP stop with a bunch of number showing or what?
Also what version where you updating from?
Can't remember old firmware version, but it was a stable one from July/august (IIRC) 2014.
The system locked up after going through the basic post VMM menu tree - after setting time, it barfed with the code
SENDING DATA
4136 502
Quote from: Vern Faulkner on December 06, 2015, 06:01:46 PM
Quote from: Resthome on December 05, 2015, 08:24:20 PM
Quote from: Vern Faulkner on December 05, 2015, 07:19:08 PM
I had a heck of a time with an update today, to the latest and greatest. It crashed the panel and I had to do the jumper reboot.... but for two hours, i was really panicking, as the controller is our source of juice now that we're off-grid.
The VMM was useless....
and I am now fearful of turning the controller off (not that it's off very often.)
Define "crashed the panel". Did the MNGP stop with a bunch of number showing or what?
Also what version where you updating from?
Can't remember old firmware version, but it was a stable one from July/august (IIRC) 2014.
The system locked up after going through the basic post VMM menu tree - after setting time, it barfed with the code
SENDING DATA
4136 502
That's occurred in the past when the jump between versions of firmware where large and boB had made some Modbus register changes.
I tend to try to do the firmware version in the order they are release, although it should not matter. Looks like it stuck trying to write the ModbusTCPPort 502.
Vern, if you try it again, after the install, disconnect the battery power as well as the PV input to the classic, then, while holding down the 2 soft keys < and >, reconnect the battery followed by the PV, ....
I found that helped. Don't know why but...??
hth
Well, finally got the firmware updated on my Classic and MNGP.
It took several times of power cycles and quitting and starting the Classic updater. I found it was easier to run a command prompt in Administrator mode and run the update line from the batch file manually. That way I could ctrl-c the command when it didn't find com8, repeat the command and power on the Classic.
Another issue was updating the MNGP. For some strange reason, the update would not work unless I plugged the MNGP into the middle port on the Classic. Once I updated the MNGP, I plugged it back into the top port and all is good now. I still had to do the power on-off-ctrl-c, etc. bit to get it to go into firmware update mode.
I was using Windows 10 to do this. I had the same issues of the updater not recognizing com8 on XP and 7, too and having to do the same as above.
Quote from: phxmark on January 08, 2016, 09:34:04 AM
Another issue was updating the MNGP. For some strange reason, the update would not work unless I plugged the MNGP into the middle port on the Classic. Once I updated the MNGP, I plugged it back into the top port and all is good now.
Phxmark, what made you try this plugging into the middle port on the Classic?
I don't recall anyone ever mentioning it...
Quote from: Westbranch on January 08, 2016, 12:40:12 PM
Quote from: phxmark on January 08, 2016, 09:34:04 AM
Another issue was updating the MNGP. For some strange reason, the update would not work unless I plugged the MNGP into the middle port on the Classic. Once I updated the MNGP, I plugged it back into the top port and all is good now.
Phxmark, what made you try this plugging into the middle port on the Classic?
I don't recall anyone ever mentioning it...
I didn't think about it. I pulled the cover off to clean and re-seat the connection and accidentally plugged it in to the middle connector. The MNGP still powered on and communicated through the middle port with the Classic. I didn't screw the cover back on. I performed the MNGP update not knowing it was in the middle port. Once it was done, I realized it was in the wrong port I plugged it back into the top port.
Hmm, that 'dirty contact' may be a part of the Upgrade issues some of us are having...
mind you I have removed and replaced that RJ cable several times of late on mine, just cant remember if it was before or after the successful upgrade.
I took the cover of to access all the connections , USB, Cat5, WBjr and RTS, just to be sure they were seated properly...
Quote from: Westbranch on January 08, 2016, 08:35:10 PM
Hmm, that 'dirty contact' may be a part of the Upgrade issues some of us are having...
mind you I have removed and replaced that RJ cable several times of late on mine, just cant remember if it was before or after the successful upgrade.
I took the cover of to access all the connections , USB, Cat5, WBjr and RTS, just to be sure they were seated properly...
I read somewhere that the top port and middle port are basically the same except the middle port does not have a couple of the LED pins running to it. Maybe I have a bad pin on the top connector. Oh well, I am happy to get it upgraded, whatever works.
I was really hoping this would work, after trying to update my Classic 150 about 12 different ways with no success. Are there any tips to get this buggy process to work? I've tried:
- three different laptops
- 4 different USB cords
- every permutation of plugging things in and turning on the Classic
As always, the USB driver installs fine, and setting the port to COM8 always works, but it *always* fails with a "Bad USB cable" error. The only thing, at this point, that I can say is that my Classic is broken. There's no other explanation for my it won't take firmware updates. The last time I was able to successfully update the firmware was back at the end of 2013.
Any suggestions? Should I send it in to Midnite to see if they can update the firmware?
Quote from: crunnells on January 22, 2016, 04:51:49 PM
I was really hoping this would work, after trying to update my Classic 150 about 12 different ways with no success. Are there any tips to get this buggy process to work? I've tried:
- three different laptops
- 4 different USB cords
- every permutation of plugging things in and turning on the Classic
As always, the USB driver installs fine, and setting the port to COM8 always works, but it *always* fails with a "Bad USB cable" error. The only thing, at this point, that I can say is that my Classic is broken. There's no other explanation for my it won't take firmware updates. The last time I was able to successfully update the firmware was back at the end of 2013.
Any suggestions? Should I send it in to Midnite to see if they can update the firmware?
What OS are you using on the laptops? I've seen someone post with the "Bad USB cable" message. I've never seen that error (maybe I just missed it), just usually times out for me with a COM8 message IIRC.
Are you updating the Classic or the MNGP?
Also:
have you tried a different USB port?
Have you re-seated the USB cable in the Classic?
I had one occurrence with a poor contact just from the cable moving when I adjusted the laptop...
Resthome: Windows 7 on all 3 laptops. I'm not sure what difference the OS would make, but maybe? Last time it worked was on a Windows 7 machine (well, a Macbook running Fusion with Windows 7 installed, but I digress). The way the problem occurs is that it detects COM8, starts uploading the update, but never gets past 0% and drops out with a "bad usb" error. It fails on both the Classic update and the MNGP update.
Westbranch: I used 4 different USB cables, on all available USB ports on the laptops. Pretty sure it's not the USB ports or the USB cables, since they work just fine for other devices.
Quote from: crunnells on January 22, 2016, 05:57:30 PM
Resthome: Windows 7 on all 3 laptops. I'm not sure what difference the OS would make, but maybe? Last time it worked was on a Windows 7 machine (well, a Macbook running Fusion with Windows 7 installed, but I digress). The way the problem occurs is that it detects COM8, starts uploading the update, but never gets past 0% and drops out with a "bad usb" error. It fails on both the Classic update and the MNGP update.
Well there are different instructions for different OS. But I've had mostly good luck with Win7 but better luck with Win8.1 and no luck with Win10. I'm at a lost since you say it starts the update and shows the 0% and then the bad cable message. Usually if you get that 0% the connection was made. All my failures have be Com8 busy or not available.
Maybe boB can decipher what is being checked when the "bad cable error" is displayed.
Ryan had said the new Beta Updater for Win10 was suppose to work with all OS but I'm not sure that is the case. It would be nice if it was and you could give it a try. I think you have to contact Ryan to get a copy of it anyway so you might PM him and ask if it will work with Win7 (maybe - maybe not).
http://kb1uas.com/mnsforum/index.php?topic=2753.msg26052#msg26052 (http://kb1uas.com/mnsforum/index.php?topic=2753.msg26052#msg26052)
I'll try to PM boB and Ryan to see if one of them can help figure this out. It's been a problem for over 2 years now, and with the upcoming move to mymidnite2.com I'm going to be out of a way to monitor my system remotely.
This might just be the kick I need to get my BBB-BB (Beagle Bone Black - Black Box) running again. Still would be nice to have some features like SoC, etc.
did you also get the MicroSoft , dudaah, New Hardware connected when you plugged the USB cable in?
I found W7 installs have to be exactly as outlined in Johns link, full power off, etc
I resurrected an old XP laptop to get a working USB that didn't need 15 pages of instructions for win 8.1
I did one update about year and half ago, and till I have a good reason to try to brick the classic, I'm not going to try it again. Still too many failure reports to risk a non critical update.
Quote from: mike90045 on January 22, 2016, 10:15:36 PM
I resurrected an old XP laptop to get a working USB that didn't need 15 pages of instructions for win 8.1
I did one update about year and half ago, and till I have a good reason to try to brick the classic, I'm not going to try it again. Still too many failure reports to risk a non critical update.
Hopefully the new updater Midnite is working on will be a lot simpler to use and it appears it does not require special drivers to be installed.
The one good thing about the Classic is I have never heard of anyone bricking one. You can even go back and installed previous version firmware.
I have a special talent, I can follow every step, and brick things. I've a knack for making things misbehave, and even at work, the software guys had me test stuff, in about 20 seconds, they were back to a week of fixes, it really helped make stuff bulletproof for the military and save the embarrassing crash when presenting to the customer.
I can also recover crashed computers, de-scramble hard drives (when SSD's fail, they are goners) and do PC repairs, and have many happy clients. Must be some magnetic field!
Westbranch: this past Sunday we updated the firmware on my brother-in-laws Classic, using his laptop (the same we were using to try to update mine). It went through flawlessly, like it should. So I definitely think we can take the common denominator (his laptop) out of the equation and suggest that either I have 4 bad USB cables (unlikely; in 20 years I've never seen a bad USB cable that wasn't obviously frayed OR rusty) or there's a problem with my Classic. I'm leaning towards the latter.
with that evidence it certainly appears that there is an issue in the Classic.
Try sending Ryan an email Ryan at Midnitesolar dot com
ADD: just looked at Ryan's opening post, did you try turning off any Wifi etc that may be causing noise?
Quote from: crunnells on January 26, 2016, 04:38:21 PM
Westbranch: this past Sunday we updated the firmware on my brother-in-laws Classic, using his laptop (the same we were using to try to update mine). It went through flawlessly, like it should. So I definitely think we can take the common denominator (his laptop) out of the equation and suggest that either I have 4 bad USB cables (unlikely; in 20 years I've never seen a bad USB cable that wasn't obviously frayed OR rusty) or there's a problem with my Classic. I'm leaning towards the latter.
Well just saw a post from Ryan that said the new W10 updated does not work with other OS without doing some fooling around, so looks like that option is out. Was it the Classic or MNGP update that fails or is your a Lite? Did boB ever reply? Sound like Ryan has been on travel and is behind on PM so don't know if you heard from him. I'm still curious as to what triggers a bad cable message. Has to be something the code is watching for.
My classic 200 is dead this morning. I download the firmware 2079 upgrade for win10 yesterday, I figured better do the upgrade before sunrise today, go to the garage at 530am, 46 deg F, plug in USB thing go ok after 3-4 times tried, power up with left/right arrow press dwn, system booth up, check the new 2079 is in. The COM was 3
The next thing tried to upgrade the mngp, 5 times when it get around 60ish% completed, it hard reboot my laptop, I gave up, my hand is cold, I wait when the sun is up and try it one more time.
All I got at this time the red led, I can not even log in local software because I did not configuration the ip yet. Help, help, help
For previous updates it is Com 8 not 3. Did this change for the W 10 updater?
When I plug in the usb, system power up, the software said com 3 connected, I did the controller ok, the mngp that is hang up, I m going to get my other laptop out there to see if I can get it going, I will let your guys know, both of my laptop are win10
Howdy,
So It's been 3 years since I last updated the Firmware on my Classic 150. 3 years ago I had a heck of a time updating and since what I had wasn't broke I haven' wanted to touch the Firmware again. Well, now there is the mymidnite.com update that needs the latest Firmware and I bought a Wiz-bang, so I have to update the Classic. Should of been fun...ah no.
I used Windows 10 and Rev 2079 For windows 10 Firmware update. Everything went smoothly for the Classic firmware update, did the Factory Reset, answered all the questions. Then I upgraded the MNGP remote. Firmware loaded 100 percent only the MNGP was now Blank! Tried to do a factory reset. Nope. nothing.
So right at this moment I am dead in the water. Anyone got ideas? Thanks! --CPT Tom
Did you try looking at the Classic with the Local App to see if you can get anything out?
I haven't used W10 yet for upgrade, do you still get the "finished' message in a command box after each upgrade is 100%?
Quote from: Westbranch on January 31, 2016, 08:24:47 PM
Did you try looking at the Classic with the Local App to see if you can get anything out?
I haven't used W10 yet for upgrade, do you still get the "finished' message in a command box after each upgrade is 100%?
Good point WB. The old installer took almost 2 additional minutes to complete after it said 100%. I'm like you and haven't tried the W10 uploaded yet because I want to have a few days to visit before attempting it. And a Win 8.1 laptop as a backup.
Hi Westbranch,
Nope, I can't see the Classic with the Local App. :(
After the update it there is a message that I think says "Update 100% Complete" or words to that effect. I even tried updating again. Still a blank screen.
Quote from: Westbranch on January 31, 2016, 08:24:47 PM
Did you try looking at the Classic with the Local App to see if you can get anything out?
I haven't used W10 yet for upgrade, do you still get the "finished' message in a command box after each upgrade is 100%?
Quote from: cpttom on January 31, 2016, 08:42:11 PM
Hi Westbranch,
Nope, I can't see the Classic with the Local App. :(
After the update it there is a message that I think says "Update 100% Complete" or words to that effect. I even tried updating again. Still a blank screen.
Quote from: Westbranch on January 31, 2016, 08:24:47 PM
Did you try looking at the Classic with the Local App to see if you can get anything out?
I haven't used W10 yet for upgrade, do you still get the "finished' message in a command box after each upgrade is 100%?
Any LEDs on?? I'd also log a trouble ticket with Midnite to get to the bottom of this since the W10 firmware loader is new.
I saw your other reply as well. I didn't even think about waiting 2 mins after the complete message. I am going to try the update again and see what happens after waiting for 2 mins.
Also, their weren't any LEDs except the power light on the MNGP once the Classic powered back on....I will post back once I do the reinstall again.
Quote from: Resthome on January 31, 2016, 08:50:28 PM
Quote from: cpttom on January 31, 2016, 08:42:11 PM
Hi Westbranch,
Nope, I can't see the Classic with the Local App. :(
After the update it there is a message that I think says "Update 100% Complete" or words to that effect. I even tried updating again. Still a blank screen.
Quote from: Westbranch on January 31, 2016, 08:24:47 PM
Did you try looking at the Classic with the Local App to see if you can get anything out?
I haven't used W10 yet for upgrade, do you still get the "finished' message in a command box after each upgrade is 100%?
Any LEDs on?? I'd also log a trouble ticket with Midnite to get to the bottom of this since the W10 firmware loader is new.
Yeah, the DOS command window will actually close after the 2 minutes with the previous updater. So if you are seeing a DOS command window wait and see if it closes. I'm not convinced that is the problem but worth a try.
I'm also assuming the short blue cable is still connected between the Classic and the front cover.
There is no DOS Command window in this version. Just the selection window and install window. I tried reinstalling. No luck. I have opened a trouble ticket. Let's see what happens.
Quote from: Resthome on January 31, 2016, 09:28:41 PM
Yeah, the DOS command window will actually close after the 2 minutes with the previous updater. So if you are seeing a DOS command window wait and see if it closes. I'm not convinced that is the problem but worth a try.
I'm also assuming the short blue cable is still connected between the Classic and the front cover.
Quote from: CharliVN on January 31, 2016, 07:53:01 AM
My classic 200 is dead this morning. I download the firmware 2079 upgrade for win10 yesterday, I figured better do the upgrade before sunrise today, go to the garage at 530am, 46 deg F, plug in USB thing go ok after 3-4 times tried, power up with left/right arrow press dwn, system booth up, check the new 2079 is in. The COM was 3
The next thing tried to upgrade the mngp, 5 times when it get around 60ish% completed, it hard reboot my laptop, I gave up, my hand is cold, I wait when the sun is up and try it one more time.
All I got at this time the red led, I can not even log in local software because I did not configuration the ip yet. Help, help, help
It sounds like you did a factory restore on the classic BEFORE you actually updated the MNGP. This may cause some issues as there are registers that are not present in one piece of the two. What I would suggest is trying the hardware factory restore then try updating the MNGP again. (Directions are on the software page) if that doesn't work email support and they will get you fixed up support@midnitesolar.com
Quote from: Westbranch on January 31, 2016, 12:18:52 PM
For previous updates it is Com 8 not 3. Did this change for the W 10 updater?
Yes in Windows 10 you do not need to worry about the com port it auto detects
Quote from: cpttom on January 31, 2016, 08:07:00 PM
Howdy,
So It's been 3 years since I last updated the Firmware on my Classic 150. 3 years ago I had a heck of a time updating and since what I had wasn't broke I haven' wanted to touch the Firmware again. Well, now there is the mymidnite.com update that needs the latest Firmware and I bought a Wiz-bang, so I have to update the Classic. Should of been fun...ah no.
I used Windows 10 and Rev 2079 For windows 10 Firmware update. Everything went smoothly for the Classic firmware update, did the Factory Reset, answered all the questions. Then I upgraded the MNGP remote. Firmware loaded 100 percent only the MNGP was now Blank! Tried to do a factory reset. Nope. nothing.
So right at this moment I am dead in the water. Anyone got ideas? Thanks! --CPT Tom
Tom
I would try it a few times and if still no success email us at support@midnitesolar.com and the support crew will get you fixed up
Ryan,
Thank you for the reply, very strange happen to me, I use I5 Asus laptop to upgrade the Classic 200 from 20xx to 2079 version, the classic go ok after couple tried, but when I upgrade the MNGP, something not going very well, my computer some how from some where keep getting power off at around 6x%ish, hard reboot so the display is blank, all I got both red LED.
Before go the bed last night, I took my I7 Dell laptop out in the garage and tried one more time, with new Win10 computer and Win10 upgrade (beta) software, it took forever to get the USB driver install, after that I start upgrade the MNGP, I watch the computer screen, it went past 64% and keep going till when it hit 100% and the msg said upgrade completed, so happy when I see that, follow the instruction, reboot the classic, and now I have 2079 version for the classic and 2056 for the MNGP, I don't know if I want to messy around with the upgrade any more, too hard to get it done, not very friendly, I hope some one working on it to make our user a lot easier.
Glad it finally went. I did not think the Windows 10 updarer asked us to monkey with a driver so I was under the impression it was pretty easy to use?
Ryan,
Since my MNGP still at 2056FW, do you think I gain anything major to go to 2079FW or should I just leave it alone for now. I thing I know my classic200 not talking to mymidnite2.com yet, when I log in it have ! mark at FW field, I need to work on this when I get home today.
Quote from: CharliVN on February 01, 2016, 11:50:22 AM
Ryan,
Since my MNGP still at 2056FW, do you think I gain anything major to go to 2079FW or should I just leave it alone for now. I thing I know my classic200 not talking to mymidnite2.com yet, when I log in it have ! mark at FW field, I need to work on this when I get home today.
I'm not Ryan. But the Classic and the MNGP are not always at the same FW version. The Readme file for Classic 2079 shows the last MNGP at 2054 for SL changes. So if you are at MNGP 2056 the documention could be wrong. But I would not try to update the MNGP again unless Ryan says there is a later version not called out in the Readme file.
Ryan..
Just curious if we had tried to update with W10 and the old loader and driver. Should we remove the old driver and old software or does it matter. Just wanted to make sure there is not conflicts between the old and new method. I believe the old driver does not get removed with the old software uninstall.
Glad I still have a working XP machine. Maybe I can rent it out ?
Quote from: Resthome on February 01, 2016, 01:35:35 PM
Ryan..
Just curious if we had tried to update with W10 and the old loader and driver. Should we remove the old driver and old software or does it matter. Just wanted to make sure there is not conflicts between the old and new method. I believe the old driver does not get removed with the old software uninstall.
Thats a good question, I would delete the driver and any trace of the installer just to be safe
I have the same issue....The thing is the directions on the website say the following in the second paragraph of the Release notes at http://www.midnitesolar.com/firmwareReport.php?firmware_ID=17&firmwareProduct_ID=1&act=edit:
Quote
After installing the firmware in the Classic or MNGP it would be a good idea to do a "Factory Restore" or a "Quick Start".
When I got the blank screen on the MNGP, I tried the hardware factory reset, but no joy. I also tried to reinstall several times. no luck.
I have a ticket open and am in the process of switching out the MNGP. I think there is something not quite right with your utility, and I also suggest you change the wording of the quoted sentence. Thanks.
Quote from: Halfcrazy on February 01, 2016, 06:06:28 AM
It sounds like you did a factory restore on the classic BEFORE you actually updated the MNGP. This may cause some issues as there are registers that are not present in one piece of the two. What I would suggest is trying the hardware factory restore then try updating the MNGP again. (Directions are on the software page) if that doesn't work email support and they will get you fixed up support@midnitesolar.com
Looks like it's been changed.
After installing the firmware in the Classic AND MNGP it would be a good idea to do a "Factory Restore" or a "Quick Start".
Quote from: Resthome on February 01, 2016, 06:01:24 PM
Looks like it's been changed.
After installing the firmware in the Classic AND MNGP it would be a good idea to do a "Factory Restore" or a "Quick Start".
Neither of those terms / functions seem to be in the General FAQ's sub forum. Where can they be found ???
They've updated the directions for the Windows 10 version of the Firmware upgrade: http://www.midnitesolar.com/firmwareReport.php?firmware_ID=17&firmwareProduct_ID=1&act=edit : Excellent!
Quote from: mike90045 on February 01, 2016, 09:44:20 PM
Quote from: Resthome on February 01, 2016, 06:01:24 PM
Looks like it's been changed.
After installing the firmware in the Classic AND MNGP it would be a good idea to do a "Factory Restore" or a "Quick Start".
Neither of those terms / functions seem to be in the General FAQ's sub forum. Where can they be found ???
First I was afraid to do the update on my Classic Lite --- I know my "luck" sometimes ... hehe
So I downloaded the video, put it on my XP netbook together with the Update exe,
AND to avoid possible problems, thanks to this post from halfcrazy, because I sometimes had lost network connection to the Classic, unplugged the network cable :D
I followed the video and - it worked like a dream ;)
no settings lost, all working again.
so easy ;)
Quote from: binkino on February 03, 2016, 12:44:40 PM
no settings lost, all working again.
After any firmware update it is advisable to do a Factory Restore that sets all settings back to default. So if you have
"no settings lost" you may not have done a Factory Restore.
Release Notes:
You should do a factory restore after this update (Please note you should update the Classic and MNGP first). This will erase all the custom settings so make sure you have them noted before hand. The New AUX functions can possibly change the settings in the existing AUX modes so if a factory restore is not done please verify all Aux settings.
After installing the firmware in the Classic AND MNGP it would be a good idea to do a "Factory Restore" or a "Quick Start". To do this first turn the battery and solar power to the Classic off. Next, turn the battery power back on while holding the Left and Right arrows. Hold the arrows until the first "Solar, Wind or Hydro" screen pops up. Follow the on screen prompts and continue setup. Note: This will reset all settings to factory defaults. You will need to reset any custom settings such as Aux 1 and 2. You may want to write these settings down for reference prior to resetting the Classic.
I have a 'Lite' - I have to do the Jumper-thing ;)
okay will do, can I restore the datas? Was hoping to keep them
Quote from: binkino on February 03, 2016, 01:11:14 PM
I have a 'Lite' - I have to do the Jumper-thing ;)
okay will do, can I restore the datas? Was hoping to keep them
If you are referring to the daily log data you can use the "NEW DAY" function to write the current day data to the EPROM and then it will write the remaining day information at 23:59 so you would have two entries for the day that you would have to add together to get the daily total. If you don't do this the current day data is lost.
Another way is to reboot after midnight and while it is still resting and before it starts charging and collecting data for the day.
You can also use the newest Local App to export all your Classic settings and then import them back in after rebooting the Classic using the Local App.
okay :)
So these datas are not lost, good to know :)
I cheated the Classic, set the time to 23.59 hour, and waited the reboot :D
So now I did the Jumper-Factory-Reset and give it all settings again.
2 reboots later all datas are displayed again, also WBJr is back in race
and Graham's Android App (a dream!) also diaplay all datas again.
oh - another hint, good to know:
If the PV-Input voltage is higher then normal in the classic at night, you forgot to switch on the PV Input breaker
hahaha - back to basement and give this switch a small roundhosekick - me again :D
thanks
Nevertheless, now the data are lost from Wednesday (yesterday) AND Tuesday ...
Tuesday was stored and the day was Wednesday
Wednesday was stored by setting the time to 23.59h and let it reboot and waiting some minutes before updating.
Why did it delete the datas from Tuesday?
See attachment, I still don't know how how to place the picture inside this post ...
Sorry, I have no idea what program you are using or how you are adding the data.
And I did not tell you to change the time on the Classic. I said to reboot after midnight while Classic was resting and before it started charging for the day. Or use the new day function that makes two entries for the same day.
Have you tried to dump the OFFLINE data from the Local App?
I have no idea what it might have done changing the time forward and then changing it back. I would guess you would have cause it to write twice to the same day but do not really know. The New Day function is the correct way to do this. However, I have no idea what your app would do with two entries for the same day.
Does your monitoring program always save to the same location and use the same file name?
If so that is why you no longer have the previous days data, it is overwritten....
AFAIK the data saved has to be APPENDED to the current data to avoid overwriting..
and it probably would have to be in a database form......
it has been too long ago for me to recall all that you have to do...
hth
The App ("Classic Monitor" from Graham) does not store datas, it allways loads the datas from the Classic (every time it connects)
So I was wondering, that also Tuesday was also lost - this is lost in the Classic
If only Wednesday would be lost, we could explane.
It is not the biggest problem, I lost so many datas because power cycling, when network part of the classic was not working, or if I had to work on the system... but curious
I would eb happy, if there would be a way to direct modify the stored datas :)
Quote from: binkino on February 06, 2016, 04:35:33 PM
The App ("Classic Monitor" from Graham) does not store datas, it allways loads the datas from the Classic (every time it connects)
So I was wondering, that also Tuesday was also lost - this is lost in the Classic
If only Wednesday would be lost, we could explane.
It is not the biggest problem, I lost so many datas because power cycling, when network part of the classic was not working, or if I had to work on the system... but curious
I would eb happy, if there would be a way to direct modify the stored datas :)
Oh I missed the part about you having a Lite with no RTC with battery backup. The time and date inside the classic will be good after it is set as long as the power does not go off. If the DC power goes off, then the time and date will have to be set by the PC Local App when it is turned back on again. The data logs will not be correct until the time and date is set again.
You also cannot do the New Day function without the MNGP as I do not believe this function is in the Local App.
Have you ever waited until it writes to the EPROM for the day at 23:59 and then do you Factory Reset after the day has rolled over (verified with the LA) but while the Classic is still resting for the night and before it wakes up? And then immediately resetting the date and time to the current date. Not changing the time with the LA to try to fake it out. It seems like that should work but maybe not.
I’m not a Lite user and much prefer the MNGP as it has so many more features and tricks that boB has put it. Well worth the money IMHO.
Yesterday noon (~ 11.00 am) I was in the basement and hear the fans were running full speed, the turbo fan was making bad noise, must check that the fan sits well in the case
AND all LEDs were blinking.
Wanted to check whats up, via the App, but was not able to connect via network.
So power.cycled the Classic by disconnect PV and then Batteries. Then reconnect Batteris and then PV, everything was running like before.
Problem: BUT again I lost stored datas of 2 days. The datas of yesterday and the day before.
Normaly it should only lose data of yesterday...
Can you give me a link to older firmwares?
Thanks
Binkino
Are. You sure the clock has been set correctly on your life?
You should contact MidNite about the issue of the Classic locking up, this is not normal.
Hi Resthome,
yes time was correct set
I first want to test older firmware - this 2-day-amnesia is since the update
Quote from: binkino on February 27, 2016, 05:45:36 AM
Hi Resthome,
yes time was correct set
I first want to test older firmware - this 2-day-amnesia is since the update
I'd be more concerned with finding the Classic in a state with all fans running and the LEDs all flashing than I would about losing two days of data. And I don't think changing firmware is going to resolve that issue. At least I don't believe anyone else has reported seeing this. Have you seen that issue more than once? Even once it seem too many times to me. I'd find it hard to believe the Classic was still providing a charging function in that state.
On the data issue I can not see why you would lose the previous day's data unless it wasn't being written to the EPROM at 23:59 or the Classic rebooted prior to that time. Have you verified the previous day's data is missing from the LA as well as with Graham's app?
I don't know,
this issue I have seen the first time now.
I was just in the basement and fixed the fan rattling problem. Fan was running full speed again, but all LEDs were off this time.
Can contact with the Midnite App and also Graham's App to the Classic via Network. Is working.
Will have to observe this now daily
Just an idea, possible only a overheating issue? Fans running, LEDs blinking ...
Searching in the manual, only find "overheating" in the FAQ page 75, blinking orange LED and reffered to the version with MNGP
We have perfect weather - cold and much sun now.
Don't know where to put this much energy to :D
It is a Classic lite 200
The PV has a VOC of 148 Volts
Temperature outside is 8°C (46°F)
_ System ist now at:
139 - 140 Volt
3.8 - 4.0 Amps
and 500-570 Watts,
_ Batteries "full" (97%) and have 54,8 Volts and consuming 10 Amps (1,3Amps for battery and rest for home energy)
I updated my two classic 150's about 2 weeks ago to the latest firmware. After a breaf stumble with the windows 10 loader that I overcome by using a old XP laptop everything has been fine on the latest firmware.
Well so I thought :)
I just opened up the local app and one of my classics is now reporting under the DATA tab....
Lifetime Values
Kilowatt Hours: 429,172,928.5
Amp Hours: 5,262
Now I know the classics can squeeze every last Kwh from your PV but four hundred and twenty nine million KWH! That's impressive :) and all that from only 5,262Ah. last time I checked I didn't have a 81,000 volt battery bank so I think something is messed up.
My other 2nd classic that was also updated is reporting correct life time values.
Kurt
Kurt that number has come up before..... maybe try a search for it, I think boB replied... hth.. off to town for grits...
I tried searching for the number but couldn't find anything.
It sure is a lot of KWH's something is adrift....
(https://farm2.staticflickr.com/1601/25336674231_2a41209c39_o.jpg)
Kurt
My standard non upgraded software unit is running perfectly! ;)
found one of the references I remembered....
http://kb1uas.com/mnsforum/index.php?topic=2693.msg25511#msg25511
Thanks Westbranch,
Yes I found some posts on odd numbers turning up. though not the same numbers. Though I think it could be along the same lines.
Russ, the software update is worth it for the online logging (my midnite) I'm pedantic about every little detail. It's nice being able to log in and see how low the batterys got over night and scan back over the days with it all plotted out as a nice simple graph.
One thing with midnite products is they are always improving things. I don't get my jocks in a knot over small hiccups. As 99% of the time they are small things that don't really effect the foundations of what the controllers is there to do (charge your batterys) The response time to sorting out (real issues) like a dead controller or one that isnt doing the basic functions correctly ...changing your bank . Is always very fast.
They really do back there product up 110% .
On that note Perhaps I should post this issue some place on the forum that will get more love (views)
Kurt
Hey Kurt,
I fully understand that, lol.
But I have no Iphone and no mobile service here :o
Lol.
Some parts of Australia are not yet in the 21st century and our phone carriers care less! ::)
Yes Russ, I don't have mobile phone reception at my place at all. You have to drive up the road a few km to get patchy reception.
As long as you have internet (I take it you do as your on the forum :)) Doesn't matter if it's ADSL, cable, Satellite, dial up what ever. That's all you need. Then you just need a Cat5 cable from your classic a hub.
The main reason I like it is for the past 5 years I have been living between two homes. It's nice to be able to keep tabs on the offgrid system when your not on there for a week.
For yourself it's just handy to have a record of your system to look back on. As your there all the time and your classic is near the house.
Anyhow I have updated my classics probably 10 times over the years and there is all ways little teething issues each time with new firmware but over all it just keeps getting better. No way I would wont to go back to the very early firmware that came stock on my classics years ago. As you would loose so many features and fixes. There has been a hell of a lot of features that people take for granted when they buy a new classic now that is shipped with later firmware over the years all the features have been added with firmware updates.
Kurt
My lappy is running windows7. Only because I could not get XP on the new machine.
Best to bring yours if it has a suitable downloaded update. I am not sure if what I downloaded from the website is complete.
Have to go to Bundaberg this week to get the A/C unit and also arrange for 4 more L16 trojans.
Internet is satilite and only 10gb, do have dial up but we will not talk about that, LMAO!
MN reg is on the way to the dunny so easy to monitor from the throne with a pair of binoculars ;D
Got my WBJ hooked up and all working fine.
SOC flicks up every 5 seconds or so.
Since I added the other 435 amp hours of batteries and WBJ the reg stays in absorb and bulk a lot longer.
The standalone load when switched on (8am) will draw the bank down from 95% after night-time to around 85% in late afternoon (intermittent cloud).
Around 3pm I turn off the standalone load and just leave 1 freezer connected through the inverter.
Most nights the soc reads 99%.
I really need the other panels up and the second reg online to finish the system off.
Quote from: Resthome on January 22, 2016, 06:27:16 PM
Quote from: crunnells on January 22, 2016, 05:57:30 PM
Resthome: Windows 7 on all 3 laptops. I'm not sure what difference the OS would make, but maybe? Last time it worked was on a Windows 7 machine (well, a Macbook running Fusion with Windows 7 installed, but I digress). The way the problem occurs is that it detects COM8, starts uploading the update, but never gets past 0% and drops out with a "bad usb" error. It fails on both the Classic update and the MNGP update.
Well there are different instructions for different OS. But I've had mostly good luck with Win7 but better luck with Win8.1 and no luck with Win10. I'm at a lost since you say it starts the update and shows the 0% and then the bad cable message. Usually if you get that 0% the connection was made. All my failures have be Com8 busy or not available.
Maybe boB can decipher what is being checked when the "bad cable error" is displayed.
Ryan had said the new Beta Updater for Win10 was suppose to work with all OS but I'm not sure that is the case. It would be nice if it was and you could give it a try. I think you have to contact Ryan to get a copy of it anyway so you might PM him and ask if it will work with Win7 (maybe - maybe not).
http://kb1uas.com/mnsforum/index.php?topic=2753.msg26052#msg26052 (http://kb1uas.com/mnsforum/index.php?topic=2753.msg26052#msg26052)
Okay finally at the boat long enough to try the 2097 Classic firmware using the production version and the WIN 10 loader. Connected the Classic USB and started Win 10 loader it said Classic found on COM4. Selected Classic 150 and uploader proceeded to 100% Classic was just showing GOT COM ? during upload. Clicked on OK after the 100% sat there for a few minutes and that dialog closed. Main app was telling me to select my model, again waited for a few minutes and app closed on its own. Unplugged USB and rebooted Classic using VMM the Classic Mode selection came up with RED com light lit (don't remember that from before but it's been 9 months since last update with Win7). Completed VMM and RED com LED turned of and Classic now said 2096 and network 2097. I did not attempt the MNGP because I was already at 2054. So do not know if there is a problem with the MNGP firmware updates that other people had. But the Classic firmware was successful using the Win 10 loader.
Will check the Classic out for network issues when the sun comes up tomorrow.
Guess that this kinna belongs here;
Downloaded Classic FW 2096 today, Exported Registers, using the LA, and
Updated the MNGP first, and the Classic 150 second. All things appeared normal, and the Classic & MNGP do work. It is just that none of the FW in the Classic has changed from the prior version, Cl 1849.
Cl version 1849 does NOT exist on the Win 7 computer that was used today, and has always been used for Updates to Classics.
25 minutes of screwing about, but at least, luckily, both the Classic and MNGP still do work, and guess that this IS something. Had hoped to actually advance FW versions ... wonder just what I did incorrectly. It HAS been about 2.5 years since the prior Update attempts, and that attempt resulted in two Bricked Classics, ... was happy, then, to just get back to Cl 1849. This particular Classic was not one of those previously Bricked.
Ideas? Thanks, Vic
Hi Vic, I have never updated the MNGP first, I have always done the FW version for the Classic first and then the MNGP...
Have you tried a second attempt to install 2096 on the Classic?
Quote from: Westbranch on September 17, 2016, 07:53:22 PM
Hi Vic, I have never updated the MNGP first, I have always done the FW version for the Classic first and then the MNGP...
Have you tried a second attempt to install 2096 on the Classic?
Yeah I have also done it in that order also, but I'm sure Ryan said it shouldn't matter.
Vic.. need a lot more info from you. Did the MNGP update? Did you wait until the DOS cmd window closed after each update? It's not complete when you get the first Sucessful message. You need to wait approx 2 minutes until the window closes itself.
Best advise is to follow the Win7 firmware instructions step by step and in the exact order. If the Classic USB driver is install on your computer you should not have to do that again. You must use COM8 for Win7. Assume you see the Classic connection on COM8 in the Win7 Device Manager?
Hi Chaps,
Erik, at least for a while, Ryan was recommending Updating the MNGP first, this is why I did it first.
Since the first UD did not work, felt that would be another total waste of time to try again, so did not ...
John,
The Cl is 1849, Network 1830, and the MNGP is 1821.
Update SO infrequently, did just notice that the actual DATE of the FW is listed in April of 2014, guess that this is the date that the FW was last Updated in this particular Classic -- #3677(?).
Seemed to me that about 99% of the Win 7 Update instructions were about just trying to get Com 8 setup and work...
I did follow the instructions, and there is a bit of a difference in opinion about when to plug in the USB cable and Power up the Classic twix the GUI, and the Loader ... the Loader instructions appear to be correct.
YES, did wait for the MNGP Update screen to close and return to the GUI screen (took about 30 seconds).
YES, did wait for the Cl Update screen to close and return to the GUI -- took about 5 min 30 seconds.
SO, if the dates noted for FW Status pages on the MNGP are the dates that the FW was implanted into the Classic, then, NO, none of the FW was loaded.
This particular Classis was Updated at least once, probably twice ... successfully.
Have always let the Firmware find the correct place for it to be loaded onto my computer ... have made NO attempt to keep the GUI, and the FW in some sort of special Folder, or anything.
Some of us DO really wish that trying to Update the FW on the Classic would be even easier, and even less subject to apparent whim of things in the Universe which appear to not matter until after the fact ...
Perhaps in 2.5 more years. will a t t e m p t to, perhaps try to perhaps again begin to try to a t t e m p t to begin attempting to perhaps Update the FW once again, perhaps.
Bottom line: am back up and running with Cl 1849 (perhaps never, ever updated anything, but the drill was fun, anyway).
Thanks for the ideas, but, for now, guess that all of this is moot.
FWIW, Thanks for the ideas, a bit frustrated - Vic
Morning Vic.... I really FEEL your frustration :o :-\ , having as you guys know too well, my (same) issues with updating my Classic...
as to order, I used the step by step step instructions, I thought, multiple times.... I eventually had them on screen, jumping back and forth to the GUI as I did the successful implant.... frustrating as H___! but it finally went in... :)
From memory, Yes, the plugging in of the USB CABLE has conflicting instructions, The long version and what the GUI says, but I can not remember which is the successful one...My mind was swirling when I finally got it...
Vic,
I can only image a few reasons why you are not see updated firmware numbers for the Classic or the MNGP. Check the c:\Midnite dir and look for the Readme.txt file. What is it showing as the last revisions numbers?
If the firmware is actually counting up the percentage in the cmd window then it is loading something. So it doesn't sound like a connection problem. You can plug the USB cable into the Classic with the Classic power off and when you start the GUI and click on Classic Model you have you can then turn the Classic power on and it should connect and start showing the Pecentage done. If you check the Win7 Device Manager and look for the COM ports you should see the Connection on the COM8 port. If you are getting this far what is showing on the MNGP as the update takes place.?
Almost seems like you have the wrong firmware files. You can run the UNINSTALLL file in the c:\midnite direct to uninstall all the old files then reload the latest Firmware files from the Midnite web page.
You should really try to resolve this and get to the latest firmware. They were a lot to fixes since 2014. Not many this year.
Hi again Erik, and John, thanks for the comments.
John, did search for Update files on the computer used for yesterday's Update attempt. Cannot find FW 1849, just 2096, which was downloaded yesterday.
YES, the Loader says something like "open Com8", or similar. The percentages of progress did increment for both the MNGP and the Classic 150 Uploads.
The Classic Update took about 5 minutes, plus that 5:30 minute wait for the Loader to close its screen. The MNGP took about 12 - 15 minutes, but its Loader screen closed in about 30 seconds ... sure DID look like it was loading something.
Will poke around a bit more.
YES, I have really wanted to Update all the Classics here, to the latest FW. Just that my past experience is that trying to Update Classics can be a real problem ... have NEVER been successful Updating, after Cl FW #1849. So am a bit gun-shy. DO feel lucky that the "Update" of yesterday did not end with a Bricked Classic.
More Later, thanks for all the help. Vic
Did some more poking around.
Did Save the 2096 FW -- the choice from Windoze was to Save or Run. Since the Classic was not near the computer, and was not ready to Update the FW, just saved it.
Did not realize that the "Run", was to run an Installer, not the Updater.
So, today, did Run the installer, and that part is probably ready for the next try at Updating the FW in this particular Classic, again.
And there were several, various older FW remains in the MidNiteSolar Folder, which could be an additional issue ...
Thanks Erik, and John, re-reading the Installing FW instructions has helped ... it has been SO long since the previous try at Classic FW Updating ...
More Later, Thanks! Vic
Vic,
Sounds like you are on the correct track. Yeah the save doesn't run the installer. So you successfully installed the old firmware. Good Luck, I think you have solved the issue. Check the Readme and look for the revision numbers after the installer is run.
Thank you again John!
I should probably Edit the whiny Posts, as this was all my problem.Should do Updates more often, to help my recall of just how to do it.
Thanks John, and Erik! Vic
Wow, if we could only get a Linux firmware updater.
Linux Mint bootable CD or thumb drive, boots right up, and finds USB ports, wi-fi radios and everything
Easy to select boot from CD, and do an update from Linux
Quote from: mike90045 on September 19, 2016, 04:58:36 PM
Wow, if we could only get a Linux firmware updater.
Linux Mint bootable CD or thumb drive, boots right up, and finds USB ports, wi-fi radios and everything
Easy to select boot from CD, and do an update from Linux
Mike, you really like linux, do you feel it's a fix to all problems with updates?
Walt
Quote from: BobWhite on September 19, 2016, 05:09:12 PM
Quote from: mike90045 on September 19, 2016, 04:58:36 PM
Wow, if we could only get a Linux firmware updater.
Linux Mint bootable CD or thumb drive, boots right up, and finds USB ports, wi-fi radios and everything
Easy to select boot from CD, and do an update from Linux
Mike, you really like linux, do you feel it's a fix to all problems with updates?
Walt
There used to be a Perl [cross platform programming language updater] but I can't find it back.
At least in most instances Linux upgrades are not known for deliberately breaking other peoples software. Mister Gates and his minions seem to do this as a matter of course. One big issue is the demented way M$ handles ports and devices. Linux just gives them names like files so easy to sort out where the device is
I believe that a bootable minimal Linux "BusyBox" live CD /USB drive with the installer on it would be the answer to many problems and the entire process could be scripted and done automatically when it boots with useful information displayed while it does it. It just can't be done by myself as I am not skilled in the scripting / coding arena. Just add the current upgrade files to the existing image for the CD / thumbdrive, name it appropriately and put it where folks can get it.
Ok, that is my operating systems diatribe for this day.
I suggested this some time ago but it never got traction.
Tom
Quote from: TomW on September 19, 2016, 05:41:57 PM
Quote from: BobWhite on September 19, 2016, 05:09:12 PM
Quote from: mike90045 on September 19, 2016, 04:58:36 PM
Wow, if we could only get a Linux firmware updater.
Linux Mint bootable CD or thumb drive, boots right up, and finds USB ports, wi-fi radios and everything
Easy to select boot from CD, and do an update from Linux
Mike, you really like linux, do you feel it's a fix to all problems with updates?
Walt
There used to be a Perl [cross platform programming language updater] but I can't find it back.
At least in most instances Linux upgrades are not known for deliberately breaking other peoples software. Mister Gates and his minions seem to do this as a matter of course. One big issue is the demented way M$ handles ports and devices. Linux just gives them names like files so easy to sort out where the device is
I believe that a bootable minimal Linux "BusyBox" live CD /USB drive with the installer on it would be the answer to many problems and the entire process could be scripted and done automatically when it boots with useful information displayed while it does it. It just can't be done by myself as I am not skilled in the scripting / coding arena. Just add the current upgrade files to the existing image for the CD / thumbdrive, name it appropriately and put it where folks can get it.
Ok, that is my operating systems diatribe for this day.
I suggested this some time ago but it never got traction.
Tom
You ok tom! Well put and I know my son would be at your side as that's all he talks about with computers. I'll look into it somemore and if it is an answer;;; let's hope it gets done!!!
o,,, by the way tom , I'm still having issues but will post properly ;-)
Walt
well I don't think there is a mint to be made BUT I believe the serial numbers of Classics sold is >= 30,000( mine is > 29,000)... at $1.00 per copy sold to 10% of the owners== ~ $3,000 Is that too bad for a day or so of programming?
Somebody out there that frequents this board must be able to pull it together, eh?
I'd gladly pay $5 to the Linux updater fund, to get a reliable updater that doesn't have a 20% chance it will brick my controller.
I currently keep an XP laptop, but it's battery is extinct and while the win 10 updater might work, i'm at W8.1 and
don't plan to move. I boot my workhorse laptop into linux mint all the time for work, works all the time, just a couple programs in windows that I need ( Visio among them)
Agree with all, who note that if Updating a Classic was even easier, it would be a plus. Although, seems that recently, there have been very few Posts about issues with Updates.
However, just to reiterate, the recent problem that I had, was entirely of my own making ... very much a RTFM kind of deal.
Apologize for my W H I N I N G about errors on my part, and essentially blaming MidNite Solar for my indiscretions.
The Classic here really did get the FW Implant, it just happened to be the same one that had been overwritten.
Easier, IS better, as is taking responsibility for my oversights. FWIW, ... Sorry MN Crew for any aspersions that I might have cast your way.
Thanks again Resthome, John for the hand-holding, and to Erik. Whiny Vic