Lathe Macros

mariusl wrote:

where is the best place to put the ngc and png files that goes with your macros?

I have them in the config folder (the same path as the INI) to keep them "safe"

There are a few annoying quirks (which I need to fix) but I use them pretty much exclusively.

The quirks are (starting from the most serious)
1) They read the starting position before doing the tool change. This is very bad. I have found that having the tool change automatic is annoying anyway, and I plan to add a "load tool" button to each screen rather than do a tool change to the selected too.
2) For some reason you generally have to click "run" twice.
3) You can't keyboard-jog with the mouse pointer over the Glade tab.

I will fix 1 soon, but I don't know how to fix 2 and 3, and just live with them.

mariusl wrote:

The main problem though is that no code is posted?

I don't know what you mean?

The tabs just run fixed parametric G-code routines. They don't generate G-code.

mariusl wrote:

I thought that you post gcode to the screen like NGCGUI does. It did nothing so I checked on the auto screen to see what the code looks like but saw no code. Hence my confusion

In the Axis interface it is actually a little strange, the G-code preview window acts like it is running a program, and highlights lines in the currently loaded file, but that isn't actually the code that is running

mariusl wrote:

Have ypu tried this with Gscreen.

No, I have actually never tried Gscreen at all.

I am getting strange behaviour. When I run the turn macro it says that the file turning.ngc cannot be found although it is in the config folder.

Looking at the sample config I think that this is due to a rather subtle addition to the INI file

SUBROUTINE_PATH = ../../../nc_files/gladevcp_lib:./

That ./ at the end means that the system also looks in the same folder as the INI file for subroutines.