Identify every supply
Record line power, transformer secondaries, DC supplies, branch protection, shared sources and backfeed paths.
HVAC OEM · BAS integration · Panel engineering
Terminal Blocks for HVAC Control Panels
Select and arrange the terminal strip by circuit family—not as one generic row. Separate power, protective earth, control supplies, discrete I/O, analog sensors, BACnet or other communications, shields, VFD interfaces and governed safety functions. Then make the terminal schedule mirror the physical strip, controller point list and approved equipment drawings.
Map every circuit firstVoltage alone does not define function, classification, noise sensitivity or protection.
Keep references explicitCOM, 0 V, signal return, shield, functional earth and PE are not synonyms.
Preserve network topologyA terminal row must not hide an unintended RS-485 branch, polarity reversal or EOL error.
Release one traceable packageSchematic, I/O list, terminal schedule, markers, BOM and test record must agree.
Product-family illustration: SENTOP Electrical Co., Ltd. The image does not establish that every pictured terminal or accessory is suitable for an HVAC, BACnet, VFD, PE or life-safety circuit.
Direct answer
Use a circuit-family terminal strategy
Terminal blocks for HVAC control panels are dependable when each connection has a documented electrical function, circuit classification, source, reference relationship, product rating, conductor rule and service method. Start from the sequence of operations, controller I/O list and field-device data—not terminal color or available rail space.
Name the circuit family
Separate power, PE, supply, digital, analog, sensor, network, shield, VFD and governed interlock functions.
Define every “common”
State whether a conductor is supply return, signal reference, network reference, shield path or protective earth.
Match exact products
Verify terminal function, catalog number, conductor, accessories, ratings, approvals, geometry and environment.
Plan testing and access
Provide approved test points, readable markers, field/panel-side identity, tool clearance and restoration records.
Control one dataset
Keep the schematic, point list, terminal plan, jumper map, labels, BOM, FAT and as-built revision synchronized.
24 V is not a circuit classification. In North American work, a 24 VAC or 24 VDC label does not by itself establish Class 2, a permitted wiring method, low available fault energy or separation rules. Record the source, listing or classification, protective device and adopted code basis before applying a routing decision. The guide to common PLC panel terminal-block mistakes adds broader I/O context.
Electrical safety boundary. A disconnect or test terminal is a functional circuit point, not an energy-isolating device and not proof of an electrically safe work condition. Nominal current is not a load-breaking rating; do not open a disconnect/test terminal under load unless the exact product and approved procedure authorize that operation. Qualified personnel must identify all sources, apply the governing lockout/tagout and safe-work procedure, and verify absence of voltage with properly rated equipment where required. A push button, BAS command, selector switch, interlock or locally opened terminal is not the sole means of de-energizing equipment.
Circuit-family map
Review the control-panel wiring guideMap the HVAC circuits before choosing terminal blocks
The same enclosure can carry circuits with very different voltage, energy, signal, topology and service consequences. The categories below are a design inventory—not a universal strip order.
| Circuit family | Typical HVAC examples | Terminal-strip response | Evidence that controls |
|---|---|---|---|
| Power and distribution | Panel supply, transformer primary, branch distribution, fan/pump circuits and VFD input. | Use the correct power terminal or listed distribution method, protection architecture, conductor and fault-duty evidence. Keep a visible boundary from controls. | Single-line, panel standard, protective-device data, available fault current, product certification and equipment manual. |
| Protective earth (PE) | Motor PE, VFD PE, enclosure bonding and field-cable protective conductors. | Use an exact PE terminal and approved rail/bonding arrangement. Do not substitute a gray feed-through block or controller common. | Protective-bonding design, IEC 60947-7-2 or applicable product evidence, panel/equipment instructions and verification plan. |
| Control supply | 24 VAC transformer secondary, 24 VDC supply, actuator power, controller supply and relay coils. | Identify source, phase/polarity, return, protection, commoning and circuit classification. Separate different sources rather than joining by label. | Transformer/supply and controller diagrams, load calculation, circuit classification and protection schedule. |
| Discrete I/O | Fan proof, damper end switch, condensate alarm, filter switch, enable relay and permissive contacts. | Use labeled feed-through, fuse, disconnect/test or interface functions as required. Preserve NO/NC logic and fail state in the schedule. | I/O list, sequence of operations, field-device contact rating, controller input/output manual and authorized test method. |
| Analog and sensors | 0–10 V, 2–10 V, 4–20 mA, thermistors, pressure sensors, RTDs and actuator feedback. | Record signal type, source/sink or active/passive loop, reference, cable and shield plan. Route away from incompatible switching and motor circuits. | Transmitter/actuator and controller manuals, cable specification, input burden/common-mode data and EMC plan. |
| BAS communications | BACnet MS/TP, another RS-485 network, controller trunk or gateway connection. | Create a dedicated bus group that preserves polarity, reference/shield convention, trunk path and end-of-line responsibility. Do not create an arbitrary star hub. | Installed controller/router manual, network design, ANSI/ASHRAE 135 basis, cable and segment record. |
| VFD and motor interfaces | Run enable, speed reference, fault relay, STO/control inputs, line/motor conductors and shield paths. | Keep high-energy power and low-level control interfaces deliberate. Attach the drive-specific routing, grounding, shielding, discharge and isolation requirements. | Selected VFD manual, motor/cable data, EMC design, safety function file and panel fault-duty review. |
| Governed safety interfaces | Fire/smoke interface, freeze protection, high limits, emergency functions and safety interlocks. | Preserve the approved hardwired or listed architecture, supervision and fail-safe state. Do not treat these points as ordinary BAS conveniences. | Equipment listing, sequence, adopted code, AHJ requirements, manufacturer instructions and authorized impairment/test procedure. |
Special sensor paths need their own detail. Thermocouples and resistance temperature detectors (RTDs) can require alloy, cold-junction and lead-compensation decisions that a generic analog-terminal row does not capture. See the guide to thermocouple and RTD terminal blocks.
Field-device boundary
A point name is not a complete terminal specification
A damper actuator can need supply, command, feedback and common conductors. A separate damper switch can provide proof or an interlock. Two devices located at the same duct section can therefore create different circuit families, voltage references and commissioning records.
Record the field tag, exact device model, supply, signal range, wiring topology, conductor/cable, shield requirement, normal state and controller destination before choosing the terminal. A current Belimo actuator example uses AC/DC 24 V with 2–10 V control and feedback; that product-specific data must not be generalized to every actuator.
- Separate command, feedback and proof rather than naming everything “damper.”
- Keep the transformer/source identity attached to every powered field device.
- Do not infer a controller common or shield connection from wire color.
- Show which circuit is opened, fused or tested and what its normal state is.
Terminal function
Use the terminal block selection guideChoose the function—not a generic connection point
Similar housings can perform materially different jobs. Record the exact function in the schematic, terminal schedule, BOM, layout and marker file.
Feed-through
Provides a labeled field-to-panel path for a compatible conductor and circuit.
Not automatically fused, testable, load-break rated, PE-approved or shield hardware.PE terminal
Connects a protective conductor through an evaluated rail or bonding arrangement.
Keep PE separate from controller common, functional earth and a cable shield.Fuse or component
Holds a specified fuse or component for a documented control circuit.
The holder does not select the fuse, protection class or branch-circuit duty.Disconnect or test
Supports a released loop-check, isolation or measurement method.
It is not automatically an energy-isolating device or permission for energized testing.Multi-level or multi-wire
Groups related conductors when levels, potentials and connection limits stay explicit.
A position, level, conductor port and electrical node are different counting units.Feed-in and jumper system
Distributes a verified source or reference through approved commoning accessories.
Check feed path, bridge current, pole pattern and every load; fit alone is not evidence.Shield terminal or clamp
Connects a cable screen to a documented chassis or functional-bonding path.
It does not decide the topology, become PE or 0 V, or provide strain relief by default.Pluggable or interface
Supports factory/field separation or a replaceable equipment module when mating parts agree.
Verify coding, retention, complete current path, approvals and controller acceptance.IEC 60947-7-1:2025 covers terminal blocks and Annex D test-disconnect terminal blocks for copper conductors. Protective-conductor terminal blocks are addressed separately by IEC 60947-7-2, while fuse terminal blocks have additional requirements in IEC 60947-7-3. Land only the conductor number, material, type and size identified for the exact connection; physical fit does not permit double-lugging, and a copper-only terminal does not accept aluminum. A PE terminal that bonds through rail is part of the protective path only when the exact terminal, rail, mounting and bonding arrangement is approved.
Reference and grounding map
Review shield-terminal boundariesResolve COM, 0 V, REF, shield and PE
Short labels are convenient on a controller face, but they are not permission to join circuits. Expand each label into a function, source and destination in the terminal schedule.
| Label | What it may mean | What must be confirmed |
|---|---|---|
| C / COM | Control common or a transformer-secondary conductor in one controller circuit. | Transformer/source, phasing, shared-source permission, protection and intended device return. |
| 0 V / − | DC supply return or negative reference. | Supply topology, isolation, channel grouping and whether any other circuit may share that node. |
| SIG− / AI COM | Analog signal reference or return for a transmitter, actuator or controller input. | Voltage/current signal, active/passive loop, common-mode range, burden and controller wiring. |
| REF | Protocol-specific communication reference or another vendor-defined point. | The exact network manual; do not assume it is analog return, 0 V, shield or PE. |
| SHLD / drain | Cable screen or drain-wire termination path. | Where the screen bonds, floats or continues; frequency, cable entry, EMC plan and equipment instructions. |
| FE / chassis | Functional bonding or cabinet/chassis reference used for EMC or equipment function. | Its relationship to PE, mounting plate, shield bus and the certified equipment design. |
| PE / ground symbol | Protective conductor and fault-current path. | PE terminal function, rail/bonding design, conductor, verification and adopted safety rules. |
Do not “fix” noise by trial bonding. An arbitrary jumper between common, shield, chassis and PE can create fault-current, ground-loop, measurement or communication problems. Use the approved grounding/reference plan and update the drawings whenever a connection changes.
Segregation and service
Separate power, controls and signals deliberately
Segregation is not a cosmetic color scheme. Line conductors, motors, contactors, coils and VFD cables can have different insulation, fault, thermal, switching-noise and service requirements from analog sensors or a serial network. The applicable code, panel/equipment standard, cable system and manufacturer instructions determine the method.
Use separate wireways, rail groups, partitions, cable entries or shield/bonding paths when the released design requires them. Do not invent one universal spacing distance. A 24 V label does not prove a quiet signal, Class 2 status, SELV/PELV status or permission to share an enclosure compartment.
For the full decision method, use the guide to separating power, control and signal terminal blocks.
Start with the governing circuit rules
Check voltage, insulation, circuit classification, available energy and the permitted conductor/cable system.
Control coupling paths
Review source and victim circuits, parallel routes, crossings, VFD/motor cables, shields and bonding.
Review the assembled rail
Consider terminal, conductor, jumper, grouping, ambient, enclosure heat and product derating together.
Keep zones unmistakable
Provide readable group boundaries, terminal IDs, wire duct access, markers and documented spare locations.
BACnet MS/TP and RS-485
The terminal group must preserve the network path
BACnet MS/TP uses an RS-485 physical layer, but cable, polarity, reference, shield, topology, end-of-line and biasing rules remain dependent on the installed controllers, routers and network design. A generic RS-485 diagram is not the project specification.
Show the physical segment
Document which cable enters and leaves each panel and whether the device is inside or at an end of the segment.
Do not use a terminal row as an undocumented branch hub.Preserve polarity and reference
Keep the vendor's plus/minus or A/B convention, reference conductor and shield treatment consistent across labels and drawings.
Letter conventions can differ between manufacturers; use the named terminal.Assign responsibility
Identify the actual end devices and which controller/router supplies termination or biasing. Record switch/jumper state.
Do not add a resistor or enable every EOL switch by habit.Use the exact network data
Confirm cable, segment/device limits, baud rate, stub policy, repeater/router boundaries, grounding and commissioning method.
IP/Ethernet BACnet and other protocols need different hardware and rules.Product-specific evidence stays product-specific. A Johnson Controls guide may call for a daisy-chain with particular cable, phasing, EOL and routing practices for its controller family. Apply those details to that documented network—not as a universal rule for every BACnet device. Use ANSI/ASHRAE 135 and the complete installed-vendor documentation together.
High-consequence interfaces
Two HVAC boundaries that deserve a separate review
A clean terminal plan cannot turn a control command into electrical isolation or turn an ordinary BAS point into an approved life-safety function.
Stop state is not isolation
A BAS stop command, run-enable removal or Safe Torque Off input does not by itself disconnect the drive's main and auxiliary circuits. Keep line/motor power, control I/O, analog reference, fault relay, shield and safety-function terminals distinct. Before electrical work, isolate all supplies and follow the selected drive's discharge, waiting and voltage-verification procedure.
Attach the VFD manufacturer's power, motor, control, shield and cable-routing rules to the terminal schedule.Do not software-substitute an interlock
Fire/smoke interfaces, freeze protection, high limits, emergency functions and similar interlocks can be governed by an equipment listing, adopted code, AHJ or hardwired safety design. Preserve the approved fail-safe state, supervision and sequence. Do not bypass, jumper or software-force an interlock except under an authorized impairment or test procedure.
Ordinary color, a spare BAS input or a convenient terminal position is not approval.Eight-stage workflow
Build the BOM from the drawingTurn the sequence of operations into a buildable terminal package
Run the workflow before procurement, repeat it after approved changes and preserve the position-to-part traceability in the released documents.
Freeze the source set
Control the sequence, single-line, schematics, I/O list, network design, field-device data, panel layout and revision/effectivity.
Map sources and circuits
Identify every supply, protection point, return/reference, circuit classification, field device and energy/backfeed path.
Classify each connection
Assign power, PE, control supply, discrete, analog/sensor, communication, shield, VFD or governed-interlock function.
Choose exact terminals
Select catalog-number-specific terminal functions, conductor rules, accessories, ratings, certifications and environmental limits.
Build the physical line-up
Set group order, rail, end stops, plates, jumpers, markers, wireway, entries, tool access, heat and category-specific spares.
Review the complete paths
Check power/fault duty, PE bonding, signal reference, BACnet topology, VFD rules, interlocks and panel/end-product evidence.
Plan FAT and commissioning
Define authorized test points, expected states, instruments, network checks, temporary states, restoration and acceptance records.
Release and control change
Issue the schedule, BOM, bridge map, marker file, assembly drawing, settings and test results under one revision and as-built process.
Spare capacity is a family-by-family decision. Fitted ordinary terminals, PE points, fused positions, analog provisions, network capacity, spare I/O, empty rail length and shelf stock are different reserves. Use the guide to spare terminal blocks in a control panel rather than applying one percentage blindly.
Illustrative AHU scenario
A terminal strip becomes the field-to-controller map
This composite air-handling-unit example is a planning aid, not a verified installation or universal strip order. The exact unit, sequence, controller, VFD and jurisdiction determine the design.
Fault and supply paths
Field PE, enclosure bonding, VFD/motor power and transformer primary are identified separately from controls.
24 VAC and 24 VDC distribution
Each source, protection device, phase/polarity, return and permitted common is documented.
Status and interlocks
Fan proof, damper switch, condensate alarm and safety contacts keep NO/NC logic and normal state visible.
Commands, feedback and values
Temperature, pressure, valve and damper signals show range, reference, cable and shield treatment.
BACnet MS/TP path
Incoming/outgoing trunk, polarity, reference/shield convention and end-of-line responsibility are explicit.
Run, speed and fault
Low-level drive I/O stays distinct from line/motor circuits and follows the exact drive EMC and safety design.
The design lesson is not that every AHU needs six zones. It is that field devices, circuit classifications, controller points, power architecture, network topology and service expectations must determine the terminal-strip architecture. An ordinary feed-through block may suit one dry contact and be unsuitable for a PE conductor, fused actuator supply, shield path or approved safety function.
Commissioning readiness
IDENTITY
STATE
ACCESS
NETWORK
INSTRUMENT
CLOSEOUT
Design the strip for controlled verification
A technician should be able to identify the field point, panel-side destination, circuit family, source/reference, terminal function and approved test interface without removing unrelated conductors. Make the normal, test and restored states explicit where they matter.
Strip, position, group, field tag, cable/core and controller point agree.
NO/NC logic, normal/test state, temporary link and restoration requirement are recorded.
Markers, test sockets, fuse status, VFD display, LEDs and approved tools remain reachable.
Polarity, trunk path, EOL/bias state, address and segment record match the installed BACnet design.
Test equipment, leads and connection accessories are inspected, rated and identified.
Forces, overrides, jumpers, temporary grounds, disconnects and exceptions are independently cleared.
Where repeatable separation or measurement is required, specify the exact functional terminal, test accessory, normal/test state and restoration record. A local open point does not prove de-energization or replace the site energy-control procedure.
Protect connected electronics during high-voltage tests. Before insulation-resistance or dielectric testing, define the test boundary and isolate controllers, VFDs, actuators, sensors, surge-protection devices and communication ports unless their exact manuals explicitly permit the test and applied voltage.
Troubleshooting clues
Use the terminal strip to narrow the evidence gap
A symptom is not a diagnosis. Compare the physical strip, released records and exact equipment state before changing bonds, jumpers, controller settings or network termination.
| Observed symptom | Possible terminal/wiring cause | Controlled review direction |
|---|---|---|
| BACnet devices intermittently offline | Polarity, EOL/bias, branch topology, loose connection, unsuitable route, address conflict or inconsistent reference/shield handling. | Review the vendor's complete bus rules, trunk path, end locations, device states and address record before changing controller configuration. |
| Actuator direction or feedback is wrong | Command/feedback transposed, common/reference mismatch, wrong signal range or device configuration. | Compare terminal IDs to current actuator/controller diagrams and verify the configured input/output mode under the approved procedure. |
| Analog value is noisy or unstable | Reference or shield plan differs from the drawing, route crosses switching/VFD power, or the signal loop type is wrong. | Inspect the actual loop, cable, route, termination and device data. Do not add an arbitrary bond or filter. |
| Proof or interlock reads the wrong state | NO/NC logic, field/panel-side identity, bypass, sequence or terminal numbering is mismatched. | Trace the field device through the terminal schedule and I/O list to the approved sequence. Correct labels and records with the wiring. |
| Control supply repeatedly faults | Undocumented commoning, wrong source, overloaded distribution, incorrect protection or conductor landed on another potential. | Verify the source, circuit classification, load budget, fusing, jumper map, expected return and every connected load. |
| VFD run/fault interface behaves unexpectedly | Wrong interface type, reference mismatch, EMC path, control-state assumption or low-level wiring mixed with power. | Use the selected drive and controller manuals, safety-function file and terminal schedule before altering connections. |
HVAC terminal-strip RFQ
Send a circuit package—not a generic block count
A useful quote connects every requested terminal family to the source drawing, conductor, circuit duty, accessories, evidence and intended assembly position. Ask the supplier to identify assumptions and deviations line by line.
01 / SOURCE PACKAGEReleased documentsSequence, single-line, schematics, I/O list, network design, panel layout, device data and revision/effectivity.
02 / CIRCUIT DATAElectrical and signal identitySource, classification, voltage, current, fault duty, signal range, reference, normal state, cable and conductor.
03 / TERMINAL FAMILIESExact functions and productsFeed-through, PE, fuse, disconnect/test, distribution, shield, multi-level, pluggable and interface positions.
04 / ACCESSORIESComplete assembled systemRail, end stops, plates, partitions, jumpers, markers, test plugs, covers, wireway and category-specific spares.
05 / BAS NETWORKPhysical-layer responsibilityProtocol, controllers, cable, trunk path, polarity, reference/shield, addresses, EOL/bias, router/repeater boundaries.
06 / MARKET EVIDENCEApplication and approvalsDestination, panel/equipment standard, field-wiring use, certification records, CoA, environment and documentation language.
07 / TEST AND HANDOFFAcceptance recordsPoint-to-point record, terminal schedule, label export, network record, approved test states, restoration and as-built file.
08 / COMMERCIALSupply and change controlQuantity, panel/rail kit structure, reserve policy, approved alternatives, samples, packaging, destination and delivery schedule.
Evidence hierarchy
Read terminal specifications correctlyA terminal approval does not certify the HVAC panel
Keep each decision attached to the evidence layer that owns it. Evidence does not move automatically from a polymer, component or controller to the completed panel and building system.
Controller and field equipment
Exact wiring, signal range, load, grounding, cable, fail state, commissioning and environmental instructions.
Terminal and accessories
Function, conductor, current/voltage, certification, field-wiring condition, jumper and product-family compatibility.
End-product evaluation
Applicable HVAC equipment or industrial-control-panel standard, SCCR, wiring space, heat, bonding and assembly markings.
Adopted code and AHJ
Circuit classification, wiring method, separation, fire/smoke interface, service access and local amendments.
Network and commissioning
Sequence, topology, point list, test plan, safe-work controls, acceptance criteria, records and as-built release.
North American panel note. Where UL 508A is the applicable industrial-control-panel basis, verify the terminal's UL 1059/ANSI/UL 60947 certification and Conditions of Acceptability, conductor material/size/count, field-wiring suitability, wiring space and the complete assembly SCCR. Do not use an ordinary terminal as a power-distribution block unless its certification and application permit that use. HVAC equipment can follow a different end-product route; confirm the actual scope rather than applying UL 508A by assumption.
Frequently asked questions
HVAC terminal-block FAQ
These answers set design boundaries. Exact equipment and project documentation still control.
What terminal blocks are used in HVAC control panels?
HVAC panels can use feed-through terminals for field wiring, PE terminals for protective conductors, fuse or disconnect/test terminals for selected control circuits, distribution terminals for verified supplies, signal terminals for analog and sensor paths, dedicated communication groups for BACnet MS/TP or other networks, and shield, multi-level, pluggable or higher-current functions where the design requires them. The correct mix comes from the actual circuit map, controller, field devices, panel standard and service method.
Are HVAC control panels always 24 VAC?
No. Many HVAC control devices use 24 VAC, but a panel may also include 24 VDC, line-voltage power, 0–10 V or 2–10 V signals, 4–20 mA loops, sensor circuits, network communications and equipment-specific interfaces. A 24 V label also does not by itself establish a Class 2 circuit or a permitted wiring method. Use each source and device document.
Can BACnet MS/TP wires land on ordinary terminal blocks?
They can land on suitable documented terminals, but the terminal path must preserve the installed controller's cable, polarity, reference/shield, trunk topology, end-of-line, biasing and segment requirements. An ordinary row can hide an unintended star branch, wrong polarity or EOL error. Label the incoming and outgoing path and follow the complete network design.
Should analog HVAC signals be separated from power wiring?
Yes, the design should deliberately route analog, sensor and communication circuits relative to line, motor, contactor and VFD wiring according to the applicable code, panel/equipment standard, cable system and manufacturer instructions. The method can use wireways, rail groups, partitions, entries, shields and bonding. Do not invent one universal spacing distance.
Is controller common the same as protective earth?
Not automatically. Controller common may belong to a transformer secondary, 24 VDC negative is a supply return, an analog common is a signal reference, a communication reference follows the network rules, a shield has an EMC function, and PE is a protective conductor. Connect them only as shown in the approved equipment and panel drawings.
Do VFD HVAC panels need a special terminal layout?
They normally need a deliberate interface because line and motor circuits coexist with run, speed-reference, fault, communication, shield and safety-function wiring. Follow the selected drive's power, cable, grounding, shielding, separation, discharge and isolation instructions. A stop command, enable removal or Safe Torque Off input is not electrical isolation.
Can fire, smoke or freeze-protection points be treated like ordinary BAS I/O?
Not by default. These can be governed interlocks or life-safety/equipment-safety functions. Preserve the approved hardwired or listed architecture, fail-safe state, supervision and sequence. Follow the equipment listing, manufacturer instructions, adopted code and AHJ requirements, and use an authorized impairment or test procedure before any bypass or forced state.
How should HVAC terminal blocks be labeled?
Use strip and terminal designations tied to the schematic and point list, plus a meaningful service description, circuit family, source/reference and field/panel destination. Show group boundaries, functional accessories, normal/test state where relevant and BACnet polarity or EOL responsibility. The reader should not need wire color to infer the circuit.
How many spare terminals should an HVAC control panel include?
Use the owner or project specification first. If it does not define a number, plan credible additions by terminal family. Ordinary discrete points, analog/sensor positions, PE, fused/disconnect positions, network capacity, spare controller I/O, empty rail space and shelf-stock replacements are different reserves. Record installed spares and reserved space in the terminal schedule and BOM.
Primary technical sources
Current evidence to verify during release
Standards, regulations and manufacturer instructions can change. Confirm the edition adopted by the project, the exact equipment revision and the final component certification record.
- IEC 60947-7-1:2025 — terminal blocks and Annex D test-disconnect terminal blocks for copper conductors.
- IEC 60947-7-2 — protective-conductor terminal blocks.
- IEC 60947-7-3 — fuse terminal blocks and additional functional requirements.
- UL Connector Certification Services — terminal-block categories, UL 1059/related evidence and factory/field-wiring conditions.
- UL 508A Supplement SA resources — component requirements within the applicable industrial-control-panel route.
- BACnet International / ANSI/ASHRAE 135 — current BACnet standard and protocol resources.
- ASHRAE Guideline 13-2024 — specifying building automation systems.
- Johnson Controls EasyIO RS-485 guidance — product-specific RS-485 wiring evidence.
- Belimo TMC24A-SR data sheet — current product-specific 24 V and 2–10 V control/feedback example.
- ABB ACH580 HVAC drive documentation — selected-drive installation, control and safety source index.
- OSHA 29 CFR 1910.333 — selection and use of electrical safe-work practices.
- NFPA 90A (2027) — current publication record; use the edition adopted by the AHJ.
From I/O list to repeatable assembly
Need an HVAC terminal strip or BOM reviewed?
Send the sequence of operations, single-line, controller I/O list, field-device data, BAS network requirements, panel layout, terminal schedule, target market and quantity. SENTOP can review the component match and identify missing terminal, accessory, labeling or supply fields; final system engineering and approval remain with the responsible project parties.
_(39727884614).jpg){kind=link}
_(47952891636).jpg){kind=link}