RFC-1 New Features and System Changes page 2.3
Alarm System Updates
The telemetry alarm channel scanning intervals have changed. The factory default scan interval is still one channel
per 10 seconds. Several new intervals have been added including a shorter 5-second interval as well as a very long
240-second interval.
Alarms can be blocked according to the day of the week. As with timed events, the RFC-1 can block an alarm on a
specific day of the week, weekdays only or weekends only.
Alarms can be blocked for a specific month. This allows alarm blocking to “float” from month to month. This will help
stations that operate at multiple power levels.
Action sequences with fixed programming are stored in the system. These action sequences perform common tasks
without occupying any of the user programmable memory space. Pre-programmed action sequences are available to
place telephone calls, print readings to a local printer or print readings to a remote printer. This frees action
sequence 1 and eliminates some potential programming errors that cause the alarm system to not work as expected.
The user programmable action sequences are designated 1 through 8. The factory programmed action sequences
are designated from 9 up.
The factory programming for all alarms is to trigger action sequence 9. If an alarm occurs and the action sequence
that is triggered has no instructions, the system will substitute action sequence 9.
Action sequences can be chained together to achieve sequences longer than eight instructions.
Alarm calls can be made to text based pagers with a site ID number and can optionally include the number of the
channel that triggered the alarm. In previous RFC-1 versions, the message was limited to a single digit repeated ID
digit. This mode is completely DTMF tone driven however some paging systems may not support this feature.
Alarm calls can be made to text based pagers with complete text messages including the channel that triggered the
alarm and the channel reading when the failure occurred. This feature requires the RFC-1 to have a data modem
(MA-1/2 or RAK-1) and data support from the pager service provider. The data communication follows the automatic
messaging mode specified in the TAP protocol that is supported by most paging terminals. Additional data protocols
have been added to the RFC-1 to support standard and non-standard TAP implementations.
To Next Page
Loading...
Need help?
General
