Using 2 Task Executers to load 1 Task Executer

Question

question

Theresa B asked Jul 18 2022 at 7:09 AM Theresa B commented Jul 22 2022 at 6:35 AM

Using 2 Task Executers to load 1 Task Executer

Hi, brains trust!

As the title states, I'm trying to get two task executers (ASRSs) to load one (a plane) with a capacity of 2 items, after which that plane will carry the two items to another location to unload to a third task executer (a ship).

I've used process flow to try and direct the ASRSs to unload to the plane but even if the plane remains stationary until the second ASRS arrives, it will not accept the second item but its stats will show an input of 2 but an output of 1.

I've tried a couple of different techniques that haven't worked and I'd like to know what's going wrong in both of them.

Unexpected behaviours in ProcessFlow:

Plane leaves without taking on the second box
Not sure why the release resource for the plane doesn't work

Unexpected behaviours in ProcessFlow2:

Not sure what's so bad about my task executer reference in the "Unload" activity

There may also be other errors in the model.

Thanks in advance!

load1TEfrom2TEs.fsm

Software Version:

FlexSim 22.1.2

processflow task executers coordinated task sequence asrs vehicle behaviour shared assets

load1tefrom2tes.fsm (60.9 KiB)

· 2

______

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 · 2022-07-19T07:30:30Z

Felix Möhlmann answered Jul 19 2022 at 7:30 AM Theresa B commented Jul 22 2022 at 6:35 AM

You only reference one item after the tokens have been batched. So the second ASRS doesn't unload its item, but instead moves the first item into the plane a second time (which is why you see both output and input go up).

You could instead use 'token.asrs[token.itemNo].subnodes[1]' to refer to the item the respective ASRS has loaded.

There is also the problem that the batched token can't release the second ASRS because it wasn't the token that acquired it.

Due to this I believe your approach of using multiple tokens in Process Flow (1) is actually the better way to build this logic. All it needs is to preserve the information about the second item.

load1tefrom2tes-fm.fsm

1658215701985.png (13.1 KiB)

load1tefrom2tes-fm.fsm (60.3 KiB)

· 5

Theresa B commented · Jul 20 2022 at 12:16 AM

Thanks, Felix! It's clear now what went wrong and that I have some missing foundational knowledge of the way that tokens use labels. Do you know of a publicly available exercise/worked solution to get me more comfortable with using dot syntax/subnodes/etc. in FlexSim?

0 ·

Jason Lightfoot ♦♦ Theresa B commented · Jul 20 2022 at 9:44 AM

In addition to the documentation you can place objects with different label types in a model an then in a script window try referencing them using an expression you write. You can put "return" in front of the expression with a semicolon at the end to see the value in the field of the script window, or just write the expression with no semicolon to do the same.

Note that you can write a long chain of methods and attributes as long as each is correct for the return type of the previous part of the chain. Attached is a small, quick example.

DotChainExample.fsm

1 ·

dotchainexample.fsm (33.0 KiB)

Theresa B Jason Lightfoot ♦♦ commented · Jul 21 2022 at 1:33 AM

Thanks, Jason. Does this work with the usual click&Run method, or are the effects of the script window confined to itself? I hadn't opened/used the script window at all before today, so a link to a walkthrough of this feature would be much appreciated.

Regarding the documentation, the examples are great but, for instance:

is there anywhere I can see a full list of the methods available to a particular object?
is there somewhere I can see the full list of subnodes of an object?

Apologies if these questions seem misguided; I am feeling a little lost in this area of FlexSim.

0 ·

Show more comments

question