CAN bus spamming

[sshenker85]

I have noticed the CANBUS being spammed with message ID 0x917 regardless of status message selection or update rate. Is this an intended function for a certain operating condition? Not sure why this is the case, please let me know if I am missing something.

[Huangney]

Same my friend😭, have you solved this problem? If I don't set the option "CAN_Status_Message_Mode" as "CAN_Status_Disabled", My CAN bus is spammed with message EXTID 0x965 regardless of rate or other mode selections. I only knows that the 9 means status_1, and the 0x65 is the CAN_ID of my VESC Driver. BUT WHY CAN BUS WAS ALWAYS FULL, It annoyed me foy days.

[sshenker85]

Yes! You need at least 1 reciever on the bus to acknowledge the CAN message. Steven Shenker

…

On Thu, 17 Oct 2024 at 11:14, Huangney ***@***.***> wrote: Same my friend😭, have you solved this problem? If I don't set the option "CAN_Status_Message_Mode" as "CAN_Status_Disabled", My CAN bus is spammed with message EXTID 0x965 regardless of rate of other mode selections. I only knows that the 9 means status_1, and the 0x65 is the CAN_ID of my VESC Driver. BUT WHY CAN BUS WAS ALWAYS FULL, It annoyed me foy days. IMG_1962.JPG (view on web) <https://github.com/user-attachments/assets/b5c531b5-28a1-477f-a58b-c43610296309> — Reply to this email directly, view it on GitHub <#715 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKLVRFP6RIACMSCPQXKUFZ3Z355WZAVCNFSM6AAAAABQDIT32GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJYHE4TMMJUGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>