Note: This feature is currently in Limited Release. While these features are planning to be released in the 2026-R2 release, we are open to considering unique projects that could provide valuable insights for further improving the feature, and Field Trials.
For inquiries, please contact Juan Manuel Torres (JuanManuel.Torres@tranetechnologies.com) , Somasundaram Subramaniam (Somasundaram.Subramaniam@tranetechnologies.com) or Cristiam Cano (CCano@trane.com).
Beginning with Synchrony v6.4.24xxx, the Tracer SC+ system supports the new Communication Module (CM2). when the controller is licensed with the CPC for Mission Critical feature. This capability is specifically designed for critical environments such as data centers where expanded and flexible BACnet/IP communication is required to meet stringent customer specifications.
The CM2 module connects directly to any USB port on the SC+ and provides an additional, fully functional Ethernet interface supporting both BACnet/IP and Modbus TCP.
Licensing Requirements
To enable CM2 support, the SC+ must have:
- CPC for Mission Critical Feature licensing
- Installer or programmer‑level user permissions for installation and configuration
- Synchrony firmware version 6.4.24xxx or later
Without the Mission Critical license, the SC+ will not recognize or activate the CM2 module.
Module Detection
When a CM2 module is plugged into any SC+ USB port:
- The SC+ automatically detects the hardware.
- Users with installer/programmer permissions must confirm and complete the setup.
The CM2 will be listed under the USB Ports section, and its power draw will be shown in the peripheral power draw area on the USB Ports and microSD page.
What the CM2 Module Adds to the SC+
Traditionally, the SC+ includes two onboard Ethernet ports, each capable of supporting BACnet/IP and Modbus TCP. With the addition of the CM2 module, the SC+ gains a third Ethernet interface.
The CM2 Ethernet interface supports both BACnet/IP and Modbus TCP, allowing it to function as an independent communication channel across either protocol. Each port onboard or CM2‑provided can be configured differently depending on the needs of the site.
For example, a technician may dedicate one port to BACnet/IP for building automation integration, while using another port exclusively for Modbus TCP data acquisition. The availability of an additional IP interface creates more room for meeting strict IT directives around VLAN use, redundancy pathways, and customer‑specified network segregation. This flexibility is particularly beneficial in mission‑critical sites such as data centers, laboratories, and healthcare facilities where networks must be isolated or duplicated for reliability and compliance.
CM2 Port & Link Setup Concepts
Once the CM2 is detected, additional settings appear within the same synchrony screens already used to manage the SC+ onboard network ports.
IP Configuration Tab
The IP Configuration tab is expanded to include all configuration fields necessary to manage the CM2 Ethernet interface. This includes settings for static IP addressing or DHCP assignment, Subnet configuration, and gateway behaviour.
Modbus Configuration Tab
- Allows enabling Modbus TCP on the CM2 port
Device Discovery
Based on how the CM2 link is configured (BACnet/IP or Modbus TCP), User will be able to discover devices through the CM2 interface.
Protocols and Features Not Supported on CM2
- The CM2 module focuses on expanding IP‑based communication and therefore does not add or support the following features:
- 802.1X network authentication
- IPv6 addressing
- BACnet Secure Connect (BSC)
- BACnet MSTP & Modbus RTU
- Direct‑connected Trane legacy communication devices