This site is now in read-only archive mode. Please move all discussion, and create a new account at the new Victron Community site.
Hello,
On the following page there is a section about "New: monitor SMA & Solar Edge PV Inverters". This section also mentions that only Solar Edge models SE2200H – SE6000H (HD-Wave) were tested.
https://www.victronenergy.com/blog/2018/02/14/venus-v2-12/
In my current Solar installation I'm using a SolarEdge SE10K inverter, this is a three phase inverter. I was curious if someone has experience combining a three phase SolarEdge inverter with for example a Victron Venus GX.
Thanks!
Emiel
I found the solution! :) Thank you Anco @AvB (Victron Energy Staff) for pointing us in the right direction.
You have to enter the following information in the RS485-1 section of the SolarEdge inverter.
Communication > RS485-1 Conf
RS485-1 Conf > Device Type > Non-SE Logger
RS485-1 Conf > Protocol > SunSpec
RS485-1 Conf > Device ID > 126
It seems not logical because these are settings for Modbus over RS485 but the Device ID is also used for the Modbus over TCP.
And with these settings the Venus GX is connecting with the SolarEdge inverter! Great feature, thank you Victron!
Amazing, thank you so much!!
Maybe Victron could add this to the instructions for Solaredge inverters?
Absolutely, done by Anco. If you have any further additions, you’re welcome to make an account and modify it further yourselves.
Hello @Guy Stewart (Victron Energy Staff),
Today I tested the following setup:
- Venus GX (with no other Victron products connected/installed)
- SolarEdge SE10K
Both connected via wired LAN on the same network (Venus GX 192.168.1.217 - SolarEdge 192.168.1.200). I enabled Modbus TCP on the SolarEdge as described in the SolarEdge documentation. After enabling the SolarEdge displays the following status
Modbus TCP: Ready
IP: 192.168.1.200
Port: 502
The meaning of this status as described in the SolarEdge documentation.
Ready – The server is up and waiting for a client to connect.
So the first part is successful.
Then I tried to find the SolarEdge inverter in the PV section of the Venus GX... but without success. Using "Find PV inverters" on the Venus GX doesn't give any result. I also manual added the ip number of the SolarEdge inverter (192.168.001.200) but without any result.
To make sure the SolarEdge inverter is reachable I installed Modbus Client software on a Windows machine. Using this software it is possible to connect to the SolarEdge inverter. After connecting the SolarEdge displays the following status:
Modbus TCP: Connected
IP: 192.168.1.200
Port: 502
Some guidance and .help is appreciated. :)
Does the Venus GX have some sort of logging to find out what is going wrong?
Greetings,
Emiel
Looking at the display of the SolarEdge inverter I get the impression the Venus GX is connecting every minute for 5 seconds. This is because of the following behaviour.
For 1 minute the following status is displayed
Modbus TCP: Ready
IP: 192.168.1.200
Port: 502
The for 4 or 5 seconds the status changes to
Modbus TCP: Connected
IP: 192.168.1.200
Port: 502
So there seems to be a Modbus connection over TCP for a short while. Does this indicate a problem with the SunSpec protocol?
Yesterday SolarEdge did an over the air update of my SE10K inverter. Now my inverter has the latest firmwares.
DSP2 Version
2.19.901
Communication Board (CPU) Version
3.2252.0
DSP1 Version
1.13.1031
Today I tried to Search for a PV inventer on my Victron Venux GX but still the same behaviour, the Venus GX does not detect the SolarEdge PV inverter. :(
Below a screenshot of an iPhone app called TCP Modbus. With this app it's possible to connect with the SolarEdge Inverter (192.168.1.200:502) and if you send a command a response is send bank and received.
@Guy Stewart (Victron Energy Staff)
Is it possible to get some help from Victron?
Thanks,
Emiel
Hello Emiel,
Can you try to set the id to 126 instead of 1 on the SE inverter. Than let the CCGX search again at inverter ip address. Curious if that helps.
Anco
i have the same problem.
devices are connected on the same LAN (ip 192.168.1.xxx)
modbus tcp is tested via simply modbus as a client on both devices and is working (laptop as a client can read all registers from 2 servers).
venus os: v2.23
SE3000hd
dsp2: 2.0.405
cpu v: 3.2155.0
dsp1: 1.0.454
since server is ok (solaredge inv), its possible that the client drops the connection (ccgx).
Should we change port on SolarEdge (502 default)?
Greetings,
Spyros
