Difference between revisions of "Fp2000"

From HSYCO
Jump to navigation Jump to search
(Created page with "Aritech Interlogix FP2000 is a multi-area fire panel. The integration with HSYCO can be accomplished via direct control through the RS232 port on the panel. The FP2000 I/O Ser...")
 
Line 98: Line 98:
 
!R/W
 
!R/W
 
!Description
 
!Description
−
 
 
|-
 
|-
  
Line 109: Line 108:
 
|R
 
|R
 
|HSYCO can't connect to the panel
 
|HSYCO can't connect to the panel
−
 
 
|-
 
|-
  
−
|rowspan="4" |armed
+
|rowspan="4" |emulation
 
|rowspan="2" |1
 
|rowspan="2" |1
 
|R
 
|R
−
|at least one area is armed
+
|emulation is active
 
|-
 
|-
 
|W
 
|W
−
|arm all active areas
+
|activate emulation
 
|-
 
|-
 
|rowspan="2" |0
 
|rowspan="2" |0
 
|R
 
|R
−
|no area is armed
+
|emulation is disabled
 
|-
 
|-
 
|W
 
|W
−
|disarm all active areas
+
|disable emulation
−
 
 
 
|-
 
|-
  
−
|rowspan="3" |alarm
+
|rowspan="3" |led.general.fire.1
−
|1
+
led.general.fire.2
 +
led.general.processor
 +
led.general.supply.fault
 +
led.general.disabled
 +
led.general.fault
 +
led.general.supply
 +
led.general.system.fault
 +
led.brigade.delay.off
 +
led.brigade.delay.on
 +
led.brigade.stop
 +
led.brigade.fault
 +
led.brigade.signal
 +
led.sounder.delay.on
 +
led.sounder.silence
 +
led.sounder.fault
 +
led.sounder.sound
 +
led.sounder.delay.off
 +
led.control.test
 +
led.control.disabled
 +
led.control.silence.buzzer
 +
led.all
 +
led.panel
 +
|on
 
|R
 
|R
−
|at least one area is in alarm
+
|the corresponding LED is on
 
|-
 
|-
−
|0
+
|off
 
|R
 
|R
−
|no area is in alarm
+
|the corresponding LED is off
 
|-
 
|-
−
|reset
+
|blink
 
|W
 
|W
−
|reset system alarms
+
|the corresponding LED is on, blinking
−
 
 
 
|-
 
|-
  
−
|rowspan="2" |clock
+
|status.alarm.count
−
|read
+
|<num>
−
|W
 
−
|request the reading of the panel’s clock value
 
−
|-
 
−
|<date_time>
 
 
|R
 
|R
−
|the panel’s clock is set to <date_time>. The value has the format "yyyy-mm-dd hh:mm:ss" (e.g. "2012-12-30 16:59:23").
+
|count of fires
−
This event is only triggered after a request.
 
−
 
 
 
|-
 
|-
  
−
|a<n>.name
+
|status.fault.count
−
|<text>
+
|<num>
 
|R
 
|R
−
|area <n> has been assigned the name <text>
+
|count of faults
−
 
 
 
|-
 
|-
  
−
|z<n>.name
+
|status.condition.count
−
|<text>
+
|<num>
 
|R
 
|R
−
|zone <n> has been assigned the name <text>
+
|count of conditions
−
 
 
 
|-
 
|-
  
−
|rowspan="5" |a<n>.armed
+
|status.event.count
−
|rowspan="2" |1
+
|<num>
 
|R
 
|R
−
|area <n> is armed
+
|count of all the events other than fire, fault or condition
−
|-
 
−
|W
 
−
|arm area <n>
 
−
|-
 
−
|rowspan="2" |0
 
−
|R
 
−
|area <n> is disarmed
 
−
|-
 
−
|W
 
−
|disarm area <n>
 
−
|-
 
−
|force
 
−
|W
 
−
|force arm area <n>
 
−
 
 
 
|-
 
|-
  
−
|rowspan="2" |a<n>.alarm
+
|rowspan="4" |clock
−
|1
+
|rowspan="2" |<val>
 
|R
 
|R
−
|area <n> is in alarm
+
|<date_time>
−
|-
 
−
|0
 
−
|R
 
−
|area <n> is not in alarm
 
−
 
 
−
|-
 
−
 
 
−
|rowspan="2" |a<n>.open
 
−
|1
 
 
|R
 
|R
−
|area <n> has open zones
+
|the panel’s clock is set to <date_time>. The value has the format "yyyy-mm-dd hh:mm:ss" (e.g. "2012-12-30 16:59:23")
 
|-
 
|-
−
|0
 
−
|R
 
−
|area <n> has no open zones
 
−
 
−
|-
 
−
 
−
|rowspan="2" |a<n>.isolated
 
−
|1
 
−
|R
 
−
|area <n> has isolated zones
 
−
|-
 
−
|0
 
−
|R
 
−
|area <n> has no isolated zones
 
−
 
−
|-
 
−
 
−
|rowspan="2" |a<n>.exit
 
−
|1
 
−
|R
 
−
|exit time is active on area <n>
 
−
|-
 
−
|0
 
−
|R
 
−
|exit time is not active on area <n>
 
−
 
−
|-
 
−
 
−
|rowspan="2" |a<n>.entry
 
−
|1
 
−
|R
 
−
|entry time is active on area <n>
 
−
|-
 
−
|0
 
−
|R
 
−
|entry time is not active on area <n>
 
−
 
−
|-
 
−
 
−
|rowspan="2" |a<n>.alarm.local
 
−
|1
 
−
|R
 
−
|local alarms are active on area <n>
 
−
|-
 
−
|0
 
−
|R
 
−
|no local alarm is active on area <n>
 
−
 
−
|-
 
−
 
−
|rowspan="2" |a<n>.warning
 
−
|1
 
−
|R
 
−
|console warning is active on area <n>
 
−
|-
 
−
|0
 
−
|R
 
−
|console warning is not active on area <n>
 
−
 
−
|-
 
−
 
−
|rowspan="6" |z<n>.state1<sup>[[#note|[Note]]]</sup>
 
−
|tamper
 
−
|R
 
−
|tamper active on zone <n>
 
−
|-
 
−
|alarm
 
−
|R
 
−
|alarm active on zone <n>
 
−
|-
 
−
|closed
 
−
|R
 
−
|zone <n> closed
 
−
|-
 
−
|night
 
−
|R
 
−
|night holdup active on zone <n>
 
−
|-
 
−
|local
 
−
|R
 
−
|local alarm active on zone <n>
 
−
|-
 
−
|isolated
 
−
|R
 
−
|zone <n> isolated
 
−
 
−
|-
 
−
 
−
|rowspan="5" |z<n>.state2<sup>[[#note|[Note]]]</sup>
 
−
|short
 
−
|R
 
−
|zone <n> in short circuit
 
−
|-
 
−
|open
 
−
|R
 
−
|zone <n> open
 
−
|-
 
−
|closed
 
−
|R
 
−
|zone <n> closed
 
−
|-
 
−
|active
 
−
|R
 
−
|zone <n> active
 
−
|-
 
−
|masked
 
−
|R
 
−
|zone <n> masked
 
−
 
−
|-
 
−
 
−
|rowspan="2" |z<n>.isolated
 
−
|1
 
−
|W
 
−
|isolate zone <n>
 
−
|-
 
−
|0
 
−
|W
 
−
|de-isolate zone <n>
 
−
 
−
|-
 
−
 
−
|z<n>.alarm
 
−
|reset
 
 
|W
 
|W
−
|reset alarms on zone <n>
+
|set the data e and time of the panel to <date_time>. The value has the format "yyyy-mm-dd hh:mm:ss" (e.g. "2012-12-30 16:59:23")
−
 
 
 
|-
 
|-
−
 
+
|rowspan="2" |read
−
|rowspan="4" |o<n>.active
 
−
|rowspan="2" |1
 
 
|R
 
|R
−
|output <n> is active
+
|
 
|-
 
|-
 
|W
 
|W
−
|activate output <n>
+
|request for reading date and time set on the panel
 
|-
 
|-
−
|rowspan="2" |0
 
−
|R
 
−
|output <n> is not active
 
−
|-
 
−
|W
 
−
|deactivate output <n>
 
−
 
−
|-
 
−
 
−
|rowspan="2" |o<n>.inverted
 
−
|1
 
−
|R
 
−
|output <n> is inverted
 
−
|-
 
−
|0
 
−
|R
 
−
|output <n> is not inverted
 
−
 
−
|-
 
−
 
−
|rowspan="2" |ras<n>.offline
 
−
|1
 
−
|R
 
−
|RAS <n> is offline
 
−
|-
 
−
|0
 
−
|R
 
−
|RAS <n> is online
 
−
 
−
|-
 
−
 
−
|rowspan="2" |ras<n>.tamper
 
−
|1
 
−
|R
 
−
|RAS <n> is tampered
 
−
|-
 
−
|0
 
−
|R
 
−
|RAS <n> is not tampered
 
−
 
−
|-
 
−
 
−
|rowspan="2" |ras<n>.isolated
 
−
|1
 
−
|R
 
−
|RAS <n> is isolated
 
−
|-
 
−
|0
 
−
|R
 
−
|RAS <n> is not isolated
 
−
 
−
|-
 
−
 
−
|rowspan="2" |ras<n>.inhibited
 
−
|1
 
−
|R
 
−
|RAS <n> is inhibited
 
−
|-
 
−
|0
 
−
|R
 
−
|RAS <n> is not inhibited
 
−
 
−
|-
 
−
 
−
|rowspan="2" |dgp<n>.offline
 
−
|1
 
−
|R
 
−
|DGP <n> is offline
 
−
|-
 
−
|0
 
−
|R
 
−
|DGP <n> is online
 
−
 
−
|-
 
−
 
−
|rowspan="2" |dgp<n>.isolated
 
−
|1
 
−
|R
 
−
|DGP <n> is isolated
 
−
|-
 
−
|0
 
−
|R
 
−
|DGP <n> is not isolated
 
−
 
−
|-
 
−
 
−
|rowspan="2" |dgp<n>.inhibited
 
−
|1
 
−
|R
 
−
|DGP <n> is inhibited
 
−
|-
 
−
|0
 
−
|R
 
−
|DGP <n> is not inhibited
 
−
 
−
|-
 
−
 
−
|rowspan="2" |dgp<n>.battery.missing
 
−
|1
 
−
|R
 
−
|battery missing on DGP <n>
 
−
|-
 
−
|0
 
−
|R
 
−
|battery ok on DGP <n>
 
−
 
−
|-
 
−
 
−
|rowspan="2" |dgp<n>.battery.low
 
−
|1
 
−
|R
 
−
|battery low on DGP <n>
 
−
|-
 
−
|0
 
−
|R
 
−
|battery ok on DGP <n>
 
−
 
−
|-
 
−
 
−
|rowspan="2" |dgp<n>.battery.test
 
−
|1
 
−
|R
 
−
|battery test active on DGP <n>
 
−
|-
 
−
|0
 
−
|R
 
−
|no battery test active on DGP <n>
 
−
 
−
|-
 
−
 
−
|rowspan="2" |dgp<n>.battery.test.fail
 
−
|1
 
−
|R
 
−
|battery test failed on DGP <n>
 
−
|-
 
−
|0
 
−
|R
 
−
|battery test ok on DGP <n>
 
−
 
−
|-
 
−
 
−
|rowspan="2" |dgp<n>.mains.fail
 
−
|1
 
−
|R
 
−
|mains failure on DGP <n>
 
−
|-
 
−
|0
 
−
|R
 
−
|mains ok on DGP <n>
 
−
 
−
|-
 
−
 
−
|rowspan="2" |dgp<n>.fuse.fail
 
−
|1
 
−
|R
 
−
|fuse failure on DGP <n>
 
−
|-
 
−
|0
 
−
|R
 
−
|fuses ok on DGP <n>
 
−
 
−
|-
 
−
 
−
|rowspan="2" |dgp<n>.siren.fail
 
−
|1
 
−
|R
 
−
|siren failure on DGP <n>
 
−
|-
 
−
|0
 
−
|R
 
−
|siren ok on DGP <n>
 
−
 
−
|-
 
−
 
−
|rowspan="2" |dgp<n>.tamper
 
−
|1
 
−
|R
 
−
|DGP <n> is tampered
 
−
|-
 
−
|0
 
−
|R
 
−
|DGP <n> is not tampered
 
−
|}
 
−
 
−
<span id="note">
 
−
;Note: The value of a zone status (datapoints z<n>.state1 and z<n>.state2) depends on the configuration of the zone typology.
 
−
</span>
 
  
 
== User Interface ==
 
== User Interface ==

Revision as of 17:01, 10 January 2014

Aritech Interlogix FP2000 is a multi-area fire panel. The integration with HSYCO can be accomplished via direct control through the RS232 port on the panel. The FP2000 I/O Server in HSYCO supports the integration of more than one unit within the same HSYCO interface.

Communication

Employ an RS-232 cable to connect the panel directly to HSYCO.

RS-232 parameters:

Baud rate same as panel settings (default 9600)
Data bits 8
Stop bit 1
Parity none
Flow control RTS/CTS


HSYCO Configuration

Options

ID Default Values Description
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
accesscode 0 0 do not request for authentication (the I/O Server will only be usable as panel emulator)
1 - 9999 use the specified value as access code for requesting authentication
keypaddisable false true disable the emulator keypad buttons
false the emulator keypad buttons are enabled
controldisable false true disable the emulator control buttons
false the emulator control buttons are enabled
displayhlcolor 339933 000000 - FFFFFF use the specified hexadecimal value as the highlight color for the display of the emulator

Datapoints

User Interface

Ats Object

The user interface for the Aritech ATS multi-area intrusion detection system:

Ats UI Object 1.png Ats UI Object 2.png Ats UI Object 3.png

The Ats object is listed in the Project Editor’s new object list only when at least one Aritech ATS I/O Server is defined.


Parameters

  • server id: the server ID
  • position: the object's position. Use the pixels or rows and columns coordinates format

Syntax

(ats <server id>; <position>)

E.g. 

(ats serverid; x10y20)

UISET Actions

ID Value R/W Description
connection online R connection established
offline R HSYCO can't connect to the panel
emulation 1 R emulation is active
W activate emulation
0 R emulation is disabled
W disable emulation
led.general.fire.1

led.general.fire.2 led.general.processor led.general.supply.fault led.general.disabled led.general.fault led.general.supply led.general.system.fault led.brigade.delay.off led.brigade.delay.on led.brigade.stop led.brigade.fault led.brigade.signal led.sounder.delay.on led.sounder.silence led.sounder.fault led.sounder.sound led.sounder.delay.off led.control.test led.control.disabled led.control.silence.buzzer led.all led.panel

on R the corresponding LED is on
off R the corresponding LED is off
blink W the corresponding LED is on, blinking
status.alarm.count <num> R count of fires
status.fault.count <num> R count of faults
status.condition.count <num> R count of conditions
status.event.count <num> R count of all the events other than fire, fault or condition
clock <val> R <date_time> R the panel’s clock is set to <date_time>. The value has the format "yyyy-mm-dd hh:mm:ss" (e.g. "2012-12-30 16:59:23")
W set the data e and time of the panel to <date_time>. The value has the format "yyyy-mm-dd hh:mm:ss" (e.g. "2012-12-30 16:59:23")
read R
W request for reading date and time set on the panel
ID Attribute Set to
log value latest security log lines (as many as specified by the 'logsize' option)
log0 value latest line of the security log when a new entry is added, set back to blank after a short period
a<n>.name value name assigned to area <n>
z<n>.name value name assigned to zone <n>
connection.label visible true when datapoint connection = offline
false when datapoint connection = online
<datapoint_id>.label.1 visible true when datapoint with ID <datapoint_id> has value '1'
false when datapoint with ID <datapoint_id> has value '0'
<datapoint_id>.label.0 visible true when datapoint with ID <datapoint_id> has value '0'
false when datapoint with ID <datapoint_id> has value '1'


USER Commands

Name Param Action
armed 1 arm all active areas
0 disarm all active areas
alarm reset reset system alarms
a<n>.armed 1 arm area <n>
0 disarm area <n>
force force arm area <n>
z<n>.isolated 1 isolate zone <n>
0 de-isolate zone <n>
z<n>.alarm reset reset alarms on zone <n>
o<n>.active 1 activate output <n>
0 deactivate output <n>
Retrieved from "http://wiki.hsyco.com/3.4.0/index.php?title=Fp2000&oldid=991"