SNIP_CLASSIC_LIN_SECTION_9_5_1_2_With_answer_No_collision

9.5.1.2 With answer (No collision) The following use case (Figure 9.10) shows the transmission of an Event-triggered frame header with a response from one slave. The first call of the LinIf_MainFunction_<LinIfChannel.ShortName> requests transmission of the header. During the second call, the frame is under transmission. In the third call, the frame is finished (this call is called after the maximum frame length). The RequestFrame call in the diagram is the interface call to the Schedule Table Manager. The LinIf_MainFunction_<LinIfChannel.ShortName> gets the frame to send and the delay to the next frame. The AllocateRxBuffer call is to show that the storage of the received SDU is made in the LIN Driver and not in the LIN Interface. The ResolvePid call is to show that the received PID in the first data field is converted to the PduId that upper layer understands. «module» LSduR BSW Task (OS task or cyclic call) «module» Lin «module» LinIf ResolvePid() Lin_GetStatus(): LIN_RX_OK AllocateRxBuffer() LinIf_MainFunction_<ChannelId>() RequestFrame() Lin_SendFrame() LinIf_MainFunction_<ChannelId>() LinIf_MainFunction_<ChannelId>() CopyBuffer() Lin_GetStatus() LSduR_LinIfRxIndication() Figure 9.10: Event-triggered frame with answer (no collision) (master node)