What to Spec in an OEM Heat Pump Control Board in 2027

Why the Heat Pump Control Board Spec Is Changing

A heat pump control board spec built for 2023 will not cover 2027. The board now has to handle refrigerant safety, secure connectivity, and field diagnostics. You could face a respin if there’s a gap at DVT or PVT. The spec is where it costs least to close.

The board now serves three roles: safety function, network node, and service tool. Each role pulls requirements from a different place.

Equipment using A2L refrigerants is certified to UL/CSA 60335-2-40. The ETL standards update notice for Edition 4 lists an effective date of November 1, 2027 for the latest revision. Code changes follow: ASHRAE 15.2 is an approved change for the 2027 IMC and applies to residential applications. Confirm which edition and revision your certification path targets before the board spec is frozen.

1. Define A2L Mitigation I/O and Fail-Safe Behavior

When a refrigerant detection system senses gas at 25% of the lower flammability limit, it must initiate a system response. The control board spec needs to define that response in hardware terms.

Start with architecture. TI’s mitigation board paper describes cases where signals from a dedicated mitigation board go to the existing control board, which switches relays for the compressor and indoor blower. Decide whether your board hosts the logic or receives the signal.

Then specify the sensor interface, behavior on sensor fault, and which outputs are forced on or off in each state. Write response time and reset conditions as testable requirements so verification maps back to the spec. Intertek notes that the detection system must be tested as a completed assembly, and that software in the sensor or detection system falls within that testing. The boundary between detection system and control board belongs in the spec.

2. Leave Headroom for BACnet/SC

BACnet/IP and BACnet MS/TP remain the baseline. BACnet/SC adds TLS-based device authentication and encrypted communication. A network can mix SC and non-SC controllers, which allows a staged upgrade.

Adoption is early. BSRIA described BACnet/SC as being at an embryonic stage in market penetration in 2022 research, with demand possibly rising alongside cloud connectivity concerns. A launch-day SC requirement may be premature for many programs.

The practical spec is headroom: MCU and memory margin for a TLS stack, space for certificate storage, and field-updatable firmware. That keeps the option open without committing the BOM today.

3. Specify Diagnostics Against No-Trouble-Found Returns

A board that’s unable to report what it saw leaves the technician guessing, and the unit comes back with no fault found. Treat diagnostics as a service-cost requirement.

Specify how many fault codes the board retains, which sensor values it exposes, and how a technician reaches them in the field, such as a local display, BLE, or RS-485. Define whether the log persists across power cycles, since intermittent faults rarely repeat on the bench. These are best included in the spec, not the firmware backlog.

4. Spec the Heat Pump Control Board for Platform Reuse

One board architecture should cover air-source, water-source, and geothermal platforms where the product line allows it. List the interfaces explicitly: EC and PSC motor support, PWM and 0–10V control, RS-485, and electronic expansion valve drive.

Apply DFX at the spec stage. Plan certification testing early, qualify second sources for relays and contactors, and review component sourcing exposure. Validate each variant through EVT, DVT, and PVT against one requirements document. Avnan’s Maritime Geothermal case study documents 35% savings on custom control board costs.

Key Takeaways

• Treat the board as a safety function, a network node, and a service tool, and spec each role.
• Confirm the UL/CSA 60335-2-40 edition and revision before design freeze.
• Define A2L mitigation architecture, sensor fault behavior, and output states in the spec.
• Plan for BACnet/SC through hardware headroom and updatable firmware.
• Write diagnostic data requirements into the spec to reduce no-trouble-found returns.
• Apply DFX early: interface coverage, certification planning, and second sources.