Events are moments in time that can be used to trigger actions in your program. They allow functionality similar to that provided by a 7-day time clock.

Each event can be set to trigger at a particular time of day on any combination of the days of the week. Each event consists of an hour, a minute and a day mask.

The events behave in such a way that an event can only be read out as True (tripped) once per matching time and day. Also, it must be read out during the exact minute it trips, or it will be missed. For example, if an event is set for 14:34 each Monday and Tuesday, then:

• If tested at 14:34 on Sunday it will be False (not set for Sunday)
• If tested at 14:33 on Monday it will be false (too early)
• If then tested at 14:34:05 on Monday it will be True (first test during the “golden minute”).
• If then tested at 14:34:25 on Monday it will be False (it has already be tripped and read out today).
• If then tested at 14:33:59 on Tuesday it will be false (too early)
• If then not tested again until 14:35:00 on Tuesday it will be false (it was not tested during the “golden minute”, so it missed out entirely on Tuesday).

The event number will be jndexed when executed inside a MultiTrack task and will be indexed if the instruction is preceded by the IasJ: precode. This can be extremely useful for multi-channel applications, say controlling 4 zones of lighting.

Please refer to the product documentation for your particular controller to find out how many events it supports.