Teldat VisorALARM PLUS 2U Manuel utilisateur

VisorALARM

PLUS 2U

Installation Manual

Doc. DM374-I Rev. 1.0

May, 2007

- ii -

INDEX

CHAPTER 1 INTRODUCTION...........................................................................................................................1

1. VISORALARM PLUS 2U INTRODUCTION ...................................................................................................2

2. INSTALLATION SCENARIO.............................................................................................................................3

3. OPERATING MODE........................................................................................................................................6

3.1. Monitoring ..........................................................................................................................................6

3.2. Sending of Alarms...............................................................................................................................7

4. ADDITIONAL FEATURES................................................................................................................................9

5. CONFIGURATION AND MANAGEMENT ........................................................................................................10

CHAPTER 2 INSTALLATION ..........................................................................................................................11

1. INTRODUCTION ...........................................................................................................................................12

1.1. General installation conditions.........................................................................................................12

1.2. Connection ........................................................................................................................................14

1.3. Switching on the device.....................................................................................................................17

CHAPTER 3 CONFIGURATION......................................................................................................................19

1. INTRODUCTION ...........................................................................................................................................20

2. COMMON CONFIGURATION .........................................................................................................................21

3. CHANGING THE IP PROTOCOL CONFIGURATION.........................................................................................25

4. CONFIGURING THE NTP CLIENT.................................................................................................................26

5. ARLY ALARM RECEPTION INTERFACE .......................................................................................................28

5.1. Alarm Receiver..................................................................................................................................28

5.2. Communicating with the Automation Server ....................................................................................30

5.3. Communication parameters with the printer....................................................................................30

5.4. Communicating with the mIP/IPDACTs...........................................................................................31

5.5. Network Backup Parameters ............................................................................................................31

5.6. Maintenance Receiver.......................................................................................................................33

5.7. User Configurable Events.................................................................................................................33

5.8. Configuration pattern .......................................................................................................................34

5.9. Upload/Download operation ............................................................................................................37

6. FINAL ADJUSTMENTS .................................................................................................................................40

7. EXAMPLE....................................................................................................................................................41

CHAPTER 4 APPENDICES................................................................................................................................57

1. TROUBLESHOOTING....................................................................................................................................58

2. CONNECTING THE CONNECTORS .................................................................................................................59

2.1. LAN1/LAN2 connections (RJ45).......................................................................................................59

2.2. AUT/PRN Connectors.......................................................................................................................59

2.3. VisorALARM Expansion Card Connectors.......................................................................................60

2.4. AUX port Connections ......................................................................................................................61

3. TECHNICAL SPECIFICATIONS ......................................................................................................................61

4. UL COMPLIANCE INSTALLATION ................................................................................................................63

4.1. Requirements prior to installation....................................................................................................63

4.2. Installation requirements..................................................................................................................64

4.3. Configuration requirements..............................................................................................................65

5. ALARM PRINTING FORMAT .........................................................................................................................68

6. AUTOMATION SOFTWARE...........................................................................................................................69

6.1. Frame formats...................................................................................................................................69

6.2. SIS Software......................................................................................................................................71

Chapter 1

Introduction

VISORALARM - Introduction

I - 2 Doc.DM374-I

Ver. 1.0

1. VisorALARM PLUS 2U Introduction

The IP VisorALARM PLUS 2U receiver (Model VisorALARM PLUS 2U) isacommunications

device developed by Teldat for security environments. The IP VisorALARM PLUS 2U receiver’s

principal task is to receive alarms over an IP network and to subsequently send them to an automation

software (SwAut). The functionality of the Teldat VisorALARM PLUS 2U is similar to any other

alarm receiver which receives alarms over the telephone line.

The IP VisorALARM PLUS 2U receiver operates together with the IP Module (mIP/IPDACT), which

receives the alarms from the alarm control panels and sends them to the Teldat VisorALARM PLUS

2U over an IP network. Additionally, the Teldat VisorALARM PLUS 2U monitors connectivity with

all the registered mIP/IPDACTs. Should connectivity fail then the VisorALARM PLUS 2U generates

alarms to the SwAut.

The VisorALARM PLUS 2U IP receiver has the network backup functionality added, which permits

an mIP/IPDACT the possibility of IP backup towards another IP receiver. The main (or primary)

receiver and the backup receiver are always synchronized at the configuration level.

The VisorALARM PLUS 2U is supplied with adisplay and akeypad in order to validate the signals

received and monitor the device. The VisorALARM PLUS 2U includes interfaces to connect to an

Automation Software and to a printer.

The user can access to the device configuration through an asynchronous serial data connection by

using aserial terminal emulator. The configuration is atext level and permits the copy/paste

functionality.

Figure 1. VisorALARM PLUS 2U 2U Receiver

VISORALARM - Introduction

I - 3 Doc.DM374-I

Ver. 1.0

2. Installation Scenario

Atraditional security scenario consists of acontrol panel (CP), located in the client environment and

an alarm receiver center (ARC) located in the security company’s control center. The CP contains a

group of sensors which trigger a series of alarms or events which, when produced, are sent to the ARC

to be processed.

Communication between the above is traditionally carried out over the telephone line so that both ends

can initiate acall to the remote end: the CP in order to notify events and the ARC for bi-directional

tasks (activation, teleloading and general control).

Public Telephony

Switched Network

Alarm

Control Panel

Client

Alarm Receiver

Sur-Gard/Radionics Automation SW

IBS/ MAS/MicroKey

Fax

Alarm Receiver Center

Figure 2. Traditional security scenario

The communication protocol varies depending on the manufacturers who usually tend to use their own

solutions.

The CP is placed as the first connection element to the PSTN so that it can prioritize the customer’s

telephone line.

Within the general user scenario, the device in question is located in the client area, next to the control

panel, intercepting the telephone line. This is displayed in Figure 3. The arrow in the figure

demonstrates the preferred path to send alarms from the CP; in aBurglary application (using mIP

devices) the telephone line is used as abackup in case there is acommunication malfunction in the IP

network. In a Fire Application (using IPDACT devices) a second telephone line is used as a backup.

VISORALARM - Introduction

I - 4 Doc.DM374-I

Ver. 1.0

Figure 3. Teldat VisorALARM PLUS 2U and mIP/IPDACT operating scenario

There is athird scenario, thanks to the network backup functionality. In the previous scenario, if

communications between the IP Module and the VisorALARM PLUS 2U fails, the former tries to

send the alarms over the telephone network, as in atraditional scenario. Network backup permits you

to add a second VisorALARM PLUS 2U configured as backup and which would be a second option of

sending alarmsin cases where the main VisorALARM PLUS 2U fails. If the probe over the main

fails, the mIP/IPDACT (from release 2.2 onwards) tries to establish communications with the backup

VisorALARM PLUS 2U. If this is achieved, the mIP/IPDACT will maintain the probe with latter and

sends the alarmswhich are produced. In the meantime, the mIP/IPDACT continues to poll the main

VisorALARM PLUS 2U until this becomes accessible once more. At this point the mIP/IPDACT

returns from backup and reestablishes all the communications with the main VisorALARM PLUS 2U.

In cases where the backup VisorALARM PLUS 2U also fails, the mIP/IPDACT will release the

telephone line so that the control panel, from this point, will take over and directly sends the alarms.

VISORALARM - Introduction

I - 5 Doc.DM374-I

Ver. 1.0

It’s advisable that the VisorALARM PLUS 2U devices have different gateways and different Internet

access servers to ensure efficient network backup.

Figure 4. Operating scenario with network backup

VISORALARM - Introduction

I - 6 Doc.DM374-I

Ver. 1.0

3. Operating Mode

The IP Mode (mIP/IPDACT) connected to the client control panel carries out two tasks:

1) Capture the alarms sent by the control panel and send them over the IP network to which it is

connected. These alarms are then received by the Teldat VisorALARM PLUS 2U in order to

be sent to the corresponding automation software (SwAut).

2) Generate monitoring traffic so that both ends of the security environment check the IP

connectivity, as it is this that permits the above task to be carried out.

3.1. Monitoring

The mIP/IPDACT is adevice that intercepts the control panel telephone connection with two aims:

firstly to detect when the panel sends an alarm in order to capture it and retransmit over the connected

IP network and secondly to allow the telephone line to be used at the same time as sending alarms.

The interception of the telephone line takes place ONLY in cases where connectivity with the Teldat

VisorALARM PLUS 2U has been verified. The mIP/IPDACT - VisorALARM PLUS 2U connectivity

is checked through atraffic monitor which the mIP/IPDACT periodically sends and to which the

Teldat VisorALARM PLUS 2U responds. If this exchange of messages does not occur during the

configured time, the mIP/IPDACT tries to resend. If, after aconfigurable number of attempts

(between 1and 9),asatisfactory response is not received, the connectivity is presumed lost. The time

between polling messages is programmable between 0and 90 seconds, atypical value being 15

seconds. The time between retries is also configurable, between 3 and 9 seconds.

If anetwork backup scheme is running, the mIP/IPDACT has asecond IP receiver to establish

communications and send alarms. If this second receiver does not respond to the communication

established with it by the mIP/IPDACT (again after aconfigurable number of attempts), the telephone

line access is returned to the control panel as if the mIP/IPDACT is no longer operative at the alarm

level. Fromthis point on, the mIP/IPDACT will try to re-establish communications with both the

main Teldat VisorALARM PLUS 2U as well as the backup, if there is one. As soon as this is re-

established with either of the two VisorALARM PLUS 2U, the mIP/IPDACT will once more intercept

the telephone line.

The monitoring traffic is encrypted UDP traffic. The Ethernet frame size does not exceed 70 bytes.

The monitoring interval, the number of retries and time between retries are all configurable, both for

the main VisorALARM PLUS 2U as well as for the backup. The time between retries is an important

parameter as it influences the global traffic supported by the VisorALARM PLUS 2U (polling over all

the devices). You also need to bear in mind that polling is atool to control the state of both the alarm

reception center and the mIP/IPDACT. Along interval between polls can give rise to situations where

the VisorALARM PLUS 2U delays in detecting aproblem with the mIP/IPDACT and consequently a

problem in aclient. Finally, if the mIP/IPDACT accesses Internet via adevice which executes NAT,

traffic coming from the VisorALARM PLUS 2U (configuration for example) will not reach the

mIP/IPDACT if the period between polls is inferior to the outgoing router NAT tables refresh time (a

typical refresh value is 5 minutes).

The Teldat VisorALARM PLUS 2U received monitoring messages from the mIP/IPDACTs. If these

are registered, they are assumed alive and an acknowledgement response is sent to them;if the

mIP/IPDACTs are not registered, they are ignored. Periodically the status of all the registered

mIP/IPDACTs is checked and an alarm is generated for all those which have not notified their

availability (i.e. those which have not responded since the last check). This is a 350 code alarm from

the Contact-ID protocol (Communication trouble)which is received inthe SwAut. From release

10.1.27 onwards, the event code is configurable. Default is 350. As each mIP/IPDACT can have a

VISORALARM - Introduction

I - 7 Doc.DM374-I

Ver. 1.0

different polling time with the center, the VisorALARM PLUS 2U checks the status of each

mIP/IPDACT starting with the polling time value for all of them.

In order to prevent the Teldat VisorALARM PLUS 2U from sending hundreds or thousands of

communication failure alarms when faced with asituation of general failure of IP traffic reception, the

device itself monitors the network access through ICMP echo packets (ping) to a known address: if the

echo packets towards this address fail then a code 356 alarmis generated from the Contact-ID protocol

(Loss of central polling). From release 10.1.27 onwards, the event code is configurable. Default is

356.

Apart from the previous codes, the Teldat VisorALARM PLUS 2U with network backup functionality

generates other codes that do not directly correspond with those pre-established by the CONTACT-ID

protocol. These have default values which can be changed via the console.

Aseries of these codes are grouped indicating the states the VisorALARM PLUS 2U passes through.

The device configured as main on startup sends a396 restore code indicating that the device is active.

The device configured as backup must send code 398 restore code indicating that the device is active.

Once the main and backup VisorALARM are connected by polling, the main device sends a358

restore code to indicate the backup device is up and the backup device sends a399 restore code to

indicate the main device is up. Both the main and the backup VisorALARM PLUS 2U can have

communication problems (Loss of central polling) and consequently pass to a down state sending code

event 396 for main and 398 for backup. If the backup device detects communication failure with the

main device it will assume that as it cannot communicate with the VisorALARM PLUS 2U then nor

will the mIP/IPDACTs. The backup will then activate sending a 399 event code (Primary

VisorALARM is down) and the mIP/IPDACT polls should go to this device. Lastly, the main

VisorALARM PLUS 2U can detect and indicate through a358 code that the polls fromthe backup

VisorALARM PLUS 2U are not reaching it and consequently there is aproblemeither with

communications with the backup or with the main VisorALARM PLUS 2U device itself.

In addition to the above codes, we need to add a further two which provide information over particular

cases. If in the mIP/IPDACT configuration there is an error where the main address is in fact the

backup address, all communications from this mIP/IPDACT will be routing to the backup. The

backup device, through a395 code, will indicate this error by sending the code after each two

programmed keep-alives have been executed. The second case indicates asituation where an

mIP/IPDACT in backup is polling the backup device but this latter is not active, consequently there is

acommunication error between the mIP/IPDACT and the main VisorALARM PLUS 2U. This

problem is indicated with a 394 code.

3.2. Sending of Alarms

When the mIP/IPDACT has connectivity with the Teldat VisorALARM PLUS 2U, the former

intercepts the telephone line and processes all the incoming and outgoing calls taking place fromthe

alarm panel.

The supported alarm sending protocol is Contact-ID. This format sends alarms through DTMF digits

complying with the following format:

AAAA MM QEEE GG CCC S

where AAA is the client number, MM the type of message, Qan event qualifier, EEE the type of alarm,

GG the group or partition number, CCC the zone number and lastly Sis the frame validation digit.

When the panel opens to send an alarm, the mIP/IPDACT provides power and emits the dialing tone.

When the control panel dials the alarm center telephone number, it issues the Contact-ID handshake

and receives the alarm frame. From this point, the mIP/IPDACT sends this alarm to the

VisorALARM PLUS 2U.

VISORALARM - Introduction

I - 8 Doc.DM374-I

Ver. 1.0

The control panel is not given the frame sent acknowledgement (kissoff)until the said

acknowledgement is received from the automation software. Ifthe mIP/IPDACT does not receive the

acknowledgement within 2seconds, this carries on resending aconfigured number of times (between

5and 10), after which connection with the Teldat VisorALARM PLUS 2U is assumed lost. As in the

case of supervision where the alarm send fails, this can be sent again this time to the backup

VisorALARM PLUS 2U if this functionality is configured. If communications also fail with the

backup then the control panel sends the alarm over the telephone line. Fromthis point, the

mIP/IPDACT tries to re-establish communication with the two VisorALARM PLUS 2U as previously

described.

The IP VisorALARM PLUS 2U receiver on receiving an alarm from an mIP/IPDACT stores this in a

non-volatile internal memory. When the operation has successfully finished, it sends the

acknowledgement to the mIP/IPDACT originating the alarm so that this in turn sends to the associated

control panel. If the alarm storage memory cannot store the alarm, no acknowledgement is given.

As regards the SwAut, the Teldat VisorALARM PLUS 2U behaves as an alarm receiver that sends

alarms received through aserial port. The Teldat VisorALARM PLUS 2U can emulate aSur-Gard, a

Radionics 6500 receiver or an Ademco 685. The serial line parameters are configurable as well as

those relative to the emulated receiver (link-test, receiver and line identifier, start and end frame

characters, etc.)

Autres manuels pour VisorALARM PLUS 2U

Table des matières

Autres manuels Teldat Récepteur

Teldat

Teldat VisorALARM+ Manuel utilisateur

Manuels Récepteur populaires d'autres marques

Garmin

Garmin GA 23 Manuel utilisateur

Aiphone

Aiphone PS-12F Manuel utilisateur

IMES

IMES TCS-01CA-PMI Manuel utilisateur

BWI Eagle

BWI Eagle AIR-EAGLE SR Manuel

AMIMON

AMIMON AMN12310 WHDI Manuel utilisateur

Dual

Dual DMCPA79BT Mode d'emploi

Sound Associates

Sound Associates SA652P Manuel utilisateur

Sherwood

Sherwood NewCastle R-772 Manuel utilisateur

Audio

Audio A10-RX Series Manuel utilisateur

AllSee

AllSee PushShare PSRV1.1 Manuel utilisateur

DEMAG

DEMAG DRC-DR D2 Manuel utilisateur

Teleco

Teleco TVRCL868A02 Manuel utilisateur

Bosch

Bosch RF3222E Manuel utilisateur

Kramer

Kramer 631R Manuel utilisateur

Xpress

Xpress xmc10 Manuel utilisateur

JVC

JVC KD-MR1BTS Manuel utilisateur

Omega Engineering

Omega Engineering UWTC-REC3 Manuel utilisateur

e-survey

e-survey E300 Pro Manuel utilisateur