Keri-systems Doors.NET Manual Manual do Utilizador

Doors.NET Reference Manual- 1 -Welcome to Doors.NETWelcome to Doors.NET- a comprehensive software suite that addresses access control,intrusion monito

Doors.NET Reference Manual- 10 -customers that have this feature enabled on theirlicense). A number of new categories have been added to the tradition

Doors.NET Reference Manual- 100 -Key Featuresl Record on Event - Define what is to be recorded and when & whether triggeredby access hardware or b

Doors.NET Reference Manual- 101 -Related Topics* Supported Video Equipment List* Reflections EVR - Camera Setup

Doors.NET Reference Manual- 102 -Supported Video EquipmentIP cameras/models supported directly by the current implementation of Doors.NET.Axis- 205 ne

Doors.NET Reference Manual- 103 -- M1011 Camera- M1011W Camera- M1031W Camera- M3011 Camera- P1311 Camera- P3301 Camera- P3301-V Camera- Q6032E (PAL)

Doors.NET Reference Manual- 104 -- DG-NS202 Network Camerav.1.11 or later- WV-NS202 Network Camera- DG-NS202A Network Camerav.2.60 or later- WV-NS202A

Doors.NET Reference Manual- 105 -PiXORD- Network CameraStarDot- NetCam network camera- Express 6 Video Server

Doors.NET Reference Manual- 106 -

Doors.NET Reference Manual- 107 -

Doors.NET Reference Manual- 108 -EVR Client - Camera SetupCameras can be added to Doors.NET through the standard administrative client orthrough the R

Doors.NET Reference Manual- 109 -3. Click on the Add Camera button.4. Enter a description/name for the camera.5. From the 'Source' drop-down

Doors.NET Reference Manual- 11 -System Architecture OverviewThe core software module is the Application Server. This component communicates withthe SQ

Doors.NET Reference Manual- 110 -6. Add a description for the camera.7. For the initial adding of the camera, the 'Video Buffer' and 'R

Doors.NET Reference Manual- 111 -11. Set the stream type to match what the camera is setup as (In the camera prop-erties).12. Set the recording frame

Doors.NET Reference Manual- 112 -Linking to Hardware1. To link the camera to a hardware object in Doors.NET (such as a reader) right-clickon the camer

Doors.NET Reference Manual- 113 -2. Use the drop down list to find the reader on the system that you wish to associatewith the newly added camera. (Yo

Doors.NET Reference Manual- 114 -4. On the ribbon bar you will see a Live Video icon.5. Click this icon and a live video window will appear in the cli

Doors.NET Reference Manual- 115 -6. Once you are at this stage you can now setup a filter to be assigned to the readerand will allow you to create Eve

Doors.NET Reference Manual- 116 -NuVision Interface ClientHelp content section under development.

Doors.NET Reference Manual- 117 -Photo ID ClientPortions of this chapter created under license from:Photo ID is an optional software module in the Doo

Doors.NET Reference Manual- 118 -Logging Inl Click/double-click on the 'Keri Photo ID Icon' located on the desktop or via Start >>All

Doors.NET Reference Manual- 119 -l On the left-hand pane (User Manager) you will see two nodes: Cardholders andPhotoID Layouts, right-click PhotoID La

Doors.NET Reference Manual- 12 -The Doors.Net Gateway connects to up to 64 NXT controllers (256 reader capability,standard license, using 4 readers pe

Doors.NET Reference Manual- 120 -Toolbarl New, Open, Save, Cut, Copy and Paste buttons: Perform commonly used Win-dows commands.l Undo and Redo button

Doors.NET Reference Manual- 121 -l Font Style buttons: Allow you to change the style of the selected font (bold, italic,underline).l Horizontal Justif

Doors.NET Reference Manual- 122 -Creating New Card DesignsWhen you launch the designer, it automatically opens a blank layout. You can create anew lay

Doors.NET Reference Manual- 123 -Opening an Existing Card File1. On the File menu, click Open, or click the Open button on the Toolbar. The Opendialog

Doors.NET Reference Manual- 124 -3. If your card design is in another drive or directory, browse to it using the Look Inlist. You will only be able to

Doors.NET Reference Manual- 125 -mapped to your PC or available from your Network Neighborhood.4. Click OK.Saving a Previously Saved Card DesignAfter

Doors.NET Reference Manual- 126 -Enhancing the Card BackgroundWhen a background image is added to a card design, the Enhance button on the appro-priat

Doors.NET Reference Manual- 127 -To crop the background image, drag one of the eight sizing handles that appear on theOriginal Image until the image h

Doors.NET Reference Manual- 128 -If your card media comes with the background image preprinted on it, you can stillinclude the image file in the layou

Doors.NET Reference Manual- 129 -2. Select a printer. The default printer (as specified in the Windows Printers controlpanel) appears in the list. To

Doors.NET Reference Manual- 13 -What's New In This ReleaseDoors.NET Version 3.5.1.19Operating System CompatibilityOperating System 32-Bit 64-BitW

Doors.NET Reference Manual- 130 -If you want to print cards to a sheet printer from your application, you will need to setparameters such as page marg

Doors.NET Reference Manual- 131 -You can add headers or footers to your card layout that will appear at the top and bottomof the printed card or sheet

Doors.NET Reference Manual- 132 -Note: This option is used for single card printing or batch printing.When you choose the Print command, you will have

Doors.NET Reference Manual- 133 -1. On the File menu, click Page Setup. The Page Setup dialog box appears with thePage Setup tab showing.2. Select the

Doors.NET Reference Manual- 134 -4. Click OK.Selecting Page SizesDifferent types of ID cards come in different sizes dependent on the types of cards a

Doors.NET Reference Manual- 135 -3. Select the required card size from the options listed in the Size list, or select Cus-tom Size to specify your own

Doors.NET Reference Manual- 136 -5. Click OK.Note: These settings will automatically be the same for both the front and back of thecard layout.Adding

Doors.NET Reference Manual- 137 -2. Draw the image object (as described in “Draw an Object”). The Open dialog boxappears when you release the mouse bu

Doors.NET Reference Manual- 138 -2. Change the Image Type by choosing from the list.Note: These options will differ depending on the product you have

Doors.NET Reference Manual- 139 -If you want to add effects to your dynamic images, it’s a good idea to select a sampleimage so you can preview the ef

Doors.NET Reference Manual- 14 -New FeaturesNew Hardware Release:l The GIOX (Greater I/O Board) has been released for use by NXT and MercuryPowered NX

Doors.NET Reference Manual- 140 -field,enter an amount of variation from the selected color, or enter 0 for an exactcolor match.Color Variation -This

Doors.NET Reference Manual- 141 -softwarewill scan and remove all of the brighter shades of green across 30 percent ofthecolor spectrum. In other word

Doors.NET Reference Manual- 142 -the appropriate level of opacity. This option uses the same algorithm as a ghostoption.l Gray scale: Select this opti

Doors.NET Reference Manual- 143 -1. Select a new color from the Color list, or click the ellipses button next to it tochange the shadow color. The Mic

Doors.NET Reference Manual- 144 -It is important to know that your Photo ID license will need to be ‘revoked’ if you wish tomove your Doors.NET badgin

Doors.NET Reference Manual- 145 -7. You will also see the following text highlighted in red: Click the Exit button.You are now able to re-activate the

Doors.NET Reference Manual- 146 -Report ClientThe system has a built-in report designer that allows you to create a new report fromscratch or to modif

Doors.NET Reference Manual- 147 -Roll Call ClientThe Doors.NET Roll Call Client has been developed to provide you with a graphical rep-resentation of

Doors.NET Reference Manual- 148 -presents their card to an 'In' reader the occupancy count increments, when they badge atan 'Out'

Doors.NET Reference Manual- 149 -By default the Photo Window will appear next to the main Roll Call window. If you wantto be able to make the Photo wi

Doors.NET Reference Manual- 15 -l None at this time.Unique to ASSA WiFi/POE Lock Hardware:l None at this time.Unique to IR/Schlage Lock Hardware:l Non

Doors.NET Reference Manual- 150 -5. Click on the Readers tab. On the right you will see a list of all the readers on thesystem.6. Generally, most of t

Doors.NET Reference Manual- 151 -When cardholders badge their card at the exit reader, to leave the building, the occu-pancy count will automatically

Doors.NET Reference Manual- 152 -they are immediately checked into all the roll call areas that the reader belongs to.Manual Overrides1. A manual Chec

Doors.NET Reference Manual- 153 -a printer at specified intervals.Roll Call Advanced must be enabled on your license. To check this, click on the Lice

Doors.NET Reference Manual- 154 -4. Close the Manage Areas page and return to the main window.5. Select the new muster area from the area selection dr

Doors.NET Reference Manual- 155 -3. To generate the muster report click on the refresh button.4. The muster report for the area currently being monito

Doors.NET Reference Manual- 156 -Time and Attendance ClientThe Time and Attendance optional component provides a generic interface directly to aSQL or

Doors.NET Reference Manual- 157 -Gateway WizardThe Gateway Wizard allows system administrators to add a Gateway to the Doors.NETsystem. The Gateway en

Doors.NET Reference Manual- 158 -3. Under the Gateway Selection pull-down list, select the gateway type that matchesyour hardware.l Keri - NXT Series

Doors.NET Reference Manual- 159 -Start/Restart the Gateway1. Review the displayed information.2. If something needs to be corrected, click BACK to ret

Doors.NET Reference Manual- 16 -Unique to PXL Controllers:l Made a number of gateway improvements to accommodate network timing con-ditions in medium

Doors.NET Reference Manual- 160 -Multiple Concurrent GatewaysBeginning with Doors.NET v3.5.1.19, the software is capable of running multiple con-curre

Doors.NET Reference Manual- 161 -Gateway Type PXL NXTMercuryPoweredNXTStandardMercuryASSAAperioASSAWiFi/POEIngersollRandIntervals per Day 4 12 12 12 1

Doors.NET Reference Manual- 162 -Gateway Type PXL NXTMercuryPoweredNXTStandardMercuryASSAAperioASSAWiFi/POEIngersollRandNumber ofAccessGroupsunlimited

Doors.NET Reference Manual- 163 -Gateway Type PXL NXTMercury PoweredNXTStandardMercuryASSAAperioASSAWiFi/POEIngersollRandGlobal APB NO NO YES YES YES

Doors.NET Reference Manual- 164 -Temp Door UnlockSince each door type has a different set of temp unlock time parameters, the softwareuser interface w

Doors.NET Reference Manual- 165 -Global Unlock/Lock and Situation ManagerThe Global Unlock/Lock features used by PXL controllers in Doors32 are also a

Doors.NET Reference Manual- 166 -Miscellaneous Feature Differences Between Hardwarel The Local Linkage feature is not yet available for PXL controller

Doors.NET Reference Manual- 167 -Language SupportDoors.NET software is written in a native Microsoft .NET environment. The .NET Frame-work provides ex

Doors.NET Reference Manual- 168 -Perform the following steps if you do not see your language when the login screenappears.l Clear the Use Default Lang

Doors.NET Reference Manual- 169 -l Click the Use Default Language check-box to return to the default language of USEnglish.Software TranslationTo tran

Doors.NET Reference Manual- 17 -l Corrected an issue with event display filtering.l Implemented new WiFi/POE drivers provided by ASSA. Driver version

Doors.NET Reference Manual- 170 -Configuration FilesHelp content section under development.

Doors.NET Reference Manual- 171 -Software UpgradesSoftware upgrades are automatically handled by the installation program. The install-ation program a

Doors.NET Reference Manual- 172 -Software TourThe following sections will help you get familiar with using the software:l System Architecture Overview

Doors.NET Reference Manual- 173 -Navigating The SoftwareThe software has three main working areas:1. Top - Toolbar and Ribbon - provides access to all

Doors.NET Reference Manual- 174 -Using the ToolbarThe Toolbar provides quick access to basic system tasks.Clicking the Keri Kiwi logo opens a menu scr

Doors.NET Reference Manual- 175 -Using the RibbonThe Ribbon provides access to all software features. Access is divided between ribbontabs (which brea

Doors.NET Reference Manual- 176 -l User Manager - all task icons are related to the management of user access rightsin the systeml Status - all task i

Doors.NET Reference Manual- 177 -Using GridsDepending upon the task being performed, the work space/data display area caninclude a grid of parameters,

Doors.NET Reference Manual- 178 -Create a New Pull-down Menu OptionSeveral of the grid screens allow you to create pull-down menu options to be used i

Doors.NET Reference Manual- 179 -

Doors.NET Reference Manual- 18 -l PXL controllers require firmware revision 8.6.09.l Legacy PXL controllers should be at firmware revision 8.4.49 or g

Doors.NET Reference Manual- 180 -Status TabsStatus tabs are found at the bottom of the work space/data display field.l Certain status tabs only appear

Doors.NET Reference Manual- 181 -l Alerts - lists events that require acknowledgement by an operatorl Audit - list information on actions performed by

Doors.NET Reference Manual- 182 -AlertsThe Alerts Status Tab opens a window that lists events that require acknowledgementby an operator.Selecting an

Doors.NET Reference Manual- 183 -l Cardnumber - The card number associated with this event (if applicable).l First Name - The first name of the cardho

Doors.NET Reference Manual- 184 -Audit StatusContent in development.

Doors.NET Reference Manual- 185 -Control PointsThe Control Points status window displays the status of all configured control points.Click on the Cont

Doors.NET Reference Manual- 186 -ControllerThe Controller Status window displays the status of all recognized controllers. Click onthe Status tab at t

Doors.NET Reference Manual- 187 -Disconnect - Immediately disconnect from this controller.Reset - Immediately reset this controller or peripheral.Requ

Doors.NET Reference Manual- 188 -DoorsThe Doors status window displays the status of all configured doors. Click on the Doorstab at the bottom of the

Doors.NET Reference Manual- 189 -l History - Opens the History Status window for that door.l Properties - Opens the Hardware Setup window for that doo

Doors.NET Reference Manual- 19 -TranslationsCompleted Translations:l Chinese (Simplified)l Chinese (Traditional/Taiwan)l English (UK)l French (France)

Doors.NET Reference Manual- 190 -History StatusContent in development.

Doors.NET Reference Manual- 191 -Live EventsLive Events Status displays real-time transactions as they occur and includes systemmessages with the newe

Doors.NET Reference Manual- 192 -

Doors.NET Reference Manual- 193 -Monitor PointsThe Monitor Points status window displays the status of all configured monitor points.Click on the Moni

Doors.NET Reference Manual- 194 -Trace EventsThe trace events grid displays specific messages that you are interested in seeingwithout the distraction

Doors.NET Reference Manual- 195 -3. Select a reader on the system from the Reader drop-down list.4. Note that since trace events are grouped by the tr

Doors.NET Reference Manual- 196 -6. The context menu from the trace events window allows for the following selections:Start and Stop Trace - allows yo

Doors.NET Reference Manual- 197 -Hardware OverviewNXTThe NXThardware platform provides unmatched system flexibility, ease of use, and costeffectivene

Doors.NET Reference Manual- 198 -l Can be used in combination with an NXT-6RK keypad for Card+Pin at one or bothof the doorsReader Interface Modulel F

Doors.NET Reference Manual- 199 -network capabilities, thereby allowing the controller to become an IP addressable net-work device. It can then be acc

Doors.NET Reference Manual- 2 -3. Performance figures and data quoted in this document are typical, and must be spe-cifically confirmed by Keri System

Doors.NET Reference Manual- 20 -Release HistoryPrevious Releases:l v3.5.1.18l v3.5.1.17l v3.5.1.16l v3.5.1.15l v3.5.1.14l v3.5.1.12 - SP-2l v3.5.1.11l

Doors.NET Reference Manual- 200 -NXT ControllersThe NXT-2D/4D Xtreme Door Controller is built for today’s IT environments. With Eth-ernet functionalit

Doors.NET Reference Manual- 201 -Weight (In Enclosure)l 4D - 5.00 Lbs (2.27 Kgs)l 2D - 4.95 Lbs (2.25 Kgs)Input Voltagel + 12 VDC nom. (10 - 14 VDC)Cu

Doors.NET Reference Manual- 202 -Wiring Diagram

Doors.NET Reference Manual- 203 -4x4 I/O BoardThe NXT-4D Input/Output Expansion Module provides functionality to any Doors.Netaccess control system by

Doors.NET Reference Manual- 204 -Size (PC Board)l 5.25” H x 3.10” W x 1” Dl 13.33 cm x 7.87 cm x 2.54 cmWeight (In Enclosure)l 2.5 Lbsl 1.14 KgsInput

Doors.NET Reference Manual- 205 -Wiring Diagram

Doors.NET Reference Manual- 206 -Greater I/O Board (GIOX)The Greater I/O Board (GIOX) provides functionality to any Doors.Net access control sys-tem b

Doors.NET Reference Manual- 207 -SpecificationsSize - KE-8 Enclosurel 15.75" H x 17.50" W x 6.625" Dl 40.00 cm x 44.45 cm x 16.83 cmSiz

Doors.NET Reference Manual- 208 -Module PlacementMother Board and individual modules are installed using 6-32 screws provided in theproduct ship kit.

Doors.NET Reference Manual- 209 -Wiring Diagrams

Doors.NET Reference Manual- 21 -Operating System 32-Bit 64-Bit2003 Yes Yes2008 Yes Yes2008 R2 Yes Yes2012 N/A Yes(1) The ASSA gateway is not yet Windo

Doors.NET Reference Manual- 210 -Mother Board

Doors.NET Reference Manual- 211 -

Doors.NET Reference Manual- 212 -Input ModuleOutput Module

Doors.NET Reference Manual- 213 -NXT ReadersKeri’s NXT Series Proximity Readers are designed to blend aesthetics, read range per-formance, and small p

Doors.NET Reference Manual- 214 -NXT-1R Euro Mount ReaderNXT-3R MullionReaderNXT-5R Wall Switch ReaderSpecificationsSizeNXT-3Rl 3.75” H x 1.6” W x 0.6

Doors.NET Reference Manual- 215 -Input Powerl NXT-1R 10 to 14 VDC @ 110 mA typicall NXT-3R 10 to 14 VDC @ 110 mA typicall NXT-5R 10 to 14 VDC @ 110 mA

Doors.NET Reference Manual- 216 -Reader Interface Module (RIM)The Reader Interface Module (RIM) is a plug-in, peripheral device that allows Keri MSfor

Doors.NET Reference Manual- 217 -to Keri MSReader500 feet152meters6 Y Y N 22 9536to WiegandReader500 feet152meters7 Y Y N 22 9537Wiring DiagramRIMCon

Doors.NET Reference Manual- 218 -Enter RIM Programming Mode1. Hold down both SW1 and SW2 for about two seconds.2. All seven LEDs on the RIM will flash

Doors.NET Reference Manual- 219 -LE-DReader TypeD4Keri MS Series- factory default settingD5 WiegandD6 not usedD7 not usedLED ControlD1 single wire LED

Doors.NET Reference Manual- 22 -including varying restriction levels of lock and unlock and the ability to assign/un-assign specific doors. The Situat

Doors.NET Reference Manual- 220 -NXT Mercury-Powered ControllersThe NXT-2D/4D Mercury-Powered controllers bring enhanced capability to the Door-s.NET

Doors.NET Reference Manual- 221 -Main Controller Featuresl Decentralizes system intelligencel Network ready with on-board Ethernet adapterl Quick-disc

Doors.NET Reference Manual- 222 -l Cardholder Capacity - 10,000 - 100,000l Access Groups per cardholder - 8 by default by configurable from 1 - 32l Tr

Doors.NET Reference Manual- 223 -l -40° F to 140° Fl -40° C to 60° Cl 0-90% Non CondensingCommunicationl To Server: TCP/IP 10/100 busl Between Control

Doors.NET Reference Manual- 224 -Mercury FamilyContent in development.

Doors.NET Reference Manual- 225 -PXL ControllersThe PXL hardware platform provides sophisticated access control solutions for up to 256doors at a sing

Doors.NET Reference Manual- 226 -PXL-500 Tiger II Controller PXL-500 Controller With EnclosureSpecificationsSize (Enclosure)l 13” H x 9 W x 4” Dl 33.1

Doors.NET Reference Manual- 227 -SB-593General Purpose (8), 2 are configurable asrequest to exit and door sense for 2nd doorOutputsPXL-500Form C Lock

Doors.NET Reference Manual- 228 -Wiring DiagramPXL

Doors.NET Reference Manual- 229 -MS Series ReadersAs with all Keri’s Proximity Readers, they are designed to blend aesthetics, read rangeperformance,

Doors.NET Reference Manual- 23 -Unique to PXL Controllers:NOTE: For PXL installations, Keri strongly recommends upgrading to the 3.5.1.18release to ta

Doors.NET Reference Manual- 230 -MS3000XMicrostarReaderMS-4000ShootingStar ReaderMS-5000 Mini Star ReaderMS-7000 MiniStarReaderSpecificationsMS-3000 M

Doors.NET Reference Manual- 231 --40° C to +65°CLED IndicatorTri-Color Standard (Red, Green, Amber)not supported in the MS-4000Audio ToneStandardnot s

Doors.NET Reference Manual- 232 -SB593 Satellite Expansion BoardThe SB-593 Satellite Expansion Board plugs directly onto the PXL500 to provide anaddit

Doors.NET Reference Manual- 233 -LAN-520 ModuleThe LAN-520 module provides low cost network capabilities to a PXL controller network- allowing the con

Doors.NET Reference Manual- 234 -oFlexible, well-developed IP protocol stackoTTL Level serial interface (asynchronous)oTwo serial portsoHTTP, serial,

Doors.NET Reference Manual- 235 -Basic System SetupThe basic system setup section is broken up by hardware type:Standard NXT Controller configurationM

Doors.NET Reference Manual- 236 -Basic NXT Controller ConfigurationThis document covers the basic configuration of NXT controllers in Doors.NET softwa

Doors.NET Reference Manual- 237 -5. Click the All tab and the NXT gateway appears at the top of the hardware tree.6. Highlight the NXT gateway in the

Doors.NET Reference Manual- 238 -8. By default, all controllers are selected. An IP address must be assigned to eachcontroller.9. Enter an IP address

Doors.NET Reference Manual- 239 -17. A green progress bar appears to the right of the controller information providing avisual indication of upgrade p

Doors.NET Reference Manual- 24 -l If you deleted an elevator controller from the hardware tree before deleting elevatoraccess groups, you could not re

Doors.NET Reference Manual- 240 -When you have made changes to the hardware, click the blue save icon at the top of theproperties frame and the change

Doors.NET Reference Manual- 241 -4. Highlight the new schedule and the description displays in the properties frame.5. An inactive Interval is also ad

Doors.NET Reference Manual- 242 -2. Click the Add icon in the Holidays icon group and a default new holiday will beadded.3. Highlight the new holiday,

Doors.NET Reference Manual- 243 -2. Click add and a new group name appears. Optionally you can give it a descriptivename.3. While still highlighted, s

Doors.NET Reference Manual- 244 -Enrollment assigns credentials to the cardholder records and cardholders can have mul-tiple credentials assigned to t

Doors.NET Reference Manual- 245 -7. The new cardholder will be immediately sent out to the network and is able to gainaccess at any reader that is in

Doors.NET Reference Manual- 246 -Basic PXL Controller ConfigurationThis document covers the basic configuration of PXL controllers in Doors.NET softwa

Doors.NET Reference Manual- 247 -3. Click the Setup tab then click Hardware Setup.4. Click the All tab and the PXL gateway appears at the top of the h

Doors.NET Reference Manual- 248 -l a serial connection (from the PC’s physical COM port, a recommended USB toSerial adapter, or a Keri USB Comm Module

Doors.NET Reference Manual- 249 -Modem Connection1. Highlight the Communication Channels node in the hardware tree.2. Click the Modem Communication Ch

Doors.NET Reference Manual- 25 -Firmware RequirementsFor NXT controllers and peripherals:l Standard NXT controllers require new firmware revision 2.05

Doors.NET Reference Manual- 250 -Ethernet ConnectionNOTE: The LAN-520 unit must already be programmed with a static IP address, gate-way, and subnet p

Doors.NET Reference Manual- 251 -Perform an Auto ConfigurationTo detect the slave PXL controllers on the network you must perform an auto-con-figurati

Doors.NET Reference Manual- 252 -5. The final step is to click the Apply button.6. A prompt appears confirming how many controllers are selected. Clic

Doors.NET Reference Manual- 253 -9. The slave controllers all have Update Required icons displayed indicating the PXLnetwork needs to be updated. To u

Doors.NET Reference Manual- 254 -software upgrade is performed from Doors.NET software revisions prior to v3.5.1.18.This results in increasing network

Doors.NET Reference Manual- 255 -Basic Mercury-Powered NXT ControllerConfigurationThis document covers the basic configuration of Mercury Powered NXT

Doors.NET Reference Manual- 256 -6. The scan feature requires the third-party software application, Bonjour for Win-dows, to be downloaded and install

Doors.NET Reference Manual- 257 -When a static IP address is assigned, that controller keeps that IP address unless a hardreset is performed, returnin

Doors.NET Reference Manual- 258 -8. You can also see from the above image that a gateway IP address can be set tothe controller, thereby allowing comm

Doors.NET Reference Manual- 259 -4. If a firmware upgrade is needed, the required revision is listed in the Status Mes-sages grid. Close the AutoConfi

Doors.NET Reference Manual- 26 -l French (France)l Polishl Russianl Slovenianl Spanish (Castilian)l TurkishTranslations Pending Updates *:l Arabic (UA

Doors.NET Reference Manual- 260 -Basic ASSA Aperio ConfigurationDoors.NET supports integration with the Aperio series wireless locks manufactured byAS

Doors.NET Reference Manual- 261 -Requirementsl Doors.NET software must at least be version 3.5.1.15 or greaterl The number of Aperio readers must be e

Doors.NET Reference Manual- 262 -There is an 8-pin terminal block on the reverse of the hub for making the wiring con-nections to the controller.RS-48

Doors.NET Reference Manual- 263 -Adding to the NXT Mercury Powered ControllerHighlight the controller’s bus in the hardware tree and select from the A

Doors.NET Reference Manual- 264 -Addressing the HubThe address of the hub is determined by Doors.NET. Refer to the Comm Address field inthe hub proper

Doors.NET Reference Manual- 265 -BusNumber8-PortHub1-PortHub 11-PortHub 21-PortHub 31-PortHub 41-PortHub 51-PortHub 61-PortHub 71-PortHub 82 2 23 24 2

Doors.NET Reference Manual- 266 -Home TasksThe Home Tab provides access to the most commonly used tasks for User/Cardholdermanagement, system monitori

Doors.NET Reference Manual- 267 -Automation TasksAutomation Tasks provide methods to automatically perform defined sets of operationswhenever certain

Doors.NET Reference Manual- 268 -CardholdersThe Cardholders tab provides access to all cardholder enrollment, management, andsearch tasks.On the Home

Doors.NET Reference Manual- 269 -1. Under the Download icon group, use the Controllers pull-down menu to selecteither all controllers or a specific co

Doors.NET Reference Manual- 27 -Operating System 32-Bit 64-BitWindows Server2003 Yes Yes2008 Yes Yes2008 R2 Yes Yes2012 N/A Yes(1) The ASSA gateway is

Doors.NET Reference Manual- 270 -Cardholder SearchThere are two cardholder search types: Basic and Advanced.Basic Cardholder SearchBasic Searches are

Doors.NET Reference Manual- 271 -l Search String - for searches requiring that a text string be matchedl Access Group - for searches associated with A

Doors.NET Reference Manual- 272 -Cardholders Access RightsThe Access Rights page displays a list of all the access groups that have been definedon the

Doors.NET Reference Manual- 273 -When using the PXL family of hardware only 1 access group can be assigned to eachcardholder. An alert message will ap

Doors.NET Reference Manual- 274 -Cardholders AdvancedThe advanced options tab contains additional options for each cardholder record. Theseare options

Doors.NET Reference Manual- 275 -The Vacation Settings selections are used to designate a date range for the cardholderto be on vacation. During the s

Doors.NET Reference Manual- 276 -Cardholder Contact TabThe contact information tab provides selections to enter additional contact informationabout se

Doors.NET Reference Manual- 277 -Cardholder Company Contact Inform-ationThe company contact tab provides selections to enter additional company relate

Doors.NET Reference Manual- 278 -The Hire Date is a date selection and is automatically defaulted to the date that the card-holder was added to the sy

Doors.NET Reference Manual- 279 -Cardholder NotesThe Notes field allows you to enter/store any kind of text information you deem of valueregarding the

Doors.NET Reference Manual- 28 -l An Elevator Override Schedule feature has been added allowing the enabling offloor access via a schedule. This featu

Doors.NET Reference Manual- 280 -Cardholders Custom tabCustom Cardholder InformationThe Custom fields allow you to enter information you specifically

Doors.NET Reference Manual- 281 -Custom.l An input box will appear allowing you to enter a new description, then click OK.l The header label displays

Doors.NET Reference Manual- 282 -Cardholder Photo ID TabThe cardholder Photo ID tab is used to select and then an image to a cardholder'srecord.

Doors.NET Reference Manual- 283 -Cardholder NotesThe Notes field allows you to enter/store any kind of text information you deem of valueregarding the

Doors.NET Reference Manual- 284 -Cardholder Notes tabCardholder NotesThe Notes field allows you to enter/store any kind of text information you deem o

Doors.NET Reference Manual- 285 -Cardholder Enrollment Edit FormThe Cardholder Edit Form allows you to perform cardholder enrollment and informationma

Doors.NET Reference Manual- 286 -Review/Edit Door Configuration Parameters section under Setup Doors).NXT Manual Enrollment1. Uncheck the Calculate In

Doors.NET Reference Manual- 287 -4. Click the Add Card button. The credential is now entered into the database.5. Click the icon in the upper-left cor

Doors.NET Reference Manual- 288 -4. Click the Add Card button. The credential is now entered into the database.5. Click the icon in the upper-left cor

Doors.NET Reference Manual- 289 -4. For a 26-bit Wiegand credential, enter the credential facility code into the FacilityCode field.5. Click the Statu

Doors.NET Reference Manual- 29 -l Added the ability to set operator permissions for viewing the status menu. Pre-viously, all operators could view the

Doors.NET Reference Manual- 290 -7. Click the icon in the upper-left corner of the window to save the cardholderenrollment.Keri MS and Wiegand 26-bit

Doors.NET Reference Manual- 291 -5. Click the Add Card button. The credential is now entered into the database.6. Click the icon in the upper-left cor

Doors.NET Reference Manual- 292 -3. Repeat this for the Expire Date.4. For tracking purposes you can use the Expiration Reason pull-down menu to enter

Doors.NET Reference Manual- 293 -3. For tracking purposes you can use the Expiration Reason pull-down menu to entera reason for the Date Range.4. Clic

Doors.NET Reference Manual- 294 -Enter Advanced OptionsAdvanced Options are special features that may or may not apply to cardholders. Cur-rent Advanc

Doors.NET Reference Manual- 295 -2.Click the icon.3. You will be asked to confirm activation for all credentials. Click the Yes Button.4. You will be

Doors.NET Reference Manual- 296 -2. A confirmation window appears for each removal. Click the Yes Button.3.Once all credentials are removed, click the

Doors.NET Reference Manual- 297 -1. Click the Template Entry box to enable the Cardholder Templates tab and click onthe tab to open the Templates wind

Doors.NET Reference Manual- 298 -Block EnrollmentBlock Enrollment allows an Operator to create a generic set of credentials (using con-secutive creden

Doors.NET Reference Manual- 299 -Date as 365 days from enrollment. The Total Access template selection auto-matically sets Total Access access rights

Doors.NET Reference Manual- 3 -Software OverviewWhat is Doors.NET?Doors.NET is Keri Systems' flagship software product. Designed to manage Keri S

Doors.NET Reference Manual- 30 -l Corrected an issue with the "Check With Host" feature. If a reader has this featureenabled the controller

Doors.NET Reference Manual- 300 -

Doors.NET Reference Manual- 301 -Access GroupsAccess Groups are combinations of readers and the time schedules at which the readersshould be active. T

Doors.NET Reference Manual- 302 -5. In the Readers field, select the Readers to be added to this Access Group.6. In the Schedules field, select the Ti

Doors.NET Reference Manual- 303 -Downloading Access Groups to ControllersAccess Groups can be immediately downloaded to controllers if needed.1. Under

Doors.NET Reference Manual- 304 -3. A removal confirmation window appears. Click the Yes Button.4. The Access Group is removed from the list.Clear Sel

Doors.NET Reference Manual- 305 -HolidaysHolidays are designated calendar days used to define exceptions to Time Schedules. Aholiday overrides the nor

Doors.NET Reference Manual- 306 -Creating a New Holiday1. Click the Add icon in the Holidays icon group.2. A new holiday is added to the list with a g

Doors.NET Reference Manual- 307 -Click the Yes Button. Once saved, the date is highlighted in bold text on the calendar.5. Under Properties:l Enter th

Doors.NET Reference Manual- 308 -6. Click in the Show All Holiday Dates tick-box to have all existing holidays high-lighted in bold text on the calend

Doors.NET Reference Manual- 309 -Downloading Holidays to ControllersHolidays can be immediately downloaded to controllers if desired.1. Under the Down

Doors.NET Reference Manual- 31 -Firmware RequirementsFor NXT controllers and peripherals:l Standard NXT controllers require new firmware revision 2.05

Doors.NET Reference Manual- 310 -Time SchedulesThe system uses Time Schedules to support access levels, local linkage, and automaticoverride modes for

Doors.NET Reference Manual- 311 -There are three default time schedules. The first two schedules cannot be deleted fromthe system.l Always Active appl

Doors.NET Reference Manual- 312 -3. In the grid, enter the time interval values for this time schedule.

Doors.NET Reference Manual- 313 -4. In this example the time interval is set for Tuesday and Thursday between 19:00and 21:00 hours (7 to 9 PM). It is

Doors.NET Reference Manual- 314 -10. Enter the descriptive Time Schedule name in the description field of the grid, clickthe save button in the grid,

Doors.NET Reference Manual- 315 -1. Under the Downloads icon group, use the Controllers pull-down menu to selecteither all controllers or a specific c

Doors.NET Reference Manual- 316 -Scan - Honor Day of WeekWhen using the Scan - Honor Day of Week setting then the Schedule will always oper-ate on the

Doors.NET Reference Manual- 317 -Setup TasksThe Setup Tab provides access to the most commonly used tasks for hardware setupand manual/override operat

Doors.NET Reference Manual- 318 -Hardware SetupThe Hardware Setup options provide access to hardware configuration, hardware main-tenance, and manual

Doors.NET Reference Manual- 319 -l Setup All - opens the All grid and displays the system hardware configuration in atree view format. This allows you

Doors.NET Reference Manual- 32 -Mercury Hardware Firmware v1.173l Provides support for the new IPv6 standard.l Improves the controller's network

Doors.NET Reference Manual- 320 -Setup DoorsThe Setup Doors process allows you to configure door operating parameters, view eventhistory, audit change

Doors.NET Reference Manual- 321 -l Gateway - the gateway type/name for the controller to which the door is connectedl Controller - the name assigned t

Doors.NET Reference Manual- 322 -l Enable Door Contact - enable/disable monitoring of the door's contact switchl Held Open - set the amount of ti

Doors.NET Reference Manual- 323 -Selected Itemsl History - list an event history for selected doors; the pull-down menu beside the His-tory option all

Doors.NET Reference Manual- 324 -NXT Exit Reader SetupBy default all Doors.NET license keys have the NXT Exit reader enabled. Older licensekeys for NX

Doors.NET Reference Manual- 325 -4.Click on the icon from the Setup tab, then click the 'All' tab.5. Highlight the bus into which both the N

Doors.NET Reference Manual- 326 -7. Click Yes to the above message and an NXT Exit reader will be added to the busin the hardware tree.8. Highlight th

Doors.NET Reference Manual- 327 -11. Transaction reports can also be run on the readers independently. Click Reports>> Transactions, then from t

Doors.NET Reference Manual- 328 -

Doors.NET Reference Manual- 329 -Setup InputsThe Setup Inputs process allows you to configure the input type, circuit supervision, andmonitoring param

Doors.NET Reference Manual- 33 -Doors.NET IS compatible with the Business, Professional, Ultimate, and Enterprise ver-sions (both 32-bit and 64-bit) o

Doors.NET Reference Manual- 330 -l Panel Description - the type of controller panel (by manufacturer and physical char-acteristics)l Description - the

Doors.NET Reference Manual- 331 -Selected Itemsl History - list an event history for selected inputs; the pull-down menu beside theHistory option allo

Doors.NET Reference Manual- 332 -Setup OutputsThe Setup Outputs process allows you to configure the output type and monitoring para-meters.Under the H

Doors.NET Reference Manual- 333 -l Panel Description - the type of controller panel (by manufacturer and physical char-acteristics)l Description - the

Doors.NET Reference Manual- 334 -l Audit - list the changes made to and operations performed on selected outputsl Request Status - returns operational

Doors.NET Reference Manual- 335 -Setup PanelsThe Setup Panels process allows you to configure controllers and setup their com-munication parameters, a

Doors.NET Reference Manual- 336 -l Firmware - the firmware revision on the panell Model - the panel's hardware model numberl IP Address - the IP

Doors.NET Reference Manual- 337 -Review/Edit Controller Configuration ParametersThe right pane of the grid lists all information and configuration par

Doors.NET Reference Manual- 338 -Note: There are a wide variety of settings and not all controller types have the sameavailable settings.Controller Pr

Doors.NET Reference Manual- 339 -l Poll Delay (ms) - the delay between communication polls (in milliseconds)l Retry Count - the number of retries befo

Doors.NET Reference Manual- 34 -l Corrected a date-check issue with appointment schedules that would not allow anappointment schedule to cross midnigh

Doors.NET Reference Manual- 340 -Serial Number/Revision Controll Lowest Allowed Serial Number - the lowest allowed serial number for this con-troller

Doors.NET Reference Manual- 341 -Auditl Universal Serial Number - Represents the sequential increment each time thisobject is savedHardware Browser Pa

Doors.NET Reference Manual- 342 -The Update Network command sends all new configuration information out to selectedpanels.Click the icon and any infor

Doors.NET Reference Manual- 343 -Setup All HardwareThe Setup All tab provides a tree view of all hardware on the system allowing you to per-form any o

Doors.NET Reference Manual- 344 -When you select a Bus on any controller the Hardware Browser ribbon adds theNXTSeries icon group which allows you to

Doors.NET Reference Manual- 345 -Auto ConfigurationAuto Configuration is a process by which Doors.NET polls the network seeking NXT orPXL series contr

Doors.NET Reference Manual- 346 -If PXL controllers are being used, the master controller needs to be online and thenselected.NOTE: Before continuing,

Doors.NET Reference Manual- 347 -PXL controllers7. If using NXT controllers Selectively Take Ownership of those controllers in yournetwork by clicking

Doors.NET Reference Manual- 348 -The program default is to automatically take ownership of all unclaimed controllers.8. You release ownership of contr

Doors.NET Reference Manual- 349 -12. Once Auto Configuration is complete, close the AutoConfiguration Results tab.13. The All tab will display all con

Doors.NET Reference Manual- 35 -l Legacy PXL controllers should be at firmware revision 8.4.49 or greater(this minimum firmware revision is programmed

Doors.NET Reference Manual- 350 -14. Now you have the opportunity to rename controllers, readers, inputs, and outputsto descriptive names. This can ma

Doors.NET Reference Manual- 351 -

Doors.NET Reference Manual- 352 -Manual ConfigurationManual Configuration allows you to manually add hardware to your system database inanticipation o

Doors.NET Reference Manual- 353 -Adding 4x4 I/O Boards to a Controller BusWhen you select a Bus on any controller on the left pane of the grid, the Ha

Doors.NET Reference Manual- 354 -Firmware UpgradesThe Firmware Upgrade command upgrades the existing firmware on a controller or con-nected peripheral

Doors.NET Reference Manual- 355 -6. The Firmware Upgrade is complete once the progress bar for all selected con-trollers reaches 100%.NOTE: Typically

Doors.NET Reference Manual- 356 -Synchronize ClocksThe synchronization command sets the clock in all gateways and controllers to the timeset in the sy

Doors.NET Reference Manual- 357 -

Doors.NET Reference Manual- 358 -Setup Reflections Express VideoReflections Express™ is the basic video client provided with Doors.NET. ReflectionsExp

Doors.NET Reference Manual- 359 -l Select your camera type from the pull-down menu list and click Add.l The selected camera is added to the Cameras tr

Doors.NET Reference Manual- 36 -Doors.NET Version 3.5.1.15Operating System RequirementsDoors.Net software IS NOT compatible with any Home version of W

Doors.NET Reference Manual- 360 -Camera Operating ParametersCamera Identificationl Name - enter a user-friendly name given to the camera, typically to

Doors.NET Reference Manual- 361 -l Post-Alarm Buffer - set the number of seconds of post event video that should besaved when an event-triggered video

Doors.NET Reference Manual- 362 -l Click the Save button.l A Save Changes dialog box appears. Click Yes to save all entered operating para-meters.l Th

Doors.NET Reference Manual- 363 -

Doors.NET Reference Manual- 364 -Extended PXL Global Unlock/LockThis document details how to enable the standard implementation of Global Unlock-/Lock

Doors.NET Reference Manual- 365 -2. In properties, locate Options > Global Unlock Enable and set it to Yes.3. Set Global Unlock Type to Unlock All

Doors.NET Reference Manual- 366 -6. The dedicated Global Unlock input is a normally-open circuit that activates GlobalUnlock when it’s closed. It is p

Doors.NET Reference Manual- 367 -8. In the doors status grid (Setup > Hardware Setup > Doors), the Detail column dis-plays “GUE Unlocked” for ea

Doors.NET Reference Manual- 368 -NOTE: The Global Unlock feature is not Fire Marshall approved. Check your local codesfor fire safety management.NOTE:

Doors.NET Reference Manual- 369 -l Lockdown – Operates as Lockout with NO RTE functionality.l Lockdown – Allow Always Schedule – The same as Lockdown

Doors.NET Reference Manual- 37 -l Corrected an issue when reassigning a door strike from a controller to a 4x4 I/Omodule. The reader assignment list w

Doors.NET Reference Manual- 370 -4. Expand the controller’s inputs in the hardware tree. The input on the master con-troller dedicated to global lock

Doors.NET Reference Manual- 371 -7. Live Events also posts appropriate Access Denied events, depending upon theLock Type that the readers have been se

Doors.NET Reference Manual- 372 -NOTE: The Global Lock feature is not Fire Marshall approved. Check your local codesfor fire safety management.NOTE: G

Doors.NET Reference Manual- 373 -Hardware OptionsSetup AirlockThe Airlock feature is supported and built into the firmware of NXT Mercury Poweredand M

Doors.NET Reference Manual- 374 -Setup AirlockThe airlock feature is only supported and built into the firmware of SCP and NXT Mer-cury Powered contro

Doors.NET Reference Manual- 375 -see the Options setting then you will need to enable Advanced View.3. In controller options select Yes to Area Contro

Doors.NET Reference Manual- 376 -6. Give both Areas a new name - One for door 1, the other for door 2, for example:7. Highlight the first Area so that

Doors.NET Reference Manual- 377 -10. Highlight the reader for Door 2 and again locate the Anti-Passback settings.l Anti-Passback Mode - must be set to

Doors.NET Reference Manual- 378 -Anti PassbackThe Anti Passback (APB) feature provides one-way card access into and out of a securearea. It prevents a

Doors.NET Reference Manual- 379 -APB Amnesty - PXLAmnesty resets the APB flag for a credential so that credential can be used again.Optionally, amnest

Doors.NET Reference Manual- 38 -l The program now requires that a new cardholder entry be saved before attaching aphoto to that cardholder. This ensur

Doors.NET Reference Manual- 380 -4. Select the desired amnesty type from the list.Local APB Setup - Mercury or Mercury Powered Con-trollersWhen using

Doors.NET Reference Manual- 381 -once the defined time period has passed, for example, 15 minutes - this time isdefined in the Anti-Passback Duration

Doors.NET Reference Manual- 382 -7. If you present a card which has access to both of these readers you will not be ableto get access to the same read

Doors.NET Reference Manual- 383 -Setup Dual Verification (Card & PIN)The Dual Verification feature requires the use of a Wiegand keypad with a bui

Doors.NET Reference Manual- 384 -4. If your properties grid is similar to what's shown above you will need to enable theAdvanced View.5. Once ena

Doors.NET Reference Manual- 385 -10. Right-click the keypad on the hardware tree, go to Mode >> and select Card AndPIN.11. You should see a read

Doors.NET Reference Manual- 386 -13. Finally, open a cardholder record (Home > Cardholders). Select a cardholderrecord and enter a PIN number in th

Doors.NET Reference Manual- 387 -Elevator ControlDoors.NET supports Elevator Control when using NXT Mercury Powered controllersand NXT 4x4 modules or

Doors.NET Reference Manual- 388 -Floor DeviceWiring Loca-tionTerminalBlockDefault OutputDesignatorDefault InputDesignator6 4x4Bus 1 - Port4TB25 Output

Doors.NET Reference Manual- 389 -4-Door Controller and 4x4sFor a 4-door controller handling up to 20 floors:Floor DeviceWiring Loca-tionTerminalBlockD

Doors.NET Reference Manual- 39 -l Added firmware upgrade status messages to provide active feedback during anupgrade.l Added options to the System Cal

Doors.NET Reference Manual- 390 -Floor DeviceWiring Loca-tionTerminalBlockDefault OutputDesignatorDefault InputDesignator16 4x4Bus 1 - Port2TB23 Outpu

Doors.NET Reference Manual- 391 -2-Door Controller an GIOX UnitFor a 2-door controller handling up to 34 floors:Floor Device Wiring LocationTerminalBl

Doors.NET Reference Manual- 392 -Floor Device Wiring LocationTerminalBlockDefault Output Desig-nator710 GIOXOutput Module 1 - Slot8TB74 Output 1.1.811

Doors.NET Reference Manual- 393 -Floor Device Wiring LocationTerminalBlockDefault Output Desig-nator28 GIOXOutput Module 4 - Slot2TB71 Output 1.4.229

Doors.NET Reference Manual- 394 -Verify Your License1. Begin by ensuring your Doors.NET Application Server license is configured withElevator Control

Doors.NET Reference Manual- 395 -3. At the bottom of the hardware tree is a node labeled ‘Facilities.’ A Facility needs tobe defined and this is where

Doors.NET Reference Manual- 396 -8. Next step is to configure the controller. Advanced view must be enabled to see allthe relevant sections. Click on

Doors.NET Reference Manual- 397 -11. Now assign the Floor Map; selecting which floors this controller will be servicing.12. Save these settings. The s

Doors.NET Reference Manual- 398 -Adding a 4x4 Adding a GIOX Unit16. Check the 4x4 or GIOX outputs are configured correctly by highlighting one of theo

Doors.NET Reference Manual- 399 -l No Floor Select means all outputs will activate for all floors to which a cardholderhas access when they present an

Doors.NET Reference Manual- 4 -Doors.NET has a very intuitive interface, that will perhaps seem familiar if you have usedKeri's Doors32 software.

Doors.NET Reference Manual- 40 -Mercury Powered NXT Firmware (MSC) v1.01.40l Corrects an issue with Assa Aperio wireless lock hubs that could interrup

Doors.NET Reference Manual- 400 -21. All the configured Elevator Outputs, including those on the controller should activ-ate.Create the Access Groups1

Doors.NET Reference Manual- 401 -8. If a cardholder requires access to various floors at different times of day then thesefloors and time schedules wo

Doors.NET Reference Manual- 402 -9. A cardholder cannot directly be assigned an ‘elevator access group,’ so this groupwill need to be added to the gen

Doors.NET Reference Manual- 403 -14. The last step is to open up a card record (which has an active card enrolled). Clickon the Access Rights tab and

Doors.NET Reference Manual- 404 -Event MonitoringThe Doors.NET software was designed to support both monitored and autonomous con-figurations. A syste

Doors.NET Reference Manual- 405 -The system uses a combination of Filters and Device Types to configure how the systemmanages and displays the various

Doors.NET Reference Manual- 406 -FiltersFilters are used by the system to specify which system generated messages are dis-played in the software as li

Doors.NET Reference Manual- 407 -3. Click the messages tab to select the event types to display in Live Events. Theevent types turn green when selecte

Doors.NET Reference Manual- 408 -and will create an 'alert' - which can then be configured (using device types) for anoperator to take actio

Doors.NET Reference Manual- 409 -

Doors.NET Reference Manual- 41 -l The NXT Reader requires new firmware revision 3.01.01 specifically to enable theIn/Out reader function. If this feat

Doors.NET Reference Manual- 410 -Device TypesThe Device Types in the system are used with the event notification options configuredin the monitoring t

Doors.NET Reference Manual- 411 -Priority sets the priority for event notification for this device type. The range is from 0 to99 with 0 being the hig

Doors.NET Reference Manual- 412 -AudioAudio Instructions lists the .wav files installed in the DoorsNET/Sounds directory. Youcan add your own custom s

Doors.NET Reference Manual- 413 -Event AcknowledgementThe acknowledgment of certain events by the operator consists of two actions: eventselection, th

Doors.NET Reference Manual- 414 -For example, in Device Types you can define the event to require a password before itcan be confirmed.3. If there are

Doors.NET Reference Manual- 415 -5. Notes are added via the Notes tab or can be selected from the Available Notesdrop-down list (if any are available)

Doors.NET Reference Manual- 416 -Sound AlertsSound Alerts can be setup and used in the Doors.NET software to generate a sound atthe client PC for diff

Doors.NET Reference Manual- 417 -2. Click Setup >> Device Types.3. Click the Add Device Type button, highlight the default name and give the dev

Doors.NET Reference Manual- 418 -Masked, or Clear sounds. For example: Monitor Point Alarm is an 'Alarm' sound,whereas Monitor Point - Secur

Doors.NET Reference Manual- 419 -6. There are several sound files added to a default system automatically, but you canadd your own .WAV files to this

Doors.NET Reference Manual- 42 -feature addition, requiring the user to repeat the activation process when Internetaccess is finally restored.l Added

Doors.NET Reference Manual- 420 -10. Go to the Messages tab then locate the exact event that you wish to use.11. Next step, go to the Acknowledge tab

Doors.NET Reference Manual- 421 -14. The next time the Reader Forced event occurs at this reader it will appear in theAlerts grid and the sound select

Doors.NET Reference Manual- 422 -Event Video RecordingAnother one of the most powerful features in the Doors.NET software is the ability tointegrate v

Doors.NET Reference Manual- 423 -3. To view and check the name of the camera(s) in the software, expand the Camerasnode at the bottom of the hardware

Doors.NET Reference Manual- 424 -7. Now that the reader is associated with the camera, every time the reader is high-lighted a live video icon will be

Doors.NET Reference Manual- 425 -9. Now a filter must be setup which will define the event that will generate the recor-ded clip.10. From the Setup ta

Doors.NET Reference Manual- 426 -12. From the Messages tab select the message: "Reader Contact - Forced Open."13. From the Acknowledge tab p

Doors.NET Reference Manual- 427 -17. The event is now generated at the controller by opening the door contacts. It willappear in Live Events.18. Assig

Doors.NET Reference Manual- 428 -Retrieving Video Clips Through Reports1. You can search for, then view video clips via Reports >> Transactions.

Doors.NET Reference Manual- 429 -2. To retrieve event information from a reader on the system chose All Messages(Reader) from the Report Type drop-dow

Doors.NET Reference Manual- 43 -l Corrected an issue with Access Groups that allowed multiple Reader assignmentsin an Access Group for Readers on buse

Doors.NET Reference Manual- 430 -5. Similarly to Live Events, the reader transaction(s) with associated video will havethe blue paperclip icon next to

Doors.NET Reference Manual- 431 -7. See Device Types for further information about setup and assignment to thereader.

Doors.NET Reference Manual- 432 -Operators PermissionsThe Operators Permissions feature allows you to create software users and operatorgroups. You ca

Doors.NET Reference Manual- 433 -Adding Additional System AdministratorsIt is a very quick and simple process to add an additional system administrato

Doors.NET Reference Manual- 434 -6. Now click the Add Login button. The new user name will be added to the SystemAdministrators user group, along with

Doors.NET Reference Manual- 435 -2. Change the default name to something descriptive.3. Add a new user name, a password, then confirm the password.4.

Doors.NET Reference Manual- 436 -5. Click the Add Login button and the new username will appear beneath the newuser group name in the left pane.6. Cli

Doors.NET Reference Manual- 437 -3. Depending upon the Permission type, the setting options are either Show or Hide,or there will be three options: Fu

Doors.NET Reference Manual- 438 -4. Click Save.Adding LocationsThe Locations tab configures which controllers the user group is allowed to manipulate.

Doors.NET Reference Manual- 439 -Adding Access GroupsThe third part of the virtual database permissions is the Access Groups tab. The systemadministra

Doors.NET Reference Manual- 44 -l Added more options to the context menus used when creating an email/SMS mes-saging macro. This makes it easier to in

Doors.NET Reference Manual- 440 -1. To configure the access groups for a specific user group, select the user group andclick on the Access Groups tab.

Doors.NET Reference Manual- 441 -1. To configure a user groups for a specific route, select the user group and click onthe Routing tab. The entire lis

Doors.NET Reference Manual- 442 -

Doors.NET Reference Manual- 443 -Application PermissionsThe Application Permissions use the Account Type to determine which menus are hid-den or disab

Doors.NET Reference Manual- 444 -Application Menu ItemsThe menu items relate to which icons will be highlighted when the users logs into thesoftware.1

Doors.NET Reference Manual- 445 -Override CommandsAs an example, you may also want to restrict how much control operators have over thehardware in the

Doors.NET Reference Manual- 446 -

Doors.NET Reference Manual- 447 -DiagnosticsDiagnostics provides quick, basic information on the clients connected to the server anda snapshot of clie

Doors.NET Reference Manual- 448 -l Click the Server tab to review server diagnostic information.

Doors.NET Reference Manual- 449 -System OptionsThe System Options window allows you to view detailed system information and enable/-configure certain

Doors.NET Reference Manual- 45 -Card-Only to more secure Two-Card required, but would not switch back to theless secure option.l Standardized the word

Doors.NET Reference Manual- 450 -LicenseLicense displays information regarding the program features, limits, and capacitiesenabled by the license you

Doors.NET Reference Manual- 451 -Situation Manager - Global Lock/UnlockThe Situation Manager is an advanced Doors.NET feature advanced feature imple-m

Doors.NET Reference Manual- 452 -l Select which doors participate in Global Lock and/or Global Unlock.l Set the override precedence between Global Loc

Doors.NET Reference Manual- 453 -Supplementary InformationTypical Global Lock/Unlock Applications - provides sample configurations for typicalGlobal L

Doors.NET Reference Manual- 454 -Configure the Situation ManagerSituation Manager configuration allows you to define how Global Lock/Unlock is applied

Doors.NET Reference Manual- 455 -2. Click Situation Manager in the list of System Options.3. In the grid, click in the Enabled field and select Yes in

Doors.NET Reference Manual- 456 -System Administrator OnlyLimits access to the Situation Manager to operators who have System Administratorlevel login

Doors.NET Reference Manual- 457 -Global Unlock EnabledEnables Global Unlock, placing the Global Unlock icon and the Normal icon into the Situ-ation Ma

Doors.NET Reference Manual- 458 -Global Lock Ignore OverrideWhen enabled, this option prevents an operator from issuing a manual door commandsuch as l

Doors.NET Reference Manual- 459 -Precedence option in the pull-down menu.NOTE: Precedence only applies if hardware inputs are being used to initiate G

Doors.NET Reference Manual- 46 -l Corrected an issue when creating monitoring filters. Certain filter types would notsave properly, rendering those fi

Doors.NET Reference Manual- 460 -l If Momentary, then no logic is needed for the restore state. The hardware input isthe trigger to put the system int

Doors.NET Reference Manual- 461 -NOTE: This option can only be used with the optional Global Linkage feature.1. To assign a Global Linkage trigger to

Doors.NET Reference Manual- 462 -4. The highlighted icon reflects the current state of the system.

Doors.NET Reference Manual- 463 -Assign Global Lock/Unlock HardwareAssigning hardware allows you to assign/unassign readers individually to the Global

Doors.NET Reference Manual- 464 -DoorsIf the Situation Manager is enabled, two additional properties in the Doors grid areenabled. These two propertie

Doors.NET Reference Manual- 465 -Global Unlock input; an input cannot be both. The default is for inputs to not be con-figured as a Global Lock or Glo

Doors.NET Reference Manual- 466 -2. A Save Changes confirmation window appears. Click Yes to confirm the optionchange.3. The Situation Manager for the

Doors.NET Reference Manual- 467 -Typical Global Lock/Unlock Applic-ationsThe following sections provide typical application descriptions for Global Lo

Doors.NET Reference Manual- 468 -icons will reflect the Global Lock/Unlock state. An operator with the appropriate per-missions must change the state

Doors.NET Reference Manual- 469 -inputs are normal before changing the system state. The system then checks to see if atleast one Global Lock input is

Doors.NET Reference Manual- 47 -that output. This only applies to new reassignments. If you upgrade the softwarefrom a previous revision and have thes

Doors.NET Reference Manual- 470 -l Allow operator defined linkage triggers to use the same logic as in AutoUnlock trig-gers (i.e., prevent a trigger f

Doors.NET Reference Manual- 471 -NOTE: This example uses Boolean Arithmetic. Please be familiar with Boolean Arith-metic before attempting to program

Doors.NET Reference Manual- 472 -Handling Offline or Network OutageStatesThe system is designed to have the ability to handle communications loss to c

Doors.NET Reference Manual- 473 -NOTE: If the Situation Manager is configured to be Hardware Driven then the followingcould occur:1. A controller that

Doors.NET Reference Manual- 474 -Photo RecallBuilt into the software is the ability to be able to show a cardholder's photographwhenever access i

Doors.NET Reference Manual- 475 -Display Optionsl Follow Live Event Filter- The feature will only process the transactions thatappear in live events.l

Doors.NET Reference Manual- 476 -l Show on Mouse Click - Shows the tooltip on mouse click for the selected photo.l Show on Mouse Hover - Shows the too

Doors.NET Reference Manual- 477 -8. This device type should then be assigned to any reader you choose.9. Highlight the reader in the hardware tree and

Doors.NET Reference Manual- 478 -11. By default, it will search the following directory C:\Keri\DoorsNET\Photos - and thisis where we recommend storin

Doors.NET Reference Manual- 479 -14. The photo strip will appear for any cardholder that has a photograph assigned andwho gains access at this reader.

Doors.NET Reference Manual- 48 -l Adds the ability to change the Server ID, Controller ID, and Network Data using Tel-net commands. This feature can b

Doors.NET Reference Manual- 480 -AutomationOverviewThe Local and Global linkage menus are by far the most powerful features of the Door-s.NET software

Doors.NET Reference Manual- 481 -tasks are available as part of the standard Doors.NET program. Other tasks are optional,licensed features. When using

Doors.NET Reference Manual- 482 -specific trigger occurs. A typical application for this would be to send a message if aDoor Forced event occurs durin

Doors.NET Reference Manual- 483 -Email/SMS AutomationEmail/SMS Automation allows an operator to create a macro that will automatically senda message v

Doors.NET Reference Manual- 484 -4. Click the Add Macro Item button.5. Enter a description for the Action Type. This name is copied into the correspon

Doors.NET Reference Manual- 485 -For Emaill Enter your message recipients in the To, CC, and BCC fields. Separate multiplerecipients with a comma (,).

Doors.NET Reference Manual- 486 -n Global Link IDn Message IDn Object IDn Route IDn SPM IDFor SMSl Enter your message recipients in the Phone Number f

Doors.NET Reference Manual- 487 -2. Click on the New Global Trigger entry to enable Trigger Properties.3. Enter a descriptive name into the Descriptio

Doors.NET Reference Manual- 488 -9. Click the Enabled check-box to enable the Condition.10. Click the Enable Time Constraint pull-down menu and select

Doors.NET Reference Manual- 489 -13. Save the Trigger.Configure the Linkage ServiceThe Linkage Service makes the communication connection that sends o

Doors.NET Reference Manual- 49 -NOTE: Due to networking restrictions built into the Home versions of Windows operatingsystems, Doors.Net software is N

Doors.NET Reference Manual- 490 -Email Settings1. Click the Email Settings tab.2. Make edits according to the type of Email service you use. Keri reco

Doors.NET Reference Manual- 491 -4. Click the Close button to exit the License Manager.SMS Settings1. Click the SMS Settings tab. Default SMS settings

Doors.NET Reference Manual- 492 -4. Click the Close button to exit the License Manager.Verify the Macro is Operational1. Right click on the Macro name

Doors.NET Reference Manual- 493 -5.Enable the Parameter Pane Advanced View .6. Scroll down the Parameter List until the Monitoring section appears.7.

Doors.NET Reference Manual- 494 -

Doors.NET Reference Manual- 495 -Global LinkageThe Global Linkage Module and related user interface screens provide a means of auto-mating system func

Doors.NET Reference Manual- 496 -The Host Based schedule runs on the Application Server PC (the host PC) and uses theDoors.NET time schedules and the

Doors.NET Reference Manual- 497 -Each Global Trigger can have multiple conditions of the same type. Each condition ofthe Global Trigger is evaluated i

Doors.NET Reference Manual- 498 -The feature is supported on all Doors.NET controller types except for the PXL con-trollers. It is an optional module

Doors.NET Reference Manual- 499 -l Program an input to unlock/lock several doors at oncel Program an output to follow an input

Doors.NET Reference Manual- 5 -software. It can be configured to run on a single PC or multiple PCs across a network -depending upon the desired chara

Doors.NET Reference Manual- 50 -l Ingersoll-Rand / Schlage AD-Series wireless locksl Support for reverse bit patterns for specific types of Magstripe

Doors.NET Reference Manual- 500 -Global Linkage - Program Doors toUnlock/Lock Based on Input StateTo program a Global Linkage you must have a Global L

Doors.NET Reference Manual- 501 -4. From the Macro Item type drop-down list select Reader Mode Control.5. Select the appropriate hardware gateway.6. S

Doors.NET Reference Manual- 502 -10. A second macro needs to be added, this macro will put the doors back to their nor-mal mode.11. Rename the second

Doors.NET Reference Manual- 503 -18. As with the first macro, multiple action types need to be added - each one cor-responding to the participating do

Doors.NET Reference Manual- 504 -20. The doors will relock when you right-click and 'Execute' the second macro.Trigger Setup1. Ensure that a

Doors.NET Reference Manual- 505 -2. Two trigger conditions must now be defined; The first trigger condition will be theinput going active, this will a

Doors.NET Reference Manual- 506 -Trigger Condition 21. Highlight the same trigger and click Add Condition button.2. Highlight the second New Condition

Doors.NET Reference Manual- 507 -5. Finally, locate the input point in the hardware tree. In the properties go to Mon-itoring >> Global Trigger

Doors.NET Reference Manual- 508 -6. There's no need to do any kind of update because the configuration gets sent outto the hardware as soon as it

Doors.NET Reference Manual- 509 -Global Linkage - Program an Output toFollow an InputTo program a Global Linkage you must have a Global Linkage licens

Doors.NET Reference Manual- 51 -Program Improvements:l Corrected typographical and display field errors in several program windows.l Corrected informa

Doors.NET Reference Manual- 510 -Macro Setup1. From the Home tab >> Automation ribbon click Global Linkage.

Doors.NET Reference Manual- 511 -2. Click the Add New button to add a new macro. In the Description create a name forthe Macro (Red LED Active), then

Doors.NET Reference Manual- 512 -5. You will now have two Macros defined in the list. The first one to Activate the out-put, the second will De-activa

Doors.NET Reference Manual- 513 -Trigger Setup1. Click the Triggers tab, click add new then create a name for the trigger (i.e MotionTrigger).2. From

Doors.NET Reference Manual- 514 -3. Click the new condition to highlight it and give the condition a description (InputActive). From Available Message

Doors.NET Reference Manual- 515 -5. Click Add Condition again. The Monitor Point - Secure condition can be assignedto the same trigger but will action

Doors.NET Reference Manual- 516 -6. Select the other Macro from the Macro drop-down list.7. Now that the configuration is complete you just have to hi

Doors.NET Reference Manual- 517 -8. Activate the input on controller one to trigger activation of the output on controller 2.If the procedure fails to

Doors.NET Reference Manual- 518 -Global Linkage MacrosThe following list details all the Global Linkage Macro options that are available in Door-s.NET

Doors.NET Reference Manual- 519 -Set LED Mode 2Set LED Mode 3Reader Mask -Forced OpenMask Reader ForcedUnmask Reader ForcedReader Mask - HeldOpenMask

Doors.NET Reference Manual- 52 -prompts the user to redefine that programming prior to removing the 4x4 from thesystem.l Corrected an issue with Doors

Doors.NET Reference Manual- 520 -Activate Severe Threat LevelActivate Global LockActivate Global Restore NormalActivate Global UnlockSMS SMS CarrierSc

Doors.NET Reference Manual- 521 -Global Linkage TriggersThe following list details all the trigger conditions available within Global Linkage. Mul-tip

Doors.NET Reference Manual- 522 -Access Denied - Count ExceededAccess Granted -Access Granted - Anti-PassbackAccess Granted - Anti-Passback, No EntryA

Doors.NET Reference Manual- 523 -SRAM Buffer OverflowController Credential Database Saved to FlashMemoryController ID ReportController Power-Up Diagno

Doors.NET Reference Manual- 524 -DeniedAccess Denied - Asked For Host Approval, thentimed outAccess Denied - Before Activation DateAccess Denied - Dea

Doors.NET Reference Manual- 525 -Access Granting - Second Transaction Will FollowAccess Granting - Waiting For Host ResponseDoor LockedDoor Locked By

Doors.NET Reference Manual- 526 -Reader Contact - Shorted LineReader Contact Door Open - Forced Open isMaskedReader Contact - Masked Both Forced Open

Doors.NET Reference Manual- 527 -Secondary Request to ExitThe wireless reader (Aperio) has a low batteryThe wireless reader (Aperio) has a stalled mot

Doors.NET Reference Manual- 528 -Video - Person FallenVideo - Person IntrusionVideo - Person LoiteringVideo - Person on WatchlistVideo - Person Runnin

Doors.NET Reference Manual- 529 -Local LinkageThe Local Linkage section is by far the most powerful feature of the Doors.NET system.It is an advanced

Doors.NET Reference Manual- 53 -l Separated the operator permissions for viewing credential activation dates fromviewing credentials themselves, creat

Doors.NET Reference Manual- 530 -Setup Local Linkage1. After logging into Doors.NET, click the Setup tab, then Local Linkage.2. The first tab you will

Doors.NET Reference Manual- 531 -2. Highlight the new procedure, change the default name, then click the Add Actionbutton. There are many Action Types

Doors.NET Reference Manual- 532 -4. You can use any available input on the controller, or a 4x4 or GIOX module con-nected to any of the controller&apo

Doors.NET Reference Manual- 533 -6. At this point you can test the Local Linkage procedure to verify its functionality.Right-click the procedure name

Doors.NET Reference Manual- 534 -When the system sees a trigger that you have defined, the event will appear in liveevents and at the same time it wil

Doors.NET Reference Manual- 535 -l The Execute This Procedure drop down selection is a list of the stored actionlists at the controller. This is the p

Doors.NET Reference Manual- 536 -2. A dialog save box will appear and the default location will be the 'Exported Link-ages' sub-folder withi

Doors.NET Reference Manual- 537 -6. The same dialog box will appear with the 'ExportedLinkages' folder as pre-selec-ted. If you have linkage

Doors.NET Reference Manual- 538 -Local Linkage Trigger Conditions ListThe table below lists all of the available trigger conditions. Changing the Sour

Doors.NET Reference Manual- 539 -Access Denied: Invalid Facil-ity Code Ext.Access Denied: Not In FileAccess Denied: Invalid IssueCodeAccess Granted: F

Doors.NET Reference Manual- 54 -NXT Firmware Version 2.05.16l Corrected a controller power-up issue that could energize a 4x4 relay during thepower up

Doors.NET Reference Manual- 540 -Access Granted: Door NotUsedAccess Denied: PIN TimeoutAccess GrantedAccess Denied: NeverAllowedAccess Denied: No Seco

Doors.NET Reference Manual- 541 -Door Secured: PreviouslyHeld OpenDoor Secured: PreviouslyForced or Held OpenDoor ClosedDoor Opened (No Alarm)Held Ope

Doors.NET Reference Manual- 542 -- Airlock is BusyControl Point Change of State Disabled From HostOff-Line: No ReportOutput is InactiveOutput is Activ

Doors.NET Reference Manual- 543 -Tamper Became InactivePanel Dia-gnosticsSystem Panel DiagnosticsPanel PowerMonitorChange of State Power Monitor Becam

Doors.NET Reference Manual- 544 -Local Linkage Procedure Action ItemsThe table below lists all of the available procedure action item selections. Chan

Doors.NET Reference Manual- 545 -Enable Cipher ModeEnable Extended User CommandsEnable Two Card RuleFacility CodeLockdownLockedLockoutPIN OnlyUnlocked

Doors.NET Reference Manual- 546 -Local Linkage - Program an Output toFollow an InputA basic Local Linkage example is to program an output on the syste

Doors.NET Reference Manual- 547 -3. Highlight the new procedure and enter a description.l The Description text field allows you to change the name of

Doors.NET Reference Manual- 548 -6. Control Points are outputs and for this example it is using an output on a 4x4 mod-ule - wired into an NXT Mercury

Doors.NET Reference Manual- 549 -There are now two different procedures (one to activate the output and one to deactivateit).8. If the hardware is onl

Doors.NET Reference Manual- 55 -The system calendar option is licensed separately but include more features thanjust the backup option.Program Improve

Doors.NET Reference Manual- 550 -Trigger Setup1. Click on the Triggers tab next. The same controller should already be pre-selectedin the controller l

Doors.NET Reference Manual- 551 -4. Rename the first trigger to something meaningful and make the following selec-tions.l The Description field allows

Doors.NET Reference Manual- 552 -l The Transaction Type drop down selection is a list of transaction types asso-ciated with the selected source type.

Doors.NET Reference Manual- 553 -Local Linkage - Change Card ReaderMode from an InputThis Local Linkage example explains how to increase the security

Doors.NET Reference Manual- 554 -3. Highlight the controller in the hardware tree (ensure Advanced View is enabled)4. Scroll down the properties until

Doors.NET Reference Manual- 555 -6. Open Local Linkage by clicking Setup tab >> Local Linkage.

Doors.NET Reference Manual- 556 -Procedure Setup1. Select the controller which the keypad is wired into then click the New Procedurebutton.2. Highligh

Doors.NET Reference Manual- 557 -5. Select the card reader door to be changed. Note that only 1 reader can be selectedfor each action type.6. From the

Doors.NET Reference Manual- 558 -9. At this point you can test the functionality of the procedures by right-clicking andselecting Execute.10. After ex

Doors.NET Reference Manual- 559 -1. Click the Triggers tab, click the Add Trigger button and in the Description field cre-ate a name for the trigger (

Doors.NET Reference Manual- 56 -Firmware Updates for Hardware Components:RIM v03.01.11l Under certain conditions, typically when “hot-swapping” reader

Doors.NET Reference Manual- 560 -3. Click Add Trigger button again, as the process now needs to be repeated for whenthe input is secure. Create a name

Doors.NET Reference Manual- 561 -5. Your Local Linkage action setup is now complete. It is now simply a case of activ-ating the Input. The input activ

Doors.NET Reference Manual- 562 -ReportsDoors.NET software includes many different default report types which are included inthe standard version of t

Doors.NET Reference Manual- 563 -Reports - Cardholders1. To run reports on Cardholders in the Doors.NET system click on the reports tab >>Cardho

Doors.NET Reference Manual- 564 -l Cardholders in a Departmentl Cardholders in a Locationl Cardholders from a County (Work)l Cardholders from a County

Doors.NET Reference Manual- 565 -6. There are several different Views that can be selected from the drop-down list. Forexample, here is how the Corpor

Doors.NET Reference Manual- 566 -8. It is also easy to export the information as a PDF, Excel or XPS document. Afteryou have generated the report, cli

Doors.NET Reference Manual- 567 -9. Then just navigate to a destination folder, change the default name of the file ifdesired and then click save.

Doors.NET Reference Manual- 568 -Reports - Transactions1. To run Transaction reports in Doors.NET click on the Reports tab >> Transactions.2. Wh

Doors.NET Reference Manual- 569 -3. There are many different Transaction Report Types available, these can all beviewed by clicking the drop-down list

Doors.NET Reference Manual- 57 -l When setting operator permissions to View Only, certain permissions were not cor-rectly applied.l The Search Cardhol

Doors.NET Reference Manual- 570 -l All Messages (Reader, Cardholder, MessageType)l All Messages (Reader, MessageType)l All Messages (Search)l Last X M

Doors.NET Reference Manual- 571 -Note: You can also select multiple readers, cardholders and message types.2. Once you have selected the reader(s) and

Doors.NET Reference Manual- 572 -4. Change the start date and the end dates, if desired, by default they are both set totoday's date. You can als

Doors.NET Reference Manual- 573 -Including Video6. Some of the transaction may have video clips associated with them. If there arecameras on the syste

Doors.NET Reference Manual- 574 -View OptionsYou can also view the report in 'Card View'.Or choose one of the View options from the drop-dow

Doors.NET Reference Manual- 575 -Printing and ExportingOnce the report has been generated it can be printed directly from the software, or it canbe ex

Doors.NET Reference Manual- 576 -Reports - Reader Access1. Click Reports > Reader Access.2. The reader access reports provides you with information

Doors.NET Reference Manual- 577 -5. This information can also be sorted by columns, i.e by cardnumber, first name, lastname or access group.NOTE:You

Doors.NET Reference Manual- 578 -

Doors.NET Reference Manual- 579 -Reports - HardwareHardware Reports allow you to run a report on the properties and configuration of all thehardware o

Doors.NET Reference Manual- 58 -l Changing filter settings required a unique password and not the standard systemadministrator password. Now the syste

Doors.NET Reference Manual- 580 -5. Use the View drop-down list to change the display of the grid.6. In addition, you can select 'Card View'

Doors.NET Reference Manual- 581 -7. As with all the Doors.NET Reports you can print the information directly or it can beexported and saved as an Exce

Doors.NET Reference Manual- 582 -ToolsUtilitiesTwo utilities are available allowing you to change the logon password or to backup theentire Doors.NET

Doors.NET Reference Manual- 583 -Tools - UtilitiesChange PasswordThe Change Password feature allows you to quickly change the password of the cur-rent

Doors.NET Reference Manual- 584 -2. Select the Global Linkage entry on the left pane.3.Click on the button.4. It opens up on the Startup tab and you w

Doors.NET Reference Manual- 585 -Changing the Video Gateway Password1. Again, open up the License Manager and select the Video Gateway on the leftpane

Doors.NET Reference Manual- 586 -The backup features is a very simple means of creating a full backup of the entire Door-s.NET database. There is no c

Doors.NET Reference Manual- 587 -6. The file should then be copied to an external hard-drive, a CD/DVD, USB-drive orother removable medium for safe st

Doors.NET Reference Manual- 588 -LayoutsThe layout and positioning of each of the main components and the location of the gridviews can be saved per u

Doors.NET Reference Manual- 589 -To save your screen preferences click on the save layout icon, give the file a name andsave it into the 'Menu La

Doors.NET Reference Manual- 59 -Technical SupportKeri's highly experienced and knowledgeable staff provides technical support world-wide.U.S. Sup

Doors.NET Reference Manual- 590 -Next time you login under this user, simply click on Tools >> Load Layout and select thesame file and click Ope

Doors.NET Reference Manual- 591 -color options for live events, can be helpful for operators who may be color blind and findit hard to distinguish bet

Doors.NET Reference Manual- 592 -View TasksThe View Tasks tab breaks into two groups:the Help Tasks group and the DockingTasks group.Help TasksThe He

Doors.NET Reference Manual- 593 -2. Click the Details button to view detailed information on the software release. Inform-ation within this window may

Doors.NET Reference Manual- 594 -3. Click the System Info button to open Microsoft's System Information window. Thiswindow provides technical det

Doors.NET Reference Manual- 595 -l The Show All icon pins open all quick-open status tabs into partitioned windows inthe data field.l The Hide All ico

Doors.NET Reference Manual- 596 -Display ColorsThe Display Colors window allows you to set the colors of key elements of the windowbeing displayed. Us

Doors.NET Reference Manual- 597 -Advanced ViewAdvanced View is not enabled by default on a standard Doors.NET installation, even forthe default System

Doors.NET Reference Manual- 598 -3. When you return to the hardware properties you will see the additional AdvancedView 'atom' icon.4. You c

Doors.NET Reference Manual- 599 -5. Refer to Operators Permissions for instructions on how to prevent a software userfrom being able to view Advanced

Doors.NET Reference Manual- 6 -Custom Credential Formats, Area Control, Host Schedules, System Calendar, RollcallClient, and a Professional Report Cli

Doors.NET Reference Manual- 60 -Software InstallationDoors.NET installation and controller configuration is a three step process. Each ofthese steps h

Doors.NET Reference Manual- 600 -SQL Database Backup and RestoreContent in development.

Doors.NET Reference Manual- 601 -Troubleshooting BasicsHelp content section under development.

Doors.NET Reference Manual- 602 -Firewalls and CommunicationHelp content section under development.

Doors.NET Reference Manual- 61 -NOTE:Navigate to the DVD's root directory and run the autorun.exe program if thismenu does not appear.l Click th

Doors.NET Reference Manual- 62 -3. Once started, the installer performs a quick installation file verification and pre-pares the file set for installa

Doors.NET Reference Manual- 63 -5. Review the version listing to confirm the revision of the software to be installed.6. Click NEXT to continue to the

Doors.NET Reference Manual- 64 -7. Click the check-box to accept the License Agreement.8. Click NEXT to enter Customer Registration information.

Doors.NET Reference Manual- 65 -9. Enter your User Name and (optionally) an Organization Name.10. Click NEXT for Hardware Selection.

Doors.NET Reference Manual- 66 -11. Click the radio button corresponding to the controller type being used in the sys-tem.l Keri NXT for standard NXT

Doors.NET Reference Manual- 67 -13. Click the Radio Button corresponding to your Type of Installation.l A Full Installation installs all software comp

Doors.NET Reference Manual- 68 -18. The default destination folder is listed in the destination folder field. Keri recom-mends using this folder for t

Doors.NET Reference Manual- 69 -20. Use the radio buttons to select if software access is to be granted to:l Current User Only (the user logged into t

Doors.NET Reference Manual- 7 -Alerts can be easily setup in Doors.NET to automatically give an indication in the soft-ware when a certain event occur

Doors.NET Reference Manual- 70 -server package) will be installed and then the database will be installed.l Scan the Network for Existing SQL Servers

Doors.NET Reference Manual- 71 -27. The installation process is complete once the software is installed, and a new data-base is created or an existing

Doors.NET Reference Manual- 72 -The software is now installed and ready for licensing and gateway configuration.

Doors.NET Reference Manual- 73 -License ManagerThe License Manager activates your software allowing use.Retrieve the License KeyA license key is provi

Doors.NET Reference Manual- 74 -Legacy controllers are carrying over from an existing Doors32 installation that is beingupgraded to Doors.NET. There i

Doors.NET Reference Manual- 75 -3. Under Installed Components, expand the Services list and click on the ApplicationServer call-out.4. Under the Regis

Doors.NET Reference Manual- 76 -6. Double-check your entry as an incorrect character will invalidate your softwareinstallation.7. Click ACTIVATE.l If

Doors.NET Reference Manual- 77 -l If the License Manager CAN connect to Keri's license server (requires an Internetconnection with external acces

Doors.NET Reference Manual- 78 -Activation via EmailIf the License Manager is unable to connect to the License Server it may be due to a fire-wall or

Doors.NET Reference Manual- 79 -3. Click the Offline Registration button and the ApplicationServerLicenseoffline.dlscfile is created.4. Locate the lic

Doors.NET Reference Manual- 8 -Doors.Net supports an unlimited number of software users and user groups. User rightscan be configured with limitations

Doors.NET Reference Manual- 80 -8. Copy the received ApplicationServerLicense.dlsc file into the C:\Keri\DoorsNET\directory.9. Reboot your PC to resta

Doors.NET Reference Manual- 81 -Verify LegacyPXL Controller CountsThe Capacities section lists the number of Legacy PXL controllers supported by your

Doors.NET Reference Manual- 82 -Verify Optional FeaturesAlso, you should verify that any optional licensed features are enabled.

Doors.NET Reference Manual- 83 -Exit the License ManagerClick Close to exit the License Manager. The next step is to configure the gateway usingthe Ga

Doors.NET Reference Manual- 84 -Licensed ApplicationsLicensed Applications are stand alone programs or plug-ins that add features or extendfunctionali

Doors.NET Reference Manual- 85 -Archive ServiceThe Archive Configuration Wizard is used to setup archiving of event information that isgenerated by th

Doors.NET Reference Manual- 86 -4. Select the Maximum amount of days to keep event information before archiving,(Min - 120 days, Max - 365 days)5. Sel

Doors.NET Reference Manual- 87 -9. The default SQL database Instance will be shown. Use the drop-down list to locatethe database Instance if it reside

Doors.NET Reference Manual- 88 -12. Click on Save Archive Server Settings and you should then see:13. Finally, close the configuration wizard and the

Doors.NET Reference Manual- 89 -Enroll ClientHelp content section under development.

Doors.NET Reference Manual- 9 -updates in real-time as the cardholders move throughoutthe facility. An occupancy counter updates as cardholders enter

Doors.NET Reference Manual- 90 -Global Linkage ServiceHelp Content Section Under Development

Doors.NET Reference Manual- 91 -IT Package ClientThe IT Package Client includes the professional Report Client, the Time and Attendanceinterface, and

Doors.NET Reference Manual- 92 -LDAP Import for Active DirectoryThe LDAP Import feature has two parts: a stand-alone LDAP Import utility and an LDAPSy

Doors.NET Reference Manual- 93 -l Runs on any Windows PC with .NET 3.5l Requires network connectivity to Doors.NET Application Server and AD DomainCon

Doors.NET Reference Manual- 94 -Managed Services ClientThe Managed Services client provides a means for remotely accessing, managing, andoperating a n

Doors.NET Reference Manual- 95 -Map ClientHelp content section under development.

Doors.NET Reference Manual- 96 -Multiple User ClientsMultiple user clients allows for multiple concurrent users to administer and monitor siteswithin

Doors.NET Reference Manual- 97 -and so on, these ports are automatically added to the Windows firewall during the install-ation process.

Doors.NET Reference Manual- 98 -EVR ClientThe Reflections Event Video Recording Client provides revolutionary integration ofvideo to any Doors.NET acc

Doors.NET Reference Manual- 99 -By using the Reflections client, customers are benefited by a common video user inter-face across multiple manufacture