Problems with setting AGV speed and Using list to synchronize two task executers

Question

question

shanice.c asked Oct 16, '21 Felix Möhlmann answered Oct 16, '21

Problems with setting AGV speed and Using list to synchronize two task executers

May I ask that I have set the curve path to slower speed, but the task executer seems only slow down at some curve paths, while others don’t. The taskexecuter not slowing is in the right hand side of the model. I have checked the Taskexecuter is set to defaultd AGV. Is there any possibility to make it controlled by some other place, so that taskexecuter is not traveling as I expected.

In the same model, I’m using 2 object process flows to control two taskexecuters, and try to make them look traveling forward and stop at the same pace.

I let the gripper to push to list, then the chasis pull from list, to let them look like ONE but actually they work separately.

I cannot find the mistake why after go through cp above queue8, the token represent gripper would stay in the travel activity(but can not see it move forward in animation).

1016.fsm

Software Version:

FlexSim 21.2.0

lists agvnetworks

1016.fsm (2.7 MiB)

5 |100000

Attachments: Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Answer 1 · 2021-10-16T14:48:46Z

Felix Möhlmann answered Oct 16, '21

I don't see anything wrong with the speed of the AGV. All of the curved paths have different radii/lengths, so traversing them will take varying amounts of time (which gets exacerbated by the minimal lengths - 0.02m to 0.06m is a 300% difference in travel time).

Either adjust them to all have the same length or add custom path types for each one and set the travel time proportional to the length to keep the travel/turning time constant.

The paths of the two task executers in the other area are connected, so the "gripper" gets blocked because the "chassis" has allocated the path.

(At the other connection between straight and curved paths as well)

Having the two components travel together could be achieved much more easily though, by simply moving the gripper into the chassis. It can still be moved individually inside the chassis with the kinematics to pick up the items. You can reference it in the chassis's flow through "current.first" (the first subnode of the chassis). This way, a single process flow can control the entire operation.

This is demonstrated in the attached model.

1016_1.fsm

1634395017907.png (3.1 KiB)

1634395604472.png (24.4 KiB)

1016-1.fsm (105.3 KiB)

5 |100000

Attachments: Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

question