Keri Systems Doors.NET with Multiple Hardware Platforms - Manual (Page 5)

Using Multiple Hardware Platforms in Doors.NET
Application Note
Page 5 of 8 P/N: 01268-001 Rev. B
Table 7: Supported Reader Interfaces
Gateway
Type
PXL NXT
Mercury
Powered
NXT
Standard
Mercury
ASSA
Aperio
ASSA
WiFi/
POE
Ingersoll
Rand
Keri-MS YES YES YES NO NO NO NO
Keri-NXT NO YES YES NO NO NO NO
Wiegand
a
a. The way different controller types handle the Wiegand bit format affects credential compatibility between the
controller types:
- The 26-bit Wiegand format is handled the same between PXL, NXT, and Mercury Powered NXT controllers
(when the NXT and Mercury Powered NXT controllers are using a RIM). It is handled differently by
Standard Mercury controllers, and by ASSA Aperio, ASSA WiFi/POE, and Ingersoll Rand lock sets (which
do not use a RIM). The difference is that the RIM reads the credential, verifies parity, then strips the parity
bits off before sending the credential ID to the controller. The Standard Mercury controllers, and ASSA
Aperio and Ingersoll Rand lock sets simply read the credential and send the entire 26 bits. If a PXL, NXT, or
Mercury Powered NXT gateway is used with a Standard Mercury, ASSA Aperio, ASSA WiFi/POE, or
Ingersoll Rand gateway, you have two options: 1) the 26-bit Wiegand credentials must be enrolled separately
for each controller/lock set type, or 2) use the optional Credential Types menu to create a custom credential
type that accommodates both data types. The Credential Types feature is not a part of the default Doors.NET
license.
- 37-bit HID Wiegand is not compatible across Wiegand reader interfaces as each reader interface
handles the 37-bit value differently resulting in being seen as a different number between interfaces.
This means all 37-bit Wiegand credentials must be enrolled separately for each controller type.
YES YES YES YES YES YES YES
Clock/Data NO NO NO YES NO NO YES