Up to 8 PIM devices can be multi-dropped on the RS-485 communication port of the controller. Since the SCP-M has two ports (labeled 2 and 3), you can attach PIMs to either of the two ports. An individual PIM can have a maximum of 16 Wireless Locks for a maximum of 64 Wireless Locks per SCP-M or EPC-1 controller. For performance reasons, it is strongly recommended that no more than 8 PIMs be connected to a single RS-485 communication port of the SCP-M or EPC-1. PIM communication addresses must be unique within each communication port and the Wireless Lock addresses must be unique within communication port as well. The Wireless Lock address range defined in the PIM is specified as the "low door" and "high door" (valid values are 0 to 127). The Wireless Lock address range for each PIM MUST be defined as a range of 16 Wireless Locks.
UnityIS PIM Integration
- Add either an SCP-M or EPC-1 controller to your Mercury Access Control Driver in Hardware Manager.
- Set the model property to 'SCP-M PIM' or 'EPC-1 PIM' depending on the controller being used.
- From the controller status screen in Hardware Manager, verify that the selected controller has firmware version 1.148 or above.
- Auto Scan or Manually add the PIM sub-controller(s).
- Once you've added all of your sub-controller(s), perform a reset to the controller to make sure that the controller has initialized and downloaded the proper settings.
- Once the PIM sub-controllers are online you should be able to program the device specific properties and the access control functionality of the the system the same way you would for any other Mercury sub-controller.
Wake-up On Radio (WOR)
Wake-up On Radio functionality on the AD-400 locks is available starting in firmware release 1.14.8.
UnityIS AD300 Integration
The AD300 devices are also supported in a similar fashion. The AD-300 is essentially a PIM supporting 1 and only 1 wireless lock. The sub-controller configuration for an AD-300 would have 2 inputs, 1 output, and 1 reader. Please make sure to follow these important notes for the AD300 support:
- RS485 direct connect to the Mercury controller requires a dedicated power supply connected to the 12 VDC input of the AD300 terminal block.
- Addressing on the AD300 can be from "2" to the number of sub-controllers supported by the RS485 Bus. 8 addresses for the EPC-1 and 32 for the SCP-M.
- Jumpers J3 and J4 on the AD300 need to be engage for the two wire configuration.
- AD300 setting needs to be set to Direct connect to the Host and proper RS485 address programmed via the PDA Hand Held Device.
- Wire RS485 from the AD300 TDA- gets wired to the TR+ (Clk) of the Mercury controller and RS485 from the AD300 TDB+ gets wired to the TR- (Data) of the Mercury controller.
- AD300 integration will only work with firmware 1.188 and above. Please upgrade your EPC-1 to this firmware. (EPC-1_1_188.crc). Reset the controller from the UnityIS software once this firmware upgrade is completed.
- Make sure the baud rate for the sub-controllers is set to 9600 in UnityIS.
- Add the EPC-1 to the Hardware tree as usual. Once Online, change the Model Type to "EPC-1 AD3" under Properties of the EPC-1 Controller. Once this is done you can Delete the On-board sub-controller (Address Zero). Add the AD300 lock by doing a Manual add sub-controller and select the device type AD300. Make sure you add this device with the same address that was programmed in the AD300 lock. We suggest adding the lock using address 1.