trouble getting the ew11 working but direct lan cable does get data.

[LeighAS]

using the ew11a 0 board (or clone there of)
i've wired it up 3 to B, 4 to A. on the rs485 socket.
Gone through the ew11 setup and have that on my lan and set the serial and the comms settings
ive installed the HACs integration.

ive tried slave id as 247 and 001 and 246 (none worked) matching inverter to ha setting each time.
I also used the lan cable and tried a direct connection and that works fine and gives me data on all the HA entities
The error i get on connection is

Error reading registers. Type: RegisterType.INPUT; start: 10016; count: 3; slave: 247 from tcp://192.168.0.70:502: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response

interestingly the inverter is recognised over the modbus as an AC1-5.0-E AUX which i assume it is getting from the modbus.

I also have a usb to rs485 device i could try but that would require relocating my PI3 to the garage with the inverter and i'm reluctant to do this.

Thanks for any help in solving this both myself and a chap called batteryman on YouTube are having the same error using the ew11 with this integration his is a H3 though where as I clearly only have the AC1.

[FozzieUK]

You need to make sure that you have disabled the ethernet port - it won't run on LAN and RS485 at the same time - disable your network DHCP in the inverter settings and you will usually see the inverter manager restart, after which you should be able to resume on the RS485 and set your slave ID back to the default 247.

If that doesn't work there are the usual suggestions for no connection, you have connected the correct pins so check all the settings in the Elfin, your baud rate looks good but double check you have the Netp set to TCP server and the protocol to modbus.

[LeighAS]

Tried disabling the dhcp server on the Ethernet settings on ac1.

Didn't see an improvement but it good to know they interfere with one another.

I've included the above to show the fw versions that I see when the direct lan connection is working with the foxess hacs integration.

Chat got seems to think versions earlier than 1.08 of the fw didn't support rs485 but it didn't specify whether it was meaning manager master or slave.

[FozzieUK]

Ahh right, they are very old firmware versions -it’s not so much RS485 wasn’t supported as the register map has changed a lot over the versions.

I’m assuming you have a Gen 2 inverter the latest firmware versions are Master 1.27 and Manager 1.44 - can you contact your installer and ask for an update or email Fox service with your inverter serial number and ask them to update the inverter firmware.

[LeighAS]

Ah shit. Fair enough. Will fire off and email to fox tomorrow

[LeighAS]

got a bit a to and fro from Fox today on the email and have established i need the fox datalogger to get fw ota'd. luckily V2Hchris has agreed to lend me his for a while to get this part done.

[williamjeccles]

worth noting that you can't swap dataloggers between sites if the site only has one datalogger attached. If you have 2 datalogger on a site you can remove one with ease. Just wanted to point this out before you pull your hair out. So if you have a fox site with zero dataloggers don't attach V2Hchris to it or you'll be stuck having it bound to your site.

[LeighAS]

Thanks Will, I won't be using the data logger again now unless I have to update the fw for register changes. Was going to send it back to Chris or are you saying they will have bound that to my inverter now. I haven't ever played with fox cloud, nor do I intend to, everything is to be kept local. Hopefully thus hasn't opened a can of worms.

[williamjeccles]

Thanks Will, I won't be using the data logger again now unless I have to update the fw for register changes. Was going to send it back to Chris or are you saying they will have bound that to my inverter now. I haven't ever played with fox cloud, nor do I intend to, everything is to be kept local. Hopefully thus hasn't opened a can of worms.

If you add the datalogger to the site, you then won't be able to remove it and Chris won't be able to adopt it again. If Chris hasn't removed his datalogger, you won't be able to use it anyway. Hope that makes sense.