Difference between revisions of "Guardall"
| Line 30: | Line 30: | ||
|- | |- | ||
| '''Flow control''' | | '''Flow control''' | ||
| − | | | + | | none |
|} | |} | ||
Revision as of 12:55, 16 May 2016
Guardall QX32i, PX80 and PX500 are multi-area security systems. The integration with HSYCO can be accomplished via direct control through the RS-232 port on the panel. The I/O Server supports QX32i, PX80 and PX500 Guardall units with software version 4.33.
Contents
Communication
Employ a female-female RS-232 crossed cable to connect the panel directly to HSYCO or to an Ethernet/RS-232 gateway. The cable must follow this pinout diagram:
2 ↔ 3 3 ↔ 2 5 ↔ 5 7 ↔ 8 8 ↔ 7
RS-232 parameters:
| Baud rate | 9600 |
| Data bits | 8 |
| Stop bit | 1 |
| Parity | none |
| Flow control | none |
It is also possible to communicate with the Guardall control panel without a full RTS/CTS flow control, but simply asserting (+3 to +15V) the CTS line (pin 8) of the Guardall serial port, and ignoring its RTS line (pin 7).
Guardall Configuration
You must configure the unit to enable serial communication even if the system is armed. Digit the technician code on the keypad and select menu entry "99" (Total Configuration), then select entry “10” (Communication) and make sure that the serial connection is enabled when the system is armed (on).
Moreover, it is necessary to enable the required features to be available remotely. To this end, from the technician’s menu, select again menu entry “99”, then “12”. Here enter the number 1 and modify the settings accordingly to your requirements.
HSYCO Configuration
Add a Guardall I/O Server in the I/O Servers section of the Settings and set its parameters:
Communication
- Comm ID: select the comm port connected to the panel.
High Availability
- Shutdown when inactive: defaults to true.
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 | ||
| logsize | 20 | n ≥ 0 | the number of log lines to display in the UI object |
| arm | true | true | allow groups arming |
| false | deny groups arming | ||
| disarm | true | true | allow groups disarming |
| false | deny groups disarming | ||
| fastpolling | false | true | perform a faster polling, required for big installations |
| false | normal polling performed | ||
| key | 00000000 | <auth_key> | the 8-digits authentication key set in the panel's configuration |
guardall.ini
The guardall.ini file is a specific configuration file located in the root directory. Here you can define the names of the groups so that they will be automatically added to the user interface. Add a new line for each group using this format:
<io_server_id>.group.<n> = <name>
For instance:
guard.group.1 = Kitchen guard.group.2 = Living room
Datapoints
| ID | Value | R/W | Description |
|---|---|---|---|
| connection | online | R | connection established |
| offline | R | HSYCO can't connect to the panel | |
| armed | 0 | R | all groups are disarmed |
| W | disarm all groups | ||
| 1 | R | the system is (partially) armed | |
| W | arm all groups | ||
| alarm | 0 | R | the system is not in a alarm state |
| 1 | R | the system is in a alarm state | |
| tamper | 0 | R | the system is not in a tamper state |
| 1 | R | the system is in a tamper state | |
| panel.tamper | 0 | R | the panel is not tampered |
| 1 | R | the panel is tampered | |
| bell.tamper | 0 | R | the bell is not tampered |
| 1 | R | the bell is tampered | |
| low.volts | 0 | R | voltage ok |
| 1 | R | low voltage detected | |
| sounder | 0 | R | the sounder is inactive |
| 1 | R | the sounder is active | |
| audio | 0 | R | the audio signal of the panel is inactive |
| 1 | R | the audio signal of the panel is active | |
| strobe | 0 | R | the strobe is inactive |
| 1 | R | the strobe is active | |
| mains.fail | 0 | R | no mains fail |
| 1 | R | mains fail | |
| power.fail | 0 | R | no power fail |
| 1 | R | power fail | |
| battery.fail | 0 | R | no battery fail |
| 1 | R | battery fail | |
| fuse.1.fault | 0 | R | fuse 1 is working |
| 1 | R | fuse 1 in fault | |
| fuse.2.fault | 0 | R | fuse 2 is working |
| 1 | R | fuse 2 in fault | |
| fuse.3.fault | 0 | R | fuse 3 is working |
| 1 | R | fuse 3 in fault | |
| line.fault | 0 | R | communication line is working |
| 1 | R | communication line in fault | |
| c<n>.name | <text> | R | the name of circuit <n> is set to <text> |
| g<n>.name | <text> | R | the name of group <n> is set to <text> |
| g<n>.armed | 0 | R | group <n> is disarmed |
| W | disarm group <n> | ||
| 1 | R | group <n> is armed | |
| W | arm group <n> | ||
| c<n>.alarm | 0 | R | circuit <n> is not in alarm state |
| 1 | R | circuit <n> is in alarm state | |
| c<n>.tamper.alarm | 0 | R | circuit <n> is not in tamper alarm |
| 1 | R | circuit <n> is in tamper alarm | |
| c<n>.open | 0 | R | circuit <n> is closed |
| 1 | R | circuit <n> is open | |
| c<n>.tamper | 0 | R | circuit <n> is not tampered |
| 1 | R | circuit <n> is tampered | |
| c<n>.fault | 0 | R | circuit <n> is working properly |
| 1 | R | circuit <n> is faulty | |
| c<n>.bypassed | 0 | R | circuit <n> is not bypassed |
| W | unbypass circuit <n> | ||
| 1 | R | circuit <n> is bypassed | |
| W | bypass circuit <n> | ||
| c<n>.isolated | 0 | R | circuit <n> is not isolated |
| W | un-isolate circuit <n> | ||
| 1 | R | circuit <n> is isolated | |
| W | isolate circuit <n> | ||
| c<n>.soaked | 0 | R | circuit <n> is not soaked |
| W | un-soak circuit <n> | ||
| 1 | R | circuit <n> is soaked | |
| W | soak circuit <n> | ||
| c<n>.status[Note 1] | <status_values> | R | the status of circuit <n> is set to the reported values |
| c<n>.attributes[Note 1] | <attributes_values> | R | the attributes of circuit <n> are set to the reported values |
| c<n>.resistance[Note 1] | <value> | R | the measured resistance on circuit <n> is <value> ohm |
| >20k | R | the measured resistance on circuit <n> is greater than 20 K-ohm | |
| k<n>.tamper | 0 | R | keypad <n> is not tampered |
| 1 | R | keypad <n> is tampered | |
| k<n>.fault | 0 | R | keypad <n> is working properly |
| 1 | R | keypad <n> is faulty | |
| logon.<n> | <user_num> | R | user with number <user_num> logged in from keypad <n> |
| error | R | wrong pin entered in keypad <n> | |
| system | reset | W | reset alarms |
- Note 1
- These datapoint are available if the option fastpolling is not set to true
| Circuit status values | |
|---|---|
| Value | Description |
| A | alarm/open |
| B | alarm/open and tamper |
| E | latched alarm and tamper |
| M | marginal clear |
| m | marginal alarm |
| N | normal |
| T | tamper |
| L | latched alarm |
| F | fault/no answer |
| X | Auxiliary alarm |
| Circuit attributes values | |
|---|---|
| Value | Description |
| B | bypassed circuit |
| I | isolated circuit |
| S | soak failed |
| T | soaked circuit |
| Y | temporarily bypassed circuit |
| Q | temporarily isolated circuit |
| H | circuit in shunt |
| A | existing circuit |
| M | multi-alarm |
| F | bank reset failed/door forced |
| L | locked |
| O | open |
Attributes can be combined together, for instance if a circuit is both isolated and bypassed, the attribute value will be “BI”.
User Interface
Guardall Object
The user interface for the Guardall multi-area intrusion detection system:
The Guardall object is listed in the Project Editor’s new object list only when at least one Guardall I/O Server is defined.
Parameters
- server id: the server ID. Supports Redirect variables
- position: the object's position. Use the pixels or rows and columns coordinates format
Syntax
(guardall <server id>; <position>)
E.g.
(guardall serverid; x10y20)
UISET Actions
| ID | Attribute | Set to | |
|---|---|---|---|
| log | value | latest security log lines (as many as specified by the 'logsize' option) | |
| log0 | value | latest line of the security log when a new entry is added, set back to blank after a short period | |
| c<n>.name | value | name assigned to circuit <n> or its number if no name is defined | |
| connection.label | visible | true | when datapoint connection = offline |
| false | when datapoint connection = online | ||
| <datapoint_id>.1.label | visible | true | when datapoint with ID <datapoint_id> has value '1' |
| false | when datapoint with ID <datapoint_id> has value '0' | ||
| <datapoint_id>.0.label | visible | true | when datapoint with ID <datapoint_id> has value '0' |
| false | when datapoint with ID <datapoint_id> has value '1' | ||
USER Commands
| Name | Param | Action |
|---|---|---|
| armed | 0 | disarm all groups |
| 1 | arm all groups | |
| g<n>.armed | 0 | disarm group <n> |
| 1 | arm group <n> | |
| c<n>.bypassed | 0 | unbypass zone <n> |
| 1 | bypass zone <n> | |
| c<n>.isolated | 0 | un-isolate zone <n> |
| 1 | isolate zone <n> | |
| c<n>.soaked | 0 | un-soak zone <n> |
| 1 | soak zone <n> | |
| system | reset | reset alarms |
| input.bypassed | 0 | unbypass circuit |
| 1 | bypass circuit | |
| input.isolated | 0 | un-isolate circuit |
| 1 | isolate circuit | |
| input.soaked | 0 | un-soak circuit |
| 1 | soak circuit |
Log Files
If a Guardall 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.
2014.02.22 11:23:08.118 - guard - 2116 2000.1.4 22:50:16 Area disinserita - Utente: 0, Area: 1 2014.02.22 11:23:08.120 - guard - 2117 2000.1.4 22:50:16 Area disinserita - Utente: 0, Area: 2 2014.02.22 11:23:13.204 - guard - 2118 2000.1.4 22:50:22 Gruppo inserito - Utente: 0, Gruppo: 2 2014.02.22 11:23:13.205 - guard - 2119 2000.1.4 22:50:22 Area inserita - Utente: 0, Area: 1 2014.02.22 11:23:13.222 - guard - 2120 2000.1.4 22:50:22 Area inserita - Utente: 0, Area: 2 2014.02.22 11:23:16.449 - guard - 2121 2000.1.4 22:50:24 Gruppo disinserito - Utente: 0, Gruppo: 2 2014.02.22 11:23:16.450 - guard - 2122 2000.1.4 22:50:24 Area disinserita - Utente: 0, Area: 1 2014.02.22 11:23:16.451 - guard - 2123 2000.1.4 22:50:24 Area disinserita - Utente: 0, Area: 2
Other information about the Guardall driver are stored in the message.log daily file.
Release Notes
3.5.0
- added "key" server option
- improved communication error handling
3.4.0
- fixed a timeout issue that could prevent proper startup with very large number of zones
- added "fastpolling" server option
3.3.0
- added “logsize” server option
- object modified
- added guardall.ini configuration file
3.1.0
- added support for the PX80 panel
- modified log messages
3.0.3
- added the “ID.logon.N = error” event
3.0.2
- initial version release
Guardall is a registered trademark of UTC Fire & Security.
