AlmDefErr in controller log
After deleting 2 tags being transfered with MMS, we got some strange messages in controller log. Does the AlmDefErr B-43-UA-MMS-PAS fbAlarm messages mean that something is wrong with the MMS setup? 800xA system: 800xA SV5.1 RevD, FP4
I 2015-08-16 09:38:30.133 Create applications definition domain
I 2015-08-16 09:38:40.192 Create controller configuration domain: DTTargetSystemDomain34720136
I 2015-08-16 09:38:40.760 Controller Config downloaded from: 172.16.36.71, (build version: 5.1.1200.6)
I 2015-08-16 09:38:40.764 New I/O-connections configuration.
I 2015-08-16 09:38:41.228 I/O-connections configuration waiting for application/s.
I 2015-08-16 09:38:41.461 Create application instance domain: R538396221P23_2
I 2015-08-16 09:38:49.449 Create application R538396221P23_2
I 2015-08-16 09:38:50.274 Application downloaded from: 172.16.36.71, (build version: 5.1.1200.6)
I 2015-08-16 09:38:53.767 Stop and restart application R648775955P23_2 as R538396221P23_2
I 2015-08-16 09:38:54.310 I/O-connections configured.
W 2015-08-16 09:39:04.359 The Idle thread has executed less than 1%.
E 2015-08-16 09:38:56.902 Unit= _SWFirmware P223 1010 Lost event notif to 172.16.124.24:22
E 2015-08-16 09:38:56.902 Unit= _SWFirmware P223 1010 Lost event notif to 172.16.124.23:22
I 2015-08-16 09:38:54.933 Unit= _SWFirmware P223 1011 AlmDefErr B-43-UA-MMS-PAS fbFault
I 2015-08-16 09:38:54.934 Unit= _SWFirmware P223 1011 AlmDefErr B-43-UA-MMS-PAS fbAlarm
I 2015-08-16 09:38:54.934 Unit= _SWFirmware P223 1011 AlmDefErr B-43-UA-MMS-PAS fbWarning
W 2015-08-16 09:39:21.042 A/E Burst: Prevented 1 alarms & events from being printed in the log, refer to an OPC AE client for more info.
Voted best answer
The first character is "I" for information. ( similarly you can see other E error and W warning messages )
Likely this message just says "something happened" when you removed the MMS transfer and can be safely ignored.
In any case, the message relates to alarm definition - not MMS transfer - and does not indicate an MMS configuration error.
This alarm definition failed error (code 1011) appears when a new alarm condition can't be created, may be because of invalid parameter (say empty string on the name). In such case, controller generates system simple event.
Yes, it is quite interesting for me to read through all details. If I come across any other details, I will post here.
In addition, please go through this content. I found it from online help. So please make sure the Source Name and Condition Name are unique (and valid):
The combination of condition name and source name must be unique throughout the entire control network. Trying to define a non-unique combination of source name and condition name in a controller will set the Error parameter to True and set the status code to -710, cErrUniqueName. Also, a system event named Alarm definition failed is generated.
The uniqueness of the combination of condition name and source name throughout the entire control network is also checked by the OPC Alarm and Event Server(s). If two non-unique alarms are active simultaneously, a system simple event is generated in the OPC Alarm and Event Server.
Please note that there is no check between different controllers, and the functionality of duplicate alarms within the control network is not predictable. However, when an OPC server detects two alarms with the same source name and alarm condition, a simple event is generated.