DAQ external triggered at 5kHz

Hello expert,
I got totally confused as I tried to do some externally triggered DAQ
with my DAQPad-MIO-16XE-50 board.
My problems are the different kinds of counters and timers and functions
to control them.
I added a piece of code, which I think should do the job...
numChans=2;
chans[0]=1;
gains[0]=1;
chans[1]=3;
gains[1]=10;
scanRateDivS[0]=1;
scanRateDivS[1]=127;
DAQ_Config (DEVICE, 0, 2)
^^^^^^^^^^^^^^^^
as far as I understand is the scan interval now externally controlled...
(signals on PFI_7)
Select_Signal(DEVICE, ND_IN_SCAN_CLOCK_TIMEBASE, ND_PFI_7,
ND_HIGH_TO_LOW)
^^^^^^^^^^^^^^^^^^
is this necessary? the manual says the timer generates an IN_START_SCAN
after the specified occurences of signal transitions... whe
re do I
specify this number of transitions???
DAQ_DB_Config (DEVICE, 1)
SCAN_Sequence_Setup(DEVICE,numChans,chans,gains,scanRateDivS,&scansSequence,&sampleSequence)
SCAN_Sequence_Retrieve(DEVICE,sampleSequence,scanSequenceVector);
SCAN_Start (DEVICE, circBuff,circBuffSize, 2, 8, 0, 1)
^^^^^^^^^^^^^^^^
which parameters are to be set here? Is the scan timer in use at all? or
should I just call Select_Signal with ND_IN_SCAN_START routed to
PFI_7???
while (sampLeftToAcq>0 && !kbhit()){
iStat = DAQ_DB_Transfer (DEVICE,halfBuff,&ptsTfr,&status);
if (iStat) break;
iStat = NI_DAQ_Mem_Copy(memhandle, halfBuff, numBytesWritten,
(long) halfBuffSize, 1);
if (iStat) break;
numBytesWritten+=halfBuffSize;
sampLeftToAcq -= halfBuffSize;
If I apply a trigger at 5kHz, the Computer locks up and presents Error
12 after removing the trigger signal.
At 2.5kHz everything works fine...
I just want to sample 127 times one channel and then once two channels
externally triggered at 5kHz.
Perhaps anyone could supply me with the essential code for this.
Many thanks, Martin

Similar Messages

Hr2000 firmware upgrade troubles with external triggering mode

Hello,
Has anyone had any problems with the latest Ocean Optics HR2000+ firmware upgrade while using external triggering mode?
I'm using the NI-provided drivers for HR2000+ which used to work without a problem before the driver update. My program synchronizes 3 spectrometers so that they continuously acquire spectra at 1 second integration time while being triggered by a pulse generator running at 20 Hz. It used to be that the specs would trigger again only once the previous integration completed, but now the spectrometers try to trigger with each trigger and don't complete the 1 second integration. My code has not changed at all between firmware upgrades, and I expected it to work exactly the same after the upgrade. I've reinstalled all programs, inf, and sys files related to the driver as well.
Do I have to wait for a new NI-Driver update that adjust to the new firmware update? Attached is the driver package I'm using.
Any clues as to what I can do about this?
Thanks,
Mike
Attachments:
Ocean Optics 2000 4000.zip ‏582 KB

Attached is a sample VI for what we're attempting to do. This used to work before the Ocean Optics firmware update.
Attachments:
specs_with_trig_post_firmware_upgrade.vi ‏57 KB

Externally Triggered 6534E Digital Output

Hi Dear Friends,
I have get a question on how to do the triggered output for the 6534E card. Right now I am using the 6534E card to output a digital gate pulse, and I want to synchronize the output of this gate pulse to an external source, which is the Sync output of a Angilent 33220A function generator(10 kHz). I want the rising edge of one trigger pulse(the sync output) to start one digital gate pulse output, and when one digital gate pulse if finished it waits for another rising edge of the trigger pulse to start another digital gate pulse.
For the more detailed description, please have a look at the attached waveform. Hope you can shed some light on the possibility of doing this.
Thanks a lot for the help.
Attachments:
6534 Triggered Digital Output.JPG ‏95 KB

Hello tiddlycorona,
From the diagram you provided, you can try the Gen Dig Pulse-Retriggerable.vi. This LabVIEW example demonstrates how to generate a digital pulse from a Counter Output Channel on a digital trigger. The Initial Delay, High Time, Low Time, and Idle State are all configurable. It also shows how to use a Digital Start trigger, so the digital pulse is not started until a trigger signal is received. Though the pulse is configured in terms of ticks, it can easily be modified to generate a pulse in terms of Frequency/Duty Cycle or Time.
Best regards,
Ali M
Applications Engineer
National Instruments
www.ni.com/support

Externally Triggering / Disabling Down a Monitor

We are using SCOM 2012 R2, and we would like to be able to trigger a "web application monitor" at 8:00 AM in the morning, and shut it down after polling the application. Would this be possible to implement ?
Our business criteria is that,
1. We cannot have this polling to occur before 8:00 AM as the data is not guaranteed to have been populated prior to 8:00 AM, so the polling result will be "negative - throwing false alarm". Since the SLA requires all the data to be
populated by 8:00 AM, and we know the polling result is correct after 8:00 AM.
2. We have not yet figured out how to schedule the polling to occur once a day at 8:00 AM, therefore, we cannot poll it using SCOM...
We were wondering if we can trigger the polling via the task scheduler, and disable it after the initial result is obtained. Is external invocation of the polling possible ?
Any assistance is appreciated.

Hi There,
I am not sure if i have understood the word Polling here correct. Correct me if i am wrong.
Polling : Take the web site offline ?
Or is it monitor the website continuously for some time ?
You can also Run scripts i.e Command or VBS Script via Scheduled rule as below to run scripts and achieve you want.
Or you can use Web application transaction monitoring for Advance Web aplication monitoring.
Gautam.75801

Exposure time with externally triggered MC1362 and PCIe-1433

Hi,
I am capturing images using a Mikrotron EoSens CL MC1362 camera and NI PCIe-1433 frame grabber. I have a question about exposure time - which I'm not sure if it is related to the frame grabber, the camera, or the combination, but hopefully someone here can help.
I'm running an external signal to the SMB connector on the frame grabber, and have the camera set to operate in "Pulse width mode", which allows the frame grabber to take control.
My question is:
How do I determine the exposure time from the parameters of the external signal? It's a square wave, and the duty cycle seems to control the exposure time.
I would guess that the exposure time, E= (D/f), where f is the signal frequency and D is the duty cycle? e.g. for f=1kHz and D=80%, the exposure time would be E=0.8ms. Is that correct?
The camera manual can be found here:
http://g4.com.tw/web/file/product/usermanual/995-EoSens%203CL-MC1361-Manual.pdf
and I have included a screenshot of the revelant portions which seem to describe how pulse width works. In particular it says "Exposure time is defined by the width of the external signal". Is that equivalent to my E=D/f idea?
Thanks in advance for any help.

Great, thank you!
"The exposure stays on while the pulse is high." - I basically just wanted to double check this, because it doesn't really say that explicitly in the manual and I find their wording confusing and didn't understand what the three traces in the diagram are.
Thanks again,
Stu

DAQCard 1200: How can I send two TTL singals on separate channels with adjustable delay shortly after (typically a few milliseconds) external triggering?

Hi, this is probably a simple question, but I have never used the digital and timing part of any DAQboard before... I wish to use an old Power Macintosh 7200 with a DAQCard 1200 for timing and synchronizing external events . The scenario is as follows; an external device (in my case; a CCD camera) sends a trigger signal (TTL, 600 ns). I want this signal to trigger the DAQCard, whereafter I want the DAQCard to send two TTL pulses (20 microsecond duration) from two separate channels (one pulse from each channel). The first pulse must be sent within a few milliseconds after the trigger is recieved. Th
en I wish to be able to control the delay from the first pulse is sent and to the second pulse. This delay should preferably be adjustable from a few microseconds and up to at least 20 milliseconds. How can I achieve that kind of operation? (I need a few tips to get started.. like for instance: should I connect the external trigger signal to the EXTTRIG pin or to the gate pin of one of the counters? Do I have to interconnect the counters in some way? Do I have to invert the OUT signals? etc..)Thanks for your help in advance.
regards,
Michal

I have not personally used the DAQCard 1200, but if it is similar to the E-series devices, you route the trigger signal to the gates of both counters.
In your code, use the Data Acquisition->Counter->Generate Delayed Pulse VI twice, once for each counter. You can then set an input on that VI to select to trigger on the gate, and set the delay and pulse width of the pulse. Since both will start from the same trigger, you can delay either pulse as long as you wish, from microsecond to seconds, making the second pulse follow the first.
Mark

1 shot sampling after external triggering of pci-6034

Hello
How do I sample the amplitude of a single pulse, that is only 2uS in duration at 1Khz, for a total of 1 second?
The 2uS pulse to be sampled, follows a trigger signal by approx 50uS.
I have measured the samples by setting the counter/timers on the daq board, which seems to work, but the time the sub-VI takes to execute seems to long, I have attached this sub-vi.
Thanks
Craig
Attachments:
Acquire 1 Point Digital Trig 2.vi ‏1 KB

Hi Craig,
The attached VI u send is not a valid VI, and can't be opened with LV 7.1. Please attached the file again, so i will examine it and try to help u...
The Bush-Man

Synchronised DAQ with 2 PCI-cards

Hi folks,
we want to use two (2) synchronised PCI-6071E DAQ cards in one PC. At
the moment we use software triggers. Is it possible two get the
software trigger for device 2 from device 1? Or do we have to use an
external trigger what is not impossible but it needs more work? Do any
DAQ vi exist for two DAQ devices?
Thanks for help, Felix
Felix Tiefenbacher
Swiss Federal Institute for Snow- and Avalanche Research
Avalanche Dynamics
Fluelastrasse 11
CH-7260 Davos Dorf
Tel: +41 (0)81/417 02 53
Fax: +41 (0)81/417 01 10

Software triggering in this case might be possible, but the better solution is to start things with a hardware trigger. Any computer running a commercial OS will have varying amounts of latency that will make reliable software triggering problematic. What's more, the faster the event is that you are trying to capture, the worse the problem gets--and sliding snow is very fast.
I understand that external triggering is more work, but you get much better results. Also the only tricky part will be generating the trigger. The code for a hardware triggered acquisition isn't any more complicated than software triggered code.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Receiving some sort of indicator that the device is triggered

Is there any way to receive data from the instrument using LabView to indicate that the instrument has been triggered? I'm using an SR400 photon counter from Stanford Research. I would like my program in LabView to start when the device is externally triggered, but I can't seem to figure out how. Thanks for any help!
- Jon

The answer to this depends on a couple of things:
1. How are you communicating with the device? GPIB? Serial? USB? TCP/IP?
2. Is the instrument designed to automatically send some indication across the bus when it's been triggered? (If you're not sure, you should check the documentation for the device)
If you are using a standard protocol, and the device has some means of sending out a notification that it has been triggered, then you can set up your system in LabVIEW to wait on that notification, whether it be waiting for bytes at the serial port (if serial) or waiting for a service request from your device (GPIB), for example.
Logan S.

Parallel triggering of DHCP and AutoIp

In my TcpIp stack, I want to trigger AutoIp/LinkLocal and DHCP addresss assignemtn parellelly. But the response from the DHCP server is too slow. By the time I get a reponse from DHCP server the AutoIp address assignment is over and assigned to my interface (NIC). After this the DHCP frames (DISCOVER/REQUEST frames) have AutoIp address as source IPv4 address in Ipv4 header.
Is this correct?

I'm confused :/
No one has never experiment external triggering of SAP billing jobs in parallel mode?

Triggering a GigE camera

Newbie question for you all. Hope this makes sense:
At the moment, we are using a Dalsa area scan camera and a NI PCI-1424 frame-grabber with a parallel digital interface. We use LabVIEW and IMAQ software. Our software creates an IMAQ session that sits and waits for a single external trigger on the PCI-1424 board. When it receives the trigger, we acquire a series of frames at a given frame rate.
Now we want to upgrade the whole system and are considering a GigE camera from Basler (Pioneer piA640-210gm). If decide to do this, how would we configure the triggering?
I noticed that NI's GigE board (PCIe-8231) does not have any trigger inputs. So I guess the only way to trigger the acquisition is to use the camera's trigger input? But that doesn't even seem possible. The user manual on the camera indicates that external triggering is used when you have a pulse train that triggers every frame. We want the camera to wait for just one rising-edge which then triggers a pre-determined acquisition that is setup in the software. Any ideas how to do that with GigE?
Also, we use NI-IMAQ software right now. If we upgrade to GigE, then we are going to have to totally re-write our software to use NI-IMAQdx, right?
- John

Hi John,
With Firewire and GigE cameras the triggering is generally* done on the camera rather than the interface into the PC. The reasoning is that the interfaces into the PC do not have low-latency, deterministic methods to trigger the camera except via a separate external trigger wire linking the PC and camera. (*With Firewire since you are bound to the distance limits of the bus, it is generally easy to make this connection than GigE). NI does sell products like the 8255R (a firewire interface combined with reprogrammable I/O suitable for use with triggering cameras via an external cable, but there is no device that combines this functionality with GigE ports (but no reason why you can't combine with a separate GigE network card). However, as I'll desribe below, GigE Vision has its own tricks that reduce/eliminate the need for this...
With the triggering moved to the camera, it is up to the camera vendor to decide the complexity the triggering methods they implement. On GigE Vision cameras, because they use GenICam XML files to allow the cameras to self-describe their features, any capabilities the camera manufacturer can dream up will be exposed through the driver. We are starting to see GigE cameras on the market with very complex triggering capabilities (including built-in pulse-generation capabilities, complex input and output interactions, etc) that can rival features on many framegrabbers. You can configure all of these features within MAX or your application just like you can control any other feature of the camera. Note that while there is flexibility to implement any feature desired, there is a "Standard Features Naming Convention" that, among other things, includes complex triggering definitions. This list aims to ensure that cameras that implement the same features (such as common triggering modes) use the same names and behavior for their features.
As to whether the Basler Pioneer will support what you want, I am unsure. I checked the triggering capability here: http://www.baslerweb.com/downloads/17785/pioneer_manual.pdf. According to their docs, they support an "AcquisitionStart" trigger, meaning you should be able to trigger the start of a single-frame, multi-frame, or continuous acquisition when that trigger comes in (and the source can be varied, including external I/O pins). However, I tried this on a Basler Scout that we have and only a single frame was generated in this mode when triggered via a software trigger. Its possible I have an earlier firmware that is behaving incorrectly, but in theory the Basler camera should be able to do what you want if they named it correctly. I would confirm the expected behavior with Basler to be certain. As I mentioned, there should be plenty of other cameras on the market that do support this triggering mode if the Basler does not.
With regards to re-writing your software for IMAQdx, its true that you would have to make the translation from IMAQ code. However, the API's are very similar for most things and code porting shouldn't be too bad.
Please let me know if you have any more questions regarding this,
Eric G

How to externally time data acquisition rate

I have Lab-PC-1200 card and Labview 5.1. I will like to read the signals from a Hamamatsu linear detector array that has 1024 pixels on it. The trigger (or sample) rate of the detector can be modified over a range covering 1 MHz to 15.625 kHz.
I use the 'Acquire N Scans ExtScanClk D-Trig.vi' (written by a NI staff member) downloaded from the web. If I set the trigger rate of the detector to 15.625 kHz (the slowest possible), the program runs without any problem. However, if I use a faster trigger rate (say, 31.25 kHz) no data is collected. According to the specs, the maximum data acquisition rate of the Lab-PC-1200 card is supposed to be 100 kS/s. How do I solve this problem?

I've answered my own question. The solution lies in disabling the internal channel clock and connecting the triggering clock to the EXTCONV* port of Lab-PC-1200 card to fire the channel clock. The scan clock should be timed with an even faster external clock from the detector. Ultimately, it is the channel clock that is important, not the scan clock. The lab-PC card uses the channel clock in conjunction with the number of channels to set up internal gating pulses which of course become the limiting factor. The external triggering clock connected to the channel clock cannot be faster than the speed of the card (in my case, it's 100 kHz).

Scanning with external DMM with Agilent 34970A using Labview

Hi,
I am a relatively inexperienced user of Labview. I have written a VI to
scan several channels on a 34970A using the 34901A multiplexer module
to take voltage readings. I want to use a more accurate DMM than the
internal one however so I have hooked up a Fluke 8840A to the agilent
and I want the scanner to simply switch between the channels while the
fluke actually takes the voltage measurements. How do I modify my
existing VI so that it uses an external DMM? One of the driver VI's is
'configure external instrument' which i assume is the obvious option
but i'm not sure where to insert this to modify the VI.
Thanks
Tom

What you do kind of depends on the capabilities of the external DMM and how fancy you want to get. If you at the section called 'Scanning With an External Instrument', you'll see how the connections can be made for an automatic scan. The 34970 will issue a trigger to the external instrument and when the measurement is complete, the instrument will send a signal back to the 34970 to close the next relay in the scan list. If you can do this, then the Conf Exteranl Instrument would replace the Conf Scan List and Conf Scan functions in the Advanced Scan Example. I'm not sure about the Conf Trigger but I suspect you would need to set slightly different parameters for that. The Read function would have to be replaced with a read of your external instrument. Some additional functionality may have to be added to take a reading after each relay closure if the DMM cannot save a series of measurements.
I had to once use an external instrument and didn't do any of this. The external instrument did not have external triggering or a an output that could be used to advance the scan so I just used the HP34970 Switch function to close a relay exclusively and a dmm read inside a for loop. I created an array of channels and the for loop auto-indexed them. This was simpler to program but the scan took a bit longer than what is described in the manual.
Message Edited by Dennis Knutson on 08-31-2006 07:47 AM
Attachments:
34970 with External DMM.JPG ‏24 KB

Synchronisation of frame grabber and DAQ board

I want to aquire images and analog voltage signals at the same time, and synchronised, using a NI PCI-1428 Camera Link frame grabber and a NI PCI-6014 DAQ board. Can this be done using the RTSI trigger functions? I know that the frame grabber supports this, but what about the DAQ board?
How about synchronising a NI-board with a non-NI frame grabber?
Thanks a lot!
Peter

Hi, Peter,
No, the PCI-6014 DAQ board does not support RTSI. However, most of the low-cost E-series NI data acquisition cards do support RTSI, such as the PCI-6024E or PCI-6036E, so you might consider using one of those boards instead.
If you decide to go that route, there is a useful tutorial that describes the signals that can be routed over RTSI for NI DAQ and IMAQ boards:
Developer Zone Tutorial: Synchronizing Motion, Vision, and Data Acquisition
as well as several example programs:
Developer Zone Example: Integra
ting IMAQ and DAQ with Single Display
Developer Zone Example: Low-level Triggered Ring (with DAQ-supplied triggers)
As for a non-NI frame grabber, that would really depend on what support the frame grabber has for timing and synchronization. You could route a trigger signal or scan clock out over the PFI pins on the PCI-6014, but you would need to see if the frame grabber is designed to receive these types of signals.
I hope that helps!
Best regards,
Dawna P.
Applications Engineer
National Instruments

Essbase restructuring triggers HFR

Hi All,
I have a requirement in which FR batch should be triggered when ever the Essbase Cube is Refreshed.
kindly, help me out
Thanks in advance
Edited by: 1005961 on May 14, 2013 9:46 PM

Check these discussions.
Re: External Event trigger FR
http://businessintelligence.ittoolbox.com/groups/technical-functional/brio-l/external-triggered-event-requirement-hyperion-v931-2752751
http://www.network54.com/Forum/58296/thread/1197315985/Trigger+Workspace+Job-
Regards
Celvin
http://www.orahyplabs.com

DAQ external triggered at 5kHz

Similar Messages

Maybe you are looking for