Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.
First time visiting? Here are some places to start:- Looking for a certain topic? Check out the categories filter or use Search (upper right).
- Need support? Ask a question to our Community Support category.
- Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
- Be respectful, on topic and if you see a problem, Flag it.
If you would like to contact our Community Manager personally, feel free to send a private message or an email.
INTERFERENCE DETECTION
Maxi
Member Posts: 1 PRO
Hello,
is there a tool for Interference Detection in On-Shape similar to the one in SolidWorks ?
is there a tool for Interference Detection in On-Shape similar to the one in SolidWorks ?
4
Answers
Owen S.
HWM-Water Ltd
Onshape, Inc.
It's super frustrating to still have to eyeball it via the cross-section tool after so many years.
Ideally, an Interference Check button would do a live calculation of the current assembly, and display a list of volumes that are the intersection between any two parts. Clicking on any intersection should zoom to it, and make all other parts transparent. Finally, there should be options to "Approve" interferences that are due to imperfect models, to "Flag" interferences that will prevent a release without the interference being eliminated (via redesign) or approved (via review).
Thanks for all you do.
For me, this is the number 1 reason not to use OS
I haven't used ID (tried it a few times in SW, but it usually is a long list of fasteners) Found it much easier to pay attention to what i was doing the first time ;p jk
But really, it is a pretty clear image even looking at that photo on a cell phone screen. What else do you need it to do? Should the section view draw a large red circle around those also?
Maybe it could me an opiton to turn the circles on and off from the plane selection window?
Would then need to determine where the interference was. Similar loop with Boolean intersection loop? Show the ghosted ice view with the solid intersection parts under it and we can see the locations of the interference.
O.S.
HWM-Water Ltd
Something like this? https://cad.onshape.com/documents/2ee680cb5e9314e2b06e9f94/v/547b09709575a33c24a3c5f0/e/7b52f0ffc178ad83f6810685
To use, just create a new part studio in-context, add this feature, and select all bodies. Also works in a part studio without in-context stuff.
I'm not sure what the best UX is -- how to report interference, what to leave, etc. -- this is just a guess (i.e., this feature deletes all bodies that don't interfere) so I'm looking for improvement ideas.
Firstly let me ask you a question? Was this fun?
If yes, then OK, otherwise please ignore anything I say at the weekend, you folks deserve a break! Nope, not something like that, exactly that, that's perfect! In 100 lines of FS you've created a feature that is useful today. OK. suggestions...
Before PT was kind enough to visit I'd have come up with ideas that would take a dept. a month to write, so I'll limit to stuff that is achievable and can be iterated upon. I'm trying to think of stuff now that can be built with existing tools, or small additions to them, not blue sky stuff.
Short term improvements:-
(a) Option one is don't change a thing, this is useful today exactly as it stands.
(b) Name the new bodies something helpful, like "interference Solid", and perhaps the name of at least one of the original parts that it was created from.
I wasn't thinking big enough. Now you've done the finding it can also be used for the fixing! Squirt the new bodies back to the assy, another ICE to boolean them away from whatever part caused the interference and you've not only found the interference but you've fixed it too!!
Mid term improvements:-
(c) We have a part property "Exclude from BOM", I propose a similar one "Exclude from Interference Checker" that will allow us to suppress false positives from stuff that is meant to interfere. Standard content comes to mind. This would have a checkbox in the feature UI as we might want to show that interference after all, to see we have the right size bolts for example. Perhaps show "expected" interference in green solids and unexpected in red?
Long Term:-
(d) Add an icon to the or right click option in the assy to create the new ICE studio, call the FS and populate it with all the parts from the assy. (old topic so I won't bang on about it but we want an "add everything when you rebuild option" not just a "add the part I clicked on when i first ran the feature" option. A bit like adding a live part studio to an assembly not just what was in it when we first clicked on it.)
(e) Be able to accept contexts as a parameter of the feature. Thinking of the folding step stool example used in your webinars... We have one context for open, one for closed and feed them both into your feature. This creates the solids to subtract from the tubes to allow it to fully open or close without any sketching, extruding etc and it's still fully parametric. This is so cooool!
(f) Get some sleep.
(g) OK getting carried away now. Perhaps have it automatically run as a background process in any new assy built, with a screen indication if there is interference?
Right, enough waffle from me, I'll just say thank you again, and leave you in peace for a while.
Cheers,
Owen S.
HWM-Water Ltd
Just goes to show that there is no problem that can't be made more complicated by thinking about it.
Cheers,
O.S.
HWM-Water Ltd
Good news, it does, and you can
https://cad.onshape.com/documents/e6714096ca4b2697b60a4fa8/w/179874f12c9ade40d5dd8880/e/3f26f4443eab2dd764d2577b
At least from the assembly. I couldn't get it to cooperate from an active, finished, or copied in place sheet metal part, but from the assembly all was good
Cheers, Owen S.
HWM-Water Ltd
HWM-Water Ltd
I don't see how to add the script in an assembly, what am I missing please.
Your example works and its amazing. Very nice, thanks!
Cheers Owen S.
HWM-Water Ltd
https://cad.onshape.com/documents/4ef9d7bf5c04de6c159e6fb0
Forum Comments:
https://forum.onshape.com/discussion/comment/39961/#Comment_39961
https://forum.onshape.com/discussion/comment/44684/#Comment_44684
IR for AS/NZS 1100
HWM-Water Ltd
So in an assembly I can right click one part and edit it in context. There I can add the Interference Check feature script. But selecting the only part I can, results in an error because "active sheet metal models are not allowed"
Use the create part studio in context toolbar button
IR for AS/NZS 1100
HWM-Water Ltd
IR for AS/NZS 1100
What an incredibly useful feature. Well done!
Owen S.
HWM-Water Ltd
V3 should work on sheet metal also and parts are named "Interference volume" -- naming them in terms of other parts is not possible with FS changes alone because FS can't access current part names. For the same reason "excluding" is not easy to add based on properties.
For exclusion, that's why I made it selection-based, so you could just not select it, or you could have a custom feature tag stuff with attributes... Neither is ideal. I'll think about this further.
I totally forgot that Jake wrote a similar feature a few months ago -- https://cad.onshape.com/documents/4ef9d7bf5c04de6c159e6fb0/w/50103cbdb65f20d04d6f68f1/e/8dba900c665b639f1b1bab53 with slightly different design decisions.
Finally, please keep in mind that this is a workaround -- we intend to have a more native interference checking solution in the future.
Even more finally, of course this is fun! -- the whole point of being at Onshape is getting to improve everyone's design experience. Quick solutions to unblock useful workflows (like this) are very satisfying.
HWM-Water Ltd
So V4 fixes the typo you pointed out. Rather than renaming the feature automatically (which could be done somewhat, but has drawbacks, such as the user wouldn't be able to rename the feature manually) and rather than doing a dropdown, I added another option, to warn if interference is found -- the feature turns orange if that option is checked and a collision is detected. If none of the checkboxes are checked (i.e., the operator error you described that could cause interference to be missed) the feature errors, turning red.