Bacne Tvs Lon Works

8/2/2019 Bacne Tvs Lon Works

1/37

Current Direction of Building Automation

BACnet

Lonworks

World View


2/37

An Overview of...


3/37

An Overview of...


4/37

An Introduction - What is BACnet?

Acronym for Building Automation and Control Network Protocol

Allows different systems to operate in a

coherent automation & control systemInternationally recognized standard since1995 (NIST, CEN)

Open data communications protocol: standardmeans of communicating between computers and devices and

share data regardless of the equipment manufacturer


5/37

The Protocol - Basic Elements

BACnet Architecture

Object Properties

BACnet Services

BACnet Media

BACnet Devices

BACnet Objects


6/37

The Protocol - Network Media Types

Peer-to-peer CSMA/CD LAN operating at10 Mbps or 100 MbpsThin-wire (10Base2)

Thick-wire (10Base5) coax cableTwisted pair (10BaseT)Fiber optics (10BaseF)

Ethernet

Peet-to-peer token-passing LAN typicallyoperating at 2.5 MbpsCoax cableTwisted pair

Fiberoptic cable.

ARCnet

Physical connections between BACnetdevices for transfer of BACnet messages


7/37

The Protocol - Media Types

EIA-485 LAN which can operate at 9600,19.2 K, 38.4 K, and 76.8 K bps.

Master devices are peer devices that passa token.Slave devices co-exist on the same wire

but can only respond to Master devices.

MS/TP

EIA-232 protocol that provides serialcommunications between two BACnet

devices, connected continuously or viadial-up modem.

PTP


8/37

The Protocol - Media Types

Based on Neuron Chip developed byEchelon with transceiver operating at 78

KBaud or 1.2 MBaudTwisted pairPower line carrierWireless connections

LonTalk


9/37

The Protocol - BACnet Objects

Data model for BACnet devices:

Analog Output

Analog Value

Analog Input

Binary Input

Binary Output

Binary Value

Calendar

Command

Event Enrollment

File

Group

Device

Loop

Multi-State Input

Multi-State Value

Multi-State Output

Notification Class

Program

Schedule

Trend log (new)

Proprietary

Objects


10/37

The Protocol - BACnet Services

How a BACnetdevice obtains, commands and acknowledgesinformation from one device to another device.

BACnetdefines 32 services, classified into 5 categories

Alarm and Events File Access

Object Access Remote DeviceManagement

VirtualTerminal

Acknowledge Alarm AtomicRead File

Add ListElement

DeviceCommunicationControl

VT-Open

Confirmed Change of ValueNotification

AtomicWrite File

Remove ListElement

ConfirmedPrivate Transfer

VT-Close

ConfirmedEvent Notification

Create Object UnconfirmedPrivate Transfer

VT-Data

Get AlarmSummary

Delete Object Re initialiseDevice

Get EnrolmentSummary

Read Property Confirmed TextMessage

Subscribe COV Read PropertyConditional

TimeSynchronisation

UnconfirmedChange of Value Notification

Read PropertyMultiple

Who-Has

Write Property Who-IsWrite PropertyMultiple

I-Am


11/37

The Protocol - Combined Elements

Existing Definitions

Functional groups

Conformance classes

New Definitions

BACnet Interoperable Building Blocks

Functional profiles


12/37

TRENDING- A TRENDING- B

ALAR

MING-A

ALARM

ING-B

DATASHARING-A DATASHARING-B SCHEDU

LING-A

SCHEDU

LING-B

NETWORKMGMT-A NETWORKMGMT-B

BACnet Interoperable Building Blocks

Data Sharing

Alarm & Event Management

Time Scheduling

Trending-150

-100

-50

0

50

100

150

BIBBs

Device and Network Management


13/37

The Protocol - PICS

PROTOCOL

IMPLEMENTATION

CONFORMANCE

STATEMENTS


14/37

Operator Workstation

Building Controller Advanced Application Controller

Application Specific Controller

Smart Sensor / Actuator

BACnet Device Profiles


15/37

An Introduction - What BACnet doesnt

provide ...

Device Set-up/ConfigurationCommon programming language

Operator Look & Feel

Total Plug & Play connectivity


16/37

Lonworks - what is it?


17/37

Lon mark Heat Pump Controller

Space Temperature

Setpoint from network

Actual Space Temp Used

Current status of unit

HVAC Mode command from

network

Network occupancy statusOccupancy status

Setpoint offset

Auxiliary heat enable

Setpoint currently being

used

Space Tempnv1

SetPointnv2

S aceTemnv3

UnitStatusnv4

EffectSetPtnv10A licModenv5

OccCmdnv6

Occu Swnv7

SetPtOffsetnv8

AuxHeatnv9

nc60 Temperature Setpoint (mandatory)

nc49 Send Heartbeat

nc17 Location (optional)nc48 Maximum Receive Time (optional)

Manufacturer

Defined

Section

Configuration Properties

Optional

Network

Variables

Mandatory

Network

Variables

Heat Pump

Hardware

Output

Hardware

Input

Figure 1.2 Heat Pump with Temperature Object Details

H d


18/37

Lon mark Fan Coil Controller

Space Temperature

Setpoint from network

Heat valve status

Cool valve status

Fan speed statusFan speed control

HVAC mode - heat/cool

Setpoint offset

Supply water temperature

Energy demand

Power consumption

Supply air temperatureReheat stage status

Space temperature status

Actual setpoint used

S ace Temnv1

SetPointnv2

HeatOutputnv3

CoolOutputnv4

FanSpeednv5

TerminalLoadnv11

LoadAbsnv12

DischAirTempnv13

Reheatnv14

SpaceTempnv15

EffectSetPtnv16

FanS eedCmdnv6

OccCmdnv7

ApplicModenv8

SetPtOffsetnv9

WaterTempnv10

DischAirTemnv17

EnergyHoldOffnv18 OccCmdnv19

EnergyHoldOffnv20

UnitStatusnv21

nc49 Send Heartbeat (mandatory)

nc48 Maximum Receive Time (optional)

nc60 Occupancy Temperature Setpoints (mandatory)

nc52 Minimum Send Time (optional)

nc17 Location (optional)

nc59 Number of Out ut Valves (o tional)

Manufacturer

Defined

Section

Configuration Properties

Optional

Network

Variables

MandatoryNetwork

Variables

Fancoil Unit Controller

Object: 8020

Hardware

Output

Hardware

Input


19/37

How does Lonworks operate

Operator Work Station

Fan System controller

VAV Box controller

- Fan control and status

- Mixed air damper control

- Supply air control ofheating coil

- Morning warm up andnight setback


- Occupancy activation

- Warm up mode - max heat

- Standby mode - no flow- Temperature setpoints

- Weekly schedules

- Annual Schedules

- Optimal start routine - Custom programming - Graphical interface

- User security

- Totalizers

- Trend logs

- Alarms

- VAV demand resets SAT

- Summer operation, boilers off

- Teacher enters front door

Scheduler


20/37

Connecting Lonworks - Binding



VAV Box controller









- Weekly schedules

- Annual Schedules


- User security

- Totalizers

- Trend logs

- Alarms




Scheduler


21/37

Connecting Lonworks - Network Management



VAV Box controller









- Weekly schedules

- Annual Schedules


- User security

- Totalizers

- Trend logs

- Alarms




SchedulerNetwork Database- Binding Backups


22/37

Lonworks and BACnet


23/37

Myths about Lonworks and BACnet

Only one standard will be left standing

They work together in harmony

One is expensive, the other isnt

One is simple, the other is complicated

Specifying is a nightmare

BACnet and Lonworks were designed for specific

applicationsTesting and certification is complete/missing


24/37


Only one standard will be left standing

Both Lon works and BACnet have different

strengths and weaknesses Control manufactures are designing hybrid product

lines

Products are not mutually exclusive

BACnet is a vendor and hardware independent

communication protocol available to everyone.


25/37


They work together in harmony

Some manufactures want their side to win and direct

ads and hype accordinglySome manufactures have incorporated the

communication technology for marketing reasons

Must realize that both groups have to work together


26/37


One is expensive, the other isnt

What story do you want to hear today

At the end device level, vav box or fan systemcontroller, this varies depending on the size of the

application and media type chosen
http://prevpage/http://prevpage/


27/37


One is simple, the other in complicated

They are both very complicated - if you are a

technician required to understand the inner workingsThey are both simple if you are an operator running

a system


28/37


Specifying is a nightmare

Depends on which control manufactures you use

Specialized Lonworks systems integrators writingdivision 13000 or 17000 indicate that this requires a

high degree of expertise.

BACnet specifying can be a similar experience

Specifying DDC system shall be BACnet/Lonworks

will not be adequate


29/37


BACnet or Lonworks was designed for a specific application

BACnet was designed to connect 2 different

proprietary systems together NOT for buildingcontrols

May have been the intent when Cornell university

instigated the process 12+ years ago

Lonworks was designed for the transportation

industry Now it is used in military, aircraft, general industrial

and HVAC industry


30/37


Testing, Certification, Verification is complete/missing

The Lon mark designation indicates that the product has been

certified to meet the protocol standards

Lon mark is not a standards body but a group of gold levelmembers

Landmarks provides certification but not verification

BACnet is just implementing testing/certification process BACnet manufactures association (BMA) and BACnet testing

laboratory (BTL)

Test qualification program underway and scheduled to completeend of 2001

Full verification


31/37

What are some of the real differences

Lonworks BACnet

Proprietary protocol built into a chip

set

Originated from transportation

industry, Echelon Corporation

Protocol in use in many industrial

type applications thus is relatively

genericDevice level protocol - determines

set of characteristics, inputs, outputs,

setpoints, for each type of device

Processor limits to Neuron chip

small applications

separate processor required for

larger applications

Consensus developed standard

protocol

Initiated by Cornell University,

owner driven

Protocol optimised for the building

automation industry

Functional view point of protocol -

objects and services

Object model protocol

Standard network chip for

Ethernet/ARCnet

RS485 (MS/TP) can have

application imbedded with network


32/37


Lonworks BACnet

Network communication speeds of

78,000 to 1.5 mbaud Lontalk

Network packet sizing of 256 bytes

Non deterministic network

Multiple networks topologies

include Ethernet, ARCnet, RS485

(MS/TP), RS232 (PTP), Lontalk

Speeds vary from 10 mbaud down

to 9600 baud.

Network packet sizing from 30

bytes to 1500 bytes at EthernetNon deterministic network -

Ethernet

Deterministic network - ARCnet,

MS/TP


33/37


Lonworks BACnet

Network manager per island of

control, only one master

Priority level of control is limited to

predefined profiles

User implemented

Pricing varies depending if the

application required can be supported

directly by the Neuron chip. If not a

second processor must be added.

Only manufactured by limited set of

companies

There is no master controller,

system architectures vary in

degrees of distributed control. Not a

BACnet limitation

16 levels of priority from Manual

life safety, operator commands,

general control languages etc.Defined by Ashrae

MS/TP is very inexpensive and

doesnt require a second processor

Ethernet and ARCnet have

separate network chips thus more

expensive

Standard chips mean mass

production


34/37

Whats the World Doing?

The importance of Europe is being proven again in the field ofbuilding automation controls. Think who owns, controls, and runs

a number of US control firms

The European Committee for Standardization, CEN, has beendrawing up standards for the Heating, Cooling and Ventilation

industry under technical committee TC247

They created a three level hierarchical model calledmanagement, automation, and field

Management level - communications, monitoring, alarms,

trends, energy management, links to non-HVAC systemsAutomation level - majority of real-time functions are executed

Field level - unitary or application specific controllers


35/37

European protocol standards for building automation

Level Protocol Description

Management FND (DIN V 32735) German (Govt) firm neutral

BACnet

Automation PROFIBUS Process field bus

WorldFIP Factory instrumentation

BACnet

Field Batibus French

EHS European home systemEIB European installation bus

Lontalk


36/37

International Organization for Standardization - ISO

Working group 3 of ISO committee TC205, Building

Environment Design, recently adopted BACnet as its

working draft for building control protocolLooking to resolve differences in the way BACnet

should be used over the internet


37/37

Application Areas for Sensor/Control/Data Networks

Data processing and networks

Ethernet

Building

DeviceNet

Fieldbus

LonWorks

BACnet

Sensor

Zone

Profibus

Documents

Bacne Tvs Lon Works