-
Notifications
You must be signed in to change notification settings - Fork 0
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
Can Message Rate Limiting #132
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
your google doc
Core/Src/compute.c
Outdated
0x156; // 0x0A is the dcl id, 0x22 is the device id set by us | ||
mc_msg.len = 8; | ||
memcpy(mc_msg.data, &discharge_data, sizeof(discharge_data)); | ||
bms_can_msgs[DISCHARGE].len = 8; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The length of the message should be defined where the CAN message is defined now where it should be sent.
charge_msg.id = | ||
CHARGE_CANID; // 0x0A is the dcl id, 0x157 is the device id set by us | ||
|
||
can_msg_t acc_status_msg; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You should put message lengths in the config since they do not change and are properties of the message.
This is gonna hella conflict with my CAN busy fixups, so you merge first and ill refactor it. |
b62c898
to
f3e444b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It works
Changes
added an interface to rate limit can messages
Closes #127