[solved] there really is a important error in the SOC%

[cybermaus]

Sorry, me again.

day before yesterday, I was surprised at the Classic again, the SOC% had shot up unbelievably much.
But I felt I had reported often enough, and decided to not mention it and keep my eye on it.

However, yesterday late evening (already dark), SOC% was at 74%. This morning it is at 99%.
Take my word for it, there was no bright sun overnight 
Also, it is at 23.9V with only 6Amp. On a 460Ah battery also a hint the 74% is more realistic.

I did activate auto-eq (using the local app) but did not notice it going to 100% as result of that. Also timing is wrong for that, if that had caused it, it would have counted down all night and be lower then 99%. The 1% loss hints it may have reset to 100% only an hour or 2 ago. Alas I am not on board, so I cannot check if the 100% may be blinking on the classic itself.

Something is up with the mechanism that resets the SOC%. And as I use it to activate load, it is very important to my use case.
And if I look back, I think my other weird experiences also are probably related to this.


Edit: I went and checked: the 99% was *not* blinking. So it was not some accidental "turn off classic" event.

[Tons001]

Mine does that when the charger kicks in overnight if the battery voltage dips too much. My whizbang jr will count up to almost 100% because I cut the absorb time short from the charger. Not sure if that is the same thing you are seeing or not.

[cybermaus]

No, most definitely the charger did not kick in. Not only is the charger off (I checked) but I would have notices the higher battery voltage during charge in mynidnite.com (checked that too). And as mentioned a higher battery voltage post charge.

It resets to 100% at (for me) unpredictable and undesirable moments. That I am now sure of.

[Tons001]

Bummer. My is working flawlessly since the 1779 firmware update.

[Resthome]

cybermaus

So you don't feel alone. When I first installed 1779 I had some very strange resets of SOC back to 100% during the night. I was only there for two night so was not able to verify or see if it repeated or if occurred around the 23:59 data save or the Auto Restart that I had it set to. Unfortunately to save on the battery bank I do not run the LA at night and I have no Internet connection for MyMidnite. I think I disable the Auto Reset before I left but not sure. Also using Skip Bulk so I don't overcharge when gone for weeks at a time. I was also trying to figure out the Net-Amp reset as it did not match my Link 10. After the thread on SOC Questions boB confirm the two were not tied to each other and used separate counting methods. Also using the LA 0.3.52

I'll be headed back up tomorrow for 4 days, but I also have a control board to change in the Classic to see if it resolves my Float Times being zeroed out 256 days in the past. Will not be able to verify if that is fixed for 256 days so it's just a try this kind of thing.

I also have one of the very early WBjr and it has a long lead going to the Classic from the Shut location. I understand a component was changed in latter WB JRs, believe it was a resister. So there a lot of variables. 

I'll post back my findings with SOC next week,

[TomW]

Sorry, me again.

day before yesterday, I was surprised at the Classic again, the SOC% had shot up unbelievably much.
But I felt I had reported often enough, and decided to not mention it and keep my eye on it.

However, yesterday late evening (already dark), SOC% was at 74%. This morning it is at 99%.

I had suspected some anomaly with SOC for awhile. A couple times I have seen quick, unexplained 100% values from lower values just too quickly.

This A.M. while under a couple hundreds watts of Solar charging after a night of extreme deep discharge with the SOC at about 60% (don't ask). Suddenly it was at 100% in a few minutes and  less than a KWH of incoming recorded into a 450 AH 24 volt bank that is quite tired.

Just because I saw it happen and it is obviously wrong in my case. I am using FW 1758. I thought I was current?

Tom

[toothy]

I'm having the exact same issue as Tom, with the exception I'm only down around 82% when it went back to 100% instantly.

In bulk, a few hundred watts in from panels, firmware 1779. I took a screen shot if it would be of any use.

Later
W

[Halfcrazy]

Could it be that any of these cases coincide with the Classic rebooting?

[TomW]

Could it be that any of these cases coincide with the Classic rebooting?

Not in my case. My local logging would have shown the KWH value reset and it didn't.

Tom

[cybermaus]

Could it be that any of these cases coincide with the Classic rebooting?

I was wondering that. Is there any place I can see the runtime?

For now, I am assuming it was not a reboot, because on a reboot the SOW% goes to blinking. I already seen it for certain twice that it shot to 100% too soon and was not blinking, and I have at least two more suspected events. (if I reread my previous reports)

But if You can tell me where I can see the current runtime since last boot, I can make sure to check that next time.

[cybermaus]

Hmm, I may have seen a link with EQ.
Not sure if it is always linked, but it was linked this one time.

Late this morning it reached FLOAT, and this afternoon I put it in manual EQ. But maybe the sun was already to low, I do not think classic was able to finish it. Anyway, several hours later (when the 1 hour EQ should have been long finished?) when it was already dark outside, it was still reading EQ MPPT. Also, as power use was apparently high this afternoon, the SOC% had dropped back to 96%

So I pressed the "stop" EQ button myself. Local app showed went to RESTING, and the SOC% shot to 100% again!

[boB]

Hmm, I may have seen a link with EQ.

.......

So I pressed the "stop" EQ button myself. Local app showed went to RESTING, and the SOC% shot to 100% again!

Yes, that makes sense.  Whenever the Classic goes from EQ or Absorb to Float, it will reset to 100% automatically.

You forced a Float by stopping the EQ.  It could have either gone to Absorb if it was in Absorb when you started the EQ or it would have gone to Float if it was in Float before you started the EQ and then forced the EQ to STOP.

I suppose that if one "forces" a float by either pressing force float or stop EQ that it ~could~ hold off resetting to 100% SOC but that is the way it works right now.

So there are only 2 ways the SOC will jump to 100%...

One is that it goes to Float for whatever reason...  It is assumed that the Classic goes to Float because the battery is Full.

The second reason to jump to 100%  (and then count down from there) is when the Classic resets.
THAT we are working on still.  But we are definitely working on it.

BTW, there will be some cases where the newest code up on fusion.midnitesolar.com  will actually FIX some of those resetting issues !   It fixes the problem where the Classic resets when you are reading offline data logs either with the Local App or MNGP (graph display mode) while the Classic saves the data logs every 5 minutes AND also if you are sitting in the wind power curve graph while the Classic saved the minutely data logs every 5 (or 10) minutes.

I'm sure that at least some of the resetting has to do with the two data reading and writing to/from logs coinciding at the same time.

That code, if you want to download it, is http://fusion.midnitesolar.com/MidNiteSolarUpdate_1794_3-12-2014_v4.28.exe

You will want to do a VMM after installing it though because there is a new feature that will stop charging (reason for resting = 36 and 136)  if the battery temperature goes above a new modbus register value and there is not guarranty that that value is going to be in the correct range at first until initialized.

More updated coming if you want to wait.

boB


boB

[zoneblue]

So there are only 2 ways the SOC will jump to 100%...

One is that it goes to Float for whatever reason...  It is assumed that the Classic goes to Float because the battery is Full.

Bob, in days between bulk, what happens there. While in float (non float mppt) and WBJr EA is met might be another case for 100% ?

[boB]

So there are only 2 ways the SOC will jump to 100%...

One is that it goes to Float for whatever reason...  It is assumed that the Classic goes to Float because the battery is Full.

Bob, in days between bulk, what happens there. While in float (non float mppt) and WBJr EA is met might be another case for 100% ?

Ending Amps should not have any effect on SOC% while in Float or EQ.  Only Absorb.

"should not" of course is the phrase here...  If you do find some interaction, I would be
very surprised but I have been surprised before.

I have a feeling the unit has reset for some reason or gone TO float.

boB

[cybermaus]

The second reason to jump to 100%  (and then count down from there) is when the Classic resets.
THAT we are working on still.  But we are definitely working on it.

You are working on preventing reset. I understand finding the reset causes is not an easy fix and may take a while and a few tries.
Can you at least make it so that after a reset / reboot it automatically goes to a blinking version of the last known value instead of a solid non-blinking 100%(as suggested in another thread)

Also, is there a place to see the current runtime, iow, when it last reset?

Thanks