Table Of Contents

Export Signal (G Dataflow)

Version:
Last Modified: September 27, 2017

Routes signals (clocks, triggers, and events) to the output terminal you specify. Refer to your device documentation for valid signal destinations.

If you export a signal with this node and commit the session, the signal is routed to the output terminal you specify. If you then reconfigure the signal to have a different output terminal, the previous output terminal is tristated after the session is committed. If you change output terminal to Do Not Export when you commit the session, the previous output terminal is tristated.

connector_pane_image
datatype_icon

session in

Instrument session obtained from the Initialize Acquisition Session node, the Initialize Generation Session node, or the Initialize External Calibration node.

datatype_icon

signal identifier

The signal being exported.

You can select Script Trigger 0, Script Trigger 1, Script Trigger 2, Script Trigger 3, Marker 0, Marker 1, Marker 2, Marker 3, or None.

spd-note-note
Note  

When using the PXI-6544/6545/6547/6548, Script Trigger 3 and Marker 3 are unavailable.

datatype_icon

signal

The signal you want to export.

spd-note-note
Note  

Selecting Script Trigger or Marker Event requires a signal identifier to describe the particular signal.

Name Value Description
Sample Clock Device Sample clock.
Reference Clock Device Reference clock.
Start Trigger Device Start trigger.
Reference Trigger Device Reference trigger (dynamic acquisition only).
Advance Trigger Device Advance trigger (dynamic acquisition only)
Pause Trigger Device Pause trigger (dynamic generation only).
Script Trigger Device Script trigger (dynamic generation only-requires signal identifier to describe a particular Script trigger).
Stop Trigger Device Stop trigger (dynamic generation only).
Data Active Event Data Active event (dynamic generation only).
Ready for Start Event Ready for Start event.
Ready for Advance Event Ready for Advance event (dynamic acquisition only).
Marker Event Marker event (dynamic generation only-requires signal identifier to describe a particular marker).
End of Record Event End of Record event (dynamic acquisition only).
Onboard Ref Clock Device onboard Reference clock (PCI devices only).
datatype_icon

output terminal

The terminal where the signal is exported.

Name Value Description
Do not export signal The signal is not exported.
PFI 0 The signal is exported to the PFI 0 front panel connector.
PFI <1..3> The signal is exported to PFI <1..3> on the DDC front panel connector.
PXI Trigger Line/RTSI <0..7> The signal is exported to PXI trigger line or RTSI trigger line.
CLK OUT The signal is exported to the front panel CLK OUT connector.
DDC CLK OUT The signal is exported to the DDC CLK OUT pin on the DDC front panel connector.
datatype_icon

error in

Error conditions that occur before this node runs.

The node responds to this input according to standard error behavior.

Standard Error Behavior

Many nodes provide an error in input and an error out output so that the node can respond to and communicate errors that occur while code is running. The value of error in specifies whether an error occurred before the node runs. Most nodes respond to values of error in in a standard, predictable way.

error in does not contain an error error in contains an error
If no error occurred before the node runs, the node begins execution normally.

If no error occurs while the node runs, it returns no error. If an error does occur while the node runs, it returns that error information as error out.

If an error occurred before the node runs, the node does not execute. Instead, it returns the error in value as error out.

Default: No error

datatype_icon

session out

Handle that identifies the session in all subsequent node calls.

The session out parameter is obtained from the Initialize Acquisition Session node or the Initialize Generation Session node.

datatype_icon

error out

Error information.

The node produces this output according to standard error behavior.

Standard Error Behavior

Many nodes provide an error in input and an error out output so that the node can respond to and communicate errors that occur while code is running. The value of error in specifies whether an error occurred before the node runs. Most nodes respond to values of error in in a standard, predictable way.

error in does not contain an error error in contains an error
If no error occurred before the node runs, the node begins execution normally.

If no error occurs while the node runs, it returns no error. If an error does occur while the node runs, it returns that error information as error out.

If an error occurred before the node runs, the node does not execute. Instead, it returns the error in value as error out.

Unconfiguring signal routes

Any routes created within a session persist after the session closes to prevent signal glitching. To unconfigure signal routes created in previous sessions, set the reset instrument parameter in the Init Generation Session node or the Init Acquisition Session node to True or use the Reset Device node.

Where This Node Can Run:

Desktop OS: Windows

FPGA: Not supported

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


Recently Viewed Topics