Update code for Open/Close ports on reset trigger for fluid generator.

Question

question

Kari Payton asked Jan 09 2018 at 9:48 PM Mischa Spelt answered Jun 28 2018 at 8:13 PM

Update code for Open/Close ports on reset trigger for fluid generator.

Idk why this is, but whenever I tried the option close port on the reset trigger for the FluidGenerator it didn't work. After some hours I saw something to use clopeop for fluids. I went in and used the custom code trigger on reset option to use closeop function instead of closeoutput and it works. Maybe update the standard fluid trigger options with this function or make functions all the same for fluid and solids?

Software Version:

FlexSim 18.0.1

fluid library fluids

· 2

Phil BoBo ♦♦ commented · Jan 10 2018 at 4:01 PM

Are you talking about a FluidGenerator or a FloWorks object?

The FluidGenerator works just fine with closeoutput() OnReset:

fluidgenerator-closeoutput-onreset.fsm

Please post a model demonstrating the issue you are having.

You can use both closeoutput/input and closeop/ip with fluid objects. Fluid will only be sent through a port if all of the connections are open (output and op of upstream object, input and ip of downstream object).

0 ·

fluidgenerator-closeoutput-onreset.fsm (16.9 KiB)

Kari Payton Phil BoBo ♦♦ commented · Jan 11 2018 at 8:51 PM

unfortunately I can't find the saved copy of the file I was working on. I was referring to FluidGenerator. I tried to redo it and couldn't replicate the issue now. Possibly I had something else going on. Next time I'll provide the model. Sorry @phil.bobo

0 ·

______

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 · 2018-01-12T09:03:29Z

Mischa Spelt answered Jan 12 2018 at 9:03 AM

In case anyone finds this topic in the future let me complement this thread with the FloWorks answer: because FloWorks does not use time slicing but events, you need to make sure that the engine is aware of ports being opened or closed so the flow rates through your network can be recalculated. In pre-17.2 FloWorks separate commands CloseFlowOp and CloseFlowOutput were provided that you had to use instead of FlexSim's closeop and closeoutput. Since version 17.2 FloWorks supports 'dot syntax' which allows you to write:

// Note: type of the variable is FlowObject instead of Object
FlowObject flowObject = model.find("...");
 
// "Red bar" for all output, just like in regular FlexSim
flowObject.output.close();
 
// Close a single port, equivalent of 'old' closeop/CloseFlowOp
flowObject.output.ports[1].close();

or directly through

// note the use of .as(..) to ensure that the treenode is treated as flow object
model.find("...").as(FlowObject).output.close();
model.find("...").as(FlowObject).output.ports[1].close();

question