Orders stuck in combiner

Orders stuck in combiner

kleopatra_a
Not applicable
13 Views
4 Replies
Message 1 of 5

Orders stuck in combiner

kleopatra_a
Not applicable

[ FlexSim 19.2.4 ]

Hello,

I want to send an order to the spesific Queue (clients) but once the order is ready, it does not leave the combiner.

ReacuTrucks1.fsm

0 Likes
Accepted solutions (1)
14 Views
4 Replies
Replies (4)
Message 2 of 5

patryk_u2
Not applicable

This is because the entire order is not completed. the wrong operator for transport is introduced on some queues

1644591754875.png


Shoud be current.centerobject[1]


0 Likes
Message 3 of 5

kleopatra_a
Not applicable

So i need to change all the transporter commands to this:

"current.centerobject[1]"

?

0 Likes
Message 4 of 5

jason_lightfootVL7B4
Autodesk
Autodesk
Accepted solution

The reason is that when the operator is busy, they send any new job to the dispatcher (the output of the operator). The dispatcher doesn't have anything connected on its output, so the job just sits there. If you look at the component list table you will see that the combiner thinks all quantities have been satisfied.

The way you've connected this up makes sense if you want to first give the specified operator the chance of doing the job, but then if they are busy have the dispatcher choose someone for the job - but for that to happen the dispatcher needs output connections to all the operators.

0 Likes
Message 5 of 5

jason_lightfootVL7B4
Autodesk
Autodesk

Usually it's easier to refer by centerport connection - the problem with your Model.find("Operator7") is that if you have a hierachical model then sometimes the operator location is not 'model' so it won't find it. Another way is to use a pointer label and sample the operator object directly - this is good if you find you have many centerport connections and managing the ranks becomes a nuisance.

But this change isn't a solution - see my answer.

0 Likes