The End-to-End (E2E) protection mechanism protects the safety-related data exchange at run time against the effects of faults within the communication link. By using E2E communication protection mechanisms, faults in the communication link can be detected and handled at run time.

AUTOSAR-Specific E2E Protection

AUTOSAR specific E2E information is present inside an .arxml file. NI-VCOM supports E2EP01, E2EP02, and E2EP05. On Automotive Ethernet bus systems, NI-VCOM also supports E2EP0M, E2EP04, E2EP04M, E2EP06, and E2EP07. The following table describes which bus systems support the different AUTOSAR E2E mechanisms:
Table 5. AUTOSAR E2E Supported Bus Systems
E2E Profile TypeNI-XNET CANNI-XNET LINAutomotive Ethernet
E2EP01ASupportedSupported
E2EP01BSupportedSupported
E2EP01CSupportedSupported
E2EP02SupportedSupportedSupported
E2EP04SupportedSupported
E2EP04MSupported
E2EP05SupportedSupportedSupported
E2EP06Supported
E2EP07Supported
E2EP07MSupported
E2EP11ASupportedSupported
E2EP11CSupportedSupported

Checksum Protection

NI-VCOM supports additional checksum mechanisms. You can configure the checksum mechanisms using the RBSConfig tool. The following table describes which bus systems support the different checksums:
Table 6. Checksum Protection Supported Bus Systems
Cyclic Redundancy Check (CRC) Mechanism TypeNI-XNET CANNI-XNET LINNI-XNET FlexRay
J1850SupportedSupportedSupported
J1850 UserSupportedSupportedSupported
CustomSupportedSupportedSupported
AddAndComplementToOneSupportedSupported
AddWithCarrySupportedSupported
Honda (OEM Specific)Supported
Mazda (OEM Specific)Supported
Gac (OEM Specific) Supported
11BitAdd (OEM specific)Supported
XORSupportedSupportedSupported
XOR4BitSupportedSupported
CCITTSupportedSupportedSupported