![]() ![]() Perhaps slowing the head down the first time it crosses the z=0 threshold in case I've had a brain-fade and started running a finishing strategy on some uncleared stock. There's a question there about the right balance between protecting the machine, opening it up to the option of running it without the protection of having to include a clearing tool path in the top of the file, yet not lumbering myself with overly slow rapid substitutes. I need to go away and think about what to do in my post-processor adaptation. The settings on the linking tab don't provide that option and, as far as I can work out, simply select the highest of the feed rates specified. In the 3d contour disable contact point bounds and set tool containment to outside boundary also tools not long enough. Safe distance in 2d contour was over an inch, dont know why. The settings on the post-processor also allow you to specify a feed rate to substitute in when replacing the G0s - this is a handy feature. Problems are shaft and holder pull away enabled, shaft clearance was. I found the high-feed mapping settings in two places - on the linking tab of the contour tool path settings, and also in the (Built-in) properties of the post-processor. to test a different finishing strategy on a piece that has already been cleared, so I looked into the high-feed options that you suggested. It then struck me that there may be times that I'd like to override this feature e.g. Ive made 2 example files that illustrate the issue. I completely take your point about needing to run a clearing strategy before using a finishing one, but I wonder if it is worth looking into building this sort of protection into Fusion too? I think novice users like myself might benefit. Im having big issues with getting Fusion 360 to export a 3D contour as G2/G3 arcs in post-processing when my stock is large and my origo, therefore, is far away from the 3D contour operation. All pretty sensible - it stops people slamming the head into the stock. If there have been some cutting movements but it believes that you are trying to complete a rapid movement into the remaining stock, it throws the error ' cut too deep/tool collision'. ![]() If the area hasn't been cleared first, and the rapid movement comes before a G01/G02/G03 or other cutting movement has been made, it throws the error ' cut made without a feedrate'. By producing a g-code file which first adaptively cleared some stock before running the contouring toolpath, I learnt that the Boxford simulator will allow rapid movements into the area that has been cleared, regardless of z level. I have done some more testing and have a clearer idea of what is going on.įirst things first, I'll clear up the point about the z level - I was mistaken. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |