Pixii PowerShaper XL 60/225

Commercial battery energy storage system

This outdoor PowerShaper XL combines 60 kW conversion with 225.1 kWh installed LFP capacity. Eniris documents a tested Modbus TCP connection to a PowerShaper XL, and Reduxi publishes Pixii Gateway TCP and RTU setup steps for PowerShaper systems. It is compatible with EpiSensor Edge over Modbus TCP at the Pixii Gateway, or Modbus RTU on its COM4 port, using Pixii's published register map.

Pixii PowerShaper XL
  • Modbus TCP
  • Modbus RTU
  • MQTT

Commercial battery energy storage system

Ask an engineer

Compatibility

Compatible with EpiSensor Edge over Modbus TCP or Modbus RTU

Pixii publishes a PowerShaper register map with cabinet and plant monitoring points, and Reduxi documents the Pixii Gateway's Modbus TCP endpoint on port 502 and an RS-485 COM4 alternative. Edge reads the Pixii Gateway as a Modbus client over either route. Read only: the map gives no permission to change service modes or issue writes.

Exact PowerShaper XL 60 kW / 225 kWh fan-filter LFP variant only. Site check: confirm Modbus is enabled in the Pixii Gateway web menu, record the Pixii Gateway and firmware versions, and compare the first readings with the Gateway display. Do not infer a path for air-conditioned, indoor, cabinet-only, PowerBase or XLP variants.

Connect it with

Route into Edge

When the Pixii Gateway has Modbus enabled in TCP/IP mode on the site network

  • Modbus
  • Edge
  • Platforms
Commercial battery energy storage system
Interface
Gateway
Edge
Output
PowerShaper XL 60/225PowerShaper XL Pixii Gateway, Ethernet LAN
Protected EthernetSegmented LAN
ZGW-20 GatewayHosts Edge locally
EpiSensor EdgeModbus client + register map
Customer platformMQTT · API · files
Modbus TCP
Protected Ethernet
Runs locally
Optional onward data
Connect Edge to the Pixii Gateway's LAN on the protected site network and poll the configured endpoint, port 502 by default. Read with FC03 at the wire addresses in the U8022_06ENG map, without subtracting 40001. Keep the Gateway's regulation mode and any existing client as they are. The customer-platform output is optional; Edge remains the local system of record.

When the site uses the Pixii Gateway’s RS-485 COM4 port instead of TCP

  • Modbus
  • Wireless
  • Edge
  • Platforms
Commercial battery energy storage system
Interface
Gateway
Edge
Output
PowerShaper XL 60/225PowerShaper XL Pixii Gateway, COM4
ZMB-31Modbus RTU to the EpiSensor wireless network
ZGW-20 GatewayHosts Edge locally
EpiSensor EdgeModbus client + register map
Customer platformMQTT · API · files
Modbus RTU · RS-485
EpiSensor wireless
Runs locally
Optional onward data
Wire the Pixii Gateway’s COM4 RS-485 port to a ZMB-31 or the Gateway’s serial interface and match the serial settings configured in the Pixii Gateway web menu. Use the same map and wire addresses as the TCP route. Keep one Modbus master on the bus. The customer-platform output is optional; Edge remains the local system of record.

Models

Download
ModelsInterfaceRoute into Edge
PowerShaper XL 60 kW / 225 kWh, fan-filter, LFPEthernet LAN, RS-485, digital I/O, Wi-Fi access point and optional 4G; published protocols include Modbus TCP/RTU and MQTTRead the commissioned Pixii Gateway over Modbus TCP, or Modbus RTU on COM4, with the U8022_06ENG map; read only.
PowerShaper XL 60 kW / 225 kWh, air-conditionedDifferent thermal package and physical specificationTreat as a separate variant and use its current product record.
PowerShaper XL Indoor, PowerBase XL and PowerShaper XLPDifferent cabinet, power, energy and deployment scopeDo not transfer the 60/225 specifications or interface assumptions.

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.1

AC rating
60 kW continuous, 60 kVA apparent, 400 V three-phase with neutral1
Battery capacity
225.1 kWh installed and 202.6 kWh usable; LFP chemistry1
Battery architecture
14 battery blocks, 16.08 kWh each; 18 PixiiBoxes; nominal DC around 48 V1
Published interfaces
Ethernet LAN, RS-485, digital I/O, Wi-Fi access point and optional 4G1
Published protocols
CAN bus and Modbus TCP/RTU are described as internal; MQTT is described as external1
Third-party monitoring precedent
Eniris tested PowerShaper XL over Modbus TCP; Reduxi documents Gateway TCP port 502 and RS-485 COM4 setup for PowerShaper systems34
Enclosure
Outdoor IP55 cabinet; -20 to +45 °C operating range; fan and heater thermal management1
Grid and generator scope
On-grid operation, off-grid support requiring a separate controller and local load-priority modification, plus published generator-backup support1

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.

Assessment

Exact PowerShaper XL 60 kW / 225 kWh fan-filter LFP product record; read-only monitoring over Modbus, with no writes or grid-compliance claim.

InteroperabilityLimited
Pixii publishes FC03 monitoring addresses, decoding and cabinet/plant scope, and the Pixii Gateway serves Modbus TCP or RTU. Validate readings against the local Gateway display; control stays separate.1345
AccuracySupported with conditions
The public U8022_06ENG revision 2.20 map documents read-only cabinet power with its sign and dynamic scale factor, plus separate plant scope. Compare a first FC03 reading with the Gateway display and feeder meter; operational readings are not a basis for settlement.5
SecuritySupported with conditions
Pixii states encrypted communications, secure remote access and current RED cybersecurity alignment; exact local interface authentication and role configuration still require commissioning.1
ReliabilityNot yet assessed
Redundancy and automated recovery are described at product-family level; the public record does not describe client recovery or data retention for an external Modbus client.1
RuggednessSupported with conditions
IP55, temperature, humidity, altitude and thermal-management limits are published for the exact outdoor variant.1
ScalabilityNot yet assessed
The system is modular, but external client count, polling capacity and multi-cabinet point ownership are not published.2
LifecycleSupported with conditions
Pixii maintains a current exact-variant page and family documentation; retain the installed firmware, battery and SLA records because specifications and warranty depend on them.12

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. Edge reads the Pixii Gateway over Modbus TCP or RTU; check the installed Gateway settings once before the first read.134
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.34
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.12
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.1
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.1