I’ve been experimenting with cutting .nc files generated in Fusion360, by importing them into Easel. I’ve done a lot of carves that were successful, but today I ran into two adaptive clearing strategies that went absolutely crazy.
After setting the Z probe height correctly, the bit travelled along that Z height (after a small lift), then carved the clearing strategy at least 10mm higher than the work zero I had set.
I went back to Fusion and simulated it- no problem. I watched it in Easels simulation feature, and saw the problem happen again (virtually). I exported Easels GCode to Camotics and simulated it again, and again it wasn’t the same as the toolpaths generated by Fusion.
I have attached the Fusion generated .nc file 1 From Fusion.nc (348.5 KB)
This is the link to the toolpath in Easel
And this is the .nc file exported after it went through Easel
3 Imported from Easel (307.6 KB)
Can anyone see why the toolpath is acting so differently that intended?