TimeTables strange behaviour?

I've found a strange behaviour if I use weekly time tables:

The simulation model starts at 3 AM, the shift is working from 4 am to 18 pm (Monday - Friday). After the weekend the shift starts at midnight instead of 4 am.

Are there any dependencies which I'm not aware of?


I'm using FlexSim 7.0.2 - 64bit.

When I run your model, the shift still starts at 4 AM on Monday after the weekend.

The Down Function and Resume Function don't only fire at the points when it changes from operational time to down time and vice-versa. Those functions also can get fired at various repeat times even if it will still be in the same state.

For example, it went down at Friday at 8 PM and that downtime lasts until Monday at 12 AM when it goes back up to decide whether to go down again. So there is a Resume on Monday at 12 AM and another Down also on Monday at 12 AM. So even though the triggers fired, the object is still down at 12:01 AM as it should be.

The same thing is also happening at 3 AM. The triggers are firing and the object is still down as it should be. It doesn't come back up (and stay up for a time period longer than 0 seconds) until 4 AM as you specified in the schedule.

I don't understand what you mean by "Are there any dependencies which I'm not aware of?".

Originally Posted by Phil BoBo

The Down Function and Resume Function don't only fire at the points when it changes from operational time to down time and vice-versa. Those functions also can get fired at various repeat times even if it will still be in the same state.

This is the dependency I meant

My problem is that I have to use more than only the stopobject and resumeobject commands. Stopobject and resumeobject are accumulated and work as you told us. But most commands aren't accumulated... (I've added a modified modell with a dashboard. The color of the processor and a tracked variable should show the running state based on the time table functions. The interesting part is between Sunday 23:59 and Monday 04:01).

Following Ideas popped into my mind to solve this:
- User Events instead of Time Tables, but without the nice table view
- Add a control mechanism to Down Function and Resume Function to execute the code only to the right time

Any thoughts or hints?

Thanks

Am I understanding right, that it is not recommended to use other commands than:

stopobject();
resumeobject();

in Functions of time tables?
Are there any rules describing when trigger fires while staying in state?

Greetings

Originally Posted by Carsten Seehafer

Following Ideas popped into my mind to solve this:
- User Events instead of Time Tables, but without the nice table view
- Add a control mechanism to Down Function and Resume Function to execute the code only to the right time

Any thoughts or hints?

The TimeTables do execute Down and Resume more often than necessary. It is an old object that was designed that way in the beginning for simplicity. It just follows the specified table of times and durations. The graphical time editor just creates that table. It creates that table as simply as possible, without regard for minimizing events.

It is on the development list to update the time tables to create events one at a time and only when necessary, but this is a lower priority than other things because the existing functionality works for bringing objects down at specified times in a specified states for a specified durations, even though the triggers fire more often than seems necessary.

You can set the "Repeat" combo box to Custom or None if you want to specify the times, states, and durations directly in the table for more control.