Transporter collision redirection

Question

question

Martin asked May 28, '24 Felix Möhlmann answered May 29, '24

Transporter collision redirection

Hello,

I have a model with four transporter HiLos moving flow items from a floor storage object to a rack. Part of what I want to simulate is spatial issues, such as space between racks and other objects, and traffic congestion related to the HiLos and also some operators at the floor storage location. I set up A* navigation and checked collision avoidance and I have the transporters set up as travel members. But it doesn't seem to influence their behavior as they pick up items from the floor storage and follow generally the same path to unload them at the next available slot on a rack.

How can I best implement collision avoidance so that they will not travel through each other, and then also to measure when the task executor is blocked due to collision avoidance? I also don't want to cause them to get stuck perpetually.

Thanks!

Martin

CQ 2.fsm

Import.xlsx

Software Version:

FlexSim 24.1.0

collision avoidance

cq-2.fsm (681.3 KiB)

import.xlsx (8.7 KiB)

· 1

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.

Jeanette F ♦♦ commented · May 28 at 06:15 PM

Hi @Martin,

Thank you for contributing to our community! We couldn't identify a maintained license or subscription linked to your account.

You may need to update your profile information to identify yourself as a license owner or their associate. Check out our article for how to ensure you receive timely support. If you update your profile comment back to let us know - we'll adjust the priority of your post accordingly.

If your current license is expired, please contact your local distributor to renew.

0 ·

Answer 1 · 2024-05-29T06:16:38Z

Felix Möhlmann answered May 29, '24

A traveller in on an A* grid will only ever occupy a single grid cell at a time, regardless of its size. If the object is larger than the grid spacing, this can lead to overlap between travellers. So as a first measure you could increase the grid spacing.

Other objects to influence the behaviour are:

- Barriers: Define regions of the grid that a traveller is not allowed to access (or only under certain circumstances)
- Dividers: Defines boundaries between cells that a traveller can not pass (think of this as a wall). Again you can set up rules that allow to ignore the barrier under certain conditions.
- Preferred/Mandatory Paths: These increase the priority by which travellers will use certain paths when travelling in a specific direction. Can be used to setup 'roads'.
- Control Areas: Limit the number of travellers that can be inside an area at a time.

cq-2-fm.fsm

When a traveller becomes blocked because it can't allocate the next cell along its path, the "On A Star Block" event should fire, for which you can add a trigger to the Task Executers.

cq-2-fm.fsm (704.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