n00b here with a Solax X3 gen4

[Zeppen]

Hi there!
Any idea how to make the Gen.4 of solax x3 work with this custom component?
If adding as g3 all entities end up as unknown.
Might be because of my knowledge but anyway..
Connected over ethernet to my router.
I do have a waveshare rs485 to eth but unsure how to connect it.

[infradom]

I also hava a Gen4 X3 Hybrid, and I am not able to connect to port tcp/502.
I use a wired (ethernet) pocketLan dongle.
This problem blocks me from helping with the Gen4 testing/development

Any suggestions ?

Thanks,

[Zeppen]

For what I've learned, connecting to the COM-port over rtu should work, but i dont think the modbus protocol is the same as for previous generations.
I sent an email to solax support but no success in geting the protocol, one has to be a dealer to get it..

[Zeppen]

An update on this. I spoke to my dealer/installer and there is a different protocol for gen4. One can use the COM-port and pins 4,5 to connect to it over rtu.
But im pretty much stuck here.. Dealers have to sign a Non Disclosure Agreement to get the modbus protocol for gen4..

[infradom]

In the coming days, I will start working on a version for Gen4, as I only hava en X3 Gen4 model, the X1 part will not be tested ..

[wills106]

@Zeppen Thanks to @infradom there is now Gen4 support. You should be able to use your Inverter either directly with an RS485 - USB adapter or your Ethernet - RS485 adapter.

[Zeppen]

Ill give it a go :) thnx for the update!

[stringkillersa]

I have two Solax X3 Gen 4 inverters, from 2021. I am using a TCP/IP <=> RS485 adapter and it works fine. But I would like to read from both inverters. On the RS485 side there is no problem. I have set one inverter to RS485 adress 1 and the other to address 2. But How do I set this up with the "Solax.-Modbus" integration? I know I can setup several instances of the integration, but how to select which RS485 address? Would be nice to no needing TWO converters... Anyone knows?

[infradom]

I have not read the manual yet, but the leaflet of the waveshare converter claims it is possible to map devices to different UDP port. Not sure if this is supported in TCP mode. I will examine the manual.
For UDP mode, we would have to adapt our integration to support this. Since the cost is low, I might decide to buy such a converter and try it myself first ...
But let me first read the manuals, if TCP mode port mapping would work, we do not need to change anything

[infradom]

I have read the waveshare manual, and I dont think using UDP will be the solution.
In our current integration, the modbus device unit address is fixed to 1.
Maybe we could make this a configurable parameter for the integration, need to hear the opinion of @wills106
In any case, you would need to start two instances of the integration, one for each inverter.

[wills106]

At the moment with Modbus over TCP its defaulted to 502 but you can change that on setup (config flow).

So if you can say setup Inverter 1 to map to 502 and inverter 2 to map to 503 that should work?

[stringkillersa]

@wills106 @infradom I have also studied the manual and as far as I can see, it's not possible to map ports to different modbus addresses. A configurable option to select device adress would really be lovely.

[wills106]

Sorry I am getting TCP Port and Modbus Port(Unit) mixed up...

I can add it in as an option.