Pixii PowerShaper XL 60/225

Compatibility

Third-party Modbus monitoring precedent; Edge point map to confirm

Pixii publishes a PowerShaper register map with cabinet and plant monitoring points. Use it as a best-effort starting point with the existing Gateway endpoint; compare the installed version and live readings once. A published map does not establish an Edge-tested installation or permission to change service modes or issue writes.

Exact PowerShaper XL 60 kW / 225 kWh fan-filter LFP variant only. Record the complete order identity, battery block, PixiiBox, Pixii Gateway and firmware versions. Do not infer a path for air-conditioned, indoor, cabinet-only, PowerBase or XLP variants.

Models

Specifications

The current exact-variant page specifies 60 kW continuous AC power, 225.1 kWh installed and 202.6 kWh usable LFP capacity, with 18 PixiiBoxes and 14 battery blocks in an outdoor IP55 cabinet. Published values are nominal and may be constrained by state of charge, state of health and thermal conditions.¹

AC rating

60 kW continuous, 60 kVA apparent, 400 V three-phase with neutral¹

Battery capacity

225.1 kWh installed and 202.6 kWh usable; LFP chemistry¹

Battery architecture

14 battery blocks, 16.08 kWh each; 18 PixiiBoxes; nominal DC around 48 V¹

Published interfaces

Ethernet LAN, RS-485, digital I/O, Wi-Fi access point and optional 4G¹

Published protocols

CAN bus and Modbus TCP/RTU are described as internal; MQTT is described as external¹

Third-party monitoring precedent

Eniris tested PowerShaper XL over Modbus TCP; Reduxi documents Gateway TCP port 502 and RS-485 COM4 setup for PowerShaper systems^3, 4

Enclosure

Outdoor IP55 cabinet; -20 to +45 °C operating range; fan and heater thermal management¹

Grid and generator scope

On-grid operation, off-grid support requiring a separate controller and local load-priority modification, plus published generator-backup support¹

Interface

Documented measurements and integration boundaries for PowerShaper XL 60/225.

• For a first integration trial, enable only the approved Pixii Gateway Modbus endpoint and identify one documented status and one power or energy value in the current OEM map. Compare fresh readings with the Pixii web interface before adding other points.
• For a single cabinet, the map recommends SOC at 40132 with signed scale factor 40177, battery events at 40147 and vendor status at 40191. For multiple cabinets, use the master Gateway’s plant registers: actual power at 39912 in kW uses the generator sign convention, and average battery SOC is at 39915. Keep cabinet and plant measurements distinct.
• Potential AC power, import and export energy, state of charge, state of health and available charge or discharge power must retain source, sign, unit, freshness and quality.
• Battery-block, PixiiBox, cabinet and site-meter values are different measurement boundaries and must not be merged under one generic BESS point.
• No charge, discharge, power-factor, islanding, generator or market command is approved by this guide.

Setup

1. Confirm the exact system

   Capture the full PowerShaper XL variant, order identity, serials, Pixii Gateway version, PixiiBox versions, battery-block identity, firmware and installed communications options.

2. Draw every control layer

   Separate the site meter, switchgear, Pixii Gateway, PixiiBoxes, battery blocks, fire and thermal systems, generator controller and any higher-level EMS or market platform.

3. Choose the monitored Gateway endpoint

   Check the Pixii Gateway web interface with the installer. Reduxi documents Menu → Communication → Modbus, Enabled and TCP/IP with port 502 by default; its alternative serial route uses Gateway COM4. Confirm those menus and the chosen route on this exact cabinet and firmware before connecting Edge.

4. Read one cabinet power value

   Use the public U8022_06ENG revision 2.20 map, sections 2 and 4.1. For one cabinet, read FC03 at wire address 40083, length 2: signed int16 AC power followed by signed int16 scale factor at 40084, big-endian. Do not subtract 40001; Pixii lists the addresses sent on the wire. Calculate W = raw power × 10^scale factor. Illustrative values 2500 and 1 yield 25000 W, or 25 kW. Positive means battery charging. Read the scale factor with the value because scaling is dynamic, then compare with the Gateway web display.

5. Keep control out of the first phase

   Commission identity, state, power, energy and alarm reads before considering writes. Do not use a published protocol label as authority to charge, discharge, island, synchronise or operate a generator.

6. Define any later command as a safety case

   For each approved command, document ownership, range, ramp, interlocks, timeout, local override, rejection feedback, safe fallback and measured response at the connection point.

Common questions

Does the PowerShaper XL publish Modbus?

Yes. Pixii's product table names Modbus TCP/RTU but labels it internal. Eniris reports a tested Modbus TCP integration with PowerShaper XL, and Reduxi documents Gateway setup for PowerShaper TCP/RTU. Confirm the installed Gateway settings and firmware-matched map before treating either route as an Edge endpoint.^1, 3, 4

What can an installer check before requesting a point map?

Inspect Menu → Communication → Modbus on the Pixii Gateway web interface. Reduxi documents an Enabled setting, TCP/IP mode and default port 502, with COM4 as a separate serial route. Record the actual configuration and existing controller roles; Eniris tested a PowerShaper XL over TCP. The current Pixii register map is still needed for a meaningful read-only point test.^3, 4

Can Edge command charge and discharge from this guide?

No. A control path needs the exact writable object, units, limits, ramp, interlocks, timeout, feedback and safe fallback approved by Pixii and the site owner. This selection guide publishes none.^1, 2

Is the usable capacity 225.1 kWh?

No. Pixii lists 225.1 kWh installed and 202.6 kWh usable for this exact variant. Actual performance may also be constrained by state of charge, state of health and thermal conditions.¹

Does off-grid support mean the cabinet can form an island by itself?

No. The exact product page states that single-cabinet off-grid operation requires an off-grid control system and local modification for load prioritisation. Project-specific switching, protection, earthing and generator coordination remain separate.¹