How do I do a manual tool change?

Hi

I just do it in G Code if I want the spindle stopped and re-started

...
M5
G28
M6T2
M3
G4 P10
...

There are so many different types of toolchanger, with a lot not wanting the spindle stopped (almost all lathes), coding it is probably easiest

regards

ArcEye wrote:

...
M5
G28
M6T2
M3
G4 P10

Maybe this is good option as in most cases when tool is changed the spindle speed is changed too.

I know this is a pretty old post, but I'm having the same issues as you were Gold Boarder. Can you share your latest config files? I'm also curious to see how you setup the Auto, Manual and MDI HAL GUI. Thanks.

Ha (noob), realized that shortly after posting. I'm trying to get to where @eslavko is at (see below). I'm having the issue where linuxcnc is not letting me control the machine during this process. Also, I'm wondering if I should be going back to G53 (my home position) before the tool change instead of currently just raising the Z axis. I'm not sure how to do this exactly. Should I just run N90 G53 with no other parameters? I've attached an example of my current code.

"When M6 is executed the popup window is shown. And I happily change tool and make Z touchoff."

Machine: Sherline 5400 Mill

Hi, robksawyer

It's been mentioned above - you need to change hal_manualtoolchange file (located at /usr/bin)
it's a Python script LinuxCNC calls when M6 command is issued.
My owm machine uses new hal_manualtoolchange (see attach) - it's a bit buggy with LinuxCNC 2.7 but works.

Your G53 question is pretty simple - you may add any code prior to toolchange in your postprocessor, or manually.
Just an example: raise Z, then move to machine coordinates X10 Y200. Do toolchange. Raise Z again to safe top.

Thanks! I haven't cracked open the file yet, but if you're able to elaborate on what you changed in the file to cancel out or allow manual mode, I'd appreciate it. Id really like to understand some of the content of these scripts. What manual would I refer to if I wanted to make my own script like this?

( an old thread yes, but I was wanting to do the same today )
( SO I boched up this bit of G-code )


( Position the head over each hole in turn and use tool change )
( commands to pause the g-code while we manually tap that hole. )

( Manually adjust Z to be higher than anything, then test it.)
( After testing, place Z close to your work )

( M05 Ensure the spindle is not running, or dissable it with a key, in Tormach PCNC exists a lockout Key )

M05

(Drill 1 position )
G00 X20.7897 Y15.1542
M6T1

(Drill 2 position )
G00 X20.8303 Y45.1541
M6T2

(Drill 3 position )
G00 X60.8065 Y42.6206
M6T3

(Drill 4 position )
G00 X60.7727 Y17.6206
M6T4

(Drill 5 position )
G00 X91.9000 Y20.8285
M6T5

(Drill 6 position )
G00 X91.9250 Y39.3285
M6T6

(Drill 7 position )
G00 X116.7250 Y39.2950
M6T7

(Drill 8 position )
G00 X116.6999 Y20.7950
M6T8

( Return to the beginning )
G00 X0.0000 Y0.0000

( End the program )
M30

Hi guys I need to manually re-home Z axis in every tool change, so I need this functionality in any case and asap!
I tested with LinuxCNC 2.11 the scripts presented here and the script from gist.github.com/robanonymous/b677a47aed504548440c8258f71724b1
but none of them works correctly.
What is happening is when the code meets Tx M6 (x is the number of the tool) the dialog box appears and the execution of the gcode is stopped. So far so good.
If you press continue in the dialog box the program is doing nothing, doesn't continue or anything.
I checked the code and should theoretically continue from the next line, but nothing is happening...
If I press the Play button again the code continues from the beginning...

Any clues?

UPDATE!!!!!

I dug into the code and actually found out that both linuxcnc.stat().motion_line and linuxcnc.stat().current_line give wrong results.
I solved the problem by changing the line 52 from curLine = linuxcncStat.motion_line to curLine = linuxcncStat.read_line

According to linuxcnc.org/docs/2.6/html/common/python-interface.html
read_line: (returns integer) - line the RS274NGC interpreter is currently reading.

For me at version 2.7.11 works!!!
The question is how it was working for others or for previous versions with the other commands given that they are now unreliable and if it is now guaranteed to work with read_line