Timetables
A timetable lets you schedule when scripts are started. By creating multiple timetables you can define different automation scenarios for your layout — for example, a busy morning schedule, relaxed afternoon freight traffic, or a night mode with minimal movement.
Creating a timetable
Navigate to Timetables in your profile and tap the + button. Each timetable has the following settings:
- Name — A descriptive label (e.g. "Express schedule", "Freight operations").
- Show in Throttle — When enabled, the timetable appears in the automate tab of the throttle for quick start/stop control.
- Start script (optional) — A script that runs automatically when the timetable is started. Useful for preparing your layout (e.g. setting initial turnout positions or activating lighting).
- Stop script (optional) — A script that runs when the timetable is stopped. Useful for cleanup (e.g. returning accessories to a neutral state).
Entries
Each timetable contains one or more entries. An entry defines when something should happen and what should run.
Time condition
Times are specified as hour : minute and matched against the model clock, so the schedule scales with the speed and starting time you set there.
WARNING
The model clock is paused by default. A timetable will not advance until you start the clock from the Clock row at the top of the automation tab.
Both hour and minute support wildcards:
| Time | Triggers |
|---|---|
2:30 | Once, at 2 hours and 30 minutes after start. |
*:15 | Every hour at minute 15. |
0:* | Every minute during the first hour. |
Script selection
Each entry can run a script in one of two ways:
- Specific script — Always runs the same script.
- Random script by tag — Picks a random script from all scripts with a matching tag. Each time the entry triggers, a different script may run. This is a great way to add variety — for example, tag several departure scripts with
departuresand let the timetable pick one at random every few minutes.
Execute events
A timetable can also be started by an event using the same execute events that scripts use — feedback, accessories, vehicles, clock, cameras, variables, script state, or system startup. Configure events from the timetable editor's Execute events row.
When any configured event matches an incoming event and the timetable is not already active, the timetable starts (its start script runs, if any). Manual start/stop continues to work alongside event triggering.
INFO
Events only start an inactive timetable; they do not stop a running one. To stop a timetable from a script, use the Control timetable action.
Running a timetable
Start a timetable from the timetable editor (play button), the automate tab in the throttle, an event (see above), or the Control timetable action inside another script. The timetable requires track power to be on and automation to be enabled.
Once started, the timetable evaluates its entries every minute. When a time condition matches, the corresponding script is executed. Timetables run in the background and do not block manual control.
You can run multiple timetables simultaneously for complex scenarios, or stop any timetable individually at any time.

