SMA Solar Technology Sunny Tripower CORE2 STP 110-60

Commercial PV inverter

CORE2 STP 110-60 is a 110 kW three-phase PV inverter with 12 MPP trackers. Its documented communication path is SunSpec Modbus, which also connects it to SMA Data Manager. A monitoring client must preserve the existing plant-control architecture and distinguish this model’s unit ID 1 from other SMA product families.

SMA Sunny Tripower CORE2 STP 110-60
  • Modbus TCP

Commercial PV inverter

Compatibility

Compatible through Modbus TCP

The manufacturer documents a local SunSpec Modbus interface. Discover the installed model list and verify the exact inverter identity before selecting measurement offsets.

Sunny Tripower CORE2 STP 110-60, non-US, with or without AFCI. Operating manual revision 17 applies from firmware 1.1.xx.R. The retained model-specific SunSpec package is V12; its included operation list is dated 12 December 2025. Verify the installed firmware and discovered model list. CORE1, Sunny Tripower X and Hybrid X are different products.

Connect it with

For read-only measurements from the individual inverter

  • Modbus
  • Edge
  • Platforms
Commercial PV inverter
Interface
Gateway
Edge
Output
Sunny Tripower CORE2 STP 110-60Sunny Tripower CORE2 STP 110-60 Ethernet interface
Protected EthernetSegmented LAN
ZGW-20 GatewayHosts Edge locally
EpiSensor EdgeEdge Modbus TCP client
Customer platformMQTT · API · files
Modbus TCP
Protected Ethernet
Runs locally
Optional onward data
Read the inverter directly using the configured network endpoint. Preserve any existing logger or plant controller; this monitoring path does not take ownership of dispatch, protection or grid settings. The customer-platform output is optional; Edge remains the local system of record.

Models

Download
ModelsInterfaceRoute into Edge
STP 110-60 CORE2110 kW, 12 MPPTsSunSpec unit ID 1; model-specific V12 package.
CORE1 / Sunny Tripower XDifferent product platformsDo not inherit their unit IDs, register profiles or server-default settings.

Specifications

The model package describes a common identity block followed by the three-phase integer inverter model 103. It identifies supported measurements and unimplemented fields, rather than promising that every SunSpec point contains useful data. Discover the actual model list, retain the firmware with the point schedule and read scale factors alongside values. Grid support and control models in the same package are outside this read-only workflow.23

Exact product
STP 110-60, 110 kW three-phase PV inverter1
PV topology
12 MPP trackers; not CORE1 or Sunny Tripower X1
Server state
SunSpec Modbus enabled by default, TCP502; verify installed settings1
Device endpoint
Unit ID1; maximum two parallel transactions with different transaction identifiers2
Measurement model
SunSpec103, integer measurements plus signed scale factors2
Active power
W int16 and W_SF sunssf; read the actual scale factor2
Energy
WH acc32 with WH_SF; read the entire two-register counter2

Interface

Documented measurements and integration boundaries for Sunny Tripower CORE2 STP 110-60.

  • Individual inverter active power and phase currents.
  • Phase voltages, frequency and supported operating states.
  • Cumulative energy with its documented counter width and scale factor.

Assessment

Sunny Tripower CORE2 STP 110-60, non-US, with or without AFCI. Operating manual revision 17 applies from firmware 1.1.xx.R. The retained model-specific SunSpec package is V12; its included operation list is dated 12 December 2025. Verify the installed firmware and discovered model list. CORE1, Sunny Tripower X and Hybrid X are different products.

InteroperabilitySupported with conditions
The exact model documentation establishes the local interface and identity checks. The installed configuration and existing site controller must be preserved.12
AccuracySupported with conditions
The measurement representation and units are documented, but inverter telemetry does not establish revenue-meter accuracy.2
SecurityNot yet assessed
The proposed local monitoring path does not establish authenticated or encrypted measurements. Restrict access to the approved site network.1
ReliabilitySupported with conditions
The model package documents possible evening communication interruption during auxiliary-supply restart; missing data must remain distinct from measured zero.2
RuggednessNot yet assessed
Use the exact operating manual installation limits; this guide does not independently qualify the environmental performance.1
ScalabilitySupported with conditions
The exact package caps parallel transactions at two; coordinate polling with the existing Data Manager.2
LifecycleNot yet assessed
Versioned documentation is available, but a guaranteed support term or replacement lifetime is not established by the retained sources.12

Setup

Discover model 103 before reading watts

The following is synthetic data, not an observed inverter response. Model placement is discovered at commissioning.

Signature
FC03 PDU 03 9C 40 00 02 reads wire address 40000, quantity 2. Expected data 53 75 6E 53 spells SunS.
Model chain
A synthetic common header 00 01 00 42 means model 1 with 66 data registers. From wire header 40002, the next header is 40002 + 2 + 66 = 40070.
Inverter model
A header 00 67 00 32 identifies model 103 with 50 data registers. Stop if the actual model differs; do not decode float model 113 as103.
Power read
For that verified layout, FC03 PDU 03 9C 94 00 02 reads 40084 and 40085. Synthetic data 2A F8 00 01 gives 11000 × 10^1 = 110000 W.
Unavailable
Signed 16-bit 8000 is unavailable for W or its scale factor. Do not turn it into a negative reading.

Acceptance: Accept only after model, firmware, units and live reference agree. Preserve existing plant control and do not write any dispatch or persistent configuration registers.

  1. Record the exact model and controller

    Confirm STP 110-60 and record firmware, serial number, IP address and any existing SMA Data Manager. Do not remove its connection or change its control role to add monitoring.

  2. Verify the local server

    The operating manual states that SunSpec Modbus is enabled by default on port 502. Check the current installed setting instead of assuming the factory state persists. Keep the service on the authorised network without Internet port forwarding.

  3. Use the documented device endpoint

    The CORE2 SunSpec package specifies unit ID 1 and at most two parallel transactions with different transaction identifiers. This is not the ennexOS X25 unit 3 convention. Use sequential polling initially and coordinate with existing clients.

  4. Discover the model list

    Read the SunS signature and common model, then advance by each model’s reported length plus its two-register header. Verify SMA and STP 110-60 in the common identity fields. The V12 package documents three-phase integer inverter model 103; do not borrow another inverter’s absolute offsets.

  5. Read power with its scale factor

    For discovered model 103, W is at offset 14 from its ID register, and W_SF at 15. Read both signed 16-bit values together and calculate W × 10^W_SF. The package’s example map places these at register numbers 40085/40086, meaning wire addresses 40084/40085 only after that layout is verified.

  6. Qualify availability without changing controls

    Read every multi-register value completely. Treat SunSpec unavailable values as missing, not zero. Compare power and energy with the inverter and site reference. The package warns that loss of PV power in the evening can briefly restart the AC auxiliary supply and interrupt Modbus; distinguish missing data from real zero generation.

Common questions

Does the enabled-by-default interface mean it is safe to expose publicly?
No. Verify the actual setting and keep access within the approved site network. Enabling a service does not provide client authentication or make Internet port forwarding appropriate.1
Can I copy the X25 unit ID and addresses?
No. CORE2’s package specifies unit 1 and SunSpec models. The Sunny Tripower X25 guide uses a different SMA-profile endpoint. Model names and Ethernet connectors do not make those maps interchangeable.2
Can I treat the scale factor shown in the spreadsheet as constant?
Read the scale factor returned by the installed device. The package documents an example W_SF of 1, but the SunSpec measurement is the signed raw value multiplied by ten to the signed exponent.23
What happens when PV power disappears?
The model package notes a possible AC auxiliary-supply restart and short Modbus interruption in the evening. A missing response must not be substituted for a measured zero.2