topic Units for api in Fusion API and Scripts Forum

Units for api

Cotral.RD2 — Fri, 22 Jun 2018 11:39:37 GMT

Has there been any updates on the default units for the sketcher?

The last lime i checked two days back the dimension from api i got was in radians for angles and cms for lengths, but now it seems the units are changed to mm and deg..

Its a good move but i need to be sure this is truly the case..

Re: Units for api

BrianEkins — Thu, 28 Jun 2018 05:10:35 GMT

What calls are you using to get those values? The API should always return distances in centimeters and angles in radians.

Re: Units for api

Cotral.RD2 — Thu, 28 Jun 2018 06:13:32 GMT

Ah my mistake!

yes when i get the values directly to a variable the units are in centimeters and radians but since i was transferring this value directly to a command input with mm and deg units the conversion happened automatically

Re: Units for api

maxim.yudayev3RJDX — Fri, 19 Oct 2018 23:09:49 GMT

Brian,

Is there a list of standard units that the Units Manager recognises? The documentation does not specify this. I am interested in using angular velocity units passed from user in RPM.

Thank you.

-Max

Re: Units for api

BrianEkins — Sat, 20 Oct 2018 03:33:03 GMT

There should be something in the documentation about this but I didn't think about it at the time because the API supports whatever core Fusion supports since it's just using internal utilities. One way to see what's supported is to run the Parameters command and create a new user parameter. You can choose the unit for the new parameter which will display a large list of unit types. There is an option for angular velocity as rpm. One thing to be aware of though is that the API always deals with consistent internal units, which are cm for length, radians for angles, seconds for time, and kilograms for mass. So if the user enters "5 rpm" and you get back the value you'll get

0.5235987755982988, which is 5 rpm expressed as radians/second.

Re: Units for api

maxim.yudayev3RJDX — Sat, 20 Oct 2018 16:20:58 GMT

Brian,

Hahaha, I actually found it right the same way a few minutes before you had left a reply! Thank you sir!

Yes, you always mention in similar threads that F360 interprets and evaluates the values in those fixed units.

Though I now have a new problem, I can't wrap my head around why I am unable to choose a "No Units" value for an addValueInput. Can you please give an advice? I had tried different spelling and letter casing, can't seem to find the right way.

Thank you very much.

-Max

Re: Units for api

BrianEkins — Sat, 20 Oct 2018 22:32:42 GMT

An empty string should work to create a parameter with no units.

addValueInput('safetyFactor', 'Safety Factor', '', 1)

Re: Units for api

maxim.yudayev3RJDX — Sat, 20 Oct 2018 22:49:15 GMT

Tried it before, but apparently it was only part of the issue, i declared number "1" in stead of "ValueInput.createByReal(1)" as the initial value for that input.

Thank you very much for the tips, the issue is solved!