We use cookies to try and give you a better experience in Freshdesk.
You can learn more about what kind of cookies we use, why, and how from our Privacy policy. If you hate cookies, or are just on a diet, you can disable them altogether too. Just note that the Freshdesk service is pretty big on some cookies (we love the choco-chip ones), and some portions of Freshdesk may not work properly if you disable cookies.
We’ll also assume you agree to the way we use cookies and are ok with it as described in our Privacy policy, unless you choose to disable them altogether through your browser.
Currently the ModBus nodes (multipoll more specific) don't output a good status when they are busy requesting data.
This makes it hard for the user to know if the request node is actually doing something or not.
See attached screenshot of a status node on a multipoll node.
We only get active - started status when the 1st request is triggered and a result when it's done. But following requests don't provide a start or busy status, only a result status.
Can this be changed so the ModBus nodes provide a proper status when busy requesting data?
Attachments (1)
2018-08-27 1....png
20.3 KB
0 Votes
1 Comments
OPTION Support posted about 6 years ago Admin
The started status is actually to indicate that the tcp/serial connection is connected.
That is why you only see it on the first request.
Giving a status when a poll from a certain node is happening is difficult because all polls to the same (tcp/serial) connection go into the same queue.
Best regards,
Timothy
0 Votes
Login to post a comment