Fp2000

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. The driver has been also tested on these panels: FP1216, FP2864.

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

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

Communication

• Comm ID: select the comm port connected to the panel.

High Availability

• Shutdown when inactive: defaults to true.

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

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	<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 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	W	request for reading date and time set on the panel
l<n>.s<m>.name	<name>	R	reports the name of sensor <m> on loop <n>
l<n>.s<m>.alarm.fire	1	R	fire alarm active for sensor <m> on loop <n>
	0	R	no fire alarm active for sensor <m> on loop <n>
l<n>.s<m>.alarm.communication	1	R	fault alarm active for sensor <m> on loop <n>
	0	R	no fault alarm active for sensor <m> on loop <n>
l<n>.s<m>.alarm.disabled	1	R	disabled alarm active for sensor <m> on loop <n>
	0	R	no disabled alarm active for sensor <m> on loop <n>
l<n>.s<m>.alarm.type	1	R	wrong type alarm active for sensor <m> on loop <n>
	0	R	no wrong type alarm active for sensor <m> on loop <n>
l<n>.s<m>.alarm.address	1	R	double address alarm active for sensor <m> on loop <n>
	0	R	no double address alarm active for sensor <m> on loop <n>
l<n>.s<m>.alarm.condition	1	R	pre condition alarm active for sensor <m> on loop <n>
	0	R	no pre condition alarm active for sensor <m> on loop <n>
l<n>.s<m>.alarm.maintenance	1	R	maintenance alarm active for sensor <m> on loop <n>
	0	R	no maintenance alarm active for sensor <m> on loop <n>
l<n>.s<m>.alarm.notype	1	R	no type alarm active for sensor <m> on loop <n>
	0	R	type alarm active for sensor <m> on loop <n>
l<n>.s<m>.alarm.enabled	1	R	enabled alarm active for sensor <m> on loop <n>
	0	R	no enabled alarm active for sensor <m> on loop <n>
l<n>.s<m>.alarm.twoset	1	R	two set alarm active for sensor <m> on loop <n>
	0	R	no two set alarm active for sensor <m> on loop <n>
l<n>.s<m>.alarm.segment	1	R	7 segment alarm active for sensor <m> on loop <n>
	0	R	no 7 segment alarm active for sensor <m> on loop <n>
l<n>.s<m>.alarm.led	1	R	LED alarm active for sensor <m> on loop <n>
	0	R	no LED alarm active for sensor <m> on loop <n>
l<n>.s<m>.alarm.segment.cont	1	R	7 segment continuous alarm active for sensor <m> on loop <n>
	0	R	no 7 segment continuous alarm active for sensor <m> on loop <n>
l<n>.s<m>.alarm.flag	1	R	flag alarm active for sensor <m> on loop <n>
	0	R	no flag alarm active for sensor <m> on loop <n>
l<n>.s<m>.alarm.pending	1	R	alarm pending for sensor <m> on loop <n>
	0	R	no alarm pending for sensor <m> on loop <n>
l<n>.s<m>.alarm	1	R	one of the above alarms is active for sensor <m> on loop <n>
	0	R	none of the above alarms is active for sensor <m> on loop <n>
l<n>.s<m>.alarm.count	<num>	R	reports the number of alarm states been active for sensor <m> on loop <n>
z<n>.name	<name>	R	reports the name of zone <n>
z<n>.alarm.fire	1	R	MCP fire alarm active on zone <n>
	0	R	no MCP fire alarm active on zone <n>
z<n>.alarm.fault	1	R	fault alarm active on zone <n>
	0	R	no fault alarm active on zone <n>
z<n>.alarm.coincidence	1	R	coincidence alarm active on zone <n>
	0	R	no coincidence fire alarm active on zone <n>
z<n>.alarm.isolated	1	R	isolated alarm active on zone <n>
	0	R	no isolated alarm active on zone <n>
z<n>.alarm.test	1	R	test alarm active on zone <n>
	0	R	no test alarm active on zone <n>
z<n>.alarm.condition	1	R	condition alarm active on zone <n>
	0	R	no condition alarm active on zone <n>
z<n>.alarm.enabled	1	R	enabled alarm active on zone <n>
	0	R	no enabled alarm active on zone <n>
z<n>.alarm.autofire	1	R	auto fire alarm active on zone <n>
	0	R	no auto fire alarm active on zone <n>
z<n>.alarm.action	1	R	action zone alarm active on zone <n>
	0	R	no action zone alarm active on zone <n>
z<n>.alarm.warning	1	R	pre warning alarm active on zone <n>
	0	R	no pre warning alarm active on zone <n>
z<n>.zone.alarm	1	R	one of the above alarms is active on zone <n>
	0	R	none of the above alarms is active on zone <n>
z<n>.alarm.count	<num>	R	reports the number of alarm states active on sensors of zone <n>
z<n>.fault.count	<num>	R	reports the number of faults states active on sensors of zone <n>
z<n>.condition.count	<num>	R	reports the number of conditions active on sensors of zone <n>
z<n>.coincidence.count	<num>	R	reports the number of coincidence alarms active on sensors of zone <n>
z<n>.isolate.count	<num>	R	reports the number of isolations in zone <n>
a<n>.name	<name>	R	reports the name of area <n>
a<n>.alarm.fire	1	R	MCP fire alarm active on area <n>
	0	R	no MCP fire alarm active on area <n>
a<n>.alarm.fault	1	R	fault alarm active on area <n>
	0	R	no fault alarm active on area <n>
a<n>.alarm.coincidence	1	R	coincidence alarm active on area <n>
	0	R	no coincidence alarm active on area <n>
a<n>.alarm.isolated	1	R	isolated alarm active on area <n>
	0	R	no isolated alarm active on area <n>
a<n>.alarm.condition	1	R	condition alarm active on area <n>
	0	R	no condition alarm active on area <n>
a<n>.alarm.enabled	1	R	enabled alarm active on area <n>
	0	R	no enabled alarm active on area <n>
a<n>.alarm.action	1	R	action alarm active on area <n>
	0	R	no action alarm active on area <n>
a<n>.area.alarm	1	R	one of the above alarms is active on area <n>
	0	R	none of the above alarms is active on area <n>
a<n>.alarm.count	<num>	R	reports the number of alarm states active on sensors of area <n>
a<n>.fault.count	<num>	R	reports the number of faults states active on sensors of area <n>
a<n>.condition.count	<num>	R	reports the number of conditions active on sensors of area <n>
a<n>.coincidence.count	<num>	R	reports the number of coincidence alarms active on sensors of area <n>
a<n>.isolate.count	<num>	R	reports the number of isolations in area <n>
o<n>.name	<name>	R	reports the number of output <n>
o<n>.status[Note 1]	1	R	output <n> is active
	0	R	output <n> is inactive
	read	W	request for reading the state of output <n>
i<n>.name	<name>	R	reports the number of input <n>
i<n>.status	1	R	input <n> is active
	0	R	input <n> is inactive
	read	W	request for reading the state of input <n>
event.action.text event.fire.text event.fault.text event.condition.text	<text>	R	reports the text of the most recently logged event accordingly to its category
key[Note 2]	<key_value>	W	send the specified emulation key command to the panel (see following table for the list of key values)

Note 1 

the status of outputs and inputs is based on the reported events on the event log, thus the panel must be set so that outputs and inputs state variations are logged. Otherwise the reading of their status must be requested via the “o<n>.status = read” and “i<n>.status = read” commands.

Note 2

The following table shows the association between key values and relative function:

<key_value>	Function
1	Scroll
2	Display Alarm
4	Print Screen
5	Alpha Numeric
6	Right Arrow
8	Left Arrow
9	Silence Buzzer
10	Down Arrow
11	Reset
12	Disable
13	Enter
14	Test
15	Sound Sounder
16	Sounder Delay
17	Sounder Disable
18	Silence Sounder
19	Fire Brigade Disable
20	Fire Brigade Delay
22	Fire Brigade Stop
26	Up Arrow
27	Exit
29	Panel
30	All
31	Fire Brigade Signal
48	Key “0”
49	Key “1”
50	Key “2”
51	Key “3”
52	Key “4”
53	Key “5”
54	Key “6”
55	Key “7”
56	Key “8”
57	Key “9”
211	Fire Protection on
212	Fire Protection Silenced
213	Fire Protection Silenced
214	Fire Protection Enabled
215	Fire Protection Disabled
216	Fire Protection Disable
217	Fire Protection Delay off
218	Fire Protection Delay on
219	Fire Protection Delay
220	Fire Protection Delay
221	Fire Protection Delay
222	Fault Routing Test
223	Fault Routing Enabled
224	Fault Routing Disabled
225	Fault Routing Disable
226	Fault Routing Delay off
227	Fault Routing Delay on
228	Fault Routing Delay
229	Fire Brigade Test
230	Fire Brigade Enabled
231	Fire Brigade Disabled
232	Fire Brigade Delay off
233	Fire Brigade Delay on
234	Sounder Test
235	Sounder Enable
236	Sounder Disable
237	Sounder Delay off
238	Sounder Delay on
239	External Reset (from Repeater)

User Interface

FP2000 Object

The user interface for the Aritech Interlogix FP2000 multi-area fire panel:

The Fp2000 object is listed in the Project Editor’s new object list only when at least one Aritech Interlogix FP2000 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

(fp2000 <server id>; <position>)

E.g.

(fp2000 serverid; x10y20)

UISET Actions

ID	Attribute	Set to
log<n>	value	latest security log lines (as many as specified by the 'logsize' option, with <n> = 1 ... 20)
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>
l<n>.s<m>.name	value	name assigned to sensor <m> on loop <n>
i<n>.name	value	name assigned to input <n>
o<n>.name	value	name assigned to output <n>
display	value	text displayed by the panel in real-time
connection.label	visible	true	when datapoint connection = online
		false	when datapoint connection = offline
l<n>.sM.alarm.label.1	visible	true	when an alarm is active for sensor <m> on loop <n>
		false	when an alarm is not active for sensor <m> on loop <n>
l<n>.sM.alarm.label.0	visible	true	when no alarm is active for sensor <m> on loop <n>
		false	when an alarm is active for sensor <m> on loop <n>
o<n>.status.label.1	visible	true	when output <n> is active
		false	when output <n> is not active
o<n>.status.label.0	visible	true	when output <n> is not active
		false	when output <n> is active
i<n>.status.label.1	visible	true	when input <n> is active
		false	when input <n> is not active
i<n>.status.label.0	visible	true	when input <n> is not active
		false	when input <n> is active
led.<name>.label.off	visible	true	when the corresponding LED is off
		false	when the corresponding LED is on
led.<name>.label.on[Note 3]	visible	true	when the corresponding LED is on
		false	when the corresponding LED is off

Note 3 

Replace <name> with one of the following strings:

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

USER Commands

The FP2000 driver supports system commands to be inserted within the Web interface that replicates the functionalities of the buttons on the panel and more. Use any ordinary user button, setting the name and param fields according to the write function of the Datapoints table.

For instance, setting the name of a user button to “fp.key” and its param field to “11”, will result in having the reset button of the panel. Naming it “o1.status” and setting “read” as param will result in a button for forcing the reading of the status of output 1.

Log Files

A permanent detailed record of all the FP2000 log messages is saved in a file called security.log in the logs/YYYY directory for the current year. This file is never overwritten or deleted by HSYCO.

Other information related to the FP2000 driver are saved in the daily message.log files.

Release Notes

3.1.0

• initial version release

---

Aritech Interlogix and FP2000 are registered trademarks of UTC Fire & Security.