Bug---Z Lift on Outline dives into material and runs to start point

Kiri:Moto
1

To start the CNC is above the part by 2 inches and at part center. When I execute the Gcode the machine dives straight down, at center and them runs through the material to the path starting point. This of course ruins the part.

Untitled2
Untitled21366Ă—1076 286 KB
Untitled
Untitled1366Ă—1076 256 KB

IMG_3428
IMG_34282448Ă—3264 2.21 MB
G21
G90
G0 Z-3.1800 F381
G0 X65.0875 Y-55.6404 F508
G1 Y55.6405
G1 X65.0454 Y56.4965
G1 X64.9082 Y57.4215
G1 X64.6810 Y58.3286
G1 X64.3660 Y59.2090
G1 X63.9662 Y60.0544
G1 X63.4854 Y60.8564
G1 X62.9284 Y61.6075
G1 X62.3004 Y62.3004
G1 X61.6075 Y62.9284
G1 X60.8564 Y63.4854
G1 X60.0544 Y63.9662
G1 X59.2090 Y64.3660
G1 X58.3286 Y64.6810
G1 X57.4215 Y64.9082
G1 X56.4965 Y65.0454
G1 X55.6405 Y65.0875

2

@dana1954 please right-click export your workspace and drop it here or in a message to me so I can replicate what you’re seeing.

3

workspace.kmz (249.9 KB)

4

when I use your workspace to generate gcode, this is how it starts for me. the animation reflects this and no collisions. the 1 inch clearance specified is shown in the preview. your gcode is missing the G0 Z25... move which I can’t explain. if you re-export the gcode, is it still missing? you can enable gcode preview in preferences so you can see the gcode without export/saving the file.

G21
G90
G0 Z25.4000 F381
G0 X65.0875 Y-55.6404 F508
G1 Z-3.1800 F254
G1 Y55.6405 F508
G1 X65.0454 Y56.4965
G1 X64.9082 Y57.4215
G1 X64.6810 Y58.3286

Screen Shot 2021-09-13 at 3.54.36 PM
Screen Shot 2021-09-13 at 3.54.36 PM2300Ă—904 510 KB

Screen Shot 2021-09-13 at 3.55.31 PM
Screen Shot 2021-09-13 at 3.55.31 PM2312Ă—944 543 KB

Screen Shot 2021-09-13 at 3.59.32 PM
Screen Shot 2021-09-13 at 3.59.32 PM1252Ă—444 79.6 KB

Screen Shot 2021-09-13 at 4.03.56 PM
Screen Shot 2021-09-13 at 4.03.56 PM1188Ă—954 182 KB

5

aha. if i execute the key sequence S, P, S, X then I can get it to omit the first move. which is puzzling. but at least repeatable. and so it shall be fixed.

6

found and fixed. will be in the next release. the workaround in the mean-time is to a arrange before re-slicing.

1 Like
7

Thanks @stewart . I’ll review the Gcode.

8

What revision should I be using. I selected 3.0 and the “G0 Z25.4000 F381” was in the code

9

What does this mean, I never use keys?

10

slice, preview, slice, export

both 2.9 and 3.0 suffered from a stale state bug that would cause this. it’s been patched but not yet pushed to production. thanks for the report.

1 Like
11

now fixed in production