Problem with G code Generation with KrabCAM

Running a test run with a file generated by KrabCam when the Maslow z access went to the top and beyond then came down and tried to drive the bit through the baseboard. After a reset I had a look at the generated code and found it had added a number of G0 z37 entries which caused the Z access to rise all the way up, messing up where the Maslow thought the z access was. A sample of the code is below:
g21
g90
g17
g40

m3 s10000
g0 z4
g0 x283.99268572 y142.15474799
g0 z0
g1 x283.89945546 y137.1559071 z-0.5 f400
g1 x283.99268572 y142.15474799 z-1 f400
g2 i-134.06110119 j-0 x247.42022442 y50.13114263 f400
g0 z37
g2 i-97.48863989 j92.02360536 x244.72709827 y47.35923425 f400
g2 i-94.79551374 j94.79551374 x243.20539513 y45.8615753 f400
g0 z0
g1 x239.54997095 y42.4505672 z-0.5 f400
g1 x243.20539513 y45.8615753 z-1 f400
g2 i-93.2738106 j96.29317269 x149.93158453 y8.09364681 f400
g2 i0 j134.06110119 x55.13607079 y47.35923425 f400
g2 i94.79551374 j94.79551374 x15.87048335 y142.15474799 f400
g2 i134.06110119 j0 x27.80458581 y197.44828319 f400
g0 z37
g2 i122.12699872 j-55.2935352 x30.40075553 y202.8569701 f400

I think it may be related to the tabs. Overall I am impressed with KrabCAM, just will be checking for this before running a job.

That will be an error in their gcode generation. GCodeClean can fix that

1 Like

@ian_ab if you can share a screenshot of your toolpath settings, then I will have a look.
Specifically I’m interested in:

  • targetDepth
  • safetyHeight
  • stepDown
  • tabHeight
  • attackMethod
3 Likes

Thanks for the fast response, I think it must be user error as I have not been able to duplicate the problem.

1 Like

Maybe 40mm instead of 4mm in tabHeight or something?
Just a wild guess :slight_smile:

I should probably add some validation for those values.

btw. There is an option to turn on comments in the gcode in the save dialog.
If you turn that on, your gcode-file will contain info about the toolpath settings.
I’m not sure what comment style the Maslow supports though.

KrabzCAM supports these two formats:

( comment )

; comment

1 Like

Setting TabHeight to 40 did duplicate it so that must have been what I did, thanks again for the fast responses. Going to try the comments and see which (if either) work with the M4.

1 Like

Comments appear to be ignored by M4, both ; and ().

2 Likes