User Tools

Site Tools


venus-os:gx_solaredge

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
venus-os:gx_solaredge [2019-05-26 15:05] avanbergeijk_victronenergy.comvenus-os:gx_solaredge [2019-05-26 23:23] – [1. Introduction] mvader
Line 5: Line 5:
 You can connect your [[venus-os:start|GX Device]] with a SolarEdge PV solution, using the ModbusTCP Sunspec protocol. Sunspec is an industry standard protocol for exchanging PV Inverter yield information. You can connect your [[venus-os:start|GX Device]] with a SolarEdge PV solution, using the ModbusTCP Sunspec protocol. Sunspec is an industry standard protocol for exchanging PV Inverter yield information.
  
-  * Zero Feed-in for SolarEdge is not available when used with a Victron System+  * Zero Feed-in for SolarEdge is not available when used with a Victron System.
   * Frequency shift power control, as required in a [[ac_coupling:start|AC-Coupling system]] might work, but has not been tested.   * Frequency shift power control, as required in a [[ac_coupling:start|AC-Coupling system]] might work, but has not been tested.
  
Line 11: Line 11:
 In other sorts of systems, for example Off-grid systems, or ESS systems in areas where grid feed-in is not allowed, using a SolarEdge PV solution is not supported by Victron. In other sorts of systems, for example Off-grid systems, or ESS systems in areas where grid feed-in is not allowed, using a SolarEdge PV solution is not supported by Victron.
  
 +Note that its not possible to use the SolarEdge Wattnode meter when used in a Victron ESS System. In laymans terms, doing so will put two captains on the same ship, both trying to regulate the power flow at the utility connection, which will fail / be unstable.
 ===== 2. How to configure ===== ===== 2. How to configure =====
  
   - Ensure that the GX Device and the SolarEdge system are both on the same LAN or WiFi network.   - Ensure that the GX Device and the SolarEdge system are both on the same LAN or WiFi network.
   - Enable ModbusTCP support on your SolarEdge system. Consult the SolarEdge documentation for that.   - Enable ModbusTCP support on your SolarEdge system. Consult the SolarEdge documentation for that.
 +  - The Modbus Device id has to be set at 126. Some SE inverters might have that by default. Changing it is done in the SE inverter menu, configuration, RS485-1 menu. Although this is in the RS485 menu it also sets the ID for modbus over TCP-IP.
   - On the GX Device, navigate to Settings -> PV Inverters. Search for the Solar Edge and complete the configuration.   - On the GX Device, navigate to Settings -> PV Inverters. Search for the Solar Edge and complete the configuration.
  
 +RS485-1 menu on the Solar Edge, showing the Device ID setting:
 +{{ :venus-os:8f94cd59-9f24-469d-a067-4e65498de01f.jpeg?400 |}}
  
 Details: Details:
   - The SE2200H - SE6000H range (HD-wave) was specifically tested, though several others are reported to work too.   - The SE2200H - SE6000H range (HD-wave) was specifically tested, though several others are reported to work too.
-  - The Modbus id has to be set at 126. This is done in the SE inverter menu, configuration, RS485-1 menu. Although this is in the RS485 menu it also sets the ID for modbus over TCP-IP 
   - During testing, we found that the SolarEdge PV Inverter accepts just one concurrent TCP connection. Additional connections are rejected.   - During testing, we found that the SolarEdge PV Inverter accepts just one concurrent TCP connection. Additional connections are rejected.
venus-os/gx_solaredge.txt · Last modified: 2021-09-21 16:22 by fjlacock

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki