Passing a value to a subroutine from a Spinbox

andypugh wrote:

BigJohnT wrote: FEATURES = 8 seemed to do the trick.

This works nicely at the start of a file. But the values only update when a program is not running, so if you need "live" data the G-code analogue inputs are the way to go.

This was an mah addition, and he has decided it was a mistake. Personally I use it too much to agree, it just needs the limitations to be documented.

The limitation has been documented.

JT

BigJohnT wrote: The limitation has been documented.

There is a more detailed explanation of the nature of the limitation here:
linuxcnc.org/index.php/english/forum/10-...ignal?start=80#51544

I'd say the 'mistake' is not the ability to read HAL-pins, but not busting the queue.

Jost curious: is all this 'better' when one uses Python for half-control/half-motion things? I already have a case where I want LinuxCNC to control a machine that is not even a far cousin of a milling machine. It is just that Mesa hardware is affordable and of good quality, GladeVCP offers a quick method to add custom GUI elements, HAL allows a lot of special requirements to be implemented and G-code is a perfect language to describe simple motions with which a lot of people are familiar.