Jump to content

Planner - Collision Detection


Recommended Posts

I'm running Planner 2020 and using collision detection. My computer graphics slow way down to a crawl. My laptop fan, which normally sits pretty idle, starts flying during this process. The second I uncheck collision detection, everything is fine.

Attached is a screenshot from task manager. The red arrow shows when I started the simulation. The CPU and GPU don't appear to be working too hard but I could be wrong.

I also notice that the machine model appears when I turn on collision detection and I don't believe I've ever seen that before.

Any ideas on what might be happening?

Thanks in advance.

Screenshot 2021-01-27 080048.jpg

Link to comment
https://qualityforum.zeiss.com/topic/12810-planner-collision-detection/
Share on other sites

Please sign in to view this quote.

Some motion speed improves but that sort of defeats the purpose of the slider in some cases. The slider speed also improves the collision detection process as it is checking to see if parts of the probe occupy the same voxel as the model, thus creating a collision. If you run the simulation too fast, the collision may not be detected due to the speed of screen refreshing.

Please sign in to view this quote.

But be aware that this is not just a speed setting, but also sets the accuracy of the collision detection! Highest speed = worst accuracy.

@Tom:
A similar issue already occured a few versions back, I don't remember which it was. Simulation in general (not only collision detection) was terribly slow then. But it was fixed in some service pack. Wouldn't be the first bug to be reintroduced. So I'd suggest to file a support ticket on this, hopefully they'll be fixing it again.
It's normal that the sim temporarily slows down when the stylus dives deep into more or less complex geometry, but it shouldn't crawl all the time.
  • 2 weeks later...
Its not just you. Norbert is right, a few versions back there was the same problem, collision detection was terribly slow. It was fine in Calypso 2019 and now in Calypso 2020 its even worse than before. I am patiently waiting for a service pack, bit its taking unusually long this time.
For the life of me I can't get my RDS simulation to actually touch the part. I enter the offsets given from various posts, and my MasterProbe is always floating slightly off of the part. I have frankly given up on getting it to touch the part and just use it to gauge navigation moves. If I use Collision detection while I have this weird offset, it goes haywire, so I simply can't use it.

Edit: I should mention it's not just the MasterProbe, but I figured I would try that first. Other stylus systems are just as bad, if not worse.

Please sign in to view this quote.

The offset changed in either 2017 or 2018.

This is the correct current offset.
659_ae1b39295506c855b7aaa8faaf1dea5e.png
Also, make sure when you are build the stylus system inside of SSC, you start with the "Probe adapter RDS-XXT 18p" first. This includes even when you build your MasterProbe for import reference.
  • 3 months later...

Please sign in to view this quote.

Never noticed an issue with that until I went to qualify a probe holder location on the rack.

Here's something i've done in the past. Load a model like the cadcube model. Load the MasterProbe. Start stylus simulation. Under plan, go to Travel to Nominal Position. Load X-10 Y10 Z2.5 and Execute. I test it in all 3 axes.

Screenshot 2021-05-14 152758.jpg

  • 3 weeks later...
Hello everyone,

I am working with the Planner feature and it seems like I am not getting an error message when my machine hits the probe rack. I purposefully put it in the way of my machine to see if it would pick it up. Is there a way to make the probe rack something that can be picked up as an object like a CAD model of a part?

Thanks so much!
×
×
  • Create New...