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

Message handled framework #9

Open
jmnc2 opened this issue Jul 16, 2024 · 0 comments
Open

Message handled framework #9

jmnc2 opened this issue Jul 16, 2024 · 0 comments
Labels
enhancement New feature or request
Milestone

Comments

@jmnc2
Copy link
Contributor

jmnc2 commented Jul 16, 2024

The protocol is message based and does not have an address but just broadcasts the message CAN network style. Maybe use the RTR and add some functions to help automatically reply when a unit that can handle the message receives it.

For example: If the unit at a light switch sends a message to say the light switch has turned on. Then the controller unit could reply saying message received. The sender then knows the message got through, and the controller was not too busy to get it.

If RTR is used, any new message would automatically have priority.

This would only be needed when the additional Ack bit that is acknowledged in the message frame is too complicated to do in an interrupt or in time, for example. If the controller could always handle message IDs that could be filtered with a bit mask, in the example, then this should not be needed.

@jmnc2 jmnc2 added the enhancement New feature or request label Jul 16, 2024
@jmnc2 jmnc2 added this to the Second Beta milestone Jul 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Development

No branches or pull requests

1 participant