Hey, I’m new to CAM and KM but I immediately fell in love with it. Such a great product!
I have designed a fairly simple part and am trying to get ease down to work. It’s working great in preview for the main part of the work except for the first step. The tool plunges into the stock without an ease down to begin the roughing operation.
What could cause this?
the path generator requires refactoring in order to fix a few ease-down missing cases. it takes a lot of historical explanation of the code evolution, but at present, the “top” clearing of the part is not integrated into the ease-down code path. this will be fixed probably in the release after the next one.
Than you so much for the swift response. In the meantime, is there a way to let the tool plunge outside of the stock and then move into it from the side? I played with the offsets but the starting point will always remain inside the stock.
I could probably come up with a mock part that I machine before the actual part to achieve this.
As of now, there is no way to start from outside the stock. I’ll get started on a fix today, and as Stewart said, it will be in a release soon.
I have good news actually. Your ease-down issue seems to have been solved in release 4.2!
You can go to Grid.Space Chooser to change your version.
Hey! I noticed that it works after the first step down. However, the first plunge from the top of the stock is still vertical and not easing down if I read the G code correctly.
I have been struggling with this issue myself. Good to know that hopefully it’ll be fixed in an update and it’s not me not understanding the software.
The work around I’ve been using under Overrides setting zTop to be just Above my stock so the first step down is just above my stock. if it’s 9 mm stock and 3mm step down I set zTop 12. Takes a bit more time cutting into the nothing for the first pass, but at least saving my drill bits.
interesting workaround. thanks for sharing that.
I found this interesting…I tried to find it in my account settings…after I changed it…I guess I will have to look out for the update notices and save this link?..Is 4.2 considered beta?
there are some large-ish changes under the hood that I want to let shake out before promoting it to the default version served.