Rev 1758 fails to install properly

[mofawayesu]

I tried installing 1758 yesterday (updating from 1735), and while everything looked to be normal, the Classic is stuck in Sending Data mode after restarting the Classic.  The Local App shows that 1758 is installed, but it is blinking yellow indicating partial shading panels' and charging does not occur.  It is correctly showing the input voltage, so that much is working.

How do I roll this back to 1735 (or some other working firmware)?

Thanks!

Mike

[zoneblue]

The firmware updater is pretty fail proof. Id be inclined to start afresh and install it again.
Do you have a copy of the instructions? They are here:

http://www.midnitesolar.com/firmwareReport.php?firmware_ID=3&firmwareProduct_ID=1&act=edit

bottom of the page.

One thing the instructions say the dos window will close. I find here that that takes an age, after it says first 100% done, then completed. I always wait for it.

[mofawayesu]

Thanks Zoneblue,

It's working!  I actually reinstalled three times, but always with the same result.  The trick?  Mashing harder on the left/right buttons for the VMM!  I've had times before where my first keypress didn't register in navigating menus, so this time I mashed them pretty good, and presto, all is good.

...except - the cooling fan runs constantly!  FET temp is currently around 53.5c, pcb 43.5, so I expect the fan to be on now, but this morning when I got finally got it running, FET was around 45 and it was blowing cold air from the vents.  Even now, the temp is climbing slowly as it's pushing more amps.  Sensor bad?  Seems suspicious that it happened at a firmware change...

[SolarMusher]

Re-open the Classic, it might be only your MNGP data wire that is not correctly routed in the Classic.

[mofawayesu]

Hi SolarMusher,

Good idea, but that wasn't it - I opened it up, and have left it open for now until I find something.  I found the internal fans (not the turbo) DID go off sometime after the controller went to Resting.  I wasn't around when they turned off, but they were off a couple of hours after dark when I checked.  They stayed off overnight, but turned on when the controller woke up this morning.  Currently, FET temps are 45.1, about the same as I saw them last night during resting.  That sounds fishy to me - why were the FETs that hot when the controller was Resting?  Even now, it's only pushing 4.3 amps in Bulk mode and that sounds warm to me.  The other interesting thing I've noticed is that FET and PCB are exactly 10 degrees different - and I mean exactly.  When one moves, the other one moves as well.

Now mind you, this all started up after I had the cover open AND updated the firmware at the same time.  It's possible that the MGNP cable damaged something somewhere along the line when I was replacing the cover and it's not a firmware issue at all.  I did find a small smidge (1cm long, 1mm thick)of plastic on top of the Ethernet connector that is about the right size to have come off of the small power transistor about 4 inches directly above, but if it's a cooling problem, I don't see how that could have affected anything...

Mike

[Halfcrazy]

You are probably gonna want to call in and talk to Mike or Mat I suspect some how the turbo fan may have got shorted. They can help diagnose it for you.

[mofawayesu]

Ok will do.  At one point early on, all fans were on including the turbo, but that only happened the once, but at least the turbo was operational at that point.

Thanks!

Mike

[mofawayesu]

It's fixed.  Just a note for others who might be searching the forums over this issue.  It turned out there was a modbus register that somehow had been incorrectly set and wasn't getting rewritten by the updates.  Changed the register value, and the fans are now behaving normally.

Midnite tech support is amazing!

[Nashville]

I can't get mine to work either. I have 2 classics and both crash when sending data. I pushed on the buttons harder too. I have updated before without issues.