[Imported] Mimic parameter manipulation


[Imported] Mimic parameter manipulation

>>Message imported from previous forum - Category:ClearSCADA Software<<
User: josh, originally posted: 2019-05-23 00:49:39 Id:431
I'm a new user (I have done L1 training) and one thing that is annoying me is setting up parameters.
Considering you'd might want to create groups of parameters that match the database hierarchy to easily animatemimics. Being able to copy and paste and move groups around would be much more convenient than having to type in everything manually. This is all assuming I'm not missing anything obvious!


Re: [Imported] Mimic parameter manipulation

>>Responses imported from previous forum

Reply From User: ROVSCADAENGINEER, posted: 2019-05-23 01:45:44
There are groups of mimics you can create called templates which can be referenced. you basically configure the Templates with the set point and animation configurations you like. you can then create "instances" of that template group.

I think this is a way to do what you are thinking of.


Reply From User: hardin4019, posted: 2019-05-23 13:03:59
I can't recall whether it was L1 or L2 training, but one of them does cover how to use the parameters of the mimic itself or its parent group, or points to make different things happen in your mimics.

One example would be at the bottom of a mimic I have the name, but it is automatically populated with the .ObjDisplayName of the group that contains the mimic. Its an animation for "Value" and looks like ('Block Valve ' + ".objDisplayName") just get rid of the ( ). The singe ' ' will make the mimic display string text and the " " is a database item, with the + in between to combine the whole thing into a single line.

One of the more complex things I have done recently is I have 2 different valve templates, one valve template contains a group called '.Comms' with the outstation in it. The other valve template doesn't have the '.Comms' group and all of the points are pointed to an outstation in a different valve instance.

So I wanted to show the users the status of the outstation in the second valve template where the is no '.Comms' group and make it look like it was there. I have a point in the valve group called UpstreamPSI, and it is pointed to the outstation I want to know the status of in this template. So I used ( ["UPstreamPSI.SourceName" + '.StateDesc'] ) note the ( ) are not necessary but the [ ] are required. This Automatically pulls the full outstation location in the database from the UpstreamPSI as a string of letters, then adds the '.StateDesc' to the end. Note that the "UpstreamPSI.SourceName" is in " " and is a database parameter, and in this case the '.StateDesc' is a string this time.

Second trick in the same situation. The second valve template without the ".Comms" group doesn't give me the 3 or 4 other RTU health status points I pull for a valve the does have the '.Comms' group. I played around and came up with a not totally automatic, but workable solution. If I go into the valve Group and put the path of the other valve Group into the .objKeywords2 parameter, I can use it in my mimics to point the mimic at points in another group entirely. IE, I have the .DCVolts point in the same valve the valve group that has the outstation. So in the second Valve's mimic I have a box with ( [".objKeywords2" + '.DCVolts.CurrentValue'] ). Again, you don't need the ( ) but you do need the [ ]. This automatically takes the path of the group that contains the DCVolts point that I had saved in the .objKeywords2 group parameter and adds the string .DCVolts.CurrentValue together and makes it a full path to a Database item and then allows the mimic to show the value.