Disclaimer

1
Disclaimer

• This presentation, for use by the TAC
  Partner Sales Channel, is designed to mirror very
  closely Bob Schultzs DVD whiteboard discussion
  (Introduction to TAC Open Systems Solutions -
  2003) regarding open systems, and the LON world.
  This presentation should be used with the
  following points in mind.
• !!!This IS NOT a sales tool!!! While certain
  sections of this presentation are suitable for a
  sales setting, there are specific pieces of
  information included that should NOT be presented
  to a potential client.
• 2. This presentation should be given only
  after watching the Bob Schultz DVD, and reading
  the notes associated with each slide. The slides
  themselves contain as little information as
  possible in an effort to create credibility for
  the presenter, and develop a relationship with
  the audience.

2
Open Systems
Terms, System Architecture Basic Concepts
3
Chapter 1

• LON Architecture
• The Enterprise Level
• The Hardware Level
• Channels Segments
• Speed Interoperability

4
The Enterprise Level

• Top Down Approach
• Older systems evolved into TCP/IP LON started
  there

The IP Level

• Can be the internet, an intranet, or crossover
  cabling. Any media that will handle TCP/IP.

5
The Enterprise Level

• Primary machine that interacts with the
  hardware environment.
• Vista IV Server

6
The Enterprise Level
Server

• Communicates with hardware through the server.
• Server/Client architecture implies vendor
  specific software.
• Multiple Clients possible
• Vista IV Workstation

7
The Enterprise Level
Server
Client

• Receives and broadcasts information from the
  server
• Vista IV Webstation

8
The Enterprise Level
The Web-Client
Server
Client
Webserver
TCP/IP

• Receives information from the Webserver.
• Vista IV Webstation 3CAL

9
The Enterprise Level

• Basic Enterprise level traffic flow
• These are pieces of software not necessarily
  separate machines.

10
The Hardware Level
Router
LON Backbone

• Routers
• Network traffic cop
• Protocol translation

11
The Hardware Level
12
Channels Segments

• Segment A piece of the network defined by the
  boundaries of any communication governor. 50
  device max.

• Device Any piece of equipment on the network
  that possesses an Echelon neuron chip I.D.

• Channel Boundaries defined by routers.
  Usually consists of 2 segments.

13
Channels Segments

• Terminators Absorb reflecting signals,and
  improve communication quality.

14
Channels Segments

• Common Misconception LON is Logically AND
  Physically Flat.
• 1 long wire carries all signals causing
  communications to bog, and system failure.

15
The Hardware Level

• Physically Tiered Logically Flat
• No device ever more than 3 steps away from the
  Enterprise Level.

Dont let anyone ever say we cannot deliver a
system with superb communication
characteristics. - Bob Schultz
16
The Hardware Level
Web-client
Server
Client
Webserver
TCP/IP

• Vastly scalable.

17
Network Speed Interoperability
Web-client
Server
Client
Webserver
TCP/IP

• Interoperability Defined by Media, Protocol
  Speed
• Echelon Transceiver forces 78kbs
• Guarantees interoperability

18
Chapter 2

• Data
• Network Bindings
• Formatting
• Echelon Conventions
• Data Transmission

19
Network Bindings
Building I
Building II

• Bind To connect and cause data flow
• Logically Flat True peer to peer. Opposite of
  Managed Communication
• LonMaker

20
Data Type SNVTs

• Standard Network Variable Type
• Basic format for data transmission across a
  LON-based network.

• Examples
• SNVT_temp_f -273.17 to 1E38 degrees C
• SNVT_freq_hz 0 to 6553.5 Hz
• SNVT_freq_khz 0 to 6553.5 kHz
• SNVT_power_f -1E38 to 1E38 watts
• SNVT_power_kilo 0 to 6553.5 kW
• Multiple syntax possibilities for each process
  variable

21
Echelon Conventions

• LonWorks The entirety of the LON protocol.
• LonMark A 3rd party guarantee of
  interoperability through the creation of LonMark
  profiles.

• Customer Freedom Depends on a Lack of Choice for
  Manufacturers

• LonWorks provides a choice.
• LonMark takes it away.

22
Data Transmission

• Send Pray
• Low Priority data
• Ex send OA temp to all VAV for display on stat.

• Send 3xs Pray Less
• Mid Priority data
• 99.9 effective

Pray
Pray Less

• Acknowledged
• Critical data
• Ex- Outside Air temp to a process controller

23
Chapter 3

• Devices Intra-level Communications
• Application Specific Devices
• Programmable Devices
• Server/Device Communication
• Software

24
Application Specific Devices

• A.S. Devices Pre-determined logic by
  manufacturer. Configuration necessary.
• VAV, Heat Pumpetc. controllers
• LON-Based Sensors
• LON-Based Actuators

TAC Xenta 101 Fan Coil ASC

• LON products add capability to contractors.
• More tools

25
Programmable Devices

• Programmable Devices Custom applications.
  Device is empty of logic off the shelf.
  Programmer in control.
• With I/O
• Sensors and Actuators wired in.
• Without I/O
• Logic only.
• No sensors or actuators wired in.

26
Server Device Communication

• Node-to-Node, more specifically, ASD-to-ASD
  communication in the LON World is fairly specific.

• In a TAC environment, data can be passed using
  public communication, specific to TAC.
• Programmable Controllers

27
Server Device Communication
Server

• LonTalk does not handle Server to
  Hardware communications well.
• Automatic Time Scheduling
• Trend Logs
• Alarm Handling
• Operator Functions
• Test
• Manual Control

Public Communication
TCP/IP
TAC Xenta 302
R
PLR
R
R
PLR

• Using Public Communication brings the total
  installed cost down!

28
Software

• Open Systems modularize software.

Server
Menta
Workstation
Webstation 3 CAL
Webstation
29
Software

• Main Functions
• Addressing
• Configuration (ASC)
• Application Creation
• Human Machine Interface

30
Software

• LonMaker for Windows
• Created by Echelon
• Addresses all nodes
• Binds all Network Communication

• Visio Based
• LNS Plug-in Support
• Creates As-built Reports

31
Software

• TAC Menta
• Extensive Block Library
• Real-time Simulation Trend Logging
• Off-line programming

32
Software

• TAC Vista IV Workstation
• HMI
• Alarm Handling
• Trend Logging
• Manual Control
• Automated Scheduling

33
Chapter 4

• Single Multi-Vendor
• Solutions
• Single Vendor/Single Building
• Multi-Vendor
• Multi-Vendor/Multi-Building LON
• Multi-Vendor/Multi-Building BACnet

34
Single Vendor/Single Building
Server

• Device Functionality

• ASCs have no memory

TCP/IP

• All Data flows to P.C. for processing

R
R
PLR
R
PLR
35
Single Vendor/Single Building
Server

• Device Functionality

• ASCs have no memory

TCP/IP

• All Data flows to P.C. for processing

Alarms Schedules Trends
R
Data Collection

• Alarm Generation
• Trend Storing
• Automated Schedules

Values
R
PLR
R
PLR
36
Multi-Vendor
Server

• Several logic only devices, placed high in the
  system architecture

TCP/IP
37
Multi-Vendor
Server

• NAC translates pure LON into HMI protocol.

TCP/IP
38
Multi-Vendor
Server
TCP/IP

• Only pure LON SNVTs are allowed to cross the DMZ

DMZ 100 LON SNVT

39
Multi-Vendor/Multi-Building - LON

• 1 Vendor controls the I.P. Level.
• That vendor is in the drivers seat with the
  client.
• More of a service contract at this level.
• Very little physical labor.

Building I Building II Building III
40
Multi-Vendor/Multi-Building - LON

• TAC can service a building even if the HMI
  doesnt belong to us.

Building I Building II Building III
41
Multi-Vendor/Multi-Building BACnet

• BACnet uses multiple HMIs

• 1 system designated as lead

• All subordinate servers pass information to
  lead

42
Summing It Up

• Physically Tiered Logically Flat
• Ladder/Rung Architecture
• Interoperability
• Speed, Media, Protocol
• LonMark Association
• Modular Software
• Single/Multi Vendor Systems
• Campus Multi-Building Systems

43
Keep in Mind

• Build a vocabulary a Dictionary
• Be SPECIFIC
• Plan Ahead

44
Data Transmission

• Send Pray
• Low Priority data
• Ex send OA temp to all VAV for display on stat.

• Send 3xs Pray Less
• Mid Priority data
• 99.9 effective

Send
Send
Send
Send

• Acknowledged
• Critical data
• Ex- Outside Air temp to a process controller

Send
Acknowledged