-
Notifications
You must be signed in to change notification settings - Fork 52
NI DCPOWER Trigger Attributes
- NIDCPOWER_ATTRIBUTE_START_TRIGGER_TYPE
- NIDCPOWER_ATTRIBUTE_EXPORTED_START_TRIGGER_OUTPUT_TERMINAL
- NIDCPOWER_ATTRIBUTE_DIGITAL_EDGE_START_TRIGGER_EDGE
- NIDCPOWER_ATTRIBUTE_DIGITAL_EDGE_START_TRIGGER_INPUT_TERMINAL
- NIDCPOWER_ATTRIBUTE_SOURCE_TRIGGER_TYPE
- NIDCPOWER_ATTRIBUTE_EXPORTED_SOURCE_TRIGGER_OUTPUT_TERMINAL
- NIDCPOWER_ATTRIBUTE_DIGITAL_EDGE_SOURCE_TRIGGER_EDGE
- NIDCPOWER_ATTRIBUTE_DIGITAL_EDGE_SOURCE_TRIGGER_INPUT_TERMINAL
- NIDCPOWER_ATTRIBUTE_MEASURE_TRIGGER_TYPE
- NIDCPOWER_ATTRIBUTE_EXPORTED_MEASURE_TRIGGER_OUTPUT_TERMINAL
- NIDCPOWER_ATTRIBUTE_DIGITAL_EDGE_MEASURE_TRIGGER_EDGE
- NIDCPOWER_ATTRIBUTE_DIGITAL_EDGE_MEASURE_TRIGGER_INPUT_TERMINAL
- NIDCPOWER_ATTRIBUTE_SEQUENCE_ADVANCE_TRIGGER_TYPE
- NIDCPOWER_ATTRIBUTE_EXPORTED_SEQUENCE_ADVANCE_TRIGGER_OUTPUT_TERMINAL
- NIDCPOWER_ATTRIBUTE_DIGITAL_EDGE_SEQUENCE_ADVANCE_TRIGGER_EDGE
- NIDCPOWER_ATTRIBUTE_DIGITAL_EDGE_SEQUENCE_ADVANCE_TRIGGER_INPUT_TERMINAL
- NIDCPOWER_ATTRIBUTE_PULSE_TRIGGER_TYPE
- NIDCPOWER_ATTRIBUTE_EXPORTED_PULSE_TRIGGER_OUTPUT_TERMINAL
- NIDCPOWER_ATTRIBUTE_DIGITAL_EDGE_PULSE_TRIGGER_EDGE
- NIDCPOWER_ATTRIBUTE_DIGITAL_EDGE_PULSE_TRIGGER_INPUT_TERMINAL
- NIDCPOWER_ATTRIBUTE_SHUTDOWN_TRIGGER_TYPE
- NIDCPOWER_ATTRIBUTE_DIGITAL_EDGE_SHUTDOWN_TRIGGER_EDGE
- NIDCPOWER_ATTRIBUTE_DIGITAL_EDGE_SHUTDOWN_TRIGGER_INPUT_TERMINAL
Numeric Value | Data type |
Access | Applies to | Coercion | High-Level Functions |
---|---|---|---|---|---|
1150021 | ViInt32 | R/W | Channel | None | niDCPower_ConfigureDigitalEdgeStartTriggerWithChannels niDCPower_ConfigureSoftwareEdgeStartTriggerWithChannels niDCPower_DisableStartTriggerWithChannels |
Specifies the behavior of the Start trigger.
!Note | Note This attribute is not supported by all devices. Refer to Supported Attributes by Device for information about supported devices. |
---|---|
Defined Values: |
NIDCPOWER_VAL_NONE (1012) | No trigger is configured. |
---|---|
NIDCPOWER_VAL_DIGITAL_EDGE (1014) | The data operation starts when a digital edge is detected. |
NIDCPOWER_VAL_SOFTWARE_EDGE (1015) | The data operation starts when a software trigger occurs. |
Default Value: NIDCPOWER_VAL_NONE |
!Note | Note To specify a channel name when accessing this attribute, you must first initialize the session using the niDCPower_InitializeWithIndependentChannels function. |
---|
Numeric Value | Data type |
Access | Applies to | Coercion | High-Level Functions |
---|---|---|---|---|---|
1150024 | ViString | R/W | Channel | None | niDCPower_ExportSignalWithChannels |
Specifies the output terminal for exporting the Start trigger.
Refer to the Device Routes tab in Measurement & Automation Explorer (MAX) for a list of the terminals available on your device. For the PXIe-4147, PXIe-4162, and PXIe-4163, refer to the Signal Routing topic for the instrument to determine which routes are available (this information is not available on a Device Routes tab in MAX).
Specify the output terminal using the form /Dev1/PXI_Trig0, where Dev1 is the instrument and PXI_Trig0 is the terminal.
!Note | Note This attribute is not supported by all devices. Refer to Supported Attributes by Device for information about supported devices. |
---|
!Note | Note To specify a channel name when accessing this attribute, you must first initialize the session using the niDCPower_InitializeWithIndependentChannels function. |
---|
Numeric Value | Data type |
Access | Applies to | Coercion | High-Level Functions |
---|---|---|---|---|---|
1150022 | ViInt32 | R/W | Channel | None | niDCPower_ConfigureDigitalEdgeStartTriggerWithChannels |
Specifies whether to configure the Start trigger to assert on the rising or falling edge.
!Note | Note This attribute is not supported by all devices. Refer to Supported Attributes by Device for information about supported devices. |
---|---|
Defined Values: |
NIDCPOWER_VAL_RISING (1016) | Asserts the trigger on the rising edge of the digital signal. |
---|---|
NIDCPOWER_VAL_FALLING (1017) | Asserts the trigger on the falling edge of the digital signal. |
Default Value: NIDCPOWER_VAL_RISING |
!Note | Note To specify a channel name when accessing this attribute, you must first initialize the session using the niDCPower_InitializeWithIndependentChannels function. |
---|
Numeric Value | Data type |
Access | Applies to | Coercion | High-Level Functions |
---|---|---|---|---|---|
1150023 | ViString | R/W | Channel | None | niDCPower_ConfigureDigitalEdgeStartTriggerWithChannels |
Specifies the input terminal for the Start trigger. Use this attribute only when the NIDCPOWER_ATTRIBUTE_START_TRIGGER_TYPE attribute is set to NIDCPOWER_VAL_DIGITAL_EDGE.
!Note | Note This attribute is not supported by all devices. Refer to Supported Attributes by Device for information about supported devices. |
---|---|
You can specify any valid terminal for this attribute, and the driver will create a route between it and the Start trigger terminal at Commit. Valid terminals are listed in Measurement & Automation Explorer under the Device Routes tab. For the PXIe-4147, PXIe-4162, and PXIe-4163, refer to the Signal Routing topic for the instrument to determine which routes are available (this information is not available on a Device Routes tab in MAX). |
Specify the output terminal using the form /Dev1/PXI_Trig0, where Dev1 is the instrument and PXI_Trig0 is the terminal. The input terminal can also be a terminal from another instrument. For example, you can set the input terminal on Dev1 to be /Dev2/Engine0/SourceCompleteEvent, where Engine0 is channel 0.
!Note | Note You must specify the input terminal for a PXI-4132 using the form /Dev1/PXI_Trig0, where Dev1 is a PXI-4132 and PXI_Trig0 is the terminal. |
---|
!Note | Note To specify a channel name when accessing this attribute, you must first initialize the session using the niDCPower_InitializeWithIndependentChannels function. |
---|
Numeric Value | Data type |
Access | Applies to | Coercion | High-Level Functions |
---|---|---|---|---|---|
1150030 | ViInt32 | R/W | Channel | None | niDCPower_ConfigureDigitalEdgeSourceTriggerWithChannels niDCPower_ConfigureSoftwareEdgeSourceTriggerWithChannels niDCPower_DisableSourceTriggerWithChannels |
Specifies the behavior of the Source trigger.
!Note | Note This attribute is not supported by all devices. Refer to Supported Attributes by Device for information about supported devices. |
---|
!Note | Note To specify a channel name when accessing this attribute, you must first initialize the session using the niDCPower_InitializeWithIndependentChannels function. |
---|---|
Defined Values: |
NIDCPOWER_VAL_NONE (1012) | No trigger is configured. |
---|---|
NIDCPOWER_VAL_DIGITAL_EDGE (1014) | The data operation starts when a digital edge is detected. |
NIDCPOWER_VAL_SOFTWARE_EDGE (1015) | The data operation starts when a software trigger occurs. |
Default Value: NIDCPOWER_VAL_NONE |
Numeric Value | Data type |
Access | Applies to | Coercion | High-Level Functions |
---|---|---|---|---|---|
1150033 | ViString | R/W | Channel | None | niDCPower_ExportSignalWithChannels |
Specifies the output terminal for exporting the Source trigger.
Refer to the Device Routes tab in MAX for a list of the terminals available on your device. For the PXIe-4147, PXIe-4162, and PXIe-4163, refer to the Signal Routing topic for the instrument to determine which routes are available (this information is not available on a Device Routes tab in MAX).
Specify the output terminal using the form /Dev1/PXI_Trig0, where Dev1 is the instrument and PXI_Trig0 is the terminal.
!Note | Note This attribute is not supported by all devices. Refer to Supported Attributes by Device for information about supported devices. |
---|
!Note | Note To specify a channel name when accessing this attribute, you must first initialize the session using the niDCPower_InitializeWithIndependentChannels function. |
---|
Numeric Value | Data type |
Access | Applies to | Coercion | High-Level Functions |
---|---|---|---|---|---|
1150031 | ViInt32 | R/W | Channel | None | niDCPower_ConfigureDigitalEdgeSourceTriggerWithChannels |
Specifies whether to configure the Source trigger to assert on the rising or falling edge.
!Note | Note This attribute is not supported by all devices. Refer to Supported Attributes by Device for information about supported devices. |
---|
!Note | Note To specify a channel name when accessing this attribute, you must first initialize the session using the niDCPower_InitializeWithIndependentChannels function. |
---|---|
Defined Values: |
NIDCPOWER_VAL_RISING (1016) | Asserts the trigger on the rising edge of the digital signal. |
---|---|
NIDCPOWER_VAL_FALLING (1017) | Asserts the trigger on the falling edge of the digital signal. |
Default Value: NIDCPOWER_VAL_RISING |
Numeric Value | Data type |
Access | Applies to | Coercion | High-Level Functions |
---|---|---|---|---|---|
1150032 | ViString | R/W | Channel | None | niDCPower_ConfigureDigitalEdgeSourceTriggerWithChannels |
Specifies the input terminal for the Source trigger. Use this attribute only when the NIDCPOWER_ATTRIBUTE_SOURCE_TRIGGER_TYPE attribute is set to NIDCPOWER_VAL_DIGITAL_EDGE.
!Note | Note This attribute is not supported by all devices. Refer to Supported Attributes by Device for information about supported devices. |
---|---|
You can specify any valid input terminal for this attribute, and the driver will create a route between it and the Source trigger terminal at Commit. Valid terminals are listed in Measurement & Automation Explorer under the Device Routes tab. For the PXIe-4147, PXIe-4162, and PXIe-4163, refer to the Signal Routing topic for the instrument to determine which routes are available (this information is not available on a Device Routes tab in MAX). |
Specify the output terminal using the form /Dev1/PXI_Trig0, where Dev1 is the instrument and PXI_Trig0 is the terminal. The input terminal can also be a terminal from another instrument. For example, you can set the input terminal on Dev1 to be /Dev2/Engine0/SourceCompleteEvent, where Engine0 is channel 0.
!Note | Note You must specify the input terminal for a PXI-4132 using the form /Dev1/PXI_Trig0, where Dev1 is a PXI-4132 and PXI_Trig0 is the terminal. |
---|
!Note | Note To specify a channel name when accessing this attribute, you must first initialize the session using the niDCPower_InitializeWithIndependentChannels function. |
---|
Numeric Value | Data type |
Access | Applies to | Coercion | High-Level Functions |
---|---|---|---|---|---|
1150034 | ViInt32 | R/W | Channel | None | niDCPower_ConfigureDigitalEdgeMeasureTriggerWithChannels niDCPower_ConfigureSoftwareEdgeMeasureTriggerWithChannels |
Specifies the behavior of the Measure trigger.
!Note | Note This attribute is not supported by all devices. Refer to Supported Attributes by Device for information about supported devices. |
---|
!Note | Note To specify a channel name when accessing this attribute, you must first initialize the session using the niDCPower_InitializeWithIndependentChannels function. |
---|---|
Defined Values: |
NIDCPOWER_VAL_DIGITAL_EDGE (1014) | The data operation starts when a digital edge is detected. |
---|---|
NIDCPOWER_VAL_SOFTWARE_EDGE (1015) | The data operation starts when a software trigger occurs. |
Default Value: NIDCPOWER_VAL_DIGITAL_EDGE |
Numeric Value | Data type |
Access | Applies to | Coercion | High-Level Functions |
---|---|---|---|---|---|
1150037 | ViString | R/W | Channel | None | niDCPower_ExportSignalWithChannels |
Specifies the output terminal for exporting the Measure trigger.
Refer to the Device Routes tab in Measurement & Automation Explorer for a list of the terminals available on your device. For the PXIe-4147, PXIe-4162, and PXIe-4163, refer to the Signal Routing topic for the instrument to determine which routes are available (this information is not available on a Device Routes tab in MAX).
Specify the output terminal using the form /Dev1/PXI_Trig0, where Dev1 is the instrument and PXI_Trig0 is the terminal.
!Note | Note This attribute is not supported by all devices. Refer to Supported Attributes by Device for information about supported devices. |
---|
!Note | Note To specify a channel name when accessing this attribute, you must first initialize the session using the niDCPower_InitializeWithIndependentChannels function. |
---|
Numeric Value | Data type |
Access | Applies to | Coercion | High-Level Functions |
---|---|---|---|---|---|
1150035 | ViInt32 | R/W | Channel | None | niDCPower_ConfigureDigitalEdgeMeasureTriggerWithChannels |
Specifies whether to configure the Measure trigger to assert on the rising or falling edge.
!Note | Note This attribute is not supported by all devices. Refer to Supported Attributes by Device for information about supported devices. |
---|
!Note | Note To specify a channel name when accessing this attribute, you must first initialize the session using the niDCPower_InitializeWithIndependentChannels function. |
---|---|
Defined Values: |
NIDCPOWER_VAL_RISING (1016) | Asserts the trigger on the rising edge of the digital signal. |
---|---|
NIDCPOWER_VAL_FALLING (1017) | Asserts the trigger on the falling edge of the digital signal. |
Default Value: NIDCPOWER_VAL_RISING |
Numeric Value | Data type |
Access | Applies to | Coercion | High-Level Functions |
---|---|---|---|---|---|
1150036 | ViString | R/W | Channel | None | niDCPower_ConfigureDigitalEdgeMeasureTriggerWithChannels |
Specifies the input terminal for the Measure trigger. This attribute is used only when the NIDCPOWER_ATTRIBUTE_MEASURE_TRIGGER_TYPE attribute is set to NIDCPOWER_VAL_DIGITAL_EDGE.
!Note | Note This attribute is not supported by all devices. Refer to Supported Attributes by Device for information about supported devices. |
---|---|
You can specify any valid input terminal for this attribute, and the driver will create a route between it and the Measure trigger terminal at Commit. Valid terminals are listed in Measurement & Automation Explorer under the Device Routes tab. For the PXIe-4147, PXIe-4162, and PXIe-4163, refer to the Signal Routing topic for the instrument to determine which routes are available (this information is not available on a Device Routes tab in MAX). |
Specify the output terminal using the form /Dev1/PXI_Trig0, where Dev1 is the instrument and PXI_Trig0 is the terminal. The input terminal can also be a terminal from another instrument. For example, you can set the input terminal on Dev1 to be /Dev2/Engine0/SourceCompleteEvent, where Engine0 is channel 0.
!Note | Note You must specify the input terminal for a PXI-4132 using the form /Dev1/PXI_Trig0, where Dev1 is a PXI-4132 and PXI_Trig0 is the terminal. |
---|
!Note | Note To specify a channel name when accessing this attribute, you must first initialize the session using the niDCPower_InitializeWithIndependentChannels function. |
---|
Numeric Value | Data type |
Access | Applies to | Coercion | High-Level Functions |
---|---|---|---|---|---|
1150026 | ViInt32 | R/W | Channel | None | niDCPower_ConfigureDigitalEdgeSequenceAdvanceTriggerWithChannels niDCPower_ConfigureSoftwareEdgeSequenceAdvanceTriggerWithChannels niDCPower_DisableSequenceAdvanceTriggerWithChannels |
Specifies the behavior of the Sequence Advance trigger.
!Note | Note This attribute is not supported by all devices. Refer to Supported Attributes by Device for information about supported devices. |
---|
!Note | Note To specify a channel name when accessing this attribute, you must first initialize the session using the niDCPower_InitializeWithIndependentChannels function. |
---|---|
Defined Values: |
NIDCPOWER_VAL_NONE (1012) | No trigger is configured. |
---|---|
NIDCPOWER_VAL_DIGITAL_EDGE (1014) | The data operation starts when a digital edge is detected. |
NIDCPOWER_VAL_SOFTWARE_EDGE (1015) | The data operation starts when a software trigger occurs. |
Default Value: NIDCPOWER_VAL_NONE |
Numeric Value | Data type |
Access | Applies to | Coercion | High-Level Functions |
---|---|---|---|---|---|
1150029 | ViString | R/W | Channel | None | niDCPower_ExportSignalWithChannels |
Specifies the output terminal for exporting the Sequence Advance trigger.
Refer to the Device Routes tab in Measurement & Automation Explorer for a list of the terminals available on your device. For the PXIe-4147, PXIe-4162, and PXIe-4163, refer to the Signal Routing topic for the instrument to determine which routes are available (this information is not available on a Device Routes tab in MAX).
Specify the output terminal using the form /Dev1/PXI_Trig0, where Dev1 is the instrument and PXI_Trig0 is the terminal.
!Note | Note This attribute is not supported by all devices. Refer to Supported Attributes by Device for information about supported devices. |
---|
!Note | Note To specify a channel name when accessing this attribute, you must first initialize the session using the niDCPower_InitializeWithIndependentChannels function. |
---|
Numeric Value | Data type |
Access | Applies to | Coercion | High-Level Functions |
---|---|---|---|---|---|
1150027 | ViInt32 | R/W | Channel | None | niDCPower_ConfigureDigitalEdgeSequenceAdvanceTriggerWithChannels |
Specifies whether to configure the Sequence Advance trigger to assert on the rising or falling edge.
!Note | Note This attribute is not supported by all devices. Refer to Supported Attributes by Device for information about supported devices. |
---|
!Note | Note To specify a channel name when accessing this attribute, you must first initialize the session using the niDCPower_InitializeWithIndependentChannels function. |
---|---|
Defined Values: |
NIDCPOWER_VAL_RISING (1016) | Asserts the trigger on the rising edge of the digital signal. |
---|---|
NIDCPOWER_VAL_FALLING (1017) | Asserts the trigger on the falling edge of the digital signal. |
Default Value: NIDCPOWER_VAL_RISING |
Numeric Value | Data type |
Access | Applies to | Coercion | High-Level Functions |
---|---|---|---|---|---|
1150028 | ViString | R/W | Channel | None | niDCPower_ConfigureDigitalEdgeSequenceAdvanceTriggerWithChannels |
Specifies the input terminal for the Sequence Advance trigger. Use this attribute only when the NIDCPOWER_ATTRIBUTE_SEQUENCE_ADVANCE_TRIGGER_TYPE attribute is set to NIDCPOWER_VAL_DIGITAL_EDGE.
!Note | Note This attribute is not supported by all devices. Refer to Supported Attributes by Device for information about supported devices. |
---|---|
You can specify any valid input terminal for this attribute, and the driver will create a route between it and the Sequence Advance trigger terminal at Commit. Valid terminals are listed in Measurement & Automation Explorer under the Device Routes tab. For the PXIe-4147, PXIe-4162, and PXIe-4163, refer to the Signal Routing topic for the instrument to determine which routes are available (this information is not available on a Device Routes tab in MAX). |
Specify the output terminal using the form /Dev1/PXI_Trig0, where Dev1 is the instrument and PXI_Trig0 is the terminal. The input terminal can also be a terminal from another instrument. For example, you can set the input terminal on Dev1 to be /Dev2/Engine0/SourceCompleteEvent, where Engine0 is channel 0.
!Note | Note You must specify the input terminal for a PXI-4132 using the form /Dev1/PXI_Trig0, where Dev1 is a PXI-4132 and PXI_Trig0 is the terminal. |
---|
!Note | Note To specify a channel name when accessing this attribute, you must first initialize the session using the niDCPower_InitializeWithIndependentChannels function. |
---|
Numeric Value | Data type |
Access | Applies to | Coercion | High-Level Functions |
---|---|---|---|---|---|
1150095 | ViInt32 | R/W | Channel | None | niDCPower_ConfigureDigitalEdgePulseTriggerWithChannels niDCPower_ConfigureSoftwareEdgePulseTriggerWithChannels niDCPower_DisablePulseTriggerWithChannels |
Specifies the behavior of the Pulse trigger.
!Note | Note This attribute is not supported by all devices. Refer to Supported Attributes by Device for information about supported devices. |
---|
!Note | Note To specify a channel name when accessing this attribute, you must first initialize the session using the niDCPower_InitializeWithIndependentChannels function. |
---|---|
Defined Values: |
NIDCPOWER_VAL_DIGITAL_EDGE (1014) | The data operation starts when a digital edge is detected. |
---|---|
NIDCPOWER_VAL_SOFTWARE_EDGE (1015) | The data operation starts when a software trigger occurs. |
NIDCPOWER_VAL_NONE (1012) | No trigger is configured. |
Default Value: NIDCPOWER_VAL_NONE |
Numeric Value | Data type |
Access | Applies to | Coercion | High-Level Functions |
---|---|---|---|---|---|
1150098 | ViString | R/W | Channel | None | niDCPower_ExportSignalWithChannels |
Specifies the output terminal for exporting the Pulse trigger.
Refer to the Device Routes tab in Measurement & Automation Explorer for a list of the terminals available on your device.
Specify the output terminal using the form /Dev1/PXI_Trig0, where Dev1 is the instrument and PXI_Trig0 is the terminal.
!Note | Note This attribute is not supported by all devices. Refer to Supported Attributes by Device for information about supported devices. |
---|
!Note | Note To specify a channel name when accessing this attribute, you must first initialize the session using the niDCPower_InitializeWithIndependentChannels function. |
---|
Numeric Value | Data type |
Access | Applies to | Coercion | High-Level Functions |
---|---|---|---|---|---|
1150096 | ViInt32 | R/W | Channel | None | niDCPower_ConfigureDigitalEdgePulseTriggerWithChannels |
Specifies whether to configure the Pulse trigger to assert on the rising or falling edge.
!Note | Note This attribute is not supported by all devices. Refer to Supported Attributes by Device for information about supported devices. |
---|
!Note | Note To specify a channel name when accessing this attribute, you must first initialize the session using the niDCPower_InitializeWithIndependentChannels function. |
---|---|
Defined Values: |
NIDCPOWER_VAL_RISING (1016) | Asserts the trigger on the rising edge of the digital signal. |
---|---|
NIDCPOWER_VAL_FALLING (1017) | Asserts the trigger on the falling edge of the digital signal. |
Default Value: NIDCPOWER_VAL_RISING |
Numeric Value | Data type |
Access | Applies to | Coercion | High-Level Functions |
---|---|---|---|---|---|
1150097 | ViString | R/W | Channel | None | niDCPower_ConfigureDigitalEdgePulseTriggerWithChannels |
Specifies the input terminal for the Pulse trigger. This attribute is used only when the NIDCPOWER_ATTRIBUTE_PULSE_TRIGGER_TYPE attribute is set to digital edge.
!Note | Note This attribute is not supported by all devices. Refer to Supported Attributes by Device for information about supported devices. |
---|---|
Specify the output terminal using the form /Dev1/PXI_Trig0, where Dev1 is the instrument and PXI_Trig0 is the terminal. The input terminal can also be a terminal from another instrument. For example, you can set the input terminal on Dev1 to be /Dev2/Engine0/SourceCompleteEvent, where Engine0 is channel 0. |
!Note | Note You must specify the input terminal for a PXI-4132 using the form /Dev1/PXI_Trig0, where Dev1 is a PXI-4132 and PXI_Trig0 is the terminal. |
---|
!Note | Note To specify a channel name when accessing this attribute, you must first initialize the session using the niDCPower_InitializeWithIndependentChannels function. |
---|
Numeric Value | Data type |
Access | Applies to | Coercion | High-Level Functions |
---|---|---|---|---|---|
1150275 | ViInt32 | R/W | Channel | None | niDCPower_ConfigureDigitalEdgeShutdownTriggerWithChannels niDCPower_ConfigureSoftwareEdgeShutdownTriggerWithChannels niDCPower_DisableShutdownTriggerWithChannels |
Specifies the behavior of the Shutdown trigger.
!Note | Note This attribute is not supported by all devices. Refer to Supported Attributes by Device for information about supported devices. |
---|
!Note | Note To specify a channel name when accessing this attribute, you must first initialize the session using the niDCPower_InitializeWithIndependentChannels function. |
---|---|
Defined Values: |
NIDCPOWER_VAL_DIGITAL_EDGE (1014) | The data operation starts when a digital edge is detected. |
---|---|
NIDCPOWER_VAL_SOFTWARE_EDGE (1015) | The data operation starts when a software trigger occurs. |
NIDCPOWER_VAL_NONE (1012) | No trigger is configured. |
Default Value: NIDCPOWER_VAL_NONE |
Numeric Value | Data type |
Access | Applies to | Coercion | High-Level Functions |
---|---|---|---|---|---|
1150276 | ViInt32 | R/W | Channel | None | niDCPower_ConfigureDigitalEdgeShutdownTriggerWithChannels |
Specifies whether to configure the Pulse trigger to assert on the rising or falling edge.
!Note | Note This attribute is not supported by all devices. Refer to Supported Attributes by Device for information about supported devices. |
---|
!Note | Note To specify a channel name when accessing this attribute, you must first initialize the session using the niDCPower_InitializeWithIndependentChannels function. |
---|---|
Defined Values: |
NIDCPOWER_VAL_RISING (1016) | Asserts the trigger on the rising edge of the digital signal. |
---|---|
NIDCPOWER_VAL_FALLING (1017) | Asserts the trigger on the falling edge of the digital signal. |
Default Value: NIDCPOWER_VAL_RISING |
Numeric Value | Data type |
Access | Applies to | Coercion | High-Level Functions |
---|---|---|---|---|---|
1150277 | ViString | R/W | Channel | None | niDCPower_ConfigureDigitalEdgeShutdownTriggerWithChannels |
Specifies the input terminal for the Pulse trigger. This attribute is used only when the NIDCPOWER_ATTRIBUTE_SHUTDOWN_TRIGGER_TYPE attribute is set to digital edge.
!Note | Note This attribute is not supported by all devices. Refer to Supported Attributes by Device for information about supported devices. |
---|---|
Specify the output terminal using the form /Dev1/PXI_Trig0, where Dev1 is the instrument and PXI_Trig0 is the terminal. The input terminal can also be a terminal from another instrument. For example, you can set the input terminal on Dev1 to be /Dev2/Engine0/SourceCompleteEvent, where Engine0 is channel 0. |
!Note | Note You must specify the input terminal for a PXI-4138/4139 using the form /Dev1/PXI_Trig0, where Dev1 is a PXI-4138/4139 and PXI_Trig0 is the terminal. |
---|
!Note | Note To specify a channel name when accessing this attribute, you must first initialize the session using the niDCPower_InitializeWithIndependentChannels function. |
---|
Creating and Setting Up a gRPC Server
Session Utilities API Reference
gRPC API Differences From C API
Sharing Driver Sessions Between Clients
C API Docs
NI-DAQmx
- gRPC API Differences From C API
- Task Configuration And Control
- Channel Configuration And Creation
- Timing
- Triggering
- Read Functions
- Write Functions
- Export Hardware Signals
- Scale Configuration
- Internal Buffer Configuration
- Advanced Functions
- System Configuration
- Error Handling
- Buffer Attributes
- Calibration Info Attributes
- Channel Attributes
- Device Attributes
- Export Signal Attributes
- Persisted Channel Attributes
- Persisted Scale Attributes
- Persisted Task Attributes
- Physical Channel Attributes
- Read Attributes
- Scale Attributes
- System Attributes
- Task Attributes
- Timing Attributes
- Trigger Attributes
- Watchdog Attributes
- Write Attributes
NI-DCPOWER
- Setup Functions
- Configure Functions
- Measurement Functions
- Control Functions
- Trigger And Event
- Attribute Functions
- Query Functions
- Calibration Functions
- Utility Functions
- Supported Device
- Source Attributes
- Transient Attributes
- Voltage Attributes
- Current Attributes
- Pulse Voltage Attributes
- Pulse Current Attributes
- Cutoff Attributes
- Measurement Attributes
- Trigger Attributes Functions
- Event Attributes
- Advanced Attributes
- Inherent Ivi Attributes
- Supported Device Attributes
NI-DIGITAL PATTERN DRIVER
- Init And Close Functions
- Session Locking Functions
- Utility Functions
- Error Handling Functions
- Calibration Functions
- Attributes Functions
- Pin Map Functions
- Low Level Functions
- Low Level Action Functions
- Pin Control Functions
- Static IO Functions
- Clock Generator Functions
- Levels And Timing Functions
- TDR Functions
- PPMU Configuration Functions
- DC Voltage Functions
- DC Current Functions
- PPMU Action Functions
- Pattern Configuration Functions
- Pattern Action Functions
- History Ram Functions
- Source Memory Functions
- Capture Memory Functions
- Triggers And Events Functions
- Conditional Jump Trigger Functions
- Sequencer Flag Functions
- Sequencer Register Functions
- Match Fail Combination Functions
- Pattern Results Functions
- Sort Results Functions
- Frequency Measurement Functions
- IVI Inherent Attributes
- Specific Driver Information Attributes, Read Only
- Driver Setup Information Attributes
- Device Attributes
- Pin Control Attributes
- Level Configuration Attributes
- Trigger Configuration Attributes
- PPMU Attributes
- Patterns Attributes
- Pattern Opcode Event Attributes
- Timing Offset Attributes
- Keep Alive Attributes
- Frequency Measurement Attributes
- Clock Generator Attributes
- History RAM
- Synchronization Attributes
- TDR Endpoint Termination Attributes
NI-FGEN
- Setup Functions
- Configuration Functions
- Standard Output Functions
- Arbitrary Waveform Output Functions
- Arbitrary Sequence Output Functions
- Incremental Waveform Write Functions
- Configure Clock Functions
- Trigger And Syncronizations Functions
- 5404 Routing Functions
- Script Output Functions
- Configure Onboard Signal Processing Functions
- Configure Peer To Peer Functions
- Attribute Functions
- Waveform Control Functions
- Error Functions
- Output Attributes
- Arbitrary Waveform Attributes
- Data Transfer Attributes
- Onboard Signal Processing Attributes
- Peer To Peer Attributes
- Standard Function Attributes
- Clock Attributes
- Event Attributes
- Triggering Attributes
- Instrument Specific Attributes
- Inherent IVI Attributes
- 5401 5411 5431
NI-RFmx Bluetooth
- gRPC API Differences From C API
- General Functions
- Configuration Functions
- Set And Get Attribute Functions
- Fetch Results Functions
- Utility Functions
- Build String Functions
- Advanced Functions
- General Attributes
- Trigger Attributes
- Packet Attributes
- Auto Detect Signal Attributes
- Modacc Attributes
- ACP Attributes
- Twenty dB Attributes
- Frequency Range Attributes
- TXP Attributes
- Advanced Attributes
NI-RFmx NR
- gRPC API Differences From C API
- General Functions
- Configuration Functions
- Set And Get Attributes Functions
- Fetch Results Functions
- Utility Functions
- Build String Functions
- Advanced Functions
- General Attributes
- Trigger Attributes
- Signal Detection Attributes
- Component Carrier Attributes
- List Attributes
- Modacc Attributes
- ACP Attributes
- CHP Attributes
- OBW Attributes
- SEM Attributes
- TXP Attributes
- Pvt Attributes
- Advanced Attributes
NI-RFmx LTE
- gRPC API Differences From C API
- General Functions
- Configuration Functions
- Ch Configuration Functions
- NB IoT Configuration Functions
- ModAcc Configuration Functions
- ACP Configuration Functions
- CHP Configuration Functions
- OBW Configuration Functions
- SEM Configuration Functions
- PVT Configuration Functions
- SlotPhase Configuration Functions
- SlotPower Configuration Functions
- Set And Get Attribute Functions
- ModAcc Fetch Functions
- ACP Fetch Functions
- CHP Fetch Functions
- OBW Fetch Functions
- SEM Fetch Functions
- PVT Fetch Functions
- SlotPhase Fetch Functions
- SlotPower Fetch Functions
- Utility Functions
- Build String Functions
- Advanced Functions
- General Attributes
- Trigger Attributes
- Component Carrier Attributes
- ModAcc Attributes
- ACP Attributes
- CHP Attributes
- OBW Attributes
- SEM Attributes
- PVT Attributes
- SlotPhase Attributes
- SlotPower Attributes
- Advanced Attributes
NI-RFmx SpecAn
- gRPC API Differences From C API
- General Functions
- Configuration Functions
- Set And Get Attribute Functions
- Read Functions
- Fetch Functions
- Utility Functions
- Marker Functions
- Build String Functions
- Advanced Functions
- General Attributes
- Trigger Attributes
- ACP Attributes
- Cdf Attributes
- CHP Attributes
- Fcnt Attributes
- Harm Attributes
- OBW Attributes
- SEM Attributes
- Spectrum Attributes
- Spur Attributes
- TXP Attributes
- AMPM Attributes
- Dpd Attributes
- IQ Attributes
- IM Attributes
- NF Attributes
- Phasenoise Attributes
- PAVT Attributes
- Advanced Attributes
NI-RFmx WLAN
- gRPC API Differences From C API
- General Functions
- Configuration Functions
- Set And Get Attribute Functions
- Fetch DSSS ModAcc Functions
- Fetch OFDM ModAcc Functions
- Fetch SEM Functions
- Fetch TXP Functions
- Fetch PowerRamp Functions
- Utility Functions
- Build String Functions
- Advanced Functions
- General Attributes
- Trigger Attributes
- OFDM Attributes
- Auto Detect Signal Attributes
- DSSS ModAcc Attributes
- OFDM ModAcc Attributes
- SEM Attributes
- TXP Attributes
- PowerRamp Attributes
- Advanced Attributes
NI-RFSA
- General Functions
- Configuration Functions
- Acquisition Functions
- Utility Functions
- Calibration Functions
- General Attributes
- Vertical Attributes
- Signal Path Attributes
- Acquisition Attributes
- Acquisition Attributes
- Triggers Attributes
- Events Attributes
- Device Characteristics Attributes
- Peer To Peer Streaming Attributes
- Configuration List Attributes
- Inherent IVI Properties Attributes
- De-embedding Attributes
- Self Calibration Attributes
- Factory Calibration Attributes
- External Alignment Attributes
- Device Specific Attributes
NI-RFSG
- General Functions
- Generation Configuration
- Utility Functions
- Calibration Functions
- Arb Attributes
- Clock Attributes
- Configuration List Attributes
- De-embedding Attributes
- Device Characteristics Attributes
- Device Specific Attributes
- Events Attributes
- External Calibration Attributes
- Inherent IVI Attributes Attributes
- IQ Impairment Attributes
- Load Configurations Attributes
- Modulation Attributes
- Obsolete Attributes
- Peer To Peer Attributes
- RF Attributes
- Self Calibration Attributes
- Triggers Attributes
NI-SCOPE
- Setup Functions
- Configure Functions
- Attribute Functions
- Acquisition Functions
- Measurement Functions
- Calibrate Functions
- Utility Funcitons
- Error Handling Functions
- IVI Compliance Or Obsolete Functions
- Vertical Attributes
- Horizontal Attributes
- Trigger Attributes
- Clocking Attributes
- Synchronization Attributes
- Acquisition Attributes
- Waveform Measurements Attributes
- Onboard Signal Processing Attributes
- Peer To Peer Streaming Attributes
- Device Attributes
- IVI Or Obsolete Attributes
- Instrument Capabilities Attributes
- If Digitizer Attributes
NI-XNET
- gRPC API differences from C APIs
- General Functions
- Cluster Properties
- Database Properties
- Device Properties
- ECU Properties
- Frame Properties
- Interface Properties
- LIN Schedule Entry Properties
- LIN Schedule Properties
- PDU Properties
- Session Ethernet Properties
- Session Frame Properties
- Session Interface Properties
- Session Properties
- Session SAE J1939 Properties
- Signal Properties
- Subframe Properties
- System Properties
- IP-Stack Functions
- Socket Options
- Socket Functions