User's Manual

Overview 311

Figure 65

eCAP Connection tab

Because the eCAP is designed to handle asynchronous serial

communications with a number of alarm systems, the eCAP requires

configuration settings to start processing. These values are returned

through the <cfgrpy> reply that is sent on return of the <cfgrqs> request.

Some parameters refer to asynchronous communication settings (for

example, port number, baud rate, data bits, parity bits, stop bits, and so

on); others refer to general information settings (for example, logging

parameters); the rest are parameters that actually determine the alarm

system (for example, manufacturer, model, bidirectional, and so on).

Note: The values shown in Figure 65 "eCAP Connection tab" (page

311) are received from the DECT Messenger database: from the

eKERNEL_INPGM table, eCAP_generic table, and the eKERNEL_SITE

table.

At startup, the eCAP.exe appears the specified COM port with the

specified settings. The COM port specified must be available, be set

to use a valid baud rate, and so on. A physical connection must exist

between the specified COM port and the external alarm system through

a properly wired serial cable. In many cases, alarm systems support

a limited number of control signals (for example, ground and send),

so consult the alarm system vendor on cable specifications. In most

cases, you can use a standard null-modem cable. If no more COM ports

are available, extra hardware (such as DigiBoard PC/4e or DigiBoard

PC/8e) is needed to provide extra serial ports. Check compatibility issues

(supported by operating system, driver available, and so on) and hardware

requirements (memory, available slots, IRQ conflicts, and so on) before

ordering or configuring a system.

Nortel Communication Server 1000

DECT Messenger Installation and Commissioning — Book 1

NN43120-301 02.01 4 June 2010