Difference between revisions of "Siemens Vanderbilt Edp"
| Line 439: | Line 439: | ||
|false | |false | ||
|when datapoint zone<n>.state != closed | |when datapoint zone<n>.state != closed | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|} | |} | ||
Revision as of 11:36, 8 July 2022
Siemens / Vanderbilt is a family of security panels compatible with the control protocol EDP. This driver has been developed following the EDP protocol specification rev 2.2, 2012-11-12
The integration with HSYCO can be accomplished with a TCP/IP network connection.
Contents
Siemens / Vanderbilt Configuration
Login in the panel web configuration page using a Engineer account.
You should see something like this in the upper right corner of the web page:
Select "Configuration" then "Reporting" then "EDP". You must configure 2 different receivers, one for the command session, one for the event session.
Let's take a look in detail at the configuration of these receivers. The events receiver is configured as "Primary receiver".
Unflag "Primary receiver" for the command receiver. The "IP port" parameter must be different from the one of the event receiver. Set the "Receiver Id" to 1.
Flag "Always connected" on both the receivers. Select protocol version 2 on both. The "Receiver IP Address" is the IP address of the HSYCO server that you want to communicate with. Set the "Receiver Id" to 2.
The "Polling Time" is a very crucial parameter. In the event receiver configuration 8 seconds should be fine because every change of status is sent in asynchronous way by the panel and the polling time only represent the interval between one polling ack and the next one. In the command receiver configuration set 2 seconds, this time, by empirical methods, it's the best one to ensure the connection stability.
In Communication > Reporting > EDP > Settings this is the suggested configuration:
HSYCO Configuration
Add a SIEMENS EDP TCP I/O Server in the I/O Servers section of the Settings and set its parameters:
Communication
- IP Address: Leave empty
- IP Port: Leave empty
High Availability
- Shutdown when inactive: defaults to true.
Options
| ID | Default | Values | Description |
|---|---|---|---|
| eventsport | 50000 | number | the TCP/IP port specified in the event receiver of the panel |
| commandsport | 50001 | number | the TCP/IP port specified in the command receiver of the panel |
| eventsaddress | 1 | number | the event receiver id address |
| commandsaddress | 2 | number | the command receiver id address |
| startupevents | true | 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 | generate uisets |
| false | disable uisets | ||
| eventspolling | 8000 | number | the event receiver polling time in ms |
| commandspolling | 2000 | number | the command receiver polling time in ms |
Datapoints
| ID | Value | R/W | Description |
|---|---|---|---|
| connection | online | R | connection established |
| offline | R | connection failed | |
| log0 | <text> | R | latest line of the security log when a new entry is added |
| last.message.frame | <text> | R | last message frame (hex) received from the panel |
| area.<n>.mode.cmd.unset | 1 | W | disarm area <n> |
| area.<n>.mode.cmd.part.set.a | 1 | W | partially arm area <n>, partition a |
| area.<n>.mode.cmd.part.set.b | 1 | W | partially arm area <n>, partition b |
| area.<n>.mode.cmd.fullset | 1 | W | full arm area <n> |
| area.<n>.mode | unset | R | area <n> is disarmed |
| part_a | R | area <n>, partition a is armed | |
| part_b | R | area <n>, partition a is armed | |
| fullset | R | area <n>, partition a is full armed | |
| area.<n>.name | <text> | R | name assigned to a<n> |
| zone.<n>.mode.cmd.isolate | 1 | W | isolate zone <n> |
| zone.<n>.mode.cmd.inhibit | 1 | W | inhibit zone <n> |
| zone.<n>.name | <text> | R | name assigned to z<n> |
| zone.<n>.type | alarm | R | zone <n> type is ALARM |
| entryexit | R | zone <n> type is ENTRY EXIT | |
| fire | R | zone <n> type is FIRE | |
| firex | R | zone <n> type is FIREX | |
| line | R | zone <n> type is LINE | |
| panic | R | zone <n> type PANIC | |
| holdup | R | zone <n> type HOLDUP | |
| tamper | R | zone <n> type is TAMPER | |
| fault | R | zone <n> type is FAULT | |
| fault_holdup | R | zone <n> type is FAULT HOLDUP | |
| fault_warning | R | zone <n> type is WARNING | |
| tech | R | zone <n> type is TECH | |
| medic | R | zone <n> type MEDIC | |
| keyarm | R | zone <n> type is KEYARM | |
| shunt | R | zone <n> type is SHUNT | |
| xshunt | R | zone <n> type is XSHUNT | |
| locksup | R | zone <n> type is LOCKSUP | |
| seismic | R | zone <n> type is SEISMIC | |
| zone.<n>.state | isolate | R | zone <n> is ISOLATED |
| inhibit | R | zone <n> is INHIBIT | |
| soak | R | zone <n> is SOAK | |
| offline | R | zone <n> is OFFLINE | |
| dcsub | R | zone <n> is DCSUB | |
| alarm | R | zone <n> is ALARMED | |
| maked | R | zone <n> is MASKED | |
| closed | R | zone <n> is CLOSED | |
| open | R | zone <n> is OPEN | |
| short | R | zone <n> is SHORT CUTTED | |
| discon | R | zone <n> is DISCONNECTED |
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 | |
| area.<n>.name | value | name assigned to area<n> | |
| area.<n>.mode | value | area<n> mode value | |
| area<n>.mode.fullset | visible | true | when datapoint area<n>.mode = fullset |
| false | when datapoint area<n>.mode != fullset | ||
| area<n>.mode.unset | visible | true | when datapoint area<n>.mode = unset |
| false | when datapoint area<n>.mode != unset | ||
| area<n>.mode.part.set.a | visible | true | when datapoint area<n>.mode = part_a |
| false | when datapoint area<n>.mode != part_a | ||
| area<n>.mode.part.set.b | visible | true | when datapoint area<n>.mode = part_b |
| false | when datapoint area<n>.mode != part_b | ||
| output<n>.1 | visible | true | when output<n> has value '1' |
| false | when output<n> has value '0' | ||
| output.<n>.0 | visible | true | when output<n> has value '0' |
| false | when output<n> has value '1' | ||
| zone.<n>.name | value | name assigned to zone<n> | |
| zone.<n>.type | value | zone<n> type value | |
| zone.<n>.state | value | zone<n> state value | |
| zone<n>.state.inhibit | visible | true | when datapoint zone<n>.state = inhibit |
| false | when datapoint zone<n>.state != inhibit | ||
| zone<n>.state.isolate | visible | true | when datapoint zone<n>.state = isolate |
| false | when datapoint zone<n>.state != isolate | ||
| zone<n>.state.open | visible | true | when datapoint zone<n>.state = open |
| false | when datapoint zone<n>.state != open | ||
| zone<n>.state.closed | visible | true | when datapoint zone<n>.state = closed |
| false | when datapoint zone<n>.state != closed | ||
Log Files
If a Protege anti-intrusion unit is connected to HSYCO, the security.log file will be written in the same directories as the daily log files and will include the log entries received by the panel.
This file is never overwritten or deleted from HSYCO SERVER.
3.8.0
- initial version release
Vanderbilt is a registered trademark of Vanderbilt Industries
