RTI

From OpenMotics
Jump to: navigation, search

Introduction

RTI is a company that makes in-wall screens, remote controls and other specialized equipment to control home and building automation. For more details, please see http://www.rticorp.com

Since we got multiple questions regarding the possibility to have a 2-way driver for RTI, we've created one and it's freely available. We also provide the source code for the RTI driver.

RTI material is pretty expensive but very high quality and the software (Integration Designer) is very easy to use for someone that is a little technical. Integration Designer is only available for integrator's but we've multiple end-users that got the software from the re-seller/integrator where they bought the material.

The goal of RTI is to have a fully integrated solution so a remote control, an in-wall screen, an ipad has full control over hifi, lights, cooling, heating, camera's etc and this with an interface that can be fully customized by using the RTI Integration Designer software.

RTI.jpg

RTI components

An RTI installation consist of a few components:

  • RTI control processor: This is the central process unit that will retrieve information from the different devices like the Openmotics gateway, Hifi receivers, Television, Remote controls, in-wall screens, Philips Hue lights and be able to give commands. Different models exist and the difference between the models depends on the number of ports (RS232, dry contacts, relay contacts etc). The Openmotics Gateway is connected to the RTI control processor by using RS232. Please always use an XP processor since the 2-way driver for Openmotics has been written for the XP processors. Also, most of the third party drivers have been written for the XP series.
  • Remote control (optional): Different models of RTI remote controls exist (some without LCD, other with color LCD etc) and can be programmed by using the Integration Designer software. Please use RTI remote controls with Zigbee since those have better reaction time from sleep to active state in other words, when you press a button, the action will be immediate (with wifi remote controls, the connection must established which takes sometime more then a second).
  • Zigbee: The XP-3 control processor has a built-in zigbee transceiver, the XP-6 and XP-8 both needs a separate Zigbee transceiver (ZM-24). The XP-3 offers good value for money. My experience with the RTI zigbee is that the range is very good and far better then Wifi (I've 3 wifi bridges in my house and only 1 Zigbee transceiver).
  • In-wall screen (optional): RTI has different type of screens that can be incorporated in any wall in your house. The screens that integrate in your house are connected (by 1 POE connection per screen) to a POE switch. You can easily connect multiple screens and let be controlled by a single processor.
  • POE switch (optional): When you use in-wall screens, a POE switch is needed.

RTI communication principle

Many people have used the Philips pronto system. Openmotics has also written a driver for the Philips pronto system a few years ago. The Philips Pronto system had a huge disadvantage compared to the RTI system: The remote controls acted as master in other words, when information was needed from the receiver for example, each remote control individually would request the same information. When multiple remotes were used at the same time, this often resulted in communication conflicts, or even equipment stop functioning.

RTI has taken a different approach: Only 1 master exist which is the Control processor. Only the Control processor will communicate with the different components in your system avoiding any conflicts. The control processor will have the different drivers of the equipment connected and retrieve the necessary information and execute the different commands. The remote controls, in-wall screens etc will communicate with the Control Processor (and not with the equipment itself).

All your different equipment will be connected by using ethernet or RS232.

Openmotics driver Version 1.0

This version provides all functionality to have bidirectional control of following functions of the Openmotics home/building automation system:

  1. Switch On/Off lights
  2. Dim lights
  3. Switch On/Off outputs
  4. Read temperature sensor data
  5. Read thermostat setpoint
  6. Set thermostat setpoint
  7. Read thermostat mode (Manual, automatic, Party, vacation and away mode)
  8. Set thermostat mode
  9. Execute Basic Actions
  10. Events

We're working on version 1.1 which will also integrate the power/voltage/current information when using the Openmotics power modules.

Downloads

All the RTI driver code can be found on Github. If you only want to use the 2-way driver in RTI integration designer software, just download "Openmotics serial.rtidriver". All the other files you can find in this directory are needed when you want to change the driver or write your own driver.

The below download will you provide the 2-way driver to control your full Openmotics system by using RTI material and the source code files:

OpenMotics serial.rtidriver
[1]