Difference between revisions of "Dea Xensity"
Jump to navigation
Jump to search
| (3 intermediate revisions by the same user not shown) | |||
| Line 7: | Line 7: | ||
== Communication == | == Communication == | ||
| − | DEA XENSITY | + | DEA XENSITY controllers can be connected via ethernet. A valid IP address must be assigned to the controller using the configuration software. |
| − | {{tip| In case of multiple DEA XENSITY IO Servers running on the same HSYCO Server you must assign a different UDP port to each XENSITY | + | {{tip| In case of multiple DEA XENSITY IO Servers running on the same HSYCO Server you must assign a different UDP port to each XENSITY controller}} |
== HSYCO Configuration == | == HSYCO Configuration == | ||
| Line 296: | Line 296: | ||
|R | |R | ||
|zone <n> on prealarm memory | |zone <n> on prealarm memory | ||
| + | |- | ||
| + | |||
| + | |rowspan="2" |z<n>.tamper | ||
| + | |0 | ||
| + | |R | ||
| + | |zone <n> not on tamper alarm | ||
| + | |- | ||
| + | |1 | ||
| + | |R | ||
| + | |zone <n> on on tamper alarm | ||
| + | |- | ||
| + | |||
| + | |rowspan="2" |z<n>.tamper.mem | ||
| + | |0 | ||
| + | |R | ||
| + | |zone <n> not on tamper memory alarm | ||
| + | |- | ||
| + | |1 | ||
| + | |R | ||
| + | |zone <n> on on tamper memory alarm | ||
|- | |- | ||
| Line 377: | Line 397: | ||
| − | '' | + | ''XENSITY is a registered trademark of DEA Security S.r.l.'' |
Latest revision as of 20:53, 23 March 2020
DEA XENSITY is a Point ID intrusion detection system using special piezoelectric sensors for the protection of doors, windows, glass surfaces, security grilles and walls. This driver is compatible with the following controllers: Xensity128, Xensity64, Xensity32. Make sure to install the latest available firmware.
Contents
Communication
DEA XENSITY controllers can be connected via ethernet. A valid IP address must be assigned to the controller using the configuration software.
In case of multiple DEA XENSITY IO Servers running on the same HSYCO Server you must assign a different UDP port to each XENSITY controller
HSYCO Configuration
Add a XENSITY I/O Server in the I/O Servers section of the Settings and set its parameters:
Communication
- Address: IP address of the XENSITY controller (mandatory)
- Port: UDP port (mandatory)
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 ≥ 0 | the 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 Xensity system |
Datapoints
| ID | Value | R/W | Description |
|---|---|---|---|
| connection | online | R | connection established |
| offline | R | HSYCO can't connect to the panel | |
| alarm | 0 | R | no alarms |
| 1 | R | at least one zone of this controller on alarm | |
| link.x16 | 0 | R | connection with X16-ER16L is not stable |
| 1 | R | connection with X16-ER16L is stable | |
| link.sens | 0 | R | connection with sensors is not stable |
| 1 | R | connection with sensors is stable | |
| bus.power | 0 | R | bus sensors power supply not ok |
| 1 | R | bus sensors power supply ok | |
| alarm.nf | 0 | R | no alarms |
| 1 | R | At least one alarm is active - not filtered- | |
| tamper.nf | 0 | R | no tamper alarms |
| 1 | R | at least one tamper alarm is active - not filtered- | |
| arm | 0 | R | arm is not active |
| 1 | R | arm is active | |
| in.tamper | 0 | R | tamper input is not active |
| 1 | R | tamper input is active | |
| battery.low | 0 | R | battery charge ok |
| 1 | R | battery charge is low | |
| test.fail | 0 | R | autotest is ok |
| 1 | R | at least one sensor failed autotest | |
| bus.fault | 0 | R | sensors bus is ok |
| 1 | R | sensors bus fault | |
| bus.overcurr | 0 | R | current on sensors bus is ok |
| 1 | R | over current on sensors bus | |
| tamper | 0 | R | no sensors in tamper alarm |
| 1 | R | At least one sensor in tamper alarm | |
| power.fault | 0 | R | power ok |
| 1 | R | power fail | |
| vin | <v> | R | power supply voltage <v> in mV |
| oc<n> | 0 | R | open collector output <n> is open |
| 1 | R | open collector output <n> is closed | |
| rel<n> | 0 | R | relay <n> is open |
| 1 | R | relay <n> is closed | |
| in<n> | 0 | R | input <n> is open |
| 1 | R | input <n> is closed | |
| serial | <string> | R | serial number <string> |
| seclev | <n> | R | global security level <n> |
| pn | <n> | R | hardware type <n> |
| z<n>.alarm | 0 | R | zone <n> not on alarm |
| 1 | R | zone <n> on alarm | |
| z<n>.alarm.mem | 0 | R | zone <n> not on alarm memory |
| 1 | R | zone <n> on alarm memory | |
| z<n>.prealarm.mem | 0 | R | zone <n> not on prealarm memory |
| 1 | R | zone <n> on prealarm memory | |
| z<n>.tamper | 0 | R | zone <n> not on tamper alarm |
| 1 | R | zone <n> on on tamper alarm | |
| z<n>.tamper.mem | 0 | R | zone <n> not on tamper memory alarm |
| 1 | R | zone <n> on on tamper memory alarm | |
| z<n>.armed | 0 | R | zone <n> disarmed |
| 1 | R | zone <n> armed | |
| z<n>.bypass | 0 | R | zone <n> not bypassed |
| 1 | R | zone <n> bypassed | |
| z<n>.fault | 0 | R | zone <n> not in fault |
| 1 | R | zone <n> fault | |
| z<n>.fault.mem | 0 | R | zone <n> not in fault memory |
| 1 | R | zone <n> fault memory | |
| z<n>.line | <v> | R | zone <n> line type |
| z<n>.name | <string> | R | zone <n> name <string> |
| z<n>.pn | <v> | R | zone <n> has hardware type <v> |
| z<n>.seclev | <v> | R | zone <n> has security level <v> |
| z<n>.serial | <string> | R | zone <n> has serial address <string> |
Release Notes
3.7.0
- initial release
XENSITY is a registered trademark of DEA Security S.r.l.
