VeriStand .NET API Reference

Table of Contents

LINPort.InlineIncoming Property

Gets or sets whether to process incoming frames inline with the VeriStand Engine's Primary Control Loop (PCL). By default, NI VeriStand runs incoming and outgoing frame sessions asynchronously, or in a parallel loop to the PCL.

Namespace: NationalInstruments.VeriStand.SystemDefinitionAPI
Assembly: NationalInstruments.VeriStand.SystemDefinitionAPI (in NationalInstruments.VeriStand.SystemDefinitionAPI.dll) Version: 2013.0.0.0 (2013.0.0.0)
Visual Basic (Declaration)
Public Overridable Property InlineIncoming As Boolean
C#
public virtual bool InlineIncoming { get; set; }
Visual C++
public:
virtual property bool InlineIncoming {
	bool get ();
	void set (bool value);
}

Property Value

A Boolean that indicates whether incoming frames are processed inline with the PCL (true (True in Visual Basic)) or asynchronously (false (False in Visual Basic)).

Remarks

By default, NI VeriStand runs incoming and outgoing frame sessions as asynchronous custom devices that execute in separate loops from the PCL. Therefore, there is a 1-cycle delay when reading and writing channel values between the frame session loops and the rest of the system. You can inline frames to eliminate this delay by running the session loops as inline hardware interface custom devices, where NI VeriStand uses the loop rate to calculate the decimation factor for calls to the session loop.

Inlining frames is useful if you need to reduce latency when getting XNET data from your system, or if you want to correlate frame data with channel data. However, it can increase CPU usage and, if the XNET loops take too long to execute, delay the execution of the Primary Control Loop.

See Also

Log in to get a better experience