Test and Measurement Forum

Autotrigger in Rapid Block Mode

Post your LabVIEW discussions here

Autotrigger in Rapid Block Mode

Postby BSI » Wed Apr 13, 2011 6:11 pm

Hi,
I am working with a 4227, and LabVIEW performing Rapid Block Acquisition. I need to acquire a predefined number of captures, let's say 100, and average the resulting 100 segments. However, sometimes the incoming signal may change so that a trigger is not detected leading the digitizer to perform an autotrigger on a few of the 100 captures after the preset Autotrigger(ms) time expires (set in the ps4000SetSimpleTrigger with autoTrigger_ms).

On my resuting data though, I now have 100 traces, some withe valid data, and a few resulting from the auto trigger. How can I find out which ones were the result of autotriggering so I can eliminate them?

Thx.
Laurent
BSI
Newbie
 
Posts: 0
Joined: Wed May 12, 2010 3:15 pm
Location: Canada

Re: Autotrigger in Rapid Block Mode

Postby ziko » Thu Apr 21, 2011 9:21 am

HI Laurent,

The only way you can tell is to look at your trigger point, if the trigger condition was not met then this would be wehn it autotriggered.

I suppose for future you should set the auto trigger delay to 0 to disable the time out.

Kind regards
Ziko

Technical Specialist
ziko
Zen Master
Zen Master
 
Posts: 1705
Joined: Fri Dec 01, 2006 10:03 am
Location: St Neots

Re: Autotrigger in Rapid Block Mode

Postby BSI » Thu Mar 06, 2014 12:02 am

Hi,
Is it still the case that the pico driver does not indicate whether a given capture was acquired from an actual trigger level being detected versus auto-triggering after a set delay (in the absence of the trigger condition)?

What happens to a given data capture if I set the auto-trigger delay to 0ms and no trigger level is detected: No capture is done, and the digitizer re-arm the trigger for the next capture?
thx
L.
BSI
Newbie
 
Posts: 0
Joined: Wed May 12, 2010 3:15 pm
Location: Canada

Re: Autotrigger in Rapid Block Mode

Postby Martyn » Thu Mar 06, 2014 7:38 am

Is it still the case that the pico driver does not indicate whether a given capture was acquired from an actual trigger level being detected versus auto-triggering after a set delay (in the absence of the trigger condition)?
There is no specific function when using RapidBlock or Block modes however you may be able to use the Trigger Time Offset functions and if these return sensible values then a trigger would have occurred.


What happens to a given data capture if I set the auto-trigger delay to 0ms and no trigger level is detected: No capture is done, and the digitizer re-arm the trigger for the next capture?

It's not a case of no capture will be done, the trigger will still be armed and the scope will be waiting indefinitely for a trigger.
Martyn
Technical Specialist
Martyn
Site Admin
Site Admin
 
Posts: 2339
Joined: Fri Jun 10, 2011 8:15 am
Location: St. Neots

Re: Autotrigger in Rapid Block Mode

Postby BSI » Thu Mar 06, 2014 4:44 pm

Ok Thx Martyn.
L.
BSI
Newbie
 
Posts: 0
Joined: Wed May 12, 2010 3:15 pm
Location: Canada


Return to LabVIEW

Who is online

Users browsing this forum: No registered users and 0 guests