Sunspec Implementation Technical Note
Sunspec Implementation Technical Note
3, February 2021 1
Version 2.1 (September 2020): New multiple MPPT inverter extension model for Synergy inverters
Contents
Technical Note – SunSpec Logging in SolarEdge Inverters ........................................................................................................................................................ 1
Overview .................................................................................................................................................................................................................................................................. 2
SolarEdge Device Configuration – Using the Inverter/Commercial Gateway Display (LCD) ............................................................................................. 12
Overview
SolarEdge inverters support transmission of inverter-level monitoring data directly from the inverter to a local non-SolarEdge device
using the SunSpec open protocol for interoperability between devices in renewable energy systems. This option can be used alongside
the connection to the SolarEdge monitoring server. This document describes the connection method and the protocol and
configurations needed to implement this feature.
Direct connection to a monitoring device is useful when a network connection is unavailable, when extensive custom data processing is
required, or when authorities require direct access to monitoring data.
In many cases, it is possible – and recommended – to employ the direct connection alongside a SolarEdge monitoring platform
connection. Connection to the monitoring platform enables all the monitoring benefits, primarily:
Proactive installer maintenance and real time troubleshooting by SolarEdge support, using with the physical mapping available
only in the monitoring platform
Module-level monitoring
Communication Technologies
SolarEdge uses an open, industry-standard communications stack in order to provide efficient messaging between SolarEdge and third-
party devices and applications.
SunSpec
SunSpec is an application-layer communications protocol designed to achieve interoperability between Distributed Energy Resource
(DER) components and smart grid applications.
Modbus
Modbus is a serial communications protocol typically used to connect data collection terminals to a centralized processing unit.
SolarEdge products use Modbus to perform SunSpec messaging over two types of physical/link-layer channels:
Modbus RTU: Remote Terminal Unit (RTU) Modbus over a serial RS485 connection
SolarEdge systems support a single Modbus Leader only – either single Modbus RTU or single Modbus TCP.
Using SetApp
SolarEdge inverters with the LCD that have Firmware version 3.xxxx and above only are SunSpec-supported.
To check the inverter firmware versions (for inverters with the LCD):
1. Short press the LCD light button until reaching the following screen:
I D : # # # # # # # # # #
D S P 1 / 2 : x . x x x x / x . x x x x
C P U : 0 0 0 2 . 0 4 9 6
C o u n t r y : X X X X X
Physical Connection
The connection is performed using an RS485 connector with a twisted pair cable. The transmission mode in SolarEdge inverters is set to
RTU (binary).
The COM port default properties are: 115200 bps, 8 data bits, no parity, 1 stop bit, no flow control. Baud rate can be changed between
9600bps to 115200bps (supported from CPU version 2.0549).
The RS485 bus can be configured to support connection either to a non-SolarEdge monitoring device or Leader-Follower connection
between SolarEdge inverters. Therefore, a Follower inverter cannot communicate simultaneously with a Leader inverter and with a non-
SolarEdge monitoring device on the same RS485 bus.
All SolarEdge inverters with SetApp configuration have two built-in RS485 ports. An inverter can act as Leader on both ports
simultaneously.
A Commercial Gateway with LCD can act as Leader on one of the built-in RS485 ports and on the RS485 Plug-in.
Use the Ethernet connection or any of the optional wireless connection options to connect to the SolarEdge monitoring platform.
Connection to a non-SolarEdge monitoring device only (without connection to the monitoring platform)
Option 1 (direct connection) – Use RS485-1 to connect Followers to the Leader and the Leader to a non-SolarEdge monitoring device.
Every inverter in the RS485 bus should be configured to a different device ID (MODBUS ID).
Option 2 – Use RS485-1 to connect Follower inverters to the Leader; use either RS485-2 or RS485-E to connect the Leader to a non-
SolarEdge monitoring device. Every inverter in the RS485 bus should be configured to a different device ID (MODBUS ID).
Use the RS485 bus for connection to a non-SolarEdge monitoring device. Every inverter in the RS485 bus should be configured to a
different device ID (MODBUS ID).
Option 1 (direct connection) – Connect each inverter to the router via Ethernet cables.
Connection to the monitoring platform and to a non-SolarEdge monitoring device using a Commercial
Gateway
Use the RS485-2 bus for connection to a non-SolarEdge monitoring device. Every inverter connected to the RS485 bus should be
configured to a different device ID (MODBUS ID).
If required, use the RS485-E bus for connecting a second chain of inverters.
Connection to a non-SolarEdge monitoring device only (without connection to the SolarEdge monitoring
platform)
Use Ethernet for connection to a non-SolarEdge monitoring device. Every inverter in the RS485 should be configured to a different
device ID (MODBUS ID).
Use Ethernet for connection to a non-SolarEdge monitoring device. Every inverter in the RS485 bus should be configured to a different
device ID (MODBUS ID).
Option 1 (direct connection) – Connect each inverter to the Ethernet router via Ethernet cables.
Option 2 – Connect the Leader only to the Ethernet router via Ethernet cables.
Connect a second chain of the inverters to the Leader inverter using RS485-2/RS485-E.
Connection to the SolarEdge monitoring platform and to a non-SolarEdge monitoring device using a
Commercial Gateway
Use Ethernet for connection to a non-SolarEdge monitoring device. Every inverter connected to the RS485 bus should be configured to
a different device ID (MODBUS ID).
If required, use the RS485-E bus for connecting a second chain of inverters.
To reach the main setup menu, access SetApp and tap Commissioning Site Communication:
To configure the inverters and gateway (when used with the Commercial Gateway):
1. Inverter configuration: For all inverters, verify the following RS485 bus settings under the Site Communication menu:
3. Use RS485-2 to connect the Commercial Gateway to the non-SolarEdge monitoring device. Configure the RS485-2 bus settings as
follows, using the device display:
4. Make sure the device ID of the non-SolarEdge monitoring device is different from all other device IDs configured in the inverters
and gateways.
5. Connect the Commercial Gateway to router via the Ethernet interface and configure the following settings using the device display:
Status
Inverter
SN 07318000C
S_OK
P_OK: 138 of 141
Server Connected
Optimizers Connected
(LAN)
Status Switch
Production ON
1.0 20 C OK
Commissioning
Here, it is used for remote 3rd party monitoring and control. MODBUS TCP is agnostic of the server connection. It works only over LAN.
When configured, MODBUS TCP does not initiate a connection - the server waits for a client to connect. Only one connection is
supported.
NOTE
The MODBUS TCP function is disabled by default. When enabled, it supports TCP port 1502 by default. Port
number can be reconfigured.
1. Select Site Communication Modbus TCP Enable. A new Port menu is added to the screen (the default port is 1502)
2. To modify the TCP port, select Port, set the port number and tap Done.
3. NOTE
The default device ID of the inverter connected to the Ethernet is 1.
NOTE
The TCP server idle time is 2 minutes. In order to leave the connection open, the request should be made
within 2 minutes. The connection can remain open without any MODBUS requests.
• Communication Server Select any server connection, except for RS485 (if the inverter is not connected to the
SolarEdge monitoring platform, select None.
• Communication RS485-1 Conf
• RS485-1 Conf Device Type Non-SE Logger
• RS485-1 Conf Protocol SunSpec
• RS485-1 Conf Device ID and enter the MODBUS address (a unique value 1…247). This will set the register
C_DeviceAddress.
2. If needed, set the baud rate to a preferred value: RS485-1 Conf Baud rate and enter the rate.
1. Inverters configuration: For all inverters, set the following RS485 bus settings:
3. Use RS485-2 to connect to the non-SolarEdge monitoring device. RS485-2 bus configuration is as follows:
4. Make sure the device ID of the non-SolarEdge monitoring device is different from all other device IDs configured in the inverters
and gateways.
5. Connect the Commercial Gateway to router via the Ethernet interface and configure the following settings:
Here, it is used for remote 3rd party monitoring and control. MODBUS TCP is agnostic of the server connection. It works only over LAN.
When configured, MODBUS TCP does not initiate a connection. The server waits for a client to connect. Only one connection is
supported.
NOTE
The MODBUS TCP function is disabled by default. When enabled, it supports TCP port 502 by default. The port number
can be reconfigured.
• Select Communication LAN Conf Modbus TCP (the default port is 502).
• To modify the TCP port, select Modbus TCP TCP Port, set the port number and long-press Enter.
NOTE
The default device ID of the inverter connected to the Ethernet is 1.
When the MODBUS TCP feature is enabled, the following status screen is shown:
M o d b u s T C P : < s t a t u s >
I P : 1 9 2 . 1 6 8 . 1 . 2 1 0
P o r t : 5 0 2
< e r r o r m e s s a g e >
Status:
• Init – Initializing server – This state only occurs after the first configuration until it reaches the ready status. This activity
lasts about 10sec.
• Ready – The server is up and waiting for a client to connect.
• Connected – The client is connected.
• Failed – The server is unable to accept clients (see error message).
Error messages:
• Disconnected – The Ethernet cable is not connected
• Gateway Ping Failed. – A ping to the 1st router failed
• No IP - Either no DHCP configuration or static IP configuration (no DHCP server that assigned an IP address) or need to
define a static IP.
NOTE
The TCP server idle time is 2 minutes. In order to leave the connection open, the request should be made
within 2 minutes. The connection can remain open without any MODBUS requests.
The register mapping can be downloaded from the SunSpec Alliance web page: http://www.sunspec.org/.
SolarEdge three phase inverters with Synergy technology also support SunSpec module ID 160 register mappings.
All parameters are defined as in the SunSpec Common block definition, except for the C_Options register, which is set to
NOT_IMPLEMENTED.
C_Version contains the CPU software version with leading zeroes, e.g. 0002.0611.
Address
Size Name Type Description
(base 0) (base 1)
Value = "SunS" (0x53756e53). Uniquely identifies this as a
40000 40001 2 C_SunSpec_ID uint32
SunSpec MODBUS Map
Value = 0x0001. Uniquely identifies this as a SunSpec
40002 40003 1 C_SunSpec_DID uint16
Common Model Block
40003 40004 1 C_SunSpec_Length uint16 65 = Length of block in 16-bit registers
40004 40005 16 C_Manufacturer String(32) Value Registered with SunSpec = "SolarEdge "
40020 40021 16 C_Model String(32) SolarEdge Specific Value
40044 40045 8 C_Version String(16) SolarEdge Specific Value
40052 40053 16 C_SerialNumber String(32) SolarEdge Unique Value
40068 40069 1 C_DeviceAddress uint16 MODBUS Unit ID
1 Supported only in split-phase configurations (Japanese grid and 240V grid in North America)
The base register of the Device Specific block is set to 40070 (MODBUS PLC address [base 1]), or 40069 (MODBUS Protocol Address
[base 0]).
acc32 is a uint32 accumulator that should always increase. Its value is in the range of 0...4294967295.
Scale Factors. As an alternative to floating point format, values are represented by Integer values with a signed scale factor
applied. The scale factor explicitly shifts the decimal point to left (negative value) or to the right (positive value).
Address
Size Name Type Units Description
(base 0) (base 1)
40069 40070 1 C_SunSpec_DID uint16 101 = single phase
102 = split phase
103 = three phase
40070 40071 1 C_SunSpec_Length uint16 Registers 50 = Length of model block
40071 40072 1 I_AC_Current uint16 Amps AC Total Current value
40072 40073 1 I_AC_CurrentA uint16 Amps AC Phase A Current value
40073 40074 1 I_AC_CurrentB uint16 Amps AC Phase B Current value
40074 40075 1 I_AC_CurrentC uint16 Amps AC Phase C Current value
40075 40076 1 I_AC_Current_SF int16 AC Current scale factor
40076 40077 1 I_AC_VoltageAB uint16 Volts AC Voltage Phase AB value
40077 40078 1 I_AC_VoltageBC uint16 Volts AC Voltage Phase BC value
40078 40079 1 I_AC_VoltageCA uint16 Volts AC Voltage Phase CA value
Address
Size Name Type Units Description
(base 0) (base 1)
40079 40080 1 I_AC_VoltageAN 1 uint16 Volts AC Voltage Phase A to N value
40080 40081 1 I_AC_VoltageBN 1 uint16 Volts AC Voltage Phase B to N value
40081 40082 1 I_AC_VoltageCN 1 uint16 Volts AC Voltage Phase C to N value
40082 40083 1 I_AC_Voltage_SF int16 AC Voltage scale factor
40083 40084 1 I_AC_Power int16 Watts AC Power value
40084 40085 1 I_AC_Power_SF int16 AC Power scale factor
40085 40086 1 I_AC_Frequency uint16 Hertz AC Frequency value
40086 40087 1 I_AC_Frequency_SF int16 Scale factor
40087 40088 1 I_AC_VA int16 VA Apparent Power
40088 40089 1 I_AC_VA_SF int16 Scale factor
40089 40090 1 I_AC_VAR int16 VAR Reactive Power
40090 40091 1 I_AC_VAR_SF int16 Scale factor
40091 40092 1 I_AC_PF int16 % Power Factor
40092 40093 1 I_AC_PF_SF int16 Scale factor
40093 40094 2 I_AC_Energy_WH acc32 WattHours AC Lifetime Energy production
40095 40096 1 I_AC_Energy_WH_SF uint16 Scale factor
40096 40097 1 I_DC_Current uint16 Amps DC Current value
40097 40098 1 I_DC_Current_SF int16 Scale factor
40098 40099 1 I_DC_Voltage uint16 Volts DC Voltage value
40099 40100 1 I_DC_Voltage_SF int16 Scale factor
40100 40101 1 I_DC_Power int16 Watts DC Power value
40101 40102 1 I_DC_Power_SF int16 Scale factor
40103 40104 1 I_Temp_Sink int16 Degrees C Heat Sink Temperature
40106 40107 1 I_Temp_SF int16 Scale factor
40107 40108 1 I_Status uint16 Operating State
40108 40109 1 I_Status_Vendor uint16 Vendor-defined operating state and error
codes. For error description, meaning and
troubleshooting, refer to the SolarEdge
Installation Guide.
1 Supported only in split-phase configurations (Japanese grid and 240V grid in North America).
# Name Description
0 GROUND_FAULT Ground Fault
1 INPUT_OVER_VOLTAGE Input Over Voltage
3 DC_DISCONNECT DC Disconnect
5 CABINET_OPEN Cabinet Open
6 MANUAL_SHUTDOWN Manual Shutdown
7 OVER_TEMP Over Temperature
12 BLOWN_FUSE Blown Fuse
13 UNDER_TEMP Under Temperature
14 MEMORY_LOSS Memory Loss
15 ARC_DETECTION Arc Detection
19 RESERVED Reserved
20 TEST_FAILED Test Failed
21 INPUT_UNDER_VOLTAGE Under Voltage
22 INPUT_OVER_CURRENT Over Current
Meter Models
The SunSpec Alliance Interoperability Specification describes the data models and MODBUS register mappings for meter devices used
in Renewable Energy systems. This section defines the models for:
Single Phase Meter
Split Phase Meter
WYE (4-wire) Meter
Delta (3-wire)Meter
Energy Value
The energy value is represented by a 32-bit unsigned integer accumulator with a scale factor. Values for import and export are provided.
Unsupported or invalid accumulators may return 0x00000000. Power signs and Energy quadrants are per IEEE 1459-2000.
This map supports single, split, wye, and delta meter connections in a single map as proper subsets. The connection type is
distinguished by the C_SunSpec_DID. Registers that are not applicable to a meter class return the unsupported value. (e.g. Single Phase
meters will support only summary and phase A values).
For 2-unit three phase inverters with Synergy technology, add 50 to the default addresses.
For 3-unit three phase inverters with Synergy technology, add 70 to the default addresses.
NOTE
Only enabled meters are readable, i.e. if meter 1 and 3 are enabled, they are readable as 1st meter and 2nd meter (and the
3rd meter isn't readable). The meter type can be read from the Common block Options field (the same strings that we use
in the menus).
Meter 1
Meter 2
Voltage
Line to Neutral Voltage
40369 40370 1 M_AC_Voltage_L N int16 Volts Line to Neutral AC Voltage (average of active
phases)
40370 40371 1 M_AC_Voltage_A N int16 Volts Phase A to Neutral AC Voltage
Frequency
40378 40379 1 M_AC_Freq int16 Herts AC Frequency
40379 40380 1 M_AC_Freq_SF int16 SF AC Frequency Scale Factor
Power
Real Power
40380 40381 1 M_AC_Power int16 Watts Total Real Power (sum of active phases)
40381 40382 1 M_AC_Power_A int16 Watts Phase A AC Real Power
40382 40383 1 M_AC_Power_B int16 Watts Phase B AC Real Power
40383 40384 1 M_AC_Power_C int16 Watts Phase C AC Real Power
40384 40385 1 M_AC_Power_SF int16 SF AC Real Power Scale Factor
Apparent Power
40385 40386 1 M_AC_VA int16 Volt- Amps Total AC Apparent Power (sum of active phases)
40386 40387 1 M_AC_VA_A int16 Volt- Amps Phase A AC Apparent Power
40387 40388 1 M_AC_VA_B int16 Volt- Amps Phase B AC Apparent Power
40388 40389 1 M_AC_VA_C int16 Volt- Amps Phase C AC Apparent Power
40389 40390 1 M_AC_VA_SF int16 SF AC Apparent Power Scale Factor
Reactive Power
40390 40391 1 M_AC_VAR int16 VAR Total AC Reactive Power(sum of active phases)
40391 40392 1 M_AC_VAR_A int16 VAR Phase A AC Reactive Power
40392 40393 1 M_AC_VAR_B int16 VAR Phase B AC Reactive Power
40393 40394 1 M_AC_VAR_C int16 VAR Phase C AC Reactive Power
40394 40395 1 M_AC_VAR_SF int16 SF AC Reactive Power Scale Factor
Power Factor
40395 40396 1 M_AC_PF int16 % Average Power Factor (average of active phases)
40396 40397 1 M_AC_PF_A int16 % Phase A Power Factor
40397 40398 1 M_AC_PF_B int16 % Phase B Power Factor
40398 40399 1 M_AC_PF_C int16 % Phase C Power Factor
40399 40400 1 M_AC_PF_SF int16 SF AC Power Factor Scale Factor
Accumulated Energy
Real Energy
40400 40401 2 M_Exported uint32 Watt- hours Total Exported Real Energy
40402 40403 2 M_Exported_A uint32 Watt- hours Phase A Exported Real Energy
40404 40405 2 M_Exported_B uint32 Watt- hours Phase B Exported Real Energy
40406 40407 2 M_Exported_C uint32 Watt- hours Phase C Exported Real Energy
40408 40409 2 M_Imported uint32 Watt- hours Total Imported Real Energy
40410 40411 2 M_Imported_A uint32 Watt- hours Phase A Imported Real Energy
40412 40413 2 M_Imported_B uint32 Watt- hours Phase B Imported Real Energy
40414 40415 2 M_Imported_C uint32 Watt- hours Phase C Imported Real Energy
40416 40417 1 M_Energy_W_SF int16 SF Real Energy Scale Factor
Apparent Energy
40417 40418 2 M_Exported_VA uint32 VA-hours Total Exported Apparent Energy
40419 40420 2 M_Exported_VA_ A uint32 VA-hours Phase A Exported Apparent Energy
40421 40422 2 M_Exported_VA_ B uint32 VA-hours Phase B Exported Apparent Energy
40423 40424 2 M_Exported_VA_ C uint32 VA-hours Phase C Exported Apparent Energy
40425 40426 2 M_Imported_VA uint32 VA-hours Total Imported Apparent Energy
40427 40428 2 M_Imported_VA_ A uint32 VA-hours Phase A Imported Apparent Energy
40429 40430 2 M_Imported_VA_ B uint32 VA-hours Phase B Imported Apparent Energy
40431 40432 2 M_Imported_VA_ C uint32 VA-hours Phase C Imported Apparent Energy
40433 40434 1 M_Energy_VA_S F int16 SF Apparent Energy Scale Factor
Reactive Energy
40434 40435 2 M_Import_VARh_ Q1 uint32 VAR-hours Quadrant 1: Total Imported Reactive Energy
40436 40437 2 M_Import_VARh_ Q1A uint32 VAR-hours Phase A - Quadrant 1: Imported Reactive Energy
40438 40439 2 M_Import_VARh_ Q1B uint32 VAR-hours Phase B- Quadrant 1: Imported Reactive Energy
40440 40441 2 M_Import_VARh_ Q1C uint32 VAR-hours Phase C- Quadrant 1: Imported Reactive Energy
40442 40443 2 M_Import_VARh_ Q2 uint32 VAR-hours Quadrant 2: Total Imported Reactive Energy
40444 40445 2 M_Import_VARh_ Q2A uint32 VAR-hours Phase A - Quadrant 2: Imported Reactive Energy
40446 40447 2 M_Import_VARh_ Q2B uint32 VAR-hours Phase B- Quadrant 2: Imported Reactive Energy
40448 40449 2 M_Import_VARh_ Q2C uint32 VAR-hours Phase C- Quadrant 2: Imported Reactive Energy
40450 40451 2 M_Export_VARh_ Q3 uint32 VAR-hours Quadrant 3: Total Exported Reactive Energy
40452 40453 2 M_Export_VARh_ Q3A uint32 VAR-hours Phase A - Quadrant 3: Exported Reactive Energy
40454 40455 2 M_Export_VARh_ Q3B uint32 VAR-hours Phase B- Quadrant 3: Exported Reactive Energy
40456 40457 2 M_Export_VARh_ Q3C uint32 VAR-hours Phase C- Quadrant 3: Exported Reactive Energy
40458 40459 2 M_Export_VARh_ Q4 uint32 VAR-hours Quadrant 4: Total Exported Reactive Energy
40460 40461 2 M_Export_VARh_ Q4A uint32 VAR-hours Phase A - Quadrant 4: Exported Reactive Energy
40462 40463 2 M_Export_VARh_ Q4B uint32 VAR-hours Phase B- Quadrant 4: Exported Reactive Energy
40464 40465 2 M_Export_VARh_ Q4C uint32 VAR-hours Phase C- Quadrant 4: Exported Reactive Energy
40466 40467 1 M_Energy_VAR_ SF int16 SF Reactive Energy Scale Factor
Events
40467 40468 2 M_Events uint32 Flags See M_EVENT_ flags. 0 = nts.
Meter 3
Frequency
40553 40554 1 M_AC_Freq int16 Herts AC Frequency
40554 40555 1 M_AC_Freq_SF int16 SF AC Frequency Scale Factor
Power
Real Power
40555 40556 1 M_AC_Power int16 Watts Total Real Power (sum of active phases)
40556 40557 1 M_AC_Power_A int16 Watts Phase A AC Real Power
40557 40558 1 M_AC_Power_B int16 Watts Phase B AC Real Power
40558 40559 1 M_AC_Power_C int16 Watts Phase C AC Real Power
40559 40560 1 M_AC_Power_SF int16 SF AC Real Power Scale Factor
Apparent Power
40560 40561 1 M_AC_VA int16 Volt- Amps Total AC Apparent Power (sum of active phases)
40561 40562 1 M_AC_VA_A int16 Volt- Amps Phase A AC Apparent Power
40562 40563 1 M_AC_VA_B int16 Volt- Amps Phase B AC Apparent Power
40563 40564 1 M_AC_VA_C int16 Volt- Amps Phase C AC Apparent Power
40564 40565 1 M_AC_VA_SF int16 SF AC Apparent Power Scale Factor
Reactive Power
40565 40566 1 M_AC_VAR int16 VAR Total AC Reactive Power (sum of active phases)
40566 40567 1 M_AC_VAR_A int16 VAR Phase A AC Reactive Power
40567 40568 1 M_AC_VAR_B int16 VAR Phase B AC Reactive Power
40568 40569 1 M_AC_VAR_C int16 VAR Phase C AC Reactive Power
40569 40570 1 M_AC_VAR_SF int16 SF AC Reactive Power Scale Factor
Power Factor
40570 40571 1 M_AC_PF int16 % Average Power Factor (average of active phases)
40571 40572 1 M_AC_PF_A int16 % Phase A Power Factor
40572 40573 1 M_AC_PF_B int16 % Phase B Power Factor
40573 40574 1 M_AC_PF_C int16 % Phase C Power Factor
40574 40575 1 M_AC_PF_SF int16 SF AC Power Factor Scale Factor
Accumulated Energy
Real Energy
40575 40576 2 M_Exported uint32 Watt- hours Total Exported Real Energy
40577 40578 2 M_Exported_A uint32 Watt- hours Phase A Exported Real Energy
40579 40580 2 M_Exported_B uint32 Watt- hours Phase B Exported Real Energy
40581 40582 2 M_Exported_C uint32 Watt- hours Phase C Exported Real Energy
40583 40584 2 M_Imported uint32 Watt- hours Total Imported Real Energy
40585 40586 2 M_Imported_A uint32 Watt- hours Phase A Imported Real Energy
40587 40588 2 M_Imported_B uint32 Watt- hours Phase B Imported Real Energy
40589 40590 2 M_Imported_C uint32 Watt- hours Phase C Imported Real Energy
40591 40592 1 M_Energy_W_SF int16 SF Real Energy Scale Factor
Apparent Energy
40592 40593 2 M_Exported_VA uint32 VA-hours Total Exported Apparent Energy
40594 40595 2 M_Exported_VA_ A uint32 VA-hours Phase A Exported Apparent Energy
40596 40597 2 M_Exported_VA_ B uint32 VA-hours Phase B Exported Apparent Energy
40598 40599 2 M_Exported_VA_ C uint32 VA-hours Phase C Exported Apparent Energy
40600 40601 2 M_Imported_VA uint32 VA-hours Total Imported Apparent Energy
40602 40603 2 M_Imported_VA_ A uint32 VA-hours Phase A Imported Apparent Energy
40604 40605 2 M_Imported_VA_ B uint32 VA-hours Phase B Imported Apparent Energy
40606 40607 2 M_Imported_VA_ C uint32 VA-hours Phase C Imported Apparent Energy
40608 40609 1 M_Energy_VA_S F int16 SF Apparent Energy Scale Factor
Reactive Energy
40610 40611 2 M_Import_VARh_ Q1 uint32 VAR-hours Quadrant 1: Total Imported Reactive Energy
40612 40613 2 M_Import_VARh_ Q1A uint32 VAR-hours Phase A - Quadrant 1: Imported Reactive Energy
40614 40615 2 M_Import_VARh_ Q1B uint32 VAR-hours Phase B- Quadrant 1: Imported Reactive Energy
40616 40617 2 M_Import_VARh_ Q1C uint32 VAR-hours Phase C- Quadrant 1: Imported Reactive Energy
40618 40619 2 M_Import_VARh_ Q2 uint32 VAR-hours Quadrant 2: Total Imported Reactive Energy
40620 40621 2 M_Import_VARh_ Q2A uint32 VAR-hours Phase A - Quadrant 2: Imported Reactive Energy
40622 40623 2 M_Import_VARh_ Q2B uint32 VAR-hours Phase B- Quadrant 2: Imported Reactive Energy
40624 40625 2 M_Import_VARh_ Q2C uint32 VAR-hours Phase C- Quadrant 2: Imported Reactive Energy
40626 40627 2 M_Export_VARh_ Q3 uint32 VAR-hours Quadrant 3: Total Exported Reactive Energy
40628 40629 2 M_Export_VARh_ Q3A uint32 VAR-hours Phase A - Quadrant 3: Exported Reactive Energy
40630 40631 2 M_Export_VARh_ Q3B uint32 VAR-hours Phase B- Quadrant 3: Exported Reactive Energy
40632 40633 2 M_Export_VARh_ Q3C uint32 VAR-hours Phase C- Quadrant 3: Exported Reactive Energy
40634 40635 2 M_Export_VARh_ Q4 uint32 VAR-hours Quadrant 4: Total Exported Reactive Energy
40636 40637 2 M_Export_VARh_ Q4A uint32 VAR-hours Phase A - Quadrant 4: Exported Reactive Energy
40638 40639 2 M_Export_VARh_ Q4B uint32 VAR-hours Phase B- Quadrant 4: Exported Reactive Energy
40640 40641 2 M_Export_VARh_ Q4C uint32 VAR-hours Phase C- Quadrant 4: Exported Reactive Energy
40642 40643 1 M_Energy_VAR_ SF int16 SF Reactive Energy Scale Factor
Events
40643 40644 2 M_Events uint32 Flags See M_EVENT_ flags. 0 = nts.
MODBUS request with explicit register addressing - supported by all communication board CPU versions. For example:
• Tx: 01 03 9C 40 00 7A EB AD – Read 122 registers starting at address 40001.
• Rx: 01 03 F4 53 75 … [Registers data] … FF FF 12 1B
MODBUS request without explicit addressing – supported by communication board CPU version 2.478 and above. For example:
• Tx: 01 03 00 00 00 7A C4 29 – Read 122 registers starting at offset 0.
• Rx: 01 03 F4 53 75 6E 53 … [Registers data] … FF FF AE DB
Inverters with CPU firmware versions support a response time of 1 second, regardless of the number of inverters:
When connected through a Commercial Gateway, the response delay through the Commercial Gateway can be as much as
N*100[ms]+60[ms], where:
100 ms is the maximum slot time per Follower in the SolarEdge bus
N*100 [ms] - SolarEdge bus delay of N Followers, assuming each inverter transmits one SolarEdge telemetry and one full
MODBUS response per grant slot.
256 * 10000/Baud rate [ms] - at least one full MODBUS packet over the MODBUS link, and limited to a minimum of 60ms
(hardcoded).
For example, the timeout delay of a bus of 10 Followers and a 115200 bps MODBUS link is: 1000 [ms] + 60 [ms].
Part of the slot is also consumed by the Follower inverters transmitting SolarEdge telemetries at the same time.
Consider the following if trying to reduce delays when a Commercial Gateway is installed:
Waiting for a response is part of the MODBUS definition, and this is limiting the bandwidth.
Multiple retries may result in multiple replies, as the inverters receive all the MODBUS commands, but the SolarEdge bus
topology delays the response. In this case, implementing a no-response-expected MODBUS command may balance between
performance and reliability, as:
• Inverters can be controlled with no delay except for the fixed 60ms per inverter (since a response is not expected).
• An ACK from the inverter is not expected and the measured power from the meter is used as the feedback loop.
• The responses from all the inverters are received in an Nx100ms timeframe, which can be used for a sanity check.
• If you try 0 [ms] timeout, expect the timeout to occur intentionally and disregard it.
If you use MODBUS-over-SolarEdge with MODBUS replies, consider lower rates.
Since 32-bit values span two registers, they must be written in a single transaction of Write Multiple Registers (Function code 10) and
not two consecutive Write Single Register (Function code 06) transactions.
Read Request
Write Request
Read Request
Write Request
https://www.solaredge.com/service/support
The error indicated on the product SetApp mobile application LCD screen or on the monitoring platform or by the LEDs, if
there is such an indication.
System configuration information, including the type and number of modules connected and the number and length of strings.