alternative communication methods for access control

Alternative Communication

Methods

forAccess Control

Revision A, Part # 6600086

E X P L A I N I N G T H E T H R E E N O T E S Y M B O L S U S E D I N T H I S M A N U A L :

Explanatory Note. These notes are for your information, and ..pose no threat to equipment or life and limb.

Cautionary Note. These notes are for your information. Pay attention to these items, since system performance or function may be affected.

WARNING Note. These warning noted are to alert you to personal danger or serious loss of function or data. IT IS MANDATORY TO READ THESE NOTES AND PERFORM THE ACTIONS OR ATTEND TO THE WARNINGS CONTAINED WITHIN THEM.

Limited Warranty

NexWatch warrants to the original user the Equipment manufactured by NexWatch as described herein (the Equipment) to be free from defects in material and workmanship for a period of ninety days (90) days from the date of purchase provided:

I NexWatch has been notified within such period by return of any alleged defective equipment, free and clear of any liens and encumbrances to NexWatch or its authorized Dealer at the address specified, transportation prepaid; and

II the Equipment has not been abused, misused, or improperly maintained and/or repaired during such period; and

III such defect has not been caused by ordinary wear and tear; and

IV such defect is not a result of voltage surges/brownouts, lightning, water damage/flooding, fire, explosion, earthquakes, tornadoes, acts of aggression or war, or similar phenomena; and

V accessories used as integral to any NexWatch System have been approved by NexWatch (for example, coaxial cables and batteries); and

VI the Equipment has been installed, and the installation has been supervised or tested by an authorized NexWatch Dealer.

This guide contains proprietary information of NexWatch and its receipt or possession does not convey any rights to reproduce, disclose its contents, or to manufacture, use, or sell anything it may describe. Reproduction, disclosure, or use without specific written authorization of NexWatch is strictly forbidden.

RESTRICTED RIGHTS LEGEND Use, duplication, or disclosure by the Government is subject to restrictions as set forth in the subdivision (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013.

NexWatch47102 Mission Falls Court

Fremont, CA 94539-7818, USAwww.WSE.com

© 2001 NexWatchAll rights reserved. Printed in the United States of America.

NexSentry™ is a trademark of NexWatch.

Microsoft Windows NT® is a registered trademark of Microsoft Corporation.

. . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Contents

Explaining The Three Note Symbols Used In This Manual:.............ii

1 Alternative Communication Methods for Access Control ...........1-1History ...............................................................................................1-1Purpose...............................................................................................1-2

2 Dial-Up Interfacing Methods ..........................................................2-1Introduction........................................................................................2-1StarGaze Dial-Up Configuration .......................................................2-2

4100 / Star I Configuration for StarGaze Dial-Up...................................... 2-2Dialer Poller Configuration ......................................................................... 2-3Device (ACU) Configuration....................................................................... 2-4StarGaze Dialer Configuration .................................................................... 2-5

How to Make an ACU Dial Out on Alarm Log.................................2-9NexSentry Manager 3.0 Dial-Up Configuration................................2-10

4100 / Star I Configuration for NSM Dial-Up............................................. 2-10Star II Configuration for NSM Dial-Up ..................................................... 2-11NSM Poller Configuration........................................................................... 2-114100 / Star I / Star II Configuration for NSM Dial-Up ............................... 2-144100 / Star I / Star II Configuration, Dial-Up Page ..................................... 2-16

MODEM Configurations ...................................................................2-19Host End AND 4100 / Star I (SEEP) Modem DIP Switches...................... 2-19Star II (CHIP) Modem DIP Switches ......................................................... 2-20Modem Firmware Commands for All Configurations ................................ 2-21

3 Ethernet with CoBox .......................................................................3-1Introduction........................................................................................3-1StarGaze with CoBox Ethernet Interface...........................................3-1NexSentry Manager with CoBox Ethernet Interface .........................3-3

Revision A, Part Number 6600086 Alternative Communication Methods C-i

C O N T E N T S

General CoBox Application Basics and Requirements .....................3-4CoBox Configuration for SEEP Poller Applications.........................3-7

SEEP Protocol (4200 / Star I) Master CoBox.............................................. 3-7SEEP (4100 / Star I) Slave CoBox .............................................................. 3-9

CoBox Configuration for CHIP Poller Applications .........................3-12CHIP Protocol (Star II) Master CoBox........................................................ 3-12CHIP (Star II) Slave CoBox ........................................................................ 3-15

Micro Cobox Initial Configuration Steps ..........................................3-18

C-ii Alternative Communicztion Methods Revision A, Part Number 6600086

. . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .List of Figures

StarGaze Poller Configuration - Configuration Tab.............. 2-3

StarGaze Device (ACU) Configuration - Configuration Tab........ 2-4StarGaze Dialer Configuration - Dial Info Tab.................. 2-6StarGaze Dialer Configuration - Alarm Activity Tab............. 2-7StarGaze Dialer Configuration - Call Activity Tab.............. 2-8REPORT (Action) Configuration for Alarm Event Dial-out......... 2-10NSM 3.0 Poller Configuration - Communications Tab.............. 2-124100 / Star I, Star II ACU Config Data - Dial-Up Comm Tab...... 2-14ACU Config Data - Dial-Up Communication Tab.................... 2-16ACU Config Data - Dial-Up Communication Tab.................... 2-17StarGaze Ethernet LAN/WAN Communication Example................ 3-2

Revision A, Part Number 6600086 Alternative Communication Methods F-i

L I S T O F F I G U R E S

F-ii Alternative Communication Methods Revision A, Part Number 6600086

. . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .List of Tables

4100 / Star I Configuration for Dial-Up with StarGaze.......... 2-2

StarGaze Poller Configuration for Dial-Up...................... 2-4Device (ACU) Configuration for Dial-Up with StarGaze........... 2-5StarGaze Dialer Configuration - Alarm Activity Tab............. 2-7StarGaze Dialer Configuration - Call Activity Tab.............. 2-84100 / Star I Configuration for Dial-Up with StarGaze.......... 2-10Star II Configuration for Dial-Up with StarGaze................ 2-11NSM 3.0 Poller - Configuration Tab............................. 2-124100 / Star I / Star II ACU Configuration Data - General Tab... 2-15ACU Configuration Data: Dial-Up Comm. Tab...................... 2-16ACU Configuration Data: ACU Dial-Up Tab........................ 2-18DIP SWITCH Settings for HOST & SEEP ACU Modems...... .......... 2-19DIP SWITCH Settings for CHIP ACU Modems........................ 2-20Modem Firmware Commands for All Configurations................. 2-21SEEP Protocol (4200 / Star I) Master CoBox..................... 3-7SEEP (4100 / Star I) Slave CoBox............................... 3-9CHIP Protocol (Star II) Master Cobox........................... 3-12Chip (Star II) Slave CoBox..................................... 3-15

Revision A, Part Number 6600086 Alternative Communication Methods C-i

L I S T O F TA B L E S

T-ii Alternative Communication Methods Revision A, Part Number 6600086

ALTERNATIVE COMMUNICATION METHODS

. . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .FOR ACCESS CONTROL 1

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .H I S T O R Y

In the early days of Access Control systems, all subsystems were hard wired together.

The distance limitations of RS-232, 20mA loop and later, RS-485 confined a system to a finite radius, such as a single building or at most a small cluster of buildings. Although some installations employed dedicated line modems and line-drivers to extend the scope of a system, this was usually at a significant additional cost.

As the need to extend the area covered by an enterprise system has continued to grow, two additional means of Host-to-Controller communication have been employed.

• Dial-Up over public telephone networks

• Corporate Ethernet networks - LAN/WAN

Revision A, Part Number 6600086 Alternative Communication Methods 1-1

A L T E R N A T I V E C O M M U N I C A T I O N M E T H O D S F O R A C C E S S C O N T R O L1

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .P U R P O S E

The purpose of this document is to explain the necessary methods to enable both Dial-Up and Ethernet communications for the following Hosts

and for these Access Control Units:

All configuration aspects of Host, Controller and accessories will be covered.

• StarGaze LINUX Host System

• NexSentry Manager Windows NT Host System

• Star II (CHIP Protocol) Controllers

• 4100 and Star I (SEEP Protocol) Controllers

• Alto 818SX and 818SC ACUs (Ethernet Only)

1-2 Alternative Communication Methods Revision A, Part Number 6600086

. . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .DIAL-UP INTERFACING METHODS 2

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I N T R O D U C T I O N

Dial-Up communication between the Host and one or more controllers offers many advantages.

The biggest single disadvantage of dial-up communication is the lag time between an alarm event occurring and its display at the Host. The ACU must dial the Host, establish the link and deliver the log. This can take many seconds, or may even be buffered until the next opportunity for this ACU to connect if the Host is already talking with another ACU at the moment.

Dial-Up is most often used where the security level is relatively low, and the amount of traffic through the controller is relatively small. It is desirable where cost reduction outweighs security considerations.

• Inexpensive communication link

• Configurable Dial-Up times for both Host and Controller

• Buffering of Controller activity (up to 5000 logs) in the event of communication failure until communication is restored.

• ACU Dial-out threshold at a specified number of logs in the buffer. Dial-out on Alarm Event log.

• Operator Override connection if an immediate update is required from an ACU.


D I A L - U P I N T E R F A C I N G M E T H O D SStarGaze Dial-Up Configuration

2

S T A R G A Z E D I A L - U P

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C O N F I G U R A T I O N

410 0 / S t ar I Conf i gur at ion f or S t arG aze Dia l - UpAt this time, Dial-Up communication in the StarGaze is supported only for 4100 family controllers and the Star I. It is necessary to log into the ACU directly in the Terminal Mode and set the Address, Serial Number and Modem Initialization String These items should

be set as follows:

NOTE: SE 6000 and NexSentry Command Center systems supported an intermediate device called an RDI to allow Dial-Up to 808/818 ACUs. StarGaze can also support the RDI, but it will not be covered here. Contact NexWatch Technical Support for details.

4100 / Star I Configuration for Dial-Up with StarGaze..........

Address Always set to 1 for Dial-Up applications. (In SYSTEM Command or DIP Switches)

Modem Init. String The default of ATZ is correct for most applications. Enter something else ONLY if a local phone system requires it. (In MODEM Command)

Serial Number Must be set for each ACU in sequential order, typically beginning with 1. In StarGaze, the Computer Number for each ACU will be set to match this Serial Number as shown below. (In MODEM Command)


. . .

. .D I A L - U P I N T E R F A C I N G M E T H O D SStarGaze Dial-Up Configuration

Dia ler Po l l er Co nf ig urat i onBefore you can configure any Dial-Up ACUs, you must first have at least one Dialer Poller. This Poller must first be built by NexWatch Engineering or Technical Support personnel at the LINUX root level. This can be done before a new system is delivered or by dial-in through the diagnostic modem if an existing system is being upgraded. There is a cost associated with this feature in both cases.

Once the root level work is done, a corresponding Poller record must be created for it. The following example will show how to do that.

StarGaze Poller Configuration - Configuration Tab..............

.....



2

Devi ce (ACU) Con f i gu rat io n

StarGaze Device (ACU) Configuration - Configuration Tab.............

StarGaze Poller Configuration for Dial-Up......................

ID and Description If possible, use the ID Number that matches the actual Poller Number as described below. The description should simply be a logical name for the poller, based on its purpose and location.

Computer Number Must be set to 0, since only the Server can control Dial-Up ACUs.

Poller Number Always set to match the root level Poller that was set up by NexWatch personnel.

Poller Type Select Remote Dialer Scheduler.


. . .


St arGa ze Dia ler Co nf ig urat i onThe Dialer program is the part of StarGaze that handles the actual Dial-Up communication to and from the ACU. It sets up at what times and under what conditions both the Star Gaze Host and the individual ACUs will initiate a Dial-Up connection. It also displays statistics about the successful or failed communication attempts by the Host. Each Dial-Up ACU will have a corresponding Dialer record, so that for 24 Dial-Up ACUs there will be 24 Dialer records.

ACUs that are connected by direct wiring, or by Ethernet will not need any Dialer records.

The following three Dialog boxes will establish the details of this function.

Device (ACU) Configuration for Dial-Up with StarGaze...........

Computer Number (= Serial Number)

Must be set for each ACU in sequential order, typically beginning with 1. A matching number will be entered in the MODEM Command for each ACU as the Serial Number. NOTE: If there are any Local Controllers (LCs), they will occupy Computer Numbers 1-X where X is the final LC. The ACU Computer Numbers must come after any LC Numbers.

Poller Number Always set to match the StarGaze Poller that will handle this individual ACU.

Address Always set to 1 for Dial-Up applications.



2

StarGaze Dialer Configuration - Dial Info Tab..................


. . .


StarGaze Dialer Configuration - Alarm Activity Tab.............

StarGaze Dialer Configuration - Alarm Activity Tab.............

No Activity Disconnect

Enter the number of seconds for the poller to remain connected with no data coming from the ACU.

Call when Alarm Occurs (Y/N)

Should the ACU Dial immediately to the Host if an Alarm event occurs? NOTE: RLC/RDI are seldom used with StarGaze but the description remains.

Dial Back (Y/N) For Future Use.

Number of Transactions to Hold

This value is downloaded into the ACU to set its Buffer size. If the threshold is reached before the next scheduled Dial-Back, the ACU will dial back immediately and allow the StarGaze to extract the logs in the ACU’s buffer. This should be set based upon anticipated ACU traffic. 10 might be good for a remote Cell-tower site while 2500 makes sense for a busy remote office building.



2

StarGaze Dialer Configuration - Call Activity Tab..............

.....

StarGaze Dialer Configuration - Call Activity Tab..............

Host Retry Enter the number of minutes StarGaze should wait to try to dial out again after a failed attempt.

Min Enter the minimum number of minutes for StarGaze to wait to dial an ACU after a successful attempt.

Max Enter the maximum number of minutes for StarGaze to wait to dial an ACU after a successful attempt.

Next Scheduled Call Enter a specific Date and Time for a special Dial-out.


. . .

. .D I A L - U P I N T E R F A C I N G M E T H O D SHow to Make an ACU Dial Out on Alarm Log

If all of the above steps are accurately completed, the StarGaze will successfully communicate with its remote ACUs.

H O W T O M A K E A N A C U D I A L

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .O U T O N A L A R M L O G

In either StarGaze or NSM, it is necessary to configure the ACU REPORT (Action) to trigger an immediate dial. This is done in the REPORT (Action) configuration screen by checking the folder labeled Print Asterisk. If this is checked, the lead character of an ACU REPORT will be the Asterisk and it will cause the ACU to immediately execute its Modem Dial-out routine.

Last Call StatisticsDate and Time

Date and Time of the last successful Host-to-ACU communication.

Statistics:Type

H = Host originated call.R = Remote ACU originated call.

Count Indicates the number of logs uploaded from the ACU in this call.

Number of Failed call attempts

The number of attempts by the Host to Dial Out to the ACU. This usually indicates a Modem or ACU problem at the Remote ACU location.


D I A L - U P I N T E R F A C I N G M E T H O D SNexSentry Manager 3.0 Dial-Up Configuration

2

REPORT (Action) Configuration for Alarm Event Dial-out.........

This works identically for the 4100 family, and the Star I and Star II ACUs.

N E X S E N T R Y M A N A G E R 3 . 0 D I A L -

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .U P C O N F I G U R A T I O N

410 0 / S t ar I Conf i gu rat ion f or NSM Dia l - UpNexSentry Manager 3.0 supports Dial-Up communication for 4100 family controllers, the Star I and Star II. For 4100 and Star I, it is necessary to log into the ACU directly in the Terminal Mode and set the Address, Serial Number and Modem Initialization String These items should be set as follows:

4100 / Star I Configuration for Dial-Up with StarGaze..........

Address Always set to 1 for Dial-Up applications. (In SYSTEM Command or DIP Switches)

Modem Init. String The default of ATZ is correct for most applications. Enter something else ONLY if a local phone system requires it. (In MODEM Command)


. . .

. .D I A L - U P I N T E R F A C I N G M E T H O D SNexSentry Manager 3.0 Dial-Up Configuration

St ar I I Con f i gu rat io n f or NS M Di a l -UpThe Star II controller has a much simpler preparation for Dial-Up use with NSM. All that is necessary is to set the Address DIP Switches. Everything else is downloaded from the NSM Host.

NSM Po l l er Con f i gu rat io nThe first step for the NSM is to set up a dialer Poller. The Dialog box shown below and the field explanations will give you enough details to accomplish this step

Serial Number Must be set for each ACU in sequential order, The Serial Number should match the Address number that will be entered in the NSM ACU config.

Star II Configuration for Dial-Up with StarGaze................

Address Set to match the Address (1 - 32) that will be entered in the NSM ACU Configuration. (In DIP Switches)



2

NSM 3.0 Poller Configuration - Communications Tab...............

NSM 3.0 Poller - Configuration Tab.............................

Poller Type Select one of the two available Dial-Up Poller types. Make sure that the SEEP or CHIP type matches the ACUs you are using. SEEP and CHIP units cannot be combined on any single Dial-Up (or direct connect) Poller.

Dial-Up Parameters Only

Phone Number Enter the Phone Number for the Poller. This is the number that an ACU will use to Dial TO the NSM.

Modem Init. String The default of ATZ ATZ is correct for most applications. Enter something else ONLY if a local phone system requires it.


. . .


Idle Timeout The default value is ideal for most applications. This should only be changed after consulting NexWatch Engineering or Technical Support.

Answer Timeout The default value is ideal for most applications. This should only be changed after consulting NexWatch Engineering or Technical Support.

Read Retries The default value is ideal for most applications. This should only be changed after consulting NexWatch Engineering or Technical Support.

For ALL Pollers, Dial-Up and Direct connect

Port Select the PC Serial port that will be used for connection to the Host Modem.

Baud Select the desired Baud rate for ACU Commun-ication, 9600 or 19,200 (if supported).NOTE: ALL ACUs on the poller must be set to the same baud rate as the Poller itself.

Acknowledge Timeout

This is the number of seconds that the NSM server will wait for a response from an ACU before deter-mining it to be off line. the default is 2 seconds.

Number of Retries This is how many times the Server must detect the ACU to be off-line before sending a log message to the Monitor window. The default is 1.

Shunted If checked, the Poller is shunted. All communi-cation to ACUs will be terminated. (The ACUs will store real-time activity in their local buffers until the buffers reach their limits.)



2

410 0 / S t ar I / S ta r I I Conf i gura t i on fo r NSM Dia l - UpOn an NSM system, the Star II Controller can support Dial-Up communication in a new and more powerful way. In order to use this feature, you must first configure a Star II (CHIP) Dial-Up Poller as shown above. Remember that Star II (CHIP protocol) Controllers cannot be mixed with any other kinds of ACUs (SEEP) on the same Poller. The screens below will detail the configuration of the Dial-Up portion of a Star II

Be sure to pay close attention to the Address and Serial Number fields on the General Tab. They are critical in establishing Dial-Up communication with the NSM Server.

CAUTIONARY NOTE: The Address and Serial Number fields function very differently between CHIP Protocol Star II Controllers and the SEEP Protocol 4100 and Star I. Be extremely careful to configure both types correctly.

4100 / Star I, Star II ACU Config Data - Dial-Up Comm Tab......


. . .


4100 / Star I / Star II ACU Configuration Data - General Tab...

ID Number Enter the ID # for the ACU. There is no absolutely logical choice since this ID # is only for use by NSM to organize its Database. See Numbering Scheme logic in the NSM Manual, Chapter 2.

Description Enter a descriptive name for the ACU.Shunt A check box to enable NSM to stop polling the

ACU. This is normally used when you are building the database while your PC is not connected to the ACU. Don’t forget to Unshunt !

Address In 4100, Star I AND Star II, the Address is set the same as if the ACU were directly connected. For example, if ACUs 1 - 6 were hard wired and 7-10 are Dial-Up, then the first Dial-Up Star II would have Address 7, and so on. NOTE: This is different from the procedure in StarGaze.

Serial Number Set the Serial Number to match the Address entered above.For 4100 / Star I, this WILL match what was configured in the ACU. For Star II, the value is unimportant but must be entered to satisfy the NSM database.

Poller Select the proper Dial-Up Poller you created from the drop-list.

Instruction Select a previously created Instruction from the Drop-box if desired.



2

410 0 / S t ar I / S ta r I I Conf i gura t i on , D ia l - Up P age

ACU Config Data - Dial-Up Communication Tab....................

Host Login(Star II Only)

Select a Host Login name and Password for the NSM to use in connecting to the Star II ACUs. Use the default unless there is a compelling reason to do otherwise.

ACU Configuration Data: Dial-Up Comm. Tab......................

Enable Call Back For Future use.

ACU’s Phone number

Enter the Telephone Number for the location of the ACU. This is the number that the NSM will dial to reach the ACU.


. . .


ACU Config Data - Dial-Up Communication Tab....................

Dial Daily at: Check this box (if desired) and enter the Time of Day that the NSM Server will dial out to the ACU.

Dial Interval Enter the number of minutes between NSM attempts to dial out to the ACU. Enter 0 (zero) if there should be no repeated attempts to dial out.

Modem Init String(Star II Only)

This is the character string that the Star II will send to the Modem to begin a call-out to the NSM Server. DO NOT CHANGE THIS VALUE without ask-ing NexWatch Engineering or Technical Support.This field does not appear in 4100/Star I set-up.

ACU to Server Dialing Config.

Click here to open the window shown below.

Dialing Statistics These fields will display the time and date of the last successful communication between the NSM and ACU (and any failed attempts).



2

ACU Configuration Data: ACU Dial-Up Tab........................

First PollerSecond PollerThird Poller

Each ACU may attempt to connect, in order, to as many as three Pollers. Select one or more Pollers from the Drop-down boxes. In most applications, ONE Poller is sufficient.

Retry Count Enter the number of times that the ACU will attempt to dial the NSM Server before giving up. If the ACU fails to connect on one set of attempts, it will try again the next scheduled or event-triggered time. Nothing will be lost from the ACU Buffer due to a failed try. The default is 4, (which is a good choice).

Answer Timeout Enter the number of seconds for the Modem to wait to be answered. 30 - 60 seconds is a good range.

Dial Threshhold Enter the maximum number of logs for the ACU to store in its buffer before dialing out to the NSM Server. Star II Controllers can hold 5,000 logs in a buffer. Star I and 4100 models can hold 4,000 logs.

The more activity that will occur at a given remote site, the larger this value should be. For the door to a Cellular Telephone tower, the threshold might be 10. For a remote service center, 2500 might be reasonable.


. . .

. .D I A L - U P I N T E R F A C I N G M E T H O D SMODEM Configurations

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .M O D E M C O N F I G U R A T I O N S

NexWatch recommends the use of US Robotics (3 Com) 56K External Fax-Modems. The following Setup instructions are based on that model. Other Modems may perform well, but NexWatch is unable to offer advice on their configurations.

You will need to connect the RS-232 port on the Modem to your PC in order to configure the Modem for use. Use a NULL Modem (TX/RX Crossover) Cable for this purpose.

Host End AND 4 100 / S t ar I ( S EEP ) Mod em DIP Swi tch es

DIP SWITCH Settings for HOST & SEEP ACU Modems...... ..........

Sw. 1 - Up DTR normal.

Sw. 2 - Up Verbal Result Codes.

Sw. 3 - Down Display Result Codes.

Sw. 4 - Down No Echo, Offline commands.

Sw. 5 - Up Auto-Answer on first ring.

Sw. 6 - Up Carrier Detect Normal.

Sw. 7 - Up Load NVRAM default.

Sw. 8 - Down Modem Smart Mode.


D I A L - U P I N T E R F A C I N G M E T H O D SMODEM Configurations

2

St ar I I ( CHIP) Mod em DIP S wi t ch es

DIP SWITCH Settings for CHIP ACU Modems........................

Sw. 1 - Down Ignore DTR. (Different from 4100/Star I)

Sw. 2 - Up Verbal Result Codes.

Sw. 3 - Down Display Result Codes.

Sw. 4 - Down No Echo, Offline commands.

Sw. 5 - Down Answer on ACU command. (Diff. frm 4100/Star I)

Sw. 6 - Up Carrier Detect Normal.

Sw. 7 - Up Load NVRAM default.

Sw. 8 - Down Modem Smart Mode.


. . .

. .D I A L - U P I N T E R F A C I N G M E T H O D SMODEM Configurations

Mo dem Fi rmware Co mman ds f or Al l Co nf ig ura t i on s

Modem Firmware Commands for All Configurations.................

ATZ (OK) Modem is Working.

AT&F (OK) Reset the Modem.

ATE0 (OK) Echo turned off.

ATS32=24 (OK) VIS-32 Mode Turned ON.

AT&B1 (OK) Select fixed Serial Port.

AT&U1 (OK) Lowest connection speed = 300 Baud.

AT&N6 (OK)OR AT&N10 (OK)

Highest Connection Speed = 9600 Baud.Highest Connection Speed = 19,200 Baud.

ATY0 (OK) Power-on Reset config. set to Profile 0 in NVRAM.

AT&W0 (OK) Write current config. to Profile 0 in NVRAM.


D I A L - U P I N T E R F A C I N G M E T H O D SMODEM Configurations

2


. . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .ETHERNET WITH COBOX 3

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I N T R O D U C T I O N

Many companies have employed electronic communication with Ethernet in a Local Area Network (LAN) or Wide Area Network (WAN) to allow their computers to exchange data. The same network can be used by an Access Control Host computer to talk to remote ACUs. Our concern is not with the Ethernet structure itself, but with the configuration and use of the CoBox devices that allow communication on the Ethernet.

Both StarGaze and NexSentry Manager are able to communicate via CoBoxes, but they approach it in slightly different ways.

S T A R G A Z E W I T H C O B O X

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .E T H E R N E T I N T E R F A C E

StarGaze, like the SE 6000 and NexSentry Command Center, employs a DigiBox Terminal Server for connection to field devices. The DigiBox allows the large number of cables to be remoted from the PC itself for easier access and servicing. Each DigiBox has 8 or 16 serial ports, all configured in software to communicate using RS-232 protocol.

In an Ethernet application, one of the DigiBox ports that has been assigned to an 808 class (Type 6) Poller will be connected to a CoBox that has been configured as a Master. The CoBox will receive the RS-232 protocol messages, being sent from the DigiBox,


E T H E R N E T W I T H C O B O XStarGaze with CoBox Ethernet Interface

3

to up to 16 ACUs in the field, and convert the signals to TCP/IP Ethernet protocol.

Tte following diagram is a composite example of CoBox applica-tions, including a Master, one Slave and two Micro-CoBoxes. (This typifies the majority of LAN/WAN Ethernet installations.)

StarGaze Ethernet LAN/WAN Communication Example................


. . .

. .E T H E R N E T W I T H C O B O XNexSentry Manager with CoBox Ethernet Interface

CoBox configuration for Master, Slave and Micro versions will be covered in detail later in this document. The set-up is the same for both StarGaze and NSM applications.

N E X S E N T R Y M A N A G E R W I T H

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C O B O X E T H E R N E T I N T E R F A C E

A drawing of an NSM system using CoBoxes would be almost identical to the one for StarGaze with two exceptions:

Because of this similarity, we will not include a separate drawing for an NSM application. Note that the CoBox configuration for Star II using the CHIP protocol is different from a SEEP configuration used with 4100 and Star I ACUs. This applies to Master, Slave and Micro CoBox models.

• NSM can handle the Star II Controller, (although a separate Poller is required),

• The Master CoBox connects directly to a serial port on the PC. (There is no DigiBox.)


E T H E R N E T W I T H C O B O XGeneral CoBox Application Basics and Requirements

3

G E N E R A L C O B O X A P P L I C A T I O N

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B A S I C S A N D R E Q U I R E M E N T S

There are three models of Lantronics CoBoxes that you may use on a StarGaze or NSM system. All three are delivered standard with a NexWatch (WSE) interface capability.

Each CoBox unit must be configured individually using a terminal or terminal emulator (HyperTerminal, etc.) for its specific application. Before beginning, you will need to have the following information:

The customer’s IT department will also need to configure any routers and/or bridges in the network to handle the CoBox traffic.

These instructions may seem complex the first one or two times you use them, but will quickly become routine. CoBox configuration takes an experienced technician less than 5 minutes after the learning curve is over.

• E2 - (SEEP only with standard firmware) - for Master and Slave applications

• FL - (SEEP and CHIP) - for Master and Slave applications

• Micro - (SEEP and CHIP) - for Slave applications only

• IP Addresses for each CoBox unit. (from the customer’s IT Department.)

• Addresses of each of the ACUs to be connected via TCP/IP. The Address range is 1 - 16. This matches the maximum number of ACUs that can be connected to a single Poller port.

• The baud rate at which the Poller and all ACUs are to be run.


. . .

. .E T H E R N E T W I T H C O B O XGeneral CoBox Application Basics and Requirements

A cable will be required to communicate from the PC Serial port to the Channel 1 port on the CoBox. This is a NULL Modem Cable.

With these facts and tools available, you are ready to begin. The connections and initial steps are identical for all CoBox models. Connect the Modem cable from the PC to the CoBox. For the Micro CoBox, connect the cable to the TERMINAL port of the Star Controller. (Make sure your TERMINAL Port baud rate matches the configuration of your Terminal emulator. This will default to 9600 baud.)

To start configuring either the E2 or FL models, it is necessary to follow this simple procedure:

• The cable is typically 9-Pin Female to 25-Pin Male for E2 and FL models. The pinouts from the PC to CoBox are: 2-2 3-3 5-7

• For Micro CoBox units, communication is through the Star Controller’s Terminal Port. This is a 9-Pin Male connector so the cable will be 9-Pin Female to 9-Pin Female, with the following pinouts: 2-3 3-2 5-5

• Have the power supply ready to plug into the CoBox.

• Press and hold the x (lower case) key on your PC keyboard.

• Quickly connect the power supply cable to the CoBox.

• As soon as you see characters on your monitor, release the x key.


E T H E R N E T W I T H C O B O XGeneral CoBox Application Basics and Requirements

3

The CoBox will respond with the following text:

*** ACOLA CoBox 2-Channel1 ***Serial Number 149-184 Software Version 04.3d (981027)

Press Enter to go into Setup Mode

When you press Enter, the CoBox will dump its current configuration to the monitor. The display will begin like this:

IP addr 194.039.078.254. no gateway set

and go down through:

Change Setup (0 Basics, 1 or 2 for Channel, 8 exit, 9 save andexit)?

From this point onward, the configuration instructions are unique for Master or Slave, and CHIP or SEEP applications.


. . .

. .E T H E R N E T W I T H C O B O XCoBox Configuration for SEEP Poller Applications

C O B O X C O N F I G U R A T I O N F O R

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .S E E P P O L L E R A P P L I C A T I O N S

SEEP Prot oco l ( 42 00 / S t ar I ) Mas ter CoBox

SEEP Protocol (4200 / Star I) Master CoBox.....................

Enter Press <0>

Ethernet Interface AUI N (default)

IP Address - first second third fourthfor the MASTER!

AAA(AAA).BBB(AAA).(BBB).CCC(AAA).(BBB).(CCC).DDDExample: 206.171.021.165

Set Gateway IP Address N (default) - if Master and Slave are on the same network.Y - if Master and Slave are on different networks. IT Dept. must provide IP Addresses for routers.

Gateway IP Address(Only appears if answer Y above.)

Enter in four segments like CoBox IP Address above.

Netmask: Number of bits for Host Port (0=default)

Press Enter to accept the default.NOTE: a small number of applications may require a different value. IT Dept. expertise is required to determine an alternate entry.

Change telnet config password N (default)

Channel 1 Configuration


E T H E R N E T W I T H C O B O XCoBox Configuration for SEEP Poller Applications

3

Baudrate (09600) Press Enter to accept the default.Other Baudrates may be entered up to the max. supported by remote ACUs.

I/F Mode - RS-232, 7/odd/1 58

Flow (00) Press Enter to accept the default.

Port (10001) Press Enter to accept the default.NOTE: A Master and all of its Slaves must have the same Port #. If more than one Master/Slave set is to be used, each set will require a unique Port #, 10002, 10003, etc.

Connect Mode (C0) 0c

Datagram Type (00) fc (Sets this CoBox as a Master)

Remote Port Use the same number entered above.10001 is the default.

Pack Cntrl (00) Press Enter to accept the default.

SendChar 1 (00) 59

SendChar 2 (00) 20 (The Main Menu will reappear.)

Channel 2 ConfigurationNOTE: Micro CoBox does not have Chan. 2.

For all currently supported applications, Channel 2 is unused and must be disabled. Future enhancements will be able to use this port. Press Enter down to “Port”.

Port (10001) 56789 (or any value that is different from the Channel 1 Port setting.


. . .


SEEP (41 00 / S t ar I ) S la ve CoBox

Press Enter to until you return to the Setup Menu. (The Main Menu will reappear.)

Finish ConfigurationExit and Save <9> Enter to exit and save.

Parameters Stored message appears.

SEEP (4100 / Star I) Slave CoBox...............................

Enter Press <0>


IP Address - first second third fourthfor this SLAVE!






E T H E R N E T W I T H C O B O XCoBox Configuration for SEEP Poller Applications

3




Channel 1 ConfigurationBaudrate (09600) Press Enter to accept the default.

Other Baudrates may be entered up to the maximum supported by the remote ACUs..

I/F Mode - RS-232, 7/odd/1 RS-485, 7/odd/1

585B




Datagram Type (00) fd (Sets this CoBox as a Slave)

Change address table(Max. 16, 00 = disable)

Y The Address table as shown in the following example will open. Enter the addresses in 1-N order as shown.


. . .


#01 (001) :#02 (004) :#03 (005) :#04 (000) :#05 (000) :

001 (Existing)004 (Existing)005 (Existing)009 (Newly added)016 (Newly added)(This Slave Co-Box will now support ACUs #1, 4, 5, 9 and 16.)



SendChar 1 (00) 0d

SendChar 2 (00) 20 (The Main Menu will reappear.)




Press Enter to until you return to the Setup Menu.




E T H E R N E T W I T H C O B O XCoBox Configuration for CHIP Poller Applications

3

C O B O X C O N F I G U R A T I O N F O R

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C H I P P O L L E R A P P L I C A T I O N S

CHIP Protoco l (S tar I I ) Mas ter Co Bo x

CHIP Protocol (Star II) Master Cobox...........................

Enter Press <0>


IP Address - first second third fourthfor the MASTER!










. . .

. .E T H E R N E T W I T H C O B O XCoBox Configuration for CHIP Poller Applications

Baudrate (09600) Press Enter to accept the default.Other Baudrates may be entered up to the maximum supported by the remote ACUs.

I/F Mode - RS-232, 8/none/1 4C




Datagram Type (00) 80 (Sets CoBox = CHIP Master)

Master Config 01 - 10 - 21 - 00 - 00 - 00 - 00 -

0b480000000000



SendChar 1 (00) Press Enter to accept the default.

SendChar 2 (00) Press Enter to accept the default. (The Main Menu will reappear.)



3

CAUTIONARY NOTE: Items printed in RED and ‘boxed’ for emphasis are unique for CHIP Poller CoBox Setup. Be especially careful to correctly enter this data.




Press Enter to until you return to the Setup Menu. (The Main Menu will reappear.)




. . .


CHIP (S ta r I I ) S lave Co Box

Chip (Star II) Slave CoBox.....................................

Enter Press <0>


IP Address - first second third fourthfor this SLAVE






Press Enter to accept the default.

NOTE: a small number of applications may require a different value. IT Dept. expertise is required to determine an alternate entry.


Channel 1 ConfigurationBaudrate (09600) Press Enter to accept the default.

If 19,200 is to be used by the Host and ACUs, enter that value as 19200.



3

I/F Mode - RS-232, 8/none/1 RS-485, 8/none/1

4C4F



Connect Mode (C0) 0C

Datagram Type (00) fd (Sets this CoBox as a Slave)

Change address table(Max. 16, 00 = disable)

Y The Address table as shown in the following example will open. Enter the addresses in 1-N order as shown.

#01 (001) :#02 (002) :#03 (005) :#04 (000) :#05 (000) :

001 (Existing)002 (Existing)005 (Existing)007 (Newly added)016 (Newly added)(This Slave Co-Box will now support ACUs #1, 2, 5, 7 and 16.)


Pack Cntrl (00) Press Enter to accept the default, 00.

SendChar 1 (00) Press Enter to accept the default, 00.

SendChar 2 (00) Press Enter to accept the default, 00. (The Main Menu will reappear.)



. . .




Press Enter to until you return to the Setup Menu.




E T H E R N E T W I T H C O B O XMicro Cobox Initial Configuration Steps

3

M I C R O C O B O X I N I T I A L

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C O N F I G U R A T I O N S T E P S

NOTE: To configure the Micro CoBox, it is first necessary to establish terminal mode communication with the Star II Controller. Set your Terminal Emulator to 8/none/1 at a baud rate that matches the DIP Switch settings for the Terminal Port (default is 9600).

Proceed as follows:

• Log on by pressing <Esc>.

• Login Name is operator1

• Password is new

• Choose item 2 from the first menu

• Choose item 17 from the second menu

• Hold down the x key as soon as characters begin appearing on the screen.

• Press <Enter> two or three times as soon as the text scroll says to do it.


alternative communication methods for access control

Documents