EcoStruxure Geo SCADA Expert Forum
Schneider Electric support forum about installation, configuration, integration and troubleshooting of EcoStruxure Geo SCADA Expert (ClearSCADA, ViewX, WebX).
Link copied. Please paste this link to share this article on your social media post.
Posted: 2024-10-01 11:02 AM
I restored the backup and graphics in pink color.
how to remove this error?
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2024-10-24 04:41 AM
Was Adam's suggestion the answer?
i.e. if you export config from location X.Y, and your configuration has relative references to items outside the export (e.g, references to A, A.B or X) then import into a different folder or level (e.g. C or D.E) then the import won't find these outside references.
It's best to name an SDE file by the full name of the group, then you know where to import it to. e.g. if you export "East.RTU.Points" group, then place your cursor on "East.RTU" and import to that parent in order to get back what you exported.
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2024-10-03 07:14 AM
Pink indicates bad quality.
In this case the pink is indication bad animation references. The OPC Paths in the objects' animations are referring to something that does not exist. You also have value displays that say ***Error*** for the value so same thing. You also are missing one or more embedded mimics. The white box with a red X in it should be displaying an object.
If you restored this mimic in a different location than the one it originated in it is possible that the objects that your mimic is trying to reference could exist and you could correct the OPC Paths. The missing Embedded mimic could simply be something you drag and drop back in but if it requires some animations to be added to it to display its functionality then you'll have to figure that out.
Also any objects that have pick actions set on them are likely to need correcting.
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2024-10-04 03:36 AM
Someone please help me with suggestion to how remove this error. Otherwise i have to develop again the whole backup.
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2024-10-04 07:12 AM
You either have an incomplete backup that you imported (restored) and will have to recreate the missing objects, or you imported that graphic into the wrong location so all its references are bad and you need to import it in the correct location.
If you look at the animations of one or more of the pink objects you'll see the reference path it is expecting the object it is referencing to be, usually references to an object will also include a parameter of the database object something like "Station1.Pump1.Speed.CurrentValue where current value is the parameter. It is most likely that the Main 1 mimic is using relative references, which means the reference path is relative to the mimics location in the database, and not the absolute path from the root of the database.
If the objects actually exist in the database you should be able to go find where the really are and then be able to figure out where the Main 1 mimic backup should be imported.
Watch the YouTube videos on Geo SCADA and reference the Geo SCADA help so you can better understand how Geo SCADA works. https://community.se.com/t5/EcoStruxure-Geo-SCADA-Expert/YouTube-playlist-for-our-Ecostruxure-Geo-SC...
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2024-10-24 04:41 AM
Was Adam's suggestion the answer?
i.e. if you export config from location X.Y, and your configuration has relative references to items outside the export (e.g, references to A, A.B or X) then import into a different folder or level (e.g. C or D.E) then the import won't find these outside references.
It's best to name an SDE file by the full name of the group, then you know where to import it to. e.g. if you export "East.RTU.Points" group, then place your cursor on "East.RTU" and import to that parent in order to get back what you exported.
Link copied. Please paste this link to share this article on your social media post.
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.