Applies To:
  • CitectSCADA 5.31, 5.40, 5.41, 5.42, 5.50, 6.0, 6.1, 7.0
  • CitectHMI 5.31, 5.40, 5.41, 5.42, 5.50, 6.0, 6.1, 7.0
  • CitectFacilities 5.31, 5.40, 5.41, 5.42, 5.50, 6.0, 6.1, 7.0
  • CitectSCADA Batch 5.31, 5.40, 5.41, 5.42, 5.50, 6.0, 6.1, 7.0
  • CitectSCADA Pocket 5.31, 5.40, 5.41, 5.42, 5.50, 6.0, 6.1, 7.0
Summary:

I modified my template and then run 'Update Pages' and now all my animation numbers have changed. How do I avoid this happening? 

Solution:

You should reserve animation points when you create templates.

For example, you have a template1 with objects which are given AN 205, 206 and 207.

When you create template2 based on template1 the objects will keep AN 205, 206 and 207 in template2. There will also be a group created with the next free AN, in this case AN 208 which includes all the objects on template1. Any new objects placed on template2 will be given the next free AN.

Problem 1

Then if you go back to template1 and add an object (lets call it object1) it will take the next free AN on the page, in this case AN 208. The problem is that AN 208 is already used on template2 so when you do update pages, object1 on template2 will have a different AN from object1 on template1 because CitectSCADA will see an animation number conflict and will change some ANs to fix the conflict.

To avoid this problem you should reserve ANs when you first create template1 and use those reserved ANs when you go back and add things to the template later on. You should also reserve ANs on template2 in case you need to come back to it later and add some objects to it.

To be able to reserve ANs in the graphics builder you need to go to Tools | Options and tick "Show version 3.xx/4.xx tools".

Problem 2

You need to be careful not to free an AN without using it because when you do this the AN becomes the first free AN for all the pages based on that template so they will use it. Then you will have animation conflicts between your pages and when you run 'Update Pages' CitectSCADA will have to modify your ANs to fix the problem. This can cause issues if you are using functions which do things at specific ANs (AlarmDsp() for example).

 

If you have accidentally created some animation number conflicts and you have different animation numbers for the same object on your template and on your page using the template, you can fix this by temporarily making all your templates and pages based on the Normal/Blank template. Then go back to your templates and pages one by one and put them back to the correct configuration. You need to do this in the right order though: Start with template1 and then template2 which is based on template 1 etc… 
Keywords:
 

Attachments