Cop Operation Status Values; Copying To A Different Data Type - Allen-Bradley Micro800 General Instructions Manual

Chapter 13
Data manipulation instructions
COP Status value
0x00
0x01
0x02
0x03
0x04
0x05
0x06
0x07
0x08
0x09
0x0A
304

COP operation status values

The following table describes COP operation status values:
Status description
No action taken (not enabled).
COP function block success.
Destination has spare bytes when copying from String.
Source data are truncated.
Copy length is invalid.
Data type mismatch when there is String Data type as either source or destination.
Source data size is too small for copy.
Destination data size is too small for copy.
Source Data offset is invalid.
Destination Data offset is invalid.
Data is invalid in either source or destination.

Copying to a different data type

When a copy to or from a String data type is performed, the ODVA short String format is used for data in the USINT array.
When COP is used between any other pair of data types, the copy operation is valid, even if the data type in the source is not
the same as the data type in the destination, and even when they are not in a valid format. The logic must be validated at
the application level.
From a USINT array to a String array
To copy a USINT array to a String array, the data in the USINT array must be in this format:
• Byte1: Length of first String
• Byte2: First Byte Character
• Byte3: Second Byte Character
• Byte n: Last Byte Character
• Byte (n+1): Length of second String
• Byte (n+2): First Byte Character for second String
• Etc.
Rockwell Automation Publication 2080-RM001D-EN-E - February 2015