NC Collisioncheck

m_ohm — Fri, 24 Apr 2020 07:00:44 GMT

Hello everyone,

we have the following problem here:

We always check every toolpath for collisions and model damage. Since we also operate in the 5-axis range, we also check collisions in the machine room. We are currently doing this via the "Simulation Problems" window.

Unfortunately, everything did not help and we collided. After some research we were able to find out that our OptFile does not seem to be compatible with the last PostProcessor update and 2 values were swapped during prepositioning (or something simelar).

Now, in my opinion, it is relatively difficult to consider all eventualities when updating. However, the fact is that a collision can quickly cost a lot of money. So I wonder:

I know there is an NC program exam. Is the OptFile also taken into account in this? Or does it "only" simulate using the data in the MTD file?
Is there a way to detect a faulty output (collision) of the NC programs (after postprocessing) in order to rule out a case as I described it?
How do you handle that in your company with regard to updates and collision avoidance?

Kind regards

Mark

Re: NC Collisioncheck

LasseFred — Fri, 24 Apr 2020 11:58:17 GMT

As far as I know, Powermill does only check if your toolpaths collides with the MTD File.
you will need a program called vericut to check your postprocessor/NC-programs in.

Here is a link to vericut in powermill: https://www.youtube.com/watch?v=GCAYgbdCgOE

Re: NC Collisioncheck

HMC400 — Fri, 24 Apr 2020 12:28:05 GMT

There is also Eureka which checks the nc file generated by the Postprocessor

https://www.youtube.com/watch?v=otNhNK2kgXo

topic Re: NC Collisioncheck in PowerMill Forum

NC Collisioncheck

Re: NC Collisioncheck

Re: NC Collisioncheck