SNIP_CLASSIC_LINIF_SECTION_7_6_3_Diagnostics_Transport_Protocol

7.6.3 Diagnostics – Transport Protocol In the ISO 17987 specifications, the Transport Protocol (TP) is optional to implement. There are three types of diagnostics defined: • Signal Based diagnostics • User Defined diagnostics • Diagnostic Transport Layer It is only relevant to support the Diagnostic Transport Layer in the LIN Interface (and this is what is called the LIN TP). The Signal Based diagnostics has no meaning since signals are not defined here. The User Defined diagnostics shall not be used since all Diagnostic communication shall use the Diagnostic Transport Layer. [SWS_LinIf_00313] Upstream requirements: SRS_Lin_01579 ⌈The LIN Interface shall support the Diagnostic Transport Layer (defined in the ISO 17987 specifications) without the contained Diagnostic API which represents the LIN TP.⌋ The support of the LIN TP shall be configurable on/off to make the LIN Interface smaller when LIN TP is not used. [SWS_LinIf_00387] Upstream requirements: SRS_BSW_00171 ⌈The support for the LIN TP shall be pre-compile time configurable by the configuration parameter LinIfTpSupported.⌋ It is possible that the LIN Interface has more than one channel (connected to more than one LIN cluster). [SWS_LinIf_00314] Upstream requirements: SRS_Lin_01574 ⌈The LIN Interface shall support the transfer of a LIN TP message on each separate channel and they shall be independent of each other.⌋ The designer of the schedule tables has to include master request and slave response frames. Otherwise, LIN TP transfer stalls. The LIN TP is used to transport diagnostic service requests and responses. Functional diagnostic requests are possible in parallel to physical requests or responses. [SWS_LinIf_00062] Upstream requirements: SRS_Lin_01534, SRS_Lin_01592 ⌈LIN Interface shall support physical (only half-duplex) and functional TP connections on one channel at the same time, while only one physical TP connection can be active at a time.⌋