-
-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connection timeout #9
Comments
More data..... if I use a modbus client application I can connect to the inverter using slave id = 2 and read the registers. Does anyone know how to do this in the script? How do I call out slave id = 0? |
With the status comment I believe you pass meter number? |
Thanks Lloyd but using the option -m 1 or -m 2 doesn't work. Looking at the Modbus frame Slave ID | Function | Start PDU Register | Length | CRC I need to set slave id to 0x02. |
In the sunspec-status script if I change unit=>2 instead of unit=>1 it works. I had to change it in 4 places in the script. I get a response from the inverter as follows: Davids-MBP:sunspec-monitor-master manterd$ ./sunspec-status -v target
Power Output (AC): 962 W METER (#1): Exported Energy: 485.372 kWh |
@dpmanter you might want to ask solaredge to look at your inverter configuration then. We had a lengthy discussion to get data from the inverter and it was all fixed by an OTA update, see #4 (comment) |
I have an solaredge inverter SE11400. I got it to communicate over modbus TCP using this script. I was even able to write values to a database for a day. However, during my fiddling with the settings it lost connection to the SolarEdge portal. Solaredge did some magic on their end and it now connects to the solar portal. However, now I can't get a connection over modbus TCP using this script. When I execute the script it says connected on the inverter LCD but it returns a timeout error (show below)
sunspec-status.pl -v target
Connection timed out
at /usr/local/share/perl/5.26.1/Device/Modbus/Client.pm line 82.
Any help would be appreciated.
Thanks,
Dave
The text was updated successfully, but these errors were encountered: