YES... there is a way to do it without Timers.
That method involves a Counter instead of a Timer. However, you should be aware that a Timer and Counter are essentially the same thing.
Before I explain the Goofy Counter method...
Take a hint from what I said about "state" and "actions".
Tracking a "State" is "timeless".
Tracking "Relative Actions" is not timeless (i.e., it is time sensitive!).
Think very carefully in terms of the actions that need to occur in order to "KNOW" that a proper "SEQUENCE" has occurred.
(A then B) OR (B then A)
Now, "A" could have just gone ON, yesterday! And "B" just gone ON just now.
Does that serve the purpose?
It's not enough to see a PB go ON while the other is ON. That would defeat the purpose of the "Anti-Tie-Down", don't cha think?
When a PB is released, you could latch the fact that it is released.
You could do that for the other PB as well.
Now, knowing that both PB's are OFF, if BOTH PB's are pressed at EXACTLY the same time then you can get a cycle. What do you think the odds are for that to happen?
Realistically, both PB operations need to be VALID AND they need to happen within X-Seconds of each other. Thus the need for the Timer.
.
.
.
The Counter Method... This is a goofy way to do it.
When a Valid PB operation occurs, if the other PB is NOT ON, then begin counting PLC scans. If the other Valid PB operation then occurs before the counter reaches the preset value then the cycle occurs.
If you made a bet with someone that you could do an Anti-Tie-Down without a Timer, this will suffice, technically.
But it can be argued that X-number of scans is actually a Timer. The time value being equal to "X-scans" times "Scan Time".
Aw, Damn!
I just posted and now see that it was a challenge put on you.
Well, there's a freebie!