question

Keter avatar image
0 Likes"
Keter asked Keter commented

Agent model not working on redirectCP

Hello,

I want to use agent system to redirect when two agv are at the same path as first file. However, the agent system I applied didn't work. Hope I can get some suggestion, thanks!


Ori_redirectagvtosiding-v21.fsm

redirectagvtosiding-v21 - agent_added.fsm

FlexSim 23.1.4
agvagent systemredirectcp
5 |100000

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

1 Answer

Felix Möhlmann avatar image
0 Likes"
Felix Möhlmann answered Keter commented

I think the agent system is not a good fit for what you are trying to do. Determining whether the TE actually needs to move to the siding when the proximity trigger fires is complex and, as you experinced, prone to errors and unforeseen issues.

Your original solution of reacting to a failed allocation is the much better approach. Since the agent model is saved in version 23.0 you can benefit from added functionality of this event. There are two additional parameters, one that denotes whether the failed allocation leads to a deadlock and the other stores an array of all involved task executers and control points/areas.

So you can set the source to only create a token if the situation actually represents a deadlock, make one of the TEs move to the siding and, importantly, override the return value of the event with a 1 to suppress the error message about the deadlock. A 1 as return value essentially tells FlexSim that you have handled the situation.

redirectagvtosiding-v23.fsm


· 3
5 |100000

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