|NI-DCPower (English | Japanese)|
A trigger is a signal to the device to start an operation. An event is a signal from the device that indicates that an operation was completed or a specific state was reached. You can use triggers and events to synchronize operations within a single NI power supply or SMU and operations with other PXI/PXIe devices.
|Note The NI PXI-4110 and NI PXI-4130 do not support triggers or signal routing. The devices support only one event, the Source Complete event, that must be called with the Wait For Event VI or the niDCPower_WaitForEvent function.|
NI-DCPower supports the following triggers.
The device waits for this trigger upon entering the
Running state (after
you call the niDCPower Initialize With Channels VI or the
function). The source unit and measure unit do not
perform any operations until this trigger is received.
|Source||The device waits for this trigger before
the source unit modifies the source configuration.
This trigger is only available when you set output function to DC Voltage or DC Current using the niDCPower Configure Output Function VI or niDCPower_ConfigureOutputFunction function.
|Measure||The measure unit takes a measurement
when it receives this trigger. While the measure unit is
taking a measurement, this trigger is ignored.
The measure unit only responds to the Measure trigger if the niDCPower Measure When property or the NIDCPOWER_ATTR_MEASURE_WHEN attribute is set to On Measure Trigger. Otherwise the Measure trigger is ignored. Refer to Acquiring Measurements for more information.
|Sequence Advance||The source unit waits for this trigger
after an iteration of the sequence completes, just before the
next iteration starts. The niDCPower Sequence
Loop Count property or the NIDCPOWER_ATTR_SEQUENCE_LOOP_COUNT
attribute should be set to a value higher than 1 for the
sequence to repeat.
The Sequence Advance trigger is only available in Sequence source mode. The Sequence Advance trigger has no effect when running in Single Point source mode.
|Pulse||The source unit waits for this trigger before transitioning from
the Pulse Bias to the Pulse Level.
This trigger is only available when you set output function to Pulse Voltage or Pulse Current using the niDCPower Configure Output Function VI or niDCPower_ConfigureOutputFunction function.
There are three possible configurations (types) for a trigger.
When configured for digital edge triggering, the device responds to the trigger on one of the physical PXI back plane trigger lines (PXI_Trig0, PXI_Trig1, …, PXI_Trig7).
The device performs the operation corresponding to the trigger when it detects a rising edge or a falling edge, shown in the following figure, on the physical trigger line.
When configuring a digital edge trigger, you must specify the input terminal that should be connected to the trigger. The input terminal can be a physical trigger line or an output terminal from another device. If you specify an output terminal from another device, NI-DCPower automatically finds a route (if one is available) from that terminal to the input terminal (going through a physical PXI back-plane trigger line). Refer to Multi-Device Synchronization and Signal Routing for more information.
To configure various digital edge triggers, use the following VIs and functions.
|niDCPower Configure Digital Edge Start Trigger||niDCPower_ConfigureDigitalEdgeStartTrigger|
|niDCPower Configure Digital Edge Source Trigger||niDCPower_ConfigureDigitalEdgeSourceTrigger|
|niDCPower Configure Digital Edge Measure Trigger||niDCPower_ConfigureDigitalEdgeMeasureTrigger|
|niDCPower Configure Digital Edge Sequence Advance Trigger||niDCPower_ConfigureDigitalEdgeSequenceAdvanceTrigger|
|niDCPower Configure Digital Edge Pulse Trigger||niDCPower_ConfigureDigitalEdgePulseTrigger|
When configured for software edge triggering, the device waits to receive the trigger signal from software. To send the trigger signal to the device, use the niDCPower Send Software Edge Trigger VI or the niDCPower_SendSoftwareEdgeTrigger function.
To configure the various software edge triggers, use the following VIs and functions.
|niDCPower Configure Software Edge Start Trigger||niDCPower_ConfigureSoftwareEdgeStartTrigger|
|niDCPower Configure Software Edge Source Trigger||niDCPower_ConfigureSoftwareEdgeSourceTrigger|
|niDCPower Configure Software Edge Measure Trigger||niDCPower_ConfigureSoftwareEdgeMeasureTrigger|
|niDCPower Configure Software Edge Sequence Advance Trigger||niDCPower_ConfigureSoftwareEdgeSequenceAdvanceTrigger|
|niDCPower Configure Software Edge Pulse Trigger||niDCPower_ConfigureSoftwareEdgePulseTrigger|
When configured for None (Disabled), the device does not wait for the trigger before performing the corresponding operation. For example, the device starts without waiting for a Start trigger, or the device starts the source operation without waiting for a Source trigger.
To configure the various triggers for None (Disabled), use the following VIs and functions.
|niDCPower Disable Start Trigger||niDCPower_DisableStartTrigger|
|niDCPower Disable Source Trigger||niDCPower_DisableSourceTrigger|
|niDCPower Disable Sequence Advance Trigger||niDCPower_DisableSequenceAdvanceTrigger|
|niDCPower Disable Pulse Trigger||niDCPower_DisablePulseTrigger|
NI-DCPower supports the following events.
|Source Complete||The source unit generates this event
when it completes the sourcing operation and waits for the
configured source delay.
In Single Point source mode, the source unit generates the Source Complete event whenever source configuration is modified (after waiting for the configured source delay); in Sequence source mode, the source unit generates the Source Complete event after waiting for the source delay in every step in the sequence.
|Measure Complete||The measure unit generates this event when it finishes taking a measurement.|
|Sequence Iteration Complete||The device generates this event when all the steps in the sequence are completed, once per iteration of the sequence. For example, if the niDCPower Sequence Loop Count property or the NIDCPOWER_ATTR_SEQUENCE_LOOP_COUNT attribute is set to 10, NI-DCPower generates ten events.|
|Sequence Engine Done||The device generates this event when it completes all iterations of the sequence.|
|Pulse Complete||The source unit generates this event when it completes the pulsing operation and waits for the configured source delay.
In Single Point source mode, the source unit generates the Pulse Complete event whenever source configuration is modified (after waiting for the configured source delay); in Sequence source mode, the source unit generates the Pulse Complete event after waiting for the source delay in every step in the sequence.
|Ready for Pulse Trigger||In Sequence source mode, if this is not the first step in a sequence, the source unit generates a Ready For Pulse Trigger event and waits for a Pulse trigger.|
There are three properties and attributes associated with each event that you can use to configure an event.
|niDCPower Event Pulse Polarity||NIDCPOWER_ATTR_EVENT_PULSE_POLARITY|
|niDCPower Event Pulse Width||NIDCPOWER_ATTR_EVENT_PULSE_WIDTH|
|niDCPower Event Output Terminal||NIDCPOWER_ATTR_EVENT_OUTPUT_TERMINAL|
The output terminal is the physical trigger line or an input terminal on another device. If an event is exported to a physical trigger line, the device outputs a pulse on that line when an event is generated.
The following properties and attributes are available for configuring events.
|Source Complete||niDCPower Source Complete Event Pulse Polarity||NIDCPOWER_ATTR_SOURCE_COMPLETE_EVENT_PULSE_POLARITY|
|niDCPower Source Complete Event Pulse Width||NIDCPOWER_ATTR_SOURCE_COMPLETE_EVENT_PULSE_WIDTH|
|niDCPower Source Complete Event Output Terminal||NIDCPOWER_ATTR_SOURCE_COMPLETE_EVENT_OUTPUT_TERMINAL|
|Measurement Complete||niDCPower Measure Complete Event Pulse Polarity||NIDCPOWER_ATTR_MEASURE_COMPLETE_EVENT_PULSE_POLARITY|
|niDCPower Measure Complete Event Pulse Width||NIDCPOWER_ATTR_MEASURE_COMPLETE_EVENT_PULSE_WIDTH|
|niDCPower Measure Complete Event Output Terminal||NIDCPOWER_ATTR_MEASURE_COMPLETE_EVENT_OUTPUT_TERMINAL|
|Sequence Iteration Complete||niDCPower Sequence Iteration Complete Event Pulse Polarity||NIDCPOWER_ATTR_SEQUENCE_ITERATION_COMPLETE_EVENT_PULSE_POLARITY|
|niDCPower Sequence Iteration Complete Event Pulse Width||NIDCPOWER_ATTR_SEQUENCE_ITERATION_COMPLETE_EVENT_PULSE_WIDTH|
|niDCPower Sequence Iteration Complete Event Output Terminal||NIDCPOWER_ATTR_SEQUENCE_ITERATION_COMPLETE_EVENT_OUTPUT_TERMINAL|
|Sequence Engine Done||niDCPower Sequence Engine Done Event Pulse Polarity||NIDCPOWER_ATTR_SEQUENCE_ENGINE_DONE_EVENT_PULSE_POLARITY|
|niDCPower Sequence Engine Done Event Pulse Width||NIDCPOWER_ATTR_SEQUENCE_ENGINE_DONE_EVENT_PULSE_WIDTH|
|niDCPower Sequence Engine Done Event Output Terminal||NIDCPOWER_ATTR_SEQUENCE_ENGINE_DONE_EVENT_OUTPUT_TERMINAL|
|Pulse Complete||niDCPower Pulse Complete Event Pulse Polarity||NIDCPOWER_ATTR_PULSE_COMPLETE_EVENT_PULSE_POLARITY|
|niDCPower Pulse Complete Event Pulse Width||NIDCPOWER_ATTR_PULSE_COMPLETE_EVENT_PULSE_WIDTH|
|niDCPower Pulse Complete Event Output Terminal||NIDCPOWER_ATTR_PULSE_COMPLETE_EVENT_OUTPUT_TERMINAL|
|Ready for Pulse Trigger||niDCPower Ready For Pulse Trigger Event Pulse Polarity||NIDCPOWER_ATTR_READY_FOR_PULSE_TRIGGER_EVENT_PULSE_POLARITY|
|niDCPower Ready For Pulse Trigger Event Pulse Width||NIDCPOWER_ATTR_READY_FOR_PULSE_TRIGGER_EVENT_PULSE_WIDTH|
|niDCPower Ready For Pulse Trigger Event Output Terminal||NIDCPOWER_ATTR_READY_FOR_PULSE_TRIGGER_EVENT_OUTPUT_TERMINAL|
You can synchronize multiple devices by routing signals (events and triggers) from one device to another.
You can export (route) the trigger and event signals to one of the physical PXI backplane trigger lines using the niDCPower Export Signal VI or the niDCPower_ExportSignal function. Instead of explicitly exporting signals to physical trigger lines, NI-DCPower can automatically create routes for you. To have NI-DCPower automatically create routes, set the digital edge input terminal on one device to be the event from another device.
To make Dev2 wait for the measurement of Dev1 to complete before Dev2 changes the source configuration, route the Measure Complete event of Dev1 to the Source trigger of Dev2. To do that, configure the source trigger of Dev2 to Digital Edge and set the input terminal to /Dev1/MeasureCompleteEvent.