Right now the only way to ensure the machine doesn’t hit either work-holding or parts of the material that are higher is to have a retract height that is higher than all obstacles.
This can lead to much increased machine time, since Z feeds really are not all that fast.
I would like to be able to create geometry (even if it is only simple regions like circles or rectangles), and then mark them as “No-Go” regions. CC would then route around them, and ensure rapids do not pass through No-Go regions. Or have No-Go regions on a layer, and be able to designate that layer as the No-Go areas.
EDIT - as pointed out below, there would probably also need support from CM. A tool change could hit work-holding even if CC avoided all that. Perhaps a setable ‘Safe Point’, where CM goes to that point first, then the BitSetter. After, go to the ‘Safe Point’, then head into the work area. Yeah, it’s simplistic, but most of the time I’ve found it’s pretty easy to find a location that is ‘reachable’ from the entire project without hitting anything.
EDIT #2 - as I think about it, CM changes may not be needed. When CM is commanding motion that isn’t in the file (for example, tool change), it travels very close to top of travel. I’ve never had a project where that was a problem. I’m sure it has happened, but it seems like an edge case.
I like this request as a Carbide Create feature. I’ve had issues with my Sweepy body making contact with clamps and destroying the piece and also being unable to utilize my CNC because of irregularly shaped pieces that had high points - this feature would help a lot.
It also got me thinking. It seems, if we had the ability to define “No-Go Regions”, there would be opportunity for MOTION to utilize them during bounds checking. For example, How do you know where to put the clamps? Could Carbide MOTION move the gantry to the identified “No-Go” locations, so you can place your clamps or confirm the location of obstacles? There have been requests for a “FRAME”-like request (LightBurn terminology) which jogs the gantry around the boundary of the cutting area, fully retracted, to help you confirm there are no obstacles. It seems this could be part of that feature if “No-Go” zones existed?
I’ll write this up as a separate request for Motion after I think it through a little bit.
I agree that this would be a highly useful function - however it would not be absolute.
Some of the machine motions are determined by functions programmed into the motion controller & CC has no control over them nor can it pass no-go-defined regions to the motion controller. This may be possible with a future controller upgrade but the current controller hardware is essentially fully utilized from what I understand.
Setting No-Go regions in a CC design which then get violated by the start-up/shut-down sequences of the motion controller would create havoc for users & a nightmare scenario for C3D to try to support & clarify.
I use that concept in Fusion to avoid part surfaces or other geometry ( radial and axial clearance).
This alters the path generation as needed ( most of the time ).
A safe height sets the Spindle height.
CC could do the same.
This path or any other is processed by the controller with it’s own rules.
The only problem I have run into where the controller was involved was trying to handle TOO tall of stock (Z axis transom interference ). I thought I was careful, I knocked the stock off moving to change tools. Oops