Delta RMC101 - Manual (Page 443)

Modbus Plus 5.3
Communications 5-193
differ between versions of Modsoft and Concept:
1. Reserve Config Extension Memory in the PLC:
Peer Cop uses Config Extension memory. Refer to Modicon Modsoft Programmer User Manual
for details on the exact procedure for allocating Config Extension memory and the method of
calculating the memory requirements.
2. Add the RMC Device as a Peer Cop Node:
Some versions of Modsoft require that the Peer Cop node be added.
3. Add Global Data Sub-entries to the RMC Peer Cop Node:
For each device, the global data can be copied into eight sections of the PLC memory. Each
section is called a sub-entry. Each sub-entry has the following pieces of information:
• Address in PLC memory (0xxxxx, 1xxxxx, 3xxxxx, 4xxxxx).
• Length (in 16-bit registers) to copy.
• Type of the data. This should always be BIN for the RMC.
• Index. The index refers to the number of the first register to be copied. Its range is from 1-31.
At the top of each scan, for each sub-entry, the Global Data registers beginning at the Index—and
continuing for the number of registers given by the Length—are copied into the PLC address.
See the example below.
4. Add a Network for Detecting the Peer Cop Health:
This step is not required, but highly recommended. Refer to MSTR Block Peer Cop Health
Operation for an example of the Modicon logic for doing this.
Example
Suppose we have a four-axis RMC module at node address 3, and we have configured the
Status Map to have the following assignments for the first nine registers:
Status
Map
Register:
RMC
Register:
Holds:
0 0 Axis 0 Command Position
1 1 Axis 0 Target Position
2 2 Axis 0 Actual Position
3 4 Axis 0 Status Word
4 10 Axis 1 Command Position
5 11 Axis 1 Target Position
6 12 Axis 1 Actual Position