Hello all! I’ve searched the forum but I cannot seem to find anything that quite matches my issue. My dad and I recently purchased a Pro XXL and have been trying small, simple projects to get a feel for the machine. Basic shapes using the end mills and ball mills have been going great, but we’re running into issues with the vee bits. When cutting a vcarve toolpath the bit seems to always start too high, and doesn’t actually cut deep enough into the wood (compared to the simulation in Carbide Create). Here are some photos of the most recent project with the issue.
As I said, the endmills work just fine and the issue only appears to happen after switching to the vee bit. Here’s the process we’ve used (from the time the Pro XXL is turned on it is not turned off or disconnected):
- Connect the computer, turn on the machine and initialize it
- Use the change tool function to load the BitZero probe. The machine then checks the height with the BitSetter.
- Run BitZero probing routine, lower left corner setting. We make sure that the BitZero is set on the wood so the corner of the material is aligned inside the recess properly. The probe sucessfully zeros the x axis and y axis within the hole then zeros the z axis by touching the top of the BitZero
- Change bit routine to load the end mill. The machine then checks the height with BitSetter.
- Load the job and start. We click continue on the tool change since the end mill is already loaded. Once again the bit height is checked with BitSetter.
- The job starts. We watch with glee as the end mill does its thing and makes beautiful cuts!
- The machine prompts us for a tool change. We load the vee bit and the height is checked with BitSetter (the vee bit is shorter than the end mill)
- The VCarve toolpath starts. There are some moves/passes with the vee bit that should cut the shallower details in the wood, but instead they float over the surface. Likewise the deeper cuts don’t go deep enough.
- The job finishes. We look at it scratching out heads because the VCarve looks nothing like the simulation from Create.
Anyone see this happen before? Any insight or advice would be appreciated!
I’ve also attached the actual create file:
Tree Sign - James.c2d (206.3 KB)