question

Peter W8 avatar image
0 Likes"
Peter W8 asked Peter W8 commented

Make the AGV wait for process to finish and two other questions

AssemblyLine_VK.fsm

I have a couple of issues with a model I'm trying to create.

1. Is there a simple solution for making the AGV unload at a processor. Wait at the processor until the processor is finished and then load the same flow item before continuing to the next processor? Right now I'm using the "Use max Wait Timer" under "Is There an Item to Load Here?" in process flow but this is not optimal. Please help me find a better solution.deadlock.png

2. See the attached image, after running the model for about 4900s it comes to a deadlock. It seems to be caused by the processor "HL005" input ports being closed. The processor says it's "idle" which means it should be ready to recieve flow items? Why is this happening and how do I solve it?

3. In the source I create a label (Type) according to a percentage. In addition to this I would also like to ad restrictions that apply to the flow items when they are created in the source, for instance:

AMT_RET(label): Is applied to 21% of the flow items but should not be created more often than every fourth flow item.

This means that flow items labeled with "AMT_RET" make up 21% of all flow items created but the restriction controlls so that they can not be created two or three or more in a row.

I've attached the model if anyone want's to take a peek.


Thanks!

FlexSim 22.1.2
labeldeadlockagv deadlockrestrictionagv wait for processor
deadlock.png (141.0 KiB)
assemblyline-vk.fsm (23.5 MiB)
· 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.

1 Answer

Jason Lightfoot avatar image
0 Likes"
Jason Lightfoot answered Peter W8 commented

1. There is a simpler solution that doesn't use the AGV template. The AGV template is built around the idea that it will travel a circuit looking for work. Your model has the AGV follow an item's process so the process flow should reflect that. Or don't use process flow at all and just reference the task executer as a label on the item in the fixed resource's 'Transport Dispatcher'. I attach an example of this approach.

2. HL005 is pulling its next item from the Queue_others, but since no AGVs are available it just gets stuck there. In the attached model I added a process flow to the first pickup position to assign the AGVs from a list and set the queue SendToPort to "Do not release". The process flow detects the item entry and tries to pull an AGV. It only releases the item when an AGV is available - this will prevent the HL005 deadlock.

3. 21% with the rules you say is basically every 4th or 5th flowitem - so I would keep a count to decide if I'm over or under 21% and label the 4th or 5th accordingly.

assemblyline-vk_jl.fsm



· 11
5 |100000

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