FG8800 Manual Rev A
FG8800 Manual Rev A
! " !#
#"$ " %&
%& "$ "#
"
" '() "
*
! #
! " # # $ %&' ( ) *
+ , # &- . * . * /( ' - . * . *
" &0 - ( 11&) %&2 3 &4 ( 1- /# 5 ( 11&) %&2 2 # 4
Publication REV A
ALLESTEC FG8800 INDUSTRIAL
GAS / FIRE CONTROL PANEL
AUTOMATIC SUPPRESSION SYSTEM
RELEASE UPDATE VERSION 7/1/06
OPERATIONS MANUAL PART NUMBER FG8800-5140A
The control panel as well as the In addition to the FM approval, each node
nodes carry the FM approval. carries the following ATEX approval.
Department __________________________________________
Name ______________________________________________
Date _______________________________________________
2
TABLE OF CONTENTS
1. INTRODUCTION …………………………………………………..………...…………………… 8
1.1 UNDERSTAND AND READ THIS MANUAL COMPLETELY..................................................... 8
1.2 CONTROL PANEL DESCRIPTION ............................................................................................ 8
1.3 SYSTEM ARCHITICTURE ........................................................................................................ 8
1.4 REQUIRED PROGRAMMING TOOLS....................................................................................... 8
1.5 INFORMATION ACCESSIBILITY ............................................................................................... 8
3
5.14 THE ADVANCED SECTION - REFER TO SECTION 25.1 ...................................................... 37
5.15 OTHER NODE COMMON FUNCTIONS .................................................................................. 37
4
13. DIRECT CONNECTION RELEASE Input node initializing .............................. 51
13.1 SELECTING AN INPUT NODE TO TRIP AN SOM OR RELAY NODE .................................... 51
13.2 SELECT INPUT NODE CHANNEL TO TRIP OUTPUT NODES ............................................. 51
13.3 RESULTANT............................................................................................................................. 52
13.4 VOTING CHANNELS WITHIN THE INPUT NODES................................................................ 52
13.5 SAVE THE CONFIGURATION ................................................................................................. 53
13.6 TESTING THE CONFIGURATION TO ALARM ON A DIRECT CONNECTION RELEASE ... 53
13.7 SYSTEM FIRE ALARM MENU ................................................................................................. 53
13.8 FIRE ALARM MENU ................................................................................................................. 53
13.9 DETAILS MENU........................................................................................................................ 54
13.10 VOTING SEQUENCING ......................................................................................................... 54
13.11 SYSTEM FAULT ALARM MENU............................................................................................ 55
13.12 FAULT ALARM MENU............................................................................................................ 55
5
17.9 SELECT OTHER NODE CHANNELS ...................................................................................... 68
17.10 RESET ALLOWED.................................................................................................................. 68
17.11 VOTING SEQUENCING ......................................................................................................... 68
17.12 SAVING THE CONFIGURATION ........................................................................................... 68
17.13 TESTING THE CYCLE MIST RELEASE CONFIGURATION FOR AN ALARM .................... 68
17.14 RESET THE ALARM............................................................................................................... 69
6
25.7 RESETTING ALL NODE ADDRESSES WHILE CONNECTED TO THE BUS ........................ 84
25.8 RESETTING SELECTIVE NODE ADDRESSES WHILE CONNECTED TO THE BUS........... 84
25.9 RESETTING A NODE ADDRESS THAT IS REMOVED FROM THE BUS.............................. 84
25.10 REMOVING A NODE.............................................................................................................. 85
7
1. INTRODUCTION
The Allestec ONGUARD FG8800 gas/fire panel provides continuous surveillance of system compon-
ents by interrogating intelligent devices connected to the panel through an addressable configuration.
The powerful configuration manager emulates cause and effect logic processes enabling simple
programming techniques of all system components. The system is designed to allow personnel familiar
with conventional control panels to fully develop and utilize the features of the FG8800 without extensive
training or special schooling. The system uses an “open concept” of simple I/O building scripts for each
action of mapping a node. After several small scripts have been built, they can be mapped to other
scripts or overlaid on open scripts allowing a multifunction logical connection.
8
DRAWING 1
9
DRAWING 2
10
2. SYSTEM HARDWARE INSTALLATION
This control panel is designed to indicate an alarm condition when the initiating devices connected to it
detect change in conditions. These conditions may or may not represent a life-threatening condition.
Also, evacuation of a building or area unnecessarily may subject individuals to an unnecessary hazard.
Therefore, it is most important that the building owner, manager or representative promulgate, distribute,
and/or post instructions describing steps to be taken when the gas/fire alarm control panel signals an
alarm condition. These instructions should be developed in cooperation and conformance with
representatives of the local authority having jurisdiction.
Along with the use of this instruction manual, the appropriate following standards and the manufacture’s
instructions for initiating and notification devices should be utilized to install and maintain a functioning
fire alarm signaling system:
For other standards that may apply contact the local authority having jurisdiction.
WIRING SHALL BE PER PLAN WITH RESPECT TO CONDUCTOR SIZE, TYPE AND QUANTITY.
CONDUCTORS SHAL BE PERMANENTLY MARKED FOR FUTURE IDENTIFICATION. PERMANENT
WIRE MARKERS SHALL BE USED TO IDENTIFY THE TERMINATIONS OF ALL CONDUCTORS
WITHIN THE FACP, PULL BOXES AND OTHER PANELS (REF. NEC 760.10).
11
IMPORTANT: After stripping the outer insulator of a wire cable, make sure that the twisted pair of wires
from the cable remain twisted as much as possible to the terminal strip. This procedure retards reflected
waves in the cable assembly.
CAUTION: DO NOT USE DIFFERENT BUS WIRE SIZES IN THE INSTALLATION OF THE SYSTEM.
DOING SO WILL CAUSE IMPEDENANCE MISMATCH AND REFLECTIVE WAVES THEREBY RE-
DUCING THE ABILITY OF THE PANEL TO DISCRIMINATE BETWEEN DIGITAL SIGNALS. ALL
BUS CONDUCTORS MUST BE OF THE SAME SIZE. DO NOT SPLICE THE BUS ANYWHERE
CAUTION: DO NOT DISCONNECT THE POWER TO THE CONTROL PANEL WHILE THE
ONGUARD PROGRAM IS RUNNING OR ANY FILE IS OPENED. DOING SO COULLD RESULT IN
THE CORRUPT OF MEMORY FLASH DATA. REFER TO SECTION 26.1 FOR MORE INFORMA-
TION.
Refer to drawing 4 to connect power to the panel and drawing 13 and 14 to power the field nodes. The
panel operates from 18 to 30 VDC and requires a redundant 24V power source to comply with NFPA.
To correctly size the power supply for the system, add the current of each node as well as the current
supplied to all initiating and appliance devices, then add the current of the control panel into the figure.
After adding all the devices, take 25% of the total current demand and add it back to the result for head-
room during appliance turn-on surges and other current requirements. If the ambient temperature of the
power supply is higher than 72 deg. F (22 deg. C), refer to the manufactures specifications to correctly
de-rate the power supply for a rise in ambient temperature. Allow enough headroom for power conduc-
tors to provide current under these adverse circumstances:
1. Long power wire runs have voltage drops thereby delivering less voltage to the intended nodes.
2. Higher temperatures lessen the efficiency of carrying current through power wires.
3. Improper wiring and termination (loose set screws) of conductors decrease the efficiency of the
power conductors, especially where vibration exists.
4. Aging conductors over time loose their ability to carry specified current.
5. Splicing wires is not recommended since it increases stray capacitance and inductance thereby im-
peding the performance of the data transfer.
6. Terminations with dissimilar connections will attribute to an electrolysis reaction thereby galvanizing
the connection and increasing contact resistance.
Do not apply power to the panel until there has been a through inspection of all field and local panel
wiring. The panel may be powered without connecting the bus to browse through the features.
12
2.5 UTILIZING MORE THAN ONE POWER SUPPLY (PARALLEL CONNECTION)
On systems that utilize long enough lengths of cable to require a power supply at the middle or end of
the system, the following criteria must be met:
A fault alarm notifies the administrator that broken or shorted wires exists so that a repair can be
completed as soon as possible, and the integrity of the alarm system will be restored in a timely manner.
The alarm integrity is assured by continuously communicating with every node in the system. The panel
will report any bus failure so that the problem can be repaired to continue the integrity of the alarm
system.
13
Refer to drawing 7 to identify the spacing of the mounting holes for the input and 4-20ma node and
drawing 10 for the SOM and relay nodes. Each node accepts four 6-32 screws with a node mounting
depth of .25” (6.35MM).
The time delay between the activation of an initiating device and the automatic activation of a local fire
safety function shall not exceed 20 seconds. Effective January 1, 2002, the time delay between the acti-
vation of an initiating device and the automatic activation of a local fire safety function shall not exceed
10 seconds.
CAUTION: DO NOT CHANGE GAGE SIZE OF BUS WIRING WITHIN THE SAME RUN.
DO NOT UTILIZE SPLICING DEVICES ANYWHERE ON THE BUS. BUS CUTS ARE
ALLOWED ONLY AT THE TB1 TERMINAL.
14
IMPORTANT: Systems requiring nodes demanding more current than the 4-wire bus can carry will be
required to utilize heavier power conductors separate from the signal bus. In this case, the bus will
contain two conductors with a shield wrapped in a PVC sheathe while the power conductor will contain
two conductors large enough to sustain the required current to satisfy the nodes as well as their
appliances.
15
DRAWING 3
16
DRAWING 4
17
DRAWING 5
18
DRAWING 6
19
DRAWING 7
20
DRAWING 8
21
DRAWING 9
22
DRAWING 10
23
DRAWING 11
24
DRAWING 12
25
DRAWING 13
26
DRAWING 14
27
3. NODE SELECTION
28
3.6 STATUS LED’s
Nodes contain LED’s to provide indication on what their status is. The LED’s also indicate when inputs are closed on the
input node. It is imperative that the sections relating to disabling channels are read to fully understand their intent.
LED STATUS INPUT NODE 4-20mA GAS NODE SOM RELAY NODE
29
4. HARDWARE INTERFACE AND PORTS
4.1 UTILIZING THE TOUCH SCREEN DISPLAY
Alarm acknowledging, silencing, resetting and other commands are implemented through the touch
screen display. The display is designed to be used intuitively instead of analytically thereby reducing
decision-making time by the administrator. Lightly touch a button or command line on the touch screen
to invoke the command. If a finger is too large, a non-metallic object like a closed pen can be used as a
stylus to touch the screen. Do not use an instrument that is sharply pointed as it will scratch the surface
and do not drag any object across the surface. Use a household glass cleaner to clean the surface of
the screen when the system is not on line.
4.3 PRINTER
Prior to bringing the system on line, print reports to verify the system is in compliance with the manner it
was programmed. The Onguard software supports different model Epson printers that are able to print
through the USB drive. For more details refer to section 23.
CAUTION: LIKE ANY OTHER COMPUTER SYSTEM, DO NOT REMOVE USB DRIVE WHILE IT IS
BEING READ FROM OR WRITTEN TO, DOING SO WILL CORRUPT THE SYSTEM FILES! VERIFY
THAT THE DATA TRANSFER LED HAS STOPPED BLINKING BEFORE REMOVING THE BUS
DRIVE.
30
DRAWING 15
31
DRAWING 16
32
5. SYSTEM STARTUP
33
5.3 ENABLING PASSWORDS
The control panel comes with the administrator password number 2222 installed. A keyboard must be
connected to change passwords. Enter the F10 key and enter a default password that will be utilized
within the program. Now enter and confirm the new password. A “backdoor” password 1793 overrides
any existing passwords in case the user password is lost or it can remain as the dominant password.
Other passwords than the two indicated here enables a more frequent beckon of the keypad.
34
5.8 UNDERSTANDING FIELD NODE ID ADDRESSES
After completing the wiring of a system the second step is to acquire node address so the control panel
can communicate to unique addresses. If the nodes are installed, the administrator must physically go to
each node and set their ID switch as they are entered into the system. It is advantageous to establish
programming on a bench next to the control panel prior to installation. The node ID switch located on
each node enables the search program to identify the next node ID to increment. Refer to Drawing 17 to
properly select the node ID switch. The first node identified will be assigned the address 0, then 1,2 etc.
Select a node that is best suited for the starting number (0) and turn ON its acquire address switch,
SW1-1 ON, SW1-2 OFF, as identified in drawing 17. After the node is identified, return SW1-1 to the
OFF position and proceed to discover the next node and repeat. Nodes can have their ID number
change if desired as indicated in section 25.6. Once a node is identified, it cannot be removed from
the bus unless it is disabled in the menu. Refer to section 25 for more information. All nodes must
have an ID address of 255 prior to starting section 5.8. New nodes are shipped with the ID address of
255. To change a node address to 255 refer to section 25.
FIGURE 5.2 Enter a password. FIGURE 5.3 Ready to search nodes. NOTE:
Only buttons pertaining to the startup proce-
dure will appear until the first node is discov-
ered and located in the above menu.
35
CAUTION: NO ALARMS CAN OCCUR UNTIL THE INDIVIDUAL CHANNELS ARE ENABLED IN THE
SETTINGS MENU AND A CONFIGURATION FILE IS CREATED, #14 SYSTEM CONFIGURATION,
OR F8 IS UTILIZED.
NOTE: If two or more ID switches are ON, the next searched node WILL NOT BE FOUND and the mes-
sage “NO MORE NODES FOUND” will appear.
9. The node in figure 5.4 appears with its 4 channels “open”. Click on the COLLAPSE button to close
the node, if desired.
10. Repeat this search procedure for all other nodes, remembering to turn ON the ID switch for only
one node at a time to be addressed, then turn the switch back OFF.
11. Select the SAVE and CLOSE button to exit the node menu.
12. After identifying all nodes connected to the system, data can be entered into each node to identify
its characteristics.
13. Figure 5.5 shows 4 nodes that have been selected for illustration purposes.
1. Optical detectors connect to the input node and any time delays or voting will be addressed.
2. Manual pulls connect to the input node and the option to add or override time delays are addressed.
NOTE: Alarm verification or timers are not permitted on manual alarm activation devices.
3. Four wire smoke detectors connect to the input node.
4. An audible remote silence switch connects to the input node and is addressed.
5. Door or other contacts connect to the input node. The option for the contact closure to proceed to an
action alarm or remain as a message on the screen is addressed.
6. For systems employing a reserve extinguish tank to trip on a post fire or first tank fail condition, con-
nect the pressure switch to the input node.
36
FIGURE 5.4 Input node open indicating its FIGURE 5.5 All four node channels collapsed.
four undefined channels.
37
DRAWING 17
38
6. CONFIGURATION ARCHITECTURE
6.1 INTRODUCTION
Prior to creating configurations, it is imperative the administrator reads this section as well as the entire
manual. The administrator must understand the structure of files and folders that reside in memory to
alleviate any misunderstanding of process and techniques of operating the system. It is important that
the administrator can navigate through Windows menu structures, folders and files effectively without
impeding the system.
NOTE: Configurations that are created and saved are not mapped together. They each reside independ-
ently in the MANAGE CONFIGURATIONS menu; however, they may SHARE a common node channel
as just described above.
39
6.5 THE CONFIGURATION FOLDER
The configuration folder contains all configurations that the administrator creates under utility menu #14,
SYSTEM CONFIGURATION. When a configuration is created for the very first time, another file called
mainconfigfile.txt is also created simultaneously and located into the configuration folder. The maincon-
fig.txt file contains the names of the configurations that are loaded. When a configuration is unloaded, its
name is removed from the mainconfig.txt file then selectively located in the same folder. Configuration
files are automatically copied into this .txt file and as more configurations are created, they are also in-
cluded, increasing the file size. The unloaded .txt file can be copied to a USB bus drive and brought to a
computer with notepad and be observed. On system initialization, only LOADED .txt files are loaded into
memory ready for alarms. The purpose of viewing this information is so the administrator can have an
understanding how files are stored. To view these files while the external monitor is connected, click the
mouse on the START button, go to Programs, then select Explorer. The folders currently visible are lo-
cated in the flash memory. Double click on the Disk C and there are more files and folders. Click on the
configuration folder to view files created in the configuration section #13-18. If the system is new, no files
are in the folder. Under normal circumstances the administrator does not have to access this folder but it
is being pointed out for information purposes. Exit out of the configuration folder back to the \Disk C di-
rectory.
1. Entering the SETTINGS in any node and not ENABLING the check-off box for a valid channel.
2. UTILITY MENU #11, NODE MANAGEMENT (F5) MENU - Whenever this selection is entered into
the polling of the nodes suspends to allow modification.
3. UTILITY MENU #13, MANAGE CONFIGURATIONS: When this selection is selected the program
suspends the polling of the nodes to allow modification of the configurations and EDITING
capabilities.
4. UTILITY MENU #13, MANAGE CONFIGURATIONS: When a loaded configuration is UNLOADED it
is DISABLED and will not function.
5. UTILITY MENU #12, SYSTEM CONFIGURATIONS or selecting F8.
6. The ONGUARD program is not loaded.
7. The system is not powered up.
40
7. BACKUP SYSTEM FILES
7.1 IMPORTANT
It is imperative that the administrator has knowledge in copying files and navigating through
Windows Explorer to perform the following tasks properly.
Do not power down the system unless proper protocol has been established or the LOSS OF
DATA will result. Refer to section 26.1 to correctly power down the system.
Use the external monitor to backup this file. While the ONGUARD screen is displayed, with the mouse
RIGHT CLICK on the ONGUARD taskbar located at the bottom at the screen. Now left click on the
“close window sign”. The ONGUARD application will close. Now click on the START button, go to PRO-
GRAMS, click on windows explorer. Insert a USB Bus drive in the connector. Wait approximately 10
seconds and the “HARD DISK” icon will appear. DOUBLE CLICK ON the Disk C folder. Copy the CON-
FIGURATION folder to the BUS drive. Wait 5 seconds after the BUS drive LED stops blinking then re-
move it from the panel. Go back to DISK C and double click on the ONGUARD word to bring the system
back up. After the screen is visible with the time and date go to the far upper right side of the monitor
screen and click on the X to close Windows Explorer.
THIRD - BACKUP TO THE SAME USB BUS DRIVE THE CONFIGURATION FOLDER LOCATED IN
DISK C.
41
8. LOADING NODE DATA TO PREPARE CONFIGURATIONS
NOTE: Nodes must be configured with text and control data prior to mapping to other
nodes to identify their personalities.
CAUTION: NODES MUST BE ENABLED OR THEY WILL NOT RESPOND TO AN ALARM. THE RE-
LAY NODE IS ALWAYS ENABLED.
Each node contains fields that allow data to be entered to identify the unique characteristics such as
location and other pertinent data. Figure 5.5 shows the four nodes we searched and their names ap-
pear. These names can be edited but the ID is fixed.
The HORN ICON is the only icon that affects the operation of the configuration on the F5 Node menu.
Refer to section 19 for more details. Solenoids are captured in the F8 configuration menu and do not
relate to the solenoid node icon.
NOTE: To simplify the following examples, the Input, Gas, Relay and SOM are the only nodes on the
bus for this demonstration and will appear in the configuration windows.
After a configuration is completed and assigned a file name, the same node channel(s) can be utilized to
trip other output devices under a different file name. After the nodes have been filled out with their perti-
nent information, they can now be mapped to activate other nodes through the configuration menus.
There are five different configurations to select from. Select #12, SYSTEM CONFIGURATION, in the
UTILITY MENU then choose the configuration.
42
9. INPUT NODE PREPARATION
[] Enter a name, location or other identification characteristic of each input in the ALARM LOCATION
box as indicated in figure 9. Applications where the input node has unused inputs do not require any
data in this field and can remain undefined.
CAUTION: BECAUSE OF THE FLEXIBILITY OF THE SYSTEM, IN THE NODE NAME FIELD, ANY
NAME CAN BE APPLIED TO ACCOMMODATE THE FUNCTION.
[] Figure 13.6 indicates how the ALARM LOCATION field reflects the data that entered in the Add/Edit
LOCATION. This ALARM LOCATION field appears to the right of the DEVICE NAME during an alarm.
Enter pertinent data in reference to the alarm location or device as necessary. There are several exam-
ples for illustration purposes in figure 9. The ALARM LOCATION, such as the example turbine optical,
can also be utilized as the device type as indicated in figure 9.
43
9.2 ICON SELECTION
[] Referring back to figure 9 to the far left, are icons in boxes that represent the device name. Select an
icon that best represents the alarm style. When an alarm occurs, the name to the right of the icon in
figure 9.1 or 9.2 will appear in the DEVICE NAME column as indicated in figure 13.7.
[] Proceed to click on an icon for each channel as well as the master node icon (top box).
[] The APPLY TO REST button simply fills the same information in the remaining lower boxes.
FIGURE 9.1 Icon Upper Menu FIGURE 9.2 Icon Lower Menu
FIGURE 9.3 EDIT box for global node name. FIGURE 9.4 EDIT box for channel 1.
44
9.4 SETTINGS SELECTON
[] With the input node still highlighted select the SET-
TINGS button.
[] Now check off a box to ENABLE the channel(s) that
will be utilized in a configuration.
CAUTION: A CHANNEL THAT IS NOT ENABLED
WILL NOT ALARM.
[] The disable can be used to temporarily turn off a
channel for a service routine.
[] Disable a channel if it is unused OR A FAULT WILL
OCCUR AFTER A CONFIGURATION IS MADE.
[] After node SETTING has been completed, it is
ready to be expanded to show all channels and in-
serted the configuration window later.
FIGURE 9.5 SETTINGS menu
CAUTION: IF THERE ARE INPUT NODES VOTING, THE DE-BOUNCE TIME MUST BE EXPIRIED
ON ANY VOTED NODES PRIOR FOR AN ALARM ACTION TO TAKE PLACE.
CAUTION: INCREMENTING THE DE-BOUNCE TIME ADDS TIME TO THE ALARM RESPONSE.
The de-bounce is based on a formula: de-bounce time/62.5ms = 5 timer periods required for the signal
to remain steady for a valid alarm. The default setting is 320 milliseconds. This time can be only set at
intervals of 62.5ms.
Another use for the de-bounce is to add time for UV only detectors to shunt out erroneous alarms from
lighting or other UV emissions. Another use serves as a deterrent for false alarms by allowing the ad-
ministrator to intelligently select a time delay appropriate for the task. The minimum de-bounce time is
64 milliseconds, the maximum is 16.32 seconds and applies to all four channels of the node.
[] After inserting the information in the settings menu, click on the APPLY button to proceed.
[] Click on the SAVE and CLOSE button to return to the main menu to proceed to continue with other
nodes.
45
10. 4-20mA NODE PREPARATION
46
10.5 CALIBRATION
[] Referring to the field wiring diagram of drawing 9, a 4-20mA constant current source is required to
connect to TB2 of the channel to calibrate.
[] As indicated in figure 10, channel #1 of node #1 was selected in the example and the name that was
inserted for demonstration purposes, METER VALVE appears for this menu. This entire menu is only for
channel one. The message NOT CALIBRATED appears until a successful calibration has been com-
pleted.
[] The tall blue bar to the far left in the graph on figure 10.4 and 10.3 represents the REAL TIME current
being measured by the control panel and is also displayed in the REAL TIME window. This current is not
affected by the calibration.
[] The green bar (shown at 5%) represents the low set point, yellow (15%) is for the HIGH and red (25%)
is for the HIGH HIGH.
FIGURE 10.3 SET ZERO menu before SET FIGURE 10.4 SET SPAN menu with 20.01 mA
0% button is pushed with 4mA applied to input. applied to same input.
[] Select the CALIBRATE button (figure 10.2) after the set point data has been entered.
[] Apply 4mA of current to this channel by reading the REAL TIME figures then click on the SET 0% but-
ton as indicated in figure 10.3.
[] Now apply 20mA to this channel as indicated in figured 10.4 and click on the SET 50% button for the
span.
[] NOTE: If the current applied to the gas node is not within the applicable range, the message “THE
50% SETTING MUST BETWEEN 8 AND 25 MILLIAMPS appears.
[] Reduce the input current back to at least below the LOW threshold then select the CAL. DONE button
to save the data. Now select the OK button.
[] After inserting the information, click on the APPLY button to proceed.
[] Click on the Cal. DONE button to save the data.
[] After channel one has been calibrated, use the same procedure to continue and calibrate the other
three channels, if utilized.
10.6 RESET
The RESET button returns the calibration settings back to the DEFAULT level. The default level is Low =
30, High = 40, HIGH HIGH = 50. Use the RESET if a new gas sensor has been installed and then re-
quires to be calibrated or if the calibration is restarted. Resetting the calibration requires that any active
sensor on line to be recalibrated.
47
10.7 ALTERNATE CALIBRATION METHOD
Manufactures of gas sensors instruct different methods for obtaining local or remote calibration. In some
cases calibration gas is utilized to connect to a gas sensor and then the 4-20mA node can then be cali-
brated. This method is called remote calibration and requires a administrator applying the gas at the
sensor while someone else is setting the zero and span at the control panel. In a correctly installed 4-
20mA system the current will not change due to field wiring. If the resistance of the wire connecting a 4-
20mA sensor is so high that the sensor cannot deliver the voltage to drive the current through the loop,
then the sensor can only be considered defective or incorrectly installed.
The use of 2.5% calibration gas is recommended for calibration. In this instance when the channel is
properly calibrated the 2.5% gas flow will indicate 50% (blue bar) or half of the scale. The calibration
method utilized here is based on the fact that the 2.5% gas concentration represents 50% of the 4-20mA
scale, or 12mA sourced into the 4-20mA node.
48
11. SUPERVISE OUTPUT (SOM) NODE PREPARATION
11.5 DEBOUNCE
FIGURE 11.1 SETTINGS
The de-bounce time here is utilized exclusively for
the output relays of this node and influences only the
fault detection. Refer to section 9.6 for more details. 11.8 PRINT NODE INFORMATION
Item #1 in the UTILITY MENU, SAVE NODE
11.6 RESETING NODE LED’s REPORT, can be selected to summarize the
[] Click on the RESET NODE LED’s to selectively information related to this node.
reset the SOM blinking LED’s after an alarm or fault
has occurred. For resetting LED’s on all the nodes
simultaneously, select menu option #10 on the UTIL-
ITY MENU.
[] Click on the APPLY button when finished.
49
12. RELAY NODE PREPARATION
50
13. DIRECT CONNECTION RELEASE Input node initializing
CAUTION: ENTERING INTO ANY CONFIGURATION DISABLES THE SYSTEM FROM RESPOND-
ING TO ALARMS. THE FAULT RELAY WILL TRIP UNTIL THE CONFIGURATION IS EXITED.
FIGURE 13.1 Input and output node trees are expanded open.
51
FIGURE 13.2
NOTE: About figure 13.2 – The SELECT ALARM TYPE box appears to enforce the decision by the ad-
ministrator that the node channel chosen is indeed the correct one. The fire and gas alarm check boxes
have no logic control on the system. The reset function is described in later sections does have control
to how the system handles the input channel.
[] Now open the SOM tree on the right menu by clicking on the + sign.
Double click on the node channel(s) that will be activated by the SELECTED OUTPUT channel.
[] Figure 13.3 illustrates that relay node channel 3 was selected for this example. SOM channels 1 and 2
were also selected.
13.3 RESULTANT
[] Based on the example, when input node 0-1 is activated all three channels in the SELECTED OUT-
PUT menu will immediately activate. Refer to figure 13.6 for the alarm action.
CAUTION: THE PROCESS OF VOTING BETWEEN ALARM CHANNELS WILL SLOW THE ALARM
RESPONSE TIME DOWN.
52
13.5 SAVE THE CONFIGURATION
[] After completing the re-
quired configuration, click on
the SAVE and CLOSE but-
ton to bring up the configura-
tion menu. Notice the rec-
tangle box is empty. As soon
as a configuration is created,
it will be inserted into this
box as well as future con-
figurations.
[] Type a file name that can
later be mapped to this con-
figuration. Notice in figure
13.6 this configuration name
appears during an alarm.
FIGURE 13.5 Fire alarm button FIGURE 13.6 Fire alarm menu
13.8 FIRE ALARM MENU
[] The SILENCE MENU allows audible appliances to be silenced. Reoccurring alarms on the same chan-
nel will activate the audible devices again. Refer to section 19.
[] The DETAILS brings up the menu in figure 13.8. It indicates and records when the highlighted alarm in
the menu has occurred, been reset or silenced for this #1 event. Select the OK button to go back to the
FIRE ALARM menu then select the SYSTEM MENU BUTTON.
[] Any subsequent fire alarm configurations will be located in this menu on the next line item.
53
[] Select the VIEW INPUTS button as indicated in figure 13.7 to view the node details as well as any
other input alarms associated with this configuration. Selecting the VIEW INPUTS allows individual view-
ing of each input node contained in the configuration.
54
13.11 SYSTEM FAULT ALARM MENU
The input alarm circuit on the node ID 0, channel 1
is opened to demonstrate a fault. Select the FAULT
ALARM button in figure 13.10 to bring up the FAULT
ALARM in figure 13.11. Figure 13.11 shows the
FAULT ALARM menu.
[] To silence the panel audible alarm, select the si-
lence button. If the fault alarm remains unattended,
the audible alarm will resound within 30 minutes.
[] The DETAILS button brings up the fault menu. It
indicates and records when the fault occurred and
has been silenced or reset.
55
14. DIRECT CONNECTION W/DELAY RELEASE Input node initializing
14.5 RESULTANT
Once any initiating device
from the SELECTED INPUT
window enters into alarm,
the Pre-Discharge time in
the SECONDS window will
commence and when t =
zero, the selected devices in
the SELECTED OUTPUT
window will initiate at the
same time and remain ON
for the duration of the Sole-
noid On Time. Follow the
example menus in figures
13.1 through 13.6 to config-
ure this menu. FIGURE 14.1. Loading the configuration with data.
56
[] Select the DELAY button to view the
counter as indicated in figure 14.4.
NOTE: If the time delay is short and the
menu is entered late, the time may have al-
ready expired.
[] During alarm time countdown, the FIRE
STATUS indicator will read ACTIVE as long
as this channel is in alarm, however the
alarm will continue in progress.
57
15. DIRECT CONNECTION RELEASE 4-20mA node initializing
58
[] Now select output appliances to trip from the gas inputs. In this example the SOM ID node #2, channel
1 and the relay node ID #3 channels 1 & 3 were selected.
[] Upon completion of mapping the node channels, click on the SAVE and CLOSE button to bring up the
CONFIGURATION screen. In this example the configuration was named “TURBINE ROOM - GAS”.
[] At this point the configuration was loaded in the CONFIGURATION folder and can be viewed by going
to the UTILITY MENU and selecting #13 MANAGE CONFIGURATIONS. The configuration is ready for
use.
15.4 RESULTANT
When a LOW alarm on
channel1 or HIGH alarm on
channel 3 occurs in the SE-
LECTED INPUT screen, all
three devices will activate in
the SELECTED OUTPUT
screen. Notice in figure 15
that on the gas alarm SE-
LECTED INPUT both chan-
nels identify the THRESH-
OLD level.
FIGURE 15.5 Select gas alarm button. FIGURE 15.6 Gas alarm menu.
59
15.6 VIEW THE ALARM
After selecting the GAS LEVEL button the graph in figure 15.8 appears. It is formatted as the original
menu where the SET POINTS are entered. The menu is color on the monitor so to identify the colors for
this manual the REAL TIME bar is the left side, then LO THRESHOLD and HIHI. Notice the REALTIME
DATA is 9% and the LOW THRESHOLD is at the setting of 5%. The REAL TIME DATA is the actual
current represented in % of the scale.
NOTE: It may take a few seconds after selecting the GAS CHART button before the bar graph can con-
struct the data and appear.
FIGURE 15.8 Gas chart alarm screen FIGURE 15.9 Details screen
60
16. DUAL MODE RELEASE Input node initializing
A. CAUSE
The SOM is activated, the MAIN solenoid timing starts, but the fire is manually extinguished prior to the
MAIN cycle time expiring.
B. EFFECT
The display will start counting down from its pre-selected time until the time expires. The display will
continue to count down unless the alarm is reset (providing the proper exception is checked off, figure
16) or the configuration is committed to the release of the first tank.
C. CAUSE
The SOM is activated, the MAIN solenoid timing starts, the fire remains until the countdown expires and
the MAIN solenoid trips thereby extinguishing the fire. The pressure switch changes state within 7 sec-
onds.
D. EFFECT
The MAIN agent release is sufficient enough to extinguish the fire and the RESERVE solenoid is
never activated.
E. CAUSE
The SOM is activated, the MAIN circuit timing starts and counts down to zero, the pressure switch
changes state within 7 seconds. The fire is of sufficient magnitude to continue after the MAIN solenoid
trips.
F. EFFECT
The display commences its second timing sequence on the RESERVE solenoid and upon the expiration
of the timing, the RESERVE solenoid trips.
G. CAUSE
The SOM is activated, the MAIN circuit timing starts, the pressure switch does not change state within 7
seconds.
H. EFFECT
The RESERVE solenoid will automatically turn on.
61
Figure 16 displays the dual
release mode configuration
menu prior to mapping the
nodes or making exceptions.
Select the CANCEL button
to exit if this menu is not the
correct.
16.3
SELECT DEVICE INPUTS
[] The first step is to expand
the input node by clicking on
the + symbol and then dou-
ble click on the specific
channels required to trip the
release.
[] For the alarm device and
pressure switch check the
fire alarm box in the SE-
LECT ALARM TYPE menu
(figure 13.2).
[] Figure 16.1 indicates one FIGURE 16. Dual release menu - preparing to configure.
optical detector on channel 1
as well as a pressure switch
(required) on channel 3 were
selected for the two inputs.
NOTE: The two time delays are independent of each other and both commence countdown simultane-
ously.
62
16.7 SELECT 2nd SOLENOID
[] Highlight the second solenoid channel then click on the SELECT SECOND SOLENOID button. Notice
that the solenoid is displayed below the SELECT SECOND SOLENOID button.
63
[] The STATUS column indicates the real time activity
of this channel and the “A” indicates the alarm is ac-
tive. The device in alarm is no longer active after the
RESET ALARM button is selected, then the letter “R”
will appear.
[] As other alarms appear, they will be located in time
occurrence order. Use the scroll arrows to the right of
the alarm window if to many alarms fill the screen and
the lower rows are out of view.
[] When the DETAILS button is selected, the menu in
figure 9.3 appears. Remember back in section 16.5,
20 seconds was entered in the PRE-DISCHARGE
DELAY window and 45 seconds in the RESERVE RE-
LEASE DELAY.
[] The fire status ACTIVE sign (figure 16.5) turns to FIGURE 16.3 Fire alarm menu
INACTIVE if the alarm device contacts open. The tim-
ers will continue to count based on the exceptions lo-
cated in the check boxes and the real-time device in
alarm.
[] Select the RETURN TO ALARM MENU to go back
to figure 16.5.
64
FIGURE 16.5 Dual time count down FIGURE 16.6 Pressure switch monitor
65
17. WATER MIST (CYCLE) RELEASE
Selection #14 of the UTILITY MENU allows the use of mist systems that correspond to NFPA 750. This
configuration allows variable time delays for the mist on/off cycling as well as pause modes. Notice in
figure 17 the center of the menu designates this is a CYCLE MIST release.
NOTE: For the proper real-time function of this configuration to work properly, the device in alarm must
be NON-LATCHING.
17.1 APPLICATIONS
The water mist configuration can be programmed to cycle the mist delivery to obtain maximum effective-
ness in fire suppression while utilizing a minimal amount of water. Applications include industrial electri-
cal equipment, flammable liquid pumping and storage facilities, co-generation power plants, oil refiner-
ies, etc.
17.2 OPERATION
The water mist configuration is designed to operate in fire systems that utilize non-latching detectors.
The control panel monitors the detector(s) fire relay status and determines if a continued mist application
is necessary, should the fire continue.
Upon receiving a confirmed fire signal from the input node, the pre-discharge delay timing sequence will
commence until its time expires. During this time the program counts down to initiate its first discharge
cycle. The mist solenoid will cycle on and off in a timing sequence pre-programmed by the administrator.
There is a provision to stipulate the quantity of complete cycles. After the pre-programmed cycle counts
(mist on & mist off) have been satisfied, the program will enter into a pause mode, maintaining the count
down in seconds. After the expiration of the pause mode, the program will suspend its timing sequences
if the fire has been extinguished. If the fire persists, the node will enter into its second timing sequence.
The number of timing sequences is usually determined by the capacity of the water supply and selected
in the CYCLE COUNT window. Select a timing sequence that will deplete the water supply should the
fire persists.
66
Figure 17 displays the cycle
mist configuration prior to
mapping the nodes or mak-
ing exceptions. Figure 17.1
displays exception boxes
that were filled.
67
17.9 SELECT OTHER
NODE CHANNELS
For this example, the SOM
ID #2, channel 1 and the
RELAY node ID #3, channel
2 was also entered into the
SELECTED OUTPUT
screen in lieu of creating an-
other configuration.
68
[] Based on the data entered in figure 17.1 the alarm
will commit to the delays and reset boxes until all
events have completed.
[] The FIRE STATUS indicator in figure 17.5 indi-
cates the real-time of the alarm input.
69
18. DEDICATED APPLIANCE RESET
Once the input node channel one is acti- FIGURE 18.1 Select the
vated, the alarm will occur to turn on the reset function box.
HORN, STROBE and VENT FAN as the
configuration of figure 13.3 indicates. In
order to implement the remote strobe re-
set, a second configuration is created as
indicated in figure 18. Channel four of the
input node will include a momentary
pushbutton switch to turn off the strobe.
NOTE: The initiating device connected to
the input node can be latching or non-
latching.
70
[] Both configurations are armed and
ready for commands.
71
18.4 CONNECTING A SWITCH TO THE INPUT NODE
Knowing which inputs are not utilized on an input node for other initiating devices, connect a momentary N.O. pushbut-
ton switch with a supervising resistor to an UNUSED channel. Wire the pushbutton into one of the four channels as indi-
cated in Drawing 8, utilizing a 3.9K ELR .
72
19. SILENCING AN AUDIBLE DEVICE AT THE CONTROL PANEL
This section explains the procedure to silence an audible device locally at the control panel. There must
already be configuration(s) that trips an audible device. The configuration utilized in figure 13.3 will be
tripped into alarm to demonstrate this feature. This configuration required the HORN ICON to be se-
lected as indicated in figure 19.1. The TURBINE OPTICAL will trip the horn which can be silenced. In
this example a horn is utilized for the device to be silenced; however, any type of audible device can be
utilized but the HORN ICON must be selected (AT THE SOM). When an alarm occurs, the horn can be
silenced at the touch screen and will reactivate on any successive alarms mapped to this device.
FIGURE 19. Add/Edit details of the input node. FIGURE 19.1 Add/Edit details of the SOM.
73
[] If the administrator wants to manually reinstate the
audible device, select the TURN ON SLENCED DE-
VICE button. These buttons toggle the highlighted
device on & off.
[] Notice in figure 19.5 the STATUS indicates the de-
vice is off.
[] If there are more than one audible devices in alarm
in this configuration, the SILENCE ALL DEVICES
can be selected.
NOTE: Any incoming alarm will re-initialize the appli-
ance based on the configuration created.
[] Select the DONE button to go back to the FIRE
ALARM menu.
[] An audible device can be reset first without silenc-
ing it if the initiating alarm has cleared.
[] Another configuration could be mapped to this FIGURE 19.4 Silence menu selected indicat-
same skid horn turning it on if it was already silenced. ing the horn is turned on.
74
20. CONFIGURING ALARMS WITH NO OUTPUT ACTION
Configurations can be created for applications that utilize the GAS or DIRECT CONNECTION RE-
LEASE where the local panel is alarmed but there is no output node action taken. This style of configu-
ration is useful for recording input actions that will not result in activating an output node but the adminis-
trator can acknowledge the alarm. After an alarm has been activated it will follow the standard proce-
dures of bringing up the gas or fire alarm display and enabling the administrator to reset it. Once reset,
go to the appropriate alarm box at the bottom of the UTILITY menu and select the proper button to view
the recorded action.
75
21. TESTING ALARM CONFIGURATIONS
CAUTION: REMOVE SOLENOID(S) FROM THEIR TANKS PRIOR TO TESTING THE SYSTEM TO
PREVENT ACCIDENTAL AGENT DISCHARGE. Refer to section 21.3 if the administrator chooses
to disable a configuration with a solenoid.
1. MECHANICAL—The most secure method is to physically remove the solenoid from the release
tank. Make sure the solenoid pin is reset after testing prior to connecting back to
the release tank.
WARNING — THE SYSTEM DOES NOT KNOW IF A SOLENOID IS REMOVED FROM A RE-
LEASE TANK.
2. ELECTRICAL— Insert a block valve in series with the solenoid circuit as indicated in drawing 11.
When the block valve is opened, the current path to the solenoid is interrupted
and at the same time a fault is created for that channel.
3. ELECTRONIC— Entering UTILITY MENU #13, MANGE CONFIGURATONS, and UNLOAD a
configuration with a solenoid is another option as described in section 24.2.
As indicated in section 6.8, while in the MANAGE CONFIGURATION menu, #13, the polling is sus-
pends, a fault is created and therefore no alarms will result; however, due to the characteristics of the
nodes, the following events will occur when exiting the manage configuration menu.
1. If a gas configuration is LOADED, the following events will occur: If there is a gas alarm that oc-
curred then went away and then the menu is then exited, the alarm will not be detected.
2. If a fire configuration is LOADED (input, or SOM node is utilized), the following events will occur: If
there is an alarm that occurred then went away and then the MANAGE CONFIGURATION is then
exited, the alarm will be detected.
76
22. MULTIPLE ALARMS
22.1 SYSTEM ALARM MENU
The SYSTEM ALARM menu is a template with corre-
sponding alarm buttons which do not change location
on the menu. Anytime there is an alarm the FIRE,
GAS, WARNING and FAULT button will remain in the
same location on the menu.
77
23. ALARM SEQUENCING, HISTORY and REPORTS
Refer to section 23.6 on how to transfer the following reports to a USB bus drive and print them out.
SAVE ALL- this option prepares all files from #1 through 7 to be copied to the USB bus drive.
SAVE SELECTED - this option allows specific files to be saved.
DELETE ALL- prepares all files in the report file manager to be deleted.
DELETE SELECTED - deletes the selected files.
DONE - Return to the UTILITY MENU.
78
23.5 PRINTING HISTORY FILES
There are three methods to obtain the reports generated from the program and all reports end with a .txt
suffix for the availability of printing on text editors.
Stylus Color 440, 640, 670, 740, 740i, 760, 777 and 777i
Stylus C20UX, C20SX, C40UX, C40S, C40SX, C41UX, C41SX, C41Plus, C42UX, C42SX, C42S,
C42Plus, C43UX, C43SX, C44UX, C44Plus, C45, C46, C60, C61, C62, C63, C64, C65, C66, C80, C82,
C83, C84, C85, C86
Stylus CX3100, CX3200, CX4500, CX4600, CX5100 CX5200, CX5300, CX5400, CX6300, CX6400,
CX6500, CX6600
Stylus Photo 780, 790, 820, 825, 890, 900, 915, 950, 960, 1280
Stylus Photo R200, R210, R300, R310, R320, RX500, RX510, RX600
NOTE: When all configurations are UNLOADED, the node polling is suspended and the fault relay trips.
NOTE: When LOADING or UNLOADING a configuration, the highlight bar descends to the next lower
configuration
NOTE: Configurations that are created and saved are not mapped together. They each reside independ-
ently in the MANAGE CONFIGURATIONS menu. However, they may SHARE a common node channel
if they were mapped to it. An example is where a configuration is completed then another configuration
is created utilizing the same channel on the target node.
80
[] Select the UNLOAD button.
[] The message in figure 24.1 will appear.
NOTE: If this message is left unattended for more
than 30 seconds, the system will automatically com-
mit and UNLOAD the configuration. The UNLOAD
will occur even if the configuration is LOADED again
without exiting the menu.
[] Click on OK to UNLOAD the configuration to con-
tinue and select the EXIT button.
[] More configurations can also be unloaded.
[] The FAULT relay located at TB3 trips and THE
SYSTEM SUSPENDS NODE POLLING.
[] When the EXIT is selected from the MANAGE
CONFIGURATIONS menu the FAULT ALARM
menu automatically appears as shown in figure FIGURE 24.1 This message appears after se-
13.10. lecting unload.
[] The DISABLE relay located at TB3 trips.
[] When the FAULT ALARM button is selected
(figure 13.10), the FAULT ALARM menu appears as
shown in figure 24.2.
[] Select the SILENCE button and the “A” turns to a
“S”, the FAULT relay remains in the same condition,
the audible alarm silences, the FAULT and DIS-
ABLE RELAY remains ON.
[] If the FAULT ALARM screen was to be left unat-
tended, this menu would remain and accumulate
alarms every 30 minutes unless a field device alarm
comes in. Each time another unattended DISABLE
alarm is received, it is located onto the next lower
text line in the menu.
[] When the RESET button is selected the menu in
figure 24.3 appears with the DISABLE ALARM RE-
MINDER note. FIGURE 24.2 A fault alarm is created. Reoc-
curring alarms will appear every 30 minutes
The system requires the administrator to make unless further action is taken.
a decision at this point:
81
[] The reminder message in figure 24.4 appears and
selecting the OK button will remove the beckon mes-
sage screen of the selected configuration(s). The
configuration(s) will be UNLOADED. The fault will be
removed as well as the disable relay action. The
UTILITY menu will return.
NOTE: Do not reload the configuration until the FIGURE 24.4 Select the reset function box.
STOP ALARMS button has been selected to com-
plete the DISABLE. It will take 30 minutes for the
menu in figure 24.4 to reappear to proceed with the
disable, then it is safe to go to the MANAGE CON-
FIGURATIONS menu and load the configuration
again.
1. While in the MANAGE CONFIGURATIONS MENU and a gas configuration is LOADED, the follow-
ing events will occur: If there is a gas or fault alarm that occurred then went away and then the
MANAGE CONFIGURATION is then exited, the alarm will not be detected.
2. While in the MANAGE CONFIGURATIONS MENU and a fire configuration (input, or SOM node is
utilized) is LOADED, the following events will occur: If there is an alarm or fault that occurred then
went away and then the MANAGE CONFIGURATION is then exited, the alarm will be detected.
3. When an input or SOM node configuration is UNLOADED, the nodes will still detect faults.
82
25. ADDING, REMOVING, RESETTING and DETECTING
NODES
83
NOTE: Unlike the FIND NEXT NODE button, this search does not look for the nodes to be in sequential
numerical order. This search indicated the actual node count in the field.
[] Now refer to CHANGE A NODE ADDRESS menu and type in the next node ID, in this case, number
4. Choose the correct style of node, in this case an SOM, then select the CHANGE button.
[] The newly installed SOM now has been reassigned from ID 255 to 4.
[] To synchronize the new node with the onguardsetup.dat file, the system must be closed and restarted
as described in section 26.1.
[] Return to the SETTINGS and ADD/EDIT details of this node and fill in the necessary information.
NOTE: If more than one node was added utilizing the ADVANCE feature, the NODE DETECTION would
indicate each of their address as 255. This identical address is OK as long as each node is a different
style. If the nodes are the same style (like two input nodes) then when the address is change for one the
other will also change. Again, refer to section 5.10 when more than one is added to the bus.
25.7 RESETTING ALL NODE ADDRESSES TO DEFAULT ID 255 WHILE CONNECTED TO THE
BUS
The selection in the ADVANCE menu resets all nodes and data on the bus to their factory default 255.
This procedure may be selected if the administrator would like to start over to change all node ID ad-
dresses simultaneously. If this is the case, then the nodes must be rediscovered by returning to section
5.10 of this manual.
25.9 RESETTING A NODE ADDRESS TO DEFAULT ADDRESS 255 THAT IS REMOVED FROM
THE BUS
To selectively reset a node ID that is removed from the system, simply locate the SW1-1 and SW1– 1
on, apply 24VDC to the power input (observing polarity) for 5 seconds, then remove the power. Now
return both switch poles of SW1 to OFF.
84
25.10 REMOVING A NODE
To remove a node from the system, first verify that there are not other configurations targeting this node.
Go to the UTILITY MENU and select #1, SAVE NODE REPORT and review any other configurations
that may be mapped to this node. To remove a node, any relating configurations must be first
UNLOADED in the MANAGE CONFIGURATIONS menu. If there are other configurations mapped to
this node they must be re-mapped as the administrator requires.
CAUTION: NOT REMOVING ALL ASSOCIATED CONFIGURATIONS TO THIS NODE CAN RESULT
IN A SYSTEM MALFUNCTION.
1. Remove any configuration(s) that are mapped to this node in the MANAGE CONFIGURATIONS
menu.
2. Go to the node to be removed and locate the SW1 switch. Carefully turn ON SW1-1 (Acquire ad-
dress setting).
3. While in the ONGUARD main screen, select F5 on the keyboard to bring up the node menu, high-
light the node to remove, then select the REMOVE NODE button to proceed.
5. Shutdown the system and bus power as described in section 26.1 then physically remove the node.
6. Restart the system then go into the MANAGE CONFIGURATIONS menu and verify the configura-
tions that should be LOADED.
7. Test the system to ensure the integrity is correct.
NOTE: Removing a node leaves an ID address void. This void is OK. If installing a new node later on,
change its ID to the removed node ID.
NOTE: When the REMOVE NODE button is selected, the system automatically sets this node address
to 255.
85
26. REDEFINING A SYSTEM TO START OVER
CAUTION: THE FOLLOWING PROCEDURES DISABLE THE CONTROL PANEL FROM DETECTING
ALARMS
Under special circumstances the administrator may want to revert back to where the system was prior to
implementing any activity. It is important to note that all data stored in the system will be eliminated and
should be backed up, if necessary. To proceed with this process, it is apparent that all necessary pre-
cautions have been made to protect any areas this control panel has supervised. Connect a VGA moni-
tor and mouse to its port located on behind the front panel. If the ONGUARD screen is active, right-click
on the mouse then click on the close icon. Click on the START then navigate to PROGRAMS, then click
on WINDOWS EXPLORER. Double click on the DISKC.
1. Highlight the Onguardsetup.dat file, right click the mouse, click on Delete, then YES. This is the file
that contains all node entry data.
2. Highlight the onguardsetupbak.dat file, right click the mouse, click on Delete, then YES. This is the
backup of the file above created in section 7.3.
3. Delete the CONFIGURATION folder and all files in this folder. This folder is the location of all the
configurations that are created.
4. Delete the REPORTS folder and delete all files in this folder.
5. Now, select the X box to exit out of the Explorer menu to go back to the Windows CE.net screen.
6. To also reset the nodes, refer to section 25. The nodes are not required to be reset if the same node
ID’s are utilized.
7. Proceed with section 26.1
CAUTION: IF THE SYSTEM IS SHUT DOWN FOR ANY REASON, THEN OTHER CONFIGURATIONS
OR ANY OTHER TYPE OF FILE FROM AN EXTERNAL SOURCE IS LOADED, THE CORRECT OP-
ERATION OF THE SYSTEM IS NOT GUARANTEED TO FUNCTION PROPERLY.
86
27. ACCESSING THE UTILITY MENU
87
9. CLEAR ALL ALARM HISTORY DATA
Deletes all data in the UTILITY MENU four DISPLAY buttons at the bottom of the screen and saves the
reports per section 23.7.
10. SYNCHRONIZE ALL NODE LED’S
Synchronizes out-of-order blinking LED’s on the nodes after change of activity.
11. NODE MANAGEMENT
Node data settings and parameters are entered in this menu.
12. SYSTEM CONFIGURATIONS
Maps input nodes to output nodes.
13. MANAGE CONFIGURATIONS
Allows editing of established configurations. Configurations can be activated (loaded) or unloaded. A
command allows unused configurations to be deleted.
14. MODBUS SETUP
Allows the baud rate and other port configurations. This option is described in detail in a separate docu-
ment.
15. DIAGNOSTIS
This section allows the administrator the ability to record events for evaluation. This selection is only util-
ized in conjunction with an Allestec representative.
16. BACKUP THE SYSTEM DATABASE
Allows the system configurations to backup the data in case the primary file gets corrupted. This com-
mand creates a file from the onguardsetup.dat file (see section 7) and calls the new file copyofonguard-
setup.dat. NOTE: Fully understand the operation of the system prior to utilizing this command.
17. USE ONGUARD AS THE SYSTEM SHELL
After a complete system has been tested and backed up, select this menu item. The complete system
will restart and initialize displaying only the ONGUARD menu. This process enables any items related to
the CE operating system to be omitted from the full-sized menu. When this function is complete, there
will be no user interface interaction between the control panel and the Windows CE operating system.
This procedure of disabling the CE user interface prevents unauthorized entry into the CE operating sys-
tem.
CAUTION: DURING THE RESETTING OF THE PANEL TO THE ONGUARD SHELL, THERE WILL
BE NO ALARM MONITORING (APPROXIMATELY 30 SECONDS).
18. USE WINDOWS AS A DEFAULT SHELL
Selecting this option restores the control panel to its level of operation prior to selecting #17.
CAUTION: DURING THE RESTORING OF THE PANEL TO THE WINDOWS SHELL, THERE WILL
BE NO ALARM MONITORING (APPROXIMATELY 30 SECONDS).
88
29. SYSTEM FAULTS
Any fault occurring in the system will bring up the fault menu as indicated in figure 29 and identify the
style of fault. The failsafe fault relay located at the SYSTEM ALARM TB3 terminal will change state. Re-
fer to drawing 6. Select the fault alarm button to enter the FAULT ALARM menu. Select the SILENCE
button to silence the fault. The audible fault alarm will occur every 30 minutes until the problem has been
resolved. Locate and resolve the fault problem in a timely manner.
29.1 COMMUNICATION FAILURE
If there is a communication failure, the inability to
properly scan a node, the problem is recorded as
indicated in figure 29.1, the error message is as fol-
lows: The bus utilizes the first channel of a non com-
municating node to convey the address of the prob-
lem node. In example figure 29.1 the bus was sev-
ered just before the SOM and fault nodes. The
FAULT alarm records the fault as node 3-1 and 2-1
indicating nodes 3 & 2 are not responding. This indi-
cation does NOT indicate channel one of each node
because the COMMUNICATION FAILURE note is
visible.
BUS SHORT:
A direct short between the A and B bus lines will re-
sult in all nodes to report their ID and name to the
FAULT ALARM menu. The alarm menu will be simi-
lar to figure 29.1 except in our example the FAULT
ALARM will indicate all 4 nodes that are attached to
the bus.
24VDC LOSS:
A loss of power to the bus will result in all nodes to
report their faults to the menu. If the power loss oc-
curs down line from the panel, then all nodes after
that power loss will report their fault status. The
FAULT DESCRIPTION field will indicate a communi-
cation error for all nodes unable to report their pres-
ence on the bus. FIGURE 29.2. Loop break failure as de-
scribed in sections 29.3.
89
29.3 COMMUNICATION FAULTS ON A RETURN
CLASS A BUS (Selecting Loop back mode when
invoking Ctrl-F7).
If the system is unable to poll a node in loop back
mode, a fault is issued and below are examples that
may occur.
BUS SHORT:
A bus short creates unreasonable circumstances
that may omit some nodes to report their ID. It is ap-
parent that this problem be resolved in the utmost
timely manner. The system will attempt to display any
messages that get through and report their fault to
the menu.
FIGURE 29.3 Fault alarm menu indicating
A OR B LINE OPEN: channel 1 of the gas node is below 9%.
Upon detecting an open in the loop A or B conductor,
a fault will be issued and will indicate loop break fail-
ure(s), example figure 29.2. All nodes after the bus
break to the TB2 end loop will report their ID’s to the
FAULT ALARM menu. At this point the fault can be
cleared but the ONGUARD menu will now indicate:
Loop Break: Alarms active.
Once the fault is cleared it will not return unless another malfunction occurs. After resetting the fault, a
file is recorded to a memory array that indicates the current location of nodes in respect to the bus
break. The system now monitors part of the nodes on the START loop then returns to the END loop to
monitor at that location. The system is now capable of operating actions correctly but the bus is in need
of a immediate repair. Close the ONGUARD program and turn off the control panel as described in sec-
tion 26.1 then proceed to repair the bus condition. Upon initialization, the system will search all node
locations and eliminate the Loop Break message. Verify that the Ctrl-F7 menu is selecting the Loop
Back mode. NOTE: Anytime the ONGUARD menu indicates a Loop Break, the fault relay will change
state.
90
29.7 4-20mA GAS NODE FAULTS
If the 4-20mA loop is opened or the current drops below –9% of the scale, a fault message will occur.
While in the MANAGE CONFIGURATIONS MENU and a gas configuration is LOADED; if there is a gas
fault alarm that occurred then went away and then the MANAGE CONFIGURATION is then exited, the
alarm will not be detected. The fault will not be created if the channel is disabled whether a configuration
is loaded or unloaded. Refer to section 15.8 for more details.
29.12 NODE MANAGEMENT FAULT- Selecting F5 or line #11 in the utility menu
When selecting the NODE MANAGEMENT menu, the node polling stops because dynamic changes are
expected from the administrator. The FAULT relay changes state as long as this menu is serviced. Upon
exiting the menu the polling will resume and the FAULT relay will resume normal condition.
29.13 MANAGE CONFIGURATION FAULT- Selecting line #13 in the utility menu or Ctrl F11
When selecting the MANAGE CONFIGURATION menu there is a FAULT issued and polling is sus-
pended. The node polling stops because dynamic changes are expected from the administrator.
Refer to section 24.6 for more information.
91
30. SOFTWARE AND FIRMWARE UPDATES
30.1 SOFTWARE MIGRATION
Software and operating systems have been improving towards a more refined and efficient method of
performing computing tasks. To keep in compliance with technology, codes, and improvements, there
will be periodic software and firmware updates available from Allestec. It is possible to upgrade firmware
versions and not software, or vice versa. A revision in the operations manual does not necessarily indi-
cate there will be a change in the code versions, or vice versa. Depending on the upgrade of software,
charges may be incurred to the customer. Instructions will be included with any upgrades as necessary.
Refer to the Allestec website and navigate to the FG8800 control panel for any information relating to
upgrades. Since this system is scaleable, there will be updates as necessary.
92
31. MAINTENANCE and TROUBLESHOOTING
Although the FG8800 was designed to last, like any electronic instrument, there is always the possibility
that something can fail. Therefore a regular test program should be followed and documented to make
sure that each part of the system is tested as described in section 7 of the NFPA 72 or more often if dic-
tated by local code requirements. Malfunctioning units must be replaced or repaired immediately by fac-
tory authorized service personnel in order to insure continued safe and reliable operation of the control
alarm system. Periodic inspection and testing should be performed in accordance with local applicable
codes and standards.
If the system is connected to the fire department, etc., or actuates an internal system, disarm the appro-
priate outputs before servicing to prevent agent actuation. (Refer to Operation for procedures). Notify the
fire department and personnel at the facility that a system test is being performed so that any alarm
sounding can be ignored during the test. Notify the fire department before resetting the system. Inspect-
ing, testing and maintenance of the fire alarm panel should be performed in accordance with NFPA 72,
The Nation Fire Alarm Code and all applicable local codes.
Any suspected problems or product manual discrepancies should be submitted to Allestec by email at
[email protected]. Please state your company name, your name and phone number. For the control
panel issues state the number of nodes attached to the system, terminated or continuous loop configu-
ration and any other information to help diagnose the system. It is important to list the version release as
stated in section 30.
93
32. PART NUMBERS AND ACCESSORIES
ACCESSORIES
OPERATIONS MANUAL 8800-5140-REV A
TERMINAL STRIP SCREWDRIVER 8800-2614
END OF LINE RESISTOR - BUS 120 OHMS, 5% 8800-1309
END OF LINE RESISTOR - FIELD DEVICES 3.9K OHMS, 5% 8800-1211
35MM DIN MOUNTING ADAPTER [INPUT AND 4-20MA NODE] 8800-5121
35MM DIN MOUNTING ADAPTER [SOM AND RELAY NODE] 8800-5139
94
33. SPECIFICATIONS
ELECTRICAL
SYSTEM OPERATING VOLTAGE, 18 30 VDC REDUNDANT POWER REQUIRED
CONTROL PANEL MAXIMUM CURRENT 1.0 AMP @ 24 VDC
NO ATTACHED DEVICES OR LOCAL RELAYS
8800 1060 INPUT NODE: 24 VDC 20 mA QUIESCENT, 35 mA ALARMED
8800 1700 4-20MA GAS NODE: 24 VDC 14 mA QUIESCENT, 14 mA ALARMED
MECHANICAL
ENVIRONMENT
95
34. WARRANTY AND RETURN POLICY
TERMS AND AGREEMENT
Allestec Corporation warrants the components and labor for three years from control date stamped on
the system identification label. Allestec identifies each system by their unique serial number stamped on
the components as well as an electronic serial number. Allestec will repair any component found by us
to be defective in workmanship or materials. This warranty does not apply to any part or product that has
been subjected to misuse, improper installation, transfer of ownership, or any type of alterations.
Items under warranty sent to Allestec just to “check out” will be charge for diagnosing something there
may not be. This procedure prevents customers from sending units in on an as needed basis for us to
verify operation. If a product is in warranty it will be repaired at no charge.
There are no implied warranties of merchantability, fitness or other implied warranties or representations
for any of Allestec's products except the warranty specified herein. In no event shall Allestec be liable for
any consequential, special or other damages attributable to our product except as specified herein. The
foregoing obligations are in lieu of all other obligations and liabilities including negligence, and of all war-
ranties of merchantability or fitness for a particular purpose or otherwise, express, or implied, in fact or in
law, and state Allestec's entire and exclusive liability and buyer's exclusive remedy for any claim of dam-
ages in connection with the sale of furnishing of the products, their design, suitability for use, installation,
or operation. Buyer is solely responsible for the proper installation, maintenance and use of the compo-
nents and Allestec will in no event be liable for any special, incidental or consequential damages what-
soever.
It is agreed that when a customer, distributor, representative, end user purchases any of the FG8800
systems or components that it is their responsibility to send back the product under warranty. The prod-
uct under warranty is to be returned to Allestec or its distributor, pre-paid by the entity returning the prod-
uct. Under no circumstances Allestec will send a product to a customer then wait for the warranty item to
return. Allestec will return the warranty item by its selected carrier on a standard delivery time. If the cus-
tomer requires to accelerate the process, the customer agrees to pay any additional expediting costs
relating to the transaction.
96