Empty NC file after saving GCode

Downloaded CC B530 today, made a basic pocket tool path to resurface my machine (SOPROXXL) to .05 in. depth and 30in. x 30in. on XY respectively. One thing is that the simulation feature doesnt work, and second, after saving the Gcode the file size is just 1kB?

this is what the G code looks like after saving it…
while running the code it just prompts me to change tool, then to start the Spindle, then it goes to the zero XY and nothing else happens… any idea?

Please post the .c2d file?

Surfacing.c2d (6.0 KB)
I think the problem might be I’m setting the Start Depth = Max Depth? which I did on purpose given the Max depth is .05 in.

This is exactly what happens here quite a lot. After that the machine goes back (very slowly) to the homing position before you can do anything else. Frustrating. This in combination with the crash when using the simulate option I have decided to wait for the next updated version…

Yes, exactly that (reproduced it on my machine). Just setting max depth to 0.0501 for the sake of testing produces the right gcode.

It seems to be a corner case where CC should rather not display at toolpath at all and produce an error, I can see how this is misleading.

However I don’t get while you would want to set start depth = max depth anyway ?
I you need to shave off 0.05", set start depth at 0 and max depth at 0.05", and zero off the wasteboard ?

1 Like

Not an edge case — there simply isn’t a cut to be made if start depth == max depth.

Apparently the generation of the first pass is done before the start depth is compared to the max depth.

The 3D preview shows no cutting or rapid movements:

so at least that verification matches EDIT: or would have, if the 3D preview had successfully been shown.

Is this the correct interpretation? Start depth can be below the stock surface - surely it’s okay for it to be the only depth required.

image

Given this, if S==D and S!=0, surely it should pocket out to a depth of S?

EDIT: Scrap that. I see what you are getting at. I still think it’s useful to pocket out something in this fashion as a finishing pass.

I suppose you could pocket start=.0499 end = .0500. I’d guess that would do something.

EDIT: Confirmed.

1 Like

It is, but in order for a cut to be made, max depth must be greater than start depth.

If it isn’t the algorithm would get in an endless loop at the bottom of the pocket.

Hmmm… I think the algorithm needs to be implemented using a repeat-until rather than a while loop, then.

Good point, should have said could, rather than would.

This topic was automatically closed after 30 days. New replies are no longer allowed.