Classic and equalising

[dapdan]

Midnite,

Could you please advise me the best way to go about confirming whether or not the classic has finished its equalisation of battery. I have noticed that in the logs one can see how long the batteries were in absorb. It would be nice to know how long they were in float as well if that information was not already there. I would like to see a count down timer for equalise as well as absorb (so when you set it to say 120mins you could know much of that time you actually spent in the state). I think this may help you decide your course of action in order to achieve complete absorption or equalisation. One may decide to utilise a generator, the grid or even get more panels so that one maybe able to complete these stages.

Cheers...
Damani

[boB]

Hi Damani !

If you go into the CHARGE menu, then CHARGE TIME  and notice the soft-left key is VU   for View
Timers, you can view where the Absorb, Float and EQ timers are at.  When in there, pressing
the soft-left key again toggles between  Hours:Minutes   to  Minutes:Seconds view so you
can watch the seconds go up or down.  If counting down, the function is getting done.
If counting UP, then it's MPPT'ing and the battery is below the set-point voltage.
The last couple of software revs at least show float time.  The new stuff coming out in
around a week or so will data log a years' worth of daily things such as Float Time.

boB

[dapdan]

boB,

I follow you and even went to my classic to go through it. I can understand that one would see the count down in real time. What I didnt see is how long it was in aborp or equalise at the end of the day. I went in log and one could only see the float time. When I went and viewed the timer vu it just showed me what the set points were so I am not sure how long an absorp or equalise time I was able to complete for the day. Will the next revision give us a history log for absorp time as well. Additionally it would be nice to be able to view this on the local/internet power dash board. I reckon this could help a user or installer see what is going on during the course of the day as it relates to absorption and equalise.

Cheers...
Damani

[boB]

During the day, if the Classic finishes an Absorb cycle, it will go to Float and/or Float MPPT so if it does that, then the Absorb finished.
If it didn't finish absorb, the timer value should be visible in the VU (View) menu until the evening. 

If and EQ finishes, the message "EQ DONE" ~should~ alternate with float/mppt on the main status screen until a button is pressed or the next morning happens, whichever happens first.

Data logging is coming up in a week or less so watch for this.  I doesn't store the absorb timer but you can see the charging stage the Classic was in at the sample times in the recent history.  The day by day history could eventually store the counts I suppose.  That might be a good addition actually.  Yeah, I like that !

I agree that the local app (over the network/internet), should display timers.  If it doesn't now, it will soon I think.

Auto EQ is also coming up in the next revision which will be able to extend over multiple days if it doesn't finish in one day.

Thanks for the ideas !

boB

[dapdan]

boB,

Your very much welcomed. I look forward to these new additions so I can better analyse what has taken place during the day when I am absent for my systems and others.

Cheers...
Damani

[laszlo]

Dapdan -- as boB says, the local app displays the float time. But it is the cumulative value.

I use the local app to chart the battery amps and voltage so I  can tell how long my system was in absorb and in float.  The local app is free - all you need is a crossover ethernet cable (or a hub and  a straight-through ethernet cable), and a PC or Mac.

[dapdan]

Laz,

There is one flaw in your reasoning. Not every system is able to run or support the local app so a history for the absorp and equalise timers will still be very useful. I have one client for instance, that although I have the classic hooked up through the local network via a wireless bridge it is not stable, it locks up frequently and requires a hard reset of the classic every time. This has happen to the extent that the client doesn't use the local app. Midnite I will forward detail on the router and wireless bridge in the local app section. Further more the graphing in the history doesn't give the correct scaling for me to adequate assess the time spent in equalise or absorp so that I can make design decisions. I do take your point that one can estimate the length of time from the qraph though.

Cheers...
Damani