MDI Commands

Can you please point me to where I can follow a newbie step-by-step instructions on how to have a one button on GUI execute this code or any pre-define G-code from a file
thanks
-Doron

This is about as succinct an explanation as I can find.
wiki.linuxcnc.org/cgi-bin/wiki.pl?Adding_Custom_MDI_Buttons

It would also help to read as much info you can find on Halui and Pyvcp in the integrators manual.

If you search around you should be able to find more examples to try to follow..

Another alternative to experiment with is a set set of probe
routines adapted for ngcgui:

(This complete simulator config will work for 2.6 or greater,
set up is for inch units)
The simulate_probe is a simple built-in gui to simulate a probe

I see that the use of MDI_COMMAND requires editing the INI file and is limited to 63 lines. (and having to restart the engine,,,)
I was hoping to be able to use several buttons which are connected to G-Code files. (typicallly for Z-touch off, center probe, special tool offsets, etc....)
Thanks.
-Doron

doronby wrote: I see that the use of MDI_COMMAND requires editing the INI file and is limited to 63 lines

You can have 63 buttons. That doesn't seem like such a limitation.
Each button can call a G-code subroutine of arbitrary length.

You can do much the same thing without INI and HAL intervention by using a GladeVCP button linked to an MDI_action object. The MDI_action contains a single line of G-code, but that too can be a subroutine call. Rather usefully the MDI_action string can contain string-substitution values from other GladeVCP controls, and those can be passed as parameters to the G-code subroutine.

What I really need a step by step 'Newbie' how-to connect GUI button to arbitary G-code.
Does anything like that exist ?
If not, I guess I will have commence the long reading + Trial-and-error exercise.

Thanks
-Doron

P.S.
So far I have done the following.
1) Installed the LiveCD
2) Run the step wizard and configure the pins and screws
3) Modify the files to use the x and y screw compensation files I created with my DRO
4) Adjust speeds, accelation and travel limits to fit my machine.
4) Adapt Z-Touch-off and Center-Finder G-code that I found on the Forum.
5) Since I had modified my setup files... I can not re-run the StepWizard again to activate options as it warns me that I am going to loose my hand edits...

andypugh wrote:

doronby wrote: I see that the use of MDI_COMMAND requires editing the INI file and is limited to 63 lines

You can have 63 buttons. That doesn't seem like such a limitation.
Each button can call a G-code subroutine of arbitrary length.

You can do much the same thing without INI and HAL intervention by using a GladeVCP button linked to an MDI_action object. The MDI_action contains a single line of G-code, but that too can be a subroutine call. Rather usefully the MDI_action string can contain string-substitution values from other GladeVCP controls, and those can be passed as parameters to the G-code subroutine.

not 63 buttons.... total of 63 lines with MDI_Command..0..63

doronby wrote: not 63 buttons.... total of 63 lines with MDI_Command..0..63

No, each MDI_COMMAND HAL pin calls a single line of G-code defined in the INI file.
If you need more than one line of G-code then the single line of G-code has to be a subroutine call.
eg
MDI_COMMAND O<hole_probe> CALL
MDI_COMMAND O<bottom_left_corner> CALL

Have you looked here...
wiki.linuxcnc.org/cgi-bin/wiki.pl?Adding_Custom_MDI_Buttons

RickG

Where does it say the limit is 63 commands?

BTW 0-63 is 64...

JT