Appendix; Application Notes; Appendix Application Notes - Trane LonWorks



TR1 Series VFD Installation And Operation Manual

The factory mounted Trane TR1 VFD will most typically be utilizing discrete I/O for control, the LCP (Local Control
Panel) for set-up and troubleshooting, and will probably not be using a serial interface. In many cases, this will also be
the direction for field applied TR1s. There has been an increasing number of requests where customers would like to
acquire additional data from the VFD. For these cases, there are 4 different scenarios that will be discussed to aid in
describing possible architectures.
A. TR1 is factory mounted or field applied using discrete I/O. A customer may wish to monitor the VFD at the Trane
BAS by mapping its values using the Generic LonTalk Device (GLD) object.
B. TR1 is field applied and using "closed loop" control. The VFD is utilizing its internal PID loop for operation and the
customer may want to enable/disable, change settings, and monitor the drive from the Trane BAS.
C. TR1 is field applied and using "open loop" control. The VFD is receiving a frequency reference from an outside
source such as Trane's AH540s and MP580s. In this case the VFD is dependent upon another controller for input.
In addition to control over the LON network, a customer may want to change settings and monitor the drive from
the Trane BAS.
D. Hybrid – A customer may want "open loop" control and, under certain circumstances, may want the drive to
default to "closed loop" control. There may also be a need to override the VFD to a preset condition, either
through an I/O contact closure or through the LON interface based upon some event.
Interface Type:
Provides data to Tracer Summit (Server)
User of data from Tracer Summit (Client)
Provides and uses data from Tracer Summit (Client / Server)
Interface Protocol:
BACnet
Modbus
LonTalk
Other __________________________

APPENDIX

Application Notes

RTU ASCII TCP
33