question

pc neo avatar image
0 Likes"
pc neo asked pc neo commented

network nodes choose path for taskexecuter

I wanted to be able to "direct" a path for task executer using closing/opening of edges on network node. In the attached model, there is a OnArrival trigger added on highlighted node to close edge, and next node has trigger OnContinue to open edge. It is seen that if the "close edge" is 1, task executer will choose the straight path. But if the "close edge" is 2, task executer will block.

I'm expecting that when "close edge" is 2, the task executer will choose the longer path to travel to destination. Is this a bug?sample_NN_closeedge.fsmsample-nn-closeedge.png

FlexSim 23.2.2
network node
· 2
5 |100000

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

Joerg Vogel avatar image Joerg Vogel commented ·

A path is called edge. Your network nodes have two paths. And this means you have two edges. The order or rank depends on the order they were built or connected. You can see it properties which path is numbered as 1 or 2.

0 Likes 0 ·
Jason Lightfoot avatar image Jason Lightfoot ♦♦ commented ·
Tip: If you clear the object's reset position it will snap to its home network node like AGVs do to their starting control point.
0 Likes 0 ·

1 Answer

Jason Lightfoot avatar image
1 Like"
Jason Lightfoot answered pc neo commented

As Joerg says the edge corresponds to the rank of the output connection:

1701350671757.png

But you don't need to close and reopen edges you can just override the route by returning the new edge number in the arrival trigger of NN1 in this case:

if (traveler.subnodes.length)   // loaded?
    return 2;   // continue via edge number 2

1701350671757.png (3.1 KiB)
· 1
5 |100000

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

pc neo avatar image pc neo commented ·
Thank you this is what I need. :)


0 Likes 0 ·