August 30, 20223 yr Thanks All I can read the info in PBM tools which means my cable is working ( I think ) I only have the 2.05 Version. Hubble did not send me the 1.46. They said it could be the cable so I have picked up theirs and will try again later. Will report back.
August 31, 20223 yr On 2022/08/25 at 10:17 AM, system32 said: Good News, Solar-Assistant Software version 2022-08-25 has fixed the incorrect temperature reporting issue on Hubble AM-2 - connected via RS232/console port: https://solar-assistant.io/help/updates/changelog 2022-08-25Beta New features: Add WiFi country code selection to network configuration. Upgrade of underlying frameworks and libraries. Basic support for EASUN SMG II and PowMr inverters that use with RS232 WiFi dongle and SmartESS app. Select inverter type "Sumry". Support for most important setting of Must and SRNE inverters. Support for adjusting more Deye and Voltronic settings via MQTT. Corrections: Correct temperature reading of USB serial protocol. Interesting, I had also previously had a chat to them stating they were reading environmental temp versus actual battery and after seeing your post, I updated however received a different date: and now seeing a completely negative temp value - thus from the 29deg to -79deg. Waiting for the system to prompt me with new update available, see yours is later.
August 31, 20223 yr On 2022/08/30 at 3:25 PM, MyproD said: Thanks All I can read the info in PBM tools which means my cable is working ( I think ) I only have the 2.05 Version. Hubble did not send me the 1.46. They said it could be the cable so I have picked up theirs and will try again later. Will report back. 20 hours ago, MyproD said: Does not work with their cable either. That is a tad annoying. Not sure if I missed a post or two... are you trying to flash version 1.46 to a AM-2 that is already on version 2.05? Is this even possible? My first AM-2 (master) was bought in November 2021 and shipped with v1.43. In January 2022 I got a second one (slave) that shipped with v2.03. After I experienced issues Hubble sent me v2.03 for the master which gave a bin file error... afterwards I was told that v2 is not compatible with v1. Long story short, the slave was later flashed to v2.05 while the master was flashed to v1.46... still had problems so the slave was sent to support on two occasions who eventually supplied a brand new unit with v1.43 that was also flashed to v1.46. After this they were running absolutely perfectly for a couple of months and then recently the master dropped to 50% SOH. After 2 weeks at support they replaced 3x cells. That's 2x repairs and 1x swap out in 9 months! Not impressed to say the least... Although minor I have since noticed that the repaired unit is charging to nearly 54V while the other one stop charging at 53.3V according to the Cloudlink. (CAN of master AM2 connected to CAN on Sunsynk and serial of master AM2 connected to cloudlink) Will be monitoring it... who knows, maybe a 4th visit insight??
August 31, 20223 yr @system32 This has been an extensive discussion topic and wondering if this topic/thread has driven Hubble to ensure their new released series of batteries, mitigates all the issues raised to date?
September 1, 20223 yr Author On 2022/08/31 at 5:08 PM, HiTech said: @system32 This has been an extensive discussion topic and wondering if this topic/thread has driven Hubble to ensure their new released series of batteries, mitigates all the issues raised to date? I would expect that these new batteries will address all know issues with AM-2. Also using LFP seems like a good choice for longevity. I'm quite happy with my 4xAM-2 subsequent to the firmware update. They have been performing as expected. Also appreciate having local support.
September 4, 20223 yr So a big sunshiny day in East London, and I still cannot get beyond 71% SOC. It could be me, It could be my 2 month old system or just plain bad settings. Help would really be appreciated. Settings are as below:
September 4, 20223 yr 52 minutes ago, Electronmonkey said: So a big sunshiny day in East London, and I still cannot get beyond 71% SOC. It could be me, It could be my 2 month old system or just plain bad settings. Help would really be appreciated. Settings are as below: Would suggest posting this as a new query under the Questions and Answers, may get a few more views that way. This thread is very specific to the Hubble AM2 issues and may or may not relate to your issue. To start could you provide a little background on what you have installed, Inverter model, batteries and model, (brief desc on cabling used may also help) PV quantity and model, etc. This will assist in trying to determine if your settings correspond to your equipment/configuration. Can you post your LiBMS screen from under settings. Batt qty/type/model will determine whether other settings are correct. Looking at your timers, you may not be giving your batteries time to charge, based on the percentages, that's if you do not have sufficient PV to run the environment through the day and provide sufficient charge. Does you battery discharge through the daylight hours?
September 4, 20223 yr 1 hour ago, Electronmonkey said: So a big sunshiny day in East London, and I still cannot get beyond 71% SOC. It could be me, It could be my 2 month old system or just plain bad settings. Help would really be appreciated. Settings are as below: Looking at the 25% setting up to 13h means most PV is used for consumption. The next setting also restricts charging to only 40%. Then without knowing PV size your load at over 750W with 1000W from PV does not leave a lot to charge a 300Ah bank before sunset. When using grid charge what level do the batteries reach? Also look at the info Hitech asked about your system.
September 5, 20223 yr Hubble Lithium have new callcentre software and there is a FAQ: Take a look at https://hubblelithium.freshdesk.com/support/solutions/folders/151000036639 This seems to describe the problem: https://hubblelithium.freshdesk.com/support/solutions/articles/151000007102-how-to-configure-unbalanced-am2-batteries-
September 5, 20223 yr Author 16 hours ago, Electronmonkey said: So a big sunshiny day in East London, and I still cannot get beyond 71% SOC. It could be me, It could be my 2 month old system or just plain bad settings. Help would really be appreciated. Settings are as below: Please supply the details of your system: SunkSynk 8k or SunSynk 5k - seems like you have a 5k. How many batteries & model do you have? How many panels & rating do you have? Are the panels north facing, any shade? Are you grid feeding? What monitoring do you have - SolarMan/SunSynk/Solar-Assistant?
September 5, 20223 yr So a big sunshiny day in East London, and I still cannot get beyond a 71% Soc. It could be me, it could be my 2 month old system or just plain bad settings. help! it’s a Sunsynk 5.5 x 2 paralleled system connected to 3 Hubble batteries. Plenty of power available from 24 JB panels. settings are as below: Hi, my system is 2 Suynsynk 5.5kw inverters in parellel feeding 3 Hubble AM 2 5.5kw batteries. I have 12 455w JA panels facing East and a further 12 JA 455w panels facing west. The LIBMS screen at1pm today in full sunshine is below. the battery does not discharge during the day. It reaches the 71% in the morning and does not increase. Monitoring is the Synsynk module. My goal is primarily to save electricity costs and secondary to beat load shedding. Thanks for responses from HiTech, Scorp007, YellowTapemeasure, and system32.
September 5, 20223 yr Author 5 hours ago, Electronmonkey said: So a big sunshiny day in East London, and I still cannot get beyond a 71% Soc. It could be me, it could be my 2 month old system or just plain bad settings. help! it’s a Sunsynk 5.5 x 2 paralleled system connected to 3 Hubble batteries. Plenty of power available from 24 JB panels. settings are as below: Hi, my system is 2 Suynsynk 5.5kw inverters in parellel feeding 3 Hubble AM 2 5.5kw batteries. I have 12 455w JA panels facing East and a further 12 JA 455w panels facing west. The LIBMS screen at1pm today in full sunshine is below. the battery does not discharge during the day. It reaches the 71% in the morning and does not increase. Monitoring is the Synsynk module. My goal is primarily to save electricity costs and secondary to beat load shedding. Thanks for responses from HiTech, Scorp007, YellowTapemeasure, and system32. AFAIK, This is the battery BMS telling the Inverter it is full (0A charge allowed), but the battery is only at 70% SoC. Check the battery ID's and inter battery cabling. On my system (4 x AM2), "Charge Current Limit" SoC starts at 400A and goes to 0A as the SoC rises to 100%. I'll take some photos at different times to confirm. EDIT: The pictures below show the LiBms as the bank discharges. Discharge Between 100% - 95% the BMS does not allow re-charging to prevent continuous topping up. Charging When charging, the Charge Current Limit is reduced as the SoC approaches 100%. I'll see if I can take some images of the charge phase. Edited September 5, 20223 yr by system32
September 5, 20223 yr 4 hours ago, Electronmonkey said: So a big sunshiny day in East London, and I still cannot get beyond a 71% Soc. It could be me, it could be my 2 month old system or just plain bad settings. help! it’s a Sunsynk 5.5 x 2 paralleled system connected to 3 Hubble batteries. Plenty of power available from 24 JB panels. settings are as below: Hi, my system is 2 Suynsynk 5.5kw inverters in parellel feeding 3 Hubble AM 2 5.5kw batteries. I have 12 455w JA panels facing East and a further 12 JA 455w panels facing west. The LIBMS screen at1pm today in full sunshine is below. the battery does not discharge during the day. It reaches the 71% in the morning and does not increase. Monitoring is the Synsynk module. My goal is primarily to save electricity costs and secondary to beat load shedding. Thanks for responses from HiTech, Scorp007, YellowTapemeasure, and system32. Did you follow the procedure which @YellowTapemeasure provided from the Hubble helpdesk?
September 5, 20223 yr So when the charge limit is at 0A and the battery is at 70%, there's a 0x0C alarm code. Can you check if the alarm light is flashing on one of the batteries? I had a similar issue with my 2 batteries where it would only charge to 96% and then the bms would set a 0A charge limit. I've hooked up a riot and saw that one of the batteries had a cell high voltage fault which would trigger this state. I cycled the batteries using the AGM V mode and then left the riot for a day to do some balancing voodoo and it seems to have worked for me, I now get to 100% soc at 54v. I do get a random contactor fault that comes and goes on one of the batteries, anybody know anything about this?
September 6, 20223 yr 23 hours ago, PowerUser said: Did you follow the procedure which @YellowTapemeasure provided from the Hubble helpdesk? Yes, did it today and…….. got 100% soc by early afternoon. Let’s see what tomorrow brings.
September 6, 20223 yr 18 minutes ago, Electronmonkey said: Yes, did it today and…….. got 100% soc by early afternoon. Let’s see what tomorrow brings. Great! Let us know how it goes. We are all curious to know, if it resolves the issue permanently.
September 7, 20223 yr I have the exact sam problem where my batteries charge from PV til 97% then stops. Tried the HUbble Support procedure and still no luck. Hubble called me today to tell me i must discharge my batteries to 20% for the next 2 weeks daily then the SOC will fix itself. Will se how it goes.
September 10, 20223 yr Been monitoring my soc last few days and the process seems to have worked. Well, getting 99 % soc which I am quite happy with. Thanks for the advice everyone.
September 13, 20223 yr Not too impressed right now. Battery 2 that was dropping to 0% from +- 35% was taken in to Hubble for assessment. Load test showed an equalisation issues and the firmware was updated to 2.07 and the battery was returned to me showing that it passed all the tests. Hooked it up and did some testing last night. At 35% the battery shut down. Not even the on LED was on. Battery 1 continued flawlessly down to 15% SOC until my PV took over this morning. Set the inverter to AGM this morning and disconnected the CAN cable. Will charge both up and let it balance again and test again tonight. Battery 2 is still on 2.05 firmware. Endless begging Hubble to supply me with the latest firmware to update... Does anyone perhaps have the file for me?
September 13, 20223 yr What invertor you using? What is your shutdown set at? Are the batteries still balancing?
September 13, 20223 yr 18 minutes ago, Singh GP said: What invertor you using? What is your shutdown set at? Are the batteries still balancing? My whole journey with this is documented earlier in this thread. Sunsynk 5k Shutdown is set at 10% They are balancing yes.
September 13, 20223 yr 9 hours ago, maxxis said: Current state of things. Those ‘charge capacity’ values are a concern. If looking at your LiBMS values on your inverter (when set to Lithium Batt), what charge current limit is displayed there? Charge current should be higher with the lower SOC and reduce as you reach 100% SOC. Your Batt #1 has low SOC with low Charge capacity.
October 24, 20223 yr On 2022/03/23 at 11:55 AM, Mier said: Interestingly, I installed a new AM-2 this morning the Capacity showed 100AH, the SoC was ~50% (shipping voltage I suppose). It proceeded to charge up to 103.4% SoC. Now, after about an hour, the Capacity is shown as 103.4 AH and SoC is 100%. I bought one battery in Dec21 and another in Sept22 and now with software have established that my 2 batteries have different firmware resulting in absolute weird readings as below: Bat1 Bat2 Capacity. 29Ah 100ah SOC. 4.2%. 62.1% Charge capacity. 1.2Ah. 62.1Ah Cycles. 561. 88 Looks like the different firmware could be the issue?
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.