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.

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

Instance number changes at reboot #547

Closed
drtinaz opened this issue Apr 24, 2023 · 2 comments
Closed

Instance number changes at reboot #547

drtinaz opened this issue Apr 24, 2023 · 2 comments
Labels
duplicate This issue or pull request already exists

Comments

@drtinaz
Copy link

drtinaz commented Apr 24, 2023

My apologies if this has been covered elsewhere. I searched but didn't find anything.
Describe the bug
If the cerbo is reboot for any reason, often times the bms gets assigned a different instance number which then requires changing settings and reconnecting nodes in node red.

To Reproduce
Steps to reproduce the behavior:
Reboot cerbo, then battery alarm 'low voltage' because bms has been assigned a different number. Seems to bounce back and forth between 1 and 2.

Expected behavior
I would expect the bms to always be assigned the same number.

Screenshots
If applicable, add screenshots to help explain your problem.

VenusOS (please complete the following information):

  • Device type: cerbo gx
  • Firmware Version: same behavior on 2.93 and beta 3.00~32

Battery/BMS (please complete the following information):

  • BMS/Battery type: Daly
  • Cells: 8
  • Interface: Daly uart to usb

Additional context
I have a rs485 to USB adapter plugged into the first USB port which runs a external relay board. Plugged into the second USB port is a powered USB hub with a mppt on ve.direct to USB, a USb bt dongle, tank140, and the uart Daly adapter. All other devices survive reboots with no issues.

I have posted this issue on the victron board and victrons response is that it is a bms driver issue.

@ramack
Copy link
Contributor

ramack commented Apr 24, 2023

I face similar problems and think that we should allow a dedicated mapping from serialnumbers as read by the low level drivers to instance numbers. That would also help in setups with multiple batteries.

@mr-manuel
Copy link
Collaborator

Hello,

please see #481 and #100.

@mr-manuel mr-manuel added the duplicate This issue or pull request already exists label Apr 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

3 participants