- Cisco Meraki
We aren't tied to any brand. If your drawings call for something else, we'll install to the specification.
What a BAS looks like at the cabling layer
Telelink Business Services is a licensed C-7 Low Voltage Systems Contractor, CSLB License #472017. The C-7 classification text expressly names instrumentation and temperature controls, so this work sits well inside the license instead of at its edge.
Set aside the graphics and sequences, and a building automation system comes down to three layers of wire and network, plus the panels they land in.
- An IP backbone connecting supervisory controllers, the head end server or workstation, and any IP-native field controllers. It’s copper to the nearest telecom room and fiber between buildings.
- Controller trunks. Field controllers are daisy chained on a shielded twisted pair bus, most often BACnet MS/TP, that runs panel to panel through mechanical rooms, ceilings and shafts.
- Device home runs. Space temperature, CO2 and humidity sensors, occupancy sensors, differential pressure switches, current sensors and actuator control wiring, each one run back to its field controller or panel.
- Panels. Control panels in mechanical rooms and above ceilings. Each one needs a network drop, a pathway in, and terminations labeled well enough for the next technician to trace.
That’s the layer we install. What runs on top of it (the sequences, the graphics and the tuning) belongs to the controls integrator.
Protocols and what each one asks of the cable
| Protocol | Typical media | Topology | What the installation has to get right |
|---|---|---|---|
| BACnet MS/TP | Shielded twisted pair | Daisy chain | End-of-line termination, one shield ground, no T-taps |
| BACnet/IP | Cat6 or fiber | Star to a switch | VLAN, plus broadcast management across subnets |
| Modbus RTU | Shielded twisted pair | Daisy chain | Same bus rules, plus address and baud rate discipline |
| Modbus TCP | Cat6 | Star to a switch | Another device on the automation VLAN |
| LonWorks | Twisted pair | Free topology or bus | Termination matched to the chosen topology |
BACnet MS/TP is the workhorse at the field level. It’s a token passing protocol on a two wire RS-485 bus. Every device on the trunk shares one pair, only one device transmits at a time, and the physical bus has to behave like a bus. It’s much less forgiving of topology mistakes than Ethernet is.
BACnet/IP puts the same data model on Ethernet, and the wiring is ordinary structured cabling: one drop per controller, star to a switch, certified and labeled like any other link. When the network spans more than one IP subnet, a BACnet broadcast management device has to be configured so broadcasts can cross the boundary. The IT department and the integrator settle that one together.
Electrically, Modbus RTU behaves like MS/TP. It uses the same two wire bus and the same termination rules, with addressing and baud rate set per device. You’ll find it on meters, variable frequency drives, boilers and packaged equipment. Modbus TCP is its Ethernet version. LonWorks is still in service on older buildings and in some current specifications. It runs on twisted pair in either free topology or a bus, and whichever one the design uses changes where the terminator goes.
If you’re estimating, the protocol determines the cable, the topology and the labor. A floor of BACnet/IP controllers is a cabling job that looks a lot like a data floor. A floor of MS/TP unit controllers is a different job with a different crew rhythm, and it should be bid differently.
Daisy chain or home run: MS/TP topology rules
An MS/TP trunk has to be a daisy chain. The cable enters a device, lands, and leaves for the next one. That means no stars, no T-taps, and no spur off a junction box just because the run was easier that way.
When MS/TP devices are home run and jumpered together on a terminal strip, each of those runs becomes a stub hanging off the bus. Stubs reflect signal. The reflections show up as intermittent communication errors that slip past a quiet walkthrough, then start failing once the trunk is loaded. By that point the ceilings are closed.
Here are the rules we follow on MS/TP trunks:
- One continuous chain, with both physical ends identified on the drawing.
- End-of-line termination at both ends and nowhere else, at the value the controller manufacturer specifies.
- Device count and trunk length stay inside the manufacturer’s limits for the baud rate in use. If the design goes past them, a repeater goes in as a documented segment instead of a field improvisation.
- Polarity stays consistent the whole way. Reversing two wires at one device can mean half a day of hunting.
- Every device is labeled with the trunk name and its position on it, so the next technician can find the break instead of tracing the whole trunk.
Device home runs are the opposite. Each sensor and each controlled device gets its own cable back to its controller, point to point and simple. With home runs, the care goes into labeling, slack and pathway instead of topology.
Shielding, grounding, separation and cable ratings
Controls cable lives in mechanical rooms, right next to the noisiest equipment in the building. Variable frequency drives and their motor leads radiate broadband noise, and an unshielded trunk running alongside them picks it up.
Shielding. Trunk cable is shielded twisted pair with a foil shield and drain wire. The shield only works when it’s continuous and grounded at exactly one end, normally at the controller panel. We carry the drain through each device without landing it and cap it at the far end. We never ground both ends, because two grounds create a loop that puts current on the shield and makes the noise worse.
Separation. Controls cable stays out of conduit shared with line voltage conductors and away from VFD output leads. Where a crossing with power can’t be avoided, it crosses at right angles. If enough separation isn’t achievable, the usual answer is metallic conduit.
Cable ratings. We use plenum rated cable in ceilings and spaces used as return air plenums, and riser rated cable in vertical shafts. The rating has to match every space the cable passes through, and not only the space where it starts. We support it on J-hooks at proper intervals. It doesn’t get draped on ceiling tile, tied to sprinkler pipe, or laid on ductwork.
Gauge and cable selection follow the controller manufacturer’s requirement for the bus. We submit actual part numbers for the controls manufacturer to confirm before anyone buys a reel. Line voltage power to control panels, transformers and mechanical equipment is electrical scope performed by a licensed C-10 contractor, and our submittal shows where our work ends and theirs begins.
Putting the BAS on the building IP network
With every product cycle, more of the automation system moves onto Ethernet. Supervisory controllers, IP-native field controllers, meters and rooftop unit controllers all need a drop, and those drops land in the same telecom rooms as everything else.
The automation system should get its own VLAN. Building controllers aren’t general purpose computers. They ship with default credentials, sit on long firmware cycles, and are managed by a vendor who visits a few times a year. On their own segment, a compromised controller has far less it can reach. It shouldn’t be able to get to the file server, the camera network, or the tenant Wi-Fi.
The rest is basic, but we still put it in writing. No automation device is exposed directly to the internet. The integrator’s remote access goes through the owner’s VPN or an IT-approved gateway, instead of a port forward someone opened during startup and forgot about. Default credentials get changed, recorded, and turned over to the owner at closeout along with the VLAN and addressing.
Physically, it’s the same cabling we install everywhere else. That means Cat6 or Cat6A drops certified and labeled like the data floor, fiber between buildings, switches with the PoE budget counted, and rooms built to the same standard. Our structured cabling and network room buildout scopes cover that side. On a campus, the automation backbone rides the same fiber as everything else.
Commissioning support and point to point checkout
Point to point checkout is where good cabling proves itself and bad cabling starts costing the job time. For each point, we confirm that the field device matches the point list and the cable is landed on the correct terminal at both ends. We also check that polarity is right, the shield is grounded at one end only, and the value reads at the controller. We check analog inputs against a known condition instead of accepting them just because a number showed up on a screen.
We keep the record as we go: a point list cross referenced to cable IDs, labels at both ends of every cable, and a marked-up drawing of trunk routing and device positions. Say the commissioning agent starts functional testing and a damper doesn’t move. The first question is whether it’s a wiring problem or a programming problem, and a documented installation usually answers that quickly.
Writing and verifying the sequence of operations is the job of the integrator and the commissioning agent. Confirming that an economizer behaves correctly across outside air conditions happens on their side of the point list. We verify the wire, support their testing, and fix what turns up on our side of the point list.
Coordinating with mechanical and the controls integrator
Building automation is a common place for scope gaps. It crosses four trades, and each one can assume another trade bid the wire.
- Mechanical contractor: the equipment, the actuators, valves and dampers, and the wells and taps that sensors mount into.
- Electrical contractor (C-10): line voltage to control panels and transformers, motor power, and disconnects.
- Controls integrator: controllers, the sequence of operations, programming, graphics, the point list, and system commissioning.
- Telelink: pathway, trunk and device cabling, terminations, labeling, the IP backbone, switching and telecom rooms, and point to point checkout support.
Five questions clear it up, and we like to get them answered in writing at the first coordination meeting:
- Who lands wire on the controller terminal strip, our technician or the integrator’s?
- Who issues the point list, and by what date? It doubles as the cable schedule.
- Who furnishes and mounts the control panels?
- Which sensors are furnished by the integrator and which by mechanical, and who mounts them?
- Are the mechanical room network drops in anyone’s package?
Once those are answered, the automation scope is much less likely to turn into a closeout argument. Our Division 27 and Division 28 spec checklist covers the same kind of gap across the other low voltage packages.
Next step
When you have controls drawings, send them through request a bid with the point list if there is one and the mechanical equipment schedule. We’ll send back a cable count by type, a trunk layout, an IP drop count and a price. We’ll also write out where our scope stops and the mechanical, electrical and integrator scopes start, so each trade’s part is on paper. General contractors can find our prequalification packet at for general contractors.