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

Missing NMT broadcast #2

Open
JoostHendriks opened this issue Jan 11, 2024 · 2 comments
Open

Missing NMT broadcast #2

JoostHendriks opened this issue Jan 11, 2024 · 2 comments

Comments

@JoostHendriks
Copy link
Contributor

The send_nmt_command is expecting a state change for a single controller. In order to change the nmt state of all controllers in the network a broadcast can be used by sending 0 as node id. But there is no function in the library to do this.

@de-vri-es
Copy link
Owner

Thanks for reporting the issue! To be clear, we should expect a state change message for all controllers?

Should we use a timeout to determine when all controllers should have responded?

@JoostHendriks
Copy link
Contributor Author

Depends on the use case. If we use it before initiailization we don't know which controllers are connected yet (case I will be using it for). If we do, we can use the individual one. But there maybe are use cases on which you want to do a broadcast when the controllers are initialized. EMCY stop maybe?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants