Difference between revisions of "Lares4"

From HSYCO
Jump to navigation Jump to search
Line 68: Line 68:
 
!Attribute
 
!Attribute
 
!colspan="2"|Set to
 
!colspan="2"|Set to
 +
 
|-
 
|-
 +
 
|log
 
|log
 
|value
 
|value
 
|colspan="2"|latest security log lines (as many as specified by the 'logsize' option)
 
|colspan="2"|latest security log lines (as many as specified by the 'logsize' option)
 +
 
|-
 
|-
 +
 
|log0
 
|log0
 
|value
 
|value
−
|colspan="2"|latest line of the security log when a new entry is added, set back to blank after a short period
+
|colspan="2"|latest security log (it will vanish after 5 seconds)
 +
 
 +
|-
 +
 
 +
|rowspan="2" |z<n>.open
 +
|rowspan="2" |visible
 +
|false
 +
|zone n not open
 +
|-
 +
|true
 +
|zone n open
 +
 
 +
|-
 +
 
 +
|rowspan="2" |z<n>.tamper
 +
|rowspan="2" |visible
 +
|false
 +
|zone n not in tampering
 +
|-
 +
|true
 +
|zone n in tampering
 +
 
 +
|-
 +
 
 +
|rowspan="2" |z<n>.trouble
 +
|rowspan="2" |visible
 +
|false
 +
|zone n not in trouble
 +
|-
 +
|true
 +
|zone n in trouble
 +
 
 +
|-
 +
 
 +
|rowspan="2" |z<n>.bypass
 +
|rowspan="2" |visible
 +
|false
 +
|zone n not bypassed
 +
|-
 +
|true
 +
|zone n bypassed
 +
 
 +
|-
 +
 
 +
|rowspan="2" |z<n>.inhibited
 +
|rowspan="2" |visible
 +
|false
 +
|zone n not inhibited
 +
|-
 +
|true
 +
|zone n inhibited
 +
 
 +
|-
 +
 
 +
|rowspan="2" |z<n>.alarm
 +
|rowspan="2" |visible
 +
|false
 +
|zone n not in alarm
 
|-
 
|-
−
|rowspan="2"|connection.online
 
−
|rowspan="2"|visible
 
 
|true
 
|true
−
|when datapoint connection = online
+
|zone n in alarm
 +
 
 
|-
 
|-
 +
 +
|rowspan="2" |z<n>.lowbatt
 +
|rowspan="2" |visible
 
|false
 
|false
−
|when datapoint connection = offline
+
|zone n not low battery
 
|-
 
|-
−
|rowspan="2"|connection.offline
 
−
|rowspan="2"|visible
 
 
|true
 
|true
−
|when datapoint connection = offline
+
|zone n low battery
 +
 
 
|-
 
|-
 +
 +
|rowspan="2" |z<n>.supervision
 +
|rowspan="2" |visible
 
|false
 
|false
−
|when datapoint connection = online
+
|zone n not in supervision
 
|-
 
|-
−
|rowspan="2"|<datapoint_id>.1
 
−
|rowspan="2"|visible
 
 
|true
 
|true
−
|when datapoint with ID <datapoint_id> has value '1'
+
|zone n in supervision
 +
 
 
|-
 
|-
 +
 +
|rowspan="2" |z<n>.alarm.mem
 +
|rowspan="2" |visible
 
|false
 
|false
−
|when datapoint with ID <datapoint_id> has value '0'
+
|zone n not in alarm memory
 
|-
 
|-
−
|rowspan="2"|<datapoint_id>.0
 
−
|rowspan="2"|visible
 
 
|true
 
|true
−
|when datapoint with ID <datapoint_id> has value '0'
+
|zone n in alarm memory
 +
 
 
|-
 
|-
 +
 +
|rowspan="2" |z<n>.activity.fail
 +
|rowspan="2" |visible
 
|false
 
|false
−
|when datapoint with ID <datapoint_id> has value '1'
+
|zone n no activity fail
 +
|-
 +
|true
 +
|zone n activity fail
 +
 
 
|}
 
|}
  

Revision as of 13:40, 28 May 2021

The KSENIA lares 4.0 are multi-area security systems. The I/O Server has been tested on unit with firmware version 1.72.2 and web server version 1.32.7. Actually this driver runs only in HTTP mode (port 80 is set by default).


HSYCO Configuration

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

Communication

  • IP Address: host name or IP address of the panel
  • IP Port: leave it blank

Authentication

  • Password: pin to access the web server

High Availability

  • Shutdown when inactive: defaults to false.

Options

ID Default Values Description
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
pollinterval 1000 n > 1000 the data acquisition interval, in milliseconds
logsize 300 n ≥ 0 the number of log lines to display in the UI object
gui true true enable the UISET "visible" field for all partition zones
false disable the UISET "visible" field for all partition zones


User Interface

UISET Actions

ID Attribute Set to
log value latest security log lines (as many as specified by the 'logsize' option)
log0 value latest security log (it will vanish after 5 seconds)
z<n>.open visible false zone n not open
true zone n open
z<n>.tamper visible false zone n not in tampering
true zone n in tampering
z<n>.trouble visible false zone n not in trouble
true zone n in trouble
z<n>.bypass visible false zone n not bypassed
true zone n bypassed
z<n>.inhibited visible false zone n not inhibited
true zone n inhibited
z<n>.alarm visible false zone n not in alarm
true zone n in alarm
z<n>.lowbatt visible false zone n not low battery
true zone n low battery
z<n>.supervision visible false zone n not in supervision
true zone n in supervision
z<n>.alarm.mem visible false zone n not in alarm memory
true zone n in alarm memory
z<n>.activity.fail visible false zone n no activity fail
true zone n activity fail

Log Files

If a Ksenia anti-intrusion unit is connected to HSYCO, the security.log file will be written in the same directories as the daily log files.

This file is never overwritten or deleted from HSYCO SERVER. 

2018.02.20 16:59:28.516 - lares - 20/02/2018 16:56:36 - Disinserimento - Part 1 - U1
2018.02.20 17:00:24.527 - lares - 20/02/2018 16:57:36 - Inserimento - Part 1 - U1
2018.02.20 17:00:44.318 - lares - 20/02/2018 16:57:57 - Allarme - Zone 1
2018.02.20 17:00:49.241 - lares - 20/02/2018 16:57:58 - Ripristino - Zone 1
2018.02.20 17:00:54.043 - lares - 20/02/2018 16:58:06 - Disinserimento - Part 1 - U1
2018.02.20 17:01:18.905 - lares - 20/02/2018 16:58:29 - Fallita Comunicazione - Leonardo - Vocale GSM
2018.02.20 17:01:29.053 - lares - 20/02/2018 16:58:40 - Fallita Comunicazione - Leonardo - SMS

Other information about the Ksenia driver are stored in the message.log daily file.

Release Notes

3.8.0

  • initial version release


Ksenia is a registered trademark of Ksenia Security s.r.l.

Retrieved from "https://wiki.hsyco.com/3.8/index.php?title=Lares4&oldid=10063"