Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

Scripts run more than once by a tag triger

Created by: Mehrnoosh at: 7/25/2006 12:27 PM (5 Replies)

Rating (0)

Thanks 0

6 Entries

7/25/2006 12:27 PM	Rate (0)
Mehrnoosh Posts: 102 Rating: (9)	Dear friends I have a problem with global actions in different WinCC projects in different machines. When I set a tag trigger for an action, it runs more than once by each change of the tag. For example I have written an action (I defined in under server actions not under global action) to save a tag (text 8 bit character set) in user archive and set this tag as the trigger of the action. But for each change of the tag I have more than one row in my table in user archive! Please help me to figure out the problem. I use WinCC 6 SP3 hotfix 2 and I wrote actions in C, but I had the same problem with SP1.
Mehrnoosh Posts: 102 Rating: (9)
Suggestion To thank Quote Answer

7/25/2006 12:51 PM	Rate (0)
Ikkezelf Posts: 1084 Rating: (72)	Hi, Please read thisThread. Several ideas are being discussed for the same problem as yours. The solution to this problem was the server action / global action, but you have set ik oke. But when you read it you can use the ideas to find out in which part your problem resides. with regards, Ikkezelf
Ikkezelf Posts: 1084 Rating: (72)
Suggestion To thank Quote Answer

7/31/2006 7:48 AM	Rate (0)
Mehrnoosh Posts: 102 Rating: (9)	Hi I have already put some "printf" command in the code to see, what the value of the triger tag is. I have more than 1 row printed by each change of the tag. The value which is printed is the same for each row!
Mehrnoosh Posts: 102 Rating: (9)
Suggestion To thank Quote Answer

7/31/2006 9:41 AM	Rate (0)
Salma Gold Member Joined: 9/27/2005 Last visit: 11/27/2007 Posts: 1398 Rating: (149)	So does this mean that you script is running multiple times ? You don't say if your printf statements are in a loop or not. Assuming they are not, this shows that your script is being triggered multiple times. You could try changing the trigger to an internal boolean tag and see what happens.

Suggestion To thank Quote Answer

7/31/2006 12:31 PM	Rate (0)
Mehrnoosh Posts: 102 Rating: (9)	Hi I do not have this problem when my triger tag is an internal tag. Thanks, Mehrnoosh
Mehrnoosh Posts: 102 Rating: (9)
Suggestion To thank Quote Answer

8/3/2006 10:28 AM	Rate (0)
Salma Gold Member Joined: 9/27/2005 Last visit: 11/27/2007 Posts: 1398 Rating: (149)	Ah, interesting ! This sounds to me like you are polling the tag too fast. Remember you should set tag poll rates to realistic values and usually never use Upon Change for PLC tags. What poll have you used for the trigger tag? Please try setting it to 2 seconds and see if this makes a difference.

Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on