Greetings.
I am experiencing difficulties using Tag Triggers to control object animation.
I already have a case number processing at Siemens tech support, but the timescales on my current project are a little tight...

I am attempting to replace an existing SCADA package / project with a 'new and improved' version under WinCC.
The existing SCADA uses Bits from multiple status Words to controll almost every aspect of the animation. My problem is that thestatus ofany given Bit mustcontrol / trigger the animation.
I have been guided in the right direction with regard to correctly addressing the relevant Bits.
The first-defined Tag Word in the scripts I create triggers the script whenever it's value changes, even if the 'new' value has no bearing on the animation (and hense does nothing).Any Tags defined after the first do not trigger the script when their values change, even if the 'new' value would alter the graphic (colour change, visibility or whatever).
Siemens have suggested using cyclic triggers, but unless I am missing something simple, that would mean having to run a script which checked thousands of bits every scan.

Can anyone help?

Here is the script that controls the visibility of an object (on or off). The originalattempt was created by converting a simple bit state dynamic to 'C' and modifying it. Thisscriptwas provided from Tech Support.
TAG_1 is a status word containing actual plant device states.
TAG_2 is a status word containing PLC control states.

As a side note, if I only have to use different Bits from the same Word (i.e. only define one Tag), everything works fine.

----------
#include "apdefap.h"
BOOL _main(char* lpszPictureName, char* lpszObjectName, char* lpszPropertyName)
{
// WINCC:TAGNAME_SECTION_START
// syntax: #define TagNameInAction "DMTagName"
// next TagID : 2
#define TAG_1 "DDEI_020_02_V01_SW"
#define TAG_2 "DDEI_020_02_V01_WW"

DWORD dwtag1,dwtag2;
BOOL hb;

dwtag1=GetTagDWordWait(TAG_1);
dwtag2=GetTagDWordWait(TAG_2);

if (( (dwtag2 & 0x1)) | (( (dwtag1 & 0x1)) && ( ! (dwtag2 & 0x1)) &&
(dwtag2 & 0x2))) return 65535;

else return 0;
}
----------

The object isthe 'Energised'state for a valve. The code for 'De-energised' isn't much different.

--On--
if (( (dwtag2 & 0x1)) | (( (dwtag1 & 0x1)) && ( ! (dwtag2 & 0x1)) &&
(dwtag2 & 0x2))) return 65535;
else return 0;
--

--Off--
if (( ! (dwtag2 & 0x2)) | (( ! (dwtag1 & 0x1)) && ( ! (dwtag2 & 0x1)) &&
(dwtag2 & 0x2))) return 65535;
else return 0;
--

The code is in the 'Dynamic' control entry for the Visibility of the object. I'm not sure what you mean by 'connect' the tag trigger. Have I done (or omitted to do) something that connects one tag but not the other?