Replacing an LCI-R with an LCI-RX
Summary:
The LCI-RX is a replacement for the LCI-R Lontalk communications interface for Voyager / Precedent units with Reliatel controls. The old version of the LCI-R is no longer available. Any new purchase will be the new version, LCI-RX. The LCI-RX does not replace the Lontalk communications interface for Voyager units with UCP (Micro) controls. Units with UCP controls still require the LCI-V, which is a separate part.
The new version LCI-R(X) firmware implements both the SCC and DAC Lon profiles, so the same card with the same firmware is used for both SCC and DAC units. This is different than for the old version LCI-R. The old version used different firmware for SCC and DAV units. As a result the program ID is different in the new version. The program ID is used by system controllers during installation so this may cause a problem when the old version LCI-R is replaced with the new LCI-R(X).
NOTE: If upgrading to the new LCI-RX communication interface, it is recommended the RTRM v19.1 or greater be used, to reduce a software mismatch or nuisance diagnostics being generated and possibly filling up the BAS alarm log. Older RTRM version will require a newer RTRM be installed
There are four possibilities:
1) Summit system: The LCI-RX is supported with BCU image 17.081 and Summit version 17 SP13. If the BCU image and Summit are up to date a normal replacement should work. Unassign the old NID from the object in summit. Install the new LCI-RX in the unit. Connect the communications link. At the Summit workstation select Site Configuration / Assign NID. Discover NID. Select the correct object and assign. If the BCU image and Summit version are not up to date there will be problems.
2) Tracer SC: Currently a direct replacement will not work with SC. It will be necessary to delete the old unit and then install the new unit with the LCI-RX as if it were a completely new unit. With SC version 3.7 or higher the new LCI-RX can auto-install. With .SC versions prior to 3.7 it will be necessary to create a template. Be sure that the DSN for the new unit is not a duplicate. (It can be the same as the old unit because that unit was deleted). The real problem will be to incorporate the new unit in to applications (Area, VAS, Schedule etc).
3) Integration to a non-Trane BAS: We cant determine how a replacement will affect a non-Trane BAS, but there may be things they will need to do in order to accommodate the new interface. The BAS contractor should be notified that the program ID (and address) has changed for this unit.
4) To install on a Tracker, the Tracker must be a version 12.27 or higher for green board or 12.54 or higher for blue board Tracker. All CCP's should be updated to the latest version before updating the Tracker. If the Tracker is already at 12.27 or 12.54, backup the Tracker then select return to factory defaults. Restore the backup when complete.
There is a plug-in for the LCI-R(X) in Rover v7.1 SP 10.
Note: The LCI-RX is not a plug-and-play replacement for the LCI-R. The program ID has changed. Since the program ID has changed the LCI-R will need to be uninstalled or removed from the BAS and then install or add the LCI-RX to the BAS. A new Rover plug-in has been created in SP10. The BCU image 17.081 supports the new variables in the LCI-RX. SC version 3.7 or newer supports auto-installation.
See the below link for LCI-RX xif files
https://tranesupport.zendesk.com/hc/en-us/articles/4636519272973-LCU-LCI-R-and-LCI-RX-xif-files
See below link for the installation guide
E-Library: ACC-SVN175* - Trane Commercial (tranetechnologies.com)
WARNING:
Information in this article is intended for use by individuals possessing adequate backgrounds of electrical and mechanical experience and who comply with all federal, state, and local laws, rules, orders, or regulations related to the installation, service, or repair of a heating or central air conditioning product. Any attempt to install, service, or repair a heating or central air conditioning product may result in personal injury and/or property damage. The manufacturer or seller cannot be responsible for the interpretation of the information contained herein, nor can it assume any liability in connection with its use.