BigGrayPrimary - web

Event Triggering/RunUntil™

Watch Video

How would I benefit from this feature?

RunUntil1 There is no limit on the number of Event Triggering/RunUntil conditions that can be defined. All conditions are tested for each acquisition in a live or saved multi-acquisition sequence. Event Triggering/RunUntil is also available in M1 TestScripts™, thus allowing the definition of compliance tests on one measurement, or on a set of varied measurements. This greatly speeds test throughout time.

Description

M1™ lets you set conditions, called Event Triggering/RunUntil Conditions, that let you locate just the problem condition that you are looking for. For instance, you may suspect that a long rise time in a clock signal is the cause of a timing problem that you have. With the Event Triggering/RunUntil capability, you can set M1 to run until the suspected condition happens, and stop at that point with the information clearly displayed. You can specify several conditions and stop when any one of them occurs, or you can stop when all of the conditions occur in the same measurement.

There is no limit on the number of Event Triggering/RunUntil conditions that can be defined. All conditions are tested for each acquisition in a live or saved multi-acquisition sequence. Event Triggering/RunUntil is also available in M1 TestScripts™, thus allowing the definition of compliance tests on one measurement, or on a set of varied measurements. This greatly speeds test throughout time.

In the example below, the user is looking for when the Peak-to-Peak Period is > 260 ps AND when the Pulse Width is < 7.5 ns. When the conditions are met, the user wants M1™ to stop acquiring new data. Time stamping identifies when, out of thousands of acquisitions, a Event Triggering/RunUntil condition was met. Event Triggering/RunUntil conditions run in the background, so that you do not have to be present to find a rare failure condition; M1 will automatically stop when the condition you have specified occurs.