single block mode: movement commands build up

Good morning, dear community,
I’m currently setting up a CNC control system and would like to include some physical buttons on the control panel. And here’s my problem: I’d like a button for ‘single block’. I’ve managed to get the basic principle working, but the problem is that movement commands build up if I press ‘Cycle Start’ several times in succession. I don’t want it to work like that. In Axis, the behaviour for single-block mode is just as problematic. Do you have any suggestions for me?

Can you provide a rough description of what behavior you are looking for?

Yes, I’ll describe how I envisage it: I have a switch for ‘single block’. When this is active and I then press ‘Cycle Start’ once, exactly one line of G-code should be processed. If I accidentally press ‘Cycle Start’ twice in succession, the next block must not be processed immediately without a pause. This is a safety feature, as is probably standard on all reputable industrial control systems. Suppose I want to move the tool along a square in single-block mode and I press ‘Cycle Start’ four times right at the start; the entire programme will be executed. However, I want only the first side to be moved. At the first corner, the machine stops and waits for my next ‘Cycle Start’ command.

You probably want to look at halui pins, see how they behave when it executes and then pauses, I think you can probably use Hal to link your panel button to not come in when the program is running, look at halui and motion pins, you can probably 'not' one of them and 'and' it with the button to then run a single line, and it will not send anything when not running or not in motion. If you cannot figure it out I can take a deeper look