doc: isotp introduce CF abbreviation
Introduce the CF abbreviation as is done for other abbreviations (like FF) before first use. Signed-off-by: Mike Fikes <mike@fikesfarm.com>
This commit is contained in:
parent
76663444c1
commit
c59b04299f
1 changed files with 1 additions and 1 deletions
|
@ -28,7 +28,7 @@ Packets smaller or equal to seven bytes on Classical CAN are called
|
|||
single-frames (SF). They don't need to fragment and do not have any flow-control.
|
||||
|
||||
Packets larger than that are segmented into a first-frame (FF) and as many
|
||||
consecutive-frames as required. The FF contains information about the length of
|
||||
consecutive-frames (CF) as required. The FF contains information about the length of
|
||||
the entire payload data and additionally, the first few bytes of payload data.
|
||||
The receiving peer sends back a flow-control-frame (FC) to either deny,
|
||||
postpone, or accept the following consecutive frames.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue