Chapter 3
MMS and Your Coprocessor
3-19
- arrays of arrays are never allowed.
This section covers MMS object management operations, including:
retaining MMS objects in non–volatile memory
saving MMS objects to, and restoring them from, DOS files
information on MMS named variables that always exist in the OSI
coprocessor
Retaining MMS Objects
You can retain the following MMS objects in the OSI coprocessor’s
non–volatile memory:
domain
program
invocation
named
variable
named variable list
named
type
To retain MMS objects in non–volatile memory, you set the Retain MMS
Objects parameter through your Allen–Bradley MAP Station Manager.
This parameter instructs the OSI coprocessor to retain MMS objects on a
continuous basis:
If the
Retain MMS Objects
parameter is set to:
Then:
No
MMS objects are not being saved. Only default
objects will exist if there is a power failure or reset.
Yes
your MMS objects are saved to non-volatile
memory continuously. If the coprocessor is reset or
power is lost, the MMS objects are retained, and
are then restored during powerup processing.
Note that your OSI coprocessor stores the MMS object reference only. No
values associated with the object are saved by the OSI coprocessor.
The restored set of MMS objects remains stored until you do one of the
following:
perform
the
Use Default MMS Objects action via the Allen–Bradley
MAP Station Manager
Important: When default MMS objects are restored, the OSI coprocessor
aborts all connections and resets itself after completing the restoration.
restore a new set of MMS objects from a file
MMS Object Management
Summary of Contents for PLC-5 MAP/OSI
Page 1: ...PLC 5 MAP OSI Software User Manual Cat No 1785 OSI AB Parts...
Page 4: ...Table of Contents iii OSI Layer Management E 1...
Page 57: ...Chapter 4 Basic Programming Techniques 4 7 For example B7 6 10 AB Parts...
Page 91: ...Mapping MMS Data Types onto PLC 5 40 5 60 File Types Appendix A A 2 T ACC D 16 AB Parts...