@johnsonshiue wrote:
....
1) The angular constraint on the crane lift is not reasonable. Better geometry targets can be used.
Could you be more specific and a little more descriptive over what are better and worse geometry targets for constrains? Until now I was convinced that all geometry is made equal, but it sounds not to be the case.
Is "being better or worse" geometry target for constrain also true/valid for other type of constrains or it is just angular constrain that is involved in this distinction?
As for myself when I apply constrain there is always (99,9% of the time) some logic behind it. So if now it turns out that constrain I have applied is somehow cause of a problems I really would use to know and understand why.
2) The crane truck should be firmly grounded (except the crane). The flexible supports are adding complexity, making the movement complicated. As you know, there is a difference between fully constrained and grounded. When a component is grounded, its DOF is taken out of compute. As long as there is a constraint, it will need to be computed.
We could argue if I know there is as difference in how grounded and fully constrained component is handled. Personally I would conclude I do NOT know the difference because I have never read any Autodesk document describing how constrain solver works and what principle it takes.
Only knowledge in this regard I have from experiments that to say the least are inconclusive.
So I will most appreciate if you could give us some inside view and knowledge how this kind of things are handled by Inventor.
Especially interesting aspect is how grounded component is positioned, and how its transformation matrix is set.
Also from many experiments it is obvious that inventor deals with independent parts when solving assembly level even if this parts are placed in multi level sub assembly structure. So I wonder how grounded components are handled if they are grounded many levels down in the structure?
3) In PosRep, drastic movement from Master to another place (like turning the crash 180 degree) can lead to failures. I think it may have something to do with the initial location.
As for my understanding POS REPS are just "containers" that allow for representation of assembly in various positions depending on different or changes set of constrains. So there should not be any issue with "drastic" movement from one POS REP to another as "drastic" should not even be a justified adjective to use.
If set of constrains defined in given POS REP allows assembly to be properly solved it should be solved no matter how other POS REPS are defined, and even it should be solved properly even if Master POS REP is broken. Each POS REP should be INDEPENDENT form others in solve. Otherwise there is "movement" required form one POS REP to the other that may not be geometrically possible (for what ever reason). But in the same time this two POS REPS may be fully legitimate as individuals.
Also how order of switching between POS REPS influences what you have described? If I have 4 POS REPS each 90 deg from previous, when I go 1-2-3-4 (0-90 deg-180deg - 270 deg) according to your description it should work, but what happens if I try to go 1-3-4-2, (0-180 drg - 270 deg - 90 deg) will it be more probable to brake twice on the way?
Here is what I did.
1) Make the crane truck flexible.
2) Delete all the pre-existing PosReps within the crane truck.
So are you saying that flexible component will cause problems if it has POS REPS defined?
And what if flexible component uses other component that is represent in POS REP of its own? (and so on deeper and deeper in the assembly structure)
3) Activate the crane truck's PosRep:Master. Create a Mate constraint between the anchor and the hook. It may fail. Suppress the Mate constraint.
I do not get that. You need to explain more.
Especially please explain why you did write "It may fail"? Why constrain should be expected to fail if it is fully legitimate?
4) Activate the "on truck 1" PosRep at the top-level.
5) Edit the crane truck in place -> create a new PosRep -> move the crane near the hook so the Mate will work.
This I also do not get.
Are you saying I should create POS REP within truck assembly?
Also as I understood (incorrectly perhaps) you require me to manually move the crane assembly in to a position where constrain works. This I would say is rather unexpected requirement (assuming I understand correctly). It is obvious, constrain will work if elements are already in the position this constrain is met. But this is totally opposite to what users expect from constrain. I, as a user, expect so it is the constrain I define that brings the geometry to a position, that is required for this constrain to be met. Otherwise it has very little sense. If constrain is not capable of bringing geometry together, there is not reason for this constrain to even exist.
There is infinite number of possible relative positions of the given geometry of two elements, that may be caused by initial placement, solve of other constrains, some random user inputs, free DOFs, set of constrains that can lead to many solutions and infinite number of other causes and reasons.
So it is only reasonable to expect that if a constrain is defined (assuming it is legitimate) it will bring geometry to a defined potion NO MATTER WHAT, no matter where it is and what is even more irreverent no matter what was the cause to bring it to the position it is (again assuming it was not another constrain that would be conflicting with the one we now consider)
6) Make sure the position overrides are captured within the new PosRep. Return to top and unsuppress the Mate constraint.
7) Repeat step 4 to 6 for other PosReps.
I am pretty sure it will brake the moment you decide to edit some of the constraints that are positioning this tower and flexible crave will have to follow.
This is actually the biggest pain.
It is possible to get it to a position as you described, but it breaks very quickly.
But let us see your model. Perhaps I am wrong about that.