device_drivers/can/can327.rst

1 .. SPDX-License-Identifier: (GPL-2.0-only OR BSD-3-Clause)
7 --------
14 -----------
26 -------------
33 order to fake full-duplex operation.
36 enough to implement simple request-response protocols (such as OBD II),
45 known limitations in older controllers and clones.
50 -----------
59 ----------------------------------
68            --debug \
69            --speed 38400 \
70            --eightbits \
71            --noparity \
72            --onestopbit \
73            --iflag -ICRNL,INLCR,-IXOFF \
88 500000 bit/s is a common rate for OBD-II diagnostics.
97 ------------------------------------
118 ----------------------
122 limitation (listed below) as well as manual testing.
127 - Command mode
128 - Reception mode
151 below on known limitations for details.
170 Once a frame has been sent and wait-for-reply mode is on (``ATR1``,
171 configured on ``listen-only=off``), or when the reply timeout expires
183 The ELM327 will receive both SFF and EFF frames - the current CAN
197 Known limitations of the controller
198 ------------------------------------
200 - Clone devices ("v1.5" and others)
221 - All versions
230   We don't have a way to get real-time notifications on CAN errors.
235 - Versions prior to 1.4b
243   command, and the "listen-only" CAN option will take effect.
246 - Versions prior to 1.4
249   change bitrate or SFF/EFF mode on-the-fly. This will have to be
254 - Versions prior to 1.3
258   on incoming data, as well as distinction of RTR frame lengths.
269 Known limitations of the driver
270 --------------------------------
272 - No 8/7 timing.
280 - No evaluation of command responses.
286   nevertheless. See the section on known limitations of the controller.
288 - No use of hardware CAN ID filtering
299 ------------------------------------------
324 ------------------------------
327 the bus. This is correct when it is plugged into a OBD-II socket, but