Support Home New Sales Website Old Sales Website Contact Us
RDP Support  


RDPWin KB Booking Engine - IRM.Net RDPWin4 & PCI Compliance Search

Install Kaba Gateway II Key Card Interface

This document outlines the steps to install the Kaba Key Card interface using the Kaba Gateway II network device and the RDPKeyCard application. These instructions do not cover the preferred Kaba Web Service interface. 

Information to collect from the customer:

  1. How many encoders do they have and what are their IDs?  These can be found by pressing the “Home” key on the FDU (Front Desk Unit).
  2. This is a TCP/IP interface between RDP and the Kaba Gateway II device.  The Gateway II box must be assigned a static IP address on the same subnet as the RDP network.  What is the IP address that the customer will use?
  3. Is the Gateway II box currently set up and connected to all FDUs?
  4. What will be the Bridge Computer which will run the RDPKeyCard application? It is best to run this on a computer that is not the RDP data server.

Kaba Gateway II Protocol Configuration

Aside from changing the Kaba Gateway II box to use the TCP/IP LAN interface instead of serial communication, there a few other settings in the Kaba Gateway II device that must be changed under the Kaba Protocol (F2) section of the Configuration area on the Gateway II box.

F1 ADD = 2
F2 SOF = 7F
F3 BID = 1
F4 TIMEOUT = 45

F5 * NEXT PAGE *
F1 LRC = 02

These changes should be made by the customer or by a Kaba representative prior to continuing with the remaining steps. RDP personnel should only make these changes under the direction of a Kaba representative.

Module Installation and Table Configuration

  1. Remotely connect to the bridge computer.
  2. Install the RY (Key Card Interface) module.
  3. Copy Kaba.upd to the RDP root folder and run it using RDP997.
  4. Build the RL table (room to lock system cross-reference)
  5. . For each guest room in RDP a separate sub-record is required. Normally the sub-record is the room number and field #1 is the room number as well. If there are lock-offs, then define additional locks in fields 2, 3 and 4.
  6. Populate the PM table with the encoders (always a two-digit code)
  7. .  Each encoder is entered as a separate sub-record by using a two-digit code starting with 01, 02, etc. The description should indicate to which workstation(s) the given encoder is assigned.  Example, Encoder for Front Desk Stations #1 and #2.
  8. To set the default number of keys to be made, enter RYNUM1 as the sub-record into the C1 Table. This sub-record determines which people classes to sum when setting the default number of keys to be requested at check-in.
  9. If the data portion of the record contains a "1" it will include as the default the value of People-1.
    If the data portion contains "1,2", it will sum the values of People-1 and People-2 fields on the reservation. To include the values of People-3 and People-4 just add 3 or 4 to the list.

RDPKeyCard Installation

  1. Verify the resorts file exists in the RDP root folder, copy resorts.txt to resorts if it does not.
  2. Make a new folder under C:\ProgramFiles\ResortDataProcessing called RDPKeyCard
  3. Unzip the latest RDPKeyCard zip file into this new folder.
  4. Create a Shortcut pointing to RDPKeyCard.exe and place it on the Desktop of the bridge computer.
  5. Run RDPKeyCard.  Note: The RL Table MUST be populated prior to running RDPKeyCard.exe.
  6. Click the Browse button and navigate to the RDP root folder.
  7. Set System Type to Kaba using the drop-down menu.
  8. Save & Close.
  9. Enter IP Address of the Gateway II Box.
  10. Verify and enter the Port number to be used.
  11. Normally the Start Encoder ID will be "1".  In rare circumstances, the customer may run more than one instance of RDPKeyCard and the Start Encoder ID will have a different value.
  12. Add relevant Resort directories as needed.
  13. Add Encoders.  RDP ID can be 01, 02, etc., which coincides with the PM Table. Use a description relevant to where the encoder is located such as "front desk left". The Target ID is the identification used for the encoder in each Kaba FDU unit. The entries in this grid provide a way to translate the encoder number in the RDP system to the encoder number in Kaba. Therefore the RDP ID and Target ID may or may not have the same value.
  14. The Track 2, VIP Flag and VIP User Group fields are optional.
  15. The Save & Close button loads the RDPKeyCard program.  Click the Connect button to establish a TCP/IP connection to the Gateway II device.
  16. Status should read that you have connected.
  17. Define the Encoder for each workstation accessing RDPWin's System - Configuration - System menu and selecting the appropriate encoder (defined in Table PM) from the drop-down.
  18. To test: 
    1. Check-in a test reservation and make a key.
    2. Select Key Card Options.
    3. Select "Make Key".
  19. Once the interface is successfully tested, you may want to select Auto Connect on the Options screen to automatically make the connection to Kaba when the RDPKeyCard application starts so the user doesn’t have to click the Connect button.

Added 05/10/10
Updated 05/12/10

Support Home  RDPWin4 & PCI Compliance Enhancement Requests Open A Web Support Ticket
Training New Sales Website Old Sales Website Contact Us

 Facebook     Twitter      LinkedIn   TODF