VdS 2465
The VdS driver allows connections to danger alarm systems with the protocol VdS 2465 over the RS232 interface. All devices that uses version 2 of the VdS protocol 2465 1999-03 will be supported. Special handling respectively manufacturer specific record types are implemented for the following devices
- DLS 4000
- Telenot
- Complex 400
- DEZ 9000
- effeff TSS 13
Supported Record types:
| Type | Description | Special handling for |
|---|---|---|
| 00H | Manufacturer specific | DLS 4000, Telenot Device information |
| 01H | Priority | |
| 02H | Event state changes with acknowledge | DLS 4000, Telenot, Complex 400 |
| 03H | Event acknowledgement | |
| 04H | Event state changes without acknowledge | DLS 4000 |
| 06H | Manufacturer specific | effeff TSS13 event state changes with acknowledge |
| 07H | Manufacturer specific | effeff TSS13 event acknowledgement |
| 08H | Manufacturer specific | effeff TSS13 event state changes without acknowledge |
| 10H | Query | |
| 11H | Error | |
| 20H | Status | DLS 4000, Telenot |
| 24H | Blockstatus | DLS 4000, Telenot, DEZ 9000 |
| 25H | General alarm | |
| 40H | Test event | |
| 41H | Test event acknowledge | Telenot |
| 50H | Date and Time | |
| 51H | Manufacturer identification | |
| 54H | ASCII character string | |
| 55H | Supported record types | |
| 56H | Identifications number | |
| 73H | Telegram counter | |
| 74H | Container | |
| ACH | Manufacturer specific | DLS 4000 Identifikation |
| BBH | Manufacturer specific | Telenot Slot Information |
| BFH | Manufacturer specific | Telenot System Information |
The name for the VdS 246 driver is: vds
The routing address of the first VdS driver is: 1150
The data point file name of the first VdS driver is: vds1.txt
The configuration file for global settings of the first VdS driver is: vds1.cfg
For the VdS driver as well as all other gateway drivers the data point definitions are as follows:
| Type | Description |
|---|---|
| M | Integer value (binary data points, counters) which can/shall only be read by the gateway |
| S | Integer value which can be either read or written by the gateway. |
| X | Floating point value (with decimal place) which can/shall only be read by the gateway |
| Y | Floating point value (with decimal place) which can be either read or written by the gateway. |
| A | String, is used e.g. with BACnet Trends and ESPA4.4.4 data points |
Addresses are defined as follows:
<ident-nr> <device>.<aera>.<address>.<sub-address>.<address-extension>[.<event>]
or
<ident-nr> test
for mapping the test events within the gateway oder
failure
for communication failure or Telenot specific
<ident-nr> test telenot system <event> telenot slot <address>.<event> telenot cmd <address>.<sub-address>.<event>
| Name | Description |
|---|---|
| ident-nr | Ident number of external systems. Maximum of 12 digits. |
| device | Device number, logical devices, integers in the range of 0 … 16. |
| area | Area within the device, integers in the range of 0 … 16. |
| address | Adresse, integers in the range of 0 … 255. |
| sub-address | Sub address, integers in the range of 0 … 255. |
| address-extension | Address extension, integers in the range of 0 … 16. |
| event | VdS event type code, integers in the range of 0 … 127. |
The precise meaning depends on the connected devices respectively is specified in the VdS standard.
Examples:
[failure] name = Communication failure [S 101010 1.1.2.0.1] name = Event IdentNr 101010, device 1, area 1, address 2, subaddress 0, extended address 1 [S 101010 1.1.2.0.1.32] name = Event IdentNr 101010, device 1, area 1, address 2, Subaddress 0, extend address 1, event code 32 [M 10101 test] name = Test event type 40H [M telenot system 1] name = Telenot system event Akku error [M telenot slot 1.16] name = Telenot Slot event DISCONNECT [M telenot cmd 5.50.97] # write to 1 --> protected, 0 unprotected name = Telenot command address/extension 0x0530 event code security area 0x61