My 2 new 6000XPs are set to charge at 56.2V and 54.0V for float. No battery comm. Firmware is the latest.
They get to 56.2V and then stay there until the sun goes down. They never go to 54V.
It is damaging to the batteries to have them stay at the high V once full. That's why we switch to a lower float V.
Does anyone else with 6000XPs have this problem or is it just my 2 units?
Sig Solar is looking into this.
Thanks.
I can confirm this behavior, and will attach snapshots.....
I sent this information to EG4, and signature Solar, about a month ago and the response was that they would tell their programming team.... but I have never heard anything back, and they do not have a formal 'bug-tracker' or trouble ticket system so I dunno how we will be informed if there IS a fix ?!
I like the 6000xp otherwise, but I do NOT like the behavior of the charge controller.
I have installed two 6000xp's recently, and run open loop with batt-type=lead-acid because I have found closed loop comms 'problematic'. I like to be able to use Voltage setpoints, not calculated SOC%. It *should* be possible for the 6000xp charge controller to use a CC-CV charge curve that is good for Lithium, but it is NOT behaving as programmed. (firmware version ccaa-C0D)
I have set:
Vbulk = 56.1
Vfloat = 54.0
Veq = 54.0
Eq days = 0
Eq time = 0
this should result in battery voltage charging up to 56.1v once a day, *not* holding at that voltage, and settling to Vfloat.
If loads exceed pv and bring the batt down, charge should return to Float voltage (not Bulk/Boost/Charge voltage).
In most charge controllers set for Lithium, the controller won't bring batts up to 'end of charge' voltage again until the 'next day', as detected by more than x time with PV voltage < 100v
what the 6000xp does is float at the Bulk voltage (56).... this is NOT good for Li battery life and increases the risk of overvoltage cells and thermal runaway.
