how it's possible to release only one brown item from source 2 between a white and silver item?
Do I need to set additional labels or is it possible to work with the "type" labels which are set in both sources?
Thank you very much.
How to resume by type via standard trigger?
FlexSim 21.2.3
Hi @Simon S5, was Ralf Gruber's answer helpful? If so, please click the "Accept" button at the bottom of their answer. Or if you still have questions, add a comment and we'll continue the conversation.
If we haven't heard back from you within 3 business days we'll auto-accept an answer, but you can always unaccept and comment back to reopen your question.
Simon,
the model conveyor-stop-resume_RG.fsm attached does what you asked for. In the process flow I check if the leaving item from the source has a Type label value of one. If so, I create a brown item in the queue otherwise I do nothing.
Good luck
Thank you Ralf,
I think I did not express myself well enough. My goal was to sort the items in the order white, brown, silver, blue, white, brown,... with traffic rules in the crossing area before they go into the sink (only one item from each color). I tried using trigger commands like "send message", "resume" instead of process flow.
The attached model shows how this can be done by just using the triggers on the decision points. Each decision point has two labels: "CurItem" stores which type last entered the intersection and "ActiveItem" stores if there is currently an item waiting at the decision point.
When an item arrives, it is stopped if it's type is not the one following the "CurItem" label.. When an item continues, the label is incremented and a message is send to the connected decision point (with a 2s delay) which causes it to reevaluate whether a waiting item can be send now.
The model also a contains an alternative solution using a process flow. The logic behind it is the same. The advantage the process flow has over the 3 logic is that the token of a waiting item can directly react to another item moving into the intersection ("Wait for Event" listening for other tokens exiting the delay activity) instead of having to send a message. This makes it much easier to scale up, in case an intersection has more than 2 incoming conveyors.
18 People are following this question.
