Can't edit constraint in Inventor Studio

Can't edit constraint in Inventor Studio

matroosoft
Advocate Advocate
2,291 Views
13 Replies
Message 1 of 14

Can't edit constraint in Inventor Studio

matroosoft
Advocate
Advocate

When I'm in Inventor Studio, trying to animate an assembly, I can edit the second but editting the first value is impossible. (the selected one on the screenshot. The part is which has to be animated is ungrounded, flexible and the constraint uses offset as resting position. (which I saw was recommendated in another topic)

 

The value simply doesn't change if I select it and type another value. Hope someone can help with this.

 

2017_03_15_08_06_09_Greenshot.png

0 Likes
2,292 Views
13 Replies
Replies (13)
Message 2 of 14

WHolzwarth
Mentor
Mentor

Can you set the new value in Assembly environment? IMO, then it's tranferred to Studio.

Walter Holzwarth

EESignature

0 Likes
Message 3 of 14

matroosoft
Advocate
Advocate

I've tried it, but the offset value in assembly environment does not affect the first value in the studio environment.. If I, for example, set the offset to 50 in assembly environment it doesn't change the value in the studio environment (which is 90).

0 Likes
Message 4 of 14

WHolzwarth
Mentor
Mentor

Tested it right now with 2017. Worked ok with initial change in Assy environment.

If needed, I can place a video (not now, but some hours later)

Walter Holzwarth

EESignature

0 Likes
Message 5 of 14

matroosoft
Advocate
Advocate

Hmm, I'm in 2017 as well and tried the same.. Even in a fresh assembly created just for testing this. If you want to make a video, it might be helpfull. I don't see what I'm doing wrong here! 😉

0 Likes
Message 6 of 14

WHolzwarth
Mentor
Mentor

Here's a link. (Screencasting is not my favorite playground) Smiley Wink

http://autode.sk/2no3PmP

 

But I got it later ..

 

 

Walter Holzwarth

EESignature

0 Likes
Message 7 of 14

matroosoft
Advocate
Advocate

Thanks for the effort you put into this! I've followed the steps you did and realized you have a mate constrained with an offset, while I have a mate constraint with a min/max offset, so I changed that. That was the only difference.

 

After that, changing the offset off the constraint does indeed affect the first value in the studio environment, but if I change the second value (in the studio env.) then the first value changes to a random number. Seems pure magic to me.. Smiley FrustratedSmiley Indifferent

0 Likes
Message 8 of 14

WHolzwarth
Mentor
Mentor

Yes, Studio has some mysteries. I've been stumbling over them on my own.

 

Perhaps it's getting better, together with annual pricing ..

Walter Holzwarth

EESignature

0 Likes
Message 9 of 14

matroosoft
Advocate
Advocate

Maybe. Smiley Happy Thanks for the help anyway! If I find a solution I will post it here.

0 Likes
Message 10 of 14

johnsonshiue
Community Manager
Community Manager

Hi The behavior does not sound right to me. The issue is more likely in the assembly constraints, not in Studio. Could you post the files here or send them to me directly ([email protected])?

Many thanks!

 



Johnson Shiue ([email protected])
Software Test Engineer
0 Likes
Message 11 of 14

matroosoft
Advocate
Advocate

I've send you the files by e-mail. Looking forward to your response!

0 Likes
Message 12 of 14

Bill_Bogan1
Autodesk
Autodesk

Another approach would be to use positional representations and animate between the reps.

 

-bill



Bill Bogan
Principal Content Experience Designer
CXD
PDMS-DiD-Digital Manufacturing
Autodesk, Inc.
0 Likes
Message 13 of 14

WHolzwarth
Mentor
Mentor

Hmm. I've seen posreps behaving unreliable. If there are more than two for a constraint, uncontrolled jumps can appear.

Walter Holzwarth

EESignature

0 Likes
Message 14 of 14

matroosoft
Advocate
Advocate

I had a talk with Johnson Shiue and after all I removed the limits of the concerned constraint. That didn't solve the problem in the assembly I was talking about but in a fresh assembly it did. I couldn't change the first value in the animation box either, but at least it wasn't a random number anymore (the value of the offset). So I consider this problem solved, at least for now. Thanks all for the replies!

0 Likes