Nembered Paramenters accessibility.

bigalex wrote:

For dev version do you mean getting it from "git" ?
At the moment I'm using a test PC with Ubuntu Hardy 8.04 and LCNC 2.5.2 (stepper configuration) installed but I understood that I need
an Ubuntu Lucid 10.04 installation to use it with GladeVCP isn't it ?:

You can get a precompiled version of "master" from the buildbot:
buildbot.linuxcnc.org
Instructions are there on how to configure it so that you can update from there as required.

I _think_ that GladeVCP works under 8.04. Try the test configurations in the config picker: sim->gladevcp

I will try to have a fiddle around with the idea in the next few days, to make sure I can get it to work.

bigalex wrote:

Ok Andy !
Do you know what is the status and the features of the G code "connectivity" to HAL logic.
I wish to have Numbered Parameters connected to HAL pins in some way:

The status (as I understand it) is that G-code can read the value of a HAL pin, but it can't set it.

I am suggesting an approach that does not store the data in numbered parameters, but in a separate dedicated file, controlled and owned by the custom GUI.
(You can have the GladeVCP GUI as the only visible GUI, too, if you want)

ArcEye wrote:

There is a way to pass values back to GCode, but it is kludgy.

A MDI command can set a parameter,

Also, as long as the G-code is able to actively _look_ for the value when it needs it, the G-code analogue input and output commands can be used.

Attached is a complete config that I think demonstrates a way to achieve what I think you want to achieve in a completely different way to the way you think you want to do it

It uses the Axis interface (but doesn't need to, you could use a standalone Glade interface, and use halui as the GUI specified in the INI file, then your Glade GUI would be the _only_ GUI.)

The three spinboxes let you define the position and radius of a circle. The default G-code program reads the gladevcp HAL pin values, and makes the programmed move. This is only possible using FEATURES=12 and the #<_hal[some.hal.pin]> structure that that allows you to use in your G-code.

Note that there is actually no HAL link between the Glade widgets and anything at all in the rest of LinuxCNC. (this is really a cool discovery, and will revolutionise the way I do my lathe subs)

When the Glade GUI exits it saves the state of all the widgets in a file called savestate.ini (this is a little unfortunate, as the config picker thinks this is a LinuxCNC ini file, but never mind).

When you start LinuxCNC all the widgets get restored to their previous value. Thus you have the persistence you wanted.

Note that the postgui hal file does nothing at all except enable the panel adjustments. This could very easily be a HAL link to a physical keyswitch, so that the panel is always visible, but only adjustable by someone with the key.
(There are about a dozen ways round this "security" but the users would have to try, they couldn't claim accident)

To try this out, set your system up to use "master" using the instructions at buildbot.linuxcnc.org
Then extract the attached config into your configs folder, and pick "glade2gcode" from the config picker.

Because the G-code file is opened before the Glade panel (wierd, but there you go) there is an error dialog when the G-code program opens. This is annoying, but could be bypassed by having the GladeVCP panel embedded Python load the program instead of the INI file