Token not move

[Jonathan_Huang]

[ FlexSim 23.1.2 ]

Hi Everyone

In my attached model

Rhino 5 20240412.fsm

Please increase speed and run the model to 8:44 AM

Then help me to see the Frame OP_T3 in Process flow

The token for wait for event cannot move to Release activity

So the task cannot be reset to run the next task sequence

Maybe I made some mistake

Please help me to see the problem

I tried long time but can't find out

Thanks and best regards

[moehlmann_fe · Accepted solution]

The logic is correct. Queue17, which T3 feeds into has a maximum content of 1 and there seems to be no logic in place that moves items out of it. So T3 is simply blocked and can't release the item.

I also don't understand the purpose of the Process Flow. If T3 is empty, the item is moved there through a port connection in the 3d model. Only if T3 is busy is the item send to a queue, which then puts the item onto a list and the Process Flow moves the item into T3 anyway, ignoring that it could not receive the item through the port connection.

[Jonathan_Huang]

Hi Mr Felix

Thank you for instruction

I deleted the port connection to T3 in 3D model and then set Queue17 maximum content greater than 1 and the token was moved.

[Jonathan_Huang]

I am sorry to reopen this issue but when I set T3 and T3_2 process time =20s. The token was pass through waiting for event activity. But when I changed it to 100s. The token cannot move.

Please help me

Rhino 5 20240413 ver1 NG.fsm

[Jonathan_Huang]

You can check in this process flow in the model

[Jonathan_Huang]

You can move related objects to another place to make it easier to see the connection in 3D model

[Jonathan_Huang]

This model is easy to see

Thank you!rhino-5-20240415 NG ver.fsm

[moehlmann_fe]

Eventually Queue24 is full and the blockage starts to propagate through the model backwards until all process are blocked.

Other than that I don't see any issue though.

[Jonathan_Huang]

It was because T3 process time = 20s. If change it to 100s. It will not move. Please try to set T3, T3_2 process time to 100s and run the model

Thank you!

[moehlmann_fe]

The child tokens (the ones becoming stuck) currently read all labels from the parent token. So when the parent pulls a new item and overwrites the "item" label, the first child will now wait until that new item exits T3. This then also happens for the second token: The item reference changes before the process is done.

In "Create Tokens", copy the labels to the created token, so they read their own rather than the parent's "item" label.

[Jonathan_Huang]

Hi Mr Felix. I followed your instruction. But it was not changed

[Jonathan_Huang]

Sorry Mr Felix

It worked. Thank you so much!