Transferring template blocks – Rockwell Automation 5370 CVIM Communications Manual User Manual
Page 57

Chapter 4
Using the Remote I/O Link
(Node Adapter)
4–20
You must use the discrete I/O bits in conjunction with block transfers to
inform the CVIM module of the Block Transfer Type, Toolset Number,
Block Number and, Last Block by setting discrete bit information using
simple ladder programming (refer to Table 4.B):
•
Set bit 1 of output word 3 to indicate a CONFIGURATION block transfer.
•
Use bits 10 through 17 of output word 3 to indicate which block to
transfer. Refer to Appendix D for block numbers.
•
Set bit 3 in output word 3 to tell the CVIM to send the last block. If you
forget to set this bit, the CVIM module will wait for an indefinite period
of time for more data.
Note: Later in this chapter we provide an example PLC program for
accessing configuration data.
Part of the configuration memory is reserved for blocks of data which
contain previously stored image information when using reference windows.
These blocks are referred to as template blocks. Template blocks can be
accessed like configuration blocks with some differences:
•
A template may require different amounts of memory depending upon the
size of the template and the complexity of the feature.
•
Total memory storage may require up to 100 (64 word) blocks of
memory.
•
You may not alter template data, you should only upload and download
the data between the CVIM and a host.
•
You must keep the complete template memory intact. You may not
transfer a single template by itself.
•
When template data is being tansferred (to or from) the CVIM module,
the CVIM module will exit the active mode and ignore incoming triggers.
The CVIM will also assert the module busy bit.
Transferring Configuration
Blocks (cont’d)
Transferring Template
Blocks