1 PLIN-API Documentation - PEAK-System

3.3 The LIN Frame Entry PLIN API Documentation
always from the first entry of the table. While the schedule is being worked out, it is not possible to send frames using the
function LIN_Write ( see page 115).
• LIN_SuspendSchedule ( see page 136): This function is used to stop processing a Schedule Table. While the
processing of the schedule is suspended, it is possible for a client application to send frames using the function LIN_Write
( see page 115).
• LIN_ResumeSchedule ( see page 136): This function is used to resume the processing of a schedule which was
suspended before. The process start at the point where it was stopped.
Reading
The client can get messages received by the Master. If a received message meets the configured filter of a client (the filter
allows the message to pass through), the Master stores the message in the receive queue of the client. From there the
messages can be read, using the functions LIN_Read ( see page 114) and LIN_ReadMulti ( see page 114).
Writing
Basically, the master can operates in two states:
Scheduler Suspended
A client application connected to the Master sends data frames using the function LIN_Write ( see page 115). The calling
of this function determines the timing behavior on the bus. The values and options of the message passed to the function
control the data flow.
Scheduler Running
The timing behavior on the bus is provided by the current Schedule Table. The values and options of the Frame Entries
Table control the data flow. The Frame Table determines how the Slave responses to an ID. While the Master is running is
not possible to directly send messages to the LIN bus using the function LIN_Write ( see page 115).
The Frame Table will be used to control the data flow, because the Schedule Table does not contain any information about
frame lengths or directions. All configurations of a Frame Entry, with exception of the Single Shot flag, can be used to
configure the frames. The configuration of the Frames is done using the function LIN_SetFrameEntry ( see page 125) and
LIN_GetFrameEntry ( see page 126). The data sent from a Master, as Publisher, will be updated on the hardware using
the function LIN_UpdateByteArray ( see page 127).
See Also
LIN_InitializeHardware ( see page 116) (.NET: InitializeHardware ( see page 64))
LIN_GetStatus ( see page 139) (.NET: GetStatus ( see page 95))
LIN_Write ( see page 115) (.NET: Write ( see page 63))
LIN_SetSchedule ( see page 130) (.NET: SetSchedule ( see page 86))
LIN_StartSchedule ( see page 135) (.NET: StartSchedule ( see page 91))
LIN_SuspendSchedule ( see page 136) (.NET: SuspendSchedule ( see page 92))
LIN_ResumeSchedule ( see page 136) (.NET: ResumeSchedule ( see page 92))
LIN_SetFrameEntry ( see page 125) (.NET: SetFrameEntry ( see page 81))
LIN_UpdateByteArray ( see page 127) (.NET: UpdateByteArray ( see page 83))
3.3 The LIN Frame Entry
A LIN Frame Entry (represented by the structure TLINFrameEntry ( see page 29)) is used to configure the LIN Table. This
table contains 64 entries, from ID 0 to ID 63. When a hardware is configured as Slave (slave-mode), the entries in the LIN
Table determine how the hardware behaves, when a LIN Master sends a header with a determined ID.
10
3