Specifications

RFC-1 Advanced Operation page 6.31
6.7 Timed Events
Incorrect use of the following information can cause unexpected or undesirable behavior. We
strongly recommend that you understand the basic operation of the RFC-1 and the specifics of
the installation before continuing. Please read the documentation above that describes the
Advanced Programming Mode before continuing if you have not done so already.
The RFC-1 has an internal clock and calendar that allow it to trigger an action sequence by the time and date with a
wide variety of options. Memory is available for at least 48 date/time triggers but there may be more depending on
the installation. This will be discussed later in this section.
Timed events are disabled when a user is connected. This includes local and remote connections in both voice and
data modes. When a connection is active, any timed events that are scheduled will not occur either during the
session or after it ends. The user session completely overrides automated activity. This decreases the potential for
a user and the RFC-1 perform conflicting activities.
New telemetry reference values for the alarm system are taken after an action sequence completes. This includes
action sequences that are triggered by the internal clock/calendar. This is usually desirable as it prevents the RFC-1
from interpreting a programmed activity as an alarm condition and taking inappropriate corrective actions.
If the RFC-1 is used to adjust equipment to an out of tolerance condition, it assumes that this is an intentional action
and does not trigger an alarm. If this not the desired behavior, the telemetry reference scan can be inhibited through
action sequence programming discussed previously.
6.7.1 Enabling Timed Events
The clock controls the master on/off switch for timed events. Set the clock and calendar with valid date and time
information and any timed events that are programmed will be active.
6.7.2 Disabling Timed Events
When the RFC-1 loses power the clock resets to 00:99:00 and freezes. Timed events cannot occur in this state.
Likewise, to disable all timed events, set the clock hours to 00 and the minutes to 99. Disable an individual timed
event by writing its memory block with the value 0. This completely removes the date/time trigger from memory.
6.7.3 Date/Time Triggers and Telemetry Channels—Shared Memory Region
Memory is permanently allocated for 48 date/time triggers in the RFC-1. These 48 date/time triggers occupy
addresses 0256-0639 in the Programming Address Table. Additionally, shared memory is available that can increase
the number up to 80 date/time triggers. The extra memory is taken from memory that would otherwise store
telemetry channel descriptors. Memory for the higher channel numbers that are not commonly used can be allocated
for more date/time triggers.