Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Notifications
Login / Register
Community
Community
Notifications
close
  • Forums
  • Knowledge Center
  • Events & Webinars
  • Ideas
  • Blogs
Help
Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Login / Register
Sustainability
Sustainability

We Value Your Feedback!
Could you please spare a few minutes to share your thoughts on Cloud Connected vs On-Premise Services. Your feedback can help us shape the future of services.
Learn more about the survey or Click here to Launch the survey
Schneider Electric Services Innovation Team!

Modbus Driver Polling Differences

Geo SCADA Knowledge Base

Access vast amounts of technical know-how and pro tips from our community of Geo SCADA experts.

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
  • Home
  • Schneider Electric Community
  • Knowledge Center
  • Geo SCADA Knowledge Base
  • Modbus Driver Polling Differences
Invite a Co-worker
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 Invite Cancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Send New Invite Close
Top Labels
Top Labels
  • Alphabetical
  • database 32
  • Web Server and Client 31
  • WebX 19
  • Request Form 18
  • Lists, Events & Alarms 16
  • ViewX 15
  • Application Programming 12
  • Setup 12
  • Telemetry 8
  • Events & Alarms 7
  • Lists 7
  • Mimic Graphics 7
  • Downloads 6
  • Support 5
  • IoT 5
  • SCADA 5
  • Geo SCADA Expert 5
  • Drivers and Communications 4
  • Security 4
  • DNP 3 3
  • IEC 61131-3 Logic 3
  • Trends and Historian 2
  • Virtual ViewX 2
  • Geo Scada 1
  • ClearSCADA 1
  • Templates and Instances 1
  • Releases 1
  • Maps and GIS 1
  • Mobile 1
  • Architectures 1
  • Tools & Resources 1
  • Privacy Policy 1
  • OPC-UA 1
  • Previous
  • 1 of 4
  • Next
Latest Blog Posts
  • OPC UA - Driver and Server
  • Requirements for Generating a Valid OPC UA Server Certificate
  • Load Events Using LoadRecord and LoadRecords
  • Geo SCADA Embedded Component Licenses
  • Geo SCADA 2023 Known Issues
Related Products
product field
Schneider Electric
EcoStruxure™ Geo SCADA Expert

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague Invite
Anonymous user
Not applicable
‎2021-06-09 02:55 PM
0 Likes
0
1529
  • Bookmark
  • Subscribe
  • Email to a Friend
  • Printer Friendly Page
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

‎2021-06-09 02:55 PM

Modbus Driver Polling Differences

Originally published on Geo SCADA Knowledge Base by Anonymous user | June 09, 2021 11:55 PM

📖 Home  Back  
ClearSCADA contains both a Modbus and SCADAPack Modbus protocol driver.  While both protocols can read from generic Modbus devices, there are differences in the polling methodology used in each.

Modbus (and Modbus Slave) are both simple drivers. The Modbus driver uses a specific polling methodology (the Modbus Slave driver does not poll data). SCADAPack Modbus is an advanced driver and uses a different polling methodology. Both polling methodologies are described below.


Modbus Driver Polling Methodology



The Modbus driver scans a defined range of registers. You can specify the range when you configure a Modbus scanner in the ClearSCADA database (in the Data Address and Data Length fields). Each Modbus scanner item instructs the Modbus driver to poll data.


The configuration of the Modbus scanner defines:


  • Which types of register are to be polled (the Location setting)


  • How many registers are to be polled (the Data Address and Data Length settings)


  • When the registers are to be polled (defined in the various Normal Scan Rate and Promoted Scan Rate fields).


By adjusting the configuration of the Modbus Scanner, you can control the amount of data that is polled and the frequency of polls.

The Modbus driver always polls the entire range of registers (the range defined by the Data Address and Data Length settings in the Modbus Scanner configuration). So, if the Location is Input Discretes, the Data Address is 10 and the Data Length is 15, the Modbus driver will poll 15 registers, starting from the 10th register in the Input Discrete range. As the Input Discrete range is 100001 to 165536, this means the Modbus driver will poll the address range 100011 to 100026.

For more information on Modbus configuration, see the ClearSCADA Help.



SCADAPack Modbus Polling Methodology



The SCADAPack Modbus driver is an advanced driver and uses different settings to determine what registers are polled and when they are polled.

Each SCADAPack Modbus point has a unique address that corresponds to a register in the Modbus outstation. The address is defined the point configuration, along with an association with a Retrieval Interval (the time scales for the Retrieval Intervals are defined in the configuration for the Modbus outstation). These configuration settings define which registers are polled and how often they are polled.

Unlike the simple Modbus driver, the SCADAPack Modbus driver dynamically creates the start register for the poll and the amount of data to poll, based on the configuration settings of the point. This means that it can poll individual registers and does not have to poll all registers in a range. For example, the SCADAPack Modbus driver can poll registers 30001 and 30050 without polling registers 30002, 30003, 30004 and so on. (Note that this can also be achieved with the simple Modbus driver, but it involves extra configuration work as you need to create and configure separate Modbus Scanners for each non-sequential register. For example, to poll registers 30003, 30004, 30009, you would need to configure 2 Modbus Scanners: 1 scanner for the sequential registers, 30003 and 30004, and another scanner for register 30009. With the SCADAPack Modbus driver, you only need to configure a single controller).

When the SCADAPack Modbus driver is required to poll sequential registers, it is more efficient to poll the entire range rather than poll each individual register. For this reason, the SCADAPack Modbus driver allows a maximum 'gap' of 4 registers or 40 coils depending on the type of data being polled. So, if the SCADAPack Modbus driver is to poll registers 30001, 30003, and 30004, it will poll them at the same time rather than individually as the 'gap' is less than 4 registers. If the SCADAPack Modbus driver had to poll registers 30001, 30003, and 30050, it would poll 30001 and 30003 together and poll register 30050 separately as the 'gap' between 30003 and 30050 is greater than 4 registers.

If the SCADAPack Modbus points are configured to use different Retrieval Intervals, the SCADAPack Modbus driver will poll each register individually according to the point's Retrieval Interval. However, if the 'gap' is less than 4 registers, and the registers are to be polled at the same time (despite having different Retrieval Intervals), the SCADAPack Modbus driver will poll both registers in a single request.

For example, Point A is configured with the Address 30002 and is associated with Retrieval Interval 2 (which is configured to be 2 seconds in the outstation configuration. Another point, Point B, is configured with the Address 30005 and is associated with Retrieval Interval 3 (which is configured to be 5 seconds).

After 2 seconds, the SCADAPack Modbus driver polls Point A.
After 4 seconds, the SCADAPack Modbus driver polls Point A.
After 5 seconds, the SCADAPack Modbus driver polls Point B.
After 6 seconds, the SCADAPack Modbus driver polls Point A.
After 8 seconds, the SCADAPack Modbus driver polls Point A.
After 10 seconds, the SCADAPack Modbus driver polls both Point A and Point B in a single request.

For more information on SCADAPack Modbus configuration, see the ClearSCADA Help.


Go: Home Back

Author

Biography

Anonymous user

Link copied. Please paste this link to share this article on your social media post.

  • Back to Blog
  • Newer Article
  • Older Article
To The Top!

Forums

  • APC UPS Data Center Backup Solutions
  • EcoStruxure IT
  • EcoStruxure Geo SCADA Expert
  • Metering & Power Quality
  • Schneider Electric Wiser

Knowledge Center

Events & webinars

Ideas

Blogs

Get Started

  • Ask the Community
  • Community Guidelines
  • Community User Guide
  • How-To & Best Practice
  • Experts Leaderboard
  • Contact Support
Brand-Logo
Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Forum-Icon

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.

Register today for FREE

Register Now

Already have an account? Login

Terms & Conditions Privacy Notice Change your Cookie Settings © 2025 Schneider Electric

This is a heading

With achievable small steps, users progress and continually feel satisfaction in task accomplishment.

Usetiful Onboarding Checklist remembers the progress of every user, allowing them to take bite-sized journeys and continue where they left.

of