SolaX Power X3-ULTRA

Compatibility

Public monitoring map; Edge commissioning remains site-specific

SolaX documents Modbus RTU on the remote COM1 pair and Modbus TCP through supported Pocket modules. The retained OEM-authored V3.29 protocol explicitly names X3-ULTRA and supplies addresses and decoding. This guide has not established a tested Edge import.

Seven high-voltage X3-ULT variants in the V2.3 datasheet. Use the published map as a best-effort starting point and compare initial reads with the local display. Keep remote RS-485 separate from SolaX accessory wiring; TCP requires a compatible monitoring module. GLV and Belgian 25KW variants remain outside this electrical assessment.

Models

Specifications

SolaX lists seven 15–30 kW high-voltage variants in its V2.3 datasheet. The 15KP and 20KP units have a third MPPT; the corresponding non-P 15K and 20K have two. The 19.9K is identified for Italy.^1, 2

Documented ratings

15, 19.9, 20, 25 and 30 kW; seven exact model codes²

PV input

Two or three MPPTs by variant; 1,000 V maximum PV input²

Battery circuit

120–800 V lithium battery range; two battery ports, 60 A maximum combined charge or discharge current²

Backup output

Three-phase EPS output requires a battery and commissioned backup arrangement^1, 2

Monitoring interfaces

Modbus RTU on remote COM1 RS-485; Modbus TCP through a supported Pocket module, TCP 502^4, 5, 6

Enclosure

IP66; -35 to +60 °C, with derating above 45 °C²

Interface

Documented measurements and integration boundaries for X3-ULTRA.

• PV, battery, inverter and meter values have different physical boundaries. Record which device originates each value before connecting a monitoring client.
• COM1 is an RS-485 connector, not Ethernet: remote pins 1/2 and 7/8 serve third-party communication; pins 3/4/5/6 are a separate bus for SolaX accessories.
• Start with FC04 grid voltage at 0x006A and frequency at 0x006D. Expand to battery state of charge, PV power and signed meter power after comparing readings with the local display.

Setup

1. Identify the exact inverter

   Record the X3-ULT model code, country variant, serial number, installed firmware and any communication accessory. Use the P suffix and country designation to select the correct electrical limits.

2. Map the plant boundaries

   Draw PV strings, both battery ports, BMS connections, grid and EPS circuits, meters, parallel links and any DataHub, EV charger or Adapter Box G2. Mark the origin of each proposed reading.

3. Wire the third-party RS-485 pair

   Use COM1 remote pins 1/2 or 7/8 according to the manual pinout. SolaX explicitly permits third-party devices on this bus; keep accessory pins 3/4/5/6 separate. Re-crimp the RJ45 connector for the required pins rather than using a full Ethernet cable blindly. Follow the installed manual cable limit, retain one polling master per bus and record existing connections.

4. Choose RTU or Pocket TCP

   Protocol V3.29 gives RTU defaults of address 1, 19200 baud, 8 data bits, no parity and 1 stop bit; match the actual inverter settings. TCP requires a SolaX monitoring module, not the COM1 connector: the protocol specifies port 502 and default unit 1. The OEM Pocket compatibility table lists X3-ULTRA ARM V4.04 and supported dongle versions. Enable the module locally, record its assigned IP and use the same protected LAN. Space requests by at least one second.

5. Read voltage and frequency

   Use the retained OEM-authored V3.29 map, whose revision history ends in September 2023, as a best-effort starting point. FC04 input register 0x006A (decimal 106), quantity 1, gives R-phase grid voltage as U16 × 0.1 V. Request PDU: 04 00 6A 00 01. Synthetic response data 08 FC decodes to 230 V. Register 0x006D (109), quantity 1, gives frequency as U16 × 0.01 Hz: PDU 04 00 6D 00 01 and data 13 88 give 50 Hz. These are hexadecimal wire addresses; do not subtract one. Compare both with the local display before adding more readings.

6. Add battery, PV and site power

   FC04 0x001C (28), quantity 1, is battery 1 state of charge, U16 in 1%; data 00 4B gives 75%. PV1/PV2 power at 0x000A/0x000B are U16 in W. Meter/CT power at 0x0046 (70), quantity 2, is signed 32-bit W with the low word first: PDU 04 00 46 00 02. Read each word as big-endian, then combine low + high × 65536 and apply two’s-complement sign. Data 30 39 00 00 gives +12345 W; CF C7 FF FF gives -12345 W. Positive indicates export and negative import. Check against the site meter, not inverter production alone. Inverter AC energy is separate: daily 0x0050 U16 × 0.1 kWh and total 0x0052/0x0053 U32, low word first, × 0.1 kWh.

7. Keep dispatch with its commissioned owner

   Use these examples for monitoring. Battery dispatch, export limits, EPS transfer and grid settings remain with the commissioned control system. This guide supplies no operational write commands.

Common questions

Can a VPP issue power commands using the advertised API or OpenADR support?

The datasheet includes VPP protocol and API names with a note that some features are coming soon. Availability, roles, permissions and the contracted control path must be confirmed for the installed country variant and firmware. This guide publishes no command path.²

Does the DataHub replace the site meter or prove Edge control?

No. DataHub is SolaX's controller for its documented multi-inverter system. Point-of-connection metering and protection remain separately commissioned, and DataHub control does not establish an Edge write interface.¹

What changes between X3-ULT-20K and X3-ULT-20KP?

The datasheet gives the 20K two MPPTs and the 20KP three, with two strings per MPPT. Check the full model code instead of selecting an array layout from the 20 kW rating alone.²