Hi,
I have attached the model, model certainly stops working at time 5092 without giving any error messages or having any other issues. I would appreciate your suggestions. sample-model.fsm
Thanks in advance.
Model stops working at certain time
FlexSim 17.1.4
That's peculiar, I'll let one of the developers know, to help debug what the problem could be.
So we looked at your model more in depth, and found that your logic gets into a loop, which causes your model to crash. You have an Event Triggered source which creates a token every time something is pushed to a list, but then that token gets to an activity where it pushes to the list, creating another token, which then gets to the same activity, over and over.
Instead, change your Event Triggered source to listen to the On Entry of the queue itself instead of every time an item is pushed to a list.
Thanks, @Sam Stubbs. But if I changed the event triggered source to the On Entry of the queue, I am struggling to achieve the FIFO strategy (based on entry time of the item in the queue) in acquiring the operator.
Basically, in this model, I am trying to send items to floor storage based on three conditions
1. Match Itemtypes
2. Max content
3. FIFO
I can achieve the first two condition by using match item type codes (Set Destination activity) and Max content by checking the content in Floor storage subnodes length.
When floor storage reaches its max content, I push token again to List2 where the entry time of that particular token overwrote. This makes me difficult to achieve the third condition which is FIFO for acquiring the resource. Is there any way to give priority to that particular token to achieve that FIFO strategy?
I see. Then if you NEED to keep the trigger based on the push/pull of the list, then you'll need to add another bit of logic, that makes sure that you don't get into that infinite push/pull loop. Perhaps have a decide activity after the initially created tokens, that determines if the number of tokens exceeds a certain number, to send that token to the sink. Then you won't keep perpetually creating tokens. But I'm not sure if that works for your model. Whatever you do, you need to add another "safeguard" decision point somewhere after the Event Triggered source, and before the Push to List, to check to make sure conditions aren't going to loop.
Thanks Sam for your suggestions. I will work on adding decision activity before push to list. Please let me know if you have any other suggestions to overcome this issue.
7 People are following this question.
