Closed Marchellos closed 2 years ago
As I already said to you in #3: The inverter closes the connection instead of answering the query after issuing a read_register (0x03) command, so having an open 502 port to connect to is clearly not enough.
The device will always close the previous connection when another connection is made to that 502 modbus port. So make sure that nothing else is trying to connect to the inverter via Modbus. This can also cause the behavior that you're seeing.
To debug, you should verify that you can succesfully retrieve a value via Modbus from the inverter.
I've only worked with Modbus directly via Python. A minimal example to debug:
from pymodbus.client.sync import ModbusTcpClient as ModbusClient
client = ModbusClient('<ip>', port=502)
client.connect()
client.read_holding_register(address=30000, count=15 ,unit=0)
If you want to use a GUI to query, you'll have to search for yourself (maybe http://www.minaandrawos.com/tcp-modbus-examiner-tool/ works for you?)
Hello Thijs,
Thank you very much for your help. I am sure there are no other connections. My inverter hangs in a barn in the countryside. The inverter can only connect to the router. Huawei recommended SPC126. By default, the modbus is turned off. But to enable the modbus I need an android phone. And I only have an iPhone cellphone. I just got this response from the helpdesk:
I escalate this issue and R&D confirmed that this month they will enable the option for Sdongle MODBUS TCP through Fusion Solar Web!
Until then we cannot do anything.
We are sorry for the inconveniences!
I wish you a nice evenin
So I will have to be patient until the update comes. In the meantime I will study modbus protocol to understand this.
Thanks again for your help and have a nice weekend..
Op vr 7 jan. 2022 om 18:17 schreef Thijs W. @.***
:
As I already said to you in #3 https://github.com/wlcrs/huawei_solar/issues/3: The inverter closes the connection instead of answering the query after issuing a read_register (0x03) command, so having an open 502 port to connect to is clearly not enough.
The device will always close the previous connection when another connection is made to that 502 modbus port. So make sure that nothing else is trying to connect to the inverter via Modbus. This can also cause the behavior that you're seeing.
To debug, you should verify that you can succesfully retrieve a value via Modbus from the inverter.
I've only worked with Modbus directly via Python. A minimal example to debug:
from pymodbus.client.sync import ModbusTcpClient as ModbusClient client = ModbusClient('
', port=502) client.connect() client.read_holding_register(address=30000, count=15 ,unit=0) If you want to use a GUI to query, you'll have to search for yourself (maybe http://www.minaandrawos.com/tcp-modbus-examiner-tool/ works for you?)
— Reply to this email directly, view it on GitHub https://github.com/wlcrs/huawei_solar/issues/13#issuecomment-1007585239, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWXEGKJKCMKVKFE7MFFVMWTUU4N3RANCNFSM5LO2UNFA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID: @.***>
It may be possible that you'll need to contact your installer to enable it via that way. My account certainly doesn't have enough access rights for that kind of changes to the installation.
System Health details
System Health
Home Assistant Community Store
GitHub API | ok -- | -- Github API Calls Remaining | 4982 Installed Version | 1.18.0 Stage | running Available Repositories | 932 Installed Repositories | 3Home Assistant Cloud
logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okHome Assistant Supervisor
host_os | Home Assistant OS 7.1 -- | -- update_channel | stable supervisor_version | supervisor-2021.12.2 docker_version | 20.10.9 disk_total | 30.8 GB disk_used | 4.8 GB healthy | true supported | true board | ova supervisor_api | ok version_api | ok installed_addons | File editor (5.3.3), Filebrowser (2.20.1), Terminal & SSH (9.2.2), MariaDB (2.4.0), phpMyAdmin (0.6.0)Lovelace
dashboards | 1 -- | -- resources | 0 views | 2 mode | storageDescribe the issue
I have followed all the steps as stated in the description..? But I can't get it to work. IP number and port number checked with https://www.advanced-port-scanner.com/
HUAWEI 17KTL M0 (SPC139) Dongle WIFI/FE (SPC123). IP 192.169.0.8
Reproduction steps
IP and port checked
Relevant debug logs