Skip to main content

Boschfpa

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

note

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:

Bosch FPA configuration 1

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

RS-232 Communication Module overview:

Bosch FPA configuration 1

RS-232 parameters:

Baud rate9600
Data bits7
Stop bit1
Parityeven
Flow controlnone

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

IDDefaultValuesDescription
guitruetrueenable support for the UI (event log object)
falsedisable UI support
languagesystem languageenlanguage of log and display messages. Supported values are English, Italian and German
it
de
logsize100n ≥ 0the 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

IDValueR/WDescription
connectiononlineRconnection established
offlineRHSYCO can't connect to the panel
buzzeroffRbuzzer silenced (forced event)
Wsilence the buzzer
line.<logical address>.<subaddress>bypassRbypass
blockedRblocked
warningthresholdRthreshold warning
tamperRtamper alarm
alarminvestigationRalarm verification
invalidRinvalid
fireRfire
fireprealarmRfire pre-alarm
firedaymodeRfire day mode
normalRnormal
faultRfault
troublelightRminor fault
supervisorymonitorwaterRsupervisory, monitor, water
offRoff
onRon
paperoutRout of paper
powerfailRpower fail
activatedRactivated
pollutionRheavy contamination
pollutionlightRminor contamination
walktestfireRwalk test fire
walktestnormalRwalk test normal
walktesttroubleRwalk test fault
walktestoffRwalk test off
walktestonRwalk test on
walktestactivationRwalk 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
1Rone or more lines in this state
0Rno lines in this state

User Interface

UISET Actions

IDAttribute
logsvaluethe 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.