June 1, 20224 yr 3 hours ago, system32 said: Note: for SunSunk you need a RJ45 (Ethernet) connector. for AM-2 you need an RJ10 connector Just got the RS232 RJ10 connector this morning from Solar Assistant to upgrade the firmware on my 2 batteries. Do you just open that file they gave you and connect the system and run or any special procedure to upgrade the battery ?
June 1, 20224 yr Author 59 minutes ago, SeaSickMama said: Just got the RS232 RJ10 connector this morning from Solar Assistant to upgrade the firmware on my 2 batteries. Do you just open that file they gave you and connect the system and run or any special procedure to upgrade the battery ? Plug USB cable into Win 10 Laptop Wait about 5 minutes for Windows to install the FTDI driver from the internet (make sure you internet connected) Check Windows Device Manager (devmgmt.msc) to confirm the COM port. Connect RJ10 end to AM-2 RS232/Console port (see below) Launched "BMS Upgrade V1.0.3.exe" - choose COMx/9600 corresponding to the Device Manager COM port Browsed for the firmware file P1247V110-12290V205T-0316.bin Entered the password Press UPGRADE button Upgrade takes about 90s Battery did a small beep The SoC will reset and may have an incorrect SoC. I ran a discharge(20%)/charge(100%) cycle and the SoC adjusted to correct value Edited June 1, 20224 yr by system32
June 1, 20224 yr @system32 Thanks went ahead as you described They also sent me two versions of the firmware V2 worked Will do the next battery this weekend as stock just arrived
June 1, 20224 yr REPORT BACK: Okay, it's been a month or so since Hubble came out did my firmware on my battery (and the other 3 we bought). I was furious, there was a problem, and I set my media team on dismantling them, but decided to give them a chance first. So, what is the outcome? The batteries (at least in my batch) definitely had a firmware bug, and SOC would disappear overnight and I was left with a useless battery - one which died with 5 x Philips Hue GU10 bulbs killing it in 30min during loadshedding. The guys who came out explained that the global chip shortage necessitated a change in controller or something, and this was the issue, and also that SunSynk blah blah. They updated the battery and I was promptly out of the country for two weeks, then back for a week that all looked good, then I travelled again, but upon checking both via loadshedding, and the Inverter running off battery during the night, all looks good. I have no idea on the 110ah vs 105ah argument (above my skill set) but I'm getting the hours and percentages that make sense to me, and it looks like the firmware is good. I want to add another battery, and I'm satisfied enough (currently) to call up Steve here on PowerForum and order another AM-2. Granted, the red flags on alternate chemistry of the batteries, the changing ah values and the double cycle counts are worrying, but I figure since it's already installed and working, I'll take the chance. I do think however Hubble has handled this VERY poorly. Instead of turning it into a total brand win and loyalty building exercise for almost no money, they dug in and took me ranting online to solve the issue (seems solved at least, which means my pitbull of a team is chilled). But it's a small batch (apparently) and they should be hiring a team of two, giving them a branded vehicle, laptop and getting lists of where it's sold and setting a schedule to GO TO people and have it sorted. Dont put it on your installers (who already told me that they are using other batteries) or consumers. Two dudes, fuel and a car is super cheap to bury a problem, that with literally 2 people and effort could zero demand for your brand. Build on your product, offer the right service. Hands on service. You'll kill everyone else. TL;DR version. New firmware fixed the draining SOC problem. Happy enough at the moment to buy a second battery for my house installation. Suggest that they hire a proper brand managenent / customer care consultant to fix their awful approach to handling a PR disaster.
June 1, 20224 yr 5 hours ago, CapeTown said: REPORT BACK: Okay, it's been a month or so since Hubble came out did my firmware on my battery (and the other 3 we bought). I was furious, there was a problem, and I set my media team on dismantling them, but decided to give them a chance first. So, what is the outcome? The batteries (at least in my batch) definitely had a firmware bug, and SOC would disappear overnight and I was left with a useless battery - one which died with 5 x Philips Hue GU10 bulbs killing it in 30min during loadshedding. The guys who came out explained that the global chip shortage necessitated a change in controller or something, and this was the issue, and also that SunSynk blah blah. They updated the battery and I was promptly out of the country for two weeks, then back for a week that all looked good, then I travelled again, but upon checking both via loadshedding, and the Inverter running off battery during the night, all looks good. I have no idea on the 110ah vs 105ah argument (above my skill set) but I'm getting the hours and percentages that make sense to me, and it looks like the firmware is good. I want to add another battery, and I'm satisfied enough (currently) to call up Steve here on PowerForum and order another AM-2. Granted, the red flags on alternate chemistry of the batteries, the changing ah values and the double cycle counts are worrying, but I figure since it's already installed and working, I'll take the chance. I do think however Hubble has handled this VERY poorly. Instead of turning it into a total brand win and loyalty building exercise for almost no money, they dug in and took me ranting online to solve the issue (seems solved at least, which means my pitbull of a team is chilled). But it's a small batch (apparently) and they should be hiring a team of two, giving them a branded vehicle, laptop and getting lists of where it's sold and setting a schedule to GO TO people and have it sorted. Dont put it on your installers (who already told me that they are using other batteries) or consumers. Two dudes, fuel and a car is super cheap to bury a problem, that with literally 2 people and effort could zero demand for your brand. Build on your product, offer the right service. Hands on service. You'll kill everyone else. TL;DR version. New firmware fixed the draining SOC problem. Happy enough at the moment to buy a second battery for my house installation. Suggest that they hire a proper brand managenent / customer care consultant to fix their awful approach to handling a PR disaster. What new version of firmware are you running ? I was given these two and did one battery so far, other still in its box V2.05 worked To add to this i had to spend R500 odd to buy a cable so that i can update the batteries, rather annoyed by that Edited June 1, 20224 yr by SeaSickMama
June 1, 20224 yr Author 1 hour ago, SeaSickMama said: What new version of firmware are you running ? I was given these two and did one battery so far, other still in its box V2.05 worked To add to this i had to spend R500 odd to buy a cable so that i can update the batteries, rather annoyed by that Can you post size and md5sum of the files?
June 1, 20224 yr 22 minutes ago, system32 said: Can you post size and md5sum of the files? Hi the MD5 is in the images V1.46 File size 111KB it failed when i ran that one V2.05 Size: 178KB
June 2, 20224 yr 15 hours ago, SeaSickMama said: What new version of firmware are you running ? I honestly have no idea. They came, they did their laptop thing and now that I'm finally at home for long enough stretches to check and report back, it appears to be good. On the cable, I'd be pissed off. I didn't even have that option as my laptop is a Macbook Pro with only USB C ports, and all my staff and companies (and friends) all are on Mac too. But I shouldn't need to update firmware on a faulty product at my expense / time. Revert back to original comments.
June 3, 20224 yr On 2022/05/16 at 2:07 PM, system32 said: On Fri 16th 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. I've asked Solar-Assistant support to confirm the temperature values as these are much higher than reported by LiBMS 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 @system32 Thanks again for the feedback and updates on new version of Hubble firmware. Subsequent to the update, has your SunSynk battery settings updated under the Lithium BMS selection? IE. What are your readings now displayed under inverters battery settings, capacity, floating, equalization, shutdown, restart, etc. just interesting to know if capacity changed to 105Ah, were all these other settings adjusted at all? Thanks.
June 3, 20224 yr Author On 2022/06/03 at 7:52 AM, AC-DC said: @system32 Thanks again for the feedback and updates on new version of Hubble firmware. Subsequent to the update, has your SunSynk battery settings updated under the Lithium BMS selection? IE. What are your readings now displayed under inverters battery settings, capacity, floating, equalization, shutdown, restart, etc. just interesting to know if capacity changed to 105Ah, were all these other settings adjusted at all? Thanks. REPORT BACK: All good since the firmware update P1247V110-12290V205T-0316.bin on Fri 16th May Fri 13th May. Glad to say that as of today Mon 27th Jun 2021, all is still good with Hubble AM-2. After the firmware update I reverted the SunSynk from AGM/V to Lithium (CANBus) >capacity, floating, equalization, shutdown, restart, These are all manually input - I used the same SoC values as before. Shutdown, Low Batt, Restart, Work Mode change from V to Percent SoC when using Lithium battery type. The inverter stores both values, so when switching, only need to enter your values once. Please note that it took a 24h cycle to re-calibrate the SoC - see attached graphs. Edited June 27, 20223 yr by system32
June 3, 20224 yr Have Hubble sorted out the comms problems with the sunsynk 5 kw inverter and hubble riot system so you can see your inverter running with the riot system.
June 3, 20224 yr 5 hours ago, system32 said: REPORT BACK: All good since the firmware update P1247V110-12290V205T-0316.bin on Fri 16th May Fri 13th May. After the firmware update I reverted the SunSynk from AGM/V to Lithium (CANBus) >capacity, floating, equalization, shutdown, restart, These are all manually input - I used the same SoC values as before. Shutdown, Low Batt, Restart, Work Mode change from V to Percent SoC when using Lithium battery type. The inverter stores both values, so when switching, only need to enter your values once. Please note that it took a 24h cycle to re-calibrate the SoC - see attached graphs. Yup same here after the upgrade, lovely to have them working as they should !!
June 3, 20224 yr 1 hour ago, Gerry R said: Hi All, has anyone tried "pbms tools v2.5" on their Hubbles. This is what I get: Interesting. I see that you have one original battery with a manufacture date of 21/05 still at 110A/h. That is the same series battery I have. Then your second Battery from 21/12 seems to be with the new Firmware with the reduction to 105A/h. Does the BMS manage the two different capacities without issues? Was wondering if I were to get one more Battery if my current Battery would have to get a Firmware change to be able to run them in Parallel. My current one is at 288 cycle and I have had zero issue.
June 3, 20224 yr 3 hours ago, Gerry R said: Hi All, has anyone tried "pbms tools v2.5" on their Hubbles. This is what I get: Can you post a link for the software and any steps etc what cable you used to connect to it
June 3, 20224 yr 1 hour ago, CJE said: Hypercut how do i get the firmware update. How do i load it Need to buy a USB to RS234 cable R500 Then phone Hubble a d they will email your the software
June 3, 20224 yr 2 hours ago, SeaSickMama said: Can you post a link for the software and any steps etc what cable you used to connect to it Link: https://www.ufo-battery.com/download-tools Instructions: https://www.ufo-battery.com/step-1-software-download-and-installation I am using the RS232 cable from Solar Assistant.
June 3, 20224 yr 4 hours ago, zsde said: I haven't had any real issues yet. Just don't like to see a mismatch. Must be my ocd and technical background. Getting the updated bin file and firmware update software from Hubble was very easy. Just emailed them and requested the update. Only I have a problem in that the loader seems to be faulty. I keep getting a bin file error. The bms tools however connects perfectly and gives me the info as in the screen shots. I am just waiting for another lone laptop to try and get it in to the hubbles again.
June 4, 20224 yr 5 hours ago, Gerry R said: I haven't had any real issues yet. Just don't like to see a mismatch. Must be my ocd and technical background. Getting the updated bin file and firmware update software from Hubble was very easy. Just emailed them and requested the update. Only I have a problem in that the loader seems to be faulty. I keep getting a bin file error. The bms tools however connects perfectly and gives me the info as in the screen shots. I am just waiting for another lone laptop to try and get it in to the hubbles again. Hi. The reason you are possible getting a bin file error is some older model AM2s won’t accept firmware version 2.05. It will however accept 1.46.
June 4, 20224 yr 9 hours ago, Gerry R said: I haven't had any real issues yet. Just don't like to see a mismatch. Must be my ocd and technical background. Getting the updated bin file and firmware update software from Hubble was very easy. Just emailed them and requested the update. Only I have a problem in that the loader seems to be faulty. I keep getting a bin file error. The bms tools however connects perfectly and gives me the info as in the screen shots. I am just waiting for another lone laptop to try and get it in to the hubbles again. The differing capacities worry me too. Would be interested to know if you have monitored the Battery capacities when running purely on battery. i.e. both batteries are fully charged and at 110/105A/h respectively. Will the 110A/h battery be discharged to 105A/h first before both batteries discharge at a similar rate or does the BMS ignore the difference and discharge both equally from the start?
June 4, 20224 yr https://www.aliexpress.com/i/32887307148.html https://www.aliexpress.com/item/32899447941.html Could this be same cable ? Edited June 4, 20224 yr by CraigL
June 4, 20224 yr 9 minutes ago, CraigL said: https://www.aliexpress.com/i/32887307148.html https://www.aliexpress.com/item/32899447941.html Could this be same cable ? With a bit of rewiring on the usb side they should work. The pin out on the RJ10 side is incorrect.
June 4, 20224 yr 24 minutes ago, zsde said: The differing capacities worry me too. Would be interested to know if you have monitored the Battery capacities when running purely on battery. i.e. both batteries are fully charged and at 110/105A/h respectively. Will the 110A/h battery be discharged to 105A/h first before both batteries discharge at a similar rate or does the BMS ignore the difference and discharge both equally from the start? Batteries just stating to charge now.
June 4, 20224 yr 4 hours ago, Leshen said: Hi. The reason you are possible getting a bin file error is some older model AM2s won’t accept firmware version 2.05. It will however accept 1.46. Does that mean that you have to load 1.46 first on both and then 2.05?
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.