External trigger ni pxi 5122

hello,
i want to generate an external trigger signal for an ni pxi 5122 to launch a specific line video : HD(720p,1080i).
what is a form of this external trigger ?

Hello,
Based on the Specifications Manual (pages 18 and 19) this module will accept a voltage signal from -5V to +5V.
http://www.ni.com/pdf/manuals/371172m.pdf
Please refer to the links below for more information about Video Triggering.
http://www.ni.com/white-paper/3735/en/
http://zone.ni.com/reference/en-XX/help/370592E-01/digitizers/5122_video_triggering/
Regards,
MCOTO.

Similar Messages

External trigger on PXIe 5672

Dear all,
I have two questions on 5672:
1.Is script the only way to control a external tigger?If not,What are other methods?
2.How can I konw a external trigger comes through LaBVIEW,or in other words,Is it possible that LabVIEW will get a signal when a external trigger comes.
Waiting for your replies.
Oshirs

The 5672 supports two types of triggers:
1) start trigger
2) script trigger
I assume you need more than just a simple start trigger. To answer your question, yes, you must use a script in order to use script triggers.
Once you initiate a script, there isn't a way to query the device to figure out which script instruction the device is currently executing. Of course, if you can control the external trigger in LabVIEW, then you should know where in the script the 5672 is at. So you may want to pursue the problem from that end.
Hope this helps!

NI PXI-5122 2bit external input

Hello.
I'm trying to acquire a normal Voltage signal with the channel 1.
But i also have to read (with the "PXI-5122") an external 2 bit input. Sended by another device.
Which port do you think is better to use to read this 2 bits?
The Bits arrives in parallel on 2 different channels.
Signal ------------------------------->PXI-5122 Chan 1
External Device ------>bit0 -------->PXI-5122 Port?
External Device ------>bit1 -------->PXI-5122 Port?

Actually from the DevSpec it seems that the Digital I/O is absent.
But i think that it may be possible to use the PFI0 and PFI1 as a 1 bit digital input.
This sentence comes from a NI 6013/6014 User Manual:"As an input, each PFI pin can be individually configured for edge or level
detection and for polarity selection."
(Even if it's not the same model of my device the functions names
should be the same)
So i think that it could be suff. to configure the trigger level in LabView in order to read the signal as a 1 bit digital. input.
Can someone confirm this theory?

Software trigger the PCI-5122

hi
I am going to program a board with PCI-6552 and in meantime in specific times capture just one sample of the anolog output of the board by PCI-5122.
1) Can I use the digital output of one channel of PCI-6552 as trigger for PCI-5122 (to activate the fetching of PCI-5122) e.g. by connecting the output of PCI-6552 to the external trigger input of PCI-5122.
2) Does it need to synchronize the two boards.
2) Is there any example for software triggering the PCI-5122, and how long it takes from triggering to sampling the data.
3) How I can capture just one sample in every triggering time and then wait for another trigger time.

1) after programming the two output of the NI-6552 (DIO0 and DIO1) with the same pattern and connecting the DIO0 to Ch0 of PCI-5122 and DIO1 to external trigger of PCI-5122 and assigning the external trigger as the edge trigger source, the the signal is different from when the Ch0 is assigned as the trigger source. why are they different, also it does not accept two triggers sequentially. (Pic 1)
2)I am using a loop for generating the data and a loop for aquisition, when I using two trigger in one cycle and select niscope repeat_time=4, the signal position for 8 aquisition should be the same but as you can see in figure 3 the first two pulse are correct but the other ones are different.
Attachments:
pic1.bmp ‏2305 KB
pic2.bmp ‏2640 KB
pic3.bmp ‏2305 KB

External trigger of ni pxi 5122

hello,
i want use external trigger of ni pxi 5122 to select video line (video HD).
how it is the form of the trigger in this case?

Hello,
Based on the Specifications Manual (pages 18 and 19) this module will accept a voltage signal from -5V to +5V.
http://www.ni.com/pdf/manuals/371172m.pdf
Please refer to the links below for more information about Video Triggering.
http://www.ni.com/white-paper/3735/en/
http://zone.ni.com/reference/en-XX/help/370592E-01/digitizers/5122_video_triggering/
Regards,
MCOTO.

PXI-5122 External Sample Clock

PXI-1031 Chassis
PXI-8106 PC
PXI-5122 14bit 100MS/s Digitizer
Labview 8.5
I am driving X-Y mirrors steering a laser.
I am measuring the reflected light
to develop a raster image of a sample.
I have a pixel clock running at 60MHz that
I want to clock the acquistion and external
trigger that defines the 'line valid' or sampling
across the mirrors during their constant velocity
range.
I am using [PFI0 with 'READY for START EVENT'] as
a start pulse to run my x-y mirror scan.
CH0: Analog signal
SMA TRIG: line valid
AUX: PFI0 with 'READY for START EVENT'
In the property node 'niScope'
when I add the following elements:
Sample Clock Timebase Source = VAL_NO_SOURCE
Sample Clock Timebase Rate = 60000000
Sample Clock Timebase Divisor = 1
I get the following message:
Error -1074118614 occurred at Error occurred at: niScope Fetch Binary 16.vi:2
Possible reason(s):
Driver Status: (Hex 0xBFFA402A)
An acquisition has not been initiated.
Error -1074134971 occurred at Property Node (arg 4) in CSKB-4X_VID.vi
Possible reason(s):
The channel or repeated capability name is not allowed.
Attribute: NISCOPE_ATTR_SAMP_CLK_TIMEBASE_SRC, Channel: 0
Attached are the VIs with the elements added to the niScope property node
and without.
I get the above errors even when I set the 'Sample Clock Timebase Source'
to 'VAL_NO_SOURCE'
It appears, by just adding the elements, it gives me the error(s).
How can I get the external sampling clock to work along with external trigger?
Solved!
Go to Solution.
Attachments:
CSKB-4_VID.vi ‏148 KB
CSKB-4X_VID.vi ‏146 KB

Hi csk,
I was wondering if you could clarify how many
samples you wish to take. Am I correct that you wish to take 30,000
sets of 150 samples each, or do you mean you want to take 150 sets of
30,000 samples each (since 30,000 periods of the 60 MHz clock fits
within 90% of a 1.8kHz signal)? In either case, the current method you
are using is only going to acquire a single record each time through
the loop, and so you will be limited by how fast you can retrigger in
software.
For your application, it sounds like you will
need to perform a multi-record acquisition, as this will allow you to
specify what condition to trigger off of and how many samples to
acquire each time the trigger occurs. In this way, each "transition" of the sawtooth wave is considered a single record, and you are acquiring multiple different records corresponding to each time a rising edge trigger occurs. I believe that you can accomplish
exactly what you need with only a slight modification to the niScope
shipping example "niScope EX Multi Record Fetch More Than Available
Memory.vi" (found at Start » Programs » National Instruments » NI-SCOPE
» Examples). With this VI, you can specify that you wish each record to
have a min record length of 30,000 samples (or 150 samples if this is
the case) and that you wish to acquire 150 records (or 30,000 if this
is the case). The only major change that you would need to make is to
change the Configure Trigger VI to be a Digital Edge trigger rather
than an analog trigger. With this and a few other modifications (ie -
configuring the external clock) you should be able to accomplish what
you need. Please let me know if I explained this alright and if my
assumptions are correct. Thanks, and best of luck!
Daniel S.
National Instruments

Re-arming trigger time with pxi-5122

Hi all!
this is my first discussion in this forum so I'm not sure it's the right place to post it, because i'm using LabView but maybe it is an hardware problem.
So... I have a problem to calculate the re-arm trigger time for the pxi 5122.
From the data sheets I read that it should be about 3 us with the tdc off or 12 us if on.
But I needed an accurate measure of the dead time following each record measured so i decided to find it by myself...
Using an acquisition program I have previous written in LabView, I started single acquisitions of 10000 records and each record is composed of 128 samples; as signal I used square waves with different frequencies, of 10 volts peak-to-peak (my trigger was set on the first channel of 5122 with 1 volt of edge value).
First acquisition: 50 kHz wave. Theoretically I need 0.2 s to capture 10000 records without loosing any signals from the square wave. Choosing an acquisition time for a single record of 15.3 us, I found that the time required was 0.199998 s, very similar to the expected one.
Then choosing an acquisition time for a single record of 15.4 us, I found about 0.4 s.
I can guess that in this second case one every two wave peaks goes lost so I required twice the time to capture 10000 records.
Because a wave period is 20 us I have calculated a dead time of 20 - 15.3 = 4.7 us.
It wasn't as the 3 us described for the 5122 but i wasn't impressed and i went on with my try.
Second wave: 20 kHz. I need 0.5 s to capture 10000 records without loosing signals from the square waves.
What i found was that in this case, choosing an acquisition time for a single record of 39.6 us I required 0,5 s to capture all the peaks, while with 39.7 us I required about 1 second, again twice the time.
As the previous example I have calculated the dead time: 50 - 39.6 = 10.4 us.
Very strange... the dead time I supposed being the rearming trigger (and so fixed) was different for the 2 cases.
Trying with others waves lenghts, values were always different.
This happen also fixing the frequency of the square wave and changing the number of samples per record.
For example, with 128 samples per records as I said before I needed a measure time of about 15.3 us to collect all the consecutive peaks, while with 64 samples I needed 12,8 us and so on.
So it seems to be a dependency between the dead time after a records ( the rearming trigger? now i'm not so sure if I can call so) and the sampling frequency of the pxi 5122.
But I don't know why the DAQ behave in this way.
Is it right? Rearm time should be fixed,shouldn't it?
I know it required a bit of time to read my problem but i tried to be more accurate I could.
Thank you in advance.
Giacomo
Solved!
Go to Solution.

Just as with full blown oscope, the cannot select a timing period between the scales shown on the front panel. For example, the horizontal setting is labled 1us, 2us, 5us, etc. You cannot select 2.5us. Here is an excerpt from the PXI-5122 spec manual triggering section:
Divide by
n decimation available where 1<n<65,535
For more information about Sample Clock and decimation, refer to the NI High-Speed Digitizers Help.
What this means is that when you change from 15.3us to 15.4us, the scope changes timing ranges. That is why it takes twice as long to acquire the samples.
- tbob
Inventor of the WORM Global

Ni pxi 5122 yuv

hello,
i want to understand why for testing video signal like RGB,Y/C.. we connect directly a video signal in a ni pxi 5122 but for yuv signal we must use an external card who has a trigger connected to a trigger of ni pxi 5122 ??

Hello hamdoulah
Here you can find related information:
DVD video-YUV output test using NI 5112
What is the NI BNC-2178 VideoMUX and How Do I Install It?
Regards
Frank R.

Ni pxi 5122

Bonjour,
je vais déclencher une ligne vidéo (HD ) a partir d'un ni-pxi 5122 et un trigger extérieur(external TRIG).
avez vous une idée sur ce trigger comment peut-être sa fréqunece,amplitude..?

In LabVIEW, select Help->Find Examples... When the dialog comes up, search for NI-SCOPE. You should find what you need.
This account is no longer active. Contact ShadesOfGray for current posts and information.

How to use PXI Star Trigger for PXIe-5663 in PXIe-1075 chassis

HI all,
I have this sytem configuration:
PXIe-8135 controller. Windows 7 64-bit, RFSA 2.7.5. NI-SYNC 3.4.1
PXIe-1075 chassis
PXIe-5663 (2x)
PXIe-6672 Timing & Sync Card (slot #10)
I want to trigger the recording of my Digitizer with an external trigger.
The External Trigger is connected to PFI0 of the PXIe-6672 Timing card.
Then, the PXIE-6672 card routes the trigger to the backplane of the PXIe-1072 (Destination "NISYNC_VAL_PXITRIG0")
The PXIe-5663 are triggered with “NIRFSA_VAL_PXI_TRIG0_STR” as the source.
The trigger fires my PXIe-5663 correctly, but the timing is not tight (> 5ns).
I would like to use the PXI Star trigger instead, I think that I should be able to acheive much better synchronization with this.
But NI-RFSA won't let me do this:
When I try to call
"niRFSA_ConfigureDigitalEdgeStartTrigger(rfsa_session, NIRFSA_VAL_PXI_STAR_STR , NIRFSA_VAL_RISING_EDGE)", I get the error:
"Specified Route Cannot Be Satisfied, Because the Hardware Does Not Support It"
I don't understand why the PXIe-5663E would not be able to use that Route.
Any idea?
Regards,
Serge
Serge Malo, ing.
Concepteur logiciel
Software Developer
T (514) 842-7577 x648 | [email protected]

That explanation isn't quite right. Usually, even PXIe modules have a connection to PXI_Star. The PXIe standard added the PXIe_DStar trigger buses, and it also preserved the PXI_Star bus from the PXI standard.
However, there is an additional twist in this situation. I'm assuming that your PXIe-5663 includes a PXIe-5622 as the digitizer. It turns out that a synchronization technique called NI-TClk has eliminated the need for our more recent digitizers to rely on triggering from PXI_Star. I was able to find some documentation that includes this information, here and here. Given that, I think you have two options that should result in better synchronization.
The first option is to use TClk; I found an example program that demonstrates using TClk to acheive phase coherent signal acquisition across two 5663s. The second option is to use cables of matched length to connect two PFI front panel terminals of the timing board (6672) to the PFI1 front panel terminals of the digitizers (5622). The timing board would accept the external trigger on PFI0 and then issue triggers on PFI1 and PFI2 with around 500 ps of skew (manual, page A-4) . The digitizers would use NIRFSA_VAL_PFI1_STR as the trigger. I hope one of these solutions will meet the demands of your particular application.
I will also follow up with the owners of the RFSA product documentation to see if we can include a note about why PXI_Star is not supported in some cases.
James Blair
NI R&D

Does the external trigger of the 5152 count as a second channel?

Hi everyone,
The PXI-5152 digitizer is listed as providing a 2GS/s sampling rate (TIS) for one channel only. My question is whether or not the External Trigger channel counts as a "second channel" when used during data acquisition. If so, does this cause the maximum acheivable sampling rate to drop to 1GS/s for my data channel (CH 0)?
My experience has been that this is the case, but I lack a smoking gun which explicitly states this. When I use the external trigger to control data acquisition on Channel 0, I'm only ever able to acheive 1GS/s. Am I making a mistake?
I was hoping that the trigger port would act as a simple comparator. If not, does this imply that the external trigger channel is being sampled at 1GS/s?
Many thanks,
Jimmy

Hi Jimmy,
The External Trigger is not digitized and therefore is not a second channel. It is appropriate to consider it like a comparator. It can be used as an analog trigger source for the TIS acquisition on channel 0 to achieve 1 channel at 2 GS/s. I am not sure why you are only achieving 1 GS/s.
I recommend starting with an example program such as "Configured Acquisition". You can navigate to this example through the Example Finder, or by using your Start Menu and navigating to All Programs>>National Instruments>>NI-SCOPE>>Examples. Select your preferred programming environment such as LabVIEW and locate Configured Acquisition.
Once you have the example open try the following settings to achieve 2GS/s on ch0 triggered from the external trigger input. Set the sampling rate to 2GS/s, the channel to 0, check "TIS Enabled", and ensure that Enforce Realtime is also checked. Set the trigger type to Edge, and the trigger source to the External Trigger.
- Jennifer O.
Product Support Engineer - High Speed Digitizers

Soft Front Panel PXI-5122 and RealTime

Can anyone tell me if the PXI 5122 Digitizer has a Soft Front Panel that is supported in LabView Realtime (8.6).
When I load the one that is on my system, it doesn't recognize my external pxi chassis hardware.
Thanks.

The soft front panel that ships with the 5122 works only under Windows with devices directly accessible from Windows. Since RT is a separate OS running over a network, the SFP will not work with it. It could be modified to do this, however. I will pass your suggestion on. You may want to consider entering a product suggestion yourself (use this link). Strange as it may seem, suggestions from customers are weighted more highly than suggestions from internal engineers .
This account is no longer active. Contact ShadesOfGray for current posts and information.

PXIe-5122 triggering problem

I have some problem in triggering the signal in my scope. I use PXIe-512214-bit 100MS/s Digitizer. What I did is I route Board Clock to RTSI0 and then in niScope Configure Triger Digital.vi, I use RTSI0 as the trigger source. But it always reported error "Source terminal to be routed could not be found on the device"and Destination Terminal is: PXI_Trig0. When I route RTSI clock to RTSI0, program runs, but the scope does not show any signal. What should I do now? Do you have any suggestions? Thank you very much

Hi, Tunde
Thanks for your reply. I am only using PXIe-5122 for Impedance Analyzer Software. Right now the scope has some problem in getting the signal. It always shows "Insufficient Signal Level on Reference Signal Increase: FGEN Amplitude". What I did is to route Board clock to RSTI0 using niFgen Route Signal Out.vi and then in niScope Configure Trigger Digital.vi I use RTSI 0 as trigger source. But it always reported error "Source terminal to be routed could not be found on the device"and Destination Terminal is: PXI_Trig0. I also tried routing RTSI clock to RTSI0, program runs and again it shows "Insufficient Signal Level on Reference Signal Increase: FGEN Amplitude". I am right now quite confused about what could be the problem. Attached is the code. The change that I made is in Initialize Scope.vi and Initialize Function Generator.vi. Thanks!
Attachments:
Impedance Analyzer Software June 2012.vi ‏419 KB

How to externally trigger the execution of TestStand with a start and abort button through a digital interface?

Hello,
I'm Currently evaluating TestStand as an alternative for an in-house developed Test Sequencer.
To start our own Test Sequencer we use a small box, connected to a DIO board. The box has a start button and an abort button. The box also has a pass, a fail and a running led.
The interface with this box is made via some digital lines of a PCI-DIO-96.
In our own Test Sequencer we have groups named Init, Run, Abort, Exit.
The Init group is executed at startup (only once). It is used to initialize all the HW and SW. -> I guess this is the Pre UUT Loop callback in TestStand.
The Exit group is only executed once at the end of the day when the application is terminated. It is used to free all the used hardware and cleanup all the resources. This probably is the Post UUT Loop Callback in TS.
When a product needs to be tested, the operator presses the "start" button which triggers our own Test Sequencer and the run and abort group are being executed (first the run group, afterwards the abort group).
When the product is being tested the "running led" of the little box lights up to indicate to the operator that the application is running. (only when the run and abort group are running)
The Run group has all the functional tests in it. (MainSequence)
The abort group is used to put everything back in it's original state after the test on this single product is done. (Post UUT)
When executing the tests and something goes wrong (operator gets stuck in a clamper, ...) the operator can still press the abort button and then the execution immediately jumps from the currently executing step in the run group to the first step of the abort group. So, when something goes wrong, immediately the abort group is called.
At the end of the run and abort group, if no errors occured, the "pass led" lights up. If one or more steps went wrong the "fail" led lights up.
This setup can also be used to test multiple product in parallel. At that time all the different parallel testers have such a small box which contains a "start" and "abort" button and a pass, fail and running led. (it is possible that they are all connected to the same PCI-DIO-96 board. )
My question:
Is it possible to do something similar like this in Teststand? If yes, is there an example available that shows me how to do this in TestStand? (externally trigger the execution of TestStand)
Typically, in the Init group (Pre UUT Loop) the digital interface box gets initialised.
In the Close group (Post UUT Loop) the digital interface box is taken out of scope.
Note: The PCI-DIO-96 board to which the digital interface box is connected will also be used in the rest of the developed application (MainSequence, ...)
What's really important for me is that I can create a process model that all the application developers in our organisation can use. I really don't want any of the application developers (limited software experience) to mess around in all the features of TestStand.
For them it's important that they just add the function DigitalInterfaceBoxInit () in the Pre UUT Loop Callback and the DigitalInterfaceBoxClose () in the Post UUT Loop Callback, and then everything works!
It is important that the appliation developers do not have to create any global variables, other functions, synchronisations, parallel sequences, ... in TestStand. All this needs to be done with a simple call to the DigitalInterfaceBoxInit function.
Thanks in advance for all the help!
Best Regards,
Dennis Vanotterdijk
[email protected]

Dennis-
Your application sounds very well suited to TestStand's abilities. I am also quite impressed with your knowledge of how TestStand's architecture is arranged when you are still just considering whether or not to use it.
I think that TestStand would work really well for you in this application. Like you mentioned it will provide you with a form of standardization for your application developers to work from. It also provides the flexibility for you to add your custom routines in many different places. TestStand also makes parallel and batch testing much easier in TS 2.0 so that you could develop one test for your product and execute different instances of it in parallel to test multiple products at once.
As for your specific question about how to c
ontrol TestStand using a DIO board. I think this is very feasible and should not be too difficult. Since TestStand provides you the ability to create a custom operator interface your operator interface could monitor the status of your DIO board and launch/abort executions based on the read values. Usually the executions are launched/aborted when a button on the GUI is pressed however, I do not see any thing different about basing the action on a DI signal vs a mouse click. I am sure your application is more involved than this high level description but from the sounds of it I think it is very possible to do with TestStand.
Based on my experience of building test systems with TestStand and your description of the application, I would feel very confident in using TestStand to achieve all the goals you mentioned. If you have further detailed questions on how one of your features might be implemented, feel free to contact one of our Application Engineers or email us at www.ni.com/ask
and we would be glad to help you.
Best regards,
Richard McDonell
National Instruments

Data-acquisition with NI 6036E DAQ card & GPIB using an external trigger

Hi all,
I hope somebody could give me some help with the following and answer some questions:
Simple system description:
Labview 6.1
PCI-GPIB card
6036E DAQ card
In my system, I am using an external analog trigger signal (A) for continuous data-acquisition. Characteristics of the analog trigger signal (A) are: ~40 Hz, signal height +1.48V, triggered by rising edge (the analog trigger signal (A) could be changed to a TTL signal). Each data-acquisition is done within ~1.0 ms after the rising edge of the trigger pulse. The timing of the data-acquisition and analyzing procedure is controlled by execution in a sequence structure placed in a loop.
Now, I connected a power meter to the system, to measure the laser power during the data-acquisition. The power meter has two options to provide the laser power data:
a) via analog signal output (voltage corresponds to laser power in watts)
b) via GPIB (direct output reading of laser power in watts).
Problem:
During a certain point in my data-acquisition sequence structure (defined by a frame), I want to use the next occuring analog trigger signal (A) to acquire 1 value from the power meter.
How do I do this in Labview programming for the following two situations?
a) If I connect the analog output from the power meter to an analog input channel of the 6036E DAQ card. The analog trigger (A) would be connected to a second analog input channel (In case the analog trigger signal (A) is changed to a TTL signal it would be connected to the PFI0/Trig input pin on the DAQ card).
b) If I use the GPIB connection of the power meter. The analog trigger (A) would be connected to a second analog input channel (In case the analog trigger signal (A) is changed to a TTL signal it would be connected to the PFI0/Trig input pin on the DAQ card).
An other possibility would be to trigger the power meter directly, so it outputs constantly power meter values at ~40 Hz. How could I than acquire 1 power meter value (at a certain time im my sequence structure) via analog input at DAQ card or GPIB?
Additional questions:
How do I configure the PFI0/Trig pin on the 6036E DAQ board individually as an INPUT?
How do I use an analog trigger signal (A) as counting signal for a loop, or as an activation signal for a sequence structure which includes GPIB commands?
It would be very nice if somebody could give me some help.
Kind regards,
beam

Hi beam,
I just want to verify that I understand your situation correctly:
An external trigger signal (A) is wired to one of your input channels (e.g. CH0) to trigger data acquisition of a second channel (e.g. CH1). Your power meter is connected to an analog input channel, which you would like to trigger with a certain rising edge at some of your sequence structure.
Problem:
During a certain point in my data-acquisition sequence structure (defined by a frame), I want to use the next occuring analog trigger signal (A) to acquire 1 value from the power meter.
How do I do this in Labview programming for the following two situations?
a) If I connect the analog output from the power meter to an analog input channel of the 6036E DAQ card. The analog trigger (A) would be connected to a second analog input channel (In case the analog trigger signal (A) is changed to a TTL signal it would be connected to the PFI0/Trig input pin on the DAQ card).
If a task has been configured to acquire signal from one analog channel, it's not possible to run a second analog input task or to add a second channel on the fly. You had mentioned that it's possible to read from the instrument through GPIB. Is it possible to perform a software trigger such that at a certain frame of your structure, when the trigger signal A reaches voltage "x", a GPIB command is written to your power meter to query a measurement reading?
Additional questions:
How do I configure the PFI0/Trig pin on the 6036E DAQ board individually as an INPUT?
You do not need to explicitly configure the PFI0 line as an input. If you want to use it as an input such that it acts as an analog trigger, simply wire the trigger signal to this pin. When configuring the trigger in your software, specify PFI0 as the trigger source.
How do I use an analog trigger signal (A) as counting signal for a loop, or as an activation signal for a sequence structure which includes GPIB commands?
You can try using the Limit VI to find out when the trigger signal reaches a certain level, and count how many times this level is reached. Similarly, you can use this as the condition to execute GPIB commands.
Hope this helps,
Lesley

External trigger ni pxi 5122

Similar Messages

Maybe you are looking for