How to handle collision when using A* Navigator ?

[aditya_prakash1]

[ FlexSim 16.1.0 ]

Has anyone worked on Collision handling on a A* Navigator. I want to know, how to handle collision on A* ? Also the pre-defined option for "createtraveltoloctask" for turning left, doesn't work on A*. [Attached model.] agv-proto1.fsm

[sam_stubbsYXX86]

@Aditya Prakash You are right that the "Turn to the Left" option in the Handle Collision field conflicts with the timing and pathing of the AStar navigator. It's designed to handle collisions in the default navigator. I'm currently working on finding a potential work around to the AStar collision issue, and wanted to give you an update letting you know.

[joerg_vogel_HsH]

@Sam Stubbs in the pre-modules version the Flexsim code was visible in library tree. I know that the new approach secures the code from copying. But is it still possible to write own script code under the nodes in the library and so to change the behaviour of the module. If it is still possible in which node should the code be written and which parameters are parsed into that node by default for Aditya's experiment.

[sam_stubbsYXX86 · Accepted solution]

So unfortunately, after trying different approaches to tackle this issue, and after talking with the developers, it seems that AStar in its current implementation is not really suitable for custom intervention. However, I would encourage you to post an Idea here on Answers requesting a dynamic AStar module that implements collision detection. That would let the developers know that there are users interested in this functionality.

[JordanLJohnson]

As far as I know, the modules (AStar, Process Flow, Conveyor, and AGV) cannot be modified using extra script nodes in the tree. While many variables governing logic are exposed (deep search in AStar, for example), the logic itself is entirely contained in the DLL.