Remote Facilities Controller Model RFC-1/B • Relay Panel Model RP-8 – INSTALLATION AND OPERATION – Remote Facilities Controller firmware version 6.00 www.sinesystems.
Table of Contents Section I – Safety Information 1.1 1.2 Safety Information FCC Compliance Page 1.1 1.2 Section 2 – New Features and System Changes 2.1 Version 6.00 2.1 Section 3 – Installation 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.
4.2 Auxiliary Circuits Audio Detection Latching Relays Telemetry Pulse Stretching Battery Backup 4.3 4.3 4.4 4.4 4.5 Section 5 – Basic Operation 5.1 5.2 5.3 5.4 5.5 5.6 5.
6.4 6.5 6.6 6.7 6.
6.9 6.10 6.11 Security Codes Security Code Programming Control Security Code Mapping Incorrect Code Lockout / Communication Mode Switch Delay Site ID and Other Options Site Identification Phrase Hardware Version Inactive System Timeout Operating Commands / Notes 6.51 6.51 6.51 6.52 6.53 6.53 6.54 6.54 6.55 Section 7 – Programming Examples 7.1 7.2 7.3 7.4 7.5 7.6 7.7 7.8 7.9 7.10 7.
Section 1 — Safety Information and FCC Compliance 1.1 Safety Information Only qualified technical personnel should attempt to install the RFC-1 system. An attempt to install this device by a person who is not technically qualified could result in a hazardous condition to the installer or other personnel, and/or damage to the RFC-1 or other equipment. Ensure that safety precautions are made before installing this device.
1.2 FCC Compliance The RFC-1 complies with Part 68 of the FCC rules. On the rear panel of the RFC-1 is a label that contains, among other information, the FCC registration number and ringer equivalence number (REN) for this equipment. If requested, this information must be provided to the telephone company. The REN is used to determine the number of devices that may be connected to the telephone line. Excessive RENs on the telephone line may result in devices not ringing in response to an incoming call.
Section 2 — New Features and System Changes 2.1 Version 6.00 General Feature Updates The RFC-1 can reset all user programmable settings to their factory default values. programming code has been added to the system that performs this operation. A special advanced The system can be manually forced to both data and voice mode with the command 84. Previously it was possible to force data mode but the system can now be forced back to voice mode too. The memory dump/print command has additional options.
Telemetry System Updates Telemetry channels that are programmed as status channels (“on/off”, “normal/alarm”, etc.) can be individually programmed to invert the status reading. Typical behavior is a reading of “off” when no voltage is present and “on” when voltage is present. The readings can be swapped so that no voltage reads “on” and voltage present reads “off”. This eliminates the need for wiring an external inverter circuit. There are a couple of changes to the telemetry channel status options.
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.
Section 3 — Installation Only qualified technical personnel should attempt to install the RFC-1 system. An attempt to install this device by a person who is not technically qualified could result in a hazardous condition to the installer or other personnel, and/or damage to the RFC-1 or other equipment. Ensure that safety precautions are made before installing this device. 3.
3.2.1 Mechanical Installation The RFC-1 and RP-8 should be mounted in a standard 19-inch equipment rack. The system generates little heat. It can be mounted in nearly any convenient location. The RP-8 panels should be mounted at a location that is convenient to the control and metering sources that will be connected to it. A flat cable is supplied for interconnection between the RFC-1 and the RP-8.
3.2.3 RP-8 Channel Block Assignment If your system uses only one RP-8 you may skip this section. Each RP-8 panel in the system should be assigned to a different “block” of eight channels. The channel blocks are: 00-07, 08-15, 16-23, 24-31, 32-39, 40-47, 48-55 and 56-63. Normally, consecutive blocks of channels are used but this is not necessary. Channel block assignment is made by moving a selection jumper located at the left end of each RP-8 panel. Simply move the jumper to the desired block position.
3.2.4 RP-8 Telemetry Connections Telemetry connections to the RP-8 are made through two-conductor screw terminal connectors. The screw terminal connectors can be removed for easier installation. There are no locks or catches, grasp the connector firmly and pull it away from the panel. The connector can be plugged onto the terminal posts in several directions: horizontal or vertical and left or right facing. You may choose the position that is most convenient.
3.2.5 RP-8 Control Connections Control connections to the RP-8 are made through three-conductor screw terminal connectors. The screw terminal connectors can be removed for easier installation. There are no locks or catches, grasp the connector firmly and pull it away from the panel. In addition, the connector can be plugged onto the terminal posts in several directions: horizontal or vertical and left or right facing. You may choose the position that is most convenient. Figure 3.
3.2.7 Telephone and Telephone Line Connection The RFC-1 should be connected to a standard (POTS) telephone line with the modular (RJ11C) jack on the rear panel labeled "Line". A telephone cable is supplied with the RFC-1 for this purpose. A telephone may be connected to the jack labeled "Phone". This telephone will be used to control the RFC-1 locally (on-site) and will function normally when the RFC-1 is not online.
3.3 Telemetry Source Inputs Telemetry samples may be elevated several hundred volts above ground on some equipment. Permanent damage may occur to the RFC-1 and/or external equipment if a high voltage telemetry source is connected to the RP-8! Failure to observe this warning may also cause injury to the installer or other personnel. Telemetry inputs are located across the top of the RP-8 panel through the 8 two conductor terminal blocks marked “Telemetry”. The channels are identified as “00” through “07”.
3.3.1 Analog Readings Any telemetry channel can be a status channel on the RFC-1. Explained briefly, the RFC-1 has the capability to read telemetry over a range of 0000 to 2040. If the reading is: • • Between 0003 and 2039 the telemetry is spoken as four digits Lower than 0003 the words "status off" are spoken • Higher than 2037 the words "status on" are spoken Thus, any channel can act as either an analog input or a status channel with no specific programming changes.
In some cases it is necessary to use an externally generated voltage to indicate status. Suppose, for example, that a large AC contactor that does not have auxiliary contacts is to be metered. A small step-down transformer can be placed across the coil of the contactor to generate a low voltage AC sample. The low voltage AC can then be routed through a series diode and resistor (approximately 1 KΩ) to the telemetry input. The 10 µF capacitor on the RP-8 should provide sufficient filtering.
3.4 Control Outputs While the control relay contacts are rated for 120 volts AC, only low voltage AC or DC sources should be connected to the RP-8. The large number of exposed terminals on this panel could result in a hazardous condition to the installer or other personnel if high voltage were present. Each RP-8 relay panel has eight “On/Raise” relay contacts and eight “Off/Lower” relay contacts.
3.5.3 Radiotelephones and Wireless Extenders This class of device uses a full duplex radio circuit to extend a POTS telephone line over a radio link. Two small transceivers are used. One is connected to the telephone line and the remote device emulates the telephone line. Radiotelephones have a range of roughly 1 to 20 miles depending on terrain. Typically these systems must be licensed. Channels are usually available in the areas where radiotelephones are most often needed.
If the DC blocking capacitors are not used, however, two conditions must be satisfied: • No more than about 50 mA DC should be drawn from this port—this is an equivalent DC load resistance of about 240 ohms • No DC load, and only a high impedance AC load, should be present across this port when the RFC-1 is being operated from a dial-up line Both of these conditions will be satisfied if an ordinary telephone is connected to this port and the telephone is left on hook when not in use.
3.6 Battery Backup and Clock/Calendar All of the user options and programmable parameters of the RFC-1 are stored in non-volatile memory that remains intact if power is interrupted. The clock/calendar requires continuous power and the system will lose the time and date if power is lost. When power is restored the clock does not advance. Resetting the clock/calendar is simple but programmed events may be missed if the clock is not running. 3.6.
3.7.2 Telephone Line Protection Be sure your local telephone company has installed gas surge arrestors on your incoming telephone lines. Old installations may contain carbon protectors that tend to provide less reliable protection. Be sure the ground connection used by the telephone company is an integral part of your station ground system.
Section 4 — Accessories and Miscellaneous Circuits 4.1 Optional Accessories Several accessories are available for the RFC-1 to extend the capabilities of the basic system. Photographs and other literature are available from our web site http://www.sinesystems.com. 4.1.1 RP-8 Relay Panel Every RFC-1 installation must have at least one relay panel. Installations that require more than eight channels of telemetry and/or control can add extra relay panels.
4.1.6 RS-232 Serial Data Adapter The RS-232 Serial Data Adapter provides a means for the RFC-1 to communicate with external serial devices. This adapter can be used with a serial printer on site, or with an external modem or network translation device to access a remote computer or printer. Voice/DTMF capability is not lost when the RS-232 is installed. The RS-232 consists of a small accessory board that attaches to the RFC-1 and new chassis parts to house the expanded system. 4.1.
4.2 Auxiliary Circuits Accessories are available that give the RFC-1 extra capabilities. Some functions are simple to add with just a few extra parts. 4.2.1 Audio Detection In some cases it is desirable to monitor the presence or loss of an audio signal with the RFC-1. This signal can be used to trigger an alarm in the RFC-1. The circuit shown below is a simple audio detector. It does not provide the features of AFS-3 Audio Failsafe but it can provide a basic audio status indication.
4.2.2 Latching Relays Some devices may require a maintained relay contact for proper operation. While the RFC-1 cannot provide a maintained relay contact, it is not difficult to use the control relays of the RFC-1 to electrically latch an outboard relay. The disadvantage of this type of latched relay is that if power fails the relay may chatter or change state. In some cases this is not an issue but, if it is, a mechanical or magnetically latched relay is probably a better solution.
4.2.2.1 Rising Edge Detection Circuit Part U1 C1-C2 R1 R2 Power Description 74HC123AN retriggerable timer IC 0.1µF 50V monolithic ceramic capacitor* 5K Ohm ¼ W carbon film resistor* 1M Ohm ¼ W carbon film resistor 5VDC regulated power supply Figure 4.3; Circuit to detect and extend a rising edge pulse 4.2.2.2 Falling Edge Detection Circuit Part U1 C1-C2 R1 R2 Power Description 74HC123AN retriggerable timer IC 0.
4.2.3 Battery Backup Do not under any conditions apply a DC voltage greater than 19.9 volts (19.9 VDC peak if significant ripple is present) to the RFC-1. Prolonged exposure will cause the protection circuitry in the RFC-1 to overheat and be damaged. This maximum voltage rating precludes the use of some rechargeable batteries. The user settings in the RFC-1 are stored in non-volatile memory. No user settings are lost when the RFC-1 loses power.
Section 5 — Basic Operation 5.1 Overview The primary function of the RFC-1 is to monitor and control outboard devices. To perform these functions, a user connects to the RFC-1 with a telephone. The telephone can be directly connected or through a telephone line. The user issues two-digit commands with the telephone keypad. The RFC-1 responds with a synthesized voice. The RFC-1 is controlled with the tones generated by a typical telephone keypad. Rotary phones do not work.
5.2.3 Reading Telemetry Channels Taking a telemetry reading is as simple as selecting a channel. The RFC-1 responds with the current telemetry value as soon as the channel is selected. For example, enter 03 on the keypad to take a reading on channel 3. The RFC-1 responds “Channel 03” followed by a four-digit reading or, depending on the calibration, it may give a status reading.
5.3 Operation from a Remote Telephone Operating the RFC-1 from a remote telephone is very much like operating it from the local phone. The primary difference is that the connection is made from a remote location through a telephone line. A user dials the telephone number at the site where the RFC-1 is installed. The RFC-1 answers and requests a security code. When the correct code is given, the RFC-1 allows user access. After that, operation is the same from local or remote phones. 5.3.
5.4 Alarm System The RFC-1 can monitor up to eight channels for abnormal telemetry conditions. If an out-of-tolerance condition is detected, the system will call up to four telephone numbers to notify an operator of the condition. In basic operation, the RFC-1 calls an operator but it does not attempt to correct the situation without user intervention. 5.4.
5.4.3 Programming Alarm Limits The eight alarm channels are designated as A through H. One telemetry channel can be assigned to each alarm. It is not necessary to use all the alarms nor is it necessary to program them in order. For example, alarm A might monitor telemetry channel 07 and alarm B could monitor telemetry channel 03 while alarms C-H are left unused. Using the commands 90 through 97, the RFC-1 will prompt through setting up each alarm.
5.4.6 Enabling / Disabling the Power Failure Alarm The RFC-1 can alert an operator of an AC power failure at the remote site. In most cases, this alarm triggers when AC power returns. The RFC-1 uses the same dialing procedure as it does for telemetry alarms as described in section 5.4.1 but the message delivered is “This is RFC-1/B. Power failure.” An operator clears this alarm just like any other alarm. The command to enable or disable the power failure alarm is 82.
If there is not a generator and a UPS is not used, when AC power fails at a site, both the RFC-1 and the transmitter lose power. When power returns, the RFC-1 makes a new reference scan. If the transmitter does not power up automatically, the reference scan will show that the power off condition is normal and no alarm will trigger. Use the power failure alarm to avoid this situation. Instruct all personnel who will receive alarm calls from the RFC-1 about the various alarms and associated channel numbers.
5.6 Basic Programming The RFC-1 can be programmed to suit the individual needs of the installation and its operators. Alarm parameters, telephone numbers, security codes, etc. are all programmable. Most of the settings in this section can be changed from either the local phone or a remote telephone. For safety and security, a few options are only available from the local phone. 5.6.
5.7 Operating Commands / Programming Notes It may be helpful to keep a table of normal programming for the RFC-1. This serves not only as a reminder of the current programming but it also acts as a handy guide to remember how to change some common system settings.
Section 6 — Advanced Operation This section is for qualified technical personnel. It contains information to alter most operating characteristics of the RFC-1 system. Improper use of this information can cause unexpected or undesirable behavior. We strongly recommend having a full understanding of the basic operation of the RFC-1 and the specifics of the installation before applying this information. Information in this document is based on the original factory programming.
6.2.1 Programming Address Table In the appendix of this document there is a list of all memory addresses with descriptions of what feature is controlled at each address—the Programming Address Table. This list is the key to programming mode in the RFC-1. It translates the memory address numbers that the RFC-1 uses into a descriptive map. The sample below shows the first four memory addresses from the table, 0000 through 0003.
6.2.2 Using the Programming Mode The programming method is the same for setting up any feature using programming mode. Different address and data tables are used for each feature but every address is programmed the same way. Programming mode temporarily suspends normal system activity—telemetry channels are not selected and control relays do not activate. This frees the keypad so that keystrokes can have different functions.
6.2.3 Restore Factory Settings In programming mode there is a special extension command that will reset the RFC-1 back to the factory default settings. This command will restore all programmable items to the factory settings including security codes, alarm values, date and time functions, channel settings, telephone numbers, site ID phrase, etc. To restore the factory settings in the RFC-1: 6. 7. Enter programming mode: 80 At the prompt, enter the advanced programming security code: 4150 8.
6.3 Telemetry Channels 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. If you have not done so already, please read the documentation above that describes the Advanced Programming Mode before continuing. Each telemetry channel in the RFC-1 can deliver a status indication or an analog reading with unit word and decimal point.
6.3.3 Status Reading Status channels are programmed like the unit words above but they are treated as a special case. The first 16 words in the Word Table (words 0-0 through 0-15) are numbers. Assigning a number as a unit word would be confusing. Instead, those values behave according to the table below. Select a telemetry format or status option from one of the tables below and program the values from columns V1 and V2 in the first two channel addresses.
6.3.4 Maximum Scale and Decimal Point Setting an appropriate scale allows the RFC-1 to give a more accurate reading. When choosing the scale, find the smallest item in the table below that is larger than the highest expected reading. Be sure to allow some headroom for out of tolerance readings. A telemetry channel will report “upper limit” if the reading exceeds the top of the scale, Select the maximum scale reading and decimal point location from the table below.
6.3.6 Indirect Power The RFC-1 can calculate output power from plate voltage and plate current when a power sample is not available. This is referred to as an indirect power calculation. This feature requires careful setup to work properly. Sine Systems provides a web page that will perform the appropriate calculations and generate values to program into the RFC-1. The web site is http://www.sinesystems.com.
6.3.6.a Indirect Power—Theory of Operation This section provides further information on calculating indirect power. If the sequence above is completed and it operates successfully then it is not necessary to read this section. This information is useful for troubleshooting. An indirect power channel has a reading from 0000 to 9999. A decimal point is optional and the unit word will be either “kilowatts” or “percent power”.
6.3.7 Telemetry Leading Zero Suppression Telemetry values in the RFC-1 are four-digits long. A channel should be calibrated to take advantage of as much of the telemetry scale as possible for maximum accuracy. Sometimes a telemetry reading will have a zero as the left most zero in part of its operating scale. The RFC-1 can ignore leading zeros when it reports the telemetry value. The leading zero still exists as part of the value but it is not spoken.
6.3.9 Number of Telemetry Channels Available The RFC-1 can support up to 8 relay Panels. Each relay panel has 8 channels. Memory addresses must be available for all 64 possible channels even though most RFC-1 systems use fewer than that. Rather than leave the memory for unused channels empty and potentially wasted, that memory space can be used for more date/time triggers. (Date/time triggers are discussed later in this document.) The factory setting reserves memory for 16 channels or 2 relay panels.
6.4 Clock and Calendar The clock and calendar are used by the RFC-1 to trigger events by the date and time. Enhancements to the timing system give the RFC-1 very good long-term accuracy. The clock will attempt to synchronize with the AC main supply when the RFC-1 is powered from either a 50 Hz or 60 Hz AC supply. The time and date are lost when the system loses power. When power returns, the clock does not run until an operator resets it. A small external UPS provides an easy solution for this issue. 6.
This feature is enabled or disabled in programming mode at address 1017. The table below shows available options. V1 0 1 Automatic Daylight Saving Time Change Disabled—no automatic change Enabled—DST clock adjust (factory setting) Automatic DST time change is enabled when shipped from the factory. Follow the instructions below to disable it. 1. 2. Enter the Advanced Programming Mode: 80 Enter the Advanced Programming Security Code: 4150 3.
The clock gains time when it runs too fast. Suppose the clock is set to a known accurate time. Six days later at 6:00 pm the RFC-1 clock is checked. Instead of 6:00 pm it reads 6:01 pm. It is running too fast and has gained 1 minute. Positive numbers in the table below make the clock run slower. The drift is (1 * 60) / 6 = 10 seconds/day. Using the first example above, find -20 seconds in the table. V1=8 and V2=3.
6.5 Action Sequences Functional knowledge of the specific installation is required to make use of the information presented here. In addition, some degree of comfort working with the RFC-1 is presumed in the documentation that follows. The RFC-1 can be programmed to respond to telemetry conditions or the time and date. These automatic functions rely on action sequences—series of instructions stored in memory to perform a specific task or set of tasks. Action sequences are simple, pre-programmed tasks.
6.5.2 User-programmable Action Sequences The RFC-1 can store up to 8 action sequences having up to 8 steps each. The available instructions are listed in the text that follows along with a unique code that identifies each instruction. Select the instructions and program the corresponding codes in the appropriate area of memory for the action sequence. The programming address table in Appendix A provides a list of all memory address and their functions.
6.5.3 Control Relay Operation The RFC-1 can operate any of the control relays as a step in an action sequence. Select an instruction from the list below and program V1 and V2 in the action sequence to activate the associated control relay. Control relays are momentary activation only. There is no need to execute an on instruction followed by a corresponding off instruction.
6.5.4 Action Sequence Delays The RFC-1 pauses for about one-half second between the steps of an action sequence. This can be adjusted in an individual action sequence by placing a delay instruction at the appropriate point(s) in the action sequence. Delay instructions can be used in succession to create a longer delay. Select the appropriate delay instruction(s) from the table below and program corresponding V1 in the action sequence as needed.
6.5.5 Alarm Calls The RFC-1 can place telephone calls as a step in an action sequence. The message delivered depends on the condition that triggers the action sequence. The message typically consists of the site identification phrase followed by an indication of the condition that triggered the call such as a telemetry alarm or power failure. The message repeats for a pre-determined length of time.
6.5.6 Logging Telemetry Readings The RFC-1 can send a set of telemetry readings to a printer or computer as a step in an action sequence. The logging device can be connected directly to the RFC-1 or at a remote location. The set of readings will start with channel 00 and end at the programmed auto-scan stop channel. The default setting stops at channel 07. Readings are printed with a header that includes the site identification phrase, the date and time and the action sequence.
6.5.7 Conditional Execution There are no instructions in the RFC-1 action sequences for performing loops or making complex decisions. These kinds of functions are simply beyond the capabilities of the available memory and processing power. However, there are some instructions that can be used to perform simple conditional behavior.
An example is the easiest way to illustrate how this works. Suppose the telemetry input on channel 01 is a transmitter output power sample. An alarm is programmed to monitor channel 01 so that if the transmitter power goes too high, the RFC-1 will adjust it down into limits. The RFC-1 control relays are momentary activation, about one-half second. Depending on how the transmitter control works, there is no guarantee that a single, brief relay closure will bring the transmitter power back into limits.
In this example, the RFC-1 has been programmed to make the power changes automatically. At the appropriate times of day the RFC-1 will execute an action sequence activating relays as needed to change the transmitter power. When the sequence terminates a new reference reading is made for the alarms. If for some reason the transmitter does not change power, the RFC-1 will record the current reading as the reference and it will be considered normal even if it is out-of-tolerance.
6.5.8 Enabling / Disabling Telemetry Alarms Telemetry alarms can be selectively enabled and disabled by an action sequence. This is particularly useful for transmitters that operate at multiple power levels. The appropriate alarm can be enabled using the same action sequence that changes the transmitter power. Be aware that any alarms that are disabled using these commands will remain disabled until they are enabled using the corresponding enable command, or until the system restarts.
6.5.10 Testing an Action Sequence Action sequences are typically activated by telemetry alarms or by date/time triggers. However, it is possible to trigger an action sequence manually for testing purposes or for ease of system use. Suppose an action sequence is programmed to adjust an antenna switch and change transmitter power. The action sequence can be used to perform the procedure manually.
6.6 Telemetry Alarms 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. There are 8 telemetry alarms in the RFC-1. Each alarm can be programmed to monitor any physical channel from channel 00 to 63.
6.6.3 Trigger Rules The trigger rule determines the conditions under which the alarm activates—which alarm limits are critical. The default trigger rule is adequate in most cases as long as the alarm limits are set properly. Program the value from the column V1 into the third memory location for the selected alarm. It is a common mistake to program alarm limits incorrectly when leading zero suppression is enabled.
6.6.5 Upper and Lower Limits The upper and lower limits specify the range of acceptable telemetry values for a channel. Limits are programmed using 4 digits. If the telemetry channel reading has a decimal point, ignore the decimal but keep the digits following the decimal. Digits are critical. Decimal points and unit words are not critical. If the reading is not 4 digits long, add zeros to the left until the reading has 4 digits. For example, to program an upper limit of 105.
6.6.7 Blocking Alarms by Time It is possible to disable a telemetry alarm during certain hours of the day by programming an alarm block. Alarm blocks are used in cases where an alarm is not valid during part of the day. Tower light monitoring is a good example. Tower lights are typically not on during daylight hours so an alarm monitoring tower light power can be blocked to prevent a false alarm. Alarm blocks use the same memory area that date/time triggers use—memory addresses 0256-0639.
Each hour setting uses 2 memory addresses. Program the first digit of the hour at the location listed as “V1” and program the second digit at the memory location listed as “V2”. Do this with both the start and stop hours. The example below shows programming for an alarm block that is active every day of the week in every month from 8:00pm (20 hours) to 6:00am (06 hours).
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.
Looking at the Programming address table, the date/time triggers appear to be numbered backward. As the address increases—the normal direction for programming—the number of the date/time trigger decreases. This is not a mistake. The numbering is consistent as the date/time triggers transition into shared memory. This selection from the Programming Address Table highlights the transition—notice the Alternate Use column. See section 6.7.4 for more information on allocating memory for date/time triggers.
6.7.5 Special Triggering Options The RFC-1 has settings that simplify programming for events that repeat on easily defined intervals. date/time trigger will trigger an event using the specified interval(s). A single Program V1 and V2 from the table below for date value 1 and 2 to trigger an event on the specified days of the week.
The previous example can be altered to print every day at 6:00 am. The programming is shown below. Addr Description Section 0632 0633 0634 0635 0636 0637 0638 0639 Date/time trigger 1: action sequence Date/time trigger 1: month Date/time trigger 1: day - value 1 Date/time trigger 1: day - value 2 Date/time trigger 1: hour - value 1 Date/time trigger 1: hour - value 2 Date/time trigger 1: minute - value 1 Date/time trigger 1: minute - value 2 6.6.4 6.6.4 6.6.4 6.6.4 6.6.4 6.6.4 6.6.4 6.6.
Suppose we need to turn a transmitter on every day at 5:30 am in April and that action sequence 3 is programmed to perform this task. We will use date/time trigger 1 but any unused date/time trigger will work.
6.7.7 Telemetry Auto-scan Data Interval The telemetry auto-scan data feature provides logging data at fixed intervals. It is a timed event that operates very much like a date/time trigger event but it is a very specialized case. First, it is not programmed in the same area of memory as the other date/time triggers. Second, it has a fixed set of timing options. And third, it has a fixed function and that is to send data readings to an external device. The programming options for this feature are easy.
6.8 Communication Incorrect communication settings can cause the RFC-1 to place repeated, unwanted calls to unsuspecting people or places. It is solely your responsibility to verify that the RFC-1 is programmed to contact only authorized personnel. 6.8.1 Programming Telephone Numbers The six telephone numbers stored in the RFC-1 are designated as Telephone Number A-F. Each telephone number contains up to twelve digits.
6.8.2 Extending Telephone Numbers When more than twelve digits are needed for a single call, two (or more) telephone numbers can be chained together to form one longer telephone number. Program the final digit of a telephone number with the value 15 as an indicator to continue dialing the next telephone number. Program the first digit of the next telephone number with a 10 (blank) to keep the RFC-1 from dialing the extended number as part of the calling rotation.
6.8.4 Setting the Call Mode Each telephone number has an associated dialing mode. This setting determines how the number is dialed: in voice mode, data mode or pager mode. There are two pager modes: pager mode and legacy pager mode. Pager mode supports many features of modern paging systems. Legacy pager mode sends a single digit repeatedly to the paging terminal for rudimentary site identification.
6.8.4.3 Calling Pagers in Voice Mode The RFC-1 can call a text pager in data mode or in voice/DTMF mode. Calling a pager in voice mode does not require extra hardware. The pager message will consist of a programmable site ID number and, optionally, the number of the telemetry channel that triggered the alarm. The RFC-1 must be set to dial using DTMF tones rather than pulse dialing to call a pager in this mode. This setting is discussed in section 6.8.5.
In the example below, the telephone number for the pager is 555-1212 and the site ID that will be sent to the pager is 615-228-3500. The optional ❊ command is being used to add the channel number to the display and the # key is being sent to terminate the page.
In this mode, the RFC-1 calls the paging terminal via modem. After the modems establish a connection, the RFC-1 sends a specially coded message to the paging terminal. The message includes the pager ID number to identify the message recipient and the message to be delivered to the pager. As in voice mode paging, data mode paging requires two telephone numbers. The first number is the paging terminal number—the telephone number to the modem bank of the service provider.
6.8.5 Tone / Pulse Dialing The original RFC-1 hardware with the mechanical sounding voice only pulse dials. Later models that use the humanmale sounding speech-processor perform tone dialing using the speech-processor. The tones are designed to compensate for component tolerances. More recent models have a dedicated hardware for generating DTMF tones. Use of the dedicated tone generator is recommended if hardware supports this feature.
6.8.8 Ring Sensitivity and Hang-up Detection Previous versions of the RFC-1 used a different, non-linear scale for the ring sensitivity adjustment. The scale below is only appropriate for systems running version 6.0 or higher. Using this data table to adjust earlier versions can cause unexpected and undesirable behavior. Attention! In previous versions of the RFC-1 the ring sensitivity setting shared a memory location with the dedicated control port feature.
6.8.9 Communication Mode This adjustment sets the mode for incoming calls only. It has no effect on outgoing telephone calls. The communication mode determines what type of connections the RFC-1 receives for monitoring and control. It also determines whether the connection is part-time or full-time. A dial-up connection is typically part-time; the connection is broken at the end of the call. A data connection can be part-time or full-time over a dedicated line.
6.8.10 Data Communication Settings References in this section to paging terminals are strictly for full-text paging in data mode. This adjustment has no effect on voice mode paging. The data communication setting is determined by the device(s) that the RFC-1 will connect to in data mode. This adjustment sets the data format for incoming and outgoing connections. The RFC-1 has two data communication settings, one for standard data connections and another for paging terminals.
6.8.12 Saving and Restoring System Settings If the RFC-1 has a data accessory attached, the system settings can be copied to the connected device. If the device is a printer then a formatted list of the settings can be printed. If the device is a modem or terminal, software can collect the data and store it to a file. Depending on the data format selected, the file can be printed or saved as a backup and used to restore the system settings should it become necessary.
Save/Restore Data Dump The save/restore data dump copies the memory contents to the data port in a format that should be captured by a computer. The dump is a continuous feed of data from every address in order from 0000 to 1023. Each data byte is followed by a “#” character. There are spaces in the data stream but there are no addresses, no comments and no carriage returns or line feeds. A short sample is shown below.
6.8.14 Backing-up System Settings The following instructions assume that you know how to connect and operate the RFC-1 in data mode with the installed data accessory. The examples use HyperTerminal in Windows. Other software and other computer platforms will work. Use appropriate terminal emulation software that is for the operating system. Using HyperTerminal to capture the RFC-1/B settings To backup the system settings, connect the terminal to the data port.
6.8.15 Restoring System Settings The following instructions assume that you know how to connect and operate the RFC-1 in data mode with the installed data accessory. The examples use HyperTerminal in Windows. Other software and other computer platforms will work. Use appropriate terminal emulation software that is for the operating system. Using HyperTerminal to restore the RFC-1/B settings To restoring the system settings, connect the terminal to the data port.
6.9 Security Codes There are four security codes in the RFC-1. They are: the main security code, the control security code, the basic programming security code and the advanced security code. The easiest way to read and reprogram the security codes is using the prompted commands 72, 73, 74 and 75. They are described in section 5 of this document. For security reasons, the prompted commands only work from the local phone.
6.9.3 Incorrect Code Lockout / Communication Mode Switch Delay The RFC-1 disconnects when an incorrect security code is given. This is a security measure to stop an intruder from making repeated attempts at guessing a code. The RFC-1 will ignore incoming calls for a short time period after a code fails. This feature can be used to thwart attempts to guess the RFC-1 security code. The duration of time that calls are ignored is adjustable.
6.10 Site ID and Other Options The section provides information on features that do not fall into any of the topics that have already been covered. 6.10.1 Site Identification Phrase The site identification phrase is what the RFC-1 uses to identify itself. This is the phrase that is spoken, or printed, when the RFC-1 comes online or when it calls out with an alarm notification. The factory setting is "This is RFC-1/B”.
6.10.2 Hardware Version Incorrect hardware version settings can cause undesirable system behavior. If incorrect data is programmed, the RFC-1 seizes the telephone line making it impossible to call the system. Do not change this setting unless you are certain that it is required for your installation. The hardware revision is set at the factory and does not normally require adjustment. If the firmware is upgraded in the field then it may be necessary to adjust this setting. RFC-1 hardware revisions 1.
6.11 Operating Commands / Programming Notes It may be helpful to keep a table of normal programming for the RFC-1. This serves not only as a reminder of the current programming but it also acts as a handy guide to remember how to change some common system settings.
Section 7 — Programming Examples This section contains programming examples. It does not contain information about using the Advanced Programming Mode of the RFC-1. You should be familiar with the section of this documentation that details Advanced Programming before using the examples in this section. You must be familiar with setup and operation of the RFC-1 for the information in this section to be useful.
7.2 Site Identification Phrase In the first example we will change the Site Identification Phrase—the phrase that the RFC-1 says when it answers the phone or when it reports an alarm. The factory programming is “This is RFC-1/B”. We will change it to say, “Hello this is Curly”. Any words or letters from the Word Table can be used. 16. Enter the advanced programming mode: 80 17. Enter the advanced programming security code: 4150 18.
7.3 Action Sequence In this example we will program action sequence 2 to activate the channel 00 “on” relay, pause 15 seconds, and then activate the channel “01” on relay. A sequence like this might be used to power up transmitter filaments with a short delay then turn on the plate voltage. The commands used by action sequences are documented in Section 6 of this manual. The commands in the example come from tables in Section 6.5. 1. Enter the advanced programming mode: 80 2.
7.4 Date/Time Trigger In this example we will program Date/Time Trigger 1 to activate the action sequence that we programmed in the previous segment. The action sequence is one that could be used to turn on a transmitter: activate the channel 00 on relay, pause 15 seconds, and then activate the channel 01 on relay. We will program the time trigger to activate the action sequence every day at 6:00am. 1. Enter the advanced programming mode: 80 2. Enter the advanced programming security code: 4150 3. 4.
7.5 Alarm Limits—Analog Channel In this example we will program Alarm A to monitor telemetry channel 03 with an upper limit of 105.0 and a lower limit of 090.0 and place a series of alarm calls if either limit is exceeded. The normal reading on this channel is approximately 100.0. In this example, we will use the fixed, factory programmed action sequence 9. It is programmed to call all programmed telephone numbers in sequence.
7.6 Alarm Limits—Status Channel In this example we will program Alarm B to monitor telemetry channel 05 for the loss of voltage on a status channel. The alarm will have an upper limit of “9999” and a lower limit of “0500”. This might be the case if an audio failsafe is monitoring presence of an audio signal. The output of the failsafe is connected so that 5 volts DC is applied to the telemetry input when audio is present and 0 volts DC is applied when audio fails.
7.7 Voice Mode Telephone Number In this example we will program Telephone Number A with a voice number to call when an alarm occurs. We will use the fictitious telephone number 615-555-1212. Since this telephone number is only 10 digits long and the RFC-1 can dial up to 12 digits, we will pad the end of the number with the value 10 to represent an unused digit. Since this is a voice number and it might be busy, we will set the number of call attempts to 2. 1. Enter the advanced programming mode: 80 2.
7.8 Text Pager—Voice Mode In this example we will program Telephone Number B with a voice pager number to call when an alarm occurs. We will use the fictitious telephone number 555-1212 for the pager number. Text pager calls require a site ID number to be programmed at Telephone Number E. We will use 228-3500 for the site ID number. Unused digits will be filled with the value 10. And because this telephone number dials a paging system, which is not likely to be busy, we will set the call attempts to 1.
The pager number is programmed. Jump to a new address to program the site ID number. This is the telephone number of the site where the RFC-1 is installed. Any number that helps you identify the specific site should work but many paging systems require a telephone number. 32. Jump to a new address in advanced programming mode: 80 33. Enter the starting address from the address table for Telephone Number E: 0696 34. Enter the first digit of the telephone number: 10 35.
7.9 Logging Readings—Local Printer In this example we will program Action Sequence 3 to print a set of readings on a local printer (connected to a PA-1/2 or an RAK-1) and we will program Date/Time Trigger 2 to activate the action sequence hourly at 10 minutes past the hour to automatically log the transmitter readings. 1. Enter the advanced programming mode: 80 2. Enter the advanced programming security code: 4150 3. 4.
7.10 Tower Light Alarm In this example we will program an alarm to monitor a telemetry channel that has a sample from a tower lighting system. We will use channel 06 as our telemetry input. It is programmed to read “100.0 percent” when all lights are operating properly—this is a direct reading from the telemetry sample programmed with the unit word “percent”. Alarm C will be programmed to monitor channel 06 for 10 percent over and 10 percent under. Adjust the alarm limits to suit your system. 1.
7.11 Tower Light Alarm Block—Daylight Hours In this example we will program an alarm block that disables the telemetry alarm programmed in the previous example. In this case we want to block the tower light alarm so that it is not active during daylight hours. The block is not necessary if you are using an ACM-2 AC Current Monitor and have a daylight sensor connected to the appropriate inputs. The daylight sensor is the preferred method but the alarm block is effective if programmed properly.
Section 8 — Troubleshooting and Factory Service 8.1 Problem: Common Problems and Possible Solutions The RFC-1 does not power up. Solutions: With the ribbon cable connecting the RFC-1 and the RP-8 check for a short circuit across the 12 VAC terminals on the RP-8. Check the wall-plug power supply for 12 VAC. Problem: The RFC-1 powers up and responds but telemetry cannot be calibrated. Solutions: The wrong calibration pot is being adjusted.
Problem: There is hum on the line when the RFC-1 answers a call but there is no hum when operated locally. Solutions: The telephone line may be shorted or the telephone line is too long and is receiving interference. Check the line. If it is okay, try shielded cable and an off-the-shelf inline filter to eliminate the offending signal. Depending on the frequency of the interference ferrite beads, filter capacitors or chokes may be necessary.
8.2 Factory Service Policy Terms are subject to change without prior notice. 8.2.1 Warranty Sine Systems, Inc. guarantees our products to be free from manufacturing defect for a period of one year from the original date of purchase from Sine Systems, Inc. This warranty covers the parts and labor necessary to repair the product to factory specifications.
Section 9 — Specifications 9.1 RFC-I Remote Facilities Controller 9.1.1 Connections Relay panel: 16-conductor 0.1" pitch pin/plug Telephone: RJ-11C modular connector Local phone: RJ-11C modular connector 9.1.2 Indicators Power: green LED 9.1.3 Power Voltage: 12 Volts AC supplied by wall-plug transformer Current: 250mA nominal, ~750mA maximum 9.1.4 Dimensions Size: 19" (w) x 6.5" (d) x 1.75" (h) Weight: 1.5 Ibs. 9.1.5 Environmental This device does not generate a significant amount of heat.
Appendix A –– Programming Address Table - Programming Section Default Current Address Description 0000 0001 0002 0003 0004 0005 0006 0007 0008 0009 0010 0011 0012 0013 0014 0015 0016 0017 0018 0019 0020 0021 0022 0023 0024 0025 0026 0027 0028 0029 0030 0031 0032 0033 0034 0035 0036 0037 0038 0039 0040 0041 0042 0043 0044 0045 0046 0047 RFC-1 Channel 00: telemetry units or status format - value 1 Channel 00: telemetry units or status format - value 2 Channel 00: full scale and decimal point Channel 00: l
Appendix A –– Programming Address Table - Programming Section Default Current Address Description 0048 0049 0050 0051 0052 0053 0054 0055 0056 0057 0058 0059 0060 0061 0062 0063 0064 0065 0066 0067 0068 0069 0070 0071 0072 0073 0074 0075 0076 0077 0078 0079 0080 0081 0082 0083 0084 0085 0086 0087 0088 0089 0090 0091 0092 0093 0094 0095 RFC-1 Channel 12: telemetry units or status format - value 1 Channel 12: telemetry units or status format - value 2 Channel 12: full scale and decimal point Channel 12: l
Appendix A –– Programming Address Table - Programming Section Default Current Address Description 0096 0097 0098 0099 0100 0101 0102 0103 0104 0105 0106 0107 0108 0109 0110 0111 0112 0113 0114 0115 0116 0117 0118 0119 0120 0121 0122 0123 0124 0125 0126 0127 0128 0129 0130 0131 0132 0133 0134 0135 0136 0137 0138 0139 0140 0141 0142 0143 RFC-1 Channel 24: telemetry units or status format - value 1 Channel 24: telemetry units or status format - value 2 Channel 24: full scale and decimal point Channel 24: l
Appendix A –– Programming Address Table - Programming Section Default Current Address Description 0144 0145 0146 0147 0148 0149 0150 0151 0152 0153 0154 0155 0156 0157 0158 0159 0160 0161 0162 0163 0164 0165 0166 0167 0168 0169 0170 0171 0172 0173 0174 0175 0176 0177 0178 0179 0180 0181 0182 0183 0184 0185 0186 0187 0188 0189 0190 0191 RFC-1 Channel 36: telemetry units or status format - value 1 Channel 36: telemetry units or status format - value 2 Channel 36: full scale and decimal point Channel 36: l
Appendix A –– Programming Address Table - Programming Section Default Current Address Description 0192 0193 0194 0195 0196 0197 0198 0199 0200 0201 0202 0203 0204 0205 0206 0207 0208 0209 0210 0211 0212 0213 0214 0215 0216 0217 0218 0219 0220 0221 0222 0223 0224 0225 0226 0227 0228 0229 0230 0231 0232 0233 0234 0235 0236 0237 0238 0239 RFC-1 Channel 48: telemetry units or status format - value 1 Channel 48: telemetry units or status format - value 2 Channel 48: full scale and decimal point Channel 48: l
Appendix A –– Programming Address Table - Programming Section Default Current Address Description Alternate Use / Notes 0240 0241 0242 0243 0244 0245 0246 0247 0248 0249 0250 0251 0252 0253 0254 0255 Channel 60: telemetry units or status format - value 1 Channel 60: telemetry units or status format - value 2 Channel 60: full scale and decimal point Channel 60: linear/log/indirect and auto relay Channel 61: telemetry units or status format - value 1 Channel 61: telemetry units or status format - value 2
Appendix A –– Programming Address Table Address Description 0288 0289 0290 0291 0292 0293 0294 0295 0296 0297 0298 0299 0300 0301 0302 0303 0304 0305 0306 0307 0308 0309 0310 0311 0312 0313 0314 0315 0316 0317 0318 0319 0320 0321 0322 0323 0324 0325 0326 0327 0328 0329 0330 0331 0332 0333 0334 0335 RFC-1 Date/time 44: action sequence Date/time 44: month Date/time 44: date - value 1 Date/time 44: date - value 2 Date/time 44: hour - value 1 Date/time 44: hour - value 2 Date/time 44: minute - value 1 Date/t
Appendix A –– Programming Address Table Address Description 0336 0337 0338 0339 0340 0341 0342 0343 0344 0345 0346 0347 0348 0349 0350 0351 0352 0353 0354 0355 0356 0357 0358 0359 0360 0361 0362 0363 0364 0365 0366 0367 0368 0369 0370 0371 0372 0373 0374 0375 0376 0377 0378 0379 0380 0381 0382 0383 RFC-1 Date/time 38: action sequence Date/time 38: month Date/time 38: date - value 1 Date/time 38: date - value 2 Date/time 38: hour - value 1 Date/time 38: hour - value 2 Date/time 38: minute - value 1 Date/t
Appendix A –– Programming Address Table Address Description 0384 0385 0386 0387 0388 0389 0390 0391 0392 0393 0394 0395 0396 0397 0398 0399 0400 0401 0402 0403 0404 0405 0406 0407 0408 0409 0410 0411 0412 0413 0414 0415 0416 0417 0418 0419 0420 0421 0422 0423 0424 0425 0426 0427 0428 0429 0430 0431 RFC-1 Date/time 32: action sequence Date/time 32: month Date/time 32: date - value 1 Date/time 32: date - value 2 Date/time 32: hour - value 1 Date/time 32: hour - value 2 Date/time 32: minute - value 1 Date/t
Appendix A –– Programming Address Table Address Description 0432 0433 0434 0435 0436 0437 0438 0439 0440 0441 0442 0443 0444 0445 0446 0447 0448 0449 0450 0451 0452 0453 0454 0455 0456 0457 0458 0459 0460 0461 0462 0463 0464 0465 0466 0467 0468 0469 0470 0471 0472 0473 0474 0475 0476 0477 0478 0479 RFC-1 Date/time 26: action sequence Date/time 26: month Date/time 26: date - value 1 Date/time 26: date - value 2 Date/time 26: hour - value 1 Date/time 26: hour - value 2 Date/time 26: minute - value 1 Date/t
Appendix A –– Programming Address Table Address Description 0480 0481 0482 0483 0484 0485 0486 0487 0488 0489 0490 0491 0492 0493 0494 0495 0496 0497 0498 0499 0500 0501 0502 0503 0504 0505 0506 0507 0508 0509 0510 0511 0512 0513 0514 0515 0516 0517 0518 0519 0520 0521 0522 0523 0524 0525 0526 0527 RFC-1 Date/time 20: action sequence Date/time 20: month Date/time 20: date - value 1 Date/time 20: date - value 2 Date/time 20: hour - value 1 Date/time 20: hour - value 2 Date/time 20: minute - value 1 Date/t
Appendix A –– Programming Address Table Address Description 0528 0529 0530 0531 0532 0533 0534 0535 0536 0537 0538 0539 0540 0541 0542 0543 0544 0545 0546 0547 0548 0549 0550 0551 0552 0553 0554 0555 0556 0557 0558 0559 0560 0561 0562 0563 0564 0565 0566 0567 0568 0569 0570 0571 0572 0573 0574 0575 RFC-1 Date/time 14: action sequence Date/time 14: month Date/time 14: date - value 1 Date/time 14: date - value 2 Date/time 14: hour - value 1 Date/time 14: hour - value 2 Date/time 14: minute - value 1 Date/t
Appendix A –– Programming Address Table Address Description 0576 0577 0578 0579 0580 0581 0582 0583 0584 0585 0586 0587 0588 0589 0590 0591 0592 0593 0594 0595 0596 0597 0598 0599 0600 0601 0602 0603 0604 0605 0606 0607 0608 0609 0610 0611 0612 0613 0614 0615 0616 0617 0618 0619 0620 0621 0622 0623 RFC-1 Date/time 8: action sequence Date/time 8: month Date/time 8: date - value 1 Date/time 8: date - value 2 Date/time 8: hour - value 1 Date/time 8: hour - value 2 Date/time 8: minute - value 1 Date/time 8:
Appendix A –– Programming Address Table Address Description - Programming Section Default Current Alternate Use / Notes 0624 0625 0626 0627 0628 0629 0630 0631 0632 0633 0634 0635 0636 0637 0638 0639 Date/time 2: action sequence Date/time 2: month Date/time 2: date - value 1 Date/time 2: date - value 2 Date/time 2: hour - value 1 Date/time 2: hour - value 2 Date/time 2: minute - value 1 Date/time 2: minute - value 2 Date/time 1: action sequence Date/time 1: month Date/time 1: date - value 1 Date/time 1:
Appendix A –– Programming Address Table Address Description 0672 0673 0674 0675 0676 0677 0678 0679 0680 0681 0682 0683 0684 0685 0686 0687 0688 0689 0690 0691 0692 0693 0694 0695 0696 0697 0698 0699 0700 0701 0702 0703 0704 0705 0706 0707 0708 0709 0710 0711 0712 0713 0714 0715 0716 0717 0718 0719 0720 RFC-1 Telephone number C: value 5 Telephone number C: value 6 Telephone number C: value 7 Telephone number C: value 8 Telephone number C: value 9 Telephone number C: value 10 Telephone number C: value 11
Appendix A –– Programming Address Table Address Description - Programming Section Default Current Alternate Use / Notes 0721 0722 0723 Telephone number F: value 12 Telephone number F: voice/data/pager ID Telephone number F: call attempts 6.8.1 6.8.4 6.8.
Appendix A –– Programming Address Table Address Description 0769 0770 0771 0772 0773 0774 0775 0776 0777 0778 0779 0780 0781 0782 0783 0784 0785 0786 0787 0788 0789 0790 0791 0792 0793 0794 0795 0796 0797 0798 0799 0800 0801 0802 0803 0804 0805 0806 0807 0808 0809 0810 0811 0812 0813 0814 0815 0816 0817 RFC-1 Action Sequence 3: step 7 - value 2 Action Sequence 3: step 8 - value 1 Action Sequence 3: step 8 - value 2 Action Sequence 4: step 1 - value 1 Action Sequence 4: step 1 - value 2 Action Sequence 4:
Appendix A –– Programming Address Table Address Description - Programming Section Default Current Alternate Use / Notes 0818 0819 0820 0821 0822 0823 0824 0825 0826 0827 0828 0829 0830 0831 0832 0833 0834 0835 0836 0837 0838 0839 0840 0841 0842 0843 0844 0845 0846 0847 0848 0849 0850 0851 Action Sequence 6: step 8 - value 1 Action Sequence 6: step 8 - value 2 Action Sequence 7: step 1 - value 1 Action Sequence 7: step 1 - value 2 Action Sequence 7: step 2 - value 1 Action Sequence 7: step 2 - value 2 Ac
Appendix A –– Programming Address Table Address Description 0864 0865 0866 0867 0868 0869 0870 0871 0872 0873 0874 0875 0876 0877 0878 0879 0880 0881 0882 0883 0884 0885 0886 0887 0888 0889 0890 0891 0892 0893 0894 0895 0896 0897 0898 0899 0900 0901 0902 0903 0904 0905 0906 0907 0908 0909 0910 0911 RFC-1 Alarm B: channel number - value 1 Alarm B: channel number - value 2 Alarm B: trigger rule Alarm B: action sequence Alarm B: upper limit - value 1 Alarm B: upper limit - value 2 Alarm B: upper limit - val
Appendix A –– Programming Address Table Address Description - Programming Section Default Current Alternate Use / Notes 0912 0913 0914 0915 0916 0917 0918 0919 0920 0921 0922 0923 0924 0925 0926 0927 0928 0929 0930 0931 0932 0933 0934 0935 0936 0937 0938 0939 0940 0941 0942 0943 0944 0945 0946 0947 Alarm F: channel number - value 1 Alarm F: channel number - value 2 Alarm F: trigger rule Alarm F: action sequence Alarm F: upper limit - value 1 Alarm F: upper limit - value 2 Alarm F: upper limit - value 3
Appendix A –– Programming Address Table - Programming Section Default Current Address Description 0960 0961 0962 0963 0964 0965 0966 0967 0968 0969 0970 0971 0972 0973 0974 0975 0976 0977 0978 0979 0980 0981 0982 0983 Control security code B - value 1 Control security code B - value 2 Control security code B - value 3 Control security code B - value 4 Control security code C - value 1 Control security code C - value 2 Control security code C - value 3 Control security code C - value 4 Basic programming s
Appendix A –– Programming Address Table Address Description 0996 0997 0998 0999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 RFC-1 - Programming Section Default Current Hardware version 6.10.2 Telemetry settling time 6.3.8 Telemetry leading zero suppression 6.3.7 Telephone dialing mode (tone/pulse) 6.8.5 Inactive system timeout 6.10.3 Answer ring number 5.6.2 Communication mode (data/voice) 6.8.
Appendix B –– Word Table Values V1 and V2 are used to identify the words when programming.
