You are not logged in.
Pages: 1
I'm using Vericut for collision checking of new probe programs for a large gantry mill with an 840D control. We have the probing license and for the most part everthing works great. I do however get false errors at times while probing holes. This is happening in several of my project files. These parts are large rings with over 100 holes repeated around the part. Out of those 100, 95 or so will probe fine, the other 5 randomly placed around the part will trigger an error (Probe Tip of the tool collided with stock) I'm taking 3 to 5 hits per hole and usually if the first one triggers an error the other hits in that hole do as well. The probe light appears to be active when taking probe hits so I don't see why it creates an error when it should be taking the hit. The holes that trigger errors are not programmed any different then the ones that don't and when I zoom in on the hole I see no visible issues with the part or tool.
I've never seen the machine have a problem at these error location once the programs been brought out to the machine. I realize its better to see something in Vericut that proves not to be an issue then to see something on the machine that I missed with Vericut but I hate having a long list of errors in my logger window.
Any ideas on where to look to fix these false errors? Could my models be the problem...they look ok.
And if it helps, I'm using both version 6.2 and 7.0. I have the same issue in both versions.
Offline
are you using vericut to write the probe routine, or software from another company?
Mike
Hoppe Tool
Offline
Outside software, PC-DMIS
Offline
We have similar problems at times. I was told if the surface wasn't "normal" to the probe tip it could cause this. Normally we see it in Z on a tilted surface and the error is on the move away. Might be the luck of the stl surface definition in the hole, possibly hitting 2 surfaces simultaneously. If you can, send the files to CGTech and they can make it better for all of us.
As long as the Touch Macro is active it shouldn't matter how it was programmed. We have been using PC-DMIS NC and running Vericut to check the path. We do have trouble when the stl file is corse and holes are not defined well enough.
Offline
Thanks for the comments,
I may be hitting two surfaces of the STL at once or something to that effect... My parts are pretty big and in trying to keep the file sizes resonable I may be loosing some of the resolution.
Offline
Pages: 1