Difference between revisions of "Protege"
Jump to navigation
Jump to search
Line 288: | Line 288: | ||
|area name | |area name | ||
|- | |- | ||
− | |||
|rowspan="5"|o<n>.state | |rowspan="5"|o<n>.state | ||
Line 317: | Line 316: | ||
|output label in ascii format | |output label in ascii format | ||
|- | |- | ||
+ | |||
+ | |rowspan="1"|o<n>.name<sup>[[#note|[Note]]]</sup> | ||
+ | |<text> | ||
+ | |R | ||
+ | |output name | ||
+ | |- | ||
+ | |||
|rowspan="4"|i<n>.state | |rowspan="4"|i<n>.state | ||
Line 380: | Line 386: | ||
|R | |R | ||
|input is not in siren lockout state | |input is not in siren lockout state | ||
+ | |- | ||
+ | |||
+ | |rowspan="1"|i<n>.name<sup>[[#note|[Note]]]</sup> | ||
+ | |<text> | ||
+ | |R | ||
+ | |input name | ||
|- | |- | ||
Line 444: | Line 456: | ||
|R | |R | ||
|trouble input is not in siren lockout state | |trouble input is not in siren lockout state | ||
+ | |- | ||
+ | |||
+ | |rowspan="1"|ti<n>.name<sup>[[#note|[Note]]]</sup> | ||
+ | |<text> | ||
+ | |R | ||
+ | |trouble input name | ||
|- | |- | ||
Line 518: | Line 536: | ||
|R | |R | ||
|door is forced open state | |door is forced open state | ||
+ | |||
+ | |rowspan="1"|d<n>.name<sup>[[#note|[Note]]]</sup> | ||
+ | |<text> | ||
+ | |R | ||
+ | |door name | ||
+ | |- | ||
|} | |} |
Revision as of 10:41, 14 August 2019
Protege is a server based architecture enabling you to securely manage, control and monitor a number of users, doors, areas, and other devices. The integration with HSYCO can be accomplished with a TCP/IP network connection.
- ProtegeGXServer needs to be configured to accept a connection on a defined TCP/IP port with the ICT Automation and Control Service protocol.
- A PIN must be set (4 to 6 digits)
- Disable encryption and checksum
- Select Little Endian format
- Enable Login Block after PIN error
HSYCO Configuration
Add a PROTEGE I/O Server in the I/O Servers section of the Settings and set its parameters:
Communication
- IP Address: the ICT Protege Server panel address
- IP Port: TCP/IP port enabled on the ICT Protege Server
High Availability
- Shutdown when inactive: defaults to true.
Options
ID | Default | Values | Description |
---|---|---|---|
pin | pin | the user PIN that the driver uses when sending commands to the Protege system. It must be a valid user code, able to engage and disengage the panel. | |
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 | ||
gui | true | true | enable support of the tecnoalarm Web interface object |
false | disable support of the tecnoalarm Web interface object | ||
debug | false | true | generates additional logs that can be viewed in verbose mode |
false | debug logging disabled | ||
areaslist | string | list of all the areas that are declared on the panel. Areas could not be consecutive and special characters "-" and ";" are used for intervals definition. E.G. 0-3;5-9 means areas from 0 to 3, from 5 to 9. E.G. 4;15 means area number 4 and number 15 | |
inputslist | string | list of all the inputs that are declared on the panel. Inputs could not be consecutive and special characters "-" and ";" are used for intervals definition. E.G. 0-3;5-9 means inputs from 0 to 3, from 5 to 9. E.G. 4;15 means input number 4 and input 15 | |
outputslist | string | list of all the outputs that are declared on the panel. Outputs could not be consecutive and special characters "-" and ";" are used for intervals definition. E.G. 0-3;5-9 means outputs from 0 to 3, from 5 to 9. E.G. 4;15 means output number 4 and output 15 | |
doorslist | string | list of all the doors that are declared on the panel. Doors could not be consecutive and special characters "-" and ";" are used for intervals definition. E.G. 0-3;5-9 means doors from 0 to 3, from 5 to 9. E.G. 4;15 means door number 4 and door 15 | |
troubleinputslist | string | list of all the trouble inputs that are declared on the panel. Trouble inputs could not be consecutive and special characters "-" and ";" are used for intervals definition. E.G. 0-3;5-9 means trouble inputs from 0 to 3, from 5 to 9. E.G. 4;15 means trouble input number 4 and trouble input 15 |
Datapoints
ID | Value | R/W | Description | |||
---|---|---|---|---|---|---|
connection | online | R | connection established | |||
offline | R | connection failed | ||||
panel.firmware.build | <text> | R | firmware build of the panel | |||
panel.firmware.type | <text> | R | firmware type of the panel | |||
panel.firmware.version | <text> | R | firmware version of the panel | |||
panel.hardware.version | <text> | R | hardware version of the panel | |||
panel.serial.number | <text> | R | serial number of the panel | |||
a<n>.armed | 1 | R | area is armed | |||
0 | R | area is disarmed | ||||
a<n>.state | armed | R | area is armed | |||
disarmed | R | area is disarmed | ||||
inputsopen | R | area is in inputs open state | ||||
trouble | R | area is in trouble state | ||||
bypasserror | R | area is in bypass error state | ||||
bypasswarning | R | area is in bypass warning state | ||||
usercountnotzero | R | area is in user count not zero state | ||||
exitdelay | R | area is in exit delay state | ||||
entrydelay | R | area is in entry delay state | ||||
disarmdelay | R | area is in disarm delay state | ||||
codedelay | R | area is in code delay state | ||||
a<n>.tamper.state | armed | R | area tamper is armed | |||
disarmed | R | area tamper is disarmed | ||||
busy | R | area tamper is busy | ||||
a<n>.state.flags.alarm.activated | 1 | R | area alarm activated | |||
0 | R | area alarm is not active | ||||
a<n>.state.flags.siren.activated | 1 | R | area siren activated | |||
0 | R | area siren is not active | ||||
a<n>.state.flags.alarms.in.memory | 1 | R | at least one area alarm in memory | |||
0 | R | no area alarms in memory | ||||
a<n>.state.flags.remote.armed | 1 | R | area remotely armed | |||
0 | R | alarm is not remotely armed | ||||
a<n>.state.flags.force.armed | 1 | R | area forced armed | |||
0 | R | alarm is not forced armed | ||||
a<n>.state.flags.instant.armed | 1 | R | area instant armed | |||
0 | R | alarm is not instant armed | ||||
a<n>.state.flags.partial.armed | 1 | R | area partially armed | |||
0 | R | alarm is not partially armed | ||||
a<n>.name[Note] | <text> | R | area name | |||
o<n>.state | off | R | output is off | |||
on | R | output is on | ||||
onpulsed | R | output is in on pulsed state | ||||
ontimed | R | output is in on timed state | ||||
onpulsedtimed | R | output is in on pulsed timed state | ||||
o<n>.ascii | <text> | R | output label in ascii format | |||
o<n>.name[Note] | <text> | R | output name | |||
i<n>.state | closed | R | input is closed | |||
open | R | input in open | ||||
short | R | input is in shortcut state | ||||
tamper | R | input is in tamper state | ||||
i<n>.closed | 1 | R | input is closed | |||
0 | R | input is open | ||||
i<n>.ascii | <text> | R | input label in ascii format | |||
i<n>.bypass.state.bypassed | 1 | R | input is bypassed | |||
0 | R | input is not bypassed | ||||
i<n>.bypass.state.bypasslatched | 1 | R | input is bypass latched | |||
0 | R | input is not bypass latched | ||||
i<n>.bypass.state.sirenlockout | 1 | R | input is siren lockout state | |||
0 | R | input is not in siren lockout state | ||||
i<n>.name[Note] | <text> | R | input name | |||
ti<n>.state | closed | R | trouble input is closed | |||
open | R | trouble input in open | ||||
short | R | trouble input is in shortcut state | ||||
tamper | R | trouble input is in tamper state | ||||
ti<n>.closed | 1 | R | trouble input is closed | |||
0 | R | trouble input is open | ||||
ti<n>.ascii | <text> | R | trouble input label in ascii format | |||
ti<n>.bypass.state.bypassed | 1 | R | trouble input is bypassed | |||
0 | R | trouble input is not bypassed | ||||
ti<n>.bypass.state.bypasslatched | 1 | R | trouble input is bypass latched | |||
0 | R | trouble input is not bypass latched | ||||
ti<n>.bypass.state.sirenlockout | 1 | R | trouble input is siren lockout state | |||
0 | R | trouble input is not in siren lockout state | ||||
ti<n>.name[Note] | <text> | R | trouble input name | |||
d<n>.lock.state | locked | R | door is locked | |||
unlockedbyuseraccess | R | door is unlocked by user access | ||||
unlockedbyschedule | R | door is unlocked by schedule | ||||
unlockedbyusertimed | R | door is unlocked by user timed | ||||
unlockedbyandlatched | R | door is unlocked by and latched | ||||
unlockedbyrex | R | door is unlocked by rex | ||||
unlockedbyren | R | door is unlocked by ren | ||||
unlockedbykeypadmenu | R | door is unlocked by keypad menu | ||||
unlockedbyarea | R | door is unlocked by area | ||||
unlockedbyfirealarm | R | door is unlocked by fire alarm | ||||
d<n>.locked | 1 | R | door is locked | |||
0 | R | door is unlocked | ||||
d<n>.state | closed | R | door is closed | |||
open | R | door is open | ||||
openalert | R | door is open alert state | ||||
leftopen | R | door is left open state | ||||
forcedopen | R | door is forced open state | d<n>.name[Note] | <text> | R | door name |
- Note
- Names of areas, inputs, trouble inputs, outputs, doors are imported from a configuration file as described later in this application note.