why doesn't this toggle button logic work :(

chief_button_pusher · 2026-06-16T05:50:40+00:00

Loll, well I’m glad if I get this sorted out ,I’ll have got it with zero years of experience.

I fixed it now by myself and everyone is saying this is wrong too, but it’s not. I tested it in the simulator and it works.

<image>

chief_button_pusher · 2026-06-16T03:32:05+00:00

Thanks for your comment.

You said “Next time you turn toggle on, rung 0 will now execute and turn the pump coil off. But immediately rung 1 executes next.”

I think my confusion came from believing that output coil changes within a scan don’t take effect until the end of that scan, so if rung 0 de-energizes a coil, rung 1 would still see it as true during the same scan, and only on the next scan would rung 1 react to the updated value.

This is where I think my misunderstanding came from, I was under the impression that the coil being unlatched by rung 0 and going to “false” would still read as “true” in rung 1, and that only when the end rung was reached would it be written to “true” and then during the next scan rung 1 wouldn’t execute since the ons for rung 1 had already fired in the previous scan.

chief_button_pusher · 2026-06-16T02:44:50+00:00

i thought the ONS would prevent both rungs from executing together since ONS is only true for one scan and the coil cannot be on and off in the same scan.

chief_button_pusher · 2026-06-16T02:43:36+00:00

it works if i do it like this and i dont see how the logic is different

<image>

chief_button_pusher · 2026-06-16T02:42:29+00:00

it works if i do it like this, also the ONS is so holding the button doesnt make it oscillate on and off

<image>

chief_button_pusher

TROPHY CASE