Add CAN Protocol Guide to Interfacing Wiki#254
Conversation
Added comprehensive documentation on Controller Area Network (CAN) protocol, including setup, usage, and debugging in robotics systems.
Controller Area Network (CAN)
4f6c490 to
ca3abce
Compare
nevalsar
left a comment
There was a problem hiding this comment.
Thanks for the contribution. Before this can be merged, please rebase this branch onto the latest master so the new PR validation workflow (recently added on master) runs on this PR.
I also found two required fixes:
-
Fix page filename/format
- The new file is currently
wiki/interfacing/CAN(no.mdextension, non-kebab-case). - Please rename it to a markdown page in repo style, for example
wiki/interfacing/controller-area-network-can.md, then update any internal references accordingly.
- The new file is currently
-
Discoverability integration
- Add the new page to
_data/navigation.ymlunder the Interfacing section. - Add the new page to
wiki/interfacing/index.mdwith a short summary.
- Add the new page to
Optional but recommended:
- Add a short “when to use this guide” paragraph near the top and trim/condense the references section to keep long-term maintenance manageable.
After rebasing and the above fixes, I can re-review quickly.
|
In addition to the above requested fixes,
|
Added guidance on when to use the CAN protocol for robotic systems, emphasizing its reliability and real-time performance. Removed an example use case to streamline the document.
|
I have renamed the file, updated the navigation, and merged the redundant sections as requested. Ready for a re-review |
|
I have made the required changes. Kindly check, Apologies for the delay
…On Mon, 11 May 2026 at 22:37, p-amyjiang ***@***.***> wrote:
*p-amyjiang* left a comment
(RoboticsKnowledgebase/roboticsknowledgebase.github.io#254)
<#254 (comment)>
In addition to the above requested fixes,
- Merge CAN Physical Layer and Hardware Requirements, and Example Use
in a Robotics System and Usage in Robotics Systems - the content in these
pairs of sections is somewhat redundant and repetitive.
—
Reply to this email directly, view it on GitHub
<#254 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BVQF36NYMSLECARFLDQA3NT42KE75AVCNFSM6AAAAACYLUYMT6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DIMRWHA4DGOBWGM>
.
You are receiving this because you authored the thread.Message ID:
<RoboticsKnowledgebase/roboticsknowledgebase.github.
***@***.***>
|
There was a problem hiding this comment.
I found three blocker issues still that need attention:
- Missing section-index discoverability entry:
wiki/interfacing/index.md(section list around lines 10-31) does not include this new CAN page. Please add it with a short summary.
Other issues - see below code suggestions.
@p-amyjiang for another pass on content review.
| - title: micro-ROS for ROS2 on Microcontrollers | ||
| url: /wiki/interfacing/microros-for-ros2-on-microcontrollers/ | ||
| - title: ROS 1 - ROS 2 Bridge | ||
| url: /wiki/interfacing/ros1_ros2_bridge/ |
There was a problem hiding this comment.
This path should stay kebab-case and match the existing page slug.
| url: /wiki/interfacing/ros1_ros2_bridge/ | |
| url: /wiki/interfacing/ros1-ros2-bridge/ |
| url: /wiki/interfacing/buffer-issues/ | ||
| - title: "CAN Protocol" | ||
| url: /wiki/interfacing/controller-area-network-can/ | ||
| url: /wiki/interfacing/ros1-ros2-bridge/ |
There was a problem hiding this comment.
This extra url line is currently nested under the CAN Protocol item and breaks the one-title/one-url structure. Please remove it.
| url: /wiki/interfacing/ros1-ros2-bridge/ |
|
|
||
| ## See Also | ||
|
|
||
| - [ROS2 QoS](/wiki/networking/ros2-qos/) |
There was a problem hiding this comment.
This link target is broken in current validation output. Please point to an existing page.
| - [ROS2 QoS](/wiki/networking/ros2-qos/) | |
| - [ROS2 QoS](/wiki/interfacing/ros1-ros2-bridge/) |
Added a new wiki article on Controller Area Network (CAN) covering:
This article is intended to provide a practical introduction to CAN communication in robotics.