IronEYE
Members-
Posts
7 -
Joined
-
Last visited
Content Type
Profiles
Forums
Gallery
Blogs
Events
Store
Downloads
Everything posted by IronEYE
-
My 9 month old 8kW SS had a firmware update a week ago and it is now on M6.0.1.4 / S0.7.1.7 / CE.4.2.4 The previous version was M6.0.1.3 / S0.7.1.7 / CE.4.2.2. Strange that the Slave MCU stayed the same? Earlier today I experienced 0W PV between 13:15-13:35 while the batteries carried the load. Full sun with no cloud insight. The load at that stage varied between 150W - 220W. Once the load went up to 340W the PV kicked in and since then the load dropped to 150W again, but this time with the PV doing its job. DC temperature between 13:15-13:35 was 60.7 degrees, this morning it spiked at 63 degrees with no issues. I also experienced this earlier in the year where the PV will drop off if the load goes below 200W.
-
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.
-
@HubbleLithium and @Coulomb I recently sold my 5KW Axpert King + first gen Hubble battery and bought the RCT Max 8KW along with a Hubble AM2 (2nd AM2 will be bought soon) The new units are not connected yet, but I'm also interested to find out 1.) if you know if the CAN BUS protocol is active yet on the Max and if it is sufficient to communicate with the batteries? Ideally I don't want to use a RIOT or ICC software on a Pi since the Max has Wi-Fi and comes with it's own monitoring software... 2.) or what are your thoughts on this? 3.) Would you know if ICC is compatible between the new MAX and 2x AM2's?
-
Sorry, I did not notice that this was already answered here https://powerforum.co.za/topic/5089-axpert-and-hubble-rs232-ports/
-
Do you know if the above cable pin-out also work between Axpert King <--> Hubble Lithium or what must the pin-out be on the Hubble battery side? I saw that with firmware 71.92 and 02.49 on the King the Hubble's RS485A can be connected to the King with setting 5 set as LIB. I presume it's better to let the battery communicate with the inverter through RS485 rather than having no comms cable and using the manual settings 5, 12, 13, 26, 27, 29? Can you also confirm that all 4 dip switches on the Hubble must stay on 0-0-0-0 for standalone (single battery) use?
-
I recently got a Hubble and I have a RCT Axpert King with the latest firmware (71.92 and 02.49), but when I use the short patch cable that came with the Hubble (standard T-568B pinout) I get 61 communication error. I could only find the below picture of a Pylontech pinout on the forum and it looks like pin 5 on the King is RS485-A, but I'm not sure if this will work on the Hubble as well? Can you please confirm the correct cable configuration?