15.2 BAS Networks, Protocols, and NEC-Compliant Cabling

15.2 BAS Networks, Protocols, and NEC-Compliant Cabling

The Building Automation Networks competency block of the Competency and Task List requires: listing the layers 1–7 of the OSI model; explaining TCP/IP protocols; defining the bus, ring, and star topologies; describing Ethernet applications and operations; explaining RS-485 and RS-232 network standards; comparing different bus architectures used in the BAS industry; contrasting open networks to closed networks; listing and contrasting Modbus, LonWorks, BACnet, and OPC; explaining BAS network-addressing formats; defining "points" in a DDC control system; creating network diagrams; fabricating an Ethernet patch cable; demonstrating common cabling practices per NEC requirements; and wiring a unit controller to a room operator per NEC requirements.

Controllers themselves are covered in Section 15.3, sensors in Section 15.5, and output devices in Section 15.6. This section is about the wire and the language.

---

1. The OSI Model

A memory aid from the bottom up: Please Do Not Throw Sausage Pizza Away.

BACnet collapses this into four layers — application, network, data link, and physical — deliberately omitting transport, session, and presentation as unnecessary overhead for building control. This is a favorite exam question, because it is the one place where the standard seven-layer answer is not the right answer.

---

2. Topologies and Physical Layers

Topologies

RS-232 versus RS-485

RS-485 wiring rules that decide whether a network works:

• Twisted pair, shielded, of the impedance the manufacturer specifies. Use that cable, not "whatever thermostat wire is on the truck" — untwisted or wrong-impedance cable destroys the differential noise rejection that makes RS-485 work.
• Daisy chain only. No stars, no T-taps, no stubs. A star on RS-485 produces signal reflections and intermittent, maddening communication faults that look exactly like a failing device.
• Terminating resistors (typically 120 Ω) at both physical ends of the segment and nowhere else. Missing terminators cause reflections; extra terminators overload the drivers and pull signal amplitude down until marginal devices drop off.
• Ground the shield at one end only, usually at the supervisory controller. Grounding both ends creates a ground loop that injects the noise the shield was installed to reject.
• Observe polarity. The + and − (or A and B) conductors must be consistent at every device; one reversed pair takes down everything downstream.
• Separate from line voltage, always (Section 5 below).
• Match baud rate across the segment. MS/TP runs at 9,600, 19,200, 38,400, or 76,800 bps, and every device on the segment must agree. A single device set wrong does not simply fail to talk — it can corrupt the token pass for the whole segment.

Ethernet and TCP/IP

Ethernet is the star-topology physical and data-link standard for the IP backbone. Cat 5e is rated to 100 MHz, Cat 6 to 250 MHz, and Cat 6A to 500 MHz; the maximum channel length is 100 m (328 ft) — 90 m of horizontal cable plus 10 m of patch cords. Exceeding it does not fail cleanly; it produces intermittent errors that appear under load.

TCP/IP is the protocol suite the backbone runs on:

• IP (layer 3) addresses and routes packets. An address such as 10.20.30.11 with a subnet mask of 255.255.255.0 says the first three octets identify the network and the last identifies the host. Devices on different subnets need a gateway to reach each other — the most common reason a BAS device "is on the network" and still cannot be reached.
• TCP (layer 4) is connection-oriented and guarantees delivery and ordering.
• UDP (layer 4) is connectionless with no delivery guarantee — lower overhead, and what BACnet/IP uses.

Fabricating an Ethernet patch cable is a named task-list competency. The two pin-out standards are T568A and T568B; both ends must use the same standard for a straight-through patch cable, and a cable with T568A on one end and T568B on the other is a crossover. Keep the pair twist intact to within about half an inch of the connector — untwisting an inch of pair to make termination easier is what turns a Cat 6 run into a Cat 5 run. Terminate, then test with a cable tester for continuity, correct pin order, and split pairs. A split-pair fault passes a simple continuity test and fails under traffic.

---

3. Protocols and the Open Versus Closed Question

BACnet's self-description is the practical difference from Modbus. A BACnet device advertises its objects — an Analog Input named "Mixed Air Temp" with units of degrees Fahrenheit and a reliability flag. A Modbus device offers register 40012 holding the integer 725, and the technician must know from the manual that it is a temperature scaled by 10. Both work; one takes far more commissioning labor and far more documentation discipline.

Open versus closed is a real business issue, and the task list asks about it directly. A closed system means every future addition, every repair, and every service call goes through one vendor at that vendor's price, for the twenty-year life of the building. An open system lets the owner competitively bid service and add equipment from other manufacturers. "BACnet compatible" on a data sheet is not the same as BTL-listed — the BACnet Testing Laboratories listing is the evidence that a device actually conforms.

---

4. Addressing Formats

The task list asks for "BAS network-addressing formats used in the BAS industry." Three distinct identifiers coexist, and confusing them causes faults that look like wiring problems.

Modbus RTU uses its own scheme: slave addresses 1–247, unique on the segment.

Two devices with the same MAC on a segment produce intermittent dropouts on both, and the symptom is indistinguishable from a marginal cable. Two devices with the same device instance on the internetwork produce a device that appears and disappears from the discovery list. Verify addressing before re-pulling cable — it is the cheaper test.

A network diagram documents this: the IP backbone, each supervisory controller, each field-bus segment beneath it, and every device with its address. It is a logical map rather than a routing drawing, and it is what tells a technician at 2 a.m. which twenty devices a dead segment covers. The companion address schema table is covered in Section 15.7.

---

5. NEC Requirements for BAS Cabling

Every wiring task on the Building Automation sheet ends with "per NEC requirements."

• Article 725 governs Class 1, 2, and 3 circuits. Most BAS control and communication wiring is Class 2, power-limited.
• Separation from line voltage is mandatory. Class 2 conductors must not share a raceway, cable, or enclosure with power conductors unless separated by a barrier. A control pair zip-tied along a VFD output conduit is the origin of most "the sensor reads erratically" calls in a mechanical room.
• Article 800 / 805 covers communications circuits and Article 770 optical fiber where applicable.
• Plenum-rated cable (CMP) is required in ducts, plenums, and other spaces used for environmental air. Using riser-rated or general-purpose cable above an accessible ceiling that serves as a return plenum is a common and citable violation.
• Support cable properly on J-hooks or in tray at code intervals. Cable draped on ceiling grid, on piping, or on sprinkler lines is a violation everywhere.
• Maintain the fire rating. Firestop every penetration of a rated wall or floor with a listed assembly.
• Low-voltage licensing varies by state, and the task list asks the candidate to describe the process in their own state.
• Ampacity and voltage-drop calculations still apply at 24 V. A 40 VA transformer feeding a long run of 18 AWG to several actuators can drop enough voltage that a damper motor stalls — and the actuator gets replaced twice before anyone measures the voltage at the device under load (Section 2.4).

Wiring a unit controller to a room operator, the specific task the list names, brings all of it together: the correct conductor count and gauge for the model, plenum rating if the run crosses a plenum, separation from line voltage, consistent polarity, no splices in inaccessible locations, both ends labeled, and — if the operator sits on a sensor bus — a unique address.