Disabling all Z rapid during plunges (Feed Height not working like expected)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Hey everyone.
My shop has a knee mill with a 2-axis Prototrak CNC system. If running a .NC program, when it encounters a Z(x) position command, it prompts the operator to manually set the new Z height, then it continues the program.
We recently subscribed to F360 and I'm running into a roadblock, where I can't get the CAM to do plunges from clearance height without it splitting into multiple Z position commands (e.g. rapid down from clearance height, then G1) - which results in lots of extraneous operator prompts.
It seemed like setting Feed Height equal to Clearance Height would do the trick. Feed height "sets the height that the tool rapids to before changing to feed/plunge rate to enter the part". This implies that if it's set equivalent to clearance/retract height, then it wouldn't rapid at all, and simply start at feed/plunge rate.
The weird thing is, when this is engaged, it doesn't disable rapids. Instead, it now "rapids" from clearance height to top height using G1 at horizontal feedrate, which is baffling.
For example.
If feed height is disabled, a plunge will look like this:
G0 X0.1 Y-0.1033
Z0.1 (first op, initial position, clearance height)
Z0 (rapid to top height)
G1 Z-0.4 F42.02 (plunge at plunge feed)
When I set feed height to clearance height, I hoped it would look like this:
G0 X0.1 Y-0.1033
Z0.1
G1 Z-0.4 F42.02 (plunge from clearance in one move. feedrate is irrelevant, move is manual)
But if I set it up like this:
I get this:
G0 X0.1 Y-0.1033
Z0.1 (first op, initial clearance height)
G1 Z0 F126.06 (plunge to top height at horizontal feedrate?)
Z-0.4 F42.02 (plunge into material at plunge feed)
That doesn't seem like intended behavior. But it also seems like a bit of a 'hack' in the first place.
Is there some cleaner way to disable Z rapids? Either with configuration in CAM, or in the post?
Thanks!
The test part is here, but there's nothing special about it. this happens in multiple parts: https://a360.co/3tx6snK
