VeriStand .NET API Reference

CANPort.InlineOutgoing Property

Gets or sets whether to process outgoing 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 InlineOutgoing As Boolean
C#
public virtual bool InlineOutgoing { get; set; }
Visual C++
public:
virtual property bool InlineOutgoing {
	bool get ();
	void set (bool value);
}

Property Value

true (True in Visual Basic) if outgoing frames are processed inline with the PCL. false (False in Visual Basic) if they are processed asynchronously.

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, inlining frames can increase CPU usage, and if the XNET loops take too long to execute, delay the execution of the PCL.

See Also

Log in to get a better experience