Code generated AGV Network

Code generated AGV Network

steven_chen1
Not applicable
6 Views
3 Replies
Message 1 of 4

Code generated AGV Network

steven_chen1
Not applicable

[ FlexSim 21.1.5 ]

Hello,

From this topic here I learned that after modified agv path/cp location, calling function "finalizeSpatialChanges" is necessary.

But this function may cause exception randomly if there are lots of agv path/cp. The exception only in FlexSim 2021 Update 1 and above.


FlexSim 21.0.10 has no exception.

codegen_agvnetwork_v21.0.fsm


FlexSim 21.1.5 ~ 22.1.1 may cause exception.

codegen_agvnetwork_v21.1.fsm

finalizespatialchangesexception-v211.png

0 Likes
Accepted solutions (1)
7 Views
3 Replies
Replies (3)
Message 2 of 4

jason_lightfootVL7B4
Autodesk
Autodesk
Can you help us identify the pattern that makes this happen? It seems like it's far from guaranteed.
0 Likes
Message 3 of 4

steven_chen1
Not applicable

For 21.1 and above, this exception may happened but not every time.

I set breakpoint at function_s(finalizeSpatialChanges) to see which path/cp causes the exception. It's true that a specific path/cp caused the exception, but after reboot my PC or run the model in different day, I got different path/cp causing issue.

I never found issue in version 21.0 so I think there could be some changes between 21.0 and 21.1 that causing issue.

Also I notice that despite multiple routes have same travel distance to destination, the AGV always chooses same route in 21.0. I guess the result determined by node pathPoints of AGVNetwork. Executing finalizeSpatialChanges creates subnodes in pathPoints, the created subnodes always in same order in 21.0, but the created subnodes in 21.1 seems to be random, results AGV chooses different route after network rebuilt. Perhaps this is reason why finalizeSpatialChanges causing exeception sometimes.



0 Likes
Message 4 of 4

kavika_faleumu
Autodesk
Autodesk
Accepted solution

Hey @Steven Chen, thank you for pointing out this difference. I've submitted a ticket to the dev team and a fix should be available in future versions!

0 Likes