Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.
Modbus poll algorithm
-
Hi,
I wanted to change the way modbus master polls the slaves, but as I see, it is implemented in seroutils...
Now if all slaves are online, they are queried one after the other. If a slave goes offline, it is queried "retries" times in one round, then it is qualified offline.
My version would always query each slave only one time in a round, and qualify a slave offline only if "retries" number of rounds has elapsed without a proper answer.
It's not a big difference, but gives more time for the network to recover from a transient failure.
I don't know, if this algorithm was suitable for other modbus users/uses, or could be implemented only as an option.Thanks,
Greg -
Hi Greg,
That's not in seroUtils. You could make that change directly in the Modbus data source RT.
-
Oh, sorry, it's not just the data source RT. It would be a combination of there, and the Modbus4J code (which is what creates the requests from the batch).
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login