AGV Load flow item from Queue before arriving at control point

[meldakroury]

[ FlexSim 23.1.1 ]

I have a model with two assembly lines that meet at a point. I've noticed that in some instances a flow item would show up on the AGV before the AGV arrives at a given control point. Following the process flow, I've noticed that tokens leave the "Travel to Next work Point" activity before the AGV actually arrive at the point, which makes it start the loading process early.

Is there a reason why tokens leave the travel to next work point activity before the AGV actually arrive?

AGVLoadingBeforeCtrlpt.fsm

[jason_lightfootVL7B4]

First of all, it's a good idea to remove/fix all exception messages from the console before posting - unless of course they are the topic of the question.

[jason_lightfootVL7B4 · Accepted solution]

Yes, sorry for this - it's a problem with the standard templates and AGV deceleration such that the travel task completes (firing a pre-arrival event for the control point) before it arrives so that it can decelerate in time if needed. The workaround is to detect the fact that it needs to stop at the next work point and give it another task to stop there. Model attached.

agvloadingbeforectrlpt_jlFix.fsm

[meldakroury]

Thanks, that fixes the issue. However, it changes my logic of having the AGV load to processor, wait until processor finishes processing, then picks up the same item again.

I see where the issue is but I don't know how to fix it.

When we do it this way, after the processor is done processing, the AGV will check if there's work at the current control point first (which is true). However it is then asked to travel to next destination which is token.cp (in this case it's always Control point 1 that have work available).

It travels to controlpoint1 and still loads the item from the processor but at the wrong location.

[meldakroury]

Yes, I agree. Will do next time.

[meldakroury]

It will also cause an interlock when I increase the number of AGVs to more than 1.

[jason_lightfootVL7B4]

This sounds like you just need a process flow that dispatches tasks to specific agvs - not a look for work loop, which is what all the templates a designed around. If the same agv takes the item around the system then when you first assign the agv put a label on the item called 'agv' and point it to the agv. Then just reference item.agv in all the transport logic. You probably don't even need a process flow for most of this - maybe the initial allocation.

[meldakroury]

Thanks, Yes, I'll attempt to do it this way.