ProSoft Technology MVI56E-DNPNET - Manual (Page 46)

Contents MVI56E-DNPNET ♦ ControlLogix Platform
User Manual DNPNET Ethernet Client/Server Communication Module
Page 46 of 140 ProSoft Technology, Inc.
February 13, 2015
Code Message
Ladd Module is waiting for required module configuration data from
ladder logic to configure the Modbus ports
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 Connect to the Module’s Web Page (page 74), or with the
MVI56E Add-On Instruction.
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
<Port Status> OK: Port is communicating without error
Client/Server Communication Errors: port is having
communication errors. Refer to Diagnostics and
Troubleshooting (page 45) for further information about the
error.
3.1.2 Non-Scrolling LED Status Indicators
The non-scrolling LEDs indicate the module’s operating status as follows:
LED Label Color Status Indication
APP Red or
Green
OFF The module is not receiving adequate power or is not securely
plugged into the rack. May also be OFF during configuration
download.
GREEN The MVI56E-DNPNET is working normally.
RED The most common cause is that the module has detected a
communication error during operation of an application port.
The following conditions may also cause a RED LED:

The firmware is initializing during startup
 The firmware detects an on-board hardware problem
during startup
 Failure of application port hardware during startup
 The module is shutting down
 The module is rebooting due to a ColdBoot or WarmBoot
request from the ladder logic or Debug Menu
OK Red or
Green
OFF The module is not receiving adequate power or is not securely
plugged into the rack.