push-push and comparative time logic in TIA / S7-1200

In that case, this is the default behavior provided by Siemens for HMIs and will be shown in every HMI sample project or application example with an HMI.  Download a few samples to see how they are used.

Others may have their own specific end-user problems or system behaviors that cause them to code their buttons differently, but, this is how I approach HMI buttons:

Each button gets default behavior, a single tag to denote the tag's action (toggle when pressed), where the appearance behaviors may have multiple PLC/HMI tags affecting them, like a button that activates a motor monitors the state of the motor "on" in the PLC and changes the graphic or words or color or other attribute for the HMI button.

If an HMI button is part of a sequence of steps rather than a toggle (push-push as you called it), I handle that completely differently.

Mike_Gera

I now think that we're on two different pages.

By "push-push", I mean that one HMI (or physical) button works as both a 1 (ON) and a 0 (OFF) button.

When the controlled bit is in the 0 state and the button is pressed, the bit state becomes 1.  When the controlled bit is in the 1 state and the same button is pressed, the bit state becomes 0.

I am not talking about "double-clicking" a button.

Sorry for the confusion.