Trigger rearm latency?

Post any questions you may have about our current range of oscilloscopes
Post Reply
rebasnop
Newbie
Posts: 0
Joined: Mon Jun 24, 2024 4:15 am
Location: https://snowrider3d.com

Trigger rearm latency?

Post by rebasnop »

Hello
Could you please provide the following specifications:

(1) Trigger rearm latency? Or put another way: what is the time interval between recapturing a fresh trigger?

(2) How long does it take to detect the logical OR between two trigger events that are (ChA rising across a specific trig level, ChB rising across another trig level) if the logic trigger function is utilized to do so?

Before the next trigger event is anticipated, the number of samples that need to be gathered after the first trigger would be finished.

Thank you,

Gerry
PICO STAFF
PICO STAFF
Posts: 1155
Joined: Mon Aug 11, 2014 11:14 am

Re: Trigger rearm latency?

Post by Gerry »

Hi rebasnop,

To answer your questions:

1) The time taken to re-arm the Trigger depends upon the Timebase being used for the capture, and the picoScope model performing the capture. The Trigger re-arm times, for the fastest Timebase of the PicoScope Model being used, are given in the Specifications page, on our Website, under the Triggering section. In general these values Range from <10us for our slowest (high precision) PicoScope 4262 to <700ns (typically 300ns) for our fastest PicoScopes.
The Trigger re-arm Time also varies slightly from capture to capture (which is why we state values of less than or typically).

2) The detection of the Logical OR of 2 Rising edges is very fast, but what matters is the time taken for the Trigger to fire (which defines the '0 seconds' point in the plot of the captured data) relative to the data being captured. So, the sequence of events are, the status of the Logic Condition that was set for the Trigger is determined, which then results in the Trigger Firing (for a True Logic outcome) or not Firing (for a False Logic outcome) and all of this happens within 1 sample period, So, this means that your capture effectively starts immediately after the Logic condition is detected.

Your last question depends upon the Trigger Mode that you are using. If you are using a Normal Trigger (i.e. a Trigger that repeats) then the data must be captured (for the duration of the Timebase that you set for the capture), and then sent to the Computer, before the next Trigger can fire. If you are instead, using a Rapid Trigger, then the data must again be captured, but then the Trigger is re-armed, which is the only delay after the capture (so if you perform a Rapid capture of 10 Waveforms, there wall be 10 capture periods, with each one separated by the Trigger Re-arm time).

Regards,

Gerry
Gerry
Technical Specialist

Post Reply