Boschfpa
The BOSCH FPA-5000 is a modular fire panel system.
Contents
Communication
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:
After the upload configuration process the FPA-5000 is ready to be connected via RS232.
RS232 Communication Module overview:
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 numbers 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.
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 |
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: sensor 4.1 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: sensore 4.1 2014.07.10 17:28:11.603 - fpa - normal: 2451.0
Other information related to the Bentel KYO driver are saved in the daily message.log files.
