Entry/Exit moves before moving Z to cutting depth

[GoogleCodeExporter]

Please swap order of G41/G42 and Z move in shape.Write_GCode, so that the entry 
move doesn't cut anything.

diff dxf2gcode_b02_shape.py.orig dxf2gcode_b02_shape.py
266,267d265
<         postpro.chg_feed_rate(config.F_G1_Depth.get())
<         postpro.lin_pol_z(mom_depth)
280a279,280
>         postpro.chg_feed_rate(config.F_G1_Depth.get())
>         postpro.lin_pol_z(mom_depth)

rgds

Original issue reported on code.google.com by goo...@e-trolley.de on 26 Oct 2010 at 11:52

[GoogleCodeExporter]

This is possible of couse, but this is not the function i want to have for my 
milling. I really want a start move like this. Yes i may cut some material 
during the start move but normally this is waste and therefore just thorw it 
away. If you dont want the start move to cut somemethink you need to reduce the 
startradius to an minimum, this should also work. Did you already tried this.

Original comment by christian.kohloeffel on 27 Oct 2010 at 9:06

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Also see comment on previous issue.

Regards
Christian 

Original comment by christian.kohloeffel on 27 Oct 2010 at 9:14

[GoogleCodeExporter]

Unfortunately reducing the start radius doesn't work, because EMC expects the 
start move to be at least 1/2 of the tool's radius.

Original comment by goo...@e-trolley.de on 27 Oct 2010 at 9:58

[GoogleCodeExporter]

This will be a new option for the new draft release we are working on.

Original comment by christian.kohloeffel on 29 Oct 2012 at 9:00

[GoogleCodeExporter]

Implemented now.

Original comment by christian.kohloeffel on 15 Feb 2015 at 2:53

• Changed state: Fixed