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

Allow/Enable a customizable delay between each Modbus request. #1664

Closed
ziotibia81 opened this issue Jan 30, 2025 · 1 comment
Closed

Allow/Enable a customizable delay between each Modbus request. #1664

ziotibia81 opened this issue Jan 30, 2025 · 1 comment
Assignees
Labels
can be closed Label uses when issue is fixed or feature is added and will be available in the next release.

Comments

@ziotibia81
Copy link

Currently, consecutive Modbus requests are sent directly without a delay.

This feature could be very useful. Some devices that implement Modbus RTU over TCP internally consist of a TCP-to-Serial converter connected to the device's microprocessor. In this scenario, it is important to have a delay between each request. Reading many consecutive registers in a singlerequest is more efficient with this type of device.

Originally posted by @ziotibia81 in #1589

This feature is also necessary when reading from multiple devices connected to an RS485 bus with a Modbus RTU to TCP bridge. A delay between each request is required to allow the devices time to internally switch their transmitters to high-impedance mode (HI-Z) and release the bus.

@imbeacon
Copy link
Member

imbeacon commented Feb 3, 2025

Hi @ziotibia81,

Thank you, for your interest in ThingsBoard IoT Gateway.
I have added parameter delayBetweenRequestsMs and processing for it to master, it allows to set delay between requests to device. Needs to be configured for each device separately, on the same configuration level, where you set port for connection.
By default it is set to 0 and doesn’t affect current processing.
In order to use it you can try the version from the master branch or wait for release. We are going to publish new release in few days.

@imbeacon imbeacon added the can be closed Label uses when issue is fixed or feature is added and will be available in the next release. label Feb 3, 2025
@imbeacon imbeacon self-assigned this Feb 3, 2025
@imbeacon imbeacon closed this as completed Feb 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
can be closed Label uses when issue is fixed or feature is added and will be available in the next release.
Projects
None yet
Development

No branches or pull requests

2 participants