question

mni_pei avatar image
0 Likes"
mni_pei asked mni_pei commented

Why can’t AGV load item?

1720026367162.png

I set the item to be different colors.

Now I want AGVs can load items according to the color of the item (I set this label to "Type").

But this doesn't seem to be going well.

Only TaskExecutor 1 successfully loaded the item according to my instructions, other TaskExecutors failed.

( TaskExecutor 1 successfully load item of Type 1 and 2 )

1720026881300.png

I have a confusion how to let Task Executors load item successfully.

Any help would be appreciated.

Example2_try to truely multiload.fsm


agvlabelload unload
1720026367162.png (398.9 KiB)
1720026881300.png (222.5 KiB)
example2-try-to-truely-multiload.fsm (88.7 KiB)
5 |100000
Toggle Comment visibility. Current Visibility: Viewable by all users

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 mni_pei commented

The unloaded items are not being pushed to the list because the queues are not part of the "LoadPort" group.

Also, each token in the loading subflow pulls up to 7 items causing further tokens to no be able to pull any items. I'd assume each token should only pull a single item here.

1720073419653.png


1720073419653.png (21.8 KiB)
· 3
5 |100000
Toggle Comment visibility. Current Visibility: Viewable by all users

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

mni_pei avatar image mni_pei commented ·

Dear @Felix Möhlmann ：

Thank you for your reply.

I followed your suggestion to make queues be part of the "LoadPort" and I changed the numbers to 1 in "Pull from List". Now the model looks better.

1720079146845.png

However, there is another problem I encounter.

All TaskExecutors always load item from "21_In" (the Queue closest to Source) rather than load item from specific Queue, and that is not I want.

1720080634439.png

As you can see, when TaskExecutor 3 arrive at "141_In" , TaskExecutor 3 will load items which is actually from "21_In".

But when I adjust the arrival schedule as follow , the above problems will not occur.

1720080347014.png

Do you know why this happens?


0 Likes 0 ·
1720079146845.png (228.1 KiB)
1720080347014.png (433.5 KiB)
1720080634439.png (480.3 KiB)
Felix Möhlmann avatar image Felix Möhlmann mni_pei commented ·

All items are pushed to the same list and by default the oldest ones will be pulled first. You can partition the list by the queue name and have the task tokens pull from the correct partition. Similar to how you do it when pulling from the unload list.

1720086150902.png

1720086175638.png

0 Likes 0 ·
1720086150902.png (35.2 KiB)
1720086175638.png (20.3 KiB)
mni_pei avatar image mni_pei Felix Möhlmann commented ·

@Felix Möhlmann

Thank you very much! !

The problem has been successfully solved .

0 Likes 0 ·