aboutsummaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorKevin O'Connor <kevin@koconnor.net>2025-04-29 13:02:34 -0400
committerKevin O'Connor <kevin@koconnor.net>2025-04-29 13:02:34 -0400
commitb7c243db198c72170dad05c0f3da0aedac8ca5ff (patch)
treef78f4b2f4702eadbbbcc783fa75eb2f75e44a3e5 /docs
parent5b2f8104c7106a2126949dcb0502dff5491023b2 (diff)
downloadkutter-b7c243db198c72170dad05c0f3da0aedac8ca5ff.tar.gz
kutter-b7c243db198c72170dad05c0f3da0aedac8ca5ff.tar.xz
kutter-b7c243db198c72170dad05c0f3da0aedac8ca5ff.zip
docs: Note functioning canbus required even in bridge mode in CANBUS.md
Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
Diffstat (limited to 'docs')
-rw-r--r--docs/CANBUS.md9
1 files changed, 9 insertions, 0 deletions
diff --git a/docs/CANBUS.md b/docs/CANBUS.md
index 321f8e89..a31ba8ce 100644
--- a/docs/CANBUS.md
+++ b/docs/CANBUS.md
@@ -130,6 +130,15 @@ iface can0 can static
and the accelerometer all communicate via a single "USB to CAN bus"
interface.
+* It is only valid to use USB to CAN bridge mode if there is a
+ functioning CAN bus with at least one other node available (in
+ addition to the bridge node itself). Use a standard USB
+ configuration if the goal is to communicate only with the single USB
+ device. Using USB to CAN bridge mode without a fully functioning CAN
+ bus (including terminating resistors and an additional node) may
+ result in sporadic errors even when communicating with the bridge
+ node.
+
* A USB to CAN bridge board will not appear as a USB serial device, it
will not show up when running `ls /dev/serial/by-id`, and it can not
be configured in Klipper's printer.cfg file with a `serial:`