-
Notifications
You must be signed in to change notification settings - Fork 52
NI DCPOWER Trigger And Event Functions
- niDCPower_ConfigureDigitalEdgeStartTriggerWithChannels
- niDCPower_ConfigureDigitalEdgeStartTrigger
- niDCPower_ConfigureSoftwareEdgeStartTriggerWithChannels
- niDCPower_ConfigureSoftwareEdgeStartTrigger
- niDCPower_DisableStartTriggerWithChannels
- niDCPower_DisableStartTrigger
- niDCPower_ConfigureDigitalEdgeSourceTriggerWithChannels
- niDCPower_ConfigureDigitalEdgeSourceTrigger
- niDCPower_ConfigureSoftwareEdgeSourceTriggerWithChannels
- niDCPower_ConfigureSoftwareEdgeSourceTrigger
- niDCPower_DisableSourceTriggerWithChannels
- niDCPower_DisableSourceTrigger
- niDCPower_ConfigureDigitalEdgeMeasureTriggerWithChannels
- niDCPower_ConfigureDigitalEdgeMeasureTrigger
- niDCPower_ConfigureSoftwareEdgeMeasureTriggerWithChannels
- niDCPower_ConfigureSoftwareEdgeMeasureTrigger
- niDCPower_ConfigureDigitalEdgeSequenceAdvanceTriggerWithChannels
- niDCPower_ConfigureDigitalEdgeSequenceAdvanceTrigger
- niDCPower_ConfigureSoftwareEdgeSequenceAdvanceTriggerWithChannels
- niDCPower_ConfigureSoftwareEdgeSequenceAdvanceTrigger
- niDCPower_DisableSequenceAdvanceTriggerWithChannels
- niDCPower_DisableSequenceAdvanceTrigger
- niDCPower_ConfigureDigitalEdgePulseTriggerWithChannels
- niDCPower_ConfigureDigitalEdgePulseTrigger
- niDCPower_ConfigureSoftwareEdgePulseTriggerWithChannels
- niDCPower_ConfigureSoftwareEdgePulseTrigger
- niDCPower_DisablePulseTriggerWithChannels
- niDCPower_DisablePulseTrigger
- niDCPower_ConfigureDigitalEdgeShutdownTriggerWithChannels
- niDCPower_ConfigureSoftwareEdgeShutdownTriggerWithChannels
- niDCPower_DisableShutdownTriggerWithChannels
- niDCPower_ExportSignalWithChannels
- niDCPower_ExportSignal
- niDCPower_SendSoftwareEdgeTriggerWithChannels
- niDCPower_SendSoftwareEdgeTrigger
- niDCPower_WaitForEventWithChannels
- niDCPower_WaitForEvent
ViStatus niDCPower_ConfigureDigitalEdgeStartTriggerWithChannels(ViSession vi, ViConstString inputTerminal, ViInt32 edge);
Configures the Start trigger for digital edge triggering.
Note This function is not supported on all devices. Refer to Supported Functions by Device for more information about supported devices.
Input | ||
---|---|---|
Name | Type | Description |
vi | ViSession | Identifies a particular instrument session. vi is obtained from the niDCPower_InitializeWithIndependentChannels function. |
channelName | ViConstString |
Specifies the channel(s) to use. Specify the channel(s) using the form PXI1Slot3/0,PXI1Slot3/2-3,PXI1Slot4/2-3 or PXI1Slot3/0,PXI1Slot3/2:3,PXI1Slot4/2:3, where PXI1Slot3 and PXI1Slot4 are instrument resource names and 0, 2, and 3 are channels. If you pass "" for this control, all channels in the session are used. |
inputTerminal | ViConstString |
Specifies the input terminal for the digital edge Start trigger. You can specify any valid input terminal for this function. Valid terminals are listed in MAX under the Device Routes tab. For the PXIe-4147 and PXIe-4162/4163, refer to the Signal Routing topic for the device to determine which routes are available. This information is not available on a Device Routes tab in MAX. Specify the input 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 or channel. For example, you can set the input terminal on Dev1 to be /Dev2/Engine0/SourceCompleteEvent, where Engine0 is channel 0. |
edge | ViInt32 | Specifies whether to configure the Start trigger to assert on the rising or falling edge. 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. |
Name | Type | Description |
---|---|---|
Status | ViStatus | Reports the status of this operation. To obtain a text description of the status code, call the niDCPower_error_message function. To obtain additional information concerning the error condition, call the niDCPower_GetError function. |
ViStatus niDCPower_ConfigureDigitalEdgeStartTrigger(ViSession vi, ViConstString inputTerminal, ViInt32 edge);
This function is deprecated. Use niDCPower_ConfigureDigitalEdgeStartTriggerWithChannels instead.
Configures the Start trigger for digital edge triggering.
Note This function is not supported on all devices. Refer to Supported Functions by Device for more information about supported devices.
Input | ||
---|---|---|
Name | Type | Description |
vi | ViSession | Identifies a particular instrument session. vi is obtained from the niDCPower_InitializeWithIndependentChannels function. |
inputTerminal | ViConstString |
Specifies the input terminal for the digital edge Start trigger. You can specify any valid input terminal for this function. Valid terminals are listed in MAX under the Device Routes tab. For the PXIe-4147 and PXIe-4162/4163, refer to the Signal Routing topic for the device to determine which routes are available. This information is not available on a Device Routes tab in MAX. Input terminals can be specified in one of two ways. If the device is named Dev1 and your terminal is PXI_Trig0, you can specify the terminal with the fully qualified terminal name, /Dev1/PXI_Trig0, or with the shortened terminal name, PXI_Trig0. The input terminal can also be a terminal from another device. For example, you can set the input terminal on Dev1 to be /Dev2/SourceCompleteEvent. |
edge | ViInt32 | Specifies whether to configure the Start trigger to assert on the rising or falling edge. 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. |
Name | Type | Description |
---|---|---|
Status | ViStatus | Reports the status of this operation. To obtain a text description of the status code, call the niDCPower_error_message function. To obtain additional information concerning the error condition, call the niDCPower_GetError function. |
ViStatus niDCPower_ConfigureSoftwareEdgeStartTriggerWithChannels(ViSession vi);
Configures the Start trigger for software edge triggering. Use the niDCPower_SendSoftwareEdgeTriggerWithChannels function to assert the trigger condition.
Note This function is not supported on all devices. Refer to Supported Functions by Device for more information about supported devices.
Input | ||
---|---|---|
Name | Type | Description |
vi | ViSession | Identifies a particular instrument session. vi is obtained from the niDCPower_InitializeWithIndependentChannels function. |
channelName | ViConstString |
Specifies the channel(s) to use. Specify the channel(s) using the form PXI1Slot3/0,PXI1Slot3/2-3,PXI1Slot4/2-3 or PXI1Slot3/0,PXI1Slot3/2:3,PXI1Slot4/2:3, where PXI1Slot3 and PXI1Slot4 are instrument resource names and 0, 2, and 3 are channels. If you pass "" for this control, all channels in the session are used. |
Name | Type | Description |
---|---|---|
Status | ViStatus | Reports the status of this operation. To obtain a text description of the status code, call the niDCPower_error_message function. To obtain additional information concerning the error condition, call the niDCPower_GetError function. |
ViStatus niDCPower_ConfigureSoftwareEdgeStartTrigger(ViSession vi);
This function is deprecated. Use niDCPower_ConfigureSoftwareEdgeStartTriggerWithChannels instead.
Configures the Start trigger for software triggering. Use the niDCPower_SendSoftwareEdgeTrigger function to assert the trigger condition.
Note This function is not supported on all devices. Refer to Supported Functions by Device for more information about supported devices.
Input | ||
---|---|---|
Name | Type | Description |
vi | ViSession | Identifies a particular instrument session. vi is obtained from the niDCPower_InitializeWithIndependentChannels function. |
Name | Type | Description |
---|---|---|
Status | ViStatus | Reports the status of this operation. To obtain a text description of the status code, call the niDCPower_error_message function. To obtain additional information concerning the error condition, call the niDCPower_GetError function. |
ViStatus niDCPower_DisableStartTriggerWithChannels(ViSession vi);
Disables the Start trigger. The specified channel(s) do not wait for a Start trigger when starting generation or acquisition.
This function is necessary only if you configured a Start trigger in the past and now want to disable it.
Note This function is not supported on all devices. Refer to Supported Functions by Device for more information about supported devices.
Input | ||
---|---|---|
Name | Type | Description |
vi | ViSession | Identifies a particular instrument session. vi is obtained from the niDCPower_InitializeWithIndependentChannels function. |
channelName | ViConstString |
Specifies the channel(s) to use. Specify the channel(s) using the form PXI1Slot3/0,PXI1Slot3/2-3,PXI1Slot4/2-3 or PXI1Slot3/0,PXI1Slot3/2:3,PXI1Slot4/2:3, where PXI1Slot3 and PXI1Slot4 are instrument resource names and 0, 2, and 3 are channels. If you pass "" for this control, all channels in the session are used. |
Name | Type | Description |
---|---|---|
Status | ViStatus | Reports the status of this operation. To obtain a text description of the status code, call the niDCPower_error_message function. To obtain additional information concerning the error condition, call the niDCPower_GetError function. |
ViStatus niDCPower_DisableStartTrigger(ViSession vi);
This function is deprecated. Use niDCPower_DisableStartTriggerWithChannels instead.
Disables the Start trigger. The device does not wait for a Start trigger when starting generation or acquisition.
Note This function is not supported on all devices. Refer to Supported Functions by Device for more information about supported devices.
Input | ||
---|---|---|
Name | Type | Description |
vi | ViSession | Identifies a particular instrument session. vi is obtained from the niDCPower_InitializeWithIndependentChannels function. |
Name | Type | Description |
---|---|---|
Status | ViStatus | Reports the status of this operation. To obtain a text description of the status code, call the niDCPower_error_message function. To obtain additional information concerning the error condition, call the niDCPower_GetError function. |
ViStatus niDCPower_ConfigureDigitalEdgeSourceTriggerWithChannels(ViSession vi, ViConstString inputTerminal, ViInt32 edge);
Configures the Source trigger for digital edge triggering.
Note This function is not supported on all devices. Refer to Supported Functions by Device for more information about supported devices.
Input | ||||
---|---|---|---|---|
Name | Type | Description | ||
vi | ViSession | Identifies a particular instrument session. vi is obtained from the niDCPower_InitializeWithIndependentChannels function. | ||
channelName | ViConstString |
Specifies the channel(s) to use. Specify the channel(s) using the form PXI1Slot3/0,PXI1Slot3/2-3,PXI1Slot4/2-3 or PXI1Slot3/0,PXI1Slot3/2:3,PXI1Slot4/2:3, where PXI1Slot3 and PXI1Slot4 are instrument resource names and 0, 2, and 3 are channels. If you pass "" for this control, all channels in the session are used. |
||
inputTerminal | ViConstString |
Specifies the input terminal for the digital edge Source trigger. You can specify any valid input terminal for this function. Valid terminals are listed in MAX under the Device Routes tab. For the PXIe-4147 and PXIe-4162/4163, refer to the Signal Routing topic for the device to determine which routes are available. This information is not available on a Device Routes tab in MAX. Specify the input 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 or channel. For example, you can set the input terminal on Dev1 to be /Dev2/Engine0/SourceCompleteEvent, where edge |
ViInt32 | Specifies whether to configure the Source trigger to assert on the rising or falling edge. 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. |
Name | Type | Description |
---|---|---|
Status | ViStatus | Reports the status of this operation. To obtain a text description of the status code, call the niDCPower_error_message function. To obtain additional information concerning the error condition, call the niDCPower_GetError function. |
ViStatus niDCPower_ConfigureDigitalEdgeSourceTrigger(ViSession vi, ViConstString inputTerminal, ViInt32 edge);
This function is deprecated. Use niDCPower_ConfigureDigitalEdgeSourceTriggerWithChannels instead.
Configures the Source trigger for digital edge triggering.
Note This function is not supported on all devices. Refer to Supported Functions by Device for more information about supported devices.
Input | ||
---|---|---|
Name | Type | Description |
vi | ViSession | Identifies a particular instrument session. vi is obtained from the niDCPower_InitializeWithIndependentChannels function. |
inputTerminal | ViConstString |
Specifies the input terminal for the digital edge Source trigger. You can specify any valid input terminal for this function. Valid terminals are listed in MAX under the Device Routes tab. For the PXIe-4147 and PXIe-4162/4163, refer to the Signal Routing topic for the device to determine which routes are available. This information is not available on a Device Routes tab in MAX. Input terminals can be specified in one of two ways. If the device is named Dev1 and your terminal is PXI_Trig0, you can specify the terminal with the fully qualified terminal name, /Dev1/PXI_Trig0, or with the shortened terminal name, PXI_Trig0. The input terminal can also be a terminal from another device. For example, you can set the input terminal on Dev1 to be /Dev2/SourceCompleteEvent. |
edge | ViInt32 | Specifies whether to configure the Source trigger to assert on the rising or falling edge. 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. |
Name | Type | Description |
---|---|---|
Status | ViStatus | Reports the status of this operation. To obtain a text description of the status code, call the niDCPower_error_message function. To obtain additional information concerning the error condition, call the niDCPower_GetError function. |
ViStatus niDCPower_ConfigureSoftwareEdgeSourceTriggerWithChannels(ViSession vi);
Configures the Source trigger for software edge triggering. Use the niDCPower_SendSoftwareEdgeTriggerWithChannels function to assert the trigger condition.
Note This function is not supported on all devices. Refer to Supported Functions by Device for more information about supported devices.
Input | ||
---|---|---|
Name | Type | Description |
vi | ViSession | Identifies a particular instrument session. vi is obtained from the niDCPower_InitializeWithIndependentChannels function. |
channelName | ViConstString |
Specifies the channel(s) to use. Specify the channel(s) using the form PXI1Slot3/0,PXI1Slot3/2-3,PXI1Slot4/2-3 or PXI1Slot3/0,PXI1Slot3/2:3,PXI1Slot4/2:3, where PXI1Slot3 and PXI1Slot4 are instrument resource names and 0, 2, and 3 are channels. If you pass "" for this control, all channels in the session are used. |
Name | Type | Description |
---|---|---|
Status | ViStatus | Reports the status of this operation. To obtain a text description of the status code, call the niDCPower_error_message function. To obtain additional information concerning the error condition, call the niDCPower_GetError function. |
ViStatus niDCPower_ConfigureSoftwareEdgeSourceTrigger(ViSession vi);
This function is deprecated. Use niDCPower_ConfigureSoftwareEdgeSourceTriggerWithChannels instead.
Configures the Source trigger for software triggering. Use the niDCPower_SendSoftwareEdgeTrigger function to assert the trigger condition.
Note This function is not supported on all devices. Refer to Supported Functions by Device for more information about supported devices.
Input | ||
---|---|---|
Name | Type | Description |
vi | ViSession | Identifies a particular instrument session. vi is obtained from the niDCPower_InitializeWithIndependentChannels function. |
Name | Type | Description |
---|---|---|
Status | ViStatus | Reports the status of this operation. To obtain a text description of the status code, call the niDCPower_error_message function. To obtain additional information concerning the error condition, call the niDCPower_GetError function. |
ViStatus niDCPower_DisableSourceTriggerWithChannels(ViSession vi);
Disables the Source trigger. The specified channel(s) do not wait for a source trigger before performing a source operation.
This function is necessary only if you configured a Source trigger in the past and now want to disable it.
Note This function is not supported on all devices. Refer to Supported Functions by Device for more information about supported devices.
Input | ||
---|---|---|
Name | Type | Description |
vi | ViSession | Identifies a particular instrument session. vi is obtained from the niDCPower_InitializeWithIndependentChannels function. |
channelName | ViConstString |
Specifies the channel(s) to use. Specify the channel(s) using the form PXI1Slot3/0,PXI1Slot3/2-3,PXI1Slot4/2-3 or PXI1Slot3/0,PXI1Slot3/2:3,PXI1Slot4/2:3, where PXI1Slot3 and PXI1Slot4 are instrument resource names and 0, 2, and 3 are channels. If you pass "" for this control, all channels in the session are used. |
Name | Type | Description |
---|---|---|
Status | ViStatus | Reports the status of this operation. To obtain a text description of the status code, call the niDCPower_error_message function. To obtain additional information concerning the error condition, call the niDCPower_GetError function. |
ViStatus niDCPower_DisableSourceTrigger(ViSession vi);
This function is deprecated. Use niDCPower_DisableSourceTriggerWithChannels instead.
Disables the Source trigger. The device does not wait for a source trigger before performing a source operation. Refer to the Single Point Source Mode topics for more information about the Source trigger.
Note This function is not supported on all devices. Refer to Supported Functions by Device for more information about supported devices.
Input | ||
---|---|---|
Name | Type | Description |
vi | ViSession | Identifies a particular instrument session. vi is obtained from the niDCPower_InitializeWithIndependentChannels function. |
Name | Type | Description |
---|---|---|
Status | ViStatus | Reports the status of this operation. To obtain a text description of the status code, call the niDCPower_error_message function. |
ViStatus niDCPower_ConfigureDigitalEdgeMeasureTriggerWithChannels(ViSession vi, ViConstString inputTerminal, ViInt32 edge);
Configures the Measure trigger for digital edge triggering.
Note This function is not supported on all devices. Refer to Supported Functions by Device for more information about supported devices.
Input | ||
---|---|---|
Name | Type | Description |
vi | ViSession | Identifies a particular instrument session. vi is obtained from the niDCPower_InitializeWithIndependentChannels function. |
channelName | ViConstString |
Specifies the channel(s) to use. Specify the channel(s) using the form PXI1Slot3/0,PXI1Slot3/2-3,PXI1Slot4/2-3 or PXI1Slot3/0,PXI1Slot3/2:3,PXI1Slot4/2:3, where PXI1Slot3 and PXI1Slot4 are instrument resource names and 0, 2, and 3 are channels. If you pass "" for this control, all channels in the session are used. |
inputTerminal | ViConstString |
Specifies the input terminal for the digital edge Measure trigger. You can specify any valid input terminal for this function. Valid terminals are listed in MAX under the Device Routes tab. For the PXIe-4147 and PXIe-4162/4163, refer to the Signal Routing topic for the device to determine which routes are available. This information is not available on a Device Routes tab in MAX. Specify the input 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 or channel. For example, you can set the input terminal on Dev1 to be /Dev2/Engine0/SourceCompleteEvent, where Engine0 is channel 0. |
edge | ViInt32 | Specifies whether to configure the Measure trigger to assert on the rising or falling edge. 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. |
Name | Type | Description |
---|---|---|
Status | ViStatus | Reports the status of this operation. To obtain a text description of the status code, call the niDCPower_error_message function. |
ViStatus niDCPower_ConfigureDigitalEdgeMeasureTrigger(ViSession vi, ViConstString inputTerminal, ViInt32 edge);
This function is deprecated. Use niDCPower_ConfigureDigitalEdgeMeasureTriggerWithChannels instead.
Configures the Measure trigger for digital edge triggering.
Note This function is not supported on all devices. Refer to Supported Functions by Device for more information about supported devices.
Input | ||
---|---|---|
Name | Type | Description |
vi | ViSession | Identifies a particular instrument session. vi is obtained from the niDCPower_InitializeWithIndependentChannels function. |
inputTerminal | ViConstString |
Specifies the input terminal for the digital edge Measure trigger. You can specify any valid input terminal for this function. Valid terminals are listed in MAX under the Device Routes tab. For PXIe-4147 and PXIe-4162/4163, refer to the Signal Routing topic for the device to determine which routes are available. This information is not available on a Device Routes tab in MAX. Input terminals can be specified in one of two ways. If the device is named Dev1 and your terminal is PXI_Trig0, you can specify the terminal with the fully qualified terminal name, /Dev1/PXI_Trig0, or with the shortened terminal name, PXI_Trig0. The input terminal can also be a terminal from another device. For example, you can set the input terminal on Dev1 to be /Dev2/SourceCompleteEvent. |
edge | ViInt32 | Specifies whether to configure the Measure trigger to assert on the rising or falling edge. 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. |
Name | Type | Description |
---|---|---|
Status | ViStatus | Reports the status of this operation. To obtain a text description of the status code, call the niDCPower_error_message function. |
ViStatus niDCPower_ConfigureSoftwareEdgeMeasureTriggerWithChannels(ViSession vi);
Configures the Measure trigger for software edge triggering. Use the niDCPower_SendSoftwareEdgeTriggerWithChannels function to assert the trigger condition.
Note This function is not supported on all devices. Refer to Supported Functions by Device for more information about supported devices.
Input | ||
---|---|---|
Name | Type | Description |
vi | ViSession | Identifies a particular instrument session. vi is obtained from the niDCPower_InitializeWithIndependentChannels function. |
channelName | ViConstString |
Specifies the channel(s) to use. Specify the channel(s) using the form PXI1Slot3/0,PXI1Slot3/2-3,PXI1Slot4/2-3 or PXI1Slot3/0,PXI1Slot3/2:3,PXI1Slot4/2:3, where PXI1Slot3 and PXI1Slot4 are instrument resource names and 0, 2, and 3 are channels. If you pass "" for this control, all channels in the session are used. |
Name | Type | Description |
---|---|---|
Status | ViStatus | Reports the status of this operation. To obtain a text description of the status code, call the niDCPower_error_message function. |
ViStatus niDCPower_ConfigureSoftwareEdgeMeasureTrigger(ViSession vi);
This function is deprecated. Use niDCPower_ConfigureSoftwareEdgeMeasureTriggerWithChannels instead.
Configures the Measure trigger for software triggering. Use the niDCPower_SendSoftwareEdgeTrigger function to assert the trigger condition.
Note This function is not supported on all devices. Refer to Supported Functions by Device for more information about supported devices.
Input | ||
---|---|---|
Name | Type | Description |
vi | ViSession | Identifies a particular instrument session. vi is obtained from the niDCPower_InitializeWithIndependentChannels function. |
Name | Type | Description |
---|---|---|
Status | ViStatus | Reports the status of this operation. To obtain a text description of the status code, call the niDCPower_error_message function. |
ViStatus niDCPower_ConfigureDigitalEdgeSequenceAdvanceTriggerWithChannels(ViSession vi, ViConstString inputTerminal, ViInt32 edge);
Configures the Sequence Advance trigger for digital edge triggering.
Note This function is not supported on all devices. Refer to Supported Functions by Device for more information about supported devices.
Input | ||
---|---|---|
Name | Type | Description |
vi | ViSession | Identifies a particular instrument session. vi is obtained from the niDCPower_InitializeWithIndependentChannels function. |
channelName | ViConstString |
Specifies the channel(s) to use. Specify the channel(s) using the form PXI1Slot3/0,PXI1Slot3/2-3,PXI1Slot4/2-3 or PXI1Slot3/0,PXI1Slot3/2:3,PXI1Slot4/2:3, where PXI1Slot3 and PXI1Slot4 are instrument resource names and 0, 2, and 3 are channels. If you pass "" for this control, all channels in the session are used. |
inputTerminal | ViConstString |
Specifies the input terminal for the digital edge Sequence Advance trigger. You can specify any valid input terminal for this function. Valid terminals are listed in MAX under the Device Routes tab. For the PXIe-4147 and PXIe-4162/4163, refer to the Signal Routing topic for the device to determine which routes are available. This information is not available on a Device Routes tab in MAX. Specify the input 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 or channel. For example, you can set the input terminal on Dev1 to be /Dev2/Engine0/SourceCompleteEvent, where Engine0 is channel 0. |
edge | ViInt32 | Specifies whether to configure the Sequence Advance trigger to assert on the rising or falling edge. 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. |
Name | Type | Description |
---|---|---|
Status | ViStatus | Reports the status of this operation. To obtain a text description of the status code, call the niDCPower_error_message function. |
ViStatus niDCPower_ConfigureDigitalEdgeSequenceAdvanceTrigger(ViSession vi, ViConstString inputTerminal, ViInt32 edge);
This function is deprecated. Use niDCPower_ConfigureDigitalEdgeSequenceAdvanceTriggerWithChannels instead.
Configures the Sequence Advance trigger for digital edge triggering.
Note This function is not supported on all devices. Refer to Supported Functions by Device for more information about supported devices.
Input | ||
---|---|---|
Name | Type | Description |
vi | ViSession | Identifies a particular instrument session. vi is obtained from the niDCPower_InitializeWithIndependentChannels function. |
inputTerminal | ViConstString |
Specifies the input terminal for the digital edge Sequence Advance trigger. You can specify any valid input terminal for this function. Valid terminals are listed in MAX under the Device Routes tab. For PXIe-4147 and PXIe-4162/4163, refer to the Signal Routing topic for the device to determine which routes are available. This information is not available on a Device Routes tab in MAX. Input terminals can be specified in one of two ways. If the device is named Dev1 and your terminal is PXI_Trig0, you can specify the terminal with the fully qualified terminal name, /Dev1/PXI_Trig0, or with the shortened terminal name, PXI_Trig0. The input terminal can also be a terminal from another device. For example, you can set the input terminal on Dev1 to be /Dev2/SourceCompleteEvent. |
edge | ViInt32 | Specifies whether to configure the Sequence Advance trigger to assert on the rising or falling edge. 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. |
Name | Type | Description |
---|---|---|
Status | ViStatus | Reports the status of this operation. To obtain a text description of the status code, call the niDCPower_error_message function. |
ViStatus niDCPower_ConfigureSoftwareEdgeSequenceAdvanceTriggerWithChannels(ViSession vi);
Configures the Sequence Advance trigger for software edge triggering. Use the niDCPower_SendSoftwareEdgeTriggerWithChannels function to assert the trigger condition.
Note This function is not supported on all devices. Refer to Supported Functions by Device for more information about supported devices.
Input | ||
---|---|---|
Name | Type | Description |
vi | ViSession | Identifies a particular instrument session. vi is obtained from the niDCPower_InitializeWithIndependentChannels function. |
channelName | ViConstString |
Specifies the channel(s) to use. Specify the channel(s) using the form PXI1Slot3/0,PXI1Slot3/2-3,PXI1Slot4/2-3 or PXI1Slot3/0,PXI1Slot3/2:3,PXI1Slot4/2:3, where PXI1Slot3 and PXI1Slot4 are instrument resource names and 0, 2, and 3 are channels. If you pass "" for this control, all channels in the session are used. |
Name | Type | Description |
---|---|---|
Status | ViStatus | Reports the status of this operation. To obtain a text description of the status code, call the niDCPower_error_message function. |
ViStatus niDCPower_ConfigureSoftwareEdgeSequenceAdvanceTrigger(ViSession vi);
This function is deprecated. Use niDCPower_ConfigureSoftwareEdgeSequenceAdvanceTriggerWithChannels instead.
Configures the Sequence Advance trigger for software triggering. Use the niDCPower_SendSoftwareEdgeTrigger function to assert the trigger condition.
Note This function is not supported on all devices. Refer to Supported Functions by Device for more information about supported devices.
Input | ||
---|---|---|
Name | Type | Description |
vi | ViSession | Identifies a particular instrument session. vi is obtained from the niDCPower_InitializeWithIndependentChannels function. |
Name | Type | Description |
---|---|---|
Status | ViStatus | Reports the status of this operation. To obtain a text description of the status code, call the niDCPower_error_message function. |
ViStatus niDCPower_DisableSequenceAdvanceTriggerWithChannels(ViSession vi);
Disables the Sequence Advance trigger. The specified channel(s) do not wait for a Sequence Advance trigger before advancing to the next iteration of the sequence.
This function is necessary only if you configured a Sequence Advance trigger in the past and now want to disable it.
Note This function is not supported on all devices. Refer to Supported Functions by Device for more information about supported devices.
Input | ||
---|---|---|
Name | Type | Description |
vi | ViSession | Identifies a particular instrument session. vi is obtained from the niDCPower_InitializeWithIndependentChannels function. |
channelName | ViConstString |
Specifies the channel(s) to use. Specify the channel(s) using the form PXI1Slot3/0,PXI1Slot3/2-3,PXI1Slot4/2-3 or PXI1Slot3/0,PXI1Slot3/2:3,PXI1Slot4/2:3, where PXI1Slot3 and PXI1Slot4 are instrument resource names and 0, 2, and 3 are channels. If you pass "" for this control, all channels in the session are used. |
Name | Type | Description |
---|---|---|
Status | ViStatus | Reports the status of this operation. To obtain a text description of the status code, call the niDCPower_error_message function. |
ViStatus niDCPower_DisableSequenceAdvanceTrigger(ViSession vi);
This function is deprecated. Use niDCPower_DisableSequenceAdvanceTriggerWithChannels instead.
Disables the Sequence Advance trigger. The device does not wait for a Sequence Advance trigger before advancing to the next iteration of the sequence. Refer to the Sequence Source Mode topic for more information about the Sequence Advance trigger.
Note This function is not supported on all devices. Refer to Supported Functions by Device for more information about supported devices.
Input | ||
---|---|---|
Name | Type | Description |
vi | ViSession | Identifies a particular instrument session. vi is obtained from the niDCPower_InitializeWithIndependentChannels function. |
Name | Type | Description |
---|---|---|
Status | ViStatus | Reports the status of this operation. To obtain a text description of the status code, call the niDCPower_error_message function. |
ViStatus niDCPower_ConfigureDigitalEdgePulseTriggerWithChannels(ViSession vi, ViConstString inputTerminal, ViInt32 edge);
Configures the Pulse trigger for digital edge triggering.
Note This function is not supported on all devices. Refer to Supported Functions by Device for more information about supported devices
Input | ||
---|---|---|
Name | Type | Description |
vi | ViSession | Identifies a particular instrument session. vi is obtained from the niDCPower_InitializeWithIndependentChannels function. |
channelName | ViConstString |
Specifies the channel(s) to use. Specify the channel(s) using the form PXI1Slot3/0,PXI1Slot3/2-3,PXI1Slot4/2-3 or PXI1Slot3/0,PXI1Slot3/2:3,PXI1Slot4/2:3, where PXI1Slot3 and PXI1Slot4 are instrument resource names and 0, 2, and 3 are channels. If you pass "" for this control, all channels in the session are used. |
inputTerminal | ViConstString |
Specifies the input terminal for the digital edge Pulse trigger. You can specify any valid input terminal for this function. Valid terminals are listed in MAX under the Device Routes tab. For the PXIe-4147 and PXIe-4162/4163, refer to the Signal Routing topic for the device to determine which routes are available. This information is not available on a Device Routes tab in MAX. Specify the input 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 or channel. For example, you can set the input terminal on Dev1 to be /Dev2/Engine0/SourceCompleteEvent. |
edge | ViInt32 | Specifies whether to configure the Pulse trigger to assert on the rising or falling edge. 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. |
Name | Type | Description |
---|---|---|
Status | ViStatus | Reports the status of this operation. To obtain a text description of the status code, call the niDCPower_error_message function. |
ViStatus niDCPower_ConfigureDigitalEdgePulseTrigger(ViSession vi, ViConstString inputTerminal, ViInt32 edge);
This function is deprecated. Use niDCPower_ConfigureDigitalEdgePulseTriggerWithChannels instead.
Configures the Pulse trigger for digital edge triggering.
Note This function is not supported on all devices. Refer to Supported Functions by Device for more information about supported devices
Input | ||
---|---|---|
Name | Type | Description |
vi | ViSession | Identifies a particular instrument session. vi is obtained from the niDCPower_InitializeWithIndependentChannels function. |
inputTerminal | ViConstString |
Specifies the input terminal for the digital edge Pulse trigger. You can specify any valid input terminal for this function. Valid terminals are listed in MAX under the Device Routes tab. Input terminals can be specified in one of two ways. If the device is named Dev1 and your terminal is PXI_Trig0, you can specify the terminal with the fully qualified terminal name, /Dev1/PXI_Trig0, or with the shortened terminal name, PXI_Trig0. The input terminal can also be a terminal from another device. For example, you can set the input terminal on Dev1 to be /Dev2/SourceCompleteEvent, where Engine0 is channel 0. |
edge | ViInt32 | Specifies whether to configure the Pulse trigger to assert on the rising or falling edge. 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. |
Name | Type | Description |
---|---|---|
Status | ViStatus | Reports the status of this operation. To obtain a text description of the status code, call the niDCPower_error_message function. |
ViStatus niDCPower_ConfigureSoftwareEdgePulseTriggerWithChannels(ViSession vi);
Configures the Pulse trigger for software edge triggering. Use the niDCPower_SendSoftwareEdgeTriggerWithChannels function to assert the trigger condition.
Note This function is not supported on all devices. Refer to Supported Functions by Device for more information about supported devices
Input | ||
---|---|---|
Name | Type | Description |
vi | ViSession | Identifies a particular instrument session. vi is obtained from the niDCPower_InitializeWithIndependentChannels function. |
channelName | ViConstString |
Specifies the channel(s) to use. Specify the channel(s) using the form PXI1Slot3/0,PXI1Slot3/2-3,PXI1Slot4/2-3 or PXI1Slot3/0,PXI1Slot3/2:3,PXI1Slot4/2:3, where PXI1Slot3 and PXI1Slot4 are instrument resource names and 0, 2, and 3 are channels. If you pass "" for this control, all channels in the session are used. |
Name | Type | Description |
---|---|---|
Status | ViStatus | Reports the status of this operation. To obtain a text description of the status code, call the niDCPower_error_message function. |
ViStatus niDCPower_ConfigureSoftwareEdgePulseTrigger(ViSession vi);
This function is deprecated. Use niDCPower_ConfigureSoftwareEdgePulseTriggerWithChannels instead.
Configures the Pulse trigger for software triggering. Use the niDCPower_SendSoftwareEdgeTrigger function to assert the trigger condition.
Note This function is not supported on all devices. Refer to Supported Functions by Device for more information about supported devices
Input | ||
---|---|---|
Name | Type | Description |
vi | ViSession | Identifies a particular instrument session. vi is obtained from the niDCPower_InitializeWithIndependentChannels function. |
Name | Type | Description |
---|---|---|
Status | ViStatus | Reports the status of this operation. To obtain a text description of the status code, call the niDCPower_error_message function. |
ViStatus niDCPower_DisablePulseTriggerWithChannels(ViSession vi);
Disables the Pulse trigger. The specified channel(s) do not wait for a pulse trigger before performing a pulse operation.
This function is necessary only if you configured a Pulse trigger in the past and now want to disable it.
Note This function is not supported on all devices. Refer to Supported Functions by Device for more information about supported devices
Input | ||
---|---|---|
Name | Type | Description |
vi | ViSession | Identifies a particular instrument session. vi is obtained from the niDCPower_InitializeWithIndependentChannels function. |
channelName | ViConstString |
Specifies the channel(s) to use. Specify the channel(s) using the form PXI1Slot3/0,PXI1Slot3/2-3,PXI1Slot4/2-3 or PXI1Slot3/0,PXI1Slot3/2:3,PXI1Slot4/2:3, where PXI1Slot3 and PXI1Slot4 are instrument resource names and 0, 2, and 3 are channels. If you pass "" for this control, all channels in the session are used. |
Name | Type | Description |
---|---|---|
Status | ViStatus | Reports the status of this operation. To obtain a text description of the status code, call the niDCPower_error_message function. |
ViStatus niDCPower_DisablePulseTrigger(ViSession vi);
This function is deprecated. Use niDCPower_DisablePulseTriggerWithChannels instead.
Disables the Pulse trigger. The device does not wait for a pulse trigger before performing a pulse operation. Refer to Pulse Mode for more information about the Pulse trigger.
This function is necessary only if you configured a Pulse trigger in the past and now want to disable it.
Note This function is not supported on all devices. Refer to Supported Functions by Device for more information about supported devices
Input | ||
---|---|---|
Name | Type | Description |
vi | ViSession | Identifies a particular instrument session. vi is obtained from the niDCPower_InitializeWithIndependentChannels function. |
Name | Type | Description |
---|---|---|
Status | ViStatus | Reports the status of this operation. To obtain a text description of the status code, call the niDCPower_error_message function. |
ViStatus niDCPower_ConfigureDigitalEdgeShutdownTriggerWithChannels(ViSession vi, ViConstString inputTerminal, ViInt32 edge);
Configures the Shutdown trigger for digital edge triggering.
Note This function is not supported on all devices. Refer to Supported Functions by Device for more information about supported devices
Input | ||
---|---|---|
Name | Type | Description |
vi | ViSession | Identifies a particular instrument session. vi is obtained from the niDCPower_InitializeWithIndependentChannels function. |
channelName | ViConstString |
Specifies the channel(s) to use. Specify the channel(s) using the form PXI1Slot3/0,PXI1Slot3/2-3,PXI1Slot4/2-3 or PXI1Slot3/0,PXI1Slot3/2:3,PXI1Slot4/2:3, where PXI1Slot3 and PXI1Slot4 are instrument resource names and 0, 2, and 3 are channels. If you pass "" for this control, all channels in the session are used. |
inputTerminal | ViConstString |
Specifies the input terminal for the digital edge Shutdown trigger. You can specify any valid input terminal for this function. Valid terminals are listed in MAX under the Device Routes tab. For the PXIe-4147 and PXIe-4162/4163, refer to the Signal Routing topic for the device to determine which routes are available. This information is not available on a Device Routes tab in MAX. Specify the input 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 or channel. For example, you can set the input terminal on Dev1 to be /Dev2/Engine0/SourceCompleteEvent, where Engine0 is channel 0. |
edge | ViInt32 | Specifies whether to configure the Shutdown trigger to assert on the rising or falling edge. 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. |
Name | Type | Description |
---|---|---|
Status | ViStatus | Reports the status of this operation. To obtain a text description of the status code, call the niDCPower_error_message function. |
ViStatus niDCPower_ConfigureSoftwareEdgeShutdownTriggerWithChannels(ViSession vi);
Configures the Shutdown trigger for software edge triggering. Use the niDCPower_SendSoftwareEdgeTriggerWithChannels function to assert the trigger condition.
Note This function is not supported on all devices. Refer to Supported Functions by Device for more information about supported devices
Input | ||
---|---|---|
Name | Type | Description |
vi | ViSession | Identifies a particular instrument session. vi is obtained from the niDCPower_InitializeWithIndependentChannels function. |
channelName | ViConstString |
Specifies the channel(s) to use. Specify the channel(s) using the form PXI1Slot3/0,PXI1Slot3/2-3,PXI1Slot4/2-3 or PXI1Slot3/0,PXI1Slot3/2:3,PXI1Slot4/2:3, where PXI1Slot3 and PXI1Slot4 are instrument resource names and 0, 2, and 3 are channels. If you pass "" for this control, all channels in the session are used. |
Name | Type | Description |
---|---|---|
Status | ViStatus | Reports the status of this operation. To obtain a text description of the status code, call the niDCPower_error_message function. |
ViStatus niDCPower_DisableShutdownTriggerWithChannels(ViSession vi);
Disables the Shutdown trigger. The specified channel(s) do not wait for a Shutdown trigger.
This function is necessary only if you configured a Shutdown trigger in the past and now want to disable it.
Note This function is not supported on all devices. Refer to Supported Functions by Device for more information about supported devices
Input | ||
---|---|---|
Name | Type | Description |
vi | ViSession | Identifies a particular instrument session. vi is obtained from the niDCPower_InitializeWithIndependentChannels function. |
channelName | ViConstString |
Specifies the channel(s) to use. Specify the channel(s) using the form PXI1Slot3/0,PXI1Slot3/2-3,PXI1Slot4/2-3 or PXI1Slot3/0,PXI1Slot3/2:3,PXI1Slot4/2:3, where PXI1Slot3 and PXI1Slot4 are instrument resource names and 0, 2, and 3 are channels. If you pass "" for this control, all channels in the session are used. |
Name | Type | Description |
---|---|---|
Status | ViStatus | Reports the status of this operation. To obtain a text description of the status code, call the niDCPower_error_message function. |
ViStatus niDCPower_ExportSignalWithChannels(ViSession vi, ViInt32 signal, ViConstString signalIdentifier, ViConstString outputTerminal);
Routes signals (triggers and events) to the output terminal you specify. The route is created when the specified channel is committed.
Note This function is not supported on all devices. Refer to Supported Functions by Device for more information about supported devices Related Topics:
Triggers
Input | ||
---|---|---|
Name | Type | Description |
vi | ViSession | Identifies a particular instrument session. vi is obtained from the niDCPower_InitializeWithIndependentChannels function. |
channelName | ViConstString |
Specifies the channel(s) to use. Specify the channel(s) using the form PXI1Slot3/0,PXI1Slot3/2-3,PXI1Slot4/2-3 or PXI1Slot3/0,PXI1Slot3/2:3,PXI1Slot4/2:3, where PXI1Slot3 and PXI1Slot4 are instrument resource names and 0, 2, and 3 are channels. If you pass "" for this control, all channels in the session are used. |
signal | ViInt32 | Specifies which trigger or event to export. Defined Values: |
NIDCPOWER_VAL_SOURCE_COMPLETE_EVENT (1030) | Exports the Source Complete event. |
---|---|
NIDCPOWER_VAL_MEASURE_COMPLETE_EVENT (1031) | Exports the Measure Complete event. |
NIDCPOWER_VAL_SEQUENCE_ITERATION_COMPLETE_EVENT (1032) | Exports the Sequence Iteration Complete event. |
NIDCPOWER_VAL_SEQUENCE_ENGINE_DONE_EVENT (1033) | Exports the Sequence Engine Done event. |
NIDCPOWER_VAL_PULSE_COMPLETE_EVENT (1051) | Exports the Pulse Complete event. |
NIDCPOWER_VAL_READY_FOR_PULSE_TRIGGER_EVENT (1052) | Exports the Ready Pulse Trigger event. |
NIDCPOWER_VAL_START_TRIGGER (1034) | Exports the Start trigger. |
NIDCPOWER_VAL_SOURCE_TRIGGER (1035) | Exports the Source trigger. |
NIDCPOWER_VAL_MEASURE_TRIGGER (1036) | Exports the Measure trigger. |
NIDCPOWER_VAL_SEQUENCE_ADVANCE_TRIGGER (1037) | Exports the Sequence Advance trigger. |
NIDCPOWER_VAL_PULSE_TRIGGER (1053) | Exports the Pulse trigger. |
signalIdentifier | ViConstString | Reserved for future use. Pass in an empty string for this parameter. |
outputTerminal | ViConstString | Specifies where to export the selected signal. Relative Terminals: |
"" | Do not export signal |
---|---|
"PXI_Trig0" | PXI trigger line 0 |
"PXI_Trig1" | PXI trigger line 1 |
"PXI_Trig2" | PXI trigger line 2 |
"PXI_Trig3" | PXI trigger line 3 |
"PXI_Trig4" | PXI trigger line 4 |
"PXI_Trig5" | PXI trigger line 5 |
"PXI_Trig6" | PXI trigger line 6 |
"PXI_Trig7" | PXI trigger line 7 |
You can also supply a fully qualified terminal name to this control, for example, /Dev1/PXI_Trig0, or /Dev1/Engine0/PXI_Trig0, where Engine0 is channel 0.
Name | Type | Description |
---|---|---|
Status | ViStatus | Reports the status of this operation. To obtain a text description of the status code, call the niDCPower_error_message function. |
ViStatus niDCPower_ExportSignal(ViSession vi, ViInt32 signal, ViConstString signalIdentifier, ViConstString outputTerminal);
This function is deprecated. Use niDCPower_ExportSignalWithChannels instead.
Routes signals (triggers and events) to the output terminal you specify. The route is created when the session is committed.
Note This function is not supported on all devices. Refer to Supported Functions by Device for more information about supported devices Related Topics:
Triggers
Input | ||
---|---|---|
Name | Type | Description |
vi | ViSession | Identifies a particular instrument session. vi is obtained from the niDCPower_InitializeWithIndependentChannels function. |
signal | ViInt32 | Specifies which trigger or event to export. Defined Values: |
NIDCPOWER_VAL_SOURCE_COMPLETE_EVENT (1030) | Exports the Source Complete event. |
---|---|
NIDCPOWER_VAL_MEASURE_COMPLETE_EVENT (1031) | Exports the Measure Complete event. |
NIDCPOWER_VAL_SEQUENCE_ITERATION_COMPLETE_EVENT (1032) | Exports the Sequence Iteration Complete event. |
NIDCPOWER_VAL_SEQUENCE_ENGINE_DONE_EVENT (1033) | Exports the Sequence Engine Done event. |
NIDCPOWER_VAL_PULSE_COMPLETE_EVENT (1051) | Exports the Pulse Complete event. |
NIDCPOWER_VAL_READY_FOR_PULSE_TRIGGER_EVENT (1052) | Exports the Ready Pulse Trigger event. |
NIDCPOWER_VAL_START_TRIGGER (1034) | Exports the Start trigger. |
NIDCPOWER_VAL_SOURCE_TRIGGER (1035) | Exports the Source trigger. |
NIDCPOWER_VAL_MEASURE_TRIGGER (1036) | Exports the Measure trigger. |
NIDCPOWER_VAL_SEQUENCE_ADVANCE_TRIGGER (1037) | Exports the Sequence Advance trigger. |
NIDCPOWER_VAL_PULSE_TRIGGER (1053) | Exports the Pulse trigger. |
signalIdentifier | ViConstString | Reserved for future use. Pass in an empty string for this parameter. |
outputTerminal | ViConstString | Specifies where to export the selected signal. Relative Terminals: |
"" | Do not export signal |
---|---|
"PXI_Trig0" | PXI trigger line 0 |
"PXI_Trig1" | PXI trigger line 1 |
"PXI_Trig2" | PXI trigger line 2 |
"PXI_Trig3" | PXI trigger line 3 |
"PXI_Trig4" | PXI trigger line 4 |
"PXI_Trig5" | PXI trigger line 5 |
"PXI_Trig6" | PXI trigger line 6 |
"PXI_Trig7" | PXI trigger line 7 |
Name | Type | Description |
---|---|---|
Status | ViStatus | Reports the status of this operation. To obtain a text description of the status code, call the niDCPower_error_message function. |
ViStatus niDCPower_SendSoftwareEdgeTriggerWithChannels(ViSession vi, ViInt32 trigger);
Asserts the specified trigger. This function can override an external edge trigger.
Note This function is not supported on all devices. Refer to Supported Functions by Device for more information about supported devices Related Topics:
Triggers
Input | ||
---|---|---|
Name | Type | Description |
vi | ViSession | Identifies a particular instrument session. vi is obtained from the niDCPower_InitializeWithIndependentChannels function. |
channelName | ViConstString |
Specifies the channel(s) to use. Specify the channel(s) using the form PXI1Slot3/0,PXI1Slot3/2-3,PXI1Slot4/2-3 or PXI1Slot3/0,PXI1Slot3/2:3,PXI1Slot4/2:3, where PXI1Slot3 and PXI1Slot4 are instrument resource names and 0, 2, and 3 are channels. If you pass "" for this control, all channels in the session are used. |
trigger | ViInt32 | Specifies which trigger to assert. Defined Values: |
NIDCPOWER_VAL_START_TRIGGER (1034) | Asserts the Start trigger. |
---|---|
NIDCPOWER_VAL_SOURCE_TRIGGER (1035) | Asserts the Source trigger. |
NIDCPOWER_VAL_MEASURE_TRIGGER (1036) | Asserts the Measure trigger. |
NIDCPOWER_VAL_SEQUENCE_ADVANCE_TRIGGER (1037) | Asserts the Sequence Advance trigger. |
NIDCPOWER_VAL_PULSE_TRIGGER (1053) | Asserts the Pulse trigger. |
NIDCPOWER_VAL_SHUTDOWN_TRIGGER (1118) | Asserts the Shutdown trigger. |
Name | Type | Description |
---|---|---|
Status | ViStatus | Reports the status of this operation. To obtain a text description of the status code, call the niDCPower_error_message function. |
ViStatus niDCPower_SendSoftwareEdgeTrigger(ViSession vi, ViInt32 trigger);
This function is deprecated. Use niDCPower_SendSoftwareEdgeTriggerWithChannels instead.
Asserts the specified trigger. This function can override an external edge trigger.
Note This function is not supported on all devices. Refer to Supported Functions by Device for more information about supported devices Related Topics:
Triggers
Input | ||
---|---|---|
Name | Type | Description |
vi | ViSession | Identifies a particular instrument session. vi is obtained from the niDCPower_InitializeWithIndependentChannels function. |
trigger | ViInt32 | Specifies which trigger to assert. Defined Values: |
NIDCPOWER_VAL_START_TRIGGER (1034) | Asserts the Start trigger. |
---|---|
NIDCPOWER_VAL_SOURCE_TRIGGER (1035) | Asserts the Source trigger. |
NIDCPOWER_VAL_MEASURE_TRIGGER (1036) | Asserts the Measure trigger. |
NIDCPOWER_VAL_SEQUENCE_ADVANCE_TRIGGER (1037) | Asserts the Sequence Advance trigger. |
NIDCPOWER_VAL_PULSE_TRIGGER (1053 | Asserts the Pulse trigger. |
Name | Type | Description |
---|---|---|
Status | ViStatus | Reports the status of this operation. To obtain a text description of the status code, call the niDCPower_error_message function. |
ViStatus niDCPower_WaitForEventWithChannels(ViSession vi, ViInt32 eventId, ViReal64 timeout);
Waits until the specified channel(s) have generated the specified event.
The session monitors whether each type of event has occurred at least once for the specified channel(s) since the last time this function or the niDCPower_InitiateWithChannels function were called. If an event has only been generated once and you call this function successively, the function times out. Individual events must be generated between separate calls of this function.
Note Refer to Supported Functions by Device for more information about supported devices
Programming States
Input | ||
---|---|---|
Name | Type | Description |
vi | ViSession | Identifies a particular instrument session. vi is obtained from the niDCPower_InitializeWithIndependentChannels function. |
channelName | ViConstString |
Specifies the channel(s) to use. Specify the channel(s) using the form PXI1Slot3/0,PXI1Slot3/2-3,PXI1Slot4/2-3 or PXI1Slot3/0,PXI1Slot3/2:3,PXI1Slot4/2:3, where PXI1Slot3 and PXI1Slot4 are instrument resource names and 0, 2, and 3 are channels. If you pass "" for this control, all channels in the session are used. |
eventId | ViInt32 | Specifies which event to wait for. Defined Values: |
NIDCPOWER_VAL_SOURCE_COMPLETE_EVENT (1030) | Waits for the Source Complete event. |
---|---|
NIDCPOWER_VAL_MEASURE_COMPLETE_EVENT (1031) | Waits for the Measure Complete event. |
NIDCPOWER_VAL_SEQUENCE_ITERATION_COMPLETE_EVENT (1032) | Waits for the Sequence Iteration Complete event. |
NIDCPOWER_VAL_SEQUENCE_ENGINE_DONE_EVENT (1033) | Waits for the Sequence Engine Done event. |
NIDCPOWER_VAL_PULSE_COMPLETE_EVENT (1051) | Waits for the Pulse Complete event. |
NIDCPOWER_VAL_READY_FOR_PULSE_TRIGGER_EVENT (1052) | Waits for the Ready for Pulse Trigger event. |
timeout | ViReal64 | Specifies the maximum time allowed for this function to complete, in seconds. If the function does not complete within this time interval, NI-DCPower returns an error. |
Note When setting the timeout interval, ensure you take into account any triggers so that the timeout interval is long enough for your application
Name | Type | Description |
---|---|---|
Status | ViStatus | Reports the status of this operation. To obtain a text description of the status code, call the niDCPower_error_message function. |
ViStatus niDCPower_WaitForEvent(ViSession vi, ViInt32 eventId, ViReal64 timeout);
This function is deprecated. Use niDCPower_WaitForEventWithChannels instead.
Waits until the device has generated the specified event.
The session monitors whether each type of event has occurred at least once since the last time this function or the niDCPower_Initiate function were called. If an event has only been generated once and you call this function successively, the function times out. Individual events must be generated between separate calls of this function.
Note This function should only be called in the Running state. Refer to the Programming States Diagram for more information
Note Refer to Supported Functions by Device for more information about supported devices
Input | ||
---|---|---|
Name | Type | Description |
vi | ViSession | Identifies a particular instrument session. vi is obtained from the niDCPower_InitializeWithIndependentChannels function. |
eventId | ViInt32 | Specifies which event to wait for. Defined Values: |
NIDCPOWER_VAL_SOURCE_COMPLETE_EVENT (1030) | Waits for the Source Complete event. |
---|---|
NIDCPOWER_VAL_MEASURE_COMPLETE_EVENT (1031) | Waits for the Measure Complete event. |
NIDCPOWER_VAL_SEQUENCE_ITERATION_COMPLETE_EVENT (1032) | Waits for the Sequence Iteration Complete event. |
NIDCPOWER_VAL_SEQUENCE_ENGINE_DONE_EVENT (1033) | Waits for the Sequence Engine Done event. |
NIDCPOWER_VAL_PULSE_COMPLETE_EVENT (1051 ) | Waits for the Pulse Complete event. |
NIDCPOWER_VAL_READY_FOR_PULSE_TRIGGER_EVENT (1052) | Waits for the Ready for Pulse Trigger event. |
|timeout|ViReal64|Specifies the maximum time allowed for this function to complete, in seconds. If the function does not complete within this time interval, NI-DCPower returns an error.|
Note When setting the timeout interval, ensure you take into account any triggers so that the timeout interval is long enough for your application
Name | Type | Description |
---|---|---|
Status | ViStatus | Reports the status of this operation. To obtain a text description of the status code, call the niDCPower_error_message 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