Task executor moving away at a random far distance

Question

question

Kashif K asked Mar 17, '22 Kashif K commented Apr 14, '22

Task executor moving away at a random far distance

Hi,

I have a model where I create trucks with trailer that get filled by with pallets. Once full, a trailer is released. Now what I want is to make the truck travel on network node which it does, but only after flying to a random far away distance in the model a shown in the picture.

I moved my truck once it was full into a queue in process flow and from there, I use travel activity. Before travel activity, I used custom code to connect the truck with the first node of network node so it becomes part of its network navigator. Can someone please help me to keep the truck on its network node as soon as it starts traveling, and not do that random flying away motion? @Logan Gold @Brenton King @Eric M

Here is a similar question I asked answered by @Eric M . I also applied the same solution in my case but it doesn't work.

https://answers.flexsim.com/questions/104503/task-executor-flies-away-to-a-random-far-distance.html

Software Version:

FlexSim 22.1.0

task executer network nodes

1647559202606.png (167.9 KiB)

· 4

Jason Lightfoot ♦ commented · Mar 18, 2022 at 01:22 PM

Take a look at the tasksequence of the truck - what is it trying to do? It would help if you upload your model.

0 ·

Kashif K Jason Lightfoot ♦ commented · Mar 23, 2022 at 09:16 PM

Hi Jason. This happens when I move or create the task executor into a queue or any object at the start of model in the process flow. This doesn't happen if my task executor is created inside the network node. I am unable to upload the model.

I guess its a bug which causes the task executor to fly away randomly in the former case before joining back the network node its supposed to start with.

0 ·

Ryan Clark commented · Mar 23, 2022 at 04:02 PM

Hi @Kashif K,

We haven't heard back from you. Were you able to solve your problem? If so, please add and accept an answer to let others know the solution. Or please respond to the previous comment so that we can continue to help you.

If we don't hear back in the next 3 business days, we'll assume you were able to solve your problem and we'll close this case in our tracker. You can always comment back at any time to reopen your question, or you can contact your local FlexSim distributor for phone or email help.

0 ·

Ryan Clark commented · Mar 29, 2022 at 05:04 PM

Hi @Kashif K, was Jason Lightfoot's answer helpful? If so, please click the "Accept" button at the bottom of their answer. Or if you still have questions, add a comment and we'll continue the conversation.

If we haven't heard back from you within 3 business days we'll auto-accept an answer, but you can always unaccept and comment back to reopen your question.

0 ·

Answer 1 · 2022-03-23T23:49:39Z

Jason Lightfoot answered Mar 23, '22 Kashif K commented Apr 14, '22

This sounds like a bug relating to travel coordinates not being translated to the container of the traveler - a similar post recently saw the same thing with patients moving to a waiting line - which has been noted.

· 1

Kashif K commented · Apr 14, 2022 at 07:22 PM

Thank you!

1 ·

question