Professional Documents
Culture Documents
Technical Training CCURE 9000 - Chapter 4 iSTAR Configuration v2.90
Technical Training CCURE 9000 - Chapter 4 iSTAR Configuration v2.90
Technical Training CCURE 9000 - Chapter 4 iSTAR Configuration v2.90
Objectives
Know how to connect and configure Inputs, Outputs and Readers to any iSTAR
Configure an iSTAR Door and all its components
Create people and get access through the door
Regardless of which iSTAR model is available for the course, we will go through the
configuration of all the components (Inputs, Outputs, Readers, Doors, Personnel etc.), and we
want to make it clear that everything you will do, can be applied to each and every iSTAR,
because the final configuration windows are always the same, regardless of the model of the
controller.
What could be slightly different in terms of hardware, are the physical connection of the objects,
and in terms of software, the sections of the configuration windows. But we will point out every
difference, and never forget the main point: the final configuration window, regardless of what
the object is, it is still the same.
Most of the iSTARs use a card called ACM (Access Control Module) to connect all the
security objects (Inputs, Outputs, Readers, Expansion Cards).
The only exception is the iSTAR Edge: being a single card, all these objects are
connected on the main board.
iSTAR LT is also a single card Controller, but it uses IP ACMs to connect the security
objects (all the Ultra family Controllers can connect to these cards called IP-ACM).
iSTAR Pro, iSTAR Ultra and iSTAR Ultra SE use these cards (ACMs): each iSTAR has
there own model of ACM, not compatible with the others controllers (except for the IP-
ACM that are the same for all the Ultra models).
Wiegand RS485
24 Inputs
8 Primary Relays
8 Secondary Relays
ACMs of the iSTAR Pro and SE have 3 banks of Dip Switch to:
The ACM of the iSTAR Ultra has dip switches to address each ACM (up to two at
present, up to four in the future), plus dip switches next to each RS485 port to
terminate it, and switches next to the Outputs connectors to choose “Dry” or “Wet”
Output.
iSTAR Edge only has dip switches to choose “Dry” or “Wet” Output.
NOTE: the quantity of objects, depends on the controller (it has been explained in the
previous chapter)
Example of connections on
the ACM of an iSTAR Ultra
RM I/8
Reader Module
The IP ACM, supported by all the iSTAR Ultra Family, acts like a door controller that
can be located next to the door, and it communicates with the iSTAR via TCP/IP (GB
port onboard, PoE compliant).
It can connect up to 2 Readers (linked to two different doors, or both on the same
door), which can be both direct Wiegand connected, or both RM connected, or one
Wiegand and one RM.
2 OSDP readers can also be connected to the IP ACM, via RS-485
The IP ACM also has 4 Inputs (supervision mode configurable per single Input, like the
iSTAR Ultra) and 2 Relays outputs onboard (wet or dry selectable per output, using a
jumper).
It also has a single rotary switch, used to reset the ACM to factory default with DHCP
(D position).
iSTAR Pro ACMs don’t require any physical address settings, they are automatically
recognized by the system when connected: they only need to be activated in the
software.
iSTAR Ultra ACMs must be physically addressed using the Dip Switch SW32 (bottom left
corner of the ACM)
SW32-2, SW32-3, and SW32-4 are not used and should be in the OFF position.
The RM bus is a 2 wire RS485 connection (plus the Power) that can be up to 1200
meters long. Using this bus you can connect RM-4/4E modules, RM Readers, I/8 and
R/8 modules. Same Pin-Outs for all the iSTARs !
When wiring a module to a bus with multiple devices, such as RM-4s, I/8s, or R/8s:
Attach the shields along the bus together (insulate each connection). Snip off the shield
wire at the end of the bus.
Attach the shield to the ground at one point only – at the ground stud inside the iSTAR or
apC cabinet adjacent to the knockout.
As said, regardless of the iSTAR used , the RM bus still has the same pin-outs and
supports RM4 and RM4-E cards, plus I/8 and R/8 Modules.
+ 12 VDC Pin 1
+TXD/+RXD Pin 2
-TXD/-RXD Pin 3
GND Pin 4
RM4
RM4-E
Pin 1
Pin 2
Pin 3
Pin 4
Pin 1
Pin 2
Pin 3
Pin 4
Pin 4
Pin 3
Pin 2
Pin 1
I/8 R/8
It is important to correctly wire and setup the Reader Bus modules address and
Termination.
Addressing: Every module from the same type must have a unique address which
goes from 1 to 8, any other values are not valid.
Termination: only the modules at the Reader bus line end must be terminated.
Any other module or board located in the middle of the bus must be unterminated.
If by chance you don’t know how many Inputs there are available in your whole
system, the license information informs you.
NOTE: (MD) = Manual Data / (IF) = Infographics / (CR) = Casi-Rusco / (AN) = Atlantek / (SP) = Simplex
NOTE: The selection for the iSTAR Edge is per Controller, for the Ultra family is per single input
NOTE: The selection for the I/8 CSI is per Card, for the IP-ACM is per single input
NOTE: The value of the resistors indicates the normal status of the Input, the double and the half
of the value means “Alarm”; any other values return the message “Line Fault”, with the indication
“Shorted” or “Open Circuit”
To monitor multiple NO points on the same input, wire the switches in parallel as
shown:
The number of normally open or normally closed detection devices each input can supervise is
limited only by the resistance of the loop. The total resistance for wire length and contacts,
minus the supervision resistors must not exceed 100 ohms.
44 C•CURE 9000 L1 – Chapter 4 iSTAR Configuration
Multiple Points on One Input - Normally Close circuit
To monitor multiple NC points on the same input, wire the switches in series as shown:
The number of normally open or normally closed detection devices each input can supervise is
limited only by the resistance of the loop. The total resistance for wire length and contacts, minus
the supervision resistors must not exceed 100 ohms.
An Output is a software object that associates an input or event action with a relay.
Outputs are sometimes referred to as Control Points.
Outputs can be triggered by inputs from our or other system or used to switch external
devices like locks or latches.
Examples of output uses include: Doors / Elevators, Alarms and Industrial Control
Dry Contact, Form C, Relays - Dry Contact means that the technician must supply
the power. Form C means that the Common (C), Normally Closed (NC), and
Normally Open (NO) connections are provided. Supported by iSTAR Pro, iSTAR
Edge, iSTAR Ultra family, R/8 Module, RM-4E Card, IP-ACM
Wet Contact, Form C, Relays - Wet Contact means that controller supplies the
power. Form C means that the Common (C), Normally Closed (NC), and Normally
Open (NO) connections are provided. Supported by iSTAR Edge, iSTAR Ultra
family
Open Collector: limited output current of 50 milli-Amps (mA). Typically used to
drive a relay contact such as the ARM-1. Supported by RM-4 Cards
With all the iSTARs you can connect any kind of Reader supporting the Wiegand
protocol (or the Mag Stripe protocol if needed), which is a two wires signal:
Wiegand protocol cannot be daisy chained and its maximum length is 150 mt.
Wiegand readers don’t have any Inputs/Outputs onboard, so the Door Contact, the
Push Button (Inputs) and the Mag Lock (Output) of the Door must be connected to the
iSTAR.
To connect the Readers in RS485, we need a module in between the head of the
reader and the iSTAR: this module is called RM4 or RM4-E card.
The main purpose of both is to convert the Wiegand into RS485, plus both have 2
Inputs and 2 Outputs onboard (we’ll see later the differences between the 2 cards) so
the Inputs and Output of the Door can be wired locally.
Each RM card is designed to control one single Reader; RM cards can take the power
from the Controller or can be powered up locally. (Standard 12VDC power supply)
We also cater for the more secure technology; OSDP Readers (Open Security Device
Protocol). These readers are connected to the RS-485 bus. [Ultra iSTAR’s
only….includes the IP-ACM] (Not covered in this L1 training)
RS485
As already mentioned, C•CURE 9000 supports readers that provide Wiegand signaling
and magnetic signaling. Wiegand signaling devices include:
Wiegand swipe readers
Proximity readers
Biometric readers
Smart card readers
Wireless readers
Some magnetic readers
Readers can be interfaced in different ways
Direct Wiegand
RM bus
OSDP is another option, but not covered in this training
Take the next 20 minutes to test yourself again, answering the easy questions on the
CCURE9000 Summary Questions.xlsx Excel file, CHAPTER 4 Section 1 ONLY.
Edit it...
Regardless of the
Controller you use,
if the Inputs are
onboard the IP-
ACM, Edit the
controller, go to the
IP ACM tab, edit
your card and go
to the Inputs tab to
configure them.
(above IP-ACM
Vers. 1, below IP-
ACM Vers. 2)
If inputs are
wired on the I/8
module
connected to
the IP-ACM,
first enable the
RS485 where
the module is
connected to,
then enable the
I/8 module and
Edit it.
Your time to configure the system: take the next 20 minutes to practice with the
exercises on page 126 of the Workbook.
Use the Workbook for reference if needed: if there are any problems, ask
the trainer.
Similar to the Inputs configuration, regardless of the controller you use, before you can
configure any Output, you must configure the card where the output is connected to.
NOTE: The next set of slides show the Input configuration on iSTAR Ultra/SE: for the
others controllers, follow the links iSTAR Pro or iSTAR Edge
NOTE: Outputs on the iSTAR LT can be connected only via IP ACM (next subject)
Edit it...
Regardless of the
Controller you use, if the
Outputs are onboard the
IP-ACM, Edit the
controller, go to the IP
ACM tab, edit the card
and go to the Inputs tab
to configure them.
If the outputs are wired on the R/8 module connected to the IP-ACM, first enable the RS485
where the module is connected to, then enable the R/8 module and Edit it.
81 C•CURE 9000 L1 – Chapter 4 iSTAR Configuration
Outputs Configuration: IP-ACM
Configure your Outputs now: take the next 20 minutes to practice the exercises
on page 133 of the Workbook.
Use the Workbook for reference if needed: if there are any problems, ask
the trainer.
Go to the Triggers Tab. Add a trigger to activate an Output when the Input is in Active state.
From the Monitoring Client you can create Manual Actions on system objects like:
Disarm an Input (NOTE: is not possible to manually Activate any Input)
Activate/Deactivate/Pulse an Output (if you want to Pulse an Output, don’t forget to set the
Pulsing time first, in the Output configuration window. The time is in Tenth of Seconds)
Go to the Explorer bar and select Hardware Status. Open the Input or Output menu.
Most actions have an End time; when reached the object will return to its normal state.
You can cancel any manual action before this time is reached using the Manual Action
menu from the Non Hardware Status or with a right click on the action Icon.
Take the next 30 minutes to practice the exercises on page 139 of the
Workbook.
Use the Workbook for reference if needed: if there are any problems, ask
the trainer.
Placing an object in Maintenance Mode does not prevent actions from occurring. For
example, if an event assigned to an intrusion zone in Maintenance Mode activates an
output that turns on the building-wide evacuation alarm, the activation of the output will
still occur.
Take the next 20 minutes to practice the exercises on page 145 of the
Workbook.
Use the Workbook for reference if needed: if there are any problems, ask
the trainer.
If Readers are RM
connected, you must first
activate the RS485 port
you want to use and then
activate the Reader.
The Index number is the
RM card address number
Take the next 20 minutes to practice the exercises on page 152 of the
Workbook.
Use the Workbook for reference if needed: if there are any problems, ask
the trainer.
Take the next 30 minutes to practice the exercises at page 156 of the
Workbook.
Use the Workbook for reference if needed: if there are any problems, ask
the trainer.
Once you finish the door configuration, the reader should be able to detect the card
(present it to the reader) and you will see the message in the monitoring station.
Let’s have a look to the possible reasons why a card could be rejected:
[card misread] = the card format read by the reader doesn’t match that specified in
the software.
[facility code] = the value of the facility code specified in the software doesn’t
match the one configured on the card read by the reader
[site code] = the value of the site code specified in the software doesn’t match the
one configured on the card read by the reader.
[card unknown] = the card read by the reader is not loaded in the CCURE9000
database.
[card not activated] = the card is not activated (activation date wrong or not yet
reached).
You got a “Card Misread” message: “card format in the reader configuration doesn’t
match what was physically presented at the reader”
When we configured the readers, we left the card format blank, and that’s the reason
for this message: readers don’t know what they have to read.
The card format is the reader-head data protocol, expected when presenting a card.
Your card may have been rejected, most likely because of “site” or “facility” code
reasons (you may also get the message “rejected unknown” or “Card Misread”).
What are Site and Facility codes? Basically, numbers: nothing else than this. They are
security codes the card uses to try to make itself unique in the world.
So how can we know their values? There are different ways to achieve this, but normally
the card manufacture provides these information. Two of the most popular cards are 26
or 37 bits: in the following slides we are going to show their bits information.
One of the most common card formats is the Wiegand 26 bit. It consists of a 16 bit Card
Number, an 8 bit Facility Code and 2 parity bits.
Another format is the Software House proprietary 37 bit format. This format has a Site
Code field as well as a Facility Code field.
We may face a problem if the end user already has their cards and wants to integrate
them into CCURE: can this be done ?
99% of the times, yes (if the card technology is compatible with our readers), BUT we
have to know the card format and all the details.
Once you know the Length of the card, one need to determinate what the Facility and
Site Codes are.
If you use a standard format (26 or 37 Bits) then you know the position on the
encoding string (see previous slides), so it is only a matter of counting the binary bits
in that position and converting their value into decimal (Windows calculator can help
you); if you don’t use a standard card format then we recommend reading at least 10
cards and check the values that never change: those are the Facility and Site Codes.
But for this training we use a standard format, so take note of the length of your card,
and calculate the Facility and Site Codes.
You must build the card parity in order to have a valid read from the card. The parity is
an added security for the card reading.
The Even parity ensures that the “1” bits from bit 2 till the middle of the format
gives a even number.
The Odd parity ensures that the “1st” bit from the middle of the format till the end
gives an Odd number.
Go to the Hardware main menu, Edit your readers and at the bottom, assign the card format
you’ve just created.
Take the next 30 minutes to practice the exercises on page 167 of the
Workbook.
Use the Workbook for reference if needed: if there are any problems, ask
the trainer.
Again present the card to the reader and observe on the monitor station what
message you get.
The message should be “Unknown card”. (if you still get “facility code” and/or “site
code” go back to your card format and check the values).
Unknown card means that the card is not loaded in the database, so let’s create it.
In the General Tab enter the First Name, Last Name and select Employee as the
Personnel Type.
Note: The Last Name is a mandatory field, and cannot be left blank.
In the Credential tab add a Card Access by entering the card number. Each Card holder can
have up to 5 Cards Access (only 1 by default). We’ll see the other fields later on.
When the card is admitted, the Monitoring Station reports the Access Granted
message and only the name of the person assigned to that card: sometimes is needed
to display the Card Number as well…
Go to System Variables in the
Options-Tools menu.
Set the Monitoring variable to
display card numbers on reads,
as shown beside. (double click
on the row to change the value).
Take the next 15 minutes to practice the exercises on page 169 of the
Workbook.
Use the Workbook for reference if needed: if there are any problems, ask
the trainer.
Again present the card to the reader and observe on the monitor station what
message you get this time.
It should be “Clearance”. (Notice that this time the card displays the name you inserted
previously, so the system recognize it).
Clearance codes define the time and the location at which an access card is valid.
With clearance codes, you can associate the following objects:
Doors or door groups
Elevators or Elevator groups
Floors or floor groups
You can assign up to 1000 clearances per cardholder (default is set to 10).
There is not limit on the total amount of clearances for the complete system.
NOTE: This number of Clearance (1000) is valid starting from version 2.60, only for
iSTAR Ultra. Previously the maximum number of clearances was 150 and the default
was 10 (this later value is still valid for iStar Pro and Edge).
Holiday Elevator
Schedules
Groups Elevator Gr.
Elevator
Holidays Clearance
Clearance
Go to Options and Tools Menu and select the Personnel options from System
Variables. Here you can modify the maximum number of Clearance per Person. You
must stop the iSTAR driver before making the changes.
Add all the Date/Time Intervals for this particular Schedule. The access schedule
normally is the same for people that belong to the same department.
Take the next 10 minutes to practice the exercises on page 172 of the Workbook.
Use the Workbook for reference if needed: if there are any problems, ask
the trainer.
Enter a name. If needed you can enable the Clearance Activation Status, to set an
Activation and Expiration Date.
Here you create the link between Doors (Door Groups) and
the Schedule.
Go back to the Personnel menu, edit the people you created and in the Clearance
tab add as many clearance as needed for each cardholder.
A new feature in 2.8 version, allows to prevent the deletion of clearances assigned to personnel
records.
To enable it, there’s a new value in the System Variables / Personnel section.
Take the next 20 minutes to practice the exercises on page 174 of the Workbook.
Use the Workbook for reference if needed: if there are any problems, ask the
trainer.
Now that we have a door fully configured, we can better appreciate how powerful the new
Monitor and Associations features are.
Go to the Hardware menu, right click on your Door and select Monitor. Click on Show
Children at the top to see which objects compose your door.
From that window, right click on your Door and select Show Associations to see which
Clearances are linked to that door.
NOTE: The Security View feature works similar to an Even Assessment layout, to display object
associated to the main one. We will cover it in L2 training.
An expiring clearance (configured on the Clearance General tab) allows a Start Date/
Time & End Date/Time to be applied when assigning the Clearance to a Personnel
record.
From version 2.4, you have the ability to use new context menu commands to quickly
create an exact duplicate of a fully configured iSTAR Cluster or individual iSTAR
Controller (including all their child objects) with the fewest clicks and least amount of
configuring. You can also use the new “Copy To/Paste From” commands to duplicate
iSTAR Cluster/Controller configurations on other Partitions or systems.
When copying a panel which has panel events associated with it, the panel events are
copied but not assigned to the panel. The panel must be assigned manually after the
copy is completed and host events must be reconfigured.
It is also possible to copy (save) objects on local or remote hard drives to paste them
into different systems….
In the System
Variables menu it is
possible to define
how many iSTAR can
use the fast
personnel download
simultaneously
(iSTAR Drivers
Section) (iSTAR
Driver needs to be
stopped and started)
Take the next 20 minutes to test yourself again , answering the easy questions on the
CCURE9000 Summary Questions.xlsx Excel file, CHAPTER 4 Section 2.
Return
229 C•CURE 9000 L1 – Chapter 4 iSTAR Configuration
Inputs on iSTAR Pro
If you move to the Inputs tab, what you see here are
the 16 Inputs onboard the ACM
If you need to configure any of them, simply put a tick
on the one you want to activate and click on Edit to
configure it.
This cannot be done during this training because we
don’t have supervised resistors to apply and you
would get the “supervision error” message.
Return
Return
233 C•CURE 9000 L1 – Chapter 4 iSTAR Configuration
Outputs on iSTAR Pro
Return
Return
237 C•CURE 9000 L1 – Chapter 4 iSTAR Configuration
Inputs on iSTAR Edge
Return
Return
240 C•CURE 9000 L1 – Chapter 4 iSTAR Configuration
Outputs on iSTAR Edge
Return
This page is the same for all the iSTARs (Pro/Edge/Ultra), unless the controller has the
firmware version greater than 6.5.4.20747.
iSTAR
iSTAR
If you want to enforce Username and Password for all the iSTAR family, you have to
modify one parameter in System Variables of the system (Options and Tools/ iSTAR
Drivers Menu), the Diagnostic Web Page Password (max 16 characters). When you
change the PW with the System Variable, the new value will apply to all iSTARs,
including the Ultras.
If you select Remember Credential, when prompted to enter the password, the iSTAR will
remember the password until its memory is cleared.
Return