Trane UC600 BACnet MS/TP to Modbus RTU Case Study

Chipkin QuickServer converted Trane UC600 BACnet MS/TP data into a documented Modbus RTU handoff for a BAS contractor and systems integrator.

A BAS contractor needed a Trane UC600 controller to expose data over Modbus RTU. Chipkin QuickServer handled the BACnet MS/TP to Modbus RTU protocol conversion, clarified the Trane UC600 point mapping, and delivered documentation that made commissioning easier.

For this systems integrator, the main issue was not whether BACnet MS/TP and Modbus RTU could be bridged. It was making sure the Trane UC600 data was presented in the right direction, with the right point definitions, and in a format the downstream Modbus RTU system could poll without extra guesswork.

At a Glance

  • Industry: Building automation
  • Location: Houston, Texas
  • Customer: BAS contractor / systems integrator
  • Facility type: Commercial building automation site
  • Project scale: Documented Trane UC600 handoff for a downstream Modbus RTU system
  • Protocols: From: BACnet MS/TP -> To: Modbus RTU
  • Chipkin product: Chipkin QuickServer
  • Project start: November 2021
  • Internal reference: FSE14305

Trane UC600 to Chipkin QuickServer to PLC or controller Modbus RTU diagram.

Trane UC600 -> BACnet MS/TP -> Chipkin QuickServer -> Modbus RTU -> PLC / controller

BACnet MS/TP to Modbus RTU Challenge

The upstream/server device was a Trane UC600 controller already communicating on BACnet MS/TP. The downstream/client requirement was a stable Modbus RTU presentation. That meant the project had to do more than pass traffic between two serial protocols. It had to define exactly how the Trane UC600 data should be exposed to the downstream Modbus RTU side.

A key challenge was clarifying the intended data flow early. The initial misunderstanding was not about whether the gateway could do the protocol conversion. It was about which side should act as the server and how the downstream system expected to consume the Trane UC600 points.

The customer also needed documentation that would make commissioning easier. In projects like this, a usable and current Trane UC600 point list matters almost as much as the gateway itself because it reduces field time spent second-guessing point meaning and downstream mapping.

Why Chipkin for BACnet MS/TP to Modbus RTU Integration

This project fit Chipkin because it combined a familiar protocol pair with a practical field need: make a Trane UC600 readable by a downstream Modbus RTU system and remove uncertainty from the handoff. QuickServer provided the protocol gateway platform, while Chipkin support helped the team validate the direction of data flow, reduce ambiguity in the Trane UC600 points package, and deliver documentation the customer could actually use.

That documentation focus mattered here. The commercial value was not just a working BACnet MS/TP to Modbus RTU bridge. It was a bridge the customer could commission with less guesswork.

The Solution: QuickServer BACnet MS/TP to Modbus RTU Bridge

Chipkin configured Chipkin QuickServer between the Trane UC600 and the downstream Modbus RTU network. The work centered on confirming the intended flow of Trane UC600 data, preparing the configuration around the BACnet MS/TP source, and delivering a points package that was easier for the downstream team to understand and use.

Instead of leaving the customer to sort out the translation details during startup, Chipkin helped package the integration into something easier to commission. That included organizing the Trane UC600 point information so the downstream Modbus RTU side was easier to interpret, easier to validate, and less dependent on field guesswork.

For another BACnet MS/TP retrofit, see the BACnet MS/TP to Metasys N2 Daikin Chiller Integration case study.

Trane UC600 Integration Results

The result was a successful BACnet MS/TP to Modbus RTU handoff for the Trane UC600 controller.

Project proof points:

  • The Trane UC600 protocol direction was clarified early enough to avoid downstream confusion.
  • The QuickServer configuration turned the BACnet MS/TP source into a usable Modbus RTU presentation.
  • The delivered Trane UC600 points list reduced ambiguity and made customer commissioning easier.
  • The customer called out the documentation quality as a meaningful part of the success.

That last point mattered enough for the customer to say:

“The points list that you put together really made my job a lot easier.”

— BAS technician, BAS integrator, Houston, Texas

Have a Similar BACnet-to-Modbus Project?

Need to expose Trane UC600 BACnet MS/TP points to a Modbus RTU client? Chipkin can help define the mapping, configure the gateway, and deliver documentation your team can commission with less guesswork. Tell us about your project.

Frequently Asked Questions

Can QuickServer convert BACnet MS/TP to Modbus RTU?

Yes. QuickServer can be used as a BACnet MS/TP to Modbus RTU protocol gateway. In this project, Chipkin used that path to expose Trane UC600 controller data to a downstream Modbus RTU system.

Can QuickServer integrate a Trane UC600 with Modbus RTU?

Yes. This case study is specifically about a Trane UC600 integration where QuickServer presented the BACnet MS/TP controller data as a Modbus RTU handoff.

Can Chipkin provide a points list for a Trane UC600 integration?

Yes, when the project scope calls for it. The delivered Trane UC600 points documentation was a major reason this customer found commissioning easier.