Modbus TCP Implementation
Re: Modbus TCP Implementation
Hello,
okay thank you very much for your reply, very appreciated.
I am looking forward for the new version then.
best regards
DK
okay thank you very much for your reply, very appreciated.
I am looking forward for the new version then.
best regards
DK
Re: Modbus TCP Implementation
@ESP_alisitsyn,
Any update on when this feature can make it into the MASTER tree?
I'm implementing a TCP modbus slave with a very sparse register map and it would save mamory to be able to have several areas of each type
Rgds
/Anders
Any update on when this feature can make it into the MASTER tree?
I'm implementing a TCP modbus slave with a very sparse register map and it would save mamory to be able to have several areas of each type
Rgds
/Anders
-
- Posts: 211
- Joined: Fri Feb 01, 2019 4:02 pm
- Contact:
Re: Modbus TCP Implementation
@jas39_,
Unfortunately I can not provide the concrete date for this feature. It is in my todo list and will be implemented after higher priority tasks.
Unfortunately I can not provide the concrete date for this feature. It is in my todo list and will be implemented after higher priority tasks.
-
- Posts: 1
- Joined: Tue Oct 27, 2020 10:19 am
Re: Modbus TCP Implementation
Could you tell me little bit more about your application? Is this Modbus master TCP or slave?
Re: Modbus TCP Implementation
in my case it is a Modbus TCP slave (server).
The problem is, that the prepared library from esp-idf does not allow several areas of holding register areas.
The problem is, that the prepared library from esp-idf does not allow several areas of holding register areas.
Re: Modbus TCP Implementation
My case is a modbus router rtu<->tcp (Rs485 master <-> Wifi Slave) with a sparse memorymap on the RS485 side and on top of that "double buffering" of tcp-write data which doubles the amount of registers needed.
Sofar I've solved the TCP slave part with a linked list of memory areas and wrapped it in my app so that I can reuse the same struct as for the master_serial. Keeping the external interface.
I now realize I have to provide both read and write pointers to mbc_tcp_slave extending the mb_register_area_descriptor_t , but I think I can still keep the external interface, well we see
Sofar I've solved the TCP slave part with a linked list of memory areas and wrapped it in my app so that I can reuse the same struct as for the master_serial. Keeping the external interface.
I now realize I have to provide both read and write pointers to mbc_tcp_slave extending the mb_register_area_descriptor_t , but I think I can still keep the external interface, well we see
Re: Modbus TCP Implementation
Okay interesting.
Did you find any possibility or work around to make several address areas of holding registers for a Modbus TCP slave?
HREG area 1: 0-100
HREG area 2: 1000-1100
HREG area 3: 2000-2100
...
Did you find any possibility or work around to make several address areas of holding registers for a Modbus TCP slave?
HREG area 1: 0-100
HREG area 2: 1000-1100
HREG area 3: 2000-2100
...
Re: Modbus TCP Implementation
I had to extend the current implementation of mbc_serial_slave.c and mbc_tcp_slave.c by using a linked list of memory areas. It's a hack for now.
-
- Posts: 211
- Joined: Fri Feb 01, 2019 4:02 pm
- Contact:
Re: Modbus TCP Implementation
@jas39_, @dkaufmann,
If you are still interested in this feature (definition of several register areas for modbus slave), the feature will be completed soon but I need to perform testing. Before the official merge I would like you to test the patch for official code. Could you test it?
Thanks.
If you are still interested in this feature (definition of several register areas for modbus slave), the feature will be completed soon but I need to perform testing. Before the official merge I would like you to test the patch for official code. Could you test it?
Thanks.
Re: Modbus TCP Implementation
Hello, yes I am still interested and I would also test it. It might takes some time because at the moment my project works with esp-idf 4.0 so I need to change some things first to be compatible with esp-idf v4.3.
thanks for your update and let me know how I can test it.
thanks for your update and let me know how I can test it.
Who is online
Users browsing this forum: No registered users and 56 guests