The Trane Tracer SC system controller (Tracer SC) is used when LON/Comm5 devices are connected to an SC.
The Trane Tracer SC gateway is not required to retrieve BACnet data from:
- BACnet MSTP devices connected under a Tracer SC.
- Trane Comm3 or Comm 4 devices connected under a Trane Comm3/Comm4 bridge. The Trane Comm3/Comm4 bridge parses Comm3/Comm4 objects within a Trane Tracer SC and creates BACnet virtual devices for all.
Consider the Trane Comm3/Comm4 bridge as if it is a Trane BCU. See the help section Scanning a Trane Tracer Summit Network. When a BACnet scan is performed on the SC network, the Trane Comm3/Comm4 Bridge will appear as a BACnet device typically in the device ID range of 100-200. Scan the Trane Comm 3-4 Bridge and mark the Sub-device checkbox.
To allow a Connect Mini Agent to retrieve LON/Comm5 data from the Tracer SC, the Tracer SC database will need to be created within the Connect Gateway Manager Tool. This Gateway parses LON/Comm5 objects within a Trane Tracer SC and creates BACnet virtual devices for all devices stored within the Tracer SC controller. This allows the Trane LON/Comm5 devices communicating to the Tracer SC to appear in Connect as multiple BACnet virtual devices.
To allow a Connect Mini Agent to retrieve data from the Tracer SC, the Tracer SC database will need to be created within the Connect Gateway Manager Tool. This Gateway parses the objects within a Trane Tracer SC and creates BACnet virtual devices for all devices stored within the Tracer SC controller. This allows the Trane Comm 4 and Comm 5 devices communicating to the Tracer SC to appear in Connect as multiple BACnet virtual devices.
...