IronEYE

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??

I had a chat with Hubble support last week after I'm also experiencing very low SOH and strange charge/SOC behavior on my 2x AM2’s and 8kW Sunsynk. The batteries have less than 100 cycles and are only a couple of months old. Funny enough Hubble never admitted to or mention anything reported in this post.


I’ll give the AGM-V setting a go and see if that makes any difference. Would be interesting to see what the outcome of possible firmware between Hubble and Sunsynk will be? Hopefully @Powerforum Store and  @HubbleLithium will keep us in the loop as the last updated was on 16 Feb 2022.