Transcription

July 2016Technical Note – SunSpec Logging in SolarEdge InvertersContentsTechnical Note – SunSpec Logging in SolarEdge Inverters1Overview. 1SunSpec Supported Inverters . 2Physical Connection. 2Use Cases for MODBUS over RS485 . 3Single Inverter Connection . 3Multiple Inverter Connection . 3Use Cases for MODBUS over TCP . 4Single Inverter Connection . 4Multiple Inverter Connection . 5SolarEdge Device Configuration . 6Modbus over RS485 Configuration. 6MODBUS over TCP Support . 7MODBUS over TCP Configuration . 8Register Mapping – Monitoring Data . 8Meter Models . 11Meter Device Block . 11Meter Event Flag Values . 12MODBUS Register Mappings . 12Appendix A – Examples of a Supported MODBUS Request . 20Appendix B – Response Time Information . 21OverviewSolarEdge inverters support reading inverter-level monitoring data directly from the inverter to a local non-SolarEdgedevice, by implementing 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 theconnection 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 customdata 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 monitoringportal connection. Connection to the SolarEdge monitoring portal enables all the monitoring benefits, primarily: Proactive installer maintenance and real time troubleshooting by SolarEdge support, using with the physicalmapping available only in the SolarEdge monitoring portalModule-level monitoring

SunSpec Supported InvertersAll inverters with CPU version 3.xxxx and above are SunSpec-supported.Please upgrade to the latest available firmware.To check the inverter firmware versions, short press the LCD light button until reaching the following screen:IDCCDSPo:# #P 1 / 2U: 0u n t r#:0y#x0:#.2X#x.X#x0X## #x x / x . x x x x4 9 6X XIf needed, contact SolarEdge support to upgrade inverters with earlier versions. To upgrade the inverter firmware version:1Ensure that the inverter has been activated using the card supplied with the inverter.2Ensure that the ON/OFF switch of the inverter is OFF.3Insert the card into the communication board slot marked “CARD”.4Switch on the AC to the inverter.5Enter the inverter Setup mode: Press the internal Enter button for 5-10 seconds and release. Enter the password 12312312.6Select Maintenance SW Upgrade – SD Card.7The LCD shows: Running Script. Done!If the LCD shows: Script error: Switch the AC OFF and ON (reset), and repeat the upgrade process.If the problem persists, contact Support.Physical ConnectionThe connection is performed using an RS485 connector with a twisted pair cable. The transmission mode in SolarEdgeinverters 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 bechanged 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 Master-Slaveconnection between SolarEdge inverters. Therefore, a slave inverter cannot communicate simultaneously with a masterinverter and with a non-SolarEdge monitoring device on the same RS485 port.2

Use Cases for MODBUS over RS485This section describes RS485 options to connect the inverter to a non-SolarEdge monitoring device and to a SolarEdgemonitoring portal.Single Inverter Connection1Use the RS485 bus for connecting to a non-SolarEdge monitoring device.2Use the Ethernet connection or any of the optional wireless connection options to connect to the SolarEdge monitoring portal.Multiple Inverter ConnectionConnection to a non-SolarEdge monitoring device only (without connection to theSolarEdge monitoring portal)Use the RS485 bus for connection to a non-SolarEdge monitoring device. Every inverter in the RS485 bus should beconfigured to a different device ID (MODBUS ID).Connection to the SolarEdge monitoring portal and to a non-SolarEdge monitoringdevice1Use the RS485 bus for connection to a non-SolarEdge monitoring device. Every inverter in the RS485 bus should be configured toa different device ID (MODBUS ID).2Connect each inverter to the SolarEdge monitoring portal via Ethernet cables.3

Connection to SolarEdge monitoring portal and to a non-SolarEdge monitoring deviceusing SolarEdge Control and Communication Gateway1Use the RS485-2 bus for connection to a non-SolarEdge monitoring device. Every inverter connected to the RS485 bus should beconfigured to a different device ID (MODBUS ID).2Use Ethernet cables to connect each inverter to the SolarEdge monitoring portal.Use Cases for MODBUS over TCPThis section describes MODBUS options to connect the inverter to a non-SolarEdge monitoring device and to a SolarEdgemonitoring portal.Single Inverter Connection1Use the MODBUS for connecting to a non-SolarEdge monitoring device.2Use an Ethernet cable or any of the optional wireless connection options for connecting to the SolarEdge monitoring portal.4

Multiple Inverter ConnectionConnection to a non-SolarEdge monitoring device only (without connection to theSolarEdge monitoring portal)Use the MODBUS for connection to a non-SolarEdge monitoring device. Every inverter in the RS485 should beconfigured to a different device ID (MODBUS ID).Connection to the SolarEdge monitoring portal and to a non-SolarEdge monitoringdevice1Use the MODBUS for connection to a non-SolarEdge monitoring device. Every inverter in the RS485 bus should be configured toa different device ID (MODBUS ID).2Connect each inverter to the SolarEdge monitoring portal via Ethernet cables.5

Connection to SolarEdge monitoring portal and to a non-SolarEdge monitoring deviceusing SolarEdge Control and Communication Gateway1Use the RS485-2 bus for connection to a non-SolarEdge monitoring device. Every inverter connected to the RS485 bus should beconfigured to a different device ID (MODBUS ID).2Use Ethernet cables to connect each inverter to the SolarEdge monitoring portal.SolarEdge Device ConfigurationThis section describes how to configure the SolarEdge device (inverter or Control & Communication Gateway) as a nonSolarEdge monitoring device. To reach the main setup menu, follow the instructions in the Installation Guide of thespecific SolarEdge device.Modbus over RS485 Configuration To configure the inverters (when used without the Control and CommunicationGateway):1Under the Communication menu, set the following:ooooo2Communication Server Select any server connection, except for RS485 (if theinverter is not connected to the SolarEdge monitoring portal, select None.Communication RS485-1 ConfRS485-1 Conf Device Type Non-SE LoggerRS485-1 Conf Protocol SunSpecRS485-1 Conf Device ID and enter the MODBUS address (a unique value 1 247). Thiswill set the register C DeviceAddress.If needed, set the baud rate to a preferred value: RS485-1 Conf Baud rate and enter the rate.6

To configure the inverter (when used with the Control and Communication Gateway):1Inverters configuration: For all inverters, set the following RS485 bus settings:ooo2Communication RS485-1 Conf Device Type SolarEdgeCommunication RS485-1 Conf Protocol SlaveCommunication RS485-1 Conf Device ID [a unique value 1 247]Gateway configuration: Use RS485-1 to connect to the inverters. RS485-1 bus configuration is as follows:o Communication RS485-1 Conf Device Type SolarEdgeo Communication RS485-1 Conf Protocol Mastero Communication RS485-1 Conf Slave DetectThe Gateway should report the correct number of slaves. If it does not, verify the connections and terminations.3Use RS485-2 to connect to the non-SolarEdge monitoring device. RS485-2 bus configuration is as follows:o Communication RS485-2 Conf Device Type Non-SE Loggero Communication RS485-2 Conf Protocol SunSpecThe Control and Communication Gateway device ID is irrelevant for the communication but needs to be set toone other than the that set for the inverters.ooCommunication RS485-2 Conf Device ID [use one of the higher ID’s (e.g. 247) tomake sure it is out of scope]The default baud rate is 115200bps. If a different baud rate is required, select:Communication RS485-2 Conf Baud Rate4Make sure the device ID of the non-SolarEdge monitoring device is different from all other device IDs configured in the invertersand gateways.5Connect the gateway to the Ethernet and configure:oooooooCommunication Server LANCommunication LAN Conf Set DHCP [Select Enable for DHCP or Disable for staticIP configuration]For Static DHCP setting, configure as follows:Communication LAN Conf Set IP [Set inverters’ IP]Communication LAN Conf Set Mask [Set inverters’ subnet mask]Communication LAN Conf Set Gateway [Set inverters’ gateway]Communication LAN Conf Set DNS [Set inverters’ DNS]6If Ethernet is connected to the server, verify that the LCD panel displays S OK .7Verify that the LCD panel of all inverters is S OK .MODBUS over TCP SupportMODBUS/TCP uses the standard 100 Mbps Ethernet media in physical layers to carry the MODBUS message handlingstructure and can support a large number of devices in one network; it is easier to integrate into the Local Area Network(LAN) of a company, so it is the choice of more and more customers.Here, it is used for remote 3rd party monitoring and control. MODBUS TCP is agnostic of the server connection. It worksonly over LAN. When configured, MODBUS TCP does not initiate a connection. The server waits for a client to connect.Only one connection is supported.NOTEMODBUS TCP function– is disabled by default. When enabled, it supports TCP port 502 by default. The port number canbe reconfigured.7

MODBUS over TCP Configuration To setup MODBUS TCP:1Select Communication LAN Conf Modbus TCP (the default port is 502).2To modify the TCP port, select Modbus TCP TCP Port, set the port number and long-press Enter .NOTEThe 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:MIP oPoed:rrb1tru9:osT C P : s t a t u s 2 . 1 6 8 . 1 . 2 1 05 0 2rm e s s a g e Status:Init – Initializing server – This state only occurs after the first configuration until it reachesthe ready status. This activity lasts about 10 seconds.o Ready – The server is up and waiting for a client to connect.o Connected – The client is connected.o Failed – The server is unable to accept clients (see error message).Error messages:o Disconnected – The Ethernet cable is not connectedo Gateway Ping Failed. – A ping to the 1st router failedo No IP - Either no DHCP configuration or static IP config (no DHCP server that assigned anIP address) or need to define a static IP.o NOTEThe 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.Register Mapping – Monitoring DataThis section describes the registers mapping for the inverter monitoring data (read-only MODBUS protocol data). TheSolarEdge inverter mapping for monitoring data is based on the open protocol managed by SunSpec: SunSpec AllianceInteroperability Specification – Inverter Models v1.0. Refer to the SunSpec Alliance Interoperability Specification –Common Models (Elements) document for a detailed description of the protocol.The register mapping can be downloaded from the SunSpec Alliance web page: http://www.sunspec.org/.SolarEdge inverters support device ID (DID) 101, 102 1 and 103 register mappings.SolarEdge SunSpec implementation supports three function codes for read and write operations: - 03 (0x03) readholding registers; 06 (0x06) write single register and 16 (0x10) write multiple registers.Supported only in split-phase configurations (Japanese grid and 240V grid in North America)18

Common Model MODBUS Register MappingsThe base Register Common Block is set to 40001 (MODBUS PLC address [base 1]), or 40000 (MODBUS Protocol Address[base 0]).All parameters are defined as in the SunSpec Common block definition, except for the C Options register, which is set toNOT IMPLEMENTED.C Manufacturer is set to SolarEdge.C Model is set to the appropriate inverter model, e.g. SE5000.C Version contains the CPU software version with leading zeroes, e.g. 0002.0611.C SerialNumber contains the inverter serial number.C DeviceAddress is the device MODBUS ID (default: 1), and may be changed using the inverter menu (refer to MeterModels on page 11).AddressSizeNameTypeDescription400012C SunSpec IDuint32Value "SunS" (0x53756e53). Uniquely identifies this as aSunSpec MODBUS Map400031C SunSpec DIDuint16Value 0x0001. Uniquely identifies this as a SunSpecCommon Model Block400041C SunSpec Lengthuint1665 Length of block in 16-bit registers4000516C ManufacturerString(32)Value Registered with SunSpec "SolarEdge "4002116C ModelString(32)SolarEdge Specific Value400458C VersionString(16)SolarEdge Specific Value4005316C SerialNumberString(32)SolarEdge Unique Value400691C DeviceAddressuint16MODBUS Unit IDInverter Device Status ValuesThe following I Status xxxx values are supported:ParameterValueDescriptionI STATUS OFF1OffI STATUS SLEEPING2Sleeping (auto-shutdown) – Night modeI STATUS MPPT4Inverter is ON and producing power9

Inverter Model MODBUS Register MappingsThe following table lists the supported MODBUS register values.Unsupported values are indicated by the NOT IMPLEMENTED value.The base register of the Device Specific block is set to 40070 (MODBUS PLC address [base 1]), or 40069 (MODBUSProtocol Address [base 0]).AddressSizeNameTypeUnitsDescription400701C SunSpec DIDuint16400711C SunSpec Lengthuint16Registers50 Length of model block400721I AC Currentuint16AmpsAC Total Current value400731I AC CurrentAuint16AmpsAC Phase A Current value400741I AC CurrentBuint16AmpsAC Phase B Current value400751I AC CurrentCuint16AmpsAC Phase C Current value400761I AC Current SFint16400771I AC VoltageABuint16VoltsAC Voltage Phase AB value400781I AC VoltageBCuint16VoltsAC Voltage Phase BC value400791I AC VoltageCAuint16VoltsAC Voltage Phase CA value101 single phase102 split phase1103 three phaseAC Current scale factor400801I AC VoltageAN2, 3 4uint16VoltsAC Voltage Phase A to N value400811I AC VoltageBN3, 4uint16VoltsAC Voltage Phase B to N value400821I AC VoltageCN4uint16VoltsAC Voltage Phase C to N value400831I AC Voltage SFint16400841I AC Powerint16400851I AC Power SFint16400861I AC Frequencyuint16400871I AC Frequency SFint16400881I AC VAint16400891I AC VA SFint16400901I AC VARint16400911I AC VAR SFint16400921I AC PFint16400931I AC PF SFint16400942I AC Energy WHacc32400961I AC Energy WH SFuint16400971I DC Currentuint16400981I DC Current SFint16400991I DC Voltageuint16401001I DC Voltage SFint16401011I DC Powerint16401021I DC Power SFint16401041I Temp Sinkint16AC Voltage scale factorWattsAC Power valueAC Power scale factorHertzAC Frequency valueScale factorVAApparent PowerScale factorVARReactive PowerScale factorPower Factor 4%Scale factorWattHoursAC Lifetime Energy productionScale factorAmpsDC Current valueScale factorVoltsDC Voltage valueScale factorWattsDC Power valueScale factorDegrees CHeat Sink TemperatureSupported for single phase inverters2Supported for split-phase configurations (Japanese grid and 240V grid in North America)3Supported for three phase inverters410

AddressSizeNameTypeUnitsDescription401071I Temp SFint16Scale factor401081I Statusuint16Operating State401091I Status Vendoruint16Vendor-defined operating state and error codes.The errors displayed here are similar to the onesdisplayed on the inverter LCD screen.For error description, meaning andtroubleshooting, refer to the SolarEdge InstallationGuide. 5*401102I Event 1uint32Not implemented401122I Event 2uint32Not implemented401142I Event 1 Vendoruint32(bitmask)Vendor defined events:0x1 – Off-grid(Available from inverter CPU firmware version3.19xx and above) 4*401162I Event 2 Vendoruint32Not implemented401182I Event 3 Vendoruint32Not implemented401202I Event 4 Vendoruint323x2 in the inverter manual (LCD display) istranslated to 0x03000002 in theI Event 4 Vendor register(Available from inverter CPU firmware version3.19xx and above) 4*Meter ModelsThe SunSpec Alliance Interoperability Specification describes the data models and MODBUS register mappings for meterdevices used in Renewable Energy systems. This section defines the models for: Single Phase MeterSplit Phase MeterWye Connect MeterDelta Connect MeterMeter Device BlockThe following data elements are provided to describe meters. C SunSpec DID – A well-known value that uniquely identifies this block as a meterblock. (4) for single phase meters and (5) for three phase meter types.C SunSpec Length – The length of the meter block in registers.M AC xxxx– Meter AC values.M Exported xxxx– Meter Exported Energy valuesM Imported xxxx– Met