In network node model, Task Executors, the task executors do not decelerate.

Question

question

Aditya Prakash asked Apr 09 2018 at 7:44 AM David Seo answered Sep 23 2019 at 3:55 PM

In network node model, Task Executors, the task executors do not decelerate.

In network node model with Task Executors, the task executor does not start to decelerate before it reaches a node. Has anyone else faced this issue? How do i solve this issue? Thanks

Software Version:

FlexSim 16.1.2

network node task executor decelration

______

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-04-09T07:58:44Z

David Seo answered Apr 09 2018 at 7:58 AM

@Aditya Prakash

All Task Executers's speed, acceleration and deceleration are valid though network node. You need to control the speed of them to change the speed limit of the network node. The curved pass line speed limit and the straight pass line speed are differently limited each other.

You can think your car speed and the limit of the roads. The running speed of the taskexecuter is determined by the intersection of two condition.

· 2

Aditya Prakash commented · Apr 09 2018 at 11:00 AM

@david.seo Thanks for your reply. I think, speed limit might not exactly be an issue, as I have set max speed of task executor and speed limit of node connections equal.

I will try to describe the case scenario:

Now, a task executor leaves NN1 to go to NN2.

Distance between 2 nodes is 1m.
Acceleration 1m/s^2
Deceleration 1m/s^2
Max Speed 2m/s
Initial speed 0
Final Speed 0

Calculation expected-case.png time taken to reach the node should be 2 seconds.

Actual Case in Flexsim it reaches in 1.41 seconds.
This can happen only if the Task Executor comes to a sudden stop. Calculation: actual-case.png

Please look into it. Am I doing something incorrectly? @david.seo

expected-case.png (5.9 kB) actual-case.png (6.3 kB) Add comment Share Accept

0 ·

Phil BoBo ♦♦ Aditya Prakash commented · Apr 25 2018 at 10:30 PM

Please post your model so we can see what you are doing. No one can tell you whether you are doing something incorrectly unless they can see what you are doing.

You probably aren't using a final speed of 0. In a travel task, var1 (the end speed parameter) of 0 means "max speed" and -1 means "zero" as explained in the documentation:

1 ·

travel-task-end-speed3.png (79.2 KiB)

question