How local messages work, How local messages work -28 – Rockwell Automation FactoryTalk View Machine Edition Users Guide User Manual
Page 330
F
ACTORY
T
ALK
V
IEW
M
ACHINE
E
DITION
U
SER
’
S
G
UIDE
19-28
• •
•
•
•
The data source is set up to exchange information (in the form of numeric or string values)
between FactoryTalk View and the machine that your application is controlling.
Identify the tags and values to monitor
To set up local messages, determine which tags associated with machine processes to
monitor, and identify the values for those tags that will trigger local messages.
For information about creating HMI tags, see Chapter 7.
How local messages work
These are the key parts of the local message system:
Local message files—text files containing lists of messages, with a numeric trigger
value for each message
Local message display object—a graphic object that shows local messages when the
Value connection assigned to the object matches a message’s trigger value
Value connection—a tag or expression. When the value of this connection matches a
message’s trigger value, the local message display object shows the associated
message.
The local message display object always appears in the graphic display it’s placed in,
whether or not there is a message to show. However, the operator does not see the
message unless the object is located in the display the operator is currently viewing.
The following example shows how the key parts of the local message system work
together.
Example: Show local messages
This example shows how to notify the operator of the status of a hoist.
1. Create a tag called Hoist_Status. This tag points to an address in a programmable
controller that is linked to sensors on the hoist. The tag has five possible values:
The tag has this value
When the hoist has this status
1
At bottom
2
Raising
3
Stopped between the top and bottom
4
Lowering
5
At top