Hi all.
Recently got my classic back from repair, it had been reloaded with 1933 MNGP/1923 Classic.
I wish to put the 1849 set back on it as there are numerous issues I'm seeing with the newer firmware. Many are just annoyances:
Forgetfulness - Change a setting, sometimes have to go in and set something several times for it to stick
"Looping" when changing values - If you don't stop periodically while changing a value, it will "loop" back to some arbitrary value between where you started and where it got "lost"
Very laggy MNGP comm, constantly seeing "Got Comm?" and other evidence it's not keeping in sync with itself (such as ignoring bulk/float tweaks etc, only to return to that menu to see "OK" stuck in the appropriate field)
But the straw that broke the camel's back is inconsistency in Ah remaining and % SoC. It terminated the charge at "100%" when the Ah counter was still a fair ways behind it. See pics below for details. (Yes, it is charging in those pics, I forced a second bulk run before taking the pics).
Are there any gotchas to look out for in attempting to reflash it with the older firmware?
Steve
Steve, any bugs that you have found in the newer 1933 firmware are very important that we fix.
Slow communications and/or Got Comm I understand and am looking into.
I REALLY appreciate the input !
But, I don't see what the problem is from the Remaining Amp-Hours you are showing here ?
What is your battery temperature ? What is your setting (MORE) for the Battery temperature
capacity adjustment ? If it is 0.0%, then maybe I could see a problem. If you could please
expand on this I would greatly appreciate it.
Which Ah counter are you referring to ? If it is NET Amp-Hours, that has no real bearing on if
the battery is at rated capacity or not. Also, NET AH does not take efficiency into account or
anything.
>>>>Forgetfulness - Change a setting, sometimes have to go in and set something several times for it to stick<<<<
Which menus or values did you see ? What I ~think~ is going on in some cases is relative to the "Got Comm?"
problem. The Classic does a lot of limits for you and if the MNGP is not communicating with the Classic, it does
not get limited and the MNGP will do its own limit which may be the rollover you are mentioning.
You ~should~ be able to go the opposite direction in the MNGP to get back to the top or bottom
of the value you were changing. If there are particular menus that are worse, I can try to
limit those in the MNGP also a bit better. The best way is to improve communications response time of course.
You can usually find older firmware versions here...
http://fusion.midnitesolar.com/
Nothing necessarily special about downgrading except to try and do the MNGP as well.
Now I gotta try and see what you mean about the capacity vs. SOC% problem, first.
boB
Quick reply, I'll elaborate more shortly, I'm presently at youngest's birthday party waiting for a table... LOL
The discrepancy is in the SoC% and the Capacity remaining Ah count. It terminated the charge when the percentage reached 100%, but out of 235Ah total capacity, it was reading well short, 218Ah. They used to track each other (seemed like before, percentage was calculated directly from (SoC/Capacity*100)? But now they don't track like that, and as a result, the charge stopped short when it should have still been absorbing.
I'll get more info on the setting cycling issue when I'm back at home... I believe you're correct, it's as if the MNGP "gets ahead of" the classic, and maybe is receiving back the actual value in the classic, and as a result, is setting it to an "earlier" value that has already gone by. Slowing down and pausing while making large changes works around the problem. It occurs both with and without using shift.
Hopefully that helps for now...
Steve
Sounds to me like your battery temperature is affecting the capacity of the battery bank which would be normal.
Yes, quit reading/writing and enjoy the birthday party !!
Also, go to WB Jr. menu, SETUP--MORE and make sure that battery temperature is set to 25.0 degrees C
and if you don't want temp-compensated capacity, set the percentage to 0.0%
Hmm ok... Back home now... looks like that might have been it... It was set to 1.0%. When I changed it back to 0, it went back to the full 235Ah. Not sure why it had been changed, maybe something I had done inadvertently. Ok so no sweat there.
Thank you much, good sir.
So all that really leaves then is some comm issues between MNGP and Classic, which you've already stated as a known issue...
One other question regarding the firmware... I'll take that over to the other thread tho instead of putting it here since it's technically off topic for these posts.
Thanks again,
Steve
Steve 1% of capacity change per degree C is default so that is how it would be set from the factory
Ryan
Quote from: Halfcrazy on February 08, 2015, 06:11:29 AM
Steve 1% of capacity change per degree C is default so that is how it would be set from the factory
Ryan
Oh, OK. I thought the VMM set it for 0.0% ?
boB