Cancel
Showing results for 
Search instead for 
Did you mean: 

Relative length constraint in a sketch?

Valued Contributor
Valued Contributor

The sketch below needs one more constraint to be fully constrained.  I could assign a dimension to "a" or "b", but what I'd rather do is set a relation between them (like a = 0.60*b).  Is there any way to do that?   I want to able to vary p1 (vertical height) and have all the sketch elements stay in the same proportion.  Thanks for any help with this.

 

relative_lengh_constraint.png

 

5 REPLIES

Re: Relative length constraint in a sketch?

Siemens Phenom Siemens Phenom
Siemens Phenom

Solving sketches with these direct equations is currently not possible.

 

Regards, **bleep**

Re: Relative length constraint in a sketch?

Gears Esteemed Contributor Gears Esteemed Contributor
Gears Esteemed Contributor

You would have to figure out an equation / expression relating the length of (b OR a) to p1 (I'm assuming there's a typo in your original post when you said "p0" - as that is your angle expression).

Then set the length of (b OR a) to that expression.

Ken Akerboom Sr CAx Systems Engr, Moog, Inc.
Production: NX10.0.3.5 MP16/TC11.2
I'd rather be e-steamed than e-diseaseled


Re: Relative length constraint in a sketch?

Legend
Legend

Try this, worked for me.

Overconstrain the sketch by adding constraints to Line A and Line B

Edit the constraint B to read whatever the p number of constraint A is  * .6  e.g p3=p2*.6

Now convert constraint A to a reference constraint.

 

Re: Relative length constraint in a sketch?

Legend
Legend

Nope, sorry that didn't work very well.

Re: Relative length constraint in a sketch?

Valued Contributor
Valued Contributor
Thanks for responses.  I was guessing doing this as I showed was probably not possible, but I just wanted to be sure.

@Ken - yes, I could come up with a relation, or in this case add an angle dimension at the intersection point, to maintain proportionality between the segments. But I was mainly wondering is there was a way to specify that more directly. Also, you were right, p0 should have been p1 (which I fixed).

Thanks again!