Applies To:
  • CitectSCADA 5.xx, 6.xx
  • CitectHMI 5.xx, 6.xx
Summary:
On page entry, a hardware alarm is generated "Animation conflict AN83". How do I find the cause of this hardware alarm?
 

Solution:
There are many ways to resolve these types of problems, including some information found in KB's Q3870, Q3774, Q3307 and Q3156.

Below is a step by step guide of troubleshooting this hardware alarm, and finding the true cause. Before proceeding, please make a backup copy of the project or graphics page:

Step 1:
The best trick is to use the GoTo feature in Graphics Builder. You can also go straight to the AN by pressing Control-G in graphics Builder, then entering the AN number that was mentioned in the hardware alarm. If the AN does not exist, then a calling cicode function is expecting this AN to exist. Either create the AN, or modify the cicode. If still no luck with this GoTo tool in Graphics builder, proceed to the next step.

Step 2:
The next best approach is to reduce the scope of the problem - i.e. start by removing the template from the page.
Open the page in Graphics Builder. Remove the Template on the Graphics Page. To do this, go File -> Properties. Then go to the Appearance Tab:
Change the Style and Name to Standard and blank.

Step 3:
Compile and run the project. See if problem still persists - if yes, we can conclude that it is not caused by the template.

Step 4:
Next, we want to reduce the scope further by removing objects from the page. Open the page in Graphics Builder. Remove all objects on screen except for Cicode objects (likely cause of assigning functions/features to existing AN points) and Keyboard objects.

Step 5:
Compile and run the project. See if problem still persists - if yes, we can conclude that it is not caused by any objects on the page.

Step 6:
Most likely, the only objects left on the page are cicode objects and keyboard objects.
The most common cicode objects which assign properties based on AN numbers are the Alarm functions. I.e. AlarmDsp(), AlarmDspLast, etc.
Ensure that all arguments in these Alarm cicode functions are correct, and that any animation points required by the cicode actually exist.

Step 7:
Compile and run the project. See if problem still persists - if yes, please contact Citect Support for further assistance.
 
Keywords:
AN, Animation, Conflict, Hardware Alarm  

Attachments