Hardware and Software Installation: Tracer™LCI-C For Tracer™ CH530/531 Chiller Controllers

Hardware and Software
Installation
Tracer™LCI-C for Tracer™ CH530/531 Chiller

Controllers
SAFETY WARNING
Only qualified personnel should install and service the equipment. The installation, starting up, and servicing
of heating, ventilating, and air-conditioning equipment can be hazardous and requires specific knowledge and
training. Improperly installed, adjusted or altered equipment by an unqualified person could result in death or
serious injury. When working on the equipment, observe all precautions in the literature and on the tags,
stickers, and labels that are attached to the equipment.
February 2011 ACC-SVN25C-EN

Copyright
© 2011 Trane All rights reserved
This document and the information in it are the property of Trane and may not be used
or reproduced in whole or in part, without the written permission of Trane. Trane reserves
the right to revise this publication at any time and to make changes to its content without
obligation to notify any person of such revision or change.
Trademarks
Trane and its logo are trademarks of Trane in the United States and other countries. All
trademarks referenced in this document are the trademarks of their respective owners.
Warnings, Cautions, and Notices

Warnings, cautions, and notices are provided in appropriate places throughout this
document:
WARNING: Indicates a potentially hazardous situation which, if not avoided,

could result in death or serious injury.
CAUTION: Indicates a potentially hazardous situation which, if not avoided,

could result in minor or moderate injury. It could also be used to alert against
unsafe practices.
NOTICE: Indicates a situation that could result in equipment or property-

damage-only accidents.
Table of Contents
Product Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
What Does an LCI-C Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
LCI-C Shipment And Inspection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Hardware and Software Installation Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Required Tools For Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Hardware Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Determine the Correct Software For Installation . . . . . . . . . . . . . . . . . . . . 8
Start the Software Installation Procedure With The Techview
Service Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Finish Software Installation Procedure With The Rover Service Tool . . 12
Ready for Network Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Appendix A: Network Variables Lists For Each Chiller Type . . . . . . . . . . . . . . . . 19

Appendix B: Network Variables Listed Alphabetically . . . . . . . . . . . . . . . . . . . . . 28
Appendix C: User-defined Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
User-defined Network Variable Types (UNVTs) . . . . . . . . . . . . . . . . . . . . . . . 31
User-defined Configuration Property Types . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Appendix D: Network Variable And Configuration Property Definitions . . . . . 36
Network Variable Input Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Network Variable Output Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Configuration Property Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Appendix E: Troubleshooting the LCI-C Installation . . . . . . . . . . . . . . . . . . . . . . . 60
Appendix F: Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Appendix G: Rover Service Tool Parts List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Reader Response Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
ACC-SVN25C-EN 3
4 ACC-SVN25C-EN
Product Overview
This installation guide takes you through all the steps necessary to install and setup aTracer™ LCI-C
with a Tracer™ CH530/531 chiller controller. It covers both electronic circuit board/hardware
installation and appropriate LCI-C software installation and set up for the following installation
types:
• Tracer Summit building automation systems
If you are connecting the LCI-C to a Tracer Summit™ system, you will not need the network
variable information in the Appendixes. Appendix G, however, provides a list of additional
resources that you may find useful.
• Non-Trane building automation systems
If you are connecting the LCI-C to a non-Trane building automation system using LonTalk,™
Appendixes B through E will provide you with the system integration information you will need
regarding network variables.
Note: If you are unfamiliar with the terminology used in this installation guide, see the “Glossary,”
p. 63.
What Does an LCI-C Do?

An LCI-C (LonTalk Communications Interface for Chillers) provides a communication interface
between a Tracer CH530/531 controller and a LonTalk network.
LonMark certification
The LonMark organization promotes LonTalk as an industry standard for control communication.
The LCI-C is certified to the LonMark Chiller Functional Profile 8040 Version 1.0, and follows LonTalk
FTT-10A communications system technology. Compliance with this technology means that the
LCI-C can provide an interface for non-Trane LonTalk networks.
Network variables
LonTalk uses network variables to communicate points on a communication link. LonMark has
defined a list of standard network variables.
Chiller Functional Profile

LonMark calls their standard list of variables for chiller control the Chiller Functional Profile. This
profile is meant to allow interoperability between control systems and chillers, regardless of chiller
type or manufacturer.
The LCI-C Extension

The LCI-C Extension is a list of additional network variables Trane created that are over and above
the ones defined by the Chiller Functional Profile. The LCI-C Extension is considered “open”
because the network variables are not proprietary.
The network variables in the LCI-C Extension are defined in Appendixes D and E.
LCI-C Shipment And Inspection

The LCI-C is either factory installed with the chiller controller or shipped as an individual part for
field installation. The service part number is MOD01216 (X13650845-02).
Storage
If the LCI-C is stored for a period of time prior to being installed, it must be protected from the
elements. The temperature of the storage location should be between -40 °F (-40 °C) and 158 °F (70
°C) and the relative humidity should be 0–95%, non-condensing.
ACC-SVN25C-EN 5
Hardware and Software Installation Procedures
Required Tools For Installation
Make sure you have the following tools:
• Laptop computer with
– TechView software
Use Version 9.04 or higher. (You can check your version by going to Help menu and selecting
About.)
– Tracer CH530/531 Main Processor software
Use the most recent version available for your chiller type. (See Table 1 on page 8 for
minimum software version requirements).
– Rover Service Tool software
Use Version 5.0 SP8 or higher. (You can check your version by looking at the splash screen
as Rover starts.)
• EIA-232 (DB-9) serial cable for the TechView service tool
• Rover Comm5 PCMCIA adapter (see , “Appendix G: Rover Service Tool Parts List” for part
number)
• Rover Comm5 adapter cable (see , “Appendix G: Rover Service Tool Parts List” for part number)
• Screwdriver
• South pole of a magnet
Notes:
• This guide assumes you are familiar with using Rover and TechView service tools. If you are not
and need additional information on how to use these tools, refer to , “Appendix F: Additional
Resources” on p. 61.
• To download, free of charge, the most recent versions of TechView software and Main Processor
software, go to the Tracer CH530 Software Download site:
http://www.trane.com/Commercial/DesignAnalysis/TechView.aspx
• Non-Trane LonTalk software tools can be used, instead of the Rover service tool, for the
procedures in this guide. These tools most likely require appropriate XIF and NXE files. Find the
XIF file at www.lonmark.org in the product directory. Both the NXE and the XIF files can be
found in the directory of a computer that has the correct version of Rover installed: C:\Program
Files\Rover\Images. Contact your local Trane office to get these files. However, go to the vendor
of that tool for technical support, since Trane will not provide technical support for another
vendor’s software tool.
• For information about parts for the Rover service tool, see , “Appendix G: Rover Service Tool
Parts List” on p. 62.
6 ACC-SVN25C-EN
Hardware Installation
The hardware of an LCI-C consists of a low-level intelligent device (LLID), which is an electronic
board that allows the Tracer CH530/531 controller to communicate on a LonTalk network. The LLID
is designed to be mounted in an enclosure so that it is protected from the environment. The chiller
control panel box, where the other Tracer CH530/531 LLIDs reside, provides a convenient place for
the LCI-C (see Figure 1 on the following page).
Figure 1. Chiller control panel box
To install the LCI-C LLID:

1. Using a screwdriver, mount the LCI-C LLID in the chiller control panel box or another suitable
enclosure.
2. Attach the IPC3 communication bus ribbon cable to the LCI-C LLID.
3. Attach the LonTalk cable to the LCI-C LLID.
4. Attach any necessary termination resistors to the LonTalk link. (For Trane control systems, refer
to the Tracer Summit Hardware and Software Installation Guide (BMTX-SVN01x-EN) (where x
is the letter of the current level) for more information on where and when to use termination
resistors.)
ACC-SVN25C-EN 7
Software Installation
This section describes how to install the correct software for the LCI-C. Make sure you have the
necessary tools for the procedure (see “Required Tools For Installation” on page 6). Total software
installation time can vary greatly, from as little as 20 minutes to a few hours.
Note: This guide provides instructions on installing LCI-C Extension software only, which is the
latest software for this product. If you need to install the LCI-C Profile Only software, contact
your local office for assistance.
Determine the Correct Software For Installation

Because all CH530/531 LCI-C LLID hardware is identical, you can load different software versions
into it. Available software versions have different network variable lists depending on the chiller
type (see Appendixes B, C, D, and E for network variables).
To determine the correct software or version for your chiller type, see Table 1. The table shows the
minimum Tracer CH530/531 Main Processor software version and the corresponding LCI-C
Program ID.
Table 1.Software versions identified by chiller type

Minimum Tracer
CH530/531 Main
Processor LCI-C software version by flash
Chiller type software version LCI-C Program ID download file name1
LCI-C Extension software:
CVHE/F/G, CVGF 6.0
CDHF/G 0011_LCI-C_NFD_1_0_CH530-CVH-
2.0 80002A-5028-0304-02
CVG-CDH-CVR.nxe
CVRD (CH531) 2.0
CGWF/H/N, CCAF, CCUH/N, 0011_LCI-C_NFD_1_0_CH530-CGW-
2.0 80002A-5028-0304-03
CGAN, CXAN, CGCL CCA-CGA.nxe
RTHD 8.0 80002A-5028-0304-04 0011_LCI-C_NFD_1_0_CH530-RTH.nxe
RTXA+ 1.0 80002A-5028-0304-05 0011_LCI-C_NFD_1_0_CH530-RTX.nxe
RTAC 30.0 80002A-5028-0304-06 0011_LCI-C_NFD_1_0_CH530-RTA.nxe
RTWD/RTUD 1.0 80002A-502B-0304-09 0011_LCI-C_NFD_1_0_CH530-RTW.nxe
LCI-C Profile Only software:
0011_LCI-C_NFD_1_0_CH530-Profile-
CVHE/F/G, CVGF, RTHD, RTAC N/A 80002A-5028-0304-01
Only.nxe
1 All software versions listed in this column refer to different types of LCI-C Extension software, except for the software version identified
in the last row, which is LCI-C Profile Only software.
LCI-C profile only

The initial release of LCI-C software provides an interface that supports the standard LonMark
Chiller Functional Profile 8040. For this publication, this initial LCI-C software release is referred to
as the LCI-C Profile Only. This software release supports a very limited number of network
variables.
LCI-C Extension
Subsequent releases of LCI-C software support the Trane Chiller Extension network variables.
These software releases are referred to as the LCI-C Extension. The LCI-C Extension provides
additional network variables.
8 ACC-SVN25C-EN
If the LCI-C was factory installed...

If the chiller was shipped from the factory with the LCI-C installed before the Trane LCI-C Extension
was available, a software upgrade may be necessary (refer to Table 1 on page 8). Please follow the
installation procedure given in this guide starting on this page.
If the LCI-C was ordered as a service part...

If the LCI-C was ordered as a service part, it contains the LCI-C Profile Only software (refer to Table 1
on page 8). Please follow the installation procedure given in this guide starting on this page.
Start the Software Installation Procedure With The Techview Service Tool
The TechView service tool is used to upgrade the Tracer CH530/531 Main Processor software and
to install the LCI-C on the Tracer CH530/531 controller. (See the CTV CH530 TechView Programming
Guide (CTV-SVP01A-EN) and “Appendix F: Additional Resources” on page 61 for other information
about the TechView service tool.)
Note: Before beginning the Main Processor and LCI-C software installation with the TechView
service tool, please note that the chiller will be unavailable to run and will not produce
chilled water during part of the installation procedure.
1. Make sure you have followed the procedures for “Hardware Installation” on page 7.
2. Connect the TechView service tool to the Tracer CH530/531 controller (Figure 2).
3. Click the TechView icon. The Connection View screen appears. Click the Local Connection
button.
Figure 2. Connecting the TechView service tool to the LCI-C LLID
4. From the View menu, select Software. The Software view displays (see Figure 3).
ACC-SVN25C-EN 9
Figure 3. Main Processor software version displayed in TechView
Compare the required software version given in Table 1 on page 8 to the version displayed in
the Installed Product & Version field. If the version appearing in the Installed Product &
Version field is:
– Less than the version required by Table 1, the Main Processor software needs to be
upgraded. Proceed to step 5.
– Equal to or greater than the version required by Table 1, the Main Processor software will
not need to be upgraded. Proceed to step 6.
5. From the Available Versions drop-down list, select the highest software version available.
If the highest version available is not equal to or greater than the version required by Table 1
on page 7, do not proceed with the installation until you have upgraded your Main Processor
software from the Tracer CH530 Software Download site. (For information on downloading
from this site, go to “Required Tools For Installation” on page 6.)
Click the Download Software to Main Processor button. The selected software version will
download to the Main Processor.
6. After the download is complete, from the View menu, select Configuration to display the
Configuration view. (The Configuration view will have different options, depending on the
chiller type.) Scroll to the option for the BAS interface.
– If the BAS interface is already configured with the LCI-C Comm5 Extension, proceed to step 7.
– If the BAS interface is not already configured with the LCI-C Comm5 Extension, select it (see
Figure 4) and click the Load Configurations button. (The Load Configuration button is
activated whenever a change is made to the configuration.) The Binding view will appear.
Proceed to step 8.
Figure 4. Configuration view: Selecting the LCI-C (LonTalk) Extension
10 ACC-SVN25C-EN
7. From the View menu, select Binding. The Binding view appears.
8. Click Bind on the LCI-C Extension LLID (see Figure 5). A dialog box will appear that prompts you
to select the device with a magnet (Figure 6). Proceed to step 9 before clicking Yes.
Figure 5. Binding view: The Bind button is activated
Figure 6. Prompt for selecting the LCI-C LLID with a magnet
9. Pass the south pole of a magnet across the LCI-C LLID so that the LED lights (Figure 7).
Figure 7. Selecting the LCI-C LLID with the south pole of a magnet
10. Click Yes on the dialog box shown in Figure 6.

Note: You may be prompted to download software to the LCI-C LLID. If so, click Yes.
ACC-SVN25C-EN 11
11. Confirm that binding took place: The frowning red face should have turned into a smiling green
face (see Figure 8).
The smiling green face marks a device that is communicating and

correctly bound. No action is required.
The frowning red face marks a necessary device (as it is set in the
Configuration view) that is not bound or is not communicating.
The expressionless yellow face marks a device that is

communicating but incorrectly bound or that has not had all of its
information confirmed.
Figure 8. Binding completed successfully
12. Make sure that all of the items in Binding view have smiling green faces. If not, see the
appropriate chiller installation documentation.
Finish Software Installation Procedure With The Rover Service Tool

The Rover service tool is used to flash download the correct Neuron software to the LCI-C.
Notes:
• If you need information on how to use the Rover service tool, see “Appendix F: Additional
Resources” on page 61.
• The diagnostic “LCI-C Software Mismatch: Use BAS Tool” may appear on the TechView service
tool and the Tracer CH530/531 DynaView display. This diagnostic indicates that the appropriate
LCI-C Neuron software needs to be downloaded.
To finish software installation with Rover
1. Make sure you have followed the procedures for “Hardware Installation” on page 7 and “Start
the Software Installation Procedure With The Techview Service Tool” on page 9.
2. If the LCI-C is currently connected to:
– A Tracer Summit system—It must be removed before proceeding. To remove it, unassign the
Neuron ID, wait for the activity on the Comm LED to slow down, and disconnect the LCI-C
LLID from the BCU. Please note that the flash download will cause the LCI-C to lose all of its
LonTalk bindings.
– A non-Trane network—Please note that the flash download will cause the LCI-C to lose all
of its LonTalk bindings. It will also change the LCI-C Program ID, which will therefore change
the network variable list. This may require that you change the configuration of the non-
Trane portion of the network.
3. Connect the Rover cable to the LCI-C communication terminals (see Figure 9). Alternatively, you
can connect the Rover alligator clips anywhere on the LonTalk network. However, two network
managers cannot be connected to the network at the same time.
In other words, you cannot have on the network at the same time:
– Two Rover tools, or
– Rover and a third party network management device, or
– Rover and a BCU.
(This is why you were instructed to disconnect the LCI-C from the BCU in step Step 2.)
12 ACC-SVN25C-EN
Figure 9. Connecting the Rover service tool to the LCI-C LLID
4. Click on the Rover icon to start the application. Then click the Flash Download Wizard button
(see Figure 10).
Figure 10. Flash Download Wizard button on the Rover service tool
ACC-SVN25C-EN 13
Note: If you do not have Flash Download Wizard, you may not have the correct version of
Rover. See “Required Tools For Installation” on page 6.
The Welcome page for the Flash Download Wizard displays.
5. The Welcome page lists the steps involved in the current procedure. Click Next. (The
information on saving files on the Welcome page does not apply to the LCI-C because the
configuration is done using the TechView service tool.)
6. The Discover link dialog box displays as Step 1 (Figure 11). Rover does a discovery of devices
on the link. You will see the devices that are connected and powered up appear under Status.
Figure 11. Step 1. Discover link
When the discovery is complete, click Next to go to Step 2 (see Figure 12 on page 15).
7. Choose the appropriate file name from the File name drop-down list. The file name will contain
“LCI-C,” “CH530,” and the chiller type (see Table 1 on page 8 for file names).
Note: If you do not have a file name that matches your chiller type, you may not have the
correct version of Rover. See “Required Tools For Installation” on page 6.
14 ACC-SVN25C-EN
Figure 12. Step 2. Select an image file
Click Next to go to Step 3 (see Figure 13 on page 16).

8. In the Possible Tracer LCI-C target devices list, select your target device by checking the
appropriate box. Click Next to go to Step 4 (Figure 14 on page 16).
You may choose more than one LCI-C to flash download. The Rover flash download utility will
flash download to one after the other.
ACC-SVN25C-EN 15
Figure 13. Step 3. Review and refine the target device list
Figure 14. Step 4. Confirm the setup and start the flash download
16 ACC-SVN25C-EN
9. This is the confirmation screen. Here you can see the Program ID of the selected image file and
the Program ID of the target device(s).
– If they are the same, then the flash download is not needed. Click Cancel.
– If they are different, then the flash download is required. Click Download.
Or you can compare the Program ID to Table 1 on page 8.
– If your LCI-C matches the Program ID for the Trane LCI-C Extension for your chiller type, then
you have the correct Neuron software. Flash download is not needed. Click Cancel.
– If the LCI-C has a Program ID that does not match your chiller type, then flash download is
required. Click Download.
The next dialog box displays: Step 5. Download (see Figure 15).
Figure 15. Step 5. Download
10. When download is complete, click Finish. The Rover service tool application closes.
11. Remove the IPC3 bus and reconnect it to cycle power on the LCI-C.
12. Rover can be used to verify that the LCI-C Program ID is correct. Click on the Rover icon to start
the application. Then click either the Configuration Only Service Tool or the Comm5
Service Tool button (see Figure 16 on page 18).
ACC-SVN25C-EN 17
Figure 16. Rover service tool menu
After Rover completes the initial discovery, select Tracer LCI-C on the tree to view the Program
ID (Figure 17). It should match the Program ID in Table 1 on page 8 for the Trane LCI-C Extension
of your chiller type. If it doesn’t match, then the wrong software version may have been selected
for flash download. Repeat the flash download with a different file.
Figure 17. Verifying the Program ID
This completes the software installation.

The diagnostic LCI-C Software Mismatch: Use BAS Tool should no longer appear on the Tracer
CH530/531 DynaView or the TechView service tool.
Ready for Network Installation

You may now assign the LCI-C Neuron ID within Tracer Summit software, or you may otherwise
install the LCI-C to a non-Trane LonTalk network. When installing the LCI-C on a Tracer Summit
system, the LCI-C can be installed as a chiller object (Version 16 or later) or a Generic LonTalk Device
(Version 14 and 15).
18 ACC-SVN25C-EN
Appendix A: Network Variables Lists For Each Chiller
Type
Table 1 through Table 7, p. 27 list network variables for different chiller types.
Table 1. Network variables for CVH/CVG/CDH/CVR

(program ID 80002A-5028-0304-02)
NV index Network variable SNVT type
0 nciLocation SNVT_str_asc(36)
1 nviChillerEnable SNVT_switch(95)
2 nviCoolSetpt SNVT_temp_p(105)
3 nvoOnOff SNVT_switch(95)
4 nvoActiveSetpt SNVT_temp_p(105)
5 nviCapacityLim SNVT_lev_percent(81)
6 nviMode SNVT_hvac_mode(108)
7 nviHeatSetpt SNVT_temp_p(105)
8 nvoActualCap SNVT_lev_percent(81)
9 nvoCapacityLim SNVT_lev_percent(81)
10 nvoLvgChWTemp SNVT_temp_p(105)
11 nvoEntChWTemp SNVT_temp_p(105)
12 nvoEntCndWTemp SNVT_temp_p(105)
13 nvoLvgCndWTemp SNVT_temp_p(105)
14 nvoAlarmDescr SNVT_str_asc(36)
15 nvoChillerStat SNVT_chlr_status(127)
16 nviRequest SNVT_obj_request(92)
17 nvoStatus SNVT_obj_status(93)
18 nvoFileDirectory SNVT_address(114)
19 nviTraneVar2 UNVT
20 nvoTraneVar9 UNVT
21 nviBaseLdgSetpt SNVT_lev_percent(81)
22 nviBaseLdgReq SNVT_switch(95)
23 nvoStatusOutputs SNVT_state(83)
24 nvoCprsrsRunning SNVT_state(83)
25 nvoEvapWtrPump SNVT_switch(95)
26 nvoEvapWtrFlow SNVT_switch(95)
27 nvoCondWtrPump SNVT_switch(95)
28 nvoCondWtrFlow SNVT_switch(95)
29 nvoEvapWFlowRate SNVT_flow(15)
30 nvoCondWFlowRate SNVT_flow(15)
31 nvoActiveBLSetpt SNVT_lev_percent(81)
32 nvoSecCndEntWTmp SNVT_temp_p(105)
33 nvoSecCndLvgWTmp SNVT_temp_p(105)
34 nvoEvapRfgtPrsC1 SNVT_press_f(59)
36 nvoEvapRfgtTmpC1 SNVT_temp_p(105)
38 nvoCondRfgtPrsC1 SNVT_press_f(59)
40 nvoCondRfgtTmpC1 SNVT_temp_p(105)
42 nvoPurgeInfoC1 UNVT_purge_information
ACC-SVN25C-EN 19
Appendix A: Network Variables Lists For Each Chiller Type
Table 1. Network variables for CVH/CVG/CDH/CVR

(program ID 80002A-5028-0304-02) (continued)
43 nvoPurgeInfoC2 UNVT_purge_information
44 nvoHiSideOilPrsA SNVT_press_f(59)
45 nvoHiSideOilPrsD SNVT_press_f(59)
46 nvoLoSideOilPrsA SNVT_press_f(59)
47 nvoLoSideOilPrsD SNVT_press_f(59)
48 nvoOilTempA SNVT_temp_p(105)
49 nvoOilTempD SNVT_temp_p(105)
50 nvoRfgtDischTmpA SNVT_temp_p(105)
51 nvoRfgtDischTmpD SNVT_temp_p(105)
52 nvoVoltageA UNVT_3phase_volt
53 nvoVoltageD UNVT_3phase_volt
54 nvoCurrentA UNVT_3phase_current
55 nvoCurrentD UNVT_3phase_current
56 nvoStartsRunTmA UNVT_starts_runtime
57 nvoStartsRunTmD UNVT_starts_runtime
58 nvoUnitPower SNVT_power_f(57)
Table 2. Network variables for CGW, CCA, CCU, CGA, CXA, CGC
(program ID 80002A-5028-0304-03)
23 nvoCondFans SNVT_state(83)
20 ACC-SVN25C-EN
Table 2. Network variables for CGW, CCA, CCU, CGA, CXA, CGC
28 nvoOutdoorTemp SNVT_temp_p(105)
29 nvoUnitVoltage UNVT_3phase_volt
30 nvoUnitCurrent UNVT_3phase_current
39 nvoAirFlowPctC1 SNVT_lev_percent(81)
42 nvoStartsRunTmB UNVT_starts_runtime
43 nvoStartsRunTmC UNVT_starts_runtime
45 nvoStartsRunTmE UNVT_starts_runtime
46 nvoStartsRunTmF UNVT_starts_runtime
Table 3. Network variables for RTH (program ID 80002A-5028-0304-04)

21 nviBaseLdgSetpt SNVT_lev_percent(81)
22 nviBaseLdgReq SNVT_switch(95)
ACC-SVN25C-EN 21
Table 3. Network variables for RTH (program ID 80002A-5028-0304-04) (continued)

29 nvoActiveBLSetpt SNVT_lev_percent(81)
30 nvoCondControl SNVT_lev_percent(81)
Table 4. Network variables for RTX

(program ID 80002A-5028-0304-05)
Index Network variable SNVT type
19 nviNoiseRdcnReq SNVT_switch(95)
22 ACC-SVN25C-EN
Table 4. Network variables for RTX

Index Network variable SNVT type
34 nvoHiSideOilPrsB SNVT_press_f(59)
35 nvoHiSideOilPrsC SNVT_press_f(59)
38 nvoOilTempB SNVT_temp_p(105)
39 nvoOilTempC SNVT_temp_p(105)
43 nvoCurrentB UNVT_3phase_current
44 nvoCurrentC UNVT_3phase_current
ACC-SVN25C-EN 23
Table 5. Network variables for RTA

(program ID 80002A-5028-0304-06)
12 nvoChillerStat SNVT_shlr_status(127)
38 nvoOilTempB SNVT_temp_p(105)
39 nvoOilTempC SNVT_temp_p(105)
41 nvoVoltageA SNVT_3phase_volt
42 nvoCurrentA SNVT_3phase_current
24 ACC-SVN25C-EN
Table 5. Network variables for RTA

43 nvoCurrentB SNVT_3phase_current
44 nvoCurrentC SNVT_3phase_current
45 nvoCurrentD SNVT_3phase_current
Table 6. Network variables for RTWD/RTUD

(program ID 80002A-5028-0304-09)
NV Index Network variable SNVT type

21 nviNoiseRdcnReq SNVT_switch(95)
29 nvoCondControl SNVT_lev_percent(81)
ACC-SVN25C-EN 25
Table 6. Network variables for RTWD/RTUD

NV Index Network variable SNVT type

45 nvoRfgtDischTmpB SNVT_temp_p(105)
46 nvoRfgtDischTmpC SNVT_temp_p(105)
49 nvoVoltageB UNVT_3phase_volt
50 nvoVoltageC UNVT_3phase_volt
51 nvoVoltageD UNVT_3phase_volt
53 nvoCurrentB UNVT_3phase_current
54 nvoCurrentC UNVT_3phase_current
26 ACC-SVN25C-EN
Table 7. Network variables for LCI-C Profile Only

(program ID 80002A-5028-0304-01)
ACC-SVN25C-EN 27
Appendix B: Network Variables Listed Alphabetically
Network variables for the LCI-C Extension are listed alphabetically in Table 1 with columns for
chillers types.
Note: Not all variables are available for every chiller. For example, the variables
nvoSecCndEntWTmp and nvoSecCndLvgWTmp apply only to the CVH model.
Table 1. Network variables for the LCI-C Extension, listed alphabetically

CGW/
CCA/
CVH/CVG/ CGA/
CVR/CDH CCU/
Tracer CXA/CGC RTH RTAC RTXA+
CH530/ Tracer Tracer Tracer Tracer RTWD/
Variable name SNVT 531 CH530 CH530 CH530 CH530 RTUD
nviBaseLdgReq SNVT_switch(95) ×
nviBaseLdgSetpt SNVT_lev_percent(81) ×
nviCapacityLim SNVT_lev_percent(81) × × × × × x
nviChillerEnable SNVT_switch(95) × × × × × ×
nviCoolSetpt SNVT_temp_p(105) × × × × × ×
nviHeatSetpt SNVT_temp_p(105) × × × × ×
nviMode SNVT_hvac_mode(108) × × × × × ×
nviNoiseRdcnReq SNVT_switch(95) × ×
nviRequest.RQ_Clear_Alarm SNVT_obj_request(92) × × × × × x
nvoActiveBLSetpt SNVT_lev_percent(81) × × ×
nvoActiveSetpt SNVT_temp_p(105) × × × × × ×
nvoActualCap SNVT_lev_percent(81) × × × × × ×
nvoAirFlowPctC1 SNVT_lev_percent(81) × × ×
nvoAirFlowPctC2 SNVT_lev_percent(81) × × ×
nvoAlarmDescr SNVT_str_asc(36) × × × × × ×
nvoCapacityLim SNVT_lev_percent(81) × × × × × ×
nvoChillerStat.chlr_op_mode SNVT_chlr_status(127) × × × × × ×
nvoChillerStat.chlr_run_mode SNVT_chlr_status(127) × × × × × ×
nvoChillerStat.chw_flow SNVT_chlr_status(127) × × × × × ×
nvoChillerStat.condw_flow SNVT_chlr_status(127) × × × ×
nvoChillerStat.in_alarm SNVT_chlr_status(127) × × × × × ×
nvoChillerStat.limited SNVT_chlr_status(127) × × × × × ×
nvoChillerStat.local SNVT_chlr_status(127) × × × × × ×
nvoChillerStat.run_enabled SNVT_chlr_status(127) × × × × × ×
nvoCondControl SNVT_lev_percent(81) × ×
nvoCondFans SNVT_state(83) ×
nvoCondRfgtPrsC1 SNVT_press_f(59) × × × × × ×
nvoCondRfgtPrsC2 SNVT_press_f(59) × × × × x
nvoCondRfgtPrsC3 SNVT_temp_f(105) ×
nvoCondRfgtPrsC4 SNVT_temp_f(105) ×
nvoCondRfgtTmpC1 SNVT_temp_p(105) × × × × × ×
nvoCondRfgtTmpC2 SNVT_temp_p(105) × × × × ×
nvoCondRfgtTmpC3 SNVT_temp_p(105) ×
nvoCondRfgtTmpC4 SNVT_temp_p(105) ×
nvoCondWFlowRate SNVT_flow(15) ×
28 ACC-SVN25C-EN
Table 1. Network variables for the LCI-C Extension, listed alphabetically (continued)
CGW/
CCA/
CVH/CVG/ CGA/
CVR/CDH CCU/
nvoCondWtrFlow SNVT_switch(95) × × × x
nvoCondWtrPump SNVT_switch(95) × × × ×
nvoCprsrsRunning SNVT_state(83) × × × × × ×
nvoCurrentA UNVT_3phase_current × × × × ×
nvoCurrentB UNVT_3phase_current × × ×
nvoCurrentC UNVT_3phase_current × × ×
nvoCurrentD UNVT_3phase_current × × × ×
nvoCurrentE UNVT_3phase_current
nvoCurrentF UNVT_3phase_current
nvoEntChWTemp SNVT_temp_p(105) × × × × × ×
nvoEntCndWTemp SNVT_temp_p(105) × × × ×
nvoEvapRfgtPrsC1 SNVT_press_f(59) × × × × × x
nvoEvapRfgtPrsC2 SNVT_press_f(59) × × × × ×
nvoEvapRfgtPrsC3 SNVT_press_f(59) ×
nvoEvapRfgtPrsC4 SNVT_press_f(59) ×
nvoEvapRfgtTmpC1 SNVT_temp_p(105) × × × × × ×
nvoEvapRfgtTmpC2 SNVT_temp_p(105) × × × × ×
nvoEvapRfgtTmpC3 SNVT_temp_p(105) ×
nvoEvapRfgtTmpC4 SNVT_temp_p(105) ×
nvoEvapWFlowRate SNVT_flow(15) ×
nvoEvapWtrFlow SNVT_switch(95) × × × × × ×
nvoEvapWtrPump SNVT_switch(95) × × × × × ×
nvoHiSideOilPrsA SNVT_press_f(59) × × × × ×
nvoHiSideOilPrsB SNVT_press_f(59) × × ×
nvoHiSideOilPrsC SNVT_press_f(59) × × ×
nvoHiSideOilPrsD SNVT_press_f(59) × × × ×
nvoHiSideOilPrsE SNVT_press_f(59)
nvoHiSideOilPrsF SNVT_press_f(59)
nvoLoSideOilPrsA SNVT_press_f(59) ×
nvoLoSideOilPrsB SNVT_press_f(59)
nvoLoSideOilPrsC SNVT_press_f(59)
nvoLoSideOilPrsD SNVT_press_f(59) ×
nvoLoSideOilPrsE SNVT_press_f(59)
nvoLoSideOilPrsF SNVT_press_f(59)
nvoLvgChWTemp SNVT_temp_p(105) × × × × × x
nvoLvgCndWTemp SNVT_temp_p(105) × × × x
nvoOilTempA SNVT_temp_p(105) × × ×
nvoOilTempB SNVT_temp_p(105) × ×
nvoOilTempC SNVT_temp_p(105) × ×
nvoOilTempD SNVT_temp_p(105) × × ×
ACC-SVN25C-EN 29
Table 1. Network variables for the LCI-C Extension, listed alphabetically (continued)
CGW/
CCA/
CVH/CVG/ CGA/
CVR/CDH CCU/
nvoOilTempE SNVT_temp_p(105)
nvoOilTempF SNVT_temp_p(105)
nvoOnOff SNVT_switch(95) × × × ×
nvoOutdoorTemp SNVT_temp_p(105) × × × ×
nvoPurgeInfoC1 UNVT_purge_information × ×
nvoPurgeInfoC2 UNVT_purge_information ×
nvoRfgtDischTmpA SNVT_temp_p(105) × × x
nvoRfgtDischTmpB SNVT_temp_p(105) x
nvoRfgtDischTmpC SNVT_temp_p(105) x
nvoRfgtDischTmpD SNVT_temp_p(105) ×
nvoRfgtDischTmpE SNVT_temp_p(105)
nvoRfgtDischTmpF SNVT_temp_p(105)
nvoSecCndEntWTmp SNVT_temp_p(105) ×
nvoSecCndLvgWTmp SNVT_temp_p(105) ×
nvoStartsRunTmA UNVT_starts_runtime × × × × × x
nvoStartsRunTmB UNVT_starts_runtime × × × x
nvoStartsRunTmC UNVT_starts_runtime × × × x
nvoStartsRunTmD UNVT_starts_runtime × × × × x
nvoStartsRunTmE UNVT_starts_runtime ×
nvoStartsRunTmF UNVT_starts_runtime ×
nvoStatus.Invalid_Request SNVT_obj_status(93) × × × × x
nvoStatusOutputs SNVT_state(83) × × × × × x
nvoUnitCurrent UNVT_3phase_current ×
nvoUnitPower SNVT_power_f(57) × × × x
nvoUnitVoltage UNVT_3phase_volt ×
nvoVoltageA UNVT_3phase_volt × × × × x
nvoVoltageB UNVT_3phase_volt x
nvoVoltageC UNVT_3phase_volt x
nvoVoltageD UNVT_3phase_volt × x
nvoVoltageE UNVT_3phase_volt
nvoVoltageF UNVT_3phase_volt
30 ACC-SVN25C-EN
Appendix C: User-defined Types
This appendix includes
• User-defined network variable types
• User-defined configuration property types
These user-defined types have been created by Trane for use by Trane controllers. In many cases,
the Trane user-defined types contain standard network variable types (SNVTs) to make them easy
to understand.
User-defined Network Variable Types (UNVTs)

UNVT_purge_information
Table 1. Structure definition
Field in
structure Byte Bit definition Description
SNVT_state Validity of bits 8–15
Byte 0 (MSB) Bits 0–7 (MSB)
purge status (1 = Valid)
Bit 8 Refrigeration Circuit On (1)
Bit 9 Pumping Out (1)
Bit 10 Regenerating (1)
Bits 11–15(LSB) Not Used
Purge 24 Hour
SNVT_time_f Byte 1–2 (LSB)
Pumpout Average
UNVT_starts_runtime

Field in structure Definition
SNVT_count_f Compressor Starts
SNVT_time_f Compressor Run Time
UNVT_3phase_current

SNVT_amp_ac L1 Current (Amps)
SNVT_lev_percent L1 Current (%RLA)
ACC-SVN25C-EN 31
UNVT_3phase_volt
SNVT_volt_ac AB Voltage
SNVT_volt_ac BC Voltage
SNVT_volt_ac CA Voltage
UNVT_refrig
Table 5. Range of enumeration values
Enumeratio Description
n Definition (reference: ARI guideline K)
0 RT_R11 R-11 (Trichlorofluoromethane)
1 RT_R12 R-12 (Dichlorodifluoromethane)
2 RT_R13 R-13 (Chlorotrifluoromethane)
3 RT_R13B1 R-13B1 (Bromotrifluoromethane)
4 RT_R14 R-14
5 RT_R21 R-21
6 RT_R22 R-22 (Chlorodifluoromethane)
7 RT_R23 R-23 (Trifluoromethane)
8 RT_R32 R-32
9 RT_R40 R-40
10 RT_R112 R-112
11 RT_R113 R-113 (Trichlorotrifluoroethane)
12 RT_R114 R-114 (Dichlorotetrafluoroethane)
13 RT_R115 R-115
14 RT_R116 R-116
15 RT_R123 R-123 (Dichlorotrifluoroethane)
16 RT_R124 R-124 (Chlorotetrafluoroethane)
17 RT_R125 R-125
18 RT_R134a R-134a (Tetrafluoroethane)
19 RT_R141B R-141B
20 RT_R142B R-142B
21 RT_R143A R-143A
22 RT_R152A R-152A
R-401A (Chlorodifluoromethane,
23 RT_R401A Difluoroethane,
Chlorotetrafluoroethane)
R-401B (Chlorodifluoromethane,
24 RT_R401B Difluoroethane,
Chlorotetrafluoroethane)
25 RT_R402A
Pentafluoroethane, Propane)
26 RT_R402B
Pentafluoroethane, Propane)
27 RT_R403B
Octafluoropropane, Propane)
R-404A (Pentafluoroethane,
28 RT_R404A
Trifluoroethane, Tetrafluoroethane)
32 ACC-SVN25C-EN
Table 5. Range of enumeration values (continued)

Enumeratio Description
n Definition (reference: ARI guideline K)
R-406A (Chlorodifluoroethane, Isobutane,
29 RT_R406A
Chlorodifluoroethane)
R-407A (Difluoromethane,
30 RT_R407A
Pentafluoroethane, Tetrafluoroethane)
R-407B (Difluoromethane,
31 RT_R407B
R-407C (Difluoromethane,
32 RT_R407C
33 RT_R408A
Trifluoroethane, Pentafluoroethane)
34 RT_R409A Chlorotetrafluoroethane,
Chlorodifluoroethane)
R-410A (Difluoromethane,
35 RT_R410A
Pentafluoroethane)
36 RT_R414B Chlorotetrafluoroethane,
Chlorodifluoroethane, Isobutane)
R-416A (Tetrafluoroethane,
37 RT_R416A
Chlorotetrafluorethane, Butane)
R-500 (Dichlorodifluoromethane,
38 RT_R500
Difluoroethane)
R-502 (Chlorodifluoromethane,
39 RT_R502
Chloropentafluoroethane)
R-503 (Chlorotrifluoromethane,
40 RT_R503
Trifluoromethane)
R-507 (Pentafluoroethane,
41 RT_R507
Trifluoroethane)
R-508B (Trifluoromethane,
42 RT_R508B
Hexafluoroethane)
43 RT_R717 R-717
44-254 RT_RESERVED Reserved for future use
0xFF RT_INVALID Invalid (default)
ACC-SVN25C-EN 33
User-defined Configuration Property Types

UCPT_chiller_type
Item Type Bytes Range and meaning
Model information
Unsigned 8-bit Range of enum values in
(See enumeration 1
(enum) UCPT_chiller_type
definitions table below.)
Capacity of unit
Unit capacity SNVT_power_f 4
(in watts)
0 = water-cooled
Unsigned 8-bit
Cooling type 1 1 = air-cooled
(enum)
2–254 = unused
Number of
Unsigned 8-bit 1 0-4; number of circuits on unit
circuits
Number of compressors on 0-3; number of compressors
Unsigned 8-bit 1
circuit 1 on circuit 1
Number of compressors on 0-3; number of compressors
Unsigned 8-bit 1
circuit 2 on circuit 2
Total length 9
Table 7. Enumeration definitions for UCPT_chiller_type

Enumeration definition (Trane
Enumeration chiller model designators)
0 RTA
1 CVH
2 CVG
3 CVR
4 CDH
5 RTH
6 CGW
7 CGA
8 CCA
9 RTW
10 RTX
11 RTU
12 CCU
13 CXA
14 CGC
15 RAU
16–254 Unused
255 Invalid (unknown)
34 ACC-SVN25C-EN
UCPT_manufacturing_location
Table 8. Range of enumeration values
Enumeration Enumeration definition
0 Field applied (unknown location)
1 La Crosse, Wisconsin, USA
2 Pueblo, Colorado, USA
3 Charmes, France
4 Rushville, Indiana, USA
5 Macon, Georgia, USA
6 Waco, Texas, USA
7 Lexington, Kentucky, USA
8 Forsyth, Georgia, USA
9 Clarksville, Tennessee, USA
10 Ft. Smith, Arkansas, USA
11 Penang, Malaysia
12 Colchester, UK
13 Curitiba, Brazil
14 Taicang, China
15 Taiwan
16 Epinal, France
17 Golbey, France
18 to 254 Unused
255 Invalid (unknown location)
ACC-SVN25C-EN 35
Appendix D: Network Variable And Configuration
Property Definitions
This appendix includes
• Network variable input definitions
• Network variable output definitions
• Configuration property definitions
Note: Not all variables are available for every chiller. For a listing of variables for each chiller type,
see , “Appendix A: Network Variables Lists For Each Chiller Type” or , “Appendix B: Network
Variables Listed Alphabetically.”
Network Variable Input Definitions

The network variable input definitions are listed alphabetically by network variable.
nviBaseLdgReq
Base loading Auto/On request, SNVT_switch
This input requests the chiller to use the base loading control method. With this method, the chiller
controls to a requested capacity level rather than to a chilled-water or hot-water setpoint. This
variable is used as an Auto/On and cannot be used to force the chiller to exit base loading control.
• Default: Uses nciBaseLdgReq
• Invalid value: 0xFF, 0xFF
Valid range (uses 2-state definition of SNVT_switch)

Resulting
Value byte State byte interpretation
Any 0 Auto (0)
0 1 Auto (0)
>0 1 On (1)
Any 0xFF Invalid
nviBaseLdgSetpt
Base loading setpoint, SNVT_lev_percent
This input network variable is the requested capacity level the chiller should control to when using
the Base Loading control method. Any setpoint value received will be clamped into a valid range
by the chiller.
• Default: Uses nciBaseLdgSetp
• Invalid value: 0x7FFF = 163.835%
• Range: -163.84% to 163.83% (limited at chiller) or invalid
nviCapacityLim
Capacity limit setpoint, SNVT_lev_percent
• Default: Uses nciCapacityLim
• Range: -163.84% to 163.83% (limited at chiller) or Invalid
This input network variable sets the maximum capacity level the chiller can use. This level cannot
be adjusted above the manufacturer-specified limit.
36 ACC-SVN25C-EN
Appendix D: Network Variable And Configuration Property Definitions
nviChillerEnable
Chiller enable/disable request, SNVT_switch
• Default: Uses nciChillerEnable
This input variable provides the mechanism to enable (start) the chiller to run if operating
conditions are satisfied, or to disable (stop) the chiller from running.

Value Resulting
byte State byte interpretation
Any 0 Disable (0)
0 1 Disable (0)
>0 1 Enable (1)
Any 0xFF Invalid
nviCoolSetpt
Chilled water setpoint, SNVT_temp_p
• Default: Uses nciCoolSetpt
• Invalid value: 0x7FFF = 327.67°C
• Range: -273.17°C to 327.66°C (limited at chiller) or Invalid
This input variable provides the desired setpoint of the evaporator leaving water when the chiller
is operating in cooling mode. This will be ignored if the control is in heat mode. The cooling mode
is the normal mode of chiller operation, unless overridden to another mode. Any setpoint value
received will be clamped into a valid range by the chiller.
nviHeatSetpt
Hot water setpoint, SNVT_temp_p
• Default: Uses nciHeatSetpt
• Range: -273.17°C to 327.66°C (limited at chiller) or Invalid
This input network variable provides the heating setpoint when the chiller is operating in the heat
mode. This will be ignored if the control is in cooling mode. Any setpoint value received will be
clamped into a valid range by the chiller.
nciLocation
Location label, SNVT_str_asc
• Default: “No Unit Config Required”
• SCPT reference: SCPTlocation (17)
• Range: Any valid string
This configuration property provides a description of the location of the unit.
ACC-SVN25C-EN 37
nviMode
Operating mode request, SNVT_hvac_mode
This input network variable provides the mode of operation of the chiller and provides the ability
for another node on the network to place a chiller in another mode.
Structure definition
Enumeration
Type name Enumeration definitiona Default
1 = HVAC_HEAT
3 = HVAC_COOL
Unsigned 8-bit hvac_t uses nciMode
10 = HVAC_FREE_COOL
11 = HVAC_ICE
a Other enumeration definitions for hvac_t, as defined by LonMark, are not used by the Tracer
CH530/531 and have no effect on its operations.
nviNoiseRdcnReq
Noise reduction Auto/On request, SNVT_switch
This input network variable requests the chiller to enter a mode of operation where the noise of the
unit is reduced. When Noise Reduction is active the chiller reduces speed of the condenser fans
in order to create less noise.
• Default: Uses nciNoiseRdcnReq
Value Resulting
byte State byte interpretation
Any 0 Auto (0)
0 1 Auto (0)
>0 1 On (1)
Any 0xFF Invalid
nviRequest
Status request input, SNVT_obj_request
Provides a mechanism for the mode of an object to be requested. Default value will be adopted at
power-up or until an update is received. Does not use the receive heartbeat function. Responses
are received through nvoStatus.
Enumeration Invalid
Item Type definition Default value
0 = node object
1 = chiller object
Object ID Unsigned 16-bit 65535 65535
2 to 65535 are not
valid
Unsigned 8-bit enum See next table:
Object request 255 255
object_request_t “Object request”
38 ACC-SVN25C-EN
Object request
Controller
Enumeration definition Description interpretation
Enable object and remove
0 = RQ_NORMAL Report object status
override
2 = RQ_UPDATE_STATUS Just report object status Report object status
5 = RQ_REPORT_MASK Report status bit mask Report status bit mask
9 = RQ_CLEAR_STATUS Clear object status Report object status
10 = RQ_CLEAR_ALARM Clear object alarm Clear object alarm
16 to 255 = RQ_NUL Value not available Ignore object request
Note: Other enumeration definitions for object_request_t, as defined by LonMark, are not used by the Tracer
CH530/531 and have no effect on its operation.
Chiller object behavior in response to object request

Request code Chiller object behavior
normal Status of the object is sent.
update status Status of the object is sent.
report mask Send a mask of supported status bits.
clear status Status of the object is sent.
Sends a command to the Chiller to clear all "remote reset" diagnostics.
clear alarm
Status of the object is then sent with alarm bit cleared.
NUL Ignore object request.
Node object behavior in response to object request

Request code Node object behavior
Status of the node object is sent. The status will be the same as the
normal
chiller object since it is the only object in the device.
update status
report mask Send a mask of supported status bits.
clear status
Sends a command to the chiller to clear all "remote reset" diagnostics.
clear alarm
Status of the object is then sent with alarm bit cleared.
NUL Ignore object request.
ACC-SVN25C-EN 39
Network Variable Output Definitions

The network variable output definitions are listed alphabetically by network variable.
nvoActiveBLSetpt
Active base loading setpoint, SNVT_lev_percent
This variable indicates the value of the Base Loading Setpoint actively being used by the chiller
when in base loading mode of operation.
• Default: 0x7FFF = 163.835%
nvoActiveSetpt
Active chilled water or hot water setpoint, SNVT_temp_p
This variable indicates the value of the Active Chilled Water Setpoint or Active Hot Water Setpoint
actively being used by the chiller. The Active Hot Water Setpoint will be displayed when in heat
mode, otherwise the Active Chilled Water Setpoint will be displayed.
• Default: 0x7FFF = 327.67°C
nvoActualCap
Actual running capacity, SNVT_lev_percent
This network variable provides the level of capacity at which the chiller is currently operating. It may
be more or less than the nominal value of the chiller’s capacity.
• Default: 0x7FFF = 163.835%
nvoAirFlowPctC1
Air flow percent—circuit 1, SNVT_lev_percent
This network variable provides the approximate air flow percentage of circuit 1.
• Default: 0x7FFF = 163.835%
nvoAirFlowPctC2
Air flow percent—circuit 2, SNVT_lev_percent
This network variable provides the approximate air flow percentage of circuit 2.
• Default: 0x7FFF = 163.835%
40 ACC-SVN25C-EN
nvoAlarmDescr
Alarm description, SNVT_str_asc
This network variable provides alarm messages based on manufacturer-determined criteria. Alarm
text will vary significantly based on the chiller model. See the corresponding chiller literature for
more details on the diagnostics. The format will be as follows:
“s nnnnnnnnnnnnnnnnnnnnnnnnnnnnn”.
s Indicates the severity of the diagnostic. There are five possibilities. There is an ASCII space
between s and the first n.
P = normal, last reset resulted from a power up

0 = normal, last reset was not from power up
1 = informational message (handle at next scheduled routine maintenance)
2 = service required (handle at normal rates during normal working hours)
3 = critical alarm (handle now, cost is no object)
n Represents 29 ASCII characters that form the human readable message. The last n must be
null (0x00). Can be less than 29 characters, but not more.
For “0” or “P” this text must be “Normal”.

• When transmitted: It is transmitted when a diagnostic occurs
• Update rate: Update occurs no faster than the configured min send time
nvoCapacityLim
Active capacity limit setpoint, SNVT_lev_percent
This variable indicates the value of the Capacity Limit Setpoint actively being used by the chiller.
• Default: 0x7FFF = 163.835
nvoCondControl
Condenser Control, SNVT_lev_percent
This network variable is the percentage of condenser water flow being requested by the controller.
• Default: 0x7FFF = 163.835%
nvoChillerStat
Chiller status, SNVT_chlr_status
This variable indicates the main running mode and states of the chiller. The modes indicate the
primary running states of the chiller and the states indicate other conditions present.
ACC-SVN25C-EN 41
Enumeration
Item Type name Definition Description
00 = CHLR_OFF Chiller off
01 = CHLR_START Chiller in start mode
02 = CHLR_RUN Chiller in run mode
chiller_run_mode unsigned 8-bit chiller_t
03 = CHLR_PRESHUTDN Chiller in pre-shutdown mode
04 = CHLR_SERVICE Chiller in service mode
any others = CHLR_NULL
01 = HVAC_HEAT Heating only
03 = HVAC_COOL Cooling only
chlr_op_mode unsigned 8-bit hvac_t 0A = HVAC_FREE_COOL Free cooling
0B = HVAC_ICE Ice-making mode
any others = HVAC_NULL
1 = Chiller has an active diagnostic
that caused the chiller to be
bit 0 (MSB) in_alarm shutdown. (These are shutdown
alarms, not warnings.)
0 = No shutdown alarms are present.
1 = Chiller is available to run or is
bit 1 run_enabled currently running.
0 = Chiller is not permitted to run.
1 = Chiller is in local mode. BAS is
disabled in the Setpoint Source and
the chiller will ignore communications.
bit 2 local
no enum bit field 0 = Chiller is not in local mode and
chlr_state unsigned 8-bit
only network visible values may be
changed remotely.
1 = Conditions may exist that prevent
the chiller from reaching setpoint.
bit 3 limited
0 = Chiller is not restricted from
attempting to reach setpoint.
1 = Chilled water flow is detected.
bit 4 chw_flow
0 = No chilled water flow is observed.
1 = Condenser water flow is detected.
bit 5 condw_flow 0 = No condenser water flow is
observed.
42 ACC-SVN25C-EN
nvoCondFans
Condenser fan(s) running outputs, SNVT_state
This variable is used to relay information about which condenser fans (or banks of fans) on the
chiller are currently being commanded to run.
Bit position Description
Bit 0 Condenser fan(s) A exists (1=Yes)
Bit 1 Condenser fan(s) B exists (1=Yes)
Bit 2 Condenser fan(s) C exists (1=Yes)
Bit 3 Condenser fan(s) D exists (1=Yes)
Bit 4 Condenser fan(s) E exists (1=Yes)
Bit 5 Condenser fan(s) F exists (1=Yes)
Bit 6 Condenser fan(s) E exists (1=Yes)
Bit 7 Condenser fan(s) H exists (1=Yes)
Bit 8 Condenser fan(s) A On (1=On)
Bit 9 Condenser fan(s) B On (1=On)
Bit 10 Condenser fan(s) C On (1=On)
Bit 11 Condenser fan(s) D On (1=On)
Bit 12 Condenser fan(s) E On (1=On)
Bit 13 Condenser fan(s) F On (1=On)
Bit 14 Condenser fan(s) G On (1=On)
Bit 15 (LSB) Condenser fan(s) H On (1=On)
nvoCondRfgtPrsC1
Condenser refrigerant pressure—circuit 1, SNVT_press_f
This network variable provides the pressure of the refrigerant in the condenser on circuit 1. This
refrigerant pressure is sometimes referred to as the condenser discharge pressure.
• Default: NaN
• Invalid value: NaN
nvoCondRfgtPrsC2
• Default: NaN
nvoCondRfgtPrsC3
• Default: NaN
ACC-SVN25C-EN 43
nvoCondRfgtPrsC4
• Default: NaN
nvoCondRfgtTmpC1
Condenser refrigerant temperature—circuit 1, SNVT_temp_p
This network variable provides the temperature of the refrigerant in the condenser on circuit 1. This
refrigerant temperature is sometimes referred to as the condenser discharge temperature.
nvoCondRfgtTmpC2
nvoCondRfgtTmpC3
nvoCondRfgtTmpC4
nvoCondWFlowRate
Condenser water flow rate, SNVT_flow
This network variable provides the rate of water flow in the condenser.
• Default: 0xFFFF = 65535 L/s
• Invalid value: 0xFFFF = 65535 L/s
44 ACC-SVN25C-EN
nvoCondWtrFlow
Condenser water flow status, SNVT_switch
This network variable indicates that there is water flowing through the condenser.
Value
byte State byte Resulting interpretation
0 0 No flow (0)
100 1 Flow (1)
0xFF 0xFF Invalid
nvoCondWtrPump
Condenser water pump output, SNVT_switch
This variable indicates a request from the chiller to turn on the condenser water pump.)

Value
0 0 Pump Off (0)
100 1 Pump On (1)
0xFF 0xFF Invalid
nvoCprsrsRunning
Compressor running outputs, SNVT_state
This variable is used to relay information about which compressors on the chiller are running.
Bit 0 Compressor A exists (1 = Yes)
Bit 1 Compressor B exists (1 = Yes)
Bit 2 Compressor C exists (1 = Yes)
Bit 3 Compressor D exists (1 = Yes)
Bit 4 Compressor E exists (1 = Yes)
Bit 5 Compressor F exists (1 = Yes)
Bits 6–7 Not used
Bit 8 Compressor A running (1 = On)
Bit 9 Compressor B running (1 = On)
Bit 10 Compressor C running (1 = On)
Bit 11 Compressor D running (1 = On)
Bit 12 Compressor E running (1 = On)
Bit 13 Compressor F running (1 = On)
Bits 14–15(LSB) Not used
ACC-SVN25C-EN 45
nvoCurrentX
Current per line—compressor X,* UNVT_3phase_current
nvoCurrentA
nvoCurrentB
nvoCurrentC
nvoCurrentD
nvoCurrentE
nvoCurrentF
These network variables provides a measurement of the three-line currents at compressor X
(*where X = A, B, C, D, E and/or F, depending on the network variable, in amperes and/or in %RLA).
There are separate network variables for each compressor.
Field in structure Description
SNVT_amp_ac L1 current (Amps)—compressor X
SNVT_lev_percent L1 current (%RLA)—compressor X
Note: X = A, B, C, D, E, and/or F, depending on the network variable.
nvoEntCndWTemp
Condenser entering water temperature, SNVT_temp_p
This network variable provides the temperature of the water entering the condenser.
nvoEntChWTemp
Evaporator entering water temperature, SNVT_temp_p
This network variable provides the temperature of the water entering the evaporator.
nvoEvapRfgtPrsC1
Evaporator refrigerant pressure—circuit 1, SNVT_press_f
This network variable provides the pressure of the refrigerant in the evaporator on circuit 1. This
refrigerant pressure is sometimes referred to as the evaporator suction pressure.
• Default: NaN
46 ACC-SVN25C-EN
nvoEvapRfgtPrsC2
• Default: NaN
nvoEvapRfgtPrsC3
• Default: NaN
nvoEvapRfgtPrsC4
• Default: NaN
nvoEvapRfgtTmpC1
Evaporator refrigerant temperature—circuit 1, SNVT_temp_p
This network variable provides the temperature of the refrigerant in the evaporator on circuit 1. This
refrigerant temperature is sometimes referred to as the evaporator suction temperature.
nvoEvapRfgtTmpC2
nvoEvapRfgtTmpC3
ACC-SVN25C-EN 47
nvoEvapRfgtTmpC4
nvoEvapWFlowRate
Evaporator water flow rate, SNVT_flow
This network variable provides the rate of water flow in the evaporator.
• Default: 0xFFFF = 65535 L/s
• Invalid value: 0xFFFF = 65535 L/s
nvoEvapWtrFlow
Evaporator water flow status, SNVT_switch
This network variable indicates that there is water flowing through the evaporator.

Value
0 0 No flow (0)
100 1 Flow (1)
0xFF 0xFF Invalid
nvoEvapWtrPump
Evaporator water pump output, SNVT_switch
This network variable indicates a request from the chiller to turn on the evaporator water pump.

Value
0 0 Pump Off (0)
100 1 Pump On (1)
0xFF 0xFF Invalid
nvoFileDirectory
File directory, SNVT_address
This network variable points to a file directory containing descriptors for the files in the device. It
is used because the LCI-C implements configuration properties as configuration parameter files
accessed by network management read/write messages.
• Default: None
• Invalid value: None
• Range: 0x4000 to 0xFCFF
48 ACC-SVN25C-EN
nvoHiSideOilPrsX
High side oil pressure—compressor X,* SNVT_press_f
nvoHiSideOilPrsA
nvoHiSideOilPrsB
nvoHiSideOilPrsC
nvoHiSideOilPrsD
nvoHiSideOilPrsE
nvoHiSideOilPrsF
This network variable measures the pressure of the oil at the high-pressure side of compressor X
(*where X = A, B, C, D, E, or F, depending on the network variable). There are separate network
variables for each compressor.
• Default: NaN
nvoLoSideOilPrsX
Low side oil pressure—compressor X,* SNVT_press_f
nvoLoSideOilPrsA
nvoLoSideOilPrsB
nvoLoSideOilPrsC
nvoLoSideOilPrsD
nvoLoSideOilPrsE
nvoLoSideOilPrsF
This network variable measures the pressure of the oil at the low-pressure side of compressor X
(*where X is A, B, C, D, E, or F, depending on the network variable). There are separate network
• Default: NaN
nvoLvgChWTemp
Evaporator leaving water emperature, SNVT_temp_p
This network variable provides the temperature of the water leaving the evaporator.
nvoLvgCndWTemp
Condenser leaving water temperature, SNVT_temp_p
This network variable provides the temperature of the water leaving the condenser.
nvoOilTempX
Oil temperature—compressor X,* SNVT_temp_p
nvoOilTempA
nvoOilTempB
nvoOilTempC
ACC-SVN25C-EN 49
nvoOilTempD
nvoOilTempE
nvoOilTempF
This network variable provides the temperature of the oil in the compressor X (*where X is A, B,
C, D, E, or F depending on the network variable.) There are separate network variables for each
compressor.
nvoOnOff
Chiller running state, SNVT_switch
This variable indicates whether the chiller is on (currently doing either cooling or heating) or is
considered off (currently doing neither cooling nor heating)

Value
0 0 Off (0)
100 1 On (1)
0xFF 0xFF Invalid
nvoOutdoorTemp
Outdoor air temperature, SNVT_temp_p
This network variable provides the temperature of the outdoor air.
nvoPurgeInfoC1
Purge information—circuit 1, UNVT_purge_information
This variable is used to relay state information about the purge system on circuit 1 of the chiller.
Refrigeration Circuit On indicates that the Purge condensing unit is operating its refrigerant circuit
and is attempting to extract non-condensable gasses from the chiller refrigerant. Pumping Out
indicates that the purge unit is attempting to rid itself of collected non-condensable gasses.
Regenerating indicates that the purge carbon bed is going through a regeneration cycle. The Purge
24 Hour Pumpout Average is the amount of pump-out time over the last sliding 24-hour window.
Field in
structure Byte Bit definitions Description
SNVT_state Validity of bits 8–15 (1 =
purge status Valid)
Refrigeration Circuit On
Bit 8
(1)
Bits 11–15 (LSB) Not used
Purge 24 Hour
Pumpout Average
50 ACC-SVN25C-EN
nvoPurgeInfoC2
Purge information–circuit 2, UNVT_purge_information
This variable is used to relay state information about the purge system on circuit 2 of the chiller.
Refrigeration Circuit On indicates that the Purge condensing unit is operating its refrigerant circuit
and is attempting to extract non-condensable gasses from the chiller refrigerant. Pumping Out
indicates that the purge unit is attempting to rid itself of collected non-condensable gasses.
Regenerating indicates that the purge carbon bed is going through a regeneration cycle. The Purge
24 Hour Pumpout Average is the amount of pumpout time over the last sliding 24 hour window.
Field in
structure Byte Bit definitions Description
SNVT_state: Purge Validity of bits 8–15 (1 =
Status Valid)
Refrigeration Circuit On
Bit 8
(1)
Bits 11-15 (LSB) Not Used
Purge 24 Hour
Pumpout Average
nvoRfgtDischTmpX
Refrigerant discharge temperature—compressor X,* SNVT_temp_p
nvoRfgtDischTmpA
nvoRfgtDischTmpB
nvoRfgtDischTmpC
nvoRfgtDischTmpD
nvoRfgtDischTmpE
nvoRfgtDischTmpF
This network variable provides the temperature of the refrigerant being discharged from
compressor X (*where X is A, B, C, D, E, or F, depending on the network variable). There are
separate network variables for each compressor.
nvoSecCndEntWTmp
Second condenser entering water temperature, SNVT_temp_p
This network variable provides the temperature of the water entering the second condenser.
nvoSecCndLvgWTmp
Second condenser leaving water temperature, SNVT_temp_p
This network variable provides the temperature of the water leaving the second condenser.
ACC-SVN25C-EN 51
nvoStartsRunTmX
Starts and run time—compressor X,* UNVT_starts_runtime
nvoStartsRunTmA
nvoStartsRunTmB
nvoStartsRunTmC
nvoStartsRunTmD
nvoStartsRunTmE
nvoStartsRunTmF
This network variable provides the number of starts and the amount of running time over the life
of compressor X (*where X is A, B, C, D, E, or F, depending on the network variable.) There are
separate network variables for each compressor.
SNVT_count_f Starts—compressor X
SNVT_time_f Run time—compressor X
nvoStatus
Status request output, SNVT_obj_status
This network variable indicates the status of the objects in the node. Sent in response to nviRequest
or poll or heartbeat. Polling does not update nvoStatus. For example, polling will not change the
alarm bit. Only nviRequest and heartbeat update nvoStatus.
Structure definition (6 bytes)

Byte
Item Type Report mask # Bit # Definition
0 = node object
object id unsigned 16-bit 0, 1 1 = chiller object
2 to 65535 = invalid
1 = requested ID is not implemented in this
invalid_ida bit 0 2 7
node
invalid_requestb bit 0 2 6 1 = request for unimplemented function
1 = object is in alarm (only shutdown
in_alarmc bit 1 4 6
alarms, not warnings)
1 = status is an event mask (set for
report_maskd bit 1 4 4
RQ_REPORT_MASK)
a invalid_id: A status of invalid_id is reported whenever a nviRequest is received for an object id that is not implemented in the node.
b invalid_request: A status of invalid_request is reported whenever a nviRequest is received for an unimplemented function.
c in_alarm: A value of TRUE is reported if the controller has a diagnostic condition.
d report_mask: Report_mask status is used to document the status bits that are supported by the object. The obj_request code RQ_REPORT_MASK
causes the object to respond with a mask of supported status bits by way of nvoStatus. A ONE in the mask means that the object may set the
corresponding bit in the object status when the condition defined for that bit occurs. A ZERO means that the bit will never be set by the object.
When reporting status in response to a RQ_REPORT_MASK, the report_mask bit must be set to distinguish this from other forms of status.
Note: Any bits within SNVT_obj_status that are defined by the LonMark profile but are not listed above, are not used by the Tracer CH530/531 and
have no affect on its operation.
• When Transmitted: nvoStatus is transmitted whenever a request is received on the nviRequest

input and as one of the heartbeat nvos. The node object status is sent during the first heartbeat
nvoStatus transmission. Then the chiller object status is sent during the second heartbeat
nvoStatus transmission, depending on which profile is being used. And then the cycle repeats.
52 ACC-SVN25C-EN
• Update Rules: The application must update the status such that a poll of the status following
the request returns the most recent data.
• Update Rate: Send heartbeat time
• Default Service Type: Unacknowledged
nvoStatusOutputs
Status outputs, SNVT_state
This variable is used to relay state information about the chiller. Max Capacity provides an
indication that all available chiller capacity is being used. When the Head Relief Request bit is set,
the chiller is asking an outside system to provide more heat rejection from the condenser water
loop. Additional heat rejection creates lower condenser water loop temperatures, which lowers the
condenser refrigerant pressure (head). Base Loading Active indicates whether the Base Loading
control method is currently being used. Hot Gas Bypass Active is set when Hot Gas Bypass is being
performed by the chiller. Noise Reduction Active is set when the chiller is in a state where the noise
is being reduced. The efficiency of the chiller may be reduced in this mode. In Defrost indicates
that one or more circuits on the chiller are in a defrost mode.
Bits 0–7 Validity of bits 8–15 (1 = valid)
Bit 8 Max Capacity (1)
Bit 9 Head Relief Request (1)
Bit 10 Base Loading Active (1)
Bit 11 Hot Gas Bypass Active (1)
Bit 12 Noise Reduction Active (1)
Bit 13 In Defrost (1)
Bits 14–15(LSB) Not Used
nvoUnitCurrent
Unit current per line, UNVT_3phase_current
This network variable provides the measurement of the three-line currents of the chiller in amperes
(Amps) and/or %RLA.
SNVT_amp_ac L1 current (Amps)
SNVT_lev_percent L1 current (%RLA)
nvoUnitPower
Unit power consumption, SNVT_power_f
This network variable provides the measurement of the power being consumed by the chiller.
• Default: NaN
ACC-SVN25C-EN 53
nvoUnitVoltage
Unit voltage per phase, UNVT_3phase_volt
This network variable provides the measurement of the three phase voltages of the chiller.
SNVT_volt_ac AB voltage
SNVT_volt_ac BC voltage
SNVT_volt_ac CA voltage
nvoVoltageX
Voltage per phase—compressor X,* UNVT_3phase_volt
nvoVoltageA
nvoVoltageB
nvoVoltageC
nvoVoltageD
nvoVoltageE
nvoVoltageF
This network variable provides a measurement of the three phase voltages at compressor X
(*where X is A, B, C, D, E, or F depending on the network variable.) There are separate network
SNVT_volt_ac AB voltage—compressor X
SNVT_volt_ac BC voltage—compressor X
SNVT_volt_ac CA voltage—compressor X
54 ACC-SVN25C-EN
Configuration Property Definitions

The configuration property definitions (implemented as configuration parameters) are listed
alphabetically by nci name.
nciBaseLdgReq
Default Value for nviBaseLdgReq, SNVT_switch, level 1
This configuration property sets the default value for the base loading request (nviBaseLdgReq) of
the chiller, unless the configuration property nciDefaults = 1. When nciDefaults = 1, the Tracer
CH530/531 ignores the BAS value and chooses from other available requests (external or front
panel) based on internal arbitration rules.
• Range: Same as nviBaseLdgReq
• Default: Invalid (0xFF, 0xFF)
• UCPT reference: None
nciBaseLdgSetpt
SNVT_lev_percent, level 1
This configuration property sets the default value for the base loading setpoint (nviBaseLdgSetpt)
of the chiller, unless the configuration property nciDefaults = 1. When nciDefaults = 1, the Tracer
CH530/531 ignores the BAS value and chooses from other available setpoints (external or front
• Range: Same as nviBaseLdgSetpt
• Default: Invalid (0x7FFF)
• UCPT reference: None
nciCapacityLim
Default value for nviCapacityLim, SNVT_lev_percent, level 1
This configuration property sets the default value for the Capacity Limit (nviCapacityLim) of the
chiller, unless the configuration property nciDefaults = 1. When nciDefaults = 1, the Tracer CH530/
531 ignores the BAS value and chooses from other available values (external or front panel) based
on internal arbitration rules.
• Range: Same as nviCapacityLim
• SCPT reference: SCPTlimitChlrCap (81)
nciChillerEnable
Default value for nviChillerEnable, SNVT_switch, level 1
This configuration property provides the default power up and restart modes (nviChillerEnable) of
the chiller, unless the configuration property nciDefaults = 1. When nciDefaults = 1, the Tracer
• Range: Same as nviChillerEnable
• SCPT reference: SCPTpwrUpState (73)
ACC-SVN25C-EN 55
nciChillerType
Chiller type information, UCPT_chiller_type, level 1
This configuration property defines some of the properties of the chiller. These values are set when
the LCI-C is bound into the Tracer CH530/531. It is a read-only configuration property that cannot
be modified over LonTalk communications.
Item Length Range
Range of enum values in
Model information 1 byte UCPT_chiller_type (see , “Appendix
C: User-defined Types”)
Unit capacity 4 bytes SNVT_power_f
Range of enum values (0=water-
Cooling type 1 byte
cooled, 1=air-cooled)
Number of circuits 1 byte 1–2
Number of compressors: circuit 1 1 byte 0–3
Number of compressors: circuit 2 1 byte 0–3
nciCoolSetpt
Default value for nviCoolSetpt, SNVT_temp_p, level 1
This configuration property sets the default Setpoint for the Leaving Chilled Water Temperature
(nviCoolSetpt), unless the configuration property nciDefaults = 1. When nciDefaults = 1, the Tracer
• Range: Same as nviCoolSetpt
• SCPT reference: SCPTcoolSetpoint (75)
nciDefaults
Default values, SNVT_switch, level 1
This configuration property determines which set of values will be used on power up and
communications failure. The choice is the stated default values or a list of manufacturer specified
values.
• Range:0–Use Stated Defaults
– 1–Use Manufacturer Specified Defaults
– 0xFF–Invalid (act with Default [1])
• Default: 1 = Use Manufacturer Specified Defaults
• SCPT reference: SCPTdefltBehave (71)
56 ACC-SVN25C-EN
nciDefaults setting
Action on communication loss
nciDefaults setting Action at power-up (nciRcvHrtBt timeout)
For each nvi individually, when it has not been heard
Set each of the nvis equal to the value that is stored
0—Use Stated defaults from for the Receive Heartbeat time, it should be set
in their corresponding nci.
back to the value that is in its corresponding nci.
Set each of the nvis equal to a value that we hardcode
in the LCI. Where possible this value should be an
invalid value that causes the controller to use its front
In this case, the nvis should not be changed. We have
1—Use Manufacturer panel inputs. If this is not possible, it should be a safe
defined Manufacturer Specified on a Comm Loss to
Specified Defaults default.
mean that we continue using the last sent value.
For this project, the Manufacturer Specified Defaults
should be equal to the default value for each of the
nci's, which have this same effect.
0xFF Invalid (act with Default [1]) Invalid (act with Default [1])
nciDevMajVer
Device Major Version, unsigned 8-bit, level 1
This configuration property displays the major version number for the software in the device. It is
read-only.
• Range: 0–254
• Default: N/A
• SCPT reference: SCPTdevMajVer (165)
nciDevMinVer
Device Minor Version, unsigned 8-bit, level 1
This configuration property displays the minor version number for the software in the device. It is
read-only.
• Range: 0–254
• Default: N/A
• SCPT reference: SCPTdevMinVer (166)
nciHeatSetpt
Default Value for nviHeatSetpt, SNVT_temp_p, level 1
This configuration property sets the default Setpoint for the Leaving Chilled Water Temperature
(nviHeatSetpt) when in heating mode, unless the configuration property nciDefaults = 1. When
nciDefaults = 1, the Tracer CH530/531 ignores the BAS value and chooses from other available
setpoints (external or front panel) based on internal arbitration rules.
• Range: Same as nviHeatSetpt
• SCPT reference: SCPTheatSetpoint (78)
ACC-SVN25C-EN 57
nciMinOutTm
Minimum send time, SNVT_time_sec, level 1
This is the minimum period of time between any two network variable output transmissions. It is
only used by send on delta and is not used by the send on heartbeat function. If nciMinOutTm =
0x7FFF (6,553.5 s), which is the not valid value, the controller will use the default value of 2.5 s for
the minimum send time. If nciMinOutTm = 0, there is no minimum time requirement between
transmissions. Transmissions will happen as fast as possible (however send on delta still applies)
when nciMinOutTm = 0.
• Range: 0–6, 553.4 s, 0 disables
• Default: 2.5 s (0x0019)
• SCPT reference: SCPTminSendTime (52)
nciMfgLocation
Chiller manufacturing location, UCPT_manufacturing_location, level 1
This configuration property defines the location that the chiller was manufactured. It will be set
when the LCI-C is bound into the Tracer CH530/531. It is a read-only configuration property that
cannot be modified over LonTalk communications.
• Range: Range of enum values
• Default: Invalid (0xFF)
• UCPT reference: UCPT_manufacturing location (see , “Appendix D: Network Variable And
Configuration Property Definitions”)
nciMode
Default value for nviMode, SNVT_hvac_mode, level 1
This configuration property sets the default operating mode of the chiller (nviMode), unless the
configuration property nciDefaults = 1. When nciDefaults = 1, the Tracer CH530/531 ignores the BAS
value and chooses from other available modes (external or front panel) based on internal
arbitration rules.
• Range: Same as nviMode
• Default: HVAC_NULL (0xFF)
• SCPT reference: SCPThvacMode (74)
nciNoiseRdcnReq
Default value for nviNoiseRdcnReq, SNVT_switch, level 1
This configuration property sets the default value for the Noise Reduction Request
(nviNoiseRdcnReq) of the chiller, unless the configuration property nciDefaults = 1. When
nciDefaults = 1, the Tracer CH530/531 ignores the BAS value and chooses from other available
modes (external or front panel) based on internal arbitration rules.
• Range: Same as nviNoiseRdcnReq
• UCPT Reference: None
58 ACC-SVN25C-EN
nciRcvHrtBt
Receive heartbeat time, SNVT_time_sec, level 1
Used to control the maximum time that elapses after the last update to a network variable input
before the controller starts to use its default values.
• Range: 0–6,553.4 s, 0 disables
• Default value: Disabled (0x0000)
• SCPT reference: SCPTmaxRcvTime (48)
nciRefrigerant
Chiller refrigerant type, UNVT_refrig, level 1
This configuration property defines the type of refrigerant that the chiller uses. It will be set when
the LCI-C is bound into the Tracer CH530/531. It is a read-only configuration property that cannot
be modified over LonTalk communications.
• Range: Range of enum values
• Default: Invalid (0xFF)
• UCPT reference: UCPT_refrig_type
nciSndHrtBt
Send heartbeat time, SNVT_time_sec, level 1
This is the maximum period of time that will expire before each bound heartbeated network
variable output will be automatically updated once. The configured minimum send time
(nciMinOutTm) is ignored. If nciSndHrtBt = 0x7FFF (6,553.5 s), which is the not valid value, the
controller will use the default value of 300 s for the send heartbeat time.
• Range: 0–6,553.4 s, 0 disables
• Default: 300 s (0x0BB8)
• SCPT reference: SCPTmaxSendTime (49)
ACC-SVN25C-EN 59
Appendix E: Troubleshooting the LCI-C Installation
Diagnostics
Table 1 gives a list of diagnostics and their explanation. The diagnostics (printed in italics) will
appear in both DynaView or TechView.
Table 1. Troubleshooting the LCI-C installation

Symptom or Diagnostic Probable Cause Action
Chiller is not using setpoints sent by Chiller is in Local mode. Check the Setpoint Source on the DynaView (front panel).
LonTalk It must be BAS/Ext/FP on the DynaView in order for the
chiller to use remote setpoints.
Check that the network variable nvoChillerStat.local has a
value of 0, which means Remote. A value of 1 means Local.
LCI-C Software Mismatch: Use BAS Tool Neuron software does not match Flash download correct Neuron software as described in
chiller type. “Hardware and Software Installation Procedures,” p. 6
Comm Loss: Local BAS Interface IPC3 communication was lost Check wire connection between the LCI-C and the IPC3 bus.
between the Tracer CH530/531 Start TechView.
main processor and the LCI-C. Go to Binding View and make sure the LCI-C is still bound.
Replace the LCI-C hardware and repeat the installation
process in “Hardware and Software Installation
Procedures,” p. 6
Waiting for BAS Communication No heartbeated network If you have a non-Trane BAS system, upgrade from the LCI-
variable inputs have yet been C Profile Only to the LCI-C Extension.
received through LonTalk after If you have a Trane BAS system, check to make sure that the
power-up of the LCI-C LLID. If BAS system is setup to communicate with LCI-C. Otherwise,
they are not received within a simply wait until communication is established or BAS Failed
specified time, diagnostic status to Establish Communication appears.
becomes BAS Failed to Establish
Communication.a
BAS Failed to Establish Communication No heartbeated network If you have a non-Trane BAS system, upgrade from the LCI-
variable inputs have been C Profile Only to the LCI-C Extension.
received within the specified If you have a Trane BAS system, check:
time after startup.a • LonTalk communication line wiring
• That BAS is still trying to communicate with LCI-C
BAS Communication Lost Valid LonTalk message not If you have a non-Trane BAS system, upgrade from the LCI-
received within a specified C Profile Only to the LCI-C Extension.
time.a If you have a Trane BAS system, check:
• LonTalk communication line wiring
• That BAS is still trying to communicate with LCI-C
a This diagnostic can appear only if:
• The LCI-C contains LCI-C Profile Only software, and/or
• The LCI-C is connected to a Trane Tracer Summit System regardless of the software contained in the LCI-C
The Trane LCI-C has a receive heartbeat functionality that can determine if communication is lost with the BAS system. This functionality is enabled
using the heartbeat configuration variable (nciRcvHrtBt).
The LCI-C Profile Only has the receive heartbeat functionality enabled as a default (nciRcvHrtBt = 900 seconds).
The LCI-C Extension has the receive heartbeat functionality disabled as a default. (nciRcvHrtBt = 0 seconds).
Not all BAS systems use receive heartbeat functionality. Since LCI-C Extension has the receive heartbeat disabled, it accommodates better those
BAS systems that choose not to use this LonTalk feature. These diagnostics will never appear. If the receive heartbeat is enabled (nciRcvHrtBt
has a value other than zero), then the diagnostic can appear even if the non-Trane BAS system is able to read status and send values to the LCI-C.
The Tracer Summit System uses the receive heartbeat functionality and will automatically enable it upon installation by setting nciRcvHrtBt to 900
seconds (15 minutes). This then allows the LCI-C to know when communication is lost. Communication is recognized as lost when none of the
network variable inputs have been written to within nciRcvHrtBt time that was set. It doesn't matter what value is written. The same value can
be written over and over.
60 ACC-SVN25C-EN
Appendix F: Additional Resources
• RF-SLB005-EN: LCI-C LonTalk Communications Interface for Chillers.
An overview and points list of the LCI-C Extension for different chiller types.
• RTAC-SVD01A-EN: Control Operation, Setup, and Troubleshooting for RTAC Units with Tracer
CH530 Controls.
This RTAC manual has a very good general section on TechView.
• BMTX-SVN01A-EN: Tracer Summit Version 16 Hardware and Software Installation Guide.
• BMTX-SVP01A-EN: Tracer Summit Version 16 System Programming Guide.
• CGWF-SVX01A-EN: Installation, Operation, and Maintenance for Scroll Liquid Chillers,
Models CGWF/CCAF 20–60 tons.
• CTV-SVP01A-EN: CTV CH530 TechView Programming Guide.
• CTV-SVD02A-EN: CTV CH530 Diagnostics Manual.
• RTHD-SVX01C-EN: Installation, Operation, and Maintenance for Series R Helical Rotary
Liquid Chillers, Models RTHD.
• Product Support Online: http://www.ComfortSite.com and http://www.Lonmark.org
For further assistance, contact your local Trane office.
ACC-SVN25C-EN 61
Appendix G: Rover Service Tool Parts List
Table 1 lists the Rover service tool parts. Items in italics are not used in the LCI-C installation
procedure.
Table 1. Rover Version 5 parts list
Lynx Service parts
ordering Rover model mnemonic Controls part
number description number number Service part descriptions
ADP01019 S3090-0365-62 Rover Comm4 PCMCIA adapter
CAB010103 S3090-0368-62 Rover Comm4 adapter cable
Comm5 & Comm5
4950-0501 (software and CAB00283 S3090-0113-62 Rover Comm5 adapter cable
hardware) consists of:
MOD00510 S3090-0091-62 Module, transient protection w/ alligator leads
KEY00482 S3090-0127-62 Comm5 communication key for ZN010
ADP00494 S3090-0114-62 Cable adapter with 1/4-inch quick connects
Comm5 & Comm4
4020-1196 Software only—no service parts
Upgrade (software)
CAB00283 S3090-0113-62 Rover Comm5 adapter cable
Comm5 (software and
4950-0456 hardware) consists of: MOD00510 S3090-0091-62 Module, transient protection w/alligator leads
ADP01019 S3090-0365-62 Rover Comm4 PCMCIA Adapter
Comm4 (software and
4950-0502 hardware) consists of: CAB01013 S3090-0368-62v Rover Comm4 Adapter Cable
MOD00510 S3090-0091-62 Module, transient protection w/alligator leads
Comm5 software
upgrade (software)
Comm4 software
upgrade (software)
CAB00283 S3090-0113-62 Rover Comm5 Adapter Cable
Comm5 configuration
4950-0503 only (software and MOD00510 S3090-0091-62 Module, transient protection w/alligator leads
hardware) consists of:
Comm5 Configuration
only (Software)
CAB00283 S3090-0113-62 Rover Comm5 Adapter Cable
Comm5 Hardware Kit
4020-1193 (Hardware) consists of: MOD00510 S3090-0091-62 “Module, transient protection w/alligator leads
ADP00494 S3090-0114-62 “Cable adapter with 1/4-inch quick connects
Comm4 Hardware Kit ADP01019 S3090-0365-62 Rover Comm4 PCMCIA Adapter

4020-1194 (Hardware) consists of: CAB01013 S3090-0368-62 Rover Comm4 Adapter Cable
MOD00510 S3090-0091-62 Module, transient protection w/alligator leads
4950-0504 Multi-user license Software only—no service parts
Multi-user license
additional seat
62 ACC-SVN25C-EN
Glossary
binding (LonTalk) LonMark communications interface (LCI)
On LonTalk communication links, a binding links a network An interface developed by Trane to allow unit controllers
variable in one device with a network variable in another to communicate using LonTalk protocol.
device, thereby allowing the devices to share common
LCI-C Profile Only software
information, such as the same setpoint or temperature
The initial release of Trane LCI-C software, which
sensor value. This type of binding is different from a
implements only the network variables described in the
binding on a Tracer CH530/531 IPC3 communication bus.
LonMark Chiller Functional Profile.
the binding process
LCI-C Extension software
(Tracer CH530/531 IPC3
communication bus) Trane LCI-C software that implements network variables
from both the LonMark Chiller Functional Profile and Trane
On a Tracer CH530/531 IPC3 communication bus, the
Chiller Extension.
bindings process is performed with the TechView service
tool. The process installs the LLIDs on the bus so that the LonTalk Protocol
LLIDs can communicate with the main processor and are An interoperable protocol developed by the Echelon
able to function as intended. Corporation and named as a standard by the Electronics
Comm5 Industries Alliance (EIA-709.1). It is packaged on a Neuron
processor that is on the LCI-C LLID.
Trane’s implementation of the LonTalk protocol.
configuration LonTalk network
(Tracer CH530/531) A collection of LonTalk devices that communicate and
interact with one another.
Refers to the use of the TechView service tool to select
the chiller type, tonnage, and other options, of a Tracer main processor
CH530/531 controller. It also refers to adding the LCI-C as (Tracer CH530/531)
one of these options, which is necessary for the LCI-C The processor contained within the front panel of the
LLID to be installed properly on the Tracer CH530/531. Tracer CH530/531 to control the chiller and coordinate
flash download wizard (Rover) communication of the LLIDs on the IPC3 communication
bus. It stores the configuration of the CH530/531 and
A step-by-step process with Rover software to change
what LLIDs are expected to be on the communication
(flash) the Neuron software of the LCI-C.
bus.
IPC
network variable input (nvi)
Acronym for intraprocessor communications.
A controller's input data item that enables it to exchange
low-level intelligent device (LLID) data values with other devices on the LonTalk network.
An electronic board that is configured and installed on the This type of data item can be changed and controlled.
Tracer CH530/531 IPC3 communication bus in order to
network variable output (nvo)
fulfill a function for the chiller controller. The LCI-C LLID
A controller's output data item that enables it to exchange
allows the Tracer CH530/531 to communicate on a
data values with other devices on the LonTalk network.
LonTalk network.
This type of data item is for status only.
LonMark International
network variable type
LonMark International is a global membership organization
A pre-defined structure for a network variable. A network
created to promote and advance the business of efficient
variable type can be either a standard network variable
and effective integration of open, multi-vendor control
type (SNVT) or a user-defined network variable type
systems utilizing ANSI/EIA/CEA 709.1 (LonTalk) and
(UNVT).
related standards.
Neuron ID
LonMark Chiller Functional profile
A unique 48-bit digital identifying number assigned by
A standard list of network variables, mandatory and
Echelon to every Neuron processor produced. This
optional, that LonMark defines for chiller controller
number is printed on a label that is attached to the LCI-C.
communications on a LonTalk network.
ACC-SVN25C-EN 63
Glossary
Neuron IDs eliminate the need to set addresses with DIP UCPT
switches. Acronym for user-defined configuration parameter type. A
pre-defined structure for communicating configuration
Neuron software
information.
Software within the LCI-C Neuron processor that defines
its program ID and network variables. UNVT
Acronym for user-defined network variable type. See
Program ID
network variable type.
An identifier stored in the LCI-C Neuron processor that
identifies the application program that is running. All
controllers with the same Program ID have the same
network variable list.
Rover service tool
A Trane software program used as a service tool to
configure Trane LonTalk controllers, flash download
Neuron software, make LonTalk bindings between
network variables, and otherwise install devices on a
LonTalk network. Rover can also be described as a LonTalk
network management tool.
SCPT
Acronym for standard configuration parameter type. A pre-
defined structure for communicating configuration
information.
SNVT
Acronym for standard network variable type. See network
variable type.
system integration
Generally, the ability for products designed independently
to communicate with each other by using the same
communications protocol. Specifically in relation to Trane
products, the ability for them to monitor and/or control
another vendor’s equipment by using an open, standard
protocol.
TechView service tool
The service tool for the Tracer CH530/531 chiller
controller. TechView is required for adding or removing
Tracer CH530/531 LLIDs.
Tracer CH530/531
Name of a family of Trane chiller controllers. Tracer CH531
is the retrofit version of the Tracer CH530. The Tracer
CH530/531 is applied to many different chiller types and
does not indicate a particular kind of chiller.
Trane Chiller Extension
The network variables that Trane provides in addition to
the network variables provided by the LonMark Chiller
Functional Profile, 8040 Version 1. (Not all network
variables in the Trane Chiller Extension are available for
every chiller type.)
64 ACC-SVN25C-EN
Reader Response Form
Our goal is to provide
1. In a word, how would you describe this guide?
accurate and efficient _____________________________________________________
information to our
customers. Please use this 2. Using the following scale, rate the overall quality of this guide:
form to help us improve (Use the following scale.)
the quality and usability
of this guide. Make copies 1 2 3 4 5
of this form if needed.
Dreadful Terrific
3. How do you use this guide? (Choose one.)
a. I read it from beginning to end.
b. I read only the sections that pertain to my immediate needs.
c. I read only the sections that pertain to my job.
1. How easily can you find information in this guide?
1 2 3 4 5
Not easy at all Moderately Very easy
—very difficult easy
2. When you actually try the instructions described in this guide, how easily can you follow them?
1 2 3 4 5
I can’t Occasionally With
follow the the content great
instructions is confusing ease
at all.
3. How well did you understand the product before reading this guide?
1 2 3 4 5
Not at all Somewhat Thoroughly
4. How well did you understand the product after reading the guide?
1 2 3 4 5
Not at all Somewhat Thoroughly
5. The best aspect of this guide is
6. If we were to change one aspect of this guide, it should be
7. Name, e-mail address: (optional)
Please send this form 8. The best aspect of this guide is _________________________________________
by fax or mail to:
______________________________________________________________________
Trane GCC
Product Communications
4833 White Bear Parkway
St. Paul, MN 55110
9. If we were to change one aspect of this guide, it should be _______________
(fax) 651-407-4193 ______________________________________________________________________
10. Name, e-mail address: (optional)
ACC-SVN25C-EN 65
Notes
Notes
Trane optimizes the performance of homes and buildings around the world. A business of Ingersoll Rand, the
leader in creating and sustaining safe, comfortable and energy efficient environments, Trane offers a broad
portfolio of advanced controls and HVAC systems, comprehensive building services, and parts. For more
information, visit www.Trane.com.
Trane has a policy of continuous product and product data improvement and reserves the right to change design and specifications without notice.
© 2011 Trane All rights reserved

ACC-SVN25C-EN 09 Feb 2011
Supersedes ACC-SVN25B-EN (01 Sep 2006)

Hardware and Software Installation: Tracer™LCI-C For Tracer™ CH530/531 Chiller Controllers

Uploaded by

Copyright:

Available Formats

Hardware and Software Installation: Tracer™LCI-C For Tracer™ CH530/531 Chiller Controllers

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Hardware and Software Installation: Tracer™LCI-C For Tracer™ CH530/531 Chiller Controllers

Uploaded by

Copyright:

Available Formats

What is an LCI-C and what does it do?

What is an LCI-C and what does it do?

What are the steps for hardware installation of an LCI-C?

What are the steps for hardware installation of an LCI-C?

Hardware and Software

Tracer™LCI-C for Tracer™ CH530/531 Chiller

February 2011 ACC-SVN25C-EN

Warnings, Cautions, and Notices

WARNING: Indicates a potentially hazardous situation which, if not avoided,

CAUTION: Indicates a potentially hazardous situation which, if not avoided,

NOTICE: Indicates a situation that could result in equipment or property-

Appendix A: Network Variables Lists For Each Chiller Type . . . . . . . . . . . . . . . . 19

What Does an LCI-C Do?

Chiller Functional Profile

The LCI-C Extension

LCI-C Shipment And Inspection

Figure 1. Chiller control panel box

To install the LCI-C LLID:

Determine the Correct Software For Installation

Table 1.Software versions identified by chiller type

LCI-C profile only

If the LCI-C was factory installed...

If the LCI-C was ordered as a service part...

Figure 2. Connecting the TechView service tool to the LCI-C LLID

Figure 3. Main Processor software version displayed in TechView

Figure 4. Configuration view: Selecting the LCI-C (LonTalk) Extension

Figure 5. Binding view: The Bind button is activated

Figure 6. Prompt for selecting the LCI-C LLID with a magnet

10. Click Yes on the dialog box shown in Figure 6.

The smiling green face marks a device that is communicating and

The expressionless yellow face marks a device that is

Figure 8. Binding completed successfully

Finish Software Installation Procedure With The Rover Service Tool

Figure 9. Connecting the Rover service tool to the LCI-C LLID

Figure 11. Step 1. Discover link

Figure 12. Step 2. Select an image file

Click Next to go to Step 3 (see Figure 13 on page 16).

Figure 15. Step 5. Download

Figure 16. Rover service tool menu

Figure 17. Verifying the Program ID

This completes the software installation.

Ready for Network Installation

Table 1. Network variables for CVH/CVG/CDH/CVR

Table 1. Network variables for CVH/CVG/CDH/CVR

Table 3. Network variables for RTH (program ID 80002A-5028-0304-04)

Table 3. Network variables for RTH (program ID 80002A-5028-0304-04) (continued)

Table 4. Network variables for RTX

Table 4. Network variables for RTX

Table 5. Network variables for RTA

Table 5. Network variables for RTA

Table 6. Network variables for RTWD/RTUD

NV Index Network variable SNVT type

Table 6. Network variables for RTWD/RTUD

NV Index Network variable SNVT type

Table 7. Network variables for LCI-C Profile Only

Table 1. Network variables for the LCI-C Extension, listed alphabetically

User-defined Network Variable Types (UNVTs)

Table 2. Structure definition

Table 3. Structure definition