Table Of Contents

Auto Start?

Last Modified: September 16, 2019

Automatically starts the output session on the first call to XNET Write.

Data type: datatype_icon

Long Name: Auto Start?

Class: XNET Session

Permissions: Read/Write

For output sessions, as long as the first call to XNET Write contains valid data, you can leave this property at its default value of True. If you need to call XNET Write multiple times prior to starting the session, or if you are starting multiple sessions simultaneously, you can set this property to False. After calling XNET Write as desired, you can call XNET Start to start the session(s).

When automatic start is performed, it is equivalent to XNET Start with scope set to Normal, and it does not wait for a start trigger. This starts the session itself, and if the interface is not already started, it starts the interface also.

For input sessions, AutoStart? is implicitly set to True and cannot be set to False. Start always is performed within the first call to XNET Read (if not already started using XNET Start.

For Signal Input Waveform sessions, when calling XNET Read (Signal Waveform) for the first time on the session, the session will be started if it was not already. Stopping the session after the first start requires the session to be explicitly started in the future. This permits reading of the pending signal values without an implicit state transition, which would result in more signal values. This behavior is shared with frame input stream sessions when used with Ethernet interfaces. Other input session types, when used with CAN, FlexRay, or LIN interfaces, will implicitly start upon any call to XNET Read, not just the first; this behavior could be altered in a future release to match Signal Input Waveforms.

Where This Property Is Available:

Desktop OS: Windows

FPGA: Not supported

Web Server: Not supported in VIs that run in a web application

Recently Viewed Topics