Rockwell Automation 5730 DriveLogix5730 Controller for PowerFlex 700S Drives with Phase II Control - Manual (Page 154)

7-14 Communicating with Devices on a ControlNet Link
When the DriveLogix5730 controller initiates messages to PLC or SLC
controllers, you do not have to map compatibility files. You enter the data
table address of the target device just as you would a tag name.
SLC 5/05 controllers, SLC 5/04 controllers (OS402 and above), and SLC 5/
03 controllers (OS303 and above) support logical ASCII addressing and
support PLC/SLC mapping (see the examples above). For all other SLC or
MicroLogix1000 controllers, you must map a PLC-2 compatibility file (see
the PLC-2 examples above).
Producing and Consuming
Data The DriveLogix5730 controller supports the ability to produce (broadcast)
and consume (receive) system-shared tags over a ControlNet link. Produced
and consumed data is accessible by multiple controllers over a ControlNet
network. Produced and consumed data are scheduled connections because
the controller sends or receives data at a predetermined RPI rate.
Produced and consumed tags must be controller-scoped tags of DINT or
REAL data type, or in an array or structure.
The producer and consumer must be configured correctly for the specified
data to be shared. A produced tag in the producer must be specified exactly
the same as a consumed tag in the consumer.
If any produced/consumed tag between a producer and consumer is not
specified correctly, none of the produced/consumed tags for that producer
and consumer will be transferred. However, other consumers can still access
their shared tags, as long as their tags are specified correctly. One consumer
failing to access shared data does not affect other consumers accessing the
same data.
PLC-5 reads from DriveLogix5730
SLC reads from DriveLogix5730
SLC 5/05
SLC 5/04 OS402 and above
SLC 5/03 OS303 and above
source tag “array_1”
destination element N7:10
The PLC-5, PLC-3, and SLC controllers support logical ASCII addressing so you do not have to
map a compatibility file for MSG instructions initiated by a PLC-5, PLC-3, or SLC controller. Place
the DriveLogix5730 tag name in double quotes (“).
You could optionally map a compatibility file. For example, if you enter 10 for the compatibility file,
you enter N10:0 for the source tag.
PLC-2 reads from DriveLogix5730 source tag 200
destination element 010
The source tag is the three-digit PLC-2 address you specified for PLC-2 mapping.
Type of MSG Instruction: Example Source and Destination:
Tag type: Description: Specify:
produced These are tags that the controller produced for
other controllers to consume. Enabled for producing
How many consumers allowed
consumed These are tags whose values are produced by
another controller. Controller name that owns the tag that the local controller wants
to consume
Tag name or instance that the controller wants to consume
Data type of the tag to consume
Update interval of how often the local controller consumes the tag