Trigger rearm time on 5112

Hello,
I have a Niscope 5112 card with 16MB/ch memory option. I would like to sample at 100 MS/s during 5us (500 samples) with a 100 Hz repetition rate. The total amount of repetitions will be 2000, which amounts to 2000 x 500 = 1M data points. I think there should be no problem for the board to be able to handle that, I just like to confirm, making sure I am not missing anything. In particular I was wondering about the time required for the trigger to rearm.
Thanks,
Jerome.

Hi Jerome,
The rearm time for the NI 5112 High Speed Digitizer is 100us, so you are correct in saying that there will be no problem with this board handling your application. With a repetition rate of 100 Hz, you have a choice of using software rearmed single records to capture your data, or you could set up a multiple-record acquisition. The examples that ship with NI-SCOPE will help you either way.
-Josh

Similar Messages

Trigger rearm time on USB 6211

I am using a USB 6211 to generate raster waveform and digital trigger to drive the galvanormeter mirror. I just want to send one cycle of waveform for every trigger pulse. The problem is that it seems like the USB 6211 trigger rearm speed is limited to about 20 Hz, which is quite low. Is this correct?
Any solution?
Attachments:
Triggering.png ‏76 KB

I might use the wrong word to explain it. What I mean by observing the behavior of the device when it was programmed as shown in the code is that no matter how fast my triggering clock was, there seem to be a certain period of time when the device did not accept any trigger pluse. That period of time was about 50 ms or about 20 Hz clock rate. The code worked as I expected it to be at trigger frequency less than 20 Hz. As soon as the clock speed pass 20 Hz, the extra pulse was not accepted.
One thing that I did to verify the 50 ms time limit was by sending 200 Hz of clockspeed and found that the one that close to 50 ms did trig the device.
Is there any example how to setup this device to surpass that trigger speed?
If not possible with the USB 6211, which DAQ device you would reccomend to achieve more than 100 Hz trigger speed, or even better for up to 200 Hz?
Thanks for your response : )

Using LabVIEW to program a Pattern Trigger for the PCI-5112

I am trying to program a pattern trigger for the PCI-5112. Has anyone ever done this? I am trying to use the the "Fetch forever" example as a base, then use the software trigger when there is a pattern match.
Any help or advice with this would be very appreciated.
PS as an example, I want to trigger when the pre-trigger data matches the pattern, say a 8 bit word such as 1010 0000. Maybe I can try to do like my Tektonix TS5104B scope and try to program a timeout trigger.

Good morning Andronicus,
Thanks for contacting National Instruments with your issue, we'll try our best to resolve it for you as quickly and efficiently as possible.
Unfortunately, there is no easy way to do what you're trying to accomplish with simply a Scope alone. The trigger input and PFI lines have no buffer and are only capable of looking for a single edge, and the standard CH0 and CH1 inputs strictly represent signals in analog.
So your current approach may be best, of using the Fetch Forever to acquire the signal into a prebuffer and then analyzing it and sending a software trigger. So the best you can do in terms of response will be software-time, which is not ideal. There is also the very tricky matter of interpreting that analog signal as a digital signal. You'd have to know the clock rate of the incoming pattern and then also the phase in order to correctly assess the incoming pattern. No easy task, and certainly nothing that would be super reliable or recommended.
Your best bet would be to purchase one of our HSDIO cards, such as the PCI-653x that inherently does pattern triggering in the hardware domain, and then route the start trigger (i.e. when the pattern has been matched) via a RTSI cable to the Scope card which can then simply use the digital edge trigger to begin it's acquisition. This will be far more robust, easier to code and have a much quicker response time.
Best of luck with your project.
Sincerely,
Minh Tran
Applications Engineering
National Instruments

Suggestion? Running out of rearms (time) building large master Win7 image - Should I use KMS until capture?

I am building a Window 7 Ent master image containing 200+ engineering applications which will be deployed to 800+ systems. My problem is, I'm close to running out of activations and am now down to one rearm remaining. I have the option of using our
KMS server.
Question: Is it allowed that I point my non-domain member master Windows 7 image at our KMS server to activate the OS while I continue to install software up until the point I'm ready to shut down and capture my master image?
If perform the above-mentioned procedure do I leave the master image pointing at our KMS server during the capture process? Or, do I remove the settings from the registry? After the client is joined to the domain, a GPO points all clients to our KMS server
anyway.
Or does it not matter that I continue building my master build image, with one rearm left, leaving it prompt me that my Windows 7 Ent. copy "may be counterfeit".
Thanks for your time in advance!

Hi,
Yes, you can point a non-domain member master Windows 7 image at your KMS server to activate the OS, it should be done by Manually Specifying a KMS Host with a command:
http://technet.microsoft.com/en-us/library/ff793406.aspx
After the Windows 7 image is activated by the KMS, you can run this command with administrator permission to check the rearm time: Slmgr.vbs /dlv
Details about deploying KMS clients can also be found at :
http://technet.microsoft.com/en-us/library/ff793406.aspx
Regards
v-yamliu

How can I calculate the slope of an isometric torque curve with a trigger and time increments of 0-30ms, 0-50ms, 0-100ms etc....

I am analyzing isometric muscle contractions of the quadriceps and want to calculate the rate of force development (not just peak torque) for the torque-time curve. I want to set a trigger so that the slope of the torque curve is calculated when 7 newton-meters is reached. From there I'm trying to calculate the slope in time increments of 0-30ms, 0-50ms, 0-100ms, etc....My data is sampled at 2000 Hz and written in text files. Below is a copy of the VI I have developed so far. I am very new to programming with LabVIEW but can definitely see its potential! Any advice would be greatly appreciated.
Attachments:
Dissertation Isometric RFD.vi ‏14 KB

Fiddler918,
When trying to implement something like this in LabVIEW, it is often helpful to think about how you would program this function in a traditional text-based language. Try and break the problem down. You need to locate the data point in your array that is 7 Nm or greater. At this point, you will need to grab the data points that are 60 indices (for the 30ms gap, assuming your points are equally spaced 0.5 ms apart), 100 indices (for the 50 ms gap), and 200 indices (for the 100ms gap) ahead of this point in your data file, and calculate the slope using pairs of data points.
Here is a general description of a possible implementation of this code:
You can wire the appropriate column of the data array into a For Loop on the block diagram and have it auto index through the points. If you right click on the Use the Greater or Equal? function to generate a Boolean that will be true when you want to exit the For Loop. Right-click on the border of the For Loop and select Conditional Terminal. This will cause a small stop sign to appear. If you wire the Boolean to the conditional terminal, the loop will stop at the value that is greater than or equal to 7 Nm. If you wire the Loop Iteration terminal out of the For Loop to the right, this will give you the index of the value in the column that you’re interested in. Having this value, you can then use the Array functions to grab the specific data points you need, and numeric functions to perform the necessary math.
If any of this didn't make sense, the LabVIEW help files are a great resource to use.
Here is a link to some video tutorials of the LabVIEW programming environment. They may help you in the development of your code.
http://www.ni.com/academic/students/learnlabview/
Regards,
Jared R.
Precision DC Product Support Engineer
National Instruments

Trigger by time and event

Hi Gurus,
Is it possible to have a batch job or process chain to be triggered by BOTH an event AND time at the same time?
How about for a job or chain to be triggered ONLY when 2 Events have triggered?
So far, I see that only 1 event is possible per trigger.
Can a program check if a particular event has been triggered? Is this status set/saved in a table?
Thanks,
Pascal Gabin

Dear Pascal Gabin,
I hate to write the following logic.. but just thining if incase if youhave not thought of this.
1) EVENT A, linked to ABAP A
2) EVENT B, linked to ABAP B
Logic ABAP A:
   - Updates FLAG A, table COMMON.
   - Checks the Flag B is X or not..
        if it is Space.
           exit.
        else.
           clear the FLAGS.
         Trger the event C, by BP:EVENT_RAISE FM.
Logic ABAP B:
   - Updates FLAG B, table COMMON.
   - Checks the Flag A is X or not..
        if it is Space.
           exit.
        else.
           clear the FLAGS.
         Trger the event C, by BP_EVENT_RAISE FM.
Event C is maaped to your Process chian or JOB..
Not a good one.. but i think it can satify the functionality of what your loking for..
table Common will have 2 fields FLAG_A and FLAG_B.
jst trying to read FLAGS instead of events..
You can also check for event tables in the work flow form.. not sure you get it.. but should give you many table names there..
regards,
Hari

Send analog trigger every time data is acquired and saved

I am currently writing a program that acquires and calibrates data from 32 channels of force plates. Once the data is acquired and calibrated it is saved to a file. I need to send a pulse to another computer running labview once every time data is acquired and saved. I have written several versions of this code that send a continuous pulse train while data is being saved. I need to modify the code so that it does not send a continuous pulse, but an individual pulse that is a set frequency every time I acquire data. I believe that I need to use a software trigger to control the pulse, but I can't seem to find a way to have the hardware send a pulse only when I want it to.
The program uses a boolean as a start trigger for the acquisition process. In this manner when the data begins saving(i.e. the boolean is switched) it would send one analog pulse per iteration of the save loop. Unfortunantly I only seem to be able to either send a continuous pulse that I start before the acquisition begins or am not able send any pulse. During the time this pulse is being sent I am also constantly acquiring data from the card. I was wondering if there is any way that I can have the pulse start and initialize before the loop begins and then have it send one analog pulse of a set frequency every time the loop is iterated. I have tried both DAQmx and DAQ traditional solutions but have had no success.
Hardware: PCI-6071-E and BNC-2110 boxes, so I have a large selection of ports and my card seems to be compatible with all the latest software capabilities.
Thanks so much for any help!
~Matt

Actually after tinkering with it for several hours I managed to figure out a way to solve my problem. I'll explain it in case anyone else has a problem.
What the software does: The software is an acquisition loop that outputs a square wave pulse of finite frequency to another acquisition system at the beginning of each acquisition iteration while data is being saved. This is so that the data from the two systems can be synchronized later.
The program flow is this Send Single Synchronization Pulse-> Acquire Data->Calibrate Data->Save Data to file->Repeat
The pulse is triggered once data begins saving, but the device begins acquiring data on execution of the software.
To do this I set up the DAQmx Channl configuration to CO Pulse frequency. I then set the timing up to be finite iterations and the number of iterations to 1. Inside the acquisition loop I enclosed the whole acquisition process in a flat sequence. In the first sequence, if the program is saving data it turns the pulse on, if not saving the task passes through. The acquisition occurs in the middle sequence and in the final sequence if saving the task is turned off. If not saving the task passes through. This allowed me to send one pulse of a finite frequency every time the loop is run.
Thank you very much for your response though. If anyone else runs into a problem like this I can post a screenshot for future reference when I get a chance. Thanks again.

What's the trigger for Time Machine to back up a FileVault folder?

Hi,
I have been enjoying the new MacBook pro and the useful FileVault for weeks now. I read quite some discontent with FileVault, which indeed could be better, but still it provides useful and free encryption.
With regards to backup on Time Machine, the Home Folder back up supposedly only happen when you log out of a FileVault encrypted account. Meanwhile, I don't always get how it starts and the rules for the Home folder to be backedup.
I make daily changes on my Home folder and the backup only starts once every other week, maybe randomly? Only few times i see the backup progress bar at shutdown and it seems to happen only after a certain amount of additional data has been added.
Has anyone more insight in how the backup (i.e. at log out, only way to backup on TM with FileVault) is triggered? Is there a way to make it a mandatory operation at log out, when my backup drive is available? As I use a WiFi HD (through airport), is it related that backup only occur once in a while and not at each logout
thanks for any tip
Y.

With FileVault enabled Time Machine only backs up when you log out or shut down, unfortunately And when it does it copies the entire encrypted .sparseimage every time. There is no incremental backup when FileVault is enabled.
Regards,
Michael

Writing trigger event time to file

I am new to LabVIEW. I have been modifying the acq_graph_voltage_dig.vi that I found to trigger recording using a digital trigger with a set number of pretrigger and posttrigger samples being recorded. I have added VIs to open, write to, and save a tdms file with this data. I want to be able to record when the trigger actually occurred, either as a separate channel or just as an event to mark when the trigger occurred in the file. I know that I can figure this out based on the pretrigger sample number, but this is something I will likely be changing as I record. I will only have one trigger per file. Anyone have suggestions on how I could record the trigger instance?
Thanks!
Solved!
Go to Solution.

Hi shelby,
I assume that you just want the timestamp of when the trigger occurred and then you'll write this value to file. If so, you can change the read position to the reference trigger, read one sample, and the record the timestamp of that sample to the end of your file. A picture is shown below as well as an edited version of the VI you were using. I didn't add any file I/O to the example as I assume you already have this part figured out. I hope that helps!
Message Edited by lion-o on 10-21-2008 02:23 PM
Mike Lyons
National Instruments
http://www.ni.com/devzone
Attachments:
reference_trigger_read_position.jpg ‏42 KB
acq_graph_voltage_dig.vi ‏92 KB

E-mail trigger delay - Time Zone (CET) ahead of System Time (UTC)

Hi,
We have developed a Z program which triggers e-mail whenever the critical System / Interface user id gets locked in the SAP Netweaver System. However, the e-mail is generated by the program in the Time Zone which is in CET and sits in t-code SOST and is sent to our mailbox in System Time which is in UTC (GMT) which is currently 2 hours behind. Hence, there is a delay of 2 hours for generated e-mail alert to be sent to our mail box. Is there any process to avoid this delay?
In the test system manually we can reduce the wait time by 2 hours in t-code SOST and then the mail gets triggered immediately. But can this be achieved programmatically so that the time in which e-mail gets generated always displays the system time in t-code SOST. Or, is there is a configuration where the e-mail is sent to our mail box from t-code SOST in Time Zone (CET) itself and not wait till the displayed time reaches System Time (UTC).
Thank you very much for your earliest response.
Regards,
SANJEEV KUMAR

In t-code STZAC both System Time and Useru2019s Default Time Zone is same (CET).
However, when I see in the menu System->Status I find the System Time is displayed in UTC, while Time Zone is in CET.
In other clients where system time is displayed in CET, there is no problem. The e-mail spool from SOST which displays CET time is actually triggered in the System Time. In case the System Time is CET, mail is triggered immediately. In case System Time is UTC, it waits UTC time to reach the displayed CET time, which is currently of 2 hours gap.
Is it possible to change the system time of the problematic client to CET to solve this problem. Please let me know what configuration can be done for this.
Regards,
SANJEEV KUMAR

Period measurement trigger rearm

Hello
I want to measure pulse widths (8 channels on a 6602) triggered by a PFI (PFI0, f.i.). The trigger comes from my LabVIEW-application in user-definable intervals of about 1 - 5 secs.
The examples provided with LV show taking a finite number of samples without a loop. But I cannot tell in advance how many samples I'll need, and I'd like to see the results before all samples are taken.
I can set a trigger property to arm the trigger. But I could not find a solution to re-arm it so as to employ it in a while-loop.
Most applications that are discussed here deal with counter output. Which works. But not on pulse measurement input.
Thank you for your help.
Michael
Attachments:
pulseinfinte2.vi ‏47 KB
pulseinifnite2.jpg ‏45 KB

Hello nimic,
thank you for contacting National Instruments.
I think the example in the following link should help to solve your problem. "NI-DAQmx: Buffered Event Counting on all Counters of a 6602 or 6608"
http://zone.ni.com/devzone/cda/epd/p/id/4836
Please feel free to contact us again for further informations.
Best wishes, Jan Kniewasser
National Instruments Germany
Jan Kniewasser | Applications Engineer | Tel.: +49 89 7413130 | Fax: +49 89 7146035

Can I skip "Done state" in high speed digitizers?

We are trying to retrieve data from a USB-5132 device, with a sample frequency of 25MS/s. Our record length is 6000 samples and we have an external digital trigger with a frequency of at least 120 Hz and we need 120 records.
We have a labview program, but somehow it only lets us retrieve the data at a frequency around 60 Hz, probably because of the USB to computer interface. Is it possible to increase this?
Alternatively we have considered the state diagram of the unit, and observed that the "Done" state waits for the computer to intervene. Is it possible to skip the "Done" state, and store the 120 records on the onboard memory and extract all the data at the end?
Regards
Jesper & Anders
Message Edited by Vegge on 10-29-2009 07:10 AM

Hi Jesper and Anders,
The USB scopes such as the 5132/3 do not have continous acquisition or multi record acquisition. That means you have to use software timing to acquire data at 120Hz, which gives us a digitizer trigger rearm time of 8.33ms.
The rearm time is the time it takes to stop the acquisition and then start the acquisition after each trigger. This means that fr USB Scops the rearm time is software dependant and non deterministic. I cant give you the exact rearm times(System dependent) but I would say it would be in the hundred millisecond range roughly.
I'm not sure that you can implement a software workaround to achieve a rearm time of <10ms. You can try to free up as much CPU resources to Labview by closing all none needed background applications. With a fast computer you might be able to reach a faster rearm time. But the recommended solution is to choose a Hardware solution, where the digitizier supports "Multi Record Acquisition".
Our other digitizers such as the NI 5105/5114/5122/5124/5142/5152/5153/5154/5622, support multi record acquisition and have a rearm time specified in the micro second range. This is calculated (500 ns + posttrigger storage time) and the 100 ¼s holdoff time. This would be recommended because the rearm time is hardware dependent unlike the USB scope.
Rearm time for a 5622 scope: http://digital.ni.com/public.nsf/allkb/99B4AFB631CD5DAF8625761F00777FB5?OpenDocument
I hope this helps!
Thanks!
Message Edited by Morini on 10-30-2009 02:02 PM
Dennis Morini
Field Sales Engineer
National Instruments Denmark
http://www.ni.com/ask

Problems retriggering

Greetings. I am using a PXI 6289 and I need to generate a fast continous pulse traing that is synced with an external clock. I have foudn several examples which at the core all have same base. Use a counter to generate a finite number of pulses that is trigered from the external clock and then retrigger it.
http://sine.ni.com/devzone/cda/epd/p/id/2415 Here is the most basic example.
So I have a 5kHz clock and I am putting it into the SRC of counter 0 (PFI8)
I use that as my trigger for CTR 0 output. I tell it to make a 50kHz clock and make 100pulses.
It does this well except when it goes to retirgger it misses one full cycle of the external clock. So the new pulse train is not continous. I have been looking through the posts and this should work. If you do 99 pulses you can see it does not miss a full cycle but the two clocks are no longer synched if you look at the signals on a scope.
In the end I jsut need to generate a fast clock from a slower clock and it needs to be continous. I would like it to work with the 6289 but I am beginning to open my mind to getting a new card if this doesn't work.
If anyone has any suggestions I would greatly appreciate it.
~D

Hi Glish Lab,
The reason you are missing a full cycle of the external clock is likely due to the trigger rearm time on the PXI-6289. I have a few questions as well as suggestions that might help us find a better solution for you.
Do you know the accuracy of the 5kHz external clock? I ask this because this would help us determine if you might be better off using a phase-locked loop (PLL) with the PXI backplane clock. Depending on which PXI chassis you are using, the accuracy of the backplane clock might differ but is around +/- 25 PPM for the PXI 1042. If your external clock is less accurate than the backplane clock, you might be better off bringing it in as a reference clock so that it will be PLL'd to the higher accuracy backplane clock.
The only problem PLLing to the backplane clock is that they are only phase locked and not synchronized. You will have to wait a few cycles of the 5kHz external clock for the backplane clock to fully PLL. This also means to synchronize the two you will need to provide a digital pulse as a start trigger (after these few cycles) to synchronize the backplane clock. You would then be able to divide down the backplane clock by an integer to adjust the sample clock to whatever you would like. Regardless of whether the accuracy of your clock is greater or less than the backplane, you can still bring in the external sample clock as a reference clock (PLL'd to the backplane) and provide a digital pulse start trigger to gain a faster synchronized clock.
If you could provide more information about the source of the external sample clock and details of the other devices you're using in your application, it might help me find a better solution.
I hope this helps,
Paul C.
Message Edited by Paul C. on 10-25-2007 03:22 PM

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

How to use start and reference trigger on HI-Scope digitizer

HI,
I would like to ask about the start and reference trigger with PCI-5124.
I found an sample VI on the following link, however it doesn't work as I expected.
http://zone.ni.com/devzone/cda/epd/p/id/2998
The VI "start_and_reference_trigger.vi" can detect both start and reference trigger in my system and they start data acquisition.
It starts data acquisition when both start and reference triggers are input.
However what I would like to do is:
1. Sampling rate at 200MHz with record length 1500 with one channel.
2. Receive the start trigger (i.e. 50Hz)
3. Receive the reference trigger (i.e. 50kHz)
4. For every reference trigger, I would like to acquire the data, i.e. acquiring 1500 data for each 100 reference trigger (not with the combination with the start trigger)
Start trigger: _|^|_________________________________________
Ref   trigger:______|__|__|__|__|__|__|__|__|__|__|__|__|__|__|____
                                  ^    ^    ^    ^   ^   ^   ^   ^    ^   ^   ^   ^    ^   ^
                                 trigger timings that I would like to acquire
With the sample VI "start_and...", I found that it acquires when both start and reference trigger comes and the data acquisition is only after the one reference trigger.
I hope my explanation is understandable and I can have a solution soon.
解決済！
解決策の投稿を見る。

Hi Tom 1225,
Thanks for posting on Discussion Forum. Based on your statement, I guess, what you want PCI-5124 to do is what general bench-top type oscilloscopes do. To realize that functionality, at the end of each sampling of a record length, PCI-5124 has to rearm its trigger for its next sampling. The amount of "rearm time" is listed in "trigger" section on 5124 manual, said that the rearm time is 10[us] when TDC is ON and 2[us] when TDC is OFF. So, we have to keep in mind that, if one waveform of measured signal is shorter than 2[us] (TDC OFF), more than one waveform may fail to kick the trigger, because 5124 still rearming its trigger.
I made two samples and attached them on this post.
In "Sample SW Timing Trigger.vi", trigger rearm occurs at software timing, when the time NI-Scope Start function is called.  In "Sample HW Timing Trigger.vi", trigger rearm occurs at hardware timing. As seen on the block diagram, for a hardware timing trigger rearm, the number in "number of records" of horizontal setting function should be equal to the times of the trigger-based measurements. If you have any question on my sample VIs, feel free to ask. If my post resolves your problem, please click on the green "解決策に決定" icon on my post.
Osamu Fujioka
Applications Enginner
National Instruments Japan
添付:
Sample SW Timing Trigger Rearm.vi ‏28 KB
Sample HW Timing Trigger Rearm.vi ‏31 KB

Trigger rearm time on 5112

Similar Messages

Maybe you are looking for