AlarmVector tag TagName has case mismatch - TAGNAME is in AlarmVector table
The AlarmVector table in Conductor NT is checked for case variants.
The case usage of the entry in the AlarmVector table in Conductor NT must be uppercase, as Unix is case-sensitive but Microsoft Access is not.
Because the uppercase tagname exists, the non-uppercase entry should be deleted (after you verify that it is calling up the same graphic as the uppercase one). It is being ignored anyway, but alarm vectoring is working because an uppercase version of the tag is in the table.
CT22-288A gms graphic:2500 CT22D-121A gms graphic:2700 <== CT22E-040 gms graphic:2281 ... ZT35Q-047 gms graphic:5936 ct22d-121a gms graphic:2700 <== di23-000 gms graphic:2282
To trigger block 2700, CT22D-121A, (the one in capital letters), must be present. The gms ct22d-121a, (lower case letters), is ignored. When the lower case gms is the only one present for a particular block number, the block will not trigger. If the capital and lower case instances do not trigger the same block, the upper case one will take effect, but the lower case one will not, so the block attached to it will not trigger.
This message is likely to show an error in the system configuration. It should be reviewed. The issue raised may be in unused logic or graphics, or have other realities that make it a non-issue.
Please contact us for help resolving your error messages.
DBDOC ©1996 - 2021 G. Michaels Consulting Ltd., all rights reserved. All other trademarks and registered trademarks are the property of their respective holders. Website source largely available under the terms of the AGPLv3.