Rockwell Automation 1203-SM1 SLC to SCANport Communication Module - Manual (Page 57)

Appendix
A
Publication 1203–5.9 –– October 1996
M0, M1, and G Files
This appendix provides information about M0–M1 files and G files.
The information is general in nature and supplements specific
information contained in earlier chapters of this manual. Topics
include:
•
M0–M1 files
•
G files
The SLC to SCANport module is considered to be a specialty I/O
module.
M0 and M1 files are data files that reside only in specialty I/O
modules, such as the SLC to SCANport module. There is no image
for these files in the processor memory. The application of these
files depends on the function of the particular specialty I/O module.
The M0 file is a module output file (a write only file), and the M1
file is a module input file (a read only file).
M0 and M1 files can be addressed in your ladder program and they
can also be acted upon by the specialty I/O module, independent of
the processor scan. Keep the following in mind when creating and
applying your ladder logic.
Important: During the processor scan, the ladder program can
address M0 and M1 data with bit, word, or file
instructions. Each time an M0–M1 file address is
encountered in the program, an immediate data transfer
to or from the specialty I/O module occurs. The impact
these immediate data transfers have on processor scan
time is described in appendix A of the Advanced
Programming Software User Manual, Publication
Number 1747–6.4.
Configuring M0–M1 Files Using APS Software
M0 and M1 files are configured as part of the I/O configuration
procedure for the processor file. After you have assigned the
specialty I/O module to a slot (the procedure is the same as assigning
other modules), the following functions are displayed at the bottom
of the APS screen:
ONLINE
CONFIG
F2
MODIFY
RACK
F4
MODIFY
SLOT
F5
DELETE
SLOT
F6
UNDEL
SLOT
F7
EXIT
F8
SPIO
CONFIG
F9
READ
CONFIG
F1
Appendix Objectives
"
M0–M1 Files