M0/M1 Monitoring Option Enabled; Transferring Data Between Processor Files And M0 Or M1 Files - Allen-Bradley 1747-SN User Manual

B–4 M0–M1 Files and G Files
Publication 1747 6.6 - July 1996

M0/M1 Monitoring Option Enabled

Important:
This option is not supported by the SLC 5/02 processor.
The SLC 5/03 and SLC 5/04 processors allows you to monitor the
actual state of each addressed M0/M1 address (or data table). The
highlighting appears normal when compared to the other processor
data files. The processor's performance will be degraded to the
degree of M0/M1 referenced screen data. For example, if your
screen has only one M0/M1 element, degradation will be minimal.
If your screen has 69 M0/M1 elements, degradation will be
significant.

Transferring Data Between Processor Files and M0 or M1 Files

The processor does not contain an image of the M0 or M1 file. As a
result, you must edit and monitor M0 and M1 file data via
instructions in your ladder program. For example, you can copy a
block of data from a processor data file to an M0 or M1 data file or
vice versa using the COP instruction in your ladder program.
The COP instructions below copy data from a processor bit file and
integer file to an M0 file. For the example, assume the data is
configuration information affecting the operation of the specialty I/O
module.
First scan bit. It makes
this rung true only for
the first scan after
entering Run mode.
The COP instruction below copies data from an M1 data file to an
integer file. This technique is used to monitor the contents of an M0
or M1 data file indirectly, in a processor data file.
COP
S:1
COPY FILE
] [
Source
15
Dest
Length
COP
COPY FILE
Source
Dest
Length
COP
COPY FILE
Source #M1:4.3
Dest #N10:0
Length
#B3:0
#M0:1.0
16
#N7:0
#M0:1.16
27
6