Thanksrealthunder wrote: ↑Tue Jul 28, 2020 1:49 pmYes, that's right. You can apply additional offset to the element(link) to attach two parts in any relation. For the multiplication fix, you can test it now if you want, by cloning my asm3 github repository to your [user directory]/FreeCAD/Mod. Or, just want for my next release, probably tomorrow.
Thanks for the thorough explanation. I've managed to get most of the assembly done. The only thing I'm still unsure is Attachment should fix two object.realthunder wrote: ↑Fri Jul 17, 2020 4:13 am...
BTW, in your particular case, 1 and 2 are aligned in axial direction. There is really no need to use two hole fixing, which is kind of expensive. Just fix it with an attachment constraint, and apply a rotation offset to the constraining element if required. Two hole fixing is only really necessary if the offset between the two parts are hard to calculate manually.
I did find a bug about Attachment. The attachment constraint allows a cheaper way to solve without requiring the expensive algebra solver. However, that only works if one of the Part is 'Locked', or attached to another 'Locked' Part. Since the flywheel is supposed to move, the Attachment constraint will be internally converted to a PlaneCoincident constraint to let the solver find the solution. The bug is that I forgot to lock the angle. Since you've already using the PlaneCoincident constraint, you can manually lock its angle with the 'Lock Angle' property.czinehuba wrote: ↑Sat Aug 01, 2020 9:52 pmBut in my case it allow rotation, I think it leave 1 DOF. Hence I still used two PlaneCoincident for the two holes for 1 & 2. And I'm also struggling to fix two object to rotate together. (in this case crank shaft and wheel or crack shaft and flywheel) I've tried Attachment but it allow for rotation.
Is this a bug or I'm still doing something wrong.
Thanks for the tip. It worked like a treat.
Hello and congratulations on your success.
I think it would be interesting if the name of the object owning a constraint element would automatically display: eg. in place of ElementXXX appears ElmtXXX_OwnerPieceName.
Code: Select all
SoFCUnifiedSelection.cpp(2409): Cyclic scene graph:
Yes. Thanks for the advice. It does work that way as well. And like you said it has less strain on the solver. It seems more fluid.
Ok, so I figured out I was using the Transform tool rather than the Axial move tool.