Software analog trigger failure

[proserpio]

I'm using the 'Software analog Trigger Example' on a Acer TM280 Notebook with Win 2k, a DaqCard AI-16XE-50 and NI-Daq 6.9.3.
The only change made to the CWAI1 property in the example is increase the number of channel acquired from Channel 1 to Channel 0,1,2,3 and increase Nscans from 1000 to 10000.
The first occurence of trigger is detected, after 1 minute generating another trigger signal the software often doesn't detect it.
The same example with 2 or 3 channel configuration works fine.

[Spencer S.]

Greetings,

You mentioned that the program often does not detect the second trigger. How frequent is often? If it does detect the second trigger, will it continue to detect subsequent triggers? Is the first trigger always detected?

Spencer S.

[proserpio]

The second trigger isn't detected more than 70% of occurence.
After trigger failure I need to press Start Button again to detect next trigger occurence.
The first trigger is always detected if the signal generation is immediate after Start, but if I wait may be the trigger isn't detected.
Thanks for your interest.

[proserpio]

I solve my problem changing this asyncronous code:

Private Sub Start_Click()
CWAI1.Configure
CWAI1.Start
End Sub

with this synchronous one:

Private Sub Start_Click()
Dim Voltages As Variant
Dim BinaryCodes As Variant
CWAI1.Configure
CWAI1.AcquireData Voltages, BinaryCodes, 90
'CWGraph1.PlotY Voltages
End Sub

This code works fine in Win 2k and in XP too, even thought I can't cancel trigger wait action until time out is reached.

[Peterlily]

I also faced this problem. We developed an application applied to detect the vibration impulse and response in LabVIEW 8.0. The data acquisition card we used is 6024E. The driver is traditional DAQ.  Because this card has no hardware trigger function, I used the software trigger function in AI Read.VI. In the process of testing the impulse and response of a beam,  we can not obtain the test datas continuously because of the software trigger problem. Namely, we often miss some datas although the trigger level of the trigger signal comes up to the configured level. Why, What method can I take to solve this problem?

帖子被Peterlily在05-28-2007 10:54 PM时编辑过了

[Peterlily]

I also faced this problem. We developed an application applied to detect the vibration impulse and response in LabVIEW 8.0. The data acquisition card we used is 6024E. The driver is traditional DAQ 7.4.1f4.  Because this card has no hardware trigger function, I used the software trigger function in AI Read.VI. In the process of testing the impulse and response of a beam,  we can not obtain the test datas continuously because of the software trigger problem. Namely, we often miss some datas although the trigger level of the trigger signal comes up to the configured level. I have used the example of software trigger function provided in LabVIEW 8.0 to validate my thought and the result is the same with my thought. Why, What method can I take to solve this problem?