Unit of Mass Flow Conveyor Generative Rate

Question

question

Shinya O asked Nov 07 2024 at 8:36 AM Shinya O commented Nov 08 2024 at 12:17 AM

Unit of Mass Flow Conveyor Generative Rate

Hi,

I am executing the following code to change the Generative Rate of the mass flow conveyor, but there is a difference between the value displayed on the GUI and the value obtained by the getProperty method. The value on the GUI is multiplied by 60, probably because the unit was changed from seconds to minutes.

Object mfc = Model.find("MFC1");
token.labels.assert("gfr", 60);
token.gfr *= 2;
mfc.setProperty("GenerativeFlowRate",token.gfr);
print(Model.time, "MFC", token.gfr, mfc.getProperty("GenerativeFlowRate"));

When I change the MaxSpeed of the operator in the same way, the value that can be confirmed on the GUI and the value that can be obtained with the getProperty method match without any problems.

Until this issue is resolved, we will need to select the same units as your model units.

Thanks in advance.mfc-sample.fsm

Software Version:

FlexSim 24.0.4

massflowconveyor mass flow conveyor generative rate

1730968286468.png (267.3 KiB)

mfc-sample.fsm (45.4 KiB)

______

Cookie preferences

Your privacy is important to us and so is an optimal experience. To help us customize information and build applications, we collect data about your use of this site.

May we collect and use your data?

Learn more about the Third Party Services we use and our Privacy Statement.

Strictly necessary – required for our site to work and to provide services to you

These cookies allow us to record your preferences or login information, respond to your requests or fulfill items in your shopping cart.

YES

Improve your experience – allows us to show you what is relevant to you

These cookies enable us to provide enhanced functionality and personalization. They may be set by us or by third party providers whose services we use to deliver information and experiences tailored to you. If you do not allow these cookies, some or all of these services may not be available for you.

YES

NO

Customize your advertising – permits us to offer targeted advertising to you

These cookies collect data about you based on your activities and interests in order to show you relevant ads and to track effectiveness. By collecting this data, the ads you see will be more tailored to your interests. If you do not allow these cookies, you will experience less targeted advertising.

YES

NO

Are you sure you want a less customized experience?

We can access your data only if you select "yes" for the categories on the previous screen. This lets us tailor our marketing so that it's more relevant for you. You can change your settings at any time by visiting our privacy statement

Your experience. Your choice.

We care about your privacy. The data we collect helps us understand how you use our products, what information you might be interested in, and what we can improve to make your engagement with Autodesk more rewarding.

May we collect and use your data to tailor your experience?

Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.

Answer 1 · 2024-11-07T11:59:05Z

Felix Möhlmann answered Nov 07 2024 at 11:59 AM Shinya O commented Nov 08 2024 at 12:17 AM

I am pretty sure this is working as intended. Property values are always stored in terms of model time and length units. If you select a different unit in the properties window, all that does is add a subnode that denotes as what the value should be displayed.

It works the same for task executers and fixed resources. Though if you use "setProperty()" on those, it actually removes the displayUnits node (at least in 24.2.2, maybe that is a bug).

So as you say, when setting any values in code, you always have to think in model units. There are commands to convert common units into model units to help with the math and make it apparent at a glance what the value is being set to.

https://docs.flexsim.com/en/24.2/Reference/CodingInFlexSim/CommandReference/CommandGroups.html#minutes

1730980278044.png (2.6 KiB)

· 2

Phil BoBo ♦♦ commented · Nov 07 2024 at 4:53 PM

For properties that correspond to measured units, such as distance, speed, acceleration, time, etc., Object.setProperty() can take an array which specifies the units. It isn't a bug that the display units are being removed if you specify a value without display units. If you want to specify a value with display units, then pass that accordingly. Object.getProperty() also has a flag for getting the value back as an array with its units abbreviation string.

See Property Tables / Types of Properties / Unit

The GenerativeFlowRate property is a little different though. It isn't a normal Unit property. Only its denominator has a unit. The GernerativeFlowRate property is stored in model units and the Properties window converts what is displayed based on the specified display units. You need to set that property's value in model units.

Object mfc = Model.find("MFC1");
double unitsPerMin = 5.0;
mfc.setProperty("GenerativeFlowRate", unitsPerMin / minutes(1));

1 ·

Shinya O Phil BoBo ♦♦ commented · Nov 08 2024 at 12:17 AM

Thank you both. Both answers were helpful.

0 ·

question