I'm a relatively recent convert to Inventor (background in SolidWorks, SolidEdge, and Solid Designer). Been using Inventor for two years, but I continue to be vexed by a problem with some of my company's legacy assemblies that I have never been able to figure out. I'm hoping someone here can shed light on the issue.
Every now and then I open an assembly that appears to be a normal assembly in every way, but it is not possible to move any components in the assembly. Typically, there are no broken constraints, but often there are components out of place from where the constraints indicate they should be. It's not possible to move any components, even by deleting all existing constraints and replacing them with new constraints. None of the immovable components is grounded. (Although a previous engineer here, who created many of these assemblies, had a nasty habit of building assemblies by just grounding components in place, rather than constraining them.)
Is there some feature for "freezing" an assembly that I'm not aware of and, if so, how do I "unfreeze" them? So far, the only way I've been able to make these assemblies usable is to rename the file and then create a new assembly from scratch, saving it to the original filename. Obviously not a very good long-term solution!
Tedd
@Anonymous wrote:I'm a relatively recent convert to Inventor (background in SolidWorks, SolidEdge, and Solid Designer).
So I take it your background is pretty "solid" then...Sorry, someone had to say it.
Welcome to the Inventor side of things.
I hate to say it but without having your assembly to look at and dive into, I can only throw darts and hope I get something right.
You eliminated the "grounded" question (I've seen my share of users building assemblies that way...ugh).
Are the assemblies using a Position Representation or even a Level of Detail?
The only other thing that comes to mind is sometimes constraints are tied to other constraints and are "frozen" in that sense until the other constraint changes or is deleted. I've seen that happen rather often.
You said you have to delete the part and then reinsert and constrain it? Just for giggles, have you just deleted all the constraints in the assy and attempted to move the parts then?
Can you maybe post a small assmebly that you are having these issues on? I'm sure someone here can access it and find out what the deal is.
I made a pack-n-go of the latest example I've encountered, but the zipped version is still 7.7 MB. Do you think that's too big to upload?
Tedd
Yep. I believe the file size limit here is 1.5 MB. If you have time and patience, you could try opening the biggest part files and dragging the End of Part marker to the top of the tree, hiding all geometry, then save. This reduces file size by a considerable amount, and you might be able to squeeze in under the limit. Or save it somewhere else (the AUGI website is one possibility) and post a link to it.
Sam B
Inventor 2012 Certified Professional
Please click "Accept as Solution" if this response answers your question.
-------------------------------------------------------------------------------------
Inventor Professional 2013 SP1.1 Update 1
Windows XP Pro 32-bit, SP3
HP EliteBook 8730w; 4 GB RAM; Core™ 2 Duo T9400 2.53 GHz; Quadro FX2700M
SpaceExplorer/SpaceNavigator NB, driver 3.7.18
still waiting for a foreshortened radius dimensioning tool in Drawing Manager
Hm. I tried simplifying the assembly by deleting some parts. Once I got it simple enough (three parts), it started to behave normally. I.e., if I suppressed mates I could move parts. So I think maybe the issue is constraints somehow tied to other constraints, as Jim suggested. I'm going to poke around with it a bit to see if I can figure out what's happening.
If I find out anything interesting I'll post the results.
Thanks,
Tedd
Tedd,
The best way to see whether your component is able to move is to check its degrees of freedom(DOF). You can show/hide DOFs for all components in the assembly by menu "View->Degrees of Freedom", or for individual components by context menu on component node in the browser view where you choose item "iProperties...->Tab: Occurrence->CheckBox: Degrees of Freedom".
Robert
One thing to keep in mind, often folks will constrain parts using a skeleton model which is an acceptable workflow.
However, constraining individual parts to LINES or POINTS in a sketch can result in more than one possible solution.
That is why we always utilize PLANES in our skeleton models.
I wonder if the parts were created using in-place modeling techniques? If so, it's entirely possible that there's geometry projected between parts. If this is the case, then you can't move anything because the projected sketch references are holding things in place. If the parts are moved, the sketches break, so Inventor doesn't allow the parts to move.
Check for this, see if parts / sketches / etc are adaptive in your assemblies and sub-parts.
Rusty
"I wonder if the parts were created using in-place modeling techniques?"
That's a good thought, I'll check for that next time I find an assembly with the problem.
One of the issues here is that when the company decided to switch to Inventor (from AutoCAD) it cheaped out on the training. Not only did the engineers not have any experience with Inventor, they didn't have any 3D CAD experience at all, but I think they only got one day of training. (This all happened before I joined.) So there is legacy of early CAD models that have problems, made during the early years when they were learning things the hard way. The cost of those legacy models is orders of magnitude greater than a little extra training up front would have cost. A great case study in how not to make a paradigm change in your engineering processes!
Hi! The behavior you describe does not sound right to me. Please send it to me at johnson.shiue@autodesk.com so I can take a look.
Thanks!
Johnson:
This generally happens in larger assemblies than I'd be able to email you (we have a pretty small choke at this end). But if I find a smaller assembly with the problem I'll send it to you.
Thanks,
Tedd
Has there been a solution to this ?
I have been starting new assemblies to get around it, eventually repeats itself.
Can't find what you're looking for? Ask the community or share your knowledge.