SNIP_CLASSIC_LIN_SECTION_9_5_1_1_With_no_answer

9.5.1.1 With no answer The following use case (Figure 9.9) shows the transmission of an Event-triggered frame header and no response. 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. No slave responds to the Event-triggered frame header. The LinIf_MainFunction_<LinIfChannel.ShortName> recognizes this situation and takes no action since this is not considered to be a communication error. BSW Task (OS task or cyclic call) «module» Lin «module» LinIf Lin_GetStatus(): LIN_RX_NO_RESPONSE Lin_GetStatus() LinIf_MainFunction_<ChannelId>() RequestFrame() AllocateRxBuffer() Lin_SendFrame() LinIf_MainFunction_<ChannelId>() LinIf_MainFunction_<ChannelId>() Figure 9.9: Event-triggered frame with no answer (master node)