@peter I’m already in contact with the Victron devs.
This feature is still in development, that’s why it’s only available in Venus beta.
They will improve the feedback you get in VRM if/why an update is failed.
Having a way to know which FW file you need to use would be good.
I can’t imagine that it is possible to read out the board type via VRM, I don’t think that this info is available via BMS-Can.
That’s definitely a thing that Victron needs to communicate with Pylontech.
Especially for mixed systems where are US2000, 3000 and 5000 with different chips.
@OGPS Updating Pytes via VRM will be the next thing I will test, maybe next week.
The new US2000C and US3000C are using the same board, E2.
The US5000 is using E3.
So a combination of US3000 and US2000 is a little bit irrelevant, because are using the same hardware and only the Coulomb info is different.
Interesting would be a combination of US5000 and US3000/US2000, because it may be possible that if the FW is for US5000, only the US5000 (usually the master) to update and if the FW is for US3000/US2000, the master to pass it downwards and only US3000/US2000 to update.
Unfortunately I can’t test that because we don’t have a US5000.
I’ll have to check if one of our customers has such a combination or our former supplier.
I wouldn’t do that remotely, only if I can be there in person to fix it locally if needed.
OGPS
(Ed @ Off-Grid Power Systems - offgridps.com)
46
I don’t believe this available for Pytes yet. If you’ve heard otherwise, please let me know. I was just told by one of their engineers that they are working on it.
It’s not available for public beta testing now, but it is in development and I’m in contact with the devs to test it together.
1 Like
OGPS
(Ed @ Off-Grid Power Systems - offgridps.com)
48
Sweet! If you’d be so kind, please let me know how it goes. Do you know if they will support the feature on the older E-Box batteries in addition to the V-series batteries?
I currently don’t have much information and next week I will only be able to test it with the V5.
I think I will be able to test the Pi LV1, V12 and V15 in the next few weeks and maybe the E-Box next months or so.
OGPS
(Ed @ Off-Grid Power Systems - offgridps.com)
50
I sent an email to info@…. and ask whoever opened it to forward it to you. I’ll take the Pytes discussion offline so I don’t hijack this thread
I have successfully performed a remote firmware update on a system with two US3000C batteries using the C3 board (identified by xxxxxxxC3xxxxxxx in the serial number).
This was a different installation from the one previously mentioned. In this case, I manually updated the batteries to v2.4 about a year ago, at the time of deployment. I have now successfully updated them to v2.5 using the new feature. I used the US_E2_V2.5_Crc.bin file, renamed to xup.
I can’t verify that both batteries were updated, but VRM now reports v2.5 instead of v2.4 for the master battery.
Great feature Pylontech remote FW updates! Any rough indication when 3.70 - 74 would be available as official release? I cannot use Beta as the system is critical support a household with daily grid blackouts. However the Pylontech battery needs FW update and I cannot do it on site. The Pylontech US5000 doesn’t balance properly and therefor currently doesn’t charge highter than 65%.
