diff options
| author | Kevin O'Connor <kevin@koconnor.net> | 2022-07-27 20:19:36 +0300 |
|---|---|---|
| committer | Kevin O'Connor <kevin@koconnor.net> | 2022-07-27 20:19:36 +0300 |
| commit | 61ab5b8db4194c99a5c61312c730ebc1c259c77e (patch) | |
| tree | fed940838da39d6a2e415a2c76847be031dd9227 | |
| parent | 4c6d70e652a2133db60cd7f2efa79d2533e45a47 (diff) | |
docs: Updates to CANBUS_protocol.md
Update the document with latest details.
Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
| -rw-r--r-- | docs/CANBUS_protocol.md | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/CANBUS_protocol.md b/docs/CANBUS_protocol.md index e1561eb59..8b6cc74fe 100644 --- a/docs/CANBUS_protocol.md +++ b/docs/CANBUS_protocol.md @@ -38,23 +38,23 @@ with a RESP_NEED_NODEID response message. The CMD_QUERY_UNASSIGNED message format is: `<1-byte message_id = 0x00>` -### CMD_SET_NODEID message +### CMD_SET_KLIPPER_NODEID message This command assigns a `canbus_nodeid` to the micro-controller with a given `canbus_uuid`. -The CMD_SET_NODEID message format is: +The CMD_SET_KLIPPER_NODEID message format is: `<1-byte message_id = 0x01><6-byte canbus_uuid><1-byte canbus_nodeid>` ### RESP_NEED_NODEID message The RESP_NEED_NODEID message format is: -`<1-byte message_id = 0x20><6-byte canbus_uuid>` +`<1-byte message_id = 0x20><6-byte canbus_uuid><1-byte set_klipper_nodeid = 0x01>` ## Data Packets A micro-controller that has been assigned a nodeid via the -CMD_SET_NODEID command can send and receive data packets. +CMD_SET_KLIPPER_NODEID command can send and receive data packets. The packet data in messages using the node's receive CAN bus id (`canbus_nodeid * 2 + 256`) are simply appended to a buffer, and when |