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

Trouble with workstation keeping up with extended logging

Building Automation Knowledge Base

Schneider Electric Building Automation Knowledge Base is a self-service resource to answer all your questions about EcoStruxure Building suite, Andover Continuum, Satchwell, TAC…

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
  • Building Automation Knowledge Base
  • Trouble with workstation keeping up with extended logging
Options
  • Bookmark
  • Subscribe
  • Email to a Friend
  • Printer Friendly Page
  • Report Inappropriate Content
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

Related Forums

  • Intelligent Devices Forum

Previous Next
Contributors
  • Cody_Failinger
    Cody_Failinger
  • CraigEl
    CraigEl
  • BillNeville
    BillNeville
  • Product_Support
    Product_Support

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague Invite
Back to Building Automation Knowledge Base
Options
  • Bookmark
  • Subscribe
  • Email to a Friend
  • Printer Friendly Page
  • Report Inappropriate Content
0 Likes
1517 Views

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

Trying to translate this page to your language?
Select your language from the translate dropdown in the upper right. arrow
Translate to: English
  • (Français) French
  • (Deutsche) German
  • (Italiano) Italian
  • (Português) Portuguese
  • (Русский) Russian
  • (Español) Spanish

Trouble with workstation keeping up with extended logging

Picard Product_Support
‎2018-09-10 04:46 AM

Last Updated: Administrator CraigEl Administrator ‎2022-08-10 05:06 PM

Issue

Standalone v1.93 system has about 1000 points being extended logged for site commissioning. There are "holes" in the extended log data.

Product Line

Andover Continuum

Environment

Standalone CyberStation v1.93

Cause

Standalone v1.93 system has about 1000 points being extended logged for site commissioning. There are "holes" in the extended log data.

The points are being logged at 2 minute intervals. Partner added a second (temporary) workstation to help with extended logging. This is still a standalone (SQLExpress) system. Extended log data is being extracted using Excel on the standalone server.

 

Even with the second CyberStation helping with the load, there are still holes in the log data.

Resolution

The workstations cannot handle the extended logging of ~1000 points at 2 minute intervals. Not using SQL Express on a single user even with a second workstation.

See also Extended Logging gaps, performance and load balancing.

This article mentions 2000 points per workstation but it is likely that this was all based on 15 minutes intervals and running full SQL Server.

At 2 minutes intervals you need to gather 720,000 entries/day or 8.333 entries/sec.
At 15 minute intervals you need to gather 96,000 entries/day or 1.111 entries/sec.
This is a big difference.

In addition, the Excel script is reading from the same extended log table being written to, at 8.333 entries/sec.
 

The controller log engine is completely independent of the extended log engine. The controller logs never send their data to CyberStation; CyberStation has to go get it. The extended log engine uses the general preference settings. In this case the settings are as follows and appear fine.

7. Extended log database check interval (minutes): 5
8. Extended log maximum LAN buffer interval (minutes): 30
10. Extended log automatic purge interval (days): 5
 

CyberStation is constantly trying to gather data from logs well before the “deadline” when the log fills and is about to be overwritten. While doing this, CyberStation also has to monitor time in the controllers, to make sure it is not too far out of sync, and this may potentially take place on field bus controllers on many network controllers, which may even be in different time zones. It also has to know when controllers have gone offline, or for some reason extended log values have not been updated.

In this case, CyberStation must try to play catch up when the controllers come back online (remember, these offline controllers have most likely continued to log data). And the same “catch up” has to take place if one or both workstations are turned off, or are busy doing other tasks like running reports or polling points via Pinpoint or Listviews.

The bottom line is that the CyberStation extended log data collection engine is sophisticated and complicated. To get a sense of this run AccTrace.exe (in the \Continuum folder) on a system busy with extended logs and you'll see it firsthand.

 When a SQL Express system with one or two workstations is trying to collect the logs and do everything else that CyberStation does (listviews, reports, schedules, pinpoint, etc), at times, some data may get dropped. The recommendation at this site was to lighten up the CyberStation load by changing the log interval to 15 minutes and monitor if the extended log holes get eliminated.
 

Labels (1)
Labels:
  • Andover Continuum
Tags (1)
  • Find more articles tagged with:
  • 6574
Was this article helpful? Yes No
No ratings

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

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