Good day,

I'm working on a PCS7 V9.1 project with WinCC V7.5 SP2 Upd6. For some of the tags I have the same block icon on 2 different pictures (hierarchy locations). Obviously I hade to manually insert one of the bock icons without the "@" in the Type field of the object. This allows me to do a OS compile without losing the block icon that is not in the same hierarchy as the CFC for this tag.

Here is my problem: When I use the Point function in WinCC runtime or other similar build in functions,  It doesn't always go to the page where the block icon was automatically generated. It sometime jumps to the block icon I manualy inserted.

I am aware that I can change the entry point picture in "Component List Editor", but this takes very long to manually update each picture. Also this looses the Object name which takes even more work to fix.

1. How can I force the "Entry point picture" to be the picture in the same hierarchy as the one where the block icon was generated automatically (I.e. the hierarchy folder of the CFC)?
2. Is it possible to export the component list editor, fix all the "Entry point pictures" in Excel and then import it again?

Thanks in advance

Hi Acron,

A sugestion, not sure if it will help.

Each block icon has the parameter "Relevant", with makes alarms appear in the alarm tree (Picture Tree). May be this parameter influence also the loop in alarm function.

So, in your manual added block icon set the parameter "Relevant" to "no".
Afterwards, compile your project.

Let us know if it worked.

Regards,
Cedric

Molthoff

Hi Acron,

A sugestion, not sure if it will help.

Each block icon has the parameter "Relevant", with makes alarms appear in the alarm tree (Picture Tree). May be this parameter influence also the loop in alarm function.

So, in your manual added block icon set the parameter "Relevant" to "no".
Afterwards, compile your project.

Let us know if it worked.

Regards,
Cedric

 Thanks Cedric, I will test this and let you know if it works

Hi, 

Yes, "Group relevant" feature will definitely work. However, the alarm did not show on the group display. 

I was exploring to change the graphics pdl name to trick the AS-OS engineering system, by changing the PDL name to arrange in the front instead of the back. However, this is still under testing.

Another method is changing the tagname attribute, adding "Server Prefix" in front. For example, if the tag name is 123PT1234/MonAnL , then i will add SERVERPREFIX::123PT1234/MonAnL at the duplicated block icon to trick the AS-OS engineering. 

Last resort is, changing directly at component list editor in WinCC Explorer. 

Hope this helps.  

JazTai

Hi, 

Yes, "Group relevant" feature will definitely work. However, the alarm did not show on the group display. 

I was exploring to change the graphics pdl name to trick the AS-OS engineering system, by changing the PDL name to arrange in the front instead of the back. However, this is still under testing.

Another method is changing the tagname attribute, adding "Server Prefix" in front. For example, if the tag name is 123PT1234/MonAnL , then i will add SERVERPREFIX::123PT1234/MonAnL at the duplicated block icon to trick the AS-OS engineering. 

Last resort is, changing directly at component list editor in WinCC Explorer. 

Hope this helps.  

 Hi JazTai,

Thanks for your suggestions. I was hoping to find an easier way to do this. After some testing I have decided to make the changes in component list editor. The other solutions all seems to give my more problems. The component list editor solution is not ideal because I loose the object name in component list editor and it is time consuming.