G71

What would be my simplest option to obtain G71 cycle?

I hear that ver2.9 has it built in. Is this my best route?

rider-83 wrote: I hear that ver2.9 has it built in. Is this my best route?

Yes.

See buildbot.linuxcnc.org for instructions on how to start using the dev version.

Would it be as simple as:

Make a back up copy of my config folder with the .HAL and .INI files

Install/replace my ver 2.7 with 2.9

Then copy over the backup folder?

Even simpler. Make a backup copy of the configs just in case. But they won't be overwritten.

A script will ask to run to update the 2.7 config to the 2.8 format.

Will it have any effect on my current Lathe set up, will everything stay as they were?

Everything should "just work". But make a backup of the config folder just in case.

Cool. I give it a try.

Andy,
I have successfully trialled G71 via version 2.9, and as you know am currently working with the new 'missing-teeth' feature with 'one' sensor in an attempt to get a working G76 cycle.
BUT, the latest upgrade of 2.9 has made my system completely unusable because of GUI screen re-sizing issues when using GMOCCAPY or other Gscreen GUI's.
I'm currently preparing a new hard drive to step back a version back down to 2.8 so that I can at least use the Lathe.
Once installed and working, is it at all possible to gain access to the G71 & 'missing-teeth' that we see in the 2.9 version, without installing the problematic GUI that comes with that upgrade?

Missing-tooth index should be easy enough to add.
Getting the G71 cycles would be a little harder.

If you are prepared to build LinuxCNC from source (not especially hard) then you should be able to simply apply the relevant patches.

github.com/LinuxCNC/linuxcnc/commit/c73b...ba16915bb200fbe5d109
As a patch to apply with github.com/LinuxCNC/linuxcnc/commit/c73b...5bb200fbe5d109.patch

For the G71 things are a bit more difficult. You would need to apply these commits in chronological order:
github.com/LinuxCNC/linuxcnc/search?q=G7x&type=commits
(to get a patch file, click on each one, then append .patch to the URL and reload. That gives a plain-text patch file)

I'm going to have a go at this, starting with G71 patch.
I have a fresh new install of 2.8 on a clean new hard drive.
We have run updates to the latest version of 2.8.2

I'm completely new to any of this, so please bare with me while I educate myself.

My first question is regarding:
github.com/LinuxCNC/linuxcnc/commit/c73b...ba16915bb200fbe5d109
Is this just a location describing the patch,

and the actual patch is located:
github.com/LinuxCNC/linuxcnc/commit/c73b...5bb200fbe5d109.patch

In order to use: patch -p1 < name-of-patch-file

How do I obtain the 'name-of-patch-file' file?
Do I cut and past the script into Geany and save it under any file name with .patch extension, or is there actually a file to download or link to ?