LONWORKS Topics: 1 – Network Requirements 2 – Network Variables

LONWORKS Topics: 1 – Network Requirements 2 – Network Variables
3 – Labwork Overview

LonWorks CONTINUE 1 – Network Requirements 2 – Network Variables
EST: 60:00 1 – Network Requirements 2 – Network Variables 3 – Labwork Overview When you’ve completed this presentation on EC-gfxProgram Basics, click on the “QUIZ” button below to take a short quiz Then click the brown “NEXT MODULE” arrow below to advance to the next e-module – Module X: Module Name. CONTINUE Click to review Instructions >

NETWORK REQUIREMENTS Topic 1
Peer-to-Peer Network CHAPTER 3 LONWORKS NETWORK REQUIREMENTS Topic 1 BACK TO MENU

Peer-to-Peer Network Now we will review the best practices for Device Addressing as well as recommendations for MS/TP Device MAC Addresses, configuration of the MS/TP Bus Master Device, configuration of the BACnet Device Instance Number and an overview of a Numbering System Example scenario. BACK TO MENU

Peer-to-Peer Network - Neuron Chipset
The central unit of any Lon device is the “Neuron® chipset.” The Neuron® chipset incorporates communications, control, scheduling and I/O support. Essentially, it is a “system on a chip.” Inside each Neuron chipset is dynamically recorded all other Lon devices/objects that require communication with it. Now we will review the best practices for Device Addressing as well as recommendations for MS/TP Device MAC Addresses, configuration of the MS/TP Bus Master Device, configuration of the BACnet Device Instance Number and an overview of a Numbering System Example scenario. BACK TO MENU

Peer-to-Peer Network - Neuron Chipset
COOL RIGHT? Now we will review the best practices for Device Addressing as well as recommendations for MS/TP Device MAC Addresses, configuration of the MS/TP Bus Master Device, configuration of the BACnet Device Instance Number and an overview of a Numbering System Example scenario. BACK TO MENU

Neuron Communication - Binding
When a set of VAV controllers needs to communicate with an AHU, the data they send out Is written into an internal “Neuron Table” of each of the controllers involved and then “bound”. This binding process ensures consistent and persistent communications. Now we will review the best practices for Device Addressing as well as recommendations for MS/TP Device MAC Addresses, configuration of the MS/TP Bus Master Device, configuration of the BACnet Device Instance Number and an overview of a Numbering System Example scenario. BACK TO MENU

TP/FT-10 Network Topologies
TP/FT-10 stands for “twisted pair/free topology.” Lon is flexible in that it can be installed using either a Bus or Free topology, although a Bus topology is normally used. Now we will review the best practices for Device Addressing as well as recommendations for MS/TP Device MAC Addresses, configuration of the MS/TP Bus Master Device, configuration of the BACnet Device Instance Number and an overview of a Numbering System Example scenario. Network Guide, CH 3 BACK TO MENU

Lon Network Channel Attributes
Now we will review the best practices for Device Addressing as well as recommendations for MS/TP Device MAC Addresses, configuration of the MS/TP Bus Master Device, configuration of the BACnet Device Instance Number and an overview of a Numbering System Example scenario. Network Guide, CH 3 BACK TO MENU

Lon Network Wiring Network Guide, CH 3
Now we will review the best practices for Device Addressing as well as recommendations for MS/TP Device MAC Addresses, configuration of the MS/TP Bus Master Device, configuration of the BACnet Device Instance Number and an overview of a Numbering System Example scenario. Network Guide, CH 3 BACK TO MENU

Lon Network Load . A maximum of 128 Lon devices is permitted per subnet. However, after 64 devices, you must extend the network using either a repeater or router. Now we will review the best practices for Device Addressing as well as recommendations for MS/TP Device MAC Addresses, configuration of the MS/TP Bus Master Device, configuration of the BACnet Device Instance Number and an overview of a Numbering System Example scenario. BACK TO MENU

Extending a Lon Network
TOPOLOGY MAX CABLE LENGTH CABLE TYPE Bus 1400 meters Type 1 (22 AWG) 2700 meters Type 2 (16 AWG Free 400 meters 500 meters Type 2 (16 AWG) In Lon, a single router or repeater is permitted to extend the network if needed, beyond the above lengths. Now we will review the best practices for Device Addressing as well as recommendations for MS/TP Device MAC Addresses, configuration of the MS/TP Bus Master Device, configuration of the BACnet Device Instance Number and an overview of a Numbering System Example scenario. Network Guide, CH 3 BACK TO MENU

Extending a Lon Network
Now we will review the best practices for Device Addressing as well as recommendations for MS/TP Device MAC Addresses, configuration of the MS/TP Bus Master Device, configuration of the BACnet Device Instance Number and an overview of a Numbering System Example scenario. BACK TO MENU

NETWORK VARIABLES Topic 2
LONWORKS NETWORK VARIABLES Topic 2 BACK TO MENU

Network Variables NVO NVI
Network Variables allow a controller to send and receive data over the network to and from other devices. A network variable is any data item such as a temperature, an actuator position, a switch’s setting that a device’s application program expects to receive from another networked device (Network Variable Input or NVI), or expects to make available to other networked devices (Network Variable Output or NVO). NVO NVI I expect somebody wants my data. I’m expecting to receive some data. BACK TO MENU

Network Variable Types
The data transmitted in network variables are specifically formatted as to their content and structure according to their type. Common data types have been defined by LonMark International such as: Standard Configuration Property Types SCPTs Standard Network Variable Types SNVTs Application programs can use non-standard types such as: User Network Variable Types (UNVTs) User Configuration Property Types (UCPTs) The number and type of NVOs/NVIs, Configuration Properties Components (CPs), and Configuration Properties (NCIs) are defined in the device’s functional profile. BACK TO MENU

Standard Network Variable Types (SNVTs)
Network variable block inputs and outputs displayed change based on the SNVT type you choose. This is based on the Echelon standard for network variables. BACK TO MENU

SNVT Examples With Index Numbers
BACK TO MENU

Each SNVT type has a common input which is the FanInNumber and the 5 following common outputs: TypeIndex FanInCount Update Com Failure Subnet and Node Id The SNVT type that has been selected in the Change Type window is shown at the bottom of the block.      BACK TO MENU

The Change Type window provides all the SNVT types that can be assigned to the block. It is typically used when there is a need to modify the variable type before creating a binding. Set the associated NVO on the other controller(s) to the same SNVT variable type. BACK TO MENU

Network Variable Binding
Binding is a process of one-way or two-way communication (depending on the type) between a sender (NVO) and receiver (NVI) to send an updated value and/or mode. The NVO initiates the communication by sending an updated current value and/or mode to the NVI. For NVOs, this method can be used for medium- to large-scale networks since, generally, updates are sent only when the value and/or mode of the internal point changes in accordance to the MaxSendTime and MinSendTime values defined in the controller. BACK TO MENU

NVO NVI MAX SEND TIME MAX RECEIVE TIME Max Receive Time – The max time period between received updates of the NV on the network. The Max Receive Time value sets a time-out for values that are not updated regularly, thus flagging a communication failure. On a Max Receive Time failure, the NV will go into alarm and the NVI will return to its default value. If using fan-in, for each fan-in value, the Max Receive time is rounded up to the next highest minute. BACK TO MENU

NVO NVI MAX SEND TIME MAX RECEIVE TIME Recommended setting: Max Receive Time = 2X Max Send Time (at least) BACK TO MENU

Bindings are made through a network management tool by configuring a device with the logical address of other devices on the network that are expecting a network variable. Once configured, the device creates and sends the appropriate packets to the bound devices. This creates a logical connection between a NVO in one device and a NVI in one or more devices. BACK TO MENU

Network Variable Binding Process
Linking a network variable from one controller to another. Compatible SNVT (ECgfx) Select Source (EC-Net-AX) Select Target (EC-Net-AX) Connect (EC-Net-AX) BACK TO MENU

Network Variable Binding Valid vs. Invalid Lon Binding
BACK TO MENU

Network Variable Binding NV Link Mark
Linking a network variable from one controller to another. NV Link Mark BACK TO MENU

Network Variable Binding Lon Link Manager
Linking a network variable from one controller to another. Lon Link Manager BACK TO MENU

Network Variable Bindings Fan-In vs. Fan-Out
An NVO can be bound to many NVIs to send values to many devices. This is called a fan out. In the same way, many NVOs can be bound to one NVI. This is a fan in. For example, a fan in is useful for a roof top unit to calculate the terminal load of all VAV boxes. BACK TO MENU

Network Variable Binding Types
One-to-One Acknowledged Controller A NVO Controller B NVI Many-to-One (FAN-IN) Unacknowledged Controller A NVO Controller B Controller C NVI Repeated One-to-Many (FAN-OUT) Controller A NVO Controller B NVI Controller C BACK TO MENU

Network Variable Binding – Service Types
STANDARD (unacknowledged) Least reliable, most often used. Default for a Niagara-AX binding. Used for highest level of network performance. Message is sent ONCE and no response is expected. RELIABLE (unacknowledged/ repeated) Recommended for messaging classified as important – if there is a need to know if status has changed. Sends a message 3 times. CRITICAL (acknowledged) Target device must acknowledge receipt of the message. Message is sent until Source device acknowledges receipt. Limited to number of Critical bindings due to strain on the network. AUTHENTICATED Reserved for secure messaging. The Source device must identify itself to the Target device, and vice versa. POLL ONLY Will only poll the internal point. These can be set in the Lon Link Manager in EC-NET-AX. BACK TO MENU

Lon Link Manager Link Descriptors Link Service Types can be configured either in the Lon Link Manager for each set of structured network variables OR in the Edit dialog box for each proxy point brought into the station database. Repeat Timer Retries Receive Timer Transmit Timer BACK TO MENU

Link types can also be specified on each proxy point in the Edit dialog box. BACK TO MENU

Network Variable Polling
Polling is a method to monitor or write to Network Variables. In a periodic fashion, as specified by the polling rate, the browser will request and display the value of a network variable. This is useful when the network variable value is constantly changing. Polling can create unnecessary network traffic if the network variable value rarely changes. This can be mitigated by reducing the polling rate. BACK TO MENU

Network Variable Inputs (NVIs)
Compatibility with NVOs Must match SNVT type # of nviFPxx (free programmable) 35 (changeable SNVTs) Interface with any NVO up to … 31 bytes Fan-In (many-to-one) support All 35 NVIs Up to 256 fan-ins Configurations Max Receive Time Persistence AX Support SNVTs only (no UNVTs) Structured SNVTs BACK TO MENU

nvi Fan-In Support All 35 changeable NVIs support the many- to-one (Fan-in) bindings. The table of values is dynamically created. The calculations are not made by the nvi block - an additional program is required to compile the typical desired values like: Highest, Lowest, Average, Sum, etc The use of the For Loop block is recommended for such a program. Some example are available from Distech Controls Code Library. BACK TO MENU

Fan-In: Maximum Bindings
The maximum number of network fan-in is limited by two factors: A network variable can support a maximum of 255 bindings for the NVI fan in input. The controller has reserved 10,000 bytes of memory for fan-in. The amount of memory that each fan-in NVI uses can be calculated as follows: NVI Size (# of bytes) + 3 bytes * # of bindings per Fan-In NVIs For example, if you want to use 35 fan-in NVIs on a controller, each being 4 bytes, the maximum number of bindings for the NVI can be calculated as follows: 10,000 bytes / (NVI Size (4 bytes) + 3 bytes) * 35 Fan-In NVIs = 40 bindings max for the Fan-In NVI BACK TO MENU

Example: For Loop – Fan-In
Fan In Count - number of fan in values available in the fan in table – used as the Stop Index for the For Loop Number - the number of Network Value block instances supported by a controller For Loop block - executes code created on the associated programming sheet a pre-determined number of times as set by the StartIndex and StopIndex at each controller scan cycle. BACK TO MENU

Example: For Loop – Key Blocks
BACK TO MENU

Example: For Loop – Fan-In
Loop Number: Provides the status of the For Loop. Each time the loop completes, the index is increased by 1. Generic NV: Used to provide access to any instance of a Network Variable Input block through the Number input. Is Null: Determines if the input is null Between: Sets the range for valid values for all calculations. BACK TO MENU

Changeable Network Variables Comparison Among ECL Models
NV types: Changeable Type – 31 bytes, SNVTs are changeable Non-changeable type Changeable Network Variables

Network Variable Outputs (NVOs)
Compatibility with NVIs Must match SNVT type # of nvoFPxx (free programmable) 35 (changeable SNVTs) Interface with any NVI up to … 31 bytes Configurations Max Send Time Persistence AX Support SNVTs only (no UNVTs) Structured SNVTs BACK TO MENU

NVO NVI Network Variables SNVT types MUST match. NVs must be: LINKED
SNVT_temp_p SNVT_temp_p NVs must be: LINKED NV Link Manager (AX) BOUND Lon Link Manager (AX) BACK TO MENU

Network Variables – Structured
NVOs are available in a structured format to optimize network traffic and are implemented as follows: Variable Type # of Blocks # NVs Structured NVs Boolean 1 to 248 2 nvoVb01_124 nvoVb125_248 Enum 1 to 54 nvoVe01_27 nvoVe28_54 Numeric 1 to 56 8 nvoVn01_07, nvoVn08_14 nvoVn15_21, nvoVn22_28 nvoVn29_35, nvoVn36_42 nvoVn43_49, nvoVn50_56 Gfx controllers have 8 or more types of internal points that are stored in structured network points. See the specific controller’s functional profile in the datasheet for the details of supported NCIs, NVIs and NVOs. BACK TO MENU

HWIs/HWOs as Network Variables
For each HWI, there is an associated nvoHwIn to make the HWI value available on the network. For each HWO, there is an associated nviHwOut and nvoHwOut to make the HWO value available on the network. Hardware Input Hardware Output nvoHwInput nviHwOutput nvoHwOutput BACK TO MENU

The nvoHwIn and nvoHwOut can be found as structured objects under the Program Lonmark object under each Lon controller in AX (or Lonwatcher). BACK TO MENU

Specific nvos can be found under each HwIn Lonmark object under each Lon controller in AX (or Lonwatcher). BACK TO MENU

Constants vs. Variables
Constants are blocks that are mostly used to configure set values (setpoints, delays, limits, etc.) that may need to be made available to a Px graphic. Variables are blocks that are mostly used to monitor changing values or calculate new values using old ones that may need to be made available to a Px graphic. BACK TO MENU

Constants Available in 1 structured configuration property and implemented as an NCI. The user can read or write the values of the Boolean Constant blocks 1 to 124 directly through this configuration property. Available in 2 structured configuration properties and implemented as NCIs. The user can read or write the values of the Enum Constant blocks 1 to 31 and 32 to 62 directly through this configuration property. Available in 8 structured configuration properties and implemented as NCIs. Can read or write the values of the Numeric Constant blocks 1 to 7, 8 to 14, 15 to 21, 22 to 28, 29 to 35, 36 to 42, 43 to 49, and 50 to 56 directly through this configuration property. BACK TO MENU

Network Constant Inputs (NCIs)
Available in structured configuration properties and implemented as NCIs as follows: Constant Type # of Blocks # CPs Structured NCIs Boolean Constant 1 to 248 1 nciCb01_248 Enum Constant 1 to 62 2 nciCe01_31, nciCe32_62 Numeric Constant 1 to 56 8 nciCn01_07, nciCn08_14 nciCn15_21, nciCn22_28 nciCn29_35, nciCn36_42 nciCn43_49, nciCn50_56 Gfx controllers have 8 or more types of internal points that are stored in structured network points. See the specific controller’s functional profile in the datasheet for the details of supported NCIs, NVIs and NVOs. BACK TO MENU

Constants vs. Variables – Example
The Internal Constant blocks set the OAT limits, which are not required to change. The Numeric Value blocks set the SAT min and max values, which can be changed through a browser-based graphic over the network. The Linear block then creates a linear interpolation based on these min and max values and the Limit block sets the values received from the Numeric Value blocks as OAT limits. The Hardware Input block sends the value of the OAT and the SAT Setpoint is calculated and outputted by the Limit block to the Numeric Value block where it can be monitored by a browser-based graphic over the network. BACK TO MENU

LABWORK – SAMPLE PROJECT OVERVIEW Topic 3
LONWORKS LABWORK – SAMPLE PROJECT OVERVIEW Topic 3 BACK TO MENU

Lab 7: Building a Multi-Sheet Project Overview
LAB 7 – 3 hrs 45 min Multi-Sheet AHU Project OVERVIEW 3:45:00 This section will provide an overview of the AHU Multi-Sheet Project BEFORE starting the project. There a total of 7 programming sheets. This project is a SIMULATION – therefore, values and setpoints must be manipulated to view system changes. The project will use pre-existing code called “Gap Solutions” available in the Student Files provided requiring you to fill in the gaps with custom blocks, links, correct formats and setpoints. BACK TO MENU

Lab 7: Building a Multi-Sheet Project Overview - Project Sections
PROGRAMMING SHEETS Hardware Inputs & Outputs Network Variable Inputs & Outputs Supply Air Temp Setpoint Reset Heat-Cool Control Fan Control Alarming System Monitoring (optional) BACK TO MENU

LAB 7-1: 65 min Unit Startup Sheet A: Hardware I/Os Sheet B: Network I/Os LAB 7-2: 30 min Supply Air Temp (SAT) Setpoint Reset Sheet C: SAT Setpoint Reset (with custom block (C1) LAB 7-3: 15 min Econo (Free) Cooling Mode Sheet D3 (Custom Block) – Part of Sheet D BACK TO MENU

LAB 7-4: 60 min AHU Operation Mode Sheet D: Heat/Cool LAB 7-5: 35 min Fan Speed Control Sheet E: Fans LAB min Alarming Sheet F: Alarms LAB min System Monitoring Sheet G: System Monitoring (optional) BACK TO MENU

LAB 7-1: 65 min Unit Startup Sheet A: Hardware I/Os Sheet B: Network I/Os Hardware I/Os Network Variable I/Os BACK TO MENU BACK TO SECTIONS

LAB 7-2: 30 min Supply Air Temp (SAT) Setpoint Reset Sheet C: SAT Setpoint Reset The SAT setpoint is dynamically being re-calculated based on: A set of High, Med and Low “anchor” setpoints Demand Average (from the VAV Terminal Load Fan-In) – which is being calculated from the For Loop block on the NVI/NVO programming (Sheet B) to be passed to SAT Setpoint Reset (Sheet C) Current HVAC mode (Heat or Cool) BACK TO MENU BACK TO SECTIONS

7-2: SAT Setpoint Reset BACK TO MENU BACK TO SECTIONS

7-2: SAT Setpoint Reset A single custom block (C1) is being used to encapsulate the heat-cool Linear resetting blocks, Switch block and Equal block. BACK TO MENU BACK TO SECTIONS

7-2: SAT Setpoint Reset - Reset Custom Block (C1)
Equal – converts HVAC mode of Cool (3) to Cool (0) Switch – switches back and forth from ON (if input is not 0) to allow SAT reset in Cool mode, to OFF to allow SAT reset in Heat mode Linear – performs a proportional (linear) resetting of SAT setpoint based on anchor setpoints – 2 for Cool, 2 for Heat – with one setpoint shared by both BACK TO MENU BACK TO SECTIONS

LAB 7-3: 15 min Econo (Free) Cooling Mode Sheet D3 (Custom Block) – Part of Sheet D Part of Sheet D – Heat/Cool Control as a custom block (D3) Inputs are converted to Enthalpy (measure of a system’s internal energy) OAT OAH RAT RAH Atmospheric pressure Output is measured in BTU/LB. BACK TO MENU BACK TO SECTIONS

7-3: Econo (Free) Cooling Mode
BACK TO MENU BACK TO SECTIONS

7-3: Econo (Free) Cooling Mode - Custom Block (D3)
Use of Hysteresis Use of Enthalpy BACK TO MENU BACK TO SECTIONS

7-3: Econo (Free) Cooling Mode
The output of this section feeds: The Enable port of a staging block – to “stage” Econo cooling (stage 1) and cooling from the Cool PID output (stage 2) A Switch block that switches to stage 2 (On port) cooling when Econo Cooling mode is 1, and to Cool PID output (Off port) when Econo Cooling mode is 0. BACK TO MENU BACK TO SECTIONS

LAB 7-4: 60 min AHU Operation Mode Sheet D: Heat/Cool OA Damper adjustment based on Fan Speed and Heat mode Staging of OA Damper and Cooling Valve Mode switching: Econo-Cool mode vs. Cooling mode control HVAC mode determination Fan Speed comparison (Supply vs. Return Fan) 6 custom blocks (D1, D2, D3, D4, D5, D6) BACK TO MENU BACK TO SECTIONS

7-4: AHU Operation Mode BACK TO MENU BACK TO SECTIONS

7-4: AHU Operation Mode - Fan Speed / OA Damper Limits
BACK TO MENU BACK TO SECTIONS

7-4: AHU Operation Mode BACK TO MENU BACK TO SECTIONS

7-4: AHU Operation Mode The outputs of this section feed:
OA Dampers HWO (Sheet A) Cooling Valve HWO (Sheet A) HVAC Mode NVO (Sheet B) SAT Setpoint Dual Reset (Sheet C) Heating Valve HWO (Sheet A) Alarms (Sheet F) System Monitoring (Sheet G) BACK TO MENU BACK TO SECTIONS

LAB 7-5: 35 min Fan Speed Control Sheet E: Fans Adjustment of Fan speed using PID loop based on maintaining Duct Static Pressure at 1.5 in H2O Ramping up of Fan speed over 120 second period Setting of Fan speed limits 1 custom block (E1) BACK TO MENU BACK TO SECTIONS

7-5: Fan Speed Control BACK TO MENU BACK TO SECTIONS

7-5: Fan Speed Control The outputs of this section feed:
OA Damper position reset (Sheet D) Supply/Return Fan VFD NVOs (Sheet B) BACK TO MENU BACK TO SECTIONS

LAB min Alarming Sheet F: Alarms Provides alarm indications on the Supply/Return Fans for the following: Fan Run Fault – fans are required to be ON but are OFF Fan Stop Fault – fans are required to be OFF but are ON Provides alarm indications for the following: SAT high or low – 3.5 degrees F OAT/OAH values in fault condition Heating/Cooling disabled Spare Uses a single NVO with a snvt_states (embedded in a custom block) to provide 16 individual alarm states. BACK TO MENU BACK TO SECTIONS

7-6: Alarming BACK TO MENU BACK TO SECTIONS

LAB min System Monitoring Sheet G: System Monitoring (optional) OPTIONAL SHEET to provide centralized / organized monitoring for selected project values. Collection of Reference Targets and Monitor blocks Must have reciprocal Reference Hubs scattered throughout project to allow flow onto this programming sheet. BACK TO MENU BACK TO SECTIONS

7-7: System Monitoring BACK TO MENU BACK TO SECTIONS

BACK TO LONWORKS MENU (CLICK HERE)

BEGIN THE AHU LAB AHU LAB
It’s time to begin Lab 7, Building a Multi-Sheet (AHU) Project using a Lon controller. Remember, the focus of this lab is not on the LonWorks protocol. It is mostly focused on building a multi-sheet project using pre-existing code. For Lon or BACnet, the best practices and processes similar, with a few differences depending on the protocol. AHU LAB Click the arrow below to start.

AHU LAB BEGIN THE AHU LAB
REALLY, THAT’S IT! On to the lab. Just click the arrow below. AHU LAB

BEGIN THE AHU LAB CLICK THE ARROW!! WHAT ARE YOU TRYING TO PULL?
Are you STILL monkeying around in this PPT when you could be getting some honest hands-on practice? CLICK THE ARROW!!

THE AHU LAB 3:45:00

LONWORKS Topics: 1 – Network Requirements 2 – Network Variables

Similar presentations

Presentation on theme: "LONWORKS Topics: 1 – Network Requirements 2 – Network Variables"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

LONWORKS Topics: 1 – Network Requirements 2 – Network Variables

Similar presentations

Presentation on theme: "LONWORKS Topics: 1 – Network Requirements 2 – Network Variables"— Presentation transcript:

Similar presentations

About project

Feedback