The real cost driver in a retrofit is cable, not controllers
Ask anyone who has priced a controls retrofit in an occupied building: the controllers are rarely what breaks the budget. Pulling new cable is. Standard Ethernet over Cat5e or Cat6 is limited to roughly 100 metres, which is fine in a data closet and nearly useless when the air handler is four floors and 300 metres away from it.
So the industry worked around it. You either drop a switch and a small enclosure every 100 metres, or you give up on IP at the edge and run a serial trunk — typically RS-485 running MS/TP — out to the field devices. That second option is why so many buildings still have a slow, hard-to-diagnose daisy chain doing the most important work in the building.
In an existing building, new cable is not just cable. It is ceilings, conduit, fire-stopping, asbestos surveys, after-hours access, and tenants who did not agree to any of this. That is the constraint T1L relaxes.
What T1L actually is
10BASE-T1L is an Ethernet physical layer standardised in IEEE 802.3cg. The specifics that matter for our work:
What it gives you
- 10 Mbps full duplex — orders of magnitude more headroom than a typical MS/TP trunk.
- Up to 1,000 m on a single twisted pair — roughly ten times the reach of Cat5e/Cat6.
- Power over the same pair, so a field device can take data and power on two conductors.
- Native BACnet/IP. T1L is Ethernet, so BACnet/IP rides on it directly — no gateway, no protocol translation, no mapping table to maintain.
- Real IP diagnostics at the device: addressing, link status, and the option of BACnet/SC for secure transport.
What still needs engineering
- T1L links are point-to-point. A daisy-chained MS/TP trunk generally cannot be reused as-is — you re-terminate as home runs or place T1L switches in the field. This is the caveat most often skipped.
- Both ends must be T1L-capable — controller and switch port. The device ecosystem sets the boundary of what is possible today.
- Existing cable has to be tested, not assumed. Age, splices, shield continuity and unknown junctions all decide whether reuse is real.
- Crews and tools. It is Ethernet, so it is troubleshooting with network tools, not a multimeter and a token-passing mental model.
Why this makes retrofits genuinely cheaper
The headline is simple: you can often reuse the pair that is already in the wall. Where a building has usable twisted-pair control cable — frequently the same pairs that were carrying RS-485 — T1L lets that copper carry full Ethernet to the device instead of a slow serial protocol. The expensive part of the job, opening up an occupied building to pull new cable, gets much smaller or disappears.
The second win is architectural. Once field devices are IP nodes, the supervisory layer stops being a translation exercise. Trends, alarms and diagnostics come from the device rather than from a gateway's interpretation of the device, and modern security options become available on a network that used to be a bare serial bus.
We deploy this on the Honeywell line, where T1L-capable field controllers pair well with the Niagara supervisory standard we build on. It is the clearest example we have of new hardware making the installation cheaper rather than just adding features.
What this looks like on real projects
Two patterns come up repeatedly, and both have won us work.
1. Reusing the comm bus other bidders wrote off. We have won multiple competitive opportunities where other contractors scoped a full re-pull of the communication run — and priced it accordingly. Where the existing pair tests out, T1L lets that same copper carry Ethernet instead, and the re-pull line item comes off the estimate. Same building, same outcome, materially lower number. Owners notice.
2. Using T1L as a long-run bridge for equipment that isn’t T1L. You do not need T1L-native controllers on both ends to benefit. At the Cherry Creek Schools Innovation Campus we had a run of more than 2,000 feet between wings — far past what standard Ethernet will carry. We placed T1L media adapters at each end and used T1L for the span itself, sharing data between the two wings over a single pair. Standard equipment on both sides; T1L doing the distance in the middle.
That second pattern is the one most people miss. T1L is often discussed as a field-device technology, but as a point-to-point transport it quietly solves the classic campus problem: two buildings, one long run, and no appetite for fiber trenching or a string of intermediate closets. Media adapters that convert standard Ethernet to a single pair are readily available — WAGO and Honeywell both make one — so the parts are not exotic. The engineering is in knowing when it applies and verifying the copper first.
How we scope a T1L retrofit
Step 01Survey the copper
Identify and test the existing pairs, the actual topology, and where home runs already exist. This determines whether reuse is real or wishful.
Step 02Design the topology
Point-to-point links, switch placement, power budget and IT coordination — agreed before hardware is ordered.
Step 03Stage the cutover
Verify the new path point-to-point, then transfer with a defined fallback — often on live equipment in an occupied building.
Step 04Document it
As-builts, addressing and sequences handed over so the next contractor — whoever that is — can work on your building.
The honest summary. T1L is not magic and it is not a reason to replace a healthy system. It is a very good answer to one specific, expensive problem: getting modern IP controls into a building where pulling new cable is the thing that kills the project. When that is your situation, it is worth asking about by name.
