GoodWe HT 100–120 kW

Compatibility

Direct Edge integration not yet verified

The exact-family datasheet specifies SunSpec-compliant Modbus RTU. The public SunSpec discovery and model definitions provide a starting read without a firmware-specific vendor map. Installed bus ownership and returned models still determine the usable interface; no physical Edge test is claimed.

Retain the exact model, region and fitted communications accessory. Use the inverter communications bus for read-only discovery and compare identity and AC power with the local interface. Keep existing meter, logger, export-limiting and protection roles intact.

Models

Specifications

GW100K-HT is rated 100 kW with ten MPPTs; GW110K-HT and GW120K-HT are rated 110 and 120 kW with twelve MPPTs. All three are 400 V three-phase models in the retained datasheet.²

GW100K-HT

100 kW, ten MPPTs, 400 V three-phase²

GW110K-HT

110 kW, twelve MPPTs, 400 V three-phase²

GW120K-HT

120 kW, twelve MPPTs, 400 V three-phase²

PV input

1100 V maximum DC; two strings per MPPT²

Published communications

RS-485, with optional Wi-Fi or 4G; datasheet states SunSpec-compliant Modbus RTU²

Enclosure

IP66; -30 to +60 °C operating range²

Interface

Documented measurements and integration boundaries for HT 100–120 kW.

• Potential inverter identity, production and state points require an exact firmware-matched GoodWe map before publication.
• A logger or accessory value must be attributed to its actual measurement point rather than assumed to be an inverter value.
• No setpoint, export-control or protection point is approved by this guide.

Setup

1. Record the exact model

   Capture GW100K-HT, GW110K-HT or GW120K-HT, the full product code, serial number, firmware and installed communication module.

2. Map the commissioned topology

   Identify every inverter, GoodWe logger, SEC1000 or Smart Energy Controller, smart meter and RS-485 chain. Record which device is the client and which are servers.

3. Discover the published SunSpec models

   On an installer-approved inverter RS-485 bus, use the configured server address and serial settings with one client. FC03 reads two registers at wire addresses 0, 40000 or 50000 to find the SunSpec signature 53 75 6E 53. Read each model header (ID and length), advance by length + 2, and stop at ID 65535. Record the returned model IDs; do not assume model 103 or fixed positions.

4. Keep control outside the proposal

   Do not propose export limitation, active-power control, reactive-power control or grid-setting writes. Those functions belong to a separately engineered vendor control system.

5. Reassess before drawing a route

   If discovery returns model 103, let H be its header wire address. FC03 at H + 14, quantity 2, reads signed int16 W and W_SF. Power = W × 10^W_SF; 0x8000 means unavailable. Synthetic H = 40070 gives PDU 03 9C 94 00 02; bytes 30 39 FF FF mean 12345 × 10^-1 = 1234.5 W. Compare with GoodWe’s interface. Model 113 or another returned model needs its own definition.

Common questions

Does SunSpec-compliant Modbus RTU prove a direct Edge path?

The datasheet supports a useful SunSpec discovery starting point. Discover the models on the installed inverter bus and use the definition actually returned; the model-103 example below is conditional. A ready-made Edge import, logger northbound API and control writes are separate from that read-only procedure.^{1, 2, 4, 5}

Can the smart-meter port be used as the inverter-monitoring bus?

The manual assigns distinct accessory and logger roles. Do not repurpose a meter connection or assume that its measurements represent inverter production.¹

Does this guide support export or power control?

No. GoodWe documents vendor controllers for such functions, but this guide publishes no Edge control route or write operation.^1, 3