EBI R610.1 StarII
EBI R610.1 StarII
EBI R610.1 StarII
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
4
Contents
5
Contents
Troubleshooting procedures 84
Adjusting a channel's tolerance for error 85
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.
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
Each section begins with this flowchart, showing where you are in the
implementation process.
8
CHAPTER
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 door sense switches are wired to an appropriate monitor input
terminal.
9
Chapter 2 - Installing the Star II controller
Task Done?
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
Decision
Go to the appropriate checklist.
Checklists Go to
11
Chapter 3 - Getting a Star II controller to communicate
Checklists Go to
When you are connecting a controller to the server via "Communications checklist:
RS-232 Using RS-232" on page 14
Task Go to Done?
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
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.
12
Chapter 3 - Getting a Star II controller to communicate
Task Go to Done?
LAN" on page 25
Task Go to Done?
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
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
Chapter 3 - Getting a Star II controller to communicate
Task Go to Done?
page 28
Task Go to Done?
Set the host port baud rate. "Setting the host port
baud rate" on page 17
14
Chapter 3 - Getting a Star II controller to communicate
7 OFF OFF ON ON ON
11 OFF ON OFF ON ON
15
Chapter 3 - Getting a Star II controller to communicate
13 OFF ON ON OFF ON
14 OFF ON ON ON OFF
15 OFF ON ON ON ON
19 ON OFF OFF ON ON
21 ON OFF ON OFF ON
22 ON OFF ON ON OFF
23 ON OFF ON ON ON
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
Chapter 3 - Getting a Star II controller to communicate
19200 OFF ON
38400 ON OFF
4. Record your baud rate setting because you will require it in a later
procedure.
Stop
You have completed this task. Return to the checklist that led to this task.
17
Chapter 3 - Getting a Star II controller to communicate
2. Using DIPs 3 and 4, set the host port to the desired speed. Honeywell
recommend you set this value to 9600.
19200 OFF ON
38400 ON OFF
57600 ON ON
3. Record your baud rate setting because you will require it in a later
procedure.
Stop
You have completed this task. Return to the checklist that led to this task.
18
Chapter 3 - Getting a Star II controller to communicate
19200 OFF ON
115200 ON ON
3. Record your baud rate setting because you will require it in a later
procedure.
Stop
You have completed this task. Return to the checklist that led to this task.
Switch S2
Protocol DIP 5
S-NET OFF
Wiegand ON
19
Chapter 3 - Getting a Star II controller to communicate
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.
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
Chapter 3 - Getting a Star II controller to communicate
Stop
You have completed this task. Return to the checklist that led to this task.
Switch S2 Switch S5
19200 ON ON ON ON
21
Chapter 3 - Getting a Star II controller to communicate
3. Using DIPs S2 and S5, set the S-NET 2 baud rate to 9600.
Switch S2 Switch S5
19200 ON ON ON ON
Stop
You have completed this task. Return to the checklist that led to this task.
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
22
Chapter 3 - Getting a Star II controller to communicate
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 reader
n To set the reader device number, see the NexSentry Star II Access
Control Unit User Guide.
Stop
You have completed this task. Return to the checklist that led to this task.
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
Chapter 3 - Getting a Star II controller to communicate
You have completed this task. Return to the checklist that led to this task.
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.
24
Chapter 3 - Getting a Star II controller to communicate
Here is an example of such a hosts file after several entries have been made.
Stop
You have completed this task. Return to the checklist that led to this task.
TIP: After completing the task, return to the checklist that lead to the
task.
25
Chapter 3 - Getting a Star II controller to communicate
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.
26
Chapter 3 - Getting a Star II controller to communicate
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.
Port
Value
Settings
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.
27
Chapter 3 - Getting a Star II controller to communicate
Port
Value
Settings
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
8. Click OK.
9. Click OK again.
Stop
You have completed this task. Return to the checklist that led to this task.
28
Chapter 3 - Getting a Star II controller to communicate
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.
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.
29
Chapter 3 - Getting a Star II controller to communicate
255.0.0.0 24
255.255.0.0 16
255.255.255.0 8
30
Chapter 3 - Getting a Star II controller to communicate
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.
Property Value
Baud Rate The value to which you set switch S5 DIPs 5 and
6.
Flow Control 00
31
Chapter 3 - Getting a Star II controller to communicate
Property Value
Remote IP none
address
Connect C0
Mode
Disconnect 00
Mode
Flush Mode 00
Disconnect 00:45
Time
SendChar 1 00
and 2
You have completed this task. Return to the checklist that led to this task.
32
Chapter 3 - Getting a Star II controller to communicate
You have completed this task. Return to the checklist that led to this task.
33
Chapter 3 - Getting a Star II controller to communicate
34
CHAPTER
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
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
Task Go to Done?
Create the Quick Builder "Creating a new Quick Builder project " on the
project. facing page
36
Chapter 4 - Defining channels and controllers
Task Go to Done?
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.
You have completed this task. Return to the checklist that led to this task.
37
Chapter 4 - Defining channels and controllers
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.
38
Chapter 4 - Defining channels and controllers
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:
You have completed this task. Return to the checklist that led to this task.
Consideration Evaluation
I have more than 30 controllers using on- Consider using LANVendor with three
board terminal servers controllers per channel.
39
Chapter 4 - Defining channels and controllers
Consideration Evaluation
I have many controllers (more than 99) You must use LANVendor.
using on-board terminal servers
You have completed this task. Return to the checklist that led to this task.
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
You have completed this task. Return to the checklist that led to this task.
40
Chapter 4 - Defining channels and controllers
Parity None
Stop Bits 1
Stop
You have completed this task. Return to the checklist that led to this task.
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
Chapter 4 - Defining channels and controllers
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
You have completed this task. Return to the checklist that led to this task.
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.
10. Set the Controller ID to the controller device number. (You set this
previously using the controller's DIP switches.)
42
Chapter 4 - Defining channels and controllers
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.)
13. Click Save to save the project.
14. Click .
The Download dialog box opens.
15. Click Selected items only.
16. Check that the items listed in the Summary list are those you want to
download.
17. 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.
18. 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
You have completed this task. Return to the checklist that led to this task.
To download
1. Select the controller you want to download.
2. Click .
The Download dialog box opens.
43
Chapter 4 - Defining channels and controllers
You have completed this task. Return to the checklist that led to this task.
Prerequisites
n You are logged on to Station with MNGR security level.
44
Chapter 4 - Defining channels and controllers
Stop
You have completed this task. Return to the checklist that led to this task.
echo 7/tcp
echo 7/udp
discard 9/tcp sink null
discard 9/udp sink null
systat 11/tcp users
...
45
Chapter 4 - Defining channels and controllers
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
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.
Checklist Go to
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
Task Go to Done?
Station tasks
Once-per-controller tasks
Once-per-door tasks
Task Go to Done?
48
Chapter 5 - Defining points for doors
Task Go to Done?
reader point.
Once-per-controller tasks
Once-per-door tasks
Configure the door "Configuring the definition for a single door if you
definition. use anti-passback" on page 60
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
Chapter 5 - Defining points for doors
Prerequisites
n Your EBI server has had its locations configured. Ensure you know where
your controller is located.
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.
13. Click Save to save the project.
Stop
You have completed this task. Return to the checklist that led to this task.
50
Chapter 5 - Defining points for doors
10. Click OK. The complete address now appears in the PV Source Address
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 7 Shunted
State 6
State 5
State 4
51
Chapter 5 - Defining points for doors
State 3
State 2 AutoUnlk
State 1 Unlocked
State 0 Locked
You have completed this task. Return to the checklist that led to this task.
52
Chapter 5 - Defining points for doors
OPEN DoorNumber
10. Click OK. The complete address now appears in the PV Source Address
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 0 Normal
You have completed this task. Return to the checklist that led to this task.
Downloading points
Download the points to continue their configuration in Station.
To download
1. Select the points you want to download.
2. Click .
The Download dialog box opens.
53
Chapter 5 - Defining points for doors
You have completed this task. Return to the checklist that led to this task.
Prerequisites
n You must be logged on to Station with MNGR level security.
54
Chapter 5 - Defining points for doors
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
n You must be logged on to Station with MNGR level security.
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 .
4. From the Location list, select the appropriate location.
5. If this is a vehicle zone, select the NexSentry Plus Vehicle zone option.
55
Chapter 5 - Defining points for doors
Prerequisites
n You must be logged on to Station with MNGR level security.
56
Chapter 5 - Defining points for doors
You have completed this task. Return to the checklist that led to this task.
TIP:
l HyperTerminal is no longer provided with Windows and Windows
57
Chapter 5 - Defining points for doors
You have completed this task. Return to the checklist that led to this task.
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
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 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
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.)
58
Chapter 5 - Defining points for doors
59
Chapter 5 - Defining points for doors
16. Click the Back button (or press F8) until you return to the SE Controller
Settings display.
17. When all changes have been made, click Save .
The system then validates the changes.
Stop
You have completed this task. Return to the checklist that led to this task.
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.)
60
Chapter 5 - Defining points for doors
61
Chapter 5 - Defining points for doors
You have completed this task. Return to the checklist that led to this task.
62
Chapter 5 - Defining points for doors
63
Chapter 5 - Defining points for doors
64
CHAPTER
Checklist
Use the checklist below to ensure that you have performed all the tasks
required.
Task Go to Done?
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.
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.
67
Chapter 7 - Downloading to controllers
68
CHAPTER
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.
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
69
Chapter 8 - Star II lift access control
70
Chapter 8 - Star II lift access control
71
Chapter 8 - Star II lift access control
0 ACCESS Security cards are not required. Access to the floor allowed.
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
Chapter 8 - Star II lift access control
73
Chapter 8 - Star II lift access control
State 7
State 6
State 5
State 4
State 3 Incomp
State 2 Auto
State 1 Manual
State 0 Access
74
Chapter 8 - Star II lift access control
State 7 Shunt
State 6
State 5 Short
State 4 Open
State 3 Access
State 2
State 1 Active
State 0 Normal
75
Chapter 8 - Star II lift access control
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.
76
Chapter 8 - Star II lift access control
1 0 l 1
2 1 2 2
3 2 3 3
4 3 4 4
1 0 5 5
2 1 6 6
3 2 7 7
4 3 8 8
77
Chapter 8 - Star II lift access control
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.
78
Chapter 8 - Star II lift access control
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.
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.
5. Click Save to download changes.
79
Chapter 8 - Star II lift access control
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.
5. Click Save to download changes.
6. Set the time period details for when a valid cad is needed to access the
floors, as shown below.
80
Chapter 8 - Star II lift access control
FloorA TP1
FloorB TP1
FloorC TP1
FloorD TP1
Lift1 TP1
Lift2 TP1
81
Chapter 8 - Star II lift access control
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:
FloorA NormalTP
FloorB NormalTP
Lift1 NormalTP
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.
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.
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.
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
Chapter 9 - Troubleshooting
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
Chapter 9 - Troubleshooting
are experiencing.
6. Download the Quick Builder project to EBI.
86
CHAPTER
10 BACKGROUND INFORMATION
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
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
Chapter 10 - Background information
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:
7:00am to 9:00pm
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:
Access levels
An access level consists of a zone and a time period. For example, the
following access levels may be defined:
89
Chapter 10 - Background information
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
Chapter 10 - Background information
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.
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.
91
Chapter 10 - Background information
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
Chapter 10 - Background information
Star
Device type II address Associated EBI point
type
Crash bar
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.
Element Description
93
Chapter 10 - Background information
Element Description
For example, the points for the 'main door' might be named as follows:
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.
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
Chapter 10 - Background information
95
Chapter 10 - Background information
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
Chapter 10 - Background information
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
Chapter 10 - Background information
Fundamentals
The server has fundamental facts that affect the discussion of network
topology and the choices you face in configuring the system.
Item Number
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.
98
Chapter 10 - Background information
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
Chapter 10 - Background information
Item Description
100
Chapter 10 - Background information
Item Description
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.
101
Chapter 10 - Background information
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.
CI-1 8 7
CI-8 64 7
102
Chapter 10 - Background information
Task Go to Done?
Task Go to Done?
103
Chapter 10 - Background information
Task Go to Done?
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?
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.
l single or double
l card reader
l door contact
l maglock
l electric strike
104
Chapter 10 - Background information
Information Yes?
l intercom
Floor plan names each zone, and indicates which doors control access to
each zone.
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
Chapter 10 - Background information
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
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.)
If not, ask whether there are routers, gateways or bridges between the server
and the Micro Cobox-equipped controllers.
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
Chapter 10 - Background information
What to check
Item Yes?
Is the proposed controller location free from corrosive fumes and vapors?
107
Chapter 10 - Background information
Item Yes?
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?
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:
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
Chapter 10 - Background information
What to check
Prerequisite Yes?
109
Chapter 10 - Background information
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.
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