LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

one device aquires one triggers

Here is my problem
 
I have a NI-9234 using a NI USB-9162 sleeve. The NI-9234 does not support hardware triggering, and the software triggering does not meet my needs for timing. Is there a way to use my DAQCard 6062E to trigger in someway either the vi or the acquisition
 
 
- there is always an easy way, but it is always the hardest to find
0 Kudos
Message 1 of 8
(3,034 Views)

PS

I need to aquire with th NI 9234 because of noise issues with the DAQCard

- there is always an easy way, but it is always the hardest to find
0 Kudos
Message 2 of 8
(3,030 Views)

Hello,

You mentioned that the software triggering does not meet your needs for triggering ... What are your needs?  Please provide a little more information about the application and how triggering is involved. 

You could very well have a VI look for a trigger on the 6062E and then use this status to route (in software) to the 9234 task.  However, this is like using an software trigger.  Would this work for you?

 

Samantha
National Instruments
Applications Engineer
0 Kudos
Message 3 of 8
(3,003 Views)

Hi Sam

The problem I have with the software trigger is that I need my program to wait for the trigger pulse then to acquire a certain amount of samples a a certain rate to give me the record length of data that I need. The software trigger does not work for me because it first acquires the samples then analysis them for the trigger. If the trigger happens late in the samples acquired, the record length is too short. I tried to loop the program around to acquire more after the trigger has occurred but there is a gap in the samples acquired.

Thanks

- there is always an easy way, but it is always the hardest to find
0 Kudos
Message 4 of 8
(2,988 Views)

Hi

This is what I have tried, is there any simplier way that reduce the time delay between trigger and acquistion. I would like to have the trigger to be time zero of the data waveforms, or as close as possible

 

Thanks

- there is always an easy way, but it is always the hardest to find
0 Kudos
Message 5 of 8
(2,978 Views)

Hello,

I am assuming that you are using the example from the Example Finder titled Cont Acq&Graph Voltage - Analog Software Trigger.vi.  Please clarify if this is the example that you are unhappy about the samples relative to the trigger.  This type of software trigger is going to be the best solution of a trigger on the 9234.  If you believe that the examples is not grabbing all the post samples that you would like, please futher example the setup with how many pre and post samples are needed.

I do understand that you have a 6062E to hardware trigger from, however routing this trigger in software is also going to have some limitations.  The code you have attached is going to have delay between when the trigger happens ... the 6062E task will have to finish the read of 100 samples and then the error status will trigger the 9234 task.  I also wanted to note that the code posted in missing a sub vi needed to run.  I look forward to hearing back from you.

Samantha
National Instruments
Applications Engineer
0 Kudos
Message 6 of 8
(2,951 Views)

Hi

Thanks for your reply. I should have posted that I have posted that I have solved my trigger issue by using seperate while loops for the continuous acq. and the software trigger and this eliminated my problem.

 

- there is always an easy way, but it is always the hardest to find
0 Kudos
Message 7 of 8
(2,941 Views)

Hi Beaton,

 

I have the same problem with you. In particular, I want to acquire signal from NI9234 after the signal passes through a threshold as a trigger. The acquire signal should include some samples before the triggering and has a fixed length of data.

 

Could you please share your solution or help me to solve my problem!

0 Kudos
Message 8 of 8
(2,525 Views)