SNIP_CLASSIC_LINIF_SECTION_9_6_Transport_Protocol_message_transmission

9.6 Transport Protocol message transmission The following diagram (Figure 9.13) shows the transmission of a TP message. The initiation of the message, the continuous copying of the data and the finish of the message are shown. The actual transmission of the MRF/SRF is not shown in the diagram and it has the same behavior as frame transmission. The TP message start is always initiated by requesting to send the TP message from the PDU Router. For LIN master nodes, the schedule table change to the diagnostic request schedule is requested if a schedule table change is enabled by the configuration parameter (see the parameter LinTpScheduleChangeDiag). The TP message is finished after the last N-PDU (SF or CF) is transmitted. The PDU Router is notified of the completion of the message transmission. For LIN master nodes, the schedule table change to the diagnostic response schedule is requested if a schedule table change is enabled by the configuration parameter (see the parameter LinTpScheduleChangeDiag). «module» LinIf BSW Task (OS task or cyclic call) «module» PduR «module» BswM «module» LinSM alt TP status [Starting TP message] [TP message transmission] [Ending TP message] loop opt Schedule table change is enabled opt Schedule table change is enabled PduR_LinTpTxConfirmation() LinIf_MainFunction_<ChannelId>() BswM_LinTp_RequestMode() LinIf_MainFunction_<ChannelId>() PduR_LinTpCopyTxData() LinIf_ScheduleRequest() LinSM_ScheduleRequest() LinTp_Transmit() BswM_LinTp_RequestMode() LinIf_ScheduleRequest() LinSM_ScheduleRequest() Figure 9.13: Transport Protocol message transmission