Hi. 

I had a F56 failure last night while my SOC was still at 50%. voltage was 47.x(forgot to make a note).

Does my battery status look ok? Volts looks very low for 82%?

How would I "recalibrate" using AGV instead of Lithium setting? Drain to x% then recharge with what settings?

Float V? Currently 53.6V

Absorption V? Currently 53.0V

Equalisation V? Currently 53.6V

1 hour ago, swazz99jhb said:

Does my battery status look ok? Volts looks very low for 82%?

The voltage will vary with differing loads. So for a certain SOC, if you add or decrease the load, that Voltage will go up and down. If there is no load then in theory the voltage will always be about the same for a certain SOC if the battery is still in good condition.
In your screenshot it looks like a 40A load which would result in a lower voltage. You need to switch off the load and then see what the Voltage is.

Still having the same issue. Battery drains to 50% SOC (while on Lithium setting) and then gives the same problem of low voltage. 

What should the Absorption Voltage be when on AGV? 

That SOC looks way out,that should be around 50%

Don't you have a USR/Voltage rather than AGV mode?

Drain down to 46v then float and absorb 53.6v

Do have a look here. But remember the data they now show for the AM2 is for the series 2, so for the original AM-2 it always was 53,6V Bulk and Float which you can still see in their Inverter setting screenshots.

https://www.hubblelithium.co.za/sunsynk

Reply from Hubble Support. Will see if this sorts it out. I have a 2020 AM2 so will double check if it must be 53.8V or 53.6V with them. 

 

Set your battery settings on your inverter as follows:

1. Bulk Voltage - 53.8V

2. Absorption Voltage - 53.8V

3. Float Voltage - 53.8V

4. Charge Amps - 30Amps (per battery)

5. Max discharge Current - 100Amps (per battery)

 

Please check all the batteries are at the same level of charge and the dip switch settings are correct. If the batteries are not at the same SOC please charge each battery up individually as described below. If the batteries are at the same voltage and dip switches done correctly you may leave the batteries connected in parallel and kindly follow the instructions below.

 

1) Disconnect the CAN comms cable.

2) Change the battery type o the inverter to AGM V.

3) Please input the Float, Bulk and equalization Voltage at 53,8Vdc.

4) Please set the Low Voltage to 44Vdc.

5) Kindly charge up battery until the inverter stops charging the battery at 53.8Vdc, this may take some time as the battery will do a cell balance at full voltage.

6) Once inverter has stopped charging, kindly reconnect your CAN cable and go back into your inverter battery menu and activate the Lithium settings and CAN communications.

1 hour ago, swazz99jhb said:

Set your battery settings on your inverter as follows:

Hubble continues to change their tech specs as they go along.
I have a 2021 AM-2. The Battery label states clearly what all voltages should be. Bulk 53,6V, Float 52,6V and cut off 42V
Then they started with the Bulk and Float voltages to actually be 53,6V for both.
Subsequently they changed the cut off to 44V
Now they upped both bulk and float to 53,8V which were the new voltages for the AM-2 Revision 2
None of these were ever published as an official amendment to the original AM-2 specs. Does an e-mail by someone at Hubble SA supersede the original official label specs?
The day that a claim comes along they will read the BMS and then state that you exceeded the 53,6V limit as per the battery label. That would be the cherry on the cake.

Firmware update needed. I'm on 1.42 need to upgrade to 1.50. 

I have the fdti unit. Just need to figure out the pin configuration to rj11 port. 

 

The attached isn't very clear. 

 

I assume it will be Rx to pin 3, Tx to pin 4 and GND to pin 5.

 

On 2022/11/28 at 8:42 PM, swazz99jhb said:

Firmware update needed. I'm on 1.42 need to upgrade to 1.50. 

I have the fdti unit. Just need to figure out the pin configuration to rj11 port. 

 

The attached isn't very clear. 

 

I assume it will be Rx to pin 3, Tx to pin 4 and GND to pin 5.

Bought a cable from SolarAssistnat. Received in 24 hours.

 

SolarAssistant (solar-assistant.io)

 

 

Anyone care to give input on these readings? SOH=50%? 

That is half the capacity. It even reports 50,32A/h capacity.
Best to check with Hubble what your next steps should be.
Maybe it needs a complete discharge before recharging with voltage control to reset the capacity calibration. 

Just now, zsde said:

That is half the capacity. It even reports 50,32A/h capacity.
Best to check with Hubble what your next steps should be.
Maybe it needs a complete discharge before recharging with voltage control to reset the capacity calibration. 

Yip have logged a new ticket and in comms with them. 

SOH was somehow set to 50. Possible with the firmware update. Hubble support set this back to 100.

I managed to drain my battery down to 40% and believe my issues is now resolved.

If anyone wish to trouble shoot their batteries a RS232 cable is a must + PbmsTools.

If you wish Hubble to assist remotely a CloudLink(RIOT) is a must. They can remotely monitor and adjust settings. NB! They cannot push Firmware updates. Thus, the need for the RS232 cable. 

Hubble confirmed that an ethernet cable works for CAN between Sunsynk and Hubble, but they've found it causes interference and recommend a cable with only pins 2,4 & 5 being used. 

Edited December 2, 20223 yr by swazz99jhb

9 hours ago, swazz99jhb said:

Anyone care to give input on these readings? SOH=50%? 

The SOH (50%) in this case is a simple rounded calculation taking "full capacity" (50320 mAH) over original capacity (100000mAH).

If it was somehow set to 50% by mistake then it should have a "full capacity" of 50000mAh and not 50320mAH. Just speculating based on the numbers, 50320mAH seems like an odd number for someone to set by mistake.

The first phase of the LFP charging cycle, or the constant current charge phase, would generally apply a constant current (or in a PV system as much as the PV can supply).

Once the battery reaches about 95% SOC (can be different depending on model and battery make) the constant volt charge phase begins and the amps start to drop slowly. When the current supplied to charge the battery reaches a fixed % (say 0.5% by example) of the battery capacity the BMS will recognise that the battery is full and will stop the charge. 

It the battery had an original capacity of say 100000 mAH it should have a "remaining capacity" of 100000mAH at this stage (battery full and charge stopped by the BMS).  If this is the case the SOH will remain at 100%. But if at this stage, say the "remaining capacity" is only 98000mAH the BMS will recognise that the battery has lost some capacity and reduce the SOH to 98%. Once this happens the "full capacity" will be shown as 98000mAH.

This process repeats itself daily. In a good battery this reduction of capacity takes years. But if there is an issue and the battery never reaches it's full capacity in a complete charge cycle you will see almost daily reductions in SOH.

You should keep on monotoring the battery just to make sure it does not slowly start to drop SOH again.

 

 

20 hours ago, swazz99jhb said:

Hubble support set this back to 100.

As additional information.
Never had to change Firmware or anything else for my AM-2. Still original as it came from the factory and I have had zero issues, except........
The inconsistency of the BMS reported data and seeming inconsistencies even between their batches and individual batteries.
My battery is still the original 110Ah capacity. I run on the Li Protocol most of the time, but as time progresses, the BMS continues to report 110Ah but the battery voltage at which it occurs drops off ever so slightly. Currently as you can see, the full capacity is at 52,8V and the cell voltages are around 4,05V with a max difference between lowest and highest of around 25mV. Compare that to the voltages and capacity of @swazz99jhb  and our batteries have the same BMS and cells? Really?
In about a month the voltage will be below 52,5V when at 110Ah
I then use manual voltage control and set it to 53,6 bulk and float. And I have monitored it numerous times now. At around 52,8V it will show having reached it's 110Ah capacity. The BMS then continues the charge and the battery and cell voltages will slowly increase, until the battery voltage reaches around 53,6V, which can take an hour or more to achieve. Now it will be 110Ah at 53,6V again. If I then leave it in Voltage control, then it will consistently be 53,6V and 110Ah.
As soon as I switch back to Li Protocol the voltage for full capacity starts dwindling.
And Solar Assistant gets it's data directly from the BMS. 
My experience with BMS and Li Protocol interfacing is anything but confidence inspiring. There are no consistent results and when the local support continues to provide voltage charges to users that are above the battery specs at time of manufacture then I believe that they also must be aware of a technical issue with the cells that they don't quite know how to solve except by artificially limiting the battery capacity and overvolting the charge cycle.
Am I satisfied with my battery? Up to now, yes, it has performed as it should without loss of capacity. Do I still have confidence in the promised 6000cycles and 10year lifespan? Looking at all the firmware changes and inconsistent user feedback with regards to voltages and capacity, I unfortunately lost some trust in that regard.

Turned out a cell was busted. Drained to 2.9V while all others sat at 3.6V causing an alarm and shutting down the battery. 

This was determined by using PbmsTools 

Battery dropped at Hubble Support in Modderfontein and sent to CapeTown where they replaced the entire cell pack and not just the single cell.