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!

Historic List Data Recording Frequency

EcoStruxure Geo SCADA Expert Forum

Schneider Electric support forum about installation, configuration, integration and troubleshooting of EcoStruxure Geo SCADA Expert (ClearSCADA, ViewX, WebX).

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
  • Remote Operations
  • EcoStruxure Geo SCADA Expert Forum
  • Historic List Data Recording Frequency
Options
  • Mark Topic as New
  • Mark Topic as Read
  • Float this Topic for Current User
  • Bookmark
  • Subscribe
  • Mute
  • Printer Friendly Page
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 Experts
User Count
sbeadle
Kirk sbeadle Kirk
308
AndrewScott
Admiral AndrewScott
97
BevanWeiss
Spock BevanWeiss
91
AdamWoodlandToo
Lt. Commander AdamWoodlandToo
37
View All
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
Back to EcoStruxure Geo SCADA Expert Forum
Emre123124
Ensign Emre123124
Ensign

Posted: ‎2025-05-26 01:57 AM

0 Likes
6
514
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

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

Posted: ‎2025-05-26 01:57 AM

Historic List Data Recording Frequency

Hello,

There are a few issues that I need to fix regarding the Historic List in the Geo Scada Expert 2023 November 2024 version.

 

The first of these is related to the recording of live data I receive from the field. I receive data from the field via Modbus TCP and it is updated instantly in Geo Scada. This data is recorded in the historic list every 5 minutes, which is what I want. However, in these 5-minute recordings, the data is recorded twice in a row within the same second. In other words, there are 2 data records when there should be 1 data record in 5 minutes. What can I do to record this number of records as 1 in 5 minutes? The sections where I set the recording and change frequency with the Historic List that I viewed for the signal are as shown in the image below.

Emre123124_0-1748248753082.png

 

Emre123124_1-1748248780936.png

 

Emre123124_2-1748248792061.png

 

Another issue is that I produce percentage data from this live data that I mentioned using the Calculation signal. This signal should be updated instantly according to the field signal I mentioned above and recorded in the Historic List every 5 minutes. However, when I try different things, this signal is either not updated instantly in some of them, or the recording frequency occurs at every change, or even if it records as frequently as I want, the number of data is 2 or 3.

 

With the settings below, the data is updated at every change, but the Historic List recording frequency is the same.

Emre123124_3-1748249075302.png

 

Emre123124_4-1748249112157.png

 

Emre123124_5-1748249119475.png

 

When I change the execution settings to Periodic, the recording frequency changes to 1 data per minute (I did this for the test, it would normally be 5 minutes), but the data update frequency is also 1 per minute, it is not updated instantly.

Emre123124_6-1748249432763.png

 

Emre123124_7-1748249513532.png

 

Emre123124_8-1748249535866.png

 

Actually, I want the update and recording frequencies to be the same for both signals. They should be updated instantly according to the value coming from the field and the Historic List should be recorded as 1 data every 5 minutes. Can you help me with this?

Labels
  • Labels:
  • ViewX
  • Tags:
  • english
  • scada
  • SCADA app
  • SCADA software
  • SCADA tutorial
  • Telemetry and SCADA
Reply

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

  • All forum topics
  • Previous Topic
  • Next Topic
Replies 6
JChamberlain1
Lieutenant JG JChamberlain1
Lieutenant JG

Posted: ‎2025-05-26 10:21 PM

0 Likes
1
477
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

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

Posted: ‎2025-05-26 10:21 PM

That's how GS implements historic compression, it saves the values before and after a significant change.

 

https://tprojects.schneider-electric.com/GeoSCADAHelp/Geo%20SCADA%202022/Default.htm#CorePointConfig...

 

Your minimum interval of 300s = 5min is driving it. If you want one value, use a historic view.

Reply

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

Emre123124
Ensign Emre123124
Ensign

Posted: ‎2025-05-27 12:24 AM

In response to JChamberlain1
0 Likes
0
420
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

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

Posted: ‎2025-05-27 12:24 AM

I couldn't understand exactly how using the Historic View would benefit me. When we add from the Historic View, aren't we actually doing something like creating a query? What exactly will I use this for? And do I need to do something like edit the query to integrate it into my signal? Can you explain a little more about how I should proceed with the Historic View list or share documentation on this subject?

Reply

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

sbeadle
Kirk sbeadle Kirk
Kirk

Posted: ‎2025-05-27 02:32 AM

0 Likes
0
439
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

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

Posted: ‎2025-05-27 02:32 AM

Jesse is correct - the historian is there to record meaningful change, not fixed time data. Compression is there to reduce the number of samples stored based on its rules.

Use a Historic View to read out, list and report on historic data in fixed periods. A Historic View can be configured with time period, averaging algorithm, data filter and the default query period (overridden by a WHERE clause on the timestamp).

When you have set up your view, define the SQL and attach it to buttons in your mimics. (Or create an 'Extra Table Query').

Reply

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

sbeadle
Kirk sbeadle Kirk
Kirk

Posted: ‎2025-05-28 12:32 AM

0 Likes
1
399
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

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

Posted: ‎2025-05-28 12:32 AM

Yes, a Historic View is a query on the raw data. You can use it in on-screen lists, mimics, reports, SQL Export files.

 

Perhaps your expectation is that the raw data must contain only one value at fixed time intervals, with no others. This is not practical if your device goes offline.

 

The Historic View is a way to derive a single value per time interval from the source. You also get a quality number from which you can work out if the value was interpolated from missing data.

 

If you really really must have a single value stored in the historian, then turn off historic compression and configure the point to scan at your choice of interval.

 

Note your calculation point will execute on Tag Processed. (But if you have more than one input to the calculation point, it will update on each tag processed. If C = A + B, then you'll get updates for both A and B changing).

Reply

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

Emre123124
Ensign Emre123124
Ensign

Posted: ‎2025-05-28 03:01 AM

In response to sbeadle
0 Likes
0
346
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

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

Posted: ‎2025-05-28 03:01 AM

I understood the Tag Processed part as changing according to the update frequency of the signal I used in the calculation made in the Calculation Point. The live data used in the calculation there changes in Scada every time there is a change and the Historic List recording frequency is 2 in 5 minutes. When I select Tag Processed in my Calculation signal, it changes instantly in the same way as the live data, it records 2 data in 5 minutes in the Historic List. If I select the Periodic option instead of Tag Processed in the Calculation signal, I can record 1 data in 5 minutes, but my Calculation signal does not change instantly, it changes every 5 minutes. As you said, if I set the Compression option to No Data, it records every change in the Historic List. In this way, it can even record 2 or 3 data per second.

Do I need to look for a solution in the live data section coming from the field? The settings of the Historic Compression section of that signal are as follows.

Also, is this actually the same as the queries we use in the Historic List regarding the Historic View section? But how can I write it in a format suitable for it? do you have any documentation about this?

Reply

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

geoffpatton
Captain geoffpatton
Captain

Posted: ‎2025-06-02 09:30 AM

0 Likes
0
221
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

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

Posted: ‎2025-06-02 09:30 AM

If you cannot get anything else to work for you, you could try using an ST program with one input that will trigger the ST execution, and the output being an execute on the calculation point. you'll have to set the calculation execution to Method.

Reply

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

Preview Exit Preview

never-displayed

You must be signed in to add attachments

never-displayed

 
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