24
CNT-SVX05A-EN
Communications
The Tracer™ AH.540 controller communicates via Trane's Comm5 protocol.
Typically, a communication link is applied between unit controllers and a
building automation system. Communication also is possible via Rover service
tool. Peer-to-peer communication across controllers is possible even when a
building automation system is not present.
You do not need to observe polarity for Comm5 communication links.
The controller provides six terminals for the Comm5 communication link
connections, as follows:
• Two terminals for communication to the board
• Two terminals for communication from the board to the next unit (daisy chain)
• Two terminals for a connection from the zone sensor back to the controller
Figure 2 — Communication wiring
The Comm5 communications protocol allows peer-to-peer communications
between controllers, which allows controllers to share information or data.
A communicated variable input such as setpoint, space temperature, or outdoor
air temperature has priority over a locally wired input to the controller.
For example: If the Tracer AH.540 controller has a wired outdoor air
temperature sensor and Tracer Summit or another Comm5 controller sends it a
communicated outdoor air temperature, the communicated value is used by
the Tracer AH.540 controller. If a communicated input value is lost, the Tracer
AH.540 controller reverts to using the locally wired sensor input.
Device addressing
Comm5 devices are given a unique address by the manufacturer. This address
is called a Neuron ID. Each Tracer AH.540 controller can be identified by its
unique Neuron ID, which is printed on a label on the controller’s logic board. The
Neuron ID is also displayed when communication is established using Tracer
Summit or Rover service tool. The Neuron ID format is 00-01-64-1C-2B-00.
