Otis Elevator Company Pty. Ltd.

Specification

For

E.M.S. - Security/B.M.S. Protocol

OTIS REF NO.: 51646B

 Document No. 51646B

An interface is to be installed between the Otis Elevator Management System and the
Building Services control computer or security control computer.

The interface comprises standard data transferred techniques to convey commands and
status information relevant to operations of the building vertical transport system. It
incorporates provision for controlling access to given floor levels.

The Building Service control computer, or Building Management Systems (B.M.S.),

shall arbitrate the communication link.

Electrical Interface:
The electrical interface is according to RS422 standard with no shielding or grounding.

The interface consists of a Master/Slave communications protocol in which all traffic is

controlled from the security controller. A watch-dog timeout at both ends of the link
shall allow for detection of failure of either unit. Checksum error detection shall be used
for data integrity.

Protocol:
The protocol used is an asynchronous 8 bit binary with 1 stop bit and odd parity
operating at 9600 Baud, i.e. each byte consists of 11 bits.

1 start bit
8 data bits
1 parity bit
1 stop bit

With data bits transmitted least significant to most significant.

Note: Data bits within this document are numbered zero to seven, least significant to
most significant. This means that 2 to the power of the bit number corresponds to its
binary value. Hence each byte appears:

: 7 : 6 : 5 : 4 : 3 :2 : 1 : 0 :

Data Link:
The data link shall comprise a Master/Slave Full Duplex interchange of data. The
B.M.S. system shall send a Command Frame to the E.M.S. which will act upon the data
provided. The E.M.S. shall then send a Response Frame back to the B.M.S. system.

The Response Frame shall be completely transmitted within 100ms of the end of the
Command Frame. Failure to respond will result in a retry of the Command Frame.

On completion of the response frame from the E.M.S., the B.M.S. is then permitted to
send another command frame. Upon failure of any Command Frames from the B.M.S.
for a period of 1 minute, the E.M.S. shall time out and set the security mask for
complete access for all elevators and all floors.

Each frame shall consist of a sequence of bytes followed by a 1 byte checksum error
detection scheme.

Page 1
 Document No. 51646B

Command Frame:
The Command Frame (packet/telegram etc.) transfers data from the B.M.S. to the
E.M.S. The E.M.S. executes control, in turn, over up to eight groups of up to 8 elevator
cars. The Response Frame shall be transmitted by the E.M.S. to the B.M.S. after every
Command Frame. Two forms of the Command shall be used. The first comprises of a
null poll and is 1 byte in length. This is used to get the Group status only. The second
comprises a Set Security command which is multiple bytes in length. This allows for
changing of the security masks for individual elevators.

The first byte of a Command Frame consists of a Group Address and a bit indicating
whether the security status is included in the command.

Null Poll:

The Null Poll shall consist of a single byte made up from the following:

bits
4-7 = Group Address (1-8)
3 = Permanent “0”
2 = Permanent “0”
1 = Permanent “0”
0 = Permanent “1”

The null poll is followed by a 1 byte checksum making a total of 2 bytes.

*Note: The maximum transmission rate of null polls to the E.M.S. should not exceed
two per second.

Set Security Poll:

The Set Security Poll is only sent when a change of security status on a particular
elevator is required. The poll consists of a sequence of bytes of data.

Byte 1

bits
4-7 = Group Address (1-8)
3 = Security Type (0=car, 1=hall)
2 = Don't Care
1 = Card Reader
0 = Zero

* Note: Card Reader - This bit = 1., indicates that this mask is in response to a card
reader. Any other security changes should not be included in the same poll.

Byte 2

4-7 = Elevator Car Number (1 to 8)

3 = * Express Priority Service
2 = * Hospital (1) /VIP services (0)
1 = Send Specific Elevator (bits 4-7 of this byte)
0 = Independent Service

Page 2
 Document No. 51646B

The Express Priority Service bit shall indicate to the Group that said service is to be
implemented according to bits 1 and 2.

· Bit 1 indicates that the particular elevator specified by bits 4 to 7 is to be sent to the
floor in byte 3. If this bit is zero then the Group may select the first available
elevator.
· Bit 2 indicates whether Hospital (bit 2 = 1) or VIP (bit 2 = 0) style service is
implemented.

The Independent Service bit places the elevator specified by bits 4 to 7 into Independent
Service.

* Note : These features may only be implemented if they are contract resident in the
elevator controller software.

Byte 3

The whole byte shall determine landing to send an elevator (or the specific elevator) in
case of an Express Priority Service request. This byte is normally zero, otherwise it is 1
to the maximum landing number.

Byte 4 and Up

These bytes shall form the security mask for the elevator specified in byte 2 bits 4-7.
The mask shall have 1 bit per level. A one shall indicate a secured floor and a zero shall
indicate free access to the floor. The lowest level served shall appear in MS bit of byte 4
and the highest level served shall appear in the last byte. The number of bits transmitted
(in whole bytes) shall be the number of landings possible by the worst case elevator (or
elevators) for the building.

Thus, if a Building has 25 landings and the “Low Rise” elevators serve the first 14
landings, then 4 bytes shall be sent as follows:

Byte 4

MS LS
Bits 7 6 5 4 3 2 1 0
Value 1 1 1 1 1 1 1 1
Landing 1 2 3 4 5 6 7 8

Byte 5

MS LS
Bits 7 6 5 4 3 2 1 0
Value 1 0 1 1 1 1 0 0
Landing 9 10 11 12 13 14 * *

Byte 6

MS LS
Bits 7 6 5 4 3 2 1 0
Value 0 0 0 0 0 0 0 0
Landing * * * * * * * *

Page 3
 Document No. 51646B

Byte 7

MS LS
Bits 7 6 5 4 3 2 1 0
Value 0 0 0 0 0 0 0 0
Landing * * * * * * * *
* Don't care

This would secure all landings except landing 10 from normal access.

If the “High Rise” elevators serve the 1st and 14th to 25th landings, then 4 bytes shall be
sent as follows:

Byte 4

MS LS
Bits 7 6 5 4 3 2 1 0
Value 1 1 1 1 1 1 1 1
Landing 1 14 15 16 17 18 19 20

Byte 5

MS LS
Bits 7 6 5 4 3 2 1 0
Value 1 0 1 1 1 1 0 0
Landing 21 22 23 24 25 * * *

Byte 6

MS LS
Bits 7 6 5 4 3 2 1 0
Value 0 0 0 0 0 0 0 0
Landing * * * * * * * *

Byte 7

MS LS
Bits 7 6 5 4 3 2 1 0
Value 0 0 0 0 0 0 0 0
Landing * * * * * * * *
* Don't care

This would secure all landings except landing 22 from normal access.

Page 4
 Document No. 51646B

If the “Goods” elevator serves all 25 landings then 4 bytes shall be sent as follows:

Byte 4

MS LS
Bits 7 6 5 4 3 2 1 0
Value 1 1 1 1 1 1 1 1
Landing 1 2 3 4 5 6 7 8

Byte 5

MS LS
Bits 7 6 5 4 3 2 1 0
Value 1 0 1 1 1 1 1 0
Landing 9 10 11 12 13 14 15 16

Byte 6

MS LS
Bits 7 6 5 4 3 2 1 0
Value 1 1 1 1 1 1 1 1
Landing 17 18 19 20 21 22 23 24

Byte 7

MS LS
Bits 7 6 5 4 3 2 1 0
Value 1 0 0 0 0 0 0 0
Landing 25 * * * * * * *
* Don't care

This would secure all landings except landings 10 and 16 from normal access.

The correspondence of the landings provided by the elevator and the actual floors is
defined by the Group programming and shall be provided by the elevator contractor.

After the security mask data shall follow the 1 byte checksum for the frame.

Page 5
 Document No. 51646B

Response Frame:
The Response Frame shall be transmitted to the B.M.S. after every Command Frame.
The frame shall consist of 20 bytes plus the checksum byte.

Byte 1

This byte contains general status for the elevator Group.

bits

4-7 = Group Address (1 to 8)

3 = Spare
2 = Error (0 = Normal, 1 = Command Frame not Understood)
1 = Watch-Dog timer (0 = Normal, 1 = Had timed out)
0 = Checksum error on Command Frame
(0 = ACK, 1 = NAK)

Bit 0 indicates a communications fault and bit 2 indicates all other errors except
communications errors. Bit 1 is set on the first Response Frame after the Group had
timed out. Successive Response Frames should have this bit reset. The elevator group
time out will occur if communications is lost between the E.M.S. P.C. and the elevator.

Bytes 2 To 17

These bytes consist of 8 entries of 2 bytes for each elevator car controlled in the Group.
The first byte consists of a mask of status bits for the elevator car. The second byte shall
provide the current landing number for the elevator.

byte 2 is elevator 1 status

byte 3 is elevator 1 landing
byte 4 is elevator 2 status
byte 5 is elevator 2 landing
byte 6 is elevator 3 status
byte 7 is elevator 3 landing
byte 8 is elevator 4 status
byte 9 is elevator 4 landing
byte 10 is elevator 5 status
byte 11 is elevator 5 landing
byte 12 is elevator 6 status
byte 13 is elevator 6 landing
byte 14 is elevator 7 status
byte 15 is elevator 7 landing
byte16 is elevator 8 status
byte 17 is elevator 8 landing

The status bits for each elevator shall be:

7 = emergency power operation
6 = spare
5 = door fully closed
4 = fire service
3 = elevator failed to start
2 = emergency stop
1 = independent service
0 = elevator alarm

Bytes 18 - 20:

Page 6
 Document No. 51646B

These bytes will respond with the information regarding car calls which have been
desecured by the card reader.

Due to response delays, this data will not relate directly to the current poll. Should more
than one car call, produced by card key validation be present, this data will be buffered
and will be transmitted on successive polls.

Binary value

Byte 18 = car number

Byte 19 = call number
Byte 20 = group ID
After the car call data follows the 1 byte checksum.

Checksum Error Detection:

The checksum byte will be the addition of the relevant frame bytes with the carry bit
discarded.

Example:

Byte 1 = 10101110
Byte 2 = 01110010
Byte 3 = 11110010
Checksum byte = 00010010

Page 7