UNWANTED SPIKES IN PSO2020 TREND AND ADVANCE REPORTING.
Industry Automation and Control Forum
This forum is addressing industrial automation design & engineering, operations, asset performance, cyber security and digital transformation for Plants & Machines.
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 InviteCancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2025-04-2003:08 AM. Last Modified: 2025-04-2004:34 AM
UNWANTED SPIKES IN PSO2020 TREND AND ADVANCE REPORTING.
Dear Guide,
I am experiencing a sudden spike for a period of 1 to 5 minutes in the scada graphics, trends and advanced reporting for some of the PMU meters. I am not sure theses spike are generating from PMU or by SCADA itself?. Eventually it is affecting our advance reporting calculations.
Can someone please support me, how to combact the recording the sudden spike data in trends and advanced reporting?
Software - Power Scada Operation 2020
Field scenerio given below.
Time
ms
(New Pane)-Building1\MMXU1\TotVA
10:38:41
725
272.8714424
10:38:43
725
272.8695883
10:38:45
725
272.8677341
10:38:47
725
272.8658799
10:38:49
725
272.8640258
10:38:51
725
272.8621716
10:38:53
725
272.8603174
10:38:55
725
272.8584633
10:38:57
725
272.8566091
10:38:59
725
272.8547549
10:39:01
725
5,983,429,845,664,970,000
10:39:03
725
12,920,715,265,664,900,000
10:39:05
725
19,858,000,685,664,900,000
10:39:07
725
26,795,286,105,664,900,000
10:39:09
725
33,732,571,525,664,900,000
10:39:11
725
40,669,856,945,664,900,000
10:39:13
725
47,607,142,365,664,900,000
10:39:15
725
54,544,427,785,664,900,000
10:39:17
725
61,481,713,205,664,900,000
10:39:19
725
68,418,998,625,664,900,000
10:39:21
725
75,356,284,045,664,900,000
10:39:23
725
82,293,569,465,664,900,000
10:39:25
725
89,230,854,885,664,900,000
10:39:27
725
96,168,140,305,664,900,000
10:39:29
725
103,105,425,725,664,000,000
10:39:31
725
98,075,851,454,335,000,000
10:39:33
725
91,138,566,034,335,000,000
10:39:35
725
84,201,280,614,335,000,000
10:39:37
725
77,263,995,194,335,000,000
10:39:39
725
70,326,709,774,335,000,000
10:39:41
725
63,389,424,354,335,000,000
10:39:43
725
56,452,138,934,335,000,000
10:39:45
725
49,514,853,514,335,000,000
10:39:47
725
42,577,568,094,335,000,000
10:39:49
725
35,640,282,674,335,000,000
10:39:51
725
28,702,997,254,335,000,000
10:39:53
725
21,765,711,834,335,000,000
10:39:55
725
14,828,426,414,335,000,000
10:39:57
725
7,891,140,994,335,010,000
10:39:59
725
953,855,574,335,012,000
10:40:01
725
275.9327648
10:40:03
725
275.7236523
10:40:05
725
275.5145398
10:40:07
725
275.3054273
10:40:09
725
275.0963148
10:40:11
725
274.8872023
10:40:13
725
274.6780898
10:40:15
725
274.4689773
10:40:17
725
274.2598648
10:40:19
725
274.0507523
Please let me know for any other details required related to errors.