FA-92149 / PLC ladder logic scan cycles / Member archive

Step transition waits for step time to exceed the minimum · case 04

Every step dwells one scan longer than its configured minimum, and zero-time steps need a scan of time.

Member previewVariant 4 · 3 implementations · 8 checks per implementation

Case contract

Cyclic step sequence with one active step. steps is a list of [min_time_ms, transition_tag]. Each scan [dt, inputs] first adds dt to the step time unless the step became active on the previous scan, then fires the transition if step time >= min_time and the transition tag is true. At most one transition fires per scan; after the last step the sequence returns to step 0; the new step time is 0. Step 0 is active before the first scan as if just entered. Return [active_step, step_time, entered_this_scan].

Why this case matters

Ladder programs are executed as repeated scans; each defect here changes what a rung, timer, counter or data-table instruction reports on a particular scan, which is how commissioning and field faults are actually observed.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
regression: scenario 1	`[[0, 0, false], [0, 40, false], [0, 50, false], [1, 0, true], [1, 0, false], [1, 25, false], [1, 75, false], [1, 100, false]]`	`[[0, 0, false], [0, 40, false], [1, 0, true], [1, 0, false], [1, 50, false], [2, 0, true], [2, 0, false], [2, 25, false]]`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.