Welcome to the new Schneider Electric Community

It's your place to connect with experts and peers, get continuous support, and share knowledge.

Close
Important Announcement: WELCOME to the new Schneider Electric Community! Community is now no longer part of Exchange, and is now rebranded under se.com. If you have any bookmarks and links saved, we request you to update them to ensure that you continue accessing our community from this new location. For any issues that you might encounter as part of this change, please reach out to SchneiderCommunity.Support@se.com, and the team will help to get your issues resolved.
Invite a Co-worker
Send a co-worker an invite to the Exchange portal.Just enter their email address and we’ll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel
82130members
349652posts

Slow mimic update in GEO SCADA

EcoStruxure Geo SCADA Expert Forum

Find out how SCADA systems and networks, like EcoStruxure Geo SCADA Expert, help industrial organizations maintaining efficiency, processing data for smarter decision making with IoT, RTU and PLC devices.

BGedco2022
Lt. Commander
Lt. Commander
0 Likes
10
751

Slow mimic update in GEO SCADA

Hello everyone,

 

We have a main mimic that represents all RTUs in the System and display color based on RTU status (if open or close)

 

When any operator control any RTU to open/close. the main mimic being refresh very slowly that took almost 2 minutes.

 

Another mimic, when enter a value that processed using script also updated slowly.

 

Note that operators machine are in VLAN network.

 

Any hint for the causes or any solutions

 

Thanks in advance

 

 

10 Replies 10
BevanWeiss
Spock
Spock
0 Likes
9
720

Re: Slow mimic update in GEO SCADA

Open the Mimic(s) in ViewX, and on the Graphics toolbar display the Diagnostics, then send us the contents (you can Copy All, then paste it into a table here).

 

My suspicion is that you have lots of objects, likely Embedded Mimics, which all cost just a little extra to load.  Hence it bogs down the system with loading and putting on scan all the items.

 

GeoSCADA Expert has quite a complex graphical model, including low level configuration of shared cache-ability (Shared with other Embedded Mimics).  If you get this wrong, then that can really harm performance.  And it's not the easiest setting to get right if you use more advanced features like Indirect tags, SQL query animations etc.

Which is where I'd recommend not using those more advanced features until you REALLY know what you're doing... and even then avoid them if you can.

 

Are you using any such advanced features (within your mimic, or ANY embedded mimics referenced from these slow displays)?

i.e. an animation with square brackets like... ["animation something here"]

or worse still, one with [? SELECT thing here]


Lead Control Systems Engineer for Alliance Automation (VIC).
All opinions are my own and do not represent the opinions or policies of my employer, or of my cat..
BGedco2022
Lt. Commander
Lt. Commander
0 Likes
8
714

Re: Slow mimic update in GEO SCADA

this is a sample of the mimic diagnostic

Objects 119
Layers 2

Groups 1
Polylines 0
Text Items 27
Embedded Mimics 89
Embedded Trends 0
Embedded Dynagraphs 0
Embedded Lists 0
Embedded Alarm Lists 0
Embedded X-Y Plots 0
Embedded X-Y-Z Plots 0
Maps 0
Images 0
Remote Images 0
Buttons 0
Pie Charts 0
Pipes 0
ActiveX Controls 0

Segments 0
Max Segments 0
Max Segments / Region 0

Pick Actions 2
Hover Effects 0

Transparent Objects 1

Linear Gradient Fills 0
Pipe Gradient Fills 0
Radial Gradient Fills 0
Linear Gradient Texts 0
Pipe Gradient Texts 0
Radial Gradient Texts 0

Flashing Objects Yes

GDI+ Redraw Count 84
GDI+ Avg. Redraw Time 0.0798 seconds
GDI+ Total Redraw Time 6.7062 seconds

=====================================

sample #2:

Objects 128
Layers 2

Groups 1
Polylines 0
Text Items 28
Embedded Mimics 97
Embedded Trends 0
Embedded Dynagraphs 0
Embedded Lists 0
Embedded Alarm Lists 0
Embedded X-Y Plots 0
Embedded X-Y-Z Plots 0
Maps 0
Images 0
Remote Images 0
Buttons 0
Pie Charts 0
Pipes 0
ActiveX Controls 0

Segments 0
Max Segments 0
Max Segments / Region 0

Pick Actions 4
Hover Effects 0

Transparent Objects 1

Linear Gradient Fills 0
Pipe Gradient Fills 0
Radial Gradient Fills 0
Linear Gradient Texts 0
Pipe Gradient Texts 0
Radial Gradient Texts 0

Flashing Objects Yes

GDI+ Redraw Count 39
GDI+ Avg. Redraw Time 0.0791 seconds
GDI+ Total Redraw Time 3.0843 seconds

 


tfranklin
Lt. Commander
Lt. Commander
0 Likes
0
702

Re: Slow mimic update in GEO SCADA

Ouch!  GDI Total Redraw time of 6.7 seconds? I'm going to go out on a limb and guess that your mimic has improper usage if indirect animations.  Do you have animations somewhere on your embedded mimics that use indirect animations?  If so, I'd advise reading the help file about improper usage of them -- specifically where it mentions to never share objects that contain indirect animations.  I'd add to if and say that if you can avoid indirect animations, avoid them.  We reserve them specifically for popup faceplates and nothing more.

 

That said, I could be completely wrong but your object/mimic counts don't look bad at all.  Has to be animation related.

BevanWeiss
Spock
Spock
0 Likes
6
674

Re: Slow mimic update in GEO SCADA

Unfortunately with 89 and 97 embedded mimics this diagnostic doesn't tell us much.

 

What are your 'shared with other embedded mimics' set to?

What are on your embedded mimics?

Having >50 of them is an awful lot for a single mimic.

Even worse if each embedded mimic may then contain other embedded mimics.

 

I'm wondering if you potentially came from a Citect-like background, and you have lots of embedded mimics with static animation data, and if you're then hiding them etc based on tag values.

That's not really the GeoSCADA Expert way, directly animating the parameters (i.e. colour / position etc) is more so how GeoSCADA Expert performs well.

 


Lead Control Systems Engineer for Alliance Automation (VIC).
All opinions are my own and do not represent the opinions or policies of my employer, or of my cat..
BGedco2022
Lt. Commander
Lt. Commander
0 Likes
5
663

Re: Slow mimic update in GEO SCADA

(for testing) we created an empty mimic contains only value of a digital point

mimic-test.PNG

 

when we change its value from 1 to 0, it also took almost 2 minutes to update its value in the mimic

 

thanks very much taking time to help.

 

sbeadle
Janeway Janeway
Janeway

Re: Slow mimic update in GEO SCADA

There may be a lot more going on here than complex mimics. Geo SCADA prioritises database writes over reads, so it's possible you have configured scanners or logic to update the database at a very high rate. Please look at the execution interval of Logic and the scan rate of any drivers to see if there is anything like this.

BevanWeiss
Spock
Spock
0 Likes
1
612

Re: Slow mimic update in GEO SCADA

Was this an Internal Digital Point, or connected to a field device (where you changed the value in the field device)?


Lead Control Systems Engineer for Alliance Automation (VIC).
All opinions are my own and do not represent the opinions or policies of my employer, or of my cat..
BGedco2022
Lt. Commander
Lt. Commander
0 Likes
0
565

Re: Slow mimic update in GEO SCADA

it was internal digital point

BGedco2022
Lt. Commander
Lt. Commander
0 Likes
1
563

Re: Slow mimic update in GEO SCADA


@sbeadle wrote:

There may be a lot more going on here than complex mimics. Geo SCADA prioritises database writes over reads, so it's possible you have configured scanners or logic to update the database at a very high rate. Please look at the execution interval of Logic and the scan rate of any drivers to see if there is anything like this.


"configured scanners or logic to update the database at a very high rate"

can you explain that more please

 

 

sbeadle
Janeway Janeway
Janeway
0 Likes
0
529

Re: Slow mimic update in GEO SCADA

Please see this document which may help:

https://community.exchange.se.com/t5/Geo-SCADA-Knowledge-Base/Technical-Guides/ba-p/278414?attachmen...

See the table at the end for queries and techniques to help find problem items in configuration.