Integrating Trane Air-Fi VAV Controllers into Non-Trane BAS

Integrating Trane Air-Fi VAV Controllers into Non-Trane BAS

This guide covers options for integrating Trane Air-Fi wireless VAV controllers into third-party building automation systems.

Understanding Air-Fi Architecture

Trane Air-Fi is a proprietary wireless mesh network for VAV controllers:

Component	Function
Air-Fi VAV Controller	Zone-level controller with wireless communication
Air-Fi Gateway	Bridges wireless mesh to wired network
Tracer SC/Summit	Trane supervisory controller (required by design)

Critical limitation: Air-Fi VAVs communicate via proprietary wireless protocol to Air-Fi Gateways, which then communicate via proprietary protocol to Trane Tracer controllers. There is no direct BACnet exposure from the Air-Fi network.

Integration Options

Option 1: Keep Trane Infrastructure, Integrate at Supervisory Level

Architecture:

Non-Trane BAS <--BACnet/IP--> Tracer SC <--Proprietary--> Air-Fi Gateway <--Wireless--> VAVs

Requirements:

• Keep existing Tracer SC or Summit controller
• Enable BACnet server on Tracer
• Map Air-Fi points to BACnet objects

Pros:

• Minimal disruption to existing system
• VAVs continue operating normally
• No rewiring required

Cons:

• Requires maintaining Trane Tracer controller
• BACnet license/subscription may be required from Trane
• Depends on Tracer for all VAV communication

Implementation:

1. Enable BACnet/IP server on Tracer SC (requires Trane configuration tool)
2. Configure BACnet device instance and IP settings
3. Create BACnet objects for required points (temperature, setpoint, airflow, damper, etc.)
4. Discover Tracer from your BAS as BACnet device
5. Map points into your supervisory system

Option 2: Gateway Devices (Limited Options)

Some third-party integration gateways claim Air-Fi support, but verify carefully:

What to ask vendors:

• Does it communicate directly with Air-Fi VAVs or require Tracer?
• Is it officially licensed/certified by Trane?
• What Air-Fi firmware versions are supported?

Reality check: Most "Air-Fi integration" products actually just talk BACnet to the Tracer, not directly to the wireless mesh.

Option 3: Replace VAV Controllers

If eliminating Trane dependency is critical:

Considerations:

• 60+ controllers = significant cost
• Existing wiring to damper actuators can usually be reused
• Zone sensors may need replacement depending on compatibility
• Actuators themselves rarely need replacement

Phased approach:

1. Integrate existing Air-Fi at Tracer level (short term)
2. Replace VAV controllers zone-by-zone as they fail (long term)
3. Budget 3-5 per controller installed for basic BACnet VAV

Option 4: Hybrid Approach

Some facilities use mixed strategy:

• Critical zones: Replace with BACnet VAV controllers
• Non-critical zones: Leave on Air-Fi with Tracer integration
• New construction/renovations: Use BACnet from start

BACnet Points from Tracer

When integrating via Tracer BACnet server, these points are typically available:

Point Type	BACnet Object	Notes
Zone Temperature	AI	Primary feedback
Zone Setpoint	AV	May be read-only depending on config
Discharge Air Temp	AI	If DAT sensor installed
Airflow	AI	CFM reading
Damper Position	AO/AV	Commanded position
Occupancy	BI	From sensor or schedule
Heating Command	AO	If reheat present
Mode	Multi-state	Heating/cooling/deadband

Limitations to Expect

1. Communication latency - Multiple protocol translations add delay
2. Point availability - Not all Air-Fi points may be exposed via BACnet
3. Alarm handling - Alarms may need to be translated
4. Schedule coordination - Tracer schedules vs BAS schedules
5. Graphics - Need to recreate zone graphics in new BAS

Cost-Benefit Analysis

Approach	Upfront Cost	Ongoing Cost	Independence from Trane
Tracer BACnet integration	Low	Medium (licensing)	No
Replace all VAVs	High	Low	Yes
Hybrid (integrate + gradual replace)	Medium	Medium	Eventually

Recommendation

For most facilities with 60+ Air-Fi VAVs:

1. Short term: Integrate via Tracer BACnet to get visibility immediately
2. Medium term: Budget for gradual VAV replacement
3. Long term: As Air-Fi controllers fail (typical life 10-15 years), replace with BACnet

This approach avoids large capital expenditure while creating a path to vendor independence.

Technical Support

• Tracer BACnet configuration: Contact Trane local office or Trane Technologies support
• Air-Fi troubleshooting: Requires Trane service agreement or trained technician
• Third-party integration: Work with your BAS vendor on point mapping