Single pulse to radiate with PXI

Good day to all, how can I generate one single pulse on Labview to later radiate it on PXI withouth using any DAQ command , because there are some samples that do so, I would like the diration of the pulse to be in the us or less

Hi Frank12244,
What PXI module is generating the signal? The PXIe-5601, is a RF Downconverter used with our PXIe-5663/5663E Vector Signal Analyzer (VSA). The VSA is used for acquiring not generating. Do you have a RF Signal Generator in your PXI chassis? If you’re looking for the drivers for communicating with your PXI modules, go to ni.com/drivers and download the driver for the device. The drivers also come with LabVIEW examples, which you can access through the NI Example Finder.
Tunde S.
Applications Engineer
National Instruments

Similar Messages

Pulse modulated CW with PXI-5650 and PXI-6653

Hello,
I am trying to generate a pulse modulated CW signal with the PXI-5650 as the RF source and the PXI-6653 as the modulating signal. Basically I am trying to generate a simple radar waveform. It seems like this would be possible to use the Timing Module (6653) to turn the RF output on/off on the Signal Generator (5650), but I am not sure how to route signals from one to the other using LabView.
Has anyone tried this or something similar before? Can anyone please offer some advice?
Thanks!
-John
Solved!
Go to Solution.

Hi John,
From reading your post, it sounds like you want to use your timing and sync card to turn the RF output on/off, in others words, On Off Keying. OOK modulation is a built-in feature to the 5650. For more information, you can navigate in the NI RF Signal Generators Help to Devices -> NI RF Signal Generators -> NI 5650/5651/5652 Overview -> Modulation Modes, and just click on Modulation Modes.
An example of this can also be found in the NI Example Finder by navigating to Help -> Find Examples... in LabVIEW and then navigating in the NI Example Finder to Hardware Input and Output -> Modular Instruments -> NI-RFSG -> Modulated Waveforms -> RFSG 565x Digital Modulation.vi.
Regards,
Jason L.
Product Support Engineer
National Instruments

Pulse Generation application with DAQmx and a PXI-6624 module?

What is the best implementation method for the following pulse generation application
using LabVIEW, DAQmx and a PXI-6624 counter\timer module?
I have two rising edge trigger signals (Trigger-1 and Trigger-2).
There is ample spacing between each trigger. They never occur at the same time.
I need to generate a single pulse (fixed width, variable delay) whenever Trigger-1 occurs and
a finite pulse train (fixed width, variable delay, N-pulses) whenever Trigger-2 occurs.
However, the output must appear on one counter output because this composite signal
will be used as a trigger source for another PXI module in the rack.
With DAQmx and a TIO counter\timer can I use both the GATE (for Trigger-1) and
AUX (for Trigger-2) at the same time on the same counter to gate out the desired pulses?
Trigger-1 would be wired to the GATE of CTR0. One Trigger-1 event would generate one pulse on the output of CTR0.
Trigger-2 would be wired to the GATE of CTR1 and the output of CTR1 would be routed to the AUX input of CTR0.
One Trigger-2 event at the GATE of CTR1 would generate multiple pulses on output of CTR0.
Would DAQmx and the PXI-6624 TIO support this implementation?
What is the best way to accomplish the task at hand.
Thank You.
Best Regards,
Scooby

Hi Scooby,
I have looked into the application you have described and I see a potential problem with what you describe. In DAQmx, it is not possible to call the counters of the same DAQ device in the same task, so you cannot have the finite pulse train generation and the single pulse generation tasks running at the same time. What you can do, since you mention the triggers will not occur at the same time, is to stop one counter task while you are triggering another. The way I would suggest you merge the outputs is with a two input Or logic gate to avoid damaging your counters. Your signals will effectively be added together by this logic gate. I do not see any way to merge the outputs internal to the DAQ device.
Please let me know if I can be of additional assistance.
Laura

Single Pulse Width with External Clock

I am trying to setup a 6602 counter for a single (non-buffered) pulse width measurement with an external clock. Under normal testing, the unit under test will provide the pulses, I need to measure the number of pulses during different time periods (1, 60, and 300 seconds). I want to do a pulse width measurement and I'll supply the gate signal pulse to the counter for the specific time needed.
Under normal operation, the unit under test is wired into the counter's source and the pulse is wired into the gate. For testing purposes I am using a BNC-2121. I have the counter's source wired to the Adjustable Square Wave Output and the gate wired to the Trigger output.
Here is my C++ code. I am getting a timeout error on the read and I don't know why. Any help would be appreciated.
   //Create Task
   DAQmxCreateTask( "task1", taskHandle );
   //Create Pulse Width Channel
   DAQmxCreateCIPulseWidthChan( taskHandle,             // TaskHandle
                                                   szCtrName.c_str(),     // Counter Name
                                                   "",                             // Channel Name
                                                  dMin,                          // Min Value
                                                  dMax,                         // Max Value
                                                  DAQmx_Val_Ticks,     // Units
                                                  DAQmx_Val_Rising,    // Gate Edge
                                                  "" );                            // Scale Name
   //Set the Pulse Width Terminal to the gate signal
   DAQmxSetCIPulseWidthTerm( taskHandle,     // TaskHandle
                                                 "",                       // Channel
                                                 "/CTR2/PFI38" ); // Terminal
   //Set the Timebase Src to the counter's source
   DAQmxSetCICtrTimebaseSrc( taskHandle,         // TaskHandle
                                                "",                       // Channel
                                                "/CTR2/PFI39" );   // Terminal
   //Start Task
   DAQmxStartTask( taskHandle );
//***Send pulse to gate counter***
   //Read Counter
   DAQmxReadCounterU32( taskHandle,                      // Task Handle
                                          DAQmx_Val_Auto,           // Num Samps to Read
                                          10,                          // Timeout
                                          ulBuffer,                           // Read Buffer
                                          1000,                               // Buffer Size
                                          &lSampsRead,                 // Num Samps Read
                                          NULL );                            // Reserved

I've setup a pulse width task in NI-MAX using the onboard clock and everything worked fine, so I know the hardware is working.
My unit under test is providing the pulses (from gyros) I need to measure. The pulses indicate the position of the unit so there are X, Y and Z axis gyros. I need to measure these pulses for specific periods of time (1, 60, and 300 seconds). For example during the 1 second measurement, the X and Y gyros should measure zero pulses and the Z axis should measure 515 gyros. During a 300 second measurement the X and Y gyros should measure < 60 and the Z axis should measure 30800.
So the gyro pulses are wired to the counter input and I am using a DIO channel from NI-6508 to provide the gate pulse. The gate signal will be high for either 1, 60, or 300 seconds depending on the test. The gyro pulses are essentially the external clock to the counter. I want to count the gyro pulses during the pulse of the gate (DIO).
To simplify the setup, I connected to BNC-2121 directly to the card. I have the adjustable clock output going to the counter input of ctr0 and the trigger signal going to the gate of ctr0. Once the task has been started and before the read ( I had a breakpoint set in the code), I would press the trigger button on the BNC-2121 and hold for approx. 1 second. I then execute the Read statement, and I always get a timeout. From my experience working with NI, I'm guessing I don't have a channel property set correctly, but its not obvious to me and I can't find an example to do exactly what I'm trying to do.
The CTR2 designation in the code was the object name of the card. I have two 6602 cards in my chassis. I was using ctr0 of the second counter card, so PFI38/39 was correct.
Again, any help would be appreciated.

Generate single pulse with DAQ card

Hi
I was trying to use a VI found on the NI site "generate single
pulse "DAQ-STC" but another VI is requested in order to run;
that's "set pulse specs.vi". Someone knows where to find it?
thanks for all
bye
-Claudio
Claudio Vinegoni
URL: http://www.gapoptique.unige.ch/members/vinegoni/default.htm
GAP-Optique Phone: +41 (0)22 7026158 (lab)
University of Geneva : +41 (0)22 7026082 (office)
Fax: +41 (0)22 7810980
20, Rue de l'Ecole de Medecine Email: [email protected]
CH-1211 Geneva
SWITZERLAND
Sent via Deja.com
http://www.deja.com/

As of NI-DAQ 6.9, you could find the Set Pulse Specs.vi in LabVIEW/vi.lib/daq/zadvctr.llb.
Erin
Claudio Vinegoni wrote:
>>>Hi>I was trying to use a VI found on the NI site "generate single>pulse
"DAQ-STC" but another VI is requested in order to run;>that's "set pulse
specs.vi". Someone knows where to find it?>thanks for all>bye>
-Claudio>-->************************************************************************>Claudio
Vinegoni>>URL: http://www.gapoptique.unige.ch/members/vinegoni/default.htm>>GAP-Optique
Phone: +41 (0)22 7026158 (lab)>University of Geneva
: +41 (0)22 7026082 (office)> Fax: +41 (0)22 7810980>20,
Rue de l'Ecole de Medecine Email: [email protected]>CH-1211 Geneva>
SWITZERLAND>>****************>>>Sent
via Deja.com>http://www.deja.com/

Triggered single pulse width measurement

I am trying to measure the width of a single pulse, but would like to use the pulse itself as the trigger for a counter input pulse width read using a PXI-6608. I would like to do this since the pulse can come at any time (much longer than any practical timeout) and I would like to avoid having to place a DAQmx read in a while loop waiting for the pulse to appear. Also, while the pulse is high, I would like to produce front panel feedback (light a boolean indicator). I seem to be able to achieve that by using a digital input line, but again requires a DAQmx read in a while loop. I haven't had much experience with triggers and my attempts so far appear to seem like triggers are not compatible with counter input pulse width measurement. Is it possible to set up a trigger for a pulse width measurement?

Hello kayotik,
I think the best thing to do here is to use separate while loops. You can put most of your code in a main while loop, and then put your DAQmx read in a separate while loop. Both loops can run in parallel (just don't wire any outputs of one while loop to the other while loop, because then one will become dependant on the other). In order to pass data between the two loops, you will need to use a local variable. The DAQmx read can write to a local variable, and the main loop can read from that local variable.
You will also need to stop both loops with a single stop button. This article shows how (and also demonstrates the use of local variables to pass data between independent while loops):
http://digital.ni.com/public.nsf/allkb/267704CDE91156D186256F6D00711AAE
Colden

Single pulse width measurement

Hello,
I am trying to measure the time of a single pulse using ctr0 on a PXIe-6361.
The input signal seen in attachment Capture7.jpg, is going to PFI 9, the gate of ctr0.
The problem is that the counter see' s the rising edge and stops. The pulse width is not given as can be seen in the output (Capture8.jpg).
I get the same results using Meas_Pulse_Width.vi example.
Is something wrong with my PXIe-6361?
Solved!
Go to Solution.
Attachments:
Capture7.JPG ‏107 KB
Capture8.JPG ‏145 KB
Striker velocity blk_dia.JPG ‏35 KB

Hi,
I did pretty much the same and ran the example as well and they do work. You can try to explicitly specify the PFI line using a DAQmx Channel Property Node with a Counter Input Pulse Time Terminal property to verify if the problem is only with PFI 9 (if you use the property, you can use any PFI line even if is not the default gate for the specified counter), and even try with the other counters.
The VI is on the 2014 version, so I included a screenshot in case you have a previous one. If you need the VI in a specific version let me know and I'll downconvert it for you.
Camilo V.
Applications Engineer
National Instruments
www.ni.com/support
Attachments:
Counter - Read Pulse Time (On Demand).vi ‏39 KB
Screenshot.jpg ‏208 KB

Using quadrature encoders with PXI-6025

Hi!,
We are using an encoder for position data. The encoder gives A and B pulses which are phase shifted by 90 deg.
Grating Pitch = 40 microns
We make the connection to our PXI-6025 as such:
Channel A pulse goes to PFI 8 (GPCTR_Source)
Channel B pulse goes to DIO6 (GP_Up_Down)
Ground goes to DGND
We are able to increment/decrement the counter on our 6025 for every 40 micron movement
However, we are unable to quad the input and increment/decrement for every 10 microns. How do we achieve this?
We have an electronic circuit which converts the 40 micron A and B pulse from the encoder into 4 pulses spaced at 10 microns. But, using this single pulse mode does not allow for up/down counting.
We are using LV-7.1
, NI-DAQ 7.2 and Win2000 prof.
Looking forward to some quick help.
Thanks,
Gurdas
Gurdas Singh
PhD. Candidate | Civil Engineering | NCSU.edu

There's one tedious way that might work if you only need to post-process the data. However there are several possible problems.
The idea is to perform buffered semi-period measurements with both the counters on the 6025. Once you've collected all the needed semi-period data, perform a cumulative sum of each array so you end up with timestamps for all the transitions. Then you'll need to go through them to distinguish (+) from (-) direction quadrature transitions and generate a cumulative position array.
I don't think there's another way -- only semiperiod measurements will react to both edges of an incoming pulse train. However, it *is* possible in principle to get your 4x factor in resolution. Now for the problem list:
1. Your 6025E only has 1 DMA channel. One of the counters will have to be configured to use interrupts, which in turn will limit the maximum encoder rate you can track. I wouldn't count on tracking better than single digits of kHz, and you may not even be able to achieve that much.
2. The last time I did semiperiods on an E-series board, there was no way to specify which edge would mark the first recognized transition. If the input was low when you started, the first transition recorded would be a rising edge; if high, then a falling edge.
Knowledge of the initial state of the inputs is critical for your software quadrature decoding. I think the solution I used was to parallel wire the A&B channels to a couple DIO pins which I inspected before any encoder motion started. If your encoder jitters or vibrates about its nominal position however, you're probably hosed.
Are you sure you can't use the LS7084 to replace your other external circuit? The alternatives are either going to be trouble-prone gimmicks like I described above or the purchase of new DAQ equipment.
If you have budget for new DAQ equipment from NI, I'd suggest you look into one of the following:
1. Low-cost M series multi-function board
These have 2 32-bit counters onboard that are capable of quadrature decode. Each counter gets its own DMA channel for buffered acquisition. Plus you get a bunch of analog in, timed digital i/o, and can get analog outs. The boards are $475 with 2 analog outputs, $375 with none.
2. dedicated counter/timer board
The 6601 is cheaper at $295, but is limited to 1 DMA channel and has a slower onboard timing clock. The 6602 costs about double that but gives you somewhat more than double capability.
-Kevin P.

How to get a single pulse Using Burst MOde?

Harlow Peeps! Just want to know how to get a SINGLE pulse generated by the AGILENT 33220A function generator? the results i get it's in the burst MODE and everything is running smoothly and fine! it's just that i want to get a single pulse froM it only and not repeated triggeriong of the pulse...
thanks! ^^
cheers!

hi,
find attached an example, how to set hp33250a ( ag33xxx ) into burst mode.
hope this helps........... - play with it - and change it to your needs.
regards
Werner
Attachments:
hp33250a _burst.zip ‏165 KB

Please How can I capture and integrate a single pulse of a DC signal from an external circuit

Hello everyone
I am trying to integrate a signal from an external circuit I have built. I want to capture just a single pulse from the signal and integrate it. Please can anyone assist me with how I can perform this?

The 6008 has no hardware analog trigger, so to capture a single pulse, you will need to trigger in software. It does have a digital trigger, so if you have a digital way to signal the start of your pulse, it would make your life easier. You will need to ensure you take enough data to get an entire pulse. At that point, use one of the trigger VIs to find the start (and possibly end) of your signal. Take a subset of your data and integrate it (LabVIEW does support integration).
If you have trouble finding anything, let us know. Find the trigger and integration VIs using the search feature of the palettes.
This account is no longer active. Contact ShadesOfGray for current posts and information.

CTR works with PXI 8196,PXIe 8102, fails with PXIe 8100 - why?

My client has reported a problem.
For years he has used a PXI 8196 RT Controller with PXI 6602 Counter card and my software has given good results. They have 20+ of these systems and they have worked well.
Now they are moving to PXIe 810x controllers, for cost reasons.
WIth a PXIe 8102, the same code also works perfectly, measuring total counts over a period, as well as instantaneous frequency.
With a PXIe 8100 - the exact same code reports DIFFERENT answers. The reported frequency is always 1% HIGHER than actual (For example, a known 4500 Hz input is reported as 4500 Hz on 8102, but as 4545 Hz on 8100.
This happens on any channel, and swapping just the controller will make the problem come and go.
Here is the CONFIGURE code, where the channels are set up (again, this has worked for years).
Here is the SAMPLE code:
Basically the CONFIG code configures the thing to count edges. I do this because they need an accurate count over a 20-minute period, in addition to instantaneous frequency readings.
The AVG TIME is a user-settable number defining how long a period to average, when showing the "instantaneous" frequency.
So, I create a buffer for N samples, corresponding to that period.
At SAMPLE time, I read the counter. I replace the oldest value in the buffer with the newest, then subtract the newest - oldest to get the total counts in the sample period.
The PULSES PER COUNT item is a scaler, to account for a 60-tooth wheel, or something.
So, this same code has worked perfectly for years, until I plug an 8100 code in. Then the result changes by 1 %, and EXACTLY 1%?
The CPU burden on the bad controller is 31%.
Any ideas?
Steve Bird
Culverson Software - Elegant software that is a pleasure to use.
Culverson.com
Blog for (mostly LabVIEW) programmers: Tips And Tricks

Well, the controllers are not in my own hands. I have an 8196 controller and on that, the CPU time is between 2 and 4%.
But the 8100 and 8102 controllers are in my client's hands.
I haven't gotten any hard timing numbers other than I saw the 31% figure reported on the video monitor.
It's hard to believe that it would be EXACTLY 1% if it was CPU overburden.
My software includes a calibration facility; here is a run from the good 8102:
Here is a run from the 8100:
This was with a reference digital freq generator. You can see the one case where everything is within 0.1 Hz.
the other case has everything EXACTLY 1% higher. My only explanation is that the scan engine is running 1% slower.
Steve Bird
Culverson Software - Elegant software that is a pleasure to use.
Culverson.com
Blog for (mostly LabVIEW) programmers: Tips And Tricks

Measure a single pulse width using usb 5133

hi im trying to measure the width of a single pulseoutpout from NI SCOPE express
however pulse measurements.vi seems to expect more than a single pulse.
any ideas?
ta

Hi Slugger,
Can you first try this with the SCOPE Soft Front Panel (SFP) located in Start >> Programs >> National Instruments >> NI-SCOPE >> NI-SCOPE Soft Front Panel.
This should give you the screen below:
Please set the items as seen in the red boxes. Make sure your trigger channel is correct Mode is set to SGL and press the measure button.
This will give you a Scope measurement screen. Please press the Add button. Select the correct Channel and then in the measurement type choose "Period".
On the main SFP window press the run button. Does the measurement give you the reading you expect?
I do not have a Scope card to test this yet, so I have been using a simulated device.
Regards
JamesC
NIUK and Ireland
It only takes a second to rate an answer

Generate a single pulse - long width ( 160sec)

Hello,
I have a DAQ Pad6052E. I want to generate a single pulse with one of the 2 counter/timer. It works for pulse width (high state) below ~160secondes. For my application I need to generate a much longer pulse width. I want to have a pulse width >200 secondes.
If somebody can give me some advices, that would be very appreciated.
Thanks,

In addition to JB's ideas, here's another one if your other counter isn't being used.
Use the other counter to generate your own custom clock. Let's suppose it's at 1000 Hz. Then setup the counter you really care about to use the 1000 Hz clock signal as its timebase. This will extend your duration capability by a factor of 100.
Your duration limit is based on the ratio of count register size to timebase frequency. Your board's counters max out at 2^24. Your max duration is approximately (2^24 / timebase freq). The lowest internal timebase is 100 kHz which is why you're limited to about 167 seconds. With your custom 1 kHz clock, you'll get 100x that much.
-Kevin P.

HP/Agilent 33120A Single Pulse Using Burst

Hello,
I am trying to trigger an on demand pulse from an HP 33120A function generator.
The pulse has to be a single, 0-5V ramp with adjustable frequency/period. I was able to get as much from the FG by using Burst and manually triggering off the front panel. Now I would like to get the same functionality from a LabVIEW VI.
While there is a driver for the device, the burst function is, unfortunately, not applicable to the model I am using. I found a similar issue on the forums and followed the SCPI code provided in the answer with some of my own midification (http://forums.ni.com/t5/LabVIEW/33120A-Pulse-Mode/td-p/1088106).
Unfortunately, my VI is not producing the same waveform as the manual triggering off the front panel. It hovers at the offset value and gives me a few square waves down to zero when I run the VI. The square waves are oddly spaced and I usually see 4-5 even though I specified 1 cycle in the VI. Reading through the 33120A, I get the impression that the issue is my not turning off the previous waveform but, if that's the case, I can't figure out how I would do that.
I am starting to move away from only using drivers and into modifying SCPI code but I am still quite new to this. Would really appreciate some advice on what the problem could be. I modified my original VI twice; once to configure only the burst with the FG wave parameters set manually and once to just set up the waveform with no burst. The former did not give me much better results and the latter works fine so I'm back to thinking the issue is in the transition.
I am attaching the initial VI (b) with the two modifications just in case (c, d).
Hope to hear from you,
Yusif Nurizade
Edit: Burst string should say TRIG: SOUR BUS instead of EXT although neither works.
Solved!
Go to Solution.
Attachments:
Init_Burst_3_19b_2014.vi ‏17 KB
Init_Burst_3_19c_2014_Local_Ramp_Rmt_Burst.vi ‏16 KB
Init_Burst_3_19d_2014_Set_Wave_Form.vi ‏16 KB

Sorry for the later reply fellas; I've been in contact with Agilent trying to figure out a fix.
To address some suggestions;
Albert, I've been in touch with Agilent. They've reproduced my SCPI commands on their end with their software (VEE) and got the desired output. I thought that maybe the issue was with the commands I was sending via LabVIEW so I downloaded a trial of VEE and sent the same commands that worked for Agilent. With VEE I have the same problem; some of the commands, relating to frequency, shape and amplitude are processed correctly, while the burst commands are not.
I suggested the firmware issue to them and they agree it might be what's causing the problem. Unfortunately, the device is no longer supported and it would be difficult, if at all possible, to get the update especially considering this is a time sensitive project.
Karl, I've run NI I/O Trace on both the .vi and VEE. The commands seem to be going over without issue. I am led to believe that the issue is with the instrument since Agilent was able to get the desired result using my exact commands and I can't reproduce the same using their software.
I must confess I am a bit confused as to how this could be a firmware issue if some of the commands are going through and the whole thing works if I program manually off the front panel.
Please advise,
Yusif Nurizade

Timebase synchronization issue with PXI 6713

As indicated in another post, I need to use a common timebase to all cards within my PXI chassis to synchronize my acquisition/generation DAQmx tasks.
I performed that successfully by setting timebases of all boards from the 20MHz timebase of a E-series DAQ board.
I have another system setup where I do not have E-series DAQ boards but only M-series. In this case, I tried to synchronize all the cards with the 10MhzRefClock of a PXI 6254 board. It seemed to work correctly, until I looked at the analog output signal of one PXI 6713 board.
This device has 8 analog outputs, I performed as for DAQ boards : I set its timebase to a 10Mhz clock. When I have at least two outputs with hardware timing I observe on scope really weird signal : nothing is visible when all outputs are left to zero volt, but when another voltage is set, the output toggles at very high frequency between 0V and the setting voltage. When two outputs are set to values different from zero, the output also toggles but between these two settings...
I thought it was a board failure, but I checked with another PXI 6713 and the behavior is the same.
When synchronizing with a 20MHz timebase, everything is fine, but 10MHz clearly shows this issue. I checked the 6713 documentation, and it seems possible to use a timebase different than 20MHz.
I attached a VI that illustrates the problem : I create a DAQmx task containing 2 AOs, where 10MHz timebase is taken from a M-series DAQ board. A hardware timed single point timing is configured and outputs are updated in a while loop. If you connect a scope to the first analog output, you will see the phenomenon.
Everyting is fine when you select a 20MHz clock as a timebase. 10MHz leads to this issue. I also tried to synchronize through PXI backplane clock (i.e. /6259_1/PXI_Clk10) but it leads to the same problem.
Please note that using the same 10MHz synchronization on DAQ cards (PXI 6040E, 6071E, 6254, 6259...) for AO works perfectly. I only encountered this problem with PXI 6713 board.
Message Edité par Inpriser le 08-18-2006 02:54 AM
Attachments:
Synchro 10 MHz PXI AO.vi ‏34 KB

Inpriser,
You wanted to use the PXI 10MHz clock to synchronize to 6713s using the PXI capabilities. I’m afraid that since the AO series doesn't have a PLL, you won't be able to use the PXI 10 clock.
I made a few search and found this:
“Neither the 6713 nor any of the AO series support PLL synchronization. However, the M-Series does, though in that case you are limited to a smaller number of analog outputs. Regardless, the best option is using an Arb or other card that can use the Star Trigger, or an m-series device with PLL synchronization capabilities.”
For more info’s about how to deal with PXI and PLL, please check this forum:
http://forums.ni.com/ni/board/message?board.id=170&message.id=11986&requireLogin=False
I’m sorry to disappoint you, hoping you’ll manage to deal with that,
Regards,
BRAUD Jean-Philippe
Field Sales Engineer - Nord et Centre France
LabVIEW Certified Developper

Single pulse to radiate with PXI

Similar Messages

Maybe you are looking for