Generating G Code from MDI history log

Ok, the last parameter is the output file so set it to the location and name you want.

For some reason the generate button does not work yet but running ./M153 from a terminal does.

John

Thanks John. I did it according to your instructions. However, not when I want to launch the linuxCNC stepconfig does created, it gives and error and doesn't launch. I guess I still have some issues with the .ini file.

It worked only when I copied all files to the folder of a particular stepconfig that I launch. Where exactly is the .ngc file generated when the "generate" command is executed?

Hi

Thanks for looking after this John, I've been out.

There are a couple of typos, as you discovered, the attached .zip has them corrected.

However, not when I want to launch the linuxCNC stepconfig does created, it gives and error and doesn't launch.

Not entirely sure what this means you are going to have to post the errors.
You need to edit the .ini file and .hal file manually, and add the custom_postgui.hal file or its contents to your existing file.

I am probably assuming too much knowledge, so a brief run down

splice is a binary and needs to be in your PATH, /usr/local/bin/ is traditional for non-standard executables

The custompanel.xml file creates the buttons and must be named in your .ini file (as per the changes_to_ini file)

The custom_postgui.hal connects the buttons to halui-mdi commands, this file must be named in the .ini and the MDI commands must be in the .ini (as per the changes_to_ini file)
and custom_postgui.hal and custompanel.xml must be in your config folder

The M152 and M153 scripts must be in the directory named in PROGRAM_PREFIX= in your .ini file and must be executable (chmod 755)
For some reason the permissions on M152 keep getting changed when it is zipped.

header.ngc footer.ngc writecords.ngc should all be in that directory too
(You will need to edit M153 so that the paths in the commandline match yours - my directory is ~/emc2/ngc/ but yours may be ~/linuxcnc/nc_files/ or similar)

Work your way through and you will probably find the solution in the above

regards

It worked only when I copied all files to the folder of a particular stepconfig that I launch.

Yeah, that's what you need to do, as per above

Where exactly is the .ngc file generated when the "generate" command is executed?

See M153, both files are generated in /tmp

What does slice do exactly? The generated file has a bunch of M100 commands and other stuff in it when I ran it.

John