Ah Bms

LobbyVision
BMS Gateway
APPLICATION HANDBOOK
Version 3.02.00 November 2000

Ident. No. 206172
Copyright © 1996 Inventio Ltd CH-6052 Hergiswil Page 1 / 56

LobbyVision BMS Gateway Application Handbook
Table of Contents
INTRODUCTION.............................................................................................................................................. 3
GENERAL ........................................................................................................................................................... 3
COMPATIBILITY ................................................................................................................................................... 3
TERMS AND ABBREVIATIONS ................................................................................................................................ 3
REFERENCES ..................................................................................................................................................... 3
FUNCTIONAL DESCRIPTION......................................................................................................................... 4
INTRODUCTION ................................................................................................................................................... 4
BMS PROTOCOL ................................................................................................................................................ 5
BMS RS232 PROTOCOL IMPLEMENTATION ........................................................................................................... 7
BMS TCP PROTOCOL IMPLEMENTATION .............................................................................................................. 8
BMS MESSAGE DEFINITION ....................................................................................................................... 10
MESSAGE FIELD STRUCTURE ............................................................................................................................. 10
BMS CONTROL MESSAGES ............................................................................................................................... 11
Connection Request ................................................................................................................................... 11
Alive Check ................................................................................................................................................ 11
Disconnect ................................................................................................................................................. 11
Bad Message ............................................................................................................................................. 12
Not Allowed Message................................................................................................................................. 12
BMS STATUS MESSAGES .................................................................................................................................. 13
General Status ........................................................................................................................................... 13
Elevator Status........................................................................................................................................... 14
Escalator Status ......................................................................................................................................... 22
Free Input Status........................................................................................................................................ 23
BMS EVENT MESSAGES ................................................................................................................................... 24
General Events .......................................................................................................................................... 24
Elevator Events .......................................................................................................................................... 25
Escalator Events ........................................................................................................................................ 37
Free Input Events ....................................................................................................................................... 39
BMS COMMAND MESSAGES .............................................................................................................................. 40
General Commands ................................................................................................................................... 40
Elevator Commands ................................................................................................................................... 41
Escalator Commands ................................................................................................................................. 47
Free Input Commands................................................................................................................................ 48
CONFIGURATION ......................................................................................................................................... 49
BMS_GW.CFG HARDWARE CONFIGURATION FILE .............................................................................................. 49
BMS GATEWAY TRACE FACILITY........................................................................................................................ 50
„C“ HEADERFILE REFERENCES................................................................................................................. 51
FEATURE NAMES, ABBREVIATIONS AND TYPES AS DEFINED IN LICDEF.H................................................................. 51
Elevator group features .............................................................................................................................. 51
Elevator Features ....................................................................................................................................... 52
Escalator Features ..................................................................................................................................... 53
TCP/IP INSTALLATION AND CONFIGURATION ......................................................................................... 54
TCP/IP INSTALLATION AS PART OF THE OS/2 W ARP CONNECT INSTALLATION ........................................................ 54
CHANGING THE IP ADDRESS .............................................................................................................................. 56
Copyright © 1996 Inventio Ltd CH-6052 Hergiswil Page 2

Introduction
General
This document describes the design of the BMS Gateway Interface for LobbyVision. It shows the
functionality and the protocols.
The BMS Gateway is a piece of software on the LobbyVision computer, which controls the
appropriate HW communication channels (RS232 and / or Ethernet).
Connecting BMS systems to the BMS Gateway enables them to receive state and event information
from the installation through LobbyVision. Furthermore, BMS systems may send state change
requests to the installation through LobbyVision.
Additionally, the design of a special BMS system called BMS Lobby Client is described within this
document. The BMS Gateway together with this BMS Lobby Client allow multiple LobbyVisions to be
connected to one installation.
Compatibility
This document is valid for all LobbyVision with version greater than 4.03.00.
Terms and Abbreviations

BMS Building Management System
Client A BMS system (BMS subscriber), which is connected to the BMS Gateway.
IP Internet Protocol
Lobby Client A special client which allows multiple LobbyVisions to share installation information.
Server The BMS Gateway within LobbyVision
Socket The abstraction provided by the operating system that allows an application program
to access the TCP/IP protocols.
TCP Transmission Control Protocol
References
[1] TCP/IP Programmer’s Reference Manual of the OS/2 Operating System
[2] Internetworking With TCP/IP Volume I, by Douglas E. Comer, ISBN 0-13-216987-8

Functional Description
Introduction
To connect BMS systems and/or Lobby Clients to the BMS Gateway, RS232 or Ethernet transparent
channels are required. Multiple BMS systems may connect to the BMS Gateway through one
Ethernet channel at the same time. To connect BMS systems through RS232 to the BMS Gateway,
each connection requires it’s own RS232 channel.
Figure 1: Overview

BMS Protocol
The basic functionality of the BMS protocol does not depend on the underlying channels.
BMS Gateway (Server) responses to BMS System (Client) actions:
Client action Server response Comment

connect request Connect Startup procedure to establish a connection
confirmed
alive request alive response Connection verification
status get status response Installation status polling
request
event request Event The server sends a message each time the event
occurs
command no response LobbyVision executes the requested command
disconnect no response
Following are the state / event diagrams for the BMS-Gateway (server) and the BMS-System
(client).
Figure 2: State/Event Diagrams (Client time-outs >= 200ms)

The general structure of a BMS message consists of the following fields.
BMSMessageType DataLen Data
The BMS-MessageType field divides the BMS messages into the following types.
BMSMessageType Comment
BMS_CONTROL_MSG communication control messages
BMS_GET_MSG status get messages (client --> server)
BMS_RESPONSE_MSG status messages (server --> client)
BMS_REQUEST_MSG event request messages (client --> server)
BMS_EVENT_MSG event messages (server --> client)
BMS_COMMAND_MSG command messages (client --> server)
The DataLen field holds a value in the range 1..80, which specifies the number of bytes within the
Data field.
The Data field consists of 1 to 80 consecutive bytes of data as specified in DataLen. The structure
depends on the BMSMessageType. For details see chapter 4.

BMS RS232 Protocol Implementation

The general BMS message structure is extended as following:
BMSMessageType Not- DataLen not-DataLen Data DataChecksum

BMSMessageType
1 Byte 1 Byte 1 Byte 1 Byte 1..80 Bytes 1 Byte
The not-BMSMessageType field holds the 1’s complement of the BMSMessageType field.
The not-DataLen field holds the 1’s complement of the DataLen field.
The DataChecksum field holds the 2’s complement checksum of the Data Field.
Following are the state/event diagrams for the RS232 transmitter and receiver.
Figure 3: RS232 transmitter / receiver state/event diagram
Protocol restrictions:
• Software encoded line parameters (8 databits, 1 stopbit, nonparity).
• No data flow control support.
• Illegal messages will not be processed (unknown BMSMessageType, illegal DataLen, bad
DataChecksum).
They only are shown within the Rx trace window.

BMS TCP Protocol Implementation

The BMS TCP Protocol Implementation uses the general BMS message structure (described in
chapter 2.2.) since the underlying TCP layer is a reliable stream transport service.
Because TCP is a connection oriented protocol, such a connection must be established before the
BMS protocol drivers are able to transmit BMS messages. There are few differences between client
and server TCP protocol drivers, because the server must be ready to accept a connection at the
time the client requests to connect to the server.
The socket interface is used to access the TCP layer. A socket must be created for the PF_INET
domain and its type must be SOCK_STREAM. For more details about the socket interface see the
TCP/IP Programmer’s Reference manual of the OS/2 operating system [3].
Following are the state / event diagrams to handle a single TCP connection between the server
(BMS-Gateway) and a client (BMS-System).
Figure 4: TCP Single Connection state/event diagram
The networking part of the operating system must be installed and operational to get access to the
TCP/IP services. For details see chapter 8.

The BMS TCP Protocol transmitter and receiver itself are equal for the BMS Gateway and the BMS
Systems.
The following are the state/event diagrams for the TCP transmitter and receiver.
Figure 5: TCP transmitter / receiver state/event diagram
Protocol restrictions:
• No data flow control support.
• No OutOfBand message support.
• Illegal messages will not be processed (unknown BMSMessageType, illegal DataLen, bad
DataChecksum).
They only are shown within the Rx trace window.

BMS Message Definition

This section describes the BMS protocol messages. The layout is based on the general structure of
the BMS messages. To use a message within a specific BMS protocol, the corresponding protocol
modifications must be done.
A few messages specified within the next sections, are for internal use only. They must not be
placed into any customer documentation! These messages are marked with (internal use only) at
the end of their header.
Message field Structure

The type in the message field is following defined:
Message Field Data structure Example
ULONG Data[0] : high Byte ULONG : 11223344 Hex
Data[1] : | Data[0] : 11 Hex
Data[2] : | Data[1] : 22 Hex
Data[3] : low Byte Data[2] : 33 Hex
Data[3] : 44 Hex
String Data[0..x] : String String : BMS
Data[0] : B
Data[1] : M
Data[2] : S
Time_t Data[0] : high Byte ULONG ( time_t ) : 12345678 Hex
Seconds from date Data[1] : | Data[0] : 12 Hex
1.Jan. 1970 0:00 GMT Data[2] : | Data[1] : 34 Hex
Data[3] : 78 Hex
Bitset Data[0] : low Byte Bitset : 10010100 01110011
Data[1] : | - -
Data[2] : | LSB MSB
Data[3] : high Byte (least significant bit) (most significant bit)
Data[0] : 94 Hex
Data[1] : 73 Hex
Short Data[0] : high Byte Int : 0998 Hex
Data[1] : 98 Hex
Byte Data[0] : Byte byte : 01 Hex
Data[0] : 01 Hex

BMS Control Messages
Connection Request
This message is sent by a BMS system to connect to the BMS Gateway.
Message Field Content Description
BMSMessageType BMS_CONTROL_MSG Connection control message
BMSDataLen 2 + Data[1]
Data[0]:Byte BMS_CONNECT_REQUEST Connection request
Data[1]:Byte Strlen(Application name) Length of the Application name
Data[2]:String Application name Name of the BMS system application
This message is sent by the BMS Gateway to confirm a connect request.

BMSDataLen 1
Data[0]:Byte BMS_CONNECT_CONFIRMED Connection request
Alive Check
This message is sent by a BMS system to the BMS Gateway to request an alive answer.
BMSDataLen 1
Data[0]:Byte BMS_ALIVE_REQUEST Alive answer request
This message is sent by the BMS Gateway to respond to an alive request.

BMSDataLen 1
Data[0]:Byte BMS_ALIVE_CONFIRMED Alive answer
Disconnect
This message is sent by a BMS system to the BMS Gateway to close a connection.
BMSDataLen 1
Data[0]:Byte BMS_DISCONNECT Close connection

Bad Message
This message is sent by the BMS Gateway to respond to an illegal message.
Data[0]:Byte BMS_BAD_MSG Unknown or illegal message
Data[1]:Byte BMSMessageType Message type of illegal message
Data[2]:Byte BMSDataLen Length of illegal message
Data[3.(Data[2]+3)]:Byte Data Data of illegal message
Not Allowed Message

This message is sent by the BMS Gateway to respond to a not allowed message.
Data[0]:Byte BMS_NOT_ALLOWED Not allowed message
Data[1]:Byte BMSMessageType Message type of not allowed message
Data[2]:Byte BMSDataLen Length of not allowed message
Data[3.(Data[2]+3)]:Byte Data Data of not allowed message

BMS Status Messages
General Status
Login
This message is sent by a BMS system to the BMS Gateway to get the current logged in user
information.
BMSMessageType BMS_GET_MSG Status get message
BMSDataLen 2
Data[0]:Byte BMS_STA_MSG LobbyVision
Data[1]:Byte BMS_ICC_CURRENT_LOGIN Login Information of current user
This message is sent by the BMS Gateway to respond to the user login information get request.
BMSMessageType BMS_RESPONSE_MSG Status response message
Data[0]:Byte BMS_STA_MSG LobbyVision
Data[1]:Byte BMS_ICC_CURRENT_LOGIN Login Information
Data[2]:Byte Not used
Data[4..6]:Char UserShort Short name of the user (3 characters)
Data[7]:Byte Strlen(UserName) Length of the user full name
Data[8]:String UserName Full name of the user

Elevator Status
Elevator Group Summary Status

This message is sent by a BMS system to the BMS Gateway to get an elevator group summary
status.
BMSDataLen 3
Data[0]:Byte BMS_STA_MSG Elevator
Data[1]:Byte BMS_ELE_GROUP_SUMMARY Group summary status
Data[2]:Byte Group Id LobbyVision group Id Number
This message is sent by the BMS Gateway to respond to an elevator group summary status
request.
BMSDataLen 11
Data[1]:Byte BMS_ELE_GROUP_SUMMARY Group summary status
Data[2]:Byte Group Id LobbyVision group Id number
Data[4]:Bitset (32 bit) GroupStatusSet Group status Bitarray
Data[8]:Byte BlockOperationMode Group block operation mode
Data[9]:Byte NbrOfUnits Number of units within this group
Data[10]:Byte NbrOfNormalUnits Number of units in normal state

Elevator Summary Status

This message is sent by a BMS system to the BMS Gateway to get an elevator unit summary status.
BMSDataLen 4
Data[1]:Byte BMS_ELE_LIFT_SUMMARY Unit summary status
Data[3]:Byte Unit Id LobbyVision unit Id number
This message is sent by the BMS Gateway to respond to an elevator unit summary status request.
BMSDataLen 18 (19) Value 19 only for double decker
Data[1]:Byte BMS_ELE_LIFT_SUMMARY Unit summary status
Data[4..11]:Bitset UnitStatusSet Unit status Bitarray
(64 bit) (LICLiftStateType)
Data[12]:Byte CabinPosition 1 is the lowest floor of the group
Data[13]:Byte ExpressZonePosition value between 0..9.
0 means cabin is on floor
1..9 mean the percentage, which is
passed.
Data[14]:Byte LICDoorStateType Door state rear
Data[15]:Byte LICDoorStateType Door state front
Data[16]:Byte LICDirType Service direction (up, down, none)
Data[17]:Byte CabinLoad % of full load (more than 100%
( lower deck for DD ) possible)
Data[18]:Byte CabinLoad upper deck for DD only (not present otherwise).

Elevator Lock Mask

This message is sent by a BMS system to the BMS Gateway to get an elevator unit lock mask.
BMSDataLen 5
Data[1]:Byte BMS_ELE_LOCK_MASK Lock mask
Data[4]:Byte IMSLockCallType Type of locked call
This message is sent by the BMS Gateway to respond to an elevator unit lock mask request.
BMSDataLen 7 + ((Data[5] - 1) / 8)
Data[1]:Byte BMS_ELE_LOCK_MASK Lock mask
Data[4]:Byte IMSLockCallType Type of locked call
Data[5]:Byte NbrOfFloors Number of valid bits in the following
mask
Data[6]:Byte BitMask Lock mask for floor 8 <- 1
Data[7]:Byte BitMask Lock mask for floor 16 <- 9
Data[8]:Byte ... ...

Floor Call
This message is sent by a BMS system to the BMS Gateway to get a Floor Call information.
BMSDataLen 3
Data[0]:Byte IMS_ELE_MSG Elevator
Data[1]:Byte IMS_E_FLOOR_CALL Floor call
This message is sent by the BMS Gateway to respond to a Floor Call information request.
BMSDataLen 7
Data[2]:Byte Unit Id If !0, it indicates the riser number of
the call
Data[3]:Byte LICSideType Entry side
Data[4]:Byte LICDirType Direction
Data[5]:Byte FloorNumber 0 means each floor
Data[6]:Byte LICStateType On or off
Cabin Call
This message is sent by a BMS system to the BMS Gateway to get a Cabin Call information.
BMSDataLen 4
Data[1]:Byte IMS_E_CABIN_CALL Cabin call
Data[3]:Byte Unit Id LobbyVision unit Id Number
This message is sent by the BMS Gateway to respond to a Cabin Call information request.
BMSDataLen 7
Data[5]:Byte FloorNumber 0 means each floor of this lift

Allocated Floor Call

This message is sent by a BMS system to the BMS Gateway to get an Allocated Floor Call
information.
BMSDataLen 4
Data[1]:Byte IMS_E_ALLOC_FLOOR_CALL Allocated floor call
This message is sent by the BMS Gateway to respond to an Allocated Floor Call information
request.
BMSDataLen 8
Data[4]:Byte LICSideType Entry side of the allocated floor call
Data[5]:Byte LICDirType Direction of the allocated floor call
Data[6]:Byte FloorNumber 0: each floor
1: lowest floor of the group
Data[7]:Byte LICStateType On or off. For off, usually floor 0 is
used
Drive State
This message is sent by a BMS system to the BMS Gateway to get a Drive State information.
BMSDataLen 4
Data[1]:Byte IMS_E_DRIVE_STATE Drive state
This message is sent by the BMS Gateway to respond to a Drive State information request.
BMSDataLen 5
Data[4]:Byte LICDriveStateType Drive state

Drive Direction
This message is sent by a BMS system to the BMS Gateway to get a Drive Direction information.
BMSDataLen 4
Data[1]:Byte IMS_E_DRIVE_DIRECTION Drive direction
This message is sent by the BMS Gateway to respond to a Drive Direction information request.
BMSDataLen 5
Data[4]:Byte LICDirType Drive direction (up, down, none)
Cabin Position
This message is sent by a BMS system to the BMS Gateway to get a Cabin Position information.
BMSDataLen 4
Data[1]:Byte IMS_E_CABIN_POSITION Cabin position
This message is sent by the BMS Gateway to respond to a Cabin Position information request.
BMSDataLen 6
Data[4]:Byte Position 1 is the lowest floor of the group
passed.

Cabin Load
This message is sent by a BMS system to the BMS Gateway to get a Cabin Load information.
BMSDataLen 4
Data[1]:Byte IMS_E_CABIN_LOAD Cabin load
This message is sent by the BMS Gateway to respond to a Cabin Load information request.
BMSDataLen 5 (6)
Data[4]:Byte Load (lower deck for DD) % of full load (more than 100% is
possible).
Data[5]:Byte LoadUpperDeck For DD only (not present otherwise)
Door State
This message is sent by a BMS system to the BMS Gateway to get a Door State information.
BMSDataLen 4
Data[1]:Byte IMS_E_DOOR_STATE Door state
This message is sent by the BMS Gateway to respond to a Door State information request.
BMSDataLen 6
Data[5]:Byte LICDoorStateType Door state

Lock Trip
This message is sent by a BMS system to the BMS Gateway to get Lock Trip information (Miconic10
only).
BMSDataLen 4
Data[1]:Byte IMS_E_LOCK_TRIP Lock trip
This message is sent by the BMS Gateway to respond to a Lock Trip information request.
BMSDataLen 9
Data[4]:Byte FloorNumber From floor
Data[5]:Byte LICSideType From entry side
Data[6]:Byte FloorNumber To floor
Data[7]:Byte LICSideType To entry side
Data[8]:Byte LICStateType On/Off
Cumulated Trip Time

This message is sent by a BMS system to the BMS Gateway to get Cumulated Trip Time.
BMSDataLen 4
Data[1]:Byte IMS_E_CUM_TRIP_TIME Cumulated trip time
Data[2]:Byte GroupId LobbyVision GroupId Number
Data[3]:Byte UnitId LobbyVision UnitId Number
This message is sent by the BMS Gateway to respond to a Cumulated Trip Time information
request.
BMSDataLen 5
Data[5]: ULONG Cumulated trip time [sec] in seconds

Escalator Status
Escalator Summary Status

This message is sent by a BMS system to the BMS Gateway to get an escalator unit summary
status.
BMSDataLen 4
Data[0]:Byte BMS_STA_MSG Escalator
Data[1]:Byte BMS_ESC_SUMMARY Unit summary status
This message is sent by the BMS Gateway to respond to an escalator unit summary status request.
BMSDataLen 8
Data[0]:Byte BMS_STA_MSG Escalator
Data[1]:Byte BMS_ESC_SUMMARY Unit summary status
Data[4]:Word LICEscalatorStateType Unit status
Data[6]:Byte LICMotorStateType Motor status
Data[77]:Byte LICDirType Service direction
Motor State
This message is sent by a BMS system to the BMS Gateway to get an escalator motor status.
BMSDataLen 4
Data[0]:Byte IMS_ESC_MSG Escalator
Data[1]:Byte IMS_E_ESC_MOTOR Motor status
This message is sent by the BMS Gateway to respond to an escalator motor status request.
BMSDataLen 5

Free Input Status
Free Input State

This message is sent by a BMS system to the BMS Gateway to get a free input unit status.
BMSDataLen 4
Data[0]:Byte BMS_FINP_MSG Free input
Data[1]:Byte BMS_E_FINP_STATE Unit status
This message is sent by the BMS Gateway to respond to a free input unit status request.
BMSDataLen 5
Data[0]:Byte BMS_FINP_MSG Free input
Data[1]:Byte BMS_E_FINP_STATE Unit status
Data[4]:Byte LICFInpStateType Unit status

BMS Event Messages
General Events
Login
This message is sent by a BMS system to the BMS Gateway to request the user login events.
BMSMessageType BMS_REQUEST_MSG Event request message
BMSDataLen 2
Data[0]:Byte IMS_ICC_MSG LobbyVision
Data[1]:Byte IMS_LOGIN Login Information
This message is sent by the BMS Gateway on user login events.

BMSMessageType BMS_EVENT_MSG Event message
Data[1]:Byte IMS_LOGIN Login Information
Data[4]:Byte LICStateType On (Login) or Off (Logout)
Data[5]:Byte Strlen(userShort) Length of the user short name
Data[6..]:String UserShort Short name of the user

Elevator Events
Floor Call
This message is sent by a BMS system to the BMS Gateway to request Floor Call events.
BMSDataLen 3
This message is sent by the BMS Gateway on Floor Call events.

BMSDataLen 8
Data[3]:Byte Unit Id If !0, it indicates the riser number of the
call
Data[6]:Byte FloorNumber 0 means each floor
Cabin Call
This message is sent by a BMS system to the BMS Gateway to request Cabin Call events.
BMSDataLen 3
This message is sent by the BMS Gateway on Cabin Call events.

BMSDataLen 7
Data[5]:Byte FloorNumber 0 means each floor of this lift

Allocated Floor Call

This message is sent by a BMS system to the BMS Gateway to request Allocated Floor Call events.
BMSDataLen 3
This message is sent by the BMS Gateway on Allocated Floor Call events.
BMSDataLen 8
used
Lock Floor Call

This message is sent by a BMS system to the BMS Gateway to request Lock Floor Call events.
BMSDataLen 3
Data[1]:Byte IMS_E_LOCK_FLOOR_CALL Lock floor call
This message is sent by the BMS Gateway on Lock Floor Call events.
BMSDataLen 8
Data[1]:Byte IMS_E_LOCK_FLOOR_CALL Lock floor call
used

Lock Cabin Call

This message is sent by a BMS system to the BMS Gateway to request Lock Cabin Call events.
BMSDataLen 3
Data[1]:Byte IMS_E_LOCK_CABIN_CALL Lock cabin call
This message is sent by the BMS Gateway on Lock Cabin Call events.
BMSDataLen 7
Data[1]:Byte IMS_E_LOCK_CABIN_CALL Lock cabin call
Data[5]:Byte FloorNumber 0 means each floor on this lift
Data[6]:Byte LICStateType On or off. For off, usually floor 0 is used
Group Status
This message is sent by a BMS system to the BMS Gateway to request Group State events.
BMSDataLen 3
Data[1]:Byte IMS_E_GROUP_STATE Group status
This message is sent by the BMS Gateway on Group State events.

BMSDataLen 6 (7)
Data[1]:Byte IMS_E_GROUP_STATE Group state
Data[4]:Byte LICGroupStateType Group feature/service
Data[6]:Byte (BlockOperationMode) Group block operation mode. Only if
Data[4] is LIC_GS_BO.

Elevator Status
This message is sent by a BMS system to the BMS Gateway to request Elevator State events.
BMSDataLen 3
Data[1]:Byte IMS_E_LIFT_STATE Elevator status
This message is sent by the BMS Gateway on Elevator State events.

BMSDataLen 6
Data[1]:Byte IMS_E_LIFT_STATE Elevator state
Data[4]:Byte LICLiftStateType Car state that changed
Drive State
This message is sent by a BMS system to the BMS Gateway to request Drive State events.
BMSDataLen 3
This message is sent by the BMS Gateway on Drive State events.

BMSDataLen 5
Data[4]:Byte LICDriveStateType Drive state

Drive Direction
This message is sent by a BMS system to the BMS Gateway to request Drive Direction events.
BMSDataLen 3
This message is sent by the BMS Gateway on Drive Direction events.

BMSDataLen 5
Data[4]:Byte LICDirType Drive direction (up, down, none)
Cabin Position
This message is sent by a BMS system to the BMS Gateway to request Cabin Position events.
BMSDataLen 3
This message is sent by the BMS Gateway on Cabin Position events.

BMSDataLen 6
Data[4]:Byte Position 1 is the lowest floor of the group
passed.

Cabin Load
This message is sent by a BMS system to the BMS Gateway to request Cabin Load events.
BMSDataLen 3
This message is sent by the BMS Gateway on Cabin Load events.

BMSDataLen 5 (6)
Data[4]:Byte Load (lower deck for DD) % of full load (more than 100% is
possible).
Data[5]:Byte LoadUpperDeck For DD only (not present otherwise)
Door State
This message is sent by a BMS system to the BMS Gateway to request Door State events.
BMSDataLen 3
This message is sent by the BMS Gateway on Door State events.

BMSDataLen 6
Data[5]:Byte LICDoorStateType Door state

Final Timer
This message is sent by a BMS system to the BMS Gateway to request Final Timer events.
BMSDataLen 3
Data[1]:Byte IMS_E_DOOR_FINAL_TIMER Final timer
This message is sent by the BMS Gateway on Final timer events.

BMSDataLen 5
Data[1]:Byte IMS_E_DOOR_FINAL_TIMER Final timer
Bypassed Floors
This message is sent by a BMS system to the BMS Gateway to request Bypassed Floors events.
BMSDataLen 3
Data[1]:Byte IMS_E_BYPASSED_FLOORS Bypassed Floors
This message is sent by the BMS Gateway on Bypassed Floors events.

BMSDataLen 7
Data[1]:Byte IMS_E_BYPASSED_FLOORS Bypassed floors
Data[6]:Byte FloorNumber Floor

Passenger Allocation
This message is sent by a BMS system to the BMS Gateway to request Passenger Allocation event-
s
(Miconic 10 only).
BMSDataLen 3
Data[1]:Byte IMS_E_PAX_ALLOCATION Passenger allocation
This message is sent by the BMS Gateway on Passenger Allocation events (Miconic 10 only).
BMSDataLen 9
Data[1]:Byte IMS_E_PAX_ALLOCATION Passenger allocation
Data[4]:Byte FloorNumber Boarding floor
Data[5]:Byte LICSideType Boarding entry side
Data[6]:Byte FloorNumber Destination floor
Data[7]:Byte LICSideType Destination entry side
Data[8]:Byte HalfRound (1..5) Half round the request will be
served
Passenger Boarded
This message is sent by a BMS system to the BMS Gateway to request Passenger Boarded events
(Miconic 10 only).
BMSDataLen 3
Data[1]:Byte IMS_E_PAX_BOARDED Passenger boarded
This message is sent by the BMS Gateway on Passenger Boarded events (Miconic 10 only).
BMSDataLen 6
Data[1]:Byte IMS_E_PAX_BOARDED Passenger boarded

Next Half Round

This message is sent by a BMS system to the BMS Gateway to request Next Half Round events
(Miconic 10 only).
BMSDataLen 3
Data[1]:Byte IMS_E_NEXT_HALF_ROUND Next half round started
This message is sent by the BMS Gateway on Passenger Boarded events (Miconic 10 only).
BMSDataLen 4
Data[1]:Byte IMS_E_NEXT_HALF_ROUND Next half round started
Display Destination
This message is sent by a BMS system to the BMS Gateway to request Display Destination events
(Miconic 10 only).
BMSDataLen 3
Data[1]:Byte IMS_E_DISPLAY_EXIT Display exit sign
This message is sent by the BMS Gateway on Display Destination events (Miconic 10 only).
BMSDataLen 6
Data[1]:Byte IMS_E_DISPLAY_EXIT Display exit sign
Data[4]:Byte FloorNumber Floor (0 means all floors)

Lock Trip
This message is sent by a BMS system to the BMS Gateway to request Lock Trip events (Miconic
10 only).
BMSDataLen 3
This message is sent by the BMS Gateway on Lock Trip events (Miconic 10 only).
BMSDataLen 9
Virtual Terminal Text

This message is sent by a BMS system to the BMS Gateway to request Virtual Terminal Text events
(Miconic 10 only).
BMSDataLen 3
Data[1]:Byte IMS_E_TERMINAL_TEXT Text to display on the terminal
This message is sent by the BMS Gateway on Virtual Terminal Text events (Miconic 10 only).
BMSDataLen 4 + strlen(text)
Data[1]:Byte IMS_E_TERMINAL_TEXT Text to display on the terminal
Data[4..3+strlen(text)]: Text[0..strlen(text)-1] ASCII text to display
char

Statistic Record
This message is sent by a BMS system to the BMS Gateway to request Statistic Record events -
(Miconic 10 only).
BMSDataLen 3
Data[1]:Byte IMS_E_STATISTIC_RECORD Passenger statistic
This message is sent by the BMS Gateway on Statistic Record events (Miconic 10 only).
BMSDataLen 21
Data[1]:Byte IMS_E_STATISTIC_RECORD Passenger statistic
Data[4]:ULONG Time_t Allocation time
Data[9]:Byte LIC_SideType Boarding entry side
Data[10]:Byte Seconds Time for approach
Data[11]:ULONG Time_t Boarding time
Data[15]:Byte FloorNumber Exit floor
Data[16]:Byte LICSideType Exit entry side
Data[17]:ULONG Time_t Exit time
Cumulated Trip Time

This message is sent by a BMS system to the BMS Gateway to request Cumulated Trip Time
events.
BMSMessageType BMS_REQUEST_MSG Status get message
BMSDataLen 3
This message is sent by the BMS Gateway on Cumulated Trip Time events.
BMSDataLen 8
Data[4]: ULONG Cumulated trip time [sec] in seconds

Clear Passenger Allocation

Clear passenger allocations (for all half rounds) (Miconic 10 only).

BMSDataLen 8
Data[1]:Byte IMS_E_CLEAR_PAX Cumulated trip time
Data[6]:Byte FloorNumber Exit floor
Data[7]:Byte LICSideType Exit entry side
Wildcards for boarding and exit floors means:

Boarding floor Exit floor Meaning
X Y Clear passenger allocations from floor X to Y
X 0 Clear all passenger allocations from floor X
0 Don’t care Clear all passenger allocations

Escalator Events
Escalator State
This message is sent by a BMS system to the BMS Gateway to request escalator status events.
BMSDataLen 3
Data[1]:Byte IMS_E_ESC_STATE Escalator state
Data[2]:Byte group Id LobbyVision group Id number
This message is sent by the BMS Gateway on escalator status events.

BMSDataLen 10
Data[1]:Byte IMS_E_ESC_STATE Escalator state
Data[3]:Byte unit Id LobbyVision unit Id number
Data[4]:Byte LICEscalatorStateType Unit status
Data[5]:Byte LICErrorPlaceType none, top, middle, button, controller,
warning
Data[6]:Byte ASCII-Code Symbol of the digital display segment
1
Data[7]:Byte ASCII-Code Symbol of the digital display point 1
symbol
Data[8]:Byte ASCII-Code Symbol of the digital display segment
2
Data[9]:Byte ASCII-Code Symbol of the digital display point 2
symbol
Motor State
This message is sent by a BMS system to the BMS Gateway to request escalator motor status
events.
BMSDataLen 3
This message is sent by the BMS Gateway on escalator motor status events.
BMSDataLen 5


Direction
This message is sent by a BMS system to the BMS Gateway to request escalator direction status
events.
BMSDataLen 3
Data[1]:Byte IMS_E_ESC_DIR Direction
This message is sent by the BMS Gateway on escalator direction status events.
BMSDataLen 5
Data[1]:Byte IMS_E_ESC_DIR Direction
Command Request Acknowledge

This message is sent by a BMS system to the BMS Gateway to request Command Request
Acknowledge events.
BMSDataLen 3
Data[1]:Byte IMS_ESC_CMD_ACKNOWLEDGE Escalator state of request
This message is sent by the BMS Gateway on Command Request Acknowledge events.
BMSDataLen 5
Data[1]:Byte IMS_ESC_CMD_ACKNOWLEDGE Escalator state of request
Data[4]:Byte LICStateType Request state

Free Input Events
State Change
This message is sent by a BMS system to the BMS Gateway to request Free Input Status events.
BMSDataLen 3
Data[0]:Byte IMS_FINP_MSG Free input
Data[1]:Byte IMS_E_FINP_STATE Free input state change
This message is sent by the BMS Gateway on Free Input Status events.
BMSDataLen 5
Data[1]:Byte IMS_E_FINP_STATE Free input state
Data[4]:Byte LICFInputStateType Unit status
Data[5]:Byte LICErrorPlaceType none, top, middle, button, controller,
warning

BMS Command Messages
General Commands
Execute Hot Key

This message is sent by a BMS system to the BMS Gateway to request an Execute Hot Key
command.
BMSMessageType BMS_COMMAND_MSG Command message
BMSDataLen 5
Data[1]:Byte IMS_HOT_KEY Execute the hot key
Data[2]:Byte not used
Data[4]:Byte HotKeyCodeType The requested hot key

Elevator Commands
Floor Call
This message is sent by a BMS system to the BMS Gateway to request a Floor Call command.
BMSDataLen 8
Data[1]:Byte IMS_C_FLOOR_CALL Floor call
Data[6]:Byte FloorNumber 1 is the lowest floor of the group
Cabin Call
This message is sent by a BMS system to the BMS Gateway to request a Cabin Call command.
BMSDataLen 7
Data[1]:Byte IMS_C_CABIN_CALL Cabin call
Data[2]:Byte group Id LobbyVision group Id Number
Data[3]:Byte unit Id LobbyVision unit Id Number
Data[5]:Byte FloorNumber 1 is the lowest floor of the group
Lock Floor Call

This message is sent by a BMS system to the BMS Gateway to request a Lock Floor Call command.
BMSDataLen 8
Data[1]:Byte IMS_C_LOCK_FLOOR_CALL Lock floor call

Lock Cabin Call

This message is sent by a BMS system to the BMS Gateway to request a Lock Cabin Call
command.
BMSDataLen 7
Data[1]:Byte IMS_C_LOCK_CABIN_CALL Lock cabin call
Data[5]:Byte FloorNumber 0 means each floor on this lift
Group Status
This message is sent by a BMS system to the BMS Gateway to request a Group State change.
BMSDataLen 6 (7) [8] {10}
Data[1]:Byte IMS_C_GROUP_STATE Group state
Data[4]:Byte LICGroupStateType Group feature/service
Data[5]:Byte LICStateType Turn on or off
Data[6]: Byte (Block operation mode) [floor] Block operation mode or origin floor
Data[7]: Byte [LICSideType] Origin side
Data[8]: Byte {floor} Destination floor
Data[9]: Byte {LICSideType} Destination side
The group state GS_BO ‘Block operation’ has an additional parameter: the mode. Its value is
between 0 and 7.
The following group features must contain as data origin floor and origin side (àBMSDataLen = 8):
• GS_RES10 Reserve
The following group features must contain as data an origin floor, origin side, destination floor and
destination side (àBMSDataLen = 10):
• GS_VIPG10 VIPG Miconic 10

Elevator Status
This message is sent by a BMS system to the BMS Gateway to request an Elevator State change.
BMSDataLen 6 (8) [10]
Data[1]:Byte IMS_C_LIFT_STATE Elevator state
Data[4]:Byte LICLiftStateType Car feature / service
Data[6]: Byte (floor) Origin floor
Data[7]: Byte (LICSideType) Origin side
Data[8]: Byte [floor] Destination floor
Data[9]: Byte [LICSideType] Destination side
The following elevator features must contain as data origin floor and origin side (àBMSDataLen =
8):
• LS_ET1 Emergency Trip 1
• LS_VIP VIP Trip
• LS_CTL Car to Lobby Trip
• LS_IND_M10 Independent Service Miconic 10
• LS_CLEAN_M10 Cleaner Control Miconic 10
• LS_RES13 Reserve
The following group features must contain as data an origin floor, origin side, destination floor and
destination side (àBMSDataLen = 10):
• LS_ET1_M10 Emergency Trip 1 Miconic 10
• LS_VIP_M10 VIP Trip Miconic 10

Lock Mask (internal use only)

This message is sent by a BMS system to the BMS Gateway to execute a Lock Mask command.
BMSDataLen 7 + (nbrOfFloors - 1) / 8
Data[1]:Byte IMS_C_LOCK_MASK Apply a lock mask
Data[4]:Byte IMSLockCallType Lock mask for cabin calls ZS1 .. floor call
down ZS20
Data[5]:Byte NbrOfFloors Nbr of valid bits within the following mask
Data[6]:Byte Bit mask Represents the lock mask for floor
8ß1
Data[7]:Byte Bit mask 16ß 8
The lock mask (each bit within the bit mask represents one floor) is only valid for one type of call.
These types are (IMSLockCallType):
IMS_LOCK_CC_ZS1 = 1 Cabin call entry side 1
IMS_LOCK_CC_ZS20 Cabin call entry side 2
IMS_LOCK_FC_ZS1_UP Floor call up entry side 1
IMS_LOCK_FC_ZS1_DOWN Floor call down entry side 1
Lock Trip (internal use only)

This message is sent by a BMS system to the BMS Gateway to execute a Lock Trip command
(Miconic 10 only).
BMSDataLen 9
Data[1]:Byte IMS_C_LOCK_TRIP Command to lock a trip

Virtual Terminal Call (internal use only)

This message is sent by a BMS system to the BMS Gateway to execute a Virtual Terminal Call
command
(Miconic 10 only).
BMSDataLen 9
Data[1]:Byte IMS_C_TERMINAL_CALL Passenger request from the terminal
Data[4]:Byte FloorNumber Boarding floor (position of terminal)
Data[5]:Byte LICSideType Boarding entry side (position of terminal)
Data[6]:Byte FloorNumber Destination floor
Data[7]:Byte LICSideType Destination entry side
Data[8]:Byte LICStateType Yes/No (Handicapped call)
Virtual Terminal Code (internal use only)

This message is sent by a BMS system to the BMS Gateway to execute a Virtual Terminal Code
command
(Miconic 10 only).
BMSDataLen 7..10
Data[1]:Byte IMS_C_TERMINAL_CODE Passenger request from the terminal
Data[4]:Byte FloorNumber Boarding floor (position of terminal)
Data[5]:Byte LICSideType Boarding entry side (position of terminal)
Data[6]:char Code[0] Code 1st byte
Data[7]:char Code[1] Code 2nd byte
Data[8]:char Code[2] Code 3rd byte
…
The virtual terminal code can consist of 1..4 bytes!

Temporary Cabin Call Lock Mask

This message is sent by a BMS system to the BMS Gateway to execute a temporary lock mask.
BMSDataLen 7 + (nbrOfFloors - 1) / 8
Data[1]:Byte IMS_C_ TEMP_LOCK_MASK Apply a lock mask
Data[4]:Byte IMSLockCallType Lock mask for cabin calls ZS1 .. floor call
down ZS20
Data[5]:Byte NbrOfFloors Nbr of valid bits within the following mask
Data[6]:Byte Bit mask Represents the lock mask for floor
8ß1
Data[7]:Byte Bit mask 16 ß 8
The lock mask (each bit within the bit mask represents one floor) is only valid for one type of call.
These types are (IMSLockCallType):
IMS_LOCK_CC_ZS1 = 1 Cabin call entry side 1
IMS_LOCK_CC_ZS20 Cabin call entry side 2

Escalator Commands
Service Switching
This message is sent by a BMS system to the BMS Gateway to request a Command Request.
BMSDataLen 5
Data[1]:Byte IMS_ESC_CMD_REQUEST Escalator start / stop request
Data[4]:Byte LICRequestType Start or stop request
This message is sent by a BMS system to the BMS Gateway to request a Command.
BMSDataLen 5
Data[1]:Byte IMS_ESC_CMD Escalator command
Data[4]:Byte LICEscalatorCommandType Command

Free Input Commands
State Change
This message is sent by a BMS system to the BMS Gateway to request a Free Input Status change.
BMSDataLen 5
Data[1]:Byte IMS_C_FINP_STATE Free input state change command
Data[4]:Byte LICStateType New state: on or off

Configuration
BMS_GW.CFG Hardware configuration file

The BMS_GW.CFG file is a text file that holds the BMS Gateway channel configuration information.
The value entries within the BMS_GW.CFG file might be altered with any text editor program, which
creates plain ASCII text.
It uses following keywords:
Keyword Comment
tcpipServer.port Present only, if TCP/IP channels are used
tcpipServer.addr Present only, if TCP/IP channels are used
nodeX.subscriberAddr Specifies the IP address of client X
nodeY.comPortNbr Specifies the RS232 port to which the client Y is
connected
nodeY.comBaudrate Specifies the RS232 port baudrate
Note: X and Y are the number values of the corresponding nodes within the BMS_GW.INI profile,
where X is a BMS_ETHERNET_NODE and Y is a BMS_RS232_NODE.
Following is the example of a valid BMS_GW.CFG file with three nodes:
//
// BMS-Gateway Configuration File
// -------------------------------------------
// ETHERNET server :
tcpipServer.port 2000
tcpipServer.addr "136.238.3.48"
// Node1 (ETHERNET) :
node1.subscriberAddr "136.238.3.49"
// Node2 (ETHERNET) :
node2.subscriberAddr "136.238.3.50"
// Node3 (RS232) :
node3.comPortNbr 2
node3.comBaudrate 38400

BMS Gateway Trace Facility

The BMS Gateway contains a build in tracer facility. It provides
• A list of all participants and their state (connected / not connected)
• A message trace per participant. The message trace also includes error messages.
To view the message trace, select ‘View’ ‘Message Trace’ from the menu. The following list will be
presented:
Figure 6: BMS Gateway Message Trace Selection
Select the desired participant (node) and tracer (receive [Rx] or transmit [Tx]). Tracer list box(es) will
appear:
Figure 7: BMS Gateway with active trace list boxes

„C“ Headerfile References

Label identifiers such as BMS_REQUEST_MSG within this document represent integer numbers
which are defined within the following „C“ language header files:
• bmsdef.h for labels starting with BMS_
• imsdef.h for labels starting with IMS_
• licdef.h for labels starting with LIC
Feature names, abbreviations and types as defined in LICDEF.H
Elevator group features

Feature Abbr. Type
Interfloor Traffic TRMI LIC_GS_TRMI
Up Peak Traffic TRMU LIC_GS_TRMU
Down Peak Traffic TRMD LIC_GS_TRMD
Noon Peak Traffic TRMNP LIC_GS_TRMNP
Block Operation BO LIC_GS_BO
Normal Traffic TRMN LIC_GS_TRMN
Traffic Mode TRM LIC_GS_TRM
Group Switch Off OFF LIC_GS_OFF
Communication Problem COM LIC_GS_COM
AITP AITP LIC_GS_AITP
Status not available SNA LIC_GS_SNA
Miconic 10 M10 LIC_GS_M10
Terminal Fault TERM LIC_GS_TERMINAL
Lock Trip LTRIP LIC_GS_LT
Virtual Terminal VTERM LIC_GS_VTERM
Emergency Power Evacuation EPE LIC_GS_EPE
Emergency Power EP LIC_GS_EP
Emergency Power Evacuation Done EPED LIC_GS_EPED
Fire Emergency FIRE LIC_GS_FIRE
Alternative Fire AFIRE LIC_GS_AFIRE
VIPG Miconic 10 VIPG10 LIC_GS_VIPG10

Elevator Features
Feature Abbr. Type
Normal Operation N LIC_LS_N = 1
Switch Off OFF LIC_LS_OFF
Independent Service IND LIC_LS_IND
Priority Trip PT LIC_LS_PT
Attended Service ATT LIC_LS_ATT
Fire Emergency FIRE LIC_LS_FIRE
Fire Emergency Service FIFIT LIC_LS_FIFIT
Emergency Power EP LIC_LS_EP
Inspection Travel INS LIC_LS_INS
Overload LX LIC_LS_LX
Disable Door DD LIC_LS_DD
Emergency Power Evacuation EPE LIC_LS_EPE
Status not available SNA LIC_LS_SNA
Bed Trip BED LIC_LS_BED
Error ERR LIC_LS_ERR
Test Travel TT LIC_LS_TT
Banker's Trip BAT LIC_LS_BAT
Button Emergency Trip ET LIC_LS_ET
Restricted Service RES LIC_LS_RES
Guest Control GUEST LIC_LS_GUEST
Cleaner Control CLEAN LIC_LS_CLEAN
Strong Wind WIND LIC_LS_WIND
VIP Trip VIP LIC_LS_VIP
Thermo Contact Driver HEAT LIC_LS_HEAT
Servitel Out of Order SOO LIC_LS_SOO
Hospital Emergency Trip HET LIC_LS_HET
Earthquake QUAKE LIC_LS_QUAKE
Car To Lobby CTL LIC_LS_CTL
Code Blue BLUE LIC_LS_BLUE
Bypass BY LIC_LS_BY
Next Car Operation NEXT LIC_LS_NEXT
Stop Button pressed STOP LIC_LS_STOP
Alarm Button pressed ALARM LIC_LS_ALARM
Communication Problem COM LIC_LS_COM
Cabin Call CC LIC_LS_CC
Floor Call FC LIC_LS_FC
Lock Cabin Call LCC LIC_LS_LCC
Lock Floor Call LFC LIC_LS_LFC
Security Service SEC LIC_LS_SEC
Independent Service Miconic 10 IND_M10 LIC_LS_IND_M10
Cleaner Control Miconic 10 CLEAN_M1 0 LIC_LS_CLEAN_M10
Indicator Fault INF LIC_LS_POST
COP Fault COP LIC_LS_INF
Post Distribution POST LIC_LS_COP

Emerg. Power Evacuation Done EPED LIC_LS_EPED

Emerg. Power Evacuation Failed EPEF LIC_LS_EPEF
Emergency Power Operation EPO LIC_LS_EPO
Alternative Fire AFIRE LIC_LS_AFIRE
Alternative Fire Fighter AFIFI LIC_LS_AFIFI
Emergency Trip 1 Miconic 10 ET1_M10 LIC_LS_ET1_M10
VIP Trip Miconic 10 VIP_M10 LIC_LS_VIP_M10
Escalator Features
Feature Abbr. Type
Automatic Operation AUTO LIC_ES_AUTO
Continuos Operation CONT LIC_ES_CONT
Switched Off OFF LIC_ES_OFF
Emergency Stop STOP LIC_ES_STOP
Operator Interaction Needed OIN LIC_ES_OIN
Inspection INS LIC_ES_INS
Error ERR LIC_ES_ERR
Status not available SNA LIC_ES_SNA

TCP/IP Installation and Configuration

It is recommended to install networking support for the OS/2 operating system, if the BMS
applications are configured to handle TCP/IP nodes.
This section might be ignored, if the BMS applications use RS232 channels only.
TCP/IP Installation as part of the OS/2 Warp Connect Installation

Contact your network administrator for correct setup values, if you plan to connect this workstation
to an existing network. Otherwise, follow the steps below to perform a minimum installation for
networking support.
Within the installation utility for the OS/2 operating system select „Yes“ when asked to install
networking support. Confirm this selection with push-button „OK“:
Figure 8: Enable networking support installation
Check IBM TCP/IP for Warp within the following page and confirm it with „OK“:
Figure 9: Networking product selection for Warp.

The IP address is the only required entry within the IBM TCP/IP setup pages. This address is
requested to be unique for the whole network your workstation will be connected to.
Figure 10: IBM TCP/IP for Warp setup page 1/2
No entries are required on the next page.
Figure 11: IBM TCP/IP for Warp setup page 2/2

Press push-button „Install“ to start the installation after you have completed your selections.

Changing the IP Address

Follow the steps below to change the IP address:
• Open the OS/2 system folder.
• Open the TCP/IP folder.
• Open the TCP/IP configuration notebook.
• Change the IP address on the first page of the configuration notebook.
• Close the notebook and select save when asked, to save your changes.
• Reboot the workstation to activate the changes.

Ah Bms

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Ah Bms

Enviado por

Direitos autorais:

Formatos disponíveis

LobbyVision

Version 3.02.00 November 2000

Copyright © 1996 Inventio Ltd CH-6052 Hergiswil Page 1 / 56

Copyright © 1996 Inventio Ltd CH-6052 Hergiswil Page 2

Terms and Abbreviations

Copyright © 1996 Inventio Ltd CH-6052 Hergiswil Page 3

Copyright © 1996 Inventio Ltd CH-6052 Hergiswil Page 4

Client action Server response Comment

Figure 2: State/Event Diagrams (Client time-outs >= 200ms)

Copyright © 1996 Inventio Ltd CH-6052 Hergiswil Page 5

The general structure of a BMS message consists of the following fields.

BMSMessageType DataLen Data

Copyright © 1996 Inventio Ltd CH-6052 Hergiswil Page 6

BMS RS232 Protocol Implementation

BMSMessageType Not- DataLen not-DataLen Data DataChecksum

Figure 3: RS232 transmitter / receiver state/event diagram

Copyright © 1996 Inventio Ltd CH-6052 Hergiswil Page 7

BMS TCP Protocol Implementation

Figure 4: TCP Single Connection state/event diagram

Copyright © 1996 Inventio Ltd CH-6052 Hergiswil Page 8

Figure 5: TCP transmitter / receiver state/event diagram

Copyright © 1996 Inventio Ltd CH-6052 Hergiswil Page 9

BMS Message Definition

Message field Structure

Copyright © 1996 Inventio Ltd CH-6052 Hergiswil Page 10

BMS Control Messages

This message is sent by the BMS Gateway to confirm a connect request.

This message is sent by the BMS Gateway to respond to an alive request.

Copyright © 1996 Inventio Ltd CH-6052 Hergiswil Page 11

Not Allowed Message

Copyright © 1996 Inventio Ltd CH-6052 Hergiswil Page 12

BMS Status Messages

Copyright © 1996 Inventio Ltd CH-6052 Hergiswil Page 13

Elevator Group Summary Status

Copyright © 1996 Inventio Ltd CH-6052 Hergiswil Page 14

Elevator Summary Status

Copyright © 1996 Inventio Ltd CH-6052 Hergiswil Page 15

Elevator Lock Mask

Copyright © 1996 Inventio Ltd CH-6052 Hergiswil Page 16

Copyright © 1996 Inventio Ltd CH-6052 Hergiswil Page 17

Allocated Floor Call

Copyright © 1996 Inventio Ltd CH-6052 Hergiswil Page 18

Copyright © 1996 Inventio Ltd CH-6052 Hergiswil Page 19

Copyright © 1996 Inventio Ltd CH-6052 Hergiswil Page 20

Cumulated Trip Time

Copyright © 1996 Inventio Ltd CH-6052 Hergiswil Page 21

Escalator Summary Status

Copyright © 1996 Inventio Ltd CH-6052 Hergiswil Page 22

Free Input Status

Free Input State

Copyright © 1996 Inventio Ltd CH-6052 Hergiswil Page 23

BMS Event Messages

This message is sent by the BMS Gateway on user login events.

Copyright © 1996 Inventio Ltd CH-6052 Hergiswil Page 24

This message is sent by the BMS Gateway on Floor Call events.

This message is sent by the BMS Gateway on Cabin Call events.

Copyright © 1996 Inventio Ltd CH-6052 Hergiswil Page 25

Allocated Floor Call

Lock Floor Call

Copyright © 1996 Inventio Ltd CH-6052 Hergiswil Page 26

Lock Cabin Call

This message is sent by the BMS Gateway on Group State events.