Fire
alarm inputs are not the easiest thing in the world to set up but this guide
aims to provide a step by step example that will allow you to become proficient
at adding a fire alarm input to any Nexus system.
Note: This relates only to a fire alarm panel that has
a latching relay output and not a pulsed relay output.
There
are five steps to follow, these being:-
To
create an alarm message select Alarm Messages from the Config menu...
The "Alarm
names, Textual messages and Alarm Page pointers" page will be displayed.
This may or may not have information displayed, depending if any alarms
had previously been set up on the system.
To create the Alarm Message you should enter the information shown in the
following image, use the first available Alarm slot - the example shows
Alarm 2 being used. It doesn't actually matter which Alarm slot is used
as the alarm is referred to by its name (which is "Fire Alarm"
in this example.) in the Fire Alarm reader logic that will be created later
in this example.
You
have now created the Alarm Message.
_________________________________________________________________________________________
_________________________________________________________________________________________
The
Alarm Message is the message that will be displayed on the Transaction Monitor
whenever the fire alarm input is triggered.
Global
variables are automatically passed to each Nexus controller and in this example
one global variable will be used to tell all Nexus controllers on the network
(this includes all controller loops) to unlock their doors.
The state (True or False) of a global variable is actually checked and acted
upon in a Reader Logic script, there can be up to 16 global variables defined
and these would be referred to in the Reader Logic script as G01, G02, G03
etc. We will create a new Reader Logic script later that will check our new
global variable.
To
create a global variable select Interconnectivity from the Config menu...
The
"Internal Variable and Script Processing" page will be displayed.
This may or may not have information displayed, this depends if any global
variables had previously been set up on the system.
To create the Global Variable you should enter the information shown in the
following image, use the first available Global slot - the example shows Global
1 being used.
The global variable will be referred to in the Fire Alarm reader logic that
will be created later in this example as G01 as it is Global 1 that is being
created. If we had used Global 2 then we would refer to it as G02 in the reader
logic.
Create
a Fire Alarm reader logic script
_________________________________________________________________________________________
The most
important piece of information entered above reads:
ALARM_STATE 1 1 3 3
this refers to where the alarm input is processed, and can be read as:
ALARM_STATE 'loop' 'controller' 'reader' 'alarm condition'
Where:
'loop' is the communications loop for the controller that the fire alarm will
be connected to.
'controller' is the controller that the fire alarm will be connected to.
'reader' is the reader that the fire alarm will be connected to.
'alarm condition' is the Alarm Condition that is checking the actual input
that the fire alarm is connected to.
So, for this example the Fire Alarm will be connecter to an input that is
used by the third reader on the first controller of communications loop one.
Exactly which input is used will be specified in the Alarm Conditions section
of the Reader Logic script that is allocated to that reader.
A
reader logic script can be thought of as a set of instructions that defines
the way a reader will work. Each reader on a system can, if required, be assigned
a different reader logic script to customise the operation of the system.
By default each reader has Standard Logic assigned to it, Standard Logic gives
each reader the basic functionality needed to open a door upon a valid card
read.
To
create a fire alarm reader logic script select Reader Logic from the Config
menu...
The
"Reader Logic Library" page will be displayed. This may or may not
have more than the default Standard Logic displayed.
To create the new reader logic type in the name Fire Alarm in the first available
logic slot and then press the Selection button to the right of where you entered
the name - the example shows Logic 3 being used.
The
reader logic editor will be displayed, this will show a blank reader logic.
You should now copy the logic script exactly as shown in the following panel
images to the reader logic editor.
Latch
Conditions:
The following configures Latch 1 to be Set when output 1 (O01) is TRUE and
and to be Reset when CCM Input 2 (C02) is True.
Output
Conditions:
The following configures Output 1 to be Set if timer 1 (T01) is True or if
global variable 1 (G01) is TRUE, if both T01 and G01 are not TRUE the output
1 will not be set.
Timer Settings
and Conditions
A Timer can be set to TRUE by its condition and will remain TRUE for the duration
it is configured for.
The following configures:
Timer 1 to be TRUE if a valid card is presented at the reader (OPN) or if
CCM input 1 (C01) is TRUE and will stay TRUE for 3 seconds.
Timer 2 to be TRUE if CCM input 2 (C02) is TRUE and will stay TRUE for 20
seconds.
Timer 3 to be TRUE if CCM input 2 (C02) is TRUE or if Latch 1 (L01) is TRUE
and will stay true for 1 second.
Alarm
Conditions
There are three alarms listed:
Alarm 1 is a door open alarm and is triggered when timer 2 (TO2)goes FALSE.
Alarm 2 is a door forced alarm and is triggered when Timer 3 (T03) goes FALSE.
Alarm 3 is the fire alarm and is triggered when CCM input 4 (C04) goes FALSE.
We set the condition for alarm 3 to the input (C04~) we are going to connect
the fire alarm to, in this case the fire alarm input is normally closed going
open. If we wished the fire alarm input to be normally open going closed then
we would change C04~ to C04.
_________________________________________________________________________________________
The
AROC Time Zones and Department Check panels are not relevant to this example.
Modifying
Other Reader Logic Scripts
_________________________________________________________________________________________
Assign
Fire Alarm reader logic to the appropriate reader
All
other reader logic scripts that are being used must be modified to include
a check for the previously created global variable Global 1 (G01). This is
to ensure all readers act upon the global variable and unlock their doors.
For this example we will assume that the only other reader logic in use is
the Standard Logic script.
The
Fire Alarm reader logic must now be assigned to the reader that it will be
used for. You will know from the section 'Create a Global Variable' that in
this example we will be assigning the Fire Alarm reader logic to reader 3
of controller 1 on communications loop 1.
The
"Reader Logic Library" page will be displayed. This may or may not
have more than the default Standard Logic script and the new Fire Alarm script
displayed.
Press the Selection button to the right of the Standard Logic name.
The
"Reader Loop Names" page will be displayed.
Press the Select button for Loop 1....
To
modify the Standard Logic script select Reader Logic from the Config menu...
_________________________________________________________________________________________
There
is only one modification that needs to be made, this is to the Output Conditions.
The change to be made is to add G01+ to the condition for Output 1, this is
shown in the following image.
To
assign the Fire Alarm reader logic select Loops & Readers from the Config
menu...
The
details for Loop 1 will be displayed. You should now set the Reader Logic
for reader three to Fire Alarm. This is shown in the following image.
Thats all
there is to setting up a fire alarm input on a Nexus system. You now need
to connect the output from the fire alarm panel to the input designated the
fire alarm input on the Nexus panel.
To determine
which physical input the fire alarm panel should be connected to we need to
look at the reader resources allocated to reader 3, reader 3 is the reader
that has the fire alarm script running on it.
As
can be seen from the Reader Resource 'NEXUS C', CCM 4 is allocated to CC Input
14. CC Input 14 actually means the 14th input on the Nexus panel, as there
are 8 inputs on each reader module the 14th input will be located on the second
reader module which is reader 3 and reader 4.
Therefore
the output from the Fire Alarm should be connected to the 6th input of the
second reader module.
View
the details for Loop 1 again (see the previous section) and check which DPU
Resources are assigned to reader 3, in this example the DPU Resources are NEXUS
C.
Now
that we know NEXUS C are the resources we need to look at them, to do this select
Reader Resources from the Config menu...
The
Reader Resource Library will be displayed...
Now
select 'NEXUS C' (Resource 8)
The details for NEXUS C will be displayed.
Conclusion
Under
Construction
To check a pulsed relay
output. Set a latch with it, check the latch instead of the input and clear
the latch with a button on the tool-bar.
L02 set = C02
L02 Reset = G05
G05 is a tool bar button.
