Skip to content

[BUG] Fix: MissedAcquisition after TriggerEnable reset in TcoDataman #48

Description

@mhareznik

Problem

After an intentional TriggerEnable FALSE → TRUE reset sequence, the function block sends a trigger too early. The TriggerReady bit seen by the PLC can be a stale PROFINET packet value — the DataMan is not yet internally ready, resulting in MissedAcquisition.

Fix

After TriggerEnable rising edge, wait for TriggerReady = TRUE stable for at least 2 consecutive PROFINET cycles (≥ 32 ms) before allowing a trigger.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingquestionFurther information is requested

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions