question

G C avatar image
2 Likes"
G C asked G C commented

Operator group with state change event troubleshoot

help.fsm

I have a backorder re-evaluation event on my operators and they should be pushed to the list (see under "MainFlows" "opVaOutGrp" under the advanced view). I use this to acquire an idle "opVa" operator based on "isIdle" expression. It seems to work fine but will eventually break and only 1 of the 3 operators will be re-evaluated (seems to be after my "BatchAndTransport" subflow is used??).

If you watch the "opVa" operators after the "VaOut1" "routingNumber" process (see globaltable "processControl") this is where it starts to go haywire.

I can't for the life of me figure out what I am doing wrong.

FlexSim 16.0.6
process flowgroups
help.fsm (860.2 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

Jacob Gillespie avatar image
2 Likes"
Jacob Gillespie answered G C commented

When I run your model these two tokens are quickly stranded here trying to Acquire stnMannix1.

As you can see the selected token has Acquired opVaOut1 and the other token has opVaOut2. These two operators are forever waiting for stnMannix1 to have no content but it never empties.

So it seems your problem isn't the "isIdle" expression. I hope this helps you figure out your problem.


troubleshoot.png (30.2 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.

Jacob Gillespie avatar image Jacob Gillespie ♦ commented ·

@G C I'm not sure how you got it working. Following your description didn't fix the issue for me.

The reason these two tokens are never able to acquire the station is because they use this query:

The problem is that this is never reevaluted. To make it reevaluate you need to click the advanced button under the resource's menu and then set a Back Order Reevaluation Event under the Back Orders tab of the properties window.

2 Likes 2 ·
query.png (9.2 KiB)
backorderreevaluation.png (18.1 KiB)
G C avatar image G C Jacob Gillespie ♦ commented ·

Yes, sorry I never followed up with this, but that is how I eventually resolved this as well.

0 Likes 0 ·
G C avatar image G C commented ·

So I added stnMannix1 into its own group (even though there is only 1) and re-referenced the corresponding activity (under "MainFlows") and now it seems to be working. However, I don't understand why I had to make it a group.

0 Likes 0 ·