Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Limit the number of concurrent connections on MODBUS TCP #1670

Closed
ziotibia81 opened this issue Feb 5, 2025 · 1 comment
Closed

Limit the number of concurrent connections on MODBUS TCP #1670

ziotibia81 opened this issue Feb 5, 2025 · 1 comment

Comments

@ziotibia81
Copy link

This is another scenario related to #1664

Some MODBUS devices support very limited concurrent TCP connections. For example, I'm using a device that supports only two connections. Sometimes a connection to a device remains open without exchanging data. When the open connections reach the device connection limits, the gateway is no longer able to read data until a gateway or device restarts.

@imbeacon
Copy link
Member

imbeacon commented Feb 6, 2025

Hi @ziotibia81,

Keeping connection is by design, the gateway keeps connection to device to have ability to control it’s activity on ThingsBoard and be able to process incoming shared attributes and RPC correctly, so it is not possible to connect each time, also it will cause a lot of connection/disconnection messages between the gateway and device.

@imbeacon imbeacon closed this as not planned Won't fix, can't repro, duplicate, stale Feb 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants