Offline Planner - Collision Detection

[[Ni...]]

I am having trouble with an offline planner detecting what clearly should be a collision. For a bit of backround these are new stylus' I have built up in the SSC software. Zeiss does not provide appropriately modifiable generic styii so in the example below the 'shafts' of the stylus are made from a combination of generic cylinders and generic cones. The only 'stylus' component in the build is the 2.5mm tip.

Is there a setting or something I need to do to have the planner detect what is shown below, as a collision, with a custom stylus. If there is not something I can do, does anyone have an explanation as to why the simulation will not detect what is shown below as a collision as it would be good to be able to explain the situation to my coworkers when I flow down these models to them..

 

[[Ri...]]

I think the speed you set prior to using collision detection has an effect on this.

When I am unsure and worried about contact, I set the speed very low.

In some cases, lower than the sample image attached.

[[No...]]

If you want the highest rate of detected collisions, ALWAYS set the "speed" slider to the leftmost position. I put the "speed" into quote because I think it's not the best way of  thinking about that setting. It doesn't just control the visual speed of the simulation, but directly determines how accurate the collision detection will be.

What the speed slider does is set the "width" of the gaps between each movement step. It's like a stop-motion animation: The machine is put to position 1, then possible collisions for this position are calculated. Then it's put (not "moved") to postion 2, collisions detected again, and so on. Inbetween these steps of movement the simulation is "blind" and will miss possible collisions. By moving the slider to the far left, you ensure that the gaps are as small as possible, i.e. the detection rate is highest. But I guess there might still be rare situations where a collision is missed nonetheless. 

However, in the screenshot above, I'd rather say it's some kind of glitch with the correct detection of all stylus elements. I don't know if there is anything you can do about that.

Edited March 27, 2025