The logic for TaskSequence-find the reference of the task that being updated?

Question

question

Kuilin S asked Jun 28 2022 at 9:11 AM Felix Möhlmann commented Jun 29 2022 at 6:50 AM

The logic for TaskSequence-find the reference of the task that being updated?

Now we have a scenario where we need to call the crown block to Queue1 20 seconds after processing, and wait for the completion of processing (the crown block is in the occupied state) to call "Box" to Queue2. The Source generates an endless stream of orders, and each order is a task that generates the above sequence of required tasks, which are sent to the Dispatcher to assign the crane (equivalent to the field dispatcher). The task is triggered at the appropriate starting point (delayed message), and I'm not sure what the reference to that task is. Because the tree structure is updated by rolling. Here is the model that I'm working with, please help me.

demo_dispatcher.fsm

Software Version:

FlexSim 22.0.4

dispatcher tasksequence coding cranes

demo-dispatcher.fsm (33.1 KiB)

· 1

______

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-06-28T10:03:43Z

Felix Möhlmann answered Jun 28 2022 at 10:03 AM Felix Möhlmann commented Jun 29 2022 at 6:50 AM

When creating the task sequence you could write it to a label on the item. When the message is received the item should be the first (and only) object inside the processor (fromObject), which gives you an easy reference to the task sequence.

Another problem with your current model is that cranes only do offset travel. To have them move to a certain location while not loading/unloading, you have to use the TRAVELTOLOC task type.

demo-dispatcher-fm.fsm

When also taking into account that the crane would then have to wait until the processor actually finishes, I believe controlling the cranes through a process flow might be the easier option.

demo-dispatcher-fm_1.fsm

1656410099090.png (14.1 KiB)

1656410110081.png (7.4 KiB)

demo-dispatcher-fm.fsm (32.6 KiB)

demo-dispatcher-fm-1.fsm (42.2 KiB)

· 2

Kuilin S commented · Jun 29 2022 at 5:52 AM

Thank you for your answer. I'm working with the problem that is related to the crane scheduling. What relplaced the function of "Dispatcher1" in process flow? Can you give me more details?

0 ·

Felix Möhlmann Kuilin S commented · Jun 29 2022 at 6:50 AM

The cranes are present in the process flow as a Resource. The tokens can acquire them. Each object that is part of the resource can only be acquired by one token at a time. So the token acquiring the crane is the equivalent of the task sequence being dispatched to the crane, only that the tasks are only given to the crane after the fact and one at a time.

To acquire a specific crane (if more than one are available), you can use the query field in the acquire activity. For example to choose the closest one to the item, you'd add the 'distance' field to the resource ('Advanced' button opens the corresponding menu) and then order by that field in the query.

Note that the distance is calculated with respect to the 'puller' by default, which in this case is the token. To get the distance between the item and the crane, you have to edit the code that calculates the distance to reference the item instead (through the token label).

demo-dispatcher-fm-2.fsm

0 ·

1656485339634.png (33.1 KiB)

1656485391643.png (14.9 KiB)

demo-dispatcher-fm-2.fsm (42.6 KiB)

question