The ethernet port no longer works from firmware version 1.50

[TexAmicoMio]

In another topic of this forum Foxess communicated that from firmware version 1.50 Modbus TCP will no longer be available (and therefore the ethernet port will be useless to most users).
Since I was using the Ethernet port, I ask the forum veterans for advice: is it better to buy an RS485-Ethernet adapter with Modbus RTU to Modbus TCP converter or do you think that the port will soon be made functional again?
If the forum is also read by Foxess technicians, I'd like to know if the reason for the unavailability is for security (which could be solved by making the port "read only") or if there are other reasons.
It is not the right way to remove a functionality from an inverter without even notifying the user.
Greetings everyone

[Can]

Ethernet ports are vulnerable by their mere availability. Having embedded controllers available on a network is always a problem, communications on ethernet uses up valuable resources on the tiny Arm Cortex MCUs that runs the entire inverter. Mess with that port and you can bring the whole lot down, speaking from experience.



Regarding hardware recommendations, go with the USR-W610 guides if you want to switch to wireless. I think it's way overpriced if you already have ethernet at the device. Personally I would stick with ethernet and move to this at half the cost and twice the inherent reliability. https://thepihut.com/products/industria ... 5-ethernet

In light of what's been happening regarding OTA updates I'm currently dogfooding a Modbus TCP to RTU gateway that I promised others using an embedded controller (£10).

[TexAmicoMio]

Hi Can,
I followed your advice and bought this device.
This adapter is not wifi but it is cheaper than the USR W610 (it costs half).

https://www.waveshare.com/wiki/RS485_TO ... )#Overview

Took a while to set it up, but finally got around to it.
Thanks for the advice.

[Will]

Appears that LAN is working again in manager firmware 1.57!

[TexAmicoMio]

Appears that LAN is working again in manager firmware 1.57!

Is the news confirmed?
There is talk of this in a Facebook group, but the news is not confirmed.
That would be good news for me.

[Dave Foster]

Appears that LAN is working again in manager firmware 1.57!

Is the news confirmed?
There is talk of this in a Facebook group, but the news is not confirmed.
That would be good news for me.

Yes confirmed, it's working again in 1.57

[mgb66]

Quick question, I have Manager version 1.45, should modbus work over LAN with this version?

[Dave Foster]

Quick question, I have Manager version 1.45, should modbus work over LAN with this version?

Yes it should.

[mgb66]

Quick question, I have Manager version 1.45, should modbus work over LAN with this version?

Yes it should.

Thanks, I'll have to do some more testing as currently I've connected my ethernet port to a WiFi adapter and it doesn't seem to want to connect. I'll try a powerlan extender instead.

[Dave Foster]

Quick question, I have Manager version 1.45, should modbus work over LAN with this version?

Yes it should.

Thanks, I'll have to do some more testing as currently I've connected my ethernet port to a WiFi adapter and it doesn't seem to want to connect. I'll try a powerlan extender instead.

You need to go into the inverter settings on the front panel and enable it’s ethernet (Settings, Communication, Ethernet), once it is switched on the manager will restart and it should update it’s IP address - you’ll find that from the front panel in About, IP Addr

[mgb66]

Yes it should.

Thanks, I'll have to do some more testing as currently I've connected my ethernet port to a WiFi adapter and it doesn't seem to want to connect. I'll try a powerlan extender instead.

You need to go into the inverter settings on the front panel and enable it’s ethernet (Settings, Communication, Ethernet), once it is switched on the manager will restart and it should update it’s IP address - you’ll find that from the front panel in About, IP Addr

All sorted - I found I wasn't pointing to the right IP address. My Wifi adapter was passing through the IP address which I didn't expect. Do seem to be getting some weird Load Power numbers though - I'll post that separately.

[Holz]

Hello everyone,
my inverter (H3-5.0) with master 1.69 slave 1.02 comm 1.59 works with modbus tcp.
But I can't read registers. For requests with FC 02, 03 or 04 I always get the answer 0x 8x 02 (with x=2,3,4). This means "The data address specified in the request is not available". I've tried a wide range of addresses.
For requests with FC 01 I get an answer for the addresses 00 to 40H. However, the values in the answer are always "0".
To me it looks like the Modbus driver is on it, but not connected to the system.
Is this a specific problem of the H3? I think I read something somewhere?

[Dave Foster]

I'm not sure which addresses you have tried, but if you follow this link and look at the file H3-LAN you will see the expected addresses and sensor names in the 30000 range for the H3

As a rule I always use the command line tool modpoll.exe to test my connections before I do anything more complicated - if you don't have it, you can get it here https://www.modbusdriver.com/modpoll.html

Then you issue the command line -

modpoll.exe -m tcp -p 502 -a 247 -t 3 -0 -1 -c 16 -r 31000 [your_ip xxx.xxx.xxx.xxx]

That should read 16 int16 holding registers starting at 31000 as long as you have the correct IP address and a valid connection.

Other things to check, are you connected direct via LAN or RS485
- if it is LAN, check the IP is allocated as you expect on the inverter panel by clicking on About, IP Addr - if it is showing as all zero's then on the inverter you need to go into Setting, Communication, Ethernet and set the IP address (DHCP etc..)

- if it is RS485 check you are connected to the correct pins on the meter connector, the H3 should be connected to pins 1 & 2 (on the H1 inverter it is pins 3 & 4)

[Holz]

Hello Dave,
thank you for the hints. I tried it right away with the tool modpoll: modpoll.exe -m tcp -p 502 -a 247 -t 3 -0 -1 -c 16 -r 31000 xxx.xxx.xxx.xxx
Answer:
Protocol configuration: MODBUS/TCP, FC4
Slave configuration...: address = 247, start reference = 31000 (PDU), count = 16
Communication.........: xxx.xxx.xxx.xxx, port 502, t/o 1.00 s, poll rate 1000 ms
Data type.............: 16-bit register, input register table
-- Polling slave...
Illegal Data Address exception response!

However, I poll with FC01: modpoll.exe -m tcp -p 502 -a 247 -t 0 -0 -1 -c 16 -r 00 xxx.xxx.xxx.xxx
Answer:
Protocol configuration: MODBUS/TCP, FC1
Slave configuration...: address = 247, start reference = 0 (PDU), count = 16
Communication.........: xxx.xxx.xxx.xxx, port 502, t/o 1.00 s, poll rate 1000 ms
Data type.............: discrete output (coil)

-- Polling slave...
[0]: 0
[1]: 0
[2]: 0
[3]: 0
[4]: 0
[5]: 0
[6]: 0
[7]: 0
[8]: 0
[9]: 0
[10]: 0
[11]: 0
[12]: 0
[13]: 0
[14]: 0
[15]: 0

With "xxx.xxx.xxx.xxx" the IP address, of course.
(By the way: What is the reason for address 247 in the command? I tried also address 1 with the same results.)
The results are essentially the same as I received with the ModbusTCP tool and as I described in my previous post.

What I found in topic "Manager version 1.56" is answer from FoxESS service:

service@fox-ess.com

Hello *****,
Modbus TCP is not available after the firmware 1.50.
But customers can still use Modbus RTU with RS485 :-+ . *There is no effect that customer can use their own private monitoring appliance.


That means, I need a modbus RS485-TCP converter!?

Thanks again Dave

Peter

[Dave Foster]

(By the way: What is the reason for address 247 in the command? I tried also address 1 with the same results.)
The results are essentially the same as I received with the ModbusTCP tool and as I described in my previous post.

What I found in topic "Manager version 1.56" is answer from FoxESS service:

service@fox-ess.com

Hello *****,
Modbus TCP is not available after the firmware 1.50.
But customers can still use Modbus RTU with RS485 :-+ . *There is no effect that customer can use their own private monitoring appliance.


That means, I need a modbus RS485-TCP converter!?

Thanks again Dave

Peter

The address 247 is the slave port, because it is TCP>RTU modbus you can have multiple slaves hanging on the bus, the default slave for the hybrids is 247 (you can see / change it in the inverter settings)

Yes agree, it does sound like you need a modbus RS485-TCP converter.

The direct LAN was removed from the H1 series but it came back on the very latest version of firmware and sounds as if it hasn't gone back onto the H3, however that said the RS485 interface has many more sensors and I would recommend using that interface.

There are many modbus TCP converters but I can highly recommend these for their speed and simplicity.

https://www.waveshare.com/wiki/RS485_TO_POE_ETH_(B)

and the usr-tcp232-410s (but don't get the W610S very slow!)

[asyrop]

Hi Peter and Dave
Thank you both for the very illuminating reports because the last few posts are of great interest as they reflect just where where I am at progressing my HA implementation. I get exactly the same response from my inverter as Peter to the modpoll.exe checks with an FC4 request and with FC1. In fact I can get 64 points reported (all as 0) for FC1 but nothing for FC4, the same error as Peter records.

The odd thing is that my inverter is an H1-5.0-E and I believe has the latest firmware - 1.57, so I don't know why people some can get modbus responses under TCP and others can't.

Just to be 100% clear, and given the vagueries of Fox systems. My app reports the versions as:
Master 1.54
Slave 1.02
Manager 1.57

whilst the Inverter itself in the About section has the same versions as:
Master 1.54
Slave 1.02
Comms 1.57

I assume the titles are slightly arbitary but the variation clearly allows for confusion as to what might affect what. Does anyone know if the Master and Slave versions might affect the Modbus reporting ?

Any further insights much appreciated,
Alan

[Dave Foster]

It's strange that you are getting all zero's in response that often means it isn't getting a response, rather than it is reading zero.

Your Manager version of 1.57 on the H1 does have LAN enabled, but can you double check the IP address that you are sending to is correct and the inverter is in agreement - if you go to the inverter panel, look at About, IP Addr - is that the same address you are sending to.

[asyrop]

Yes, Dave. Thanks for the feedback - it encourages me that I am on the right track.
I have double checked the IP address - it also pings correctly across the network and I also did a separate check of asking modpoll.exe to poll an IP address either side of the inverter's and got an "unreachable" response, which made me conclude that modpoll sees it as "live".
Finally, I manually disconnected the ethernet cable and retried modpoll which correctly identified the host as unreachable, whilst reconnecting the cable brought back the string of zero's with the FC1 query as before.
Any other thoughts ?
All the advice in this forum is truly valuable for those of us simply trying to use the various undocumented features; please keep up the good work.
Alan

[Dave Foster]

If a register is not reachable the response to a larger modpoll can sometimes zero's, sometimes an error (depending on which version of modpoll) but as the initial response was address unreachable for an FC4 across that range it would be worth checking registers we know should reply in case some in the range are unreachable.

Can you try polling a smaller range of 6 registers with FC4, I know these are reachable and should respond -

modpoll.exe -m tcp -p 502 -a 247 -t 3 -0 -1 -c 6 -r 31000 xxx.xxx.xxx.xxx[your IP]

This should return -

31000 = PV1 Voltage
31001 = PV1 Current
31001 = PV1 Power
31001 = PV2 Voltage
31001 = PV2 Current
31001 = PV2 Power

[asyrop]

Thank you very much, Dave, for your persistence on this one.

I have tried your query string and then with a count of 1, both of which elicited the same response. So you can see the version of modpoll and all the rest, here is the precise exchange:

….\modpoll\win>modpoll.exe -m tcp -p 502 -a 247 -t 3 -0 -1 -c 1 -r 31000 192.168.1.120
modpoll 3.10 - FieldTalk(tm) Modbus(R) Master Simulator
Copyright (c) 2002-2021 proconX Pty Ltd
Visit https://www.modbusdriver.com for Modbus libraries and tools.

Protocol configuration: MODBUS/TCP, FC4
Slave configuration...: address = 247, start reference = 31000 (PDU), count = 1
Communication.........: 192.168.1.120, port 502, t/o 1.00 s, poll rate 1000 ms
Data type.............: 16-bit register, input register table

-- Polling slave...
Illegal Data Address exception response!

As always, any further suggestions are most welcome,
Alan

[Holz]

Hello David and Alan,
Anyway, I ordered the recommended RS485 to TCP converter from Waveshare.
Then we'll see. Dave, maybe I need your help with the configuration then!?

[APfox]

Hello David and Alan,
Anyway, I ordered the recommended RS485 to TCP converter from Waveshare.
Then we'll see. Dave, maybe I need your help with the configuration then!?

I'm not not Dave, but it's rather well explained here: https://github.com/nathanmarlor/foxess_ ... TH-%28B%29

[Dave Foster]

Thank you very much, Dave, for your persistence on this one.

I have tried your query string and then with a count of 1, both of which elicited the same response. So you can see the version of modpoll and all the rest, here is the precise exchange:

….\modpoll\win>modpoll.exe -m tcp -p 502 -a 247 -t 3 -0 -1 -c 1 -r 31000 192.168.1.120
modpoll 3.10 - FieldTalk(tm) Modbus(R) Master Simulator
Copyright (c) 2002-2021 proconX Pty Ltd
Visit https://www.modbusdriver.com for Modbus libraries and tools.

Protocol configuration: MODBUS/TCP, FC4
Slave configuration...: address = 247, start reference = 31000 (PDU), count = 1
Communication.........: 192.168.1.120, port 502, t/o 1.00 s, poll rate 1000 ms
Data type.............: 16-bit register, input register table

-- Polling slave...
Illegal Data Address exception response!

As always, any further suggestions are most welcome,
Alan

Alan,
Just a thought from a comment on another thread, but the H3 registers are holding registers (not inputs), try repeating the modpoll with -t 4 (and not -t 3)

[asyrop]

You are a hero, Dave - yes, your suggestion works as evidenced below ! I have learnt a great deal and reassured that I am on the right track.
Hopefully, others can benefit too.

Many many thanks; I am one big step forward to a decent HA monitoring system.
Alan.

D:\DDownloads\modpoll\win>modpoll.exe -m tcp -p 502 -a 247 -t 4 -0 -1 -c 16 -r 31000 192.168.1.120
modpoll 3.10 - FieldTalk(tm) Modbus(R) Master Simulator
Copyright (c) 2002-2021 proconX Pty Ltd
Visit https://www.modbusdriver.com for Modbus libraries and tools.

Protocol configuration: MODBUS/TCP, FC3
Slave configuration...: address = 247, start reference = 31000 (PDU), count = 16
Communication.........: 192.168.1.120, port 502, t/o 1.00 s, poll rate 1000 ms
Data type.............: 16-bit register, output (holding) register table

-- Polling slave...
[31000]: 2275
[31001]: 39
[31002]: 903
[31003]: 2139
[31004]: 99
[31005]: 2126
[31006]: 2480
[31007]: 9
[31008]: 166
[31009]: 5010
[31010]: 0
[31011]: 0
[31012]: 0
[31013]: 0
[31014]: -13
[31015]: 0

[Dave Foster]

You are a hero, Dave - yes, your suggestion works as evidenced below ! I have learnt a great deal and reassured that I am on the right track.
Hopefully, others can benefit too.

Many many thanks; I am one big step forward to a decent HA monitoring system.
Alan.

You are very welcome