This frame is transmitted by the master as required, so a collision cannot occur. If more than one slave task responds to the header in the same frame slot a collision will occur, and the master has to resolve the collision by requesting all associated unconditional frames before requesting the event-triggered frame again. If none of the slave tasks responds to the header the rest of the frame slot is silent and the header is ignored. A slave shall reply with an associated unconditional frame only if its data value has changed. The first data byte of the carried unconditional frame shall be equal to a protected identifier assigned to an event-triggered frame. The purpose of this is to increase the responsiveness of the LIN cluster without assigning too much of the bus bandwidth to the polling of multiple slave nodes with seldom occurring events. All subscribers of the unconditional frame shall receive the frame and make it available to the application (assuming no errors were detected). These always carry signals and their identifiers are in the range 0 to 59 (0x00 to 0x3b). A message contains the following fields:
0 kommentar(er)
