disclaimer this presentation, for use by the tac partner sales channel, is designed to mirror very...
TRANSCRIPT
DisclaimerDisclaimer
This presentation, for use by the TAC Partner Sales Channel, is designed to mirror very closely Bob Schultz’s 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.
1. !!!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.
Open SystemsOpen Systems
Terms, System Architecture & Terms, System Architecture & Basic ConceptsBasic Concepts
Chapter 1Chapter 1
LON ArchitectureLON Architecture
The Enterprise LevelThe Enterprise Level
The Hardware LevelThe Hardware Level
Channels & SegmentsChannels & Segments
Speed & InteroperabilitySpeed & Interoperability
The Enterprise LevelThe Enterprise Level
Top Down Approach Older systems evolved into TCP/IP – LON started there
TCP/IP
“The IP Level”
Can be the internet, an intranet, or crossover cabling. Any media that will handle TCP/IP.
The Enterprise LevelThe Enterprise Level
TCP/IP
“The Server”
Primary machine that interacts with the hardware environment.
Vista IV Server
The Enterprise LevelThe Enterprise Level
Communicates with hardware through the server.Server/Client architecture implies vendor specific software.
Multiple Clients possible• Vista IV Workstation
“The Client”
Server
TCP/IP
The Enterprise LevelThe Enterprise Level
Receives and broadcasts information from the serverVista IV Webstation
Server
TCP/IP
Client
“The Webserver”
The Enterprise LevelThe Enterprise Level
Receives information from the Webserver.Vista IV Webstation 3CAL
Server
Client Webserver
TCP/IPThe Internet
“The Web-Client”
The Enterprise LevelThe Enterprise Level
Basic Enterprise level traffic flowThese are pieces of software –not necessarily separate machines.
Server
Client Webserver
TCP/IPThe Internet
Web-client
Router
LON
Backbone
The Hardware LevelThe Hardware Level
RoutersNetwork traffic copProtocol translation
Server
Client Webserver
TCP/IPThe Internet
Web-client
The Hardware LevelThe Hardware Level
Client Webserver
TCP/IPThe Internet
Web-client
Physical Layer Repeater
Server
D D DDDD
Channels & SegmentsChannels & Segments
SegmentSegment – A piece of the network defined by the boundaries of any communication governor. 50 device max.
DeviceDevice – Any piece of equipment on the network that possesses an Echelon neuron chip & I.D.
ChannelChannel – Boundaries defined by routers. Usually consists of 2 segments.
Channels & SegmentsChannels & Segments
TerminatorsTerminators – Absorb reflecting signals,and improve communication quality.
T T TT
Channels & SegmentsChannels & Segments
Common Misconception – LON is Logically AND Physically Flat.1 long wire carries all signals causing communications to bog, and system failure.
50 Dev. 50 Dev.50 Dev. 50 Dev. 50 Dev. 50 Dev. 50 Dev. 50 Dev.
WRONG
The Hardware LevelThe Hardware Level
Physically Tiered Logically FlatPhysically Tiered Logically FlatNo device ever more than 3 steps away from the Enterprise Level.
““Don’t let anyone ever say we cannot deliver a Don’t let anyone ever say we cannot deliver a system with superb communication system with superb communication characteristics.”characteristics.”
- Bob Schultz
Client Webserver
TCP/IPThe Internet
Web-client
Server
50 Dev. 50 Dev.
50 Dev. 50 Dev.
The Hardware LevelThe Hardware Level
Vastly scalable.
Client Webserver
TCP/IPThe Internet
Web-client
Server
Network Speed & InteroperabilityNetwork Speed & Interoperability
Interoperability – Defined by: Media, Protocol & SpeedEchelon Transceiver forces 78kbs
Guarantees interoperability
Client Webserver
TCP/IPThe Internet
Web-client
78 kbps
1.25 Mbps
Or
78 kbps
100 Mbps
Server
Chapter 2Chapter 2
DataData Network BindingsNetwork Bindings
FormattingFormatting
Echelon ConventionsEchelon Conventions
Data TransmissionData Transmission
Network BindingsNetwork Bindings
BindBind – To connect and cause data flowLogically Flat – True peer to peer. Opposite of Managed Communication
LonMaker
D
D
Building I Building II
Data Type – SNVT’sData Type – SNVT’s
SStandard NNetwork VVariable TTypeBasic format for data transmission across a LON-based network.
ExamplesSNVT_temp_f = -273.17 to 1E38 degrees CSNVT_freq_hz = 0 to 6553.5 HzSNVT_freq_khz = 0 to 6553.5 kHzSNVT_power_f = -1E38 to 1E38 wattsSNVT_power_kilo = 0 to 6553.5 kW
Multiple syntax possibilities for each process variable
Echelon ConventionsEchelon Conventions
LonWorksLonWorks – The entirety of the LON protocol.
LonMark LonMark – A 3rd party guarantee of interoperability through the creation of LonMark “profiles”.
Customer Freedom Depends on a Customer Freedom Depends on a Lack of ChoiceLack of Choice for for ManufacturersManufacturers
LonWorks provides a choice.
LonMark takes it away.
Data TransmissionData Transmission
Send & PrayLow Priority data
Ex – send OA temp to all VAV for display on stat.
Send 3x’s & Pray LessMid Priority data
99.9% effective
Acknowledged
Critical data
Ex- Outside Air temp to a process controller
SendSendSendSendPrayPray LessGet it?Got it.
Chapter 3Chapter 3
Devices & Intra-level Devices & Intra-level CommunicationsCommunications
Application Specific DevicesApplication Specific Devices Programmable DevicesProgrammable Devices Server/Device CommunicationServer/Device Communication SoftwareSoftware
Application Specific DevicesApplication Specific Devices
A.S. Devices – Pre-determined logic by manufacturer. Configuration necessary.
VAV, Heat Pump…etc. controllersLON-Based SensorsLON-Based Actuators
TAC Xenta 101 Fan Coil ASC
TAC Xenta 102 AX VAV ASC
Belimo GM24 LON Actuator
LON products add capability to contractors.
More tools
Programmable DevicesProgrammable Devices
Programmable Devices – Custom applications. Device is empty of logic off the shelf. Programmer in control.
With I/OSensors and Actuators wired in.
Without I/OLogic only.
No sensors or actuators wired in.
TAC Xenta 401 Programmable Controller
TAC Xenta 302 Programmable Controller
Server Device CommunicationServer Device Communication
Node-to-Node, more specifically, ASD-to-ASD communication in the LON World is fairly specific.
D DOpen LonTalk
In a TAC environment, data can be passed using public communication, specific to TAC.
Programmable Controllers
TA Network Variables
TAC Xenta 401TAC Xenta 302
Server Device CommunicationServer Device Communication
LonTalk does not handle Server to Hardware communications well.
Automatic Time SchedulingTrend LogsAlarm HandlingOperator Functions
TestManual Control
Server
Using Public Communication brings the total installed cost down!
TCP/IP
R
PLRR
R
PLR
TAC Xenta 302
Public Communication
SoftwareSoftware
Open Systems “modularize” software.
SoftwareSoftware
Main FunctionsAddressingConfiguration (ASC)Application Creation
HHuman MMachine IInterface
LonMaker for Windows
TAC Menta
TAC Vista IV Workstation
SoftwareSoftware
LonMaker for WindowsCreated by EchelonAddresses all nodesBinds all Network Communication
Visio Based
LNS Plug-in Support
Creates As-built Reports
SoftwareSoftware
TAC MentaExtensive “Block” LibraryReal-time Simulation & Trend LoggingOff-line programming
SoftwareSoftware
TAC Vista IV WorkstationHMI
Alarm HandlingTrend LoggingManual ControlAutomated Scheduling
Chapter 4Chapter 4
Single & Multi-Vendor Single & Multi-Vendor
SolutionsSolutions
Single Vendor/Single BuildingSingle Vendor/Single Building
Multi-VendorMulti-Vendor
Multi-Vendor/Multi-Building – LONMulti-Vendor/Multi-Building – LON
Multi-Vendor/Multi-Building BACnet Multi-Vendor/Multi-Building BACnet
Single Vendor/Single BuildingSingle Vendor/Single Building
Device FunctionalityClient
TCP/IP
Server
R
R
R
PLR
PLR
TAC Xenta 101TAC Xenta 302
ASC’s have no memory
All Data flows to P.C. for
processingValues
Single Vendor/Single BuildingSingle Vendor/Single Building
Device FunctionalityClient
TCP/IP
Server
R
R
R
PLR
PLR
Data Collection
Alarms Schedules
Trends
ASC’s have no memory
All Data flows to P.C. for
processingValues
• Alarm Generation
• Trend Storing
• Automated Schedules
Multi-VendorMulti-Vendor
Several logic only devices, placed high in the system architecture
Client
TCP/IP
Server
Logic only devices (401’s)
Trends Alarm Gen.
Schedules
Multi-VendorMulti-Vendor
NAC translates pure LON into HMI protocol.
Client
TCP/IP
Server
Network Area Controller (NAC) i.e. – JACE Box
Multi-VendorMulti-Vendor
Only pure LON SNVT’s are allowed to cross the DMZ
Client
TCP/IP
Server
=
DMZ – 100% LON SNVT
Multi-Vendor/Multi-Building - LONMulti-Vendor/Multi-Building - LON
1 Vendor controls the I.P. Level.That vendor is in the driver’s seat with the client.More of a service contract at this level.
Very little physical labor.
Building I Building II Building III
= = =
Multi-Vendor/Multi-Building - LONMulti-Vendor/Multi-Building - LON
TAC can service a building even if the HMI doesn’t belong to us.
Building I Building II Building III
= = =
Multi-Vendor/Multi-Building BACnetMulti-Vendor/Multi-Building BACnet
BACnet uses multiple HMI’s
1 system designated as lead
All subordinate servers pass information to lead
Summing It UpSumming It Up
Physically Tiered – Logically FlatPhysically Tiered – Logically Flat Ladder/Rung Architecture
InteroperabilitySpeed, Media, Protocol
LonMark Association
Modular Software Single/Multi Vendor Systems
Campus & Multi-Building Systems
Keep in MindKeep in Mind
Build a vocabulary & a Dictionary Be SPECIFIC Plan Ahead
Data TransmissionData Transmission
Send & PrayLow Priority data
Ex – send OA temp to all VAV for display on stat.
Send 3x’s & Pray LessMid Priority data
99.9% effective
Acknowledged
Critical data
Ex- Outside Air temp to a
process controller
SendSend
SendSend
Send
Acknowledged