Cognex In-Sight 26.2.1 · first-party documentation guide

Why encoder trigger delay and acquisition timeout zero are different controls

If encoder triggers queue up while the timeout is zero, what happens? Trigger delay and acquisition timeout are different controls.
Why encoder trigger delay and acquisition timeout zero are different controls
Trigger-delay queue ≠ acquisition timeout.Encoder-step delay can queue up to 18 triggers.Timeout 0 means the acquisition timeout is disabled.

If encoder triggers queue up while the timeout is zero, what happens? Trigger delay and acquisition timeout are different controls.

Start with the symptom

If encoder triggers queue up while the timeout is zero, what happens? Trigger delay and acquisition timeout are different controls.

What the documentation establishes

Encoder Trigger Delay postpones a trigger by encoder steps and can queue up to 18 triggers within the delay. This control is not available on In-Sight 6900 controllers.

Encoder Acquisition Timeout limits how long acquisition may take. The documented range is 0–10000 ms, and the default 0 disables the timeout.

Five checks at a glance

ScenePointLimit
1Trigger-delay queue ≠ acquisition timeout.The trigger-delay queue and acquisition watchdog are different controls.
2Encoder-step delay can queue up to 18 triggers.Encoder-step delay; this control is unavailable on In-Sight 6900 controllers.
3Timeout 0 means the acquisition timeout is disabled.Range 0–10000 ms; default 0 disables the acquisition timeout.
4Do not invent the fate of a 19th trigger.The cited page does not establish the fate of a 19th trigger.
5Check controller, queue and acquisition completion separately.No measured missed-acquisition or cycle test was performed.

Do not over-interpret the symptom

Do not infer that a 19th trigger is necessarily discarded, or that timeout zero stops acquisition. The cited documentation does not establish those outcomes.

Read-only preflight

Evidence limits

Check the exact controller, encoder settings, queued triggers and acquisition completion separately. This is a documentation-based illustration, not a measured miss test.

This article interprets first-party documentation and uses hypothetical diagrams. It does not report a live device, database, customer-data, outage, recovery or performance test.

Watch the short explanation

YouTube channel

The public YouTube schedule may be linked here after the provider assigns the native video ID. The article and local video are already self-contained.