The second operator doesn't move according to the process Flow

Question

question

lili Suspended asked May 17, '23 lili Suspended commented May 22, '23

The second operator doesn't move according to the process Flow

Hi everyone!

I have a model where two operators must follow a crane and supervise the loading/ unloading operation of the crane. I have designed a process flow and everything works except for the second operator. I have tries many different ways of modeling this (including only 3D modeling or, using two dispatchers or task coordination) but when the flow item arrives in the first queue, only one of the operators moves towards the correct destination in all of my different scenarios. The other one skips the moving task and continues through the process flow to the next tasks.

I'll upload my model here.

Thanks in advance!

test3.fsm

Software Version:

FlexSim 22.2.0

process flow operator movement

test3.fsm (71.7 KiB)

Answer 1 · 2023-05-17T13:22:35Z

Felix Möhlmann answered May 17, '23 lili Suspended commented May 22, '23

To use multiple similar/equal objects as a resource you generally add them to a group and then have the resource activity refer to that group. In the attached model I acquire both operators in a single activity and thus also assign both to the same label (which then becomes an array). This is not strictly needed though.

You are also using Event-Triggered Sources in places where it looks like a Wait for Event activity should be used (Item is moved to processor4 -> wait until process finishes -> move on to processor5). An existing token will move through a source without stopping.

test3-fm.fsm

test3-fm.fsm (76.0 KiB)

· 5

lili commented · May 20, 2023 at 12:50 PM

Thank you so much for your help @Felix Möhlmann

I fixed the problem. I have another problem now I think it's similar to the last one. The process flow stops at acquire crane activity and I don't know what the problem is because I don't get any errors or exceptions. Would you mind taking a look at it?

Scenario2-2 - Test_autosave.fsm

0 ·

scenario2-2-test-autosave.fsm (135.5 KiB)

Felix Möhlmann lili commented · May 20, 2023 at 01:52 PM

The uploaded model crashes on reset/run because the M3 machines are set to pull from a list that does not exist.

From I found in the process flow is that you acquire two operators in one activity but then only release one of them later. The Release activity should probably be set to Release All (every object that is assigned to that label).

0 ·

capture.png (35.0 KiB)

lili commented · May 21, 2023 at 05:01 AM

@Felix Möhlmann I deleted M3 machines to avoid complications for now and I set the release resource to release all, but the problem remains. The crane does not move.Scenario2-2 - Test_autosave.fsm

0 ·

scenario2-2-test-autosave.fsm (113.1 KiB)

Felix Möhlmann lili commented · May 21, 2023 at 07:16 AM

This happens because of the split/join. The token that originally acquires the objects is deleted in the Join activity. While the copied references remain on the other token, the Release activities do not work without the original token.

You can make sure that the original token is kept by making sure it enters the Join activity first by placing a 0s delay for the second token.

0 ·

capture.png (15.8 KiB)

lili commented · May 21, 2023 at 09:55 AM

Thanks for your help @Felix Möhlmann I fixed my model

0 ·

question