Lathe Macros

I see your point.

It's just the same on my test machine, but a lot faster, so it isn't so much of a problem.

I don't know how to fix it. The macro screen is designed to be resizable (I have invested a _lot_ of effort to make it resizable) as the original fixed-size one only suited a particular GUI and screen size combination.

The macro screen creates itself a few pixels smaller than the space it is given to live in by the host application. This allows the host gui to then shrink the window, the macros resize, and so on....

If you know that you will only ever want one size, replace the alloc.height and alloc.width with fixed numbers here: github.com/LinuxCNC/linuxcnc/blob/master.../lathehandler.py#L53

Andy Sir,
Thanks that helps me a lot. now screen remains same size, and ready to work.
Your highlighted line 53 in lathehandler.py
x, y, w, h = (alloc.x, alloc.y, 400, 400)
Did the trick.

Hi Andy,
I am just trying to set up the Lathe Macros on my Schaublin. I have LinuxCNC 2.8.2.11 with Gmoccapy 3.1.38.

I have put the current version of all these files in the Config directory where the {machine}.Ini resides.
boring.ngc
chamfer.ngc
drilling.ngc
facing.ngc
grooving.ngc
lathehandler.py
LatheMacro.svg
lathemacro.ui
radius.ngc
threading.ngc
turning.ngc

and then added the line you provided to the {machine}.ini[DISPLAY]
DISPLAY = gmoccapy
POSITION_OFFSET = RELATIVE
POSITION_FEEDBACK = ACTUAL
MAX_FEED_OVERRIDE = 2.000000
MAX_SPINDLE_OVERRIDE = 1.000000
MIN_SPINDLE_OVERRIDE = 0.500000
INTRO_GRAPHIC = linuxcnc.gif
INTRO_TIME = 5
PROGRAM_PREFIX = /home/schaublin/linuxcnc/nc_files
INCREMENTS = 1mm .1mm .01mm .001mm
LATHE = 1
POSITION_FEEDBACK = ACTUAL
DEFAULT_LINEAR_VELOCITY = 10
MAX_LINEAR_VELOCITY = 50
MIN_LINEAR_VELOCITY = 0.500000
DEFAULT_ANGULAR_VELOCITY = 12.000000
MAX_ANGULAR_VELOCITY = 180.000000
MIN_ANGULAR_VELOCITY = 1.666667
EDITOR = gedit
GEOMETRY = xyz
EMBED_TAB_COMMAND = halcmd loadusr -Wn gladevcp gladevcp -c gladevcp -U notouch=1 -U norun=0 -u lathehandler.py -x {XID} lathemacro.ui

When I restart LinuCNC I get no errors, but also no change to the GUI, no additional tab for the Macros. Do I have the wrong versions for LCNC 2.8? I see in the thread that there is GTK3 after come point. I haven't changed anything since the basic 2.8 on Mint install nearly a year ago.
Mark

Hi there, im very much a noob when it comes to anything other than g-Code.
I have just installed LinuxCNC 2.9 on MX21.2.1 (using this guide www.qtpyvcp.com/install/bullseye.html ) to run an old Orac lathe. It was running on 2.7.14 but wanted the G71 cycles, and figured as i was doing it from scratch id try to get some macros working.
I ran stepconf on the old file and have gmoccapy 3.1.3.10 running (used Axis with no macros on 2.7.14)I went here configs/sim/gmoccapy/lathe_configs /  and downloaded all the new macros, svg, .ui. py etc into my . Modified the ini as follows (Embed, RS274NGC, Macros)

I get the tab appearing in the window but when i click on it, nothing happens.
If i go MDI i see the macro buttons and clicking these generate errors such as g1 without feed rate etc, so it looks like its trying to run them from here but i have no interface to input parameters.

Any ideas? These macro look like a real good job fora lot of what i use the lathe for,

Thanks

For 2.8 the simpler way would be to copy the set of files from the 2.8 branch.

If you are using the notouch and norun options then I suspect that you have copied the 2.9 files.

It is probably possible to make the 2.9 files work with 2.8. And there are significant enhancements in graphics and layout (plus extra cycles). I will see what it takes to make it work.

Thanks for looking at that Andy.
Mark