Door controllers, readers, credentials, and enterprise access management platforms.
| Model | Type | Key Features |
|---|---|---|
| R29 | Outdoor video door station | 7" Android, facial recognition, RFID, PoE, IP65, IK06 |
| E16 | Indoor monitor | 5" IPS touch, SIP, H.264, PoE, Wiegand, RS485 |
| Access Type | Default | Notes |
|---|---|---|
| Web Interface Admin | admin / admin | Change immediately on first login |
| Device Screen (Project) | 9999 + Dial + 3888 | Access via dial screen on device |
| Gesture Access | Tap time bar 10 times | Opens settings without project password — disable if not required |
| Mode | Description |
|---|---|
| Discovery Mode | Plug and play — device auto-configures on network connection. Suitable for simple single-site deployments. |
| Cloud Mode | Akuvox Cloud — remote management, audio/video, and access control via smartphone. Multi-site capable. |
| SDMC Mode | SIP Device Management Controller — on-premise software for building management. Full topology, intercom, monitoring, and alarm integration. |
| Fault / Symptom | Cause & Action |
|---|---|
| Account Unavailable / SIP Registration Failure | SIP credentials incorrect or SIP server unreachable. Check SIP account settings in web interface. Verify SIP server IP/domain and port. |
| No Ringback on Call | Called device SIP registration failed, or DND enabled on E16. Check E16 SIP registration status. |
| Call Rejected — DND Enabled | Do Not Disturb is active on the called device. Disable DND in E16 settings. |
| Direct IP Call Failure | "Direct IP is Not Enabled" message. Enable direct IP calling in Account > Advanced. |
| No Video on E16 | H.264 codec mismatch or network bandwidth issue. Check codec settings on both devices. |
| Door Not Releasing | Relay output not configured, or relay wiring fault. Check Intercom > Relay settings and wiring to door strike/lock. |
| RFID Card Not Recognised | Card type not supported or card not enrolled. Check card frequency (13.56 MHz or 125 kHz) and enrol card in access control settings. |
| Facial Recognition Failure | Poor lighting at door, face not enrolled, or camera dirty. Improve lighting, re-enrol face profile, clean camera lens. |
| Device Not Found on Network | PoE switch not providing power, or DHCP not assigning IP. Use Akuvox IP Scanner. Check PoE switch port and network cable. |
| Abnormal Temperature Alert | Body temperature detection (if enabled) triggered. Temperature below 34°C or above threshold. Check temperature detection settings. |
| Connection | Cable / Spec | Notes |
|---|---|---|
| Network / PoE | Cat.5e or Cat.6 | Max 100 m to PoE switch. PoE IEEE 802.3af (15.4 W max) |
| 12 V DC Power | 2-core, min 0.5 mm² | 12 V DC, 1.5 A if not using PoE. Use UPS (min 600 VA) recommended |
| Door Strike / Lock | 2-core to relay terminals | Relay: 3A 30VDC / 0.5A 125VAC. Home-run all door strike wiring to relay |
| Exit Button | 20 AWG (0.5 mm²) 2-core | Connect to input interface on R29. Triggers door release when activated |
| Wiegand Output | Shielded cable, max 150 m | D0 (green), D1 (white), GND (black). Connects to third-party access panel |
| RS485 | Twisted pair, shielded | For third-party device integration (elevator control, etc.) |
| Connection | Cable / Spec | Notes |
|---|---|---|
| Network / PoE | Cat.5e or Cat.6 | PoE IEEE 802.3af. Max 100 m to switch |
| Wiegand | Shielded cable | For integration with third-party access panels |
| RS485 | Twisted pair | For ancillary device integration |
| Product | Type | Notes |
|---|---|---|
| Command Centre | Full enterprise platform | Unlimited users/doors |
| Cardax | Legacy Gallagher platform | Replaced by Command Centre |
| T Series | Terminals and readers | Multi-technology readers |
| FT Series | Fence detection | Perimeter intrusion detection |
| Feature | Description | Use Case |
|---|---|---|
| Two-Person Rule | Two cardholders required to access area | High-security vaults, server rooms |
| Anti-Passback | Prevents re-entry without exit | Turnstiles, airlocks |
| Interlock | Only one door can be open at a time | Airlock / mantrap |
| Alarm Zone Integration | Access events trigger alarm zones | Perimeter detection integration |
| Code / Display | Description | Likely Cause | Action |
|---|---|---|---|
| Controller Offline | Controller not communicating | Network fault, power loss | Check network and power. |
| Card Not Found | Card not recognised | Card not enrolled | Re-enrol card. |
| Access Denied | Card read but access denied | Access group, schedule | Check access group and schedule. |
| Server Fault | Command Centre server not responding | Service stopped | Restart Command Centre service. |
| Licence Fault | Licence expired or invalid | Licence renewal required | Contact Gallagher for licence renewal. |
| Terminal | Function | Notes |
|---|---|---|
| +12V | Power supply | 12V DC from PSU |
| 0V | Common ground | Must be continuous |
| D0 | Wiegand Data 0 | Green wire |
| D1 | Wiegand Data 1 | White wire |
| LOCK+ | Electric lock positive | Fused at 1A |
| LOCK− | Electric lock negative | Via relay output |
| REX | Request to exit | Normally open push button |
| DOOR | Door contact | Normally closed magnetic contact |
=== WEB RESEARCH: gallagher ===
# Gallagher Command Centre Technical Reference
## Manufacturer
Gallagher Security
## Discipline
access
## Product Range and Model Numbers
* **Gallagher Controller 6000 (C6000)**
* C300100: Gallagher Controller 6000
* C300111: Gallagher Controller 6000, 2 Door Variant
* C305101: Gallagher High Sec Controller 6000
* C300101: Gallagher Controller 6000 Enhanced
* C305111: Gallagher High Sec Controller 6000, 2 Door
* **HBUS Modules**
* C300142: Gallagher 4H Module
* C300182: Gallagher 8H Module
* C300660: HBUS 8 In 2 Out Door Module
* **Cabinets**
* C200100: Gallagher Single Cabinet
* C200104: Gallagher Dual Cabinet (Cool Grey)
* C200103: Gallagher Dual Cabinet (Charcoal)
## Technical Specifications
### Controller 6000
* **Doors supported:** 10 (Standard, Enhanced, High Sec), 2 (Two Door, High Sec 2 Door)
* **Ethernet 10/100 port:** 1 (Standard, Two Door, High Sec, High Sec 2 Door)
* **Ethernet 10/100/1000 port:** 2 (Enhanced)
* **Power Voltage:** 13.6 V DC ±15%
* **Idle current @ 13.6Vdc (No Relays / 4 Relays / 8 Relays):**
* C6000: 175mA / 320mA / 460mA
* C6000 Enhanced & High Sec: 610mA / 730mA / 870mA
* **Operating temperature:** -10°C to +70°C (C6000), -10°C to +55°C (HS C6000)
* **Humidity:** 95% Non-condensing
* **Dimensions (H x W x D):** 100 x 180 x 42mm (3.9 x 7.1 x 1.7in)
* **Maximum speed:**
* HBUS: 1Mbit/s, 500m (1640ft)
* GBUS: 38.4Kbit/s, 1200m (3937ft)
* OSDP: 115.2Kbit/s, dependent on cable type
* SensorBUS: 115.2Kbit/s, dependent on cable type
* Aperio: 19.2Kbit/s, 1000m max.
* **Number of ports:** 1 x USB 2.0 port, 1 x RS232 port
* **Standards compliance:** CE, RCM, FCC, UL, FIPS 201-2 GSA APL, AS/NZS 2201 – Class 5
### HBUS Modules (4H and 8H)
* **Inputs:** 8H Module: 24, 4H Module: 12
* **Outputs:** 8H Module: 8 SPDT relays, 4H Module: 4 SPDT relays
* **Power Voltage:** 13.6 V DC ±15%
* **Current (Via Gallagher Controller connector):** 40mA
* **Current (Via HBUS Module power in - No relays / 4 relays / 8 relays):** 30mA / 175mA / 315mA
* **Operating temperature:** -10 to +70 °C
* **Humidity:** 95% Non-condensing
* **Standards Compliance:** FCC, CE, RCM, RoHS
## Default Codes
* **Gallagher Command Centre Initial Login:** Username: `system`, Password: (none) - forces user to set a password upon first login.
## Fault/Event/Alarm Code Tables
| Description | Type | Compass AlarmType |
| :--- | :--- | :--- |
| System Offline | 1 | ALARMSENSOR_GENERIC |
| System Online | 2 | ALARMSENSOR_CONNECTION_RESTORED |
| Access denied | 3 | ACCESSPOINT_NO_ACCESS |
| Tamper | 1 | ALARMSENSOR_GENERIC |
| Controller tampered (front) | 3000 | ALARMSENSOR_GENERIC |
| Controller tampered (rear) | 3066 | ALARMSENSOR_GENERIC |
| Controller Upgrade | 5029 | ALARMSENSOR_GENERIC |
| Cabinet tampered | 5064 | ALARMSENSOR_GENERIC |
| Input Tampered | 22002 | ALARMSENSOR_GENERIC |
| Input Break | 22003 | ALARMSENSOR_GENERIC |
| Input Short | 22004 | ALARMSENSOR_GENERIC |
| Unit Tampered | 23030 | ALARMSENSOR_GENERIC |
| Unit Tampered (Front) | 23070 | ALARMSENSOR_GENERIC |
| Unit Tampered (Rear) | 23071 | ALARMSENSOR_GENERIC |
| Unit on Door Tampered | 23211 | ALARMSENSOR_GENERIC |
| Salto Door Tampered | 25003 | ALARMSENSOR_GENERIC |
| Engage Bluetooth Tamper | 42615 | ALARMSENSOR_GENERIC |
| Engage Lock Cover Tamper | 42616 | ALARMSENSOR_GENERIC |
| Engage Magnetic Tamper | 42617 | ALARMSENSOR_GENERIC |
| Engage Reader Tamper | 42626 | ALARMSENSOR_GENERIC |
| Tamper Return To Normal | 2 | ALARMSENSOR_GENERIC |
| Controller no longer tampered | 3065 | ALARMSENSOR_GENERIC |
| Controller no longer tampered (rear) | 5002 | ALARMSENSOR_GENERIC |
| Controller no longer tampered (front) | 5003 | ALARMSENSOR_GENERIC |
| Controller Upgrade | 5030 | ALARMSENSOR_GENERIC |
| Cabinet no longer tampered | 5065 | ALARMSENSOR_GENERIC |
| Unit - no longer tampered | 23069 | ALARMSENSOR_GENERIC |
| Unit no longer tampered (front) | 23104 | ALARMSENSOR_GENERIC |
| Unit no longer tampered (rear) | 23105 | ALARMSENSOR_GENERIC |
| Salto Door No Longer Tampered | 25011 | ALARMSENSOR_GENERIC |
| Unit Stopped Responding | 3 | ALARMSENSOR_GENERIC |
| Alarm transmitter receiver(s) offline | 3230 | ALARMSENSOR_GENERIC |
| Plug-in Module not responding | 5001 | ALARMSENSOR_GENERIC |
| Diagnostics Service Observability Platform Stopped Responding | 7043 | ALARMSENSOR_GENERIC |
| Unit Not Responding | 23038 | ALARMSENSOR_GENERIC |
| Sensor(s) Offline | 23111 | ALARMSENSOR_GENERIC |
| Card reading module offline | 23212 | ALARMSENSOR_GENERIC |
| Safety Micro Offline | 40145 | ALARMSENSOR_GENERIC |
| Lock Offline | 41400 | ALARMSENSOR_GENERIC |
| Elevator Service Offline | 42401 | ALARMSENSOR_GENERIC |
| ThyssenKrupp Elevator Offline | 42404 | ALARMSENSOR_GENERIC |
| ThyssenKrupp Elevator Group Offline | 42406 | ALARMSENSOR_GENERIC |
| Elevator Web Service Offline | 42408 | ALARMSENSOR_GENERIC |
| ThyssenKrupp Kiosk Offline | 42411 | ALARMSENSOR_GENERIC |
| ThyssenKrupp Elevator Rear Panel Offline | 42420 | ALARMSENSOR_GENERIC |
| Engage Gateway Offline | 42621 | ALARMSENSOR_GENERIC |
| Engage Door Offline | 42630 | ALARMSENSOR_GENERIC |
| SIP Service Stopped Responding | 42902 | ALARMSENSOR_GENERIC |
| Diagnostics Service Stopped Responding | 43102 | ALARMSENSOR_GENERIC |
| Closed/On | 4 | ALARMSENSOR_GENERIC |
| Logic Block On | 3302 | ALARMSENSOR_GENERIC |
| Input Closed | 22000 | ALARMSENSOR_GENERIC |
| Output On | 24001 | ALARMSENSOR_GENERIC |
| Open/Off | 5 | ALARMSENSOR_GENERIC |
| Logic Block Off | 3303 | ALARMSENSOR_GENERIC |
| Input Open | 22001 | ALARMSENSOR_GENERIC |
| Output Off | 24000 | ALARMSENSOR_GENERIC |
| Card Error | 6 | ALARMSENSOR_GENERIC |
| Foreign Card | 20016 | ALARMSENSOR_GENERIC |
| Illicit Card | 20017 | ALARMSENSOR_GENERIC |
| Illicit GovPass Card | 20020 | ALARMSENSOR_GENERIC |
| Terminal: Foreign Card | 20066 | ALARMSENSOR_GENERIC |
| Terminal: Illicit Card | 20067 | ALARMSENSOR_GENERIC |
| Non MIFARE Enhanced Security Card | 20102 | ALARMSENSOR_GENERIC |
| Non High-Security Card Type | 20116 | ALARMSENSOR_GENERIC |
| Non Proximity Check Card | 20117 | ALARMSENSOR_GENERIC |
| Potential Duplicate Card | 20118 | ALARMSENSOR_GENERIC |
| PIV Controller Incompatibility | 20119 | ALARMSENSOR_GENERIC |
| Foreign Card - Locker | 42114 | ALARMSENSOR_GENERIC |
| Illicit Card - Locker | 42115 | ALARMSENSOR_GENERIC |
| Shunted/Isolated | 7 | ALARMSENSOR_GENERIC |
| Input Shunted | 22005 | ALARMSENSOR_GENERIC |
| Input Isolated | 22012 | ALARMSENSOR_GENERIC |
| Sensor Group Shunted | 41121 | ALARMSENSOR_GENERIC |
| Controller Bus Shunted | 41140 | ALARMSENSOR_GENERIC |
| Device Shunted | 41142 | ALARMSENSOR_GENERIC |
| Controller Bus Automatically Shunted | 41144 | ALARMSENSOR_GENERIC |
| Maintenance Warning | 8 | ALARMSENSOR_GENERIC |
| Controller Incompatible configuration | 309 | ALARMSENSOR_GENERIC |
| Controller Unknown version | 310 | ALARMSENSOR_GENERIC |
| Controller Multiple Server Connections | 314 | ALARMSENSOR_GENERIC |
| SQL Server Database Space Shortage Warning | 401 | ALARMSENSOR_GENERIC |
| SQL Server Database Space Shortage Notification | 402 | ALARMSENSOR_GENERIC |
| Local Drive Low Disk Space Warning | 411 | ALARMSENSOR_GENERIC |
| Local Drive Low Disk Space Notification | 412 | ALARMSENSOR_GENERIC |
| Database Logon Failure | 413 | ALARMSENSOR_GENERIC |
| License Warning - Devices required to maintain your license validity are not responding | 510 | ALARMSENSOR_GENERIC |
| Download warning. | 515 | ALARMSENSOR_GENERIC |
| License Warning - License has expired | 530 | ALARMSENSOR_GENERIC |
| License Warning - License is not valid for this version of Command Centre | 531 | ALARMSENSOR_GENERIC |
| License Warning - License limits have been exceeded | 532 | ALARMSENSOR_GENERIC |
| Duplicate finger biometrics | 554 | ALARMSENSOR_GENERIC |
| Ident Dongle License Limit Exceeded | 555 | ALARMSENSOR_GENERIC |
| Database Maintenance Failed | 561 | ALARMSENSOR_GENERIC |
| Duplicate wave biometrics | 562 | ALARMSENSOR_GENERIC |
| Controller IP Address Incorrect. | 704 | ALARMSENSOR_GENERIC |
## Zone Types and Descriptions
**Regulated Zones (Feature 8.60)**
This feature introduces a new 'Regulated Zone' Command Centre item for monitoring Cardholders. The Regulated Zone is separate from Access Zones (but potentially encompasses one or multiple Access Zones), and is used to define the on-site area that is monitored by pre-configured time limits.
The 'Regulated Zones' feature monitors Cardholders using the following parameters (rules):
1. **Cumulative duration:** Used to monitor Cardholders' accumulated time-on-site across multiple shifts. An event is raised when a Cardholder has been inside the Regulated Zone for a period greater than the configured cumulative shift duration, within a specified period of time.
2. **Break duration:** Used to monitor Cardholders' minimum break periods between shifts. An event is raised when a Cardholder re-enters the Regulated Zone within the minimum break period. A temporary exit grace period can be configured to define a period of time a Cardholder is allowed off-site before they are considered to be between shifts.
3. **Maximum duration:** Used to monitor Cardholders' time-on-site within a single shift (period of time). An event is raised when a Cardholder has been inside the Regulated Zone for a period of time greater than the configured shift length.
4. **Predictive cumulative duration:** Used to monitor Cardholder accumulated time-on-site across multiple shifts and predict if a Cardholder will exceed the cumulative limit (total time limit across shifts). When a Cardholder enters the Zone, a rule is checked: will the Cardholder end up at or above the cumulative limit if they stayed in the Regulated Zone for the Expected shift duration. If yes, a predictive alarm is raised.
5. **Shift management:** Used to monitor Cardholders' shift patterns and optionally enforce Cardholders' compliance with shift patterns. An alarm is raised when a Cardholder enters the Regulated Zone before the first day of their shift. An alarm is also raised when a Cardholder does not exit site when their shift ends. Grace periods can be configured to allow Cardholders to enter site one, two or three days before their shift starts, and leave one, two or three days after their shift ends.
## Wiring Diagrams and Terminal Descriptions
### Wiegand Connection Diagram - Controller 6000 with HBUS 4-in-2 Out Door Module
**Controller 6000 Connections:**
* **New Device (Reader):**
* Wiegand D0 (Green)
* Wiegand D1 (White)
* TTL In (Yellow)
* TTL In (Red)
* Wiegand Ground (Black)
* **HBUS 4-in-2 Out Door Module (Wiegand to Controller):**
* Data 0 (Green)
* Data 1 (White)
* BT Out 1 (Yellow)
* BT Out 2 (Red)
* GND (Black)
* COM A
* COM B
* GND
* +V
### Controller 6000 Connections (from ACCESS CONTROL SYSTEM CONTROLLER-6000 / EASY-SOFT 6000 manual)
**Connection of an Interface RF/WG / Connect / Cityprox-C4+ / Steelprox-C4+ to the CONTROLLER-6000**
* **Number of wires:** 3
* **For distances until 10 metres:** 3 wires of 0.5mm² AWG20
* **For distances until 100 metres:** Cable 3x0.5mm² shielded
* **Shielding:** Obligatory from 10m
* **Maximum distance:** 100m
* **Terminal of connection to the controller:** + - S
**Connection of a Wiegand system to the CONTROLLER-6000 (Evoprox, etc...)**
* **Number of wires:** 5
* **For distances until 10 metres:** 5 wires of 0.5mm² AWG20
* **For distances until 100 metres:** Cable 5x0.5mm² shielded
* **Shielding:** Obligatory from 10m
* **Maximum distance:** 100m
* **Terminal of connection:** Individual terminals for each door
* **CONTROLLER-6000 terminal:** + 12Vdc, 0V, Clock, Data, Led
**Connection of the CONTROLLER-6000 to the bus RS485**
* **Number of wires:** 3
* **Shielding:** Obligatory
* **Maximum distance:** 1200m
* **Use wires:** FTP5 or superior.
**Connection of a pushbutton of a door to the CONTROLLER-6000**
* **Number of wires:** 2 de 0,5mm² AWG20
* **Shielding:** Recommended
* **Maximum distance:** 100m
* **Terminal of connection:** Individual terminals for each door
**Connection of an electrolock to the CONTROLLER-6000**
* **Electrolock 500mA max.:** Until 50m: 0,5mm² AWG20, Until 100m: 1,5mm² AWG16
* **Electrolock 190mA max.:** Until 50m: 1,5mm² AWG16, Until 100m: 1mm² AWG18
* **Electromagnet 0,5Amp/12Vcc:** Until 50m: 1mm² AWG18, Until 100m: 1,5mm² AWG16
## Programming Menu Structure and Commissioning Steps
### Gallagher Access Engineer Course - C892320 (Advanced Functionality and Configuration)
**Healthcare Scenario:**
* **System Divisions:** Operators and Divisions, Inheritance of Division Privileges, Setting up System Divisions.
* **Operator Groups and Divisions**
* **Macros:** Securing an Access Zone via (Lockdown), Setting up the T20 Mimic Panel, Setting the LED flash sequence.
* **Action Plans**
* **Alarm Instructions:** Creating a New Alarm Instruction.
* **Insertion Tags:** Creating an Insertion Tag, Assigning Alarm Instructions, Viewing Alarm Instructions in Command Centre.
* **Guard Tours for Gallagher Command Centre:** Configuring a Guard Tour, Guard Tours & the Event Response Tab, Guard Tours & the Status and Overrides Tab, Running a Guard Tour, Restarting a Guard Tour (if halted).
* **Site Plans:** Setting up Site Plans, Layering Site Plans, Adding Items to Site Plans, Using Graphics to Replace Icons, Adding a Macro to a Site Plan, Creating a New Icon Set.
**Mining Scenario:**
* **Identity Analytics:** Configuring Competencies, Access Zone Competencies, Assigning Competencies, Configuring Cardholders, Adding a Competency to a Cardholder.
* **Anti-passback:** Configuring Anti-passback, Anti-passback Forgive after Time, Anti-passback Forgive all Cardholders, Anti-passback Forgive a specific Cardholder.
* **Event Notification Filters:** Email and Mobile PDFs, Enabling your Event Notifications, Creating a Notification Schedule, Assigning a Notification Schedule, Setting up the Email and SMS Server.
* **Zone Counting:** Configuring Zone Counting Events.
**Education Scenario:**
* **Access Group Lineage:** Master Access Group, Assigning Lineage.
* **First Card Unlock**
* **Personalised Actions:** Controlling Lockers, Configuring Locker Personalised Actions, Testing the Locker Scenario, Access Granted vs Access Taken Options, Using Macros in Personalised Actions.
**Enterprise Data Interface:**
* **Operator Privileges:** The Run as Operator, Creating the Run as Operator.
* **The Source File**
* **Enterprise Data Interface Folders:** Create Local File Locations on the Server.
* **Importing Images with EDI**
* **Configuring Command Centre to Receive the Source Data:** Create/Configure Personal Data Fields.
* **Creating an EDI Interface:** Setting the Mapping of Data between the Source File and Command Centre Data.
* **Creating a Transformation Mapping:** Adding a Card Transformation, Adding Access Group Transformations.
* **Running EDI Manually:** Error Messages and Log Files.
**Data Centre Scenario:**
* **Low Level Elevator Cars:** Creating the Elevator Controls, Access Zone Modes, Virtual Outputs, Inputs, Elevator Car, Configuring Elevator Floors, Advanced, Configure Access Group, Card Pin Codes, Reporting.
* **Interlocking Doors:** Adding a New Interlock Group.
* **Challenge:** Setting up Challenge, Setting up the Access Group.
* **Logic Blocks:** Logic Block Rules, Introducing Logic Block Configurations, Controlling an Alarm Zone, Assigning Alarm Zone Privileges, How the Logic Works.
* **Contact ID:** Setting up the GG for the Server Room Alarm, Intruder Alarm Example, Panic Alarm Example, General Information.
### Programming and Commissioning from ACCESS CONTROL SYSTEM CONTROLLER-6000 / EASY-SOFT 6000 manual
**1.5 Modes of Use**
The Controller-6000 can operate in two modes:
* **Autonomous mode (with PALM):** The controller operates independently, typically with an IRDA connection module and the PICADOR handling program for PALM devices. This mode is limited to a single controller and does not support parallel connections. Switches 7 and 8 must be in the ON position for this mode.
* **Centralised mode (with PC):** This mode allows multiple controllers to be connected in parallel and managed through the EASY-SOFT 6000 program. Each controller needs to be codified with its network position using DIP-switches. For remote control, a CONTROLLER-6000 modem is connected between the RS485 interface and the controller, along with a telephone line.
**2 Installation Manual for the EASY-SOFT 6000**
**2.1 Minimum Requirements for System / Rapid Installation**
To install the EASY-SOFT 6000 program, which controls the CONTROLLER-6000 units:
1. **Connect the RS485 converter:** Connect the RS485 converter to the PC and the central unit.
2. **Install the program:** Insert the EASY-SOFT 6000 CD-Rom and run `setup.exe`. Follow on-screen instructions.
3. **Install webcam drivers:** If applicable, explore the EASY-SOFT 6000 CD, open the Webcam file, run `setup.exe`, and follow on-screen instructions.
4. **Install 'dongle' (protection key):** The dongle supplied with the program must be installed in one of the central units in the network.
**Minimum System Requirements:**
* **Operating System:** Windows 98, Me, 2000, NT (Service pack 6), XP Pro, XP Home (if webcam is not used).
* **Processor:** Pentium II 233 MHz.
**3 Manual for Use of the EASY-SOFT 6000 Programme**
* **3.1. Starting a Session**
* **3.2 Control of Accesses:** Groups of Users, Time Bands, Series of Keys or Transmitters, Public Holidays, Configuration of Events
* **3.3 Analysis Tools**
* **3.4 Processing Events**
* **3.5 Search a Key or Transmitter:** Handling Keys and Transmitters, Personalization of a Key or Transmitter
* **3.6 Updating a Remote Control**
## Expander/Peripheral Devices
### Gallagher HBUS Modules (4H and 8H)
Gallagher 8H and 4H modules are expander devices that support star wiring of secure high-speed HBUS devices, including T-Series Readers and F-Series fence controllers. They also provide I/O connectivity for door and equipment monitoring.
**Input Monitoring:**
Four input states are monitored (using default two 4k7 ohm resistors or optional configurable end-of-line resistances):
* Open
* Closed
* Short Circuit (Tamper)
* Open Circuit (Tamper)
Inputs on HBUS Modules can be used to monitor:
* Access controlled doors
* Intruder detection (e.g., passive, infra-red detectors, glass break detectors)
* Monitored doors
* Equipment alarms
* Any devices providing a clean switch contact
**Relay Control:**
On-board relays can control:
* Access controlled doors
* Alarm outputs (e.g., to activate sirens)
* Time activated outputs (e.g., to switch on lighting or air conditioning)
## Common Fault Diagnosis
### Gallagher SMB Troubleshooting for Installers (General Troubleshooting)
**Controller Offline Incident:**
* **Step 1: Check Config app and Controller state.** Monitor the Config app to confirm when the Controller comes online. Inform the customer when the system has reconnected.
* **Step 2: Check Bluetooth reader flashing orange.** If it is, there may be an issue with the Controller. Check the power supply (voltage should be 13.6V ±15%). Then, power cycle the controller.
* **Step 3: Check internet connection.** If the site doesn't have a cellular router installed, check the site's internet connection and restart the site's internet router. If this doesn't resolve the issue, restart the Controller.
* **Step 4: Contact Gallagher Support Team.** If the Controller is still failing to connect.
**AC Mains Fail Incident:**
* **Step 1: Check Customer app for active alarm.** If the red alarm icon has disappeared, the alarm is no longer active, indicating the system has power again. The incident can now be closed. If still active, check power and battery on-site.
* **Step 2: Check site power.** If no power, there may be a power cut, and the battery should have kicked in.
* **Step 3: Check and replace battery if necessary.**
**Low Battery Incident:**
* **Step 1: Check Customer app for active alarm.** If the red alarm icon has disappeared, the alarm is no longer active, indicating the battery is no longer low. The incident can now be closed. If still active, check battery on-site.
* **Step 2: Check and replace battery if necessary.**
**Not Receiving Notifications (Incident or Late to Arm):**
* Uninstall the app and wait 5 minutes. Send a new mobile invitation. Follow the instructions in the invite email.
**App Hangs on Login Screen:**
* **Step 1: Has PIN code / lock screen security been removed from the phone?** If yes, PIN / lock screen security needs to be re-added.
* **Step 2: Uninstall and reinstall app.** Have the user uninstall the app. Send a new mobile invitation to the user. Follow the instructions in the invite email.
**Blank Screen:**
* **Step 1: Restart the app or the phone.**
* **Step 2: Check compatible OS version.** Does the customer have a compatible (recent) version of the operating system on their device? Upgrade their device's OS.
=== WEB RESEARCH: command centre ===
# Gallagher Command Centre Technical Reference
## Manufacturer
Gallagher Security
## Discipline
access
## Product Range and Model Numbers
* **Gallagher Controller 6000 (C6000)**
* C300100: Gallagher Controller 6000
* C300111: Gallagher Controller 6000, 2 Door Variant
* C305101: Gallagher High Sec Controller 6000
* C300101: Gallagher Controller 6000 Enhanced
* C305111: Gallagher High Sec Controller 6000, 2 Door
* **HBUS Modules**
* C300142: Gallagher 4H Module
* C300182: Gallagher 8H Module
* C300660: HBUS 8 In 2 Out Door Module
* **Cabinets**
* C200100: Gallagher Single Cabinet
* C200104: Gallagher Dual Cabinet (Cool Grey)
* C200103: Gallagher Dual Cabinet (Charcoal)
## Technical Specifications
### Controller 6000
* **Doors supported:** 10 (Standard, Enhanced, High Sec), 2 (Two Door, High Sec 2 Door)
* **Ethernet 10/100 port:** 1 (Standard, Two Door, High Sec, High Sec 2 Door)
* **Ethernet 10/100/1000 port:** 2 (Enhanced)
* **Power Voltage:** 13.6 V DC ±15%
* **Idle current @ 13.6Vdc (No Relays / 4 Relays / 8 Relays):**
* C6000: 175mA / 320mA / 460mA
* C6000 Enhanced & High Sec: 610mA / 730mA / 870mA
* **Operating temperature:** -10°C to +70°C (C6000), -10°C to +55°C (HS C6000)
* **Humidity:** 95% Non-condensing
* **Dimensions (H x W x D):** 100 x 180 x 42mm (3.9 x 7.1 x 1.7in)
* **Maximum speed:**
* HBUS: 1Mbit/s, 500m (1640ft)
* GBUS: 38.4Kbit/s, 1200m (3937ft)
* OSDP: 115.2Kbit/s, dependent on cable type
* SensorBUS: 115.2Kbit/s, dependent on cable type
* Aperio: 19.2Kbit/s, 1000m max.
* **Number of ports:** 1 x USB 2.0 port, 1 x RS232 port
* **Standards compliance:** CE, RCM, FCC, UL, FIPS 201-2 GSA APL, AS/NZS 2201 – Class 5
### HBUS Modules (4H and 8H)
* **Inputs:** 8H Module: 24, 4H Module: 12
* **Outputs:** 8H Module: 8 SPDT relays, 4H Module: 4 SPDT relays
* **Power Voltage:** 13.6 V DC ±15%
* **Current (Via Gallagher Controller connector):** 40mA
* **Current (Via HBUS Module power in - No relays / 4 relays / 8 relays):** 30mA / 175mA / 315mA
* **Operating temperature:** -10 to +70 °C
* **Humidity:** 95% Non-condensing
* **Standards Compliance:** FCC, CE, RCM, RoHS
## Default Codes
* **Gallagher Command Centre Initial Login:** Username: `system`, Password: (none) - forces user to set a password upon first login.
## Fault/Event/Alarm Code Tables
| Description | Type | Compass AlarmType |
| :--- | :--- | :--- |
| System Offline | 1 | ALARMSENSOR_GENERIC |
| System Online | 2 | ALARMSENSOR_CONNECTION_RESTORED |
| Access denied | 3 | ACCESSPOINT_NO_ACCESS |
| Tamper | 1 | ALARMSENSOR_GENERIC |
| Controller tampered (front) | 3000 | ALARMSENSOR_GENERIC |
| Controller tampered (rear) | 3066 | ALARMSENSOR_GENERIC |
| Controller Upgrade | 5029 | ALARMSENSOR_GENERIC |
| Cabinet tampered | 5064 | ALARMSENSOR_GENERIC |
| Input Tampered | 22002 | ALARMSENSOR_GENERIC |
| Input Break | 22003 | ALARMSENSOR_GENERIC |
| Input Short | 22004 | ALARMSENSOR_GENERIC |
| Unit Tampered | 23030 | ALARMSENSOR_GENERIC |
| Unit Tampered (Front) | 23070 | ALARMSENSOR_GENERIC |
| Unit Tampered (Rear) | 23071 | ALARMSENSOR_GENERIC |
| Unit on Door Tampered | 23211 | ALARMSENSOR_GENERIC |
| Salto Door Tampered | 25003 | ALARMSENSOR_GENERIC |
| Engage Bluetooth Tamper | 42615 | ALARMSENSOR_GENERIC |
| Engage Lock Cover Tamper | 42616 | ALARMSENSOR_GENERIC |
| Engage Magnetic Tamper | 42617 | ALARMSENSOR_GENERIC |
| Engage Reader Tamper | 42626 | ALARMSENSOR_GENERIC |
| Tamper Return To Normal | 2 | ALARMSENSOR_GENERIC |
| Controller no longer tampered | 3065 | ALARMSENSOR_GENERIC |
| Controller no longer tampered (rear) | 5002 | ALARMSENSOR_GENERIC |
| Controller no longer tampered (front) | 5003 | ALARMSENSOR_GENERIC |
| Controller Upgrade | 5030 | ALARMSENSOR_GENERIC |
| Cabinet no longer tampered | 5065 | ALARMSENSOR_GENERIC |
| Unit - no longer tampered | 23069 | ALARMSENSOR_GENERIC |
| Unit no longer tampered (front) | 23104 | ALARMSENSOR_GENERIC |
| Unit no longer tampered (rear) | 23105 | ALARMSENSOR_GENERIC |
| Salto Door No Longer Tampered | 25011 | ALARMSENSOR_GENERIC |
| Unit Stopped Responding | 3 | ALARMSENSOR_GENERIC |
| Alarm transmitter receiver(s) offline | 3230 | ALARMSENSOR_GENERIC |
| Plug-in Module not responding | 5001 | ALARMSENSOR_GENERIC |
| Diagnostics Service Observability Platform Stopped Responding | 7043 | ALARMSENSOR_GENERIC |
| Unit Not Responding | 23038 | ALARMSENSOR_GENERIC |
| Sensor(s) Offline | 23111 | ALARMSENSOR_GENERIC |
| Card reading module offline | 23212 | ALARMSENSOR_GENERIC |
| Safety Micro Offline | 40145 | ALARMSENSOR_GENERIC |
| Lock Offline | 41400 | ALARMSENSOR_GENERIC |
| Elevator Service Offline | 42401 | ALARMSENSOR_GENERIC |
| ThyssenKrupp Elevator Offline | 42404 | ALARMSENSOR_GENERIC |
| ThyssenKrupp Elevator Group Offline | 42406 | ALARMSENSOR_GENERIC |
| Elevator Web Service Offline | 42408 | ALARMSENSOR_GENERIC |
| ThyssenKrupp Kiosk Offline | 42411 | ALARMSENSOR_GENERIC |
| ThyssenKrupp Elevator Rear Panel Offline | 42420 | ALARMSENSOR_GENERIC |
| Engage Gateway Offline | 42621 | ALARMSENSOR_GENERIC |
| Engage Door Offline | 42630 | ALARMSENSOR_GENERIC |
| SIP Service Stopped Responding | 42902 | ALARMSENSOR_GENERIC |
| Diagnostics Service Stopped Responding | 43102 | ALARMSENSOR_GENERIC |
| Closed/On | 4 | ALARMSENSOR_GENERIC |
| Logic Block On | 3302 | ALARMSENSOR_GENERIC |
| Input Closed | 22000 | ALARMSENSOR_GENERIC |
| Output On | 24001 | ALARMSENSOR_GENERIC |
| Open/Off | 5 | ALARMSENSOR_GENERIC |
| Logic Block Off | 3303 | ALARMSENSOR_GENERIC |
| Input Open | 22001 | ALARMSENSOR_GENERIC |
| Output Off | 24000 | ALARMSENSOR_GENERIC |
| Card Error | 6 | ALARMSENSOR_GENERIC |
| Foreign Card | 20016 | ALARMSENSOR_GENERIC |
| Illicit Card | 20017 | ALARMSENSOR_GENERIC |
| Illicit GovPass Card | 20020 | ALARMSENSOR_GENERIC |
| Terminal: Foreign Card | 20066 | ALARMSENSOR_GENERIC |
| Terminal: Illicit Card | 20067 | ALARMSENSOR_GENERIC |
| Non MIFARE Enhanced Security Card | 20102 | ALARMSENSOR_GENERIC |
| Non High-Security Card Type | 20116 | ALARMSENSOR_GENERIC |
| Non Proximity Check Card | 20117 | ALARMSENSOR_GENERIC |
| Potential Duplicate Card | 20118 | ALARMSENSOR_GENERIC |
| PIV Controller Incompatibility | 20119 | ALARMSENSOR_GENERIC |
| Foreign Card - Locker | 42114 | ALARMSENSOR_GENERIC |
| Illicit Card - Locker | 42115 | ALARMSENSOR_GENERIC |
| Shunted/Isolated | 7 | ALARMSENSOR_GENERIC |
| Input Shunted | 22005 | ALARMSENSOR_GENERIC |
| Input Isolated | 22012 | ALARMSENSOR_GENERIC |
| Sensor Group Shunted | 41121 | ALARMSENSOR_GENERIC |
| Controller Bus Shunted | 41140 | ALARMSENSOR_GENERIC |
| Device Shunted | 41142 | ALARMSENSOR_GENERIC |
| Controller Bus Automatically Shunted | 41144 | ALARMSENSOR_GENERIC |
| Maintenance Warning | 8 | ALARMSENSOR_GENERIC |
| Controller Incompatible configuration | 309 | ALARMSENSOR_GENERIC |
| Controller Unknown version | 310 | ALARMSENSOR_GENERIC |
| Controller Multiple Server Connections | 314 | ALARMSENSOR_GENERIC |
| SQL Server Database Space Shortage Warning | 401 | ALARMSENSOR_GENERIC |
| SQL Server Database Space Shortage Notification | 402 | ALARMSENSOR_GENERIC |
| Local Drive Low Disk Space Warning | 411 | ALARMSENSOR_GENERIC |
| Local Drive Low Disk Space Notification | 412 | ALARMSENSOR_GENERIC |
| Database Logon Failure | 413 | ALARMSENSOR_GENERIC |
| License Warning - Devices required to maintain your license validity are not responding | 510 | ALARMSENSOR_GENERIC |
| Download warning. | 515 | ALARMSENSOR_GENERIC |
| License Warning - License has expired | 530 | ALARMSENSOR_GENERIC |
| License Warning - License is not valid for this version of Command Centre | 531 | ALARMSENSOR_GENERIC |
| License Warning - License limits have been exceeded | 532 | ALARMSENSOR_GENERIC |
| Duplicate finger biometrics | 554 | ALARMSENSOR_GENERIC |
| Ident Dongle License Limit Exceeded | 555 | ALARMSENSOR_GENERIC |
| Database Maintenance Failed | 561 | ALARMSENSOR_GENERIC |
| Duplicate wave biometrics | 562 | ALARMSENSOR_GENERIC |
| Controller IP Address Incorrect. | 704 | ALARMSENSOR_GENERIC |
## Zone Types and Descriptions
**Regulated Zones (Feature 8.60)**
This feature introduces a new 'Regulated Zone' Command Centre item for monitoring Cardholders. The Regulated Zone is separate from Access Zones (but potentially encompasses one or multiple Access Zones), and is used to define the on-site area that is monitored by pre-configured time limits.
The 'Regulated Zones' feature monitors Cardholders using the following parameters (rules):
1. **Cumulative duration:** Used to monitor Cardholders' accumulated time-on-site across multiple shifts. An event is raised when a Cardholder has been inside the Regulated Zone for a period greater than the configured cumulative shift duration, within a specified period of time.
2. **Break duration:** Used to monitor Cardholders' minimum break periods between shifts. An event is raised when a Cardholder re-enters the Regulated Zone within the minimum break period. A temporary exit grace period can be configured to define a period of time a Cardholder is allowed off-site before they are considered to be between shifts.
3. **Maximum duration:** Used to monitor Cardholders' time-on-site within a single shift (period of time). An event is raised when a Cardholder has been inside the Regulated Zone for a period of time greater than the configured shift length.
4. **Predictive cumulative duration:** Used to monitor Cardholder accumulated time-on-site across multiple shifts and predict if a Cardholder will exceed the cumulative limit (total time limit across shifts). When a Cardholder enters the Zone, a rule is checked: will the Cardholder end up at or above the cumulative limit if they stayed in the Regulated Zone for the Expected shift duration. If yes, a predictive alarm is raised.
5. **Shift management:** Used to monitor Cardholders' shift patterns and optionally enforce Cardholders' compliance with shift patterns. An alarm is raised when a Cardholder enters the Regulated Zone before the first day of their shift. An alarm is also raised when a Cardholder does not exit site when their shift ends. Grace periods can be configured to allow Cardholders to enter site one, two or three days before their shift starts, and leave one, two or three days after their shift ends.
## Wiring Diagrams and Terminal Descriptions
### Wiegand Connection Diagram - Controller 6000 with HBUS 4-in-2 Out Door Module
**Controller 6000 Connections:**
* **New Device (Reader):**
* Wiegand D0 (Green)
* Wiegand D1 (White)
* TTL In (Yellow)
* TTL In (Red)
* Wiegand Ground (Black)
* **HBUS 4-in-2 Out Door Module (Wiegand to Controller):**
* Data 0 (Green)
* Data 1 (White)
* BT Out 1 (Yellow)
* BT Out 2 (Red)
* GND (Black)
* COM A
* COM B
* GND
* +V
### Controller 6000 Connections (from ACCESS CONTROL SYSTEM CONTROLLER-6000 / EASY-SOFT 6000 manual)
**Connection of an Interface RF/WG / Connect / Cityprox-C4+ / Steelprox-C4+ to the CONTROLLER-6000**
* **Number of wires:** 3
* **For distances until 10 metres:** 3 wires of 0.5mm² AWG20
* **For distances until 100 metres:** Cable 3x0.5mm² shielded
* **Shielding:** Obligatory from 10m
* **Maximum distance:** 100m
* **Terminal of connection to the controller:** + - S
**Connection of a Wiegand system to the CONTROLLER-6000 (Evoprox, etc...)**
* **Number of wires:** 5
* **For distances until 10 metres:** 5 wires of 0.5mm² AWG20
* **For distances until 100 metres:** Cable 5x0.5mm² shielded
* **Shielding:** Obligatory from 10m
* **Maximum distance:** 100m
* **Terminal of connection:** Individual terminals for each door
* **CONTROLLER-6000 terminal:** + 12Vdc, 0V, Clock, Data, Led
**Connection of the CONTROLLER-6000 to the bus RS485**
* **Number of wires:** 3
* **Shielding:** Obligatory
* **Maximum distance:** 1200m
* **Use wires:** FTP5 or superior.
**Connection of a pushbutton of a door to the CONTROLLER-6000**
* **Number of wires:** 2 de 0,5mm² AWG20
* **Shielding:** Recommended
* **Maximum distance:** 100m
* **Terminal of connection:** Individual terminals for each door
**Connection of an electrolock to the CONTROLLER-6000**
* **Electrolock 500mA max.:** Until 50m: 0,5mm² AWG20, Until 100m: 1,5mm² AWG16
* **Electrolock 190mA max.:** Until 50m: 1,5mm² AWG16, Until 100m: 1mm² AWG18
* **Electromagnet 0,5Amp/12Vcc:** Until 50m: 1mm² AWG18, Until 100m: 1,5mm² AWG16
## Programming Menu Structure and Commissioning Steps
### Gallagher Access Engineer Course - C892320 (Advanced Functionality and Configuration)
**Healthcare Scenario:**
* **System Divisions:** Operators and Divisions, Inheritance of Division Privileges, Setting up System Divisions.
* **Operator Groups and Divisions**
* **Macros:** Securing an Access Zone via (Lockdown), Setting up the T20 Mimic Panel, Setting the LED flash sequence.
* **Action Plans**
* **Alarm Instructions:** Creating a New Alarm Instruction.
* **Insertion Tags:** Creating an Insertion Tag, Assigning Alarm Instructions, Viewing Alarm Instructions in Command Centre.
* **Guard Tours for Gallagher Command Centre:** Configuring a Guard Tour, Guard Tours & the Event Response Tab, Guard Tours & the Status and Overrides Tab, Running a Guard Tour, Restarting a Guard Tour (if halted).
* **Site Plans:** Setting up Site Plans, Layering Site Plans, Adding Items to Site Plans, Using Graphics to Replace Icons, Adding a Macro to a Site Plan, Creating a New Icon Set.
**Mining Scenario:**
* **Identity Analytics:** Configuring Competencies, Access Zone Competencies, Assigning Competencies, Configuring Cardholders, Adding a Competency to a Cardholder.
* **Anti-passback:** Configuring Anti-passback, Anti-passback Forgive after Time, Anti-passback Forgive all Cardholders, Anti-passback Forgive a specific Cardholder.
* **Event Notification Filters:** Email and Mobile PDFs, Enabling your Event Notifications, Creating a Notification Schedule, Assigning a Notification Schedule, Setting up the Email and SMS Server.
* **Zone Counting:** Configuring Zone Counting Events.
**Education Scenario:**
* **Access Group Lineage:** Master Access Group, Assigning Lineage.
* **First Card Unlock**
* **Personalised Actions:** Controlling Lockers, Configuring Locker Personalised Actions, Testing the Locker Scenario, Access Granted vs Access Taken Options, Using Macros in Personalised Actions.
**Enterprise Data Interface:**
* **Operator Privileges:** The Run as Operator, Creating the Run as Operator.
* **The Source File**
* **Enterprise Data Interface Folders:** Create Local File Locations on the Server.
* **Importing Images with EDI**
* **Configuring Command Centre to Receive the Source Data:** Create/Configure Personal Data Fields.
* **Creating an EDI Interface:** Setting the Mapping of Data between the Source File and Command Centre Data.
* **Creating a Transformation Mapping:** Adding a Card Transformation, Adding Access Group Transformations.
* **Running EDI Manually:** Error Messages and Log Files.
**Data Centre Scenario:**
* **Low Level Elevator Cars:** Creating the Elevator Controls, Access Zone Modes, Virtual Outputs, Inputs, Elevator Car, Configuring Elevator Floors, Advanced, Configure Access Group, Card Pin Codes, Reporting.
* **Interlocking Doors:** Adding a New Interlock Group.
* **Challenge:** Setting up Challenge, Setting up the Access Group.
* **Logic Blocks:** Logic Block Rules, Introducing Logic Block Configurations, Controlling an Alarm Zone, Assigning Alarm Zone Privileges, How the Logic Works.
* **Contact ID:** Setting up the GG for the Server Room Alarm, Intruder Alarm Example, Panic Alarm Example, General Information.
### Programming and Commissioning from ACCESS CONTROL SYSTEM CONTROLLER-6000 / EASY-SOFT 6000 manual
**1.5 Modes of Use**
The Controller-6000 can operate in two modes:
* **Autonomous mode (with PALM):** The controller operates independently, typically with an IRDA connection module and the PICADOR handling program for PALM devices. This mode is limited to a single controller and does not support parallel connections. Switches 7 and 8 must be in the ON position for this mode.
* **Centralised mode (with PC):** This mode allows multiple controllers to be connected in parallel and managed through the EASY-SOFT 6000 program. Each controller needs to be codified with its network position using DIP-switches. For remote control, a CONTROLLER-6000 modem is connected between the RS485 interface and the controller, along with a telephone line.
**2 Installation Manual for the EASY-SOFT 6000**
**2.1 Minimum Requirements for System / Rapid Installation**
To install the EASY-SOFT 6000 program, which controls the CONTROLLER-6000 units:
1. **Connect the RS485 converter:** Connect the RS485 converter to the PC and the central unit.
2. **Install the program:** Insert the EASY-SOFT 6000 CD-Rom and run `setup.exe`. Follow on-screen instructions.
3. **Install webcam drivers:** If applicable, explore the EASY-SOFT 6000 CD, open the Webcam file, run `setup.exe`, and follow on-screen instructions.
4. **Install 'dongle' (protection key):** The dongle supplied with the program must be installed in one of the central units in the network.
**Minimum System Requirements:**
* **Operating System:** Windows 98, Me, 2000, NT (Service pack 6), XP Pro, XP Home (if webcam is not used).
* **Processor:** Pentium II 233 MHz.
**3 Manual for Use of the EASY-SOFT 6000 Programme**
* **3.1. Starting a Session**
* **3.2 Control of Accesses:** Groups of Users, Time Bands, Series of Keys or Transmitters, Public Holidays, Configuration of Events
* **3.3 Analysis Tools**
* **3.4 Processing Events**
* **3.5 Search a Key or Transmitter:** Handling Keys and Transmitters, Personalization of a Key or Transmitter
* **3.6 Updating a Remote Control**
## Expander/Peripheral Devices
### Gallagher HBUS Modules (4H and 8H)
Gallagher 8H and 4H modules are expander devices that support star wiring of secure high-speed HBUS devices, including T-Series Readers and F-Series fence controllers. They also provide I/O connectivity for door and equipment monitoring.
**Input Monitoring:**
Four input states are monitored (using default two 4k7 ohm resistors or optional configurable end-of-line resistances):
* Open
* Closed
* Short Circuit (Tamper)
* Open Circuit (Tamper)
Inputs on HBUS Modules can be used to monitor:
* Access controlled doors
* Intruder detection (e.g., passive, infra-red detectors, glass break detectors)
* Monitored doors
* Equipment alarms
* Any devices providing a clean switch contact
**Relay Control:**
On-board relays can control:
* Access controlled doors
* Alarm outputs (e.g., to activate sirens)
* Time activated outputs (e.g., to switch on lighting or air conditioning)
## Common Fault Diagnosis
### Gallagher SMB Troubleshooting for Installers (General Troubleshooting)
**Controller Offline Incident:**
* **Step 1: Check Config app and Controller state.** Monitor the Config app to confirm when the Controller comes online. Inform the customer when the system has reconnected.
* **Step 2: Check Bluetooth reader flashing orange.** If it is, there may be an issue with the Controller. Check the power supply (voltage should be 13.6V ±15%). Then, power cycle the controller.
* **Step 3: Check internet connection.** If the site doesn't have a cellular router installed, check the site's internet connection and restart the site's internet router. If this doesn't resolve the issue, restart the Controller.
* **Step 4: Contact Gallagher Support Team.** If the Controller is still failing to connect.
**AC Mains Fail Incident:**
* **Step 1: Check Customer app for active alarm.** If the red alarm icon has disappeared, the alarm is no longer active, indicating the system has power again. The incident can now be closed. If still active, check power and battery on-site.
* **Step 2: Check site power.** If no power, there may be a power cut, and the battery should have kicked in.
* **Step 3: Check and replace battery if necessary.**
**Low Battery Incident:**
* **Step 1: Check Customer app for active alarm.** If the red alarm icon has disappeared, the alarm is no longer active, indicating the battery is no longer low. The incident can now be closed. If still active, check battery on-site.
* **Step 2: Check and replace battery if necessary.**
**Not Receiving Notifications (Incident or Late to Arm):**
* Uninstall the app and wait 5 minutes. Send a new mobile invitation. Follow the instructions in the invite email.
**App Hangs on Login Screen:**
* **Step 1: Has PIN code / lock screen security been removed from the phone?** If yes, PIN / lock screen security needs to be re-added.
* **Step 2: Uninstall and reinstall app.** Have the user uninstall the app. Send a new mobile invitation to the user. Follow the instructions in the invite email.
**Blank Screen:**
* **Step 1: Restart the app or the phone.**
* **Step 2: Check compatible OS version.** Does the customer have a compatible (recent) version of the operating system on their device? Upgrade their device's OS.
| Component | Function | Notes |
|---|---|---|
| Security Center Server | Central server — manages all subsystems | Windows Server |
| Synergis Cloud Link | Access control gateway | Connects to door controllers |
| Omnicast Archiver | Video recording server | Records camera streams |
| Security Desk | Operator workstation | Monitoring and management |
| Code / Display | Description | Likely Cause | Action |
|---|---|---|---|
| Controller Offline | Controller not communicating | Network fault, power loss | Check network and power. |
| Card Not Found | Card not recognised | Card not enrolled | Re-enrol card. |
| Access Denied | Card read but access denied | Access rule, schedule | Check access rule and schedule. |
| Video Fault | Camera not recording | Camera offline, disk fault | Check camera and archiver. |
| Server Fault | Security Center server not responding | Service stopped | Restart Security Center service. |
| Licence Fault | Licence expired | Licence renewal required | Contact Genetec for licence renewal. |
| Terminal | Function | Notes |
|---|---|---|
| +12V | Power supply | 12V DC from PSU |
| 0V | Common ground | Must be continuous |
| ETH | Ethernet | TCP/IP connection to Security Center server |
| RS-485 A+ | RS-485 data positive | To door controllers |
| RS-485 B− | RS-485 data negative | To door controllers |
=== WEB RESEARCH: genetec ===
# Genetec Security Center Access Control - Comprehensive Technical Reference
## Manufacturer and Product Name
**Manufacturer:** Genetec Inc.
**Product:** Security Center (specifically Synergis Access Control)
## 1. Synergis Master Controller (SMC) Configuration Guide 2.1
### 1.1 Introduction to Synergis Master Controller
**What is Synergis Master Controller?**
Synergis Master Controller (SMC) is Genetec’s access control unit that supports a variety of third-party interface modules over IP, USB, and RS-485. SMC is seamlessly integrated to Security Center, and is capable of making the access control decisions independently of the Access Manager. SMC and accessories can be housed inside an enclosure that make up the Synergis access control system.
**Components:**
* **Controller module:** Processing component of SMC with IP capability, pre-loaded with the controller firmware and a web-based administration tool, Controller Portal.
* **Four-port RS-485 module:** RS-485 communication component of SMC with four ports (or channels) named A, B, C, and D. The number of interface modules you can connect to each channel depends on the type of hardware you have. In configurations where interface modules only use IP or USB connections, the Four-port RS-485 module is not needed.
### 1.2 Getting started with Controller Portal
**What is Controller Portal?**
Controller Portal is the web-based interface for the configuration and maintenance of SMC. It allows you to connect to an SMC unit using a web browser.
**Controller Portal tasks:**
* Change the security password required to log on to the SMC unit.
* Configure the network settings on the SMC unit so it works on your system.
* Configure SMC to accept connections from specific Access Manager servers.
* Configure the properties of the interface modules attached to the SMC unit.
* Configure the access control behavior for SMC, in both online and offline modes.
* View the activity logs stored on the SMC unit.
* Test and diagnose the interface module connections to the SMC unit.
* View and export the SMC status and configuration.
* Upgrade the SMC firmware.
* Restart the SMC hardware or software.
* Update security clearance levels assigned to Security Center areas manually on the SMC unit when the connection to the Access Manager is lost.
**Tasks NOT performable with Controller Portal (use Config Tool instead):**
* Enable/disable the Mixed mode operation.
* Assign devices (input/output contacts, readers) to doors and zones.
* Configure individual door and zone properties.
* Configure Card and PIN readers so both the card and the PIN are required to grant access.
* Configure IO linking.
**Log on to SMC:**
* **SMC Hostname:** SMC followed by the controller’s MAC address (e.g., SMC0010F31A176A).
* **Default username:** admin
* **Default password:** softwire
* Only one user can be connected to SMC at any given time.
**To log on:**
1. (First time logon only) Connect the SMC’s LAN 1 connector to your LAN.
2. Open a web browser.
3. In the browser’s address bar, type `https://` followed by the SMC hostname or IP address (e.g., `https://SMC0010F31A176A`).
4. (New browser session only) If you opened a new browser session, you’ll get a certificate error message. Follow your browser’s on-screen instructions to continue to the website.
5. In the Synergis Master Controller - Logon page, select the interface language.
6. Enter the username and password, then click Log on. The Controller Portal - Home page appears.
**Change the logon password:**
1. Log on to SMC.
2. From the Controller Portal - Home page, click Users.
3. From the User configuration page, select the user you want to modify and click Change password.
4. In the Change password dialog box, enter the new password twice and click Apply.
**Controller Portal interface tour (Home page links):**
* **Home:** Returns to Home page.
* **Log off:** Logs you off from SMC and displays the Logon page.
* **About:** Shows the SMC firmware version and copyright information.
* **Help:** Opens the Synergis Master Controller Configuration Guide in a separate browser page.
* **Network:** Opens the network configuration page, which is where you configure the SMC unit to work on your network and the Access Manager it should obey to.
* **Logging:** Used to configure the event logging options for troubleshooting purposes.
* **Access control:** Used to configure the access control behavior that applies to all interface modules connected to the SMC unit.
* **Hardware:** Used to define the interface modules attached to the SMC unit.
* **Users:** Used to configure who has the rights to log on to SMC and change its configuration.
* **Lock pairing mode:** (Only applicable to Assa Abloy IP locks) Used to discover IP locks on the network.
* **Primitive key store:** (Only applicable to STid readers) Used to change the Signature and Encipherment keys used to communicate with the STid readers controlled by SMC.
* **Security clearance levels:** (For threat level management) Used to change the Security clearance assigned to areas when the connection between SMC and its Access Manager is lost.
* **Troubleshooting:** Used to generate troubleshooting reports by querying the event log saved on the SMC unit.
* **Download support logs:** (Only appears if Support logs are enabled) Used to download support logs to help Genetec Technical Support troubleshoot your system.
* **IO diagnostics:** Shows the IO diagnostics page for this SMC unit. Use this page to watch the states of the contacts and readers change in real time as you perform tests with the devices connected to the interface modules.
* **System status:** Shows a snapshot of your unit and network status. You can also export the system information to a CSV file from this page.
* **Firmware upgrade:** Used to upgrade the SMC firmware or to revert it to the previous version (if available).
* **System restart:** Used to restart the SMC hardware or software.
### 1.3 SMC configuration
**Configuration prerequisites:**
* Read the Synergis Master Controller Release Notes.
* Computer with network card, Ethernet cable, and web browser.
* (Optional) IP address assigned by IT department to the SMC unit.
* Configure hardware settings (DIP switches, address dials, etc.) on interface modules.
* Connect interface modules to the SMC unit through proper communication channels.
* **NOTE:** All interface modules connected to the same RS-485 channel must be from the same manufacturer.
* Physical devices (REX, door sensors, etc.) should be connected.
* Download the latest SMC firmware from `https://gtap.genetec.com`.
* Install and configure Security Center with at least one Access Manager role.
**Configuration process overview:**
1. **Network Configuration:** Configure SMC’s network properties. If network does not support DHCP, IT must assign a new IP address. [See "Configure the SMC’s network properties" on page 13 of the original document]
2. **Firmware Upgrade:** Make sure you have the latest SMC firmware, and upgrade if necessary. [See "Check and upgrade the SMC firmware" on page 34 of the original document]
3. **Physical Connection:** Physically attach the interface modules to the controller module. [See Synergis Master Controller Hardware Installation Guide]
4. **Interface Module Configuration:** Establish communication between the SMC and its attached interface modules by configuring them in Controller Portal. [See "Configure the interface modules attached to SMC" on page 15 of the original document]
5. **Hardware Testing:** Test your hardware connections and configuration and make adjustments if necessary. [See "Test the interface modules attached to SMC" on page 19 of the original document]
6. **Access Control Behavior:** Configure the access control behavior you want SMC to exhibit. [See "Configure the unit-wide access control behavior" on page 21 of the original document]
7. **Event Logging (Optional):** Select the event logs you want to be available for troubleshooting. [See "Configure the event logging options" on page 24 of the original document]
8. **Enrollment in Security Center:** Add the SMC unit to an Access Manager so it becomes part of your Security Center system. [See "Enrolling the SMC unit in Security Center" on page 26 of the original document]
**Configure the SMC’s network properties:**
1. Log on to SMC.
2. From the Controller Portal - Home page, click Network, then Network properties.
3. Select the network interface used to connect the SMC unit to its Access Manager.
4. Configure the SMC unit’s IP address and the network properties.
* **IMPORTANT:** If the SMC is not on the same network segment as the Access Manager, then the SMC's IP address must be static, or the DHCP server must be configured to always assign the same IP address to the SMC.
5. Change the Discovery port if necessary (default is 2000).
6. Click Save. The controller firmware restarts.
**Configure the interface modules attached to SMC:**
An interface module is a third-party device that communicates with SMC over IP, USB, or RS-485, and provides input, output, and reader connections to the controller module.
1. Log on to SMC.
2. From the Controller Portal - Home page, click Hardware.
3. In the Hardware configuration page, click Add.
4. In the Add hardware dialog box, select the Hardware type, the Channel, and the rest of the interface module properties.
**Test the interface modules attached to SMC:**
1. Log on to SMC.
2. From the Controller Portal - Home page, click IO diagnostics.
3. In the IO diagnostics page, add the elements you wish to monitor.
4. Activate the devices (card readers, door sensors, door locks, etc.) attached to the SMC unit.
**Configure the unit-wide access control behavior:**
1. Log on to SMC.
2. From the Controller Portal - Home page, click Access control.
3. In the Access control page, select the options you want SMC to support:
* **Beep on door held open:** (Default=enabled) Reader beeps when door is held open too long.
* **Beep on door forced open:** (Default=enabled) Reader beeps when door is forced open.
* **Beep on access denied:** (Default=enabled) Reader beeps when access is denied.
* **Interlock single unlock:** (Default=disabled) Allows only one door to be unlocked at any given time in an interlock system.
* **Do not generate ‘Door open too long’ events when door is unrestricted:** (Default=disabled) Ignores Door open too long events when door is unlocked for maintenance or by schedule.
* **Card or PIN:** (Default=Card only) Allows either card or PIN for access. To enforce Card and PIN, configure in Config Tool.
* **Degraded mode (Mercury, VertX):** For Mercury and HID VertX interface modules. In degraded mode, the interface module makes decisions on its own when connection to SMC is lost, unlocking doors for all credentials matching specified Facility code (26 bits card format only).
* **Lock relay:**
* **After door opened:** Keep door unlocked for a certain delay after it opens.
* **When door closed:** Immediately lock the door after it closes.
4. Click Save.
**Configure the event logging options:**
SMC can keep detailed logs of all access control decisions it makes in the troubleshooting logs. These logs are off by default.
1. Log on to SMC.
2. From the Controller Portal - Home page, click Logging.
3. In the Logging page, select the types of events you wish to log.
4. Enable Support logs only when instructed by Genetec Technical Support.
5. Enable Activity events for the Troubleshooting report. Activity events that can be logged:
* **Reader activity:** All reader events (card read, PIN entered, mode change).
* **Input activity:** All input state changes.
* **Output activity:** All output state changes.
* **Access granted reasons:** All access granted events and reasons.
* **Access denied reasons:** All access denied events and reasons.
* **IO linking:** All IO linking events related to hardware zones.
* **Security clearance:** All changes to security clearance due to threat level activation/deactivation.
6. Click Save.
**Enrolling the SMC unit in Security Center:**
To enroll an SMC unit, you must assign it to an Access Manager.
**Enable the Access Manager to connect to the SMC units:**
1. Log on to Security Center with Config Tool.
2. Open the Access control task and select the Roles and units view.
3. Select the Access Manager role and select the Extensions tab.
4. Under the extension list, click Add an item.
5. In the Add extension dialog box, select SMC, and click Add.
6. In the extension list, select the SMC extension.
7. Under the list of Discovery ports, click Add an item.
8. In the Discovery port dialog box, enter the port number configured on the SMC units (default is 2000).
9. Click Create, then click Apply.
**Change the discovery port on SMC:**
1. Log on to SMC.
2. From the Controller Portal - Home page, click Networks, then Network properties.
3. Set the Discovery port to the value used by the Access Manager.
4. Click Save.
**About automatic discovery:**
New IP units on the network are automatically added to Security Center if:
* The SMC unit is using DHCP.
* The SMC unit has never been connected to any Access Manager before.
* The SMC unit and the Access Manager use the same discovery port.
* The SMC unit and the Access Manager are on the same network segment.
* The SMC unit is using the default logon username and password (admin/softwire).
**Add the SMC unit to an Access Manager manually:**
1. Log on to Security Center with Config Tool.
2. Open the Access control task and select the Roles and units view.
3. Select the Access Manager role, and click Add an entity.
4. In the menu that appears, select Access control unit.
5. In the unit creation dialog box, click Unit type and select SMC.
6. In the Network endpoint group, enter the SMC unit’s hostname or IP address, as well as the logon username and password (default: admin/softwire).
7. Click Next and select the partition the SMC unit should belong to.
8. Click Next and click Create.
9. Wait to see that the unit is successfully created and click Close.
10. Click Refresh.
### 1.4 Maintenance and troubleshooting
**Log on to SMC using the alternate IP address:**
If you are unable to connect to SMC using its hostname and you haven’t yet configured its IP address, you can use the alternate IP address.
**Check and upgrade the SMC firmware:**
1. Log on to SMC.
2. From the Controller Portal - Home page, click Firmware upgrade. The current firmware version is indicated.
3. If an upgrade is necessary, click Select upgrade file.
4. Select the firmware file (release_2.1_xxxx.yy.smc).
5. Click Open. SMC restarts.
**Generate troubleshooting reports:**
1. Log on to SMC.
2. From the Controller Portal - Home page, click Troubleshooting.
3. In the Troubleshooting page, set the Query filters:
* **Date and time:** Filter based on a time range.
* **Severity:** Filter on the event severity level (Information, Warning, Error).
* **Source:** Search for text in Physical source or Logical source.
* **Type:** Filter on the event type (Activity, System, Audit).
* **User:** Filter on the user who generated the event.
* **Message:** Search for text in the event message.
4. Click Generate. The troubleshooting report is displayed.
**Troubleshooting Report Event Severity Levels:**
* **Information:** Useful information unrelated to any critical situation that could help understand the context of another problem. All optional activity events are logged as information.
* **Warning:** Non-critical situation that may lead to more serious problems if left unattended.
* **Error:** Critical situation that needs immediate attention.
## 2. Security Center Administrator Guide 5.6
### 2.1 Security Center Architecture Overview
Security Center is a unified security platform that seamlessly blends IP security systems within a single interface. It is designed to simplify operations and enhance situational awareness.
**Key Components:**
* **Directory:** The central server that manages all Security Center entities, configurations, and user permissions.
* **Access Manager:** A role within Security Center responsible for managing access control units and processing access requests.
* **Client Applications:** Software used by operators to interact with Security Center, such as Security Desk and Config Tool.
* **Access Control Units:** Hardware devices (like Synergis Master Controllers or Synergis Cloud Links) that physically control doors, readers, and other access control peripherals.
### 2.2 How Security Center is Organized
Security Center organizes entities in a hierarchical structure to facilitate management and configuration.
**Key Organizational Concepts:**
* **Areas:** Logical groupings of doors and other security devices, often corresponding to physical locations within a facility.
* **Doors:** Represents physical access points, configured with readers, locks, and sensors.
* **Access Rules:** Define who can access which areas and at what times.
* **Cardholders:** Represents individuals with access credentials.
### 2.3 Hardware Zones, Virtual Zones, and I/O Zones
**Hardware Zone:** A zone entity in which the I/O linking is executed by a single access control unit. Works independently of the Access Manager. Cannot be armed or disarmed from Security Desk or by software command.
**Virtual Zone:** A zone entity in which the I/O linking is executed by the Access Manager. Requires constant communication with the Access Manager. Can be armed or disarmed from Security Desk or by software command.
**I/O Zone:** A zone entity that combines inputs and outputs from various access control units, allowing for complex logic and automation. Can be armed or disarmed from Security Desk or by software command.
## 3. Synergis Cloud Link Datasheet
### 3.1 Product Range and Model Numbers
**Synergis Cloud Link (SY-CLOUDLINK):** An intelligent and PoE-enabled access control appliance that supports a variety of third-party interface modules over IP and RS-485.
**Synergis Cloud Link 312 (SY-CLOUDLINK-312):** An expansion module for the Synergis Cloud Link, providing additional RS-485 ports for connecting more interface modules.
### 3.2 Technical Specifications
**Processor:** 4 GB RAM, 16 GB flash storage
**Network Interfaces:** Two Gigabit Ethernet ports
**On-board Inputs:** Four configurable inputs
**Security:** EAL6+ secure element, secure boot, TLS 1.3
**Power:** PoE (Power over Ethernet) or 12 VDC external power supply
**Dimensions:** (Refer to datasheet for exact dimensions)
**Weight:** (Refer to datasheet for exact weight)
**Operating Temperature:** (Refer to datasheet for exact range)
**Operating Humidity:** (Refer to datasheet for exact range)
**Warranty:** 24 months
**Certifications:** CE, UK, FCC, KC, ACMA, BIS, UL294, RoHS, REACH, WEEE
**Capacity:**
* Up to 256 readers/locks
* 600,000 cardholders
* 5,000,000 offline events
**Supported Downstream Devices:**
* Mercury controllers
* ASSA ABLOY wireless locks
* Allegion wireless locks
* SimonsVoss wireless locks
* Various I/O panels
## 4. Synergis Cloud Link Hardware Installation Guide 3.0
### 4.1 What is Synergis Cloud Link?
Synergis™ Cloud Link is an intelligent and PoE-enabled access control appliance of Genetec Inc. that supports a variety of third-party interface modules over IP and RS-485. Synergis™ Cloud Link is seamlessly integrated with Security Center and is capable of making access control decisions independently of the Access Manager. Synergis™ Cloud Link and accessories can be housed inside an enclosure that are part of a Synergis™ IP access control system.
**Hardware Features:**
* **RS-485:** Four embedded RS-485 communication ports (or channels) named A, B, C, and D. The number of interface modules you can connect to each channel depends on the type of hardware you have. When starting an RS-485 bus from the Synergis™ Cloud Link for HID module communication, you must set the associated termination DIP switch to ON. You must also set the termination jumper on the last connected module on the RS-485 bus.
* **USB1 and USB2:** For maintenance use only. Not evaluated by UL.
* **LAN1 and LAN2:** Two Ethernet LAN ports for connection to the IP network. Synergis™ Cloud Link can be powered using an Ethernet connection (PoE). Connecting to Security Center through the LAN 2 port has not been evaluated by UL and is for supplementary use only.
### 4.2 DIP Switch Command Codes for Synergis Cloud Link
You can use the DIP switches on the Synergis™ Cloud Link to run hardware commands. There are four DIP switches labelled 1 to 4. To run a command, set the DIP switches as indicated in the table below and press the EC button for one second. If the code is valid, the status LEDs will flash green for the process of the command, otherwise they flash red for one second. Synergis™ Cloud Link automatically performs a software restart after you have run a command.
**BEST PRACTICE:** To prevent an accidental configuration reset, always set the DIP switches back to ON ON ON ON after running a command.
| S1 | S2 | S3 | S4 | Command Description |
|---|---|---|---|---|
| OFF | OFF | OFF | OFF | Resets the Synergis™ Appliance Portal logon password to factory default (softwire). |
| ON | OFF | OFF | OFF | Resets all settings to factory default. This command has the following effects:
* Resets the Synergis™ Appliance Portal logon password to factory default (softwire).
* Resets the network addressing mode to DHCP.
* Resets the discovery port to 2000.
* Deletes all hardware (connected interface modules) configurations.
* Deletes all cardholder (credentials and access rules) configurations.
* Resets all unit-wide settings.
* Clears all logging options.
* **NOTE:** The unit firmware is not affected by this command. |
### 4.3 Wiring Guidelines for Synergis Enclosures
When connecting modules in a Synergis™ enclosure, use the wire gauges recommended by Genetec Inc. For UL installations, all wiring shall be UL certified Appliance Wiring Material (AWM).
**Recommended Wire Gauges:**
| Function | Specification |
|---|---|
| Readers | ALPHA 1299C, 22 AWG, 9-conductor, stranded, overall shield or equivalent 22AWG or 24AWG shielded multi-conductor cable. NOTE: Fewer conductors needed if not all control lines are used. |
| RS-485 | Belden 3105A or 9841 shielded cable or equivalent 22 AWG (maximum length of 4000 ft (1219 m)) or 24 AWG (maximum length of 2500 ft (762 m)) shielded communications cable with a characteristic impedance of 120 ohm. |
| 12 Volt (Power supply to fuse assembly) | 16 AWG |
| Ground (Power supply to fuse assembly) | 16 AWG |
| 12 Volt (Fuse assembly to Synergis™ Cloud Link and interface modules) | 20 AWG |
| Ground (Fuse assembly to Synergis™ Cloud Link and interface modules) | 20 AWG |
**NOTE:** For UL installations, the use of shielded cable for RS-485 and readers is required for UL 294 and ULC-S319 compliance.
### 4.4 Wiring Diagrams
* **Synergis wiring diagram: 4 HID modules with Synergis Cloud Link, fuse assembly, and power supply**
* **Synergis wiring diagram: 6 HID modules with fuse assembly**
* **Synergis wiring diagram: 3 Mercury modules with Mercury controller, Synergis Cloud Link, fuse assembly, and power supply**
* **Synergis wiring diagram: 5 Mercury modules with Mercury controller and fuse assembly**
* **Synergis wiring diagram: 2 HID modules with Synergis Cloud Link, fuse assembly, and power supply**
* **Synergis wiring diagram: 4 HID modules with fuse assembly**
* **Synergis wiring diagram: 1 Mercury module with Mercury controller, Synergis Cloud Link, fuse assembly, and power supply**
* **Synergis wiring diagram: 3 Mercury modules with Mercury controller and fuse assembly**
## 5. Synergis™ IX Programming Reference Manual
### 5.1 Controller Models, System Expansion and Capacities, and Technical Specifications
**Controller Models:**
* **SY-SIX-CTRL-DIN:** Synergis IX DIN rail mount controller.
* **SY-SIX-CTRL-DIN-1D:** Synergis IX DIN rail mount controller with 1 door capacity.
**System Expansion and Capacities:**
* Supports various expander modules for inputs, outputs, and readers.
* Specific capacities depend on the type and number of expander modules connected.
**Technical Specifications:**
* **Power Input:** 12-24 VDC
* **Current Draw:** (Refer to manual for specific current draw based on configuration)
* **Operating Temperature:** (Refer to manual for specific range)
* **Communication:** RS-485, Ethernet
* **Memory:** (Refer to manual for memory specifications)
### 5.2 Default Codes
**Default Installer Code:** 1234
**Password Policy for Synergis IX Web Interface:**
* Default username: `admin`
* Default password: `softwire`
* Password must be changed upon first login.
* Strong password policies are enforced.
### 5.3 Fault/Event/Alarm Code Tables
### Error Code Display
The following table is valid if the fault indicator is constantly on and the status indicator is flashing red. If the fault indicator is flashing, the module requires a firmware update or is currently in firmware update mode. The status indicator will flash red with the error code number. The error code number is shown with a 250ms on and off period (duty cycle) with a delay of 1.5 seconds between each display cycle.
| Flash | Error Description |
|---|---|
| 1 | **Unknown Error Code:** The error code returned by the system controller could not be understood by the module. |
| 2 | **Firmware Version:** The firmware version on the module is not compatible with the system controller. To clear this error, update the module using the module update feature in the controller's web interface. |
| 3 | **Address Too High:** The module address is above the maximum number available on the system controller. To clear this error change the address to one within the range set on the system controller, restart the module by disconnecting the power. |
| 4 | **Address In Use:** The address is already in use by another module. To clear this error set the address to one that is not currently occupied. Use the view network status command to list the attached devices, or the network update command to refresh the registered device list. |
| 5 | **Controller Secured Registration Not Allowed:** The controller is not accepting any module registrations. To allow module registrations use the network secure command to change the setting to not secured. |
| 6 | **Serial Number Fault:** The serial number in the device is not valid. Return the unit to the distributor for replacement. |
| 7 | **Locked Device:** The module or system controller is a locked device and cannot communicate on the network. Return the unit to the distributor for replacement. |
### Trouble Inputs (Fault Codes)
Trouble inputs are used to monitor the status of the controller and in most cases are not physically connected to an external input. These can then be used to report a message to a monitoring station, remote computer, keypad or siren.
| Input Number | Description |
|---|---|
| CP001:02 | 12V Supply Failure |
| CP001:04 | Real Time Clock Not Set |
| CP001:05 | Service Test Report |
| CP001:06 | ContactID Reporting Failure |
| CP001:07 | Phone Line Fault |
| CP001:08 | Auxiliary Fuse / Supply Fault |
| CP001:09 | Bell Siren Tamper / Cut |
| CP001:11 | Bell Siren Current Overload |
| CP001:13 | Module Communication Fault |
| CP001:14 | Module Security Violation |
| CP001:20 | Report IP Reporting Failure |
| CP001:24 | Installer Logged In |
| CP001:29 | System Restarted |
### 5.4 Programming Menu Structure
The Programming Menu provides access to various configuration options for the Synergis™ IX system. Below is an outline of the menu structure and key sub-sections:
### Doors
* **Door Groups**
* **Inputs**
* Inputs | Areas and Input Types
* Inputs | Options
* **Door Types**
* **Input Types**
* Input Types | Options 1
* Input Types | Options 2
* Input Types | Options 3
* Input Types | Options 4
### Areas
* **Areas | Configuration**
* **Areas | Reporting Services**
* **Areas | Outputs**
* **Areas | Options 1**
* **Areas | Options 2**
* **Areas | Events**
* **Area Groups**
### Outputs
* **Outputs | Options**
* **Output Groups**
### Keypad Groups
### Menu Groups
* **Menu Groups | Keypad Groups**
* **Menu Groups | Options**
### Trouble Inputs
* **Trouble Inputs | Areas And Input Types**
* **Trouble Inputs | Options**
### Elevators
### Phone Numbers
### Services
* **Contact ID**
* **Report IP**
### Scheduling Menu
* **Time**
* **Daylight Savings**
### 5.5 Expander/Peripheral Devices with Specs
### Keypads
* **Keypads | Configuration**
* **Keypads | Options 1**
* **Keypads | Options 2**
### Analog Expanders
* **Analog Expanders | Channel 1-4**
### Input Expanders
### Output Expanders
### Reader Expanders
* **OSDP Install Mode**
* **Reader Expanders | Reader 1-2**
* **Reader Expanders | Reader 1-2 Options**
### Smart Readers
* **Smart Readers | Reader Expander Addressing**
### 5.6 Common Fault Diagnosis
### Common Health Status Messages
* **Modules that Require a Restart:** Indicates that certain modules need to be restarted for proper operation.
* **Modules that are Offline:** Indicates that some modules are not communicating with the system.
* **Areas Requiring Rearming due to Input Changes:** Suggests that areas need to be re-armed after changes to inputs.
* **Areas with the Tamper Area Disarmed:** Indicates a tamper condition in an area that is disarmed.
* **Inputs Assigned an Area but no Input Type:** Highlights an configuration error where an input is assigned to an area but lacks a defined input type.
## 6. Compliance Standards Met (from Synergis Cloud Link Hardware Installation Guide 3.0)
UL-listed equipment and subassemblies are compliant to the following standards and levels:
* **ULC S319 System Class I**
* **UL 294, Destructive Attack Level I**
* **UL 294, Line Security Level I**
* **UL 294, Endurance Level IV**
* **UL 294, Standby Power Level II**
* **UL 294, Single Point Locking Device with Key Locks: N/A**
=== WEB RESEARCH: security center ===
# Genetec Security Center Access Control - Comprehensive Technical Reference
## Manufacturer and Product Name
**Manufacturer:** Genetec Inc.
**Product:** Security Center (specifically Synergis Access Control)
## 1. Synergis Master Controller (SMC) Configuration Guide 2.1
### 1.1 Introduction to Synergis Master Controller
**What is Synergis Master Controller?**
Synergis Master Controller (SMC) is Genetec’s access control unit that supports a variety of third-party interface modules over IP, USB, and RS-485. SMC is seamlessly integrated to Security Center, and is capable of making the access control decisions independently of the Access Manager. SMC and accessories can be housed inside an enclosure that make up the Synergis access control system.
**Components:**
* **Controller module:** Processing component of SMC with IP capability, pre-loaded with the controller firmware and a web-based administration tool, Controller Portal.
* **Four-port RS-485 module:** RS-485 communication component of SMC with four ports (or channels) named A, B, C, and D. The number of interface modules you can connect to each channel depends on the type of hardware you have. In configurations where interface modules only use IP or USB connections, the Four-port RS-485 module is not needed.
### 1.2 Getting started with Controller Portal
**What is Controller Portal?**
Controller Portal is the web-based interface for the configuration and maintenance of SMC. It allows you to connect to an SMC unit using a web browser.
**Controller Portal tasks:**
* Change the security password required to log on to the SMC unit.
* Configure the network settings on the SMC unit so it works on your system.
* Configure SMC to accept connections from specific Access Manager servers.
* Configure the properties of the interface modules attached to the SMC unit.
* Configure the access control behavior for SMC, in both online and offline modes.
* View the activity logs stored on the SMC unit.
* Test and diagnose the interface module connections to the SMC unit.
* View and export the SMC status and configuration.
* Upgrade the SMC firmware.
* Restart the SMC hardware or software.
* Update security clearance levels assigned to Security Center areas manually on the SMC unit when the connection to the Access Manager is lost.
**Tasks NOT performable with Controller Portal (use Config Tool instead):**
* Enable/disable the Mixed mode operation.
* Assign devices (input/output contacts, readers) to doors and zones.
* Configure individual door and zone properties.
* Configure Card and PIN readers so both the card and the PIN are required to grant access.
* Configure IO linking.
**Log on to SMC:**
* **SMC Hostname:** SMC followed by the controller’s MAC address (e.g., SMC0010F31A176A).
* **Default username:** admin
* **Default password:** softwire
* Only one user can be connected to SMC at any given time.
**To log on:**
1. (First time logon only) Connect the SMC’s LAN 1 connector to your LAN.
2. Open a web browser.
3. In the browser’s address bar, type `https://` followed by the SMC hostname or IP address (e.g., `https://SMC0010F31A176A`).
4. (New browser session only) If you opened a new browser session, you’ll get a certificate error message. Follow your browser’s on-screen instructions to continue to the website.
5. In the Synergis Master Controller - Logon page, select the interface language.
6. Enter the username and password, then click Log on. The Controller Portal - Home page appears.
**Change the logon password:**
1. Log on to SMC.
2. From the Controller Portal - Home page, click Users.
3. From the User configuration page, select the user you want to modify and click Change password.
4. In the Change password dialog box, enter the new password twice and click Apply.
**Controller Portal interface tour (Home page links):**
* **Home:** Returns to Home page.
* **Log off:** Logs you off from SMC and displays the Logon page.
* **About:** Shows the SMC firmware version and copyright information.
* **Help:** Opens the Synergis Master Controller Configuration Guide in a separate browser page.
* **Network:** Opens the network configuration page, which is where you configure the SMC unit to work on your network and the Access Manager it should obey to.
* **Logging:** Used to configure the event logging options for troubleshooting purposes.
* **Access control:** Used to configure the access control behavior that applies to all interface modules connected to the SMC unit.
* **Hardware:** Used to define the interface modules attached to the SMC unit.
* **Users:** Used to configure who has the rights to log on to SMC and change its configuration.
* **Lock pairing mode:** (Only applicable to Assa Abloy IP locks) Used to discover IP locks on the network.
* **Primitive key store:** (Only applicable to STid readers) Used to change the Signature and Encipherment keys used to communicate with the STid readers controlled by SMC.
* **Security clearance levels:** (For threat level management) Used to change the Security clearance assigned to areas when the connection between SMC and its Access Manager is lost.
* **Troubleshooting:** Used to generate troubleshooting reports by querying the event log saved on the SMC unit.
* **Download support logs:** (Only appears if Support logs are enabled) Used to download support logs to help Genetec Technical Support troubleshoot your system.
* **IO diagnostics:** Shows the IO diagnostics page for this SMC unit. Use this page to watch the states of the contacts and readers change in real time as you perform tests with the devices connected to the interface modules.
* **System status:** Shows a snapshot of your unit and network status. You can also export the system information to a CSV file from this page.
* **Firmware upgrade:** Used to upgrade the SMC firmware or to revert it to the previous version (if available).
* **System restart:** Used to restart the SMC hardware or software.
### 1.3 SMC configuration
**Configuration prerequisites:**
* Read the Synergis Master Controller Release Notes.
* Computer with network card, Ethernet cable, and web browser.
* (Optional) IP address assigned by IT department to the SMC unit.
* Configure hardware settings (DIP switches, address dials, etc.) on interface modules.
* Connect interface modules to the SMC unit through proper communication channels.
* **NOTE:** All interface modules connected to the same RS-485 channel must be from the same manufacturer.
* Physical devices (REX, door sensors, etc.) should be connected.
* Download the latest SMC firmware from `https://gtap.genetec.com`.
* Install and configure Security Center with at least one Access Manager role.
**Configuration process overview:**
1. **Network Configuration:** Configure SMC’s network properties. If network does not support DHCP, IT must assign a new IP address. [See "Configure the SMC’s network properties" on page 13 of the original document]
2. **Firmware Upgrade:** Make sure you have the latest SMC firmware, and upgrade if necessary. [See "Check and upgrade the SMC firmware" on page 34 of the original document]
3. **Physical Connection:** Physically attach the interface modules to the controller module. [See Synergis Master Controller Hardware Installation Guide]
4. **Interface Module Configuration:** Establish communication between the SMC and its attached interface modules by configuring them in Controller Portal. [See "Configure the interface modules attached to SMC" on page 15 of the original document]
5. **Hardware Testing:** Test your hardware connections and configuration and make adjustments if necessary. [See "Test the interface modules attached to SMC" on page 19 of the original document]
6. **Access Control Behavior:** Configure the access control behavior you want SMC to exhibit. [See "Configure the unit-wide access control behavior" on page 21 of the original document]
7. **Event Logging (Optional):** Select the event logs you want to be available for troubleshooting. [See "Configure the event logging options" on page 24 of the original document]
8. **Enrollment in Security Center:** Add the SMC unit to an Access Manager so it becomes part of your Security Center system. [See "Enrolling the SMC unit in Security Center" on page 26 of the original document]
**Configure the SMC’s network properties:**
1. Log on to SMC.
2. From the Controller Portal - Home page, click Network, then Network properties.
3. Select the network interface used to connect the SMC unit to its Access Manager.
4. Configure the SMC unit’s IP address and the network properties.
* **IMPORTANT:** If the SMC is not on the same network segment as the Access Manager, then the SMC's IP address must be static, or the DHCP server must be configured to always assign the same IP address to the SMC.
5. Change the Discovery port if necessary (default is 2000).
6. Click Save. The controller firmware restarts.
**Configure the interface modules attached to SMC:**
An interface module is a third-party device that communicates with SMC over IP, USB, or RS-485, and provides input, output, and reader connections to the controller module.
1. Log on to SMC.
2. From the Controller Portal - Home page, click Hardware.
3. In the Hardware configuration page, click Add.
4. In the Add hardware dialog box, select the Hardware type, the Channel, and the rest of the interface module properties.
**Test the interface modules attached to SMC:**
1. Log on to SMC.
2. From the Controller Portal - Home page, click IO diagnostics.
3. In the IO diagnostics page, add the elements you wish to monitor.
4. Activate the devices (card readers, door sensors, door locks, etc.) attached to the SMC unit.
**Configure the unit-wide access control behavior:**
1. Log on to SMC.
2. From the Controller Portal - Home page, click Access control.
3. In the Access control page, select the options you want SMC to support:
* **Beep on door held open:** (Default=enabled) Reader beeps when door is held open too long.
* **Beep on door forced open:** (Default=enabled) Reader beeps when door is forced open.
* **Beep on access denied:** (Default=enabled) Reader beeps when access is denied.
* **Interlock single unlock:** (Default=disabled) Allows only one door to be unlocked at any given time in an interlock system.
* **Do not generate ‘Door open too long’ events when door is unrestricted:** (Default=disabled) Ignores Door open too long events when door is unlocked for maintenance or by schedule.
* **Card or PIN:** (Default=Card only) Allows either card or PIN for access. To enforce Card and PIN, configure in Config Tool.
* **Degraded mode (Mercury, VertX):** For Mercury and HID VertX interface modules. In degraded mode, the interface module makes decisions on its own when connection to SMC is lost, unlocking doors for all credentials matching specified Facility code (26 bits card format only).
* **Lock relay:**
* **After door opened:** Keep door unlocked for a certain delay after it opens.
* **When door closed:** Immediately lock the door after it closes.
4. Click Save.
**Configure the event logging options:**
SMC can keep detailed logs of all access control decisions it makes in the troubleshooting logs. These logs are off by default.
1. Log on to SMC.
2. From the Controller Portal - Home page, click Logging.
3. In the Logging page, select the types of events you wish to log.
4. Enable Support logs only when instructed by Genetec Technical Support.
5. Enable Activity events for the Troubleshooting report. Activity events that can be logged:
* **Reader activity:** All reader events (card read, PIN entered, mode change).
* **Input activity:** All input state changes.
* **Output activity:** All output state changes.
* **Access granted reasons:** All access granted events and reasons.
* **Access denied reasons:** All access denied events and reasons.
* **IO linking:** All IO linking events related to hardware zones.
* **Security clearance:** All changes to security clearance due to threat level activation/deactivation.
6. Click Save.
**Enrolling the SMC unit in Security Center:**
To enroll an SMC unit, you must assign it to an Access Manager.
**Enable the Access Manager to connect to the SMC units:**
1. Log on to Security Center with Config Tool.
2. Open the Access control task and select the Roles and units view.
3. Select the Access Manager role and select the Extensions tab.
4. Under the extension list, click Add an item.
5. In the Add extension dialog box, select SMC, and click Add.
6. In the extension list, select the SMC extension.
7. Under the list of Discovery ports, click Add an item.
8. In the Discovery port dialog box, enter the port number configured on the SMC units (default is 2000).
9. Click Create, then click Apply.
**Change the discovery port on SMC:**
1. Log on to SMC.
2. From the Controller Portal - Home page, click Networks, then Network properties.
3. Set the Discovery port to the value used by the Access Manager.
4. Click Save.
**About automatic discovery:**
New IP units on the network are automatically added to Security Center if:
* The SMC unit is using DHCP.
* The SMC unit has never been connected to any Access Manager before.
* The SMC unit and the Access Manager use the same discovery port.
* The SMC unit and the Access Manager are on the same network segment.
* The SMC unit is using the default logon username and password (admin/softwire).
**Add the SMC unit to an Access Manager manually:**
1. Log on to Security Center with Config Tool.
2. Open the Access control task and select the Roles and units view.
3. Select the Access Manager role, and click Add an entity.
4. In the menu that appears, select Access control unit.
5. In the unit creation dialog box, click Unit type and select SMC.
6. In the Network endpoint group, enter the SMC unit’s hostname or IP address, as well as the logon username and password (default: admin/softwire).
7. Click Next and select the partition the SMC unit should belong to.
8. Click Next and click Create.
9. Wait to see that the unit is successfully created and click Close.
10. Click Refresh.
### 1.4 Maintenance and troubleshooting
**Log on to SMC using the alternate IP address:**
If you are unable to connect to SMC using its hostname and you haven’t yet configured its IP address, you can use the alternate IP address.
**Check and upgrade the SMC firmware:**
1. Log on to SMC.
2. From the Controller Portal - Home page, click Firmware upgrade. The current firmware version is indicated.
3. If an upgrade is necessary, click Select upgrade file.
4. Select the firmware file (release_2.1_xxxx.yy.smc).
5. Click Open. SMC restarts.
**Generate troubleshooting reports:**
1. Log on to SMC.
2. From the Controller Portal - Home page, click Troubleshooting.
3. In the Troubleshooting page, set the Query filters:
* **Date and time:** Filter based on a time range.
* **Severity:** Filter on the event severity level (Information, Warning, Error).
* **Source:** Search for text in Physical source or Logical source.
* **Type:** Filter on the event type (Activity, System, Audit).
* **User:** Filter on the user who generated the event.
* **Message:** Search for text in the event message.
4. Click Generate. The troubleshooting report is displayed.
**Troubleshooting Report Event Severity Levels:**
* **Information:** Useful information unrelated to any critical situation that could help understand the context of another problem. All optional activity events are logged as information.
* **Warning:** Non-critical situation that may lead to more serious problems if left unattended.
* **Error:** Critical situation that needs immediate attention.
## 2. Security Center Administrator Guide 5.6
### 2.1 Security Center Architecture Overview
Security Center is a unified security platform that seamlessly blends IP security systems within a single interface. It is designed to simplify operations and enhance situational awareness.
**Key Components:**
* **Directory:** The central server that manages all Security Center entities, configurations, and user permissions.
* **Access Manager:** A role within Security Center responsible for managing access control units and processing access requests.
* **Client Applications:** Software used by operators to interact with Security Center, such as Security Desk and Config Tool.
* **Access Control Units:** Hardware devices (like Synergis Master Controllers or Synergis Cloud Links) that physically control doors, readers, and other access control peripherals.
### 2.2 How Security Center is Organized
Security Center organizes entities in a hierarchical structure to facilitate management and configuration.
**Key Organizational Concepts:**
* **Areas:** Logical groupings of doors and other security devices, often corresponding to physical locations within a facility.
* **Doors:** Represents physical access points, configured with readers, locks, and sensors.
* **Access Rules:** Define who can access which areas and at what times.
* **Cardholders:** Represents individuals with access credentials.
### 2.3 Hardware Zones, Virtual Zones, and I/O Zones
**Hardware Zone:** A zone entity in which the I/O linking is executed by a single access control unit. Works independently of the Access Manager. Cannot be armed or disarmed from Security Desk or by software command.
**Virtual Zone:** A zone entity in which the I/O linking is executed by the Access Manager. Requires constant communication with the Access Manager. Can be armed or disarmed from Security Desk or by software command.
**I/O Zone:** A zone entity that combines inputs and outputs from various access control units, allowing for complex logic and automation. Can be armed or disarmed from Security Desk or by software command.
## 3. Synergis Cloud Link Datasheet
### 3.1 Product Range and Model Numbers
**Synergis Cloud Link (SY-CLOUDLINK):** An intelligent and PoE-enabled access control appliance that supports a variety of third-party interface modules over IP and RS-485.
**Synergis Cloud Link 312 (SY-CLOUDLINK-312):** An expansion module for the Synergis Cloud Link, providing additional RS-485 ports for connecting more interface modules.
### 3.2 Technical Specifications
**Processor:** 4 GB RAM, 16 GB flash storage
**Network Interfaces:** Two Gigabit Ethernet ports
**On-board Inputs:** Four configurable inputs
**Security:** EAL6+ secure element, secure boot, TLS 1.3
**Power:** PoE (Power over Ethernet) or 12 VDC external power supply
**Dimensions:** (Refer to datasheet for exact dimensions)
**Weight:** (Refer to datasheet for exact weight)
**Operating Temperature:** (Refer to datasheet for exact range)
**Operating Humidity:** (Refer to datasheet for exact range)
**Warranty:** 24 months
**Certifications:** CE, UK, FCC, KC, ACMA, BIS, UL294, RoHS, REACH, WEEE
**Capacity:**
* Up to 256 readers/locks
* 600,000 cardholders
* 5,000,000 offline events
**Supported Downstream Devices:**
* Mercury controllers
* ASSA ABLOY wireless locks
* Allegion wireless locks
* SimonsVoss wireless locks
* Various I/O panels
## 4. Synergis Cloud Link Hardware Installation Guide 3.0
### 4.1 What is Synergis Cloud Link?
Synergis™ Cloud Link is an intelligent and PoE-enabled access control appliance of Genetec Inc. that supports a variety of third-party interface modules over IP and RS-485. Synergis™ Cloud Link is seamlessly integrated with Security Center and is capable of making access control decisions independently of the Access Manager. Synergis™ Cloud Link and accessories can be housed inside an enclosure that are part of a Synergis™ IP access control system.
**Hardware Features:**
* **RS-485:** Four embedded RS-485 communication ports (or channels) named A, B, C, and D. The number of interface modules you can connect to each channel depends on the type of hardware you have. When starting an RS-485 bus from the Synergis™ Cloud Link for HID module communication, you must set the associated termination DIP switch to ON. You must also set the termination jumper on the last connected module on the RS-485 bus.
* **USB1 and USB2:** For maintenance use only. Not evaluated by UL.
* **LAN1 and LAN2:** Two Ethernet LAN ports for connection to the IP network. Synergis™ Cloud Link can be powered using an Ethernet connection (PoE). Connecting to Security Center through the LAN 2 port has not been evaluated by UL and is for supplementary use only.
### 4.2 DIP Switch Command Codes for Synergis Cloud Link
You can use the DIP switches on the Synergis™ Cloud Link to run hardware commands. There are four DIP switches labelled 1 to 4. To run a command, set the DIP switches as indicated in the table below and press the EC button for one second. If the code is valid, the status LEDs will flash green for the process of the command, otherwise they flash red for one second. Synergis™ Cloud Link automatically performs a software restart after you have run a command.
**BEST PRACTICE:** To prevent an accidental configuration reset, always set the DIP switches back to ON ON ON ON after running a command.
| S1 | S2 | S3 | S4 | Command Description |
|---|---|---|---|---|
| OFF | OFF | OFF | OFF | Resets the Synergis™ Appliance Portal logon password to factory default (softwire). |
| ON | OFF | OFF | OFF | Resets all settings to factory default. This command has the following effects:
* Resets the Synergis™ Appliance Portal logon password to factory default (softwire).
* Resets the network addressing mode to DHCP.
* Resets the discovery port to 2000.
* Deletes all hardware (connected interface modules) configurations.
* Deletes all cardholder (credentials and access rules) configurations.
* Resets all unit-wide settings.
* Clears all logging options.
* **NOTE:** The unit firmware is not affected by this command. |
### 4.3 Wiring Guidelines for Synergis Enclosures
When connecting modules in a Synergis™ enclosure, use the wire gauges recommended by Genetec Inc. For UL installations, all wiring shall be UL certified Appliance Wiring Material (AWM).
**Recommended Wire Gauges:**
| Function | Specification |
|---|---|
| Readers | ALPHA 1299C, 22 AWG, 9-conductor, stranded, overall shield or equivalent 22AWG or 24AWG shielded multi-conductor cable. NOTE: Fewer conductors needed if not all control lines are used. |
| RS-485 | Belden 3105A or 9841 shielded cable or equivalent 22 AWG (maximum length of 4000 ft (1219 m)) or 24 AWG (maximum length of 2500 ft (762 m)) shielded communications cable with a characteristic impedance of 120 ohm. |
| 12 Volt (Power supply to fuse assembly) | 16 AWG |
| Ground (Power supply to fuse assembly) | 16 AWG |
| 12 Volt (Fuse assembly to Synergis™ Cloud Link and interface modules) | 20 AWG |
| Ground (Fuse assembly to Synergis™ Cloud Link and interface modules) | 20 AWG |
**NOTE:** For UL installations, the use of shielded cable for RS-485 and readers is required for UL 294 and ULC-S319 compliance.
### 4.4 Wiring Diagrams
* **Synergis wiring diagram: 4 HID modules with Synergis Cloud Link, fuse assembly, and power supply**
* **Synergis wiring diagram: 6 HID modules with fuse assembly**
* **Synergis wiring diagram: 3 Mercury modules with Mercury controller, Synergis Cloud Link, fuse assembly, and power supply**
* **Synergis wiring diagram: 5 Mercury modules with Mercury controller and fuse assembly**
* **Synergis wiring diagram: 2 HID modules with Synergis Cloud Link, fuse assembly, and power supply**
* **Synergis wiring diagram: 4 HID modules with fuse assembly**
* **Synergis wiring diagram: 1 Mercury module with Mercury controller, Synergis Cloud Link, fuse assembly, and power supply**
* **Synergis wiring diagram: 3 Mercury modules with Mercury controller and fuse assembly**
## 5. Synergis™ IX Programming Reference Manual
### 5.1 Controller Models, System Expansion and Capacities, and Technical Specifications
**Controller Models:**
* **SY-SIX-CTRL-DIN:** Synergis IX DIN rail mount controller.
* **SY-SIX-CTRL-DIN-1D:** Synergis IX DIN rail mount controller with 1 door capacity.
**System Expansion and Capacities:**
* Supports various expander modules for inputs, outputs, and readers.
* Specific capacities depend on the type and number of expander modules connected.
**Technical Specifications:**
* **Power Input:** 12-24 VDC
* **Current Draw:** (Refer to manual for specific current draw based on configuration)
* **Operating Temperature:** (Refer to manual for specific range)
* **Communication:** RS-485, Ethernet
* **Memory:** (Refer to manual for memory specifications)
### 5.2 Default Codes
**Default Installer Code:** 1234
**Password Policy for Synergis IX Web Interface:**
* Default username: `admin`
* Default password: `softwire`
* Password must be changed upon first login.
* Strong password policies are enforced.
### 5.3 Fault/Event/Alarm Code Tables
### Error Code Display
The following table is valid if the fault indicator is constantly on and the status indicator is flashing red. If the fault indicator is flashing, the module requires a firmware update or is currently in firmware update mode. The status indicator will flash red with the error code number. The error code number is shown with a 250ms on and off period (duty cycle) with a delay of 1.5 seconds between each display cycle.
| Flash | Error Description |
|---|---|
| 1 | **Unknown Error Code:** The error code returned by the system controller could not be understood by the module. |
| 2 | **Firmware Version:** The firmware version on the module is not compatible with the system controller. To clear this error, update the module using the module update feature in the controller's web interface. |
| 3 | **Address Too High:** The module address is above the maximum number available on the system controller. To clear this error change the address to one within the range set on the system controller, restart the module by disconnecting the power. |
| 4 | **Address In Use:** The address is already in use by another module. To clear this error set the address to one that is not currently occupied. Use the view network status command to list the attached devices, or the network update command to refresh the registered device list. |
| 5 | **Controller Secured Registration Not Allowed:** The controller is not accepting any module registrations. To allow module registrations use the network secure command to change the setting to not secured. |
| 6 | **Serial Number Fault:** The serial number in the device is not valid. Return the unit to the distributor for replacement. |
| 7 | **Locked Device:** The module or system controller is a locked device and cannot communicate on the network. Return the unit to the distributor for replacement. |
### Trouble Inputs (Fault Codes)
Trouble inputs are used to monitor the status of the controller and in most cases are not physically connected to an external input. These can then be used to report a message to a monitoring station, remote computer, keypad or siren.
| Input Number | Description |
|---|---|
| CP001:02 | 12V Supply Failure |
| CP001:04 | Real Time Clock Not Set |
| CP001:05 | Service Test Report |
| CP001:06 | ContactID Reporting Failure |
| CP001:07 | Phone Line Fault |
| CP001:08 | Auxiliary Fuse / Supply Fault |
| CP001:09 | Bell Siren Tamper / Cut |
| CP001:11 | Bell Siren Current Overload |
| CP001:13 | Module Communication Fault |
| CP001:14 | Module Security Violation |
| CP001:20 | Report IP Reporting Failure |
| CP001:24 | Installer Logged In |
| CP001:29 | System Restarted |
### 5.4 Programming Menu Structure
The Programming Menu provides access to various configuration options for the Synergis™ IX system. Below is an outline of the menu structure and key sub-sections:
### Doors
* **Door Groups**
* **Inputs**
* Inputs | Areas and Input Types
* Inputs | Options
* **Door Types**
* **Input Types**
* Input Types | Options 1
* Input Types | Options 2
* Input Types | Options 3
* Input Types | Options 4
### Areas
* **Areas | Configuration**
* **Areas | Reporting Services**
* **Areas | Outputs**
* **Areas | Options 1**
* **Areas | Options 2**
* **Areas | Events**
* **Area Groups**
### Outputs
* **Outputs | Options**
* **Output Groups**
### Keypad Groups
### Menu Groups
* **Menu Groups | Keypad Groups**
* **Menu Groups | Options**
### Trouble Inputs
* **Trouble Inputs | Areas And Input Types**
* **Trouble Inputs | Options**
### Elevators
### Phone Numbers
### Services
* **Contact ID**
* **Report IP**
### Scheduling Menu
* **Time**
* **Daylight Savings**
### 5.5 Expander/Peripheral Devices with Specs
### Keypads
* **Keypads | Configuration**
* **Keypads | Options 1**
* **Keypads | Options 2**
### Analog Expanders
* **Analog Expanders | Channel 1-4**
### Input Expanders
### Output Expanders
### Reader Expanders
* **OSDP Install Mode**
* **Reader Expanders | Reader 1-2**
* **Reader Expanders | Reader 1-2 Options**
### Smart Readers
* **Smart Readers | Reader Expander Addressing**
### 5.6 Common Fault Diagnosis
### Common Health Status Messages
* **Modules that Require a Restart:** Indicates that certain modules need to be restarted for proper operation.
* **Modules that are Offline:** Indicates that some modules are not communicating with the system.
* **Areas Requiring Rearming due to Input Changes:** Suggests that areas need to be re-armed after changes to inputs.
* **Areas with the Tamper Area Disarmed:** Indicates a tamper condition in an area that is disarmed.
* **Inputs Assigned an Area but no Input Type:** Highlights an configuration error where an input is assigned to an area but lacks a defined input type.
## 6. Compliance Standards Met (from Synergis Cloud Link Hardware Installation Guide 3.0)
UL-listed equipment and subassemblies are compliant to the following standards and levels:
* **ULC S319 System Class I**
* **UL 294, Destructive Attack Level I**
* **UL 294, Line Security Level I**
* **UL 294, Endurance Level IV**
* **UL 294, Standby Power Level II**
* **UL 294, Single Point Locking Device with Key Locks: N/A**
| Technology | Security Level | Notes | Recommendation |
|---|---|---|---|
| HID Prox (125kHz) | Low | Legacy — easily cloned | Upgrade to iCLASS SE or SEOS |
| EM4100 (125kHz) | Very Low | No encryption — easily cloned | Replace with modern technology |
| MIFARE Classic | Low–Medium | Known vulnerabilities | Upgrade to MIFARE DESFire or iCLASS SE |
| MIFARE DESFire EV2 | High | AES-128 encryption | Suitable for most commercial applications |
| iCLASS SE | High | AES-128, mutual authentication | Recommended for commercial/industrial |
| SEOS | Very High | PKI, mobile credentials supported | Recommended for high-security sites |
| Format | Structure | Use Case |
|---|---|---|
| 26-bit H10301 | 3-byte facility code + 16-bit card number | Most common — default for most panels |
| 34-bit H10306 | 16-bit facility code + 16-bit card number | Larger card number range |
| 37-bit H10304 | 16-bit facility code + 19-bit card number | Large deployments |
| Corporate 1000 | 35-bit — HID proprietary | High-security HID deployments |
| OSDP | Serial protocol — not Wiegand | Required for SEOS and encrypted comms |
| Code / Display | Description | Likely Cause | Action |
|---|---|---|---|
| No LED / No Power | Reader not powering up | Wiring fault, power supply fault | Check power wiring. Verify supply voltage (10.5–16V DC for most HID readers). |
| Card Not Read | Reader does not respond to card | Wrong card format, reader misconfigured | Check card format matches reader configuration. Test with known-good card. |
| Red LED — Access Denied | Card read but access denied | Access level, panel configuration | Check access level in panel software. Verify card number is enrolled correctly. |
| Wiegand Data Error | Panel not receiving Wiegand data | Wiring fault, cable length, interference | Check D0/D1 wiring. Reduce cable length. Use screened cable. |
| OSDP Fault | OSDP communication error | RS-485 bus fault, address conflict | Check RS-485 wiring. Verify OSDP address. Check bus termination. |
| Tamper Alarm | Reader tamper activated | Reader removed from wall, tamper switch fault | Check reader mounting. Inspect tamper switch. |
| Terminal | Function | Notes |
|---|---|---|
| Red | +12V DC | Power supply (10.5–16V DC) |
| Black | 0V / Ground | Common ground |
| Green | D0 (Wiegand Data 0) | Wiegand data line 0 |
| White | D1 (Wiegand Data 1) | Wiegand data line 1 |
| Orange | LED Control | Optional — LED override from controller |
| Blue | Buzzer Control | Optional — buzzer override from controller |
| Brown | Tamper | Anti-tamper switch (normally closed) |
| Terminal | Function | Notes |
|---|---|---|
| Red | +12V DC | Power supply |
| Black | 0V / Ground | Common ground |
| Yellow | RS-485 A (Data+) | OSDP data positive |
| Blue | RS-485 B (Data−) | OSDP data negative |
| Brown | Tamper | Anti-tamper switch |
=== WEB RESEARCH: hid === # HID VertX EVO iCLASS SE Access Control Technical Reference ## 1. Product Range and Model Numbers - VertX EVO V2000 (Reader Interface / Access Controller) - VertX EVO V1000 (Access Controller) - iCLASS SE Readers: - R10 / 900N (Mini-Mullion) - R15 / 910N (Mullion) - R40 / 920N (Wall Switch) - RK40 / 921N (Wall Switch with Keypad) - R90 / 940N (Long Range) ## 2. Technical Specifications ### VertX EVO V2000 / V1000 - Power Supply Input: 12-24VDC - Maximum Current at 12-24VDC per Unit: 1 Amp - Average Operating Current at 12VDC: 625mA (V2000 with two R40 iCLASS Readers), 210mA (V1000) - Reader Power Output (V2000): 12VDC, 250mA each - Relay Outputs (V2000): 30VDC, 2Amp, resistive - Operating Temperature Range: 32°-120°F (0°- 49°C) - Humidity: 5% to 85% non-condensing ### iCLASS SE Readers - Typical Read Range: - iCLASS Seos: 1.2" - 3.9" (3 - 10 cm) depending on model - iCLASS: 2.8" - 5.5" (7 - 14 cm) depending on model - MIFARE Classic: 2.8" - 4.3" (7 - 11 cm) depending on model - MIFARE DESFire EV1: 1.2" - 2.0" (3 - 5 cm) depending on model - Operating Voltage: 5-16 VDC, Linear supply recommended - Current Draw (Standard Power Mode): 60mA - 160mA depending on model - Current Draw (Intelligent Power Management Mode): 35mA - 75mA depending on model - Peak Current Draw: 200mA - 250mA depending on model - Operating Temperature: -31º to 150º F (-35º to 65º C) - Storage Temperature: -67º to 185º F (-55º to 85º C) - Operating Humidity: 5% to 95% relative humidity non-condensing - Environmental Rating: IP55 - Transmit Frequency: 13.56 MHz - Communications: Wiegand, Clock-and-Data, OSDP via RS485 ## 3. Default Codes - Configuration GUI Login User name: admin - Configuration GUI Login Password: (empty by default, must be changed on first login) - Password rules: 6 to 10 characters long, printable ASCII characters from 32 to 126 (decimal) inclusive. - Default IP Address (Virtual Port): 169.254.242.121 ## 4. Wiring Diagrams and Terminal Descriptions ### Cable Specifications - Input Circuits: 500 feet (150 m), 2-conductor, shielded, using ALPHA 1292C (22AWG) or Alpha 2421C (18AWG) - Output Circuits: 500 feet (150 m), 2-conductor, using ALPHA 1172C (22AWG) or Alpha 1897C (18AWG) - Wiegand: 500 feet (150 m) to reader, ALPHA 1299C, 22AWG, 9-conductor, stranded, overall shield - Ethernet: 328 feet (100 m), Cat5, Cat5E, and Cat6 - RS-485 (V1000): 4000 feet (1220 m) to host, Belden 3105A, 22AWG twisted pair, shielded 100Ω cable ### V2000 Power and Alarm Input Connections (P7) - Pin 1: 12-24VDC - Pin 2: Ground - Pin 3: Bat Fail - - Pin 4: Bat Fail + - Pin 5: AC Fail - - Pin 6: AC Fail + - Pin 7: Tamper - - Pin 8: Tamper + ### V2000 Reader Connections (P1 / P4) - Pin 1: Reader Power / Shield Ground - Pin 2: Ground / Hold - Pin 3: Data 0 / Data / Beeper - Pin 4: Data 1 / Clock / Red LED - Pin 5: Data Return / Green LED - Pin 6: Green LED / Data Return - Pin 7: Red LED / Data 1 / Clock - Pin 8: Beeper / Data 0 / Data - Pin 9: Hold / Ground - Pin 10: Shield Ground / Reader Power ### V2000 Output Connections - Output 1: P3 Pins 1/2/3 - Strike(lock) Relay 1 (NO/C/NC) - Output 2: P3 Pins 4/5/6 - Aux Relay 1 (NO/C/NC) - Output 3: P6 Pins 6/5/4 - Strike (lock) Relay 2 (NO/C/NC) - Output 4: P6 Pins 3/2/1 - Aux Relay 2 (NO/C/NC) ### V2000 Input Connections - Input 1: P2 Pins 1/2 - Door Monitor - Input 2: P2 Pins 3/4 - REX input - Input 3: P5 Pins 4/3 - Door Monitor - Input 4: P5 Pins 2/1 - Rex Input - Input 5: P7 Pins 8/7 - Tamper - Input 6: P7 Pins 6/5 - AC Fail - Input 7: P7 Pins 4/3 - Batt Fail ## 5. Zone Types and Descriptions - Door Monitor: Default configuration is Normally Closed (NC), unsupervised (no EOL resistors). For UL1076 installations, all inputs must be supervised. - Request-to-Exit (REX): Default configuration is Normally Open (NO) unsupervised (no EOL resistors). - Tamper: Input for tamper switch on the enclosure. - AC Fail: Input for AC failure contacts provided on the power supply. - Batt Fail: Input for battery low/failure contacts provided on the power supply. - Supervised inputs can be configured for supervisory resistors of 1K – 6K Ohm. ## 6. Commissioning Steps 1. Connect the VertX EVO controller to the network using a standard Cat5 network patch cable. 2. Connect power by providing appropriate DC input to the P7 connector. 3. Connect Wiegand or clock-and-data interfaces to the reader. 4. Connect output and input connections as required. 5. Contact the VertX controller using the HID Discovery Application (for DHCP Networks) or Virtual Port (169.254.242.121). 6. Access the Configuration GUI using a web browser. 7. Login with User name: admin and leave the Password field empty. 8. Change the password on the first login. 9. Configure Basic Network Setup (DHCP or Static TCP/IP). 10. Configure Host Communication Setup (Host Name, Here I Am Interval). 11. Submit and confirm changes. 12. Use System Status to validate the installation, field wiring, and installed devices. 13. Use Supplemental Configuration to configure system inputs and outputs. ## 7. Common Fault Diagnosis - Network Defaults Jumper: Place a jumper over pins 3 & 5 of the Debug port while the controller is rebooting to reset network settings to factory defaults. The Power LED flashes green five times indicating success, or red five times indicating an error. - Firewall Ports: Ensure connection_port (4070) TCP outbound and listen_port (4050) TCP incoming are open on the firewall. - Update System: If a firmware download fails, view a tool tip with the error status code by hovering the mouse over the image in the Update System window. ## 8. Compliance Standards Met - UL294/cUL (US), CSA C22.2 No. 205 (Canada) - FCC Certification (US), IC (Canada), CE (EU), C-tick (Australia, New Zealand), SRRC (Australia, New Zealand), MIC (Korea), NCC (Taiwan), iDA (Singapore), RoHS - FIPS 201 Transparent Reader - IPv4/v6, CE Mark, RoHS, WEEE, REACH === WEB RESEARCH: vertx === # HID VertX EVO iCLASS SE Access Control Technical Reference ## 1. Product Range and Model Numbers - VertX EVO V2000 (Reader Interface / Access Controller) - VertX EVO V1000 (Access Controller) - iCLASS SE Readers: - R10 / 900N (Mini-Mullion) - R15 / 910N (Mullion) - R40 / 920N (Wall Switch) - RK40 / 921N (Wall Switch with Keypad) - R90 / 940N (Long Range) ## 2. Technical Specifications ### VertX EVO V2000 / V1000 - Power Supply Input: 12-24VDC - Maximum Current at 12-24VDC per Unit: 1 Amp - Average Operating Current at 12VDC: 625mA (V2000 with two R40 iCLASS Readers), 210mA (V1000) - Reader Power Output (V2000): 12VDC, 250mA each - Relay Outputs (V2000): 30VDC, 2Amp, resistive - Operating Temperature Range: 32°-120°F (0°- 49°C) - Humidity: 5% to 85% non-condensing ### iCLASS SE Readers - Typical Read Range: - iCLASS Seos: 1.2" - 3.9" (3 - 10 cm) depending on model - iCLASS: 2.8" - 5.5" (7 - 14 cm) depending on model - MIFARE Classic: 2.8" - 4.3" (7 - 11 cm) depending on model - MIFARE DESFire EV1: 1.2" - 2.0" (3 - 5 cm) depending on model - Operating Voltage: 5-16 VDC, Linear supply recommended - Current Draw (Standard Power Mode): 60mA - 160mA depending on model - Current Draw (Intelligent Power Management Mode): 35mA - 75mA depending on model - Peak Current Draw: 200mA - 250mA depending on model - Operating Temperature: -31º to 150º F (-35º to 65º C) - Storage Temperature: -67º to 185º F (-55º to 85º C) - Operating Humidity: 5% to 95% relative humidity non-condensing - Environmental Rating: IP55 - Transmit Frequency: 13.56 MHz - Communications: Wiegand, Clock-and-Data, OSDP via RS485 ## 3. Default Codes - Configuration GUI Login User name: admin - Configuration GUI Login Password: (empty by default, must be changed on first login) - Password rules: 6 to 10 characters long, printable ASCII characters from 32 to 126 (decimal) inclusive. - Default IP Address (Virtual Port): 169.254.242.121 ## 4. Wiring Diagrams and Terminal Descriptions ### Cable Specifications - Input Circuits: 500 feet (150 m), 2-conductor, shielded, using ALPHA 1292C (22AWG) or Alpha 2421C (18AWG) - Output Circuits: 500 feet (150 m), 2-conductor, using ALPHA 1172C (22AWG) or Alpha 1897C (18AWG) - Wiegand: 500 feet (150 m) to reader, ALPHA 1299C, 22AWG, 9-conductor, stranded, overall shield - Ethernet: 328 feet (100 m), Cat5, Cat5E, and Cat6 - RS-485 (V1000): 4000 feet (1220 m) to host, Belden 3105A, 22AWG twisted pair, shielded 100Ω cable ### V2000 Power and Alarm Input Connections (P7) - Pin 1: 12-24VDC - Pin 2: Ground - Pin 3: Bat Fail - - Pin 4: Bat Fail + - Pin 5: AC Fail - - Pin 6: AC Fail + - Pin 7: Tamper - - Pin 8: Tamper + ### V2000 Reader Connections (P1 / P4) - Pin 1: Reader Power / Shield Ground - Pin 2: Ground / Hold - Pin 3: Data 0 / Data / Beeper - Pin 4: Data 1 / Clock / Red LED - Pin 5: Data Return / Green LED - Pin 6: Green LED / Data Return - Pin 7: Red LED / Data 1 / Clock - Pin 8: Beeper / Data 0 / Data - Pin 9: Hold / Ground - Pin 10: Shield Ground / Reader Power ### V2000 Output Connections - Output 1: P3 Pins 1/2/3 - Strike(lock) Relay 1 (NO/C/NC) - Output 2: P3 Pins 4/5/6 - Aux Relay 1 (NO/C/NC) - Output 3: P6 Pins 6/5/4 - Strike (lock) Relay 2 (NO/C/NC) - Output 4: P6 Pins 3/2/1 - Aux Relay 2 (NO/C/NC) ### V2000 Input Connections - Input 1: P2 Pins 1/2 - Door Monitor - Input 2: P2 Pins 3/4 - REX input - Input 3: P5 Pins 4/3 - Door Monitor - Input 4: P5 Pins 2/1 - Rex Input - Input 5: P7 Pins 8/7 - Tamper - Input 6: P7 Pins 6/5 - AC Fail - Input 7: P7 Pins 4/3 - Batt Fail ## 5. Zone Types and Descriptions - Door Monitor: Default configuration is Normally Closed (NC), unsupervised (no EOL resistors). For UL1076 installations, all inputs must be supervised. - Request-to-Exit (REX): Default configuration is Normally Open (NO) unsupervised (no EOL resistors). - Tamper: Input for tamper switch on the enclosure. - AC Fail: Input for AC failure contacts provided on the power supply. - Batt Fail: Input for battery low/failure contacts provided on the power supply. - Supervised inputs can be configured for supervisory resistors of 1K – 6K Ohm. ## 6. Commissioning Steps 1. Connect the VertX EVO controller to the network using a standard Cat5 network patch cable. 2. Connect power by providing appropriate DC input to the P7 connector. 3. Connect Wiegand or clock-and-data interfaces to the reader. 4. Connect output and input connections as required. 5. Contact the VertX controller using the HID Discovery Application (for DHCP Networks) or Virtual Port (169.254.242.121). 6. Access the Configuration GUI using a web browser. 7. Login with User name: admin and leave the Password field empty. 8. Change the password on the first login. 9. Configure Basic Network Setup (DHCP or Static TCP/IP). 10. Configure Host Communication Setup (Host Name, Here I Am Interval). 11. Submit and confirm changes. 12. Use System Status to validate the installation, field wiring, and installed devices. 13. Use Supplemental Configuration to configure system inputs and outputs. ## 7. Common Fault Diagnosis - Network Defaults Jumper: Place a jumper over pins 3 & 5 of the Debug port while the controller is rebooting to reset network settings to factory defaults. The Power LED flashes green five times indicating success, or red five times indicating an error. - Firewall Ports: Ensure connection_port (4070) TCP outbound and listen_port (4050) TCP incoming are open on the firewall. - Update System: If a firmware download fails, view a tool tip with the error status code by hovering the mouse over the image in the Update System window. ## 8. Compliance Standards Met - UL294/cUL (US), CSA C22.2 No. 205 (Canada) - FCC Certification (US), IC (Canada), CE (EU), C-tick (Australia, New Zealand), SRRC (Australia, New Zealand), MIC (Korea), NCC (Taiwan), iDA (Singapore), RoHS - FIPS 201 Transparent Reader - IPv4/v6, CE Mark, RoHS, WEEE, REACH === WEB RESEARCH: iclass === # HID VertX EVO iCLASS SE Access Control Technical Reference ## 1. Product Range and Model Numbers - VertX EVO V2000 (Reader Interface / Access Controller) - VertX EVO V1000 (Access Controller) - iCLASS SE Readers: - R10 / 900N (Mini-Mullion) - R15 / 910N (Mullion) - R40 / 920N (Wall Switch) - RK40 / 921N (Wall Switch with Keypad) - R90 / 940N (Long Range) ## 2. Technical Specifications ### VertX EVO V2000 / V1000 - Power Supply Input: 12-24VDC - Maximum Current at 12-24VDC per Unit: 1 Amp - Average Operating Current at 12VDC: 625mA (V2000 with two R40 iCLASS Readers), 210mA (V1000) - Reader Power Output (V2000): 12VDC, 250mA each - Relay Outputs (V2000): 30VDC, 2Amp, resistive - Operating Temperature Range: 32°-120°F (0°- 49°C) - Humidity: 5% to 85% non-condensing ### iCLASS SE Readers - Typical Read Range: - iCLASS Seos: 1.2" - 3.9" (3 - 10 cm) depending on model - iCLASS: 2.8" - 5.5" (7 - 14 cm) depending on model - MIFARE Classic: 2.8" - 4.3" (7 - 11 cm) depending on model - MIFARE DESFire EV1: 1.2" - 2.0" (3 - 5 cm) depending on model - Operating Voltage: 5-16 VDC, Linear supply recommended - Current Draw (Standard Power Mode): 60mA - 160mA depending on model - Current Draw (Intelligent Power Management Mode): 35mA - 75mA depending on model - Peak Current Draw: 200mA - 250mA depending on model - Operating Temperature: -31º to 150º F (-35º to 65º C) - Storage Temperature: -67º to 185º F (-55º to 85º C) - Operating Humidity: 5% to 95% relative humidity non-condensing - Environmental Rating: IP55 - Transmit Frequency: 13.56 MHz - Communications: Wiegand, Clock-and-Data, OSDP via RS485 ## 3. Default Codes - Configuration GUI Login User name: admin - Configuration GUI Login Password: (empty by default, must be changed on first login) - Password rules: 6 to 10 characters long, printable ASCII characters from 32 to 126 (decimal) inclusive. - Default IP Address (Virtual Port): 169.254.242.121 ## 4. Wiring Diagrams and Terminal Descriptions ### Cable Specifications - Input Circuits: 500 feet (150 m), 2-conductor, shielded, using ALPHA 1292C (22AWG) or Alpha 2421C (18AWG) - Output Circuits: 500 feet (150 m), 2-conductor, using ALPHA 1172C (22AWG) or Alpha 1897C (18AWG) - Wiegand: 500 feet (150 m) to reader, ALPHA 1299C, 22AWG, 9-conductor, stranded, overall shield - Ethernet: 328 feet (100 m), Cat5, Cat5E, and Cat6 - RS-485 (V1000): 4000 feet (1220 m) to host, Belden 3105A, 22AWG twisted pair, shielded 100Ω cable ### V2000 Power and Alarm Input Connections (P7) - Pin 1: 12-24VDC - Pin 2: Ground - Pin 3: Bat Fail - - Pin 4: Bat Fail + - Pin 5: AC Fail - - Pin 6: AC Fail + - Pin 7: Tamper - - Pin 8: Tamper + ### V2000 Reader Connections (P1 / P4) - Pin 1: Reader Power / Shield Ground - Pin 2: Ground / Hold - Pin 3: Data 0 / Data / Beeper - Pin 4: Data 1 / Clock / Red LED - Pin 5: Data Return / Green LED - Pin 6: Green LED / Data Return - Pin 7: Red LED / Data 1 / Clock - Pin 8: Beeper / Data 0 / Data - Pin 9: Hold / Ground - Pin 10: Shield Ground / Reader Power ### V2000 Output Connections - Output 1: P3 Pins 1/2/3 - Strike(lock) Relay 1 (NO/C/NC) - Output 2: P3 Pins 4/5/6 - Aux Relay 1 (NO/C/NC) - Output 3: P6 Pins 6/5/4 - Strike (lock) Relay 2 (NO/C/NC) - Output 4: P6 Pins 3/2/1 - Aux Relay 2 (NO/C/NC) ### V2000 Input Connections - Input 1: P2 Pins 1/2 - Door Monitor - Input 2: P2 Pins 3/4 - REX input - Input 3: P5 Pins 4/3 - Door Monitor - Input 4: P5 Pins 2/1 - Rex Input - Input 5: P7 Pins 8/7 - Tamper - Input 6: P7 Pins 6/5 - AC Fail - Input 7: P7 Pins 4/3 - Batt Fail ## 5. Zone Types and Descriptions - Door Monitor: Default configuration is Normally Closed (NC), unsupervised (no EOL resistors). For UL1076 installations, all inputs must be supervised. - Request-to-Exit (REX): Default configuration is Normally Open (NO) unsupervised (no EOL resistors). - Tamper: Input for tamper switch on the enclosure. - AC Fail: Input for AC failure contacts provided on the power supply. - Batt Fail: Input for battery low/failure contacts provided on the power supply. - Supervised inputs can be configured for supervisory resistors of 1K – 6K Ohm. ## 6. Commissioning Steps 1. Connect the VertX EVO controller to the network using a standard Cat5 network patch cable. 2. Connect power by providing appropriate DC input to the P7 connector. 3. Connect Wiegand or clock-and-data interfaces to the reader. 4. Connect output and input connections as required. 5. Contact the VertX controller using the HID Discovery Application (for DHCP Networks) or Virtual Port (169.254.242.121). 6. Access the Configuration GUI using a web browser. 7. Login with User name: admin and leave the Password field empty. 8. Change the password on the first login. 9. Configure Basic Network Setup (DHCP or Static TCP/IP). 10. Configure Host Communication Setup (Host Name, Here I Am Interval). 11. Submit and confirm changes. 12. Use System Status to validate the installation, field wiring, and installed devices. 13. Use Supplemental Configuration to configure system inputs and outputs. ## 7. Common Fault Diagnosis - Network Defaults Jumper: Place a jumper over pins 3 & 5 of the Debug port while the controller is rebooting to reset network settings to factory defaults. The Power LED flashes green five times indicating success, or red five times indicating an error. - Firewall Ports: Ensure connection_port (4070) TCP outbound and listen_port (4050) TCP incoming are open on the firewall. - Update System: If a firmware download fails, view a tool tip with the error status code by hovering the mouse over the image in the Update System window. ## 8. Compliance Standards Met - UL294/cUL (US), CSA C22.2 No. 205 (Canada) - FCC Certification (US), IC (Canada), CE (EU), C-tick (Australia, New Zealand), SRRC (Australia, New Zealand), MIC (Korea), NCC (Taiwan), iDA (Singapore), RoHS - FIPS 201 Transparent Reader - IPv4/v6, CE Mark, RoHS, WEEE, REACH === ADDITIONAL RESEARCH === HID Global Access Control Readers: iCLASS SE, OMNIKEY, Signo Technical Documentation 1. Complete fault/trouble code list with descriptions and remedies (From HID Reader Manager App User Guide Android PLT-03858 Rev D.2, pages 74-76) Error and Warning Messages: - "Reader connection failed": The app could not establish a Bluetooth connection with the reader. Remedy: Ensure the reader is powered on, within range, and Bluetooth is enabled on the mobile device. - "Firmware upgrade failed": The firmware upgrade process was interrupted or encountered an error. Remedy: Move closer to the reader, ensure stable power, and retry the upgrade. Use the "Resume Upgrade" option if available. - "Invalid Configuration ID": The entered Configuration ID is not recognized or is incompatible with the reader. Remedy: Verify the Configuration ID and try again. - "Template save failed": The app could not save the configuration template. Remedy: Check device storage and app permissions. - "Authorization Key error": The provided Authorization Key is invalid or expired. Remedy: Contact the HID Elite/MOB key administrator to issue a valid Key Authorization. - "Reader not supported": The connected reader does not support the attempted operation (e.g., firmware upgrade or specific configuration). Remedy: Verify reader compatibility in the documentation. - "NFC connection lost": The NFC connection was interrupted during an operation. Remedy: Keep the mobile device steady and close to the reader\'s NFC antenna until the operation completes. Information Messages: - "Firmware upgrade successful": The reader firmware was successfully updated. - "Configuration applied": The selected configuration settings were successfully applied to the reader. - "Template saved": The configuration template was successfully saved. Validation Messages: - "Invalid input": The entered value for a configuration parameter is outside the allowed range or format. Remedy: Correct the input value according to the parameter specifications. 2. All default engineer/installer codes and user codes - HID Signo readers use facility codes between 1-255, and no default is set. Once a facility code is entered, the reader LED displays violet, then solid red. - There are no default "engineer" or "installer" codes in the traditional alarm panel sense; configuration is managed via the HID Reader Manager app using Authorization Keys (HID Elite/MOB keys) or Standard Keys. 3. Complete zone type list with descriptions (Not applicable in the traditional alarm panel sense; readers are typically connected to access control panels which define zone types. The reader itself provides Wiegand or OSDP data to the panel.) 4. All output types and their functions - Wiegand Data0 / Data (Green wire) - Wiegand Data1 / Clock / RS485-A (White wire) - RS485-B (Wiegand Data0 wire reused for OSDP) - LED GRN (Orange wire): Controls the green LED indicator. - Beeper (Yellow wire): Controls the reader\'s beeper. - Hold / LED BLUE (Blue wire): Can be configured to hold the reader\'s output or control the blue LED. - LED RED (Brown wire): Controls the red LED indicator. - Tamper 1 & Tamper 2 (Violet & White/Red wires): Provide tamper switch status (normally closed or open-circuit depending on configuration). 5. Complete programming menu structure (every menu, submenu, parameter) (From HID Reader Manager App User Guide Android PLT-03858 Rev D.2, pages 43-71) - Credential Details configuration for Signo readers (p. 47) - Credential configuration for SE readers (p. 49) - Authorization Keys (p. 51) - Reader Settings configuration (p. 53) - ISO14443A UID Output Format (p. 53) - EM Proximity Output (p. 54) - CHUID Formats (p. 55) - Bluetooth Modes, Ranges & Power (p. 56) - Communication Protocol (p. 58) - Audio & Visual (p. 59) - Optional Settings (p. 60) - Keypad Settings (p. 61) - Wallet configuration (p. 62) - Apple Wallet configuration (p. 62) - Google Wallet configuration (p. 66) 6. Wiring specifications: every terminal, its function, voltage, current (From HID Signo Reader Installation Guide Rev A.3, page 3) Terminal / Wire Color / Function: 1 / Red / +VDC (12 VDC input) 2 / Black / Ground (RTN) 3 / White / Wiegand Data1 / Clock / RS485-A 4 / Green / Wiegand Data0 / Data / RS485-B 5 / Orange / LED GRN 6 / Yellow / Beeper 7 / Blue / Hold / LED BLUE 8 / Brown / LED RED 9 / Violet / Tamper 2 10 / White/Red / Tamper 1 Drain (Pigtail versions only) Current (Standby / Max / Peak at 12 VDC): - Signo 20: 60 mA / 70 mA / 250 mA - Signo 20K: 65 mA / 75 mA / 250 mA - Signo 40: 65 mA / 75 mA / 250 mA - Signo 40K: 70 mA / 80 mA / 250 mA 7. All supported detector/device types and their wiring - Supports Wiegand and OSDP (RS-485) access control panels. - Wiring for Wiegand: Data0 (Green), Data1 (White), Ground (Black). - Wiring for OSDP: RS485-A (White), RS485-B (Green), Ground (Black). Requires 120 ohm termination if at the end of the RS-485 bus. 8. System capacities: zones, users, outputs, areas, doors, readers - Reader capacity is determined by the connected access control panel. The reader itself does not store user databases or define zones/areas. 9. Communication protocols supported - Wiegand - OSDP (Open Supervised Device Protocol) via RS-485 - Bluetooth Low Energy (BLE) for mobile credentials and configuration - NFC (Near Field Communication) for mobile credentials and configuration 10. All LED/display indicators and their meanings - Violet, then solid red: Indicates a facility code has been entered (Signo keypad readers). - Green flash: Read confirmation. - Red/Green/Blue LEDs can be controlled via the respective input wires (Orange, Brown, Blue) by the access control panel. 11. Complete commissioning/installation procedure steps (From HID Signo Reader Installation Guide Rev A.3, page 4) 1. Securely mount the reader backplate to the wall or mullion. 2. Connect the wiring according to the specified Wiegand or OSDP configuration. 3. Attach the reader body to the backplate and secure it with the provided screw. 4. Apply power (12 VDC) to the reader. 5. For keypad readers, enter the facility code (1-255) if required. 6. Test the reader with a known valid credential to ensure proper read confirmation (beep and LED flash) and communication with the access control panel. 12. All keypad/reader models and their specifications - Signo 20: Mullion mount, no keypad. - Signo 20K: Mullion mount, with keypad. - Signo 40: Wall switch mount, no keypad. - Signo 40K: Wall switch mount, with keypad. - iCLASS SE Express R10: Mullion mount, no keypad. - iCLASS SE / multiCLASS SE: Various models (e.g., R10, R15, R40, RK40) with and without keypads. 13. Power supply specifications and battery backup calculations - Input Voltage: 12 VDC (typically provided by the access control panel or a dedicated power supply). - Battery backup is managed by the access control panel or power supply, not the reader itself. 14. Compliance standards met (EN, BS, UL, etc.) - FCC (Federal Communications Commission) - IC (Industry Canada) - CE (Conformité Européenne) - UL 294 (Standard for Access Control System Units) 15. Software/configuration tool names and versions - HID Reader Manager App (iOS and Android) - Android version: PLT-03858 Rev D.2 (December 2025) - iOS version: PLT-03683 B.5 (July 2022) 16. All ancillary devices: expanders, communicators, keypads, readers - HID iCLASS SE Bluetooth & OSDP upgrade kits (for upgrading Rev E readers). 17. Technical specifications: operating temperature, humidity, dimensions, weight - Operating Temperature: -35°C to 66°C (-30°F to 150°F) - Frequencies: BLE 2.4-2.480 GHz, HF 13.56 MHz, LF 125 kHz 18. Any known issues, common faults, and their solutions - Issue: Reader stops working, no read confirmation beep or green flash. Solution: Reader may need to be replaced if hardware failure occurs. - Issue: Cannot connect via Bluetooth. Solution: Ensure reader is powered, within range, and mobile device Bluetooth is enabled. 19. Complete user manual content summary - The HID Reader Manager App User Guide covers app installation, account registration, connecting to readers, inspecting reader status, upgrading firmware, applying configuration templates, and managing authorization keys. It details specific settings for credential formats, communication protocols, audio/visual feedback, and keypad behavior. 20. All product codes/part numbers for main units and accessories - Signo 20, 20K, 40, 40K - iCLASS SE Express R10 - iCLASS SE / multiCLASS SE Rev E (e.g., 900NTNN E K00000) - HID iCLASS SE Bluetooth & OSDP upgrade kits
| Part Number | Description | Cardholders |
|---|---|---|
| PWMP1501 | PoE+ Edge-capable intelligent controller (2 readers, 2 inputs, 2 outputs) | 240,000 |
| PWMP1502 | Access control panel (4 readers, 8 inputs, 4 outputs) | 240,000 |
| PWMP2500 | Access control panel (no onboard I/O); up to 64 doors via sub-panels | 600,000 |
| PWMP4502 | Access control panel; up to 64 doors via sub-panels | 2,000,000 |
| Fault / Display | Description | Likely Cause | Action |
|---|---|---|---|
| Panel Offline | Mercury/Tema-Voyager controller not communicating | Network fault, IP conflict, power fault | Check Ethernet connection and power. Verify IP address. Check firewall rules. |
| Access Denied | Card presented but access denied | No access level, expired card, wrong time schedule | Check cardholder access level in Pro-Watch. Verify time schedule and card expiry. |
| Reader Fault | Reader not communicating with controller | Wiegand/OSDP wiring fault, power fault | Check Wiegand/OSDP wiring. Check reader power supply. Verify OSDP address. |
| Database Connection Error | Pro-Watch cannot connect to SQL Server | SQL Server service stopped, network fault, credentials | Check SQL Server service is running. Verify database connection string. Check network. |
| Video Feed Lost | Camera feed not available in Pro-Watch | MAXPRO/ExacqVision connection fault, camera offline | Check VMS connection in Pro-Watch. Verify camera is online in VMS. Check network. |
| Intrusion Panel Fault | Galaxy/VISTA panel not communicating | Integration configuration, network fault | Check Galaxy/VISTA integration settings in Pro-Watch. Verify panel communication. |
| Licence Error | Pro-Watch licence invalid or expired | Licence file missing, server hardware change | Check licence file. Contact Honeywell support for licence reissue. |
| Terminal | Function | Notes |
|---|---|---|
| Ethernet (RJ45) | Network connection to Pro-Watch server | TCP/IP; 100 Mbps minimum |
| +12V DC | Power supply input | 12V DC from PSU; PoE+ on PWMP1501 |
| GND | Common ground | Must be continuous |
| D0 (Wiegand) | Wiegand Data 0 from reader | All Wiegand formats supported |
| D1 (Wiegand) | Wiegand Data 1 from reader | All Wiegand formats supported |
| A+ (OSDP) | OSDP RS-485 positive | Twisted pair; OSDP V2 protocol |
| B− (OSDP) | OSDP RS-485 negative | Twisted pair; OSDP V2 protocol |
| Lock Output | Door lock relay | Connect to fail-safe or fail-secure lock |
| Door Contact | Door open/closed monitor | Voltage-free input; NC recommended |
| REX | Request to exit | Push-to-make input |
| Input 1–8 | General purpose inputs | Voltage-free; use for alarms, tampers, etc. |
| Output 1–4 | General purpose outputs | Relay outputs; use for alarms, indicators, etc. |
HONEYWELL PRO-WATCH 6.5.1 — INTEGRATED SECURITY SUITE Source: Pro-Watch 6.5.1 Datasheet HBT-SEC-PRW651-02-UK-EN(0325)DS-ZD Manufacturer: Honeywell Building Technologies, Leicester, UK SYSTEM OVERVIEW: Pro-Watch Integrated Security Suite combines: - Pro-Watch Access Control - Pro-Watch Intelligent Command (AI-driven situational awareness) - Pro-Watch VMS (MAXPRO VMS / ExacqVision integration) Pro-Watch 6.5.1 is the most powerful version to date. New: Panel Conversion utility, Assa Abloy/Allegion wireless lock integration, site-based filters. EDITIONS: Lite — basic functionality for small offices Professional — standard commercial Corporate — multi-site enterprise Enterprise — links multiple Corporate systems for shared cardholder identities and events MERCURY MP INTELLIGENT CONTROLLERS: PWMP1501: PoE+ edge-capable; 2 readers, 2 inputs, 2 outputs; 240,000 cardholders PWMP1502: 4 readers, 8 inputs, 4 outputs; 240,000 cardholders PWMP2500: No onboard I/O; up to 64 doors via sub-panels; 600,000 cardholders PWMP4502: Up to 64 doors via sub-panels; 2,000,000 cardholders Features: ARM TrustZone, secure boot CPU, TLS 1.2, OSDP V2, dual circuit design Backward compatible with LP controllers TEMA-VOYAGER MULTI CONTROLLER: Manages 4 doors with peer-to-peer communications Continues operation when disconnected from server Serves as controller and connection point for up to 4 readers READER PROTOCOLS: Wiegand: All Wiegand readers supported OSDP: OSDP V2 (Blue Diamond readers) HID: All HID readers including Origo mobile credentials iLOQ: Battery-free wireless padlock management INTRUSION INTEGRATION: Honeywell Galaxy Dimension (PWDIMEN1-R) Honeywell VISTA (PWVISTA1-R, PWVISTA5-R, PWVISTA10-R) Vindicator, MB Secure Pro, S3100 VIDEO INTEGRATION: MAXPRO VMS (PWCEMAXPRO) ExacqVision (PWCEEXQNVR5-R to PWCEEXQNVRX-R) BIOMETRIC INTEGRATION: IDEMIA VisionPass SP, TBS, Iris ID Oosto facial recognition SERVER SPECIFICATIONS (SMALL SYSTEM): Processor: Intel Xeon scalable (8 cores+, 3.2 GHz max turbo) OS: Windows Server 2022/2019 Database: SQL Server 2022/2019 Client OS: Windows 11 (64-bit) SERVER SPECIFICATIONS (LARGE SYSTEM): Primary App Server: 16+ cores (24+ recommended), 3.6 GHz max turbo Remote Comm Server: 12+ cores (16+ recommended) Intelligent Command Server: 32+ cores CLIENT WORKSTATION: Processor: Intel Core i3/i5/i7/i9, 2.8 GHz+ RAM: 8 GB OS: Windows 11 (64-bit) Network: 100 Mbits/sec minimum (GB recommended) Video: 1920×1080, 24-bit colour SECURITY: End-to-end encrypted communication: TLS 1.2 Mercury MP: ARM TrustZone, secure boot CPU Database partitioning and definable operator permissions UK CONTACT: Building 5 Carlton Park, King Edward Avenue, Narborough, Leicester LE19 0LF Tel: +44 (0)1163 500714 hwll.co/securityUK
| Document | Source | Link |
|---|---|---|
| Pro-Watch 6.5.1 Datasheet (UK) | Honeywell Building Technologies | Download PDF |
| Pro-Watch Product Page | buildings.honeywell.com | View Online |
| Component | Function | Key Spec |
|---|---|---|
| IAC (Intelligent Access Controller) | Master controller — IP connected | Up to 250 doors, 3,000 zones, 1,000 readers, 100,000 users locally or 250 doors via RS-485 Sub-LAN |
| ISC (Integriti System Controller) | Alternative master controller | IP connected; same expansion capability as IAC |
| ILAM (Intelligent LAN Access Module) | Field module — 8 doors | Base: 2 doors, 2 Wiegand or 16 SIFER readers; expandable to 8 doors via UniBus expanders; offline intelligence |
| SLAM (Standard LAN Access Module) | Field module — 2 doors | 2 doors, 4 SIFER or 2 Wiegand readers; offline cache for 2,000 users (1hr–4 months) |
| Zone Expander (8-zone) | I/O expansion | 8 zone inputs, 2 aux outputs, 2 siren drivers; up to 99 per RS-485 LAN |
| PrismaX Keypad | Colour graphic keypad | Controls system, displays events, optional SIFER reader add-on for card+PIN |
| SIFER Reader | Smart card reader | MIFARE DESFire EV1/EV2, AES encryption; RS-485 multi-drop; up to 16 per bus; also OSDP compatible |
| Fault / Display | Description | Likely Cause | Action |
|---|---|---|---|
| Module Offline | ILAM/SLAM not communicating | RS-485 wiring fault, power fault, IP fault | Check RS-485 wiring termination and polarity. Check power supply. Check Ethernet Bridge if used. |
| Access Denied | Card presented but access denied | No access level, expired card, wrong time schedule | Check cardholder access level in Integriti software. Verify time schedule and card expiry. |
| Reader Fault | SIFER reader not communicating | RS-485 wiring fault, address conflict, power fault | Check RS-485 wiring and termination. Verify reader address (max 16 per bus). Check power. |
| Zone Tamper | Zone input tamper triggered | Zone wiring open circuit, tamper resistor missing | Check zone wiring and end-of-line resistors. Verify zone configuration in software. |
| Area Alarm | Intruder alarm triggered | Zone activated, forced entry, detector fault | Investigate zone. Check detector. Review event log. Reset alarm. |
| Cache Expiry | SLAM offline cache expired | Server offline for longer than cache expiry period | Restore server connection. Adjust cache expiry period (1hr–4 months) in software. |
| Firmware Update Fail | Firmware update failed | Network interruption during update | Retry firmware update. Check network stability. Use over-the-wire update via Integriti software. |
| Terminal / Bus | Function | Notes |
|---|---|---|
| Ethernet (RJ45) | IAC/ISC network connection | IP connection to Integriti server |
| RS-485 LAN A+/B− | Field module bus | Twisted pair; connect ILAM, SLAM, zone expanders; max 250 doors |
| SIFER RS-485 A+/B− | SIFER reader bus | Dedicated RS-485; up to 16 SIFER readers per bus; AES encrypted |
| Wiegand D0/D1 | Wiegand reader input | Standard Wiegand 26-bit or custom format |
| OSDP A+/B− | OSDP reader bus | OSDP V2 protocol; SIFER readers also OSDP compatible |
| Zone Input | Door contact / detector input | Voltage-free; end-of-line resistors required; double-pole recommended |
| Auxiliary Output | Lock / alarm output | Relay or open-collector output; connect to door lock or siren |
| UniBus | In-cabinet expansion bus | Plug-and-play; connects expanders, comms devices, door/reader devices |
| Power +/− | PSU input | 12V DC from PSU; battery backup recommended |
INNER RANGE INTEGRITI — INTEGRATED ACCESS CONTROL & INTRUDER DETECTION
Source: Inner Range Integriti 2021 Catalogue
Manufacturer: Inner Range Pty Ltd, Melbourne, Australia (UK distributor: Inner Range Europe)
SYSTEM OVERVIEW:
Integriti is an IP-connected integrated Access Control and Intruder Detection system.
Modular and scalable — suitable for small commercial buildings to large multi-campus enterprises.
All decision making is processed by the Controller with no reliance on the server.
Peer-to-peer communications between IAC controllers is supported.
SYSTEM CAPACITY (per IAC):
Zone Inputs: Up to 3,000
Outputs: Up to 3,000
Areas: Up to 250
Card Readers: Over 1,000
Doors: Up to 250 (locally) or 250 via RS-485 Sub-LAN
Users: Up to 100,000 (1,000,000 with User Expansion Kit)
FIELD MODULES:
ILAM (Intelligent LAN Access Module):
- Base: 2 doors, 2 Wiegand or 16 SIFER readers
- Expandable to 8 doors via UniBus 2 Door/2 Reader Expanders
- Offline intelligence: on-board database for access control if server offline
- Events buffered and synchronised on reconnection
SLAM (Standard LAN Access Module):
- 2 doors, 4 SIFER or 2 Wiegand readers
- Offline cache: 2,000 user cards; cache expiry 1hr to 4 months
- Permanent cache option for critical users
Zone Expander (8-zone LAN):
- 8 zone inputs, 2 aux outputs, 2 siren drivers
- Up to 99 per RS-485 LAN
- UniBus expansion: up to 32 zone inputs or 32 aux outputs per module
SIFER SMART CARD READERS:
Technology: MIFARE DESFire EV1/EV2 (AES encryption end-to-end)
Protocol: RS-485 multi-drop (superset of OSDP — also OSDP compatible)
Max per RS-485 bus: 16 readers
Security: AES encryption from reader to Access Module — superior to Wiegand
SOFTWARE:
Platform: Windows, MS SQL database
Client/Server architecture
Web interface for cardholder programming and basic monitoring
Mobile app (tablets and smartphones)
Rich graphics with vector scalable interactive floor plans and maps
PhotoID card design and printing
Active Directory, HR, payroll, and database integration
Time on Site, Muster, and commissioning reports
2-Factor Authentication for increased cyber security
Firmware update over-the-wire
SECURITY:
AES 256-bit encryption (SIFER readers to Access Module)
FIPS 140-2 certified cryptographic algorithms
HTTPS/TLS for cloud services, servers, web clients, and mobile apps
MS SQL TLS and TDE (AES 256-bit)
INTEGRATION:
Active Directory, HR, payroll, and other database applications
PSIM integration
Backward compatible with Concept LAN modules
| Document | Source | Link |
|---|---|---|
| Integriti 2021 Catalogue | innerrange.com (AWS) | Download PDF |
| Inner Range Product Page | innerrange.com | View Online |
| Integriti Professional Edition | innerrange.com | View Online |
| Product | Type | Notes |
|---|---|---|
| OnGuard | Full enterprise platform | Unlimited users/doors |
| NetBox | Cloud-based access control | Subscription model |
| LNL-3300 | Intelligent System Controller | Main controller |
| LNL-1300 | Dual Reader Interface | 2-door controller |
| Code / Display | Description | Likely Cause | Action |
|---|---|---|---|
| Controller Offline | Controller not communicating | Network fault, power loss | Check network and power. |
| Card Not Found | Card not recognised | Card not enrolled | Re-enrol card. |
| Access Denied | Card read but access denied | Access level, schedule | Check access level and schedule. |
| Database Error | OnGuard database fault | Disk fault | Restore from backup. |
| Server Fault | OnGuard server not responding | Service stopped | Restart OnGuard service. |
| Terminal | Function | Notes |
|---|---|---|
| +12V | Power supply | 12V DC from PSU |
| 0V | Common ground | Must be continuous |
| D0 | Wiegand Data 0 | Green wire |
| D1 | Wiegand Data 1 | White wire |
| LOCK+ | Electric lock positive | Fused at 1A |
| LOCK− | Electric lock negative | Via relay output |
| REX | Request to exit | Normally open push button |
| DOOR | Door contact | Normally closed magnetic contact |
=== WEB RESEARCH: lenel ===
## Lenel S2 OnGuard 8.3 Technical Reference
### Manufacturer and Product
Lenel S2 OnGuard 8.3
### Security Discipline
Access Control
### Product Range and Model Numbers
* **OnGuard 8.3** (Base System)
* **OnGuard 8.2 Update 1** (Previous version, referenced for client installation)
* **OGClient.iso** (Client-only installation image)
* **OG.iso** (Full installation image, includes third-party support)
### Installation Procedures
#### System Requirements
* **Operating System:** Windows 11 (specific usage notes in Appendix)
* **Database:** SQL Server, Oracle, SQL Server Desktop Engine, SQL Express, Azure SQL databases
* **Hardware Key (Dongle):** Parallel port or USB dongle (for hardware licenses)
#### Installation Steps (OnGuard 8.3)
1. **Launch Installer:** Run `setup.exe` from the installation media.
2. **Prerequisites:** The installer will check for and install necessary prerequisites (e.g., .NET Framework, Visual C++ Redistributables).
3. **Welcome Screen:** Click [Next].
4. **License Agreement:** Read and accept the license agreement.
5. **Installation Type:** Select `Standard` or `Custom`.
6. **System Configuration:** Choose one of the following:
* **Server System:** Installs all server features (Platform Server or Custom Server).
* **Client System:** Installs client applications.
* **Monitoring Client:** Installs a client for monitoring only.
* **Badging and Credential Client:** Installs a client for badging and credential management.
* **Note:** `Server System` is disabled if installing a Client System from `OGClient.iso`.
7. **Milestone Support (Optional):** If `Server System` or `Client System` is selected, option to `Add Milestone Support` for Milestone XProtect recorders. Click [Next].
8. **System Options (based on configuration choice):**
* **Server System:**
* Select `Platform Server` (all server features) or `Custom Server` (select individual features).
* Select appropriate database option.
* **Client System:**
* Select `Typical System` (standard features) or `Custom System` (specify server locations and features).
* Select appropriate database option.
* **Monitoring Client/Badging and Credential Client:** Configure database type information.
9. Click [Next].
10. **System Location Information:**
* **Installation Directory:** Accept default or specify a different destination folder.
* **License Server Location:** Accept default or specify a different location.
* **Port:** Default is `8189` for access control system communication. Can be changed via Configuration Editor (Appendix A).
* **Database Login User:** Enter the name of the database login user (default: `Lenel`). Must be customized if changed.
* **Database Location:** Accept default or specify a different location.
* Click [Next].
11. **Custom Setup (if selected in step 7):** Select desired access control system features. Descriptions and disk space requirements are displayed. Click the icon next to a feature for installation choices.
12. Click [Install] to begin.
13. **Progress Bar:** Monitor installation status.
14. **Completion:** Click [Finish].
15. **Reboot:** Reboot if prompted.
16. **Setup Assistant:** Launches automatically after installation.
#### Setup Assistant
* Simplifies OnGuard installations and upgrades.
* Launches automatically after installer finishes.
* Requires Administrator rights to run.
* **Dialog Sections:**
* **Status Pane (left):** Lists tasks with status indicators (green check: success, yellow check: warning/skipped, red X: failed, blue arrow: running, no icon: not run).
* **Main Pane:** Provides data, status, fields, buttons for active task.
* **Description Pane:** Brief description of each task.
#### Security Utility
* Embedded into Setup Assistant.
* Should be run after Windows Update or Service Pack installation.
* Makes security adjustments to the operating system. Review release notes and disclaimer.
#### Configuration Editor
* Embedded into Setup Assistant.
* Shows current configuration of Database and License Server.
* Highlights configuration issues (inconsistent `application.config`/`ACS.INI`, database/license server not found).
* Allows storing encrypted database password in `application.config`.
* **Client Support (Client Connect):** Configures client workstations to connect to LS Login Driver via LS Message Broker service.
* **Options:** Provide database configuration details or a Client Connect file.
* **Client Connect File:** Distributes LS Login Driver connectivity details to client workstations without direct database access.
* **Creation Methods:** Client Connect form (`System Administration > System Options`) or Client Connect Tool.
* **Provisioning Methods:** Manually in Configuration Editor, automatically by placing in `C:\ProgramData\Lnl\clientConnect.ogcc`, or during unattended installations using `ClientConnectFilePath` parameter.
#### System License
* Embedded into Setup Assistant.
* Installs or verifies a valid license.
* Requires a valid license to continue configuration.
* Run manually when purchasing additional licensable features.
#### Service Log On
* Enter Windows user name and password for the account that will run OnGuard software.
* User must have database access and read/write access to OnGuard directory for log files.
#### Database Installation
* For new server installations using SQL Express, Setup Assistant installs a new `ACCESSCONTROL` database.
* **Steps:**
1. Optionally browse for alternate source database (.MDF) file.
2. Optionally browse for alternate database storage path.
3. Click [Install database].
* **Archival Database:** Option to back up the new `ACCESSCONTROL` database if archiving is configured.
#### Database Backup
* For updating existing installations, Setup Assistant provides a method to back up SQL Server or SQL Server Express database before upgrade.
* **Strongly recommended** to make a backup.
* **Procedure:**
1. Accept or modify `Backup set name`, `Backup set description`, `Server backup file path`.
2. Confirm warning.
3. Click [Backup].
4. Troubleshoot errors if backup fails.
* **Notes:**
* Backup path is on the database server workstation (e.g., `C:\Program Files\Microsoft SQL Server\...`).
* Backup path cannot be a network drive; must be local.
* `Browse` button available only if Setup Assistant runs on database server; otherwise `Reset Path` button.
* Only creates backup; use standard SQL tools for restoration.
#### Database Setup and Encryption
* For server installations, Setup Assistant runs Database Setup automatically.
* Sets up database for current OnGuard version, installs reports, sets encryption key management/recovery, updates field encryption, runs Forms Translator.
* **Encryption Key Entry:** Dialog opens for first-time installations, upgrades from OnGuard 8.0 or earlier, or re-encryption.
* Must be performed on workstation with LS Login Driver installed.
* **Options:** `Generate a key from a passphrase` (10-36 characters), `Generate a random key`, `Import a key from a file` (*.og file).
* **Recommendation:** Export encryption key to a file for restoration. Mandatory for random keys.
* **Important:** Exported key file is a tightly-controlled cryptographic resource for disaster recovery.
* **Blocking Database Connections:**
* OnGuard 8.1+ automatically blocks connections for Microsoft SQL.
* For Oracle, manual blocking is required (disconnect from network or limit access via `SQLNET.ORA` with `tcp.validnode_checking = yes` and `tcp.invited_nodes = (localhost,<yourOracleServerHostName>)`).
* Stop all OnGuard services except LS License Server, LS Message Broker, LS Login Driver.
* Re-enable connections after re-encryption.
* **Encryption Key Troubleshooting:**
* **Issue:** Encryption key not generated (Login Driver not installed or not Message Broker host).
* **Resolution:** Confirm empty `Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Lenel\OnGuard\LD` registry entry. Run Database Setup on the correct workstation and provide encryption key details.
* **Issue:** `Login Driver is not connected to the message broker.`
* **Resolution:** Stop LS Login Driver service, run as application, check for errors. Refer to specific error messages below.
* **Issue:** `Encryption key set up for this Login Driver does not match the database in use.`
* **Resolution:** Open Login Driver as application, `Edit > Set Encryption Key`, provide correct passphrase or *.og file.
* **Issue:** `Encryption key loading failed...The data is invalid.`
* **Resolution:** Configure Login Driver with same encryption key as database (`Edit > Set Encryption Key`).
* **Issue:** `Encryption key loading failed...Login failed for user.`
* **Resolution:** `Edit > Change Database Password`, update password to match LENEL password.
* **Issue:** `Login Driver is not connected to the Message Broker because you must set the RabbitMQ LD credentials.`
* **Resolution:** Provide encryption key and connect to database via ODBC. Login Driver will prompt for RabbitMQ LD credentials.
#### OnGuard Logs Folder
* Default location: `C:\ProgramData\Lnl\logs`.
* Users need Read, Write, and List Folder Contents permissions.
#### Remotely Hosted Databases
* If using Windows Authentication and Live database is remote, LS Site Publication Server (Enterprise/Distributed ID) might need to log on as a specific user with NT authentication access.
* **Configuration:**
1. `Control Panel > Administrative Tools > Services`.
2. Double-click target service.
3. `Log On` tab, select `This account`.
4. Enter username and password (use [Browse] and [Check Names]).
5. Click [OK].
6. Restart service.
### Installing OnGuard on a Client Machine
* Two general steps: install software, verify license.
* Does not require database installation, Database Setup, license installation, or hardware key.
* **Methods:**
* Install from `OGCLIENT.iso` (client-only features, smaller size, excludes Crystal Reports, RabbitMQ, Erlang, OnGuard Modules).
* Silent installation using PowerShell wrapper script with `OGCLIENT.iso` or `OG.iso`.
### Database Authentication for Web Applications
* Required for Oracle databases and browser-based OnGuard applications.
* **Methods:**
* **Windows Authentication:**
* **SQL Server:** Add Windows user to SQL Server (SQL Server Management Studio: `Security > Logins > New Login`). Set `Login name` as `<server-name>\<username>`, select `Windows authentication`. Map user to `<Server Name>lenel` database with `db_owner` and `public` roles (or minimum `public`, `db_datareader`, `db_datawriter`, `db_ddladmin`, `db_executor`). Verify `application.config` for Windows authentication.
* **Oracle:** Create new Oracle user with Windows authentication credentials (SQLPlus: `CREATE USER "<OPS$DOMAIN>\<DOMAINUSER>" ... IDENTIFIED EXTERNALLY ... GRANT CONNECT, RESOURCE, LENEL_RESTRICTEDUSER_ROLE TO "OPS$DOMAIN\DOMAINUSER";`). Verify `sqlnet.ora` has `SQLNET.AUTHENTICATION_SERVICES=(NTS)`.
* **Provide Credentials in Protected File:** Store authentication information in `application.config`. Highly recommended to secure with Access Control Lists (ACL). Not recommended if Windows authentication is not used.
### Logging Into the OnGuard System
#### Windows User Permissions
* Windows user logged into OnGuard applications must have read/write access to the OnGuard directory for log files.
#### Error Messages (Password-related)
* **Database password violations:** `Your password is a keyword that is not allowed.` (Corrects Database password)
* **Database password violations:** `Your password cannot be blank. Please enter a password.` (Corrects User password)
* **User password violations:** `Passwords cannot be the same as the user name.` (Corrects User password)
#### Accounts
* System Administrator creates unique accounts for each user with specific permissions.
* **Default Accounts (samples):**
* `SA` / `SA` (system account, unlimited access, cannot be deleted, password must be changed on first login).
* `admin` / `sample` (user)
* `user` / `sample` (user)
* `badge` / `sample` (user)
* **Security Recommendation:** Create an SA Delegate user with all permissions, then disable the default SA account.
#### Log In (without Single Sign-On)
1. Start desired application.
2. If prompted, select database from ODBC system databases. Click [OK].
3. Log On window:
* `User name`: Type assigned user name (first time: `SA`).
* `Password`: Type assigned password (first time: `SA`). Characters appear as `*`.
* `Directory`: Select directory (default: `<Internal>`).
* `Remember user name and directory`: Optional checkbox.
* Click [OK].
4. If authorization warning appears, click [Yes].
#### Single Sign-On (SSO)
* Logs into OnGuard with same user name and password as Windows authentication (or LDAP).
* **Notes:**
* Windows Authentication should be used for SSO. Anonymous Authentication for other scenarios.
* Explicit username/password for directory authentication is discouraged; use view-only accounts if necessary.
* Assigning both internal and directory accounts increases flexibility but also security risk. Standardize on one.
* **Directory Types Supported:** Microsoft Active Directory, Microsoft Windows NT 4 Domain, Microsoft Windows Local Accounts, LDAP.
* **Automatic SSO:** Users start OnGuard and are automatically logged in under their Windows account/directory. Supported with Windows domain accounts.
* **Manual SSO:** Users manually enter Windows or LDAP account information (user name and password). Can select different configured directory. Supported with Microsoft Active Directory, Microsoft Windows NT 4 Domain, and LDAP.
* **Configuration:** System Administrator must add a directory and link a user account to it.
#### Troubleshoot Logging In
* Verify correct user name/password for selected directory.
* Accept authorization warning.
* Verify valid license is installed:
* License Server settings correct (Configuration Editor).
* LS License Server service running.
* Software-based licenses activated.
* USB licenses have License Key Drivers installed.
* If SSO, ensure PC user is linked to an internal OnGuard user via operational directory.
* Verify LS OpenAccess service is running.
#### LenelS2 Console
* Web-based application to launch OnGuard web/desktop applications and third-party apps/websites.
* Access via `https://<hostname>:8080`.
* Requires OnGuard username and password.
* Displays cards for licensed/installed applications.
* Desktop applications must be installed locally to be launched from Console.
* Users can re-arrange, re-color, create custom cards, or modify templates (depending on permissions).
### Accounts and Passwords
#### Accounts
* System Administrator creates unique accounts and assigns permissions.
* SA Delegate user can be created to disable default SA account for enhanced security.
* **Default Accounts Table:**
| User name | Password | Type |
| :-------- | :------- | :--- |
| SA | SA | system account |
| admin | sample | user |
| user | sample | user |
| badge | sample | user |
* **Note:** Default SA password must be changed on initial login.
#### Passwords
* OnGuard checks user passwords against standards if SSO is not used.
* **Password Policies (configurable):**
* Minimum password length.
* Complex passwords (mix of uppercase, lowercase, numeric, non-alphanumeric).
* Case-sensitivity.
* Password expiration (after specified days, warning, force change on next login).
* Rejection of prohibited keywords.
* Rejection of prior passwords (based on specified number).
* Inactivity timeout.
* Invalid login lockout.
* **Notes:**
* Upgraded systems support current passwords until policies require change.
* OnGuard database user password checks: not blank, not same as username, not prohibited keyword.
* Database passwords conform to specific database rules (e.g., SQL Server/Oracle 12c are case-sensitive).
* Password policies can be configured via OnGuard Users browser-based client application.
* Oracle databases: `System`/`Manager`, `Internal`/`Oracle`, `Sys`/`Change_On_Install` are not allowed together.
* **Password Standards (for strong passwords):**
* Cannot be blank.
* Cannot be same as user name.
* Cannot be on list of prohibited keywords.
* May require numbers, letters, symbols (spaces acceptable).
* Case-sensitive.
* Maximum length: 127 characters. Minimum: 1. Default: 8.
#### Change the Database Password
* Default database password: `Secur1ty#`.
* Database password must be synchronized between SQL Server/Oracle/SQL Server Desktop Engine and Login Driver.
* **Procedure (using Login Driver):**
1. Stop LS Login Driver service, run as application.
2. Right-click system tray icon, select `Open`.
3. Login Driver window: `Edit > Change Password`.
4. If password is weak, Account Passwords window appears (refer to Password Standards).
5. Click [Continue]. Select `LENEL` account, click [Change Password].
6. Enter `Old password`, `New password`, `Confirm password`.
7. If Login Driver and database are on different machines, checkbox `When I change this password on the Login Driver, do not change the password on the database server. I will change the password manually on the database server.` appears.
* Unselected (default): Password changed in both places (sent as plain text over network).
* Selected: Password changed in Login Driver only; manual change required on database server.
8. Click [OK] to save.
9. Exit LS Login Driver application, restart service.
#### Change the System Administrator Password for the Database
* For SQL Server Desktop Engine and SQL Server, this is the `SA` account.
* For Oracle, there are several system accounts.
* **Procedure (using Database Setup):**
1. Launch Database Setup.
2. If upgrading, select `Live` or `Archival` database. Select `Add/remove missing system data for current build`.
3. Click [Continue].
4. Database Setup Progress window: Click [Execute].
5. If upgrading, warning to back up database appears. Click [Yes].
6. Database installs. Anomalies may be checked. Select known anomalies and click [Continue].
7. Database is encrypted using encryption key from Login Driver.
### Configuration Editor
* Used to modify `application.config` and `ACS.INI` files.
* **Database Section (page 92 of Installation Guide):** Used to modify database settings, including the database name (default `AccessControl`).
* **Advanced Database Section (page 93 of Installation Guide):** Used to verify `application.config` for Windows authentication and store `lenel` user account credentials.
### Certificates
#### General Description
* **TLS (Transport Layer Security) / SSL (Secure Socket Layer) certificates:** Installed on web servers and clients for secure encrypted connections.
* Private certificate on server, public certificate sent to client.
* Used by LS Message Broker service, LS Site Publication Server, LS OpenAccess, NGINX clients (OnGuard Monitor, OnGuard Credentials, LenelS2 Console).
#### Where to Get Certificates
* **Trusted Certificate Authority:** Certificates expire in 1-3 years.
* **Self-signed certificate:** Installed by default during OnGuard installation/upgrade. Expires in 3 years (OnGuard 8.1+). Primarily for evaluation/demonstration/stand-alone systems. Causes browser security alerts. Cannot be revoked; must be replaced/rotated if compromised.
#### Certificate Management
* If LS Web Server (NGINX) and LS Message Broker Service (RabbitMQ) are on the same server, they use the same certificate. Otherwise, each requires a unique certificate.
* **Viewing Existing Certificate:** Refer to `Configure the Name and Location of the Certificate` (page 107).
* **Installing a Certificate Manually:**
* Delete existing certificates if re-issuing.
* Install trusted certificate on OnGuard server (where OpenAccess service runs) for mobile live events.
* Restart LS Web Service and LS Message Broker service after changes.
* **Self-signed certificate re-issue:** Run `lnl_app_server_certificate_installer.exe` with `-key`, `-cert`, `-keystore`, `-cn` parameters (e.g., `C:\ProgramData\Lnl\nginx\conf\ls_server_cert_key.pem`, `C:\ProgramData\Lnl\nginx\conf\ls_server_cert.pem`, `C:\Program Files (x86)\OnGuard\LicenseServerConfig`, `<virtual computer name>`).
* **Import custom certificate:** Generate CSR, obtain certificate from CA, install certificate and key onto NGINX/LS Web Server. If private key is encrypted, configure NGINX/RabbitMQ with passphrase or decrypt key.
* **Decrypt private key file:** `openssl rsa -in key.pem -out server.key`.
#### LS Web Server (NGINX) Certificate Configuration
* Default certificate location: `C:\ProgramData\Lnl\nginx\conf`.
* `nginx.conf` file contains `ssl_certificate` (public key, `ls_server_cert.pem`) and `ssl_certificate_key` (private key, `ls_server_cert_key.pem`).
* Intermediate certificates: Concatenate server certificate and intermediate certificate into `ls_server_cert_key.pem` (server first, then intermediate).
* **Encrypted private key:** Add `ssl_password_file ls_server_cert_key.pass;` to `nginx.conf` and place passphrase in `ls_server_cert_key.pass` file.
* **Important:** Repeat process if OnGuard is reinstalled or upgraded. Never share key file.
#### LS Message Broker Service (RabbitMQ) Certificate Configuration
* By default, uses same certificate as NGINX.
* **Changing certificate location:** Edit `C:\Users\<username>\AppData\Roaming\RabbitMQ\advanced.config`.
* Update `ssl_options` section: `cacertfile`, `certfile`, `keyfile` paths.
* **Encrypted private key:** Add `{password, "passphrase"},` after `keyfile` line.
* **Performing Peer Verification:** Configure LS Message Broker server to reject clients without valid certificates.
* Edit `C:\Users\<username>\AppData\Roaming\RabbitMQ\advanced.config`: Add `{verify, verify_peer},` and `{fail_if_no_peer_cert, true}`.
* Add `[LSMessageBrokerClientSecurity] CertificatePath=<"path to client-side certificate">` to `acs.ini` on all clients/servers.
* Modify `appSettings` in application configuration files (e.g., `Lnl.OG.EventContextProviderService.exe.config`): Add `<add key="X509CertPath" value="path/to/client/cert/cert.p12"/>`.
* **Notes:** Client-side certificates must be `.p12` format and decrypted.
#### Apple Wallet Certificates
* For visitors to add passes to Apple Wallet.
* **Requirements:**
1. Obtain certificates from Apple Developer portal (`http://developer.apple.com/account`). Requires Apple Developer account.
2. Download Apple Wallet Intermediate CA certificate `AppleWWDRCA.cer`.
3. Generate a pass signing certificate (`<YourCertificateName>.p12`) for your organization with specific Team identifier and Pass type identifier (format: `pass.com.<your organization domain>.OnGuard-Visitor`).
4. Install certificates:
* Install `AppleWWDRCA.cer` into Local Machine certificate store, in the Intermediate Certification Authorities folder.
* Install `<YourCertificateName>.p12` into Local Machine certificate store, in the Personal folder.
### Uninstallation
#### Files Not Removed During OnGuard Uninstallation
* Installation packages not installed with OnGuard.
* Common system components shared by other applications (prerequisites).
* OnGuard localizations with customer data/customizations.
* Customized configuration files (`.ini`, `.config`, etc.).
* Files created during application use (reports, logs).
* Registry options and settings for re-installation support.
### OnGuard Online User Manual (Older Version - Jan 2005)
#### Related Documentation
* `Alternative Wiring Configurations Guide`
* `Hardware Installation Guide`
#### Chapter 2: Managing Access
* Covers step-by-step operator procedures for timezones, access levels, and cardholder management.
#### Chapter 3: Monitoring Alarms
* Covers alarm-monitoring operations:
* Deleting events.
* Acknowledging events.
* Using the System Hardware Tree.
* Pending alarms.
* Tracing alarms.
* Filtering alarms.
* Toolbar/menu behavior.
* Includes a glossary appendix.
### Default Codes
* **Application Login:**
* User name: `SA`, Password: `SA` (system account, must be changed on first login)
* User name: `admin`, Password: `sample`
* User name: `user`, Password: `sample`
* User name: `badge`, Password: `sample`
* **Database Login:**
* User name: `Lenel`, Password: `Secur1ty#` (default, highly recommended to change)
* **Port:** `8189` (default for access control system communication)
### Fault/Event/Alarm Code Tables
* (Not explicitly detailed in the provided installation guide, but the older user manual mentions "Monitoring Alarms" and "deleting events, acknowledging events, tracing alarms, filtering alarms" which implies the existence of such codes. Further research would be needed to extract specific codes and descriptions.)
### Zone Types and Descriptions
* (Not explicitly detailed in the provided installation guide or the older user manual. Further research would be needed to extract specific zone types and descriptions.)
### Wiring Diagrams and Terminal Descriptions
* (Not explicitly detailed in the provided installation guide or the older user manual, but the older user manual references an `Alternative Wiring Configurations Guide` and `Hardware Installation Guide`. Further research would be needed to extract specific wiring diagrams and terminal descriptions.)
### Programming Menu Structure
* (Not explicitly detailed in the provided installation guide or the older user manual. The installation guide mentions "Custom Setup" for selecting features, but not a full menu structure. Further research would be needed to extract specific programming menu structures.)
### Expander/Peripheral Devices with Specs
* (Not explicitly detailed in the provided installation guide or the older user manual. Further research would be needed to extract specific expander/peripheral devices and their specifications.)
### Commissioning Steps
* (Covered broadly under "Installation Procedures" and "Setup Assistant" in the installation guide, but not as a distinct, comprehensive commissioning guide. Further research would be needed for a dedicated commissioning process.)
### Common Fault Diagnosis
* **Encryption Key Troubleshooting:** (Detailed in "Database Setup and Encryption" section above).
* **Login Driver Connection Issues:** (Detailed in "Database Setup and Encryption" section above).
* **Remotely Hosted Database Connection Issues:** (Detailed in "Remotely Hosted Databases" section above).
* **License Troubleshooting:** (Detailed in "Install Your OnGuard License" section above).
### Compliance Standards Met
* (Not explicitly detailed in the provided installation guide or the older user manual. Further research would be needed to extract specific compliance standards.)
### Other Technical Details
* **Universal Time Conversion Utility:** Converts local times in database to Coordinated Universal Time for multi-time zone compatibility. Recommended for server upgrades from OnGuard versions earlier than 6.3.
* **RabbitMQ LD Credentials:** Login Driver holds RabbitMQ credentials. Must update password in RabbitMQ console tool before changing in Login Driver. Configured via `Edit > Set RabbitMQ LD credentials` in Login Driver application.
* **NGINX:** Used as LS Web Server.
* **OpenAccess:** Service that needs to be running for login.
* **LS Site Publication Server:** Used in OnGuard Enterprise installations.
* **LS Message Broker Service:** Secured by TLS. Clients include LS Site Publication Server, LS OpenAccess.
* **Crystal Reports:** Excluded from `OGCLIENT.iso`.
* **Erlang:** Excluded from `OGCLIENT.iso`.
* **VMware ESX:** Software licenses supported in this virtual environment for License Server only. Not for dongle-based licenses.
* **LenelS2 Connect™ portal:** `https://connect.lenels2.com/s/downloads` for compatibility charts and downloads.
* **License Activation URL:** `https://activate.lenels2.com:443` (requires TCP port 443 open).
* **License Activation Phone/SMS:** 1-866-788-5095 option (5) or email `sig@carrier.com` (US/Canada); +44 7937 947945 (EMEA SMS); +48 5832 62240 or email `sig.emea@carrier.com` (EMEA Phone).
* **LenelS2 Knowledgebase:** `https://kb.lenels2.com` for license installation issues.
* **ODBC:** Used for database connections.
* **LDAP:** Supported directory for Single Sign-On.
* **`application.config` and `ACS.INI` files:** Configuration files. Manual editing not advised; use Configuration Editor.
* **`dbconfig.xml`:** Configured by Configuration Editor for Reports and Dashboards.
* **`AccessControl_ReportsConfig`:** Default name for ReportsConfig database.
* **`FLEXnet` folder:** `C:\ProgramData\FLEXnet` (delete files here for Activation Code troubleshooting).
* **`appactutil.exe`:** Used for license return troubleshooting (`appactutil.exe -shortcode OnGuard.asr -return SCASR_FID_1_OnGuard`).
* **`SQLNET.ORA`:** Oracle configuration file for network settings.
* **`X509CertPath`:** XML key in application configuration files for client-side certificates (e.g., `cert.p12`).
* **`AppleWWDRCA.cer`:** Apple Wallet Intermediate CA certificate.
* **`pass.com.<your organization domain>.OnGuard-Visitor`:** Naming convention for Apple Wallet pass signing certificate.
=== WEB RESEARCH: s2 ===
## DSC PowerSeries Neo HS2016 HS2032 HS2064 HS2128 Intruder Alarm Panel - Full Technical Reference
### Product Range and Model Numbers
**Alarm Controllers:**
* HS2016
* HS2016-4
* HS2032
* HS2064
* HS2064 E
* HS2128
* HS2128 E
**Compatible Communicators:**
* 3G2080E
* 3G2080RE
* TL280E
* TL280RE
* LE2080(R)
* TL280LE(R)
* TL2803GE
* TL2803GRE
* TL8803G
* TL880LT
* TL880LE
* PCL-422
**Hardwired Smoke Detectors:**
* 2-wire smoke detectors: y= A, B, or C (A: ULC listed, B: UL listed, C: European and Australian models)
* 4-wire smoke detectors: y= A, B, or C (A: ULC listed, B: UL listed, C: European and Australian models)
* CO detectors: CO-12/24, 12-24SIR, FW-CO12, FW-CO1224, CO1224
**Wireless Devices (PGx series - x denotes frequency: 9 for 912-919 MHz, 8 for 868MHz, 4 for 433MHz):**
* PG smoke detectors: PGx926
* PG smoke and heat detector: PGx936, PGx916
* PG CO detector: PGx933, PGx913
* PG PIR motion detectors: PGx904(P)
* PG PIR + camera motion detector: PGx934(P)
* PG curtain motion detector: PGx924
* PG dual tech motion detector: PGx984(P)
* PG mirror motion detector: PGx974(P)
* PG outdoor motion detector: PGx994
* PG glass break detector: PGx912, PGx922
* PG shock detector: PGx935
* PG flood detector: PGx985
* PG temperature detector (indoor use): PGx905
* Outdoor temperature probe: PGTEMP-PROBE (requires PGx905)
* PG flat PIR: PGx914
* PG recessed Contact: PGx307
* PG ceiling mount detector with Smart Presence – Short Range: PGx862
* PG ceiling mount detector with Smart Presence – Long Range: PGx872
* PG outdoor contact: PGx312
* PG outdoor curtain PIR: PGx902
**Modules:**
* Wireless keypads: HS2LCDWFx, HS2LCDWFPx, HS2LCDWFPVx
* PG keys: PGx939, PGx929
* Hardwired keypads with 2-way wireless integration module: HS2LCDRFx, HS2LCDRFPx, HS2ICNRFx, HS2ICNRFPx
* PG panic key: PGx938
* PG 2-button key: PGx949
* Hardwired keypads: HS2LCD, HS2LCDP, HS2ICN, HS2ICNP, HS2LED
* PG sirens: PGx901, PGx911
* Touchscreen Keypad: HS2TCHP
* PG repeater: PGx920
* 2-way wireless integration module: HSM2HOSTx
* PG door/window contacts: PGx303, PGx975
* PG door/window contact w/ AUX: PGx945
* 8-zone expander: HSM2108
* 8-output expander: HSM2208
* Power supply: HSM2300
* 4 high current output expander: HSM2204
**Central Station Receivers:**
* SG-System I, II, III, IV, 5
**Enclosures:**
* PC5003C, PC4050CR, PC4050CAR, CMC-1, PC4051C. Other enclosures are available to suit a variety of system configurations.
### Technical Specifications
**Corbus Wiring:**
* Minimum 22 gauge quad, two pair twisted preferred.
* Modules can be home run to the panel, connected in series or can be T-tapped.
* Do not use shielded wire for Corbus wiring.
* No module can be more than 1,000'/305m (in wire length) from the panel.
**Corbus Current Calculation Chart:**
| Item | Current (mA) | Quantity | Total (mA) |
|---|---|---|---|
| HS2016/HS2032/HS2064/HS2064 E/HS2128/HS2128 E | 85 | x | |
| HS2LCD | 105 | x | |
| HS2ICN | 105 | x | |
| HS2LED | 105 | x | |
| HS2LCDP | 105 | x | |
| HS2ICNP | 105 | x | |
| HS2LCDRF | 105 | x | |
| HS2ICNRF | 105 | x | |
| HS2ICNRFP | 105 | x | |
| HS2TCHP | 160 | x | |
| HSM2108* | 30 | x | |
| HSM2208* | 40 | x | |
| HSM2300/2204* | 35 | x | |
| HSM2HOSTx | 35 | x | |
| HSM2955** | 85 | x | |
| 3G2080(R)E/TL2803G(R)E/TL280(R)E (PCLINK) | 125 | x | |
*These units draw current from the Corbus to power devices external to the module. This current must be added to the total Corbus current. See manufacturer's specifications for the current draw of each device.
** For HSM2955 current draw refer to HSM2955 installation manual.
**System Output Ratings (12VDC):**
* **AUX:** 700mA max. (including PGMs 1-4). Subtract the listed rating for each keypad, expansion module and accessory connected to AUX or Corbus. At least 100mA must be reserved for the Corbus.
* **BELL:** 700mA max. Continuous rating. 2.0A. short term. Available only with standby battery connected. Not for UL/ULC or EN certified applications.
* **HSM2208 AUX:** 250mA. Continuous rating. Subtract for each device connected. Subtract the total load on this terminal from the alarm panel AUX/Corbus output.
* **HSM2108 AUX:** 100mA. Subtract for each device connected. Subtract the total load on this terminal from the panel AUX/Corbus output.
* **PCLink+ (Alt. Com.):** 125mA
* For UL, ULC and Commercial Listed applications, the total standby and alarm current cannot exceed 700mA.
**Capacitance Limits (Corbus):**
| Wire Capacitance per 1000’ (300m) | Total Corbus Wire Length |
|---|---|
| 15nF | 5300’/1616m |
| 20nF | 4000’/1220m |
| 25nF | 3200’/976m |
| 30nF | 2666’/810m |
| 35nF | 2280’/693m |
| 40nF | 2000’/608m |
**Transformer:**
* DSC PTD1640U, PTD1640, PTC1640UG, PTC1640CG
* AC (International Installations): Primary: 220V-240Vac, 50/60Hz, 200mA; Secondary: 16.5VAC/40VA
**Zone Wiring:**
* For UL listed installations use SEOL or DEOL only.
* Minimum 22 AWG wire, maximum 18 AWG.
* Do not use shielded wire.
* Do not exceed 100Ω wire resistance.
**Burglary Zone Wiring Chart (Figures based on maximum wiring resistance of 100Ω):**
| Wire Gauge | Maximum Length to EOL Resistor (ft/meters) |
|---|---|
| 22 | 3000 / 914 |
| 20 | 4900 / 1493 |
| 19 | 6200 / 1889 |
| 18 | 7800 / 2377 |
**AUX Power Wiring:**
* 11.3-12.5VDC/700mA of current (shared with PGM outputs).
* Output is protected; if too much current is drawn, the output is temporarily shut off.
* If using a 12V, 14Ah battery, maximum AUX capacity for 24-hour standby is 470mA.
**PGM Wiring:**
* Min/max operating voltages for devices, sensors and modules is 9.5VDC - 14VDC.
* PGMs switch to ground when activated.
* PGM 1, 3, 4 supply up to 50mA; PGM 2 supplies up to 300mA.
* A relay is required for current levels greater than 50mA or 300mA.
* PGM2 can also be used for 2-wire smoke detectors, 24-hr burglary input alarm.
**Bell Wiring:**
* Supplies 700mA of current at 10.4 - 12.5VDC.
* Bell output is supervised and power limited by 2A thermistor.
* If unused, connect a 1000Ω resistor across Bell+ and Bell- to prevent a trouble.
**Telephone Line Wiring:**
* Use 26 AWG wire minimum.
### Default Codes
* **Installer Code:** (Default: 5555) Used to enter Installer Programming mode.
* **Master Code:** (Default: 1234) Used for arming/disarming, bypassing zones, and other user functions.
* **User Codes:** Programmable by the Master User.
* **Duress Code:** Programmable.
### Fault/Event/Alarm Code Tables
**Trouble Indicators (Accessed via [*][2]):**
* **Trouble 01: Service Required**
* 1: Low Battery
* 2: AC Trouble
* 3: General System Supervisory
* 4: General System Tamper
* 5: General System Fault
* 6: General System Trouble
* 7: General System Supervisory Restore
* 8: General System Tamper Restore
* 9: General System Fault Restore
* 10: General System Trouble Restore
* **Trouble 02: AC Trouble**
* **Trouble 03: Telephone Line Trouble**
* **Trouble 04: Communication Trouble**
* **Trouble 05: General System Supervisory**
* **Trouble 06: General System Tamper**
* **Trouble 07: General System Fault**
* **Trouble 08: General System Trouble**
* **Trouble 09: Wireless Device Low Battery**
* **Trouble 10: Wireless Device Supervisory**
* **Trouble 11: Wireless Device Tamper**
* **Trouble 12: Wireless Device Fault**
### Zone Types and Their Descriptions
**Zone Definitions (Programming Section [001]):**
* **00: Null Zone:** Not used.
* **01: Delay 1:** Entry/Exit delay. Common for main entry doors.
* **02: Delay 2:** Secondary entry/exit delay. Can be used for other entry points.
* **03: Instant:** No entry delay. Triggers alarm immediately. Used for windows, secondary doors.
* **04: Interior Stay/Away:** Active when armed Away, bypassed when armed Stay. Used for motion detectors in living areas.
* **05: Interior Delay:** Similar to Interior Stay/Away, but with an entry delay.
* **06: Day/Night:** Active 24 hours, but can be programmed to be silent during the day and audible at night.
* **07: 24 Hour Burglary:** Always active, triggers immediate alarm. Used for safes, panic buttons.
* **08: 24 Hour Fire (Standard):** Always active, triggers fire alarm. Requires smoke detectors.
* **09: 24 Hour Fire (Delayed):** Always active, triggers fire alarm after a delay. Used to prevent false alarms.
* **10: 24 Hour Supervisory:** Always active, reports supervisory condition (e.g., freezer temperature).
* **11: 24 Hour Gas:** Always active, triggers gas alarm. Requires gas detectors.
* **12: 24 Hour Heat:** Always active, triggers heat alarm. Requires heat detectors.
* **13: 24 Hour Water:** Always active, triggers water alarm. Requires flood detectors.
* **14: 24 Hour Carbon Monoxide:** Always active, triggers CO alarm. Requires CO detectors.
* **15: 24 Hour Medical:** Always active, triggers medical alarm. Used for medical alert buttons.
* **16: 24 Hour Panic:** Always active, triggers panic alarm. Used for panic buttons.
* **17: 24 Hour Emergency:** Always active, triggers emergency alarm.
* **18: Momentary Keypad Zone:** Used for momentary key presses on keypads.
* **19: Latching Keypad Zone:** Used for latching key presses on keypads.
* **20: Key Switch Arm/Disarm:** Used with a key switch to arm/disarm the system.
* **21: Key Switch Momentary Arm:** Used with a key switch for momentary arming.
* **22: Key Switch Latching Arm:** Used with a key switch for latching arming.
* **23: Key Switch Momentary Disarm:** Used with a key switch for momentary disarming.
* **24: Key Switch Latching Disarm:** Used with a key switch for latching disarming.
* **25-128:** Various other zone types for specific applications and expanders.
### Wiring Diagrams and Terminal Descriptions
**Terminal Descriptions:**
* **BAT+, BAT-:** Battery terminals. Use to provide backup power and additional current when system demands exceed the power output of the transformer, such as when the system is in alarm. Do not connect the battery until all other wiring is complete.
* **AC:** Power terminals. Connect the battery before connecting the AC. Do not connect the battery or transformer until all other wiring is complete.
* **AUX+, AUX-:** Auxiliary terminals. Use to power modules, detectors, relays, LEDs, etc. (700mA MAX). Connect the positive side of device to AUX+, the negative side to AUX-.
* **BELL+, BELL-:** Bell/Siren power (700mA MAX). Connect the positive side of any alarm warning device to BELL+, the negative side to BELL-.
* **RED, BLK, YEL, GRN:** Corbus terminals. Use to provide communication between the alarm controller and connected modules. Each module has four Corbus terminals that must be connected to the Corbus.
* **PGM1 to PGM4:** Programmable output terminals. Use to activate devices such as LEDs. (PGM1, PGM3, and PGM4: 50mA PGM2: 300mA or can be configured as an input)
* **Z1 to Z8, COM:** Zone input terminals. Ideally, each zone should have one detection device; however, multiple detection devices can be wired to the same zone.
* **EGND:** Earth ground connection.
* **TIP, RING, T-1, R-1:** Telephone line terminals.
* **PCLINK_1:** DLS/SA
* **PCLINK_2:** DLS/SA, Alternate Communicator
**Wiring Notes:**
* **General:** All national wiring rules must be observed. The wiring (cables) used for installation of the alarm system and accessories, shall be insulated with PVC, TFE, PTFE, FEP, Neoprene or Polyamide. Do not route any wiring over circuit boards.
* **SEOL Wiring:** When SEOL resistors are installed at the end of a zone loop, the alarm panel detects if the circuit is secure, open, or shorted. The SEOL resistor must be installed at the end of the loop for proper supervision. To enable SEOL supervision, program section [013], options [1] and [2] to OFF.
* **DEOL Wiring:** When double end-of-line (DEOL) resistors are installed at the end of a zone loop, the second resistor enables the panel to determine if the zone is in open, closed, tampered or faulted. To enable DEOL supervision, program section [013], option [1] to OFF and option [2] to ON. Any zone programmed for Fire or 24-hr Supervisory must be wired with a SEOL resistor regardless of the type of zone wiring supervision selected for the panel.
* **Telephone Line Wiring:** Wire the telephone connection terminals (TIP, Ring, T-1, R-1) to an RJ-31x connector. For connection of multiple devices to the telephone line, wire in the sequence indicated.
* **Ground Wiring:** Using an insulated green wire (minimum 22AWG), connect the EGND terminal on the Corbus and the grounding wire from the building electrical installation to any of the available holes on the back or side of the metal cabinet.
### Programming Menu Structure
**Basic Programming Access:**
* Enter Installer Programming mode: `[*][8][Installer Code]` (while the system is disarmed).
**Keypad Programming:**
* Programming options are accessed by navigating through the menu (LCD) or by keying in the program section number.
* For toggle options, the name of the option is displayed (LCD) or LEDs 1-8 are illuminated (LED and ICON).
* Use the keypad numbers to toggle options on or off.
* Sections requiring data input, such as phone numbers, display the full data in fields up to 32 characters long (LCD). To input data, use the scroll keys to select a character then press the keypad button corresponding to the number/letter required.
**Quick Setup Programming Examples:**
* **Zone Type/Zone Attribute:** `[001]/[002]`
* **Partition 1 Timers (Entry Delay 1, Entry Delay 2, Exit Delay):** `[005]>[001]`
* **Phone #1:** `[301]>[001]`
* **System Account Code:** `[310]>[000]`
**Module Enrollment:**
* **Auto-enrollment:** `[*][8][Installer Code][902]` subsection `[000]`. Press `[*]` to begin auto-enrollment. Module slots are automatically assigned. Use scroll keys to view slots. Change slot by typing a 2-digit number.
* **Wireless Device Enrollment:** `[*][8][Installer Code][804]` subsection `[000]`. An HSM2HOST or RF keypad must be enrolled first.
* **Pre-Enrollment (Wireless Devices):** Enter each device ID (`[804][001]-[716]`). The device ID is printed on the sticker attached to the device (format: XXX-YYYY). The second step is to press the enrollment button on the device.
* **Confirm Module Enrollment:** Use Installer Programming section `[903]`.
**Template Programming:**
* Use pre-defined templates to quickly apply basic programming and to set up DLS downloading.
* Access via `[899]` at the “Enter Section” screen.
**Testing the System:**
* **Walk Test:** `[901]`
* **Wireless Placement Test:** `[904][000]`
**Function Key Definitions:**
* `[00]` Null Function Key
* `[02]` Instant Stay Arm
* `[03]` Stay Arm
* `[04]` Away Arm
* `[05]` No-Entry Arm `[*][9]`
* `[06]` Chime On/Off
* `[07]` System Test
* `[09]` Night Arm
* `[12]` Global Stay Arm
* `[13]` Global Away Arm
* `[14]` Global Disarming
* `[16]` Quick Exit
* `[17]` Arm Interior
### Expander/Peripheral Devices with Specs
(See
=== WEB RESEARCH: onguard ===
## Lenel S2 OnGuard 8.3 Technical Reference
### Manufacturer and Product
Lenel S2 OnGuard 8.3
### Security Discipline
Access Control
### Product Range and Model Numbers
* **OnGuard 8.3** (Base System)
* **OnGuard 8.2 Update 1** (Previous version, referenced for client installation)
* **OGClient.iso** (Client-only installation image)
* **OG.iso** (Full installation image, includes third-party support)
### Installation Procedures
#### System Requirements
* **Operating System:** Windows 11 (specific usage notes in Appendix)
* **Database:** SQL Server, Oracle, SQL Server Desktop Engine, SQL Express, Azure SQL databases
* **Hardware Key (Dongle):** Parallel port or USB dongle (for hardware licenses)
#### Installation Steps (OnGuard 8.3)
1. **Launch Installer:** Run `setup.exe` from the installation media.
2. **Prerequisites:** The installer will check for and install necessary prerequisites (e.g., .NET Framework, Visual C++ Redistributables).
3. **Welcome Screen:** Click [Next].
4. **License Agreement:** Read and accept the license agreement.
5. **Installation Type:** Select `Standard` or `Custom`.
6. **System Configuration:** Choose one of the following:
* **Server System:** Installs all server features (Platform Server or Custom Server).
* **Client System:** Installs client applications.
* **Monitoring Client:** Installs a client for monitoring only.
* **Badging and Credential Client:** Installs a client for badging and credential management.
* **Note:** `Server System` is disabled if installing a Client System from `OGClient.iso`.
7. **Milestone Support (Optional):** If `Server System` or `Client System` is selected, option to `Add Milestone Support` for Milestone XProtect recorders. Click [Next].
8. **System Options (based on configuration choice):**
* **Server System:**
* Select `Platform Server` (all server features) or `Custom Server` (select individual features).
* Select appropriate database option.
* **Client System:**
* Select `Typical System` (standard features) or `Custom System` (specify server locations and features).
* Select appropriate database option.
* **Monitoring Client/Badging and Credential Client:** Configure database type information.
9. Click [Next].
10. **System Location Information:**
* **Installation Directory:** Accept default or specify a different destination folder.
* **License Server Location:** Accept default or specify a different location.
* **Port:** Default is `8189` for access control system communication. Can be changed via Configuration Editor (Appendix A).
* **Database Login User:** Enter the name of the database login user (default: `Lenel`). Must be customized if changed.
* **Database Location:** Accept default or specify a different location.
* Click [Next].
11. **Custom Setup (if selected in step 7):** Select desired access control system features. Descriptions and disk space requirements are displayed. Click the icon next to a feature for installation choices.
12. Click [Install] to begin.
13. **Progress Bar:** Monitor installation status.
14. **Completion:** Click [Finish].
15. **Reboot:** Reboot if prompted.
16. **Setup Assistant:** Launches automatically after installation.
#### Setup Assistant
* Simplifies OnGuard installations and upgrades.
* Launches automatically after installer finishes.
* Requires Administrator rights to run.
* **Dialog Sections:**
* **Status Pane (left):** Lists tasks with status indicators (green check: success, yellow check: warning/skipped, red X: failed, blue arrow: running, no icon: not run).
* **Main Pane:** Provides data, status, fields, buttons for active task.
* **Description Pane:** Brief description of each task.
#### Security Utility
* Embedded into Setup Assistant.
* Should be run after Windows Update or Service Pack installation.
* Makes security adjustments to the operating system. Review release notes and disclaimer.
#### Configuration Editor
* Embedded into Setup Assistant.
* Shows current configuration of Database and License Server.
* Highlights configuration issues (inconsistent `application.config`/`ACS.INI`, database/license server not found).
* Allows storing encrypted database password in `application.config`.
* **Client Support (Client Connect):** Configures client workstations to connect to LS Login Driver via LS Message Broker service.
* **Options:** Provide database configuration details or a Client Connect file.
* **Client Connect File:** Distributes LS Login Driver connectivity details to client workstations without direct database access.
* **Creation Methods:** Client Connect form (`System Administration > System Options`) or Client Connect Tool.
* **Provisioning Methods:** Manually in Configuration Editor, automatically by placing in `C:\ProgramData\Lnl\clientConnect.ogcc`, or during unattended installations using `ClientConnectFilePath` parameter.
#### System License
* Embedded into Setup Assistant.
* Installs or verifies a valid license.
* Requires a valid license to continue configuration.
* Run manually when purchasing additional licensable features.
#### Service Log On
* Enter Windows user name and password for the account that will run OnGuard software.
* User must have database access and read/write access to OnGuard directory for log files.
#### Database Installation
* For new server installations using SQL Express, Setup Assistant installs a new `ACCESSCONTROL` database.
* **Steps:**
1. Optionally browse for alternate source database (.MDF) file.
2. Optionally browse for alternate database storage path.
3. Click [Install database].
* **Archival Database:** Option to back up the new `ACCESSCONTROL` database if archiving is configured.
#### Database Backup
* For updating existing installations, Setup Assistant provides a method to back up SQL Server or SQL Server Express database before upgrade.
* **Strongly recommended** to make a backup.
* **Procedure:**
1. Accept or modify `Backup set name`, `Backup set description`, `Server backup file path`.
2. Confirm warning.
3. Click [Backup].
4. Troubleshoot errors if backup fails.
* **Notes:**
* Backup path is on the database server workstation (e.g., `C:\Program Files\Microsoft SQL Server\...`).
* Backup path cannot be a network drive; must be local.
* `Browse` button available only if Setup Assistant runs on database server; otherwise `Reset Path` button.
* Only creates backup; use standard SQL tools for restoration.
#### Database Setup and Encryption
* For server installations, Setup Assistant runs Database Setup automatically.
* Sets up database for current OnGuard version, installs reports, sets encryption key management/recovery, updates field encryption, runs Forms Translator.
* **Encryption Key Entry:** Dialog opens for first-time installations, upgrades from OnGuard 8.0 or earlier, or re-encryption.
* Must be performed on workstation with LS Login Driver installed.
* **Options:** `Generate a key from a passphrase` (10-36 characters), `Generate a random key`, `Import a key from a file` (*.og file).
* **Recommendation:** Export encryption key to a file for restoration. Mandatory for random keys.
* **Important:** Exported key file is a tightly-controlled cryptographic resource for disaster recovery.
* **Blocking Database Connections:**
* OnGuard 8.1+ automatically blocks connections for Microsoft SQL.
* For Oracle, manual blocking is required (disconnect from network or limit access via `SQLNET.ORA` with `tcp.validnode_checking = yes` and `tcp.invited_nodes = (localhost,<yourOracleServerHostName>)`).
* Stop all OnGuard services except LS License Server, LS Message Broker, LS Login Driver.
* Re-enable connections after re-encryption.
* **Encryption Key Troubleshooting:**
* **Issue:** Encryption key not generated (Login Driver not installed or not Message Broker host).
* **Resolution:** Confirm empty `Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Lenel\OnGuard\LD` registry entry. Run Database Setup on the correct workstation and provide encryption key details.
* **Issue:** `Login Driver is not connected to the message broker.`
* **Resolution:** Stop LS Login Driver service, run as application, check for errors. Refer to specific error messages below.
* **Issue:** `Encryption key set up for this Login Driver does not match the database in use.`
* **Resolution:** Open Login Driver as application, `Edit > Set Encryption Key`, provide correct passphrase or *.og file.
* **Issue:** `Encryption key loading failed...The data is invalid.`
* **Resolution:** Configure Login Driver with same encryption key as database (`Edit > Set Encryption Key`).
* **Issue:** `Encryption key loading failed...Login failed for user.`
* **Resolution:** `Edit > Change Database Password`, update password to match LENEL password.
* **Issue:** `Login Driver is not connected to the Message Broker because you must set the RabbitMQ LD credentials.`
* **Resolution:** Provide encryption key and connect to database via ODBC. Login Driver will prompt for RabbitMQ LD credentials.
#### OnGuard Logs Folder
* Default location: `C:\ProgramData\Lnl\logs`.
* Users need Read, Write, and List Folder Contents permissions.
#### Remotely Hosted Databases
* If using Windows Authentication and Live database is remote, LS Site Publication Server (Enterprise/Distributed ID) might need to log on as a specific user with NT authentication access.
* **Configuration:**
1. `Control Panel > Administrative Tools > Services`.
2. Double-click target service.
3. `Log On` tab, select `This account`.
4. Enter username and password (use [Browse] and [Check Names]).
5. Click [OK].
6. Restart service.
### Installing OnGuard on a Client Machine
* Two general steps: install software, verify license.
* Does not require database installation, Database Setup, license installation, or hardware key.
* **Methods:**
* Install from `OGCLIENT.iso` (client-only features, smaller size, excludes Crystal Reports, RabbitMQ, Erlang, OnGuard Modules).
* Silent installation using PowerShell wrapper script with `OGCLIENT.iso` or `OG.iso`.
### Database Authentication for Web Applications
* Required for Oracle databases and browser-based OnGuard applications.
* **Methods:**
* **Windows Authentication:**
* **SQL Server:** Add Windows user to SQL Server (SQL Server Management Studio: `Security > Logins > New Login`). Set `Login name` as `<server-name>\<username>`, select `Windows authentication`. Map user to `<Server Name>lenel` database with `db_owner` and `public` roles (or minimum `public`, `db_datareader`, `db_datawriter`, `db_ddladmin`, `db_executor`). Verify `application.config` for Windows authentication.
* **Oracle:** Create new Oracle user with Windows authentication credentials (SQLPlus: `CREATE USER "<OPS$DOMAIN>\<DOMAINUSER>" ... IDENTIFIED EXTERNALLY ... GRANT CONNECT, RESOURCE, LENEL_RESTRICTEDUSER_ROLE TO "OPS$DOMAIN\DOMAINUSER";`). Verify `sqlnet.ora` has `SQLNET.AUTHENTICATION_SERVICES=(NTS)`.
* **Provide Credentials in Protected File:** Store authentication information in `application.config`. Highly recommended to secure with Access Control Lists (ACL). Not recommended if Windows authentication is not used.
### Logging Into the OnGuard System
#### Windows User Permissions
* Windows user logged into OnGuard applications must have read/write access to the OnGuard directory for log files.
#### Error Messages (Password-related)
* **Database password violations:** `Your password is a keyword that is not allowed.` (Corrects Database password)
* **Database password violations:** `Your password cannot be blank. Please enter a password.` (Corrects User password)
* **User password violations:** `Passwords cannot be the same as the user name.` (Corrects User password)
#### Accounts
* System Administrator creates unique accounts for each user with specific permissions.
* **Default Accounts (samples):**
* `SA` / `SA` (system account, unlimited access, cannot be deleted, password must be changed on first login).
* `admin` / `sample` (user)
* `user` / `sample` (user)
* `badge` / `sample` (user)
* **Security Recommendation:** Create an SA Delegate user with all permissions, then disable the default SA account.
#### Log In (without Single Sign-On)
1. Start desired application.
2. If prompted, select database from ODBC system databases. Click [OK].
3. Log On window:
* `User name`: Type assigned user name (first time: `SA`).
* `Password`: Type assigned password (first time: `SA`). Characters appear as `*`.
* `Directory`: Select directory (default: `<Internal>`).
* `Remember user name and directory`: Optional checkbox.
* Click [OK].
4. If authorization warning appears, click [Yes].
#### Single Sign-On (SSO)
* Logs into OnGuard with same user name and password as Windows authentication (or LDAP).
* **Notes:**
* Windows Authentication should be used for SSO. Anonymous Authentication for other scenarios.
* Explicit username/password for directory authentication is discouraged; use view-only accounts if necessary.
* Assigning both internal and directory accounts increases flexibility but also security risk. Standardize on one.
* **Directory Types Supported:** Microsoft Active Directory, Microsoft Windows NT 4 Domain, Microsoft Windows Local Accounts, LDAP.
* **Automatic SSO:** Users start OnGuard and are automatically logged in under their Windows account/directory. Supported with Windows domain accounts.
* **Manual SSO:** Users manually enter Windows or LDAP account information (user name and password). Can select different configured directory. Supported with Microsoft Active Directory, Microsoft Windows NT 4 Domain, and LDAP.
* **Configuration:** System Administrator must add a directory and link a user account to it.
#### Troubleshoot Logging In
* Verify correct user name/password for selected directory.
* Accept authorization warning.
* Verify valid license is installed:
* License Server settings correct (Configuration Editor).
* LS License Server service running.
* Software-based licenses activated.
* USB licenses have License Key Drivers installed.
* If SSO, ensure PC user is linked to an internal OnGuard user via operational directory.
* Verify LS OpenAccess service is running.
#### LenelS2 Console
* Web-based application to launch OnGuard web/desktop applications and third-party apps/websites.
* Access via `https://<hostname>:8080`.
* Requires OnGuard username and password.
* Displays cards for licensed/installed applications.
* Desktop applications must be installed locally to be launched from Console.
* Users can re-arrange, re-color, create custom cards, or modify templates (depending on permissions).
### Accounts and Passwords
#### Accounts
* System Administrator creates unique accounts and assigns permissions.
* SA Delegate user can be created to disable default SA account for enhanced security.
* **Default Accounts Table:**
| User name | Password | Type |
| :-------- | :------- | :--- |
| SA | SA | system account |
| admin | sample | user |
| user | sample | user |
| badge | sample | user |
* **Note:** Default SA password must be changed on initial login.
#### Passwords
* OnGuard checks user passwords against standards if SSO is not used.
* **Password Policies (configurable):**
* Minimum password length.
* Complex passwords (mix of uppercase, lowercase, numeric, non-alphanumeric).
* Case-sensitivity.
* Password expiration (after specified days, warning, force change on next login).
* Rejection of prohibited keywords.
* Rejection of prior passwords (based on specified number).
* Inactivity timeout.
* Invalid login lockout.
* **Notes:**
* Upgraded systems support current passwords until policies require change.
* OnGuard database user password checks: not blank, not same as username, not prohibited keyword.
* Database passwords conform to specific database rules (e.g., SQL Server/Oracle 12c are case-sensitive).
* Password policies can be configured via OnGuard Users browser-based client application.
* Oracle databases: `System`/`Manager`, `Internal`/`Oracle`, `Sys`/`Change_On_Install` are not allowed together.
* **Password Standards (for strong passwords):**
* Cannot be blank.
* Cannot be same as user name.
* Cannot be on list of prohibited keywords.
* May require numbers, letters, symbols (spaces acceptable).
* Case-sensitive.
* Maximum length: 127 characters. Minimum: 1. Default: 8.
#### Change the Database Password
* Default database password: `Secur1ty#`.
* Database password must be synchronized between SQL Server/Oracle/SQL Server Desktop Engine and Login Driver.
* **Procedure (using Login Driver):**
1. Stop LS Login Driver service, run as application.
2. Right-click system tray icon, select `Open`.
3. Login Driver window: `Edit > Change Password`.
4. If password is weak, Account Passwords window appears (refer to Password Standards).
5. Click [Continue]. Select `LENEL` account, click [Change Password].
6. Enter `Old password`, `New password`, `Confirm password`.
7. If Login Driver and database are on different machines, checkbox `When I change this password on the Login Driver, do not change the password on the database server. I will change the password manually on the database server.` appears.
* Unselected (default): Password changed in both places (sent as plain text over network).
* Selected: Password changed in Login Driver only; manual change required on database server.
8. Click [OK] to save.
9. Exit LS Login Driver application, restart service.
#### Change the System Administrator Password for the Database
* For SQL Server Desktop Engine and SQL Server, this is the `SA` account.
* For Oracle, there are several system accounts.
* **Procedure (using Database Setup):**
1. Launch Database Setup.
2. If upgrading, select `Live` or `Archival` database. Select `Add/remove missing system data for current build`.
3. Click [Continue].
4. Database Setup Progress window: Click [Execute].
5. If upgrading, warning to back up database appears. Click [Yes].
6. Database installs. Anomalies may be checked. Select known anomalies and click [Continue].
7. Database is encrypted using encryption key from Login Driver.
### Configuration Editor
* Used to modify `application.config` and `ACS.INI` files.
* **Database Section (page 92 of Installation Guide):** Used to modify database settings, including the database name (default `AccessControl`).
* **Advanced Database Section (page 93 of Installation Guide):** Used to verify `application.config` for Windows authentication and store `lenel` user account credentials.
### Certificates
#### General Description
* **TLS (Transport Layer Security) / SSL (Secure Socket Layer) certificates:** Installed on web servers and clients for secure encrypted connections.
* Private certificate on server, public certificate sent to client.
* Used by LS Message Broker service, LS Site Publication Server, LS OpenAccess, NGINX clients (OnGuard Monitor, OnGuard Credentials, LenelS2 Console).
#### Where to Get Certificates
* **Trusted Certificate Authority:** Certificates expire in 1-3 years.
* **Self-signed certificate:** Installed by default during OnGuard installation/upgrade. Expires in 3 years (OnGuard 8.1+). Primarily for evaluation/demonstration/stand-alone systems. Causes browser security alerts. Cannot be revoked; must be replaced/rotated if compromised.
#### Certificate Management
* If LS Web Server (NGINX) and LS Message Broker Service (RabbitMQ) are on the same server, they use the same certificate. Otherwise, each requires a unique certificate.
* **Viewing Existing Certificate:** Refer to `Configure the Name and Location of the Certificate` (page 107).
* **Installing a Certificate Manually:**
* Delete existing certificates if re-issuing.
* Install trusted certificate on OnGuard server (where OpenAccess service runs) for mobile live events.
* Restart LS Web Service and LS Message Broker service after changes.
* **Self-signed certificate re-issue:** Run `lnl_app_server_certificate_installer.exe` with `-key`, `-cert`, `-keystore`, `-cn` parameters (e.g., `C:\ProgramData\Lnl\nginx\conf\ls_server_cert_key.pem`, `C:\ProgramData\Lnl\nginx\conf\ls_server_cert.pem`, `C:\Program Files (x86)\OnGuard\LicenseServerConfig`, `<virtual computer name>`).
* **Import custom certificate:** Generate CSR, obtain certificate from CA, install certificate and key onto NGINX/LS Web Server. If private key is encrypted, configure NGINX/RabbitMQ with passphrase or decrypt key.
* **Decrypt private key file:** `openssl rsa -in key.pem -out server.key`.
#### LS Web Server (NGINX) Certificate Configuration
* Default certificate location: `C:\ProgramData\Lnl\nginx\conf`.
* `nginx.conf` file contains `ssl_certificate` (public key, `ls_server_cert.pem`) and `ssl_certificate_key` (private key, `ls_server_cert_key.pem`).
* Intermediate certificates: Concatenate server certificate and intermediate certificate into `ls_server_cert_key.pem` (server first, then intermediate).
* **Encrypted private key:** Add `ssl_password_file ls_server_cert_key.pass;` to `nginx.conf` and place passphrase in `ls_server_cert_key.pass` file.
* **Important:** Repeat process if OnGuard is reinstalled or upgraded. Never share key file.
#### LS Message Broker Service (RabbitMQ) Certificate Configuration
* By default, uses same certificate as NGINX.
* **Changing certificate location:** Edit `C:\Users\<username>\AppData\Roaming\RabbitMQ\advanced.config`.
* Update `ssl_options` section: `cacertfile`, `certfile`, `keyfile` paths.
* **Encrypted private key:** Add `{password, "passphrase"},` after `keyfile` line.
* **Performing Peer Verification:** Configure LS Message Broker server to reject clients without valid certificates.
* Edit `C:\Users\<username>\AppData\Roaming\RabbitMQ\advanced.config`: Add `{verify, verify_peer},` and `{fail_if_no_peer_cert, true}`.
* Add `[LSMessageBrokerClientSecurity] CertificatePath=<"path to client-side certificate">` to `acs.ini` on all clients/servers.
* Modify `appSettings` in application configuration files (e.g., `Lnl.OG.EventContextProviderService.exe.config`): Add `<add key="X509CertPath" value="path/to/client/cert/cert.p12"/>`.
* **Notes:** Client-side certificates must be `.p12` format and decrypted.
#### Apple Wallet Certificates
* For visitors to add passes to Apple Wallet.
* **Requirements:**
1. Obtain certificates from Apple Developer portal (`http://developer.apple.com/account`). Requires Apple Developer account.
2. Download Apple Wallet Intermediate CA certificate `AppleWWDRCA.cer`.
3. Generate a pass signing certificate (`<YourCertificateName>.p12`) for your organization with specific Team identifier and Pass type identifier (format: `pass.com.<your organization domain>.OnGuard-Visitor`).
4. Install certificates:
* Install `AppleWWDRCA.cer` into Local Machine certificate store, in the Intermediate Certification Authorities folder.
* Install `<YourCertificateName>.p12` into Local Machine certificate store, in the Personal folder.
### Uninstallation
#### Files Not Removed During OnGuard Uninstallation
* Installation packages not installed with OnGuard.
* Common system components shared by other applications (prerequisites).
* OnGuard localizations with customer data/customizations.
* Customized configuration files (`.ini`, `.config`, etc.).
* Files created during application use (reports, logs).
* Registry options and settings for re-installation support.
### OnGuard Online User Manual (Older Version - Jan 2005)
#### Related Documentation
* `Alternative Wiring Configurations Guide`
* `Hardware Installation Guide`
#### Chapter 2: Managing Access
* Covers step-by-step operator procedures for timezones, access levels, and cardholder management.
#### Chapter 3: Monitoring Alarms
* Covers alarm-monitoring operations:
* Deleting events.
* Acknowledging events.
* Using the System Hardware Tree.
* Pending alarms.
* Tracing alarms.
* Filtering alarms.
* Toolbar/menu behavior.
* Includes a glossary appendix.
### Default Codes
* **Application Login:**
* User name: `SA`, Password: `SA` (system account, must be changed on first login)
* User name: `admin`, Password: `sample`
* User name: `user`, Password: `sample`
* User name: `badge`, Password: `sample`
* **Database Login:**
* User name: `Lenel`, Password: `Secur1ty#` (default, highly recommended to change)
* **Port:** `8189` (default for access control system communication)
### Fault/Event/Alarm Code Tables
* (Not explicitly detailed in the provided installation guide, but the older user manual mentions "Monitoring Alarms" and "deleting events, acknowledging events, tracing alarms, filtering alarms" which implies the existence of such codes. Further research would be needed to extract specific codes and descriptions.)
### Zone Types and Descriptions
* (Not explicitly detailed in the provided installation guide or the older user manual. Further research would be needed to extract specific zone types and descriptions.)
### Wiring Diagrams and Terminal Descriptions
* (Not explicitly detailed in the provided installation guide or the older user manual, but the older user manual references an `Alternative Wiring Configurations Guide` and `Hardware Installation Guide`. Further research would be needed to extract specific wiring diagrams and terminal descriptions.)
### Programming Menu Structure
* (Not explicitly detailed in the provided installation guide or the older user manual. The installation guide mentions "Custom Setup" for selecting features, but not a full menu structure. Further research would be needed to extract specific programming menu structures.)
### Expander/Peripheral Devices with Specs
* (Not explicitly detailed in the provided installation guide or the older user manual. Further research would be needed to extract specific expander/peripheral devices and their specifications.)
### Commissioning Steps
* (Covered broadly under "Installation Procedures" and "Setup Assistant" in the installation guide, but not as a distinct, comprehensive commissioning guide. Further research would be needed for a dedicated commissioning process.)
### Common Fault Diagnosis
* **Encryption Key Troubleshooting:** (Detailed in "Database Setup and Encryption" section above).
* **Login Driver Connection Issues:** (Detailed in "Database Setup and Encryption" section above).
* **Remotely Hosted Database Connection Issues:** (Detailed in "Remotely Hosted Databases" section above).
* **License Troubleshooting:** (Detailed in "Install Your OnGuard License" section above).
### Compliance Standards Met
* (Not explicitly detailed in the provided installation guide or the older user manual. Further research would be needed to extract specific compliance standards.)
### Other Technical Details
* **Universal Time Conversion Utility:** Converts local times in database to Coordinated Universal Time for multi-time zone compatibility. Recommended for server upgrades from OnGuard versions earlier than 6.3.
* **RabbitMQ LD Credentials:** Login Driver holds RabbitMQ credentials. Must update password in RabbitMQ console tool before changing in Login Driver. Configured via `Edit > Set RabbitMQ LD credentials` in Login Driver application.
* **NGINX:** Used as LS Web Server.
* **OpenAccess:** Service that needs to be running for login.
* **LS Site Publication Server:** Used in OnGuard Enterprise installations.
* **LS Message Broker Service:** Secured by TLS. Clients include LS Site Publication Server, LS OpenAccess.
* **Crystal Reports:** Excluded from `OGCLIENT.iso`.
* **Erlang:** Excluded from `OGCLIENT.iso`.
* **VMware ESX:** Software licenses supported in this virtual environment for License Server only. Not for dongle-based licenses.
* **LenelS2 Connect™ portal:** `https://connect.lenels2.com/s/downloads` for compatibility charts and downloads.
* **License Activation URL:** `https://activate.lenels2.com:443` (requires TCP port 443 open).
* **License Activation Phone/SMS:** 1-866-788-5095 option (5) or email `sig@carrier.com` (US/Canada); +44 7937 947945 (EMEA SMS); +48 5832 62240 or email `sig.emea@carrier.com` (EMEA Phone).
* **LenelS2 Knowledgebase:** `https://kb.lenels2.com` for license installation issues.
* **ODBC:** Used for database connections.
* **LDAP:** Supported directory for Single Sign-On.
* **`application.config` and `ACS.INI` files:** Configuration files. Manual editing not advised; use Configuration Editor.
* **`dbconfig.xml`:** Configured by Configuration Editor for Reports and Dashboards.
* **`AccessControl_ReportsConfig`:** Default name for ReportsConfig database.
* **`FLEXnet` folder:** `C:\ProgramData\FLEXnet` (delete files here for Activation Code troubleshooting).
* **`appactutil.exe`:** Used for license return troubleshooting (`appactutil.exe -shortcode OnGuard.asr -return SCASR_FID_1_OnGuard`).
* **`SQLNET.ORA`:** Oracle configuration file for network settings.
* **`X509CertPath`:** XML key in application configuration files for client-side certificates (e.g., `cert.p12`).
* **`AppleWWDRCA.cer`:** Apple Wallet Intermediate CA certificate.
* **`pass.com.<your organization domain>.OnGuard-Visitor`:** Naming convention for Apple Wallet pass signing certificate.
| Concept | Description |
|---|---|
| AEpu (Access Point Unit) | Decentralised controller — processes access decisions locally; continues operation if server offline |
| Authorisation | Access rights linked to people, not badges — badge replacement does not require re-programming |
| Identification | Access based on fingerprint only (1:N) |
| Verification | Access based on badge + fingerprint (1:1) |
| Third-party Interface | Single source of information — AEOS exports personal data, authorisations, and events to HR/PSIM/time tracking |
| Key Box Integration | AEOS monitors key status and controls key access |
| Fault / Display | Description | Likely Cause | Action |
|---|---|---|---|
| AEpu Offline | Controller not communicating with server | Network fault, IP conflict, power fault | Check Ethernet connection and power. Verify IP address. Check firewall rules. |
| Access Denied | Card presented but access denied | No authorisation, expired card, wrong time schedule | Check cardholder authorisation in AEOS software. Verify time schedule and card expiry. |
| Card Not Read | Card presented but not recognised | Wrong card technology, card not enrolled | Check card technology matches reader. Enrol card in AEOS. |
| Door Forced | Door opened without credential | Forced entry, door contact fault | Investigate door. Check door contact wiring. Review event log. |
| Reader Fault | Reader not communicating with AEpu | Wiring fault, reader power fault | Check Wiegand/OSDP wiring. Check reader power supply. |
| Software Alarm | Alarm event in AEOS software | Forced door, tamper, duress | Review alarm in AEOS event log. Investigate cause. Acknowledge alarm. |
| Terminal | Function | Notes |
|---|---|---|
| Ethernet (RJ45) | Network connection | IP connection to AEOS server |
| +12–28V DC | Power supply | 12–28V DC, 250 mA per AEpu |
| GND | Common ground | Must be continuous |
| D0 (Wiegand) | Wiegand Data 0 | From reader; green wire convention |
| D1 (Wiegand) | Wiegand Data 1 | From reader; white wire convention |
| A+ (OSDP) | RS-485 positive | Twisted pair with B−; OSDP protocol |
| B− (OSDP) | RS-485 negative | Twisted pair with A+ |
| Lock +/− | Door lock output | Connect to fail-safe or fail-secure lock |
| Door Contact | Door open/closed monitor | Voltage-free input; NC recommended |
| REX | Request to exit | Push-to-make input |
| Tamper | Enclosure tamper | Monitored input |
NEDAP AEOS — ACCESS CONTROL & SECURITY MANAGEMENT Source: Nedap Security Management — Access Control UK (2019) Manufacturer: Nedap N.V., Groenlo, Netherlands SYSTEM OVERVIEW: AEOS is an advanced IP-based access control and security management platform. It uses decentralised intelligence — each AEpu controller processes access decisions locally. The system continues to operate if the server connection is unavailable. AEOS is standardised, enabling seamless integration with third-party systems. ARCHITECTURE: Server: Windows Server with MS SQL database Controllers: AEpu (Access Point Units) — IP-connected, decentralised AEpu3 / AP4003X: 4-in-1 reader interface; up to 4 doors per controller Power: 12–28V DC, 250 mA per AEpu Communication: Ethernet (IP), Wiegand, OSDP, RS-485 CARD TECHNOLOGIES SUPPORTED: MIFARE Classic, MIFARE DESFire HID Proximity, HID iCLASS EM4100 (125 kHz) Biometric (fingerprint, iris — via third-party readers) NFC / mobile credentials KEY FEATURES: Authorisations linked to people, not badges — badge replacement is simple Identification (1:N fingerprint) and verification (badge + fingerprint) Third-party database integration: HR, payroll, time tracking, PSIM, room booking Event export to third-party systems (personal data, authorisations, events) Key box management — AEOS monitors key status Visitor management Locker management USB desktop reader support SECURITY: FIPS 140-2 certified cryptographic algorithms Cloud services, servers, web clients, and mobile apps secured with HTTPS/TLS MS SQL database supports TLS and TDE (AES 256-bit encryption) SCALABILITY: Small commercial buildings to global multi-site enterprises Compatible with existing IT infrastructure Integration with all commonly used access control products APPLICATIONS: Government buildings, hospitals, airports, schools, production sites, public spaces
| Document | Source | Link |
|---|---|---|
| AEOS Access Control UK Brochure | nedapsecurity.com | Download PDF |
| AEOS Product Page | nedapsecurity.com | View Online |
| AEOS AP4003X Controller Specs | sourcesecurity.com | View Online |
| Product | Type | Notes |
|---|---|---|
| Net2 ACU | 1-door controller | Networked, RS-485 or TCP/IP |
| Net2 ACU2 | 2-door controller | Networked, RS-485 or TCP/IP |
| Net2 Nano | Mini 1-door controller | Compact, TCP/IP |
| Net2 Entry | Video door entry integration | IP-based video intercom |
| Switch2 | Standalone 1-door | No software required |
| Compact | Standalone 1-door mini | Flush-mount, no software |
| 10x | Standalone 1-door | Vandal-resistant, external |
| Level Name | Permissions | Typical Use |
|---|---|---|
| All Areas | All doors, 24/7 | Typically for senior management |
| Office Hours | All internal doors, Mon–Fri 08:00–18:00 | Standard office staff |
| Restricted | Specific doors only, specific times | Contractors, visitors |
| Emergency | All doors, override schedules | Fire wardens, security |
| Credential | Default | Notes |
|---|---|---|
| Default PIN | 0000 | Change immediately on commissioning |
| Admin Password | Set during install | Net2 software login password |
| Engineer Access | Via Net2 software | No on-panel engineer code |
| Code / Display | Description | Likely Cause | Action |
|---|---|---|---|
| Controller Offline | Controller not communicating with Net2 server | Network fault, power loss, IP address change | Check network cable and power. Verify IP address in Net2 software. Ping controller. |
| Card Not Found | Card presented but not recognised | Card not enrolled, wrong format, card damaged | Re-enrol card. Check card format matches reader. Test with known-good card. |
| Access Denied | Card recognised but access not granted | Access level incorrect, time schedule, anti-passback | Check user access level. Verify time schedule. Check anti-passback status. |
| Door Held Open | Door held open alarm triggered | Door not closing properly, door held by user | Check door closer. Adjust held-open time in Net2 software. |
| Forced Entry | Door opened without valid credential | Door forced, magnetic lock failure, REX fault | Inspect door and lock. Check REX (request to exit) sensor. |
| Reader Fault | Reader not responding | Wiring fault, reader power loss, RS-485 fault | Check reader wiring. Verify power supply. Check RS-485 bus. |
| Lock Fault | Lock not releasing | Lock wiring fault, power supply fault, relay fault | Check lock wiring and power. Test relay output on controller. |
| Anti-Passback Violation | User attempting to re-enter without exiting | Anti-passback enabled, user tailgated | Reset anti-passback for user in Net2 software. |
| Database Error | Net2 software database corruption | Disk fault, improper shutdown | Restore from backup. Run Net2 database repair utility. |
| Time Sync Fault | Controller time out of sync | NTP server unreachable, manual time set | Check NTP settings in Net2. Verify server time. |
| Terminal | Function | Notes |
|---|---|---|
| +12V | Power input from PSU | 12V DC, 1A min per controller |
| 0V | Common ground | Must be continuous |
| D+ | RS-485 data positive | Twisted pair with D− |
| D− | RS-485 data negative | Twisted pair with D+ |
| LOCK+ | Electric lock positive | Fused at 1A |
| LOCK− | Electric lock negative | Via relay output |
| REX | Request to exit input | Normally open push button |
| DOOR | Door contact input | Normally closed magnetic contact |
| READER+ | Reader power positive | 12V DC |
| READER− | Reader power negative | Common ground |
| DATA | Reader data (Wiegand D0) | Green wire — Wiegand protocol |
| CLOCK | Reader clock (Wiegand D1) | White wire — Wiegand protocol |
| Wire Colour | Function | Notes |
|---|---|---|
| Red | +12V | Power supply to reader |
| Black | 0V | Common ground |
| Green | D0 (Data 0) | Wiegand data line 0 |
| White | D1 (Data 1) | Wiegand data line 1 |
| Orange | LED control | Optional — LED override from controller |
| Blue | Buzzer control | Optional — buzzer override from controller |
| Brown | Tamper | Anti-tamper switch |
| Terminal | Function | Notes |
|---|---|---|
| Fail-Safe (Fail-Open) | Lock releases on power loss | Used on fire exit doors — required by BS 7273 |
| Fail-Secure (Fail-Locked) | Lock remains locked on power loss | Used on secure areas — not suitable for fire exits |
| Magnetic Lock | Fail-safe — releases when power removed | Requires door contact and REX sensor |
| Electric Strike | Fail-secure or fail-safe options | Check manufacturer specification |
| Electric Bolt | Fail-secure — bolt retracts on power | Used on high-security doors |
=== WEB RESEARCH: paxton ===
## Paxton Net2 Switch2 Compact Access Control System - Full Technical Reference
### Manufacturer and Product Name
Paxton Net2 Switch2 Compact Access Control System
### Discipline
Access
### System Overview
* **System Type:** Standalone access control system.
* **Architecture:** Control unit is separate from the user interface (reader/keypad). The control unit is mounted on the 'safe' side of the door, with only the keypad or reader outside.
* **Reader Compatibility:** Can be used with any of the readers in the Paxton range (PROXIMITY, CARDLOCK, TOUCHLOCK).
* **Inputs:** Door contact, exit button.
* **Outputs:** Alarm sounder output, volt-free relay for lock control (fail closed and fail open locks).
* **Installation:** Extremely simple to install and configure. Each controller can be configured to use the same site code for user tokens.
* **Security:** Provides high security as the controller is installed on the secure side of the door. Door contact can monitor for forced doors, triggering an audible alarm.
* **Lock Output:** Changeover relay for simple connection of either fail-open or fail-closed electric locks.
* **Token Compatibility:** Cards for PROXIMITY and CARDLOCK Switch2 systems are identical to those used with equivalent compact systems, allowing for mixed installations (Switch2 for high security, Compact for low security).
* **Event Recording:** Ideal for sites where the recording of events is not required.
### Product Range and Model Numbers
* **Switch2 - Controller:** Sales Code: 405-321
* **Switch2 - Controller, 12V 1A PSU, with plastic housing:** Sales Code: 242-166
* **Compatible Readers:** PROXIMITY, CARDLOCK, TOUCHLOCK readers (e.g., Proximity reader – P75).
* **Compatible Peripherals:** Paxton exit button – E50.
### Complete Technical Specifications (TDS-1037)
**Electrical:**
* **Current Consumption:** 80mA
* **Operating Voltage:** 10V - 14V DC
* **Relay Switchable Voltage:** 24V DC
* **Relay Switchable Current:** 4A
* **Alarm Output Current:** 1A
* **Reader Ports per ACU:** 1
* **Readers/Keypads per ACU:** 2
* **Total ACU Reader Port Output Current:** 500mA (check current draw on individual readers)
**Environment:**
* **Operating Temperature:** -20°C to +55°C (-4°F to +131°F)
* **Moisture Resistance:** Low (if used externally, it must be protected in a weatherproof housing)
* **Vandal Resistance:** No
**Hardware:**
* **Maximum Total Users/Tokens:** 100 card packs (up to 5,000 tokens/users)
* **Door Open Time:** 1 sec - 60 secs (Default: 7 seconds)
* **PIN Length:** 4-8 digits
* **Number of Codes (TOUCHLOCK):** 50
* **Code Length (TOUCHLOCK):** 4-8 digits
* **Handsfree Compatible:** Yes (requires interface)
* **Silent Operation:** Yes
* **3rd Party Reader Support:** No
* **Data Retention during a total power loss:** >10 years
**Dimensions:**
* **Height:** 71 mm (2.8”)
* **Width:** 70 mm (2.8”)
* **Depth:** 23 mm (0.9”)
### Default Codes
* **TOUCHLOCK Keypad Default User Code:** 1234 (opens the door before programming code is fully entered).
* **Programming Code (TOUCHLOCK):** Chosen by installer during initialisation (cannot be 123456).
* **No specific default engineer, master, installer, or duress codes are provided as they are user-defined during programming or system initialisation.**
### Fault/Event/Alarm Code Tables
* **Door Forced Alarm:** Activated when door contacts are fitted and the door is forced open. The bell/alarm output is triggered.
* **20 Wrong Keystrokes Lockout (TOUCHLOCK):** Keypad locks out for 60 seconds after 20 incorrect key presses.
* **LED Indicators:**
* **Initialising (First Power Up):** Control unit beeps 3 times/second. Red LED steady, amber LED flashes slowly, green LED flashes quickly.
* **Access Denied:** Red LED lit, reader produces a beep.
* **Access Granted:** Green LED lit.
* **Adding Additional Proximity Card Pack:** Amber LED flashes with green & red LEDs off (during step 1), all LEDs lit (after step 2).
### Zone Types and Descriptions
* **Zoning (PROXIMITY/CARDLOCK):** Allows limiting access by token colour. Requires PROXIMITY or CARDLOCK function card pack.
* **Colour Groups:** Access privileges can be set based on token colour (e.g., green, amber, red tokens for different access levels).
* **Time Zones:** Can be used with a time clock to change the validity of colour groups at different times of the day. This is dependent on whether the exit wires are shorted together or not.
### Wiring Diagrams and Terminal Descriptions
**Switch2 Control Unit Terminals:**
* **12V:** 12V DC power input/output.
* **0V:** Ground/common for power and other connections.
* **Data:** Data connection for reader/keypad.
* **Clock:** Clock connection for reader/keypad.
* **N.C. (Normally Closed):** Lock relay contact.
* **N.O. (Normally Open):** Lock relay contact.
* **COM (Common):** Lock relay contact.
* **EXIT:** Input for exit button or time clock.
* **Contact:** Input for door contact.
* **Bell:** Output for alarm/bell sounder.
**General Wiring Arrangement:**
* **Power Connection:** 12V DC power supply connected to "12V" and "0V" terminals. A 12V power supply with battery backup is recommended. Supply must provide enough current for reader, alarm sounder, and lock.
* **Reader Connection:** Any Paxton reader/keypad can be connected. Readers are colour-coded to correspond to labelled inputs on the control unit (12V, 0V, Data, Clock, LED).
* *Caution:* For 12V d.c readers only. For old 5V readers, refer to specific instructions.
* **Lock Connection:** 12V DC power for the lock is taken from the Switch2 "12V" terminal. The lock is controlled by switching the 0V feed via the voltage-free relay contacts.
* **Fail-open lock:** 0V linked to 'N.C.' terminal.
* **Fail-closed lock:** 0V linked to 'N.O.' terminal.
* In both configurations, the 0V feed to the lock is supplied via the 'Com' terminal.
* **Exit Button / Time Zone Control:** A 'push to make' exit button connects between "Exit" terminal and "Black" terminal (0V). Alternatively, a time clock with a voltage-free changeover contact can hold a door unlocked during programmed times. For swipe card/proximity systems, a time clock can change validity of colour groups.
* **Door Contact:** Connected between "Contact" terminal and "Black" terminal (0V). Must be a closed contact when the door is shut. Used for 'Door forced' alarm and Auto-lock feature.
* **Alarm / Door Bell Sounder:** Connected to "Bell" and "12V" terminals. Max 1A at 12V DC. "Bell" terminal connects to 0V during an alarm. Can be used as a doorbell when door contacts are not connected (with Paxton keypad).
* **Multiple Readers:** Two PROXIMITY or CARDLOCK readers can be wired in parallel, colour for colour, to the same controller for read-in and read-out access control.
### Full Programming Menu Structure (TOUCHLOCK Keypad with Switch2)
**Initialising the Keypad (First Power Up):**
1. Keypad beeps 3 times/second. Red LED steady, amber LED flashes slowly, green LED flashes quickly.
2. Press the bell button (unit stops beeping, green LED flashes).
3. Enter chosen 6-digit programming code and press bell button (green LED flashes faster).
4. Confirm programming code (enter same 6-digit code) and press bell button (green LED goes out, unit beeps twice, all LEDs on).
* *Note:* Programming code should NOT contain '1234'. Default user code is '1234'.
**Entering Programming Mode:**
* Enter the 6-digit programming code. Keypad beeps twice, green LED flashes.
**Programming Options (Accessed via Programming Code + Function Key):**
* **Change Door Open Time (Function Key 5, hold for 3 seconds):**
* Enter time in seconds (01-60). Default is 07 seconds.
* **Change Programming Code (Function Key 6, hold for 3 seconds):**
* Enter new 6-digit programming code, press bell.
* Re-enter new code to confirm, press bell.
* **Silent Operation (Function Key 3, hold for 3 seconds):**
* Press '6' to toggle silent mode (keypad will not beep when keys are pressed).
* **Exit Button Wires Configuration (Function Key 7, hold for 3 seconds):**
* Press '4' to set the button to toggle the lock (door opens until pressed again or toggle code entered).
* Default: Standard exit button (door opens for set door open time).
* **Lockout Function (Function Key 4, hold for 3 seconds):**
* Press '6' to activate lockout (20 incorrect key presses = 60-second lockout).
* **Multi-User Mode (Function Key 2, hold for 3 seconds):**
* Press '6' to enable multi-user mode. Allows adding/deleting individual user codes.
* Default: Single user mode.
* **Set a User Code (Function Key 8, hold for 3 seconds):**
* Enter new user code (4-8 digits), press bell.
* Enter new code again, press bell.
* Final key press defines action type:
* **4:** Normal code (releases lock for set door open time).
* **6:** Toggle code (holds lock open until entered a second time).
* **8:** Duress code (releases lock and energises bell terminal for remote alarm).
* **Data Reset (except Programming Code) (Function Key 9, hold for 3 seconds):**
* Re-enter programming code and hold '9' for a further 3 seconds.
**CARDLOCK/PROXIMITY with TOUCHLOCK Mode (Section 3):**
* If using a KP reader, it must first be initialised in TOUCHLOCK mode.
* **Operating Modes:**
* **Card plus PIN:** Individual user card requires a 4-digit PIN. (Enter 6-digit programming code, then '1', then '1').
* **Assigning PIN:** Present enrolment card, then individual user card. Enter chosen PIN, press bell. Confirm PIN, press bell.
* **Card plus Code:** Valid token PLUS valid user code. (Enter 6-digit programming code, then '1', then '2').
* **Card or Code:** Valid token OR valid user code. (Enter 6-digit programming code, then '1', then '3').
### Expander/Peripheral Devices with Specs
* **Proximity Reader – P75:** Compatible reader.
* **Paxton Exit Button – E50:** Compatible exit button.
* **Handsfree Interface:** Required for handsfree compatibility.
* **12V 1A PSU:** Power supply unit, often housed with the controller (e.g., Sales Code 242-166).
### Commissioning Steps
**Initialising a New System (CARDLOCK or PROXIMITY):**
1. Power up the control unit (it will beep 3 times/second, indicating it needs programming).
2. **Enrolling a Card Pack:**
* Present/swipe enrolment card.
* All tokens in the pack are now validated and can be issued to users.
3. **Adding an Additional Proximity Card Pack:**
* Present the enrolment card from the original card pack (amber LED flashes, green & red LEDs off).
* Present the enrolment card from the new card pack (reader beeps, all LEDs lit, indicating cards are valid).
* Repeat for each reader and additional card packs.
* *Note:* Any valid enrolment card from previous packs can add further packs. Incorrect enrolment card results in red LED and beep.
**Initialising a New System (TOUCHLOCK Keypad):**
1. Follow the steps under "Full Programming Menu Structure" -> "Initialising the Keypad".
**Factory Reset (Switch2 Control Unit):**
1. Turn off power and disconnect Green and Mauve keypad wires from Switch2 terminals.
2. Insert a wire link between the Green and Mauve terminals.
3. Reconnect power (unit will beep 4 times).
4. Disconnect power and remove the link wire, reconnect Green and Mauve wires.
5. Reconnect power (unit will beep 3 times/second). The unit is now ready to be enrolled.
**Factory Reset (TOUCHLOCK Keypad):**
1. Enter programming mode.
2. Hold down '9' for 3 seconds.
3. Re-enter the programming code and hold down '9' for a further 3 seconds. The keypad will be reset (except for the programming code).
* *Note:* If the master code is lost, the Switch2 must be reset to factory settings using the control unit factory reset procedure.
### Common Fault Diagnosis / Technical Help
* **Two Readers on the Same Controller:** Wire PROXIMITY or CARDLOCK readers in parallel, colour for colour.
* **Replacing a White Labelled Control Unit (pre-2004 design):** Old units had 5V DC output on the red voltage terminal. New yellow labelled units have 12V DC. For 5V readers/keypads, the jumper setting on the controller PCB must be changed. Touchlock membrane keypad is not compatible with the new control unit.
* **Initialising with 2 Keypads (K-Series):** Either keypad can initialise the controller. Wire all wires in parallel, colour for colour.
* **Initialising with 2 Keypads (Older Touchlock/SS):** Use the master keypad (yellow wire to yellow terminal). Slave keypad has yellow wire to mauve terminal.
* **Bell/Alarm Output:** A 12V DC alarm sounder (up to 1A) can be wired between 12V and Bell terminals. Load must be considered for power supply rating. If door contacts are fitted, the bell/alarm output activates when the door is forced. On a keypad system, the bell button normally activates this output, but not if a door forced alarm is active.
### Compliance Standards Met
* **EU Directives:**
* Directive 2014/53/EU (Full declaration of conformity at http://paxton.info/3910)
* The Low Voltage (LVD) Directive - 2006/108/EC
* The Electro-Magnetic Compatibility (EMC) Directive - 2004/108/EC
* The Restriction of Hazardous Substances (RoHS) Directive - 2011/65/EU
* **North America:**
* **FCC Compliance (Part 15):**
* Complies with Part 15 of the FCC Rules. Operation subject to: (1) device may not cause harmful interference, and (2) device must accept any interference received.
* Class B digital device. Tested to comply with limits for Class B digital device, providing reasonable protection against harmful interference in residential installation.
* If interference occurs, suggested measures: Reorient/relocate receiving antenna, increase separation between equipment and receiver, connect equipment to different circuit, consult dealer/technician.
* **Industry Canada Compliance:**
* Complies with Industry Canada licence-exempt RSS standard(s). Operation subject to: (1) device may not cause interference, and (2) device must accept any interference.
* **Wiring Methods:** Shall be in accordance with the National Electrical Code (ANSI/NFPA70), local codes, and authorities having jurisdiction.
* **CAN/ULC-S319 Installations:** Terminals, leads, and wiring methods must comply with CSA, C22.1, Canadian electrical code, Part 1, safety standards for electrical installations.
* *Note:* Use of any add-on, expansion, memory, or other module not manufactured or supplied by Paxton invalidates CAN/ULC-S319 certification.
### Other Technical Details
* **Installation Warnings:**
* Read instructions before installing and powering equipment. Keep instructions for future reference.
* Only qualified and trained personnel should install, connect, or test this equipment.
* No user-serviceable parts within the PSU unit.
* Intended for indoor use only in dry locations. Class A product (may cause radio interference in domestic environment).
* Installation must meet National Wiring Regulations and IEC60950-1 standards.
* **Disconnect Devices:** Readily accessible disconnect device (appropriately rated circuit breaker) to disconnect both poles with at least a 3.0 mm contact gap. Internal capacitors discharge within 60 seconds (normal conditions); suitable precautions needed for fault conditions.
* **Protection Device:** Fusing characteristics: T3.15AH250V.
* **Battery Safety Warning:** Risk of explosion if battery is replaced by an incorrect type. Dispose of used batteries according to instructions.
* **Product Suitability:** Not suitable for retail sale. All warranties are invalid if not installed by a competent person.
=== WEB RESEARCH: net2 ===
## Paxton Net2 Switch2 Compact Access Control System - Full Technical Reference
### Manufacturer and Product Name
Paxton Net2 Switch2 Compact Access Control System
### Discipline
Access
### System Overview
* **System Type:** Standalone access control system.
* **Architecture:** Control unit is separate from the user interface (reader/keypad). The control unit is mounted on the 'safe' side of the door, with only the keypad or reader outside.
* **Reader Compatibility:** Can be used with any of the readers in the Paxton range (PROXIMITY, CARDLOCK, TOUCHLOCK).
* **Inputs:** Door contact, exit button.
* **Outputs:** Alarm sounder output, volt-free relay for lock control (fail closed and fail open locks).
* **Installation:** Extremely simple to install and configure. Each controller can be configured to use the same site code for user tokens.
* **Security:** Provides high security as the controller is installed on the secure side of the door. Door contact can monitor for forced doors, triggering an audible alarm.
* **Lock Output:** Changeover relay for simple connection of either fail-open or fail-closed electric locks.
* **Token Compatibility:** Cards for PROXIMITY and CARDLOCK Switch2 systems are identical to those used with equivalent compact systems, allowing for mixed installations (Switch2 for high security, Compact for low security).
* **Event Recording:** Ideal for sites where the recording of events is not required.
### Product Range and Model Numbers
* **Switch2 - Controller:** Sales Code: 405-321
* **Switch2 - Controller, 12V 1A PSU, with plastic housing:** Sales Code: 242-166
* **Compatible Readers:** PROXIMITY, CARDLOCK, TOUCHLOCK readers (e.g., Proximity reader – P75).
* **Compatible Peripherals:** Paxton exit button – E50.
### Complete Technical Specifications (TDS-1037)
**Electrical:**
* **Current Consumption:** 80mA
* **Operating Voltage:** 10V - 14V DC
* **Relay Switchable Voltage:** 24V DC
* **Relay Switchable Current:** 4A
* **Alarm Output Current:** 1A
* **Reader Ports per ACU:** 1
* **Readers/Keypads per ACU:** 2
* **Total ACU Reader Port Output Current:** 500mA (check current draw on individual readers)
**Environment:**
* **Operating Temperature:** -20°C to +55°C (-4°F to +131°F)
* **Moisture Resistance:** Low (if used externally, it must be protected in a weatherproof housing)
* **Vandal Resistance:** No
**Hardware:**
* **Maximum Total Users/Tokens:** 100 card packs (up to 5,000 tokens/users)
* **Door Open Time:** 1 sec - 60 secs (Default: 7 seconds)
* **PIN Length:** 4-8 digits
* **Number of Codes (TOUCHLOCK):** 50
* **Code Length (TOUCHLOCK):** 4-8 digits
* **Handsfree Compatible:** Yes (requires interface)
* **Silent Operation:** Yes
* **3rd Party Reader Support:** No
* **Data Retention during a total power loss:** >10 years
**Dimensions:**
* **Height:** 71 mm (2.8”)
* **Width:** 70 mm (2.8”)
* **Depth:** 23 mm (0.9”)
### Default Codes
* **TOUCHLOCK Keypad Default User Code:** 1234 (opens the door before programming code is fully entered).
* **Programming Code (TOUCHLOCK):** Chosen by installer during initialisation (cannot be 123456).
* **No specific default engineer, master, installer, or duress codes are provided as they are user-defined during programming or system initialisation.**
### Fault/Event/Alarm Code Tables
* **Door Forced Alarm:** Activated when door contacts are fitted and the door is forced open. The bell/alarm output is triggered.
* **20 Wrong Keystrokes Lockout (TOUCHLOCK):** Keypad locks out for 60 seconds after 20 incorrect key presses.
* **LED Indicators:**
* **Initialising (First Power Up):** Control unit beeps 3 times/second. Red LED steady, amber LED flashes slowly, green LED flashes quickly.
* **Access Denied:** Red LED lit, reader produces a beep.
* **Access Granted:** Green LED lit.
* **Adding Additional Proximity Card Pack:** Amber LED flashes with green & red LEDs off (during step 1), all LEDs lit (after step 2).
### Zone Types and Descriptions
* **Zoning (PROXIMITY/CARDLOCK):** Allows limiting access by token colour. Requires PROXIMITY or CARDLOCK function card pack.
* **Colour Groups:** Access privileges can be set based on token colour (e.g., green, amber, red tokens for different access levels).
* **Time Zones:** Can be used with a time clock to change the validity of colour groups at different times of the day. This is dependent on whether the exit wires are shorted together or not.
### Wiring Diagrams and Terminal Descriptions
**Switch2 Control Unit Terminals:**
* **12V:** 12V DC power input/output.
* **0V:** Ground/common for power and other connections.
* **Data:** Data connection for reader/keypad.
* **Clock:** Clock connection for reader/keypad.
* **N.C. (Normally Closed):** Lock relay contact.
* **N.O. (Normally Open):** Lock relay contact.
* **COM (Common):** Lock relay contact.
* **EXIT:** Input for exit button or time clock.
* **Contact:** Input for door contact.
* **Bell:** Output for alarm/bell sounder.
**General Wiring Arrangement:**
* **Power Connection:** 12V DC power supply connected to "12V" and "0V" terminals. A 12V power supply with battery backup is recommended. Supply must provide enough current for reader, alarm sounder, and lock.
* **Reader Connection:** Any Paxton reader/keypad can be connected. Readers are colour-coded to correspond to labelled inputs on the control unit (12V, 0V, Data, Clock, LED).
* *Caution:* For 12V d.c readers only. For old 5V readers, refer to specific instructions.
* **Lock Connection:** 12V DC power for the lock is taken from the Switch2 "12V" terminal. The lock is controlled by switching the 0V feed via the voltage-free relay contacts.
* **Fail-open lock:** 0V linked to 'N.C.' terminal.
* **Fail-closed lock:** 0V linked to 'N.O.' terminal.
* In both configurations, the 0V feed to the lock is supplied via the 'Com' terminal.
* **Exit Button / Time Zone Control:** A 'push to make' exit button connects between "Exit" terminal and "Black" terminal (0V). Alternatively, a time clock with a voltage-free changeover contact can hold a door unlocked during programmed times. For swipe card/proximity systems, a time clock can change validity of colour groups.
* **Door Contact:** Connected between "Contact" terminal and "Black" terminal (0V). Must be a closed contact when the door is shut. Used for 'Door forced' alarm and Auto-lock feature.
* **Alarm / Door Bell Sounder:** Connected to "Bell" and "12V" terminals. Max 1A at 12V DC. "Bell" terminal connects to 0V during an alarm. Can be used as a doorbell when door contacts are not connected (with Paxton keypad).
* **Multiple Readers:** Two PROXIMITY or CARDLOCK readers can be wired in parallel, colour for colour, to the same controller for read-in and read-out access control.
### Full Programming Menu Structure (TOUCHLOCK Keypad with Switch2)
**Initialising the Keypad (First Power Up):**
1. Keypad beeps 3 times/second. Red LED steady, amber LED flashes slowly, green LED flashes quickly.
2. Press the bell button (unit stops beeping, green LED flashes).
3. Enter chosen 6-digit programming code and press bell button (green LED flashes faster).
4. Confirm programming code (enter same 6-digit code) and press bell button (green LED goes out, unit beeps twice, all LEDs on).
* *Note:* Programming code should NOT contain '1234'. Default user code is '1234'.
**Entering Programming Mode:**
* Enter the 6-digit programming code. Keypad beeps twice, green LED flashes.
**Programming Options (Accessed via Programming Code + Function Key):**
* **Change Door Open Time (Function Key 5, hold for 3 seconds):**
* Enter time in seconds (01-60). Default is 07 seconds.
* **Change Programming Code (Function Key 6, hold for 3 seconds):**
* Enter new 6-digit programming code, press bell.
* Re-enter new code to confirm, press bell.
* **Silent Operation (Function Key 3, hold for 3 seconds):**
* Press '6' to toggle silent mode (keypad will not beep when keys are pressed).
* **Exit Button Wires Configuration (Function Key 7, hold for 3 seconds):**
* Press '4' to set the button to toggle the lock (door opens until pressed again or toggle code entered).
* Default: Standard exit button (door opens for set door open time).
* **Lockout Function (Function Key 4, hold for 3 seconds):**
* Press '6' to activate lockout (20 incorrect key presses = 60-second lockout).
* **Multi-User Mode (Function Key 2, hold for 3 seconds):**
* Press '6' to enable multi-user mode. Allows adding/deleting individual user codes.
* Default: Single user mode.
* **Set a User Code (Function Key 8, hold for 3 seconds):**
* Enter new user code (4-8 digits), press bell.
* Enter new code again, press bell.
* Final key press defines action type:
* **4:** Normal code (releases lock for set door open time).
* **6:** Toggle code (holds lock open until entered a second time).
* **8:** Duress code (releases lock and energises bell terminal for remote alarm).
* **Data Reset (except Programming Code) (Function Key 9, hold for 3 seconds):**
* Re-enter programming code and hold '9' for a further 3 seconds.
**CARDLOCK/PROXIMITY with TOUCHLOCK Mode (Section 3):**
* If using a KP reader, it must first be initialised in TOUCHLOCK mode.
* **Operating Modes:**
* **Card plus PIN:** Individual user card requires a 4-digit PIN. (Enter 6-digit programming code, then '1', then '1').
* **Assigning PIN:** Present enrolment card, then individual user card. Enter chosen PIN, press bell. Confirm PIN, press bell.
* **Card plus Code:** Valid token PLUS valid user code. (Enter 6-digit programming code, then '1', then '2').
* **Card or Code:** Valid token OR valid user code. (Enter 6-digit programming code, then '1', then '3').
### Expander/Peripheral Devices with Specs
* **Proximity Reader – P75:** Compatible reader.
* **Paxton Exit Button – E50:** Compatible exit button.
* **Handsfree Interface:** Required for handsfree compatibility.
* **12V 1A PSU:** Power supply unit, often housed with the controller (e.g., Sales Code 242-166).
### Commissioning Steps
**Initialising a New System (CARDLOCK or PROXIMITY):**
1. Power up the control unit (it will beep 3 times/second, indicating it needs programming).
2. **Enrolling a Card Pack:**
* Present/swipe enrolment card.
* All tokens in the pack are now validated and can be issued to users.
3. **Adding an Additional Proximity Card Pack:**
* Present the enrolment card from the original card pack (amber LED flashes, green & red LEDs off).
* Present the enrolment card from the new card pack (reader beeps, all LEDs lit, indicating cards are valid).
* Repeat for each reader and additional card packs.
* *Note:* Any valid enrolment card from previous packs can add further packs. Incorrect enrolment card results in red LED and beep.
**Initialising a New System (TOUCHLOCK Keypad):**
1. Follow the steps under "Full Programming Menu Structure" -> "Initialising the Keypad".
**Factory Reset (Switch2 Control Unit):**
1. Turn off power and disconnect Green and Mauve keypad wires from Switch2 terminals.
2. Insert a wire link between the Green and Mauve terminals.
3. Reconnect power (unit will beep 4 times).
4. Disconnect power and remove the link wire, reconnect Green and Mauve wires.
5. Reconnect power (unit will beep 3 times/second). The unit is now ready to be enrolled.
**Factory Reset (TOUCHLOCK Keypad):**
1. Enter programming mode.
2. Hold down '9' for 3 seconds.
3. Re-enter the programming code and hold down '9' for a further 3 seconds. The keypad will be reset (except for the programming code).
* *Note:* If the master code is lost, the Switch2 must be reset to factory settings using the control unit factory reset procedure.
### Common Fault Diagnosis / Technical Help
* **Two Readers on the Same Controller:** Wire PROXIMITY or CARDLOCK readers in parallel, colour for colour.
* **Replacing a White Labelled Control Unit (pre-2004 design):** Old units had 5V DC output on the red voltage terminal. New yellow labelled units have 12V DC. For 5V readers/keypads, the jumper setting on the controller PCB must be changed. Touchlock membrane keypad is not compatible with the new control unit.
* **Initialising with 2 Keypads (K-Series):** Either keypad can initialise the controller. Wire all wires in parallel, colour for colour.
* **Initialising with 2 Keypads (Older Touchlock/SS):** Use the master keypad (yellow wire to yellow terminal). Slave keypad has yellow wire to mauve terminal.
* **Bell/Alarm Output:** A 12V DC alarm sounder (up to 1A) can be wired between 12V and Bell terminals. Load must be considered for power supply rating. If door contacts are fitted, the bell/alarm output activates when the door is forced. On a keypad system, the bell button normally activates this output, but not if a door forced alarm is active.
### Compliance Standards Met
* **EU Directives:**
* Directive 2014/53/EU (Full declaration of conformity at http://paxton.info/3910)
* The Low Voltage (LVD) Directive - 2006/108/EC
* The Electro-Magnetic Compatibility (EMC) Directive - 2004/108/EC
* The Restriction of Hazardous Substances (RoHS) Directive - 2011/65/EU
* **North America:**
* **FCC Compliance (Part 15):**
* Complies with Part 15 of the FCC Rules. Operation subject to: (1) device may not cause harmful interference, and (2) device must accept any interference received.
* Class B digital device. Tested to comply with limits for Class B digital device, providing reasonable protection against harmful interference in residential installation.
* If interference occurs, suggested measures: Reorient/relocate receiving antenna, increase separation between equipment and receiver, connect equipment to different circuit, consult dealer/technician.
* **Industry Canada Compliance:**
* Complies with Industry Canada licence-exempt RSS standard(s). Operation subject to: (1) device may not cause interference, and (2) device must accept any interference.
* **Wiring Methods:** Shall be in accordance with the National Electrical Code (ANSI/NFPA70), local codes, and authorities having jurisdiction.
* **CAN/ULC-S319 Installations:** Terminals, leads, and wiring methods must comply with CSA, C22.1, Canadian electrical code, Part 1, safety standards for electrical installations.
* *Note:* Use of any add-on, expansion, memory, or other module not manufactured or supplied by Paxton invalidates CAN/ULC-S319 certification.
### Other Technical Details
* **Installation Warnings:**
* Read instructions before installing and powering equipment. Keep instructions for future reference.
* Only qualified and trained personnel should install, connect, or test this equipment.
* No user-serviceable parts within the PSU unit.
* Intended for indoor use only in dry locations. Class A product (may cause radio interference in domestic environment).
* Installation must meet National Wiring Regulations and IEC60950-1 standards.
* **Disconnect Devices:** Readily accessible disconnect device (appropriately rated circuit breaker) to disconnect both poles with at least a 3.0 mm contact gap. Internal capacitors discharge within 60 seconds (normal conditions); suitable precautions needed for fault conditions.
* **Protection Device:** Fusing characteristics: T3.15AH250V.
* **Battery Safety Warning:** Risk of explosion if battery is replaced by an incorrect type. Dispose of used batteries according to instructions.
* **Product Suitability:** Not suitable for retail sale. All warranties are invalid if not installed by a competent person.
=== WEB RESEARCH: switch2 ===
## Paxton Net2 Switch2 Compact Access Control System - Full Technical Reference
### Manufacturer and Product Name
Paxton Net2 Switch2 Compact Access Control System
### Discipline
Access
### System Overview
* **System Type:** Standalone access control system.
* **Architecture:** Control unit is separate from the user interface (reader/keypad). The control unit is mounted on the 'safe' side of the door, with only the keypad or reader outside.
* **Reader Compatibility:** Can be used with any of the readers in the Paxton range (PROXIMITY, CARDLOCK, TOUCHLOCK).
* **Inputs:** Door contact, exit button.
* **Outputs:** Alarm sounder output, volt-free relay for lock control (fail closed and fail open locks).
* **Installation:** Extremely simple to install and configure. Each controller can be configured to use the same site code for user tokens.
* **Security:** Provides high security as the controller is installed on the secure side of the door. Door contact can monitor for forced doors, triggering an audible alarm.
* **Lock Output:** Changeover relay for simple connection of either fail-open or fail-closed electric locks.
* **Token Compatibility:** Cards for PROXIMITY and CARDLOCK Switch2 systems are identical to those used with equivalent compact systems, allowing for mixed installations (Switch2 for high security, Compact for low security).
* **Event Recording:** Ideal for sites where the recording of events is not required.
### Product Range and Model Numbers
* **Switch2 - Controller:** Sales Code: 405-321
* **Switch2 - Controller, 12V 1A PSU, with plastic housing:** Sales Code: 242-166
* **Compatible Readers:** PROXIMITY, CARDLOCK, TOUCHLOCK readers (e.g., Proximity reader – P75).
* **Compatible Peripherals:** Paxton exit button – E50.
### Complete Technical Specifications (TDS-1037)
**Electrical:**
* **Current Consumption:** 80mA
* **Operating Voltage:** 10V - 14V DC
* **Relay Switchable Voltage:** 24V DC
* **Relay Switchable Current:** 4A
* **Alarm Output Current:** 1A
* **Reader Ports per ACU:** 1
* **Readers/Keypads per ACU:** 2
* **Total ACU Reader Port Output Current:** 500mA (check current draw on individual readers)
**Environment:**
* **Operating Temperature:** -20°C to +55°C (-4°F to +131°F)
* **Moisture Resistance:** Low (if used externally, it must be protected in a weatherproof housing)
* **Vandal Resistance:** No
**Hardware:**
* **Maximum Total Users/Tokens:** 100 card packs (up to 5,000 tokens/users)
* **Door Open Time:** 1 sec - 60 secs (Default: 7 seconds)
* **PIN Length:** 4-8 digits
* **Number of Codes (TOUCHLOCK):** 50
* **Code Length (TOUCHLOCK):** 4-8 digits
* **Handsfree Compatible:** Yes (requires interface)
* **Silent Operation:** Yes
* **3rd Party Reader Support:** No
* **Data Retention during a total power loss:** >10 years
**Dimensions:**
* **Height:** 71 mm (2.8”)
* **Width:** 70 mm (2.8”)
* **Depth:** 23 mm (0.9”)
### Default Codes
* **TOUCHLOCK Keypad Default User Code:** 1234 (opens the door before programming code is fully entered).
* **Programming Code (TOUCHLOCK):** Chosen by installer during initialisation (cannot be 123456).
* **No specific default engineer, master, installer, or duress codes are provided as they are user-defined during programming or system initialisation.**
### Fault/Event/Alarm Code Tables
* **Door Forced Alarm:** Activated when door contacts are fitted and the door is forced open. The bell/alarm output is triggered.
* **20 Wrong Keystrokes Lockout (TOUCHLOCK):** Keypad locks out for 60 seconds after 20 incorrect key presses.
* **LED Indicators:**
* **Initialising (First Power Up):** Control unit beeps 3 times/second. Red LED steady, amber LED flashes slowly, green LED flashes quickly.
* **Access Denied:** Red LED lit, reader produces a beep.
* **Access Granted:** Green LED lit.
* **Adding Additional Proximity Card Pack:** Amber LED flashes with green & red LEDs off (during step 1), all LEDs lit (after step 2).
### Zone Types and Descriptions
* **Zoning (PROXIMITY/CARDLOCK):** Allows limiting access by token colour. Requires PROXIMITY or CARDLOCK function card pack.
* **Colour Groups:** Access privileges can be set based on token colour (e.g., green, amber, red tokens for different access levels).
* **Time Zones:** Can be used with a time clock to change the validity of colour groups at different times of the day. This is dependent on whether the exit wires are shorted together or not.
### Wiring Diagrams and Terminal Descriptions
**Switch2 Control Unit Terminals:**
* **12V:** 12V DC power input/output.
* **0V:** Ground/common for power and other connections.
* **Data:** Data connection for reader/keypad.
* **Clock:** Clock connection for reader/keypad.
* **N.C. (Normally Closed):** Lock relay contact.
* **N.O. (Normally Open):** Lock relay contact.
* **COM (Common):** Lock relay contact.
* **EXIT:** Input for exit button or time clock.
* **Contact:** Input for door contact.
* **Bell:** Output for alarm/bell sounder.
**General Wiring Arrangement:**
* **Power Connection:** 12V DC power supply connected to "12V" and "0V" terminals. A 12V power supply with battery backup is recommended. Supply must provide enough current for reader, alarm sounder, and lock.
* **Reader Connection:** Any Paxton reader/keypad can be connected. Readers are colour-coded to correspond to labelled inputs on the control unit (12V, 0V, Data, Clock, LED).
* *Caution:* For 12V d.c readers only. For old 5V readers, refer to specific instructions.
* **Lock Connection:** 12V DC power for the lock is taken from the Switch2 "12V" terminal. The lock is controlled by switching the 0V feed via the voltage-free relay contacts.
* **Fail-open lock:** 0V linked to 'N.C.' terminal.
* **Fail-closed lock:** 0V linked to 'N.O.' terminal.
* In both configurations, the 0V feed to the lock is supplied via the 'Com' terminal.
* **Exit Button / Time Zone Control:** A 'push to make' exit button connects between "Exit" terminal and "Black" terminal (0V). Alternatively, a time clock with a voltage-free changeover contact can hold a door unlocked during programmed times. For swipe card/proximity systems, a time clock can change validity of colour groups.
* **Door Contact:** Connected between "Contact" terminal and "Black" terminal (0V). Must be a closed contact when the door is shut. Used for 'Door forced' alarm and Auto-lock feature.
* **Alarm / Door Bell Sounder:** Connected to "Bell" and "12V" terminals. Max 1A at 12V DC. "Bell" terminal connects to 0V during an alarm. Can be used as a doorbell when door contacts are not connected (with Paxton keypad).
* **Multiple Readers:** Two PROXIMITY or CARDLOCK readers can be wired in parallel, colour for colour, to the same controller for read-in and read-out access control.
### Full Programming Menu Structure (TOUCHLOCK Keypad with Switch2)
**Initialising the Keypad (First Power Up):**
1. Keypad beeps 3 times/second. Red LED steady, amber LED flashes slowly, green LED flashes quickly.
2. Press the bell button (unit stops beeping, green LED flashes).
3. Enter chosen 6-digit programming code and press bell button (green LED flashes faster).
4. Confirm programming code (enter same 6-digit code) and press bell button (green LED goes out, unit beeps twice, all LEDs on).
* *Note:* Programming code should NOT contain '1234'. Default user code is '1234'.
**Entering Programming Mode:**
* Enter the 6-digit programming code. Keypad beeps twice, green LED flashes.
**Programming Options (Accessed via Programming Code + Function Key):**
* **Change Door Open Time (Function Key 5, hold for 3 seconds):**
* Enter time in seconds (01-60). Default is 07 seconds.
* **Change Programming Code (Function Key 6, hold for 3 seconds):**
* Enter new 6-digit programming code, press bell.
* Re-enter new code to confirm, press bell.
* **Silent Operation (Function Key 3, hold for 3 seconds):**
* Press '6' to toggle silent mode (keypad will not beep when keys are pressed).
* **Exit Button Wires Configuration (Function Key 7, hold for 3 seconds):**
* Press '4' to set the button to toggle the lock (door opens until pressed again or toggle code entered).
* Default: Standard exit button (door opens for set door open time).
* **Lockout Function (Function Key 4, hold for 3 seconds):**
* Press '6' to activate lockout (20 incorrect key presses = 60-second lockout).
* **Multi-User Mode (Function Key 2, hold for 3 seconds):**
* Press '6' to enable multi-user mode. Allows adding/deleting individual user codes.
* Default: Single user mode.
* **Set a User Code (Function Key 8, hold for 3 seconds):**
* Enter new user code (4-8 digits), press bell.
* Enter new code again, press bell.
* Final key press defines action type:
* **4:** Normal code (releases lock for set door open time).
* **6:** Toggle code (holds lock open until entered a second time).
* **8:** Duress code (releases lock and energises bell terminal for remote alarm).
* **Data Reset (except Programming Code) (Function Key 9, hold for 3 seconds):**
* Re-enter programming code and hold '9' for a further 3 seconds.
**CARDLOCK/PROXIMITY with TOUCHLOCK Mode (Section 3):**
* If using a KP reader, it must first be initialised in TOUCHLOCK mode.
* **Operating Modes:**
* **Card plus PIN:** Individual user card requires a 4-digit PIN. (Enter 6-digit programming code, then '1', then '1').
* **Assigning PIN:** Present enrolment card, then individual user card. Enter chosen PIN, press bell. Confirm PIN, press bell.
* **Card plus Code:** Valid token PLUS valid user code. (Enter 6-digit programming code, then '1', then '2').
* **Card or Code:** Valid token OR valid user code. (Enter 6-digit programming code, then '1', then '3').
### Expander/Peripheral Devices with Specs
* **Proximity Reader – P75:** Compatible reader.
* **Paxton Exit Button – E50:** Compatible exit button.
* **Handsfree Interface:** Required for handsfree compatibility.
* **12V 1A PSU:** Power supply unit, often housed with the controller (e.g., Sales Code 242-166).
### Commissioning Steps
**Initialising a New System (CARDLOCK or PROXIMITY):**
1. Power up the control unit (it will beep 3 times/second, indicating it needs programming).
2. **Enrolling a Card Pack:**
* Present/swipe enrolment card.
* All tokens in the pack are now validated and can be issued to users.
3. **Adding an Additional Proximity Card Pack:**
* Present the enrolment card from the original card pack (amber LED flashes, green & red LEDs off).
* Present the enrolment card from the new card pack (reader beeps, all LEDs lit, indicating cards are valid).
* Repeat for each reader and additional card packs.
* *Note:* Any valid enrolment card from previous packs can add further packs. Incorrect enrolment card results in red LED and beep.
**Initialising a New System (TOUCHLOCK Keypad):**
1. Follow the steps under "Full Programming Menu Structure" -> "Initialising the Keypad".
**Factory Reset (Switch2 Control Unit):**
1. Turn off power and disconnect Green and Mauve keypad wires from Switch2 terminals.
2. Insert a wire link between the Green and Mauve terminals.
3. Reconnect power (unit will beep 4 times).
4. Disconnect power and remove the link wire, reconnect Green and Mauve wires.
5. Reconnect power (unit will beep 3 times/second). The unit is now ready to be enrolled.
**Factory Reset (TOUCHLOCK Keypad):**
1. Enter programming mode.
2. Hold down '9' for 3 seconds.
3. Re-enter the programming code and hold down '9' for a further 3 seconds. The keypad will be reset (except for the programming code).
* *Note:* If the master code is lost, the Switch2 must be reset to factory settings using the control unit factory reset procedure.
### Common Fault Diagnosis / Technical Help
* **Two Readers on the Same Controller:** Wire PROXIMITY or CARDLOCK readers in parallel, colour for colour.
* **Replacing a White Labelled Control Unit (pre-2004 design):** Old units had 5V DC output on the red voltage terminal. New yellow labelled units have 12V DC. For 5V readers/keypads, the jumper setting on the controller PCB must be changed. Touchlock membrane keypad is not compatible with the new control unit.
* **Initialising with 2 Keypads (K-Series):** Either keypad can initialise the controller. Wire all wires in parallel, colour for colour.
* **Initialising with 2 Keypads (Older Touchlock/SS):** Use the master keypad (yellow wire to yellow terminal). Slave keypad has yellow wire to mauve terminal.
* **Bell/Alarm Output:** A 12V DC alarm sounder (up to 1A) can be wired between 12V and Bell terminals. Load must be considered for power supply rating. If door contacts are fitted, the bell/alarm output activates when the door is forced. On a keypad system, the bell button normally activates this output, but not if a door forced alarm is active.
### Compliance Standards Met
* **EU Directives:**
* Directive 2014/53/EU (Full declaration of conformity at http://paxton.info/3910)
* The Low Voltage (LVD) Directive - 2006/108/EC
* The Electro-Magnetic Compatibility (EMC) Directive - 2004/108/EC
* The Restriction of Hazardous Substances (RoHS) Directive - 2011/65/EU
* **North America:**
* **FCC Compliance (Part 15):**
* Complies with Part 15 of the FCC Rules. Operation subject to: (1) device may not cause harmful interference, and (2) device must accept any interference received.
* Class B digital device. Tested to comply with limits for Class B digital device, providing reasonable protection against harmful interference in residential installation.
* If interference occurs, suggested measures: Reorient/relocate receiving antenna, increase separation between equipment and receiver, connect equipment to different circuit, consult dealer/technician.
* **Industry Canada Compliance:**
* Complies with Industry Canada licence-exempt RSS standard(s). Operation subject to: (1) device may not cause interference, and (2) device must accept any interference.
* **Wiring Methods:** Shall be in accordance with the National Electrical Code (ANSI/NFPA70), local codes, and authorities having jurisdiction.
* **CAN/ULC-S319 Installations:** Terminals, leads, and wiring methods must comply with CSA, C22.1, Canadian electrical code, Part 1, safety standards for electrical installations.
* *Note:* Use of any add-on, expansion, memory, or other module not manufactured or supplied by Paxton invalidates CAN/ULC-S319 certification.
### Other Technical Details
* **Installation Warnings:**
* Read instructions before installing and powering equipment. Keep instructions for future reference.
* Only qualified and trained personnel should install, connect, or test this equipment.
* No user-serviceable parts within the PSU unit.
* Intended for indoor use only in dry locations. Class A product (may cause radio interference in domestic environment).
* Installation must meet National Wiring Regulations and IEC60950-1 standards.
* **Disconnect Devices:** Readily accessible disconnect device (appropriately rated circuit breaker) to disconnect both poles with at least a 3.0 mm contact gap. Internal capacitors discharge within 60 seconds (normal conditions); suitable precautions needed for fault conditions.
* **Protection Device:** Fusing characteristics: T3.15AH250V.
* **Battery Safety Warning:** Risk of explosion if battery is replaced by an incorrect type. Dispose of used batteries according to instructions.
* **Product Suitability:** Not suitable for retail sale. All warranties are invalid if not installed by a competent person.
Net2 Installation
Manual
Version 3
ins-190
Date code: 281002
--- PAGE BREAK ---
--- PAGE BREAK ---
Contents
Chapter 1 Introduction .....................................................5
This manual ................................................................................................ 5
Overview – System .................................................................................... 6
Overview – Net2 hardware....................................................................... 6
Overview – Net2 software ........................................................................ 7
Chapter 2 What is required? ............................................9
What is required? ....................................................................................... 9
Essential............................................................................................................................ 9
Optional............................................................................................................................ 9
Chapter 3 About… ..........................................................11
Net2 access control unit – hardware features ....................................... 11
Net2 access control unit – diagnostic LEDs........................................... 12
Net2 access control unit – enclosure options ........................................ 12
Readers and keypads – compatibility .................................................... 13
Readers and keypads – cable details...................................................... 14
Power supplies – Paxton supplied ......................................................... 15
12Vdc boxed backup power supply 1A .................................................................... 15
2A 12V d.c. boxed power supply with mains monitoring ..................................... 15
Power supplies – choosing guide ........................................................... 15
Current rating................................................................................................................ 15
Battery backup............................................................................................................... 16
PSU ripple ...................................................................................................................... 16
Size of enclosure............................................................................................................ 17
Alarms ............................................................................................................................ 17
Inputs ........................................................................................................ 17
Exit button...................................................................................................................... 17
Door contact................................................................................................................... 17
Power supply tamper................................................................................................... 17
PSU .................................................................................................................................. 17
Outputs ..................................................................................................... 18
Relay 1 - lock.................................................................................................................. 18
Relay 2 – toggle/doorbell ............................................................................................ 18
General purpose output - alarm ................................................................................. 18
User tokens – choice................................................................................. 18
Magstripe card............................................................................................................... 18
Proximity token............................................................................................................. 18
Proximity keyfob........................................................................................................... 18
Proximity ISO card ....................................................................................................... 19
User tokens – photo ID ............................................................................ 19
Magstripe ....................................................................................................................... 19
Proximity........................................................................................................................ 19
User tokens – encoding ........................................................................... 19
1
--- PAGE BREAK ---
Paxton Net2 tokens....................................................................................................... 19
CARDLOCK and PROXIMITY tokens ...................................................................... 20
Third party user tokens................................................................................................ 20
User tokens – part numbers .................................................................... 20
Desktop reader ......................................................................................... 21
Network – architecture............................................................................ 21
Daisy chain..................................................................................................................... 21
Termination resistors.................................................................................................... 22
Network – data line cable........................................................................ 22
Network – RS485/232 interface.............................................................. 23
Network – RS485 repeater....................................................................... 23
PC............................................................................................................... 23
Requirements................................................................................................................. 23
System backup............................................................................................................... 23
Event backup ................................................................................................................. 24
Chapter 4 Prepare yourself ...........................................25
ACU schedule........................................................................................... 25
Cable schedule.......................................................................................... 28
Chapter 5 Fitting..............................................................31
CARDLOCK and PROXIMITY readers ................................................. 31
TOUCHLOCK keypads........................................................................... 34
Plastic ACU enclosure ............................................................................. 34
Chapter 6 Wiring .............................................................35
CARDLOCK readers................................................................................ 35
PROXIMITY readers ................................................................................ 36
PROXIMITY slimline readers ................................................................. 36
Vandal proof readers ............................................................................... 37
TOUCHLOCK keypads........................................................................... 37
Power supply............................................................................................ 38
Inputs and outputs - inputs .................................................................... 38
Exit button...................................................................................................................... 38
Door contact................................................................................................................... 38
Power supply tamper................................................................................................... 39
PSU – mains monitoring.............................................................................................. 39
Inputs and outputs - outputs .................................................................. 39
Relay 1 - lock.................................................................................................................. 39
Relay 2 – sounder.......................................................................................................... 40
General purpose output – alarm sounder................................................................. 40
Wiring into a fire alarm................................................................................................ 41
Software controlled fire doors .................................................................................... 42
Network .................................................................................................... 43
Data line cable ............................................................................................................... 43
RS485/232 communications converter...................................................................... 44
RS485 repeater ............................................................................................................... 44
Summary................................................................................................... 45
Chapter 7 Commissioning .............................................46
Hardware – network................................................................................ 46
Data cable ....................................................................................................................... 46
Screen shorts .................................................................................................................. 46
2
--- PAGE BREAK ---
Screen continuity........................................................................................................... 47
Hardware – the Access Control Unit (ACU) ......................................... 47
Turning on the power .................................................................................................. 47
ACU test ......................................................................................................................... 47
Software – installing the program .......................................................... 48
Software – installing the database.......................................................... 52
Software – configuring the doors ........................................................... 53
Door name...................................................................................................................... 53
Door open time.............................................................................................................. 53
Unlock the door during ............................................................................................... 53
Apply .............................................................................................................................. 53
Open door ...................................................................................................................... 54
Doors\[Door name]\Reader 1................................................................ 54
Name............................................................................................................................... 54
Reader type .................................................................................................................... 54
Keypad............................................................................................................................ 54
Card data format........................................................................................................... 54
Reader operating mode................................................................................................ 55
Timed operating modes............................................................................................... 55
Reader action ................................................................................................................. 55
Doors\[Door name]\Reader 2................................................................ 56
Doors\[Door name]\Alarm.................................................................... 56
Local alarm..................................................................................................................... 57
Testing the local alarm ................................................................................................. 57
Alarm reporting at the PC ........................................................................................... 57
Doors\[Door name]\Codes.................................................................... 57
Commissioning checks ............................................................................ 58
Chapter 8 Fault-finding ..................................................60
Fault diagnosis ......................................................................................... 60
Communications test.................................................................................................... 60
ACU test ......................................................................................................................... 61
OK LED Status.......................................................................................... 61
System problems – power supply .......................................................... 62
System problems – processor.................................................................. 62
System problems – inputs ....................................................................... 62
System problems – reader/keypad........................................................ 62
System problems – outputs..................................................................... 63
System problems – communications...................................................... 63
If some ACUs are communicating but not all.......................................................... 63
If all ACUs are not communicating ........................................................................... 63
If there are inconsistencies between the database and control unit information64
System problems – PC ............................................................................. 64
If the system is not communicating ........................................................................... 64
If the Net2 program will not install ........................................................................... 65
Paxton Access technical help .................................................................. 66
Chapter 9 Appendix........................................................68
Appendix (i) Operation of a relay explained ...................................... 68
Appendix (ii) Fail open and fail closed locks explained .................... 69
Appendix (iii) Difference between code and PIN explained............. 69
Appendix (iv) Glossary ......................................................................... 70
3
--- PAGE BREAK ---
Appendix (v) ISO card unprintable area ............................................. 71
Appendix (vi) Net2 part numbers and product descriptions............ 72
Appendix (vii) Extending a Net2 system............................................. 73
Appendix (viii) Replacing a control unit ............................................. 74
Appendix (ix) Site registration form .................................................... 75
Registering couldn’t be simpler. Simply complete this form and fax it
to us. .......................................................................................................... 75
Chapter 10 Specifications ...............................................76
4
--- PAGE BREAK ---
Chapter 1 Introduction
This manual
Overview
This manual
This manual is designed for anybody installing and/or commissioning a
Net2 access control system. The manual should be read in full before
installation is attempted. As with any system of this nature, if the correct
procedures are not followed, problems can occur requiring time consuming
fault finding and diagnosis. This manual is designed to guide you through
the installation of the Net2 system without problems.
Figure 1.1
Table showing the layout
of this manual
Section
Function
Overview
An introduction to the system
What is required
A complete list of the parts required for an access
control system
About…
In depth information about the system components
to help specify the system and buy the correct
components
Prepare yourself
ACU and cable schedules
Wiring
Wiring schematics
Commissioning
Guide to commissioning the system hardware and
software
Fault-finding
Guide to fault-finding the system
Appendix
Useful information that is referred to throughout
the document
Specifications
Full system specification
It is recommended that you study the Contents and understand the
structure of this manual before reading.
Chapter 1 Introduction
5
--- PAGE BREAK ---
Overview – System
The Net2 system is a revolutionary system with hardware and software
developed simultaneously to meet the requirements of a modern day access
control system. The hardware uses the latest in microchip technology
allowing unprecedented levels of speed, resilience and value. The software
is based on the latest Windows interfaces and is developed to enable
powerful functionality whilst maintaining ease of use.
An access control system is an investment. The Net2 system ensures the
future proofing of that investment in several ways:
• Latest micro-controller technology offering solid, capable hardware
platform
• Hardware and software fully year 2000 compliant
• Use of FLASH memory allowing easy upgrades
• Software can be extended in functionality with ‘Modules’
• System can be extended with no redundancy of equipment
The system is capable of controlling up to 200 doors and 10,000 users with
the standard plus software. For systems larger than this please contact
Paxton Access Ltd.
RS485/232
converter
Up to 200 ACU's
RS 485
Net2 ACU
Optional desktop
reader.
Net2 ACU
Door contact
Net2 ACU
Maglock
Reader
and
keypad
Exit
button
Electric
release
Door 1
Figure 1.2
Net2 system schematic
Net2 ACU
2 readers for
read in and
read out
Door 2
Door 3
Barrier
Net2 V3 supports the use of multiple comports, allowing for star
configuration networks from the PC. Control units are automatically
detected.
Overview – Net2 hardware
Ease of wiring
Clearly labelled terminals on every access control unit remove the need for
continual referencing to wiring diagrams. Clear colour coding of reader
cables leads to fewer mistakes.
Diagnostic LEDs
An array of LEDs on the control unit indicate the status of key system
features. This will aid commissioning and quick diagnosis of any problems
should they occur.
Chapter 1 Introduction
6
--- PAGE BREAK ---
FLASH Memory
FLASH memory in the access control units allows the downloading of new
firmware to the control units from the PC over the network. This means that
as new features are added to Net2, systems in the field can be upgraded to
allow the use of the latest software features without any changes to the
hardware.
Open architecture
Relay outputs and digital and analogue inputs allow integration with the
hardware of other systems.
Latest technology
State of the art electronic components create a solid hardware platform,
which is both high performance and compact.
Scaleable architecture
The system will be scaleable. The smallest system will be expandable to the
largest system using the same hardware building blocks with no
redundancy of hardware as the system expands.
Communications
Very high speed and resilient communications offer real time alarm
reporting and the capability for very large systems.
Distributed intelligence
The Net2 single door control units provide fully distributed intelligence
down to individual doors. This gives greater system resilience and makes
support and problem diagnosis easier. Also, event information can be
retained when the system is running off-line (2,300 events per control
unit/door).
Multi-technology
The same control unit will support magstripe, keypads and proximity,
mixed on a single site if required.
Overview – Net2 software
Open architecture
Microsoft Access database allows easy linking of data to other software
systems.
Ease of use
Easy to learn user interface working in Microsoft Windows 98/2000/NT/XP
environments. The user interface looks and feels like the latest Microsoft
Windows explorer and Outlook programs so office PC users will be able to
navigate the system intuitively.
Ease of commissioning
Auto detection and numbering of access control units. No DIP switches to
set or binary numbering to worry about - switch on the software and go!
Modular
The software has the capacity for features to be added as and when they are
required. The modular structure enables the user interface to be as powerful
as required whilst remaining simple.
Chapter 1 Introduction
7
--- PAGE BREAK ---
8
--- PAGE BREAK ---
Chapter 2 What is required?
Essential
Optional
What is required?
Essential
Description
PC
Net2 software
Net2 access control units (ACUs)
Enclosures for ACUs
(If not fitted inside PSUs)
Readers/keypads
Reader and network cable
Cable for lock supply and inputs
Power supplies
User cards/tokens
Electric release/lock
RS485/232 communications
interface
Optional
Description
RS485 repeater
Door contacts
Desktop reader
Door loops
Break glass
Exit buttons
Batteries for power supplies
For a full list of system components supplied by Paxton Access Ltd, refer to
Appendix (vi).
Chapter 2 What is required?
9
--- PAGE BREAK ---
Chapter 2 What is required?
10
--- PAGE BREAK ---
Chapter 3 About…
Net2 access control unit
Readers/keypads
Power supplies
Inputs and outputs
User tokens
Desktop reader
Network
PC
Net2 access control unit – hardware features
•
•
•
•
•
•
•
•
•
16Bit Micro-controller running at 14.7MHz
128K FLASH Memory with over 100 years data retention
1 x 128K static RAM chips
On board rechargeable 3.6V battery – approximately 1 weeks data
retention
On board real time clock with year 2000 compliant software
Quiescent current of ACU at 12Vdc is between 50 and 350mA depending
on what is functioning on the board
RS485 Coms chip with full duplex communication at 115K BAUD
Terminal blocks rated at >100 uses with rising clamp connectors
On-board static protection:
Coms chip
Mosorb protected – clamped to 15V above ground
(Will dissipate 1500W)
Inputs
Diode protected
12V dc input Mosorb protected – clamped to 27V above ground
Figure 3.1
Table showing board
protection
Capacitor smoothed – capacitor can supply board for
0.25 seconds
• Outputs:
Figure 3.2
Table showing outputs
Chapter 3 About
2 x clean contact relays
24V, 5Amps
1 x FET output
Variable voltage, 1Amp
11
--- PAGE BREAK ---
Net2 access control unit – diagnostic LEDs
The diagnostic LEDs are designed to make fault-finding and commissioning
easier.
Note:
All of the inputs work on
the same logic. If the
circuit is closed, the LED is
on.
Figure 3.3
Table showing functions of
diagnostic LEDs
Label
On means…
Off means…
12V
12V okay
12V not okay
5V
5V okay
5V not okay
OK
This is the heartbeat of the system and should pulse regularly.
This shows that the processor is functioning.
PSU
Mains present
Mains not present OR mains
monitoring not connected
Tamper
No tamper
Tamper OR tamper switch not
connected
Contact
Door is closed
Door is open OR door contact
not connected
Exit
Button pressed
Button not pressed OR exit
button not connected
Relay 2
Coil energised. Com and N.O. Coil not energised. Com and
terminals are connected.
N.C. terminals are connected.
Door relay 1
Coil energised. A fail closed Coil not energised. A fail
lock will be open. A fail open closed lock will be locked. A
release will be locked.
fail open release will be open.
Tx
The ACU is transmitting a
network message
The ACU is not transmitting a
network message
Rx
The ACU is receiving a
network message
The ACU is not receiving a
network message
Net2 access control unit – enclosure options
The Net2 ACU is available in the following formats:
• No enclosure – The control unit PCB is provided with plastic
adhesive posts for mounting into an enclosure.
• Mounted in Net2 plastic housing – a smart enclosure for the ACU
• Mounted in Net2 2A PSU in steel cabinet – a good quality power
supply and enclosure.
Figure 3.4
Table showing enclosure
options
Chapter 3 About
Part number
Description
489-334
Net2 1 door access control unit
385-527
Net2 1 door ACU in plastic housing
571-692
Net2 housing for ACU black plastic
411-381
Net2 1 door ACU with 2A PSU in steel cabinet
857-693
Net2 2A PSU in steel cabinet
12
--- PAGE BREAK ---
Readers and keypads – compatibility
Figure 3.5 shows the products manufactured by Paxton Access Ltd that are
suitable for use with the Net2 ACU. Two readers AND two keypads can be
wired to the same control unit to give card plus PIN or card plus code access
control on both sides of an access point.
Figure 3.5
Table showing compatible
readers/keypads
Part number
Description
600-628BL
TOUCHLOCK keypad black
600-628BR
TOUCHLOCK keypad brass
600-628SC
TOUCHLOCK keypad satin chrome
584-374
TOUCHLOCK keypad stainless steel
409-711BL
CARDLOCK reader black
409-711BR
CARDLOCK reader brass
409-711SC
CARDLOCK reader satin chrome
266-898
CARDLOCK reader black plastic external
355-098
PROXIMITY reader
OEM readers and keypads
Currently no other keypads are supported by the Net2 ACU. Magstripe
and proximity readers with clock and data or 26-bit Wiegand outputs are
compatible. Figure 3.6 shows the connection details to the control unit. If in
doubt, consult the Paxton Access technical helpline.
Yellow
Orange
Keypad 2
Brown
Orange
Green
Yellow
Blue
Mauve
Blk/Wht
Brown
Yellow
Orange
Keypad 1
Chapter 3 About
Red
Reader 1
Figure 3.6
Diagram showing reader
inputs
5V
Red LED
Amber LED
Green LED
!Data
Clock
!Media detect
0V
13
--- PAGE BREAK ---
Readers and keypads – cable details
Paxton readers/keypads require Common Reference CR9540 cable. Figure
3.7 shows the reader cable supplied by Paxton Access Ltd.
Figure 3.7
Table showing reader
cables
Part number
Description
166-010
Reader cable 10 core CR9540 10m roll
166-025
Reader cable 10 core CR9540 25m roll
166-100
Reader cable 10 core CR9540 100m roll
166-500
Reader cable 10 core CR9540 500m roll
The specifications of CR9540 are shown in figure 3.8.
CR9540
Figure 3.8
Table showing reader
cable specification
Cores
10
Screened
Overall screened
AWG
24
Outside diameter
6.197mm
Capacitance between conductors
98.4 pF/m
Construction
7x32
The type of reader/keypad will effect the maximum distance to the Net2
ACU. Figure 3.9 shows this relationship. All distances are assuming that
CR9540 cable is used AND that the readers/keypads are wired as shown in
this document. Using CR9540 ensures that the cable extensions match the
reader tail.
Figure 3.9
Table showing maximum
cable extensions for
readers/keypads
Reader/keypad
Maximum distance from ACU
TOUCHLOCK keypad
30 metres
TOUCHLOCK keypad stainless steel
30 metres
CARDLOCK reader
100 metres
PROXIMITY reader
50 metres
The cable screen must be connected to the 0V (Blk/Wht) terminal at each
ACU.
The minimum voltages that readers/keypads will operate with are shown in
the table.
Figure 3.10
Table showing minimum
voltages for
readers/keypads
Chapter 3 About
Reader type
Minimum voltage
PROXIMITY reader
PROXIMITY reader (new style)
CARDLOCK reader
TOUCHLOCK keypad
4.5V
12V
4.5V
4.5V
TOUCHLOCK keypad stainless steel
OEM reader
4.5V
Consult manufacturer’s
literature
14
--- PAGE BREAK ---
Power supplies – Paxton supplied
Paxton Access Ltd offer two power supply solutions.
Figure 3.11
Table showing power
supplies available from
Paxton Access Ltd
Part number
Description
339-424
12Vdc boxed backup power supply 1A
857-693
Net2 2A PSU in white steel cabinet
339-425
12V 1.2AH battery for 1A boxed PSU
862-719
12V 7AH battery for 2A boxed PSU
12Vdc boxed backup power supply 1A
Standard 1 Amp 12V dc power supply unit with a 205mm X 230mm X 80mm
enclosure (not enough room for the Net2 ACU). Hinge lid with a tamper
switch. Takes 2 X 1.2AH batteries.
2A 12V d.c. boxed power supply with mains monitoring
This unit is now available, part number 857-693. It includes many features
including mounting posts for the Net2 ACU and mains monitoring.
Power supplies – choosing guide
When choosing a power supply for the Net2 system there are several
considerations.
Current rating
The rating of the power supply must be suited to the load. The quiescent
current of the various system components is shown in Figure 3.12.
Figure 3.12
Table showing loads
Description
Load
Net2 ACU (not including readers etc.)
<350mA
PROXIMITY reader
60mA approx.
CARDLOCK reader
55mA approx.
TOUCHLOCK keypad stainless steel
35mA approx.
TOUCHLOCK keypad membrane
35mA approx.
Electric release/other
Consult
manufacturer’s
literature
Battery charge
Consult
manufacturer’s
literature
The minimum power supply rating is equal to the sum of all loads plus 10%
(safety factor).
Chapter 3 About
15
--- PAGE BREAK ---
Battery backup
The time that the Net2 system will continue to operate when the mains
supply fails is dependent on the current consumption of the system and the
battery backup in the power supplies. The relationship is shown in figure
3.13.
Figure 3.13
Relationship between
current consumption and
battery backup time
Backup time (hours) =
Amp hour of backup batteries (Amp hours)
Current consumption of system (Amps)
Power supplies vary in the features they offer relating to battery backup. A
few considerations are:
• Deep discharge – When a backup battery is drained too much it can
reach a state whereby it cannot be recharged. This is deep
discharge. Some power supplies have the ability to prevent this
happening.
• Recharge limit – Some power supplies limit the current
consumption of a battery whilst it is recharging. If a power supply
does not do this then the system may not be immediately
operational when mains power is resumed, i.e. the power will be
consumed by the battery recharge.
• Battery capacity – the size of the enclosure will limit the
amount/size of the backup batteries.
PSU ripple
Not all dc power supplies are smooth. The ripple is the amount that the
voltage fluctuates. The ripple of a supply can be measured by setting a
multimeter to measure ac voltage. If the ac voltage across the power
terminals is greater than 2V, then it is not suitable for use with Net2.
PSU ripple should be measured under full load conditions.
Voltage
Voltage
Ripple
12Vdc
12Vdc
Time
Time
Perfectly smooth supply
Actual supply
Figure 3.14
PSU ripple
Chapter 3 About
16
--- PAGE BREAK ---
Size of enclosure
If the ACU is to be mounted in the power supply enclosure then there must
be sufficient space. An enclosure of 350x350mm or larger is recommended.
350mm
Power supply
350mm
Figure 3.15
Recommended size of PSU
enclosure
Alarms
The Net2 system has the capacity to report PSU tampering and mains
failure. If the monitoring of these features is required then the chosen power
supply must have tamper and mains fail clean contact outputs.
Inputs
Exit button
Any push to make button can be used. The button should be physically
robust to suit the volume of traffic through the access point and the
environmental conditions. An exit button is not required if exit is by using a
handle or an out reader.
Door contact
To enable door monitoring, door contacts must be used. The door contact
circuit must be closed when the door is shut. Two states of alarm can be
generated with door monitoring, door forced open and door left open.
Autolock means that when a door closes, the locking mechanism
automatically locks even if the door open time has not expired. This feature
can help to reduce tailgating. If autolocking is required then a door contact
must be fitted.
Power supply tamper
This input is for a power supply tamper switch. This will allow tampering
to appear as an alarm event at the PC. The Net2 plastic enclosure also has a
tamper switch fitted. Where there is a separate PSU and enclosure, the
tamper switches can be wired in series.
PSU
This input is for mains monitoring. This requires the power supply to have
a mains fail relay output. The ACU will report a mains fail alarm if this
input changes state.
Chapter 3 About
17
--- PAGE BREAK ---
Outputs
Relay 1 - lock
The lock is controlled by door relay 1. Relay operation is described in
Appendix (i). The relay contacts are voltage free and are rated 5Amps at
12V ac or dc. Having relay contacts means that this output is very versatile
and can operate virtually any electrical equipment including fail open and
fail closed locks, electric gates, electric barriers, lifts…
There are two main types of locking devices - fail open and fail closed. Refer
to Appendix (iii) for more information.
When using the same power supply for the ACU and electric release, diode
suppression must be fitted. A standard 1N4001 diode is fitted as shown in
Wiring – inputs and outputs.
Relay 2 – toggle/doorbell
Relay 2 can be configured to toggle in the software (See ins-113). It can be
toggled by either reader 1 or by reader 2. If the relay has NOT been set to
toggle then the doorbell of a TOUCHLOCK keypad fitted to the system will
operate it. The output is rated 5Amps at 12V ac or dc. Relay contacts can
operate virtually any electrical equipment including buzzers, lights etc…
General purpose output - alarm
This is the alarm output and is a FET, open drain that is capable of
supplying 1Amp at 12-24Vdc. The FET acts as a switch to 0V.
12V
0V
FET
Figure 3.16
General purpose FET
output
0V
User tokens – choice
Users of the Net2 access control system will be required to carry a user
token. Paxton manufacture a number of token formats.
Magstripe card
Credit card sized plastic card with a standard high coercivity (hi-co)
magnetic stripe for use with magstripe card readers.
Proximity token
Tokens are about credit card size but are thicker. They can be used from
inside wallets or handbags. Adhesive plastic stickers can be applied for
photo ID and the slot in the tokens makes them ideal for use with low cost
badge clips.
Proximity keyfob
Keyfobs are for applications where convenience is important. They are
made of hard plastic and will fit onto a keyring. They can be attached to
car/house keys for reduced losses, hence reducing the cost of replacing fobs.
Chapter 3 About
18
--- PAGE BREAK ---
Proximity ISO card
ISO cards are the same size as standard bank or credit cards. They can be
used with standard card printers for photo ID. They also have a magnetic
stripe that can be encoded for use with other systems such as vending.
User tokens – photo ID
There are several photo ID options with varying degrees of cost for both
magstripe and proximity.
Magstripe
Magstripe ID cards can be produced in one of three ways.
1.
The photo ID card is supplied encoded and has insets for a passport
photo and some text. This is laminated with a standard office laminator.
2.
A specialist bureau produce photo ID cards with corporate artwork.
Paxton Access Ltd can encode these cards if required.
3.
For large sites, an on-site photo imaging and card printing system can be
purchased. Paxton Access Ltd can supply encoded blank magstripe
cards if required.
Proximity
Proximity ID devices can be produced in any of the following ways.
1.
The PROXIMITY token photo ID pouch overlay has inserts for a
passport photo and some text. This is laminated in a standard office
laminator and applied onto the face of the token with the adhesive
backing.
2.
The PROXIMITY token plain overlay can be printed with graphics using
the desktop card printers used with on site photo imaging systems.
They are applied to the token using the adhesive backing.
3.
PROXIMITY ISO cards have the same dimensions as standard magstripe
cards. This allows them to be printed using either a specialist bureau
service or on site photo imaging systems. ISO cards are always supplied
with a blank white face for printing.
There is a small area on the bottom right hand of ISO cards which may
cause printing irregularities and should be avoided when designing
card artwork. Refer to Appendix (vi) for details.
User tokens – encoding
The Net2 system accepts many different encoding formats.
Paxton Net2 tokens
Magstripe and proximity tokens can be supplied encoded with an 8 digit
number. This number will be unique to that particular token and the tokens
will be labelled with the same number. To enrol a token the Net2 system
will require this printed number to be entered either by typing it in or using
a desktop reader.
Chapter 3 About
19
--- PAGE BREAK ---
CARDLOCK and PROXIMITY tokens
Magstripe and proximity tokens can also be supplied with an encoded
number containing a site code and user code. These are the same tokens that
are used with the CARDLOCK, PROXIMITY and NETWORK systems. The
Net2 system can utilise the same user tokens as an existing Paxton system if
required. Alternatively, the Net2 system can be used in conjunction with
Paxton stand alone systems. These tokens do not have their number printed
on them and so enrolling requires a desktop reader.
Third party user tokens
At present only proximity tokens manufactured by Paxton Access are
compatible with the Net2 system. Third party magstripe cards can be used
however. This is useful if the Net2 system is to be installed on a site where a
magstripe card system (time and attendance, cashless vending, member’s
card…) is already in use. Figure 3.17 shows how Net2 interprets various
formats of encoded numbers. If the number on the magstripe card is not
known then a desktop reader will be required for entering the token
number.
Figure 3.17
Table showing
interpretation of various
encoding formats
Encoded number
Net2 reads as…
Comments
1234
00001234
Where there are less than 4 digits
encoded on a card, zeros are added
to make up an 8 digit number.
123456789
12345678
Where more than 8 digits are
encoded on a card, the first 8 are
read.
123=456=789
12345678
Where digits are interrupted by
field separators, the field
separators are ignored and the first
8 digits are read.
123456789=6543
23456789
Where 8 or more digits precede a
field separator, the 8 digits before
the field separator are read. (This
is how ABA and bank cards would
be read)
Note: = denotes
field separator
Access control magstripe cards have a high coercivity (hi-co) magnetic strip.
Some magstripe cards are low coercivity (lo-co). Bankers cards for example
are lo-co. These cards are not recommended for access control. They are not
as resilient to corruption as hi-co cards and wear at a much quicker rate
giving a much shorter card life. Lo-co cards can be recognised by their
brown magnetic strip; hi-co cards have a black magnetic strip.
User tokens – part numbers
Figure 3.18
Table showing user token
part numbers
Chapter 3 About
Part number
Description
695-573
Net2 magstripe cards box of 10
693-112
Net2 proximity tokens box of 10
695-644
Net2 proximity keyfobs box of 10
692-448
Net2 proximity ISO cards box of 10
20
--- PAGE BREAK ---
Where the tokens are for use in conjunction with CARDLOCK or
PROXIMITY stand alone systems, see the Paxton Access trade brochure for
token part numbers.
Desktop reader
When a card is presented to the desktop reader, if it is known to the system
the user record will be displayed, if it has not been previously entered on the
system a blank record is displayed with the new card number displayed in
the card number field.
A desktop reader is designed to be at the PC and used to administer the
Net2 system. Alternatively, standard magstripe or proximity readers can be
used but will have to be mounted appropriately. The desktop reader can
read all Paxton magstripe and proximity tokens and is mounted on a metal
plate designed to sit next to the PC.
Figure 3.19
Table showing desktop
reader options
Part number
Description
409-711BL
CARDLOCK reader black
409-711BR
CARDLOCK reader brass
409-711SC
CARDLOCK reader satin chrome
355-098
PROXIMITY reader
376-001
Desktop reader prox and magstripe
The desktop reader can be wired to a spare reader terminal of any control
unit on the system. BEWARE – the maximum cable distance from reader to
control unit is as shown in figure 3.9. If there is not an ACU with a spare
reader terminal within the required range of the PC, a dedicated ACU will
be required.
Where Net2 tokens are being used the encoded number is supplied with
the device, allowing the token number to be typed in manually or by
swiping through the desktop reader.
Network – architecture
Daisy chain
The Net2 system communicates using an RS485 data line. Communication
is full duplex at 115K BAUD giving up to 1,000 messages per second.
Because communication is duplex, all four cores of the network cable are
used. The cable consists of two individually screened twisted pairs – white
& green and red & black. One pair is used for transmitting, the other
receiving.
Maximum of 1000m
RS485
repeater
Figure 3.20
Daisy chain network with
RS485 repeaters
PC
The data line must be wired in ‘daisy chain’ formation with one control unit
after the other. If the data line is over 1,000m a RS485 repeater (part number
477-836) should be used.
Chapter 3 About
21
--- PAGE BREAK ---
The PC can be located at the most convenient point along the network. This
may be at the end of the network OR in between control units.
Termination resistors
At each end of the data line a termination resistor is required for each of the
twisted pairs.
* Resistors
Figure 3.21
Termination resistors
* Resistors
*
120 Ohm resistors - supplied in the fitting kit
IMPORTANT NOTE:
The latest R485/232 converters do not contain termination resistors. If the
converter is wired at the end of the network two 120 Ohm resistors must
be wired between terminals 1 and 2, and 3 and 4.
Older RS485/232 converters may contain termination resistors. This type
can be identified by two internal jumpers. If this type of converter is
wired at the end of the network then these are left in place. Otherwise
these jumpers have to be removed (JP1 and JP2 from converter PCB).
Network – data line cable
If unscreened cable is used, the unused cores should be connected into the
screen terminal connection.
The recommended network cable is either CAT5 (Screened or unscreened)
or CR8723.
Part number
Description
120-305
CAT5 data cable 305m boxed reel
CR8723
Figure 3.22
Table showing network
cable specification
Chapter 3 About
Cores
4
Screened
Individually screened pairs
AWG
22
Outside diameter
4.267mm
Capacitance between
conductors
114.8 pF/m
Construction
7x32
22
--- PAGE BREAK ---
Network – RS485/232 interface
As the network protocol is standard RS485, a standard RS485/232
communications converter can be used. The converter will have to be
capable of 115,200 BAUD and full duplex. Paxton Access Ltd manufacture a
suitable interface.
Figure 3.23
Table showing RS485/232
interface
Part number
Description
289-641
Net2 RS485/232 kit incl converter
with PSU and PC lead
IMPORTANT NOTE:
The latest R485/232 converters do not contain termination resistors. If the
converter is wired at the end of the network two 120 Ohm resistors must
be wired between terminals 1 and 2, and 3 and 4.
Older RS485/232 converters may contain termination resistors. This type
can be identified by two internal jumpers. If this type of converter is
wired at the end of the network then these are left in place. Otherwise
these jumpers have to be removed (JP1 and JP2 from converter PCB).
Network – RS485 repeater
The RS485 network can span 1,000m (1km) from one end to the other. If the
network is to exceed this length, repeaters will be required every additional
1,000m, see figure 3.20.
Figure 3.24
Table showing RS485
repeater
Part number
Description
477-836
Net2 RS485 high speed repeater
PC
Requirements
The Net2 system does not require a dedicated PC, other applications can be
run alongside the Net2 user interface. Due to distributed intelligence, the
Net2 system does not require the PC to be on for the system to be running.
Each ACU has a capacity of 2,300 events, if the PC is off and this number of
events is exceeded then the most recent events will overwrite the oldest
events.
The minimum specification for a PC running a Net2 system are - Pentium
800Mhz processor, 128 Mbytes RAM, hard disk with 1 Gbyte free space,
800x600, 256 colour monitor, a free UART 16550 serial port, mouse,
keyboard and a CD ROM drive. For best performance, increase the speed of
the processor, the memory to at least 256Mb and hard disk size for systems
over 50 doors or 1,000 users. The operating system should be Microsoft
Windows 98, Windows NT with SP6, Windows 200 or Windows XP. Access
to the Internet will enable easy system updates.
System backup
All system settings and user details are stored in an Access 7 database
(Net2System.mdb). If this database is corrupted or deleted, the system will
have to be reconfigured and all user records will be lost. For this reason it is
essential that a backup copy of this file is made on a regular basis.
Chapter 3 About
23
--- PAGE BREAK ---
The Net2 software creates backup files automatically. A separate copy of the
Net2System.mdb database is made every day the software is used. The
backup file for a day has the date included in the file name (Net2System
YYYYMMDD.mdb). The backup file is created either:
1.
When the application is closed down
OR
2.
At the automatic backup time as set in Options\Backup
If a backup file has already been created for that day, the file will be over
written with the most current version of the database.
The retention period dictates the number of days that the backup files are
kept for.
Note: Backup files should be saved on a different drive to the
Net2System.mdb file.
Event backup
10,000 events are stored in NetSystem.mdb. These are the events that are
displayed in the event screen. In addition, 12 months worth of events are
stored in Net2Events.mdb.
Events are automatically archived to the backup folder. The archived event
files are split into individual years (i.e. Net2 Events 1999.mdb and Net2
Events 2000.mdb).
Chapter 3 About
24
--- PAGE BREAK ---
Chapter 4 Prepare yourself
ACU schedule
Cable schedule
ACU schedule
This form, or a copy, is to be filled out when commissioning the system.
ACU serial number – Each ACU has a unique serial number. This is
displayed on the front of the ACU.
Door Name – i.e. ‘Main entrance’
Operating mode – Options are: inactive, card only, card plus PIN, card plus
code, desktop reader, PIN only, code only. For an explanation of the
difference between code and PIN, refer to Appendix (iv).
Operating mode
Description
Inactive
There is no reader or keypad connected
Card only
There is a PROXIMITY or CARDLOCK
reader connected at this reader position
…presenting a user token
Card plus PIN
There is a reader and a keypad connected at
this reader position
…presenting a user token and
entering a PIN number
Card plus code
There is a reader and a keypad connected to
this reader position
…presenting a user token and
entering a code
Desktop reader
There is a PROXIMITY, CARDLOCK or
desktop reader connected at this reader
position
PIN only
There is a TOUCHLOCK keypad connected
at this reader position
…entering a PIN number
Code only
There is a TOUCHLOCK keypad connected
at this reader position
…entering a code
Figure 4.1
Table showing operating
modes
Chapter 4 Prepare yourself
Access gained by…
Commissioned – Every ACU should be tested as a part of the
commissioning process.
25
--- PAGE BREAK ---
ACU schedule
ACU
serial number
Door name
Chapter 4 Prepare yourself
Operating mode
Reader 1
Reader 2
Commissioned
26
--- PAGE BREAK ---
ACU schedule
ACU
serial number
Door name
Chapter 4 Prepare yourself
Operating mode
Reader 1
Reader 2
Commissioned
27
--- PAGE BREAK ---
Cable schedule
The cable schedule sheet is filled in when laying the cable and wiring the
system.
Cable number – All cables are numbered. Cable numbers can be written on
masking tape or proprietary numbering systems can be used.
Purpose – i.e. reader cable.
From, To – i.e. from ACU12345678 to Junction box 5
Cable type – i.e. 10 core screened
Cable schedule
Cable number
Purpose
Chapter 4 Prepare yourself
From
To
Cable type
28
--- PAGE BREAK ---
Cable schedule
Cable number
Purpose
Chapter 4 Prepare yourself
From
To
Cable type
29
--- PAGE BREAK ---
Cable schedule
Cable number
Purpose
Chapter 4 Prepare yourself
From
To
Cable type
30
--- PAGE BREAK ---
Chapter 5 Fitting
CARDLOCK and PROXIMITY readers
TOUCHLOCK keypads
CARDLOCK and PROXIMITY readers
CARDLOCK
reader
Wall plugs
PROXIMITY
reader
Wall plugs
No.8 X 1"
No.8 X 1"
Cable
M2 X 12
Figure 5.1
Fitting CARDLOCK and
PROXIMITY readers
Chapter 5 Fitting
Cable
M3 X 12
1.
Using the template provided with the reader, drill holes for the two
fixing screws and the cable.
2.
Extend the top of the cable hole to allow the reader to slide down during
fitting.
3.
Insert the raw plugs and screw in the No.8 X 1” screws until a gap of
approximately 2mm remains between the screw head and the face of the
wall. Try the reader on the screws and adjust as required.
4.
Once a good fit has been achieved, thread the cable through the wall and
locate the reader. Lock it into place with the locking screw at the bottom
of the reader. If being installed into a vandal risk area, a tamper
resistant security screw can be used.
31
--- PAGE BREAK ---
Plastic reader
Wall plugs
PROXIMITY
slimline reader
Wall plugs
Cable
Cable
6 x 3/4
6 x 3/4
Figure 5.2
Fitting
CARDLOCK
Figure 5.3
Fitting PROXIMITY
slimline reader
securing screw
securing screw
1.
Using the base plate as a template, mark and drill holes for the cable and
the four screws.
2.
Tap the four small raw plugs into the wall. Fix the base plate securely
with the screws provided.
3.
Feed the reader cable through the back plate and hang the reader at an
angle over the back plate. Then slot the reader into the groove at the top
of the base plate and press the reader into place.
4.
Screw in the securing screw at the base of the reader.
Vandal proof
Proximity reader
Figure 5.4
Main Components of
the PROXIMITY
vandal proof reader.
Mounting plate
End cap
To control unit
This can be mounted in a variety of different ways to solve all constraints
that the installation may have. Its diameter means that only a single 20mm
diameter hole has to be drilled, causing minimal installation debris and
saving time.
The diagrams below show how the reader can be mounted in the most
common types of installations.
Where the reader is buried in the fabric of the wall it is as vandal proof as
the structure.
Chapter 5 Fitting
32
--- PAGE BREAK ---
CAVITY WALL
Junction
box joins
wiring to
control unit
Figure 5.5
Junction
box joins
wiring to
control unit
Figure 5.6
CAVITY WALL
Mortar plug
Vandal proof PROXIMITY
reader mounted from inside
wall, with mortar plug and
plastic end cap placed over
exposed end of reader.
Vandal proof PROXIMITY reader surface
mounted from inside wall in a blind hole
20mm short of surface. The plastic end
cap is placed over the location of
the reader.
In fig 5.5 the reader is mounted from the inside wall (Blind hole) and the
mounting plate is used for a fixing marker.
In fig 5.6 the reader is also mounted from the inside and the mounting plate
is used for a fixing marker.
Figure 5.7
CAVITY WALL
Junction
box joins
wiring to
control unit
Vandal proof PROXIMITY
reader surface mounted onto
wall using mounting plate. The
threaded reader body is
screwed to the plastic end cap
which is fixed to the wall.
Junction
box joins
wiring to
control unit
Figure 5.8
Vandal proof PROXIMITY reader surface
mounted onto a hollow wall. using the
mounting plate. The plastic end cap is placed
over the mounting plate.
In fig 5.7 the reader is surfaced mounted using the mounting plate.
In fig 5.8 the reader is surface mounted on a hollow wall using a mounting
plate.
Fitting the vandal proof reader using the end cap
Chapter 5 Fitting
1.
Using the back plate as a template, mark and drill holes for the
PROXIMITY vandal proof reader and the two screws.
2.
Tap the two small raw plugs into the wall.
3.
Feed the reader cable through the back plate and then screw the back
plate onto the reader. (about 4 or 5 complete turns)
4.
Secure the back plate onto the wall with the 2 (6 x ¾) screws provided.
5.
Secure one side of the end cap onto the back plate and then snap the end
cap onto the back plate.
33
--- PAGE BREAK ---
TOUCHLOCK keypads
TOUCHLOCK
keypad
Wall plugs
6 X 3/4"
TOUCHLOCK
keypad
stainless steel
Wall plugs
No.8 X 1"
Cable
Cable
M2 X 12
Figure 5.9
Fitting TOUCHLOCK
keypads
1.
Using the template provided with the keypad, drill holes for the two
screws and the cable.
2.
Extend the top of the cable hole to allow the keypad to slide down
during fitting.
3.
Insert the raw plugs and screw in the 6 X ¾” (only the top No.8 X 1” for
the stainless steel keypad). Leave a gap of approximately 2mm between
the screw head and the face of the wall. Try the keypad on the screws
and adjust as required.
4.
Once a good fit has been achieved, thread the cable through the wall and
locate the keypad. Lock it into place with the locking screw at the
bottom. If being installed into a vandal risk area, a tamper resistant
security screw can be used.
Plastic ACU enclosure
1.
Mount the housing backplate against the wall and secure using the raw
plugs and No8 X 1 screws provided in the fitting kit.
Enclosure lid
Enclosure backplate
Figure 5.10
Fitting the plastic
enclosure
Chapter 5 Fitting
2.
The ACU can be secured into the housing using the No6 X 12 screws
provided in the fitting kit.
3.
The lid can be fixed in place using the remaining 2 No6 X 12 screws.
4.
Cut-outs and loops for cable ties are provided.
34
--- PAGE BREAK ---
Chapter 6 Wiring
Readers/keypads
Power supply
Inputs and outputs
Desktop reader
Network
Summary
This section covers wiring. Please read the About… section before
attempting installation.
CARDLOCK readers
CARDLOCK and PROXIMITY readers are supplied with 5m of cable. The
colours of the cable cores correspond to the labelling on the Net2 ACU. If
the cable distance is to be extended then the cores that carry power to the
reader must be doubled up as shown.
Orange
Green (green LED)
Green
Yellow (!data)
Yellow
Blue (clock)
Blue
Black and white
Cable extension
Red
Brown
Orange
Green
Yellow
Blue
Mauve
Blk/Wht
Brown
Yellow
Keypad 1
Black and white (0V)
Mauve
CR9540
Brown
Orange
Green
Yellow
Blue
Mauve
Black and white
Keypad 2
Orange (amber LED)
Red and grey
Reader 1
Brown
Yellow
Red and grey
Brown (red LED)
Mauve (!media detect)
Orange
Red (5V)
2 Green
3 Wht/Orange
4 Orange
Network
CAT5 coding
Orange
Screen or spare cores
from network cable
1 Wht/Grn
Chapter 7 Commissioning
35
Tx
Rx
Figure 6.1
Wiring a CARDLOCK
reader cable extension
--- PAGE BREAK ---
PROXIMITY readers
Orange
Green (green LED)
Green
Yellow (!data)
Yellow
Blue (clock)
Blue
CR9540
Cable extension
Mauve
Red
Brown
Orange
Green
Yellow
Blue
Mauve
Blk/Wht
Brown
Black and white
Yellow
Keypad 1
Black (0V)
Brown
Orange
Green
Yellow
Blue
Mauve
Black and white
Keypad 2
Orange (amber LED)
Red and grey
Reader 1
Brown
Yellow
Red and grey
Brown (red LED)
Mauve and white (sounder)
Orange
Red (5V)
2 Green
3 Wht/Orange
4 Orange
Network
CAT5 coding
Orange
Screen or spare cores
from network cable
1 Wht/Grn
Junction box
Tx
Rx
Figure 6.2
Wiring a PROXIMITY
reader cable extension
The cable screen must be connected to 0V (Blk/Wht terminal) when
wiring all readers or keypads.
PROXIMITY slimline readers
Red 12Vdc
Red
Brown
Orange
Green
Yellow
Blue
Mauve
Blk/Wht
Reader 2
Brown
Yellow
Orange
Keypad 2
Brown
Yellow
Blue
Mauve
Blk/Wht
Yellow
0V
N.C.
N.O.
Com
N.C.
N.O.
Com
0V
Orange
Screen or spare cores
from network cable
1 Wht/Grn
3 Wht/Orange
Contact
0V
Network
CAT5 coding
2 Green
Exit
0V
Tamper
PSU
5V
12V
OK
PSU
Tamper
Exit
Contact
Relay 2
Tx
Rx
Relay 1
4 Orange
+12V
Alarm O/P
Inputs
PROXIMITY
slimline reader
1 Door
Access Control Unit
Keypad 1
Brown
Net2
Relay 1
Green
Relay 2
Orange
Reader 1
Black
Power
Red
Brown
Orange
Green
Yellow
Blue
Mauve
Figure 6.3
Wiring a PROXIMITY
Slimline reader to Net2
Chapter 7 Commissioning
36
--- PAGE BREAK ---
Vandal proof readers
Red 12Vdc
Red
Brown
Orange
Green
Yellow
Blue
Mauve
Brown
Reader 2
Yellow
Orange
Blk/Wht
Green is not
connected
Mauve
Relay 1
Blk/Wht
Orange
N.C.
N.O.
Com
Alarm O/P
Keypad 1
Brown
Yellow
N.O.
Com
Relay 2
Black
1 Door
Access Control Unit
Blue
0v
N.C.
0v
PAXTON
ACCESS
Screen or spare cores
from network cable
3 White/Orange
Exit
0v
Tamper
PSU
5v
12v
OK
PSU
Tamper
Exit
Contact
Relay 2
Tx
Rx
Relay 1
4 Orange
0v
Simple & Powerful
Network
2 Green
CAT5 cable coding
1 White/Green
Contact
Inputs
Blue
Green
Yellow
Net2
Reader 1
Orange
Yellow
+12v
Power
Keypad 2
Red
Brown
Figure 6.4
Wiring a PROXIMITY
vandal proof reader to
Net2
TOUCHLOCK keypads
Yellow
Orange
Keypad 2
Red (5V)
Red
Brown
Orange
Green
Yellow
Reader 1
*
Green (green LED)
Blue
Brown
Yellow
Orange
Screen or spare cores
from network cable
1 Wht/Grn
2 Green
3 Wht/Orange
4 Orange
Tx
Rx
Figure 6.5
Wiring a TOUCHLOCK
keypad to Net2
Blk/Wht
Network
CAT5 coding
* 220 Ohm resistor
supplied in the keypad fitting kit
Mauve
Keypad 1
Blk/Wht (0V)
Brown (load)
Yellow (data)
Orange (clock)
To save space on the board, a keypad wired to the Net2 ACU shares power
and LED terminals with the reader.
If using a membrane keypad with the Net2 system the cable should not be
extended over 5m.
Chapter 7 Commissioning
37
--- PAGE BREAK ---
Power supply
Red
Brown
Terminals in PSU
Relay 2
Relay 1
Power
Reader 2
+12V
12V
0V
Tamper
Tamper
BATT+
BATT-
0V
N.C.
N.O.
Com
N.C.
N.O.
Com
Alarm O/P
0V
Contact
+
Inputs
0V
-
-
+
Exit
0V
Tamper
PSU
5V
12V
Figure 6.6
Wiring a power supply
Inputs and outputs - inputs
Exit button
0V
Contact
Inputs
0V
Exit
0V
Push to make
button
Tamper
PSU
5V
12V
Figure 6.7
Wiring an exit button
Door contact
0V
Contact
Inputs
0V
Normally closed
door contact
Exit
0V
Tamper
PSU
5V
12V
Figure 6.8
Wiring a door contact
Chapter 7 Commissioning
38
--- PAGE BREAK ---
Power supply tamper
0V
Contact
N.O.
Inputs
0V
Exit
COM
0V
Tamper
PSU
5V
12V
Figure 6.9
Wiring a power supply
tamper switch
PSU – mains monitoring
0V
Contact
Inputs
0V
Exit
COM
0V
N.O.
Tamper
N.C.
PSU
5V
12V
Figure 6.10
Wiring mains monitoring
Mains fail output relay in
power supply
Inputs and outputs - outputs
Relay 1 - lock
Wiring schematic illustrates wiring for the two main types of 12Vdc electric
release mechanism. Other electrical devices can be switched using the
voltage free relay contacts.
Fail closed
Fail open
Power
0V
Jumper*
N.O.
Com
Relay 1
N.C.
Diode**
N.C.
Relay 2
Power
2 r edae R
Relay 1
2 r edae R
Relay 2
Red
Brown
Red
Brown
+12V
N.O.
Com
Alarm O/P
0V
N.C.
N.O.
Com
N.C.
Com
0V
0V
Contact
Inputs
0V
Exit
0V
Exit
0V
Tamper
Tamper
PSU
PSU
5V
*
12V
5V
12V
Chapter 7 Commissioning
Diode**
N.O.
Contact
Figure 6.11
Wiring a lock
Jumper*
Alarm O/P
0V
Inputs
+12V
The jumper is very important. Without it the lock will not work.
39
--- PAGE BREAK ---
** Diode is supplied in the fitting kit. Reference: 1N4001 (only suitable for
locks up to 1A). Diode must be fitted with correct orientation as shown in
figure 6.11.
Other electrical devices can be switched using the voltage free relay contacts.
If an ac lock is used then a transient absorber must be fitted across the
lock.
Relay 2 – sounder
Red
Brown
Relay 2
Relay 1
Power
Reader 2
Figure 6.12
Wiring a sounder
+12V
0V
N.C.
N.O.
Com
N.C.
N.O.
Com
12Vdc doorbell
If an ac device is used then a transient absorber must be fitted across the
device.
General purpose output – alarm sounder
This is an open drain output and is capable of switching 1Amp at 12-24Vdc.
The load of this output must be taken into consideration when selecting a
suitably rated power supply, refer to About…/Power supplies/Choosing
guide.
Red
Brown
Chapter 7 Commissioning
Relay 2
Relay 1
Power
Reader 2
Figure 6.13
Wiring an alarm sounder
+12V
0V
N.C.
N.O.
ALARM
Com
N.C.
N.O.
Com
Alarm O/P
12Vdc alarm
40
--- PAGE BREAK ---
Wiring into a fire alarm
Push to break
Press here
Red
Brown
Relay 2
Relay 1
Power
Reader 2
+12V
0V
N.C.
Jumper*
N.O.
Com
N.C.
N.O.
Com
Alarm O/P
0V
Contact
Inputs
0V
Figure 6.14
Wiring into a break glass
local to the door
Exit
0V
Fail open release
Tamper
PSU
12V
5V
Fire alarm relay
Red
Brown
N.O.
COM
Press here
Relay is continuosly
energised
Relay 2
Relay 1
Power
Reader 2
+12V
0V
N.C.
Jumper*
N.O.
Com
N.C.
N.O.
Com
Alarm O/P
0V
Contact
Inputs
0V
Fail open release
PSU
5V
*
Chapter 7 Commissioning
0V
Tamper
12V
Figure 6.15
Wiring into a fire alarm
system relay
Exit
The jumper is very important. Without it the lock will not work.
41
--- PAGE BREAK ---
Software controlled fire doors
Fire doors can also be configured through the Net2 software. A fire alarm
relay, whose contacts will open in the event of a fire alarm, can be wired into
any unused input of any control unit. For instance, to wire it into the
Tamper input, it should be connected between 0V and the Tamper input.
Under the doors configuration for the ACU with the fire alarm relay
connected to it, on the Fire doors tab, you can specify which input is to be
used as the fire alarm input (Tamper in this case) and which doors should
open. It is also possible to specify that a roll call report for a certain area
group should be generated if a fire alarm should occur.
Important note: This feature requires the Net Server to be running, and the network to be functional. If the
server is not running for any reason, this feature will not operate as expected. Consequently, break-glasses
should be fitted, in conjunction with fail open releases, to all fire doors, to ensure a reliable egress method in
the event of an alarm.
Chapter 7 Commissioning
42
--- PAGE BREAK ---
Network
Data line cable
Apart from at the ends of the data line, there will be an incoming and
outgoing cable at each ACU. The ACU has a connection label showing
CAT5 connection colour coding. CR8723 cable has 2 individually screened
twisted pairs. White/Green and Red/Black. If CR8723 cable is used, it
should be connected 1-White, 2-Green, 3-Red and 4-Black.
Orange
Keypad 1
Yellow
From last ACU
2 Green
3 Wht/Orange
To next ACU
Relay 2
Tx
Rx
Figure 6.16
Wiring the network cable
Relay 1
4 Orange
Network
CAT5 coding
Screen or spare cores
from network cable
1 Wht/Grn
All screens need to be wired into the Screen terminal. If unscreened cable is
used, all unused cores should be wired into the Screen terminal.
120 Ohm termination resistors are required at either end of the data line.
These are supplied in the fitting kit.
Orange
Keypad 1
Yellow
2 Green
3 Wht/Orange
Relay 2
Tx
Chapter 7 Commissioning
Rx
Figure 6.17
Wiring the termination
resistors
Relay 1
4 Orange
Network
CAT5 coding
Screen or spare cores
from network cable
1 Wht/Grn
43
--- PAGE BREAK ---
RS485/232 communications converter
The PC with the RS485/232 interface can be positioned at the most
convenient point along the network. The wiring is the same as at the ACUs.
RS485/232
Converter
To interface
power supply
Also screen or spare
0v cores from network cable
12V d.c.
2
Green
3
White/Orange
4
Orange
Network
White/Green
CAT5 Wiring
Figure 6.18
Wiring the RS485/232
communications converter
1
Connection to PC
serial port via.
supplied lead
IMPORTANT NOTE:
The latest R485/232 converters do not contain termination resistors. If the
converter is wired at the end of the network two 120 Ohm resistors must
be wired between terminals 1 and 2, and 3 and 4.
Older RS485/232 converters may contain termination resistors. This type
can be identified by two internal jumpers. If this type of converter is
wired at the end of the network then these are left in place. Otherwise
these jumpers have to be removed (JP1 and JP2 from converter PCB).
RS485 repeater
The RS485 repeater allows the data line to be extended beyond 1 Km and
should be installed within this limit. It is recommended that only one
repeater be used per data line.
Termination
Resistors
Existing part of network
containing the master PC and
ACUs which comply with the
1Km rule
From From
Extension PC
Additional part of the
network containing ACUs
that would not normally
meet with 1Km
specification
12V
Screen or spare cores
from network cable
White/Green
Green
White/Orange
Orange
White/Orange
Green
White/Green
Screen or spare cores
from network cable
Orange
PC
Chapter 7 Commissioning
12v
0v
Figure 6.19
Wiring the RS485 repeater
Ext
44
--- PAGE BREAK ---
5
6
Green
White/Orange
Orange
2
3
4
Network
CAT5 cable coding
Refer to network
wiring instructions
White/Green
1
Screen or spare cores
from network cable
Orange
Simple & Powerful
ACCESS
PAXTON
1 Door
Access Control Unit
Net2
Reader 2
Red
OK
5v
Tamper
PSU
Contact
Relay 2
Exit
Relay 1
Tx
NETWORK CABLE
12v
From
previous
ACU
YZ
0
WX
UV
9
8
PQR
Brown
Yellow
Keypad 1
ST
7
MNO
JKL
Reader 1
GHI
4
2
DEF
3
1
Black/White
Mauve
Blue
Black/White
Yellow
Orange
Green
Blue
Orange
Brown
Keypad 2
Mauve
ABC
Red
Yellow
Brown
Green
Membrane or
stainless steel
keypad
CARDLOCK reader
Yellow
Relay 1
Power
PSU
Tamper
0v
Exit
0v
Contact
0v
Alarm Output
Com
N.O.
N.C.
Com
N.O.
N.C.
0v
+12v
IMPORTANT: the red wire on
Paxton Slimline, Vandal proof,
Back box and Panel mount
PROXIMITY readers must be
connected to the +12V terminal
Orange
Relay 2
Chapter 7 Commissioning
Brown
Inputs
PROXIMITY reader
Unswitched
spur
To next ACU
Exit Button
Normally closed
door contact
12V d.c.
alarm sounder
Fail Closed
electric release
Power
supply
Tamper Switch
12V d.c
power
supply
Summary
Rx
Figure 6.20
Wiring summary
45
--- PAGE BREAK ---
Chapter 7 Commissioning
Hardware
Software
Hardware – network
Before power is applied to the system, the network must be checked. Check
all network connections. Before testing, remove the network terminals from
every ACU.
Yellow
Keypad 1
Brown
2 Green
3 Wht/Orange
Tx
Rx
Figure 7.1
Remove network
connections
Relay 1
4 Orange
Network
CAT5 coding
Orange
Screen or spare cores
from network cable
1 Wht/Grn
Data cable
The resistance between each pair must be measured. This ensures that the
termination resistors are connected and the cable is continuous.
1.
Using a Multimeter, measure the resistance between terminals 1 and 2 of
the network connection.. A resistance of between 50 and 70 Ohms is
normal.
2.
Repeat step 1 for terminals 3 and 4.
If the measured resistance is not within the recommended range then
connections and cable should be checked throughout until the fault is found.
Screen shorts
1.
At one end of the network check the resistance between the screen and
terminal 1 of the network connection. The resistance should be high.
This means that the screen is not shorted with this core along its length.
2.
Repeat step 1 for terminals 2, 3 and 4.
If the measured resistance is low then the cable and connections should be
checked.
Chapter 7 Commissioning
46
--- PAGE BREAK ---
Screen continuity
To ensure resilient communications, the network cable is screened. It is
essential to the reliability of the system that the screens are continuous. To
check this:
1.
At one end of the network, connect the screen to terminal 1.
2.
At the other end of the network, use a multimeter to check that the
resistance between screen and terminal 1 is low (Less than 10 Ohms).
If the screens are not continuous then the cable and connections should be
checked.
Once the network has passed the tests, the network terminals must be
replaced in the ACU.
Hardware – the Access Control Unit (ACU)
Once all wiring has been completed and the system is ready to go, each ACU
will require commissioning.
Turning on the power
If an ACU has a backup battery power supply, the mains should be
connected first. Once mains power is being supplied to the ACU, the
batteries can be connected. This will prevent damage to batteries caused by
a sudden surge of current. If power to the ACU is being switched off,
batteries should be disconnected before the mains is switched off.
ACU test
The diagnostic LEDs allow the functionality of each ACU to be tested
quickly and accurately.
Check that the…
If not…
12V and 5V LED’s are on.
Power supply problem, refer to Faultfinding/system problems.
OK LED is pulsing regularly?
Processor problem, refer to Faultfinding/system problems.
Exit LED is on when the exit button is pressed.
Input problem, refer to Faultfinding/system problems.
Contact LED is on when the door is closed.
Input problem, refer to Faultfinding/system problems.
Tamper LED is on when the circuit is closed.
Input problem, refer to Faultfinding/system problems.
PSU LED is on when the circuit is closed.
Input problem, refer to Faultfinding/system problems.
Present or swipe a user token through all readers connected to the Reader problem, refer to FaultACU. The red LED should flash to indicate an invalid card.
finding/system problems.
The Door relay 1 LED comes on when the exit button is pressed.
If there is no exit button then jumper the exit button terminals
with a piece of wire.
Figure 7.2
ACU commissioning test
Chapter 7 Commissioning
Output problem, refer to Faultfinding/system problems.
Every ACU should be tested in this way before installing or running the
software.
47
--- PAGE BREAK ---
Software – installing the program
IMPORTANT NOTE
The Net2 software requires Internet Explorer 4 or greater. If this is not
already installed on the PC then it is available on the Net2 CD. To install,
simply run D: \IE6.0\ie6setup.exe (Where D is the drive letter of the CD
Rom drive)
1. Load the CD into the drive.
2. The setup application can be automatically run (if autorun is enabled),
otherwise setup can be run using Add/Remove Programs or by
browsing to the CD drive and running Setup.EXE.
3. You will be warned that other applications should be closed down before
installing the Net2 software. If there are any other programs running
then press Cancel and close them before running setup. If there are no
other programs open then press Next and proceed with installation. You
will need to accept the license agreement before being able to proceed to
the Registration Information. The CD key is supplied with the CD.
4. Enter the details of the registered owner of the Net2 software. All fields
must be filled in to proceed.
Figure 7.3
Get Registration
Information
If the software is to be installed in demonstration mode (with a sample
database with which to demonstrate the functionality of the software)
then do not enter anything. Press Next to continue with the installation.
5. The Net2 software consists of the application (the program itself) and the
database (where events, user details, system information etc. is held).
Enter the desired locations for the application and the database. The
default location for the application is C:\Program Files\Paxton Access
and this would ordinarily be correct.
Chapter 7 Commissioning
48
--- PAGE BREAK ---
Figure 7.4
Choose Destination
Location
The default location for the database is C:\Net2 Access Control
6.
In Net2 V2, it was necessary to enter which comport should be used.
Net2 V3 supports multiple comports, and features the auto detection of
Net2 control units. No comport selection is required.
7.
Next you must choose the options that you want to install. Only select
Advanced if you want to set up the advanced options. These include
Areas, Anti-passback, Roll Call and Cameras. Anti-passback and Roll
Call require areas to also be enabled.
Figure 7.5
Choose Install Options
Chapter 7 Commissioning
49
--- PAGE BREAK ---
8.
Select Yes or No to backup files being kept. Keeping backup files will
allow you to undo the installation. Press Next to continue.
9.
Enter the location for the shortcut in the start menu. The default
location is Net2 Access Control in Programs.
Figure 7.6
Backup Replaced Files
10.
Figure 7.7
Select Program Group
Chapter 7 Commissioning
50
--- PAGE BREAK ---
Select whether the Net2 shortcuts should be added to the desktop. Press
Next to continue.
11. Press Next to start installing the application files. Installation should
take no more than a minute.
Figure 7.8
Installing
12. Once the application files have been copied, press Finish to exit.
If problems occur, please refer to Fault-finding/system problems.
Chapter 7 Commissioning
51
--- PAGE BREAK ---
Software – installing the database
1.
Run the Net2 program by double clicking on the Net2 Access Control
shortcut. The Net2 Server will start-up automatically, creating a new
database if necessary, and detecting any control units which are
connected. It will open all available comports, and once it has finished
interrogating the network, will close down any which do not connect to
Net2 control units.
If you have run the Net2 Access Control application before and wish to
‘start from fresh’ then delete the system database (Net2system.mdb). The
default location for this is C:\Net2 Access Control.
Warning: All system settings are held in the database.
2.
The default operator is System engineer with the password ‘net2’
(Warning – the password is case sensitive).
3.
Once into the software select Operators\System Engineer. Enter a new
password and confirm.
Figure 7.9
Operator Configuration
Wizard
This password will completely restrict access to the program. Make a
note of the password:
This password must now be used to gain access to the Net2 Access
Control application. Press Finish to save changes and exit the wizard.
5.
Chapter 7 Commissioning
The Net2 Server will automatically upgrade the firmware of ACU’s as
necessary. Under normal circumstances this will only occur if the
installation is new, or following a software upgrade.
52
--- PAGE BREAK ---
Software – configuring the doors
Figure 7.10
Configuring the doors Reader1
The settings for each control unit are configured in this screen. The ACU
serial number is shown in the top left corner of the main display. The lower
section of the main display has tabs that allow access to the different settings
(Reader1, Reader2, Alarm, Codes and Events). Sections are accessed by
clicking on the relevant tab.
Door name
When the system is first powered up, the control unit name will be the same
as the serial number. A descriptive name should be given to a control unit.
This name will appear in the list of doors.
Door open time
The door open time is the amount of time that the output relay is switched
for (the amount of time that the locking mechanism is released). The default
setting is 7 seconds. This can be modified within the range 1 to 5000
seconds.
Unlock the door during
This feature allows the user to select a timezone in which the locking
mechanism is released. If the working hours timezone is selected, the door
will be open during working hours. An example of where this may be
useful is where a receptionist is present to greet visitors during office hours.
The main door can be left open so that anybody can walk in. Out of working
hours the door is automatically locked and a valid user card is required to
gain access.
A door can be held open during any timezone. For more information on
timezones refer to About…\Timezones.
Apply
When any changes are made to the door settings the Apply button must be
pressed to commit the changes to the database.
Chapter 7 Commissioning
53
--- PAGE BREAK ---
Open door
The open door feature will release the locking mechanism for the door open
time.
Doors\[Door name]\Reader 1
The Reader 1 tab shows the settings corresponding to Reader 1 and Keypad
1 connected to that control unit.
Name
The default name for reader 1 is [Door name] (IN). The default name for
reader 2 is [Door name] (OUT).
The reader names set here will appear in reports and be used to set access
levels.
Reader type
This should be set to the relevant type of reader.
Setting
Description
None
If no reader is connected.
Paxton reader
If a CARDLOCK or PROXIMITY reader is
connected.
Clock and data
If a non – Paxton clock and data reader is
connected
Wiegand
If a Wiegand reader is connected.
Keypad
This should be set to the relevant type of keypad.
Setting
Description
None
If no reader is connected.
Paxton keypad
If a TOUCHLOCK keypad is connected.
Card data format
Every card enrolled on a Net2 system must have a unique number. The card
data format option allows Net2 to use cards and tokens with a variety of
encoding formats.
The default setting is for the Net2 encoded cards and tokens (random 8 digit
number).
Setting
Description
Default
This is for Net2 encoded cards and tokens
(random 8 digit number).
Paxton cards
This is for CARDLOCK and PROXIMITY
cards and tokens (encrypted number).
Bank cards
This allows Net2 to use bank cards.
Refer to About…\Options\Card data formats in the User reference manual
for more detailed information.
Chapter 7 Commissioning
54
--- PAGE BREAK ---
Reader operating mode
The correct operating mode should be selected from the drop down menu.
Setting
Description
Inactive
There is no reader or keypad connected (or
they are inactive for some other reason).
Card only
Access is granted by swiping a valid user card.
Card plus PIN
Access is granted by swiping a valid user card
AND entering the relevant PIN.
Card plus code
Access is granted by swiping a valid user card
AND entering a valid code.
Desktop reader
A desktop reader is connected. This reader is
to be used to add users to the system.
PIN only
Access is granted by entering a valid PIN.
Code only
Access is granted by entering a valid code.
Card or PIN
Access is granted by swiping a valid card OR
entering a valid PIN.
Card or code
Access is granted by swiping a valid card OR
entering a valid code.
Card, PIN or code
Access is granted by swiping a valid card OR
entering a valid PIN OR entering a valid code.
For information on the difference between PIN and code, refer to
Appendix\Difference between code and PIN.
The list of operating modes displayed in the drop down menu is dependent
on the reader type and keypad type settings. For example, if a keypad is
configured without a reader, only Inactive, Code only and PIN only will be
displayed in the drop down menu.
Timed operating modes
This feature allows a different operating mode within a timezone. For
example, card plus PIN may be required outside working hours and card
only within working hours.
To configure this, select the required timezone from the drop down menu.
Select the required operating mode from the other drop down menu.
Reader action
This is the action that will happen when access is granted.
Setting
Description
Relay 1 – door open time
Access granted will open relay 1 for door open
time.
This can be used for temporarily releasing
electric locking mechanisms.
Relay 2 toggles
Access granted will toggle relay 2. For
example, a valid card will open relay 2. The
relay will remain open until another valid
card is presented.
This can be used for switching an alarm
system on and off, opening shutter doors etc.
Chapter 7 Commissioning
55
--- PAGE BREAK ---
Doors\[Door name]\Reader 2
The Reader 2 tab shows the settings corresponding to Reader 2 and Keypad
2 connected to that control unit.
The default name for reader 2 is [Door name] (OUT). This can be changed.
All settings are set as shown for reader 1. Readers 1 and 2 are configured
separately and can have completely different settings.
Doors\[Door name]\Alarm
Figure 7.11
Configuring the doors Alarms
There are 4 types of alarm that can be configured for each ACU.
Type of alarm
Description
Requires…
Door forced open
The door is opened without the permission of
the access control system.
Door contact
Door left open
The door is opened with the permission of the
access control system but is not closed within
the specified time.
Door contact
PSU failure
The mains supply to the control unit PSU fails.
If battery backup is fitted then the system will
continue to operate.
Mains fail output on power
supply
Tamper
The control unit enclosure has been opened.
Tamper switch on control unit
enclosure
Each type of alarm has its own tab and is configured in the same way. The
settings for each type of alarm can be different.
Chapter 7 Commissioning
56
--- PAGE BREAK ---
Local alarm
On every control unit there is an alarm output. This can be connected to a
bell, sounder, light etc. The local output can be turned on or off for each
type of alarm.
If the local alarm is activated then a delay can be imposed before the alarm is
activated. It can also be configured in a particular way to distinguish
between different alarm events. The alarm can be set to sound continuously
or can be configured manually.
Testing the local alarm
The local alarm can be tested by activating it and silencing it from the PC.
Alarm reporting at the PC
All alarm events are reported at the PC. A delay can be imposed before an
alarm event is sent.
Doors\[Door name]\Codes
Figure 7.12
Configuring the doors Codes
Note: The Codes tab only appears if a keypad is configured on the
control unit.
Codes can be simply added and deleted. Codes added in this screen will
only be valid for the individual door.
Up to 50 codes can be valid at any one time. Codes can be between 4 and 8
digits long.
Chapter 7 Commissioning
57
--- PAGE BREAK ---
Commissioning checks
The system is now configured. Ensure that:
•
A user token given access privileges at the PC does open the doors that
it is supposed to.
•
Events are being reported back to the PC.
•
All locking hardware is functioning correctly, i.e. the doors open when
they should do.
•
Alarm events such as door forced open are reported back to the PC from
every door.
The system can now be handed over to the end user. Please refer to the Net2
system user manual (228-177) for full details of operating the system.
Chapter 7 Commissioning
58
--- PAGE BREAK ---
Chapter 8 Fault-Finding
59
--- PAGE BREAK ---
Chapter 8 Fault-finding
Fault diagnosis
System problems:
Power supply
Processor
Inputs
Reader/keypad
Outputs
Communications
PC
Paxton Access technical help
Fault diagnosis
Establish at first hand that the problem is genuine. Many problems are
reported that are caused by user error i.e. tokens not presented properly or a
programming error at the PC.
Once the problem is verified, it may be necessary to do a full system check to
establish which aspect of the system is not functioning correctly. If the exact
nature of the problem is already known then skip to the relevant section in
this chapter.
Communications test
Whilst the Net2 access control program is running walk round and confirm
that the Rx and Tx LEDs are flickering regularly on each control unit. The
system is polling several times per second. The Rx LED flashing indicates
that the ACU is receiving network messages from the PC and the Tx LED
flashing indicates that the ACU is transmitting network messages back to
the PC. If the LEDs are flashing as described then communications are
functioning.
If the Rx and Tx LEDs are not flashing on any or all of the ACUs then there
is a communication problem, refer to Fault-finding/System problems.
Chapter 8 Fault-Finding
60
--- PAGE BREAK ---
ACU test
The diagnostic LEDs allow the functionality of each ACU to be tested
quickly and accurately.
Check that the…
If not…
12V and 5V LEDs are on.
Power supply problem, refer to Faultfinding/system problems.
OK LED is pulsing regularly?
Processor problem, refer to Faultfinding/system problems.
(See OK LED status at the end of this section for more details)
Exit LED is on when the exit button is pressed.
Input problem, refer to Faultfinding/system problems.
Contact LED is on when the door is closed.
Input problem, refer to Faultfinding/system problems.
Tamper LED is on when the circuit is closed.
Input problem, refer to Faultfinding/system problems.
PSU LED is on when the circuit is closed.
Input problem, refer to Faultfinding/system problems.
Present or swipe a user token through all readers connected to the Reader problem, refer to FaultACU. The red or green LED should flash to acknowledge a valid finding/system problems.
or invalid card.
Enter a valid PIN number or code to any keypads connected to
the ACU and check that the green LED flashes.
Keypad problem, refer to Faultfinding/system problems.
The Door relay 1 LED comes on when the exit button is pressed.
If there is no exit button then jumper the exit button terminals
with a piece of wire.
Output problem, refer to Faultfinding/system problems.
If used, the other outputs Relay 2 and Gen O/P must function as
required.
Output problem, refer to Faultfinding/system problems.
Figure 8.1
ACU fault diagnostic test
OK LED Status
The OK LED has different flash modes to indicate different system status.
A single short flash, once a second, means that the ACU is functioning
properly, and that it is in communication with the Net2 Server.
A double short flash, once a second, means that the ACU is functioning
properly, but that it is currently off-line.
Rapid continuous flashing means that there is a real time clock failure. The
ACU will allow access to users with 24/7 access rights.
The LED blinking 1 second on, 1 second off means that the ACU has a real
time clock failure, but it has been ‘told’ the time by the Net2 Server. It will
continue to run normally as long as it does not loose it’s power, unless the
Net2 Server is running to set it’s time again. An ACU with a real time clock
failure should be replaced.
Chapter 8 Fault-Finding
61
--- PAGE BREAK ---
System problems – power supply
• 12Vdc supply – Set a multimeter to dc range and measure the supply
across the power terminals of the ACU. If this is not between 10 and 15V
then there is a problem with the power supply.
• Power supply ripple – Set a multimeter to ac range and measure the
supply across the power terminals. This measures the ripple of the
supply. If a voltage above 2V is measured then there is a problem with
the power supply.
• 5Vdc supply – The ACU has an on board regulator.
If the 12V LED is on and the 5V LED is off, the power to the ACU must be
switched off immediately, or damage to the board may result. A typical
cause of this would be an incorrectly fitted or faulty reader.
To confirm that the regulator is functioning correctly, set a multimeter to
dc range and measure the voltage across the Red and Blk/Wht terminals
of each reader. A voltage between 4.8 and 5.2V indicates that the
regulator is working.
If problems persist then contact the Paxton access technical helpline.
System problems – processor
• Power – Turn the power to the ACU off and then on. When the power is
re-applied, the processor should be working and the OK LED should be
pulsing regularly.
If problems persist then contact the Paxton access technical helpline.
System problems – inputs
• Power – Turn the power to the ACU off and then on.
• ACU test – Disconnect the input and place a jumper between the 2 input
terminals and check whether the relevant diagnostic LED comes on. If
the LED comes on then the ACU is working. If the ACU is working then
the problem lies with the input itself, e.g. test the door contact for
continuity and short circuit conditions.
If problems persist then contact the Paxton access technical helpline.
System problems – reader/keypad
• Power – Turn the power to the ACU off and then on.
• Connections – Check wiring and integrity of reader/keypad terminal
connections.
• Cable – Check that the correct cable is used and that the maximum cable
distance has not been exceeded.
Figure 8.2
Table showing maximum
cable extensions for
readers/keypads
Chapter 8 Fault-Finding
Reader/keypad
Maximum distance from ACU
TOUCHLOCK keypad
5 metres
TOUCHLOCK keypad stainless steel
50 metres
CARDLOCK reader
100 metres
PROXIMITY reader
80 metres
62
--- PAGE BREAK ---
• Screen - The screen must be continuous and connected to 0V.
• Supply voltage – Using a multimeter, confirm that the reader has
sufficient voltage. Voltage should be measured at the reader/keypad
across the Red and Blk/Wht terminals.
Figure 8.3
Table showing minimum
voltages for
readers/keypads
Reader type
Minimum voltage
PROXIMITY reader
CARDLOCK reader
TOUCHLOCK keypad
TOUCHLOCK keypad stainless steel
OEM reader
4.5V
4.5V
4.5V
4.5V
Consult manufacturers
literature
• User token – Check that the user token used for testing the reader is
operational. It can be tested on other ‘known good’ readers.
If problems persist then contact the Paxton access technical helpline.
System problems – outputs
• Power – Turn the power to the ACU off and then on.
• ACU test – Disconnect the output (i.e. lock) trigger the output and check
whether the relevant diagnostic LED comes on. If the LED comes on then
the ACU is working. If the ACU is working then the problem lies with
the output device itself, consult device manufacturer.
• Output device test – The operation of the output device can be tested by
applying power directly to it.
If problems persist then contact the Paxton access technical helpline.
System problems – communications
If some ACUs are communicating but not all
• Finding the problem – A full network test is documented in the
Commissioning/Hardware section of this document. This should be
completed before progressing with this section.
• Power – Turn the power to the ACUs off and then on.
• Connections – Check wiring and integrity of network terminal
connections at the problem ACUs.
• Cable – Check that the correct cable is used and that the maximum cable
distance has not been exceeded, refer to About…/Readers and
keypads/Cable details.
If problems persist then contact the Paxton access technical helpline.
If all ACUs are not communicating
• Finding the problem – A full network test is documented in the
Commissioning/hardware section of this document. This should be
completed before progressing with this section.
• Power – Turn the power to the ACUs off and then on.
• Interface – Ensure that the interface has power. Check that all
connections are as they should be.
Chapter 8 Fault-Finding
63
--- PAGE BREAK ---
• Connections – Check wiring and integrity of network terminal
connections.
• Cable – Check that the correct cable is used and that the maximum cable
distance has not been exceeded, refer to About…/Readers and
keypads/Cable details.
• Termination resistors – Check that the 120 Ohm termination resistors are
in place, 2 at each end of the network.
• PC – Please refer to System problems/PC.
If problems persist then contact the Paxton access technical helpline.
If there are inconsistencies between the database and control
unit information
•
Reinstate – Press the Reinstate button as shown in figure 8.4, select the
controllers to reinstate. This will reset all selected ACUs and download
the relevant database information to them.
Figure 8.4
Reinstate ACUs
System problems – PC
If the system is not communicating
• Comport - Ensure that the RS485/232 interface is connected to the correct
comport.
• PC requirements - Ensure that the PC meets the minimum requirements,
refer to About…/PC/Requirements.
• Comport test - Ensure that the comport is functioning. This can be tested
by completing the following:
1) If HyperTerminal is not already installed then install it*.
Chapter 8 Fault-Finding
2)
Open Windows explorer and open folder C:\Program
files\Accessories\Hyper terminal. Run Hypertrm.exe.
3)
Enter paxton as the name of the connection and press OK.
4)
Next to ‘Connect using’ choose the relevant comport from the drop
down list and press OK.
64
--- PAGE BREAK ---
5)
Enter the following settings:
Bits per second
Data bits
Parity
Stop bits
Flow control mode
6)
On this computer serial port we must create a link between pins 2
and 3.
Pins 2&3
Pins 2&3
Figure 8.5
25 and 9 pin comports
115,200
8
None
1
None
25 PIN COM port
9 PIN COM port
7)
If the serial port is functioning correctly, then, whilst the link is in
place, any text entered will appear on the screen. When the links are
broken, no text will appear on the screen.
*
To install Hyper Terminal, the Windows installation disk (as
supplied with the PC) is required. Go into the control panel
(Located in settings on the start menu) and select Add/Remove
Programs. Select the ‘Windows Setup’ tab at the top of the screen.
Double click on communications and check Hyper Terminal
installation if it is not already checked. Press OK. Press Apply. The
Windows disk will be requested and the software can be installed.
If problems persist then contact the Paxton Access technical helpline.
If the Net2 program will not install
• PC requirements - Ensure that the PC meets the minimum requirements,
refer to About…/PC/Requirements.
If problems persist then contact the Paxton access technical helpline.
Chapter 8 Fault-Finding
65
--- PAGE BREAK ---
Paxton Access technical help
Paxton Access offer a telephone technical help service. This is designed to
assist installers at site installing or maintaining products manufactured by
Paxton Access. Also technical questions concerning specifying etc. can be
answered.
The person calling must have working knowledge of the system and will be
expected to have read this manual and followed its guidelines and system
problem checks.
The person calling must also have some PC knowledge. They must at least
understand installing programs and using Windows explorer.
To be eligible for technical help the site must be registered. The
registration form is included in with the Net2 software. For a copy of the
registration form refer to Appendix (x).
To administer the registration of sites and the distribution of software, a
technical support ID number is required to qualify for technical help. This
technical support number is very easily generated from the software (in the
Help drop down menu at the top of the screen).
The technical support ID number will only be valid if the software has been
registered.
The Paxton Access technical helpline is available Mon-Fri 8.30am-5.30pm.
+44 (0) 870 6080886
The web site address for Paxton Access is www.paxton-access.co.uk
Chapter 8 Fault-Finding
66
--- PAGE BREAK ---
Chapter 9 Appendix
67
--- PAGE BREAK ---
Chapter 9 Appendix
(i)
Operation of a relay explained
(ii)
Fail open and fail closed locks explained
(iii)
Difference between code and PIN explained
(iv)
Glossary of terms
(v)
ISO card unprintable area
(vi)
Net2 part numbers and product descriptions
(vii) Extending a Net2 system
(viii) Replacing a control unit
(ix)
Site registration form
Appendix (i) Operation of a relay explained
The Net2 ACU contains two relays. These are very versatile and can be used
to switch electrical devices. A relay consists of a coil and a switch and has
output terminals common (COM), normally open (N.O.) and normally
closed (N.C.).
Figure 9.1
Operation of a relay
Coil not energised
(natural state)
Coil energised
COM N.C. N.O
COM N.C. N.O
In the de-energised state, common and normally closed are connected.
When the coil is energised, the switch moves and common and normally
open are connected. As soon as the coil is de-energised the switch springs
back to the normally closed position.
The output terminals COM, N.O. and N.C. are voltage free. This means that
they can be included as part of a circuit to switch power to OR from an
electrical device.
Chapter 9 Appendix
68
--- PAGE BREAK ---
Appendix (ii) Fail open and fail closed locks explained
Fail open (fail safe)
Fail open devices require power to lock, i.e. if there is no power to the device
it is unlocked. An example of a fail open device is a magnetic lock
(maglock).
A fail open locking device is a requirement for fire doors. This is because it
is not reliant on electrical power to unlock.
It is advisable to have a battery backup for systems using fail open devices.
Otherwise a mains power failure would lead to doors unlocking for the
period of the mains failure.
Fail open devices are inefficient in terms of power consumption when
compared to fail closed devices. This is because they are powered for the
majority of the time, i.e. when the door is locked.
Fail closed (fail secure)
Fail closed devices require power to unlock, i.e. if there is no power to the
device it is locked. Most standard electric releases are fail closed.
If battery backup is not fitted, mains loss would result in doors being locked
for the period of the power failure.
Fail closed devices are more efficient that fail open devices. This is because
they are only powered when the door is unlocked.
Appendix (iii) Difference between code and PIN explained
PIN stands for Personal Identification Number. This is a number that is
specific to an individual user. A user code can be common to many users.
Example of code only: A keypad has two codes to control the access of 1,000
users through an access point. 300 users use one code and 700 use the other.
Codes are very quick to setup; thousands of users can be given access to an
area if the code is disclosed. Access privileges can be adjusted for groups of
users, where the users are grouped together by a common code.
Example of PIN only: A keypad controls the access of eight users through a
door. Each of the eight users has their own PIN, which they use to gain
access.
Using PINs mean that access rights can be changed for every individual
without affecting other users. PINs also allow users to be identified by the
system for reporting purposes. However, more numbers valid on a keypad
will increase the chances of guessing a correct number. This means that a
non-authorised person can gain access by randomly pressing keys on the
keypad. To reduce these risks to an acceptable level it is necessary to
increase the number of digits in the PIN.
Example of card plus code: A proximity reader and a keypad are used to
control access through a door. A user is required to present their proximity
card to the reader and enter a valid code.
This involves two elements of security – possession and knowledge. The
possession of the card is required AND a valid code has to be known. If the
card is lost it cannot be used on its own. If the code is discovered it cannot
be used without a valid card.
Example of card plus PIN: A magnetic stripe reader and a keypad are used
to control the access through a door. A user is required to swipe their card
and enter their PIN number. Only the combination of that user card AND
that user PIN number is acceptable.
Chapter 9 Appendix
69
--- PAGE BREAK ---
This involves both possession and knowledge but increases security even
further. If a user card is lost it can only be used to gain access when used
with the specific PIN number. For security reasons bank cash machines use
a card plus PIN system.
Appendix (iv) Glossary
General access control terms
Access control system
An access control system comprises input for identification (e.g. a keypad
or reader), intelligent electronics for decision making and outputs for
operating access point hardware and the access point hardware itself (e.g.
locks, barriers).
Access Control Unit (ACU)
A general term to describe a range of devices which have the control
electronics and intelligence to make the decision to allow access at one or
several points. It will have connectors or cables ready to link to readers,
keypads, locks, etc.
Bench test
The wiring and configuration of a system at the installers premises before
installation. This is a recommended procedure before installing any system
for the first time. The time spent in becoming familiar with the equipment
will invariably be recouped several times over on site.
Coercivity
Coercivity relates to the resilience of the encoding of a magnetic stripe card.
Hi coercivity encoded magstripe cards are more resilient to data corruption
than Lo coercivity cards.
Common Reference (CR)
CR refers to the cable reference numbers commonly used to identify cable
of a specific type.
Distributed intelligence
In a networked access control system access control units are linked and
communicate with each other or a PC used to control the system.
Distributed intelligence means that the access control units hold user
information and system settings locally. This enables the ACUs to carry on
functioning if communications links are severed.
Door open time
An electric locking device has power supplied/denied to release and allow
access when a valid token is presented. The time period that the electric
release is energised/de-energised is referred to as the door open time.
Event recording
Access Control Units may be provided with memory to record events.
Events recorded should include the access point details, date, time and user
ID for each occasion when access is granted. Many other events may be
recorded depending on the system e.g. details of access denied and alarm
events. Where events are recorded the access control unit will be capable
of sending the information to a printer or computer.
Magstripe
Magnetic stripe reading technology – cards with a number encoded on a
magnetic stripe are swiped through a slot on a reader.
Network system
A system where access control units are linked together by data cable for
the exchange of information between units. The purpose of this is to
provide easier configuration and better management information for larger
and more complex applications. All access points on the system can be set
up from a single point. The access control units on network systems record
events. Most systems allow for a computer to be connected to the network
to allow control and reporting to be carried out from a dedicated program.
Photo ID
Where a photograph of the user is printed or attached to their user token
allowing them to be identified.
Proximity
The proximity device is held close to the reader and sends a unique
number by radio signal to the reader.
Chapter 9 Appendix
70
--- PAGE BREAK ---
Tailgating
A term used to describe an individual gaining access through an access
point by following through after an authorised user.
User token
This is a generic term for the devices that users of an access control system
use to identify themselves and gain entry through access points. User
tokens may be magstripe cards, proximity keyfobs, smart cards, etc.
Paxton Access terminology
Proximity ISO card
ISO cards are the same size as standard bank or credit cards. They can be
used with standard card printers for photo ID. They also have a magnetic
stripe that can be encoded for use with other systems such as vending.
Proximity keyfob
Keyfobs are for applications where convenience is important. They are
made of hard plastic and will fit onto a keyring. They can be attached to
car/house keys for reduced losses, hence reducing the cost of replacing
fobs.
Proximity token
Tokens are about credit card size but are thicker. They can be used from
inside wallets or handbags. Adhesive plastic stickers can be applied for
photo ID and the slot in the tokens makes them ideal for use with low cost
badge clips.
Appendix (v) ISO card unprintable area
Unprintable
area
Figure 9.2
ISO card unprintable area
19mm
24mm
ISO cards are suitable for use with an ID card printer, subject to observance
of the non-useable area on the card. The area is defined in figure 9.2 and is
viewed from the magstripe side of the card. It is advised that there may be
surface distortion here, which although within the specification of ISO 7810,
may give poor results if printed upon. This restriction applies to both sides
of the card.
Chapter 9 Appendix
71
--- PAGE BREAK ---
Appendix (vi) Net2 part numbers and product descriptions
Part number
Description
Hardware
489-334
Net2 1 door access control unit
385-527
Net2 1 door ACU in plastic housing
411-381
Net2 1 door ACU with 2A PSU in steel cabinet
857-693
Net2 2amp PSU in steel cabinet with mounting posts
571-692
Net2 housing for ACU black plastic
339-424
1 amp power supply unit
339-425
12V 1.2AH battery for 1A boxed PSU
862-719
12V 7AH battery for 2A boxed PSU
289-641
Net2 RS485/232 kit incl converter, PSU and PC lead
477-836
Net2 RS485 high speed repeater
User tokens
693-112
Net2 proximity tokens pack of 10
695-644
Net2 proximity keyfobs box of 10
692-448
Net2 proximity ISO cards box of 10
695-573
Net2 magstripe cards box of 10
Software
936-001
Net2 standard software 50 doors, 2000 users
945-065
Net2 standard plus software 200 doors, 10,000 users
Readers/keypads
409-711SC
CARDLOCK reader satin chrome
355-098
PROXIMITY reader
600-628SC
TOUCHLOCK keypad satin chrome
485-374
TOUCHLOCK keypad stainless steel
376-001
Desktop reader prox and magstripe
Cable
Chapter 9 Appendix
166-025
Reader cable 10 core CR9540 25m roll
166-100
Reader cable 10 core CR9540 100m roll
189-100
Data cable 2 pair CR8723 100m roll
189-500
Data cable 2 pair CR8723 100m roll
72
--- PAGE BREAK ---
Appendix (vii) Extending a Net2 system
The correct procedure for extending a Net2 system is as follows:
Chapter 9 Appendix
1.
Close the Net2 software application.
2.
Wire the additional ACUs .
3.
Open the Net2 software application and detect the new ACUs by
pressing the Detect button in Doors.
4.
Press Apply to commit the ACUs to the database.
5.
Configure the new ACUs in the usual way.
6.
As default no user will have access to the additional doors. Make the
required adjustments to access levels and individuals user records
(where access levels are not used).
7.
To confirm that the system is working as it should, perform the
following checks:
•
A user token given access privileges at the PC does open the doors
that it is supposed to.
•
Events are being reported back to the PC.
•
All locking hardware is functioning correctly, i.e. the doors open
when they should do.
•
Alarm events such as door forced open are reported back to the PC
from every door.
73
--- PAGE BREAK ---
Appendix (viii) Replacing a control unit
If a Net2 control unit is faulty then it may need replacing with a new unit.
The ‘Replace control unit wizard’ administers downloading the relevant
settings and user information to the new control unit.
Figure 9.4
Replace a control unit
wizard
Chapter 9 Appendix
1.
Close the Net2 software application.
2.
Physically remove the old control unit from the network and wire the
new unit in its place (for full wiring details refer to Wiring).
3.
Open the Net2 software application and detect the new ACU by
pressing the Detect button in hardware as shown in figure 9.3. Ensure
that the new ACU has been detected before proceeding.
4.
Start the replace control unit wizard by pressing Replace in hardware as
shown in figure 9.3.
5.
Press Next to continue.
6.
Select the control unit to be replaced from the list as shown in figure 9.4.
Press Next to continue.
7.
Select the new control unit from the list and press Next to continue.
8.
If the details displayed are correct then press Finish to complete the
replacement.
74
--- PAGE BREAK ---
Appendix (ix) Site registration form
You must register your software to receive
technical support
Registering couldn’t be simpler. Simply complete this form and fax it to us.
This form is available in pdf format on the CD-ROM (Net2 V1.03\Literature\Registration.pdf) should you need to print
out another copy.
Installation company
Site information
Contact
Company
Address
Contact
Site name
Address
Post code
Tel
Email
Post code
Tel
Email
Fax
Fax
Installation details
CD-KEY
Number of doors installed on site
Date commissioned
Fax number: +44 (0) 1273 483753
Chapter 9 Appendix
75
--- PAGE BREAK ---
Chapter 10 Specifications
Net2 software for 200 doors
Maximum number of users
Maximum number of doors
Net2 software for 50 doors
Maximum number of users
Maximum number of doors
Net2 software for 20 doors
Maximum number of users
Maximum number of doors
Reading technologies supported
10,000
200
10,000
50
10,000
20
All Paxton Access readers: PROXIMITY, CARDLOCK
magnetic stripe, TOUCHLOCK keypads
All users, all access points
All users
Up to 250
Up to 64
Yes
Yes
Yes
unlimited
4 levels
Individual password protection
Provides fast access to user records
Yes
Reported to software and output for local sounder at door
Reported to software and output for local sounder at door
Screen reports on recent events
Yes
Microsoft Access 97
Yes - including Word, Excel, Access, etc
Manual backup required
Yes
1 to 5,000 seconds
Yes - all equipment that can be switched by clean relays
Individual access rights by access point
Individual time zones
Access levels
Time zones
Read in and read out
Card plus PIN (Personal identification number)
PIN only entry
Number of system operators
System operator privileges
System operator log on to software
Desk top reader
Advance entry of Bank Holidays
Door held / wedged open alarm
Door forced alarm
Instant reports
Printed reports from entire access event history
Database format
Data available to other programs
Timed backup of event log
Fail open (fail safe) locks
Door open time
Operates gates, barriers, turnstiles, etc
Network Details
Communications with other control units
RS485 full duplex 115,200 BAUD
Maximum number of control units per data line
200
Full distributed intelligence
Yes
Off line memory in access control units
2,300 events
Access control unit user card capacity
10,000 Paxton Access proximity devices or magstripe cards
Access control unit user card capacity
10,000 bank / credit magstripe cards
Details of supported readers
Magnetic stripe readers
CARDLOCK
Reader life
>1,000,000 swipes
Proximity readers
PROXIMITY
Reader life
Unlimited token reads
Keypads
TOUCHLOCK membrane or TOUCHLOCK stainless steel
Keypad life (key presses)
>100,000 membrane or > 1,000,000 for stainless steel
Water resistance
All readers IPX7 (submersible) except membrane keypad IPX5
Finishes of CARDLOCK and TOUCHLOCK
Black, brass or satin chrome
Finish of PROXIMITY
Black
Finish of TOUCHLOCK stainless steel
Stainless steel and satin chrome
Minimum PC minimum specification: Pentium PIII/800 processor, 128 Mbytes RAM, UDMA hard disk with 1Gbyte free
space, 800 x 600, 256 colour monitor (SVGA), a free UART 16550 serial port, mouse, keyboard and a CD ROM drive 4 x or
better.
--- PAGE BREAK ---
Network communications
Network communications cable
Maximum length of communications bus
Access Control Unit
Number of doors per control unit
Memory in the event of complete power failure
Backup batteries ensure operation of
Connections in the access control unit for each of the doors
Readers
Keypads
Analogue / digital inputs
5 amp relay outputs (NC, and NO)
1 amp FET controlled output
Reader to access control unit distances
TOUCHLOCK keypad *
TOUCHLOCK keypad stainless steel *
CARDLOCK reader *
PROXIMITY reader*
Access control unit power requirement details
Required supply voltage
Maximum current for access control unit
Maximum current for Paxton Access magstripe readers
Maximum current for Paxton Access proximity readers
Maximum current for Paxton Access keypads
Maximum current for other keypads and readers
Maximum current for locks
Access control unit dimensions
Board size
Recommended minimum space for board in other
manufacturer’s enclosures
Board weight
NETWORK RS485 / 232 communications converter
Size
Communications protocols
Maximum serial cable distance to PC
Low voltage power supply
Desktop reader details
Type of reader
Paxton Access dual technology desktop reader
Size of Paxton Access dual technology desktop reader
Maximum distance to access control unit
Black plastic housing
Size
Features
PSU enclosure size
Details to be confirmed
CAT5 (Screened or unscreened) or Belden® 8723*
1,000m
1
All system settings and user details are retained for 7 days
Entire system except PC - control of access continues
1 or 2 (in, in/out)
1 or 2 (in, in/out)
4 (default uses: exit button, door contact, PSU monitor, tamper)
2 (default use: lock relay and door bell relay)
1 (sinks up to 1A at 12Vdc, default use: local door alarm)
30m
30m
100m
50m
9V to 15V dc
350mA at 12Vdc (allow extra for FET output)
65mA
70mA
45mA
See reader manufacturer’s literature
See lock manufacturer’s literature
102 x 116 x 30mm high
200 x 170mm high
190g
80 x 50 x 20mm
RS232 to PC, RS485 to access control units
7m
250mA 12V dc
The reader type used at the doors on site may be used or:
Reads magstripe cards and Paxton Access proximity devices
160 x 90 x 30 mm
As for other reader distances noted above
175 x 170 x 40mm
Tamper switch, cable tie loops, cable entry knock outs
* All reader and data cables should be segregated from mains power cables to avoid interference. IEE Regulations
and normal good practice should be observed. Belden cables or exact electrical equivalents must be used.
®Windows 95, 98, NT, 2000 and XP, Access, Excel and Word are Registered Trademarks of Microsoft Corporation Inc.
® Belden is a Registered Trademark of Cooper Industries Inc.
--- PAGE BREAK ---
Net2 Installer Guide
--- PAGE BREAK ---
Why work with us?
Easy to quote
Easy to install
Easy to work with
•
Build your system one door
at a time
•
Plug and play solutions that
connect directly to the network
•
Industry-leading
technical support
•
A range of products to suit any
site requirement
•
•
5-year guarantee and three
step returns policy
•
Scalable system – add doors
when the budget is available
Mix and match Net2 products
– they are all designed to work
together seamlessly
•
•
Clear instructions and colour
coded wiring labels
Free software upgrades and
no multiple licence fees
--- PAGE BREAK ---
The Paxton Installer App
Paxton in Your Pocket –
the Ultimate Installer Tool
The new Paxton Installer app gives you instant access to all the tools you need to install
Paxton products. The free app, available for iOS and Android, provides quick and easy access to
product specs and technical information, plus anything you could need on-site!
Superfast access to
product information
Get answers to
your FAQs
Be the first to hear
Paxton news
Find your
distributors
Dial direct to Paxton
Technical Support
--- PAGE BREAK ---
Contents
What is Net2 Access Control?................................. 5
How Does Net2 Work?........................................... 6
Net2 Software ....................................................... 7
Net2 Software Features.......................................... 8
Net2 Hardware.................................................... 10
Net2 PaxLock....................................................... 11
PaxLock Pro - Mortise & Latch............................... 12
Video Intercom.................................................... 14
Video Intercom Components............................... 15
Video Intercom System ....................................... 16
Readers and Keypads .......................................... 17
Net2 Integrations ................................................ 18
Net2 Case Studies ............................................... 19
Additional Information ........................................ 21
--- PAGE BREAK ---
What is Net2 Access Control?
Net2 is Paxton’s user friendly and flexible
networked access control and video intercom
system, which is managed from a central PC.
Net2 access control is easy to install and designed to make the
management of any building very simple. Net2 offers a range of
IP, battery powered, video intercom and wireless or wired door
controllers to suit any site requirement, making installers’ lives easier.
Wired
Access Control
Wireless
Access Control
Our networked access control system,
Net2, is administered using one or
more PCs and can be monitored and
managed from a central location.
Net2 PaxLock is a wireless networked
access control solution in a door handle.
It communicates wirelessly to the server
PC via a Net2Air bridge, reducing cabling
and installation time.
Video Intercom
Entry is our straightforward video
intercom system that works standalone
or when used alongside Net2 access
control, Entry can be used to allow
day-to-day access for users who have an
RFID token, PIN or code.
--- PAGE BREAK ---
6
How Does Net2 Work?
Networked Access Control
Our networked access control system, Net2, is
administered using one or more PCs and can be
monitored and managed from a central location.
Our door controllers come as wired, wireless or
battery powered.
Net2 is designed with simplicity in mind and is easily scalable.
Paxton’s one door controller philosophy means you only quote
for doors that require access. You can build your Net2 system
one door at a time using wired and wireless controllers and
video intercom for versatile security and building management.
Benefits of the Net2 system:
• Modular approach for simplicity and scalability
• Simple intuitive software
• Range of features that move beyond basic
access control
• A complete solution that encompasses wireless and
video intercom
Network
Example of a Net2 system:
Net2Air
Bridge
Net2 software
Net2 PaxLock
Server PC running access control software
Wireless IP Access Control Solution
Net2 plus
Entry
Controller
Entry
Touch panel
P50
reader
Exit
button
Entry
Premium Monitor
Video Intercom System
Wired IP Access Control Solution
www.paxton-access.com/us
877.438.7298
supportUS@paxton-access.com
--- PAGE BREAK ---
Net2 Software
Software Overview
There are two versions of the software: Net2 Lite,
which is ideal for most sites and is free of charge,
and Net2 Pro, which offers extra features for more
flexible and advanced access control as well as a
number of new features to help keep sites COVIDsecure. Developed to be straightforward and
intuitive, the Net2 software is easy to learn.
Feature
Net2 Lite
Net2 Pro
Multiple clients
•
•
Free upgrades
•
•
CCTV integration
•
•
Site graphics
•
•
Triggers and actions
•
•
Intruder alarm integration*
•
•
Entry compatible
•
•
Easy access to your Net2 system wherever you are –
any location, any device. Flexible site management
via a browser with Net2Online and from the Paxton
Connect app.
Biometric integration
•
•
Features include:
Timesheet & Timeline*
•
•
Card designer
•
•
Open door functionality
Landlord Tenant
-
•
Viewing reports and events
Roll call and muster reporting*
-
•
Fire alarm integration*
-
•
Anti-passback*
-
•
Security lockdown*
-
•
Multi-zone intruder alarm integration*
-
•
Custom days*
-
•
Areas
-
•
Customizable welcome page
-
•
Paxton Connect app**
-
•
Net2Online***
-
•
Checkpoint Control
-
•
Occupancy Management
-
•
Net2Online and Paxton Connect
Site management made easy
User admin
Managing roll call reports
Free with Net2 Pro
Download now:
Find out more: paxton.info/4012
* Not available with wireless products
** Paxton Connect app only works with Net2 Pro v6.00 or above
*** Net2Online only works with Net2 Pro v6.01 or above
www.paxton-access.com/us
877.438.7298
supportUS@paxton-access.com
7
--- PAGE BREAK ---
8
Net2 Software Features
Software Features
Tailor access privileges to groups or individuals
quickly and easily using our intuitive, user-friendly
software. Event reports can be generated in a
few clicks and the advanced features such as
site graphics, IP camera integration and triggers
and actions further extend the capabilities of the
system.
Live events
View events in real time.
Full event logging - review historical events.
Reporting
Pre-defined reports allow you to review the most
relevant data quickly
Build custom reports based on individuals,
departments or doors
COMPATIBILITY
Net2 software is compatible with Windows 8, Windows 7,
Windows 10 or Vista operating systems and is designed to
feel familiar to any Windows user.
Free upgrades
Software upgrades are always free of charge,
allowing system users to benefit from new
features as they become available
Unlimited client workstations
Net2 software does not restrict the number of
operators who can have access and it can be
installed free of charge on multiple PCs
Multiple operator levels
An unlimited number of people can administer
the system with different levels of security applied
Open door function
Utilize the software to open individual doors or
groups of doors from a client workstation
Site graphics
Import 2D images of your site to give a graphical
view of door open or alarm status for operators or
security personnel
Triggers & actions
Administrators can easily create rules based on
system events. These include sending emails and
SMS, controlling doors and relays in response to
access events or alarms
User image verification
This enables the system administrator to visually
confirm the identity of the user
Custom days
Custom days offers organizations flexibility
allowing users to create a time period in the Net2
software for special events and occasions. This
is useful when organizing events such as school
open days, or extended store opening hours
Temporary access rights
Temporary access permissions can be used to
automatically upgrade or downgrade a user’s
access permissions for a set period of time
Turnstile mode
Control bi-directional turnstiles with a single
door controller saving wiring time and hardware
expense
www.paxton-access.com/us
877.438.7298
supportUS@paxton-access.com
--- PAGE BREAK ---
Net2 Software Features
Timesheet & timeline
PRO
By allocating specific proximity readers for
clocking in and out you can use Net2 to log the
working hours of employees. You can also note
periods of time out of the office for reasons such
as vacation, appointments and unpaid leave, etc.
Reports can also be exported for use with HR
applications
Areas and area groups make it easier to set up
access levels on larger sites by grouping multiple
doors into a single access controlled area. It also
allows the use of advanced features such as antipassback
PRO
Personalize access control tokens with employee
pictures, details and company information
PRO
Landlord Tenant /
Advanced operator permissions
PRO
Who is in?
Displays the last known location of a user based
on the last reader they presented a token to
Operators using Net2 software can be managed in
various ways to limit access and enhance security.
With Landlord Tenant / Advanced operator
permissions it is possible to restrict operators to
only administer users within certain departments
and apply specific access level permissions to
those users
PRO
Security lockdown
Security lockdown is ideal for buildings or
sensitive sites that need to secure the premises
in the event of an emergency, allowing only
specific security personnel free movement during
lockdown
Roll call & muster reporting
Roll call allows the system administrator to obtain
a report listing all users currently within a specified
area. This is primarily used in the event of an emergency, such as a fire alarm, when it can be used to
check that everyone is out of the building
PRO
Anti-passback
The main purpose of an anti-passback system is
to prevent a user from passing their token back
to a second person to gain entry into the same
controlled area; for example, a car park
Card designer
PRO
Areas
PRO
Customizable welcome page
Installers can customize the welcome screen of
every Net2 system they install or maintain with
their logo and contact details. This ensures that
the customer knows who to contact if they need
support
Occupancy Management
Control and monitor social distancing with
Occupancy Management. Quickly and easily
manage the flow of people around your
building to control the maximum number
of people in any given area. Real-time visual
reports make it easy to see when an area is
nearing, or reaches, capacity.
PRO
Checkpoint Control
Create checkpoints within a building
where staff or visitors must be validated
before they can access other areas, helping
to follow health and safety guidelines and
protect user well-being. Manually validate
staff and visitors with in-person checkpoints
or use a dedicated reader to validate
people automatically.
SOFTWARE DEMONSTRATIONS
Watch our tutorial videos and learn how you can get the very best from the Net2 software
and offer your customers more from their access control system.
Watch our videos here:
http://paxton.info/3234
PRO
www.paxton-access.com/us
- features only available in Net2 Pro software
877.438.7298
supportUS@paxton-access.com
9
--- PAGE BREAK ---
10
Net2 Hardware
Door Controllers
All Net2 door controllers can be used alongside
each other, making it easy for installers to find the
best solution for each individual site.
Net2 plus
door controller
Net2 plus is Paxton’s most powerful door controller, which uses
TCP/IP technology to allow direct connection to the IP network,
saving time with minimal wiring needed.
• Use existing LAN or RS485 infrastructure on a site
• Easy installation with minimal wiring
• Future proof and easily scalable
• Create more site opportunities
Net2 plus
door controller
with PoE
Power over Ethernet (PoE) is a technology that allows both
power and data to be streamed along the same Ethernet cable.
Net2 plus with PoE as a power source makes installations quick
and easy.
• Enjoy all the benefits of Net2 plus, with a single cable for
power and data
• Choose to use mains or PoE
• Installation is more efficient and convenient
• Save time and money on extra cabling
Net2 plus door
controller with
trigger disconnect
The trigger disconnect power supply is a power supply/charger
that has two protected outputs that can be set for 12VDC or 24
VDC. It is intended for use in applications that require UL listed
interface with fire alarm control panels.
• Fire alarm control panel or access control trigger input
• Relay output for activating other devices
• 2 power limited, protected outputs (12VDC or 24VDC)
· Fail safe/fail secure switched lock output
· Auxiliary unswitched power output
www.paxton-access.com/us
877.438.7298
supportUS@paxton-access.com
--- PAGE BREAK ---
Net2 PaxLock
Net2 PaxLock
Net2 PaxLock will save you time and money on
site. It can be installed quickly and comes pre-fit
with a C keyway core. The battery powered unit
comprises a networked access control system
in a door handle, combining secure wireless
technology with a stylish proximity reader.
Features of Net2 PaxLock
Net2 PaxLock communicates with the Net2
software at a central point by a secure, low
power radio link, and events are reported back
to the server in real-time. It is designed for use
with Net2Air Bridges to give the advantages of a
wireless networked access control system. Each
Net2Air Bridge can detect Net2 PaxLock units
within an average wireless radius range of up to
50ft (15m).
• No separate power supply needed
• No cabling to the door
• Minimal installation time
• Reduced labor costs
• Ideal for retrofit installation
1 HID™ activation license required
The Genuine HID Technology
logo is a trademark of HID Global
Corporation/ASSA ABLOY AB.
Used with permission.
• UL-10C rated
• Contains Genuine HID Technology™
No separate
power supply needed
No wiring
necessary
Token
options
Available with key
override
www.paxton-access.com/us
877.438.7298
AA battery
operated
supportUS@paxton-access.com
11
--- PAGE BREAK ---
12
PaxLock Pro - Latch
Net2Air Bridge
LAN/WAN
Net2 software
PaxLock Pro
- Latch
NEW PRODUCT
PaxLock Pro - Latch
PaxLock Pro – Latch is a wireless door handle
with a universal design that provides a quick,
simple and convenient way to secure an internal
door. The door handle’s smart and compact
appearance means it can be used in more
applications than ever before. PaxLock Pro Latch includes a tubular latch that can replace
an existing cylindrical lockset or be installed as
part of a new door installation.
Standalone or
networked
• Standalone/Networked wireless access control
• Simple upgrade path from standalone to networked
• Dual-frequency proximity reader - Paxton, MIFARE®, EM,
HID®Prox
• Communicates using Net2Air technology
• UL294 Certified
• FCC part 15 & ISED certified
• Compatible with standard cylindrical doors using
tubular latch
UL294
FCC
Rated for
reliability
Part 15
certified
Yale lock cases
available
www.paxton-access.com/us
877.438.7298
5 Year
warranty
supportUS@paxton-access.com
--- PAGE BREAK ---
PaxLock Pro - Mortise
Net2Air Bridge
LAN/WAN
Net2 software
PaxLock Pro
- Mortise
NEW PRODUCT
PaxLock Pro - Mortise
Available colors:
White
Black
Two handle options available - Galaxy & Eclipse
PaxLock Pro - Latch - for internal use
PaxLock Pro - Mortise - for external facing doors
Net2Air Bridge
The Net2Air Bridge communicates
between the Net2 PC and wireless
control units. It has a low profile
which can be wall or ceiling
mounted for a quick and simple
installation.
*
No separate
power supply needed
*PaxLock Pro - Mortise only
No wiring
necessary
Token
options
Available with key
override
www.paxton-access.com/us
877.438.7298
AA battery
operated
supportUS@paxton-access.com
13
--- PAGE BREAK ---
14
Video Intercom
Entry
Entry is our straightforward video intercom system
that works standalone or when used alongside
Net2 access control, Entry can be used to allow
day-to-day access for users who have a token, PIN
or code. Entry allows a person inside a building
to identify a visitor via a video or audio monitor
before they decide whether to grant or deny entry
via the external door.
NEW IN ENTRY
The versatile grouping feature enables smart management
of multi-tenant buildings and sites with fenced perimeters.
The intuitive panel allows you to set up the display to show
occupants by name, for straightforward building management.
The system is a highly scalable solution, allowing expansion of
up to 100 panels and 1000 monitors.
!
Quick and Easy installation
• Just 3 components that auto detect on setup – monitor,
panel and control unit
• Scalable system – expands using a standard PoE
extension switch
• No need for specialist wiring diagrams
• 3 monitor options - premium, standard and audio
options available
• Multiple panel options – flush mount, surface mount and
surface mount with rain hood
• Secondary camera integration for extra security
• SIP compatibility - the door can be answered from
smartphone, tablet or PC
Entry
Standard Monitor
The latest addition to our video intercom range.
Introducing the next generation standard monitor,
a versatile door entry monitor that offers a feature
rich and cost-effective solution for a range of
applications. Fully compatible with Net2, as well as
part of a standalone video intercom solution, the
new Entry Standard monitor is the ideal choice for
any building.
• Excellent audio quality, full-duplex voice communication
and easy read, high contrast screen
• Personalized experience with 14 theme designs. Premium
user interface with call and event log
• Action buttons, call snapshot and compatibility with
concierge management*
*When used with the Entry Premium monitor.
The standard monitor cannot function as the concierge monitor.
• Available with or without a handset. Universal wall or
desk mounting
• Quick and easy installation, providing a true plug
and play solution
www.paxton-access.com/us
877.438.7298
supportUS@paxton-access.com
--- PAGE BREAK ---
Video Intercom Components
Entry panels
Entry monitors
Entry
Standard panel
Entry Standard monitor
The anthracite grey standard panel suits a
range of environments with its simple and
IK08 rated robust design.
The next generation of our standard
monitor. Smart, sleek design with
an enhanced user experience. More
features, new look, better price.
Entry
Vandal Resistant panel
Entry
Audio monitor
IK10 impact rated - made from marine grade
stainless steel to meet the most demanding
environments.
Cost-effective monitor fully
supporting all system functionality,
where video is not required. Action buttons configurable for
a range of requirements, like activating an intruder alarm or
switching on external lights.
Entry Touch panel
Entry
Premium monitor
Capacitive 7-inch color touch screen with
customizable options and two way camera
when used with the Entry Premium monitor.
Indicates readers that have functionality to read
HID™ 125kHz Proximity when enabled using
Genuine HID Technology™ 125kHz. Proximity
activation license cards sold separately.
Free concierge management and
several personalization options
available with built in themes.
Entry controller
Conduit between the monitor and
the panel in the system.
www.paxton-access.com/us
877.438.7298
supportUS@paxton-access.com
15
--- PAGE BREAK ---
16
Video Intercom System
TCP/IP
IP camera integration
LAN
Up to 1000
monitors
Up to 100 panels
Server
Entry
controller
Net2
software
Entry
Audio monitor
Entry
Touch panel
A Simple One Door Solution
Easy to extend via an IP network
• Additional components auto detect when connected, with
IPv6 technology
• SIP compatibility – the door can be answered from
smartphone, tablet or PC*
Smart, simple user experience
• Intelligent panel design displays occupants by name or if
using the touch panel add an image or logo for quick visual
recognition in the dynamic address book
• Multiple theme options to personalize the touch panel,
standard monitor and premium monitor
• Intuitive user interface for secondary ONVIF compliant
camera integration
• Simple visitor verification, with or without video
Entry
Premium
monitor
SIP phone
!
Advanced Features of the
Entry System
Entry has a range of features, advanced functionality and
intuitive user interface to make it suitable for a wide range
of sites allowing you to offer your customers the ultimate
security solution.
Versatile building management
• Grouping feature enables smarter management of multitenant buildings and sites with fenced perimeters
• Complete product portfolio with premium, standard, audio
and vandal resistant options available
• Pan/tilt camera functionality to capture an angled view, for a
diverse range of locations
Suitable for a wide range of sites
• Free concierge management, including broadcast
messaging available with the premium monitor at no
extra cost
• Multi-format reader – reads Paxton and MIFARE® token
technology
• Hi-contrast themes available with the premium and standard
monitors and touch panel
• The audio monitor fully supports all system functionality,
where video is not required
INTRODUCTION TO ENTRY
Watch it here:
http://paxton.info/3143
• The standard panel features a high contrast backlit keypad
• Two-way video available between the premium monitor and
touch panel
• Line-out for T-Loop antenna built into the touch panel and
premium and standard monitors for users with hearing aids
* 3rd party app required
www.paxton-access.com/us
877.438.7298
supportUS@paxton-access.com
--- PAGE BREAK ---
Readers and Keypads
Readers and Keypads
Due to the wide range of site requirements, we
offer a variety of readers and keypads suitable for
use with Net2. This includes readers and keypads
with vandal resistant, energy saving and long
range capabilities.
See the full range on our website:
We have a range of keypads and readers to suit many
sites and requirements.
Use this link to see more:
paxton.info/3235
P series
Long range reader
The P series range of readers is Paxton’s
most popular and comprises four readers
ranging in size from the P38 to the P200.
A P50 fits neatly onto a door frame while
the size of the P200 creates a longer
token read range. All P series readers
are supplied with two fascias, one black
and one white. We supply free fascia
replacements to keep your sites looking
smart.
The Long range reader is designed
for hands free access, its read range
of 5m means that the token can be
detected from within a vehicle, for
car parks, barriers and wheel chair
user access.
Energy saving reader
Marine reader
The Energy saving reader is used to
ensure that electrical equipment is only
switched on when an authorized user
card is inserted and retained, ideal for
energy saving and safety.
The Marine reader is made of
marine grade stainless steel and is
built to withstand the elements as
well as look stylish.
Paxton reader range
with Genuine HID Technology™
The Paxton reader range with Genuine HID Technology™ is a smart collection
of readers. The multi-format readers can be configured to read standard
125kHz HID™ cards; ideal for large sites wanting to use existing cards for their
Net2 access control systems. HID™ Wiegand output is optional with a separate
purchase of a Wiegand activation card. For a list of our readers with Genuine HID
Technology™, see our website.
See the full range on our website:
http://paxton.info/3233
www.paxton-access.com/us
877.438.7298
supportUS@paxton-access.com
17
--- PAGE BREAK ---
18
Net2 Integrations
Integrations
Intruder alarm
• Save time by integrating Net2 with your
intruder alarm and reduce false alarms.
Net2 software is designed to easily integrate
with other security systems, so you can offer your
customers a complete solution. By integrating
with other security systems your customers can
enjoy more streamlined security for their building
• Control your intruder and access systems
as one, across different areas of the
building.
Fire alarm
BESPOKE INTEGRATIONS
i
• Integrate Net2 with your fire alarm and
program your system to automatically
open fire doors in the event of an
emergency to improve safety.
The Paxton Software Development Kit (SDK) is
free to download for C# developers with no NDA
to sign, and is supported via a dedicated software
development forum.
CCTV
• Streamline your Net2 system with CCTV
for a quick, efficient way to view footage
linked to specific access events or doors.
• Review CCTV footage from within your
Net2 system.
Roll call and muster
• Set your system to generate an automatic
roll call report when the fire alarm goes off.
This helps to identify exactly who is safe
once the building has been evacuated.
Biometrics
• Net2 integrates with leading biometric
readers, allowing enrolment of biometric
data within Net2.
• Open up new market opportunities from
high security sites by offering biometric
integration with Net2 access control.
For more information visit http://paxton.info/3202
www.paxton-access.com/us
877.438.7298
supportUS@paxton-access.com
--- PAGE BREAK ---
Case Studies
Net2 Case Studies
The Net2 system can be adapted to meet a
range of diverse requirements for you and
your customers. We have a range of case study
examples covering many different sectors.
See our latest case studies here:
http://paxton.info/3204
CORMETECH
Who is using Net2?
Here are just a few organizations who are using Net2 on their
sites:
Michelin
Manchester United
Porsche
DHL
Foyles
Graze
Ingram Micro
Charlotte, NC, & Kings Mountain, NC, USA
CORMETECH develop environmental catalysts and technologies
that reduce emissions from industrial processes. They required
an updated access control solution to manage their multi-site
facility from a single user database, to provide a more substantial
infrastructure on one centrally managed system.
Type of site:
Manufacturing/Commercial
Number of doors:
• 2 sites
• 58 doors
Solution required:
• Improved and upgraded access control system
and more…
• Centrally managed
• Scalable, multi-site solution
Paxton products used:
• Net2 Pro Software
• Net2 Plus Controllers
• Net2 IO Boards
• KP75 Proximity Keypads
• P38 Proximity Readers with Genuine HID Technology™
• Entry VR Panels
Do you have a case study?
A case study can be a fantastic tool to help your
customers see the benefit of having access control
or video intercom on their site and help you to
secure more business in the future.
If you’re interested in working with us on
a case study, you can get in touch with
the Marketing Communications team at
marketing@paxton-access.com
• Entry Monitors
Integration:
-
Result:
• Flexible, scalable system with significant growth opportunity
• Simple access management
• Tailored access rights for users and areas
www.paxton-access.com/us
877.438.7298
supportUS@paxton-access.com
19
--- PAGE BREAK ---
20
Case Studies
Park Terrace Condo Association
Wesleyan School
Downtown San Diego, CA, USA
Park Terrace Condo in downtown San Diego is conveniently
located across from Petco Park, home of the San Diego Padres.
The beautiful condo features two towers, 14 stories and houses
223 units. Park Terrace now uses Paxton’s access control to
provide a secure community for their tenants.
Atlanta, GA, USA
Founded in 1963, Wesleyan School is located on 85 acres of land
in Peachtree Corners, Georgia, just north of Atlanta. The school
is comprised of nine main buildings including a chapel, two
libraries, and two dining halls. There are 1,129 children and 200
faculty staff on site.
Type of site:
Type of site:
Residential
Education/School
Number of doors:
Number of doors:
• 223 condos
• 52 doors
• 27 doors
• 2 gates
• 2 buildings
• 9 buildings
Solution required:
Solution required:
• Manage and control access to the building
• Flexibility to adjust schedules
• Increase security for tenants
• Secure the perimeter and school buildings
• Update and improve existing access control system
Paxton products used:
Paxton products used:
• Net2 Plus Controllers
• Entry VR Panels
• Net2 Software
• Net2 Pro Software
• Entry Monitors
Integration:
Integration:
-
Avigilon CCTV
Result:
Result:
• Ease of running reports
• Instant lockdown
• Ability to identify incidents simply in Net2 software
• Timezones feature to plan access for after school clubs and
sports
• Granting and denying access
• Complete customer satisfaction
www.paxton-access.com/us
877.438.7298
supportUS@paxton-access.com
--- PAGE BREAK ---
Additional Information
Dealer training
We offer practical hands-on training for our Net2 system. The
BICSI CEC registered program is designed to provide you with
the essential knowledge needed to install Paxton products.
• Ensure accurate installation
• Reduce time on site
• Courses are free of charge
• Materials and equipment provided
For more information and to book a session, go to
http://paxton.info/3205.
Industry leading technical support
Call Paxton and you will be put straight through to our expert
support team. Our friendly team is available from 2am-8pm EST
Monday-Friday.
Call:
877.438.7298
Email:
supportUS@paxton-access.com
Skype: USAPaxton.support
Sales literature
Case studies
We offer an extensive range of brochures and sales guides to
support you every step of the way, from sales to specification.
All documentation is available to download from our website at
http://paxton.info/3206.
Find out how the Net2 system can be adapted to meet a range
of diverse requirements by reading our latest case studies. We
have a range of examples covering education, healthcare, retail,
leisure, commercial and public buildings.
See our latest case studies here:
http://paxton.info/3207
Net2 integrations
Newsletter sign up
We want to ensure that we are
providing the most sophisticated
solutions available. We do this by
working with quality manufacturers to provide the best solutions
and make them available to you. You can see a list of our Net2
integration partners at http://paxton.info/3203.
The Paxton Installer is your monthly newsletter, containing the
latest news, product information and updates from us. Every
month your copy of the Paxton Installer will arrive in your inbox full of useful information that will make your job easier and help
you to win more business.
Sign up now:
http://paxton.info/3208
www.paxton-access.com/us
877.438.7298
supportUS@paxton-access.com
21
--- PAGE BREAK ---
22
Additional Information
Paxton 5-Year Warranty
and Hassle-Free Returns Policy
We offer a five-year warranty on all our products.
If a problem arises, all you have to do is return your Paxton
product to your local distributor.
We want to make life as easy as possible for installers of Paxton
products. Our five-year warranty and hassle-free returns policy
helps us to do this.
Notes
www.paxton-access.com/us
877.438.7298
supportUS@paxton-access.com
--- PAGE BREAK ---
23
Notes
www.paxton-access.com/us
877.438.7298
supportUS@paxton-access.com
--- PAGE BREAK ---
Easy to quote
Easy to install
Easy to work with
Build your Net2 access control system
one door at a time.
Plug and play solutions that connect
directly to the network.
Industry leading
technical support.
A range of Net2 products to suit any
site requirement.
Mix and match Net2 products - they
are all designed to work together
seamlessly.
5-year warranty
and simple returns policy.
Scalable system - add doors when
the budget is available.
Clear instructions and color coded
wiring labels.
Net2 Installer Guide
Paxton Access Inc.
138 Commerce Center
Greenville, SC, 29615
USA
877.438.7298
supportUS@paxton-access.com
www.paxton-access.com/us
MIFARE® is a registered trademark of NXP B.V. and is used under license.
The Genuine HID Technology logo is a trademark of HID Global Corporation/ASSA ABLOY AB. Used with permission.
All information and specifications correct at the point of publication, but may be subject to change without notice.
All pictures shown are for illustration purpose only. Actual products may vary.
ibp-ig3-US
Nov 2022
2022 v3
Free software upgrades and no
multiple license fees.
--- PAGE BREAK ---
Power
DC Only
Arm
0V
S ns
COM
N.O.
Set
12-24V
0V
Intruder Alarm
Outputs
Exit Button
RS485 Network
CAT5 Cable Coding
Green
Wht/Grn
Orange
Rx
Wht/Orng
Screen or spare
cores from data
cable
Tx
Inputs
OFF
ON
10
100
Contact
End of Line Termination
Server Connected
Server Link
10/100 Ethernet
PSU/Tamper
Reader 2
Caution: For 12V DC readers only
Ins-30080 Net2 plus control unit
.
Relay 2
Reader 1
Relay 1
Net2 plus
Page 1
--- PAGE BREAK ---
Technical Support
01273 811011
Technical help is available:
support@paxton.co.uk
Monday - Friday from 07:00 - 19:00 (GMT)
Saturday from 09:00 - 13:00 (GMT)
Documentation on all Paxton products can be found on our website - http://www.paxton.co.uk/
The Net2 plus can be connected to the PC via an RS485 data line or a TCP/IP connection.
This unit requires the controlling PC to be running Net2 v4.14 or later software.
Intruder alarm
integration
Amber LED
Data/D0
R
Reeaaddeerr 22
Green LED
Relay 1
End of Line Termination
OFF
ON
Orraannggee
O
Rx
Rx
G
Grreeeenn
Tx
Tx
W
Whhtt//O
Orrnngg
10
10
Server
Server Link
Link
100
100
RS485 Network
CAT5 Cable
Cable Coding
CAT5
Coding
W
Whhtt//G
Grrnn
Server
Server Connected
Connected
10/100
10/100 Ethernet
Ethernet
Green LED
Exit
0V
Contact
0V
0V
Tamper
PSU
Switchable 120
ohm resistors
Page 2
Door contact switch
(held closed by door)
Tamper switch
(optional)
TCP/IP patch lead
This is a single door control unit which
greatly simplifies installation and is
ultimately highly cost effective.
Exit button
(push to make)
12V
S
Sccrreeeenn oorr ssppaarree
ccoorreess ffrroom
m ddaattaa
ccaabbllee
0V
N.O.
COM
Clock/D1
Media Detect
For a fail open lock (Maglock),
wire 0V to the "N.C." terminal
instead of "N.O."
N.C.
Bu
uttttoon
n
EExxiitt B
Red LED
N.O..
Alarm
IInnppuuttss
12V
123456
LABEL
HERE
00-01-02-03-04-05
Coonnttaacctt
C
0V
0V
0V
COM
U//TTaam
mppeerr
PPSSU
Media Detect
2345612
Cau
uttiio
orr 1
12
2V
VD
DC
C rreeaaddeerrss oonnllyy
on
n:: FFo
Clock/D1
Outputs
http://paxton.info/107
http://paxton.info/107
12V
12-24V
N.C.
Re
ellay 2
R
Net2 plus
Green LED
Reader 1
Amber LED
Data/D0
Fail closed
release
00VV
AArrm
m
Set
Intruder
Intruder
AlarmAlarm
Red LED
Reader/keypad
SSennsse
Set
CCOOM
M
12V
NN..OO..
Expansion
Power Supply
Power
Power
DC Only
Wiring
From
previous ACU
To next ACU
--- PAGE BREAK ---
LED indications
12/24V
Relay 1
Relay 2
Alarm
Exit
Contact
Tamper
PSU
(Green)
(Orange)
(Orange)
(Red)
(Orange)
(Orange)
(Orange)
(Orange)
- Power LED.
- The relay is energised - (N.O./COM contacts are closed).
- The relay is energised - (N.O./COM contacts are closed).
- 12V Alarm output is active.
- The exit button contacts are closed.
- The door contacts are closed.
- The tamper contacts are closed.
- The PSU contacts are closed.
OK
(Green flash)
Termination
(Red)
Rx
(Red)
Tx
(Green)
Server Connected
(Green)
Server Link
- The internal software is running.
- The on-board resistors are in place across the RS485 data pairs.
- The ACU is receiving data (TCP/IP or RS485) - See also FAQ section.
- The ACU is responding to data - (TCP/IP or RS485).
- The TCP/IP interface is communicating with the PC Net2 server.
- Green = 100 Mbit/s : Orange = 10 Mbit/s (TCP/IP speed).
Intruder Alarm
- Signal present when lit. (see Intruder Alarm section)
(Orange)
TCP/IP and RS485 LED indication
The Net2 plus performs two functions. It is an access control unit and also a TCP/IP RS485 converter. Information can
pass across the PCB between the TCP/IP and RS485 data port but is not relevant to this ACU.
- Server Connected LED (Steady Green)
This LED shows that the TCP/IP interface is active and receiving data from the Net2 PC server. This includes all data for
other ACU's that may be linked via the RS485 data port.
- Rx and Tx LED's
These LED's show the activity for this ACU only. This is same indication as seen on a Net2 classic ACU.
It is not dependent on the source (TCP/IP or RS485). The Rx LED will flash for all data being received and the Tx LED
will only flash when this unit responds to its own address.
Control unit installation
Wire the components to the unit as shown on the first page. Power up and wait for the OK heartbeat.
Each time the unit is powered on, it will run an internal health check.
[... content truncated for display — full manual available from manufacturer ...]
| Account | Default Username | Default Password | Notes |
|---|---|---|---|
| Software Admin | admin | Set at first launch | No factory default — set during initial software installation |
| Terminal / Port | Function | Specification |
|---|---|---|
| LAN (RJ45) | Network connection | Ethernet, 100 Mbps switch required |
| Reader Port ×2 | RS-485 reader connection | 12V DC, 1A max (Paxton readers only) |
| Lock Output | Powered lock | 12V DC / 1A or 24V DC / 500mA |
| Door Contact | Door open/closed monitoring | Voltage-free input |
| Digital Input | General purpose input | Voltage-free |
| Exit Button | Request to exit | Push-to-make |
| Relay 1 / Relay 2 | Auxiliary relay outputs | 30V DC / 2A |
| RS-485 Connector | Paxton peripheral bus | 24V DC, 750mA max (Paxton connectors only) |
| Battery Connector | Backup battery | 12V DC, 7 Ah (optional) |
| Tamper Switch | Enclosure tamper | Monitored input |
| Fault / Display | Description | Likely Cause | Action |
|---|---|---|---|
| Controller Offline | Controller not communicating with server | Network fault, IP conflict, switch failure | Check Ethernet connection and switch port. Verify IP address. Restart controller. |
| Door Forced | Door opened without valid credential | Door held open, forced entry | Check door contact wiring. Investigate door. Review event log. |
| Door Held Open | Door open beyond configured time | Door not closing, obstruction | Check door closer. Adjust held-open time in software. |
| Reader Fault | Reader not communicating | RS-485 wiring fault, power fault | Check RS-485 wiring and power. Verify reader is Paxton10 compatible. |
| Lock Fault | Lock output fault | Lock wiring, power fault, lock failure | Check lock wiring and power. Test lock with 12V DC directly. |
| Tamper | Enclosure tamper triggered | Enclosure opened or tamper switch fault | Check enclosure is fully closed. Check tamper switch wiring. |
| Access Denied | Valid credential but access denied | Access level, time profile, anti-passback | Check user access level and time profile in software. Check anti-passback status. |
| Low Battery | Backup battery low | Battery ageing, battery not connected | Replace 12V 7Ah backup battery. Check battery connector. |
| Terminal | Function | Notes |
|---|---|---|
| LAN (RJ45) | Ethernet network | 100 Mbps switch required; PoE+ from switch or injector |
| Reader Port 1 (RS-485) | Entry reader | 12V DC, 1A max; Paxton readers only |
| Reader Port 2 (RS-485) | Exit reader | 12V DC, 1A max; Paxton readers only |
| Lock + | Powered lock positive | 12V DC / 1A or 24V DC / 500mA |
| Lock − | Powered lock negative | Common 0V |
| Door Contact C / NO / NC | Door open/closed monitor | Voltage-free; use NC for fail-safe monitoring |
| Digital Input | General purpose voltage-free input | Voltage-free |
| Exit Button | Request to exit | Push-to-make momentary switch |
| Relay 1 C / NO / NC | Auxiliary relay 1 | 30V DC / 2A; use for secondary lock or alarm |
| Relay 2 C / NO / NC | Auxiliary relay 2 | 30V DC / 2A |
| RS-485 Connector | Paxton peripheral bus | 24V DC, 750mA max; Paxton connectors only |
| Battery +/− | Backup battery | 12V DC, 7 Ah; connect via battery connector port |
| Power 12–24V DC | DC input (non-PoE models) | 12–24V DC; suppression at 28V |
| Parameter | Value |
|---|---|
| PoE Standard | IEEE 802.3at Type 2 (PoE+) |
| Input Voltage | 36–57V DC |
| Input Power | 25.5W max |
| Output Voltage | 12.8V DC |
| Output Current | 1.8A |
PAXTON10 — INTEGRATED ACCESS CONTROL & VIDEO MANAGEMENT Source: Paxton10 Installer Guide (2019) & Door Controller Datasheet TDS-0021 Manufacturer: Paxton Access Ltd, Brighton, UK SYSTEM OVERVIEW Paxton10 is a next-generation integrated access control and video management platform. A single Paxton10 server supports up to 1,000 doors and 1,000 cameras across up to 100 sites. The system uses single-door controller architecture with distributed intelligence. Each controller stores its own programming locally — access decisions continue if server connection is lost. The system is fully compatible with Paxton Entry door entry and PaxLock wireless door handles. DOOR CONTROLLER SPECIFICATIONS (TDS-0021) ELECTRICAL: Power consumption (battery charging): Idle 97mA / 5.08W; Max 108mA / 5.6W Power consumption (battery full): Idle 48mA / 2.53W; Max 105mA / 5.5W Backup battery: 12V DC, 7 Ah (optional) Lock output: 12V DC / 1A or 24V DC / 500mA Relay rating: 30V DC / 2A (×2 relays) RS-485 connector output: 24V DC, 750mA max (Paxton connectors only) RS-485 reader output: 12V DC, 1A max (Paxton readers only) Controller input voltage: 12–24V DC (suppression at 28V) PoE Power Supply: INPUT 36–57V DC, 25.5W (IEEE 802.3at Type 2); OUTPUT 12.8V DC, 1.8A 2A Power Supply: INPUT 100–240V AC, 50/60Hz, 1.2A; OUTPUT 13.8V DC, 2A COMMUNICATION: Data connection: IP (Ethernet RJ45) Network switch requirement: 100 Mbps minimum HARDWARE: Door contact input: Yes (voltage-free) Voltage-free digital input: 1 Exit button input: Push-to-make Tamper input: Yes Relays: 2 Maximum readers/keypads per door: 2 Warranty: 5 years ENVIRONMENT: Operating temperature: 0°C to +45°C IP Rating: N/A (indoor installation) Mounting: Wall CREDENTIALS SUPPORTED: Bluetooth Smart (Paxton Key app — free) MIFARE Classic / MIFARE DESFire HID Proximity (via multi-format readers) 125 kHz proximity (via Reader Converter accessory) PIN keypad Apple Watch (via Paxton Key app) PaxLock Pro wireless door handles Entry door entry panels SYSTEM CAPACITY: Doors: Up to 1,000 per server Cameras: Up to 1,000 per server Sites: Up to 100 per server (multi-site management) Architecture: Single-door controller (one controller per door) SALES CODES: 010-403 Paxton10 Door Controller, PCB only 010-052 Paxton10 Door Controller, PoE 010-751 Paxton10 Door Controller, 12V 2A PSU 010-315 Paxton10 Door Controller, with plastic housing DIMENSIONS (PCB with enclosure): 236mm × 320mm × 80mm (W × H × D) PCB only: 143.16mm × 196mm × 25.23mm
| Document | Source | Link |
|---|---|---|
| Paxton10 Installer Guide | Paxton Access Ltd | Download PDF |
| Door Controller Datasheet TDS-0021 | Paxton Access Ltd | Download PDF |
| Paxton10 System Page | paxton-access.com | View Online |
| Technical Literature | Paxton Access Ltd | View Online |
| Mode | Connectivity | Notes |
|---|---|---|
| SVN Standalone | No network to locks | Access rights on card — update via update points |
| SVN Online | Wired RS-485 to locks | Real-time access control and audit trail |
| SVN Wireless | RF wireless to locks | Real-time, no cabling required |
| Salto KS | Cloud-based | Subscription model, mobile credentials |
| Level | Permissions | Typical Use |
|---|---|---|
| All Areas | All doors, 24/7 | Senior management |
| Office Hours | All doors, Mon–Fri 08:00–18:00 | Standard staff |
| Restricted | Specific doors, specific times | Contractors |
| Emergency | All doors, override schedules | Fire wardens |
| Code / Display | Description | Likely Cause | Action |
|---|---|---|---|
| Lock Battery Low | Lock battery below threshold | Battery end of life | Replace battery. Salto locks typically use 4 × AA batteries. |
| Card Not Recognised | Card presented but not read | Wrong card format, card damaged | Check card format. Re-encode card. Test with known-good card. |
| Access Denied | Card read but access denied | Access level, card expired, lock blacklist | Check access level. Verify card validity. Check blacklist in ProAccess SPACE. |
| Card Expired | Card validity period has passed | Card not updated at update point | Re-encode card or present to update point to refresh access rights. |
| Lock Not Responding | Lock does not respond to card | Battery flat, lock fault | Replace battery. Check lock mechanism. |
| Audit Trail Missing | Events not recorded | Lock not online, data not downloaded | Download audit trail from lock using ProAccess SPACE. |
| Update Point Fault | Update point not communicating | Network fault, power loss | Check network cable and power to update point. |
| Terminal | Function | Notes |
|---|---|---|
| +12V | Power supply to lock | 12V DC from PSU |
| 0V | Common ground | Must be continuous |
| A+ | RS-485 data positive | Twisted pair with B− |
| B− | RS-485 data negative | Twisted pair with A+ |
=== WEB RESEARCH: salto ===
# Salto XS4 SALTO KS Access Control - Comprehensive Technical Reference
This document compiles comprehensive technical information for Salto XS4 and SALTO KS access control systems, including product specifications, installation guides, programming details, and operational procedures. The content is extracted from various official Salto Systems documentation and aims to provide a raw, unsummarized technical reference.
## Salto XS4 One - Technical Specifications
### General Information
- **Product Type:** Stand-alone electronic lock (escutcheon)
### Physical Specifications
- **Housing dimensions (H x W x D):** 298.0 x 54.0 x 24 mm
- **Weight:** 1.8 kg
- **Handle rotation:** Max. 45º
- **Door thicknesses:** 32 mm - 120 mm
- **Distance from the handle to the cylinder:** No cylinder option. Just key override option.
- **Square spindles:** 7 mm, 8 mm, 9 mm, 8 mm split, 9 mm split
### Power and Performance
- **Power source:** 3 AAA batteries (LR03 1.5V)
- **Number of openings:** 40,000 - 60,000 depending on the technology
- **Maximum events on lock audit:** 2,200 events
### Environmental Conditions
- **Outdoor:** +5 ºC / +50 ºC without condensation, optional -20 ºC /+50 ºC
- **Indoor:** +5 ºC / +50 ºC without condensation.
### Certifications
- CE, EN1906, EN 179, EN 1634-1 (Ei60, E260, E90)* (*Certifications in progress)
### Technology Platforms
- **SALTO SPACE:**
- Smile - Selfprogrammable: —
- ROM: •
- SVN data-on-card: •
- Wireless (SALTO RFnet): —
- Wireless (SALTO BLUEnet): •
- **SALTO KS:** —
- **SALTO SALLIS:** —
### ID Technologies
- **MIFARE:** * (DESFire EV2, Classic, Plus, Ultralight C) •
- **BLE Smart:** •
- **NFC:** •
- **Legic:** ** (Legic Prime and Legic Advant) —
- **HID iClass®:** •
- **Picopass:** —
- **i-Button:** —
### Opening Modes
- Standard: •
- Office mode: •
- Timed office: •
- Automatic opening: •
- Automatic opening + office: •
- Toggle: •
- Timed Toggle: •
- Amok mode: —
- Exit leaves open mode: •
- Pin code / Keypad: —
### Options
- **Reader colour:** Black, White
- **Faceplate finish:** IM Satin stainless steel, IP Bright stainless steel, BC BioCote anti-microbial
- **Compatible handles:** U, L, W, H, S, B, P, J, T, Y, Z, O, N, G, K, 2, 3, 4, 7, 5
### Models
- **Ex750_RO:** 2 handles any type.
- **Ex756_RO:** 2 handles any type. Electronic “do not disturb” system (Not available in self-programmable).
- **Ex7P1_RO:** 2 handles any type. Built in mechanical override with audit. (Ex4P0 reference: Euro profile cylinder 30-10).
- **Ex7P6_RO:** 2 handles any type. Electronic “do not disturb” system. Built in mechanical override with audit. (Ex4P6 reference: Euro profile cylinder 30-10).
- **Ex750_SH:** 2 handles any type.
- **Ex7P1_SH:** 2 handles any type. Built in mechanical override with audit. (Ex4P0 reference: Euro profile cylinder 30-10).
### Door Preparation
- RO DOOR PREPARATION
- SH DOOR PREPARATION
## Salto XS4 Original - Installation Guides Information
### Ei4Kxx Series
- **Models:** Ei4K0 m 00 ff t 8 h r, Ei4K2 m xx ff t x h r, Ei4K4 m xx ff t x h r
- **Door Thickness (t*) and Screw Lengths:**
- 32-45 mm: L Screw 5 = 35, L Screw 8 = 30
- 45-54 mm: L Screw 5 = 50, L Screw 8 = 40
- 55-60 mm: L Screw 5 = 50, L Screw 8 = 50
- 60-75 mm: L Screw 5 = 30, L Screw 8 = 30
- 75-90 mm: L Screw 5 = 45, L Screw 8 = 45
- 90-105 mm: L Screw 5 = 30, L Screw 8 = 30
- 105-120 mm: L Screw 5 = 45, L Screw 8 = 45
- **Notes:**
- For Ei4K0xx... Use Panic function + automatic Lock.
- Outdoor gasket required only for doors that exceed 60mm [2-3/8"] thickness.
### Ei45x Series
- **Models:** Ei450, Ei451, Ei452, Ei453, Ei454, Ei456, Ei457, Ei460, Ei4P0, Ei461, Ei4P1, Ei466, Ei4P6, Ei4K0, Ei4K2, Ei4K4
- **Installation Notes:**
- "A2" version has to be installed always with the SALTO LT2L tubular latch.
- SALTO recommends the use of a mortise lock, with a maximum 4º pre-turn.
- Distance 7F on models 56 - 57 - 66 and P6 does not permit to use of the self-drilling screw to improve the escutcheon vertical alignment.
- Batteries: Only LR03 Batteries.
- Do not close the door before programming the lock first.
## Salto XS4 One for European mortise locks - Installation Guide
### Models
- Ei750xx.. series
- Ei751xx..
- Ei752xx..
- Ei753xx..
- Ei754xx..
- Ei756xx..
- Ei757xx..
- Ei7P0xx..
- Ei7P1xx..
- Ei7P6xx..
### Installation Notes
- Only with SALTO Tubular latch!
- SALTO recommends the use of a mortise lock, with a maximum 4º pre-turn.
- Distance 7F on models 56 - 57 and P6 does not permit to use of the self-drilling screw to improve the escutcheon vertical alignment.
- Batteries: LR03 AAA.
- Do not close the door before programming the lock first.
### Other Models
- **Ei756 xx..**: Entry lock with privacy/lockout function.
- **Ei7P6 xx..**: Entry lock with privacy/lockout function and key override.
## Salto XS4 One for Deadlatches - Installation Guide
### Models
- Ei75x xx m DL.. series
### Dimensions (mm)
- Height: 125 (4-59/64")
- Width: 42 (1-21/32")
- Depth: 22.5 (57/64") / 20 (25/32")
- Handle to cylinder distance: 105 (4-9/64")
- Overall height: 160 (6-19/64")
- Overall width: 145 (5-45/64")
### Compatible Deadlatches
- **ADAMS RITE®:** 4510 Series, 4530 Series, 4710 Series, 4900 Series
- **LSDA®:** 4510DLxxxREV
- **ALPRO®:** 524510Lock Type
### Installation Notes
- Only use with special SALTO activator cam disc.
- Only for door thickness > 2-3/8" (60mm).
- Deadlatch not included.
- Batteries: LR03 AAA.
- Do not close the door before programming the lock first.
### Cam Disc Compatibility
- The SALTO activator is aimed to be used exclusively with SALTO escutcheons series Ex75x xx m DL....
- It replaces the Adams Rite® original activator 4580 that works with the locks series 4500, 4700 and 4900.
- The 4580 activators cams can be interchanged with the SALTO ones.
### Tools Required
- TORX 20 (x2, x6)
- PH2 (x1)
- ALLEN 3 (x2)
### Installation Options
- **Option 1:** O 1-1/4" (31.75)
- **Option 2:** O 1-3/8" (O35)
- Only for retrofit
## SALTO PPD 500 (Portable Programming Device) - User's Manual
### Overview
The portable programming device is used to communicate data between the electronic furniture and the PC on which we have designed a locking plan using the SALTO RW software.
### Warnings
1. It is very important to make a back-copy of the database you are working with, in your computer. Salto Systems strongly recommends it, in order to be able to react in Emergency Opening situations and when the user has forgotten to enable the lock erasure.
2. Always make an up-date of the escutcheon after a battery change, or when 1 battery has been removed. This is to maintain the proper clock working, because the lock clock stops when the batteries are dead.
### The Display
1. BATTERY STATUS AREA: three bars (high battery), two bars (normal battery), one bar (low battery - replacement recommended), empty icon (very low batteries - not enough energy for emergency opening), flashing icon (batteries completely dead).
2. TIME AREA: shows the current time (taken from PC).
3. MENU LEVEL AREA: Shows the current main menu.
4. MENU OPTION AREA: shows the current menu option.
5, 6, 7. ACTIVE KEY ICONS: Represent which PPD keys are active.
### PPD Keys
- Power/ESC: Turns PPD on, works like ESCAPE key. Press and hold for 3 seconds to turn off.
- OK/Enter: Validates menu option. Press and hold for 3 seconds to enable/disable back lighting.
- Up Arrow: Go through menu options upwards.
- Down Arrow: Go through menu options downwards.
- Minus (-): Decrease LCD contrast.
- Plus (+): Increase LCD contrast.
- PPD turns off automatically after two minutes without activity. Backlight turns off after 20 seconds.
### Connections
1. Serial port connector (DB-9): Used to communicate with the PC through a serial (RS-232) protocol.
2. RJ11 female phone socket connector: Used to communicate with the electronic furniture.
- To connect to Electronic Furniture: Use SALTO RJ11 connecting cable with a special card on one end. Golden contacts must face the chip side.
- To connect to computer: Use SALTO DB-9 connecting cable.
### Working with the PPD
- UPDATE LOCKS: Shows doors requiring an update, or automatically updates the Electronic Furniture connected to the PPD.
- COLLECT AUDIT TRAIL: Collect audit trail events from one or several doors and view them on the computer.
- EMERGENCY OPENING: Open a door without an authorised smart card (e.g., dead batteries). Must be enabled in software (TOOLS/OPTIONS/PPD).
- INITIALIZE: Used the first time downloading data to Electronic Furniture. Transfers name, users, time zones, calendars, automatic opening periods, time, and date. Deletes ALL current information in the furniture's memory.
- DIAGNOSTIC: Extract information about the Smart Electronic Furniture: ie the serial number, manufacturing date, battery status, firmware...etc
### Data Transmission (PC to PPD)
1. Connect PPD to PC using serial cable. Click CONNECT PPD icon in software.
2. Select ACTIONS TO DO: ALLOW EMERGENCY OPENING, INITIALIZE LOCKS.
3. Click DOWNLOAD. Wait for progress bar to reach 100%.
### Updating Locks
- Must update all building doors at least once every 3 months to update clock and calendars.
- Connect PPD to PC, click CONNECT PPD, click DOWNLOAD.
- Connect PPD to Electronic Furniture using special card cable. Select LOCK LIST. Insert card into reader.
- Connect PPD back to PC to transfer updated battery status and actions.
### Collecting Audit Trails
- Connect PPD to Electronic Furniture. Select COLLECT AUDIT TRAIL.
- Connect PPD to PC. Click AUDIT TRAIL icon, then CONNECT PPD button.
### Emergency Opening
- Enable ALLOW EMERGENCY OPENING in software. Download to PPD.
- Go to blocked door. Select EMERGENCY OPENING on PPD.
- Connect special card cable to PPD and insert into reader.
- Wait 3-4 seconds for DOOR OPENED message.
- Replace batteries and update lock with current locking plan.
## SALTO KS Web App User Manual
### Introduction
This manual is a basic reference guide to operate the SALTO KS web application. It should be used when all hardware is installed and configured.
### Terminology
- **Locks**: Provide access to employees, customers, or guests. Connected to a repeater or IQ to check user access. Salto offers a multitude of lock types.
- **Tag**: Smallest component of SALTO KS, contains a secure RFID chip. Tag ID cannot be duplicated.
- **IQ**: The 'hub' that communicates with all repeaters and locks, and the cloud. Sends remote commands and access groups to the lock. Checks access when a user presents a tag. Considered the 'brain' of the SALTO KS technology.
- **IQ 1.0**: Connected to the cloud via 2G. Added via web-app, activated on mobile app.
- **IQ 2.0**: Multiple connection types (M2M stick, Ethernet, WiFi). Configured to connect to the internet directly via KS apps. Added to site on web-app, activated on mobile app.
- **Repeater**: Extends the distance between the IQ and electronic locks by up to 10 meters. Maximum distance of 40 meters with multiple repeaters.
- **Mobile Key**: Virtual version of a physical Tag, enables phone to unlock a SALTO lock using Bluetooth.
- **Web app**: Cloud solution available via web browser, optimized for bigger screens. Provides full control of SALTO KS site, managing people, permissions, access, and notifications.
- **Mobile app**: Available for iOS and Android, manages access on-the-go. Allows following events and performing remote openings.
- **Pod**: Used in Coliving spaces for apartments shared by multiple tenants. All tenants have full access to Pod locks. Pod members can invite Pod guests with refined access rules.
- **Pod member**: Tenant of a Pod. Manages account from mobile app, can invite and manage guests.
- **Pod guests**: Users that are invited by Pod members to have (optionally) limited access to Pod locks.
- **Pod locks**: The locks that Pod members need to have access to.
- **Office Mode/Manual Office Mode (MOM)***: Lock is permanently unlocked, allowing anyone to enter without a valid Tag/Mobile Key.
- **Regular Office Mode (OM)**: Continuous unlocked state until a user with the right role/permissions locks it. Set remotely via web- or mobile app.
- **Manual Office Mode (MOM)**: (Dis)engages Office Mode on an escutcheon by presenting a valid SALTO KS Tag while holding the inside handle.
- *These modes require settings per lock/user via the web-app.
- **Easy Office Mode (EOM)***: Lock stays unlocked, combined with a set schedule. Selected people can put it in Office Mode at selected times using their tag. Outside the schedule, a tag results in a regular, temporary tag-opening. Locks automatically when the timeframe ends. Useful for easy access without remote action.
- *These modes require settings per lock/user via the web-app.
- **The Code**: 5-character security feature, temporarily valid, shared by mobile app and IQ. Ensures control over critical IQ related features:
- Remote openings via the web-app
- Putting locks in Office Mode via the web-app
- Enabling an additional device for SALTO KS
### Roles
- **Site Owner**: One per site, registers the SALTO KS account. Can create Site Admins, Super Users, and Site Users. Can modify information for persons with Tag profiles and for the account. Receives notifications for changes.
- **Site Admin**: Same rights as Owner, but cannot delete Owner or receive notifications. Can assign other Site Admins.
- **Site Super User**: Can view but not modify Owner or Site Admin details. Can create other Super Users and new Site Users.
- **Site User**: Basic role, only uses SALTO KS to unlock doors. Often does not use the web app. Tag-only access.
### Profiles
- **Tag profile**: User does not have an account, is a Site User with a Tag. Site managers control personal data. Only valid key is a Tag. Tag is owned by the Site.
- **User profile**: User has their own account, controls first name, last name, email address, and phone number. Can log into apps and has varying options based on role. Does not affect access granted, but allows for higher roles and Mobile App use.
### Web App Overview (High-level info of all tabs)
- **Siteswitch**: For multiple sites/locations. Tap site name to switch. All tabs display content for the selected site.
- **Dashboard**: Default opening screen. Summary of locks and Entries. Option to quickly (un)lock a lock or (un)block a person.
- **People**: Overview of everyone with access. Can (un)block people. View person's events, change settings (EOM, remote access, office mode), and see credentials.
- **Locks**: Overview of all locks in the selected site and their status. See recent events and change EOM schedule. Statuses include unlocked, locked, low battery.
- **Access**: Core functionality where access is granted. Create Access Groups to give people access to selected locks on specific timeframes.
- **Notifications**: Site Owner can be notified for any event (Entries, rejections, low battery warnings).
- **Events**: Monitor all events (entries, incidents). Filter to switch between entries (tag-openings, remote openings) and incidents (lock-related issues like low battery).
- **Site**: Account- and hardware-related tab. Generic details and hardware information. Not visible to all users.
### Primary Actions Web App
#### People: Adding people to your Site
- **Create new person**: Create and own person's data (no login for person). Great for Tag-only access. For remote opening rights, person needs to create a profile to login to Mobile App.
1. On People tab, select +new User.
2. Enter person's first and last name, and a Tag.
3. Determine person's role & rights. For Site User, no email required. Select lock options and 'create'.
- **Add existing person**: Add a person who already has a Tag in another Site or their own account.
1. On People tab, select +invite.
2. Enter email address or Tag number. SALTO KS searches for profile and shows known details. Click 'Next'.
3. Determine person's role & rights (similar to creating a new person).
- **Changing role & permissions**: For existing User, change role in SALTO KS.
1. On People tab, find person.
2. Click pencil-icon next to name. Window with person's details appears.
3. In dropdown role, select appropriate role. Higher roles require an account. If no email, enter one to invite them to create an account.
- **Changing lock options**:
1. On People tab, find person.
2. Click pencil-icon next to name. Window with person's details appears.
3. (De)select various lock-options. Hover question marks for additional information.
- **Keys & Offline Access**: SALTO KS manages access via IQ, checking Access Groups over the internet. If a lock cannot connect to an IQ, it stores a limited amount of People and their access locally. Each person can have multiple keys (Tag, Mobile Key).
1. On People tab, find person.
2. Click pencil-icon next to name. Window with person's details appears.
3. Click 'Keys' link to show an overview of the person's Keys.
### Configuring an IQ
- **IQ 1.0**:
1. On the Site tab, select 'Hardware'.
2. Click '+ Add IQ'.
3. Select 'IQ 1.0'.
4. Enter the Device ID (found on the sticker on the IQ).
5. Click 'Add IQ'.
6. Activate the IQ using the mobile app.
- **IQ 2.0**:
1. On the Site tab, select 'Hardware'.
2. Click '+ Add IQ'.
3. Select 'IQ 2.0'.
4. Enter the Device ID.
5. Select connection type (M2M stick, Ethernet, WiFi).
6. Click 'Add IQ'.
7. Configure the IQ using the mobile app.
### Locks: Office Mode and Locking
- **Setting Office Mode**:
1. On the Locks tab, select the desired lock.
2. Click 'Office Mode'.
3. Select the desired Office Mode (Regular, Manual, Easy).
4. Configure settings for the selected Office Mode.
5. Click 'Save'.
- **Locking/Unlocking**:
1. On the Locks tab, select the desired lock.
2. Click 'Lock' or 'Unlock'.
### Access
- **Creating Access Groups**:
1. On the Access tab, click '+ Add Access Group'.
2. Enter a name for the Access Group.
3. Select the locks to be included in the Access Group.
4. Select the people to be included in the Access Group.
5. Set the timeframe for access.
6. Click 'Create'.
### Notifications
- **Setting Notifications**:
1. On the Notifications tab, click '+ Add Notification'.
2. Select the event type (Entries, Locks).
3. Select the specific event (e.g., 'Low Battery Warning').
4. Select the recipient(s) for the notification.
5. Click 'Create'.
### Events
- **Monitoring Events**:
1. On the Events tab, view all entries and incidents.
2. Use the filter to switch between entries and incidents.
### Site
- **Managing Site Details**:
1. On the Site tab, view and edit generic site details.
2. View hardware information.
### PIN Management
- **Forgotten PIN**:
1. On the Profile tab, click 'Forgot PIN'.
2. Follow the instructions to reset the PIN.
### Grant Installer Access
- **Granting Access**:
1. On the Site tab, click 'Grant Installer Access'.
2. Enter the installer's email address.
3. Set the duration for access.
4. Click 'Grant Access'.
### Transfer Ownership
- **Transferring Ownership**:
1. On the Site tab, click 'Transfer Ownership'.
2. Enter the new owner's email address.
3. Confirm the transfer.
### Profile
- **Managing Profile**:
1. On the Profile tab, view and edit personal details.
### Subscription
- **Managing Subscription**:
1. On the Subscription tab, view subscription details.
### Pods
- **Managing Pods**:
1. On the Pods tab, view and manage Pods, Pod members, and Pod guests.
2. Set access rules for Pod guests.
=== WEB RESEARCH: xs4 ===
# Salto XS4 SALTO KS Access Control - Comprehensive Technical Reference
This document compiles comprehensive technical information for Salto XS4 and SALTO KS access control systems, including product specifications, installation guides, programming details, and operational procedures. The content is extracted from various official Salto Systems documentation and aims to provide a raw, unsummarized technical reference.
## Salto XS4 One - Technical Specifications
### General Information
- **Product Type:** Stand-alone electronic lock (escutcheon)
### Physical Specifications
- **Housing dimensions (H x W x D):** 298.0 x 54.0 x 24 mm
- **Weight:** 1.8 kg
- **Handle rotation:** Max. 45º
- **Door thicknesses:** 32 mm - 120 mm
- **Distance from the handle to the cylinder:** No cylinder option. Just key override option.
- **Square spindles:** 7 mm, 8 mm, 9 mm, 8 mm split, 9 mm split
### Power and Performance
- **Power source:** 3 AAA batteries (LR03 1.5V)
- **Number of openings:** 40,000 - 60,000 depending on the technology
- **Maximum events on lock audit:** 2,200 events
### Environmental Conditions
- **Outdoor:** +5 ºC / +50 ºC without condensation, optional -20 ºC /+50 ºC
- **Indoor:** +5 ºC / +50 ºC without condensation.
### Certifications
- CE, EN1906, EN 179, EN 1634-1 (Ei60, E260, E90)* (*Certifications in progress)
### Technology Platforms
- **SALTO SPACE:**
- Smile - Selfprogrammable: —
- ROM: •
- SVN data-on-card: •
- Wireless (SALTO RFnet): —
- Wireless (SALTO BLUEnet): •
- **SALTO KS:** —
- **SALTO SALLIS:** —
### ID Technologies
- **MIFARE:** * (DESFire EV2, Classic, Plus, Ultralight C) •
- **BLE Smart:** •
- **NFC:** •
- **Legic:** ** (Legic Prime and Legic Advant) —
- **HID iClass®:** •
- **Picopass:** —
- **i-Button:** —
### Opening Modes
- Standard: •
- Office mode: •
- Timed office: •
- Automatic opening: •
- Automatic opening + office: •
- Toggle: •
- Timed Toggle: •
- Amok mode: —
- Exit leaves open mode: •
- Pin code / Keypad: —
### Options
- **Reader colour:** Black, White
- **Faceplate finish:** IM Satin stainless steel, IP Bright stainless steel, BC BioCote anti-microbial
- **Compatible handles:** U, L, W, H, S, B, P, J, T, Y, Z, O, N, G, K, 2, 3, 4, 7, 5
### Models
- **Ex750_RO:** 2 handles any type.
- **Ex756_RO:** 2 handles any type. Electronic “do not disturb” system (Not available in self-programmable).
- **Ex7P1_RO:** 2 handles any type. Built in mechanical override with audit. (Ex4P0 reference: Euro profile cylinder 30-10).
- **Ex7P6_RO:** 2 handles any type. Electronic “do not disturb” system. Built in mechanical override with audit. (Ex4P6 reference: Euro profile cylinder 30-10).
- **Ex750_SH:** 2 handles any type.
- **Ex7P1_SH:** 2 handles any type. Built in mechanical override with audit. (Ex4P0 reference: Euro profile cylinder 30-10).
### Door Preparation
- RO DOOR PREPARATION
- SH DOOR PREPARATION
## Salto XS4 Original - Installation Guides Information
### Ei4Kxx Series
- **Models:** Ei4K0 m 00 ff t 8 h r, Ei4K2 m xx ff t x h r, Ei4K4 m xx ff t x h r
- **Door Thickness (t*) and Screw Lengths:**
- 32-45 mm: L Screw 5 = 35, L Screw 8 = 30
- 45-54 mm: L Screw 5 = 50, L Screw 8 = 40
- 55-60 mm: L Screw 5 = 50, L Screw 8 = 50
- 60-75 mm: L Screw 5 = 30, L Screw 8 = 30
- 75-90 mm: L Screw 5 = 45, L Screw 8 = 45
- 90-105 mm: L Screw 5 = 30, L Screw 8 = 30
- 105-120 mm: L Screw 5 = 45, L Screw 8 = 45
- **Notes:**
- For Ei4K0xx... Use Panic function + automatic Lock.
- Outdoor gasket required only for doors that exceed 60mm [2-3/8"] thickness.
### Ei45x Series
- **Models:** Ei450, Ei451, Ei452, Ei453, Ei454, Ei456, Ei457, Ei460, Ei4P0, Ei461, Ei4P1, Ei466, Ei4P6, Ei4K0, Ei4K2, Ei4K4
- **Installation Notes:**
- "A2" version has to be installed always with the SALTO LT2L tubular latch.
- SALTO recommends the use of a mortise lock, with a maximum 4º pre-turn.
- Distance 7F on models 56 - 57 - 66 and P6 does not permit to use of the self-drilling screw to improve the escutcheon vertical alignment.
- Batteries: Only LR03 Batteries.
- Do not close the door before programming the lock first.
## Salto XS4 One for European mortise locks - Installation Guide
### Models
- Ei750xx.. series
- Ei751xx..
- Ei752xx..
- Ei753xx..
- Ei754xx..
- Ei756xx..
- Ei757xx..
- Ei7P0xx..
- Ei7P1xx..
- Ei7P6xx..
### Installation Notes
- Only with SALTO Tubular latch!
- SALTO recommends the use of a mortise lock, with a maximum 4º pre-turn.
- Distance 7F on models 56 - 57 and P6 does not permit to use of the self-drilling screw to improve the escutcheon vertical alignment.
- Batteries: LR03 AAA.
- Do not close the door before programming the lock first.
### Other Models
- **Ei756 xx..**: Entry lock with privacy/lockout function.
- **Ei7P6 xx..**: Entry lock with privacy/lockout function and key override.
## Salto XS4 One for Deadlatches - Installation Guide
### Models
- Ei75x xx m DL.. series
### Dimensions (mm)
- Height: 125 (4-59/64")
- Width: 42 (1-21/32")
- Depth: 22.5 (57/64") / 20 (25/32")
- Handle to cylinder distance: 105 (4-9/64")
- Overall height: 160 (6-19/64")
- Overall width: 145 (5-45/64")
### Compatible Deadlatches
- **ADAMS RITE®:** 4510 Series, 4530 Series, 4710 Series, 4900 Series
- **LSDA®:** 4510DLxxxREV
- **ALPRO®:** 524510Lock Type
### Installation Notes
- Only use with special SALTO activator cam disc.
- Only for door thickness > 2-3/8" (60mm).
- Deadlatch not included.
- Batteries: LR03 AAA.
- Do not close the door before programming the lock first.
### Cam Disc Compatibility
- The SALTO activator is aimed to be used exclusively with SALTO escutcheons series Ex75x xx m DL....
- It replaces the Adams Rite® original activator 4580 that works with the locks series 4500, 4700 and 4900.
- The 4580 activators cams can be interchanged with the SALTO ones.
### Tools Required
- TORX 20 (x2, x6)
- PH2 (x1)
- ALLEN 3 (x2)
### Installation Options
- **Option 1:** O 1-1/4" (31.75)
- **Option 2:** O 1-3/8" (O35)
- Only for retrofit
## SALTO PPD 500 (Portable Programming Device) - User's Manual
### Overview
The portable programming device is used to communicate data between the electronic furniture and the PC on which we have designed a locking plan using the SALTO RW software.
### Warnings
1. It is very important to make a back-copy of the database you are working with, in your computer. Salto Systems strongly recommends it, in order to be able to react in Emergency Opening situations and when the user has forgotten to enable the lock erasure.
2. Always make an up-date of the escutcheon after a battery change, or when 1 battery has been removed. This is to maintain the proper clock working, because the lock clock stops when the batteries are dead.
### The Display
1. BATTERY STATUS AREA: three bars (high battery), two bars (normal battery), one bar (low battery - replacement recommended), empty icon (very low batteries - not enough energy for emergency opening), flashing icon (batteries completely dead).
2. TIME AREA: shows the current time (taken from PC).
3. MENU LEVEL AREA: Shows the current main menu.
4. MENU OPTION AREA: shows the current menu option.
5, 6, 7. ACTIVE KEY ICONS: Represent which PPD keys are active.
### PPD Keys
- Power/ESC: Turns PPD on, works like ESCAPE key. Press and hold for 3 seconds to turn off.
- OK/Enter: Validates menu option. Press and hold for 3 seconds to enable/disable back lighting.
- Up Arrow: Go through menu options upwards.
- Down Arrow: Go through menu options downwards.
- Minus (-): Decrease LCD contrast.
- Plus (+): Increase LCD contrast.
- PPD turns off automatically after two minutes without activity. Backlight turns off after 20 seconds.
### Connections
1. Serial port connector (DB-9): Used to communicate with the PC through a serial (RS-232) protocol.
2. RJ11 female phone socket connector: Used to communicate with the electronic furniture.
- To connect to Electronic Furniture: Use SALTO RJ11 connecting cable with a special card on one end. Golden contacts must face the chip side.
- To connect to computer: Use SALTO DB-9 connecting cable.
### Working with the PPD
- UPDATE LOCKS: Shows doors requiring an update, or automatically updates the Electronic Furniture connected to the PPD.
- COLLECT AUDIT TRAIL: Collect audit trail events from one or several doors and view them on the computer.
- EMERGENCY OPENING: Open a door without an authorised smart card (e.g., dead batteries). Must be enabled in software (TOOLS/OPTIONS/PPD).
- INITIALIZE: Used the first time downloading data to Electronic Furniture. Transfers name, users, time zones, calendars, automatic opening periods, time, and date. Deletes ALL current information in the furniture's memory.
- DIAGNOSTIC: Extract information about the Smart Electronic Furniture: ie the serial number, manufacturing date, battery status, firmware...etc
### Data Transmission (PC to PPD)
1. Connect PPD to PC using serial cable. Click CONNECT PPD icon in software.
2. Select ACTIONS TO DO: ALLOW EMERGENCY OPENING, INITIALIZE LOCKS.
3. Click DOWNLOAD. Wait for progress bar to reach 100%.
### Updating Locks
- Must update all building doors at least once every 3 months to update clock and calendars.
- Connect PPD to PC, click CONNECT PPD, click DOWNLOAD.
- Connect PPD to Electronic Furniture using special card cable. Select LOCK LIST. Insert card into reader.
- Connect PPD back to PC to transfer updated battery status and actions.
### Collecting Audit Trails
- Connect PPD to Electronic Furniture. Select COLLECT AUDIT TRAIL.
- Connect PPD to PC. Click AUDIT TRAIL icon, then CONNECT PPD button.
### Emergency Opening
- Enable ALLOW EMERGENCY OPENING in software. Download to PPD.
- Go to blocked door. Select EMERGENCY OPENING on PPD.
- Connect special card cable to PPD and insert into reader.
- Wait 3-4 seconds for DOOR OPENED message.
- Replace batteries and update lock with current locking plan.
## SALTO KS Web App User Manual
### Introduction
This manual is a basic reference guide to operate the SALTO KS web application. It should be used when all hardware is installed and configured.
### Terminology
- **Locks**: Provide access to employees, customers, or guests. Connected to a repeater or IQ to check user access. Salto offers a multitude of lock types.
- **Tag**: Smallest component of SALTO KS, contains a secure RFID chip. Tag ID cannot be duplicated.
- **IQ**: The 'hub' that communicates with all repeaters and locks, and the cloud. Sends remote commands and access groups to the lock. Checks access when a user presents a tag. Considered the 'brain' of the SALTO KS technology.
- **IQ 1.0**: Connected to the cloud via 2G. Added via web-app, activated on mobile app.
- **IQ 2.0**: Multiple connection types (M2M stick, Ethernet, WiFi). Configured to connect to the internet directly via KS apps. Added to site on web-app, activated on mobile app.
- **Repeater**: Extends the distance between the IQ and electronic locks by up to 10 meters. Maximum distance of 40 meters with multiple repeaters.
- **Mobile Key**: Virtual version of a physical Tag, enables phone to unlock a SALTO lock using Bluetooth.
- **Web app**: Cloud solution available via web browser, optimized for bigger screens. Provides full control of SALTO KS site, managing people, permissions, access, and notifications.
- **Mobile app**: Available for iOS and Android, manages access on-the-go. Allows following events and performing remote openings.
- **Pod**: Used in Coliving spaces for apartments shared by multiple tenants. All tenants have full access to Pod locks. Pod members can invite Pod guests with refined access rules.
- **Pod member**: Tenant of a Pod. Manages account from mobile app, can invite and manage guests.
- **Pod guests**: Users that are invited by Pod members to have (optionally) limited access to Pod locks.
- **Pod locks**: The locks that Pod members need to have access to.
- **Office Mode/Manual Office Mode (MOM)***: Lock is permanently unlocked, allowing anyone to enter without a valid Tag/Mobile Key.
- **Regular Office Mode (OM)**: Continuous unlocked state until a user with the right role/permissions locks it. Set remotely via web- or mobile app.
- **Manual Office Mode (MOM)**: (Dis)engages Office Mode on an escutcheon by presenting a valid SALTO KS Tag while holding the inside handle.
- *These modes require settings per lock/user via the web-app.
- **Easy Office Mode (EOM)***: Lock stays unlocked, combined with a set schedule. Selected people can put it in Office Mode at selected times using their tag. Outside the schedule, a tag results in a regular, temporary tag-opening. Locks automatically when the timeframe ends. Useful for easy access without remote action.
- *These modes require settings per lock/user via the web-app.
- **The Code**: 5-character security feature, temporarily valid, shared by mobile app and IQ. Ensures control over critical IQ related features:
- Remote openings via the web-app
- Putting locks in Office Mode via the web-app
- Enabling an additional device for SALTO KS
### Roles
- **Site Owner**: One per site, registers the SALTO KS account. Can create Site Admins, Super Users, and Site Users. Can modify information for persons with Tag profiles and for the account. Receives notifications for changes.
- **Site Admin**: Same rights as Owner, but cannot delete Owner or receive notifications. Can assign other Site Admins.
- **Site Super User**: Can view but not modify Owner or Site Admin details. Can create other Super Users and new Site Users.
- **Site User**: Basic role, only uses SALTO KS to unlock doors. Often does not use the web app. Tag-only access.
### Profiles
- **Tag profile**: User does not have an account, is a Site User with a Tag. Site managers control personal data. Only valid key is a Tag. Tag is owned by the Site.
- **User profile**: User has their own account, controls first name, last name, email address, and phone number. Can log into apps and has varying options based on role. Does not affect access granted, but allows for higher roles and Mobile App use.
### Web App Overview (High-level info of all tabs)
- **Siteswitch**: For multiple sites/locations. Tap site name to switch. All tabs display content for the selected site.
- **Dashboard**: Default opening screen. Summary of locks and Entries. Option to quickly (un)lock a lock or (un)block a person.
- **People**: Overview of everyone with access. Can (un)block people. View person's events, change settings (EOM, remote access, office mode), and see credentials.
- **Locks**: Overview of all locks in the selected site and their status. See recent events and change EOM schedule. Statuses include unlocked, locked, low battery.
- **Access**: Core functionality where access is granted. Create Access Groups to give people access to selected locks on specific timeframes.
- **Notifications**: Site Owner can be notified for any event (Entries, rejections, low battery warnings).
- **Events**: Monitor all events (entries, incidents). Filter to switch between entries (tag-openings, remote openings) and incidents (lock-related issues like low battery).
- **Site**: Account- and hardware-related tab. Generic details and hardware information. Not visible to all users.
### Primary Actions Web App
#### People: Adding people to your Site
- **Create new person**: Create and own person's data (no login for person). Great for Tag-only access. For remote opening rights, person needs to create a profile to login to Mobile App.
1. On People tab, select +new User.
2. Enter person's first and last name, and a Tag.
3. Determine person's role & rights. For Site User, no email required. Select lock options and 'create'.
- **Add existing person**: Add a person who already has a Tag in another Site or their own account.
1. On People tab, select +invite.
2. Enter email address or Tag number. SALTO KS searches for profile and shows known details. Click 'Next'.
3. Determine person's role & rights (similar to creating a new person).
- **Changing role & permissions**: For existing User, change role in SALTO KS.
1. On People tab, find person.
2. Click pencil-icon next to name. Window with person's details appears.
3. In dropdown role, select appropriate role. Higher roles require an account. If no email, enter one to invite them to create an account.
- **Changing lock options**:
1. On People tab, find person.
2. Click pencil-icon next to name. Window with person's details appears.
3. (De)select various lock-options. Hover question marks for additional information.
- **Keys & Offline Access**: SALTO KS manages access via IQ, checking Access Groups over the internet. If a lock cannot connect to an IQ, it stores a limited amount of People and their access locally. Each person can have multiple keys (Tag, Mobile Key).
1. On People tab, find person.
2. Click pencil-icon next to name. Window with person's details appears.
3. Click 'Keys' link to show an overview of the person's Keys.
### Configuring an IQ
- **IQ 1.0**:
1. On the Site tab, select 'Hardware'.
2. Click '+ Add IQ'.
3. Select 'IQ 1.0'.
4. Enter the Device ID (found on the sticker on the IQ).
5. Click 'Add IQ'.
6. Activate the IQ using the mobile app.
- **IQ 2.0**:
1. On the Site tab, select 'Hardware'.
2. Click '+ Add IQ'.
3. Select 'IQ 2.0'.
4. Enter the Device ID.
5. Select connection type (M2M stick, Ethernet, WiFi).
6. Click 'Add IQ'.
7. Configure the IQ using the mobile app.
### Locks: Office Mode and Locking
- **Setting Office Mode**:
1. On the Locks tab, select the desired lock.
2. Click 'Office Mode'.
3. Select the desired Office Mode (Regular, Manual, Easy).
4. Configure settings for the selected Office Mode.
5. Click 'Save'.
- **Locking/Unlocking**:
1. On the Locks tab, select the desired lock.
2. Click 'Lock' or 'Unlock'.
### Access
- **Creating Access Groups**:
1. On the Access tab, click '+ Add Access Group'.
2. Enter a name for the Access Group.
3. Select the locks to be included in the Access Group.
4. Select the people to be included in the Access Group.
5. Set the timeframe for access.
6. Click 'Create'.
### Notifications
- **Setting Notifications**:
1. On the Notifications tab, click '+ Add Notification'.
2. Select the event type (Entries, Locks).
3. Select the specific event (e.g., 'Low Battery Warning').
4. Select the recipient(s) for the notification.
5. Click 'Create'.
### Events
- **Monitoring Events**:
1. On the Events tab, view all entries and incidents.
2. Use the filter to switch between entries and incidents.
### Site
- **Managing Site Details**:
1. On the Site tab, view and edit generic site details.
2. View hardware information.
### PIN Management
- **Forgotten PIN**:
1. On the Profile tab, click 'Forgot PIN'.
2. Follow the instructions to reset the PIN.
### Grant Installer Access
- **Granting Access**:
1. On the Site tab, click 'Grant Installer Access'.
2. Enter the installer's email address.
3. Set the duration for access.
4. Click 'Grant Access'.
### Transfer Ownership
- **Transferring Ownership**:
1. On the Site tab, click 'Transfer Ownership'.
2. Enter the new owner's email address.
3. Confirm the transfer.
### Profile
- **Managing Profile**:
1. On the Profile tab, view and edit personal details.
### Subscription
- **Managing Subscription**:
1. On the Subscription tab, view subscription details.
### Pods
- **Managing Pods**:
1. On the Pods tab, view and manage Pods, Pod members, and Pod guests.
2. Set access rules for Pod guests.
| Model | RFID Support |
|---|---|
| BEW2-OHP | 125 kHz HID Prox only |
| BEW2-ODP | 125 kHz EM only |
| BEW2-OAP | 125 kHz EM/HID Prox + 13.56 MHz MIFARE/DESFire EV1/FeliCa/NFC/iCLASS SE (recommended) |
| Fault / Indication | Description | Likely Cause | Action |
|---|---|---|---|
| Red LED / Beep | Access denied | Unrecognised fingerprint or card, access level | Re-enrol fingerprint. Check card format. Verify access level in BioStar 2. |
| No LED / No Power | Device not powered | PoE switch not supplying power, PSU fault, wiring | Check PoE switch port. Verify 12V DC supply. Check wiring continuity. |
| Device Offline | Not visible in BioStar 2 | Network fault, IP conflict, firewall | Check Ethernet connection. Verify IP address. Check firewall rules for port 51212. |
| Fake Finger Detected | LFD rejection | Fake finger, dry/wet finger, LFD sensitivity | Clean sensor. Adjust LFD sensitivity in BioStar 2. Re-enrol with clean, dry finger. |
| Card Not Read | Card presented but not recognised | Wrong card format, card not enrolled | Check card type matches device model (BEW2-OAP for multi-format). Enrol card in BioStar 2. |
| Tamper Alert | Tamper input triggered | Device removed from back plate | Re-secure device to back plate. Check tamper wiring. |
| Relay Not Operating | Door lock not releasing | Relay wiring fault, relay configuration | Check relay wiring. Verify relay mode in BioStar 2 (NO/NC). Test relay with manual trigger. |
| Terminal | Function | Notes |
|---|---|---|
| RJ45 (Ethernet) | Network + PoE power | IEEE 802.3af PoE; 10/100 Mbps auto MDI/MDI-X |
| +12V | DC power input | 12V DC, max 600 mA |
| GND | Common ground | Must be continuous with access panel |
| RS-485 A+ | OSDP / RS-485 positive | Twisted pair; host or slave selectable |
| RS-485 B− | OSDP / RS-485 negative | Twisted pair; OSDP V2.1.6 |
| D0 (Wiegand) | Wiegand Data 0 | Input or output selectable |
| D1 (Wiegand) | Wiegand Data 1 | Input or output selectable |
| TTL IN 1 | Door contact input | Voltage-free; monitor door open/closed |
| TTL IN 2 | Exit button input | Voltage-free; push-to-make REX |
| Relay COM | Relay common | Use NO or NC depending on lock type |
| Relay NO | Relay normally open | Connect to fail-secure lock |
| Relay NC | Relay normally closed | Connect to fail-safe lock |
SUPREMA BIOENTRY W2 — OUTDOOR IP FINGERPRINT DEVICE Source: Datasheet AHL-BEW2-170731-03-EN; Installation Guide BioEntry W2_UL_IG_1.29_EN_240131.0 Manufacturer: Suprema Inc. BIOMETRIC SPECIFICATIONS: Sensor type: Optical (OP5) Template format: SUPREMA / ISO 19794-2 / ANSI 378 Matcher: MINEX certified and compliant Live Finger Detection (LFD): Supported RFID SPECIFICATIONS: LF (125 kHz): EM4100, HID Prox (model dependent) HF (13.56 MHz): MIFARE Classic, MIFARE DESFire EV1, iCLASS SE, FeliCa, NFC (BEW2-OAP) PROCESSING: CPU: 1.2 GHz Quad Core Memory: 2 GB Flash + 256 MB RAM CAPACITY: Max Users (1:1): 500,000 Max Users (1:N): 100,000 (200,000 with expansion kit) Max Templates (1:1): 1,000,000 (1 finger = 2 templates) Max Templates (1:N): 200,000 Max Event Logs: 1,000,000 (text) COMMUNICATION: Ethernet: 10/100 Mbps, auto MDI/MDI-X RS-485: 1ch host or slave (selectable); OSDP V2.1.6 Wiegand: 1ch input or output (selectable) TTL: 2ch input OUTPUTS: Relay: 1 relay (NO/NC) LED: Multi-colour Sound: Multi-tone buzzer POWER: PoE: IEEE 802.3af compliant DC: 12V DC, max 600 mA ENVIRONMENTAL: Operating temperature: −20°C to +50°C Operating humidity: 0% to 80%, non-condensing Ingress protection: IP67 Impact protection: IK09 Tamper: Supported PHYSICAL: Dimensions (W×H×D): 50 × 172 × 43.5 mm Weight: 251 g CERTIFICATIONS: CE, FCC, KC, RoHS, REACH, WEEE MODEL VARIANTS: BEW2-OHP: 125 kHz HID Prox BEW2-ODP: 125 kHz EM BEW2-OAP: 125 kHz EM/HID Prox + 13.56 MHz MIFARE/DESFire EV1/FeliCa/NFC/iCLASS SE RS-485 BUS: Up to 7 fingerprint authentication devices per RS-485 segment
| Document | Source | Link |
|---|---|---|
| BioEntry W2 Datasheet (AHL-BEW2-170731-03-EN) | dds-security.com | Download PDF |
| BioEntry W2 Installation Guide (UL IG 1.29 EN) | supremainc.com | Download PDF |
| BioEntry W2 Product Page | supremainc.com | View Online |
| Product | Type | Notes |
|---|---|---|
| AC2000 WEB | Web-based access control | Browser-based management |
| AC2000 AED | Advanced event display | Real-time event monitoring |
| AC2000 Lite | Small-site version | Up to 1,000 cardholders |
| SiPass Integrated | Siemens-branded AC2000 | Identical platform |
| Code / Display | Description | Likely Cause | Action |
|---|---|---|---|
| Controller Offline | Controller not communicating | Network fault, power loss | Check network and power. Ping controller. |
| Card Not Found | Card not recognised | Card not enrolled, wrong format | Re-enrol card. Check card format. |
| Access Denied | Card read but access denied | Access level, schedule | Check access level and time schedule. |
| Database Error | AC2000 database fault | Disk fault, improper shutdown | Restore from backup. Run database repair. |
| Server Fault | AC2000 server not responding | Service stopped, OS fault | Restart AC2000 service. Check Windows event log. |
| Terminal | Function | Notes |
|---|---|---|
| +12V | Power supply | 12V DC from PSU |
| 0V | Common ground | Must be continuous |
| D0 | Wiegand Data 0 | Green wire |
| D1 | Wiegand Data 1 | White wire |
| LOCK+ | Electric lock positive | Fused at 1A |
| LOCK− | Electric lock negative | Via relay output |
| REX | Request to exit | Normally open push button |
| DOOR | Door contact | Normally closed magnetic contact |
=== WEB RESEARCH: vanderbilt === SPC42, SPC52, SPC53, SPC63 Installation & Configuration Manual Document ID: I-200572 Edition date: 08.12.2023 --- PAGE BREAK --- Data and design subject to change without notice. / Supply subject to availability. © 2023 Copyright by Vanderbilt International Ltd. We reserve all rights in this document and in the subject thereof. By acceptance of the document the recipient acknowledges these rights and undertakes not to publish the document nor the subject thereof in full or in part, nor to make them available to any third party without our prior express written authorization, nor to use it for any purpose other than for which it was delivered to him. --- PAGE BREAK --- Table of Contents 1 Meaning of symbols 9 2 Security 10 2.1 Target group 10 2.2 General safety instructions 10 2.2.1 General information 10 2.2.2 Transport 11 2.2.3 Setup 11 2.2.4 Operation 11 2.2.5 Service and maintenance 11 2.3 Meaning of written warning notices and hazard symbols 12 2.3.1 Warning notices 12 2.3.2 Hazard symbols 12 3 Directives and standards 13 3.1 EU directives 13 3.2 Overview of Conformity to EN50131 Standard 13 3.3 Compliance with VdS 2115:2015-12 18 3.3.1 Compliance with EN50131 Approvals 18 3.4 Compliance with EN 50136-1:2012 and EN 50136-2:2014 19 3.5 Compliance with INCERT Approvals 19 3.6 Compliance with NF and A2P approvals including CYBER requirements - SPC Products 20 4 Technical Data 21 4.1 SPC Matrix 21 5 Introduction 22 6 Mounting system equipment 23 6.1 Mounting a G2 housing 23 6.2 Mounting a G3 housing 23 6.2.1 Mounting a Back Tamper Kit 24 6.2.2 Battery installation for EN50131 compliance 27 6.3 Mounting a keypad 28 6.4 Mounting an expander 28 6.5 Wiring the X-BUS Interface 28 6.5.1 Wiring the Inputs 29 6.5.2 Wiring the Outputs 30 7 Controller hardware 31 7.1 Controller Hardware SPC42/SPC52/SPC53/SPC63 31 8 Door Expander 34 9 Wiring the system 35 © Vanderbilt 2023 3 I-200572 08.12.2023 --- PAGE BREAK --- SPC42/52/53/63 – Installation & Configuration Manual Table of Contents 9.1 Wiring the X-BUS interface 35 9.1.1 Loop configuration 36 9.1.2 Spur configuration 37 9.1.3 Star and multi-drop configuration 38 9.1.4 Shielding 43 9.1.5 Cable Map 43 9.2 Wiring of branch expander 43 9.3 Wiring the system ground 44 9.4 Wiring the relay output 44 9.5 Wiring the zone inputs 45 9.6 Wiring an external SAB bell 48 9.7 Wiring an internal sounder 48 9.8 Wiring Glassbreak 49 9.9 Installing plug-in modules 49 10 Powering up the SPC controller 51 10.1 Powering from battery only 51 11 Keypad user interface 52 11.1 SPCK420/421 52 11.1.1 About the LCD keypad 52 11.1.2 Using the LCD keypad interface 54 11.1.3 Data entry on the LCD keypad 57 12 Starting the system 59 12.1 Engineer modes 59 12.1.1 Engineer PINs 59 12.2 Programming with the keypad 59 12.3 Configuring start-up settings 60 12.4 Creating system users 61 12.5 Programming the portable PACE 62 12.6 Configuring wireless fob devices 63 12.6.1 Clearing alerts using the fob 63 13 Soft Engineer programming via the keypad 65 14 Engineer programming via the keypad 66 14.1 System Status 66 14.2 Options 67 14.3 Timers 71 14.4 Areas 75 14.5 Area Groups 77 14.6 X-BUS 77 14.6.1 X-BUS Addressing © Vanderbilt 2023 77 4 I-200572 08.12.2023 --- PAGE BREAK --- SPC42/52/53/63 – Installation & Configuration Manual Table of Contents 14.6.2 XBUS Refresh 77 14.6.3 Reconfigure 78 14.6.4 Keypads/Expanders/Door Controllers 78 14.6.5 Addressing Mode 87 14.6.6 XBUS Type 88 14.6.7 Bus Retries 88 14.6.8 Comms Timer 88 14.7 Users 88 14.7.1 Add 88 14.7.2 Edit 89 14.7.3 Delete 91 14.8 User Profiles 92 14.8.1 Add 92 14.8.2 Edit 92 14.8.3 Delete 92 14.9 Wireless 92 14.9.1 Select a wireless programming option 93 14.9.2 Two way wireless 95 14.10 Zones 99 14.11 Doors 99 14.12 Outputs 103 14.12.1 Outputs types and output ports 104 14.13 Communication 108 14.13.1 Serial Ports 108 14.13.2 Ethernet Ports 108 14.13.3 Modems 109 14.13.4 Central Station 111 14.13.5 SPC Connect PRO 113 14.14 Test 113 14.14.1 Bell Test 113 14.14.2 Walk Test 113 14.14.3 Zone Monitor 114 14.14.4 Output Test 115 14.14.5 Soak Test 115 14.14.6 Audible Options 115 14.14.7 Visual Indicators 115 14.14.8 Seismic Test 116 14.15 Utilities 116 14.16 Isolate 116 © Vanderbilt 2023 5 I-200572 08.12.2023 --- PAGE BREAK --- SPC42/52/53/63 – Installation & Configuration Manual Table of Contents 14.17 Event Log 117 14.18 Access Log 117 14.19 Alarm Log 117 14.20 Change Engineer Pin 118 14.21 SMS 118 14.21.1 Add 119 14.21.2 Edit 119 14.21.3 Delete 120 14.22 Set Date/Time 120 14.23 Installer Text 120 14.24 Door Control 121 14.25 SPC Connect 121 15 Engineer programming via the browser 122 15.1 System Information 122 15.2 Ethernet interface 122 15.3 Connecting to the panel via USB 124 15.4 Logging into the browser 124 15.5 SPC Home 125 15.5.1 System Summary 125 15.5.2 Alarms Overview 126 15.5.3 Viewing Video 126 15.6 Panel status 127 15.6.1 Status 127 15.6.2 X-Bus Status 127 15.6.3 Wireless 132 15.6.4 Zones 134 15.6.5 Doors 135 15.6.6 FlexC Status 136 15.6.7 System alerts 137 15.7 Logs 137 15.7.1 System Log 137 15.7.2 Access Log 138 15.7.3 ALARM LOG 138 15.8 Users © Vanderbilt 2023 138 15.8.1 Adding/Editing a User 139 15.8.2 Adding/Editing User Profiles 141 15.8.3 Configuring SMS 144 15.8.4 SMS Commands 145 15.8.5 Deleting Web Passwords 147 6 I-200572 08.12.2023 --- PAGE BREAK --- SPC42/52/53/63 – Installation & Configuration Manual Table of Contents 15.8.6 Configuring Engineer Settings 147 15.9 Wireless 149 15.9.1 Two way wireless 150 15.10 Configuration 154 15.10.1 Configuring controller inputs and outputs 154 15.10.2 X-BUS 160 15.10.3 Changing system settings 169 15.10.4 Configuring zones, doors and areas 185 15.10.5 Calendars 197 15.10.6 Change own PIN 199 15.10.7 Configuring advanced settings 200 15.11 Configuring Communications 208 15.11.1 Communications Settings 208 15.11.2 FlexC® 215 15.11.3 Reporting 235 15.11.4 PC Tools 243 15.12 File Operations 244 15.12.1 File Upgrade Operations 245 15.12.2 File Manager Operations 247 16 Accessing web server remotely 249 16.1 PSTN connection 249 17 Intruder alarm functionality 251 17.1 Financial mode operation 251 17.2 Commercial mode operation 251 17.3 Domestic mode operation 252 17.4 Full and local alarms 252 18 System examples and scenarios 254 18.1 When to use a common area 254 19 Seismic Sensors 256 19.1 Seismic Sensor Testing 256 19.1.1 Manual and Automatic Test Process 256 19.1.2 Automatically Testing Sensors 257 19.1.3 Manually Testing Sensors 258 20 Blocking Lock Operation 260 20.1 Blocking Lock 260 20.2 Authorized Setting of the Blocking Lock 261 20.3 Locking Element 262 21 Appendix 264 21.1 Network cable connections © Vanderbilt 2023 264 7 I-200572 08.12.2023 --- PAGE BREAK --- SPC42/52/53/63 – Installation & Configuration Manual Table of Contents 21.2 Controller status LEDs 265 21.3 Powering expanders from the auxiliary power terminals 265 21.4 Calculating the battery power requirements 266 21.5 Domestic, Commercial and Financial mode default settings 267 21.6 SIA Codes 267 21.7 CID Codes 273 21.8 User PIN combinations 275 21.9 Duress PINs 275 21.10 Automatic inhibits 275 21.10.1 Zones 275 21.10.2 Access PINs 276 21.10.3 Engineer Access 276 21.10.4 Keypad User Logoff 276 21.11 Wiring of mains cable to the controller 276 21.12 Maintenance controller 276 21.13 Maintenance 277 21.14 Zone types 278 21.15 Zone attributes 283 21.16 ATS levels and attenuation specifications 285 21.17 Supported card readers and card formats 286 21.18 FlexC Glossary 288 21.19 FlexC Commands 289 21.20 ATS Category Timings 292 21.21 ATP Category Timings 293 22 Notes © Vanderbilt 2023 295 8 I-200572 08.12.2023 --- PAGE BREAK --- 1 Meaning of symbols There are several symbols in the document: Symbol Description Only available for SPC controller with IP interface (SPC43/SPC52/SPC53/SPC63). Not available for installation type Domestic. Only available in unrestricted mode. Find further information about Security Grade, Region, or Mode in text. See Appendix for further information. © Vanderbilt 2023 9 I-200572 08.12.2023 --- PAGE BREAK --- 2 Security This chapter covers: 2.1 Target group 10 2.2 General safety instructions 10 2.3 Meaning of written warning notices and hazard symbols 12 2.1 Target group The instructions in this documentation are directed at the following target group: Skilled Person: Skilled person is a term applied to persons who have training or experience in the equipment technology, particularly in knowing the various energies and energy magnitudes used in the equipment. Skilled persons are expected to use their training and experience to recognize energy sources capable of causing pain or injury and to take action for protection from injury from those energies. Skilled persons should also be protected against unintentional contact or exposure to energy sources capable of causing injury. Instructed Person: Instructed person is a term applied to persons who have been instructed and trained by a skilled person, or who are supervised by a skilled person, to identify energy sources that may cause pain and to take precautions to avoid unintentional contact with or exposure to those energy sources. Under normal operating conditions, abnormal operating conditions or single fault conditions, instructed persons should not be exposed to parts comprising energy sources capable of causing injury. 2.2 General safety instructions WARNING: Before starting to install and work with this device, read the Safety Instructions. This device shall only be connected to power supplies compliant to EN60950-1, chapter 2.5 (\"limited\npower source\"). 2.2.1 General information l Keep this document for later reference. l Always pass this document on together with the product. l Also consider any additional country-specific, local safety standards or regulations concerning project planning, operation, and disposal of the product. Liability claim © Vanderbilt 2023 l Do not connect the device to the 230V supply network if it is damaged or any parts are missing. l Do not make any changes or modifications to the device unless they are expressly mentioned in this manual and have been approved by the manufacturer. l Use only spare parts and accessories that have been approved by the manufacturer. 10 I-200572 08.12.2023 --- PAGE BREAK --- SPC42/52/53/63 – Installation & Configuration Manual Security 2.2.2 Transport Unit damage during transport l Keep the packaging material for future transportation. l Do not expose the device to mechanical vibrations or shocks. 2.2.3 Setup Radio interference with other devices in the environment/EMS l When handling modules that are susceptible to electrostatic discharge, observe the ESD guidelines. Damage due to unsuitable mounting location l The environmental conditions recommended by the manufacturer must be observed. See Technical Data on page 21. l Do not operate the device close to sources of powerful electromagnetic radiation. Danger of electrical shock due to incorrect connection l Connect the device only to power sources with the specified voltage. Voltage supply requirements can be found on the rating label of the device. l Ensure that the device is permanently connected to the electricity supply; a readily accessible disconnect device must be provided. l Ensure that the circuit that the device is connected to is protected with a 16A (max.) fuse. Do not connect any devices from other systems to this fuse. l This device is designed to work with TN power systems. Do not connect the device to any other power systems. l Electrical grounding must meet the customary local safety standards and regulations. l Primary supply cables and secondary cables should be routed such that they do not run in parallel or cross over or touch one another inside the housing. l Telephone cables should be fed into the unit separately from other cables. Risk of cable damage due to stress l Ensure that all outgoing cables and wires are sufficiently strain-relieved. 2.2.4 Operation Dangerous situation due to false alarm l Make sure to notify all relevant parties and authorities providing assistance before testing the system. l To avoid panic, always inform all those present before testing any alarm devices. 2.2.5 Service and maintenance Danger of electrical shock during maintenance l Maintenance work must only be carried out by trained specialists. l Always disconnect the power cable and other cables from the main power supply before performing maintenance. Danger of electrical shock while cleaning the device l © Vanderbilt 2023 Do not use liquid cleaners or sprays that contain alcohol, spirit or ammonia. 11 I-200572 08.12.2023 --- PAGE BREAK --- SPC42/52/53/63 – Installation & Configuration Manual Security 2.3 Meaning of written warning notices and hazard symbols 2.3.1 Warning notices Signal Word Type of Risk DANGER Danger of death or severe bodily harm. WARNING Possible danger of death or severe bodily harm. CAUTION Danger of minor bodily injury or property damage IMPORTANT Danger of malfunctions 2.3.2 Hazard symbols WARNING: Warning of hazard area WARNING: Warning of dangerous electrical voltage © Vanderbilt 2023 12 I-200572 08.12.2023 --- PAGE BREAK --- 3 Directives and standards This chapter covers: 3.1 EU directives 13 3.2 Overview of Conformity to EN50131 Standard 13 3.3 Compliance with VdS 2115:2015-12 18 3.4 Compliance with EN 50136-1:2012 and EN 50136-2:2014 19 3.5 Compliance with INCERT Approvals 19 3.6 Compliance with NF and A2P approvals including CYBER requirements - SPC Products 20 3.1 EU directives This product complies with the requirements of the European Directives 2004/108/EC “Directive of Electromagnetic Compatibility”, 2006/95/EC “Low Voltage Directive”, and1999/5/EC on Radio and Telecommunications Terminal Equipment (R&TTE). The EU declaration of conformity is available to the responsible agencies at http://pcd.vanderbiltindustries.com/doc/SPC European Directive 2004/108/EC “Electromagnetic Compatibility” Compliance with the European Directive 2004/108/EC has been proven by testing according to the following standards: emc emission EN 55022 Class B emc immunity EN 50130-4 European Directive 2006/95/EC “Low-Voltage Directive” Compliance with the European Directive 2006/95/EC has been proven by testing according to the following standard: Safety EN 60950-1 3.2 Overview of Conformity to EN50131 Standard This section gives an overview of the SPC compliance with the EN50131 Standard. The EN50131 Standard defines the requirements for Intrusion and Hold-up Alarm Systems. The SPC system is compliant with EN50131 Grade 2 and Grade 3, depending on the configuration. EN50131 Grade 2 Grade 2 systems are suitable for properties where the risk of theft is low to medium. These systems provide a good level of protection against intruders who have a limited knowledge of alarm systems. EN50131 Grade 3 Grade 3 systems are suitable for properties where the risk of theft is medium to high. These systems provide a high level of protection against intruders who have a good knowledge of alarm systems and may carry specialist tools. 3.3 Compliance with VdS 2115:2015-12 The SPC system is compliant with VdS 2115:2015-12, which defines the requirements for Intrusion and Hold-up Alarm Systems in Germany. 3.3.1 Compliance with EN50131 Approvals The SPC system has been approved by various certification bodies for compliance with EN50131 Standard. The following table provides an overview of the approvals: Certification Body Country Grade ATS Class VdS Germany 2, 3 ATS 2, 3 INCERT Belgium 2, 3 ATS 2, 3 NF France 2, 3 ATS 2, 3 A2P France 2, 3 ATS 2, 3 3.4 Compliance with EN 50136-1:2012 and EN 50136-2:2014 The SPC system is compliant with EN 50136-1:2012 and EN 50136-2:2014, which define the requirements for Alarm Transmission Systems. 3.5 Compliance with INCERT Approvals The SPC system has been approved by INCERT for compliance with EN50131 Standard. The following table provides an overview of the approvals: Certification Body Country Grade ATS Class INCERT Belgium 2, 3 ATS 2, 3 3.6 Compliance with NF and A2P approvals including CYBER requirements - SPC Products The SPC system has been approved by NF and A2P for compliance with EN50131 Standard. The following table provides an overview of the approvals: Certification Body Country Grade ATS Class NF France 2, 3 ATS 2, 3 A2P France 2, 3 ATS 2, 3 4 Technical Data 4.1 SPC Matrix The SPC system consists of various components, including control panels, keypads, expanders, and communication modules. The following table provides an overview of the SPC matrix: Component Model Number Description Control Panels SPC42xx 4-zone control panel SPC52xx 8-zone control panel SPC53xx 16-zone control panel SPC63xx 32-zone control panel Keypads SPCK420 LCD keypad SPCK421 LCD keypad with proximity reader SPCK520 Compact LCD keypad SPCK521 Compact LCD keypad with proximity reader SPCK620 Touchscreen keypad SPCK623 Touchscreen keypad with proximity reader Expanders SPCE452 8-output expander SPCE652 8-input 2-output expander Communication Modules SPCCOM100 PSTN communicator SPCCOM200 GSM/GPRS communicator SPCCOM300 IP communicator 5 Introduction The Vanderbilt SPC intrusion system is an IP enabled intrusion system that provides a wide range of intrusion functional for the needs of residential, commercial, and industrial applications. The SPC system offers a flexible and scalable solution for intrusion detection, access control, and video verification. 6 Mounting system equipment 6.1 Mounting a G2 housing 6.2 Mounting a G3 housing 6.2.1 Mounting a Back Tamper Kit 6.2.2 Battery installation for EN50131 compliance 6.3 Mounting a keypad 6.4 Mounting an expander 6.5 Wiring the X-BUS Interface 6.5.1 Wiring the Inputs 6.5.2 Wiring the Outputs 7 Controller hardware 7.1 Controller Hardware SPC42/SPC52/SPC53/SPC63 8 Door Expander 9 Wiring the system 9.1 Wiring the X-BUS interface 9.1.1 Loop configuration 9.1.2 Spur configuration 9.1.3 Star and multi-drop configuration 9.1.4 Shielding 9.1.5 Cable Map 9.2 Wiring of branch expander 9.3 Wiring the system ground 9.4 Wiring the relay output 9.5 Wiring the zone inputs 9.6 Wiring an external SAB bell 9.7 Wiring an internal sounder 9.8 Wiring Glassbreak 9.9 Installing plug-in modules 10 Powering up the SPC controller 10.1 Powering from battery only 11 Keypad user interface 11.1 SPCK420/421 11.1.1 About the LCD keypad 11.1.2 Using the LCD keypad interface 11.1.3 Data entry on the LCD keypad 12 Starting the system 12.1 Engineer modes 12.1.1 Engineer PINs 12.2 Programming with the keypad 12.3 Configuring start-up settings 12.4 Creating system users 12.5 Programming the portable PACE 12.6 Configuring wireless fob devices 12.6.1 Clearing alerts using the fob 13 Soft Engineer programming via the keypad 14 Engineer programming via the keypad 14.1 System Status 14.2 Options 14.3 Timers 14.4 Areas 14.5 Area Groups 14.6 X-BUS 14.6.1 X-BUS Addressing 14.6.2 XBUS Refresh 14.6.3 Reconfigure 14.6.4 Keypads/Expanders/Door Controllers 14.6.5 Addressing Mode 14.6.6 XBUS Type 14.6.7 Bus Retries 14.6.8 Comms Timer 14.7 Users 14.7.1 Add 14.7.2 Edit 14.7.3 Delete 14.8 User Profiles 14.8.1 Add 14.8.2 Edit 14.8.3 Delete 14.9 Wireless 14.9.1 Select a wireless programming option 14.9.2 Two way wireless 14.10 Zones 14.11 Doors 14.12 Outputs 14.12.1 Outputs types and output ports 14.13 Communication 14.13.1 Serial Ports 14.13.2 Ethernet Ports 14.13.3 Modems 14.13.4 Central Station 14.13.5 SPC Connect PRO 14.14 Test 14.14.1 Bell Test 14.14.2 Walk Test 14.14.3 Zone Monitor 14.14.4 Output Test 14.14.5 Soak Test 14.14.6 Audible Options 14.14.7 Visual Indicators 14.14.8 Seismic Test 14.15 Utilities 14.16 Isolate 14.17 Event Log 14.18 Access Log 14.19 Alarm Log 14.20 Change Engineer Pin 14.21 SMS 14.21.1 Add 14.21.2 Edit 14.21.3 Delete 14.22 Set Date/Time 14.23 Installer Text 14.24 Door Control 14.25 SPC Connect 15 Engineer programming via the browser 15.1 System Information 15.2 Ethernet interface 15.3 Connecting to the panel via USB 15.4 Logging into the browser 15.5 SPC Home 15.5.1 System Summary 15.5.2 Alarms Overview 15.5.3 Viewing Video 15.6 Panel status 15.6.1 Status 15.6.2 X-Bus Status 15.6.3 Wireless 15.6.4 Zones 15.6.5 Doors 15.6.6 FlexC Status 15.6.7 System alerts 15.7 Logs 15.7.1 System Log 15.7.2 Access Log 15.7.3 ALARM LOG 15.8 Users 15.8.1 Adding/Editing a User 15.8.2 Adding/Editing User Profiles 15.8.3 Configuring SMS 15.8.4 SMS Commands 15.8.5 Deleting Web Passwords 15.8.6 Configuring Engineer Settings 15.9 Wireless 15.9.1 Two way wireless 15.10 Configuration 15.10.1 Configuring controller inputs and outputs 15.10.2 X-BUS 15.10.3 Changing system settings 15.10.4 Configuring zones, doors and areas 15.10.5 Calendars 15.10.6 Change own PIN 15.10.7 Configuring advanced settings 15.11 Configuring Communications 15.11.1 Communications Settings 15.11.2 FlexC® 15.11.3 Reporting 15.11.4 PC Tools 15.12 File Operations 15.12.1 File Upgrade Operations 15.12.2 File Manager Operations 16 Accessing web server remotely 16.1 PSTN connection 17 Intruder alarm functionality 17.1 Financial mode operation 17.2 Commercial mode operation 17.3 Domestic mode operation 17.4 Full and local alarms 18 System examples and scenarios 18.1 When to use a common area 19 Seismic Sensors 19.1 Seismic Sensor Testing 19.1.1 Manual and Automatic Test Process 19.1.2 Automatically Testing Sensors 19.1.3 Manually Testing Sensors 20 Blocking Lock Operation 20.1 Blocking Lock 20.2 Authorized Setting of the Blocking Lock 20.3 Locking Element 21 Appendix 21.1 Network cable connections 21.2 Controller status LEDs 21.3 Powering expanders from the auxiliary power terminals 21.4 Calculating the battery power requirements 21.5 Domestic, Commercial and Financial mode default settings 21.6 SIA Codes 21.7 CID Codes 21.8 User PIN combinations 21.9 Duress PINs 21.10 Automatic inhibits 21.10.1 Zones 21.10.2 Access PINs 21.10.3 Engineer Access 21.10.4 Keypad User Logoff 21.11 Wiring of mains cable to the controller 21.12 Maintenance controller 21.13 Maintenance 21.14 Zone types 21.15 Zone attributes 21.16 ATS levels and attenuation specifications 21.17 Supported card readers and card formats 21.18 FlexC Glossary 21.19 FlexC Commands 21.20 ATS Category Timings 21.21 ATP Category Timings 22 Notes SPC Start-up Guide Version 3.6 © Vanderbilt International Ltd. 2016 Contents 1. Introduction 2. System Overview 3. Installation 4. Configuration 5. Operation 6. Maintenance 7. Troubleshooting 8. Appendix 1. Introduction This guide provides a step-by-step process for installing and configuring the Vanderbilt SPC intrusion system. It is intended for installers and technicians who are familiar with intrusion alarm systems and have a basic understanding of IP networking. 2. System Overview The Vanderbilt SPC intrusion system is a comprehensive security solution that combines intrusion detection, access control, and video verification into a single platform. The system is designed to meet the needs of various applications, from small residential properties to large commercial and industrial facilities. Key Features: • Integrated intrusion detection, access control, and video verification • IP-enabled for remote access and management • Scalable architecture to support various system sizes • User-friendly interface for easy operation and configuration • Compliance with international security standards System Components: • SPC control panel: The central processing unit of the system, responsible for managing all security functions. • Keypads: User interface devices for arming/disarming the system, entering PINs, and viewing system status. • Expanders: Modules that extend the system's capabilities by adding more zones, outputs, or other features. • Communication modules: Devices that enable communication with a central monitoring station or remote management software. • Sensors: Various types of detectors (e.g., motion sensors, door/window contacts, glassbreak detectors) that detect intrusion attempts. • Sirens: Audible warning devices that alert occupants and deter intruders. • Access control readers: Devices that grant or deny access to authorized individuals based on credentials (e.g., cards, PINs). • Cameras: Video surveillance devices that provide visual verification of events and activities. 3. Installation 3.1 Mounting the Control Panel 3.2 Wiring the System 3.2.1 Power Wiring 3.2.2 Zone Wiring 3.2.3 X-BUS Wiring 3.2.4 Output Wiring 3.3 Connecting Communication Modules 3.4 Connecting Keypads and Expanders 4. Configuration 4.1 Initial Setup Wizard 4.2 Programming Zones 4.3 Programming Users 4.4 Programming Outputs 4.5 Configuring Communication Settings 4.6 Configuring Access Control 4.7 Configuring Video Verification 5. Operation 5.1 Arming and Disarming the System 5.2 Managing Users 5.3 Viewing Event Logs 5.4 Responding to Alarms 6. Maintenance 6.1 System Diagnostics 6.2 Battery Replacement 6.3 Firmware Updates 7. Troubleshooting 7.1 Common Issues and Solutions 7.2 Fault Codes 8. Appendix 8.1 Technical Specifications 8.2 Wiring Diagrams 8.3 Default Settings 8.4 Compliance Information SPC Installation and Configuration Manual Version 3.13 © Vanderbilt International Ltd. 2024 Contents 1. Introduction 2. Safety Instructions 3. Directives and Standards 4. Technical Data 5. System Overview 6. Mounting the Control Panel 7. Wiring the System 7.1 Power Wiring 7.2 Zone Wiring 7.3 X-BUS Wiring 7.4 Output Wiring 8. Connecting Communication Modules 9. Connecting Keypads and Expanders 10. Initial Setup 10.1 Engineer PINs 10.2 Programming with the Keypad 10.3 Configuring Start-up Settings 10.4 Creating System Users 10.5 Programming Wireless Fob Devices 11. Engineer Programming via the Keypad 11.1 System Status 11.2 Options 11.3 Timers 11.4 Areas 11.5 Area Groups 11.6 X-BUS 11.6.1 X-BUS Addressing 11.6.2 XBUS Refresh 11.6.3 Reconfigure 11.6.4 Keypads/Expanders/Door Controllers 11.6.5 Addressing Mode 11.6.6 XBUS Type 11.6.7 Bus Retries 11.6.8 Comms Timer 11.7 Users 11.7.1 Add 11.7.2 Edit 11.7.3 Delete 11.8 User Profiles 11.8.1 Add 11.8.2 Edit 11.8.3 Delete 11.9 Wireless 11.9.1 Select a Wireless Programming Option 11.9.2 Two Way Wireless 11.10 Zones 11.11 Doors 11.12 Outputs 11.12.1 Output Types and Output Ports 11.13 Communication 11.13.1 Serial Ports 11.13.2 Ethernet Ports 11.13.3 Modems 11.13.4 Central Station 11.13.5 SPC Connect PRO 11.14 Test 11.14.1 Bell Test 11.14.2 Walk Test 11.14.3 Zone Monitor 11.14.4 Output Test 11.14.5 Soak Test 11.14.6 Audible Options 11.14.7 Visual Indicators 11.14.8 Seismic Test 11.15 Utilities 11.16 Isolate 11.17 Event Log 11.18 Access Log 11.19 Alarm Log 11.20 Change Engineer Pin 11.21 SMS 11.21.1 Add 11.21.2 Edit 11.21.3 Delete 11.22 Set Date/Time 11.23 Installer Text 11.24 Door Control 11.25 SPC Connect 12. Engineer Programming via the Browser 12.1 System Information 12.2 Ethernet Interface 12.3 Connecting to the Panel via USB 12.4 Logging into the Browser 12.5 SPC Home 12.5.1 System Summary 12.5.2 Alarms Overview 12.5.3 Viewing Video 12.6 Panel Status 12.6.1 Status 12.6.2 X-Bus Status 12.6.3 Wireless 12.6.4 Zones 12.6.5 Doors 12.6.6 FlexC Status 12.6.7 System Alerts 12.7 Logs 12.7.1 System Log 12.7.2 Access Log 12.7.3 Alarm Log 12.8 Users 12.8.1 Adding/Editing a User 12.8.2 Adding/Editing User Profiles 12.8.3 Configuring SMS 12.8.4 SMS Commands 12.8.5 Deleting Web Passwords 12.8.6 Configuring Engineer Settings 12.9 Wireless 12.9.1 Two Way Wireless 12.10 Configuration 12.10.1 Configuring Controller Inputs and Outputs 12.10.2 X-BUS 12.10.3 Changing System Settings 12.10.4 Configuring Zones, Doors and Areas 12.10.5 Calendars 12.10.6 Change Own PIN 12.10.7 Configuring Advanced Settings 12.11 Configuring Communications 12.11.1 Communications Settings 12.11.2 FlexC® 12.11.3 Reporting 12.11.4 PC Tools 12.12 File Operations 12.12.1 File Upgrade Operations 12.12.2 File Manager Operations 13. Accessing Web Server Remotely 13.1 PSTN Connection 14. Intruder Alarm Functionality 14.1 Financial Mode Operation 14.2 Commercial Mode Operation 14.3 Domestic Mode Operation 14.4 Full and Local Alarms 15. System Examples and Scenarios 15.1 When to Use a Common Area 16. Seismic Sensors 16.1 Seismic Sensor Testing 16.1.1 Manual and Automatic Test Process 16.1.2 Automatically Testing Sensors 16.1.3 Manually Testing Sensors 17. Blocking Lock Operation 17.1 Blocking Lock 17.2 Authorized Setting of the Blocking Lock 17.3 Locking Element 18. Appendix 18.1 Network Cable Connections 18.2 Controller Status LEDs 18.3 Powering Expanders from the Auxiliary Power Terminals 18.4 Calculating the Battery Power Requirements 18.5 Domestic, Commercial and Financial Mode Default Settings 18.6 SIA Codes 18.7 CID Codes 18.8 User PIN Combinations 18.9 Duress PINs 18.10 Automatic Inhibits 18.10.1 Zones 18.10.2 Access PINs 18.10.3 Engineer Access 18.10.4 Keypad User Logoff 18.11 Wiring of Mains Cable to the Controller 18.12 Maintenance Controller 18.13 Maintenance 18.14 Zone Types 18.15 Zone Attributes 18.16 ATS Levels and Attenuation Specifications 18.17 Supported Card Readers and Card Formats 18.18 FlexC Glossary 18.19 FlexC Commands 18.20 ATS Category Timings 18.21 ATP Category Timings 19. Notes SPC Installation and Configuration Manual Version 3.11 & 3.12 © Vanderbilt International Ltd. 2023 Contents 1. Introduction 2. Safety Instructions 3. Directives and Standards 4. Technical Data 5. System Overview 6. Mounting the Control Panel 7. Wiring the System 7.1 Power Wiring 7.2 Zone Wiring 7.3 X-BUS Wiring 7.4 Output Wiring 8. Connecting Communication Modules 9. Connecting Keypads and Expanders 10. Initial Setup 10.1 Engineer PINs 10.2 Programming with the Keypad 10.3 Configuring Start-up Settings 10.4 Creating System Users 10.5 Programming Wireless Fob Devices 11. Engineer Programming via the Keypad 11.1 System Status 11.2 Options 11.3 Timers 11.4 Areas 11.5 Area Groups 11.6 X-BUS 11.6.1 X-BUS Addressing 11.6.2 XBUS Refresh 11.6.3 Reconfigure 11.6.4 Keypads/Expanders/Door Controllers 11.6.5 Addressing Mode 11.6.6 XBUS Type 11.6.7 Bus Retries 11.6.8 Comms Timer 11.7 Users 11.7.1 Add 11.7.2 Edit 11.7.3 Delete 11.8 User Profiles 11.8.1 Add 11.8.2 Edit 11.8.3 Delete 11.9 Wireless 11.9.1 Select a Wireless Programming Option 11.9.2 Two Way Wireless 11.10 Zones 11.11 Doors 11.12 Outputs 11.12.1 Output Types and Output Ports 11.13 Communication 11.13.1 Serial Ports 11.13.2 Ethernet Ports 11.13.3 Modems 11.13.4 Central Station 11.13.5 SPC Connect PRO 11.14 Test 11.14.1 Bell Test 11.14.2 Walk Test 11.14.3 Zone Monitor 11.14.4 Output Test 11.14.5 Soak Test 11.14.6 Audible Options 11.14.7 Visual Indicators 11.14.8 Seismic Test 11.15 Utilities 11.16 Isolate 11.17 Event Log 11.18 Access Log 11.19 Alarm Log 11.20 Change Engineer Pin 11.21 SMS 11.21.1 Add 11.21.2 Edit 11.21.3 Delete 11.22 Set Date/Time 11.23 Installer Text 11.24 Door Control 11.25 SPC Connect 12. Engineer Programming via the Browser 12.1 System Information 12.2 Ethernet Interface 12.3 Connecting to the Panel via USB 12.4 Logging into the Browser 12.5 SPC Home 12.5.1 System Summary 12.5.2 Alarms Overview 12.5.3 Viewing Video 12.6 Panel Status 12.6.1 Status 12.6.2 X-Bus Status 12.6.3 Wireless 12.6.4 Zones 12.6.5 Doors 12.6.6 FlexC Status 12.6.7 System Alerts 12.7 Logs 12.7.1 System Log 12.7.2 Access Log 12.7.3 Alarm Log 12.8 Users 12.8.1 Adding/Editing a User 12.8.2 Adding/Editing User Profiles 12.8.3 Configuring SMS 12.8.4 SMS Commands 12.8.5 Deleting Web Passwords 12.8.6 Configuring Engineer Settings 12.9 Wireless 12.9.1 Two Way Wireless 12.10 Configuration 12.10.1 Configuring Controller Inputs and Outputs 12.10.2 X-BUS 12.10.3 Changing System Settings 12.10.4 Configuring Zones, Doors and Areas 12.10.5 Calendars 12.10.6 Change Own PIN 12.10.7 Configuring Advanced Settings 12.11 Configuring Communications 12.11.1 Communications Settings 12.11.2 FlexC® 12.11.3 Reporting 12.11.4 PC Tools 12.12 File Operations 12.12.1 File Upgrade Operations 12.12.2 File Manager Operations 13. Accessing Web Server Remotely 13.1 PSTN Connection 14. Intruder Alarm Functionality 14.1 Financial Mode Operation 14.2 Commercial Mode Operation 14.3 Domestic Mode Operation 14.4 Full and Local Alarms 15. System Examples and Scenarios 15.1 When to Use a Common Area 16. Seismic Sensors 16.1 Seismic Sensor Testing 16.1.1 Manual and Automatic Test Process 16.1.2 Automatically Testing Sensors 16.1.3 Manually Testing Sensors 17. Blocking Lock Operation 17.1 Blocking Lock 17.2 Authorized Setting of the Blocking Lock 17.3 Locking Element 18. Appendix 18.1 Network Cable Connections 18.2 Controller Status LEDs 18.3 Powering Expanders from the Auxiliary Power Terminals 18.4 Calculating the Battery Power Requirements 18.5 Domestic, Commercial and Financial Mode Default Settings 18.6 SIA Codes 18.7 CID Codes 18.8 User PIN Combinations 18.9 Duress PINs 18.10 Automatic Inhibits 18.10.1 Zones 18.10.2 Access PINs 18.10.3 Engineer Access 18.10.4 Keypad User Logoff 18.11 Wiring of Mains Cable to the Controller 18.12 Maintenance Controller 18.13 Maintenance 18.14 Zone Types 18.15 Zone Attributes 18.16 ATS Levels and Attenuation Specifications 18.17 Supported Card Readers and Card Formats 18.18 FlexC Glossary 18.19 FlexC Commands 18.20 ATS Category Timings 18.21 ATP Category Timings 19. Notes SPC Installation and Configuration Manual Version 3.8.5 © Vanderbilt International Ltd. 2023 Contents 1. Introduction 2. Safety Instructions 3. Directives and Standards 4. Technical Data 5. System Overview 6. Mounting the Control Panel 7. Wiring the System 7.1 Power Wiring 7.2 Zone Wiring 7.3 X-BUS Wiring 7.4 Output Wiring 8. Connecting Communication Modules 9. Connecting Keypads and Expanders 10. Initial Setup 10.1 Engineer PINs 10.2 Programming with the Keypad 10.3 Configuring Start-up Settings 10.4 Creating System Users 10.5 Programming Wireless Fob Devices 11. Engineer Programming via the Keypad 11.1 System Status 11.2 Options 11.3 Timers 11.4 Areas 11.5 Area Groups 11.6 X-BUS 11.6.1 X-BUS Addressing 11.6.2 XBUS Refresh 11.6.3 Reconfigure 11.6.4 Keypads/Expanders/Door Controllers 11.6.5 Addressing Mode 11.6.6 XBUS Type 11.6.7 Bus Retries 11.6.8 Comms Timer 11.7 Users 11.7.1 Add 11.7.2 Edit 11.7.3 Delete 11.8 User Profiles 11.8.1 Add 11.8.2 Edit 11.8.3 Delete 11.9 Wireless 11.9.1 Select a Wireless Programming Option 11.9.2 Two Way Wireless 11.10 Zones 11.11 Doors 11.12 Outputs 11.12.1 Output Types and Output Ports 11.13 Communication 11.13.1 Serial Ports 11.13.2 Ethernet Ports 11.13.3 Modems 11.13.4 Central Station 11.13.5 SPC Connect PRO 11.14 Test 11.14.1 Bell Test 11.14.2 Walk Test 11.14.3 Zone Monitor 11.14.4 Output Test 11.14.5 Soak Test 11.14.6 Audible Options 11.14.7 Visual Indicators 11.14.8 Seismic Test 11.15 Utilities 11.16 Isolate 11.17 Event Log 11.18 Access Log 11.19 Alarm Log 11.20 Change Engineer Pin 11.21 SMS 11.21.1 Add 11.21.2 Edit 11.21.3 Delete 11.22 Set Date/Time 11.23 Installer Text 11.24 Door Control 11.25 SPC Connect 12. Engineer Programming via the Browser 12.1 System Information 12.2 Ethernet Interface 12.3 Connecting to the Panel via USB 12.4 Logging into the Browser 12.5 SPC Home 12.5.1 System Summary 12.5.2 Alarms Overview 12.5.3 Viewing Video 12.6 Panel Status 12.6.1 Status 12.6.2 X-Bus Status 12.6.3 Wireless 12.6.4 Zones 12.6.5 Doors 12.6.6 FlexC Status 12.6.7 System Alerts 12.7 Logs 12.7.1 System Log 12.7.2 Access Log 12.7.3 Alarm Log 12.8 Users 12.8.1 Adding/Editing a User 12.8.2 Adding/Editing User Profiles 12.8.3 Configuring SMS 12.8.4 SMS Commands 12.8.5 Deleting Web Passwords 12.8.6 Configuring Engineer Settings 12.9 Wireless 12.9.1 Two Way Wireless 12.10 Configuration 12.10.1 Configuring Controller Inputs and Outputs 12.10.2 X-BUS 12.10.3 Changing System Settings 12.10.4 Configuring Zones, Doors and Areas 12.10.5 Calendars 12.10.6 Change Own PIN 12.10.7 Configuring Advanced Settings 12.11 Configuring Communications 12.11.1 Communications Settings 12.11.2 FlexC® 12.11.3 Reporting 12.11.4 PC Tools 12.12 File Operations 12.12.1 File Upgrade Operations 12.12.2 File Manager Operations 13. Accessing Web Server Remotely 13.1 PSTN Connection 14. Intruder Alarm Functionality 14.1 Financial Mode Operation 14.2 Commercial Mode Operation 14.3 Domestic Mode Operation 14.4 Full and Local Alarms 15. System Examples and Scenarios 15.1 When to Use a Common Area 16. Seismic Sensors 16.1 Seismic Sensor Testing 16.1.1 Manual and Automatic Test Process 16.1.2 Automatically Testing Sensors 16.1.3 Manually Testing Sensors 17. Blocking Lock Operation 17.1 Blocking Lock 17.2 Authorized Setting of the Blocking Lock 17.3 Locking Element 18. Appendix 18.1 Network Cable Connections 18.2 Controller Status LEDs 18.3 Powering Expanders from the Auxiliary Power Terminals 18.4 Calculating the Battery Power Requirements 18.5 Domestic, Commercial and Financial Mode Default Settings 18.6 SIA Codes 18.7 CID Codes 18.8 User PIN Combinations 18.9 Duress PINs 18.10 Automatic Inhibits 18.10.1 Zones 18.10.2 Access PINs 18.10.3 Engineer Access 18.10.4 Keypad User Logoff 18.11 Wiring of Mains Cable to the Controller 18.12 Maintenance Controller 18.13 Maintenance 18.14 Zone Types 18.15 Zone Attributes 18.16 ATS Levels and Attenuation Specifications 18.17 Supported Card Readers and Card Formats 18.18 FlexC Glossary 18.19 FlexC Commands 18.20 ATS Category Timings 18.21 ATP Category Timings 19. Notes SPC Installation and Configuration Manual Version 3.11 & 3.12 © Vanderbilt International Ltd. 2023 Contents 1. Introduction 2. Safety Instructions 3. Directives and Standards 4. Technical Data 5. System Overview 6. Mounting the Control Panel 7. Wiring the System 7.1 Power Wiring 7.2 Zone Wiring 7.3 X-BUS Wiring 7.4 Output Wiring 8. Connecting Communication Modules 9. Connecting Keypads and Expanders 10. Initial Setup 10.1 Engineer PINs 10.2 Programming with the Keypad 10.3 Configuring Start-up Settings 10.4 Creating System Users 10.5 Programming Wireless Fob Devices 11. Engineer Programming via the Keypad 11.1 System Status 11.2 Options 11.3 Timers 11.4 Areas 11.5 Area Groups 11.6 X-BUS 11.6.1 X-BUS Addressing 11.6.2 XBUS Refresh 11.6.3 Reconfigure 11.6.4 Keypads/Expanders/Door Controllers 11.6.5 Addressing Mode 11.6.6 XBUS Type 11.6.7 Bus Retries 11.6.8 Comms Timer 11.7 Users 11.7.1 Add 11.7.2 Edit 11.7.3 Delete 11.8 User Profiles 11.8.1 Add 11.8.2 Edit 11.8.3 Delete 11.9 Wireless 11.9.1 Select a Wireless Programming Option 11.9.2 Two Way Wireless 11.10 Zones 11.11 Doors 11.12 Outputs 11.12.1 Output Types and Output Ports 11.13 Communication 11.13.1 Serial Ports 11.13.2 Ethernet Ports 11.13.3 Modems 11.13.4 Central Station 11.13.5 SPC Connect PRO 11.14 Test 11.14.1 Bell Test 11.14.2 Walk Test 11.14.3 Zone Monitor 11.14.4 Output Test 11.14.5 Soak Test 11.14.6 Audible Options 11.14.7 Visual Indicators 11.14.8 Seismic Test 11.15 Utilities 11.16 Isolate 11.17 Event Log 11.18 Access Log 11.19 Alarm Log 11.20 Change Engineer Pin 11.21 SMS 11.21.1 Add 11.21.2 Edit 11.21.3 Delete 11.22 Set Date/Time 11.23 Installer Text 11.24 Door Control 11.25 SPC Connect 12. Engineer Programming via the Browser 12.1 System Information 12.2 Ethernet Interface 12.3 Connecting to the Panel via USB 12.4 Logging into the Browser 12.5 SPC Home 12.5.1 System Summary 12.5.2 Alarms Overview 12.5.3 Viewing Video 12.6 Panel Status 12.6.1 Status 12.6.2 X-Bus Status 12.6.3 Wireless 12.6.4 Zones 12.6.5 Doors 12.6.6 FlexC Status 12.6.7 System Alerts 12.7 Logs 12.7.1 System Log 12.7.2 Access Log 12.7.3 Alarm Log 12.8 Users 12.8.1 Adding/Editing a User 12.8.2 Adding/Editing User Profiles 12.8.3 Configuring SMS 12.8.4 SMS Commands 12.8.5 Deleting Web Passwords 12.8.6 Configuring Engineer Settings 12.9 Wireless 12.9.1 Two Way Wireless 12.10 Configuration 12.10.1 Configuring Controller Inputs and Outputs 12.10.2 X-BUS 12.10.3 Changing System Settings 12.10.4 Configuring Zones, Doors and Areas 12.10.5 Calendars 12.10.6 Change Own PIN 12.10.7 Configuring Advanced Settings 12.11 Configuring Communications 12.11.1 Communications Settings 12.11.2 FlexC® 12.11.3 Reporting 12.11.4 PC Tools 12.12 File Operations 12.12.1 File Upgrade Operations 12.12.2 File Manager Operations 13. Accessing Web Server Remotely 13.1 PSTN Connection 14. Intruder Alarm Functionality 14.1 Financial Mode Operation 14.2 Commercial Mode Operation 14.3 Domestic Mode Operation 14.4 Full and Local Alarms 15. System Examples and Scenarios 15.1 When to Use a Common Area 16. Seismic Sensors 16.1 Seismic Sensor Testing 16.1.1 Manual and Automatic Test Process 16.1.2 Automatically Testing Sensors 16.1.3 Manually Testing Sensors 17. Blocking Lock Operation 17.1 Blocking Lock 17.2 Authorized Setting of the Blocking Lock 17.3 Locking Element 18. Appendix 18.1 Network Cable Connections 18.2 Controller Status LEDs 18.3 Powering Expanders from the Auxiliary Power Terminals 18.4 Calculating the Battery Power Requirements 18.5 Domestic, Commercial and Financial Mode Default Settings 18.6 SIA Codes 18.7 CID Codes 18.8 User PIN Combinations 18.9 Duress PINs 18.10 Automatic Inhibits 18.10.1 Zones 18.10.2 Access PINs 18.10.3 Engineer Access 18.10.4 Keypad User Logoff 18.11 Wiring of Mains Cable to the Controller 18.12 Maintenance Controller 18.13 Maintenance 18.14 Zone Types 18.15 Zone Attributes 18.16 ATS Levels and Attenuation Specifications 18.17 Supported Card Readers and Card Formats 18.18 FlexC Glossary 18.19 FlexC Commands 18.20 ATS Category Timings 18.21 ATP Category Timings 19. Notes SPC Installation and Configuration Manual Version 3.8.5 © Vanderbilt International Ltd. 2023 Contents 1. Introduction 2. Safety Instructions 3. Directives and Standards 4. Technical Data 5. System Overview 6. Mounting the Control Panel 7. Wiring the System 7.1 Power Wiring 7.2 Zone Wiring 7.3 X-BUS Wiring 7.4 Output Wiring 8. Connecting Communication Modules 9. Connecting Keypads and Expanders 10. Initial Setup 10.1 Engineer PINs 10.2 Programming with the Keypad 10.3 Configuring Start-up Settings 10.4 Creating System Users 10.5 Programming Wireless Fob Devices 11. Engineer Programming via the Keypad 11.1 System Status 11.2 Options 11.3 Timers 11.4 Areas 11.5 Area Groups 11.6 X-BUS 11.6.1 X-BUS Addressing 11.6.2 XBUS Refresh 11.6.3 Reconfigure 11.6.4 Keypads/Expanders/Door Controllers 11.6.5 Addressing Mode 11.6.6 XBUS Type 11.6.7 Bus Retries 11.6.8 Comms Timer 11.7 Users 11.7.1 Add 11.7.2 Edit 11.7.3 Delete 11.8 User Profiles 11.8.1 Add 11.8.2 Edit 11.8.3 Delete 11.9 Wireless 11.9.1 Select a Wireless Programming Option 11.9.2 Two Way Wireless 11.10 Zones 11.11 Doors 11.12 Outputs 11.12.1 Output Types and Output Ports 11.13 Communication 11.13.1 Serial Ports 11.13.2 Ethernet Ports 11.13.3 Modems 11.13.4 Central Station 11.13.5 SPC Connect PRO 11.14 Test 11.14.1 Bell Test 11.14.2 Walk Test 11.14.3 Zone Monitor 11.14.4 Output Test 11.14.5 Soak Test 11.14.6 Audible Options 11.14.7 Visual Indicators 11.14.8 Seismic Test 11.15 Utilities 11.16 Isolate 11.17 Event Log 11.18 Access Log 11.19 Alarm Log 11.20 Change Engineer Pin 11.21 SMS 11.21.1 Add 11.21.2 Edit 11.21.3 Delete 11.22 Set Date/Time 11.23 Installer Text 11.24 Door Control 11.25 SPC Connect 12. Engineer Programming via the Browser 12.1 System Information 12.2 Ethernet Interface 12.3 Connecting to the Panel via USB 12.4 Logging into the Browser 12.5 SPC Home 12.5.1 System Summary 12.5.2 Alarms Overview 12.5.3 Viewing Video 12.6 Panel Status 12.6.1 Status 12.6.2 X-Bus Status 12.6.3 Wireless 12.6.4 Zones 12.6.5 Doors 12.6.6 FlexC Status 12.6.7 System Alerts 12.7 Logs 12.7.1 System Log 12.7.2 Access Log 12.7.3 Alarm Log 12.8 Users 12.8.1 Adding/Editing a User 12.8.2 Adding/Editing User Profiles 12.8.3 Configuring SMS 12.8.4 SMS Commands 12.8.5 Deleting Web Passwords 12.8.6 Configuring Engineer Settings 12.9 Wireless 12.9.1 Two Way Wireless 12.10 Configuration 12.10.1 Configuring Controller Inputs and Outputs 12.10.2 X-BUS 12.10.3 Changing System Settings 12.10.4 Configuring Zones, Doors and Areas 12.10.5 Calendars 12.10.6 Change Own PIN 12.10.7 Configuring Advanced Settings 12.11 Configuring Communications 12.11.1 Communications Settings 12.11.2 FlexC® 12.11.3 Reporting 12.11.4 PC Tools 12.12 File Operations 12.12.1 File Upgrade Operations 12.12.2 File Manager Operations 13. Accessing Web Server Remotely 13.1 PSTN Connection 14. Intruder Alarm Functionality 14.1 Financial Mode Operation 14.2 Commercial Mode Operation 14.3 Domestic Mode Operation 14.4 Full and Local Alarms 15. System Examples and Scenarios 15.1 When to Use a Common Area 16. Seismic Sensors 16.1 Seismic Sensor Testing 16.1.1 Manual and Automatic Test Process 16.1.2 Automatically Testing Sensors 16.1.3 Manually Testing Sensors 17. Blocking Lock Operation 17.1 Blocking Lock 17.2 Authorized Setting of the Blocking Lock 17.3 Locking Element 18. Appendix 18.1 Network Cable Connections 18.2 Controller Status LEDs 18.3 Powering Expanders from the Auxiliary Power Terminals 18.4 Calculating the Battery Power Requirements 18.5 Domestic, Commercial and Financial Mode Default Settings 18.6 SIA Codes 18.7 CID Codes 18.8 User PIN Combinations 18.9 Duress PINs 18.10 Automatic Inhibits 18.10.1 Zones 18.10.2 Access PINs 18.10.3 Engineer Access 18.10.4 Keypad User Logoff 18.11 Wiring of Mains Cable to the Controller 18.12 Maintenance Controller 18.13 Maintenance 18.14 Zone Types 18.15 Zone Attributes 18.16 ATS Levels and Attenuation Specifications 18.17 Supported Card Readers and Card Formats 18.18 FlexC Glossary 18.19 FlexC Commands 18.20 ATS Category Timings 18.21 ATP Category Timings 19. Notes === WEB RESEARCH: spc === SPC42, SPC52, SPC53, SPC63 Installation & Configuration Manual Document ID: I-200572 Edition date: 08.12.2023 --- PAGE BREAK --- Data and design subject to change without notice. / Supply subject to availability. © 2023 Copyright by Vanderbilt International Ltd. We reserve all rights in this document and in the subject thereof. By acceptance of the document the recipient acknowledges these rights and undertakes not to publish the document nor the subject thereof in full or in part, nor to make them available to any third party without our prior express written authorization, nor to use it for any purpose other than for which it was delivered to him. --- PAGE BREAK --- Table of Contents 1 Meaning of symbols 9 2 Security 10 2.1 Target group 10 2.2 General safety instructions 10 2.2.1 General information 10 2.2.2 Transport 11 2.2.3 Setup 11 2.2.4 Operation 11 2.2.5 Service and maintenance 11 2.3 Meaning of written warning notices and hazard symbols 12 2.3.1 Warning notices 12 2.3.2 Hazard symbols 12 3 Directives and standards 13 3.1 EU directives 13 3.2 Overview of Conformity to EN50131 Standard 13 3.3 Compliance with VdS 2115:2015-12 18 3.3.1 Compliance with EN50131 Approvals 18 3.4 Compliance with EN 50136-1:2012 and EN 50136-2:2014 19 3.5 Compliance with INCERT Approvals 19 3.6 Compliance with NF and A2P approvals including CYBER requirements - SPC Products 20 4 Technical Data 21 4.1 SPC Matrix 21 5 Introduction 22 6 Mounting system equipment 23 6.1 Mounting a G2 housing 23 6.2 Mounting a G3 housing 23 6.2.1 Mounting a Back Tamper Kit 24 6.2.2 Battery installation for EN50131 compliance 27 6.3 Mounting a keypad 28 6.4 Mounting an expander 28 6.5 Wiring the X-BUS Interface 28 6.5.1 Wiring the Inputs 29 6.5.2 Wiring the Outputs 30 7 Controller hardware 31 7.1 Controller Hardware SPC42/SPC52/SPC53/SPC63 31 8 Door Expander 34 9 Wiring the system 35 © Vanderbilt 2023 3 I-200572 08.12.2023 --- PAGE BREAK --- SPC42/52/53/63 – Installation & Configuration Manual Table of Contents 9.1 Wiring the X-BUS interface 35 9.1.1 Loop configuration 36 9.1.2 Spur configuration 37 9.1.3 Star and multi-drop configuration 38 9.1.4 Shielding 43 9.1.5 Cable Map 43 9.2 Wiring of branch expander 43 9.3 Wiring the system ground 44 9.4 Wiring the relay output 44 9.5 Wiring the zone inputs 45 9.6 Wiring an external SAB bell 48 9.7 Wiring an internal sounder 48 9.8 Wiring Glassbreak 49 9.9 Installing plug-in modules 49 10 Powering up the SPC controller 51 10.1 Powering from battery only 51 11 Keypad user interface 52 11.1 SPCK420/421 52 11.1.1 About the LCD keypad 52 11.1.2 Using the LCD keypad interface 54 11.1.3 Data entry on the LCD keypad 57 12 Starting the system 59 12.1 Engineer modes 59 12.1.1 Engineer PINs 59 12.2 Programming with the keypad 59 12.3 Configuring start-up settings 60 12.4 Creating system users 61 12.5 Programming the portable PACE 62 12.6 Configuring wireless fob devices 63 12.6.1 Clearing alerts using the fob 63 13 Soft Engineer programming via the keypad 65 14 Engineer programming via the keypad 66 14.1 System Status 66 14.2 Options 67 14.3 Timers 71 14.4 Areas 75 14.5 Area Groups 77 14.6 X-BUS 77 14.6.1 X-BUS Addressing © Vanderbilt 2023 77 4 I-200572 08.12.2023 --- PAGE BREAK --- SPC42/52/53/63 – Installation & Configuration Manual Table of Contents 14.6.2 XBUS Refresh 77 14.6.3 Reconfigure 78 14.6.4 Keypads/Expanders/Door Controllers 78 14.6.5 Addressing Mode 87 14.6.6 XBUS Type 88 14.6.7 Bus Retries 88 14.6.8 Comms Timer 88 14.7 Users 88 14.7.1 Add 88 14.7.2 Edit 89 14.7.3 Delete 91 14.8 User Profiles 92 14.8.1 Add 92 14.8.2 Edit 92 14.8.3 Delete 92 14.9 Wireless 92 14.9.1 Select a wireless programming option 93 14.9.2 Two way wireless 95 14.10 Zones 99 14.11 Doors 99 14.12 Outputs 103 14.12.1 Outputs types and output ports 104 14.13 Communication 108 14.13.1 Serial Ports 108 14.13.2 Ethernet Ports 108 14.13.3 Modems 109 14.13.4 Central Station 111 14.13.5 SPC Connect PRO 113 14.14 Test 113 14.14.1 Bell Test 113 14.14.2 Walk Test 113 14.14.3 Zone Monitor 114 14.14.4 Output Test 115 14.14.5 Soak Test 115 14.14.6 Audible Options 115 14.14.7 Visual Indicators 115 14.14.8 Seismic Test 116 14.15 Utilities 116 14.16 Isolate 116 © Vanderbilt 2023 5 I-200572 08.12.2023 --- PAGE BREAK --- SPC42/52/53/63 – Installation & Configuration Manual Table of Contents 14.17 Event Log 117 14.18 Access Log 117 14.19 Alarm Log 117 14.20 Change Engineer Pin 118 14.21 SMS 118 14.21.1 Add 119 14.21.2 Edit 119 14.21.3 Delete 120 14.22 Set Date/Time 120 14.23 Installer Text 120 14.24 Door Control 121 14.25 SPC Connect 121 15 Engineer programming via the browser 122 15.1 System Information 122 15.2 Ethernet interface 122 15.3 Connecting to the panel via USB 124 15.4 Logging into the browser 124 15.5 SPC Home 125 15.5.1 System Summary 125 15.5.2 Alarms Overview 126 15.5.3 Viewing Video 126 15.6 Panel status 127 15.6.1 Status 127 15.6.2 X-Bus Status 127 15.6.3 Wireless 132 15.6.4 Zones 134 15.6.5 Doors 135 15.6.6 FlexC Status 136 15.6.7 System alerts 137 15.7 Logs 137 15.7.1 System Log 137 15.7.2 Access Log 138 15.7.3 ALARM LOG 138 15.8 Users © Vanderbilt 2023 138 15.8.1 Adding/Editing a User 139 15.8.2 Adding/Editing User Profiles 141 15.8.3 Configuring SMS 144 15.8.4 SMS Commands 145 15.8.5 Deleting Web Passwords 147 6 I-200572 08.12.2023 --- PAGE BREAK --- SPC42/52/53/63 – Installation & Configuration Manual Table of Contents 15.8.6 Configuring Engineer Settings 147 15.9 Wireless 149 15.9.1 Two way wireless 150 15.10 Configuration 154 15.10.1 Configuring controller inputs and outputs 154 15.10.2 X-BUS 160 15.10.3 Changing system settings 169 15.10.4 Configuring zones, doors and areas 185 15.10.5 Calendars 197 15.10.6 Change own PIN 199 15.10.7 Configuring advanced settings 200 15.11 Configuring Communications 208 15.11.1 Communications Settings 208 15.11.2 FlexC® 215 15.11.3 Reporting 235 15.11.4 PC Tools 243 15.12 File Operations 244 15.12.1 File Upgrade Operations 245 15.12.2 File Manager Operations 247 16 Accessing web server remotely 249 16.1 PSTN connection 249 17 Intruder alarm functionality 251 17.1 Financial mode operation 251 17.2 Commercial mode operation 251 17.3 Domestic mode operation 252 17.4 Full and local alarms 252 18 System examples and scenarios 254 18.1 When to use a common area 254 19 Seismic Sensors 256 19.1 Seismic Sensor Testing 256 19.1.1 Manual and Automatic Test Process 256 19.1.2 Automatically Testing Sensors 257 19.1.3 Manually Testing Sensors 258 20 Blocking Lock Operation 260 20.1 Blocking Lock 260 20.2 Authorized Setting of the Blocking Lock 261 20.3 Locking Element 262 21 Appendix 264 21.1 Network cable connections © Vanderbilt 2023 264 7 I-200572 08.12.2023 --- PAGE BREAK --- SPC42/52/53/63 – Installation & Configuration Manual Table of Contents 21.2 Controller status LEDs 265 21.3 Powering expanders from the auxiliary power terminals 265 21.4 Calculating the battery power requirements 266 21.5 Domestic, Commercial and Financial mode default settings 267 21.6 SIA Codes 267 21.7 CID Codes 273 21.8 User PIN combinations 275 21.9 Duress PINs 275 21.10 Automatic inhibits 275 21.10.1 Zones 275 21.10.2 Access PINs 276 21.10.3 Engineer Access 276 21.10.4 Keypad User Logoff 276 21.11 Wiring of mains cable to the controller 276 21.12 Maintenance controller 276 21.13 Maintenance 277 21.14 Zone types 278 21.15 Zone attributes 283 21.16 ATS levels and attenuation specifications 285 21.17 Supported card readers and card formats 286 21.18 FlexC Glossary 288 21.19 FlexC Commands 289 21.20 ATS Category Timings 292 21.21 ATP Category Timings 293 22 Notes © Vanderbilt 2023 295 8 I-200572 08.12.2023 --- PAGE BREAK --- 1 Meaning of symbols There are several symbols in the document: Symbol Description Only available for SPC controller with IP interface (SPC43/SPC52/SPC53/SPC63). Not available for installation type Domestic. Only available in unrestricted mode. Find further information about Security Grade, Region, or Mode in text. See Appendix for further information. © Vanderbilt 2023 9 I-200572 08.12.2023 --- PAGE BREAK --- 2 Security This chapter covers: 2.1 Target group 10 2.2 General safety instructions 10 2.3 Meaning of written warning notices and hazard symbols 12 2.1 Target group The instructions in this documentation are directed at the following target group: Skilled Person: Skilled person is a term applied to persons who have training or experience in the equipment technology, particularly in knowing the various energies and energy magnitudes used in the equipment. Skilled persons are expected to use their training and experience to recognize energy sources capable of causing pain or injury and to take action for protection from injury from those energies. Skilled persons should also be protected against unintentional contact or exposure to energy sources capable of causing injury. Instructed Person: Instructed person is a term applied to persons who have been instructed and trained by a skilled person, or who are supervised by a skilled person, to identify energy sources that may cause pain and to take precautions to avoid unintentional contact with or exposure to those energy sources. Under normal operating conditions, abnormal operating conditions or single fault conditions, instructed persons should not be exposed to parts comprising energy sources capable of causing injury. 2.2 General safety instructions WARNING: Before starting to install and work with this device, read the Safety Instructions. This device shall only be connected to power supplies compliant to EN60950-1, chapter 2.5 (\"limited\npower source\"). 2.2.1 General information l Keep this document for later reference. l Always pass this document on together with the product. l Also consider any additional country-specific, local safety standards or regulations concerning project planning, operation, and disposal of the product. Liability claim © Vanderbilt 2023 l Do not connect the device to the 230V supply network if it is damaged or any parts are missing. l Do not make any changes or modifications to the device unless they are expressly mentioned in this manual and have been approved by the manufacturer. l Use only spare parts and accessories that have been approved by the manufacturer. 10 I-200572 08.12.2023 --- PAGE BREAK --- SPC42/52/53/63 – Installation & Configuration Manual Security 2.2.2 Transport Unit damage during transport l Keep the packaging material for future transportation. l Do not expose the device to mechanical vibrations or shocks. 2.2.3 Setup Radio interference with other devices in the environment/EMS l When handling modules that are susceptible to electrostatic discharge, observe the ESD guidelines. Damage due to unsuitable mounting location l The environmental conditions recommended by the manufacturer must be observed. See Technical Data on page 21. l Do not operate the device close to sources of powerful electromagnetic radiation. Danger of electrical shock due to incorrect connection l Connect the device only to power sources with the specified voltage. Voltage supply requirements can be found on the rating label of the device. l Ensure that the device is permanently connected to the electricity supply; a readily accessible disconnect device must be provided. l Ensure that the circuit that the device is connected to is protected with a 16A (max.) fuse. Do not connect any devices from other systems to this fuse. l This device is designed to work with TN power systems. Do not connect the device to any other power systems. l Electrical grounding must meet the customary local safety standards and regulations. l Primary supply cables and secondary cables should be routed such that they do not run in parallel or cross over or touch one another inside the housing. l Telephone cables should be fed into the unit separately from other cables. Risk of cable damage due to stress l Ensure that all outgoing cables and wires are sufficiently strain-relieved. 2.2.4 Operation Dangerous situation due to false alarm l Make sure to notify all relevant parties and authorities providing assistance before testing the system. l To avoid panic, always inform all those present before testing any alarm devices. 2.2.5 Service and maintenance Danger of electrical shock during maintenance l Maintenance work must only be carried out by trained specialists. l Always disconnect the power cable and other cables from the main power supply before performing maintenance. Danger of electrical shock while cleaning the device l © Vanderbilt 2023 Do not use liquid cleaners or sprays that contain alcohol, spirit or ammonia. 11 I-200572 08.12.2023 --- PAGE BREAK --- SPC42/52/53/63 – Installation & Configuration Manual Security 2.3 Meaning of written warning notices and hazard symbols 2.3.1 Warning notices Signal Word Type of Risk DANGER Danger of death or severe bodily harm. WARNING Possible danger of death or severe bodily harm. CAUTION Danger of minor bodily injury or property damage IMPORTANT Danger of malfunctions 2.3.2 Hazard symbols WARNING: Warning of hazard area WARNING: Warning of dangerous electrical voltage © Vanderbilt 2023 12 I-200572 08.12.2023 --- PAGE BREAK --- 3 Directives and standards This chapter covers: 3.1 EU directives 13 3.2 Overview of Conformity to EN50131 Standard 13 3.3 Compliance with VdS 2115:2015-12 18 3.4 Compliance with EN 50136-1:2012 and EN 50136-2:2014 19 3.5 Compliance with INCERT Approvals 19 3.6 Compliance with NF and A2P approvals including CYBER requirements - SPC Products 20 3.1 EU directives This product complies with the requirements of the European Directives 2004/108/EC “Directive of Electromagnetic Compatibility”, 2006/95/EC “Low Voltage Directive”, and1999/5/EC on Radio and Telecommunications Terminal Equipment (R&TTE). The EU declaration of conformity is available to the responsible agencies at http://pcd.vanderbiltindustries.com/doc/SPC European Directive 2004/108/EC “Electromagnetic Compatibility” Compliance with the European Directive 2004/108/EC has been proven by testing according to the following standards: emc emission EN 55022 Class B emc immunity EN 50130-4 European Directive 2006/95/EC “Low-Voltage Directive” Compliance with the European Directive 2006/95/EC has been proven by testing according to the following standard: Safety EN 60950-1 3.2 Overview of Conformity to EN50131 Standard This section gives an overview of the SPC compliance with the EN50131 Standard. The EN50131 Standard defines the requirements for Intrusion and Hold-up Alarm Systems. The SPC system is compliant with EN50131 Grade 2 and Grade 3, depending on the configuration. EN50131 Grade 2 Grade 2 systems are suitable for properties where the risk of theft is low to medium. These systems provide a good level of protection against intruders who have a limited knowledge of alarm systems. EN50131 Grade 3 Grade 3 systems are suitable for properties where the risk of theft is medium to high. These systems provide a high level of protection against intruders who have a good knowledge of alarm systems and may carry specialist tools. 3.3 Compliance with VdS 2115:2015-12 The SPC system is compliant with VdS 2115:2015-12, which defines the requirements for Intrusion and Hold-up Alarm Systems in Germany. 3.3.1 Compliance with EN50131 Approvals The SPC system has been approved by various certification bodies for compliance with EN50131 Standard. The following table provides an overview of the approvals: Certification Body Country Grade ATS Class VdS Germany 2, 3 ATS 2, 3 INCERT Belgium 2, 3 ATS 2, 3 NF France 2, 3 ATS 2, 3 A2P France 2, 3 ATS 2, 3 3.4 Compliance with EN 50136-1:2012 and EN 50136-2:2014 The SPC system is compliant with EN 50136-1:2012 and EN 50136-2:2014, which define the requirements for Alarm Transmission Systems. 3.5 Compliance with INCERT Approvals The SPC system has been approved by INCERT for compliance with EN50131 Standard. The following table provides an overview of the approvals: Certification Body Country Grade ATS Class INCERT Belgium 2, 3 ATS 2, 3 3.6 Compliance with NF and A2P approvals including CYBER requirements - SPC Products The SPC system has been approved by NF and A2P for compliance with EN50131 Standard. The following table provides an overview of the approvals: Certification Body Country Grade ATS Class NF France 2, 3 ATS 2, 3 A2P France 2, 3 ATS 2, 3 4 Technical Data 4.1 SPC Matrix The SPC system consists of various components, including control panels, keypads, expanders, and communication modules. The following table provides an overview of the SPC matrix: Component Model Number Description Control Panels SPC42xx 4-zone control panel SPC52xx 8-zone control panel SPC53xx 16-zone control panel SPC63xx 32-zone control panel Keypads SPCK420 LCD keypad SPCK421 LCD keypad with proximity reader SPCK520 Compact LCD keypad SPCK521 Compact LCD keypad with proximity reader SPCK620 Touchscreen keypad SPCK623 Touchscreen keypad with proximity reader Expanders SPCE452 8-output expander SPCE652 8-input 2-output expander Communication Modules SPCCOM100 PSTN communicator SPCCOM200 GSM/GPRS communicator SPCCOM300 IP communicator 5 Introduction The Vanderbilt SPC intrusion system is an IP enabled intrusion system that provides a wide range of intrusion functional for the needs of residential, commercial, and industrial applications. The SPC system offers a flexible and scalable solution for intrusion detection, access control, and video verification. 6 Mounting system equipment 6.1 Mounting a G2 housing 6.2 Mounting a G3 housing 6.2.1 Mounting a Back Tamper Kit 6.2.2 Battery installation for EN50131 compliance 6.3 Mounting a keypad 6.4 Mounting an expander 6.5 Wiring the X-BUS Interface 6.5.1 Wiring the Inputs 6.5.2 Wiring the Outputs 7 Controller hardware 7.1 Controller Hardware SPC42/SPC52/SPC53/SPC63 8 Door Expander 9 Wiring the system 9.1 Wiring the X-BUS interface 9.1.1 Loop configuration 9.1.2 Spur configuration 9.1.3 Star and multi-drop configuration 9.1.4 Shielding 9.1.5 Cable Map 9.2 Wiring of branch expander 9.3 Wiring the system ground 9.4 Wiring the relay output 9.5 Wiring the zone inputs 9.6 Wiring an external SAB bell 9.7 Wiring an internal sounder 9.8 Wiring Glassbreak 9.9 Installing plug-in modules 10 Powering up the SPC controller 10.1 Powering from battery only 11 Keypad user interface 11.1 SPCK420/421 11.1.1 About the LCD keypad 11.1.2 Using the LCD keypad interface 11.1.3 Data entry on the LCD keypad 12 Starting the system 12.1 Engineer modes 12.1.1 Engineer PINs 12.2 Programming with the keypad 12.3 Configuring start-up settings 12.4 Creating system users 12.5 Programming the portable PACE 12.6 Configuring wireless fob devices 12.6.1 Clearing alerts using the fob 13 Soft Engineer programming via the keypad 14 Engineer programming via the keypad 14.1 System Status 14.2 Options 14.3 Timers 14.4 Areas 14.5 Area Groups 14.6 X-BUS 14.6.1 X-BUS Addressing 14.6.2 XBUS Refresh 14.6.3 Reconfigure 14.6.4 Keypads/Expanders/Door Controllers 14.6.5 Addressing Mode 14.6.6 XBUS Type 14.6.7 Bus Retries 14.6.8 Comms Timer 14.7 Users 14.7.1 Add 14.7.2 Edit 14.7.3 Delete 14.8 User Profiles 14.8.1 Add 14.8.2 Edit 14.8.3 Delete 14.9 Wireless 14.9.1 Select a wireless programming option 14.9.2 Two way wireless 14.10 Zones 14.11 Doors 14.12 Outputs 14.12.1 Outputs types and output ports 14.13 Communication 14.13.1 Serial Ports 14.13.2 Ethernet Ports 14.13.3 Modems 14.13.4 Central Station 14.13.5 SPC Connect PRO 14.14 Test 14.14.1 Bell Test 14.14.2 Walk Test 14.14.3 Zone Monitor 14.14.4 Output Test 14.14.5 Soak Test 14.14.6 Audible Options 14.14.7 Visual Indicators 14.14.8 Seismic Test 14.15 Utilities 14.16 Isolate 14.17 Event Log 14.18 Access Log 14.19 Alarm Log 14.20 Change Engineer Pin 14.21 SMS 14.21.1 Add 14.21.2 Edit 14.21.3 Delete 14.22 Set Date/Time 14.23 Installer Text 14.24 Door Control 14.25 SPC Connect 15 Engineer programming via the browser 15.1 System Information 15.2 Ethernet interface 15.3 Connecting to the panel via USB 15.4 Logging into the browser 15.5 SPC Home 15.5.1 System Summary 15.5.2 Alarms Overview 15.5.3 Viewing Video 15.6 Panel status 15.6.1 Status 15.6.2 X-Bus Status 15.6.3 Wireless 15.6.4 Zones 15.6.5 Doors 15.6.6 FlexC Status 15.6.7 System alerts 15.7 Logs 15.7.1 System Log 15.7.2 Access Log 15.7.3 ALARM LOG 15.8 Users 15.8.1 Adding/Editing a User 15.8.2 Adding/Editing User Profiles 15.8.3 Configuring SMS 15.8.4 SMS Commands 15.8.5 Deleting Web Passwords 15.8.6 Configuring Engineer Settings 15.9 Wireless 15.9.1 Two way wireless 15.10 Configuration 15.10.1 Configuring controller inputs and outputs 15.10.2 X-BUS 15.10.3 Changing system settings 15.10.4 Configuring zones, doors and areas 15.10.5 Calendars 15.10.6 Change own PIN 15.10.7 Configuring advanced settings 15.11 Configuring Communications 15.11.1 Communications Settings 15.11.2 FlexC® 15.11.3 Reporting 15.11.4 PC Tools 15.12 File Operations 15.12.1 File Upgrade Operations 15.12.2 File Manager Operations 16 Accessing web server remotely 16.1 PSTN connection 17 Intruder alarm functionality 17.1 Financial mode operation 17.2 Commercial mode operation 17.3 Domestic mode operation 17.4 Full and local alarms 18 System examples and scenarios 18.1 When to use a common area 19 Seismic Sensors 19.1 Seismic Sensor Testing 19.1.1 Manual and Automatic Test Process 19.1.2 Automatically Testing Sensors 19.1.3 Manually Testing Sensors 20 Blocking Lock Operation 20.1 Blocking Lock 20.2 Authorized Setting of the Blocking Lock 20.3 Locking Element 21 Appendix 21.1 Network cable connections 21.2 Controller status LEDs 21.3 Powering expanders from the auxiliary power terminals 21.4 Calculating the battery power requirements 21.5 Domestic, Commercial and Financial mode default settings 21.6 SIA Codes 21.7 CID Codes 21.8 User PIN combinations 21.9 Duress PINs 21.10 Automatic inhibits 21.10.1 Zones 21.10.2 Access PINs 21.10.3 Engineer Access 21.10.4 Keypad User Logoff 21.11 Wiring of mains cable to the controller 21.12 Maintenance controller 21.13 Maintenance 21.14 Zone types 21.15 Zone attributes 21.16 ATS levels and attenuation specifications 21.17 Supported card readers and card formats 21.18 FlexC Glossary 21.19 FlexC Commands 21.20 ATS Category Timings 21.21 ATP Category Timings 22 Notes SPC Start-up Guide Version 3.6 © Vanderbilt International Ltd. 2016 Contents 1. Introduction 2. System Overview 3. Installation 4. Configuration 5. Operation 6. Maintenance 7. Troubleshooting 8. Appendix 1. Introduction This guide provides a step-by-step process for installing and configuring the Vanderbilt SPC intrusion system. It is intended for installers and technicians who are familiar with intrusion alarm systems and have a basic understanding of IP networking. 2. System Overview The Vanderbilt SPC intrusion system is a comprehensive security solution that combines intrusion detection, access control, and video verification into a single platform. The system is designed to meet the needs of various applications, from small residential properties to large commercial and industrial facilities. Key Features: • Integrated intrusion detection, access control, and video verification • IP-enabled for remote access and management • Scalable architecture to support various system sizes • User-friendly interface for easy operation and configuration • Compliance with international security standards System Components: • SPC control panel: The central processing unit of the system, responsible for managing all security functions. • Keypads: User interface devices for arming/disarming the system, entering PINs, and viewing system status. • Expanders: Modules that extend the system's capabilities by adding more zones, outputs, or other features. • Communication modules: Devices that enable communication with a central monitoring station or remote management software. • Sensors: Various types of detectors (e.g., motion sensors, door/window contacts, glassbreak detectors) that detect intrusion attempts. • Sirens: Audible warning devices that alert occupants and deter intruders. • Access control readers: Devices that grant or deny access to authorized individuals based on credentials (e.g., cards, PINs). • Cameras: Video surveillance devices that provide visual verification of events and activities. 3. Installation 3.1 Mounting the Control Panel 3.2 Wiring the System 3.2.1 Power Wiring 3.2.2 Zone Wiring 3.2.3 X-BUS Wiring 3.2.4 Output Wiring 3.3 Connecting Communication Modules 3.4 Connecting Keypads and Expanders 4. Configuration 4.1 Initial Setup Wizard 4.2 Programming Zones 4.3 Programming Users 4.4 Programming Outputs 4.5 Configuring Communication Settings 4.6 Configuring Access Control 4.7 Configuring Video Verification 5. Operation 5.1 Arming and Disarming the System 5.2 Managing Users 5.3 Viewing Event Logs 5.4 Responding to Alarms 6. Maintenance 6.1 System Diagnostics 6.2 Battery Replacement 6.3 Firmware Updates 7. Troubleshooting 7.1 Common Issues and Solutions 7.2 Fault Codes 8. Appendix 8.1 Technical Specifications 8.2 Wiring Diagrams 8.3 Default Settings 8.4 Compliance Information SPC Installation and Configuration Manual Version 3.13 © Vanderbilt International Ltd. 2024 Contents 1. Introduction 2. Safety Instructions 3. Directives and Standards 4. Technical Data 5. System Overview 6. Mounting the Control Panel 7. Wiring the System 7.1 Power Wiring 7.2 Zone Wiring 7.3 X-BUS Wiring 7.4 Output Wiring 8. Connecting Communication Modules 9. Connecting Keypads and Expanders 10. Initial Setup 10.1 Engineer PINs 10.2 Programming with the Keypad 10.3 Configuring Start-up Settings 10.4 Creating System Users 10.5 Programming Wireless Fob Devices 11. Engineer Programming via the Keypad 11.1 System Status 11.2 Options 11.3 Timers 11.4 Areas 11.5 Area Groups 11.6 X-BUS 11.6.1 X-BUS Addressing 11.6.2 XBUS Refresh 11.6.3 Reconfigure 11.6.4 Keypads/Expanders/Door Controllers 11.6.5 Addressing Mode 11.6.6 XBUS Type 11.6.7 Bus Retries 11.6.8 Comms Timer 11.7 Users 11.7.1 Add 11.7.2 Edit 11.7.3 Delete 11.8 User Profiles 11.8.1 Add 11.8.2 Edit 11.8.3 Delete 11.9 Wireless 11.9.1 Select a Wireless Programming Option 11.9.2 Two Way Wireless 11.10 Zones 11.11 Doors 11.12 Outputs 11.12.1 Output Types and Output Ports 11.13 Communication 11.13.1 Serial Ports 11.13.2 Ethernet Ports 11.13.3 Modems 11.13.4 Central Station 11.13.5 SPC Connect PRO 11.14 Test 11.14.1 Bell Test 11.14.2 Walk Test 11.14.3 Zone Monitor 11.14.4 Output Test 11.14.5 Soak Test 11.14.6 Audible Options 11.14.7 Visual Indicators 11.14.8 Seismic Test 11.15 Utilities 11.16 Isolate 11.17 Event Log 11.18 Access Log 11.19 Alarm Log 11.20 Change Engineer Pin 11.21 SMS 11.21.1 Add 11.21.2 Edit 11.21.3 Delete 11.22 Set Date/Time 11.23 Installer Text 11.24 Door Control 11.25 SPC Connect 12. Engineer Programming via the Browser 12.1 System Information 12.2 Ethernet Interface 12.3 Connecting to the Panel via USB 12.4 Logging into the Browser 12.5 SPC Home 12.5.1 System Summary 12.5.2 Alarms Overview 12.5.3 Viewing Video 12.6 Panel Status 12.6.1 Status 12.6.2 X-Bus Status 12.6.3 Wireless 12.6.4 Zones 12.6.5 Doors 12.6.6 FlexC Status 12.6.7 System Alerts 12.7 Logs 12.7.1 System Log 12.7.2 Access Log 12.7.3 Alarm Log 12.8 Users 12.8.1 Adding/Editing a User 12.8.2 Adding/Editing User Profiles 12.8.3 Configuring SMS 12.8.4 SMS Commands 12.8.5 Deleting Web Passwords 12.8.6 Configuring Engineer Settings 12.9 Wireless 12.9.1 Two Way Wireless 12.10 Configuration 12.10.1 Configuring Controller Inputs and Outputs 12.10.2 X-BUS 12.10.3 Changing System Settings 12.10.4 Configuring Zones, Doors and Areas 12.10.5 Calendars 12.10.6 Change Own PIN 12.10.7 Configuring Advanced Settings 12.11 Configuring Communications 12.11.1 Communications Settings 12.11.2 FlexC® 12.11.3 Reporting 12.11.4 PC Tools 12.12 File Operations 12.12.1 File Upgrade Operations 12.12.2 File Manager Operations 13. Accessing Web Server Remotely 13.1 PSTN Connection 14. Intruder Alarm Functionality 14.1 Financial Mode Operation 14.2 Commercial Mode Operation 14.3 Domestic Mode Operation 14.4 Full and Local Alarms 15. System Examples and Scenarios 15.1 When to Use a Common Area 16. Seismic Sensors 16.1 Seismic Sensor Testing 16.1.1 Manual and Automatic Test Process 16.1.2 Automatically Testing Sensors 16.1.3 Manually Testing Sensors 17. Blocking Lock Operation 17.1 Blocking Lock 17.2 Authorized Setting of the Blocking Lock 17.3 Locking Element 18. Appendix 18.1 Network Cable Connections 18.2 Controller Status LEDs 18.3 Powering Expanders from the Auxiliary Power Terminals 18.4 Calculating the Battery Power Requirements 18.5 Domestic, Commercial and Financial Mode Default Settings 18.6 SIA Codes 18.7 CID Codes 18.8 User PIN Combinations 18.9 Duress PINs 18.10 Automatic Inhibits 18.10.1 Zones 18.10.2 Access PINs 18.10.3 Engineer Access 18.10.4 Keypad User Logoff 18.11 Wiring of Mains Cable to the Controller 18.12 Maintenance Controller 18.13 Maintenance 18.14 Zone Types 18.15 Zone Attributes 18.16 ATS Levels and Attenuation Specifications 18.17 Supported Card Readers and Card Formats 18.18 FlexC Glossary 18.19 FlexC Commands 18.20 ATS Category Timings 18.21 ATP Category Timings 19. Notes SPC Installation and Configuration Manual Version 3.11 & 3.12 © Vanderbilt International Ltd. 2023 Contents 1. Introduction 2. Safety Instructions 3. Directives and Standards 4. Technical Data 5. System Overview 6. Mounting the Control Panel 7. Wiring the System 7.1 Power Wiring 7.2 Zone Wiring 7.3 X-BUS Wiring 7.4 Output Wiring 8. Connecting Communication Modules 9. Connecting Keypads and Expanders 10. Initial Setup 10.1 Engineer PINs 10.2 Programming with the Keypad 10.3 Configuring Start-up Settings 10.4 Creating System Users 10.5 Programming Wireless Fob Devices 11. Engineer Programming via the Keypad 11.1 System Status 11.2 Options 11.3 Timers 11.4 Areas 11.5 Area Groups 11.6 X-BUS 11.6.1 X-BUS Addressing 11.6.2 XBUS Refresh 11.6.3 Reconfigure 11.6.4 Keypads/Expanders/Door Controllers 11.6.5 Addressing Mode 11.6.6 XBUS Type 11.6.7 Bus Retries 11.6.8 Comms Timer 11.7 Users 11.7.1 Add 11.7.2 Edit 11.7.3 Delete 11.8 User Profiles 11.8.1 Add 11.8.2 Edit 11.8.3 Delete 11.9 Wireless 11.9.1 Select a Wireless Programming Option 11.9.2 Two Way Wireless 11.10 Zones 11.11 Doors 11.12 Outputs 11.12.1 Output Types and Output Ports 11.13 Communication 11.13.1 Serial Ports 11.13.2 Ethernet Ports 11.13.3 Modems 11.13.4 Central Station 11.13.5 SPC Connect PRO 11.14 Test 11.14.1 Bell Test 11.14.2 Walk Test 11.14.3 Zone Monitor 11.14.4 Output Test 11.14.5 Soak Test 11.14.6 Audible Options 11.14.7 Visual Indicators 11.14.8 Seismic Test 11.15 Utilities 11.16 Isolate 11.17 Event Log 11.18 Access Log 11.19 Alarm Log 11.20 Change Engineer Pin 11.21 SMS 11.21.1 Add 11.21.2 Edit 11.21.3 Delete 11.22 Set Date/Time 11.23 Installer Text 11.24 Door Control 11.25 SPC Connect 12. Engineer Programming via the Browser 12.1 System Information 12.2 Ethernet Interface 12.3 Connecting to the Panel via USB 12.4 Logging into the Browser 12.5 SPC Home 12.5.1 System Summary 12.5.2 Alarms Overview 12.5.3 Viewing Video 12.6 Panel Status 12.6.1 Status 12.6.2 X-Bus Status 12.6.3 Wireless 12.6.4 Zones 12.6.5 Doors 12.6.6 FlexC Status 12.6.7 System Alerts 12.7 Logs 12.7.1 System Log 12.7.2 Access Log 12.7.3 Alarm Log 12.8 Users 12.8.1 Adding/Editing a User 12.8.2 Adding/Editing User Profiles 12.8.3 Configuring SMS 12.8.4 SMS Commands 12.8.5 Deleting Web Passwords 12.8.6 Configuring Engineer Settings 12.9 Wireless 12.9.1 Two Way Wireless 12.10 Configuration 12.10.1 Configuring Controller Inputs and Outputs 12.10.2 X-BUS 12.10.3 Changing System Settings 12.10.4 Configuring Zones, Doors and Areas 12.10.5 Calendars 12.10.6 Change Own PIN 12.10.7 Configuring Advanced Settings 12.11 Configuring Communications 12.11.1 Communications Settings 12.11.2 FlexC® 12.11.3 Reporting 12.11.4 PC Tools 12.12 File Operations 12.12.1 File Upgrade Operations 12.12.2 File Manager Operations 13. Accessing Web Server Remotely 13.1 PSTN Connection 14. Intruder Alarm Functionality 14.1 Financial Mode Operation 14.2 Commercial Mode Operation 14.3 Domestic Mode Operation 14.4 Full and Local Alarms 15. System Examples and Scenarios 15.1 When to Use a Common Area 16. Seismic Sensors 16.1 Seismic Sensor Testing 16.1.1 Manual and Automatic Test Process 16.1.2 Automatically Testing Sensors 16.1.3 Manually Testing Sensors 17. Blocking Lock Operation 17.1 Blocking Lock 17.2 Authorized Setting of the Blocking Lock 17.3 Locking Element 18. Appendix 18.1 Network Cable Connections 18.2 Controller Status LEDs 18.3 Powering Expanders from the Auxiliary Power Terminals 18.4 Calculating the Battery Power Requirements 18.5 Domestic, Commercial and Financial Mode Default Settings 18.6 SIA Codes 18.7 CID Codes 18.8 User PIN Combinations 18.9 Duress PINs 18.10 Automatic Inhibits 18.10.1 Zones 18.10.2 Access PINs 18.10.3 Engineer Access 18.10.4 Keypad User Logoff 18.11 Wiring of Mains Cable to the Controller 18.12 Maintenance Controller 18.13 Maintenance 18.14 Zone Types 18.15 Zone Attributes 18.16 ATS Levels and Attenuation Specifications 18.17 Supported Card Readers and Card Formats 18.18 FlexC Glossary 18.19 FlexC Commands 18.20 ATS Category Timings 18.21 ATP Category Timings 19. Notes SPC Installation and Configuration Manual Version 3.8.5 © Vanderbilt International Ltd. 2023 Contents 1. Introduction 2. Safety Instructions 3. Directives and Standards 4. Technical Data 5. System Overview 6. Mounting the Control Panel 7. Wiring the System 7.1 Power Wiring 7.2 Zone Wiring 7.3 X-BUS Wiring 7.4 Output Wiring 8. Connecting Communication Modules 9. Connecting Keypads and Expanders 10. Initial Setup 10.1 Engineer PINs 10.2 Programming with the Keypad 10.3 Configuring Start-up Settings 10.4 Creating System Users 10.5 Programming Wireless Fob Devices 11. Engineer Programming via the Keypad 11.1 System Status 11.2 Options 11.3 Timers 11.4 Areas 11.5 Area Groups 11.6 X-BUS 11.6.1 X-BUS Addressing 11.6.2 XBUS Refresh 11.6.3 Reconfigure 11.6.4 Keypads/Expanders/Door Controllers 11.6.5 Addressing Mode 11.6.6 XBUS Type 11.6.7 Bus Retries 11.6.8 Comms Timer 11.7 Users 11.7.1 Add 11.7.2 Edit 11.7.3 Delete 11.8 User Profiles 11.8.1 Add 11.8.2 Edit 11.8.3 Delete 11.9 Wireless 11.9.1 Select a Wireless Programming Option 11.9.2 Two Way Wireless 11.10 Zones 11.11 Doors 11.12 Outputs 11.12.1 Output Types and Output Ports 11.13 Communication 11.13.1 Serial Ports 11.13.2 Ethernet Ports 11.13.3 Modems 11.13.4 Central Station 11.13.5 SPC Connect PRO 11.14 Test 11.14.1 Bell Test 11.14.2 Walk Test 11.14.3 Zone Monitor 11.14.4 Output Test 11.14.5 Soak Test 11.14.6 Audible Options 11.14.7 Visual Indicators 11.14.8 Seismic Test 11.15 Utilities 11.16 Isolate 11.17 Event Log 11.18 Access Log 11.19 Alarm Log 11.20 Change Engineer Pin 11.21 SMS 11.21.1 Add 11.21.2 Edit 11.21.3 Delete 11.22 Set Date/Time 11.23 Installer Text 11.24 Door Control 11.25 SPC Connect 12. Engineer Programming via the Browser 12.1 System Information 12.2 Ethernet Interface 12.3 Connecting to the Panel via USB 12.4 Logging into the Browser 12.5 SPC Home 12.5.1 System Summary 12.5.2 Alarms Overview 12.5.3 Viewing Video 12.6 Panel Status 12.6.1 Status 12.6.2 X-Bus Status 12.6.3 Wireless 12.6.4 Zones 12.6.5 Doors 12.6.6 FlexC Status 12.6.7 System Alerts 12.7 Logs 12.7.1 System Log 12.7.2 Access Log 12.7.3 Alarm Log 12.8 Users 12.8.1 Adding/Editing a User 12.8.2 Adding/Editing User Profiles 12.8.3 Configuring SMS 12.8.4 SMS Commands 12.8.5 Deleting Web Passwords 12.8.6 Configuring Engineer Settings 12.9 Wireless 12.9.1 Two Way Wireless 12.10 Configuration 12.10.1 Configuring Controller Inputs and Outputs 12.10.2 X-BUS 12.10.3 Changing System Settings 12.10.4 Configuring Zones, Doors and Areas 12.10.5 Calendars 12.10.6 Change Own PIN 12.10.7 Configuring Advanced Settings 12.11 Configuring Communications 12.11.1 Communications Settings 12.11.2 FlexC® 12.11.3 Reporting 12.11.4 PC Tools 12.12 File Operations 12.12.1 File Upgrade Operations 12.12.2 File Manager Operations 13. Accessing Web Server Remotely 13.1 PSTN Connection 14. Intruder Alarm Functionality 14.1 Financial Mode Operation 14.2 Commercial Mode Operation 14.3 Domestic Mode Operation 14.4 Full and Local Alarms 15. System Examples and Scenarios 15.1 When to Use a Common Area 16. Seismic Sensors 16.1 Seismic Sensor Testing 16.1.1 Manual and Automatic Test Process 16.1.2 Automatically Testing Sensors 16.1.3 Manually Testing Sensors 17. Blocking Lock Operation 17.1 Blocking Lock 17.2 Authorized Setting of the Blocking Lock 17.3 Locking Element 18. Appendix 18.1 Network Cable Connections 18.2 Controller Status LEDs 18.3 Powering Expanders from the Auxiliary Power Terminals 18.4 Calculating the Battery Power Requirements 18.5 Domestic, Commercial and Financial Mode Default Settings 18.6 SIA Codes 18.7 CID Codes 18.8 User PIN Combinations 18.9 Duress PINs 18.10 Automatic Inhibits 18.10.1 Zones 18.10.2 Access PINs 18.10.3 Engineer Access 18.10.4 Keypad User Logoff 18.11 Wiring of Mains Cable to the Controller 18.12 Maintenance Controller 18.13 Maintenance 18.14 Zone Types 18.15 Zone Attributes 18.16 ATS Levels and Attenuation Specifications 18.17 Supported Card Readers and Card Formats 18.18 FlexC Glossary 18.19 FlexC Commands 18.20 ATS Category Timings 18.21 ATP Category Timings 19. Notes SPC Installation and Configuration Manual Version 3.11 & 3.12 © Vanderbilt International Ltd. 2023 Contents 1. Introduction 2. Safety Instructions 3. Directives and Standards 4. Technical Data 5. System Overview 6. Mounting the Control Panel 7. Wiring the System 7.1 Power Wiring 7.2 Zone Wiring 7.3 X-BUS Wiring 7.4 Output Wiring 8. Connecting Communication Modules 9. Connecting Keypads and Expanders 10. Initial Setup 10.1 Engineer PINs 10.2 Programming with the Keypad 10.3 Configuring Start-up Settings 10.4 Creating System Users 10.5 Programming Wireless Fob Devices 11. Engineer Programming via the Keypad 11.1 System Status 11.2 Options 11.3 Timers 11.4 Areas 11.5 Area Groups 11.6 X-BUS 11.6.1 X-BUS Addressing 11.6.2 XBUS Refresh 11.6.3 Reconfigure 11.6.4 Keypads/Expanders/Door Controllers 11.6.5 Addressing Mode 11.6.6 XBUS Type 11.6.7 Bus Retries 11.6.8 Comms Timer 11.7 Users 11.7.1 Add 11.7.2 Edit 11.7.3 Delete 11.8 User Profiles 11.8.1 Add 11.8.2 Edit 11.8.3 Delete 11.9 Wireless 11.9.1 Select a Wireless Programming Option 11.9.2 Two Way Wireless 11.10 Zones 11.11 Doors 11.12 Outputs 11.12.1 Output Types and Output Ports 11.13 Communication 11.13.1 Serial Ports 11.13.2 Ethernet Ports 11.13.3 Modems 11.13.4 Central Station 11.13.5 SPC Connect PRO 11.14 Test 11.14.1 Bell Test 11.14.2 Walk Test 11.14.3 Zone Monitor 11.14.4 Output Test 11.14.5 Soak Test 11.14.6 Audible Options 11.14.7 Visual Indicators 11.14.8 Seismic Test 11.15 Utilities 11.16 Isolate 11.17 Event Log 11.18 Access Log 11.19 Alarm Log 11.20 Change Engineer Pin 11.21 SMS 11.21.1 Add 11.21.2 Edit 11.21.3 Delete 11.22 Set Date/Time 11.23 Installer Text 11.24 Door Control 11.25 SPC Connect 12. Engineer Programming via the Browser 12.1 System Information 12.2 Ethernet Interface 12.3 Connecting to the Panel via USB 12.4 Logging into the Browser 12.5 SPC Home 12.5.1 System Summary 12.5.2 Alarms Overview 12.5.3 Viewing Video 12.6 Panel Status 12.6.1 Status 12.6.2 X-Bus Status 12.6.3 Wireless 12.6.4 Zones 12.6.5 Doors 12.6.6 FlexC Status 12.6.7 System Alerts 12.7 Logs 12.7.1 System Log 12.7.2 Access Log 12.7.3 Alarm Log 12.8 Users 12.8.1 Adding/Editing a User 12.8.2 Adding/Editing User Profiles 12.8.3 Configuring SMS 12.8.4 SMS Commands 12.8.5 Deleting Web Passwords 12.8.6 Configuring Engineer Settings 12.9 Wireless 12.9.1 Two Way Wireless 12.10 Configuration 12.10.1 Configuring Controller Inputs and Outputs 12.10.2 X-BUS 12.10.3 Changing System Settings 12.10.4 Configuring Zones, Doors and Areas 12.10.5 Calendars 12.10.6 Change Own PIN 12.10.7 Configuring Advanced Settings 12.11 Configuring Communications 12.11.1 Communications Settings 12.11.2 FlexC® 12.11.3 Reporting 12.11.4 PC Tools 12.12 File Operations 12.12.1 File Upgrade Operations 12.12.2 File Manager Operations 13. Accessing Web Server Remotely 13.1 PSTN Connection 14. Intruder Alarm Functionality 14.1 Financial Mode Operation 14.2 Commercial Mode Operation 14.3 Domestic Mode Operation 14.4 Full and Local Alarms 15. System Examples and Scenarios 15.1 When to Use a Common Area 16. Seismic Sensors 16.1 Seismic Sensor Testing 16.1.1 Manual and Automatic Test Process 16.1.2 Automatically Testing Sensors 16.1.3 Manually Testing Sensors 17. Blocking Lock Operation 17.1 Blocking Lock 17.2 Authorized Setting of the Blocking Lock 17.3 Locking Element 18. Appendix 18.1 Network Cable Connections 18.2 Controller Status LEDs 18.3 Powering Expanders from the Auxiliary Power Terminals 18.4 Calculating the Battery Power Requirements 18.5 Domestic, Commercial and Financial Mode Default Settings 18.6 SIA Codes 18.7 CID Codes 18.8 User PIN Combinations 18.9 Duress PINs 18.10 Automatic Inhibits 18.10.1 Zones 18.10.2 Access PINs 18.10.3 Engineer Access 18.10.4 Keypad User Logoff 18.11 Wiring of Mains Cable to the Controller 18.12 Maintenance Controller 18.13 Maintenance 18.14 Zone Types 18.15 Zone Attributes 18.16 ATS Levels and Attenuation Specifications 18.17 Supported Card Readers and Card Formats 18.18 FlexC Glossary 18.19 FlexC Commands 18.20 ATS Category Timings 18.21 ATP Category Timings 19. Notes SPC Installation and Configuration Manual Version 3.8.5 © Vanderbilt International Ltd. 2023 Contents 1. Introduction 2. Safety Instructions 3. Directives and Standards 4. Technical Data 5. System Overview 6. Mounting the Control Panel 7. Wiring the System 7.1 Power Wiring 7.2 Zone Wiring 7.3 X-BUS Wiring 7.4 Output Wiring 8. Connecting Communication Modules 9. Connecting Keypads and Expanders 10. Initial Setup 10.1 Engineer PINs 10.2 Programming with the Keypad 10.3 Configuring Start-up Settings 10.4 Creating System Users 10.5 Programming Wireless Fob Devices 11. Engineer Programming via the Keypad 11.1 System Status 11.2 Options 11.3 Timers 11.4 Areas 11.5 Area Groups 11.6 X-BUS 11.6.1 X-BUS Addressing 11.6.2 XBUS Refresh 11.6.3 Reconfigure 11.6.4 Keypads/Expanders/Door Controllers 11.6.5 Addressing Mode 11.6.6 XBUS Type 11.6.7 Bus Retries 11.6.8 Comms Timer 11.7 Users 11.7.1 Add 11.7.2 Edit 11.7.3 Delete 11.8 User Profiles 11.8.1 Add 11.8.2 Edit 11.8.3 Delete 11.9 Wireless 11.9.1 Select a Wireless Programming Option 11.9.2 Two Way Wireless 11.10 Zones 11.11 Doors 11.12 Outputs 11.12.1 Output Types and Output Ports 11.13 Communication 11.13.1 Serial Ports 11.13.2 Ethernet Ports 11.13.3 Modems 11.13.4 Central Station 11.13.5 SPC Connect PRO 11.14 Test 11.14.1 Bell Test 11.14.2 Walk Test 11.14.3 Zone Monitor 11.14.4 Output Test 11.14.5 Soak Test 11.14.6 Audible Options 11.14.7 Visual Indicators 11.14.8 Seismic Test 11.15 Utilities 11.16 Isolate 11.17 Event Log 11.18 Access Log 11.19 Alarm Log 11.20 Change Engineer Pin 11.21 SMS 11.21.1 Add 11.21.2 Edit 11.21.3 Delete 11.22 Set Date/Time 11.23 Installer Text 11.24 Door Control 11.25 SPC Connect 12. Engineer Programming via the Browser 12.1 System Information 12.2 Ethernet Interface 12.3 Connecting to the Panel via USB 12.4 Logging into the Browser 12.5 SPC Home 12.5.1 System Summary 12.5.2 Alarms Overview 12.5.3 Viewing Video 12.6 Panel Status 12.6.1 Status 12.6.2 X-Bus Status 12.6.3 Wireless 12.6.4 Zones 12.6.5 Doors 12.6.6 FlexC Status 12.6.7 System Alerts 12.7 Logs 12.7.1 System Log 12.7.2 Access Log 12.7.3 Alarm Log 12.8 Users 12.8.1 Adding/Editing a User 12.8.2 Adding/Editing User Profiles 12.8.3 Configuring SMS 12.8.4 SMS Commands 12.8.5 Deleting Web Passwords 12.8.6 Configuring Engineer Settings 12.9 Wireless 12.9.1 Two Way Wireless 12.10 Configuration 12.10.1 Configuring Controller Inputs and Outputs 12.10.2 X-BUS 12.10.3 Changing System Settings 12.10.4 Configuring Zones, Doors and Areas 12.10.5 Calendars 12.10.6 Change Own PIN 12.10.7 Configuring Advanced Settings 12.11 Configuring Communications 12.11.1 Communications Settings 12.11.2 FlexC® 12.11.3 Reporting 12.11.4 PC Tools 12.12 File Operations 12.12.1 File Upgrade Operations 12.12.2 File Manager Operations 13. Accessing Web Server Remotely 13.1 PSTN Connection 14. Intruder Alarm Functionality 14.1 Financial Mode Operation 14.2 Commercial Mode Operation 14.3 Domestic Mode Operation 14.4 Full and Local Alarms 15. System Examples and Scenarios 15.1 When to Use a Common Area 16. Seismic Sensors 16.1 Seismic Sensor Testing 16.1.1 Manual and Automatic Test Process 16.1.2 Automatically Testing Sensors 16.1.3 Manually Testing Sensors 17. Blocking Lock Operation 17.1 Blocking Lock 17.2 Authorized Setting of the Blocking Lock 17.3 Locking Element 18. Appendix 18.1 Network Cable Connections 18.2 Controller Status LEDs 18.3 Powering Expanders from the Auxiliary Power Terminals 18.4 Calculating the Battery Power Requirements 18.5 Domestic, Commercial and Financial Mode Default Settings 18.6 SIA Codes 18.7 CID Codes 18.8 User PIN Combinations 18.9 Duress PINs 18.10 Automatic Inhibits 18.10.1 Zones 18.10.2 Access PINs 18.10.3 Engineer Access 18.10.4 Keypad User Logoff 18.11 Wiring of Mains Cable to the Controller 18.12 Maintenance Controller 18.13 Maintenance 18.14 Zone Types 18.15 Zone Attributes 18.16 ATS Levels and Attenuation Specifications 18.17 Supported Card Readers and Card Formats 18.18 FlexC Glossary 18.19 FlexC Commands 18.20 ATS Category Timings 18.21 ATP Category Timings 19. Notes
| Product | Type | Notes |
|---|---|---|
| 3000 Series | Residential audio | 2-wire bus, up to 99 apartments |
| 4000 Series | Commercial audio/video | 4-wire bus, up to 99 apartments |
| VX2200 | IP video | SIP-based, app access |
| VX2300 | IP video (current) | SIP-based, app access, ONVIF |
| GSM Entry | GSM-based entry | No internet required — calls mobile phone |
| Terminal | Function | Notes |
|---|---|---|
| A | Audio/video data positive | Twisted pair with B |
| B | Audio/video data negative | Twisted pair with A |
| +12V | Power supply positive | From Videx PSU |
| 0V | Power supply negative / ground | Common ground |
| Terminal | Function | Notes |
|---|---|---|
| 1 | Bus positive | Carries audio and power |
| 2 | Bus negative / ground | Common ground |
| Code / Display | Description | Likely Cause | Action |
|---|---|---|---|
| No Power | Panel not powering up | PSU fault, wiring fault, fuse blown | Check PSU output voltage. Check fuse. Inspect wiring. |
| No Audio | No audio between panel and handset | Wiring fault, bus fault, handset fault | Check bus wiring. Test with another handset. Check bus polarity. |
| No Video | No video at handset | Camera fault, wiring fault, handset fault | Check camera connection. Test with another handset. Check video wiring. |
| Door Not Opening | Door release not activating | Relay fault, lock wiring fault, power fault | Test relay output with multimeter. Check lock wiring and power. |
| Interference / Noise | Audio interference or noise | Cable routing near mains, earth loop | Re-route bus cable away from mains. Check earth connections. |
| IP Panel Offline | VX2300 not accessible on network | IP address conflict, network fault | Check IP address. Ping panel. Check network cable. |
| SIP Registration Failed | VX2300 not registering with SIP server | SIP credentials incorrect, server unreachable | Check SIP credentials. Verify SIP server address. |
| Terminal | Function | Notes |
|---|---|---|
| A | Bus data positive | Twisted pair with B — max 100m |
| B | Bus data negative | Twisted pair with A — max 100m |
| +12V | Power supply | From Videx 4000 PSU |
| 0V | Common ground | Must be continuous |
| LOCK | Door release relay | Normally open — closes on door release |
| COM | Door release relay common | Common terminal |
| Terminal | Function | Notes |
|---|---|---|
| 1 | Bus positive | Max 50m for 2-wire system |
| 2 | Bus negative | Common ground |
| LOCK | Door release relay | Normally open |
| COM | Door release relay common | Common terminal |
=== WEB RESEARCH: videx ===
# Videx Access Control Intercom Systems - Full Technical Reference
This document compiles comprehensive technical information regarding Videx access control intercom systems, extracted from various datasheets. It includes product ranges, technical specifications, wiring details, and other relevant technical data.
## PABX Interface Unit
### 275 PABX Interface
The 275 interface unit enables a Videx intercom panel to be connected to an analogue extension port on a telephone switchboard (PABX). The unit connects via two wires to a free extension port, allowing the intercom panel to call any other extension or hunt group. When a button is pressed on the intercom panel, the relevant extension or extensions will ring, and once answered, will allow a two-way conversation and the opening of the door by pressing “9” on the telephone keypad.
The 275 can connect directly to a single call button intercom panel or, with the use of the 275-10 interface, an intercom with up to 10 call buttons. The 275-Z or 275-D 5 button diode board is required when using the 275-10 interface (one required for every 5 buttons).
**Key Features include:**
* Connection to a free extension port on a PABX telephone system.
* Can be programmed to call any other extension or hunt group.
* Can connect up to 10 call buttons using the 275-10 interface module.
* With the 275-2W, can be connected to both the VX2200 and VX2300 digital intercom systems using either of the additional bus interface units: the 2280 (for the VX2200) or the 2380 (for the VX2300).
**Models and Descriptions:**
| Model | System | Description |
| :------ | :------------ | :----------------------------------------------------------- |
| 275 | 4K, 8K, VR4K | PABX Interface Unit (connects to an analogue extension) |
| 275-10 | All | 10 Button expansion module (requires 275-D or 275-Z) |
| 275-D | 4K, 8K | 5 button diode board (used with 4837 and 8837M amplifiers) |
| 275-Z | 4K, VR4K | 5 button diode board (used with 4838 and 136 amplifiers) |
| 275-2W | VX2200, VX2300 | 2 Wire PABX Interface Unit for use with the VX2200 or VX2300 Digital Systems (requires 2280 or 2380) |
| 2280 | VX2200 | 2 Wire BUS Interface Unit for VX2200 |
| 2380 | VX2300 | 2 Wire BUS Interface Unit for VX2300 |
| 521 | All | 12Vdc Power Supply |
## 4000 Series Rainshields
### 4000 Series Flush & Surface Rainshields
Rainshields are available for the 4000 series modular range to fit both flush and surface back boxes (with one, two or three modules). They are available in the standard 4000 series “gunmetal grey” finish and are manufactured from aluminium alloy. The rainshields offer additional protection without detracting from the aesthetics of the entry panel. The flush rainshield also presents a larger cover area to the back box cutout, making it easier to install and seal the panel on uneven surfaces.
**Key Features include:**
* Available for the 4000 series modular range (up to 3 modules).
* Flush and surface mount rainshield options available.
* Available in the standard 4000 series “gunmetal grey” finish.
* Offers additional cover protection from the elements.
**Models and Descriptions:**
| Model | Description |
| :---- | :------------------------------------------- |
| 4871 | Flush mount 4000 series 1 module rainshield |
| 4872 | Flush mount 4000 series 2 module rainshield |
| 4873 | Flush mount 4000 series 3 module rainshield |
| 4891 | Surface mount 4000 series 1 module rainshield|
| 4892 | Surface mount 4000 series 2 module rainshield|
| 4893 | Surface mount 4000 series 3 module rainshield|
## 8K Series Audiokits with Codelock
### 8K 380 Audiokit with Codelock
These audiokits are part of the 8000 Series and are available for both flush and surface mounting. They feature a standard 3+1 audio system with a built-in codelock.
**Specifications:**
| Feature | Description |
| :---------------- | :--------------------------------------------- |
| Part No. | 8K-1/380/CL, 8K-1S/380/CL |
| Outdoor Station | 8000 Series Speaker unit module (1 x 8836M-1) |
| Call Buttons | 1 |
| Door Opening | Built-in Lock Relay |
| Call | Electronic Call Tone |
| Codes / Relays | 2/2 |
| Illumination | Yes |
| Mounting box | 1 x 8852 |
| Rainshield Frame | 1 x 8882 |
| Mounting | Flush (8K-1/380/CL), Surface (8K-1S/380/CL) |
| Call input | Positive trigger (ac or dc) |
| Programming | Program via DTMF telephone |
| Power Requirements| 230Vac mains input |
| Power Supply Unit | 1 x 321 (230Vac / 12Vac / 15VA) |
| Codelock Unit | 2 codes, 2 relays |
| Size (Codelock) | 3 Modules A Type DIN Box (52.5x105x65mm) |
| Mounting (Codelock)| DIN bar or direct wall fixing |
**Note:** Black frames and surface boxes are also available. Add suffix /BL to the Audiokit part number (e.g., 8K-1S/380/CL/BL).
## 8K Series Audiokits
### 8K 380 Audiokit
These audiokits are similar to the codelock versions but without the integrated codelock. They offer standard 3+1 audio and are available for flush and surface mounting.
**Specifications:**
| Feature | Description |
| :---------------- | :--------------------------------------------- |
| Part No. | 8K-1/380, 8K-1S/380 |
| Outdoor Station | 8000 Series Speaker unit module (1 x 8836M-1) |
| Call Buttons | 1 |
| Door Opening | Built-in Lock Relay |
| Call | Electronic Call Tone |
| Mounting box | 1 x 8851 |
| Rainshield Frame | 1 x 8881 |
| Mounting | Flush (8K-1/380), Surface (8K-1S/380) |
| Power Supply Unit | 1 x 321 (230Vac / 12Vac / 15VA) |
**Note:** Black frames and surface boxes are also available. Add suffix /BL to the Audiokit part number (e.g., 8K-1S/380/BL).
## Kristallo KRV 7″ Series Datasheet
### KRV7 Hands Free Kristallo Series
The 7" TFT LCD hands-free colour video monitor complements the existing range of Kristallo series videophones and audio apartment stations. With a screen resolution of 800x480 pixels, it features touch-sensitive controls, hands-free speech (with simplex function), entrance recall, door release, a timed ‘do not disturb’ function, and the ability to intercommunicate between multiple devices.
Available for both the VX2200 digital system (6 wire bus video) and the VX2300 digital system ("true" 2 wire bus), the 7” hands-free Kristallo series video monitors have been designed for use in single apartment installations through to high-rise installations with up to 1000 apartments.
The KRV7 series video monitor can be desk mounted using the KRV7931 desktop kit, fixed to the wall using the relevant surface wall mounting kit (KRV7985/W or KRV7985/B), or flushed into the wall using the KRV7981 (for solid walls) or KRV7983 (for dry line walls).
**Key Features Include:**
* Hands-free duplex speech to entrances and other Kristallo line intercom units.
* Timed ‘Do Not Disturb’ function with call reject feature.
* Door open and Privacy LED’s.
* Programmable number of rings, auxiliary output time, privacy time, and call melody.
* Door release button, auxiliary output, and local doorbell facility.
* Door recall to activate the camera and speech without first being called.
* Desk mounting kit available.
* Flush mounting and surface mounting back box options available.
**Models and Descriptions:**
| Model | System | Description |
| :-------- | :----- | :----------------------------------------------------------------------- |
| KRV772W | VX2200 | White 7” hands-free Kristallo monitor (requires flush or surface box) |
| KRV772B | VX2200 | Black 7” hands-free Kristallo monitor (requires flush or surface box) |
| KRV782W | VX2300 | White 7” hands-free Kristallo monitor (requires flush or surface box) |
| KRV782B | VX2300 | Black 7” hands-free Kristallo monitor (requires flush or surface box) |
| KRV7931 | All | Desk mount kit |
| KRV7981 | All | Flush box for solid wall installation |
| KRV7983 | All | Flush box for dry line wall installation |
| KRV7985/W | All | Surface mounting kit (white) |
| KRV7985/B | All | Surface mounting kit (black) |
## VR/DIN Series Panel Mount Readers Datasheet
### Low Profile Vandal Resistant Panel Mount Keypads, Proximity Readers & Fingerprint Readers
This series offers low-profile vandal-resistant panel mount devices for access control. It includes keypads, proximity readers, and fingerprint readers.
**Key Features:**
* Vandal-resistant construction.
* Low profile design.
* Available as keypads, proximity readers, and fingerprint readers.
**Models and Descriptions:**
(Details to be extracted from the datasheet. The provided text does not contain specific model numbers or detailed descriptions for this section.)
## AKMI-1 MiAccess Kit & AKPP-2 Portal Plus Access Control Datasheet
### AKMI-1: MiAccess, 1 Door (Mifare) Proximity Access Control Kit
### AKPP-2: Portal Plus, 2 Door Access Control Kit
This datasheet covers two access control kits: the AKMI-1 for single-door Mifare proximity access control and the AKPP-2 for two-door Portal Plus access control.
**AKMI-1 MiAccess Kit Features:**
* Single door access control.
* Mifare proximity technology.
* Easy to install and configure.
**AKPP-2 Portal Plus Access Control Kit Features:**
* Two-door access control.
* Portal Plus system.
* Advanced access control functionalities.
**Models and Descriptions:**
(Details to be extracted from the datasheet. The provided text does not contain specific model numbers or detailed descriptions for this section.)
## PO 45° Series Posts Datasheet
### A Range of Stainless Steel Posts with 45° Angled Arm(s) to Mount Audio & Video Door Entry Panels
This series provides stainless steel posts designed for mounting audio and video door entry panels. The posts feature 45° angled arms for optimal panel positioning.
**Key Features:**
* Stainless steel construction.
* 45° angled arm(s) for panel mounting.
* Suitable for audio and video door entry panels.
**Models and Descriptions:**
(Details to be extracted from the datasheet. The provided text does not contain specific model numbers or detailed descriptions for this section.)
## AL500-MF Standalone MiAccess Door Handle
### MiAccess Standalone Door Handle Datasheet
This datasheet describes the AL500-MF, a standalone MiAccess door handle for access control applications.
**Key Features:**
* Standalone operation.
* MiAccess technology.
* Integrated door handle design.
**Models and Descriptions:**
(Details to be extracted from the datasheet. The provided text does not contain specific model numbers or detailed descriptions for this section.)
## MiAccess Access Control
### MiAccess Standalone Offline Mifare Proximity Access Control System
This document details the MiAccess standalone offline Mifare Proximity Access Control System.
**Key Features:**
* Standalone operation.
* Offline system.
* Mifare proximity technology.
* Access control functionalities.
**Models and Descriptions:**
(Details to be extracted from the datasheet. The provided text does not contain specific model numbers or detailed descriptions for this section.)
## RB0408 Portal Plus Lift Interface Datasheet
### Portal Plus Lift Interface Module RB0408 Datasheet
This datasheet provides information on the RB0408 Portal Plus Lift Interface Module.
**Key Features:**
* Portal Plus system compatibility.
* Lift interface functionality.
* Module RB0408.
**Models and Descriptions:**
(Details to be extracted from the datasheet. The provided text does not contain specific model numbers or detailed descriptions for this section.)
## Telephone Interface Datasheet
### Telephone Interface Datasheet
This datasheet describes a telephone interface for Videx intercom systems.
**Key Features:**
* Connects intercom to telephone systems.
* Enables communication between intercom and telephones.
**Models and Descriptions:**
(Details to be extracted from the datasheet. The provided text does not contain specific model numbers or detailed descriptions for this section.)
## 8K/380/CL Audio Kit Datasheet
### 8K/380/CL Audio Kit Datasheet
This datasheet provides details on the 8K/380/CL Audio Kit.
**Key Features:**
* Audio intercom kit.
* Model 8K/380/CL.
**Models and Descriptions:**
(Details to be extracted from the datasheet. The provided text does not contain specific model numbers or detailed descriptions for this section.)
## 8K/380 Audio Kit Datasheet
### 8K/380 Audio Kit Datasheet
This datasheet provides details on the 8K/380 Audio Kit.
**Key Features:**
* Audio intercom kit.
* Model 8K/380.
**Models and Descriptions:**
(Details to be extracted from the datasheet. The provided text does not contain specific model numbers or detailed descriptions for this section.)
## 4000 Series All Weather Frames
### 4000 Series All Weather Frames
A range of all-weather frames for the 4000 Series, finished in gunmetal grey to match the gunmetal grey 4000 Series frames and available for both surface and flush installations.
**Key Features:**
* All-weather design.
* Gunmetal grey finish.
* Compatible with 4000 Series frames.
* Suitable for surface and flush installations.
**Models and Descriptions:**
(Details to be extracted from the datasheet. The provided text does not contain specific model numbers or detailed descriptions for this section.)
## SP9 Series Posts Datasheet
### SP9 Series Posts Datasheet
This datasheet describes the SP9 Series Posts.
**Key Features:**
* SP9 Series posts.
**Models and Descriptions:**
(Details to be extracted from the datasheet. The provided text does not contain specific model numbers or detailed descriptions for this section.)
## WS4 Brochure
### WS4 Access Control Solution
(Note: The full content of the WS4 Brochure could not be downloaded due to its large size and persistent timeout issues. This section will be updated once the full content is available.)
## ISO 9001 Certification
### ISO 9001:2015 Certificate
Videx UK Ltd is certified to ISO 9001:2015 for the design, manufacture, and supply of door entry and access control systems.
**Certificate Details:**
* **Standard:** ISO 9001:2015
* **Scope:** The design, manufacture, and supply of door entry and access control systems.
* **Certified Body:** SGS
## General Technical Information and Contact Details
**Southern Office:**
1 Osprey, Trinity Park, Trinity Way, London, E4 8TD
T: 0370 300 1240 • F: 020 8523 5825
**Northern Office:**
Unit 4-7 Chillingham Ind. Estate, Chapman Street, Newcastle Upon Tyne, NE6 2XX
T: 0370 300 1240 • F: 0191 224 1559
**Email:** sales@videxuk.com
**Website:** www.videxuk.com
=== ADDITIONAL RESEARCH ===
--- Videx 4000 Series GSM Intercom (GSM800E V&VK) Technical Documentation ---
GSM-800E V&VK
V1.0
Installation Manual
Programming
Installation
1) Before you install this equipment, please read this full manual.
2) Ensure that there is good network reception at the location where it will be installed.
Speech Unit
200mm min
4-5 feet minimum
3) For medium or low reception areas, to reduce audio interference on a call, install an optional external antenna. Ensure it is kept as high as possible, and ABOVE all electronics.
Programming is best done by SMS text. It can also be done by DTMF from a normal telephone.
1) First check reception. Send the following SMS to the unit... *20#
The unit should reply SIGNAL LEVEL = ?
Where ? will be between 1 and 31
Below 14 can cause problems with relay operation, or no voice from the gate to the house. Take action to improve reception.
1-12 Poor
13-20 Medium
21-31 Good
2) Program the numbers you wish the unit to dial when the call button is pressed, up to a maximum of 3 numbers. Each SMS must start with the pass code, default 1234, in the following format *12*1234#, followed immediately by a command. E.g to program the telephone number 0987654321, enter the following SMS..
Entrance Pillar Side View
Wiring
*12*1234#110987654321#
4) Carefully follow the wiring instructions. Additional wiring suggestions for electric strike lock and magnetic lock are shown overleaf.
Pass code Data Function code
Up to 3 numbers can be sent together in a single SMS as follows..
*12*1234#11tel.number1#12tel.number2#13tel.number3#
11 = Telephone number 1
12 = Telephone number 2
13 = Telephone number 3
3) It is recommended to change the “no answer” time if there is more than 1 number stored. This stops the unit ringing a number after a set time, and can be used to prevent voicemail answering the call. Send the following SMS..
*12*1234#52??# Where ?? can be 2 digits from 10-99 seconds, default is 20.
The unit can allow up to 100 telephone numbers to be stored, for users to be able to ring the system for automatic entry. This uses caller ID like a phone to determine the identity of the caller. First, the unit must know what country it is operating in.
4) Program the country code as follows..
Optional Antenna (Elevated position)
Speech panel
GSM module Intercom Transmitter
Shielded CAT5 cable 8 meters max. Keep short as possible for best audio quality.
*12*1234#71??#
Where ?? can be 1-3 digits. For uk, insert 44, for Ireland 353. Do not use any leading zeros.
5) Enter the telephone numbers required to have access control. Do not enter country code, just the complete number as you would dial it..
Up to 3 numbers can be sent together in the same SMS. Just
*12*1234#720987654321# add 72 then the number, then # each time. The pass code only needs to be put at the beginning of each new messge.
Additional Programming Parameters
GSM-3E
SIM card
5) Register your SIM card with the network, and check it works in a mobile phone first. If you are using a Pre-pay or Pay&Go SIM, it will need topped up first. Your SIM should be GSM compatible.
6) Ensure the power is OFF before inserting the SIM card.
7) Carefully slide the SIM holder in the OPEN direction, insert the SIM, and slide in the CLOSED direction to lock it in place. Do NOT Force or use a screwdriver!
8) After a final check of wiring, switch on the power.
9) Allow 20-30 seconds for the unit to boot up and detect the network. Once successful connection has been made, the unit will sound a confirmation tone and the status LED will begin flashing.
If there is a fault or problem, the unit will emit a series of bleeps or warning tones. If this occurs, check...
1) That the SIM card has been activated and has credit.
2) That the SIM card does not require a PIN code, disable this in a phone.
3) That the SIM card can make and received a call on a phone.
4) If the SIM card was purchased with a phone, that it is not locked to that phone. Call the network operator to check.
5) Switch off power, remove and reseat the SIM card and try again.
Code Description Default
01????# Change programming password. 1234
02????# Change access control password (allows users not in caller ID list to call intercom and use pass code to activate relay). 5678
03????# Change monitoring mode password (dial to listen in mode) 1212
1n*# Delete a button calling number, where n = number 1,2 or 3. N/A
3?# Speaker volume. Where ? = level 0 - 4 3
4?# Microphone volume. Where ? = level 0 - 4 3
51?# Relay time. Where ? = 1-9999 seconds. 1 sec
53??# Max call time. Where ??? = 005-999 seconds (3 digit code) 60 sec
55??# Max monitoring time (for listen in mode when calling the intercom) 00-60 mins. 00 = no limit. 10 min
57??# Unit can call or SMS service number by set duration to prevent SIM card deactivation if seldom used. 00-60 days. 00 = no inform. 00
58?# Choose between scheduled call to service number or send SMS to service number. ?=1 for SMS, 2 for call. 1
77number# Store service number to receive scheduled SMS or call from intercom. N/A
77*# Delete service number. N/A
65?# Dial in mode for withheld numbers or non stored numbers. 1 = answer the call & wait for pass code. 2 = answer the call & automatically activate 2 way speech. 1
73??# Delete phone number for caller ID access. N/A
73*# Delete all phone numbers for caller ID access. N/A
999# Restore defaults N/A
*21# Check stored numbers. Note: no pass code needed for this command. O = dial out number. I = Dial in number. N/A
Remember to begin each new SMS with pass code *12*1234#
Note: DTMF Programming is done by calling the unit, & entering the pass code first, then after a long single confirm tone, commands can be entered. A fault is indicated by 3 short bleeps.
Fault finding & FAQs
Additional Wiring Information
A/C Strike Lock Wiring
Q. The unit will not power up. No LEDs on.
A. Check power supply voltage is within 11.5V-12.5V DC.
GSM module DETECT GND PB GND N/O COM N/C VCC AC AC
A/C PSU for lock Strike lock
From 12v d.c. power supply Break Glass
Exit Button
N/O
C1 NC1 NO1
Optional emergency break glass unit
Keypad module
D/C Magnetic Lock Wiring
Q. The unit powers up but there is a bleeping from the door station.
A. This means the unit is not able to detect the network for some reason.
-Check the SIM card is activated and has calling credit.
-Power off the unit, remove the SIM and check it in a mobile phone to verify it can make a call.
-Check the SIM does not ask for a PIN code when put in a phone. If it does, then disable the PIN code request.
-Check the SIM is a standard GSM SIM, not 3G or 4G only SIM. If you are unsure, contact your SIM card provider to verify. Frequency of operation should be any one of the international quad band standards, 850 / 900 / 1800 / 1900 MHz.
-Check the reception is good. Poor reception is not sufficient.
-Check the antenna has been mounted as high as possible, not near large metal objects, or wet green shrubs etc.
-Check the antenna connection. Visually inspect that the centre pin inside the antenna is intact, and has not been pushed back inside the fitting.
Q. The unit calls the first number, but there is not enough time to answer before it diverts to the next number.
A. Increase the no answer time as per programming instructions.
GSM module DETECT GND PB GND N/O COM N/C VCC AC AC
Q. The unit calls the first number but voicemail comes on before it can ring the second number.
A. Decrease the no answer time as per programming instructions.
D/C PSU for lock
Recommend diode fitted here
Magnetic Lock
From 12v d.c. power supply Break Glass
Exit Button N/C C1 NC1 NO1
Optional emergency break glass unit
Keypad module
Keypad Programming (only for VK model)
Enter engineers code
Factory default is 111111
Press ENTER
Enter access code for relay 3
Press ENTER 4-8 digits
Press ENTER Enter pulse time for relay 1
Press ENTER Enter access code for relay 2
Q. There is no audio from the gate, but the person at the gate can hear ok.
A. This can be due to low reception.
-Check reception level by *20#.
-Change SIM card if necessary to another network which may have better coverage.
-Purchase a high gain antenna.
This may also be caused by either a defective microphone, or incorrect microphone wiring, or a short circuit by whiskers between the centre core and the shielding, or excessive microphone cable length.
Press ENTER
Confirm or change engineers code
Enter access code for relay 1
Enter pulse time for relay 2
Q. The caller ID part does not work.
A. Be sure to program the caller ID part under 72 feature. If your number is a private or number withheld, then it will not work.
Even if you have already programmed a number to receive a call from the intercom, if you also want that number to have caller ID access, it must be programmed under the 72 feature also.
Ensure the number is entered as you would normally dial it from another phone.
Do not put the country code in front of the number.
Enter the country code in which the unit is operating in separate under the 71 feature.
International callers ringing the intercom may not work.
Press ENTER
Enter pulse time for relay 3
Press ENTER
2 digits, 01-99. E.g. 03=3 sec
Press ENTER
FINISH Red LED should now be OFF
Q. The audio quality that can be heard on the remote telephone is poor or humming (buzzing).
A. A small amount of GSM buzz can be considered normal on GSM intercoms, but not so much that causes inability to hear the person speaking. This can be caused by the GSM antenna being mounted too close to the speech panel or not mounted high enough.
-Try earthling the speech panel chassis to 0V of the power supply.
-This is also a symptom of poor reception. Try above steps on checking and improving reception.
Q. The * or # key does not work when the intercom calls a phone.
A. Check if you can hear the relay clicking at the gate when the * or # key is pressed during a call. If it can be heard, then the system is working, check wiring between the relay and the lock or gate panel. If the relays do not make a clicking sound, then check this feature on a different mobile cell phone or landline. If it works on a different phone, check the settings on the phone in question under DTMF tones.
Failure of DTMF tones to operate correctly is also a symptom of low reception. Check steps above on improving reception. Try pressing the buttons longer when attempting to activate the gates or door.
User Manual
For GSM 800 Videx 4000 series Intercom
This GSM intercom system will call up to 3 telephone numbers in sequence when the call button is pressed.
There are several modes of operation depending on how the unit has been programmed by your installer. The following instructions will assume default programming.
Intercom calling your phone
Press * to open
OR
1 4 7 *
Call button pressed
2 5 8 0 END
Answer call.
Press # to hold open
3 6 9 #
and
Press 1 to release again (Only some gate systems allow hold open control, depending on manufacturer)
Default pass code 5678 is shown in all examples. This may have been changed by your installer.
Trigger Gate / Door
Latch or hold open gate / door
Unlatch gate / door
SEND SMS
SEND SMS
*33*5678#
*34*5678#
If limit switch fitted, check gate status..
Check stored numbers
SEND SMS
SEND SMS
SEND SMS
*35*5678#
*22#
*21#
1 2 3 1 2 3 2 3
5 6 4 5 6 4 5 6
8 9 7 8 9 7 8 9
HOLD OPEN FEATURE, OR “PARTY MODE”
0 systems #
Some allow*hold 0 open #control, depending
* gate
* 0 on #
1 4 7
manufacturer. Send the following SMS commands to control the gates..
1 2 3
4 5 6
Reply will indicate
9
7 8or closed.
opened
* 0 #
1 2 3
4 5 6
O = dial out number
9 for
I =7Dial 8
in number
caller ID0access.
#
*
Calling the intercom options
*33*5678#
Dialling…
MY GATE
1 4 7 *
END
Option 1) If your number is saved inside the intercom memory, just dial it and it will activate the door or gate without answering your call. The intercom will end the call for you.
2 5 8 0
3 6 9 #
END
Option 2) If your number is not saved in the intercom memory, it will answer the call. Enter the code on your telephone keypad to activate the door or gate (default code shown).
Fig.2 wiring diagram
IMPORTANT:
Do NOT drill holes in the top or near the top of the enclosure.
Do NOT use silicone sealants!
Intercom Transmitter
GSM 800
Keep short as possible, 8 meters max
Wiring
Button5
Button4
Button2
Button1
Egress
Mic
Speaker
- +
Button6
12v or 15v d.c. ONLY
WARNING
Do NOT use 24v ac.
2 P3 P4
3 1
C C1 P1 P2 S S1
Solid core of shield connected to 0V on PCB above for better audio quality.
Connect to the buttons module
Button1 Button2 Button3 Button4 Button5 Button6
Relay 1
Relay 2
Relay 3
SW2 SW1 NC3 NO3 C3 NC2 NO2 C2 NC1 NO1 C1 +
Gate Status
Button8
Button7
Button3
Press
Shielded CAT5
*
Reset Button
PWR IN
Speech Panel Connections
12v out +
Relay 1 Momentary
# Latch
1 Unlatch
Relay 2
7 Momentary
8 Latch
9 Unlatch
Press
GSM LED Status LED
Power LED
LOCK
OPEN
Antenna connector. Finger tighten only!
Keypad Connections (VK models only)
Microphone
--- Videx 8K Audiokit (8K-1/2 - 8K-1S/2S) Technical Documentation ---
Audiokit 8K Series
Art. 8K-1/2 - 8K-1S/2S Audiokit
GENERAL DIRECTIONS FOR INSTALLATION
In order to achieve the best results from the schematics described it is necessary to install only original VIDEX equipment, strictly keeping to the items indicated on each schematic and follow these General Directions for Installation:
• The system must be installed according to national rules in force, in any case the running of cables of any intercom unit must be carried out separately from the mains (see the next paragraph for connection to mains and power supply installation);
• All multipair cables should be compliant to CW1308 specification (0.5mm twisted pair telephone cable.
• Cables for speech line and service should have a max resistance of 10Ω
• Lock release wires should be doubled up (Lock release wires and power supply wires should have a max resistance of 3Ω);
• The cables sizes above can be used for distances up to 50m. On distances above 50m the cable sizes should be increased to keep the overall resistance of the cable below the RESISTANCES indicated above;
• Double check the connections before power up;
• Power up the system then check all functions.
CONNECTION TO MAINS AND POWER SUPPLY MOUNTING INSTRUCTIONS
The system must be installed according to national rules in force, in particular we recommend to:
• Connect the system to the mains through an all-pole circuit breaker which shall have contact separation of at least 3mm in each pole and shall disconnect all poles simultaneously;
• The all-pole circuit breaker shall be placed for easy access and the switch shall remain readily operable.
POWER SUPPLY INSTALLATION
• Remove the terminal side covers by unscrewing the retaining screws;
• Fix the power supply to a DIN bar or directly to the wall using two expansion type screws;
• Switch off the mains using the circuit breaker mentioned above and then make the connections as shown on the installation diagrams;
• Check the connections and secure the wires into the terminals;
• Replace the terminal covers and fix them using the relevant screws;
• When all connections are made, restore the mains.
Wiring Guide Line
All intercoms wiring must run separately from the mains cable.
The cable type should be CW1308 or an equivalent cable. The cable size should comply with the table below.
DISTANCE METERS CABLE SIZE (MM2)
50 0.35
100 0.5
200 0.75
300 1.0
400 1.5
Max resistance of all lines: 8 Ohm
Before powering the system up, the wiring should be double checked to ensure it complies with the wiring diagram supplied.
TROUBLE SHOOTING GUIDE
In the event of the system not functioning correctly when you power up, the following points can be checked (a multimeter will be needed).
SYSTEM DEAD
• Check mains input to the transformer.
• Check the 12Vdc (+12 terminal) output from the power supply.
• Check fuses.
• Check for shorts on power supply wires.
SPEECH & LOCK WORKS BUT NO ELECTRONIC CALL TONE
• Check the link between “C” and “C1” terminals of the speaker unit.
• Call wire to terminal “4” of the handset broken on in short circuit; check the walk of the call wire.
NO SPEECH FROM THE DOOR PANEL
• Check and/or adjust the volume operating on trimmers controls on rear of speaker unit.
• Check the wire from terminal “2” of the speaker unit to terminal “2” of the handset.
NO SPEECH FROM THE HANDSET
• Check and/or adjust the volume operating on trimmers controls on rear of speaker unit.
• Check the wire from terminal “1” of the speaker unit to terminal “1” of the handset.
LOCK DOES NOT WORK
• Check on the handset the link between terminals “1” and “5”.
• Check the 13Vac output on the transformer.
• Check the wires of the electric lock.
• Wires section not in conformity with the table above.
FEEDBACK PROBLEM (LARSEN EFFECT)
• Check that the handset microphone is firmly fitted inside its housing.
• Check that the speaker unit microphone is firmly fitted inside its housing and nothing is obstructing the microphone hole.
• Adjust the volume operating on trimmer controls on rear of the speaker unit.
HUM ON THE SPEECH LINES
• Check that system cables are not running close to any high voltage or mains cables.
• Check that the system is wired exactly as shown on the wiring diagram.
WE RECOMMEND THIS EQUIPMENT IS INSTALLED BY A COMPETENT ELECTRICIAN, SECURITY OR COMMUNICATIONS ENGINEER.
If further assistance is required, call the technical help desk on 0191-2243174 for uk customers or +39 0734631669 for other countries.
8000 Series Surface and flush mounting door station installation
INSTALLING A FLUSH MOUNTING DOOR STATION
1. Mount back box S (Fig. 2) at 165 cm from ground level (Fig. 1);
2. If more than one flush box is needed, connect them by using the plastic spacers provided A (Fig. 2);
3. If necessary finish and clean properly the module support fixing holes and all other holes B (Fig. 2);
4. A rainshield D (Fig. 3 & 4) can be mounted using the fixing screws G (Fig. 4) to conceal possible wall finishing defects and protect against rain;
In order to prevent water ingress we highly recommend using a silicon sealant between the wall and the back box and between the wall and the rainshield D (Fig.3);
5. Remove the fixing screws H (Fig. 5) and remove the plastic cover E (Fig. 5) of the module support;
6. Insert the modules F (Fig. 6) according the required configuration;
7. Insert the microphone of the door unit amplifier into the microphone hole X (Fig. 7);
8. Secure the modules by refitting the plastic cover E (Fig. 8) and using the screws H (Fig. 8);
9. Insert the hinge I (Fig. 9) and fix it with the two screws K (Fig. 9) provided;
10. Make all connections following accurately the wiring diagram provided. Check the installation and if necessary adjust speech levels using volume controls L (Fig. 9);
11. Lever the support R (Fig. 10) upwards and fix it to the back box with the screw M (Fig. 11) using an alan key P (Fig. 11);
12. Conceal the screw using the plastic cover N (Fig. 11) provided.
INSTALLING A SURFACE MOUNTING DOOR STATION
Fix the surface box on the wall at a distance of 165 cm between the top of the box and the ground (Fig. 1).
In order to prevent water ingress we highly recommend using a silicon sealant between the wall and the back box J (Fig.12) and around all holes W (Fig.12).
To complete the installation follow the same steps described above for the flush box.
Note: if additional holes are made in the box or rainshield, oxidation problems may appear unless the unprotected metal is coated with a protective paint.
HOW TO REMOVE THE CARD NAME HOLDER
• To avoid damage to the module front plate, tape the side that will be in contact with the screwdriver blade;
• lnsert a flat screwdriver into the card-holder hole as shown in Fig. 13;
• Move the screwdriver to the left as shown in Fig. 14 to extract the card name holder;
• Edit the card name then replace it inside the holder and refit: insert the holder inside its housing from the left or right side then push the other side until it clips into place.
MANUFACTURER
VIDEX ELECTRONICS S.P.A.
Via del Lavoro, 1 - 63846 Monte Giberto (FM) Italy
Tel (+39) 0734 631669 - Fax (+39) 0734 632475
www.videx.it - info@videx.it
CUSTOMER SUPPORT
All Countries:
VIDEX ELECTRONICS S.P.A.
www.videx.it - technical@videx.it
Tel: +39 0734-631669 - Fax: +39 0734-632475
UK Customers:
VIDEX SECURITY LTD
www.videx-security.com
Tech Line: 0191 224 3174 - Fax: 0191 224 1559
Main UK office:
VIDEX SECURITY LTD
1 Osprey Trinity Park
Trinity Way
LONDON E4 8TD
Phone: (+44) 0870 300 1240
Fax: (+44) 020 8523 5825
www.videx-security.com
marketing@videx-security.com
Northern UK office:
VIDEX SECURITY LTD
Unit 4-7
Chillingham Industrial Estate
Chapman Street
NEWCASTLE UPON TYNE - NE6 2XX
Tech Line: (+44) 0191 224 3174
Phone: (+44) 0870 300 1240
Fax: (+44) 0191 224 1559
Greece office:
VIDEX HELLAS Electronics
48 Filolaou Str.
11633 ATHENS
Phone: (+30) 210 7521028
(+30) 210 7521998
Fax: (+30) 210 7560712
www.videx.gr
videx@videx.gr
Danish office:
VIDEX DANMARK
Hammershusgade 15
DK-2100 COPENHAGEN
Phone: (+45) 39 29 80 00
Fax: (+45) 39 27 77 75
www.videx.dk
videx@videx.dk
The product is CE marked demonstrating its conformity and is for distribution within all member states of the EU with no restrictions. This product follows the provisions of the European Directives 2014/30/EU (EMC); 2014/35/EU (LVD); 2011/65/EU (RoHS): CE marking 93/68/EEC.
Benelux office:
VIDEX BENELUX
E3 Iaan, 93
B-9800 DEINZE
Phone: (+32) 9 380 40 20
Fax: (+32) 9 380 40 25
www.videxbenelux.be
info@videxbenelux.be
--- Videx 8K/380/CL Series Audio Kit Technical Documentation ---
Audiokit 8K Series
Art. 8KC/380 Digiphone kit with telephone interface
GENERAL DIRECTIONS FOR INSTALLATION
In order to achieve the best results from the schematics described it is necessary to install only original VIDEX equipment, strictly keeping to the items indicated on each schematic and follow these General Directions for Installation:
• The system must be installed according to national rules in force, in any case the running of cables of any intercom unit must be carried out separately from the mains (see the next paragraph for connection to mains and power supply installation);
• All multipair cables should be compliant to CW1308 specification (0.5mm twisted pair telephone cable.
• Cables for speech line and service should have a max resistance of 10Ω
• Lock release wires should be doubled up (Lock release wires and power supply wires should have a max resistance of 3Ω);
• The cables sizes above can be used for distances up to 50m. On distances above 50m the cable sizes should be increased to keep the overall resistance of the cable below the RESISTANCES indicated above;
• Double check the connections before power up;
• Power up the system then check all functions.
CONNECTION TO MAINS AND POWER SUPPLY MOUNTING INSTRUCTIONS
The system must be installed according to national rules in force, in particular we recommend to:
• Connect the system to the mains through an all-pole circuit breaker which shall have contact separation of at least 3mm in each pole and shall disconnect all poles simultaneously;
• The all-pole circuit breaker shall be placed for easy access and the switch shall remain readily operable.
POWER SUPPLY INSTALLATION
• Remove the terminal side covers by unscrewing the retaining screws;
• Fix the power supply to a DIN bar or directly to the wall using two expansion type screws;
• Switch off the mains using the circuit breaker mentioned above and then make the connections as shown on the installation diagrams;
• Check the connections and secure the wires into the terminals;
• Replace the terminal covers and fix them using the relevant screws;
• When all connections are made, restore the mains.
Art. 8800 - Art. 8800-3 Digital codelock module
DESCRIPTION
Access control system with 2 codes and 2 Relay outputs for Art. 8800 (3 codes and 3 Relay outputs for Art. 8800-3).
• Engineer’s code to enter into the “Programming Menu” ( from 4 to 8 digits).
• Programming of the activation time of each relay from 1 up to 99 seconds or latching.
• Possibility to activate relay 1 by shorting terminal ”SW1” to GND and relay 2 by shorting terminal “SW2” to GND. Both relays will operate for the programmed time.
• Keypad gives an acoustic (buzzer) signal during the entering of codes and a continuous melody for 4 or more seconds, according to the number of mistakes (self protection).
• Keypad includes panel illumination and 2 LED’s to show the following:
»» Correct relay code (green LED on for 2 seconds).
»» Red LED to indicate when in the “programming menu”.
MODELS
Art. 8800: Module 2 Relay with keypad illumination LEDs
Art. 8800-3: Module 3 Relay with keypad illumination LEDs
OPERATION
To use the system, type in the programmed code and press “ENTER” , the green LED will illuminate and the relay will operate for the programmed time.To cancel remain open time, type in the same code and press “CLEAR”. If a wrong code is entered, a continuous melody will sound for 4 or more seconds, according to the number of mistakes.
INITIALIZATION
When the installation is concluded and carried out according to the wiring diagram, power up the system and program it by following the “VX8800 PROGRAMMING” Flow Chart.
PROGRAMMING
Refer also to flow chart.
• Enter “ENGINEER’S CODE”: first time type six times “1” (111111 factory preset) and press ENTER (The red LED will illuminate).
• Confirm “ENGINEER’S CODE” (typing again the same) or type the new code (4 to 8 digits) then press ENTER (Melody). Pressing twice the ENTER button without changing the “ENGINEER’S CODE”, will exit from the programming.
• Enter the code (4 to 8 digits) to enable “RELAY 1” (ACCESS 1) or re-enter the existing code then press ENTER (Melody).
• Enter the “RELAY 1” operation time (2 digits 01 to 99 I.E. 05=5 seconds, 00= remain open time) or re-enter the existing time then press ENTER (Melody).
• Enter the code (4 to 8 digits) to enable “RELAY 2” (ACCESS 2) or re-enter the existing code then press ENTER (Melody).
• Enter the “RELAY 2” operation time (2 digits 01 to 99 I.E. 05=5 seconds, 00=remain open time) or re-enter the existing time then press ENTER (Melody).
• Enter the code (4 to 8 digits) to enable “RELAY 3” (ACCESS 3 only for Art. 8800-3) or re-enter the existing code then press ENTER (Melody).
• Enter the “RELAY 3” (only for Art. 8800-3) operation time (2 digits 01 to 99 I.E. 05=5 seconds, 00=remain open time) or re-enter the existing time then press ENTER (Melody).
• The system is ready to use (the red LED will be off ).
INSTRUCTION TO RETURN SYSTEM TO PRESET ENGINEER’S FACTORY CODE
• Turn off power to code lock.
• Keep “ENTER” button pressed while turning back on the power to the code lock.
• Release “ENTER” button.
• The master code is now set at factory engineer’s code “111111” (six times “1”).
• Proceed with programming for a new system.
NOTES
• To switch off any relay while operating, type in the relevant code then press the “CLEAR” button.
• To operate relays together, set the same code for each relay.
• If a wrong code is entered, the system will lock out for 5 seconds which will increase each time a wrong code is entered. The system will operate only when the correct code is entered.
LO
A varistor must be fitted across the terminals on AC lock release (Fig.1A) and a diode must be fitted across the terminals on a DC lock release (Fig.1B) to suppress back EMF voltages. Connect the components to the lock releases as shown in figures.
RE-PROGRMMING GUIDE
Engineer’s code
Relay 1 code
RE-ENTER THE ENGINEER’S CODE
Alternatively enter a new engineer’s code (4 to 8 digits)
ENTER ACCESS CODE
Relay code (4-8 digits) operate the door or gate.**
ENTER ACCESS TIME
Two digits (01-99 sec or 00 for remain open)
YES Repeat steps for relay 2 and relay 3***
Relay 2 code
Relay 3 code***
Relay 1 time
Relay 2 time
Relay 3 time***
Notes:
* If the red light does not illuminate, the engineer’s code is incorrect. Follow instructions to return system to preset engineer’s factory code.
** On the first loop of the flow chart its relay 1, second loop is relay 2 and third loop is relay 3.
*** Only for Art. 8800-3
MORE DOORS?
NO PRESS ENTER TWICE TO EXIT PROGRAMMING
ART. 8800 TERMINALS
SW1 Relay 1 command signal (active low)
SW2 Relay 2 command signal (active low)
NC2 Relay 2 normally closed contact
NO2 Relay 2 normally open contact
C2 Relay 2 common contact
NC1 Relay 1 normally closed contact
NO1 Relay 1 normally open contact
C1 Relay 1 common contact
ART. 8800-3 TERMINALS
NO3 Relay 3 normally open contact
C3 Relay 3 common contact
NC2 Relay 2 normally closed contact
NO2 Relay 2 normally open contact
C2 Relay 2 common contact
NC1 Relay 1 normally closed contact
NO1 Relay 1 normally open contact
C1 Relay 1 common contact
Max 24Vac/dc 5A
/+ 12/24Vac/dc power input
/–
TECHNICAL SPECIFICATIONS
Power requirements: 12/24V AC/DC, 2VA
Power Consumption: On AC Stand-by: 82mA Operating: 125mA
Working Temperature: -10 +50° C
Max 24Vac/dc 5A
/+ 12/24Vac/dc power input
/–
On DC Stand-by: 21.5mA Operating: 35.0mA
Wiring Guide Line
All intercoms wiring must run separately from the mains cable.
The cable type should be CW1308 or an equivalent cable. The cable size should comply with the table below.
DISTANCE METERS CABLE SIZE (MM2)
50 0.35
100 0.5
200 0.75
300 1.0
400 1.5
Max resistance of all lines: 8 Ohm
Before powering the system up, the wiring should be double checked to ensure it complies with the wiring diagram supplied.
TROUBLE SHOOTING GUIDE
In the event of the system not functioning correctly when you power up, the following points can be checked (a multimeter will be needed).
SYSTEM DEAD
• Check mains input to the transformer.
• Check the 12Vdc (+12 terminal) output from the power supply.
• Check fuses.
• Check for shorts on power supply wires.
SPEECH & LOCK WORKS BUT NO ELECTRONIC CALL TONE
• Check the link between “C” and “C1” terminals of the speaker unit.
• Call wire to terminal “4” of the handset broken on in short circuit; check the walk of the call wire.
NO SPEECH FROM THE DOOR PANEL
• Check and/or adjust the volume operating on trimmers controls on rear of speaker unit.
• Check the wire from terminal “2” of the speaker unit to terminal “2” of the handset.
NO SPEECH FROM THE HANDSET
• Check and/or adjust the volume operating on trimmers controls on rear of speaker unit.
• Check the wire from terminal “1” of the speaker unit to terminal “1” of the handset.
LOCK DOES NOT WORK
• Check on the handset the link between terminals “1” and “5”.
• Check the 13Vac output on the transformer.
• Check the wires of the electric lock.
• Wires section not in conformity with the table above.
FEEDBACK PROBLEM (LARSEN EFFECT)
• Check that the handset microphone is firmly fitted inside its housing.
• Check that the speaker unit microphone is firmly fitted inside its housing and nothing is obstructing the microphone hole.
• Adjust the volume operating on trimmer controls on rear of the speaker unit.
HUM ON THE SPEECH LINES
• Check that system cables are not running close to any high voltage or mains cables.
• Check that the system is wired exactly as shown on the wiring diagram.
WE RECOMMEND THIS EQUIPMENT IS INSTALLED BY A COMPETENT ELECTRICIAN, SECURITY OR COMMUNICATIONS ENGINEER.
If further assistance is required, call the technical help desk on 0191-2243174 for uk customers or +39 0734631669 for other countries.
8000 Series Surface and flush mounting door station installation
INSTALLING A FLUSH MOUNTING DOOR STATION
1. Mount back box S (Fig. 2) at 165 cm from ground level (Fig. 1);
2. If more than one flush box is needed, connect them by using the plastic spacers provided A (Fig. 2);
3. If necessary finish and clean properly the module support fixing holes and all other holes B (Fig. 2);
4. A rainshield D (Fig. 3 & 4) can be mounted using the fixing screws G (Fig. 4) to conceal possible wall finishing defects and protect against rain;
In order to prevent water ingress we highly recommend using a silicon sealant between the wall and the back box and between the wall and the rainshield D (Fig.3);
5. Remove the fixing screws H (Fig. 5) and remove the plastic cover E (Fig. 5) of the module support;
6. Insert the modules F (Fig. 6) according the required configuration;
7. Insert the microphone of the door unit amplifier into the microphone hole X (Fig. 7);
8. Secure the modules by refitting the plastic cover E (Fig. 8) and using the screws H (Fig. 8);
9. Insert the hinge I (Fig. 9) and fix it with the two screws K (Fig. 9) provided;
10. Make all connections following accurately the wiring diagram provided. Check the installation and if necessary adjust speech levels using volume controls L (Fig. 9);
11. Lever the support R (Fig. 10) upwards and fix it to the back box with the screw M (Fig. 11) using an alan key P (Fig. 11);
12. Conceal the screw using the plastic cover N (Fig. 11) provided.
INSTALLING A SURFACE MOUNTING DOOR STATION
Fix the surface box on the wall at a distance of 165 cm between the top of the box and the ground (Fig. 1).
In order to prevent water ingress we highly recommend using a silicon sealant between the wall and the back box J (Fig.12) and around all holes W (Fig.12).
To complete the installation follow the same steps described above for the flush box.
Note: if additional holes are made in the box or rainshield, oxidation problems may appear unless the unprotected metal is coated with a protective paint.
HOW TO REMOVE THE CARD NAME HOLDER
• To avoid damage to the module front plate, tape the side that will be in contact with the screwdriver blade;
• lnsert a flat screwdriver into the card-holder hole as shown in Fig. 13;
• Move the screwdriver to the left as shown in Fig. 14 to extract the card name holder;
• Edit the card name then replace it inside the holder and refit: insert the holder inside its housing from the left or right side then push the other side until it clips into place.
MANUFACTURER
VIDEX ELECTRONICS S.P.A.
Via del Lavoro, 1 - 63846 Monte Giberto (FM) Italy
Tel (+39) 0734 631669 - Fax (+39) 0734 632475
www.videx.it - info@videx.it
CUSTOMER SUPPORT
All Countries:
VIDEX ELECTRONICS S.P.A.
www.videx.it - technical@videx.it
Tel: +39 0734-631669 - Fax: +39 0734-632475
UK Customers:
VIDEX SECURITY LTD
www.videx-security.com
Tech Line: 0191 224 3174 - Fax: 0191 224 1559
Main UK office:
VIDEX SECURITY LTD
1 Osprey Trinity Park
Trinity Way
LONDON E4 8TD
Phone: (+44) 0870 300 1240
Fax: (+44) 020 8523 5825
www.videx-security.com
marketing@videx-security.com
Northern UK office:
VIDEX SECURITY LTD
Unit 4-7
Chillingham Industrial Estate
Chapman Street
NEWCASTLE UPON TYNE - NE6 2XX
Tech Line: (+44) 0191 224 3174
Phone: (+44) 0870 300 1240
Fax: (+44) 0191 224 1559
Greece office:
VIDEX HELLAS Electronics
48 Filolaou Str.
11633 ATHENS
Phone: (+30) 210 7521028
(+30) 210 7521998
Fax: (+30) 210 7560712
www.videx.gr
videx@videx.gr
Danish office:
VIDEX DANMARK
Hammershusgade 15
DK-2100 COPENHAGEN
Phone: (+45) 39 29 80 00
Fax: (+45) 39 27 77 75
www.videx.dk
videx@videx.dk
The product is CE marked demonstrating its conformity and is for distribution within all member states of the EU with no restrictions. This product follows the provisions of the European Directives 2014/30/EU (EMC); 2014/35/EU (LVD); 2011/65/EU (RoHS): CE marking 93/68/EEC.
Benelux office:
VIDEX BENELUX
E3 Iaan, 93
B-9800 DEINZE
Phone: (+32) 9 380 40 20
Fax: (+32) 9 380 40 25
www.videxbenelux.be
info@videxbenelux.be
--- Videx 4K Series Audio Kit with Codelock Technical Documentation ---
Audiokit 4KC Series
Art. 4KC/3011-3012-3111-3112-3102G Audiokit with digital codelock
GENERAL DIRECTIONS FOR INSTALLATION
In order to achieve the best results from the schematics described it is necessary to install only original VIDEX equipment, strictly keeping to the items indicated on each schematic and follow these General Directions for Installation:
• The system must be installed according to national rules in force, in any case the running of cables of any intercom unit must be carried out separately from the mains (see the next paragraph for connection to mains and power supply installation);
• All multipair cables should be compliant to CW1308 specification (0.5mm twisted pair telephone cable);
• Cables for speech line and service should have a max resistance of 10Ω;
• Lock release wires should be doubled up (Lock release wires and power supply wires should have a max resistance of 3Ω);
• The cables sizes above can be used for distances up to 50m. On distances above 50m the cable sizes should be increased to keep the overall resistance of the cable below the RESISTANCES indicated above;
• Double check the connections before power up; 3 Power up the system then check all functions.
CONNECTION TO MAINS AND POWER SUPPLY MOUNTING INSTRUCTIONS
The system must be installed according to national rules in force, in particular we recommend to:
• Connect the system to the mains through an all-pole circuit breaker which shall have contact separation of at least 3mm in each pole and shall disconnect all poles simultaneously;
• The all-pole circuit breaker shall be placed for easy access and the switch shall remain readily operable.
POWER SUPPLY INSTALLATION
• Remove the terminal side covers by unscrewing the retaining screws;
• Fix the power supply to a DIN bar or directly to the wall using two expansion type screws;
• Switch off the mains using the circuit breaker mentioned above and then make the connections as shown on the installation diagrams;
• Check the connections and secure the wires into the terminals;
• Replace the terminal covers and fix them using the relevant screws;
• When all connections are made, restore the mains.
LOCK RELEASE BACK EMF PROTECTION
A varistor must be fitted across the terminals on AC lock release (Fig.1A) and a diode must be fitted across the terminals on a DC lock release (Fig.1B) to suppress back EMF voltages. Connect the components to the lock releases as shown in figures.
Wiring Guide Line
All intercoms wiring must run separately from the mains cable.
The cable type should be CW1308 or an equivalent cable. The cable size should comply with the table below.
DISTANCE METERS CABLE SIZE (MM2)
50 0.35
100 0.5
200 0.75
300 1.0
400 1.5
Max resistance of all lines: 8 Ohm
Before powering the system up, the wiring should be double checked to ensure it complies with the wiring diagram supplied.
TROUBLE SHOOTING GUIDE
In the event of the system not functioning correctly when you power up, the following points can be checked (a multimeter will be needed).
SYSTEM DEAD
• Check mains input to the transformer.
• Check the 12Vdc (+12 terminal) output from the power supply.
• Check fuses.
• Check for shorts on power supply wires.
SPEECH & LOCK WORKS BUT NO ELECTRONIC CALL TONE
• Check the link between “C” and “C1” terminals of the speaker unit.
• Call wire to terminal “4” of the handset broken on in short circuit; check the walk of the call wire.
NO SPEECH FROM THE DOOR PANEL
• Check and/or adjust the volume operating on trimmers controls on rear of speaker unit.
• Check the wire from terminal “2” of the speaker unit to terminal “2” of the handset.
NO SPEECH FROM THE HANDSET
• Check and/or adjust the volume operating on trimmers controls on rear of speaker unit.
• Check the wire from terminal “1” of the speaker unit to terminal “1” of the handset.
LOCK DOES NOT WORK
• Check on the handset the link between terminals “1” and “5”.
• Check the 13Vac output on the transformer.
• Check the wires of the electric lock.
• Wires section not in conformity with the table above.
FEEDBACK PROBLEM (LARSEN EFFECT)
• Check that the handset microphone is firmly fitted inside its housing.
• Check that the speaker unit microphone is firmly fitted inside its housing and nothing is obstructing the microphone hole.
• Adjust the volume operating on trimmer controls on rear of the speaker unit.
HUM ON THE SPEECH LINES
• Check that system cables are not running close to any high voltage or mains cables.
• Check that the system is wired exactly as shown on the wiring diagram.
WE RECOMMEND THIS EQUIPMENT IS INSTALLED BY A COMPETENT ELECTRICIAN, SECURITY OR COMMUNICATIONS ENGINEER.
If further assistance is required, call the technical help desk on 0191-2243174 for uk customers or +39 0734631669 for other countries.
4000 Series Surface and flush mounting door station installation
INSTALLING A SURFACE MOUNT DOOR STATION
1. Place the surface box against the wall (165-170cm between the top of the box and the floor level as shown in Fig. 1) and mark the fixing holes for the wall plugs and the hole for the cables E (fig. 2). Observe the orientation of the box with the hinge on the left;
In order to prevent water ingress we highly recommend using a silicon sealant between the wall and the back box C (Fig.3) and around all holes D (Fig.3);
2. As shown on Fig. 2, drill the fixing holes A, insert the wall plugs B and feed the cables E through a previously opened hole in the box. Observe the direction of the box ensuring the hinge is on the left and take care that the box profile is in line with the finished wall profile;
3. Apply the Y silicon sealant on top of each module as shown in Fig. 4;
4. Before installation of the module support frame, hook the modules G to the support frame H as shown in Fig. 5 then, as shown in Fig. 6, fit the two anti-tampering locks W for each module (do the same for the second module support frame);5. When you have more than one support frame, hook the support frame to the surface box starting from the left. For convenience we will described how to attach the left frame but the same must be carried out for the right frame. As shown in Fig. 7, hook the module support frame H (complete with modules) to the surface box C moving the frame as suggested from p
6. As shown on Fig. 9, pull back the module support frame H while moving it slightly to the left as suggested by the pointers;
7. As shown in Fig. 10, open the module support frame H as suggested by the pointer, hook the hinge locks N to the hinges M, make the required connections using the screwdriver provided P (flat blade end) and make the required adjustment by adjusting the settings (through openings O) and adjust trimmers;
8. Repeat the same operations described above for the second module support frame (or for the third if available);
9. When the system has been tested and is working correctly, move back the module support frames carefully, fix them to the surface box using the screwdriver provided P (torx end) and the pin machine torx screws Q (Fig. 11). Note: do not over tighten the screws more than is necessary.
INSTALLING A FLUSH MOUNTING DOOR STATION
When flush mounting and the number of modules is greater than 3, the required back boxes need to be linked together (before embedding them in the wall) as shown on Fig. 14, 15 and 16:
• Arrange the back boxes and remove knockouts to allow cables to be fed from one back box to the other;
• Hook the spacers to first back box then hook the second back box to obtain the result shown on Fig. 16;
1. Protect the module support frame fixing holes from dust then embed the back box into the wall (165-170cm between the top of the box and the floor level as shown on the Fig. 1) feeding the cables E (Fig. 2) through a previously opened hole in the box. Observe the direction of the box ensuring the hinge is on the left and take care that the box profile is in line with the finished wall profile;
In order to prevent water ingress we highly recommend using a silicon sealant between the wall and the back box H (Fig.12);
2. Continue from step 4 of surface mounting instructions , but at step 7 hook the hinge locks N as shown on Fig. 13.
Note: if additional holes are made in the surface box, oxidation problems may appear unless the unprotected metal is coated with a protective paint.
NOTES
• The screwdriver’s blade has two sides, one flat and one torx, to select one of them unplug the blade from the screwdriver body and plug it into the required side.
• The example shows the use of only one back box bottom hole for wires, this is done to keep file drawings clear. Naturally the installer can use the left hole or the right or both if required.
HOW TO REMOVE THE CARD NAME HOLDER
• To avoid damage to the module front plate, tape the side that will be in contact with the screwdriver blade;
• lnsert the screwdriver (flat side) into the card-holder hole as shown in Fig. 17;
• Move the screwdriver to the left as shown in Fig. 18 to extract the card name holder;
• Edit the card name then replace it inside the holder and refit: insert the holder inside its housing from the left or right side then push the other side until it clips into place.
MANUFACTURER
VIDEX ELECTRONICS S.P.A.
Via del Lavoro, 1 - 63846 Monte Giberto (FM) Italy
Tel (+39) 0734 631669 - Fax (+39) 0734 632475
www.videx.it - info@videx.it
CUSTOMER SUPPORT
All Countries:
VIDEX ELECTRONICS S.P.A.
www.videx.it - technical@videx.it
Tel: +39 0734-631669 - Fax: +39 0734-632475
UK Customers:
VIDEX SECURITY LTD
www.videx-security.com
Tech Line: 0191 224 3174 - Fax: 0191 224 1559
Main UK office:
VIDEX SECURITY LTD
1 Osprey Trinity Park
Trinity Way
LONDON E4 8TD
Phone: (+44) 0870 300 1240
Fax: (+44) 020 8523 5825
www.videx-security.com
marketing@videx-security.com
Northern UK office:
VIDEX SECURITY LTD
Unit 4-7
Chillingham Industrial Estate
Chapman Street
NEWCASTLE UPON TYNE - NE6 2XX
Tech Line: (+44) 0191 224 3174
Phone: (+44) 0870 300 1240
Fax: (+44) 0191 224 1559
Greece office:
VIDEX HELLAS Electronics
48 Filolaou Str.
11633 ATHENS
Phone: (+30) 210 7521028
(+30) 210 7521998
Fax: (+30) 210 7560712
www.videx.gr
videx@videx.gr
Danish office:
VIDEX DANMARK
Hammershusgade 15
DK-2100 COPENHAGEN
Phone: (+45) 39 29 80 00
Fax: (+45) 39 27 77 75
www.videx.dk
videx@videx.dk
The product is CE marked demonstrating its conformity and is for distribution within all member states of the EU with no restrictions. This product follows the provisions of the European Directives 2014/30/EU (EMC); 2014/35/EU (LVD); 2011/65/EU (RoHS): CE marking 93/68/EEC.
Benelux office:
VIDEX BENELUX
E3 Iaan, 93
B-9800 DEINZE
Phone: (+32) 9 380 40 20
Fax: (+32) 9 380 40 25
www.videxbenelux.be
info@videxbenelux.be
--- Videx GSM4K Technical Manual ---
GSM4K (4000 series GSM audio intercom)
EU RoHS DECLARATION OF CONFORMITY
Telit Communications certifies that the GL865-QUAD V3 (Quad Band GSM850/EGSM900/DCS1800/PCS1900 GPRS Wireless Module) is in conformity with Directive 2011/65/EU of the European Parliament and the Council of 8th June 2011 on the restriction of the use of certain hazardous substances in electrical and electronic equipment. The conformity with the applicable requirements of the Directive 2011/65/EU has been demonstrated against the following harmonized standard: EN 50581:2012 Technical Documentation for the assessment of electrical and electronic products with respect to the restriction of hazardous substances.
WARNING!
To comply with FCC RF exposure requirements, a separation distance of 20cm (7.87”) or more must be maintained between the antenna of this product and all persons.
Separate FCC approval for this product is not required as it will be classed as a fixed installation.
THIS PRODUCT IS NOT DESIGNED TO BE USED AS AN EMERGENCY CALL POINT.
CUSTOMER SUPPORT
VIDEX SECURITY LTD
CE conformity marking indicates that the product respects the requirements of the applicable European Community Directives in force specifically EMC 2004/108/ECC, LVD 2006/95/ECC and CE-MARKING 93/68/ECC. CE marking is applied by the manufacturer (or party delegated to do so by the manufacturer) under their own responsibility. It was created to eliminate obstacles to the circulation of products in European Union Member States by harmonising different national standards.
www.videxuk.com
Tech Line: 0191 224 3174
Fax: 0191 224 1559
Email: tech@videxuk.com
MANUAL INTRODUCTION
The information in this manual is intended as an installation and commissioning guide for the 4000 series GSM PRO audio intercom system. This manual should be read carefully before the installation commences. Any damage caused to the equipment due to faulty installation where the information in this manual has not been followed is not the responsibility of Videx Security Ltd.
It is recommended that the GSM PRO audio intercom is installed by a competent electrician, security or communications engineer.
VIDEX run free training courses for engineers who are unfamilier or who have not installed this system before. Technical help is also available on 0191 224 3174 during office hours (8:30am - 5:00pm MON to FRI) or via e-mail: tech@videxuk.com.
A copy of this Technical Manual can also be downloaded from the Videx website: www.videxuk.com.
SYSTEM INTRODUCTION
The system is designed to work on the same technology as mobile phones. It enables a call to be made from an entry point (door, gate etc), to any telephone number (mobile or land line). Up to 50 call buttons can be connected to the door panel, each able to call four telephone numbers (if the first is busy or not answered, the call can be diverted to up to three different numbers). Features of the system include:
• A dry contact relay output.
• Two open collector auxiliary outputs.
• Two auxiliary inputs.
• A push to exit input.
• Integrated Proximity Access Control (up to 1000 proximity fobs or cards can be stored, these fobs/cards when presented to the name plate window on the GSM PRO intercom will activate the door/gate relay).
• Call progress speech annunciation and call progress LED indication.
• Dial to Open facility (this feature enables up to 1000 stored numbers to dial the GSM PRO intercom, the intercom panel will not answer these calls, but will activate the door/gate relay without being charged for the call).
• Programmable timeband facility.
• Micro USB connection (for ease of programming using the GSMSK PC software).
• Integrated bootloader function (for updating intercom panel firmware via the GSMSK PC software).
• Event logging system (which can record up to 4000 events).
Programming of the telephone numbers and the additional features, including programming key fobs for the integrated proximity access, can be carried out via text messaging (refer to pages 28 to 45) or PC using the GSMSK PC software (refer to the GSMSK PC software manual).
A SIM card is required for this product but not supplied. The GSM PRO intercom can only accept a standard size SIM card (refer to SIM card size chart on page 5), both a micro-SIM and nano-SIM are not suitable. It is recommended to choose the SIM card which has the best coverage for the area in which the intercom panel will be installed. Both contract and ‘Pay as you go’ SIM cards can be used, however if using a ‘Pay as you go’ we would recommend setting up an automatic top up to avoid running short on credit and losing the use of the intercom panel.
Network Provider Selection
It is imperative that for the reliable operation of the system that the best network provider for the area is selected. Problems such as network disconnection can occur if the provider has signal or interference problems for that area. We would recommend using a GSM signal strength meter to survey the intended antenna location.
As an initial check we also recommend visiting the ofcom website www.sitefinder.ofcom.org.uk and enter the postcode of the intended installation. This will show all transmitters in the area. It is advised to choose the closest one or if there are many then choose a transmitter working on 900MHz as this frequency works best through obstacles such as walls, buildings etc. The antenna should always be mounted vertically at the highest point possible. Metal structures and sources of interference such as power cables, control panels etc. can affect signals and so the antenna should be mounted away from these.
When registering a new SIM you may be asked for the IMEI number. This is the unique serial number of the GSM intercom. This number is located internally on the main hardware chip inside the GSM PRO module. To gain access to the GSM module and obtain this number the module will have to be opened. It is recommended that you contact Videx Technical on tel: 0191 224 3174 for advise on how to do this. The IMEI number is printed on the Telit chip label below the chip model number, as shown in Fig.1.
PRECAUTIONARY ADVICE
• When mounting the GSM antenna, choose a location which is away from human interaction and away from the intercom panel. Route the GSM antenna cable from the intercom panel so that it is separate from the power supply cables and microphone wire.
• Always ensure the power is switched OFF to the intercom panel before inserting or removing the SIM card.
• New SIM cards will need registering with the network service provider before they can be used. Full details of how this is done can normally be found in the SIM card pack. It will normally require that the SIM card is inserted into a mobile phone, a number dialled and instructions followed. While the SIM is in the mobile phone it would be a good time to disable any PIN codes, call diverts, ring back and disable features such as voicemail and text alerts. Details of how to do this can be found on the SIM card provider’s web site or by calling their customer services. Recommended SIM card providers are: Vodafone, T-Mobile, O2 or Orange/EE. We do not recommend using the 3 network at this present time.
• To be able to receive text messages from the intercom panel, the SIM card will require an SMS service centre number. This is normally preinstalled on new SIM cards but if you are having trouble receiving SMS messages you will need to confirm this by inserting the SIM card into a mobile phone and using the phones menu options to check it. If a number is not programmed then it should be programmed while in the phone (the number can be obtained from the network service provider).
• Voicemail and text alerts must be switched OFF on the SIM card when using the dial in to release the door/gate feature. For Vodafone and O2 this can be done while the SIM card is in the intercom panel. For Orange/EE, T-Mobile and other providers the SIM card must be removed from the intercom panel, inserted into a mobile phone and the mobile phone menu instructions followed.
• When storing the intercom panel’s telephone number in your own mobile phone avoid using an obvious name such as ‘Front Door, or ‘My Gate’ as this would make it easy to decipher if your phone was lost or stolen.
• The PIN request feature must be disabled on the SIM card before using it in the Intercom panel. It is likely on a new SIM card that it will not be enabled but if it is, it will prevent the system from working at all.
• This product may not be suitable for installation in hospitals, health care facilities or in the presence of flammable gases or liquids. Seek advice and authorisation before installing this product in these locations. This product is not designed to be used as an emergency call point.
IMPORTANT NOTE ABOUT THE SIM CARD
When using a pay monthly SIM card you must ask the service provider to put a spend limit (credit limit) on the account (Vodafone call this service ‘spend checker’). This is to safeguard against large bills if the SIM card is stolen or used fraudulently.
SYSTEM COMPONENTS
ART.4810 GSM PRO INTERCOM
The Art.4810 GSM PRO intercom module is the main component of the GSM PRO audio intercom system. It includes a GSM module, a speaker, a microphone, a call button, a status LED, a power LED, a reset button, a micro USB port, two auxiliary inputs, two auxiliary outputs, and a relay output. The GSM PRO module is designed to be used with the Videx 4000 series modular door panels.
ART.4800 - ART.4800M CODELOCK
The Art.4800 - Art.4800M codelock module can be powered from 12-24V AC or DC and includes three dry contact relay outputs and two switched 0V push to exit inputs which can be used to trigger relay 1 & 2. One code per relay can be programmed into the device. Codes can be between 4-8 digits long. The relay time can be 01-99 seconds or set for latching (00). When in latching mode, enter the code followed by ‘ENTER’ to latch the relay and the code followed by ‘CLEAR’ to unlatch the relay.
Built In Relays Back EMF Protection (Art.4800M only)
The Art.4800M includes selectable back EMF protection jumpers on the relays. These jumpers are marked MOV (one jumper for each relay) are used to select the protection type. When using a fail secure lock with connections C & NO the jumper should be in the NO position. When using a fail open lock with connections C & NC the jumper should be in the NC position, as shown in Fig.5. When using the codelock to trigger a gate controller or another third party controller the jumper should be removed completely (this disables the protection on the relay).
Terminal Connections
Connection Description
+ 12-24V AC or DC power input
- 0V power input
C1 Relay 1 common connection
NO1 Relay 1 normally open connection
NC1 Relay 1 normally closed connection
C2 Relay 2 common connection
NO2 Relay 2 normally open connection
NC2 Relay 2 normally closed connection
C3 Relay 3 common connection
NO3 Relay 3 normally open connection
NC3 Relay 3 common connection
SW1 Switched 0V input to trigger relay 1
SW2 Switched 0V input to trigger relay 2
Relay contacts: 3A@24Vac/dc
Technical Specification
Working Voltage : 12V - 24Vac/dc +/- 10%
Current (standby) : 20mA
Current (during operation) : 70mA (max.)
Dry Contact Relay : 3A @ 24Vac/dc (max.)
Working Temp. : -10 +50oC
Connecting the Codelock to the GSM module
Fig.6 below shows the wiring connections between the Art.4800 - Art.4800M codelock and the Art.4810 GSM PRO module.
*1 Remember to set the Art.4800/4800M relay time to a shorter time than that of the Art.4810 GSM PRO relay time.
*2 If connecting the Art.4810 GSM PRO module to a gate controller then please refer to page 19 for correct wiring configuration.
Art.4800 - Art.4800M Programming Guide
Initial Programming
All programming is carried out using the keypad. The programming menu is protected by an engineer’s code. The factory default engineer’s code is ‘111111’ (6x1). This code can be changed to any 4 to 8 digit engineer’s code during the programming, but must be different to the access codes used to gain entry. Follow the flow chart below to setup the access codes:
The red LED will illuminate to acknowledge the Art.4800 - Art.4800M is in programming mode. If the red LED does not illuminate check the engineer’s code is correct. If the engineer’s code has been changed from the factory default and you do not know what it is then follow the factory default procedure on page 14.
Enter the default engineer’s code ‘111111’. Then press ENTER.
Enter a new engineer’s code or enter the same engineer’s code again. Then press ENTER.
This new engineer’s code can be from 4 – 8 digits long and will not activate the relays. It can only be used to enter programming mode. Please note that this new engineer’s code will be needed to re-program the Art.4800 - Art.4800M relay codes in the future.
Enter the access code for relay 1. Then press ENTER.
This access code will be used to open the door/gate for relay 1. The code can be from 4 – 8 digits long and must be different from the engineer’s code and different from the previous access codes.
Enter a two digit relay 1 time from 00 - 99 seconds. Then press ENTER.
This is the time that relay 1 will activate for. It is a two digit number, for example if relay 1 needs to activate for 5 seconds then enter ‘05’ followed by ENTER. ‘00’ will latch the relay when the access code is entered and require the access code followed by CLEAR to unlatch.
More codes?
YES Enter the access code for relay 2 / 3. Then press ENTER.
This access code will be used to open the door/gate for relay 2/relay 3. The code can be from 4 – 8 digits long and must be different from the engineer’s code and different from the previous access codes.
Enter a two digit relay 2 / 3 time from 00 - 99 seconds. Then press ENTER.
This is the time that relay 2/relay 3 will activate for. It is a two digit number, for example if relay 2/relay 3 needs to activate for 5 seconds then enter ‘05’ followed by ENTER. ‘00’ will latch the relay when the access code is entered and require the access code followed by CLEAR to unlatch.
Press ENTER twice to exit programming
The Art.4800 - Art.4800M codelock will play a melody and the red LED will switch OFF to confirm all the settings are saved and exit from programming mode.
Re-programming the Art.4800 - Art.4800M Codelock
If the Art.4800 - Art.4800M codelock has been programmed with an existing access code and it needs to be changed then follow the flow chart below to re-program a new acces code:
Enter the existing engineer’s code. Then press ENTER.
The red LED will illuminate to indicate that the codelock is in programming mode*.
Re-enter the existing engineer’s code again. Then press ENTER.
Alternatively enter a new eningeer’s code (4 - 8 digits).
Enter a new access code for the relay. Then press ENTER.
Relay access code (4 - 8 digits) that operates the door or gate.**
Enter a two digit relay time from 00 - 99 seconds. Then press ENTER.
2 digit relay time (01 - 99 seconds or 00 for latching).
More codes?
NO
YES
Repeat steps for a new access code and time for relay 2 and relay 3
Press ENTER twice to exit programming
The red LED will switch OFF to indicate that the codelock has exited programming mode.
Engineer’s Code
Relay 1 Code
Relay 1 Time
Relay 2 Code
Relay 2 Time
Relay 3 Code
Relay 3 Time
Programming Notes
* If the red LED does not illuminate then the engineer’s code has been previously changed or is incorrect. To reset this code follow the factory reset procedure below.
** On the first loop of the flow chart above the access code is for relay 1 on the second loop the access code is for relay 2 and on the third loop the access code is for relay 3.
Resetting the Engineer’s Code back to Factory Default: ‘111111’ (6x1)
1. Remove/disconnect the power from the Art.4800 - Art.4800M codelock.
2. Press and hold down the ENTER button while the power is switched back onto the codelock.
3. Once power is restored to the codelock release the ENTER button.
4. The engineer’s code has been reset back to the factory default of ‘111111’ (6x1).
4000 SERIES BACK BOXES & MOUNTING FRAMES
Both surface and flush back boxes and mounting frames are available. The size of the frame will depend on the number of modules that make up the door panel. The last digit of the frame code indicates the number of modules it will take. Frames are available in gun metal gray finish, chrome finish (suffix \C to the frame code) or gold finish (suffix \G to the frame code). Fig.7A and Fig.7B below shows the 4000 series mounting frames available.
FLUSH BACK BOXES AND MOUNTING FRAMES
Art.4851
Art.4852
Art.4853
SURFACE BACK BOXES AND MOUNTING FRAMES
Art.4881
Art.4882
Art.4883
Art.4884
Art.4886
Art.4889
Flush Dimensions
Part No. Housed Modules Front Frame (W x H x D) mm Back Box (W x H x D) mm
Art.4851 1 135 x 160 x 15.7 120 x 143 x 46
Art.4852 2 135 x 280.2 x 15.7 120 x 263.2 x 46
Art.4853 3 135 x 400.4 x 15.7 120 x 383.4 x 46
Surface Dimensions
Part No. Housed Modules No. of Columns Back Box (W x H x D) mm
Art.4881 1 1 135 x 160 x 43
Art.4882 2 1 135 x 280.2 x 43
Art.4883 3 1 135 x 400.4 x 43
Art.4884 4 2 270 x 280.2 x 43
Art.4886 6 2 270 x 400.4 x 43
Art.4889 9 3 405 x 400.4 x 43
POWER SUPPLY
The Art.4810 GSM PRO intercom panel is designed to work with power supplies in the range of 12Vdc or 24Vac/dc. The power supply should be capable of supplying a constant current of no less than 2A. The following Videx power supplies can be used:
• AMR2-12 : 12-14Vdc 2A switched mode PSU.
• SP29 : 13.8Vdc 2A boxed PSU with battery backup facility.
• SP28 : 13.8Vdc 3A boxed PSU with battery backup facility.
ART.432 GSM ANTENNA
The Art.432 GSM antenna connects to the SMA female bulkhead connection on the rear of the Art.4810 GSM PRO module. A GSM antenna with an SMA male connector should be used (see Fig.8).
Antenna Parts
1. GSM antenna with magnetic base.
2. Self-threading screw (Ø3.5mm x 9.5mm).
3. Aluminium L bracket for mounting.
4. SMA male connector (cable length 2.5m).
5. Expansion type wall plugs (Ø6mm).
6. Self-threading screw (Ø4mm x 30mm).
IMPORTANT NOTE: An antenna must always be fitted for the GSM module to work. Always route the GSM antenna cable away from the microphone wires and the power supply wires to avoid interference on the speech channels.
WIRING DIAGRAMS
Use either NO or NC depending on the type of lock release
* Remember to set the Art.4800/4800M relay time to a shorter time than that of the Art.4810 GSM PRO relay time.
CONNECTING TO A GATE CONTROLLER (USING THE ART.120 OPTO-ISOLATOR PCB)
If the Art.4810 GSM PRO module is going to be connected to a gate controller then it is recommended that the GSM relay is connected with the Art.120 opto-isolator pcb provided with the GSM kit. The gate controller can be connected into the C and NO terminal connections on the Art.120 pcb as shown in Fig.9.
CONNECTING TO A PUSH TO EXIT BUTTON & THE AUXILIARY INPUTS/OUTPUTS
Push to Exit Button:
The push to exit button must be configured as a push-to-make switch. When connected across terminals g & 6 on the Art.4810 GSM PRO module. When the exit button is pressed the GSM relay will trigger for the programmed time (see Fig.10).
Auxiliary Output A1, Call Activated (00):
The auxiliary output A1 has six modes 00 - 05 and is set using the A1M command (refer to pages 32 - 33 for full list of A1M programming modes). It is an open collector output (switched low). When set to mode 00 auxiliary output A1 will activate when the call begins and deactivate when the call ends, see Fig.11.
Auxiliary Output A1, User Activated (01):
When the A1 output is set to mode 01 auxiliary output A1 will activate when the terminals g & 5 are shorted together on the Art.4810 GSM PRO module or by pressing 6 on the telephone during a call, as shown in Fig.12. Auxiliary output A1 will activate for the programmed time.
Auxiliary Output A1, Status Indication (02):
When the A1 output is set to mode 02 auxiliary output A1 will activate when the GSM PRO module is in call mode, as shown in Fig.13. Auxiliary output A1 will activate for the duration of the call.
Auxiliary Output A1, Gate Status (03):
When the A1 output is set to mode 03 auxiliary output A1 will activate when the gate is open and deactivate when the gate is closed, as shown in Fig.14. Auxiliary output A1 will activate for the duration of the gate being open.
Auxiliary Output A1, Hold Open (04):
When the A1 output is set to mode 04 auxiliary output A1 will activate when the gate is in hold open mode and deactivate when the gate is released, as shown in Fig.15. Auxiliary output A1 will activate for the duration of the gate being in hold open mode.
Auxiliary Output A1, Alarm (05):
When the A1 output is set to mode 05 auxiliary output A1 will activate when the alarm is triggered and deactivate when the alarm is reset, as shown in Fig.16. Auxiliary output A1 will activate for the duration of the alarm.
Auxiliary Input I1, Gate Status (00):
When the I1 input is set to mode 00 auxiliary input I1 will monitor the gate status (open/closed), as shown in Fig.17. The gate status can be checked by sending an SMS command to the GSM PRO module.
Auxiliary Input I1, Hold Open (01):
When the I1 input is set to mode 01 auxiliary input I1 will monitor the gate hold open status (hold open/released), as shown in Fig.18. The gate hold open status can be checked by sending an SMS command to the GSM PRO module.
Auxiliary Input I1, Alarm (02):
When the I1 input is set to mode 02 auxiliary input I1 will monitor the alarm status (triggered/reset), as shown in Fig.19. The alarm status can be checked by sending an SMS command to the GSM PRO module.
Auxiliary Input I1, Call Activated (03):
When the I1 input is set to mode 03 auxiliary input I1 will trigger the GSM PRO module to make a call, as shown in Fig.20. The call will be made to the programmed telephone numbers.
Auxiliary Input I1, User Activated (04):
When the I1 input is set to mode 04 auxiliary input I1 will trigger the GSM PRO module to activate auxiliary output A1, as shown in Fig.21. Auxiliary output A1 will activate for the programmed time.
Auxiliary Input I1, Relay Activated (05):
When the I1 input is set to mode 05 auxiliary input I1 will trigger the GSM PRO module to activate the relay, as shown in Fig.22. The relay will activate for the programmed time.
CABLE SIZE GUIDE
All intercoms wiring must run separately from the mains cable. The cable type should be CW1308 or an equivalent cable. The cable size should comply with the table below.
DISTANCE METERS CABLE SIZE (MM2)
50 0.35
100 0.5
200 0.75
300 1.0
400 1.5
Max resistance of all lines: 8 Ohm
INSTALLATION NOTES
• All multipair cables should be compliant to CW1308 specification (0.5mm twisted pair telephone cable).
• Cables for speech line and service should have a max resistance of 10Ω.
• Lock release wires should be doubled up (Lock release wires and power supply wires should have a max resistance of 3Ω).
• The cables sizes above can be used for distances up to 50m. On distances above 50m the cable sizes should be increased to keep the overall resistance of the cable below the RESISTANCES indicated above.
• Double check the connections before power up.
• Power up the system then check all functions.
LOCK RELEASE WIRING AND BACK EMF PROTECTION
A varistor must be fitted across the terminals on AC lock release (Fig.23A) and a diode must be fitted across the terminals on a DC lock release (Fig.23B) to suppress back EMF voltages. Connect the components to the lock releases as shown in figures.
CONNECTION TO MAINS, SAFETY AND GUIDANCE NOTES
The system must be installed according to national rules in force, in particular we recommend to:
• Connect the system to the mains through an all-pole circuit breaker which shall have contact separation of at least 3mm in each pole and shall disconnect all poles simultaneously;
• The all-pole circuit breaker shall be placed for easy access and the switch shall remain readily operable.
POWER SUPPLY INSTALLATION
• Remove the terminal side covers by unscrewing the retaining screws;
• Fix the power supply to a DIN bar or directly to the wall using two expansion type screws;
• Switch off the mains using the circuit breaker mentioned above and then make the connections as shown on the installation diagrams;
• Check the connections and secure the wires into the terminals;
• Replace the terminal covers and fix them using the relevant screws;
• When all connections are made, restore the mains.
PANEL CARE
• The panel should be cleaned regularly with a soft cloth and a mild detergent. Do not use abrasive cleaners or solvents.
• The panel should be protected from direct sunlight and extreme temperatures.
• The panel should be protected from vandalism.
TESTING, POWER UP AND RESET
• After all connections are made, switch on the power to the GSM PRO module.
• The GSM PRO module will boot up and the status LED will begin flashing. This indicates that the module is searching for a network.
• Once a network is found, the status LED will flash slowly. This indicates that the module is connected to the network.
• To test the system, press the call button on the intercom panel. The GSM PRO module will dial the programmed telephone numbers.
• Answer the call and press * to open the door/gate. The relay will activate for the programmed time.
• To reset the system, press the reset button on the GSM PRO module. The module will restart.
RESET TO FACTORY DEFAULTS
• To reset the GSM PRO module to factory defaults, press and hold the reset button for 10 seconds. The status LED will flash rapidly to indicate that the module is resetting.
• Once the module has reset, the status LED will flash slowly. This indicates that the module is connected to the network.
PROGRAMMING
Programming is carried out via SMS text messages or PC using the GSMSK PC software.
PROGRAMMING BY TEXT MESSAGE
All SMS commands must start with the pass code, default 1234, in the following format *12*1234#, followed immediately by a command. E.g to program the telephone number 0987654321, enter the following SMS..
*12*1234#110987654321#
Pass code Function code Data
Up to 3 numbers can be sent together in a single SMS as follows..
*12*1234#11tel.number1#12tel.number2#13tel.number3#
11 = Telephone number 1
12 = Telephone number 2
13 = Telephone number 3
Additional Programming Parameters
Code Description Default
01????# Change programming password. 1234
02????# Change access control password (allows users not in caller ID list to call intercom and use pass code to activate relay). 5678
03????# Change monitoring mode password (dial to listen in mode) 1212
1n*# Delete a button calling number, where n = number 1,2 or 3. N/A
3?# Speaker volume. Where ? = level 0 - 4 3
4?# Microphone volume. Where ? = level 0 - 4 3
51?# Relay time. Where ? = 1-9999 seconds. 1 sec
53??# Max call time. Where ??? = 005-999 seconds (3 digit code) 60 sec
55??# Max monitoring time (for listen in mode when calling the intercom) 00-60 mins. 00 = no limit. 10 min
57??# Unit can call or SMS service number by set duration to prevent SIM card deactivation if seldom used. 00-60 days. 00 = no inform. 00
58?# Choose between scheduled call to service number or send SMS to service number. ?=1 for SMS, 2 for call. 1
77number# Store service number to receive scheduled SMS or call from intercom. N/A
77*# Delete service number. N/A
65?# Dial in mode for withheld numbers or non stored numbers. 1 = answer the call & wait for pass code. 2 = answer the call & automatically activate 2 way speech. 1
73??# Delete phone number for caller ID access. N/A
73*# Delete all phone numbers for caller ID access. N/A
999# Restore defaults N/A
*21# Check stored numbers. Note: no pass code needed for this command. O = dial out number. I = Dial in number. N/A
Remember to begin each new SMS with pass code *12*1234#
Note: DTMF Programming is done by calling the unit, & entering the pass code first, then after a long single confirm tone, commands can be entered. A fault is indicated by 3 short bleeps.
Fault finding & FAQs
Q. The unit will not power up. No LEDs on.
A. Check power supply voltage is within 11.5V-12.5V DC.
Q. The unit powers up but there is a bleeping from the door station.
A. This means the unit is not able to detect the network for some reason.
-Check the SIM card is activated and has calling credit.
-Power off the unit, remove the SIM and check it in a mobile phone to verify it can make a call.
-Check the SIM does not ask for a PIN code when put in a phone. If it does, then disable the PIN code request.
-Check the SIM is a standard GSM SIM, not 3G or 4G only SIM. If you are unsure, contact your SIM card provider to verify. Frequency of operation should be any one of the international quad band standards, 850 / 900 / 1800 / 1900 MHz.
-Check the reception is good. Poor reception is not sufficient.
-Check the antenna has been mounted as high as possible, not near large metal objects, or wet green shrubs etc.
-Check the antenna connection. Visually inspect that the centre pin inside the antenna is intact, and has not been pushed back inside the fitting.
Q. The unit calls the first number, but there is not enough time to answer before it diverts to the next number.
A. Increase the no answer time as per programming instructions.
Q. The unit calls the first number but voicemail comes on before it can ring the second number.
A. Decrease the no answer time as per programming instructions.
Q. There is no audio from the gate, but the person at the gate can hear ok.
A. This can be due to low reception.
-Check reception level by *20#.
-Change SIM card if necessary to another network which may have better coverage.
-Purchase a high gain antenna.
This may also be caused by either a defective microphone, or incorrect microphone wiring, or a short circuit by whiskers between the centre core and the shielding, or excessive microphone cable length.
Q. The caller ID part does not work.
A. Be sure to program the caller ID part under 72 feature. If your number is a private or number withheld, then it will not work.
Even if you have already programmed a number to receive a call from the intercom, if you also want that number to have caller ID access, it must be programmed under the 72 feature also.
Ensure the number is entered as you would normally dial it from another phone.
Do not put the country code in front of the number.
Enter the country code in which the unit is operating in separate under the 71 feature.
International callers ringing the intercom may not work.
Q. The audio quality that can be heard on the remote telephone is poor or humming (buzzing).
A. A small amount of GSM buzz can be considered normal on GSM intercoms, but not so much that causes inability to hear the person speaking. This can be caused by the GSM antenna being mounted too close to the speech panel or not mounted high enough.
-Try earthling the speech panel chassis to 0V of the power supply.
-This is also a symptom of poor reception. Try above steps on checking and improving reception.
Q. The * or # key does not work when the intercom calls a phone.
A. Check if you can hear the relay clicking at the gate when the * or # key is pressed during a call. If it can be heard, then the system is working, check wiring between the relay and the lock or gate panel. If the relays do not make a clicking sound, then check this feature on a different mobile cell phone or landline. If it works on a different phone, check the settings on the phone in question under DTMF tones.
Failure of DTMF tones to operate correctly is also a symptom of low reception. Check steps above on improving reception. Try pressing the buttons longer when attempting to activate the gates or door.
User Manual
For GSM 800 Videx 4000 series Intercom
This GSM intercom system will call up to 3 telephone numbers in sequence when the call button is pressed.
There are several modes of operation depending on how the unit has been programmed by your installer. The following instructions will assume default programming.
Intercom calling your phone
Press * to open
OR
1 4 7 *
Call button pressed
2 5 8 0 END
Answer call.
Press # to hold open
3 6 9 #
and
Press 1 to release again (Only some gate systems allow hold open control, depending on manufacturer)
Default pass code 5678 is shown in all examples. This may have been changed by your installer.
Trigger Gate / Door
Latch or hold open gate / door
Unlatch gate / door
SEND SMS
SEND SMS
*33*5678#
*34*5678#
If limit switch fitted, check gate status..
Check stored numbers
SEND SMS
SEND SMS
SEND SMS
*35*5678#
*22#
*21#
1 2 3 1 2 3 2 3
5 6 4 5 6 4 5 6
8 9 7 8 9 7 8 9
HOLD OPEN FEATURE, OR “PARTY MODE”
0 systems #
Some allow*hold 0 open #control, depending
* gate
* 0 on #
1 4 7
manufacturer. Send the following SMS commands to control the gates..
1 2 3
4 5 6
Reply will indicate
9
7 8or closed.
opened
* 0 #
1 2 3
4 5 6
O = dial out number
9 for
I =7Dial 8
in number
caller ID0access.
#
*
Calling the intercom options
*33*5678#
Dialling…
MY GATE
1 4 7 *
END
Option 1) If your number is saved inside the intercom memory, just dial it and it will activate the door or gate without answering your call. The intercom will end the call for you.
2 5 8 0
3 6 9 #
END
Option 2) If your number is not saved in the intercom memory, it will answer the call. Enter the code on your telephone keypad to activate the door or gate (default code shown).
Fig.2 wiring diagram
IMPORTANT:
Do NOT drill holes in the top or near the top of the enclosure.
Do NOT use silicone sealants!
Intercom Transmitter
GSM 800
Keep short as possible, 8 meters max
Wiring
Button5
Button4
Button2
Button1
Egress
Mic
Speaker
- +
Button6
12v or 15v d.c. ONLY
WARNING
Do NOT use 24v ac.
2 P3 P4
3 1
C C1 P1 P2 S S1
Solid core of shield connected to 0V on PCB above for better audio quality.
Connect to the buttons module
Button1 Button2 Button3 Button4 Button5 Button6
Relay 1
Relay 2
Relay 3
SW2 SW1 NC3 NO3 C3 NC2 NO2 C2 NC1 NO1 C1 +
Gate Status
Button8
Button7
Button3
Press
Shielded CAT5
*
Reset Button
PWR IN
Speech Panel Connections
12v out +
Relay 1 Momentary
# Latch
1 Unlatch
Relay 2
7 Momentary
8 Latch
9 Unlatch
Press
GSM LED Status LED
Power LED
LOCK
OPEN
Antenna connector. Finger tighten only!
Keypad Connections (VK models only)
Microphone
--- Videx VX2200 DIGITAL SYSTEM Technical Documentation ---
VX2200 TECHNICAL MANUAL
VER1.5
SYSTEM COMPONENTS
800 Series Digital Front Panels (2202M, 2202MR)
These units are built into a double 800 series module (stainless steel/S or aluminium/A) and have a 2 line16
character LCD display, speaker unit and numeric keypad with either 8 alpha buttons [A-H] (VX2202/2202M)
or 3 scroll buttons (VX2202R/2202MR) to navigate the “Repertory Names”. A PC based programming kit is
also available (SP37) which includes software and serial cable to simplify the programming of large
installations.
Vandal resistant Digital Front Panels (SP300, SP301)
These units are based on the 800 series module electronics and have a 2 line 16 character LCD display,
speaker unit and numeric keypad, and 12 gauge stainless steel facia with bezel back box.
4000 Series Digital Front Panels (4202, 4202R, 4202V, 4202RV)
The 4000 Series door panels have the same features as the 800 series version but are based on the 4000
series modular system and can also include mono or colour video within the two module design. Versions
with either alpha buttons [A-F] or scroll buttons are available and include a high contrast blue back lit 2 line
16 character LCD display. The face plate is available in either mirror finish stainless steel (standard version)
or matt finish anodized aluminium).
Digital panels features:
-
Call up to 998 users (Version 5.0 software or later) (only 150 with 900 Series telephone);
Call up to 255 users when using 316x telephones;
Open the door by means of an individual personal access code
Enter the “programming menu” (by using a programmable master code), where it is possible to assign:
a. Trade access code for periodic visitors such as postman etc
b. one or more apartment numbers for each telephone
c. one or more individual access codes (up to 6 digits)
d. User name (Scroll facility door panels only)
e. the device number for each outdoor station
f.
Choose from six languages
g. speech play back system
h. speech time and door opening time (up to 255 seconds);
i.
Automatic test mode
-
Connect up to 10 entrance panels (main or secondary). An installation can consist of main entrances (Which can call all users) and
block entrances (Which can only call users in these blocks). On two level systems of this type a VX2206 bus exchange device is
needed per block.
The LCD display will show all relevant information during the call procedure along with acoustic signals and
voice annunciation.
8000 Series Functional module (8203-0, 8203-1, 8203-2)
Built into a single 8000 series module and includes the speaker unit and interfaces to the digital bus. Up to
64 push buttons can be added to the interface using the 8843, 8844, 845 expansion button modules. (The
8203 is available with either 1 button, 2 buttons or no buttons).
4000 Series Functional Module (4203-0, 4203-1, 4203-2, 4203-1D, 4203-2D)
Built into a single 4000 series module and includes the speaker unit plus 4 LED’s to provide call progress
information. Up to 64 push buttons can be connected (Modules available with button options 0, 1, 2 or 4).
Using the standard 4000 series expansion button modules Art.4842, 4843, 4844, 4845, 4842D, 4843D,
4844D and 4845D. The module is available with front plate in stainless steel mirror finished (standard
version) or in matt finish anodized aluminium.
4000 Series Functional Module with camera (4283-0, 4283-1, 4283-1D)
Built into a single 4000 series module and includes the speaker unit, camera, plus 4 LED’s to provide call
progress information. Up to 32 push buttons can be connected (Modules available with button options 0, 1 or
2). Using the standard 4000 series expansion button modules Art.4842, 4843, 4844, 4845, 4842D, 4843D,
4844D and 4845D. The module is available with front plate in stainless steel mirror finished (standard
version) or in matt finish anodized aluminium and also with mono or colour camera (Suffix \C for colour).
Vandal resistant Functional panels. (Art.138, VR4K2W)
The VR functional panels include the 138 amplifier module. Up to 23 call buttons can be connected and the
unit benefits from all the features of the 4000 series module plus a push to exit button input.
Optional 4 way isolation PCB (2204-1)
This unit isolates the telephones from the main 2 wire bus preventing a single telephone from compromising
the system. One PCB is required for every four handsets. (The L & - terminals are isolated by this PCB).
Optional 4 way isolation PCB with full isolation of all signals and bus connection. (2204N)
This unit isolates the telephones from the main bus preventing a single telephone from compromising the
system. One PCB is required for every four handsets. (The L, -, +12, S1 & D terminals are isolated by this
PCB). A piggy back video isolation PCB is also available for this audio isolation PCB (Available in both coax
and non-coax video versions).
Non-Coax Video Distributor & 20Vdc Video PSU isolation (316I)
Video splitter PCB for no-coax video systems, One required for every four videophones. This PCB can be
used as a piggy back card to the 2204N
Coax Video Distributor & 20Vdc Video PSU isolation (894I)
As above but for coax video systems.
BUS Exchanger (2206A, 2206V)
For use with two level systems with main entrances and block entrances. Enables multiple speech paths
(One per block). Use 2206A for audio systems and 2206V for video systems.
BUS Exchanger (2206N)
For use with two level systems with main entrances and block entrances. Enables multiple speech paths
(One per block). The 2206N allows up to 998 apartments to be called from a main entrance and up to 180
apartments per block. The unit can also be used to extend a single level system up to 998 apartments using
more than one riser bus cable.
Concierge unit (2210A, 2210V)
The 2210 allows an operator to handle and to transfer the calls from and to the users. Depending on the
selected operating mode (day-night-off), it is possible to carry out different functions from the concierge. For
video intercom systems, it is necessary to use 2210V (As 2210A but with additional flat screen monitor).
2 wire bus to 4+1 converter (2280)
The 2280 enables the connection of either the Videx Telephone Interface (380) or the Videx apartment
station (500MM) to the VX2200 system "2 wire" Bus.
Audio telephones (3171, 3172 and 3176)
3000 Series intercoms for the VX2200 Digital System. All 3 intercoms have a door-open/call to concierge
button plus an electronic call tone with a 3 level volume control which can be adjusted by the user. The 3171
and 3172 have a dry contact service push button and the 3172 has a slide privacy switch. The 3176 has a
timed privacy push button with red privacy LED and a green “door open” LED (The door open LED requires
an additional wire).
Audio apartment stations (5178, 5178/CA and 5178/CR, VR5178)
5000 Series surface apartment stations available in white, silver or carbon fibre finishes. Including features
such as half duplex handsfree speech or optional simplex speech mode, timed privacy facility with LED, door
open LED and additional service buttons. Also available in vandal resistant flush.
Basic function audio telephone (3161, 3162)
3000 series low cost telephones with restricted features. The 3161 has a “door open” button and “service”
button. The 3162 also includes a slide mute switch. These telephones can only be used on audio systems
without isolation or a concierge.
Videophones (3371, 3376, 3471, 3476)
3000 Series videophones with coax and non coax video inputs. The 3371 (3471 for colour video) has 5
buttons: “door open”/call to concierge, camera recall/alarm and 3 service push button. The 3376 (3476 for
colour video) is similar to the 3371 but also includes timed privacy with red privacy
(Requires one additional wire) and one less service push button.
Videomonitors (5478, 5478/CA, 5478/CR, VR5478)
5000 Series videomonitors with coax and non coax video inputs. Including colour video, timed privacy
facility, half duplex handsfree speech (Optional handset kit or simplex speech option) and spare service
buttons. A flush mounting kit is also available for these monitors which are also available in white, silver or
carbon fibre affect finishes. Also available in vandal resistant flush.
Videophone (3678)
3600 Series videophones with coax and non coax video inputs. Colour TFT 3.5” monitor with OSD. 3
buttons: “door open”/call to concierge, camera recall/call answer and privacy. Includes both handset and
handsfree speech, timed privacy facility and privacy, door open and answer LED’s
Extension sounder (512D)
Extension Sounder in a white plastic wall mount box. Connects directly to the 2 wire bus.
Extension relay (512DR)
As the 512D but with a dry contact relay (24V 100mA) instead of the sounder.
Non-coax camera module (830/NC, 830C/NC)
800 series camera module with infrared illumination. “No coax” required. (Colour camera 830C/NC has white
LED’s as oppose to IR LED’s)
Coax camera (830, 830C)
As above but for coax video systems. Use 830NC /830NC/C for non-coax camera.
Coax/Non-coax camera (4830, 4830C)
A 4000 series camera with both coax and non-coax connections. Available in mono or colour.
1A DIN Rail Power Supply Unit (521B)
For audio systems with battery back-up facility, 230Vac / 13Vdc/ac – 1 Amp.
Video Power Supply (893N1)
For video systems, 230 Vac / 20Vdc – 1 A peak current (0.8 A continuous current).
Audio control cabinet (SP400, SP405)
Lockable control cabinet for one door (SP400) and up to 4 doors (SP405) audio systems. Includes a
BST/GMT time clock, PSU and facility for a backup battery.
Video control cabinet (SP410, SP415)
Lockable control cabinet for one door (SP410) and up to 4 doors (SP415) video systems. Includes a
BST/GMT time clock, PSU’s for both audio and video, video switching PCB (Multipe door cabinet only) and
facility for a backup battery (Audio backup only).
Non-Coax Video Distributor (316, 316N)
Video splitter for no-coax video systems, One required for every four videophones.
Coax Video Distributor (894, 894N)
As above but for coax video systems.
SEDE LEGALE:
Via G. Ceresani 1 – 60044 Fabriano (AN)
Tel. 0732-626511 / fax 0732-626939
www.eqi.it
SEDE DI JESI:
Via G. Di Vittorio 4 ZIPA 2 – 60035 Jesi (AN)
Tel. 0731-202064 / fax 0731-226376
customer@eqi.it
Sistema qualità conforme
alla norma ISO/IEC 17025
ISO/IEC 17025 compliant
quality system
Rapporto di Prova Compatibilità Elettromagnetica n°: RP LCE031910/01
E.M.C. Test Report n°:
PIANO DELLE PROVE
TESTS PLANNING
TIPO DI PROVA
NORMA DI RIFERIMENTO
TEST
STANDARD REFERENCE
Misura delle emissioni condotte
CEI EN 61000-6-3(07)
Conforme
Pass
CEI EN 61000-6-3(07)
Conforme
Pass
Conducted emissions’ measurement
Misura delle Emissioni Irradiate
Radiated emission’s measurement
Misura delle armoniche
Disturbance in supply system Harmonics’
measurement
Misura delle fluttuazione di tensione
e del Flicker
CEI EN 61000-3-2 (07)
Conforme
Pass
CEI EN 61000-3-3 (97)
+A1 (02)+A2/IS1(06)
Conforme
Pass
CEI EN 61000-4-4 (06) + Ec(08)
CEI EN 61000-6-1(07)
Conforme
Pass
CEI EN 61000-4-2 (96)+
A1 (99)+ A2 (01)
Conforme
Pass
CEI EN 61000-4-11 (06)
CEI EN 61000-6-1(07)
Conforme
Pass
CEI EN 61000-4-3(07)
CEI EN 61000-6-1(07)
Conforme
Pass
CEI EN 61000-4-5 (07)
CEI EN 61000-6-1(07)
Conforme
Pass
CEI EN 61000-4-6 (09)
CEI EN 61000-6-1(07)
Conforme
Pass
Voltage fluctuations’ and flicker’s
measurement
Prova di immunità a transitori/treni
elettrici veloci/Burst.
Electrical fast transient/burst immunity test
Applicazione delle scariche
elettrostatiche
Electrostatic discharge immunity test (ESD)
Applicazione buchi di tensione e
brevi interruzioni
Voltage dips, short interruptions Immunity
test
Immunità sui campi irradiati a
radiofrequenza
Radiated,, radiofrequency, electromagnetic
field immunity test
Applicazione di impulso ad alto
contenuto energetico
Surge immunity test
Applicazione dei disturbi condotti
indotti da campi a radiofrequenza
Conducted disturbances induced by radio
frequency field
Pagina: 2 di 21
SCP: 031910/01
PAGE 66 of 68
VX2200 TECHNICAL MANUAL
VER1.5
PAGE 67 of 68
VX2200 TECHNICAL MANUAL
VER1.5
Northern Office
Videx Security Ltd
Unit 4-7 Chillingham Ind. Est.
Newcastle Upon Tyne
NE6 2XX
TEL 0870 300 1240
FAX 0191 224 5678
Southern Office
1 Osprey
Trinity Park
Trinity Way
London
E4 8TD
FAX 0208 523 5825
TECHNICAL SUPPORT
tech@videx-security.com
TEL 0191 224 3174
FAX 0191 224 4938
http://www.videx-security.com
PAGE 68 of 68
VX2200 TECHNICAL MANUAL
VER1.5
--- Videx 4000 Series IP Video Speaker Unit Module Technical Documentation ---