When i try to open up Solidworks assembly file (SLDASM) in Inventor, why does all the parts gets unconstrained? Those files are constrained in Solidworks but some where in the transition, things get unconstrained. is there a quick fix for this?
Thanks !!
AFAIK, no 3D CAD software will allow you to keep constraints when exporting from one product to another. No fix is available.
Hi Aventador2011,
Typically when working with translated assemblies, I'll just ground all of the imported parts in place so they won't move, and then unground and properly constrain the ones that are intended to move, or that need to be modified.
I hope this helps.
Best of luck to you in all of your Inventor pursuits,
Curtis
http://inventortrenches.blogspot.com
That should be a defaulted-on user switch when opening non-native assemblies: ground everything, so it's not like a hand grenade going off.
Thanks all for your feedback.
The solution in the future should be "to keep the constraints in data translation", but "setting all grounded" is not the direct solution from my perspective. Since we can choose all components and set them all grounded together and it's very straightforward to achieve, I am not quite sure how useful such an option should be...
Thanks,
-Austin
FYI
the ground & root tool from the productivity menu is flawed
Not only does it ground your parts, it adds flush constraints to the parts origin planes, this will add huge overhead to your file sizes.
@AustinLiu wrote:Thanks all for your feedback.
The solution in the future should be "to keep the constraints in data translation", but "setting all grounded" is not the direct solution from my perspective.
I like your perspective - let's see you do it though.
I agreed.
Actually I didn't try to set all grounded, but only for those I needed when want to set constraints to them.
This is one of the reasons that I don't think need to add such an option.
Thanks,
-Austin
Hi JDMather,
You are the mentor to me on this forum and some Inventor functionalities too especially on data translation; personally I learn a lot from you. 🙂
Thank you.
For the constraints, users need them during data translation, but we still need more time to plan for this in the future.
Back to the question about the option for "set all grounded", how do you feel this option would work for users if Inventor suppots it? Have you, or someone else you know, ever met any problems and then want such an option?
We want to hear more feedback from our customers and Inventor experts.
Thank you so much for your help on this topic, and this forum.
-Austin
This is what I am interested in, "The solution in the future should be "to keep the constraints in data translation".
Pull that off and you will have at least one advantage over competitors.
Thanks. I will pass on the information to our development team.
We could use a Ground All components when importing a file. We have to import files all of the time from STEP, Rhino, SAT, DWG, and Solidworks. Usually the imported components are reference, so I don't need the constraints. We have had people import a model, not ground the components, and accidentally move a component out of place while working on it. The movement isn't caught right away, and we wasted a lot of time trying to figure what went wrong when we finally caught the mistake.
I'm thinking it could be a check box in the Options dialog when importing.
Joe Bartels
Hi everyone,
Here is a quick iLogic rule to ground all components that can be used when importing models from other modelers.
I hope this helps.
Best of luck to you in all of your Inventor pursuits,
Curtis
http://inventortrenches.blogspot.com
' set a reference to the assembly component definintion. ' This assumes an assembly document is open. Dim oAsmCompDef As AssemblyComponentDefinition oAsmCompDef = ThisApplication.ActiveDocument.ComponentDefinition 'set the Master LOD active Dim oLODRep As LevelofDetailRepresentation oLODRep = oAsmCompDef.RepresentationsManager.LevelOfDetailRepresentations.Item("Master") oLODRep.Activate 'Iterate through all of the occurrences and ground them. Dim oOccurrence As ComponentOccurrence For Each oOccurrence In oAsmCompDef.Occurrences 'check for and skip virtual components If Not TypeOf oOccurrence.Definition Is VirtualComponentDefinition Then oOccurrence.Grounded = True else end if Next