No Initial Move to Clearance Height in 2.5D

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create a sketch
2. Generate a profile
3. Create and save gcode

What is the expected output? What do you see instead?

The first cutter move is to an xy coordinate at whatever the z position happens 
to be.  If the cutter is at or below the part surface it will hang or gouge.

(Created with emc2b post processor 2011/01/31 23:55)
G64 P 0.0127 Q 0.0127
G54      (Select Relative Coordinate System)
(tool change to 1/8 inch Carbide End Mill)
T1 M06
 G90 G20 G17
(Sketch)
G00 X-0.06250 Y-0.60000

It seems there should be a G00 Zxx.xxx where xx.xxx is the configured clearance 
height before the XY move.

What version of the product are you using? On what operating system?

r1298, Ubuntu Linux

Please provide any additional information below.

Thanks for a great product!

Original issue reported on code.google.com by kc8...@gmail.com on 1 Feb 2011 at 5:11

[GoogleCodeExporter]

if you call a tool on a Real CNC it is recected to the Tool change position 

only on some real weard mashines okuma it will return to the last XY move

on normal Mashines it will be inthe upper zone if it comes out of the Tool 
change so this woudt be ok !!

TESTET on Haas VF2,5,Minimill 

Original comment by lot...@foengarage.de on 11 Feb 2011 at 6:10

[GoogleCodeExporter]

When I programmed that post, I intended for it to be up in the air, as it would 
be right after a toolchange. I figured that the machine would rapid to XY in 
that position and then drop down to the Z clearance height. If you need a 
different post processor- it's really easy enough to copy that emc2b.py file 
and the emc2b_read.py file to something like emc3.py and emc3_read.py. Then 
have a look at the tool change def in iso.py here:
    def tool_change(self, id):

        self.write_blocknum()

        self.write((iso.codes.TOOL() % id) + '\n')

        self.t = id

You could probably copy that into your new post processor -emc3.py (which would 
over ride it with your new definition) and maybe put in a safe Z height for 
your particular machine at the end like:
    def tool_change(self, id):

        self.write_blocknum()

        self.write((iso.codes.TOOL() % id) + '\n')

        self.t = id + '\n'
        self.write("G0 Z6.00\n")  

You would then need to add your new machine listing to machines.txt like this:
emc3 Linux EMC3 kc8wmc's gantry post - 0
Take a look at it and comment back here. You could pop into irc at #cam or 
#heekscad on freenode and someone could help you make a good post for your 
machine.
Dan

Original comment by ddfalck2...@yahoo.com on 12 Feb 2011 at 2:59

[GoogleCodeExporter]

It looks pretty real to me :)  However, it's a small hobbyist machine with a 
manual tool changer - if the same tool is in use, a common case, there is no 
physical tool change or tool movement, just close the tool change prompt.  I 
appreciate the insight into bigger machine operation.

Thanks for the effort, Dan - it looks pretty straightforward.  It will be a few 
days until my job will allow time to work with the machine, and I'll comment 
here.  IMHO guaranteeing the tool is left at a safe height irregardless of 
starting position seems appropriate, but my perspective is limited and your 
approach works for me.

Original comment by kc8...@gmail.com on 13 Feb 2011 at 12:33

[GoogleCodeExporter]

Original comment by danhe...@gmail.com on 24 Mar 2014 at 8:07

• Changed state: Invalid

[GoogleCodeExporter]

This issue just confounded me a little. I guess one can set zero, then manually 
lift the z axis up off of the stock, then start program.

Original comment by jamcinn...@gmail.com on 25 Aug 2014 at 8:05