Skip to main content
BluINFO

Assa Abloy DDE Configuration/Testing Checklist

Server Applications

Server Role
  • Assa Abloy
Installed Applications
  • MS SQL
  • LocalSync
  • ServerManager
  • AssaAbloyInterface
  • DSRInstaller
  • DSR-Demo Application
  • LCT Installer

BluSKY Verification

Server
  • Server is created in BluSky.
  • Server Role of Assa Abloy DSR  is correctly assigned to the server
  • Sync status and Data upload are enabled
  • Data Download Batch size is set to 500
Mercury Controller
  • Create Mercury Controller. This automatically creates a controller SIO Board
MercurySIO Board
  • Create MercurySIO Board of AssaAbloy POE Lock OR AssaABloyWiFiLock for EVERY Assa Abloy Lock that this Server will work with
Reader
  • Create MercuryReaders and attach it to the corresponding SIO Boards previously created. One reader for each Assa Abloy Lock
Portal
  • Create a Portal and select newly created readers for those portals. Also on portal screen select the lock schedule and lock Time out time (normally 5 second)
DSR
  • On a DSR Diagnostics tool select correct remote server in Remote Servers for the selected system window. Type a DSR Name in DSR Name text Box and press Add DSR Button.
  • Refresh DSR Diagnostics tool screen and verify that you can see newly created DSR in Door Service Router (DSRs) window. 
  • Select the DSR in the window above and verify that you can see the newly created Reader in the Readers Window.

Server Verification/Bench Testing

Server
  • Operating system has all the latest updates
  • Windows MSMQ and Telnet features are enabled
SQL Server
  • The latest version of SQL Server (from OPS folder) is installed with dual login mode
LocalSYNC
  • The latest version of Local Sync is installed with the administrator account
  • Correct RemoteServerId is specified in LocalSync.exe.config file
  • Start Local Sync in Console and verify that there are no errors
  • Verify that Local Sync created BluB0X and BluB0XLogs databases in the SQL Server
  • Stop LocalSync in console and start in service mode
ServerManager
  • The latest version of the server manager is installed
  • Correct RemoteServerId is specified in ServerManager.exe.config file
  • Start ServerManager in the console mode and verify there are no errors
  • Stop ServerManager in the console and start in service mode
Assa Abloy Software
  • Latest Version of DSR Installer is Installed (from OPS folder). Communication Security is set to false. All passwords are set to our standard.
  • Latest Version of LCT Installer is installed
  • Latest version of DSR Demo Application is installed
BluBØX Assa Abloyinterface
  • Latest version of AssaAbloyInterface is installed

Building Commissioning

Lock Configuration Tool
  • Using Lock Configuration Tool (LCT) connect to the lock
  • Update the Lock Firmware to the latest version
  • If needed install the patch for the lock to read MIFARE cards
DSR Support Tool
  • Log in into the server and open DSR Support tool.
  • Verify that there are no locks listed in the DSR Support tool
  • Using Lock Configuration Tool configure the lock to point to the server IP address
  • After the lock reboots verify that it shows up in the DSR Support tool
  • Verify that the newly configured lock is NOT online, NOT confirmed
  • Repeat the operations above for every lock connected to this DSR
DSR Diagnostic Tool
  • In DSR Diagnostics Tool select correct ACSystem and DSR
  • Copy the serial number from DSR support tool into Serial Number Text Box in DSR Diagnostics Tool
  • Select correct Portal Type
  • Give this Lock (portal) a name in Portal/Reader Name Text Box.
  • Press Add and Confirm Portal Button to confirm the selected lock. Wait until you see the message that Lock is confirmed
  • Verify in the DSR Support tool on the server that now the selected lock is confirmed and online
  • Update the DSR Diagnostics Tool and verify that you can see the lock in Portals/Readers window
  • Select that newly confirmed portal in Portal Readers window
  • Select the corresponding reader in Readers Window and press Map To Portal button
  • Verify that the lock (portal0 is now mapped to the selected reader
  • Repeat the operations above for every lock connected to this DSR
Users Synchronizations
  • In BluSKY create an access level that would have the newly created portal
  • Create a new user, give her a card and newly created access level
  • Wait a minute and using DSR Support tool verify that user was added to the lock
  • Repeat the operations above for every lock connected to this DSR

DDE Routing

Requires Administrator privileges

  1. Read routing: > Route print
  2. Route add: Route add-p NetwordAddressMask Maskaddress Gatewayaddress
  3. Route delete: Route delete Network Address

 

  • Was this article helpful?