SNIP_CLASSIC_LIN_SECTION_9_5_1_3_With_collision

9.5.1.3 With collision The following use case (Figure 9.11) shows the transmission of an Event-triggered frame header with a response from more than one slave. This means that there is a collision in the response field. 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 local function ChangeToCollisionResolvingSchedule switches to the corresponding collision resolving schedule table to enable sporadic transmission from slave. BSW Task (OS task or cyclic call) «module» Lin «module» LinIf Lin_GetStatus(): LIN_RX_ERROR LinIf_MainFunction_<ChannelId>() Lin_GetStatus() Lin_SendFrame() ChangeToCollisionResolvingSchedule() LinIf_MainFunction_<ChannelId>() AllocateRxBuffer() LinIf_MainFunction_<ChannelId>() RequestFrame() Figure 9.11: Event-triggered frame with collision (master node)