If Easel uses the safety height written into my imported g-code file, why do I still have to raise the bit when I execute the carve? My g-code files have a safety height of .25". However, to carve the file, I have to click “raise the bit” which raises the bit by the default .15" and then it adds the .25" safety height written into my g-code. That means the bit is raised a total of .40" above the work (.15 + .25). Since my g-code file’s safety height is .25" that’s the amount the router is plunged to start the cut. However, it doesn’t seem to take into account that the router was raised an additional .15" by Easel. Am I missing something here?
I don’t use Easel, but isn’t the next step to turn on the router? You don’t want that endmill spinning at Z0.
Are you saying that your job started cutting 0.15" above your work?
I’m not sure if it’s cutting .15" above the work or not as I cancelled the operation. I want to find out what’s going on before I commit. After I raised the bit and switched on the router, I hit carve and the router raised up the additional .25" of safety height written in the g-code. My concern is that once the router has moved on the X and Y to the start of the cut, it will only plunge the .25" specified in the g-code which would put the end of the bit .15" (the default amount Easel raises the bit) above the material surface. Now I am wondering if the router descends the .15" as it moves into position for the first cut. I’ll have to check.
Are you sure it’s raising .25" and not just another .10"?
Use a piece of scrap material (plywood or similar) COMMIT to the cut. let it run and see what happens.
There’s really no other way to know or troubleshoot if you abort the cut and are unaware of what happens when you let the machine do it’s thing.
It could just be the way easel works… I’ve never questioned the “rais the bit” step and not had problems with it continuing on the carve at the proper height.