ATTENTIONThis FlexSim Community Forum is read-only. Please post any new questions, ideas, or discussions to our new community (we call it Answers) at https://answers.flexsim.com/. Our new Question & Answer site brings a modern, mobile-friendly interface and more focus on getting answers quickly. There are a few differences between how our new Q&A community works vs. a classic, threaded-conversation-style forum like the one below, so be sure to read our Answers Best Practices. |
flexsim.com |
#1
|
|||
|
|||
initlaizing rack
Hi everybody,
I wonder what would be an efficient way of initializing a rack on the OnReset trigger? some thing better than dirty tricks. I do appreciate any comment. |
#3
|
|||
|
|||
Thanks for the comment.
This using this, even if we set the delay to zero it only generates the box in the run time and not by reset, even if it is put in reset trigger. another thing is that it keeps producing and removing containers from the rack as it likes during the simulation. |
#4
|
|||
|
|||
FlowItems can't exist at zero time.
If you want to look nice, create VisualTools that look like your FlowItem and have them created with the OnReset trigger, then destroy or hide them with the OnMessage trigger and create your real flowitems there. If your rack randomly creates FlowItems in between the simulation, make sure that no other objects fire messages to your rack. Or if so and it's necessary, use messages with paramteres and do a case differentiation in the OnMessage trigger whether it's your initializing routine or something else. |
#5
|
|||
|
|||
Thanks for the comment.
well the rack is aware who is the message sending object and only do it for that but still generates some boxes. |
#6
|
|||
|
|||
If it's a delayed message that's creating them - step through the model and see when those events get created. You can also find the senddelayedmessage instances and place breakpoints on those lines so you know when they are firing.
If you've other places where a direct message call is made then use the debugger to trace back which event and trigger sequence is calling the message (v6). If that doesn't work for you, then post the model and we'll identify the problem for you. |