Skip to main content

Bentel

The Bentel KYO320 is an advanced, multi-area security system integrated HSYCO.

The KYO320 driver in HSYCO supports the integration of more than one KYO320 unit on the same HSYCO SERVER.

The integration with HSYCO can be accomplished through the standard RS-232 port on the KYO320’s motherboard.

note

This I/O server requires the KYO320 firmware version 2.0x or later (protocol revision 1.06).

Communication

Employ a DE-9 (often called DB-9) female-female RS-232 crossed cable to connect the RS-232 KYO port to the serial port on HSYCO SERVER. The cable must follow this pinout diagram:

2 ↔ 3
3 ↔ 2
5 ↔ 5

RS-232 parameters:

Baud ratesame as defined on the KYO320 (usually 9600, 38400 or 57600)
Data bits8
Stop bit1
Parityeven
Flow controlnone

HSYCO Configuration

Add a BENTEL 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 object, UISET actions and USER commands
falsedisable UI support
languagesystem languageenlanguage of log and display messages. Supported values are it and en
it
zoneactivitylogfalsetruelogs the open/close status of zones in the log page and security.log files
falsedisable zone status log
userlogsfalsetruegenerates logs that can be viewed with the userlist object, and can be selected to generate user events
falselogs for userlist objects disabled. Normal text logs are generated even when this option is false
code<code>the user code to be used when sending IO commands to the KYO, if code is not explicitly set in the command
logsize50n ≥ 0the number of log lines to display in the UI object
polltime1000n ≥ 0the data polling interval, in milliseconds. Shorter time improve the response of the system, but increase the load on the CPU of both HSYCO and the KYO system

bentel.ini

The bentel.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 and partitions names. If defined, these names will be used instead of the original numbers in the log files and the bentel GUI object.

The bentel.ini is automatically detected at start-up. Changes to this file become effective when the I/O Server is restarted.

For each zone or partition, enter a line formatted as:

<io_server_id>.zone.<n> = <name>
<io_server_id>.area.<n> = <name>

For instance:

kyo.zone.1 = kitchen
kyo.zone.2 = garage
kyo.area.1 = basement
kyo.area.2 = second floor

Datapoints

IDValueR/WDescription
connectiononlineRconnection established
offlineRHSYCO can't connect to the panel
system.fault1Rgeneral system fault
0Rreset
system.batteryfault1Rgeneral battery fault
0Rreset
system.lowbattery1Rlow battery
0Rreset
system.nobattery1Rlow battery
0Rreset
system.nopower1Rgeneral no AC power fault
0Rreset
system.tamper1Rgeneral tamper condition (central unit, zones, modules)
0Rreset
system.radiofault1Rgeneral radio modules fault
0Rreset
system.radiolowbattery1Rradio modules low battery
0Rreset
system.duress1Rduress status
0Rreset
system.maintenance1Rmaintenance mode
0Rreset
zone.<n>.disabled1Rzone <n> disabled
0Rzone <n> enabled
zone.<n>.alarm1Rzone <n> alarm
0Rreset
zone.<n>.alarmmemory1Rzone <n> alarm memory
0Rreset
zone.<n>.tamper1Rzone <n> tamper alarm
0Rreset
zone.<n>.tampermemory1Rzone <n> tamper memory alarm
0Rreset
zone.<n>enableWenable zone <n> using default code
disableWdisable zone <n> using default code
enable.<c>Wenable zone <n> using code <c>
disable.<c>Wdisable zone <n> using code <c>
partition.<n>.armed1Rarea <n> is armed (any mode)
0Rreset
partition.<n>.disarmed1Rarea <n> is not armed
0Rreset
partition.<n>.away1Rarea <n> away mode
0Rreset
partition.<n>.stay1Rarea <n> stay mode
0Rreset
partition.<n>.staynodelay1Rarea <n> stay no delay mode
0Rreset
partition.<n>.alarm1Rarea <n> alarm memory
0Rreset
partition.<n>awayWarm area <n> using default code
disarmWdisarm area <n> using default code
stayWstay arm area <n> using default code
staynodelayWinstant stay arm area <n> using default code
away.<c>Warm area <n> using code <c>
disarm.<c>Wdisarm area <n> using code <c>
stay.<c>Wstay arm area <n> using code <c>
staynodelay.<c>Winstant stay arm area <n> using code <c>
out.<n>offWturn off output <n> using default code
onWturn on output <n> using default code
off.<c>Wturn off output <n> using code <c>
on.<c>Wturn on output <n> using code <c>

User Interface

UISET Actions

IDAttribute
areasvaluethe status of all partitions
log0valuethe latest entry of the security log for a short period
logsvaluethe latest entries of the security log (as many as specified in hsyco.ini)
zonesvaluethe status of all known zones (zones are added to this list as soon as an event is detected on a zone)
connection.label.onlinevisibletrue when the panel is connected to HSYCO, false otherwise
connection.label.offlinevisibletrue when the panel is not connected to HSYCO, false otherwise
partition.<n>.label.alarmvisibletrue when partition <n> alarm is active, false otherwise
partition.<n>.label.armedvisibletrue when partition <n> is armed, false otherwise
partition.<n>.label.disarmedvisibletrue when partition <n> is disarmed, false otherwise
partition.<n>.label.awayvisibletrue when partition <n> is armed in away mode, false otherwise
partition.<n>.label.stayvisibletrue when partition <n> is armed in stay mode, false otherwise
partition.<n>.label.staynodelayvisibletrue when partition <n> is armed in stay no delay mode, false otherwise
zone.<n>.label.alarmvisibletrue when zone <n> alarm is active
zone.<n>.label.tampervisibletrue when zone <n> tamper alarm is active
zone.<n>.label.disabledvisibletrue when zone <n> is disabled

Bentel UI Object

The user interface for the Bentel KYO320 multi-area intrusion detection system:

Bentel UI Object 1 Bentel UI Object 2 Bentel UI Object 3 Bentel UI Object 4

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

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.30 20:09:21.760 - SECOND FLOOR - ARMED
2014.07.30 20:09:21.763 - SECOND FLOOR - AWAY
2014.07.30 20:10:02.364 - [2] GARAGE - OPEN
2014.07.30 20:10:04.779 - [2] GARAGE - OK
2014.07.30 20:10:06.167 - BASEMENT - ALARM
2014.07.30 20:10:48.477 - BASEMENT - DISARMED
2014.07.30 20:10:48.481 - SECOND FLOOR - DISARMED
2014.07.30 20:39:31.326 - ZONE 281 - OPEN
2014.07.30 20:39:36.708 - ZONE 281 - OK
2014.07.30 20:40:41.571 - AC POWER - FAULT
2014.07.30 20:49:58.945 - ZONE 281 - OPEN
2014.07.30 20:50:04.181 - ZONE 281 - OK
2014.07.30 20:50:11.559 - AC POWER - OK

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

Release Notes

3.8.0

  • added alarm memory and tamper memory datapoints

3.4.0

  • partition buttons (P1-P12) are now automatically highlighted on armed areas
  • fixes to the (bentel) object

3.3.0

  • Bentel KYO driver converted to I/O Server
  • Java API write command methods are now obsolete and deprecated, replaced by IO write commands
  • new (bentel) object
  • new option userlogs. Used to create (userlist) clickable logs

2.0.0

  • full integration within HSYCO 2.9.0

1.1.0

  • change to the status polling thread to improve recovery time after transient communication problems

Bentel, KYO and KYO320 are registered trademarks of BENTEL SECURITY SRL.