The VT7300 PI thermostat family is specifically designed for fan coil control. The
product features a backlit LCD display with dedicated function menu buttons for simple
operation. Accurate temperature control is achieved due to the product’s PI
proportional control algorithm, which virtually eliminates temperature offset associated
with traditional, differential-based thermostats.
Models are available for On/Off, 3 point floating and analog 0 to 10 Vdc control.
All models contain can control three, two or single fan speed. 3 additional inputs are
also provided for monitoring and / or various advanced functions.
All models feature configurable System and Fan button functions to meet all possible
applications. They all contain an SPST auxiliary switch that can be used to control
lighting or auxiliary reheat.
The thermostats are also compatible with the new TACO PIR cover accessories. Thermostats equipped with a PIR cover
provide advanced active occupancy logic, which will automatically switch occupancy levels from Occupied to Stand-By
and Unoccupied as required by local activity being present or not. This advanced occupancy functionality provides
advantageous energy savings during occupied hours without sacrificing occupant comfort. All thermostats can be ordered
with or without a factory installed PIR cover (see notes below ).
The additional following documents are available at: www.taco-hvac.com
• PIR application information and examples, are available on document: PIR Application Guide 102-354
• PIR cover installation information is available on document: PIR Cover Install Guide 102-355
• Detailed information on the thermostat (VT73xxX5x21x), is available on document:102-220
Contents
• Thermostat Objects
• SNVTs and SCPTs Table Per Model
• Input Network Variables (nvi’s) Description
• Output Network Variables (nvo’s) Description
• Configuration Properties (nci’s) Description
• Integration - Global Commands
• Integration - Graphic User Interface (GUI) Objects
• Integration - Configuration Objects
• Wiring Guide
Overview
Network Configuration
Maximum Number Of Devices
Maximum Cable Length
EI-485 Repeaters
Terminators
• Network Adapter
• Software Files
• RoHS and Non-RoSH APB and NXE Files
• Device Identification
• Tips And Things You Need To Know
• Troubleshooting Section
• Document Control
2
Page 3
Thermostat Objects
VT7300 Space Comfort Controller
Object Type #8500
nviSpaceTemp
SNVT_temp_p
nviOutdoorTemp
SNVT_temp_p
nviSetpoint
SNVT_temp_p
nviSpaceRH
SNVT_lev_percent
nviFanSpeedCmd
SNVT_switch
nviAuxHeatEnable
SNVT_switch
nviOccManCmd
SNVT_occupancy
nviApplicMode
SNVT_hvac_mode
nviHeatCool
SNVT_hvac_mode
Mandatory
Network
Variables
Optional
Network
Variables
nvoSpaceTemp
SNVT_temp_p
nvoUnitStatus
SNVT_hvac_status
nvoDischAirTemp
SNVT_temp_p
nvoSpaceRH
SNVT_lev_percent
nvoEffectOccup
SNVT_occupancy
nvoTerminalLoad
SNVT_lev_percent
nviRemLockout
SNVT_count
nviDhumidLCK
SNVT_switch
nviAuxOut
SNVT_switch
Configuration Properties
Send Heartbeat (mandatory)
Temperature Setpoints (mandatory)
Minimum Send Time (optional)
Receive Heartbeat (optional)
Manufacturer
Network
Variables
Manufacturer Configuration Properties
Please see the manual for details.
Plug-In for configuration provided.
nvoSCCstatus
SNVT_state_64
3
Page 4
SNVTs
1
and SCPTs2 Table Per Model
Model Number
VT7300F5x21E
VT7300A5x21E
VT7300C5x21E
VT7350C5x21E
VT7305A5x21E
VT7305C5x21E
VT7355C5x21E
Point Name
No
Sub
N/A: Not applicable on this model
0nviSpaceTempXXXXXXXXXXX
1nviOutdoorTempXXXXXXXXXXX
2nviSetpointXXXXXXXXXXX
3nviSpaceRHN/A N/A XN/A N/A X N/A XN/A X N/A
4nviFanSpeedCmdXXXXXXXXXXX
5nviAuxHeatEnableXXXXXXXXXXX
6nviOccManCmdXXXXXXXXXXX
7nviApplicModeXXXXXXXXXXX
8nviHeatCoolXXXXXXXXXXX
9nviRemLockoutXXXXXXXXXXX
This input network variable provides a network remote temperature
value to the thermostat. When linked of written to, the internal
temperature reading (internal sensor) is no longer used.
Valid Range: 40 to 122°F (-40 to 50°C)
Default Null (release) Value: 621.81°F (327.67°C or 0x7FFF)
This network variable is subject to the Receive HeartBeat Time,
nviRcvHrtBt.
Outdoor Air
Temperature
network input
SNVT_temp_p
nviOutdoorTemp
This input network variable provides outdoor air temperature
information to the thermostat from a network value temperature
value. The device will automatically display the value on its display
when linked.
Valid Range: 40 to 122°F (-40 to 50°C)
Default Null (release) Value: 621.81°F (327.67°C or 0x7FFF)
Occupied
Cool & Heat
Setpoints
network Input
SNVT_temp_p
nviSetpoint
This input network variable is used to allow the occupied
temperature setpoints only to be changed via the network from a
single analog value. (Note: the Stand-By and Unoccupied setpoints
are not changed). The corresponding heating and cooling values
are derived from the minimum deadband configuration value
Default Null Value: 621.81°F (327.67°C or 0x7FFF)
Ex. If the minimum deadband configuration value = 2 °F and
nviSetpoint = 70°F.
• The resulting Occupied heating setpoint will equal 69 °F which is
derived from 70 °F minus _ the minimum deadband configuration
value of 2 °F
• The resulting Occupied cooling setpoint will equal 71 °F which is
derived from 70 °F plus _ the minimum deadband configuration
value of 2 °F
Room
Humidity
network input
SNVT_lev_percent
nviSpaceRH
This input network variable is the measured room humidity in
percent monitored by the thermostat.
Valid Range: 5 to 90%
Default Null Value: +163.835 (0x7FFF)
This network variable is subject to the Receive HeartBeat Time,
nviRcvHrtBt
6
Page 7
ParameterVariable NameFunction
Fan Modenetwork input
SNVT_switch
nviFanSpeedCmd
This input network variable is used to connect an external fan
speed switch to the node or to allow any supervisory device to
override the fan speed controlled by the node’s control algorithm.
This input is used in conjunction with FanMenu bit in nciGenOpts.
Default Null Value: AUTO (state = 0xFF)
Valid Range:
Fan
Menu
Value
StateValueEquivalent
Percent
Requested Speed
Sequence of
Operation
network input
SNVT_switch
nviAuxHeatEnable
0
0
1
1
1
1
1
N/AN/AOff - Not Used
00%Off - Not Used
1 to 660.5 to 33%Low
67 to 13333.5 to 66.5%Medium
134 to 20067 to 100%High
201 to 255100%3 – Not Used
0xFFN/AN/AAuto – Not Used
1
0n/N/AOff – Not Used
100%Off – Not Used
10 to 1000.5 to 50%Low
1101 to 20050.5 to 100%High
1201 to 255100%2 – Not Used
0xFFN/AN/AAuto – Not Used
2
0N/AN/AOff - Not Used
100%Off - Not Used
11 to 660.5 to 33%Low
167 to 13333.5 to 66.5%Medium
1134 to 20067 to 100%High
1201 to 255100%3 – Not Used
0xFFN/AN/AAuto
3
0n/N/AOff – Not Used
100%Off – Not Used
10 to 1000.5 to 50%Low
1101 to 20050.5 to 100%High
1201 to 255100%2 – Not Used
0xFFN/AN/AAuto
4
0n/N/AOff – Not Used
100%Off – Not Used
11 to 2000.5 to 100%On (High)
1201 to 255100%On – Not Used
0xFFN/AN/AAuto
This input network variable is used to enable or disable the
1
auxiliary heat stage.
This input is used in conjunction with nviHeatCool and SeqOper.
Default Null Value: AUTO (state = 0xFF)
Set value to 100% for both On & Off state
Valid Range:
See note 1 below
StateValueAuxiliary Heat Operation
0N/ADisabled – Not Used
10 %Disabled
11 to 99%Partially Enabled – Not Used
1100%Enabled
0xFFN/AEnabled (invalid)
7
Page 8
ParameterVariable NameFunction
Occupancynetwork input
SNVT_occupancy
nviOccManCmd
This input network variable is used to command the Space
Comfort Controller into different occupancy modes. It is typically
set by a supervisory node to remotely control the occupancy
modes to override the local occupancy routines of the thermostat.
This network variable input is used to coordinate the Space
Comfort Controller with any node that may need to control the
heat/cool changeover of the unit.
This input is used in conjunction with nviHeatCool and SeqOper.
Default Null Value: HVAC_AUTO.
This network variable is subject to the receive heartbeat time,
nciRcvHrtBt
Valid Range:
0 = OC_OCCUPIED *
1 = OC_UNOCCUPIED )
2 = OC_BYPASS – Not Used
3 = OC_STANDY – Not Used
0xFF = OC_NUL (Release to internal occupancy)**
* OC_OCCUPIED and OC_UNOCCUPIED commands will
always have full authority over the local occupancy routines
of the thermostat may they be a local input or a PIR cover.
** OC_NUL command will release the thermostat to use its
own internal occupancy routine driven from one of the digital
input or a PIR cover installed on board.
0 = HVAC_AUTO
1 = HVAC_HEAT
2 = HVAC_MRNG_WRMUP – Not Used
3 = HVAC_COOL
4 = HVAC_NIGHT_PURGE – Not Used
5 = HVAC_PRE_COOL – Not Used
6 = HVAC_OFF
7 = HVAC_TEST – Not Used
8 = HVAC_EMERG_HEAT – Not Used
9 = HVAC_FAN_ONLY – Not Used
12 = HVAC_MAX_HEAT – Not Used
13 = HVAC_ECONOMY – Not Used
14 = HVAC_DEHUMID – Not Used)
15 = HVAC_CALIBRATE – Not Used)
0xFF = HVAC_NUL – Not Used
8
Page 9
ParameterVariable NameFunction
Sequence of
operation
network input
SNVT_hvac_mode
nviHeatCool
1
This network variable input is used to coordinate the Space
Comfort Controller with any node that may need to control the
heat/cool changeover of the unit. This input is overridden by
nviApplicMode, unless nviApplicMode is HVAC_AUTO. If
nviApplicMode is HVAC_AUTO, then nviHeatCool determines the
effective mode of the unit.
Default Null Value: HVAC_AUTO.
This network variable is subject to the receive heartbeat time,
nciRcvHrtBt
Valid Range:
See note 1 below
Lockoutnetwork input
UNVT_nvi/nvo
nviRemLockout
This network variable input is used to enable or disable user
This network variable input is used to enable or disable
dehumidification
Default Null Value: Dehumidification not allowed
Set value to 100% for both On & Off state
Valid Range:
Aux contactnetwork input
UNVT_nvi/nvo
nviAuxOut
This network variable input is used remotely command the
Auxiliary Output (BO5).
NOTE Auxiliary Contact configuration NEEDS to be set to 5 for this
function to operate ( 5 = Output to follow secondary network
occupancy command )
Set value to 100% for both On & Off state
Default Null Value: Auxiliary contact Off
Valid Range:
0 = HVAC_AUTO
1 = HVAC_HEAT
2 = HVAC_MRNG_WRMUP – Not Used
3 = HVAC_COOL
4 = HVAC_NIGHT_PURGE – Not Used
5 = HVAC_PRE_COOL – Not Used
6 = HVAC_OFF
7 = HVAC_TEST – Not Used
8 = HVAC_EMERG_HEAT – Not Used
9 = HVAC_FAN_ONLY – Not Used
12 = HVAC_MAX_HEAT – Not Used
0xFF = HVAC_NUL – Not Used
Temperature
Setpoints
System
Mode
Settings
Fan Mode
Settings
Unoccupied
Override
State =0 = Dehumidification not allowed (Thermostat’s default
value)
State = 1 = Dehumidification allowed
State = 0 = Auxiliary contact Off (Thermostat’s default value)
State = 1 = Auxiliary contact On
9
Page 10
Output Network Variables (nvo’s) Description
All output network variables will be updated no faster than the Minimum Send Time (nciMinOutTm) configuration value.
An output network variable will be transmitted immediately when its value has changed significantly (manufacturer’s
defined). Additionally, this variable will also be transmitted as a heartbeat output on a regular basis as dictated by the
Maximum Send Time (nciSndHrtBt) configuration value.
ParameterVariable NameFunction
Room
Temperature
network output
SNVT_temp_p
nvoSpaceTemp
This output network variable is used to monitor the effective space
temperature sensor that the Space Comfort Controller is using for
control. This output echoes the value of the input.
Valid Range: 14 to 122°F (-10 to 50°C)
The value 621.07°F (327.67°C or 0x7FFF) will be sent as an
invalid value in case of a sensor failure.
Supply
Temperature
network output
SNVT_temp_p
nvoDischAirTemp
This output network variable is used to monitor the temperature of
the air that leaves the Space Comfort Controller
NOTE: UI3 needs to be configured to (SS) Supply air sensor
monitoring
Valid Range: -40 to 122°F (-40 to 50°C)
The value 621.81°F (327.67°C or 0x7FFF)will be sent as an invalid
value in case of a sensor failure.
Room
Humidity
network output
SNVT_lev_percent
nvoSpaceRH
This output network variable indicates the space humidity in
percent.
Valid Range: 0 to 100%.
The value 0x7FFF = +163.835% will be set as an invalid value to
indicate a humidity sensor failure.
Occupancynetwork output
SNVT_occupancy
nvoEffectOccup
This output network variable is used to indicate the actual
occupancy mode of the unit. This information is typically reported
to a supervisory controller or provided to another Space Comfort
Controller to coordinate the operation of multiple units
Valid Range:
0 = OC_OCCUPIED
1 = OC_UNOCCUPIED
2 = OC_BYPASS
1
3 = OC_STANDBY
Unit Status
network
output
SNVT_hvac_status
nvoUnitStatus
Note 1: OC_BYPASS can be initiated by either nviOccManCmd or a
local input. NvoEffectOccup will only be in OC_BYPASS for the
duration of the ToccTime (nciGenOpts), until reinitiated by either a
transition of the local input or an update to nviOccManCmd.
This output network variable is available to report the Space
Comfort Controller status. It combines the operating mode, the
capacity of heating and cooling used and an indication if any
alarms are present in the object.
SubNameValid Value
01modeHVAC_AUTO
HVAC_HEAT
HVAC_MRNG_WRMUP – Not Used
HVAC_COOL
HVAC_NIGHT_PURGE – Not Used
HVAC_PRE_COOL – Not Used
HVAC_HVAC_OFF
HVAC_HVAC_TEST – Not Used
HVAC_HVAC_EMERG_HEAT – Not Used
10
Page 11
ParameterVariable NameFunction
Unit Status
network
SNVT_hvac_status
nvoUnitStatus
SubNameValid Value
output
02:heat_output
_primary
03heat_output
_secondary
04cool_output:0-100%, 0x7FFF (Invalid)
05econ_outputNot Used
06fan_output0-100%, 0x7FFF (Invalid)
07In_alarm0 (No alarms)
Thermostat’s
I/O status
network output
UNVT_fc_thermo_
state
nvoSccStatus
This network variable output is used to report the Space Comfort
Controller inputs’ and outputs’ status.
SubNameValid valueDefault Value
01StateTerminal BO20 = Off
02StateTerminal BO10 = Off
03StateTerminal BO40 = Off
04StateTerminal BO30 = Off
05StateTerminal BO50 = Off
06FanLow0 = Off
07FanMed0 = Off
08FanHigh0 = Off
09UI3 Status-40 to 122 °F
10BI2 Status0 = activated
11BI1 Status0 = activated
12Local PIR Motion0 = No motion
13Service Alarm0 = No alarm
14Filter Alarm0 = No alarm
15Window Opened0 = No alarm
16Dehumidification
Active
Heating/
Cooling
demand
network output
SNVT_lev_percent
nvoTerminalLoad
This output indicates the current heat/cool energy demand of the
unit. Positive values indicate that cooling energy is in use by the
space comfort controller, while negative values indicate that
heating energy is in use by the space comfort controller.
Valid Range: -100% to 100%
HVAC_FAN_ONLY – Not Used
HVAC_MAX_HEAT – Not Used
0-100%, 0x7FFF (Invalid)
Not Used
1 (Alarm On)
0x7FF (Alarming disabled) – Not Used
0 = Off
1 = On
0 = Off
1 = On
0 = Off
1 = On
0 = Off
1 = On
0 = Off
1 = On
0 = Off
1 = On
0 = Off
1 = On
0 = Off
1 = On
N/A
(-40 to 50°C)
40°F = Open
122°F = Close
1 = not activated
1 = not activated
1 = not activated
1 = not activated
0 = No motion
1 = Motion
0 = No alarm
1 = Alarm on
0 = No alarm
1 = Alarm on
0 = No alarm
1 = Alarm on
0 = Off
0 = Off
1 = On
11
Page 12
Configuration Properties (nci’s) Description
ParameterVariable NameFunction
Temperature
Setpoints
network input config
SNVT_temp_setpt
nciSetPts
This configuration property defines the space temperature
Valid Range and Default values:
SubNameValid RangeDefault value
01occupied_cool54 to 100°F
02standby_cool54 to 100°F
03unoccupied_cool54 to 100°F
04occupied_heat40 to 90°F
05standby_heat40 to 90°F
06unoccupied_heat40 to 90°F
RH optionsnetwork input config
This configuration property defines the space humidity parameters
UNVT_gen_opts
nciRHmodel
Valid Range and Default values:
SubNameValid RangeDefault value
01RHdisplay0 = Not active
02RHsetpoint30 to 100% RH50% RH
03DehumHyst2 to 20% RH5% RH
04DehumCool20 to 100% RH100% RH
05RHcalib-15 to +15% RH0% RH
Thermostat’s
common
configuration
parameters
network input
UNVT_fc_gen_opts
nciGenOpts
This configuration property defines the thermostat’s common
Valid Range and Default values:
SubNameValid RangeDefault value
01Control Type0 = On/Off Control
config
02Drive Time0.5 to 9 minutes (0.5
03Cycles Per Hour 3, 4, 5, 6, 7 and 8 CPH4 CPH
04ReverseActing
05BI10 = None
06BI20 = None
07UI30 = None
08Menu Scroll0 = No Scroll
setpoints for various heat, cool and occupancy modes.
75°F (24.0°C)
(12 to 37.5°C)
78°F (25.5°C)
(12 to 37.5°C)
80°F (26.5°C)
(12 to 37.5°C)
72°F (22.0°C)
(4.5 to 32°C)
69°F (20.5°C)
(4.5 to 32°C)
62°F (16.5°C)
(4.5 to 32°C)
and their settings.
0
1 = Active
configuration parameters and their settings.
0
1 = Floating Control
3 minutes
increments)
Output
0 = Direct Acting (DA)
1 = Reverse Acting (RA)
0
0
1 = Rem NSB
2 = Motion NO
3 = Motion NC
4 = Window
0
1 = Door Dry
2 = Override
3 = Filter
4 = Service
0
1 = COC/NH
2 = COC/NC
3 = COS
4 = SS
1
1 = Scroll Active
12
Page 13
ParameterVariable NameFunction
Thermostat’s
common
UNVT_fc_gen_opts
nciGenOpts
SubNameValid RangeDefault value
09Auto Mode0 = Not Active
configuration
parameters
network input
config
10Temperature
Scale
11Pipes # Main
out config
12Sequence of
Operation
13Fan Menu0 = Low-Med-High
14Heat
Maximum
Setpoint
15Cool Minimum
Setpoint
16Setpoint Type0 = Permanent
17Temporary
Occ Time
18Deadband2, 3, 4 or 5 °F
19Calibration
Room Sensor
20Auxiliary
Contact Config
21Reheat Time
Base
22Fan Mode0 = Low
23PIR Stand-By
Timer
24PIR
Unoccupied
Timer
0
1 = Active
0 = °C
°F
1 = °F
2 = 2 pipe
4 pipe
4 = 4 pipe
0 = Cooling Only
1 = Heating Only
Figure 2: Graphical User Interface (GUI) example of a Fan-Coil system
17
Page 18
Configuration Objects
The following SNVT and UNVT should be typically used for configuration purposes:
nciGenOpts;
nciRHmodel;
nciSetpoints;
Wiring Guide
Overview
For clarity we will use the term “Device” to represent any product with an active Echelon network connection, including
TACO and non-TACO controllers.
Summary Specifications:
ParameterDetails
Network Wiring24 to 16AWG, twisted pair
Maximum total wire length
1
1600 feet (500 meters) in free topology
Maximum device-to-device distance1600 feet (500 meters) in free topology
PolarityPolarity insensitive
Multi-dropFree Topology
Termination for Free Topology Network Segment
Termination for Doubly Terminated Bus Network
One RC network with Ra = 52.3Ω±1%, 1/8W
Two RC network with Ra = 105Ω±1%, 1/8W
Segment
Number of transceivers per segmentUp to 64
Baud rate78000 bits per second
1
Network segment length varies depending on wire type.
Table 1: Summary of Specifications for a TACO ’ LON Network
Network Configuration
The Echelon network is designed to support free topology wiring and will accommodate bus, star, loop or any of these
topologies. Echelon devices can be located at any point along the network wiring.
Figures 3.1 to 3.5 present five different network topologies. The actual termination circuit will vary by application.
18
Page 19
Maximum Number Of Devices
Up to 64 transceivers are allowed per network segment. If your network requires more than 64 transceivers a repeater is
then required to extend your network
19
Page 20
Maximum Cable Length
The maximum length of a chain is related to its transmission speed. The longer the chain, the slower the speed.
Using proper cable, Echelon supports a baud rate of 78 kilobits per second for distances up to 1600-ft (500 m) in free
topology and 8800 ft (2700 m) in bus topology with double terminations.
If you require a maximum network length of more than 1600-ft (500 m) or 8800 ft (2700 m), then a repeater is
required to extend the network.
Repeater
In the event that the limits on the number of transceivers or total wire distance are exceeded, a physical layer
repeater can be added to interconnect two or more network segments. A repeater will double the overall channel
capability, including node count and network extent, but not bandwidth. Note that only one physical layer repeater
should be placed in series between any two nodes on a channel. If additional cabling or network bandwidth is
required, then a LonWorks Router should be used in place of a repeater.
Terminators
Echelon network segments requires termination for proper data transmission performance. The type of terminator varies
depending on whether shielded or unshielded cable is used. Free topology and Bus networks also differ in their
termination requirements. The following sections describe the various terminators and terminations procedure.
Free Topology Network Segment
In a free topology segment, only one termination is required and may be placed anywhere on the free topology
segment. There are two choices for the termination:
1. RC network with Ra = 52Ω±1%, 1/8W
2. LPI-10 Link Power Interface, with jumper at “1 CPLR” setting.
Doubly Terminated Network Segment
In a doubly terminated bus topology, two terminations are required, one at each end of the bus. There are two
choices for each termination:
1. RC network with Ra = 105Ω±1%, 1/8W
2. LPI-10 Link Power Interface, with jumper at “2 CPLR” setting.
Only one LPI-10 interface is supported per segment. The other terminator must be an RC-type.
Grounding Shielded Twisted Pair Cable
When using Shielded Twisted Pair, terminate the twisted pair as listed in the previous section and ground the
cable shield by using a capacitor, to tie the shield to earth ground, and a large-value resistor to bleed off any
static charge on the shield. Tying the shield to earth ground through a capacitor will avoid DC and 50/60Hz
ground paths from being formed through the shield. Typical values for resistor and capacitor are as follows:
The cable shield should be grounded at least once per segment, and preferably at each node. Grounding the
shield at every node will assist in suppressing 50/60Hz standing waves.
20
Page 21
Network adapter
Although network connections are polarity insensitive, it is good practice to keep polarity consistent throughout the entire
site. Figure 4 shows a network connection example and the location of the Status LED. This Status LED may help to
troubleshoot network problems.
Figure 4: Network connections and location of the Status LED on a LON module
Table 2 shows the different possibilities with the Status LED behaviour of the LON module.
Condition of the Status LEDExplanation
Continuously ONThe device has no application loaded in its memory and is
Un-configured
Flashing at a rate of 1/2HzThe device has an application loaded in its memory but is
Un-configured. When a device is in the un-configured state, it
does not know which devices to communicate with. A
network management tool is used to logically bind the node
to another in a LonWorks network.
Continuously OFFThe device has an application loaded into its memory and is
bound onto a LonWorks network.
Table 2: Status LED condition
Software Files
XIF: When binding a node onto the network, an XIF file is needed. The XIF file has information that is used by the network
management tool to help ease the installation and maintenance process of a node. It is also used for offline configuration
of the node.
APB and NXE: When running an application program associated with a XIF file, an APB or NXE file is needed. Please
note that the thermostats have the APB file already flashed from the factory.
Device Resource File (DRF): When a LON network management tool is used; a DRF file must be installed. DRF files are
needed to display special manufacturer defined variables or configurations correctly.
•Please note that all release notes for the XIF, APB & NXE software files will be included under the
following folder name on your hard drive: C:\LonWorks\Import\Viconics. The name of the file is:
VT7xxxReadme.txt
Plug-Ins File: Plug-Ins simplify start-up, maintenance, configuration and reduce the installation effort.
•Please note that all release notes for Plug-Ins files will be included under the following folder name on
your hard drive: C:\LonWorks\Plug-Ins\Viconics\VT7xxx. The name of the file is: Readme.txt.
•All the latest software files can be downloaded from VICONICS’ web site at
www.viconics.com.com
21
Page 22
RoHS & Non-RoHS APB and NXE Files
In July of 2006, new APB and NXE files where introduced to support new RoHS compliant components from Echelon
Corporation. Those APB and NXE software revisions are not backward compatible and some care and attention
must be taken to assure you are utilizing the correct revision during the commissioning procedure. Please note that the
thermostats already have the proper file flashed from the factory.
In order to differentiate non-RoHS and RoHS software, a new PID has been issued for each new RoHS software as
shown in Figure 5.
Your LNS systems already have a built in protection against firmware mismatch and will refuse any upload from nonRoHS software to a RoHS device or vice-versa. The PID change has been instituted in order to prompt an
“incompatibility” message from your Niagara based system.
Figure 5: RoHS and Non-RoHS Marking and Program IDs
XIF, APB and NXE File Names and Corresponding PIDs
Used on thermostatXIF file namesAPB / NXE file
names
Non-RoHS VT7200 / VT7300 SeriesT7X-FC.XIFT7X-FC.APB80:00:C5:55:00:04:04:0B
RoHS VT7200 / VT7300 SeriesT7X-FCr.XIFT7X-FCr.APB80:00:C5:55:00:04:04:1B
RoHS PIR VT7200 / VT7300 Series **T7X-FC-PIR.XIFT7X-FC-PIR.APB80:00:C5:55:00:04:04:1D
** Please note that all new PIR ready thermostat series of the VT7200 / VT7300 thermostat family will use the latest
released files to properly use all the new advanced occupancy functions associated with a local PIR accessory cover
installed on the thermostat.
Associated PID
22
Page 23
Device Identification
An Echelon device has a unique mechanism to identify itself, the Neuron ID, which is obtained during commissioning.
There are two ways of getting the Neuron ID: with a Service Pin or manually.
Service PIN
The service pin is used to identify the device at commissioning. By pressing simultaneously the “Up” button and the
“Down” button located on the keypad interface of a VT7300 device, the program ID and the Neuron ID (LonWorks Unique
ID) contained in the device are transmitted to the commissioning or service tool. The Status LED will blink when the
device accepts the Service Pin command.
Figures 6 and 7 show an example of a Service PIN request made through a commissioning tool
Figure 6: Service Pin request through a commissioning tool
Figure 7: Service Pin request through a commissioning tool
23
Page 24
Manual Identification
Neuron ID of a device can also be entered manually through a commissioning or service tool. Neuron ID should be
located on the Echelon chip of the device being commissioned.
Figure 8 shows an example of a Manual Neuron ID request made through a commissioning tool.
Figure 8: Manual Neuron ID request
Tips And Things You Need To Know
In order to operate nviAuxOut (auxiliary output) from the network, Aux contact configuration (Auxcont nciGenOpt)
needs to be set as “Network Controlled”;
If the heartbeat is lost, the module will release the network sensor value for the Room Temperature (nviSpaceTemp)
and the Outdoor Temperature (nviOutdoorTemp);
The SeqOpera value (Sequence of Operation) depends on the nviHeatCool value and nviAuxHeatEnable value. See
note 1 on page 15 for all the details;
Troubleshooting Section
Error / Trouble
Possible CauseSolution
Condition
Thermostat does not
come online
The LON network has too many
devices.
Do not exceed the maximum number of
devices and maximum length allowed
by the EIA-485 specifications.
Too many devices were installed
without any repeaters.
Repeaters need to be installed as
specified in this document.
The LON cable runs are brokenLocate the break and correct wiring
The thermostat does not have powerApply power to the thermostat
RevisionDateChanges
01January 4, 2006Created to coincide with release of the VT7300 as a LonMark certified product.
02April 5, 2006Updated the DRF files section and removed any application guide reference
03July 11, 2006Modified the Software Files section and added the RoHS / Non-RoHS section
04Aug 15, 2006Modified Note 1 on page 15
05Nov 21, 2007Added modifications required for PIR support to the new VT73xxX5xxxE release
06Jan 21, 2008Added additional modifications required for PIR support
24
Page 25
Do it Once. Do it Right.
®
LIMITED WARRANTY STATEMENT
A
y
Taco, Inc. will repair or replace without charge (at the company’s option) any product or part which is proven defective under normal use within three
(3) years from the date of start-up or three (3) years and six (6) months from date of shipment (whichever occurs first).
In order to obtain service under this warranty, it is the responsibility of the purchaser to promptly notify the local Taco stocking distributor or Taco in
writing and promptly deliver the subject product or part, delivery prepaid, to the stocking distributor. For assistance on warranty returns, the
purchaser may either contact the local Taco stocking distributor or Taco. If the subject product or part contains no defect as covered in this warranty,
the purchaser will be billed for parts and labor charges in effect at time of factory examination and repair.
ny Taco product or part not installed or operated in conformity with Taco instructions or which has been subject to misuse, misapplication, the
addition of petroleum-based fluids or certain chemical additives to the systems, or other abuse, will not be covered by this warranty.
If in doubt as to whether a particular substance is suitable for use with a Taco product or part, or for any application restrictions, consult the
applicable Taco instruction sheets or contact Taco at [401-942-8000].
Taco reserves the right to provide replacement products and parts which are substantially similar in design and functionally equivalent to the
defective product or part. Taco reserves the right to make changes in details of design, construction, or arrangement of materials of its products
without notification.
TACO OFFERS THIS WARRANTY IN LIEU OF ALL OTHER EXPRESS WARRANTIES. ANY WARRANTY IMPLIED BY LAW INCLUDING
WARRANTIES OF MERCHANTABILITY OR FITNESS IS IN EFFECT ONLY FOR THE DURATION OF THE EXPRESS WARRANTY SET FORTH
IN THE FIRST PARAGRAPH ABOVE.
THE ABOVE WARRANTIES ARE IN LIEU OF ALL OTHER WARRANTIES, EXPRESS OR STATUTORY, OR ANY OTHER WARRANTY
OBLIGATION ON THE PART OF TACO.
TACO WILL NOT BE LIABLE FOR ANY SPECIAL, INCIDENTAL, INDIRECT OR CONSEQUENTIAL DAMAGES RESULTING FROM THE USE OF
ITS PRODUCTS OR ANY INCIDENTAL COSTS OF REMOVING OR REPLACING DEFECTIVE PRODUCTS.
This warranty gives the purchaser specific rights, and the purchaser may have other rights which vary from state to state. Some states do not allow
limitations on how long an implied warranty lasts or on the exclusion of incidental or consequential damages, so these limitations or exclusions ma
not apply to you.