1 / 14

Achieving Interoperability in HVAC and Building Systems

Discover how interoperability in HVAC and building systems has evolved since DDC technology, enabling a seamless integration of various operations such as HVAC, fire, power, and security. Explore key protocols like BACnet, LonTalk, and Modbus that facilitate this integration, allowing for single-seat operations and flexible supplier selections. Learn about the benefits and limitations of each protocol and how Trane supports these standards to ensure successful interoperability across thousands of projects with over 30 companies, enhancing control and management efficiencies.

allistair-bates
Download Presentation

Achieving Interoperability in HVAC and Building Systems

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Interoperability Summary Trane Company

  2. Interoperable Protocols • Before we had DDC technology we had interoperability • Now solutions are available to make these systems interoperable

  3. Interoperable Goals • Single seat operation - HVAC, Fire, Power, Security, etc. • Ability to select the best supplier to expand a system • Ability to select the best alternatives when purchasing parts of a system

  4. How do you achieve Interoperability? • There are several promising technologies • BACnet (ASHRAE / ANSI 135-95) • LonTalk (EIA 709.1) • Modbus (Industrial defacto Protocol)

  5. BACnet • ASHRAE Standard developed by consensus committee • Defines standard method of moving data as well as how to model data, and physical transport methods • BACnet is now under constant revision

  6. BACnet Pros and Cons • BACnet is designed to work on networks and IP • How to exchange data, schedule, trend, alarm, and manage the network are all clearly defined • What comprises a controller is not yet defined • Works great on networks!

  7. LonTalk • Developed by Echelon Corporation - now an EIA standard • How to move data and physical layer are defined in a chip - the Neuron • LonMark is an organization that has created a series of standard device models called profiles

  8. LonMark Profiles • The LonMark association has created standard equipment profiles • For example Space Comfort Controller, Discharge Air Controller, Chiller, etc.

  9. LonMark Profiles Space Comfort Controller Outputs Inputs Space Temp. Space Temp. Local Setpoint Fan Speed Fan Run Hours Master Slave Input Configuration Default Setpoints Mandatory Override Time Optional Setpoint Limits Proprietary

  10. LonTalk Pros and Cons • LonTalk is easy to implement with the use of the Neuron chip • LonTalk protocol works great for controllers • The Profiles make controllers interchangeable • Using LonTalk over IP is presently proprietary

  11. Modbus • Industrial defacto standard • Many sub-versions exist (RTU, ASCII, Ethernet, IP, etc.) • Allows data exchange only • Trane supports with the use of a Bridge

  12. Interoperability Summary • Using standard protocols the goals of Integration and Interoperability can be met • Trane Support BACnet, LonTalk, and Modbus as part of Tracer Summit • Trane has connected to over 30 companies on thousands of projects

  13. Other Equipment Typical Tracer Summit Architecture Trane Protocol or LonTalk BACnet LAN Chillers, AHU, Etc. Chillers, AHU, Etc. Chillers, AHU, Fire Alarm VAV boxes

  14. Questions and Discussion

More Related