Notifier

From HSYCO
Revision as of 18:44, 16 March 2016 by Ulde (talk | contribs) (→‎3.5.1)
Jump to navigation Jump to search

The NOTIFIER AM-2000, AM-4000 and AM-6000 are multi-area fire panels. The integration with HSYCO can be accomplished via a standard Modbus RTU slave interface.

IO Server Notifier Panel.png

Communication

The NOTIFIER SIB 600 Modbus interface is required. The default connection parameters are:

Modbus address: 1 ... 32

RS-485 parameters:

Baud rate 9600
Data bits 8
Stop bit 1
Parity none
Flow control none

Refer to the Notifier manuals for installation, wiring and power supply requirements.

Here's a screenshot of the manual:

Notifier Sib600.png

RS485 MODBUS port is on pin 5,6,7

It's mandatory to enable the SIB 600 module with UPLOAD PK 2000, PK4000 or PK6000. The MODBUS address must be assigned in the TCP/IP field.

HSYCO Configuration

Add a NOTIFIER I/O Server in the I/O Servers section of the Settings and set its parameters:

Communication

  • Comm ID: select a MODBUSTCP I/O server if using a Modbus gateway, or the serial port id when using a direct RS-485 port with HSYCO acting as Modbus RTU master.

High Availability

  • Shutdown when inactive: defaults to false.

Options

ID Default Values Description
address 1 1 ... 32 the panel’s Modbus address
gui true true enable support for the UI object, UISET actions and USER commands
false disable UI support
startupevents false true generate IO events also during the driver’s start-up phase
false start generating events only after HSYCO is aligned with the current status of the system
pollinterval 1 > 0 set to the highest zone number configured in the panel. Set to 0 to disable zone status polling and control commands
lastzone 150 0 ... 150 set to the highest zone number configured in the panel. Set to 0 to disable zone status polling and control commands
loglines 100 ≥ 0 if GUI support is enabled, set to the maximum number of lines to show in the log text object. Set to 0 to disable the GUI log

Datapoints

ID Value R/W Description
connection online R connection established
offline R HSYCO can't connect to the panel
annunciator.<n>.<m>.offline 1 R annunciator <n>.<m> offline
0 R annunciator <n>.<m> online
annunciator.<n>.<m>.fault 1 R annunciator <n>.<m>fault
0 R annunciator <n>.<m> no fault
annunciator.<n>.<m>.cfg.error 1 R annunciator <n>.<m> configuration error
0 R annunciator <n>.<m> configured
lcd.<n>.offline 1 R LCD <n> offline
0 R LCD <n> online
lcd.<n>.fault 1 R LCD <n> fault
0 R LCD <n> no fault
lcd.<n>.cfg.error 1 R LCD <n> configuration error
0 R LCD <n> configured
loop.<n>.short 1 R loop <n> short circuit
0 R loop <n> no short circuit
loop.<n>.open 1 R loop <n> open fault
0 R loop <n> no open fault
loop.<n>.voltage 1 R loop <n> low voltage fault
0 R loop <n> no low voltage fault
module.<l>.<n>.normal 1 R module <n> on loop <l> normal state
0 R module <n> on loop <l> error state
module.<l>.<n>.disabled 1 R module <n> on loop <l> disabled
W disable module <n> on loop <l>
0 R module <n> on loop <l> enabled
W enable module <n> on loop <l>
module.<l>.<n>.disabled 1 R module <n> on loop <l> output active (ON)
W turn ON out of module <n> on loop <l>
0 R module <n> on loop <l> output not active (OFF)
W turn OFF out of module <n> on loop <l>
module.<l>.<n>.fault 1 R module <n> on loop <l> fault
0 R module <n> on loop <l> no fault
module.<l>.<n>.alarm 1 R module <n> on loop <l> alarm
0 R module <n> on loop <l> no alarm
panel.fault.batt.disconn 1 R batteries disconnected
0 R batteries connected
panel.fault.power 1 R batteries disconnected
0 R batteries connected
panel.fault.batt.unbal 1 R batteries disconnected
0 R batteries connected
panel.fault.batt.fail 1 R batteries unbalanced charge
0 R batteries no unbalanced charge
panel.fault.bex 1 R external batteries fault
0 R no external batteries fault
panel.fault.earth 1 R ground connection fault
0 R no ground connection fault
panel.fault.undervoltage 1 R AC power under-voltage fault
0 R no AC power under-voltage fault
panel.fault.overvoltage 1 R AC power over-voltage fault
0 R no AC power over-voltage fault
panel.fault.loop.open 1 R at least one loop is open
0 R no loops open
panel.fault.loop.short 1 R at least one loop short circuit
0 R no loop short circuit
panel.fault.fuse.user 1 R fuse fault
0 R fuse ok
panel.fault.batt.charger.undervoltage 1 R battery charger under-voltage fault
0 R no battery charger under-voltage fault
panel.fault.batt.charger.overvoltage 1 R battery charger over-voltage fault
0 R no battery charger over-voltage fault
panel.filesystem.clear.error 1 R memory delete error
0 R no memory delete error
panel.filesystem.init.error 1 R memory initialization error
0 R no memory initialization error
panel.reliab.par.mod 1 R reliability parameters modified warning
0 R no reliability parameters modified warning
panel.hardkey.enabled 1 R hardware programming key enabled
0 R hardware programming key not enabled
panel.power.on 1 R power on phase
0 R power on phase completed
panel.wdt.reset 1 R main CPU watchdog fault
0 R main CPU watchdog ok
panel.cfg.error 1 R configuration error
0 R configuration ok
panel.filesystem.error 1 R memory corruption
0 R memory ok
panel.hard.clock 1 R internal hardware clock fault
0 R internal hardware clock ok
panel.arch.full 1 R log archive full
0 R log archive not full
panel.arch.full.warning 1 R log archive warning (80% full)
0 R no log archive warning
panel.zone.default 1 R sensors not yet assigned to zones
0 R zones assignment done
panel.sib.offline 1 R SIB board offline
0 R SIB board online
panel.sib.not.prg 1 R SIB board not programmed
0 R SIB board programmed
panel.pc.invalid.cmd 1 R invalid command from PC
0 R no invalid command from PC
panel.arch.disabled 1 R log archive disabled
0 R log archive disabled
panel.lib.<n>.offline 1 R LIB board <n> offline
0 R LIB board <n> online
panel.lib.<n>.cfg.error 1 R LIB board <n> configuration error
0 R LIB board <n> configured
panel.lib.<n>.not.prg 1 R LIB board <n> not programmed
0 R LIB board <n> programmed
panel.fire silence W fire alarm silence
reset R fire alarm reset
panel.fire.normal 1 R fire panel normal state
0 R fire panel error state
panel.fire.exclusions 1 R fire panel has one or more disabled components
0 R fire panel’s all components are enabled
panel.fire.test 1 R fire panel test
0 R fire panel no test
panel.fire.fault 1 R fire panel fault
0 R fire panel no fault
panel.fire.alarm 1 R fire panel alarm
0 R fire panel no alarm
panel.fire.alarm.silent 1 R fire panel alarm silenced
0 R fire panel no alarm silenced
panel.fire.unknown 1 R fire panel unknown events
0 R fire panel no unknown events
panel.tech silence R technical alarm silence
reset R technical alarm reset
panel.tech.normal 1 R technical panel normal state
0 R technical panel error state
panel.tech.exclusions 1 R technical panel has one or more disabled components
0 R technical panel’s all components are enabled
panel.tech.test 1 R technical panel test
0 R technical panel no test
panel.tech.fault 1 R technical panel fault
0 R technical panel no fault
panel.tech.alarm 1 R technical panel alarm
0 R technical panel no alarm
panel.tech.unknown 1 R technical panel unknown events
0 R technical panel no unknown events
sensor.<l>.<n>.normal 1 R sensor <n> on loop <l> normal state
0 R sensor <n> on loop <l> error state
sensor.<l>.<n>.disabled 1 R sensor <n> on loop <l> disabled
W disable sensor <n> on loop <l>
0 R sensor <n> on loop <l> enabled
W enable sensor <n> on loop <l>
sensor.<l>.<n>.prealarm.1 1 R sensor <n> on loop <l> pre-alarm 1
0 R sensor <n> on loop <l> pre-alarm 1 off
sensor.<l>.<n>.prealarm.2 1 R sensor <n> on loop <l> pre-alarm 2
0 R sensor <n> on loop <l> pre-alarm 2 off
sensor.<l>.<n>.fault v R sensor <n> on loop <l> fault (see sensor fault error table below)
0 R sensor <n> on loop <l> no fault
sensor.<l>.<n>.alarm 1 R sensor <n> on loop <l> alarm
0 R sensor <n> on loop <l> no alarm
zone.<n>.normal 1 R zone <n> normal state
0 R zone <n> error state
zone.<n>.disabled 1 R zone <n> disabled
W disable zone <n>
0 R zone <n> enabled
W enable zone <n>
zone.<n>.fault 1 R zone <n> fault
0 R zone <n> no fault
zone.<n>.alarm 1 R zone <n> alarm
0 R zone <n> no alarm

Sensors fault values for generic sensors

The value v of the fault data point can be the combination (sum) of multiple error values.

Value ID Description
1 EDEINST not installed
4 EINV not responding
8 EFAULTTYPEID type id fault
16 EDRIFT type id fault
32 EDRIFT maintenance
64 ELOW low value


Sensors fault values for GASS or OXY sensors

The value v of the fault data point can be the combination (sum) of multiple error values.

Value ID Description
1 EDEINST not installed
4 EINV not responding
8 EFAULTTYPEID type id fault

User Interface

UISET Actions

You can use any object that accepts a text attribute, usually text, but also marquee and others, to display the status of the system according to the following table:

ID Attribute Set to
log value a textual log of all relevant events. The last event is at the top, with older events scrolled down, then removed from the log past the log lines limit
log0 value latest line of the security log when a new entry is added, set back to blank after a short period
offline.label visible true when HSYCO can’t connect to the Notifier panel, false otherwise
annunciator.<n>.<m>.offline.label visible true when annunciator <n>.<m> is offline
annunciator.<n>.<m>.fault.label visible true when annunciator <n>.<m> fault
annunciator.<n>.<m>.cfg.error.label visible true when annunciator <n>.<m> has a configuration error
cd.<n>.offline.label visible true when LCD <n> is offline
lcd.<n>.fault.label visible true when LCD <n> is showing a fault condition
lcd.<n>.cfg.error.label visible true when LCD <n> has a configuration error
loop.<n>.short.label visible true when loop <n> short circuit
loop.<n>.open.label visible true when loop <n> is open
loop.<n>.voltage.label visible true when loop <n> voltage is too low
module.<l>.<n>.normal.label visible true when module <n> on loop <l> normal state
module.<l>.<n>.disabled.label visible true when module <n> on loop <l> disabled
module.<l>.<n>.out.label visible true when module <n> on loop <l> output is ON
module.<l>.<n>.fault.label visible true when module <n> on loop <l> fault
module.<l>.<n>.alarm.label visible true when module <n> on loop <l> alarm
panel.fire.normal.label visible true when fire panel normal state
panel.fire.exclusions.label visible true when fire panel has one or more disabled components
panel.fire.test.label visible true when fire panel test mode
panel.fire.fault.label visible true when fire panel fault
panel.fire.alarm.label visible true when fire panel alarm
panel.tech.normal.label visible true when technical panel normal state
panel.tech.exclusions.label visible true when technical panel has disabled components
panel.tech.test.label visible true when technical panel test mode
panel.tech.fault.label visible true when technical panel fault
panel.tech.alarm.label visible true when technical panel alarm
sensor.<l>.<n>.normal.label visible true when sensor <n> on loop <l> normal state
sensor.<l>.<n>.disabled.label visible true when sensor <n> on loop <l> disabled
sensor.<l>.<n>.prealarm.1.label visible true when Sensor <n> on loop <l> pre-alarm 1
sensor.<l>.<n>.prealarm.2.label visible true when Sensor <n> on loop <l> pre-alarm 2
sensor.<l>.<n>.fault.label visible true when sensor <n> on loop <l> fault
sensor.<l>.<n>.alarm.label visible true when sensor <n> on loop <l> alarm
zone.<n>.normal.label visible true when zone <n> normal state
zone.<n>.disabled.label visible true when zone <n> disabled
zone.<n>.fault.label visible true when zone <n> fault
zone.<n>.alarm.label visible true when zone <n> alarm

USER Commands

You can use the user object, or any other GUI object that generates user events, to execute any command that could be sent writing to a data point, as defined in the | Datapoints table. Set the user object’s name field to the datapoint (event) name, prefixed by the IO Server id, and its param field to the value that should be written to execute the command.

For example, to disable zone 1, use the following object:

(user fire.zone.1.disabled; 1; r4c2; gr; zone 1 off)

To enable zone 1:

(user fire.zone.1.disabled; 0; r4c3; gr; zone 1 on)

Release Notes

3.5.1

  • minor changes to the sensor.<l>.<n>.fault data point

3.3.0

  • initial release


Honeywell and Notifier are registered trademarks owned by Honeywell International Inc., or its subsidiaries or affiliates.