Ats
Aritech ATS panels are multi-area intrusion detection systems. The integration with HSYCO can be accomplished via direct control through the RS-232 port on the serial module.
Communication
Employ an RS-232 cable to connect the panel directly to HSYCO or to an Ethernet/RS-232 gateway. The cable must follow this pinout diagram:
RS-232 parameters:
Baud rate | same as panel settings (default 4800) |
Data bits | 8 |
Stop bit | 1 |
Parity | none |
Flow control | RTS/CTS |
HSYCO Configuration
Options
ID | Default | Values | Description |
---|---|---|---|
gui | true | true | enable support for the UI object, UISET actions and USER commands |
false | disable UI support | ||
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 | 5 | n > 0 | the data acquisition interval, in seconds |
logsize | 20 | n ≥ 0 | the number of log lines to display in the UI object |
maxzone | 256 | 0 ≤ n ≤ 256 | highest zone index set on the panel. This option is recommended to improve the I/O Server's performances |
maxoutput | 256 | 0 ≤ n ≤ 256 | highest output index set on the panel. This option is recommended to improve the I/O Server's performances |
maxras | 16 | 0 ≤ n ≤ 16 | highest RAS (Remote Arming Station) index set on the panel. This option is recommended to improve the I/O Server's performances |
ats.ini
The ats.ini file is a specific configuration file located in the root directory. Here you can define the names of zones and areas so that they will be automatically added to the user interface. Add a new line for each name using this format:
<io_server_id>.zone.<n> = <name> <io_server_id>.area.<n> = <name>
For instance:
ats.zone.1 = Kitchen ats.zone.2 = Corridor ats.area.1 = Floor 1
Datapoints
ID | Value | R/W | Description |
---|---|---|---|
connection | online | R | connection established |
offline | R | HSYCO can't connect to the panel | |
armed | 1 | R | at least one area is armed |
W | arm all active areas | ||
0 | R | no area is armed | |
W | disarm all active areas | ||
alarm | 1 | R | at least one area is in alarm |
0 | R | no area is in alarm | |
reset | W | reset system alarms | |
clock | read | W | request the reading of the panel’s clock value |
<date_time> | R | the panel’s clock is set to <date_time>. The value has the format "yyyy-mm-dd hh:mm:ss" (e.g. "2012-12-30 16:59:23").
This event is only triggered after a request. | |
a<n>.name | <text> | R | area <n> has been assigned the name <text> |
z<n>.name | <text> | R | zone <n> has been assigned the name <text> |
a<n>.armed | 1 | R | area <n> is armed |
W | arm area <n> | ||
0 | R | area <n> is disarmed | |
W | disarm area <n> | ||
force | W | force arm area <n> | |
a<n>.alarm | 1 | R | area <n> is in alarm |
0 | R | area <n> is not in alarm | |
a<n>.open | 1 | R | area <n> has open zones |
0 | R | area <n> has no open zones | |
a<n>.isolated | 1 | R | area <n> has isolated zones |
0 | R | area <n> has no isolated zones | |
a<n>.exit | 1 | R | exit time is active on area <n> |
0 | R | exit time is not active on area <n> | |
a<n>.entry | 1 | R | entry time is active on area <n> |
0 | R | entry time is not active on area <n> | |
a<n>.alarm.local | 1 | R | local alarms are active on area <n> |
0 | R | no local alarm is active on area <n> | |
a<n>.warning | 1 | R | console warning is active on area <n> |
0 | R | console warning is not active on area <n> | |
z<n>.state1[Note] | tamper | R | tamper active on zone <n> |
alarm | R | alarm active on zone <n> | |
closed | R | zone <n> closed | |
night | R | night holdup active on zone <n> | |
local | R | local alarm active on zone <n> | |
isolated | R | zone <n> isolated | |
z<n>.state2[Note] | short | R | zone <n> in short circuit |
open | R | zone <n> open | |
closed | R | zone <n> closed | |
active | R | zone <n> active | |
masked | R | zone <n> masked | |
z<n>.isolated | 1 | W | isolate zone <n> |
0 | W | de-isolate zone <n> | |
z<n>.alarm | reset | W | reset alarms on zone <n> |
o<n>.active | 1 | R | output <n> is active |
W | activate output <n> | ||
0 | R | output <n> is not active | |
W | deactivate output <n> | ||
o<n>.inverted | 1 | R | output <n> is inverted |
0 | R | output <n> is not inverted | |
ras<n>.offline | 1 | R | RAS <n> is offline |
0 | R | RAS <n> is online | |
ras<n>.tamper | 1 | R | RAS <n> is tampered |
0 | R | RAS <n> is not tampered | |
ras<n>.isolated | 1 | R | RAS <n> is isolated |
0 | R | RAS <n> is not isolated | |
ras<n>.inhibited | 1 | R | RAS <n> is inhibited |
0 | R | RAS <n> is not inhibited | |
dgp<n>.offline | 1 | R | DGP <n> is offline |
0 | R | DGP <n> is online | |
dgp<n>.isolated | 1 | R | DGP <n> is isolated |
0 | R | DGP <n> is not isolated | |
dgp<n>.inhibited | 1 | R | DGP <n> is inhibited |
0 | R | DGP <n> is not inhibited | |
dgp<n>.battery.missing | 1 | R | battery missing on DGP <n> |
0 | R | battery ok on DGP <n> | |
dgp<n>.battery.low | 1 | R | battery low on DGP <n> |
0 | R | battery ok on DGP <n> | |
dgp<n>.battery.test | 1 | R | battery test active on DGP <n> |
0 | R | no battery test active on DGP <n> | |
dgp<n>.battery.test.fail | 1 | R | battery test failed on DGP <n> |
0 | R | battery test ok on DGP <n> | |
dgp<n>.mains.fail | 1 | R | mains failure on DGP <n> |
0 | R | mains ok on DGP <n> | |
dgp<n>.fuse.fail | 1 | R | fuse failure on DGP <n> |
0 | R | fuses ok on DGP <n> | |
dgp<n>.siren.fail | 1 | R | siren failure on DGP <n> |
0 | R | siren ok on DGP <n> | |
dgp<n>.tamper | 1 | R | DGP <n> is tampered |
0 | R | DGP <n> is not tampered |
- Note
- The value of a zone status (datapoints z<n>.state1 and z<n>.state2) depends on the configuration of the zone typology.