Chapter 5
Addditional and Advanced
Programming Techniques
5-10
Figure 5.1
Verifying Another Machine Accepts the Data Type You Want to Use
another vendor's MAP device
OSI Network
Allen-Bradley OSI Coprocessor
another vendor's MAP device
You can use the DTYPE
parameter in your
command line...
def :c6'ven' t "xxx" dt "f8:0,1"
...to verify that
another vendor's
machine accepts a
particular data type.
I - 12427
For example:
def :c6’other_vendor_var’ t ”xxxx” dt ”f8:0,12”
In the example above, we are defining the variable as address ”xxxx”.
With the added DTYPE parameter, we are specifying that we want an
array of 12 floating points to be used as the data type. If the data type is
not acceptable, we will receive an error message right away. If we had not
used DTYPE here, we would have had to use the MMS named variable
within a MOVE command line before knowing the data type was
unacceptable.
When you define an MMS named variable using the DEFVAR command
(see chapter 4), you also define the scope of that variable. A variable can
have one of three scope types:
VMD–specific
application association (AA)
domain
Important:
Domain variable scope is only supported by the OSI
coprocessor as a client, not a server. Therefore, you can specify all three
domain types in client–type applications, but only VMD and AA scope
will be accepted by server applications. For example, you can define
MMS named variables with VMD–specific and AA scope in the OSI
coprocessor, but not domain scope. You can, however, define MMS
Defining the Scope of an
MMS Named Variable (using
DEFVAR)
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...