LON and BACnet: History and Approach - LonWorks · PDF fileLON and BACnet: History and...
Transcript of LON and BACnet: History and Approach - LonWorks · PDF fileLON and BACnet: History and...
![Page 1: LON and BACnet: History and Approach - LonWorks · PDF fileLON and BACnet: History and Approach Serge LeMen Newron System, General Manager](https://reader031.fdocuments.in/reader031/viewer/2022030417/5aa3e8cb7f8b9a7c1a8b6a4b/html5/thumbnails/1.jpg)
LON and BACnet: History and Approach
Serge LeMen
Newron System, General Manager
![Page 2: LON and BACnet: History and Approach - LonWorks · PDF fileLON and BACnet: History and Approach Serge LeMen Newron System, General Manager](https://reader031.fdocuments.in/reader031/viewer/2022030417/5aa3e8cb7f8b9a7c1a8b6a4b/html5/thumbnails/2.jpg)
The same goals
• Intend to propose a standard architecture
• Intend to be normalized
• Be at solution level: from product to system
• Propose a multi manufacturer solution
• Simplify and dope supervision
• Simplify maintenance
– Corrective
– Evolutive
![Page 3: LON and BACnet: History and Approach - LonWorks · PDF fileLON and BACnet: History and Approach Serge LeMen Newron System, General Manager](https://reader031.fdocuments.in/reader031/viewer/2022030417/5aa3e8cb7f8b9a7c1a8b6a4b/html5/thumbnails/3.jpg)
LonWorks® history
• Technology created in1988 by Echelon Corp. The firm own the rights (IPR)
• A founder: Mike Markkula: Ex Apple … different …
• A “networked” vision of openness « peer to peer »
• A vision from the IT: decentralize automation
• Product Interoperability: LonMark was born in 1994
• System Interoperability: LNS was born in 1997
• In 1999, Echelon choose to standardize LonWorks® EIA709.x , EIA 852, EN14908, …
![Page 4: LON and BACnet: History and Approach - LonWorks · PDF fileLON and BACnet: History and Approach Serge LeMen Newron System, General Manager](https://reader031.fdocuments.in/reader031/viewer/2022030417/5aa3e8cb7f8b9a7c1a8b6a4b/html5/thumbnails/4.jpg)
BACnet history • ASHRAE discovers a need in 1987
A collection of individual company need!
• They set up a committee : SPC-135P: BACnet was born
• Collection of companies that want to gather information => cannot force a protocol => Find a consensus: a meta protocol
• Vision of openness «Protocol Standardization »
• From 1995 to 2010 specifications are moving => different communication media/ objects
• In 2000, BMA ask for a product certification Creation of BACnet Testing Laboratories (BTL)
• BACnet becomes a standard: EN16484
![Page 5: LON and BACnet: History and Approach - LonWorks · PDF fileLON and BACnet: History and Approach Serge LeMen Newron System, General Manager](https://reader031.fdocuments.in/reader031/viewer/2022030417/5aa3e8cb7f8b9a7c1a8b6a4b/html5/thumbnails/5.jpg)
Standard properties ;o)
Open
Standard
Interoperable
LonMark Association
LonUsers
(F,UK,D,Dk,Fi,It,NL,
CH,Po,Es,US,Sg,Chi)
Test: LonMark
Open
Standard
Interoperable
BMA Association
BIG
(Nor Am, Eu)
Test: BTL
LonWorks® BACnet
![Page 6: LON and BACnet: History and Approach - LonWorks · PDF fileLON and BACnet: History and Approach Serge LeMen Newron System, General Manager](https://reader031.fdocuments.in/reader031/viewer/2022030417/5aa3e8cb7f8b9a7c1a8b6a4b/html5/thumbnails/6.jpg)
LonWorks® system vision
The « networked » openness vision Peer to peer
We come from the field to go up to the management
Centralized Proprietary sub systems
Opened, multi vendor
![Page 7: LON and BACnet: History and Approach - LonWorks · PDF fileLON and BACnet: History and Approach Serge LeMen Newron System, General Manager](https://reader031.fdocuments.in/reader031/viewer/2022030417/5aa3e8cb7f8b9a7c1a8b6a4b/html5/thumbnails/7.jpg)
BACnet system vision The « consensus» openness vision
Automation Island
We come from then management to gather the complete protocols
Local supervision
META Supervision
Protocol(s)
BACnet Supervision
Protocol(s)
![Page 8: LON and BACnet: History and Approach - LonWorks · PDF fileLON and BACnet: History and Approach Serge LeMen Newron System, General Manager](https://reader031.fdocuments.in/reader031/viewer/2022030417/5aa3e8cb7f8b9a7c1a8b6a4b/html5/thumbnails/8.jpg)
Zoom on strength due to history
• BACnet good at automation level – Standardized automation level
– Interoperable alarming / scheduling / Trending
– Excellent application objects
– Historically designed to gather different field networks
• LonWorks® good at network management – A true interoperable commissioning method
– A real effective peer 2 peer binding at field
– An efficient embedded field test system
– Historically designed to build up a single field network
![Page 9: LON and BACnet: History and Approach - LonWorks · PDF fileLON and BACnet: History and Approach Serge LeMen Newron System, General Manager](https://reader031.fdocuments.in/reader031/viewer/2022030417/5aa3e8cb7f8b9a7c1a8b6a4b/html5/thumbnails/9.jpg)
Compared architectures
File
d
level
Managem
ent
level
BACnet
LonWorks®
LonWorks®
LonWorks®
![Page 10: LON and BACnet: History and Approach - LonWorks · PDF fileLON and BACnet: History and Approach Serge LeMen Newron System, General Manager](https://reader031.fdocuments.in/reader031/viewer/2022030417/5aa3e8cb7f8b9a7c1a8b6a4b/html5/thumbnails/10.jpg)
Results depending on management level LonWorks® at field level BACnet Lon
Standard and interoperable
Supervision
Ensure automation functions
Interconnection and island exchange
Ensure field level management functions
Ensure field level maintenance functions
Ensure field level configuration functions
√
√
√
√
√
√
√
X*
X*
X*
*Enabled if gateway embeds a LON router
√ √
√ √*
![Page 11: LON and BACnet: History and Approach - LonWorks · PDF fileLON and BACnet: History and Approach Serge LeMen Newron System, General Manager](https://reader031.fdocuments.in/reader031/viewer/2022030417/5aa3e8cb7f8b9a7c1a8b6a4b/html5/thumbnails/11.jpg)
Why?? History!!
• BACnet objects only embed application data to collect information
• BACnet objects do not embed LonWorks ® management functions
• BACnet objects do not embed LonWorks ® maintenance functions
• LNS ensures a LonWorks® database system interoperability