Collision Resolving Schedule
LIN schedule that resolves a collision for this event-triggered entry (XNET LIN Schedule I/O Name). This property applies only when the entry's Type property is Event-triggered. When a collision occurs for the event-triggered entry in this schedule, the master must switch to the collision resolving schedule to transfer the unconditional frames successfully. If the XNET interface is acting as the master on the LIN cluster, NI-XNET automatically writes a schedule request for this collision resolving schedule. The collision resolving schedule's Run Mode must be Once. When the entry's Type property is any value other than Event-triggered, this property returns an empty schedule (invalid).
Delay
Time from the start of this entry (slot) to the start of the next entry (DBL seconds, fractional part used for milliseconds and microseconds).
Event Identifier
Identifier of the event-triggered entry. This identifier is unprotected (NI-XNET handles the protection). This property applies only when the entry's Type property is Event-triggered. This identifier is used for the event-triggered entry itself, and the 1st byte of the payload contains the protected identifier of the corresponding Unconditional frame. When the entry's Type property is any value other than Event-triggered, this property returns hexadecimal FFFFFFFF (invalid).
Frames
Array of frames for this LIN schedule entry (array of XNET Frame I/O Name). If the Type of the entry is Unconditional, this array contains one element, which is the single Unconditional frame. If the Type of the entry is Sporadic, this array contains one or more Unconditional frames. When multiple frames are pending in the NI-XNET interface, the order to transmit is determined by the order in this array. If the Type of the entry is Event-triggered, this array contains one or more Unconditional frames. When multiple frames are pending in the NI-XNET interface, the order to transmit is determined by the order in this array. If frames are pending in multiple ECUs, a collision will typically occur (see Collision Resolving Schedule).
Name (Short)
Short name of the LIN schedule entry (string). The I/O name (long name) contains qualifiers to ensure that it is unique, such as the database name. If you write this property, it changes both short and long name (see Detailed help).
Node Configuration:Free Format:Data Bytes
An array of 8 bytes containing raw data for LIN node configuration.
Schedule
LIN schedule that uses this entry (XNET LIN Schedule I/O Name). This LIN schedule is considered the parent of this entry.
Type
This property determines the mechanism used to transfer frames in this schedule entry (slot): - Unconditional: A single frame transfers in this slot. - Sporadic: Master transmits in this slot. The master can select among multiple frames to transmit. - Event-triggered: Multiple slaves can transmit. When a collision occurs, this is detected and resolved using a different schedule. - Node configuration: Schedule entry contains a node configuration service.

Parent topic: XNET Refnum

NI-XNET LabVIEW API Reference

Log in to get a better experience