swazz99jhb

Bought a cable from SolarAssistnat. Received in 24 hours. SolarAssistant (solar-assistant.io)

I have the same label on my AM2. Connected a Cloudlink/RIOT and the Hubble technician could see exactly what is what. He still gave me 53.8V for Absorption/Float/Equalization. They gave me Firmware 1.50 which I updated using a SolarAssitant cable. Will see if this resolved my F56 problems. The support from @HubbleLithium was exceptional. Constant emails and phone calls with quick turnaround times.

Did you guys figure this out? Same issue with a SunSynk 5 kW.

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.

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.

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?

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

Think the upgrade changed it to 00. I changed it back to 01.

Double check your Unit Id hasn't changed. Happened to me with a firmware upgrade.

They diagnostics and didn't find anything wrong. They managed to charge it using voltage settings instead of CAN. Thus it wasn't anything wrong with battery. The out of sync issue could have been the firmware. If you have a RIOT then can diagnose and upgrade remotely. You can also buy the cable from them and upgrade the firmware yourself. Must be some installers out there that could assist.

Setup voltage as per their page, tick Battery Type AGM V. Disconnect CAN cable and let it charge.

Sorry can't remember. It was over a phone call. I eventually took it to them to sort out. You can try attached. https://www.hubblelithium.co.za/sunsynk-hubble-setup.html

Dear Francois Smit, This is regarding Ticket #476, which you opened with Hubble Lithium helpdesk. I trust all is well Apologies on the terrible response time of your support query since the last interaction. We've been dealing with a large number of support tickets are try our best to get to everyone as soon as possible Seems like you may have a synchronization issue. Refer to he link below and ensure that your inverter settings are correct: https://www.hubblelithium.co.za/sunsynk-hubble-setup.html Once that has been configured correctly, removed the CAN cable and charge batteries using voltage settings only. Once the batteries have charged fully according to the inverter, plug the CAN cable back in. Drain the battery and charge up with no load. You may charge it up with load if charging with no load isn't an option. Warm regards, Imraan

Sorry not sure. I took my battery to them where they then sorted it out. From what I understood they didn't use a Sunsynk.

Use the settings provided by Hubble but change the battery from lithium to AGM V and disconnect the CAN cable (batt bms will protect you) let it drain and then charge. That is what they did to resolve my issue.

Item: Earth Neutral Box Age: UNUSED (Bought 1 year ago) Price: R900.00 Payment Method Accepted: EFT Warranty: none Packaging: In original box Condition: New Location: Randburg / Gauteng Reason: UnUsed Shipping: Can be arranged at additional fees Collection: Randburg, Gauteng Link:, zhttps://segensolar.co.za/product/segen/protection-segen/ac-protection-box/earth-neutral-bridge-box-for-ac-protection-box/

A good one or a school project? In essence it is a motor in reverse. I've seen DIY Wind turbines using washing machine motors.

Search the forum for monitoring. I use a PiZero to connect to my Sunsynk via a USB to serial converter and interacting with it via NodeRed using the ModBus protocol.

What size wire is beyond this breaker? The breaker protects the wire. Doesn't help the breaker is 32a if the wire is going to melt.

Ja ja. I understand but my solution is not to get rid of Eskom or utilise the sun. Mine is so that I have Internet and lights when Eskom fails to deliver. Whether it be loadshedding or bad management. Probably wouldn't be so stingy if I had solar panels and an extra battery. Solar is on its way.

Yes because my battery will already be drained cause I heated my geyser with it.

I don't want to waste battery on heating my power hungry geyser when there's loadshedding and I can't be sure when the power goes back on.

You don't need it, but it will show usage from grid. Arrow is with the flow thus towards db/inverter. Manual says 5 & 6. Can't remember if that was correct. Search on the forum, there was discussion on it.

Turn around time via their ticket system was redoncoulus! But social platforms is the new normal for support.