Resume - rmu75/linuxcnc-wiki GitHub Wiki

date: '2013-12-28T14:44:53' title: One_Button_Run/Resume wiki_parent: One Button Run

Note

The HAL component toggle2nist is designed to provide this function. An example is on the forum [here].

Introduction

I recently added 3 large, physical buttons to control my machine. All three are used Allen Bradley buttons like those that can be found on eBay, that should last forever. The three buttons are: E-Stop -A red, protruding, button that locks in position that signals LinuxCnc to trigger an E-Stop condition Pause - An amber, protruding, momentary button, that tells LinuxCnc to pause the running program Run - A green, recessed, momentary button. I wanted this to either begin running a program, or resume it if it is paused.

The first two buttons are trivial to add. Their signals connect directly to halui.program pins.

Here's the problem. "Run" and "Resume" are two distinct operations. HAL must decide which signal to generate based on the current state of the system. In addition, halui must be in 'auto' mode in order to run the program. It must be requested if it is not already selected. Furthermore, timing can be a bit tricky. Continuing to assert halui.mode.auto, halui.program.resume, or maybe even halui.program.run can result in screwey behavior. An ideal solution is to assert these signals only until they take effect.

The Flip Flop

Halui comes with a native flipflop component. This is the ideal component for holding a signal for only as long as required. A simple example is shown to request 'auto' mode. This is shown at the top of the diagram below.

We are using two inputs of the flip flop: "set" and "reset". The logic of the output is follows:

If "reset" is true, the output is false
Otherwise if "set" is true, the output is true
Otherwise, if neither are true, the output remains constant.

Here's how we use it to request 'auto'.

We feed 'halui.mode.is-auto' to the 'reset' port. If we're already in 'auto' mode, there's no reason to request it.
We feed our 'run' button to the 'set' port. If it's pressed, we want 'auto' mode.
The output is connected to 'halui.mode.auto'. It will be set true only if the button is pressed, and we're not already in auto mode. It goes false as soon as linuxcnc switches to auto mode.

To Run or Resume, That is the Question

The logic uses 'and2' components to decide which mode to request. If the button is pressed and the program is idle, we want to run the program. Alternatively, if the button is pressed and the program is paused, we want to resume the program. These two 'and2' components are shown in the diagram below.

We use flip flops for each of these signals to limit how long they are presented. Once 'halui.program.is-running' is true, we no longer need to assert either 'run' or 'reset'.

You will also notice the 'edge' component. This component is used to ensure that only one signal is generated. The short pulse generated by 'edge' is sufficient to trigger the 'set' pin on either flip flop. Without this component, if linuxcnc momentarily goes to 'idle' on its way from 'paused' to 'running', the other 'and2' component would fire, generating a 'run' command, thus starting the program over instead of resuming.

upload:run_pause_halui_schematic.png

-Kip Shaffer