building technologies standard protocols update january 2011 building automation integration &...
TRANSCRIPT
Building TechnologiesStandard Protocols Update January 2011
Building Automation
Integration & Standard ProtocolsIntegration & Standard Protocols
Building TechnologiesStandard Protocols Update January 2011
Topics
• Systems integration why and how?• Protocol inner workings • BAS migration• Modbus pros and cons • LonTalk pros and cons• BACnet pros and cons• Questions
Fascinating!!
Building TechnologiesStandard Protocols Update January 2011
Protocols within building subsystems…
BACnetLonTalkModbusOPCProprietary
ModbusLonTalkBACnetEIBProprietary
ModbusProfibusOPCProprietary
BACnetLonTalkModbusProprietary
ProprietaryBACnet
ProprietaryBACnet
ModbusLonTalkProprietary
Graphics, Internet
Schedules
Reports & Alarms
Text & E-mail
H
V
A
C
F
I
R
E
A
C
C
E
S
S
L
I
G
H
T
I
N
G
P
O
W
E
R
S
C
A
D
A
B
A
S
Building TechnologiesStandard Protocols Update January 2011
BACnet/IP
System Architecture
BACnet MS/TP, LonTalk, ModbusProprietary Protocols, Modbus
H
V
A
C
L
I
G
H
T
I
N
G
B
A
S
F
I
R
E
A
C
C
E
S
S
P
O
W
E
R
B
A
S
Building TechnologiesStandard Protocols Update January 2011
B
A
S
BACnet/IP
Ethernet
Legacy BAS Migration
Proprietary Protocol to BACnet/IPProprietary Protocol to BACnet/IP
Functions to ExpectFunctions to Expect
Translation
B
A
S
Translation
Monitor and Command
Alarm
Trend
Schedule
Proprietary
Protocol A
Proprietary
Protocol B
Building TechnologiesStandard Protocols Update January 2011
B
A
S
BACnet/IP
Ethernet
Legacy BAS Migration
Proprietary Protocol to BACnet/IPProprietary Protocol to BACnet/IP
Migration Changes ToolsMigration Changes Tools
Translation
B
A
S
Translation
Programming
Database
Commissioning Tools
Schedules
Proprietary
Protocol A
Proprietary
Protocol B
Building TechnologiesStandard Protocols Update January 2011
B
A
S
BACnet/IP
Ethernet
Legacy BAS Migration
Proprietary Protocol to BACnet/IPProprietary Protocol to BACnet/IP
BenefitsBenefits
Translation
B
A
S
Translation
Single Programming Language
Single Database
Consistent Commissioning Tools
Consistent Schedules
Proprietary
Protocol A
Proprietary
Protocol B
Building TechnologiesStandard Protocols Update January 2011
Top Benefits of Sharing and Aggregating Information
● Lower energy costs
● Lower maintenance costs
● Improved staff utilization
● Lower repair and replacement costs/extend equipment life
● Increase occupant comfort/tenant productivity
● Improve system performance
● Generate business decision support information
● Enterprise wide data consolidation
Building TechnologiesStandard Protocols Update January 2011
Protocol Inner Workings
A protocol is a set of rules defining the format of data transmission between two or more devices.
The protocol defines:
•Data format and composition
•Addressing
•Error checking
•Data compression
•Send/receive message notification
For communications to work effectively between two or more devices, the rules covering the required functionality must be interpreted and implemented exactly the same way
The OSI Model explains the basics
Building TechnologiesStandard Protocols Update January 2011
• Developed by Modicon (Schneider Electric)
• Considered a defacto-standard• Register based protocol
• Digital data• Analog data
• Master/Slave or Client/Server based architecture
• Several types of Modbus:• Modbus RTU• Modbus ASCII• Modbus Plus• Modbus TCP
Integration Using Modbus
ModbusModbus - Overview - OverviewModbusModbus - Overview - Overview
ModbusDriver
EBLNMLN
RS-485
Modbus TCP
Modbus RTU
Building TechnologiesStandard Protocols Update January 2011
• Simple data protocol means simple development
• Extensive implementation in many building systems:
• Process controls• Power meters• Power and Lighting control• Chillers• Boilers• BAS
• Leverage existing driver development and integration expertise
Integration Using Modbus
Modbus - ProsModbus - ProsModbus - ProsModbus - Pros
ModbusDriver
EBLNMLN
RS-485
Modbus TCP
Modbus RTU
Building TechnologiesStandard Protocols Update January 2011
Integration Using Modbus
Modbus - Modbus - ChallengesChallengesModbus - Modbus - ChallengesChallenges
• Simple protocol means functionality limited
• No high level application standardization
• No time stamping
• Information limited to simple register data implemented by vendor
• Vendors may not implement the standard consistently
• Mapping is project specific
ModbusDriver
EBLNMLN
RS-485
Modbus TCP
Modbus RTU
Building TechnologiesStandard Protocols Update January 2011
Integration Using LonTalk
LonTalk – OverviewLonTalk – OverviewLonTalk – OverviewLonTalk – Overview
• LonWorks Technology is from Echelon Corp.
• LonWorks is a suite of products
• LonMaker Integration Tool
• LNS network operating system
• iLon IP router and Internet Server
• LonTalk protocol
• Neuron Chip
LonTalk Devices
LonTalkDevices
Network Manager
Building TechnologiesStandard Protocols Update January 2011
Integration Using LonTalk
LonTalk – ProsLonTalk – ProsLonTalk – ProsLonTalk – Pros
• LonTalk is the standard protocol• ANSI/EIA/CEA 709.1 A 1999
• LonTalk is an effective device level protocol standard
• Product selection impressive• HVAC and BAS devices• Lighting control
• LonMark controllers adhering to LonMark profiles are cost effective and standard
• Neuron chip provides unique address out of factory
LonTalk Devices
LonTalkDevices
Network Manager
Building TechnologiesStandard Protocols Update January 2011
Integration Using LonTalk
LonTalk – LonTalk – ChallengesChallengesLonTalk – LonTalk – ChallengesChallenges
• LonTalk standard does not define important applications
• Scheduling, Trending, Alarming, Programming, etc.
• LonMark profiles provide few mandatory network variables, leading to many variances in vendor implementations
• LonMark programmable controllers do not conform to LonMark profiles
LonTalk Devices
LonTalkDevices
Network Manager
Building TechnologiesStandard Protocols Update January 2011
Integration Using LonTalk
LonTalk – LonTalk – ChallengesChallengesLonTalk – LonTalk – ChallengesChallenges
• Device vendors create non-standard implementations
• proprietary network variables
• proprietary start-up and commissioning tools
• Little acceptance in certain systems
• Fire, Security, Power, PLCs LonTalk Devices
LonTalkDevices
Network Manager
Building TechnologiesStandard Protocols Update January 2011
Integration Using LonTalk
LonTalk – LonTalk – ChallengesChallengesLonTalk – LonTalk – ChallengesChallenges
• LonTalk Standard does not define system level components
• Network Operating Systems
• Network Management Software products
• Web server products
• Database is site/job and vendor specific
• Hardware, licensing fees, and royalties are high
LonTalk Devices
LonTalkDevices
Network Manager
Building TechnologiesStandard Protocols Update January 2011
• ASHRAE 135-2004 and 2008 Standard
• Communications media (MS/TP, ARCnet, Ethernet, IP, PTP, LonTalk)
• PICS (Protocol Implementation and Conformance Statement) and BIBBS (BACnet Interoperability Building Blocks) from vendors
• BTL (BACnet Testing Lab) certification process
BACnet - OverviewBACnet - OverviewBACnet - OverviewBACnet - Overview
Integration using BACnet
Ethernet
RS485
Other BACnet Controller
BACnet/IP
BACnetMS/TP
Building TechnologiesStandard Protocols Update January 2011
• Available from most BAS and HVAC equipment vendors
• Cost effective integration solution• Standard provides insulation from
vendor system migrations and upgrades
• Standard allows for flexibility in implementation
• Protocol implementation disclosure documents (PICS and BIBBs)
• Testing procedure and certification (BTL)
BACnet - ProsBACnet - ProsBACnet - ProsBACnet - Pros
Integration using BACnet
Ethernet
RS485
Other BACnet Controller
BACnet/IP
BACnetMS/TP
Building TechnologiesStandard Protocols Update January 2011
• Network security• Encryption mechanism in
review• Standard in review for user
authentication and access rights
• Programming language• Every system will have a
unique programming language
• Unique programming tools are required for each vendor
BACnet - ChallengesBACnet - ChallengesBACnet - ChallengesBACnet - Challenges
Integration using BACnet
Ethernet
RS485
Other BACnet Controller
BACnet/IP
BACnetMS/TP
Building TechnologiesStandard Protocols Update January 2011
• Configuration tools are proprietary• No device application profiles• System and device control
algorithms are unique to vendors• Database structure not
standardized• Methods of implementing
functionality vary from vendor to vendor
• Private transfer services• Proprietary objects
BACnet - ChallengesBACnet - ChallengesBACnet - ChallengesBACnet - Challenges
Integration using BACnet
Ethernet
RS485
Other BACnet Controller
BACnet/IP
BACnetMS/TP
Building TechnologiesStandard Protocols Update January 2011
Steps to Successful Integration
• Document functional requirements
• Assess and assign integration responsibilities
• Assess the capabilities against expectations and requirements
• LonTalk Variables
• Modbus Register List
• BIBBS (BACnet Interoperability Building Blocks)
• BACnet Object List
• Communication between departments
• Facilities
• IT
• Purchasing
• Communicate and coordinate vendor responsibilities for integration implementation and commissioning
Building TechnologiesStandard Protocols Update January 2011
Questions