Bit rises after each pass VCPro 10.514

[adze_cnc]

It seems my aside to any Vectric staff reading this was misinterpreted.

Of course, the software internally must know the starting and ending points of things. That information is not made external to us though.

As Adrian and martin54 have observed the only way to get rid of those spurious Z-up and Z-down moves is to edit the created g-code file directly.

[sharkcutup]

If you are not familiar as to how this Spiral works -

It starts at the material surface and as it progresses it will gradually increase its depth until it reaches the depth set for the tool/bit in the tool database (ex. 25). It will then maintain the depth (.25") for each pass until it reaches the Cut Depth (C) setting. Just so you know it works well when you use tabs too!

Sharkcutup

[Adrian]

Sharkcutup, It's the pocket toolpath he is having issues with not the profile toolpath. When he originally posted he said it was the profile toolpath but later posted to say it was the pocket toolpath instead.

[sharkcutup]

Okay yeah I found his correction! Thanks!

Not exactly sure what now the OP is trying to accomplish so ---
I am out of here!!!

The OP is all yours Adrian! Good Luck!

Sharkcutup

[nmflyr]

Thanks to all for your help. Since I feel accomplished just to know what G code is, I think the rest is above my pay grade, so better left alone. So the final take away is that it is supposed to do that and I didn't miss a setting selection. I'm learning each time.

[Janettx]

I have the same issue and there is no rhyme or reason to it. I can create the exact same pocket in one file and the bit does not lift up each time and then on a new file with same pocket it will. It's really crazy and I think it's a bug.

[Adrian]

I have the same issue and there is no rhyme or reason to it. I can create the exact same pocket in one file and the bit does not lift up each time and then on a new file with same pocket it will. It's really crazy and I think it's a bug.

Can you post a file showing that behaviour?

[Massynrt]

I had the same question a few weeks ago - Was advised by Vectric support that the reason is:

The most of the customers is hobbyists, with not very rigid machines, they don't want to take the risk to keep the tool down as there might be material in the way.

Although I disagree with this - It is just the way it is. Very safe implementation of pocket toolpaths. it does work, just no options for optimized production workflows.

[Adrian]

That's correct as confirmed earlier in the thread but the last poster was saying that he can setup two identical jobs and on one it will lift and the other it won't hence the request for a file showing that behaviour. I guess he found the issue as there's been no activity since.