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

Join our "Ask Me About" community webinar on May 20th at 9 AM CET and 5 PM CET to explore cybersecurity and monitoring for Data Center and edge IT. Learn about market trends, cutting-edge technologies, and best practices from industry experts.
Register and secure your Critical IT infrastructure

Request Timeout and Request Timeout Extension for Advanced Drivers

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
  • Request Timeout and Request Timeout Extension for Advanced Drivers
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 08:27 AM
0 Likes
0
1381
  • 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 08:27 AM

Request Timeout and Request Timeout Extension for Advanced Drivers

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

📖 Home  Back  
You can use the ClearSCADA Server Configuration Tool (under Global Parameters/Drivers) to define the maximum amount of time permitted for a driver to complete a request. By defining a maximum time, you ensure that the driver can abort a request that is taking too long to complete. This prevents requests from taking an excessive amount of time to complete (or becoming 'stuck' and unable to complete).

There are two driver request timeouts:
  • Request Timeout — The driver must start to perform the request within this period. If the request is still pending after this period, the request is aborted and fails. However, if the request is active when the Request Timeout time expires, additional time is allowed for the request to complete. This additional amount of time is the Request Timeout Extension.

  • Request Timeout Extension — An additional amount of time that is added to the Request Timeout. The Request Timeout Extension is only used if the request is active at the time the Request Timeout expires. For example, if the Request Timeout is 600 seconds, and after 600 seconds the request is active (the driver is in the process of performing the request), the request is allowed an additional period to complete. The additional time period is the amount of time defined for the Request Timeout Extension. If the request has not completed after this extended period, the request is aborted and fails.


Typically, the default settings of 10 minutes, with a 5 minute extension are adequate. However, certain requests such as a file transfer or download configuration may take longer due to slow communication links, or very large files or outstations. For these types of request, you may need to increase the timeouts.

Requests that are aborted and fail due to a timeout are logged in the Event Journal.

Following we have real world examples of how the timeouts work showing excerpts from the DNP3 driver log:
  • Request completed within the Request Timeout period

  • Driver receives from DBServer a request to disable alarms for a point in an outstation (DNP3 protocol). This involves file/configuration transfer.

02-AUG-2010 00:23:27.571 [Main] Received Disable Alarms request (Id:63763) for "S.BONDI.SP0028 BALMAIN.SITE_.PWR01.Authority Supply Fail Hours"

  • The process is completed within 10 min (600 sec, default Request Timeout period)

02-AUG-2010 00:23:27.574 [Main] Sending Disable Alarms request (Id:63763) for "S.BONDI.SP0028 BALMAIN.SITE_.PWR01.Authority Supply Fail Hours" to "*System.Comms.S.DNP IP.SetChannel 0091.Channel A"02-AUG-2010 00:23:27.574 [Channel A #2823932] Activated Disable Alarms request for "S.BONDI.SP0028 BALMAIN.SITE_.PWR01.Authority Supply Fail Hours" in scanner02-AUG-2010 00:23:27.578 [Channel A #2823932] Adjusting Disable Alarms request for "S.BONDI.SP0028 BALMAIN.SITE_.PWR01.Authority Supply Fail Hours" to timeout in 30164 ms02-AUG-2010 00:23:27.621 [Channel A #2823932] Adjusting Disable Alarms request for "S.BONDI.SP0028 BALMAIN.SITE_.PWR01.Authority Supply Fail Hours" to timeout in 37183 ms02-AUG-2010 00:23:30.847 [Channel A #2823932] Adjusting Disable Alarms request for "S.BONDI.SP0028 BALMAIN.SITE_.PWR01.Authority Supply Fail Hours" to timeout in 30151 ms02-AUG-2010 00:23:31.777 [Channel A #2823932] Adjusting Disable Alarms request for "S.BONDI.SP0028 BALMAIN.SITE_.PWR01.Authority Supply Fail Hours" to timeout in 30154 ms02-AUG-2010 00:23:31.815 [Channel A #2823932] Adjusting Disable Alarms request for "S.BONDI.SP0028 BALMAIN.SITE_.PWR01.Authority Supply Fail Hours" to timeout in 30161 ms02-AUG-2010 00:23:31.865 [Main] Received reply (Successful) from scanner to Disable Alarms request (Id:63763) for "S.BONDI.SP0028 BALMAIN.SITE_.PWR01.Authority Supply Fail Hours"

  • Request started within the Request Timeout Period and completed within the Request Timeout Extension Period

  • Driver receives from DBServer a request to disable alarms for a point in an outstation (DNP3 protocol). This involves file/configuration transfer.

02-AUG-2010 00:24:08.096 [Main] Received Disable Alarms request (Id:63963) for "S.BONDI.SP0028 BALMAIN.SP0028.WELCNTL_.Control Well Rotation"

  • Driver starts the process within 10 min (600 sec, default Request Timeout period)

02-AUG-2010 00:34:07.837 [Main] Sending Disable Alarms request (Id:63963) for "S.BONDI.SP0028 BALMAIN.SP0028.WELCNTL_.Control Well Rotation" to "*System.Comms.S.DNP IP.SetChannel 0091.Channel A"02-AUG-2010 00:34:07.837 [Channel A #2823932] Activated Disable Alarms request for "S.BONDI.SP0028 BALMAIN.SP0028.WELCNTL_.Control Well Rotation" in scanner02-AUG-2010 00:34:07.841 [Channel A #2823932] Adjusting Disable Alarms request for "S.BONDI.SP0028 BALMAIN.SP0028.WELCNTL_.Control Well Rotation" to timeout in 30164 ms02-AUG-2010 00:34:07.875 [Channel A #2823932] Adjusting Disable Alarms request for "S.BONDI.SP0028 BALMAIN.SP0028.WELCNTL_.Control Well Rotation" to timeout in 37183 ms

  • As the process doesn't end within 10 mins, a Request Timeout Extension Period of 5 mins is granted (300 sec, default Request Timeout Extension period). It ends successfully within the extended period.

02-AUG-2010 00:34:08.096 [Main] Extending time out of Disable Alarms request (Id:63963) for "S.BONDI.SP0028 BALMAIN.SP0028.WELCNTL_.Control Well Rotation" by 300 sec02-AUG-2010 00:34:10.570 [Channel A #2823932] Adjusting Disable Alarms request for "S.BONDI.SP0028 BALMAIN.SP0028.WELCNTL_.Control Well Rotation" to timeout in 30151 ms02-AUG-2010 00:34:12.139 [Channel A #2823932] Adjusting Disable Alarms request for "S.BONDI.SP0028 BALMAIN.SP0028.WELCNTL_.Control Well Rotation" to timeout in 30154 ms02-AUG-2010 00:34:12.181 [Channel A #2823932] Adjusting Disable Alarms request for "S.BONDI.SP0028 BALMAIN.SP0028.WELCNTL_.Control Well Rotation" to timeout in 30161 ms02-AUG-2010 00:34:12.226 [Main] Received reply (Successful) from scanner to Disable Alarms request (Id:63963) for "S.BONDI.SP0028 BALMAIN.SP0028.WELCNTL_.Control Well Rotation"

  • Request not started within 10 min (timeout)

  • In this case, the queue of messages is full, and the requested process don't start within 10 min.

02-AUG-2010 00:24:08.251 [Main] Received Disable Alarms request (Id:63964) for "S.BONDI.SP0028 BALMAIN.SP0028.WELCNTL_.Control Well Selection"02-AUG-2010 00:34:08.251 [Main] Timed out Disable Alarms request (Id:63964) for "S.BONDI.SP0028 BALMAIN.SP0028.WELCNTL_.Control Well Selection" (Overall)


Go: Home Back
Labels:
  • Drivers and Communications

  • Request Form

Author

Biography

Anonymous user

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

  • Back to Blog
  • Newer 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