SFCD: Federal Commander Digital System - Federal Signal

SFCD: Federal Commander Digital System - Federal Signal SFCD: Federal Commander Digital System - Federal Signal

federalsignal.indust.com
from federalsignal.indust.com More from this publisher
05.05.2013 Views

Federal Commander Digital System This checkbox field controls whether or not AC power fail will be auto reported from this RTU. If enabled this RTU will auto report power fail when it occurs. If disabled power fail will not be auto reported however they will be sent when this RTU is polled. Time Encryption The Time Encryption option, when enabled adds extra security against malicious operation. This is accomplished by comparing the base station's time and date encoded into the activation message with the rtu's (siren) time. If they differ by a predetermined amount, the siren will not sound and a sync fail error will occur. It is recommended that this option not be used unless malicious operation by recording activation signals is a problem. There is a potential the sirens may fail to operate when called upon if the time clocks drift out if sync. Trunking Mode (ENABLED/ DISABLED) This checkbox field controls trunking mode. Trunking mode is used only for selected trunking transceivers and should normally be disabled. Repeater General Information A repeater is a normal RTU that is used as a communication link between the CCU and a target RTU. The best possible situation is that the CCU will be able to communicate directly with every RTU in the network. In this situation, no repeaters are needed to reach any RTU. In real life there are usually RTUs that the CCU cannot communicate with directly because the distance is too great, or there is some object in between the CCU and RTU. In this situation, up to four repeaters can be used to reach any RTU. If the CCU does not need to use repeaters to be able to communicate with an RTU, both RTU Repeater Set #1 and RTU Repeater Set #2 will contain blanks for all RTU numbers. If Repeater Set #1 is blank and Set #2 contains repeaters, the CCU will first attempt to communicate using the direct path and retry using Set #2 only if the direct path fails. If the CCU does need to use repeaters to be able to communicate with an RTU, RTU Repeater Set #1 will contain one or more RTU numbers, and RTU Repeater Set #2 can optionally contain a different set of RTU numbers. If any repeaters are specified for RTU Repeater Set #1, they will always be used in any communication attempt with this RTU. If any repeaters are specified for RTU Repeater Set #2, they will only be used if the CCU is unable to communicate with this RTU using RTU Repeater Set #1. The CCU will then wait the number of seconds indicated in the Retry Delay field of the System Setup window for a reply from the RTU. If no reply is received within the Retry Delay time, and if the # Tries field on the System Setup window is greater than 1, the CCU will try again to communicate with the RTU, using the same repeaters as before, if any. The CCU will attempt to communicate with this RTU with the same repeaters (if any) as many times as the # Tries field indicates. The CCU will again wait the indicated number of seconds. If no reply is received again, the CCU will generate a Comm Fail alarm message for the Alarm Log, with the CCUs date and time of when the last failure occurred. Then if the CCU used any repeaters for the first attempt(s), and if there are any repeaters specified in RTU Repeater Set #2, the CCU will again attempt to communicate with the RTU using the repeaters from RTU Repeater Set #2. During an All Poll the 134 RTU

Federal Commander Digital System retry for Repeater Set #2 will occur at the end of the queue, after an attempt has been made to communicate with all sites using Repeater Set #1. The CCU will again wait the indicated number of seconds for a reply. If no reply is received again, and if the # Tries field on the Status of Base Unit window is greater than 1, the CCU will try again to communicate with the RTU, using the same repeaters from RTU Repeater Set #2. The CCU will attempt to communicate with this RTU with the repeaters from RTU Repeater Set #2 as many times as the # Tries fields indicates. Note: To first try without repeaters (direct path) put the destination site address as the first repeater in Set #1. The CCU will attempt to communicate using Set #2 only if the direct path fails. To retry without repeaters (direct path) for Repeater Set #2, put the destination site address as the first repeater in Set #2. If Repeater Set #2 is blank, no retries, direct or otherwise, will occur. If all attempts to communicate with the RTU fail, the CCU will generate a Comm Fail alarm message for the Alarm Log, with the CCUs date and time of when the last failure occurred. RTU Repeater Set #1 The format of these four data entry fields is from 0 to 3 digits each. If any repeaters are used, the first repeater must be entered in the repeater box labeled 1-, with the second repeater in the box labeled 2-, etc. If any repeaters are used, the RTU numbers must be entered as 3 digits each, with leading zeros required. If a repeater is to be removed from use, replace the RTU number with 3 blanks. To change any one of the repeaters, highlight the current repeater, then enter a new 3 digit RTU number or 3 blanks. These data entry fields control which RTUs are used as a first set of repeaters to reach this RTU. Each of the four fields can contain one RTU number. RTU numbers must be entered in exactly the same order as they will be physically used; entry 1 would contain the RTU number of the first RTU in the link, while entry 2 would contain the RTU number of the next RTU in the link, etc. If it is desired to first try the direct path and retry using repeaters only if the direct path fails, put the destination site address as the first repeater in Repeater Set #1. RTU Repeater Set #2 These data entry fields control which RTUs are used as a second set of repeaters to reach this RTU if all communication attempts using Repeater Set #1 fail. The format of these data entry fields is the same as for RTU Repeater Set #1. If Repeater Set #2 is blank, no retries will occur if Repeater Set #1 fails; however, if it is desired to retry a direct path if Repeater Set #1 fails, put the destination site address as the first repeater in Repeater Site #2. Voice Call-out On The checkboxes contained in this group enable or disable telephone Call-out for each of the respective monitoring points indicated. Siren Configuration The Siren Configuration window is used to set up certain programmable parameters at the selected RTU site. When this selection is made, the following window will be displayed. 135 RTU

<strong>Federal</strong> <strong>Commander</strong> <strong>Digital</strong> <strong>System</strong><br />

retry for Repeater Set #2 will occur at the end of the queue, after an attempt has been made to<br />

communicate with all sites using Repeater Set #1. The CCU will again wait the indicated number<br />

of seconds for a reply. If no reply is received again, and if the # Tries field on the Status of Base<br />

Unit window is greater than 1, the CCU will try again to communicate with the RTU, using the<br />

same repeaters from RTU Repeater Set #2. The CCU will attempt to communicate with this RTU<br />

with the repeaters from RTU Repeater Set #2 as many times as the # Tries fields indicates.<br />

Note: To first try without repeaters (direct path) put the destination site address as the first<br />

repeater in Set #1. The CCU will attempt to communicate using Set #2 only if the direct path<br />

fails. To retry without repeaters (direct path) for Repeater Set #2, put the destination site address<br />

as the first repeater in Set #2. If Repeater Set #2 is blank, no retries, direct or otherwise, will<br />

occur.<br />

If all attempts to communicate with the RTU fail, the CCU will generate a Comm Fail alarm<br />

message for the Alarm Log, with the CCUs date and time of when the last failure occurred.<br />

RTU Repeater Set #1<br />

The format of these four data entry fields is from 0 to 3 digits each. If any repeaters are used, the<br />

first repeater must be entered in the repeater box labeled 1-, with the second repeater in the box<br />

labeled 2-, etc. If any repeaters are used, the RTU numbers must be entered as 3 digits each,<br />

with leading zeros required. If a repeater is to be removed from use, replace the RTU number<br />

with 3 blanks. To change any one of the repeaters, highlight the current repeater, then enter a<br />

new 3 digit RTU number or 3 blanks.<br />

These data entry fields control which RTUs are used as a first set of repeaters to reach this RTU.<br />

Each of the four fields can contain one RTU number. RTU numbers must be entered in exactly<br />

the same order as they will be physically used; entry 1 would contain the RTU number of the first<br />

RTU in the link, while entry 2 would contain the RTU number of the next RTU in the link, etc.<br />

If it is desired to first try the direct path and retry using repeaters only if the direct path fails, put<br />

the destination site address as the first repeater in Repeater Set #1.<br />

RTU Repeater Set #2<br />

These data entry fields control which RTUs are used as a second set of repeaters to reach this<br />

RTU if all communication attempts using Repeater Set #1 fail.<br />

The format of these data entry fields is the same as for RTU Repeater Set #1.<br />

If Repeater Set #2 is blank, no retries will occur if Repeater Set #1 fails; however, if it is desired to<br />

retry a direct path if Repeater Set #1 fails, put the destination site address as the first repeater in<br />

Repeater Site #2.<br />

Voice Call-out On<br />

The checkboxes contained in this group enable or disable telephone Call-out for each of the<br />

respective monitoring points indicated.<br />

Siren Configuration<br />

The Siren Configuration window is used to set up certain programmable parameters at the<br />

selected RTU site. When this selection is made, the following window will be displayed.<br />

135<br />

RTU

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!