Kinetic tracked variable error with wait for event

Question

question

Patrick Zweekhorst asked Jun 6, '19 Patrick Zweekhorst commented Jul 22, '20

Kinetic tracked variable error with wait for event

Hi,

I get an error while running the attached model.
At time 600 a trigger level is reached for the kinetic tracked variable (in the Wait for trackedvar ).
There are two event that I am waiting for at this wait for event, the first one fires. The problem seems to be that the second listener is not removed correctly. If you look at the event list there is an event scheduled at time 3540 (that would be the time of the second event in the wait for event if nothing would change). When the tokens falls out of the wait for event this event seems to be incorrect. The object is no longer valid, and after the breathe activity the event shouldn't even happen (the rate is set to 0).

Why is the object invalid and what goes wrong here?

Thanks for your time,

Patrick

testmodelkintracked.fsm

Software Version:

FlexSim 19.0.3

wait for event kinetic tracked variable

testmodelkintracked.fsm (28.9 KiB)

· 1

Patrick Zweekhorst commented · Jun 19, 2019 at 12:07 PM

Is someone else also able to reproduce this bug? Or is it already on the dev list?

0 ·

Answer 1 · 2019-06-19T19:41:09Z

Matthew Gillespie answered Jun 19, '19 Patrick Zweekhorst commented Jul 22, '20

This looks like a bug to me. I'll add it to the dev list.

· 3

Patrick Zweekhorst commented · Jun 30, 2020 at 09:38 AM

Hi @Matthew Gillespie,

Is this bug still on the list or should it have been fixed? A colleague of mine has a similar problem right now (see also this post: https://answers.flexsim.com/questions/87236/kinetic-tracked-variable-creates-a-strange-event.html )

0 ·

Matthew Gillespie ♦♦ Patrick Zweekhorst commented · Jul 21, 2020 at 06:41 PM

This bug was fixed for 19.0.7 in November 2019 - "Fixed a bug with kinetic tracked variable level crossed events." https://docs.flexsim.com/en/20.2/Reference/ReleaseNotesAndHistory/#19-0-7

I see that Jordan added the other issue to the dev list. Are you still seeing issues with this model?

0 ·

Patrick Zweekhorst Matthew Gillespie ♦♦ commented · Jul 22, 2020 at 06:44 AM

Hi @matthew.gillespie,

Yes we still have the same issue with this model, but taking a closer look, it might be more or less the same thing as the other post. In this model we still see the invalid event at time 3540 (you can see this event if you run the model to the stop time)

0 ·

question