CentraLine LYNX TOOL User Guide

Copyright © 2010 Honeywell GmbH All Rights Reserved EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

Table of Contents
About CentraLine LYNX 3
What’s new?......................................................................................................... 3
Abbreviations ....................................................................................................... 3
Domain Dictionary................................................................................................ 4
Scenarios ............................................................................................................. 4

Getting Started 5
Installation ............................................................................................................ 5
Migration .............................................................................................................. 7

Programming CentraLine LYNX 9

Downloading Application Logic ............................................................................ 9
Updating Modules ................................................................................................ 10
Error View on LonLYNX device............................................................................ 10
Error View on BacnetLYNX device....................................................................... 11
ControlProgram Details View ............................................................................... 13
Controller Summary View .................................................................................... 13
ControlProgram NV Configuration View............................................................... 14
Viewing the List of Network Variables .................................................................. 14
Group as NV ........................................................................................................ 15
Bacnet Object Configuration View ....................................................................... 15
Viewing the List of Bacnet Objects....................................................................... 15
ControlProgram Wiresheet View.......................................................................... 16
Designing The Application Logic.......................................................................... 16
ControlProgram Resource Usage View ............................................................... 17
ControlProgram Resource Usage ........................................................................ 17
ControlProgram Terminal Assignment View......................................................... 17
Macro Details View .............................................................................................. 18
Macro Resource Usage View............................................................................... 18
Macro Wiresheet View ......................................................................................... 18
Application Details View....................................................................................... 19
Application Programming View ............................................................................ 19
Application Resource Usage View ....................................................................... 19
Application NV Configuration View ...................................................................... 19
Viewing the List of Network Variables .................................................................. 20
Application Bacnet Object Configuration View..................................................... 20
Viewing the List of Bacnet Objects....................................................................... 20
Actions on BacnetLYNX explained....................................................................... 21

Physical Points 23
Binary Inputs ........................................................................................................ 23
Binary Outputs ..................................................................................................... 25
Modulating Inputs................................................................................................. 27
Modulating Outputs .............................................................................................. 31

Software Points 35
Constants ............................................................................................................. 35
Network Inputs ..................................................................................................... 37
Network Setpoints ................................................................................................ 38
Network Outputs .................................................................................................. 40

Editing Software Points 43

Network Input ....................................................................................................... 43
Network Setpoint.................................................................................................. 43
Constant............................................................................................................... 44
Network Output .................................................................................................... 44

Network Variables 45
Viewing the List of Network Variables .................................................................. 45
Group NVs ........................................................................................................... 46
Network Variable Input ......................................................................................... 47
Network Configuration Input ................................................................................ 50
Many To One NV.................................................................................................. 54
Network Variable Output ...................................................................................... 55
Edit Network Variables ......................................................................................... 59

EN2Z-0960GE51 R0710 2
 CENTRALINE LYNX TOOL - USER GUIDE

Invalid Points........................................................................................................ 63

Bacnet Objects 64
Viewing the List of Bacnet Objects ...................................................................... 65
Object Input ......................................................................................................... 65
Object Setpoint .................................................................................................... 66
Object Output....................................................................................................... 68
Edit Objects.......................................................................................................... 69

BindingS or Data Sharing 72

Binding Lon Devices ............................................................................................ 72
Binding Bacnet Devices ....................................................................................... 72
About Bacnet Link Manager ................................................................................ 73
Add Bindings........................................................................................................ 74
Binding HAWK and LYNX .................................................................................... 75

Flow Calibration 76
Pre-requisites....................................................................................................... 76
Procedure ............................................................................................................ 76

Function Blocks 78
Add Device .......................................................................................................... 78
Add Function Block .............................................................................................. 78
Configure Function Block..................................................................................... 78
Delete Function Block .......................................................................................... 78

Analog Function Blocks 79

Analog Latch ........................................................................................................ 79
Average................................................................................................................ 81
Compare .............................................................................................................. 82
Encode................................................................................................................. 82
Hysteretic Relay................................................................................................... 86
Maximum ............................................................................................................. 87
Minimum .............................................................................................................. 88
Priority Select....................................................................................................... 89
Select ................................................................................................................... 91
Switch .................................................................................................................. 92

Built In Function Blocks 93

Schedule .............................................................................................................. 93
Conventional Wall Module ................................................................................... 95
SBus wall module ................................................................................................ 96
Configuring S-Bus wall module............................................................................ 97

Control Function Blocks 114

AIA ....................................................................................................................... 114
Cycler................................................................................................................... 116
Cycler Functionality.............................................................................................. 117
Stager Functionality ............................................................................................. 118
Flow Control......................................................................................................... 119
PID ....................................................................................................................... 121
Rate Limit............................................................................................................. 123
Stager................................................................................................................... 124
Cycler Functionality.............................................................................................. 125
Stager Functionality ............................................................................................. 126
Stage Driver ......................................................................................................... 127

Data Function Blocks 130

Counter ................................................................................................................ 132
Override ............................................................................................................... 134
Priority Override ................................................................................................... 135
Runtime Accumulate............................................................................................ 137

Logic Function Blocks 139

AND ..................................................................................................................... 139
Oneshot .............................................................................................................. 140
OR ....................................................................................................................... 142
XOR ..................................................................................................................... 143

3 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

Math Function Blocks 144

Add....................................................................................................................... 144
Digital Filter .......................................................................................................... 145
Divide ................................................................................................................... 146
Enthalpy ............................................................................................................... 147
Exponential .......................................................................................................... 148
Flow Velocity ........................................................................................................ 149
Limit ..................................................................................................................... 150
Multiply................................................................................................................. 151
Ratio..................................................................................................................... 152
Reset.................................................................................................................... 154
Square Root ......................................................................................................... 156
Subtract................................................................................................................ 157

Zone Arbitration Function Blocks 158

General Set Point Calculator ............................................................................... 158
Occupancy Arbitrator ........................................................................................... 161
Set Temperature Mode ........................................................................................ 165
Temperature Set Point Calculator ........................................................................ 169

Pass Thru 174

Calibrate sensors 175

Pre-requisites ....................................................................................................... 175

Diagnose Outputs 176

Pre requisites ....................................................................................................... 176
Diagnose Outputs for a Lon Device ..................................................................... 176
Diagnose Outputs for a Bacnet Device ................................................................ 177

Macros 178

LYNX Library 179

Open LYNX Library .............................................................................................. 180
Close LYNX Library.............................................................................................. 180
Add Items to LYNX Library................................................................................... 180
Saving Library Items ............................................................................................ 181
Load Library Item ................................................................................................. 182
Delete Library items ............................................................................................. 183
Export Library Items............................................................................................. 184
Import items to Library ......................................................................................... 184
LYNX Library Applications.................................................................................... 184

Modes of Operation 188

Accessing Different Modes .................................................................................. 188

Engineering Mode 189

Online Debugging Mode 190

Force Values 208

Actions ................................................................................................................. 209

Select Points to Debug 210

Simulation 211
Example Scenario................................................................................................ 213

Simulation Settings 228

Time Simulation ................................................................................................... 228
Continuous Simulation ......................................................................................... 228
Step Simulation .................................................................................................... 228
Force Values ........................................................................................................ 229
Actions ................................................................................................................. 231
Select Points to Display in Simulation Log Window ............................................. 231

Generate XIF File 233

EN2Z-0960GE51 R0710 4
 CENTRALINE LYNX TOOL - USER GUIDE

Order Of Execution 234

Custom Palette File 235

Create Custom Palette File.................................................................................. 235
Add Items to Custom Palette File ........................................................................ 236
Close Custom Palette File ................................................................................... 236
Add Device to Custom Palette File ...................................................................... 236

Device Icons 237

Lon Icons ............................................................................................................. 237
Bacnet Icons ........................................................................................................ 237
Device Icons in Library......................................................................................... 237

Virtual Offline Discovery 238

5 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

ABOUT CENTRALINE LYNX

This document serves as a guide to configure and use the 1. Set up BacnetLYNX controllers on the network
CentraLine LYNX Tool. The CentraLine LYNX Tool is an add- 2. Create applications to program the controller
on module to the existing Niagara framework modules. It 3. Simulate the applications you have created
provides a graphical environment to program CentraLine 4. Download the configuration to the controller
LYNX Controllers. 5. Debug the applications
It provides the following features: 6. Set up offline data sharing links and download to the
controllers
• Graphical environment to program a CentraLine LYNX 7. Perform online operations like sensor calibration, Con-
controller troller diagnostics, flow balancing, and so on.
• Libraries of function blocks to create an application logic
• Calibration of inputs, and diagnostics of outputs
• Offline simulation The Lon models, LYNX II and LYNX Micro support configuring
• Online debugging the S-Bus (Sylk-Bus) wall module (2-wire wall module) in
addition to the conventional wall module (7-wire). You can
connect the Kingfisher wall module to the controller, use the
What’s new? LYNX tool to configure it by using the S-Bus wall module
The Lon LYNX II, LYNX Micro, and BacnetLYNX models function block, save the changes, and download it to the
support 200 function blocks. Also, the LYNX II and LYNX LonLYNX controller. The BacnetLYNX models are configured
Micro models support 220 Network Variables. with an SBus wall module.
LonLYNX models include: You can upload the changes made in the settings on the wall
module display, to the LYNX controller using the tool. You can
LYNX II models: also simulate the S-Bus wall module logic using the
• CLLYVL6436AS Simulation feature. The S-Bus wall module configuration can
• CLLYVL6438NS be stored in the LYNX library and can be reused across
• CLLYUL6438S applications.
The Quick Download allows you to download only the
LYNX Micro models: changed configuration to the database.
• CLLYVL4024NS The following function blocks have the Ignore invalid input
• CLLYVL4022AS parameter to specify behavior of invalid inputs:
• CLLYUL4024S • Minimum
• CLLYUL1012S • Maximum
• CLLYVL0000AS • Average
• Add
BacnetLYNX models include: • Multiply
• CLLYVB6436AS • Divide
• CLLYVB6438NS • Subtract
• CLLYUB6438S • Ratio
The tool now supports LonLYNX Micro models. With this option, you can configure the function block to ignore
any invalid inputs, and consider only the valid inputs to
You can configure the physical inputs of a Micro model to be
calculate the output. If this option is left selected, the invalid
used as Pulse Meter or Counter types or Momentary type
inputs make the output also invalid.
binary inputs.
Support of Bacnet LYNX device is major enhancement in the
tool. Abbreviations
The following sequence of operations can be performed on a • NRE: Niagara Runtime Environment
Bacnet LYNX controller. • JVM: Java Virtual Machine
• NV: Network Variable

EN2Z-0960GE51 R0710 6
 CENTRALINE LYNX TOOL - USER GUIDE

Domain Dictionary Scenarios

1. Fox: This is Tridium’s proprietary protocol for communi- The CentraLine LYNX Tool provides the programming
cation between workbench and the station. environment for the CentraLine LYNX controllers. It is
2. Host: The host is a hardware platform or computer on developed with using Niagara AX framework developed by
which the Niagara software runs. Niagara can run on a Tridium and runs in the Niagara Runtime environment.
computer or a HAWK controller. The CentraLine LYNX Tool can be used to program the LYNX
3. Station: The Niagara station is a JVM that hosts the run- controller in the following two ways:
ning of objects.
4. Commission: This is the process of downloading the • Through HAWK
application (program logic + network image) to the Cen- HAWK controller bundles the software capability of the
traLine LYNX controller. framework in a hardware platform. HAWKs connect to system
5. Functional blocks: Functional blocks are the atomic pro- field buses on the other end and provide real time control
gram objects that define a specific function. functions. CentraLine LYNX Tool can be hosted on a
6. Macros: Macros are a set of functional blocks that computer loaded with Niagara AX framework as well as
define a specific functionality. HAWK. HAWK is loaded with the framework, the station
7. Wiresheet: Wiresheet is the view in the Niagara work- database, and all the modules available in the computer. The
bench that allows you to drag and drop functional blocks CentraLine LYNX Tool communicates with the CentraLine
and macros to define application logic. LYNX controller through HAWK. HAWK is connected to the
8. Programming environment/Graphical environment: A same LAN as the PC and communicates to the CentraLine
wiresheet view that allows you to define your application LYNX Tool on Fox Protocol (on LAN). On the other end, it
logic for the CentraLine LYNX controller. communicates to the CentraLine LYNX controller on the Lon
9. Application: An Application is a group of function blocks bus.
that are interconnected to form control logic. This appli- The workbench in the computer also communicates with the
cation is then downloaded to the controller to run the HAWK by dialing into the onboard modem of the HAWK.
control logic in the controller. However, this can be a slow connection.
• Through Engineering computer
In this case, the Niagara AX framework runs on the computer.
The computer connects to the system field buses directly
through the appropriate network interface. This is the soft
HAWK option.
The CentraLine LYNX Tool can be hosted on a computer
loaded with Niagara AX framework. The station database
resides on the same computer and connects to the
CentraLine LYNX controller on the Lon Network using the
PCLTA/PCMCIA card or through SLTA.
Station databases are typically engineered on the engineering
computer (this is called Offline Mode), then installed to a
HAWK and its associated Web Supervisor computer, if any.

7 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

GETTING STARTED
Installation 1. Depending on the flavor of the tool being installed, copy
the dist file and the corresponding batch file to any
This release contains three flavours of the LYNX tool: folder in your PC. The following is the list of available
• Lon and Bacnet dist files and their corresponding batch files.
• Lon only — dist_PC_Lon_Bacnet_LYNX.dist;
• Bacnet only PC_Split_Installer_Lon_Bacnet.bat1
— dist_PC_Bacnet_LYNX.dist;
Installing LYNX tool in Soft HAWK - Manual Copy PC_Split_Installer_Bacnet.bat1
— dist_PC_Lon_LYNX.dist; PC_Split_Installer_Lon.bat1
Method 2. Locate a file with extension .bat1 in installation of a
1. Stop any stations that are running and close the work- given flavor of the tool and rename it to .bat extension.
bench. 3. Double-click on the batch file(.bat file). This opens the
2. Delete following modules, if they are present, from the command prompt prompting for Niagara Home Path.
Modules folder in NiagaraHome. For example: C:\Cen- 4. Type the folder path where Niagara is installed in your
traLine\CoachAX -3.3.22\modules PC. For example, D:\CentraLine\CoachAX -3.4.43. The
• wsStdLonDeviceTemplates.jar installer then prompts for Niagara Platform Credentials.
• wsStdBACNetDevTemplates.jar 5. Type the User Name and Password to connect to the
• wsLonChannel.jar Niagara Platform. 
• wsBacnetChannel.jar After the Platform authentication succeeds, the dist file
3. Browse to the location of the required flavor of the tool installer proceeds to install the required modules. Once
and copy the jar files present in that folder to your Nia- the installation is complete, a confirmation message is
garaHome\modules folder. displayed on the console.
4. Restart the station and the workbench. 6. Press any key to close the console.

Installing LYNX tool in Soft HAWK - Installer EXE NOTE: Existing applications created with earlier versions of
the tool need to be migrated using LYNX Migration
Method tool to be compatible with the current version of the
1. Install Java Runtime Environment (JRE) v1.6 on your tool.
system, if not installed already as the installer program
requires JRE 1.6.
2. Stop all running stations and close the workbench.
Upgrading Hard HAWK
Close any other application accessing the jar files from You must stop the station running on the HAWK and start the
the NiagaraHome\modules folder. workbench before you start upgrading the hard HAWK.
3. Browse to the location of the release folder of the 1. Select one of the following dist files.
required tool flavor. For example: if Lon + BACnet flavor — dist_HAWK_Bacnet_LYNX.dist
of the tool has to be installed, locate the folder <release- — dist_HAWK_Lon_Bacnet_LYNX.dist
Folder>\PC\Lon_Bacnet. — dist_HAWK_Lon_LYNX.dist
4. You will find the Installer file called Lynx_ LonBacnetIn- 2. Run the file using Niagara Platform’s Distribution File
staller<versionNo>.exe. Installer option. The Distribution File Installer installs
5. Double click the installer executable file. the required modules in the HAWK.
6. End User License Agreement screen appears, accept
the agreement. NOTE: Existing applications created with earlier versions of
7. An installation screen appears. The installer detects the the tool need to be migrated using LYNX Migration
current NiagaraHome path and displays it on the tool to be compatible with the current version of the
screen. If there are more than one Niagara versions tool.
installed, the installer picks the higher version. You can
change the path to install the jar files using the Browse After installing the new tool version in the HAWK, you can
button next to the CoachAX Home option. migrate the existing LYNX applications in the HAWK using the
8. Click Install for the Installer to start the Installation. The following procedure.
installer installs the required jar files in the Niagara mod- 1. Copy the station running in the HAWK to your local PC
ules folder. As the installation proceeds, the installation using the Station Copier option available in the Plat-
status is displayed. After the installation is complete, form options of the HAWK.
Install Status text in the screen changes to Installation 2. Migrate the copied HAWK station using the LYNX
complete and the progress bar indicates 100% comple- Migration tool.
tion. 3. Copy the migrated station back to the HAWK using the
9. Please see the Installation instructions section in the Station Copier option and restart the HAWK.
SRB for more details on the installation procedure.
Launching the Workbench
Upgrading Soft HAWK • Click Start > Programs > Niagara > Workbench to launch
You must stop all stations running on your PC and close the the workbench.
workbench before upgrading the soft HAWK.

EN2Z-0960GE51 R0710 8
 CENTRALINE LYNX TOOL - USER GUIDE

Adding New Station 3. Select bacnet from the list if available and click OK. 
On the Workbench: or 
Click Browse and select the location this folder is
1. Click Tools > New Station. The New Station Wizard stored and click OK.
appears. 4. Expand Config in the Nav palette to display Drivers.
2. Type the Station Name. 5. Select BacnetNetwork from the Palette and drag it on
3. The Station Directory path is updated with the name Drivers in the Nav palette.
you just entered and displays the location where the 6. Type a name for the BACnet Network you are adding
files are stored. Click Next. and click OK.
4. Type a password in the Admin Password field. 7. Expand Drivers and verify to see that the BACnet Net-
5. Re-type the same password in the Admin Password work is added.
Confirm field.
6. Click Finish to complete adding a station. The station is
added and the Property Sheet of the station is dis- Adding a Controller
played on the right portion of your screen. To add a CentraLine LYNX controller:
1. Click the Open Palette button on the Palette. The
Starting the Station Open Palette dialog box appears.
1. On the Nav palette, click Platform. The Authentication 2. Select CentraLineLYNXTool from the list if available
dialog box appears. and click OK.
or 
NOTE: If the Nav palette is not visible on the left pane, from Click Browse and select the location this folder is
the Menu bar, select Window > Sidebars > Nav to stored and click OK.
display the Nav palette. 3. Select LonLYNX from the Palette and drag it on Lon
Network under Drivers in the Nav palette.
2. Type the User Name, Password, and click OK. The or
right portion of your screen displays a list of object Select BacnetLYNX from the Palette and drag it on
names and their description. BacnetNetwork under Drivers in the Nav palette.
3. Double-click Application Director. The list of available 4. Type a name for the device you are adding and click
stations appears. OK.
4. Select the station you have added and click Start. The Expand the Lon Network or Bacnet Network and verify
station you have added appears in the Nav palette to see that the device is added.
under Platform.
5. Double-click the Station option on the Nav palette. The Viewing/Modifying Controller Summary Details
Authentication dialog box appears. To view or modify the summary details of the LonLYNX
6. Type the User Name and Password and click OK. The controller:
Station you have added is launched and the Station
1. Double-click the device name in the Nav palette to dis-
Summary Property view appears on the right portion of
play the Controller Summary View on the right portion
your screen.
of your screen.
Device Name is an editable field.
Adding a Network 2. Click the drop-down menu to select a Device Model
To add a Lon Network: from the list.
1. Click Windows > Side Bars > Palette to add the pal- 3. Select Enable Daylight Savings option and specify the
ette named Palette if it is not visible on the left pane. following information when the day light savings must
2. Click the Open Palette button on the Palette. The come into effect:
Open Palette dialog box appears. — Start Month
3. Select Lonworks from the list if available and click OK. — End Month
or  — Start Day
Click Browse and select the location this folder is — End Day
stored and click OK. 4. Click Save to save the changes made to the Controller
4. Expand Config in the Nav palette to display Drivers. Summary View.
5. Select LonNetwork from the Palette and drag it on To view or modify the summary details of the BacnetLYNX
Drivers in the Nav palette. controller:
6. Type a name for the Lon Network you are adding and 1. Double-click the device name in the Nav palette to dis-
click OK. play the Controller Summary View on the right portion of
Expand Drivers and verify to see that the Lon Network your screen. 
is added. Device Name is an editable field.
2. Click the drop-down menu to select a Device Model
To add a BACnet Network: from the list.
3. Click the Set button to change the Global Update Rate.
1. Click Windows > Side Bars > Palette to add the pal-
ette named Palette if it is not visible on the left pane. NOTES: Setting the Global Update Rate changes all the indi-
2. Click the Open Palette button on the Palette. The vidual update rates including the update rates for
Open Palette dialog box appears. Network Input points, Analog Outputs, Binary Out-
puts that are enabled for Fail Detect. Global Update
Rate has a default value of 60 seconds. The value
can range from 0-3600 seconds.

9 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

4. LYNXClick the Set button to change the Global Send 4. Select the controller from the list and click Discover.
Heart Beat. The device appears under Discovered on the top por-
tion of the screen.
NOTES: Global Send Heart Beat is set at the device level 5. Select the controller under Discovered and click Add to
and the changes made to this value is applied auto- add the controller.
matically to all the objects. Global Send Heart Beat 6. Click OK.
has a default value of 60 seconds. The value can 7. Click Match to match the neuron id of the field controller
range from 0-3600 seconds. with the device in station.
5. Select Enable Daylight Savings option and specify the 8. Select the new model you are migrating to in the Con-
following information when the day light savings must troller Summary View (right-click device in the Nav
come into effect: palette and choose Views > Controller Summary
— Start Month View).
— End Month 9. Load an application from the LYNX library.
— Start Day 10. Download the configuration to the new LYNX Micro con-
— End Day troller model by right-clicking the device and selecting
6. Click Save to save the changes made to the Controller Actions > Download.
Summary View.
You can use Bacnet LYNX in one of the following ways.
Migration • Create a new application in the BacnetLYNX controller.
• Convert an existing Lon Application to corresponding
Bacnet application.
From LYNX II to LYNX Micro
If you want to migrate from any of the earlier LonLYNX To create a Bacnet LYNX application:
models, that is, LYNX II (CLLYVL6436AS, CLLYVL6438NS, or
CLLYUL6438S) to the latest Lon models supported by LYNX, 1. Drag a BacnetLYNX device to the station under a Bac-
that is LYNX Micro (CLLYVL4024NS, CLLYVL4022AS, net Network.
CLLYUL4024S, CLLYUL1012S, or CLLYVL0000AS), do the 2. Double-click the device you have added and right-click
following: on it to choose Views > Controller Summary View.
3. Select a model from the list.
1. Replace the existing LYNX controller in the field (could 4. Browse to the ControlProgram of the BacnetLYNX
be any one of the LYNX II models) with the new LYNX device.
Micro controller. 5. Drag the required objects from CentraLineLYNXTool
2. Right-click the Lon network in the Nav palette of the palette and create an application.
LYNX tool. 6. Browse to Bacnet Device Manager view on Bacnet
3. Select Views > Lon Device Manager. The list of con- Network and discover the online Bacnet LYNX devices.
trollers is displayed on the right portion of the screen. 7. Match the device in Niagara to appropriate discovered
4. Select the controller from the list and click Discover. device.
The device appears under Discovered on the top por-
tion of the screen. NOTE: Alternately, instead of creating an application you
5. Select the controller under Discovered and click Add to can load a suitable application from LYNX library or
add the controller. from Standard Applications Library in palette.
6. Click OK.
7. Click Match to match the neuron id of the field controller 8. Download the configuration to the online device using
with the device in station. Download option on the device.
8. Select the new model you are migrating to in the Con-
troller Summary View (right-click device in the Nav
palette and choose Views > Controller Summary To use an existing Lon Application in a BacnetLYNX device:
View). 1. Drag a BacnetLYNX device to the station under a Bac-
9. Load an application from the LYNX library. net Network.
10. Download the configuration to the new LYNX Micro con- 2. Double-click the device you have added and right-click
troller model by right-clicking the device and selecting on it to choose Views > Controller Summary View.
Actions > Download. 3. Select a model from the list.
4. Browse to the ControlProgram of the BacnetLYNX
device.
From LonLYNX to BacnetLYNX 5. Drag an existing Lon Application from LYNX Library to
If you want to migrate from any of the LonLYNX models (LYNX the Control Program under the BacnetLYNX device.
II, or LYNX Micro) to the Bacnet models (CLLYVB6436AS, The tool automatically creates a Bacnet interface for the
CLLYVB6438NS, or CLLYUB6438S) supported by LYNX, do Lon application. (If it is an application in library, the tool
the following: would have automatically created the Bacnet interface
1. Replace the existing LonLYNX controller in the field in library). Review the Bacnet interface that the tool has
(could be any one of the LYNX II or LYNX Micro models) created and make necessary changes, if any.
with the new BacnetLYNX controller. 6. Browse to Bacnet Device Manager view on Bacnet
2. Right-click the Bacnet network in the Nav palette of the Network and discover the online Bacnet LYNX devices.
LYNX tool. 7. Match the device in Niagara to appropriate discovered
3. Select Views > Bacnet Device Manager. The list of device
controllers is displayed on the right portion of the 8. Download the configuration to the online device using
screen. Download option on the device.

EN2Z-0960GE51 R0710 10
 CENTRALINE LYNX TOOL - USER GUIDE

From Conventional wall module to SBus wall module 9. Download the configuration to the new LYNX controller
If you want to replace the existing conventional wall module model.
(T7770) with the SBus wall module, do the following: 10. Replace the existing wall module model to any one of
the SBus wall module models (same as hardware
1. Replace the existing LYNX controller in the field with a attached).
new LYNX Micro or BacnetLYNX controller. 11. Drag the ConventionalWallModule function block from
2. Right-click the Lon or Bacnet network in the Nav palette the Palette onto the wiresheet of the controller.
of the LYNX tool. 12. Right-click the conventional wall module block and
3. Select Views > Lon Device Manager or Bacnet select Configure Properties. The General Settings
Device Manager. The list of controllers is displayed on dialog box appears.
the right portion of the screen. 13. Select LCD Display under Model Options on the dia-
4. Select the controller from the list and click Discover. log box. This changes the wall module selection from
The device appears under Discovered on the top por- Conventional to S-Bus wall module.
tion of the screen. 14. Make appropriate links in the wire sheet of the applica-
5. Select the controller under Discovered and click Add to tion logic where the wall module is being used.
add the controller. 15. Download the configuration to the controller.
6. Click OK.
7. Click Match to match the neuron id of the field controller NOTE: Make sure that the SBusWallModule should be
with the device in station. assigned the same address using rotatory Address
8. Select the new model you are migrating to in the Con- switch as defined in the SBus wall module function
troller Summary View (right-click device in the Nav block in Station.
palette and choose Views > Controller Summary).

11 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

PROGRAMMING CENTRALINE LYNX

The CentraLine LYNX Tool offers a graphical environment to • Application: This includes macros and logic that you can
program the CentraLine LYNX controller. You can use the define and use in applications.
wiresheet view in the Engineering Mode to use Physical • StandardApplications: Standard applications shipped by
points, Software points, and function blocks to build an CentraLine which you can use to build application logic
application in the ControlProgram. The Physical points, You can drag any of these items on to the wiresheet of a
Software points, and function blocks can be accessed using ControlProgram in its Engineering Mode and make the
the Palette. You can drag these items on to the wiresheet and connections between Physical points, Software points, and
connect them, based on your need, to develop your function blocks to create a ControlProgram or an Application.
application logic. The logic that you create can then be stored Use this wiresheet view to drag the Physical points and
in a LYNX Library for reuse. Once you are satisfied with the Function blocks to build your application logic. You can save a
logic you have created, you can download the same to the logic you created to be used later and also share it with other
controller. The logic thus created can be tested for users.You can build several applications and store them in a
correctness using the Simulation and Online Debugging LYNX Library along with CentraLine supplied standard
modes. applications.
NOTE: Changing NCI values, configuration of a Schedule
block, or Daylight savings option, puts the application Downloading Application Logic
in a quick download pending state. As long as the After you have created your application logic and tested the
application has been downloaded at least once to logic using the simulation feature, you can download the
the controller, these changes only trigger a quick application logic to the controller. To download the application
download to the controller. logic:
Use the ControlProgram option to program the CentraLine 1. On the Nav palette, right-click the device and select
LYNX tool. To do this: Actions > Download. The Download dialog box
appears.
• Expand LonLYNX or BacnetLYNX in the Nav palette and 2. Select True under Full Download for a full download or
double-click ControlProgram to display the Wiresheet False for a quick download.
view.
• Display the Palette (From the Menu bar, select Window > NOTE: A Quick Download only downloads the modified
Sidebars > Palette to display the Palette). items from a previous download where as with a Full
The Palette appears on the left pane with the following items: Download the entire configuration is downloaded to
• LonLYNX: This is a device that you can drag on to the the controller replacing the existing configuration.
LonNetwork in the Nav palette to create a new device. However, if changes have been made to the SBus
wall module by an operator/tenant locally from the
NOTE: You cannot drop this on to the wiresheet of any display on the wall module, and a full download is
macro or ControlProgram or Application. performed, LYNX tool downloads the entire configu-
ration to the controller except the SBus wall module
• BacnetLYNX: This is a device that you can drag on to the configuration. This is done to avoid losing any
BacnetNetwork in the Nav palette to create a new device. changes made locally on the SBus wall module dur-
ing a download operation.
NOTE: You cannot drop this on to the wiresheet of any
macro or ControlProgram or Application. 3. Click OK. The application logic is downloaded to the
controller based on your selection.
Physical Points: Modulating and Binary Inputs or Outputs.
SoftwarePoints: Use this to create Network Input, Network NOTE: Make sure that if you are using the SBus wall module
Setpoints, or Network Output. or the ignore invalid option for function block, the
models selected are LonLYNX II, LYNX Micro, or
• Analog: Analog function blocks BacnetLYNX. SBus wall module cannot be down-
• Logic: Logic function blocks loaded to the LonLYNX I models.
• Math: Math function blocks
• Control: Control function blocks When using LYNX II, LYNX Micro, or BacnetLYNX models, if
• DataFunction: Data Function function blocks you modify SBus wall module settings from the display in the
• ZoneArbitration: Zone Arbitration function blocks wall module, you can also upload the same configuration into
• BuiltIn: BuiltIn function blocks the LYNX tool.
• Macro: A Macro is a group of functional blocks grouped
together that define a specific functionality. Commonly
used program elements can be defined as macros so that
they could be reused across applications.

EN2Z-0960GE51 R0710 12
 CENTRALINE LYNX TOOL - USER GUIDE

Updating Modules There are 6 categories of alarms:

Follow this procedure to install updates of Standard Alarm Type Description
Applications. This is the StandardApps.jar file you will receive Sensor Alarms Generated for all sensors configured in
that you will need to install to begin using the latest Standard the logic. All input blocks assigned to pins
Applications provided. UI0 to UI6 are listed in this category.
1. Connect to the platform of the station.
Invalid Occurs if there is an error in the
2. Navigate to File transfer Client and transfer the Stan-
Configuration configuration that was downloaded.
dardApps.jar file from the local drive to the modules
Alarms
folder of the Station.
3. Restart the workbench/webworkbench. Network Occur ONLY for NVIs and Object Inputs
4. Expand StandardApplications in the LYNX palette. Communication configured as fail detect. The network
The latest Standard Applications are displayed. Alarms variable or object input names are listed in
this category. In the LonLYNX I and LYNX
II models, you may define upto 32 input
Error View on LonLYNX device network variables with fail detect.
This view displays all the alarms generated by the CentraLine On detection of an alarm condition, the
LYNX controller. There are 6 categories of alarms: LonLYNX I and LYNX II models fill a
• Sensor Alarms: These alarms are generated for all the number between 16 and 47.
Sensors configured in the logic. All input blocks assigned In the LYNX Micro models, you may
to pins UI0 to UI6 are listed in this category. define upto 150 input network variables
• Invalid ConfigurationAlarms: This alarm occurs if there is with fail detect. LYNX Micro models fill a
an error in the configuration that was downloaded. number between 48 and 197.
• Network Communication Alarms: These alarms occur Control Alarms All the alarm blocks configured in the logic
ONLY for NVIs and Object inputs configured as fail detect. are listed in this category. If an alarm block
The network variable names are listed in this category. does not have any incoming link then the
• Control Alarms: All the alarm blocks configured in the status is always NORMAL. You may
logic are listed in this category. If an alarm block does not define upto 32 alarm function blocks in
have any incoming link then the status is always NORMAL. LonLYNX I, LYNX II, and LYNX Micro
• S-BUS WM Communication Alarm: These alarm occur models.
when the communication link between the On detection of an alarm condition, the
SbusWallModule and the controller are lost. LonLYNX I and LYNX II models fill a
• S-BUS WM Fail Detect Alarms:These alarms occurs for number between 48 and 79.
the linked outputs of the SBusWallmodule.All the linked LYNX Micro models fill a number between
outputs are listed in this category. 16 and 47.
S-BUS WM These alarms occur when there is a
NOTE: The S-BUS WM Communication Alarm and the S- Communication communication break between the device
BUS WM Fail Detect Alarms are shown only for: Alarm and the wall module.
— LYNX II models: CLLYVL6436AS, S-BUS WM Fail Shown only for LonLYNX II and LYNX
CLLYVL6438NS, CLLYUL6438S Detect Alarms Micro models. These alarms occur for the
— LYNX Micro models: CLLYVL4024NS, linked outputs of the SBusWallmodule. All
CLLYVL4022AS, CLLYUL4024S, CLLYUL1012S, the linked outputs are listed in this
CLLYVL0000AS category. In the LonLYNX II models, you
To view the Alarms View of a controller, right-click the Device may define upto 168 alarm function
Name in the Nav palette and select Views > Alarms View. blocks.
The Alarms view is displayed on the right half of the screen. On detection of an alarm condition, the
The Alarms view is static and you must refresh the view to get LonLYNX II models fill a number between
the latest update. 80 and 247.
In the LYNX Micro models, you may
define upto 50 alarm function blocks.
nvoError LYNX Micro models fill a number between
The CentraLine LYNX tool provides a multi-byte network 198 and 247.
variable, nvoError, which indicates errors. You can access the
nvoError map on the Property Sheet view of the controller. NOTE: It is not necessary that two consecutive bits are filled
The nvoError map consists of 10 fields of one byte each. As during two consecutive alarm conditions. The tool
each byte is 8 bits long, there are a maximum of 80 bits that allocates any bit position within the specified range.
are used to indicate errors. Each bit is mapped to an alarm. For example, in case of S-Bus WM Fail Detect
Alarms in LYNX Micro, it is not necessary that the bit
position 198 is filled and then 199 and so on. Centra-
Line LYNX allocates any bit position between 198
and 247.Similarly is the case for all the models in
Network Communication Alarms, Control Alarms,
and S-Bus WM Fail Detect Alarms.

13 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

To view the Alarms View of a controller, right-click the Device The range and bit positions differ for LonLYNX Micro. The
Name in the Nav palette and select Views > Alarms View. following table indicates the bit positions for the Control
The Alarms view is displayed on the right half of the screen. Alarms, Network Communication Alarms, and S-Bus WM Fail
The Alarms view is static and you must refresh the view to get Detect Alarms.
the latest update.
Bit
The following table indicates the bit positions and the alarms Position Alarm Type Description
they are used to represent:
16-47 Control The alarm function block reporting
Bit Alarm the alarm represented by this bit.
Position Alarm Type Description
48-197 Network The input network variable
0-7 Sensor Alarm Indicates error condition on Communicati represented by this bit is not being
Modulating inputs or on Alarm received within the fail detect time.
outputs.
198-247 S-BUS WM The output of the S-Bus
0 Sensor Alarm The on-board pressure Fail Detect Wallmodule represented by this bit
sensor is open or shorted. Alarms is not being received within the fail
1 Sensor Alarm Universal Input 1 exceeds detect time.
the user defined range, that
is, it is open or shorted. NOTE: UI 0 is displayed only for models that support UI 0. UI
7 is not shown on the Alarms View.
2 Sensor Alarm Universal Input 2 exceeds
the user defined range
3 Sensor Alarm Universal Input 3 exceeds Error View on BacnetLYNX device
the user defined range This view displays all the errors generated by the CentraLine
4 Sensor Alarm Universal Input 4 exceeds LYNX controller. There are 6 categories of errors:
the user defined range • Sensor Alarms: These errors are generated for all the
5 Sensor Alarm Universal Input 5 exceeds Sensors configured in the logic. All input blocks assigned
the user defined range to pins UI0 to UI6 are listed in this category.
• Invalid Configuration Alarm: This alarm occurs if there is
6 Sensor Alarm Universal Input 6 exceeds an error in the configuration that was downloaded.
the user defined range • Network Communication Alarms: These errors occur
7 Sensor Alarm Universal Input 7 exceeds ONLY for object inputs configured as fail detect. The object
the user defined range names are listed in this category.
• Control Alarms: All the alarm blocks configured in the
8-14 No mapping The on-board thermistor is logic are listed in this category. If an alarm block does not
open or shorted have any incoming link then the status is always NORMAL.
15 Invalid The configuration • S-BUS WM Communication Alarm: These alarm occur
Configuration Alarm downloaded to the controller when the communication link between the
is illegal. One or more file SbusWallModule and the controller are lost.
sections have a CRC error • S-BUS WM Fail Detect Alarms: These alarms occurs for
16-47 Network The input network variable the linked outputs of the SBusWallmodule.All the linked
Communication represented by this bit is not outputs are listed in this category.
Alarm being received within the fail
detect time To view the Error View of a controller, right-click the Device
Name in the Nav palette and select Views > Error View. The
48-79 Control Alarm The alarm function block Error view is displayed on the right half of the screen. This
reporting the alarm view is static and you must refresh the view to get the latest
represented by this bit. update.
80-247 S-BUS WM Fail The output of the S-Bus
Detect Alarms Wallmodule represented by
this bit is not being received
within the fail detect time.

EN2Z-0960GE51 R0710 14
 CENTRALINE LYNX TOOL - USER GUIDE

Error Objects The following table indicates the bit positions and the alarms
The CentraLine LYNX tool provides 248 error bits which they are used to represent:
indicates errors. LYNX Bacnet supports the 16 error objects, Bit
AV_Error0 to AV_Error15. Each error object is 16-bit long Position Alarm Type Description
except for the 16th Error Object(AV_Error15) which is 8-bit
long. 0 Sensor Alarm The on-board pressure
sensor is open or shorted.
To access the error objects:
1 Sensor Alarm Universal Input 1 exceeds
1. Expand the Bacnet device on the Nav sidebar. the user defined range, that
2. Right-click Points and select Bacnet LYNX Point Man- is, it is open or shorted.
ager.
3. The Point Manager view appears on the right pane. 2 Sensor Alarm Universal Input 2 exceeds
4. Click the Discover button to discover all the points on the user defined range
the device. 3 Sensor Alarm Universal Input 3 exceeds
5. The points are listed under Discovered on the screen. the user defined range
6. Click the Add button to add the points to the database.
There are 6 categories of alarms: 4 Sensor Alarm Universal Input 4 exceeds
the user defined range
Alarm Type Description 5 Sensor Alarm Universal Input 5 exceeds
Sensor Alarms Generated for all sensors configured in the user defined range
the logic. All input blocks assigned to pins 6 Sensor Alarm Universal Input 6 exceeds
UI0 to UI6 are listed in this category. the user defined range
On detection of an error on modulating
inputs, the Bacnet LYNX models fill a 7 Sensor Alarm Universal Input 7 exceeds
number between 0 and 7. the user defined range
Invalid Occurs if there is an error in the 8 Invalid The configuration
Configuration configuration that was downloaded. Configuration Alarm downloaded to the controller
Alarms is illegal. One or more file
sections have a CRC error
Control Alarms All the alarm blocks configured in the logic
are listed in this category. If an alarm block 9 S-BUS WM The input to the S-Bus
does not have any incoming link then the Communication Wallmodule represented by
status is always NORMAL.You may define Alarm this bit is not being received
up to 32 input objects with fail detect. from the controller output
On detection of an error condition, the 10-15 No mapping The on-board thermistor is
BacnetLYNX models fill a number open or shorted
between 16 and 47.
16-47 Control Alarm The alarm function block
Network Occur ONLY for object inputs configured reporting the alarm
Communication as fail detect. The network variable or represented by this bit.
Alarms object input names are listed in this
category.You may define up to 32 alarm 48-197 Network The input network variable
function blocks. Communication represented by this bit is not
On detection of an error condition, the Alarm being received within the fail
BacnetLYNX models fill a number detect time.
between 48 and 197. 198-247 S-BUS WM Fail The output of the S-Bus
S-BUS WM These alarms occur when there is a Detect Alarms Wallmodule represented by
Communication communication break between the device this bit is not being received
Alarm and the wall module. within the fail detect time.

S-BUS WM Fail These alarms occur for the linked outputs NOTE: UI 0 is displayed only for models that support UI 0. UI
Detect Alarms of the SBusWallmodule. All the linked 7 is not shown on the Alarms View.
outputs are listed in this category. You
may define up to 168 alarm function
blocks.
On detection of an alarm condition, the
BacnetLYNX models fill a number
between 198 and 247.
To view the Error View of a controller, right-click the Device
Name in the Nav palette and select Views > Error View. The
Error view is displayed on the right half of the screen. This
view is static and you must refresh the view to get the latest
update.

15 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

ControlProgram Details View

This view provides details of the ControlProgram, Application A check mark appears against the feature that is selected
or the Macro for which it is selected. It displays details such as from the list. To use the Flow Balancing View, the feature Air
the Name, Version number, and a brief description. Balance Supported must be selected under VAV Zone
Terminal Single Duct Application type.
To access the Details View of the controller:
To override the reheat valve and peripheral heat valve values,
1. On the Nav palette, browse to Station > Config > Driv- select the features Reheat Valve Override Supported and
ers> LonNetwork > LonLYNX. Peripheral Heat Valve Override Supported under VAV Zone
or  Terminal Single Duct Application type. The option to
Browse to Station > Config > Drivers> BacnetNet- override the values of reheat valve and peripheral heat valve
work > BacnetLYNX. is enabled in the Flow Balancing View.
2. Right-click ControlProgram and select Views > Details.
The following fields appear: — Version: The version number.
— Name: The name you specified for the ControlPro- — Description: A brief description of the application.
gram while creating it. It is non editable. Use this field to briefly describe the purpose of this
— Type: Indicates the air conditioning type used. You ControlProgram.
can select one of the following options from the list.
Application Type Controller Summary View
General application Use this view to view or modify Device Name, Device Model,
and select the period when day light savings are in effect. To
VAV Zone Terminal Single Duct Application view or modify the summary details of the controller:
CVAHU Single Duct Application 1. Double-click the device name in the Nav palette to dis-
VAV Zone Terminal Double Duct Application play the Controller Summary View on the right of your
screen. 
VAV Zone Flow Tracking Application Device Name is an editable field.
Water Source Heat Pump AHU Application 2. Select a Device Model.
Unit Vent AHU Application Lon Controller
One of the following Lon models can be selected:
FCU Application
LYNX II models:
CVAHU Double Duct Application
• CLLYVL6436AS
VAV AHU Single Duct Application • CLLYVL6438NS
VAV AHU Double Duct Application • CLLYUL6438S
Multi Zone AHU Application
LYNX Micro models:
CZS (Rapid Zone) AHU Application
• CLLYVL4024NS
CZS Zone Terminal Application • CLLYVL4022AS
• CLLYUL4024S
NOTE: Exercise caution while changing the Type as it could • CLLYUL1012S
modify the application. • CLLYVL0000AS

— Features: It provides the features of the selected Bacnet Controller

application type. The following features are available
for selection when the application type chosen is VAV a. One of the following Bacnet models can be
Zone Terminal Single Duct Application. selected:
• CLLYVB6436AS
• CLLYVB6438NS
Features • CLLYUB6438S
Air Balance Supported
Reheat Valve Override Supported b. Click the Set button to set the Global Update
Rate.
Peripheral Heat Valve Override Supported
Serial Fan speed Supported
Fan Override Supported
Series Fan
Parallel Fan

EN2Z-0960GE51 R0710 16
 CENTRALINE LYNX TOOL - USER GUIDE

Global Send Heartbeat is set at the device level. Update and LYNX Micro models, and BacnetLYNX models
Rate is the time period for which the controller waits for an support SBus wall module and the Model Description
update from the source object. The Set button can be used for these models indicates the same.
to globally set the update rate for all objects in the control
program logic. Although, any new object added to the
control program would have the default update rate. ControlProgram NV Configuration View
(a)On clicking the Set button, the Set Global A Network Variable (NV) is a data item such as a temperature,
Update Rate dialog box appears. a switch value or actuator state. NVs can be thought of simply
(b)Type the Update Rate value. as point parameters. LonMark functional profiles define
(c)Click OK. Standard Network Variable Types (SNVTs), but additional
non-standard NVs are usually available, depending on the
NOTE: The default update rate value is 60 sec- device, to store additional non-standard data.
onds.The value can range from 0-3600 sec- There are three categories of NVs that the Lon LYNX
onds. supports. They are:
• Mandatory: Mandatory NVs are the default, mandatory
c. Click the Set button to set the Global Send Heart NVs present in a Lon LYNX device.
Beat. • Fixed: You can use Fixed Dropable NVs while creating an
Global Send Heartbeat is set at the device level. Update application logic but can edit only its Internal Data Type.
Rate is the time period for which the controller waits for an You can also display Fixed Dropable NVs on the wiresheet.
update from the source object. The Set button can be used • Custom: Custom NVs are the NVs you create while
to globally set the update rate for all objects in the control creating an application logic. They can be created, edited,
program logic. Although, any new object added to the and deleted based on your requirements.
control program would have the default update rate. The Lon LYNX provides the following four built-in functions
(a)On clicking the Set button, the Set Global that enable you to connect function blocks with other function
Update Rate dialog box appears. blocks.
(b)Type the Update Rate value. • NVI - Network Variable Inputs
(c)Click OK. • NVO - Network Variable Output
• NCI - Network Configuration Input
NOTE: The default update rate value is 60 sec- • Many to One NV - Many to One Network Variable
onds.The value can range from 0-3600 sec- The Lon LYNX provides built-in functions, Network Variable
onds. Inputs, to allow the selection of variables that are available
from/to the network. The configured network variables are
3. Select the Enable Daylight Savings option and specify mapped to the Function Block memory space to be used by
the following information when the day light savings any Function Block. Each Network variable may be configured
must come into effect: with a name.
— Start Month
— End Month
— Start Day Viewing the List of Network Variables
— End Day 1. Browse to Station > Config > Drivers > LonNetwork >
LonLYNX.
NOTE: You must clear the Day Light Savings check box and 2. Select ControlProgram > Views > NV Configuration
download it to the controller, for the controller to stop View. The summary page appears with a list of pre-pro-
using daylight savings. grammed Mandatory, Fixed, and Custom NVs in a
tabular format. The table has the following columns:
4. Click Save to save the changes or Cancel to revert to — NV Name: The name of the network variable.
the previous settings. — Type: Indicates if the NV is of type NVI, NVO, NCI or
Many to One NV.
NOTE: You are free to select any device model even if the — Category: Indicates if the NV is Mandatory, Fixed, or
application created does not fit the memory require- Custom.
ments of the target model. CentraLine LYNX per- — NV Container: Indicates where the NV is used.
forms necessary actions on model change and gives 3. You have options to:
a report of the same. — Show on wiresheet as points -
— Add NV
NOTE: The LonLYNX I models do not support the SBus Wall — Edit NV
module. On selecting any of these models, the — Delete NV
Model Description indicates that the selected model
does not support SBus wall module. The the LYNX II,

17 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

4. The bottom half of the NV Configuration view displays

the software points available on the wiresheet in a tabu-
Bacnet Object Configuration View
lar format. The table has the following columns: An Object is a data item such as a temperature, a switch value
— Point Name: The name of the network point (Network or actuator state. Objects can be thought of as point
Input/Network Setpoint/Network Output) as it appears parameters.
on the wiresheet. The three categories of Objects supported by BacnetLYNX
— Field Names: Indicates if the NV is of type NVI, NVO, are:
NCI or Many to One NV. • Mandatory: Mandatory Objects are the default Objects
— Point Container: Indicates where the software point is present compulsorily in a Bacnet LYNX device.
used. All software points that are used in a Program • Fixed: Fixed Dropable Objects can be used while creating
within an application are also listed. an application logic and only its Internal Data Type can be
5. You have options to: edited. Fixed Dropable Objects can also be displayed on
— Group as NV the wiresheet.
— Edit Point • Custom: Custom Objects are the objects that are created
— Remove points from wiresheet while creating an application logic. They can be created,
edited, and deleted based on your requirements.
Group as NV
The Bacnet LYNX supports the following object types.
You can group points belonging to types NVI, NCI, NVO,
Constants, and Invalid points to form a new NVI, NCI, or NVO. AVI - Analog Value Input
• AVO - Analog Value Output
NOTE: Use the CTRL key to select multiple points to group. • AV Setpoint - Analog Value Setpoint
This button is disabled in the following cases: • BVI - Binary Value Input
• BVO - Binary Value Output
— If one or more selected points belong to a Fixed NV. • BV Setpoint - BinaryValue Setpoint
— If one or more selected points belong to a Many to • MVI - Multi-state Value Input
One NV. • MVO - Multi-state Value Output
— If one or more selected points is configured as Bit field. • MV Setpoint - Multi-state Value Setpoint
— If you select an input point and an output point.
— If the point belongs to nciTempSetpoints The configured objects are mapped to the Function Block
See the Add NVI, Add NCI, Add NVO, or Add Many to One memory space to be used by any Function Block. Each Object
NV topics for more details. is configured with a name.
NOTE:
Viewing the List of Bacnet Objects
— Mandatory NVs cannot be used in the application logic. 1. Browse to Station > Config > Drivers > BacnetNet-
— Mandatory NVs cannot be edited or deleted. work > BacnetLYNX.
— In a Fixed NV, only Internal Data Type can be modified. 2. Select ControlProgram > Views > Object Configuration
— Custom NV is the user defined NV. A Custom NV can be View. The summary page appears with a list of pre-pro-
edited or deleted. grammed Mandatory, Fixed, and Custom Objects in a
— Fixed NVs marked as Fixed_Dropable can be exposed on tabular format. The table has the following columns:
the wiresheet. Other fixed NVs cannot be exposed as — Name: The name of the object.
points. — Type: Indicates if the object is of type AVI, AVO, AV
— Network Input with Point Type configured as Constant in a Setpoint, BVI, BVO, BV Setpoint, MVI, MVO, or MV
macro are not shown in the lower pane of the NV Setpoint.
Configuration View. — Category: Indicates if the Object is Mandatory, Fixed,
— For each point that is copied and pasted on the wiresheet: or Custom.
— If the network type is a scalar SNVT, the new NV cre- — Object Container: Indicates where the Object is used.
ated is SNVT of the network type. — Object Instance: A unique number that is automati-
— If the network type is a Bit field, the new NV of SNVT cally assigned to the object.
type nearest to the selected internal data type is cre- — Update Rate: The rate at which inputs are sent to the
ated automatically. network.
— In all other cases, a single-field UNVT with the same — Send Heartbeat: The rate at which a Network object
configuration as the point being copied is created. value is sent to the network regardless of whether its
value is changed or not. The timeout value is equal to
the value entered in this field multiplied by 5. This
value should be configured as multiples of 5 only, else
tool rounds it off to the nearest multiple of 5 during
download.
3. You have options to:
— Show on wiresheet as points
— Add NV
— Edit NV
— Delete NV

EN2Z-0960GE51 R0710 18
 CENTRALINE LYNX TOOL - USER GUIDE

4. The bottom half of the Object Configuration view dis- 1. On the Nav palette, browse to Station > Config > Driv-
plays the physical and software points available on the ers > LonNetwork > LonLYNX.
wiresheet in a tabular format. The table has the follow- 2. Expand LonLYNX and select ControlProgram.
ing columns: 3. Right-click ControlProgram and select Views >
— Point Name: The name of the physical /software point Wiresheet.
as it appears on the wiresheet.
— Field Names: Indicates the Object type. To view the Wiresheet View of the Bacnet controller:
— Point Container: Indicates where the physical /soft-
ware point is used. All physical /software points that 1. On the Nav palette, browse to Station > Config > Driv-
are used in a Program within an application are also ers > BacnetNetwork > BacnetLYNX.
listed. 2. Expand BacnetLYNX and select ControlProgram.
5. You have options to: 3. Right-click ControlProgram and select Views >
— Create Bacnet Object from Point: Use this button to Wiresheet.
convert an invalid point into a valid Bacnet object.
— Edit Point: Select a point and click this button to edit The wiresheet is displayed on the right of the screen in the
its configuration. Engineering mode. The Wiresheet View consists of a
— Remove points from wiresheet: Use this button to wiresheet like appearance on the right pane. You can drag the
remove a point from the wiresheet. function blocks, Physical points, and NVs or Objects on to this
wiresheet and make the connections to and from Physical
NOTE: points and function blocks to build your logic on the wiresheet.
It also consists of fixed Physical points. It also consists of a
— Mandatory Objects cannot be used in the application logic. snapshot view of the entire wiresheet page on the top right
— Mandatory Objects cannot be edited or deleted. corner. This helps you to have an overview of the entire sheet
— In a Fixed Dropable Object, only Internal Data Type can be in cases where you have many function blocks/Physical points
modified. and so on.
— Custom Object is the user defined Object. A Custom
Object can be edited or deleted. NOTE: All the Fixed Physical points are visible on the Con-
— Fixed Objects marked as Fixed_Dropable can be exposed trolProgram Wiresheet view of the Controller.
on the wiresheet. Other fixed objects cannot be exposed
as points.
— Network Input with Point Type configured as Constant in a Designing The Application Logic
macro are not shown in the lower pane of the Object
Configuration View. NOTE: You can use the Windows mechanism of copy/paste/
cut to copy/delete Function blocks, NVs, and IOs on
the wiresheet
ControlProgram Wiresheet View
The Wiresheet View is that screen or view of the CentraLine To design your application:
LYNXTool interface that you use to engineer the tool. Function 1. Decide the Physical points
blocks, Physical points, and NVs or Objects are the building 2. Develop Sequence
blocks of the logic you can create and download to the 3. Decide the interface requirements for the open Lon con-
CentraLine LYNX controller. nection or with other Lon devices
You can create and build your own logic using function blocks 4. Develop software logic using modules or import the
or create ControlProgram and libraries or macros, using the modules that you want to use
Wiresheet view. On this view, you can drag the function 5. Interconnect Physical points to other modules and to the
blocks, Physical points, and NVs or Objects that you use to outside connections
build and define logic. This logic then forms a part of the 6. Test the logic through simulation
macros and LYNX libraries that you want to save and reuse. 7. Correct any changes to the design or modifications to
the Macros
NOTE: Names of Physical points must be unique. No two 8. Save Macros that you would want to reuse in a library
Physical points can have the same name. 9. Save your device in a library if you want to be able to
reuse it here or on other projects.
To view the Wiresheet View of the Lon controller:

19 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

ControlProgram Resource Usage View 7. Click the Memory usage details button to view details
of the different memory types. The Block Memory
The ControlProgram, LYNX libraries and macros you create Details tab displays memory usage details of the Func-
consume memory. The function blocks, Physical points and tion blocks, NVs or Objects, and Physical IOs used in
NVs or Objects have different memory usage. Some elements the device in a tabular format.
of a function block may use a Float RAM while some others
could be using memory in the Non-Volatile RAM.
The Resource Usage View provides details of the total Name Definition
memory and the used memory as a result of all the Block Name of the Function block, IO, or NV.
ControlProgram, LYNX libraries and macros you create.
Type Indicates the type of the Function block, IO, or
You can see the memory usage at different levels as NV.
described:
Float RAM Indicates the Float RAM usage of the Function
• ControlProgram Resource Usage block, IO, or NV.
• Application Resource Usage
• Macro Resource Usage Byte RAM Indicates the Byte RAM usage of the Function
• LYNX library Resource Usage block, IO, or NV.
Flash Indicates the Flash memory usage of the
NOTE: At each of these levels the memory used up by Function block, IO, or NV.
the entire application is shown. NV RAM Indicates the NV RAM usage of the Function
block, IO, or NV.
ControlProgram Resource Usage Valid Indicates if the point is valid/inavlid.
To view the Resource Usage View of the controller: Block Indicates the location of the Function block, IO,
1. On the Nav palette, browse to Station > Config > Driv- Container or NV.
ers > LonNetwork > LonLYNX. 8. Click the RAM Pool Usage Details tab to view the
or memory usage status of the controller. You can click the
Browse to Station > Config > Drivers > BacnetNet- Tabular View button to view the breakup of RAM pool
work > BacnetLYNX. usage details in a tabular format. Click the Tabular
2. Right-click LonLYNX or BacnetLYNX. View button to hide/display the tabular view.
or 9. Click the Validate button to find out the Error messages
Expand LonLYNX or BacnetLYNX and select Control- and Warning messages, if any, in a new window. Typi-
Program. Right-click ControlProgram. cally you will find messages pertaining to warnings,
3. Select Views > Resource Usage. The Controller errors and detailed report of invalid points, IOs, excess
Details appear on the right half of the screen. memory counters, excess NVs created, excess engi-
4. You can select the controller Device Model. This is the neering units configured and so on. Click OK to close
model number or make of the controller that you are the window.
programming using this tool. 10. Click Save if you have made any changes to the Con-
5. The Memory Usage chart graphically displays a bar troller Model for the changes to take effects.
chart of the total memory and used memory details. 
You can click the Tabular View button to view the
breakup of RAM pool usage in a tabular format. Click ControlProgram Terminal Assignment View
the Tabular View button to hide/display the tabular This view provides a layout of the physical arrangement of the
view. pins on the controller. Use this view to view or modify the
configuration of inputs or outputs of the selected controller.
NOTE: The upper limit range of total memory for Float RAM, According to the selected controller model, you can select
Byte RAM, Flash, Non Volatile RAM, and RAM pool which inputs or outputs must be assigned to the pins. The IO
is higher in case of LYNX Micro controllers. pins for LYNX II and LYNX Bacnet models are:
• Universal Inputs (UI) 1 to 6
6. The Blocks Usage table displays the number of Func-
• Digital Inputs (DI) 1 to 4
tion blocks, Network variables or Objects, and Physical
• Analog Outputs (AO) 1 to 3
IOs used at the device level. Physical IOs indicate the
• Digital Outputs (DO) 1 to 8
number of hardware pins used.

NOTE: The number of blocks supported by LonLYNX Micro The inputs or outputs you have used to build the application
is higher. They support 200 Function blocks, 220 logic along with invalid IO points are available as options for
Network Variables, and 21 Physical IOs. UI, DI, AO, and DO. You can choose the inputs or outputs that
are used to build the application logic, to be assigned to the
physical pins of the controller. You can choose invalid IOs and
reassign them to valid terminals.

NOTE: UI 0 and UI 7 for LYNX II and LYNX Bacnet models

are not shown on the Terminal Assignment View.

EN2Z-0960GE51 R0710 20
 CENTRALINE LYNX TOOL - USER GUIDE

Example: A report of all actions taken is generated.

Let us say you have used four Modulating Inputs named If the name of a custom NV or Object clashes with a fixed NV
Modulating Input 1, Modulating Input 2, Modulating Input 3, or Object name in the target model, CentraLine LYNX
Modulating Input 4 and two Binary Inputs named BinaryInput generates a new unique name for the custom NV or Object
1 and BinaryInput2. On the Terminal Assignment View, for and creates the new fixed NV or Object.
each Universal Input (UI 0 to 7), you have the option to
choose Modulating Inputs 1 to 4 or Binary Inputs 1 to 2.
The IO pins for LYNX Micro models are:
Macro Details View
This view provides details of the Macro. It displays details
• Universal Inputs (UI) 1 to 4 such as the Name, Type, Version number, and a brief
• Analog Outputs (AO) 1 and 2 description.
• Digital Outputs (DO) 1 to 4
To access the Details View of the macro:
The input pin UI1 is fixed for Pulse_Meter or Counter type 1. On the Nav palette, browse to Station > Config > Driv-
sensors, or Momentary type binary input. If the pin is not ers > LonNetwork > LonLYNX. 
available or is currently assigned to another point, the tool or
creates the point as an invalid point. Browse to Station > Config > Drivers > BacnetNet-
work > BacnetLYNX.
To view the Terminal Assignment View of the controller: 2. Expand ControlProgram and right-click Macro.
1. On the Nav palette, browse to Station > Config > Driv- 3. Select Views > Details. The following fields appear:
ers > LonNetwork > LonLYNX. — Name: The name you specified for the Program while
or creating it. It is non editable.
Browse to Station > Config > Drivers > BacnetNet- — Type: The type of Program. It is non editable.
work > BacnetLYNX. — Version: The version number. It is non editable.
2. Right-click LonLYNX or BacnetLYNX. — Description: A brief description of the macro. Use this
or field to briefly describe the purpose of this macro.
Expand LonLYNX or BacnetLYNX and select Control-
Program. Right-click ControlProgram.
3. Select Views > Terminal Assignment View. The view Macro Resource Usage View
appear on the right side of the screen. The ControlProgram, LYNX libraries and macros you create
4. Assign all the inputs and outputs and click Save to save consume memory. The function blocks, Physical points, and
the details or Reset to revert to the last saved changes. NVs or Objects have different memory usage. Some elements
of a function block may use a Float RAM while some others
NOTE: If you change the device model, the physical IOs could be using Non-Volatile RAM.
continue to retain the IO pins previously assigned The Resource Usage View provides details of the total
except in the following scenarios: memory and the used memory as a result of all the logic you
have used in creating the macro.
1. If a custom IO has been assigned a pin that is
fixed in the target model, CentraLineLYNX To view the Resource Usage View of the macro:
assigns a free pin, if available. If no free pin is 1. On the Nav palette, right-click the Macro and select
available, the IO becomes an invalid IO. Views > Resource Usage. The Resource Usage View
2. If there was a fixed pin assigned to a fixed IO in is displayed on the right of the screen.
the source model and is different in the target 2. The Memory Usage chart graphically displays a bar
model, CentraLine LYNX reassigns the fixed pin chart of the total memory and used memory details.
in the target model to that IO. But if the fixed pin is 3. The memory usage details of the different memory
already in use in the target model, CentraLine types is also displayed in a tabular format.
LYNX converts the IO to the nearest custom type
and reassigns a valid pin available. If there is no
valid pin available the IO becomes unassigned. Macro Wiresheet View
3. If the target model supports less number of IOs To view the Macro wiresheet:
than the source model, CentraLine LYNX unas- 1. On the Palette palette, expand Util to view the list of
signs the pins for the IOs that are in excess in the utility functions.
target model. 2. Right-click Macro and select Views > Wiresheet. The
4. If target model supports more number of IOs than Wiresheet is displayed on the right of the screen.
the source, CentraLine LYNX assigns available Use this screen to build your logic using Physical points
free pins to any invalid IOs present. and Function Blocks.
NOTE: The UI0 pin is not displayed on the Terminal Assign-
ment View.

21 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

Application Details View Application Resource Usage View

This view provides details of the Application. It displays details The application logic, LYNX libraries and macros you create
such as the Name, Type, Version number, and a brief consume memory. The function blocks, Physical points and
description. NVs / Objects have different memory usage. Some elements
To access the Details View of the Application: of a function block may use a Float RAM while some others
could be using Non-Volatile RAM.
1. On the Nav palette, browse to Station > Config > Driv-
ers > LonNetwork > LonLYNX.  The Resource Usage View provides details of the total
or memory and the used memory as a result of all the application
Browse to Station > Config > Drivers > BacnetNet- logic, LYNX libraries and macros you have used in creating
work > BacnetLYNX. the Program.
2. Expand ControlProgram and right-click Application. To view the Resource Usage View of the Program:
3. Select Views > Details. The following fields appear: 1. On the Nav palette, browse to Station > Config > Driv-
— Name: The name you specified for the Program while ers > LonNetwork > LonLYNX.
creating it. It is non editable. or
— Type: Indicates the type used. It is non-editable. Browse to Station > Config > Drivers > BacnetNet-
— Version: The version number. It is non editable. work > BacnetLYNX.
— Description: A brief description of the application. 2. Expand LonLYNX or BacnetLYNX and expand Con-
Use this field to briefly describe the purpose of this trolProgram.
Program. 3. Right-click ControlProgram and select Views >
Resource Usage. The Resource Details appear on
Application Programming View the right half of the screen.
4. The Controller Model is non editable. This is model
The Wiresheet View for the Sub Application that screen/view number or make of the controller that you are program-
of the CentraLine LYNXTool interface that you use to engineer ming using this tool.
the tool. You can create the Program by connecting function 5. The Memory Usage chart graphically displays a bar
blocks to network inputs/setpoints/outputs and physical chart of the total memory and used memory details.
inputs/outputs. 6. The memory usage details of the different memory
To view the Application Wiresheet view of the controller: types is also displayed in a tabular format.
1. On the Nav palette, browse to Station > Config > Driv-
ers > LonNetwork > LonLYNX.
or
Application NV Configuration View
Browse to Station > Config > Drivers > BacnetNet-
work > BacnetLYNX. NOTE: This screen displays only those NVs that are used in
2. Expand LonLYNX or BacnetLYNX and select Control- this Application.
Program.
3. Expand the ControlProgram and right-click the Appli- A Network Variable (NV) is a data item such as a temperature,
cation whose wiresheet you want to view and select a switch value or actuator state. NVs can be thought of simply
Views > Wiresheet. The wiresheet is displayed on the as point parameters. LonMark functional profiles define
right of the screen. Standard Network Variable Types (SNVTs), but additional
4. Use this screen to build your Program using Physical non-standard NVs are usually available, depending on the
points and Function Blocks. device, to store additional non-standard data.
There are three categories of NVs that the Lon LYNX
NOTE: supports. They are:
• Mandatory: Mandatory NVs are the default, mandatory
— If you drag an Application from the Nav palette on to NVs present in a Lon LYNX device.
the Wiresheet of an ControlProgram, Physical points • Fixed: You can use Fixed Dropable NVs while creating an
are not visible. application logic but can edit only its Internal Data Type.
— If you drag an Application from a library to the Control- You can also display Fixed Dropable NVs on the wiresheet.
Program’s Wiresheet View, Physical points are visible • Custom: Custom NVs are the NVs you create while
in the wiresheet of the Program and not on the Control creating an application logic. They can be created, edited,
Program Wiresheet View of the parent. and deleted based on your requirements.
— If you delete the Program, fixed Physical points appear The CentraLine LYNX Tool provides the following four built-in
in the Wiresheet View of the ControlProgram. functions that enable you to connect function blocks with other
function blocks.
• NVI: Network Variable Inputs
• NVO: Network Variable Output
• NCI: Network Configuration Input
• Many to One NV: Many to One Network Variable
The CentraLine LYNX Tool provides built-in functions,
Network Variable Inputs, to allow the selection of variables
that are available from/to the network. The configured network
variables are mapped to the Function Block memory space to
be used by any Function Block. Each Network variable may
be configured with a name.

EN2Z-0960GE51 R0710 22
 CENTRALINE LYNX TOOL - USER GUIDE

Viewing the List of Network Variables Application Bacnet Object Configuration

1. Browse to Station > Config > Drivers > LonNetwork >
LonLYNX.
View
2. Expand ControlProgram and right click Application
and select Views > NV Configuration View. The sum- NOTE: This screen displays only those Bacnet Objects that
mary page appears with a list of NVs used in the Pro- are used in this Application.
gram appears. The table has the following columns:
— NV Name: The name of the network variable. An Object is a data item such as a temperature, a switch value
— Type: Indicates if the NV is of type NVI, NVO, NCI or or actuator state. Objects can be thought of as point
Many to One NV. parameters.
— Category: Indicates if the NV is Mandatory, Fixed, or There are three categories of Objects that the BacnetLYNX
Custom. supports. They are:
— Display on WireSheet: Indicates if the NV will be dis- • Mandatory: Mandatory Objects are the default Objects
played on the wiresheet or not. present compulsorily in a Bacnet LYNX device.
3. You have options to: • Fixed: Fixed Dropable Objects can be used while creating
— Show on wiresheet as points an application logic and only its Internal Data Type can be
— Add NV edited. Fixed Dropable Objects can also be displayed on
— Edit NV the wiresheet.
— Delete NV • Custom: Custom Objects are the objects that are created
4. The bottom half of the NV Configuration view displays while creating an application logic. They can be created,
the software points available on the wiresheet in a tabu- edited, and deleted based on your requirements.
lar format.
The Bacnet LYNX supports the following object types.
The table has the following columns:
• AVI - Analog Value Input
• Point Name: The name of the software point (Network • AVO - Analog Value Output
Input/Network Setpoints/NetworkOutput) as it appears on • AV Setpoint - Analog Value Setpoint
the wiresheet. • BVI - Binary Value Input
• Field Names: Indicates if the NV is of type NVI, NVO, NCI • BVO - Binary Value Output
or Many to One NV. • BV Setpoint - BinaryValue Setpoint
• Point Container: Indicates where the software point is • MVI - Multi-state Value Input
used. • MVO - Multi-state Value Output
• MV Setpoint - Multi-state Value Setpoint
NOTE: The configured objects are mapped to the Function Block
memory space to be used by any Function Block. Each Object
— Mandatory NVs cannot be used in the application is configured with a name.
logic.
— Mandatory NVs cannot be edited or deleted.
— In a Fixed NV, only Internal Data Type can be Viewing the List of Bacnet Objects
modified. 1. Browse to Station > Config > Drivers > BacnetNet-
— Custom NV is the user defined NV. A Custom NV work > BacnetLYNX.
can be edited or deleted. 2. Expand ControlProgram and right-click Application
— Fixed NVs marked as Fixed_Dropable can be and select Views > Object Configuration View. The
exposed on the wiresheet. Other fixed NVs can- summary page appears with a list of Objects used in the
not be exposed as points. Program.
— For each point that is copied and pasted on the
wiresheet, a new NV of SNVT type nearest to the
The table has the following columns:
selected datatype is created automatically.
• Name: The name of the object.
• Type: Indicates if the object is of type AVI, AVO, AV
Setpoint, BVI, BVO, BV Setpoint, MVI, MVO, or MV
Setpoint.
• Category: Indicates if the Object is Mandatory, Fixed, or
Custom.
• Object Container: Indicates the location of the Object.
• Object Instance: A unique number that is automatically
assigned to the object.
• Update Rate: The rate at which inputs are sent to the
network.
• Send Heartbeat: The rate at which a Network object value
is sent to the network regardless of whether its value is
changed or not. The timeout value is equal to the value
entered in this field multiplied by 5. This value should be
configured as multiples of 5 only, else tool rounds it off to
the nearest multiple of 5 during download.
3. You have options to:
— Show on wiresheet as points

23 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

— Add NV Generate Network Objects

— Edit NV The Generate Network Objects action on device level creates
— Delete NV the object references from control program to create the
4. The bottom half of the Object Configuration view dis- binding between the objects. These Object references are
plays the software points available on the wiresheet in a listed and used in Add Bindings dialog to make the binding
tabular format. between the devices.
The table has the following columns:
The Input points object references are displayed in the Target
• Point Name: The name of the physical /software point as it details of Add Bindings dialog box.
appears on the wiresheet.
• Field Names: Indicates the Object type. The Output points object references are displayed on the
• Point Container: Indicates where the physical /software Source details of Add Bindings dialog box.
point is used. All physical /software points that are used in The Binary Output and Modulating Output points have 16
a Program within an application are also listed. priority input object references and an output object reference
on device level. The priority object references are displayed in
NOTE: Target details and output object reference are displayed in
Source details of Add Binding dialog box.
— Mandatory Objects cannot be used in the application On restarting the station the object references are removed
logic. from the device if it is not involved in binding.
— Mandatory Objects cannot be edited or deleted.
— In a Fixed Dropable Objects, only Internal Data Type
can be modified. Clear slots
— Custom Object is the user defined Object. A Custom The object references for binding are created using the
Object can be edited or deleted. Generate network objects action on the device level (refer
— Fixed Objects marked as Fixed_Dropable can be Generate network Objects action description).
exposed on the wiresheet. Other fixed objects cannot The Clear slots action is used to remove the object references
be exposed as points. that are not involved in binding.

Actions on BacnetLYNX explained Clear Bindings

The Clear Bindings action on device level removes the
binding information from the controller.
Download
The clear binding action changes the bound links to new
Perform this action to download the logic to the
Links. If the device is having the obsolete Links then the
ControlProgram of an online device. If there is no modification
obsolete links are removed from the controller. These can be
done to the logic from previous download to that controller
observed in Bacnet Link manager view (see Types of Link
apart from Setpoints value changes, Schedule block
Status section for more information).
configuration changes, Wall module block configuration
changes, Day Light Savings changes, tool performs a quick The clear binding action can be performed only in the
download of the configuration. following conditions:
• Device should be online.
LYNX Upload • Device should be in the downloaded state.
• Device should not be in use
Perform this action to upload application in the controller to
the ControlProgram. If the application in the online controller
matches with application in Control Program, invoking this Learn Links
Action does only a quick upload. In the case of quick upload, The Learn Links action on device level learns the bound links
tool only uploads Network Setpoint values, Schedule, Wall from the device.
Module, Day Light Savings configurations. If the Control When the bound link is deleted from the link manger view then
Program application is different than that in the device, tool the link are displayed as obsolete link. If the user wants to
perform a full upload. restore the bound link then the user can perform the learn
links action on the device. After learn Links the obsolete link
Write Device Instance are changed to bound link.
Perform this action to change the device instance number in The Learn Links action can be performed only in the following
the online device through Niagara. Change the device conditions:
Instance number in Device Object under Config object of a • Device should be online.
device and click Action to write the changed value to the • Device should be in the downloaded state.
controller. • Device should not be in use.

EN2Z-0960GE51 R0710 24
 CENTRALINE LYNX TOOL - USER GUIDE

Fetch Object Names references. In this case the Fetch Object Names action loads
The Learn Links action first checks if the device from which the control program and fetch the exact name of the object
the link is learnt is having the object reference at the device and rename the default name.
level, if its not present it will look for the object in the control
program. But for the other device involved in binding it only
checks for the object reference at the device level and if the
reference is not found it would create default object

25 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

PHYSICAL POINTS
Physical points are logical objects that are used in building NOTE:
application logic. Depending on the model selected, default
(Fixed) Physical points, for that model, are made available. — If the Input Type is Momentary for a Binary Input and if
The CentraLine LYNXTool automatically validates rules, the UI1 pin is not available, or is assigned another
based on the model selected. point, then the tool creates the point as an invalid
point.
The four types of Physical points available that you can — For a Momentary type binary input, when there is an
configure are: OPEN to CLOSE to OPEN transition on the physical
• Binary Inputs input, the input state changes from FALSE to TRUE
• Binary Outputs (or) TRUE to FALSE.
• Modulating Inputs — The Momentary type binary input can be configured to
• Modulating Outputs be Normally Open or Normally Close. This reverses
the TRUE/FALSE logic.
Binary Inputs While using a Bacnet Controller, the following fields are
A binary input is a physical input. You can configure Binary displayed.
Input blocks and use them while creating application logic.
Name Definition
NOTE: A binary input cannot be dropped under a macro Point Name Type a name of the function block or use the
default names given by the tool.
To add and configure a binary input block.
Point Type Binary Input is the default selection. You
1. Right-click ControlProgram under CentraLine LYNX in
can select Constant, Binary Input,
the Nav palette and select Views > Wiresheet View to
Modulating Input, Network Input or Network
view the wiresheet.
Setpoint to change the point type.
2. Drag the Binary Input block from the LYNX Palette on
to the wire sheet. Input Type When the input type is selected as
3. Type the desired name for the Binary Input block and Momentary this input can be assigned only
click OK. The block appears as a container on the wire to the UI1 pin in LYNX Micro models:
sheet similar to any function block. CLLYVL4024NS, CLLYVL4022AS,
4. Right-click the container and select Configure Proper- CLLYUL4024S, CLLYUL1012S, and
ties. The Configure Properties dialog box appears. CLLYVL0000AS. In other LYNX models if
The following table defines the fields shown in the dia- Momentary is selected as input type, then
log box. the point will be an invalid point. When
Maintained is selected this pin can be
While using a LonLYNX Controller, the following fields are assigned to any input pin.
displayed. Input State Normally Open
Normally Closed
Name Definition
Advanced Displays the Bacnet object details. Object
Point Type a name of the function block or use the Name, Object Type, Object Instance are the
Name default names given by the tool. fields provided. Object Name is
Point Binary Input is the default selection. You can automatically provided by the tool and can
Type select Constant, Network Input, Network be edited. Object Instance number can also
Setpoint, Binary Input or Modulating Input be edited. Object Type is a read only field
to change the point type. and cannot be edited. If the GPU option in
Input When the input type is selected as the advanced dialog box is set to True, Send
Type Momentary this input can be assigned only Heartbeat is enabled.
to the UI1 pin in LYNX Micro models: OK Saves the entered information and closes
CLLYVL4024NS, CLLYVL4022AS, the dialog box.
CLLYUL4024S, CLLYUL1012S, and Cancel Closes the dialog box. Any information
CLLYVL0000AS. In other LYNX models if entered is lost.
Momentary is selected as input type, then the
point will be an invalid point. When
Maintained is selected this pin can be
assigned to any input pin.
Input Normally Open
State Normally Closed
OK Saves the entered information and closes the
dialog box.
Cancel Closes the dialog box. Any information
entered is lost.

EN2Z-0960GE51 R0710 26
 CENTRALINE LYNX TOOL - USER GUIDE

The following table defines the fields shown in the Advanced — If the Input Type is Momentary for a Binary Input and if
screen of a Binary Input point.. the UI1 pin is not available, or is assigned another
point, then the tool creates the point as an invalid
Name Description point.
Object Name Displays the name of the binary — You can drag IOs on to the wiresheet even when all
input point. The object name can be pins are used up. CentraLine LYNX allows IOs to be
edited. dropped but they are not assigned with a pin. Such
Field Name Displays the name of the backend IOs are termed as invalid IOs. A message indicating
object created for the input point. It that the IO does not get a pin is displayed.
is non-editable. — When a physical IO (Modulating input, Binary input,
Modulating output, Binary output) with a valid IO pin is
Object Type Displays the object type as Binary copied and pasted in the wiresheet, the resulting IO
Input. It is non-editable. gets the same configuration as the source and a new
Object Instance A unique number that is available pin. If no free pin is available, the resulting IO
automatically assigned to the object. becomes an invalid IO.
This field is editable. If you try — When an invalid physical IO (Modulating input, Binary
replacing the instance value with a input, Modulating output, Binary output) is copied and
value of your choice, the pasted in the wiresheet, the resulting IO gets the same
replacement is successful only if the configuration as the source and it is also an invalid IO.
value of your choice is not in use by
any other object.
Update Interval The rate at which the input point is
updated.
GPU Set the GPU of each binary input to
either True or False.
• True means if the Binary Input is
bound and it has not sent an
update to the Bacnet network
target in the GPU specified time
then an alarm is generated and
the Binary Input is set to Invalid.
• False means the Binary Input
retains what was written to it until
a Bacnet network source
changes it or the CentraLine
LYNX has a power outage or
resets.
Send Heart Beat The rate at which a Network object
value is sent to the network
regardless of whether its value is
changed or not. The timeout value is
equal to the value entered in this
field multiplied by 5. This value
should be configured as multiples of
5 only, else tool rounds it off to the
nearest multiple of 5 during
download.

NOTE:

27 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

Point Conversion
To what do I
What do I convert convert? How do I do it? What is the effect?
Binary Input Constant 1. Right-click the Binary 1. If the Binary Input was connected to a slot of
input block and select a function block, the slot is converted from
Configure Properties. Connector type to Constant.
2. Select Constant from the 2. Any IO pins used by the Binary input are
Point Type list. freed.
3. Click OK.
Binary Input NCI 1. Right-click the Binary 1. The IO pins used by the Binary Input are
input block and select freed.
Configure Properties. 2. A new NCI of type Snvt is created, deter-
2. Select Constant from the mined by the Point Category, Internal Data
Point Type list. Type unit selected.
3. Enter a Value. 3. The new NCI is seen in the NVs table in the
4. Select Share Point on NV Configuration View.
Network.
5. Click OK.
Binary Input Network Input 1. Right-click the Binary 1. The IO pins used by the Binary Input are
(NVI) input block and select freed.
Configure Properties. 2. A new NVI of type Snvt is created, deter-
2. Select Constant from the mined by the Point Category, Internal Data
Point Type list. Type unit selected.
3. Enter a Value. 3. The new NVI is seen in the NVs table in the
4. Select Share Point on NV Configuration View.
Network.
5. Click OK.
Binary Input Modulating 1. Right-click the Binary 1. If there are no IO pins available for the target
Input input block and select physical IO (in this case, the Modulating input
Configure Properties. that is created), the point becomes an invalid
2. Select Modulating Input IO.
from the Point Type list. 2. A warning message appears indicating that
3. Select Type. there are no more pins to allocate, and an
4. Select Data Type. unassigned IO is created.
5. Click OK.
Binary Input Network 1. Right-click the Binary 1. The IO pins used by the Binary Input are
Setpoint input block and select freed.
Configure Properties. 2. The new setpoint input is seen in the Objects
2. Select Network Set- table in the Object Configuration View.
point from the Point
Type list.
3. Select Type.
4. Click OK.
Binary Input Network Input 1. Right-click the Binary 1. The IO pins used by the Binary Input are
input block and select freed.
Configure Properties. 2. The new network input is seen in the Objects
2. Select Network Input table in the Object Configuration View.
from the Point Type list.
3. Select Type.
4. Click OK.

Binary Outputs 3. Type the desired name for the Binary Output block and
click OK. The block appears as a container on the wire
A binary output is a physical output. You can configure Binary sheet similar to any function block.
Output blocks and use them while creating application logic. 4. Right-click the container and select Configure Proper-
To add and configure a binary output block: ties. The Binary Output dialog box appears. The fol-
1. Right-click ControlProgram under LonLYNX or Bac- lowing table defines the fields shown in the dialog box.
netLYNX in the Nav palette and select Views >
Wiresheet View to view the wiresheet.
2. Drag the Binary Output block from the LYNX Palette
on to the wire sheet.

EN2Z-0960GE51 R0710 28
 CENTRALINE LYNX TOOL - USER GUIDE

While using a LonLYNX Controller, the following fields are Name Description
displayed.
Relinquish Default A default value can be set for the
Name Definition Binary Output when all the priority
Point Type a name or use the default names given by slots in the Priority Override
Name the tool. function block are set to null.
Point Type Binary Output is the default selection. You can Logic Command Enables you to assign a priority to
select Software Output, Binary Output or Priority the output point. The point is
Modulating Output to change the point type. mapped to the priority level in the
Priority Override function block.
OK Saves the entered information and closes the
dialog box. Update Interval The rate at which the output point is
updated.
Cancel Closes the dialog box. Any information entered
is lost. GPU Set the GPU of each binary output
to either True or False.
While using a Bacnet Controller, the following fields are • True means if the Binary Output
displayed. is bound and it has not sent an
Name Definition update to the Bacnet network
target in the GPU specified time
Point Name Type a name or use the default then an alarm is generated and
names given by the tool. the Binary Output is set to
Point Type Binary Output is the default Invalid.
selection. You can select Network • False means the Binary Output
Output, Binary Output or retains what was written to it until
Modulating Output to change the a Bacnet network source
point type. changes it or the CentraLine
LYNX has a power outage or
Advanced Displays the Bacnet object details. resets.
Object Name, Object Type, Object
Instance are the fields provided. Send Heart Beat The rate at which output points send
Object Name is automatically data to the network.
provided by the tool and can be Fail Detect Enabled Set the Fail Detect Enabled of each
edited. Object Instance number can binary output to either True or
also be edited. Object Type is a read False.
only field and cannot be edited. If the • True means if the Binary Output
GPU option in the advanced dialog is bound and it has not received
box is set to True, Send Heartbeat an update from the Bacnet
is enabled. network source in the fail detect
OK Saves the entered information and time then an alarm is generated
closes the dialog box. and the Object Input is set to
Invalid.
Cancel Closes the dialog box. Any • False means the Binary Output
information entered is lost. retains what was written to it until
The following table defines the fields shown in the Advanced a Bacnet network source
screen of a Binary Output point. changes it or the CentraLine
LYNX has a power outage or
Name Description resets.
Object Name Displays the name of the binary Update Rate The rate at which a Network object
output point. The object name can value is sent to the network
be edited. regardless of whether its value is
Field Name Displays the name of the backend changed or not. The timeout value is
object created for the output point. It equal to the value entered in this
is non-editable. field multiplied by 5. This value
should be configured as multiples of
Object Type Displays the object type as Binary
5 only, else tool rounds it off to the
Output. It is non-editable.
nearest multiple of 5 during
Object Instance A unique number that is download.
automatically assigned to the object.
This field is editable. If you try NOTE:
replacing the instance value with a
value of your choice, the — You can drag the IOs on to the wiresheet even
replacement is successful only if the when all pins are used up. CentraLine LYNX
value of your choice is not in use by allows IOs to be dropped but they are not
any other object. assigned with a pin. Such IOs are termed as
invalid IOs. A message indicating that the IO does
not get a pin is displayed.

29 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

— When a binary output is deleted, if it had a valid — When an invalid physical IO (Modulating input,
IO pin assigned, the freed pin is automatically Binary input, Modulating output, Binary output) is
assigned to an invalid Modulating output config- copied and pasted in the wiresheet, the resulting
ured as PWM type or to an invalid binary output, if IO gets the same configuration as the source and
any. it is also an invalid IO.
— When a physical IO (Modulating input, Binary — When an invalid physical IO (Modulating input,
input, Modulating output, Binary output) with a Binary input, Modulating output, Binary output) is
valid IO pin is copied and pasted in the wiresheet, copied and pasted in the wiresheet, the resulting
the resulting IO gets the same configuration as IO gets the same configuration as the source and
the source and a new available pin. If no free pin it is also an invalid IO.
is available, the resulting IO becomes an invalid
IO.
Point Conversion
To what do I
What do I convert convert? How do I do it? What is the effect?
Binary Output Software Output 1. Right-click the Binary out- 1. The IO pins used by the Binary output are
(NVO) put block and select Con- freed.
figure Properties. 2. A new NVO of type Snvt is created, deter-
2. Select Software Output mined by the Point Category, Internal Data
from the Point Type list. Type unit selected.
3. Select a Point Category. 3. The new NVO is seen in the NVs table in the
4. Select Units to be used NV Configuration View.
within logic. 4. A new NV is created even if the NV count
5. Click OK. exceeds the maximum number and a warning
message appears indicating the same.
Binary Output Modulating 1. Right-click the Binary out- 1. If there are no IO pins available for the target
Output put block and select Con- physical IO (in this case, the Modulating out-
figure Properties. put that is created), the point becomes an
2. Select Modulating Out- invalid IO.
put from the Point Type 2. A warning message appears indicating that
list. there are no more pins to allocate, and an
3. Select Type. unassigned IO is created.
4. Select Analog Type.
5. Select Output Values.
6. Click OK.
Binary Output Network Output 1. Right-click the Binary out- 1. The IO pins used by the Binary output are
put block and select Con- freed.
figure Properties. 2. The new Network Output is seen in the
2. Select Network Output Objects table in the Object Configuration
from the Point Type list. View.
3. Select a Point Category.
4. Select Units to be used
within logic.
5. Click OK.

Modulating Inputs While using a LonLYNX Controller, the following fields are
displayed.
A modulating input is a physical input. You can configure
Modulating Input blocks and use them while creating
application logic.
Name Definition
To add and configure a Modulating Input block:
Point Name Enter a name of the function block or use the
1. Right-click ControlProgram under LonLYNX or Bac- default names provided by the tool.
netLYNX in the Nav palette and select Views >
Wiresheet View to view the wiresheet. Point Type Modulating Input is the default selection. You
2. Drag the Modulating Input block from the LYNX Pal- can select Constant, Binary Input, Network
ette on to the wire sheet. Input, or Network Setpoint if you want to
3. Type the desired name for the Modulating Input block change the input type.
and click OK. The block appears as a container on the Type Displays the list of sensors that can be
wire sheet similar to any function block. connected. Select a sensor type.
4. Right-click the container and select Configure Proper-
ties. The Modulating Input dialog box appears. The Data Displays the unit of measurement for the Type.
following table defines the fields shown in the dialog Category This is enabled when Custom Resistive or
box. Custom Voltage is selected in the Type field.

EN2Z-0960GE51 R0710 30
 CENTRALINE LYNX TOOL - USER GUIDE

Data Type Displays the engineering unit based on the 3600 pulses per hour and this is multiplied with a scale factor
Data Category. of 10 Watt-Hours/Pulse, the current power is 3600 x 10 =
36000 Watts or 36 KW.
Input State Use this to edit sensor characteristics. The
Input State is editable only when a custom NOTE: The modulating input types Counter and
sensor (Custom Resistive or Custom Pulse_Meter can be configured to be Normally Open
Voltage) is selected in the Type field. You can or Normally Close. This reverses the TRUE/FALSE
enter values for: logic.
• Input Low
• Input High While using a BacnetLYNX Controller, the following fields are
• Output Low displayed.
• Output High
Name Definition
Sensor Click the Sensor Limits button to view and set
Limits the upper and lower limits. Point Name Enter a name of the function block or
• Enter a lower limit in the Low Limit field. use the default names provided by
• Enter an upper limit in the High Limit field. the tool.
Point Type Modulating Input is the default
Sensor Readings Outside Limit selection. You can select Constant,
• Choose Value is INVALID outside High if Modulating Input, Binary Input,
you want Invalid to be displayed when the Network Setpoint, or Network
limits are crossed. Input if you want to change the input
• Choose Clamp Value as High and Low type.
Limit if you want the Low and High Limits
that you enter to be displayed when the Type Displays the list of sensors that can
limits are crossed. be connected. Select a sensor type.
OK Saves the entered information and closes the Point Category Displays the unit of measurement for
dialog box. the Type. This is enabled when
Custom Resistive or Custom
Cancel Closes the dialog box. Any information entered Voltage is selected in the Type field.
is lost.
Unit Displays the engineering unit based
NOTE: For LYNX Micro models: CLLYVL4024NS, on the Point Category.
CLLYVL4022AS, CLLYUL4024S and Input State Use this to edit sensor
CLLYUL1012S, if you select Pulse_Meter or Counter characteristics. The Input State is
as the sensor type, a default pin UI1 is assigned. If editable only when a custom sensor
the pin is not available, or is currently assigned to (Custom Resistive or Custom
another point, the tool creates the point as an invalid Voltage) is selected in the Type field.
point. You can enter values for:
• Input Low
When the modulating input is configured to type Counter in a • Input High
LYNX Micro model, it reads the number of counts received in • Output Low
the last second. For example, if a 10Hz signal is connected to • Output High
the input, the input reads 10 counts each second. Another
example, suppose a 0.5Hz signal is connected to the input,
the input reads a 0 in the 1st second, a 1 in the 2nd second, a
0 in the 3rd second, a 1 in the 4th second, and so on. The
maximum frequency of the signal allowed is 15Hz that is,
maximum counts per second that can be wired to the input is
15 per second. The user can connect this to the function block
logic and accumulate counts.
When the modulating input is configured to type Pulse_Meter
in a LYNX Micro model, it reads the number of pulses per
hour. The algorithm averages the readings depending on the
rate at which the pulses come in.
For fast pulses (<20 seconds apart), average of the last 4
readings is taken.
For medium pulses (<40 seconds apart), average of the last 2
readings is taken.
For slow pulses (>40 seconds apart), the last reading is taken.
When the pulses stop coming in, the power gradually
decreases and goes to 0 in about 11 minutes. The maximum
measured rate is 54000 pulses per hour. The calculated
output of a pulse meter input is in pulses per hour. You can
connect this to the function block logic (multiply by scale
factor) to compute power. For example, if the pulse meter is at

31 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

Name Definition Name Description

Sensor Limits Click the Sensor Limits button to Sen Delta The Significant Event Notification
view and set the upper and lower is also known as SEN Delta. The
limits. object is sent on the Bacnet Network
• Enter a lower limit in the Low whenever any field exceeds the SEN
Limit field. Delta. SEN Delta of zero (0) disables
• Enter an upper limit in the High the feature.
Limit field. Update The rate at which the input point is
Sensor Readings Outside Limit Interval updated.
• Choose Value is INVALID outside
High if you want Invalid to be GPU Set the GPU of each modulating
displayed when the limits are input to either True or False.
crossed. • True means if the Modulating
• Choose Clamp Value as High Input is bound and it has not sent
and Low Limit if you want the Low an update to the Bacnet network
and High Limits that you enter to target in the GPU specified time
be displayed when the limits are then an alarm is generated and
crossed. the Modulating Input is set to
Invalid.
Advanced Displays the Bacnet object details. • False means the Modulating Input
Object Name, Object Type, Object retains what was written to it until
Instance are the fields provided. a Bacnet network source changes
Object Name is automatically it or the CentraLine LYNX has a
provided by the tool and can be power outage or resets.
edited. Object Instance number can
also be edited. Object Type is a Send Heart The rate at which a Network object
read only field and cannot be edited. Beat value is sent to the network
If the GPU option in the advanced regardless of whether its value is
dialog box is set to True, Send changed or not. The timeout value is
Heartbeat is enabled. equal to the value entered in this field
multiplied by 5. This value should be
OK Saves the entered information and configured as multiples of 5 only,
closes the dialog box. else tool rounds it off to the nearest
Cancel Closes the dialog box. Any multiple of 5 during download.
information entered is lost.
NOTE:
The following table defines the fields shown in the Advanced — You can drag and drop IOs on to the wiresheet even
screen of a Modulating Input point. when all pins are used up. CentraLine LYNX allows
Name Description IOs to be dropped but they will not be assigned with a
pin. Such IOs are termed as invalid IOs. A message
Object Name Displays the name of the modulating indicating that the IO does not get a pin is displayed.
input point. The object name can be — When a modulating input is deleted, if it had a valid IO
edited. pin assigned, the freed pin is automatically assigned
Field Name Displays the name of the backend to any invalid modulating input or an invalid binary
object created for the input point. It is input.
non-editable. — When a physical IO (Modulating input, Binary input,
Object Type Displays the object type as Modulating output, Binary output) with a valid IO pin is
Modulating Input. It is non-editable. copied and pasted in the wiresheet, the resulting IO
gets the same configuration as the source and a new
Object A unique number that is available pin. If no free pin is available, the resulting IO
Instance automatically assigned to the object. becomes an invalid IO.
This field is editable. If you try — When an invalid physical IO (Modulating input, Binary
replacing the instance value with a input, Modulating output, Binary output) is copied and
value of your choice, the pasted in the wiresheet, the resulting IO gets the same
replacement is successful only if the configuration as the source and it is also an invalid IO.
value of your choice is not in use by — When you copy and paste a modulating input of type
any other object. standard and custom sensors on the wiresheet, the
same configuration is retained. Even though an On
Board Pressure Sensor can be configured, it will not
be as a consequence of the copy and paste action on
the wiresheet.

EN2Z-0960GE51 R0710 32
 CENTRALINE LYNX TOOL - USER GUIDE

Adding an Onboard Pressure Sensor To add an Onboard Pressure Sensor:

The on-board pressure sensor is always assigned to the 1. Drag a Modulating Input from the LYNX Palette to the
Universal Input # 0, in case where the model supports this wiresheet.
fixed physical point, whether it is physically present or not. 2. Right-click the Modulating Input you just added and
select Configure Properties.
NOTE: The number of On Board Pressure Sensors you can 3. Select On_Board_Pressure from the Type list.
add are dependent on the Controller model selected. 4. Click OK to complete adding an On Board Pressure
If you exceed the allowed limit of On Board Pressure Sensor.
Sensors in an application logic, you cannot configure
the modulating inputs as On Board Pressure Sensor. Point Conversion

To what do I
What do I convert convert? How do I do it? What is the effect?
Modulating Input Constant 1. Right-click the Modulating 1. If the Modulating Input was connected to a
input block and select slot of a function block, the slot is converted
Configure Properties. from Connector type to Constant.
2. Select Constant from the 2. IO pins used by the Modulating input are
Point Type list. freed.
3. Select a Point Category.
4. Select Units to be used
within logic.
5. Select Value.
6. Click OK.
Modulating Input NCI 1. Right-click the Modulating 1. The IO pins used by the Modulating input are
input block and select freed.
Configure Properties. 2. A new NCI of type Snvt is created, deter-
2. Select Constant from the mined by the Point Category, Internal Data
Point Type list. Type unit selected.
3. Enter a Value. 3. The new NCI is seen in the NVs table in the
4. Select Share Point on NV Configuration View.
Network.
5. Click OK.

33 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

Modulating Input Network Input 1. Right-click the Modulating 1. The IO pins used by the Modulating input are
(NVI) input block and select freed.
Configure Properties. 2. A new NVI of type Snvt is created, deter-
2. Select Network Input mined by the Point Category, Internal Data
from the Point Type list. Type unit selected.
3. Select a Point Category. 3. The new NVI is seen in the NVs table in the
4. Select Units to be used NV Configuration View.
within logic.
5. Click OK.
Modulating Input Binary Input 1. Right-click the Modulating 1. If there are no IO pins available for the target
input block and select physical IO (in this case, the Binary input that
Configure Properties. is created), the point becomes an invalid IO.
2. Select Binary Input from 2. A warning message appears indicating that
the Point Type list. there are no more pins to allocate, and an
3. Select Type. unassigned IO is created.
4. Select Data Type.
5. Click OK.
Modulating Input Network 1. Right-click the Modulating 1. The IO pins used by the Modulating Input are
Setpoint input block and select freed.
Configure Properties. 2. The new setpoint input is seen in the Objects
2. Select Network Set- table in the Object Configuration View.
point from the Point
Type list.
3. Select Type.
4. Click OK.
Modulating Input Network Input 1. Right-click the Modulating 1. The IO pins used by the Modulating Input are
input block and select freed.
Configure Properties. 2. The new network input is seen in the Objects
2. Select Network Input table in the Object Configuration View.
from the Point Type list.
3. Select Type.
4. Click OK.

NOTE: While using a LonLYNX Controller, the following fields are

displayed.
— When you copy and paste an On Board Pressure Sen-
sor (modulating input) on the wiresheet such that the Name Definition
maximum allowed count for that model is exceeded, it Point Name Enter a name of the function block or use the
is converted to a custom voltage sensor. default names provided by the tool.
Point Type Modulating Output is the default selection. You
Modulating Outputs can select Software Output or Binary Output
to change the point type.
A modulating output is a physical output. You can configure
Modulating Output blocks and use them while creating Type Indicates modulating output type. You can
application logic. select one of the following types:
• Analog: Use this option to drive the motor
To add and configure a Modulating Output block:
fully opened or fully closed based on the
1. Right-click ControlProgram under LonLYNX or Bac- output values specified.
netLYNX in the Nav palette and select Views > • Floating: Select this option if you want an
Wiresheet View to view the wiresheet. output that behaves as a digital output.
2. Drag the Modulating Output block from the Palette on • Pwm: Select this option if you want an
to the wire sheet. output that behaves as a digital output.
3. Type a name for the Modulating Output block and click • Actuator: Select this option if you want an
OK. The block appears as a container on the wire sheet output as a fixed Physical point.
similar to any function block.
4. Right-click the container and select Configure Proper- Analog Type This is enabled only when Analog is selected
ties. The Modulating Output dialog box appears. The in the Type field. You can select one of the
following table defines the fields shown in the dialog following:
box. • Volts: The range is 0-10 Vdc
• Amps: The range is 4-20mA.

EN2Z-0960GE51 R0710 34
 CENTRALINE LYNX TOOL - USER GUIDE

Output This is enabled only when Analog is selected Floating This is enabled when Floating is selected in
Values in the Type field. Enter the value for Zero Motor the Type field.
Percent and Full Percent. Configuratio • Travel time
n • AutoSyncType: You can select one of the
NOTE: Each modulating output can be con- following values:
figured for the output voltage/current • None: CentraLine LYNX assumes the motor
at 0% and at 100%. Each Modulating is fully closed.
Output circuit operates in current • Sync Open: The motor is driven fully open.
mode for loads up to 600 ohms. For • Sync Closed: The motor is driven fully
loads of 600 to 1000 ohms, the output closed.
transitions to voltage mode. For loads • AutoSyncInterval: The Auto
above 1000 ohms, the output oper- Synchronization Interval is configured from
ates in voltage. 0 to 255 hours in one hour increments. The
timer is loaded and starts counting down
NOTE: When full percent is less than zero right after power up reset and power up
percent, the motor runs in reverse delay. When the timer expires, the motor is
direction. synchronized. This only applies if the user
PWM This is enabled when Pwm is selected in the configured auto synchronization to be Sync
Configuratio Type field. You can enter the values for the Open or Sync Closed.
n following: • PowerupSyncType: You can select one of
• Period: The range is between 1-3276.7 the following values:
seconds in tenths of seconds. • None: CentraLine LYNX assumes the motor
• Zero time is fully closed.
• Full time • Sync Open: The motor is driven fully open.
• Sync Closed: The motor is driven fully
closed.
• PowerupDelay: The Power Up Delay is
configured from 0 to 3276.7 seconds in
tenths of seconds. Zero (0) means no delay.
Motor Action This is enabled only when Floating is selected
in the Type field. You can select one of the
following values:
• Direct
• Reverse
Reverse Action is configured for
— True = 100% = full closed, 0% = full
open.
— False is the opposite.
OK Saves the entered information and closes the
dialog box.
Cancel Closes the dialog box. Any information entered
is lost.

35 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

While using a BacnetLYNX Controller, the following fields Name Description

are displayed.
Floating Motor This is enabled when Floating is selected in
Name Description Configuration the type field.
Point Name Enter a name or use the default names • Travel time:
provided by the tool. • AutoSyncType: You can select one of
the following values:
Point Type Modulating Output is the default selection. — None: CentraLine LYNX assumes
You can select Network Output, the motor is fully closed.
Modulating Output or Binary Output to — Sync Open: The motor is driven
change the point type. fully open.
Type Indicates modulating output type. You can — Sync Closed: The motor is driven
select one of the following types: fully closed.
• Analog: Use this option to drive the motor • AutoSyncInterval: The Auto
fully opened or fully closed based on the Synchronization Interval is configured
output values specified. from 0 to 255 hours in one hour
• Floating: Select this option if you want an increments. The timer is loaded and
output that behaves as a digital output. starts counting down right after power up
• Pwm: Select this option if you want an reset and power up delay. When the
output that behaves as a digital output. timer expires, the motor is synchronized.
• Actuator: Select this option if you want an This only applies if the user configured
output as a fixed Physical point. auto synchronization to be Sync Open or
Sync Closed.
Analog Type This is enabled only when Analog is
• PowerupSyncType: You can select one
selected in the Type field. You can select
of the following values:
one of the following:
— None: CentraLine LYNX assumes
• Volts: The range is 0-10 Vdc.
the motor is fully closed.
• Amps: The range is 4-20mA.
— Sync Open: The motor is driven
Output Values This is enabled only when Analog is fully open.
selected in the Type field. Enter the value — Sync Closed: The motor is driven
for Zero Percent and Full Percent. fully closed.
• PowerupDelay: The Power Up Delay is
NOTE: Each modulating output can be configured from 0 to 3276.7 seconds in
configured for the output voltage/ tenths of seconds. Zero (0) means no
current at 0% and at 100%. Each delay.
Modulating Output circuit operates
Motor Action This is enabled only when Floating is
in current mode for loads up to 600
selected in the Type field.
ohms. For loads of 600 to 1000
You can select one of the following values:
ohms, the output transitions to volt-
• Direct
age mode. For loads above 1000
• Reverse
ohms, the output operates in volt-
age. When full percent is less than
Reverse Action is configured for True =
zero percent, the motor runs in
100% = full closed, 0% = full open. False is
reverse direction.
the opposite.
PWM This is enabled when Pwm is selected in
Advanced Displays the Bacnet object details. Object
Configuration the Type field. You can enter the values for
Name, Object Type, Object Instance are
the following:
the fields provided. Object Name is
• Period: The range is between 1-3276.7
automatically provided by the tool and can
seconds in tenths of seconds.
be edited. Object Instance number can
• Zero time
also be edited. Object Type is a read only
• Full time
field and cannot be edited. If the GPU option
in the advanced dialog box is set to True,
Send Heartbeat is enabled. If the Fail
Detect Enabled is set to True, Update
Rate is enabled.
OK Saves the entered information and closes
the dialog box.
Cancel Closes the dialog box. Any information
entered is lost.

EN2Z-0960GE51 R0710 36
 CENTRALINE LYNX TOOL - USER GUIDE

NOTE: — When an invalid physical IO (Modulating input, Binary

input, Modulating output, Binary output) is copied and
— You can drag the IOs on to the wiresheet even when pasted in the wiresheet, the resulting IO gets the same
all pins are used up. CentraLine LYNX allows IOs to configuration as the source and it is also an invalid IO.
be dropped but they are not assigned with a pin. Such — When you copy and paste a modulating output on the
IOs are termed as invalid IOs. A message indicating wiresheet, the same configuration is retained. When
that the IO does not get a pin is displayed. copying an analog type, even if digital pins are
— When a Modulating output configured as Floating type present, a pin is not assigned. A pin is assigned only
is deleted, if it had a valid IO pin assigned, the freed when a floating/pwm type is copied and pasted on the
pin is automatically assigned to any available invalid wiresheet or when it is dragged on to the wiresheet.
Modulating output configured as Floating type or to an
invalid binary output. Adding an Actuator
— When a modulating output configured as PWM type is
deleted, if it had a valid IO pin assigned, the freed pin An actuator is a fixed physical point. The Actuator is always
is automatically assigned to any available invalid Mod- assigned to the Digital Output # 7 and 8, in case where the
ulating output configured as PWM or to an invalid model supports this fixed physical point, whether it is
binary output. physically present or not.
— When a modulating output configured as Analog type To add an Actuator:
is deleted, if it had a valid IO pin assigned, the freed 1. Drag a Modulating Output from the LYNX palette to
pin is automatically assigned to any available invalid the wiresheet.
Modulating output configured as Analog type or to an 2. Right-click the Modulating Output you just added and
invalid binary output. select Configure Properties.
— When a physical IO (Modulating input, Binary input, 3. Select Actuator from the Type list.
Modulating output, Binary output) with a valid IO pin is 4. Select Floating Motor Configuration details.
copied and pasted in the wiresheet, the resulting IO 5. Specify Motor Action.
gets the same configuration as the source and a new 6. Click OK to complete adding an Actuator.
available pin. If no free pin is available, the resulting IO
becomes an invalid IO.

Point Conversion
To what do I
What do I convert convert? How do I do it? What is the effect?
Modulating Output Binary Output 1. Right-click the Modulating 1. If there are no IO pins available for the target
output block and select physical IO (in this case, the Binary output
Configure Properties. that is created), the point becomes an invalid
2. Select Binary Output IO.
from the Point Type list. 2. A warning message appears indicating that
3. Click OK. there are no more pins to allocate, and an
unassigned IO is created.
Modulating Output Network Output 1. Right-click the Modulating 1. The IO pins used by the Modulating output
output block and select are freed.
Configure Properties. 2. The new network output is seen in the
2. Select Network Output Objects table in the Object Configuration
from the Point Type list. View.
3. Select a Point Category.
4. Select the Unit.
5. Click OK.

37 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

SOFTWARE POINTS
Software IOs are non-physical IOs that you can configure as
Constants, Network Input, Network Setpoint, or Network To define your own custom enumeration type for the software
Output and use in your application logic. points:
1. Select Custom from the Sub-Category list.
Constants 2. Click the button next to the Sub-Category drop-down.
A constant input is a non-physical input which is not visible to The Enum dialog box appears.
the network. You can configure Constant blocks and use them 3. Click the check box Load from Standard list to load the
while creating application logic in Bacnet LYNX. range from the standard list.
or
To add and configure a network input block: Click Add to create your own custom enumeration type.
1. Right-click ControlProgram under CentraLine LYNX in Enter the New Enum name and click Save.
the Nav palette and select Views > Wiresheet View to 4. Click OK.
view the wiresheet.
2. Drag the Constant block from the LYNX Palette on to NOTE: You can drag IOs on to the wiresheet even when all
the wire sheet. pins are used up. CentraLine LYNX allows IOs to be
3. Type the desired name for the Constant block and click dropped but they are not assigned with a pin. Such
OK. The block appears as a container on the wire sheet IOs are termed as invalid IOs. A message indicating
similar to any function block. that the IO does not get a pin is displayed.
4. Right-click the container and select Configure Proper-
ties. The Constant dialog box appears. The following NOTE: You can add a Constant to a macro.
table defines the fields shown in the dialog box.

Name Description
Point Name Type a name of the function block or
use the default names given by the
tool.
Point Type Constant is the default selection.
You can select Constant, Network
Input, Network Setpoint, Binary
Input or Modulating Input to
change the point type.
Point Category Displays the unit of measurement for
the Point Type.
Unit Displays the engineering unit based
on the Point Category.
Sub-Category Displays the enumeration type for
the software points. The field Unit is
renamed as Sub-Category if the
point category selection is unitless.
OK Saves the entered information and
closes the dialog box.
Cancel Closes the dialog box. Any
information entered is lost.

EN2Z-0960GE51 R0710 38
 CENTRALINE LYNX TOOL - USER GUIDE

Point Conversion
What do I want To what do I want to
to convert? convert? How do I do it? What is the effect?
Constant Network Input 1. Right-click the Network input block 1. If the Functional block slot to which
and select Configure Properties. the point was connected was of
2. Select Constant from the Point type Constant/Connector, the slot
Type list. is converted from Constant type to
3. Select a Point Category. Connector but the link is retained.
4. Click OK. 2. If the functional block slot to which
the point was connected was of
type Connector only, the link is bro-
ken.
3. A network input is created and
added to the Objects table in the
Object Configuration View.
Constant Network Setpoint 1. Right-click the Network input block 1. If the Functional block slot to which
and select Configure Properties. the point was connected was of
2. Select Network Setpoint from the type Constant/Connector, the slot
Point Type list. is converted from Constant type to
3. Select a Point Category. Connector but the link is retained.
4. Click OK. 2. If the Functional block slot to which
the point was of type Constant
only, the link is broken.
3. A new setpoint input is created and
added to the Objects table in the
Object Configuration View.
Constant Binary Input 1. Right-click the Network input block 1. If the Functional block slot to which
and select Configure Properties. the point was connected was of
2. Select Binary Input from the Point type Constant/Connector, the slot
Type list. is converted from Constant type to
3. Select Type. Connector but the link is retained.
4. Select Data Type. 2. If the Functional block slot to which
5. Click OK. the point was of type Constant
only, the link is broken.
3. The resulting physical IO object
(Binary input in this case) gets any
free IO pin available. If no pin is
available, the resulting physical IO
becomes an invalid IO (IO with no
pin).
Constant Modulating Input 1. Right-click the Network input block 1. If the Functional block slot to which
and select Configure Properties. the point was connected was of
2. Select Modulating Input from the type Constant/Connector, the slot
Point Type list. is converted from Constant type to
3. Select Type. Connector but the link is retained.
4. Select Data Type. 2. If the Functional block slot to which
5. Click OK. the point was of type Constant
only, the link is broken.
3. The resulting physical IO object
(Modulating input in this case) gets
any free IO pin available. If no pin is
available, the resulting physical IO
becomes an invalid IO (IO with no
pin).

39 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

Network Inputs The following table defines the fields shown in the Advanced
screen of a Network Input point.
A network input is a non-physical input. You can configure
Network Input blocks and use them while creating application Name Description
logic in Bacnet LYNX. Object Name Displays the name of the network
To add and configure a network input block: input point. The object name can be
1. Right-click ControlProgram under CentraLine LYNX in edited.
the Nav palette and select Views > Wiresheet View to Field Name Displays the name of the backend
view the wiresheet. object created for the input object. It
2. Drag the Network Input block from the LYNX Palette is non-editable.
on to the wire sheet.
3. Type the desired name for the Network Input block and Object Type Displays the object type as Network
click OK. The block appears as a container on the wire Input. This field is non-editable.
sheet similar to any function block. Object Instance A unique number that is
4. Right-click the container and select Configure Proper- automatically assigned to the object.
ties. The Network Input dialog box appears. The fol- This field is editable. If you try
lowing table defines the fields shown in the dialog box. replacing the instance value with a
value of your choice, the
Name Description replacement is successful only if the
Point Name Type a name of the function block or value of your choice is not in use by
use the default names given by the any other object.
tool. Proposed Type Enables you to select the object type
Point Type Network Input is the default as Analog Value or Binary Value.
selection. You can select Constant, Update Interval The rate at which the input object is
Network Input, Network Setpoint, updated.
Binary Input or Modulating Input to
change the point type. Fail Detect Enabled Set the Fail Detect Enabled of each
object input to either True or False.
Point Category Displays the unit of measurement for • True means if the Object Input is
the Point Type. bound and it has not received an
Unit Displays the engineering unit based update from the Bacnet network
on the Point Category. source in the fail detect time then
Sub-Category Displays the enumeration type for the an alarm is generated and the
software points. The field Unit is Object Input is set to Invalid.
renamed as Sub-Category if the • False means the Object Input
point category selection is unitless. retains what was written to it until
a Bacnet network source
Advanced Displays the Bacnet object details. changes it or the CentraLine
Object Name, Object Type, Object LYNX has a power outage or
Instance are the fields provided. resets.
Object Name is automatically
provided by the tool and can be Update Rate The polling rate to update Object
edited. Object Instance number can values of Object components.
also be edited. Object Type is a read
only field and cannot be edited. To define your own custom enumeration type for the software
OK Saves the entered information and points:
closes the dialog box. 1. Select Custom from the Sub-Category list.
Cancel Closes the dialog box. Any 2. Click the button next to the Sub-Category drop-down.
information entered is lost. The Enum dialog box appears.
3. Click the check box Load from Standard list to load
the range from the standard list.
or
Click Add to create your own custom enumeration type.
Enter the New Enum name and click Save.
4. Click OK.

NOTE: You can add a Network Input with Point Type as

Constant to a macro.

EN2Z-0960GE51 R0710 40
 CENTRALINE LYNX TOOL - USER GUIDE

Point Conversion
What do I want to To what do I want to
convert? convert? How do I do it? What is the effect?
Network Input Constant 1. Right-click the Network input block 1. If the functional block slot to
and select Configure Properties. which the point was connected
2. Select Constant from the Point was of type Constant/Connector,
Type list. the slot is converted from Con-
3. Select a Point Category. nector type to Constant and the
4. Click OK. link is retained.
2. If the functional block slot to
which the point was connected
was of type Connector only, the
link is broken.
Network Input Network Setpoint 1. Right-click the Network input block 1. If the point is connected to any
and select Configure Properties. functional block, the functional
2. Select Network Setpoint from the blocks slot type and links are
Point Type list. retained.
3. Select a Point Category. 2. A new setpoint input is created
4. Click OK. and added to the Objects table in
the Object Configuration View.
Network Input Binary Input 1. Right-click the Network input block 1. If the point is connected to any
and select Configure Properties. functional block, the functional
2. Select Binary Input from the Point block slot type and links are
Type list. retained.
3. Select Type. 2. The resulting physical IO object
4. Select Data Type. (Binary input in this case) gets
5. Click OK. any free IO pin available. If no
pin is available, the resulting
physical IO becomes an invalid
IO (IO with no pin).
Network Input Modulating Input 1. Right-click the Network input block 1. If the point is connected to any
and select Configure Properties. functional block, the functional
2. Select Modulating Input from the block slot type and links are
Point Type list. retained.
3. Select Type. 2. The resulting physical IO object
4. Select Data Type. (Modulating input in this case)
5. Click OK. gets any free IO pin available. If
no pin is available, the resulting
physical IO becomes an invalid
IO (IO with no pin).

Network Setpoints
A network setpoint is a non-physical input. You can configure
Network Setpoint blocks and use them while creating Name Description
application logic in Bacnet LYNX. Point Name Type a name of the function block or
To add and configure a network input block: use the default names given by the
tool.
1. Right-click ControlProgram under CentraLine LYNX in
the Nav palette and select Views > Wiresheet View to Point Type Network Setpoint is the default
view the wiresheet. selection. You can select Constant,
2. Drag the Network Setpoint block from the LYNX Pal- Network Input, Network Setpoint,
ette on to the wire sheet. Binary Input or Modulating Input to
3. Type the desired name for the Network Setpoint block change the point type.
and click OK. The block appears as a container on the Point Category Displays the unit of measurement for
wire sheet similar to any function block. the Point Type.
4. Right-click the container and select Configure Proper-
ties. The Network Setpoint dialog box appears. The Unit Displays the engineering unit based
following table defines the fields shown in the dialog on the Point Category.
box.

41 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

Name Description The following table defines the fields shown in the Advanced
screen of a Network Setpoint.
Sub-Category Displays the enumeration type for
the software points.The field Unit is Name Description
renamed as Sub-Category if the Object Name Displays the name of the network
point category selection is unitless. setpoint. The object name can be
Advanced Displays the Bacnet object details. edited.
Object Name, Object Type, Object Field Name Displays the name of the backend
Instance are the fields provided. object created for the setpoint object.
Object Name is automatically It is non-editable.
provided by the tool and can be
edited. Object Instance number can Object Type Displays the object type as Network
also be edited. Object Type is a Setpoint. This field is non-editable.
read only field and cannot be edited. Object Instance A unique number that is
OK Saves the entered information and automatically assigned to the object.
closes the dialog box. This field is editable. If you try
replacing the instance value with a
Cancel Closes the dialog box. Any value of your choice, the
information entered is lost. replacement is successful only if the
value of your choice is not in use by
any other object.
Update Interval The rate at which the setpoint object
is updated.
Proposed Type Enables you to select the object type
as Analog Value or Binary Value.
To define your own custom enumeration type for the software
points:
1. Select Custom from the Sub-Category list.
2. Click the button next to the Sub-Category drop-down.
The Enum dialog box appears.
3. Click the check box Load from Standard list to load the
range from the standard list.
or
Click Add to create your own custom enumeration type.
Enter the New Enum name and click Save.
4. Click OK.

NOTE: You can add a Network Setpoint with Point Type as

Constant to a macro.

EN2Z-0960GE51 R0710 42
 CENTRALINE LYNX TOOL - USER GUIDE

Point Conversion
What do I want to To what do I want
convert? to convert? How do I do it? What is the effect?
Network Setpoint Constant 1. Right-click the Network setpoint 1. If the functional block slot to which
block and select Configure Prop- the point was connected was of type
erties. Constant/Connector, the slot is con-
2. Select Constant from the Point verted from Connector type to Con-
Type list. stant but the link is retained.
3. Select a Point Category. 2. If the functional block slot to which
4. Click OK. the point was connected was of type
Connector only, the link is broken.
Network Setpoint Network Input 1. Right-click the Network setpoint 1. If the point is connected to any func-
block and select Configure Prop- tional block, the functional block slots
erties. and links are retained.
2. Select Network Input from the 2. A new network input is created and
Point Type list. added to the Objects table in the
3. Select a Point Category. Object Configuration View.
4. Click OK.
Network Setpoint Binary Input 1. Right-click the Network setpoint 1. If the point is connected to any func-
block and select Configure Prop- tional block, the functional block slot
erties. type and links are retained.
2. Select Binary Input from the 2. The resulting physical IO object
Point Type list. (Binary input in this case) gets any
3. Select Type. free IO pin available. If no pin is avail-
4. Select Data Type. able, the resulting physical IO
5. Click OK. becomes an invalid IO (IO with no
pin).
Network Setpoint Modulating Input 1. Right-click the Network setpoint 1. If the point is connected to any func-
block and select Configure Prop- tional block, the functional block slot
erties. type and links are retained.
2. Select Modulating Input from the 2. The resulting physical IO object
Point Type list. (Modulating input in this case) gets
3. Select Type. any free IO pin available. If no pin is
4. Select Data Type. available, the resulting physical IO
5. Click OK. becomes an invalid IO (IO with no
pin).

Network Outputs
While in the midst of creating an ControlProgram/Program, if Name Description
you need to quickly add an Network Output, use the Software Point Name Type a name of the function block or
Outputs item on the LYNX Palette. use the default names given by the
You cannot add an Network Output point to a macro. tool.
To add and configure a Network output block: Point Type Network Setpoint is the default
1. Right-click ControlProgram under BacnetLYNX in the selection. You can select Constant,
Nav palette and select Views > Wiresheet View to view Network Input, Network Setpoint,
the wiresheet. Binary Input or Modulating Input to
2. Drag the Network Output block from the LYNX Palette change the point type.
on to the wire sheet. Point Category Displays the unit of measurement for
3. Type the desired name for the Network Output block the Point Type.
and click OK. The block appears as a container on the
wire sheet similar to any function block. Unit Displays the engineering unit based
4. Right-click the container and select Configure Proper- on the Point Category.
ties. The Network Output dialog box appears. The fol-
lowing table defines the fields shown in the dialog box.

43 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

Name Description Name Description

Sub-Category Displays the enumeration type for the Proposed Type Enables you to select the object type as
software points. The field Unit is Analog Value or Binary Value.
renamed as Sub-Category if the point Sen Delta The Significant Event Notification is
category selection is unitless. also known as SEN Delta. The object is
Advanced Displays the Bacnet object details. sent on the Bacnet Network whenever
Object Name, Object Type, Object any field exceeds the SEN Delta. SEN
Instance are the fields provided. Delta of zero (0) disables the feature.
Object Name is automatically GPU Set the GPU of each object output to
provided by the tool and can be edited. either True or False.
Object Instance number can also be • True means if the Object Output is
edited. Object Type is a read only field bound and it has not sent an update
and cannot be edited. to the Bacnet network target in the
OK Saves the entered information and GPU specified time then an alarm is
closes the dialog box. generated and the Object Output is
Cancel Closes the dialog box. Any information set to Invalid.
entered is lost. • False means the Object Output
retains what was written to it until a
Bacnet network source changes it or
The following table defines the fields shown in the Advanced the CentraLine LYNX has a power
screen of a Network Output point. outage or resets.
Name Description Send Heart Beat The rate at which a Network object value
is sent to the network regardless of
Object Name Displays the name of the network output whether its value is changed or not. The
point. The object name can be edited. timeout value is equal to the value
Field Name Displays the name of the backend object entered in this field multiplied by 5. This
created for the output object. It is non- value should be configured as multiples
editable. of 5 only, else tool rounds it off to the
nearest multiple of 5 during download.
Object Type Displays the object type as Network
Output. This field is non-editable.
Object Instance A unique number that is automatically To define your own custom enumeration type for the software
assigned to the object. This field is points:
editable. If you try replacing the instance 1. Select Custom from the Sub-Category list.
value with a value of your choice, the 2. Click the button next to the Sub-Category drop-down.
replacement is successful only if the The Enum dialog box appears.
value of your choice is not in use by any 3. Click the check box Load from Standard list to load
other object. the range from the standard list.
Update Interval The rate at which the output object is or
updated. Click Add to create your own custom enumeration type.
Enter the New Enum name and click Save.
4. Click OK.

EN2Z-0960GE51 R0710 44
 CENTRALINE LYNX TOOL - USER GUIDE

Point Conversion
What do I want to To what do I want to
convert? convert? How do I do it? What is the effect?
Network Output Binary Output 1. Right-click the Network output 1. If there are any free pins avail-
block and select Configure Prop- able, the resulting physical IO
erties. object gets an IO pin. 
2. Select Binary Output from the If no pin is available, the result-
Point Type list. ing physical IO becomes an
3. Click OK. invalid IO (IO with no pin).
2. If the point is connected to any
functional block, the functional
block slot type and links are
retained.
Network Output Modulating Output 1. Right-click the Network output 1. If there are any free pins avail-
block and select Configure Prop- able, the resulting physical IO
erties. object gets an IO pin. 
2. Select Modulating Output from If no pin is available, the result-
the Point Type list. ing physical IO becomes an
3. A warning message appears. invalid IO (IO with no pin).
Click Yes to continue. 2. If the point type is connected to
4. Click OK. any functional block, the function
block slot type and links are
retained.

45 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

EDITING SOFTWARE POINTS

To edit a software point in Lon or Bacnet network: 3. The summary page appears with a list of pre-pro-
1. Browse to Station > Config > Drivers > LonNetwork > grammed Mandatory, Fixed, and Custom NVs/Objects
LonLYNX. and Software points.
or 4. Select the software point you want to edit from the bot-
Browse to Station > Config > Drivers > BacnetNet- tom half of the Object Configuration View and click the
work > BacnetLYNX. Edit Point button. The Configure Properties dialog
2. Select ControlProgram > Views > NV Configuration box appears.
View for Lon. 5. Click OK to save the changes or Cancel to close the
or Configure Properties dialog box without saving the
Select ControlProgram > Views > Object Configura- changes.
tion View for Bacnet.

Network Input
Name Definition
Point Name The name of the software point.
Point Type Enables you to select Constant, Network Input, Network Setpoint, Binary Input or
Modulating Input.
Point Category Select a unit of measurement for the Point Type.
Unit to be used within Logic Select the engineering unit based on the Point Category.
Sub-Category Select the enumeration type for the software points. The field Unit to be used within logic is
renamed as Sub-Category if the Point Category selection is Unitless.
Value This field is enabled when the Point Type is Network Setpoint or Constant. The field enables
you to provide a setpoint or constant input value.
Advanced Object Name is automatically provided by the tool and can be edited. Object Instance number
can also be edited. Object Type is a read only field and cannot be edited.

Network Setpoint
Name Definition
Point Name The name of the software point.
Point Type Enables you to select Constant, Network Input, Network Setpoint, Binary Input or
Modulating Input.
Point Category Select a unit of measurement for the Point Type.
Unit to be used within Logic Select the engineering unit based on the Point Category.
Sub-Category Select the enumeration type for the software points. The field Unit to be used within logic is
renamed as Sub-Category if the Point Category selection is unitless.
Value Enables you to provide a setpoint input value. Check the Configure Invalid option to disable the
Value field.
Advanced Object Name is automatically provided by the tool and can be edited. Object Instance number
can also be edited. Object Type is a read only field and cannot be edited.

EN2Z-0960GE51 R0710 46
 CENTRALINE LYNX TOOL - USER GUIDE

Constant Name Definition

Name Definition Point Category Select a unit of measurement for the

Point Type.
Point Name The name of the software point.
Unit to be used within Select the engineering unit based on
Point Type Enables you to select Constant, logic the Point Category.
Network Input, Network Setpoint,
Binary Input or Modulating Input. Sub-Category Select the enumeration type for the
software points. The field Unit to be
Point Category Select a unit of measurement for the used within logic is renamed as
Point Type. Sub-Category if the Point Category
Unit to be used within Select the engineering unit based on selection is Unitless.
logic the Point Category. Advanced Object Name is automatically
Sub-Category Select the enumeration type for the provided by the tool and can be
software points. The field Unit to be edited. Object Instance number can
used within logic is renamed as also be edited. Object Type is a read
Sub-Category if the Point Category only field and cannot be edited.
selection is Unitless.
Value Enables you to provide a constant
input value.
Advanced Object Name is automatically
provided by the tool and can be
edited. Object Instance number can
also be edited. Object Type is a read
only field and cannot be edited.

Network Output
Name Definition
Point Name The name of the software point.
Point Type Enables you to select Constant,
Network Input, Network Setpoint,
Binary Input or Modulating Input.

47 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

NETWORK VARIABLES
A Network Variable (NV) is a data item such as a temperature, NOTE: Make sure that Mandatory and Fixed NVs should be
a switch value or actuator state. NVs can be thought of simply created as per the model selected. If you expose the
as point parameters. LonMark functional profiles define point of such fixed or droppable NVs which are
Standard Network Variable Types (SNVTs), but additional removed in the next selected model ( the reason
non-standard NVs are usually available, depending on the could be that the next selected model does not sup-
device, to store additional non-standard data. port the NV) then that point becomes an invalid point.
There are three categories of NVs that the CentraLine LYNX Note: The LYNX tool permits downloading or upload-
supports. They are: ing network and internal data type information of all
NV fields.
• Mandatory: Mandatory NVs are the default NVs
compulsorily present in a Lon LYNX device. The LonLYNX provides the following four built-in functions that
• Fixed: You can use Fixed Dropable NVs while creating an enable you to connect function blocks with other function
application logic but can edit only its Internal Data Type. blocks.
You can also display Fixed Dropable NVs on the wiresheet.
• Custom: Custom NVs are the NVs you create while • NVI - Network Variable Inputs
creating an application logic. They can be created, edited, • NVO - Network Variable Output
and deleted based on your requirements. • NCI - Network Configuration Input
• Many to One NV - Many to One Network Variable
The CentraLine LYNX provides built-in functions, Network
The following is a list of mandatory and fixed NVs supported Variable Inputs, to allow the selection of variables that are
by LYNX. available from/to the network. The configured network
NvName Data Type NV Type variables are mapped to the Function Block memory space to
be used by any Function Block. Each Network variable may
nroPgmVer UNVT_pgmVer Mandatory be configured with a name.
nvoNodeStatus SNVT_obj_status Mandatory
nviFileRequest SNVT_file_req Mandatory Viewing the List of Network Variables
nvoFileStatus SNVT_file_status Mandatory 1. Browse through to Station > Config > Drivers > Lon-
nviFilePos SNVT_file_pos Mandatory Network > LonLYNX.
2. Select ControlProgram > Views > NV Configuration
nviNodeRequest SNVT_obj_request Mandatory View. The summary page appears with a list of pre-pro-
nvoConfigError UNVT_configError Mandatory grammed Mandatory, Fixed, and Custom NVs in a tabu-
nciApplVerNew UCPT_applVerNew Mandatory lar format. The table has the following columns:
— NV Name: The name of the network variable.
nviDebugIndex UNVT_debugIndex Mandatory — Type: Indicates if the NV is of type NVI, NVO, NCI or
nvoDebug1 UNVT_debug Mandatory Many to One NV.
— Category: Indicates if the NV is Mandatory, Fixed,
nvoDebug2 UNVT_debug Mandatory Fixed Dropable, or Custom.
nciDeviceName UCPT_devName Mandatory — NV Container: Indicates where the NV is used.
nviInUse UNVT_inUse Mandatory 3. The bottom half of the NV Configuration View displays
the software points available on the wiresheet in a tabu-
nvoAlarmH UNVT_alarm Mandatory lar format. The table has the following columns:
nvoAlarmStatus UNVT_alarmStatus Mandatory — Point Name: The name of the software point (Network
Input/Network Setpoint/Network Output) as it appears
nvoError UNVT_error Mandatory on the wiresheet.
nciAlarmInhibit UCPT_alarmInhibit Mandatory — Field Names: Indicates if the NV is of type NVI, NVO,
nciSndHrtBt SCPTmaxSendTime Mandatory NCI or Many to One NV.
— Point Container: Indicates where the software point is
nciRcvHrtBt SCPTmaxRcvTime Mandatory used. All software points that are used in a Program
nvoWMCommError UNVT_WMCommError Mandatory within an application are also listed.
nciUICalOffset UCPT_uiCalOffset Fixed
nviTimeSet SNVT_time_stamp Fixed
nvoTime SNVT_time_stamp Fixed
nvoIO1 UNVT_io1 Fixed
nvoIO2 UNVT_io2 Fixed
nvoIO3 UNVT_io3 Fixed
nviManVal UNVT_manVal Fixed

EN2Z-0960GE51 R0710 48
 CENTRALINE LYNX TOOL - USER GUIDE

NOTE:

— Mandatory NVs cannot be used in the application Name Definition

logic. Group as Select this option if you want to save the fields
— Mandatory NVs cannot be edited or deleted. New NV you want to group as a new NV. In this case,
— In a Fixed NV, only Internal Data Type can be you can enter a new NV Name.
modified. Note: The new NV is created on the same folder
— Custom NV is the user defined NV. A Custom NV on which the Group as NV option is invoked.
can be edited or deleted. Example: If you have a ControlProgram which
— Fixed NVs marked as Fixed_Dropable can be has an Application2 residing in Application1, if
exposed on the wiresheet. Other fixed NVs can- you group points on the NV Configuration
not be exposed as points. View of Application2, the new NV is created in
— For each point that is copied and pasted on the the Application2 folder. However, if you grouped
wiresheet, a new NV of SNVT type nearest to the NVs on the NV Configuration View of the
selected data type is created automatically. Application1, the new NV is created in the
— When a user changes the device model, if the Application1 folder.
name of a custom NV clashes with a fixed NV
name in the target model, CentraLine LYNX gen- Add to Select this option if you want to add the points
erates a new unique name for the custom NV and Existing NV you want to group to an existing NV. In this
creates the new fixed NV case, you can select an existing custom NVI/
NCI from the NV Name list.
On selecting this option, the fields of the NV to
Group NVs which the new points will be added are listed in
You can group multiple points spread across NVs into a single the Fields Properties table.
new NV or add it to an existing one. The points must be Note: In the case where the selected NVI was of
available on the wiresheet to make such a grouping possible. a SNVT type, the NV is converted to a UNVT
Multiple points of an NV of the type NVI and NCI can be after grouping of points is done.
grouped together to create a new NV. The new NV created
can be saved as an NVI or NCI. When one or more NVs are NV Name The name that you can configure this NV with.
grouped. NV Type The NV type you want to save the selected
Also, invalid points can be grouped with fields of another NV fields as. You can choose NVI or NCI.
to create a new NV. Fields Displays the following properties for each field:
You can also group a single point belonging to an NV. In this Properties • Field Name
case a new NV is created • Data Category
• Network Data Type
NOTE: The Group as NV option is not available for software • Internal Data Type
points of type:
Up Arrow Use this button to reorder a field.
— Network Output (NVO points) Down Use this button to reorder a field.
— ManyToOneNV Arrow
— Network Input/Network Setpoint Field Name User defined field name.
— Software points of a ManyToOneNV if at least one
or whose network datatype of the corresponding Data Select the data type for the NV fields.
field is configured as bit field is selected Category
— Fixed NV fields exposed as points Network It is the engineering unit received by the
To group fields as NVs: Data Type CentraLine LYNX controller. Specify the
1. On the NV Configuration View, select the fields that Network Data Type. Based on data category
you want to group from the Software points available selected, the drop-down list changes.
on wiresheet list. Internal It is the unit(s) of the output of the Network
Data Type Variable. Specify the Internal Data Type. Based
NOTE: Use the CTRL key on your keyboard to select the dif- on data category selected, the drop-down list
ferent fields you want to group. changes.
2. Click the Group as NV button. The Confirmation dialog Value You can edit this option for an NCI.
box appears, if you are trying to group fields belonging UNVT Enter UNVT Name in case you are creating a
to NVI or NCI. Also, the fields will be deleted from the Name new NVI.
NVs from which they are being selected. If a field was
the only field in an NV, and it was selected to be 5. Click OK. The new NV is created and appears in the
grouped as an NV, the NV from which it is being NVs list in the NV Configuration View. If you select
selected is deleted. You will not see this dialog box if Add to an existing NV, the fields are added to the
you are grouping fields of NVOs. existing NV and can be seen in the NVs list.
3. Click OK. The Group as NV dialog box appears. The following table summarizes how you can group a point(s)
4. Fill the necessary information in the fields as explained of an NV.
in the following table.

49 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

Valid Invalid
Valid Invalid Network Network
Software Software Constant Output Output
NVI NCI NVO Input Point Input Point Point Point point
NVI Yes Yes No Yes Yes Yes No No
NCI Yes Yes No Yes Yes Yes No No
Valid Software Input Yes Yes No Yes Yes Yes No No
Point
Invalid Software Input Yes Yes No Yes Yes Yes No No
Point
Constant Point Yes Yes No Yes Yes Yes No No
NVO No No Yes No No No Yes Yes

Network Variable Input — You cannot add a Software Output to a macro.

The Network Variable Input (NVI) converts a raw network
variable input into a value(s) that can be used by other Name Definition
function blocks. NVName The name that you can configure this NVI with.
NOTE: The maximum limit of the fields is based on the Fail Detect Set the Fail Detect of each NVI to either True or
memory limitation of a selected controller model and False.
NV size cannot exceed 31 bytes. • True: if the Network Variable Input is bound
and it has not received an update from the
Each field is converted from Network Data Type to Internal Lon network source in the fail detect time,
Data Type engineering units. Network Data Type is the then an alarm is generated and the Network
engineering unit received by the CentraLine LYNX controller. Variable Input is set to Invalid.
Internal Data Type is the unit(s) of the output of the Network • False: the Network Variable Input will retain
Variable. what was written to it until a Lon network
source changes it or the CentraLine LYNX
Example: Programming the Network Data Type to be
has a power outage or resets.
SNVTtempp, and the Internal Data Type to be DegF, converts
network temperatures of type SNVTtempp into DegF for use Copy NV Enables you to select Standard NVs or User
by the Function Blocks. From Defined NVs (NVs you created and saved
earlier).
Adding an NVI Standard If you select Standard NV, you can choose a list
You can add an NVI from: NV of available NVs from the Select list. Standard
NVs are pre-defined NVs known as SNVTs.
• NV Configuration View
• CentraLineLYNX Palette Custom NV If you select Custom you can choose a list of
available NVs from the Select list. NVs you
have created. This is taken from UNVT Name
Adding an NVI from the NV Configuration View field.
To add a new Network Variable Input:
Fields Displays the following properties for each field:
1. Navigate to Station > Config > Drivers > LonNetwork Properties • Field Name
> LonLYNX. • Data Category
2. Select ControlProgram > Views > NV Configuration • Network Data Type
View. The summary page appears with a list of pre-pro- • Internal Data Type
grammed Mandatory, Fixed, and Custom NVs.
Add Field Use this button to add a field. You can add a
NOTE: If adding an NVI to a Program, browse through to the maximum of 99 fields.
appropriate Program on the Nav palette. Delete Field Use this button to delete a field.
Edit
3. Click Add NV. The New NV dialog box appears. Select
Selected
Network Variable Input.
Field
4. Click OK. The Add NVI dialog box appears. Select Net-
work Variable Input. Field Name Enter a name for the field. The default names of
5. Fill the necessary information in the fields and click OK fields being Field_x, where x is from 1 to 99.
to complete adding an NVI. The NVI is displayed in the Data Select the data type for the NV fields.
NVs table. Category
NOTE: You cannot add an NVI to a macro. You can only add
a Constant point to a macro.

EN2Z-0960GE51 R0710 50
 CENTRALINE LYNX TOOL - USER GUIDE

Network It is the engineering unit received by the 3. Click Cancel if you do not wish to continue adding an
Data Type CentraLine LYNX controller. Specify the NVI.
Network Data Type. Based on data category
selected, the drop-down list changes. Adding an NVI from the LYNX Palette
Internal It is the unit(s) of the output of the Network While in the midst of creating an ControlProgram/Program, if
Data Type Variable. Specify the Internal Data Type. Based you need to quickly add an NVI, use the Software Inputs item
on data category selected, the drop-down list on the LYNX Palette.
changes.
NOTE: You cannot add an NVI to a macro. You can only add
UNVT Enter UNVT Name in case you are creating a
a Constant point to a macro.
Name new NVI.
>> Click this button to view the Facets Details To add an NVI to an ControlProgram/Application:
Viewer for the network/internal data type. 1. On the LYNX Palette, expand the SoftwarePoints
The following information is displayed: folder. If the LYNX Palette is not visible on the left side
• Minimum – The minimum limit for selected of your screen, on the Menu bar, click Windows > Side-
unit bars > Palette to display the Palette.
• Maximum– The maximum limit for selected 2. Drag and drop a Network Input to the wiresheet of an
unit ControlProgram/Application. The Name dialog box
OR appears.
3. Enter a name for the point and click OK.
• Range - Indicates the possible enumeration 4. Right click the Network Input point you have just added
with their ordinal for a selected unit. and select Configure Properties. The Configure
• Units - Indicates the units symbol for the Properties dialog box appears.
selected unit (If it shows null, it means the 5. Enter/select the following:
unit symbol is not applicable there) — Point Name: Enter a name for the point.
• Type - Indicates the data type size for — Point Category: Select a category.
selected unit — Unit to be used within Logic: Select the unit for the
F32 - 4 Bytes Point Category chosen.
U16 – Unsigned 2 bytes — Value: This is disabled.
S16 – Signed 2 bytes 6. Click OK to complete adding an NVI.
U8 – Unsigned byte
S8 – Signed byte NOTE: When you create an NV using the LYNX Palette on
E8 - Enumerated byte the wiresheet, by default, the fields are exposed and
UB – Unsigned bit you do not have to manually expose the fields of the
• Resolution - Scaling factor for the selected NVI on the wiresheet.
Unit. When a value is written to controller, the
value is divided by the value specified in the
Resolution field and when it is read from the Connecting NVIs
controller, it is multiplied by the Resolution Once you have created an NVI, you can connect an NVI to an
value before it is displayed in Niagara. NVO/Function Block or Physical point by left-clicking on the
• Precision - Precision for the selected Unit output of an NVI and dragging your mouse to the input of an
NVO/Function Block or Physical point.
NOTE: You can create new NVs even if the NV count, field You can group multiple points spread across NVs into a single
count, or unit stores count has been exceeded. Cen- new NV or add it to an existing one. The points must be
traLine LYNX displays a message informing the available on the wiresheet to make such a grouping possible.
same but allows creation of NVs. Multiple points of an NV of the type NVI and NCI can be
grouped together to create a new NV. The new NV created
Exposing an NVI field from the NV Configuration can be saved as an NVI or NCI. When one or more NVs are
grouped.
View
Also, invalid points can be grouped with fields of another NV
To expose the NV fields you have added:
to create a new NV.
1. Expand the NVI in the table to display the fields. Select
You can also group a single point belonging to an NV. In this
the fields you want to display on the wiresheet and click
case a new NV is created.
the Show on wiresheet as Points button
or
NOTE: The Group as NV option is not available for software
Drag and drop the fields you want to display on the
points of type:
wiresheet on to Software Points available on
wiresheet list at the bottom of your screen on the right
— Software Output (NVO points)
side. The Add Points dialog box appears.
— ManyToOneNV
2. Click OK. The fields you have selected appear on the
— Network Input/Network Setpoint
Software Points available on wiresheet list at the bot-
— Software points of a ManyToOneNV if at least one
tom of your screen on the right side. The field name dis-
or whose network data type of the corresponding
plays the NV Name. Field Name information. If you do
field is configured as bit field is selected
not select point to be displayed on the wiresheet, the
— Fixed NV fields exposed as points
NV is added but is not visible on the wiresheet.

51 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

Grouping Points of type NVI — If you group invalid software input points (an invalid
You can group two or more points of type NVI, NCI, valid NVI point) to form an NVI/NCI, the invalid NVI point is
software input point, invalid software input point, or software converted to a valid NVI/NCI point.
input point configured as constant to: — When a software input point configured as a Constant
is grouped to form an NVI or NCI, the software point is
— Create a new NVI converted to a NVI/NCI point and any links from that
— Add to an existing NVI point to functional blocks slots is broken. Such func-
— Create a new NCI tional block slots are converted to Connector type of
— Add to an existing NCI slots. he links are broken only when the target prop-
When grouping to create a new NVI/NCI, the number of fields erty type in the function blocks is CONSTANT_ONLY,
of the new NVI equals the number of software points selected else, target property type is converted to CONNEC-
for grouping. When you group points to add to an existing NVI/ TOR and the link is retained.
NCI, the selected software output points are added to the — The result of copying and pasting an invalid Network
existing fields of the selected target NVI/NCI. The new/edited input/setpoint/output point in the wiresheet is the cre-
NVI/NCI appears in the upper pane in the list of NVs in the NV ation of an invalid Network input/setpoint/output point.
Configuration View. The lower pane in the NV — When a folder contains some software points (NVI/
Configuration View displays the list of all NVs with which a NCI/NVO points) whose NVs are present in other fold-
particular software output has been grouped. ers (other than its child folders), the points become
The result of such a grouping is that the previous NVI/NCI is invalid as the reference to the NV is lost.
modified such that the corresponding field to this point is — If points selected for grouping have a mixture of soft-
removed from the NV. The NV is deleted if the NV was a ware input and output points, Group as NV option is
single field NV. This happens when points selected are not available
already attached to an existing NV. The following table summarizes how you can group a point(s)
of a source NV to form a target NV..
NOTE:
Target NV
Valid Invalid
Valid Invalid Network Network
Software Software Constant Output Output
Source NV Points NVI NCI NVO Input Point Input Point Point Point point
NVI Yes Yes No Yes Yes Yes No No
NCI Yes Yes No Yes Yes Yes No No
Valid Software Input Yes Yes No Yes Yes Yes No No
Point
Invalid Software Input Yes Yes No Yes Yes Yes No No
Point
Constant Point Yes Yes No Yes Yes Yes No No
NVO No No Yes No No No Yes Yes

To group points of NVIs: 2. Click the Group as NV button. The Confirmation dia-
1. On the NV Configuration View, select the fields that log box appears. The fields are deleted from the NVs
you want to group from the Software points available on from which they are being selected. 
wiresheet list. If you select a field from an NV (for grouping) in which it
was the only field, the NV from which it is being selected
NOTE: Use the CTRL key on your keyboard to select the dif- is deleted.
ferent fields you want to group.

EN2Z-0960GE51 R0710 52
 CENTRALINE LYNX TOOL - USER GUIDE

3. A message appears warning you that if the selected Data Select the data type for the NV fields.
point is attached to an NV, grouping will delete that point Category
from that NV. Click OK. The Group as NV dialog box
appears. Network Data It is the engineering unit received by the
4. Fill the necessary information in the fields as explained Type CentraLine LYNX controller. Specify the
in the following table. Network Data Type. Based on data category
selected, the drop-down list changes.
Internal Data It is the unit(s) of the output of the Network
Name Definition
Type Variable. Specify the Internal Data Type.
Group as Select this option if you want to save the Based on data category selected, the drop-
New NV selected fields you want to group as a new NV. down list changes.
In this case, you can enter a new NV Name.
UNVT Name Enter UNVT Name in case you are creating a
new NVI. This is not mandatory.
NOTE: The new NV is created on the same
folder in which the NV Configuration
View is invoked. Example: If you 5. Click OK. The new NV is created and appears in the
have a ControlProgram which has an NVs list in the NV Configuration View. If you select
Application2 residing in Application1, Add to an existing NV, the fields are added to the
if you group points on the NV Config- existing NV and can be seen in the NVs list.
uration View of Application2, the
new NV is created in the Application2
folder. However, if you grouped NVs Network Configuration Input
on the NV Configuration View of the NCI is a Network Configuration Input.
Application1, the new NV is created
in the Application1 folder.
Adding an NCI
Add to Select this option if you want to add the points You can add an NCI from:
Existing NV you want to group to an existing NV. In this
case, you can select an existing custom NVI/ • NV Configuration View
NCI from the NV Name list. • CentraLineLYNX Palette
On selecting this option, the fields of the NV to
which the new points will be added are listed Adding an NCI from the NV Configuration View
in the Fields Properties table. To add a new Network Configuration Input:
NOTE: 1. Navigate to Station > Config > Drivers > LonNetwork
> LonLYNX.
— In this case, the selected existing NV 2. Select ControlProgram > Views > NV Configuration
is edited to reflect the changes. View. The summary page appears with a list of pre-pro-
— In the case where the selected NVI grammed Mandatory, Fixed, and Custom NVs.
was of a SNVT type, the NV is con-
verted to a UNVT after grouping of NOTE: If adding an NCI to an Application, browse through to
points is done the appropriate Application on the Nav palette.

NV Name The name that you can configure this NV with. 3. Click Add NV. The New NV dialog box appears. Select
NV Type The NV type you want to save the selected Network Configuration Input.
fields as. You can choose NVI or NCI. 4. Click OK. The Add NCI dialog box appears.
5. Fill the necessary information in the fields and click OK
Fields Displays the following properties for each field: to complete adding an NCI. The NCI is displayed in the
Properties — Field Name NVs table.
— Data Category
— Network Data Type NOTE:
— Internal Data Type
Up Arrow Use this button to reorder a field and move it — You cannot add an NCI to a macro. You can only
up in the list. add a Constant point to a macro.
Down Arrow Use this button to reorder a field and move it — You can create new NVs even if the NV count,
down in the list. field count, or unit stores count has been
exceeded. CentraLine LYNX displays a message
Point Name The name of the point. informing the same but allows creation of NVs.
Field Name User defined field name.

53 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

Exposing an NCI from the NV Configuration View Internal Data It is the unit(s) of the output of the Network
To expose the NV fields you have added: Type Variable. Specify the Internal Data Type.
1. Expand the NCI in the table to display the fields. Select Based on data category selected, the drop-
the fields you want to display on the wiresheet and click down list changes.
the Show on wiresheet as Points button Value Indicates the default value of the selected
or variable. You can edit this field. The units are
Drag and drop the fields you want to display on the based on the Internal Data Type selected.
wiresheet on to Software Points available on Configure Use this option to configure an invalid value.
wiresheet list at the bottom of your screen on the right Invalid Consequently, the Value field is disabled and
side. The Add Points dialog box appears. displays NaN.
2. Click OK. The fields you have selected appear on the
Software Points available on wiresheet list at the bot- UNVT Name Enter UNVT Name in case you are creating a
tom of your screen on the right side. The field name dis- new NCI.
plays the NV Name. Field Name information. If you do >> Click this button to view the network/internal
not select point to be displayed on the wiresheet, the data type details.
NV is added but is not visible on the wiresheet. Click this button to view the Facets Details
3. Click Cancel if you do not wish to continue adding an Viewer for the network/internal data type.
NCI.
. The following information is displayed:
Name Definition
• Minimum – The minimum limit for selected
NVName The name that you can configure this NVI unit
with. • Maximum– The maximum limit for selected
Copy From Enables you to select Standard NVs or User unit
Defined NVs. OR
• Range - Indicates the possible
Standard If you select Standard, you can choose a list enumeration with their ordinal for a
of available NVs from the Select list. Standard selected unit.
NVs are pre-defined NVs known as SNVTs. • Units - Indicates the units symbol for the
Custom If you select Custom you can choose a list of selected unit (If it shows null, it means the
available NVs from the Select list. NVs you unit symbol is not applicable there)
have created. This is taken from UNVT Name • Type - Indicates the data type size for
field. selected unit
Field Displays the following properties for each field: — F32 - 4 Bytes
Properties • Field Name — U16 – Unsigned 2 bytes
• Data Category — S16 – Signed 2 bytes
• Network Data Type — U8 – Unsigned byte
• Internal Data Type — S8 – Signed byte
• Value — E8 - Enumerated byte
— UB – Unsigned bit
Add Field Use this button to add a field. You can add a • Resolution - Scaling factor for the selected
maximum of 16 fields. Unit. When a value is written to controller,
Delete Field Use this button to delete a field. the value is divided by the value specified
in the Resolution field and when it is read
Edit Selected from the controller, it is multiplied by the
Field Resolution value before it is displayed in
Field Name User defined field name. Niagara.
Data Select the data type for the NV fields. • Precision - Precision for the selected Unit
Category
Network Data It is the engineering unit received by the
Type CentraLine LYNX controller. Specify the
Network Data Type. Based on data category
selected, the drop-down list changes.

EN2Z-0960GE51 R0710 54
 CENTRALINE LYNX TOOL - USER GUIDE

Adding an NCI from the LYNX Palette — Software Output (NVO points)
While in the midst of creating an ControlProgram/Program, if — Many to one NV
you need to quickly add an NCI, use the Software Inputs item — Network Input/Network Setpoint
on the LYNX Palette. — Software points of a ManyToOneNV if at least one
or whose network data type of the corresponding
NOTE: field is configured as bit field is selected
— Fixed NV fields exposed as points
— You cannot add an NCI to a macro. You can only
add a Software Input with Point Type as Con- Grouping Points of type NCI
stant to a macro. You can group two or more points of type NVI, NCI, Valid
— You cannot add a Software Output to a macro. Network Input/Setpoint, Invalid Network Input/Setpoint, or
Constant point to:
To add an NCI to an ControlProgram/Application: — Create a new NCI
1. On the LYNX Palette, expand the SoftwarePoints — Add to an existing NCI
folder. — Create a new NVI
— Add to an existing NVI
NOTE: If the LYNX Palette is not visible on the left side of When grouping to create a new NVI/NCI, the number of fields
your screen, on the Menu bar, click Windows > of the new NV equals the number of software input points
Sidebars > Palette to display the LYNX Palette. selected for grouping. When you group points to add to an
existing NVI/NCI, the selected software input points are added
2. Drag and drop a Network Setpoint to the wiresheet of to the existing fields of the selected target NVI/NCI. The new/
an ControlProgram/Program. The Name dialog box edited NVI/NCI appears in the upper pane in the list of NVs in
appears. the NV Configuration View. The lower pane in the NV
3. Enter a name for the point and click OK. Configuration View displays the list of all NVs with which a
4. Right click the Network Setpoint you have just added particular software input has been grouped.
and select Configure Properties. The Configure The result of such a grouping is that the previous NVI/NCI is
Properties dialog box appears. modified such that the corresponding field to this point is
5. Enter/select the following: removed from the NV. The NV is deleted if the NV was a
— Point Name: Enter a name for the point. single field NV. This happens when points selected are
— Unit to be used within Logic: Select the unit for the already attached to an existing NV.
Point Category chosen.
— Value: Enter a value based on the Point Category NOTE: If you group invalid software input points (an invalid
and Units to be used within Logic fields chosen. NCI point) to form an NVI/NCI, the invalid NCI point
6. Click OK to complete adding an NCI. is converted to a valid NVI/NCI point.
NOTE: When you create an NV using the LYNX Palette on — When a software input point configured as a Con-
the wiresheet, by default, the fields are exposed and stant is grouped to form an NVI or NCI, the soft-
you do not have to manually expose the fields of the ware point is converted to a NVI/NCI point and
NCI on the wiresheet. any links from that point to functional blocks slots
is broken. Such functional block slots (Property/
Connecting NCIs Input Type) are converted to Connector type of
Once you have created an NCI, you can connect a point of an slots. The links are broken only when the target
NCI to an NVO/Function Block/Physical point by left-clicking property type in the function blocks is
on the output of a point of an NCI and dragging your mouse to CONSTANT_ONLY, else, target property type is
the input of an NVO/Function Block/Physical point. converted to CONNECTOR and the link is
retained.
You can group multiple points spread across NVs into a single — The result of copying and pasting an invalid Net-
new NV or add it to an existing one. The points must be work Input/Setpoint/Output point in the wiresheet
available on the wiresheet to make such a grouping possible. is the creation of an invalid Network Input/Set-
Multiple points of an NV of the type NVI and NCI can be point/Output point.
grouped together to create a new NV. The new NV created — When a folder contains some software points
can be saved as an NVI or NCI. When one or more NVs are (NVI/NCI/NVO points) whose NVs are present in
grouped. other folders (other than its child folders), the
Also, invalid points can be grouped with fields of another NV points become invalid as the reference to the NV
to create a new NV. is lost.
You can also group a single point belonging to an NV. In this — If points selected for grouping have a mixture of
case a new NV is created. software input and output points, Group as NV
option is not available.
NOTE: The Group as NV option is not available for software
points of type:

55 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

The following table summarizes how you can group a point(s)

of a source NV to form a target NV.
Target NV
Valid Software Valid Network
Source NV Points NVI NCI NVO Input Point Output Point
NVI Yes Yes No Yes No
NCI Yes Yes No Yes No
Valid Software Input Point Yes Yes No Yes No
Invalid Software Input Point Yes Yes No Yes No
Constant Point Yes Yes No Yes No
NVO No No Yes No Yes

To group points of NCIs: Name Definition

1. On the NV Configuration View, select the fields that Group as Select this option if you want to save the
you want to group from the Software points available New NV selected fields you want to group as a new
on wiresheet list. NV. In this case, you can enter a new NV
Name.
NOTE: Use the CTRL key on your keyboard to select the dif-
ferent fields you want to group. NOTE: The new NV is created on the same
folder in which the NV Configura-
2. Click the Group as NV button. The Confirmation dia- tion View is invoked. Example: If you
log box appears. The fields are deleted from the NVs have a ControlProgram which has an
from which they are being selected.  Application2 residing in Application1,
If you select a field from an NV (for grouping) in which it if you group points on the NV Con-
was the only field, the NV from which it is being selected figuration View of Application2, the
is deleted. new NV is created in the Application2
3. A message appears warning you that if the selected folder. However, if you grouped NVs
point is attached to an NV, grouping will delete that point on the NV Configuration View of
from that NV. Click OK. The Group as NV dialog box the Application1, the new NV is cre-
appears. ated in the Application1 folder.
4. Fill the necessary information in the fields as explained
in the following table. Add to Select this option if you want to add the points
Existing NV you want to group to an existing NV. In this
case, you can select an existing custom NVI/
NCI from the NV Name list.
On selecting this option, the fields of the NV to
which the new points will be added are listed
in the Fields Properties table.

NOTE:

— In this case, the selected existing

NV is edited to reflect the
changes.
— In the case where the selected
NVI was of a SNVT type, the NV
is converted to a UNVT after
grouping of points is done
NV Name The name that you can configure this NV with.
NV Type The NV type you want to save the selected
fields as. You can choose NVI or NCI.
Fields Displays the following properties for each
Properties field:
— Field Name
— Data Category
— Network Data Type
— Internal Data Type
Up Arrow Use this button to reorder a field and move it
up in the list.
Down Arrow Use this button to reorder a field and move it
down in the list.

EN2Z-0960GE51 R0710 56
 CENTRALINE LYNX TOOL - USER GUIDE

Point Name The name of the point. 1. Navigate to Station > Config > Drivers > LonNetwork
> LonLYNX.
Field Name User defined field name. 2. Select ControlProgram > Views > NV Configuration
Data Select the data type for the NV fields. View. The summary page appears with a list of pre-pro-
Category grammed Mandatory, Fixed, and Custom NVs.
3. Click New NV. The Select dialog box appears.
Network Data It is the engineering unit received by the
4. Select Many To One NV.
Type CentraLine LYNX controller. Specify the
5. Click OK. The Add Many-To-One NVI dialog box
Network Data Type. Based on data category
appears.
selected, the drop-down list changes.
6. Fill the necessary information in the fields and click OK
Internal Data It is the unit(s) of the output of the Network to complete adding a Many To One NV.
Type Variable. Specify the Internal Data Type.
Based on data category selected, the drop-
down list changes. Name Definition
UNVT Name Enter UNVT Name in case you are creating a NVName The name that you can configure this Many-To-
new NCI. This is not mandatory. One NVI with.
>> Click this button to view the network/internal Number of The minimum and maximum limits are 2 and 8.
data type details. Bound
Input NVs
Field Name This is non-editable.
5. Click OK. The new NV is created and appears in the
NVs list in the NV Configuration View. If you select Data Select the data type for the NV fields.
Add to an existing NV, the fields are added to the Category
existing NV and can be seen in the NVs list. Network It is the engineering unit received by the
Data Type CentraLine LYNX controller.
Many To One NV Internal It is the unit(s) of the output of the Network
Use this built-in function to bind an output from 2 to 8 other Data Type Variable.
network NVOs to a single network variable input on
CentraLine LYNX. The value from each controller is placed on NOTE: You can create new NVs even if the NV count, field
an output of the ManytoOne. For example, you can use the count, or unit stores count has been exceeded. Cen-
Minimum, maximum, Average or other function blocks to traLine LYNX displays a message informing the
combine them as per the application. same but allows creation of NVs.
The many to one network variable has a single input NV field.
The field can be 1, 2, or 4 bytes long. It can not be configured Exposing a Many-To-One NVI from the NV
for SNVT types. Configuration View
You can configure the input engineering units and the output To expose the NV fields you have added:
engineering units. All outputs have the same engineering unit.
1. Expand the Many-To-One NVI in the table to display the
You can configure from 2 to 8 outputs. Each output is the fields. Select the fields you want to display on the
value of the NVO of the corresponding source controller. As wiresheet and click the Show on wiresheet as Points
each output source is received on the input, it is assigned an button
output slot. CentraLine LYNX keeps track of the domain/ or
subnet/node of all NVs bound so that it can put new values Drag and drop the fields you want to display on the
into the proper output slot. wiresheet on to Software Points available on
The outputs are assigned on a first-come-first-served basis. wiresheet list at the bottom of your screen on the right
Data is not saved over a power outage. This means it is side. The Add Points dialog box appears.
possible the order may be different after each power outage. 2. Click OK. The fields you have selected appear on the
The Many-to-One input is not Fail Detect. However a fail Software Points available on wiresheet list at the bot-
detect timer is kept for each input source. nciRcvHrtBt is used tom of your screen on the right side. The field name dis-
for the timer. If the Timer expires the corresponding output is plays the NV Name. Field Name information. If you do
set to INVALID. not select point to be displayed on the wiresheet, the
If less source NVs are bound than are configured then the NV is added but is not visible on the wiresheet.
ones not received are set to Invalid. 3. Click Cancel if you do not wish to continue adding a
many-To-One NVI.
If more source NVs are bound than are configured, then any
sources received after the slots are filled are ignored.
Connecting Many To One NVs
The Many-to-one outputs are set to Invalid on power up/reset.
As NV updates are received, the corresponding output slot is Once you have created a Many To One NV, you can connect a
set to the received value. point of a Many To One NV to an NVO by left-clicking on the
output of a point of a Many To One NV and dragging your
To add a new Many To One Network Variable: mouse to the input of an NVO.

Grouping as NV
The Group as NV option is not available for software points of
the type Many to One NV.

57 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

Network Variable Output

The Network Variable Output (NVO) converts input value(s) Name Definition
(Public Variable(s)) into a raw network variable output that is NVName The name that you can configure this NVO with.
published onto the LonWorks network. Each NVO can be
defined with up to 16 fields. Output Set the Output Refresh of each NVO to either
Refresh Polled or Unpolled.
NOTE: The maximum limit of the fields is based on the • Output Refresh is only valid when the
memory limitation of a selected controller model and Guaranteed Periodic Refresh is set to False.
NV size cannot exceed 31 bytes. • If a Output Refresh is Polled, then the value
of the output network variable is never
Each field is converted from Internal Data Type to Network propagated as a result of its value changing.
Data Type engineering units. Internal data type is the units of Instead the value of the output network
the input of the Network Variable. Network Data Type is the variable is sent only in response to a poll
engineering unit sent by the CentraLine LYNX controller onto request from a reader node.
the LonWorks network. For example, programming the
Guaranteed Set Guaranteed Periodic Refresh of each
Network Data Type to be SNVT_temp_p, and the Internal
Periodic Network Variable Output to either True or False.
Data Type to be DegF converts network temperatures of type
Refresh • True indicates that the CentraLine LYNX
SNVT_temp_p into DegF for use by the Function Blocks.
controller periodically sends this variable to
the LonWorks network at the GPU rate
Adding an NVO (nciSndHrtBt). Setting this to True also
You can add an NVO from: enables the Significant Event Notification
• NV Configuration View also known as SEN Delta. The Network
• CentraLineLYNX Palette Variable is also sent on the LonWorks
Network whenever any field exceeds the
SEN Delta. SEN Delta of zero (0) disables
Adding an NVO from the NV Configuration View the feature.
To add a new Network Variable Output: • False indicates that the CentraLine LYNX
1. Navigate to Station > Config > Drivers > LonNetwork controller does not send the value to the
> LonLYNX. LonWorks network. The Network Variable
2. Select ControlProgram > Views > NV Configuration Output must be polled to get its value.
View. The summary page appears with a list of pre-pro- Message The Message Service type of each NVO is
grammed Mandatory, Fixed, and Custom NVs. Service Unacknowledged, Acknowledged or
Unacknowledged Repeated.
NOTE: If adding an NVO to a Program, browse through to • Unacknowledged means the update is sent
the appropriate Application on the Nav palette. once and no acknowledgement is expected.
• Acknowledged means all receiver nodes
3. Click Add NV. The New NV dialog box appears. must acknowledge receipt of the message to
4. Select Network Variable Output. the sender node.
5. Click OK. The Add NVO dialog box appears. • Unacknowledged Repeated means the
6. Fill the necessary information in the fields and click OK update is sent multiple times and no
to complete adding an NVO. The NVO is displayed in acknowledgements are expected.
the NVs table.
Copy From Enables you to select Standard NVs or User
Defined NVs.
NOTE:
Standard If you select Standard you can choose a list of
— You cannot add a Software Output to a macro. available NVs from the Select list. Standard
NVs are pre-defined NVs known as SNVTs.
Custom If you select Custom you can choose a list of
available NVs from the Select list. NVs you
have created. This is taken from UNVT Name
field.
Fields Displays the following properties for each field:
Properties Field Name
Data Category
Internal Data Type
Network Data Type
Significant Event Notification
Add Field Use this button to add a field. You can define a
maximum of 16 fields.
Delete Field Use this button to delete a field.

EN2Z-0960GE51 R0710 58
 CENTRALINE LYNX TOOL - USER GUIDE

Edit Exposing an NVO from the NV Configuration View

Selected To expose the NV fields you have added:
Field 1. Expand the NVO in the table to display the fields. Select
Field Name User defined field name. the fields you want to display on the wiresheet and click
Internal It is the unit(s) of the output of the Network the Show on wiresheet as Points button
Data Type Variable. Specify the Internal Data Type. Based or
on data category selected, the drop-down list Drag and drop the fields you want to display on the
changes. wiresheet on to Software Points available on
wiresheet list at the bottom of your screen on the right
Network It is the engineering unit received by the side. The Add Points dialog box appears.
Data Type CentraLine LYNX controller. Specify the 2. Click OK. The fields you have selected appear on the
Network Data Type. Based on data category Software Points available on wiresheet list at the bot-
selected, the drop-down list changes. tom of your screen on the right side. The field name dis-
Significant Indicates the sen delta value of the selected plays the NV Name. Field Name information. If you do
Event variable.You can edit this field. The units are not select point to be displayed on the wiresheet, the
Notification based on the Network Data Type selected. NV is added but is not visible on the wiresheet.
3. Click Cancel if you do not wish to continue adding an
UNVT Enter UNVT Name in case you are creating a NVO.
Name new NVO.
>> Click this button to view the network/internal
data type details.
Adding an NVO from the LYNX Palette
Click this button to view the Facets Details While in the midst of creating an ControlProgram/Application,
Viewer for the network/internal data type. if you need to quickly add an NVO, use the Software Outputs
item on the LYNX Palette.
The following information is displayed:
NOTE: You cannot add an NVO or a Software Output point
• Minimum – The minimum limit for selected to a macro.
unit
• Maximum– The maximum limit for selected To add an NVO to an ControlProgram/Application:
unit 1. On the LYNX Palette, expand the SoftwarePoints
OR folder.

• Range - Indicates the possible enumeration NOTE: If the LYNX Palette is not visible on the left side of
with their ordinal for a selected unit. your screen, on the Menu bar, click Windows >
• Units - Indicates the units symbol for the Sidebars > Palette to display the Palette.
selected unit (If it shows null, it means the
unit symbol is not applicable there) 2. Drag and drop a Software Output to the wiresheet of an
• Type - Indicates the data type size for ControlProgram/Program. The Name dialog box
selected unit appears.
— F32 - 4 Bytes 3. Enter a name for the point and click OK.
— U16 – Unsigned 2 bytes 4. Right click the Software Output point you have just
— S16 – Signed 2 bytes added and select Configure Properties. The Config-
— U8 – Unsigned byte ure Properties dialog box appears.
— S8 – Signed byte 5. Enter/select the following:
— E8 - Enumerated byte — Point Name: Enter a name for the point.
— UB – Unsigned bit — Point Type: By default Software Output is selected.
• Resolution - Scaling factor for the selected This is the only available option.
Unit. When a value is written to controller, the — Point Category: Select a category.
value is divided by the value specified in the — Unit to be used within Logic: Select the unit for the
Resolution field and when it is read from the Point Category chosen.
controller, it is multiplied by the Resolution 6. Click OK to complete adding an NVO.
value before it is displayed in Niagara.
• Precision - Precision for the selected Unit NOTE: When you create an NV using the LYNX Palette on
the wiresheet, by default, the fields are exposed and
NOTE: You can create new NVs even if the NV count, field you do not have to manually expose the fields of the
count, or unit stores count has been exceeded. Cen- NVO on the wiresheet.
traLine LYNX displays a message informing the
same but allows creation of NVs. Connecting NVOs
Once you have created an NVO, you can connect an NVO to
an NVI/Function Block or Physical point by left-clicking on the
output of an NVI/Function Block/Physical point and dragging
your mouse to the input of an NVO.

59 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

Grouping as NVOs — Deleting a software output point from the wiresheet

You can group (share) two or more NVO points, or valid/ modifies all the NVOs in which the point is grouped.
invalid software output points to: The field corresponding to the point is deleted in the
NVOs and if this happens to be the last field, the NVO
— Create a new NVO itself is deleted.
— Add to an existing NVO — If you group invalid software output points to NVOs,
When grouping to create a new NVO, the number of fields of the invalid software points are converted to valid soft-
the new NVO equals the number of software output points ware points.
selected for grouping. When you group points to add to an — The result of copying and pasting an invalid Network
existing NVO, the selected software output points are added Input/Setpoint/Output point in the wiresheet is the cre-
to the existing fields of the selected target NVO. In either ation of an invalid Network Input/Setpoint/Output
case, the structure of the source NVOs to which the points point.
originally belong are not affected. The new/edited NV appears — When a folder contains some software points(NVI/
in the upper pane in the list of NVOs in the NV Configuration NCI/NVO points) whose NVs are present in other fold-
View. The lower pane in the NV Configuration View displays ers (other than its child folders), the points become
the list of all NVOs to which a particular software output has invalid as the reference to the NV is lost.
been grouped into. — The following table summarizes how you can group a
point(s) of a source NV to form a target NV.
NOTE:

— The new NVO created by grouping of software output

points is created at the same Application folder level
as the one where the Group as NV operation screen is
invoked.
— You cannot edit a shared NVO point from the NV Con-
figuration View screen. To edit a shared NVO, you
must right-click the NVO on the wiresheet and select
Configure Properties. If you edit software point
details of an NVO, whose points are grouped, all
newly created NVOs in which the point is grouped are
modified. You can only edit field names of the points
selected to be grouped as NVO. This is true even if the
points are added to an existing NVO. However, no
information of the existing NVO fields is editable. Only
the field names of the newly selected points are edit-
able.

Target NV
Valid Invalid
Valid Invalid Network Network
Software Software Constant Output Output
Source NV Points NVI NCI NVO Input Point Input Point Point Point point
NVI Yes Yes No Yes Yes Yes No No
NCI Yes Yes No Yes Yes Yes No No
Valid Software Input Yes Yes No Yes Yes Yes No No
Point
Invalid Software Input Yes Yes No Yes Yes Yes No No
Point
Constant Point Yes Yes No Yes Yes Yes No No
NVO No No Yes No No No Yes Yes
To group points of NVOs:

EN2Z-0960GE51 R0710 60
 CENTRALINE LYNX TOOL - USER GUIDE

1. On the NV Configuration View, select the points of one NV Type The NVO type you want to save the selected
or more NVOs that you want to group from the Soft- points for grouping as.
ware points available on wiresheet list.
Fields Displays the following properties for each field:
NOTE: Use the CTRL key on your keyboard to select the dif- Properties — Field Name
ferent points you want to group. — Data Category
— Network Data Type
2. Click the Group as NV button. The Group as NV dialog — Internal Data Type
box appears. Up Arrow Use this button to reorder a field and move it
3. Fill the necessary information in the fields as explained up in the list.
in the following table.
Down Arrow Use this button to reorder a field and move it
down in the list.
Name Definition Point Name The name of the point. It is in the format
Group as Select this option if you want to save the NVName_PointName.
New NV points you want to group as a new NVO. In Field Name User defined field name.
this case, you can enter a new NVO Name.
Data Select the data type for the NV fields.
NOTE: The new NVO is created on the Category
same folder on which the NV Config- Network Data It is the engineering unit received by the
uration View is invoked. Example: If Type CentraLine LYNX controller. This is non-
you have a ControlProgram which editable.
has an Application2 residing in
Internal Data It is the unit(s) of the output of the Network
Application1, if you group points on
Type Variable. This is non-editable.
the NV Configuration View of
Application2, the new NVO is created UNVT Name Enter UNVT Name in case you are creating a
in the Application2 folder. However, if new NVO.
you grouped NVs on the NV Config-
uration View of the Application1, the
new NVO is created in the 4. Click OK. The new NVO is created and appears in the
Application1 folder. NVs list in the NV Configuration View. If you select
Add to an existing NV, the fields are added to the
Add to Select this option if you want to add the points existing NVO and can be seen in the NVs list.
Existing NV you want to group to an existing NVO. In this
case, you can select an existing custom NVO
from the NV Name list. Edit Network Variables
On selecting this option, the original fields of You can partially modify Fixed Dropable NVs and totally
the NVO to which the new points will be added modify Custom NVs. However, you cannot modify Mandatory
are listed in the Fields Properties table. and Fixed NVs.

NOTE: In the case where the selected NVO NOTE: If you delete a point of an NV and if this point is the
was of a SNVT type, the NV is con- only point in that NV, the NV itself is deleted.
verted to a UNVT after grouping of
points is done. The following table summarizes what you can or cannot do
NV Name The name that you can configure this NV with. with NVs in the Wiresheet and the NV Configuration Views.

61 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

Show NV on
Type Wiresheet Create Edit Delete
Wiresheet NV Config Wiresheet NV Config Wiresheet NV Config Wiresheet NV Config
View View View View
NVI Yes. Yes. Yes. Yes. Yes. Yes. Yes. Yes.
NCI Any NV added You need to You can only You can add You can only You can edit You can only You can
NVO to the add an NV add an NV an NV with edit an NV an NV with delete an NV delete an NV
wiresheet is and select with a single multiple with a single multiple with a single with multiple
automatically the points point. points. point at a points at a point at a points at a
displayed on you want to time. time. time. time.
the wiresheet be displayed • NVs of
on the Fixed
wiresheet by Dropable
clicking the type and
Display on NVs with
Wiresheet Bit
button. Configurat
ion are
not
deleted
but only
hidden
from the
wiresheet.
They are
still
available
in the NVs
list.
Many to Yes. Yes. No. Yes. No. Yes. Yes. Yes.
One Any NV added You need to You can add You can edit You can only You can
to the add an NV an NV with an NV with delete an NV delete an NV
wiresheet is and select multiple multiple with a single with multiple
automatically the points points. points at a point at a points at a
displayed on you want to time. time. time.
the wiresheet be displayed
on the
wiresheet by
clicking the
Display on
Wiresheet
button.

5.
If the NV is a Custom type, by default, the settings are
To edit an NV: such that you can change:
— Internal Data Type
1. Browse to Station > Config > Drivers > LonNetwork > — Fail Detect
LonLYNX. — SNVT Select
2. Select ControlProgram > Views > NV Configuration — Standard/User Defined NV
View. The summary page appears with a list of pre-pro- 6. Click OK to save the changes. However, for a Custom
grammed Mandatory, Fixed, and Custom NVs and Soft- NV, you can uncheck the Copy NV From check box
ware points. and change all parameters as described in Adding an
3. Select the Fixed/Custom NV you want to edit and click NVI/NCI/NVO, and Many to one NV sections of this doc-
the Edit NV button. ument.
4. The Edit NV: NV Name dialog box appears. If the Example: The nciSetPoints is an NV used in the Temperature
selected NV is a Fixed Dropable NV type, you can only Set Point Calculator. You can only change its Internal Data
change the Internal Data Type and click OK to save the Type and the Value.
changes.

EN2Z-0960GE51 R0710 62
 CENTRALINE LYNX TOOL - USER GUIDE

The following table summarizes editing network variables

from the Wiresheet and NV Configuration Views.
NV Type Action From Procedure
NVI/NCI/NVO Remove points from Wiresheet You cannot remove (hide) a point from the
wiresheet wiresheet.
Remove points from NV Configuration View 1. Select the exposed fields from the Soft-
wiresheet ware Points available on wiresheet list.
2. Click Remove Points from wiresheet.
3. Click OK to confirm.
Edit NV Wiresheet You can only edit individual points of an NV at a
time.
1. Right click the individual point of an NV
and select Configure Properties.
2. Edit the available fields and click OK to
save the changes.
Edit NV NV Configuration View You can edit multiple points of an NV at a time.
1. Select the NV from the NVs list on the
right side of your screen on top.
2. Click Edit NV and edit one or multiple
points of the NV at once.
3. Click OK to save the changes made.
Delete NV Wiresheet You can only delete individual points of an NV at
a time.
Delete NV NV Configuration View You can delete an NV with multiple points at a
time. To delete an NV with multiple points:
1. Select the NV from the NVs list on the
right side of your screen on top.
2. Click Delete NV.
3. Click OK to save the changes made.

You can also delete individual points in an NV

1. Select the NV from the NVs list on the
right side of your screen on top.
2. Click Delete NV.
3. Click OK to save the changes made.
Many to One NV Remove points from Wiresheet You can remove (hide) a point from the
wiresheet wiresheet.
1. Select the point of a Many to One NV you
want to hide and press Delete button on
your keyboard. The point is removed from
the wiresheet.
This point is however available in the NVs list in
the NV configuration View.
Remove points from NV Configuration View 1. Select the exposed fields from the Soft-
wiresheet ware Points available on wiresheet list
and click Remove Points from
wiresheet.
2. Click OK to confirm.

63 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

Edit NV Wiresheet You can only edit individual points of an NV at a

time.
1. Right click the individual point of an NV
and select Configure Properties.
2. Edit the available fields and click OK to
save the changes.
Edit NV NV Configuration View You can edit multiple points of an NV at a time.
1. Select the NV from the NVs list on the
right side of your screen on top.
2. Click Edit NV and edit one or multiple
points of the NV at once.
3. Click OK to save the changes made.
Delete NV Wiresheet You cannot delete points of a Many to One NV
from the wiresheet.
Delete NV NV Configuration View You can delete an NV with multiple points at a
time. To delete an NV with multiple points:
1. Select the NV from the NVs list on the
right side of your screen on top.
2. Click Delete NV.
3. Click OK to save the changes made.

You can also delete individual points in an NV

1. Select the NV from the NVs list on the
right side of your screen on top.
2. Click Delete NV.
3. Click OK to save the changes made.

NOTE: 3. Select the Custom NV you want to delete.

4. Click the Delete NV button. A Delete Confirmation dia-
— For special NVs used in function blocks, you can log box appears.
only change the Internal Data Type and the Value. 5. Select:
All other fields are unusable. Also, you cannot use Retain Points to delete the NV and make its exposed
the name nciSetPoints to name any other item as points (if any) as invalid points.
it is a reserved name. Delete Points to delete the NV and its exposed points
— If you edit software point details of an NVO, (if any).
whose points are grouped (shared), all newly cre- Cancel Delete to cancel the deletion
ated/shared NVOs in which the point is grouped
(shared) are modified. You can only edit field NOTE: While deleting an NV, if you select the Retain Points
names of the points selected to be grouped as option, points of the NV are converted to invalid
NVO. This is true even if the points are added to points. The option to retain exposed points of deleted
an existing NVO. However, no information of the NVs is available only from the NV Configuration
existing NVO fields is editable. Only the field View. The invalid points are displayed in the lower
names of the newly selected points are editable. pane of the NV Configuration View.
— When an NVO is edited such that the details of
the field whose exposed point is grouped across Deleting Software Points From Wiresheet
multiple NVs are modified, the association of the
point with the NV is lost. The point is no longer If you delete a software point on the wiresheet, the NV to
shared with this NVO. The lower pane in the NV which the point belonged to is modified such that the
Configuration View does not list this NVO in the corresponding field is deleted. The NV itself is deleted if the
list of NVOs to which that point belongs. The mod- field happens to be the last field.
ified field becomes local to the NVO and you r
must explicitly expose it on the wiresheet to use it NOTE: In the following cases, deleting a point from the
in the logic wiresheet puts the point back in the NV.

— If the point is attached to Many to One NVI or Fixed

Deleting NVs NV
To delete an NV: — if the point is configured as Bit Field
1. Browse to Station > Config > Drivers > LonNetwork > — if the point is attached to nciTempSetpoints
LonLYNX.
2. Select ControlProgram > Views > NV Configuration
View. The summary page appears with a list of pre-pro-
grammed Mandatory, Fixed, and Custom NVs and Soft-
ware points.

EN2Z-0960GE51 R0710 64
 CENTRALINE LYNX TOOL - USER GUIDE

Invalid Points field (to which the exposed point belonged) is removed from
the NV. However, an additional field is added to the NV to
You can delete an NV without deleting its exposed points. make the NV valid.
Points of such NVs are converted as invalid points. This
option is available only from the NV Configuration view. NOTE:
You can copy and paste NVs from a source controller to a
target controller. When an application folder containing points, — The tool shall allow grouping of invalid software
but the NV to which it belongs is present in the parent folder of output points to NVOs.
the folder in which the points are present, is copied/cut and — When the invalid points shall be grouped to form
pasted to the target controller, the points become invalid. NVs, the invalid points shall be converted to valid
When an application folder containing NVs whose points are software points.
exposed in its parent folder, is cut/copied and pasted to a — When an invalid Network Input/Setpoint/Output
target controller, the corresponding field (to which the exposed point is copied and pasted, the resulting point is
point belonged) is removed from the NV. The NV is deleted if an invalid point.
the point happens to be the last field in the controller. — When a folder containing some software points
(NVI/NCI points) whose NVs are present in other
When an application folder containing NVs (containing bit field
folders (other than its child folders) is deleted, the
configuration) whose points are exposed in its parent folder, is
NV itself is deleted if the point happens to be the
cut/copied and pasted to a target controller, the corresponding
last field of the NV

65 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

BACNET OBJECTS
An Object is a data item such as a temperature, a switch value The following is a list of mandatory objects supported by
or actuator state. Objects can be thought of as point LYNX.
parameters.
Object
There are three categories of Objects that the Bacnet LYNX Object Name Object Type Instance
supports. They are:
HardwareID Analog-value 0
• Mandatory: Mandatory Objects are the default Objects
present compulsorily in a Bacnet LYNX device. BrandModel Analog-value 1
• Fixed: Fixed Dropable Objects can be used while creating VersionReflash Analog-value 2
an application logic and edit only its Internal Data Type can
be edited. Fixed Dropable Objects can also be displayed VersionMajor Analog-value 3
on the wiresheet. VersionMinor Analog-value 4
• Custom: Custom Objects are the objects that are created InUse Analog-value 5
while creating an application logic. They can be created,
edited, and deleted based on your requirements. Error0 Analog-value 6
Error1 Analog-value 7
The following is a list of fixed objects supported by LYNX. Error2 Analog-value 8
Object Name Object Type Error3 Analog-value 9
DebugIndex0 Analog-value Error4 Analog-value 10
DebugIndex1 Analog-value Error5 Analog-value 11
DebugIndex2 Analog-value Error6 Analog-value 12
DebugIndex3 Analog-value Error7 Analog-value 13
DebugIndex4 Analog-value Error8 Analog-value 14
DebugIndex5 Analog-value Error9 Analog-value 15
DebugIndex6 Analog-value Error10 Analog-value 16
DebugIndex6 Analog-value Error11 Analog-value 17
DebugIndex7 Analog-value Error12 Analog-value 18
DebugIndex8 Analog-value Error13 Analog-value 19
DebugIndex9 Analog-value Error14 Analog-value 20
DebugIndex10 Analog-value Error15 Analog-value 21
DebugIndex11 Analog-value AlrmStatus Analog-value 22
DebugIndex12 Analog-value AlarmH Analog-value 23
DebugIndex13 Analog-value ConfigErrorID Analog-value 24
Debug0 Analog-value ConfigErrorNature Analog-value 25
Debug1 Analog-value ConfigErrorRecord Analog-value 26
Debug2 Analog-value WMCommErrorDeviceAddr Analog-value 27
Debug3 Analog-value WMCommErrorFileID Analog-value 28
Debug4 Analog-value UniqueID0 Analog-value 29
Debug5 Analog-value UniqueID1 Analog-value 30
Debug6 Analog-value UniqueID2 Analog-value 31
Debug7 Analog-value UniqueID3 Analog-value 32
Debug8 Analog-value UniqueID4 Analog-value 33
Debug9 Analog-value UniqueID5 Analog-value 34
Debug10 Analog-value
Debug11 Analog-value
Debug12 Analog-value
Debug13 Analog-value

EN2Z-0960GE51 R0710 66
 CENTRALINE LYNX TOOL - USER GUIDE

NOTE: The Bacnet LYNX supports the following object — Fixed Objects marked as Fixed_Dropable can be
types. exposed on the wiresheet. Other fixed objects
cannot be exposed as points.
— AVI - Analog Value Input — When a user changes the device model, if the
— AVO - Analog Value Output name of a custom object clashes with a fixed
— AV Setpoint - Analog Value Setpoint object name in the target model, CentraLine
— BVI - Binary Value Input LYNX generates a new unique name for the cus-
— BVO - Binary Value Output tom object and creates the new fixed object.
— BV Setpoint - BinaryValue Setpoint
— MVI - Multi-state Value Input
— MVO - Multi-state Value Output Object Input
— MV Setpoint - Multi-state Value Setpoint The Object Inputs (Analog Value Input, Binary Value Input,
The configured objects are mapped to the Function Block Multi-state Value Input) convert a raw object input into a
memory space to be used by any Function Block. Each Object value(s) that can be used by other function blocks.
is configured with a name. When an Object Input is added to the wiresheet, the object
appears in the Object Configuration View.
Viewing the List of Bacnet Objects
1. Browse to Station > Config > Drivers > BacnetNet- Adding an Object Input
work > BacnetLYNX. You can add an Object Input from:
2. Select ControlProgram> Views > Object Configura- 1. Object Configuration View
tion View. The summary page appears with a list of pre- 2. CentraLineLYNX Palette
programmed Mandatory, Fixed, and Custom Objects
in a tabular format. The table has the following columns:
— Name: The name of the Object. Adding an Object Input from the Object
— Type: Indicates if the object is of type AVI, AVO, AV Configuration View
Setpoint, BVI, BVO, BV Setpoint, MVI, MVO, or MV To add a new Object Input:
Setpoint.
1. Browse to Station > Config > Drivers > BacnetNet-
— Category: Indicates if the Object is Mandatory, Fixed,
work > BacnetLYNX.
or Custom.
2. Select ControlProgram > Views > Object Configura-
— Object Container: Indicates where the Object is used.
tion View. The summary page appears with a list of pre-
— Object Instance: A unique number that is automati-
programmed Mandatory, Fixed, and Custom Objects.
cally assigned to the object.
— Update Rate: The polling rate to update object value
NOTE: If adding an Object Input to an application,
of Object components.
browse through to the appropriate application
— Send Heartbeat: The rate at which a Network object
on the Nav palette.
value is sent to the network regardless of whether its
value is changed or not. The timeout value is equal to
3. Click Add Object. The New Object dialog box appears.
the value entered in this field multiplied by 5. This
Select an Object Type (Analog Value, Binary Value,
value should be configured as multiples of 5 only, else
Multi-state Value).
tool rounds it off to the nearest multiple of 5 during
download.
NOTE: The Input option is selected by default under
3. The bottom half of the Object Configuration view dis-
Select Point Type.
plays the physical and software points available on the
wiresheet in a tabular format. The table has the follow-
4. Click OK. The Advanced (Network Input) dialog box
ing columns:
appears.
— Point Name: The name of the physical /software point
5. Fill the necessary information in the fields and click OK
as it appears on the wiresheet.
to complete adding an Object Input. The Object Input is
— Field Names: Indicates the Object type.
displayed in the Objects table.
— Point Container: Indicates where the physical /soft-
ware point is used. All physical /software points that
NOTE: You cannot add an Object Input to a macro.
are used in a Program within an application are also
You can only add a Software point with Point
listed.
Type as Constant to a macro. You cannot add
a Network Output to a macro.
NOTE:

— Mandatory Objects cannot be used in the applica- Exposing an Object Input from the Object
tion logic. Configuration View
— Mandatory Objects cannot be edited or deleted.
To expose the Object Inputs you have added:
— In a Fixed Dropable Object, only Internal Data
Type can be modified. 1. Select the object you want to display on the wiresheet
— Custom Object is the user defined Object. A Cus- from the objects table and click the Show on wiresheet
tom Object can be edited or deleted. as Points button.
or
Drag the object you want to display on the wiresheet on

67 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

to the Software Points available on wiresheet list at 1. On the LYNX Palette, expand the SoftwarePoints
the bottom of the Object Configuration View. The Add folder. If the LYNX Palette is not visible on the left side
Points dialog box appears. of your screen, on the Menu bar, click Windows >
2. Click OK. The object you have selected appears on the Sidebars > Palette to display the Palette.
Software Points available on wiresheet list at the bot- 2. Drag a Network Input to the wiresheet of an Control-
tom of the view. The field name displays the Object Program/Application. The Name dialog box appears.
Name. Field Name information. If you do not select 3. Type a name for the point and click OK.
point to be displayed on the wiresheet, the Object is 4. Right-click the Network Input point you have just added
added but is not visible on the wiresheet. and select Configure Properties. The Configure
3. Click Cancel if you do not wish to continue adding an Properties dialog box appears.
Object Input. 5. Select Network Input, Modulating Input, or Binary
Input from the Point Type field.
Name Definition 6. Type or select the following:
Object Name The name of the Object Input. This — Point Name: Type a name for the point.
field is editable. — Point Category: Select a category.
Object Type Indicates if the object input is of type — Unit: Select the unit for the Point Category chosen.
AV, BV or MSV. This field is non- — Sub-Category: Select the enumeration type.
editable. — Value: This is disabled.
7. Click the Advanced button. The Advanced(Network
Object Instance A unique number that is Input) dialog box appears.
automatically assigned to the object. 8. Fill the necessary information in the fields and click OK
This field is editable. If you try to return to the configure properties dialog box.
replacing the instance value with a 9. Click OK to complete adding an Object Input.
value of your choice, the
replacement is successful only if the
value of your choice is not in use by Connecting Object Inputs
any other object. Once you have created an Object Input, you can connect an
Object Input to an Object Output/Function Block or Physical
Update Interval The rate at which the input object is point by left-clicking on the output of an Object Input and
updated. dragging your mouse to the input of an Object Output/
Object Category Displays the unit of measurement for Function Block or Physical point.
the object input.
Unit Displays the engineering unit based
on the object category.
Object Setpoint
The Object Setpoints are Analog Value Setpoint, Binary Value
Sub-Category Displays the enumeration type for Setpoint and Multi-State Value Setpoint.
the object inputs. The field Unit is
renamed as Sub-Category if the
object category selection is unitless. Adding an Object Setpoint
You can add an NCI from:
Fail Detect Enabled Set the Fail Detect Enabled of each
object input to either True or False. 1. Object Configuration View
• True means if the Object Input is 2. CentraLineLYNX Palette
bound and it has not received an
update from the Bacnet network Adding an Object Setpoint from the Object
source in the fail detect time then
an alarm is generated and the
Configuration View
Object Input is set to Invalid. To add a new Object Setpoint:
• False means the Object Input 1. Browse to Station > Config > Drivers > BacnetNet-
retains what was written to it until work > BacnetLYNX.
a Bacnet network source changes 2. Select ControlProgram > Views > Object Configura-
it or the CentraLine LYNX has a tion View. The summary page appears with a list of pre-
power outage or resets. programmed Mandatory, Fixed, and Custom Objects.
Update Rate The polling rate to update Object
values of Object components. NOTE: If adding an Object Setpoint to an Application,
browse through to the appropriate Application
on the Nav palette.
Adding an Object Input From LYNX Palette
While in the midst of creating an ControlProgram/Application, 3. Click Add Object. The New Object dialog box appears.
if you need to quickly add an Object Input, use the Network Select an Object Type (Analog Value, Binary Value,
Input item on the LYNX Palette. Multi-state Value).
4. Select the Select Point Type as Setpoint.
NOTE: You cannot add an Object Input to a macro. You can 5. Click OK. The Advanced(Network Input) dialog box
only add a Software point with Point Type as Con- appears.
stant to a macro. 6. Fill the necessary information in the fields and click OK
to complete adding an Object Setpoint. The Object Set-
To add an Object Input to an ControlProgram/Application: point is displayed in the Objects table.

EN2Z-0960GE51 R0710 68
 CENTRALINE LYNX TOOL - USER GUIDE

NOTE: You cannot add an Object Setpoint to a macro. You Name Definition
can only add a Object Input with Point Type as Con-
stant to a macro. Update Interval The rate at which the setpoint object
is updated.
Exposing an Object Setpoint from the Object Object Category Displays the unit of measurement for
the object setpoint.
Configuration View
Unit Displays the engineering unit based
To expose the Object Setpoints you have added:
on the object category.
1. Select the object you want to display on the wiresheet
from the objects table and click the Show on wiresheet Sub-Category Displays the enumeration type for the
as Points button. object inputs. The field Unit is
or renamed as Sub-Category if the
Drag the object you want to display on the wiresheet on object category selection is unitless.
to the Software Points available on wiresheet list at
the bottom of the Object Configuration View. The Add Adding an Object Setpoint from the LYNX Palette
Points dialog box appears. While in the midst of creating an ControlProgram/Application,
2. Click OK. The object you have selected appears on the if you need to quickly add an Object Setpoint, use the Network
Software Points available on wiresheet list at the bot- Setpoint item on the LYNX Palette.
tom of the view. The field name displays the Object
Name. Field Name information. If you do not select NOTE: You cannot add an Object Setpoint to a macro. You
point to be displayed on the wiresheet, the Object is can only add a Software point with Point Type as
added but is not visible on the wiresheet. Constant to a macro. You cannot add a Object Out-
3. Click Cancel if you do not wish to continue adding an put to a macro.
Object Setpoint.
To add an Object Input to an ControlProgram/Application:
Name Definition 1. On the LYNX Palette, expand the SoftwarePoints
Object Name The name of the Object Setpoint. folder.
This field is editable.
NOTE: If the LYNX Palette is not visible on the left side
Object Type Indicates if the object input is of type of your screen, on the Menu bar, click Win-
AV, BV or MSV. This field is non- dows > Sidebars > Palette to display the LYNX
editable. Palette.
Object Instance A unique number that is automatically
assigned to the object. This field is 2. Drag a Network Setpoint to the wiresheet of an Con-
editable. If you try replacing the trolProgram/Application. The Name dialog box appears.
instance value with a value of your 3. Type a name for the point and click OK.
choice, the replacement is successful 4. Right-click the Network Setpoint point you have just
only if the value of your choice is not added and select Configure Properties. The Config-
in use by any other object. ure Properties dialog box appears.
5. By default Network Setpoint is the Point Type. If it is
not, select Network Point from the Point Type field.
6. Type or select the following:
— Point Name: Type a name for the point.
— Point Category: Select a category.
— Unit: Select the unit for the Point Category chosen.
— Sub-Category: Select the enumeration type.
— Value: Enter a value based on the Point Category

69 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

Object Output Name Definition

The Object Outputs (AVO, BVO, MVO) convert input value(s) Unit Displays the engineering unit based
(Public Variable(s)) into a raw network variable output that is on the object category.
published onto the Bacnet network.
Sub-Category Displays the enumeration type for the
object inputs. The field Unit is
Adding an Object Output renamed as Sub-Category if the
You can add an Object Output from: object category selection is unitless.
1. Object Configuration View GPU Set the GPU of each object output to
2. CentraLineLYNX Palette either True or False.
• True means if the Object Output is
Adding an Object Output from the Object bound and it has not sent an
update to the Bacnet network
Configuration View target in the GPU specified time
To add a new Object Output: then an alarm is generated and
1. Browse to Station > Config > Drivers > BacnetNet- the Object Output is set to Invalid.
work > BacnetLYNX. • False means the Object Output
2. Select ControlProgram > Views > Object Configura- retains what was written to it until
tion View. The summary page appears with a list of pre- a Bacnet network source changes
programmed Mandatory, Fixed, and Custom Objects. it or the CentraLine LYNX has a
power outage or resets.
NOTE: If adding an Object Output to an Application, browse Send Heart Beat The rate at which output objects send
through to the appropriate Application on the Nav data to the network.
palette.

3. Click Add Object. The New Object dialog box appears. Exposing an Object Output from the Object
4. Select an Object Type (Analog Value, Binary Value, Configuration View
Multi-state Value). To expose the Object Output you have added:
5. Select the Select Point Type as Setpoint.
1. Select the object you want to display on the wiresheet
6. Click OK. The Advanced (Network Output) dialog box
from the objects table and click the Show on wiresheet
appears.
as Points button.
7. Fill the necessary information in the fields and click OK
or
to complete adding an Object Output. The Object Out-
Drag the object you want to display on the wiresheet on
put is displayed in the Objects table.
to the Software Points available on wiresheet list at
the bottom of the Object Configuration View. The Add
NOTE: You cannot add an Object Output to a macro.
Points dialog box appears.
2. Click OK. The object you have selected appears on the
Name Definition Software Points available on wiresheet list at the bot-
Object Name The name of the Object Output. This tom of the view. The field name displays the Object
field is editable. Name. Field Name information. If you do not select
point to be displayed on the wiresheet, the Object is
Object type Indicates if the object input is of type
added but is not visible on the wiresheet.
AV, BV or MSV. This field is non-
3. Click Cancel if you do not wish to continue adding an
editable.
Object Output.
Object Instance A unique number that is
automatically assigned to the object.
This field is editable. If you try
Adding an Object Output from the LYNX Palette
replacing the instance value with a While in the midst of creating an ControlProgram/Application,
value of your choice, the replacement if you need to quickly add an Object Output, use the Network
is successful only if the value of your Outputs item on the LYNX Palette.
choice is not in use by any other
object. NOTE: You cannot add an Object Output to a macro.
Update Interval The rate at which the output object is To add an Object Output to an ControlProgram/Application:
updated.
1. On the LYNX Palette, expand the SoftwarePoints
Sen Delta The Significant Event Notification folder. If the LYNX Palette is not visible on the left side
is also known as SEN Delta. The of your screen, on the Menu bar, click Windows >
object is sent on the Bacnet Network Sidebars > Palette to display the Palette.
whenever any field exceeds the SEN 2. Drag a Network Output to the wiresheet of an Control-
Delta. SEN Delta of zero (0) disables Program/Application. The Name dialog box appears.
the feature. 3. Type a name for the point and click OK.
Object Category Displays the unit of measurement for 4. Right-click the Network Output point you have just
the object output. added and select Configure Properties. The Config-
ure Properties dialog box appears.
5. Select Network Output, Modulating Output, or
Binary Output from the Point Type field.

EN2Z-0960GE51 R0710 70
 CENTRALINE LYNX TOOL - USER GUIDE

6. Type or select the following:

— Point Name: Type a name for the point.
Edit Objects
— Point Category: Select a category. You can partially modify Fixed Dropable Objects and totally
— Unit: Select the unit for the Point Category chosen. modify Custom Objects. However, you cannot modify
— Sub-Category: Select the enumeration type. Mandatory and Fixed Objects.
7. Click OK to complete adding an Object Output.
NOTE: If you delete a point of an Object and if this point is
the only point in that Object, the Object itself is
Connecting Object Outputs deleted.
Once you have created an Object Output, you can connect an
Object Output to an Object Input/Function Block or Physical The following table summarizes what you can or cannot do
point by left-clicking on the output of an Object Input/Function with Objects in the Wiresheet and the Object Configuration
Block/Physical point and dragging your mouse to the input of View.
an Object Output.
Show Object
Type on wiresheet Create Edit Delete
Wiresheet Object Config Wiresheet Object Wiresheet Object Wiresheet Object
View Config View Config View Config
View
Object Input Yes. Yes. Yes. Yes. Yes. Yes. Yes. Yes.
Object Any Object You need to You can add You can add You can edit You can edit You can You can
Setpoint added directly add an an object with an object an Object an Object delete an delete an
Object to the Object and a single point. with single with a single with single Object with Object with
Output wiresheet is select the point. point at a point at a a single single point
automatically points you time. time. point at a at a time.
displayed on want to be time.
the wiresheet displayed on Objects of
the wiresheet Fixed
by clicking Dropable
the Display type and
on Wiresheet Objects
button. with Bit
Configurati
on are not
deleted but
only hidden
from the
wiresheet.
They are
still
available in
the Objects
list.
4. The Edit Object Name dialog box appears. If the
To edit an Object: selected Bacnet object is a Fixed Dropable Object type,
you can only change the Internal Data Type and click
1. Browse to Station > Config > Drivers > BacnetNet- OK to save the changes.
work > BacnetLYNX. 5. If the object is Custom type, by default, the settings are
2. Select ControlProgram > Views > Object Configura- such that you can change:
tion View. The summary page appears with a list of pre- — Object Name
programmed Mandatory, Fixed, and Custom Objects — Object Type
and Software points. — Object Instance
3. Select the Fixed or Custom Object you want to edit and — Update Interval
click the Edit Object button. 6. Click OK to save the changes.

71 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

The following table summarizes editing bacnet objects from

the Wiresheet and NV Configuration View..
Object Type Action From Procedure
Object Input/ Remove points from wiresheet Wiresheet You cannot remove (hide) a
ObjectSetpoint./ point from the wiresheet.
ObjectOutput
Remove points from wiresheet Object Configuration View 1. Select the exposed fields
from the Points available
on wiresheet list.
2. Click Remove Points
from wiresheet.
3. Click OK to confirm.
Edit Object Wiresheet 1. You can edit individual
points of an object at a
time.
2. Right-click the individual
point of an object and
select Configure Prop-
erties.
3. Edit the available fields
and click OK to save the
changes.
Edit Object Object Configuration View 1. You can edit individual
points of an object at a
time.
2. Select the object from the
Objects list on the right
side of your screen on
top.
3. Click Edit Object and
edit the point of the
object.
4. Click OK to save the
changes made.
Delete Object Wiresheet 1. You can delete individual
points of an objects at a
time.
Delete Object Object Configuration View 1. You can delete an object
with individual points at a
time. To delete an object
with individual points:
2. Select the object from the
Objects list on the right
side of your screen on
top.
3. Click Delete Object.
4. Click OK to save the
changes made.

Deleting Objects 5. Select:

To delete an Object: — Retain Point(s) to delete the object and make its
exposed points (if any) as invalid points.
1. Browse to Station > Config > Drivers > BacnetNet- — Delete Point(s) to delete the object and its exposed
work > BacnetLYNX. points (if any).
2. Select ControlProgram > Views > Object Configura- — Cancel to cancel the deletion.
tion View. The summary page appears with a list of pre-
programmed Mandatory, Fixed, and Custom objects NOTE: While deleting an object, if you select the Retain
and Software points. Point(s) option, point of the object is converted to
3. Select the Custom object you want to delete. invalid point. The option to retain exposed points of
4. Click the Delete Object button. A Delete Confirmation deleted objects is available only from the Object
dialog box appears. Configuration View. The invalid points are dis-
played in the lower pane of the Object Configura-
tion View.

EN2Z-0960GE51 R0710 72
 CENTRALINE LYNX TOOL - USER GUIDE

Deleting Points From Wiresheet When an application folder containing objects whose points
If you delete a software point on the wiresheet, the object to are exposed in its parent folder, is cut or copied and pasted to
which the point belonged to is modified such that the a target controller, the corresponding field (to which the
corresponding field is deleted. The object along with it's point exposed point belonged) is removed from the object. The
is deleted. object is deleted if the point happens to be the last field in the
controller.
When an application folder containing objects (containing bit
Invalid Points field configuration) whose points are exposed in its parent
You can delete an Object without deleting its exposed points. folder, is cut or copied and pasted to a target controller, the
Points of such Objects are converted to invalid points. This corresponding field (to which the exposed point belonged) is
option is available only from the Object Configuration View. removed from the object. However, an additional field is
You can copy and paste objects from a source controller to a added to the object to make the object valid.
target controller. When an application folder containing points,
but the object to which it belongs is present in the parent NOTE: When an invalid object input, setpoint, or an output
folder of the folder in which the points are present, is copied or point is copied and pasted, the resulting point are
cut and pasted to the target controller, the points become also invalid.
invalid.

73 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

BINDINGS OR DATA SHARING

A binding refers to a configured association between 5. Select the Object from the destination device pane to
LonWorks network variables (NVs) either within a device, or which you want to link the source object.
between separate devices on a Lon network.
Data Sharing is the terminology that is used for Bindings in NOTE: The Object Properties of the source device
case of Bacnet devices. shows Present Value. This implies that the
present value of the object input or object out-
NOTE: The terms network object and BACnet object are put is taken as input to the control logic.
used interchangeably. The Object Properties of the destination device
shows Present Value for all objects except AO
and BO. When an AO or BO object is selected
Binding Lon Devices as a destination object, Object Properties dis-
To bind two Lon Devices in CentraLine LYNX Tool: plays the priority array index from 1 to 16. You
can set the priority value for the destination
1. Right-click Lon Network in the Nav palette and select object. 
Views > Wire sheet. All devices on the Lon Network If an AO and BO object is set as the source
are displayed as containers on the wire sheet. objects, then their present value is taken as
2. Right-click the source device container and select Link input to drive the logic. 
Mark. AO and BO object types can act as both
3. Right-click the target device container and select Link source and target.
from Source Device Name. The Add Binding dialog
box appears. 6. Click OK. A link appears on the wiresheet between the
4. Click the NV of the source controller you want to link. source and destination controllers.
The pane showing the target NVs highlights NVs with 7. Right-click Bacnet Network in the Nav palette and
which you can bind the source NV. select Views > Bacnet Link Manager. A row providing
5. Select the NV from the target device pane to which you the link details appears.
want to link the source NV. 8. Select the row and click Bind to complete binding
6. Click OK. A link appears on the wire sheet between the Objects between a source and destination controller.
source and target controllers.
7. Right click Lon Network in the Nav palette and select NOTE: Binding cannot be done if both source and destina-
Views > Link Manager. A row providing the link details tion devices are third party Bacnet devices. At least
appears. one of them must be a LYNX device.
8. Select the row and click Bind to complete binding NVs
between a source and target controller. — AI, BI, AV/BV/MSV (setup as NetworkOutput) can
act as source objects to the device.
When you perform the operations such as, add/delete/modify — AV/BV/MSV (setup as NetworkInput) can act as
NVs in Control Program, the changes are not reflected to NVs destination objects to the device.
under LonLYNX device until you perform a download — Only the custom Bacnet objects are displayed in
operation or click Generate NVs. the Add Binding dialog box for binding devices.
Generate NVs option recreates the NVs under the device as The mandatory and fixed objects are not available
per the NVs in the Control Program of that device. You do not for binding.
have to be online for the LYNX device to use this option. You Unlike LON, the objects will not be present under the device
can set up offline Lon bindings involving LYNX devices and level until you click Generate Network Objects on the
bind the devices when the LYNX devices are online. This BacnetLYNX device.This option creates a
feature is useful for offline engineering. BacnetObjectReferences for network objects in the Control
Program.

Binding Bacnet Devices When a new network object is added, perform Generate
Network Objects so that the corresponding
To bind two Bacnet devices in CentraLine LYNXTool: BacnetObjectReference is added at the BacnetLYNX device
1. Right-click Bacnet Network in the Nav palette and level.
select Views > Wiresheet. All devices on the Bacnet When you perform operations such as delete/modify Network
Network are displayed as containers on the wiresheet. Objects in the Control Program, BacnetObjectReferences are
2. Right-click the source device container and select Link automatically updated.
Mark. Generate Network Objects option recreates the
3. Right-click the destination device container and select BacnetObjectReferences under the device as per the Bacnet
Link To. The Add Binding dialog box appears. Objects under Control Program of that device. You do not
4. Click the Object of the source controller you want to link. have to be online for the LYNX device to use this option. You
The pane showing the destination objects highlights the can set up offline Bacnet data sharing links involving LYNX
objects with which you can bind the source object. devices and bind the devices when the LYNX devices are
online. This feature is of useful for offline engineering.

EN2Z-0960GE51 R0710 74
 CENTRALINE LYNX TOOL - USER GUIDE

About Bacnet Link Manager • Click Delete, to delete the links from the database. The link
status changes to Obsolete after the deletion, to indicate
Using Bacnet Link Manager view, you can manage the that the link is deleted only in the database. Click Bind, to
binding of LYNX devices. The view also provides the link remove the binding information from the controller.
details of the Bacnet devices. Refresh
The following link details are displayed in the Bacnet Link • Click Refresh, to refresh the status of the bindings
Manager view. between the devices. The link status is displayed as
• Link Status: Displays the current status of each link as NewLink, Bound, or Obsolete, depending on whether the
NewLink, Bound, or Obsolete. For more details, see link is downloaded to the device or is yet to be
“Types of Link Status”. downloaded.
• Device Status: Displays the status of the device as Bind
Downloaded, To be downloaded, or Offline. If the device • Click Bind, to download the binding information to the
status is Downloaded, it indicates that the bindings are devices. The link status is updated, after the Bind option is
downloaded to the controller. To be downloaded indicates invoked.
that the download is pending. If the device status is offline, Selective Bind
it indicates that the device is not downloaded to the
controller. • Click Selective Bind, to download the binding information
• Source Device: Displays the name of the source Bacnet selectively to one or more devices.
device whose output is linked or bound to the target Bacnet Learn Link(s)
device. • Click Learn Link(s), to learn the binding information from
• Source Object: Displays the name of the Bacnet object in the devices. The link status is updated, after the binding
the source device. information is retrieved from the device. On clicking Learn
• Source Property: Displays the object property of the Link(s), all obsolete links are marked as Bound. The
source object. NewLinks that are not yet downloaded to the controller are
• Target Device: Displays the name of the target Bacnet retained.
device.
• Target Object: Displays the name of the Bacnet object in NOTE:
the target device.
• Target Property: Displays the object property of the target — At any point, for Learn Link(s) to restore the link
object. The object property of the target device shows status from a LYNX Bacnet device, the device has
PresentValue for all objects, except AO and BO. When an to be in downloaded state, that is, the application
AO or BO object is selected as a target object, target in Control Program of the source device in Nia-
property displays the priority selected. gara should match that in the online device. Oth-
• Poll or Push: LYNX Bacnet devices use a poll/push erwise Learn Links(s) does not learn links from
mechanism to share data on the network. Every LYNX that device.
Bacnet device has 1 poll table and 1 push table, the size of — The application in the target device involved in
each being 256. The tool automatically decides the poll/ data sharing in Niagara does not have to match
push mechanism when you add a link. The push table on that in the online device.
the source LYNX is filled first and when there are no spare Clear Bindings
entries in the push table, the poll table on the destination • Click Clear Bindings, to clear all the links from the device.
device is used. When there is binding between a LYNX and The links that are in Bound and Obsolete states are
a third party device, the push/poll table on the LYNX device marked as NewLink.
is used depending on whether it is a source or a target
device. The status Poll implies that the target device would
poll the value periodically from the source device used in Types of Link Status
binding. The interval for polling is the Update Rate Each link or binding in the Bacnet Link Manager view
configured on the destination object. The status Push appears with a status in the LinkStatus column. The links
implies that the source device would push the value show one of the following status, assuming there is no error.
periodically to the target device. The interval for pushing — NewLink: If links are created between two or more
the data is the GPU interval configured on the source devices and are not downloaded to the device.
object. You cannot select the mechanism to be used for — Bound: If links are created between two or more
binding. devices and are downloaded to the device. On clicking
the Bind button on the Bacnet Link Manager view, all
Opening Bacnet Link Manager View the links with a status as NewLink are converted to
To access the Bacnet Link Manager view: Bound.
— Obsolete: If links that are downloaded to the device
• Right-click Bacnet Network in the Nav tree and select are deleted. All links with a status as Bound are
View > Bacnet Link Manager. changed to Obsolete when you click the Delete but-
ton on the Bacnet Link Manager view. On clicking the
Bacnet Link Manager Commands Bind button on the Bacnet Link Manager view, all
The following commands are available in the Bacnet Link links with a status as Obsolete are deleted.
Manager view-
Add Error Conditions
• Click Add,to bind two LYNX Bacnet devices, or bind a Errors and warnings may occur while attempting to change or
LYNX Bacnet device and a third party Bacnet device. modify data when the devices are bound. The following are
Delete some of the error conditions.

75 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

— After the devices are bound, a break in communication 5. Select the destination Object Type from the list.
between the devices causes a Network Communica- 6. Type the object instance number in the Object ID text
tion alarm, which is displayed in the Error View. box. A default Object Name is provided for the destina-
— If the GPU rate of the source or target device is tion object.
changed after the links are downloaded to the device,
then a warning message appears suggesting you to NOTE: The Object Name can be edited.
download the links once again to the device. In the
Bacnet Link Manager view, the links with the status 7. Select presentValue from the Property list when the
as Bound are changed to NewLink. destination object type is AV, BV, and MSV.
— If the GPU rate on the source is greater than the or
update rate on the target, a warning message Select the priority value from the Property list when the
appears. destination object type is AO or BO. A priority value
— When changing a point type results in the change of from 1 to 16 can be set for the destination object.
the Bacnet object type, a warning message appears to 8. Click OK to bind the two devices.
delete the links. It may not be possible to bind the new
object type with the existing objects. Perform the following to bind a third party source device with a
— When editing Bacnet objects from the Object Config- LYNX destination device.
uration View, the links with status as Bound is
changed to NewLink. 1. Select a third party source device from the Device list.
— If the source and target devices are third party 2. Select an Object Type from the list.
devices, an error message appears. 3. Type the object instance number in the Object ID text
box. A default Object Name is provided for the destina-
tion object.
Add Bindings
Add Bindings allows you to bind two devices wherein at least NOTE: The Object Name can be edited.
one device is a LYNX device. You can bind two devices in any
one of the following ways. 4. Select presentValue from the Property list. The
present value of the source object is taken by default.
— A LYNX source device with a LYNX target device 5. Select a LYNX Bacnet destination device from the
— A LYNX source device with a third party target Device list.
— A third party source device with a LYNX target device 6. Select the destination object from the Object list.
7. Select presentValue from the Property list when the
The LYNX device can be selected under the Source Details destination object type is AV, BV, and MSV.
or the Target Details section. or
Perform the following to bind two LYNX devices. Select the priority value from the Property list when the
destination object type is AO or BO. A priority value
1. Select a LYNX Bacnet source device from the Device from 1 to 16 can be set for the destination object.
list.
2. Select the source object from the Object list. NOTE: The priority index selected for binding in case
3. Select presentValue from the Property list. of a destination device should be different from
4. Select a LYNX Bacnet destination device from the the priority index being driven by the control
Device list. program logic.
5. Select the destination object from the Object list.
6. Select presentValue from the Property list when the 8. Click OK to bind the two devices.
destination object type is AV, BV, and MSV.
or  NOTE: Binding cannot be done if both source and destina-
Select the priority value from the Property list when the tion devices are third party Bacnet devices. An error
destination object type is AO or BO. A priority value message, "Cannot create the link. Both are non-
from 1 to 16 can be set for the destination object. bindable devices." appears, if you try binding two
third party devices.
NOTE: The priority index selected for binding in case
of a destination device should be different from
the priority index being driven by the control Binding HAWK and LYNX
program logic. A HAWK can behave as a Bacnet device. Points from LYNX
and other third party devices can be exported to the HAWK to
7. Click OK to bind the two devices. be monitored. The points in the HAWK are monitored by
setting up a binding between the HAWK and LYNX. This
Perform the following to bind a LYNX source device with a reduces the number of polls needed to read or write values to
third party destination device. the point.
1. Select a LYNX source device from the Device list.
2. Select the source object from the Object list. Configuring Bacnet Device
3. Select presentValue from the Property list. The Local Device represents the Bacnet device being added
4. Select a third party destination device from the Device to the network.
list.

EN2Z-0960GE51 R0710 76
 CENTRALINE LYNX TOOL - USER GUIDE

1. Expand Config > BacnetNetwork > Bacnet Comm > 7. Type the MAC Address specified in the Mstp Address
Network in the Nav sidebar. text box of the Mstp Port.
2. Right-click MstpPort and choose Actions > Enable.  8. Set MAC Address Style as MSTP/Other.
The Property Sheet on the right pane displays the
details of the mstp port. The details include Network See the About BACnet server access section on the Niagara
Number and Mstp Address. Help set for more details on monitoring points by binding
3. Drag a Bacnet device from the Palette onto the Nav HAWK and LYNX controller.
sidebar. 
For more details, see "Adding a Controller" under "Get- By default, the Bacnet driver provides read access to all
ting Started". exposed objects from third party Bacnet devices.
4. Type a name for the device you are adding and click To enable write access to exposed objects from third party
OK. Bacnet devices, you must ensure that you have the necessary
5. Right-click the Bacnet device in the Nav sidebar and permissions to those objects. To allow write access, the Super
choose Views > Property Sheet. User option must be enabled in the Property Sheet of the user
6. Type the Network Number specified in the Network service.
Number text box of the Mstp Port. See "About BACnet server access" on the Niagara Help set
for more details on allowing write access from Bacnet.

77 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

FLOW CALIBRATION
The flow balancing view is used to balance a LYNX controller • The option to calibrate the reheat valve is available when
that is programmed with a standard VAV application. Based Reheat Valve Override Supported is selected.
on the version of the VAV application and its features, the • The option to calibrate the peripheral heat valve is
following operations can be performed on the view. available when Peripheral Heat Valve Override
• Flow pressure zero calibration Supported is selected.
• Two point calibration
• K factor calibration
• Heating coil water flow calibration
Procedure
1. On the Nav palette, browse to Station > Config > Driv-
ers> LonNetwork > LonLYNX.
Pre-requisites or 
• The LYNX controller must be online. Browse to Station > Config > Drivers> BacnetNet-
• The LYNX controller must be in a commissioned state. work > BacnetLYNX.
• VAV Zone Terminal Single Duct must be selected as the 2. Right-click ControlProgram and select Views > Flow
Application Type and Air Balance Supported must be Balancing View. The Flow Balancing View appears
selected. on the right pane.
You can type the values into the following field.
NOTE: The selections must be done before download-
ing the program to the LYNX controller.
Name Description
Actuator Travel Time The actuator travel time is the time required by the actuator to travel from 0% to 100% open or 100%
to 0% open. This time interval depends on the actuator type and can vary from 0 to 500 seconds.
K Factor The value of K factor varies the air velocity. This field allows you to manually change the K factor
value.
Inlet Area Displays the area of the duct. Either a standard diameter can be selected or a custom area can be
entered in this field.
Measured Flow Displays the actual air flow when measured by the balancer using an accurate device. This field is
editable.
Maximum Flow Setpoint This field allows you to set the flow setpoint for maximum flow calibration and k factor calibration.
The controller seeks stable flow and when it is reached, it allows you to set the calibration source
value.
Minimum Flow Setpoint This field allows you to set the flow setpoint value which must be less than the maximum value to
obtain minimum flow calibration. The controller seeks stable flow and when it is reached, it allows
you to set the calibration source value.
Re-heat Valve Override This allows you to override the value of the reheat valve in an application built for the reheat valve.
This field is visible when the Reheat Valve Override Supported feature is selected in the Details
View of the Control Program.
Peripheral Heat Valve This allows you to override the value of the peripheral heat valve in an application built for the
Override peripheral heat valve. This field is visible when the Peripheral Heat Valve Override Supported
feature is selected in the Details View of the Control Program.
Device Mode Displays the current device mode. This is a non-editable field.
Damper Position Displays the current damper position. This is a non-editable field.
Sensed Flow Displays the actual air flow that is measured by a pressure sensor. This field is non-editable.
Flow Pressure Displays the current flow pressure. This field is non-editable.

Flow pressure zero calibration Two point calibration

To start zero balancing calibration method: You can set the device to either maximum or minimum
• Click on Start Zero Balancing. balancing in any order. The tool does not enforce any rules on
the order of balancing.
The damper is completely closed. If any flow pressure is Maximum calibration
detected the value is considered to be a flow pressure offset. To start maximum calibration method:
After the completion of zero balancing the device mode is set • Click on Start Maximum Balancing.
to automatic operation.

EN2Z-0960GE51 R0710 78
 CENTRALINE LYNX TOOL - USER GUIDE

The device adjusts the damper to try and attain the maximum After the measured flow is entered, the K factor value is
flow setpoint. After the setpoint is attained, the Measured calculated by the tool and displayed. The tool prompts you to
Flow field is enabled and the actual measured flow value can write this value to the device. You can choose to calculate the
be entered. The device remains in manual mode (Open K factor without using the tool and set the calculated value in
Maximum) after maximum balancing is complete. the K factor field. The device remains in manual mode (Open
Minimum calibration Maximum) after K factor balancing has completed.
To start minimum calibration mode calibration method:
• Click on Start Minimum Balancing.
Heating coil water flow calibration
To override the reheat valve position:
The device adjusts the damper to try and attain the minimum • Type the reheat value in percentage and click the Override
flow setpoint. After the set point is attained, the Measured button next to Reheat Valve Override field.
Flow field is enabled and the actual measured flow value can
be entered. The device remains in manual mode (Open To override the peripheral heat valve position:
Minimum) after minimum balancing is complete. • Type the peripheral heat value in percentage and click the
Override button next to Peripheral Heat Valve Override
K Factor calibration field.
To start K factor calibration method:
NOTE: Click the Auto button to set the reheat and periph-
• Click on Start K Factor Balancing. eral heat valve into automatic operation.

After a warning message, the two point calibration data is

returned to factory defaults.
Setting the device mode to automatic operation
To set the device to automatic operation:
The device adjusts the damper to try and attain the maximum
flow setpoint. After the setpoint is attained the Measured Flow • Click on Set Mode to Auto when it is enabled.
field is enabled and the actual measured flow value can be
entered. While exiting the view if the device is in manual mode, then
the tool prompts you to change the mode to automatic
operation.

79 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

FUNCTION BLOCKS
Use Function Blocks to program the CentraLine LYNX — Program: This includes macros and logic that you can
controller to perform a wide variety of HVAC applications. define and use in applications.
Function Blocks are modules that perform a specific task by — StandardApplications: Standard applications
reading inputs, operating on them, and outputting a value(s). shipped by CentraLine which you can use to build
Use the Programming Tool to select the appropriate function application logic
blocks, configure them and connect them together to perform 2. Expand the LonLYNX or BacnetLYNX device in the
a specific HVAC application. Nav tree and select the ControlProgram folder.
Function Blocks are classified into six categories. They are: 3. Drag and drop the desired function block on to the
wiresheet.
• Analog Function Blocks 4. Enter the name of the function block and click OK. The
• Logic Function Blocks function block is added and appears on the wire sheet.
• Math Function Blocks
• Control Function Blocks NOTE: A total of 100 function blocks are supported in the
• Zone Control Function Blocks LonLYNX I, LYNX II, and Bacnet LYNX models.LYNX
• Data Function Blocks Micro models support 200 Function blocks.

Add Device — LonLYNX II models are: CLLYVL6436AS,

CLLYVL6438NS and CLLYUL6438S
To add a device: — LonLYNX Micro models are: CLLYVL4024NS,
1. Select CentraLineLYNX from the drop-down list in the CLLYVL4022AS, CLLYUL4024S, CLLYUL1012S, and
LYNX Palette. CLLYVL0000AS
2. Drag the LonLYNX folder on to LonNetwork in the Nav — BacnetLYNX models are: CLLYVB6436AS,
tree.  CLLYVB6438NS & CLLYUB6438S
or
Drag the BacnetLYNX folder on to BacnetNetwork in
the Nav tree Configure Function Block
3. Enter the desired name for the device and click OK. Complete the following procedure to configure a function
block:
Add Function Block 1. Add the desired function block to the wiresheet of an
Application Logic, Program or Macro. See Adding a
To add a function block: Device and Adding a Function Block for more details.
1. Display the LYNX palette (If you do not see the LYNX 2. Right-click the function block on the wiresheet and
palette on the left pane, on the Menu bar select Win- select Configure Properties. A dialog box with the con-
dow > Side Bars > Palette). The LYNX palette is dis- figuration details appears.
played with the following items: 3. Enter information in the available fields.
— Physical Points: Modulating and Binary Inputs/Out- 4. Click Apply to save the changes 
puts. or 
— SoftwarePoints: Constant/Network Input/Setpoint/ Click OK to save the changes and close the dialog box.
Output. Use this to create NVI, NCI, NVO, or con- 5. Click Cancel to revert to the last saved settings and
stants. close the dialog box.
— Analog: Analog function blocks
— Logic: Logic function blocks
— Math: Math function blocks Delete Function Block
— Control: Control function blocks To delete a function block:
— DataFunction: Data Function function blocks 1. On the wiresheet, select the function block you want to
— ZoneArbitration: Zone Arbitration function blocks delete.
— BuiltIn: BuiltIn function blocks 2. Click the Delete button on your keyboard or right-click
— Macro: A Macro is a group of functional blocks the function block and select Delete. The function block
grouped together that define a specific functionality. is deleted along with bindings to it, if any.
Commonly used program elements can be defined as
macros so that they could be reused across applica-
tions.

EN2Z-0960GE51 R0710 80
 CENTRALINE LYNX TOOL - USER GUIDE

ANALOG FUNCTION BLOCKS

The CentraLine LYNXTool provides the following Analog Analog Inputs
function blocks that you can configure and use to build your
application logic:
• Analog Latch Range
• Average Input Input
• Compare Name Low High Value Description
• Encode
x >=- <+infi unconnect x=invalid
• Hysteretic Relay
infinit nity ed
• Maximum
y
• Minimum
• Priority Select invalid x=invalid
• Select
• Switch
Output
Analog Latch Output
This function latches the Y output to the value on the X input Name Range Description
when the latch input transitions from FALSE to TRUE. The
output is held at this value until the next FALSE to TRUE Y Any floating Value from X when the latch
transition. At each FALSE to TRUE transition the Y output is point value input goes from FALSE to
latched to the current X input. TRUE

NOTE:
Logic Inputs
— If both the X and latch inputs are unconnected,
Input Input Logic the output will be zero.
Name Value Value Description — If the input is invalid, the output will transition to
invalid when the latch input goes from FALSE to
latch unconnect 0 Output remains at zero as there TRUE.
ed is nothing to cause a latch. — The latch input can be negated to cause a TRUE
VAL != 0.0 1 Latch the input X to the output to FALSE transition to latch X to Y.
on FALSE to TRUE transitions — From iteration to iteration of the Analog Latch
(no negation) keeps track of the last state of the latch input so
that it knows when a FALSE to TRUE transition
invalid 0 Output remains as it was.
occurs.
— On power up/reset the last latch value is set to
FALSE, regardless of the negation configuration.

81 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

Example:
An illustration to explain the behavior of the Analog Latch.

EN2Z-0960GE51 R0710 82
 CENTRALINE LYNX TOOL - USER GUIDE

Average Ignore invalid inputs: Select this option if you want the
function block to ignore any invalid inputs, if any, and consider
This function calculates the average of 8 inputs. You can have only the valid inputs to calculate the output. If this option is left
a combination of analog inputs from other function blocks and unselected, the invalid inputs will make the output also as
constant values as inputs to this function block. The output is invalid.
set to the average of the connected inputs.

NOTE: The Output returns an invalid value if no inputs are

connected or if all inputs are invalid.

Inputs

Range
Input Name Low High Input Value Description
in1-8 >=- infinity <+ infinity unconnected not used in calculation
if all inputs unconnected then output = invalid
in1-8 >=- infinity <+ infinity invalid If any input is invalid then output=invalid

Outputs

Output Name Range Description

OUTPUT Any floating point number Average of the inputs

83 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

Compare Setpoints
This function compares two inputs to each other.
Range
Name Value Description
Operation Equals • The output is set to true if (Input 2
– On Hyst) <= input 1 <= (Input 2
+ Off Hyst)
Less • The output is set to true if Input 1 <
Than (input 2 – on Hyst)
• The output does not change if
(Input 2 – on Hyst) <= input1 less
than (Input 2 +off Hyst)
• The output is set to false if Input1
>= (Input 2 + off Hyst)
Greater • The output is set to true if Input 1 >
NOTE: It is possible to create invalid numbers by combining Than (input 2 + on Hyst)
large values of input 2 and on and off hysteresis. The • The output does not change if
behavior is dependant on the operation selected, (Input 2 – off Hyst) < input1 <=
value of input 1, and the compiler. (That is, the simu- (Input 2 + on Hyst)
lator may have a behavior different from the product.) • The output is set to false if Input1
<= (Input 2 - off Hyst)
The following comparison calculations can be made using the
Compare function block:
— Input1 less than input2 Outputs
— Input1 greater than input2
— Input1 equal to input2
Output
Additionally, on and off hysteresis analog inputs are provided
Name Range Description
which you can use to make compare calculations.
OUTPUT False (0) • Comparison of inputs
NOTE: The Output returns a zero value if no inputs are con- or True
nected or if all inputs are invalid. (1)
• If Property Negate is selected, the
Inputs output is negated after performing
the logic. The sense of the
hysteresis settings does not
Range change.
Input Input • When negation is selected, the old
Name Low High Value Description output (from the previous cycle) is
determined by negating the current
input1-2 >=- <+ unconnect out = 0 value of the output.
infinity infinity ed
invalid out = 0
onHyst 0 unconnect val = 0
ed
invalid val = 0
offHyst 0 unconnect val = 0
ed
invalid val = 0

EN2Z-0960GE51 R0710 84
 CENTRALINE LYNX TOOL - USER GUIDE

Encode In 4,5,6 0 167772 0xDDEEFF See Note

This function translates enumerations of a digital value into 15.0
different enumeration numbers, allowing standard and custom Input 4 value 0xDD
enumerations to be combined and used together. If a match maps to output 4
between inEnum and one of the in values is found, then the values;
appropriate output value is put into out and the “fire” line is Input 5 value 0xEE
true. If there is no match, then the inEnum is put to the out and maps to output 5
fire is false. Disable disables all matching and allows the Input 6 value 0xFF
inEnum to be put to the out line. maps to output 6
In 7,8,9 0 167772 0xGGHHII See Note
15.0
Input 7 value 0xGG
maps to output 7
values;
Input 8 value 0xHH
maps to output 8
Input 9 value 0xII
maps to output 9
Out 1,2,3 0 167772 0xaabbcc See Note
15.0
Input 1 value 0xaa
maps to output 1
values;
Input 2 value 0xbb
maps to output 2
Input 3 value 0xcc
maps to output 3
Out 4,5,6 0 167772 0xddeeff See Note
15.0
Analog Inputs Input 4 value 0xdd
maps to output 4
values;
Range Input 5 value 0xee
Input maps to output 5
Name Low High Input Value Description Input 6 value 0xff
maps to output 6
inEnum 0 255 unconnecte Val = 0
d Out 7 0 255 0xgg Input 7 value 0xgg
maps to output 7
invalid Val = 0 values;
Val matches Output = matching Out 8 0 255 0xhh Input 8 value 0xhh
an input input’s output value maps to output 8
value values;
Val matches Output = matching Out 9 0 255 0xii Input 9 value 0xii
two or more input’s first output maps to output 9
input values value values;
Disable 0 255 unconnecte Val= 0
d NOTE: In123,In456, In789, Out 123,and Out456 are created
invalid Val = 0 by taking each individual input value (0-255) and
convert to a hex byte (0x00 – 0xFF) and putting first
VAL !=0 All mappings value in Most Significant Byte, 2nd value in middle
disable, pass input and 3rd value in Least Significant Byte. The end
to output result gives an integer value that must be stored as a
Val=0 Enable mappings float. So if In1 is 1, In2 is 2 and In3 is 3 then the inte-
ger would be 0x010203=66051, and the float value
In 1,2,3 0 167772 0xAABBCC See Note
stored as a parameter would be 66051.0. The tool
15.0 Input 1 value 0xAA
will prompt user for individual in1 out9 values and do
maps to output 1
the conversion both to and from the packed structure
values;
for the user.
Input 2 value 0xBB
maps to output 2
Input 3 value 0xCC
maps to output 3

85 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

Analog Outputs in5 HVAC 4 out5 NIGHT_MODE 7

_NIGH
T_PU
Range RGE
Input Input in6 HVAC 5 out6 COOL_MODE 0
Name Cfg Low High Value Description _PRE
Out OUT_D 0 255 See If input matches COOL
IG descriptio a block mapping in7 HVAC 6 out7 OFF_MODE 255
n and disable is _OFF
false, then output
in8 HVAC 7 out8 OFF_MODE 255
= block mapping.
_TEST
If input does not
mach a block in9 HVAC 8 out9 EMERG_HEAT 3
mapping or if _EME
disable is true, RGEN
the output = CY_H
input. EAT
fire OUT_D 0 1 See If disable is false Block 2 HVAC 9 Block2 not Pass through
IG descriptio and input passed _FAN_ used (output =9)
n matches a block throug ONLY (Does not
mapping then fire h require mapping
is true. If disable because the
is true then fire is output is the
true. same as the
input.)
Block2I HVAC 255 Block2Out1 REHEAT_MOD 1
For example, to map a standard HVAC enumeration into a n1 _NUL E
custom enumeration, the standard HVAC enumeration and
desired mapping is as follows:
The first encode function block parameters are:
• In 1,2,3 : 0,1,2 = 0x000102 = 258
• In 4,5,6: 3,4,5 = 0x030405 = 197637
Input • In 7,8,9: 6,7,8 = 0x060708 = 395016
In Enum Out • Out 1,2,3: 0,2,2 = 0x000202 = 514
Param eratio Parameter Output • Out 4,5,6: 0,7,0 = 0x000700 = 1792
eter nsCfg # Enumerations • Out 7: 255
• Out 8: 255
in1 HVAC 0 out1 COOL_MODE 0
• Out 9: 3
_AUT
O
And the Second block:
in2 HVAC 1 out2 HEAT_MODE 2
_HEAT • In 1,2,3: 255,0,0 = 0xFF0000 = 16711680
• In 4,5,6: 0,0,0 = 0x000000 = 0
in3 HVAC 2 out3 HEAT_MODE 2 • In 7,8,9: 0,0,0 = 0
_MOR • Out 1,2,3: 1,0,0 = 0x010000 = 65535
NING_ • Out 4,5,6: 0,0,0 = 0
WARM • Out 7: 0
_UP • Out 8: 0
in4 HVAC 3 out4 COOL_MODE 0 • Out 9: 0
_COO
L

EN2Z-0960GE51 R0710 86
 CENTRALINE LYNX TOOL - USER GUIDE

Connect as follows:

87 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

Hysteretic Relay onVal >=- <+ unconnect val = invalid

This function takes an analog input and sets the output TRUE infinit infinit ed Output = FALSE
at OnVal and FALSE at OffVal while honoring min on and off y y
times. From iteration to iteration, the Function Block keeps invalid val = invalid
track of the current minimum on or off time. On power up/reset Output = FALSE
this timer is cleared.
offVal >=- <+ unconnect val = FALSE
infinit infinit ed Output = invalid
y y
invalid val = invalid
Output = FALSE
minOn 0 6553 unconnect val = 0
5 ed
(sec) invalid val = 0
minOff 0 6553 unconnect val = 0
5 ed
(sec) invalid val = 0

Outputs
Inputs
Output
Range Name Range Description
Input Input OUTPU Any The output is set TRUE at OnVal and
Name Low High Value Description T floating FALSE at OffVal while honoring min on
point value and off times.
in >=- <+ unconnect val = invalid
infinit infinit ed Output = FALSE
y y
invalid val = invalid
Output = FALSE

EN2Z-0960GE51 R0710 88
 CENTRALINE LYNX TOOL - USER GUIDE

Maximum Ignore invalid inputs: Select this option if you want the
function block to ignore any invalid inputs, if any, and consider
This function calculates the maximum of 8 inputs (connected only the valid inputs to calculate the output. If this option is left
inputs or inputs set as constant). The output is set to the unselected, the invalid inputs will make the output also as
largest input. invalid.

Inputs

Range
Input Input
Name Low High Value Description
in1-8 >=- <+ unconnect Not used in calculation.
infinit infinit ed If all inputs are
y y unconnected, output is
invalid.
in1-8 >=- <+ invalid If any input is invalid then
infinit infinit output is invalid
y y
in1-8 >=- <+ valid Calculates the maximum
infinit infinit of 8 inputs or those set as
y y constant.
NOTE: If one or more inputs are selected as constant, any
previous connection from outputs of other functional
blocks to this block is removed automatically and the Outputs
maximum of the selected constant values is set as
the output.
Output
Name Range Description
OUTPU Any floating point Maximum of the inputs
T number

89 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

Minimum
This function calculates the minimum of 8 inputs or those set
as constant. The output is set to the smallest input. Unused/ Inputs
invalid inputs are ignored.

Range
Input Input
Name Low High Value Description
in1-8 >=- <+ unconnect Not used in calculation.
infinit infinit ed If all inputs are
y y unconnected, output is
invalid.
in1-8 >=- <+ invalid If any input is invalid then
infinit infinit output is invalid
y y
in1-8 >=- <+ valid Calculates the maximum
infinit infinit of 8 inputs or those set as
y y constant.

Outputs

Ignore invalid inputs: Select this option if you want the

function block to ignore any invalid inputs, if any, and consider Output
only the valid inputs to calculate the output. If this option is left Name Range Description
unselected, the invalid inputs will make the output also as OUTPU Any floating point Maximum of the inputs
invalid. T number

EN2Z-0960GE51 R0710 90
 CENTRALINE LYNX TOOL - USER GUIDE

Priority Select Setpoint

This function allows one to four inputs in any combination to
be individually enabled to override the default. The output is
the input with its highest priority enabled TRUE. Name Range/Value Description
In1AsDefa Yes Output is set to Input 1 even if all
ult Enable Inputs 1-4 are invalid
No Output is set to Invalid if all
Enable Inputs 1-4 are disabled.

Output

Output
Name Range Description
OUTPU Any floating point value The output is set to the
T input that is enabled.

• If all inputs are

unconnected, output is
invalid
• If all Enable inputs are
Login Inputs disabled, and all inputs
are invalid, output is
invalid
• If SetIn1asDefault is
Input Input Logic
enabled, output is
Name Value Value Description
Input1, even if all
enable1 VAL != 0.0 1 Enable inputs are
-4 disabled.
0 0 • When
SetIn1asDefault is
unconnect 0 disabled/Enabled and
ed if at least one Enable
invalid 0 input is enabled,
output is the input with
its highest priority
Analog Inputs enabled TRUE. The
priority order among
Enable inputs is:
Range 1. Enable1
Input Input 2. Enable2
Name Low High Value Description 3. Enable3
4. Enable4
in1-4 >=- <+ unconnect val = invalid
infinit infinit ed
y y
invalid val = invalid

91 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

Based on the In1asDefault option and the Enable options

selected, the output is set as Input as follows::
In1asDefault Enable Inputs 1-4 Inputs 1-4 Output
Enabled Disabled Output is set to Input1
Enabled Output is set to highest enabled input.
Disabled Disabled Output is invalid
One or more inputs Output is set to one of the Inputs 1-4 based on the
is Enabled priority order:
1. Enable1
2. Enable2
3. Enable3
4. Enable4

NOTE:

• Enable 1 has highest priority and if it is enabled,

output is taken as Input1.
• If Enable 1 is disabled, Enable 2 has the next
highest priority and if Enable 2 is enabled, output is
taken as Input 2.
• Enable 3 has the third highest priority and if Enable
1 and Enable 2 are disabled, output is taken as
Input 3.
• Enable 4 has the least priority and output is set to
Input 4 only if Enable 1-3 are disabled.

EN2Z-0960GE51 R0710 92
 CENTRALINE LYNX TOOL - USER GUIDE

Select Output
The Select function block selects one of the 6 input values to
be transferred to the output. The input selected depends on
the values of x and the offset. Output
Name Range Description
The default input allows multiple Select function blocks to be
tied together by chaining the output of one block to the default Output Any floating point Output = input (x-offset)
input of the next. When Select function blocks are chained, all value
chained blocks receive the same input, but different offsets, so
they examine different ranges of the input value. When (x-
offset) selects one of the 6 inputs, the output equals the value
Setpoint
on input (x-offset). Otherwise, the output equals the value on
the default input.
Name Range Description
offset 0 - 255 Used to determine the
output as Output = input (x-
offset)

NOTE: If any input is invalid, the output is invalid.

Output = Position determined by the value (X - Offset). If the

value of (X – Offset) is greater than 6, the default value is
taken as the Output.
If the value (X - Offset) is a floating point number between 0
and 6, the position is determined thus:
Analog Inputs • 0.10 – 0.99, 0 is returned and Input 0 is taken as Output
• 1.10 – 1.99, 1 is returned and Input 1 is taken as Output
• 2.10 – 2.99, 1 is returned and Input 2 is taken as Output
• 3.10 – 3.99, 1 is returned and Input 3 is taken as Output
Enable
• 4.10 – 4.99, 1 is returned and Input 4 is taken as Output
In1asDefa Inputs
• 5.10 – 5.99, 1 is returned and Input 5 is taken as Output
ult 1-4 Inputs 1-4 Output
Example 1:
Enabled Disable Output is set to Input1 X = 100, Offset = 97, default = 10
d
Output = 100 – 97 = 3, and hence Input 3 is taken as the
Enabled Output is set to highest output.
enabled input.
Example 2:
Disabled Disable Output is invalid
X = 100.6, Offset = 95.2, default = 10
d
Output = 100.6 – 95.2 = 5.4, and hence Input 5 is taken as the
One or Output is set to one of the output.
more Inputs 1-4 based on the
inputs is priority order: Example 3:
Enabled Enable1 X = 100, Offset = 5.2, default = 10
Enable2 Output = 100 – 5.2 = 94.4, and hence default value 10, is
Enable3 taken as the output.
Enable4
Note:
Enable 1 has highest
priority and if it is enabled,
output is taken as Input1.
If Enable 1 is disabled,
Enable 2 has the next
highest priority and if
Enable 2 is enabled,
output is taken as Input 2.
Enable 3 has the third
highest priority and if
Enable 1 and Enable 2
are disabled, output is
taken as Input 3.
Enable 4 has the least
priority and output is set
to Input 4 only if Enable 1-
3 are disabled.

93 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

Switch Setpoint
This function takes an enumerated type input and subtracts a
user defined offset to determine which output to set TRUE,
holding all others FALSE. The valid range of the input minus Output Range/
the offset is 0 through 7. Name Value Description
The output X (0 through 7) is TRUE if input – offset = X, else, offset 0 - 255 Used to determine which Output is set to
it is FALSE. TRUE based on the expression (input -
offset) = Output
Output = Output position determined by the value (input -
Offset). If the value of (input – Offset) is greater than 7, all
outputs are taken as FALSE.
If the value (input - Offset) is a floating point number between
0 and 8, the position is determined thus:
• 0.10 – 0.99, 0 is returned, Output 0 is TRUE and all other
outputs are FALSE
• 1.10 – 1.99, 1 is returned, Output 1 is TRUE and all other
outputs are FALSE
• 2.10 – 2.99, 2 is returned, Output 2 is TRUE and all other
outputs are FALSE
Analog Inputs • 3.10 – 3.99, 3 is returned, Output 3 is TRUE and all other
outputs are FALSE
• 4.10 – 4.99, 4 is returned, Output 4 is TRUE and all other
outputs are FALSE
Range • 5.10 – 5.99, 5 is returned, Output 5 is TRUE and all other
Input Lo Hig Input outputs are FALSE
Name w h Value Description • 6.10 – 6.99, 6 is returned, Output 6 is TRUE and all other
input 0 255 unconnect val = invalid, all outputs off. outputs are FALSE
ed • 7.10 – 7.99, 7 is returned, Output 7 is TRUE and all other
outputs are FALSE
invalid val = invalid, all outputs off.
in - offset all outputs off. Example 1:
>7 Input = 100, Offset = 97
in - offset all outputs off. Output = 100 – 97 = 3, and hence Output 3 is made TRUE
<0 and all other outputs are made FALSE.
Example 2:
Output X = 100.6, Offset = 95.2
Output = 100.6 – 95.2 = 5.4, and hence Output 5 made TRUE
and all other outputs are made FALSE.
Output
Name Range Description Example 3:
OUTPU Any The output 0 through 7 is TRUE if (input X = 100, Offset = 5.2
T 0-7 floating – offset) = X, otherwise it is FALSE Output = 100 – 5.2 = 94.4, and hence all Outputs are made
point If you negate an output, the output is FALSE.
value negated from the value determined by
the function block logic.

EN2Z-0960GE51 R0710 94
 CENTRALINE LYNX TOOL - USER GUIDE

BUILT IN FUNCTION BLOCKS

The CentraLine LYNXTool provides the following Built In • Schedule TUNCOS is the time (in minutes) until the next
function blocks that you can configure and use to build your change of state. The CentraLine LYNX controller uses this
application logic: to perform setpoint recovery.
• Schedule
• Wall Module Configure Schedules
— Conventional wall module You can configure occupancy schedules for eight days of the
— SBus wall module week: Monday through Sunday, and a holiday. There are four
events per day with one state/time per event. There are four
Schedule states:
The Schedule function block configures schedule and • Occupied
schedule assignment for the controller. The day and date is • Standby
used by the scheduler to determine the scheduled occupancy. • Unoccupied
The time of day and date may be updated by an external • Unconfigured
device via LON communications. This function calculates the The event time range is 0 - 1439 minutes. The event time
current occupancy state, next state and time until next state resolution is 1 minute. Zero is the first minute of the day at
(TUNCOS) based on the date/time and the schedule. 12:00 a.m. 1439 is the last minute of the day at 11:59 p.m.
Event times greater than 1439 minutes are illegal and the
event is treated as if the state were null.
The scheduled events execute in the order based on time of
day. It is not necessary for the events to be in time sequential
order. If the events are entered non-sequentially, the event
which is the earliest is executed and the next earliest and so
on. If an event state is not programmed (Unconfigured), the
event time can be anything and will not be used.
To configure a schedule:
1. On the Scheduling tab, click the day of the week to
select the day you want to configure the schedule.
2. Select a maximum of four events, Occ1, Occ2, Unocc1,
Unocc2, for the selected day. Use the drop down list to
Inputs specify occupancy status for the event. Notice that the
Date and Time from the operating system are the inputs to the cell turns green if the occupied mode is selected, white
Scheduler. for an unoccupied mode, yellow for a standby mode and
windows default background color for the unconfigured
Outputs option.
Schedule Current State is the occupancy state the controller 3. Click the hours, minutes, and/or AM/PM and use the up/
must be in at this minute. down arrow buttons to set the time.
4. Click Apply Event.
• OCC means use the occupied set point. 5. Repeat the steps 1 through 5 for the remaining days of
• UNOCC means use the unoccupied set point. the week and the Holiday.
• STANDBY means use the standby set point.
• Schedule Next State is the occupancy state the controller
will go to after the current state is complete. To unconfigure a day schedule/event:
• OCC means the next state is occupied. 1. Select the row/cell of the day whose schedule you want
• UNOCC means the next state is unoccupied. to unconfigure.
• STANDBY means the next state is standby. 2. Right-click the row/cell and select Delete. The schedule
• OCCNUL means the next state is unknown. for that row/cell is unconfigured.

To copy the schedule from one day/event to another:

95 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

Configure Holiday Schedules Month list and the date from the Select Holiday Start
You can schedule a maximum of 10 holidays. Each scheduled Date list to specify the holiday start month and start
holiday has a valid start month, day, and duration. Holidays date.
are every year by definition. After the start month/date is 4. Select the month, start date, and duration of the holiday
calculated, the duration is added to find the end date. If it is a from the Select Holiday Start Month, Select Holiday
one day holiday, then the duration is one day. The end date is Start Date, and Duration fields respectively. The dura-
set to the start date. If the current date is within the start and tion can be configured from 1 to 255 days.
end dates, inclusive, then it is a holiday. 5. Select one of the options provided and click Add to add
to the Holiday list.
You can specify holidays in any order in the list. Holidays do 6. To remove a holiday from the Holiday List, select the
not have to be in date consecutive order. The Scheduler is holiday and click Remove.
called once per second and ensures that the clock time of the
day is valid. It computes the occupancy by examining the
programmed schedule. It looks at the current date/time and Load U.S. Holidays
compares it to the entered schedule and holidays to To select the list of US holidays to your holiday list, click the
determine the current state, next state and TUNCOS. Load US Holidays button. The following pre-configured US
A holiday is configured by a start date and duration. The start holidays are loaded to the holiday list:
date can be a specific date or a relative day in a month. A • January 1
holiday is not specific to a particular year, each holiday • Memorial Day
configuration is applicable for every year. • July 4
A holiday can be configured by either specifying a date or by • Labor Day
specifying a day in a month. To configure a Holiday schedule: • Thanksgiving and Day After
• Christmas Eve and Day After
1. Click the Holidays tab. You have options to select holi- If there are more than four holidays already configured, the
days based on weekday/month every year or on a spe- Load US holidays option will not load all the six holidays, since
cific date every year. they would exceed the maximum holiday count. The first few
2. To specify a weekday/month for every year as a holiday, US holidays are loaded until the total count has reached the
select the Weekday/Month for every year option to con- maximum of 10 holidays. No duplicate holidays are allowed.
figure a holiday by selecting a weekday in a month.
Select the month from the Select Holiday Start Month
list and the day from the Select Holiday Start Day list Save Schedule
to specify the holiday start month and start day. The • Click Apply to save the changes you made to the
days are the relative days, such as, First Sunday, schedule.
Fourth Monday, and so on. • Click OK to save the changes and close the Schedule
3. To specify a specific date(s) every year as a holiday, dialog box.
select the Specific Date for every year option to con- • Click Cancel to close the Schedule dialog box without
figure a holiday by selecting a specific date for every saving the changes.
year. Select the month from the Select Holiday Start

EN2Z-0960GE51 R0710 96
 CENTRALINE LYNX TOOL - USER GUIDE

Conventional Wall Module NOTE: Only one wall module block for each type (SBus and
Conventional) is supported by the LYNX tool.
The LYNX tool supports configuring the SBus wall module (2-
wire wall module) in addition to the conventional wall module 3. Right click the conventional wall module block and
(7-wire) for the LonLYNX II, and LYNX Micro models. You can select Configure Properties. The Wall Module Configu-
have a maximum of one SBus and one conventional wall ration Wizard appears. You can configure General Set-
module per control program. If you add more than one SBus tings for the conventional wall module.
or conventional wall modules to an application, a message
appears stating that you must delete the extra wall module
before downloading the application logic to the controller. Procedure
To configure the conventional wall module: 1. Click the General Settings button on the left pane to
open the General Settings page.
1. Expand the BuiltIn folder in the CentraLineLYNX palette. 2. Enter information into available fields.
2. Drag the Conventional wall module on to the wiresheet 3. Click Finish to save the settings or Cancel to revert to
or on to the ControlProgram in the Nav palette. The the last saved settings.
Conventional wall module block appears on the
wiresheet. FIELDS

Name Definition
Block Name Enter a name for the Wall module block.
Block Type Displays the type of wall module.
Wall Module Model
Wall Module Type Displays the wall module type selected.

NOTE: For a Conventional wall module having links on the

wiresheet, if you change the Wall module type to that of an
SBus wall module, a warning stating that the links will be
deleted if you try to change the model type, appears.
Model Options Use these options only if you want to change the wall module to an
SBus wall module. If you check either option, a message appears
informing you that the model selection has been changed and that all
settings of the conventional wall module will be lost. You must confirm
to proceed. Also, with this confirmation, you have decided to change
over to an SBus wall module type. To proceed further, see the
Conventional wall module section. If you want to continue configuring
a conventional wall module, read on.
Select Model You can choose one of three options:
• NORMAL_OVERRIDE
• BYPASS_ONLY_OVERRIDE
• OVERRIDE_DISABLED
Bypass Time Source Select one of the following options:
• Fixed Parameter
• Variable Input
Enter the Time in Minutes.
Finish Saves the configuration changes you have made.
Cancel Exits the wizard without saving the configuration changes.

97 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

SBus wall module If you change one of the following and perform a quick
download, only the changed configuration is downloaded to
The LYNX tool supports configuring the SBus (Sensor-Bus) the controller.
wall module (2-wire wall module) in addition to the
conventional wall module for the LonLYNX II and LYNX Micro — Toggling the Viewable by Tenant check box.
models. You can have a maximum of one SBus and one — Changing the default home screen only.
conventional wall module per control program. Additionally, — Changing the default value of Value from wall module.
Bacnet LYNX models also support configuring the SBus wall — Changing the default value of Sensor or Offset param-
module. eters.
For all other changes, the whole configuration is downloaded
NOTE: If you add more than one S-Bus or conventional wall (full download) to the controller.
modules to an application, the following message You can save these applications to the LYNX library for later
appears, stating that you must delete the extra wall use. Applications that are stored can be imported from the
module before downloading the application logic to library and used to rapidly build application logic.
the controller. You can also delete an already configured S-Bus wall module
function block if necessary.
However, if you fail to delete the second wall module and click
the Validate button on the toolbar, an error message appears. You can:
Click OK to close the message window and delete the extra — Connect the S-Bus wall module to the controller and
wall module before downloading the application logic. use the LYNX tool to configure it by using the S-Bus
wall module function block in the control program.
You can configure different models of the S-Bus wall modules — Save the configuration changes you make and down-
in one of two ways. load it to the controller
1. You can invoke the configuration wizard of the S-Bus — Upload the changes in settings you make on the wall
wall module function block and use the wizard screens module display to the LYNX controller using the LYNX
to configure the wall module. Use the Preview screen to tool
preview the configuration you have made. You must — Simulate the S-Bus wall module logic using the Simu-
download the configuration changes made to the con- lation feature of the LYNX tool
troller to view the configuration changes on the Wall — Store the S-Bus wall module configuration in the LYNX
module. library to be reused across applications
2. You can configure locally using the display screen of the Use the Wall Module Configuration Wizard to configure the S-
wall module mounted on the wall. This can be done only Bus wall module.
in the Contractor mode.
After completing the configuration, link the slots on the S-Bus Initial Setup and Configuration
wall module function block of the control program logic of the
LYNX tool as required. The input and output slots of the Wall Once the wall module is wired to the controller, you configure
module can be connected to other function blocks, Physical/ the wall module using the LYNX tool.
software points, and NVs/Bacnet objects, to develop the
CONFIRM BUS ADDRESS SETTING
application logic. You can then download the configuration to
the controller. This configuration is then automatically Check to ensure that the bus address dial (located on the
downloaded to the S-Bus wall module by the LYNX controller. back of the module) of the Wall Module is set to one (1) to
match the default setting of the configuration tool.
If you have made changes to the configuration locally on the
wall module, you can upload the same to the controller. Note NOTE: Multi-drop installations are not available at this time.
that the wall module configuration is not uploaded directly to Only one wall module may be wired to the program-
the LYNX tool. So, you need to upload the LYNX controller mable controller.
configuration to the tool in order to upload the wall module
configuration.

EN2Z-0960GE51 R0710 98
 CENTRALINE LYNX TOOL - USER GUIDE

Configuring S-Bus wall module You can configure the following settings using the Wizard and
are displayed on the left pane of the wizard:
To configure the S-Bus wall module using the configuration
wizard: — General Settings
— Categories and Parameters
1. Expand the BuiltIn folder in the CentraLineLYNX palette. — Home Screen Options
2. Drag and drop the S-Bus wall module on to the — Occupancy and Override
wiresheet or on to the ControlProgram in the Nav pal- — Fan Command
ette. The S-Bus wall module block appears on the — System Status and Command
wiresheet. This block only shows slots relevant to the — Preview
configuration that you have made. By default, slots con-
figured in standard applications will be shown as part of NOTE: When you drag and drop the S-Bus wall module on
the wall module block. the wiresheet, right click it, and select Configure
Properties, the General Settings properties are dis-
NOTE: Only one wall module block for each type (S-Bus and played in the Wizard window.
Conventional) is supported by the LYNX tool. If you
drop more than one block of the same wall module
type, the tool gives a warning message and does not General Settings
allow the addition of the second wall module of the Use this page to configure the general settings of the S-Bus
same type. wall module.

3. Right-click the S-Bus wall module block and select Con- PROCEDURE
figure Properties. The Wall Module Configuration Wiz- 1. Click the General Settings button on the left pane to
ard appears. open the General Settings page.
2. Enter information into available fields.
3. Click Finish to save the settings or Cancel to revert to
the last saved settings.
4. Click Next to display the Categories and Parameters
page.

FIELDS

Name Definition
Block Name Enter a name for the Wall module block.
Block Type Displays the type of wall module.
Wall module model
Wall Module Type Lists all wall module models supported by LYNX. The following
options are available:
• Temperature Only
• Temperature, Humidity
• Temperature, CO2
• Temperature, CO2, Humidity
Depending on the wall module type selected, the available models are
displayed in the Select Model list.
The Wall Module type you select determines the function block type. If
you select a model of Conventional wall module type, the function
block becomes a Conventional wall module. Similarly, if the module
type selected is an S-Bus wall module, the function block becomes a
S-Bus wall module.

NOTE: For a Conventional wall module having linkages on the

wiresheet, if you change the Wall module type to that of an S-
Bus wall module, a warning stating that the linkages will be
deleted if you try to change the model type appears.

99 EN2Z-0960GE51 R0710
CENTRALINE LYNX TOOL - USER GUIDE

Model Options You have the following model options to choose from:
• LCD Display
• 2 wire Sensor Bus Communication
For the current LYNX version, the available models have both LCD
display and 2-wire Sensor Bus Communication options and therefore
selecting any one option automatically selects the other.

NOTE: Based on the Wall Module Type and the Model Option
selected, the Model Selection list displays the available mod-
els.

Changing conventional wall module to S-Bus and vice-versa

You can suitably change the wall module you have dropped on to the
wiresheet by checking the Model Options check-boxes. If you have
dropped a conventional wall module on the wiresheet and check any
of the Model Options check-boxes, the wall module changes to a S-
Bus wall module and all the wizard buttons are displayed on the left
pane. Similarly, if you have dropped an S-Bus wall module on the
wiresheet and uncheck the Model Options checkbox, the wall module
changes to that of a conventional type and all wizard buttons except
for the General Settings disappear from the left pane.

Select Model The options available in this list are based on the Wall Module Type
and Model Option selected.
Example: If you select Temperature Only as the Wall Module Type
and LCD Display as the Model option, The Select Model list lists Temp
(LCD, 2 Wire) as the selectable option.
Application Selection These fields are available only if a level 3 (TR 70) model is selected.
For all other models, these fields are hidden.
Application Type This field appears automatically when a level 3 model is dropped on
the wiresheet or if you select a level 3 model from the Wall Module
Type list. You can select one of three applications:
Standard Application (default): Displays the eight pre programmed
application names in the Select Application List.
Custom Application: Displays existing custom applications in the
Select Application List.
New Application: This selection hides the Application Selection list
and displays all the wizard menu items along the left side of the
window.

EN2Z-0960GE51 R0710 100

 CENTRALINE LYNX TOOL - USER GUIDE

Select Application Select from one of the eight pre programmed applications:
• VAV- Min/Max Balance, Network Override: Typical set-up for a VAV
system pre-configured with a Min/ Max Airflow balancing method
(balancing can be done through the wall module keypad), and uses
the network determined occupied override duration.
• VAV- K-Factor Balance, Network Override: Typical set-up for a VAV
system pre-configured with a KFactor method of balancing
(balancing can be done though the wall module keypad), and uses
the network determined occupied override duration.
• VAV- No Balance, Network Override: Typical set-up for a VAV
system. No balancing loaded, which frees up additional memory if
greater controller parameter access is desired. Uses the network
determined occupied override duration.
• VAV- No Balance, Full Override: Typical set-up for a VAV system.
No balancing loaded, which frees up additional memory if greater
controller parameter access is desired. Loaded with a user
adjustable occupied override time from 30 minutes to 3 hours, as
well as an adjustable vacation (multiple day) override (unoccupied),
and a continuous unoccupied time.
• FCU- Network Override: Typical set-up for a fan coil system pre-
configured to use the network determined occupied override
duration.
• FCU- Full Override: Typical set-up for a fan coil system pre-
configured to use the network determined occupied override
duration. Loaded with a user adjustable occupied override time
from 30 minutes to 3 hours, as well as an adjustable vacation
(multiple day) override (unoccupied), and a continuous unoccupied
time.
• CVAHU- Network Override: Typical set-up for a CVAHU system
pre-configured to show system status and system override (heat,
cool, auto, etc., like a thermostat), and uses the network
determined occupied override duration.
• CVAHU- Full Override: Typical set-up for a CVAHU system pre-
configured to show system status and system override (heat, cool,
auto, etc., like a thermostat). This status can be removed. Loaded
with a user adjustable occupied override time from 30 minutes to 3
hours, as well as an adjustable vacation (multiple day) override
(unoccupied), and a continuous unoccupied time).
This drop-down list displays applications which are either compatible
in terms of either the onboard sensor or a subset of the onboard
sensor of the selected model. For example, if a model with T+CO2
sensor is selected the Select Application list will just display
applications having T/CO2/T+CO2/none sensors. Based on the
Application Type selected, this list shows the available Level 3
applications.
Standard CentraLine applications are tied to models based on the
sensor parameters available. However, all standard applications are
shown in the Select Application list. For example, if model selected
has humidity parameter, the application may have home screen with
humidity shown.
Custom applications are also tied to the sensor parameters for each
model. However, all user defined applications are shown in the Select
Application list. If you select an application that contains different
sensor parameters than the model selected, the application will still
maintain all the parameters and settings and it is up to you (via
Customize button) to add/remove manually.
The default custom application is the first (if any) application at the
default location. If no applications are in the custom library, Select… is
shown.

101 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

Customize This button is visible only if you select a saved Standard or Custom
application from the Select Application list.
A message appears informing you that the changes you make must
be saved as a new application. If you confirm, the Select Application
list and Block Name changes to New Custom Application.

NOTE: Pressing the Customize button shows all the wizard steps
and buttons.
Browse Only if you have selected a Custom Application type, you have the
option to browse to different file locations to view the custom
applications you have created.

NOTE: This button is hidden for both Standard and New application
types.
Wall Module Address This field is hidden for any wall modules that are not on 2 wire bus or
have LCD display (all LCD wall modules are 2 wire).
Select an address from 1 through 15 that indicates the address for the
selected wall module on the 2 wire bus (corresponding to dip switch
selections). The default selection is 1.
Time Display Format Specify whether time is shown in 12 hour or 24 hour units.
Show wall module memory usage Shows current memory usage for the wall module. Memory updates
are made any time a change is made to the configuration (Save,
Remove, Next, Back, Finish).
The current memory usage in shown in 1% increments. A bar graph
indicating current memory usage is provided in the lower left of the
wall module window.

NOTE: Memory usage must be less than 100% in order to download

the configuration to the programmable controller.

If the memory usage exceeds the maximum limit, a message appears

indicating that the configuration must be modified in order to reduce
the memory usage before downloading the configuration.
If the memory bar is not visible, click the Show check box in the lower
left of the window.
The memory usage help message shows the distribution of memory
for each configured component graphically and in a tabular format.
Save to Library Saves the wall module configuration to the LYNX library.

NOTE: See Save Items to Library for more information about how to
save this configuration to the library.
Preview Previews the wall module selected, which includes a model preview
image of the actual wall module, and configuration you have chosen.
This appears in the preview area at the bottom of the wizard screen.
Next Moves to the Categories and Parameters wizard window.
Finish Exits the wizard after saving the configuration changes.
Cancel Exits the wizard without saving the configuration changes.

EN2Z-0960GE51 R0710 102

 CENTRALINE LYNX TOOL - USER GUIDE

Categories and Parameters block changes to reflect the new category but any links to the
Use this page to configure the categories and parameters of application logic remain. You can also drag and drop
the S-Bus wall module. All available categories and parameters between categories. This results in a copy of the
parameters are displayed in a hierarchical tree structure. You parameter being added.
can expand and collapse the tree levels. Selecting a level
PROCEDURE
shows the preview associated with the selected level (whether
category or parameter) at the bottom of the screen in the 1. Click the Categories and Parameters button on the left
Category Preview area. The first category is highlighted by pane to open the Categories and Parameters page.
default and preview is shown. 2. Enter information into available fields.
3. Click Finish to save the settings or Cancel to revert to
You can use the context menu (right-click menu) to cut, copy, the last saved settings.
paste, delete, parameters across categories. You can also
drag, and drop parameters across categories. When a FIELDS
parameter is dragged and dropped under a category, a slot is
added to the function block. If you move a parameter to a
different category (cut and paste) the slot name in the function
Name Definition
Up/Down arrow reorder buttons Re-orders the sequence of categories and parameters in the wall
module. The buttons are disabled only for the first and last items of the
list.
Add Category Adds a new category at the bottom of the tree with the default name is
CATEG#, where # is determined by the number of categories in the
tree (starting at 1). See the Sensor Details Fields section of this table
for more information.
Add Parameter Adds a new parameter below the selected category at the bottom of
the tree with the default name PARAM##, where ## is determined by
the number of parameters in the tree (starting at 1). The Parameter
details screen appears. See the Sensor Details Fields section of this
table for more information.
Edit Takes you to the corresponding detail screen to edit configuration
details of the selected category/parameter.
Remove Removes the selected category/parameter from the tree.
You can remove only those categories/parameters that are not
referenced in any homescreen. If you still want to remove such
parameters/categories, you must remove references to the parameter/
category in the homescreen before you can do so.
Only after all references are removed will you be able to remove the
category/parameter.
If you remove a parameter/category which is not used in one or more
home screens, there is no scope to undo this change.
Category details - These fields are available when you add/edit a category.
Category Name Displays the name of either the newly created category (CATEG1) or
the selected category (SENSORS). You can edit the name.
The category name has a limit of 8 characters and cannot begin with a
numeric or special character.
Examples of invalid category names: 2category or.categ2
Examples of valid category names: Categ1 or categ123
Description Displays the brief description of the category.
The description has a limit of 255 characters.
Number of Parameters A read-only field that displays the number of parameters under the
selected category.
For newly created categories, the number of parameters would be 0.
Save Saves the configuration changes after displaying a message asking
you to confirm saving the changes made. After confirmation, the
preview screen appears.
It is disabled until a configuration change is made.
Cancel Cancels the configuration changes made and ignores any changes
made.
On clicking Cancel, a message appears indicating that the changes
made will be lost. On confirmation, the Preview screen of the selected
category (or parameter) appears.
Parameter details - These fields are available only when you add/edit a parameter.

103 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

Parameter Name Displays the name of either the newly created parameter (PARAM1)
or the selected parameter (CO2). You can edit the name.
Parameter name must be unique within a category. If you try to save a
parameter with an existing parameter name, a message appears
indicating that a parameter with the name already exists.
For a parameter of the category OFFSET, default names appear. The
default names are as follows:
• Temperature: TEMPOFST
• Humidity: RH OFST
• CO2: CO2 OFST
The parameter name has a limit of 8 characters and cannot begin with
a numeric or special character.
Viewable by Tenant Check this option for parameters that need to be displayed to the
tenant.
Editable by Tenant Applies to the following Parameter Types:
• Value from Wall module
• Dynamic value
• Sensor offset value
Description Displays the brief description of the parameter.
The description has a limit of 255 characters.
For a parameter of the category OFFSET, this field, by default displays
the parameter name.

EN2Z-0960GE51 R0710 104

 CENTRALINE LYNX TOOL - USER GUIDE

Parameter Type You can select one of the following parameter types:
• Value from Controller: These are also called as "IN"
parameters.Only inputs can be connected to these
parameters.When values change in the controller, they are
reflected in the SBusWallModule.There can be a maximum of 30 IN
parameters. This includes the "IN" type parameters configured
from Parameters and Categories screen, Occupancy status
configured from Occupancy/Override screen and System Status
configured from System Status and Command screen.Time Of Day
type parameter is also considered as an "IN" parameter.
• Value from Wall module: These are also called as "OUT"
parameters.These parameters can be connected to input slots of
function blocks. There can be a maximum of 19 OUT parameters.
This includes the OUT type parameters configured from Categories
and Parameters screen, Enable Occupancy Override option
configured from Occupancy/Override screen, Enable Fan
Command option configured from Fan Command screen and
Enable System Command option configured from System Status
and Command screen.
• Dynamic value (Last one wins): Dynamic value parameters are
both inputs and outputs and are also called "IN-OUT"
parameters.LYNX sends these values to SBusWallModule to be
displayed. You can also modify them from the wallmodule.
Example: NCIs. These parameter types can be created in the
SBusWallModule configuration and linked to NCI slots in the
application. There can be a maximum of 10 IN-OUT
parameters.This includes the "IN-OUT" type parameters configured
from Parameters and Categories screen, Network Bypass Time in
Occupancy/Override screen. The time components - hours,
minutes, days, month, year of Time parameters are also
considered as dynamic values.
• Temperature from wall module (depends on model): For SBus
wall modules supporting temperature sensor, this parameter gives
the temperature sensor output which can be used in the
application.
• CO2 from wall module (depends on model):For SBus wall
modules supporting CO2 sensor, this parameter gives the CO2
sensor output which can be used in the application.
• Humidity from wall module (depends on model): For SBus wall
modules supporting humidity sensor, this parameter gives the
humidity sensor output which can be used in the application.
• Sensor offset value: Depending on the SBus wall module type,
this parameter defines offset values for the sensor parameter type.
• Time: Consists of the following time components:
Time of Day: This value is derived from the controller.
Hours (Dynamic value): This can be set by the user or derived
from the controller.
Minutes (Dynamic value): This can be set by the user or derived
from the controller.
Days (Dynamic value): This can be set by the user or derived from
the controller.
Month (Dynamic value): This can be set by the user or derived
from the controller.
Year (Dynamic value): This can be set by the user or derived from
the controller.
Select Sensor Displays the list of sensors you want to configure an offset for. All
available sensors are listed but the selection is based on the selected
model. The default selection is Temperature.
This field is displayed only for a parameter of the category OFFSET.
Number of Decimals Applies to all parameter types except Time. For This value affects
Increment/Decrement options.

105 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

Default Sensor Offset Value The default value for the following parameter types:
• Temperature from wall module
• Humidity from wall module
• CO2 from wall module
The default value has a limit of 5 characters.

NOTE: For the Parameter Types Temperature/Humidity/CO2 from

wall module, if you edit this value and save the changes, the
Default Value of the Sensor Offset Value of the corre-
sponding sensor also changes to the edited value.
Default value The value that will be initially downloaded to the wall module. This
value must be between the Low and High limits. This field is displayed
for the following parameter types:
• Value from wall module
• Sensor offset value
By default it is set to 0.
Show Temperature Units as Provides options to select the temperature units for display on the wall
module when the Parameter Type selected is Temperature from
wall module. Fahrenheit and Centigrade options are available and
Fahrenheit is the default selection.
Increment/Decrement Depends on the Number of decimal places selected.
If number of decimal places = 0, then increment/decrement = 1, 10,
100.
If number of decimal places = 1, then increment/decrement = 0.1, 1,
10, 100.
If number of decimal places = 2, then increment/decrement = 0.01,
0.1, 1, 10, 100.
Low limit Defines the low limit for the adjustable value. This limit is used at the
wall module. Once the limit is reached, additional button presses have
no effect. The value is determined by the number of decimal places.
For example, if the number of decimals = 1, then the low limit is shown
as XXX.X (0.0 for default).
The Low Limit must not be greater than the High Limit.
High Limit Defines the high limit for the adjustable value. This limit it used at the
wall module. Once the limit is reached, additional button presses have
no effect. The value is determined by the number of decimal places.
For example, if the number of decimals = 1, then the low limit is shown
as XXX.X (999.9 would be default).
The High Limit must not be lesser than the Low Limit.
Allow null values Indicates whether null values can be set for the adjustable value. If
enabled, when the LCD user reaches a low/high limit, an additional
button press will send the null value.
Time Component Indicates the time and the time format you want to configure. This field
is available only if the Parameter Type selected is Time.
You have the following options:
• Time of Day (From controller, Read Only)
• Hours (Dynamic value)
• Minutes (Dynamic value)
• Day (Dynamic value)
• Month (Dynamic value)
• Year (Dynamic value)
If Time of Day option is selected, Editable by Tenant is disabled
(because TOD is read only). However, you can enable Viewable by
tenant and Editable by tenant for other Time Component options.
The following fields are available to all categories and parameters.
Preview Gives a preview of the wall module selected along with the model
preview image and configuration you have chosen in the model
preview area at the bottom of the wizard screen.
Back Moves to the General Settings wizard window.
Next Moves to the Home Screen Options wizard window.
Finish Exits the wizard after saving the configuration changes.

EN2Z-0960GE51 R0710 106

 CENTRALINE LYNX TOOL - USER GUIDE

Cancel Exits the wizard without saving the configuration changes.

Show wall module memory usage Shows current memory usage for the wall module. Memory updates
are made any time a change is made to the configuration.
The memory usage help message shows the distribution of memory
for each configured component graphically and in a tabular format.
If the memory usage exceeds the maximum limit, a message appears
indicating that the configuration must be modified in order to reduce
the memory usage before downloading the configuration.
Save to Library Saves the wall module configuration to the LYNX library

NOTE: See Save Items to Library for more information about how to
save this configuration to the library.
Preview Area
Labels Users can define the segments (labels) to show by selecting the
corresponding boxes. Selecting a box toggles the segment (label) on/
off. Selected segments (labels) are shown in Preview and in LCD.
Next soft key Displays the preview image of the next category/parameter.
Previous soft key Displays the preview image of the previous category/parameter.
Middle soft key

NOTE: If you edit a parameter that is used in a home screen Click the labels in the preview area (in the Contractor mode)
and save the configuration, the change (any custom- to enable/disable the labels which need to be made visible to
ization already done in home screen is changed) is the tenants on the wall module screens for the selected
also reflected in the home screen. parameter. Changes made to parameter labels do not affect
home screens.
If the change applies to parameter name, type, number of If you edit a parameter and change the parameter type, any
decimals, limits, increment/decrement, default value, a links to the parameter slot in the control program will be lost.
message appears indicating that the parameter is used in one
or more home screens and options are provided to save this DEFAULTS
change or discard it.

Parameter Type Default values

Value from controller • Viewable = Not selected
• Number of decimals = 0
Value from wall module • Viewable = not selected
• Default value = 0
• Number of Decimals = 0
• Increment/decrement = 1
• Low limit = 0
• High limit = 9999
• Allow null = not selected
Dynamic value (Last one wins) • Viewable = not selected
• Number of Decimals = 0
• Increment/decrement = 1
• Low limit = 0
• High limit = 999
• Allow null = not selected
Temperature from wall module • Viewable = not selected
• Number of Decimals = 0
• Default sensor offset value = 0
• Show temperature units as = Deg.F

107 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

CO2 from wall module • Viewable = not selected

• Number of Decimals = 0
• Default sensor offset value = 0
Humidity from wall module • Viewable = not selected
• Number of Decimals = 0
• Default sensor offset value = 0
Time PT • Viewable = not selected
• Time component = Time of day (From controller, read only)
Sensor Offset value • Viewable = not selected
• Default value = from sensor parameter (0 unless user changes it)
Default values for Sensor OFFSET
Field Temperature Humidity CO2
• No Decimals 1 0 0
• Increment/Decrement 1 1 1
• Low limit -5 -5 - 100
• High limit 5 5 100

EN2Z-0960GE51 R0710 108

 CENTRALINE LYNX TOOL - USER GUIDE

Home Screen Options PROCEDURE

Use this page to see the available home screen options that 1. Click the Home Screen Options button on the left pane
are configured in the wall module. All available home screen to open the Home Screen Options page.
options are displayed in a list view. Selecting a home screen 2. Enter information into available fields.
shows the preview associated with the selected home screen 3. Click Finish to save the settings or Cancel to revert to
option at the bottom of the screen in the Home Screen the last saved settings.
Option preview Area. You can use the Next (soft key on the
extreme right) and Previous (soft key on the extreme left) soft FIELDS
keys in the preview area to preview the other home screen
options in the list. The first home screen option is highlighted
by default and its preview is shown.
Name Definition
Set as Default Sets a selected home screen option as the default home screen.
You can change the default home screen by selecting another home
screen from the list and then clicking this button. Default appears in
parentheses along with the home screen name.
Add Adds a new home screen option at the bottom of the tree. The Home
Screen details screen appears.
Two home screens cannot have the same name. You must provide
unique name to home screens.
Edit Takes you to the corresponding detail screen to edit configuration
details of the selected home screen.
Remove Removes the selected home screen from the list. A message appears
indicating that this action cannot be undone and a confirmation is
sought. On confirmation, the home screen is removed.
Up/Down Arrow reorder buttons Re-orders the sequence of home screens in the wall module. To re-
order the sequence of home screens, click the home screen name
and use the up/down arrow to move it up/down in the list. The buttons
are disabled only for the first and last items of the list.
Home Screen Details
Option Name Displays the name of the newly created home screen. Enter a unique
home screen name for each option that you create. If you type a name
that already exists, a message appears asking you to change the
name as such a name already exists.
The option name has a limit of 32 characters.
Set as Default A check mark for this option indicates that this is the default home
screen option.
As only one home screen option can be set as the default screen, the
last home screen to be selected as default becomes the default home
screen.
This option is not checked by default for every new home screen that
is added. However, the exception is that if there are no other home
screens in the list (this is the first), the set as default button is checked
automatically.
Description Displays the brief description of the home screen. This description is
shown on mouse over of a home screen option in the preview area.
The description has a limit of 255 characters.
Option Type Displays the two home screen option types available. Based on this
selection, you are provided with options to select parameters and
labels which you can view in the preview area.
Multiple parameters: Select up to three parameters and any labels
(fixed segments)
Single parameter: Select one parameter and provide a unique 8
character label. You can also select any labels (fixed segments) to
show.
Save Saves the configuration changes you make. It is enabled once any
change is made on the screen.
Back Moves to the Categories and Parameters wizard window.

109 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

Next Moves to the Occupancy and Override wizard window.

Finish Exits the wizard after saving the configuration changes.
Show wall module memory usage Shows current memory usage for the wall module. Memory updates
are made any time a change is made to the configuration.
The memory usage help message shows the distribution of memory
for each configured component graphically and in a tabular format.
If the memory usage exceeds the maximum limit, a message appears
indicating that the configuration must be modified in order to reduce
the memory usage before downloading the configuration.
Save to Library Saves the wall module configuration to the LYNX library.

NOTE: See Save Items to Library for more information about how to
save this configuration to the library.

PREVIEW AREA

Name Definition
Label and Parameter Selection Section Define the segments (labels) to show by selecting the corresponding
boxes in the preview area. Selecting a box toggles the segment (label)
on/off. The selected segments (labels) are shown in the Preview and
in the LCD display.
If the Option Type you select is Multiple Parameter:
You have three drop-down lists (right, left, and central) to select the
parameters that you want to display on the home screen.

NOTE: For the left and right drop-down lists, you cannot select a
parameter of type Time and Time of Day as the Time com-
ponent. If you select Dynamic value (Last one wins) or
Value from wall module as the Parameter Type, a mes-
sage appears suggesting you to move it to the central drop-
down list as the right and left drop-down lists have a limit on
the number of digits that can be displayed.

If you select a parameter with more digits than are available based on
position, the available digits are rounded off to the maximum digits
permitted by the wall module. For example, if you wanted to show a
CO2 value of 1200 in the left drop-down list, it would be displayed as
999 on the display (shown in the Preview).
• If the Option Type you select is Single Parameter
You have a single drop-down list and a field to enter a label name.

NOTE: The label name cannot exceed 8 characters and cannot

begin with a special character or a numeral.

EN2Z-0960GE51 R0710 110

 CENTRALINE LYNX TOOL - USER GUIDE

Occupancy and Override PROCEDURE

Use this page to view Occupancy settings and enable 1. Click the Occupancy and Override button on the left
Occupancy Override. The Preview Area at the bottom of the pane to open the Occupancy and Override page.
screen displays the occupancy and override options you have 2. Enter information into available fields.
selected for the wall module. 3. Click Finish to save the settings or Cancel to revert to
the last saved settings.

FIELDS

Name Definition
Enable Occupancy Override Enables occupancy override and the current override state
configuration is shown in parentheses.
You have the following options:
• Occupied: This option is displayed once you enable the Enable
Occupancy Override option.
• Unoccupied: This option is displayed only if you click the Show
Advanced Settings button.
• Standby: This option is displayed only if you click the Show
Advanced Settings button.
If the Occupancy Override Type (see next row in the table for more
details) is set to
• Continuous: The status is shown as Continuous.
• Timed (Days/Hours): The status is shown as Min and Max hours/
days selected.
Checking the Enable Occupancy Override option also automatically
checks the Occupancy check box.
If you check this option but do not have any valid states checked, a
message appears asking you to configure at least one override state
or disable the occupancy override feature.
Settings Displays the Override to (Override Type selected) Settings window
that lets you set the Override Type. You have the following options:
• Continuous Override: The default setting, this setting disables the
time override type options.
• Timed Override in Hours: This option enables the Time Setting
Details, wherein you can set the Minimum Time and Maximum
Time in Hours and Minutes. The default setting is Min = Max = 3
hours. Make sure that the Maximum Time is greater than the
Minimum time or that the Minimum Time is lesser than Maximum
Time. If either case is not true an error message appears informing
that the min value is greater than max value. The range is from 0 to
24 hours.
• Timed Override in Days: This option enables the Time Setting
Details, wherein you can set the Minimum Time and Maximum
Time in Days. In this case, the Hours and Minutes options are
disabled. The default setting is Min = Max = 1 day. The range is
from 1 to 99 days.

NOTE: If the range is exceeded, an error message appears to inform

you of the same.

Use Network Bypass Time Only: If you select this option all other
override details are disabled. The timed override details will be
determined by the LYNX application.

NOTE: The Use Network Bypass Time Only option only applies to
Occupied override type settings. This option is not available
for Unoccupied and Standby override type settings.
Show Advanced Settings Displays the following advanced override occupancy settings:
• Unoccupied
• Standby
• Occupancy Values: Defaults will follow the LONMark standards

111 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

Occupancy Status Display Options Provides options to select how you want override status to be
displayed in the LCD. The options are:
Show effective occupancy status: LCD shows the actual occupancy
status taking into account the LYNX application.
Show occupancy override status: LCD shows the occupancy override
status initiated from the LCD, independent of the LYNX application.
Do not show occupancy or override status: LCD does not show
occupancy or override, regardless of what the user initiates and the
LYNX application.
Back Moves to the Home Screen Options wizard window.
Next Moves to the Fan Command wizard window.
Finish Exits the wizard after saving the configuration changes.
Cancel Exits the wizard without saving the configuration changes.
Show wall module memory usage Shows current memory usage for the wall module. Memory updates
are made any time a change is made to the configuration.
The memory usage help message shows the distribution of memory
for each configured component graphically and in a tabular format.
If the memory usage exceeds the maximum limit, a message appears
indicating that the configuration must be modified in order to reduce
the memory usage before downloading the configuration.
Save to Library Saves the wall module configuration to the LYNX library.

NOTE: See Save Items to Library for more information about how to
save this configuration to the library.
PREVIEW AREA

Name Definition
Preview Area Displays the configured options. All valid occupancy states are shown
in the preview with the active one black and other states grayed out.

EN2Z-0960GE51 R0710 112

 CENTRALINE LYNX TOOL - USER GUIDE

Fan Command 3. Click Finish to save the settings or Cancel to revert to

Use this page to view Fan command settings. The Preview the last saved settings.
Area at the bottom of the screen displays the LCD fan
FIELDS
command options you have selected for the wall module.

PROCEDURE
1. Click the Fan Command button on the left pane to open
the Fan Command page.
2. Enter information into available fields.
Name Definition
Enable Fan Command Enables the fan command. Only if this option is checked will the Valid
Fan States options be enabled.
You have three valid fan states to choose from:
• 2 State
• 3 State
• 5 State
Default Fan State: You have the following fan state options:
• 2 State: On/Off. The default option is On.
• 3 State: On/Off/Auto. The default option is On.
• 5 State: Off/Auto/Low/Medium/High. The default option is Auto.
Show Advanced Settings Displays the Fan Status values. Defaults will follow the LONMark
standards. Valid fan status values are shown as enabled. Invalid
status values are disabled (depending on the fan status options
selected).
Fan Command Preview Displays the configured fan state options. All valid fan states appear
grayed out (unless configured) in the preview area, by default. Note
that the configuration you make is reflected in the preview area.
Example: If you select the Enable Fan Command option and choose
Default Fan State as On, the preview area shows a fan icon with On
highlighted. Auto the other Default Fan State is also displayed but is
grayed out indicated that it is not the selected option.
Back Moves to the Occupancy and Override wizard window.
Next Moves to the System Status and Command wizard window.
Finish Exits the wizard after saving the configuration changes.
Cancel Exits the wizard without saving the configuration changes.
Show wall module memory usage Shows current memory usage for the wall module. Memory updates
are made any time a change is made to the configuration.
The memory usage help message shows the distribution of memory
for each configured component graphically and in a tabular format.
If the memory usage exceeds the maximum limit, a message appears
indicating that the configuration must be modified in order to reduce
the memory usage before downloading the configuration.
Save to Library Saves the wall module configuration to the LYNX library.

NOTE: See Save Items to Library for more information about how to
save this configuration to the library.

113 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

System Status and Command PROCEDURE

Use this page to view System Status and Command settings. 1. Click the System Status and Command button on the
The Preview Area at the bottom of the screen displays the left pane to open the System Status and Command
LCD fan command options you have selected for the wall page.
module. 2. Enter information into available fields.
3. Click Finish to save the settings or Cancel to revert to
the last saved settings.

FIELDS

Name Definition
Show System Status Option to enable/disable displaying the system status.
Enable System Command Option to enable/disable tenant commanding the system.
You have five valid system commands options to choose from:
• Off / Heat
• Off / Cool
• Off / Heat / Cool
• Off / Auto / Heat / Cool
• Off / Auto / Heat / Cool / Emergency Heat
Default System Command: Set the default value for the system
command options:
• Off / Heat: Heat
• Off / Cool: Cool
• Off / Heat / Cool: Heat
• Off / Auto / Heat / Cool: Auto
• Off / Auto / Heat / Cool / Emergency Heat: Auto
Show Advanced Settings Displays the System Status Values and System Command Values.
System status values are enabled when Show system status
checkbox is enabled.
System command values are enabled only when enable system
command checkbox is enabled and depending on the valid system
commands selected, the respective values are enabled.
Invalid values are disabled (depending on the system configuration
options selected).
Defaults will follow the LONMark standards.
System Status and Command Preview Area Displays a preview of the LCD system status and command options.
If the Enable System Command option is checked, the SYSTEM soft
key label is shown in the preview area and the soft key button (the soft
key button on the extreme right) is activated. Press the soft key button
to cycle through the available system command options.
Back Moves to the Fan Command wizard window.
Next Moves to the Preview wizard window.
Finish Exits the wizard after saving the configuration changes.
Cancel Exits the wizard without saving the configuration changes.
Show wall module memory usage Shows current memory usage for the wall module. Memory updates
are made any time a change is made to the configuration.
The memory usage help message shows the distribution of memory
for each configured component graphically and in a tabular format.
If the memory usage exceeds the maximum limit, a message appears
indicating that the configuration must be modified in order to reduce
the memory usage before downloading the configuration.
Save to Library Saves the wall module configuration to the LYNX library.

NOTE: See Save Items to Library for more information about how to
save this configuration to the library.

EN2Z-0960GE51 R0710 114

 CENTRALINE LYNX TOOL - USER GUIDE

Preview 3. Click Finish to save the settings or Cancel to revert to

Use this page to preview the wall module configuration the last saved settings.
settings. 4. Click Back to display the System Status and Command
page.
PROCEDURE
FIELDS
1. Click the Preview button on the left pane to open the
Preview page.
2. Select the view you want to display.
Name Definition
Select View Displays the wall module configuration preview with options to view
the following:
• Tenant view: Displays wall module settings for tenant (normal
user)
• Contractor view: Displays wall module settings for contractors (A
unique button press sequence is used as a method of identifying a
user as a Contractor. This button press sequence is made available
only to Contractors.)
Use the soft keys to preview the configuration made. All valid settings
are shown based on the configuration at the point the Preview button
is pressed (including any defaults). For segments that are not
enabled, based on the configuration, the soft key button (located
directly beneath the segment) is not enabled.
Click Close to close the Preview window.

115 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

CONTROL FUNCTION BLOCKS

The CentraLine LYNXTool provides the following Control
function blocks that you can configure and use to build your
application logic:
• AIA
AIA
• Cycler This function is an Adaptive Integral Action controller (AIA). It
• Flow Control can be used in place of the PID. This control works better than
• PID PID when delays in the process being controlled cause
• Rate Limit integral windup resulting in undershoot or overshoot that
• Stage Driver leads to instability.

Err = Sensor – Set Point.

If Direct/Reverse is set to reverse, then Err term is set to –Err. Logic Inputs
Tr (throttling range) is Error value that results in an Output
change of the maximum value (MaxAOchange) from one step
to the next. MaxAOchange is the maximum amount(%) that Input Input Logic
Output will change for a single cycle of the control (1 sec). Name Value Value Description
This is typically set to 100%/(actuator speed (sec/full stroke)). disable unconnect 0 AIA function runs.
Deadband is the absolute value that Error must be greater ed
than before the output will change.
VAL != 0.0 1 Disable AIA function.
EffErr = Err – dead band
Output set to 0.
If Err > 0 , ErrSign = 1 else ErrSign = -1
0 0 AIA function runs.
If |Err| < dead band, then AbsErr = 0.
invalid 0 AIA function runs.
Otherwise( |Err |> dead band), AbsErr = |Err| - deadband
Output = output + ErrSign*[( maxAOchng – minAO)*(AbsErr/
(ThrottlingRange-Deadband))**3 + MinAO)]. Analog Inputs
From iteration to iteration, the Function Block keeps track of
the old proportional error. On power up/reset this is cleared.
Range
Input
Name Low High Input Value Description
sensor >=- <+ unconnected AIA function disabled.
infinit infinit Output set to 0.
y y
invalid Same as unconnected.
setPt >=- <+ unconnected AIA function disabled.
infinit infinit Output set to 0.
y y
invalid Same as unconnected.
Range

EN2Z-0960GE51 R0710 116

 CENTRALINE LYNX TOOL - USER GUIDE

Input VAL < low val = low

Name Low High Input Value Description minAO 0< <= unconnected MinAOchange = 0
tr 0 <+ unconnected AIA function disabled. Change maxA
infinit Output set to 0. Ocha
y nge
invalid Same as unconnected. invalid MinAOchange = 0
VAL <= 0 Same as unconnected. VAL < 0 MinAOchange = 0
maxAO 0< 100 unconnected MaxAOChange = 1.1 %/ VAL>=MaxA MinAOchange = 0
Change sec Ochange
(%/sec) invalid MaxAOChange = 1.1 %/
sec Output
0 MaxAOChange = 1.1 %/
sec
Output
VAL < low MaxAOChange = 1.1 %/ Name Range Description
sec
OUTPUT 0 to +100 Output = output +
VAL > high MaxAOChange = 1.1 %/ % ErrSign*NonLin(AbsErr,ThrottlingRan
sec ge,MaxAOchange,MinAOchange)
deadba 0 < tr unconnected disable Dead Band
nd action
Setpoint
invalid disable Dead Band
action
VAL < low DB = 0 Name Range/Value Description
OR VAL >+ revAct 0 = Direct acting User specified revAct value.
tr 1 = reverse
0 disable Dead Band acting
action
derivGa 0 <+ unconnected val = 0
in
invalid val = 0

117 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

Cycler maxSt 1 255 unconnec stgsAct = 0

This function is a generic stage driver or a Thermostat Stage gs ted
Cycler dependant on the value of the CPH parameter (cph=0 invalid maxStgs = 1
means stager functionality, and cph=1-60 gives thermostat
minOn 0 6553 unconnec stgsAct = 0
cycler functionality).
5 ted
(sec) invalid stgsAct = 0
minOff 0 6553 unconnec stgsAct = 0
5 ted
(sec) invalid stgsAct = 0
intstgO 0 6553 unconnec stgsAct = 0
n 5 ted
(sec) invalid stgsAct = 0
intstgO 0 6553 unconnec stgsAct = 0
ff 5 ted
(sec) invalid stgsAct = 0

Output
Logic Inputs
Output
Name Range Description
Input Input Logic
STAGES_ 0 to +100 The number of stages active (on)
Name Value Value Description
ACTIVE %
disable unconnect 0 Normal operation
ed
Setpoints
VAL != 0.0 1 Disable block, output = 0
0 0 Normal operation
invalid 0 Normal operation Range/
Name Value Description
override unconnect 0 Normal operation
Off ed anticipatorAuth 0 to 200% User specified value. Typical
ority value 100%
VAL != 0.0 1 Turns off stages as min on
time allows. cph 0 to 60 User specified value.
0 0 Normal operation hyst 0 to 100 User specified value.
invalid 0 Normal operation
Configuration
1. Specify CPH from 0 to 60.
Analog Inputs 2. Specify Anticipator Authority from 0 to 200%. Typical
value is 100%.
3. Specify hysteresis from 0 to 100.
Range
Input Input
Name Low High Value Description
in 0 100 unconnec stgsAct = 0
ted
(%) invalid in = 0%

EN2Z-0960GE51 R0710 118

 CENTRALINE LYNX TOOL - USER GUIDE

Cycler Functionality note that for multiple stage cyclers the PID block feeding this
block should have an appropriately large throttling range to
The Cycler function is the traditional anticipator cycling achieve smooth behavior.
algorithm used in CentraLine thermostats. Input is ether P or
PI space temperature error in% (0-100). Standard
(recommended) settings are cph=3 for cooling, cph = 6 for
heating, anticAuth = 100%, hyst = 100%/maxstages/2. Also

119 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

Stager Functionality From iteration to iteration, the Function Block keeps track of
the on timer, off timer, anticipator, and CPH multiplier. On
The Stager Function takes a 0-100 percent (typically PID power up/reset, the off timer and anticipator are cleared, the
error) input and determines how many stages to turn on. The on timer is set equal to the inter-stage on time and the CPH
0-100 percent input range is divided evenly between how multiplier is recalculated.
many stages are configured in MaxStages. The first stage is
turned on at CmdPercent > 0 and off at CmdPercent < - Hyst.
As shown in following illustration the general criterion for
turning on stage N is:
CmdPercent > (N -1)*100%/MaxStages.
For turning off stage N the criterion is:
CmdPercent < (N -1)*100%/MaxStages – Hyst.

When override is true, active stages are shed (turned off) • AnticAuth (cycler only (CPH != 0)) is the anticipator
based on min on and interstage timers regardless of the authority, which allows adjustment of the cycling behavior.
CmdPercent input. Output is number of stages active (0- It represents the max amount of “fake” error in % that is
MaxStages) which can be sent to the StageDriver function input into the switching logic when MaxStages are turned
block. Configuration parameters include: on. (Range 0 < AnticAuth < 200.)
• MaxStages is the maximum stages available to turn on. • MinOnTime is minimum time a stage must be on once it is
• CPH (non-zero) is max cycle rate in Cycles Per Hour when turned on.
input is halfway between stages available and AnticAuth is • MinOffTime is minimum time a stage must be off once it is
at default value (100%). CPH = 0 means the Stager logic is turned off.
performed and has no other effect. • InterstageOn is minimum time before the next stage can be
• Hyst is the switching differential around the switch points in turned on after the previous one is turned on.
% error. (Range: 0 < Hyst < 100/Maxstgs.) • InterstageOff is minimum time before the next stage can be
turned off after the previous one is turned off.

EN2Z-0960GE51 R0710 120

 CENTRALINE LYNX TOOL - USER GUIDE

Flow Control
This function is a Variable Air Volume (VAV) Damper Flow
Controller. Traditionally this is the second half of a pressure
independent VAV box cascade control strategy where typically
the input would come from the output of a PID block
controlling space temperature.

Analog Inputs

Range
Input Name Low High Input Value Description
cmdFlowPercent 0 <+ unconnected cmdFlowPercent= 0
(%)
invalid Same as unconnected.
sensedFlowVol >=- infinity <+ infinity unconnected damperPos = cmdFlowPercent
invalid damperPos = cmdFlowPercent
minFlowSetPt >=- infinity <+ infinity unconnected Switch to Pressure dependant mode.
minFlowSetPt = 20
maxFlowSetPt = 100
effFlowSetPt = invalid
invalid Same as unconnected
maxFlowSetPt >=- infinity <+ infinity unconnected Switch to Pressure dependant mode.
minFlowSetPt = 20
maxFlowSetPt = 100
effFlowSetPt = invalid
invalid Same as unconnected
manFlowOverride >=- infinity <+ infinity unconnected Normal operation
invalid Same as unconnected.
manFlowValue 0 <+ infinity unconnected value = invalid
invalid Same as unconnected.
ductArea >0 <+ infinity invalid effFlowSetPt = invalid & damperPos = (100*
minFlowSetPt/ maxFlowSetPt)
unconnected Same as invalid
VAL <= 0 Same as invalid

121 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

Output

Output Name Range Description

EFF_FLOW_SETPT Any floating point value Effective Flow setpoint
DAMPER_POS Any floating point value Damper position.

Setpoints

Name Range/Value Description

units 0 to 2 0 = flow (cfm), area(ft**2)
1 = flow (Lps), area (m**2)
2 = flow (cmh), area (m**2).
Default is zero (0).
motorSpeed 1 to 255 seconds per 90 Default is 90
degrees

Configuration The Units parameter sets the units being used for the flow
• Specify the units from 0 to 2. sensor, set points, and duct area where 0 = cfm (flow) and ft2
— 0 = flow (cfm), area(ft**2) (area), 1 = L/s(flow) and m2(area), 2 = m3/hr(flow) and
— 1 = flow (Lps), area (m**2) m2(area). The cmdFlowPercent input is the input in percent
— 2 = flow (cmh), area (m**2). from the temperature control logic. DuctArea is the duct area
• Specify the motor speed from 1 to 255 seconds per 90 in units per the Units parameter selection. DuctArea is
degrees. Default is 90. required for the control algorithm. The control loop is
The Flow Controller function calculates an effective flow implemented in air velocity in order to simplify loop tuning.
control set point (effFlowSetPt) and outputs a 0 -100 percent The motorSpeed parameter is the time the actuator being
command to drive a VAV box damper. The commanded flow used takes to travel a full 90 deg stroke in seconds (this is
set point (in percent) from a temperature control signal is used to automatically adjust the control gains). The
mapped into the effective flow set point such that 0 percent manFlowOverride input allows the flow set point to be
maps to the min flow set point and 100 percent maps to the selectively overridden based the following codes: (taken from
max flow set point. The sensedFlowVol input is the volumetric snvt_hvac_overid)
flow into the box, if it is invalid (sensor fails) the damper is — 0 and all others not listed = no override (normal opera-
driven in a pressure dependant mode where: tion)
Output = 100%*(minSP/maxSP)+ (1-minSP/ — 2 = effFlowSetPt is set to the ManFlowValue input
maxSP)*cmdPercent. — 6 = effFlowSetPt is set to the minFlowSetPt input
— 7 = effFlowSetPt is set to the maxFlowSetPt input
If either flow MinSP, MaxSP is invalid, the output = 20% + Manual flow override is particularly useful when trying to make
.8*cmdPercent. the box easy to be balanced.

EN2Z-0960GE51 R0710 122

 CENTRALINE LYNX TOOL - USER GUIDE

PID Logic Inputs

The PID controller compares a measured value from a
process with a reference setpoint value. The difference (or
error signal) is then used to calculate a new value for a Input Input Logic
manipulatable input to the process that brings the process' Name Value Value Description
measured value back to its desired setpoint. Unlike simpler disable unconnect 0 PID function runs.
control algorithms, the PID controller can adjust process ed
outputs based on the history and rate of change of the error
VAL != 0.0 1 PID function is disabled.
signal, which gives more accurate and stable control.
Output set to zero.
In a PID loop, correction is calculated from the error in three
ways: 0 0 PID function runs.
• Cancel out the current error directly (Proportional) invalid 0 PID function runs.
• The amount of time the error has continued uncorrected
(Integral)
• Anticipate the future error from the rate of change of the
error over time (Derivative)
— Err = Sensor – Set Point
— Kp = 100/Proportional Band Analog Inputs
— Ti = Integral Time (seconds) t
— Td = Derivative Time (sec)
— Bias = proportional offset (%) 
( Err )dt
— Output (%) =bias + Kp*Err + Kp/Ti 0 +
Kp*Td*dErr/dt
Range
Input Name Low High Input Value Description
sensor >=- infinity <+ infinity unconnected PID function disabled.
Output set to 0.
invalid
setPt >=- infinity <+ infinity unconnected PID function disabled.
Output set to 0.
invalid Same as unconnected.
tr 0< <+ infinity unconnected PID function disabled.
Output set to 0.
invalid Same as unconnected.
0 PID function disabled.
Output set to 0
VAL < low val = low
intgTime 0 <+ infinity unconnected PID function disabled.
Output set to 0.
(sec) invalid Disable Integral Action.
0 Disable Integral Action.
VAL < low IT = low
dervTime 0 <+ infinity unconnected Disable Derivative action.
(sec) invalid Disable Derivative action.
0 Disable Derivative action.
VAL < low DT = low
deadBand 0 < tr unconnected same as 0 input
invalid same as 0 input
VAL < low or VAL >= DB = 0
tr
0 disable Dead Band action
dbDelay 0 65565 dead band delay

123 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

(sec) unconnected same as 0 input

invalid same as 0 input
0 dead ban action enabled without delay
VAL < low DeadBandDelay = low

Output

Output Name Range Description

OUTPUT -200 to +200 % t

 ( Err )dt
0
Output (%) =bias + Kp*Err + Kp/Ti + Kp*Td*dErr/dt

Setpoints

Name Range Description

Action 0 = Direct acting User specified inputs
1 = reverse acting
bias 0 to 100% User specified inputs

Configuration When Err < Dead band, Err is set to zero until Dead band
1. Specify Action Delay time has elapsed and Err is still in the dead band.
• 0 = Direct acting To prevent integral wind up, the integral portion of the total
error output is limited to 100%.
• 1 = reverse acting
From iteration to iteration, the Function Block keeps track of
2. Specify the bias: 0 to 100%. the old proportional error, integral error, and dead band timer.
When Disable/Initialize input is TRUE, The Output and the On power up/reset these are cleared.
integral are set to 0 and the block stops running. If Direct/
Reverse is set to reverse, then Err term is set to –Err.

EN2Z-0960GE51 R0710 124

 CENTRALINE LYNX TOOL - USER GUIDE

Rate Limit
This function creates an output that follows the input but upRate 0< <+ unconnecte No limit on up rate
prevents the output from changing faster that the specified infinity d
rates depending on direction.
(chg/sec) invalid No limit on up rate
0 no limit on up rate
<0 upRate = 0 (no limit
on up rate)

downRat 0< <+ unconnecte no limit on down rate

e infinity d
(chg/sec) invalid no limit on down rate
0 no limit on down rate
<0 downRate=0 (no limit
on up rate)

Output
Logic Inputs
Output
Input Input Logic Name Range Description
Name Value Value Description
OUTPUT Any Rate limit
disable unconnecte 0 Function runs. floating
d point value
VAL != 0.0 1 Function disabled
0 0 Function runs. Operation
invalid 0 Function runs. The value StartInterval (sec) limits the output after the rate
limit function is enabled (disable input set to 0) and the
StartInteval time is still in process. Ratelimit uses the startVal
Analog Inputs input as the default output during disable.
If the rate limit function is disabled (disable input set to 1) the
output will be set to StartVal.
Range
After rateLimit is enabled (disable set to 0) the StartInterval
Input Input timer will count down from the StartInterval number of
Name Low High Value Description seconds and during this time the output will be rate limited.
in >=- <+ unconnecte In= 0.0 When the timer expires (and ratelimit is enabled) the out value
infinit infinity d will be exactly what the input (in) is set to and there will no
y longer be rate limiting.
invalid In = Invalid If the StartInterval seconds is set to 0 (and ratelimit is
Valid In = value enabled), then the output will be Ratelimited.
During Ratelimit the output will move at a maximum allowed
rate toward the new input value each second.
startInter 0 65535 unconnecte Startinterval = 0 UpRate controls the rate in a more positive direction, and
val d DownRate controls the rate in a more negative direction.
(sec) invalid Start interval = 0 UpRate set to zero means the uprate limit is not enforced.
0<val<max Limit Start interval DownRate set to zero means the downrate limit is not
float value 0 to 65535.0 enforced.
seconds Out is set to StartVal before rate limiting is enabled (disable
set to 0).
<0 StartInterval = 0
From iteration to iteration, the Function Block keeps track of
startVal >=- <+ Output assumes the the start timer. On power/up/reset, this is set to the
infinit infinity start value when the StartInterval.
y function is disabled.
unconnecte If disable=1, then
d Out=in Stager
invalid If disable=1, then This function is a generic stage driver or a Thermostat Stage
Out=in Cycler dependant on the value of the CPH parameter (cph=0
means stager functionality, and cph=1-60 gives thermostat
cycler functionality).

125 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

Logic Inputs (sec) invalid stgsAct = 0

minOff 0 6553 unconnec stgsAct = 0
5 ted
Input Input Logic
Name Value Value Description (sec) invalid stgsAct = 0
disable unconnect 0 Normal operation intstgO 0 6553 unconnec stgsAct = 0
ed n 5 ted
VAL != 0.0 1 Disable block, output = 0 (sec) invalid stgsAct = 0
0 0 Normal operation intstgO 0 6553 unconnec stgsAct = 0
ff 5 ted
invalid 0 Normal operation
(sec) invalid stgsAct = 0
override unconnect 0 Normal operation
Off ed
VAL != 0.0 1 Turns off stages as min on
Output
time allows.
0 0 Normal operation Output
invalid 0 Normal operation Name Range Description
STAGES_ 0 to +100 The number of stages active (on)
ACTIVE %
Analog Inputs
Setpoints
Range
Input Input
Name Low High Value Description Range/
Name Value Description
in 0 100 unconnec stgsAct = 0
ted hyst 0 to 100 User specified value.
(%) invalid in = 0%
maxSt 1 255 unconnec stgsAct = 0 Configuration
gs ted 1. Specify hysteresis from 0 to 100.
invalid maxStgs = 1
minOn 0 6553 unconnec stgsAct = 0
5 ted

EN2Z-0960GE51 R0710 126

 CENTRALINE LYNX TOOL - USER GUIDE

Cycler Functionality
The Cycler function is the traditional anticipator cycling
algorithm used in CentraLine thermostats. Input is ether P or
PI space temperature error in% (0-100). Standard
(recommended) settings are cph=3 for cooling, cph = 6 for
heating, anticAuth = 100%, hyst = 100%/maxstages/2. Also
note that for multiple stage cyclers the PID block feeding this
block should have an appropriately large throttling range to
achieve smooth behavior.

127 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

Stager Functionality From iteration to iteration, the Function Block keeps track of
the on timer, off timer, anticipator, and CPH multiplier. On
The Stager Function takes a 0-100 percent (typically PID power up/reset, the off timer and anticipator are cleared, the
error) input and determines how many stages to turn on. The on timer is set equal to the inter-stage on time and the CPH
0-100 percent input range is divided evenly between how multiplier is recalculated.
many stages are configured in MaxStages. The first stage is
turned on at CmdPercent > 0 and off at CmdPercent < - Hyst.
As shown in following illustration the general criterion for
turning on stage N is:
CmdPercent > (N -1)*100%/MaxStages.
For turning off stage N the criterion is:
CmdPercent < (N -1)*100%/MaxStages – Hyst.

When override is true, active stages are shed (turned off) • AnticAuth (cycler only (CPH != 0)) is the anticipator
based on min on and interstage timers regardless of the authority, which allows adjustment of the cycling behavior.
CmdPercent input. Output is number of stages active (0- It represents the max amount of “fake” error in % that is
MaxStages) which can be sent to the StageDriver function input into the switching logic when MaxStages are turned
block. Configuration parameters include: on. (Range 0 < AnticAuth < 200.)
• MaxStages is the maximum stages available to turn on. • MinOnTime is minimum time a stage must be on once it is
• CPH (non-zero) is max cycle rate in Cycles Per Hour when turned on.
input is halfway between stages available and AnticAuth is • MinOffTime is minimum time a stage must be off once it is
at default value (100%). CPH = 0 means the Stager logic is turned off.
performed and has no other effect. • InterstageOn is minimum time before the next stage can be
• Hyst is the switching differential around the switch points in turned on after the previous one is turned on.
% error. (Range: 0 < Hyst < 100/Maxstgs.) • InterstageOff is minimum time before the next stage can be
turned off after the previous one is turned off.

EN2Z-0960GE51 R0710 128

 CENTRALINE LYNX TOOL - USER GUIDE

Stage Driver nonvolatile memory to reference the starting runtime memory

index. stgStatusOut is the offset to digital stage status that is
The StageDriverMaster function takes input number of stages used by connected StageDriverAdd blocks.
active and determines which stages to energize or de
energize based on the lead/lag strategy chosen. Stage Driver As more stages are set up during design, the configuration
works with StageDriverAdd to distribute additional stages tool will calculate the starting address for both stage status
above those provided in Stage Driver. Stage Driver also and runtime and allocate the memory and calculate the offset
maintains a nonvolatile runtime total and digital stage status from the base index that is the starting address for the runtime
information for each stage. area and the stage status area in their respective memories.
The configuration tool will set a runtime and stage stages The stage status information is accessible to drive additional
offset in a single offsets variable. The offsets variable is not stages. The StageDriverAdd function blocks are use to drive
used as a Public Variable ID. The lower byte will store the stages above those provided in Stage Driver up to 255 stages.
offset in digital memory to reference the starting stage status
memory index, and the upper byte will store the offset in

Analog Inputs

Range
Input Name Low High Input Value Description
nStagesActive 0 255 unconnected Stages all off
invalid Stages all off
runtimeReset 0 255 Unconnected No action to reset; runtime can accumulate
Invalid No action; runtime can accumulate
Value=0 No action; runtime can accumulate
1<=VAL<=255 Stage runtime for stage VAL is reset to 0; runtime for this
stage will not accumulate—you must reset VAL to 0 to allow
accumulation of runtime.

Outputs

Range
Output Name Low High Description
Stage1 0 1 Stage 1 output
Stage2 0 1 Stage 2 output
Stage3 0 1 Stage 3 output

129 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

Stage4 0 1 Stage 4 output

Stage5 0 1 Stage 5 output
stgStatusOut Output value to connect to StageDriverAdd block. The floating number must be
converted to an integer and then converted to a 2 byte value. The upper byte (value
right shifted 8 bits) is the maxStgs info and the lower byte (value AND 0xFF) is the
stageStatus offset to reference the starting location in digital memory for the
stageStatus bytes.
offset Float value has two components – after conversion to a two byte unsigned integer
value the upper byte is offset of number of nonvolatile entries to get to the start of the
stage runtime storage (used only for leadLag=LL-RUNEQ) and the lower byte is the
offset of number of digital memory locations to the start of the stage status bytes (one
byte allocated per 8 stages assigned in maxStgs)

Configuration Offsets store the public Variable ID to a float a value created

Specify the maximum number of stages (maxStgs) from 1 to by the tool to allocate storage memory and reference for stage
255. status in digital memory and stage runtime in nonvolatile
memory. There are two offsets stored inside the float value,
Specify the lead lag (leadlag) one for runtime, and one for stage status. The offset float
• LL STD = 0 first on last off value right shifted 8 bits gives the number of nonvolatile float
• LL FOFO = 1 first on first off values from the beginning nonvolatile index (offset) where the
• LL RUNEQ = 2 runtime equalization for lowest runtime runtime values are stored (one runtime value offset for each
If the leadlag is outside of the range of 0 - 2 then stages are stage configured), and the offset ANDED with 0xff gives the
initialized to off and not commanded. number of digital values from the base where the stagestatus
is stored (one byte per up to 8 stages configured). Each digital
Inputs memory location takes up 1 byte storage in calculating the
offset.
nStagesActive is the input number of stages to be distributed
to on/off values to individual stages. Example
runtimeReset is the stage number runtime to be reset to 0 if If three nonvolatiles were already assigned and four digital
the lead-lag parameter is set to LL RUNTIME. 0 or outputs were already assigned before adding a stagedriver
unconnected results in no reset occurring. This value must be stage of nine stages with runtime accumulation, then the
returned to 0 to allow the reset stage number to resume offset float value would be 256(3) + 4 = 772.0.
counting. Only valid if leadLag is set to LL RUNTIME. The That means the tool would have 8 nonvolatile runtime
stage runtime values are only allocated and updated if the locations starting at offset 3 from the base of nonvolatile
leadLag config is set to LL RUNTIME. The runtime for each memory and the tool would allocate digital memory of two
stage is stored as a floating point number in intervals of 1 bytes for the stage status starting at offset of 4 from the base
minute. of digital memory. The tool sets this float value for offsets and
The stages are sampled once a minute and if the stage is on, allocates the memory, and then stagedriver uses this
then the stage runtime accumulator number for that stage is information to know where to look for stagestatus and stage
incremented by one minute. The range of values for an runtime information.
integer number stored as a float is from -16,777,216 to The Float value that stores Offsets is composed of two values
16,777,216. If the runtime is stored in minutes starting at 0 to • offsetStageRuntimer (byte)
16,777,216, then the range of runtime is from 0 to 31.92 years The float value converted to an integer and shifted 8 bits
of runtime. specifies the variable quantity offset to be applied to the
beginning of nonvolatile memory variable number that
Outputs indicates the starting variable number used to store the
Stage1, stage2, stage3, stage4, and stage5 are individual individual stage runtime values. This number is calculated by
outputs that represent on or off values. These are outputs that the configuration tool and is not changeable.
are turned on in different order depending on the leadLag • offsetStageStatus (byte)
strategy. The float value converted to an integer and ANDed with 0xFF
stgStatusOut is connected from StageDriver to the specifies the variable number offset to be applied to the
StageDriverAdd block and gives a floating point number beginning of digital memory area that indicates the starting
combined to hold two pieces of information, offset in the variable number used to store the individual stage on/off
Common Memory to the StageBitStatus values and maximum values. This number is calculated by the configuration tool
number of stages available. This information is used by the and is not changeable. This value is exported to other stages
StageDriverAdd to find the correct offset to command which through the stageBitStatus output.
stages to turn on or off. The floating value can be converted to
an integer and ANDed with 0xFF and will give the value of the Parameters
stageStatus Offset. The floating value stgStatusOut converted leadLag (Byte param:UBYTE) specifies whether the staging
to an integer and right shifted 8 bits will give the byte value of strategy should be:
the maxStages. These values are needed to allow the
StageDriverAdd to work properly. The values in stgStatusOut • First on last off (LL STD = 0 - standard)
are created by the StageDriver stage and no tool calculation is • First on first off (LL FOFO = 1 - Rotating)
required.

EN2Z-0960GE51 R0710 130

 CENTRALINE LYNX TOOL - USER GUIDE

• Run time accumulation where next on is lowest runtime For a final example, let us take the example of LL RUNTEQ
and next off has highest runtime (LL RUNTEQ = 2 - for a sequence. Each stage now has a runtime accumulation
Runtime Accumulation) in minutes. So let us assume that all 4 stages turn on for 12
Runtime Accumulation selection requires the tool to allocate minutes. Each stage for stage1, stage2, stage3, and stage 4 is
Nonvolatile memory and Set the Offsets value. on and accumulates 12 minutes of runtime. Now it is time to
Example turn off one stage so all the ON stages are evaluated for the
highest runtime and since they are all the same, the last stage
In a boiler control system configured for a maximum stages of that is on that is evaluated has the highest runtime so stage 4
4, LL STD will take the number of stages active and activate is turned off so stage 1 on stage2 on and stage3 = on. Now let
the stages in the following order, stage 1 on, then stage1 and us run the boilers for 2 more minutes. Now stage 1 has 14
stage 2 on, then stage 1 on stage2 on stage3 on, then stage 1 minutes runtime, stage 2 has 14 minutes runtime, stage 3 has
on stage2 on stage3 on and stage 4 on. When one stage is 14 minutes runtime, and stage 4 has 12 minutes runtime. Now
removed then it will be stage 1 on stage 2 on stage 3 on. If the number of stages requested drops to 2 stages so stage 3
one more stage is removed then it will be stage 1 on stage 2 is turned off and now stage 1 on, stage 2 on, stage 3 off, and
on. If one more stage is removed then stage 1 on, and finally if stage 4 off. So now the boilers are run for 2 more minutes.
one more stage is removed then there is only one stage on. The runtimes are now stage 1 on = 16 minutes, stage 2 on
And finally if one more stage is removed then no stages are =16 minutes, stage 3 = off =14 minutes, and stage 4 = off = 12
on. Stage 1 always comes on first and is always the last stage minutes. Now let us add one more stage so number of stages
to turn off. goes from 2 to 3. Now all the stages that are off are evaluated
If we take this same example and implement it as a LL FOFO for lowest runtime. Stage 4 has the lowest runtime of 12
which is rotating or First on first off, then the boiler keeps track minutes so now stage 4 is turned on.
of where the starting stage is from the last cycle. Say for maxStages (Byte param:UBYTE) specifies how many total
example there are no stages on and a stage is added. Then stages nStagesActive can reach. MaxStages can go up to a
adding one stage will turn on stage1. If another stage is total of 255 stages.
added, then stage1 is on and stage2 is on. If one more stage
is added then stage1 is on stage2 on and stage 3 is on. Now Note: Due to limitations of Niagara, only 95 stages can be
lets say that the number of stages goes from 3 to 2 so now it is seen on the wiresheet. To see, say stage number 200, do one
time to remove a stage. Because of LL FOFO, the first stage of the following:
we turned on is the first stage to turn off so stage 1 would go Select the stages (in this case, stage 200) you want to see by
off and only stage 2 and stage 3 would be on. Then if you right-clicking them in the Block Configuration table under
were to turn off one more stage then stage 2 would go off and Show Stages and select Show.
only stage 3 would be on. Now if you added one more stage, Invoke the link editor on the wire sheet. Select the Source
stage 4 would turn on in addition to stage 3. If One more stage and the Target (in this case, stage 200).
were added (numstages = 3) then stage 3 is on, stage 4 is on,
and now stage 1 turns on too.

131 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

DATA FUNCTION BLOCKS

The CentraLine LYNXTool provides the following Data High >=- <+ unconnec High Limit = invalid
Function function blocks that you can configure and use to Limit infinit infinit ted
build your application logic: y y
• Alarm invalid High Limit = invalid
• Counter
• Override Low >=- <+ unconnec Low Limit = invalid
• Run Time Accumulate Limit infinit infinit ted
y y
Alarm invalid Low Limit = invalid
This function creates an alarm based on the value of the input Preset 0 3276 unconnec Preset Time = 0
compared to the high and low limits. You may create up to 32 Time 7 ted
alarm function blocks that map to nvoError. From iteration to (sec) invalid Preset Time = 0
iteration, the function block keeps track of the alarm status
and delay timer. On power up/reset, these are cleared. It is Post 0 3276 unconnec Post Time = 0
NOT necessary to connect the output of this Function Block to Time 7 ted
the input of another for this function block to work. (This is (sec) invalid Post Time = 0
said because as a general rule if a Function Block’s output is
not connected, it has no value.) The Alarm Function Block is
different because it also sets/resets a bit in nvoError. Output

Output
Name Range Description
ALARM_STA False (0) / True Alarm status
TUS (1)

Operation
If the Value is greater than the High Limit or less than the Low
Limit continuously for the Preset Time, the Alarm Status is
TRUE. Once the alarm is set TRUE, it remains TRUE for at
least the Post Time. If at the end of the Post Time the Value is
Logic Inputs still outside of the limits, the alarm will remain. If the Value is
within the limits and the post time expires, the Alarm Status is
set to FALSE.
Input Input Logic
If the Value is Invalid (open, short, or not connected) or the
Name Value Value Description
Disable input is TRUE, the Alarm Status and timers are
Disabl unconnecte 0 Set Disable = False cleared.
e d
invalid 0 Set Disable = False NOTE: If a universal input is open or shorted, it generates an
alarm ID configured to do so. (By adjusting the UI
0 0 Disable is False limits, you can choose when a UI is open or shorted.)
VAL != 0.0 1 Disable is True
Alarms on Digital Values
Analog Inputs The Alarm function block can be used to alarm on digital
values by setting the high and low limits to zero (0.0). When
Value equals FALSE (0), Alarm status will be FALSE. When
Range Value is any other value, the Preset Time will start.
Input Input The Preset and Post Time values are limited to 0 to 32767
Name Low High Value Description seconds (9.1 hours).
When the Alarm Status is TRUE, the configured bit in nvoError
Value >=- <+ unconnec Value = invalid
is set. When the Alarm Status is FALSE, the configured bit in
infinit infinit ted
nvoError is reset.
y y
invalid Value = invalid

EN2Z-0960GE51 R0710 132

 CENTRALINE LYNX TOOL - USER GUIDE

Alarm State Value Timer Action Comment

False Outside < Preset Time Increment Timer. Insure alarm is valid for the preset time before
limits issuing the alarm.
False Outside >= Preset Time Set Alarm Status = TRUE; The preset time has been met, post alarm and
limits Clear Timer clear the timer so it can count the post time.
False Inside limits Don’t care Clear Timer Value is inside the limits and there is no prior
alarm, so clear the timer so it’s ready to count
the preset time when the value goes outside
[again].
True Outside < Post Time Increment Timer Insure that we post the alarm for at least Post
limits Time seconds regardless of what the value
does with respect to the limits.
True Outside >= Post Time Stop Timer The alarm has been issued for at least the
limits Post Time. The alarm is now allowed to return
to normal as soon as the value goes back
within the limits.
True Inside limits < Post Time Increment Timer Value has gone back inside the limits after
posting the alarm. Wait until the timer expires
before issuing the return to normal.
True Inside limits >= Post Time Clear Alarm Status; The alarm has been issued for at least the
Clear Timer Post Time. Clear the alarm because the
conditions are no longer present.

View Alarms • Invalid ConfigurationAlarms: This alarm will occur if

To view the alarms that are generated, right click there is an error in the configuration that was downloaded.
LonCentraLine in the Nav palette and select Views > • Network Communication Alarms: These alarms will
Alarms View. occur ONLY for Network variable inputs (NVIs) configured
as fail detect. The network variable names will be listed in
The Alarms View is displayed. this category.
There are 4 categories of alarms: • Control Alarms: All the alarm blocks configured in the
• Sensor Alarms: These alarms are generated for all the logic will be listed in this category. If an alarm block does
Sensors configured in the logic. All input blocks assigned not have any incoming link then the status will always be
to pins UI0 to UI7 will be listed in this category. NORMAL.

133 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

Counter VAL != 0.0 1 Set Preset = True

This function counts leading edge transitions of the input. If StopAt unconnecte 0 Set Stop At Zero = False.
enable is True and the input transitions from False to True, Zero d Default value is False.
then the count is incremented or decremented by the count
invalid 0 Set Stop At Zero = False.
value. Positive values on count value increment the count.
Negative values decrement the count. If preset is True, the 0 0 Stop At Zero is False. Count is
count is set to the Preset Value. From iteration to iteration, the unaffected by a zero value.
Function Block keeps track of the previous state of the input VAL != 0.0 1 Stop At Zero is True. Stops
so that it can detect a transition. On power up/reset, this is counting at zero if counting
cleared. down from a positive count or
up from a negative count.

Analog Inputs

Range
Input Input
Name Low High Value Description
Count >=- <+ unconne Set Count Value = 1.0
Value infinit infinit cted Default value = 1.0
y y
Invalid Set Count Value = 1.0
VAL < Set Count Value = 1.0
low
VAL > Set Count Value = 1.0
Logic Inputs high
Preset >=- <+ unconne Set Preset Value = 0.0
Value infinit infinit cted
Input Input Logic y y
Name Value Value Description
Invalid Set Preset Value = 0.0
Input unconnecte 0 Set Input = False
d VAL < Set Preset Value = 0.0
low
invalid 0 Set Input = False
VAL> Set Preset Value = 0.0
0 0 Input is False high
VAL != 0.0 1 Input is True
Enable unconnecte 1 Set Enable = True Output
d
invalid 1 Set Enable = True
Output Name Range Description
0 0 Set Enable = False
COUNT Any floating point Counter value
VAL != 0.0 1 Set Enable = True number
Preset unconnecte 0 Set Preset = False
d
invalid 0 Set Preset = False
0 0 Set Preset = False

EN2Z-0960GE51 R0710 134

 CENTRALINE LYNX TOOL - USER GUIDE

Transition versus time with positive and negative count

values

135 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

Override priority1V >=- <+ Unconnec Output = highest priority

This function sets the output to the highest priority input that is alue infini infini ted or input (priority1Val is top
not invalid. The Priority1 value has the highest priority and through ty ty invalid priority and cntrlInput is
cntrlInput the Lowest priority. This function block checks if the priority6V lowest priority) that is not
Inputs are not invalid in the following order: alue invalid or unconnected. If
no inputs are valid, then
1. Priority 1 Value use defaultValue
2. Priority 2 Value
3. Priority 3 Value cntrlInput >=- <+ Unconnec Output = highest priority
4. Priority 4 Value infini infini ted or input (priority1Val is top
5. Priority 5 Value ty ty invalid priority and cntrlInput is
6. Priority 6 Value lowest priority) that is not
7. Ctrl Input invalid or unconnected. If
The first value that is not invalid in the order of priority is set as no inputs are valid, then
the output. If all inputs are invalid or unconnected, the output use defaultValue
is set to the defaultValue. defaultVa >=- <+ unconnec defaultValue = invalid
This function block corresponds to the BACnet priority array lue infini infini ted
implementation with the replacement of the BACnet NULL ty ty
state with invalid. invalid defaultValue = invalid

Output

Range
Output
Name Low High Description
EFF_O >=- <+ effOutput = highest priority input that is
UTPU infinit infinit not invalid.
T y y
Example
Analog Inputs Set the Inputs to the following:
• Priority 1 Value = Invalid
• Priority 2 Value = Invalid
Range • Priority 3 Value = 50
Input Hig Input • Priority 4 Value = 60
Name Low h Value Description • Priority 5 Value = -20
• Priority 6 Value = 80
• Ctrl Input = 30
The output is set as 50. Priority 1 and Priority 2 values are
invalid. The next highest priority value (Priority 3 value = 50) is
set as the output.
An invalid input to this function block could arise when you
connect the output of the Minimum function block whose input
is invalid.

EN2Z-0960GE51 R0710 136

 CENTRALINE LYNX TOOL - USER GUIDE

Priority Override Output

The PriorityOverride block supports driving the outputs based Range
on the priority of the connected application components.
There can be different control program logic components Output
driving the outputs at different priority levels. This block Name Low High Description
decides the priority level at which the output must be driven. Priority >=- <+ PriotityOut = value of the highest
This block supports up to 16 priority levels that can be Out infinit infinit priority input.
connected to different application components. y y
The Priority1 value has the highest priority and Priority 16 the
lowest priority. The block provides an output called Example
PriorityOut. The value of the highest priority is set as the
output PriorityOut. The PriorityOut slot of the PriorityOverride Set the Inputs to the following:
block can be linked only to a modulating/binary output. 1. Priority 1 = Unconnected
The block can be used in both LON and BACnet applications. 2. Priority 2 = Invalid
This block provides the PriorityArray mechanism in case of 3. Priority 3 = 50
BACnet objects. This block details do not get downloaded to 4. Priority 4 = 60
the controller in case of BACnet. In case of LON, the 5. Priority 5 = -20
PriorityArray mechanism is internally achieved using Override 6. Priority 6 = 80
blocks. The information of the override blocks get downloaded 7. Priority 7 = 30
to the LON controller. Hence there would be a difference in 8. Priority 8 =Unconnected
function block count between BACnet and LON application 9. Priority 9 =Unconnected
when this block is used. 10. Priority 10 =Unconnected
During upload the PriorityOverride block is depicted as part of 11. Priority 11 =Unconnected
the ControlProgram, depending on the number of application 12. Priority 12 =Unconnected
components driving the outputs. If there is only one 13. Priority 13 =Unconnected
application components driving the output, the 14. Priority 14 =Invalid
ControlProgram wiresheet would show a direct link from that 15. Priority 15 =40
application component to the output. If there are more than 16. Priority 16 =10
one application component driving the output, the The output is set as invalid as Priority 2 is invalid. The highest
PriorityOverride block would be depicted in the logic with priority value is set as the output.
outputs being driven at different priority levels. The properties of the Priority Override function block are listed
in the following table.
Analog Inputs

Range
Input Hig Input
Name Low h Value Description
priority1V >=- <+ Unconnec Output = value of the
alue infini infini ted or highest priority input
through ty ty invalid (priority1 is top priority and
priority16 priority16 is lowest priority).
If no inputs are valid, then
the output is also invalid.

S.No. Description LON BACnet‘

1 The input to the priority slot of the Priority Override function block can be a Applicable Applicable
physical point, a software point, or function blocks but cannot be a constant.
2 The PriorityOut slot can be connected to only one physical point which can Applicable Applicable
be modulating output or binary output.
3 The memory increment depends on the type of input block. Applicable Applicable
4 The FB count in the Resource Usage View is only incremented when the Applicable Not Applicable
Priority Override block contains a Valid Link and a Valid Knob.
5 If there are valid links from priority levels 1 to 8, FB count is incremented by Applicable Not Applicable
1.
6 If there are valid links from priority levels 9 to 15, FB count is incremented by Applicable Not Applicable
2.
7 If there are valid links greater than priority level 15, FB count is incremented Applicable Not Applicable
by 3.
8 The FB count in the Resource Usage View is not incremented. Not Applicable Applicable

137 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

Runtime Accumulate VAL != 0.0 1 Enable is True

This function accumulates runtime whenever the input is True Preset unconnect 0 Set Preset = False
(non zero) and enable is True. If Preset is True, runtime is set ed
equal to the Preset Value. Runtime is provided in four outputs
invalid 0 Set Preset = False
of seconds, minutes, hours, and days. From iteration to
iteration, the Function Block keeps track of the run time 0 0 Preset is False
seconds. On power up/reset, this is cleared. VAL != 0.0 1 Preset is True
NOTE: On power up/reset, only the Runtime Sec output is
set to zero. The other three outputs, Runtime Min, Analog Inputs
Runtime Hrs, Runtime Days are stored and not lost.

Range
Input Input
Name Low High Value Description
Preset 0 <+8 unconne Set Preset Value = 0.0 (in
Value cted minutes)
invalid Set Preset Value = 0.0
VAL < Set Preset Value = 0.0
low
VAL > Set Preset Value = 0.0
high

Output

Logic Inputs Output

Name Range Description
RUNTIME_M Any floating point Runtime Min
Input Input Logic
IN number >= 0
Name Value Value Description
RUNTIME_S Any floating point Runtime Sec
Input unconnect 0 Set Input = False
EC number >= 0
ed
RUNTIME_H Any floating point Runtime Hrs
invalid 0 Set Input = False
RS number >= 0
0 0 Input is False
RUNTIME_D Any floating point Runtime Days
VAL != 0.0 1 Input is True AYS number >= 0
Enable unconnect 1 Set Enable = True
ed
invalid 1 Set Enable = True
0 0 Enable is False

EN2Z-0960GE51 R0710 138

 CENTRALINE LYNX TOOL - USER GUIDE

Operation

Run time is always accumulated internally in minutes. It is Runtime Min is effectively limited to 16, 277,216 minutes (31
reported in 4 different units of seconds, minutes, hours and years).
days. Run time Min is saved over a power outage and reset. If Example
a power outage or reset occurs, the controller could lose up to
one minute of runtime. Runtime Sec, Runtime Hrs, and Connect an output from another block to the Input. Connect a
Runtime Days are calculated every iteration from the Runtime digital input to Preset. Set the Preset Value to 123. Set the
Min. Preset Value to 255 (TRUE).
Runtime Hrs and days outputs are fractional units to the The four outputs are as follows:
nearest minute. Runtime sec is runtime Min multiplied by 60. • Runtime Min = 123
You must use the preset input to set the runtime to an initial • Runtime Secs = 7380
value in minutes. • Runtime Hrs = 2.05
Runtime Accumulate is run every second. The state of input, • Runtime Days = 0.085416
enable, and preset are examined by the Function Block when
it is run. Momentary transitions of the inputs between
invocations of the Function Block will not be detected. If the
runtime reaches 16,277,216 minutes, it will stop.

139 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

LOGIC FUNCTION BLOCKS

The CentraLine LYNXTool provides the following Logic Analog Inputs
function blocks that you can configure and use to build your
application logic:
• AND Range
• One Shot Input Lo
• OR Name w High Input Value Description
• XOR
Inputs to Logic Function Block may come from either Digital or trueDela 0 3276 unconnected val = 0
Floating point variables. y 7 It is the minimum time
the computed output
For digital inputs
must stay True before
• 0 = FALSE the output actually
• 1-255 = TRUE changes from False to
For floating point variables True.
• 0.0 = FALSE (sec) invalid val = 0
• any nonzero number = TRUE
An output sent to a Digital variable will be 0 or 1. Similarly, an falseDel 0 3276 unconnected val = 0
output sent to a float point variable will be 0.0 or 1.0. ay 7 It is the minimum time
the computed output
must stay False before
AND the output actually
AND output becomes TRUE if all inputs are TRUE. This changes from True to
function is a six-input AND Function Block. Each input may be False.
individually inverted (NOT). (sec) invalid val = 0
Unconnected or invalid inputs default to True, without
negation, so as to have no effect on the result.
Output
From iteration to iteration, the function block keeps track of the
last computed output value and the current true or false delay
time. These values are cleared on power up/reset. Output
Name Range Description
OUTPUT Any floating point Output = AND/NAND
value (inputs).
Negating the Output makes
the AND function block
behave like a NAND function
block.

Example
1. Set In1- In6 = 1, and True delay = 2, and False delay =
6.
In this case, the output is set to 1 after a time delay of 2
Logic Inputs seconds as specified by the True delay.
2. Set In1 = 0, In2 - In6 = 1, and True delay = 2, and False
delay = 6.
Input Input Logic In this case, the output is set to 0 after a time delay of 6
Name Value Value Description seconds as specified by the False delay.
in1-6 VAL != 0.0 1
0 0
unconnec 1 Inputs with a "not" interpreted
ted as logic 1 when
disconnected.
invalid 1 Negin does not affect the
invalid logic value.

EN2Z-0960GE51 R0710 140

 CENTRALINE LYNX TOOL - USER GUIDE

Oneshot Logic Inputs

In the Oneshot function block, when x transitions from False
to True, y is set to True for OnTime seconds.
Input Input Logic
OnTime is limited to the range 0 to 65535 seconds. An Name Value Value Description
OnTime of zero keeps the output OFF no matter what
changes occur at the x input. x unconnect N/A For an invalid input make
ed output be OFF (ON if
Both the x input and y outputs have an option to be negated.
output is negated). Clear
From iteration to iteration, the Function Block keeps track of
the timer
the last input and the on time. On power up/reset, these are
cleared. VAL != 0.0 1
0 0
invalid N/A Must go from FALSE to
TRUE (or TRUE to FALSE
(Negated))

Analog Inputs

Range
Input Input
Name Low High Value Description
onTime 0 6553 unconnect onTime =0
5 ed
(sec) invalid onTime =0
<0 0
> 65535 65535

Output

Output
Name Range Description
Y Any floating When x transitions from FALSE to
point value TRUE, y will be set to TRUE (1) for
onTime seconds

141 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

Example
The Input is a square wave of 2 second amplitude. The time
transition diagram of the Output for different ontimes of 1 and
5 seconds is illustrated.

EN2Z-0960GE51 R0710 142

 CENTRALINE LYNX TOOL - USER GUIDE

OR Analog Inputs
The OR output becomes TRUE if at least one input is TRUE.
This function is a six input OR. Each input may be individually
inverted (NOT). Range
Unconnected or invalid inputs default to True, without Input Lo Input
negation, so as to have no effect on the result. Name w High Value Description
From iteration to iteration, the function block keeps track of the trueDela 0 3276 unconnect val = 0
last computed output value and the current true or false delay y 7 ed
time. These values are cleared on power up/reset. (sec) invalid val = 0
falseDel 0 3276 unconnect val = 0
ay 7 ed
(sec) invalid val = 0

Output

Output
Name Range Description
Logic Inputs
OUTPUT Any floating point Output = OR/NOR (inputs).
value Negating the Output makes
Input Input Logic the OR function block behave
Name Value Value Description like a NOR function block.
in1-6 VAL! = 0.0 1
0 0
unconnec 0 Inputs with a not interpreted
ted as logic 0 when disconnected.
invalid 0 Negin does not affect the
invalid logic value

143 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

XOR Analog Inputs

XOR output becomes TRUE if exactly one input is TRUE. This
function is a six input XOR. Each input may be individually
inverted (NOT). Range
Unconnected or invalid inputs default to True, without Input Lo Hig Input
negation, so as to have no effect on the result. Name w h Value Description
From iteration to iteration, the function block keeps track of the trueDela 0 327 unconnect val = 0
last computed output value and the current true or false delay y 67 ed
time. These values are cleared on power up/reset. (sec) invalid val = 0
falseDel 0 327 unconnect val = 0
ay 67 ed
(sec) invalid val = 0

Output

Output
Logic Inputs Name Range Description
OUTPUT Any floating point Output = XOR/XNOR
value (inputs).
Input Input Logic Negating the Output makes
Name Value Value Description the XOR function block
behave like a XNOR
in1-6 VAL != 1
function block.
0.0
0 0
unconne 0 Inputs with a not interpreted
cted as logic 0 when disconnected.
invalid 0 Negin does not affect the
invalid logic value

EN2Z-0960GE51 R0710 144

 CENTRALINE LYNX TOOL - USER GUIDE

MATH FUNCTION BLOCKS

The CentraLine LYNXTool provides the following Math
function blocks that you can configure and use to build you
application logic:
• Add
• Digital Filter
• Divide
• Enthalpy
• Exponential
• Flow Velocity
• Limit
• Multiply
• Ratio
• Reset
• Square Root
• Subtract

Add Inputs
Math functions operate on and produce single precision
floating point numbers. In the absence of any other
restrictions, if the result overflows the range of a single Range
precision floating point number (approx minus 3.4e38 to plus
3.4e38) the result returned is invalid. Input Input
Name Low High Value Description
NOTE: You can connect both Analog and Digital inputs as x1-x8 >=- <+ Unconne Not used in calculation
inputs to this function block. infinit infinit cted If all inputs are
y y unconnected, output is zero.
Ignore invalid inputs: Select this option if you want the
Invalid If any input is invalid, output
function block to ignore any invalid inputs, if any, and consider
is invalid
only the valid inputs to calculate the output. If this option is left
unselected, the invalid inputs will make the output also as
invalid. Output

Outpu
t
Name Range Description
Y Any floating Output is the sum of inputs x1 through
point value x8.

145 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

Digital Filter NOTE: You can connect both Analog and Digital inputs as
inputs to this function block.
This function digitally filters the input.
Ynew = Yold + (X -Yold)*(1-exp(-t/Tau)) Example 1:
Where, t = 1 second and Tau is in the range 0 to 65535 Set In1 (X) = 4, tau = 2.0, Set ZeroInit = 1 (initializes filter to
seconds. 0.0)
The output can be initialized to zero (zeroInit=TRUE) or the Ynew = Yold +(X -Yold)*(1-exp(-t/Tau))
first valid input value (zeroInit=FALSE). In the first iteration,
From iteration to iteration, the Function Block keeps track of Yold = 0; Ynew = Yold + ( X - Yold) * (1 – exp (-t/tau))
the tau multiplier (1-exp(-t/Tau). On power up/reset, this is
recalculated. Ynew = 0 + (4 - 0) * (1 – 2.718(-1/2))
Ynew = 0 + 4 * (0.393)
Ynew = 1.572
In the second iteration,
Yold = 1.572; X = 4; Ynew = 1.57 + (4 – 1.57) * (0.393)
Ynew = 2.52
In the third iteration,
Ynew = 2.52 + (4 – 2.52) * (0.393)
Ynew = 3.107
The iterations continue until the input is reached.
Example 2:
Set In1 (X) = 4, tau = 2.0, Set ZeroInit = 0 (initializes filter to
first valid value)
Ynew = Yold + (X -Yold) * (1-exp(-t/Tau))
Inputs In the first iteration,
Ynew = X
Range Ynew = 4
Input Input In the second iteration, if X = 6
Name Low High Value Description Ynew = Yold + ( X - Yold) * (1 – exp (-t/tau))
x >=- <+ Unconne Output is invalid. Ynew = 4 + (6 - 4) * (0.393)
infinit infinit cted Ynew = 4 + 0.786
y y
Ynew = 4.786
Invalid Output is set to invalid and
In the third iteration, if X = 6
filter reinitializes when the
input returns to valid. Ynew = Yold + ( X - Yold) * (1 – exp (-t/tau))
Ynew = 4.786 + (6 – 4.786) * (0.393)
Output Ynew = 5.263
The iterations continue until the input is reached.

Outpu
t Divide
Name Range Description This function divides one input by the other. Y = x1 / x2.
Division by 0 results in an invalid output. If the result overflows
Y Any floating Ynew = Yold +(X -Yold)*(1-exp(-t/Tau)).
the range of a single precision floating point number
point value
(approximately minus 3.4e38 to plus 3.4e38) the result
returned is invalid.
Setpoint
NOTE: You can connect both Analog and Digital inputs as
inputs to this function block.
Name Range/Value Description
tau 0 – 65535 seconds Configuration parameter.
zeroIni 0 Initializes filter value to first
t 1 valid value
Initializes filter value to 0.0

EN2Z-0960GE51 R0710 146

 CENTRALINE LYNX TOOL - USER GUIDE

invalid output set to invalid

x2 >=- <+ unconnecte output set to invalid
infinit infinit d
y y
0 output set to invalid
invalid output set to invalid

Output

Outpu
t
Name Range Description
Y Any floating Y= x1 / x2
point value
Analog Inputs

Range
Input Input
Name Low High Value Description
x1 >=- <+ unconnecte x1=0
infinit infinit d
y y

147 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

Enthalpy VAL < T = low

This function computes the enthalpy (BTU/LB) based on the low
temperature (Deg.F) and relative humidity (percent) inputs. VAL > T = high
Relative humidity (rh) is limited to 0 to 100 percent. high
Temperature is limited to 0-120 Deg.F.
rth 0 100 unconne output = invalid
cted
(%) invalid output = invalid
VAL < RH = low
low
VAL > RH = high
high

Output

Outpu
t
Name Range Description
Y Any floating Output = Enthalpy (t, rh)
point value
Analog Inputs

Range
Input Input
Name Low High Value Description
t 0 120 unconne output = invalid
Deg. Deg. cted
F F
(F) invalid output = invalid

EN2Z-0960GE51 R0710 148

 CENTRALINE LYNX TOOL - USER GUIDE

Exponential
This function raises y to the power of x. x and y are floating
point numbers. The application designer is limited to two of
these function blocks per device. Unconnected inputs are
treated as 0. Invalid inputs result in an invalid output. The
negInvalid input determines whether the operation should
proceed with a negative base and non-integer exponent,
operating on the absolute value of the base, or return invalid.
The negInvalid input does not affect an unconnected or invalid
input. If both the X and y inputs are disconnected, then the
output z, is 1.

Analog Inputs

Range
Input Name Low High Input Value Description
x >=- infinity <+ infinity base number
unconnected output = 1 if y=0;
output = 0 if y is non-zero.
invalid output set to invalid
y >=- infinity <+ infinity exponent
unconnected output = 1
invalid output set to invalid
negInvalid 0 1 Configuration option for the condition of x^y when the
exponent (y) is a non-integer and the base number (x) is
negative.
enumeration:
0 – use the absolute value of x
1 – output is set to invalid
Default value = 1
unconnected val = 0
invalid val = 0

Output

Output Name Range Description

Z Any floating point value Z = x power y

149 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

Flow Velocity • Area = duct area in ft^2.

This function computes the flow and velocity based on the
measured pressure and the K factor.

and
Vel = flow/area
Where:
• K=Flow coefficient (K-Factor) representing the actual flow
in ft^3/min corresponding to a velocity pressure sensor
output of 1 w.g.
• DeltaP=flow sensor output pressure in inches water gauge
(inW). Analog Inputs
• Offset=a correction pressure (inW) to adjust for zero.
• Flow=airflow in ft^3/min (CFM)
• vel=flow velocity in ft/min
Range
Input Name Low High Input Value Description
press >=- infinity <+ infinity unconnected Output set to invalid
invalid output set to invalid
>-0.002425 and Flow and vel=0
<0.002425 inw
autoSetOffset >=- infinity <+ infinity Unconnected no effect on output
Invalid No effect on output
!=0 Set offset=incoming press
clearOffset >=- infinity <+ infinity unconnected or No effect on output
invalid
!=0 Set offset=0
area >=- infinity <+ infinity Invalid or <=0; value Velocity set to invalid
in ft^2
kFactor >=- infinity <+ infinity unconnected output set to invalid
invalid output set to invalid
<=0 kFactor=1015

Output

Range
Output Name Low High Description
FLOW >=- <+ Flow value (ft^3/min)
OFFSET >=- <+ Input press offset correction (inches water column). Not for connection. Stores Flow
offset amount
VEL >=- <+ Flow velocity (ft/min)

EN2Z-0960GE51 R0710 150

 CENTRALINE LYNX TOOL - USER GUIDE

Limit x<loLimit Output set to loLimit

This function limits the input to the low and high limits. loLimit>h Limits not enforced (not
If the value of input (x) is: iLimit enforced means Y is
always set to X.)
• Lower than the loLimit, value of output is set to loLimit
• Higher than the highLimit, output is set to highLimit loLimit<x Output set to x
• Between the loLimit and highLimits, output is set to input <hiLimit
x>hiLimit Output set to hiLimit
hiLimit >=- <+ unconne hiLimit not enforced
infinity infinity cted
invalid hiLimit not enforced
loLimit >=- <+ unconne loLimit not enforced
infinity infinity cted
invalid loLimit not enforced

Output

Outpu
t
Analog Inputs Name Range Description
Y Any floating Y = Limit (x, low limit, hi limit)
point value
Range
Input Input
Name Low High Value Description
x >=- <+ unconne output set to invalid
infinity infinity cted
invalid output set to invalid

151 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

Multiply
This function multiplies one input with the other. y = x1
multiplied by x2. If the result overflows the range of a single
precision floating point number (approximately minus 3.4e38
to plus 3.4e38), the result returned is invalid.

NOTE: You can connect both Analog and Digital inputs as

inputs to this function block.

Ignore invalid inputs: Select this option if you want the

function block to ignore any invalid inputs, if any, and consider
only the valid inputs to calculate the output. If this option is left
unselected, the invalid inputs will make the output also as
invalid.

Analog Inputs

Range
Input Input
Name Low High Value Description
x1, x2 >=- <+ unconnec Unconnected inputs are set
infinit infinit ted to 0
y y If all inputs unconnected,
output is set to zero
invalid If any input is invalid then
output is invalid

Output

Output
Name Range Description
Y Any floating Y= x1 * x2
point value

EN2Z-0960GE51 R0710 152

 CENTRALINE LYNX TOOL - USER GUIDE

Ratio x1-2 >=- <+ unconne output set to invalid

This function converts the input X to the output Y based on the infinity infinity cted
line defined by x1, y1, x2, and y2. invalid output set to invalid
Output (Y) = y1 + (((x - x1) * (y2 - y1)) / (x2 - x1)) x1=x2 output set to y1
y1-2 >=- <+ unconne output set to invalid
infinity infinity cted
invalid output set to invalid

Output

Outpu
t
Name Range Description
OUTP Any floating Out Ratio(X, X1,Y1, X2,Y2)
UT point value

Setpoints

Output
Analog Inputs Name Range/Value Description
operatio • Unlimited
n • Vav_Flow_Bal
Range ance
Input Input • Endpoint_Limit
Name Low High Value Description ed
x >=- <+ unconne output set to invalid
infinity infinity cted
invalid output set to invalid

153 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

Unlimited
The Output is based on the line defined by x1, x2, y1, y2. The
behavior of the function block is as illustrated.
Y = y1 + (((x - x1) * (y2 - y1)) / (x2 - x1))

Endpoint Limited
The Output is based on the line defined by x1, x2, y1, y2. The
slope of the line is as shown in the illustration below. Beyond
points x1 and x2, the output is limited to the points y1 and y2
respectively. The Output is held between the points y1 and y2.
VAV Flow Balance
The Output is based on the line defined by x1, x2, y1, y2. The
slope of the line is as shown in the illustration below.
When x >= x1
Y = y1 + (((y2 – y1) (x2 – x1)) / (x2 – x1))
When x < x1
Y=x

When x1 < x < x2

Y = y1 + (((y2 – y1) (x2 – x1)) / (x2 – x1))
When x >= x1
Y = y2
When x <= x1
Y = y1

EN2Z-0960GE51 R0710 154

 CENTRALINE LYNX TOOL - USER GUIDE

Reset
This function computes the reset value based on the relation
of the input to the reset parameters.

Analog Inputs

Range
Input Name Low High Input Value Description
input >=- infinity <+ infinity unconnected output set to invalid
invalid output set to invalid
sensor >=- infinity <+ infinity unconnected output set to invalid
invalid output = input
zeroPctResetVal >=- infinity <+ infinity unconnected output set to invalid
invalid output = input
0%RV = 100%RV output set to input
hundredPctResetVal >=- infinity <+ infinity unconnected output set to invalid
invalid output = input
0%RV = 100%RV output set to input
resetAmount >=- infinity <+ infinity unconnected output set to invalid
invalid output = input

Output

Output Name Range Description

OUTPUT Any floating point value Y = Reset (input, sensor, 0%, 100%, reset amount)

155 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

Working

If Input Condition is Output

• input is unconnected Output = invalid
• input is invalid
• sensor is unconnected
• zeroPctResetVal is unconnected
• hundredPctResetVal is unconnected
• resetAmount is unconnected
• sensor is invalid Output = input
• sensor < zeroPctResetVal
• zeroPctResetVal is invalid
• hundredPctResetVal is invalid
• resetAmount is invalid
• hundredPctResetVal = zeroPctResetVal
• Sensor > hundredPctResetVal Output = input + resetAmount
• If none of the above conditions are satisfied Output = input + ((sensor – zeroPctResetVal)/
(hundredPctResetVal - zeroPctResetVal))*resetAmount

EN2Z-0960GE51 R0710 156

 CENTRALINE LYNX TOOL - USER GUIDE

Square Root x1 < 0 See negInvalid description

This function takes the square root of the input. The Output Y negInva 0 1 0 Use the square root of the
is the Sqrt (X), where X is the input. The behavior of a lid 1 absolute value.
negative X input is controlled by the parameter negInvalid. If the input is negative the
output is invalid.
NOTE: Negative values are treated as absolute values. The default value is 0.
Example: Square root of -9801 is given as 99, taking
unconne Y = sqrt(X), output is invalid
the absolute value of -9801 as 9801.
cted for neg x1
invalid Y = sqrt(X), output is invalid
for neg x1

Output

Output
Name Range Description
Y Any floating point Y= Sqrt (X)
value

Analog Inputs

Range
Input Input
Name Low High Value Description
x >=- <+ unconne Y= 0
infini infini cted
ty ty
invalid output set to invalid

157 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

Subtract
This function subtracts one input from the other. Y = x1 – x2. If
the result overflows the range of a single precision floating
point number, (approximately minus 3.4e38 to plus 3.4e38)
the result returned is invalid.

NOTE: You can connect both Analog and Digital inputs as

inputs to this function block.

Ignore invalid inputs: Select this option if you want the

function block to ignore any invalid inputs, if any, and consider
only the valid inputs to calculate the output. If this option is left
unselected, the invalid inputs will make the output also as
invalid.

Analog Inputs

Range
Input Input
Name Low High Value Description
x1, x2 >=- <+ unconne Unconnected inputs are set
infinit infinity cted to 0
y if all inputs unconnected, y
is set to 0
invalid If any input is invalid, y is
invalid

Output

Outpu
t
Name Range Description
Y Any floating Y= x1 - x2
point value

EN2Z-0960GE51 R0710 158

 CENTRALINE LYNX TOOL - USER GUIDE

ZONE ARBITRATION FUNCTION BLOCKS

The CentraLine LYNXTool provides the following Zone
Arbitration function blocks that you can configure and use to
build your application logic:
• General Set Point Calculator
• Occupancy Arbitrator
• Set Temperature Mode
• Temperature Set Point Calculator

General Set Point Calculator

This function does generic setpoint calculation, including
reset. It uses the three configuration parameters, effective
occupancy, current state, and reset input to calculate the
effective setpoint.

Analog Inputs

Range
Input Name Low High Input Value Description
effOccuCurrentState 0 3 unconnected Eff Occ Current state = 0 (OCC)
invalid Eff Occ Current state = 0 (OCC)
VAL < low Eff Occ Current state = 0 (OCC)
VAL > high Eff Occ Current state = 0 (OCC)
ResetInput >=- infinity <+ infinity unconnected Reset Input = Invalid
invalid Reset Input = Invalid
VAL < low Reset Input = Invalid
VAL > high Reset Input = Invalid
Reset0Pct >=- infinity <+ infinity unconnected Reset 0Pct = Invalid
invalid Reset 0Pct = Invalid
Val < low Reset 0Pct = Invalid
Val > high Reset 0Pct = Invalid
Reset100Pct >=- infinity <+ infinity unconnected Reset 100Pct = Invalid
invalid Reset 100Pct = Invalid
Val < low Reset 100Pct = Invalid
Val > high Reset 100Pct = Invalid
ResetAmount >=- infinity <+ infinity unconnected Reset Amount = Invalid
invalid Reset Amount = Invalid
Val < low Reset Amount = Invalid
Val > high Reset Amount = Invalid
OccupiedSetpoint >=- infinity <+ infinity unconnected Occupied Setpoint = Invalid
invalid Occupied Setpoint = Invalid
Val < low Occupied Setpoint = Invalid
Val > high Occupied Setpoint = Invalid
StandbySetpoint >=- infinity <+ infinity unconnected Standby Setpoint = Invalid
invalid Standby Setpoint = Invalid
Val < low Standby Setpoint = Invalid
Val > high Standby Setpoint = Invalid

159 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

UnoccupiedSetpoint >=- infinity <+ infinity unconnected Unoccupied Setpoint = Invalid

invalid Unoccupied Setpoint = Invalid
Val < low Unoccupied Setpoint = Invalid
Val > high Unoccupied Setpoint = Invalid
• Occ = 0
• Unocc=1
• Bypass =2
• Standby = 3
• Null = 255 Output

Output Name Range Description

EFF_SETPT Any floating point number Effective Setpoint

Reset
Reset allows you to change the Effective Setpoint either in the
direction of increased energy savings or in the direction of
increased comfort. The Reset Amount (+/-) is positive or
negative to accommodate energy savings versus comfort.
The reset value varies between zero and the Reset Amount
and is proportional to the Reset Input with respect to the
Reset 0% and Reset 100% parameters.

NOTE: Insure that the Reset 0% and Reset 100% parame-

ters are in the same engineering unit as the Reset
Input. The Reset Amount should be in the same units
as the configured setpoints.

Positive reset values are added to the setpoint and negative

resets are subtracted. Reset only applies in the occupied
mode. Reset 0% can be any relation to Reset 100%. The
following illustration shows Reset 0% less than Reset 100%
with a positive reset Amount. If the any of the Reset Input,
Reset 0%, Reset 100% or Reset Amount parameters are
invalid, the reset value is set to zero (0). Reset Calculation: Positive amount 0% < 100%

EN2Z-0960GE51 R0710 160

 CENTRALINE LYNX TOOL - USER GUIDE

• Occupied
• Unoccupied
• Bypass
• Standby
• Null
The General Setpoint Calculator uses the three configured
setpoints: effective occupancy, current state, and Reset Input
to determine the effective setpoint. If a setpoint is invalid,
INVALID will be propagated to the output as appropriate.

Eff Occ Current

State Eff Setpoint
UNOCC Result = unoccupied setpoint
STANDBY Result = standby setpoint
OCC Result = occupied setpoint + reset
Reset Calculation: Positive amount 100% < 0% BYPASS Result = occupied setpoint + reset
Eff Occ Current State
NULL Result = occupied setpoint + reset
Effective Occupancy Current State comes from a scheduler.
The valid values are

161 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

Occupancy Arbitrator
This function computes the current Effective Occupancy
Current State and the Manual Override State.

Inputs

Range
Input Name Low High Input Value Description
scheduleCurrentState 0 1,3,255 unconnected Schedule Current State = 255 (OCCNUL)
invalid Schedule Current State = 255 (OCCNUL)
VAL < low Schedule Current State =0 (OCC)
VAL > high Schedule Current State = 255 (OCCNUL)
WMOverride 0 1-3,255 unconnected WM Override = 255 (OCCNUL)
invalid WM Override = 255 (OCCNUL)
VAL < low WM Override = 0 (OCC)
VAL > high WM Override = 255 (OCCNUL)
NetworkManOcc 0 1-3,255 unconnected Network Man Occ = 255 (OCCNUL)
invalid Network Man Occ = 255 (OCCNUL)
VAL < low Network Man Occ = 0 (OCC)
VAL > high Network Man Occ = 255 (OCCNUL)
OccSensorState 0 1, 255 unconnected Occ Sensor State = 255 (OCCNUL)
invalid Occ Sensor State = 255 (OCCNUL)
VAL < low Occ Sensor State = 0 (OCC)
VAL > high Occ Sensor State = 255 (OCCNUL)
• Occ = 0
• Unocc=1
• Bypass =2 Outputs
• Standby = 3
• Null = 255
Output Name Range Description
EFF_OCC_CURRENT_STA 0 to 3 (Occupied, Unoccupied, Bypass, Effective Occupancy Current state
TE Standby)
MANUAL_OVERRIDE_STAT 0 to 3, 255 (Occupied, Unoccupied, Manual Override State
E Bypass, Standby, Null)

Configuration Specify the occupancy sensor operation. There are 3 choices:

Specify Net wins (0) or Last in wins (1). Conference room (0), Unoccupied Cleaning Crew (1), and
Unoccupied Tenant (2).

EN2Z-0960GE51 R0710 162

 CENTRALINE LYNX TOOL - USER GUIDE

Operation

Manual Override Arbitration Mechanism The Manual Override Arbitrator uses either a Net Wins or a
Manual Override Arbitration mechanism determines the value Last in Wins scheme to evaluate the inputs. Net Wins means
of Manual Override State. This value is used as an input to the the network command always takes precedence over the wall
Occupancy Arbitrator. module command. The following truth table is followed.

RESULT:
Net Wins/ Network Manual Override
Last in Wins Man Occ WM Override State Comment
Net Wins OCC Don’t Care OCC Result set to Network Man Occ.
Net Wins UNOCC Don’t Care UNOCC Result set to Network Man Occ.
Net Wins BYPASS Don’t Care BYPASS Result set to Network Man Occ.
Net Wins STANDBY Don’t Care STANDBY Result set to Network Man Occ.
Net Wins OCCNUL OCC OCC Result set to the wall module override.
Net Wins OCCNUL STANDBY STANDBY Result set to the wall module override.
Net Wins OCCNUL BYPASS BYPASS Result set to the wall module override.
Net Wins OCCNUL UNOCC UNOCC Result set to the wall module override.
Net Wins OCCNUL OCCNUL OCCNUL Override canceled.

163 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

With Last in Wins, the last override source is used to Occ, WM Override. Each second the function block is called,
determine the final state. If multiple sources change state in the algorithm looks for a change of state to Network Man Occ
the same second, they are evaluated in order: Network Man or WM Override. If either of these changed state, then
appropriate action is taken. Generally, a new command on
any input cancels prior action by another source..
Network RESULT:
Net Wins/ Man Occ WM Override Manual Override
Last in Wins (note2) (note 2) State Comment
Last in Wins OCC Don’t Care OCC Result set to Network Man Occ.
Last in Wins UNOCC Don’t Care UNOCC Result set to Network Man Occ.
Last in Wins BYPASS Don’t Care BYPASS Result set to Network Man Occ.
Last in Wins STANDBY Don’t Care STANDBY Result set to Network Man Occ.
Last in Wins OCCNUL Don’t Care OCCNUL Override canceled.
Last in Wins Don’t Care OCC OCC Result set to the wall module override.
Last in Wins Don’t Care STANDBY STANDBY Result set to the wall module override.
Last in Wins Don’t Care BYPASS BYPASS Result set to the wall module override.
Last in Wins Don’t Care UNOCC UNOCC Result set to the wall module override.
Last in Wins Don’t Care OCCNUL OCCNUL Override canceled.

NOTE: Any other input value not listed, is not a valid state. If occupied, unoccupied, standby, bypass or null. It is required
received, it is treated as OCCNUL. that the workstation (nviManOccCmd) or network node
(nviBypass) perform any timing needed (i.e. bypass).
NOTE: For last in wins, the value in the table was just WM Override Input
changed from another state and this is the current
state. WM Override is a method to command the occupancy state
from a locally wired wall module. WM Override can command
This function block doesn’t have the ability to trigger on a the state to be occupied, unoccupied, standby, bypass or null.
network variable update. This differs from E-Bus Mechanisms It is required the function block wired to this input perform any
which state the node should do the bypass timing for the timing needed (i.e. bypass). Note: the current T7770 wall
network Manual Occupancy Command and reload the timer module function doesn’t support occupied or standby
when a BYPASS update occurs. override, but future wall modules might.
From iteration to iteration of the Function Block, the Occupancy Arbitration Mechanism
Occupancy Arbitrator keeps track of the last state of the The Occupancy Arbitrator computes the effective occupancy
Network Man Occ and WM Override inputs so that it knows status. The inputs of the Effective Occupancy Arbitrator
when a transition occurs. On power up/reset the last latch include the Schedule Current State, Occ Sensor State, and
value is set to FALSE, regardless of the negation Manual Override State. The Manual Override State comes
configuration. Override is canceled after a power outage. The from above.
Network Man Occ and WM Override inputs must reassert The Effective Occupancy Arbitrator sets the Effective Occ
themselves after a power outage. Current State. Valid states of current state are:
Network Manual Occupancy Input • OCC: The space is occupied.
Network Man Occ is a method to command the occupancy • UNOCC: The space is unoccupied.
state from a network workstation or a node. The user may • BYPASS: The space is occupied, though it is not
write logic to combine these if both are required for the scheduled to be occupied.
application. Network Man Occ can command the state to be • STANDBY: The space is in a standby state, somewhere
between occupied and unoccupied.
OCCNUL is not a valid output. If all inputs are OCCNUL, the
output will be set to occupied.

EN2Z-0960GE51 R0710 164

 CENTRALINE LYNX TOOL - USER GUIDE

Manual Schedule Occ RESULT: Follows

Override Current Sensor Occ Sensor effOcc LonMark
State State State Operation CurrentState Comments SCC
OCC Don’t Care Don’t Care Don’t Care OCC Result = Manual Override Yes
State
STANDBY Don’t Care Don’t Care Don’t Care STANDBY Result = Manual Override Yes
State
UNOCC Don’t Care Don’t Care Don’t Care UNOCC Result = Manual Override Yes
State
BYPASS OCC Don’t Care Don’t Care OCC Result stays at occupied Yes
because bypass isn’t effective
when scheduled for occupied.
BYPASS STANDBY Don’t Care Don’t Care BYPASS Result stays at bypass. Yes
BYPASS UNOCC Don’t Care Don’t Care BYPASS Result = bypass Yes
BYPASS OCCNUL OCC Don’t Care OCC Result follows occupancy Yes
sensor
BYPASS OCCNUL UNOCC Don’t Care BYPASS Result follows manual Yes
override
BYPASS OCCNUL OCCNUL Don’t Care OCC When occupancy sensor is Yes
null, default to occupied.
OCCNUL STANDBY Don’t Care Don’t Care STANDBY Result = scheduled state. Yes
OCCNUL OCC OCC Don’t Care OCC All say we’re Occupied. Yes
OCCNUL OCC UNOCC Don’t Care STANDBY We’re schedule to be Yes
occupied but room is actually
unoccupied, so go to standby
to save energy.
OCCNUL OCC OCCNUL Don’t Care OCC Sensor not present so use Yes
schedule.
OCCNUL UNOCC UNOCC Don’t Care UNOCC All say we’re unoccupied. Yes
OCCNUL UNOCC OCCNUL Don’t Care UNOCC Sensor not present so use Yes
schedule
OCCNUL OCCNUL OCC Don’t Care OCC Result -= occupancy sensor Yes
state.
OCCNUL OCCNUL UNOCC Don’t Care UNOCC Result -= occupancy sensor Yes
state.
OCCNUL OCCNUL OCCNUL Don’t Care OCC Result = occupied because Yes
the LonMark SCC sets a null
occupancy sensor to
Occupied.
OCCNUL UNOCC OCC Conference UNOCC Stay unoccupied regardless of Yes
Room what the sensor says (i.e.
save energy).
OCCNUL UNOCC OCC Cleaning Crew STANDBY We’re schedule to be No
unoccupied but the room is
actually occupied, so go to
standby for the comfort of the
cleaning crew.
OCCNUL UNOCC OCC Tenant OCC We’re schedule to be No
unoccupied but the room is
actually occupied, so go to
occupied for the comfort of the
tenant.

165 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

Set Temperature Mode

This function automatically calculates the effective
temperature control mode based on the control type, system
switch setting, network mode command, temperature set
points, supply temperature and space temperature. From
iteration to iteration, the Function Block keeps track of the
previous command mode and the effective temperature
mode. On power up/reset, these are cleared.

effTempMode indicates the current Mode determined by input

states and arbitrated by control logic. SetTempMode does not
generate all the possible Modes available. The valid
enumerated values have the following meanings:

effTempMode Meaning
COOL_MODE=0 Cool air is being supplied to the node via the central air supply and cooling energy is
being supplied to the controlled space.
REHEAT_MODE=1 Cool air is being supplied to the node via the central air supply. The air is being
reheated by a local Heat source.
HEAT_MODE=2 Heated air is being supplied to the node via the central air supply and heated air is
being supplied to the controlled space.
EMERG_HEAT=3 Emergency Heat is being supplied to the node via the central air supply.
OFF_MODE=255 Controller is commanded off.

Analog Inputs

Range
Input Name Cfg Low High Input Value Description
sysSwitch IN 0 255 unconnected SystemSwitch = SS_AUTO(0)
invalid SystemSwitch = SS_AUTO(0)
VAL < low SystemSwitch = SS_AUTO(0)
VAL > high SystemSwitch = SS_AUTO(0)
cmdMode IN 0 255 unconnected val = CMD_AUTO_MODE(0)
invalid val = CMD_AUTO_MODE(0)
VAL < low val = CMD_AUTO_MODE(0)
VAL > high val = CMD_AUTO_MODE(0)
supplyTemp IN 0 255 unconnected SupplyTemp = invalid
invalid SupplyTemp = invalid
Val < low SupplyTemp = low
Val > high SupplyTemp = high
spaceTemp IN 0 255 unconnected SpaceTemp = invalid
invalid SpaceTemp = invalid
Val < low SpaceTemp = low
Val > high SpaceTemp = high
effHeatSP IN >=- <+ unconnected EffHeatSp = 68
invalid EffHeatSp = 68

EN2Z-0960GE51 R0710 166

 CENTRALINE LYNX TOOL - USER GUIDE

effCoolSP IN >=- <+ unconnected EffCoolSp = 75

invalid EffCoolSp = 75
allowAutoChange IN_PAR 0 1 unconnected allowAutoChange=1
invalid allowAutoChange=1
Val < low allowAutoChange=1
Val > high allowAutoChange=1

Outputs

Range
Output Name Cfg Low High Description
EFF_SETPT OUT_FLT 0.0 255.0 If effTempMode=COOL_MODE then val= effCoolSetPt, else
val=effHeatSetPt
EFF_TEMP_MO OUT_DIG 0 255 See arbitration table for VAV and CVAHU behavior
DE

Configuration Input Enumerations

Specify the control Type (controlType)
• 0 – CVAHU
• 1 – VAV

sysSwitch
SS_AUTO =0
SS_COOL =1
SS_HEAT =2
SS_EMERG_HEAT =3
SS_OFF = 255
cmdMode
CMD_AUTO_MODE = 0 =0
CMD_HEAT_MODE = 1 =1
CMD_COOL_MODE = 2 =2
CMD_OFF_MODE = 3 =3
CMD_EMERG_HEAT_MODE = 4 =4
CMD_NUL_MODE = 255 = 255

The CVAHU arbitration logic for ControlType = 0 (CVAHU) is

summarized by the table below:

Space Temp sysSwitch cmdMode effTempMode

X X CMD_OFF(3) OFF_MODE(255)
X X CMD_EMERG_HEAT_MODE(4) EMERG_HEAT(3)
X X CMD_COOL_MODE(2) COOL_MODE(0)
X X CMD_HEAT_MODE(1) HEAT_MODE(2)
X X ENUMERATION (5) through HEAT_MODE(2)
ENUMERATION (254)
X SS_COOL (1) CMD_AUTO_MODE(0), CMD_NUL_MODE(255) COOL_MODE (0)
X SS_HEAT (2) CMD_AUTO_MODE(0), CMD_NUL_MODE(255) HEAT_MODE(2)
or ENUMERATION(4)
through ENUMERATION
(254)

167 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

X SS_EMERGENCY_HEAT(3) CMD_AUTO_MODE(0), CMD_NUL_MODE(255), EMERG_HEAT(3)

X SS_OFF (255) CMD_AUTO_MODE(0), CMD_NUL_MODE(255) OFF_MODE(255)
INVALID SS_AUTO(0), invalid, CMD_AUTO_MODE(0), CMD_NUL_MODE(255) HEAT_MODE(2)
unconnected, or a non-listed
enumeration.
VALID SS_AUTO(0), invalid, CMD_AUTO_MODE(0), CMD_NUL_MODE(255), COOL_MODE(0) or
unconnected, or a non-listed HEAT_MODE(2)
enumeration. (see following note)

X means Don’t Care The VAV Mode arbitration logic for controlType = 1 (VAV) is
summarized by the table below:
NOTE: If allowAutoChange = 1 then allow to switch between
HEAT_MODE and COOL_MODE. Must have valid
effHeatSP and effCoolSP. If allowAutoChange = 1
and effHeatSp > effCoolSp, then effHeatSp will be
internally set to effCoolSP.

Space
Temp sysSwitch Supply Temp cmdMode effTempMode
X X X CMD_OFF_MODE(3) OFF_MODE(255)
X X X CMD_EMERG_HEAT_MODE(4) HEAT_MODE(2)
X X X ENUMERATION (5) through COOL_MODE(0)
ENUMERATION (254)
Valid X <70.0 CMD_AUTO_MODE (0), COOL_MODE (0) or
CMD_HEAT_MODE (1), REHEAT_MODE (1)
CMD_NUL_MODE (255) (see note 1)
Valid X <70.0 CMD_COOL_MODE(2) COOL_MODE (0)
Valid X 70.0 TO 75.0 CMD_AUTO_MODE (0), COOL_MODE (0),
CMD_HEAT_MODE (1), REHEAT_MODE (1),
CMD_COOL_MODE (2), HEAT_MODE (2) (see note 1 for
CMD_NUL_MODE (255) transition between cool mode and
reheat mode)
Valid X >75 CMD_AUTO_MODE (0), HEAT_MODE(2)
CMD_HEAT_MODE (1),
CMD_NUL_MODE (255)
Valid X Invalid or CMD_HEAT_MODE (1) HEAT_MODE (2)
unconnected
Valid X Invalid or CMD_COOL_MODE (2) COOL_MODE (0)
unconnected
Valid SS_COOL(1) Invalid or CMD_AUTO_MODE (0), COOL_MODE(0)
unconnected CMD_NUL_MODE (255)
Valid SS_HEAT(2) Invalid or CMD_AUTO_MODE (0), HEAT_MODE(2)
unconnected CMD_NUL_MODE (255)

EN2Z-0960GE51 R0710 168

 CENTRALINE LYNX TOOL - USER GUIDE

Valid SS_ Invalid or CMD_AUTO_MODE (0), HEAT_MODE(2)

EMERGENCY_H unconnected CMD_NUL_MODE (255)
EAT(3)
Valid SS_OFF(255) Invalid or CMD_AUTO_MODE (0), OFF_MODE(255)
unconnected CMD_NUL_MODE (255)
Valid SS_AUTO(0), Invalid or CMD_AUTO_MODE (0), COOL_MODE(0) or
invalid, unconnected CMD_NUL_MODE (255), REHEAT_MODE(1)
unconnected, or a (see note 1)
non-listed
enumeration.
InValid SS_AUTO(0), Invalid or CMD_AUTO_MODE (0), COOL_MODE(0)
invalid, unconnected CMD_NUL_MODE (255),
unconnected, or a
non-listed
enumeration.

X means Don’t Care If in cool mode and spacetemp < effheat setpt and space temp
< effcoolsetpt – 1.0 then go to reheat mode. If in reheat mode
NOTE: If allowAutoChange = 1 then allow to switch between and spacetemp > effCoolSetpt and spacetemp > effHeatsetpt
REHEAT_MODE and COOL_MODE. Must have + 1.0 then go to cool mode.
valid effHeatSP and effCoolSP.

169 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

Temperature Set Point Calculator

This function calculates the current Effective Heat setpoint
and Effective Cool setpoint based on the current schedule
information, occupancy override, and intelligent recovery
information.

Inputs
Range
Input Name Low High Input Value Description
EffOccCurrentState 0 3 unconnected Eff Occ Current State = 0 (OCC)
invalid Eff Occ Current State = 0 (OCC)
VAL < low Eff Occ Current State = 0 (OCC)
VAL > high Eff Occ Current State = 0 (OCC)
ScheduleNextState 0 1, 3, 255 unconnected Schedule Next State = 255 (OCCNUL)
invalid Schedule Next State = 255 (OCCNUL)
VAL < low Schedule Next State = 255 (OCCNUL)
VAL > high Schedule Next State = 255 (OCCNUL)
ScheduleTUNCOS 0 11520 unconnected Schedule TUNCOS = 11520
(min) invalid Schedule TUNCOS = 11520
VAL < low Schedule TUNCOS = 0
VAL > high Schedule TUNCOS = 11520
Setpoint >=- <+ unconnected Setpoint = 0
invalid Setpoint = 0
VAL < low Setpoint = 0
VAL > high Setpoint = 0
HeatRampRate 0 <+ unconnected Heat Ramp Rate = 0
invalid Heat Ramp Rate = 0
VAL < low Heat Ramp Rate = 0
VAL > high Heat Ramp Rate = 0
CoolRampRate 0 <+ unconnected Cool Ramp Rate = 0
invalid Cool Ramp Rate = 0
VAL < low Cool Ramp Rate = 0
VAL > high Cool Ramp Rate = 0
ManualOverrideState 0 3,255 unconnected Manual Override State = 255 (OCCNUL)
invalid Manual Override State = 255 (OCCNUL)
VAL < low Manual Override State = 255 (OCCNUL)
VAL > high Manual Override State = 255 (OCCNUL)
• Occ = 0
• Unocc=1
• Bypass =2
• Standby = 3
• Null = 255

EN2Z-0960GE51 R0710 170

 CENTRALINE LYNX TOOL - USER GUIDE

Outputs You may have more than one TempSPCalc Function Block,
however all blocks use the same nciSetpoints network
variable and map to the same 6 public variables. See below
Output Name Range Description for more information.
EFF_HEAT_S Any floating point Effective Heat Setpoint
ETPT number
EFF_COOL_ Any floating point Effective Cool Setpoint
SETPT number

Configuration
• Specify the 6 setpoints. When the TempSPCalc Function
Block is used, nciTempSetpoints (SNVT temp setpt) is
added by the LYNX Tool. nciTempSetpoints is mapped by
the Tool to the first 6 Public variables under Control non-
volatile. The order is:
— Occupied Cool
— Standby Cool
— Unoccupied Cool
— Occupied Heat
— Standby Heat
— Unoccupied Heat

Temperature Setpoint Calculator • Scheduled next state and TUNCOS

• The Temperature Setpoint Calculator uses the following 6 • Center/offset setpoint
programmed setpoints to determine the effective heat • Manual override state
setpoint and effective cool setpoint: • Recovery heat ramp rate
• Effective occupancy current state • Recovery cool ramp rate

171 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

The algorithm: Center Setpoint

• Verifies if inputs are within range. If the value on the Setpoint input is greater than or equal to 10,
• Computes the occupied and standby heat and cool it will be used as the center setpoint (that is, absolute
setpoints based on the setpoint input and programmed setpoint). If an invalid setpoint is on the Setpoint input, then
setpoints. the programmed setpoints will be used. The individual heat/
— If the effective occupancy current state is in unoccu- cool setpoints for occupied and standby mode then derive
pied mode and not in manual override, then calculates from the Setpoint input minus/plus half the zero energy bands
the recovery ramps. calculated from the programmed setpoints.
— If the effective occupancy current state is in occupied
or bypass mode, uses the occupied setpoints.
— If the effective occupancy current state is in standby
Example
mode, uses the standby setpoints. • zeb occ = programmed occupied cool - programmed
occupied heat
• zeb standby = programmed standby cool - programmed
Programmed Set Points standby heat.
The controller is programmed with six setpoints. There are • Occupied cool setpoint = setpoint + 1/2 zeb occ
three setpoints of occupied, standby and unoccupied for • Occupied heat setpoint = setpoint - 1/2 zeb occ
heating and the same for cooling. All six can be changed from • Standby cool setpoint = setpoint + 1/2 zeb standby
the Network via nciSetpoints. The Temperature Setpoint • Standby heat setpoint = setpoint - 1/2 zeb standby
calculator does not place any restrictions on relationships
between the setpoints and other inputs and the resulting
calculations. This function block depends on the Tools writing
Manual Override State
nciSetpoints to enforce the range and relationship. The Manual Override State is required to turn off recovery if in
manual mode. If the Manual Override State is any value other
For reference, the LonMark Space Comfort Controller profile than null, then the algorithm does not know the scheduled
defines nciSetpoints as having a range of 10 Deg. C to 35 next state and setpoint recovery is NOT done.
Deg. C with the following relationship unoccupied heat =
standby heat = occupied heat = occupied cool = standby cool NOTE: Manual Override State does not affect the effective
= unoccupied cool. occupancy state. The OccArb function block already
handles this. The effective setpoints never go to the
Setpoint Input state commanded by the Manual Override state
This input allows the temperature setpoint for the occupied input. Manual Override State just affects recovery as
and standby mode to be changed via the wall module and/or stated above.
network. This input can be either center or offset setpoint. If
the input is less than 10, then it is treated as offset setpoint. If Effective Occupied State
the input is greater than or equal to 10, it is treated as center This is used by the algorithm to determine the setpoints for the
setpoint. It is the user’s responsibility to insure the results are current occupancy state. When the Effective Occupancy
within the desired range. That is, it is possible to combine the Current state is occupied or bypass, use the occupied
setpoint input and the programmed heat and cool setpoints setpoints. When the Effective Occupancy Current state is
and get an effective setpoint outside of the unoccupied standby, use the standby setpoints. When the Effective
setpoints. Occupancy Current state is unoccupied, recover the setpoint
to the next state of occupied or standby. No recovery is done if
Offset Setpoint in manual mode. See Adaptive Intelligent Recovery section.
The setpoint acts in offset mode (that is, relative setpoint)
when the value on the Setpoint input is less than 10. The Heating and Cooling Ramp rates
setpoint input adjusts the programmed occupied and standby These are used by the adaptive recovery algorithm to recover
heating and cooling setpoints up and down by the amount on the heating and cooling setpoints from their unoccupied
the input. The user must insure the input range is less than values.
+10 for offset setpoint to be used. The setpoint input does not
affect the unoccupied setpoints. During bypass, the occupied
setpoints are adjusted. If the setpoint input is not connected or Schedule Next state and TUNCOS
the sensor has failed, the offset is zero. You must insure These are used by the adaptive recovery algorithm to recover
consistent units. That is, if the Setpoint input is in degrees the heating and cooling setpoints from their unoccupied
Fahrenheit, the programmed setpoints should also be in values.
degrees Fahrenheit.
• Occupied cool setpoint = programmed occupied cool Adaptive Intelligent Recovery
setpoint + Setpoint input. Set point recovery applies to setpoint changes associated
• Occupied heat setpoint = programmed occupied heat with the following schedule state changes:
setpoint + Setpoint input.
• Standby cool setpoint = programmed standby cool setpoint • Unoccupied to Standby
+ Setpoint input. • Unoccupied to Occupied
• Standby heat setpoint = programmed standby heat setpoint Setpoint changes from occupied or standby to unoccupied
+ Setpoint input. state, changes from occupied to standby state, and changes
from standby to occupied state use a step change in setpoint.
The heating or cooling recovery ramp begins before the next
state transition time.

EN2Z-0960GE51 R0710 172

 CENTRALINE LYNX TOOL - USER GUIDE

During the recovery ramps, the heating and cooling set points mode. This means the setpoint steps from one setpoint to the
are ramped from the unoccupied setpoint to the next state other at the event time. (that is, No extra 10 minutes). The
setpoint. The setpoint ramps will be at the target setpoint 10 user must insure consistent units. That is, the ramp rates
minutes prior to the occupied/standby event time. should be in the same units as the setpoints.
This allows the HVAC equipment an extra 10 minutes to get Note: If the user programs a rate of 1 degree/Hr and has more
the space temperature to the target setpoint during recovery. than 192 degree spread between OCC and UNOCC set
points, the algorithm will be in recovery immediately when
NOTE: Recovery is NOT done if manual occupancy is in going to UNOCC. This is because the maximum TUNCOS is
effect. 11520 minutes times 1 degree/Hr = 192 degree maximum
delta.

TUNCOS Mesa
The controller implements the TUNCOS Mesa feature. This
feature, also known as the Smith Mesa after Gary Smith
implemented it in the T7300 series 1000. The TUNCOS Mesa
was added to the algorithm to insure the HVAC equipment
gets the space temperature up to setpoint by the occupied
time. The recovery algorithm subtracts 10 minutes from the
TUNCOS and uses that to calculate the setpoint ramps.

Effective Setpoint Limiting

You provide the heat and cool recovery ramp rates to the This algorithm does nothing to insure the effective cooling
Temperature Setpoint Calculator. These can be constants, setpoint does not go above the unoccupied cooling setpoint
values calculated using the Ratio function block using outdoor and the effective heating setpoint does not go below the
air temperature, or some other method. unoccupied heating setpoint. No check is made to insure the
Heating and cooling recovery ramp rates can be any value effective heat and cool setpoints stay a minimum distance
greater than or equal to zero and have units of degree/Hr. A apart.
ramp rate of 0 degree/Hr means no recovery ramp for that

173 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

PASS THRU
Use this utility to provide input to multiple slots in one go. Alternatively, you can drag a Pass Thru component from the
Example: Assume we have an Application called CentraLine LYNX Palette (Util > Pass Thru) to Application1.
Application1. This has a function block Add inside it. Now, you Now, you can expose the Pass slot using the Composite
want to give inputs to all slots of the Add block in one go from feature and then connect this slot to the NV/Object. Double-
an NV or Object outside Application1. To achieve this, you can click Application1 and connect Pass slot to as many slots on
expose all slots of the Add block using the Composite feature the Add block as you want.
and then connect the NV or Object to each slot.

EN2Z-0960GE51 R0710 174

 CENTRALINE LYNX TOOL - USER GUIDE

CALIBRATE SENSORS
Pre-requisites NOTE: If no sensors are configured, a warning message,
'No sensors configured' appears. If a Modulating
• The application logic is opened in Niagara Workbench and input is configured as Counter/Pulse Meter it will not
the same is downloaded to the Controller. be shown up in this screen.
• The Controller should be online.

Procedure
The Sensor Calibration screen allows the user to calibrate
the sensor. This option is available only for commissioned and
downloaded controllers.
1. Right click the controller name on the Nav palette.
Select Calibrate Sensor. The Sensor Calibration dia-
log box opens.
2. Enter the value the sensor must detect in the Edit Value
field.
3. Click Close to close the dialog box.

Name Definition
Name Shows all the Modulating Inputs configured in the ControlProgram.
Sensor Type Shows the actual sensor type configured for that modulating input. This field is non-editable.
Actual Value Shows the actual value of the modulating input read by the controller. This field is non-editable.
Edit Value Enter the value that the sensor must detect.
Offset Shows the difference between the actual and the edit value. This field is non-editable.
Calibrate Click Calibrate to calibrate the Modulating Input to the value entered by the user.
Refresh Click Refresh to refresh the Modulating Input values.
Close Click Close to close the dialog box.

175 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

DIAGNOSE OUTPUTS
You can monitor and diagnose the output value of the Lon and Procedure
Bacnet controllers. If the output is faulty, it can be identified by 1. Right click on the controller. Select Controller Diag-
manually setting the values of the physical points. nostics. The Diagnostics dialog box appears.
2. Enter the value of the current output to be detected in
Pre requisites the Edit Value field and enter/select information as
given in the following table..
• The Controller should be online.
• It should be in a downloaded state. Name Definition
Modulating The number of Modulating Outputs depends
The Diagnostic screen displays: Output on the outputs configured in the application
• The Outputs section where outputs can be commanded. logic.
• The current output values to enable you to watch the effect Actual Value: Displays the value of the
of the outputs on various values. modulating output read by the controller.
• The current mode of the device is displayed. This field is non-editable.
Edit Value: Enter the value that the current
output must be detecting. The range is 0-
Diagnose Outputs for a Lon Device 100 percent.
Using the Controller Diagnostics feature, you can monitor Binary Output The number of Binary Outputs depends on
and diagnose the outputs of a Lon device. By setting the the outputs configured in the application
mode from auto to manual, you can edit the values of the logic.
modulating and binary outputs to get the required output. Actual Value: Displays the value of the
modulating output read by the controller.
This field is non-editable.
Edit Value: Select True or False.
Mode Displays the current mode of the device.
Set Click Set to set the controller to manual
mode. It writes the configured values to the
controller and automatically puts the
modulating output in the manual mode.
Refresh Click Refresh to refresh the values.
Close Click Close to close the dialog box. It
prompts you to set all inputs in the manual
or auto mode.

NOTE:

— When an output is set to manual mode, the tool

writes to priority 8 of that output.
— If the output is already driven at a higher priority,
there is no effect of setting an output in manual
mode. In this case, manual mode takes into effect
only when priority 1 to priority 7 are relinquished.
3. Click Close to close the dialog box.

EN2Z-0960GE51 R0710 176

 CENTRALINE LYNX TOOL - USER GUIDE

Diagnose Outputs for a Bacnet Device Binary Output The number of Binary Outputs depend on
Using the Diagnose Outputs feature, you can monitor and the outputs configured in the application
diagnose the outputs of a Bacnet device. By setting the mode logic.
from auto to manual, you can edit the values of the modulating Current Value: Displays the value of the
and binary outputs to get the required output. binary output read by the controller. This
field is non-editable.
Edit Value: Select True or False. This field
Procedure is non-editable in the automatic mode.
1. Right-click on the controller. Select Diagnose Outputs. Enable Manual Mode: Check this check
The Diagnostics screen of TargetLYNX dialog box box to enable manual mode. The Edit Value
appears. field is editable and you can select True or
2. Type/select information as given in the following table. False from the list.
Name Definition
NOTE: If the value entered in the field is
Modulating The number of Modulating Outputs depend invalid, an error message appears.
Output on the outputs configured in the application
Set Click Set to set the changes made to the
logic.
values of the controller in manual mode. It
Current Value: Displays the value of the
writes the configured values to the controller
modulating output read by the controller.
when the modulating output or binary output
This field is non-editable.
are in manual mode.
Edit Value: Type the value that the current
output must be detecting. The range is 0- Refresh Click Refresh to refresh the values.
100 percent. This field is non-editable in the Close Click Close to close the dialog box. It
automatic mode. prompts you to set all outputs into manual or
Enable Manual Mode: Check this check auto mode.
box to enable manual mode. The Edit Value
field is editable and you can type the value
that the current output must be detecting. 3. Click Close to close the dialog box.
The range is 0-100 percent.

NOTE: If the value entered in the field is

above or below the range, an error
message appears.

177 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

MACROS
A Macro is a group of functional blocks grouped together that You can selectively choose inputs/outputs of the blocks that
define a specific functionality. Commonly used program you have used in a macro need to be exposed in a particular
elements can be defined as macros so that they could be setup. However, this does not limit you from using the same
reused across applications. Macros offer you a way of macro elsewhere and choosing a different set of inputs/
transporting logic between different devices. They help in outputs to expose.
segmenting a huge program into smaller logical blocks. When a macro is created and saved, it can be dragged and
Functional blocks can be grouped as macros and you can dropped on to the wiresheet view and used in creating
include macros under macros. Macros can be re-used in other application logic. The fields of the function blocks that make
applications. up a macro become available as fields of the macro itself.
Macros are displayed as any other function blocks in a
container view.
Macros:
• can contain only functional blocks.

EN2Z-0960GE51 R0710 178

 CENTRALINE LYNX TOOL - USER GUIDE

LYNX LIBRARY
You can use a LYNX library to store devices, To change the current parent folder path:
ControlPrograms, applications, and/or macros. A default 1. Click the options button on the library palette to get a
library is automatically created at the location <Drive>:/ drop-down list and select Select Parent Path. The
Niagara/AppLib. This library is available when you open the Advance Options dialog box appears.
LYNX Library the first time. You cannot close this default
library.
You can, however, create your own library to create and store
macros, applications, and/or devices. Each library comes with
two default folders: Device(s), Application(s) and
SBus_WM_Config(s). All the SBusWall modules you add
and save are stored in the SBus_WM_Config(s) folder of a
library.
All the devices you create and save are stored in the
Device(s) folder of a library. All macros and applications you
create and save are stored in the Application(s) folder of a
library. 2. Click the browse button on the right side of the
Advance Options dialog box. The Directory Chooser
Display LYNX Library Palette dialog box appears.
To display the LYNX Library palette on the left side of the 3. Browse through to the location where you have stored
window: your library files and click Choose.
4. Select the Save as default parent path option if you
• From the Menu bar, select Windows > Side Bars > LYNX
want to make this folder the default folder for future
Library.
use.The libraries available in the default parent folder
path are displayed when the workbench is restarted. On
subsequent uses, the libraries available in the last
selected parent folder path are listed. Even while
uploading items, the default library path is invoked.
5. Click OK. The drop-down list box in the LYNX palette
then displays the application libraries in the selected
folder. If you select an application library from the drop-
down list box, all the devices and applications present in
that library in the tree is displayed in the sidebar.

NOTE: The parent folder path selected in a workbench is not

applicable when the library is opened from a
browser. The parent folder selected in the browser is
applicable only when the library is opened from a
browser and is not reflected when the library is
The LYNX Library palette appears on the left side of the opened from a workbench.
screen with the contents of the default library. Every library
contains the default folders: Device(s), Application(s) and Close LYNX Library Palette
SBus_WM_Config(s). The application libraries present in the Click the down arrow on the menu bar of the LYNX Library
default parent folder path are displayed in the dropdown list. palette and click Close to close the library palette.

Open LYNX Library

Macros, Applications and Devices that you create can be
stored in a library for being reused in another project or
scenario. You can create libraries based on your requirement
and store them. You can then import selected items of
libraries in the station (in LonNetwork or Device Logic).

179 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

There is a default library shipped by CentraLine. However,

you can create and save your own libraries containing
macros, applications and or devices. Such user defined
libraries can be modified, saved and shared across projects or
across users.
To open a user-created library:

1. Click the options button on the library palette to get a

drop-down list and select Select Parent Path. 

 NOTE: If you have multiple libraries stored at a location, use

the down arrow next to the field displaying the library
path and select the library you want to open.

— The parent folder path selected in a workbench is not

applicable when the library is opened from a browser.
The parent folder selected in the browser is applicable
only when the library is opened from a browser and is
not reflected when the library is opened from a work-
bench.

Close LYNX Library

Click the button on the library palette (as shown below) and
click Close Library to close the library.

The Advance Options dialog box appears.

NOTE: The default library cannot be closed.

Add Items to LYNX Library

2. Click the browse button on the right side of the You can add devices, macros, Sbus wall modules and/or
Advance Options dialog box and select a destination applications to a library.
folder where the library you have stored is located. The
Directory Chooser dialog box appears. Add New Item to Library
3. Browse through to the location where you have stored
your library files and select Choose.
4. Select the Save as default parent path option if you From the LYNX Library Palette
want to make this folder the default folder for future To add a new Macro, Device, SbusWallModule,
use.The libraries available in the default parent folder ControlProgram, or Application to a library:
path are displayed when workbench is restarted. On 1. Open the Library in which you want to add the new
subsequent uses, the libraries available in the last application logic.
selected parent folder path are listed. 2. Click the options button on the library palette to get a
5. The contents of the library are displayed in the library drop-down list and select New > Application/LonDe-
palette. Also, the path where the library files are stored vice/BacnetDevice/Macro/SBusWallModule.
is also displayed in the library palette. 3. The App/LonDevice/BacnetDevice/Macro/
SBusWallModule Name dialog box appears.
4. Type a name for the item and click OK. The new item is
added to the library in the Application(s) folder of the
library in case of macros and applications and to the
Device(s) folder in case of in case of Lon and Bacnet
devices and displayed in the library palette.

EN2Z-0960GE51 R0710 180

 CENTRALINE LYNX TOOL - USER GUIDE

From the Nav Palette gara. If you want to change the location, click
To add a new Macro, Device, Application, ControlProgram, or Advanced Settings to display the Advanced Options
SBusWallModule to a library: dialog box.
6. Click the ellipsis (...) button and browse through to the
1. Right-click the device, macro, application, ControlPro- location where you want to save this new library and
gram, or SBusWallModule in the Nav palette and select click Choose. The new library is created at the location
Save to Library. The Save Library Item dialog box you have specified.
appears. 7. Enter/select:
— Name: Enter a name for the items you are saving.
— Macro/Device/Type: Select the type of item you are
saving (macro/device/application, respectively).
— Description: A brief description of the item with the
changes made.
— Version: This is auto-updated. You will not be able to
change the version number.
— Attachment: Click Add to browse through and attach
a document(s). The path of the document you are
attaching is displayed in the Attachment field. Select
an attachment and click Remove to remove an attach-
ment.
8. Click OK. The new item is stored at the desired location.

Saving Library Items

You can add or modify devices, applications,
SBusWallModules, or macros to a library. Items such as
Applications and macros are saved to the Application(s) folder
in a library while a new device or changes to a device are
added to the Device(s) folder in a library. Once you have done
all the changes to a library, you must save them so that they
are available for subsequent use.

NOTE: You do not have the option to save these items to a

different library.

To save the changes you have made to a library:

1. Click the options button on the library palette to get a
NOTE: Note: The Library list displays all libraries in the Par- drop-down list and select Save Library. The Save
ent folder. The Parent folder is indicated by the Par- Library Items dialog box appears with the unsaved
ent Folder Path.  changes listed.
The Save to Library function is possible only in the 2. Select the items on the list you want to save. A check
Engineering mode and applies to macros, applica- mark appears across each item you have selected.
tions, devices, SBusWallModules, and control pro- 3. Click OK.The Save Library Item dialog box appears
grams. with the library name and folder where the library is
being saved. The default library path is displayed in the
2. You have options to: Parent Folder Path field when the workbench is
Save as New App: If you are adding this item for the restarted. On subsequent uses, the last selected library
first time to a library, this is the only option available. If is listed.
not saving an item for the first time, this option creates a 4. Select one of the two options to save the changes you
new item in the specified library.  have made. You have options to: 
or  Overwrite App (new version): This creates a new ver-
Overwrite App (New Version): If you are adding an sion of the existing library. By selecting this option, all
item for the first time to a library, this option is disabled. changes are saved as a new version. 
If not saving an item for the first time, this option over- Save as New App: This creates a new library and
writes the existing item and increments the version saves the library with the changes as a new library.
number. 5. If you have chosen to:
3. Select the library to which you want to save this item (d)Overwrite the existing version, type or select:
from the Library list and proceed to step 6 of this proce- — Description: A brief description of the application with
dure. the changes made.
4. Alternatively, if you want to create a new library and — Type: Select the Application Type.
save the changes in the newly created library, click the — Version: This is auto-updated. You will not be able to
+ button. The Library Name dialog box appears. change the version number.
5. Enter the name of the library and click OK. The location — Attachment: Click Add to browse through and attach
where the new library is saved is displayed in the Par- a document(s). The path of the document you are
ent Folder Path. The default location is <Drive>:\Nia- attaching is displayed in the Attachment field. Select
an attachment or click Remove to remove an attach-
ment.

181 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

d. Save as a new application, enter/select: — When a physical IO is added to an application under

— Name: Enter a name for the items you are saving. Applications category in the library, the physical point
— Description: A brief description of the application with is not assigned any pin. It is in an unassigned state.
the changes made. — When an application is created under Applications cat-
— Type: Select the Application Type. egory in the application library, the tool does not warn
— Version: This is auto-updated. You will not be able to users of the application going out of limits (This is
change the version number. because the application (in the absence of the device)
— Attachment: Click Add to browse through and attach is independent of the model and model based restric-
a document(s). The path of the document you are tions). You can create as many NVs/Objects, and IOs
attaching is displayed in the Attachment field. Select and drag as many FBs as you wish.
an attachment and click Remove to remove an attach- — When an application is created under a device in the
ment. library, the tool warns you when the application goes
6. Click OK to complete saving the items to the library. The out of limits based on the model selected.
newly added items along with the attachments are dis- — You can also add SBus wall module to your applica-
played in the library palette. tion logic and load the same to a library only if you are
Alternatively, you can save a device/macro/application/ using the LonLYNX II, LYNX Micro, or BacnetLYNX
SBusWallModule that you have created from the Nav Palette. models.
For additional information, refer to From the Nav Palette — PX files created on the library item being saved are
section of this topic. also saved to the library automatically.

NOTE:
Load Library Item
— When an Application folder is saved to a library, all This feature enables you to quickly load an application or a
network variables/Bacnet objects created on that macro you might have stored in a library to an application or
folder are also saved. macro you are currently working with in the Nav palette.
— When an Application folder is saved to a library, an
NV/Object whose field(s) is(are) exposed on the same NOTE: The Load From Library function is possible only in
folder as point(s) is saved to the library in such a way the Engineering mode and applies to macros, appli-
that: cations, and control programs only. You can also add
— The network variable/object is saved. SBus wall module to your application logic and load
— The fields are exposed as points the same way as in the same to a library only if you are using the LonL-
the application being saved (that is, NV/Object fields YNX II, LYNX Micro, or BacnetLYNX models.
remain exposed and the NV/Object configuration
screen indicates that the fields of the NV/Object are 1. Right-click the macro/application on the Nav palette and
exposed on the same folder level. select Load from Library.
— When an Application folder is saved to a library, an
NV/Object whose field(s) is(are) exposed on a differ-
ent folder other than the current one as points is saved
in such a way that:
— The network variable/object is saved.
— The fields exposed as points are saved as unexposed
fields. The NV/Object configuration view indicates
those fields as unexposed
— Fields exposed as points on the same folder are saved
as exposed points
— When an Application folder with exposed point(s)
whose associated NV/Object is present in other fold-
ers other than the current folder and its child Applica-
tion folders, is saved to a library, the associated NV/
Object is also copied along with that folder.
— When an Application folder is saved to a library, the
physical points (I/O points) in the logic are saved along
with their assigned terminal IDs.
— When an Application folder is saved to a library, only
the NVs/Objects created in that folder and its child
Application folders are saved. No additional Fixed
NVs/Objects are saved along with it. (This implies that
the tool does not do any thing in the background to
make the application being saved a complete applica-
tion based on the model because the application is
independent of the model.)
— When an Application is saved to the library, all the
fixed NVs/Objects and fixed IOs become of the type 2. The Load Library Item dialog box appears.
custom in the library and they can be modified/ 3. Select the Library from which you want to load an item
deleted. from the Library list. The parent folder path displays the
location of the library from which you are loading items.

EN2Z-0960GE51 R0710 182

 CENTRALINE LYNX TOOL - USER GUIDE

4. Select the Application or Macro from the Application/ • If the target controller is not a fresh device and
Macro/SBusWallModule list. This list displays the if any of the fixed NVs/Objects are exposed on
available applications, macros, or SBus wall modules in the wiresheet as points, the tool strips off
the library. matching NVs/Objects from the incoming folder
5. Type a name for the item you are loading. and the exposed points of those NVs/Objects
6. The Type and Version fields are not available for edit- are converted to invalid state. There is no effect
ing. The Version number is auto-generated. on the exposed fixed NV/Object points on the
7. The Attachment field displays the attachments saved target controller.
with the items you are loading, if any.
— The LonLYNX tool checks for UNVT name clashes.
8. Click OK to load the items to the macro/application. The
The tool generates a unique UNVT name for those
newly loaded items are displayed in the Nav palette to
incoming NVs whose structure matches with UNVT
the application/macro.
name clashes with existing NVs.
— If the target controller is a fresh device, then analog
NOTE: When an application is imported from a library:
output type (Current or Voltage) of the incoming AOs
(if any) would be the default type. That is, any new AO
— The application is added as a subfolder at that level in
that is dragged onto the wiresheet in the station has
the target.
the analog output type set to be same as that set for
— The NVs/Objects with name clashes are removed and
incoming AOs.
its exposed points if any, are converted to invalid
— When loading from a library, PX files are also copied to
points.
the Station and can be accessed in the Station.
— If the IO being imported has no pin assigned, the tool
— Attachments can exist only in the library. They can not
assigns a pin to the IO, if available. If no pin is avail-
be created or loaded from the library in Station. If you
able, the IO is imported as an invalid IO.
try to load or drag the library item which contains an
— If the IO being imported has a pin already assigned,
attachment, then the attachment is discarded from the
the tool retains the pin if it (the pin) is free on the tar-
library item automatically.
get. If the pin has already been used on the target con-
troller, the tool reassigns a pin to the IO, if available. If
no pin is available, the tool unassigns the pin from the Delete Library items
IO (the IO is converted to an invalid IO).
You cannot delete a library using the CentraLine LYNX tool.
— If the IO being imported has a fixed IO configuration,
However, you can use the Windows mechanism to delete the
the tool assigns a fixed IO pin to the IO as per the tar-
library file stored on the computer. To delete a library, you can
get controller, if available. If not, the tool converts the
browse to the location where you have stored the library and
IO to a custom type and reassigns a free IO pin, if
use the Windows mechanism to delete the file.
available. If not available, the IO becomes an invalid
IO. However, you can delete items within a library.
— When an application is imported from a library to an To delete items in a library:
empty controller (fresh controller with no changes 1. Right-click the item(s) (device/macro/application) you
made to the logic), both the ControlProgram and the want to delete in the Library palette and click Delete.
imported application folder get the same GUID (Uni-
versal Unique Identifier).
— For the NVs/Objects whose NV/Object name, number
of fields, field names and network datatypes matches
that of fixed NVs/Objects on the target controller, the
tool does the following:
• If the target controller is a fresh device, the tool
strips off the fixed NV/Object from the
ControlProgram/Application folder of the target
controller. The matching NVs/Objects on the
target folder are marked as fixed.
• If the target controller is not a fresh device,
matching fixed NVs/Objects on the incoming
folder are stripped off. Any incoming fixed NV/
Object points that are exposed on the incoming
folder are remapped to point to the fixed NVs/
Objects on the target controller logic (provided
the fields configuration, including the value and
the internal data type are matching).
2. A confirmation message is displayed. Click OK to delete
the item from the Library.

Export Library Items

You can export items in a library to another file for purposes of
distribution. To export items in a library:

183 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

1. Click the options button on the library palette to get a

drop-down list and select Export. The Export to File
dialog box appears with all the items in the library listed.

NOTE: You can also add SBus wall module to your applica-
tion logic and import the same to a library only if you
are using the LonLYNX II, LYNX Micro, or BacnetL-
2. Select the items on the list you want to export. A check YNX models.
mark appears across each item you have selected.The
File Path field displays the default location, the Niagara
installation folder (Example: C:\...\niagara 3.2.16.2\). LYNX Library Applications
Make sure that you are choosing those items that are The applications and macros created and saved to the library
not modified. If for any reason, you have chosen an item are stored in the Application(s) folder in the library.
that is modified, you must save it before exporting it. If Application(s) is one of the default folders in every library.
you attempt to export an item that is modified but not
saved, an error message appears. You must save the To create a new application in the library:
items before you export. 1. Click the options button in the LYNX Library sidebar. A
3. Select the browse button to display the File Chooser list of options appear.
dialog box. 2. Select New > Application. The Application Name dia-
4. Browse through to the folder to which you want to log box appears.
export these library items and click Save. 3. Type the name of the application in the Application
5. Click OK to export the file to the desired folder. Name dialog box.
4. Click OK. An application with the given name is created
in the Application(s) folder in the library.
Import items to Library 5. Expand the Application(s) folder on the left pane to
You can import items such as a device/macro/application to a view the application file of the application you just now
library from an exported file. created.
6. Expand the application file under the Application(s)
To import items to a library:
folder on the left pane to view the application you just
1. Click the options button on the library palette to get a now created.
drop-down list and select Import. The File Chooser
dialog box appears.
To add any LYNX object such as an application, macro,
2. Browse through to the file you want to import to this
physical IO, software IO, Function block to the application in
library and click Open. The items are imported to the
the library:
library.
1. Browse to the application by clicking Station > Drivers >
NOTE: If the import fails, an error message appears giving LonNetwork > LonLYNX > ControlProgram
you the following details: or
Station > Drivers > BacnetNetwork > BacnetLYNX >
— An item of the same name already exists. You must ControlProgram in the Nav sidebar.
rename the library object and import again. 2. Right-click any LYNX object such as application, macro,
— An item with the same logic already exists. You must device, FB, or IO in the Palette sidebar and select Copy.
delete the similar object(s) in the destination library 3. Right-click the application in the LYNX Library sidebar
and import again. and select Paste.
or
Drag the object to the wiresheet of the application in the
LYNX Library sidebar. The application, macro, device,
FB, or IO appears on the wiresheet of the application.
Note:

EN2Z-0960GE51 R0710 184

 CENTRALINE LYNX TOOL - USER GUIDE

— When a software IO in Lon such as NVI, NCI, or NVO Application Conversion - Lon Applications to
is added to the wiresheet, an NV is created in the NV
Configuration View. The corresponding backend BACnet and vice-versa
object is created in the Object Configuration View.
— When a software IO in Bacnet such as Network Inputs, LON TO BACNET
Network Setpoints, or Network Outputs is added to the If an application created under Lon LYNX device is dropped
wiresheet, a backend object is created in the Object onto a BACnet LYNX device:
Configuration View. The corresponding NV is created 1. Lon network interface will be removed and BACnet net-
in the NV Configuration View. work interface will be added.
— When a Bacnet software input of type Constant is 2. All Lon Network Variables will be removed.
added to the wiresheet, no backend object or NV is 3. BACnet objects will be created for all the points on the
created. wiresheet
— When a physical input of type Modulating Input is a. If the point on the wiresheet is of type Modulating
added to the wiresheet, a backend object -AI, as well Input, a corresponding AI object and an UICalOffset
as a reference object -UICalOffset are created in the object will be created.
Object Configuration View. There is no NV created for b. If the point on the wiresheet is of type Network
the physical point in the NV Configuration View. Setpoint and if it corresponds to a field of nci-
— When a physical IO such as Binary Input, Binary Out- UICalOffset, then the tool will do the following
put, or Modulating Output is added to the wiresheet, a automatically:
backend object is created in the Object Configuration (1) Create Modulating Input (MI) only if MI with the
View. There is no NV created for the physical point in same terminal number as the exposed point is
the NV Configuration View. not available in the BACnet device. If the BAC-
net device already has an MI with the same ter-
minal number, the tool will not create a new MI.
(2) Create the corresponding AI object and
UICalOffset object for the newly created MI.
c. If the point is of type Modulating Output, Binary
Input, or Binary Output the corresponding BACnet
object will be created by the tool.
d. If the point is of type Network Input and if it is
attached to nviTimeSet, the tool will automatically
map the exposed point to the corresponding
DEV_DeviceObject field.
4. If the logic has a TemperatureSetpointCalculator block,
6 BACnet objects will be created (only if the BACnet
device does not already have one) representing the set-
point values of the block.

LON TO LIBRARY APPLICATION

If an application created under Lon device is dropped onto the
Library application:
1. BACnet network interface will be added.
2. BACnet objects will be created for all points on the
wiresheet.
a. If the point is of type Modulating Input (MI), AI and
UICalOffset objects will be created. If the BACnet
device has any free terminal, MI added to BACnet
device will be assigned to that terminal. If the BAC-
net device does not have any free terminal, the MI
will remain unassigned.
b. If the point is of type Network Setpoint and if it is
attached to nciUICalOffset, the tool will do the fol-
lowing automatically.
(1) Create Modulating Input (MI) only if MI with the
same terminal number as the exposed point is
not available in the BACnet device. If the BAC-
net device already has an MI with the same ter-
minal number, the tool will not create a new MI.
(2) Create the corresponding AI object and
UICalOffset object for the newly created MI.
c. If the point is of type Modulating Output, Binary
Input, or Binary Output, the corresponding BAC-
net object will be created by the tool.
d. If the point is of type Network Input and if it is
attached to nviTimeSet, the tool will automatically
map the exposed point to the corresponding
DEV_DeviceObject field.

185 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

3. If the logic has a TemperatureSetpointCalculator block, 1. Browse to application in the Application(s) folder in the
6 BACnet objects will be created (only if the BACnet LYNX Library sidebar.
device does not already have one) representing the set- 2. Right-click the application and select Views.
point values of the block. 3. Select Wiresheet to view the LYNX objects such as
application, macro, device, FB, or IO in the Application
BACNET TO LON Library.
If an application created under BACnet LYNX device is 4. Right-click any physical IO or software IO on the
dropped onto the Lon LYNX device: wiresheet and select Configure Properties. The Con-
1. BACnet network interface will be removed and Lon net- figure Properties dialog box appears.
work interface will be added. 5. Click Advanced. The Advanced dialog box contains
2. All BACnet objects will be removed. the two tabs Bacnet Object and Lon NV.
3. Lon objects will be created for all points on the
wiresheet NOTE: The version of the tool installed must support both
a. If the point is of type Network Setpoint and if it is Lon and Bacnet to be able to view the two tabs in the
attached to UICalOffset object, the tool will automat- Advanced dialog box.
ically map the exposed NetworkSetpoint to the nci-
UICalOffset field based upon the terminal number If a Lon application is dragged onto the wiresheet of a Bacnet
used by the corresponding Modulating Input. device then,
b. If the point is of type Network Input and if it is — All the Lon NVs that appear on the wiresheet are con-
attached to DEV_DeviceObject, the tool will auto- verted to the corresponding Bacnet objects. During the
matically map the exposed point to the corre- conversion, the network data type of all points are
sponding nviTimeSet field. removed.
4. If the logic has a TemperatureSetpointCalculator block, — The backend objects are created for the points on the
the network variable nciTempSetpoints will be created wiresheet of the Bacnet device.
(only if the Lon device does not already have one) rep- — The assignment of pins in the Terminal Assignment
resenting the setpoint values of the block. View are also corrected. If the Bacnet device has
fewer terminal, then the physical points are unas-
BACNET TO LIBRARY APPLICATION signed.
If an application created under BACnet device is dropped onto
the Library application: If a Bacnet application is dragged onto the wiresheet of a Lon
1. Lon network interface will be added. device then,
2. Lon objects will be created for all the points on the — All the software points that appear on the wiresheet of
wiresheet. the Bacnet application are converted to the corre-
a. If the point is of type Network Setpoint and if it is sponding Lon NVs. The physical points on the
attached to UICalOffset object, the tool will automat- wiresheet are mapped to the fixed NVs. During the
ically map the exposed NetworkSetpoint to the nci- conversion, the network datatype of all points are
UICalOffset field based upon the terminal number mapped to a standard NV type (SNVT).
used by the corresponding Modulating Input.
b. If the point is of type Network Input and if it is NOTE: For tools supporting both Lon and Bacnet:
attached to DEV_DeviceObject, the tool will auto-
matically map the exposed point to the corre- — When you save an application to library from a Lon
sponding nviTimeSet field. Network, backend Bacnet objects are created for the
3. If the logic has a TemperatureSetpointCalculator block, points on the wiresheet. Backend objects are not cre-
network variable nciTempSetpoints will be created (only ated for mandatory and fixed NVs.
if the Lon device does not already have one) represent- — When you save an application to library from a Bacnet
ing the setpoint values of the block. network, the points are shown as invalid in the NV
Configuration View.
Viewing and Editing Bacnet Objects and Lon NVs — When a Lon NV is created in the NV Configuration
1. Browse to the application in the Application(s) folder in View, the corresponding Bacnet object is automatically
the LYNX Library sidebar. created only when the Lon NV is shown on the
2. Right-click the application and select Views. wiresheet as point.
3. Select NV Configuration View to view the Lon Network — When a Bacnet object is created in the Object Config-
Variables available on the wiresheet of the application. uration View, the corresponding Lon NV is automati-
or cally created only when the Bacnet object is shown on
Select Object Configuration View to view the Bacnet the wiresheet as point.
Objects available on the wiresheet of the application. — When a point is added to the wiresheet, the corre-
sponding Lon NV and Bacnet Object is created with
the default settings.
The configuration properties of the physical and software IOs — If the configuration details of the point on the wiresheet
in the application library now enables you to edit the points for is modified, the changes are applied to both Lon and
both the network interfaces. The Advanced option under Bacnet.
Configure Properties contains the two tabs, Bacnet Object — Changing Bacnet object details such as GPU, Fail
and Lon NV. Detect, Update Rate, or Sen Delta does not affect the
To edit the physical and software IOs in the application library: corresponding NV.

EN2Z-0960GE51 R0710 186

 CENTRALINE LYNX TOOL - USER GUIDE

MODES OF OPERATION
The different modes of operation in the CentraLine LYNXTool Simulation Mode: Use this mode to simulate the working of
include: your ControlProgram. You can test the working of the
Engineering Mode: Use this mode to build application logic. ControlProgram you create before downloading it to the
In this mode, you can perform engineering operations such as controller. You can give values to NVs or Bacnet Objects and
logic creation, linking of blocks, exposing fields of blocks, Physical points and view the calculated output values.
macros, Physical points, and so on.
Online debugging Mode: In this mode, you can debug the Accessing Different Modes
application after downloading it to the controller. You can
select the points that need to be debugged. You can force
debug points and watch the true picture of the values that get Pre-requisites
executed in the controller. • Network with CentraLine LYNX controllers.
• CentraLine LYNX Tool is licensed.
• The programmed logic is downloaded to the controller
(This is applicable only to debug points and not to
Engineering and Simulation).

187 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

ENGINEERING MODE
This is the mode you work in to perform engineering For a detailed discussion of how to perform the engineering
operations such as creating a ControlProgram, creating operations mentioned above, see ControlProgram Wiresheet
macros, creating LYNX libraries, linking blocks, selecting View.
points to debug, force write points to controller, and so on.

EN2Z-0960GE51 R0710 188

 CENTRALINE LYNX TOOL - USER GUIDE

ONLINE DEBUGGING MODE

Use the Online Debugging mode to debug the output points of
Functional Blocks, Network Inputs/Network Setpoints (NVIs
and NCIs in LonLYNX, Analog Value Objects, Binary Value
Objects, and Multi-state Value Objects in BacnetLYNX, and
physical input points such as binary inputs and modulating
inputs) in the online mode. You can force write points to NVs
or Objects and observe field values. You can also select the
points (in an application) you want to debug. The prerequisites
to work in this mode include, creation of an application logic
and downloading it to the controller.
To be able to debug function blocks, they must be linked to
other function blocks or output points or configured as
Out_Save, Out_Byte, Out_float, or constant. An exception,
however, is the Alarm function block. If you have an Alarm
function block with only its input linked, you can still perform
debugging.
To be able to debug input points (NVIs or Network Inputs,
NCIs or Network Setpoints, analog inputs, and binary inputs),
they must be linked to function blocks or other output points.
The points you select for debugging and with the view in the
watch window option enabled appear in the watch window at
the bottom of the wiresheet. Use the watch window if the
points you want to watch are scattered between macros and
sub-application logic. In such a situation, you do not have to
view the container containing the point. You can use the The Debug button on the tool bar becomes unselectable and
Watch Window feature to watch the values of all the points you have the following options available: 
you selected, irrespective of where they are or are not on the
wire sheet. • Force Values: To Force write your
In the Debug mode you can: 
own values to Software input points (Network Inputs,
• Force Values Network Setpoints). 
• Select Points to debug 
• Start debugging points
• Select Point :To select the points
Working in Online Debugging Mode 
You can access the Online Debugging Mode from either the you want to debug. The selected points appear in the
Engineering or Simulation mode with the click of a button. To Watch Window with the field values.
move to Online Debugging Mode from any mode: 
Click on the Tool bar
• Stop: To stop debugging and access the
or 
Right-click anywhere on the wiresheet and select Debug engineering mode. 


• Simulate: To enter the simulation mode. 




• Simulation Setup: To choose a Simulation Setup


type. If you click this button in the Online Debugging
Mode, the Simulation Setup dialog box appears and you
can choose a simulation setup type. However, the
changes are only saved and are effected only when you
move to the Simulation mode.

189 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

Download Application Logic to Controller

To download an application logic to a controller:
Action Result
After you have created your application logic and tested the
logic using the simulation feature, you can download the Add/remove a block Not allowed
application logic to the controller. To download the application Add/remove a link Not allowed
logic: Rename/Reorder a component (function Not allowed
1. In the Nav palette, right-click the device and select block, physical/software points, composite
Actions > Download. The Download dialog box slots, macros, applications, controlprograms,
appears. device)
Point Conversion Not allowed
All configuration changes for function blocks Not allowed
except Property description change and
Output property type change
Change Constant value through Config Not allowed
properties and NOT through Force values/
Actions screen
Change Network Setpoint value through Not allowed
Config Properties dialog and not through
Force values/Actions screen
Change Schedule configuration Not allowed
Change Property description of function block Allowed
Change Simulation settings Allowed
Change Model Not allowed
Reassign/Unassign IO terminals in Terminal Not allowed
Assignment View
Change Daylight settings in Controller Not allowed
Summary View
Import XML Not allowed
Change IO configuration Not allowed

2. The Download dialog box appears. Click OK to down-

load the logic to the controller. Changing Modes
On changing the mode from Engineering/Online Debugging to
NOTE: A Quick Download only downloads the modified Simulation the message, “Do you want to remove the
items from a previous download where as with a Full overridden input points?” message appears.
Download the entire configuration is downloaded to
the controller replacing the existing configuration. NOTE: If you select Yes:
However, if changes have been made to the SBus
wall module by an operator or tenant locally from the — For Network Inputs, Override values is removed in the
display on the wall module, and a full download is tool and values in the controller temporarily remain
performed, LYNX tool downloads the entire configu- until updated.
ration to the controller except the SBus wall module — For Software Constants (NetworkConfigs) in LonL-
configuration. This is done to avoid losing any YNX, and Network Setpoints in BacnetLYNX, Override
changes made locally on the SBus wall module dur- values except the values that have been Set are
ing the download. Make sure that if you are using the removed and the Set value is retained in the controller
SBus wall module, the models selected are LonL- and in the tool.
YNX II, LYNX Micro, or BacnetLYNX. When using
the LonLYNX and BacnetLYNX models, if you modify NOTE: If you select No:
SBus wall module settings from the display in the
wall module, you can also upload the same configu- — For Network Inputs, Override values are retained in
ration into the LYNX tool.  the tool and values in the controller temporarily remain
SBus wall module cannot be downloaded to the Lon- until updated.
LYNX I models. — For Software Constants (NetworkConfigurations) in
LonLYNX, and Network Setpoints in BacnetLYNX, the
Override value are taken as the Set value and all the
Modify Application During Debugging overridden values are removed and values in the con-
You can modify the application logic even when debugging of troller temporarily remains until updated.
points is going on. The following table summarizes the actions — Selecting Yes may take several minutes depending on
and their effects on points in the debugging mode. the number of wiresheet objects.

EN2Z-0960GE51 R0710 190

 CENTRALINE LYNX TOOL - USER GUIDE

NOTE: Whenever you restart a Station, by default, the NOTE: If you select No:
actions described on selecting No, is performed.
— For Network Inputs, Override values are retained in
NOTE: On changing the mode from Engineering to Online the tool and values in the controller temporarily remain
Debugging or vice-versa, the message, "Do you until updated.
want to remove the overridden input values?" — For Software Constants (NetworkConfigurations) in
appears. LonLYNX, and Network Setpoints in BacnetLYNX, the
Override value are taken as the Set value and all the
NOTE: If you select Yes: overridden values are removed and the new Set value
is retained in the controller and in the tool.
— ForNetwork Inputs, Override values are removed in — Selecting Yes may take several minutes depending on
the tool and values in the controller temporarily remain the number of wiresheet objects.
until updated.
— For Software Constants (NetworkConfigs) in LonL- NOTE: Whenever you restart a Station, by default, the
YNX, and Network Setpoints in BacnetLYNX, Override actions described on selecting No, is performed.
values except the values that have been Set are
removed and the Set value is retained in the controller
and in the tool.

191 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

Example
1. Create an application logic in the Engineering Mode.

EN2Z-0960GE51 R0710 192

 CENTRALINE LYNX TOOL - USER GUIDE

2. Download the logic to the controller.

193 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

3. Click OK

EN2Z-0960GE51 R0710 194

 CENTRALINE LYNX TOOL - USER GUIDE

• Download in progress appears in the Job palette.

195 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

• A download success message appears.

EN2Z-0960GE51 R0710 196

 CENTRALINE LYNX TOOL - USER GUIDE

4. Click the Debug button.

197 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

• The Watch window appears.

EN2Z-0960GE51 R0710 198

 CENTRALINE LYNX TOOL - USER GUIDE

5. Select points you want to view in the Watch Window

and click OK.

199 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

• The values of the selected points appear in the watch

window.

EN2Z-0960GE51 R0710 200

 CENTRALINE LYNX TOOL - USER GUIDE

201 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

6. Force points of NVs.

EN2Z-0960GE51 R0710 202

 CENTRALINE LYNX TOOL - USER GUIDE

203 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

• The new values after force writing points appear.

EN2Z-0960GE51 R0710 204

 CENTRALINE LYNX TOOL - USER GUIDE

7. Click Stop to end debugging.

205 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

• The Engineering Mode appears.

EN2Z-0960GE51 R0710 206

 CENTRALINE LYNX TOOL - USER GUIDE

FORCE VALUES
1. By forcing values to input points, you can test the appro- for physical points, and software points configured as
priateness of the application logic that you create. You constant. They are available only in the Simulation
can verify if the output values return desired values. If mode.
there are discrepancies you can fine tune your logic by
forcing values by trial and error to generate the desired NOTE: To force write all points that are exposed on the
output. wiresheet, you can right-click the points on the
1. In the Engineering mode, the values you force are not wiresheet and use the Force Values option.
written to the controller but are stored in the CentraLine You cannot force write values to any point of a logic
LYNX tool. However, in the Online debugging mode, the in an Application library.
values you force are written to the controller and stored
in the tool. The CentraLine LonLYNX tool does not support forcing values
1. You can force values to each field of Software point to a Many-to-one NVI. You can use the Bindings feature to
(Network Inputs and Network Setpoints), in the Engi- test the Many-to-one NVI.
neering and Online debugging modes. However, in To force write points to the controller:
these modes, the Force values option is not available
1. Right-click the NV/Object you want to force value to,
and select Force Values. In this case you see only the
selected point.
Alternatively, click the Force Values button on the tool-
bar. The Forced Values dialog box appears. In this
case, you see all points, that you can force values to, on
the wiresheet. The following table defines the fields
shown in the dialog box.

Name Definition
Input Point Name Shows all the software points. It is non-editable.
Mode You can select the following options for the points as mentioned:
• Network Input:
— Emergency Override: Emergency Override has the highest priority and value written through
Emergency override is assigned to the point.
— Emergency Auto: Use this option to remove the Emergency Override from the tool. In this case,
the point is assigned a value based on the values defined by Override or Set, depending on
whichever is defined. If both are defined, Override has the higher priority.
— Override: This has the second highest priority. A point is assigned this value if Emergency Auto
is selected and the Override value is already defined.
— Auto: Use this option to remove the Override option from the tool. Auto clears off the Override
state of the point and the point is assigned the Set value.
— Set: This has the least priority. A point is assigned this value if Auto is selected and the Set value
is already defined.
— Clear Set: Use this option to cancel the Set value.

NOTE: Auto or the previously set mode is the default mode displayed.

Network Setpoint:
— Emergency Override: Emergency Override has the highest priority and value written through
Emergency override is assigned to the point and incase of online debugging it goes down to the
controller.
— Emergency Auto: Use this option to remove the Emergency Override. In this case, the point is
assigned a value based on the values defined by Override or Set, depending on whichever is
defined. If both are defined, Override has the higher priority.
— Override: This has the second highest priority. A point is assigned this value if Emergency Auto
is selected and the Override value is already defined.
— Auto: Use this option to remove the Override option. Auto clears off the Override state of the
point and the point is assigned the Set value.
— Set: This has the least priority. A point is assigned this value if Auto is selected and the Set value
is already defined.

NOTE: Set or the previously set mode is the default mode displayed
Units This is editable only when the Mode is Emergency Override, Override or Set. It shows the unit you
selected.

207 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

Value This is editable only when the Mode is Emergency Override, Override or Set. It shows the value that
you want to write to the controller.

NOTE: You can force write invalid values to a point by keying in alphabets. Such an invalid value is
displayed as Nan. Any value outside the specified range is also considered invalid. For exam-
ple, if the lower range is 0 and the upper range is 20, values such as 21 or -1 are considered
invalid.
Upper Range This is non-editable. It shows the upper limit of the Network Variable.
Lower Range This is non-editable. It shows the lower limit of the Network Variable.
Select point path Indicates the location of the component. It is a relative and not an absolute path
Select point ord Indicates the absolute path. It can be used to resolve the component.
Clear All Invoke this option to put all the points to the default state.
For an NVI, this sets mode to Auto (i.e value = Null or to the current value in the controller)
For an NCI, this sets the mode to Set with its value.
OK Saves the entered information and closes the dialog box.
Cancel Closes the dialog box. Any information entered is lost.
An explanation of the actions allowed in the Online Debugging
2. Click OK to close the dialog box. The value, in the mode follows:
Online Debugging mode, is directly written to the con- • Emergency Override: Emergency Override has the
troller. highest priority and value written through Emergency
override is assigned to the point and incase of online
NOTE: Many to one NVs in LonLYNX and physical IOs will debugging it goes down to the controller.
be cleared on moving to the online debugging mode, • Emergency Auto: Use this option to remove the
always. Emergency Override from the tool. In this case, the point is
assigned a value based on the values defined by Override
or Set, depending on whichever is defined. If both are
Actions defined, Override has the higher priority.
Use the Actions options to quickly force values to Network • Override: This has the second highest priority. This has
Input points. You can use these options to set values based the second highest priority. A point is assigned this value if
on the priority: Emergency Override > Override > Set. Emergency Auto is selected and the Override value is
Right-click the point on the wiresheet and select Actions to already defined.
get to this option. • Auto: Use this option to remove the Override option from
the tool. Auto clears off the Override state of the point and
NOTE: The Actions option is not available for physical the point is assigned the Set value.
points, software points configured as constant in • Set: This has the least priority. A point is assigned this
Online Debugging and Engineering modes, and in value if Auto is selected and the Set value is already
LonLYNX, Many-to-one NV in Online Debugging defined.
mode. They are available only in the Simulation
mode. NOTE: The value written to an Network Setpoint using the
Set option changes the configuration of the point.
That is, the value configured for the Network Set-
point can also be changed using the Set option in
both Online Debugging and Simulation.

EN2Z-0960GE51 R0710 208

 CENTRALINE LYNX TOOL - USER GUIDE

SELECT POINTS TO DEBUG

NOTE: A many to one Network Input cannot be selected for 4. Select the check box of the point you want to view in the
debugging. watch window.

To select points that you need to debug:  NOTE: Use the Select All option to select all points selected
for debugging to be displayed in the watch win-
1. Click the button. The Select Points dialog box dow.You can use the left arrow button to remove the
 selected points to the Select Output Points list. This
appears. The following table defines the fields shown in removes the points from being selected for debug-
the dialog box. ging or from being shown in the watch window. If you
select All in the Select Function Blocks list and
Name double-click it, all points are shown in the third col-
Definition umn with the watch window option checked.
Select Shows all the Function Blocks, SBus wall
Function module, Conventional wall module, Physical 5. Click OK. The points appear in the watch window.
Block IOs, Network Variables, Bacnet Objects, and
Network Inputs that are not constants that View Values in Watch Window
have output points and are connected to You can select points for debugging in the Engineering and
other functional blocks or network variables. Online Debugging modes. However, the selected points are
It also displays all OUT parameters of both displayed, in a watch window at the bottom of the wiresheet,
SBus and conventional wall modules. only in the Online Debugging or Simulation modes. Use this to
Select Shows all the output points of selected analyze your application logic and to find the field values
Output Function Blocks, SBus wall module, being returned based on the logic you have defined.
Points Conventional wall module, Physical I\O, To hide/display the watch window:
Network Variables, Bacnet Objects, and
• Select Wire Sheet > Watch Window in the Menu bar or
Network Inputs that are not constants and are
right click on the wiresheet and select Watch Window.
connected to other functional blocks or
network variables.
Watch Shows the selected output points that appear
Changes in Select Points Screen On Changing
Window/ in the watch window. You must select the Modes
option to view points in watch window check 1. If you select a point for debugging & check the watch
box to be able to see the values in the watch window option in Engineering/Online Debugging mode,
window. the same is retained in Simulation mode.
Point Name Shows the values of the output points in the 2. If you select a point for debugging & uncheck the watch
watch window. window option in Engineering/Online Debugging mode,
the same is not retained in Simulation mode.
Select point Indicates the location of the component. It is 3. If you select a point in the Simulation mode, the same
path a relative and not an absolute path point is retained in the Engineering/Online Debugging
Select point Indicates the absolute path. It can be used to mode with watch window enabled.
ord resolve the component. 4. If a point selected for debugging & not for watch window
in the Engineering/Debugging mode is selected in the
OK Saves the selected points to be debugged
Simulation mode, the point will be retained in the Engi-
and closes the dialog box.t
neering/Debugging mode with watch window enabled.
Cancel Closes the dialog box. Any operation done so 5. If you add and remove a point in the Simulation mode,
far is cancelled. the same point is displayed as selected for debugging
but not for watching in the Engineering/Online Debug-
ging mode.
2. Select the Function Block or Network Variable from the 6. Select a point in Simulation mode. Move to the Engi-
Select Function Block section. The output points are neering/Debugging mode and select the point for both
shown in the Select Output Points section. debugging & watching. Now, remove the option for
3. Select the output points that you want to view. The watching. Move to the Simulation mode. The point will
selected points appear in the Watch Window / Point not be shown in the simulation mode.
Name section.

209 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

SIMULATION
CentraLine LYNX provides the Simulation feature that enables
you to simulate the working of your ControlProgram. Use the • Stop: To stop debugging and access the
Simulation Mode to test the working of the ControlProgram.
You can give values to Software points (Network Inputs, engineering mode.
Network Setpoint), and Physical points.
You can also force write points to the controller and
understand the behavior of the application with the values you • Pause: To temporarily halt the simulation.
enter and the effect it has on other points.

NOTE: You can simulate application logic with SBus wall • Resume: This button becomes selectable only
module irrespective of the model selected. The fol-
lowing LYNX models support SBus wall module. when you have paused the simulation. If you click the
Resume button, it becomes disabled and will be available
— LYNX II models: CLLYVL6436AS, CLLYVL6438NS, or
CLLYUL6438S only after pressing the Pause button.
— LYNX Micro models: CLLYVL4024NS,
CLLYVL4022AS, CLLYUL4024S, CLLYUL1012S, or
CLLYVL0000AS Modify Application During Simulation
— LYNX Bacnet models: CLLYVB6436AS, You can modify the application logic even when simulation is
CLLYVB6438NS, or CLLYUB6438S going on. The following table summarizes the actions and
You can also simulate the SBus wall module logic alone using
their effects on points in the Simulation mode.
the Preview feature available in the SBus wall module wizard
screen.
Action Result
Working in Simulation Mode
Add/remove a block Not allowed
You can access the Simulation Mode from either the
Engineering or Online Debugging Mode with the click of a Add/remove a link Not allowed
button. To move to Simulation Mode from any mode: Rename/Reorder a component (function Not allowed
Click on the Tool bar block, physical/software points, composite
or slots, macros, applications, controlprograms,
Right click anywhere on the wiresheet and select Simulate device)
The Simulate button on the tool bar becomes unselectable Point Conversion Not allowed
when you move to the Simulation mode and you have the All configuration changes for function blocks Not allowed
following options available: except Property description change and
• Force Values: To Force write your own values to Output property type change
Change Constant value through Config Not allowed
Software input points (Network Inputs, Network Setpoints).
properties and NOT through Force values/
Actions screen
• Select Point: To select the points you want to Change NCI value through Config Properties Not allowed
dialog and not through Force values/Actions
debug. screen
Change Schedule configuration Restart
• Simulation Setup: To choose a Simulation Change Property description of function block Allowed
Change Simulation settings Allowed and
Setting. If you click this button in the Online Debugging
Simulation
or Engineering Mode, the Simulation Settings dialog restarts
Change Model Not allowed
box appears and you can choose a simulation setting.
Reassign/Unassign IO terminals in Terminal Not allowed
However, the changes are only saved and are effected Assignment View
only when you move to the Simulation mode. If you click Change Daylight settings in Controller Restart
Summary View
this button in the Simulation Mode, the current simulation Import XML Not allowed
type is overridden by the new selection and the options you Change IO configuration Allowed
have chosen are lost.

EN2Z-0960GE51 R0710 210

 CENTRALINE LYNX TOOL - USER GUIDE

Change Modes NOTE: If you select No:

NOTE: On changing the mode from Simulation to Engineer- — For Network Inputs,"Override" values are retained in
ing/Online Debugging, the message, "Do you want to the tool; and the values in the controller temporarily
remove the overridden input point values?" message remain until updated.
appears. — For Software Constants (NCI) in LonLYNX, and Net-
work Setpoints in BacnetLYNX, the Override value are
NOTE: If you select Yes: taken as Set value and all the overridden values are
removed; and values in the controller temporarily
— For Network Inputs,"Override" values are removed in remain until updated.
the tool and the values in the controller temporarily — Selecting Yes may take several minutes depending on
remain until updated. the number of wiresheet objects.
— For Software Constants (NCI) in LonLYNX, and Net-
work Setpoints in BacnetLYNX, Override values NOTE: Whenever you restart a Station, by default, the
except the values that have been Set are removed actions described on selecting No, is performed.
and the Set value are retained in the controller and in Always, Many to one NVs in LonLYNX, and physical
the tool. IOs are cleared on moving to the online debugging
mode.

211 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

Example Scenario
The entire simulation operation is explained with the aid of an
example.
• Create an application logic.Click the Simulate button.

EN2Z-0960GE51 R0710 212

 CENTRALINE LYNX TOOL - USER GUIDE

213 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

EN2Z-0960GE51 R0710 214

 CENTRALINE LYNX TOOL - USER GUIDE

• Select the points you want to display in the Watch Window

by clicking the button. Select the points you want and click
OK.

215 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

• The points you have selected are displayed with their

values in the Watch Window.

EN2Z-0960GE51 R0710 216

 CENTRALINE LYNX TOOL - USER GUIDE

7. Click the button to select a Simulation Type.


The Simulation Setup button appears. Continuous
Simulation is the default selection. Enter the details and
click OK.

217 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

• or select the Step Simulation option. Enter the details and

click OK.

EN2Z-0960GE51 R0710 218

 CENTRALINE LYNX TOOL - USER GUIDE

• or select the Time Simulation option. Enter the details and

click OK.

219 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

• A confirmation message is displayed. Click Yes.

EN2Z-0960GE51 R0710 220

 CENTRALINE LYNX TOOL - USER GUIDE



Till the simulation is completed, the is enabled and the 


Resume button is disabled.

221 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

After the simulation is complete the Pause button is disabled


and the Resume button is enabled.

EN2Z-0960GE51 R0710 222

 CENTRALINE LYNX TOOL - USER GUIDE

• Click the Force Inputs button to force write Physical point

values.

223 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

• The values appear in the Watch window.

EN2Z-0960GE51 R0710 224

 CENTRALINE LYNX TOOL - USER GUIDE

• Click Stop to return to the Engineering Mode.

225 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

EN2Z-0960GE51 R0710 226

 CENTRALINE LYNX TOOL - USER GUIDE

SIMULATION SETTINGS
The CentraLine LYNX has three Simulation Types that you
can make use of for testing the applications you create:
Continuous Simulation
Use this simulation type to simulate your application
• Time Simulation continuously. The output values are calculated continuously
• Continuous Simulation until you end the simulation. To select the Continuous
• Step Simulation Simulation type:
You can also choose to simulate at two speeds:
1. Click . The Simulation Setup dialog box
• Simulate as fast as possible: Select this option to choose
to simulate at the fastest possible time. In this case, the appears.
simulation may be executed at speeds greater than the
usual 1 second per loop. 2. Select Continuous Simulation.
• Simulate at the speed of the controller: Select this 3. The Time Period is disabled and you cannot modify it.
option to choose to simulate at the speed of the controller, 4. Select the Set Start Time As option to modify the date
which is at the rate of 1 second per loop. and time. You can modify the Date, Month, Year, Hour,
Minute, AM/PM by clicking it and use the up and down
NOTE: If you change simulation settings when you are in the arrows on your keyboard. This option enables you to
Simulation mode, the current simulation is restarted define (not set) the starting time of the simulation. 
to reflect the changes you make. However, if you Example: If you want to simulate an application logic in
make changes to Simulation Settings in the Engi- another timezone at 00:00 hours, you can select the
neering or Online Debugging modes, the settings are timezone and hours and minutes. The start time of the
saved and take effect the next time you enter simula- simulation is taken as 00:00 hours although the simula-
tion mode. tion itself begins once you click the OK button.
5. Click OK save the changes you have made. The simu-
lation of your application begins and the values of all
Time Simulation Physical Points/NV points and function blocks are dis-
Use this simulation type to simulate your application for a played on the wiresheet. Additionally, if you have
specified time period. The output values are calculated selected points to be displayed in the Simulation Log
continuously until the specified time period is reached. To Window, the values of such points are displayed in the
select Time Simulation type: Watch Window at the bottom of the wiresheet.
1. Click the button. The Simulation Setup dialog
NOTE: You can use the Pause and Resume
box appears.
buttons if you want to temporarily halt/resume the
2. Select Time Simulation.
simulation.
3. Enter the Time Period in Hours, Minutes, and Seconds.
This specifies the time period over which the CentraLine
LYNX Tool simulates the application logic. 6. Click the button to enter the Engineering Mode.
4. Select the Set Start Time As option to modify the date
and time. You can modify the Date, Month, Year, Hour, You can click the button to enter the Online
Minute, AM/PM by clicking it and use the up and down
arrows on your keyboard. This option enables you to Debugging Mode.
define (not set) the starting time of the simulation.
Example: If you want to simulate an application logic in
another timezone at 00:00 hours, you can select the Step Simulation
timezone and hours and minutes. The start time of the
Use this simulation type to simulate your application desired
simulation is taken as 00:00 hours although the simula-
number of steps at a time. In this simulation type, the
tion itself begins once you click the OK button.
application logic you have defined is simulated based on a
5. Click OK save the changes you have made. The simu-
specified number of steps. In each step, the values of the
lation of your application begins and the values of all
application logic is calculated once. To select the Step
Physical points/NV points and function blocks are dis-
Simulation type:
played on the wiresheet. Additionally, if you have
selected points to be displayed in the Simulation Log 1. Click . The Simulation Setup dialog box
Window, the values of such points are displayed in the
Watch Window at the bottom of the wiresheet. appears.
2. Select Step Simulation.
NOTE: You can use the Pause and Resume 3. Type the Number Of Steps.
4. Select the Set Start Time As option to modify the date
buttons if you want to temporarily halt/resume the
and time. You can modify the Date, Month, Year, Hour,
simulation. Minute, AM/PM by clicking it and use the up and down
arrows on your keyboard. This option enables you to
define (not set) the starting time of the simulation.
6. Click the button to enter the Engineering Mode.

227 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

— Example: If you want to simulate an application logic in values. If there are discrepancies you can fine tune your logic
another timezone at 00:00 hours, you can select the by forcing values by trial and error to generate the desired
timezone and hours and minutes. The start time of the output. You can use the Force Values option to force values
simulation is taken as 00:00 hours although the simu- on physical points, software points such as Network Inputs,
lation itself begins once you click the OK button. Network Setpoints and Constants, and Function blocks.
5. Click OK save the changes you have made. The simu- In the Simulation mode alone, you can override Functional
lation of your application begins and the values of all block outputs. Use the Force Values dialog box to display the
Physical Points/NV points and function blocks are dis- list of outputs of all functional blocks. You can also use the
played on the wiresheet. Additionally, if you have right-click menu to invoke the output of the selected function
selected points to be displayed in the Simulation Log block alone. You can reset the overridden values of functional
Window, the values of such points are displayed in the blocks using the Auto mode.
Watch Window at the bottom of the wiresheet.
NOTE: While forcing values to SBus wall module, value
NOTE: You can use the Pause and Resume from wall module and dynamic values which are not
connected to any input slot can be over ridden.
buttons if you want to temporarily halt/resume the
simulation. When any one functional block output is overridden, the other
outputs of that functional block also go into overridden state
and the mode of all the outputs of that functional block is
6. Click the button to enter the Engineering Mode. changed to Override state with a default value of Nan (invalid
value) for non-Enums and the first item for Enums.
You can click the button to enter the Online
Use the button to force the values of each field in an
Debugging Mode.
NV, Physical point, Constant, or function block. Alternatively,

Force Values right-click on the desired IO/NV/Function block and select

By forcing values to IOs, NVs or Objects, and Function blocks Force Value.
you can test the appropriateness of the application logic that
you create. You can verify if the output values return desired

EN2Z-0960GE51 R0710 228

 CENTRALINE LYNX TOOL - USER GUIDE

To force write points to the controller: ton on the toolbar. The Forced Input Screen dialog box
appears. In this case, you will see all points, that you
1. Right-click the IO/NV you want to force value to, and can force values to, on the wiresheet. The following
select Force Values. In this case you will see only the table defines the fields shown in the dialog box.
selected point.Alternatively, click the Force Values but-
Name Definition
Input Point Name Shows all the inputs and NVIs. It is non-editable.
Mode You can select the following options for the points as mentioned:
• Emergency Override: Emergency Override has the highest priority and value written
through Emergency override is assigned to the point.
• Emergency Auto: Use this option to remove the Emergency Override. In this case, the point
is assigned a value based on the values defined by Override, Sine/Cosine/Range or Set,
depending on whichever is defined. If all three are defined, Override has the higher priority
• Override: This has the second highest priority. A point is assigned this value if Emergency
Auto is selected and the Override value is already defined
• Auto: Use this option to remove the Override option. Auto clears off the Override state of the
point and the point is assigned the Sine/Cosine/Range value, if it is set.
• Set: This has the least priority. A point is assigned this value if Clear Sine/Cosine/Range
option is selected and the Set value is already defined.

NOTE: The value written to a Network Setpoint using the Set option changes the config-
uration of the point. That is, the value configured for the NCI point can also be
changed using the Set option in both Online Debugging and Simulation.

• Clear Set: Use this option to remove the Set value. Not available for NCI.
• Sine/Cosine/Range: This has the third highest priority. A point is assigned this value if Auto
is selected and the Sine/Cosine/Range value is already defined. The value that you specify
is written to In9 slot of the point so that it goes to the point out slot.
• Clear Sine/Cos/Range: Use this option to clear the Sine/Cosine/Range value. This option
removes the Sine/Cosine/Range value and assigns the Set value, if it is already defined.
Clear Set option is available for Network Inputs, Constants, and Physical inputs.

The value set to the Network Setpoint through either Override, Emergency Override or Sine/
Cosine/Range does not change the actual value configured for the point.

Units This is editable only when the Mode is Emergency Override, Override, Set, Sine, Cosine,
and Range. It shows the unit you selected.
This is not applicable o function blocks.

Value This is editable only when the Mode is Emergency Override, Override, or Set. It shows the
value that you want to write to the controller.

NOTE: You can force write invalid values to a point by keying in alphabets. Such an invalid
value is displayed as Nan. Any value outside the specified range is also considered
invalid. For example, if the lower range is 0 and the upper range is 20, values such as
21 or -1 are considered invalid.
Upper Range It shows the upper limit of the Network Variable. This is non-editable except for Sine, Cosine,
and Range.
Lower Range It shows the lower limit of the Network Variable. This is non-editable except for Sine, Cosine,
and Range.
Select point path Indicates the location of the component. It is a relative and not an absolute path
Select point ord Indicates the absolute path. It can be used to resolve the component.
Clear All Invoke this option to put all the points/Function blocks to the default state. NCIs/Network
Setpoints go back to their configured value, NVIs/Network Inputs go to null, function block
outputs go back to null.
OK Saves the entered information and closes the dialog box.
Cancel Closes the dialog box. Any information entered is lost.

2. Click OK to close the dialog box.

229 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

Actions 1. Click the Select Points button on the tool bar. The
Select Points to be displayed in the Simulation Log
Use the Actions options to quickly force values. You can use Window dialog box appears. The following table
these options to set values based on the priority: Emergency defines the fields shown in the dialog box.
Override > Override Sine/Cosine/Range > Set.
An explanation of the actions allowed in the Online Debugging
mode follows: Name Definition
• Emergency Override: Emergency Override has the Select Shows all the Function Blocks, Physical IOs
highest priority and value written through Emergency Function and Network Inputs, Network Setpoints,
override is assigned to the point and incase of online Block Physical inputs such as analog and digital
debugging it goes down to the controller. inputs that have output points and are
• Emergency Auto: Use this option to remove the connected to other functional blocks or
Emergency Override. In this case, the point is assigned a Network Output points.
value based on the values defined by Override, Sine/ Select Shows all the output slots of the selected
Cosine/Range or Set, depending on whichever is defined. Output components in the Select Function Block
If all three are defined, Override has the higher priority. Points list.
• Override: This has the second highest priority. The value
written through Override is assigned if it is already defined. Select point Indicates the location of the component. It is
• Auto: Use this option to remove the Override option. Auto path a relative and not an absolute path
clears off the Override state of the point and the point is Select point Indicates the absolute path. It can be used to
assigned the Sine/Cosine/Range value, if it is set. ord resolve the component.
• Set: This has the least priority. A point is assigned this Point Name Shows the points selected to be displayed in
value if Clear Sine/Cosine/Range option is selected and the watch window.
the Set value is already defined.
OK Saves the selected points to be debugged
NOTE: The value written to a Network Setpoint using the Set and closes the dialog box.
option changes the configuration of the point. That is, Cancel Closes the dialog box. Any operation done
the value configured for the Network Setpoint can so far is cancelled.
also be changed using the Set option in both Online
Debugging and Simulation. 2. Select the Function Block or Network Variable from the
Select Function Block section. The output points are
Right-click the point on the wiresheet and select Actions to shown in the Select Output Points section.
get to this option. 3. Select the output points that you want to view. The
selected points appear in the Point Name section.
4. Click OK. The points appear in the watch window with
Select Points to Display in Simulation Log the values.
Window
View Values in Watch Window
After you have selected points to be displayed in the
Pre-requisites Simulation Log Window, the points appear in a Watch Window
— To be able to simulate function blocks, they must be at the bottom of the wiresheet. Use this to analyze your
linked to other function blocks or output points or con- application logic and to find the values being returned based
figured as Out_Save, Out_Byte, Out_float, or con- on the logic you have defined.
stant. An exception, however, is the Alarm function
block. If you have an Alarm function block with only its NOTE: All points in the logic will be simulated. However, only
input linked, you can still perform simulation. those points for which you have enabled the View in
— To be able to simulate input points (Network Inputs, Watch Window option are displayed in the watch
Network Setpoints, analog inputs, and binary inputs), window
they must be linked to function blocks or other output
points.
— To select the points being simulated that need to be
Changes in Select Points Screen On Changing
visible in the Watch Window: Modes
After you have selected the points to be debugged, if you
NOTE: All points in the logic will be simulated. However, only switch to another mode and select/unselect the points to be
those points for which you have enabled the View in debugged and then get back to the Online Debugging Mode,
Watch Window option are displayed in the watch the selected points are not selected to be displayed in the
window. watch window. You have to select them again.
1. If you select a point for debugging & enable the watch
window option in Engineering/Debugging mode, it is
retained in Simulation mode.
2. If you select a point for debugging and uncheck the
watch window option in Engineering/Debugging mode,
the same is not retained in Simulation mode.
3. If you select a point in Simulation mode, it is retained in
Engineering/Debugging mode with the watch window
enabled.

EN2Z-0960GE51 R0710 230

 CENTRALINE LYNX TOOL - USER GUIDE

4. Select a point for debugging and with the watch window — If Sine/Cosine/Range was selected for a point in Simu-
option unchecked in Engineering/Debugging mode. If lation mode and you enter the Engineering/Online
you select the same point in Simulation mode, then on Debugging mode, and invoke the Force Input screen,
returning to the Engineering/Online Debugging mode, the mode for that point is shown as Set/Auto. If you
you will find this point is with the watch window option click OK and go to the Simulation mode, the Force
enabled. Input screen indicates the mode as Set/Auto.
5. If you add and remove a point in Simulation mode, the — If Sine/Cosine/Range is selected for a point in Simula-
same point is selected for debugging but not for watch- tion mode and the you enter the Engineering/Online
ing in the Engineering/Online Debugging mode. Debugging mode, and invoke the Force Input screen,
6. Select a point in Simulation mode. Go to the Engineer- the mode for that point is shown as Set/Auto. If you
ing/Debugging mode and see that it is selected for both click Cancel and visit the Simulation mode, the Force
Debug & watching. Now, uncheck the watch window Input screen will indicate the mode as Sine/Cosine/
option. You will find that it is not shown in Simulation Range (depending on what was last selected).
mode. — If Sine/Cosine/Range is selected for a point in Simula-
tion mode and you enter the Engineering /Online
NOTE: Debugging mode, and do not invoke Force Input
screen or any option in the right click menu on that
• The value written to a point and the mode last set (in point and go to the Simulation mode again, the Force
Engineering/Online debugging/Simulation) will be available Input screen indicates the mode as Sine/Cosine/
the next time you visit any other mode (Engineering/Online Range (depending on what was last selected).
debugging/Simulation) with the following exceptions: — The values set for constant blocks are not saved
across mode revisits. When you exit Simulation mode,
the actual value configured for the constant block is
put back on the out slot.

231 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

GENERATE XIF FILE

LONMARK external interface files(.xif) are files that define the There are two benefits to using external interface files. First,
external interface for one or more LONWORKS devices. The an external interface file may include information that is not
external interface is the interface to a device that is exposed included in a device such as network variable names. Second,
over a LONWORKS network. The external interface does not an external interface file can be used during network
expose the internal algorithms of a device, instead, it only engineering when the device is not accessible from the
exposes the inputs to the algorithms and the outputs from the network engineering tool.
algorithms. To generate an XIF file:
The external interface file includes the program ID information • Right-click the device in the Nav palette and select
of the device, application type information, self-documentation Actions > Generate XIF. The XIF file is generated and
information, the configuration information of network stored at the following location: Drive:\\Niagara\Niagara-x-
variables. x-xx\XIF

EN2Z-0960GE51 R0710 232

 CENTRALINE LYNX TOOL - USER GUIDE

ORDER OF EXECUTION
The order of execution defines the sequence in which function NOTE: You cannot change the order of execution for Built In
blocks are executed by the controller. When you drag function function blocks.
blocks on to a wire sheet to build an application logic, by
default, the tool sets the execution order of the functional NOTE: Execution order for blocks within a macro or Applica-
blocks in the order you drop them on to the wire sheet. tion is maintained based on the order in which you
However, you can alter the order in which the controller drag the blocks within them.
executes the function blocks by re-ordering the blocks. In the
Simulation Mode, the order of execution that you set is To change the order of execution:
followed. 1. From the LYNX Palette, drag function blocks, macros or
Programs on the wiresheet. The order in which you drag
NOTE: You can reorder the execution of function blocks the function blocks determines the execution order. The
only. Although NVs or Bacnet objects and Physical execution order is displayed on the container of each
points are shown in the Reorder screen, you cannot function block on the wiresheet.
reorder their order of execution. 2. Right-click the specific container or ControlProgram in
the Nav sidebar. Click Reorder. The Reorder dialog
NOTE: When you remove a block, the order of execution box appears.
gets affected. 3. Select the required application and click Move Up or
Move Down to change the order of execution.
4. Click OK to close the dialog box.

233 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

CUSTOM PALETTE FILE

Create and use a custom palette file to store any LYNX object
application, macro, device, FBs, IOs from a station. You can
use this file to share it across Stations and among multiple
users. This custom palette file acts only as a repository but
you can not configure an object that exists in the palette.
You can later copy and paste or drag and drop these objects
from the custom palette to the station.

Create Custom Palette File

To create a custom palette file:
1. On the Nav sidebar, navigate to the drive where you
want to create the custom palette file. Right click the
drive and select New Folder. A new folder is created.

4. Enter a name for the palette file and click OK. A new
palette file is created. Expand the newly created folder
to view the palette file that you just now created.
5. Double click the palette folder to open its wiresheet.
6. On the Palette sidebar, click the Open Palette button.
The Open Palette dialog box appears.
7. Select Baja module and click OK. You will see the
UnrestrictedFolder in the Baja Palette (Palette sidebar
with Baja module selected).
8. Drag the unrestricted folder in to the folder with the pal-
ette file that you have created. A .bog file appears in the
folder which contains the unrestricted folder.
9. Double-click the UnrestrictedFolder.bog file that was
added to the new folder, to open its wiresheet.
10. Right-click on the folder to rename it. This is the Unre-
stricted folder where you can store all LYNX objects.

NOTE: You can double click the folder on the wiresheet and
drag the UnrestrictedFolder object from the Palette
palette on to the wiresheet. This has the effect of
nesting folders within the palette file. This enables
you to categorize objects that are stored in the pal-
2. Enter a name for the new folder and click OK. ette file. For example, you can drag an Unrestrict-
3. Right click the new folder and select New > Palette- edFolder from the Baja palette (Palette palette with
file.palette Baja module selected) on to the wiresheet of the pal-
ette file and name it Applications. You can then dou-
ble-click the Applications folder on the wiresheet and
drag another UnrestrictedFolder object from the
Baja palette and name it VAV Applications. This cre-
ates the VAV Applications folder under the Applica-
tions folder in a tree structure in the custom palette
file you are creating.

EN2Z-0960GE51 R0710 234

 CENTRALINE LYNX TOOL - USER GUIDE

Add Items to Custom Palette File or

Station > Drivers > BacnetNetwork > BacnetLYNX in
To add any LYNX object such as a macro, application, IO, the Nav sidebar.
Function block to the custom palette: 2. Double-click the ControlProgram under the device
1. Browse to the controlprogram you want to save in the once. It opens the wire sheet of the ControlProgram.
custom palette file by clicking Station > Drivers > Lon- This makes sure that ControlProgram is loaded (all
Network > LonLYNX > ControlProgram device objects are available in memory while copying).
or 3. Right click the device and select Copy.
Station > Drivers > BacnetNetwork > BacnetLYNX > 4. Navigate to the folder you created under the custom
ControlProgram in the Nav sidebar. palette file (Applications or VAV Applications as given in
2. Right click any LYNX object such as application, macro, the Note) and right click it and select Paste.
device, FB, or IO and select Copy. 5. Right click the device and select Enable Saving Con-
3. Navigate to the folder you created under the custom trol Program.
palette file (Applications or VAV Applications as given in
the Note) and right click it and select Paste. NOTE: The Enable Saving ControlProgram option makes
or the ControlProgram under device non-transient so
drag and drop the object to the wiresheet of the folder that it can be saved to the bog file. If this option is not
(Applications or VAV Applications in the Note) under the invoked or before invoking this option, you close the
custom palette file bog file or the workbench, the device looses the Con-
or trolProgram configuration in the custom palette file.
drag and drop a LYNX object directly on to the folder This option appears on device only when device is in
(Applications or VAV Applications in the Note) under the the custom palette and the ControlProgram under
custom palette file in the Nav sidebar. the device is transient. Once you invoke the option,
4. The object is saved under the folder in the custom pal- the next time onwards the same device option does
ette file. not appear on the that particular device object. This
5. Right click the file in the custom palette file and click option appears only when required. If it does not
Save. appear, it means the ControlProgram of the device is
6. Right click the custom palette file and click Close to already in a non-transient state. This may happen
close the custom palette file. when copy-pasting/duplicating a saved device within/
across palettes occurs or when you copy-paste
Close Custom Palette File device object from the LYNX library to the custom
palette folder.
To close the custom palette file, right click the custom palette
file and click Close.

NOTE: If you close a custom palette file without saving the

contents of the custom palette file or close the Work-
bench without saving the contents of the custom pal-
ette file, the newly added contents are not saved and
will not be available when you access this folder the
next time.

You can reuse components from the custom palette file in any
application logic you create by dragging and dropping the
desired object from the custom palette file to the wiresheet of
the ControlProgram.

Add Device to Custom Palette File

Adding a device to the custom palette file is similar to adding a
LYNX object but it has some specific steps you have to
perform additionally. To add a device to the Custom palette
file:
1. Browse to the device you want to save in the custom
palette file by clicking Station > Drivers > LonNetwork
> LonLYNX

6. Right click the custom palette file and select Save. The
device is saved under the folder in the custom palette
file.

235 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

DEVICE ICONS
You can add Lon and Bacnet devices to the station to create • The Bacnet device icon is Downloaded State when
Control Programs and Applications. The Control Program or the Control Program or Application has been downloaded
Application logic is downloaded to the controller or saved to to the controller.
the library. The state of the device is represented by the • The Bacnet device icon is Quick Download Pending
device icon. The Lon and Bacnet device icons differ in their when the Control Program or Application logic is
appearance depending on 5 conditions. modified and is pending for a quick download to the
controller.
• The Bacnet device icon is Binding Pending when a
Lon Icons new link is added to a downloaded device and is pending
• The Lon device icon is Normal in the Palette and for binding. After binding the device, the icon goes to
LYNX Library sidebars. Downloaded State.
• The Lon device icon is Download Pending when the
device is dropped onto the Nav sidebar. NOTE:
• The Lon device icon is Downloaded State when the
Control Program or Application has been downloaded to — If the download fails, the device icon is Download
the controller. Pending.
• The Lon device icon is Quick Download Pending — If changes are made to the Object Configuration View
when the Control Program or Application logic is modified of the device, the icon is Download Pending.
and is pending for a quick download to the controller. — If a new link is added to a Lon device which is in
• The Lon device icon is Binding Pending when a new Download Pending state, the device icon remains in
link is added to a downloaded device and is pending for the Download Pending state.
binding. After binding the device, the icon goes to — When a link is created between two Bacnet devices,
Downloaded State. the source device icon is in Binding Pending state
when the link status is Push. The target device icon is
NOTE: in Binding Pending state when the link status is Poll.

— If the download fails, the device icon is Download

Pending. Device Icons in Library
— If changes are made to the Object Configuration View • When a LonLYNX/BacnetLYNX device is copied and
of the device, the icon is Download Pending. pasted, the resulting copy of the device icon will be in
— If a new link is added to a Lon device which is in Download Pending state.
Download Pending state, the device icon remains in • When a LonLYNX/BacnetLYNX device is cut and pasted in
the Download Pending state. the same Station, the device icon will be in the same state
— When a link is created between two Lon devices, both as it was before the cut/paste action.
the device icons are in Binding Pending state. • When a LonLYNX/BacnetLYNX device is cut and pasted
from the Library, the state of the resulting copy of the
device will be in the Download Pending state
Bacnet Icons • When you save a Control Program or Application logic
• The Bacnet device icon is Normal in the Palette and from the station to the LYNX library, the device icon is in
LYNX Library sidebars. Normal state.
• The Bacnet device icon is Download Pending when • When a device is dragged from the LYNX Library onto the
the device is dropped onto the Nav sidebar. Nav sidebar, the device icon is in Download Pending
state.

EN2Z-0960GE51 R0710 236

 CENTRALINE LYNX TOOL - USER GUIDE

VIRTUAL OFFLINE DISCOVERY

Using the Virtual feature you can view the online and offline The online/offline points can be used in a Px view.
points of the device. To create a new Px view:
To view the online and offline points of the device: 1. Right-click the Bacnet device on the Nav sidebar.
1. Expand the Bacnet device on the Nav sidebar. 2. Choose Views > New View. The New Px View dialog
2. Right-click Virtual and choose Actions. box appears.
3. Select Online Discovery to view the online points of 3. Type the View Name and click OK. The screen displays
the device.  the new view.
or
Select Offline Discovery to view the fixed, mandatory, To use the offline point on the Px view:
and offline points of the device.
1. Create an application logic on the wiresheet under Con-
NOTE: trolProgram.
2. Right-click Virtual and select Offline Discovery.
— The points in online or offline discovery mode are 3. Expand Virtual to view the online points on the Nav
automatically unloaded after a specific time. sidebar.
— A point which is left expanded in offline discovery 4. Expand the point and drag the required property from
mode is not unloaded. the Nav sidebar onto the Px view.
5. Right-click the Bacnet device and select Views to view
the Px view you have created.
The mode of operation can be restored from offline discovery
to online discovery in the following two ways.
To view the online values from the device:
1. Choose Virtual > Actions > Online Discovery and
forcibly change the mode. 1. Download the application logic to the controller.
2. Click Virtual when one of the points in offline discovery 2. Right-click Virtual and select Online Discovery.
mode is unloaded. The mode is restored to online dis- 3. Right-click the Bacnet device and select Views.
covery. 4. Select the Px view you have created to see the online
values.

237 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

EN2Z-0960GE51 R0710 238

 CENTRALINE LYNX TOOL - USER GUIDE

239 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

EN2Z-0960GE51 R0710 240

 CENTRALINE LYNX TOOL - USER GUIDE

241 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

EN2Z-0960GE51 R0710 242

 CENTRALINE LYNX TOOL - USER GUIDE

243 EN2Z-0960GE51 R0710

CENTRALINE LYNX TOOL - USER GUIDE

Manufactured for and on behalf of the Environmental and Combustion Controls Division of Honeywell Technologies Sàrl, Rolle, Z.A. La Pièce 16, Switzerland by its Authorized Representative:

CentraLine CentraLine Printed in Germany.

Honeywell GmbH Honeywell Control Systems Ltd. Subject to change without notice.

Böblinger Strasse 17 Arlington Business Park EN2Z-0960GE51 R0710

71101 Schönaich, Germany UK-Bracknell, Berkshire RG12 1EB

phone: +49 7031 637 845 phone: +44 13 44 656 565

fax: +49 7031 637 846 fax: +44 13 44 656 563

[email protected] [email protected]

www.centraline.com www.centraline.com