I would do as Andy said and use the buildbot first: a lot less hassle if you are tight on time and I doubt you need to go back to 2.6. It won't be long before they release 2.7 officially anyway.
Thus:
- Open a terminal window
- Do a 'sudo apt-key adv --keyserver hkp://keys.gnupg.net --recv-key E0EE663E' in that terminal window
- Do a 'sudo gedit /etc/apt/sources.list.d/linuxcnc-buildbot.list' and change a reference to 2.6 which is already there to 2.7. If there is none, add these two lines at the end of the file:
deb
buildbot.linuxcnc.org/
lucid 2.7-rt
deb-src
buildbot.linuxcnc.org/
lucid 2.7-rt
- Then save and exit gedit.
- Still in the terminal window do 'sudo apt-get update'
- Do a 'sudo apt-get install linuxcnc'
- Done.
The quotes (') above are not part of the commands and just there to separate the command from the rest of the text. Type/copy the commands without these quotes.
If you want to revert back to 2.6 do the same, but change 2.7 to 2.6 when editing the linuxcnc-buildbot.list file.
Now, I think the new TP uses reasonable defaults, but in case you might want to play: I have this configuration in my INI file:
..
..
[TRAJ]
AXES = 4
COORDINATES = X Y Z A
..
..
ARC_BLEND_ENABLE = 1
ARC_BLEND_FALLBACK_ENABLE = 0
ARC_BLEND_OPTIMIZATION_DEPTH = 480
ARC_BLEND_GAP_CYCLES = 4
ARC_BLEND_RAMP_FREQ = 200
..
..
Both the optimization depth and ramp freq are a lot higher than default, but as I said: I am mostly running curvy toolpaths, I have fairly speedy axes (18 meters/minute) with high acceleration (2500-5000mm/s^2), a high servo thread rate (8kHz) and I need to keep the cutter cutting so heat goes into the chips and not into the endmill/workpiece when doing HSM-style toolpaths.
