"Cicode type mismatch" Hardware Alarm Context?

G'day Nick,

Try this setting in the citect.ini file:
[Debug]EnableHardwareAlarmLogging

Really handy for tracking down hardware alarms. I believe we added it in 2018 version.

Looks like you are using older version of Citect , so you might not be able to use '[Debug]EnableHardwareAlarmLogging' in citect.ini..

Can you reproduce the hw alarm?
- for example when pressing a button, changing pages or the like in order to be able to trace what is causing the hw-alarm.
"Cicode type mismatch" that appear are due to tag type mismatches made somewhere. 
** VAL = TAG1-TAG2 will show the error if any of them are of different type (Int, String..)

Thanks Brad, unfortunately this site is running version 2015

The alarm just seems to stay on, it's not turning off. Usually when I've seen it (years ago when I still used Citect), it goes away after a short period, then comes back as you say, when clicking buttons or whatnot. But this time, it doesn't seem to be following the same process.

Regardless, it sounds like it's not possible to get the context from Citect itself in the version this customer has, and that trial and error must be used to locate the error? Sounds exciting