Constraint for UCS (UserCoordinateSys.) allthoug for OCS (OroginCoordinateSys.)

[c_stulz]

Often I want to place different Parts exact on there one CoordinateSystem.

Then I go and place 3 constraints YZ to YZ / XZ to XZ and XY to XY.

The constraint-tool for UCS makes the same, but I need first in both parts an UCS. So it would be nice tu use the constraint-tool for UCS allthough für the existing orogin coordinate system.

allthough for 

[PaulMunford]

This would be grate!

I'm the meantime, there are a couple of alternatives you may not be aware of?

If your part remains parallel with the XYZ plains, you could use the:

iProperties > occurrence

Tab to ground the part at the origin and then offset...

Or you can use 'Ground and root' from the assembly productivity tools to add your constrains automatically.

Does that help?

[c_stulz]

Hello,
Thanks for replay.
Yes I know that bothe Ways.
ground and Fix:
Not every time these Parts are in the MainCenter as they will be when I am modeling with multibody ore thome thing like this.

Inset position over the partinstance:
This is allthough Timeconsuming and not faster then placing three constraints.

And In my opinion there could be exact the same funktion between OCS and OCS or OCS and UCS because they are the same family with 3 Planes, 3axis and Point (only planes are used in this funktion)


When I have to enter some Numbers I am not fasten then Plasing 3 constraints (where I only have to look on there groundplanes xy to xy and so on.





Mit freundlichen Grüßen
Christoph Stulz


Schwabsgasse 15
77971 Kippenheim
c.stulz@vektor-werkstatt.com
www.vektor-werkstatt.com
Tel.: +49(0)7825 432939
Mobil: +49(0)152 21938471

[DRoam]

I'm on board with this but I'm not sure how feasible it is given that the OCS is not a coordinate system "object" like a UCS is. It's just a folder with a few pre-defined work features in it. So you couldn't really select the OCS itself for a CS-to-CS constraint.

Autodesk would have to convert the origin into a coordinate system "object" in future part files. Ideally, this is probably how it should have been to begin with... but it might not be realistic at this point. It would completely change the way the Origin works in Part files and might result in conflicts with old Parts with the current architecture.

But here's a suggestion for you. Set up your Part/Assembly templates so that you have a UCS at the origin, and then you'll always have this in your new Parts/Assemblies. This is easy to do in existing Parts/Assemblies as well. Just start the UCS command, type in 0-tab-0-tab-0, then hit Enter twice and you're done. Then you can drag this UCS to the top of your Browser tree if you want. And then you can use this for any UCS-to-UCS constraints.

Is that a possibly acceptable alternative?

[PaulMunford]

DRoam - Good Idea 🙂

[c_stulz]

Hello Droam,

this is a great Hint.

I testet it an allready plased the UCS in the Template.

Thanks