Accessing TCP Slave at 1RPS often results in no response (IDFGH-15564)

[dsyx]

Checklist

• Checked the issue tracker for similar issues to ensure this is not a duplicate
• Read the documentation to confirm the issue is not addressed there and your configuration is set correctly
• Tested with the latest version to ensure the issue hasn't been fixed

How often does this bug occurs?

always

Expected behavior

Since the request was correct, the client should receive a response every time.

Actual behavior (suspected bug)

The client sometimes receives the correct response and sometimes does not receive the response.

Error logs or terminal output

Client tool log:

[09:20:35.316]发→◇00 01 00 00 00 06 01 04 00 00 00 04 □
[09:20:35.518]收←◆00 01 00 00 00 0B 01 04 08 00 04 57 8A 00 09 74 F0 
[09:20:36.319]发→◇00 01 00 00 00 06 01 04 00 00 00 04 □
[09:20:36.413]收←◆00 01 00 00 00 0B 01 04 08 00 04 59 35 00 09 75 A7 
[09:20:37.321]发→◇00 01 00 00 00 06 01 04 00 00 00 04 □
[09:20:37.462]收←◆00 01 00 00 00 0B 01 04 08 00 04 58 5F 00 09 77 06 
[09:20:38.314]发→◇00 01 00 00 00 06 01 04 00 00 00 04 □
[09:20:39.314]发→◇00 01 00 00 00 06 01 04 00 00 00 04 □
[09:20:40.322]发→◇00 01 00 00 00 06 01 04 00 00 00 04 □
[09:20:41.321]发→◇00 01 00 00 00 06 01 04 00 00 00 04 □
[09:21:00.981]发→◇00 01 00 00 00 06 01 04 00 00 00 04 □
[09:21:01.219]收←◆00 01 00 00 00 0B 01 04 08 00 04 58 95 00 09 6E 80 
[09:21:01.993]发→◇00 01 00 00 00 06 01 04 00 00 00 04 □
[09:21:02.091]收←◆00 01 00 00 00 0B 01 04 08 00 04 58 FF 00 09 6D AA 
[09:21:02.992]发→◇00 01 00 00 00 06 01 04 00 00 00 04 □
[09:21:03.107]收←◆00 01 00 00 00 0B 01 04 08 00 04 59 35 00 09 6E 34 
[09:21:03.986]发→◇00 01 00 00 00 06 01 04 00 00 00 04 □
[09:21:04.080]收←◆00 01 00 00 00 0B 01 04 08 00 04 58 95 00 09 6D 4F 
[09:21:04.993]发→◇00 01 00 00 00 06 01 04 00 00 00 04 □
[09:21:05.101]收←◆00 01 00 00 00 0B 01 04 08 00 04 58 95 00 09 6D 4F 
[09:21:05.994]发→◇00 01 00 00 00 06 01 04 00 00 00 04 □
[09:21:06.090]收←◆00 01 00 00 00 0B 01 04 08 00 04 57 DA 00 09 6D 4F 
[09:21:06.982]发→◇00 01 00 00 00 06 01 04 00 00 00 04 □
[09:21:07.092]收←◆00 01 00 00 00 0B 01 04 08 00 04 58 44 00 09 6C C5 
[09:21:07.990]发→◇00 01 00 00 00 06 01 04 00 00 00 04 □
[09:21:08.099]收←◆00 01 00 00 00 0B 01 04 08 00 04 58 5F 00 09 6D 30 
[09:21:08.991]发→◇00 01 00 00 00 06 01 04 00 00 00 04 □
[09:21:09.147]收←◆00 01 00 00 00 0B 01 04 08 00 04 58 0F 00 09 6E 06 
[09:21:09.984]发→◇00 01 00 00 00 06 01 04 00 00 00 04 □
[09:21:10.985]发→◇00 01 00 00 00 06 01 04 00 00 00 04 □
[09:21:11.983]发→◇00 01 00 00 00 06 01 04 00 00 00 04 □
[09:21:12.981]发→◇00 01 00 00 00 06 01 04 00 00 00 04 □


TCP Slave log:

[09:18:58.408]收←◆I (232092) port.utils: Socket (#55), accept client connection from address[port]: 10.10.50.210[40998]

[09:20:39.392]收←◆E (333082) mb_port.tcp.slave: queue can not find the item to send.
E (333082) mb_port.tcp.slave: incorrect frame to send.
E (333082) mb_object.slave: 0x4084355c:frame send error. 5

[09:20:41.605]收←◆E (335282) mb_port.tcp.slave: 0x40844eec, no queued items found
E (335282) mb_port.tcp.slave: queue can not find the item to send.
E (335282) mb_port.tcp.slave: incorrect frame to send.
E (335292) mb_object.slave: 0x4084355c:frame send error. 5

[09:20:42.748]收←◆E (336432) mb_port.tcp.slave: 0x40844eec, no queued items found

[09:20:43.892]收←◆E (337582) mb_port.tcp.slave: 0x40844eec, no queued items found

[09:20:45.049]收←◆E (338732) mb_port.tcp.slave: queue can not find the item to send.
E (338732) mb_port.tcp.slave: incorrect frame to send.
E (338732) mb_object.slave: 0x4084355c:frame send error. 5

[09:20:46.147]收←◆E (339832) mb_port.tcp.slave: queue can not find the item to send.
E (339832) mb_port.tcp.slave: incorrect frame to send.
E (339832) mb_object.slave: 0x4084355c:frame send error. 5

[09:20:47.198]收←◆E (340882) mb_port.tcp.slave: queue can not find the item to send.
E (340882) mb_port.tcp.slave: incorrect frame to send.
E (340882) mb_object.slave: 0x4084355c:frame send error. 5

[09:20:48.302]收←◆E (341982) mb_port.tcp.slave: queue can not find the item to send.
E (341982) mb_port.tcp.slave: incorrect frame to send.
E (341982) mb_object.slave: 0x4084355c:frame send error. 5

[09:20:48.396]收←◆I (342082) port.utils: Socket (#57), accept client connection from address[port]: 10.10.50.210[50392]

[09:20:48.495]收←◆E (342182) mb_port.tcp.slave: Node: #0 is not alive, err= -11

[09:21:11.079]收←◆E (364762) mb_port.tcp.slave: 0x40844eec, no queued items found

[09:21:12.233]收←◆E (365912) mb_port.tcp.slave: 0x40844eec, no queued items found

[09:21:13.378]收←◆E (367062) mb_port.tcp.slave: 0x40844eec, no queued items found

[09:21:14.522]收←◆E (368212) mb_port.tcp.slave: 0x40844eec, no queued items found

Steps to reproduce the behavior

1. ESP32 runs a TCP Slave instance.
2. Use the TCP client tool to connect to the TCP Slave.
3. The TCP client tool sends requests to the TCP Slave at a rate of 1RPS.

Project release version

v2.1.0

System architecture

Intel/AMD 64-bit (modern PC, older Mac)

Operating system

Windows

Operating system version

Windows 10 22H2

Shell

Bash

Additional context

The faster the client's request rate, the sooner unresponsiveness occurs.

[sytuacmdyh]

In my case, this modbus tcp client works well when I start only one modbus tcp master.

but when I start the second modbus master, this bug occurs frequently.

---

v1.0.18 both works fine

[alisitsyn]

@sytuacmdyh ,

Thank you for report. I was able to reproduce this and know the reason for this. I will continue with the fix once other tasks are completed. I will let you know once fixed. Sorry for inconvenience.

[alisitsyn]

This issue was fixed with commit [6dcac67].

@sytuacmdyh , @dsyx ,

Please check if this fixes your issue. Also, please take a look to some comments related to communication from multiple masters to one slave.