...

Installation

The driver is implement as a plugin. Therefore, it has to be installed via the Extension Manager. To do so, stop the server, and start the Extension Manager within the menu "Extensions" within the Core Studio. Select the "Protel" interface and press install as shown in the following screenshot:

Image Removed

After having installed the interface, restart the server.

Integration steps

To start, open the BMS Studio. First, configure the IP address and port number that you have enter within the web service URL.This can be done by selecting "Driver Configuration" within the menu "Modules" -> "Protel". If this information is not known, please ask the Protel integrator.

...

After having defined all rooms, the NETx Server has to be restarted. Afterwards, the configured devices are shown within the item tree. For the NETx BMS Platform and NETx Multi Protocol Server, you You will find the items under the sub tree "NETx\XIO\Protel". For the NETx BMS Server 2.0, you will find them under "NETx\API\NXA_PROTEL".Image Removed 

Image Added

The retrieved information from Protel is stored as Server Items. Here all available Server Items that are available for each room are listed (including their access rights):

• BuildingNumber
  • String, read only
  • Specified within Room Definitions within NETx Server
• LevelNumber
  • String, read only
  • Specified within Room Definitions within NETx Server
• RoomNumber
  • String, read only
  • Specified within Room Definitions within NETx Server. Must be identically with the room number used within Protel
• Description
  • String, read only
  • Specified within Room Definitions within NETx Server
• GuestsCount
  • UINT8, read only
  • Amount of guest that are checked in for this room
• GuestName
  • String, read only
  • Guest name that is received from Protel
• GuestLanguage
  • String, read only
  • Language code that is received from Protel . E.g. de, en, es, ...
• GuestVIP
  • UINT8, read only
  • VIP status that is received from Protel
• GuestId
  • String, read only
  • Reserveration / guest ID
• RoomCheckedForecast (only available if enabled in "Driver configuration...")
  • Boolean, read only
  • True if there is a forecast check in for this room – False if room not
• RoomChecked
  • Boolean, read only
  • True if at least 1 guest is check in this room – False if room is free
• ClassOfService (read only)
  • UINT8, read only
  • Received from Protel . 0 (Barred/hotel internal only), 1 (local), 2 (national), 3 (no restrictions)
• DoNotDisturb 
  • Boolean, read only
  • True if DND is received from Protel  – False otherwise
• RoomStatus
  • UINT8, read and writable
  • See table below
• ClearText
  • String, read and writable
• GuestArrivalDate
  • DateTime, read only
  • Arrival data and time of guest. Normally this is equal to the checkin data and time. Please keep in mind that Protel is not providing an arrival date before the checkin signal
• GuestDepartureDate
  • DateTime, read only
  • Scheduled depature data and time of guest.
• PrinterPort
  • UINT8, read only
• MessageCount
  • UINT8, read only
  • Amount of messages that are available for this room
• NextMessage
  • Boolean, write only
  • If set to true, the next message that is queued within the server is shown within the server item "MessageText"
• MessageText
  • String, read only
  • Last message that was received from Protel
• GetMessage 
  • Boolean, write only
  • If set to true, all available messages are fetched from Protel and stored within the server. Using the item "NextMessage", these messages can be shown within the item "MessageText"
• SendMessage 
  • String, read and writable
  • Used to send a message to Protel for this room
• MessageLightStatus
  • Boolean, write only

...

A typical use case would be the mapping of the RoomCheck item from Protel to a data point like the set point or the mode of the room's climate control. For implementing this use case, a predefined XLogic command called "HotelCheckInCheckOut" is already included within the server. Open the XCommand Event Definitions (BMS Studio --> Extensions) and add a new definition line. Give the logic a name (e.g. Room101), select "ON_VALUE_INPUTCHANGE" as type and select the XLogic "HotelCheckInCheckOutHotel.CheckInCheckOut". Within the configuration dialog, select the input item (e.g. NETx\APIXIO\NXA_FIDELIOProtel\PartA\Floor1\101\RoomChecked) and as output the data point that shall be controlled by the checkin/checkout signal (e.g. KNX group address of the set point of the room). The following screenshot shows an example:

Image RemovedImage Added

Repeat these steps for a hotel rooms. After having finished all definitions, restart the server.

...