Passing a value to a subroutine from a Spinbox

BigJohnT
Topic Author
Offline
Administrator

23 Oct 2014 23:44 #52336 by BigJohnT

Replied by BigJohnT on topic 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

Please Log in or Create an account to join the conversation.

andypugh
Offline
Moderator

24 Oct 2014 00:15 #52338 by andypugh

Replied by andypugh on topic Passing a value to a subroutine from a Spinbox

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

Please Log in or Create an account to join the conversation.

DaBit
Offline
Elite Member

24 Oct 2014 01:48 #52340 by DaBit

Replied by DaBit on topic Passing a value to a subroutine from a Spinbox

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.

Please Log in or Create an account to join the conversation.

Time to create page: 0.138 seconds