This site is now in read-only archive mode. Please move all discussion, and create a new account at the new Victron Community site.
I am getting the following error if I try to update my Multiplus 2 12/3000.
I have a VEbus BMS V2.
An error occurred during the update process. Please try again later! Error Message: vbdup failed with exit code 122 Error: 733
I can't find anything online for this specific 122 code.
HI @Kees Oomen,
The closest I have is from this page - https://www.victronenergy.com/live/venus-os:remote_ve.bus_firmware_updates
"vbdup failed with exit code 123 One or more firmware file(s) supplied do not match the connected device models."
I know it's 123 and not the 122 you're seeing. But my first thought is that it is close.
Can you please give me some more details about how you are going about updating? Are you clicking the update button in VRM, or trying to upload a custom file?
Could you please post the VRM URL as well?
I was clicking the update button in VRM.
This is the link https://vrm.victronenergy.com/installation/299154/firmware-update
Hi @Kees Oomen,
I have some more information;
This exit code 122 is "The MK2/MK3 did not respond"
In this context this is internal MK3 that exists inside the GX device.
There are two suggested troubleshooting steps, first reboot the GX device.
If that doesn't help could you please go into the device list on the GX menu, go into your MultiPlus, and see if there is any mention of updating the MK3, or any other information about the MK3 such as version number, and then report back. It might also say MK2, but in this case MK2/MK3 are interchangeable.
Rebooting did not help.
I have MK2 version MK3
And MK2 version 1170216
i am getting exactly the same error. Vbdup failed error 122. error 733.
current version V510, updating to V552. multiplus 12/1600.
Hello,
Anybody has a solution for this problem? I have the same issue with my new Multiplus II 12/3000/120-32, version v508 to v552.
@Guy Stewart (Victron Community Manager) : I have also MK2 device MK3 and MK2 version 1170216
I also tried the update from https://vrm.victronenergy.com/installation/476392/firmware-update
Further I am using Ekrano GX version up to date v3.41 and VE.Bus BMS V2 version v113.
Hope anybody can help.
Thanks
Hi @robertpvose & @Shimanski,
Thank you for the additional reports, they will help to escalate a fix for this.
@Guy Stewart (Victron Community Manager),
Thank you for your response!
When and how can we expect a solution and will it be communicated here?
Depending on the fix, or if he needs to test a solution you will either get an email, or I will post an @ mention here.
There is no indication of how long that will take yet.
Hi @robertpvose
The charger is disabled until step 3.2 is completed here - https://www.victronenergy.com/live/venus-os:remote_ve.bus_firmware_updates
Hi @robertpvose , @Guy Stewart (Victron Community Manager) ,
My multiplus als doesn’t charge anymore after I performed the failed update. Luckily I had enough sun last days, so could do without grid charging until now. But now I have seen that it doesn’t work anymore. Where can I set the charge voltage back again? I have VE bus BMS V2 and Ekrano GX. Cannot find the charge voltage. I have a 200Ah victron lithium battery. I also installed a BMV 712 in the meantime. The voltage drops to 13V now, but charger stays in float and the DC current is 0.0. Also when I switch multiplus off and on, the charger goes into absorption, but also no DC current then.
I am on holiday, don’t have a laptop with me. Just restored a config file of 10 days ago, but that didn’t solve the charge issue…
I appreciate not much help to you now but I am very wary about any firmware upgrades Victron, Navionics or B&G when away cruising. Too much risk if it goes wrong .
Thanks for your response, I realize that indeed, but due to another issue, I did the upgrade just before we went on holiday.
I have restored a config file, from a timestamp before the upgrade, in the meantime, but that didn’t solve the issue. If I look back, I see that 4 days ago, the charger did put 12% of grid power into the battery, so it must be another issue, I guess. Thanks anyway for your help.
I’m encountering the same issue with my Multiplus 2 12/3000 and VEbus BMS V2. I’ve tried updating several times, but I keep getting the "vbdup failed with exit code 122" error. Have you found any solutions or additional information about this error code? Thanks in advance for any help!
Just as a sidenote, do you guys actually disconnect the VEbus bms for the update? I know the error message does not match a connected VEbus bms, but just a question
Disconnecting the BMS shouldn't be necessary with the V2:
But im also right. Taking the VEbus BMSv2 out of the loop allowed the update to go trough
Hi @Kees Oomen, @Chrigu, @abuhanzala, @robertpvose @Shimanski
Sorry for the inconvenience. R&D has found and fixed the bug.
However it requires an update to Venus OS and VictronConnect, so isn't available for you just yet.
The problem is related to the VE.Bus BMS V2. This bug was introduced in Venus v3.41 and VictronConnect v6.08.
Hi @Guy Stewart (Victron Community Manager),
Can I still use this site I saw a message that it’s in read-only mode and have to use https://victron.discourse.group/ now. Hope you can still help me here, as I am on holiday an run into serious trouble if my battery drains too much….
My multiplus als doesn’t charge anymore after I performed the failed update. Luckily I had enough sun last days, so could do without grid charging until now. But now I have seen that it doesn’t work anymore. Where can I set the charge voltage back again? I have VE bus BMS V2 and Ekrano GX. Cannot find the charge voltage. I have a 200Ah victron lithium battery. I also installed a BMV 712 in the meantime. The voltage drops to 13V now, but charger stays in float and the DC current is 0.0. Also when I switch multiplus off and on, the charger goes into absorption, but also no DC current then.
I am on holiday, don’t have a laptop with me. Just restored a config file of 10 days ago, but that didn’t solve the charge issue…
Hi @Shimanski,
Please create the new post on https://victron.discourse.group/ - and @ mention me if you can - this is no longer a reliable place to discuss.
