Migrating from AMAG systems - Best Practices - This guide contains integration best practices and general hardware information on AMAG systems, so that integrators know what to expect when migrating from AMAG to a Security Center access control system. - Security Center 5.8 - 5.12

Product
Security Center
Content type
Best practices
Version
5.12
5.11
5.10
5.9
5.8
Language
English
Last updated
2023-12-20

AMAG system insights

Use the following information to understand the basics of how AMAG systems work, and know what to expect when migrating from AMAG to a Security Center access control system.

NOTE: This information is collected by Genetec™ system integrators and is being updated as required.

AMAG card formats

Before migrating, make sure you understand how AMAG card formats work and how they might differ from card formats in other access control systems.
  • Card formats are stored in the panel, not in SQL.
  • The only data added by users at the cardholder level is the facility code and the cardholder number.
  • On 37-bit formats, the default facility code is 0.
  • The SQL table called badgeformatID is not a card format; it is the template for how a card is printed.
  • Panels are limited to 8 card formats, and a single instance of each bit length.

    For example, if a panel is using H10301 as its 26-bit card format, there cannot be a second 26-bit card format programmed to the panel.

Some systems might have duplicated or redundant credentials, meaning the credentials have the same cardholder number, but different facility codes or card formats. If you do not know which credential is actively being used, you can import the card formats into Security Center as different credentials. You can then import and run the provided macro to remove the duplicate credentials after the active one has triggered an access granted event.

This macro is designed to work with the default Security Center card format, and can be modified to work with custom formats. You can download the macro at the following URL: https://techdocs.genetec.com/viewer/book-attachment/fVrjIPxZgsGR5zQdpcs9fw/7PvhAwecNZDEHU5qKBE06w

AMAG readers and panels

AMAG-specific readers use their own 20 mA protocol and are not reusable. You must replace them with HID readers, or with other Weigand or OSDP readers.

See Migration tips for AMAG devices for more information on replacing AMAG devices.

Circuit monitoring and supervised inputs

The cables for door controllers, card readers, and other monitoring points can use short and open circuits, depending on resistor configuration. Before migrating, you must be aware of how your system uses supervised inputs and resistors.
  • AMAG systems typically use four-state supervision, using two 10K resistors for open circuits, and two 4.7K resistors for closed circuits.
    NOTE: Some AMAG systems might also use three-state supervision using 4.7K resistors, but this is rare.
  • You can either replace the supervisory resistors as needed, or use and define custom resistance values to correspond to the correct resistor types and values.
  • The following diagrams show how AMAG boards use input supervision compared to Mercury boards:

Migration tips for AMAG devices

To help you migrate from AMAG to a Security Center access control system, the following tables provide a brief description of AMAG series platforms and their associated devices. This applies to M4000, M2150, M2000, MultiNode-2, M1000, Edge, and SR.

NOTE: This information is collected when possible by Genetec™ system integrators and is being updated as required.

M4000 platform

Device number Description Migration tips
M4000 PSU Power supply used with the M4000 solution. Not related to Mercury controllers; only used as power supply.
M4000 DBB Door database controller that provides Ethernet and database support.

Turns a 4-door SIO into a 4-door intelligent controller.
  • Replace with any LP intelligent controller and Mercury boards, up to the required number of readers:
    • The LP1501 can support up to 17 readers.
    • Other LP controllers can support up to 64 readers.
  • Supports downstream communication to up to four M4000-DEC4 units for up to 20 card readers.
  • Supports downstream communication to up to four M4000 IOC20/16 controllers for up to 80 inputs and 64 outputs.
M4000 DEC4
  • W: 223 mm (9.2 in)
  • H: 150 mm (5.9 in)
 Entry controller for 4 doors.

Can manage up to 16 doors when paired with DBB.
  • If being used as an intelligent controller, replace with one of the following:
    • One LP1502 and 1 MR52-S3
    • One LP1502 and 1 MR62e
  • If being used as a downstream reader board, replace with one of the following:
    • Two MR52-S3
    • Two MR62e
M4000 IOC20/16 20 input/16 output controller board.
  • Replace with up to two MR16IN-S3 and 1 MR16OUT-S3, depending on used capacity.

M2150 platform

Device number Description Migration tips
M2150 DBU
  • W: 240 mm (9.45 in)
  • H: 160 mm (6.3 in)
 Intelligent controller with database.

Can manage up to 16 doors using more door controllers.
  • Replace with one LP2500.
  • Likely requires new cabinets or updated standoffs in existing cabinets.
  • Might have add-on modules for auxiliary I/O; MR52-S3 accounts for these additions.
  • Supports 20,000 cardholders; add-on memory can be used to support up to 250,000 cardholders.
M2150 8DBC
  • W: 280 mm (11.03 in)
  • H: 260 mm (10.24 in)
 Intelligent controller with database and support for 8 card readers.

Can manage up to 16 doors; 8 onboard and 8 more through 8DC.
  • Replace with one LP1502 and 3 MR52-S3.
  • Likely requires more cabinets because sizes do not match.
  • Might have add-on modules for auxiliary I/O; MR52-S3 accounts for these additions.
  • Supports 20,000 cardholders; add-on memory can be used to support up to 250,000 cardholders.
M2150 8DC
  • W: 280 mm (11.03 in)
  • H: 260 mm (10.24 in)
 Door controller for 8 card readers.

Used to expand the capacity of an intelligent controller up to the maximum 16 readers.
  • Replace with four MR52-S3.
  • Likely requires more cabinets because sizes do not match.
  • Might have add-on modules for auxiliary I/O; MR52-S3 accounts for these additions.
M2150 4DBC
  • W: 280 mm (11.03 in)
  • H: 260mm (10.24 in)
 Intelligent controller with database and support for 4 card readers.

Can manage up to 12 doors; 4 onboard and 8 more through other door controllers.
  • Replace with one LP1502 and 1 MR52-S3.
  • Likely requires more cabinets because sizes do not match.
  • Might have add-on modules for auxiliary I/O; MR52-S3 accounts for these additions.
  • Supports 20,000 cardholders; add-on memory can be used to support up to 250,000 cardholders.
M2150 4DC
  • W: 175 mm (6.89 in)
  • H: 320 mm (12.6 in)
 Door controller for 4 card readers.

Used to expand the capacity of an intelligent controller up to the maximum 16 readers.
  • Replace with two MR52-S3.
  • Likely requires more cabinets because sizes do not match.
  • Might have add-on modules for auxiliary I/O; MR52-S3 accounts for these additions.
M2150 2DBC
  • W: 220 mm (8.67 in)
  • H: 233 mm (9.18 in)
 Intelligent controller with database and support for 2 card readers. Provides distributed intelligence.

Can manage up to 16 doors; 8 onboard and 8 more through 8DC.
  • If using OSDP readers without expansion boards, replace with one LP1501.
  • If using OSDP with expansion boards, replace with one LP1501 and loose the reader port on the LP controller.
  • If using Wiegand, replace with one LP1502.
  • Likely requires more cabinets because sizes do not match.
  • Might have add-on modules for auxiliary I/O; MR52-S3 accounts for these additions.
  • Supports 20,000 cardholders; add-on memory can be used to support up to 250,000 cardholders.
M2150 2DC
  • W: 118 mm (4.65 in)
  • H: 280 mm (11.03 in)
 Door controller for 2 card readers.

Used to expand the capacity of an intelligent controller up to the maximum 16 readers.
  • Replace with one MR52-S3.
  • Likely requires more cabinets because sizes do not match.
  • Might have add-on modules for auxiliary I/O; MR52-S3 accounts for these additions.
M2150 AC24/4 input controller
  • W: 175 mm (6.89 in)
  • H: 320 mm (12.6 in)
 Adds an additional 24 inputs and 3 outputs to either DBC or DBU door controllers where extra I/O is required.
  • Replace with up to two MR16IN-S3, depending on used capacity.
  • Likely requires more cabinets because sizes do not match.
  • Might have add-on modules for auxiliary I/O; MR52-S3 accounts for these additions.
M2150 OC4/24 output controller
  • W: 175 mm (6.89 in)
  • H: 320 mm (12.6 in)
 Adds an additional 24 outputs and 4 inputs to either DBC or DBU door controllers where extra I/O is required.
  • Replace with up to two MR16OUT-S3, depending on used capacity.
  • Likely requires more cabinets because sizes do not match.
  • Might have add-on modules for auxiliary I/O; MR52-S3 accounts for these additions.
M2150 elevator controller Controls entry to 64 floors for up to four elevator cabs.
  • Replacement might require an elevator plugin, depending on elevator feature requirements such as floor tracking.
  • If Mercury can meet integration requirements, replace with one LP1501 (recommended one per elevator) and MR16OUT (depending on the number of floors).
  • Card readers can be sited inside the elevator.

M2100 platform

Device number Description Migration tips
M2100 DBU Database unit that performs all local management functions.

Can control a maximum of 16 readers, 32 auxiliary outputs, and 96 monitor points for alarm monitoring.

  • A node consists of one DBU connected to one or more door or alarm controllers, or to an elevator interface board.
  • Used in an elevator node, a DBU can control up to 64 floors and 4 elevator cabs.
  • Replace with any LP intelligent controller and more Mercury boards, up to the required number of readers.
  • Replacement might require an elevator plugin, depending on elevator feature requirements such as floor tracking.
M2100 4DCU 4-door controller unit that can connect to up to four readers and associated door furniture.1
  • Connects to the DBU using a ribbon cable
  • Replace with two MR52-S3.
M2100 2DCR Remote 2-door controller unit that can connect to 2 readers and associated door furniture.1
  • Can be sited up to 1 km (3000 ft) from the DBU.
  • Replace with either 1 MR52 over RS-485, or 1 LP1502 over Ethernet.
M2100 1DCR-P Remote 1-door controller unit that can connect directly to one reader and associated door furniture,1 along with two monitor points (for alarm monitoring) and one auxiliary output.
  • Can be sited up to 1 km (3000 ft) from the DBU.
  • Replace with either 1 MR50 over RS-485, or 1 LP1501 over Ethernet.
M2100 4DCR-P Remote 4-door controller unit similar to 4DCU or any MR52, but with an integral 18Vac-to-12Vdc power supply.
  • Can convert 24V to 12V onboard for readers and inputs.
  • Can be sited up to 1 km (3000 ft) from the DBU.
  • Replace with any MR52.
  • Does not supply auxiliary power; would require an external power supply.
M2100 ACU Alarms controller unit that can connect directly to up to 24 monitor points (for alarms monitoring) and , replace.
  • Connects to the DBU using a ribbon cable
  • Replace with two MR16in boards (each has 2 outputs) over RS-485.
M2100 ACR Remote alarms controller unit that can connect directly to up to 24 monitor points (for alarms monitoring) and , replace.
  • Can be sited up to 1 km (3000 ft) from the DBU.
  • Replace with two MR16IN boards (each has 2 outputs) over RS-485.
M2100 elevator interface board Board fitted in an M2100 elevator node that provides the interface to the elevator floor buttons, readers (maximum of 4), and floor relays (maximum of 64).
  • Not part of a typical integration.
  • Mercury inputs cannot handle 120VAC without damage.
  • Would require multiple M16IN boards, wired to outputs at the elevator controller, for older elevators that do not support software integrations.

1 Door furniture refers to equipment such as a release device, bypass, door monitor, or exit request button.

MutliNode-2 platform

Device number Description Migration tips
MDU 2 Database unit with on-board ports for direct communication to up to two readers and associated door furniture.1

On-board 3.6V battery maintains the controller configuration in the event of a power failure.
  • Replace with any Mercury LP controller.
MDU 4 Database unit with on-board ports for direct connection to up to four readers and associated door furniture.1

On-board 3.6V battery maintains the controller configuration in the event of a power failure.
  • Replace with any LP controller and more MR52 boards, up to the required number or readers.
2DC Remote 2-door controller unit that can connect to 2 readers and associated door furniture.1
  • Can be sited up to 1 km (3000 ft) from the DBU.
  • Replace with either 1 MR52 over RS-485, or 1 LP1502 over Ethernet with 1 connected MR52.
4DC Remote 4-door controller unit that can connect to 4 readers and associated door furniture1 to be connected.
  • Can be sited up to 1 km (3000 ft) from the DBU.
NOTE: Only available in selected markets that do not require UL compliance.
  • Replace with either 2 MR52 over RS-485 or 1 LP1502 over Ethernet with 1 connected MR52.
Elevator interface module Board fitted in a MultiNode-2 360 elevator node.

Provides the interface to the elevator floor buttons, elevator reader, and floor readers (maximum of 32).
  • Not part of a typical integration.
  • Mercury inputs cannot handle 120VAC without damage.
  • Would require multiple MR16IN boards, wired to outputs at the elevator controller, for older elevators that do not support software integrations.

1 Door furniture refers to equipment such as a release device, bypass, door monitor, or exit request button.

M1000 platform

  • Marketed as Symmetry Business for small systems.
  • 2-reader and 4-reader panels can scale to 16 or 64 readers, depending on the architecture.

Edge platform

Device number Description Migration tips
EN 1DBC+
  • W: 147 mm (5.8 in)
  • H: 185 mm (7.3 in)
  • D: 50 mm (2.0 in)
 Intelligent Edge Network controller with PoE and support for 1 card reader.

Can manage up to 1 door.

Can upgrade to support 2 card readers.
  • Replace with either 1 LP1501 or 1 MR62e. MR62e connection requires an LP controller.
  • Provides 2 general-purpose inputs and 1 general-purpose relay.
  • Might require enclosure to be updated due to Ethernet cable.
EN 2DBC
  • W: 147 mm (5.8 in)
  • H: 185 mm (7.3 in)
  • D: 50 mm (2.0 in)
 Intelligent Edge Network controller with PoE and support for 2 card readers.

Provides distributed intelligence.

Can manage up to two doors.
  • Replace with either 2 LP1501 or 1 MR62e. MR62e connection requires an LP controller.
  • Provides 4 general-purpose inputs and 2 general-purpose relays. If general-purpose inputs are fully used, then an MR62e is required.
  • Might require enclosure to be updated due to Ethernet cable.
EN DBU
  • W: 240 mm (9.45 in)
  • H: 160 mm (6.3 in)
 Intelligent Edge Network controller with database and NIC.

Can manage up to 16 doors using more door controllers.
  • Replace with one LP2500.
  • Seems to be the same as the M2150 DBU board, which is not an end controller.
  • Likely requires new cabinets or updated standoffs in existing cabinet.
  • Might have add-on modules for auxiliary I/O; MR52-S3 accounts for these additions.
  • Supports 20,000 cardholders; add-on memory can be used to support up to 250,000 cardholders.
EN LDBU
  • W: 240 mm (9.45 in)
  • H: 160 mm (6.3 in)
 Controller enabling ASSA ABLOY Aperio wireless locks to be fully integrated into Symmetry Access Control.

Can support up to 16 Aperio locks using the Aperio Hub.
  • Replace with one LP controller, depending on OEM support.
  • Might be able to reuse enclosure depending on how and where LDBU was installed.
  • Supports 20,000 cardholders; add-on memory can be used to support up to 250,000 cardholders.

SR platform

Device number Description Migration tips
SR-DBU database controller Intelligent database controller that provides distributed intelligence and encrypted communication.
  • Replace with any Mercury LP controller.
SR-PCU interface module Interface module that provides power distribution and regulation for an SR controller. Includes communication interfaces.
  • Replace with an external power supply.
SR-DC2 door controller Door controller for 2 card readers.
  • Supports Wiegand and F/2F reader communication
  • Replace with one MR52.
SR-DC8 door controller Door controller for 8 card readers.
  • Supports F/2F reader communication for a range of applications
  • Replace with four MR52.
SR-AC20 input module Auxiliary digital input module with 20 auxiliary inputs.
  • Supports supervised or unsupervised inputs.
  • Replace with two MR16IN boards for a total 20 inputs.
SR-OC16 output module Auxiliary relay output module with 16 auxiliary relay outputs.
  • Replace with one MR16OUT.
SR-OCS16 output module Auxiliary solid-state output module with 16 solid-state outputs.
NOTE: Mercury controllers do not have solid-state outputs.
  • Replace with one MR16OUT and power supply wiring to provide the necessary output voltage.
SR-2000 4 door controller 4-door fixed-configuration access controller with 10 auxiliary inputs and 8 auxiliary relay outputs.
  • Replace with two MR52 boards.