Table Of Contents

stPMU External Sense Control (G Dataflow)

Last Modified: September 27, 2017

Connects or disconnects the channel specified in the channel parameter to or from the external sense terminal (either on the AUX I/O connector or the remote sense connector on the device front panel, depending on the value of the connector parameter).

spd-note-note
Note  

You can conduct an external sense operation on only one channel at a time with this node.

spd-note-note
Note  

Only the PXIe-6555 and PXIe-6556 support this nodes

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

channel

The channel on which to conduct the external sense.

This parameter only allows you to specify one channel at a time. Use PFI1 or PFI2 to specify a valid PFI channel.

datatype_icon

action

Parameter that selects whether to connect or disconnect the channel from the EXTERNAL SENSE terminal.

spd-note-note
Note  

On the PXIe-6556, selecting Disconnect disconnects both the AUX I/O and Remote Sense connectors regardless of which is connected currently.

Name Description
Connect

Connects the channel to the EXTERNAL SENSE terminal.

Disconnect

Disconnects the channel from the EXTERNAL SENSE terminal.

Default: Connect

datatype_icon

connector

Parameter that selects whether to access the PMU pins on the AUX I/O connector or the REMOTE SENSE connector.

Name Description
AUX I/O

Accesses the PMU pins on the AUX I/O connector. This is the default value.

Remote Sense

Accesses the PMU pins on the REMOTE SENSE connector.

Using this parameter with the PXIe-6555/6556

This parameter is valid only on the PXIe-6556, which has both the AUX I/O and REMOTE SENSE connectors. If you are operating an PXIe-6555, you must select Remote Sense because the PXIe-6555 does not have an AUX I/O connector. If you select AUX I/O while using an PXIe-6555, NI-HSDIO returns an error.

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.

Committing your session

If you have not yet committed your session, calling this node implicitly commits your session. If you have already committed your session by calling a node such as the Commit node, the Initiate node, the Read Waveform node, the Write Named Waveform node, or the other nodes, this node will not commit your session again.

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