User manual

Publication CNET-UM001C-EN-P - November 2005
Produce and Consume Tags (Interlock Controllers) 5-5
Organize Tags for Produced
or Consumed Data
This table describes the guideline to follow as you organize your tags for
produced or consumed data (shared data).
Table 5.2 Guidelines for Produced or Consumed Data Tags
Guideline Details
Create the tags at the controller
scope.
You can only produce and consume controller-scoped tags.
Produce and consume specific
tags.
You cannot produce or consume the following tag types:
• Alias
• Axis type
• BOOL
• Consumed
• I/O
• INT
• Message
Use one of these data types:
• DINT
• REAL
• array of DINTs or REALs
• user-defined
• To share other data types, create a user-defined data type that contains the required data.
• Use the same data type for the produced tag and corresponding consumed tag or tags.
Limit the size of the tag to ≤ 480
bytes.
If you must transfer more than 480 bytes, create logic to transfer the data in smaller packets or create
multiple produce/consume tags.
To share tags with a PLC-5C
controller, use a user-defined
data type.
To This Then
produce integers, BOOLs or
combinations of
both
Create a user-defined data type that contains an array of INTs
with an even number of elements, such as INT[2].
only one REAL value Use the REAL data type.
more than one REAL
value
Create a user-defined data type that contains an array of REALs.
consume integers Create a user-defined data type that contains the following
members:
Data type Description
DINT Status
BIT 0 = 0 PLC5 in PROG mode
= 1 PLC5 in RUN mode
INT[x], where x is the output
size of the data from the PLC-5C
controller. (If you are consuming
only one INT, omit x.)
Data produced by a PLC-5C
controller
Use the highest permissible RPI
for your application.
If the controller consumes the tag over a ControlNet network, use a binary multiple of the ControlNet
network update time (NUT). For example, if the NUT is 5 ms, use an RPI of 5, 10, 20, 40 ms.