NBN ISO 11898-1:2024

< p class=" MsoBodyText" > < span lang=" EN-GB" > This document specifies the controller area network (CAN) data link layer (DLL) and the physical coding sub-layer (PCS). The CAN DLL features data fields of up to 2048 byte when the CAN extended data field length (XL) frame format is used.< / span>

< p class=" MsoBodyText" > < span lang=" EN-GB" > This document divides the CAN DLL into the logical link control (LLC) and the medium access control (MAC) sub-layers. The DLL’s service data unit (SDU), which interfaces the LLC and the MAC, is implemented by means of the LLC frame. The LLC frame also features the service data unit type (SDT) and the virtual CAN channel identifier (VCID), which provide higher-layer protocol configuration and identification information. How the higher-layer functions are handled is not specified in this document. There are five implementation options:< / span>

< p class=" ListNumber1" style=" mso-list: l0 level1 lfo1 " > < !-- [if !supportLists]--> < span lang=" EN-GB" style=" mso-fareast-font-family: Cambria mso-bidi-font-family: Cambria " > < span style=" mso-list: Ignore " > 1)< span style=" font: 7.0pt ' Times New Roman' " >        < / span> < / span> < / span> < !--[endif]--> < span lang=" EN-GB" > support of the CAN classic frame format only, not tolerating the CAN flexible data rate (FD) frame format < / span>

< p class=" ListNumber1" style=" mso-list: l0 level1 lfo1 " > < !-- [if !supportLists]--> < span lang=" EN-GB" style=" mso-fareast-font-family: Cambria mso-bidi-font-family: Cambria " > < span style=" mso-list: Ignore " > 2)< span style=" font: 7.0pt ' Times New Roman' " >        < / span> < / span> < / span> < !--[endif]--> < span lang=" EN-GB" > support of the CAN classic frame format and tolerating the CAN FD frame format < / span>

< p class=" ListNumber1" style=" mso-list: l0 level1 lfo1 " > < !-- [if !supportLists]--> < span lang=" EN-GB" style=" mso-fareast-font-family: Cambria mso-bidi-font-family: Cambria " > < span style=" mso-list: Ignore " > 3)< span style=" font: 7.0pt ' Times New Roman' " >        < / span> < / span> < / span> < !--[endif]--> < span lang=" EN-GB" > support of the CAN classic frame format and the CAN FD frame format < / span>

< p class=" ListNumber1" style=" mso-list: l0 level1 lfo1 " > < !-- [if !supportLists]--> < span lang=" EN-GB" style=" mso-fareast-font-family: Cambria mso-bidi-font-family: Cambria " > < span style=" mso-list: Ignore " > 4)< span style=" font: 7.0pt ' Times New Roman' " >        < / span> < / span> < / span> < !--[endif]--> < span lang=" EN-GB" > support of the CAN classic frame format, the CAN FD frame format and the CAN XL frame format < / span>

< p class=" ListNumber1" style=" mso-list: l0 level1 lfo1 " > < !-- [if !supportLists]--> < span lang=" EN-GB" style=" mso-fareast-font-family: Cambria mso-bidi-font-family: Cambria " > < span style=" mso-list: Ignore " > 5)< span style=" font: 7.0pt ' Times New Roman' " >        < / span> < / span> < / span> < !--[endif]--> < span lang=" EN-GB" > support of the CAN FD frame format for CAN FD light responders (Annex A).< / span>

< p class=" Note" > < span lang=" EN-GB" > NOTE< span style=" mso-tab-count: 1 " >             < / span> Nodes of the first option can communicate with nodes of the third and fourth option when only the CAN classic frame format is used. Nodes of the first option cannot communicate with nodes of the fifth option: any attempt at communication generates error frames. Therefore, new designs implementing the fourth option can communicate with all other nodes.< / span>