Study guide
15.4 Digital Logic, Numbering Systems, and Controller Programming
HVAC Excellence Certification Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Introduction, Safety, Tools, and Diagnostic Method
1.1 HVAC Excellence Certification, Industry Codes, and Standards 1.2 Electrical Safety, PPE, Lockout/Tagout, and Hazard Communication 1.3 Multimeters, Manifold Gauges, Micron Gauges, and Diagnostic Instruments 1.4 HVACR Mathematics, Unit Conversions, and Efficiency Ratings 1.5 OSHA Standards, Fall Protection, Rigging, and Confined Spaces 1.6 HVACR Industry Organizations, Energy Resources, and Building Energy Programs 1.7 Systematic Troubleshooting: Data Plates, Manufacturer Literature, and Diagnostic Method
2 Chapter 2: Electrical Fundamentals and Circuit Theory
2.1 Voltage, Current, Resistance, and Ohm's Law Calculations 2.2 Series, Parallel, and Series-Parallel Circuits and Power Calculations 2.3 AC Fundamentals, Single-Phase vs Three-Phase Power, and Control Transformers 2.4 Conductors, Insulators, Wire Sizing, Voltage Drop, and NEC Ampacity
3 Chapter 3: Electrical Components, Motors, and Schematics
3.1 Contactors, Relays, Switches, Overload Protection, and Thermostats 3.2 HVAC Motors (PSC, CSIR, CSCR, ECM, 3-Phase) and Run/Start Capacitors 3.3 Interpreting Ladder Diagrams, Schematics, and Point-to-Point Wiring 3.4 Motor Testing, Insulation Resistance, Bearings, and Belt Drives
4 Chapter 4: Thermodynamics and the Refrigeration Cycle
4.1 Heat Transfer, Temperature Scales, BTUs, Sensible vs Latent Heat, and Enthalpy 4.2 The Four Vapor-Compression Cycle Stages (Compression, Condensation, Expansion, Evaporation) 4.3 P-T Charts, Saturated Conditions, Target Superheat, and Subcooling Calculations 4.4 Pressure–Enthalpy Diagrams, Compression Ratio, and Cycle Analysis
5 Chapter 5: Refrigerants, Environmental Regulations, and Recovery
5.1 Refrigerant Types (CFC, HCFC, HFC, HFO, HC) and ASHRAE Safety Groups (A1, A2L, A3) 5.2 EPA Section 608 Regulations, Venting Prohibitions, and Evacuation Standards 5.3 Recovery/Recycling/Reclaiming Equipment, Procedures, and Leak Detection 5.4 Refrigerant Retrofits, Cylinder Handling, and Refrigerant Purity 5.5 A2L and Low-GWP Refrigerants: Codes, Charge Limits, and Service Practice
6 Chapter 6: Refrigeration System Components and Accessories
6.1 Compressor Mechanics (Reciprocating, Scroll, Rotary, Screw) and Failures 6.2 Expansion Devices (TXV/TEV, Fixed Orifice, EEV) and Superheat Control 6.3 Condensers, Evaporators, Filter-Driers, Accumulators, Receivers, and Solenoids 6.4 Pressure Controls, Capacity Controls, and System Protection 6.5 Refrigerant Line Sizing, Pressure Drop, Brazing, and Piping Practice
7 Chapter 7: Gas Heating, Combustion Analysis, and Fuel Piping
7.1 Combustion Theory, Fuel Gases (Natural Gas vs LP), and Gas Burners 7.2 Gas Valves, Ignition Systems (Standing Pilot, Spark, HSI), and Safety Limit Controls 7.3 Flue Venting, Draft Principles, Combustion Analysis, and CO Safety 7.4 Fuel-Gas and Oil Piping, Vent System Selection and Sizing, and Installation Practice
8 Chapter 8: Electric Heating, Oil Heat, and Hydronics
8.1 Electric Heating Elements, Sequencers, Limit Switches, and kW Calculations 8.2 Oil Burners, Fuel Pumps, Nozzles, Ignition Electrodes, and Primary Controls 8.3 Hydronic Boilers, Circulator Pumps, Expansion Tanks, and Zone Controls 8.4 Combustion Air, Water Heaters, and Combustion Appliance Zone Testing
9 Chapter 9: Heat Pumps and Dual-Fuel Systems
9.1 Heat Pump Operation in Heating/Cooling Modes and Reversing Valve Operation 9.2 Defrost Controls (Time-Temperature, Demand Defrost), Sensors, and Sequences 9.3 Balance Points, Auxiliary/Emergency Heat, and Dual-Fuel (Hybrid) Systems 9.4 Heat Pump Diagnostics, Refrigerant Flow, and Troubleshooting Procedures 9.5 Heat Pump Types, Cold-Climate Performance, and Sizing Approaches
10 Chapter 10: Air Distribution, IAQ, and System Commissioning
10.1 Airflow Fundamentals, CFM Measurement, External Static Pressure, and Fan Laws 10.2 Duct Sizing Principles, Supply/Return Distribution, Dampers, and Air Balancing 10.3 Indoor Air Quality, MERV Ratings, Electronic Cleaners, Humidification, and Dehumidification 10.4 Deep Vacuum Evacuation (Micron Gauge), Subcooling/Superheat Charging, and System Commissioning 10.5 Duct Leakage, Blower Door Testing, and Building Envelope Performance
11 Chapter 11: Psychrometrics, Airside Calculations, and Load Estimation
11.1 Reading the Psychrometric Chart: Properties and Plotting 11.2 The Eight Air-Conditioning Processes and the Process Triangle 11.3 Mixed Air, Ventilation, and Infiltration Calculations 11.4 Residential Heat Loss, Heat Gain, and Equipment Sizing
12 Chapter 12: Light Commercial Air Conditioning
12.1 Packaged Rooftop and Split Light-Commercial Systems 12.2 Water-Cooled Condensers, Cooling Towers, and Chilled-Water Systems 12.3 Economizers, Demand-Controlled Ventilation, and VAV Air Distribution 12.4 Light-Commercial Start-Up, Commissioning, and Troubleshooting
13 Chapter 13: Light Commercial Refrigeration
13.1 Temperature Ranges, Box Loads, and Refrigeration System Types 13.2 Evaporators, Defrost Methods, and Defrost Controls 13.3 Condensing Units, Parallel Racks, Oil Management, and Capacity Control 13.4 Refrigeration Control Valves and Automatic Pump-Down 13.5 Commercial Refrigeration Diagnostics and Ice Machines
14 Chapter 14: Ductless, Mini-Split, and VRF Systems
14.1 Mini-Split Architecture and Inverter-Driven Compressors 14.2 Multi-Zone and VRF Operation, Electronic Expansion Valves, and Controls 14.3 Ductless Installation, Evacuation, Charging, and Diagnostics
15 Chapter 15: Building Automation and Digital Controls
15.1 DDC Fundamentals, Control Loops, and Sequences of Operation 15.2 BAS Networks, Protocols, and NEC-Compliant Cabling 15.3 Building Automation Controllers: Supervisory, Field, and Room Devices 15.4 Digital Logic, Numbering Systems, and Controller Programming 15.5 Sensor Selection, Installation, and Input Point Configuration 15.6 Actuators, Output Devices, and VFD Integration 15.7 Commercial Prints, Equipment Schedules, and BAS Documentation
15.4 Digital Logic, Numbering Systems, and Controller Programming
Key Takeaways Explain This Topic AI
Relay logic, ladder logic, truth tables, Boolean algebra, and logic gates are five notations for the same information, and the task list requires converting between them.
A series contact pair is a logical AND; a parallel contact pair is a logical OR; a normally-closed contact used as an input is a NOT.
Binary, octal, decimal, and hexadecimal are the four numbering systems named on the Competency and Task List; one hexadecimal digit represents exactly four binary bits.
BAS data points are numeric (analog), Boolean (binary), enumerated (multi-state), or string, and choosing the wrong type makes a value unusable in logic.
Analog communication transmits a continuously variable signal such as 0-10 VDC or 4-20 mA, while digital communication transmits discrete encoded values and is immune to signal-level drift.
Last updated: August 2026
15.4 Digital Logic, Numbering Systems, and Controller Programming
The Building Automation sheet contains a competency block titled Digital Logic and Programming . It requires:
Comparing the following expressions of logic — relay logic, truth tables, ladder logic, Boolean algebra, logic gates
- Defining decimal, binary, octal, and hexadecimal numbering systems
- Contrasting analog and digital communications
- Defining microprocessor control systems
- Identifying data point types: numeric, Boolean, enumerated, string
- Converting between the different expressions of logic (e.g., relay logic to truth tables)
- Developing flow charts for simple programs
- Connecting a laptop/workstation to a field controller and using it to configure the controller
- Programming controllers using line programming, icon-based programming, or block programming
This is the block that connects the ladder diagrams of Chapter 3 to the DDC controller of Chapter 15. The relay logic a technician already reads on a furnace schematic and the Boolean expression inside a controller are the same statement written two ways.
1. Five Notations, One Statement
Consider a supply fan that must run when the schedule is occupied AND the smoke detector is normal . Here is that single requirement in all five notations the task list names.
Relay logic (physical contacts in series): L1 ---[ Schedule Relay ]---[ Smoke Det. NC ]---( Fan Starter )--- L2
- Ladder logic (the same, drawn as a controller rung): Occupied Smoke_Normal Fan_Cmd
- ---] [------------] [--------------------( )----
- Logic gate: Occupied -----|\
- | )AND >---- Fan_Cmd
- Smoke_Normal -----|/
Boolean algebra: Fan_Cmd = Occupied ⋅ Smoke_Normal \text{Fan\_Cmd} = \text{Occupied} \cdot \text{Smoke\_Normal} Fan_Cmd = Occupied ⋅ Smoke_Normal
Truth table:
- Occupied Smoke_Normal Fan_Cmd
- 0 0 0
- 0 1 0
- 1 0 0
- 1 1 1
All five say the same thing. The exam asks you to move between them, so learn the three translation rules:
- Circuit arrangement Logic function Boolean operator
- Contacts in series AND A ⋅ B A \cdot B A ⋅ B
- Contacts in parallel OR A + B A + B A + B
- A normally-closed contact used as an input NOT (inversion) A ‾ \overline{A} A
- 2. The Gates and Their Truth Tables
- Gate Symbol notation Output is 1 when… Boolean
- AND ⋅ \cdot ⋅ all inputs are 1 A ⋅ B A \cdot B A ⋅ B
- OR + + + any input is 1 A + B A + B A + B
- NOT (inverter) overbar the input is 0 A ‾ \overline{A} A
- NAND not all inputs are 1 A ⋅ B ‾ \overline{A \cdot B} A ⋅ B
- NOR no input is 1 A + B ‾ \overline{A + B} A + B
- XOR (exclusive OR) ⊕ \oplus ⊕ inputs differ A ⊕ B A \oplus B A ⊕ B
Two-input truth table for the common gates:
- A B AND OR NAND NOR XOR
- 0 0 0 0 1 1 0
- 0 1 0 1 1 0 1
- 1 0 0 1 1 0 1
- 1 1 1 1 0 0 0
Where XOR shows up in HVAC: an XOR of "heating valve open" and "cooling valve open" is a simultaneous heating and cooling alarm — the output is 1 whenever exactly one is open, so a 0 with both open flags the fault. It is also the core of a changeover-mode check.
A Boolean identity worth memorizing (De Morgan's theorem): A ⋅ B ‾ = A ‾ + B ‾ and A + B ‾ = A ‾ ⋅ B ‾ \overline{A \cdot B} = \overline{A} + \overline{B} \qquad\text{and}\qquad \overline{A + B} = \overline{A} \cdot \overline{B} A ⋅ B = A + B and A + B = A ⋅ B
In plain language: "not (both)" is the same as "either one is not." This is why a safety chain can be drawn either as a series string of normally-closed safeties feeding an enable, or as a parallel string of alarm flags feeding a shutdown — and why the two drawings are equivalent.
3. Numbering Systems
The task list names four: decimal, binary, octal, hexadecimal . Each is defined by its base — the number of distinct digits it uses.
- System Base Digits Where it appears in BAS
- Decimal 10 0–9 Setpoints, engineering units, device instance numbers
- Binary 2 0, 1 The controller's native form; binary points; DIP-switch addressing
- Octal 8 0–7 Legacy addressing and some file permissions; rare in modern BAS
- Hexadecimal 16 0–9, A–F MAC addresses, IP notation in some tools, memory addresses, protocol frames
Place values. Each column is the base raised to its position, counting from zero on the right.
Binary 1011 2 1011_2 101 1 2 : 1 ( 2 3 ) + 0 ( 2 2 ) + 1 ( 2 1 ) + 1 ( 2 0 ) = 8 + 0 + 2 + 1 = 11 10 1(2^3) + 0(2^2) + 1(2^1) + 1(2^0) = 8 + 0 + 2 + 1 = 11_{10} 1 ( 2 3 ) + 0 ( 2 2 ) + 1 ( 2 1 ) + 1 ( 2 0 ) = 8 + 0 + 2 + 1 = 1 1 10
Hexadecimal 2 F 16 2F_{16} 2 F 16 : 2 ( 16 1 ) + 15 ( 16 0 ) = 32 + 15 = 47 10 2(16^1) + 15(16^0) = 32 + 15 = 47_{10} 2 ( 1 6 1 ) + 15 ( 1 6 0 ) = 32 + 15 = 4 7 10
The conversion shortcut that matters most. One hexadecimal digit represents exactly four binary bits , because 16 = 2 4 16 = 2^4 16 = 2 4 . So converting between binary and hex requires no arithmetic — just group the bits in fours from the right: 1011 1110 2 → 1011 ⏟ B 1110 ⏟ E → B E 16 1011\,1110_2 \;\rightarrow\; \underbrace{1011}_{B} \; \underbrace{1110}_{E} \;\rightarrow\; BE_{16} 1011 111 0 2 → B 1011 E 1110 → B E 16
The same trick works for octal in groups of three bits, because 8 = 2 3 8 = 2^3 8 = 2 3 .
- Decimal Binary Octal Hex
- 0 0000 0 0
- 5 0101 5 5
- 8 1000 10 8
- 10 1010 12 A
- 15 1111 17 F
- 16 10000 20 10
- 255 11111111 377 FF
Why a service technician cares: an 8-bit value tops out at 2 8 − 1 = 255 2^8 - 1 = 255 2 8 − 1 = 255 , which is why so many limits in networking are 255 and why a DIP-switch address block of eight switches addresses 0 through 255. When a tool reports a device address as 1A and the drawing says 26 , they are the same device — 1 A 16 = 26 10 1A_{16} = 26_{10} 1 A 16 = 2 6 10 .
4. Analog Versus Digital Communication
- Analog Digital
- Signal Continuously variable Discrete encoded states
- HVAC examples 0–10 VDC, 4–20 mA, 0–135 Ω, 3–15 psi pneumatic BACnet MS/TP, Modbus RTU, Ethernet
- Conductors per value One pair per point One pair carries hundreds of points
Effect of noise / voltage drop Directly corrupts the value Rejected until the error is large enough to break the frame
- Diagnostics available The value only Value plus status, reliability flag, units, alarm state
- Failure mode Silent drift — a wrong number that looks right Loud — the point goes offline or unreliable
The 4–20 mA advantage is worth understanding: because it is a current loop, series resistance in the wire does not change the current, so long runs do not shift the reading the way a 0–10 VDC signal does. And because the live zero is 4 mA , a broken wire reads 0 mA — a value outside the valid range, which the controller can flag as a fault. A 0–10 VDC signal with a broken wire reads 0 V, which is indistinguishable from a legitimate 0% command. This is the classic exam contrast.
A microprocessor control system is any system in which a programmed processor reads inputs, executes stored logic on a repeating scan cycle , and writes outputs. The distinction from electromechanical control is that the behavior lives in software, so changing the sequence changes no wiring — and equally, a logic error changes nothing visible in the panel.
5. Data Point Types
The task list requires identifying numeric, Boolean, enumerated, and string data points. Choosing the wrong type is a common commissioning error because the point will display correctly and still be unusable in logic.
Type Holds BACnet object Example
Numeric (analog) A continuous value with engineering units Analog Input / Output / Value 72.4 °F; 1.25 in. w.c.; 43%
Boolean (binary/digital) Exactly two states Binary Input / Output / Value Fan status On/Off; alarm True/False
Enumerated (multi-state) One of a defined list of named states Multi-state Input / Output / Value Mode = {Off, Heat, Cool, Auto}; Occupancy = {Occupied, Unoccupied, Standby}
String Text Character String Value Equipment tag; alarm message; a technician's note
Why the distinction bites. An operating mode with four states written as a numeric point stores 0, 1, 2, 3 with no labels — the graphic shows "2" and nobody remembers what 2 means. Written as an enumerated point it shows "Cool," and logic can test for the named state. Conversely, a value stored as a string cannot be compared numerically or trended: "72.4" as text will not drive a control loop, even though it looks identical on screen.
6. Flow Charts and Programming Methods
Flow charts are a named competency, used to document a sequence before writing it. The standard shapes: an oval terminator for start/stop, a rectangle for a process or action, a diamond for a decision with labeled Yes/No branches, and a parallelogram for input/output.
Loading diagram... Flow Chart: Supply Fan Start Sequence
Drawing this before programming exposes the questions that matter — what happens if status never proves, what the dampers do in unoccupied mode — while they are still cheap to answer.
Three programming methods , all named on the task list:
Method What it looks like Strengths
Line programming Text statements, one per line, in a manufacturer's control language Compact, powerful, easy to diff and archive; steepest learning curve
Block (function block) programming Graphical blocks — PID, AND, timer, comparator — wired together Data flow is visible; the standard for Niagara-style tools
Icon-based programming Pre-built application icons dragged onto a canvas and parameterized Fastest; least flexible; closest to a configurable controller
Connecting to the controller. Field controllers expose a service port — USB, a serial jack, or an IP connection. The workflow does not change with the programming method: connect, upload and archive the running program , edit offline, download, then verify with live point values and a functional test. Never edit live on a running controller in an occupied building unless the change is trivial and reversible.
Documentation is part of programming. Comment the logic, keep the archived program with the address schema and the points list (Section 15.7), and label the controller with the file name of its program. A brilliant sequence nobody can find the source for is a controller that gets replaced instead of repaired.