New Community Ranking System
Our Community ranking system has recently been updated. You may notice changes in user rankings and receive system messages or notifications. If you have questions about how the new ranking works, please refer to the announcement post for more details (click here).
Advanced Modbus driver optimization
Geo SCADA and Remote Operations Devices Ideas
Use this portal to submit your innovative ideas to make Geo SCADA Expert and Devices such as SCADAPack, Trio and Realflo of greater value to you and to the SCADA & Telemetry community. Every idea will be individually reviewed by our team for merit and will be marked Under Consideration.
Search in
Improve your search experience:
Exact phrase→Use quotes " "(e.g., "error 404")
Wildcard→Use * for partial words(e.g., build*, *tion)
AND / OR→Combine keywords(e.g., login AND error, login OR sign‑in)
Keep it short→Use 2–3 relevant words, not full sentences
Filters→Narrow results by section(Knowledge Base, Users, Products)
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send InviteCancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
This feature request comes from a customer via bFO # 98925769 and # 98053984 as well as JIRA CSUP-13309.
The initial request was to optimize the driver to poll outstations as fast as possible (as they used to use a competitors SCADA system which performed that way). After discussing the pros/cons of that type of architecture, this customer chose to set up a separate channel for "Fast Scan" polling. Below are comments from the customer regarding this operation.
Switching Outstation to a separate “Fast Scan” channel and allowing IP100 to handle flow of communications helped, but did not completely resolve issues. When switching outstation back to “Normal Scan” channel it does a restart sequence similar to what a refresh does. SE development team should look at improving how Adv modbus driver handles communication flow and implement a better way of promote / refresh outstations. Outstation retrieval intervals is a great way to optimize points that don’t need to be poll often, but there should also be away to set poll interval to poll data fast as possible and still allow promote scan to work as it was intended to!
Whilst there isn't a specific promoted retrieval interval for continuous, setting the interval to a very small value (e.g. 1ms) will achieve the same effect.
This allows points to be promoted from their normal retrieval interval to 'continuous' using any type of promoted scanning (manual promotion, promote on display, promote after control).
When using two channels for "Normal Scan" and "Fast Scan" how are they switching between channels? Are they using a switched / shared outstation set and switching lines, or are they reconfiguring the outstation (or set) to a different channel? All of these will stop and restart comms with the outstation when switching. Making configuration changes for operational reasons should be avoided as its not efficient.