You are not logged in.
Does Vericut use values typed in to adjust feedrates as 'not to exceed' values (especially removal rate and chip thickness)?
I wondered because if I check limits after a NC optipath optimization (with constant chip thickness+constant removal rate method) I exceed a lot the ideal constant removal rate I set for optimization. I add more cuts with 0.2 resolution and however I got spikes until twice the constant removal rates goal...
Offline
I investigated and I found there was probably an issue with 'break arcs' parameter.
As I said, at some points added on broken arcs, removal rate sometimes exceeds removal rate set(spikes on graph) All is OK with 'optimize' parameter (removal rate is constant)
Offline