Difference between revisions of "Boschfpa"

From HSYCO
Jump to navigation Jump to search
 
(12 intermediate revisions by 3 users not shown)
Line 9: Line 9:
 
Be sure to use BOSCH sofware management tool RPS version 4_0_11 or later for the FPA configuration.
 
Be sure to use BOSCH sofware management tool RPS version 4_0_11 or later for the FPA configuration.
  
Configure the RS232 Communication Module module as follows:
+
Configure the RS-232 Communication Module module as follows:
  
 
[[File:fpa1.png]]
 
[[File:fpa1.png]]
  
After the upload configuration process the FPA-5000 is ready to be connected via RS232.
+
After the upload configuration process the FPA-5000 is ready to be connected via RS-232.
  
RS232 Communication Module overview:
+
RS-232 Communication Module overview:
  
 
[[File:fpa2.png|500px]]
 
[[File:fpa2.png|500px]]
Line 84: Line 84:
 
=== boschfpa.ini ===
 
=== boschfpa.ini ===
  
The boschfpa.ini file is an optional configuration file located in the main directory (same directory as hsyco.ini or hsyco.jar) and used to define zones (lines) names. If defined, these names will be used instead of the original numbers in the log files and GUI event log object.  
+
The boschfpa.ini file is an optional configuration file located in the main directory (same directory as hsyco.ini or hsyco.jar) and used to define zones (lines) names. If defined, these names will be used instead of the original <logical address>.<subaddress> format in the log files and GUI event log object.  
  
 
Changes to the boschfpa.ini file are automatically detected and don't require a restart to become effective.
 
Changes to the boschfpa.ini file are automatically detected and don't require a restart to become effective.
Line 102: Line 102:
 
fpa.line.4.1 = GENERATORS ROOM
 
fpa.line.4.1 = GENERATORS ROOM
 
</pre>
 
</pre>
 
  
 
== Datapoints ==
 
== Datapoints ==
Line 124: Line 123:
  
 
|rowspan="2" |buzzer
 
|rowspan="2" |buzzer
|off
+
|rowspan="2" |off
 
|R
 
|R
 
|buzzer silenced (forced event)
 
|buzzer silenced (forced event)
 
|-
 
|-
|off
+
|W
|w
 
 
|silence the buzzer
 
|silence the buzzer
 
|-
 
|-
  
|rowspan="2" |system.batteryfault
+
|rowspan="26" |line.<logical address>.<subaddress>
|1
+
|bypass
 
|R
 
|R
|general battery fault
+
|bypass
 
|-
 
|-
|0
+
|blocked
 
|R
 
|R
|reset
+
|blocked
 
|-
 
|-
 
+
|warningthreshold
|rowspan="2" |system.lowbattery
 
|1
 
 
|R
 
|R
|low battery
+
|threshold warning
 
|-
 
|-
|0
+
|tamper
 
|R
 
|R
|reset
+
|tamper alarm
 
|-
 
|-
 
+
|alarminvestigation
|rowspan="2" |system.nobattery
 
|1
 
 
|R
 
|R
|low battery
+
|alarm verification
 
|-
 
|-
|0
+
|invalid
 
|R
 
|R
|reset
+
|invalid
 
|-
 
|-
 
+
|fire
|rowspan="2" |system.nopower
 
|1
 
 
|R
 
|R
|general no AC power fault
+
|fire
 
|-
 
|-
|0
+
|fireprealarm
 
|R
 
|R
|reset
+
|fire pre-alarm
 
|-
 
|-
 
+
|firedaymode
|rowspan="2" |system.tamper
 
|1
 
 
|R
 
|R
|general tamper condition (central unit, zones, modules)
+
|fire day mode
 
|-
 
|-
|0
+
|normal
 
|R
 
|R
|reset
+
|normal
 
|-
 
|-
 
+
|fault
|rowspan="2" |system.radiofault
 
|1
 
 
|R
 
|R
|general radio modules fault
+
|fault
 
|-
 
|-
|0
+
|troublelight
 
|R
 
|R
|reset
+
|minor fault
 
|-
 
|-
 
+
|supervisorymonitorwater
|rowspan="2" |system.radiolowbattery
 
|1
 
 
|R
 
|R
|radio modules low battery
+
|supervisory, monitor, water
 
|-
 
|-
|0
+
|off
 
|R
 
|R
|reset
+
|off
 
|-
 
|-
 
+
|on
|rowspan="2" |system.duress
 
|1
 
 
|R
 
|R
|duress status
+
|on
 
|-
 
|-
|0
+
|paperout
 
|R
 
|R
|reset
+
|out of paper
 
|-
 
|-
 
+
|powerfail
|rowspan="2" |system.maintenance
 
|1
 
 
|R
 
|R
|maintenance mode
+
|power fail
 
|-
 
|-
|0
+
|activated
 
|R
 
|R
|reset
+
|activated
 
|-
 
|-
 
+
|pollution
|rowspan="2" |zone.<n>.disabled
 
|1
 
 
|R
 
|R
|zone <n> disabled
+
|heavy contamination
 
|-
 
|-
|0
+
|pollutionlight
 
|R
 
|R
|zone <n> enabled
+
|minor contamination
 
|-
 
|-
 
+
|walktestfire
|rowspan="2" |zone.<n>.alarm
 
|1
 
 
|R
 
|R
|zone <n> alarm
+
|walk test fire
 
|-
 
|-
|0
+
|walktestnormal
 
|R
 
|R
|reset
+
|walk test normal
 
|-
 
|-
 
+
|walktesttrouble
|rowspan="2" |zone.<n>.tamper
 
|1
 
 
|R
 
|R
|zone <n> tamper alarm
+
|walk test fault
 
|-
 
|-
|0
+
|walktestoff
 
|R
 
|R
|reset
+
|walk test off
 
|-
 
|-
 
+
|walkteston
|rowspan="4" |zone.<n>
 
|enable
 
|W
 
|enable zone <n> using default code
 
|-
 
|disable
 
|W
 
|disable zone <n> using default code
 
|-
 
|enable.<c>
 
|W
 
|enable zone <n> using code <c>
 
|-
 
|disable.<c>
 
|W
 
|disable zone <n> using code <c>
 
|-
 
 
 
|rowspan="2" |partition.<n>.armed
 
|1
 
 
|R
 
|R
|area <n> is armed (any mode)
+
|walk test on
 
|-
 
|-
|0
+
|walktestactivation
 
|R
 
|R
|reset
+
|walk test activation
 
|-
 
|-
  
|rowspan="2" |partition.<n>.disarmed
+
|rowspan="2" |
 +
status.bypass<BR>
 +
status.blocked<BR>
 +
status.warningthreshold<BR>
 +
status.tamper<BR>
 +
status.alarminvestigation<BR>
 +
status.invalid<BR>
 +
status.fire<BR>
 +
status.fireprealarm<BR>
 +
status.firedaymode<BR>
 +
status.normal<BR>
 +
status.trouble<BR>
 +
status.troublelight<BR>
 +
status.supervisorymonitorwater<BR>
 +
status.off<BR>
 +
status.on<BR>
 +
status.paperout<BR>
 +
status.powerfail<BR>
 +
status.activated<BR>
 +
status.pollution<BR>
 +
status.pollutionlight<BR>
 +
status.walktestfire<BR>
 +
status.walktestnormal<BR>
 +
status.walktesttrouble<BR>
 +
status.walktestoff<BR>
 +
status.walkteston<BR>
 +
status.walktestactivation
 
|1
 
|1
 
|R
 
|R
|area <n> is not armed
+
|one or more lines in this state
 
|-
 
|-
 
|0
 
|0
 
|R
 
|R
|reset
+
|no lines in this state
 
|-
 
|-
 +
|}
  
|rowspan="2" |partition.<n>.away
+
== User Interface ==
|1
+
 
|R
+
=== UISET Actions ===
|area <n> away mode
+
 
 +
{| class="wikitable"
 +
!ID
 +
!Attribute
 +
!colspan="2"|Set to
 
|-
 
|-
|0
+
 
|R
+
|logs
|reset
+
|value
 +
|the latest entries of the security log (as many as specified in hsyco.ini)
 
|-
 
|-
 +
|}
  
|rowspan="2" |partition.<n>.stay
 
|1
 
|R
 
|area <n> stay mode
 
|-
 
|0
 
|R
 
|reset
 
|-
 
  
|rowspan="2" |partition.<n>.staynodelay
+
== Log Files ==
|1
+
 
|R
+
A permanent record of all the events shown in the log page is saved in a file called security.log in the logs/YYYY directory for the current year.
|area <n> stay no delay mode
+
 
|-
+
This file is never overwritten or deleted by HSYCO.
|0
+
<pre>
|R
+
2014.07.10 17:27:24.873 - fpa - fault: 2451.0
|reset
+
2014.07.10 17:27:46.813 - fpa - fire: data room sensor
|-
+
2014.07.10 17:27:48.851 - fpa - activated: 1603.1
 +
2014.07.10 17:27:54.002 - fpa - activated: 1602.1
 +
2014.07.10 17:27:54.924 - fpa - activated: 1601.1
 +
2014.07.10 17:28:10.609 - fpa - normal: data room sensor
 +
2014.07.10 17:28:11.603 - fpa - normal: 2451.0
 +
</pre>
 +
 
 +
Other information related to the BOSCH FPA driver may be saved in the daily message.log files.
 +
 
  
|rowspan="2" |partition.<n>.alarm
+
== Release Notes ==
|1
+
=== 3.4.0 ===
|R
+
*initial release
|area <n> alarm memory
 
|-
 
|0
 
|R
 
|reset
 
|-
 
  
|rowspan="8" |partition.<n>
+
----
|away
 
|W
 
|arm area <n> using default code
 
|-
 
|disarm
 
|W
 
|disarm area <n> using default code
 
|-
 
|stay
 
|W
 
|stay arm area <n> using default code
 
|-
 
|staynodelay
 
|W
 
|instant stay arm area <n> using default code
 
|-
 
|away.<c>
 
|W
 
|arm area <n> using code <c>
 
|-
 
|disarm.<c>
 
|W
 
|disarm area <n> using code <c>
 
|-
 
|stay.<c>
 
|W
 
|stay arm area <n> using code <c>
 
|-
 
|staynodelay.<c>
 
|W
 
|instant stay arm area <n> using code <c>
 
|-
 
  
|rowspan="4" |out.<n>
 
|off
 
|W
 
|turn off output <n> using default code
 
|-
 
|on
 
|W
 
|turn on output <n> using default code
 
|-
 
|off.<c>
 
|W
 
|turn off output <n> using code <c>
 
|-
 
|on.<c>
 
|W
 
|turn on output <n> using code <c>
 
|-
 
  
|}
+
''FPA-5000 is a registered trademark of Bosch Security Systems.''

Latest revision as of 11:33, 24 October 2014

The BOSCH FPA-5000 is a modular fire panel system.

This I/O server requires the FPA firmware version 2.12.7 or later.

Communication

Be sure to use BOSCH sofware management tool RPS version 4_0_11 or later for the FPA configuration.

Configure the RS-232 Communication Module module as follows:

Fpa1.png

After the upload configuration process the FPA-5000 is ready to be connected via RS-232.

RS-232 Communication Module overview:

Fpa2.png


RS-232 parameters:

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

HSYCO Configuration

Add a BOSCHFPA 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 (event log object)
false disable UI support
language system language en language of log and display messages. Supported values are English, Italian and German
it
de
logsize 100 n ≥ 0 the number of log lines to display in the UI object

boschfpa.ini

The boschfpa.ini file is an optional configuration file located in the main directory (same directory as hsyco.ini or hsyco.jar) and used to define zones (lines) names. If defined, these names will be used instead of the original <logical address>.<subaddress> format in the log files and GUI event log object.

Changes to the boschfpa.ini file are automatically detected and don't require a restart to become effective.

Note This file is case sensitive.

For each zone (line), enter a line formatted as:

<io_server_id>.line.<logical address>.<subaddress> = <name>

For instance:

fpa.line.3.1 = DATA ROOM SENSOR
fpa.line.4.1 = GENERATORS ROOM

Datapoints

ID Value R/W Description
connection online R connection established
offline R HSYCO can't connect to the panel
buzzer off R buzzer silenced (forced event)
W silence the buzzer
line.<logical address>.<subaddress> bypass R bypass
blocked R blocked
warningthreshold R threshold warning
tamper R tamper alarm
alarminvestigation R alarm verification
invalid R invalid
fire R fire
fireprealarm R fire pre-alarm
firedaymode R fire day mode
normal R normal
fault R fault
troublelight R minor fault
supervisorymonitorwater R supervisory, monitor, water
off R off
on R on
paperout R out of paper
powerfail R power fail
activated R activated
pollution R heavy contamination
pollutionlight R minor contamination
walktestfire R walk test fire
walktestnormal R walk test normal
walktesttrouble R walk test fault
walktestoff R walk test off
walkteston R walk test on
walktestactivation R walk test activation

status.bypass
status.blocked
status.warningthreshold
status.tamper
status.alarminvestigation
status.invalid
status.fire
status.fireprealarm
status.firedaymode
status.normal
status.trouble
status.troublelight
status.supervisorymonitorwater
status.off
status.on
status.paperout
status.powerfail
status.activated
status.pollution
status.pollutionlight
status.walktestfire
status.walktestnormal
status.walktesttrouble
status.walktestoff
status.walkteston
status.walktestactivation

1 R one or more lines in this state
0 R no lines in this state

User Interface

UISET Actions

ID Attribute Set to
logs value the latest entries of the security log (as many as specified in hsyco.ini)


Log Files

A permanent record of all the events shown in the log page 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.

2014.07.10 17:27:24.873 - fpa - fault: 2451.0
2014.07.10 17:27:46.813 - fpa - fire: data room sensor
2014.07.10 17:27:48.851 - fpa - activated: 1603.1
2014.07.10 17:27:54.002 - fpa - activated: 1602.1
2014.07.10 17:27:54.924 - fpa - activated: 1601.1
2014.07.10 17:28:10.609 - fpa - normal: data room sensor
2014.07.10 17:28:11.603 - fpa - normal: 2451.0

Other information related to the BOSCH FPA driver may be saved in the daily message.log files.


Release Notes

3.4.0

  • initial release


FPA-5000 is a registered trademark of Bosch Security Systems.