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
Autotrigger in Rapid Block Mode
Re: Autotrigger in Rapid Block Mode
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
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
Technical Specialist
Re: Autotrigger in Rapid Block Mode
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.
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.
Re: Autotrigger in Rapid Block Mode
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.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)?
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.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?
Martyn
Technical Support Manager
Technical Support Manager
Re: Autotrigger in Rapid Block Mode
Ok Thx Martyn.
L.
L.