Академический Документы
Профессиональный Документы
Культура Документы
MNETXT
ControlLogix Platform
Modbus TCP/IP Communication
Module
July 1, 2010
SETUP GUIDE
Important Safety Information - MVI56E and MVI56E-XT Modules
Ratings
Backplane Current Load: 800 mA @ 5 Vdc; 3 mA @ 24 Vdc
Operating Temperature:
For standard MVI56E modules: 0C to 60C (32F to 140F)
For MVI56E XT (conformal coated): -25C to 70C (-13F to 158F)
Storage Temperature: -40C to 85C (-40F to 185F)
Shock: 30 g operational; 50 g non-operational; Vibration: 5 g from 10 to 150 Hz
Relative Humidity 5% to 95% (without condensation)
All phase conductor sizes must be at least 1.3 mm (squared) and all earth ground conductors must be at least
4mm (squared).
MVI56E XT module comes with conformal coating installed.
Markings
ANSI / ISA ISA 12.12.01 Class I Division 2, GPs A, B, C, D
CSA/cUL C22.2 No. 213-M1987
CSA CB Certified IEC61010
ATEX EN60079-0 Category 3, Zone 2
EN60079-15
243333 E183151
CL I Div 2 GP A, B, C, D
Temp Code T4
II 3 G
Ex nA nL IIC T4 X
-20C <= Ta <= 70C
II Equipment intended for above ground use (not for use in mines).
3 Category 3 equipment, investigated for normal operation only.
G Equipment protected against explosive gasses.
Battery Life Advisory
The module uses a rechargeable Lithium Vanadium Pentoxide battery to backup the real-time clock and CMOS
settings. The battery itself should last for the life of the module. However, if left in an unpowered state for 14 to 21
days, the battery may become fully discharged and require recharging by being placed in a powered-up ControlLogix
chassis. The time required to fully recharge the battery may be as long as 24 hours.
Once it is fully charged, the battery provides backup power for the CMOS setup and the real-time clock for
approximately 21 days. Before you remove a module from its power source, ensure that the battery within the module
is fully charged (the BATT LED on the front of the module goes OFF when the battery is fully charged). If the battery
is allowed to become fully discharged, the module will revert to the default BIOS and clock settings.
ProSoft Technology
5201 Truxtun Ave., 3rd Floor
Bakersfield, CA 93309
+1 (661) 716-5100
+1 (661) 716-5101 (Fax)
www.prosoft-technology.com
support@prosoft-technology.com
Copyright 2010 ProSoft Technology, Inc., all rights reserved.
MVI56E-MNET / MNETXT Setup Guide
6/25/2010
ProSoft Technology , ProLinx , inRAx , ProTalk , and RadioLinx are Registered Trademarks of ProSoft
Technology, Inc. All other brand or product names are or may be trademarks of, and are used to identify products
and services of, their respective owners.
MVI56E-MNET / MNETXT ControlLogix Platform Contents
Modbus TCP/IP Communication Module Setup Guide
Contents
Important Safety Information - MVI56E and MVI56E-XT Modules ..................................................... 2
Battery Life Advisory ........................................................................................................................... 3
ProSoft Technology Product Documentation....................................................................................3
Your Feedback Please........................................................................................................................ 4
1 Scope 7
1.1 What's New? .............................................................................................................8
1.2 Learning Objectives...................................................................................................9
1.3 ProSoft Technology Documentation .......................................................................10
1.4 Prerequisites ...........................................................................................................11
5 Procedures 25
5.1 Physical Setup.........................................................................................................25
5.1.1 Setting Jumpers ......................................................................................................25
5.1.2 Install the Module in the Rack .................................................................................26
5.1.3 Connect your PC to the Module ..............................................................................27
5.1.4 Set Temporary IP Address ......................................................................................28
5.1.5 Connect to the Module's Web Page........................................................................35
5.1.6 Upload the Add-On Instruction from the Module.....................................................36
5.2 Connect your PC to the ControlLogix Processor ....................................................43
5.3 Download the Sample Program to the Processor...................................................44
5.4 Using ProSoft Configuration Builder Software ........................................................45
5.4.1 Upload the Sample Configuration from the Module ................................................46
5.4.2 Enable the MNET Client 0 Commands ...................................................................48
5.5 Download the Project to the Module .......................................................................51
5.6 Configure the NOE Ethernet adapter for Modbus TCP/IP (Server) ........................53
5.7 Connect the MVI56E-MNET Module to the Modbus TCP/IP Server ...................... 54
5.8 Verify Communication .............................................................................................55
6 Building on Success 63
6.1 Frequently Asked Questions................................................................................... 64
6.1.1 What are the differences between the MVI56 and the MVI56E modules? What
does the "E" stand for?................................................................................................................ 64
6.1.2 What is the difference between the MVI56E-MNET(R) and the MVI56E-
MNETC(R)? 65
6.1.3 Is the MVI56E product a direct replacement to my existing MVI56 product?......... 65
6.1.4 How is the MVI56E-MNET configured?.................................................................. 65
6.1.5 What is ProSoft Configuration Builder (PCB)? ....................................................... 65
6.1.6 What is the purpose of the MVI56E-MNET Ethernet (E1) Port? ............................ 66
6.1.7 How do I change the modules IP address? ........................................................... 66
6.1.8 What is the purpose of the Optional MVI56E-MNET Add-On Instruction?............. 66
6.1.9 Is there a Setup Guide to help with configuration?................................................. 66
6.1.10 What is ProSoft Discovery Service (PDS)? ............................................................ 67
6.1.11 Does the MVI56E-MNET module require processor logic?.................................... 67
6.1.12 How do I monitor MVI56E-MNET operation? ......................................................... 67
6.1.13 Are there any other ways to monitor module diagnostics besides being connected
to the modules network (subnet)? .............................................................................................. 67
6.1.14 What is the MVI56E-MNETXT? .............................................................................. 67
7 Glossary of Terms 69
Index 73
1 Scope
In This Chapter
What's New? ...........................................................................................8
Learning Objectives................................................................................. 9
ProSoft Technology Documentation...................................................... 10
Prerequisites ......................................................................................... 11
1.4 Prerequisites
To get the most benefit from this setup guide, you should have the following
skills:
Rockwell Automation RSLogix 5000 software: launch the program,
configure and transfer the Add-On Instruction to the processor
Microsoft Windows: install and launch programs, execute menu commands,
navigate dialog boxes and enter data.
Ethernet networking: connect the MVI56E-MNET module to an Ethernet
network using a valid IP address and subnet mask
Hardware installation and wiring: install the module and safely connect
Modbus TCP/IP and ControlLogix devices to a power source and to the
MVI56E-MNET modules Ethernet port
In This Chapter
System Requirements ........................................................................... 13
Required Items ...................................................................................... 14
Sample Files..........................................................................................15
Note: For RSLogix v15 (or older) applications, please refer to the MVI56E-MNET User Manual for
information on how to use the sample ladder logic.
In This Chapter
Install ProSoft Configuration Builder...................................................... 17
In This Chapter
About the MODBUS TCP/IP Protocol.................................................... 19
General Overview.................................................................................. 20
Architecture ........................................................................................... 22
Memory Map .........................................................................................24
When you finish the steps in this Setup Guide, you will have enough information
to set up your own application.
4.3 Architecture
The sample application uses the following hardware and connections.
A Personal Computer running a supported version of Microsoft Windows, with
a web browser, RSLogix 5000, ProSoft Discovery Service and an Ethernet
port
A ControlLogix processor with MVI56E-MNET module acting as a Modbus
TCP/IP Client
A Quantum processor with a NOE Ethernet adapter acting as a Modbus
TCP/IP Server
An Ethernet network connecting the PC with the MVI56E-MNET, either
directly, or through an Ethernet hub or switch.
An Ethernet cable connecting the MVI56E-MNET Modbus TCP/IP Client to
the Modbus TCP/IP Server.
Note: The illustration does not show the required Ethernet connection for processor programming.
5 Procedures
In This Chapter
Physical Setup....................................................................................... 25
Connect your PC to the ControlLogix Processor ................................... 43
Download the Sample Program to the Processor.................................. 44
Using ProSoft Configuration Builder Software....................................... 45
Download the Project to the Module...................................................... 51
Configure the NOE Ethernet adapter for Modbus TCP/IP (Server) ....... 53
Connect the MVI56E-MNET Module to the Modbus TCP/IP Server...... 54
Verify Communication ........................................................................... 55
Note: If you are installing the module in a remote rack, you may prefer to leave the Setup pins
jumpered. That way, you can update the modules firmware without requiring physical access to
the module.
Warning: You must follow all safety instructions when installing this or any other electronic
devices. Failure to follow safety procedures could result in damage to hardware or data, or even
serious injury or death to personnel. Refer to the documentation for each device you plan to
connect to verify that suitable safety procedures are in place before installing or servicing the
device.
After you have checked the placement of the jumpers, insert the MVI56E-MNET
into the ControlLogix chassis. Use the same technique recommended by
Rockwell Automation to remove and install ControlLogix modules.
You can install or remove ControlLogix system components while chassis power
is applied and the system is operating. However, please note the following
warning.
Warning: When you insert or remove the module while backplane power is on, an electrical arc
can occur. An electrical arc can cause personal injury or property damage by:
sending an erroneous signal to your systems actuators causing unintended machine motion
or loss of process control
causing an explosion in a hazardous environment
Verify that power is removed or the area is non-hazardous before proceeding. Repeated electrical
arcing causes excessive wear to contacts on both the module and its mating connector. Worn
contacts may create electrical resistance that can affect module operation.
9 Align the module with the top and bottom guides, and then slide it into the
rack until the module is firmly against the backplane connector.
Note: If you insert the module improperly, the system may stop working, or may behave
unpredictably.
Note: When using the MVI56EMNETXT, you must use the 1756-A5XT or 1756-A7LXT chassis.
Important: ProSoft Configuration Builder locates MVI56E-MNET modules through UDP broadcast
messages. These messages may be blocked by routers or layer 3 switches. In that case, ProSoft
Discovery Service will be unable to locate the modules.
To use ProSoft Configuration Builder, arrange the Ethernet connection so that there is no router/
layer 3 switch between the computer and the module OR reconfigure the router/layer 3 switch to
allow the routing of the UDP broadcast messages.
3 Use the mouse to select DEFAULT MODULE in the tree view, and then click the
right mouse button to open a shortcut menu.
4 On the shortcut menu, choose CHOOSE MODULE TYPE. This action opens the
CHOOSE MODULE TYPE dialog box.
5 In the PRODUCT LINE FILTER area of the dialog box, select MVI56E. In the
SELECT MODULE TYPE dropdown list, select MVI56E-MNET, and then click
OK to save your settings and return to the ProSoft Configuration Builder
window.
6 Right click over the module icon.
1 Click the SET UP CONNECTION button to browse for the modules IP address.
2 On the CONNECTION SETUP dialog box, click the TEST CONNECTION button to
verify if the module is accessible with the current settings
3 If PCB is still unable to connect to the module, click the BROWSE DEVICE(S)
button to open the PROSOFT DISCOVERY SERVICE.
4 Select the module, then right click and choose ASSIGN TEMPORARY IP.
CIPconnect
You can use CIPconnect to connect a PC to the MVI56E-MNET module over
Ethernet using Rockwell Automations 1756-ENBT EtherNet/IP module. This
allows you to configure the MVI56E-MNET module and network, upload and
download files, and view network and module diagnostics from a PC. RSLinx is
not required when you use CIPconnect. All you need are:
The IP addresses and slot numbers of any 1756-ENBT modules in the path
The ControlNet node numbers and slot numbers of any 1756-CNBx
ControlNet Bridge modules in the path
The slot number of the MVI56E-MNET in the destination ControlLogix chassis
(the last ENBT/CNBx and chassis in the path).
2 Click CIP PATH EDIT to open the CIPCONNECT PATH EDITOR dialog box.
The CIPCONNECT PATH EDITOR allows you to define the path between the PC
and the MVI56E-MNET module. The first connection from the PC is always a
1756-ENBT (Ethernet/IP) module.
Each row corresponds to a physical rack in the CIP path.
If the MVI56E-MNET module is located in the same rack as the first 1756-
ENBT module, select RACK NO. 1 and configure the associated parameters.
If the MVI56E-MNET is available in a remote rack (accessible through
ControlNet or Ethernet/IP), include all racks (by using the ADD RACK button).
Parameter Description
Source Module Source module type. This field is automatically selected
depending on the destination module of the last rack
(1756-CNB or 1756-ENBT).
Source Module IP Address IP address of the source module (only applicable for
1756-ENBT)
Source Module Node Address Node address of the source module (only applicable for
1756-CNB)
Destination Module Select the destination module associated to the source module
in the rack. The connection between the source and destination
modules is performed through the backplane.
Destination Module Slot Number The slot number where the destination MVI56E module is
located.
The web page contains the product documentation and sample programs.
Important: The temporary IP address is only valid until the next time the module is initialized.
Please refer to Set Temporary IP Address (page 28) in the MVI56E-MNET User Manual for
information on how to set the modules permanent IP address.
2 Select the 1756-MODULE (GENERIC 1756 MODULE) from the list and click OK.
This action opens the NEW MODULE dialog box.
3 In the NEW MODULE dialog box, enter the following values.
Parameter Value
NAME Enter a module identification string. Example: MNET.
DESCRIPTION Enter a description for the module. Example: Modbus
TCP/IP Communication Module
COMM FORMAT Select DATA-INT.
SLOT Enter the slot number in the rack where the MVI56E-MNET
module is located.
INPUT ASSEMBLY INSTANCE 1
INPUT SIZE 250
OUTPUT ASSEMBLY INSTANCE 2
OUTPUT SIZE 248
CONFIGURATION ASSEMBLY INSTANCE 4
CONFIGURATION SIZE 0
Important: You must select the COMM FORMAT as DATA - INT in the dialog box, otherwise the
module will not communicate over the backplane of the ControlLogix rack.
4 Click OK to continue.
5 Edit the Module Properties. Select the REQUESTED PACKET INTERVAl value for
scanning the I/O on the module. This value represents the minimum
frequency at which the module will handle scheduled events. This value
should not be set to less than 1 millisecond. The default value is 5
milliseconds. Values between 1 and 10 milliseconds should work with most
applications.
4 Navigate to the location on your PC where you saved (page 36) the Add-On
Instruction (for example, "My Documents" or "Desktop"). Select the
MVI56EMNET_ADDON_RUNG_V1_3.L5X file
This action opens the IMPORT CONFIGURATION dialog box, showing the
controller tags that will be created.
5 If you are using the module in a different slot (or remote rack), select the
correct connection input and output variables that define the path to the
module. If your module is located in Slot 1 of the local rack, this step is not
required.
6 Click OK to confirm the import. RSLogix will indicate that the import is in
progress:
When the import is completed, the new rung with the Add-On Instruction will
be visible as shown in the following illustration.
The procedure has also imported new User Defined Data Types, data objects
and the Add-On instruction for your project.
7 Save the application and then download the sample ladder logic into the
processor.
2 Connect the straight connector end of the cable to the serial port on your
computer.
Note: The key switch on the front of the ControlLogix processor must be in the REM or PROG
position.
1 If you are not already online with the processor, open the COMMUNICATIONS
menu, and then choose DOWNLOAD. RSLogix will establish communication
with the processor. You do not have to download through the processor's
serial port, as shown here. You may download through any available network
connection.
2 When communication is established, RSLogix will open a confirmation dialog
box. Click the DOWNLOAD button to transfer the sample program to the
processor.
3 RSLogix will compile the program and transfer it to the processor. This
process may take a few minutes.
4 When the download is complete, RSLogix will open another confirmation
dialog box. If the key switch is in the REM position, click OK to switch the
processor from PROGRAM mode to RUN mode.
Note: If you receive an error message during these steps, refer to your RSLogix documentation to
interpret and correct the error.
Note: The MVI56E-MNET module receives its protocol and backplane configuration information
from the Personality Module (Compact Flash). Use ProSoft Configuration Builder to configure
module settings, and to download changes to the Personality Module.
2 In the UPLOAD FILES dialog box, click BROWSE DEVICES to locate the MVI56E-
MNET module. This action opens the PROSOFT DISCOVERY SERVICE dialog
box. Select the module, and then click the right mouse button to open a
shortcut menu. On the shortcut menu, choose SELECT FOR PCB. This action
places the modules Ethernet address in the Upload Files dialog box.
3 Click the X in the top right corner to close the ProSoft Discovery Service
dialog box.
4 In the UPLOAD FILES dialog box, click Upload. When the upload is complete,
as shown in the following illustration, click the OK button.
ProSoft Configuration Builder now contains the sample configuration for your
MVI56E-MNET module. In the following steps, you will configure the Read and
Write commands.
2 Double-click the MNET CLIENT 0 COMMANDS tag to open the EDIT MNET
CLIENT 0 COMMANDS dialog box.
Select the first command in the list, and then click EDIT ROW.
Notes:
Func 3 represents Modbus Function Code 3, the command code to Read Holding Registers
The DevAddress parameter is 0-based so 800 = 400801, 801 = 400802, and so on.
The Enable code must be set to 1 to enable the command (0 = disable)
The destination Slave node address must be set as 1 (Node parameter)
Notes:
Func 16 represents Modbus Function Code 16, the command code to Preset (Write) Holding
Registers
The DEVADDRESS parameter is 0-based so 400 = 400401, 401 = 400402, and so on.
The ENABLE code must be set to 1 to enable the command (0 = disable).
The destination Slave node address must be set as 1 (Node parameter)
If the Test Connection procedure fails, you will see an error message. To correct
the error, follow these steps.
1 Click OK to dismiss the error message.
2 On the DOWNLOAD dialog box, click BROWSE DEVICES to open PROSOFT
DISCOVERY SERVICE.
3 Select the module, and then click the right mouse button to open a shortcut
menu. On the shortcut menu, choose SELECT FOR PCB.
4 Close ProSoft Discovery Service.
5 Click DOWNLOAD to transfer the configuration to the module.
5.6 Configure the NOE Ethernet adapter for Modbus TCP/IP (Server)
The next part of this tutorial is to configure the remote Modbus TCP/IP Server.
For this example, the Modbus TCP/IP Server will be a NOE communication
adapter.
The IP Address for the Modbus TCP/IP Server must match the IP Address
settings for the MNET Client 0 Commands in ProSoft Configuration Builder.
The following illustration shows the ETHERNET / I/O SCANNER dialog box with the
NOE card configured as a Modbus TCP/IP Server in Concept version 2.6.
This action sends the values you entered to the MODBUS CLIENT 0 on the
MVI56E-MNET, and then to the Quantum processor, where you will be able
to see the data in Concept.
3 In Concept, navigate to the REFERENCE DATA EDITOR to monitor the
processor memory addresses from 400401 through 400410. The data should
match the data you sent from RSLogix 5000.
This action populates the memory addresses in the Quantum processor that
the MVI56E-MNET will attempt to retrieve with the ReadData Command.
2 In RSLogix 5000, the values in MNET.DATA.READDATA[0] through [9]
should match the data you entered in Concept.
Tip: Repeat these tests, using different values each time, to verify that the same data appears in
the proper place in each processor.
In this case, the COMMAND ERROR POINTER was set to 1500 and the READ
REGISTER START to 1000. This means that (1500 1000 = 500); so
READDATA[500] and READDATA[501] will tell you the individual status of each of
the two commands issued by the module.
To verify that the Modbus TCP/IP Server is communicating with a Modbus
TCP/IP Client, view the contents of the MNET.STATUS.CLIENTSTATUS tag for
total commands issued, responses received, errors, and so on.
The following controller tags should increment periodically, indicating that the
Modbus TCP/IP Client is continuously sending commands and receiving
responses:
MNET.STATUS.CLIENTSTATUS.CMDREQ
MNET.STATUS.CLIENTSTATUS.CMDRESP
MNET.STATUS.CLIENTSTATUS.REQUESTS
MNET.STATUS.CLIENTSTATUS.RESPONSES
If the error counters continuously increment, the LASTERROR controller tag value
shows the command index that caused the latest failure.
Initialization Messages
Code Message
Boot / DDOK Module is initializing
Ladd Module is waiting for required module configuration data from
ladder logic to configure the application port(s)
Waiting for Processor Connection Module did not connect to processor during initialization
Sample ladder logic or AOI is not loaded on processor
Module is located in a different slot than the one
configured in the ladder logic/AOI
Processor is not in RUN or REM RUN mode
Last config: <date> Indicates the last date when the module changed its IP
address. You can update the module date and time through the
modules web page, or with the optional MVI56E Optional Add-
On Instruction.
C0 (Client): CmdCnt: X MinDly : After power up and every reconfiguration, the module will
X CmdOffs: X RespTmout : X display the configuration the application port(s). The
Retries : X ErrOffs : X information consists of:
ARPTmout : X ErrDelay : X Client
FltFlag : X FltSt : X FltOffs : X CmdCnt : number of commands configured for the client
SVR (server) : BIOffs: X WIOffs : MinDly : Minimum Command Delay parameter
X OutOffs : X HoldOffs : X CmdOffs : Command Error Pointer parameter
FltFlag : X FltSt : X FltSt : X RespTmout : Response Timeout parameter
CommTmout : X
Retries : Retry Count parameter
ErrOffs : Error/Status Offset parameter
ARPTmout : ARP Timeout parameter
ErrDelay: Command Error Delay parameter
FltFlag: Float Flag parameter
Flt St : Float Start parameter
FltOffs : Float Offset parameter
Server
BIOffs: Bit Input Offset parameter
WIOffs : Word Input Offset parameter
OutOffs : Output offset parameter
HoldOffs : Holding Register offset parameter
FltFlag: Float Flag parameter
Flt St : Float Start parameter
FltOffs : Float Offset parameter
Operation Messages
After the initialization step, the following message pattern will be repeated.
<Backplane Status> <IP Address> <Backplane Status> <Port Status>
Code Message
<Backplane Status> OK: Module is communicating with processor
ERR: Module is unable to communicate with processor. For
this scenario, the <Port Status> message above is replaced
with "Processor faulted or is in program mode".
<IP Address> Module IP address
<C0> OK: Port is communicating without error
Communication Errors: port is having communication errors.
Refer to PCB diagnostics for further information about the
error.
6 Building on Success
In This Chapter
Frequently Asked Questions ................................................................. 64
Now that you have successfully installed, configured, and verified operation of
the MVI56E-MNET module, you should have a better understanding of how to
make it work for your specific application. The following resources are available
to help you build on your success.
For more information about the MVI56E-MNET module, including detailed
hardware and software configuration, troubleshooting, and application
information, refer to the MVI56E-MNET User Manual.
For technical support and warranty information for your MVI56E-MNET
module, refer to Support, Service, and Warranty in the MVI56E-MNET User
Manual.
For more information on ProSoft Technology products and services, please
visit www.prosoft-technology.com.
6.1.1 What are the differences between the MVI56 and the MVI56E
modules? What does the "E" stand for?
The "E" stands for Enhanced with Ethernet communication capabilities. The new
enhancements are:
PCB: ProSoft Configuration Builder software; a Windows-based configuration
utility providing a graphical user interface for module diagnostics with screen
navigation, improving interoperability with the module.
Seamless Migration: MVI56E products are backward compatible with
existing ladder logic and module configuration files, allowing for a smooth
transition when upgrading MVI56 products.
Personality Module: The MVI56E incorporates a non-volatile CF (Industrial
Compact Flash) memory card for storing the modules setup and network
configuration data (or personality). This feature benefits the end-user with
quick replacement of modules for disaster recovery. Restore a module by a
simple exchange of the Personality Module with absolutely no PC or
configuration requirements.
Ethernet Configuration port: Allows for remote module connectivity.
Replaces the serial communication port, becoming the primary configuration
port with faster access.
Web server: Provides HTML information about the status of the product,
download access to documents such as the product manual, and for firmware
updates. Components are stored locally in the modules flash memory.
LED Display: The LED provides detailed, plain English diagnostics and error
information for the module, backplane communication, and network
conditions.
Discovery Service: Allows PCB configuration software (or separate utility) to
find and display products located on the network with key product attributes
such as name, serial number, and IP address. The user will be able to
change IP address, upload/download, and enter into diagnostics from the list.
CIPconnect-enabled: Allows end-users to use PCB from remote locations
to local and remote chassis installed MVI56E module(s) through a 1756-
ENxT. Multi hop (Ethernet and ControlNet) connections are supported.
RSLinx OEM is not required.
7 Glossary of Terms
A
ASCII
American Standard Code for Information Interchange. A communication mode in
which each eight-bit byte in a message contains one ASCII character code.
ASCII characters (or hexadecimal characters) are sometimes used as a key to
encrypt data and ensure its secure transmission.
C
Client
A client is a software program, or the device on which that program runs, that
makes requests for information from a software program, or the device on which
that program runs, in a client-server relationship.
A Client on an Ethernet network is equivalent to a Master on a serial network.
D
Default Gateway
The IP address of a network router where data is sent if the destination IP
address is outside the local subnet. The gateway is the device that routes the
traffic from the local area network to other networks such as the Internet.
E
ESD
Electrostatic Discharge. Can cause internal circuit damage to the coprocessor.
Ethernet
A set of network cabling and network access (CSMA/CD) protocol standards for
bus topology computer networks invented by Xerox but now controlled by the
802.3 subcommittee of the IEEE.
F
Firmware
Software for embedded computers.
Full-Duplex
A communications circuit or system designed to simultaneously transmit and
receive two different streams of data. Telephones are an example of a full-duplex
communication system. Both parties on a telephone conversation can talk and
listen at the same time. If both talk at the same time, their two signals are not
corrupted.
H
Half-Duplex
A communications circuit or system designed to transmit and receive data, but
not both simultaneously. CB or walkie-talkie radios are an example of a half-
duplex communication system. Either parties on a radio conversation may talk or
listen; but both cannot talk at the same time without corrupting each other's
signal. If one operator is "talking", the other must be "listening" to have
successful communication.
I
IP Address
A 32-bit identification number for each node on an Internet Protocol network.
These addresses are represented as four sets of 8-bit numbers (numbers from 0
to 255), separated by periods ("dots").
Networks using the TCP/IP Protocol route messages based on the IP address of
the destination. Each number can be 0 to 255. For example, 192.168.0.100 could
be an IP address. Each node on the network must have a unique IP address.
L
LED
Light-emitting diode.
M
MAC ID
A hexadecimal number that uniquely identifies an Ethernet device.
Master
A Master is a device that makes requests for information from a software
program, or the device on which that program runs, in a Master-Slave
relationship.
A Client on an Ethernet network is equivalent to a Master on a Serial network.
N
Network
A series of stations or nodes connected by some type of communication medium.
A network may consist of a single link or multiple links.
Node
An address or software location on the network.
P
Peer-to-Peer
A network relationship between devices where each device can send commands
as a master or client, and respond to commands as a slave or server.
Power Supply
Device that supplies electrical power to the I/O chassis containing the processor,
coprocessor, or other modules.
Protocol
The language or packaging of information that is transmitted between nodes on a
network.
S
Server
A Server is a software program, or the device on which that program runs, that
provides a specific kind of service to a Client software program, or the device on
which that program runs, on an Ethernet network.
A Server on an Ethernet network is equivalent to a Slave on a Serial network.
Simplex
A communications circuit or system designed to either transmit data or receive
data, but not both. Broadcast television is an example of simplex communication
system. A television station sends a TV signal but cannot receive responses
back from the television sets to which it is transmitting. The TV sets can receive
the signal from the TV station but cannot transmit back to the station.
Slave
A Slave is a software program, or the device on which that program runs, which
provides a specific kind of service to a Master software program, or the device on
which that program runs, on a serial network.
A Slave on a Serial network is equivalent to a Server on an Ethernet network.
Subnet Mask
A mask used to determine what subnet an IP address belongs to. An IP address
has two components: the network address, and the host (node or device)
address. For example, consider the IP address 150.215.017.009. Assuming this
is part of a Class B network (with a subnet mask of 255.255.0.0), the first two
numbers (150.215) represent the Class B network address, and the second two
numbers (017.009) identify a particular host on this network.
G
General Overview 20
Index H
Half-Duplex 70
A How do I change the modules IP address? 66
How do I monitor MVI56E-MNET operation? 67
About the MODBUS TCP/IP Protocol 19 How is the MVI56E-MNET configured? 65
Architecture 22
Are there any other ways to monitor module I
diagnostics besides being connected to the Import Add-On Instruction 40
modules network (subnet)? 67 Important Safety Information - MVI56E and MVI56E-
ASCII 69 XT Modules 2
B Install ProSoft Configuration Builder 17
Install the Configuration Tools 9, 17
Battery Life Advisory 3 Install the Module in the Rack 26
Before You Begin 13 IP Address 70
Building on Success 63 Is the MVI56E product a direct replacement to my
existing MVI56 product? 65
C Is there a Setup Guide to help with configuration? 66
Check Module Status through ControlLogix Controller L
Tags 55, 58
Check Read Data 57 Learning Objectives 9
Check Write Data 56 LED 70
CIPconnect 32 LED Status Indicators 55, 60
Client 69
Configure the Modbus Client Read Command 21, 49 M
Configure the Modbus Client Write Command 21, 50 MAC ID 70
Configure the NOE Ethernet adapter for Modbus Master 70
TCP/IP (Server) 9, 21, 53 Memory Map 24
Connect the MVI56E-MNET Module to the Modbus
TCP/IP Server 54 N
Connect to the Module's Web Page 35
Connect your PC to the ControlLogix Processor 21, Network 71
43 Node 71
Connect your PC to the Module 27 Non-Scrolling LED Status Indicators 62
Create a new RSLogix 5000 project 21, 37
Create the Module 38 P
Peer-to-Peer 71
D Physical Setup 9, 21, 25
Default Gateway 69 Power Supply 71
Does the MVI56E-MNET module require processor Prerequisites 11
logic? 67 Procedures 25
Download the Project to the Module 21, 51 ProSoft Technology Documentation 10
Download the Sample Program to the Processor 9, ProSoft Technology Product Documentation 3
21, 44 Protocol 71
E R
Enable the MNET Client 0 Commands 9, 21, 48 Required Items 14
ESD 69 Required Steps 21
Ethernet 69
Ethernet LED Indicators 61 S
Sample Files 15
F Scope 7
Firmware 69 Scrolling LED Status Indicators 60
Frequently Asked Questions 64 Server 71
Full-Duplex 70 Set Temporary IP Address 28, 35
Setting Jumpers 25
Simplex 71
Slave 71
Subnet Mask 72
System Requirements 13
T
The Sample Application 9, 19
U
Upload the Add-On Instruction from the Module 36,
41
Upload the Sample Configuration from the Module
21, 46
Using ProSoft Configuration Builder Software 45
V
Verify Communication 9, 21, 55
View Exchanged Data 55
W
What are the differences between the MVI56 and the
MVI56E modules? What does the 64
What is ProSoft Configuration Builder (PCB)? 65
What is ProSoft Discovery Service (PDS)? 67
What is the difference between the MVI56E-MNET(R)
and the MVI56E-MNETC(R)? 65
What is the MVI56E-MNETXT? 67
What is the purpose of the MVI56E-MNET Ethernet
(E1) Port? 66
What is the purpose of the Optional MVI56E-MNET
Add-On Instruction? 66
What's New? 8
Y
Your Feedback Please 4