G00 doesn't finish move until next move

I am having the same problem as described in this thread...

40266-g0-movement-gouges-part

It isn't clear to me what the recommended solution is. I have gcode that cuts out a pocket then drills 4 holes. The four holes are gouged out because the g00 z clearance move isn't completed unit the next move. I removed all of the pocketing code and the g00 z5 moves do not exhibit this behavior. Why does this occur only after the pocketing gcode that only contains G00, G01 and G03 moves?

Is g64 or G61 the only options to deal with this?  It seems like this problem would be encountered frequently.

Thanks for considering my issues.


 

I assume either g64 or G61 will work. My post has asked some specific questions.

Linuxcnc requires a great deal of learning (doc supported). If the goal is to have post-processed gcode that safely make parts, I can't recommend enough learning about its trajectory planner along with standard industry cad/cam path blending for contour rough, semi-rough & finish operations, tolerancing for manufacturing and (and) clearances.

Revisit your specific questions once that's assimilated.

ps. What gave it up; there are no known CAM programmers omitting g61 for drilling and center line operations. Your gcode is textbook beginner. 

e.g.

G17 G21 G40 G49 G80 G92.1 G94 G90 G61 <<< always init exact stop

(WALL_PROFILING)
G0 G53 Z0.
T24 M6 G43
G54
G64 P.05 <<< enable path blend for roughing (P0.002 Q0.002 = finishing = tolerancing).
.....
G0 Z10.
G61 <<< end of operation; disable path blending.
G49

(DRILLING)
G0 G53 Z0.
T12 M6 G43
G54
...... <<< G61 is modal. Nothing to do here, let it drill exact. 
G49
G53 Z0.
M2

Thanks to everyone for all of the replies. I'm as green as they come, I had never heard of g61 or g64 before yesterday.

I relied on Estlcam to spit out working gcode, so several lessons learned here.

Mecanix, your general tips and specific pointers are appreciated.

Joe

 
See if Estlcam can give you a hand with tweaking your post processor. Tols & blending are normally automated via CAM really. Most CAM platform hack this easy, if not all (nowadays). The logic in mine evaluates the tolerance for the type of operation, then move on calling the appropriate "path_mode_x" template for it. 

e.g.