Its dead after update

Started by MikeJ, April 16, 2014, 04:28:22 PM

Previous topic - Next topic

MikeJ

Hello all

So this AM I was updating the classic and everything was going along just nicely and then on the dos box sat at o% for a very long time 1/2 hr or more so I powered down the classic 150 and it never came back  no screen on the MNGP display and only 1 red led on the classic no fans no nothing.   Might add the the display looks like ALL the led are lit. Any ideas whats going on here

ws trying to go for the update from 10/4/2013 to the latest and greatest

Thanks
Mike 

Halfcrazy

Mike
It sounds like there was a glitch during the update. I would try it again. Basically the firmware is erased but not installed at this point so you should be able to get the new firmware to go

Ryan
Changing the way wind turbines operate one smoke filled box at a time

MikeJ

Rayn

I have tried several times and in the dos box it says the there is no response from the classic. I will try it again in the morning

Thanks
Mike

boB

If it made it die, then it did communicate with the classic and erase the app so that is good in that it communicated.

I would try another USB cable.

If that does not work, might need to try another computer.

If no go, then we will just have to help you out in another way.


Really sorry for the inconvenience
K7IQ 🌛  He/She/Me

Resthome

Try running the uninstall from the MidNite directory and reinstalling the update from scratch.
John

10 x Kyocera KC140, Classic 150 w/WBJr, Link10 Battery Monitor, 850 AH @ 12v Solar One 2v cells, Xantrex PROwatt SW2000
Off Grid on Houseboat Lake Don Pedro, CA

philb

#5
Sounds like you have a bad usb line to me. It may also be that you'd inadvertantly skipped a step it setting up the upgrade.
I get comm 8 ready, start the dos update box for mngp, then plug in the usb line and give power to the classic.
The zero starts moving up scale. I use the same proceedure with the classic. Hope this helps.

MikeJ

Hello All

After several try's i got it figured out ;)  It was a bad USB cable after trying 4 of them found a good one and all is well !!

Needless to say all the bad one are in the trash.

Thanks for all the help
Mike

TomW

Quote from: MikeJ on April 17, 2014, 10:19:26 AM
Hello All

After several try's i got it figured out ;)  It was a bad USB cable after trying 4 of them found a good one and all is well !!

Needless to say all the bad one are in the trash.

Thanks for all the help
Mike

Mike;

One thing that can catch you is some USB cables are only intended for charging devices and not for communication. The ones  I have seen are not marked as such.

Just saying.

Glad you got it sorted out.

Tom
Do NOT mistake me for any kind of "expert".

( ͡° ͜ʖ ͡°)


24 Trina 310 watt modules, SMA SunnyBoy 7.7 KW Grid Tie inverter.

I thought that they were angels, but much to my surprise, We climbed aboard their starship and headed for the skies

MikeJ

Mike;

One thing that can catch you is some USB cables are only intended for charging devices and not for communication. The ones  I have seen are not marked as such.

Just saying.

Glad you got it sorted out.

Tom



Never knew there was a difference.  Guess you do learn something everyday!!!   Maybe someday this post will help somebody out someday


Mike

boB


MikeJ,   which cable was bad ?  Was it one that came with the Classic ?

I think that sometimes they aren't bad but just too long of cable for some
combinations of computers and Classics.

boB
K7IQ 🌛  He/She/Me

MikeJ

Bob

Yes the one that came with the classic was not working. What I used that did work was one from a portable hard drive about a foot and a half long.

Mike

Lars-Olof Holm

I had a similar problem yesterday, , after trying to update to "Firmware Revision Number: REV 1849".
I used a HP laptop with OS Vista Business. The reason was that OS W8 is so complicated, because the unsigned driver and the change to port 8 etc. It,s easier to do this operation in Vista.  After i had tried a number of times with the  "Vista Computer", there was only a red led light - "ERROR" at the Classic. I tried to make a  factory restore (VMM), but it didnt work, only the red led was lit, both before and after the VMM.

Then I changed to another laptop with W8. I notised that there was a sound when I put the USB into the computer. And I could identify  Bootloader 1.06, but there was a problem with the driver. Then I installed the driver and had to defeat all the attempts from W8 to stop me from installing the "unsigned" driver.

After I had sucessfully installed the driver, I changed the com port to 8. Then I made a new try and started up the software to upload the new REV and suddenly the computer and Classic started to communicate.
The Classic was revived!
Note: I only used the USB cable provided with the Classic, in the both cases, but different laptops..