anyone know why this seemingly takes so many detail passes? what can i change? its like taking 5- runs at the tiniest details…
1 Like
so whats happening is it does the vbit areas that it cannot connect to other areas, then comes back and does the last bit of that areas perimeter, then comes back and does that areas wall corners to get the corner crisp. So 3 passes is the most I count anywhere with the vbit…
There isn’t much that can be done about the multiple re-visits to the same area besides re-writing the Easel algorithm for this specific project…
However IF the desire is to expedite the carve you could use a smaller endmill like a 1/8" instead of the 1/4"
Here I’ve swapped the original 1/4" (Right Side) to the 1/8" (Left side) and was able to shave off 11.9% of the carve time
OR you could increase the Vbit stepover… Here I’ve changed the Vbit stepover from the 1% default to 2%… (Endmill was left at 1/4", the ONLY thing changes was the vbit stepover %)
Doing both in this instance doesn’t actually make it any faster though. BUT it is an option to also keep in your toolbox to check the times on a different project…
One more thing to shave time is reducing the safety height IF you can get away with it, I use a 1mm (0.04") safety height and that change will also shave off another minute or 2 from each bits time…
1 Like
Thanks, Seth.
I also wonder if you can limit the jumping around so much in the rough pass? It goes left to right to left to right why not stay on the same side? Is that an algorithm thing too?
1 Like
Exactly, they really face some tough choices in setting up the software algorithm as to whether it uses a basic method of tool pathing, which might be top to bottom which might throw the machine around in that left and right pattern you’re seeing, . . . OR whether they rely on the user’s PC’c processing capabilities to calculate multiple methods and select the most efficient one (this is what some of the other more PC Spec heavy software like Vectric, Carveco, Fusion360 do, which means if your PC doesn’t meet the processor Specs than your SOL and cannot use the software at all)
Instead Easel is running very processor light (vs those others I listed) and uses the first toolpath that it comes up with instead of looking for the most efficient.
Kind of a trade off for a more user friendly software, catering to the vast majority of users, even those out there running cheap $100 notebooks… (even my phone can run Easel to some extent… it can even process simple toolpaths)…
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.