Hi,
I tried to delay the events of a processor, but it seems that the message parameters of a message that is delayed get lost. See the attached model where the problem is found. Msgparam1 and msgparam2 seem to point to somewhere in memory space, but not where they should.
testmessagebehaviouratstop-delayeventsofobject.fsm
When using delayevents the same model works as it should.
Could this be a bug?
Thank you!
Kind regards,
Axel
HI @phil.bobo
Any clue why this happens or if it has been fixed in some version?
Thank you!
Kind regards,
Axel
Sorry for the delay in answering this. Somehow this question got lost.
Yes, this is a bug in delayeventsofobject(). That command is re-creating the event at a new time and deleting the old event. This is not working correctly with delayed message events.
I'll add a case to the dev list.
In the meantime, you should avoid using that command. For example, in your model with a station, send the messages to a processor instead of the station, and then when the station goes down, stop the processor, and when the station goes back up, resume the processor. That way, you can avoid using delayeventsofobject().
This has been fixed. The fix will be in the FlexSim 18.0.9 and FlexSim 18.2.3 updates.
Great! Thank you for getting it fixed.
Does this mean that stopping a station also delays the events of the objects as with e.g. processors or do I still need to use delayeventsofobjects to delay the events of the station?
Thank you!
Kind regards,
Axel
8 People are following this question.
FlexSim can help you understand and improve any system or process. Transform your existing data into accurate predictions.
FlexSim is a fully 3D simulation software environment. FlexSim can be used to simulate any process in any industry.
FlexSim®, FlexSim Healthcare™, Problem Solved.®, the FlexSim logo, the FlexSim X-mark, and the FlexSim Healthcare logo with stylized Caduceus mark are trademarks of FlexSim Software Products, Inc. All rights reserved.
