Mercury Security Boards & Panels: Complete Buyer's Guide

March 31, 2026  •  12 min read

Whether you're expanding an existing Mercury system or speccing one from scratch, this guide covers what the hardware actually is, how the boards connect and scale, and — more importantly — the installation and maintenance mistakes that generate most of the service calls we hear about.

We sell Mercury boards direct, without the integrator markup. Browse Mercury hardware

What Mercury Boards Are

Mercury Security makes the intelligent controllers and expansion I/O boards that sit at the core of most enterprise access control systems — hospitals, universities, government buildings, data centers. Genetec Security Center, Lenel OnGuard, Avigilon ACM, ACRE, RS2 Technologies, and most other platforms use Mercury hardware as their physical controller layer.

Mercury boards don't include software. They're the hardware that your access control platform talks to. The platform manages credentials, schedules, and events. The Mercury board makes the access decision at the door, controls the lock relay, and handles the I/O — door contacts, REX devices, alarm points.

The Intelligent Controller: Mercury MP1502

The Mercury MP1502 is the current-generation intelligent controller. It holds the credential database, makes access decisions when the network is down, manages downstream expansion modules over RS-485, and communicates upstream to your ACS over TCP/IP.

The MP1502 supports up to 32 RS-485 expansion modules for a maximum of 64 doors/openings per controller. The same physical board works across Genetec, Lenel, Avigilon, ACRE, RS2, and every other Mercury OEM partner platform.

Cybersecurity: ARM TrustZone, secure boot, TLS 1.3, AES-256/128 host communications, AES-encrypted RS-485 downstream bus, FIPS 140-3 compliant OpenSSL.

Expansion Modules

MR52 — Two-Reader Expansion: The Mercury MR52 is how you add doors beyond the MP1502's native two. Each board adds two more doors on the RS-485 downstream bus. Per MR52: 2 reader ports (Wiegand, F2F, OSDP Secure Channel), 8 programmable inputs, 6 Form C control relays, AES-128/256 encrypted RS-485 communication.

MR16IN — 16-Input Expansion: The Mercury MR16IN-S3 is for monitoring capacity beyond what the MP1502 and MR52 boards provide. 16 fully supervised programmable inputs, 2 relay outputs, AES-128/256 RS-485 communication.

New vs. Refurbished

Mercury boards are built to last. A properly maintained board from ten years ago will run indefinitely if the firmware is current. Every refurbished Mercury board we ship goes through a 47-point inspection and full burn-in test. Both new and refurbished ship with a 1-year guarantee.

Installation Mistakes That Cause Most of the Callbacks

RS-485 Addressing: Duplicate Addresses and Wrong Baud Rate. Every expansion module on the RS-485 bus needs a unique address set via DIP switches. Duplicate addresses cause intermittent or complete loss of communication. Baud rate mismatches between the module and the controller cause communication failures that look like hardware failures.

Undersized Power Supply. Calculate total load across the controller, readers (600mA per reader port maximum), expansion modules, and all lock hardware. Add 20% headroom for inrush current. An undersized supply will brownout under inrush when multiple doors unlock simultaneously.

Missing Tampers. The MP1502 has dedicated unsupervised inputs for cabinet tamper monitoring. If you're using physical tamper switches, wire them. If not, jumper them out. Open tamper inputs generate continuous alarm conditions.

Battery Neglect. The MP1502 has a slot for a CR2032 lithium cell that extends onboard memory backup — add it at installation and replace every two years. Sealed lead-acid backup batteries in power supplies degrade silently; service every two years.

Buy Direct

Related Reading