Build 644 is great, some real improvements, but the introduction of not allowing a vbit to pre-carve/pocket on advanced carve is a step backwards.
I’m using a custom build cnc, so only use this software for its brilliance and simplicity, but removing this is forcing me down a road I don’t want to go with bit changes mid run. The idea of this makes me want to cancel my subscription and look elsewhere. A lot of my work is using bits and advanced v-carve for flat bottomed v-carve. I now have no way to even fudge the software into thinking I’m using a vbit for this as the end mill will program a far different toolpath to a vbit, I use flat bottom bits with a stopover of 0.1-0.2mm to get a perfect finish on my work.
Thanks for the feedback Chris, we’ll definitely take that into consideration. We’ve only seen support problems with people using a V-cutter as a mistake and generating really long toolpaths.
For now, you could create an endmill with a small diameter, maybe .01" or so, and then use a stepover of .005" for the pocketing. This should closely emulate the prior behavior (unless I’m missing something).
Are others intentionally using the V-bit for pocketing in Advanced V-carving?
Hi Rob, thanks for reply, I get if your selecting the pocket only tool path you’d want this, but for the advanced vcarve defo need this as an option, and I guess depending on the size of the job you may want to pocket really quick, so also need to be able to select endmills as well. I do a lot of coasters so need this for finer work.
Even fusion 360 can’t do advanced vcarve like your product, you have a niche market with this! Defo keep it as it was in previous build
On a slight different note to this very same tool path type, for users whom do not use your machines, when you select advanced v-carve and use a different tool for advance v-carve pocketing, eg a larger tool for speed, say 1/4 end mill, then a vbit for finishing, when you save the gcode it obviously save the whole tool path, then in code causes a pause on machine cut to change bit. For none carbide machine users, we are unable to change the tool mid run and re-zero bit, is there a way to add an option to save gcode for pocket clearing with one bit and another gcode for the vbit work, in other words the 2nd code will know where eh first code tool path has run, and carry on from there? LFC Gates.c2d (788.2 KB)
I’ve attached an example, for me, the only way I can run this file is manually amending the gcode, splitting into 2 files, one for the larger bit and one for the vbit finishing, doing it manually creates risks if you don’t know what your doing, adding this as another feature would be a really good addition for users who don’t use your cnc’s.
I run an open builds black box and custom build cnc, with a probe, so being able to save advanced as two gcodes and probing each bit will ensure an accurate cut.