Message severities, Audiences, Message severities -4 audiences -4 – Rockwell Automation FactoryTalk View Machine Edition Users Guide User Manual
Page 166

F
ACTORY
T
ALK
V
IEW
M
ACHINE
E
DITION
U
SER
’
S
G
UIDE
10-4
• •
•
•
•
Choose not to log messages
Message severities
FactoryTalk View categorizes messages in four severities:
Errors indicate that a process or action has failed. For example, a tag’s value could not
be written, or a user typed the wrong password while logging on to the system.
Warnings indicate that a process or action might not function correctly, or might
eventually fail if preventive action isn’t taken. For example, if an ActiveX
®
control
used in a graphic display is a different version than the one installed on the run-time
computer, a warning is logged to indicate the mismatch. Mismatched ActiveX
controls might not behave as expected at run time.
Information indicates that a process or action has completed successfully. For
example, a user logged on to the system or a tag value has been written to the data
source.
Audit indicates that the system configuration has been changed. FactoryTalk View
records the creation, modification, and deletion of components (such as graphic
displays) as audit messages.
Other Rockwell Automation products also use audit messages. For example, if you set
up an audit log in FactoryTalk AssetCentre, FactoryTalk View’s audit messages will
be sent there, as well as to FactoryTalk Diagnostics.
In the FactoryTalk Diagnostics Viewer, the message severity is shown in the Severity
column, indicated by the ! symbol.
The content of the messages is provided by the system—you don’t need to do anything to
set up message content.
Audiences
FactoryTalk Diagnostics allows messages to be categorized differently for the various
people for whom the messages are relevant. You can sort the messages in the FactoryTalk
Diagnostics Viewer, so that those relevant to a particular person are grouped together.
Who receives which messages?
You can specify which types of messages are sent to the Operator, Engineer, and
Developer audiences.
If messages of a particular category are not routed to any destination, the messages for that
category are not logged. For example, you might not want to log information messages, or you
might not want to send any messages to the Operator.