What this page solves

This page is for situations where a site needs more than a simple PV inverter. The goal is to coordinate rooftop PV, a battery rack and the public grid so that daytime surplus can be stored, peaks can be shaved and critical loads stay powered during outages, all through one hybrid inverter instead of loosely coupled boxes.

Typical questions include whether to use a DC-coupled or AC-coupled architecture, how many MPPT channels are worth the extra cost, and how to define energy priority between PV, battery and grid. There is also the challenge of deciding which limits come from BMS and which from EMS or microgrid controllers, and how the hybrid inverter should react when these constraints conflict.

The content on this page focuses on decisions made inside the hybrid inverter and at its immediate interfaces: selection of hybrid power-stage topology, the sensing and protection loops required around PV, battery, DC-link and grid, and the split of responsibilities between local control and higher-level EMS or BMS logic. Pack-level cell monitoring, detailed SOH algorithms and container-scale PCS design are handled on their own pages.

• Clarify when a DC-coupled hybrid inverter is preferable to keeping a separate PV inverter and battery PCS.
• Choose MPPT and power-stage structures that match PV string layouts, battery voltage range and grid connection.
• Identify the voltage, current and temperature sensing chains and protection loops that must be closed locally inside the hybrid inverter.
• Decide which energy-management functions live in the hybrid inverter firmware and which are delegated to BMS, EMS or microgrid controllers.

For PV-only grid-tied inverters without batteries, see the dedicated string or micro inverter topic. For container-scale ESS and MW-class PCS design, refer to the PCS for ESS (bidirectional) topic.

System context & operating modes

A hybrid inverter sits between four worlds: rooftop PV strings, a battery rack with its own BMS, the public grid and local loads or backup circuits. Depending on wiring, it may see PV and battery on a common DC-link, the battery on a separate AC-coupled PCS, or both ports integrated inside one enclosure together with the grid bridge and backup output.

DC-coupled, AC-coupled and integrated hybrid wiring

In a DC-coupled arrangement, PV strings and the battery share a DC bus inside the hybrid inverter. PV boost stages and a bidirectional battery DC-DC both feed a common DC-link that supplies the grid bridge. This improves conversion efficiency when routing PV energy directly into the battery but ties PV voltage windows and battery voltage range into the same insulation levels, sensing ranges and protection thresholds.

In AC-coupled systems, an existing PV inverter remains on the AC bus and the battery connects through a separate PCS. From the hybrid inverter perspective this mainly changes how grid-side power and current are measured and controlled, and how power or power-factor setpoints are exchanged with site EMS. The DC-side structures stay simpler, but system-level energy flow depends strongly on external control.

Many modern products implement a true hybrid architecture inside one box: dedicated PV boost converters, a bidirectional battery DC-DC, a grid-tied bridge and sometimes a separate backup or critical-load output. This configuration drives the most demanding requirements for gate drivers, current sensing, DC-link monitoring and control processing, and is the primary focus for the rest of this page.

Key operating modes and inverter behaviour

Hybrid inverters are typically configured by operating mode rather than by raw power setpoints alone. Common modes include self-consumption, battery-priority operation, time-of-use arbitrage, backup or UPS-like operation and anti-feed-in where no power is exported to the public grid. Each mode changes how MPPT runs, how battery limits are applied and whether the grid bridge remains tied to the grid or switches into an islanded state.

• Self-consumption — MPPT tracks PV maximum power and the inverter uses the battery mainly to cover local loads and reduce imports. Battery charge and discharge limits are enforced from BMS and EMS constraints, while the grid bridge normally stays grid-tied.
• Battery-priority or TOU arbitrage — MPPT still follows PV maxima, but power flow is scheduled so the battery reaches specific state-of-charge targets before expensive time windows. EMS schedules overlay BMS limits, and grid import or export is shaped accordingly.
• Backup or UPS-like — during normal operation the grid bridge synchronises to the grid; when outages are detected the hybrid inverter disconnects from the grid and reconfigures to support a backup or critical-load output purely from PV and battery within BMS constraints.
• Anti-feed-in — MPPT may be power-limited so that the combination of PV and battery never exports active power to the grid. Export limits come from grid-code settings or site EMS, and the grid bridge remains connected but constrained.

Later sections detail how these wiring and mode choices drive power-stage architectures, MPPT and energy flow control, grid PLL and protection chains, and the sensing and communication links needed to enforce BMS and EMS constraints.

Power-stage architectures for hybrid inverter

Once the system context and operating modes are defined, the next step is choosing a power-stage architecture that can actually deliver those behaviours. Hybrid inverters typically fall into a few families: DC-coupled designs where PV and battery share a DC-link, hybrids with dedicated bidirectional battery DC-DC stages, and AC-coupled or split architectures where PV and battery power-trains remain largely separate and meet on an AC bus.

Each topology has a direct impact on gate-driver counts, isolation strategy, current-sensor placement and DC-link measurement requirements. A simple PV boost plus inverter chain with a direct battery connection minimises component count but limits how precisely battery charging can be controlled. Adding a bidirectional DC-DC between the battery and DC-link introduces more switches and drivers, yet unlocks independent control of PV, battery and grid power. AC-coupled approaches push some of the complexity into separate PCS units and rely more heavily on EMS coordination.

The following comparison focuses on hardware structures and their IC implications rather than on detailed control algorithms. PV-side MPPT methods are referenced only insofar as they affect sampling points and converter sizing, and cell-level battery protection is left to pack BMS and related topics. The goal is to map each representative power-stage family to the drivers, sensing front-ends and protection chains that a hybrid inverter design needs to plan for.

• PV boost plus DC-link feeding a single-phase or three-phase inverter, with battery connected directly to the DC bus.
• Hybrids with a dedicated bidirectional battery DC-DC stage between the battery rack and the DC-link.
• Architectures where PV and battery have separate DC-links or AC interfaces and are combined through an AC bus or external PCS.

MPPT & energy flow control

With a power-stage architecture chosen, the control problem becomes how to extract power from PV at or near its maximum point while respecting battery and grid constraints. Maximum power point tracking operates on PV voltage and current alone and does not directly know state-of-charge, temperature or tariff schedules. Those limits arrive through BMS and EMS interfaces and effectively cap how much of the PV maximum can be used at any time.

Hybrid inverters often support one or more MPPT channels. A single MPPT channel simplifies hardware and sampling, but assumes that all PV strings behave similarly. Multiple MPPT channels, each with its own voltage and current measurement path, cope better with mixed orientations or partial shading at the cost of more converters, drivers and ADC resources. In both cases the control chain is built around accurate, synchronised PV measurements feeding a digital controller that adjusts DC-DC duty cycles or current references.

Above the MPPT loops sits an energy-flow controller that decides how PV, battery and grid share the load. In self-consumption modes, PV power is steered towards local loads and then into the battery. In time-of-use or arbitrage modes, grid import to the battery may be enabled during low-tariff periods, and battery discharge may be prioritised during peaks. In backup operation, grid power is removed from the balance and PV plus battery together must cover critical loads without violating BMS limits.

• MPPT loops work on PV-side I – V behaviour and expose a maximum available PV power estimate.
• BMS and EMS provide hard and soft limits for battery charge and discharge power, grid import and export.
• The energy-flow controller reconciles these values into current and voltage targets for the DC-DC and inverter stages.

Detailed MPPT algorithm design can be delegated to a dedicated MPPT charge controller topic, while long-horizon scheduling, forecasting and tariff logic are typically implemented in ESS EMS edge controllers. This section highlights the measurement chains, control hooks and processing resources inside the hybrid inverter that these higher-level strategies depend on.

Grid PLL, protection & islanding

A hybrid inverter must behave like a well-behaved grid resource at its AC terminals. This requires a phase-locked loop (PLL) to track grid voltage, protection logic to detect out-of-range conditions and islanding detection so that the inverter disconnects safely when the public grid can no longer be trusted. All of these functions start from clean voltage and current measurements at the point of common coupling.

The PLL input chain begins with grid-side voltage and current sensing, passes through front-ends and anti-alias filters, and then into ADCs or sigma-delta receivers inside the control controller. From these samples the PLL derives frequency, phase angle and sequence components that support both current control and protection. Over- and under-voltage, over- and under-frequency, rate-of-change-of-frequency and phase-jump supervision are implemented on top of the same measurements, often combining fast hardware comparators with slower but more selective digital logic.

Anti-islanding adds another layer. Passive methods rely on changes in voltage, frequency, ROCOF and harmonic content once the grid becomes weak or disappears. Active schemes inject small perturbations in current or reactive power and observe whether the grid clamps these disturbances. Both approaches drive requirements for measurement bandwidth, synchronised sampling and control-loop resolution in the inverter IC set, even if detailed microgrid resync sequences are handled at a higher system level.

When a grid fault or islanding condition is detected, trip decisions must propagate reliably to the power interface. Relay, contactor or solid-state switch drivers implement the final disconnection from the grid, often with dual-channel safety paths and feedback from auxiliary contacts. Hybrid inverters frequently interface with external safety relays or STO functions so that system-level safety chains can override local control. Complex microgrid reclosing and resynchronisation strategies are better handled in a dedicated microgrid islanding and resync interface topic.

Sensing, control and communication chain

A hybrid inverter depends on a dense network of sensing, control and communication paths to coordinate PV, battery and grid ports safely. PV-side voltage and current sensing support MPPT and converter protection. DC-link voltage, current and temperature measurements provide the reference point for all power-stage control. Grid-side measurements feed PLL, power calculation and protection, while battery port sensing links the power stage back to pack-level BMS decisions.

At the centre of these chains sits a real-time control MCU or DSP, often supported by additional processing for communications, logging and user interfaces. The control core must synchronise ADC sampling with PWM outputs, run current and voltage loops, execute MPPT and grid-synchronisation algorithms, and apply protection thresholds. Surrounding ICs implement shunt, CT or transformer-based current sensing, high-side voltage measurement, insulation checks, thermal monitoring and supervision of control power.

Communication links tie the inverter into the broader energy system. BMS interfaces carry state-of-charge, temperature and current limits from the battery pack. EMS and gateway links carry power setpoints, tariff-based instructions and telemetry for SCADA or cloud platforms. Local HMI, service ports and data loggers complete the picture, ensuring that measurements and events are visible and traceable across the lifecycle of the installation.

• PV, DC-link, grid and battery sensing chains built from shunts, amplifiers, CTs, transformers and sigma-delta modulators.
• A control core with synchronised ADCs, high-resolution PWM, watchdogs and non-volatile memory for configuration and logging.
• Communication busses that connect the hybrid inverter to BMS, EMS, gateways and maintenance tools.

Detailed implementation of current-sensing front-ends and insulation monitoring can be explored in dedicated current sensing and insulation monitor topics. This section highlights how those functions sit inside the overall signal and control structure of a hybrid inverter.

IC design hooks & vendor mapping

A hybrid inverter design spans multiple functional blocks, and each block imposes specific requirements on IC categories and future device choices. This section consolidates the main design hooks from PV front-ends, DC-link and grid sensing, DC-DC and inverter stages, protection, communications and safety into a single view. The goal is to make it clear where measurement points, PWM channels, protection thresholds and communication resources must be reserved before device selection.

The table below maps each functional block to key design decisions and representative IC types. Brand columns are left intentionally open so that project-specific device choices from TI, ADI, Infineon, ST, NXP, Renesas and others can be added without restructuring the design notes. More detailed current sensing, insulation monitoring and power measurement trade-offs are handled in dedicated topics; this section focuses on keeping the hybrid inverter IC roles visible at a system level.

Application mini-stories

1) 10 kW European residential hybrid upgrade

A 10 kW single-phase residential PV system in central Europe originally used a PV-only grid-tied inverter with two MPPT inputs and no battery. Rising energy prices and lower feed-in tariffs drove a retrofit project to add a 10–15 kWh battery cabinet and replace the inverter with a hybrid unit, while remaining compliant with VDE-AR-N 4105 and related grid codes. Roof space was limited, and the homeowner wanted to accommodate future PV expansion with mixed roof orientations.

The selected hybrid architecture used a DC-coupled topology with PV boost stages and a bidirectional battery DC-DC feeding a shared DC-link. Four MPPT channels were implemented: two for existing strings and two reserved for future panels on a west-facing roof. The hybrid inverter handled grid PLL, over-/under-voltage and frequency protection, ROCOF supervision and anti-islanding functions internally, while exchanging state-of-charge limits and charge/discharge power caps with the wall-mounted battery BMS over CAN. A simple local scheduler in the hybrid executed self-consumption, peak-shaving and backup rules without needing a full external EMS.

IC selection focused on a real-time control MCU with enough PWM and ADC resources for PV boost, battery DC-DC and the inverter bridge, along with isolated gate drivers, high-side current sensors and robust grid measurement AFEs. Communication building blocks had to support at least one CAN FD interface for the battery and one Ethernet or RS-485 channel for installer tools and firmware updates.

The following bill-of-materials snapshot lists example ICs used to implement the control, sensing, drivers and communications for a design of this class. Actual device choice must still consider safety, certification, thermal design, sourcing and lifecycle constraints.

2) C&I rooftop PV and basement battery cabinet with building EMS

A mid-sized office building uses a 50 kW rooftop PV array and a 100 kWh battery cabinet located in the basement. The target operating profile is daytime self-consumption, evening peak shaving and limited overnight charging from the grid during low-tariff periods. The local distribution network operator restricts export power, so the system must enforce anti-feed-in limits while coordinating with the existing building EMS and gateway that already handle HVAC and lighting.

Two 25 kW three-phase hybrid inverters connect the PV and battery ports to the building low-voltage bus. Each hybrid executes fast current and voltage control, while a site EMS computes P/Q setpoints based on building load forecasts, tariff information and export limits. The hybrids expose status, events and measurements to the building gateway via Modbus/TCP and a secondary RS-485 link for supervisory backup. The basement battery cabinet includes environmental monitoring and fire interfaces, and the hybrids report battery-related alarms into the building alarm system.

On the IC level, the design separates time-critical power-stage control from higher-layer communications and security. A real-time MCU handles converter control and protection, while a Linux-capable SoC implements gateway functions, protocol stacks and remote connectivity. Multiple Ethernet PHYs and RS-485 transceivers support building integration, and a secure element protects TLS keys and update images. Current and voltage measurement chains are extended to cover additional feeder monitoring and cabinet environmental sensors.

The list below illustrates one possible IC combination for this type of commercial and industrial hybrid installation. It is representative rather than prescriptive and must be adapted to grid codes, company standards and component availability.

The concrete parts listed in these mini-stories illustrate how functional blocks from the design hooks section can be implemented with real ICs from multiple vendors. Alternative devices with equivalent capabilities can be substituted to match preferred suppliers, voltage classes and qualification targets.

Design checklist for a hybrid PV + battery inverter

This checklist is intended as a final design review tool before schematics and layout are frozen. It groups key decisions for topology, power stages, MPPT and operating modes, grid protection and anti-islanding, measurement and safety chains, and communications and compliance. Each item links back to the section where the underlying context and trade-offs are discussed in more detail.

Topology & power stage choices

• Have the DC-coupled, AC-coupled and mixed hybrid architectures been compared, and is the chosen connection for PV, battery, grid and loads clearly documented? (see System context & operating modes, Power-stage architectures)
• Does the number of MPPT channels and their power ratings match all planned PV strings and orientations, including realistic future expansion on available roof or ground space? (see System context, MPPT & energy flow)
• Are the battery-port voltage window, maximum charge and discharge currents and thermal limits aligned with the target pack/BMS specification and cabinet design margins? (see Power-stage architectures)
• For the chosen inverter bridge topology (single-/three-phase, two-level or multilevel) and device technology (IGBT, Si MOSFET, SiC), are gate-drive requirements and protection paths fully captured? (see Power stage, IC design hooks)

MPPT & operating modes

• Have self-consumption, battery-priority, TOU arbitrage, export-limited and backup modes been defined with clear power-priority rules and transition conditions? (see System context & modes)
• Does the MPPT layer operate based on PV I–V behaviour only, with explicit interfaces for EMS/BMS power and current limits rather than inferring battery constraints locally? (see MPPT & energy flow control, Sensing & communication chain)
• Under export-limited or no-feed-in operation, is the MPPT derating strategy stable and free from oscillations when irradiance or load changes quickly? (see Energy routing)
• When grid parameters exceed limits or the grid fails, is a complete sequence defined for switching from grid-tied operation to islanded/backup mode and back, including power ramps and reconnection criteria? (see Operating modes, Grid PLL & protection)

Grid protection & anti-islanding

• Do grid-side voltage and current measurement chains meet the accuracy, bandwidth and synchronised sampling requirements implied by the target grid code? (see PLL & protection chain, Sensing overview)
• Are over-/under-voltage, over-/under-frequency and ROCOF thresholds derived from the applicable standards for each target market rather than from generic values? (see Protection logic)
• Have passive and/or active anti-islanding methods been selected, and has their impact on AFE bandwidth, control-loop stability and flicker been evaluated? (see Anti-islanding)
• Do trip decisions propagate over a robust safety path to relays, contactors or SSRs, with auxiliary contact feedback and diagnostics to confirm actual disconnection? (see Trip & interlock, Safety-related ICs)

Measurement & safety chains

• Do PV, DC-link, grid and battery ports each have voltage and current measurement points that fully support the required control loops, protection functions and diagnostics? (see Sensing, control & communication chain)
• Are critical temperature points such as power semiconductors, DC-link capacitors, magnetics, terminals and cabinet environment instrumented and linked to derating or shutdown policies? (see Thermal & auxiliary sensing)
• Do hardware comparators and fast overcurrent/overvoltage paths provide a second layer of protection in addition to MCU- or DSP-based software limits, and has a failure mode analysis been performed? (see Protection chain, Safety supervision)
• Does the clocking and RTC scheme support consistent timestamps for event logs, fault records and sequence-of-events reporting, and is time synchronisation with EMS/SCADA defined? (see Control core & timing)
• Have auxiliary and control power rails been assigned clear start-up and shutdown sequencing, voltage supervision and reset strategies to avoid undefined driver and logic states? (see Aux/backup supplies, Supervisor & reset ICs)

Communications & compliance

• Has the BMS communication interface (CAN, CAN FD, RS-485 or Ethernet) been aligned with the chosen battery system’s protocol and timing, with sufficient margin for multi-vendor compatibility? (see BMS interface, Residential mini-story)
• Are EMS and site gateway links (Ethernet, RS-485, cellular) designed around the protocols and network topology actually used on site, including addressing, redundancy and security? (see EMS / gateway communications, C&I mini-story)
• Do protection parameters, event codes and measurement channels support the documentation and evidence required for grid-code certification and type testing? (see Grid protection, Logging & diagnostics)
• Is a secure start-up and firmware update strategy defined, including bootloader behaviour, signature verification, rollback handling and storage for multiple firmware images? (see Secure OTA & control core, Secure element & crypto)
• Are local and remote diagnostic interfaces available to support grid-code, safety and EMC testing phases, including log export, event filters and service access levels? (see HMI, service & logging, Application mini-stories)

FAQs about hybrid PV + battery inverters

These frequently asked questions address the main decision points when using a hybrid inverter instead of separate PV and battery converters. Each answer points back to the section where trade-offs, measurement chains and IC roles are explained in more depth so that a design can move from concept to implementation with fewer surprises.