SAFLOK System 6000™ PMS Interface Pg.

1 of 73

SAFLOK System 6000™

PMS Interface

Communications and
Message Formats

BASED ON THE
SAFLOK SYSTEM 6000™
INTERFACE PROTOCOL 4 - ASCII

October 29, 2004

All information contained herein, including but not limited to product pricing and other intellectual property, is confidential
and intended for the sole use of the addressee(s) so named. Any misuse of this confidential information contained herein
may result in legal action by Computerized Security Systems dba SAFLOK and its parent company.
© SAFLOK Proprietary and Confidential AS 10/04
SAFLOK System 6000™ PMS Interface Pg. 2 of 73

Table of Contents

1.0 GENERAL COMMUNICATIONS INFORMATION.................................................. 3

1.1 Purpose................................................................................................................... 3
1.2 Hardware Communications and Software Protocol................................................. 3

2.0 GENERAL MESSAGE FIELD AND FORMAT INFORMATION............................. 9

2.1 Field Descriptions for All Messages ........................................................................ 9

3.0 PMS INTERFACE MESSAGE FORMATS (PFC)................................................... 13

3.1 Detailed Format for Null Message (PFC 0) ............................................................. 13
3.2 Detailed Format for Abort Request Message (PFC 7) ............................................ 14
3.3 Detailed Format for Linking Message (PFC 10) ...................................................... 15
3.4 Detailed Format for Unlinking Message (PFC 13)................................................... 16
3.5 Detailed Format for Transaction Message (PFC 20)............................................... 17
3.6 Additional Field Descriptions for PFC 20 ................................................................ 23

4.0 SAFLOK INTERFACE MESSAGE FORMATS (SRC) ........................................... 30

4.1 Detailed Format for Linked Response Message (SRC 55) ..................................... 30
4.2 Field Descriptions for SAFLOK SRC 62 Messages ................................................ 31
4.3 Additional Message Formatting Rules/Future Message Format Compatibility........ 32
4.4 Detailed Format for PFC 20 Response Message (SRC 62).................................... 33

5.0 GENERAL MESSAGE EXCHANGE PROCEDURES

FOR PMS INTERFACE REQUESTS ........................................................................... 39
5.1 Definition of a Transaction Request and Interactive Message Exchanges ............. 39
5.2 PFC 20 Request for a Standard Transaction (TXC 1-127) ..................................... 39
5.3 PFC 7 Request To Abort a Pending PFC 20 Request ............................................ 40
5.4 PFC 13 Request To Unlink From SAFLOK Interface .............................................. 41
5.5 PFC 10 Request To Link to SAFLOK Interface....................................................... 41
5.6 PFC 20, TXC 127 for Standard SAFLOK Information ............................................. 41

6.0 MISCELLANEAOUS .............................................................................................. 43

6.1 Glossary of Terms ................................................................................................... 43
6.2 Example: How To Calculate a Message Checksum and
Add Message Control Codes ............................................................................ 45
6.3 ASCII-to-Hexadecimal Conversion Table ............................................................... 46

7.0 ERROR/MESSAGE CONTROL CODES................................................................ 47

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 3 of 73

1.0 GENERAL COMMUNICATIONS INFORMATION

1.1 Purpose
This document provides the communications details between the SAFLOK Desklinc
interface and your property management system (PMS) interface.

This specification is compatible with the SAFLOK System 5000 interface specifications.
The interface software for the SAFLOK System 6000 was designed to eliminate or
minimize changes that would be required by the PMS companies that have already
developed SAFLOK System 5000 interfaces. However, not all of the SAFLOK System
6000 features will be available to previous System 5000 users.

1.2 Hardware Communications and Software Protocol

This section describes the communications protocol and hardware required. Later
sections provide information on the actual message lines.

Communications between the PMS interface and the SAFLOK interface can be
performed two ways:
• Over an RS232 cable connection between the two computers
• Or over the TCP/IP network using sockets

RS232 Option – Settings and Hardware Requirements

This option uses a RS232 cable connection between the SAFLOK interface and PMS
interface computers. The RS232 link should be:
Full duplex
Asynchronous
4800 or 9600 baud
Even parity
7 data bits
1 stop bit

We recommend using 9600 baud because this baud rate is set in the SAFLOK System
6000’s PMS request server (PRS) program.

The PMS company should include an RS232 cable with a 9-pin male D-connector to
connect to the SAFLOK interface computer. The RS232 cable should not be more than
25-feet long.

The SAFLOK interface uses the pins below. The SAFLOK interface equipment is wired
like a standard PC (DCE). The wiring below is for standard RS232 (pin 2 to 3, pin 3 to 2,
etc.), which assumes the PMS computer is wired as a DCE. If it is wired as a DTE, you
will need to use null modem wiring instead (pin 2 to 2, pin 3 to 3).

SAFLOK 9-Pin D-Connector

Pin 1: DCD (data carrier detect) – input to SAFLOK interface from PMS interface
Pin 2: RXD (receive data) – input to SAFLOK interface from PMS interface
Pin 3: TXD (transmit data) – output from SAFLOK interface to PMS interface
Pin 4: DTR (data terminal ready) – output from SAFLOK interface to PMS interface
Pin 5: Signal ground
Pin 6: DSR (data set ready) – input to SAFLOK interface from PMS interface
© SAFLOK Proprietary and Confidential AS 10/04
SAFLOK System 6000™ PMS Interface Pg. 4 of 73

Pin 7: RTS (request to send) – output from SAFLOK interface to PMS interface
Pin 8: CTS (clear to send) – input to SAFLOK interface from PMS interface
Pin 9: Not used

[ARTIST: INSERT APPROPRIATE ARROWS BELOW, SEE ORIGINAL MANUAL]

SAFLOK 9-Pin D-Connector PMS 9-Pin Connector
Pin 1: DCD ← Pin 1 DCD
Pin 2: RXD → Pin 3 TXD
Pin 3: TXD ← Pin 2 RXD
Pin 4: DTR → Pin 4 DTR
Pin 5: Signal Ground Pin 5 Signal Ground
Pin 6: DSR ← Pin 6 DSR
Pin 7: RTS → Pin 7 RTS
Pin 8: CTS ← Pin 8 CTS
Pin 9: Not used

If you are using three-wire communications and cannot use hardware-level handshaking,
then pins 6, 8, and 20 should be tied together, as well as tying pins 4 and 5 together, in
the RS232 cable.

[ARTIST: INSERT APPROPRIATE ARROWS BELOW, SEE ORIGINAL MANUAL]

SAFLOK 9-Pin Connector PMS 3-Pin Connector
Pin 1: DCD ← Pin 1 DCD
Pin 2: RXD → Pin 3 TXD
Pin 3: TXD ← Pin 2 RXD
Pin 4: DTR →
Pin 5: Signal Ground
Pin 6: DSR ←
Pin 7: RTS →
Pin 8: CTS ←
Pin 9: Not used

TCP/IP Socket Option – Settings and Hardware Requirements

If interfacing through a TCP connection is required, the SAFLOK IRS (interface request
server) application will need to be installed on the SAFLOK System 6000 server. The
IRS is a server application that uses any available logical port native to its operating
system to transmit/receive IP data packets.

Here are additional settings and requirements:

• The SAFLOK System 6000 server should be assigned a static or reserved IP
address
• The message format is exactly the same as in serial communication
• No ACKs or NAKs are used for handshaking
• The IRS listens on two ports for PMS requests
• The port numbers can be changed, but are defaulted to port 8264 and 8274
• A socket connection to the SAFLOK System 6000 server can handle multiple
requests at one time
• Multiple requests can also be made through multiple socket connections by the
PMS

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 5 of 73

TCP/IP Optional Beacon Message

Either the IRS or PMS can use the following message to determine if the socket
connection is still valid:
• The transaction number for the beacon message is 135
• The format of the messages is 200000000135SAFLOK1
• The response to the beacon is 6200000000
• The message and response will be the same, regardless of the originator

Software Protocol (Serial Interfacing Only)

The following protocol control codes are referred to throughout this document.

Line Control Codes

These are for communications line control if needed. The SAFLOK interface will
recognize XON and XOFF if the PMS interface does not use hardware handshaking to
control transmission when receiving a message.

XOFF – Transmitted by the PMS interface to stop the SAFLOK interface from
transmitting to it; this condition can be cleared by the PMS interface by transmitting any
subsequent byte
XON – Transmitted by the PMS interface to explicitly clear the XOFF condition

Message Envelope Control Codes

These codes are used as a message text header and trailer.

STX – Transmitted by the PMS interface and SAFLOK interface as a header of the
incoming message
ETX – Transmitted by the PMS interface and SAFLOK interface as a trailer of the
message to indicate the end of message data

The remaining control codes are used for message handshaking protocol.

Message Handshaking Control Codes Transmitted by the PMS Interface

ACK – Transmitted by the PMS interface to indicate it received a message properly from
the SAFLOK interface
NAK – Transmitted by the PMS interface to indicate it did not receive a message from
the SAFLOK interface
ENQ – Transmitted by the PMS interface to request retransmission of an ACK or NAK

Message Handshaking Control Codes Transmitted by the SAFLOK Interface

ACK – Transmitted by the SAFLOK interface to indicate it received a message properly
from the PMS interface; retransmitted if the PMS interface responds with an ENQ
NAK – Transmitted by the SAFLOK interface to indicate it did not receive a message
properly from the PMS interface; retransmitted if the PMS interface responds with an
ENQ
ENQ – Transmitted by the SAFLOK interface to request retransmission of an ACK or
NAK

Determining If the Communications Link With the SAFLOK Interface Is Online

The SAFLOK System 6000 interface does not require the PMS interface to send it a link
request before it will process key-making requests. However, it is a good idea to test for
the continued connection. If desired, the PMS interface can send a null message at any

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 6 of 73

time – or periodically – to test whether the SAFLOK interface is still there. A null
message is PMS function code (PFC) 0.

When the SAFLOK interface will NOT respond with an ACK or a NAK to a message or
any ENQ sent by the PMS interface, this indicates that the SAFLOK interface is not
running or is not connected.

If the PMS interface receives no ACK or NAK response from the SAFLOK interface after
sending a message and the various ENQs, it should drop the message request from its
memory. It should then send null messages to the SAFLOK interface three times. If the
SAFLOK interface still does not respond, the PMS interface should then terminate all
requests in its memory and then repetitively send a PFC 0 or PFC 10 message to the
SAFLOK interface until it responds with an ACK (and an SRC 55 reply message if a PFC
10 was sent).

If the SAFLOK interface program is running and the connection to the PMS interface is
good, the SAFLOK interface will return an ACK (followed by an SRC 55 if it receives a
PFC 10 request).

If the PMS interface receives a NAK, it should continue to resend the PFC 0 indefinitely.
Normally, this would indicate a cable or port problem in the connecting equipment. If no
response is received, the PMS interface should go through the ENQ process and send
the PFC 10 or PFC 0 message again.

PMS interface: message line (other than PFC 10 link request)

SAFLOK interface: no response within two seconds
PMS interface: ENQ control code – requesting ACK or NAK
SAFLOK interface: no response within two seconds
PMS interface: ENQ control code – requesting ACK or NAK
SAFLOK interface: no response within two seconds
PMS interface: ENQ control code – requesting ACK or NAK
SAFLOK interface: no response within two seconds

Repeat this procedure until the SAFLOK interface responds with ACK:
PMS interface: PFC 0 null message line
SAFLOK interface: no response within two seconds
PMS interface: ENQ control code – requesting ACK or NAK
SAFLOK interface: no response within two seconds
PMS interface: ENQ control code – requesting ACK or NAK
SAFLOK interface: no response within two seconds
PMS interface: ENQ control code – requesting ACK or NAK
SAFLOK interface: no response within two seconds

PMS Interface Transmits Message Line to SAFLOK Interface

After sending a message, the PMS interface must wait for an ACK or NAK from the
SAFLOK interface before it can send another message. It must also wait for a reply
message from the SAFLOK interface before it can send another message for the same
terminal number/request number (destination address).

If a reply message is not received within a predetermined number of seconds, the PMS
interface should send a PFC 7 message to abort the message. The number of seconds
to wait for a reply should equal 45 seconds. If the number of keys in the request is

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 7 of 73

greater than one, an additional 15 seconds – multiplied by the number of keys requested
– should be added to the timeout.

If the SAFLOK interface can’t decipher the message line (complete message envelope
was not received within two seconds or message doesn’t checksum) or was not ready to
handle the message, the SAFLOK interface will return a NAK. Otherwise, it will return an
ACK. If the PMS interface does not receive an ACK or NAK within two seconds, it should
send an ENQ and wait two seconds for an ACK or NAK. This should be repeated three
times. If the SAFLOK interface does not respond after three ENQ tries, the PMS
interface should assume the SAFLOK interface is not online. It should then abort the
message in memory.

If the SAFLOK interface sends a NAK, the PMS interface should resend the message
line again. This procedure should be repeated for a total of three times before the sender
gives up and drops the message.

PMS interface: message line

SAFLOK interface: ACK control code – acknowledge receipt of message

PMS interface: message line

SAFLOK interface: NAK control code – not acknowledging receipt of message
PMS interface: message line
SAFLOK interface: ACK control code

PMS interface: message line

SAFLOK interface: no response within two seconds
PMS interface: ENQ control code – requesting ACK or NAK
SAFLOK interface: no response within two seconds
PMS interface: ENQ control code
SAFLOK interface: no response within two seconds
PMS interface: ENQ control code
SAFLOK interface: no response within two seconds
PMS interface: drop request from memory

PMS interface: message line

SAFLOK interface: NAK control code
PMS interface: message line
SAFLOK interface: NAK control code
PMS interface: message line
SAFLOK interface: NAK control code
PMS interface: drop the request

SAFLOK Interface Transmits Message Line to PMS Interface

Likewise, the SAFLOK interface will wait for an ACK or NAK from the PMS interface
after sending a message before it can send another message.

If the PMS interface can’t decipher the message line or was not ready to handle the
message, the PMS interface should return a NAK. Otherwise, it will return an ACK.

If the SAFLOK interface does not receive an ACK or NAK within two seconds, it will send
an ENQ and wait two seconds for an ACK or NAK. This will be repeated three times. If
the PMS interface does not respond or responds with an NAK after three tries, the
SAFLOK interface will drop the message.
© SAFLOK Proprietary and Confidential AS 10/04
SAFLOK System 6000™ PMS Interface Pg. 8 of 73

2.0 GENERAL MESSAGE FIELD AND FORMAT INFORMATION

This section describes the basic format for all messages. The various information fields
that are common in many of the message formats are also explained in this section.
(Detailed formats for PMS interface and SAFLOK interface messages are provided in
Sections 3 and 4.)

All messages contain an STX (start of text), message text, optional data fields, ETX (end
of text), and an LRC (longitudinal redundancy check) checksum:

<STX> Message Text <ETX> <LRC>

STX Control Character

This is the message header control character that must always be transmitted as the first
character of any message.

Message Text
The message text includes all of the relevant data in a message. Fields for the different
message texts are always fixed in length and position. The SAFLOK interface does,
however, allow all sequentially trailing ASCII 0 (30 hex) and ASCII “space” (20 hex)
characters to be dropped from the message text.

The different message text formats and fields are explained in the rest of this section
and in Sections 3 and 4.

ETX Control Character

This is the “end of text” control character that must always be transmitted after the last
character of the message text data.

LRC Checksum
The LRC checksum is a single byte and must be transmitted as the final character of the
message. An example of how to calculate the LRC checksum for a message is provided
in the example in Section 6.2.

Constructing the Entire Message

Once the message text is constructed, the ETX control character must be added to the
message text and the LRC checksum must be calculated and added after the ETX.
Lastly, the STX control character must be inserted before the message text. (See the
example in Section 6.2.)

2.1 Field Descriptions for All Messages

This is an explanation of each field.

Integer and Logical

Integer fields are expressed as one-, two-, or three-byte ASCII fields. Integer values with
less than the maximum number of digits for the field will be represented with leading
zeroes (e.g., three-byte field with decimal value 1 would be 001 ASCII [30 30 31 hex]).
Logical fields are expressed as one-byte ASCII fields with an ASCII value of 1 or 0 (30 or
31 hex).

Alphanumeric
© SAFLOK Proprietary and Confidential AS 10/04
SAFLOK System 6000™ PMS Interface Pg. 9 of 73

Alphanumeric fields are expressed in ASCII-equivalent characters. Alphanumeric fields

are always specified as a maximum number of uppercase alphanumeric characters.
Each alphanumeric character is expressed as its ASCII equivalent. There is a limited
group of valid ASCII characters for most alphanumeric fields. The characters allowed
include the following and are marked in shaded bars in the ASCII-to-hex conversion
table in Section 6.3.

ASCII: 0 to 9, A to Z, a to z, and SP (space) ! " $ % & ' ( ) + - . : ; < = > ? ` { } |

Hex: 20-22, 24-29, 2B, 2D, 2E, 30-3F, 41-5D, 5F-5D, 5F-7D

Note: Lowercase alpha a to z (61 to 7A hex) will be converted to uppercase A to Z (41 to

5A hex) in the SAFLOK interface. If there is less than the specified number of
alphanumeric characters for the field, left-justify the value in the field and fill the
remaining unused byte positions with ASCII “space” (20 hex).

Dates and Times

There are several fields that call for dates or times. These field values should be
expressed using the format for date (MMDDYY) and military/24-hour time (HHMM). The
date is then expresses by six ASCII-equivalent bytes – the time by four bytes. Each digit
in the format is expressed by its ASCII equivalent. An example is as follows: January 5,
2004, equals 010504 (30 31 30 35 30 34 hex), and 3:34 p.m. equals 1534 (31 35 33 34
hex).

Basic Text Examples:

Example 1: 200000135001………
© SAFLOK Proprietary and Confidential AS 10/04
SAFLOK System 6000™ PMS Interface Pg. 10 of 73

Example 2: 62000010003…………..
Byte Value Possible
Position(s) Type Length Values Description

1-2 Integer Two 00, 07, 10, PMS function code (PFC) or SAFLOK
ASCII 13, 20, 55, response code (SRC)
bytes, 58, 62
fixed

3-4 Integer Two Normally set To interface station number – destination

ASCII to “00” value is ignored by the SAFLOK interface
bytes, (but is required)
fixed

5-6 Integer Two Normally set From interface station number – source
ASCII to “00” value is ignored by the SAFLOK interface
bytes, (but is required)
fixed

7-9 Integer Three 000-254 Unique PMS terminal number or request

ASCII number
bytes,
fixed

10-n* Integer or Two or 00, 03, 04, Value is determined from its respected PFC
alpha- three 05, 08, FE, or SRC; values are explained in Sections 3
numeric ASCII 001, 003, and 4
bytes, 014, 015, 127
fixed

*A predetermined numeric value

PFC and SRC

This field contains a main message code that defines the purpose of the message and
further defines the additional data fields. The code should be expressed as two ASCII
bytes.

There are six main message codes the PMS interface will use for sending messages to
the SAFLOK interface. They are referred to as PFCs (PMS function codes).

There are two message codes the SAFLOK interface will use to send messages to the
PMS interface. They are referred to as SRCs (SAFLOK response codes).

To Interface Station and From Interface Station Number

The values in these two message fields (two ASCII bytes per field) are ignored by the
SAFLOK System 6000 and are normally set to all zeros. The first field refers to the
destination of the message. The second refers to the source of the message. When the
PMS interface is generating the message, the first field will be the station number of the
SAFLOK interface and the second will be the PMS interface.

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 11 of 73

For the PMS interface, the values in these message fields should always be the same.
The SAFLOK interface provides both station numbers to the PMS interface when it
responds to the PMS interface request to link (SRC 55 message). From then on, the
PMS interface should always use those numbers for any further messages. The
SAFLOK System 6000 interface station number values can range from 0 to 99 and are
expressed as two ASCII bytes.

Unique PMS Terminal Numbers or PMS Interface Request Numbers

The value in this field must correspond to a particular PMS terminal or unique PMS
interface request. This field is very important because the SAFLOK interface handles
multiple PFC 20 requests simultaneously and uses the value to cross-reference all
messages to and from the PMS interface and other SAFLOK system equipment to the
proper request in progress.

Each PMS terminal must have a unique number, and the PMS interface must be
assigned unique request numbers that should never be the same as any PMS terminal
numbers. The PMS interface would need to use its request numbers for any PFC 20
messages that are not generated by a PMS terminal. It may also need to use them if any
PFC 20 messages would be generated by a PMS host function (such as a group check-
out). If unique request numbers are not used, there is a high risk of aborting requests of
actual PMS terminals.

If the PMS terminals do not have unique hardware-set station numbers, unique
addresses should be used. Alternatively, if the PMS is designed so that a user can only
be signed onto one terminal at a time, the person’s user number could be used. If the
terminal number values are not within the range required (see below), a cross-reference
table could be created in the PMS interface. The PMS interface request numbers can be
set by software in the PMS interface. You will need at least one number, but should have
two to four.

The terminal or request numbers should range from 000 to 254, expressed as three
ASCII bytes. For PMS interface PFC 20 and SAFLOK interface SRC 62 messages, the
value must be between 001 and 254. The PMS interface and SAFLOK interface will use
value 000 for linking and unlinking and miscellaneous messages (PFC 0, 10, and 13 and
SRC 55).

Additional Fields of Data Information

Additional data fields will be required for certain PFCs and SRCs. These fields are
identified in the detailed message formats for each PFC and SRC in Sections 3.0 to 4.3.

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 12 of 73

3.0 PMS INTERFACE MESSAGE FORMATS (PFC)

This section contains the message formats for all messages sent by the PMS interface
to the SAFLOK interface. All PMS interface messages include a PMS function code
(PFC) identifying the type of message.

PFC Codes
ASCII Hex PFC General Purpose

00 30 30 Null response; used when no response to a PMS message or ENQs

07 30 37 Used to request that the SAFLOK interface abort and terminate a PFC 20
transaction request

10 31 30 Used to test for interface linked SRC message

13 31 33 Used to test for unlinked SRC message

20 32 30 Used to request a SAFLOK System 6000 transaction; this message includes

a TXC field indicating the type of transaction being requested

58 35 38 Used to indicate that the PMS interface received an undefined SAFLOK

interface SRC 62 message with an undefined GRC code or an SRC 62-GRC
0 to 5 message with message text byte #15 (future use) > 0

3.1 Detailed Format for Null Message (PFC 0)

This message can be sent to test for a communications link between the interfaces. If
the SAFLOK interface returns an ACK or NAK, it indicates communications are still up
and the PMS interface can resume normal message communications procedures.

If the SAFLOK interface never responds with an ACK or NAK, the PMS interface should
assume the SAFLOK interface is not online and should terminate all requests in memory
and begin sending a PFC 0 or 10 message to the SAFLOK interface to determine when
communications are again up.

After receiving this message, the SAFLOK interface will not return a corresponding
message.

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 13 of 73

Example:
000000000
Byte Type Value Possible Description
Position(s) Length Value

1-2 Integer Two ASCII 00 PFC 00; null message delimiter

bytes, fixed

3-4 Integer Two ASCII 00 To SAFLOK interface station number

bytes, fixed (normally set to 00)

5-6 Integer Two ASCII 00 From SAFLOK interface station

bytes, fixed number (normally set to 00)

7-9 Integer Three 000 Unique PMS terminal number or

ASCII request number
bytes, fixed

3.2 Detailed Format for Abort Request Message (PFC 7)

This message can be sent when the PMS interface wants to abort a PFC 20 request
while it is currently waiting for a SAFLOK interface response message. It should then
wait for a SAFLOK interface request termination message (SRC 62-GRC 0, 3, 4, 5, or
8).

After receiving a PFC 7 message, the SAFLOK interface will return a termination
message, which will allow the PMS interface to drop the PFC 20 request from memory.

Example:
070000123
Byte Type Value Possible Description
Position(s) Length Value

1-2 Integer Two ASCII 07 PFC 07; abort message delimiter

bytes, fixed

3-4 Integer Two ASCII 00 To SAFLOK interface station number

bytes, fixed (normally set to 00)

5-6 Integer Two ASCII 00 From SAFLOK interface station

bytes, fixed number (normally set to 00)

7-9 Integer Three ASCII 001-254 Existing PMS terminal number or

bytes, fixed request number to be aborted

3.3 Detailed Format for Linking Message (PFC 10)

© SAFLOK Proprietary and Confidential AS 10/04
SAFLOK System 6000™ PMS Interface Pg. 14 of 73

This message can be sent at any time and is primarily used for testing the linked state.
After receiving the PFC 10 message, the SAFLOK interface will return a response
message (SRC 55 link response) if it is connected and the program is running.

Example:
100000000FE
Byte Type Value Possible Description
Position(s) Length Value

1-2 Integer Two ASCII 10 PFC 10; null message delimiter

bytes, fixed

3-4 Integer Two ASCII 00 To SAFLOK interface station number

bytes, fixed (normally set to 00)

5-6 Integer Two ASCII 00 From SAFLOK interface station

bytes, fixed number (normally set to 00)

7-9 Integer Three ASCII 000 or Unique PMS terminal number or

bytes, fixed 001-254 request number 000

10-11 Alpha- Two ASCII FE Value require if PMS wants to receive

numeric bytes, fixed SRC 55 linked response

3.4 Detailed Format for Unlinking Message (PFC 13)

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 15 of 73

This message can be sent any time and is primarily used for testing. After receiving the
PFC 13 message, the SAFLOK interface will not return a corresponding message.

Example:
130000000
Byte Type Value Possible Description
Position(s) Length Value

1-2 Integer Two ASCII 13 PFC 13; unlink message delimiter

bytes, fixed

3-4 Integer Two ASCII 00 To SAFLOK interface station number

bytes, fixed (normally set to 00)

5-6 Integer Two ASCII 00 From SAFLOK interface station

bytes, fixed number (normally set to 00)

7-9 Integer Three ASCII 000 or Unique PMS terminal number or

bytes, fixed 001-254 request number 000

3.5 Detailed Format for Transaction Message (PFC 20)

© SAFLOK Proprietary and Confidential AS 10/04
SAFLOK System 6000™ PMS Interface Pg. 16 of 73

This message can be sent any time, but only one PFC 20 message per unique PMS
terminal number or PMS interface request number should be in progress at any time.

After receiving this message, the SAFLOK interface will return a response message
SRC 62 of some kind.

Make New or Duplicate Keys

Example:
200000123001SAFLOKS250SSSSSSSSSSSS105FF021005041100100504140000000
00000001*20512345
Byte Type Value Possible Description
Position(s) Length Value

1-2 Integer Two ASCII 20 PFC 20; transaction request delimiter

bytes, fixed

3-4 Integer Two ASCII 00 To SAFLOK interface station number

bytes, fixed (normally set to 00)

5-6 Integer Two ASCII 00 From SAFLOK interface station

bytes, fixed number (normally set to 00)

7-9 Integer Three ASCII 001-254 Unique PMS terminal number or PMS
bytes, fixed interface request number

10-12 Integer Three ASCII 001 or 003 Transaction code (TXC) with 001 =
bytes, fixed new key and 003 = duplicate key
(more TXC values will be available in
the future)

13-19 Alpha- Three to 000-9999 SAFLOK password – three to seven

numeric seven ASCII 999, AAA- alphanumeric characters; each
bytes, ZZZZZZZ, character is an ASCII character;
variable S* convert the seven characters to ASCII,
left justify, and fill unused character
positions with ASCII “space” (S) (20h)

20-34 Alpha- One to 15 0-999999 Key number (example: 250)

numeric ASCII bytes, 9999999
variable 99, A-ZZZZ
ZZZZZZZZ
ZZZ, S*

35 Integer One ASCII 1, 2, 3, 4 Key level; 1 = guest level, 2 =

byte, fixed connecter level, 3 = multi-connector
level, 4 = limited-use level

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 17 of 73

36-37 Integer Two ASCII 00-99 Encoder station number to make key(s)
bytes, fixed at (example: 05)

38-39 Alpha- Two ASCII 00-FF Encoder LED control information

numeric bytes, fixed (normally set to FF)

40-41 Integer Two ASCII 00-99 Number of keys to make (example: 02)
bytes, fixed

42-47 Integer Six ASCII MM: 01-12 Projected check-out date;

bytes, fixed DD: 01-31 MM = month, DD = day, YY = year
YY: 00-99 (example: 100504 for 10/5/04)

48-51 Integer Four ASCII HH: 00-24 Projected check-out time; military/24-
bytes, fixed MM: 00-59 hour time; HH = hour, MM = minutes
(example: 1100 for 11 a.m.)

52-57 Integer Six ASCII MM: 01-12 Key expiration date; MM = month, DD
bytes, fixed DD: 01-31 = day, YY = year (example: 100504 for
YY: 00-99 10/5/04)

58-61 Integer Four ASCII HH: 00-24 Key expiration time; military/24-hour
bytes, fixed MM: 00-59 time; HH = hour, MM = minutes
(example: 1400 for 2 p.m.)

62 Logical One ASCII 0 or 1 Pass number option; 0 = add pass

byte, fixed numbers to key’s automatic pass
numbers; 1 = only use pass numbers
provided and ignore automatic pass
numbers

63-74 Logical 12 ASCII 0 or 1 Pass numbers 12 to 1; each byte

bytes, fixed represents a pass number from 12 to 1
(pass number positions are in
descending order); 1 = pass, 0 = no
pass; pass number 12 = 71st byte, 11 =
72nd byte…to 1 = 82nd byte

75-n Option for magnetic track data encoding and/or card printing; see Section 3.6 for
configurations

*Fill position with an ASCII “space” (not the letter “S”)

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 18 of 73

Change Standard Key’s Check-Out Date or Time

Example:
200000123014SAFLOKS250SSSSSSSSSSSS110060411001005041100
Byte Type Value Possible Description
Position(s) Length Value

1-2 Integer Two ASCII 20 PFC 20; transaction request delimiter

bytes, fixed

3-4 Integer Two ASCII 00 To SAFLOK interface station number

bytes, fixed (normally set to 00)

5-6 Integer Two ASCII 00 From SAFLOK interface station

bytes, fixed number (normally set to 00)

7-9 Integer Three ASCII 001-254 Unique PMS terminal number or PMS
bytes, fixed interface request number

10-12 Integer Three ASCII 014 Transaction code (TXC) 014; change
bytes, fixed current standard key’s check-out
date or time

13-19 Alpha- Three to 000-9999 SAFLOK password; three to seven

numeric seven ASCII 999, AAA- alphanumeric characters; each
bytes, ZZZZZZZ, character is an ASCII character;
variable S* convert the seven characters to ASCII,
left justify, and fill unused character
positions with ASCII “space” (S) (20h)

20-34 Alpha- One to 15 0-999999 Key number (example: 250)

numeric ASCII bytes, 9999999
variable 99, A-ZZZZ
ZZZZZZZZ
ZZZ, S*

35 Integer One ASCII 1, 2, 3, 4 Key level; 1 = guest level, 2 =

byte, fixed connecter level, 3 = multi-connector
level, 4 = limited-use level

36-41 Integer Six ASCII MM: 01-12 Projected check-out date; MM =

bytes, fixed DD: 01-31 month, DD = day, YY = year (example:
YY: 00-99 100604 for 10/6/04)

42-45 Integer Four ASCII HH: 00-24 Projected check-out time; military/24-
bytes, fixed MM: 00-59 hour time; HH = hour, MM = minutes
(example 1100 for 11 a.m.)

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 19 of 73

46-51 Integer Six ASCII MM: 01-12 Original check-out date; MM = month,
bytes, fixed DD: 01-31 DD = day, YY = year (example: 100504
YY: 00-99 for 10/5/04); also see note below**

52-55 Integer Four ASCII HH: 00-24 Original check-out time; military/24-
bytes, fixed MM: 00-59 hour time; HH = hour, MM = minutes
(example 1400 for 2 p.m.); this field
value will only be used if the original
check-out date field is >000000

*Fill position with an ASCII “space” (not the letter “S”)

**Note: SAFLOK should always change its longest check-out date and time to the new projected check-out
(which is when the last guest will check out of the room); MMDDYY – SAFLOK should only change its
longest check-out date and time if it is less than the new projected check-out (PMS is providing the new
check-out for one of the guests checking out of the room but not the last guest)

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 20 of 73

Check out a Current Key From the Computer

Example:
200000123015SAFLOKS250SSSSSSSSSSSS1
Byte Type Value Possible Description
Position(s) Length Value

1-2 Integer Two ASCII 20 PFC 20; transaction request delimiter

bytes, fixed

3-4 Integer Two ASCII 00 To SAFLOK interface station number

bytes, fixed (normally set to 00)

5-6 Integer Two ASCII 00 From SAFLOK interface station

bytes, fixed number (normally set to 00)

7-9 Integer Three ASCII 001-254 Unique PMS terminal number or PMS
bytes, fixed interface request number

10-12 Integer Three ASCII 015 Transaction code (TXC) 015; check
bytes, fixed out current standard key

13-19 Alpha- Three to 000-9999 SAFLOK password – three to seven

numeric seven ASCII 999, AAA- alphanumeric characters; each
bytes, ZZZZZZZ, character is an ASCII character;
variable S* convert the seven characters to ASCII,
left justify, and fill unused character
positions with ASCII “space” (S) (20h)

20-34 Alpha- One to 15 0-999999 Key number (example: 250)

numeric ASCII bytes, 9999999
variable 99, A-ZZZZ
ZZZZZZZZ
ZZZ, S*

35 Integer One ASCII 1, 2, 3, 4 Key level; 1 = guest level, 2 =

byte, fixed connecter level, 3 = multi-connector
level, 4 = limited-use level

*Fill position with an ASCII “space” (not the letters “S”)

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 21 of 73

Check in a Pre-Registration Key

Example:
200000123018SAFLOKS250SSSSSSSSSSSS 11006041100
Byte Type Value Possible Description
Position(s) Length Value

1-2 Integer Two ASCII 20 PFC 20; transaction request delimiter

bytes, fixed

3-4 Integer Two ASCII 00 To SAFLOK interface station number

bytes, fixed (normally set to 00)

5-6 Integer Two ASCII 00 From SAFLOK interface station

bytes, fixed number (normally set to 00)

7-9 Integer Three ASCII 001-254 Unique PMS terminal number or PMS
bytes, fixed interface request number

10-12 Integer Three ASCII 018 Transaction code (TXC) 018; check
bytes, fixed in a pre-reg key

13-19 Alpha- Three to 000-9999 SAFLOK password – three to seven

numeric seven ASCII 999, AAA- alphanumeric characters; each
bytes, ZZZZZZZ, character is an ASCII character;
variable S* convert the seven characters to ASCII,
left justify, and fill unused character
positions with ASCII “space” (S) (20h)

20-34 Alpha- One to 15 0-999999 Key number (example: 250)

numeric ASCII bytes, 9999999
variable 99, A-ZZZZ
ZZZZZZZZ
ZZZ, S*

35 Integer One ASCII 1, 2, 3, 4 Key level; 1 = guest level, 2 =

byte, fixed connecter level, 3 = multi-connector
level, 4 = limited-use level

36-41 Integer Six ASCII MM: 01-12 New projected check-out date;
bytes, fixed DD: 01-31 MM = month, DD = day, YY = year
YY: 00-99 (example: 100604 for 10/6/04)

42-45 Integer Four ASCII HH: 00-24 New projected check-out time;
bytes, fixed MM: 00-59 military/24-hour time; HH = hour, MM =
minutes (example: 1100 for 11 a.m.)

*Fill position with an ASCII “space” (not the letters “S”)

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 22 of 73

Request Standard SAFLOK Information

Example:
200000123127SAFLOKS
Byte Type Value Possible Description
Position(s) Length Value

1-2 Integer Two ASCII 20 PFC 20; transaction request delimiter

bytes, fixed

3-4 Integer Two ASCII 00 To SAFLOK interface station number

bytes, fixed (normally set to 00)

5-6 Integer Two ASCII 00 From SAFLOK interface station

bytes, fixed number (normally set to 00)

7-9 Integer Three ASCII 001-254 Unique PMS terminal number or PMS
bytes, fixed interface request number (PMS
terminals don’t usually make this
request)

10-12 Integer Three ASCII 127 Transaction code (TXC) 127;

bytes, fixed request standard SAFLOK
information*

13-19 Alpha- Three to 000-9999 SAFLOK password – three to seven

numeric seven ASCII 999, AAA- alphanumeric characters; each
bytes, ZZZZZZZ, character is an ASCII character;
variable S** convert the seven characters to ASCII,
left justify, and fill unused character
positions with ASCII “space” (S) (20h)

*Note: Byte 7-9 = unique PMS interface request number (PMS terminals don’t usually make this request)
**Fill position with an ASCII “space” (not the letters “S”)

3.6 Additional Detailed Field Descriptions for PFC 20

Descriptions and information on the most common additional data fields for PFC 20
messages are given in this section. Additional clarification of the information to use for
the fields can be found in the detailed formats for each PFC.

Transaction Code (TXC)

This integer field is always required for PFC 20 messages. Transaction codes specify
what SAFLOK System 6000 operation is desired (e.g., 1 = new card, 3 = duplicate card).
The particular TXC will define what additional data fields will be required. This field
consists of three ASCII bytes.

SAFLOK Passwords
This alphanumeric field is always required for PFC 20 messages. SAFLOK passwords
are required for any request that will require data from the SAFLOK System 6000
computer. The password can be from three to seven uppercase alphanumeric
characters. If possible, it is easiest to use the same password that the PMS requires.
© SAFLOK Proprietary and Confidential AS 10/04
SAFLOK System 6000™ PMS Interface Pg. 23 of 73

The PMS interface will also need its own password for requests that it will initiate
directly.

The three- to seven-byte field should be constructed by expressing each character as its
ASCII equivalent. There is a limited group of valid ASCII characters for key number
characters. The characters allowed are marked in shaded bars in the ASCII-to-hex
conversion table in Section 6.3.

If there are less than 15 characters for the field, left-justify the value in the field and fill
the remaining unused byte positions with ASCII “space” (20 hex).

Key Number
This alphanumeric field is used for some PFC 20 messages. The PMS terminal would
always default the key number to equal a room number. However, since it may be
different than the room number, the user should be able to change it.

Key numbers can be up to 15 uppercase alphanumeric characters. The field should be

constructed by expressing each character as its ASCII equivalent. There is a limited
group of valid ASCII characters for key number characters. The characters allowed are
marked in shaded bars in the ASCII-to-hex conversion table in Section 6.3.

If there are less than 15 characters for the field, left-justify the value in the field and fill
the remaining unused byte positions with ASCII “space” (20 hex).

Key Level Code (KLC)

This integer field is required for some PFC 20 messages. This field is one ASCII byte
with values from 0 to 4.

Key levels correspond to the 14 different SAFLOK levels. Levels greater than 0 include:
1 – Room key
2 and 3 – Connector key
4 – Limited-use key

Levels 1 through 3 are guest key levels. Level 1 represents a key that will work in a
single room and is the standard default that should be used for guest keys.

Levels 2 and 3 represent a key that will work in several rooms. If these levels are used,
the PMS interface must be designed to allow a clerk to enter a key name, which may not
be the same as any of the room names. This is necessary because a room may have
several different keys assigned to these levels for each room lock, and the SAFLOK
System 6000 would have no way of knowing which key was desired if it only knew the
room.

Level 4 is a limited-use key. Limited-use keys allow maintenance personnel or

contractors access to only the rooms and areas where work has been authorized. This
type of key provides access to one or several rooms for a specific limited time before it
expires.

Encoder Station Number To Make Key at or Alternate Encoder

This integer field is used in PFC 20 messages. The encoder station number to be used
to make keys should be selected by the PMS terminal clerk when the clerk signs into the
terminal The encoder number should also be included in the “Key Request” screen so
the clerk can change it at any time. All encoders should be labeled their station number.
© SAFLOK Proprietary and Confidential AS 10/04
SAFLOK System 6000™ PMS Interface Pg. 24 of 73

This field is represented by two ASCII bytes (values 00 to 60). The station number
should only be 00 (30 30 hex) if a PFC 22 message is sent to abort the selection of an
alternative encoder.

LED Control Characters

This alphanumeric field is used in PFC 20 messages. It is actually a bit-mapped field
allowing an encoder’s LEDs to provide a visual indication that an encoder is reserved
and ready for a key to be inserted. It is also used to identify whether a PMS terminal or
another device (e.g., SAFLOK terminal) has reserved it. The LED control character
refers to LEDs 3 through 6. The LEDs will stay on for the entire time the encoder is held
reserved for the PMS terminal, indicating to a clerk that an encoder is busy even before
they make a key request.

The field value used in the messages should always be a fixed value, depending on
what type of external system is communicating to the SAFLOK interface. These are the
alphanumeric characters that should be used by different devices:
• FF hex (LEDs 3, 4, 5, 6) – PMS interface
• FE hex (LEDs 3, 4, 5) – Auto check-in station
• F6 hex (LEDs 4, 5) – Remote SAFLOK terminal/computer
• F8 hex (LED 6) – Local SAFLOK terminal/computer

This field is represented by two ASCII bytes (values 00 to FF).

Number of Keys To Make

This integer field is required for some PFC 20 messages. The number of keys to make is
usually “1” or “2” and should be selectable by the user. The PMS interface may provide a
default value that can be changed. The PMS terminal’s “Key Request” screen should
have this field. The “Key Request” screen would also allow a value of “00” to indicate the
clerk wanted to check in existing pre-registration keys. (This lets the PMS terminal know
to request TXC 18 instead of 1. This field is represented by two ASCII bytes (values 00
to 99).

Check-Out and Key Expiration Dates/Times

These date and time fields are required for some PFC 20 messages. There are several
fields that call for dates or times. The date fields are represented by six ASCII characters
in this format: MMDDYY. Each digit of the field is expressed as its ASCII equivalent. For
example, January 5, 2004 = 010504 ASCII (30 31 30 35 30 34 hex). The time fields are
represented by four ASCII characters in military time format (HHMM). For example, 3:34
p.m. = 1534 ASCII (31 35 33 34 hex).

Check-out is used by the SAFLOK System 6000 to provide an error warning if someone
tries to make another new key (for a new guest) before the current guest has checked
out. It is also used to determine the key expiration if the PMS interface does not provide
one. Some users may be allowed to override not-checked-out errors and make the new
key. Check-out is not encoded on the key and does not indicate how long it will work in a
lock.

The key expiration is when the keys will stop working in the locks. The SAFLOK System
6000 uses offsets (days and hours) from the check-out or the time the key is made to
determine the key expiration.

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 25 of 73

When changing the check-out (PFC 20, TXC 14), original and new check-out fields can
be included. The original check-out date and time must be provided if the guest is
checking out early but another guest in the room will still be occupying the room.

If the original check-out cannot be provided, TXC 14 should only be done when the new
check-out date and time will apply to all of the guests in the room. The original check-out
date will allow the SAFLOK interface to determine whether the guest key expiration
exists. If the keys will expire before the new check-out date, it will inform the clerk that
the guest’s key will need replacement.

Check-Out Date
If at all possible, the PMS interface should always provide the check-out date based on
the guest registration data. If the PMS cannot provide the guest check-out date for some
reason, the check-out date field can be sent as all zeroes (000000 ASCII). The SAFLOK
interface will convert the check-out date to equal the average guest stay (from the
SAFLOK System 6000 key files), added to the current date or pre-registration check-in
date.

Check-Out Time
If the PMS does not have a standard check-out time, the PMS interface should use the
ones the SAFLOK interface provides when the PMS interface first links communications
and performs several initialization transactions. The times are provided when the PMS
interface requests PFC 20-TXC 127 and the SAFLOK interface returns an SRC 62-GRC
8 message.

Key Expiration Date and Time

The key expiration date and time identify when a key will stop working in any locks.
Every key made can have a different expiration. There are two ways that a key’s
expiration date and time can be set. You need to identify which option should be used:

1) The key expiration date and time is included in the “Key Request” screen so clerks
can select it. (A default should be provided.) This option:
• Allows nonstandard key expirations to be selected
• Requires the PMS terminal and interface to obtain SAFLOK defaults or set up its
own for providing default values and keeping them updated and valid

2) The key expiration date and time is left at 00/00/00 00:00 in the PMS (and clerks
cannot select it), and the SAFLOK interface automatically sets it up based on the check-
out date and time provided (for guest keys) or based on when the key is made (limited-
use keys). This option:
• Does not allow clerk to select a nonstandard expiration
• Does not require the PMS terminal or interface to obtain SAFLOK defaults or set
up its own for providing values

If the first option is selected, the clerk will be able to change the key expiration.
(However, the SAFLOK interface will impose the same limitations that are in the
SAFLOK terminals.) Clerks can, in particular, select the key expiration they want to use
for limited-use keys.

The PMS terminal will also require some way of knowing the default key expiration it
should use for guest keys and for limited-use keys (the defaults are not handled the
same way). The PMS interface and terminal must come up with a default key expiration
date and time similar to what the SAFLOK interface does in the second option. The
© SAFLOK Proprietary and Confidential AS 10/04
SAFLOK System 6000™ PMS Interface Pg. 26 of 73

offsets that the property chose for guest keys when using the SAFLOK System 6000 are
available to the PMS interface if it requests “Standard SAFLOK Information” (TXC 127)
when it establishes communications. The standard expiration for limited-use keys is not,
however, available. Software would also have to be developed to input the default
offsets that should be used, convert them to dates and times, and ensure the dates and
times have not already passed.

If the second option is selected, the PMS interface and clerk will not need to determine
key expiration date or times because the SAFLOK interface will determine them based
on the defaults the property selected in the SAFLOK System 6000. Guest key expiration
would be an offset (days and hours) from the check-out date and time provided by the
PMS interface. Limited-use-key expiration would use a different offset, based on the time
the key is made.

If the PMS interface will not supply key expiration, it should set the key expiration date
and time fields as: 00/00/00 00:00.

Pass Field Option

This logical field is required for some PFC 20 messages. It indicates whether the PMS
wants the SAFLOK System 6000 to only use the pass number(s) that the PMS indicates
– or whether the SAFLOK System 6000 should add selectable pass number(s) to the
automatic pass numbers that SAFLOK normally includes on the key.

Automatic pass numbers refer to the pass locks a key should always work in, regardless
of the guest. For instance, guests on a regency floor should always be able to have their
keys pass in the elevator.

A selectable pass number represents pass locks that are optional and depend on
whether the particular guest should be given access (such as to a lounge that must be
paid for).

If you want the software designed to display both the automatic and selectable pass
numbers to the clerk, this option would be set to “1.” If only pass numbers that may vary
by particular guest need to be displayed for input, this option should be set to “0.” If you
opt not to handle pass numbers at the PMS terminals, the option should be set to “0.”
This field is one ASCII byte (0 for no, 1 for yes).

Pass Numbers 1-12

These logical fields are required for some PFC 20 messages. They identify the
additional selectable pass numbers or all the pass numbers the key should have
(depending on the pass number option field).

Since the pass numbers used will vary by property, the PMS interface needs some way
of identifying what types of pass locks a pass number activates to associate it with a
registration or “Key Request” screen description. The descriptions of pass numbers are
available from the SAFLOK interface (TXC 131). The descriptions would have to be
collected by the PMS interface after linking communications and passed to the PMS
terminals if this method is used. An alternative would be to set up a special data file for
each property that could be updated at the PMS terminal or interface.

Each of these 12 fields is one ASCII byte (0 for no, 1 for yes). The first field corresponds
to pass number 12 and the last field to pass number 1.

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 27 of 73

Additional Magnetic Track 2 Data for Guest Keys With Format 3 or 4

This field is only used for PFC 20 key-making messages. It is for encoding numeric
information on Track 2 of the magnetic stripe, which is used by a point-of-sale (POS)
system. Up to 35 ASCII bytes can be included. Valid characters are 0 thru 9 for data and
the “=” character for a field delimiter. Data intended to be encoded on Track 2 will be
encoded in the standard ANSI X4.16-1976 numeric only, 40 characters, 5 bit/character,
75 bpi format. Do not include the start sentinel, end sentinel, or LRC checksum
characters.

This data will only be encoded on Track 2 if the SAFLOK System 6000 is configured for
Format 3 or 4 for guest keys and if the encoders in the system are capable of it.
Otherwise, it will be ignored. For Format 3, the SAFLOK System 6000 will add two
characters (3=) to the beginning of the data. For Format 4, the SAFLOK System 6000
will add two characters (=4) at the end of the data (in the last two data character
positions).

Additional Variable Magnetic Track 1, 2, and/or Printable Data

If a variety of data for magnetic stripe tracks and/or printing on the key is desired, a
variety of fields for each track or purpose will be required. If this method is used, the
above-mentioned additional Track 2 field cannot be used. Byte 65 of the PFC 20
message must be an asterisk (*), which will indicate that the remaining data in the
message will follow this format. All additional data tracks must use this format. There is
no specific order that the tracks must be supplied since the track must be identified as
part of the data. Data intended to be encoded on Track 2 will be encoded in the standard
ANSI X4.16-1976 numeric only, 40 character, 5 bit/character, 75 bpi format.

Data intended to be encoded on Track 1 will be encoded in the standard ANSI

alphanumeric, 79 character, 7 bit/character, 210 bpi format. This data will be encoded on
the indicated tracks if the SAFLOK System 6000 is configured for Format 3 (or higher)
for guest keys – but only if the encoders in the system are capable of it. Otherwise, it will
be ignored.

An asterisk character (*) is used in byte 83 to indicate that the remaining PFC 20
message data uses the variable track format (instead of the Track 2 format described
above).

For each track desired, include the following fields in this order:
• Track # – Which track the data is for: magnetic Track 1 or 2 or printing Track 4
• # Data Chars – Two-digit value indicating the number of characters to follow that
should be included in the track data; Track 2’s maximum is 37, Track 1’s
maximum is 76, and the printable maximum is 99; Track 1 and 2 data should not
include the start and end sentinel or LRC checksum characters
• Data Chars – The actual data to be encoded for the track should then follow:
o The number of characters must equal the number indicated in the “# Data
Chars” field
o For Track 2, all characters must be numeric or field separators (0-9, =)
o For Track 1, all characters must be alphanumeric or field separators (A-Z,
0-9, space, $, (,), </, =, [,\,], and ^)
o Track 1 and 2 data should not include start and end sentinel or LRC
checksum characters
o For Track 4, all characters should be standard printer ASCII characters
(with hex values 07 through 0F or 16 through 1F) and should include any
control and delimiter characters needed by the printing device
© SAFLOK Proprietary and Confidential AS 10/04
SAFLOK System 6000™ PMS Interface Pg. 28 of 73

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 29 of 73

4.0 SAFLOK INTERFACE MESSAGE FORMATS (SRC)

This section contains the message formats for all messages sent by the SAFLOK
interface to the PMS interface. All SAFLOK interface messages include a SAFLOK
response code (SRC) identifying the type of message.

SRC Codes
ASCII Hex SRC General Purpose

55 35 35 Used to send a “linked” response back to the PMS interface after receiving a
PFC 10 request

62 36 32 Used to send a response back to the PMS interface after receiving a PFC 20
request; this message includes additional fields that, combined with a GRC
code, indicate the status of the request and what PFC message is next
expected from the PMS interface (if any)

4.1 Detailed Format for Linked Response Message (SRC 55)

This message will only be sent after receiving a PMS interface request message PFC 10
requesting to link. After receiving this message, the PMS interface should not return a
response message.

Example:
550000000FE
Byte Type Value Possible Description
Position(s) Length Value

1-2 Integer Two ASCII 55 SRC 55; link confirmed message

bytes, fixed delimiter

3-4 Integer Two ASCII 00 To SAFLOK interface station number

bytes, fixed (normally set to 00)

5-6 Integer Two ASCII 00 From SAFLOK interface station

bytes, fixed number (normally set to 00)

7-9 Integer Three ASCII 000 or Unique PMS terminal number or

bytes, fixed 001-254 request number 000

10-11 Alpha- Two ASCII FE Fixed value needed to respond

numeric bytes, fixed correctly to PFC 10

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 30 of 73

4.2 Field Descriptions for SAFLOK SRC 62 Messages

Descriptions and information on the additional data fields for an SRC 62 are given in this
section. Additional clarification of the information for the fields can be found in Section 7.

General Response Code (GRC)

A GRC will always be provided with an SRC 62. It identifies whether the request is still
active or terminated and what type of response message it wants back from the PMS
interface. It further identifies the additional data fields that will be in the message.
Section 7 provides explanations of all the GRCs. This field is represented by two ASCII
bytes (values 0 through 99).

Detailed Response Code (DRC)

A DRC will be provided with GRC 3, 4, and 5. It represents a particular error or
message. Section 7 provides explanations of all the DRCs. This field is represented by
three ASCII bytes (values 0 through 255).

Number of Keys Made

The number of keys actually made is provided with a GRC 0.

Default Check-Out Time, Default Check-in Time, and Automatic Pre-Registration

Check-in Time
These date and time fields are provided with a GRC 8. All of these fields call for times
and use a military/24-hour time format (HHMM). The time field is represented by four
ASCII bytes. For example, 3:34 p.m. = 31 35 33 34 hex (1534 ASCII).

The default check-in and check-out times can be used by the PMS interface if this
information is not available in the PMS. The automatic pre-registration check-in time
indicates when the SAFLOK System 6000 will automatically check in all pre-registration
keys due for check-in.

Maximum Days or Hours for Pre-Registration Check-in

These integer fields are also provided with a GRC 8. All of these fields call for numbers
and are represented by three ASCII bytes. The maximum days and hours fields can
range from 1 to 254. These fields indicate how far in the future a pre-registration key’s
check-in date and time can be from the time the key is made. If the check-in will be
further in the future than this, the SAFLOK System 6000 will not allow a key to be made.

Automatic Pre-Registration Check-in Status and Automatic Key Check-Out Status

These logical fields are also provided with a GRC 8. Each is a one-byte ASCII logical
field (0 for no, 1 for yes) that indicates whether the SAFLOK System 6000 will:
• Automatically check-in pre-registration keys at a designated time each day
• Consider a key checked out when its check-out date and time is passed or not

The check-out information is used by the PMS interface routines, which send check-out
requests to the SAFLOK interface. If the SAFLOK System 6000 is automatically
checking out keys, then the PMS interface should only send a check-out request if the
guest is checking out earlier than the original check-out date and time. Otherwise, all
check-outs should be sent to the SAFLOK interface.

Standard Guest Key Expiration Day and Hour Offsets

These integer fields are also provided with a GRC 8. The day fields can range from 0 to
512 (three ASCII bytes). The hours field can range from 0 to 23 (two ASCII bytes).
These fields represent an offset from the check-out date and time. They indicate the
© SAFLOK Proprietary and Confidential AS 10/04
SAFLOK System 6000™ PMS Interface Pg. 31 of 73

additional time the key will continue to work after check-out. This information is provided
in case the PMS interface wants to use the same defaults as the SAFLOK System 6000.
Standard expiration offsets for limited-use keys are not available.

System Date and Time and Daylight-Saving Time (DST) Status

These fields are provided with a GRC 8. The date field is in a month-date-year format
(MMDDYY) with six ASCII bytes. The time field is in a military time format (HHMM) with
four ASCII bytes.

The DST status is represented by one logical ASCII byte and indicates whether DST is
in effect or not (0 for no, 1 for yes). The values of the date and time fields should be
determined by reading each ASCII character as a digit. For example, 4/30/04 = 30 34 33
30 30 34 hex (043004 ASCII) and 3:34 p.m. = 31 35 33 34 hex (1534 ASCII).

Since the SAFLOK System 6000 is designed to automatically adjust its date and time for
leap days and DST, the PMS interface is not allowed to change it. The system date and
time can be used by the PMS interface to notify PMS users that the systems’ times do
not match.

4.3 Additional Message Formatting Rules and Future Message Format

Compatibility
As additional capabilities are added to the SAFLOK System 6000, they may become
available through the SAFLOK interface. The changes will be designed so that the new
SAFLOK interface message formats will be compatible with these original formats. This
is accomplished in the following manner:
• Changes to existing message formats will consist of additional fields added to the
end of the data fields already in existence
• New messages would be formatted using the same general message format

In addition, the SAFLOK interface software is designed with the following message
handling software:
• If the PMS interface sends a message that is shorter than expected (excludes
some of the additional message text bytes expected by the SAFLOK interface),
the SAFLOK interface will assume the missing message text bytes are of null
(space or zero) value and will still process the request (see example in Section
6.2)
• Note: The message text should always be a minimum of nine ASCII bytes
• If the PMS interface sends a message that is longer than expected (includes
some additional message text bytes not recognized by the SAFLOK interface),
the SAFLOK interface will ignore the additional message text bytes and will still
process the request

PMS Message Decoding To Ensure Compatibility

To ensure general compatibility with any future SAFLOK interface software version, the
following procedures should be used in the PMS interface software. Although total
compatibility may not be possible, these procedures would make future changes or
additions to the PMS interface software easier to implement:
• If the SAFLOK interface sends a message that is shorter than expected, the PMS
interface should assume the missing bytes are null values and should still
process the request; THIS IS IMPORTANT because even in these current specs,

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 32 of 73

SRC 62 messages have optional data fields that will not be included in the
message if they are not needed
• If the SAFLOK interface sends a message that is longer than expected, the PMS
interface should ignore the additional message text bytes and still process the
message
• If the SAFLOK interface sends an SRC 62-GRC-DRC message with a DRC code
that the PMS interface does not have a PMS terminal display message assigned,
the PMS interface should send a general error message to the PMS terminal
displaying the GRC and DRC codes (see Section 7)

4.4 Detailed Format for PFC 20 Response Message (SRC 62)

This message will only be sent after receiving a PMS interface message PFC 20
transaction.

Note: For all of the general response code (GRC) messages below, the additional fields
identified under “optional data fields” refer to fields that may not be included in the
message. The SAFLOK interface will truncate the message text after the last field with a
value >30 hex. The PMS interface should then assume that any “missing” field bytes
have a value of 0 (30 hex) or “space” (20 hex).

GRC 00
Example:
620000123000010
Byte Type Value Possible Description
Position(s) Length Value

1-2 Integer Two ASCII 62 SRC 62; transaction status response

bytes, fixed delimiter

3-4 Integer Two ASCII 00 To SAFLOK interface station number

bytes, fixed (normally set to 00)

5-6 Integer Two ASCII 00 From SAFLOK interface station

bytes, fixed number (normally set to 00)

7-9 Integer Three ASCII 001-254 Unique PMS terminal number or

bytes, fixed request number 000

10-11 Integer Two ASCII 00 Transaction completed successfully

bytes, fixed – request terminated

12-14 Integer Three ASCII 001-099 Number of keys made

bytes, fixed

15 - - - Optional data field (future use)

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 33 of 73

GRC 03
Example:
62000012303190
Byte Type Value Possible Description
Position(s) Length Value

1-2 Integer Two ASCII 62 SRC 62; transaction status response

bytes, fixed delimiter

3-4 Integer Two ASCII 00 To SAFLOK interface station number

bytes, fixed (normally set to 00)

5-6 Integer Two ASCII 00 From SAFLOK interface station

bytes, fixed number (normally set to 00)

7-9 Integer Three ASCII 001-254 Unique PMS terminal number or

bytes, fixed request number 000

10-11 Integer Two ASCII 03 Non-recoverable procedural error –

bytes, fixed request terminated

12-14 Integer Three ASCII 000-231 Detailed response code (DRC); see
bytes, fixed Section 7 for error codes

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 34 of 73

GRC 04
Example:
620000123041750
Byte Type Value Possible Description
Position(s) Length Value

1-2 Integer Two ASCII 62 SRC 62; transaction status response

bytes, fixed delimiter

3-4 Integer Two ASCII 00 To SAFLOK interface station number

bytes, fixed (normally set to 00)

5-6 Integer Two ASCII 00 From SAFLOK interface station

bytes, fixed number (normally set to 00)

7-9 Integer Three ASCII 001-254 Unique PMS terminal number or

bytes, fixed request number 000

10-11 Integer Two ASCII 04 Non-recoverable system

bytes, fixed error – request terminated

12-14 Integer Three ASCII 000-188 Detailed response code (DRC); see
bytes, fixed Section 7 for error codes

15 - - - Optional data field (future use)

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 35 of 73

GRC 05
Example:
620000123052540
Byte Type Value Possible Description
Position(s) Length Value

1-2 Integer Two ASCII 62 SRC 62; transaction status response

bytes, fixed delimiter

3-4 Integer Two ASCII 00 To SAFLOK interface station number

bytes, fixed (normally set to 00)

5-6 Integer Two ASCII 00 From SAFLOK interface station

bytes, fixed number (normally set to 00)

7-9 Integer Three ASCII 001-254 Unique PMS terminal number or

bytes, fixed request number 000

10-11 Integer Two ASCII 05 Non-recoverable system

bytes, fixed error – request terminated

12-14 Integer Three ASCII 000-255 Detailed response code (DRC); see
bytes, fixed Section 7 for error codes

15 - - - Optional data field (future use)

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 36 of 73

GRC 08
Example:
62000010008120006001300100200111005042044100012
Byte Type Value Possible Description
Position(s) Length Value

1-2 Integer Two ASCII 62 SRC 62; transaction status response

bytes, fixed delimiter

3-4 Integer Two ASCII 00 To SAFLOK interface station number

bytes, fixed (normally set to 00)

5-6 Integer Two ASCII 00 From SAFLOK interface station

bytes, fixed number (normally set to 00)

7-9 Integer Three ASCII 001-254 Unique PMS terminal number or

bytes, fixed request number 000

10-11 Integer Two ASCII 08 Standard SAFLOK information

bytes, fixed returned after a PFC 20, TXC 127

12-15 Integer Four ASCII HH: 00-24 Standard default check-in time;
bytes, fixed MM: 00-59 military/24-hour time, HH = hour, MM =
minutes (example: 1200 for 12 p.m.)

16-19 Integer Four ASCII HH: 00-24 Standard default check-out time;
bytes, fixed MM: 00-59 military/24-hour time, HH = hour, MM =
minutes (example: 0600 for 6 a.m.)

20-23 Integer Four ASCII HH: 00-24 Automatic pre-reg check-in time;
bytes, fixed MM: 00-59 military/24-hour time, HH = hour, MM =
minutes (example: 1300 for 1 p.m.)

24 Logical One ASCII 0 or 1 Automatic pre-reg check-in status; 0 =

byte, fixed not activated and 1 = activated

25-27 Integer Three ASCII 001-254 Maximum days away pre-reg check-in
bytes, fixed can be (example: 002 = 2 days)

28-30 Integer Three ASCII 001-254 Maximum hours early a pre-reg can be
bytes, fixed checked in (example: 001 = 1 hour)

31 Logical One ASCII 0 or 1 Automatic key check-out status; 0 =

byte, fixed not activated and 1 = activated

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 37 of 73

32-37 Integer Six ASCII MM: 01-12 System date; MM = month, DD = day,
bytes, fixed DD: 01-31 YY = year (example: 100504 for
YY: 00-99 10/5/04)

38-41 Integer Four ASCII HH: 00-24 System time; military/24-hour time, HH
bytes, fixed MM: 00-59 = hour, MM = minutes (example: 1100
for 11 a.m.)

42 Logical One ASCII 0 or 1 System daylight-saving time (DST)

byte, fixed status; 0 = standard time and 1 = DST

43-45 Integer Three ASCII 000-512 Standard key expiration days after
bytes, fixed check-out date

46-47 Integer Three ASCII 00-23 Standard key expiration hours after
bytes, fixed check-out time

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 38 of 73

5.0 GENERAL MESSAGE EXCHANGE PROCEDURES FOR PMS INTERFACE

REQUESTS

5.1 Definition of a Transaction Request and Interactive Message Exchanges

Transaction requests are always initiated by a PFC 20 message from the PMS interface.
These requests are assigned a SAFLOK interface task slot in memory, and information
must be obtained from the SAFLOK System 6000 computer to complete them. All other
PMS interface PFC messages (PFC 0, 10, and 13) either are SAFLOK interface function
requests, which don’t require task slots, or provide more information for a PFC 20
transaction request. Each SAFLOK interface can handle simultaneous requests.

Some important rules for the PMS interface’s handling of requests include:
• All transaction requests are terminated only by the SAFLOK interface. The PMS
interface should always maintain a record of the request until the SAFLOK
interface sends a termination message for it (SRC 62, GRC 0, 3, 4, 5, or 8).
• The PMS interface should never allow another PFC 20 request using the same
PMS terminal/request number in the byte 7-9 request number position until the
previous PFC 20 request has been terminated by the SAFLOK interface. This
does not apply to PFC 7 requests, which always reference an existing PFC 20
request number.

Only one transaction request (PFC 20) can be in process for a particular PMS terminal
or PMS interface request number. If there is a request currently in progress for a PMS
terminal or PMS interface request number and a second transaction request (PFC 20) is
received with the same request number (same PMS terminal), the SAFLOK interface will
immediately terminate both the original and second PFC 20 requests, and one SRC 62-
GRC 3 message will be sent to the PMS interface for both requests. The new PFC 20
request will not be accepted.

It is the responsibility of the PMS interface to ensure that it does not use an existing
request number in a PFC 20 transaction until the SAFLOK interface indicates the first
one is terminated. Explanations of SAFLOK GRC-DRC error and information codes are
provided in Section 7.

Sample Message Exchanges Between the PMS and SAFLOK Interfaces for PFC 20
Requests
The SAFLOK interface software is designed to require the PMS interface to generate all
requests and to require only a single terminating SAFLOK interface reply message in
response to any PFC 20 request.

PMS Interface SAFLOK Interface

PFC 20 message SRC 62, GRC 0, 3, 4, or 5 message (request terminated)

5.2 PFC 20 Request for a Standard Transaction (TXC 1-127)

When a PMS terminal wants to start a SAFLOK System 6000 transaction, the PMS
interface would send a PFC 20 message with a specified TXC to the SAFLOK interface.

PMS interface: transaction request message – PFC 20/TXC xx

SAFLOK interface: ACK control code – acknowledge receipt of message

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 39 of 73

If the transaction request cannot complete due to an unrecoverable procedure error,

then the SAFLOK interface will respond with an SRC 62, a GRC 3, and a DRC xx to the
PMS interface (where xx equals the detailed error code). The SAFLOK interface aborts
and terminates the request. The PMS interface can be designed to change some data in
the original transaction request (PFC 20) to keep the error from occurring again and then
to send a new revised PFC 20 request.

SAFLOK interface: unrecoverable error response message – SRC 62/GRC 3/

DRC xx
PMS interface: ACK control code – acknowledge receipt of message

If the transaction request cannot complete due to an unrecoverable SAFLOK system

error, then the SAFLOK interface will respond with an SRC 62, a GRC 4, and a DRC xx
to the PMS interface. The SAFLOK interface aborts and terminates the request. The
PMS interface cannot keep these errors from occurring again by changing data and
sending a revised PFC 20 request.

SAFLOK interface: unrecoverable error response message – SRC 62/GRC 4/

DRC xx
PMS interface: ACK control code – acknowledge receipt of message

If the transaction was successfully completed or any keys requested were successfully
made, then the SAFLOK interface will transmit an SRC 62, a GRC 0 or 5, and a DRC xx
to the PMS interface (where xx equals the number of keys made for a GRC 0 or a
detailed message code for a GRC 5). The SAFLOK interface terminates the transaction
request.

SAFLOK interface: completed response message – SRC 62/GRC 0 or 5/DRC xx

PMS interface: ACK control code – acknowledge receipt of message

5.3 PFC 7 Request To Abort a Pending PFC 20 Request

If the PMS interface wants to abort a request still pending in its memory that the
SAFLOK interface is still working on, it would send a PFC 7 message with the original
request number to the SAFLOK interface. The PMS terminal field would contain the
original request number instead of a new PMS interface request number. This message
could also be sent for each request in the PMS interface’s memory after communications
are linked and all other initialization messages have been completed. These requests do
not use a separate transaction task slot in the SAFLOK interface. The PMS interface
must continue to wait for the SAFLOK interface to send a message that will terminate
the original request before it can drop it from memory.

PMS interface: abort request message – PFC 7

SAFLOK interface: ACK control code – acknowledge receipt of message

The original request will still be active and the SAFLOK interface will terminate it and
send an SRC 62 and a GRC 0, 3, 4, 5, or 8 (depending on the original PFC request type
and the stage the request was at when the PFC 7 abort request was received) to the
PMS interface.

SAFLOK interface: terminated request message – SRC 62/GRC 0, 3, 4, 5, or 8

PMS interface: ACK control code – acknowledge receipt of message

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 40 of 73

5.4 PFC 13 Request To Unlink From SAFLOK Interface

When the when the PMS interface program is being stopped, the PMS interface should
send a PFC 13 request message to the interface to unlink communications. After
receiving the request, the SAFLOK interface will unlink. It will not return a message to
the PMS interface, since communications will already have ended.

PMS interface: unlink request message – PFC 13

SAFLOK interface: ACK control code – acknowledge receipt of message

5.5 PFC 10 Request To Link to SAFLOK Interface

When the SAFLOK interface does not send or respond (ACK or NAK) to a null (PFC 0)
message from the PMS interface after 10 tries, it’s indicating that communications are
unlinked. The PMS interface should terminate any requests it has in memory and send a
PFC 10 request message to the SAFLOK interface until it responds.

In addition, any time the PMS interface is first booted up, it should always send this
message until the SAFLOK interface responds with an ACK and an SRC 55 reply
message.

Upon successful linking, the SAFLOK interface will return an SRC 55 to the PMS
interface to indicate it is linked. The PMS interface should then use the PMS
interface/SAFLOK interface station number provided in all its future messages to the
SAFLOK interface.

SAFLOK interface: no response (ACK or NAK) after 10 attempts of a PFC 0

message and ENQs
PMS interface: link message request – PFC 10
(repeated until SAFLOK interface responds with an ACK)
SAFLOK interface: ACK control code – acknowledge receipt of message
SAFLOK interface: link response message – SRC 55
PMS interface: ACK control code – acknowledge receipt of message.

After the communications link is established, the PMS interface should request the
standard SAFLOK information to compare the PMS and SAFLOK System 6000 dates
and times – and to obtain any SAFLOK System 6000 default information it will use. The
PMS interface would send a PFC 20 message with a TXC 127 to the SAFLOK interface
(see Section 5.6).

5.6 PFC 20, TXC 127 for Standard SAFLOK Information

After the communications link is established, the PMS interface should request the
standard SAFLOK information. The PMS interface would send a PFC 20 message with a
TXC 127 to the SAFLOK interface. The PMS terminal field would contain a unique
request number instead of a PMS terminal number.

PMS interface: transaction request message – PFC 20, TXC 127

SAFLOK interface: ACK control code – acknowledge receipt of message

When the transaction request successfully completes, the SAFLOK interface will
respond with an SRC 62, a GRC 8, and various data fields, which terminates the
transaction request. The PMS interface would write these to a file or hold them in
memory.
© SAFLOK Proprietary and Confidential AS 10/04
SAFLOK System 6000™ PMS Interface Pg. 41 of 73

SAFLOK interface: completed response message – SRC 62/GRC 8

PMS interface: ACK control code – acknowledge receipt of message

Once the information is received, the PMS interface should compare the SAFLOK
System 6000 date and time to its own to determine whether they are acceptably close. If
they are not, the PMS interface should unlink and display a message on its screen
indicating the date and time and information that one of the two systems needs to be
adjusted.

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 42 of 73

6.0 MISCELLANEOUS

6.1 Glossary of Terms

ACK – Message handshaking control code transmitted by the SAFLOK interface or PMS
interface to indicate it received a message properly from the other; acknowledge receipt
ASCII – American Standard Code for Information Interchange
CTS – Clear to send
DCD – Data carrier detect
DCE – Data communication equipment (ex: modem)
DRC – Detailed response code; standard field in SAFLOK interface messages
DSR – Data set ready
DST – Daylight-saving time
DTE – Data terminal equipment (ex: computer, printer)
DTR – Data terminal ready
ENQ – Message handshaking control code transmitted by the SAFLOK interface or PMS
interface to request retransmission of an ACK or NAK; enquiry
ETX – Message envelope control code transmitted by the PMS interface and SAFLOK
interface as a trailer of the message to indicate the end of message data; end of text
GRC – General response code; standard field in SAFLOK interface messages
KLC – Key level code
LRC checksum – Longitudinal redundancy check
Message – A single communications message sent from the PMS interface to the
SAFLOK interface or vice versa; every request includes several messages
NAK – Message handshaking control code transmitted by the SAFLOK interface or PMS
interface to indicate it did not receive a message from the other; not acknowledging
receipt
PFC – PMS function code; standard field in PMS interface messages
PMS – Property management system
PMS Interface – The property management system’s interface device (connected to the
PMS network and RS232 line to the SAFLOK interface)
PMS Terminal – Property management system’s registration terminal (connected to the
PMS network)
PRS – PMS request server
Request – A group of message exchanges between the PMS interface and the SAFLOK
interface that completes a SAFLOK interface function or SAFLOK system transaction;
requests are initiated by the PMS interface
RTS – Request to send
RXD – Receive data
SAFLOK Encoder – Key encoder device (connected to the SAFLOK network)
SAFLOK Interface – SAFLOK’s interface computer, typically the SAFLOK System 6000
server (connected to the PMS interface via an RS232 cable or over the TCP/IP network
via sockets)
SRC – SAFLOK response code; standard field in SAFLOK interface messages
STX – Message envelop control code transmitted by the PMS interface and SAFLOK
interface as a header of the incoming message; start of text
Transaction/TX – A SAFLOK system function or operation requiring the SAFLOK
interface to request information from the SAFLOK System 6000 computer; A PMS
interface message can specify a transaction code (TXC); making a new key would be
one transaction, and making a duplicate key would be another transaction
TXC – Transaction code; standard field in PMS interface messages
TXD – Transmit data

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 43 of 73

XOFF – Line control code transmitted by the PMS interface to stop the SAFLOK
interface from transmitting to it
XON – Line control code transmitted by the PMS interface to explicitly clear the XOFF
condition

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 44 of 73

6.2 Example: How To Calculate a Message Checksum and Add Message Control
Codes
For a message to request a new key for Room 101, for example, a PFC 20 message
would need to be formatted (see Section 3.5).

Message
Text
Byte # Hex Description
1-2 32 30 PFC 20
3-4 30 32 To SAFLOK interface station #2
5-6 30 32 From PMS interface station #2
7-9 30 30 31 Unique PMS terminal number or PMS
interface request #1
10-12 30 30 31 Transaction 1
13-19 32 35 30 20 20 20 20 SAFLOK password 250 (ASCII equivalent)
20-24 31 30 31 20 20 Key/room number 101 (ASCII equivalent)
25 31 Room key level 1
26-27 30 34 Encoder station #4 to make key at
28-29 46 46 LED control information FF
30-31 30 31 Number of keys to make, 1
32-37 31 32 30 31 30 34 Projected check-out date, 12/01/04
38-41 31 33 30 30 Projected check-out time, 1:00 p.m.
42-47 31 32 30 31 30 34 Key expiration date, 12/01/04
48-51* 31 36 30 30 Key expiration time, 4:00 p.m.
52* 30 Pass number info field, 0 = add to auto pass
numbers
53-64* 30 30 30 30 30 30 30
30 30 30 30 30 Pass numbers, 000000000000
*Delete unnecessary data bytes

Although there are 64 bytes in the message, data bytes 50 through 64 can be excluded
from the message because they are the last additional data bytes in the message and
have a 20 or 30 hex value. For this example, we will delete them.

The protocol control code ETX (03 hex) – or end text – would then be added to the
message:
32 30 30 32 30 32 30 30 31 30 30 31 32 35 30 20 20 20 20 31 30 31 20 20
31 30 34 46 46 30 31 31 32 30 31 38 39 31 33 30 30 31 32 30 31 38 39 31 36 03

The LRC checksum would then be calculated and added to the message:
XOR every byte = 00010111 binary = 17 hex
32 30 30 32 30 32 30 30 31 30 30 31 32 35 30 20 20 20 20 31 30 31 20 20
31 30 34 46 46 30 31 31 32 30 31 38 39 31 33 30 30 31 32 30 31 38 39 31 36 03
17

The protocol control STX code (02 hex) – or start text – would then be added to the
message:
02 32 30 30 32 30 32 30 30 31 30 30 31 32 35 30 20 20 20 20 31 30 31 20 20
31 30 34 46 46 30 31 31 32 30 31 38 39 31 33 30 30 31 32 30 31 38 39 31 36 03
17

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 45 of 73

6.3 ASCII-to-Hexadecimal Conversion Table

Shaded bars identify valid ASCII characters for the key number and lock number fields.

High 0 1 2 3 4 5 6 7
char\
Low char
0 NUL DLE SP 0 @ P ` p

1 SOH DC1 ! 1 A Q a q
2 STX DC2 " 2 B R b r
3 ETX DC3 # 3 C S c s
4 EOT DC4 $ 4 D T d t
5 END NAK % 5 E U e u
6 ACK SYN & 6 F V f v
7 BEL ETB 7 G W g w

8 BS CAN ( 8 H X h x
9 HT EM ) 9 I Y i y
A LF SUB * : J Z j z
B VT ESC + ; K [ k {
C FF FS , < L \ l |
D CR GS _ = M ] m }
E SO RS . > N ^ n ~
F SI US / ? O o DEL
Examples: ASCII 4D = M, space = ASCII 20

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 46 of 73

7.0 ERROR/MESSAGE CONTROL CODES

GRC- GRC- PMS

DRC DRC Appli- Request Terminal
Deci- Hex cation Status Message Description
mal Display

G-xxx 00-zz Interface Termi- PMS KEY REQUEST SUCCESSFULLY

nated response – COMPLETED
NA,
PMS log –
no

1-190 01-BE Encoder Active PMS ENCODER TIMED OUT WAITING FOR KEY TO
key response – BE INSERTED. TRY KEY AGAIN?
21,
PMS log –
no

1-192 01-C0 Encoder Active PMS ENCODER HAS JAMMED KEY INSIDE. PRESS
key response – RUN MOTOR SWITCH. TRY KEY AGAIN?
21,
PMS log –
no

1-193 01-C1 Encoder Active PMS KEY WAS REJECTED. KEY MUST BE FACE
key response – UP AND POINTING IN. TRY KEY AGAIN?
21,
PMS log –
no

1-194 01-C2 Encoder Active PMS KEY WAS REJECTED AND MAY BE
key response – DAMAGED. WILL YOU TRY DIFFERENT KEY?
21,
PMS log –
no

1-205 01-CD TX 1 Active PMS ROOM OCCUPIED W/KEY # nnnn, LV yy NOT

response – DUE mm/dd/yy. MAKE NEW KEY ANYWAY?
21,
PMS log –
no

1-205 01-CD TX 18 Active PMS ROOM OCCUPIED W/KEY # nnnn, LV yy NOT

response – DUE mm/dd/yy. CHECK IN PRE-REG
21, ANYWAY?
PMS log –
no

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 47 of 73

1-206 01-CE TX 1 Active PMS ROOM OCCUPIED W/KEY # nnnn, LV yy

response – CHECK-OUT mm/dd/yy. MAKE NEW KEY
21, ANYWAY?
PMS log –
no

1-206 01-CE TX 3 Active PMS KEY # nnnn LV yy MAY BE OUT OF

response – SEQUENCE AND NOT WORK. CONTINUE
21, ANYWAY?
PMS log –
no

1-206 01-CE TX 18 Active PMS ROOM OCCUPIED W/KEY # nnnn, LV yy

response – CHECK-OUT mm/dd/yy. CHECK IN PRE-REG
21, ANYWAY?
PMS log –
no

1-207 01-CF TX 1 Active PMS NEW KEYS WERE MADE mm/dd/yy hh:mm
response – AND WILL BE CANCELLED. MAKE NEW KEYS
21, ANYWAY?
PMS log –
no

1-208 01-D0 TX 1 Active PMS IF DISPLAY PRE-REG GUEST NAME IS NULL

response – IN SAFLOK MESSAGE: PRE-REG KEY # nnnn
21, LV yy DUE mm/dd/yy MAKE NEW KEY
PMS log – ANYWAY? OTHERWISE DISPLAY PRE-REG
no GUEST NAME IS NOT NULL IN SAFLOK
MESSAGE: PRE-REG KEY # nnnn LV vv FOR
aaaaaaaaaaaaaaaaaaaa. MAKE NEW KEY
ANYWAY?

1-208 01-CF TX 18 Active PMS IF DISPLAY PRE-REG GUEST NAME IS NULL

response – IN SAFLOK MESSAGE: PRE-REG KEY # nnnn
NA, LV yy DUE mm/dd/yy GIVE GUEST PRE-REG?
PMS log – OTHERWISE DISPLAY PRE-REG GUEST
no NAME IS NOT NULL IN SAFLOK MESSAGE:
PRE-REG KEY # nnnn LV yy FOR
aaaaaaaaaaaaaaaaaaaa. GIVE GUEST PRE-
REG?

1-211 01-D3 TX 3 Active PMS CURRENT GUEST KEY IS KEY # nnnn, LV yy.
response – MAKE DUPLICATE KEY ANYWAY?
21,
PMS log –
no

1-211 01-D3 TX 14 Active PMS CURRENT GUEST KEY IS KEY # nnnn, LV yy.
response – CONTINUE WITH ORIGINAL KEY ANYWAY?
21,
PMS log –
no

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 48 of 73

1-211 01-D3 TX 14 Active PMS CURRENT GUEST KEY IS KEY # nnnn, LV yy.
response – CHECK OUT ORIGINAL KEY ANYWAY?
21,
PMS log –
no

1-211 01-D3 TX 18 Active PMS PRE-REG KEYS # nnnn LV yy WILL EXPIRE

response – mm/dd/yy hh:mm. CONTINUE?
21,
PMS log –
no

1-213 01-D5 TX 3 Active PMS KEY # nnnn LV yy IS DUE FOR OR CHECKED

response – OUT. MAKE DUPLICATE KEYS ANYWAY?
21,
PMS log –
no

1-214 01-D6 TX 14 Active PMS ALL KEYS WILL EXPIRE mm/dd/yy hh:mm
response – BEFORE CHECK-OUT TIME. CONTINUE
21, ANYWAY?
PMS log –
no

1-215 01-D7 TX 1 Active PMS CHECK-OUT CONFLICTS WITH PRE-REG

response – CHECK-IN mm/dd/yy hh:mm. CONTINUE
21, ANYWAY?
PMS log –
no

1-215 01-D7 TX 14 Active PMS CHECK-OUT CONFLICTS WITH PRE-REG

response – CHECK-IN mm/dd/yy hh:mm. CONTINUE
21, ANYWAY?
PMS log –
no

1-216 01-D8 TX 18 Active PMS CHECK-OUT DATE mm/dd/yy APPEARS TOO

response – FAR IN FUTURE. CONTINUE ANYWAY?
21,
PMS log –
no

1-223 01-DF TX 1 Active PMS ROOM OCCUPIED W/PRE-REG KEY # nnnn,

response – LV yy CHECKED IN mm/dd/yy. CONTINUE
21, ANYWAY?
PMS log –
no

1-223 01-DF TX 3 Active PMS KEY # nnnn, LV yy MAY BE EXPIRED. MAKE

response – DUPLICATE KEYS ANYWAY?
21,
PMS log –
no

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 49 of 73

1-223 01-DF TX 14 Active PMS KEY # nnnn, LV yy WAS PRE-REG CHECKED

response – IN mm/dd/yy hh:mm. IS THIS THE GUEST?
21,
PMS log –
no

1-223 01-DF TX 15 Active PMS THIS IS PRE-REG KEY # nnnn, LV yy AUTO

response – CHECKED IN mm/dd/yy. CONTINUE?
21,
PMS log –
no

1-225 01-E1 TX 3 Active PMS KEY # nnnn, LV yy IS DUE FOR OR CHECKED

response – OUT. MAKE DUPLICATE KEYS ANYWAY?
NA,
PMS log –
no

1-225 01-E1 TX 14 Active PMS KEY # nnnn, LV yy WAS PRE-REG CHECKED

response – IN mm/dd/yy hh:mm. IS THIS THE GUEST?
21,
PMS log –
no

1-225 01-E1 TX 15 Active PMS THIS IS PRE-REG KEY # nnnn, LV yy

response – MANUALLY CHECKED IN mm/dd/yy.
NA, CONTINUE?
PMS log –
no

1-228 01-E4 TX 14 Active PMS KEY # nnnn, LV yy WAS MANUALLY CHECKED

response – OUT mm/dd/yy hh:mm. CHECK BACK IN?
21,
PMS log –
no

1-229 01-E5 TX 3 Active PMS NEW KEY DATE mm/dd/yy hh:mm IS AHEAD
response – OF SYSTEM TIME. MAKE DUPLICATE KEYS
21, ANYWAY?
PMS log –
no

1-229 01-E5 TX 14 Active PMS KEY # nnnn, LV yy WAS CONSIDERED

response – CHECKED OUT mm/dd/yy hh:mm. CHECK
21, BACK IN?
PMS log –
no

1-230 01-E6 TX 3 Active PMS KEY WAS A PRE-REG AUTO CHECKED IN

response – mm/dd/yy. IS THIS THE GUEST’S KEY?
21,
PMS log –
no

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 50 of 73

1-230 01-B6 TX 14 Active PMS KEY # nnnn, LV yy WAS AUTO CHECKED OUT
response – BY A PRE-REG mm/dd/yy hh:mm. CHECK IN?
21,
PMS log –
no

1-230 01-E6 TX 18 Active PMS PRE-REG KEYS WILL NOT WORK UNTIL
response – mm/dd/yy hh:mm. CONTINUE?
21,
PMS log –
no

1-231 01-E7 TX 3 Active PMS KEY WAS A PRE-REG MANUALLY CHECKED

response – IN mm/dd/yy. IS THIS THE GUEST’S KEY?
21,
PMS log –
no

1-xxx 01-Z2 Any TX Active PMS GRC 01, DRC zz, TXC ww ERROR –
response – CONTINUE ANYWAY?
21,
PMS log –
yes

2-161 02-A1 Encoder Active PMS REQUESTED ENCODER IS NOT ONLINE OR

request response – DOES NOT EXIST. CHANGE ENCODER # AND
22, RE-REQUEST.
PMS log –
no

2-162 02-A2 Encoder Active PMS REQUESTED ENCODER IS NOT

request response – RESPONDING. CHECK ENCODER OR
22, CHANGE ENCODER # AND RE-REQUEST.
PMS log –
no

2-163 02-A3 Encoder Active PMS STATION # xx IS NOT AN ENCODER. CHANGE

request response – ENCODER # AND RE-REQUEST.
22,
PMS log –
no

2-192 02-D0 Encoder Active PMS ENCODER xx HAS JAMMED KEY INSIDE.
request response – PRESS RUN MOTOR SWITCH OR CHANGE
22, ENCODER #.
PMS log –
no

2-197 02-C5 Encoder Active PMS STATION # xx HAS A BAD ROM. CONTACT
request response – SAFLOK. CHANGE ENCODER # AND RE-
22, REQUEST.
PMS log –
no

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 51 of 73

2-198 02-C6 Encoder Active PMS REQUESTED ENCODER IS BUSY WITH

request response – ANOTHER REQUEST. RETRY LATER OR
22, CHANGE ENCODER # AND RE-REQUEST.
PMS log –
no

2-xxx 02-zz Any TX Active PMS GRC 02, DRC zz, TXC ww ERROR – CHANGE
response – ENCODER # AND RE-REQUEST.
NA,
PMS log –
yes

3-001 03-01 TXHelp Termi- PMS PMS INTERFACE REQUESTED UNAVAILABLE

nated response – TRANSACTION NUMBER
NA,
PMS log –
yes

3-002 03-02 TXHelp Termi- PMS THE REQUESTED KEY LEVEL IS NOT
nated response – RELEVANT FOR THIS TRANSACTION
NA,
PMS log –
no

3-025 03-25 Computer Termi- PMS SAFLOK ENI CORE AND TX SOFTWARE IS
nated response – INCOMPATIBLE. CONTACT SAFLOK.
NA,
PMS log –
no

3-026 03-1A Interface Termi- PMS PMS INTERFACE REQUESTED AN INVALID

nated response – TRANSACTION. CONTACT PMS COMPANY.
NA,
PMS log –
yes

3-027 03-1B Interface Termi- PMS PMS INTERFACE SENT PASSWORD LESS
nated response – THAN THREE CHARACTERS. CONTACT PMS
NA, COMPANY.
PMS log –
yes

3-030 03-1E Computer Termi- PMS YOUR SAFLOK INTERFACE PASSWORD IS

nated response – INVALID. MUST CHANGE TO PMS
NA, PASSWORD.
PMS log –
yes

3-031 03-1F Computer Termi- PMS YOU ARE NOT AUTHORIZED IN SAFLOK TO
nated response – DO THIS TRANSACTION. MUST FIRST BE
NA, GIVEN AUTHORIZATION.
PMS log –
yes

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 52 of 73

3-032 03-20 Computer Termi- PMS SAFLOK MAIN COMPUTER IS MISSING

nated response – REQUIRED DATA FILES. CONTACT SAFLOK.
NA,
PMS log –
no

3-039 03-27 Computer Termi- PMS REQUESTED KEY NUMBER DOES NOT
nated response – EXIST IN SAFLOK DATABASE. CONTACT
NA, SAFLOK TO ADD.
PMS log –
no

3-045 03-2D Computer Termi- PMS SAFLOK MAIN COMPUTER IS MISSING

nated response – REQUIRED KEY FILES. CONTACT SAFLOK.
NA,
PMS log –
no

3-047 03-2F Computer Termi- PMS SAFLOK COMPUTER IS ARCHIVING OR

nated response – REPLACING FILES. MUST WAIT UNTIL DONE.
NA,
PMS log –
no

3-050 03-32 Computer Termi- PMS REQUESTED KEY NUMBER IS CURRENTLY

nated response – BEING ACCESSED BY ANOTHER TERMINAL.
NA,
PMS log –
no

3-051 03-33 Computer Termi- PMS KEY # nnnn, LV yy IS INCORRECTLY

nated response – DESIGNATED AS FAILSAFE. CONTACT
NA, SAFLOK.
PMS log –
no

3-052 03-34 Computer Termi- PMS YOU ARE NOT AUTHORIZED IN SAFLOK TO
nated response – MAKE THE REQUESTED KEY
NA,
PMS log –
yes

3-100 03-64 Interface Termi- PMS PMS INTERFACE MESSAGE FORMAT IS

nated response – INCORRECT. CONTACT PMS COMPANY.
NA,
PMS log –
yes

3-101 03-65 Interface Termi- PMS PMS INTERFACE USED AN INVALID PMS
nated response – TERMINAL REQUEST #. CONTACT PMS
NA, COMPANY.
PMS log –
yes

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 53 of 73

3-102 03-66 Interface Termi- PMS THE KEY LEVEL MUST BE BETWEEN 1 AND
nated response – 4. CHANGE AND RE-REQUEST.
NA,
PMS log –
yes

3-103 03-67 Interface Termi- PMS REQUESTED KEY CONTAINS INVALID

nated response – CHARACTERS. RE-ENTER KEY NUMBER AND
NA, RE-REQUEST.
PMS log –
yes

3-104 03-68 Interface Termi- PMS KEY NUMBER CANNOT BE NULL. RE-ENTER
nated response – KEY NUMBER AND RE-REQUEST.
NA,
PMS log –
yes

3-107 03-6B Interface Termi- PMS PMS INTERFACE REQUESTED AN INVALID

nated response – DATE. CONTACT PMS COMPANY.
NA,
PMS log –
yes

3-108 03-6C Interface Termi- PMS PMS INTERFACE REQUESTED AN INVALID

nated response – TIME. CONTACT PMS COMPANY.
NA,
PMS log –
yes

3-109 03-6D Interface Termi- PMS THE ENCODER STATION MUST BE BETWEEN
nated response – 1 AND 99. CHANGE AND RE-REQUEST.
NA,
PMS log –
yes

3-110 03-6E Interface Termi- PMS YOU MUST REQUEST AT LEAST 1 KEY.
nated response – CHANGE AND RE-REQUEST.
NA,
PMS log –
yes

3-111 03-6F Interface Termi- PMS INVALID PMS INTERFACE RESPONSE (21 OR
nated response – 22). CONTACT PMS COMPANY.
NA,
PMS log –
yes

3-112 03-70 Interface Termi- PMS SAFLOK INTERFACE COULD NOT ACCEPT
nated response – ANOTHER REQUEST. RE-REQUEST IF
NA, DESIRED.
PMS log –
yes

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 54 of 73

3-113 03-71 Interface Termi- PMS PMS INTERFACE LOST YOUR REQUEST. RE-
nated response – REQUEST IF DESIRED.
NA, PMS log
– no

3-114 03-72 Interface Termi- PMS SAFLOK TIMED OUT WAITING FOR A
nated response – CONTINUATION RESPONSE. RE-REQUEST IF
NA, PMS log DESIRED.
– no

3-115 03-73 Interface Termi- PMS SAFLOK TIMED OUT YOUR REQUEST –
nated response – GENERAL COMMUNICATIONS TIME OUT
NA, OCCURRED.
PMS log –
yes

3-116 03-74 Interface Termi- PMS NO ALTERNATE ENCODER WAS SELECTED.

nated response – REQUEST IS TERMINATED.
NA,
PMS log –
no

3-117 03-75 Interface Termi- PMS YOU DID NOT OVERRIDE ERROR. REQUEST
nated response – IS TERMINATED.
NA,
PMS log –
no

3-118 03-76 Interface Termi- PMS INCOMPATIBLE SAFLOK AND PMS

nated response – INTERFACE SOFTWARE. CONTACT SAFLOK
NA, AND PMS COMPANY.
PMS log –
yes

3-119 03-77 Interface Termi- PMS REQUESTED KEY IS A BATCH KEY. USE
nated response – SAFLOK TERMINAL OR CONTACT SAFLOK.
NA,
PMS log –
yes

3-120 03-78 Interface Termi- PMS REQUESTED KEY AND LEVEL IS A FAILSAFE
nated response – KEY. USE SAFLOK TERMINAL OR CONTACT
NA, SAFLOK.
PMS log –
yes

3-121 03-79 Interface Termi- PMS SAFLOK LOST YOUR REQUEST. RE-
nated response – REQUEST IF DESIRED.
NA,
PMS log –
no

3-122 03-7A Interface Termi- PMS PMS SENT PFC 22 OR 21 WHEN SAFLOK DID
nated response – NOT EXPECT EITHER. CONTACT PMS
© SAFLOK Proprietary and Confidential AS 10/04
SAFLOK System 6000™ PMS Interface Pg. 55 of 73

NA, COMPANY.
PMS log –
no

3-123 03-7B Interface Termi- PMS SAFLOK SENT STANDARD GRC BUT PMS
nated response – INDICATED INVALID GRC CODE. CONTACT
NA, PMS COMPANY.
PMS log –
no

3-124 03-7C Interface Termi- PMS PMS INTERFACE USED AN INVALID PASS
nated response – OPTION > 1. CONTACT PMS COMPANY.
NA,
PMS log –
no

3-125 03-7D Interface Termi- PMS PMS INTERFACE USED AN INVALID PASS # =
nated response – 0 or > 12. CONTACT PMS COMPANY.
NA,
PMS log –
no

3-126 03-7E Interface Termi- PMS PMS INTERFACE USED AN INVALID # OF

nated response – SECONDS. CONTACT PMS COMPANY.
NA,
PMS log –
no

3-127 03-7F Interface Termi- PMS PMS INTERFACE USED INCORRECT

nated response – DESTINATION STATION #. CONTACT PMS
NA, COMPANY.
PMS log –
yes

3-128 03-80 Interface Termi- PMS PMS INTERFACE USED NON-NUMERIC

nated response – CHARACTERS FOR NUMERIC FIELD.
NA, CONTACT PMS COMPANY.
PMS log –
yes

3-132 03-84 Interface Termi- PMS SAFLOK ERROR NOT HANDLED PROPERLY.
nated response – CONTACT SAFLOK.
NA,
PMS log –
no

3-133 03-85 Interface Termi- PMS TIMED OUT WAITING FOR ENI BUFFER TO
nated response – PMS INTERFACE.
NA,
PMS log –
no

3-134 03-86 Interface Termi- PMS TIMED OUT WAITING FOR SAFLOK
nated response – COMPUTER TO ACCEPT REQUEST.
NA,
© SAFLOK Proprietary and Confidential AS 10/04
SAFLOK System 6000™ PMS Interface Pg. 56 of 73

PMS log –
no

3-148 03-94 Computer Termi- PMS LOCK mmmmm FOR KEY # nnnn, LV yy IS
nated response – INACCESSIBLE. RESTORE ACCESS (TX 57)
NA, FIRST.
PMS log –
no

3-149 03-95 Computer Termi- PMS KEY # nnnn, LV yy IS INACCESSIBLE. MUST

nated response – RESTORE ACCESS FIRST (TX 25).
NA,
PMS log –
no

3-161 03-A1 Encoder Termi- PMS REQUESTED ENCODER IS NOT ONLINE OR

request nated response – DOES NOT EXIST. USE DIFFERENT
NA, ENCODER.
PMS log –
no

3-162 03-A2 Encoder Termi- PMS REQUSETED ENCODER IS NOT

request nated response – RESPONDING. CONTACT SAFLOK. USE
NA, DIFFERENT ENCODER.
PMS log –
no

3-163 03-A3 Encoder Termi- PMS REQUESTED STATION IS NOT AN

request nated response – ENCODER. USE DIFFERENT ENCODER.
NA,
PMS log –
no

3-189 03-BD System Termi- PMS ORIGINAL REQUEST WAS ABORTED PER
all nated response – ABORT MESSAGE.
NA,
PMS log –
no

3-190 03-BE System Termi- PMS REQUESTED ENCODER TIMED OUT WAITING
all nated response – FOR KEY TO BE INSERTED. RETRY IF
NA, DESIRED.
PMS log –
no

3-192 03-C0 Encoder Termi- PMS REQUESTED ENCODER HAS A JAMMED KEY
request nated response – INSIDE. PRESS RUN MOTOR SWITCH FIRST.
NA,
PMS log –
no

3-193 03-C1 Encoder Termi- PMS KEY WAS REJECTED. KEY MUST BE FACE
key nated response – UP AND POINTING IN. RETRY IF DESIRED.
NA,
PMS log –
© SAFLOK Proprietary and Confidential AS 10/04
SAFLOK System 6000™ PMS Interface Pg. 57 of 73

no

3-194 03-C2 Encoder Termi- PMS KEY WAS REJECTED AND MAY BE
key nated response – DAMAGED. USE A DIFFERENT KEY AND
NA, RETRY IF DESIRED.
PMS log –
no

3-197 03-C5 Encoder Termi- PMS REQUESTED ENCODER HAS A BAD ROM.
key nated response – CONTACT SAFLOK. USE DIFFERENT
NA, ENCODER.
PMS log –
no

3-198 03-C6 Encoder Termi- PMS REQUESTED ENCODER IS BUSY WITH

request nated response – ANOTHER REQUEST. USE DIFFERENT
NA, ENCODER.
PMS log –
no

3-199 03-C7 Encoder Termi- PMS ENCODER DID NOT RESPOND. CHECK IT
key nated response – FOR PROBLEMS. RETRY IF DESIRED.
NA,
PMS log –
no

3-200 03-C8 TX 18 Termi- PMS NO PRE-REG KEY EXISTS FOR REQUESTED

nated response – KEY NUMBER. TRY ANOTHER KEY OR MAKE
NA, NEW KEYS.
PMS log –
no

3-201 03-C9 TX 3 Termi- PMS REQUESTED KEY IS INHIBITED. REPLACE

nated response – ALL GUEST KEYS WITH NEW KEYS.
NA,
PMS log –
no

3-201 03-C9 TX 18 Termi- PMS NO PRE-REG KEY EXISTS. MAKE NEW KEYS.
nated response –
NA,
PMS log –
no

3-202 03-CA TX 1 Termi- PMS REQUESTED KEY IS NOT PROGRAMMED IN

nated response – LOCKS. REPROGRAM LOCK FIRST.
NA,
PMS log –
no

3-202 03-CA TX 3 Termi- PMS REQUESTED KEY IS NOT PROGRAMMED IN

nated response – LOCKS. REPROGRAM LOCK FIRST.
NA,
PMS log –
© SAFLOK Proprietary and Confidential AS 10/04
SAFLOK System 6000™ PMS Interface Pg. 58 of 73

no

3-202 03-CA TX 14 Termi- PMS CANNOT CHANGE REQUEST KEYS

nated response – CHECKOUT DATE/TIME BECAUSE IT HAS
NA, EITHER NEVER BEEN MADE OR ALREADY
PMS log – CHECKED OUT OR OLD PRE-REG EXISTS.
no

3-202 03-CA TX 15 Termi- PMS CANNOT CHECKOUT REQUESTED KEY

nated response – BECAUSE IT HAS EITHER NEVER BEEN
NA, MADE OR ALREADY CHECKED OUT OR OLD
PMS log – PRE-REG EXISTS.
no

3-202 03-CA TX 18 Termi- PMS REQUESTED KEY IS NOT PROGRAMMED IN

nated response – LOCKS. CANCEL PRE-REG AND
NA, REPROGRAM LOCK.
PMS log –
no

3-204 03-CC TX 1 Termi- PMS REQUESTED KEY IS NOT PROGRAMMED IN

nated response – LOCKS. REPROGRAM LOCK FIRST.
NA,
PMS log –
no

3-204 03-CC TX 3 Termi- PMS REQUESTED KEY IS NOT PROGRAMMED IN

nated response – LOCKS. REPROGRAM LOCK FIRST.
NA,
PMS log –
no

3-204 03-CC TX 14 Termi- PMS REQUESTED KEY IS NOT A GUEST KEY AND
nated response – HAS NEVER BEEN MADE – CHECK-OUT IS
NA, NOT RELEVANT.
PMS log –
no

3-204 03-CC TX 15 Termi- PMS REQUESTED KEY IS NOT A GUEST KEY AND
nated response – NEVER BEEN MADE – CHECK-OUT IS NOT
NA, RELEVANT.
PMS log –
no

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 59 of 73

3-204 03-CC TX 18 Termi- PMS IF DISPLAY PRE-REG GUEST NAME IS NULL

nated response – IN SAFLOK MESSAGE: PRE-REG DUE
NA, mm/dd/yy hh:mm IS KEY # nnnn, LV yy, RE-
PMS log – REQUEST. OTHERWISE DISPLAY PRE-REG
no GUEST NAME IS NOT NULL IN SAFLOK
MESSAGE: PRE-REG FOR
aaaaaaaaaaaaaaaaaaaaa IS KEY # nnnn, LV yy,
RE-REQUEST.

3-205 03-CD TX 1 Termi- PMS OCCUPIED W/KEY # nnnn, LV yy CHECK-OUT

nated response – NOT DUE mm/dd/yy. MUST CHECK OUT
NA, FIRST.
PMS log –
no

3-205 03-CD TX 3 Termi- PMS KEY # nnnn, LV yy MAY BE OUT OF

nated response – SEQUENCE. REPLACE ALL KEYS WITH NEW.
NA,
PMS log –
no

3-205 03-CD TX 14 Termi- PMS KEY # nnnn, LV yy HAS NEVER BEEN MADE.
nated response – ALREADY CHECKED OUT.
NA,
PMS log –
no

3-205 03-CD TX 15 Termi- PMS KEY # nnnn, LV yy HAS NEVER BEEN MADE.
nated response – ALREADY CHECKED OUT.
NA,
PMS log –
no

3-205 03-CD TX 18 Termi- PMS OCCUPIED W/KEY # nnnn, LV yy .CHECK-OUT

nated response – NOT DUE mm/dd/yy. MUST CHECK OUT
NA, FIRST.
PMS log –
no

3-206 03-CE TX 1 Termi- PMS OCCUPIED W/KEY # nnnn, LV yy. CHECK-OUT

nated response – OVERDUE mm/dd/yy. MUST CHECK OUT
NA, FIRST.
PMS log –
no

3-206 03-CE TX 3 Termi- PMS REPLACE ALL KEYS # nnnn, LV yy WITH NEW
nated response – KEYS.
NA,
PMS log –
no

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 60 of 73

3-206 03-CE TX 18 Termi- PMS OCCUPIED W/KEY # nnnn, LV yy. CHECK-OUT

nated response – OVERDUE mm/dd/yy. MUST CHECK OUT
NA, FIRST.
PMS log –
no

3-207 03-CF TX 1 Termi- PMS MAKE DUPLICATE KEYS OR WAIT UNTIL

nated response – mm/dd/yy hh:mm TO MAKE NEW KEYS.
NA,
PMS log –
no

3-207 03 -CF TX 14 Termi- PMS KEY # nnnn, LV yy IS NOT A GUEST KEY.

nated response – CHECK-OUT IS NOT RELEVANT.
NA,
PMS log –
no

3-207 03-CF TX 15 Termi- PMS KEY # nnnn, LV yy IS NOT A GUEST KEY.

nated response – CHECK-OUT IS NOT RELEVANT.
NA,
PMS log –
no

IF TRANSACTION IS NOT IN KEY REQUEST

SCREEN: IF DISPLAY PRE-REG GUEST NAME
IS NULL IN SAFLOK MESSAGE: CHECK IN
PRE-REG EARLY DUE mm/dd/yy (KEY # nnnn,
LV yy, 0 KEYS) OR CANCEL. OTHERWISE
DISPLAY PRE-REG GUEST NAME IS NOT
PMS NULL IN SAFLOK MESSAGE: CHECK IN PRE-
response – REG FOR aaaaaaaaaaaaaaaaaaaa (KEY #
Termi- NA, nnnn, LV yy, 0 KEYS) OR CANCEL. IF
3-208 03-D0 TX 1
nated PMS log – TRANSACTION IS IN KEY REQUEST SCREEN:
no IF DISPLAY PRE-REG GUEST NAME IS NULL
IN SAFLOK MESSAGE: CHECK IN PRE-REG
EARLY DUE mm/dd/yy (KEY # nnnn, LV yy, TX
18) OR CANCEL. OTHERWISE DISPLAY PRE-
REG GUEST NAME IS NOT NULL IN SAFLOK
MESSAGE: CHECK IN PRE-REG FOR
aaaaaaaaaaaaaaaaaaaaaaaaa (KEY # nnnn, LV
yy, TX 18) OR CANCEL.

3-208 03-D0 TX 3 Termi- PMS TOO LONG SINCE LAST NEW KEY # nnnn, LV
nated response – yy MADE mm/dd/yy. REPLACE KEYS WITH
NA, NEW.
PMS log –
no

3-208 03-D0 TX 14 Termi- PMS KEY # nnnn, LV yy WAS MANUALLY CHECKED

nated response – OUT mm/dd/yy hh:mm.
NA,
PMS log –
no

3-208 03-D0 TX 15 Termi- PMS KEY # nnnn, LV yy WAS MANUALLY CHECKED

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 61 of 73

nated response – OUT mm/dd/yy hh:mm.

NA,
PMS log –
no

3-208 03-D0 TX 18 Termi- PMS CHECK IN PRE-REG EARLY OR MAKE NEW

nated response – KEYS FOR GUEST.
NA,
PMS log –
no

3-209 03-D1 TX 1 Termi- PMS IF DISPLAY PRE-REG GUEST NAME IS NULL

nated response – IN SAFLOK MESSAGE: CANCEL PRE-REG
NA, DUE mm/dd/yy (KEY # nnnn, LV yy) OR WAIT.
PMS log – OTHERWISE DISPLAY PRE-REG GUEST
no NAME IS NOT NULL IN SAFLOK MESSAGE:
CANCEL PRE-REG FOR
aaaaaaaaaaaaaaaaaaa (KEY # nnnn, LV yy) OR
WAIT.

3-209 03-D1 TX 14 Termi- PMS KEY # nnnn, LV yy WAS CONSIDERED

nated response – CHECKED OUT mm/dd/yy hh:mm.
NA,
PMS log –
no

3-209 03-D1 TX 15 Termi- PMS KEY # nnnn, LV yy WAS CONSIDERED

nated response – CHECKED OUT mm/dd/yy hh:mm.
NA,
PMS log –
no

3-209 03-D1 TX 18 Termi- PMS IF DISPLAY PRE-REG GUEST NAME IS NULL

nated response – IN SAFLOK MESSAGE: CAN’T CHECK IN PRE-
NA, REG EARLY. DUE mm/dd/yy hh:mm. USE
PMS log – SAFLOK OR WAIT. OTHERWISE DISPLAY
no PRE-REG GUEST NAME IS NOT NULL IN
SAFLOK MESSAGE: CAN’T CHECK IN PRE-
REG EARLY FOR aaaaaaaaaaaaaaaaaaaaa.
USE SAFLOK OR WAIT.

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 62 of 73

IF TRANSACTION IS NOT IN KEY REQUEST

SCREEN: IF DISPLAY PRE-REG GUEST NAME
IS NULL IN SAFLOK MESSAGE: CHECK IN
PRE-REG DUE mm/dd/yy (KEY # nnnn, LV yy, 0
KEYS) OR CANCEL. OTHERWISE DISPLAY
PRE-REG GUEST NAME IS NOT NULL IN
PMS SAFLOK MESSAGE: CHECK IN PRE-REG FOR
response – aaaaaaaaaaaaaaaaaaaa (KEY # nnnn, LV yy, 0
Termi- NA, KEYS) OR CANCEL. IF TRANSACTION IS IN
3-210 03-D2 TX 1
nated PMS log – KEY REQUEST SCREEN: IF DISPLAY PRE-
no REG GUEST NAME IS NULL IN SAFLOK
MESSAGE: CHECK IN PRE-REG DUE
mm/dd/yy (KEY # nnnn, LV yy, TX 18) OR
CANCEL OTHERWISE DISPLAY PRE-REG
GUEST NAME IS NOT NULL IN SAFLOK
MESSAGE: CHECK IN PRE-REG FOR
aaaaaaaaaaaaaaaaaaaa (KEY # nnnn LV yy TX
18) OR CANCEL.

3-210 03-D2 TX 3 Termi- PMS NOT THE CURRENT GUEST KEY. RE-
nated response – REQUEST KEY # nnnn, LV yy OR MAKE NEW
NA, KEYS.
PMS log –
yes

3-210 03-D2 TX 14 Termi- PMS NOT THE CURRENT GUEST KEY. RE-
nated response – REQUEST KEY # nnnn, LV yy.
NA,
PMS log –
yes

3-210 03-D2 TX 15 Termi- PMS NOT THE CURRENT GUEST KEY. RE-
nated response – REQUEST KEY # nnnn, LV yy.
NA,
PMS log –
yes

3-211 03-D3 TX 1 Termi- PMS CHECK-OUT mm/dd/yy hh:mm HAS ALREADY

nated response – PASSED. CHANGE CHECK-OUT FIRST.
NA,
PMS log –
no

3-211 03-D3 TX 3 Termi- PMS FOR CURRENT GUEST KEY, REQUEST KEY #
nated response – nnnn, LV yy OR MAKE NEW KEYS.
NA,
PMS log –
no

3-211 03-D3 TX 14 Termi- PMS TO CHANGE CURRENT GUEST KEY,

nated response – REQUEST KEY # nnnn, LV yy.
NA,
PMS log –
no

3-211 03-D3 TX 15 Termi- PMS TO CHECK OUT CURRENT GUEST KEY,

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 63 of 73

nated response – REQUEST KEY # nnnn, LV yy.

NA,
PMS log –
no

3-211 03-D3 TX 18 Termi- PMS CANCEL PRE-REG KEY # nnnn, LV yy AND

nated response – MAKE NEW KEYS FOR GUEST.
NA,
PMS log –
no

3-212 03-D4 TX 1 Termi- PMS IF KEY EXPIRATION IS NOT A KEY REQUEST

nated response – SCREEN FIELD: KEY EXPIRATION mm/dd/yy
NA, hh:mm IS BEFORE CHECK-OUT. CONTACT
PMS log – PMS COMPANY. OTHERWISE KEY
no EXPIRATION IS A KEY REQUEST SCREEN
FIELD: KEY EXPIRATION mm/dd/yy hh:mm IS
BEFORE CHECK-OUT. CHANGE EXPIRATION.

3-212 03-D4 TX 3 Termi- PMS KEY # nnnn, LV yy IS DUE FOR OR CHECKED

nated response – OUT. CHANGE CHECK-OUT OR MAKE NEW
NA, KEY.
PMS log –
no

3-212 03-D4 TX 14 Termi- PMS KEY # nnnn, LV yy WAS AUTO CHECKED OUT
nated response – BY A PRE-REG KEY mm/dd/yy hh:mm.
NA,
PMS log –
no

3-212 03-D4 TX 18 Termi- PMS PRE-REG KEYS WILL EXPIRE mm/dd/yy

nated response – hh:mm BEFORE CHECK-OUT. CANCEL AND
NA, MAKE NEW KEYS.
PMS log –
no

3-213 03-D5 TX 1 Termi- PMS IF KEY EXPIRATION IS NOT A KEY REQUEST

nated response – SCREEN FIELD: KEY EXPIRATION mm/dd/yy
NA, hh:mm HAS ALREADY PASSED. CONTACT
PMS log – PMS COMPANY. OTHERWISE KEY
no EXPIRATION IS A KEY REQUEST SCREEN
FIELD: KEY EXPIRATION mm/dd/yy hh:mm
HAS ALREADY PASSED. CHANGE
EXPIRATION.

3-213 03-D5 TX 3 Termi- PMS KEY # nnnn, LV yy ID IS DUE FOR OR

nated response – CHECKED OUT. CHANGE CHECK-OUT OR
NA, MAKE NEW KEY.
PMS log –
no

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 64 of 73

3-213 03-D5 TX 14 Termi- PMS CHECK-OUT mm/dd/yy hh:mm HAS ALREADY

nated response – PASSED. CORRECT CHECK-OUT.
NA,
PMS log –
no

3-213 03-D5 TX 15 Termi- PMS KEY WAS CHECKED OUT WHEN PRE-REG
nated response – KEY # nnnn, LV yy WAS AUTO CHECKED IN.
NA,
PMS log –
yes

3-213 03-D5 TX 18 Termi- PMS PRE-REG KEYS # nnnn, LV yy MADE ARE

nated response – EXPIRED. CANCEL PRE-REG AND ISSUE
NA, NEW KEYS.
PMS log –
no

3-214 03-D6 TX 1 Termi- PMS IF THE KEY EXPIRATION IS NOT A KEY

nated response – REQUEST SCREEN FIELD: KEY EXPIRATION
NA, mm/dd/yy CANNOT BE 9 YEARS FROM NOW.
PMS log – CONTACT PMS COMPANY. OTHERWISE KEY
no EXPIRATION IS A KEY REQUEST SCREEN
FIELD: KEY EXPIRATION mm/dd/yy CANNOT
BE 9 YEARS FROM NOW. CHANGE
EXPIRATION.

3-214 03-D6 TX 14 Termi- PMS REPLACE GUEST KEYS WITH NEW KEYS
nated response – FOR LATER KEY EXPIRATION.
NA,
PMS log –
no

3-215 03-D7 TX 1 Termi- PMS CHANGE CHECK-OUT BEFORE mm/dd/yy OR

nated response – CHANGE PRE-REG KEY # nnnn, LV yy CHECK-
NA, IN.
PMS log –
no

3-215 03-D7 TX 3 Termi- PMS IF KEY EXPIRATION IS NOT A KEY REQUEST

nated response – SCREEN FIELD: KEY EXPIRATION mm/dd/yy
NA, SHIFT hh:mm HAS ALREADY PASSED. USE
PMS log – SAFLOK. OTHERWISE KEY EXPIRATION IS A
no KEY REQUEST SCREEN FIELD: KEY
EXPIRATION mm/dd/yy SHIFT hh:mm HAS
ALREADY PASSED. CHANGE EXPIRATION.

3-215 03-D7 TX 14 Termi- PMS CHANGE CHECK-OUT BEFORE mm/dd/yy OR

nated response – CHANGE PRE-REG KEY # nnnn, LV yy CHECK-
NA, IN.
PMS log –
no

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 65 of 73

3-216 03-D8 TX 1 Termi- PMS CHANGE CHECK-OUT BEFORE mm/dd/yy AND

nated response – RE-REQUEST.
NA,
PMS log –
no

3-216 03-D8 TX 3 Termi- PMS KEY # nnnn, LV yy HAS MAX. 255 DUPLICATE
nated response – KEYS. REPLACE ALL KEYS WITH NEW.
NA,
PMS log –
no

3-216 03-D8 TX 14 Termi- PMS CHECK-OUT TOO FAR IN FUTURE. CHANGE

nated response – BEFORE mm/dd/yy hh:mm AND RE-REQUEST.
NA,
PMS log –
no

3-216 03-D8 TX 18 Termi- PMS CHANGE CHECK-OUT BEFORE mm/dd/yy

nated response – hh:mm AND RE-REQUEST.
NA,
PMS log –
no

3-217 03-D9 TX 1 Termi- PMS PASS # yy MUST BE SELECTED. CONTACT

nated response – PMS COMPANY OR ENTER #.
NA,
PMS log –
no

3-217 03-D9 TX 3 Termi- PMS IF KEY EXPIRATION IS NOT A KEY REQUEST

nated response – SCREEN FIELD: KEY EXPIRATION mm/dd/yy
NA, hh:mm IS BEFORE CHECK-OUT. CONTACT
PMS log – PMS COMPANY. OTHERWISE KEY
no EXPIRATION IS A KEY REQUEST SCREEN
FIELD: KEY EXPIRATION mm/dd/yy hh:mm IS
BEFORE CHECK-OUT. CHANGE EXPIRATION.

3-218 03-DA TX 1 Termi- PMS PASS # yy IS NOT A VALID PASS #. CONTACT

nated response – PMS COMPANY OR ENTER #.
NA,
PMS log –
no

3-218 03-DA TX 3 Termi- PMS IF KEY EXPIRATION mm/dd/yy hh:mm HAS

nated response – ALREADY PASSED, CHANGE CHECK-OUT
NA, FIRST. OTHERWISE KEY EXPIRATION IS A
PMS log – KEY REQUEST SCREEN FIELD: KEY
no EXPIRATION mm/dd/yy hh:mm HAS ALREADY
PASSED. CHANGE EXPIRATION.

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 66 of 73

3-219 03-DB TX 3 Termi- PMS IF KEY EXPIRATION IS NOT A KEY REQUEST

nated response – SCREEN FIELD: KEY EXPIRATION mm/dd/yy
NA, CANNOT BE 9 YEARS FROM NOW. CONTACT
PMS log – PMS COMPANY. OTHERWISE KEY
no EXPIRATION IS A KEY REQUEST SCREEN
FIELD: KEY EXPIRATION mm/dd/yy CANNOT
BE 9 YEARS FROM NOW. CHANGE
EXPIRATION.

3-220 03-DC TX 1 Termi- PMS IF KEY EXPIRATION IS NOT A KEY REQUEST

nated response – SCREEN FIELD: KEY EXPIRATION mm/dd/yy
NA, SHIFT hh:mm HAS ALREADY PASSED.
PMS log – CONTACT PMS COMPANY. OTHERWISE KEY
no EXPIRATION IS A KEY REQUEST SCREEN
FILED: KEY EXPIRATION mm/dd/yy SHIFT
hh:mm HAS ALREADY PASSED. CHANGE
EXPIRATION.

3-221 03-DD TX 3 Termi- PMS PASS # yy MUST BE SELECTED. CONTACT

nated response – PMS COMPANY OR ENTER #.
NA,
PMS log –
no

3-222 03-DE TX 3 Termi- PMS PASS # yy IS NOT A VALID PASS #. CONTACT

nated response – PMS COMPANY OR ENTER #.
NA,
PMS log –
no

3-223 03-DF TX 1 Termi- PMS PRE-REG KEY # nnnn, LV yy WAS CHECKED

nated response – IN mm/dd/yy. MUST USE IT OR CHECK OUT
NA, FIRST.
PMS log –
no

3-223 03-DF TX 3 Termi- PMS USE SAFLOK TERMINAL TO MAKE KEY #

nated response – nnnn, LV yy.
NA,
PMS log –
no

3-223 03-DF TX 14 Termi- PMS CHECK-OUT CHANGE HAS BEEN IGNORED.

nated response –
NA,
PMS log –
no

3-223 03-DF TX 15 Termi- PRE-REG KEY # nnnn, LV yy AUTO CHECKED

nated PMS IN WAS NOT CHECKED OUT.
response –
NA,
PMS log –
no

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 67 of 73

3-224 03-E0 TX 1 Termi- PMS PRE-REG KEY # nnnn, LV yy WAS CHECKED

nated response – IN mm/dd/yy. MUST USE IT OR CHECK OUT
NA, FIRST.
PMS log –
no

3-224 03-E0 TX 3 Termi- PMS KEY # nnnn, LV yy IS DUE FOR OR CHECKED

nated response – OUT. PRE-REG KEY EXISTS. VERIFY KEY.
NA,
PMS log –
no

3-224 03-D0 TX 15 Termi- PMS PRE-REG KEY # nnnn, LV yy AUTO CHECKED

nated response – IN mm/dd/yy. NOT ALLOWED TO CHECK OUT.
NA,
PMS log –
no

3-224 03-D0 TX 18 Termi- PMS zzz PRE-REG KEYS # nnnn, LV yy AUTO

nated response – CHECKED IN mm/dd/yy. ISSUE OR MAKE NEW
NA, KEYS.
PMS log –
no

3-225 03-E1 TX 1 Termi- PMS OCCUPIED W/KEY # nnnn, LV yy CHECK-OUT

nated response – NOT DUE mm/dd/yy. MUST CHECK OUT
NA, FIRST.
PMS log –
no

3-225 03-E1 TX 3 Termi- PMS VERIFY GUEST KEY OR CHANGE CHECK-

nated response – OUT OF KEY # nnnn, LV yy.
NA,
PMS log –
no

3-225 03-E1 TX 14 Termi- PMS CHECKED OUT CHANGE HAS BEEN

nated response – IGNORED.
NA,
PMS log –
no

3-225 03-E1 TX 14 Termi- PMS PRE-REG KEY # nnnn, LV yy MANUALLY

nated response – CHECKED IN WAS NOT CHECKED OUT.
NA,
PMS log –
no

3-226 03-E2 TX 1 Termi- PMS OCCUPIED W/KEY # nnnn, LV yy CHECK-OUT

nated response – OVERDUE mm/dd/yy. MUST CHECK OUT
NA, FIRST.
PMS log –
yes

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 68 of 73

3-226 03-E2 TX 15 Termi- PMS PRE-REG KEY # nnnn, LV yy MANUALLY

nated response – CHECKED IN mm/dd/yy. NOT ALLOWED TO
NA, CHECK OUT.
PMS log –
no

3-226 03-E2 TX 18 Termi- PMS zzz PRE-REG KEYS # nnnn, LV yy CHECKED

nated response – IN mm/dd/yy. ISSUE OR MAKE NEW KEYS.
NA,
PMS log –
yes

3-227 03-E3 TX 1 Termi- PMS NEW KEYS WERE RECENTLY MADE

nated response – mm/dd/yy hh:mm SO A NEW SEQUENCE
NA, CANNOT BE MADE YET.
PMS log –
yes

3-228 03-E4 TX 1 Termi- PMS LAST KEY DATE mm/dd/yy hh:mm IS AHEAD
nated response – OF SYSTEM TIME. USE SAFLOK TO MAKE
NA, KEY.
PMS log –
no

3-228 03-E4 TX 3 Termi- PMS NEW KEY DATE mm/dd/yy hh:mm IS AHEAD
nated response – OF SYSTEM. REPROGRAM LOCK FIRST.
NA,
PMS log –
no

3-228 03-E4 TX 14 Termi- PMS CHECK-OUT CHANGE IGNORED. KEY

nated response – REMAINS CHECKED OUT AS OF mm/dd/yy
NA, hh:mm.
PMS log –
no

3-228 03-E4 TX 15 Termi- PMS LAST KEY DATE mm/dd/yy hh:mm IS AHEAD
nated response – OF SYSTEM TIME. USE SAFLOK TO MAKE
NA, KEY.
PMS log –
no

3-228 03-E4 TX 18 Termi- PMS PRE-REG NEW KEY DATE IS OLDER THAN
nated response – LAST KEY DATE mm/dd/yy hh:mm. USE
NA, SAFLOK.
PMS log –
no

3-229 03-E5 TX 3 Termi- PMS REPROGRAM LOCK THEN REPLACE KEYS

nated response – WITH NEW KEYS.
NA,
PMS log –
no

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 69 of 73

3-229 03-E5 TX 14 Termi- PMS CHECK-OUT CHANGE IGNORED. KEY

nated response – REMAINS CHECKED OUT AS OF mm/dd/yy
NA, hh:mm.
PMS log –
no

3-230 03-E6 TX 1 Termi- PMS PRE-REG KEY CHECKED IN EARLY. USE IT,
nated response – WAIT UNTIL mm/dd/yy hh:mm, OR USE
NA, SAFLOK.
PMS log –
no

3-230 03-E6 TX 3 Termi- PMS USE SAFLOK AND VERIFY GUEST'S KEY
nated response – BEFORE CONTINUING.
NA,
PMS log –
no

3-230 03-E6 TX 14 Termi- PMS CHECK-OUT CHANGE IGNORED. KEY

nated response – REMAINS CHECKED OUT AS OF mm/dd/yy
NA, hh:mm.
PMS log –
no

3-230 03-E6 TX 15 Termi- PMS PRE-REG KEY CHECKED IN EARLY. USE IT,
nated response – WAIT UNTIL mm/dd/yy hh:mm, OR USE
NA, SAFLOK.
PMS log –
no

3-230 03-E6 TX 18 Termi- PMS CANCEL PRE-REG KEYS # nnnn, LV yy AND

nated response – ISSUE GUEST NEW KEYS THAT WILL WORK
NA, NOW.
PMS log –
no

3-231 03-E7 TX 3 Termi- PMS USE SAFLOK AND VERIFY GUEST’S KEY
nated response – BEFORE CONTINUING.
NA,
PMS log –
no

3-xxx 03-zz Any TX Termi- PMS GRC 3, DRC zz, TXC ww ERROR – REQUEST
nated response – ABORTED.
NA,
PMS log –
yes

4-159 04-9F System Termi- PMS SAFLOK MAIN COMPUTER IS NOT POLLING
all nated response – ENI.
NA,
PMS log –
yes

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 70 of 73

4-160 04-A0 System Termi- PMS SAFLOK ENI OR MAIN COMPUTER IS NOT
all nated response – ONLINE.
NA,
PMS log –
yes

4-164 04-A4 System Termi- PMS SAFLOK KEY DATA FILES ARE CORRUPT.
all nated response – CONTACT SAFLOK.
NA,
PMS log –
yes

4-165 04-A5 System Termi- PMS SAFLOK MAIN COMPUTER STATION ERROR
all nated response – RESPONSE. NOTIFY SAFLOK.
NA,
PMS log –
no

4-166 04-A6 System Termi- PMS SAFLOK INTERFACE IS BUSY SIGNING ON.
all nated response – RETRY LATER.
NA,
PMS log –
yes

4-168 04-A8 System Termi- PMS SAFLOK INTERFACE IS BUSY CLEARING

all nated response – REQUESTS DUE TO UNLINK. RE-REQUEST IF
NA, DESIRED.
PMS log –
no

4-170 04-AA System Termi- PMS SAFLOK MAIN COMPUTER CALLED INVALID
all nated response – PROGRAM ROUTING. NOTIFY SAFLOK.
NA,
PMS log –
no

4-171 04-AB System Termi- PMS SAFLOK COMPUTER COULD NOT ACCEPT
all nated response – ANOTHER REQUEST. RE-REQUEST IF
NA, DESIRED.
PMS log –
yes

4-173 04-AD System Termi- PMS SAFLOK COMPUTER DRIVE ACCESS

all nated response – PROBLEM. NOTIFY SAFLOK.
NA,
PMS log –
no

4-175 04-AF System Termi- PMS SAFLOK SYSTEM CAUSED TIME OUT ON
all nated response – YOUR RE-REQUEST. RE-REQUEST IF
NA, DESIRED.
PMS log –
yes

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 71 of 73

4-176 04-B0 System Termi- PMS SAFLOK TX FILE DELETION PROBLEM.

all nated response – NOTIFY SAFLOK.
NA,
PMS log –
no

4-177 04-B1 System Termi- PMS SAFLOK TX FILE IS CORRUPT. NOTIFY

all nated response – SAFLOK.
NA,
PMS log –
no

4-180 04-B4 System Termi- PMS SAFLOK COMPUTER RAM SPACE PROBLEM.
all nated response – RE-REQUEST IF DESIRED.
NA,
PMS log –
no

4-181 04-B5 System Termi- PMS SAFLOK COMPUTER CLOCK HARDWARE

all nated response – PROBLEM. NOTIFY SAFLOK.
NA,
PMS log –
no

4-182 04-B6 System Termi- PMS SAFLOK CALCULATION OVERFLOW. NOTIFY

all nated response – SAFLOK.
NA,
PMS log –
no

4-183 04-B7 System Termi- PMS SAFLOK SYSTEM HAS READ BEYOND END
all nated response – OF FILE PROBLEM. CONTACT SAFLOK.
NA,
PMS log –
yes

4-184 04-B8 System Termi- PMS SAFLOK COMPUTER OUT OF DISK SPACE.
all nated response – NOTIFY SAFLOK.
NA,
PMS log –
no

4-185 04-B9 System Termi- PMS SAFLOK COMPUTER FILE WRITE ERROR.
all nated response – NOTIFY SAFLOK.
NA,
PMS log –
no

4-187 04-BB System Termi- PMS SAFLOK SYSTEM HAS A FILE NOT FOUND
all nated response – PROBLEM. CONTACT SAFLOK.
NA,
PMS log –
yes

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 72 of 73

4-188 04-BC System Termi- PMS SAFLOK CANNOT OPEN A FILE. NOTIFY
all nated response – SAFLOK.
NA,
PMS log –
no

4-xxx 04-zz Any TX Termi- PMS GRC 4, DRC zz, TXC ww ERROR – REQUEST
nated response – ABORTED.
NA,
PMS log –
yes

5-252 05-FC TX 14 Termi- PMS CHECK-OUT CHANGED. ALL KEYS # nnnn, LV

nated response – yy ARE EXPIRED. REPLACE ALL GUEST
NA, KEYS.
PMS log –
no

5-253 05-FD TX 14 Termi- PMS CHECK-OUT CHANGED. THIS KEY # nnnn, LV

nated response – yy IS EXPIRED. RE-MAKE DUPLICATE KEY.
NA,
PMS log –
no

5-254 05-FE TX 15 Termi- PMS KEYS ARE CHECKED OUT BUT WILL WORK
nated response – UNTIL mm/dd/yy hh:mm OR UNTIL INHIBITED.
NA,
PMS log –
no

5-254 05-FE TX 18 Termi- PMS REMAKE zzz PRE-REG KEYS # nnnn, LV yy AS

nated response – DUPLICATE KEYS FOR PROPER
NA, EXPIRATION.
PMS log –
yes

5-254 05-FE TX 14 Termi- PMS CHECK-OUT CHANGED. THIS KEY WILL

nated response – EXPIRE mm/dd/yy hh:mm. REPLACE WITH
NA, DUPLICATE IF NEEDED.
PMS log –
no

5-255 05-FF TX 14 Termi- PMS CHECK-OUT CHANGED. KEYS WILL

nated response – CONTINUE TO WORK.
NA,
PMS log –
no

5-255 05-FF TX 15 Termi- PMS KEYS ARE CHECKED OUT AND ARE
nated response – EXPIRED IN LOCKS.
NA,
PMS log –
no

© SAFLOK Proprietary and Confidential AS 10/04

SAFLOK System 6000™ PMS Interface Pg. 73 of 73

5-255 05-FF TX 18 Termi- PMS ISSUE zzz PRE-REG KEYS # nnnn, LV yy.
nated response – MAKE DUPLICATES IF MORE NEEDED.
NA,
PMS log –
yes

5-xxx 05-zz Any TX Termi- PMS GRC 5, DRC zz, TXC ww – REQUEST
nated response – COMPLETED.
NA,
PMS log –
yes

6-xxx 06-xx Encoder Termi- PMS FOR KEY # nnnn, LV yy INSERT KEY AT
request nated response – ENCODER # xx.
NA,
PMS log –
no

7-xxx 07-xx TX 128 Termi- PMS IF STATUS CODE IS 0: SAFLOK DOES NOT
nated response – HAVE YOUR REQUEST. RE-REQUEST OR
NA, EXIT. IF STATUS CODE IS > 0: SAFLOK IS
PMS log – STILL PROCESSING REQUEST.
no

8-xxx 08-xx TX 127 Termi- PMS NO DISPLAY – STANDARD SAFLOK

nated response – INFORMATION SUCCESSFULLY PROVIDED.
NA,
PMS log –
no

11-xxx 0B-xx TX 129, Termi- PMS NO DISPLAY – STATUS xxx OF KEY

130 nated response – INSERTION.
NA,
PMS log –
yes

12-xxx 0C-xx TX 131 Termi- PMS NO DISPLAY – SAFLOK PASS # STATUS AND
nated response – DESCRIPTION SUCCESSFULLY PROVIDED.
NA,
PMS log –
no

© SAFLOK Proprietary and Confidential AS 10/04