Skip to content
English
SUBMIT A TICKET HERE
Go to alocity.com
  • There are no suggestions because the search field is empty.

Mercury Intelligent Controller Network Requirements

How to Ensure Your Device is Connected and Operating Efficiently

To ensure that your Mercury Intelligent Controller operates smoothly and delivers reliable Access Control performance, it's important to meet the following network requirements. This guide outlines what you need to prepare for optimal functionality.

1. Ethernet Connection

The Mercury Intelligent Controller must be connected to the Local Area Network (LAN) using a wired Ethernet connection.

  • DHCP is recommended, but static IP configurations are also supported

  • All Panels must be on the same local network

  • Avoid isolated VLANs or guest networks unless properly routed

2. Firewall Settings

Configure your firewall to allow outbound communication on the following ports (Mercury panels utilize outbound polling, so complex inbound port forwarding rules are not required):

  • TCP Port 443 – Secure cloud communication and web services.
  • TCP Port 8883 – Secure, cloud-friendly MQTT broker messaging and live event delivery.
  • UDP Port 123 – NTP network time synchronization to keep the real-time clock array accurate.

Ensure these ports are open for outbound traffic on both local and upstream firewalls.

3. Recommended Internet Speed for Mercury Panels

Mercury panels have a very lightweight bandwidth footprint compared to video systems, but they require a stable, ultra-low-latency connection to process real-time cloud unlocks and instant database synchronization.

  • Minimum Upload Speed: 2 Mbps per intelligent controller.
  • Minimum Download Speed: 2 Mbps per intelligent controller.
  • Recommended Jitter: Less than 30 ms to prevent heartbeat timeout alerts.
  • Recommended Latency: Under 50 ms to ensure instant door release execution when a credential is presented.

4. Downstream Board & Reader Requirements

To ensure compatibility across your access control infrastructure, verify that all downstream components match our supported architectural lineup:

  • Intelligent Controllers (IP Brains): Supported hardware includes both 3rd-Gen (LP1501, LP1502, LP2500, LP4502) and 4th-Gen (MP1501, MP1502, MP2500, MP4502) models running on the Mercury 2.x firmware platform.
  • Downstream Modules (RS-485 Sub-Panels): Supported expanders include the MR50-S3 single-reader interface, MR52-S3B/S4 dual-reader interfaces, and MR16in/MR16out high-density I/O modules. Downstream loops must use 24 AWG, twisted-pair shielded cabling up to 4,000 feet.
  • Network Reader Interfaces: The IP-enabled, PoE+ MR62e dual-reader sub-panel must reside on a local network segment that can be cleanly routed to from the master intelligent controller.
  • Reader Protocols: All connected card readers must support standard Wiegand formats or modern multi-drop OSDP protocols.

5. Network Testing Recommendations

  • Measure Jitter: Ensure jitter remains under 30 ms to avoid heartbeat communication drops or false "offline" alerts.
  • Inspect Wiring: Use high-quality Cat5e or Cat6 cabling, and check for physical damage or weak terminations
  • Direct Connection Testing: During troubleshooting, temporarily connect the Mercury Panel directly to the main router to validate connection quality.

Following these network and controller requirements will help ensure reliable communication, stable downstream connectivity, and consistent cloud performance for your Alocity Mercury Intelligent Controller deployment.