GE Industrial Solutions POWER LEADER ModBus Monitor - Manual (Page 45)

POWER LEADER Modbus Monitor
Chapter 6 – Troubleshooting Guide
39
Symptom Possible Cause Corrective Action
11. PMCS Event Log screen
viewed at Monitor is
blank. No events have been logged.
Monitor Proxy client application
has lost communications with
PMCS Event Logger client.
None - no events will be visible at the Monitor until some
events are logged by the Event Logger. Note that alarms
are not considered events by the Monitor and will not be
displayed.
For the Monitor to display the PMCS Event Log, the
Monitor Proxy client application must be able to
communicate with the PMCS Event Logger client. The
Event Logger client may have locked up or, if it is located
on a different PC and the two clients are communicating
by NetDDE, the network connection may have been lost.
Restart the Proxy after checking to see that the Event
Logger client is running correctly.
12. Monitor displays
“UNABLE TO UPDATE
DATA” and no updates
are displayed. The PMCS DDE Server may be
incorrectly configured, showing
the Monitor to be on the wrong
Modbus segment. Check PMCS network configuration to make sure that the
Monitor is on the correct Modbus segment.
13. Many timeouts recorded
at PMCS DDE Server. Monitor may be physically
disconnected from the network.
Incorrect Modbus address or
Modbus segment set at Server;
Server expects Monitor to be at
address X on segment x when
Monitor is actually at address Y on
segment y.
Check the RS-485 connections to the Monitor.
The PMCS DDE Server supports up to 256 Modbus
segments. Check that the PMCS DDE Server is correctly
configured with the proper Modbus segment and Modbus
address for the Monitor in question.
14. Unable to read or write
configurations to the
Monitor using the
Configuration Tool. PC not connected to Monitor.
Port setting on PC doesn’t match
port used by Configuration Tool.
Make sure the RS-232 cable is properly connected
between the Monitor and the PC running the
Configuration Tool.
Check the Configuration Tool’s environ.ini file and make
sure that the Port=x line is consistent with the physical
RS-232 port in use. X must equal the com port number
where the RS-232 cable is attached to the PC.
15. AutoScan does not detect
any devices on the
Modbus segment. RS-232 port settings incorrect in
either environ.ini or autoscan.ini
file. Check the two .ini files to make sure the RS-232 port is
set correctly. Default is COM1, but not all laptops have
the COM1 port available as the RS-232 port.
In the environ.ini file, the port entry under the [Port
Settings] group must be set to the number of the com port
to which the RS-232 cable is attached. In the autoscan.ini
file, the port entry under the [Settings] group must be set
to the same value.
16. Device network address
is not available for
selection when adding a
new network device. Another device has already been
assigned this address. As device addresses are used, they are removed from the
list of available addresses to prevent conflicts. If an
address appears to be missing, check to see if you have
already assigned this address to another device. Also
check the Modbus Monitor’s network address under the
Port Settings dialog.