Configuring Controllers GMS 4.07 - Technician Guide v1.0

GMS 4.
07
Graphical Management System
Configuring Controllers -
Technician Guide
800 010 014 Version 1.0 6/12/2010 © 2010 Pacom Systems

© 2010 Pacom Systems All Rights Reserved
No parts of this work may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language in any form by any means
without the prior written consent of Pacom Systems Pty Ltd.
Software License Notice

Your license agreement with Pacom Systems Pty Ltd, which is included with this product, specifies the permitted and prohibited uses of the product. It is
protected by Australian and international copyright laws and international treaty obligations. Your rights to use the Software are limited by the terms stated
below, and your use of the Software indicates your acceptance of these terms. If you do not agree with them, you must return, delete or destroy all copies
of the Software. Your rights to use the Software terminate immediately if you violate any of the terms stated below.
Any unauthorized duplication or use in whole or in part, in print, or in any other storage and retrieval system is forbidden.
You may not reverse-engineer, disassemble, decompile, or make any attempt to discover the source code of the Software.
You may not modify the Software in any way whatsoever.
Trademarks
All trademarks, brand and product names are property of their respective owners.
Pacom System Pty Ltd makes no warranty of any kind with regard to this product, including, but not limited to, the implied warranties of merchantibility and
fitness for a particular purpose. Pacom Systems Pty Ltd shall not be liable for errors contained herein or for incidental consequential damages in connection
with the furnishing, performance, or use of this product.
This document contains proprietary information and is protected by copyright. The information contained within this document is subject to change without
notice.
Configuring Controllers - Technician Guide
Table of Contents
..............................................................................................................................5
Introduction
Chapter 1: Setting .........................................................................................................8
Up Controllers
Setting DIP Switch Functions
...........................................................................................................................................9
Backing Up Controller Configurations and Using Templates
...........................................................................................................................................10
Connecting to GMS
...........................................................................................................................................12
Using a Keypad for Basic Configuration
.........................................................................................................................................17
Dialling in to Controllers
.........................................................................................................................................18
Setting Controller ID
...........................................................................................................................................20
Using the Controller Dialog Box
...........................................................................................................................................21
Configuring Controller Ports for Alarm Messaging
...........................................................................................................................................25
Configuring Primary IP Communications Over Ethernet
.........................................................................................................................................30
Configuring Secondary/Primary Communications Using PSTN
.........................................................................................................................................31
Configuring GSM Modems
.........................................................................................................................................34
Configuring GPRS Modems
.........................................................................................................................................36
Configuring Controller Ports for Contact ID/SIA Reporting
.........................................................................................................................................39
Configuring Controller RS485 Ports For Base Station Connection
.........................................................................................................................................41
Configuring EMCS Connections
.........................................................................................................................................43
Communications Protocol Parameters Reference
.........................................................................................................................................47
Contact ID and Basic Signal Protocol Templates
.........................................................................................................................................89
Configuring the Controller Timezone
...........................................................................................................................................91
Configuring TAPI (Telephony) Devices
...........................................................................................................................................92
Advanced Configuration Options
...........................................................................................................................................93
Configuring Alarm Panel Types
...........................................................................................................................................97
Predefined Compliance Configurations
.........................................................................................................................................99
Configuring Controllers for Transender Operation
.........................................................................................................................................101
Configuring Third-Party Alarm Panels
.........................................................................................................................................106
Configuring Generic Contact ID Alarm Panels
.........................................................................................................................................106
Configuring a Galaxy Interface
.........................................................................................................................................107
Configuring a Hisec Interface
.........................................................................................................................................109
Configuring a Tecom Interface
.........................................................................................................................................110
Using Controller Licensing Grace Period
...........................................................................................................................................112
Printing Controller Configuration Reports
...........................................................................................................................................114
Configuring and Using Controller Power Monitoring
...........................................................................................................................................115
Checking Controller Memory Battery Status
...........................................................................................................................................118
Controller User-Defined Commands
...........................................................................................................................................119
Chapter 2: Managing
.........................................................................................................122
Firmware
Controller Firmware
...........................................................................................................................................123
Device Firmware
...........................................................................................................................................127
Chapter 3: Configuring
.........................................................................................................130
Hardware Devices and Alarm Functions
Configuring Alarm Users Types
...........................................................................................................................................131
Configuring Keypads and Device Hardware
...........................................................................................................................................134
Auto-Configuring Connected Devices
.........................................................................................................................................141
Configuring Input and Output Points
.........................................................................................................................................142
Configuring Delayed Alarm Notification Points
.........................................................................................................................................148
Configuring Input Point Groups
.........................................................................................................................................151
Configuring Point Description Vocabs
.........................................................................................................................................153
Configuring Card Activated Keypad Mode Changing
.........................................................................................................................................155
Configuring Inovonics Devices
.........................................................................................................................................158
Installing Dedicated Micros DS2 Series DVRs
.........................................................................................................................................160
Configuring Controllers to Use OnSafe DVRs
.........................................................................................................................................161
Configuring General Alarm System Parameters
...........................................................................................................................................163
Configuring Alarm System Flags
...........................................................................................................................................167
Configuring Alarm Areas
...........................................................................................................................................172
Configuring Alarm Area Access
...........................................................................................................................................175
Creating Event Drivers and Macros
...........................................................................................................................................183
Using Hardware Serial Numbers
...........................................................................................................................................194
Contact ID and SIA Event Codes
...........................................................................................................................................195
.........................................................................................................198
Access Control
Configuring Access Area Profiles
...........................................................................................................................................202
Configuring Readers
...........................................................................................................................................204
Table of Contents | 3
Programming Card Data Formats

.........................................................................................................................................218
Card Reader Compatibility
.........................................................................................................................................222
Configuring Reader Time Schedules
...........................................................................................................................................223
Configuring Access Area Open/Close Schedules
.........................................................................................................................................226
Configuring Reader Event Drivers and Macros
...........................................................................................................................................227
Configuring Access Card Types
...........................................................................................................................................229
Configuring Degraded Mode Operation
...........................................................................................................................................231
Configuring Miscellaneous Global Access Settings
...........................................................................................................................................233
Configuring Third-Party Access Control Interfaces
...........................................................................................................................................234
Configuring a Schlage Wyreless Interface
.........................................................................................................................................235
Configuring Assa Abloy Aperio Lock-Readers
.........................................................................................................................................237
Configuring Sargent & Greenleaf IP Series Locks
.........................................................................................................................................239
.........................................................................................................242
Elevator Control
Configuring Ports for Elevator Control
...........................................................................................................................................243
Configuring Elevators
...........................................................................................................................................244
Configuring Unrestricted Floor Access
.........................................................................................................................................248
Configuring Elevator Readers
.........................................................................................................................................249
Viewing Elevator Status
...........................................................................................................................................251
.........................................................................................................254
Building Management Systems (BMS) Functionality
Configuring BMS BACnet Protocol, Inputs and Actions
...........................................................................................................................................255
Configuring BMS Modbus Protocol
...........................................................................................................................................258
Programming BMS Macros
...........................................................................................................................................261
Configuring Pulse Counters
...........................................................................................................................................262
.........................................................................................................266
Listen-In Operation
Wiring Up Devices
...........................................................................................................................................268
Setting Up GMS
...........................................................................................................................................269
Operating Listen-In Devices
...........................................................................................................................................270
.........................................................................................................272
Intercom Operation
Setting Up Internal (GMS) Intercoms
...........................................................................................................................................273
Setting Up External Intercom Systems
...........................................................................................................................................274
Scripting Intercom Actions
...........................................................................................................................................275
Intercom Script Commands
.........................................................................................................................................279
Chapter 9: Using
.........................................................................................................288
the IVR Facility
Chapter 10: Apendices
.........................................................................................................292
A...........................................................................................................................................292
- Using the 1057/8001 Controller LED Display
B...........................................................................................................................................294
- GMS32.INI File Reference
C...........................................................................................................................................304
- GMS Config Application Information
Index
.........................................................................................................................305
4 | Table of Contents
Introduction
This documentation is divided into several sections:
Setting Up Initial Controller Communications - Initial configuration requires a PC connected directly to the
Controller using a serial or cross-over network cable. Once you have established communications with GMS, the
complete configuration can be completed directly, or remotely.
Configuring Controller Hardware and Alarm Functions - The Controller requires configuration for its
attached hardware and also how it interacts with them for alarm functionality.
Note: Controller firmware version 5.00 (for 1057/1058) and 1.02 (for 8001) and later auto-detect
connected devices. The basic device configuration is uploaded when the Controller detects the device on
the RS485 device loop. To customize device configuration, proceed with normal Controller setup and GMS
configuration steps.
Configuring Access Control - The Controller requires configuration for access control functionality.
Configuring Elevator Control - The Controller requires configuration for access control functionality, if
required.
Configuring Business Management Systems - The Controller requires configuration for interacting with
third-party business management systems, if required.
Controller Firmware - The Controller uses locally stored firmware to control its functionality. Firmware
upgrades can be downloaded to Controllers without interruption to Controller operation.
Note: Procedures detailed assume that the Controller is online to a GMS terminal, unless otherwise stated.
Controllers and Remote Terminal Units

"Controller" is a generic security industry term that refers to a hardware device that controls the security of a site in a
remote location from the monitoring center. Traditionally Pacom has used the term "field controller" and "Remote
Terminal Unit" or "RTU" for this type of device. This term is no longer used. Throughout this documentation the term
"Controller" is used. Within GMS, the site number and the Controller number are synonymous. Although some
buildings may have more than one Controller, the term "site" refers to all areas controlled by a single Controller.
During any kind of configuration procedure it is always a good idea to have the Transaction Manager open. The
Transaction Manager helps you see what is occurring, whether correctly or incorrectly and in real-time (as it
happens) by continuously listing all communications between GMS and the Controller. Open the Transaction
Manager by clicking on the GMS toolbar.

Select the GMS Hardware menu for a range of configuration options. All hardware configuration is completed from
this menu.
Supporting Material
The following documentation may provide further assistance for installing and configuring Pacom Controllers:
Pacom Hardware Installation Guide.
CCU Configuration Guide.
TransIT Configuration Guide.
Using GMS - Operator Guide.
Configuring GMS - Administrator Guide.
Assumptions
For technicians, it is assumed that you have successfully completed an electrical trade or equivalent technical training
to satisfy local requirements and authorities. You may also be required to meet the requirements of the local
telecommunications authority during the installation of the equipment detailed in this guide. Some knowledge of
networks and network types is also required.
North American Compliance Note

At the time of print, 8001 Controllers are ETL approved to UL standards, however, are not approved by UL.
Introduction | 5
blank page
Chapter 1
Setting Up Controllers
7
For a Controller to communicate with the monitoring center over a network or using PSTN, some initial configuration
is required. There are three methods you can use to perform the initial configuration:
A laptop PC with GMS software installed (GMS laptop), connected to the Controller Diagnostic port using a serial
cable. Assign the Controller an address and configure the network port for remote management.
A keypad, connected to the Controller using an RS485 device line (see Using a Keypad for Basic Configuration
17 ). Configure the Controller internal modem so it can dial a remote GMS terminal.
A pre-configured External EEPROM Module (EEM), referred to as a configuration dongle, that plugs directly in to
the Controller RAP port. Using the appropriate DIP switch settings (see Setting DIP Switches 9 ), the Controller
downloads the configuration information.
The following is an outline of the steps required to bring a Controller online using a GMS laptop:
1. For new installations, reset the Controller to default parameters (see Setting DIP Switch Functions 9 ).
2. Connect a laptop/PC to the Controller (see Connecting to GMS 12 ).
3. Program the Controller address (see Setting Controller ID 20 ).
4. Configure port parameters (see Configuring Controller Ports for Alarm Messaging 25 ).
5. Create Controller accounts on the linecard (see the TransIT or CCU Configuration Guides).
6. Increase the Controller Diagnostic port connection speed (optional) (see Increasing the Diagnostic Port
Connection Speed (Baud Rate) 13 )
This section also details the most common Controller configurations and related port protocol parameters (see
Configuring Controller Ports for Alarm Messaging 25 ):
IP Over Ethernet.
PSTN.
Dial-Backup.
Dialup for Primary Connections.
8 | Chapter 1 - Setting Up Controllers

Setting DIP Switch Functions

All Pacom Controller PCBs have a block of four DIP switches. The DIP switches perform various functions during
power-up or reset, such as loading default parameters.
To perform DIP switch functions, switch all DIP switches to the ON position and power up or restart the Controller.
The Controller performs an initial self-test and:
The 8001 seven-segment diagnostic LED display cycles in a circular motion.
The 1057 seven-segment diagnostic LED display cycles in a circular motion.
The 1058 flashes LED#3 green.
The Witness seven-segment diagnostic LED display cycles in a circular motion.
Note: For a complete listing of LED display codes and meaning, see Using the 1057/8001 Controller LED
Display 292 .
When the self test is complete, ensure all DIP switches are returned to the OFF position. This is normal operation
mode setting.
Caution: Defaulting a live system causes all existing configuration settings to be lost.
DIP Switch Functions

DIP Switch Description
Normal operation.
Reset all parameters, except access control, to default. The Controller is also set to
Night mode (firmware 5.07/1.07 and later).
Read parameters from the External EEPROM Module (EEM).
Set the Diagnostic port to the default protocol settings. This setting is dependent on
firmware version, as follows:
Pre 5.00 - Pacom Communication Protocol (PCP) at 4800 baud rate regardless of
setting.
5.00 - 5.01 - Enhanced PCP protocol (EPCP) at 38400 baud rate (OFF for PCP at
4800).
5.02 - PCP at 4800 baud rate (OFF for EPCP at 38400).
Note: 8001 Controllers operate as per 105x Controller firmware 5.02.
Clear access control parameters only.
Self-test Controller on power up.
Note: Having DIP switches 1 and 4 ON at Controller power-up will set it to factory defaults. The
Controller is also set to Night mode (firmware 5.07/1.07 and later).
Chapter 1 - Setting Up Controllers | 9

Backing Up Controller Configurations and Using

Templates
This section describes how to save and load Pacom Controller configurations. You can save configuration files as a
backup and also use them as templates for setting up other Controllers.
Note: Controller configuration backup files contain the configuration data only, it does not backup the card
database stored in the Controller.
The "default" configuration options in pre GMS 4.00 releases are no longer supported. Some dialog boxes
still feature a Default button, which was designed to save that particular configuration as a "default" file.
This feature is no longer supported.
Templates can be applied directly to other Controllers of the same type, or upwardly from 105x to 8xxx Controller
models. For example, a template created from a 1057 Controller configuration can be loaded into a 1057 or 8001
Controller, but not a 1058. When a 105x template is applied to an 8xxx Controller, all compatible settings are applied
to the new Controller, however, incompatible settings require re-configuration.
Compatible Settings Incompatible Settings (require re-configuration)

Access control. On-board inputs (1058 only).
Alarm system On-board outputs (1058 only).
parameters. Controller IP address (if used).
Alarm system flags
(options). Controller Port Mapping
Alarm areas.
Mapping between 1057, 1058 and 8001 Controller ports is shown in the following
Alarm users. table. Highlighted 105x port configurations require re-configuration on 8000 series
Temporary schedules. Controllers:
Alarm time schedules. 1057 1058 8001
RS485 device loop. Port 1 (Ethernet 1) Port 1 (Ethernet) Port 11 (Ethernet 1)
Macros. Port 2 (Modem) Port 2 (Modem) Port 1 (EXPN 1)
Port 3 (RAP) Port 3 (RAP) Port 3 (EXPN 2)
Port 4 (RS232 2) Port ??? (RS232) Port 4 (EXPN 3)
Port 5 (Mezz 1) Port 9 (Mezz 1) Not available
Port 6 (Network) Port 4 (Network) Not available
Port 7 (Mezz 2) Not available Not available
Port 8 (Diagnostic) Port 10 (Diagnostic) Not available
Port 9 (RS232 1) Not available Port 9 (RS232) (on-board,
default settings)
Port 10 (RS485) Not available Port 10 (RS485) (on-board,
default settings)
Port 11 (RS485) Not available Not available
Port 12 (RS485/RS232) Not available Not available
Saving Controller Configurations

To save a Controller configuration (template), including the Controller ID number, system passwords, port and BMS
settings, proceed as follows:
1. Open the Controller dialog box and select the required Controller (see Using the Controller Dialog Box 21 ).
2. In the Controller dialog box, select File > Save Template to File. A Windows Save As dialog box opens, where
you can select a save location and name for the file. Click OK to begin the process. The Transaction Manager
will show the data upload activity from the Controller.
Applying Saved Controller Configurations

To load a saved a Controller configuration (template) into a Controller, proceed as follows:
2. In the Controller dialog box, select File > Load Template from File. A Windows Open dialog box opens, where
you can browse to and select a saved configuration file (*.rtu). Click Open to begin the process and display the
Controller Template dialog box.

Note: The alarm panel type configured when the template was created is applied (see Configuring Alarm
Panel Types 97 ).
3. In the Controller Template dialog box, make the necessary changes for the Controller (you cannot have more
than one Controller in the same system using the same ID number, IP address, etc).
4. Click OK to close the dialog box and begin loading the configuration (with the new settings). The Transaction
Manager will show the data download activity to the Controller. The Controller will restart after the download
completes.

Connecting to GMS
Pacom Controllers can be configured using a laptop with GMS software installed. There are two methods of connection
to the Controller from GMS:
Connect a serial cable from the laptop to the Controller Diagnostic port.
Connect a cross-over Ethernet cable from the laptop to the Controller Ethernet port.
When communication is established with the Controller, the Transaction Manager displays connection messages
and an icon is displayed in the lower right-hand corner of the main GMS application window, indicating successful
connection.
Note: If there is no configuration PC/laptop available, you can program the Controller ID number and a
dial-up phone number by connecting a keypad directly to a Controller RS485 device line port (see Using a
Keypad for Basic Configuration 17 ).
Creating a Serial Connection to the Controller
Using a Diagnostic Cable

The diagnostic cable connects the RJ12 connection on 1057/1058 Controllers, or three-pin PCB terminal CN3 on 8001
Controllers, to the laptop serial connection. Diagnostic cables are available from Pacom or can be made up using the
following pin connection table.
1057/1058 Controller Diagnostic Cable Pin Connections
Diagnostic Port (RJ12) Pin PC DB9 Pin

3 2
4 3
5 5
8001 Controller Diagnostic Cable Pin Connections

PCB Terminal CN3 Pin PC DB9 Pin
1 2
2 3
3 5
Using a GMS COM Port

The following procedure describes the process of establishing communications between GMS and the Controller
Diagnostic port. It is assumed the laptop or PC used for this operation has GMS installed.
1. Connect a diagnostics cable between the laptop serial port and the Controller Diagnostic port.
2. In GMS, select Hardware > Connection 1. The Connection Properties - Port 1 dialog box opens. You need to
set the laptop COM port parameters to match the Controller Diagnostic port parameters.
3. From the Connection list, select Enhanced PCP over Serial. The parameters change to represent the laptop
COM port parameters.
Note: GMS 4.05 supports PCP and enhanced PCP (EPCP) protocols.

The Controller Diagnostic port parameters can be determined in one of three ways:
For new installations, reset the Controller to default settings (see Setting DIP Switch Functions 9 ).
For existing systems, where the Controller is in communication with the monitoring system, the parameters
can be determined using the Controller Port Parameters dialog box from the monitoring PC (see Accessing
Port Parameters 27 ).
For existing systems, where the Controller is offline and cannot be reset to default, the only way to
determine COM parameters is by trial and error. That is, the COM port parameters must be varied until
communications are established. It is recommended that you try default parameters first. Failing that, select
a Baud Rate setting of either 38400 or 9600. You can also set the Diagnostic port to 4800 PCP or 38400
EPCP using Engineering mode.
4. In the Connection Properties - Port 1 dialog box, select the required Comm port from the COM list, and ensure
the appropriate parameters are set. The default parameters for all Pacom Controller serial ports (excluding the
Diagnostic port) are:
Connection - Enhanced PCP.
Baud Rate - 38400.
Parity - None.
Data Bits - 8.
Stop Bits - 1.
The default parameters for 105x Controller Diagnostic ports are:
Connection - Enhanced PCP if DIP switch 3 is OFF during cold boot, or PCP if DIP switch 3 is ON during cold
boot.
Note: The above Connection setting applies only to 105x Controllers. 8001 Controllers always use EPCP
regardless of DIP switch 3 setting.
Baud Rate - 38400 if DIP switch 3 is ON during cold boot, or 4800 if DIP switch 3 is OFF during cold boot
(see Setting DIP Switch Functions 9 ).
Parity - None.
Data Bits - 8.
Stop Bits - 1.
Note: To "cold boot" a Controller, set DIP switches 1 and 4 to ON, then restart the Controller. This sets
the Controller to factory defaults and the Diagnostic port to 4800 PCP. DIP switches 1, 3 and 4 defaults the
Controller also, but sets the Diagnostic port to 38400 enhanced PCP.
You can set the diagnostic port to 4800 PCP or 38400 Enhanced PCP using Engineering mode from a
keypad.
5. Click OK to close the Connection Properties - Port 1 dialog box.
Increasing the Diagnostic Port Connection Speed (Baud Rate)

Increasing the speed dramatically reduces the amount of time taken to complete firmware downloads and other
tasks. To change the baud rate, proceed as follows:
1. Establish communications with the Controller.
2. Open the Port Parameters dialog box (see Accessing Port Parameters 27 ) and click the Diagnostic port image.
The Port Protocol Parameters dialog box opens for the port.

3. From the Protocol list, select Enhanced PCP. This protocol (Enhanced Pacom Communication Protocol)
provides a 38400 baud rate and improved data transfer efficiency.
4. Click Download to save the new settings, then click Close to close the dialog box.
Note: Altering the Diagnostic port baud rate causes the Controller to lose communication with the GMS
laptop. The final steps in this procedure will bring the Controller back online.
5. In GMS, select Hardware > Connection 1. The Connection Properties dialog box opens.
6. From the Connection list, select Enhanced PCP over Serial.
7. Set the Baud Rate setting to 38400.
8. Click OK to close the dialog box. Communication with the Controller re-establishes shortly afterwards.
Note: Make a note of the baud rate setting (for example, a note on the Diagnostic port), so future
technicians will know what baud rate to set in GMS.
Creating an Ethernet Connection to the Controller

An Ethernet connection can be used to connect a laptop to the Controller. For direct Ethernet port-to-port
communications (no switch between), an Ethernet cross-over cable is required. Up to four machines running GMS can
connect to one Controller simultaneously, each using a different Connection ID number. Ethernet connection to GMS
does not require the Ethernet port to be enabled, however, if the port is disabled, the Ethernet settings on the
Controller cannot be changed, and the Controller will not connect to a Pacom Base Station using Ethernet.
Caution: Ethernet connectivity is designed to directly connect between the laptop and the Controller. If
the Controller Ethernet port is going to be used to connect to a Pacom Base Station, after configuration is
complete, ensure that the port is enabled and the IP address is correct. Where DHCP servers are used for
assigning IP addresses, re-assigning the IP address manually should not be required.
1. Set up the laptop with an IP address of "10.1.1.2" and a subnet mask of "255.0.0.0".
2. Connect the cross-over ethernet cable between the Ethernet ports of the laptop and the Controller.
3. In GMS, select Hardware > Connection 1. The Connection Properties - Port 1 dialog box opens.
4. From the Connection list, select PacLAN over IP. The parameters change to represent the laptop IP port
parameters.

5. Select a Connection ID number from the Connection ID list. This number represents a set of parameters that
the Controller retains for automatically accepting future GMS connections.
Note: Controllers can accept a Connection ID number of 1 to 4 only. If you are connecting to a TransIT
the Connection ID can range from 1 to 16.
6. In the Password ID field, enter the number that is used to connect to the Controller. The Password ID can
range between 1 and 8. By default, Connection ID 1 is the only one enabled in the Controller. To set passwords,
see Setting Controller Passwords 96 .
Note: Controllers can accept a Password ID number of 1 to 8 only. If you are connecting to a TransIT the
Password ID can range from 1 to 10.
7. In the Password field, enter the password for the associated Password ID number set in Step 5. The default
Connection ID 1 password is "Pacom" (case-sensitive). When a Controller is reset to factory defaults, the
password is reset to "Pacom".
Note: The default password for a TransIT is "Pacom001" (case-sensitive).
8. The Connection ID allows for different options when receiving messages. If the value is set to 1 (default), all
messages stored in the Controller are displayed upon connection. If 2, 3, or 4 are entered, messages stored in
the Controller will not be displayed upon connection. Only messages occurring after the connection are
displayed.
9. In the IP Address 1 field, enter the IP address of the Controller. The default IP address is "10.1.1.1".
10. Click OK to close the Connection Properties - Port 1 dialog box. When communication is established with the
Controller, the Transaction Manager displays connection messages.
Creating a Dialup Connection to the Controller

A dialup connection can be used to connect a laptop to the Controller.
1. Ensure a telephone line is connected to the laptop and another to the Controller.
2. In GMS, select Hardware > Connection 1. The Connection Properties - Port 1 dialog box opens.
3. From the Connection list, select Controller Dialup. The parameters change to represent the PSTN protocol
port parameters.

4. Select a Connection ID number from the Connection ID list. This number represents a set of parameters that
the Controller retains for automatically accepting future GMS connections.
Note: Controllers can accept a Connection ID number of 1 to 4 only. If you are connecting to a TransIT
the Connection ID can range from 1 to 16.
5. In the Password ID field, enter the number that is used to connect to the Controller. The Password ID can
range between 1 and 8. By default, Connection ID 1 is the only one enabled in the Controller. To set passwords,
see Setting Controller Passwords 96 .
Note: Controllers can accept a Password ID number of 1 to 8 only. If you are connecting to a TransIT the
Password ID can range from 1 to 10.
6. In the Password field, enter the password for the associated Password ID number set in Step 5. The default
Connection ID 1 password is "Pacom" (case-sensitive). When a Controller is reset to factory defaults, the
password is reset to "Pacom".
Note: The default password for a TransIT is "Pacom001" (case-sensitive).
7. The Connection ID allows for different options when receiving messages. If the value is set to 1 (default), all
messages stored in the Controller are displayed upon connection. If 2, 3, or 4 are entered, messages stored in
the Controller will not be displayed upon connection. Only messages occurring after the connection are
displayed.
8. Click OK to close the Connection Properties - Port 1 dialog box.
9. Establish communications with the Controller using the Hardware > Dial Connect option (see Dialling in to
Controllers 18 ).

Using a Keypad for Basic Configuration

If there is no configuration PC/laptop available, you can program the Controller number and a dialup telephone
number by connecting a keypad directly to a Controller RS485 device line port. Once you have done this, the rest of
the configuration can be completed using a GMS computer attached to a Base Station.
Caution: This procedure should only be performed on a new installation, as you need to reset the
Controller to default parameters for it to communicate with the keypad.
Configuring a Controller Directly Using a Keypad

To configure the Controller number from a keypad, proceed as follows:
1. Connect a Pacom keypad to one of the Controller RS485 device line port(s).
Note: For 8001 Controllers, attach the keypad to the connector block next to the Ethernet port(s) - Pin 2
to Tx; Pin 3 to Rx; Pin 5 to GND.
2. Connect a 12V power supply and power up the Controller.

3. Configure the keypad address as Device Address 1 (see the appropriate keypad installation manual for
instructions on programming their device addresses).
4. With the system in Day mode (press the DAY key and enter default ID = "1" and PIN = "2461"), log on as
Engineer (default ID = "2", PIN = "2462"). as follows:
Press the LOG ON softkey.
Press the 1 key, then press the ENT key.
Press the 2, 4, 6 then 2 keys, then press the ENT key.
5. Press the LOG ON softkey again to display the Engineering menu.
6. Press the CONFIG softkey.
7. Press the RTU No softkey.
8. Enter the required Controller number (usually obtained from the Base Station administrator).
9. Press the ENT key on the keypad. After the new data loads ("EEPROM burn"), the keypad display returns to the
initial Engineering menu:
10. Press the LOG ON softkey to display the Engineering menu.
11. Press the CONFIG softkey.
12. Press the NETWORK softkey.
13. Press the DIALUP softkey.
14. Press the PACOM softkey.
15. Enter the telephone number of the PSTN card in the Base Station. "Attempting dialup recovery" is displayed on
the keypad and the Controller attempts to connect to the GMS location. Press the REFRESH softkey every 10
seconds to update the status of the dialup connection. Once the connection is made the keypad displays
"Connected".
16. Once the connection is made, configure the Controller from the GMS site or download an existing configuration
using the dialup connection.

Dialling in to Controllers
You can use GMS to dial directly into a Controller to configure it. Dialling into a Controller is generally performed
through a Pacom Base Station, where GMS dials into the Base Station, which in turn dials into the Controller.
GMS can also dial directly into a Controller using an external modem. Pacom recommends the following modems to
be used:
U.S. Robotics Model 0701.
U.S. Robotics Model 5686.
Note: If another modem type is used, ensure the modem has auto-answer mode enabled.
This section applies to 1057/1058 Controllers with firmware 4.08 to 4.11. To dial into 1057/1058
Controllers with firmware 4.12, see Creating a Dialup Connection to the Controller 15 .
Configuring the Controller Network Port

To setup the Network port parameters, proceed as follows:
2. Select General > Network > Port Settings. The Port Parameters dialog box opens.
3. Select the Port Parameters option.
4. Click the Network port image. The Port Network protocol Parameters dialog box opens.
5. Select Enhanced PCP Protocol from the Protocol list.
6. Click Download, then Reboot to save settings.
7. Click Close. The dialog box closes.
8. In the Port Parameters dialog box, click Advanced, then select Controller Settings. The General System
Parameters dialog box opens
9. In the Settings for Port list, select Network.
10. In the Port Priority list, select No Priority.
11. Click Download, then Close. Network port configuration is now complete.
Configuring GMS for Direct Dial In and Connection

To configure GMS to dial directly into a Controller, proceed as follows:
1. In GMS, select Hardware > Dial Connect. The Dial dialog box opens.
2. In the TAPI Line list, select the modem (or other TAPI device) that is attached to the PC running GMS.
Note: Only TAPI devices that have been registered with Windows and are functional with GMS are
displayed. The TAPI device must support data transmission.

3. For modems, click Configure Line. The selected modem configuration options are displayed in a dialog box.
a. In the Port Speed list, select 38400 and click OK to close the dialog box and return to the Dial dialog box.
4. In the Phone Number field, enter the phone number of the modem connected to the Controller. Use the
country and area code prefix options, if required.
To make the telephone number selectable from the Dialers list, so that you do not have to enter them manually
each time, click Edit Speed Dial. The Speed Dial dialog box opens.
a. In the Name field, enter a name to reference the telephone number by.
b. In the Phone Number field, enter the telephone number to dial.
c. Click Save. You can add other speed dial numbers as required. When finished, click Close.
Once GMS is connected, the Call Status region in the Dial dialog box displays "Line Connected". Watch the
Transaction Manager until you see it confirming the connection, then you can configure the Controller as
required.
5. When configuration is complete, click Hangup in the Dial dialog box and click Yes when a confirmation box
displays.

Setting Controller ID
Each Controller in a system requires a unique identifier, or address. This ID is a number that GMS uses to recognize
the Controller. Controller ID numbers can range from 1 to 9999, with "1" being the default address for all Pacom
Controllers.
Note: During installation, you must assign the Controller an ID not already in use by another Controller.
To assign an ID (address) to a Controller, proceed as follows:

1. In GMS, select Hardware > Change Controller ID. The Program Controller ID dialog box opens.
2. In the Enter Current Controller ID field, enter the existing ID number of the Controller you want to change.
3. In the Enter New Controller ID field, enter the new ID number for the Controller.
Caution: Make sure that you have the correct ID number for the Controller. If two Controllers are
assigned the same ID number, the second one assigned may not be able to communicate with the system
properly.
Note: The Network Type and Encoding Type selections only apply to the 1050/1060 and are ignored
by later model Controllers.
4. Click OK to complete the process and close the dialog box.

You must use the new Controller ID to access the Controller parameters.

Using the Controller Dialog Box

Most Controller configuration procedures are completed using the Controller dialog box (the ID number of the
selected Controller appears in the dialog box title). In previous versions of GMS, this was known as "RTU
Parameters".
Pacom Controllers provide complete alarm panel functionality. They also provide an interface to third-party alarms
panels - referred to as "interface mode". Operating in interface mode, the Controller functions as a protocol
translator, that is, it receives alarm messages from the third-party panel and forwards them over the network to the
monitoring station.
The following settings are defined from the Controller dialog box:
Alarm areas (see Configuring Alarm Areas 172 ).
Hardware devices, for example, inputs, outputs and keypads (see Configuring Controller Keypad and Device
Hardware 134 ).
General system parameters and options, for example timeouts, test modes and PIN options (see Configuring
General Alarm System Parameters 163 ).
Hours of operation, for example, normal hours and cleaner access times (see Configuring Alarm Area Access 175
).
Alarm vocabs (see Configuring Controller Keypad and Device Hardware 134 and Configuring Point Description
Vocabs 153 ).
Note: For configuration changes to take effect, they must be downloaded to the Controller. Configuration
dialog boxes all have a Download button for this purpose. Upon download, the Controller reboots
automatically and the changed configuration comes into effect.
In GMS 4.00+, Controller configuration is completed using the Controller dialog box. There are two main displays in
the dialog box:
The Controller Status display (above) represents a summary of current Controller conditions. The Hardware
display (below), also known as the "device map" (select Alarm > Configure > Hardware) is a graphical
representation of the hardware configuration, showing the various pieces of hardware (Keypads, I/O devices, etc)
attached to the Controller. The alarm areas configured in the Controller and those controlled by keypads are
represented as colored squares. In the case of keypads, the colors also represent alarm areas that are controlled by
the keypad. Controller alarm parameters for each device are also uploaded to GMS when you open the device map.
The device map is divided into three columns:
Keypads 135 .
Local Devices 135 .
Remote Devices 135 .

While this dialog box is different to earlier versions, the functionality for configuring Controllers remains the same. It
is the method for accessing each configuration function that has changed (see Layout of the Controller Dialog Box 22
).
The steps required to access the Controller dialog box are repeated regularly in the configuration documentation and
is therefore described only once.
To access Controller configuration options:
1. In GMS, select Hardware > Controller Settings. The Controller dialog box opens. Alternatively, from the
Summary Manager window, right-click the site you want to access the Controller for, then select Controller
Settings from the context menu.
2. In the Controller ID field, enter the Controller ID number, then click Change.
Note: If you are accessing the Controller dialog box from the Summary Manager, there is no need to
enter the Controller ID.
At any time, click Refresh to update the dialog box display with any changes that have been made.
Layout of the Controller Dialog Box

The Controller dialog box displays an overview of the selected Controller, outlining the current status of the Controller
and its related devices and points. The identification number (address) of the current Controller is displayed in the
Controller ID field and in the title bar of the dialog box. The name, type and other details of the Controller are also
displayed alongside the Controller ID field, below the menu bar.
Use the options in the tree on the left hand side of the dialog box to view the status and other details for the
Controller and related devices. You can access all Controller configuration commands from the dialog box menus.
Note: For a list of old RTU Parameters dialog box (GMS 3.84 and earlier) commands and their new
location in the Controller dialog box, see the Controller Menu and Command Changes topic.

To display/access a different Controller, type the address of the Controller you want to access in the Controller ID
field, then click Change.
Accessing Configuration Settings for Non-Pacom Alarm Panels/

Controls
When non-Pacom Controllers are used, the Controller dialog box is not used. Instead, the previous GMS RAP
configuration dialog boxes are used. The available functions are the same, however, the method of accessing them
differs from a single dialog box to multiple dialog boxes that you can access from the previous Controller Config
Options dialog box (shown below).

This dialog box acts as the access point to the various available configuration options (instead of through the
Controller dialog box). To access the various configuration screens, select the configuration type from the Options
list, then click OK. The corresponding dialog box opens, as it would from selecting the same option using the menu
system in the Controller dialog box for Pacom Controllers.

Configuring Controller Ports for Alarm Messaging

Port configuration for alarm messaging defines how the Controller establishes communications with GMS (using Base
Station or TransIT hardware), or to third-party receivers using Contact ID or SIA message formats (see Contact ID
and SIA Event Codes 195 ).
Each port is assigned a priority. The priority determines the order in which each port is used. For example, if the
Ethernet port operates with primary priority and the Modem port operates with secondary priority, a loss of primary
network communication will cause the secondary Modem port to be used. Port priorities include:
Primary - The port is used as the first option for alarm reporting.
Secondary - If the Primary priority port fails, this port is used for alarm reporting.
Tertiary - If the Primary and Secondary priority ports fail, this port is used for alarm reporting.
Dual Alarm Reporting - The port is used in conjunction with any Primary/Secondary/Tertiary port for
simultaneous alarm reporting to a second monitoring system. This can be used for Contact ID or SIA reporting
as well.
Note: Only Modem (dialup) ports support Contact ID or SIA reporting.
No Priority - The port is not be used for alarm reporting.

Generally, primary priority is assigned to the Ethernet or Network port for network communication to a linecard.
Secondary priority is assigned to dialup, and tertiary to a wireless or GSM modem.
For secondary/tertiary ports, which are designed for dialup communications, you can program an array of numbers
into the system. There are three groups of numbers:
Comms #1 and 2 - Are numbers to dial when the Controller needs to send "non-important alarm" messages.
Alarm #1 and 2 - Are numbers to dial when the Controller needs to send "important alarm" messages.
Disaster #1 and 2 - Are numbers to dial in the event that primary, secondary and tertiary (if used) communications
cannot be established.
Whenever the Controller has had to use a non-primary port for alarm messaging, it will always default back to the
primary when it becomes available again. In cases where further alarm messages need to be sent and the primary is
still unavailable, the Controller will attempt to communicate over the secondary/tertiary ports or disaster numbers (if
necessary).
The following two sections illustrate the dialling sequences that the Controller will execute in an attempt to establish
communications.
General Contact Sequence

Port Priority Contact Sequence

Port Configuration Overview

Pacom Controllers can communicate with the linecard over a variety of network types. Controller operation is
completely transparent to the data network. If the network or data-line fails the Controller can be configured to
automatically use the Public Switched Telephone Network (PSTN) or cellular telephone networks to re-establish
communication with the linecard (TransIT or CCU).
The following commonly used protocols for communicating with the linecard are detailed:
IP Over Ethernet 30 .
PSTN 31 .
Other communication protocols used by Pacom Controllers include:
SNA.
IP Token Ring (using adaptor).
X.25.
SLDC Poll.
IP over PPP (for example, GPRS).
For information regarding the configuration of Controllers for operation over other network types contact Pacom
Support at support@pacom.com.
Accessing Port Parameters

If a Controller is online to a linecard, its port parameters can be accessed from any GMS monitoring PC. Port
parameters can also be accessed using a GMS laptop or PC directly connected to the Controller (see Connecting to
GMS 12 ).
The following procedure describes the process of accessing Controller port parameters.
2. In the Controller dialog box, select General > Networks > Port Settings. The Controller Port Parameters
dialog box opens. This dialog box and the displayed ports vary depending on the type of Controller.
3. Enable the Port Parameters option. Each port maintains a set of parameters and error statistics. The options at
the bottom of the dialog box are used to select whether or not parameters or error statistics display when a port
is selected.
4. Click the required port. The Port Protocol Parameters dialog box opens for the selected port. The parameters
displayed within the dialog box vary depending on the selected port. The following image shows the dialog box
for the Ethernet port.

Dual Communications Port Connection Capabilities

GMS supports two communications connections, or "channels" for connection redundancy between it and a Controller,
TransIT, Base Stations or Pacom Port Combiner (PPC) data multiplexer. Each channel can be configured using
different protocols and parameters for the target device type and can be manually switched to at any time, if
required. Data from the target device is sent to both channels, however, messages received on the channel that is
not currently being used are discarded to prevent message duplication in GMS.
Note: GMS stores hardware connection information in a COMMS.INI file in the GMS\Customer\NotSynch
folder. This file is not automatically synched between GMS servers, therefore, allowing individual
connection parameters for each server.
To configure the communication channel, proceed as follows:

1. In GMS, select Hardware > Connection 1 or Connection 2. The Connection Properties dialog box opens for
the selected channel.
2. In the Connection list, select the required connection type. Each connection type presents a range of
parameters specific to it.
3. Enter the parameters as required (see Connecting to GMS 12 ).
To switch communications channel, proceed as follows:
1. In GMS, select Hardware > Set Active Connection. A dialog box displays to confirm the switch.

2. Click Yes to confirm the switch.

GMS stops displaying messages received on the previously active connection and begins displaying messages
received on the newly selected one.
Note: Two connections must be configured to be able to switch between them.

Releasing the connection (Hardware > Release Connection) stops GMS from displaying messages from
the previously active connection, however, does not automatically start displaying messages from the
other channel.
Port Protocol Parameter Descriptions

The following sections describe commonly used Controller port protocols and parameters.
Asynchronous Driver Parameters 47 .
Base Station Parameters for IP Networks 30 .
Base Station Parameters for Dialup 31
Pacom Communications Protocol 70 .
Enhanced Pacom Communications Protocol 25 .
UDP/IP on Ethernet 25 .
RS485 Device Loop 25
ASCII Protocol 49 .
Logging Printer Protocol 68 .
Controller Dialup Parameters 25 .

Configuring Primary IP Communications Over Ethernet

IP over Ethernet is used when Controller communications are to be transmitted over an IP Ethernet network, or if a
dedicated security IP LAN/WAN network is present. Each Controller must have an IP address configured.
By default, the onboard Ethernet ports connect using the UDP/IP protocol. A simplified version of TCP/IP is also
available with onboard Ethernet Ports.
Note: TCP/IP is an alternative type of IP protocol and is only used on IP networks that do not allow, or
support, UDP traffic. UDP is the recommended protocol.
You should consider the following when operating IP over Ethernet:

The required bandwidth is low due to the small size of alarm and access control messages.
Ethernet connectivity must use 10BaseT RJ45 connections.
IP addresses should be obtained from a network administrator prior to configuration. Subnet masks must be the
same as the monitoring PCs if both are on the same Ethernet segment.
The equipment can also communicate over a VLAN, if this is set up. The VLAN must support UDP data packets
for default UDP/IP operation.
Configuring a Primary IP Connection

To configure the Controller to use an UDP/IP Ethernet network port, proceed as follows:
1. Establish communications with the Controller (see Connecting to GMS 12 ).
2. Open the Port Parameters dialog box (see Accessing Port Parameters 27 ), select the Port Parameters option,
then click the Ethernet port image. The Port Protocol Parameters dialog box opens for the port.
3. Click the Session Level tab and:
a. From the Protocol list, select UDP/IP Protocol on Ethernet.
Note: On a defaulted Controller, the UDP port number is 3435 (for 1057/1058 firmware version 5.06 or
higher, for 8001 firmware version 1.06 of higher).
b. In the IP address of local node field, enter the Controller IP address.

c. In the Subnet Mask of local node field, enter a subnet mask for the Controller.
d. In the IP address of a router field, enter the IP address of the router. If a router is not present, leave
default parameters. Leave all other parameters as default.
4. Click the Application Level tab and:
a. From the Port Priority list, select Primary Priority. Leave all other parameters as default.
Note: To disable the Ethernet port from reporting alarms, set the Port Priority setting to No Priority.
5. Click the Base Station tab and:

a. From the Protocol list, select UDP/IP Protocol on Ethernet.
b. In the Linecard A region, from the Line 1 list, select IP address and enter the IP address of the TransIT/
CCU/linecard port to which the Controller connects in the adjacent field.
Note: For more information regarding Base Station tab parameters for Ethernet operation, see UDP/IP on
Ethernet Parameters 78 .
6. Click Download to save and apply the new settings. The Transaction Manager window displays a list of
messages confirming the changes.
Caution: The Close button does not save or apply any changes. You must click Download before closing
the dialog box to save and apply your changes.
7. Click Close to close the dialog box and return to the Port Parameters dialog box. Once the initial configuration is
complete, the Controller can be remotely managed over the network.
For more information on UDP/IP on Ethernet protocol parameters, see Communications Protocol Parameters
Reference 78 .

Configuring Secondary/Primary Communications Using

PSTN
The Controller onboard modem can be configured to use the Public Switched Telephony Network (PSTN) to send
alarm messages. PSTN is generally used as a secondary means of reporting. In such cases, the configuration is
referred to as "dial-backup". A dialup connection can also be used as the primary means of communication (see
Configuring a Primary Dialup Connection 32 ).
Unlike Controllers operating over other network types (for example, LAN or IP), a Controller using dial-backup to
contact a Base Station does not need to own an account on the linecard in order to communicate with it. Rather, the
Controller is programmed with the Base Station telephone number, which it dials to connect.
Note: If a primary network connection is already present, the Controller can be configured for dial-backup
using the existing GMS connection.
Dialup connections can also be used to dial mobile/cell telephone numbers using the PSTN network (no GSM modem
required). This allows the Controller to notify of an alarm by calling a particular number. The details of the alarm are
not provided. Calls made this way will comply with the normal timeout and retry settings. If the call is answered for at
least three seconds before the call is ended [by the call receiver], the Controller clears the alarm queue.
Configuring a Dial-Backup Connection

To configure a Controller for dial-backup alarm reporting using PSTN, proceed as follows:
2. Open the Port Parameters dialog box (see Accessing Port Parameters 27 ), select the Port Parameters option,
then click the Modem or Phone Line port image. The Port Protocol Parameters dialog box opens for the port.
3. Click the Link Level tab and:
Select the Modem Driver option.
From the Port Priority list, select Secondary Priority.
Note: The Port Priority setting must be set to Secondary Priority in order to avoid a conflict with the
existing primary network connection.

Select the Telephone Numbers option.
In the Telephone Numbers region, in the Comms #1 list, select from:
Unused - Select to disable the connection.
Pacom - Select to contact a Base Station linecard.
Contact ID - Select to report in Contact ID format (generally for third-party receivers).
SIA Format - Select to report in SIA format (generally for third-party receivers).
SMS Format - Select to report in short message service format (generally for contacting a person
directly).
Note: To set the port to call a mobile/cell telephone number to notify of alarms (notify only - no alarm
details are provided), select either Contact ID, SIA Format or SMS Format, then enter "****" (four
asterisk characters) in the appropriate predial# field. For example, if Alarm#2 is to be used for
notification, enter "****" in the Predial# for Telephone#2 field.
Enter the appropriate telephone number in the adjacent field.

In the Alarm #1 list, follow the procedure above for the Comms#1 setting.
For more information on the different telephone numbers, see Telephone Numbers 53 .
Note: "Comms" numbers are used for reporting network status messages and "Alarm" numbers are used
for reporting alarm messages. There must be at least one number present for each message type. While
you can use the same number for both, it is not recommended because network status reporting may
obstruct more important alarm messages from being received. It is therefore recommended that, as a
minimum, the receiver (for example, Base StationCCU/TransIT linecard) has at least two modems - one
dedicated to alarm reporting and the other to network status reporting (for information regarding linecard
configuration, see CCU or TransIT Configuration Guides).
If required, in the Predial # for Telephone #1 field, enter the prefix that corresponds to the telephone
number entered. This is used for dialling an outside line where a PABX is used. If no prefix is required, leave
the field blank. If using the port to call a mobile/cell, enter "****" in the field.

If required, in the Postdial # for Telephone #1 field, enter the postdial number that corresponds to the
telephone number entered in the previous step. Postdial numbers are used when, for example, a PIN or
extension number is required after a connection has been established. If no postdial number is required,
leave the field blank.
For more information regarding Base Station parameters for dial-up operation, see Base Station Parameters
for Dialup 53 .
6. Click Close to close the dialog box and return to the Port Parameters dialog box.
For more information on Controller Dialup protocol parameters, see Communications Protocol Parameters Reference
51 .
Configuring a Primary Dialup Connection

To configure a Controller dialup port for primary communications, proceed as follows:
2. Open the Port Parameters dialog box (see Accessing Port Parameters 27 ) and click the Modem or Phone Line port
image. The Port Protocol Parameters dialog box opens for the port.
a. Select the Modem Driver option.
b. From the Port Priority list, select Secondary Priority.
Note: Although the internal modem will provide the primary method of communication, it is recommended
that the Port Priority setting be set to Secondary Priority. If no network connection is available, the
Controller still dials out.

a. Select the Telephone Numbers option.
b. In the Telephone Numbers region, in the Comms #1 list, select Pacom and enter the linecard telephone
number in the adjacent field.
Note: To set the port to report in SIA or Contact ID formats (for third-party monitoring) select the
required format from the Comms list.
c. In the Alarm #1 list, select Pacom and enter the linecard telephone number in the adjacent field.
d. For more information on the different phone numbers, see Telephone Numbers 53 .
Note: Comms numbers report network status messages and alarm numbers report alarm messages.
There must be at least one number present for each message type. While you can use the same number
for both, it is not recommended because network status reporting may obstruct more important alarm
messages from being received. It is therefore recommended that, as a minimum, the CCU/TransIT
linecard has at least two modems - one dedicated to alarm reporting and the other to network status
reporting. For information regarding linecard configuration see the CCU or TransIT Configuration Guides.
e. If required, in the Predial # for Telephone #1 field, enter the prefix that corresponds to the telephone
the field blank.
f. If required, in the Postdial # for Telephone #1 field, enter the postdial number that corresponds to the
leave the field blank.
g. Under the Base Station tab, select the Parameters option. All parameters in this tab should remain as
default.
For more information regarding Base Station tab parameters for dialup operation, see Base Station
Parameters for Dialup 53 .
5. Click Download to save and apply the new settings. The Transaction Manager displays a list of messages
confirming the changes.

7. Once configuration of Internal Modem Protocol Parameters is complete, you must disable the Ethernet port. For
information regarding Ethernet port configuration Configuring Primary IP Communications Over Ethernet 30 .
Testing Dialup Connections

2. In the Controller dialog box, select Commands > Test > Perform Dialup Test. The Controller Port Parameters
3. The Transaction Manager window displays a string of messages to indicate the status of the test. It displays
"Dialing Telephone number #X", where X represents the telephone number programmed in the Base Station
parameters, as per the following table.
Telephone Number Base Station Programming

#1 Comms #1
#2 Alarms #1
#3 Comms #2
#4 Alarms #2
#5 Disaster #1
#6 Disaster #2

Configuring GSM Modems

GSM modems can be used as a backup priority line if primary communications fail. Generally, a GSM modem is setup
with tertiary priority (with dialup as secondary priority).
Note: The following configuration is for data transfer only, and not for sending SMS through the GSM
network.
Configuring Controller Ports for GSM

To set up a Controller to use a GSM modem, proceed as follows:
2. In the Controller dialog box, select General > Network > Port Settings. The Controller Port Parameters dialog
box opens. This dialog box and the displayed ports vary depending on the type of Controller.
3. Click the Phone Line/Modem port image. The Port Protocol Parameters dialog box opens for it.
4. In the Protocol list, select Controller Dialup Protocol.
5. In the Link Level tab, select the Modem Driver option. The modem driver parameters display.
6. In the Port Priority list, select the appropriate priority for using the GSM modem (generally, Secondary
Priority or Tertiary Priority options).
7. In the Modem Type list, select Falcom GSM modem.
b. In the Telephone Numbers region, in the Comms #1 list, select Pacom and enter the mobile telephone
number to receive the communications in the adjacent field.
Note: GSM does not use tone dialling. Contact ID and SIA Format require tone handshaking to operate,
therefore, will not operate with a GSM modem. A fixed phone line must be used for Contact ID and SIA.
c. In the Alarm #1 list, select Pacom and enter the mobile telephone number in the adjacent field. Generally,
this number is the same as for Comms #1.
d. If required, in the Predial # for Telephone #1 field, enter the prefix that corresponds to the telephone
the field blank.
e. If required, in the Postdial # for Telephone #1 field, enter the postdial number that corresponds to the
leave the field blank. For more information regarding Base Station parameters for dialup operation, see Base
Station Parameters for Dialup 53 .
f. Select the Parameters option.
g. In the Dialback Parameters region, select the Dialback Time option and select a time of day for the
Controller to contact the receiver from the adjacent list. This is a regular contact setting so that the system
regularly checks that the communications are viable. Ensure that the receiver is not busy at the time you
select.
h. Enable the Apply Message Filters before Dialup option to ensure that the required messages are sent.

the dialog box to save and apply changes.
51 .

Configuring GPRS Modems

GPRS modems can be used as a backup priority line if primary communications fail. Controllers can connect to
external third-party modems using a serial connection. 8000 series Controllers are also able to use an 8201 GPRS
Modem card, which plugs into a Controller expansion slot (see 8000 Series Hardware Installation Guide).
Configuring Controller Ports for GPRS

To set up a Controller to use a GPRS modem, proceed as follows:
box opens. This dialog box and the displayed ports vary depending on the type of Controller (8001 Controller
screen shown).
3. On the image, click the expansion card slot that has the GPRS modem card installed, or for third-party external
modems, the image of the port that the modem is connected to. The Port Protocol Parameters dialog box opens
for it.
Note: Apart from the specific settings detailed below, leave all other paramters at their default settings.

a. In the Protocol list, select UDP/IP on PPP.

b. Set Baud Rate to 115200 for 8201 card, or 38400 for serially connected modems.
c. Enable the Enable LCP Echo option.
d. In the Modem string to use list, select 2.
e. In the Modem Type list, select Pacom GPRS for 8201 GPRS expansion card, or Wavecom GPRS or
Multitech GPRS for third-party modems.
f. Enable the Force download modem string option.
5. Click the Session Level tab and:
a. Select the UDP/IP Parameters option.

b. In the IP address of local node field, enter the 0.0.0.0.
c. In the Subnet mask of local node field, enter the 0.0.0.0.
d. In the IP address of a router field, enter the 0.0.0.0.
e. In the IP address of another router field, enter the 0.0.0.0.
6. Click the Application Level tab and:

a. In the Port Priority list, select the appropriate priority for using the GPRS modem (generally, Secondary
Priority or Tertiary Priority options).
b. Enable the Enable network idle poll to maintain IP connection option.
a. In the Linecard A region, Line 1 list, select IP address.

b. In the field adjacent to the Line 1 list, enter the destination IP address of the Base Station linecard Ethernet
port.
the dialog box to save and apply changes.
For more information on UDP/IP on PPP protocol parameters, see Communications Protocol Parameters Reference 84 .

Configuring Controller Ports for Contact ID/SIA Reporting

You can set up Controllers to contact a third-party digital receiver or alarm panel and report to it using industry
standard Contact ID or SIA messaging formats. The Controller connects using either dialup or serial port
communications.
Reporting Over Dialup

To set up a Controller for Contact ID/SIA reporting over dialup, proceed as follows:

4. Click the Phone Line/Modem port image. The Port Protocol Parameters dialog box opens for it.
b. In the Telephone Numbers region, in the Comms #1 list, select either the Contact ID or SIA Format
option and enter the telephone number in the adjacent field.
c. In the Alarm #1 list, select either the Contact ID or SIA Format option and enter the telephone number in
the adjacent field. This is usually the same number as for Comms #1. For more information on the different
phone numbers, see Telephone Numbers 53 .
d. If required, in the Predial # for Telephone #1 field, enter the prefix that corresponds to the telephone
the field blank.
e. If required, in the Postdial # for Telephone #1 field, enter the postdial number that corresponds to the
leave the field blank. For more information regarding Base Station parameters for dial-up operation, see
Base Station Parameters for Dial-Up 53 .
f. Select the Parameters option.
g. In the Dialback Parameters region, select the Dialback Time option and select a time of day for the
Controller to contact the receiver/alarm panel from the adjacent list. This is a regular contact setting so that
the system regularly checks that the communications are viable. Ensure that the receiver/alarm panel is not
busy at the time you select.
h. Enable the Apply Message Filters before Dialup option.
complete, the Controller can be remotely managed using the network.
51 .

Reporting Over a Serial Port

To set up a Controller for Contact ID/SIA reporting over a serial port, proceed as follows:

4. Click the RS485 port image. The Port Protocol Parameters dialog box opens for it.
6. In the Link Level tab, select the Modem Driver option. The modem driver parameters display.
7. In the Port Priority list, select a priority for reporting. Generally, an Ethernet would be primary priority, with
other ports used for back-up. There is also a dual reporting priority that reports alarms in parallel, using two
communications channels.
8. In the Modem Type list, select CID/SIA over Serial Port.
9. Set the Time between polls to modem field to 10.
Select the Telephone Numbers option.
In the Telephone Numbers region, in the Comms #1 list, select either the Contact ID or SIA Format
option and enter a dummy telephone number in the adjacent field.
Note: If you select Contact ID for the Disaster# setting, a copy of the alarms are saved to be
transmitted over the primary communication port.
12. Click Close to exit the dialog box and return to the Port Parameters dialog box. Once the initial configuration is
51 .

Configuring Controller RS485 Ports For Base Station

Connection
You can use the Controller RS485 port to connect multiple Controllers, in a daisy-chain fashion, to a Pacom Base
Station when no local network is available. The Controllers should be located in the same building. Generally, a
screened cable is required for this, with a maximum total cable run of 1000 meters (3000 feet).
The Controller RS485 port is recommended for connections to a Base Station. When using RS485, the Controller port
links must be set accordingly. Links are set for either RS232 or RS485 operation and additional links must be set
where line termination is required.
Note: When using the RS485 in this way, no other devices (for example, keypads, 1065, etc.) can be
attached to the port.
Hardware setup, such as link settings, cabling requirements and expansion boards is beyond the scope of this
documentation. For more information on these topics and other Controller related hardware, see the Hardware
Installation Guide.
Configuring the RS485 Port for Base Station Connection

To configure Controller port parameters for RS485 Base Station operation, proceed as follows:
1. Connect the diagnostic cable and establish communications with the Controller (see Connecting to GMS Using a
Diagnostic Cable 12 ).

5. Click the RS485 port image. The Port Protocol Parameters dialog box opens for it.
6. Click the Link Level tab, then from the Protocol list, select HDLC/SDLC. The default parameters for the
protocol display.
7. Enable the Async mode option. The parameters for asynchronous operation display. Set them as required.
8. Click the Application Level tab.
9. In the General Parameters region, enter the required message response time (default is 10 seconds) in the
Response Time to a Message field.
10. In the Port Priority list, select Primary Priority.
11. Click the Base Station tab.
12. Select the Linecard Addresses option.
13. In the Linecard A region, in the Line 1 list, select SNA Luname and enter any value in the adjacent field.
Note: Linecard address parameters reside at a network level. However, HDLC operation only requires an
address at the link level. To be consistent with other protocol configurations the Controller requires an
input of some type for HDLC in order to function correctly.
14. All parameters that display when the Parameters radio button is selected remain as default.
15. Click Download to save and apply the new settings. The Transaction Manager displays a list of messages
confirming the changes.

For more information on HDLC/SDLC protocol parameters, see Communications Protocol Parameters Reference 62 .

Configuring EMCS Connections

Controller firmware version 5.06 (for 1057/1058 Controllers) and version 1.06 (for 8001 Controllers) and later
support the Pacom .is EMCS (event management control system) application platform. This includes support for
multiple communication protocol services, data and message encryption and master key management between the
Controller and Pacom .is.
Pacom .is supports up to eight protocol services, which can be configured for redundancy and third-party reporting
etc. For initial setup, it is necessary to manually configure the Controller with the IP address of an EMCS protocol
service. All other protocol services are automatically configured by Pacom .is on connection.
Configuring Controllers for Pacom .is EMCS Connections

To configure Controller port parameters for Pacom .is EMCS protocol service connections, proceed as follows:
Note: It is also possible to configure the EMCS connection using a keypad.
2. In the Controller dialog box, select General > Network > EMCS Settings. The EMCS Parameters dialog box
opens.
3. Ensure that the screen displayed is for protocol service 1. The Device Parameters region label will show 1/8.
Use and to scroll through protocol services.
4. Enable the Address Field Valid, Use TCP, Enable Event Reporting and Enable DTP Transfers options.
These are required for successful communications and enables the automatic configuration of other protocol
services.
5. In the Encryption Type list, select the encryption type being used for message verification.
6. In the Physical Port list, select the Controller port to use for the connection. For EMCS, this is generally an
Ethernet port.
7. In the Destination UDP/TCP Port field, enter the number of the port on the protocol service machine to
connect using.
8. In the IP Address field, enter the IP address of the protocol service machine.
9. In the High Level Address field, enter the telephone number for dialling in to the protocol service machine, if
required.
Note: Leave all other settings at their default values, the EMCS will configure and optimize all settings
when it connects.
10. Click Download to load the settings into the Controller and close the dialog box. The Transaction Manager will
show the download status.
Note: If you click Close without downloading the settings, any changes will be lost.

Parameters Reference
Parameter Description
Device Parameters
Display settings for the next protocol service (protocol service number is indicated
next to Device Parameters label).
Display settings for the previous protocol service (protocol service number is
indicated next to Device Parameters label).
Address Field Valid Enable to use the connection (protocol service number is indicated next to Device
Parameters label).
Use TCP Enable to use TCP protocol for communications between the Controller and the
protocol service.
Enable Event Reporting Enable so that events are reported using the connection.
Enable DTP Transfers Enable to allow the connection to be used for large data transfers between the
Controller and EMCS.
Enable Full Data Enable to encrypt the entire contents of messages. When this option is disabled,
Encryption message security is based on an encrypted digital signature only. Full data
encryption is most secure, however, it may reduce system performance somewhat.
Alternate Router Enable to allow the Controller to use a secondary Ethernet router for sending
Subport Operation messages to the EMCS. Secondary routers are used only as backup to the main
router.
Entry is a Low Priority Enable to allow the connection to be used for reporting events of any priority.
Connection Entry Disable to restrict the connection to reporting high level events only.
Operate in Disaster Enable for the system, when reporting to a third-party due to connection failure with
Mode the EMCS, to retain events sent during the failure. When the EMCS is online again,
the events will be reported.
Encryption Type Encryption ensures that any messages which may have been altered in-between
being sent and received are identified as suspect and discarded. Click for options.
Click an option to select it:
Caution: Encryption settings for Controllers and EMCS must be identical.
None - No encryption.
HMAC - Uses a RFC 2104 compliant MD5 hash algorithm for all packet data and
encrypts the result using the session key, which is known only to the Controller
and protocol service.
AES enc mac - For future use. Uses a FIPS 113 compliant AES algorithm for all
packet data and encrypts the result using an AES 128 bit encrypted session key.
This method is considered "stronger" than HMAC.
AES hash mac - For future use. Uses a MD5 algorithm for all packet data and
encrypts the result using an AES encrypted session key. This method is considered
slightly "stronger" than HMAC.
Note: The Enable Full Data Encryption option allows you to optionally
encrypt the entire message data in addition to encrypted MAC verification.
Protocol Type The message protocol determines the structure of messages, so that sent messages
are properly interpreted by the receiving device. The protocol selected must conform
with that of the receiver. Click for options. Click an option to select it:
Note: Where possible, use Pacom format as it is more detailed than Contact
ID or SIA.
Pacom - Select to use Pacom message format.

Contact ID - Select to use Contact ID message format.
SIA Format - Select to use SIA message format.
Physical Port Represents the physical Controller port used by EMCS connections. Click to view a
list of available ports on the Controller. Click an option to select it.
Protocol Service Represents the EMCS ID number of the protocol service that the connection uses. To
Address edit, click the field and enter the ID number.
Note: Leaving the setting at 0 ignores using the EMCS ID number as part of
identifying the protocol service.

Heartbeat Type This setting determines the time window to use for Controller heartbeating. That is,
the Controller contacts the system once per period of time to maintain a status of
being online. The settings are pre-defined:
Note: Longer heartbeat durations will reduce the amount of data sent for
heartbeat polling, however, does potentially increase the time between a
Controller going offline and the system being made aware of it.
1 - Occurs randomly between five and 15 minutes since the last heartbeat.
2 - Occurs randomly between 10 and 45 minutes since the last heartbeat.
Destination UDP/TCP Represents the port number on the protocol service machine that the connection
Port uses (default = 3435). To edit, click the field and enter the port number.
Non-Important Alarms The number of non-important messages that the Controller will accumulate before
Queue before Sending connecting to the EMCS and sending them all. If an "important alarm" is activated,
to EMCS the EMCS is contacted immediately and all queued alarms are reported. To edit, click
the field and enter the number of alarms to queue.
High Level Address Represents a non-IP connection address. This is generally a telephone number for
establishing a connection using GPRS or PSTN to the EMCS. To edit, click the field
and enter the contact number.
This setting supports the following dual-tone multi-frequency (DTMF) signalling
characters, which, when used, provide the following functionality:
0 to 9 - Normal digits.
, - [comma] AT pause command [normally a one to five second pause].
W - AT wait for second dial tone command.
* - Asterisk character.
# - Hash/pound character.
The following example shows a Controller set to dial "9" for an outside line, wait for
the dial tone, pause for a short time, then dial the number "0299885566":
9W,0299885566
Note: Be aware that GMS dialup protocols currently use "*" to represent AT
pause and "+" to represent AT wait for dial tone commands.
IP Address The internet protocol (IP) address of the computer that is running the protocol
service. To edit, place cursor in the field and type in the IP address details.
Open Wait Time The length of time to wait (in seconds) after attempting to establish a connection
with the EMCS and receiving no response. After the timeout, the connection request
is dropped and a new one created.
DTP Idle Time The length of time to allow (in seconds) during data download/upload for an
interruption to data transfer. After the timeout, the data transfer is dropped and a
new one created.
Event Idle Time The length of time to wait (in seconds) after communicating with the EMCS for event
reporting, before dropping the connection. This allows the system a period of time,
after initial communication is complete, for further event reporting using the same
connection. After the timeout, the connection is dropped.
Command Idle Time The length of time to wait (in seconds) after communicating with the EMCS for
command execution, before dropping the connection. This allows the system a period
of time, after initial communication is complete, for further command execution using
the same connection. After the timeout, the connection is dropped.

Message Response The length of time to wait (in seconds) for an acknowldement (ACK) response from
Time the EMCS after sending data. After the timeout, the message is considered
unacknowledged (NACK) and will be sent again. The number of times the message is
retried using the current connection is set by No. Retries.
No. Retries Represents the number of times in the one session (connection between Controller
and EMCS) to attempt to send data to the EMCS without acknowledgement. If all
retries are used without acknowledgement, the system will use an alternative route
for connecting to the EMCS.
System ID For future use. Represents the identification number of the EMCS that the Controller
connects to, when there are multiple EMCSs being managed by the one instance of
Pacom .is..
Enable EMCS only when Enable for the Controller to communicate with the EMCS only if an attached Base
Base Station is in Station is unable to connect using its Comms and Alarm connections. If no Base
Disaster Operation Station is in use, this setting is ignored.
In order to confirm the connectivity of the Controller to the Pacom .is EMCS, check in Pacom .is if the Controller is
available. For further details refer to Pacom .is documentation.

Communications Protocol Parameters Reference

This section is a Controller port parameters reference for various protocols and includes asynchronous driver
parameters.
Supported Protocols
Aperio 48 . Logging Printer 68 .
ASCII 49 . Modbus 69 .
Async. Poll 50 . Pacom Communications Protocol (PCP) 70 .
Controller Dialup 51 . RS485 Device Loop 71 .
Elevator Interface 56 . Securitel (STU) Receiver 72 .
Enhanced Pacom Communications Protocol (EPCP) 57 . SFEP 72 .
General Carrier Message 58 . Slave RS485 Device Loop 73 .
General Purpose Driver 59 . SNA 74 .
General Purpose DVR Driver 60 . Text Pager 76 .
General PTZ/Switcher Driver 60 . Timecon TTC 77 .
Generic Fire Alarm/Securitas 62 . UDP/IP on 1051/1052 78 .
HDLC/SDLC 62 . UDP/IP on Ethernet 78 .
IEC 63 . UDP/IP on PPP 84 .
Inovonics 64 . VCS/Dialup 85 .
Iris 66 . Wyreless Application Protocol (WAP) 86 .
IRISYS Driver 67 . X.25 86 .
Asynchronous Driver Parameters

Asynchronous driver parameters are common to:
Aperio 48 . Iris 66 .
ASCII 49 . IRISYS Driver 67 .
Async. Poll 50 . Logging Printer 68 .
Controller Dialup 51 . Modbus 69 .
Elevator Interface 56 . Pacom Communications Protocol (PCP) 70 .
Enhanced Pacom Communications Protocol (EPCP) 57 . RS485 Device Loop 71 .
General Carrier Message 58 . Securitel (STU) Receiver 72 .
General Purpose Driver 59 . Slave RS485 Device Loop 73 .
General Purpose DVR Driver 60 . Text Pager 76 .
General PTZ/Switcher Driver 60 . UDP/IP on PPP 84 .
Generic Fire Alarm/Securitas 62 . VCS/Dialup 85 .
IEC 63 . Wyreless Application Protocol (WAP) 86 .
Inovonics 64 .
Baud rate Asynchronous baud rate for connection (Speed of data transfer).

No. of Data Bits Number of async data bits per byte.
Number of Stop Bits Number of stop bits used in byte (1 or 2).
Parity Parity is used to check the validity of data. An extra bit is added to the data to make
the number odd or even. If the number received by the receiving port is not of the
correct parity, the specified the data is rejected and must be sent again.
None - Parity not used.
Odd - Parity bit is set to 1 if the byte is even, to make it odd.
Even - Parity bit is set to 1 if the byte is odd, to make it even.
Space - Parity bit is always set to 1.
Mark - Parity bit is always set to 0.
Receive Buffer Size Size of receive message in multiples of 16 bytes. Range 1-255.
Maximum Idle Time The time to wait between characters before the buffer is closed and processed.
Physical Layer Type of physical protocol to use (RS232, RS422, RS485, V36 etc.) This parameter
Protocol only applies to the network pot which has a programmable communications chip. All
other ports require changes to PCB link settings to change the physical layer protocol
of the port.
Operate in the 68360's Sets the enveloping mode for 68360 microprocessor communications:
automatic enveloping RTS - Request To Send.
mode
CTS - Clear To Send.
DCD - Data Carrier Detect.
Aperio Protocol
Link Level Parameters
Asynchronous Driver See Asynchronous Driver Parameters 47 .
Offset Aperio device The number to offset the current logical Aperio device ID number by (0 - 63). This is
ID number by only required when mutliple RS485 ports are being used for Aperio devices on the
one Controller, so that each device has a unique identification number.
For example, if one RS485 port has Aperio devices 1 to 16 on it and another RS485
port has four Aperio devices on it, the offset for devices using the second port would
be "16" [or greater]. That is, the first device on the second RS485 port will have an
ID number of 17 (16 + 1).
Note: A single RS485 port is capable of addressing up to 32 Aperio devices.

A single Controller can support up to 64 Aperio devices (Controller firmware
version 1.07 or later) using several RS485 ports.
Aperio device support is limited to 8001 Controllers only.

ASCII Protocol
Message forwarding Time to wait for no character before the message is transmitted.
time
Message forwarding Character to look for to close buffer and transmit.
character
SCC reset time when Time to reset the SCC when no devices are online as a background check.
offline
Enable forwarding Select to enable character for encoding.
data on character
Enable forwarding Select to enable timer for encoding.
data on timer

Async. Poll Protocol
Note: You must enable the Enable Octal Addressing option, and the Address of Device setting must
not contain the digits 8 or 9.
Line Idle Timer The amount of time that the line can remain idle before it is marked as offline.
Response Timer The amount of time to wait for a response to a message.
Message Retry The maximum number of times that the system will attempt to unsuccessfully send a
Counter message before it is discarded and an error message is sent to the monitoring
system.
Address of the Device The address of the connected device. Displayed/entered in octal if the Enable Octal
Addressing option is enabled (see below).
SCC Reset Time When The regularity between checks to see if the port is still marked as online. If it is not,
offline then the Serial Comms Chip for this port is reset.
Enable Octal When selected, denotes that the Address of the Device setting is octal. That is,
Addressing digits eight and nine are not allowed.

Controller Dialup Protocol
Dialup Parameters / Selects between the two parameters screens.
Modem Driver
Config Parameters See Asynchronous Driver Parameters 47 .
Local Telephone The telephone number for the Controller to dial out to, including area/country codes.
Number Use the "*" and "+" characters to instruct the Controller to wait for a dial tone ("+")
as well as to pause ("*") [normally a one to five seconds]. The maximum number of
digits allowable is 20 (or 18 if pre-dial digits are being used).
The following example shows a Controller set to dial "9" for an outside line, wait for a
dial tone, then pause for a short time, then dial the number "0299885566".
Enable predial digits Enable to allow up to two digits to be added as a prefix to the Local Telephone
Number setting. This is for systems that require extra digits to get an outside line
through a PABX or similar. For example, dialing "9" before making an external call.
Predial digits Digits to dial before dialing the Local Telephone Number. To edit, click the field and
enter the digits (max. = 2 digits). If a single digit is required (for example, "9"), enter
that digit only.
Note: This setting is available only when the Enable predial digits option is
enabled.
Message response The amount of time the port will wait for an acknowledgment to a transmitted
timeout time message before it is resent.
Max num of no Not used in this release.
responses before
offline
Max num of invalid The maximum number of invalid polls from the dial card before it is marked as
polls before offline offline.
Listen-in time The maximum time (in minutes) to allow the modem to be used as a listen-in device.
When the timer expires, the Controller hangs up the call (see Using Listen-In
Operation 266 ).

Wait for dial tone time The amount of time (in multiples of 100 milliseconds) the port will wait for a dial tone
before the dial tone is declared missing.
Modem Driver Parameters
Dialup Parameters / Selects between the two parameters screens.
Modem Driver
Port Priority Selects the priority for this port and enables the Base Station display.
Modem string to use 1, 2 or Default. 1 and 2 are preset modem types. Can be changed by changing the
Modem Type setting.
Modem Type List of all modems supported. Select the type of modem used from the pull-down
menu.
Force download To reduce the amount of data transmitted, modem strings are not downloaded, as
modem string they are not expected to change frequently and there is no need to send the strings if
other parameters are changed. However, the modem strings are sent always if this
option is selected.
Pulse Dial / Tone Dial Select either pulse or tone dialling for the modem.
Time to wait for DCD Number of seconds after it has dialled that this port will wait to receive a Data
after dialing Carrier Detect signal.
Num. Rings until Number of times that the modem will allow an incoming call to ring before answering
answering incoming it. When set to 0 with the Answer on Redial option enabled, if an incoming call rings
call twice and hangs up, the Controller will answer the next incoming call (if within 60
seconds after the previous two ring call).
Note: If the Controller shares the same line as another device (for example,
a fax machine) it is recommended to set this to 0 and enable the Answer on
Redial option, so that the Controller does not answer fax calls and that the
fax doesn't answer Controller calls.
Time to wait for DCD The number of seconds the modem will wait to receive a Data Carrier Detect signal
after answering after answering an incoming call before hanging up.
Time to wait for first The number of seconds the modem will wait to receive data after answering a call,
data message before hanging up.
Time allowed between The number of seconds the modem will remain idle after receiving a message before
data messages hanging up. (Inactivity Timer)

Time between polls to The regularity at which the modem is polled. In the case of ViControlleral Access
modem ISDN T/A this is the frequency that the Controller checks to see if there is an ISDN
line connected to the T/A.
No responses before How many times the port will receive a no response to a poll from the modem before
making modem failed marking it as failed.
Time for ACK response Time waited for an acknowledgment to a transmission.
to a Tx
Time between dial Number of minutes between phone line checks. In the case of ViControlleral Access
tone tests ISDN T/A this is the frequency that the Controller will test if the FEP T/A can be
contacted.
Time between SCC The regularity between checks to see if the port is still marked as online. If it is not
resets then the Serial Comms Chip for this port is reset.
Answer on redial Enable to have the Controller answer an incoming call if the Num. Rings until
answering incoming call is set to 0 and an incoming call rings twice and hangs up,
then is called again within 60 seconds after the previous two ring call.
Application Level Parameters
Port Priority Selects the priority for this port and enables the Base Station tab.
Response time to a Time to wait (in seconds) for the application level response to a message transmission
packet . If the timer expires without acknowledgement of the message, the system considers
the message transmission as failed.
Enable network idle Allows the system to poll the network in the background as a regular check of
poll to maintain IP connectivity.
connection
Time between retries Time to wait (in seconds) after a failed message transmission before re-sending the
message. This applies to retries in a single Pacom .is EMCS connection session.
Sleep time between Time to wait (in multiples of 10 seconds) after re-sending a message for the
retries permitted number of retry times in a single Pacom .is EMCS connection session and
not receiving an acknowledgement.
Base Station Parameters

All dialup protocols display the same fields within the Port Parameters dialog box, Base Station tab. The tab contains
two screens:
Telephone Numbers.
General Parameters.
Options at the top of the dialog box toggle between the two sets of parameters.
Telephone Numbers
When connecting to other reporting systems, select the message format type from the Comms, Alarm or Disaster
lists. The available message formats are:
Pacom - Reports to a Pacom Base Station.
Contact ID - Reports to receivers that support Contact ID message format.

SIA - Reports to receivers that support SIA message format.

SMS - Reports text messages to mobile/cell phones using a GSM Modem.
Note: Contact ID, SIA and SMS formats can be used for calling a mobile/cell telephone number over PSTN
to notify of alarms (no details are provided in the call) (see Configuring a Dial-Backup Connection 31 ).
Telephone Numbers Input the first and second priority telephone numbers for communication, alarms and
disasters. * or + can be added to the beginning of the telephone numbers to pause or
to wait for a dial tone before dialling.
Comms #1 Primary communications number - used for sending less important general
communications messages to a receiver (Base Station, third-party etc). Select the
message format type from the list.
Comms #2 Secondary communications number - used for general communications messages
when connection cannot be established with Comms #1. Select the message format
type from the list.
Alarm #1 Primary alarms number - used to report alarm messages to a receiver (Base Station,
third-party etc). Select the message format type from the list.
Alarm #2 Secondary alarms number - used to report alarm messages when connection cannot
be established using the Alarm #1 telephone number. Select the message format
type from the drop down list.
Disaster #1 Used when a connection cannot be established with Comms #2, Alarm #2 and (if
programmed) a Comms and Alarm numbers on a Tertiary Priority port. Select the
message format type from the list.
Disaster #2 Used when a connection cannot be established with Disaster #1. Select the message
format type from the list.
Predial # Enter any numbers that need to be dialled prior to the phone number for the
corresponding Comms, Alarm or Disaster number.
Note: For calling a mobile/cell telephone number over PSTN to notify of

alarms (no details are provided in the call), enter "****" (see Configuring a
Dial-Backup Connection 31 ).
Postdial # Enter any numbers that need to be dialled after establishing connection with the Base
Station or third-party receiver.

General Parameters
Sleep time between Approximately how long the port will wait to re-contact the Base Station after a series
contact cycles of failed attempts +/- Contact Sleep window value.
Contact sleep window Used to create a random window around sleep time between contact cycles to avoid
all Controllers trying to re-contact the Base Station at the same time.
Contact response time How long this port will wait for a response from the Base Station before it is
considered a failed attempt.
Contact retry counter The number of times that this port will retry connecting before the next priority port
is activated. This port will wait until sleep time has expired and then attempt again.
Waiting time between The amount of time after a failed attempt before retry.
contacts
Time to wait for a The number of seconds that this port will wait for an acknowledgement of a sent
response message before sending it again.
Retry counter for The number of times that this port will attempt to re send the same message before
sending messages considering communications lost.
# Non-important The number of non-important messages that the Controller will accumulate before
alarms to activate making a dialup connection to send them all. If an "important alarm" is activated, the
dialup Base Station is contacted immediately and all queued alarms are reported (see
Include as Important Alarms in General System Parameters 93 ).
Dialup type How often a Controller dials in to the Base Station to check-in. The timings are
applicable when using Contact ID and SIA formats. If contacting a Pacom Base
Station, the timings for the specific Dialback time are set in the Base Station. Every
time the Controller contacts the Base Station, the Base Station provides the times for
the Dialup type selected:
Dialup Type-1 - 1 to 2 minutes
Dialup Type-2 - 30 to 60 minutes
Dialup Type-3 - 1 to 2 hours
Dialup Type-4 - 2 to- 4 hours
Dialup Type-8 - 10 to 12 hours.

Note: These are default Base Station time intervals, however, they can be
changed.
Dialback time A specific time when the Controller will dial in to a third-party receiver to check-in.
Random time between The Controller will randomly dial in to the Base Station up to 30 minutes before or
time specified +/- 30 after the selected time. Applicable when Dialback time is selected, and used with
mins Contact ID and SIA.
Do dial tone test at When this flag is selected the Controller will check the phone line for a dial tone each
midnight night at midnight
Multiple alarm reports Select this flag only if you are reporting to an SIA receiver that is capable of handling
capable SIA receiver multiple messages per data packet.
Apply Message Filters This flag is only used if there is no Primary Priority port programmed. Apply
Before Dialup message filter to messages before they are put in the queue to be reported to a
Pacom Base Station or a third-party receiver so that only certain messages are sent.
Create Alarm If a Controller is setup to send messages to a third-party receiver (that is, Contact ID,
messages queue for SIA etc.) users cannot view the messages stored in the network queue if they dial in
Pacom base station from a Pacom Base Station. Selecting this option creates a separate queue which
while reporting to 3rd contains all alarm messages stored in the network queue. This allows GMS users to
party receiver dial in and view the alarm messages in the queue. If a user has dialed in and an
Important Alarm occurs, the connection is disconnected immediately and a telephone
line is used to report the Important Alarm to the third-party receiver. The user will
have to manually dial in again. The Controller will store 700 alarm messages. If card
access queue is also selected it will store the last 350 alarms and 350 card access
messages.
Create Access Control If a Controller is setup to send messages to a third-party receiver (that is, Contact ID,
messages queue for SIA etc.) users cannot view the messages stored in the network queue if they dial in
Pacom base station from a Pacom Base Station. Selecting this option creates a separate queue which
while reporting to 3rd contains all card access messages stored in the network queue. This allows GMS
party receiver users to dial in and view the card access messages in the queue. If a user has dialed
in and an Important Alarm occurs, the connection is disconnected immediately and a
telephone line is used to report the Important Alarm to the third-party receiver. The
user will have to manually dial in again. The Controller will store 700 card access
messages. If alarm queue is also selected it will store the last 350 alarms and 350
card access messages.
Elevator Interface Protocol

Elevator Type Select the type of elevator connected. Supported types are Kone and Otis.
Note: Schindler is in the menu, but is not supported.
Groups (Banks) Enable the checkboxes for the number of banks that will be used.
Applies to Otis and Kone systems, with either capable of handling multiple banks of
elevators.
Note: Readers are numbered from 1 - 64. It is a requirement that the

elevator has the same number as its reader. By assigning matching reader
and elevator numbers, it is not possible to have more than one card reader in
an elevator.
Maximum levels on an Enter the number of floors that an elevator will service (max. 128).
elevator
Slow poll time Enter the number of seconds that the system will wait between polling the elevator
for its position if an elevator bank stops responding within normal polling time.
Message response Enter the time (in multiples of 100 milliseconds) for the system to wait for a response
time to a message.
Maximum retries Enter the number of times that the port attempts to send a message without getting a
before marking offline response before the marking the elevator bank as offline.
Enhanced Pacom Communications Protocol

For information regarding Link Level parameters for EPCP, see Pacom Communications Protocol 70 .

For information regarding Base Station parameters for EPCP, see Base Station Parameters for IP Networks 81 .

General Carrier Message Protocol
Poll Delay when offline Time between re-polls when port is offline.
Poll Delay during Time between polls when port is online (but no response is received.
transitions
Poll Delay when online Time between polls when port is online and receiving poll responses.
Msg resp Timeout The amount of time the port will wait for an acknowledgment to a transmitted
message before it is timed out.
Message delimit time The time period to wait for the entire message after receiving the start of the
message.
No. of No Resps Till The number of polls with no response before the port is marked as offline.
offline
No. of invalid Resps The number of times that the Controller will receive an invalid response before going
Till offline offline.
Max NAKs before The number of times a message can be Not Acknowledged before it is deleted and
delete Msg discarded.
Max Retrans before The number of times a message has no response before it is deleted and discarded.
delete Msg
Echo Time Not used in the current version.
No. of offline Polls to The port will poll this many times, then stop until it receives a poll from the connected
use device.
SCC reset time when The time period to perform a background task of re-initializing the serial comms chip.
offline

General Purpose Driver Protocol
Time Between Idle The amount of time waited while the line remains remain idle between polls.
Polls
Driver Type Select the type of interface from the drop down list.

General Purpose DVR Driver Protocol
DVR Type Select which DVR is connected to the Controller.
SSC Reset Time when The regularity between checks to see if the port is still marked as online. If it is not,
Offline then the Serial Comms Chip for this port is reset.
Time between idle This is how often the Controller will poll the DVR.
polls
Max. NAKs before The number of times a message can be "Not Acknowledged" before it is deleted and
delete discarded.
Device ID Device ID of the DVR connected.
General PTZ/Switcher Driver

The General PTZ/Switcher Driver applies to the Pacom Witness only. To configure a Witness, attach the PTZ device.

Asynchronous Driver See Asynchronous Driver Parameters 47 . Ensure that the default values are not
changed for the asynchronous driver parameters.
PTZ Type Select the type of PTZ that is connected to the Witness. The available PTZ types are:
Intercept Camera decoder (Pelco).
American Dynamics.
G3 AutoDome (Philips).
Robot Switcher (MV96e).
Video Controls Limited (VCL).
VCL Telemetry Matrix (MAXCOM8).
SSC Reset Time when The regularity between checks to see if the port is still marked as online. If it is not,
Offline then the Serial Comms Chip for this port is reset.

Generic Fire Alarm (and Securitas) Protocol
Time to wait before This is the length of time to wait for the Gent panel signal before the panel is reported
panel offline as offline.
Number of Gent Points This is the number of alarm points connected to the Gent panels.
Number of Gent This is the physical number of Gent panels in the system (the Controller only connects
Panels to one of these panels but the total number of Gent panels in the system is entered
here).
SCC reset time when The time period to perform a background task of re-initializing the serial
offline communications chip.
HDLC/SDLC Protocol

The HDLC/SDLC protocol displays the same Link Level parameters as the SNA Protocol 74 .

Port Priority Select the port priority and enable the Base Station window.
Response Time to a Enter the time to wait for the application level response to a transmitted message.
Message
Enable Pacom leased
line operation
IEC Protocol
Time to wait before The time of no response before the Controller marks the local switcher as offline.
panel offline
Response Timer The time the local switcher has to respond to the Controller after a message is sent to
it.

Max. NAKs before Maximum number of NAK responses to a message before it is deleted from the
delete queue.
Time between idle The amount of time waited while the line remains idle between polls.
polls
Start address of Address of the first camera attached to the local switcher.
camera on switcher
Number of cameras on Number of cameras attached to the local switcher.
switcher
Physical input on Address of input on the remote switcher that is used by GMS if viewing video from
remote switcher within GMS. If no remote switcher is used, enter value as 0.
physical output on Address of output of the local switcher. When set, the switcher will send data from a
local switcher camera to the output to be viewed elsewhere.
Alarm directory size Size of the Alarm Directory that is used to store alarms sent to the local switcher.
(x10)
SSC reset time when The regularity between checks to see if the port is still marked as online. If it is not,
Pan/Tilt speed Set the pan/tilt speed of the cameras on the local switcher.
Enable alarm When selected, alarms from the Alarm Directory are sent to the local switcher. The
operation switcher can then carry out operations depending on its configuration.
Note: The local switcher is connected to the Controller. The remote switcher (if used) is connected to
GMS.
Inovonics Protocol
An Inovonics device can be registered using GMS when no keypads are used in the setup.
2. In the Controller dialog box, select Commands > Inovonics. The Inovonics dialog box opens.
3. Select the Register Transmitter option from the list.

4. In the Input Number field, enter the input number on the Inovonics device.
5. Click Send. Watch the Transaction Manager to ensure an enrolment confirmation notification appears. The
Transaction Manager example below shows Controller #25 registering transmitter on input number 204.
6. To test Inovonics input, press Reset to send the input into alarm. Check that the Transaction Manager reports
the alarm.

Supervision Window This is the amount of time a transmitter has to report to the Controller before the
Controller declares the transmitter offline. This should be the worst case check-in time
as there are no individual timers. All transmitters may have different check-in times,
so to avoid having any go offline, this time must be set to the value of the longest
check-in time.
Receiver Poll Time This is the time between polls if no messages status messages are received from the
receiver.
Logical device number Actual logical number that is reported in the Online and Offline messages to the GMS.
SSC Reset Time Time to reset the SCC when no devices are online as a background check.
Application ID The value of the application when using the FA400 receiver.
To set up Inovonics wireless devices, see Configuring Inovonics Devices 158 .
General Purpose IP Parameters for Inovonics
TCP/UDP Ports; Port 1 Enter port address on the Inovonics device for communication. Select TCP or
and/or Port2 UDP from the list.
Protocol Select Inovonics.
Local Ports Select the local ports which is used to connect to network.

IP Address IP address of the Inovonics device.
Logical device number Enter the device address of the Inovonics device on the device line.
Supervised Time <x Mins> The time within which the Inovonics device should respond back. If at point it
does not respond, a alarm is reported in the Transaction Manager.
Back arrow and Next Use to traverse through configuration of connected third-party devices (max. =
arrow 6).
Iris Protocol
No of tries before The number of times that this port will attempt to establish communications with the
offline Iris reader before it is marked as offline.
SCC reset time when The time period to perform a background task of re-initializing the serial
offline communications chip.

IRISYS Driver
Enable Status This generates status messages when the counter changes. (Not implemented in this
messages release.)
People counter logical The number that is reported in Online and Offline messages.
number
People counter area (Not implemented in this release.)
number
Time between Polls Time between consecutive polls by the Controller to a Controller Area Network (CAN)
device.
Counter Type People Counter - The Controller will poll the counter devices connected and collect
the data on how many counts have been detected. The counts are kept for seven days
and have counts at 15 minute intervals. This allows a graph of counts vs time to be
generated on a third-party device. The counts are reported to the Pacom Base
Station, then reported on third-party Carrier ports, at around midnight, based on the
Controller address.
Evacuation Counter - Allows a third-party PC connected at the Base Station to send
messages to the Controller and out to the People Counter to request directly the count
of how many people are left. The value is sent then from the People Counter to the
Controller and then back to the Base Station, then on to the PC using the Third Carrier
Message Protocol.

Logging Printer Protocol
For complete details regarding the Logging Printer protocol and implementation, see the Controller SDK/ASCII
Interface Manual, available from the Pacom website.
SCC reset time when The amount of time waited after the printer has been marked as offline before the
offline SCC is reset.
Append strings with Adds a line feed to the end of each message to start each message on a new line.
line feed
Append strings with Adds a carriage return to the end of each message to start each message on a new
carriage return line.
Enable printer Poll/Ack When this flag is selected, the port will send periodic poll messages to the printer and
expect an acknowledgement, otherwise the printer is marked as offline. Only for
printers that support this flag.
Enable printer when When this flag is selected, the printer port will only be enabled when the primary
network fail communications to the GMS has been lost.
Filter access control Selection of this flag prevents access control messages from being sent to the
messages printer/host.
Filter man number Selection of this flag will prevent alarm user ID messages from being sent to the
messages printer/host.
Filter Controller status Selection of this flag prevents Controller status messages from being sent to the
Messages printer/host.
Filter internal alarms Selection of this flag prevents alarms relating to the internal operation of the
and resets. Controller and their corresponding reset messages from being sent to the printer/
host.
Filter external alarms Selection of this flag prevents alarms relating to external alarm points etc. of the
and resets Controller and their corresponding reset messages from being sent to the printer/
host.
Use condensed Sends a condensed message format to the printer/host, instead of the complete
message format message format.
Command supported Sets the type of commands a Controller accepts.

Modbus Protocol
Transmission Mode Two methods of transmission are available - Controller or ASCII. Controller sends
the data in 8-bit binary format, and ASCII sends the data in ASCII format, which is
helpful for lines supporting 7-bit data transfer. Ensure that the mode ends of the
transmission line are identical.
Bus Interface Mode Modbus is a single-master/multi-slave poll-response system with the Controller always
acting as a master. This is the default mode. Selecting Listen Mode prevents the
Controller from sending polls, and instead relies on another master on the line to poll.
Device Poll Rate This is how often (in multiples of either one second or 0.1 second) each input is polled
for data. Min. = 0, max. = 127 (12.7 seconds). Select the time value using the
adjacent options:
Second - Select so that the Device Poll Rate value is calculated in full seconds.
For example, a poll rate of "5" and this option selected equates to a poll rate of five
seconds.
1/10 Second - Select so that the Device Poll Rate value is calculated in tenths of
a second. For example, a poll rate of "5" and this option selected equates to a poll
rate of 0.5 seconds.
Note: If Listen Mode is selected, this field is ignored, as the Controller is not
the Modbus bus master.
Device Response The time (in seconds) that the Controller will wait after issuing a Modbus request for
Timeout the slave to reply before declaring a timeout. Min. = 0, max. = 255.

Pacom Communications Protocol
Protocol Selects which communications protocol is used by this port. The system will not allow
selection of a protocol that the selected port does not support.
Poll Delay when offline Time between re-polls when port is offline.
Poll Delay during Time between polls when port is online (but no response is received).
transitions
Poll Delay when online Time between polls when port is online and receiving poll responses.
Msg resp Timeout The amount of time the port will wait for an acknowledgment to a transmitted
Time message before it is timed out.
Receive Char Timeout The time period to wait for the entire message after receiving the start of the
Time message.
No. of No Resps Till The number of polls with no response before the port is marked as offline.
offline
No. of invalid Resps The number of polls without a valid response before the port is marked as offline.
Till offline
Max NAKs before The number of times a message can be Not Acknowledged before it is deleted and
delete Msg discarded.
Max Retrans before The number of times a message has no response before it is deleted and discarded.
delete Msg
Echo Timer Not used in the current version.
No. of offline Polls to The port will poll this many times then stop, until it receives a poll from the connected
use device.
SCC reset time when The time period to perform a background task of re-initializing the serial comms chip.
offline

For information regarding Base Station parameters for PCP, see Base Station Parameters for IP Networks 81 .

RS485 Device Loop
Start of the device Specifies the range of device addresses connected to this loop in multiples of 32.
address range
Poll all devices delay Time to poll devices. If set as Master/Slave, slave starts polling devices if it stops
detecting polling from the master.
Poll cycles before Poll cycle retries before the device is marked as offline.
offline
Wait time for response Time to wait for a response to a message sent to a device.
Number of no response Number of retries to send message before the device is marked as offline.
till offline.
Transmit delay when Number of characters/times to wait to send message when Tx is enabled and port is
not in Cont. not in contention.
Transmit delay when Number of characters/times to wait to send message when Tx is enabled and port is
in Contention in contention.
offline
Loop Operation None - Normal device loop operation
Enable slave - Makes this port a slave ring port.
Enable master - Makes this port a master ring port. This allows the device loop to
be wired from the master ring port through all devices then to a slave ring port.
Should the ring be broken, both master and slave ring ports will communicate with all
devices still remaining on their section of loop.

Securitel (STU) Receiver
Receiver Offline Time The monitoring company hardware polls the Controller. This is the time that the
Controller must receive a poll within before assuming it is offline.
Hard ID Update Time This is how often the Controller will send the Account ID to the monitoring center.
STU Account ID Number that is provided by the monitoring center to identify the Controller/site that is
reporting.
SSC Reset Time Time to reset the SCC when no devices are online, as a background check.
STU Receiver Type Select the type of receiver that is used by the monitoring center.
SFEP Protocol
The SFEP protocol displays the same parameters as the SNA Protocol 74 .

Slave RS485 Device Loop Protocol
Retry count before The number of times that a message is sent unsuccessfully before the Controller will
Baudrate change change baud rate and try again.
Contention Time The Controller will wait this long (x 10 ms) before attempting to re-send a message
when the device line is busy.
Wait Time for The amount of time waited for a response to a message.
response
Time without poll from The amount of time that the Controller will wait without receiving a poll form the
BAU master device (Branch Alarm Unit) on the RS485 line before changing baud rate.
Encryption Enabled Enable encryption (1) or disable encryption (0).
Transmitter time out If outgoing data is not detected during a transmission, the transmitter is reset after
to reset Tx waiting this amount of time.
Transmit Delay when The amount of time waited when switching from receive to transmit when the data
not in Cont. line is not being used.
Transmit Delay when The amount of time waited when switching from receive to transmit when the data
in Contention line is being used.

SNA Protocol
Acync Mode This flag enables this port to operate HDLC without synchronization. Selection will
enable the Asynchronous HDLC Driver Parameters.
Encoding Type Type of encoding (NRZ or NRZI).
HDLC/SDLC Address Link level address (in hex).
Receive Buff. Size Size of receive message in multiples of 16 bytes. This is the largest message that is
expected to be received on the link, including Address Control and FCS.
Baud rate If the clock is supplied by a Controller, select the baud rate here.
Physical Layer Type of physical protocol to use (RS232 etc.).
Protocol
Operate in the 68360's Sets the enveloping mode for the 68360 chips communications. RTS-Request To Send
Automatic enveloping CTS-Clear To Send DCD-Data Carrier Detect.
mode
Operating Mode Set the mode of operation. Options are:
DCE Point to Point - Used for X25 LAPB operating as DCE mode.
DTE Point to Point - Used for X25 LAPB operating as DTE mode.
DCE Multidrop - Used for FEP SNA mode.
DTE Multidrop - Used for SNA PU2.1.
T1 Timer Low Byte The time the Controller will wait for a message from a Front End Processor (FEP). If
the port is in active state and no message is received, the port will disconnect and
enter a down state, and will require manual initialization.
T3 Timer Low Byte (Not implemented).
Time Between FEP/ Time between FEP/X25 Poll when operating in DCE mode.
X25 Poll
No response till link The number of times a message is sent without a response before the link level is
level fail considered to have failed.
Window Size Window size for frames (module 8 is default).
Extended Sequence Enables module 8 sequencing.
Numbering
Num. Slow Poll SNRM Used for DCE multidrop mode to poll offline devices.
cycles

Time to Reset SCC Time to reset SCC as a background check.
Line Identifier ASCII line name.
Block Num for SNA Block/ID number for XID frames.
Session Level Parameters
Response Time The time to wait for a definite response to Iframes.
Max. Retransmission This is the maximum number of retransmissions before a session fail.
Attempts
ASCII LU name Our LU name in ASCII.
ASCII control prog Our control program name in ASCII.
name
ASCII local network ID Our local network identifier in ASCII.
Definite Response The flag selected for definite response to Iframes, not selected for exception
response.
Two sessions needed A session created using SNA protocol transmits data in one direction only. By
for bidirect. Operation selecting this option, two sessions are created in parallel. One session is used to
transmit data, and the other session is used to receive data.
Enable ActPU When enabled, the Controller will not wait for an "ActPU" message (it will assume PU
Suppresion is activated), and will continue through the boot-up process.
Pacing Window Size Set to non zero to enable session level pacing.
Max Wait Time for Bind Enter the time to wait for response to the above message.
Resp

Response time to an
Enter the time to wait for the application level response to a transmitted message.
FMD
Text Pager Protocol
Pager number This string precedes the alarm message.
Buzzer Type Type of buzzer character.
Time between sending Time to wait between sending messages.
Messages
offline

Append strings with Selection of this flag adds line feed to the end of all messages.
line feed
Append strings with Selection of this flag adds carriage return to the end of all messages.
carriage return
Filter access control Selection of this flag means access control messages will not be printed.
messages
Filter man number Selection of this flag means man number messages will not be printed.
messages
Filter Controller status Selection of this flag means Controller status messages will not be printed.
messages
Filter internal alarms Selection of this flag means internal alarms and resets messages will not be printed.
and resets
Filter external alarms Selection of this flag means external alarms and resets messages will not be printed.
and resets
Timecon TTC
Number of Message The number of times to send the same message without receiving a response before
Retries a session fail.
Device Response This is the time (in multiples of 100 milliseconds) to wait for a response to a message
Timeout before re-sending the message.
Host IP Address The IP address of the connected Timecon device.
Connected To Select if the connected Timecon device is a TTC or a Timecon server.

UDP/IP on 1051/1052

The UDP/IP on 1051/1052 protocol displays the same LAN MAC Level parameters as the UDP/IP on Ethernet 78
protocol.
Driver Parameters
The UDP/IP on 1051/1052 protocol displays the same 1051/1052 Driver parameters as Link Level parameters as the
Pacom Communications Protocol 70 .

The UDP/IP on 1051/1052 protocol displays the same Session Level parameters as the UDP/IP on Ethernet 78
protocol.

The UDP/IP on 1051/1052 protocol displays the same Application Level parameters as the UDP/IP on Ethernet 78
protocol.
UDP/IP on Ethernet Protocol

Link Level Two parameter sets comprise the Port Parameters dialog box, Link Level tab for UPD/IP over Ethernet:
LAN MAC Level Parameters.
Internal Ethernet Driver Parameters.
Link (LAN MAC) Level Parameters
SAP to Use for LLC LLC2 service access port number to use.
Level
Window Size <1-127> LLC2 extended window size.

T1 message ACK time Time to wait for a response to an LLC2 frame.
limit
N2 message retry Time to retry sending an Iframe on LLC2
count
SABME polling Time between sending SABME requests to offline SAPs in LLC2.
frequency
RR Polling frequency Time between LLC2 and Receiver Ready poll cycled.
SABME sending Enable sending SABME commands from our node to disconnect SAP.
enabled
Sending of RARP Enables reverse address resolution protocol used with RARP sever on LAN.
messages
Sending of IP filters to Used with 1051/1052/1053 devices to allow filtering of IP messages within the
105x 1051/1052/1053 to minimize serial traffic. Only receive messages to our IP address.
LLC test frame sending Enable sending of LLC test frames when route is not determined.
Token Ring source Enables token ring source routing option.
routing
IEEE 802.3 (or DIX) Enable Ethernet type messages (802.3 or DIX) framing.
framing
Token Ring Speed Selects between 4MHz and 16MHz token ring.
MAC Address Enable local MAC address programming. Used to select and alternate MAC address.
Parameter Enabled
LLC Test Message timer Time between sending of LLC test frames.
Local MAC Address Used in conjunction with Use of MAC Address parameter (above) to program the
alternate address. When not in use, will show the burned-in MAC Address.
Internal Ethernet Driver Parameters
LAN MAC Level Enables the LAN MAC Level parameter options.
Internal Ethernet Enables the Internal Ethernet Driver parameter options.
Driver
LAN MAC Level Displayed when LAN MAC Level option is selected.
Internal Ethernet Displayed when the Internal Ethernet Driver option is selected.
Driver
Persistence This parameter allows the driver to be less aggressive in its attempts to re-send data
following a collision. Should normally be set to 0 but can be set from 1 to 9, 9 being
the least aggressive.
Enable SQE Used to increase signal transmission reliability over long distances.
Enable full duplex Enables full two-way communication, that is, Rx during Tx or vice-versa.
operation
Enable link heartbeat Enables the sending of heartbeat pulses in the absence of data to confirm connection
pulses over the link.
Operate in Enables this port to read all data on ethernet, not only that data which has been
promiscuous Mode addressed to it. Used for re-routing.

UDP port to send data This is the UDP port number for UDP messages. The default used by Pacom is
to "2800".
IP time to live count How many hops the IP data message will pass before being discarded.
IP Address of local Controller IP address.
node
Subnet mask Controller subnet mask.
IP Address of router IP address of gateway router 1.
IP Address of another IP address of gateway router 2 (where applicable).
router
Response time to a Time to wait for an IP/UDP data message to be sent to the LAN.
message
Max retrans attempts The number of retries to send UDP/IP data message to the LAN if there is no
for message response before discarding the message from the current session.
Time for pinging Time between pings to an IP address in the cache table. Used to verify that a remote
device is still active. Default = 0.
Note: For Controllers that reside behind a firewall, pinging may not be
possible.
Time for pinging Time to wait for a response to a ping request from a remote node.
response
Retry count for pinging How many times to retry pings to remote before the remote is marked as failed.
Time for router ping Time between pings to the router.
Time for router Time to wait for a response to a ping to one of the two routers.
response
Retry count for router How many times to retry pings to remote before the router is marked as failed.
ping
Disable SNMP The Controller can respond to SNMP messages over the network. if ticked, then the
Management Controller will not respond to any SNMP messages. By default SNMP is enabled.
Enable DHCP Get the IP address, the subnet, and the Router IP address from a DHCP server on
the network. When enabled, the IP Address, Subnet Mask, IP of Router, and IP
for another Router fields are disabled. The addresses displayed in these fields will
be those allocated by the DHCP server. If not allocated yet, "0.0.0.0" is displayed.

If the Controller connects to a CCU or TransIT, the Controller should be added in into
the CCU/TransIT with an IP Address of 0.0.0.0.
Note: The Controller will not attempt to connect to the Base Station until at
least the local IP address has been received. If the Controller requires a
router to connect to the Base Station, it will not try to connect until the
router IP address is also obtained.
Port priority Selects the priority for this port and enables the Base Station tab.
Response time to a Time to wait (in seconds) for the application level response to a message transmission
packet . If the timer expires without acknowledgement of the message, the system considers
the message transmission as failed.
Enable network idle Allows the system to poll the network in the background as a regular check of
poll to maintain IP connectivity.
connection
Time between retries Time to wait (in seconds) after a failed message transmission before re-sending the
message. This applies to retries in a single Pacom .is EMCS connection session.
Sleep time between Time to wait (in multiples of 10 seconds) after re-sending a message for the
retries permitted number of retry times in a single Pacom .is EMCS connection session and
not receiving an acknowledgement.

All network protocols display the same fields within the Port Parameters dialog box, Base Station tab. The tab
contains two sets of parameters:
Linecard Addresses.
Base Station Parameters.
Options at the top of the dialog box toggle between the two sets of parameters.
Linecard Addresses
This screen is used to enter the address and phone number of the line cards (in the Base Station) to which the
Controller will report. You can program up to three line cards with up to two alternate address/phone numbers each.

Linecard Addresses Provides selection of the protocol for line card communication. Selection of a protocol
enables the address field for the line cards.
Linecard A - Line 1 Enter the address of Line 1 of Linecard A.
Linecard A - Line 2 Used if Linecard A Line 1 fails. Enter the address of Line 2 of Linecard A.
Linecard B - Line 1 Used if Linecard A Line 2 fails. Enter the address of Line 1 of Linecard B.
Linecard B - Line 2 Used if Linecard B Line 1 fails. Enter the address of Line 2 of Linecard B.
Backup Linecard A - Used if Linecard B Line 2 fails. Enter the address of Line 2 of Backup Linecard A.
Line 1
Backup Linecard A - Used if Backup Linecard A Line 1 fails. Enter the address of Line 2 of Backup
Line 2 Linecard A.
SNA Network ID Appropriate field are enabled by selecting SNA LU name from the related Linecard
Addresses list. It allows the linecards network ID to be specified.
Note: For more information regarding linecard addressing and protocols, see the CCU/TransIT
Configuration Guides.
General Parameters

Secondary activate Specifies the length of time the Controller waits for the network to respond, after
timer which it declares lost network communications. It will then attempt to connect using
the secondary port.
Tertiary activate Specifies the length of time the Controller waits after it has lost network
Timer communications, including all retries and timeouts associated with recovering
primary/secondary communications, before attempting to connect using the tertiary
port.
Sleep time between The approximate length of time the port waits to re-contact the Base Station following
contact cycles a series of failed attempts the Contact Sleep window setting.
Contact sleep window The amount of approximation for sleep time between contact cycles to avoid all
Controllers trying to re-contact the Base Station at the same time.
Contact response time The length of time the port waits for a response from the Base Station before the
attempt is considered to have failed.
Contact retry counter The number of times the port attempts to connect before the next priority port is
activated. The port waits until the specified sleep time expires before attempting
again.
Waiting time between The length of time, following a failed attempt, before retry.
contacts
Time to wait for a The number of seconds that this port will wait for an acknowledgement of a sent
response message before sending it again.
Retry counter for The number of times the port attempts to re-send the same message before
sending messages communication is considered lost.
Waiting time for new The time that the Controller will wait for a heartbeat from the Base Station after a
heartbeat. successful call establishment, before clearing the call and trying again.
It is also the time that the Controller will wait for a new heartbeat from the Base
Station during a heartbeat exchange. After a call, the Controller expects a first
heartbeat from the Base Station. The Controller will then store the heartbeat and
when the timer within the heartbeat expires, the Controller will send a heartbeat
response to the Base Station. It then starts this timer and waits for a new heartbeat
from the Base Station.
If it receives a new heartbeat, the process continues. If heartbeat is not received, the
Controller will re-send the heartbeat response X number of times where X is the value
specified in Retry Counter for Sending Messages. If there is still no response, the
Controller will drop the connection and try to re-establish.
Queue Non Important Forces all non-important alarms in to queue, until an "important alarm" is activated,
Alarms at which time all queued alarms report (see Include as Important Alarms in
General System Parameters 93 ).
Use TCP for Base Forces all linecard messages to be sent using TCP/IP instead of UDP/IP.
Station connection
Enable Rijndael MAC Rijndael is a high-security method of message authentication used to encrypt
messages between a Base Station and Controller.
Rijndael Data Different methods are available for encrypting data between a Base Stations and
Encryption Controllers. Currently, only Method 1 is supported. Methods 2 and 3 are for future
use.
Note: To comply with NIST AES(FIPS) 197, select Enable Rijndael MAC, and select Method 1 under
Rijndael Encryption.

UDP/IP on PPP
LCP ping/rsp timer Link control protocol (LCP) ping timer. This is the timer used to send LCP ping
requests to the router.
LCP ping retry Retry count of ping or LCP messages before LCP level re-initializes.
Data idle timeout The time to remain idle (in multiples of 10 seconds) after the last piece of data is
exchanged, in case of further data, before ending the session.
SCC Reset time when Time to reset SCC as a background check, when LCP fails.
offline
Modem string to use 1,2 or default.1&2 are preset modem types. Can be changed simply by changing
modem types.
Modem Type List of all modems supported. Select the type of modem used from the pull-down
menu.
Force Download To reduce the amount of data transmitted, modem strings are not downloaded, as
Modem string they are not expected to change frequently and there is no need to send the strings if
other parameters are changed. However, the modem strings are sent always if this
option is selected.
Enable LCP Echo Enables LCP echo message to the router during no traffic periods to maintain link
integrity.
Enable PAP Select if Password Authentication Protocol (PAP) is used for authentication.
Authentication
Enable CHAP Select if Challenge-Handshake Authentication Protocol (PAP) is used for
Authentication authentication.
PAP User Name Enter the user name required for authentication.
PAP Password Enter the password required for authentication.


The UDP/IP protocol on PPP displays the same Session Level parameters as those used for the UDP/IP on Ethernet 78
protocol.

The UDP/IP protocol on PPP displays the same Application Level parameters as those used for the UDP/IP on Ethernet
78 protocol.
VCS/Dialup Protocol

For details regarding VCS/Dialup protocol parameters, see Controller Dialup Protocol 51 .
Offline timer Timer for any incoming messages. If no incoming messages are received, the VCS
video controller is reported as offline.
Response Time to a Time that a VCS controller has to respond before the Controller re-transmits the
Message message.
Max retrans before Number of times a message is re-transmitted before it is deleted from the messages
delete message queue.
Poll time How often the Controller will poll the VCS controller.
ISDN number to call The number the Controller will dial.
2B ISDN Tick the checkbox if two channel ISDN is used. Leave unchecked if single channel
ISDN is used.
Start address of Address at which to start the transmission of the camera. If six cameras are
camera on switcher connected (addresses 1 to 6), and the address is set to 4, then only cameras 4, 5 and
6 are transmitted over the ISDN network to the Base Station.
Number of cameras on The total number of camera connected to the VCS switcher.
switcher
Physical input on (Not implemented in this release.)
remote switcher
Physical output on (Not implemented in this release.)
local switcher

Wyreless Access Protocol (WAP)
Asynchronous Driver See Asynchronous Driver Parameters 47 . Ensure that the default values are not
changed for the asynchronous driver parameters.
Address Range The range in which the Wyreless products are addressed. Set up the addressing of
the Wyreless products using the supplied software prior to setting up port
parameters.
Poll Period This is how often a Controller will poll the Wyreless Access Point Module (WAPM).
Device Response Period for which the Controller will wait after issuing a poll reply before declaring a
Timeout timeout.
For more information on configuring the WAP modules, see Selecting Reader Types and Functionality 205 .
X.25 Protocol

The X.25 protocol displays the same Link Level parameters as the SNA Protocol 74 .

Num of PVCs assigned Number of Permanent Virtual Circuits to be used.
Num Incoming only Number of channels to be used for incoming calls only.
channels
Channel num of lowest This is the start number of 2-way channels to be used. It is linked to the number of
2-way channel 2-way channels to be used (below).
Num of 2-way channels The number of channels to be used for 2-way communication.
Channel num of lowest Lowest outgoing channel to be used.
outgoing only
Number of outgoing The number of outgoing only channels.
channels
DTE reject supervisory DTE reject supervisory packets supported.
packets
Packet Size Size of the largest packet in bytes.
Extended sequence Extended sequence numbering selected.
numbering
Packet level DCE Packet level DCE operation selected.
operation
Use delivery Use of delivery confirmation (D bit) selected.
confirmation
Window Size Packet window size.
Session (dis)connect Enables session (dis)connect alarm reporting.
alarm reporting
T20 restart time limit The X25 T20 restart confirmation time limit. Measured in multiples of ten seconds up
to 255.
T21 call confirmation The X25 T21 call confirmation time limit. Measured in multiples of ten seconds up to
time limit 255.
T21 reset confirmation The X25 T22 reset confirmation time limit. Measured in multiples of ten seconds up
time limit to 255.
Data response time The maximum response time waiting for either an information packet or a
supervisory packet acknowledging a transmitted data packet. Measured in multiples
of ten seconds up to 255.
Interrupt response time The maximum response time waiting for an interrupt acknowledge packet. Measured
in multiples of ten seconds up to 255.

Addr. Of local node The eight byte X25 address of the local node in packed BCD terminated by a nibble
of "F" hex (unless all 16 digits are present). If defined, it is transmitted in all call
setup packets.
Port Priority Selects the priority for this port and enables the Base Station tab.
Response time to a Time to wait for the application level response to a message transmitted.
packet

Contact ID and Basic Signal Protocol Templates

GMS converts native Contact ID, Basic Signal Protocol and Modem II/III protocol messages from digital receivers and
other third-party devices into native Pacom1000 message format using a built-in conversion list. This is the default
behavior, however, GMS also supports editable templates to replace or add to the default conversion list.
Caution: Editing of templates should be performed by a suitably qualified or experienced person.
Message conversion is data-driven, using up to two templates to define the conversions for each type of message.
Template files are stored in the GMS\Customer\NonOverwrite folder and are named "Tmplxxxx.cid", where "xxxx" is
the template identification number.
Multiple template files can exist and messages from any given device can be assigned specific templates, by template
identification number, and a site (Controller) number in the SiaRtu.idx file, located in the GMS\Customer folder. Each
device listed in the file may have a default template and a primary template. If no default template is specified, the
built-in conversion list is used. Entries in primary templates, where specified, over-ride default template entries (or
built-in conversion list). This allows a common default template to be used for multiple devices, with specific
differences listed in primary templates. Primary templates may also include entries that specifically disable conversion
for the same entries in the default template. This is done by setting the "function code" to "0" in primary template
entries.
Note: Template files can be refreshed in GMS at any time by restarting GMS (4.00 onwards).
Editing Templates
A template file consists of a number of data lines of comma-separated parameter values. Each data line represents a
single message conversion with 12 separate integer parameter values and may be followed by arbitrary descriptive
text. Comment lines must be prefixed with a semicolon (";"). The following refers to Contact ID, with additional
information for Basic Signal Protocol and Modem II/III protocol noted. The format of a data line is:
evCode,grpMin,grpMax,zoneMin,zoneMax,fcAlm,fcRes,area,e1,e2,e3,exData2
where:
"evCode" is the Contact ID event code.
Note: For Basic Signal Protocol or Modem II/III protocol, it is the ASCII decimal value of the event code
character. For example, "68" for "D" or "83" for "S". If there are two event code characters, then the
ASCII decimal value of the first is multiplied by 1000 and the second is added to it. For example, "68083"
for "DS".
"grpMin" is the minimum Contact ID group field value.
Note: For Basic Signal Protocol or Modem II/III protocol, the group values are for the area, with valid
values being in the range "1" to "15" or "0" if no area is specified. For messages that have a non-decimal
character as the first character of the field (for example, "A Dxx"), the group values include the ASCII
decimal value of that character multiplied by 1000 plus any area value. For example, for "A4Dxx" the
group value would be "68004" ("68" for "D" x 1000 + 4). The group range in the template file to match
this may be "68001,68015". In this case, the two "xx" characters only form the zone value.
"grpMax" is the maximum Contact ID group field value. For Basic Signal Protocol or Modem II/III protocol, see "
grpMin".
"zoneMin" is the minimum Contact ID zone field value.
Note: For Basic Signal Protocol or Modem II/III protocol, the first of the three zone value characters must
be either decimal or a space, otherwise it is treated as a "special character". If either of the last two
characters are ASCII hex ("A" to "F"), the value is read as a hexadecimal, otherwise as a decimal. For
example, "123" is decimal; "12F" and "1D2" are hexadecimal; "D12" is special character "D" with zone
"12", and "DFF" is special character "D" with zone "FF" (255 decimal). This may result in conflicts, for
example, "015" and "00F" both meaning zone 15, however, it is assumed that any device using a
particular template will not send both types of messages. A zone value must have at least two characters,
where the first may be "0".
Zone values that have a single character in the third position are treated as "special characters" rather
than zone numbers, even if the character is a decimal or hexadecimal digit. For example, "R 5" is not the
same as "R 05" and "T D" is not the same as "T 0D" (the latter being the same as "T 13"). For these
characters, the fields are the ASCII decimal value of the character multiplied by 1000, for example
"68000,68000" for "D". It is possible to specify a range, for example, "68000,70000" for "D" to "F",
however, it is not possible to use that value in any Pacom1000 message field, as the maximum that can be
subtracted is 9999.
"zoneMax" is the maximum Contact ID zone field value. For Basic Signal Protocol or Modem II/III protocol, see "
zoneMin".

"fcAlm" is the Pacom1000 function code for the alarm condition.

"fcRes" is the Pacom1000 function code for the restore condition.
"area" is the area number.
"e1 "is the first Pacom1000 alarm field value.
"e2" is the second Pacom1000 alarm field value.
"e3" is the third Pacom1000 alarm field value.
"exData2" is the second extra data byte (the first is always the area number if present).
When GMS searches template entries to convert a message:
The event code must match exactly.
The group value must be within the minimum and maximum values.
The special Basic Signal Protocol characters in group and zone fields must match exactly.
The zone value must be within the minimum and maximum values (where it is not a special character).
Once a match is found, the rest of the values are used to create the Pacom1000 message.
Note: All values are signed decimal integers that are ultimately limited by either the size of the Contact ID
or Basic Signal Protocol field they come from or the size of the Pacom1000 field they fit in to.
Open the SiaRtu.idx file using a text editor, such as Notepad. To assign conversion templates, each entry should start
with:
Assigning Templates in the SiaRtu.idx File

Open the SiaRtu.idx file using a text editor, such as Notepad. To assign conversion templates, each entry should start
with:
Tp&d
where:
"T" represents a template file reference.
"p" is the primary template identification number.
"&" is the ampersand character.
"d" is the default template number.
To specify a primary template only and allow the built-in conversion list to be the default, omit the "d" value as
follows:
Tp&
To specify a default template only, omit the "p" value and the "&" as follows:
Td
For example, using an sample entry of "07003,55,0/0", the following template specifications are valid:
"T1,07003,55,0/0" - Where Tmpl0001.cid is the default and only template file.
"T2&5,07003,55,0/0" - Where Tmpl0002.cid is the primary template file and Tmpl0005.cid is the default
template file.
"T99&,07003,55,0/0" - Where Tmpl0099.cid is the primary template file, defaulting to the built-in conversion
list.
"07003,55,0/0" - Where the built-in conversion list only is used.
Any number of template files can exist, each with any number of entries. A receiver can be specify at most two. The
total amount of data is only limited by the available memory.
If present, this field must be separated from the next by a comma (",").

Configuring the Controller Timezone

Controllers require time settings to cater for daylight savings and geographical location. These are known as
timezones. The notion of time is referenced from UTC (Co-ordinated Universal Time and also known as GMT), with
your local time being UTC ± your regional time offset.
For example, London, England is at UTC and Sydney, Australia is at UTC +10 hours. A Controller in Australia that is
part of a GMS system located in the UK will operate several hours ahead (in its local time) of the main UK system (in
its local time). GMS provides the flexibility to work in local time, however, all system database entries are recorded
using UTC time.
You must set the timezone correctly, particularly in installations that span multiple geographical locations that operate
at different time. Accurate time keeping is essential to monitoring, synchronizing and reacting to events in all aspects
of security operation.
Selecting a Timezone
To configure the timezones, proceed as follows:
2. In the Controller dialog box, select Commands > Controller Commands > Set Controller Timezones. The
Controller Timezone dialog box opens.
3. In the Select Timezone list, select the local timezone that the Controller operates in.
4. Click OK to apply the timezone and close the dialog box. The timezone setting is downloaded to the Controller.
Note: The available timezones will depend on the timezones set up in the Controller. The Controller comes
with a default selection, however, you can add or edit timezones as needed (see Editing and Adding
Timezones 91 ).
You can also see the entire range of available timezones. To do this, in GMS, select Tools > Timezones.
The Configure Timezones dialog box opens, where you can see all available timezones. You cannot edit or
add timezones in this dialog box.
Finding Out the Current Controller Timezone

To find out which timezone is currently being used by the Controller, proceed as follows:
2. In the Controller dialog box, select Commands > Controller Commands > Get Controller Timezones. The
Controller Timezone Data dialog box opens, which shows you the current timezone settings.
Editing and Adding Timezones

Timezone information is stored in a text file in the GMS directory. To edit the Time Zone file, proceed as follows:
1. In GMS, select Tools > System Files > Edit System Files. The Edit System Files dialog box opens.
2. In the File Selection list, select RTU Time Zone Data and click OK. The GMS text editor opens with the "RTU
Time Zone Data" file loaded.
3. Add or edit the timezones as required. Add a new timezone entries on new lines, with a new identifier.
4. Click Save to save the file. Use the text editor controls to select another file, copy and paste, etc.

Configuring TAPI (Telephony) Devices

Many GMS operations, such as operator response actions, require telephony for communications. Telephony in
Windows uses TAPI devices, which can be modems, mobile/cell phones, Skype, etc.
GMS supports up to two simultaneous telephone connections, using two separate TAPI devices. The TAPI connections
are configured on the GMS server, not workstations.
Configuring TAPI Devices for Telephony

To configure GMS to use TAPI devices, proceed as follows:
1. In GMS, select Hardware > Dial Connect. The Dial dialog box opens.
2. In the TAPI Line list, select the modem (or other TAPI device) that is attached to the PC running GMS.
Note: Only TAPI devices that have been registered with Windows and are functional with GMS are
displayed. The TAPI device must support voice transmission.
For modems that require a password to establish full communications, you can delay when GMS attempts
to use the connection, in order to provide time for the password request to be received, displayed to the
operator and responded to. Do this by entering a value (0 - 300 seconds) in the Password Delay field.
This prevents GMS attempting to use the connection straight away and likely losing the call because either
the password was never received correctly by the modem or GMS did not receive an appropriate response.
3. For modems, click Configure Line. The selected modem configuration options are displayed in a dialog box.
Configure the modem according to the modem documentation.
4. Click Use for Voice Line 1 to use the selected device for line 1 communication, or Use for Voice Line 2 for
line 2 communications.
5. Click Close.
If you need to use a prefix before dialling out through a PABX, you can use the TAPI.INI file to set it, as follows:
1. In GMS, open the TAPI.INI file for editing (see Editing System Data Files) and add the following lines:
[GMS TAPI]
DialPrefix=xx
Where xx is the dial prefix number.
2. Save the file.
3. Restart GMS.

Advanced Configuration Options

GMS offers a number of "advanced" configuration options for Controllers. You can access these from several areas
within GMS for quick access when you are performing similar tasks. For example, click Advanced in the Port
Parameters dialog box, then select the required option from the menu.
General System Parameters
Note: The Settings for Port, Port Priority and Route to Port settings are provided as a convenience,
where you can set multiple ports and priorities from the one dialog box. The other settings (shown below)
are system wide settings and are not associated with any specific port.
Settings for Port Select a port to apply the parameters to.

Port Priority Sets a port priority for the port selected in the Settings for Port list.
Route to Port Used for Controller message routing. Controller connection is set up between
the port selected in Settings for Port and the port selected here.
Normal point offset Select to apply the ID number offset (Offset field) to reader ID numbers.
reporting
CCTV only offset reporting Select to apply the ID number offset (Offset field) to CCTV camera ID
numbers.
Offset Enter the number (in multiples of 64) for the Controller (site) to report card
reader or CCTV camera ID numbers as. This allows GMS to receive data from
numerous Controllers (sites) and to use unique ID numbers for all of them. For
example, if five sites are being monitored, set this field to 5. Thus, if CCTV
camera 10 is reporting from the third site, it will report the ID as 138 (64 + 64
+ 10). If the offset is not used, CCTV camera 10 will be reported as is and
could be confused with which site it is associated with.
Holiday Profile <0-8> The Holiday profile that the Controller will apply. Holiday profiles represent
regions. You set up differing holiday profiles to represent regions in the system
that have differing holidays. For example, in a multi-region installation where
sites in one country (country A) do not observe a holiday that sites in another
country (country B) do, you would have two holiday profiles - one for country A
Controllers and one for country B Controllers. A Controller can accept a single
holiday profile. Holiday profiles are applied from the Yearly Calendar (see
Configuring GMS - Administrator Guide, Configuring Holidays in the Yearly
Calendar).

Battery AH Rating Capacity of the Controller backup battery. If more than one battery is used and
connected in series, enter the capacity of one of the batteries. If connected in
parallel, then enter the total combined capacity of all batteries. This affects
Pacom Controllers 1057 and 1058.
Disaster Controller The Controller number that this Controller will report to if reporting to a
disaster backup site using the disaster backup telephone number.
Number of Users Maximum number of card users (in thousands) for the Controller. If set to 0,
which indicates no card access, the Linecard will not send any Card Access
broadcast message to the Controller.
Slave Device Address Enter the RS485 address of a slave Pacom Witness.
Note: This setting is used with Pacom Witness only when it is

connected as a slave device.
Disable AC fail monitoring Used when the AC fail input on the Controller is not connected.
Disable DC supply Used when the external DC supply is not being used or does not require
monitoring monitoring.
Disable battery monitor When selected Controller batteries will not be monitored.
Ignore Base Station Enable to prevent Controllers from accepting Base Station timesets (time
Timesets references). This option is designed to be used in systems where an external
time source is required for synchronizing Controllers, and not that of connected
Base Stations.
Disable spare async1 port Disables the tamper alarm on the second DB9 RAP port of 1057 Controllers
tamper only. Same as Disable RAP port tamper (below).
There is no effect on the 1058 as there is no second DB9 port.
Pins 4 and 5 on the DB9 connector must be shorted at the remote end.
Disable RAP port tamper Disables the tamper alarm on the DB9 RAP port of the Controller. If not
selected, pin 4 on the DB9 is monitored for a ground connection. If it is not
terminated, a Main Unit Port Tamper message is generated. Pins 4 and 5 on
the DB9 connector must be shorted at the remote end.
Enable local CCTV switcher Allows the Controller to activate a locally connected camera switcher so that
video can be viewed at a remote monitoring station.
Enable Date Stamp for Enable to include the date as part of the event message time stamp information
Events to prevent any possibility of confusing when a message was actually generated.
The time/date stamps for messages appear in the Transaction Manager and
in reports.
Note: In order to see dates in the Transaction Manager, it must be

set to display them. To do this, select Options > Toggle Date
Display.
Downstream Controller Used to offset the Access Control reader numbers by 64 to make a reader
Addr. number unique throughout the entire system. For example, if a 1 was entered,
64 would be added to all reader numbers when reporting to the monitoring
system. If 2 was entered, 128 would be added to all numbers and so on.
Number of Events The maximum number of events (in thousands) that the Controller will store in
memory.
Enable separate card access A separate queue is created that will store ONLY card access transactions.
queue These are separate to all other alarms raised, and alarm messages are
processed before card access messages. The number of events stored are
shared by both queues, hence the size of both queues is half of the number of
events. For example, if the number of events is 1000, then both the alarm and
card access queues will be 500 events each.
Include as Important Alarms
All available alarm types that can be classified as "important" for are listed
according to their basic category. Enable the checkbox next to each alarm type
in order to classify it as "important".
Note: The options may change depending on other dialog box settings.

If Queue Non-important Alarms (see Dialup Base Station Parameters 53 ) is
selected for network protocols, or if the Controller is on dialup, all non-
important alarms are queued until an Important alarm is activated or when it
dials in. When an Important alarm is activated, the Controller immediately
contacts the Base Station to report all alarms. All External Alarms, Controller
Restart and the Alarms selected here are Important Alarms.
Message Filters
Message filtering allows for various message types to be reported to a Pacom Base Station or a third-party receiver,
so that not all messages are reported. This reduces message bandwidth consumption and stops unwanted messages.
In addition to filtering messages, you can also select message encoding in either Contact ID or SIA format for
compatibility with third-party monitoring systems (see Contact ID and SIA Event Codes 195 ).
Message Filters Select the message types that are to be reported to a Pacom Base Station, or a third-party
receiver. Click a message type to select it. Clicking it again de-selects it (that is, the message
type is not reported).
Report All Click to select and report all available message types.
Filter All Click to de-select all message types from being reported. That is, all message types are
filtered.
Account Number that is provided by the monitoring center to identify the Controller/site that is
Number reporting.
Report true Select to report areas by their actual identification number. For example, area 1 is reported
area number (1 as area 1, area 2 is reported as area 2, and so on. If no selected areas are reported starting
as 1) at 0, that is, area 1 is reported as area 0, area 2 is reported as area 1, and so on.
Supervisory When selected, the Controller reports supervisory messages as supervisory to the monitoring
Command station. If not selected, supervisory messages are reported as standard messages.
Enabling Enable so that the Controller will dial out and send alarm messages to a third-party
Enhanced monitoring station.
Trans-sender
Format Selection
Contact ID Select to encode messages using the standard Contact ID format.
SIA Format Select to encode messages using the standard SIA format.
SNMP Parameters
A Controller can be setup to send messages to SNMP management servers on the network. Specific alarm messages
can also be sent to the servers.

IP Address 1 Enter the IP Address off the SNMP management server on the network that you want specific
alarm messages sent to.
IP Address 2 Enter the IP Address off the second SNMP management server (if it exists) on the network
that you want specific alarm messages sent to. Leave blank if there is only one SNMP server.
Community Enter the community name that is set up on the SNMP server.
Name
Message Text Type in a message to use as part of messages to identify the Controller/site that the
message has been sent from. For example, "Controller No.1 in building 2".
Setting Controller Passwords

A Controller can store up to eight different passwords. These passwords are used when connecting GMS to the
Controller using IP, and connecting IP devices to the Controller (for example, ControllerSignal).
Password X Enter the password (up to eight characters long), as required.
Note: When asked to enter a log on ID, enter the password number to use. For example, if Password 1 is
used, enter log on ID as 1, and enter the password for Password 1.

Configuring Alarm Panel Types

GMS can interact with alarm panels from other manufacturers as well as directly with Pacom Controllers. You need to
define the alarm panel/Controller type in GMS, so that it communicates correctly with the system.
Configuring an Alarm Panel Type and Setting the Number of Alarm

User Types
The Controller dialog box contains an extensive list of panel types, including Pacom panels and third-party panels. By
default all Pacom Controllers are defined as "Pacom Standard", regardless of being an 8001, 1057 or 1058.
Therefore, it is generally not necessary to set the alarm panel type for Pacom Controllers.
To define a Pacom Controller alarm panel type, proceed as follows:
2. In the Controller dialog box, select General > Alarm Panel Type. The Set Remote Alarm Panel Type dialog box
opens.
3. In the RAP Types list, select an alarm panel type.
Note: Some third-party alarm panel types require additional set up procedures or hardware (see
Configuring Third-Party Alarm Panels 106 ).
For Pacom Alarm Panels:

a. In the RAP Types list, select Pacom Standard for 1057/1058 Controllers or Pacom Enhanced for 8001
Controllers.
b. In the Users region select 99 or 66. If 99 is selected, the maximum number of possible alarm users is 99
and the maximum PIN length for identifying them is four digits. If 66 is selected, the maximum number of
possible alarm users is 66 and the maximum PIN length for identifying them is eight digits.
c. For general operation, in the Custom Code list, select Standard config. For information on available
predefined configuration options for compliance with certain standards, see Predefined Compliance
Configurations 99 .
4. Click OK. A warning dialog box is displayed. Click Yes to proceed with the settings changes. To select another
setting, click No.
Note: Changing the alarm panel type defaults any configuration in the Controller (except for Port Settings)
to default settings.
Once the alarm panel type has been changed, restart it before proceeding.
Accessing Configuration Settings for Non-Pacom Alarm Panels/

Controls
When non-Pacom Controllers are used, the Controller dialog box is not used. Instead, the previous GMS RAP
configuration dialog boxes are used. The available functions are the same, however, the method of accessing them
differs from a single dialog box to multiple dialog boxes that you can access from the previous Controller Config
Options dialog box (shown below).

This dialog box acts as the access point to the various available configuration options (instead of through the
Controller dialog box). To access the various configuration screens, select the configuration type from the Options
list, then click OK. The corresponding dialog box opens, as it would from selecting the same option using the menu
system in the Controller dialog box for Pacom Controllers.

Predefined Compliance Configurations

Options in the Set Remote Alarm Panel Type dialog box (see Configuring Alarm Panel Types 97 ), Custom Code list
(apart from the Standard Config option) represent predefined Controller configurations. These configurations are
designed to aid compliance with a range of operational standards for different regions or applications of the system.
Many parameters set by the predefined Controller configurations remain editable, therefore, it is advisable to note
which settings are affected. Refer to the following sections for descriptions of applicable settings as they are
configured by default for each option:
EN50131 Configuration
Alarm Area Settings (see Configuring Alarm Areas 172 )

Exit Delay 1 for each alarm area = "30".
Exit Delay 2 for each alarm area = "15".
Entry Delay 1 for each alarm area = "30".
Entry Delay 2 for each alarm area = "15".
General Alarm System Parameters (see Configuring General Alarm System Parameters 163 )
Multiple PIN Attempt Timeout = "90".
Alarm Confirm Time = "30".
Alarm Confirm Areas = Option enabled for alarm area 1 only.
Abort Window Time = "45".
Suspect Device Activation Counter = "3".
Reset Activation Latch by User = Option enabled.
Message Log Size = "1000".
Enable PIN Code Error Reporting = Option enabled.
Enable Scrolling of Power Alarms = Option enabled.
Engineer Requires Staff to Log On First = Option enabled.
Staff Can Change Only their Own PIN = Option enabled.
Do Not Show Status on Keypads when Idle = Option enabled.
Alarm System Flags (see Configuring Alarm System Flags 167 )

Enable AC/Batter Low Display on Exit = Option enabled.
Enable Comms Status Display on Exit = Option enabled.
Latch Tamper Alarms = Option enabled.
Report Tampers when Point is Latched = Option enabled.
Report Tamper Alarms when Device is Latched = Option enabled.
SIA CP-01 Configuration
Alarm Area Settings (see Configuring Alarm Areas 172 )

Exit Delay 1 = "50".
Exit Delay 2 = "10".
Entry Delay 1 = "20".
Entry Delay 2 = "10".
General Alarm System Parameters (see Configuring General Alarm System Parameters 163 )
Abort Window Time = "30".

1058 Bank Configuration

As per the Standard Config option, however, with specific keypad message strings that cannot be over-ridden.
UK Bank Configuration
As per the Standard Config option, however, with the first eight input points pre-configured and the access times
for Staff, Cleaner and ATM alarm user types preset for 24 hour access (see Configuring Alarm Users Types 131 ).

Configuring Controllers for Transender Operation

Transender operation enables alarms originating from different Controllers to be consolidated and sent from a single
location to a central monitoring station. For dial-out applications, this could mean that a customer can interconnect
multiple Controllers over an IP network, which requires a single telephone line, rather than a dedicated line per
Controller (site), to report to the monitoring center.
In an enterprise-wide application, users can configure exactly which Controllers (sites), as well as the specific alarm
types, to report to the central monitoring station using the Transender. The Transender provides flexible and cost-
effective monitoring system.
Pacom 1057/1058 and 8001 Controllers can be configured to operate as Transenders. The Transender has an on-
board dialer which supports dialling out to the monitoring station and messaging using Contact ID or SIA formats. It
also supports SMS format when dialling out using a GSM modem. Other Transender features include:
Queuing "non-important" alarms before initiating dial-out.
Consolidating alarms from up to 10,000 sites using Pacom TransIT and Base Station hardware, or up to 24 sites
per master Controller in a peer-to-peer configuration.
Filtering alarm types to send to a monitoring station.
Using enhanced messaging functionality (see Enhanced Transender Configuration 104 ).
Transender in Peer-to-Peer Configuration
In a peer-to-peer network, the master Controller acts as the Transender, while all the other connected Controllers act
as slaves. The Transender routes the slave Controller messages to third-party monitoring stations.
The Transender (master Controller) will report its (Controller/site ID number) or account ID to the monitoring center
for any slave Controller message. Using enhanced Transender configuration, slave Controllers can report their
individual ID as part of the message (see Enhanced Transender Configuration 104 ).
Setting Up a Controller-TransIT-Transender Configuration

To configure the TransIT port that the Transender is connected to, proceed as follows:
1. In GMS, select Hardware > CCU Card/TransIT. The TransIT Options Menu and Line Card dialog boxes open.

2. In the Line Card dialog box:

a. In the Card No field, enter 1.
b. Select the CPU Port A option, then click OK.
3. In the TransIT Options Menu dialog box:
a. In the menu list, select Port Parameters, then Click OK. The CCU Parameters/Errors dialog box for the
TransIT opens.
b. Click the port image that the Transender is connected to. The CCU Port Parameters dialog box for the port
opens.
i. Click the Protocol tab.
ii. In the Protocol list, select Enhanced PCP.
iii. In the Application list, select Setup/Monitoring PC.
iv. Click the Async Driver tab.
v. In the Baud Rate list, select 38400.
vi. Click the Protocol tab, then click Download.
Configuring Controller to Transender Reporting

To enable Controllers to report to the monitoring center using the Transender, ensure that the TransIT CPU port for
each Controller is set for the Controller account in the TransIT. The CPU port is the port on the TransIT that the
Transender is connected to.
Configuring the Transender Port for TransIT Communications

To configure the Transender RS232 port to communicate with the TransIT, proceed as follows:
1. Open the Controller dialog box and select the Controller acting as the Transender (see Using the Controller
Dialog Box 21 ).
box opens.
3. Click the image of the port connected to the TransIT. The Port Protocol Parameters dialog box for the port
opens.
4. Click the Link Level tab.
5. In the Protocol list, select Enhanced PCP Protocol.

6. Click Download.
Setting Up a Slave-Master/Transender Controller Configuration

To configure the Controller for master/Transender operation, proceed as follows:
box opens.
3. Click Advanced, then select Peer-to-Peer Settings. The Peer Parameters dialog box opens.
4. In the Master Controller region, enable the Enable Transender and Send alarms to all ports options.
5. Click Download.
Configuring the Transender Modem Port

1. Open the Controller dialog box and select the Controller acting as the Transender (see Using the Controller
Dialog Box 21 ).
box opens.
3. Click the Modem port image. The Port Protocol Parameters dialog box for the port opens.
4. Click the Base Station tab, and select the Telephone Numbers option.
5. Choose the correct reporting format (Contact ID or SIA) and enter the required telephone numbers for the
receiver.
6. Select the Parameters option.
7. Enable the Apply Message Filters before Dialup option.
8. Click Download.
Configuring Message Format and Filtering

The message format instructs the Controller to encode the Pacom message into the equivalent Contact ID or SIA
format for interpretation by the third-party monitoring system .
Message filtering determines which alarms/messages are forwarded to the receiver. Normal Transender operation
uses the Transender to apply any message filtering. With enhanced operation individual Controllers can apply
message filtering before reporting to the Transender or TransIT. For greatest flexibility, use enhanced Transender
operation (see Enhanced Transender Configuration 104 ).
Note: The message format must be consistent across all Controllers and the Transender.
To set up message formatting and filtering, proceed as follows:

1. Open the Controller dialog box and select the Controller as required (see Using the Controller Dialog Box 21 ).
2. In the Controller dialog box, select General > Message Filters. The Message Filters dialog box opens.

3. In the Message Filters list, select the messages to report. Highlighted messages are reported.
Note: Filters applied to the Transender will apply to all messages reported to it.
4. In the Account Number field:

For normal Transender operation, enter the Transender account number for identification by the third-party
receiver.
For enhanced Transender operation, enter the Controller account number for identification by the third-party
receiver (see Enhanced Transender Configuration 104 ).
5. Enable the Report true area number option to report areas by their actual identification number. For example,
area 1 is reported as area 1, area 2 is reported as area 2, and so on. If no selected areas are reported starting
at 0, that is, area 1 is reported as area 0, area 2 is reported as area 1, and so on.
6. Select the Contact ID or SIA option to determine the message encoding required by the third-party receiver.
Note: The message format must be consistent across all Controllers and the Transender.
7. Click Download.
Enhanced Transender Configuration

Enhanced Transender operation provides greater flexibility for identifying reporting Controllers and filtering reported
messages. With enhanced Transender operation, you can:
Configure unique account numbers for each reporting Controller. The account number range is 1-9999 for
Contact ID, and 1-999999 for SIA. With normal Transender operation, reporting Controllers include their
Controller ID/address with each message.
Configure individual Controller message filtering and apply them prior to reporting to the Transender.
Configure individual input points to report more specific messages (see Configuring Input and Output Points 142 ).
To enable Enhanced Transender functionality, proceed as follows:
1. Open the Controller dialog box and select the Controller as required (see Using the Controller Dialog Box 21 ).
2. In the Controller dialog box, select General > Message Filters. The Message Filters dialog box opens.
3. Enable the Enabling Enhanced Transender option.
4. Click Download.
Checking Slave Communications with Master/Transender

Controllers
Once a slave Controller has established communication with the master, the slave will regularly poll the master to
maintain activity notification. In the event of a failure in communications, the master will report the slave as being
offline and the GMS Summary Manager will also show the site as offline. If, however, a slave Controller is added to
the system and never establishes communications with the master, the master will never have a record of it and will
not be able to report the failure.

To check slave Controllers are communicating with the master, and therefore, able to send alarms/messages to it,
proceed as follows:
1. Open the Controller dialog box (see Using the Controller Dialog Box 21 ).
2. In the Controller ID field, enter the ID number of the Controller.
3. Click Change.
If the Controller parameters are downloaded and the Controller dialog box shows the Controller status,
communications are normal.

Configuring Third-Party Alarm Panels

Pacom Controllers are capable of interfacing with a range of third-party alarm panel products, allowing for easy
integration with existing systems. Generally, the Pacom system provides a higher level of functionality than most
third-party systems, such as IP communications and remote control capability from a monitoring center.
The configuration is based around connecting the third-party panel to a Pacom Controller. The Controller then
communicates messages from the panel to GMS in the normal way.
Third-party panels can be connected using a:
Generic Contact ID interface, which provides one-way messaging from the third-party panel.
Specially designed interface for some popular third-party alarm panels that support the third-party
manufacturer's protocol. This provides messaging as mentioned previously, but may also allow commands to be
received from GMS through the attached Pacom Controller. Refer to the sub-sections to this topic for more
detailed configuration information for some of the more common third-party panels.
Note: For a list of currently supported third-party alarm panels and features, refer to the DSH-025 Third-
Party Panel Interface Datasheet.PDF file that is available from the Pacom website.
Configuring Generic Contact ID Alarm Panels

Pacom Controllers are compatible with third-party alarm panels and digital receivers that support Contact ID
messaging format.
Wiring Information
A Pacom 1050-204 mezzanine card is required for the Controller to communicate with the third-party Contact ID
compatible panel. Install the mezzanine card on the Controller according to the installation instructions.
Use a RJ12 cable with the following pin assignment to connect the two systems.
Pacom PIN Third-Party Panel

3 Tip
4 Ring
Configuring the Alarm Panel Type and Controller Port for Third-
Party Contact ID Communications
To configure the alarm panel type and port parameters for Contact ID operation with a third-party alarm panel,
proceed as follows:
opens.
3. In the RAP Tyes list, select CID-Dialler (Mezzanine).

4. Click OK. A warning dialog box displays. Click OK to continue. The Controller restarts to apply the settings.

6. Enable the Port Parameters option.

7. Click the image representing the port that the panel is connected to. The Port Protocol Parameters dialog box
opens for the port.
8. In the Protocol list, select General Purpose Driver.
9. In the Driver Type list, select Dialer Interface.
10. In the Time between idle polls field, enter a value according to the following rules. Values in the range of 1 -
127 is x100 milliseconds. 128 indicates termination on input for reporting online/offline messages. 129
indicates 1 hour check-in time one has to enter. Similarly, 130 indicates 2 hours check-in time, etc.
11. Click Download to save the settings to the Controller, then click Reboot.
The Controller is now configured to receive communications from the third-party panel.
Configuring the Panel

Follow the relevant installation and programming instructions for the third-party panel and ensure the Reporting
Format is set to DTMF Contact ID - Large.
Configuring a Galaxy Interface

This section outlines integration between the Pacom system and Galaxy alarm panels.
Wiring Information
You need to connect the Pacom Controller to the Galaxy panel using RS232. The Galaxy panel requires a DB25
connector and, depending on the attached Controller, a DB25 or DB9 connector, or hard wired to the Controller
RS232 serial port.
Note: Ensure that any Controller RS232/485 link settings for the port are set for RS232 operation.
The cable requires the following pin connections:
Controller DB25 Connector
Controller Port Pin (DB25) Galaxy Panel DB25 Connector Pin

3 (Rx) 2 (Tx)
2 (Tx) 3 (Rx)
7 (GND) 7 (GND)
Controller DB9 Connector
Controller Port Pin (DB9) Galaxy Panel DB25 Connector Pin

2 (Rx) 2 (Tx)
3 (Tx) 3 (Rx)
5 (GND) 7 (GND)

Configuring the Alarm Panel Type and Controller Port for Galaxy
Communications
To configure the alarm panel type and port parameters for operation with a Galaxy alarm panel, proceed as follows:
opens.
3. In the RAP Type list, select Galaxy Panel, then click OK. A warning dialog box is displayed. Click OK to
continue. The Controller will restart to apply the new settings.

opens for the port.
7. In the Protocol list, select General Purpose Driver and make the following settings:
a. Baud Rate: 38400.
Note: The baud setting may vary according to the panel type. If the panel does not come online (indicated
in the Transaction Manager), try other baud settings until communications are established.
b. No. of Data Bits: 8.

c. No. of Stop Bits: 1.
d. Parity: None.
e. Receive Buffer Size: 17.
f. Maximum Idle Time: 10.
g. Physical Layer Protocol: EIA RS232C.
h. Time Between Idle Polls: 2.
i. SCC Reset Time when Offline: 5.
8. In the Driver Type list, select Galaxy Serial Interface.
9. Click Download, then click Reboot.
The Controller is now configured to communicate with the Galaxy panel. The panel should come online, indicated by
a Transaction Manager message:
Controlling the Panel from GMS

GMS can control various functions of the Galaxy panel. The functionality available through GMS is:
Mode change commands for individual areas or the whole site.
Interacting with alarm points - acknowledging, activations etc.
Adding alarm panel users of different types and assigning PINs.
Saving Controller configurations that you can apply to other alarm panels.

The following procedure describes adding alarm panel users. For more information regarding other setup options,
contact Pacom support.
Configure alarm panel users as follows:
1. Open the Controller dialog box and select the required Controller (see Using the Controller Dialog Box 21 ). The
dialog box layout changes to suit the supported functions for Galaxy panels. It also includes some configuration
or status features of the attached Pacom Controller.
2. In the Options list, select User IDs, then click OK. The Galaxy Panel Password Configuration dialog box opens.
3. Select the user type option as required. Each user type has access to particular alarm panel functionality, for
various purposes. The table below summarizes the available settings and limitations.
User Type Number Name Password

User 1 - 97 Alpha characters only (no Numerical
numbers) up to six in total characters only
Manager 98 (fixed) MGR (fixed) (no letters)
between four and
Engineer 99 (fixed) ENG (fixed) six digits in length
Remote 100 (fixed) REMOTE (fixed)
Site N/A N/A
4. Click Download to save the settings in the Galaxy panel.
Configuring a Hisec Interface

This section outlines integration between the Pacom system and Hisec ThorGuard alarm panels.
Wiring Information
You need to connect the Pacom Controller to the Hisec panel using RS232 cable connection and the Hisec GPI
(General Purpose Interface) protocol.
Configuring the Alarm Panel Type and Controller Port for Hisec
Communications
To configure the alarm panel type and port parameters for RS232 operation with a Hisec ThorGuard alarm panel,
proceed as follows:
opens.

3. In the RAP Type list, select Hisec ThorGuard.

4. In the CU # field, enter the Hisec panel number.
5. In the Input Bank list, select the range of inputs (in groups of 256) that are mapped to the Pacom Controller
inputs.
6. In the Output Bank list, select the range of outputs (in groups of 64) that are mapped to the Pacom Controller
outputs.
7. Click OK. A warning dialog box is displayed. Click OK to continue. The Controller will restart to apply the new
settings.

opens for the port.
9. In the Driver Type list, select Hisec ThorGuard.
10. Click Download to save the settings to the Controller, then click Reboot.
The Controller is now configured to receive communications from and send certain commands to the Hisec alarm
panel.

Follow the relevant installation and programming instructions for the Hisec panel. For more information, contact
Pacom support.
Configuring a Tecom Interface

This section outlines integration between the Pacom system and Tecom Challenger V8 alarm panels.
Wiring Information
You need a Pacom 1050-202 mezzanine card for the Controller to communicate with the Tecom Challenger V8. Install
the mezzanine card on the Controller according to the installation instructions.
Use a standard RJ12 PSTN cable to connect the Tecom panel to the mezzanine card.

Configuring the Alarm Panel Type and Controller Port for Tecom
Communications
To configure the alarm panel type and port parameters for operation with a Tecom Challenger alarm panel, proceed
as follows:
opens.
3. In the RAP Type list, select Challenger-V8, then click OK. A warning dialog box is displayed. Click OK to
continue. The Controller will restart to apply the new settings.

opens for the port.
8. In the Driver Type list, select Challenger.
9. Click Download, then click Reboot.
The Controller is now configured to receive communications from and send certain commands to the Tecom
Challenger V8 panel.

Follow the relevant installation and programming instructions for the Tecom Challenger V8. Ensure that the Reporting
Format is set to Tecom Direct Line - Large, and that Network Commands are enabled on the panel. For more
information, contact Pacom support.

Using Controller Licensing Grace Period

It is possible to enable Controller features that are unlicensed for a period of 14 days. This feature is generally aimed
at installers or technicians that have installed or replaced a Controller and do not have the required license file on
hand to enable the necessary features.
Note: The grace period can be set only once. After the grace period expires, any Controller features that
are unlicensed will be disabled.
Enabling the Controller Licensing Grace Period

You can enable the grace period option from either a keypad connected to the Controller, or from GMS.
To enable the Controller licensing grace period, proceed as follows:
Using a Keypad:
1. With the system in Day mode, log on to Engineering mode.
2. Enter the Config menu.
3. Enter the License menu.
4. Enable the Enable Grace Period option.
5. Log off.
Using GMS:
2. Select Commands > User Defined Commands > Define Command. The Controller User Defined Command
dialog box opens.
3. In the Function Code field, enter 46.

4. In the Command Data field, enter 4,0x81,0,0,0,0,0,0.
5. Click Send.
Viewing the Remaining Grace Period

The Controller starts the grace period countdown. To view how much grace time is available, proceed as follows:
2. Select View > Controller Licenses. The Controller License Options dialog box opens.

The number of days remaining appears under the Controller serial number.

Printing Controller Configuration Reports

You can create HTML files detailing alarm and access control configurations stored in a Controller. The files can be
opened in any web browser and saved or printed.
To export Controller configuration information into HTML files, proceed as follows:
2. In the Controller dialog box, select File > Export, then select an option for the information you want. Options
are:
All Configurations - Creates files for all alarm and access control configurations and places them in the "
GMS\Customer" folder by default.
Alarm > All - Creates files for all alarm configurations and places them in the "GMS\Customer" folder by
default.
Access Control > All - Creates files for all access control configurations and places them in the "
GMS\Customer" folder by default.
All other sub-group options - Creates files for the selected sub-group and places them in a folder you select
from the Windows Save As dialog box.
After each file is created it will open in the default web browser.

Configuring and Using Controller Power Monitoring

You can use GMS and the Controller to set up the parameters for Pacom 8303 devices. The 8303 is a transformer/
power supply and voltage regulator that has monitoring circuitry built-in. The monitoring functionality is used for
remote maintenance testing (see Configuring GMS - Administrator Guide, Configuring Remote Maintenance Testing)
and reporting (see Using GMS - Operator Guide, Remote Maintenance Reporting.
Signals from 8303s can be used to trigger alarms if the output voltage (to the monitoring circuitry), backup battery
voltage or temperature of the unit fall outside defined parameters. These parameters are monitored constantly.
Configuring Battery Testing and Power Monitoring

To configure battery test schedules and power supply parameters, proceed as follows:
2. Select General > Power Supply Settings. The Battery Testing and Power Supply Parameters dialog box
opens.
3. Click a numbered button at the top of the dialog box to select the 8303 to configure. Up to four 8303s can be
monitored using a single Controller. Configure the parameters according to the following table.
4. Click Download to send the configuration to the Controller.
Not Configured Enable to activate power monitoring and battery testing for the selected 8303.
When disabled, the parameter controls are disabled.
Note: 8303 devices are auto-detected by the system when the

Controller is restarted and their device addresses are automatically
assigned.
Device loop address Enter the device address for the 8303. If the address is unknown, enable the
Not Configured option and restart the Controller. The device address is
automatically configured.
Battery test time The time of day to begin battery testing. Battery testing is performed daily.
Click to display a list of time options. Click an option to select it.
Battery test period The period of time to run off the battery during testing. Battery testing is
performed daily. Click to display a list of time options. Click an option to select
it. If you select OFF, no battery testing is performed.
Battery ampere hours Enter the ampere-hour (Ah) of the backup battery. This setting is used to
calculate operating time when running off the battery. Entering 0 disable the
Pre-warning time setting.
Nominal current drain Enter the anticipated current drain (in amperes) on the backup battery when
running off it. This setting is used to calculate operating time when running off
the battery. Entering 0 disables the Pre-warning time setting.

Pre-warning time Enter the time (in hours) before the battery will run out to generate an alarm.
For example, if the backup battery is rated at 16Ah, and the current drain is
2A, the battery will last for eight hours. Setting the Pre-warning time to 2,
will generate an alarm after the battery has been used continuously for six
hours.
Using 1057/1058 on Enable to charge the backup battery from the charger built into 1057 and
board charger 1058 Controllers.
Report as main unit Enable to have the Transaction Manager report power monitoring alarms as
though generated by the Controller and not specifically the attached 8303
device.
Battery Slide the bars to set the acceptable backup battery voltage range. The
acceptable range is shown in green. If the voltage falls outside the range and
into the red, an alarm is generated.
Input Supply Slide the bars to set the acceptable voltage range from the mains voltage to
nominal 15V DC transformer. The acceptable range is shown in green. If the
voltage falls outside the range and into the red, an alarm is generated.
Temperature Slide the bars to set the acceptable 8303 internal temperature range. The
acceptable range is shown in green. If the voltage falls outside the range and
into the red, an alarm is generated.
Manually Testing Batteries

You can use the GMS user-defined command feature to perform a backup battery load test on selected Controllers
using 8303/8301 devices. The test places a 1A load on the batteries for a period of time (approx. one minute). In
cases where multiple power monitoring devices are attached to a Controller, all connected batteries are load tested
and reported on.
Test results are based on the same parameters as in the Battery Testing and Power Supply Parameters dialog box.
To manually test backup batteries, proceed as follows:
2. Select Commands > Test > Perform Battery Test for Pacom 8303 Power Supply, then select an option to
either test an individual power monitor device, or all of them simultaneously.
After the load test completes, result messages display in the Transaction Manager.
You can also test power monitoring device backup batteries with a user-defined command (see Controller User-
Defined Commands 119 ), as follows:
1. In GMS, select Hardware > User Defined Commands. The User Defined Commands dialog box opens.
2. In the Element Type list, select Controller.
3. In the Element No. field, type the ID number of the Controller(s) to accept the command.
4. In the Function Code field, type 21.
5. In the Command Data field, type 59, followed by a comma (",") and either 0, 1, 2, 3 or 255, where:
0 represents power monitoring device 1.
255 represents all power monitoring devices.
For example, "59,2".
6. Click Send. After the load test completes, result messages display in the Transaction Manager.
Power Monitoring Alarm Messages

Power monitoring alarms are displayed in the Transaction Manager using the following messages:
Message Description
AC Fail Indicates that the 8303 transformer stage - from mains voltage to nominal 15V DC,
is outside the acceptable range.

Message Description
AC Restore Indicates that the 8303 transformer stage - from mains voltage to nominal 15V DC,
is within the acceptable range. This message displays only after an AC Fail alarm
has occurred.
Battery Low or High Indicates that the connected backup battery is outside the acceptable range.
Reset Battery Low or Indicates that the connected backup battery is within the acceptable range. This
High message displays only after a Battery Low or High alarm has occurred.
High Temperature Indicates that the internal temperature of the 8303 is outside the acceptable range.
High Temperature Indicates that the internal temperature of the 8303 is within the acceptable range.
Restored This message displays only after a High Temperature alarm has occurred.
Fuse Fail Indicates that an 8303 power output fuse has failed.
Battery testing involves running the attached hardware devices from the backup battery for a specified period of time
on a daily basis. During battery testing, the voltage is monitored, so that batteries that will require replacement can
be identified before possible failure.
Viewing Controller Power Monitor Status

The Controller dialog box has facilities to view the status of configured power monitoring 8303 devices.
2. Select Power Monitors from the list on the left-hand side. The power monitor status screen appears. If there
are several 8303s being monitored, use and to switch between them.

Checking Controller Memory Battery Status

Note: This feature is applicable to firmware versions 5.02+ for 105x Controllers and 1.04+ for 8001
Controllers.
You can force Controllers to test their on-board lithium memory battery and return the battery status in the
Transaction Manager. Use this check to determine whether or not the:
Battery is present. The plastic tabs may still be in place and the battery is not connected, or a battery is not
installed.
Battery voltage is low. The battery requires replacement.
Note: Transaction Manager messages appear only if the battery fails the test.
The battery test is performed by Controllers whenever they receive the time set command. Perform the test as
follows:
Note: Sending this command also synchronizes the Controller time setting with GMS time, however, does
not alter any timezone settings. GMS automatically broadcasts this command each night to help maintain
accuracy between GMS and Controllers.
1. In GMS, select Hardware > Broadcast Commands. The Broadcast Commands dialog box opens.
2. Select the Set System Time option.

3. Click OK. Check the Transaction Manager - it will show "Reminder: Battery Test Fail" messages for each
Controller where the test is not passed.

Controller User-Defined Commands

GMS provides facilities for configuring Controllers and other hardware through the use of a command structured
syntax. Using commands can speed up parameter settings and other configuration information without having to use
the standard GMS user interface.
Note: The range of commands is not intended for use by GMS operators or administrators however, and is
provided specifically for use by Pacom technicians. For further information on commands, contact Pacom
support.
Controller Specific User-Defined Commands

To create and save commands for applying to specific Controllers, proceed as follows:
2. Select Commands > User Defined Commands > Define Command. The Controller User Defined Command
dialog box opens.
3. Create the command by entering the required values in the Function Code and Command Data fields.
4. Type a command description in the Available Commands list, then click Save/Delete. To save the command,
click Save from the confirmation context menu that appears.
To run a saved user-defined command, proceed as follows:
2. Select Commands > User Defined Commands > Available Commands, then select the command to run
from the list that appears.
Using User-Defined Commands for Diagnostics

User-defined commands are used by technicians to run diagnostics on the connected Controller. For example, send
Function Code=46, Command Data=5,4. Check the response in Transaction Manager. This will report back
information on the flash memory on the Controller. 1=4 MB flash, 2=8 MB flash, 3=16MB flash. Switching to
hexadecimal display on the same message should show the following:
extended data 0 = 10
extended data 1 = 0
extended data 2 = Hardware type (19 for 1057, 23 for 1058)
extended data 3 = Hardware revision number
extended data 4 = Current running chip
extended data 5 = chip 1 version high byte
extended data 6 = chip 1 version low byte
extended data 7 = chip 2 version high byte
extended data 8 = chip 2 version low byte
extended data 5 = Rijndael encryption version high (running chip)
extended data 6 = Rijndael encryption version low (running chip)
Hardware User-Defined Commands

To create and save commands for all hardware types, proceed as follows:
1. In GMS, select Hardware > User Defined Commands. The User Defined Commands dialog box opens.

2. In the Element Type list, select the hardware type to be targeted by the command.
3. In the Element No. field, enter the ID number of the hardware to accept the command.
4. Create the command by entering the required values in the Function Code and Command Data fields.
To upload the data specified in the command to GMS memory, enable the Data Upload? option, then enter the
function code required for the uploaded data in the Upload Function Code field. When the data is uploaded
you can use the command to download the data into other hardware. For example, to copy the configuration of
a Controller and download it into other Controllers.
Enable the Hex Display option to display the returned data in hex format. The data appears within the User
Defined Commands dialog box.
5. Type a command description in the Available Commands list, then click Save.
To run a saved user-defined command, proceed as follows:
1. In GMS, select Hardware > User Defined Commands. The User Defined Command dialog box opens.
2. In the Available Commands list, select the saved command.
3. Click Send.

Chapter 2
Managing Firmware
121
Firmware is a term used to describe a program that resides between software and hardware. Generally, the program
is embedded in some type of ROM (read-only memory) memory on a hardware product to control its operation.
Firmware for Pacom Controllers is stored on EEPROM and can be updated using GMS.
Firmware is downloaded into Controllers using GMS, either locally from a laptop connected using a diagnostic cable,
or remotely from a monitoring workstation (if the Controller is online). Firmware can also be stored on TFTP (trivial
file transfer protocol) servers. This process does not require you to load the firmware files into GMS first and can be a
faster and more convenient way of managing firmware.
Note: You can obtain the latest firmware from the Pacom website (www.pacom.com) in compressed
format. Before you can load it into GMS, unzip the files to a folder on your system.
This section contains information and procedures about obtaining firmware and downloading it to Pacom Controllers
and devices, including:
Checking Controller Firmware Version 123 .
Downloading Firmware to Controllers 123 .
Continuing Interrupted Downloads 125 .
Running Firmware in Chip 1 or Chip 2 125 .
Running the Latest Version Firmware 125 .
Specifying the Active Chip 125 .
Deleting Firmware Files.
Downloading Firmware to 1064/1076/1068 Devices 127 .
Deleting Firmware Files

To delete firmware files from GMS, proceed as follows:
2. Select Commands > Firmware Commands > Other Firmware Commands. The Firmware Commands dialog
box opens.
3. Enable Options and select Delete Firmware Files from the list below it. The Select File to Delete list
displays.
4. Select the file to delete, then click OK. The file is removed from the list and will no longer appear in the Select
File to Download list.
5. Click Exit to close the dialog box.
122 | Chapter 2 - Managing Firmware

Controller Firmware
Controller firmware is stored in non-volatile flash memory chips. Some Controllers use two physical chips and some
use a single chip divided into two virtual chips. In either case, operation is the same. Controllers operate using
firmware stored on either chip. The chip that is not being used to operate the Controller is available to store updated
firmware while it is being downloaded. This minimizes interruption to the system during firmware upgrades.
Once the new version has been downloaded, use a Controller command to run the latest software version. The
Controller automatically determines the newer version, or it can be commanded to run from a specific chip.
Pacom Controllers are shipped with the latest firmware at the time of manufacture. However, it is always a good idea
to check if for later versions at www.pacom.com.
Checking Controller Firmware Version

To view Controller firmware version and related information, proceed as follows:
1. If the Controller is online, connect to it through a monitoring PC. If the Controller is not online, connect to it
locally using a diagnostic cable (see Connecting to GMS 12 ).
3. Select Commands > Firmware Commands > View Firmware Version. The Controller dialog box opens
showing the firmware version contained in chip 1 and chip 2, the active chip, the Controller type, PCB hardware
revision and Rijndael encryption algorithm version.
Note: ff.ff indicates the chip is empty or contains incomplete firmware.
Downloading Firmware to Controllers

Firmware can be downloaded to the inactive chip only. Two files are required for each version of firmware:
.EPR - A firmware file that resides in the flash memory on the Controller PCB.
.BDT - A bank definition file required by GMS that describes the contents of the .EPR file.
Downloading Directly from TFTP Servers

You can use GMS to instruct Controllers to download firmware directly from a TFTP server. Using TFTP servers can
significantly reduce firmware download times.
To download firmware to a Controller from a TFTP server, proceed as follows:
box opens.
3. Select Options, then select TFTP Download from the list below it.
Chapter 2 - Managing Firmware | 123

4. In the TFTP Server IP Address field, enter the IP address of the server.
5. In the Controller Port list, select Ethernet.
6. Optionally, in the File Name field, enter the name of the *.EPR file. If no entry is made, default filename values
are applied according to the Controller type.
7. Click OK. A Download Confirmation dialog displays. Click Yes to download the firmware, or No to return to the
Firmware Commands dialog box.
8. If Yes is clicked, the Download dialog box opens and the:
The Controller EEPROM is erased.
The firmware downloads. This can takes several minutes.
When the download is complete, a status alarm generates, confirming a successful download.
9. Once the download completes, click Exit to close the dialog box (do not click OK). The Controller must be
commanded to run the new software version (see Running Firmware in Chip 1 or Chip 2 125 ).
Downloading from GMS

Downloading firmware from GMS is a two step process:
1. Load the firmware in to GMS. Firmware cannot be loaded directly in to the Controller/TransIT/CCU from a
storage device.
2. Download the firmware to the Controller/TransIT/CCU using GMS.
Note: Increasing the baud rate to 38400 prior downloading firmware substantially decreases download
time (see Increasing the Diagnostic Port Connection Speed (Baud Rate) 13 .
To download firmware to a Controller, proceed as follows:

box opens.
3. Select Options, then select Load Firmware Files from the list below it.
4. Specify the location of the *.EPR and *.BTD files using one of the following methods:
Enter the entire path to the directory directly in to the Enter Source Dir field, or
Click ... to browse for the files using the Browse for Folder dialog box.
5. Once the file locations are specified, click OK.
6. If the files are successfully located by GMS a confirmation message is displayed. Click OK to return to the
7. In the Options list, select Download Firmware. The Select File to Download list displays below the Options
list.
8. Select the required firmware version from the Select File to Download list.
9. In the Target list, select Controller, or 1064/1068/1076/8303 (for Card Reader Interface firmware
downloads).
10. Click OK. A Download Confirmation dialog displays. Click Yes to download the firmware, or No to return to the
11. If Yes is clicked, the Download dialog box opens:
The Controller EEPROM is erased.
The firmware then downloads. This can takes approximately 20 to 30 minutes at 38400 baud.

The firmware version number displays in the Download dialog box title bar. The Bank and Pointer No.
information also displays.
When the download is complete, a status alarm generates, confirming a successful download.
If a Card Reader Interface firmware version has been downloaded to the Controller do not click Exit, but continue as
described in Downloading Firmware to 1064/1076/1068 Devices 127 .
Caution: Once the download is complete, do not click OK in the Firmware Commands dialog box. Doing
so restarts the download, erasing the previous data before the abort key can be pressed.
Continuing Interrupted Downloads

Normally, the full firmware is downloaded, starting at bank one and pointer zero. For download purposes, the
firmware is divided into 32K banks. Each downloaded bank uses a separate Pacom Streaming Protocol (PSP)
operation. GMS automatically moves to the next bank after the previous bank has completed downloading. GMS does
this until all banks are downloaded.
If a download fails to complete for any reason, it can be continued from the break point using the Options list
Continue Download command. GMS automatically detects the bank and pointer values at which the operation failed
and continues the download from that point.
Note: This does not apply to TFTP downloads 123 , where a timeout or other download interruption has
occurred. For TFTP download failures, the download must be tried again.
To continue downloading a cancelled or erroneous download, proceed as follows:

1. In the Firmware Commands dialog box Options list, select Continue Download. The Select Process to
Continue list displays.
2. In the Select Process to Continue list, select the process to continue, then click OK. The Download dialog box
opens and the downloads continues from where it was previously stopped.
Caution: Once the download is complete, do not click OK in the Firmware Commands dialog box. Doing
so restarts the download, erasing the previous data before the abort key can be pressed.
Running Firmware in Chip 1 or Chip 2

Controllers store firmware in two flash EEPROM chips. Only one chip is active (that is, operational) at any one time.
The Controller is commanded to operate using the firmware on either chip as required. Data is only downloaded to
the inactive chip, that is, the chip that is not being used by the system. Once the firmware download is complete, the
Controller must be commanded to operate using the other chip to run the new firmware.
Running the Latest Version Firmware

To run the latest firmware version, proceed as follows:
2. Select Commands > Firmware Commands > Restart Using Latest Version.
For the Controller to change from one chip to the other, it must shut down momentarily. When the Controller
comes back online, it runs in the chip containing the latest firmware version. This action is verified in the
Transaction Manager (see Configuring GMS - Administrator Guide, Using the Transaction Manager).
3. Click Exit to close the Firmware Commands dialog and return to the Controller dialog box.
Confirm the latest version of firmware is running (see Checking Controller Firmware Version 123 ).
Specifying the Active Chip

To change the active chip (that is, the one that the system runs from), proceed as follows:
Note: If the Controller is turned off and on again, the chip containing the later firmware version is set
active, and its firmware loaded.

2. Select Commands > Firmware Commands then either:

Restart Using Chip 1 Version.
Restart Using Chip 2 Version.
3. Click OK to initiate the procedure.
For the Controller to change from one chip to the other, it must shut down momentarily. When the Controller comes
back online, it runs in the chip specified. This action is verified in the Transaction Manager (see Configuring GMS -
Administrator Guide, Using the Transaction Manager).

Device Firmware
Pacom 1064 and 1076 Card Reader Interfaces (CRI) and 1068 I/O also support firmware upgrades.
Note: For 1064 firmware upgrade capability, it must use a PIC18F252 chip and firmware version 4.07 or
later.
Checking Device Firmware Version

To view device firmware version and related information, proceed as follows:
1. If the Controller is online, connect to it through a monitoring PC. If the Controller is not online, connect to it
locally using a diagnostic cable (see Connecting to GMS 12 ).
3. Click Device Info in the left side of the Controller dialog box to display the various device options. Click an
option to display the list of devices in a table. Columns in the table represent various device information
including the firmware version.
Note: The Controller requires firmware version 5.00 or later for this feature to be available.
Downloading Firmware to 1064/1076/1068 Devices

The 1064, 1076 Card Reader Interfaces and 1068 EOL device support firmware upgrades. When upgrading firmware,
if a compatible device is detected by the Controller, that particular device goes offline, the firmware is downloaded to
it, then is comes back online. The Controller will then upgrade the next device of type until all compatible devices are
upgraded. Any incompatible devices are skipped. If a device is not configured in the Controller, it will still be
upgraded with the new firmware, assuming it is compatible.
Caution: The devices will not report any messages when downloading firmware.
To upgrade device firmware, proceed as follows:

1. Follow the procedure in Downloading Firmware to Controllers 123 . Ensure that 1064/1068/1076/8303 is
selected in the Target list, and the device firmware file is selected in the Select File to Download list.
2. Click OK.
Note: The device firmware is held temporarily in the Controller memory. If the Controller is reset, the
firmware is lost and will have to be downloaded again.
After the firmware has downloaded to the Controller (a confirmation dialog box is displayed), it automatically
downloads the firmware to the devices. Once the device receives the new firmware, it restarts. If the device is not
configured in the Controller, then the Transaction Manager Offline/Online messages will not appear.

Error Messages
The error message "Operation aborted" is displayed when the Controller cannot communicate with a device while
performing a firmware download. The message is displayed if the device goes offline (for example, power
failure), or there is no activity between the Controller and the device for 10 minutes.
The error message "Software version error" is displayed if the device firmware is corrupted. This may happen if
the device goes offline (for example, power failure) during the download. On the next startup, the error message
is displayed. The device will come online, but may not operate correctly. Download the device firmware again.

Chapter 3
Configuring Hardware Devices
and Alarm Functions
129
Remote alarm panel (RAP) configurations represents to the alarm system functions of a Controller. Alarm functions
are different from access control functions. Access control involves identifying each individual user and authorizing or
denying access, for example, securing areas, doors, or elevator floors. Commonly, the alarm system is generally
deactivated when the first user enters the area and places the system into Day mode.
Although the alarm system and the access control system closely interact, they are considered separate functions and
are therefore configured separately.
See the following topics:
Configuring Alarm Users 131 .
Configuring Keypads and Device Hardware 130 .
Contact ID and SIA Event Codes 195 .
Configuring Input Point Groups 151 .
Configuring Alarm Areas 172 .
Configuring General Alarm System Parameters 163 .
Configuring Alarm System Flags 167 .
Configuring Alarm Area Access 175 (operational hours).
Creating Event Drivers and Macros 183 .
130 | Chapter 3 - Configuring Hardware Devices and Alarm Functions

Configuring Alarm Users Types

Alarm users represent personnel that are authorized to interact with the alarm system. For example, to access
different areas within the premises at certain times, switch alarm system modes and respond to alarms. This works in
conjunction with point configuration options for isolation (see Configuring Input and Output Points 142 ). For example,
when an alarm user of "Cleaner" type logs on to the system, points that are set to be isolated for this user type will
isolate, enabling the cleaner to access relevant parts of the premises without triggering alarms.
Alarm users are authenticated by the system using unique alarm user type ID numbers and personal identification
numbers (PIN). This makes managing how users interact with the system by a grouping, rather than individual
settings on a per user basis. Access is day and time-of-day based also, meaning that users are generally not able to
access the premises outside of these settings (see Configuring Alarm Area Access 175 ).
Depending on the Controller alarm user PIN setting, you can have up to either 66 or 99 alarm users (see Configuring
Alarm Panel Types 97 ). Alarm users can be configure at any time from GMS or directly from a keypad. Any changes
made at keypads are downloaded to the Controller.
Available alarm user types are:
Staff Type 1 to 4 - Programmable access and operational privileges used by general staff. Four types are
available for allocating different settings. Staff type alarm users generally have access to the alarm system for
mode changing, responding to alarms etc.
Guard - Limits access to programmed times and to points isolated for Guard type alarm users.
Engineer - Used by Pacom service technicians for maintenance and testing, and isolates all points. Available in
Day mode only.
ATM Service/Maint - Limits access to programmed times and to points isolated for service access. This alarm
user type can be given access to any points.
ATM - Limits access to programmed times and to points isolated for ATM type alarm users.
ATM Type 1 - Not used.
ATM Type 2 - Not used.
Cleaner - Limits access to programmed times and to points isolated for Cleaner type alarm users.
Cleaner Type 2 - Limits access to programmed times and to points isolated for Cleaner type alarm users,
where they are required to swipe an access card and enter a PIN.
Auxiliary 1 - Limits access to programmed times and to points isolated for Aux1 type alarm users. Can be
renamed and is used mainly to provide limited building access, for example, a meeting room.
Auxiliary 2 - Limits access to programmed times and to points isolated for Aux2 type alarm users. Can be
renamed and is used mainly to provide limited building access, for example, a meeting room.
Duress - Used by staff when under threat, or other unusual circumstance, to discretely notify the system with a
"duress alarm", without any obvious signs to an observer. Allows access to any alarm area controlled by the
keypad and at any time.
No PIN Defined - Disables the current alarm user.
Configuring Alarm User ID Types

To configure a User ID type, proceed as follows:
2. Upload the current hardware and alarm parameter configuration (see Uploading Hardware Configuration and
Associated Alarm Parameters 134 ).
3. In the Controller dialog box, select Alarm > Alarm Users. The Configuration for User ID dialog box opens.
Chapter 3 - Configuring Hardware Devices and Alarm Functions | 131

4. Enter parameters for the user ID type as required according to the following table.
Note: ATM Access, PIN Management, Test Mode, Allow Camera Management, Alarm Cancel,
Isolate and Late Work options are available only to user Staff Type ID 1 to 4.
User ID Select a user ID type number by clicking or , or by typing the number in
the adjacent and clicking User ID.
User Name Enter the user name (max. 20 characters)
User PIN Enter a 4 or 8 digit PIN.
Note: When this dialog box is accessed, viewing and/or editing alarm
user PINs is dependent on the logged on users's privileges. This
dialog box is not available using the "GMS Config" application,
however, editing of the PIN (not viewing) may be available from the
Operator Setup dialog box.
ID Type Select a user ID type is selected from the list. Some options change
depending on the type you select.
ID Options Click to open the Options for Staff ID dialog box, where you can apply a
range of management functions to the user ID type (see Setting Management
Options for Staff Type Alarm Users 132 ).
Note: This option is available only for Staff Type 1 - 4 user ID types.
Allow Entry Outside Enable to allow users access to the building after the Late Work time setting
Hours (see Configuring Alarm Area Access 175 ).
Can log On to All Areas Enable to allow users to unset/set all assigned areas when unsetting their
first area.
Allow Access Control Not used.
Allow Camera Enable to allow users to access camera management functions from the
Management keypad.
Note: that this option applies to film cameras only, not CCTV
cameras.
Allow Point Isolation Enable to allow users to isolate points in alarm. Isolating a point effectively
turns it off and stops any reporting or functionality.
5. Click OK to close the dialog box and download changes to the Controller.
Setting Management Options for Staff Type Alarm Users

Further options are available to Staff Type alarm users. This allows for the configuration of different management
levels. You set the options on an area by area basis.

To configure the User ID options, proceed as follows:

1. Open the Configuration for User ID dialog box (see Configuring Alarm User ID Types 131 ).
2. From the ID Type list, select a Staff Type ID to modify.
3. Click ID Options. The Options for Staff ID dialog box opens.
4. Enter parameters for the Staff Type ID user type as required according to the following table.
ATM Access Enable to allow staff members to log on to the area using an ATM user ID type
to isolate ATM areas.
PIN Management Enable to allow staff members to change the PINs of all users through the
keypad Management mode.
Test Mode Enable to allow staff members to activate Test mode.
Single Area Log On Tied to the Linked to setting in area configuration (see Configuring Alarm
Areas 172 ). When the user logs on, if Can Log On to All Areas is disabled,
then the only areas affected are the linked areas.
Alarm cancel Enable to allow staff members to cancel alarms using the cancel softkey from
the menu mode.
Isolate Enable to allow staff members to isolate alarm points from the keypad Menu
mode.
Late Work Enable to allow staff members to select Late Work from the keypad to extend
staff access from the Staff Exit time (default) to the Latest Staff Exit time
(see Configuring Alarm Area Access 175 ). The premises is put in Night mode
after this time. If Late Work is selected twice at the keypad, access is granted
all night (24hrs).
Change Mode Enable to allow users to change the alarm system from Day mode to
Restricted/Night modes, or from Restricted/Night modes to Day mode.
Select All (large button) Click to enable all options for all areas.
Select All (small button) Click to enable all options for a single area.
Clear All (large button) Click to disable all options for all areas.
Clear All (small button) Click to disable all options for a single area.
5. Click OK to close the dialog box and save changes.

Configuring Keypads and Device Hardware

Each Controller requires information about the alarm inputs and outputs connected to the system. Inputs and outputs
are configured from the Controller dialog box. The hardware configuration display is also commonly referred to as the
"device map" or "I/O device map". The icons on the device map are referred to as I/O items. However, the physical
inputs and outputs are referred to as I/O "points".
Each I/O item must be configured with a descriptive name and a response action to perform, or output to activate (if
any), in the event an input triggers an alarm condition.
For more information, see Configuring Input and Output Points 142 .
Once the I/O points are configured, GMS downloads their parameters to the Controller. GMS does not store a local
copy of the parameters. If the parameters require alteration, GMS uploads them from the Controller, and after
alteration, downloads them back again.
The Controller stores I/O configuration parameters in a portion of non-volatile memory. The memory available for
storage of I/O parameters supports up to 64 I/O items on the device map. In most circumstances this enables the
Controller to control up to 256 inputs and 64 outputs.
The I/O configuration supports six different device types:
Input.
Output.
Film Camera.
CCTV Camera.
Analog Input.
Pulse Counter.
Uploading Hardware Configuration and Associated Alarm

Parameters
To upload and display a Controller hardware configuration and their associated alarm parameters, proceed as follows.
2. In the Controller dialog box, select Alarm > Configure > Hardware. A graphical representation of the hardware
configuration is displayed in the dialog box - this is the "device map", showing the various pieces of hardware
(keypads, I/O devices, etc) attached to the Controller. The alarm parameters for each device are also uploaded to
GMS.
The device map is divided into three columns:
Keypads 135 .
Local Devices 135 .
Remote Devices 135 .
The following example device map shows a Pacom 1058 Controller with a range of attached hardware.

Keypads
All keypads display on the left of the device map. Keypads do not count towards the 64 total I/O items. The areas
controlled by keypads are represented as colored squares. By default, all Controllers are configured with two
keypads:
Pacom 1061.
Pacom 1062.
Keypads that appear on the device map initially contain default parameters. This allows a keypad, that is set to
default, to communicate with an offline Controller without requiring any configuration. The keypad is then used to
configure the Controller to establish communications with a remote GMS terminal, from where further configuration is
performed. For further information regarding initial configuration of a Controller using a keypad, Using a Keypad for
Basic Configuration 17 .
Local Devices
Local devices display in center of the device map. These include inputs and outputs, and the Controller itself. Local
devices are those that connect directly to the Controller PCB or to an expansion card mounted on the PCB.
Remote Devices
Remote devices display on the right of the device map. Remote devices are those that connect to the Controller
RS485 device line. For example, 1065 16 I/O expansion modules, 1064 or 1076 reader interfaces, wireless inputs,
etc.
There is not a requirement for the input and output points to be wired consecutively, although wiring them
consecutively does simplify the configuration. Extra entries must be added to the configuration for each group of
consecutively wired inputs or outputs. A Controller has memory to store a maximum of 32 device entries (excluding
keypads). This can become a limiting factor if this has not been taken into account when the system was designed
and installed.
Managing Connected Hardware

After you have uploaded the Controller hardware information into GMS you can use the Controller dialog box to
manage the devices. For example, to add and configure a device.
Adding Keypads
To add a keypad to the device map, proceed as follows:
Associated Alarm Parameters 134 ). By default, all Controllers are configured with two keypads - a Pacom 1061
and Pacom 1062. If the required keypad(s) is displayed on screen, delete any keypads not required (see
Deleting Devices 140 ).
3. To add a keypad, right-click a blank area of the device map and select Add Keypad from the context menu.
The Configuration (for Keypad) dialog box opens. The table below outlines the parameters available in the
Configuration dialog box.

Keypad Type Select the type of device that is to be configured from the list:
Undefined - Not in use.
Pacom 1028 (Main Keypad) - Use a Pacom 1028 (obsolete).
Pacom 8101/1062 (Remote Keypad) - Use a 8101/1062 keypad without
an LCD screen.
Pacom 1061 (Main Keypad) - Use a 1061 keypad with an LCD screen.
Pacom 1061 (Remote Keypad) - Use a 1061 keypad without an LCD
screen.
Mosler RSD - Use a Mosler RSD keypad (obsolete).
Pacom 8101/1062 (Main Keypad ) - Use a 8101/1062 keypad with an
LCD screen.
Pacom 1061 (Queuing Type ) - Use a 1061 keypad without an LCD
screen.
Device Address For local alarms and outputs leave as default (1). The next available device
address is automatically shown.
If the Controller has multiple device lines, each device line is allocated a range
of 32 devices (1-32, 33-64, 65-96 or 97-128). A valid device address can be
any number from 1-128. When entering the Device Address the highest
address in the previous range must be added to the address that was
programmed into the device, that is:
For Address range 1-32, add 0.
For example, if a device is programmed with device address 3, and it is
connected to a device line that has been allocated the 65-96 range of
addresses, the Device Address should be entered as 67 (3 + 64). The device
range and physical device address will appear in the shaded fields below the
Device Address field.
For Areas Select the areas that the keypad will control.
Note: Pacom 8001 Controllers support up to 32 areas. Other Pacom

Controllers support up to eight areas.
Return to Idle Causes the keypad to switch to the first configured area after the Idle Time
for Display setting has expired (see Configuring General Alarm System
Parameters 163 ).
Enable card access Enable to allow valid user card swipes to unlock the keypad. This feature
operation allows valid users to access keypad functionality without having to use a PIN
(see Configuring Card Activated Keypad Access 155 ).
Update LEDs for Alarms Appears in place of the Return to Idle setting for keypads that do not do not
have a LCD screen. A specific LED will flash when an alarm occurs in a
particular area.
Disable During Day Disables the keypad during the hours set for Day mode operation. This also
Mode allows the welcome message to be displayed (if configured).
LEDs Map Pacom keypads have eight LEDs. Each LED represents an area that the keypad
controls. The keypad LEDs show users which areas are in Day mode (green),
Night mode (amber) or flash red (alarm during Night mode).
For Pacom 8001 Controllers that support up to 32 areas, you can define which
LEDs represent areas from nine onwards (see Setting Keypad Area Mapping
136 ).
Setting Keypad Area LED Mapping

Pacom 8001 Controllers support up to 32 areas, however, keypads have eight LEDs. This means that each possible
area from area nine onwards cannot have an individual LED to represent it. In such cases, you can map the existing
eight LEDs to different areas as required.
To set keypad area LED mapping, proceed as follows:
1. In the Configuration for Keypad dialog box, LEDs Map region, click a button for the LED to configure. The LED
Area Mapping for Keypad dialog box for the LED opens.

2. Enable the checkbox for each area to be represented by the selected LED. In the example above, LED 1 will
represent areas 1, 9 and 17.
3. Click OK.
Now if, for example, the alarm system is in Night mode (amber color LEDs) and area 9 goes into alarm, LED 1 will
flash red.
Setting Mandatory User PIN Changing with 1061/1062 Keypads

For added security, it is possible to have the system force users to change their PIN after a set period of time, using
an enrolment reader. For example, allowing user PINs to be valid for a period of 90 days, after which that PIN is
rejected by the system. During the seven days prior to PIN cancellation, keypads will display a message to users as
they log on that their PIN requires changing. A special keypad is configured as an enrolment reader, where users can
create and confirm new PINs.
To set mandatory user PIN changing, proceed as follows:
1. Create a new reader (see Configuring Readers 204 ) using the Configuration for Reader dialog box and set the
following parameters in the Reader tab:
Set the Reader Type to Pacom 1061 Type or Pacom 1062 CRI Type as required.
Note: For 1061 keypads, which do not have a built-in RF antenna, a reader is required to be attached to
it.
Set the Reader Category to Enrolment reader. The keypad displays "RENEW PIN SWIPE CARD".
2. Once the keypad has been set up as an enrolment reader, activate the PIN validity function and define the
number of days that a user PIN is valid for. On the enrolment reader keypad:
a. Press the MENU key. The display shows "[ENROL MENU] 1. PIN enrolment".
b. Press the ENT key. The display shows "Enable PIN Enrol".
c. Press the 1 key to activate the function (press 0 to deactivate it).
d. Press ENT.
e. Press MENU twice. The display shows "[ENROL MENU] 2. Set PIN Expiry".
f. Press ENT. The display shows "Set PIN Expiry".
g. Enter the number of days (1 to 90) for PIN validity.
h. Press ENT.
Caution: Access to the PIN enrolment menus on the keypad is not secure as it does not require a log on.
Adding Devices
To add a device to the device map, proceed as follows:
3. To add a device, right-click a blank area of the device map and select Add Device from the context menu. The
Device Configuration dialog box opens. The table below outlines the parameters available in the Device
Configuration dialog box.

Device Type Select the type of device that is to be configured. For device type descriptions
see the Device Types table 138 .
Device Address For local alarms and outputs leave as default (1). The next available device
address is automatically shown.
If the Controller has multiple device lines each device line is allocated a range
of 32 devices (1-32, 33-64, 65-96 or 97-128). A valid device address can be
any number from 1-128. When entering the Device Address the highest
address in the previous range must be added to the address that was
programmed into the device, that is:
For example, if a device is programmed with device address 3, and it is
connected to a device line that has been allocated the 65-96 range of
addresses, the Device Address should be entered as 67 (3 + 64). The device
range and physical device address will appear in the shaded fields below the
Device Address field.
Port Number This appears only when 3rd Party Device is selected in Device Type - the
Device Address setting will change to Port Number. Select the port that the
third-party device is connected to.
Start Point No. on Is the point at which the input/output devices are physically wired to the
Device: boards (For example, 1st point is wired to the IN 6 Input on Witness).
Point Type Defines the device hardware to the Controller. The different device types on
each device must usually be added separately. Exception: Witness inputs and
CCTV Cameras. Options are:
Input - Defines the device as providing input signals.
Output - Defines the device as providing output signals.
Film Camera - Defines the device specifically as a film camera controller.
CCTV Camera - Defines the device specifically as a CCTV camera.
Analog Input - Defines the device as providing analog input signals.
Pulse Counter - Defines the device as providing input signals for a pulse
counter.
Report Point Start Is the number of the first device wired, as it is recognized by the system. For
Address: example, call the first device on the PCB input No 17. The remaining points are
numbered sequentially starting from this number.
No. of Report Points The number of physically wired inputs, outputs or CCTV cameras on the device.
For example, 7 devices connected (devices must be wired consecutively).
4. Select the appropriate device type from the Device Type list. See the table below for device type options for
8001, 1057 and 1058 Controllers.
Device Type Description

Local Alarm Card Pacom 1050-004, 16 Input Mezzanine card mounted on the Controller PCB -
this device appears in the center column.
Note: For 8001 Controllers, the Point Type setting can be Input or
Analog Input.
Local Output Card Pacom 1050-003, 8 Output Mezzanine card mounted on the Controller PCB -
this device appears in the center column.

Device Type Description

16IO (PACOM 1030) Pacom Remote I/O expansion card. This card has been superseded by the
Pacom 1065.
Camera Controller Camera controller with four inputs.
Inovonics To program a set of sequentially programmed Inovonics transmitters. Add 1 to
the IDM and IDL programmed into the first transmitter and enter them as the
IDM and IDL. Enter the number of transmitters used in the Number of Report
Points setting. The wireless inputs are numbered in the system sequentially,
starting from the Report Point Start Address setting. Once configured,
Inovonics inputs are treated like any other input and can be used to trigger
alarms, outputs, macros, etc (see Configuring Inovonics Devices 158 ).
3rd Party Device Third-party device with up to 256 inputs. For example, a Digital Video Recorder
(DVR).
PACOM 1061 Pacom 40 character x 2-line, 1061 LCD keypad.
PACOM 1065 Use this device type to configure a Pacom 1065 16I/O card. It has 16 onboard
inputs and 4 onboard outputs. The 1065 also has two mezzanine card slots
which can accommodate any combination of the 16 input and 8 output cards.
Inputs and outputs must be added to the configuration in separate entries,
however, onboard points, and points connected to mezzanine cards are
combined and added in a single entry.
Input and output points must be wired consecutively from the Start Point No.
on Device setting. If the No. of Report Points setting exceeds the number
available on the PCB, the system will assume that an expansion card has been
installed. See Device Configuration Parameters 138 .
Local Alarms on Use this device type for input points connected directly to the onboard inputs
1065A/1058/Witness of the 1065A, 1058, 1058A or Witness.
Local Outputs/CCTV on Use this device type for output points connected directly to the onboard
1065A/1058/Witness outputs of 1065A, 1058, 1058A or Witness Controllers, plus up to eight CCTV
cameras which can be triggered for recording to the Witness hard drive or
display on its local monitor output.
PACOM 1064 (CRI) Use this device type to configure any spare input or outputs on a Pacom 1064
that is being used as a Card Reader Interface (CRI).
PACOM 1064 I/O Use this device type to configure the inputs or outputs on a Pacom 1064 that is
being used in I/O mode (6 inputs and 4 outputs).
IRIS Panel Use this device type to configure the inputs or outputs on an Iris I/O panel.
PACOM 8101/1062 Pacom 16-character x 2-line LCD keypad.
Pacom Witness Use this device type to configure a Pacom Witness CCTV recording and
management device.
PACOM 1067/1076 Pacom 1076 (and 1067) dual card reader interface. Use this device type to
configure spare inputs or output.
PACOM 1068 I/O Use this device type to configure a Pacom 1068 intelligent end of line card (2
inputs and 1 output).
Chubb I/O Card Not used at present.
Pacom 1074 Dialler/ Use this device type to configure up to 4 inputs and 1 output on a Pacom
Leased Line Unit 1074.
Pacom Vault Controller Use this device type to configure a Pacom vault controller device.
PACOM 1076 I/O Use this device type to configure the inputs or outputs on a Pacom 1076 I/O (8
inputs and 4 outputs).
OnSafe DVR I/O Use this device type to configure the inputs or outputs on an OnSafe DVR I/O.
PACOM 8501 Use this device type to configure the inputs or outputs on a Pacom 8501 I/O
(16 inputs and 5 outputs, with up to 32 inputs and 13 outputs using
expansion).
SART Card Use this device type to configure the inputs or outputs on a Pacom SART card
(up to 60 inputs and 60 outputs).
5. Assign an address to the selected device. It should be noted that when you select from the Device Type list,
GMS automatically enters an address in the Device Address field. However, the address can be specified by the
operator.
6. Enter the start point number. The start point is the first physical point on the device where an input or output is
wired.
7. Specify the Point Type setting. The options in the Point Type list vary depending on the type of device being
configured.

8. In the Report Point Start Address field, enter a logical address for the first physical point on the device. This
is the address the system uses to identify the point. For example, if a start point address of 4 is entered, and
the number 1 is entered for the report point start number, the system will see point number 1 on the device, as
point 4.
9. In the No. of Report Points field, enter the number of points used. For example, if all input points on a Pacom
1065 are to be used, the number entered would be 16. Furthermore, if a Pacom 1050 mezzanine expansion
module, with 16 input points, is added to the 1065, and all points on the module were required, the number of
report points would be 32. Because a 1065 has only 16 input points, when the number of report points specified
exceeds 16, GMS intuitively assumes a 1050 expansion module is present.
10. Click OK to complete the procedure. The Device Configuration dialog box closes and the new device displays on
the device map.
Note: For devices that have both input and output points (for example, 1064 I/O), you can use both point
types. To do this, you need to add the device twice, using the same device address, however, assign one
instance with an input Point Type setting and the other with an output Point Type setting.
Deleting Devices
To delete a device from the device map, proceed as follows:
Note: Any device, except the Controller, can be deleted.
3. Right-click the device you want to remove and select Delete Device from the context menu. A prompt will
confirm if you want to delete the device.
Viewing Vault Controller Status

The Controller dialog box has facilities to view the status of configured Pacom vault controller devices. Information
includes the current status of the device plus a range of device settings. This facility makes it easier to manage and
monitor vault controllers.
2. Select Vault Controllers from the list on the left-hand side. The vault controller status screen appears. If there
are several vault controllers being monitored, use and to switch between them.

Auto-Configuring Connected Devices

Pacom Controller 1057/1058 firmware version 5.00 and 8001 firmware version 1.02 and later offers device auto-
configuration. Connected devices are automatically detected and their basic configuration is downloaded to the
Controller. This helps to reduce setup time and effort.
Auto-Configuration of Input and Output Devices

When a keypad (1061, 1062, or 8000 series) is wired to the Controller RS485 device line, the Controller automatically
detects the device when it powers up. It is allocated the first available keypad slot, registered to the list of keypads
and is assigned to area 1.
When an I/O device (1064, 1065, 1067, 1076IO, or PX8) is wired onto the Controller RS485 device line, the
Controller automatically detects the device when it powers up. It is allocated the first available device address and
added to the I/O device list.
The number of inputs and outputs that the Controller automatically registers depends on the connected detected
device, as follows:
1064 - 6 input, 4 outputs.
1065 - 16 inputs, 4 outputs.
1076 - 8 inputs, 4 outputs.
1068 - 2 inputs, 1 output.
PX8IO - 8 inputs, 2 outputs.
Auto-Configuration of Access Control Devices

When an access control device (1064, 1076, 1076CRI or 1062 card reader) is wired to the Controller RS485 device
line, the Controller automatically detects the device when it powers up. It is allocated the first available device
address and registered to the list of readers.
If the device line already has a similar access control device set up, its configuration is copied and used for the new
device. If it is the first access control device, then the basic settings are downloaded to the Controller.
The configuration settings for all attached devices can be customized as required.

Configuring Input and Output Points

Once you have added all inputs and output hardware to the device map, you will need to configure the individual
inputs points for them to activate alarm messages and outputs. It is recommended that you configure outputs points
first (see Configuring Device Output Points 142 ). This is because it is easier to assign outputs as activations during the
process of configuring inputs.
Input points are generally detection devices attached to the Controller. When they signal the Controller to represent
an alarm or system condition, the Controller responds by activating devices connected to its output points.
Configuring Device Output Points

To configure output points and assigning vocabs to them, proceed as follows:
Note: To make it easier to configure the input points, it is recommended that you configure the output
points first. This makes it easier to identify the appropriate output to assign when configuring inputs.
3. On the device map, click the PCB image for the output device. A graphic of the PCB displays in a new dialog box.
The output points display as a purple and white icons.
4. Double-click an output point to assigned a vocab to it. The Output Configuration dialog box opens. Configure the
output according to the following sections.
Output No. The point number of the selected output.
Vocab Select an appropriate vocab description for the output type. For information
regarding I/O point vocabs and customizing them, see Configuring Point
Description Vocabs 153 .
Previous / Next Use to cycle through configured outputs.
Device, Address and These are information only fields (greyed out). They detail the device type, its
Point address and the point number that the output is connected to.
5. Select an appropriate description for each output from the Vocab list, clicking Next to select the next output.
6. Click OK to close the dialog box when you have configured all outputs.
Configuring Device Input Points

To configure input points and assign vocabs to them, proceed as follows:
3. On the device map, click the PCB image for the input device. A graphic of the PCB displays in a new dialog box.
The input points display as a red and white icons.
4. Double-click an input point to configure it. The Configuration for Input dialog box opens.
5. In the Input No. field specify an input number to configure and click Input No.. By default, the selected input
number (step 4) displays in the Input No. field. Alternatively, use Prev and Next to cycle through the available
inputs.
6. In the Configuration for Input dialog box, enter the required parameters.
7. Click OK when you have configured all inputs.

Input No. The number of the input as it is recognized in the system. Specify the required
input number and click Input No..
Area No. Specify the area number to assign the point to (see Configuring Alarm Areas
172 ).
Note: The number of areas available depends on the Controller type.
Input Vocab
Input Vocab Click to view a list of available vocabs. Click a list entry to select it.
Standard Select to use a vocab from the pre-defined list stored in GMS.
Note: This option is available when the Controller is set to use pre-
defined vocabs (see Configuring Alarm System Flags 167 ).
User Defined Select to create a custom vocab manually by entering it into the Input Vocab
list - up to six can be defined. When creating user-defined vocabs in this way,
any point also set up to the same vocab entry (the indexed position of the
vocab in the list) also changes. For example, the first user-defined entry will
apply to all points that also use the first vocab entry in the list (see Configuring
Point Description Vocabs 153 ).
Note: Each entry can be a maximum of 20 characters.

This option is available when the Controller is set to use pre-defined
vocabs (see Configuring Alarm System Flags 167 ).
Edit Pick List Click to view the custom vocab list. From the list, use the Windows clipboard to
copy (CTRL + C) the vocab text and paste it (CTRL + V) into the Input Vocab
list (see Configuring Point Description Vocabs 153 ).
Note: This option is available when the Controller is set to use custom
vocabs (see Configuring Alarm System Flags 167 ).
Notify Alarms Determines whether or not the point reports any alarms to the monitoring
system.
Report Trouble Alarms Selects whether or not the point reports trouble (open and short circuit)
as Normal conditions. Trouble conditions can be reported only if the input point has been
terminated with a pair of input resistors.
Ask Outputs
Outputs Click to open the Ouput Activations for Input dialog box, where you can set up
an output to be switched by the input activation (see Step 9, below).
Class
Note: The Ask Outputs option must be enabled for this setting to
become available.
Adv Click to open a dialog box, where you can

Note: The Ask Outputs option must be enabled for this setting to
become available.
Point Isolated During

Night, Restricted, Day, Determines which alarm system modes that the point is active in. Isolation
Cleaner Mode, ATM refers to the system ignoring signals from the point. For example, enabling the
Mode, Guard Access, Day option will isolate the point when the system is in Day mode; enabling the
Aux1 Mode, Aux2 Mode Cleaner Mode option isolates the point when a Cleaner type alarm user logs
on to the system. Enable the mode options as required.
Delay Options
No Delay Select for the point to generate an alarm as soon as it is activated.
Primary Delay Select for the point to apply the primary delay timer (entry timer) when it is
activated. An alarm is reported if a user does not access the alarm system from
a keypad before the timer expires. This is generally used for an alarm point at
an entry.
Secondary Delay Walk through point send a full alarm if activated before the primary delay point
(normal).
Pending Delay These points are active in Day mode only. This setting is also tied to the
Pending Delay Count and False Alarm Timeout settings (see Configuring
Alarm Areas 172 ).
Test
No Test Select to disable any testing of the point.
Self Test While Inactive Select to test devices, such as PIRs, during normal office hours. When selected,
the alarm point is expected to be triggered at least once during Day mode as
staff conduct their normal business activities. If the alarm point has not been
triggered at all during the test period, the point is marked as being faulty.
Self Test Select to test points that have a self-test facility, such as seismic detectors,
which use a small vibrator to test the sensor. The output used to activate the
self test facility for the sensor is specified in the Output No. field. Self test of
these points can be selected on entry/exit of different modes. The output is
automatically activated on entry to test mode.
Test Day Select for the point has to be triggered on the day set in the Test Day field.
The Test Day field settings are: Monday = 1, Tuesday = 2, Wednesday = 3,
Thursday = 4, Friday = 5.
Point Category
Point Category Lists various categories to classify activity from the point. In cases of reporting
to third-party receivers using Contact ID or SIA formats, these options can
make messages more specific. Options are:
Normal Alarm - For all other devices that do not fit any of the following
categories.
Tamper/24 Hr - For all tamper points or points that are live 24 hr/day
(sonalert).
Note: Latched tamper alarms in EN50131 compliant installations can

be reset as per normal reset operations.
PIR Point - For all PIRs other than entry route devices.
PIR Perimeter Point - For all PIRs on the entry/exit route. Follows Anti
False Alarm setup.
Perimeter Point - For all entry/exit points.
Environment Point - This point classification passes through the point
incident without causing the panel to activate.
Final Set Point - For devices such as push button sets.
Alarm Cancel Point - This point classification is used to reset alarm points
(alternative to the keypad).
Vault Point - For all vault protection except vibration. These points may
require group isolation (these are used in association with a Vault Area) only.
Vibration Point - For all vibration points that may require group isolation.

Shunt Point - This selects this point as a shunting point. If selected the
point shunts the next point numerically. Upon activation, that is, using a
shunt lock, a message is transmitted to the control room as alarm point (x).
Where x is the point being shunted when the shunt is restored, then the
restore signal is transmitted.
Lockset/Unset Point - This point, if selected, sets and un-sets the
corresponding area. No primary delay points are required and all points
within that area should be of no delay (instant). If the area has a restricted
area as well as a full day mode, on un-setting the system it will go to
restricted mode and require the user to un-set to full day mode.
Fire Point - These points cannot be isolated. They also enable a set of sub-
categories. These sub-categories allow the selection of further types of fire
alarms to report as follows:
No Special Sub-category.
Pre-Fire Point.
Fire Fault Point.
Test Key Point. Fire test will generate an alarm entry to the fire test mode,
and will trigger a test period (set in System General Parameters 93 ). Any
normal fire alarms are inhibited while in test mode. Other types are
transmitted.
Raid Point - Not be isolated, and will remain active at all times, including
Engineering mode.
Day Delay Alarm - These points follow the delay rule, whereby if the point
resets within a prescribed period of time, no alarm is transmitted. If the point
stays in alarm past the programmed time, then it transmits an alarm
condition. This flag is also linked to the Sonalert On Day Delay flag which
can set the maximum number of actuations of the day delay alarm before an
alarm is sent during a one day period (see Adding Devices 137 ).
Alarm Confirmation - Attached to the Pending Alarms setting. Activation
of this point by-passes the Pending Alarm Count and False Alarm Count
settings.
Latched Point Enabel for the point to be restored (reset) by an operator before another
activation can be reported.
Point Category 2 Available if Contact ID or SIA are set up in the dialup (Modem or Mezzanine)
port parameters 51 . The options in the list depend on the configuration of the
port priority port and if Assign CID/SIA Event Type is selected in the
Advanced Input Configuration dialog box (see Advanced Input Configuration
Parameters 146 ). If either port is configured to use Contact ID or SIA, then the
menu appears. If both ports are configured, then the settings of the Secondary
Priority port are used.
Point Category Options Select the Contact ID/SIA alarm type that will be sent to the monitoring centre
when this point is in alarm. The options vary depending upon the Point
Category setting, and the alarm type (Contact ID or SIA).
Copy From Copies all attributes of the alarm point entered in the adjacent field to the
current alarm point.
Adv. Config Opens the Advanced Input Configuration dialog box for more alarm point
options.
8. In the Advanced Input Configuration dialog box, enter the required parameters (see Advanced Input
Configuration Parameters 146 ).

Report Day Local Report all alarms during Day mode from this point to a locally connected GMS
machine. Alarms will also be reported to the GMS machine connected to the
master Controller in a peer-to-peer configuration (see the Peer-to-Peer
Configuration Guide).
Report Night Local Report all alarms during Night mode from this point to a locally connected GMS
machine. Alarms will also be reported to the GMS machine connected to the
master Controller in a peer-to-peer configuration (see the Peer-to-Peer
Configuration Guide).
Delay Backup Reporting (Not implemented in this release).
Report Change while Report all messages from the selected point while the point remains inactive/
Inactive isolated.
Report Alarm in Alarms are reported to a Pacom Base Station or a third-party receiver as
Supervisory Mode supervisory messages. Ensure that Supervisory Mode is enabled in the
Message Filters 95 dialog box.
Report Input During When the Controller is in Test mode, the alarm messages will still be reported.
Test Mode
Inverse Polarity for the This will reverse the logic of the input. Normal state is treated as alarm state
Alarm Point and vice-versa. That is, 10K is alarm, and 5K or 20K are normal.
Enable Abort Window Enable the input to utilise the Abort Window Time setting (see Configuring
General Alarm System Parameters 163 ).
Held in Time The input must be active for the time selected before an alarm is generated.
Assign CID/SIA Event Assign a CID/SIA Event Type for this point. The Event Type can be set from
Type the Input Configuration dialog box.
Note: In order to do this the port must be set up for reporting events
in either SIA or Contact ID formats. See Contact ID and SIA Event
Codes. 195
Enable Groups See Configuring Input Point Groups 151 .
9. In the Input Point Configuration dialog box, click Outputs to configure the output activations for each input.
The Output Activations for Input dialog box opens.
10. In the Activate During region, select the appropriate modes in which the alarm output is activated.
11. To activate an output, select it from the Select an output or camera... list and the click Add Activation. The
output and its vocab is added to the Activate list and the Activation Duration dialog box for the selected output
opens.

Activation Lists
When you use the input configuration dialog boxes to set up output activations for various inputs, GMS records the
settings as you make them in what are known as "activation lists". These lists are based on the Point Isolated
during and Activate During mode settings and are available to other inputs with the same settings. Activation list
entries are available from the Programmed Activations region of the Output Activations for Input dialog box. For
example, an input that is active in Restricted mode and activates a range of outputs when it is triggered becomes
available to other inputs that are also active in restricted mode. This makes making common activation settings for
different input points easier.
The following table outlines the parameters available in the Output Activations for Input dialog box.
Activate During Select which alarm system mode the output is active for.
Activate List outputs that are activated when this input is tripped. These selections are made
from the Select an... list below. To edit or delete and activation, select it here first.
Select an output or Located below the Activate field. Lists all configured outputs. Once an output is
camera... selected, click Add Activation. The output is added to the Activate field. When you
add an activation the Activation Duration dialog box opens.
Edit Displays the Activation Duration dialog box for the output selected in the Activate
list.
Delete Removes the selected output from the Activate list.
Delay Count This allows actuation of the outputs in the active list to be used when the delay count
is reached. Used in conjunction with the Pending Delay Count setting in Area
configuration (during unset).
In Area configuration, set Preliminary Delay Count = 2. This means after two
activations of any alarm with the Pending Delay option enabled (set in the Input
Configuration dialog box) an alarm is sent immediately. If there is only one activation
of this type, then the false alarm timeout begins and no alarm is sent until this time
expires (this only occurs in Day mode). This timeout allows the operator time to
cancel the alarm.
When configuring outputs, specify in the Delay Count field the count of Delay
Points Active to trigger the listed outputs.
Programmed List the output activation settings that have previously been applied to other inputs.
Activations
Delete All Lists Clears all entries in all current activation lists.
Delete List Clears all entries in the current activation list. That is, for inputs that share the
current Point Isolated during setting.
Previous List Click to load the last available activation list.
Next List Click to load the next available activation list.
Browse Click to view the activation lists applicable to the input.
Select Click to add the contents of the Programmed Activations list to the Activate list.
The table below outlines the parameters in the Activation Duration dialog box.
Follow Input The output follows the input (on and off with the alarm).
Latched The output changes state until manually reset or a mode change occurs.
Time Enables the Duration time setting. The output changes state for the set time when
activated.
Duration The number of seconds (or minutes if the Activation time in min. option is enabled)
that the output is activated for.
Activation time in Min. Enable for the Duration setting to be in minutes instead of seconds.
Hold-On Delay Enabled The output follows the area parameter for Hold On Delay.
Hold-Off Delay The output follows the area parameter for Hold Off Delay.
Enabled
Capture Pre and Post Available only for CCTV camera activations. Selecting this option enables the capture
Alarm Video of video before and after the event. The amount of video captured that occurred prior
to the alarm activation is configurable.
Set Video to Local Available only for CCTV camera activations and displays video from this channel on
Playback Port the local video out port.
Note: Applies to Pacom Witness DVRs only.
Write vVideo to disk Select to have any video captured by this activation saved to the DVR hard disk drive.

Note: Applies to Pacom Witness DVRs only.
12. Select the appropriate parameters for the output activation duration (see Activation Duration Parameters 147 ).
13. Click OK to close the Activation Duration dialog box and return to the Outputs Activations for Input dialog box.
14. When you have configured all outputs for the selected input, click OK to save all settings and close the Output
Activations for Input dialog box and return to the Configuration for Input dialog box.
15. When you have configured all inputs, click OK to save all settings and close the dialog box.
16. Click Close to exit the PCB graphic dialog box.
17. When you have configured all devices, close the Controller dialog box. A prompt to download the hardware
parameters is displayed. Click Yes to download the settings to the Controller and complete the input point
configuration procedure. The Transaction Manager confirms the download.
Configuring Delayed Alarm Notification Points

In GMS 4.07, it is possible to "delay" alarm notifications to operators based on special conditions. That is, GMS does
not present the event to the operator unless another condition is also met. The feature is generally designed to
reduce "false alarms" and is for use with particular industry requirements (namely, UK and Irish banks).
Using the delayed alarm notification feature enables the system to generate events in GMS based on certain
conditions, rather than an alarm event being generated as a default GMS behavior. This is achieved in conjunction
with the GMS Events Publisher module and message priority settings - alarm points that are to be "delayed" must
initially be configured with an alarm priority setting of "0". Events with priority settings of "0" are sent to the delayed
alarm "listener" (and not to GMS), where depending on settings and other circumstances, they can be "escalated" to
a GMS event that has a priority of greater than "0" (requiring operator notification/action). Escalation occurs when
either of the following conditions are met:
Escalate if confirmed - An alarm is escalated if a confirmation alarm is received within a set amount of time.
For example, a PIR alarm - it should be escalated only if another PIR in the same alarm area generates an
alarm.
Escalate if not cancelled - An alarm is escalated if no cancellation message is received within a set amount of
time. For example, a "Raid alarm" - it should be escalated only if no "Cancel Alarm" message is received
(generated by a user from a keypad, for instance).
Mapping of alarm points, alarm priorities, delay lengths and confirmation points are handled through a configuration
file see Configuring Controllers - Technician Guide, Configuring Delayed Alarm Points.
Note: The GMS Events Publisher must be installed (see GMS Installation Guide).
Sites that are in Suspend mode do not generate events.
Secondary point activations that occur during the original event delay timer will not restart or cancel the
original delay timer.
For more details, refer to the GMS Delayed Alarms Solution Implementation document in the Extras/
DelayedAlarms folder of the GMS installation media.
On startup, the delayed alarm "listener" creates a site range filter based on the sites referenced in the configuration.
The filter is registered with the Events Publisher so that messages generated by "relevant sites" only are sent to the
listener.
Caution: If any configuration rule(s) are changed or new sites are added to the configuration, the listener
must be restarted in order to send an updated site range filter to the Events Publisher.
Before configuring delayed alarm notifications, ensure that the points being used are configured with an alarm
message group that has been given a priority of "0" (see Configuring GMS - Administrator Guide, Configuring Alarm/
Event Message Priorities).
Configuring Points to Use Delayed Alarm Notifications

A configuration file named DelayAlarmConfig.txt and located in the delayed alarm feature installation folder contains
the point information and parameters that control delayed alarm operation. You can edit the operational parameters,
if required, using a text editor, such as Notepad.
Warning: It is vital that the point configuration details are entered exactly, following the format described
below. Errors in configuration may prevent the delayed alarm feature from correct operation or may
possibly prevent GMS from receiving correct alarm notifications.
The delayed alarm configuration file contains a separate line for each point. The parameters are separated by comma
(",") characters. The format is:

AlarmType=DelayedAlarmSpecifier, AlarmGroupPriority=AlarmGroupName, Delay=NumberSeconds,

TriggerType=[AlarmType=TriggerAlarmSpecifier]
AlarmType is the source of the alarm and the state that it needs to be in to send an event to the listener. The
DelayedAlarmSpecifier value can be:
Input SET - Input point going to a SET (active) condition.
Input RESET - Input point going to a RESET (inactive) condition.
Output ON - Output point going to a ON (active) condition.
Output OFF - Output point going to a OFF (inactive) condition.
The DelayedAlarmSpecifier must include the site identification number (Site=) and whether or not a specific
point is targeted (Point=) or any point within a specified alarm area can be used (Area=). For example:
"AlarmType=Input SET, Site=10, Point=3" means when input point 3 in site 10 goes into a SET condition.
"AlarmType=Output ON, Site=10, Area=1" means when any output point in alarm area 1 in site 10 goes into
a ON condition.
AlarmGroupPriority is the alarm type that has the required alarm priority (not "0") that is applied to the event, if it
is escalated. The AlarmGroupName value must be identical to a valid GMS alarm group configuration. For example:
"AlarmGroupPriority=Raid alarm" means that if the alarm is escalated, apply the priority given to the "raid
alarm" alarm message group.
Delay is the length of time (in seconds) to allow for confirmation or cancellation to occur. The NumberSeconds
value can be any integer. For example:
"Delay=100" means allow up to 100 seconds to pass from receving the initial event for a confirmation or
cancel event. If the alarm is confirmed or is not cancelled within 100 seconds, the alarm is discarded.
TriggerType determines if alarm escalation is to occur by confirmation or cancellation. The TriggerType value can
be:
ConfirmedBy - The alarm is escalated if the confirmation conditions are met within the delay timer.
CancelledBy - The alarm is escalated if the cancellation conditions are not met within the delay timer.
There may be any number of TriggerType conditions in the same entry, with each one enclosed by "[" and "]"
characters. The very first condition only should be prefixed with the "ConfirmedBy=" or "CancelledBy="
specifier. For example:
"ConfirmedBy=[ConditionX]" means that the alarm is escalated if ConditionX occurs within the delay timer.
"CancelledBy=[ConditionY][ConditionZ]" means that the alarm is escalated if ConditionY or ConditionZ does
not occur within the delay timer.
AlarmType in the TriggerType section is the source of the confirmation or cancellation condition that is required in
order for the event to be escalated. The TriggerAlarmSpecifier value can be:
Input SET - Input point going to a SET (active) condition.
Input RESET - Input point going to a RESET (inactive) condition.
Output ON - Output point going to a ON (active) condition.
Output OFF - Output point going to a OFF (inactive) condition.
ValidSwipe - Card reader sending a "valid swipe" message.
RAW - Use a custom GMS message, based on function code and optional data bit parameters.
The TriggerAlarmSpecifier must include the site identification number (Site=) and whether or not a specific
point is targeted (Point=) or any point within a specified alarm area can be used (Area=) or, if using the
ValidSwipe condition, a specific reader is targeted (Reader=). When using RAW, a site identification (Site=)
and message function code (FC=) are mandatory requirements. Data bit parameters can also be specified, if
required. For more information, contact Pacom support. For example:
"AlarmType=Output ON, Site=12, Point=30" means when output point 30 in site 12 goes into an ON
condition.
"AlarmType=ValidSwipe, Site=10, Reader=1" means when reader 1 in site 10 sends a "valid card" message.
"AlarmType=RAW, Site=12, FC=8, D3=77, D8=1" means a message from site 12 using function code 8 and
containing a value of 77 for data bit 3 and a value of 1 for data bit 8.
The following example sets up input point 5 in site 6 to notify GMS of an alarm using the priority set for "raid alarm"
when the point is in a SET state and is confirmed within eight seconds by input point 1 in site 1 going into a RESET
state or any input point in alarm area 3 going into a SET state.
AlarmType=Input SET, Site=5, Point=6, AlarmGroupPriority=Raid alarm, Delay=8, ConfirmedBy=
[AlarmType=Input RESET, Site=1, Point=1][AlarmType=Input SET, Site=1, Area=3]

The following example sets up input point 25 in site 36 to notify GMS of an alarm using the priority set for "panic
alarm" when the point is in a SET state and is not cancelled within 30 seconds by output point 10 in site 36 or output
point 20 in site 36 going into a ON state, or card reader 1 in site 36 sending a "valid swipe" message.
AlarmType=Input SET, Site=36, Point=25, AlarmGroupPriority=Panic alarm, Delay=30, CancelledBy=
[AlarmType=Output ON, Site=36, Point=10][AlarmType=Output ON, Site=36, Point=20]
[AlarmType=ValidSwipe, Site=36, Reader=1]

Configuring Input Point Groups

You can allocate any device input points (see Configuring Device Input Points 142 ) within an area (see Configuring
Alarm Areas 172 ) into groups and sub-groups. Grouping input points allows you to apply rules for the operation and
reporting of alarms in the group. You can also assign sub-groups, which are point groups within an input point group.
For example, input points from a vault area are appropriate to being grouped. Some of the input points, such as
seismic detectors and PIRs, may be appropriate to being sub-grouped to the vault input point group. You can then
use the input point groups/subgroups to prevent any more than one sensor type from being isolated, or for full
alarms to be triggered only if a point is active for a minimum amount of time. These kinds of facilities help prevent
isolating too many input points and also reduce the possibility of false alarms.
Input point groups are structured as follows:
Area 1
Input Point Group 1
Subgroup 1
Subgroup 2
Input Point Group 2
Input Point Group 3
Area 2
... and so on.
Note: Pacom 1057/1058 Controllers can support up to eight areas, 8001 Controllers up to 32 areas. Each
area can support up to 32 input point groups. Each input point group can support up to eight subgroups.
Adding Device Inputs to an Input Point Group

To add device input points to create an input point group, proceed as follows:
3. On the device map, click the PCB image for the input device. A graphic of the PCB displays in a new dialog box.
4. Double-click an input point to open the Configuration for Input dialog box for it. Make sure that the Area No.
setting is the correct area for the input point.
5. Click Adv Config. The Advanced Input Configuration dialog box opens.
6. Select the Enable Groups option.
Note: If the No Delay option is enabled for the point, the area the input point group belongs to will apply
its False Alarm Timeout setting to it.
7. In the Point Group Number field, enter the number that represents the main group category for the input
point (for example, a vault).
8. In the Point Subgroup Number field, enter the number that represents the subgroup of the Point Group
Number setting (for example, subgroups to a bank vault may be vibration sensors, motion detectors, door
contacts, etc).
Input Point Group Conditions

The following conditions apply to input point groups when transmitting alarms:

If an input is activated and restored within its area False Alarm Timeout setting and there have been no other
activations in the same input point group, then no alarm is reported.
When an input is activated and restored, the Alarm Confirm Time counter starts (see Configuring General
Alarm System Parameters 163 ). If another input belonging to the same input point group is activated during the
Alarm Confirm Time counter, the alarm is reported immediately. To reset the Alarm Confirm Time counter,
open the Controller dialog box and select Commands > Restore All Latched Alarms. The Select Areas dialog
box opens, in it select the appropriate area, then click OK.
If an input point group consists of one input point only, an alarm from that point gives a full-transmitted alarm.
If an input point group consists of several input points, an alarm lasting more than eight seconds, from any input
point within the group, generates a full-transmitted alarm.
If an input point group consists of several input points, an alarm lasting less than eight seconds, from any of the
points within the point group, generates a pending alarm.
An alarm from a point during the Alarm Confirm Time from the same point group, will generate a full-
transmitted alarm for that point.
The following conditions apply to isolating input points in subgroups:
If a sub-group consists of one point only, that point cannot be isolated locally (that is, from a keypad).
If a sub-group consists of more than one point, only one of the points in the sub-group can be isolated locally
(that is, from a keypad).

Configuring Point Description Vocabs

A point "vocab" is a description given to an input or output (I/O) point to make it easily identifiable to system
operators. Vocabs are stored as lists in special files. Each vocab occupies an index position in the list, which precedes
the vocab text. based on 0 being the first entry, 1 being the second and so on. All vocab files can contain up to 256
entries.
Vocab are shown in the Transaction Manager. Attaching vocabs to input/output points helps security staff to
understand the situation faster and react accordingly. For information on configuring input and output points, see
Configuring Controller Keypad and Device Hardware. 134
GMS supports several methods of using and applying vocabs:
Pre-Defined Vocabs - These are provided as a convenience, using commonly used vocab "themes". The files
are stored on the GMS server and when an alarm is received from a Controller, GMS "opens" the correct pre-
defined vocab file and "looks up" the index entry specified for the point, to display the correct vocab. The vocab
entries can be edited, if required (see Editing Pre-Defined Vocabs 153 ).
Note: Vocab files ALMVOC04.MSG to ALMVOC015.MSG only can be edited.
User-Defined Vocabs - These are "substitutes" for up to six pre-defined vocabs entries. The vocabs can be
created by selecting the User Defined option in the Configuration for Input dialog box and entering the entries
directly. To create a new entry, click to view current entries and select a blank line from the list that appears.
The user-defined vocabs are stored in the selected pre-defined vocab file, using the last six available entries.
Custom Vocab List - This is a fully user-defined and editable "pick list" that is Controller-specific. That is, any
Controller can have up to 256 custom vocabs, defined specifically for that Controller, instead of any of the pre-
defined vocab files. With custom lists, GMS maintains file synchronization with Controller pick lists, so that
changes made to them are automatically uploaded to GMS (see Editing Custom Vocabs 153 ).
Editing Pre-Defined Vocabs

To edit pre-defined vocab entries, proceed as follows:
1. Open the Transaction Manager (click ).

2. In the Transaction Manager, select Options > Edit Message Files. The Edit System Files dialog box opens.
3. In the File Selection list:
To edit an input point vocab file, select Alarm Vocab File-x, where x is the number of the file.
Note: Vocab files ALMVOC04.MSG to ALMVOC015.MSG only can be edited.

Edited vocab text is displayed in the Transaction Manager only and not from the Controller, where the
files are hard-coded.
Each entry can be a maximum of 20 characters.
To edit output vocab entries, select Output Vocab Strings.

4. The GMS text editor opens, showing the file contents. Each vocab appears on a separate line and has a
sequential identifying number on the left.
5. Add or edit the vocabs as required. Add a new vocab on a new line, with a new sequential identifier.
6. Click to save the file. Use the text editor controls to select another file, copy and paste, etc.
After you have changed any input vocab files, you must download them to the Controller, as follows:
2. In the Controller dialog box, select View > Alarm > Alarm System Flags. The System Flags dialog box opens.
3. In the Vocab List for Alarms list, select the required vocab file, then click Download.
Editing Custom Vocabs

To edit custom vocab entries, proceed as follows:
Note: The Controller must be set to use custom vocabs (see Configuring Alarm System Flags 167 ).
2. In the Controller dialog box, select Alarm > Configure > Hardware.
3. On the device map, click the PCB image for an input device. A graphic of the PCB displays in a new dialog box.
4. Double-click an input point to access the Configuration for Input dialog box.

5. Click Edit Pick List. The pick list file opens in the Windows default text editor (usually Notepad).
Note: Each entry can be a maximum of 20 characters.
6. Edit any vocab entries as required, then select File > Save to save the file.

Configuring Card Activated Keypad Mode Changing

You can configure Pacom 1061 keypads to use a valid card swipe as user authentication for alarm mode changes
using the keypad, instead of manually entering a PIN. That is, to switch the system between alarm modes, the user
swipes their card, which "unlocks" the keypad and allows the mode to be changed.
Note: This feature allows alarm mode change only and is restricted to Staff Type 1-4 alarm user ID types.
Setting Up Keypad Alarm Mode Change Access from Card Swipes

To set up a keypad to grant system access from a card swipe, proceed as follows:
1. Add a 1061 keypad (see Adding Keypads 135 ) with the following parameters:
a. Set the device address to 1 in the Keypad Address field.
b. Enable the checkbox for each area that the keypad can control.
c. Enable the Enable card access operation option.
d. Click OK to save changes and close the Configuration for Keypad dialog box.
2. Add a reader (see Configuring Readers 204 ) with the following parameters:
a. Set the device address to 1 in the Device Address field.
b. In the Reader tab, Reader Interface list, select Pacom 1061 Type.
c. Click OK to save changes and close the Configuration for Reader dialog box.
3. Configure an alarm user ID type with mode change permission for the area(s) that the keypad can control (see
Configuring Alarm Users 131 ) with the following parameters:

a. In the ID Type list, select either Staff Type 1 ID, Staff Type 2 ID, Staff Type 3 ID or Staff Type 4 ID.
b. Enable the checkbox for each area(s) that the keypad can control.
c. Enable the Change Mode option for the area(s).
d. Click OK to save changes and close the Configuration for User ID dialog box.
4. Configure the cardholders that will have mode change access (see Using GMS - Operator Guide, Creating New
Cardholders) with the following parameters:
a. In the Card Details tab, User Type list, select same alarm user ID type defined in step 3.
b. In the Access Level tab, Selected Reader Access list, ensure that the cardholder has access to the reader
defined in step 2.

c. Save, then download that cardholder details to the Controller. Repeat this process for each cardholder.

Configuring Inovonics Devices

If you are using Inovonics wireless devices, such as pendants for personal duress buttons, infra-red detectors etc, the
Controller and Inovonics receiver are registered as a device and the transmitters are mapped to Controller inputs.
Pacom supports the Inovonics Frequency Agile (FA) and EchoStream series products. The major distinction between
the two being that EchoStream devices cannot be programmed with a device addresses or options using GMS - these
are built-in to the devices.
Configuring Controller IP Settings for Inovonics Devices

The following IP port configuration is required for Inovonics device communications:
1. Open the Controller dialog box and select General > Network > General Purpose IP Settings. The General
Purpose IP Parameters dialog box opens.
2. In the Port# field, enter the port address to use for communications. The default port for Pacom devices is
"3435" and "2800".
3. In the Protocol list, select Invonics and in the adjacent list, select UDP.
Note: You can use either UDP or TCP. UDP is faster because it does not require acknowledgement,
however, may be less reliable than TCP.
4. In the Local Port list, select (1) Ethernet.

5. In the IP Address field, enter the IP address of the Inovonics receiver.
6. In the Logical Device Number field, enter the logical device ID number for the receiver. For example, if it is
the second receiver, enter 2.
7. In the Supervise Time field, enter the time that the Controller will wait for a response from the device before
marking it as offline.
8. Click Download to save the settings to the Controller, then click Close.
When the Inovonics receiver comes online to the Controller, a corresponding message is displayed in the
Transaction Manager.
For more information on Inovonics protocol parameters, see Communications Protocol Parameters Reference 64 .
Configuring Inovonics Receivers and Transmitters to Communicate

with GMS
To set up an Inovonics receiver and related transmitters, proceed as follows:
1. Set up a Controller serial port to use the Inovonics protocol (see Configuring Controller Ports 25 ) to connect and
communicate with the Inovonics wireless receiver. The receiver is the hardware that accepts signals from the
wireless devices and sends them on to the Controller.
2. Add an Inovonics receiver device to the Controller (see Configuring Keypads and Device Hardware 130 ).
3. Use GMS to register the receiver (see Inovonics Protocol 64 ).
4. In the Controller dialog box (see Using the Controller Dialog Box 21 ), select Commands > Inovonics. The
Inovonics dialog box opens. Set up the device addresses for each transmitter as follows:
Note: Some Inovonics receivers may be supplied with a non-Pacom compatible communications protocol.
To program them to be compatible with Pacom, select Reset Receiver Protocol in the Inovonics dialog
box, then click Send.

For FA Transmitters:
a. Select Program Transmitter from the list.

b. In the Transmitter Option field, enter the hex code for the options. The bit codes for options are:
0..2 - Check-in interval.
3 and 4 - Unused.
5 - Internal contact.
6 - Normally open.
7 - End of line (EOL) resistor.
c. In the Transmitter Address field, enter the hex code for the device address for the transmitter. The value
represents:
IDM - System ID number.
IDL - Transmitter ID number.
d. Click Send and perform the required action on the transmitter (see Inovonics documentation).
For EchoStream Transmitters:
a. Select Register Transmitter from the list.

b. In the Input Number field, enter the device address (input number) for the transmitter.
c. Click Send and perform the required action on the transmitter (see Inovonics documentation).

Installing Dedicated Micros DS2 Series DVRs

You need to connect the DVR to the Controller using a serial port. The protocol used is MCI (Machine Control
Interface) and it requires that you install a CC01A interface unit to convert messages/commands between the DVR
and Controller into MCI format over the Controller RS232 port. In order to connect the Controller to the CC01A, you
need to use cables with the following pin assignments:
Serial DB25 to DB9 Cable Pin Connections
CC01A DB25 Female Controller RS485 DB9 Male Signal

2 3 RS232 Tx
3 2 RS232 Rx
7 5 Signal GND
Note: You must short pins 4 and 5 on the CC01A DB25 connector.
Serial DB25 to DB25 Cable Pin Connections

CC01A DB25 Female Controller Network DB25 Signal
Female
2 3 RS232 Tx
3 2 RS232 Rx
7 7 Signal GND
The Controller periodically polls the DVR and gets camera and DVR status in response. If polling response stops, GMS
treats the DVR as offline until it responds to polling again.
If you are installing multiple DS2 series DVRs, they can be "daisy-chained" together. With daisy-chained DVRs, the
Controller will require that each DVR address is sequential in order for it to map cameras to the relevant DVR.
The multiplexer address needs to be a decimal number in the range 16-31 (inclusive). For example, Address 16 =
DVR Unit 01; Address 17 = DVR Unit 02; Address 18 = DVR Unit 03, etc.

Configuring Controllers to Use OnSafe DVRs

This section outlines integration of Pacom Controllers and an OnSafe DVRs.
Configuring the DVR

Set up the DVR with cameras, inputs points and output points according to its documentation.
Configuring the Controller for IP DVR Communications

To configure Controller port parameters for IP operation with the DVR, proceed as follows:
2. In the Controller dialog box, select General > Network > General Purpose IP Settings. The General Purpose
IP Parameters dialog box opens. Configure the DVR settings according to the following sections.
3. In the Port# field, enter the DVR port address to use for communications. The default port for onSafe DVRs is
"2002". Specifying 2002 or 0 will connect to the default port.
Note: If the DVR is not using the default port number, ensure that you specify the correct port number.
4. In the Protocol list, select OnSafe and in the adjacent list, select TCP.
5. In the Local Port list, select (1) Ethernet.
6. In the IP Address field, enter the DVR IP address. If you leave the setting at "0.0.0.0", the Controller will look
for an OnSafe DVR and use the details of the first OnSafe DVR it finds.
Note: If the network has multiple onSafe DVRs, it is best to specify IP addresses.
7. In the Login Name field, enter the login name programmed in the DVR (max. 15 characters).
8. In the Select a number from the Password Index field, enter a password number from the Pacom password
list. This password associated with the number must match the password programmed in the DVR.
Note: Controller preset passwords are set from General > Networks > Port Settings > Advanced >
System Passwords. When setting the password, ensure that the Unicode option is disabled.
When the DVR comes online to the Controller, a corresponding message is displayed in the Transaction Manager.
Configuring the Controller Hardware Device Map Settings

The following procedure describes how to add an OnSafe DVR to the device map:
3. Right-click a blank area of the device map and select Add Device from the context menu. The Configuration (for
Device) dialog box opens. Set the parameters according to the following sections.

4. In the Device Type list, select onSafe DVR I/O.

All OnSafe DVR inputs are mapped 1 to 1. This means all DVR inputs can be mapped to Controller inputs.
Physical inputs 1 - 4.
Hard drive fails 121 - 122.
Virtual inputs 128 - 135.
Camera no signal 136 - 155.
Virtual inputs 201 - 220.
Note: See the OnSafe DVR documentation for input types.
All OnSafe DVR outputs are mapped 1 to 1.

Physical outputs 1 - 3.
To turn an OnSafe virtual input on, additional virtual outputs are used. Onsafe virtual outputs 193 - 200 are
used to activate virtual inputs 128 - 135 and virtual outputs 201 - 220 for virtual inputs 201 - 220.
Note: Virtual outputs are not assigned to any outputs in the OnSafe DVR.
When configuring Controller outputs to activate the first block of virtual inputs on the DVR, add a new
OnSafe output device which starts at address 201. Set this to any free output point on the Controller (max.
available outputs is generally 64).
All OnSafe DVR cameras are assigned an ID number from 1 - 20. When configuring cameras on the
Controller, add a new OnSafe device which starts at address 1. Set this to any free camera point on the
Controller.
Note: OnSafe DVRs generate alarm messages if they have a hard drive failure.
5. Click OK to complete the procedure. The Configuration dialog box closes and the new device displays on the
device map.

Configuring General Alarm System Parameters

General alarm system parameters, in conjunction with alarm system flags (options) (see Configuring Alarm System
Flags 167 ), determine how the alarm system functions for the selected Controller.
To configure general alarm system parameters, proceed as follows:
3. In the Controller dialog box, select Alarm > Alarm System Parameters. The System General Parameters
dialog box opens (see General Alarm System Parameters 163 ).
Parameter/Option Description
Mode Durations
Duration for Test Mode The time (in minutes) to allow systems users to complete Test mode. A
warning on the keypad occurs 60 seconds before expiry. A timeout alarm is
sent if this time expires and the area returns to Day mode.
Duration for Entry The time (in minutes) to allow users with Out of Hours access to gain access to
Outside Hours areas after the Latest Staff Exit Time setting and before the earliest Staff
Entry setting (see Configuring Area Access 175 ). If set to 255 allows unlimited
access. If set to 0 then no access is allowed.
Duration for Remote The time (in minutes) to allow the remote central station to give access to ATM
ATM Mode mode when commanding ATM mode.
Duration for Remote R/ The time (in minutes) to allow a remote central station to give a user entry
A Mode into any other mode.
Display Exit Message The time (in minutes) before the set area exit time that the system sonalerts
before Exit the keypad to warn the user that the area(s) require to be set within.
Open Warning Time This time (in minutes) used for all areas to define when after the Day Start
time (see Configuring Area Access 175 ) the system expects the area to be un-
set by. This timer is also used to select when Auto Lockout comes into effect.
Day lockout prevents users from accessing Day mode after the timer expires if
Day mode not entered before day start and open warning timers expire. To
enable this, set the Open Warning Time to a non-zero value and enable the
Warning Messages option. If the Day Start time is "0" (zero), then Auto
Lockout is disabled.

Briefcase Window The time (in minutes) allowed for the user to re-enter the premises to retrieve
a bag etc after the system is set. The period of time that this activates is
between the Staff Exit Time and Latest Staff Exit Time settings. This is
also the time that is extended to for late working, when selected from the
menu mode on the keypad (see the Pacom 1061 or 1062 manual). If set to
255 it allows unlimited access.
Areas to Use Briefcase Enable the checkbox for the areas to use the Briefcase window setting.
Window
Keypad Parameters
Normal Inactivity Time- The length of time (in minutes and seconds) that the keypad waits before
out sending keyboard inactivity time-out alarm, if a user accesses the system and
leaves the keypad without either logging off or completing the process that
they started.
Walk-test Inactivity The length of time (in minutes and seconds) to replace the Normal Inactivity
Time-out Time-out setting with if the system is in Test mode or the system has any
unsealed points that require a longer period of time to attend.
Extended Inactivity The length of time (in minutes) to use if the system is using its own camera
Time-out controllers to allow film counting.
Multiple PIN Attempt The length of time (in seconds) that the systems keypad locks out a after
Time-out multiple PIN entry attempts.
Message Scroll Speed The length of time (in seconds) that the keyboard takes between displaying
different items, that is, when viewing alarms.
No of PIN Attempts The number of tries that the user has to correctly enter their PIN code. After
before Fail this number of tries the system keypad locks the user out for the length of
time entered in the Multiple PIN Attempt Time-out setting.
Idle Time For Display The length of time (in seconds) that the keypad takes before reverting back to
displaying area one (if more than one area is being used) and displaying the
welcome message (if configured). This also requires the Return to Idle option
being enabled (for keypad configuration information, see the Pacom Keypad
Manual).
Alarm Confirm Time The length of time (in minutes) to allow for a point to remain in alarm in order
for it to be "confirmed" by another alarm activation within the same alarm
area. If the alarm is not confirmed, it is automatically isolated and a message
is sent to the monitoring center notifying of the isolation. If the point is
restored, the timer continues counting down and, if another point goes into
alarm within this time period, then both alarms are reported immediately. The
following conditions should be met:
System in Night mode.
Be a PIR, PIR Perimeter, Perimeter, Vibration or Vault point category.
The Enable Night Delay option is enabled (see Configuring Alarm System
Flags 167 ).
The alarm area in which the point is defined is selected in the Alarm
Confirm Areas setting.
Note: For EN50131 compliance, override the auto-isolation of points

after the Alarm Confirm Time has expired by enabling the Prevent
Auto Isolation of Confirmed Alarms option (see Configuring Alarm
System Flags 167 ).
Any active alarms are never "confirmed" by using a keypad to disarm
the system. An unconfirmed alarm message is generated from a
keypad if the user fails to enter the necessary PIN in time to disarm
the system.
Alarm Confirm Output An output point to activate when an alarm is confirmed.

Alarm Confirm Areas Enable the checkbox for the alarm areas to use the Alarm Confirm Time
function.
Ambush Areas Enable the checkbox for the alarm areas to use the Ambush Timer function.
Abort Window Time The length of time (in seconds) to allow for a triggered input that has been
configured to utilise the abort window to be disarmed before an alarm is
generated.
Miscellaneous System Parameters
Device Test Cycle Days The number of weekdays that pass between device test days. For example, to
set the test period to one week, set the number of test cycles to 5.

Note: Testing cannot be performed on Saturday or Sunday.
Current Test Day The weekday number that the system uses, in conjunction with the Device
Test Cycle Days setting, to set the present day. Monday = 1, Tuesday = 2,
Wednesday = 3, Thursday = 4, Friday = 5.
Note: Ensure that whatever day you are commissioning the system
that this number corresponds to that day. This number will change
every 24 Hrs.
Testing cannot be performed on Saturday or Sunday.
Self Test Output ON The length of time (in seconds) that the self-test output changes state for.
Time
Self Test Output OFF The length of time (in seconds) to apply after the Self Test Output ON Time
Time setting to allow tested devices to restore. The system expects that a normal
test of the device will produce an alarm but that the device should restore by a
certain time after being triggered. If the device does not restore before this
timer has expired then the device is judged to have failed the self test.
Entry/Exit Delay 2 The beep repetition frequency of the secondary entry/exit time beeper. The
Beeper number set is the period of the beep repetition in 0.1 sec increments. The
frequency of this beeper should be set faster than the Delay Timer 1, which is
one beep/sec, therefore the number set here should be less than 10 (10 x 0.1
= 1 sec) (5 or less recommended) (see Entry Delay 2 173 or Exit Delay 2 173 ).
Anti-False Timer The length of time (in seconds) associated with the Anti-False Alarm settings
that is added to the Exit Time setting to allow Perimeter or PIR Perimeter
points time to settle and restore after an exit.
If the Enable Local Isolation option is enabled and a point is still in alarm
after the Exit Time and Anti-False Timer have expired, then the point(s) are
automatically isolated and a corresponding message is sent to the monitoring
center. If the Enable Local Isolation option is disabled and a point is still in
alarm after the Exit Time and Anti-False Timer have expired, then a full
alarm is sent to the monitoring center.
Ambush Timer The length of time (in minutes) that the user has to un-set the system and
press the ENT key on the 1061/1062 keypad before an ambush signal is sent
to the monitoring center. Set to 0 to disable the timer.
Lock-set Debounce Time The length of time (in seconds) to allow for the lock to fully set. This time
should be kept as low as possible and can be judged if the site has a sticking
lock or ill-fitting door.
Note: Any effort to start the entry cycle before the timer expires is
ignored by the system.
Final Set Debounce As per Lock-set Debounce Time, but for the final set button.
Time
No of ATMs Accessed The number of areas that can be put into ATM mode at the same time.
Suspect Device The number of times (0 - 127) over a 30 second period that if an input
Activation Counter activates, it is reported as faulty and is automatically isolated.
Note: After a device has been classified as suspicious, it must be sent

a restore command or be reset from a keypad to resume normal
operation.
Day Delay Alarm Time The length of time (in minutes or seconds) that applies to any Day Delay
category point to allow before the system starts the sonalert and transmits an
alarm to the monitoring center. Selection of Sec or Min changes the time
value between seconds and minutes.
Day Delay Alarm Count The number of Day Delay category point alarm actions allowed in a one day
period (set to 0 for timer only operation). If the count is reached, then the
alarm is sent without delay.
Enable Sonalert for Day Enable to cause sonalert on keypads with the area displayed where the day
Delay Points delay alarm has been triggered after the Day Delay Alarm Timer expires.
Enable Sonalert Enable to bypass the Day Delay Alarm Timer and activate the sonalert
Immediately immediately.

Note: This option becomes available only after the Enable Sonalert
for Day Delay Points option is enabled.
Reset Activation Latch Enable to have the system reset the latched alarm count back to zero
by User whenever an alarm system user logs on and changes the alarm system mode.
Welcome Message The text that keypads will show after a normal inactivity time-out.
Staff Help Message on The text that keypads display when the user has a fault and requires a prompt
Exit to inform them of the procedure to follow. For example, providing a help
contact telephone number.
Contact Additional text to the Staff Help Message on Exit setting. For example, a
contact name.
ATM Pre-Delay The length of time (in minutes) that ATM personnel must wait after specifying
their code before being allowed to enter an ATM.
No. Isolate Points The maximum number of points that can be isolated from a keypad. If the
number is set to 0 (zero), then any number of points can be isolated.
Note: Points isolated from GMS do contribute to this number,

however, isolations from GMS are possible when this setting is
exceeded.
Message Log Size The maximum number of messages that can be viewed on a keypad.
Supervision Window The length of time (in minutes) that an Inovonics transmitter has to report to
[Inovonics FA400] the Controller before it is marked as offline. This should be the worst case
check-in time as there are no individual timers. All transmitters may have
different check-in times, so to avoid having any go offline, this time must be
set to the value of the longest check-in time.
Inovonics Application The ID of the Inovonics receiver connected to the Pacom 1068 device. This ID
ID is stored in the 1068, and only messages from the device with the specified ID
are accepted.
Enable PIN Code Error Enable for GMS to report and display all invalid user ID/PIN combinations
Reporting entered into a keypad. If no user ID is entered (PIN only entry, see
Configuring Alarm System Flags 167 ) GMS reports the user ID as 256.
Enable scrolling of Enable for power alarm messages to display when viewing alarms from a
power alarms keypad.
Enable scrolling of Enable for alarm messages to display on keypads without requiring a user ID/
alarms without logon PIN to log on to the keypad first.
Prevent Set/Autoset Enable so that if an area has one or more outstanding alarms it cannot be
when area is in alarm manually or automatically set.
Engineer requires staff Enable so that a staff type user must log on before an engineer can log on.
to log on first The engineer must enter their user ID and/or PIN within the Normal
Inactivity Timeout setting. If the timer expires and the system has not
entered engineering mode, the staff type user must log on again.
Staff can change only Enable so that Staff Type ID 1 - 4 alarm users can change their PIN at a
their own PIN keypad. If the user has access to more than one Controller (site), GMS
updates all relevant Controllers with the user's new PIN.
Note: Only the original PIN owner can change their PIN.
For added security, it is possible to have the system force users to
change their PIN after a set period of time, using an enrolment reader
(see Setting Mandatory User PIN Changing with 1061/1062 Keypads
137 ).
Do not show status on Enable so that when idle, 1061 and 1062 keypads will not show the status of
keypads when idle areas.
Extended Late Work on Enable so that the Extended Late Work option (if enabled) applies to area 1
area 1 only only.
Note: Areas linked to area 1 will not inherit this setting.
4. Click OK to download the parameters to the Controller. The Transaction Manager confirms the download.

Configuring Alarm System Flags

Alarm system flags (options), in conjunction with general alarm system parameters (see Configuring General Alarm
System Parameters 163 ), determine how the alarm system functions for the selected Controller.
To configure alarm system options, proceed as follows:
3. In the Controller dialog box, select Alarms > Alarm System Flags. The Alarm System Flags dialog box opens.
Configure the settings according to the following section.
Option Description
Enable Local Isolation Enable to allow users to isolate points locally using a keypad.
Enable Local De- Enable for the system to automatically de-isolate any isolated points when
isolation entering Day mode.
Enable Forced Exit Enable for the system to automatically log off any users from keypads when
the system is entering Night mode. If users are still in the building, they must
log on again and select an appropriate alarm system mode.
Enable Auto Lockout Enable so that after the Open Warning Time (see Configuring General Alarm
after Warning System Parameters 163 ) expires, the system automatically locks all areas in
the current mode (Night/Restricted Access) and prevents local users putting
the system into Day mode. The local user will have to contact the monitoring
center to take the system to Day mode.
Enable AC/Battery Low Enable to display any abnormal state of system power supplies on keypads
Display on Exit during exit.
Enable Comms Display Enable to display any abnormal state of system communications on keypads
on Exit during exit.
Enable Night Alarm Enable to display any alarm activations for an area that occurred during the
Display on Entry alarm armed period on keypads when the area is being disarmed.
Enable Exit Delay in Day Enable for the system to apply the Exit Delay timer (see Configuring Alarm
for Partials Areas 172 ) to any partial areas when users are exiting from Day mode. When
the exit delay beeper starts, a pending message displays in the Transaction
Manager indicating that the Controller is waiting for the timer to expire.
Partial areas refer to areas that can have mode settings independent of other
areas within the system.
Enable Partial during Enable for the system to allow partial areas to remain in their current mode
Mode Exit when a user changes the mode of an area. Partial areas refer to areas that can
have mode settings independent of other areas within the system.
Always Report Open/ Enable so that all states of an input are reported as an alarm.
Short Circuits
Raid Alarm in Enable to make all Raid category points live in Engineering and Test modes.
Engineering Mode

Option Description
Enable Pending Alarms Enable for GMS to report any pending (conditional) alarms. If disabled, the
pending alarm still occurs, but is not reported. The conditions for pending
alarms (number of alarm counts and the time period that they must occur
within) before reporting takes place is set in the area configuration (see
Configuring Alarm Areas 172 ).
Disable AREA Soft-key Enable to prevent area soft-key options being displayed on keypads.
Option
Enable IGNORE Soft-key Enable to display an "Ignore" soft-key option on keypads to allow users to be
for Unsealed Points able to accept unsealed points at keypads on setting the alarm system.
Late Work for Linked Enable for the system to apply the late work setting to all linked areas when a
Areas user sets the displayed area to late work.
Enable Extended Late Enable to allow users to extend late work to all day (24 hours).
Work
Enable CCTV Output Enable to allow Controller outputs 33 to 48 to report as CCTV type outputs.
Enable Sub-areas Enable for the system to support sub-areas. A sub-area is an area that resides
within another area for the purposes of supporting a different configuration
and different reporting. For example, an office with a safe that is located within
an existing area configuration.
Soft-keys to follow Enable to force the function keys below the keypad LCD to function in the
DAY/ NIGHT keys same way as the DAY and NIGHT keypad keys.
Enable Master Area Enable to force all areas to follow area 1 (the master area) in/out of Night
mode, regardless of the mode the other areas are in.
Enable Night Delay Enable to allow pending alarm operation in Night mode. There are two
instances of this:
Enabling this flag, with the input point configured for Pending Delay, forces
the point to use pending operation in both Day and Night modes (see Enable
Pending Alarms 168 ).
If the input point is not set for pending operation and its category is either
PIR, Perimeter, Perimeter PIR, Vault or Vibration and it goes into
alarm it delays reporting for eight seconds to allow the alarm to be cleared.
If it doesn't clear in eight seconds then a real alarm is reported. After being
triggered, if there is another night alarm from a similar input point within the
next 30 minutes, then it is sent immediately. After 30 minutes, the system
returns to a normal state, and allows delay before sending.
Disable Outputs for Enable to prevent any output linkages (that is, output points that are switched
Trouble Alarms by an input point) being triggered when an input point goes into alarm from a
trouble condition (either open, short or trouble). If the alarm is normal
(genuine), then output linkages activate as configured.
Disable Test for Night Enable to force the system not to check for points that have not seen
Area movement during the day, if they are sealed. This is linked to the input Self
Test while Inactive option (see Configuring Device Input Points 142 ), where
points are monitored for activity during the day, and a report is sent when
going to Night mode if there has been no activity from the device. This could
mean that it is faulty. If the keypad used when exiting has links to other areas
that are in Night mode, the system will not check for points set to Self Test
While Inactive in the areas already in Night mode.
Display Zone Numbers Enable for the system to display the physical zone number on the keypad
when displaying the vocab (point description) as additional information. This
occurs whenever the display scrolls for unsealed points etc.
Show Warning Areas Enable to force keypads to switch the display automatically to any areas that
have warnings or alarms (for example, "STAFF EXIT NOW") and sonalert. If
there are multiple areas with warnings, the keypad switches between them.
For example, if the keypad is displaying area 1, and there is an alarm or
warning on area 2, the keypad will display area 2 and begin sonalert.
Do Not Report Outputs Enable so that alarm messages are not reported when activating outputs that
with Null Vocab have not been assigned a vocab, that is, outputs assigned "Null
Vocab" (default).
Latch Tamper Alarms Enable to allow tamper alarms to be latched when they occur. That is, they
must be reset manually from a keypad or GMS.


Option Description
Report Tampers when Enable to allow input points thats are configured as tamper alarms, or device
Point is Latched tamper switches, to continue reporting tamper alarms after they have been
activated and latched (needs to be manually restored to be reset). This allows
the system to automatically isolate alarm reporting from the tamper if it
exceeds the Suspect Device Activation Counter setting (see Configuring
General Alarm System Parameters 163 ), which generally indicates a fault with
the input.
Note: This setting applies only when the Latch Tamper Alarms
option is enabled.
Do Not Display Test Enable to prevent the system from displaying failed test results on keypads (or
Result beeping) as a result of any selected self-test on mode change options (Test
on Exit from Day, Test on Entry to Day, Test on Entry to Test Mode or
Test Cameras on Entry to Day). In other words, the test goes ahead on
mode change request, however, the keypad user is not made aware of the
results, nor prompted for any further action, and the mode is changed.
Note: If test failures occur, they are logged by GMS.
Prevent Auto Isolation Enable to prevent the system from automatically isolating alarm points if they
of Confirmed Alarms are not confirmed within the Alarm Confirm Time setting (see Configuring
General Alarm System Parameters 163 ). This setting is required for EN50131
compliance.
Test on Exit from Day Enable to perform the self test upon exit of Day mode.
Test on Entry to Day Enable to perform the self test upon entry to Day mode.
Test on Entry to Test Enable to perform the self test upon entry to Test mode.
Mode
Test Cameras on Entry Enable to perform the self test on the camera system upon entry to Day mode.
to Day
Enable Combined ID Enable for the system to prompt users for a single entry code that combines
and PIN Entry the user ID number and PIN. For example, if an ID is 8 and a PIN is 1234,
then the user only has to enter "81234" for access.
Enable PIN Entry Only Enable for the system to prompt users for their PIN only for access. User ID
numbers are not required.
Use Card Access User Enable for the system to use cardholder access PINs for alarm user mode
PINs change operations. That is, to not use the normal alarm user PINs, which are
limited to a maximum of 66 or 99 users, and use cardholder PINs instead to
activate alarm area mode changing. This increases the number of alarm users
to however many cardholders are in the system (see Configuring Readers 216 ).
Note: The Use access levels for area settings miscellaneous global
access setting must be enabled for this option to work (see
Configuring Miscellaneous Global Access Settings 233 ).
Enable PIN Entry when Enable for the system to prompt users for their PIN when exiting.
Exiting
Enable Random Enable so that when adding a user via a keypad, the Controller will randomly
Rejection of PIN reject the PIN, and will require the user to enter another PIN.
Note: This setting applies only when adding a user with a keypad.
Duress with 3 Enable to send a duress alarm if a user enters a PIN containing three
Ascending Digits consecutive ascending digits. For example, a duress alarm is sent if PIN is
7456.
Users can enter a duress PIN when he/she is threatened or when unusual
circumstances exist and they wish to secretly alert security. After entering a
duress PIN access is granted and operation appears normal to an observer,
however, a duress alarm is sent to the monitoring station.
When adding users to the system, it automatically checks to ensure that a user
does not select an unacceptable duress PIN. For example, if Duress with 3
Ascending Digits is enabled, a user cannot have a PIN similar to 1238.

Option Description
Duress with 3 Enable to send a duress alarm if a user enters a PIN containing three
Descending Digits consecutive descending digits. For example, a duress alarm is sent if a PIN is
8762.
Duress with 3 Same Enable to send a duress alarm if a user enters a PIN containing three of the
Digits same digits consecutively. For example, a duress alarm is sent if a PIN is
7771.
Duress with PIN Enable to send a duress alarm when the Enable PIN Entry Only option is
Incremented by 1 enabled by the user entering a PIN incremented by one (1). For example, if
the normal PIN is 9623, then the duress PIN is 9624.
Note: In this case, system administrators must ensure that user ID

PINs are not consecutive.
duress PIN, access is granted and operation appears normal to an observer,
Duress with PIN Enable to send a duress alarm when the Enable PIN Entry Only option is
Incremented by 2 enabled by the user entering a PIN incremented by two (2). For example, if
the normal PIN is 9623, then the duress PIN is 9625.
Note: In this case, system administrators must ensure that user ID

PINs are not two digits apart.
duress PIN, access is granted and operation appears normal to an observer,
Duress with Specified Enable to send a duress alarm if a user enters a PIN containing a specific digit
Last Digit as the last digit. For example, a duress alarm is sent if a PIN is 1659, where 9
is set as the specific digit. Enter the duress digit in the adjacent field.
Ask Duress Enable for the system to prompt the user for confirmation after entering a
valid duress code.
Enable Sonalert for Enable so that keypads sonalert if any tamper conditions are encountered
Tampers during Day (unset) mode only.
Enable Sonalert for Enable so that keypads sonalert if any Environment category input point is
Environmental Points activated during Day (unset) mode only.

Option Description
Enable Sonalert during Enable so that keypads sonalert if any points tested during Test mode are still
Test Mode active when they scroll across the display.
Enable Sonalert during Enable so that keypads sonalert with a series of short beeps as any unsealed
Scroll points scroll across the display.
Output 57 - 64 to Enable so that the system automatically activates the following outputs as
Follow Graphics Status mode and alarm indicators:
Output 57 - Activated when the system is in Night mode.
Output 58 - Activated when any point is in alarm.
Output 59 - Activated when any point is isolated.
Output 60 - Activated when the system is in Restricted Access mode.
Output 61 - Activated when the system is in Test mode.
Output 62 - Activated when there is a power (AC/battery) alarm.
Output 63 - Activated when there is a duress alarm.
Output 64 - Activated when there is a comms alarm.
Output 56 to Follow AC Enables output 56 to activate following a passed AC power and backup battery
& Battery OK check.
Disable Voltage Enable for the system to remove voltage switching from inputs and look for a
Switching for Alarms 7 or 12 volts DC voltage input. Use the 12V or 7V options to determine the
required voltage.
Note: This setting is for Asia only.
Vocab List for Alarms Select a vocab file from the list to determine the list of descriptions available
when configuring points (see Configuring Input Points 142 ). It is possible to edit
vocab files ALMVOC05.MSG to ALMVOC15.MSG and download them to the
Controller.
The CUSTOM option enables the use of point vocabs from Controller-specific
and editable pick list files instead of any of the pre-defined vocab files. With
custom lists, GMS maintains file synchronization with Controllers, so that
changes made to the files are automatically uploaded to GMS.
Language Select a language for display on the keypads from the list. There is hard-coded
translation in the Controller for all keypad messages. Available languages are:
English, Chinese, Swedish, German, Hebrew, French, Spanish and Finnish.
4. Click OK to download the parameters to the Controller. The Transaction Manager confirms the download.

Configuring Alarm Areas

When a Pacom alarm system is installed it can be divided into a maximum of eight separate alarm areas (32 for 8001
Controllers). Alarm areas are sets of alarm points that are grouped together to share, for example, common users,
parameters and time schedules. These areas can be linked together, or independently operated.
Area configuration allows you to define parameters such as:
Areas that report to the system.
Links to other areas.
General timers.
User and alarm reset types
Keypads message strings.
Configuring Alarm Area Parameters

To configure alarm area parameters, proceed as follows:
3. In the Controller dialog box, select Alarm > Area Settings. The Parameters for Area dialog box opens.
4. Enable the Report on this Area option to activate the area parameter controls and set them according to the
following table.
Report on this Area Enables the area to be processing by the system. No parameters can be
specified unless this option is selected. The system will not report or process
any function unless at least one area is configured with the Report on this
Area option enabled.
For programming consecutive areas, click Next Area - the current area
number displays in the dialog box title bar. To return to Area 1, cycle the Next
Area button through the remaining areas.
Access/Secure Only Forces the system to report only during Restricted Access and Night modes
Area only (see Configuring Area Access 175 ).
Vault Area Changes the format of the Normal and Temporary Hours, allowing a vault time
window. All points that are defined as vault type in alarm configuration
category are inhibited between the vault start and vault end times. If enabled,
Normal and Temporary hours are used (see Configuring Area Access 175 ).
Local Report Only Alarms are reported only to local ports and not to the Base Station using the
network.
Linked to
Linked to Enable the checkbox next to each area to be linked. If areas are linked, when
securing the area the user is prompted to close any linked areas, provided
they have authorization (see Configuring Alarm User Types 131 ).

General Timers
Entry Delay 1 The time allowed for the user to enter the premises and deactivate the alarm
system from the keypad using their PIN. The timer is activated when the user
is detected entering the premises. If Enable Beeper On Entry is selected the
keypad emits a slow beep until the timer has expired, at which time it will
activate the Entry Delay 2 timer.
Entry Delay 2 This timer is activated when the Entry Delay 1 timer expires. During this time
the keypad will beep at a faster rate than for Entry Delay 1. This indicates
that an alarm is about to be sent and to give the user an increased sense of
urgency.
The beep repetition frequency is controlled using system Entry/Exit Delay 2
Beeper setting (see Configuring Alarm System Flags 167 ).
Entry delay applies only to input points that have the Primary Delay or
Pending Delay option selected (see Configuring Device Input Points 142 ).
Exit Delay 1 Exit delay is the time allowed for the user to leave the premises after they
have armed the alarm system. The Exit Delay 1 timer is activated when the
user enables Night mode from the keypad. If the Enable Beeper On Exit
option is enabled the keypad emits a slow beep until the timer has expired at
which time it will activate Exit Delay 2 .
Exit Delay 2 This delay timer is activated when the Exit Delay 1 timer expires. During this
time the keypad will beep at a faster rate than for Exit Delay 1. This is to
indicate that the system is about to be armed and to give the user an
increased sense of urgency. The frequency of this beep is controlled by the
Entry/Exit Delay Beeper 2 setting (see Configuring Alarm System Flags 167 ).
If a final set point (see Configuring Device Input Points 142 ) point is activated,
all exit delays are immediately terminated and the system will change to Night
mode .
Holdoff Timer Enter the time (minutes and seconds) for any linked output points to be
delayed from activating.
Holdon Timer Enter the time (minutes and seconds) for any linked output points to be
activated for.
User Defined Descriptions
Night Select to display the text (in the field to the left) on the keypad instead of the
default (Night) when the area is in Night mode. The text is restricted to ten
characters, click the text field and enter the text.
Restricted Select to display the text (in the field to the left) on the keypad instead of the
default (Restricted) when the area is in Restricted mode. The text is restricted
to ten characters, click the text field and enter the text.
Day Select to display the text (in the field to the left) on the keypad instead of the
default (Day) when the area is in Day mode. The text is restricted to ten
characters, click the text field and enter the text.
Staff Select to display the text (in the field to the left) on the keypad instead of the
default (Staff). The text is restricted to ten characters, click the text field and
enter the text.
User Type
User Type Select a user type so that when they are logged on, the system periodically
reminds them log on again by beeping the keypad. The interval is set in the
Reminder Timer field. This is a security setting to avoid the selected user
type from logging on and failing to log off. After the timer expires the keypad
beeps for 60 seconds and, if the selected user type fails to log on to the
system again, they are logged off and an alarm is sent.
Reminder Timer Enter the time (in multiples of 10 minutes) that the user type can remain
logged on for before the reminder beeping begins and the user has to log on
again.
Reset Type
No Special Reset Type Allows any user to reset alarms.
Client Reset Allows the client to reset alarms at the keypad.
Engineer Reset Allows a Pacom engineer to reset tamper alarms at the keypad.

General Parameters

Enable Beeper on Entry Enable the beeper/sonalert on the keypad during log on or entry operations,
starting the entry procedure.
Enable Beeper on Exit Enable the beeper/sonalert on the keypad during log off or exit operations.
Enable 10 Sec. Warning Enable the beeper on the keypad when a warning message is displayed. The
Beeper beeper sounds every 10 seconds for the following warnings:
Film Count Low.
Staff Exit xx Min.
Staff Exit Now.
User Exit xx Min.
User Exit Now.
Display Welcome Display the welcome message, if required. This message is linked to the Idle
Message While Idle. Time setting (see Configuring Alarm System Flags 167 ) and the keypad
Return To Idle setting (see Pacom keypad manual). When a key is pressed
on the keypad, the display shows the current status. After the Idle Time has
expired the welcome message is displayed again. If the Welcome Message
field (see Configuring General Alarm System Parameters 163 ) is left blank the
keypad display will go entirely blank after the Idle Time expires.
Disable Warning Stops the following alarm warning messages:
Messages. Late to Open Vault.
Late to Close Vault.
Pending Delay Count Enter a number to determine the number of pending alarms that have to be
tripped before a full alarm is sent. If the pending alarms count is higher than
the Pending Delay Count setting, the alarms are transmitted immediately.
False Alarm Timeout The pending alarm delay timer. This is how long the system will wait until it
transmits all pending alarms. Select the M option for the timer to be in
minutes, or S for seconds. If you have the Pending Delay Count set to more
than 1, several pending alarms need to occur within the pending alarm delay
timer for the alarm to be reported.
Area Description The name of the area that appears on the keypad. It is restricted to eight
characters.
Log On/Log OFF Message String on Keypad
Log On/Log OFF Select a message for display on the keypad during log on/log off.
Message String on
Keypad
5. Specify the area parameters as required.

6. To set up other areas, click Next Area or Previous Area, or enter an area number at the top of the dialog box
and click Goto. Proceed from step 4 for each new area.
7. Click OK to download the area parameters to the Controller. The Transaction Manager window confirms the
download.

Configuring Alarm Area Access

Operational hours see the times during which a site is accessible, and when a specified type of type of user (for
example, a guard or a cleaner) is permitted to enter or leave the premises.
There are six operational time frames available (access them from the Controller dialog box, Alarm > Alarm Access
menu):
Setting Normal Hours 175 .
Setting Temporary Hours 177 .
Setting ATM Hours. 178
Setting Cleaner Hours 178 .
Setting Guard Hours 179 .
Setting Service Hours 180 .
You can also create Temporary Schedules, which override any other access settings. See Setting Temporary
Schedules 181 .
Along with access settings is the Yearly Calendar. This calendar defines days of the year which are different to normal
access settings. For example, public holidays. See Setting the Yearly Calendar 180 .
Operational time frames must be configured in the following sequential order:
1. Staff Entry and Day Start - The Day Start time must not be earlier than the Staff Entry time.
2. Day End - Must not be later than the Staff Exit or Latest Staff Exit times.
3. Day Start and Day End - Must not be the same.
Note: All times must be entered in the 24 hour format (00:00 to 24:00, HH:MM). Due to the overlap of
time (00:00 and 24:00 are the same time) the system is always active. If any "Start" time = 00:00 and
"End" time = 24:00, then 24 hour access is allowed.
Setting Normal Hours

Normal Hours are the hours set for general staff and patron entry and exit to an area. These hours must be set for
each area and are dependent on the parameters set in the area configuration (see Configuring Alarm Areas 172 ).
Normal Hours are overridden by Temporary Hours (see Temporary Hours 177 ) and the yearly calendar (see Yearly
Calendar 180 ).
Note the following points when entering normal hours:
If the Staff Entry time equals the Day Start time, then there is no restricted access on entry. The system will
go to Day mode.
If the Day End time equals the Staff Exit time, then there is no restricted access on exit. The system will go to
Night mode.
If the Day Start and Staff Entry times are set to 00:00 hours and the Day End and Staff Exit times are set to
24:00 hours, then this area has 24 hour access.
If the times set in normal hours are exceeded then the following warnings are sent:
The "Late to Open" warning message is sent if the system remains in Night mode past the Day Start time,
provided the Staff Entry time is not 00:00.
The "Late to Open Vault" warning is sent if the system is not in Day mode at the Day Start time for more than
the Open Warning Delay time setting (see Configuring General Alarm System Parameters 163 ), provided the
Day Start time is not 00:00.
The "Late to Close Vault" warning is sent if the system has not left the Day mode by the Day End time,
provided the Day End time is not 24:00 and that Latework has not been selected.
The "Late to Close" warning is sent if the system has not left the Day or Restricted modes (that is, not in Night
mode) by the Staff Exit time, provided the Staff Exit time is not 24:00 and that Latework has not been
selected.
Note: If the Disable Warning Message option is selected in the area configuration (see Configuring
Alarm Areas 172 ), no warnings are sent.
To access and configure Normal Hours, proceed as follows:

1. Select Alarm > Area Access > Normal Hours in the Controller dialog box (see Using the Controller Dialog Box
21 ). The Normal Hours for Area dialog box opens.

2. Referring to the following section, enter parameters as required.
Programmed Hours The hour settings that you program into the system for repeated use. To
program a set of hours, in Permanent Selection select Default, then proceed
to enter the hours as required. Click Add to add the settings to the
Programmed Hours list (see Quick Select 176 for how to apply
Programmed Hours list settings).
Permanent Selection Permanent Selection is used to define the type of alarm status of that
particular day. Options are:
Night - Used to select Night mode for alarm operation from 00:00 to 24:00.
Times are not entered in the fields for that day.
Day - Used to select Day mode for alarm operation from 00:00 to 24:00.
Default is used to program the times of entry and exit to the premises for
that day.
Staff Entry Used when the Permanent Selection setting is Default. This time is the
earliest time a staff member may enter the premises. The premises is in
Restricted Access mode after this time and in Night mode before.
Day Start Used when the Permanent Selection setting is Default. This time is the start
of normal hours. The premises is in Day mode after this time.
Force Entry Enable for the system to automatically switch to Day mode at the Day Start
time. This setting is not available for selection during Night mode.
Day End Used when the Permanent Selection setting is Default. The time entered
here is the end of normal hours. The premises is put in Restricted Access mode
after this time.
Force Exit Enable for the system to automatically switch to Restricted Access mode at the
Staff Exit time. This setting is not available for selection during Day mode.
Staff Exit Used when the Permanent Selection setting is Default. This time is the
normal staff exit time. The premises is in restricted access mode after this
time.
Latest Staff Exit Used when the Permanent Selection setting is Default. This time is only
active if Latework is selected from the keypad. If Latework is selected twice,
access is granted all night. The premises are put in Night mode after this time.
Quick Select Used when the Permanent Selection setting is Default and in conjunction
with the Programmed Hours list. Select the required hours from the
Programmed Hours list, then click Quick Select to apply them.
Allow Outside Hours Allows the user with Allow Entry Outside Hours permission set to access this
area outside normal hours (see Configuring Alarm User Types 131 ).
Use Restricted Access Used in conjunction with the Duration for Remote R/A mode option (see
Duration Configuring General Alarm System Parameters 163 ). When selected, it limits
alarm system access to the area to the Duration for Remote R/A mode
[timer] setting. When the timer expires, the system requests the user to exit
the system (alarm sent and keypad beep) and logs the user off.
Disable LTO Enable for the system to not generate "late to open" messages.
Disable LTC Enable for the system to not generate "late to close" messages.
3. Click OK to save the settings.

Setting Temporary Hours

Temporary Hours are available only to Staff Types 1, 2, 3, and 4. They are valid only for seven days after being
programmed. At midnight on the seventh day the system automatically deletes the hours. Temporary Hours override
the monthly calendar and Normal Hours 175 , however, operate in the same way as Normal Hours.
To access and configure Temporary Hours, proceed as follows:
1. Select Alarm > Area Access > Temporary Hours in the Controller dialog box (see Using the Controller Dialog
Box 21 ). The Temporary Hours for Area dialog box opens.
program a set of hours, in Permanent Selection select Default, then
proceed to enter the hours as required. Click Add to add the settings to the
Permanent Selection Permanent Selection is used to define the type of alarm status of that
particular day. Options are:
Night - Used to select Night mode for alarm operation from 00:00 to 24:00.
Day - Used to select Day mode for alarm operation from 00:00 to 24:00.
Default - Used to program the times of entry and exit to the premises for
that day.
Staff Entry Used when the Permanent Selection setting is Default. This time is the
earliest time a staff member may enter the premises. The premises is in
Restricted Access mode after this time and in Night mode before.
Day Start Used when the Permanent Selection setting is Default. This time is the start
of normal hours. The premises is in Day mode after this time.
Force Entry Enable for the system to automatically switch to Day mode at the Day Start
time. This setting is not available for selection during Night mode.
Day End Used when the Permanent Selection setting is Default. This time is the end
of normal hours. The premises is put in Restricted Access mode after this time.
Force Exit Enable for the system to automatically switch to Restricted Access mode at
the Staff Exit time. This setting is not available for selection during Day
mode.
Staff Exit Used when the Permanent Selection setting is Default. This time is the
normal staff exit time. The premises is in restricted access mode after this
time.
Latest Staff Exit Used when the Permanent Selection setting is Default. The time entered
here is only active if Latework is selected from the keypad. If Latework is
selected twice, access is granted all night. The premises are put in Night mode
after this time.
Allow Outside Hours Allows the user with Allow Entry Outside Hours permission set to access
this area outside normal hours (see Configuring Alarm User Types 131 ).

Use Restricted Access Used in conjunction with the Duration for Remote R/A mode option (see
Duration Configuring General Alarm System Parameters 163 ). When selected, it limits
alarm system access to the area to the Duration for Remote R/A mode
[timer] setting. When the timer expires, the system requests the user to exit
the system (alarm sent and keypad beep) and logs the user off.
Disable LTO Enable for the system to not generate "late to open" messages.
Disable LTC Enable for the system to not generate "late to close" messages.
Setting ATM Hours

ATM Hours are designed to allow access to an ATM (Automatic Teller Machine) area by service people for various
purposes (for example, servicing, cash fills, etc) without activating alarms. The times are programmed by selecting
the day and entering the hours.
Note: If End Time is 23:59, then the user is logged off regardless of any remaining Duration time. If
End Time is 00:00 or 24:00, then the user logged off after the Duration timer expires.
To access and configure ATM Hours, proceed as follows:

1. Select Alarm > Area Access > ATM Hours in the Controller dialog box (see Using the Controller Dialog Box
21 ). The ATM Hours for Area dialog box opens.
Start Time The earliest time of day that an ATM service person can access the premises.
End Time The latest time of day that an ATM service person can access the premises.
Duration The length of time on the premises available to an ATM service person once
they have logged on. If the service person does not exit the premises before
this time has elapsed, an alarm is sent.
Setting Cleaner Hours

Cleaner Hours are programmed to allow cleaning personnel access to an area without activating alarms. The times
are programmed by selecting the day and entering the hours.

To access and configure Cleaner Hours, proceed as follows:

1. Select Alarm > Area Access > Cleaner Hours in the Controller dialog box (see Using the Controller Dialog Box
21 ). The Cleaner Hours for Area dialog box opens.
Programmed Hours list (see Quick Select 176 for how to apply Programmed
Hours list settings).
Start Time The earliest time of day that a cleaner can access the premises.
End Time The latest time of day that a cleaner can access the premises.
Duration The length of time on the premises available to a cleaner once they have logged
on. If the cleaner does not exit the premises before this time has elapsed, an
alarm is sent.
Setting Guard Hours

Guard Hours are programmed to allow security personnel access to the premises without activating alarms.
To access and configure Guard Hours, proceed as follows:

1. Select Alarm > Area Access > Guard Hours in the Controller dialog box (see Using the Controller Dialog Box
21 ). The Guard Hours dialog box opens.

Days Allowed Enable the checkbox for each day that security personnel are allowed into the
premises.
Start Time The earliest time of day that a security person can access the premises.
End Time The latest time of day that a security person can access the premises.
Duration The length of time on the premises available to a security person once they
have logged on. If the security person does not exit the premises before this
time has elapsed, an alarm is sent.
Setting Service Hours

Service Hours provide a time window for isolating and servicing various alarm inputs. Service Hours are valid in the
system at all times and must be deleted manually if they are no longer required. Service hours are independent of
the Normal Hours and are only used when the service PIN is selected in the user ID (see Configuring Alarm User
Types 131 ).
To access and configure Service Hours, proceed as follows:

1. Select Alarm > Area Access > Service Hours in the Controller dialog box (see Using the Controller Dialog Box
21 ). The Service Hours dialog box opens.
Days Allowed Enable the checkbox for each day to allow input points to be isolated for
servicing.
Points Isolated Enable the checkbox for each input point type to be isolated for servicing
Start Time The earliest time of day that a service person can access the premises.
End Time The latest time of day that a service person can access the premises.
Duration The length of time on the premises available to a service person once they
have logged on. If the service person does not exit the premises before this
time has elapsed, an alarm is sent.
Setting the Yearly Calendar

The Yearly Calendar allows you to the program days when access is not required to the premises, for example, public
holidays. The calendar is programmable for a 12 month period starting at the present month.
Note: The Yearly Calendar entries can be overridden by Temporary Schedules 181 .
Selecting a day in the calendar will set the alarm system to Night mode for the entire day. Selecting areas (Areas to
use Yearly Calendar region) will enable Night mode in those areas only.
To configure the Yearly Calendar, proceed as follows:

1. In the Controller dialog box (see Using the Controller Dialog Box 21 ) select General > Yearly Calendar >
Alarms. The Yearly Calendar dialog box opens.
Calendar Enable the checkbox next to each date that you want to exclude normal
access (that is, Night mode for the entire day).
Areas to use Yearly Enable the checkbox next to each area that the Yearly Calendar will apply to.
Calendar
Note: The areas you select will be the common to the Yearly
Calendar for all months.
Next Month Click to display the calendar for the next month.
3. Click OK to save the Yearly Calendar.
Setting Temporary Schedules

Temporary Schedules override all other schedules and can be configured for use by all user types. You can create up
to eight Temporary Schedules.
To create a Temporary Schedule, proceed as follows:
1. To access and configure Temporary Schedules, select Alarm > Temporary Schedule in the Controller dialog
box (see Using the Controller Dialog Box 21 ). The Temporary Schedule dialog box opens.
User ID no This is the ID number to associate with the User PIN code.
User PIN The PIN (personal identification number) that the user must enter to gain
access.
Allow any Staff ID Enable to allow all users with a Staff ID type to use this schedule.
ID Type Select the user ID type allowed for the schedule.

Temporary ID Vocab You can enter text here so that when the user logs on, the system display
states who is present (used for auxiliary users).
Days of Schedule Select which days that schedule is to be allowed to be used by the system.
Area to Access These are the areas that the user is allowed to enter using the schedule.
Start Time This is the time from which the user can gain entry.
End Time This is the time after which the user will not be given entry.
Delete Schedule after Use Enable to delete the schedule after one use.
Allow Entry Outside Enable to allow the user access outside Normal Hours.
Hours
Can Log on to All Areas Enable to allow the user access to more than one area (requires log on) after
logging on to one area.
Allow Fingerscan Enables the user to log on using fingerscan, if attached to the system.
Allow Access Control Enable to allow the user to use the systems ability of having a card reader
and PIN pad associated with an area to un-set.
3. Click OK to save the Temporary Schedule.

Creating Event Drivers and Macros

Event drivers and macros are system utilities that allow you to tailor behavior of the system, based on a set of
circumstances or conditions. When the conditions are met, the Controller performs the required task.
Configuring Event Drivers

Event drivers provide a method of controlling the system outputs based on specific pre-defined events. When these
events take place, the Controller responds by performing the required action. You can program up to 16 different
event driven activations.
To configure an event driver, proceed as follows:
1. In the Controller dialog box (see Using the Controller Dialog Box 21 ) select Macros > Alarm Events. The
Time/Event Driven Activation dialog box opens.
For Days Enable the checkbox next to each day that the event driver can activate
during.
For Areas Enable the checkbox next to the area that the event driver can activate from.
Previous Click to go back to the previously created event driver settings.
Next After making settings, click to create a new event driver.
Macros Click to open the Macro Configuration dialog box.
Activation Type
Time Driven Enable to have the activation driven by the time of day. When selected, the
Time field becomes active.
Mode Driven Enable to have the activation driven by a change in mode. When selected,
the Activate on Entry to options become active. You can select multiple
options, unless the two definitions contradict, for example, day/night.
Condition Driven Enable to have the activation driven by an alarm system condition, for
example, whenever an "Entry Warning" or "Exit Warning" message is sent.
When selected, the Activate During options become active. You can select
multiple options.
Event Driven Enable to have the activation driven by an event, for example, a device
tamper event. When selected, the Activate on options become active. You
can select multiple options.
Time Enter the time that you require the event to happen. The output changes
state at that time. Another event can then be raised to turn the output off.
This setting requires the Time Driven option to be selected.
Activate
Output no. Select for the event driver to switch an output. Enter the output number in
the adjacent field.
Trigger no. Select for the event driver to run a macro. Enter the macro number in the
adjacent field. See Creating Macros 184 .
On Select for the event driver to turn the output or trigger ON.
Off Select for the event driver to turn the output or trigger OFF.
Latched Select so that the relay will not change back until the system has exited the
mode that drives the relay.
Momentary Select so that the relay will only change state for five seconds when the
event occurs.

3. Click OK. The dialog box closes and the event driver details are downloaded to the Controller.
Creating Macros
The concept of macros is based on a series of basic logical functions performed on specified conditions, resulting in an
action. Macros allow you to be very specific with the conditions that need to be met and with the subsequent actions
to take, providing you with complete flexibility. Event drivers are used to activate macros (see Configuring Event
Drivers 183 ).
The key functions in macro programming are the NOT, AND, OR and THEN functions. These can be used in any
combination to establish an action.
The AND function is used to link two conditions that must both be correct before the action is performed or to
link multiple actions to be performed.
The OR function is used to link two conditions so that the action is performed when either condition is correct.
The NOT function is added to any condition to denote that it must be in a negative or untrue state to satisfy the
condition, for example, when input number four is NOT active.
The THEN function is used to lead the macro from the end of the conditions into the action.
Note: For macros controlling elevator floor access, if a macro is triggered after another macro is already
running for that elevator, the properties of the second macro override that of the first macro. For example,
if a macro is running that unlocks elevator floor 12 for one hour, then another macro runs that unlocks
elevator floor 12 for 10 minutes, the floor is unlocked for 10 minutes from the running of the second
macro before being locked, regardless of any time left of the first macro timer.
In macro programming the AND function takes priority over OR function where multiple functions are used, for
example:

To program a macro, proceed as follows:

1. In the Controller dialog box (see Using the Controller Dialog Box 21 ) select Macros > Alarm Macros (or click
Macros in the Time/Event Driven Activation dialog box). The Macro Configuration dialog box opens. The dialog
box is divided into two regions - Macro Conditions and Functions and Actions. If macros have been
programmed previously, you can enter the macro number at the top of the dialog box, and click Goto to display
it.
2. Select Edge Triggered or Level Triggered.

If you select Edge Triggered, the action occurs at the time the condition is met and will not effect the action
after this.
If you select Level Triggered, the action will continue to be performed while the condition is true.
3. Select the first condition from the list in the Macro Conditions and Functions region.
Conditions are tests performed on the current state of the system and are continuously monitored. The following
table lists the available macro conditions.
Condition Description
Undefined Conditions not used.

Trigger Defined using an event driver. There are up to 256 triggers available,
depending on the Controller model. Triggers can be set to = TRUE or FALSE, or
be reset by an action from another macro expression. The associated number
is the number as set in the associated event driver.
Masked Input Inputs that have reported as alarms to the system. A masked input is active
only if the alarm reporting criteria for it are correct when the sensor goes
active. Any input can be used as masked or unmasked. The associated number
is the input number.
Output The normal GPOs (General Purpose Outputs) that are used throughout the
system. The associated number is the output number.
Graphics Status Information the system uses during general operation to summarize the status
of an area. In macros the status can be used as conditions. Click Edit to open
the Graphic Status for Condition dialog box, where you can define further
options. Make no selections in this dialog box for Day mode.
Timer Expired There are 10 in the system that can be used for general purpose operation
within the macros. A timer set as an action with a value in one macro, can be
used as a condition in another macro. Functions are performed and tested
when the timer has completed its count. The associated number is the macro
number in which the timer is defined as an action.
Timer Active There are 10 in the system that can be used for general purpose operation
within the macros. A timer set as an action with a value in one macro, can be
used as a condition in another macro. Functions are performed and tested on
the timer being active (it has a value loaded and counting). The associated
number is the macro number in which the timer is defined as an action.
Network Status Information the system uses during general operation to summarize the status
of the network. In macros the status can be used as conditions. Click Edit to
open the Network Status for Condition dialog box, where you can define
further options.
Panel Status Information the system uses during general operation to summarize the status
of the panel. In macros the status can be used as conditions. Click Edit to
open the Panel Status for Condition dialog box, where you can define further
options.
Unmasked Input Unmasked inputs are not affected by any alarm reporting criteria. An
unmasked input is active whenever the sensor is active. Any input can be used
as masked or unmasked. The associated number is the input number.
Tamper State Triggered when an RS485 devices tamper input is activated. The associated
number is the RS485 address of the device.
Offline State Triggered when an RS485 device goes offline. The associated number is the
RS485 address of the device.
Point Category Triggered when any input of a particular programmable input goes into alarm.
Click Edit to open the Point Category for Condition dialog box, where you can
select the category and set whether or not it is to be triggered by the masked
or unmasked status.
Analog Input Allows a trigger based on the current value of an analog input being greater or
less than a set value. Click Edit to open the Analog Input for Condition dialog
box, where you can select the input and set the threshold levels for when the
input is considered active.
Time Zone Active during a particular days and times (time schedules). Click Tz to open
the Time Zone Number dialog box, where you can define the days and hours
during which the condition can be met.
Advanced Condition Provides access to additional macro conditions (for example, when a "Battery
Low", "Alarm Restored", "Open Circuit" condition occurs for an input device)
using the Extended Macro Conditions dialog box (see Using Extended Macro
Conditions 187 ).
After you select a condition, a number of further controls in the Macro Conditions and Functions region
appear. Change details as required:
Enable the ! option to impose a NOT function to the condition.
The list to the right of the condition are is for selecting the trigger, input, output, bit or timer number for the
condition. When you select a trigger, the number in this field is set to the macro number where the trigger is
defined. For certain conditions a button appears. Clicking it opens a dialog box where you can further define
the condition.
The second list to the right of the condition is for selecting a logical function for the next condition. Selecting
OR or AND will display similar fields for defining the next condition. For the last condition in the macro, set
this field to Then to lead the macro into the Action region. Setting this field to None disables the macro (no
action is taken).

In the Action region select the first action to perform. Depending on the type of action you select, a variety of
parameter fields appear so you can enter the parameters in the required format. Each action has an
associated number and their required parameters are as follows:
Note: An Area mask is represented by a series of checkboxes that appear below an action requiring you
to select which alarm areas are affected by the action. Enable the checkbox next to an area to include it in
the selection.
A Zone Number corresponds to the Input Number to which the sensor for that zone is connected.
Pseudo Number refers to the Trigger Number as set in the event driver configuration.
Using Extended Macro Conditions

Extended macro conditions are additional to the standard list (detailed above) and are presented through the
Extended Macro Conditions dialog box. To access the dialog box, select Advanced Condition, then click Edit
(appears when Advanced Condition is selected).
Click the Extended Condition list to view the additional conditions:
Alarm Triggered when an alarm event is sent from a specific input point (1 - 256).
Restored Triggered when a specific input point (1 - 256) receives a restore command.
Open Circuit Triggered when a specific input point (1 - 256) sends open circuit event.
Closed Circuit Triggered when a specific input point (1 - 256) sends a closed circuit event.
Trouble Triggered when a specific input point (1 - 256) sends a trouble event.
Suspicion Triggered when a specific input point (1 - 256) sends suspicion event.
Battery Low Triggered when a specific input point (1 - 256) sends a battery low event.
Tamper Triggered when a specific input point (1 - 256) sends a tamper event.
Isolated Triggered when a specific input point (1 - 256) receives an isolate command.
Soaked Triggered when a specific input point (1 - 256) receives a soak command.
Vault Door Open Triggered by a specific input point (1 - 256), indicating a vault door is physically open.
Vault Seismic Alarm Triggered by a specific input point (1 - 256), indicating a vault seismic detector has
gone into an alarm state.
Vault Unlocked Triggered by a specific input point (1 - 256), indicating a vault door is unlocked [but
not physically open].
Vault Tampered Triggered by a specific input point (1 - 256), indicating a vault controller has been
tampered with.
Vault Offline Triggered by a specific input point (1 - 256), indicating a vault controller is offline to
the Controller.
Power Monitor Fuse Triggered by a specific input point (1 - 256), indicating that the power monitor fuse-
Failed fail circuit has detected a faulty fuse in the power supply.
Power Monitor AC Triggered by a specific input point (1 - 256), indicating that the power monitor AC fail
Failed circuit has detected an AC supply failure to the power supply. That is, the power
supply is using backup power (if available).
Power Monitor Triggered by a specific input point (1 - 256), indicating that the power monitor has
Battery detected a backup battery not operating within acceptable limits. That is, the battery
could be under or over voltage.
Power Monitor Triggered by a specific input point (1 - 256), indicating that the power monitor has
Temperature Failed detected that the power supply temperature not operating within acceptable limits.
That is, the power supply could be too hot.
Power Monitor No Triggered by a specific input point (1 - 256), indicating that the power monitor has
Battery detected that no backup battery is connected to the power supply.
Power Monitor Triggered by a specific input point (1 - 256), indicating a power supply (with power
Tampered monitor) has been tampered with.
Power Monitor Offline Triggered by a specific input point (1 - 256), indicating a power supply (with power
monitor) is offline to the Controller.
The list adjacent to the Extended Condition list allows you to select a specific input point to associate the condition
with.

8. Select And to define another action and so on.

9. Click Next to define another macro, Prev to view or edit a previous macro, OK to exit and save all macros, or
Cancel to exit without saving.
Note: There is a finite amount of space available in the Controller memory for storing macro code. The
title bar of the Macro Configuration dialog box displays available memory.
Action Numbers and Parameters
Action Number Description

00 Change the alarm system to Night mode for the selected alarm areas (1 - 8 or 32
depending on Controller type).
01 Change the alarm system to Day mode for the selected alarm areas (1 - 8 or 32
depending on Controller type).
02 Change the alarm system to Restricted Access mode for the selected alarm areas (1 -
8 or 32 depending on Controller type).
03 Allow user type Cleaner entry to the selected alarm areas (1 - 8 or 32 depending on
Controller type).
04 Allow user type Cleaner exit from the selected areas (1 - 8 or 32 depending on
Controller type).
05 Allow user type ATM entry to the selected alarm areas (1 - 8 or 32 depending on
Controller type).
06 Allow user type ATM exit from the selected alarm areas (1 - 8 or 32 depending on
Controller type).
07 Allow user type Guard entry to the selected alarm areas (1 - 8 or 32 depending on
Controller type).
08 Allow user type Guard exit from the selected alarm areas (1 - 8 or 32 depending on
Controller type).
09 Allow user type Aux1 entry to the selected alarm areas (1 - 8 or 32 depending on
Controller type).
10 Allow user type Aux1 exit from the selected alarm areas (1 - 8 or 32 depending on
Controller type).
11 Allow user type Aux2 entry to the selected alarm areas (1 - 8 or 32 depending on
Controller type).
12 Allow user type Aux2 exit from the selected alarm areas (1 - 8 or 32 depending on
Controller type).
13 Change the alarm system to Engineering mode for the selected alarm areas (1 - 8 or
32 depending on Controller type).
14 Ignore any input point activity during the selected zone (time schedule).
15 Accept any input point activity during the selected zone (time schedule).
16 Activate the selected output point for a set time in minutes or seconds.
17 Deactivate the selected output point.
18 Activate the selected CCTV camera (1 - 32) for a set time in minutes or seconds.
19 Deactivate the selected CCTV camera (1 - 32).
20 Set the selected trigger (pseudo state) to = TRUE.
21 Set the selected trigger (pseudo state) to = FALSE.
22 Set timer 1 to a set time in seconds and begin counting down.
32 Reset all input and output points in the selected areas.
33 Force setting of the selected alarm input point.
34 Force resetting of the selected alarm input point.
35 Lockout the selected keypad so that it cannot be used for access.


36 Reset the selected keypad so that it is no longer locked out, and can be used for
access.
37 Stop all PIR input points in the selected alarm areas (1 - 8 or 32 depending on
Controller type) from functioning.
38 Allow all PIR input points in the selected alarm areas (1 - 8 or 32 depending on
Controller type) to function.
39 Stop all Perimeter PIR input points in the selected alarm areas (1 - 8 or 32 depending
on Controller type) from functioning.
40 Allow all Perimeter PIR input points in the selected alarm areas (1 - 8 or 32
depending on Controller type) to function.
41 Stop all Perimeter input points in the selected alarm areas (1 - 8 or 32 depending on
42 Allow all Perimeter input points in the selected alarm areas (1 - 8 or 32 depending on
43 Stop all Vibration input points in the selected alarm areas (1 - 8 or 32 depending on
44 Allow all Vibration input points in the selected alarm areas (1 - 8 or 32 depending on
45 Stop all Vault input points in the selected alarm areas (1 - 8 or 32 depending on
46 Allow all Vault input points in the selected alarm areas (1 - 8 or 32 depending on
47 Activates the sonalert (beeping) function at the selected keypad.
48 Deactivates the sonalert (beeping) function at the selected keypad.
49 Lock the selected reader (1 - 64) so that it cannot be used for access.
50 Unlock the selected reader (1 - 64) so it can be used for access.
51 Allow a single passage through the selected reader (1 - 64).
52 Restore the selected reader (1 - 64) so that it resumes normal access controlled
operation
53 Disable the egress button associated with the selected reader (1 - 64) to prevent
exiting.
54 Ignore any door contact signals associated with the selected reader (1 - 64).
55 Enable the egress button associated with the selected reader (1 - 64) to allow exiting.
56 Accept any door contact signals associated with the selected reader (1 - 64).
57 Clear the access card passback list for the selected reader (1 - 64).
58 Reset the selected area count (0 - 25) back to zero.
59 Prevent the selected output point (1 - 64) from being activated.
60 Allow the selected output point (1 - 64) to be activated.
61 Prevent the selected CCTV camera (1 - 32) from being activated.
62 Allow the selected CCTV camera (1 - 32) to be activated.
63 Prevent the selected film camera output point from being activated.
64 Allow the selected film camera output point to be activated.
65 Force the Controller to immediately send all alarms queued on dialup.
66 Allow access to the selected floor for a set time in minutes or seconds.
67 Force the selected input point (1 - 256) to send a SNMP alarm alert message.
68 Force the selected input point (1 - 256) to send a SNMP alarm reset message.
69 Send footage from the selected CCTV camera (1 - 32), connected to a Pacom
Witness, to the local output connection (usually a monitor) for a set time in minutes
or seconds.
70 Stop sending footage from the selected CCTV camera (1 - 32), connected to a Pacom
Witness, to the local output connection.
71 Start recording footage from the selected CCTV camera (1 - 32) for a set time in
minutes or seconds.
72 Stop recording footage from the selected CCTV camera (1 - 32).
73 Instruct the system to record footage from the selected CCTV (1 - 32) as part of an
event, including settings such as pre and post recording times. This command applies
to Pacom Witness and third-party DVRs.
74 Reset any alarms on the selected reader (1 - 64).


75 Send the selected macro action command (from this list) to Controller(s). The target
Controller can be:
A single selection.
A local broadcast to all Controllers on the same linecard.
A global broadcast to all Controllers in the system.
76 Apply the Alternate Bandwidth setting (including length of time) for footage
generated by the selected CCTV camera, connected to a Pacom Witness.
77 Instruct the selected CCTV camera (1 - 32) to the selected preset pan/tilt/zoom (PTZ)
orientation.
78 Activate the buzzer on the selected reader (1 - 64) for a set time in minutes or
seconds.
79 Deactivate the buzzer on the selected reader (1 - 64).
80 Activate the green LED on the selected reader (1 - 64) for a set time in minutes or
seconds.
81 Deactivate the green LED on the selected reader (1 - 64).
82 Activate the red LED on the selected reader (1 - 64) for a set time in minutes or
seconds.
83 Deactivate the red LED on the selected reader (1 - 64).
84 Enable or disable reporting alarms on the backup line.
85 Stop the selected input point (1 - 256) from functioning.
86 Allow the selected input point (1 - 256) to function.
87 Stop the selected output point (1 - 64) from functioning.
88 Allow the selected output point (1 - 64) to function.
89 Stop door alarm reporting from the selected input point (1 - 256).
90 Allow door alarm reporting from the selected input point (1 - 256).
91 Allow access card passback operation on the selected reader (1 - 64).
92 Disable passback operation on the selected reader (1 - 64).
93 Prevent all access cards with the selected card type from having access. Card type
identifiers do not have to have an actual number, it is the position in the list of card
types that you select. For example, if you want to select a card type called
"apprentice", which is fifth in the list of card types, select 5.
94 Allow all access cards with the selected card type to have access. Card type
identifiers do not have to have an actual number, it is the position in the list of card
types that you select. For example, if you want to select a card type called
"apprentice", which is fifth in the list of card types, select 5.
95 Transmit live video from the selected CCTV camera (1 - 32) to the selected receiver
(1 - 8).
96 Stop transmitting live video from the selected CCTV camera (1 - 32) to the selected
receiver (1 - 8).
97 Force the interlock function on the door associated with the selected reader (1 - 64).
98 Force resetting the interlock function on the door associated with the selected reader
(1 - 64).
99 Set the security level (1 - 8) for the selected alarm area (1 - 8 or 32 depending on
Controller type).
100 Start exit to Night mode in the selected alarm areas (1 - 8 or 32 depending on
Controller type).
101 Stop exit to Night mode in the selected alarm areas (1 - 8 or 32 depending on
Controller type).
102 Sets the selected reader (1 - 64) to validate access cards using the facility code only.
103 Disable system ID check for reader + reader number (1 - 64).
104 Enable or disable local Controller ports.
105 Sets late work operation in the selected alarm areas (1 - 8 or 32 depending on
Controller type).
106 Allow override of the selected reader time zone (time schedule) (1 - 256) settings.
107 Prevent override of the selected reader time zone (time schedule) (1 - 256) settings.
108 Clear the passback status for all access cards that have been used on the selected
reader (1 - 64) for the current day.
109 Resets the selected pulse counter (1 - 256) back to zero.
110 Load tests the selected power monitor (1 - 256) for a set time in minutes or seconds.


111 Override PIN access control at the selected access area (1 - 256) for a set time in
minutes or seconds.
112 Extend access at the selected reader (1 - 64) for a set time in minutes or seconds.
113 Override the configured wait time setting of the selected vault controller to a set time
in minutes or seconds.
114 Reset the wait time setting of the selected vault controller to its configured value.
115 Test the selected Controller port for communications. The selected port number must
be on of the primary ports (primary, secondary or tertiary). If the test fails a
message displays in the Transaction Manager.
116 Activate the selected listen-in device (1 - 4).
117 Activate interlocks associated with the selected vault controller (1 - 256 or all).
118 Deactivate interlocks associated with the selected vault controller (1 - 256 or all).
119 Activate the open sequence associated with the selected vault controller (1 - 256 or
all).
120 Terminate the open sequence associated with the selected vault controller (1 - 256 or
all).
121 Pause the timer associated with the selected trigger (1 - 256). That is, the selected
trigger must have an associated condition that has some from of countdown timer,
which will be paused. For example, a condition to trigger pausing the open timer of a
vault controller.
122 Resume the timer associated with the selected trigger (1 - 256). That is, the selected
trigger must have an associated condition that has some from of countdown timer,
which will be resumed from a paused state.
Macro Examples
The following example macros show you how conditions must be set to achieve the desired result.
Example 1:
In the macro shown above, the conditions are set as follows:

The conditions are Edge Triggered. That is, once the conditions are met the macro will run and is not affected
by the state of the conditions until they are reset.
The action is performed when trigger #1 (as defined in the event driver) is active AND unmasked input #72
inactive (! option enabled). The input is unmasked, which means that the input is active any time that the sensor
goes into an active state and is not be affected by any conditions that may have been placed on it to prevent it
from triggering an alarm during certain modes or conditions.
The action will also be performed at any time when masked input #3 is active. This is achieved by selecting OR
between the second and third conditions. THEN the action is defined as follows:
Change area 1 to Night mode AND activate output #15 for 10 minutes.
This example is summarized as:

Note: Note how the AND function takes priority.
Example 2:
The following example further refines macro example 1 by changing the conditions to look for either trigger #1 being
active AND unmasked input #72 inactive OR trigger #1 being active AND masked input #3 active. That is, trigger
#1 must be active for either condition to be met.
Example 3:
The following example demonstrates how a timer set in one macro is then utilized in a second macro to perform
further actions when the timer expires.

In the above example the conditions are set as follows:

The conditions are Edge Triggered.
Perform the action when unmasked input #1 AND unmasked input #2 are both active. THEN perform the
following action:
Set Timer #1 to 60 seconds (the timer begins immediately) AND lockout keypad #7 AND activate output #1 for
five seconds.
To use the timer set in the example above, click Next to define macro #2.
In the example above, the condition for this macro is that timer #1 (set in the previous macro) expires.
The conditions are set as follows:
The condition is Edge Triggered.
Perform the action when timer #1 has expired. THEN perform the following actions:
Force alarm input #1 to reset AND reset the locked out keypad #7.

Using Hardware Serial Numbers

Pacom hardware can notify GMS of its serial number. Pacom uses serial numbers as a means for tracking licensed
hardware features. For example, to enable Inovonics features, contact Pacom and supply the Controller serial
number. When the license is purchased, Pacom supplies an activation code that you use to enable the feature.
GMS not only keeps a record of hardware serial numbers, but for I/O devices, will also associate port settings with
the physical device using the serial number. For example, if an I/O device is moved to a different mezzanine port on
the Controller, GMS will recognize the same piece of hardware on a different port and will "move" with it the ports
previously configured for it. That is, port numbers and configuration settings.
Requesting Hardware Serial Numbers

To request hardware serial numbers, proceed as follows:
2. In the Controller dialog box, select View > Controller Licenses. The Controller License Options dialog box
opens.
The Controller and attached expansion card serial numbers are shown at the top of the dialog box.
Note: In the case of 8001 Controllers, the serial numbers for attached mezzanine cards are also shown.
Enabling and Disabling Features and Options

To enable licensed features or options, proceed as follows:
1. Obtain the Controller serial number (see Requesting Hardware Serial Numbers 194 ).
2. Contact Pacom to obtain the required activation code.
3. In the Controller License Options dialog box, click Enable for the required feature. The License Update dialog
box opens.
4. In the Enter Code field, type the activation code, then click OK.
The hardware feature or option becomes enabled and is shown as enabled in the Controller License Options dialog
box.
To disable a feature or option, click Disable for the required feature and use the required activation code to confirm
the action.

Contact ID and SIA Event Codes

You can assign an individual Contact ID or SIA event code to any configured device input point (see Configuring
Device Input Points 142 ) provided that a Controller Modem (dialup) port is set up to communicate using either format
(see Configuring Ports 25 ).
Use the Contact ID Event Codes 195 and SIA Event Codes 196 tables below to determine the codes to apply to various
alarm type messages.
Contact ID Event Codes

Note: If Undefined is selected when configuring Contact ID, a 130 Burglar is sent to the monitoring
center, except for Fire Point, which is reported as 110 Fire Alarm.
Alarm Type Event Code Alarm Type Event Code

Normal Alarm Undefined Environment 152 Refrigeration
130 Burglar Point 153 Loss of heat
140 General Alarm 157 Water Tank
100 Medical 158 High Temperature
120 Panic 159 Low Temperature
121 Duress 161 Loss of air flow
146 Silent Burglar 162 Carbon Monoxide detected
Tamper Undefined 163 Tank level
Point/24Hr 137 Tamper
PIR Point Undefined Final Set Point Internal used only
132 Interior Alarm Cancel Internal used only
Point
PIR Perimeter Undefined Vault Point Undefined
131 Perimeter 130 Burglar
Perimeter Undefined 132 Interior
131 Perimeter Vibration Point Undefined
Environment Undefined 132 Interior
Point 150 24 hour non Burglar Shunt Point Undefined
151 Gas Detected 132 Interior
Lock Set/Unset Undefined Fire Point 201 Low Water
Point 409 Key Switch open/closed 202 Low CO2
Fire Point Undefined 203 Gate Valve sensor
110 Fire Alarm 204 Low water level
111 Smoke 205 Pump Active
112 Combustion 206 Pump failure
113 Water Flow 373 Fire Loop Trouble
114 Heat Raid Point Undefined
115 Pull Station 122 Silent
116 Air Duct Day Delay Undefined
117 Flame Alarm 132 Interior
118 Near Fire Alarm Internal used only
Confirmation
200 Supervisory Alarm

SIA Event Codes

Note: If Undefined is selected when configuring SIA, a Fire Point is reported as FA Fire Alarm, Raid Point
is reported as PA Panic Alarm, Alarm Cancel is reported as OC Cancel Report, Lock Set/Unset is reported
as OG for Entry (Unset), and CG for Exit (Set). All other points are reported as BA Burglar Alarm.
Alarm Type Event Code Alarm Type Event Code

Normal Alarm Undefined Vault Point Undefined
BA Burglar Alarm BA Burglar Alarm
UA Remote Power Supply Vibration Point Undefined
MA Medical Alarm BA Burglar Alarm
PA Panic Alarm
HA Holdup Alarm Shunt Point Undefined
Tamper Undefined BA Burglar Alarm
Point/24Hr TA Tamper Alarm Lock Set/Unset Undefined
PIR Point Undefined Point OP/CL Open/Closed
BA Burglar Alarm Fire Point Undefined
PIR Perimeter Undefined FA Fire Alarm
BA Burglar Alarm SS Supervisory Alarm
Perimeter Undefined FT Fire Trouble
BA Burglar Alarm Raid Point Undefined
Environment Undefined HA Holdup Alarm
Point UA Remote Power Supply Day Delay Alarm Undefined
Final Set Point Internal used only UA Remote Power Supply
Alarm Cancel Internal used only Alarm Internal used only
Point Confirmation

Chapter 4
Configuring Access Control
197
Access control allows the security system to control and monitor the movement and location of personnel throughout
a site. Access control is accomplished with the combination of GMS software, Controller software/firmware, and
Pacom 1064 and 1076 Single and Dual Card Reader Interfaces (CRIs). The 1064 and 1076 act as the local hardware
interface for various types of third-party card reader devices and associated electronic door lock devices.
Note: For information on the installation of access control hardware, see the Pacom 1064 and 1076
Installation Manuals.
Within any given system the level of access control implementation can vary widely. It can range from a simple
system, with a single card reader on the front door for controlling access to the premises during restricted hours of
the day, to a fully controlled premises, divided into secured areas by controlled access points using sophisticated
readers that enable tracking and monitoring of users throughout a premises.
Access to secured areas can be limited to particular cardholders or types of cardholders, during certain times, modes
or in various circumstances. Cardholder access to secured areas is controlled by assigning a range of options and
parameters to the areas themselves, or to individual readers or cardholders.
Note: Cardholder options are covered in the Using GMS - Operator Guide, Using the Card Access Manager.
Cardholder options are not discussed in this section, except where they directly effect or are affected by
hardware options or parameter settings.
GMS has an integrated reporting module that you can use to produce reports on any card access transaction data. For
example, reports can be made on the number of users passing through a particular door or area, or about individual
cardholder activities. Time and attendance (T&A) reports can be created on cardholder activities for payroll purposes.
Stand-Alone Readers
Stand-alone readers are the cheaper and more commonly installed method of controlling access. A stand-alone
reader is where a single card reader is placed on each door and access is controlled on entry to the area only. In
some cases a door may use a lock that can be opened from the inside, or an egress button can be connected to the
reader to unlock the door, for exit.
Egress buttons may also be installed when there is a door lock that can be opened from the inside. The button is used
to mask out the door contacts during the Shunt Time (see I/O parameters 209 tab in Configuring Readers 204 ) and
prevent a "Forced Door" alarm from being sent when the door is opened.
When stand-alone readers are used, the system cannot monitor who is actually in the area, and certain functions that
require in/out readers are not possible.
In/Out Readers
An in/out reader is a pair of card readers mounted on a single access point. Each reader is used to control access in a
single direction through the access point. Readers can be connected as:
Two master readers that have their own door contact inputs (from the same door) and the strike can be
connected to both readers in parallel. Separate one-way doors can also be used with this configuration for high
traffic areas. Master readers connected to the same door do not require consecutive reader numbers.
A master/slave pair, where the door contacts and strike output are connected to the master reader, and the
slave reader monitors the door contacts of the master reader and activates the master reader strike relay. A
slave reader must be the next consecutive reader number from its associated master.
Note: Sending commands to one reader in an in/out reader pair does not affect the operation of the other
reader. For example, sending a lock command to the "in" reader will not lock the associated "out" reader.
Readers are setup in an in/out configuration to allow the system to keep track of all users entering and leaving
individual areas. This determines the location and/or the number of users within a site or area. For the system to
work, all access points to any secured area must be controlled.
Note: The system keeps track of the area a user is in and, before accepting the new area after a valid
read, the system checks that the door has actually been opened. If the door contacts are not connected,
the Shunt Time setting can be set to 0 so that the user is accepted to the new area immediately upon a
valid read.
Each in/out reader is programmed using the areas that they are in and control access to. These are the Area No.
Leaving and the Area No. Entering parameters. The Area No. Leaving setting is the same number as the Area
Number (the location of the reader). When you assign these parameters the easiest way to identify the correct area
to enter is to draw a diagram of all the areas and the location of the readers within them.
198 | Chapter 4 - Configuring Access Control

An extension to in/out readers are parking lot readers. The system keeps a count of the entries/exits and compares it
with the area profile configuration (see Configuring Area Profiles 202 ). For example, when the car park is full, it could
trigger an event, such as activating an output to turn on a "Car Park Full" sign or to change modes. You can program
the output in the access area profile configuration (see Configuring Access Area Profiles 202 ). As in the above
example, a GPO is activated while the count for the area remains at or above the maximum. This output is ignored if
the count is set to 0. If the system is only concerned with the number of valid cardholders in the area (parking lot in
this example) and not identities, an input device, such as a push button, can be used to allow egress from the area
and command the system to decrement the number of cardholders still present.
PIN Codes and Keypads

Card access can also be combined with PIN (personal identification number) code entry using a keypad device. You
can assign users a PIN code in addition to being a cardholder. This enables you to set up extra security, for example,
swiping a card before or after entering a PIN for access. In addition, you can assign these kinds of functions in
accordance with time schedules, so that they are valid only during certain times of the day or on certain days. The
system can also be programmed to allow PIN entry during certain modes only, or a combination of modes/times/
days. See Configuring Keypads 215 .
Interlocks
In some instances you may want to ensure that one door is closed before another is opened and vice-versa. For
example, if there are two access controlled doors that lead to a high security area, you can interlock them so that no
other person can open the first interlocked door whilst the second door is currently open. Once the second door is
closed and locked, the first door can be opened again. Interlock doors from their associated reader configuration.
Each reader/door can be interlocked with up to eight others.
Chapter 4 - Configuring Access Control | 199

Note: When a door is interlocked, it can only be opened through the interlock functionality. That is, it will
reject access and unlock commands or egress requests whilst interlocked.
Doors that are interlocked by another door, or are commanded into an interlocked state, will illuminate the
red LED on their associated readers.
Anti-Passback
Anti-passback is a function that prevents two users gaining access to an area using a single card. When you enable
anti-passback, the system remembers up to the last 16 cards used on the reader, and can optionally do so for a set
amount of time. These cards will not be allowed access to the reader again until they drop out of the remembered
list, time out, or are reset by using another reader. There is also an option for clearing the reader passback memory
in other readers, if the card is used in a particular reader.
With peer to peer communications between Controllers, Pacom access control has the ability for "global anti-
passback". This is where the anti-passback can be reset using any reader, including those connected to other
Controllers.
Note: You can assign anti-passback functionality to stand-alone readers only. In/out readers do not
require anti-passback as they will generate an error if a card is used to attempt entry to the same area
twice, without exiting.
Degraded Mode
Under normal operating conditions the Controller performs all access processing. Degraded mode occurs when the
reader becomes disconnected from the Controller. The reader will allow entry to cards with specific facility codes to
enter certain areas. There are two forms of degraded operation.
Option 1 - When the reader first comes online, a Master card is downloaded to the reader and stored in non-
volatile memory. If the reader goes offline, the Master card is always allowed access.
Option 2 - As each valid transaction occurs while the reader is online, an instruction is sent to the reader to
store a configurable part of the code read in to non-volatile memory (maybe the facility and/or issue, or the
whole card number), so that in degraded mode, any card that matches this code is validated. Up to 256 codes
can be stored in a 1064 card reader interface, and up to 1000 in 1076 models (these values are based on the
26-bit Weigand format. Higher bit counts per card reduce the maximum number.). The reader can be
programmed to store individual users (selectable in the user configuration). If the masked part of the code is
already in the table, the entry is not stored. This ensures that there are no repeated entries in the list. In
addition to this, the 1076 can store 500 offline transactions per reader.
To configure degraded mode operation, see Configuring Degraded Mode Operation 231 .
Time Schedules
User Time Schedule Profiles

User time schedule profiles define access times to readers and are assigned to cardholders. The system allows for up
to 100 time schedules and up to three individual time ranges (shifts) per day. Each time schedule entry has a start
and end time (in multiples of ten minutes) for each day of the week (starting at Sunday). Holidays are also
programmable. See Configuring Reader Time Schedules 223 .
Holidays Per Time Schedule

If the Holidays option is selected in the time schedule profile, the system checks the Yearly Calendar 224 to see if the
day is programmed as a holiday. If it is, the hours in the Holiday field are used. If it is not, Normal Hours 175 for that
day are used. If three holidays (for the three shifts) are present, the system checks all three for a match.
Reader Time Schedule Profiles

There is provision for up to 32 reader time schedule profiles that you can use when selecting output activation,
keypad operation, and locking and unlocking readers (see Configuring Readers 204 ). These cannot be used for user
time schedules, only for reader tasks. When setting up the reader in GMS, there are options for setting reader
operation during certain times.
Maximum Access Cards (Cardholders)

Access control is supported by Pacom 1057, 1058 and 8001 Controllers. Pacom Controllers store access card
information in onboard non-volatile memory, so the system can continue operation even if connection to the
monitoring center is lost. Controllers have a finite amount of memory and can therefore store a finite number of
cards. The main factor in determining the best suited Controller for the application is the number of cards that it
needs to support.

You can expand Pacom Controller memory to increase the number of cards supported by adding SRAM memory cards
(SRAM) to the dedicated slot on the Controller PCB. The SRAM is proprietary Pacom hardware and must be purchased
through Pacom.
Note: 1057 revision 5+ and 1058 revision 4+ are required for 16 or 32MB memory cards. If you place a
16MB or 32MB memory card into an old revision Controller, it will still operate, but only using up to 4MB of
available memory. The 1058 Controller can support a maximum of 10,000 cards.
Maximum Numbers of Access Cards

Configuration 1057 1058 8001
Standard (no expansion) GMS 3.xx - 4.00+ 9235 1,000 9235
With 4MB expansion GMS 3.xx - 4.00+ 32,000 10,000 N/A
With 16MB expansion GMS 3.xx - 4.00+ 128,000 10,000 N/A
With 32MB expansion GMS 3.xx - 4.00+ 250,000 10,000 250,000
Note: GMS 2.xx with 4MB expansion on a 1057 Controller supports up to 128,000 cards and 10,000 on a
1058.

Configuring Access Area Profiles

Pacom Controllers support up to 255 access control areas that can be assigned one of up to 16 configurable profiles.
Area profiles define the operation of readers that have been configured as part of a particular area that has been
assigned that profile. The operation of some functions may differ depending on whether they are applied to in/out or
stand-alone readers. Some functions require stand-alone readers, and some functions are incompatible with in/out
readers and/or other functions.
Configuring Access Area Profile Parameters

To configure an area profile, proceed as follows:
2. In the Controller dialog box, select Access Control > Area Profiles. The Configuration for Area Profile dialog
box opens.
3. Set that area parameters according to the following table.
Area Type The access of cardholders to secured areas can be limited by assigning the
area one of four special area types:
Supervised Area - Requires in/out readers. A cardholder is designated as a
supervisor in the cardholder options. The supervisor must be present in the
area for non-supervisors to enter. The supervisor will not be allowed to leave
if they are the only supervisor and non-supervisors are still present. This
option requires in/out readers and is applied to the area number entering,
that is, the area to which the reader is granting access.
Dual Entry Area - Used to prevent any user from entering a secured area
alone. The first valid user cannot access the area until a second user is
validated. This option is used in conjunction with the Dual User Control
option in the Card Details tab for each user (see Using GMS - Operator
Guide, Using the Card Access Manager). The order in which the cards are
swiped is not important. If the access point is a type of turnstile, the reader
Dual Strike activation when Accessed option should be enabled to
activate the strike twice (see Configuring Readers 204 ). This will allow the
entry of both users once the valid transactions are complete. This option
applies to the operation of the reader that is in the area assigned this profile
and is not compatible with Supervised Area operation described above.
Supervised Dual Entry - Same as Dual Entry Area except that at least
one of the cardholders must also be designated as a supervisor in the
cardholder options. If the access point is a type of turnstile, the reader Dual
Strike activation when Accessed option should be enabled to activate the
strike twice (see Configuring Readers 204 ). This will allow the entry of both
users once the valid transactions are complete. This option applies to the
operation of the reader that is in the area assigned this profile and is not
compatible with Supervised Area operation described above.
Limited Count Area - Used in areas that have a maximum capacity. Valid
cardholders are granted access until the number of users in the area has
reached the Max. Allowed Access Count setting. The output set in
Activate when Max Access Count Reached setting will remain activated
while the maximum number of users are still present. Limited Count Area
operation requires in/out readers or a reader with egress button configured
to track the number of users.

Enable Mode Changes Card access areas 1-8 can be associated with alarm areas 1-8 respectively, for
alarm system mode change operations. When this option is enabled and a valid
card for an alarm user type (other than "normal") is read by a reader
associated with the area, the alarm system mode for the area is changed to
the mode for that alarm user type. For example, if an area is in Night mode
and a Cleaner user type swipes their card, the area is changed to Cleaner
mode operation. When the user leaves the area, the alarm system mode
changes back to the mode used before the user first entered.
Note: If Dual Mode Exit Enable is enabled, two card swipes are
required when leaving in order to change mode.
Inactivity Timer for PIN Used with Pin Entry Modes or Card Swipe after PIN Entry PIN operation
Entry (see Configuring Readers 204 ). This timer starts when a card is swiped or a
PIN is entered within the area. If the card swipe and PIN entry combination are
not completed before the timer expires, access is denied and the cardholder
will have to start again.
If you are using event drivers driven by multiple reader swipes in the access
area, this setting also determines the time limit that the swipes must occur in.
Change Mode when When enabled, this option causes the system to change modes when the Max
Maximum Count Allowed Access Count setting is reached. The system will revert to the
reached previous mode when the number of cardholders in the area falls below the
Max Allowed Access Count setting.
Dual Mode Exit Enable Used in conjunction with Enable Mode Changes, for alarm system mode
change operations. When this option is enabled and a valid card for an alarm
user type (other than "normal user") is read by a reader associated with the
area twice within a certain time, the alarm system mode changes back to the
mode used before the user first entered.
Note: This option is valid only when Enable Mode Changes is

enabled.
The timer used for detecting a "dual swipe" is the Extended Shunt/
Strike Time setting for the reader (see Configuring Readers 204 ).
Max. Allowed Access Used in conjunction with Limited Count Area operation. Determines the
Count maximum number of authorized cardholders that are granted access to the
area.
Activate when Max This is the number of the GPO (General Purpose Outlet) or trigger to activate
Access Count Reached when the Max. Allowed Access Count setting is reached. This number is the
output number (0-127) as set up in alarm configuration (see Configuring Input
and Output points 142 ). Enable the GPO or Trigger option to specify what to
activate.
Duress Code for A duress code is used when a cardholder is being forced to grant someone
Readers in This Area unauthorized access, or during any other suspicious circumstance. The
cardholder is granted access as normal so that suspicion is not aroused,
however, a duress alarm is sent to the monitoring center. The numeric code
entered in this field is the duress PIN for this area only.
Duress Code at End Enable to allow users to use the Duress Code for Readers in This Area
setting, after entering their PIN.
Duress by PIN Enable to allow users to send a duress signal to the monitoring center by
Incremented by 1 entering their PIN with the last digit incremented by one. For example, a
normal PIN of "4855" would send a duress signal if it is entered as "4856".
Master Code for Sets the master access card code for Degraded mode 200 reader operation.
Degraded Mode This setting is stored in the area readers and always allows the card with this
code to access the area during degraded mode.
Copy From Area No. Enter the number of an area with the same or similar parameters in this field
to copy its settings to the area.
4. Click OK to close the dialog box and download the settings to the Controller.

Configuring Readers
There are various options available for controlling the operation of card readers. The Configuration for Reader dialog
box has a set of common controls for selecting readers and configuring their address and other general details, and a
number of tabs for setting specific reader parameters and options.
To configure readers, proceed as follows:
2. In the Controller dialog box, select Access Control > Hardware > Readers. The Configuration for Reader
dialog box opens. Use the following sections as a guide to available parameters.
Setting Common Reader Properties

These settings are required for every reader and are always visible in the Configuration for Reader dialog box.
Reader No Select a card reader by typing a number in the adjacent field and clicking Reader
Number. Or, use and to scroll through all readers. All configuration options are
applied to the reader with the ID number displayed here.
of Shows the total number of configured card readers.
Device Address The unique RS485 address (1-256) of the reader (see Setting Device Addresses and
Address Ranges 204 ).
Address Range Shows the range containing the Device Address (see Setting Device Addresses and
Address Ranges 204 ).
Link Settings Shows the required PCB link settings on the Card Reader Interface (Reader 205 tab
205 ), if required, for the Device Address.
Delete Remove the currently selected reader details from the database.
Copy Opens the Copy Reader dialog box to copy settings from one reader to others (see
Copying Reader Setting To/From Other Readers 216 ).
Setting Device Addresses and Address Ranges

An RS485 device line supports up to 32 devices. Each device is assigned an address unique on that line (address 1-
32). Pacom Controllers support multiple device lines. Each device line used is assigned an address range of 32
devices (1-32, 33-64, 65-96, 97-128, 129-160, 161-192, 193-224, 225-256). When you the device address here, the
address set on the device (1-32) is combined with the address range, to give a unique address in the range of 1-256.
To do this, add the address set on the device to the last address in the previous address range. For example, for
address range:
1-32, add 0.
33-64, add 32.
65-96, add 64.

97-128, add 96.

129-160, add 128.
161-192, add 160.
193-224, add 192.
225-256, add 224.
For example, if the device is programmed with device address 3, and it is connected to a device line that has been
allocated the 65-96 range of addresses, the device address should be entered as 67 (3 + 64).
The address ranges of device lines do not all have to be different, as long as the individual device addresses are kept
unique. The total number of devices must not exceed 32 for lines assigned the same range.
Selecting Reader Types and Functionality

These settings determine the actual reader make and model as well as its base functionality. Proceed as follows:
1. In the Configuration for Reader dialog box, click the Reader tab and configure the reader according to the
parameters below.
Reader Interface Select the card reader interface that the reader is attached to. Options are:
Undefined - Not in use.
Local Proximity Type - Connected directly to a serial port on the
Controller.
Local Motorola Type - Connected directly to a serial port on the Controller.
Local Fingerscan Type - Connected directly to a serial port on the
Controller.
Pacom 1061 Type - Using a Pacom 1061 keypad with reader.
Pacom 1065 Type - Using a Pacom 1065 I/O module with reader.
Pacom 8101/1062 CRI Type - Using a Pacom 8101 or 1062 keypad with
internal or external reader.
Pacom 1064 CRI Type - Using a Pacom 1064 (CRI).
Pacom 8101/1062 Type - 8101 or 1062 keypad used in access control
mode as a PIN pad.
Pacom 1067/1076 IF1 Type - Using a Pacom 1067 or 1076 Interface A.
Pacom 1067/1076 IF2 Type - Using a Pacom 1067 or 1076 Interface B.
Wyreless Access Point (WAP) - Using a Wyreless Access Point device.
Note: The device address of a WAP configured using third-party

software must be incremented by 1 to be compatible with GMS. For
example, if a WAP is configured in the third-party software as address
"3", it is configured in the device address as address "4".
Timecon TTC Reader - Using Timecon TTC Reader.

Virtual Door - Using a Controller to send door commands to a third-party
access control panel.
Timecon (spare) - Reserved for future use.

Pacom 8102 128x64x1 Access - Reserved for future use.
Pacom 8102 128x64x1 - Reserved for future use.
Pacom 8102 256x64x16 Access - Reserved for future use.
Pacom 8102 256x64x16 - Reserved for future use.
Aperio - Using Aperio wireless lock-readers connected to an Aperio hub.
Alarm Areas - Using a "phantom" reader for cardholder PIN alarm area
mode changes (see Using Cardholder PINs for Alarm Area Mode Changes 216
).
Reader Type Select the installed reader type from the list of options. If you are setting up a
keypad, see Configuring Keypads 215 .
Note: To support Online/offline messages from a HID RK40 reader,

select Multi-Card Format. For programming multi-card format
readers, see Programming Card data Formats 218 .
Reader Category Select a category for determining reader operation. Options are:
No Special Category - Unused.
Anti-Passback Enabled - Sets the area for anti-passback to prevent the
same card from being used to gain access through the same door more than
once. The method of passback reset can be set for timer and/or by a count
of users according to the following settings.
Passback Time - Set the time that a card is denied access after it has been
used on the reader. This setting is in seconds unless the Time in Minutes
option is enabled.
Passback Count - Set the number of other cards that need to be used on
the reader before a card that has been used on the reader can gain access
again.
Note: Anti-passback operation is automatically implied when using in/

out readers.
IN/OUT Master Type Reader - Used in conjunction with in/out slave

readers (see In/Out Readers 198 ).
IN/OUT Slave Type Reader - Used in conjunction with in/out master
reader (see above). The slave reader must have the next consecutive reader
number from the master reader. The Shunt and Strike times can differ
between the master and slave readers, even though the door connections
are controlled through the master.
Muster Reader - Used in situations where the users can swipe to be
registered as out of the system. For example, in the case of a fire it can be
used for the system to report if people are still in the building. If a reader is
configured as a muster reader, it will reset the area the user is currently
accessing.
Enrolment Reader - Used to enrol cards and user PINs into the system.
When a card is used the system creates a new database entry in GMS,
registering the card enrolled number.
Queuing Type - Contact Pacom Systems for information.
Area No. Entering Enter the access control area number (1-254) that the reader controls access
to.
Note: This setting applies only if the Reader Category is set to In/
Out Master Type or In/Out Slave Type (see In/Out Readers 198 ).
Area No. Leaving Shows the access control area number (1-254) that the reader controls exit
from. As this is the area where the reader is located, this defaults to the area
number.
Note: This setting applies only if the Reader Category is set to In/
Out Master Type or In/Out Slave Type (see In/Out Readers 198 ).
Area No. Enter the access control area number for the reader (1-254).

Configure Area Click to open the Configuration for Area Profile dialog box, where you can
configure the area profile for the area entered in the Area No. field (see
Configuring Access Area Profiles 202 ).
Format 1 Select the access card data format from the list. The options are
If the access card data is not a standard configuration, you can program the
reader for the required data format by clicking Configure (see Programming
Card Data Formats 218 ).
Note: If the Reader Type setting is Multi-Card Format, you can

select up to four other card data formats.
Setting Reader LED Control

These settings determine the reader LED and buzzer behavior. Proceed as follows:
1. In the Configuration for Reader dialog box, click the LED Control tab and configure the reader according to the
parameters below.
Accept LED Control
Duration to Activate for Enter the time (in seconds) that the green LED is lit on the card reader after
Valid Card a valid card has been read.
Flash During Activation Enable to flash the green LED (instead of just being lit) during the Duration
for Valid Card to Activate for Valid Card time.
During Unlock Select a behavior for the green LED while the door is unlocked/open. Options
are On, Off or Flashing.
During Embarrassment Select a behavior for the green LED during the Embarrassment Timer
setting (I/O Parameters 209 tab). Options are Do Nothing, Flash, On or
Flashing then On.
Denied LED Control
Duration to Activate for Enter the time (in seconds) that the red LED is lit on the card reader after a
Denied Card invalid card has been read.
Flash During Activation Enable to flash the red LED (instead of just being lit) during the Duration to
for Denied Card Activate for Denied Card time.
During Lock Select a behavior for the red LED while the door is locked. Options are On,
Off or Flashing.
During Embarrassment Select a behavior for the red LED during the Embarrassment Timer setting
(I/O Parameters 209 tab). Options are Do Nothing, Flash, On or Flashing
then On.
Denied LED Control During Read Error
Duration to Activate for Enter the time (in seconds) that the red LED is lit on the card reader after a
Read Error read error.
Flash During Activation Enable to flash the red LED (instead of just being lit) during the Duration to
for Read Error Activate for Read Error time.

Unlabelled List Select a behavior for the buzzer during the Duration to Activate for Read
Error time. Options are No buzzer during error, Buzzer On during error
or Beep during error.
Buzzer Control
For Valid Card Select a behavior for the Card Reader Interface buzzer when a valid card is
swiped. Options are No buzzer, Continuous or Pulse.
During Embarrassment Select a behavior for the Card Reader Interface buzzer during the
Embarrassment Timer setting (I/O Parameters 209 tab). Options are No
buzzer, Continuous, Pulse. or Pulse and then Continuous.
For Invalid Card Select a behavior for the Card Reader Interface buzzer when an invalid card
is swiped. Options are No buzzer, Continuous or Pulse.
During Interlock Select a behavior for the Card Reader Interface buzzer during reader
interlocking (see Interlocks 199 ). Options are No buzzer, Continuous or
Pulse.
Inhibit Heartbeat Pulse Enable to stop 1064 Card Reader Interface PCBs from flashing their
operational LED. By default, the 1064 LED flashes every 10 seconds to
indicate that it is operating.
Note: This setting functions with a 1064 CRI with firmware 4.07 or
above. A 1064 with firmware lower than 4.06 will not flash at all. A
1064 with firmware 4.06 will flash every ten seconds, regardless of
the flag status.
Setting Reader Time Schedules (Timezones)

These settings determine automated reader functionality according to time schedules. Proceed as follows:
1. In the Configuration for Reader dialog box, click the Timezones tab and configure the reader according to the
parameters below.
TZ no. Click to open the Configuration for Reader Timezone dialog box, where you
can select, edit or create a time schedule to apply to the relevant function
(see Configuring Time Schedules 223 ). Any selected time schedule ID
number is shown beside the relevant option
to Inhibit Alarms During the selected time schedule, door alarms from the reader will not be
reported.
to Keep Reader Locked During the selected time schedule, the reader is locked automatically.
to Keep Reader Unlocked During the selected time schedule, select this option for the door to be
unlocked automatically.
for Entry of PIN Required: During the selected time schedule, the system will prompt the reader for
PIN entry for users requiring PIN operation.
for System ID Only During the selected time schedule, the reader will only check the facility
Required field of the access card for the transaction.

Note: Time schedule operation for lock and unlock overrides any manual lock/unlock command sent to the
reader from the GMS Reader/Elevator Status dialog box unless the Enable Timezone Override option is
also selected.
Setting Reader Modes

These settings determine automated reader functionality according to its area mode. Proceed as follows:
1. In the Configuration for Reader dialog box, click the Modes tab and configure the reader according to the
parameters below.
Auto-Lock Modes Select to allow the system to automatically lock the reader when its area is in
any of the modes selected in the Modes region (beneath).
Auto-Unlock Modes Select to allow the system to automatically unlock the door when its area is in
any of the modes selected in the Modes region (beneath).
Pin Entry Modes Select to allow the system to automatically unlock the reader, but require a PIN
for access, when its area is in any of the modes selected in the Modes region
(beneath).
Inhibit Alarm Modes Select to allow the system to prevent the reader reporting alarms when its
area is in any of the modes selected in the Modes region (beneath).
Modes Enable the checkbox next to each mode for it to perform the functions as
detailed above while that area is in that mode.
Setting Reader Input/Output Parameters

These settings determine various timed reader functions and switching that it performs after being activated. Proceed
as follows:
1. In the Configuration for Reader dialog box, click the I/O Parameters tab and configure the reader according to
the parameters below.

Debounce Time for Door Enter a time (in milliseconds) for the system to wait for activation to restore
Contact the door input. You can filter noisy or poor contacts digitally by setting longer
debounce times.
Debounce Time for Enter a time (in milliseconds) for the system to wait for activation to restore
Egress Input the egress input. You can filter noisy or poor contacts digitally by setting longer
debounce times.
Debounce Time for Enter a time (in milliseconds) for the system to wait for activation to restore
Strike Input the strike input. You can filter noisy or poor contacts digitally by setting longer
debounce times.
Invert Strike Output Enable to reverse the polarity of the strike output relay so, for example, that
Relay "closed" become "open".
Invert Door Contact Enable to reverse the logic or state of the door contact so for example, that an
"alarm" report becomes "secure".
Invert Egress Input Enable to reverse the polarity of the egress input so, for example, that an
Invert Strike Input Enable to reverse the polarity of the strike input so, for example, that an
1076 Spare Output 1076 (and 1067) Card Reader Interface PCBs are equipped with an extra
Operation output point that you can activate in set circumstances. For example, to turn
on a light (see Configuring Input and Output Points 142 ). Options are:
None - Never activate the output.
Activate during shunt timer - Activate the output during the Shunt Time
timer.
Activate on extended access - Activate the output during any extended
access timer (Extended Shunt/Strike Time, Warning Time and
embarrassment timers).
Strike Time Enter the number of seconds that the door is unlocked for after a valid card is
read.
In Minutes - Enable this option to count the Strike Time setting in
minutes.
Permanent - Enable this option leave the door unlocked.
Shunt Time Enter the number of seconds that the door contact alarm will be masked for
after a valid card is read.
In Minutes - Enable this option to count the Shunt Time setting in
minutes.
Permanent - Enable this option leave the door unlocked.
Extended Shunt/Strike Enter the number of seconds to add to the Shunt Time and Strike Time
Time settings for cardholders with the Extended Shunt/Strike Time option
enabled in their cardholder profile (take longer to get through doors) (see
Using GMS - Operator Guide, Using the Card Access Manager).
This timer is also used when using access card swipes for alarm system mode
changes in the area. The access area profile must be set for mode change
operation, using the Enable Mode Changes option (see Configuring Access
Area Profiles 202 ), then each card swipe causes a mode change.
If the Dual Mode Exit Enable option is also selected for the area, two card
reads are required for the system to change mode, and:
If the Extended Shunt/Strike Time setting = "0", each card swipe causes
a change to Day mode.
If the Extended Shunt/Strike Time setting = "0", a card swipe and "*0"
plus PIN entry causes a change to Night mode.
If the Extended Shunt/Strike Time setting > "0", each card swipe causes a
change to Day mode.
If the Extended Shunt/Strike Time setting > "0", a card swipe and "*0"
plus PIN entry causes a change to Night mode.
Note: Mode changes using card swipe and PIN entry requires the
reader to have the Set to use '*' as part of PIN data option enabled
- see Setting Keypads and Interlocking Readers 211 and the cardholder
to have the Use PIN to Access option enabled as well as be a User
Type other than "normal user" - see Creating New Cardholders).

Warning Time Enable this option for a second embarrassment timer to count down before an
alarm is reported, or activating an output. When selected, the Door warning
to start after strike and Door warning output fields appear in place of the
Extended Shunt/Strike Time and Remote I/O Address settings.
Door warning to start Enter the number of seconds after the strike has been activated before
after strike activating the Door warning output to signify the door being open. This
setting is displayed when Warning Time is selected.
Embarrassment Timer Enter the number of seconds after the strike has been activated before
to start after the Strike sounding the beeper to signify the door being open.
Remote I/O Address This setting is used when the door strike and door contact are controlled by a
remote device, so that the wiring for the door contacts cannot be accessed by
ripping devices from the wall. This parameter is the RS485 address of a 1064
where the remote contacts are connected. 0 = not used.
Door warning output Select an output to activate after the Door warning to start after strike
(second embarrassment timer) setting expires (see Configuring Input and
Output Points 142 ). This setting is displayed when Warning Time is selected.
Door Lock Mode This setting controls the locking behavior the door strike mechanism after a
valid card swipe and is designed for different functionality based on the door
lock type. Options are:
Normal Strike Operation - Select to make the door strike reset as soon as
the door is opened. If the door is not opened, the strike resets after the
Strike Time setting expires.
Door Bolt Mode - Select for electronically operated door locking bolts,
where after the door is opened, the system waits for it to be fully closed
again, regardless of Strike Time setting, before power can be applied to the
locking bolt.
Magnetic Lock Mode - Select for electronically operated magnetic door
locks, where after the door is opened, the system waits for the Strike Time
setting to expire before re-energizing the magnetic lock.
Note: Whenever an opened door is closed it is immediately locked,

regardless of lock mode.
Setting Keypads and Interlocking Readers

These settings determine how reader interacts with other readers and which keypad it is assigned to. Proceed as
follows:
1. In the Configuration for Reader dialog box, click the Keypads/Interlock tab and configure the reader according
to the parameters below.
Antipassback Interlock Enable to prevent a card entering more than once through the same reader,
or any other reader that it is interlocked with, before the card has exited
(see Anti-Passback 200 ).
Keypad Device Address Enter the hardware address of the keypad to obtain PIN entry for the reader.

Enable Input for Enable to allow the reader to be unlocked when the Input no. for
Permanent Unlock Permanent Unlock input is activated.
Input no. for Permanent Enter an input number that will unlock the reader when it is activated
Unlock (through alarm operation). When the input is restored, the reader is also
restored.
Keypad Configuration - These options appear only when the Reader Type setting is a keypad and the
Reader Interface setting is a Pacom 1064, 1067 or 1076 type (set in the Reader 205 tab).
Inactivity Timer Enter the time in seconds that the keypad allows after each key press before
the user must re-enter their PIN.
No. of Digits to Enter Enter the number of digits that make up a valid PIN code.
Note: GMS requires a minimum PIN length of four digits.
Set to use '*' as part of When selected, the reader will send all PIN data to the Controller, including
PIN data asterisk ("*") characters. This is required for readers that are configured for
mode changing on entry, in order to change mode back again on exit. For
example, a user enters through the reader, causing a change of mode. Then
on exit, the mode can be changed back again by the user entering "*0"
followed by their PIN.
Note: The profile for the alarm area associated with the reader must
have the Dual Mode Exit Enable option selected (see Configuring
Access Area Profiles 202 ) for this feature to work.
Interlock Parameters
Readers to be Enable the checkbox next to each reader number to interlock it. The reader
Interlocked will only allow access if all other readers that it is interlocked with are closed.
Use interlock bytes for Enable so that the Controller memory bytes usually used to store information
elevator addr about interlocked readers is used to store the address of the 1065 Elevator
Controllers used for controlling each group of 16 floors. This option is
displayed when the Elevator Reader option is enabled (Flags 212 tab).
Floor Relays Controller Enter the RS485 address of the 1065EC controlling each range of 16 floors.
Address For the installation and configuration of elevator control, see the Hardware
Installation Guide. These settings are displayed when the Elevator Reader
option is enabled (Flags 212 tab).
PIN Operation
Within PIN Timezones or Select how users gain access using the reader. Options are:
PIN Modes Card Only - Users must swipe a valid access card.
Card Swipe before PIN entry - Users must swipe a valid access card
then enter a valid PIN.
Card Swipe after PIN entry - Users must enter a valid PIN then swipe a
valid access card.
Card or PIN - Users can either swipe a valid card or enter a valid PIN.
Allow PIN/Card Swipe Enable to allows users access by PIN entry or card swipe outside any
Outside PIN Timezones specified time schedules or modes (Timezones 208 and Modes 209 tabs).
and PIN Modes
Setting Reader Flag Options

These settings determine various timed reader functions and switching that it performs after being activated. Proceed
as follows:
1. In the Configuration for Reader dialog box, click the Flags tab and configure the reader according to the
parameters below.

Dual Strike Activation when Enable to allow dual user operation with a turnstile type access point. This
Accessed allow the strike to activate twice and let two users enter after two cards
have been validated.
Report Exceptions Only Enable to report invalid transactions from the reader. No valid transactions
are reported.
Clear Pass Back Memory on Enable to clear the swiped card from the passback list (see Anti-Passback
Other Readers 200 ) of all other readers after a valid access. For example, an exit door.
Enable Strike Contact Enable for the strike input contact to report its state to the system.
Monitoring
Process Egress in the CRI Enable to allow the reader to process egress button use, to actuate the
door strike during degraded mode (see Configuring Degraded Mode
Operation 231 ).
Egress Activates Shunt Enable for when an egress button is required only to disable the door
Timer Only contact input and not activate the strike. That is, door has a handle on the
inside and the egress button is used to prevent a forced door alarm during
exit.
Store Code Locally for Enable to force the Card Reader Interface to check the access card mask
Degraded Mode and, if the mask is not stored in the CRI, it will add it to the list (see
Configuring Degraded Mode Operation 231 ).
Elevator Reader Enable for an elevator car reader for floor access control. This option also
changes the Keypads/Interlocks tab to allow the input of the Floor
Relay Controller Addresses, which are the RS485 address of the 1065ECs
used for each group of floors (see Keypads/Interlocks 211 tab).
Egress to Keep Strike Enable so the door remains unlocked whilst the egress button is pressed.
Picked
Reset User InOut when Enable so that the current user position is reset after a permanent unlock
Alarm Secured is complete. When a permanent unlock occurs, user location data is no
longer valid because they can move freely through permanently unlocked
points. Used in conjunction with the Enable Input for Permanent
Unlock setting (see Keypads/Interlocks 211 tab).
Enable Time and Attendance Enable to report valid transactions (per access control area) to the
Reports system, as "Time in Attendance Transactions". This allows GMS to provide
Time in Attendance (T&A) reports (for example, for payroll purposes).
See T&A Reporting Example 215 .
Enable Alarm User Pins Enable so the reader, when used as a PIN pad, can be accessed using
Alarm User Type PINs instead of a user access PINs (see Configuring
Alarm Panel Types 97 and Configuring Alarm Users 131 ).
Always Report Ajar Alarms Enable to report an alarm whenever the door has not been correctly
sealed and the Shunt and Embarrassment timers have expired.
Report Card Transaction Enable to report card transaction messages to a locally connected GMS
Messages Locally Only machine. Messages will not be sent over any network connections.
Report Access/Restore Enable to send a message to the monitoring system whenever the reader
Messages is accessed, and again when the reader is restored (resealed).
Prevent Access When Area Enable to prevent cardholders without a User Type assigned to them from
Sealed accessing the area after it is sealed (see Configuring Alarm Panel Types
97 and Configuring Alarm Users 131 ).

Do Not Activate Strike on Enable to prevent the door strike from being activated when the user is
Exit exiting. Used when a card is required to seal an area, but access to the
area is not required. In some instances, door strike activation can cause
extra delays because of large timed bolts.
Report Egress Messages Enable to send a message to the monitoring system whenever the egress
button is pushed.
T&A Reports Follow Inputs Enable to generate Time and Attendance (T&A) report data based on the
state of 1064 Card Reader Interface alarm inputs. Any 1064 input (up to
four - contact, egress, strike and spare) can be used for T&A reporting
purposes. The alarm points are reported as GPI alarms and are not
mapped into normal alarm operation. The alarm number shown in the
transaction log for these inputs is the reader number multiplied by four.
For example, for reader 14, the input points will be shown as alarm 53 to
56
When an input goes active, it is reported as a "T&A entry" for the last user
to log on. When the alarm is reset, "T&A exit" is reported. The Strike
Time setting allows the system to toggle the T&A reporting based on the
input point state. the zone number = reader number * 4 + input
number ). The area reported is offset by 1, 2 , 3 and 4 respectively from
the programmed reader area. Contact Pacom Systems for further
information.
Note: The Enable Time and Attendance Reports option must

be enabled, the Inihibit Alarm Modes setting must be disabled
for the required alarm system mode(s) (see Setting Reader Modes
209 ) and the Strike Time setting set to "255" (see Setting
Reader Input/Output Parameters 209 ) for this feature to work.
Process Valid Cards During Enable so that card swipe in/out data is maintained when the reader is
Unlock unlocked.
Report Tamper from CRI Enable to report tamper messages from a tamper switch connected to a
1064 CRI input.
Latch Door Alarms Enable so that if a door is opened without a valid read (that is, forced
open), the alarm is latched on and can only reset from GMS.
Enable Count Up Enable for the system to count the number of users in an area by
incrementing the total up by 1 for each valid read. Used with a limited
count area (see Configuring Access Area Profiles 202 ).
Enable Count Down Enable for the system to count the number of users in an area by
incrementing the total down by 1 for each egress. Used with a limited
count area (see Configuring Access Area Profiles 202 ).
Disable T&A Entry Reports Enable to ignore user entry data from the reader for T&A reporting (see
T&A Reporting Example 215 ).
Note: This option appears in place of Enable Count Up if the

Enable Time and Attendance Reports option is enabled.
Disable T&A Exit Reports Enable to ignore user exit data from the reader for T&A reporting (see
T&A Reporting Example 215 ).
Note: This option appears in place of Enable Count Down if the

Enable Time and Attendance Reports option is enabled.
Enable Global Anti-Passback Enable to extend anti-passback functionality to readers connected to other
Controllers in the system. See Anti-Passback 200 .
Enable Door Trouble Alarms Enable so the Card Reader Interface reports the states of open and short
circuit door contacts as trouble alarms.
Note: The door contacts need to be terminated with end-of-line

(EOL) monitoring resistors.
Enable Buzzer/LED for Enable so that the buzzer and LED are activated when the egress button is
Egress used.

Process Multiple Swipes Enable so that events driven by double and/or triple badging must occur
after Timer Expiry within the Inactivity Timer for Pin Entry setting for the access area
(see Configuring Access Area Profiles 202 ), and that the event is triggered
once the timer expires. When disabled, events driven by multiple swipes
are processed immediately. See Configuring Reader Event Drivers and
Macros 227 .
Note: If the same card is not badged consecutively (that is,

another card is badged), the timer will restart for the newly
badged card.
If both double and triple badging event drivers are used, when a
card is triple badged within the specified time, both double and
triple badging events are triggered.
Report Door Alarm as Enable so that door alarms are reported to a Pacom Base Station or third-
Supervisory party receiver as "supervisory" messages. Ensure that the Supervisory
Command option is enabled in the Controller Message Filters 95 dialog
box.
Report Ajar Alarm as Day Report ajar alarms from the reader during Day mode to a locally
Local connected GMS machine.
Report Ajar Alarm as Night Report ajar alarms from the reader during Night mode to a locally
Report Forced Alarm as Day Report forced alarms from the reader during Day mode to a locally
Report Forced Alarm as Report forced alarms from the reader during Night mode to a locally
Night Local connected GMS machine.
Enable Auto Egress Enable so that if a secured door is opened without a card and/or PIN, an
Activation when Contact "Egress" message is reported instead of "Door Forced". This option is
Activates designed for free handle doors where egress wiring may be impractical.
Caution: When enabled, "Door Forced" messages will not be

reported.
Disable Door Access for Enable so that during a guard tour, all valid guard tour card transactions
Guard Tour are processed by the reader, however, the reader does not provide
access.
Note: Normal user type cards operate with the reader as per
normal.
Time and Attendance (T&A) Reporting Example

If the Enable Time and Attendance Reports option is enabled, the time and attendance of staff, based on their
access data, can be recorded and later generated into reports. For example, this may be used to record when a user
passes from access area X to access area Y using a card reader configured for T&A reporting. In a normal scenario,
the user is reported as leaving area X and entering area Y. If the Disable T&A Entry Reports option is enabled,
entry into area Y is not reported, but exit from area X is. If the Disable T&A Exit Reports option is enabled, entry
into area Y is reported, and exit from area X is not.
Configuring Reader Keypads

You set up keypads using the Configuration for Reader dialog box in much the same way as for readers, however,
with the following differences:
Select an appropriate keypad type from the Reader Type list in the Reader 205 tab. The system then
recognizes the device as a keypad and not a card reader.
Link the keypad to the reader. Do this by entering the RS485 address of the 1064/1067/1076 connected to the
keypad in the Keypad Device Address field (Keypads/Interlocks 211 tab). This must be done for both the
reader and the keypad (that is, the same address appears in both configurations). A keypad by itself (that is, no
reader) has its own address.
Select the PIN operation for the keypad using the PIN Operation options in the Keypads/Interlocks 211 tab.
Cardholders required to use a PIN must have the Use PIN to Access option enabled and a PIN set in the PIN
field of the Card Details tab in the Card Access Manager dialog box.

If Card or PIN operation is used, the only duress PIN option available is Duress by PIN Incremented by 1
(see Configuring Access Area Profiles 202 ).
Note: System administrators must ensure that PINs are not consecutive so that one user's PIN is not
another user's duress PIN. In systems with many users this is usually best achieved by only allowing all
odd or all even PIN numbers.
Using Cardholder PINs for Alarm Area Mode Changes

It is possible to use cardholder PINs for alarm area mode change operations. Normally, alarm area control is
restricted to a maximum of 66 or 99 "alarm users" (depending on the number of PIN digits and also regardless of the
number of cardholders in the system), however, this can be increased to however many cardholders are in the
system. That is, any cardholder is able to control particular alarm areas (open, close etc) based on their card reader
access settings.
Note: The availability to change modes is dependent on the alarm system configuration - mode, reader,
area, access settings etc.
Card readers always have an association with an alarm area in GMS, therefore, in this mode of operation the alarm
area(s) associated with card reader(s) that a user can access are available for mode changing when the user enters a
known cardholder PIN at a keypad. For example, if a cardholder has access to readers in alarm areas 1, 3 and 7, then
they will be able to change modes for those alarm areas. Other alarm areas will not be available to that particular
user.
Because it is the association between card readers and alarm areas that enables the functionality, it has been
designed to also cater for situations where:
No actual card readers are used (PIN-pad only access). In this case, readers must be added to the required
alarm area in the site map (see Configuring GMS - Administrator Guide, Drawing and Adding Objects to Site
Maps).
Card readers are used, however, alarm areas exist that do not have associated readers. In this case, because
the Controller (site) is already configured with physical card readers, a "phantom" reader of Alarm Areas
interface type needs to be set up in the Controller for the required alarm area.
Once the above configurations are complete and cardholder access has been set up with the appropriate card readers
(see Using GMS - Operator Guide, Configuring Cardholder Access Levels), enable the following options in GMS:
Use card access user PINs (see Configuring Alarm System Flags 167 ).
Use access levels for area settings (see Configuring Miscellaneous Global Access Settings 233 ).
For more information, contact Pacom support.
Copying Reader Settings To/From Other Readers

You can copy setting from a reader to another reader or range of readers to speed up your system configuration.
Proceed as follows:
1. In the Configuration for Reader dialog box, click Copy to open the Copy Reader dialog box, where you can
select which readers to copy setting to or from.
Copy From Reader Enter the reader number in the adjacent field to copy the settings from.
Copy to Readers Enter the reader number (or the first reader in a range of consecutive
readers) to copy the reader (Copy From Reader)settings to.
to Enter the last reader in a range of consecutive readers to copy settings to. To
copy settings to a single reader, leave this field set to 0.

Auto Increment Enable to automatically define the device address (see Setting Device
Addresses Addresses and Address Ranges 204 ) for each reader you are copying settings
to. The addresses are consecutive, starting from the reader number in the
Copy to Readers setting.
After configuring the reader(s), click OK to close the dialog box and download the settings to the Controller.

Programming Card Data Formats

Pacom Controllers are capable of supporting a variety of card data formats. The Reader Type list contains several
standard and commonly used formats that you can select if only one type of card is being used.
Note: The Reader Type list Multi-Card Format option is not considered "standard". For programming
this type, see Programming Readers for Multi-Card Format 219 .
Programming Readers for Standard Card Format

To program the reader to interpret card data for standard formats, click Configure to open the Card Format dialog
box.
Standard Format Example:

For example, for a reader head that outputs 26 bit Wiegand and uses:
A parity bit on either end of the key data.
An 8 bit facility field length.
An 8 bit issue field length.
An 8 bit code field length.
Set the card format data fields according to the following diagram. The field offsets are incremental, so each
progressive field offset must include the previous field(s) offset and field length(s). GMS knows the overall key data
length, so no information is required for the final parity bit.
Program the data format according to the parameters below.
Note: Some parameters change depending on the card format you are programming.
New Format Click to clear all settings and create a new card data format. Enter a name for the
format in the field beside the Save button.
Prev Click to revert the dialog box settings back to the previously saved card data format.
Next Click to revert the dialog box settings to the next saved card data format.
Delete Click to remove the current card data format from the GMS database.
Facility Field Data Specifications
Field Length Specify the length as the number of consecutive bytes/nibbles of data.
Field Offset Specify the offset as the start of the data to be interpreted by GMS.

Field Type Specify the data portion required for Facility data.
Unused - Select to ignore any field data.
Bits - Select to specify field data in data bits (1 bit).
Nibble - Select to specify field data in nibbles (4 bits).
Bytes - Select to specify field data in bytes (8 bits).
Include Facility Field See Configuring Degraded Mode Operation 231 .
in Mask for Degraded
Check
Field Designator in This is the number of nibbles used to report the Facility data to the GMS in
Nibbles transaction reports.
Caution: Do not change this setting.
Issue Field Data Specifications

Field Type Specify the data portion required for Issue data.
Include Issue Field in See Configuring Degraded Mode Operation 231 .
Mask for Degraded
Check
Field Designator in This is the number of nibbles used to report the Issue data to the GMS in transaction
Nibbles reports.
Code Field Data Specifications

Field Type Specify the data portion required for Code data.
Include Code Field in See Configuring Degraded Mode Operation 231 .
Mask for Degraded
Check
Field Designator in This is the number of nibbles used to report the Code data to the GMS in transaction
Nibbles reports.
GMS Profile
Save Click to store the data card format in the GMS database.
Note: You need to save any new format as a GMS profile in order order to be
able to select it as a valid card data format
Programming Readers for Multi-Card Format

To program the reader to interpret card data for multiple formats, click Configure to to open the Card Format dialog
box.
Note: For Aperio lock-readers, create

Multi-Card Format Example:

For example, for a reader head that outputs 34 bit Wiegand and uses:
A parity bit on either end of the key data.
A 12 bit facility field length.
A 12 bit issue field length.
An 8 bit code field length.
Set the card format data fields according to the following diagram and parameters. The field offsets are incremental,
so each progressive field offset must include the previous field(s) offset and field length(s).
Setting Parity Checking:

1. Enter the key data length (bits) in the No. of Weigand Bits field.
2. Enable a Parity Enable checkbox - the available bits become active (white) along the bar below the checkbox
for the relevant Parity Check region. You can perform up to three separate parity checks.
3. Right-click the rectangle in the bar that represents the parity bit - it will show as red.
4. Left-click the rectangle(s) in the bar that represent the bits to check parity against - they show as blue.
Program parity checking according to the parameters below.
Note: The table below lists only parity checking parameters that are additional to those available for
standard format card programming (see Programming Readers for Standard Card Format 218 ).

No. of Weigand Bits Enter the number of bits that make up the overall key data length (max. = 64). When
you enter a value in the field, if any parity checking is enabled, the available bits
become active in the parity bar.
Reverse Bits Enable to have the card data interpreted from right to left, instead of left to right.
Invert Bits Enable to have the card data interpreted inversely. That is, 0s are read as 1s, and 1s
as 0s.
Parity Enable Enable to set a parity bit and the bits to check parity against.
Even Specify the length as the number of consecutive bytes/nibbles of data.
Odd Specify the offset as the start of the data to be interpreted by GMS.

Card Reader Compatibility

The following table lists the compatibility between Pacom card reader interfaces and popular reader makes and
models.
Pacom Wyre Time-

-less con
Reader Make and
Model 1061 1062 1062 1064 1076 AP TTC
CRI Keypad
Weigand 26bit
Weigand 27bit
Mag Stripe Track 1
Mag Stripe Track 2
Mag Stripe track 3
Mosler Mag Stripe
Track 2
Weigand 26bit/
Keypad
Binary Keypad
Weigand Mag Stripe
Track 2
Weigand 26bit Insert
Generic Weigand
Generic Weigand
Insert
Generic Weigand
(Raw Data)
Generic Weigand
Insert (Raw Data)
Weigand 26bit
Keypad
Weigand Keypad
Weigand Keypad
(Raw Data)
Weigand 26bit Key
Reader
Matrix Keypad
Generic Weigand/
Keypad
Microprox Reader/
Keypad
Mercury Reader
Weigand
Mercury Reader Mag
Stripe
Generic Weigand
Parity
Generic Weigand/
Keypad Parity
Generic Weigand/
Keypad 26bit Parity
RCO Reader
Multicard Format
Barcode Reader

Configuring Reader Time Schedules

Reader time schedules (time zones) are used to determine the time for locking/unlocking the reader on various days.
They can also be used to control when other reader functions are performed. Card reader time schedules can also be
used with elevator readers to inhibit certain alarms, but are otherwise separate and independent of all other time
schedules within the system. A Controller can handle up to 32 reader time schedules.
Once you have created reader time schedules, you can apply them to all readers in each access area of a site from a
single dialog box. This makes applying the time schedules faster than applying them individually to every reader. See
Configuring Access Area Open/Close Schedules 226 .
Along with access settings is the Yearly Calendar. This calendar defines days of the year which are different to normal
access settings. For example, public holidays. See Setting the Yearly Calendar 224 .
Time Schedule Resolution

Reader time schedules have a "standard resolution" of 10 minutes. This means that any time settings must be in
increments of 10 minutes. For example, a time of 09:00 or 09:10 is acceptable, however, a time of 09:05 is not. GMS
4.07 and 8001 Controllers with firmware 1.07 can support a time schedule resolution of five minutes. For example, a
time of 09:00 or 09:05 or 09:10 is acceptable, however, a time of 09:08 is not.
In order for GMS to use the five minute resolution, add the following line to the GMS32.INI file:
[System Parameters]
Enable 5 minute access schedule=Y
Note: When using the five minute resolution, up to two time schedules per day can be applied to the
reader. When using 10 minute (standard) resolution, up to three time schedules per day can be applied to
the reader. If three shifts were defined previously, and then five minute resolution is applied, the
Controller will "lose" the third shift settings.
105x Controllers do not support this functionality and are limited to 10 minute resolution.
Setting Reader Time Schedules

To configure reader time schedules, proceed as follows:
2. In the Controller dialog box, select Access Control > Access Control Time Schedules. The Configuration for
Reader Timezone dialog box opens. Use the following section as a guide to parameters available in this dialog
box.
Note: The dialog box image on the right shows the apperance when using five minute resolution.
program a set of hours, proceed to enter the hours as required. Click OK to
close the dialog box and add the settings to the Programmed Hours list. The
next time you open the dialog box, the hour settings become available.
See Quick Select 224 for how to apply Programmed Hours list settings.

Sunday to Holiday 3 Enable the checkbox next to each day or holiday to activate the time setting
fields for it. The Holiday types allow you to create up to three different holiday
time schedules that you can set in the Yearly Calendar for various holidays
(see Setting the Yearly Calendar 224 ). For example, you may have a holiday
type to use when the premises is denying all access and another type that can
allow access for part of the day.
Note: If you had Holiday 4 time schedules configured from a previous

version of GMS, these are automatically changed to Holiday 3.
Start Time Enter the beginning time for the schedule (Shift) in 24 hour format. Times
must increase from left to right across the time shifts. Times must end by
midnight, or else be configured in for the next day.
Note: You do not have to create schedules for all shifts.
End Time Enter the end time for the schedule (Shift) in 24 hour format. Times must
increase from left to right across the time shifts. Times must end by midnight,
or else be configured in for the next day.
Note: You do not have to create schedules for all shifts.
Quick Select Used in conjunction with the Programmed Hours list. Select the required
hours from the Programmed Hours list, then click Quick Select to apply
them.
Prev Click to load the settings for the next configured reader time schedule.
Next Click to load the settings for the previously configured reader time schedule.
Note: If any shifts overlap, the settings of the last shift covering the time apply. For example, if shift 1
ends at 12:00 and shift 2 starts at 11:00, shift 2 settings will apply after 11:00.
3. Click OK to save the reader time schedules.
Setting the Yearly Calendar

The Yearly Calendar allows you to the program days when reader access is different to normal, for example, public
holidays. The calendar is programmable for a 12 month period starting at the present month.
To configure the Yearly Calendar, proceed as follows:
1. In the Controller dialog box (see Using the Controller Dialog Box 21 ) select General > Yearly Calendar >
Card Access. The Yearly Calendar dialog box opens. Use the following section as a guide to parameters
available in this dialog box
Calendar Enable the checkbox next to each date that you want to apply a holiday time
schedule to. Right-click to display the Holiday Type list.
Holiday Type Selector Click to display the available holiday types (below the calendar), then click to
select one and apply it. This setting will apply to subsequent holidays until you
change the type.
Last Month Click to display the calendar for the previous month.

Next Month Click to display the calendar for the next month.
2. Click OK to save the Yearly Calendar.

Configuring Access Area Open/Close Schedules

Open/close schedules allow you to apply reader time schedules for any areas in a site from one dialog box. That is,
you can set the time schedules for all areas configured in a Controller at once, and not have to apply them
individually to each reader.
Applying Time Schedules to Access Areas

To configure access area open and close schedules, proceed as follows:
1. In the Controller dialog box (see Using the Controller Dialog Box 21 ) select Access Control > Open/Close
Schedules. The Open/Close Schedules dialog box opens. Use the following section as a guide to parameters
available in this dialog box
Timezone for Lists all access areas for the Controller. Click the list next to the area number to
select a time schedule by its ID number.
... Click to open the Configuration for Reader Timezone dialog box, where you can
browse through the details of all configured time schedules. Use Prev TZ and
Next TZ to switch between schedules. Click OK to apply a schedule and close
the dialog box.

Configuring Reader Event Drivers and Macros

Event drivers and macros are system utilities that allow you to tailor behavior of the system, based on a set of
circumstances or conditions. When the conditions are met, the Controller performs the required task. You can set up
event drivers that are specific to readers. This can then be used in conjunction with macros (see Creating Event
Drivers and Macros 183 ).
Configuring Reader Event Drivers

To configure an event driver for a reader, proceed as follows:
1. In the Controller dialog box (see Using the Controller Dialog Box 21 ) select Macros > Reader Macros. The
Creation for Event Driven Activations dialog box opens.
Readers to cause Event Enable the checkbox next to the reader that the event driver can activate from.
Driven Activations
Note: 1057/1058 Controllers require firmware version 5.00 or later to
support up to 64 different reader macros.
TZ no. Click to open the Configuration for Reader Timezone dialog box (see
Configuring Reader Time Schedules 223 ), where you can select a reader time
schedule. The reader can only initiate the event driver during the selected time
schedule. The number of the time schedule appears in the to Trigger this
Event field.
Event Type: Select a reader event to initiate the event driver (activate an output) as
detailed in output control:
Undefined - No action is taken.
Event active when valid card accepted - The event driver initiates when
a valid card is used on the reader.
Event active when card denied - The event driver initiates when an
invalid card is used on the reader.
Event active when contact alarm active - The event driver initiates when
the reader contact goes into an alarm state.
Event active when strike alarm active - The event driver initiates when
the reader strike goes into an alarm state.
Event active when any readers locked - The event driver initiates when
the reader is locked.
Event active when any readers unlocked - The event driver initiates
when the reader is unlocked
Event active when duress PIN entered - The event driver initiates when
a user enter a duress PIN.
Event active when invalid PIN entered - The event driver initiates when
a user enters an invalid PIN.

Event active when any reader is interlocked - The event driver initiates
when the reader becomes interlocked.
Event active when egress activated - The event driver initiates when a
user presses the egress button.
Event active when extended strike enabled - The event driver initiates
when any extended strike time starts.
Event active when card blocked - The event driver initiates when a
blocked card is used on the reader.
Event active when card expired - The event driver initiates when an
expired card is used on the reader.
Event active when card anti-passback - The event driver initiates when
a card is passed back for use on an anti-passback reader.
Event active when card in/out error - The event driver initiates when the
reader generates an in/out error.
Event active when valid guard tour - The event driver initiates during a
valid guard tour.
Event active when card traced - The event driver initiates when a traced
card is used on the reader.
Event active when unmasked door contact active - The event driver
initiates when the unmasked reader contact goes into an alarm state.
Event active when dual swipe with same card - The event driver
initiates when a card is used twice in succession on the reader. The time for
the swipes can be limited.
Event active when triple swipe with same card - The event driver
initiates when a card is used three times in succession on the reader. The
time for the swipes can be limited.
Event active when valid system ID card - The event driver initiates
when a card with a valid facility code (system ID) is used on the reader.
Event active when Door Ajar - The event driver initiates when the reader
generates a "Door Ajar" message.
Event active when Door Forced - The event driver initiates when the
reader generates a "Door Forced" message.
Output Select for the event driver to switch an output. Enter the output number in the
Output field.
CCTV Select for the event driver to switch a CCTV camera. Enter the camera number
in the CCTV field.
Trigger Select for the event driver to run a macro. Enter the macro number in the
Trigger field. See Creating Macros 184 .
On/Off Select the behavior for the selected Output, CCTV or Trigger. The event
driver can either turn it ON or OFF.
Permanent Enable to permanently activate the Output, CCTV or Trigger until it is reset
from GMS. When selected, you cannot set an Activation Time.
Activation Time Enter the time (in seconds) for how long to activate the Output, CCTV or
Trigger for. This option is disabled if the Permanent option is enabled.
Time in Min. Enable to count the Activation Time setting in minutes.
Prev Click to go back to the previously created event driver settings.
Next After making settings, click to create a new event driver.
3. Click OK to close the dialog box and download settings to the Controller.


You can use cardholder access card "types" for specifying additional functionality within Controllers that is outside of
pure access control management from within the GMS head system. This provides additional control on a site-only
basis. You can think of card types as not only determining access levels through templates based on card type, but
also to interact with the security system differently. For example, being able to reset latched door alarms on access,
or overriding passback settings.
There are eight card types available as standard, however, you can create up to 256 types. Create card types and
assign users to them from the Card Access Manager.

To configure access card types, proceed as follows:
1. In the Controller dialog box (see Using the Controller Dialog Box 21 ) select Access Control > Card Type
Settings. The Card Type Config dialog box opens.
Card Type Select a card type to configure from the list. Use and to scroll through all
card types. Any settings changed will apply to the card type selected.
Warning Limit Control Enable to activate the warning controls for the number of this card type
allowed in any access area. The system warns when the Warning Count
setting is reached.
Warning Count Enter a number for the maximum allowable cards of this type in any access
area. When the setting is reached, an output, CCTV, or trigger is activated.
Output Select for the Warning Count to switch an output ON. Enter the output
number in the Output Number field.
CCTV Select for the Warning Count to switch a CCTV camera ON. Enter the
camera number in the CCTV Number field.
Trigger Select for the Warning Count to run a macro. Enter the macro number in
the Trigger Number field (see Creating Event Drivers and Macros 184 ).
Trigger for.
In Minutes Enable to count the Activation Time setting in minutes.
Maximum Limit Control Select to enable a maximum limit on the number of cards of this card type.
Maximum Count Enable to activate the limit controls for the number of this card type allowed
in any access area. The system prevents access to the card type when the
Maximum Count setting is reached. Access is allowed when the number
drops below the Maximum Count setting.
Allow Access Over Enable to allow access beyond the Maximum Count setting. Every time
Maximum Count access is given over the Maximum Count setting, the selected output, CCTV,
or trigger is activated.
Output Select for the Maximum Count to switch an output ON. Enter the output
CCTV Select for the Maximum Count to switch a CCTV camera ON. Enter the
camera number in the CCTV Number field.

Trigger Select for the Maximum Count to run a macro. Enter the macro number in
the Trigger Number field (see Creating Event Drivers and Macros 184 ).
Trigger for.
In Minutes Enable to count the Activation Time setting in minutes.
Months used before card Enter the number of months to elapse since the card type was last used
disabled before denying access to the card type. A setting of 0 means indefinite.
Set for allowing card Enable to have the system reset any latched door alarms when this card type
type to reset latched is used.
door alarms
Allow Passback Override Enable to have the system allow passback (if anti-passback is enabled) when
this card type is used.
Auto block card after 5 Enable to have the system block access to this card type after five failed card
invalid attempts (Card or card with PIN access attempts.
only or Card with PIN)
Allow access in Security Enable to have the system allow access to this card type if the area is
level 1/5 currently on Security Level 1 or 5 (see Setting Security Levels 230 ).
Setting Security Levels

You can set an access area (or all access areas) to specific security levels. These settings determine which card types
are allowed access and have no defined meaning. This enables you to use the security level settings for whatever
purpose, with the underlying theme being that only card types of a security level setting can gain access to areas that
have a security level setting other than 0. An area, by default, during normal operation is at security level 0, meaning
that card access is based on access level (time schedule and reader) and has no security level as such.
For example, an area with security level 6 will only allow card types with security level 6 access to them.
There are two ways to put an area into a different security level: either by macro command to use an event driver
and using the Set security level for an area action to set the area security level (see Creating Event Drivers and
Macros 183 ), or using GMS if the operator has a special attribute to control it directly.

Configuring Degraded Mode Operation

Under normal operating conditions, the Controller performs all access card processing when a user attempts access
with a reader. If a reader becomes disconnected from the Controller, it can use a "degraded mode" of operation to
continue access control (although limited compared to normal operation). In degraded mode, readers can allow
access to specific cards depending on the parameters set in the Card Format dialog box (see Programming Card Data
Formats 218 ). The three most popular methods are:
Facility Code Only 231 .
Facility and Card Code 231 .
Facility, Issue and Card Codes 231 .
As well as enabling the methods of access control, the Card Reader Interface (CRI) must also be set to allow access
in degraded mode. There are two methods two enable access in degraded mode:
Degraded Mode for a Reader 232 .
Degraded Mode for a Card 232 .
Card Reader Interface Storage Capabilities

Each Pacom CRI can store a specific amount of card information. This information is used during degraded mode
operation to allow access. The table below shows how many previously used cards different Pacom CRIs can store in
internal memory.
Storage Values
1064 1064 V4+ 1076
Facility 8 256 500
Facility, Issue, Code combination Not Supported 96 - 384 500
Note: The 1064 with v4.xx firmware can store from 96 to 384 cards, depending on the configuration of
Facility, Issue, and Code. Contact Pacom for more information.
Facility Code Only

Access during degraded mode can be controlled by using the facility code on the card. Any card with the matching
facility code is given access. To enable facility code only during degraded mode, enable the Include Facility Field in
Mask for Degraded Check option in the Card Format dialog box (see Programming Card Data Formats 218 ).
Caution: Using a facility code only may be a security risk. Any card with that facility code and the same
card format is given access, regardless of the restrictions. Meaning, a card not belonging to a company is
given access if the facility code matches. Cards which have been blocked are also given access if the
facility code matches.
Facility and Card Code

Access during degraded mode can be more secure if both a facility code and a card code are included. When the
facility code and card code options are selected, the CRI with facility and card code storage capability will remember
previously used valid cards. The actual number of cards stored are shown in Card Reader Interface Storage
Capabilities 231 . When the CRI enters degraded mode, only the cards in the CRI memory are allowed access.
To enable both the facility and the card codes, enable the Include Facility Field and Code Field in Mask for
Degraded Check options in the Card Format dialog box (see Programming Card Data Formats 218 ).
Note: If the 1064 CRI running firmware v2.XX is in use, including the card code will have no effect. The
1064 v2.XX will allow cards with the same facility only.
Facility, Issue and Card Codes

Access during degraded mode can be made secure for cards using all three fields. The issue code is used to keep
track of the number of cards a user has been provided. To enable all three codes during degraded mode, enable the
Include Facility Field and Code Field and Issue Field in Mask for Degraded Check options in the Card Format
dialog box (see Programming Card Data Formats 218 ).

Note: the Issue Code is only used on mag stripe, and can be reprogrammed.
Setting Degraded Mode for a Reader

A reader can be setup so that only that reader will allow access during degraded mode. Individual cards do not have
to be setup to have access in degraded mode. Selecting this option forces the reader to check the selected mask, and
if the mask is not stored in the CRI it will add it to the list (up to eight entries). The following describes how to setup
a reader for degraded mode.
Note: A CRI must be setup for access during degraded mode. If the reader is not setup, then the reader
will not allow access to any cards during degraded mode.
1. In the Controller dialog box (see Using the Controller Dialog Box 21 ) select Access Control > Hardware >
Readers. The Configuration for Reader dialog box opens.
2. Click the Flags tab and enable the Store Code Locally for Degraded Mode option, then click OK.
Setting Degraded Mode for a Card

A card can be setup to have access during degraded mode. The card will work during degraded mode for all the
readers attached to the Controller. The following describes how to set up a card for degraded mode:
1. In GMS, click to open the Card Access Manager dialog box. Find the card in the database and click the
Card Details tab to display the card details (see Using GMS - Operator Guide, Using the Card Access Manager).
2. In the User Flags region, enable the Store Code for Degraded Mode option. Click Save, then click
Download to store the card settings in the Controller.

Configuring Miscellaneous Global Access Settings

You can use GMS to globally set several access security options. These settings are provided through a single menu
option and dialog box for fast and simple setting up.
To set miscellaneous global access settings:
2. Select Access Control > Overall Settings. The Overall Settings dialog box opens. Edit the settings as
required.
Parameter Function
Cards in Controller Shows the number of access cards currently in the Controller access card
database database. This field is for reference and is non-editable.
Keypad menu The identification number that the system requires to allow the keypad user
authorization PIN access to the Enrol Card, Change PIN and Edit Door Name functions. This
applies only to Pacom keypads that are in CRI (card reader interface) operating
mode (1062/8101). The PIN can be from four to eight digits in length.
Card access database Shows the version of the Controller access card database. This field is for
version reference and is non-editable.
Card PIN Validity The length of time (in days) that all user access cards and PINs will be vaild for,
Period before the system requires them to be changed. For example, a value of 30 will
force users to change their access PINs every 30 days. A value of 0 means that
the validity period is infinite. Min. = 0, max. =256.
Note: The access card PIN validity period will apply only to cards that
are downloaded to the Controller access card database. Existing cards in
the database will remain unchanged unless they are downloaded again
into the Controller.
Multiple access levels Enables multiple access levels per card by using the card issue number as the
using card issue# as access level identifier. Meaning, access cards can be issued with up to 255
access level individual access levels.
Note: The Multiple Access Levels feature is client-specific and is not

intended for "standard" GMS users. For further information, contact
Pacom support.
Use access levels for Enables the system to use cardholder access levels for alarm area mode change
area settings operations (see Configuring Readers 216 ).
Note: The Use card access user PINs alarm system option must be
enabled for this feature to work (see Configuring Alarm System Flags
167 ).
3. Click OK to save the configuration and download it to the Controller.

Configuring Third-Party Access Control Interfaces

Pacom Controllers are capable of interfacing with a range of third-party access control products, allowing for easy
integration with existing systems and for system expansion.
The configuration is based around connecting the third-party device to a Pacom Controller. The Controller then
communicates messages from the device to GMS in the normal way. Some devices allow commands to be sent from
the Controller, providing a higher level of control from the GMS system.

Configuring a Schlage Wyreless Interface

This section outlines the integration between the Pacom system and a Schlage Wyreless access system.
Wiring Information
You need to connect the Pacom Controller to the Wyreless Panel Interface Module (PIM) using the RS485 port.
Note: Only Wyreless PIMs can be connected to a Pacom RS485 port configured for Wyreless.
The following diagram outlines required wiring and RF connectivity.
Configuring the Wyreless Access Point Modules

Set up the Wyreless Access Point Modules (WAPM) using the supplied software.
Configuring the Controller Port and a Reader for Wyreless

Communications
To configure port parameters for RS485 operation with a Wyrless PIM, proceed as follows:
2. In the Controller dialog box, select General > Networks > Port Settings. The Controller Port Parameters


4. Click the RS485 port image that the PIM is connected to. The Port Protocol Parameters dialog box opens for it.
5. In the Protocol list, select Wyreless Access Protocol. The Wyreless Access protocol parameters display.
Caution: Only Wyreless PIMs can be attached to the RS485 port used for the Wyreless Access Protocol.
Other devices attached to the same RS485 port may not operate correctly.
6. In the Address Range list, select the appropriate address range (in groups of 64) that the WAPMs are
configured in.
7. Click Download to save the settings to the Controller.
8. In the Port Protocol Parameters dialog box, click Close.
dialog box opens.
10. In the Reader Interface list, select Wyreless Access Point.
11. In the Device Address field, enter the appropriate address.
Note: The device address of a WAPM configured using the third-party software must be incremented by 1
to be compatible in GMS. For example, if a WAPM is configured in the third-party software as address 3, it
is configured in GMS as address 4.
12. Configure all other parameters as per a standard reader, then click OK to save the settings and close the dialog
box.
For more information on Wyreless Access protocol parameters, see Communications Protocol Parameters Reference
86 .

Configuring Assa Abloy Aperio Lock-Readers

8001 Controllers (firmware version 1.06 or higher) can be configured to communicate with Assa Abloy Aperio wireless
lock-reader devices. The Aperio system uses wireless communications between an Aperio hub (router) and a number
of Aperio lock-readers. Support for Aperio devices is a licensed feature.
When users swipe a card against the Aperio lock-reader, it sends a signal to the hub, which then signals the local
Controller. The Controller determines whether or not the access is valid and sends the appropriate signal back to the
hub. The hub then signals the lock-reader to either unlock or remain locked as required. As such, GMS can be used to
"lock" the door by ignoring requests for access from it, however, that is the extent of direct control.
The hub(s) are wired to the Controller for two-way communications using a dedicated RS485 device line. On the
Controller, the RS485 can be connected to a RS485 expansion card or to the on-board RS485 port. The system
supports up to 64 Aperio devices (Controller firmware version 1.07 or higher) using multiple RS485 ports, each
capable of supporting up to 32 Aperio devices.
Caution: An RS485 port that is configured for Aperio devices must not have any other types of devices
attached to the RS485 line. Mixing device types may cause unpredictable behavior.
Note: The lock-readers signal the hub only when a card is swiped against them to request access, and
each hour to verify its online/offline status. Signalling between the hub and Controller enables GMS to
warn of low battery power and whether or not the lock-reader is online.
Aperio lock-readers are designed to work with MIFARE RFID access cards.
Enabling Aperio Device Support

To communicate with the Aperio hub, check first if the license is enabled, then program the number of Aperio lock-
readers that require support. Proceed as follows:
2. Select View > Controller Licenses. The Controller License Options dialog box opens.
3. Click Change (should be active if the license allows for Aperio support) next to OEM CRI. The License Update
dialog box opens.
4. In the Enter Code field, type the license code (in hexadecimal format).
5. In the Enter Limits field, type the number of card readers to be supported.
6. Click OK to close the dialog box and save the settings.
7. Click OK to close the Controller License Options dialog box.
Configuring Controller Ports for Aperio Devices

To set up the port to communicate with the Aperio device, proceed as follows:
box opens.
2. Click on the port that has the Aperio-dedicated RS485 line connected.
3. From the Protocol list, select Aperio Protocol. The Aperio protocol parameters display.
4. Enter the parameters as required, (see Communications Protocol Parameters Reference 48 ).
Aperio lock-readers are auto-detected on the RS485 port and have a default configuration applied to them.
Note: Messages from Aperio lock-readers are reported in the Transaction Manager. Aperio lock-readers
can report battery low and online/offline status.
Viewing and Editing Aperio Reader Configurations

Aperio lock-reader(s) are auto-configured with default settings, however, some settings can be edited. Basic
configuration is as follows:

Note: Settings in the LED Control and I/O Parameters tabs have no effect with these devices. Some
settings in the other tabs may be applicable.
Aperio lock-readers are designed to work with MIFARE RFID access cards.
dialog box opens.
2. In the Reader tab, use < and > to select a reader.

3. In the Reader Interface list, select Aperio.
4. In the Reader Type list, select Multi-Card Format.
5. In the Card Format region, click Configure. The Card Format dialog box opens (see Programming Card Data
Formats 218 ).
6. In the GMS Profile region, click to view options and select Mifare 34 Bit Card Serial Number.
7. Click OK to close the dialog box and return to the Configuration for Reader dialog box.
8. Use the dialog box tabs to view or change other settings if required (see Configuring Readers 204 ).

Configuring Sargent & Greenleaf IP Series Locks

8001 Controllers (firmware version 1.06 or higher) can be configured to communicate with Sargent & Greenleaf IP
Series electronic locks. The S&G IP Series locks employ a keypad and display as part of the locking mechanism. The
lock works independently of GMS access control and will allow access only to users that enter a valid user ID and PIN.
IP Series locks are able to be configured through connection to the LAN/WAN and must be wired to the Controller
Network port. Each lock must have a unique IP address, with GMS used to program user ID and PINs to the lock.
These devices use the GMS general purpose IP (GPIP) protocol, which allows a maximum of six connections per
Controller. That is, if IP Series locks are the only devices using GPIP, a maximum of six can be supported.
Configuring Lock Communications

To set up the Controller Network port to communicate with the lock, proceed as follows:
1. In the Controller dialog box, select General > Network > General Purpose IP Settings. The General Purpose
IP Parameters dialog box opens.
2. The Port 1 and Port 2 settings represent port numbers on the device. If left at "0", it defaults to: Port 1 =
2000 (the command port) and Port 2 = 5000 (the event port).
3. In the Protocol list, select IP Series Lock. From the adjacent list, select TCP.
4. In the Local Port list, select the Controller port to which the lock is connected.
5. In the IP Address field, enter the IP address of the device. The IP address cannot be assigned using GMS and
should be available from IT administrators or installers.
Note: The Login Name and Password Index settings are not required.
6. Click Download, then check to see whether an online message is reported in the Transaction Manager.
Once the lock comes online, its clock is updated to match that of GMS.
Note: Messages from S&G IP Series locks are reported in the Transaction Manager. Locks can report
tamper and online status.
Configuring Lock Users and PINs

Each lock requires configuration for users of the lock. That is, they will have a user ID number and a password (PIN).
These can be programmed into the locks and managed (enabled, disabled, added, deleted) with GMS user-defined
commands, as follows:
1. In the Controller dialog box, select Commands > User Defined Commands > Define Commands. The
Controller User Defined Command dialog box opens.
2. In the Function Code field, type 21.

3. In the Command Data field, program the lock using the following ASCII format: "68,xx,yy,zz", where:
68 denotes communication to S&G IP Series locks.

xx is the index number of the lock. 0 is the first lock, 1 is the second lock and so on.
yy represents the number of bytes that make up the command, so the lock can determine the end of the
command.
zz represents the actual configuration command. Some of the IP Series commands supported are:
US - add lock user (represented in ASCII as "85,83").
HA - enable previously added lock user (represented in ASCII as "72,65").
DE - disable previously enabled lock user (represented in ASCII as "68,69").
BU - delete previously added lock user (represented in ASCII as "66,85").
For example, "68,2,9,85,83,1,6,5,4,3,2,1" represents communicating with a SG IP Series device (68);
index number 2 (2), which is lock 3; a following command byte code length of ten bytes (9); lock
command US to add a user (85,83) [two bytes]; a user ID number of 1 (1) [one byte]; a six-digit PIN for
the user that is 654321 (6,5,4,3,2,1) [six bytes].
Note: If you are configuring several locks, save the command and re-use it (see Controller User-Defined
Commands 119 ).
4. Click Send. The Transaction Manager will show a "Security Modified" message if the command is accepted, or
an "Authority Denied" message of the command has failed.
Note: All IP Series lock commands are supported, however, reply messages other than acknowledge or
deny are ignored by GMS. For more command information refer to S&G IP Series protocol documentation.
The following example command adds user "1" with password "654321" on the third lock "2":

Chapter 5
Configuring Elevator Control
241
Pacom Controllers can control and monitor elevator floor access. There are two interfaces configured for elevator
control: a High Level Interface (HLI) and a Low Level Interface (LLI). It supports Kone and Otis elevator systems
using HLI, and other elevators by LLI.
High level interfacing is where the Controller talks to third-party Elevator Security Systems.
Low level interfacing is using a Pacom 1065EC.
The following provisions on Pacom Controller support elevator functionality:
RS232, 2 wire RS485 and 4 wire RS422 for HLI (RS422 is not available on 1058 Controllers).
Support for up to 64 elevators, with a maximum of 128 floors.
GMS is required to configure elevator functionality, and to manage the card access database.
Each elevator car must be fitted with a Pacom compatible card reader. The readers are assigned numbers from 1 –
64. The corresponding elevator must have the same number as the reader.
On a LLI configuration, each card reader can control eight elevator controllers (Pacom 1065EC), and each elevator
controller can control 16 floors.
Pacom Controllers can obtain the current elevator floor location (floor level) from a Pacom 1065EFM or 1064EFM.
GMS can use this to display a graphical representation of elevator position.
Note: The current elevator floor number can be available from HLI, however, this is not a standard
feature.
242 | Chapter 5 - Configuring Elevator Control

Configuring Ports for Elevator Control

In order to interface with elevators, you need to configure a Controller port.
Configuring a Port for a High Level Interface (HLI)

To configure a port for HLI, proceed as follows:
box opens.
3. Select the Port Parameters option, then click the port that the third-party elevator security system is
connected to. The Port Protocol Parameters dialog box for the port opens.
4. In the Port Protocol Parameters dialog box, from the Protocol list, select Elevator Interface. The elevator
interface parameters appear.
5. Enter the elevator parameters as required (see Communications Protocol Parameters Reference 56 ).
6. Click Download to save the new settings, then click Close to close the dialog box.
Configuring a Low Level Interface (LLI)

To configure a low level interface elevator control, proceed as follows:
1. Set the address of the 1065EC, ensuring that it is a unique address (see the Hardware Installation Guide for
more information on setting addresses for 1065EC).
2. Connect the 1065EC to the Controller using an RS485 device line.
3. Set the RS485 port parameter (see RS485 Device Loop 71 ).
Note: The 1065EC does not need to be added in the Controller hardware configuration. The system will
automatically recognize the 1065EC as an elevator controller.
Chapter 5 - Configuring Elevator Control | 243

Configuring Elevators
The following procedure apply to both HLI and LLI. There are minor differences in configuration options which are
shown.
2. In the Controller dialog box, select Access Control > Elevators > Elevator Settings. The Configuration for
Elevator dialog box opens. Configure the elevator parameters according to the following sections.
Setting Common Elevator Properties

These settings are required for every elevator and are always visible in the Configuration for Reader dialog box.
Elevator No Select an elevator by typing a number (1 to 64) in the adjacent field and clicking
Elevator No. Or, use and to scroll through all elevators. All configuration options
are applied to the elevator with the ID number displayed here.
Floor Monitor No. This is the device loop address of the 1064EFM/1065EFM. An EFM (Elevator Floor
Monitor) is a Pacom device used to detect which floor an elevator is on.
Clear Returns the currently selected elevator details to default values in all dialog box tabs.
Copy Opens the Copy Elevator Parameters dialog box to copy settings from one elevator to
others (see Copying Elevator Settings To/From Other Elevators 216 ).
Setting Elevator Floors and Relay Controller Addresses

These settings determine the floors that the elevator services as well as the relay addresses for the Controller.
Proceed as follows:
Note: If low-level 1065 Elevator Controllers are used, their device loop addresses can be configured from
this page (ensure that the Controller firmware is > 4, and the GMS version is > 3).
1. In the Configuration for Elevator dialog box, click the Elevator tab and configure the elevator according to the
parameters below.

Floors Serviced Enable the checkbox next to each floor number for the elevator to service it.
Floors 1-64 as shown by default, click Floors 65-128 to display floors 65-128.
Select All Click to enable the checkbox for all floors.
Deselect All Click to disable the checkbox for all floors.
Floor Relay's Controller Enter the device loop address of the 1065EC controlling the specified floors. For
Address example, floors 1-16 are controlled by a 1065EC with a device loop address of
11. This option applies to LLI only.
Area Configuration The area with which the elevator is associated (see Configuring Access Area
Profiles 202 ).
Apartment Mode Enter the time (in seconds) that a floor remains off security when triggered
from an input. For example, in an apartment building, a tenant on the fifth floor
can set a floor to be off security to allow a guest to enter the elevator and press
the fifth floor button without requiring a card. In this mode of operation the
inputs on 1065EC are not used for button press feedback (see the 1065EC
Installation Manual, option 3 Configuration). This option applies only to the
1065EC and not to the elevator HLI.
Setting Elevator Time Schedules

These settings determine the time schedules (time zones) that the elevator will report status messages. For example,
its floor location and its destination (as selected by users). Proceed as follows:
1. In the Configuration for Elevator dialog box, click the Timezones tab and configure the elevator according to the
parameters below.
TZ no. Click to open the Configuration for Reader Timezone dialog box, where you
can browse through the details of all configured time schedules. Use Prev TZ
and Next TZ to switch between schedules. Click OK to apply a schedule and
close the dialog box.
to report status msgs Shows the selected time schedule number.

Setting Elevator Options

These settings determine if HLI is used for elevator control and what status information the elevator reports to GMS.
Proceed as follows:
1. In the Configuration for Elevator dialog box, click the Flags tab and configure the elevator according to the
parameters below.
Disable HLI Control Enable to discontinue HLI elevator control. For HLI, ensure this option is
disabled.
Note: You can use a combination of HLI and LLI on the same
elevator. For example, LLI for fast response and floor access, and
HLI for status information (that is, which floor the elevator is on),
then disable this option.
Only report secure floors Enable so that only secure floors (those with access control) chosen by
chosen elevator users are reported to GMS. See Configuring Floor Access 248 .
Disable floor chosen Enable so that the floors chosen by elevator users are not reported to GMS.
reporting
Note: This option overrides the Only report secure floors chosen
option.
Disable elevator floor Enable to prevent the system reporting which floor it is on to GMS.
reporting
After configuring the elevator(s), click OK to close the dialog box and download the settings to the Controller.
Copying Elevator Settings To/From Other Elevators

You can copy setting from an elevator to another elevator or range of elevators to speed up your system
configuration. Proceed as follows:
1. In the Configuration for Elevator dialog box, click Copy to open the Copy Elevator Parameters dialog box, where
you can select which elevators to copy setting to or from.
Copy From Elevator Enter the elevator number in the adjacent field to copy settings from.
Copy to Elevators Enter the elevator number (or the first in a range of consecutive elevators) to
copy the elevator (Copy From Elevator) settings to.
to Enter the last elevator in a consecutive range to copy settings to. To copy
settings to a single elevator, leave this field set to 0.

Auto Increment Enable to automatically define the device address (see Setting Device
Addresses Addresses and Address Ranges 204 ) for each elevator you are copying
settings to. The addresses are consecutive, starting from the elevator number
in the Copy to Elevators setting.

Configuring Unrestricted Floor Access

You can select elevators and floors that allow unrestricted access (no access control) at certain times of the day, for
example, a lobby during normal working hours. The system allows up to 32 different elevator time schedules you can
use for configuring unrestricted floor access.
Note: By default, any floor that an elevator services is considered secure. That is, under access control.
You must un-secure any floors using this procedure.
Setting Floor Accessibility

To access and control elevator accessibility, proceed as follows:
2. In the Controller dialog box, select Access Control > Elevators > Unlock Floors. The Configuration for
Elevator Floor Timezone dialog box opens. Configure the elevator according to the parameters below.
Elevators Enable the checkbox next to each elevator that will provide unrestricted access
during the time schedule. Available elevators only can be enabled.
TZ no. Click to open the Configuration for Reader Timezone dialog box, where you can
browse through the details of all configured time schedules. Use Prev TZ and
Next TZ to switch between schedules. Click OK to apply a schedule and close
the dialog box.
to Trigger this Event Shows the selected time schedule number.
Accessible Floors Enable the checkbox next to each floor number for the elevator to service it
with unrestricted access. Floors 1-64 as shown by default, click Floors 65-128
to display floors 65-128.
Select All Click to enable the checkbox for all floors.
Deselect All Click to disable the checkbox for all floors.
Previous View the previous unrestricted floor access configuration.
Next View the previous unrestricted floor access configuration (max. 32).
Clear Click to clear all fields back to default values for the current floor access
configuration.


Every elevator has a card reader associated with it. You must configure elevator card readers so that the system
correctly associates it with an elevator.

To configure an elevator reader, proceed as follows:
dialog box opens. Use the following sections as a guide parameters available in this dialog box.
3. Select a card reader by typing a number in the adjacent field and clicking Reader Number. Or, use and to
scroll through all readers. All configuration options are applied to the reader with the ID number displayed here.
4. Click the Flags tab, and enable the Elevator Reader option.
5. Click the I/O Parameters tab, and set the Extended Shunt/Strike Time setting to 0.


Viewing Elevator Status

You can view the tamper and offline status for elevators from the Controller dialog box:
2. In the Controller dialog box left-hand pane, click Elevators. The right-hand pane shows that tamper and offline
status for each connected and configured elevator. Each row represents an elevator controller.

blank page
Chapter 6
Configuring Building Management
Systems (BMS) Functionality
253
This section contains information about Pacom Controller Building Management Systems (BMS) functionality, and the
configuration requirements for BMS. Building Management Systems are designed to operate a range of building
services that are wired to operate using a centralized controller. For example, to control lights and air-conditioning or
heating systems. There are a number of manufacturers producing BMS hardware, many of which utilize the industry
standard BACnet and Modbus protocols for communications.
Pacom Controllers support both BACnet and Modbus protocols, so that they are compatible with most building
management controllers. To configure the system to use these protocols, see:
Configuring BMS BACnet Protocol 255 .
Configuring BMS Modbus Protocol 258 .
Setting the General BMS Configuration

To configure the Controller to use BMS and set the communications protocol(s), proceed as follows:
2. In the Controller dialog box, select Access Control > Building Management > General Settings. The BMS
General Configuration dialog box opens. Configure the parameters according to the following sections.
Time to update data to Enter the time in minutes for how often the BMS analog input and pulse count
TFTP server data from the Controller hardware device configuration is sent to the
Controller TFTP message queue. Once in the TFTP message queue, the update
time in the TFTP server settings control when the data is forwarded to a TFTP
server (see the Peer To Peer Configuration Guide, TFTP General Operation).
Midnight Enable so that BMS analog input and pulse count data from the Controller
hardware device configuration is sent to the Controller TFTP message queue
at midnight each day. Once in the TFTP message queue, the update time in
the TFTP server settings control when the data is forwarded to a TFTP server
(see the Peer To Peer Configuration Guide, TFTP General Operation). When
enabled this setting overrides the Time to update data to TFTP server
setting.
Enable Protocol Enable the checkbox next to each BMS protocol you want to configure the
system to use. Options are:
BACnet only enabled - Allows for up to 32 digital inputs and up to 64
digital outputs. No allowance for Modbus.
Modbus only enabled - Allows for up to 256 digital inputs, 64 digital
outputs and 16 analog inputs. No allowance for BACnet.
BACnet and Modbus enabled - Allowance for both BACnet and Modbus.
Allows for up to 32 digital inputs and up to 64 digital outputs for BACnet.
Allows for up to 32 digital inputs, 16 digital outputs and 16 analog inputs
for Modbus.
254 | Chapter 6 - Configuring Building Management Systems (BMS) Functionality

Configuring BMS BACnet Protocol, Inputs and

Actions
BACnet is a proprietary BMS protocol that is popular with some BMS controller manufacturers. Pacom Controllers
support BACnet.
Configuring BACnet Protocol, Inputs and Actions

To configure Controller to use the BACnet protocol, input and action parameters, proceed as follows:
2. In the Controller dialog box, select Building Management > BACnet Settings. The BACnet Configuration
dialog box opens. Configure the protocol according to the following sections.
Configuring BACnet Protocol Parameters

These settings determine the general communications settings for the protocol. Proceed as follows:
1. In the BACnet Configuration dialog box, click the Protocol Parameters tab and configure the protocol according
to the parameters below.
Port Number Enter the Controller port number to use for BACnet.
Note: Currently this must be the Ethernet port.
Link Layer Protocol Select the link layer protocol to use for BACnet operation.
Note: Currently only BACnet/IP protocol supported.
BACnet Device Instance Enter the Controller ID number. This associates the Pacom Controller with the
BACnet device.
BACnet Network Enter the number of the BACnet network that the Pacom Controller is on.
Number
Chapter 6 - Configuring Building Management Systems (BMS) Functionality | 255

Number of APDU retries Enter the number of retries that the Controller will attempt to contact the
BACnet device without a response before communication using BACnet is
marked as offline.
APDU timeout Enter the time in seconds that the Controller will wait for a response before
ending the communications attempt.
APDU segment timeout For future use only.
Tx. Segment window For future use only.
size
Rx. Segment window For future use only.
size
Alarm Enrolment Time Enter the time in minutes over which the Pacom Controller will keep contacting
the BACnet device until it is enrolled.
BACnet UDP Port Enter the UDP port number to use for BACnet.
Note: Port 47808 is the recommended port for BACnet.
Address of BBMD For future use only.
Configuring BACnet Inputs

These settings determine the inputs to send to the BMS using BACnet. Proceed as follows:
1. In the BACnet Configuration dialog box, click the BACnet Input tab and configure the input according to the
parameters below.
Input No. Enter the ID number for the input. Or, use and to scroll through all
inputs. Click Input No. to load its settings.
Notify For future use only.
Device Enter the ID number of the remote BMS device.
Notification Class For future use only.
Object Type Select the type of the object assigned to this input. For example, if the
object is a light on/off switch, select binary value.
Object Instance Object number of the object inside the remote device.
Event Type For future use only.
Point Type Select if the input is a normal input or an analogue input.
Point Number For future use only.
Delete Delete current input.
Copy Copy the parameters from an existing input to this input (see Copying
Settings To/From Other BACnet Settings 257 ).
Configuring BACnet Actions

These settings determine the output to send to the BMS using BACnet. Proceed as follows:
1. In the BACnet Configuration dialog box, click the BACnet Action tab and configure the action according to the
parameters below.

Action No. Enter the ID number for the action. Or, use and to scroll through all
actions. Click Action No. to load its settings.
Service Request Type Select how the action is to be performed on the "present value" of the object
in the remote device. Currently, only the Write Property option is supported.
Device Address Enter the device number of the remote BMS device.
Object Type Select the type of the object assigned to this input. For example, if the object
is a light on/off switch, select binary value.
Object Instance Object number of the object inside the remote device.
New "Present Value" For future use only.
Output Point Number For future use only.
Delete Delete current action.
Copy Copy the parameters from an existing action to this action (see Copying
Settings To/From Other BACnet Settings 257 ).
2. Click Reboot to load the BACnet protocol settings on the Controller for them to apply. Click OK to close the
dialog box.
Copying Settings To/From Other BACnet Settings

You can copy settings from a BACnet input or action configuration to one or more others to speed up your system
1. In the BACnet Configuration dialog box, click Copy to open the Copy Parameters dialog box, where you can
select which BACnet configuration to copy settings to or from.
Copy From Enter the BACnet configuration number in the adjacent field to copy the
settings from.
Copy to Enter the BACnet configuration number (or the first BACnet configuration
in a range of consecutive BACnet configurations) to copy the BACnet
configuration (Copy From) settings to.
to Enter the last BACnet configuration in a range of consecutive BACnet
configurations to copy settings to. To copy settings to a single BACnet
configuration, leave this field set to 0.

Configuring BMS Modbus Protocol

Modbus is a proprietary BMS protocol that is popular with some BMS controller manufacturers. Pacom Controllers
support Modbus.
Configuring Modbus Protocol, Inputs and Outputs

To configure the BMS for use with the Modbus protocol, inputs and outputs, proceed as follows:
2. In the Controller dialog box, select Building Management > Modbus Settings. The Modbus Configuration
dialog box opens. Configure the protocol according to the following sections.
Note: If the required device type or a specific input/output type does not appear in the list, contact Pacom
support.
Configuring Modbus Digital Inputs

These settings determine the digital inputs to send to the BMS using Modbus. The system supports up to 256 digital
inputs. Proceed as follows:
1. In the Modbus Configuration dialog box, click the Digital Input tab and configure the input according to the
parameters below.
Input No. Enter the ID number for the input. Or, use and to scroll through all
inputs. Click Input No. to load its settings.
Modbus Port Select the port that has been configured with the Modbus Protocol. Items
in black text show the ports that have been configured.
Device Type Select the device that is to be used. Select the device that is to be used.
Devices currently supported are:
Hsiang Cheng HC6000 Power Meter.
Advantech ADAM-4068 Relay Output Module.
Advantech ADAM-4055 Input Output Module.
Liaison PLC Device Module.
Device Address Enter the address of the device.
Input Type Select the digital input number on the selected Device Type option.
Delete Delete current digital input.

Copy Copy the parameters from an existing digital input to this digital input
(see Copying Settings To/From Other Modbus Settings 260 ).
Configuring Modbus Digital Outputs

These settings determine the digital outputs to send to the BMS using Modbus. The system supports up to 64 digital
outputs. Proceed as follows:
1. In the Modbus Configuration dialog box, click the BACnet Output tab and configure the output according to the
parameters below.
Output No. Enter the ID number for the output. Or, use and to scroll through all
outputs. Click Output No. to load its settings.
Modbus Port Select the port that has been configured with the Modbus protocol. Items in
black text show the ports that have been configured.
Device Type Select the device that is to be used.Select the device that is to be used.
Devices currently supported are:
Hsiang Cheng HC6000 Power Meter.
Advantech ADAM-4068 Relay Output Module.
Advantech ADAM-4055 Input Output Module.
Liaison PLC Device Module.
Output Type Select the Digital Output on the Device Type selected.
Delete Delete current digital output.
Copy Copy the parameters from an existing digital output to this digital output
(see Copying Settings To/From Other Modbus Settings 260 ).
Configuring Modbus Analog Inputs

These settings determine the analog inputs to send to the BMS using Modbus. Proceed as follows:
1. In the Modbus Configuration dialog box, click the Analog Input tab and configure the input according to the
parameters below.
Input No. Enter the ID number for the input (max. 16). Or, use and to scroll through
all inputs. Click Input No. to load its settings.

Modbus Port Select the port that has been configured with the Modbus Protocol. Items in
black text show the ports that have been configured.
Device Type Select the device that is to be used.
Analog Input Type Select the Analog Input on the Device Type selected.
Delete Delete current analog input.
Copy Copy the parameters from an existing analog input to this analog input (see
Copying Settings To/From Other Modbus Settings 260 ).
Copying Settings To/From Other Modbus Settings

You can copy settings from a Modbus input or output configuration to one or more others to speed up your system
1. In the Modbus Configuration dialog box, click Copy to open the Copy Parameters dialog box, where you can
select which Modbus configuration to copy settings to or from.
Copy From Enter the Modbus configuration number in the adjacent field to copy the
settings from.
Copy to Enter the Modbus configuration number (or the first Modbus configuration in a
range of consecutive Modbus configurations) to copy the Modbus configuration
(Copy From) settings to.
to Enter the last Modbus configuration in a range of consecutive Modbus
configurations to copy settings to. To copy settings to a single Modbus
configuration, leave this field set to 0.


BMS macros enable you to activate BMS controlled outputs when certain input conditions are met. For example,
setting a counter on a reader to turn on the lights in a room when a person enters (counter => 1) and turn them off
when everyone has left (counter = 0).
Note: The device that is providing the count must be configured as a counter.
You can configure up to 170 separate BMS macros in a Controller, each driven by an input from a hardware device.
BMS macros can also be used to trigger other macros to run a set of specific actions.

To configure BMS macros, proceed as follows:
2. In the Controller dialog box, select Building Management > BMS Macros. The BMS Macro Configuration
dialog box opens. Program the macro according to the following sections.
Macro No. Enter the ID number of the macro (max. 170). Or, use and to scroll
through all BMS macros. Click Macro No. to load its settings.
BMS Device Type Select the method of counting. That is, what to count. Options are:
Pulse Counter - Increments the count every time the device activates.
People Counter - Increments the count for valid card swipes only.
No Enter the ID number of the device that is providing the count.
Condition Select the condition (rule) type that has to be met in relation to the Count
setting to activate the Output Type setting. Options are:
Undefined - No condition is checked for and the macro does not activate
any output.
Equal To - The output will activate when the Count setting is reached.
Greater Than - The output will activate when the Count setting is passed.
Less Than - The output will activate when the Count setting is not reached.
Greater Than and Equal To - The output will activate when the Count
setting is reached or passed.
Less Than and Equal To - The output will activate when the Count setting
is reached or not reached.
Count Enter the value that the Condition setting watches for to activate the Output
Type setting.
Output Type Select what to activate if the condition is met. Options are:
GPO - Select for the macro to activate an output. Enter the output ID
CCTV - Select for the macro to activate a CCTV camera. Enter the camera
ID number in the CCTV Number field.
Trigger - Select for the macro to activate a trigger (for another macro).
Enter the trigger ID number in the Trigger Number field.
Activation Time The number of seconds (or minutes if the In Minute option is enabled) that
the output is activated for.
In Minute Enable for the Activation Time setting to be in minutes instead of seconds.

Configuring Pulse Counters

Pulse counting is a special Controller utility that you can use to count the number of digital actuations from a
hardware device (for example, a 1064CRI). There are various uses for this, such as keeping count of the number of
entries to an area, the number of users within an area, whether or not more than one person has entered an area
after a single card swipe.
The GMS system can be used to perform certain actions depending on the count, such as preventing further entry to
an area when a certain number of people are in it, or to activate an alarm or point if the count exceeds a set
threshold.
Configuring a Pulse Counter

To configure a pulse counter, proceed as follows:
2. In the Controller dialog box, select Alarm > Counter Settings. The Pulse Counter Configuration dialog box
opens. Configure the parameters according to the following sections.
Input No. Click after entering the Controller input number in the adjacent field (max.
32). Or, use and to scroll through all inputs. The device that is providing
the input signal (for example, a Pacom 1064) needs to be set as a pulse
counter.
Category Select the pulse counter category, which defines how the count is used.
Options are:
Normal Pulse Counter - The count is based on a signal being monitored
by the system. This could range from an I/O device that can be used as a
counter (for example, a 1064 CRI), which counts the number of door
openings to monitoring an electrical output for changes in values that will
count as a pulse.
Card Counter - The count is not incremental in that it is designed to be
used in ensuring that a single person has passed into an area after a valid
card swipe. The system requires a detection device in addition to the card
reader that is able to "see" how many people have passed it. For example,
having a turnstile in conjunction with the reader that will cause the system
to perform some action if the turnstile is operated more than once after a
single valid card swipe. That is, the system is double-checking that one
person passes into an area per card swipe. This type of feature can be used
where, after a valid card swipe, you want to double-check that the user has
gone on to enter a particular area.
Area People Counter - The count is based on number of users in the
area the counter belongs to. This is used in conjunction with an I/O
device that can be used as a counter, which is set to increment by one
when there is a valid access to an area and to decrement by one for
each egress from the area. This can be used in conjunction with area
profile settings to prevent more than a set number of people being in an
area at the same time. Another example can be a access controlled car
park, where the number of vehicles entering and leaving is counted so
that when the car park is full a sign can be illuminated.
Area Enter the area number for the pulse counter to operate in.
Trigger Enter the trigger ID number for the pulse counter to work in conjunction with.
The trigger looks at the relevant pulse counter and performs its actions
according to the counter rules.

Enable Counter change Enable for the Transaction Manager to display pulse count change
status messages messages. That is, each time the counter changes.
Click OK to close the dialog box and download the settings to the Controller.

blank page
Chapter 7
Configuring Listen-In Operation
265
The listen-in operation for the Pacom system is designed to allow existing Controllers to be able to send back audio
information from a site over a telephone line under the control of GMS operators. Listen-in operation can be used in
conjunction with alarm macros to provide a discreet audio feed from a site in trouble. The system can handle up to
four microphones per Controller.
Note: 8xxx or 1057 + modified 1060 Controllers support listen-in operation.
The system supports two-way communication between the monitoring GMS and the remote Controller (site), using
suitable devices. For example, having a combination microphone/speaker at the remote site will enable the GMS
operator to not only listen-in at the site, but to be heard there as well.
Requirements
GMS workstations at the monitoring center require the telephone number of the Controller it is using to receive
listen-in audio from. This is programmed using the Workstation Parameters dialog box, Telephone No 2 field.
For 1057 Controller operation, a modified 1060 Controller is required for each GMS workstation requiring listen-
in operation. The listen-in port of the 1060 connects to the operator headset. The telephone line connects to the
Modem port of the 1060. The modified 1060 configuration allows the listen-in terminal to connect in parallel with
the modem circuit. This enables the 1060 Controller to recognize when the remote Controller ends the call.
Currently, 1060 Controllers only can be modified for this type of operation.
For 8xxx Controller operation, an 8202 modem expansion card is required for dial out operations, with a normal
telephone required at the monitoring center.
If more than one microphone is required at the remote Controller (except 1057 with Europlex), they can be
wired using any available Controller or expansion card output (see Wiring Up Devices 268 ).
For 1057 operation with Europlex alarm panels, if more than one microphone is required at the remote
Controller, they must be wired using an eight output mezzanine card (see Wiring Up Devices 268 ).
Outputs 1 and 2 on the receiver at the workstation activate when a listen-in call is in progress and de-activate
when there is no activity on the listen-in connection.
Listen-in operation is available only on GMS workstations or standalone servers.
Deployment
The following figure shows basic connectivity for listen-in operation using 1057 plus modified 1060 Controllers.
The following figure shows basic connectivity for listen-in operation using 8001 Controllers.
266 | Chapter 7 - Configuring Listen-In Operation

Chapter 7 - Configuring Listen-In Operation | 267

Wiring Up Devices
1057 or 8xxx Controllers Using Pacom Alarm Panel (PAP)
Operation
Note: 1057 Controllers require firmware version 5.01 or later. 8xxx Controllers require firmware 1.02 or
later.
PAP operation refers to using the Pacom Controller as the actual alarm panel and not as an interface between GMS
and a third-party alarm panel (for example, Europlex). When using PAP operation, map listen-in devices logically
within GMS and the Controller as follows:
1. Connect the listen-in device to the required Controller input. This can be directly on the Controller itself, or
through an I/O expansion card/device.
2. Set the input to use vocab number 3 - this registers it as a listen-in device. The logical number is the position of
the device in the device list (1 - 64). For example, if you select output 10, 20 and 30 as vocab type 3 (listen-in
devices), then the logical listen-in device connects to output 10, logical listen-in connects to output 20, etc.
Note: There is no isolation as such, as each device is mapped to one output only. If isolation is required,
then a separate double throw relay is needed.
1060 or 1057/8xxx Controllers Using

Wire listening devices to the Controller mezzanine card or directly to as shown below:
Note: To provide isolation, the wiring uses two relays per device.
When using Europlex alarm panel operation on a 1057, listen-in devices must be wired using an eight
output expansion card and be switched in pairs.

Setting Up GMS
After setting up the hardware at the workstation and remote Controllers, set up the following parameters at the GMS
workstation and on the site map.
Program the telephone number at the workstation as follows:
1. Select Tools > Workstation Setup. The Workstation Parameters dialog box opens.
2. In the Telephone No. 2 field, enter the telephone number.
Add listen-in devices to the site map as follows:

1. In the GMS Map Editor, select Device ( ), then place them on the site map. You can enter up to four listen-in
devices onto one Controller site map.
2. In the Device Configuration dialog box for the listen-in device, in the Device Type list, select Listen-in Device,
then click OK.
Chapter 7 - Configuring Listen-In Operation | 269

Operating Listen-In Devices

In the site map, when the operator selects a listen-in device, the Listen-in Device Status dialog box opens
automatically and a GMS log message appears that the listen-in device (1 – 4) is selected.
To use the listen-in device, enable the Establish Call option, then click OK. This requests the remote Controller, over
the Ethernet, to start a listen-in call. The telephone number of the workstation is sent as part of the call request.
For 1057 Controller Operation

If there is no call already in progress to the receiving workstation, the remote Controller switches to the modem
and dials the number sent in the request. It also switches to the required microphone, which is also sent in the
request.
The 1060 Controller at the workstation answers the call and verifies that at the other end is a valid Controller. If
so, it instructs the remote Controller to enter listen-in mode, causing it to switch from being modem connected
to the listen-in line. At the same time the workstation Controller switches the listen-in terminals to the line in
order to connect the operator headset. The operator can now listen to the selected microphone.
For 8xxx Controller Operation

The remote Controller switches to the modem and dials the number sent in the request. It also switches to the
required microphone, which is also sent in the request.
When the call is answered, the Controller switches to the audio feed after three seconds and also begins
generating required messages. If the call is unanswered, busy or no dial tone is present...
Once the listen-in device is operating, its site map icon changes from black to pink. Listen-in messages are also
generated and show in the Transaction Manager.
Operators can select another microphone from the site map during a call. When the remote Controller receives the
command, it switches to audio feed from the requested microphone.
To end a call, enable the Hangup Call option in the Listen-in Device Status dialog box, then click OK. Calls are
automatically terminated if the call idle timeout occurs (Enter Connection Time setting). When the call ends, the
remote Controller switches back to the modem and disconnects the listen-in terminals. For 1057 operation, the
remote Controller sends a tone to the workstation 1060 Controller, causing it to disconnect the call, and both ends
hang up.

Chapter 8
Configuring Intercom Operation
271
Intercom operation refers to access requests by users from an intercom device, input point or card reader. When the
system receives the intercom "call", it notifies GMS operators of the call and provides a range of options:
Allow Access.
Deny.
Wait.
A special .INI file requires configuration for controlling the general behavior of GMS when an intercom call is received
and when an operator actions an intercom call (see Configuring GMS - Adminsitrator Guide, The Intercom.INI File).
Intercom activity reports are also available through GMS and require some setting up before use (see Configuring
GMS - Adminsitrator Guide, Configuring Intercom Report Options).
Intercom response actions can be configured to include additional operations with devices connected to, and
controlled by GMS. For example, opening a door, activating an output to turn lights on, streaming video camera
feeds, operating a CCTV switcher, etc. Configuration of response actions is performed using xml-based scripts (see
Scripting Intercom Actions 275 ).
GMS supports two types of intercom operation:
Internal to GMS - Uses "normal" devices to generate the intercom request. That is, the request is made by
triggering an input point or card reader connected to the Controller (see Setting Up Internal (GMS) Intercoms
273 ). Voice communications are not supported using input points/readers for intercom operation.
External to GMS - Uses third-party intercom device hardware (for example, Jacques intercom system) to
provide intercom requests and voice communications. Operators will have an intercom master station that
connects to slave intercoms for voice communications (see Setting Up External Intercom Systems 274 ).
Intercom connectivity with GMS - Internal and External. Note: The dashed line colors illustrate
mapping between GMS workstation/master intercom units and slave intercom units
272 | Chapter 8 - Configuring Intercom Operation

Setting Up Internal (GMS) Intercoms

"Internal" intercom operation uses normal inputs and/or card readers connected to the Controller to generate
intercom "calls". Direct voice communications between the intercom requestor and the GMS operator is not available
using this system.
For internal intercom operation, the input point(s)/card readers used as intercom "triggers" must be configured on
the site map with corresponding intercom devices. That is, each intercom point requires two site map objects - input
point or card reader and intercom device. Mapping between the objects is provided using the identification number of
the associated input point/card reader as a configuration parameter of the intercom object (see Configuring GMS -
Administrator Guide, Drawing and Adding Objects to Site Maps).
How the System Works

In a general sense, the intercom system workflow for internal operation can be described as follows:
1. A person triggers the input associated with the intercom point to make the "call". This could be, for example, a
wall mounted button connected to an input or a card reader. For card readers, the person must swipe their
access card and receive a valid entry response.
Note: The input point/card reader will be available for intercom use according to normal configuration
paramaters. For example, during modes and times of day that the input point/card reader is active
(available for use).
2. GMS receives the signal from the input/card reader (trigger) and recognizes it as an intercom call.
3. GMS analyzes the call using a set of pre-defined rules, and generates an "Intercom Access Request" (IAR).
4. The GMS server dispatches the IAR to each applicable GMS workstation for actioning. All current IARs are
displayed in list form to GMS workstation operators through the Intercom Manager.
5. A GMS workstation operator then selects an IAR from the list in order to action it.
Chapter 8 - Configuring Intercom Operation | 273

Setting Up External Intercom Systems

Note: It is assumed that external intercom system devices have been installed and configured by qualified
persons and that required information, such as intercom unit identifications numbers have been noted.
"External" intercom operation uses third-party intercom device hardware to generate intercom "calls". Direct voice
communications between the intercom requestor and the GMS operator is available using this system. The external
intercom system notifies GMS of intercom requests through the Intercom Gateway component and a GMS intercom
system plug-in, which is a specific device driver for interfacing the two systems. Events between the two systems are
synchronized and controlled from within GMS.
For external intercom operation, intercom device objects must be configured on the site map (see Configuring GMS -
Administrator Guide, Drawing and Adding Objects to Site Maps and Mapping External Intercom Devices 274 ). Mapping
between the site map intercom objects is provided using the identification number of the physical intercom device as
it is defined in the plug-in with a configuration parameter of the intercom object.
Note: The Intercom Gateway component of GMS and the required intercom system plug-in must be
installed and the Intercom Gateway Windows service configured before external intercom configuration
can be completed (see the GMS Installation Guide, Intercom Gateway).
How the System Works

In a general sense, the intercom system workflow for external operation can be described as follows:
1. A person uses an intercom device to make the call.
2. GMS receives the signal from the intercom unit through the Intercom Gateway and intercom system plug-in
driver components and recognizes it as an intercom call.
3. GMS analyzes the call using a set of pre-defined rules, and generates an "Intercom Access Request" (IAR).
4. The GMS server dispatches the IAR to each applicable GMS workstation for actioning. All current IARs are
displayed in list form to GMS workstation operators through the Intercom Manager.
5. A GMS workstation operator then selects an IAR from the list in order to action it.
Mapping External Intercom Devices

Mapping between GMS workstations and master intercom units is performed through configuration of the external
intercom system plug-in and may vary according to the plug-in being used. The plug-in uses an .INI file for
configuration that must be stored in the same folder as the Intercom Gateway. Its name is x.INI, where x is the
name of the third-party intercom system. For example, for Jacques intercom systems, the file is called Jacques.INI.
Note: Due to each plug-in being specific to the requirements of the associated third-party intercom
system, configuration is beyond the scope of this documentation - refer to the Intercom Driver document
supplied with the intercom system plug-in.

Scripting Intercom Actions

Generally, an intercom point has a number of peripheral devices associated with it, such as a door lock, one or more
output points (for example, to control lights), one or more CCTV cameras etc. When an intercom "call" is made, or an
operator actions an intercom call, it is usually required to send command(s) to the associated peripheral devices. For
example, it may be necessary to turn the lights on when a person presses the intercom button, to unlock/lock the
door, and to switch lights off a few seconds after the person passes through the door, and so on.
GMS external intercom integration is designed to be as flexible as possible, and it uses scripts to control the
peripherals associated with intercom points.
Caution: It is highly advisable to test-run any script before deploying it.
Script Definition
A script is a set of one or more commands. Each intercom script must be described as an individual section within
the GmsIntercomScripts.config file, located in the GMS server, GMS\Customer\Intercom folder. The files in this folder
are automatically synchronized with any other GMS servers (slave/remote) and are also backed up/restored as
required during normal GMS system operations. Basic rules for intercom scripts are:
A script section begins with [ScriptName] followed by one or more commands.
Each command must be on a separate line.
A script section ends when another script sections starts, or at the end of the file. The file may contain any
number of script sections.
Script names and commands are case-insensitive. A script name can have spaces.
Empty lines are ignored. Lines beginning with ";" and "//" are interpreted as comments. Anything else is parsed
as a line containing a command.
The script processor validates the entire script before processing it. An incorrectly specified command will
prevent the script from been executed.
Associating Intercom Events with Scripts

GMS intercom point configuration allows associating certain intercom events with a script. When an association exists,
GMS automatically runs the script when the event occurs. The following intercom events can be associated with
scripts: OnCreate, OnSelect, OnDeny and OnLetIn.
OnCreate runs when a new intercom request is generated. It is also executed when an operator selects the Wait
option.
OnSelect runs when an operator selects an item in the Intercom Manager, or clicks a flashing intercom point
device icon on a site map.
OnLetIn runs when an operator selects the Allow Access option.
OnDeny runs when an operator selects the Deny option, and also when the Request Time to Live timer
expires for the call (see Configuring GMS - Administrator Guide, Drawing and Adding Objects to Site Maps).
Note: There are no "default" scripts. Any automated processing to be performed by GMS, such as
unlocking a door, requires a script.
A new event for a particular intercom point will stop a currently running script (triggered by a previous event for the
same intercom point), even if the new event does not have a script associated with it. For example, the OnSelect
script may still be executing when an operator selects the Allow Access option, in which case it will be terminated
regardless of whether or not there is a OnLetIn script.
Scripts for Intercom Points Associated with More than one Door
(Entrance)
If an intercom point is associated with more than one door (maximum is three), it may be required to execute a
specific OnLetIn script when a particular door is selected for Allow Access.
To define a script that should be executed on Allow Access for a particular door, add it to the required script section
by adding a period (".") to the end of the script section name, then adding the door name to it. For example, if an
intercom point has two associated doors – one named "LeftDoor" and the other "RightDoor", define the OnLetIn script
name for the intercom point (in the following example, "ExampleScript" is used) and configure the scripts inside the
GmsIntercomScripts.config file, as follows:
[ExampleScript.LeftDoor]
Script commands here…

[ExampleScript.RightDoor]
Script commands here…
When the Allow Access option is selected for a particular door, GMS first attempts to find and run an OnLetIn script
that contains the door name. If not found, it will find and run an OnLetIn script without the door name.
Note: The door name(s) must also be specified in the Intercom Configuration dialog box for the intercom
point in GMS.
Script Configuration File Data

GMS maintains intercom point configuration data in XML-based text files. Separate files are required for each GMS
site.
Note: The files are located in the GMS\Customer\Intercom folder, named IntercomDevicesConfig_NNNN.
XML, where NNNN is a 0-padded, 0-based site number.
Intercom point configuration data contains a number of "handling profiles". Inside a handling profile is a provision for
associating intercom events with scripts.
Example:
<IntercomDevices>
<IntercomDevice>
<IntercomPoint ShortDisplayName="West entry" IntercomPointNo="0"
FullDisplayName="Intercom outside West entry" AreaNo="0">
<HandlingProfiles>
<HandlingProfile TTL="1" ProfileID="1" IARPriority="1" Info="profile 1">
<Scripts>
<OnSelect scriptName="OnSelectScript"/>
<OnLetIn scriptName="IntercomDoorOpenScript"/>
<OnDeny scriptName=""/>
<OnCreate scriptName="OnCreateScript"/>
</Scripts>
… and so on.
In the above example, the OnSelect, OnLetIn and OnCreate events have associated scripts, but OnDeny does not.
Parameterized Values
It may be useful to re-use the same script for several intercom points. For example, there can be a number of
intercom points with identical peripherals (for example, door, outputs controlling lights, the same number of CCTV
cameras etc). The scripts for these intercom points would be virtually identical, with the only difference being the
actual ID numbers of the peripherals. For instance, an OnSelect script could be defined as turn the light on, turn
privacy indicator on and show the live video from the overhead camera - the same sequence can be applied to more
than one intercom point, as long as the correct peripherals are triggered.
To allow a script to be used by several intercom points, most of the script command arguments can be
parameterized. For instance, a pointNo argument and Output OFF command can be defined as a parameter. Any
number of parameters can be specified.
Example:
<HandlingProfile TTL="1" ProfileID="1" IARPriority="1" Info="profile 1">
<Scripts>
<OnSelect scriptName="OnSelectScript">
<parameters>
<Parameter Name="%pointNo%" Value="1" />
<Parameter Name="%siteNo%" Value="123" />
</parameters>
</OnSelect>
<OnLetIn scriptName="IntercomDoorOpenScript"/>

Inside a script command, parameters are entered by enclosing the parameter name within "%" and "%". Parameter
names are case-insensitive.
Note: The <parameters> element has lower-case "p". The <Parameter> element has an upper-case
"P".
Example:
Output OFF (%siteNo%/%pointNo%)

Command Execution
The GMS intercom script processor runs script commands in groups. A group is defined as a set of commands before
(and including) a WAIT command, and the last group is limited by the end of the script file. Each command in a group
is started simultaneously and is run in parallel. The script processor waits for all commands of the currently running
group to finish, before running the next group.
Example:
[OnCreate]
DOOR ACCESS (3/5) duration=4000
Output ON (4/7) duration=5000 pulse=500/500
WAIT 3000
Output OFF (4/7)
WAIT 3000
Output ON (4/7)
The above example contains three command groups:
Group Syntax Description

1 DOOR ACCESS (3/5) duration=4000 This group will take five seconds to run,
Output ON (4/7) duration=5000 pulse=500/500 because of the Output ON
duration=5000 command. All commands
WAIT 3000 start simultaneously, with the Output ON
command taking the longest to finish.
Note: The WAIT 3000 command

will finish before the Output ON
command finishes.
DOOR OPEN (the command terminates

immediately)
Output ON 1 sec, 2 sec, 3 sec, 4 sec, 5
sec
WAIT 1 sec, 2 sec, 3 sec
2 Output OFF (4/7) This group start after the first group
WAIT 3000 commands finish and will take three
seconds to complete its commands.
3 Output ON (4/7) This group starts after the second group
commands finish and runs instantly as
there is no WAIT command and the
Output ON command has no duration
parameter.
For intercom commands information, see Intercom Script Commands 279 .

Intercom Script Commands
CAMERA HIDE
Closes a live video dialog box currently open for a particular camera. The command does nothing if the live video
dialog box is not currently open.
Syntax
CAMERA HIDE (SiteNo/CameraNo)
Arguments
(SiteNo/CameraNo)
Mandatory. SiteNo and CameraNo are 1-based. Can be parameterized.
Example:
; Closes a live video dialog box currently open for camera 3 in site 7
CAMERA HIDE (3/7)
CAMERA SHOWLIVE
Opens a live video dialog box for a particular camera, similarly to an operator clicking a camera icon on a site map.
Syntax
CAMERA SHOWLIVE (SiteNo/CameraNo) [POS=X,Y] [SIZE=W,H]
Arguments
(SiteNo/CameraNo)
Mandatory. SiteNo and CameraNo are 1-based. Can be parameterized.
POS
Optional. Defines coordinates for top left corner of the dialog box. Can be parameterized.
SIZE
Optional. Defines width and height of the dialog box. Can be parameterized.
Example:
; Show live video from camera 3 in site 7, the dialog box position is 100,100
CAMERA SHOWLIVE (7/3) POS=100,100
DOOR ACCESS
Unlocks a door.
Syntax
DOOR ACCESS (SiteNo/DoorNo) [DURATION=seconds]
Arguments
(SiteNo/DoorNo)
Mandatory. SiteNo and DoorNo are 1-based. Both values can be parameterized.
DURATION=seconds
Optional. If defined, the door is unlocked for the value of DURATION, in seconds. Otherwise, the shunt time
for the door as configured in the hardware is used. Can be parameterized.

Example:
; Unlock door 4 in site 50
DOOR ACCESS (4/50)
; Keeps door 4 in site 50 unlocked for 6 seconds
DOOR ACCESS (4/50) DURATION=6

DOOR CLOSE
Locks a door.
Syntax
DOOR CLOSE (SiteNo/DoorNo)
Arguments
(SiteNo/DoorNo)
Mandatory. SiteNo and DoorNo are 1-based. Can be parameterized.
Example:
; Locks door 4 in site 50
DOOR CLOSE (4/50)
DRIVER NATIVE
Sends a user-defined command to the intercom plug-in. A command will be communicated to the plug-in along with
six 1-byte arguments, which the plug-in will interpret it in whichever way. The commands are plug-in-specific, not
generic.
Syntax
DRIVER NATIVE ddd1 ddd2 ddd3 ddd4 ddd5 ddd6
Arguments
ddd
A placeholder for a single decimal value between 0 and 255. All six must always be specified, even if a
particular command for a particular plug-in needs only one. Can be parameterized.
Example:
DRIVER NATIVE 110 112 1 77 0 0
INTERCOM CALL
Initiates a call to a specified intercom device. The same as if Call is selected in the GMS Intercom Status dialog box
for the device.
Syntax
INTERCOM CALL (SiteNo/PointNo)
Arguments
(SiteNo/PointNo)
Mandatory. SiteNo and PointNo are 1-based. Can be parameterized.
Example:
; Call intercom device 50 in site 4
INTERCOM CALL (4/50)
Note: The command obeys the same rules as selecting Call in the GMS Intercom Status dialog box for the
device – a call can be initiated only if the device is in idle state and there are currently no other calls
associated with the same workstation.


INTERCOM HANGUP
Disconnects a call to a specified intercom device. The same as if Hangup is selected in the GMS Intercom Status
dialog box for the device.
Syntax
INTERCOM HANGUP (SiteNo/PointNo)
Arguments
(SiteNo/PointNo)
Example:
; Disconnect call to intercom device 50 in site 4
INTERCOM HANGUP (4/50)
Output OFF
Turns an output point off.
Syntax
Output OFF (SiteNo/PointNo)
Arguments
(SiteNo/PointNo)
Example:
; Turn OFF output point 4 in site 50
Output OFF (4/50)
Output ON
Turns an output point on, with optional pulsing.
Syntax
Output ON (SiteNo/PointNo) [PULSE=msON/msOFF [DURATION=ms]]
Arguments
(SiteNo/PointNo)
PULSE=msON/msOFF
Optional. If defined, the point is pulsed - staying ON for the duration of msON, and OFF for the duration of
msOFF (minimum pulse time = 50ms). Both msON and msOFF can be parameterized.
DURATION=milliseconds
This argument should be used only with the PULSE argument. It is ignored otherwise. If PULSE is defined
and DURATION is not, DURATION is set to 0. With DURATION specified, the command "locks" the
current command group for the specified number of milliseconds (minimum = 50ms). With a DURATION
value greater than 0, the output point is turned off at the end of the command execution. The milliseconds
value can be parameterized.

Caution: If DURATION=0, the command runs indefinitely, therefore, the entire command group and
script runs indefinitely. It can be stopped only by starting another script for the same intercom point.
Example:
; Turn ON output point 4 in site 50
Output ON (4/50)
; Pulse output point 4 in site 50, 500 milliseconds ON and 100ms OFF, for a duration of 3 seconds
Output ON (4/50) PULSE=500/100 DURATION=3000

RTU CMD
Sends a user-defined command to a Pacom Controller (previously known as an "RTU"). The effect of the command is
the same as if an operator uses a "Send a user-defined command" from GMS.
Syntax
RTU CMD SiteNo FC ddd ddd …
Arguments
SiteNo
Mandatory. A value between 1 and 10000 (1-based). Cannot be parameterized.
FC
Mandatory. A decimal value between 1 and 255 corresponding to the required function code for the user-
defined command. Cannot be parameterized.
ddd
A placeholder for a single decimal value between 0 and 255 corresponding to the required function code for
the user-defined command. The values correspond to D1, D2 etc. At least D1 must be present. Cannot be
parameterized.
Example:
; Turn ON output point 3 of Controller 100 - user-defined command function code 100 and data 14
RTU CMD 100 14
WAIT
Pauses running the script for the specified number of milliseconds.
Syntax
WAIT milliseconds
Arguments
milliseconds
Mandatory. Can be parameterized.
Example:
; Pause the script for 3 seconds
WAIT 3000

blank page
Chapter 9
Using the IVR Facility
287
The GMS interactive voice response (IVR) facility allows engineers to call a GMS workstation in order to place a site in
Suspend mode and to send commands to Controllers. IVR requires a voice over Internet protocol (VoIP) and/or ISDN
(using Dialogic hardware) drivers for operation. Suspend mode is a temporary system mode that disables alarm
reporting for the purposes of testing input and output points for correct operation.
An example of use would be a technician on site wanting to check the operation of input points. They could use IVR to
call in and place the site in Suspend mode. Then, walk around to the various input points and activate them - GMS
keeps a record of all point activity during Suspend mode. The technician can then use IVR to play back all the events
that have been recorded during Suspend mode for the site, confirming the operation of each tested input point.
Note: A site can be entered into Suspend mode only from Day mode.
If a site (master) has other sites linked to it (slaves) that will normally follow its mode changes, you can
control whether or not they will follow the master site into Suspend mode using the GMS32.INI file on the
GMS server. In the GMS32.INI file, under [SYSTEM PARAMETERS], add the line Linked RTUs=x,
where x = 0 for linked sites to ignore the master site entering Suspend mode, or x = 1 for linked sites to
follow the master site into Suspend mode. In cases where linked sites are being used in this way, the
Summary Manager may require holding the SHIFT key whilst refreshing the display for the site colors to
update.
IVR callers must supply a valid user ID number and PIN as well as an overall system security code in order to gain
access to IVR menus. In addition to the log on requirements, callers must also be:
In the GMS global contacts list.
Categorized as "Engineer" user type.
The following image shows the general IVR structure. For information on configuring the IVR facility, see Configuring
GMS - Administrator Guide, Configuring IVR Operation.
Note: The following procedures are generic, as IVR operation is customizable.
Logging On to IVR
To log on to the IVR facility, proceed as follows:
1. Call the GMS workstation. When the IVR facility answers, you are prompted for a:
User ID number.
PIN.
Security code (this is common for all IVR users).
Enter security credentials as required. When the system logs you on, the main menu options are presented.
Switching a Site into Suspend Mode

To switch a site into Suspend mode from Day mode, proceed as follows:
1. After logging on, select the option for placing a site in Suspend mode.
2. Enter the site ID number.
3. Enter the length of time for Suspend mode to last for. When entering the information, the first two digits
represent hours, the second two for minutes. For example, 0130 equals one hour and 30 minutes.
288 | Chapter 9 - Using the IVR Facility

Note: When using IVR, you must always enter the full amount of requested digits when entering
information. For example, to select site "13" when the IVR requests four digits, enter "0013".
4. Enter a contact telephone number, followed by the hash ("#") key. The IVR system will use this number to
contact you when the site is approaching the end of Suspend time (if configured to do so).
5. Select the option to confirm the request. The site is switched to Suspend mode and begins counting down.
Changing Suspend Mode Time

After switching a site to Suspend mode, you can alter the Suspend mode remaining time. To do so, proceed as
follows:
1. Call and log on to the IVR facility. You will immediately be able to interact with the site you previously placed
into Suspend mode.
2. Select the option for changing Suspend mode time.
3. Enter the new length of time for Suspend mode to last for.
4. Select the option to confirm the request. The site Suspend mode time is amended and begins counting down.
Switching a Site From Suspend Mode

To switch a site into Day mode from Suspend mode, proceed as follows:
into Suspend mode.
2. Select the option for switching the site from Suspend back to Day mode.
3. Select the option to confirm the request. The site immediately returns to Day mode.
Playing Back Recorded Events

After placing a site in Suspend mode, you can have the IVR system play back any events that occurred during
Suspend mode. To do so, proceed as follows:
Note: You can play back events whilst the site is still in Suspend mode.
into Suspend mode.
2. Select the option for playing back Suspend mode events.
Once you have begun playing back events, use the stated options as required to replay an event message or abort
event play back.
Sending Controller Commands

The IVR facility supports a range of Controller commands that can be sent to a site at anytime (does not require
Suspend mode). The following commands are supported:
Reset latched alarms - Resets any latched input/output points.
Isolate input - Isolates the selected input point for a period of time (hours and minutes).
De-isolate input - De-isolates the selected isolated input point.
Activate output - Activates the selected output point for a period of time (hours and minutes).
Deactivate output - Deactivates the selected active output point.
Soak input - Soaks the selected input point for a period of time (days).
Unsoak input - Unsoaks the selected soaked input point.
To send a command to a Controller, proceed as follows:
1. After logging on, select the option for accessing Controller commands.
2. Enter the Controller ID number.
3. Select the command option as required.
4. Enter the command parameters as required for the command. For example, isolating an input requires you to
enter the input point ID number and the number of hours and minutes to isolate it for.
Chapter 9 - Using the IVR Facility | 289

Note: When using IVR, you must always enter the full amount of requested digits when entering
information. For example, to select site "13" when the IVR requests four digits, enter "0013".
5. Select the option to confirm the request. The command is applied to the selected Controller.
290 | Chapter 9 - Using the IVR Facility

Chapter 10
Apendices
291
A - Using the 1057/8001 Controller LED Display

Pacom 1057 and 8001 Controllers indicate current operating conditions on a seven-segment LED display, located on
the front panel. There are two sets of characters, one set that is displayed on start-up during self test and
initialization, and one that is a running diagnostic, displayed at any time after start-up.
Controller Start-Up Display

During start-up the display will run through each of the characters as each of the test and initialization steps is
performed (usually too fast to be visible). If any of the steps should fail, the start-up will halt and display the test that
has failed for a few seconds before restarting.
Display Description
Processor SIM configured - determining chip to run in.
Flash EPROM test.
RAM test.
Initializing data segment from Flash EPROM.
Initializing "malloc" space.
C++ global constructor calls.
Finished stage one initialize.
Restarting to run in other chip.
Stage two initialization begins - initialize buffer memory, RTC and check for copy
software.
Read external EEPROM data into internal. If either "E" or
"e" is
displayed, then
Read and check internal EEPROM data. one of the two
EEPROMS have
failed. "e" is for
EEPROM 1 fail,
which contains
the system
parameters
(that is,
Controller
address, port
parameters and
alarm
parameters)
and is labelled
on the
Controller PCB
as "system".
"E" is for
EEPROM 2 fail,
which contains
the access
control
parameters and
is labelled on
the 1057 PCB
as "access".
Initialize alarm panel and access control modules.
Initialize PSP, BMS and software download modules.
292 | Chapter 10 - Apendices

Display Description
Cold start initialize of all ports.
Initialize all ports.
Blank - finished stage two initialize.

Blank display
Cycles and displays running diagnostic codes (see table below).
Outer segment
cycle
Controller Running Diagnostics Display

The character sets displayed during the running diagnostics are dependant on the network type. When connected to a
UDP/IP network, additional characters are displayed and the meaning of the other characters is slightly different. If
more than one condition is active, then the display will alternate between characters. The running diagnostic displays
are shown after the Start-Up displays.
Display Description
Normal operation.
Outer segment
cycle
Controller offline.
Data line DCD failure on RS232 ports.

**Loss of communication to LAN adapter.
Data modem failure on RS232 ports.
**LAN adapter fail or loss of power to it.
Communications failure (primary and any configured backup methods) to receiver
(Base Station, TransIT etc).
Controller cover open (tamper switch activated).
Branch Controller or network connection has failed.
**LAN adapter loss of LAN connection.

**Router failed.
Controller on security poll (SDLC/asynchronous polling).
Controller using dialup communications.
Controller using the port configured for secondary or tertiary communications because
primary communication has failed.
Indicates +5V supply is OK. If not illuminated, the +5V supply is faulty. Check AC
connector.
Decimal point
Controller fault. Contact Pacom.
Blank display
Note: ** Indicates UDP/IP/PPP networks only.
Chapter 10 - Apendices | 293

B - GMS32.INI File Reference

The follwing section details GMS32.INI file parameters. It is designed as a reference for technicians when configuring
GMS.
Note: Not all listed entries are available in all configuration files, as many are dependant on various GMS
installation and setup options, features and licensing. Likewise, functionality of all entries may not be
available on all systems.
Entries that are highlighted in blue generally represent settings that are either automatically configured by
GMS or are configured using GMS.
Generally, most settings are required on the GMS server GMS32.INI file, however, some are required in
the workstation GMS32.INI file - these are noted where required.
Some features/functions have supporting documents that provide greater detail than listed here. To access
these documents, contact Pacom Support and quote the "TT" number reference as shown (these
references are provided where available only).
[MAIN SERVER], [SLAVE SERVER] and [REMOTE SERVER] Sections

Parameter Values/Value Type Default Description
Name=x x = Machine name (text) GMSMAINSV The GMS server machine name(s) or IP
GMSSLAVESV addresses.
GMSREMOTESV
Share=x x = Folder name (text) GMS The share name of the GMS folder on the
server.
Domain=x x = Domain name (text) GMSDOMAIN. The Windows domain the GMS server is
LOCAL located in.
Use Socket for WS-x=y x = Workstation number 0 The type of connection to use between
(integer) workstation and servers.
y = 0 = Use sockets
y = 1 = Use named pipes
WS-x IP=y x = Workstation number 192.168.0.11 Workstation IP address(es).
(integer)
y = IP address (text)
SQL Server Name=x x = Machine name (text) GMSSQLSV SQL server machine name or IP address.
GMS Database Name= x = Database name (text) GMS32DBASE The GMS database name. References exist
x for this item - quote TT4153 and TT5050.
Note: Required only if SQL is

running on a separate machine to
the GMS server.
SQL User=x x = User name (text) SA The SQL user name for logging on to SQL
databases.
SQL Password=x x = Password (text) Password The SQL password used for logging on to
SQL databases.
SQL Connection x = 0 = SQL 1 Determines if SQL or Windows
Trusted=x x = 1 = Windows authentication is used for SQL database
connections.
[REMOTE SERVER]
Active Consoles=x,x,x x = Workstation number 0 Workstation numbers entered here are
... (integer) allowed to connect to the Remote server if
the Main and Slave server(s) are not
running GMS or are unavailable.
[SUB SERVER] Section

Count=x x = Number (integer) 0 The total number of Sub-servers.
No Card Access=x x = 0 = Card access 0 Determines if card access management is
x = 1 = No card access allowed on Sub-servers.
Note: This setting applies to all

Sub-servers.
Name-x=y x = Sub-server number GMSSUBSV001 The Sub-server machine name or IP

(integer) address.
y = Machine name (text)


Domain-x=y x = Sub-server number GMSDOMAIN. The Windows domain the Sub-server is
(integer) LOCAL located in.
y = Machine name (text)
Share-x=y x = Sub-server number GMS The share name of the GMS folder on Sub-
(integer) server.
y = Folder name (text)
Range-x=(y) x = Sub-server number (1-50) The Controllers (sites) that the Sub-server
(integer) controls. A range of sites can be specified
y = Controllers using start and end site numbers (for
example, "(200-750)", or single site
numbers in a comma-separated list (for
example, "1,3,5,222").
Highest Priority-x=y x = Sub-server number 32 The highest event priority that can be
(integer) processed by the Sub-server. Higher
y = Priority number (integer) priority events are processed by the Main
server.
Time-x=(y,z) x = Sub-server number 00:00,24:00 The start and end times per day that the
y = Start time in HH:MM format Sub-server is allowed to monitor alarms.
(text) Outside this time all alarms are processed
z = End time in HH:MM format by the Main server.
(text)
Mapping-x=y x = Sub-server number 1 Determines if the Sub-server connects to
(integer) the Main server through a Controller
y = 0 = Controller (through which all communication will flow),
y = 1 = Network or by using the network (LAN/WAN).
Note: Card access is not possible

using a Controller connection.
CPU Connected-x=y x = Sub-server number 0 Determines if the Sub-server connects

(integer) directly to a Controller, or a Base Station/
y = 0 = Controller TransIT.
y = 1 = Base Station/TransIT
[SA SERVER] Section

SQL Server Name=x x = Machine name (text) GMSSQLSV SQL server machine name or IP address.
GMS Database Name= x = Database name (text) GMS32DBASE The GMS database name. References exist
x for this item - quote TT4153 and TT5050.
Note: Required only if SQL is

running on a separate machine to
the GMS server.
SQL User=x x = User name (text) SA The SQL user name for logging on to SQL
databases.
SQL Password=x x = Password (text) Password The SQL password used for logging on to
SQL databases.
SQL Connection x = 0 = SQL 0 Determines if SQL or Windows
Trusted=x x = 1 = Windows authentication is used for SQL database
connections.
[SYSTEM PARAMETERS] Section

ALT Tag Included=x x = 0 = No 0 Determines if temporary access is included
x = 1 = Yes in automatically created access level
templates when using the CMS interface.
References exist for this item - quote
TT3834.
AutoFixDeleteCmd x = Controller number(s) N/A Specifies Controllers (sites) to exclude from
ExcludeRtus=x,x,x ... (integer) being updated by the Auto-fix functionality.
Auto-fix functionality automatically updates
Controllers if a discrepancy is found
between the card details in the Controller
local card database and that of GMS.
TT4973.


AutoLogon=x x = 0 = No 0 Determines if Auto-logon to a GMS server is
x = 1 = Yes enabled. When enabled, GMS can be
started and will not require a GMS user to
log on in order to access the application
features.
AutoPrintFireAlarm x = 0 = No N/A Determines if GMS automatically prints a
Report=x x = 1 = Yes cardholder status (IN or OUT) report in the
event of a fire alarm. References exist for
this item - quote TT5145.
Backup=x Text C:\GMS32B The path to the GMS backup folder.
BCP_CP=x x = Codepage value (integer) 1250 Force the Bulk Copy Data command called
by GMS to use a specific language
codepage. This may be required for non-
English languages where characters may be
replaced by junk characters in databases if
an incorrect codepage is used. References
exist for this item - quote TT5070.
CMS Folder=x x = Folder path and name C:\GMSTOCMS The path to the CMS interface folder,
(text) where GMS32TOCMS files are copied, with
an additional .TMP file extension.
CMS Starting Card x = Number (integer) 20000 GMS auto-assigns card numbers, starting
Number=x with the card number specified, when using
the CMS interface to import users without
cards. References exist for this item - quote
TT3380.
Disconnect Beeps=x x = Number (integer) 1 Specifies the number of beeps a
workstation sounds if it becomes offline to
the server.
Note: A value of "0" = no

beeping.
Display Linked Camera x = 0 = No 0 No longer used - applies to Pacom Witness

Video=x x = 1 = Yes DVRs only.
Display Note Number= x = 0 = No 1 Determines if "Note-x:", where x is the
x x = 1 = Yes identification number, is displayed for note
entries in response procedures callout lists.
False Alarm x = 0 = No 0 Not used.
Management=x x = 1 = Yes
GMS Socket Port=x x = Port number (integer) 5003 The port number to use when a socket
connection is selected for workstation
connection.
Lock Timeout=x x = Number (integer) 5000 The SQL lock timer. GMS automatically
closes any SQL lock file if open longer than
the timer. For internal use only.
Logon Type=x x = 0 = Initials 0 The log on user name entry method for
x = 1 = Full name GMS users.
x = 2 = Display name
x = 3 = Windows account
Mixed Card Access=x x = 0 = No 0 No longer used in GMS 3.x and later.
x = 1 = Yes
MOD File Delete Days= x = Number (integer) 3 The number of days GMS keeps card access
x MOD files for before deleting them. MOD
files are generated whenever a card record
is changed. References exist for this item -
quote TT4693.
Multi-Access Level=x x = 0 = No 1 Determines if more than one Global Access
x = 1 = Yes (rule enforced) Group (GAG) can be assigned to cards.
x = 2 = Yes (rule not Otherwise, a single GAG only can be
enforced) assigned to cards. The rule
("SingleTimeZone") means that if a reader
is encountered more than once in the GAGs
being assigned and has different time
schedules (timezones) associated with it,
GMS will show an error message and
prevent the card from being saved.
TT4612, TT4410 and TT6143.
Multi-Site Map for x = 0 = No 0 Determines if users can display Multi-Site
Event Handling=x x = 1 = Yes Map View, when actioning alarms, for points
configured on multi-site maps.
No Message Box for x = 0 = No 0 Determines if GMS displays "Starting as
CPU Switchover=x x = 1 = Yes Active Server. Do you want to switch CPU
Card from Backup to Primary?" messages
whenever a CPU card switchover occurs.


No Message Box for x = 0 = No 0 Determines if GMS displays "Press OK to
GMS Shutdown=x x = 1 = Yes shutdown GMS or Cancel to abort shutdown
process..." messages at shutdown.
NonStopSound=x x = 0 = No 0 Determines if GMS plays audible
x = 1 = Yes notifications of new incoming alarms for a
site, even if the Site Map View is currently
open. References exist for this item - quote
TT4969.
OP Alphanumeric=x x = 0 = Any characters 0 Determines the password requirements for
x = 1 = At least one digit and GMS operators. References exist for this
letter item - quote TT4163.
x = 2 = At least one digit, one
upper-case letter and one
lower-case letter
x = 3 = At least one upper-
case letter and one lower-case
letter
OP Expiry Days=x x = Number (integer) 25 The number of days that a password will be
accepted for before it must be changed.
Applies to passwords only as they are
renewed. References exist for this item -
quote TT4163.
OP Min Length=x x = Number (integer) 1 The minimum acceptable password length.
TT4163.
OP Security Policy=x x = 0 = GMS 1 Determines if GMS or Windows
x = 1 = Windows authentication is used for operators.
TT4163.
OP Authenticating x = Domain name (text) N/A When using Windows authentication for
Domain=x operators, specify the name of the domain
containing the users identities. References
exist for this item - quote TT4163.
PAC1000 Resolver x = Port number (integer) N/A If specified, the GMS servers listen on this
Port=x (UDP) port for PAC1000 messages and
reply with strings describing the message.
TT5837.
Polls=x x = Number (integer) 5 The number of unacknowledged hardware
device polls before GMS marks the device
as being offline.
Reset Points=x x = 0 = No N/A Used with CCTV operation. If set to yes and
x = 1 = Yes a "Restore all latched points" command is
sent, a message is also sent to the matrix
switcher to not display the camera.
Site List Alphabetic x = Y = Yes N Determines if the Summary Manager,
Sort Menu=x x = N = No Options > Site List Alphabetic Sort
Menu option is available. The option allows
operators to list sites alphabetically.
TT5172.
Note: GMS must be restarted

after modifying this value.
Show Acess Level N/A N/A No longer used.

Template=x
Show Server Switch x = 0 = No 1 Determines if a message box is displayed
Message=x x = 1 = Yes on a workstation when it switches to a
different server.
Server_Drive_Mapping a = Main server drive letter X:,Y:,Z: Determines the GMS shared folder drive
s=a:,b:,c: (text) mappings for different GMS servers.
b = Slave server drive letter References exist for this item - quote
(text) TT5167.
c = Remote server drive letter
(text) Note: For standalone systems
(single server), all three drive
letter mappings must still be
specified.
Unique GAG=x x = 0 = No N/A Determines if GMS allows more than one

x = 1 = Yes Global Reader Group (GAG) configuration
under different GAG names. That is, two or
more GAGs with identical contents.


Use Alarm State x = 0 = No 1 Determines if GMS allows different site map
Bitmap=x x = 1 = Yes bitmaps to be used for different point states
(alarm, isolated etc). See GMS help for
details.
UseOldStyleCustom x = 0 = No 0 Determines if the pre-GMS 4.00 method for
ReportsDialog=x x = 1 = Yes creating user-defined (custom) reports is
used.
Zero Priority for x = 0 = No 0 Determines if events generated during
Alarms in Suspend x = 1 = Yes Suspend mode are assigned a priority of 0.
Mode=x If not enabled, event priorities will be as set
for Test mode. References exist for this
item - quote TT4736.
Linked RTUs=x x = 0 = No 0 Determines if Suspend/Unsuspend mode
x = 1 = Yes change operation also affects any linked
Controllers (RTUs). References exist for this
Dual Password Auto x = Number (integer) 5 Determines the time (in minutes) that
Logoff=x operators set for Dual Password operation
(requires a second operator to log on in
order to run commands) will remain logged
on for after the second operator logs off,
before being automatically logged off.
Minimum = 1, maximum = 65534.
TT6001.
Note: The timer operates

independently of any inactivity
timers.
A setting of "0" disables automatic
log off - Dual Password operator
remains logged on. An undefined
value (blank) causes the system
to use the default value ("5").
Settings must be made on a GMS
server.
Display Note Number= x = 0 = No 1 Determines if the "Note" prefix appears to

x x = 1 = Yes operators when displaying the Notes list in
the Selected Instructions dialog box, after
editing existing note entries in the Global
List and Selected Instructions dialog boxes
(after using Edit button), and after creating
new note entries in the Selected
Instructionsdialog box (after using New
button). References exist for this item -
quote TT5563.
Note: If a value is not entered, or

has a numerical value other than
0, the prefix is displayed. If a non-
numerical value is entered, the
prefix is not displayed. The
wording of the prefix is
translatable and is defined in the
FORMAT.MSG file, ID 128.
Max Log File Size=x x = Number (integer) 10 Determines the maximum allowable size (in
MB) for various log files. When the limit is
reached, GMS automatically truncates the
file. References exist for this item - quote
TT5555.
Note: It is recommended to keep

the size below 50MB, for best
performance.
Enable 5 Minute Access x = Y = Yes N Determines if card reader and alarm time
Schedule=x x = N = No schedules can be set in increments of five
minutes ("standard" is 10 minutes).
TT6152.

Note: Applicable to 8000 series

Controllers only. When used, two
time shifts per day can be
specified, not three (as per
"standard").
Custom Vocab Auto x = Y = Yes N Determines if any alarm point vocab entries
Upload=x x = N = No that have been customized in a Controller,
using GMS or a locally connected GMS
Config, are notified to GMS through a
"Custom_Vocab_Changed" message when
the Controller next connects. GMS
TT5950.
SuspendModeIgnore x = Priority number (integer 0 255 Determines any alarm priority numbers
Priority=x to 255) that, if activated during Suspend mode
operation, are sent with their actual
priority, and not using the Suspend mode
priority. References exist for this item -
quote TT6512.
CheckGlobalContact x = YES = Yes YES Determines if GMS performs a complete
Delete=x x = NO = No check for where a global contact is used
before performing global contact delete
operations. System performance may be
increased during global contact delete
operations if this setting is "No".
TT6458.
[SYSTEMQ] Section
Textx=a,b,c x = Column number (integer) N/A Determines Events Manager column view
a = Short description (text) details, where the short description, long
b = Long description (text) description and default column width values
c = Column width (integer) are specified.
Note: The short description is the

displayed column title.
Sequence=x x = Number (integer, comma- 0,1,2,3,4,5,6,7,8 The left-to-right display sequence of

separated) Events Manager columns, using column
number as the identifier.
Dispatch Message to
Old Events=x
[SERVER CONFIG] Section

x=Workstation-y,a|b|c x = Logical workstation Workstation-x,0 Determines the mapping between logical
|d|e number (integer) GMS workstation numbers and actual
y = Workstation number workstations; the contact information for
(integer) workstations; whether or not GMS sends
a = Telephone number 1 events to a workstation for actioning; the
(integer) workstation type (0 = "Administration", 1 =
b = Telephone number 2 "Supervisor", 2 = "Monitoring", 3 =
(integer) "Maintenance", 4 = "Management", 5 =
c = Pager number (integer) "System Setup", 6 = "Card-Access", 7 =
d = Send events? (0 = No, 1 "Visitor-Badging").
= Yes)
e = Workstation type (integer Note: The workstation type
0 to 7) determines the initial screens
displayed in GMS after logging on
and the available features.

[SITE GROUPS] Section

x=y@(a-b) x = Site Group number N/A Determines the identification number,
(integer) name and range of sites for each Site
y = Site Group name (text) Group.
a = First site number (integer)
b = Last site number (integer) Note: The system also accepts
single site numbers in a comma-
separated list. For example, "
1,3,5,222".
[RADIONICS] Section
Dialup Alarm=x x = 0 = No N/A Determines if passed dialup tests are
x = 1 = Yes reported as Contact ID code 602.
[PAGER] Section
Type=x x = Type name (text) ASCOM The pager type used by the GMS pager
interface. Currently, "ASCOM" pager type
only is supported.
[INSTRUCTIONS] Section
0=x x = Option name (text) Classic Style 1 The name of the first response procedure
viewing option.
1=x x = Option name (text) Classic Style 2 The name of the second response
procedure viewing option.
2=x x = Option name (text) Dockable The name of the third response procedure
viewing option.
3=x x = Option name (text) Dockable with The name of the fourth response procedure
Reading Pane viewing option.
Template=x,x,x x = Option number (integer, 0,1,2,3 Determines the display order to GMS
comma-separated) operators of the different response
procedure options.
[PARAMETERS] Section
Soft Path=x x = Folder name (text) N/A The source folder specified the last time
Controller firmware was loaded into GMS.
Site Log Refresh=x x = 0 = No 0 Determines if the site transaction log is
x = 1 = Yes rebuilt each time a site map is opened.
Start Site=x x = Site number (integer) 0 Specifies the first site, by identification
number, that is available to operators
when they log on.
End Site=x x = Site number (integer) 9999 Specifies the last site, by identification
number, that is available to operators
when they log on.
CURMode=x x = Number (integer) 1 Specifies the default number of sites to
display in the Summary Manager.
Increments are in lots of 50. For example,
0 = 50, 1 = 100, 2 = 150 etc.


OHAOffset=x x = Number (integer) 30 Defines a length of time (in minutes)
where, if a site is disarmed within this
length of time before its set open time or is
armed within this length of time after its
set close time, GMS will not generate
"Outside Hours Access", "Late to Open" or
"Late to Close" messages.
OHAEnabled=x x = 0 = No 0 Determines if GMS generates "Outside
x = 1 = Yes Hours Access" messages when a site
enters Day mode and its open/close times
are not set.
[PUBLISHER] Section
EventsInjectingOnOff= x = ON = Enabled OFF Determines if GMS creates and polls an
x x = OFF = Disabled injecting queue for the Events Gateway.
Currently, the behavior is "on" regardless
of this setting. References exist for this
[EVENTS PUBLISHING] Section

PublisherHost=x x = Machine name (text) N/A The name or IP address of the machine
hosting the GMS Events Publisher service.
TT5019.
[VALIDATORS] Section
1=x x = Object name (text) N/A The name of the first validator COM object
used by GMS. References exist for this
2=x ... x = Object name (text) N/A The name of the second validator COM
object used by GMS, and so on.
[NEW CARD] Section

New_Card_Validity=x x = Value (text) BLANK Determines if the Valid To date setting for
newly created access cards defaults to the
current date, or is set to no date (infinite
validity). To set the behavior to apply the
current date, change the value to anything
but "BLANK". References exist for this
[IMPORT CARD] Section

COMObjectID=x x = Object name (text) N/A The name of the COM object used by the
"Import Card" module.

[MAP LAYER] Section

Layer1=x x = Layer name (text) N/A The name of the first site map layer.
Layer2=x ... x = Layer name (text) N/A The name of the second site map layer,
and so on, up to 16 layers.
[IVR] Section
SecurityCode=x x = Code binary (stored as N/A The security code required for logging on to
text) the IVR facility, as it is defined in GMS.
TT5417.
[HOLIDAY ZONES] Section

1=x x = Profile name (text) N/A Determines the name of the first GMS
"Holiday Profile". For example, "
1=Australia". References exist for this
2=x ... x = Profile name (text) N/A Determines the name of the second GMS
"Holiday Profile". For example, "2=New
Zealand", and so on.
[MAPPOINT APPLICATION] Section

Note: More than one region can be specified. The settings must be performed on each GMS workstation that is to use
Microsoft MapPoint.
Europe=x x = YES = Yes NO Determines if Microsoft MapPoint application

x = NO = No (if used) is set for the Europe region.
TT5776.
North America=x x = YES = Yes NO Determines if Microsoft MapPoint application
x = NO = No (if used) is set for the North America
region.
[VIRTUAL MAPS] Section

Note: More than one application can be specified. When several mapping applications are available, operators are provided
with options for which application to view with. The settings must be performed on each GMS workstation that is to use a
mapping application.
GoogleEarthApplication x = YES = Yes NO Determines if GMS uses Google Earth

=x x = NO = No application as a separate entity. That is,
when operators select to view maps using
Google Earth, it opens as a separate
application. References exist for this item -
quote TT5836.
GoogleEarthAPI=x x = YES = Yes NO Determines if GMS uses Google Earth
x = NO = No application within GMS. That is, the
application opens within a GMS window.
TT5836.


BingMapsAPI=x x = YES = Yes NO Determines if GMS uses Microsoft BingMaps
x = NO = No application with GMS. That is, the
application opens within a GMS window.
TT5836.
[TPRAP_IF] Section
1=x x = Alarm panel number N/A Determines the identification number of the
(integer) first Redcare alarm panel (if used).
2=x ... x = Alarm panel number N/A Determines the identification number of the
(integer) second Redcare alarm panel (if used), and
so on.
[dotNET Settings] Section

GMSLanguageId=x x = Number (integer) 0 This setting is internal to GMS and should
not be changed.
[SITE TIME ZONES] Section - No Longer Used

C - GMS Config Application Information

GMS Config is a license-free version of GMS without access control, card management and other database related
GMS features. It is designed for Pacom technicians to perform Controller and hardware configuration on individual
sites. This is carried using direct cable connection between the computer running GMS Config and the target
Controller (site).
Note: GMS Config cannot be installed on a computer that has an existing version of GMS Config installed.
You must uninstall the existing GMS Config before installing the new version.
GMS Config can be installed on a computer that already has a version of GMS installed. However, in this
scenario, you will need to uninstall GMS Config before you can upgrade GMS on that computer.
GMS Config cannot connect to a Base Station or TransIT, only directly to a Controller.
The operation of GMS Config is identical to standard GMS, so there is no additional learning or other procedures to
understand. It is the reduced feature set and limited connectivity only that are different between the two.
In order for GMS to track configuration changes and identify the user responsible, previous versions of GMS Config
would send the GMS Config dongle number as the identifier. In the license-free GMS Config application, the serial
number of the hard drive that GMS Config is installed on is used as the identifier. The identifier is recorded in the
GMS transaction log as part of configuration change records.

Access, applying time schedule to 226

Index Access, overview 202
Access, profile configuring 202
-1- Access, security level setting

Alarm, configuring 172
229
1058 Bank
Alarm, configuring access 175
Predefined Controller configuration 99
Alarm, overview 172, 175
Keypad LED, mapping to 134
-A- Mode change, using cardholder access PIN
Access 204
Alarm area, configuring 175 Assa Abloy
Alarm area, overview 175 Aperio, lock-reader configuring 237
Miscellaneous global settings 233 Asynchronous driver, parameters 47
Access area ATM hours
Overview 202 Setting 175
Profile, configuring 202
Security level, setting 229
Time schedules (time zones), applying 226
-B-
Base Station
Access card
Controller daisy-chain connection 41
Data format, programming 218
Controller RS485 port, configuring 41
Database version, Controller 233
Basic Signal Protocol
PIN validity 233
Message conversion template, assigning 89
Total in Controller 233
Message conversion template, editing 89
Type, configuring 229
Message conversion template, overview 89
Access Control Interface
Battery
Schlage Wyreless, configuring 235
Controller, memory checking 118
Third-party, configuring 234
Baud rate
Access level
Increasing speed 12
Mode changing, using for 233
BMS
Alarm
BACnet actions, configuring 255
Contact sequence 25
BACnet input, configuring 255
Messaging 25
BACnet protocol, configuring 255
Overview 25
Modbus analog inputs, configuring 258
Port priority contact sequence 25
Modbus digital inputs, configuring 258
System flags, setting 163, 167
Modbus digital outputs, configuring 258
Alarm area
Modbus protocol, configuring 258
Access, configuring 175
Overview 254
Access, overview 175
Building Management Systems
Configuring 172
Overview 254
Overview 172
Building Management Systems (BMS)
Alarm panel
BACnet actions, configuring 255
Contact ID (third-party generic), configuring
BACnet input, configuring 255
106
BACnet protocol, configuring 255
Galaxy interface, configuring 107
Macro, programming 261
Hisec interface, configuring 109
Modbus analog inputs, configuring 258
Tecom interface, configuring 110
Modbus digital inputs, configuring 258
Type, configuring 97
Modbus digital outputs, configuring 258
Alarm user
Modbus protocol, configuring 258
Number of, setting 97
Overview 131
Types, configuring 131 -C-
Anti-Passback Calendar
Overview 198 Yearly, setting 175
Aperio Cardholder
Lock-reader, configuration 237 PIN, using for area mode changes 204
Lock-reader, support 237 Commands
Area Intercom, scripts 279
Index | 305
Compliance Power supply, monitoring 115

Predefined Controller configurations, SIA Predefined configuration, overview 99
CP-01, EN50131, UK Bank, 1058 Bank 99 Primary connection, IP 30
Contact ID Primary dialup connection, configuring 31
Alarm panel (third-party generic), configuring RS485 port to Base Station, configuring 41
106 Serial connection to GMS 12
Message conversion template, assigning 89 Serial number, viewing 194
Message conversion template, editing 89 Setup, overview 8
Message conversion template, overview 89 SIA reporting, configuring 39
ContactID SNMP messaging, setting 93
Codes reference 195 Timezone, setting 91
ContactID reporting User-defined commands, overview 119
Controller, configuring 39 CP-01
Controller Predefined Controller configuration 99
Access cards, number in database 233
Active chip, specifying 123
Backup dialup connection, configuring 31
-D-
Dedicated Micros
Chip 1/2, running 123
DS2 Series, installing 160
Commands, sending using IVR 288
Degraded mode
Configuration, applying templates 10
Configuring 231
Configuration, export (HTML) 114
Device
Configuration, saving as template 10
Access control, auto-configuration 141
Configuration, using templates 10
Activation lists 142
Configuring for Transender operation 101
Adding 134
ContactID reporting, configuring 39
Auto-detection 141
Daisy chain connection, configuring 41
Configuration, overview 130
Dialling in to 18
Firmware version, checking 127
Dialog box, accessing 21
Firmware, downloading 127
Dialog box, overview 21
I/O, auto-configuration 141
Dialup connection to GMS 12
Inovonics, configuring 158
Dialup connection, testing 31
Input point, configuring 142
DIP switch, functions 9
Output point, configuring 142
Direct dial connection 18
Output, activating 142
Elevator control, port configuration 243
Removing 134
EMCS, configuring 43
Types table 134
Ethernet connection to GMS 12
Diagnostic port
Firmware version, checking 123
Baud rate, increasing 12
Firmware, deleting 122
Dialog box
Firmware, downloading 123
Advanced Input Configuration 142, 151
Firmware, managing 122
BACnet Configuration 255
Firmware, overview 122
Battery Testing and Power Supply Parameters
GSM modem, configuring 34
115
ID (address), setting 20
BMS General Configuration 254
IP connection, configuring 30
BMS Macro Configuration 261
IP connection, parameters 30
Branch ATM Access Hours 175
Keypad, configuring with 17
Branch Cleaner Hours 175
LED display (1057/8001), meanings 292
Branch Normal Hours 175
License grace period, setting 112
Branch Temporary Hours 175
License grace period, viewing 112
Card Format 218
Memory battery, checking 118
Card Type Config 229
Message filters, setting 93
CCU Parameters 101
Network port, configuring 18
Configuration for Area Profile 202
Overall access settings 233
Configuration for Elevator 244
Password, setting 93
Configuration for Event Driven Activation
Port configuration, overview 25 227
Port configuring, advanced 93 Configuration for Input 142
Power monitoring status, viewing 115 Configuration for Keypad 134
306 | Index
Dialog box OnSafe, confiiguring Controllers for 161

Configuration for Reader 204
Configuration for Reader Timezone 223 -E-
Configuration for User ID 131 Elevator control
Connection Properties 12 Configuration 244
Controller 21 Configuration, overview 242
Controller ID 123 Controller, port configuration 243
Controller License Options 112, 194 Floor accessibiility, setting 248
Controller Template 10 Floor and relay addresss, setting 244
Controller Timezone 91 Reader, configuring 249
Controller User Defined Command 119 Status, viewing 251
Copy Parameters 244 Time schedule (time zone), configuring 244
Copy Properties 255, 258 EMCS
Copy Reader 204 Controller, configuring for 43
Device Configuration 134 EN50131
Dial 18, 92 Predefined Controller configuration 99
EMCS Settings 43 Event
Firmware Commands for Controller 122, 123 Playback, using IVR 288
General Purpose IP Parameters 158 Event driver
General System Parameters 93 Overview 183
Guard Access Hours 175 Programming 183
Inovonics 158 Reader, programming 227
LED Area Mapping for Keypad 134
License Update
Line Card 101
194, 237
-F-
Firmware
Macro Configuration 183
Chip 1/2, Controller 123
Message Filters 93, 101
Commands, Controller 123
Modbus Configuration 258
Controller, checking version 123
Open/Close Schedules 226
Controller, downloading 123
Options for Staff ID 131
Deleting 122
Output Activation for Input 142
Device, checking version 127
Output Configuration 142
Device, downloading 127
Overall Settings 233
Managing, overview 122
Parameters for Area 172
Peer Parameters 101
Port Protocol Parameters 25 -G-
Pulse Counter Configuration 262 Galaxy
Service Access Hours 175 Alarm panel, configuring 107
Set Remote Alarm Panel Type 97 GMS
SNMP Parameters 93 Listen-in operation, setting up for 269
Speed Dial 18 Listen-in operation, using 270
System Flags 167 GMS Config
System General Parameters 163 Application information 304
System Passwords 93 Overview 304
Temporary Schedule 175 Group
Time/Event Driven Activation 183 Input point, conditions 151
TransIT Options Menu 101 Input point, creating 151
User Defined Commands 119 GSM
Yearly Calendar 175, 223 Modem configuration, Controller 34
Dialup connection Guard hours
Backup, configuring 31 Setting 175
Primary, configuring 31
Testing 31 -H-
DIP switch Hardware
Controller, functions 9 Adding 134
DVR Configuration, uploading 134
Dedicated Micros DS2 Series, installing 160 Configuration, viewing 134
Index | 307
Hardware Grace period, Controller 112

Removing 134 Listen-in Device
Serial number, viewing 194 Controller, using PAP 268
Hisec Wiring, multiple 268
ThorGuard alarm panel, interface configuring Listen-In operation
109 Deployment 266
HLI GMS, setting up for 269
Port configuration 243 GMS, using 270
Holiday type Overview 266
Assigning to dates 223 Requirements 266
LLI
-I- Port configuration 243
Inovonics Lock
Configuring 158 S&G IP Series, configuring 239
EchoStream 158 Lock-reader
Frequency Agile (FA) 158 Aperio, configuring 237
Input point
Configuring 142 -M-
Groups, creating 151 Macro
Vocab, configuring 153 Building management systems (BMS),
Interactive voice response (IVR) 288 programming 261
Intercom Overview 183
External, operation overview 274 Programming 183
External, setting up 274 Reader, programming 227
Internal, operation overview 273 Mode
Internal, setting up 273 Degraded reader, configuring 231
Overview, technicians 272 Degraded reader, overview 198
Script, commands 279 Suspend, switching to 288
Scripting, associating intercom events with Time limiting 288
275 Mode change
Scripting, overview 275 Keypad, configuring for 155
Interlock Modem
Overview 198 GSM, configuring 34
IP connection
Controller, configuring
Controller, parameters
30
30
-N-
Normal hours
IVR
Setting 175
Logging on to 288
Overview 288
Playing back recorded events 288
-O-
OnSafe
Sending Controller commands 288
DVR, configuring Controllers for 161
Output point
-K- Configuring 142
Keypad
Vocab, configuring 153
Access security, setting from GMS 233
Adding 134
Controller, configuring 17
-P-
Pacom .is
LED, mapping area to 134
EMCS support, GMS 43
Mode change, configuring for 155
Point vocabs
PIN access, overview 198
Downloading to Controller 153
Reader, configuring 204
Input/Output, configuring 153
Removing 134
Overvew 153
Port
-L- Dual communications, overview 25
License
Parameters, accessing 25
Feature, enabling/disabling 194
Power monitoring
308 | Index
Power monitoring Elevator, configuring 249

Alarm, messages 115 Event driver, programming 227
Controller, configuring 115 Flag options 204
Controller, viewing 115 I/O parameters 204
Protocol In/Out, overview 198
Aperio, parameters 47 Interlock, overview 198
ASCII, parameters 47 Interlocking 204
Asynch Poll, parameters 47 LED control 204
Basic Signal Protocol, message conversion Macro, programming 227
templates 89 Mode setting 204
BMS, parameters 47 Stand-alone, overview 198
Contact ID, message conversion templates Time schedule (Time zone), configuring 223
89 Types and functionality 204
Controller Dialup, parameters 47 Remote Maintenance
Elevator Interface, parameters 47 8303. using for 115
EPCP, parameters 47 Report
General Carrier Message, parameters 47 Controller configuration 114
General PTZ/Switcher, parameters 47 Rijndael
General Purpose Driver, parameters 47 Algorithm, checking version 123
General Purpose DVR Driver, parameters 47
Generic Fire Alarm (Securitas), parameters
47
-S-
HDLC/SDLC, parameters 47 S&G IP Series lock
IEC, parameters 47 Configuring 239
Inovonics, parameters 47 Schlage
Iris, parameters 47 Wyreless alarm panel, configuring 235
IRISYS, parameters 47 Script
Logging Printer, parameters 47 Intercom, associating events with 275
Modbus, parameters 47 Intercom, commands 279
Modem, message conversion templates 89 Service hours
PCP, parameters 47 Setting 175
RS485 Device Loop, parameters 47 SIA
Securitel (STU) Receiver, parameters 47 Codes reference 195
SFEP, parameters 47 SIA reporting
Slave RS485 Device Loop, parameters 47 Controller, configuring 39
SNA, parameters 47 SNMP
Text Pager, parameters 47 Messaging, Controller setting 93
UDP/IP on 1051/1052, parameters 47 Staff type ID
UDP/IP on Ethernet, parameters 47 Management options 131
UDP/IP on PPP, parameters 47 Suspend mode
VCS/Dialup, parameters 47 Switiching to (IVR) 288
Wyreless Access, parameters 47 Time limiting (IVR) 288
X.25, parameters 47
PSTN dialup connection -T-
Controller, configuring 31 TAPI
Controller, parameters 31 Device, configuring 92
Pulse counter Device, selecting 18
Dual, configuring 262 Tecom
Challenger V8 alarm panel, configuring 110
-R- Telephony
Reader Configuring 92
Alarm Areas 204 Template
Anti-Passback, overview 198 Basic Signal Protocol, message conversion
89
Configuring 204
Contact ID, message conversion 89
Degraded mode, configuring 231
Modem, message conversion 89
Degraded mode, overview 198
Template, Controller
Device address, setting 204
Index | 309
Template, Controller
Applying 10
Saving 10
Using 10
Temporary hours
Setting 175
Temporary schedule
setting 175
Third-party Alarm panel, capabilities summary
Aritech 106
BT 106
Concept 106
ContactID 106
Diebold 106
DSC 106
Europlex 106
Galaxy 106
Hisec 106
Tecom 106
Time and attendance reporting
Overview 204
Time schedule (time zone)
Applying to access area 226
Overview 198
Timezone
Adding/editing, Controller 91
Transender
Operation, Controller configuring 101
-U-
UK Bank
Predefined Controller configuration 99
-V-
Vault controller
Adding 134
Viewing status 134
Vocab
Editing, pre-defined 153
Vocabs
Downloading to Controller 153
Input/Output, configuring 153
Overvew 153
Voice line
Configuring 92
-Y-
Yearly calendar
Holiday type, assigning to dates 223
Setting 175
310 | Index

Configuring Controllers GMS 4.07 - Technician Guide v1.0

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Configuring Controllers GMS 4.07 - Technician Guide v1.0

Uploaded by

Copyright:

Available Formats

GMS 4.

800 010 014 Version 1.0 6/12/2010 © 2010 Pacom Systems

Software License Notice

Programming Card Data Formats

Controllers and Remote Terminal Units

Manager by clicking on the GMS toolbar.

North American Compliance Note

8 | Chapter 1 - Setting Up Controllers

Setting DIP Switch Functions

DIP Switch Functions

Read parameters from the External EEPROM Module (EEM).

Note: 8001 Controllers operate as per 105x Controller firmware 5.02.

Clear access control parameters only.

Self-test Controller on power up.

Chapter 1 - Setting Up Controllers | 9

Backing Up Controller Configurations and Using

Compatible Settings Incompatible Settings (require re-configuration)

Saving Controller Configurations

Applying Saved Controller Configurations

10 | Chapter 1 - Setting Up Controllers

Chapter 1 - Setting Up Controllers | 11

Creating a Serial Connection to the Controller

Using a Diagnostic Cable

1057/1058 Controller Diagnostic Cable Pin Connections

Diagnostic Port (RJ12) Pin PC DB9 Pin

8001 Controller Diagnostic Cable Pin Connections

Using a GMS COM Port

12 | Chapter 1 - Setting Up Controllers

5. Click OK to close the Connection Properties - Port 1 dialog box.

Increasing the Diagnostic Port Connection Speed (Baud Rate)

Chapter 1 - Setting Up Controllers | 13

Creating an Ethernet Connection to the Controller

14 | Chapter 1 - Setting Up Controllers

Note: The default password for a TransIT is "Pacom001" (case-sensitive).

Creating a Dialup Connection to the Controller

Chapter 1 - Setting Up Controllers | 15

Note: The default password for a TransIT is "Pacom001" (case-sensitive).

16 | Chapter 1 - Setting Up Controllers

Using a Keypad for Basic Configuration

Configuring a Controller Directly Using a Keypad

2. Connect a 12V power supply and power up the Controller.

Chapter 1 - Setting Up Controllers | 17

Configuring the Controller Network Port

Configuring GMS for Direct Dial In and Connection

18 | Chapter 1 - Setting Up Controllers

Chapter 1 - Setting Up Controllers | 19

To assign an ID (address) to a Controller, proceed as follows:

4. Click OK to complete the process and close the dialog box.

20 | Chapter 1 - Setting Up Controllers

Using the Controller Dialog Box

Chapter 1 - Setting Up Controllers | 21

Layout of the Controller Dialog Box

22 | Chapter 1 - Setting Up Controllers

Accessing Configuration Settings for Non-Pacom Alarm Panels/

Chapter 1 - Setting Up Controllers | 23

24 | Chapter 1 - Setting Up Controllers

Configuring Controller Ports for Alarm Messaging

Note: Only Modem (dialup) ports support Contact ID or SIA reporting.

No Priority - The port is not be used for alarm reporting.

General Contact Sequence

Chapter 1 - Setting Up Controllers | 25

Port Priority Contact Sequence

26 | Chapter 1 - Setting Up Controllers

Port Configuration Overview