Difference between revisions of "Protege"
Jump to navigation
Jump to search
Line 19: | Line 19: | ||
=== High Availability === | === High Availability === | ||
*'''Shutdown when inactive''': defaults to true. | *'''Shutdown when inactive''': defaults to true. | ||
+ | |||
+ | === Options === | ||
+ | |||
+ | {| class="wikitable" | ||
+ | !ID | ||
+ | !Default | ||
+ | !Values | ||
+ | !Description | ||
+ | |- | ||
+ | |||
+ | |code | ||
+ | | | ||
+ | |code | ||
+ | |the user code that the driver uses when sending commands to the Tecnoalarm system. It must be a valid user code, or the MASTER code when using the TP8-64BUS | ||
+ | |- | ||
+ | |||
+ | |model | ||
+ | | | ||
+ | |string | ||
+ | |the system’s model. Use one of the following values: TP16-256, TP8-64BUS, TP8-96VIDEO, TP8-96GSM, TP16-512GSM, TP8-88, TP8-88P, TP20-440 | ||
+ | |- | ||
+ | |||
+ | |rowspan="2"|startupevents | ||
+ | |rowspan="2"|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 | ||
+ | |- | ||
+ | |||
+ | |rowspan="2"|gui | ||
+ | |rowspan="2"|true | ||
+ | |true | ||
+ | |enable support of the tecnoalarm Web interface object | ||
+ | |- | ||
+ | |false | ||
+ | |disable support of the tecnoalarm Web interface object | ||
+ | |- | ||
+ | |||
+ | |rowspan="2"|userlogs | ||
+ | |rowspan="2"|false | ||
+ | |true | ||
+ | |generates logs that can be viewed with the userlist object, and can be selected to generate user events | ||
+ | |- | ||
+ | |false | ||
+ | |logs for userlist objects disabled. Normal text logs are generated even when this option is false | ||
+ | |- | ||
+ | |||
+ | |logsize | ||
+ | |50 | ||
+ | |n ≥ 0 | ||
+ | |the number of log events shown in the tecnoalarm Web object. Set to 0 to hide the log in the tecnoalarm object | ||
+ | |- | ||
+ | |||
+ | |pass | ||
+ | | | ||
+ | |string | ||
+ | |the passphrase used to encrypt the TCP/IP traffic. If the Tecnoalarm system doesn’t support the passphrase, you should omit this parameter | ||
+ | |- | ||
+ | |||
+ | |polltime | ||
+ | |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 Tecnoalarm system | ||
+ | |- | ||
+ | |||
+ | |||
+ | |} |
Revision as of 07:15, 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 |
---|---|---|---|
code | code | the user code that the driver uses when sending commands to the Tecnoalarm system. It must be a valid user code, or the MASTER code when using the TP8-64BUS | |
model | string | the system’s model. Use one of the following values: TP16-256, TP8-64BUS, TP8-96VIDEO, TP8-96GSM, TP16-512GSM, TP8-88, TP8-88P, TP20-440 | |
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 | ||
userlogs | false | true | generates logs that can be viewed with the userlist object, and can be selected to generate user events |
false | logs for userlist objects disabled. Normal text logs are generated even when this option is false | ||
logsize | 50 | n ≥ 0 | the number of log events shown in the tecnoalarm Web object. Set to 0 to hide the log in the tecnoalarm object |
pass | string | the passphrase used to encrypt the TCP/IP traffic. If the Tecnoalarm system doesn’t support the passphrase, you should omit this parameter | |
polltime | 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 Tecnoalarm system |