Ask Me About Webinar: Data Center Assets - Modeling, Cooling, and CFD Simulation
Join our 30-minute expert session on July 10, 2025 (9:00 AM & 5:00 PM CET), to explore Digital Twins, cooling simulations, and IT infrastructure modeling. Learn how to boost resiliency and plan power capacity effectively. Register now to secure your spot!
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
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!
Link copied. Please paste this link to share this article on your social media post.
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.