You are not logged in.
We program in Powermill with 0.05mm collision avoidance on toolshank, and 1mm on toolholder.
So now, if we do not want plenty of errors, we should change the HolderStockNearMiss value below 0.05. It is nonsense.
The 0.5mm is good for the toolholder, but not for the tool shank.
And then, it would be great, if we could filter the errors.
Offline
Trying to clarify the problem.
Are you saying your tool shank is being defined as a holder when imported from Powermill?
If this is the case then we agree. I think the fix is that Vericut needs to support a "shank" definition again, as it did many revs ago.
Many interfaces into Vericut define the shank as a Holder and this just doesn't work right with collision checking. Often we want .1"/2.5mm clearance for the holder, but 0 for the shank. For a ground down shank .001"/.02mm.
Last edited by vhubbard (2016-06-29 14:16:41)
Offline
I agree, we have this problem too...
Vericut show messages like "Near miss error" when you are boring with a reamer????this really doesn't make sense....
To "solve" this problem, I simulate many times with near miss 0,5 mm (default here) and then reduce the value for 0,05 to see if you forgot any error...
The best solution is divide near miss error in 2 options as you said above....
Send this request to Cgtech, and give us the SCR number, then we can ask for this too...
Igor Freitas
CNC programming
GROB - Brazil
Offline
Thanks for both Your responses.
First we transfer tool shanks as a holder, but in this case we had to lower the near miss value.
CGTech staff suggested to define shanks as a tool (so not as holder) with 0.001mm cut length. I have modified the interface, and now we use this way. Seems Ok.
Offline