EBI R610.1 StarII

NexSentry Star II: A Step by Step Guide
July 2019
Issue 2
DISCLAIMER
This document contains Honeywell proprietary information. Information
contained herein is to be used solely for the purpose submitted, and no part of
this document or its contents shall be reproduced, published, or disclosed to a
third party without the express permission of Honeywell International Sàrl.
While this information is presented in good faith and believed to be accurate,
Honeywell disclaims the implied warranties of merchantability and fitness for
a purpose and makes no express warranties except as may be stated in its
written agreement with and for its customer.
In no event is Honeywell liable to anyone for any direct, special, or
consequential damages. The information and specifications in this document
are subject to change without notice.
Copyright 2019 - Honeywell International Sàrl
2
Contents
CONTENTS
Contents 3
Chapter 1 - Speeding up Star II implementation 7
Key tasks 7
New to security and/or the Star II 8
Chapter 2 - Installing the Star II controller 9
Installation checklist 9
Chapter 3 - Getting a Star II controller to communicate 11
Communications checklist: Using a simple LAN 12
Communications checklist: Using a complex LAN 13
Communications checklist: Using RS-232 14
Setting the controller device number 14
Setting the terminal port baud rate 16
Setting the host port baud rate 17
Setting the Cobox baud rate 18
Selecting between S-NET or Wiegand 19
Setting bus baud rates 21
Configuring attached devices 22
Restarting the Star II controller 23
Editing the HOSTS file 24
Setting the Micro Cobox IP address on a simple LAN 25
Setting the Micro Cobox IP address using the Lantronix Device Installer 25
Configuring Micro Cobox ports using Lantronix Device Installer 27
Setting the Micro Cobox IP address on a complex LAN 28
Setting the Micro Cobox IP address using telnet 29
Configuring Micro Cobox ports using telnet 31
Testing communications with the Micro Cobox 32
3
Contents
Chapter 4 - Defining channels and controllers 35

LAN channel checklist 35
Serial channel checklist 36
Creating a new Quick Builder project 37
Defining a Star II channel 38
Defining channels 38
Configuring a Star II channel for LAN communications 38
Configuring the channel's main properties for LAN communications 38
Configuring a LAN channel's port properties 39
Setting terminal server port properties 40
Setting LANVendor port properties 40
Configuring a serial channel's port properties 40
Downloading the channel 41
Defining a Star II controller 42
Downloading the controller 43
Enabling the channel and controller 44
Editing the SERVICES file 45
Chapter 5 - Defining points for doors 47
Checklist: Configuring a basic push door 48
Checklist: Configuring a single push door for anti-passback 48
Defining points in Quick Builder 49
Defining a reader point 50
Defining a lock point 51
Defining a door sense 52
Downloading points 53
Configuring access levels 54
Configuring time periods 54
Configuring zones 55
Combining zones and time periods in an access level 56
4
Contents
Configuring the controller’s users 57

Configuring the door definition for a pushdoor 58
Configuring the definition for a single door if you use anti-passback 60
Testing the door 63
Chapter 6 - Configuring cards and cardholders 65
Checklist 65
Adding a card 65
Testing a door's access configuration 66
Chapter 7 - Downloading to controllers 67
Downloading changes to a controller 67
Chapter 8 - Star II lift access control 69
Star II lift access control checklist 69
Creating the channel and controller for lift access control 70
Creating reader points for lift access 70
Creating floor points for lift access 72
Creating the input points for lift access 74
Configuring the reader points for lift access 76
Configuring the inputs under SE System Parameters 77
Configuring the outputs under SE System Parameters 78
Creating a floor access time period 79
Configuring the Elevator tab under SE System Parameters 80
Creating access levels for lift access 81
Creating cardholders and assign access levels for lift access 82
Chapter 9 - Troubleshooting 83
Common problems 83
Problem connecting to some of the controllers 83
One of the channels fails due to excessive errors 83
EBI does not receive any states from monitor inputs 84
5
Contents
Troubleshooting procedures 84
Adjusting a channel's tolerance for error 85
Chapter 10 - Background information 87

Related Star II documents 87
Star II names 87
Understanding building security 88
Understanding zones, time periods and access levels 88
Understanding anti-passback 90
Understanding how EBI and Star II control doors 91
A basic door configuration 91
More complex door configurations 94
Door configurations for anti-passback 94
Understanding communications topology between server and controller 97
LAN options 98
Serial options 101
Ideas for speeding up implementation 103
Information checklist 104
Site contact 105
IT Administrator contact 106
Site contact walkthrough 107
IT checklist 108
EBI checklist 108
Notices 111
6
CHAPTER
1 SPEEDING UP STAR II
IMPLEMENTATION
This guide describes how to implement NexSentry Star II in conjunction with
Enterprise Buildings Integrator (EBI).
TIP: If you want to print this guide, open and print StarII.pdf, which is
on your Honeywell server DVD.
Section-level checklists
Each section in this guide has one or more checklists. Sometimes you need to
choose which of several checklists to follow; in these cases, decision points
show you where the appropriate checklist is located.
n Complete the tasks in order shown, unless specified otherwise.

n Complete only the specific task, then return to the checklist that led to the
task.
n Some of the tasks and steps have conditional statements. For example,
the statement 'If you have installed Windows, continue to page 6' is a
conditional statement with a directive. When the condition is true, follow
the directive and then continue with the remaining tasks or steps, unless
the directive is to skip tasks or steps. When the condition is not true,
continue to the next task or step.
Task-based procedures
n Make sure you satisfy the Prerequisites before starting each task.
Sometimes you have to complete something else before you start the
procedure.
n Ensure you understand the Considerations that appear before each task.
This information informs you about material relevant to completing the
procedure.
Key tasks
This chart shows all the phases of implementing the Star II.
7
Chapter 1 - Speeding up Star II implementation
Figure 1-1: The implementation process
Each section begins with this flowchart, showing where you are in the
implementation process.
New to security and/or the Star II

If you are a technician new to security, or new to the Star II, this guide also
provides:
n A list of essential documents for implementing the Star II.

n Background information on building security concepts, for those new to
the industry.
n A description of how EBI and the Star II control doors.
n An outline of network topologies that can be used with the Star II.
n Some project and pre-project checklists that can speed up
implementation.
8
CHAPTER
2 INSTALLING THE STAR II

CONTROLLER
Star II installation instructions are provided in the NexSentry Star II Access
Control Unit User Guide. Use any wiring diagrams you may have, together
with the manual, for wiring the Star II and its MIROs.
Figure 2-1: Your location in the implementation process
Installation checklist
Use the checklist below to ensure that all installation tasks have been
performed.
Identify the wiring plan in a format similar to the following tables. The EBI SE
Input or Output Parameters determine on which logical input or output within
EBI a physical point will reside. The system supports 1-255 inputs and 1-96
outputs.
Task Done?
Ensure all readers are connected as per installation instructions.
Ensure all door sense switches are wired to an appropriate monitor input
terminal.
9
Chapter 2 - Installing the Star II controller
Task Done?
Ensure all REX switches are wired to an appropriate monitor input

terminal.
Ensure all door locks are wired to an appropriate relay output terminal.
Ensure any other monitor inputs or relay outputs are wired to appropriate
monitor input terminals and relay output terminals.
INPUT
EBI SE Input Parameters Description
MIRO Point
...
255
OUTPUT
EBI SE Output Parameters Description
MIRO Point
...
96
10
CHAPTER
3 GETTING A STAR II CONTROLLER

TO COMMUNICATE
Having installed and configured the Star II, this stage involves establishing
communications between the Star II and the server.
This section describes how to configure communications between the server
and the controller using each of the supported topologies. You need to run
through this section multiple times using different instructions when your
project includes multiple topologies.
Decision
Go to the appropriate checklist.
Checklists Go to
When you are connecting a controller to a simple LAN "Communications checklist:

with no gateways or routers between the server and Using a simple LAN" on the
the Star II controller next page
When you are connecting a controller to a complex "Communications checklist:

LAN, with gateways or routers between the server and Using a complex LAN" on
11
Chapter 3 - Getting a Star II controller to communicate
Checklists Go to
the Star II controller page 13
When you are connecting a controller to the server via "Communications checklist:
RS-232 Using RS-232" on page 14
Communications checklist: Using a simple LAN

Use the checklist below to ensure that you have completed all the required
tasks.
Task Go to Done?
Set the controller device number. "Setting the controller

device number" on
page 14
Set the terminal port baud rate. "Setting the terminal port
baud rate" on page 16
Set the host port baud rate. "Setting the host port baud
rate" on page 17
If you have a Micro Cobox "Setting the Cobox baud

attached to the controller, set the rate" on page 18
Cobox baud rate.
Select either S-NET or Wiegand "Selecting between S-NET

reader protocol. or Wiegand" on page 19
Set the S-NET baud rates. "Setting bus baud rates" on

page 21
Configure devices attached to the "Configuring attached

Star II. devices" on page 22
Restart the Star II controller. "Restarting the Star II

controller" on page 23
Edit the hosts file, so you can "Editing the HOSTS file" on
refer to the controller from the page 24
EBI server by a name.
Set the Micro Cobox IP address "Setting the Micro Cobox

and port settings. IP address on a simple
12
Task Go to Done?
LAN" on page 25
Test communications between the "Testing communications

EBI server and the Micro Cobox with the Micro Cobox" on
terminal server. page 32
Communications checklist: Using a complex LAN

tasks.
Task Go to Done?
Set the controller device number. "Setting the controller device

number" on the next page
Set the terminal port baud rate. "Setting the terminal port baud
rate" on page 16
Set the host port baud rate. "Setting the host port baud rate"
on page 17
If you have a Micro Cobox attached to "Setting the Cobox baud rate" on
the controller, set the Cobox baud rate. page 18
Select either S-NET or Wiegand reader "Selecting between S-NET or

protocol. Wiegand" on page 19
Set the S-NET baud rates. "Setting bus baud rates" on

page 21
Configure devices attached to the Star "Configuring attached devices"

II. on page 22
Restart the Star II controller. "Restarting the Star II controller"

on page 23
Edit the hosts file, so you can refer to "Editing the HOSTS file" on
the controller from the EBI server by a page 24
name.
Set the Micro Cobox IP address and "Setting the Micro Cobox IP
network settings. address on a complex LAN" on
13
Task Go to Done?
page 28
Test communications between the EBI "Testing communications with

server and the Micro Cobox terminal the Micro Cobox" on page 32
server.
Communications checklist: Using RS-232

tasks.
Task Go to Done?
Set the controller device number. "Setting the controller

device number" below
Set the terminal port baud rate. "Setting the terminal

port baud rate" on
page 16
Set the host port baud rate. "Setting the host port
baud rate" on page 17
Select either S-NET or Wiegand reader protocol. "Selecting between S-

NET or Wiegand" on
page 19
Set the S-NET baud rates. "Setting bus baud rates"

on page 21
Configure devices attached to the Star II. "Configuring attached

devices" on page 22
Restart the Star II controller. "Restarting the Star II

controller" on page 23
Plug the RS-232 connection between the COM

port on the server and the host port on the Star
II.
14
Setting the controller device number

The controller device number is usually only modified when the controller is
being multidropped.
To configure the controller device number

1. On the Star II, locate the S2 and S4 switches. (They are located near the
Intel chip, towards the middle board. Their names are printed on the
board itself.)
2. On the S2 switch, ensure DIPs 1–4 are set to off (0).
3. On the S4 switch, ensure DIPs 6–10 are set to off (0).
4. On the S4 switch, using DIPs 1–5, set the desired address according to
the following table.
Set DIPs on switch S4 to:

For Address:
5 4 3 2 1
0 OFF OFF OFF OFF OFF
1 OFF OFF OFF OFF ON
2 OFF OFF OFF ON OFF
3 OFF OFF OFF ON ON
4 OFF OFF ON OFF OFF
5 OFF OFF ON OFF ON
6 OFF OFF ON ON OFF
7 OFF OFF ON ON ON
8 OFF ON OFF OFF OFF
9 OFF ON OFF OFF ON
10 OFF ON OFF ON OFF
11 OFF ON OFF ON ON
12 OFF ON ON OFF OFF
15
Set DIPs on switch S4 to:

For Address:
5 4 3 2 1
13 OFF ON ON OFF ON
14 OFF ON ON ON OFF
15 OFF ON ON ON ON
16 ON OFF OFF OFF OFF
17 ON OFF OFF OFF ON
18 ON OFF OFF ON OFF
19 ON OFF OFF ON ON
20 ON OFF ON OFF OFF
21 ON OFF ON OFF ON
22 ON OFF ON ON OFF
23 ON OFF ON ON ON
24 ON ON OFF OFF OFF
25 ON ON OFF OFF ON
26 ON ON OFF ON OFF
27 ON ON OFF ON ON
28 ON ON ON OFF OFF
29 ON ON ON OFF ON
30 ON ON ON ON OFF
31 ON ON ON ON ON
Stop:
You have completed this task. Return to the checklist that led to this task.
16
Setting the terminal port baud rate

The terminal port baud rate sets the speed at which the Star II communicates
with devices connected to its terminal port.
To set the terminal port baud rate

1. Set JP16 for LAN (Cobox), as appropriate.
2. Locate the S5 switch. (It is located near the Intel chip, towards the middle
board, next to the S2 switch. Its name is printed on the board itself.)
3. Using DIPs 1 and 2, set the terminal port to the speed you want.
Switch S5—Terminal Port

DIPs
Comment
Baud
Dip 2 Dip 1
Rate
9600 OFF OFF
19200 OFF ON
38400 ON OFF
115200 ON ON Honeywell recommend you set this

rate, unless it proves to be a
problem.
4. Record your baud rate setting because you will require it in a later
procedure.
Stop
Setting the host port baud rate

The host port baud rate sets the speed at which the Star II communicates with
devices connected to its host port.
To set the host port baud rate

17
2. Using DIPs 3 and 4, set the host port to the desired speed. Honeywell
recommend you set this value to 9600.
Switch S5—Host Port

DIPs
Comment
Baud
Dip 4 Dip 3
Rate
9600 OFF OFF Honeywell recommend that you use

this rate.
19200 OFF ON
38400 ON OFF
57600 ON ON
procedure.
Stop
Setting the Cobox baud rate

The Cobox baud rate sets the speed at which the Star II communicates with
the Micro Cobox.
TIP: This setting is relevant only if a Micro Cobox terminal server is

plugged into the J4 connector.
To set the Cobox baud rate

2. Using DIPs 5 and 6, set the terminal port to the desired speed.
Switch S5—Cobox DIPs

Comment
Baud
Dip 6 Dip 5
Rate
9600 OFF OFF
18
Switch S5—Cobox DIPs

Comment
Baud
Dip 6 Dip 5
Rate
19200 OFF ON
38400 ON OFF Honeywell have found that this rate

works well in most cases.
115200 ON ON
procedure.
Stop
Selecting between S-NET or Wiegand

The Star II can be configured to communicate with DKR or MSR readers via
S-NET, or Wiegand readers via Wiegand. Each Star II has four buses, two of
which can independently configured to use either S-NET or Wiegand.
To select between S-NET 1 or Wiegand 1

2. Place DIP 5 in the correct position for your desired protocol.
ATTENTION: Although some Star II boards label DIP 5 as an

ADR (Address) switch, it does select between S-NET or Wiegand.
Switch S2
Protocol DIP 5
S-NET OFF
Wiegand ON
19
Locate the first set of jumpers behind TB1. (TB1 is next to the two RS-232
ports.) The board marking WG1 is visible next to this set of jumpers. Set the
jumpers to either S-NET or Wiegand configuration, as shown in this
illustration.
To select between S-NET 2 or Wiegand 2

2. Place DIP 6 in the correct position for your desired protocol.
ATTENTION: Although some Star II boards label DIP 6 as an

ADR (Address) switch, it does select between S-NET or Wiegand.
Switch S2
Protocol DIP 6
S-NET OFF
Wiegand ON
Locate the second set of jumpers behind TB1. (TB1 is next to the two RS-232
ports.) The board marking WG1 is visible next to this set of jumpers. Set the
jumpers to either S-NET or Wiegand configuration, as shown below.
20
Stop
Setting bus baud rates

While it is possible to change the bus baud rates, it is recommended that the
default baud rate is used.
The S-NET baud rate sets the speed at which the Star II bus operates.
Whatever value this is set to dictates the speed at which MIROs or WIROs are
connected. Some older hardware does not support S-NET baud rate
configuration.
To set bus baud rates

1. Locate the S2 and S5 switches. (They are located near the Intel chip,
towards the middle board. Their name is printed on the board itself.)
2. Using DIPs S2 and S5, set the S-NET 1 baud rate to 9600.
Switch S2 Switch S5
Baud Rate DIP 10 DIP 9 DIP 10 DIP 9
2400 OFF OFF OFF OFF
4800 OFF ON OFF ON
9600 ON OFF ON OFF
19200 ON ON ON ON
21
3. Using DIPs S2 and S5, set the S-NET 2 baud rate to 9600.
Switch S2 Switch S5
Baud Rate DIP 8 DIP 7 DIP 8 DIP 7
2400 OFF OFF OFF OFF
4800 OFF ON OFF ON
9600 ON OFF ON OFF
19200 ON ON ON ON
Stop
Configuring attached devices

The Star II supports a range of connected hardware: MIROs, WIROs and
readers.
Each of these devices require their own configuration. You must read their
documentation to learn how to configure them.
The points that follow provide guidance for the issues you should read in the
manufacturer's documentation.
Considerations
n In most cases, MIRO means MIRO or WIRO. MIROs and WIROs serve
similar purposes, with the difference being WIROs have the capability of
being configured to communicate with either S-NET devices or Wiegand
devices.
n The NexSentry Star II Access Control Unit User Guide has an
identification code that identifies devices by the number of:
Wiegand inputs/monitor inputs/relayoutputs
So a board will be given a name, and a number, such as 4/8/4,

meaning, the board is capable of 4 Wiegand inputs, 8 monitor inputs, and
4 relay outputs.
22
n The NexSentry board's name or identification code may not match the
NexSentry Star II Access Control Unit User Guide name or identification
code exactly. You may need to determine a match between the board and
the documentation by the meaning of the names and identification codes.
For a MIRO / WIRO

n To set the device number—ensuring that each MIRO connected on the
same bus has consecutive device numbers—see the NexSentry Star II
Access Control Unit User Guide.
n To set the reader protocol—DKR, MSR or Wiegand—see the NexSentry
Star II Access Control Unit User Guide.
n To set the reader address ranges for Wiegand only (not for S-NET), see
the NexSentry Star II Access Control Unit User Guide.
For a reader
n To set the reader device number, see the NexSentry Star II Access
Control Unit User Guide.
Stop
Restarting the Star II controller

If you change the DIP switches on the controller, you must restart the
controller for those changes to take effect.
To restart
1. Find the S1 switch. (It is near the battery, in the corner of the controller.)
2. Press the S1 switch for a few seconds, then release it.
When the board restarts, its VITAL light begins slowly flashing. (The VITAL
light is on the opposite side of the J3 connector to the Intel CPU.)
When communications are established, the SNET5 light begins flashing
fast. (The SNET5 light is above the large Microchip that sits next to the
Intel CPU.)
When you see both these lights flashing, the Star II is successfully
restarted.
Stop
23
Editing the HOSTS file

To configure the EBI server to communicate with a Star II controller across a
LAN, you can add an entry to the
%windir%\system32\drivers\etc\hosts file. The file contains
information similar to this example.
# Copyright (c) 1993-1999 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for
Windows.
...
127.0.0.1 localhost
...
When using LANVendor it is not possible to use the name associated with the
IP address. Quick Builder only supports an IP address for LANVendor
connections.
Prerequisites
n You have decided on the controller's hostname and IP address. The
hostname is the name you use when you want to refer to the controller
from the EBI server.
To add the entry

1. Open the Run dialog box.
2. Type notepad and click OK.
3. From Notepad, choose File > Open .
4. Go to the folder %windir%\system32\drivers\etc.
5. Select the hosts file.
6. Add an entry at the bottom of the file similar to the following line.
ip_address hostname
where ip_address is the IP address assigned to the Micro Cobox

device and hostname is the name by which you want to refer to this
controller.
7. Choose File > Save .
8. Close the document.
24
Here is an example of such a hosts file after several entries have been made.

#
# This is a sample HOSTS file used by Microsoft
TCP/IP for Windows.
...
127.0.0.1 localhost
192.168.1.25 ACU1
192.168.1.29 ACU2
192.168.1.45 ACU3
...
Stop
Setting the Micro Cobox IP address on a simple

LAN
When the Micro Cobox terminal server is shipped, it has no IP address
configured. The first task is to configure the Micro Cobox card with an IP
address and ensure the ports are set correctly.
On a simple LAN, with no routers or gateways between the server and the
Star II, you can use the Lantronix Device Installer utility.
TIP: After completing the task, return to the checklist that lead to the
task.
Setting the Micro Cobox IP address using the

Lantronix Device Installer
The Lantronix Device Installer is a quick and easy way to install the IP
address.
25
Prerequisites
n You have the following information:
l The IP address to be assigned to the terminal server.
l The Gateway IP address, if required.
l The subnet mask value used on this network.
n The Star II is powered. When it is powered, it has two status lights

flashing. If you have MIROs attached via the S-NET bus, they have vital
lights that are lit up.
n The Micro Cobox terminal server is physically seated on connector J4.
(See the NexSentry Star II Access Control Unit User Guide for physical
block layout diagram.) The LEDs are on.
n You have installed the LANTRONIX Device Installer on the EBI server
computer.
n A live ethernet cable is plugged between the Micro Cobox terminal server
and the network.
To set the IP address

1. From the server, open the Lantronix Device Installer. Choose Start >
Programs > Lantronix > DeviceInstaller > DeviceInstaller .
2. If multiple adapters or subnets are configured on the EBI server, the
Device Installer asks whether you want to specify the adapter or subnet to
search. Choose No .
Otherwise, the DeviceInstaller window appears.
3. Click Search .
The Device Installer scans all networks searching for Cobox devices.
When the scan is complete, it lists all detected devices.
4. From the devices that have been discovered, select your desired device.
5. Click Assign IP.
The Assign IP Address wizard appears.
6. Select Assign a specific IP address. Click the Next button.
7. Enter the desired IP address, Subnet mask and Default gateway. Click
Next.
8. Click Assign .
The task progress bar appears, showing the progress.
9. When complete, click Finish .
26
Configuring Micro Cobox ports using Lantronix Device

Installer
The Lantronix Device Installer is a quick and easy way to configure the port
settings.
Prerequisites
n The Lantronix Device Installer is open, listing the target Micro Cobox
device.
n Note that HyperTerminal is no longer provided with Windows and
Windows Server.
To configure the ports

1. Double-click the target Micro Cobox device.
The Configure Device dialog appears.
2. Click the Ports tab.
3. Double-click Port 1 and set the Port Settings to the values below.
Port
Value
Settings
Baud Set to the same rate as the Cobox baud rate.

Rate
Data bits 8
Parity None
Stop bits 1
Flow None
control
Flow control helps with busy system
communications to ensure message flow is more
robust. If you set the controller internal mechanism
to enable flow control—you configure this via
Hyperterminal (or an equivalent utility) directly in
the controller, not via EBI—you should match the
Cobox terminal server setting as well.
Flow control for Cobox should be set to Hardware if
27
Port
Value
Settings
Auto Flow Control is set to Enabled using Auto Flow

Control (System Configuration menu in Terminal
mode).You set up the terminal server configuration
via telnet. This is also independent of the EBI
configurations for the controller.
4. Click the Advanced tab.

5. Look for the entry Local Port. Note its value for later reference.
By default the value is 3001 .
6. Click OK.
7. Double-click on Port 2 and set the Port Settings to the values in the table
below.
Port
Value
Settings
Baud Rate The value to which you set switch S5 DIPs 5 and
6.
Data bits 8
Parity None
Stop bits 1
Flow control None
8. Click OK.
9. Click OK again.
Stop
Setting the Micro Cobox IP address on a complex

LAN
When the Micro Cobox terminal server is shipped, it has no IP address
configured. The first task is to configure the Micro Cobox card with an IP
address and ensure the ports are set correctly.
28
On a complex LAN, with routers or gateways between the server and the Star
II, you can use command line tools, such as arp and telnet, to configure the IP
address and port settings.
Setting the Micro Cobox IP address using telnet

When there is a firewall or router between the server and the controller, you
must follow this procedure in order to install the IP address on the Micro
Cobox terminal server. If the server and controller are connected via a simple
network, it is often easier to do this configuration via the Lantronix Device
Installer.
Prerequisites
n You have the following information:
l The server IP address that will be assigned to the terminal server.
l The gateway IP address if required.
l The subnet mask value.
n An available network connection and CAT5 patch cable to connect the

terminal server to the network.
n The Star II is powered and you can see the Vital light is flashing. If you
have MIROs attached via the S-NET bus, they have lights that are lit up.
n The Micro Cobox terminal server is physically seated on connector J4.
(See the NexSentry Star II Access Control Unit User Guide for physical
block layout diagram.) The LEDs are on.
To set the IP address

1. Record the Micro Cobox's MAC address. To do this, remove the Micro
Cobox from the controller, turn it over, read it off the label. Re-insert the
Micro Cobox.
2. From a Windows PC, open a Command Prompt.
3. Type the command:
arp -sxxx.xxx.xxx.xxxmm-mm-mm-mm-mm-mm
where xxx.xxx.xxx.xxx is the IP Address to be assigned to the
terminal server and mm-mm-mm-mm-mm-mm is the terminal server's MAC
Address.
For example, if you want to set the terminal server's IP address to
191.12.3.77 and its MAC address is 00-20-4A-02-64-0B, you would type:
29
arp -s 191.12.3.77 00-20-4A-02-64-0B

4. In the Command Prompt, open a telnet connection to port number 1 by
typing:
telnetxxx.xxx.xxx.xxx1
where xxx.xxx.xxx.xxx is the IP address assigned in the previous
step. This connection fails, but causes the Micro Cobox to change its IP
address to the desired one.
5. Open a telnet connection to port 9999 by typing:
telnet xxx.xxx.xxx.xxx9999
where xxx.xxx.xxx.xxx is the IP address assigned in a previous
step.
6. Press ENTER when you see the Cobox information screen.
7. Configure the network settings as follows:
a. Type 0 to enter the network settings.
b. Type the IP address (for example, 191.12.3.77) when prompted with:
IP address : (000)
c. Press Y when prompted with:
Set Gateway IP Address (N)
d. Type the gateway address when prompted with:
Gateway IP addr (000)
e. When prompted with:
Netmask: Number of Bits for Host Part
(0=default)
type the appropriate value from the following table. (The most common
value is 8.)
Desired Netmask Value
255.0.0.0 24
255.255.0.0 16
255.255.255.0 8
f. When prompted with:

Change telnet config password (N)
press N, unless you know you need to change the password.
The Change Setup menu appears.
30
g. Press 9 to save and exit.

You have now configured the terminal server's network settings.
Configuring Micro Cobox ports using telnet

When there is a firewall or router between the server and the controller, you
must follow this procedure in order to configure the ports on the Micro Cobox
terminal server. If the server and controller are connected via a simple
network, it is often easier to do this configuration via the Lantronix Device
Installer.
Prerequisites
n You have assigned an IP address to the Micro Cobox.
n You are logged on to Windows as Administrator.
n The Lantronix Device Installer is open, listing the target Micro Cobox
device.
To configure the ports

1. From a Command Prompt, type telnetxxx.xxx.xxx.xxx9999
where xxx.xxx.xxx.xxx is the IP address you assigned to the Micro
Cobox.
You should see the Cobox information screen.
2. Press ENTER as soon as possible after being prompted.
3. Type 1 to enter the settings for Channel 1 or type 2 to set up Channel 2.
4. Configure the channel parameters according to the following table.
Property Value
Baud Rate The value to which you set switch S5 DIPs 5 and
6.
Interface 4C if using RS-232

Mode
Flow Control 00
Port Number 3001, unless you are doing LANVendor

multidropping, and require this value to be
different
31
Property Value
Remote IP none
address
Remote TCP none

Port
Connect C0
Mode
Disconnect 00
Mode
Flush Mode 00
Disconnect 00:45
Time
SendChar 1 00
and 2
Do not confuse a Cobox channel with an EBI channel.

Make sure that each Cobox port number is unique between the channels.
(You can use the same port numbers for different terminal servers, as the
port numbers are device specific.)
The channel settings should now be completed.
5. Type 9 to save the settings.
The Cobox should now be ready for use with your controller.
Stop
Testing communications with the Micro Cobox

Having configured the Micro Cobox, test it to ensure you can communicate
with it from the EBI server.
To test communications with the Micro Cobox

1. Log on to the operating system of the EBI server as Administrator .
2. Open a Command Prompt and type:
pinghostname
32
where hostname is the name you assigned in the HOSTS file.

3. Check that the ping request replies without error.
4. In the Command Prompt, type:
telnethostname9999
where hostname is the name you assigned in the HOSTS file for your
terminal server.
5. If you see the following response, then the device is responding correctly.
*** Lantronix Universal Device
Server ***
Serial Number ...
Software version ...
Press Enter to go into Setup Mode.
6. After a few seconds, the device will automatically disconnect.

Connection to host lost.
This is expected behavior.

Stop
33
34
CHAPTER
4 DEFINING CHANNELS AND

CONTROLLERS
To configure EBI to communicate with the controller you have just configured,
you define the channel and controller properties in Quick Builder, then
download them to EBI.
Go to the appropriate checklist.
Checklists Go to
Defining a channel and controller over a LAN "LAN channel checklist" below
Defining a channel and controller over a serial "Serial channel checklist" on the
connection next page
LAN channel checklist

Use the checklist below to make sure that you complete all the required tasks.
Task Go to Done?
Create the Quick Builder "Creating a new Quick Builder project " on
35
Chapter 4 - Defining channels and controllers
Task Go to Done?
project. page 37
Add the channel. "Defining a Star II channel " on page 38
Configure the channel's "Configuring the channel's main properties for

main properties. LAN communications" on page 38
Configure the LAN port "Configuring a LAN channel's port properties"

properties. on page 39
Download the channel to "Downloading the channel" on page 41

the server.
Define the controller. "Defining a Star II controller" on page 42
Download the controller "Downloading the controller" on page 43

to the server.
Enable the channel and "Enabling the channel and controller" on

controller in Station. page 44
Serial channel checklist

Use the checklist below to make sure that you complete all the required tasks.
Task Go to Done?
Create the Quick Builder "Creating a new Quick Builder project " on the
project. facing page
Add the channel. "Defining a Star II channel " on page 38
Configure the channel's "Configuring the channel's main properties

main properties. for LAN communications" on page 38
Configure the serial port "Configuring a serial channel's port

properties (for RS-232). properties" on page 40
Download the channel to "Downloading the channel" on page 41

the server.
Define the controller. "Defining a Star II controller" on page 42
Download the controller to "Downloading the controller" on page 43

the server.
36
Task Go to Done?
Enable the channel and "Enabling the channel and controller" on

controller in Station. page 44
Creating a new Quick Builder project

Quick Builder is an application that configures an EBI database. You add and
configure all system components in a Quick Builder project, then download
the project to EBI.
TIP:
Experienced technicians sometimes want to directly select the correct
components instead of entering the authorization code. To do this,
check SE in the controller components list.
If you have added components that are not needed, you can disable
them. See the Quick Builder help for more information.
To create a new project

1. Click .
The Create New Project dialog box opens.
2. Type the project's filename in File Name . (Quick Builder uses a qdb
extension for project files.)
3. Click Save .
The Enable Components dialog box opens.
4. From Enable Components, select the required Server . Ensure you select
the server with the correct release number.
5. Type the system license into System Number and the authorization code
into Authorization Code , then click Apply.
6. Click the Enable Components tab.
All components licensed are checked.
7. Deselect each component you want to disable, then click OK.
Stop
37
Defining a Star II channel

You need to define a channel for the Star II controllers to communicate with
EBI using Quick Builder.
Defining channels
You can define either one channel, or simultaneously define multiple
channels.
To define a channel
1. In Quick Builder, select the Channels view.
2. Click to add a channel.
3. Make sure Channel is displayed in the Add Items box.
4. Choose SE Channel as the channel type.
5. Give the channel an appropriate name.
6. Click OK to add the channel to the Channel list.
7. Add an appropriate description.
8. Click Save to save the project.
Configuring a Star II channel for LAN

communications
Having defined a channel, you need to configure the channel's properties.
Quick Builder presents you with three tabs with which to configure the
channel's properties.
Configuring the channel's main properties for LAN

communications
Ensure each of the channel's main properties is set to a reasonable value for
your installation.
38
To configure the channel main properties

1. Enter an accurate description for the channel in the Description field.
2. Set the properties to the values appearing in the following table.
Property Default LAN value
Marginal 25
Alarm Limit
Fail Alarm 50
Limit
Response 10
Time
Exception 2
Scan Rate
Diagnostic 60
Scan Rate
Connect 10
Timeout
Read 2
Timeout
Or, where read timeout errors appear in the log,
increase this to 5 or 10 seconds.
Stop:
Configuring a LAN channel's port properties

You can configure a LAN channel using either LANVendor or Terminal
Service drivers. Considerations between selecting LANVendor or Terminal
Service drivers are summarized below.
Consideration Evaluation
I have several controllers and doors. Use Terminal Server, as the

configuration is simpler.
I have more than 30 controllers using on- Consider using LANVendor with three
board terminal servers controllers per channel.
39
Consideration Evaluation
I have many controllers (more than 99) You must use LANVendor.
using on-board terminal servers
Setting terminal server port properties
To configure terminal server port properties

1. Set the Port Type to Terminal Server .
2. Set Terminal Server TCP Host Name to the host name your entered into
your Hosts file, or the IP address of the controller.
3. Set Terminal Server TCP Port No to the port number set on your terminal
server. This is typically 3001. (You may have chose to set it to something
different when you configured this in the task “Setting the Micro Cobox IP
address on a simple LAN”.
Stop
Setting LANVendor port properties

You set the port properties in Quick Builder, and by editing the Windows
Services file.
To configure
1. Set Port Type to LANVendor .
2. Set Port Name to an appropriate name. For example, port_3001 or
port_3002.
3. Add the code you entered into Port Name into the Windows Services
file.
Stop
Configuring a serial channel's port properties

Configure serial properties for RS-232 as described in this section.
40
TIP: This procedure describes how to configure Quick Builder to

match the Star II's baud rate, as set by switch S5 DIPs 3 and 4. They
will be set to 9600 unless you configured them differently.
To configure the serial channel port properties

1. Set Port Type to Serial. Make sure you can see Serial in the Port Type box.
2. Set the Serial Port Name to the name of the COM port to which you will
attach the RS-232 cable.
3. Set the Baud Rate to match the controller's baud rate. The Star II's baud
rate is set by the DIP switches 3 and 4 on switch S5.
4. Set the properties to the values listed in the table below.
Port Setting Value
Number of data bits 8
Parity None
Stop Bits 1
XON / XOFF None
Stop
Downloading the channel

Downloading the channel helps determine whether the channel definition is
good.
To download
1. Select the channel you want to download.
2. Click .
The Download dialog box opens.
3. Click Selected items only.
4. Check that the items listed in the Summary list are those you want to
download.
41
5. Click OK.
If Pharmaceutical Compliance Restrictions is licensed, the QB User
Sign-On dialog box opens. Type a User Name , Password and Domain
and click OK.
You can terminate the download by clicking Cancel on the progress bar.
When downloading is complete, the Results dialog box opens, listing
every file created by Quick Builder during the download. It displays point
(*.pnt) and hardware (*.hdw) definition files. If any errors occur, it
generates an *.out file. You can view any file by double-clicking it.
6. If a *.out file is generated, double-click it and read the information after
the ***** for a description of the problem that causing the error.
Stop
Defining a Star II controller

Having defined the SE Channel necessary for EBI and the controller to
communicate on, you now need to define the Star II controller itself.
You can define one or more controllers on a channel.
To define a controller
1. In Quick Builder, select the Controllers view.
2. Click to add a controller.
3. Make sure Controller is displayed in the Add Items box.
4. Choose SE Controller as the controller type.
5. Give the controller an appropriate name, with a maximum length of 10
characters.
6. Click OK to add the controller to the Controllers list.
7. Add an appropriate description.
8. Select the name you gave to your channel from the list of channel names
in the Channel Name box.
9. Select from Controller Type the type NexSentryPlus.
ATTENTION: Do not select NexSentry. NexSentry is for Star I, not

Star II.
10. Set the Controller ID to the controller device number. (You set this
previously using the controller's DIP switches.)
42
11. Set the RTU ID to a sensible value.
ATTENTION: Station lists controllers by their RTU ID. Keeping

related controllers together in Station's list significantly improves
operations.
12. If you are defining this controller in a LANVendor channel, enter the
terminal server's IP address into the IP Address box. (IP Address does not
appear on controllers in a Terminal Server channel.)
14. Click .
download.
17. Click OK.
and click OK.
Stop
Downloading the controller

Downloading the controller helps determine whether the channel definition is
good.
To download
1. Select the controller you want to download.
2. Click .
43

download.
5. Click OK.
and click OK.
Stop
Enabling the channel and controller

Having defined the channel and controller, you can now enable the channel
and controller in Station.
Prerequisites
n You are logged on to Station with MNGR security level.
To enable the channel and controller

1. Choose Configure > System Hardware > Controller Interfaces > Channels.
The channel display appears.
2. Click the channel name and click the Status Details tab.
3. Check the Enable box.
The channel is now connected. The controller that was added to the
channel is enabled by default. Both should now be enabled.
4. Examine the Error Statistics to see whether EBI is communicating. When
it is, Total requests continue increasing at a much faster rate than the
number of errors.
If the channel fails, see the “Troubleshooting” section.
44
Stop
Editing the SERVICES file

To configure the EBI server to communicate with a Star II controller across a
LAN using the LANVendor driver, you must add an entry to the
%SystemRoot%\%windir%\system32\drivers\etc\services
file. The file contains information similar to the example shown here:
#
# This file contains port numbers for well-known services
defined
by IANA
#
# Format:
#
# <service name> <port number>/<protocol> [aliases...]
[#<comment>]
#
echo 7/tcp
echo 7/udp
discard 9/tcp sink null
discard 9/udp sink null
systat 11/tcp users
...
To add the entry

1. Open the Run dialog box.
2. Type notepad and click OK.
3. From Notepad, choose File > Open .
4. Go to the Windows folder. (The Windows folder could be named
C:\Windows, C:\%windir% or some other name.)
5. From the Windows folder, go to the folder \system32\drivers\etc.
6. Select the services file.
7. Add an entry anywhere in the file similar to the following line. Ensure that
the code you use on the left matches the code that appears in Quick
Builder's Port Name property, on the channel's Port tab.
45
port_3001 3001/tcp # Star II

Controller
Multiple port names are only required if the terminal servers being used
have more than one port. If all terminal servers are onboard Coboxes, it is
much simpler to use the same port number for all connections.
46
CHAPTER
5 DEFINING POINTS FOR DOORS
After establishing communications between the controller and server, you can
begin defining points.
It is best to define a single door, then test it, before you define additional
doors. It is quicker to find and fix faults using small iterations.
The following checklists describe prototypical point configurations for doors.

Due to the wide variation in configuring points, the precise design you need
may not be described here. Use these as prototypes that you adapt to serve
your needs.
Checklist Go to
Configuring a basic push door "Checklist: Configuring a basic push door" on

the next page
Configuring a single push door "Checklist: Configuring a single push door for
configured for anti-passback anti-passback" on the next page
47
Chapter 5 - Defining points for doors
Checklist: Configuring a basic push door

Use the checklist below to ensure that you complete all the required tasks.
Task Go to Done?
Quick Builder tasks
Define the reader "Defining a reader point" on page 50

point.
Define the lock point. "Defining a lock point" on page 51
Define the door "Defining a door sense" on page 52

sense.
Download the points "Downloading points" on page 53

to the server.
Station tasks
Configure access "Configuring access levels" on page 54

levels.
Once-per-controller tasks
Configure the "Configuring the controller’s users" on

controller's users. page 57
Once-per-door tasks
Configure the door "Configuring the door definition for a

definition. pushdoor" on page 58
Test the door. "Testing the door" on page 63
Checklist: Configuring a single push door for anti-

passback
Use the checklist below to ensure that you complete all the required tasks.
Task Go to Done?
Quick Builder tasks
Define the first "Defining a reader point" on page 50
48
Task Go to Done?
reader point.
Define the first door "Defining a door sense" on page 52

sense.
Define the second "Defining a reader point" on the next page

reader point.
Define the second "Defining a door sense" on page 52

door sense.
Download the points "Downloading points" on page 53

to the server.
Once-per-installation Station tasks
Configure access "Configuring access levels" on page 54

levels.
Once-per-controller tasks
Configure the "Configuring the controller’s users" on page 57

controller's users.
Once-per-door tasks
Configure the door "Configuring the definition for a single door if you
definition. use anti-passback" on page 60
Test the door. "Testing the door" on page 63
Defining points in Quick Builder

To configure a door, you need to create at least one of each of the following
types of points:
n Reader
n Lock
n Sense
Not all these points are built in Quick Builder though, because the reader point
is a complex point, containing multiple options within it.
49
Defining a reader point

You need one reader point for each door monitored by EBI.
Prerequisites
n Your EBI server has had its locations configured. Ensure you know where
your controller is located.
To define the access point

1. Within the Quick Builder project, click the Points view.
2. Click to add a point. The Add Items dialog box appears.
3. Make sure Point is displayed in the Add Items box.
4. Select Access Point from the Type list. Click OK.
5. Give the point a name, description, and assign it an appropriate location.
6. Click the ellipsis button to the right of PV Source Address. The Address
Builder dialog box appears.
7. In the Address Builder dialog box, leave the Address Type as Controller .
ATTENTION: People new to point addressing commonly select

an Address Type of Point in this box because they are adding a lock
point. This is incorrect. What you are defining here is a controller
point.
8. Make sure the controller's name appears in the Controller list.

9. In the Address box, type ACCESS , then type the door number attached
to the Star II. (The DoorNumber is a number between 1 and 16.)
ACCESS DoorNumber
10. Click OK. The complete address now appears in the PV Source Address
box.
11. Type the name of the zone this access point enables in the Entry to Zone
box.
12. If anti-passback or PGAP is enabled for this point, type the names of the
zones the cardholder will exit from in the Exit From Zone box.
Stop
50
Defining a lock point

You need one door lock point for each door monitored by EBI.
To define a lock point

4. Select Status Point from the Type list. Click OK.
ATTENTION: People new to point addressing commonly select

an Address Type of Point in this box because they are adding a lock
point. This is incorrect. What you are defining here is a controller
point, as opposed to a file point or a database point.

9. In the Address box, type LOCK , then enter the number of the door that is
associated with this switch. (The DoorNumber is a number between 1
and 16.)
LOCK DoorNumber
box.
11. From the Number of States list, select 8. All eight state descriptor boxes
are enabled.
12. Enter into the State Descriptor boxes the values that appear in this table.
State Number Descriptor
State 7 Shunted
State 6
State 5
State 4
51
State 3
State 2 AutoUnlk
State 1 Unlocked
State 0 Locked
13. Select and copy the PV Source Address.

14. Click on the Control tab.
15. Paste the information you copied from the PV Source Address box into the
Source AddressOutput (OP) box.
16. Paste the same information into the Destination Address Output (OP) box.
Stop
Defining a door sense

An open point can be used to alert when a door or other device changes state.
To define a door sense switch

4. Select Status Point from the Type list. Click OK.
People new to point addressing commonly select an Address Type of
Point in this box because they are adding a lock point. This is incorrect.
What you are defining here is a controller point, as opposed to a file point
or a database point.
9. In the Address box, type OPEN , then enter input address for the physical
wiring. (The DoorNumber is a number between 1 and 16.)
52
OPEN DoorNumber
box.
11. From the Number of States list, select 8. All eight state descriptor fields are
enabled.
12. Type into the State Descriptor boxes the values that appear in this table.
State 7 Shunted
State 6
State 5 ShortCCT
State 4 OpenCCT
State 3
State 2 Forced
State 1 Too Long
State 0 Normal
13. Click the Alarms tab.

14. Select the Enable check box to enable the alarm.
15. Select the urgency level from the Priority drop down list.
Stop
Downloading points
Download the points to continue their configuration in Station.
To download
1. Select the points you want to download.
2. Click .
53

download.
5. Click OK.
and click OK.
Stop
Configuring access levels

An access level defines at what times, on what days, a cardholder can enter
which zone. Cards can have any number of access levels associated with
them, limited only by the controller's capacity. SE controllers support 120
access codes per controller.
To define an access level, the underlying zones and time periods must be
defined. You then combine the zones and time periods within the access
level.
Configuring time periods

Time periods form a basic building block for access control.
Prerequisites
n You must be logged on to Station with MNGR level security.
To add a new time period

1. Call up the Time Period display. Choose Configure > Access Control >
Time Periods.
54
2. Click an undefined time period—a blank line.

The Time Period Definition display appears.
3. From the Details for list box, select NexSentry+.
4. Type the name of the time period into the Name box based on what period
of time is being defined.
Examples: Work days, weekend nights, weekends.
5. Describe the purpose of the time period in the Description box.
6. From the Location list, select the appropriate location.
7. Enter up to four ranges of time by specifying the Start Time , Stop Time and
checking the days on which they are in force.
8. When all changes have been made, click Save .
The system validates the changes.
Configuring zones
Zones are also a basic building block for access control. Zones are mostly
defined in Quick Builder as a side-effect of adding access points. You can only
change the configuration of the zone—its location and description—in Station,
plus some controller (NexSentryPlus) options.
Prerequisites
TIP: When PGAP (Perimeter Global Anti Passback) is enabled, you

can define one or more zones as 'outside' zones. This determines
which zones are 'outside' the facility and defines the cards' alternative
'outside' access to the facility. For details about enabling PGAP, see
the Security Electronics Access Control Configuration Guide.
To modify a zone
1. Call up the Zones display. Choose Configure > Access Control > Zones.
2. Click a zone in the Zone list.
The Zone Definition display appears.
3. Enter an appropriate Description .
5. If this is a vehicle zone, select the NexSentry Plus Vehicle zone option.
55

Combining zones and time periods in an access level

The access level is where you combine the time periods and zones together,
in order to enable any cardholder to enter a zone during approved hours.
It is likely that different job roles—those with different time restrictions—will be
entered on different access levels.
Prerequisites
TIP: When you configure an access level, EBI checks if an access

level with identical properties already exist. If it exists, you are
prompted to create a duplicate access level.
To configure access levels

1. Call up the Access Levels display. Choose Configure > Access Control >
Access Levels.
2. Click an access level in the Access Level list.
The Access Level Definition display appears.
3. Enter an appropriate name into the Name box.
Examples: IT Staff, Lvl 3
4. Enter a description of the access level in the Description box.
5. Enter the Location where the zone is located. (This is the same zone you
entered in Quick Builder location boxes.)
6. If you want to duplicate an existing access level, select the access level
from the Access level to copy from drop down list. Then click the Copy
button.
7. To add a new zone–time period pair:
a. Select a zone from the Zone list.
b. Select a time period from the Time Period list.
8. Repeat step 7 until all zone–time period pairs have been added.
56

The system then validates and downloads changes associated with the
access level.
Stop
Configuring the controller’s users

When you access the controller via HyperTerminal, you log on to it with a
username and password.
TIP:
l HyperTerminal is no longer provided with Windows and Windows
Server. You should refer to the manufacturer's documentation to

find out how to complete this configuration task without using
HyperTerminal.
l You must be logged on with MNGR-level privileges.
l The default user name and password is operator1 and new. You
must set this password in Station, because the first time you
download to the controller from EBI, EBI will overwrite the default
user name and password, rendering the controller inaccessible via
HyperTerminal.
To reset the controller password

1. Call up the SE System Parameters display. Choose Configure >
Access Control > SE Parameters.
2. Click the Next or Previous buttons until you see the controller you are
wanting to configure. (Controller name is in the top right of the screen.)
3. Click the Users tab.
4. Enter a username into the Operator Name box.
5. Enter a password into the Operator Password box.
6. Enter the appropriate privilege into the Privileges Level box. In practice
this should be level A, the highest level (F being the lowest).
The system validates and downloads the changes.
Stop
57
Configuring the door definition for a pushdoor

Unlike many controllers, the Star II enables you to map to arbitrary inputs and
outputs to points in EBI. Note carefully how the first reader input can be
mapped to any arbitrary physical input on the controller or MIRO.
Prerequisites
n You have downloaded the point definitions for at least one door from
Quick Builder. (No error files were generated when you downloaded to
the server.)
To configure
wanting to configure. (Controller name is in the top right of the screen.)
3. Click the Inputs tab.
4. Find the row number matching the value you entered into the Door switch
box. You will now connect this logical input with a physical input.
a. In the Device ID box, enter the value of the device to which the monitor
input is wired. (This is 1 for the controller's device number, or the MIRO
device number.)
b. Looking carefully at the device, determine the monitor input to which
the door switch is wired. (You may need to consult the NexSentry Star
II Access Control Unit User Guide to determine which monitor input.)
c. Select an appropriate configuration from the Configuration drop down
list.
The schematic for each configuration option appears at the bottom of
the display.
d. Select the appropriate State for the input.
e. Select SE-ACTION1 from the Action drop-down list.
5. Find the row number matching the value you entered into the REX switch
device number.)
58

the REX switch is wired. (You may need to consult the NexSentry Star
c. Select an appropriate configuration from the Configuration drop-down
list.
the display.
d. Select the appropriate State for the input.
e. Select SE-ACTION1 from the Action drop-down list.
6. Click the Outputs tab.
7. Find the row number matching the value you entered into the Door output
a. In the Device ID box, enter the value of the device to which the relay
output is wired. (This is 1 for the controller's device number, or the
MIRO device number.)
the relay output is wired. (You may need to consult the NexSentry Star
II Access Control Unit User Guide to determine which relay output.)
c. Select SE-ACTION1 from the Action list.
8. Click the Doors tab.
You see a list of the reader points that you configured against this
controller in Quick Builder.
9. Double-click on the name of the reader point.
The Access Point Detail display appears.
10. Click the Door Definition tab.
The Door Definition tab appears.
11. Enter the logical output number into the Door output box between the
values of 1 and 96.
12. Enter the logical input number into the Door switch box between the
values of 1 and 255.
13. Enter another logical input number into the REX switch box between the
values of 1 and 255, ensuring it is a different number from the Door switch
box.
14. Select the REX unlock check box.
15. Click Save .
59
16. Click the Back button (or press F8) until you return to the SE Controller
Settings display.
The system then validates the changes.
Stop
Configuring the definition for a single door if you

use anti-passback
Unlike many controllers, the Star II enables you to map to arbitrary inputs and
outputs to points in EBI. Note carefully how the first reader input can be
mapped to any arbitrary physical input on the controller or MIRO.
This capability is especially useful in configuring multiple virtual doors against
a single physical door. Note carefully how outputs from multiple doors are
pointed at the same physical relays.
For details about configuring Perimeter Global anti-passback (PGAP), refer
to 'Enabling PGAP' in the Security Electronics Access Control Configuration
Guide.
Prerequisites
n You have downloaded the point definitions for both virtual doors from
Quick Builder. (No error files were generated when you downloaded to
the server.)
To configure a single door

2. Click the Next or Previous buttons until you see the controller you want to
configure. (The controller name is in the top right of the screen.)
device number.)
60

c. Select an appropriate configuration from the Configuration list.
the display.
d. Select the appropriate State for the reader.
e. Select SE-ACTION1 from the Action list.
6. Find the row number matching the value you entered into the Door output
a. In the Device ID box, enter the value of the device to which the relay
output is wired. (This is 1 for the controller's device number, or the
MIRO device number.)
b. Looking carefully at the device, determine the relay to which the relay
output is wired. (You may need to consult the NexSentry Star II
Access Control Unit User Guide to determine which relay output.)
c. Select SE-ACTION1 from the Action list.
8. Double-click the name of the reader point corresponding to the first door.
10. Enter the logical output number into the Door output box between the
values of 1 and 96. Note this number.
11. Enter the logical input number into the Door switch box between the
values of 1 and 255. Note this number.
12. Enter zero into the REX switch box.
13. Click Save .
Settings display.
The system then validates the changes. You have now configured one of
the two virtual doors.
61

17. Double-click the name of the reader point corresponding to the second
door.
19. Enter the first door's logical output number into the Door output box.
For anti-passback doors, it is recommended to use two separate lock
outputs that are wired to the same physical door strike. This eliminates a
door timeout and relock.
20. Enter a logical input number into the Door switch box between the values
of 1 and 255. This should be the same door switch number as defined for
the first door.
21. Enter zero into the REX switch box.
22. Click Save .
Settings display.
device number.)
c. Select an appropriate configuration from the Configuration list.
the display.
d. Select the appropriate State for the reader.
e. Select SE-ACTION1 from the Action list.
The system then validates the changes.
Stop
62
Testing the door

Test the door after configuring it to ensure that it operates as expected.
To check the newly configured door

1. Toggle the REX. Ensure the lock relay fires.
2. Test the open circuit. Ensure it behaves as intended.
3. Simulate a forced door. Ensure an alarm is generated.
63
64
CHAPTER
6 CONFIGURING CARDS AND

CARDHOLDERS
Having configured a door, you need to add your card to EBI in order to test the
access control configuration.
Checklist
Use the checklist below to ensure that you have performed all the tasks
required.
Task Go to Done?
If this is the first door you are "Adding a card" below

testing, you add your card.
Test the door's access configuration. "Testing a door's access

configuration" on the next page
Adding a card
You add an employee's card to the system in order to test the access control
on each individual door.
65
Chapter 6 - Configuring cards and cardholders
For details about cardholders and cards, refer to 'Managing cardholders and
cards' in the EBI Operator's Guide.
To add a cardholder and issue a card

1. Log on to Station with MNGR security privileges.
2. Choose Configure > Cardholder Management > Add Employees.
3. Enter the cardholder's first name into the First Name box.
4. Enter the cardholder's last name into the Last Name box.
5. Issue a card to the cardholder by typing the card number in the Card
Number box.
As you issue a card, it appears in the box below.
6. Click Add .
The Cardholder display appears.
7. Click the Access Rights tab.
8. From the Available Access Rights list, select the access levels necessary
for testing the card with the reader and click the Assign button.
The access levels you selected appear in the Assigned Access Rights list.
9. Click Save to download this card to all controllers.
Your card should now be registered with all configured controllers.
Testing a door's access configuration

Test that the reader correctly reads your card and causes the door to unlock.
Prerequisites
n Assign sufficient privileges to access your target door.
To test
1. Swipe your card in front of the reader.
The green LED on the reader lights up. The relay activating the lock or
strike should fire. The door should be able to be opened.
2. Ensure that the door relocks after an appropriate delay.
66
CHAPTER
7 DOWNLOADING TO
CONTROLLERS
When you have completed all door configuration and added all cardholders
necessary to complete the task, the information must be downloaded to the
controllers. Downloading is done automatically in EBI, so this section outlines
how to download manually, if necessary.
Downloading changes to a controller

Downloads are now automatic in Station and all access information is
downloaded to the controllers when the Save button is clicked. If a controller is
offline during a download, changes are then downloaded when the controller
comes online. If necessary, you can still use the Download display to
download changes to a controller.
To download all information

1. Log on to Station with a security level of SUPV (or higher).
2. Choose Action > Access Download to call up the Download display.
3. Select the controllers you want to download to. (Click Select All to select
all controllers.)
67
Chapter 7 - Downloading to controllers
4. Click Download All.

A message appears in the Message Zone asking whether you want to
continue.
5. Click the Yes button to the right of the message.
A display, showing the download progress, appears.
6. If there are any problems with the download, click the View Download
Error Summary link.
7. If, after the download has finished, you want to perform another
download, click Return to Download start page .
68
CHAPTER
8 STAR II LIFT ACCESS CONTROL
This section describes setting up a sample lift (elevator) configuration using

EBI and a Star II controller with an external MIRO. This example shows
building a lift controller with two lifts which access four floors.
Star II lift access control checklist

This checklist describes how to configure lift access control for Star II
controllers.
Prerequisites
n You have set up the Star II controller and MIRO according to instructions
in the NexSentry Star II Access Control Unit User Guide.
n You must be logged on to Station with MNGR level security to complete
the configuration.
Complete the tasks in the following order.
Task Go to: Done?
Create the channel and "Creating the channel and controller for
controller lift access control" on the next page
Create the reader points "Creating reader points for lift access" on
the next page
Create the floor points "Creating floor points for lift access" on
page 72
Create the input points "Creating the input points for lift access"
on page 74
Configure the reader points "Configuring the reader points for lift
access" on page 76
Configure the inputs under SE "Configuring the inputs under SE System

System Parameters Parameters" on page 77
Configure the outputs under "Configuring the outputs under SE
69
Chapter 8 - Star II lift access control
Task Go to: Done?
SE System Parameters System Parameters" on page 78
Create a floor access time "Creating a floor access time period" on

period page 79
Configure the Elevator tab "Configuring the Elevator tab under SE

under SE System Parameters System Parameters" on page 80
Create access levels "Creating access levels for lift access" on

page 81
Create cardholders and assign "Creating cardholders and assign access

access levels levels for lift access" on page 82
Creating the channel and controller for lift access

control
An SE channel and controller must be defined, downloaded and enabled
before you can start configuring lift access control.
To create the SE channel and controller

1. Using Quick Builder, create a new Quick Builder project. The project may
include a Facility Model that indicates four floors (Floors 1, 2, 3, and 4) but
this is not essential.
2. Using Quick Builder, build an SE channel as appropriate, for example,
CHASEC1.
3. Using Quick Builder, build an SE controller, for example, CONSEC1, and
set the Controller Type to NexSentry Plus.
4. Download the configuration to the EBI database.
5. In Station, enable the channel and verify communication is good.
Creating reader points for lift access

You need one reader point for each lift controlled by EBI. Build two access
points for the lift readers, one for each of the two lifts in this example.
70
To create the reader points for lift access

4. Select Access Point from the Type list and select 2 from the Number of
items to Add list.
5. Type a prefix for the point names in the Format text box, for example,
LiftAccess , and start the numbering from 1.
6. Click OK to create two access point items, LiftAccess1 and
LiftAccess2.
7. Click the first access point item, LiftAccess1, and complete the Main
tab of the Points display as follows:
a. If the project has a Facility Model, add the location of the access point.
To do so, click the ellipsis button to the right of the Location box and
click on the relevant Facility name. Click Apply and Close .
b. In the Description box, type Lift 1 Reader .
c. Click the ellipsis button to the right of the PV Source Address box,
select Controller for the Address Type list, click CONSEC1 in the
Controller list and type ACCESS 1 in the Location box. Click OK.
Note that this location is a different parameter than the Facility model's
location entered above. For more information about SE address
syntaxes, see the Security Electronics Access Control Configuration
Guide.
d. Type Lift1 in the Entry to Zone text box for reader 1.
e. Make sure the Scanning Enabled check box is selected.
8. Click Save .
9. Click the second access point item, LiftAccess2, and incomplete the
Main tab as follows:
a. If the project has Facility Model, add the location of the second access
point.
click the relevant Facility name. Click Apply and Close .
b. In the Description box, type Lift 2 Reader .
Controller list, and type ACCESS 2 in the Location box. Click OK.
d. Type Lift2 in the Entry to Zone box for reader 2.
e. Make sure the Scanning Enabled check box is selected.
71
10. Click Save .

11. Download the added points to the EBI database. Choose Tools >
Download , click All Items Relevant to Selected Server and then click OK.
Creating floor points for lift access

Floor points are specialized status points that restrict access to certain floors
of a building through control of the lifts. A floor is either in an access state,
allowing anyone to stop at the floor, or in a secure state, where only
cardholders with the required privileges can access the floor.
A floor point has two functions:
n Provides access to the floor when the floor is in secure mode

n Allows an operator to set a floor to the Secure or Access state.
The floor point states are defined as follows:
State Descriptor Meaning
0 ACCESS Security cards are not required. Access to the floor allowed.
1 MAN Manual secure control. Security cards are required.
2 AUTO Auto secure state. Security cards are required.
3 INCOMP Different lifts for the same floor report different states
The MAN state is the state the point will normally be in if there is no schedule
assigned to the floor under the Elevator tab for the SE Parameters. If the floor
is in the MAN state, a card is required to access the appropriate floors. The
floor point can be commanded to the ACCESS state to allow free access.
If there is a schedule defined for the floor, the point will be in either AUTO or
ACCESS depending on the schedule. The AUTO state corresponds to
AutoEnable in Star II controllers. In the AUTO state, a card is required to
access the floors. The floor point can be manually commanded to override the
current scheduled state.
When setting up the time period, it needs to be set up for the times you want
the floor(s) to be in the AUTO state (that is, you need a card to access). When
the time is outside of this schedule, the floor(s) will be in ACCESS mode and
allow free access to the floors.
Now we will build four floor points for the four floors that the two lifts can
access.
72
To create the floor points for lift access control

4. Select Status Point from the Type list and select 4 from the Number of
items to Add list.
LiftFloorStat , and start the numbering from 1.
6. Click OK to create four floor point items: LiftFloorStat1 through to
LiftFloorStat4.
7. Click the first status point item, FloorStat1, and complete the Main tab
of the Points display as follows:
a. If the project has Facility Model, add the location of the first status
point, for example, LiftFloor1.
b. In the Description box, type Floor 1 Status Point .
Controller list, and type FLOOR 1 in the Location box. Click OK.
For more information about SE address syntaxes, see in the Security
Electronics Access Control Configuration Guide.
d. Type 8 in the Number of States box.
73
e. Type in the State Descriptors as follows:
State 7
State 6
State 5
State 4
State 3 Incomp
State 2 Auto
State 1 Manual
State 0 Access
f. Make sure the Scanning Enabled check box is selected.

8. Click the Control tab and make sure the Output (OP) Destination Address
is the same as the PV Source Address.
9. Click the Display tab and type FloorA in the Entry to Zone box for the first
floor point.
10. Repeat steps 7-9 to configure the remaining floor points, keeping in mind
to increment the floor point items, for example, the PV Source Address for
the second floor point, LiftFloorStat2, becomes CONSEC1 FLOOR
2 and it uses FloorB in the Entry to Zone box in the Display tab.
11. Click Save .
12. Download all the added points to the EBI database. Choose Tools >
Download , click on All Items Relevant to Selected Server and click OK.
Creating the input points for lift access

In this section, we will build eight input points for the lifts, i.e. four for each lift.
This is not essential for lift access control but may be required for extra
monitoring capabilities. Input points are most commonly used for destination
reporting and single floor latching.
To create the input points for the lift

74

4. Select Status Point from the Type list and select 8 from the Number of
items to Add list.
LiftInput .
6. Click OK to create eight input point items, for example, LiftInput1,
LiftInput2, etc.
7. Click the first status point item, LiftInput1, and fill in the Main tab of the
Points display as follows:
a. If the project has Facility Model, add the location of the first input point,
for example, Floor1.
b. In the Description box, type Lift 1 Floor 1 input .
Controller list, and type MNTR 1 in the Location box (MNTR for
monitor point status). Click OK.
For more information about SE address syntaxes, see in the Security
Electronics Access Control Configuration Guide.
d. Type 8 in the Number of States box.
e. Type in the State Descriptors as follows:
State 7 Shunt
State 6
State 5 Short
State 4 Open
State 3 Access
State 2
State 1 Active
State 0 Normal
f. Make sure the Scanning Enabled check box is selected.
75
8. Repeat step 7 to configure the remaining input points. Inputs points 1-4
are for floors 1-4 (Lift 1) and points 5-8 are for floors 1-4 (Lift 2), so add an
appropriate description to the points.
Remember to increment the input point items, for example, the PV Source
Address for the second input point, LiftInput2, becomes CONSEC1
MNTR 2.
9. Click Save .
10. Download all the added points to the EBI database. Choose Tools >
Download , click on All Items Relevant to Selected Server and click OK.
Configuring the reader points for lift access

The two reader points created must be configured to determine that they are
Elevator types, and to link the actual floor numbers (Index) to the Logical Floor
Numbers, Input IDs, and Output IDs.
To configure the reader points

1. In Station, call up the SE System Parameters display (choose Configure
> Access Control > SE Parameters)
wanting to configure; for example, the Star II lift controller, CONSEC1.
3. Click the Doors tab. You see a list of the reader points that you configured
against this controller in Quick Builder.
4. Call up the Access Point Detail for the first reader, LiftAccess1, by
double-clicking on the reader point name.
5. Click the Door Definition tab and configure as follows:
a. Select Elevator as the Reader Mode.
b. Make sure that 0 (zero for unassigned) is set in the Door output, Door
switch and REX switch boxes.
6. Click the Elevator tab and configure as follows:
a. Elevator mode is Normal and Elevator type is Type 1 .
Note that input configuration is only required if the elevator type is set
to Type 2 . Elevator Type 2 is "single floor latching" and must be
physically wired differently.
b. Type in the Index, Logical Floor Number , Input ID, and Output ID boxes
for the first reader as follows:
76
Index Logical Floor Number Input ID Output ID
1 0 l 1
2 1 2 2
3 2 3 3
4 3 4 4
The Index corresponds to the actual floor number. In our example, we

have two lifts that access the same four floors (1 through to 4). Note
that the first Logical Floor Number must be zero.
The Input ID and Output ID correspond to the inputs and outputs
configured for the controller under the SE Parameters display. In this
example, reader 1 is configured to use inputs and outputs 1 through to
4 and reader 2 uses inputs and outputs 5 through to 8.
7. Repeat steps 1-6 to configure the second reader point, using the following
Index numbers: Logical Floor Numbers, Input IDs, and Output IDs.
Index Logical Floor Number Input ID Output ID
1 0 5 5
2 1 6 6
3 2 7 7
4 3 8 8
8. Click Save to download changes.
Configuring the inputs under SE System

Parameters
It is not required that you set up your input definitions in any particular order.
The input number to the left of the Point Name is the Input ID that will now be
recognized by EBI and the controller. This number corresponds to the
number that we used for the Input ID on the Elevator tab for the readers.
77
Another example could be that input 1 is set for physical input 4 on MIRO 3
(i.e. Device ID = 3 and Point ID = 4). Whenever you reference input 1 for this
controller (i.e. for a door switch or lift input), it corresponds to input 4 on MIRO
3.
To configure the inputs

1. In Station, choose Configure > Access Control > SE Parameters to call up
the SE System Parameters display.
2. Select the lift controller, CONSEC1, and click the Inputs tab.
The Point Name column is populated when the input points are built and
downloaded from Quick Builder.
3. The Star II controller's on-board MIRO is always address 1, so make sure
the Device ID is 1 when using the on-board MIRO. If you have multiple
MIROs, set the appropriate address in the Device ID column for the MIRO
to which you will be physically connecting your inputs (if used).
4. Set the Point IDs to the physical input on the MIRO, such as 1 through to
8.
This depends upon the MIRO connected, for example 16/8, 4/2, and so
on.
5. The Configuration corresponds to the End-Of-Line-Resistor (E)
configuration you are using on your inputs. The Normal State is Open .
6. Set an Input Action so point changes are reported to EBI. Use the default
SE‐ACTION1 .
Configuring the outputs under SE System

Parameters
In this example, we will configure the outputs from the on-board MIRO and
four more relays from an external MIRO.
To configure the outputs

1. In Station, call up the SE System Parameters display (Configure >
Access Control > SE Parameters) and select your lift controller.
Note that the Point Name does not have an entry here because there
were no output points built in Quick Builder.
78
3. The on-board MIRO has four relays and we will use four more relays from
the external MIRO (address 2) as an example.
The Star II controller's on-board MIRO is always address 1, so make sure
the Device ID is 1 for points 1-4 (the four relays on the on-board MIRO).
The external MIRO uses its first four relays, so the Device ID is 2 for Points
5-8, as shown below.
Point Name Device ID Point ID
1 1 1
2 1 2
3 1 3
4 1 4
5 2 1
6 2 2
7 2 3
8 2 4
4. Set the Point IDs to the physical input on the MIRO, i.e. 1 through to 4 for
points 1-4 (Device ID 1), then 1 through to 4 for points 5-8 (Device ID 2),
as shown above.
Creating a floor access time period

Now create a time period for when a valid card is required for access, that is
when the elevator floor access is locked down. You set up time periods for the
times you want the floor(s) to be in the AUTO state and a valid card is needed
to access them. When the time is outside of this schedule, access to floors is
allowed without cards (ACCESS mode).
In this example, a time period named LiftSecure will be set for when cards are
required (all hours except between 8am and 5pm, Monday to Friday).
To create a floor access time period

1. In Station, choose Configure > Access Control > Time Periods call up the
Time Periods display.
79
2. Click in a blank line to call up the Time Period Definition display and
create a new time period named LiftSecure.
3. Type in a description and choose the location to which the controller
belongs from the Location list.
4. Choose NexSentry+ from the Details for list.
6. Set the time period details for when a valid cad is needed to access the
floors, as shown below.
Configuring the Elevator tab under SE System

Parameters
Configure the Elevator tab to assign the time period created in the previous
section to each of the four floors so that they allow access with a valid card for
all hours except between 8am to 5pm, Monday to Friday.
To configure the Elevator tab

1. In Station, call up the SE System Parameters display (Configure >
Access Control > SE Parameters) and select your lift controller.
2. Click the Elevator tab.
3. Set the Time group to LiftSecure for floor numbers 1 through to 4.
80
Creating access levels for lift access

We will create two new access levels. One access level will give access to
valid cardholders to all floors by both lifts at all times. The other access level
will be for Lift1 with access to floors 1 and 2 only.
To create access levels

1. In Station, go to the Zones display (Configure > Access Control > Zones).
If you have been following this example, you will see zones for the two
readers (Lift1 and Lift2) and four zones for the floors (FloorA,
FloorB, FloorC, and FloorD).
2. Go to the Access Levels display (Configure > Access Control > Access
Levels).
3. Click an available access level and configure as follows to allow access by
valid cards to all four floors from either reader, 24 hours a day.
a. Type a name for the access level, for example, Lift .
b. Type in the Zone names and Time period as follows. Note that TP1 is
the default time period that requires cards to access locations 24 hours
a day.
Zone Time period
FloorA TP1
FloorB TP1
FloorC TP1
FloorD TP1
Lift1 TP1
Lift2 TP1
4. Create another access level and configure as follows to allow cardholders

access to floors 1 and 2 from Lift1.
Use the same time periods that provide access to normal doors within the
system. Normal access to floors, for example, between 7am and 10pm,
could be named time period 'NormalTP'.
81
a. Type a name for the access level, for example, Floors 1 and 2 .
b. Type in the Zone names and Time period as follows:
Zone Time period
FloorA NormalTP
FloorB NormalTP
Lift1 NormalTP
5. Create other access levels as desired.

Creating cardholders and assign access levels for

lift access
When all the configurations for lift access control have been finalized,
cardholders can be assigned lift access levels.
To create cardholders and assign access levels

1. Create cardholders and assign cards and access levels as desired.
2. Test the operation of the cards.
82
CHAPTER
9 TROUBLESHOOTING
This section assumes you have followed each checklist in this guide and are
experiencing exceptional issues.
Common problems
This section describes issues you may encounter and their resolution.
Problem connecting to some of the controllers

You have followed all the instructions in this guide, and cannot connect to or
read from only some of the controllers in your implementation.
Diagnostic check
Connect timeout and read timeout may be too low. Check by experimenting
with these values.
Cause
The controller may be slow to respond (especially if all 16 doors are being
used).
Solution
1. Open the Quick Builder project for your installation.
2. Select the channel on which you are experiencing the errors.
3. Increase the values for the Connect Timeout and Read Timeout until the
controller begins to work correctly.
One of the channels fails due to excessive errors

The LAN or serial connections produce a high number of errors.
83
Chapter 9 - Troubleshooting
Diagnostic check
You may need to adjust the channel's tolerance for errors. Check by
experimenting with these values.
Cause
The line may be noisy.
Solution
Adjust the channel's tolerance for error.
EBI does not receive any states from monitor inputs

EBI does not receive any states from monitor inputs.
TIP: HyperTerminal is no longer provided with Windows and Windows

Server. You should refer to the manufacturer's documentation to find
out how to complete this task without using HyperTerminal.
Diagnostic check
Set the option Print to terminal in the SE Actions display, then connect
Hyperterminal to the terminal port to see whether the controller is displaying
communications activity.
Cause
There may be an addressing, controller, or even a wiring problem.
Solution
Troubleshoot the problem using this diagnostic check.
Troubleshooting procedures
Additional procedures for use during troubleshooting follows.
84
Adjusting a channel's tolerance for error

If the LAN or serial connections produce a high number of errors, you may
need to adjust the channel's tolerance for error.
LANVendor should never have more than four controllers assigned to any
one channel.
To adjust a channel's tolerance for error

1. Open the Quick Builder project for your installation.
2. Select the channel on which you are experiencing the errors.
3. A rule of thumb is to set the Marginal Alarm Limit to the square root of the
number of controllers on the channel multiplied by 25. Examples:
Number of controllers on channel Enter
1 25
2 35
3 43
4 50
5 56
6 61
7 66
8 71
9 75
10 79
15 97
20 112
4. Set the Fail Alarm Limit to twice the Marginal Alarm Limit. For example,
when the Marginal Alarm Limit is 25, set the Fail Alarm Limit to 50.
5. If these values prove insufficient, experiment by increasing the marginal
and fail limits to see whether adjusting these values fixes the problem you
85
are experiencing.
6. Download the Quick Builder project to EBI.
86
CHAPTER
10 BACKGROUND INFORMATION
This section provides background information about security, doors and

points. It does not provide direction for completing a project, but provides
information that is essential to completing the work.
Related Star II documents

This manual assumes you have an installed EBI and have a functioning
system. If that is not the case, refer to the following documents:
n Installation Guide for EBI

n Configuration Guide for EBI
n Security Electronics Access Control Configuration Guide
For information about the Star II, see:
n NexSentry Star II Access Control Unit User Guide

n NexWatch Star Controller Flash Memory Upgrade Instructions
For manufacturer information about the Micro Cobox, see:
n Lantronix Embedded Integration Kit User Guide
Star II names
During its life, the Star II has several different names. If you see these names
in EBI, they refer to the Star II:
n Star II
n Security Electronics
n SE
n NexSentry Plus
n NexSentry+
When you see NexSentry and NexSentry Plus, or NexSentry and
NexSentry+ in a list, the NexSentry refers to the Star II's predecessor, the
Star I. When you see Star in a list, it is likely to refer to the Star I, rather than
the Star II.
87
Chapter 10 - Background information
Understanding building security

Access control involves controlling and monitoring employee and visitor
access to a building or site, or specific parts of it, at different times of the day or
night.
Everyone is issued with a card which they present to card readers before
attempting to enter restricted locations. The card reader grants access if the
cardholder has the required access rights.
Some access control functions are optional. Ask your supervisor or an
experienced colleague for the list of options applicable to your system.
Understanding zones, time periods and access levels

In order to understand how EBI controls a cardholder's access, you need to
understand the relationship between zones, time periods, and access levels.
Zones
A zone represents a physical space that is totally enclosed by card readers.
This means that to enter a zone, you must present your card to a card reader.
When the controller recognizes that your access to the zone is valid, it allows
you to enter the zone. The following figure shows a floor layout with two
zones: Human Resources and Pay Office.
88
To get into the Pay Office, you need to use your card twice: first to get into
Human Resources, and then to get into the Pay Office.
You should plan the zones carefully. The system is easier to manage if you
have a large number of zones with only a small number of readers in each.
This provides more flexibility than attempting to have a large number of
readers included in a zone. Also, the zones must be an accurate
representation of the physical spaces within the building.
A zone is defined whenever the first access point for the zone is defined in
Quick Builder. Zones can also be added and modified within Station.
Zones are paired with time periods and included in access levels.
Time periods
A time period represents a specified set of times, during which associated
cardholders have access to the required zones.
For example, there might be two time periods:
Time period Access allowed
Standard Monday to Saturday (excluding holidays)
7:00am to 9:00pm
Payroll Monday to Friday (including holidays)
8:30am to 5:00pm
Time periods control access to the building or site by forming part of an access
level. Time periods are paired with zones and are then included in an access
level in order to specify when access to a particular zone is allowed.
Time periods are also used:
n To automatically open or close sections of the building

n With the Guard Tour option to specify when guards should arrive at a
control point
n With the Lighting Control option to specify when lights are turned on or off
Access levels
An access level consists of a zone and a time period. For example, the
following access levels may be defined:
89
Access level Details
Staff Consists of only one zone/time period pair:
l Human Resources (zone), and Standard (time period)
Pay Consists of two zone/time period pairs:
l Human Resources (zone), and Payroll (time period)

l Pay Office (zone), and Payroll (time period)
Using the above examples, a card belonging to:
n An ordinary staff member would have the Staff access level.

n A payroll officer would have the Pay access level.
In more complex systems, a card may be assigned many access levels. For a
card to be granted access, one of those access levels must include the zone
that the cardholder is attempting to access, paired with a time period that
includes the current time.
You should carefully plan the access levels so as to minimize the number of
access levels required. This makes administering and maintaining the system
much easier.
Understanding anti-passback
Anti-passback is designed to prevent a cardholder from gaining access to a
particular zone then passing the card to someone who uses it to enter the
zone.
Anti-Passback requires that card readers control access to and exit from the
zone. When a cardholder gains entry to the zone, the anti-passback system
registers them as being 'in' the zone. It will not provide their card access to the
zone. So it defeats card pass-back. Only after the cardholder presents their
card to a card reader to exit the zone does the system then provide access
into the zone again.
Anti-Passback is commonly used in car parks or high security environments
where it is critical that only valid cardholders may enter a zone.
Two types of Anti-Passback can be used in with the Star II and EBI:
n Controller-based Anti-Passback
n Perimeter Global Anti-Passback (PGAP)
90
Controller-based anti-passback
The simplest way to implement anti-passback functionality is through the
controller. However, this requires all card readers controlling the entry and
exit points of the anti-passback zone to be connected to a single controller.
Controller capacity or reader distance can prevent this configuration.
To implement controller-based Anti-Passback, see the controller
documentation.
Perimeter Global Anti-Passback

If you want to implement anti-passback across readers attached to multiple
controllers, you can use Perimeter Global Anti-Passback (PGAP). PGAP
requires card readers to control all entry and exit points of the perimeter of the
anti-passback zone. EBI enables PGAP by spanning multiple controllers.
Understanding how EBI and Star II control doors

Understanding how EBI and Star II control doors requires you to understand:
n Door devices.
n Basic door configuration.
n How the controller monitors and controls door devices.
n How EBI provides indirect control of the door devices.
n More complex door configurations.
A basic door configuration

Controllers and EBI track the 'functional' parts of the door—the card reader,
lock, sense and request to exit (REX) device, as shown below.
91
The Star II monitors the functional parts of the door by storing information
consisting of measurements and states within its memory. Each piece of
information about each functional part is stored in a specific memory address
on the controller. The Star II records events, such as cards being presented to
the reader, and states, such as whether the door is open, closed or forced. It
keeps a history of events and states. And it controls the door by firing the relay
that controls the lock.
EBI indirectly monitors and controls the door. It is indirect because the Star II
monitors and controls the door directly, then it communicates with EBI.
EBI obtains the events and states of the functional parts of the door by
examining Star II's memory addresses. The collection of memory addresses
that store information about each functional part of the door is collected
together in EBI by what is known as a 'point'.
EBI points
An EBI point contains the current status of the functional part it represents,
and it provides the ability to control its target. When configured to do so, it can
collect the history of measurements or states, generates alarms entering
certain states, and can be programmed to control its target.
A point has a name (a tag), and a Point ID unique within the EBI system. It is
also configured to 'know' which controller and which memory addresses
within the controller contain various elements of information that make up a
point. In EBI, these various pieces of information are known as 'point
parameters'. Each point parameter belongs to an EBI point, and has a
physical address within the Star II controller. Point parameters have names
like PV (present value), OP (output), MD (mode), SP (set point).
The points typically used to collect information about the door devices are
explained in the following table.
92
Table 10-1: Device and address types
Star
Device type II address Associated EBI point
type
Card reader ACCESS An access point monitors card usage, reporting

events such as 'access granted' and 'access denied'.
Hand reader
You use this point to obtain details about card usage.
For example, you would request a report on this
point to find out when a particular cardholder has
passed through the door.
Lock LOCK A status point that controls the lock.
Strike Normally, the point is controlled by the card reader.

However, you control it manually in Station when you
Drop bolt unlock the door for visitors, or for staff who have
Magnetic lock forgotten their cards.
Crash bar
Sense OPEN A status point monitors the door's open / closed

status.
For example, it raises an 'open too long' alarm if

someone holds the door open longer than allowed.
Request to Exit operates A status point monitors the status of the REX switch.
(REX) switch through Activating the switch may open a door, or simply
OPEN prevent an alarm being raised when opening it.
Point naming conventions

Points are generally named so that technicians and operators can easily
identify the point's location in the building, its function, its controller and
relationship with other points. This is typically achieved by adopting a naming
convention that includes the following elements:
Element Description
Floor Indicates the floor number.
Controller Indicates which controller monitors the door. Enables you to

Number or Code understand the structure of the system.
93
Element Description
Door Number or Identifies the door to the building inhabitants.

Name
Function Identifies the function of the point.
For example, the points for the 'main door' might be named as follows:
n F1_ACU01_MAINDR_RD for the card reader

n F1_ACU01_MAINDR_LK for the door lock
n F1_ACU01_MAINDR_SN for the door sense
n F1_ACU01_MAINDR_RX for the REX switch
The naming convention makes it easier for you and the operators. For
example, if you need to unlock a door, you would unlock the door's 'LK' point.
More complex door configurations

The table titled 'Device and address types' lists a range of devices that provide
alternatives for configuring on a door. It is possible to combine the devices:
n Placing a REX device in the door handle which, when the handle is
turned, causes the relay controlling the strike to be activated
n Controlling access to a door by combining a card reader and a hand
reader—where both devices must be activated in order to gain access
n Configuring two card readers on either side of a single door as two logical
doors—in order to implement anti-passback using a single door
The next section describes alternative configurations to implementing anti-
passback.
Door configurations for anti-passback

There are a variety of physical considerations for successful design of an anti-
passback system:
n Preventing tail-gating
n Accurately determining when the cardholder has entered the zone
n Allowing all cardholders to exit the zone quickly in the event of an
emergency
n Using card readers to exit a zone
94
The next two sections describe alternative configurations to address these

issues.
Anti-passback using two doors

To correctly identify when someone has entered a zone, the door must be
monitored by a door sense. Using the door sense ensures that the controller
waits until the door opens—signaled by the door sense—before changing the
cardholder status as having entered the new zone. Without this, the controller
assumes that the cardholder gains access to the new zone when the card is
presented to the reader; if the cardholder is interrupted before entering the
door, the system prevents access on the second presentation of the card to
the reader. For this reason, a door sense is recommended in anti-passback
zones.
A typical Anti-Passback installation is shown in the previous figure. Door 1

uses a one way mechanical turnstile, which grants access when a card is
presented to reader 1. Door 2 uses an electro-mechanical turnstile with an
emergency release, which under normal conditions, grants the cardholder
permission to pass through when a card is presented to reader 2.
95
Anti-passback using a single door

To configure a single door for traffic in both directions, install a reader for each
direction. In the figure below, the door is used for two-way traffic. Cardholders
use reader 4 to enter the zone and reader 3 to exit the zone. The door has a
sense.
This single door must be configured on the controller as two logical doors.
Sharing the door sense between logical door 1 (direction 1) and logical door 2
(direction 2) tells the controller that the REX and alarm states must be
processed differently.
The door must have two different relays to control the door lock. It checks the
state of logical door 2 before card reading for exit and door sense processing,
but does not check the state of logical door 1's lock relay. So if logical door 2
starts in an auto unlocked state and access is granted for logical door 1, then
after the unlock time expires the relay for logical door 1 will re-lock. (If there is
only one lock relay, it means the lock relay for logical door 2 will also have re-
locked, since it is the same physical relay.)
Ensure you use two separate lock relays and wire them in parallel. Then if
either logical door is unlocked the lock will be energized. This means that for
the physical door to be locked, both logical lock relays must be locked.
96
Understanding communications topology

between server and controller
Star II communicates using three main communication methods:
n LAN communications using the Micro Cobox terminal server

n Serial communications using RS-232
Each of method has multiple options in terms of physical wiring and
communications configurations. Each choice has differing impact on network
reliability and server efficiency.
About topology
Topology refers to the physical, electrical and communications protocols
employed, as well as how the physical cabling is laid out and connected
together.
About channels
The server that communicates with a controller on a single RS-232 is said to
communicate on a single channel. While an RS-232 channel usually
precludes having multiple controllers on it, NexSentry have modules that
enable this, which is called multidropping. The decision about whether to use
one channel per controller, or multidrop controllers onto a channel, is an
97
important one because it affects server efficiency. It affects server efficiency

because the server dedicates one scan task per channel and one network
client per channel: having 50 channels means having 50 scan tasks and 50
network clients on a server; whereas multidropping could reduce the number
of scan tasks and network clients significantly, improving server performance.
While the concept of a channel derives from its use across a single physical
link, the concept—and its performance implications—applies to LANs.
Fundamentals
The server has fundamental facts that affect the discussion of network
topology and the choices you face in configuring the system.
Item Number
Controllers per server 255
Channels per server 99
Scan tasks per channel 1
Controllers per terminal server channel (when using an on-board 1

terminal server)
Controllers per LANVendor channel 4
LAN options
Using a LAN is the most flexible and manageable method of having a Star II
communicate with a server. If you have a choice between LAN or serial,
choose LAN.
When you communicate using LAN, the server provides two drivers:
n Terminal Server
n LANVendor
Each driver has its own capabilities that are important for you to consider in
light of the networking hardware being used for a project.
One terminal server per controller

The Star II can have an optional Micro Cobox terminal server mounted on its
J4 connector. The Micro Cobox connects a single controller to the LAN.
98
When you configure this topology with a Terminal Server driver, you will have
a single channel per controller. This implies you will have a maximum of 99
controllers, and a scan task per controller.
When you configure this topology with a LANVendor driver, you can add up to
four controllers per channel (although Honeywell recommend three per
channel). So the LANVendor driver enables up to 255 controllers with its own
Micro Cobox to communicate with the server.
LAN multidropping
When you use an external terminal server, you have the capability to
multidrop controllers on the one channel.
99
Honeywell recommends you use the Terminal Server driver in this

configuration.
Occasionally you will have an installation which calls for LANVendor: where
you have a large number of terminal servers (more than 99), but few
controllers connected to each terminal server.
You could also connect the RS-232 connection in the figure shown above
directly to the server.
Three communications settings enable the server to communicate with each
controller:
Item Description
IP address Identifies the terminal server on the network.
Port Addresses the network port on which the terminal server

number communicates with the controllers.
100
Item Description
Controller Addresses an individual controller. (Each controller on a channel must

number have a unique controller number.)
Serial options
Serial communications provide a direct and low-cost way of linking Star II
controllers with the EBI server. Honeywell recommend using LAN
configurations over RS-232 if at all possible, for reasons of overhead and
supporting server redundancy.
RS-232
RS-232 links straight from the server's COM ports directly to the RS-232
interface on the Star II. RS-232, by itself, is limited to a range of 50 feet,
without specialized cables. This type of connection requires a 'crossed' RS-
232 cable.
Extending RS-232 range with a short haul modem

Short haul modems are devices that do not require an external power source
other than the RS-232 signal. Short haul modems extend the range of RS-
232 to miles. (Consult the manufacturer's notes for greater precision on
range.)
101
Remote Star II panels require either dial-up modems or short haul modems
that provide carrier control. The recommended setup is for the modem at the
server end set for constant carrier and modems at the Star II panels set for
switched carrier.
Multidropping with RS-232

The Star II interface supports multidropping from the single RS-232 serial line
using Star II CI-1 and CI-8 modules.
CI module Maximum controllers Recommended controllers
CI-1 8 7
CI-8 64 7
102
Ideas for speeding up implementation

These checklists provide some ideas for getting a smoothly-running project
before you even go on-site and when you first arrive on-site.
Task Go to Done?
Check that you have all required "Information checklist" on the

information. next page
Call the site contact. "Site contact" on page 105
Call the IT system administrator. "IT Administrator contact" on

page 106
Check that you have all required

equipment.
Task Go to Done?
Walk through the installation with the "Site contact walkthrough" on
103
Task Go to Done?
site contact. page 107
Work through the IT checklist. "IT checklist" on page 108
Ensure the EBI checklist is complete. "EBI checklist" on page 108
Information checklist
When the project manager tasks you with commissioning a system, check all
the information they give you. This information has already been obtained
from the customer, and they are expecting you to know what they want.
If there is anything in this list you do not have, obtain it from the project
manager or sales organization. Obtaining this information up-front prevents
project delays.
Information Yes?
Primary contact name and phone number.
Street address, building number and floor numbers.
Floor plan specifies number and location of server(s) and Station(s).
Floor plan has each access control door marked.
Floor plan or list contains each controller, and indicates which doors are
controlled by which controller.
Floor plan or list clearly specifies the communication method (LAN, RS-232)
between each Star II and the EBI server.
Wiring diagram showing how to wire doors, switches and readers to the
controller.
Floor plan or list has each door option described:
l single or double
l card reader
l door contact
l maglock
l electric strike
104
Information Yes?
l REX push button

l REX motion detection
l REX latch switch
l sonalert
l intercom
Floor plan names each zone, and indicates which doors control access to
each zone.
List indicates all required time periods.
List indicates all required access levels.
List indicates all required user groups.
System policies, such as zone enforcement or anti-passback, are described.
Site contact
The main purpose of phoning the site contact is to obtain the name, phone
number and possibly email of the person responsible for the LAN.
It is useful to introduce yourself and let the site contact know when you will be
on-site to begin commissioning.
Ensure you get this information.
What to obtain
Information Yes?
IT system administrator
Name
Phone number
Email address
105
IT Administrator contact
The main purpose of ringing the system administrator is to introduce your
needs of them ahead of time. This can help smooth the project when you get
on-site, even if they don't prepare what you ask them to.
When you call the system administrator, ensure you discuss each of these
points.
What to discuss
Discussion points Yes?
State that you will be installing _____ number of servers and _____ number of
Stations on the network.
State that you will be installing _____ number of controllers on the network.
(One controller on the network per Micro Cobox terminal server.)
State that your system uses static IP addresses. Therefore you need a block
of _____ static IP addresses allocated for your use. (Number of servers +
Number of Stations + Number of Micro Cobox cards.)
Discuss where each Micro Cobox-equipped controller will be located, and

ask whether there is a LAN port nearby. (You may need to email the floor
plan to the administrator.)
Having established the locations of the Micro Cobox-equipped controllers,

ask the administrator whether the server and the controllers sit on the same
subnet.
If not, ask whether there are routers, gateways or bridges between the server
and the Micro Cobox-equipped controllers.
Are there are routers, gateways or bridges? YES | NO
If there are routers, gateways or bridges between the server and the Micro
Cobox-equipped controllers, notify the administrator that you will need IP
addresses and ports opened up between the server and the controllers.
l For LANVendor channels, you will need one IP address per controller
opened on port 3001.
l For Terminal Server channels, you will need one IP address per Micro
Cobox, and one port {3001, 3002, 3003 ...} per controller.
(You can use different port numbers. These are just the suggested default.)
106
Site contact walkthrough

When you arrive on the site, ensure you walk through the installation with the
site contact, or their nominated representative. Explain to the site contact
what you intend to install, how the zones and schedules will work, and how
the system will function.
At each door and controller location, look for the following items.
What to check
Item Yes?
Is the proposed controller location accessible to service personnel in the

event of an emergency?
Is the proposed controller a minimum of 6 feet from AC panels, motors,

pumps, and so on?
Is the proposed controller location a minimum of 3 feet from telephone

cabling equipment?
Is the proposed controller location free from corrosive fumes and vapors?
Is the proposed controller location within 25 feet of its power supply
Is the proposed reader location free from RF interference, such as:
l Air conditioning systems

l Arc welders
l Diathermy machines
l Electric motors
l Elevator lift motors
l Fluorescent lighting
l Industrial equipment
l Radio transmitters
l Relay panels
l PC monitors
l Telephone switching panels
107
Item Yes?
Is the proposed reader location free from direct sunlight?
Is there an ethernet port for each controller being connected via LAN?
IT checklist
Meet with the IT system administrator to confirm network details prior to
beginning work. Meeting with the system administrator first enables them to
implement any changes you may require by the time you need them, rather
than slowing you down later.
What to check
Item Yes?
Ensure you know the block of available IP addresses.
For each controller being connected via the LAN, confirm that the ethernet
port near the controller is live.
Ask the administrator whether the server is on the same subnet as each of
the controller locations.
Where controllers are being installed on the LAN, ask for the:
l IP address of the gateway.

l Subnet mask in use on the network.
If the server is not on the same subnet, ask the administrator whether the
router, gateway or bridge ports you need for communications have been
opened.
Plug in the server, then check that each ethernet-connected controller port
can communicate with the server via the necessary ports.
EBI checklist
Ensure the EBI is consistent with the following prerequisites prior to working
through this guide.
108
What to check
Prerequisite Yes?
EBI is correctly installed.
EBI locations have been configured.
109
110
Notices
NOTICES
Honeywell Trademarks
IdentiPoint® is a U.S. registered trademark of Honeywell International, Inc.
Other trademarks
Microsoft and SQL Server are either registered trademarks or trademarks of
Microsoft Corporation in the United States and/or other countries.
BACnet® is a registered trademark of the American Society of Heating,
Refrigerating and Air-Conditioning Engineers.
Other brands or trademarks are trademarks of their respective owners.
Trademarks that appear in this document are used only to the benefit of the
trademark owner, with no intention of trademark infringement.
How to report a security vulnerability

For the purpose of submission, a security vulnerability is defined as a software
defect or weakness that can be exploited to reduce the operational or security
capabilities of the software.
Honeywell investigates all reports of security vulnerabilities affecting
Honeywell products and services.
To report a potential security vulnerability against any Honeywell product,
please follow the instructions at:
https://www.honeywell.com/en-us/product-security.
Support
For technical assistance, contact your nearest Honeywell office.
Training classes
Honeywell holds technical training classes on Enterprise Buildings Integrator.
These classes are taught by experts in the field of building control systems.
For more information about these classes, contact your Honeywell
representative.
111
Notices
112

EBI R610.1 StarII

Uploaded by

Copyright:

Available Formats

EBI R610.1 StarII

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

EBI R610.1 StarII

Uploaded by

Copyright:

Available Formats

NexSentry Star II: A Step by Step Guide

Chapter 4 - Defining channels and controllers 35

Configuring the controller’s users 57

Chapter 10 - Background information 87

n Complete the tasks in order shown, unless specified otherwise.

Figure 1-1: The implementation process

New to security and/or the Star II

n A list of essential documents for implementing the Star II.

2 INSTALLING THE STAR II

Figure 2-1: Your location in the implementation process

Ensure all readers are connected as per installation instructions.

Ensure all REX switches are wired to an appropriate monitor input

3 GETTING A STAR II CONTROLLER

Figure 3-1: Your location in the implementation process

When you are connecting a controller to a simple LAN "Communications checklist:

When you are connecting a controller to a complex "Communications checklist:

the Star II controller page 13

Communications checklist: Using a simple LAN

Set the controller device number. "Setting the controller

If you have a Micro Cobox "Setting the Cobox baud

Select either S-NET or Wiegand "Selecting between S-NET

Set the S-NET baud rates. "Setting bus baud rates" on

Configure devices attached to the "Configuring attached

Restart the Star II controller. "Restarting the Star II

Set the Micro Cobox IP address "Setting the Micro Cobox

Test communications between the "Testing communications

Communications checklist: Using a complex LAN

Set the controller device number. "Setting the controller device

Select either S-NET or Wiegand reader "Selecting between S-NET or

Set the S-NET baud rates. "Setting bus baud rates" on

Configure devices attached to the Star "Configuring attached devices"

Restart the Star II controller. "Restarting the Star II controller"

Test communications between the EBI "Testing communications with

Communications checklist: Using RS-232

Set the controller device number. "Setting the controller

Set the terminal port baud rate. "Setting the terminal

Select either S-NET or Wiegand reader protocol. "Selecting between S-

Set the S-NET baud rates. "Setting bus baud rates"

Configure devices attached to the Star II. "Configuring attached

Restart the Star II controller. "Restarting the Star II

Plug the RS-232 connection between the COM

Setting the controller device number

To configure the controller device number

Set DIPs on switch S4 to:

0 OFF OFF OFF OFF OFF

1 OFF OFF OFF OFF ON

2 OFF OFF OFF ON OFF

3 OFF OFF OFF ON ON

4 OFF OFF ON OFF OFF

5 OFF OFF ON OFF ON

6 OFF OFF ON ON OFF

8 OFF ON OFF OFF OFF

9 OFF ON OFF OFF ON

10 OFF ON OFF ON OFF

12 OFF ON ON OFF OFF

Set DIPs on switch S4 to:

16 ON OFF OFF OFF OFF

17 ON OFF OFF OFF ON

18 ON OFF OFF ON OFF

20 ON OFF ON OFF OFF