Differences

This shows you the differences between two versions of the page.

--- doc:rfc_canraw-mode [2014/08/31 12:33] – [Examples] admin
+++ doc:rfc_canraw-mode [2016/10/30 09:22] (current) – [Initialization] admin
@@ Line 40: / Line 40: @@
   p 8 4 0
-Select HS-CAN bus speed to 500kbit/s (for other bitrates please have a look to the firmware syntax here: [[brokenlink|The OOBD Firmware Syntax]])
+Select HS-CAN bus speed to 500kbit/s (for other bitrates please have a look to the firmware syntax here: [[doc:hw_commands|The OOBD Firmware Syntax]])
   p 8 3 3
@@ Line 80: / Line 80: @@
-The OOBD CAN raw format does not only allow single CAN frames, it can also send (if necessary) quite long telegram sequences. To do this, the data format is as follow:
+The OOBD CAN raw format does not only allow single CAN frames, it can also send (if necessary) several telegrams in one go. To do this, the data format is as follow:
 The data consists of one or more blocks:
@@ Line 98: / Line 98: @@
 Following the scheme above, there can be so much blocks send in one go as fit into the input buffer of 4095 bytes.
+The whole sequence is only sent once. For repetition, the application need to raise the command again.
@@ Line 169: / Line 172: @@
 ^ Field name  ^ Length (Bytes)  ^ Meaning ^
 |    SB    |      1          | Sync Byte (SB), Value 0xFF, **optional** |
-|    IB    |      1          | Bit 7 (MSB)=0 \\ Bit 5 = Extended CAN-ID \\ Bit 3-4 Errorflags \\ Bit 0-2 DLC |
+|    IB    |      1          | Bit 7 (MSB)=0 \\ Bit 6 = Extended CAN-ID \\ Bit 4-5 Errorflags \\ Bit 0-3 DLC |
 |    TS    |      2          | Time Stamp (0..65535 ms) |
 |    ID    |      2 / 4      | Extended / Normal CAN ID |