doc:rfc_canraw-mode
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revisionNext revisionBoth sides next revision | ||
doc:rfc_canraw-mode [2014/03/02 06:47] – created admin | doc:rfc_canraw-mode [2014/08/31 11:41] – [Examples] admin | ||
---|---|---|---|
Line 58: | Line 58: | ||
Activate CANraw listen mode | Activate CANraw listen mode | ||
- | p 7 1 1 | + | p 7 1 x |
+ | |||
+ | where x is one of the output formats of the listen command. | ||
- | Hint: | + | Received |
- | + | ||
- | If there are already | + | |
==== Configuration ==== | ==== Configuration ==== | ||
Line 107: | Line 107: | ||
==== Examples ==== | ==== Examples ==== | ||
- | receiving | + | === Receiving Frames: === |
+ | |||
+ | Depending on the parameter x given at the listen format '' | ||
+ | |||
+ | == Vector Style Output (1) == | ||
+ | |||
+ | When having x=1, the output is like this | ||
# 170943 0x1f6 0x0 8 00 00 01 49 00 03 00 0a | # 170943 0x1f6 0x0 8 00 00 01 49 00 03 00 0a | ||
Line 113: | Line 120: | ||
# 170944 0x2fd 0x0 6 00 e5 e2 00 2e f0 | # 170944 0x2fd 0x0 6 00 e5 e2 00 2e f0 | ||
- | FIXME Sending frames: | ||
+ | == Vector Style Output from ISR (2) == | ||
+ | |||
+ | When having x=2, the output is like 1, but to have higher output performance (if needed), this output is already made in the CAN service routine. | ||
+ | |||
+ | |||
+ | == Vector Style Output from ISR (2) == | ||
+ | |||
+ | When having x=2, the output is like 1, but to have higher output performance (if needed), this output is already made in the CAN service routine. | ||
+ | |||
+ | == Lawicel Output from ISR (3) == | ||
+ | |||
+ | With x=3, the output comes also straight out of the CAN Interrupt service routine, having the so called Lawicel or SLCAN format: | ||
+ | |||
+ | T000007e1801a1a2a3a4a5a6a7deab | ||
+ | T000007e247202700000000000e293 | ||
+ | T000007e381010323334353637e67b | ||
+ | T000007e081112131415161718ea63 | ||
+ | T000007e1802b1b2b300000000ee4b | ||
+ | T000007e3821363738393a3b3cf233 | ||
+ | |||
+ | Which has the following format for 11-bit CAN Identifier | ||
+ | |||
+ | tiiindddddddddddddddd[ssss] | ||
+ | |||
+ | or | ||
+ | |||
+ | Tiiiiiiiindddddddddddddddd[ssss] \r | ||
+ | |||
+ | for 29 bit CANIDs, where the meaning is | ||
+ | |||
+ | ^ Field name ^ Length (Bytes) | ||
+ | | T / t | 1 | T= 29 bit CAN ID, t= 11 bit CAN ID | | ||
+ | | i | 2 / 4 | CAN ID either as 2 bytes (=11 bit) or 4 Bytes (=29 bit) | | ||
+ | | n | 1 | DLC (Number of Bytes) in Hex Format (" | ||
+ | | d | 0.. 8 | 0-8 Data Bytes in Hexadecimal writing | | ||
+ | | s | 2 | optional timestamp in hexadecimal writing (0..65535 ms) | | ||
+ | |||
+ | |||
+ | |||
+ | FIXME Sending frames: | ||
===== Implementation Details ===== | ===== Implementation Details ===== | ||
doc/rfc_canraw-mode.txt · Last modified: 2016/10/30 09:22 by admin