AnswerHub Upload Issue
Our AnswerHub community currently has a bug that prevents you from attaching your model or other files to your questions. AnswerHub is aware of this issue and they are working on a fix. Until we receive their patch, you can upload your models and other files to FlexSim's file share site. Include the file name in your question so that we know which upload to reference.

question

Kathryn McNeal avatar image
0 Likes"
Kathryn McNeal asked Sam Stubbs commented

Seizing an unavailable resource in process flow does not stop item

In the model attached, there are two processors in the model, but only a single resource available in the process flow. For some reason, items are still going through both processors simultaneously, even if they have not successfully retrieved that resource. I would expect that if a resource is unavailable at the "acquire" step, that the token would stop there, preventing the object that initiated the token from moving forward as well. How do I make both the token AND the object wait until the resource is available?

FlexSim 16.1.2
process flowresourcestop objectacquire
flexsim-help.fsm (21.1 KiB)
5 |100000

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

Steven Hamoen avatar image
0 Likes"
Steven Hamoen answered Steven Hamoen commented

@Kathryn McNeal There is no link between your processflow resource and the actual resources in your model. Your processflow resource is just numeric and 1 and as you see in your processflow there is only 1 token passing and the other tokens are waiting in the acquire so the model behaves correctly. If you want to link the resource to your 3D model, put both processors in a group and on the resource reference, reference the processor group you just made.

· 2
5 |100000

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

I tried to implement this in the attached model, but it still doesn't seem to be working for me. What else am I missing?

0 Likes 0 ·
@Kathryn McNeal

My solution was not correct because if you acquire a processor resource in the process flow, only then the item in the 3D should pass to the processor and because you had a port connection in the 3D they will also continue in there as well. So either control the flow in process flow or in 3D but not in both.

So I changed the model a little. I removed the link between the queue and the processor and let the moving be done in the process flow. And because processor 6 and 9 are serial you only have to acquire the first processor and release when it passes the last one.

When the flowitem enters the queue, the source generates a token and a label with the item is placed on that token. Next when a processor is available the process flow passes on the item to the processor. And then in the waitonevent activity I made sure that the correct token is released by checking the label. I hope that this model is more what you are looking for.

3044-3015-flexsim-help-tal.fsm

0 Likes 0 ·
David Besson avatar image
0 Likes"
David Besson answered Sam Stubbs commented

The 3D logic only triggers events in your ProcessFlow logic BUT is not influenced by it in return.

One solution could be to build a SubFlow for the "Pick Operator" field on the Processors (3D logic -> ProcessFlow). Then the SubFlow stops the Processor if no resources are available (ProcessFlow -> 3D logic).

I hope this will help you.

3015-flexsim-help-subflow.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.

I'm trying to implement this concept in a much more complex model where operators are already being used with the processors. I need to model a limited number of molds that are used for 5 consecutive processes before being released. Is there a way to do this without altering the current operator usage?

0 Likes 0 ·

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

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