ProSoft Technology MVI46-MBP - Manual (Page 87)

Reference MVI46-MBP ♦ SLC Platform
Modbus Plus Communication Module
ProSoft Technology, Inc. Page 87 of 101
February 19, 2008
5.9 Frequently Asked Questions
5.9.1 How is data transferred between the SLC and the MVI46-MBP?
The transfer of data is performed using the module M0 and M1 files across the
backplane. So the M1 file is a copy of the module internal database and the M0
file is used for module control from ladder logic.
5.9.2 How many registers can be used for user data?
The first 4000 registers (0 to 3999) can be used to store user data.
5.9.3 How is new configuration data written to the MVI46-MBP
module?
The SLC data files should be used to store the configuration data. When the
module performs a restart operation (either through a cold boot or warm boot) it
will request configuration data to the SLC by moving a value of 9000 to register
4370 of M1 file. When this happens, the ladder logic should copy the
configuration data to the module (general configuration, global in file map, device
definition and master command list). After the configuration data is copied, the
ladder logic should place a value of 9001 to register 4370 of M1 file in order to
flag the end of the operation.
5.9.4 How is the current module configuration copied to the SLC
memory?
The user should select option 'Y' (Transfer module cfg to processor) using the
debug terminal to initiate the transfer. At this point, the module sets a value of -
9000 to word 4370 of the M1 file. Ladder logic must recognize this value and the
move the configuration data from the M1 file to the SLC data file (general
configuration, global in file map, device definition and master command list). The
order of the registers is the same as defined the Reference chapter - Memory
Definition. After the data is copied to the SLC memory, the ladder logic must
move a value of 0 to word 4370 of the M1 file in order to flag the end of the
operation.
5.9.5 Why do I get an error code 3 every time I try to send
configuration data from the module to the processor and no
data is moved?
Look at the ladder logic and make sure the ladder logic moves a value of 0 to
word 4370 of the M1 file in order to flag the end of the operation.