Community
Fusion API and Scripts
Got a new add-in to share? Need something specialized to be scripted? Ask questions or share what you’ve discovered with the community.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

No isLocked property on asBuiltJoints?

2 REPLIES 2
SOLVED
Reply
Message 1 of 3
lodeKYAQ8
176 Views, 2 Replies

No isLocked property on asBuiltJoints?

Hi all,

 

Using a script to control the angles of some joints in my design, I found out that it is sometimes needed to be able to lock other joints first, as setting one joint can influence others, which is not always wanted.

 

When setting everything manually (via the browser UI), things seem to work, both (normal) joints and asBuiltJoints have the option to lock/unlock them.

 

Via the api, this does not seem to be the case: only (normal) joints have an isLocked property, asBuiltJoints don't seem to have it.

 

Am a overlooking something here?

 

Thanks,

Lode 

2 REPLIES 2
Message 2 of 3
BrianEkins
in reply to: lodeKYAQ8

That's an oversight in the API design and should be added.  I thought there might be a workaround until then but I tried it and ran into another issue so I don't believe there is a solution at the current time.

 

---------------------------------------------------------------
Brian Ekins
Inventor and Fusion 360 API Expert
Website/Blog: https://EkinsSolutions.com
Message 3 of 3
lodeKYAQ8
in reply to: BrianEkins

Thanks for the reply Brian!

 

Meanwhile I found a workaround that does the trick for me. I create a (normal) joint between two dummy components (which can be hidden, or implemented in the form of a handle next to the design...) and have that one motion linked with the asBuiltJoint one I want to lock from the API. Now locking the dummy joint 'locks' the asBuiltJoint too, which solves my problem.

 

Something else I noticed is that using the API to change the angle of a joint in a linked component doesn't seem to work either (even though I can confirm I found it traversing through the component hierarchy). And interestingly enough, the above workaround also solves this issue (unless this is not an issue but rather my ignorance... I am a complete fusion noob, only a couple days of experience so far, but learning a lot and enjoying every bit of it)

 

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Autodesk DevCon in Munich May 28-29th


Autodesk Design & Make Report