Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

vebus updater: Fix error 122 when updating Multi/Quattro firmware in combination with a VE.Bus BMS V2 #1341

Open
vejpasop opened this issue Sep 4, 2024 · 1 comment
Open

vebus updater: Fix error 122 when updating Multi/Quattro firmware in combination with a VE.Bus BMS V2 #1341

vejpasop opened this issue Sep 4, 2024 · 1 comment
Assignees
@vejpasop
Labels
bug high_prio

Comments

@vejpasop
Copy link
Collaborator

vejpasop commented Sep 4, 2024

Error 122 description: " The MK2/MK3 did not respond"
Affected systems: All systems with a VE.Bus BMS V2
Bug since Venus v3.41~1 and v3.50~7 (vbdup version v1.13)
introduced by fix for #1325

VictronConnect is also affected.

When updating a Multi/Quattro in a system with a VE.Bus BMS V2 the updater errors out after a time out while waiting for BMS response on a Multi/Quattro only command mistakenly being send to the BMS.
@vejpasop vejpasop self-assigned this Sep 4, 2024
@vejpasop
Copy link
Collaborator Author

vejpasop commented Sep 4, 2024

Fixed in vbdup v1.14 (on the Venus todo)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@vejpasop vejpasop

Labels
bug high_prio
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@vejpasop