Cluster
Cluster that uses this LIN schedule (XNET Cluster I/O Name). This cluster is considered the parent of this schedule.
Comment
Comment describing the LIN schedule (string).
Configuration Status
Configuration status of the LIN schedule. This property is used only if you change the Database property Show Invalid From Open? from false (default) to true.
Entries
Array of entries for this LIN schedule (array of XNET LIN Schedule Entry I/O Name). Each entry's position in this array specifies the position in the schedule. The database file and/or the order that you create entries at runtime determine the position.
Name (Short)
Short name of the LIN schedule (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).
Priority
Priority of this run-once LIN schedule when multiple run-once schedules are pending for execution. The valid range for this property is 1-254. Lower values correspond to higher priority. This property applies only when the Run Mode property is Once. Run-once schedule requests are queued up for execution based on this Priority. When all run-once schedules have completed, the master returns to the previously running continuous schedule (or null). Run-continuous schedule requests are not queued. Only the most recent run-continuous schedule is used, and it executes only if no run-once schedule is pending. Therefore, a run-continuous schedule has an effective priority of 255, but this property is not used. Null schedule requests take effect immediately, and supercede any running run-once or run-continuous schedule. The queue of pending run-once schedule requests is flushed (emptied without runnning them). Therefore, a null schedule has an effective priority of 0, but this property is not used. This property is not read from the database file. After opening a database, it returns the default value of 42, but you can change the property.
Run Mode
This property specfies how the master runs this schedule: - Continuous: Master runs the schedule continuously. When the last entry executes, the schedule starts again with the first entry. - Once: Master runs the schedule once (all entries), then returns to the previously running continuous schedule (or null). If requests are submitted for multiple run-once schedules, each run-once executes in succession based on its Priority, then the master returns to the continuous schedule (or null). - Null: All communication stops immediately. A schedule with this run mode is called a Null Schedule. This property is not read from the database file. After opening a database, it returns the default value, but you can change the property. If the schedule is configured as the Collision Resolving Schedule property of an event-triggered XNET LIN Schedule Entry, the default is Once. Otherwise, the default is Continuous.

Parent topic: XNET Refnum

NI-XNET LabVIEW API Reference

Log in to get a better experience