Task executor flies away to a random far distance

Question

question

Kashif K asked Jun 30, '21 Logan Gold commented Feb 5, '24

Task executor flies away to a random far distance

Hi

I have 3 floors (each on a plane of their own) in my model and an elevator that brings operators from 2F and 3F to 1F. I have network nodes on each of the floors and there is one task executor for each floor. The issue arises when my task executor from 2F or 3F goes down from elevator to unload an item on a queue which is on 1F. I connected the network node from top floors to that queue to include all floor network nodes into default network node navigator of all the task executors. But as soon as the task executor gets down from the elevator, he flies away from the elevator to a random far distance (marked as red cross/dot in the pic), and then travels directly to the network node on 1F. This happens on Travel to object activity in process flow. I am unloading my task executor on network node of 1F (unloader is the elevator).
Is there a way to avoid this flying off? How do I make smooth transition between floors?

Software Version:

FlexSim 21.1.4

network nodes elevator task executoir

1625085378029.png (170.5 KiB)

1625085432330.png (49.5 KiB)

· 3

Kashif K commented · Jun 30, 2021 at 08:50 PM

@Logan Gold @Brenton King @Eric M @Emily Hardy

0 ·

Javan commented · Feb 01 at 10:58 PM

Hi, I'm new to Flexsim. This post seemed similar to what I am experiencing but is not using network nodes. I was experimenting with the roomevacuation.fsm file and had agents flying away. I created a new A* grid with +20m Z and a bridge to connect the upper level to the lower level. Agents are created on the upper level and travel to a sink on the lower level. The issue is that some of the agents on the upper level fly away instead of going down the bridge.

File:roomevacuation two level.fsm

0 ·

1706828106274.png (664.8 KiB)

roomevacuation-two-level.fsm (38.2 KiB)

Logan Gold ♦♦ Javan commented · Feb 05 at 04:49 PM

Hey @Javan, please post a new question so we can better help you.

0 ·

Answer 1 · 2021-07-01T17:20:13Z

Eric M answered Jul 1, '21

Hi @Kashif K I was able to replicate the issue using the attached model and provide a solution. I found that instead of moving the transporter to a network node after exiting the elevator, moving the transporter to an object worked to avoid the strange movement. I'm not sure what is causing that weird motion, but sending the traveler somewhere other than the network node helped.

While this does seem to solve the problem, I would probably recommend using an AGV network instead of network nodes and use the AGV Elevator process flow template. It's up to you, though, and you can always make the "send to objects" very small so they aren't visible in the model.

Network Nodes and Elevators.fsm

network-nodes-and-elevators.fsm (58.8 KiB)

question