Find out if AC450 signals is on any displays
A customer has many (30) AC450.
They have several system (5.0 and 5.1).
The 5.0 system only needs some signals from one AC450 for example PS10, but they have uploaded every signal from that AC450.
Now they want to know how many and the name of the signals used in graphics displays.
Can this be done or must they manually check the references for every signal or if i export one AC450 (PS10) with dependencies the export would contain the displays containing signals from that AC450?
No, exporting the AC450 control structure wont give you what you need. The cross reference information your customer wants comes from the graphic display and graphic element aspects, not the controler object properties. Most of the customer graphic displays will not be in the controller object structure.
With PG2 graphics, you can create display documentation from the Graphic Builder that includes all the aspects used in a graphic, including the AC450 controller signal graphic aspects. This will tell you what data points are on that display.
This customer uses VB6.
Does a signal in control structure have a special aspect if it is used in a display?
Every signal contains a faceplate regardless if it's used/not used in a display.
Is there any way to read a file that contains the name/guid to signals used in display?
Or is it just to manually check references for each signal?
No, there is no special aspect that tells you where data from an object is used.
Simple answer.. "No, there is no tool to tell you where all your objects apear in a graphic"
Longer answer... Its not impossible. If there isnt already a tool out there somewhere then, well, it depends how much of a VB hacker you are....
I dont have access to a system with VB6 installed right now so I cant give you exact details of how it would work but basically Yes, "in theory" you could use a VB6 program to open the VB6 source files in the OperateITData/graphics cache and read the code looking for references to AC450 graphic elements. These will contain either an object name or an object GUID which you can use to identify the data source.
Another alternative might be to write a VB extension to the VB6 Graphics builder and search for object references ( actually this might be an easier solution )
But this would take some considerable work (like a couple of weeks for someone who already knows what to do) and may not be worth the effort. How important is this to your customer ? Why do they really need the data ? If it is just for tag license counts then there may be better ways to deal with the problem.