Alex Lisitsyn

Hi @pr200sd, I just took a look to your change and it seems the change you made ``` c pucMBTCPFrame[MB_TCP_UID] = pxInfo->ucSlaveAddr; ``` is not needed. When the `xMBMasterTCPPortSendResponse()` is...

> Thanks for the answer, yes, I saw your version V2, but everything has been changed there, and I’m not sure that I can run my project simply by replacing...

Hi @pr200sd, The stack v2 version is updated and supports the multi-instance TCP Slave and Master with its own communication options. The pre-release esp-modbus component version [2.0.0-beta.1](https://components.espressif.com/components/espressif/esp-modbus/versions/2.0.0-beta.1) can be selected...

@iamalek, @pr200sd, > with the exception of not starting master tcp if at the initial stage there is no one of the configured Slaves, so I would like to get...

@pr200sd, Thank you for the feedback. > I tried to replace the contents of the old esp-modbus-master folder in my idf with what is in the new one, the assembly...

> The fact that the calls in my code will need to be adjusted is understandable, I’m talking about the esp-idf assembly itself, I wouldn’t want to change everything globally,...

> Okay, I'll check it out. Do I understand correctly that now I should wait for you to build v2.0.0 for esp-idf 4.4? I will check possible issues for v4.4...

> I plan to in the future, but since my project is complex with support for ethernet and wi-fi with a large number of libraries added manually, I’m not sure...

I clearly understand your concern and understand if you would keep it as is. The most important process is migration to esp-idf v5 from v4.4. This update move many of...

Hi @greentd, Thank you for the issue. This happens because the port for Modbus TCP Slave is not implemented yet in v2.0.0. There are placeholders instead of real implementation. The...