Difference between deceleration in different TE´s

Question

question

Sebastian Hemmann asked May 05 2017 at 11:02 AM tannerp commented Sep 13 2018 at 6:47 PM

Difference between deceleration in different TE´s

Hi, does anybody have a good Explanation why the "deceleration" option in different Task Executers work different?

Attached is a model in which all Task Executers have an acceleration of 1 but a deceleration of 0.1. The deceleration seems to be called in the first TE only on it´s frist travel. The second TE does it allways. Operator same like Transporter never do it!?

deceleration-example-sh.fsm

Software Version:

FlexSim 17.1.2

task executer deceleration

deceleration-example-sh.fsm (22.9 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 · 2018-09-13T14:42:50Z

Phil BoBo answered Sep 13 2018 at 2:42 PM

For what it is worth, I explained what is happening here to Sebastian offline. Here's a summary:

The default travel tasks given to the task executer when using Use Transport have a desired end speed of "the maximum speed of the task executer" (see var1 of TASKTYPE_TRAVEL).

This causes the task executers to not start to decelerate until they finish their travel task and start performing their load or unload tasks. With a really low deceleration value and very little room to decelerate between when the travel finished and when they arrive at the load/unload location, the task executers that have a Navigator are moving a lot faster than the task executers without a Navigator because the task executers without a Navigator aren't doing the travel tasks at all and are instead immediately starting their load/unload tasks with a lot more space to decelerate.

Answer 2 · 2018-06-29T14:58:36Z

tannerp answered Jun 29 2018 at 2:58 PM tannerp commented Sep 13 2018 at 6:47 PM

After examining your model, I found that because Task Executer 1 was assigned to a Default Network Navigator, it was not looking to its own properties and obeying the deceleration rule which you set. I removed the Network and now the Task Executors behave the same.

deceleration-example.fsm

deceleration-example.fsm (21.6 KiB)

· 4

Sebastian Hemmann commented · Sep 12 2018 at 5:26 PM

Thanks. I´ve got some Questions on this:

1. I did not add a Default Network Navigator -> is it added in standard?

2. Who made this answer the best answer? Is it only because it is the only answer?

3. What is wrong with all other TE´s?

0 ·

tannerp Sebastian Hemmann commented · Sep 12 2018 at 5:57 PM

1. Here's where the setting is found to assign a Navigator to a TE:

I believe it is default and is therefore applied automatically. As to how to change the default settings, I'm not sure. I would need @jordan.johnson or @phil.bobo to help explain the code behind it.

2. I'm not sure who accepted this answer, but sometimes when we don't receive feedback for an extended period of time, the only answer available is accepted.

3. Could you clarify what you mean when you say there's something "wrong" with them? Are you referring to their deceleration as well?

0 ·

default-network-navigator.png (37.4 KiB)

Sebastian Hemmann tannerp commented · Sep 12 2018 at 7:24 PM

1. You are right, if I change the option in the field to "none" the TaskExecuter1 is showing the complete same behavior like TaskExecuter2. But it also is not using the Network at all, so expect it should work so because now it is the same Szenario like the one with TaskExecuter2.

2. Shouldn´t I be the only one who accept an answer for my question?

3. The deceleration seems to be called in the first TE only on it´s frist travel. The second TE does it always. Operator same like Transporter never do it!? I´ve used standard settings for all Szenarios. So is it wrong if I expect completely same behavior for all of them?

1 ·

Show more comments

question