Skip to content
View in the app

A better way to browse. Learn more.

Power Forum - Renewable Energy Discussion

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Hubble Lithium Battery AM-2 5.5kWh

Featured Replies

31 minutes ago, Leonb said:

As I haven't bought anything yet, I need to avoid costly mistakes or endless hassles.

So I had a quick call with Hubble technical support yesterday about the Hubble/Sunsynk "issues". I dont know what level of tech support the guys was, but it was not a very confidence inspiring call....

According to him there is a definite communication issue between the Sunsynk and Hubble AM2 battery, and you need to run the RIOT Cloudlink if you want to pair the Sunsynk inverter and Hubble battery. 

He also advised me, since I haven't bought an inverter yet, to rather get a Kodak or Victron ... ?

Lucky you got through, eventually I sent an email yesterday morning trying to get some sort of response, still nothing.

Maybe Pylontech would be more suitable for the Sunsynk ? 

 

  • Replies 509
  • Views 129.6k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • Powerforum Store
    Powerforum Store

    I am noticing a trend here on the posts and I find it concerning borders on Product bashing.  It maybe due to lack of Knowledge or lack of understanding how lithium batteries work. The reaso

  • Powerforum Store
    Powerforum Store

    Hi all .Just an update on the Hubble issues you have been experiencing I have been in talks with Hubble Senior Engineer and these are some Highlights of our discussion. 1. All firmware updates an

  • Update time.  Over the past week I've done a lot of monitoring and calculations to determine my capacity and to track down where the problem lies with my pack. The original problem I experienced

Posted Images

19 minutes ago, isetech said:

Lucky you got through, eventually I sent an email yesterday morning trying to get some sort of response, still nothing.

Maybe Pylontech would be more suitable for the Sunsynk ? 

 

Hubble have not formally said that their battery does not talk to the Sunsynk and that you definitely need Riot.  If they did that, and we had known that, then it may have been better to go with other batteries, e.g. Freedom Won or Pylontech ...

Unfortunately I have this problem. Pack1 purchased in Feb 2022. Pack 2 purchased Aug 2021. Problem is obviously with different firmware. I purchased the batteries from the Powerforum store and am the installer. I am waiting for feedback from my supplier since the 19th April. Not a peep yet.

My main question is what do us guys out in the sticks (East London) do to update the firmware if we do not intend to purchase a RIOT?

hubble.JPG

  • Author
On 2022/05/13 at 11:08 AM, system32 said:

 

image.png
In my case I'm seeing ~18% difference between AM-2 BMS SoC and SunSync AGM/V SoC calculation.
The SunSync SoC calculation is confirmed by the Juntek SoC/Ah readings.

If I use the AM-2 BMS SoC, the inverter stops drawing battery at 20% (horizontal).
Using AGM-V helps.

I've updated my call with Hubble support.

On Fri 16th May Fri 13th May, I received and installed P1247V110-12290V205T-0316.bin AM-2 firmware from hubble support.
The firmware installation was done with with a Windows 10 laptop and USB/RS232/RJ10 console cable (same cable used by Solar-Assistant)

The firmware has reset the SoH to 100% and Capacity to 105Ah.
I've reverted the SunSynk back to Lithium/CANBus.
image.thumb.png.a1870dabe01cdfb9005ed5736a4b06f5.png
I've asked Solar-Assistant support to confirm the temperature values as these are much higher than reported by LiBMS
image.png.7d87235cf3f7900fc1e472681684d941.png

image.png.26ad7d927593478eda92a7a2e3211be1.png


All seems to be good so far with P1247V110-12290V205T-0316.bin.
I'll monitor the installation and report back once more time has elapsed.

From what I can establish the AM-2 BMS is from PACE
http://www.pacebms.com
 

Edited by system32

1 hour ago, system32 said:

I've received and installed P1247V110-12290V205T-0316.bin AM-2 firmware from hubble support.
The firmware installation was done with with a Windows 10 laptop and USB/RS232/RJ10 console cable (same cable used by Solar-Assistant)

The firmware has reset the SoH to 100% and Capacity to 105Ah.
I've reverted the SunSynk back to Lithium/CANBus.
image.thumb.png.a1870dabe01cdfb9005ed5736a4b06f5.png
I've asked Solar-Assistant support to confirm the temperature values as these are much higher than reported by LiBMS
image.png.7d87235cf3f7900fc1e472681684d941.png

image.png.26ad7d927593478eda92a7a2e3211be1.png


All seems to be good so far with P1247V110-12290V205T-0316.bin.
I'll monitor the installation and report back once more time has elapsed.

From what I can establish the AM-2 BMS is from PACE
http://www.pacebms.com
 

Why would they artificially restrict the capacity of 110Ah to 105Ah?

@system32could you post a snip of your Battery Dashboard when the batteries are at 100% SOC. Would like to compare those cell voltages at the new 100% (105Ah) restriction to those of mine, which is still at 110Ah capacity.

as a side note. If the 105Ah is now an official capacity, then these batteries cannot be advertised as 5,5kW units anymore. 

Edited by zsde

  • Author
48 minutes ago, zsde said:

Why would they artificially restrict the capacity of 110Ah to 105Ah?

@system32could you post a snip of your Battery Dashboard when the batteries are at 100% SOC. Would like to compare those cell voltages at the new 100% (105Ah) restriction to those of mine, which is still at 110Ah capacity.

as a side note. If the 105Ah is now an official capacity, then these batteries cannot be advertised as 5,5kW units anymore. 

When I first received my AM-2 they read 110Ah each.
Hubble Support reduced them to 100Ah for my own good to prevent dendrite formations.
This latest update set them to 105Ah.

Seems that 5.5kWh is a marketing capacity.

Edited by system32

I have the AM-2 that is 2 weeks old, and is reading 101.5

Capacity 101.5 Ah
State of charge 98.8 %
Power -187 W
Current -3.5 A
Voltage 53.3 V
Temperature 29.8 °C
Cycles 10
Charge capacity 100.2 Ah
Cell voltage - Highest 4.112 V
Cell voltage - Average 4.097 V
Cell voltage - Lowest 4.066 V
Cell temperature - Highest 30.1 °C
Cell temperature - Average 29.8 °C
Cell temperature - Lowest 29.6 °C

Hoping that someone from Hubble is prepared to answer my concern now.
I am a happy Hubble customer. My Battery is performing as per it's original promises and design.
Still have full capacity at 270 cycles albeit early days.
I have the original firmware from the June 2021 manufacture date.
If I now decide to add another unit in parallel, I shall assume it will be with the new firmware which would then create an imbalance from the start.
Would Hubble insist that I flash the firmware on my original perfectly working Battery to match the new version or will they flash the new Battery to the same firmware present on my current battery?
What percentage of their Batteries did they receive problem reports on and which were the majority of Inverters that were used within those problem reports.
If a user like me with my Inverter has had no issues, then a Inverter specific Firmware may be required to address the issue.
There obviously have not been any long term tests with this new Firmware to determine if it reduces the problem percentage.
Thus if ever I decide to add a battery, will Hubble assist in providing the firmware that works so well with my setup?

image.png.6851e9b4a87a1db0fcfe8aa13e7e9c9a.png 

I am also running P1247V110-12290V205T-0316.bin AM-2 firmware, since mid April 2022. Capacity also set at 105Ah. SoH=100

Apparently this is a new hardware version of the BMS, hence the reason for the new firmware.

All seems to working okay for the moment, just hope this is the last of the firmware issues.

12 hours ago, zsde said:

Hoping that someone from Hubble is prepared to answer my concern now.
I am a happy Hubble customer. My Battery is performing as per it's original promises and design.
Still have full capacity at 270 cycles albeit early days.
I have the original firmware from the June 2021 manufacture date.
If I now decide to add another unit in parallel, I shall assume it will be with the new firmware which would then create an imbalance from the start.
Would Hubble insist that I flash the firmware on my original perfectly working Battery to match the new version or will they flash the new Battery to the same firmware present on my current battery?
What percentage of their Batteries did they receive problem reports on and which were the majority of Inverters that were used within those problem reports.
If a user like me with my Inverter has had no issues, then a Inverter specific Firmware may be required to address the issue.
There obviously have not been any long term tests with this new Firmware to determine if it reduces the problem percentage.
Thus if ever I decide to add a battery, will Hubble assist in providing the firmware that works so well with my setup?

image.png.6851e9b4a87a1db0fcfe8aa13e7e9c9a.png 

Best to log a call with them and raise your questions and concerns.

  • Author
On 2022/01/11 at 5:24 PM, TimCam said:

Your batteries temperature is high. No way to cool the room?

My AM2's run between 18C and 24C, and still show a SOH of 100%.

FYI:
Just did more testing wrt to temperature.
Seems Solar-Assistant temperature reading via the AM2 RS232/Console port may be incorrect.
RIOT, SynSynk LiBMS, Juntek temperature probe, Modbus all show ~21.5/~24.5C, but SA shows ~29.5C

modbus register(  31)=22.1
modbus register(  32)=21.8
modbus register(  33)=21.6
modbus register(  34)=21.7
modbus register(  35)=24.9
modbus register(  36)=24.5

image.png.dc437157365b5279bae8daadf929c359.png

image.png.f33c872d42d7040b62363f86b0afdc4b.png

image.png.e63bface3e4599a3bc8c92fbbb4da790.png

image.png.18c97c045dbf3775e4d9d592b70b8509.png
Odd system out is Solar-Assistant via RS232/Console:image.png.814725124dc02f41caaccf010075d61e.png

I've asked SA support to check why there is a discrepancy.

10 minutes ago, system32 said:

FYI:
Just did more testing wrt to temperature.
Seems Solar-Assistant temperature reading via the AM2 RS232/Console port may be incorrect.
RIOT, SynSynk LiBMS, Juntek temperature probe, Modbus all show ~21.5/~24.5C, but SA shows ~29.5C

modbus register(  31)=22.1
modbus register(  32)=21.8
modbus register(  33)=21.6
modbus register(  34)=21.7
modbus register(  35)=24.9
modbus register(  36)=24.5

image.png.dc437157365b5279bae8daadf929c359.png

image.png.f33c872d42d7040b62363f86b0afdc4b.png

image.png.e63bface3e4599a3bc8c92fbbb4da790.png

image.png.18c97c045dbf3775e4d9d592b70b8509.png
Odd system out is Solar-Assistant via RS232/Console:image.png.814725124dc02f41caaccf010075d61e.png

I've asked SA support to check why there is a discrepancy.

I was always wondering why/how everyone's battery temps are the same at 29-30 lol . Thanks for your investigative work !

2 hours ago, system32 said:

FYI:
Just did more testing wrt to temperature.
Seems Solar-Assistant temperature reading via the AM2 RS232/Console port may be incorrect.
RIOT, SynSynk LiBMS, Juntek temperature probe, Modbus all show ~21.5/~24.5C, but SA shows ~29.5C

modbus register(  31)=22.1
modbus register(  32)=21.8
modbus register(  33)=21.6
modbus register(  34)=21.7
modbus register(  35)=24.9
modbus register(  36)=24.5

image.png.dc437157365b5279bae8daadf929c359.png

image.png.f33c872d42d7040b62363f86b0afdc4b.png

image.png.e63bface3e4599a3bc8c92fbbb4da790.png

image.png.18c97c045dbf3775e4d9d592b70b8509.png
Odd system out is Solar-Assistant via RS232/Console:image.png.814725124dc02f41caaccf010075d61e.png

I've asked SA support to check why there is a discrepancy.

@system32Just a quick question. On SA is your "Pack #1" the master or slave battery? On my system Battery 1 is shown as "Pack #2".

  • Author
1 hour ago, Gerry R said:

@system32Just a quick question. On SA is your "Pack #1" the master or slave battery? On my system Battery 1 is shown as "Pack #2".

Same here.
The pack order on SA using RS232/console is different from SA using RS485/modbus.

I notice that the battery temperature on the Dashboard > Inverter page is the correct value.

6 hours ago, system32 said:

FYI:
Just did more testing wrt to temperature.
Seems Solar-Assistant temperature reading via the AM2 RS232/Console port may be incorrect.
RIOT, SynSynk LiBMS, Juntek temperature probe, Modbus all show ~21.5/~24.5C, but SA shows ~29.5C

modbus register(  31)=22.1
modbus register(  32)=21.8
modbus register(  33)=21.6
modbus register(  34)=21.7
modbus register(  35)=24.9
modbus register(  36)=24.5

image.png.dc437157365b5279bae8daadf929c359.png

image.png.f33c872d42d7040b62363f86b0afdc4b.png

image.png.e63bface3e4599a3bc8c92fbbb4da790.png

image.png.18c97c045dbf3775e4d9d592b70b8509.png
Odd system out is Solar-Assistant via RS232/Console:image.png.814725124dc02f41caaccf010075d61e.png

I've asked SA support to check why there is a discrepancy.

On the Dasboard > Inverter  page the temperature has the correct value.

Capture.JPG

7 hours ago, system32 said:

FYI:
Just did more testing wrt to temperature.
Seems Solar-Assistant temperature reading via the AM2 RS232/Console port may be incorrect.
RIOT, SynSynk LiBMS, Juntek temperature probe, Modbus all show ~21.5/~24.5C, but SA shows ~29.5C

modbus register(  31)=22.1
modbus register(  32)=21.8
modbus register(  33)=21.6
modbus register(  34)=21.7
modbus register(  35)=24.9
modbus register(  36)=24.5

image.png.dc437157365b5279bae8daadf929c359.png

image.png.f33c872d42d7040b62363f86b0afdc4b.png

image.png.e63bface3e4599a3bc8c92fbbb4da790.png

image.png.18c97c045dbf3775e4d9d592b70b8509.png
Odd system out is Solar-Assistant via RS232/Console:image.png.814725124dc02f41caaccf010075d61e.png

I've asked SA support to check why there is a discrepancy.

I've noticed this difference too, and have ignored SA temp's and read temp on the SunSynk.

Thanks the the clarification. 👍

  • 2 weeks later...
  • Author

Update: 1 June 2022
It's been 2 weeks 3 days since I updated the firmware on the 4xAM-2.
So far all good.
SoH 100%🙂 and Capacity 105Ah😢 per battery.

image.thumb.png.152e357580158fe7d536782417d937c9.png

The firmware installation was done with with a Windows 10 laptop and USB/RS232/RJ10 console cable
https://solar-assistant.io/shop/products/hubble_am

image.png.de92026487ef3e257da69b5b86584eb3.png

EDIT: had to do a discharge to 20% and charge to 100% for reported SoC to match actual SoC.
 

Edited by system32

@system32 I got the firmware update utility and bin file (Same as yours) but i am getting a bin file error when I try to "Upgrade" I am using the usb to serial lead that works with Solar-Assistant. Setting appear to be set the same as in your screen shot.

Am I missing something? Does the AM2 have to be set into firmware update mode or something?

 

 

  • Author
1 hour ago, Gerry R said:

@system32 I got the firmware update utility and bin file (Same as yours) but i am getting a bin file error when I try to "Upgrade" I am using the usb to serial lead that works with Solar-Assistant. Setting appear to be set the same as in your screen shot.

Am I missing something? Does the AM2 have to be set into firmware update mode or something?

Did you put in the password?

Are you using the correct COM port? My laptop took a while to install the USB FTDI driver.

I just clicked browse, selected the bin file, entered the password and pressed upgrade.

I'll update the post with the MD5 checksum

Thanks for the reply.

Did all those things. Was using a borrowed laptop. Looks like I have to haul my desktop PC out to the garage and try again.

Checksum will be a big help. This is the MD5 of the file I downloaded.

57639ba3640761b7762e9807a1464d0c

MD5 checksum matches, so the bin file is not corrupted. Borrowed laptop had to be returned, but com port on my main PC matches yours, So will lug it out tomorrow and try again. Thanks for the info anyhow.

 

On 2022/04/15 at 10:32 AM, werner.potgieter said:

A1. I used the 6pin RJ11/RS232 port, successfully.

A2. RIOT is supposed, however in my case it seems Hubble Support could not.

A3. I do not know, but I think it should work, but at R500 it is a bit steep for a RS232 cable.

https://solar-assistant.io/shop/products/hubble_am

Considering the USB/RS485 i think thats the number you can buy the uGreen one from Sonic Informed for R212 

So they are sure marking those cables up nicely 

Edited by SeaSickMama

  • Author
7 hours ago, SeaSickMama said:

Considering the USB/RS485 i think thats the number you can buy the uGreen one from Sonic Informed for R212 

So they are sure marking those cables up nicely 

Note:

for SunSunk you need a RJ45 (Ethernet) connector.

for AM-2 you need an RJ10 connector

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.