question

Allister Wilson avatar image
0 Likes"
Allister Wilson asked Clair A commented

Non-blocking conveyor picking using robots, how should cancelled picks be handled?

In the attached model, there's a robot picking items from a conveyor to fill a batching queue.

The transfer is setup to not stop items, and it seems unpicked items aren't (always?) releasing their reservation in the queue when they pass the end of the transfer, resulting in items no longer being sent to the queue and the batch never being completed.

Is there something else I should be doing to ensure items release their "spot" when they leave the transfer area?

I'd be interested in possible workarounds if this turned out to be a bug.

conveyor-robot-ignore-late-picks.fsm

FlexSim 16.2.1
conveyorrobotpickingexit transfer
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

Joerg Vogel avatar image
1 Like"
Joerg Vogel answered Clair A commented

If the item reaches the end of the ExitTransfer, a Photoeye trigger create an aborting and destroying tasksequence for the current transport tasksequence. The Trigger looks for any existing tasksequence in the tasksequencequeue, too, wether it is needed or not, which transport the blocking item.

fetch-items-synchronous-conveyor.fsm


· 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.

Clair A avatar image Clair A commented ·

Thank you very much for your answer Jörg, it's working perfectly with this arrival schedule.

However if you increase the arrival rate like in the attached model synchronous-conveyor-arrival-rate-incr.fsm, you get boxes hierarchically inside the exit transfer, and visually stopped out of the conveyor. When adding a breakpoint in your code, this occurs when transportoutcomplete is called.

fetch-items-

0 Likes 0 ·