EasyManuals Logo

ProSoft Technology MVI56E-MCM User Manual

ProSoft Technology MVI56E-MCM
209 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Page #200 background imageLoading...
Page #200 background image
Reference MVI56E-MCM ControlLogix Platform
User Manual Modbus Communication Module
Page 200 of 209 ProSoft Technology, Inc.
_PassThru
Use this optional task to send pass-through data between the processor and the
Modbus devices connected to the MVI56E-MCM module. Pass-Through
functionality allows the Modbus Master to read and write the same Modbus
address on a Modbus Slave. If pass-through mode is not chosen, then the
attached Modbus Master device must read from one set of Modbus register/bits
and write to another set of Modbus register/bits. Pass-Through mode takes a
Modbus write command (Function Codes 5, 6, 15, and 16) and passes that to the
ControlLogix processor. The pass-through ladder logic then parses that
information and updates the MCM.DATA.WRITEDATA array with the new value
that has been written by the Modbus Master.
_ReadControl
Use this optional task to get status and event data from the Modbus devices
connected to the MVI56E-MCM module. Special command blocks requested
from the module in the _WriteControl routine are processed and handled in this
routine. If command control, event command, or Slave status blocks are not
going to be used in the application, then this rung and the _ReadControl and
_WriteControl ladder files may be removed.
_WriteControl
Use this optional task to send commands to the Modbus devices connected to
the MVI56E-MCM module. Command Control, Event Command, and Slave
status blocks are sent to the module in this task.
Copying the Controller Tags
Next, copy the Controller Tags from the sample program to your existing
program. The sample program includes the following tags in the MCM structure.
MCM.MODDEF configures the database in the module. The module uses this
database to store input and output data transferred between the processor
and the Modbus devices connected to the MVI56E-MCM module.
MCM.PORT1 and MCM.PORT2 configure the module’s serial ports for Modbus
communications. The sample program configures Port 1 as a Modbus
Master, and Port 2 as a Modbus Slave.
MCM.P1.CMD and MCM.P2.CMD configure the Modbus Master commands for
the module. These commands are active only if a port is configured as a
Modbus Master.
MCM.READDATA contains data read by the ControlLogix processor from the
MVI56E-MCM module.
MCM.WRITEDATA contains data read from the ControlLogix processor to the
module’s internal database.
The remaining controller tags contain error and status information, and special
commands to execute.
1 In the CONTROLLER ORGANIZATION pane in each instance of RSLogix 5000,
expand the CONTROLLER folder.
2 Double-click the CONTROLLER TAGS icon in each instance of RSLogix 5000.
This action opens the CONTROLLER TAGS dialog box.

Table of Contents

Other manuals for ProSoft Technology MVI56E-MCM

Questions and Answers:

Question and Answer IconNeed help?

Do you have a question about the ProSoft Technology MVI56E-MCM and is the answer not in the manual?

ProSoft Technology MVI56E-MCM Specifications

General IconGeneral
BrandProSoft Technology
ModelMVI56E-MCM
CategoryControl Unit
LanguageEnglish

Related product manuals