Lathe Macros

kjacobs wrote:

andypugh wrote: I have put an updated file in the first post.

For me, the zip file comes up with an empty "lathemacro.hal" file which is the POSTGUI_HALFILE according to the .ini file, and from what I know that file should contain the _hal[gladevcp.turn.z-f] ... definitions? linuxcnc complains.
Karl

Mine is zero length too but it doesn't seem to matter. The problem you're having may be that your linuxcnc is too old. I thing the _hal stuff showed up in 2.6. I'm running 2.6.5.

Drew

drogge wrote:

kjacobs wrote:

andypugh wrote: I have put an updated file in the first post.

Mine is zero length too but it doesn't seem to matter. The problem you're having may be that your linuxcnc is too old. I thing the _hal stuff showed up in 2.6. I'm running 2.6.5.

Drew

I am running 2.7.0~pre on the machinekit branch, The problem may be in that branch, then. The gladevcp panel and everything else comes up fine.
Karl

Andy's last line in message #54119 (supplying the GUI numbers als parameters) works for me. Thanks for your help.
Karl

EDIT: I probably was just too dumb to apply FEATURES=12 in the ini file as said in post #42245... so I consider changing everything to paramters was an appropriate punishment.

Huge thanks to Andy for this! I haven't tried it yet, but I bookmarked it. My CNC Mini-Lathe is running LinuxCNC 2.5.x, and I don't have a spindle encoder or automated control of spindle speed yet. The LinuxCNC update and the spindle encoder and speed control are on the To Do list, but I also have a larger lathe build where I really want to use these macros. I'm particularly interested in using them as G code generators so I can create programs for short run production jobs. It seems that the macros are currently intended mostly for use with one-off jobs. I hope this, or something very much like this, is integrated into future versions of LinuxCNC.

BruceLayne wrote: I'm particularly interested in using them as G code generators so I can create programs for short run production jobs..

These macros don't produce any G-code. Each operation runs a pre-programmed routine with different parameters.

If you want to produce G-code then look at NGCGUI or Features or JT's G-code generator

I have just posted an updated ZIP file to the first post in this thread.

The macros now receive the values as subroutine parameters. so the FEATURES option is not needed.

Also new is the ability to type "3in" and have the value automatically become 76.2 to use imperial values on a metric lathe, or type "75mm" and have the value automatically become "2.95" for the reverse
You can also type "tpi" for conversion to mm pitch or "pitch" to convert mm pitch numbers to TPI.
Also converted are the fractions "/2" "/4" "/16" "/32" "/64" too. I found this very useful making Imperial Ner-a-Car parts on my Metric lathe.

So, if you want you can type "2 5/64in" and end up with the value in the box of "52.784"

There is code in the handler to move the cursor to the end when these conversions happen, but for some reason it doesn't work.