Pocket Toolpath - drilled extra holes at start? (2024)

Version 12.005

I have a pocket toolpath to route away a good chunk of material. Max depth is set to 1/2 of my material thickness (4 passes to cut away 3/8" of material). The preview looks good. However, when the toolpath started it moved to the start point and plunged all the way through the material, moved about 1/4" along the vector and then raised back up to the proper depth. The rest of the toolpath has run as expected.

The project is only a template so not a finished product, so the holes don't break the piece. Has anyone encountered this before? I didn't change any settings that I'm aware of.

Picture of said bug hole:
https://drive.google.com/file/d/1sc5OTl ... sp=sharing

[Admin edited title as shown not to be a bug in the software]

Was the hole visible in the preview?
If not then it is likely a machine or setup issue.
If the hole in the preview please upload the .CRV file.

To upload a file/photo:

• Click on the Upload attachment button below the message area
• Click on Choose File and select your file
• Finally, click on Add the file to upload it to the forum

If the file is too large to upload here you can use a file sharing site such as drive.google.com, onedrive.com, or dropbox.com. They all have free accounts available

• Upload the file to the file sharing site
• Make the link shareable
• Share the link to the file here

For screenshots please use the Windows Snipping tool. These are far easier to read than photos taken with your phone.

On many Windows systems you can also use <Windows-key><Shift><S>

Where did you Z-Zero at the Start of the Pocket Toolpath -- Machine Bed or Material Surface?

Sharkcutup

I don't see a problem with the G code.

When I look at the code generated for the pocket using the 1/4" end mill it does the gradual ramp down to Z-0.093750, which is what I expect. I do not see a too-deep plunge .

Can you ZIP and attach the g code file for the pocket toolpath so we can compare results?

 [TOOLPATH NAME: Pocket 1 [Clear 1]] F40 XY [SET FEEDRATE FOR X AND Y] F10 Z [SET FEEDRATE FOR Z] G0 X6.000000 Y6.816250 G0 Z1.010 G0 X6.000000 Y6.816250 Z0.200000 G1 X6.000000 Y6.816250 Z0.000000 G1 X6.080195 Y6.812301 Z-0.003764 G1 X6.161741 Y6.800065 Z-0.007629 G1 X6.243374 Y6.779123 Z-0.011579 G1 X6.323717 Y6.749314 Z-0.015596 G1 X6.401339 Y6.710768 Z-0.019659 G1 X6.474839 Y6.663922 Z-0.023744 G1 X6.542925 Y6.609505 Z-0.027830 G1 X6.604488 Y6.548506 Z-0.031892 G1 X6.658662 Y6.482108 Z-0.035909 G1 X6.704862 Y6.411623 Z-0.039860 G1 X6.742795 Y6.338408 Z-0.043725 G1 X6.772449 Y6.263792 Z-0.046875 G1 X6.742795 Y6.338408 Z-0.050639 G1 X6.704862 Y6.411623 Z-0.054504 G1 X6.658662 Y6.482108 Z-0.058454 G1 X6.604488 Y6.548506 Z-0.062471 G1 X6.542925 Y6.609505 Z-0.066534 G1 X6.474839 Y6.663922 Z-0.070619 G1 X6.401339 Y6.710768 Z-0.074705 G1 X6.323717 Y6.749314 Z-0.078767 G1 X6.243374 Y6.779123 Z-0.082784 G1 X6.161741 Y6.800065 Z-0.086735 G1 X6.080195 Y6.812301 Z-0.090600 G1 X6.000000 Y6.816250 Z-0.093750

The G code you supplied is correct. This means it is not a VCarve/software issue.

Was this a one-time occurrence, or does it happen every time you run the file?

THIS is exactly why some of us are critical of those who insist on posting the word BUG in the title of a post.

There was no bug. Yet a guest browsing this forum thinking about buying the software is left with the impression that a BUG exists.

That does not help Vectric, yanno, the ones who provide this forum?

Rcnewcomb wrote: ↑

Sun May 19, 2024 6:36 pm

Was this a one-time occurrence, or does it happen every time you run the file?

I just ran the start of the file twice more and no, it didn't do the weird plunge either time. So was a one time thing. I've reached out to OpenBuilds to see what they have to suggest.