150
Rockwell Automation Publication 2711P-UM006A-EN-P - November 2010
Chapter 9
Troubleshoot the System
Advanced Diagnostics
Ping and ipconfig are valuable tools for network debugging along with some
knowledge of IP and the Winsock error codes:
•
Try to ping the destination host.
•
Check the destination address.
•
Check whether you have a router configured in your network system (your
WinSock implementation).
•
Use the tracert command at the command prompt on the desktop to try
and determine where the failure occurs along the route between your host
and the destination host.
•
Some utility programs can be developed using the software development
kit (SDK).
•
Take advantage of alternate connectivity - mouse versus touch screen,
keyboard versus keypad, serial communication, and alternate Ethernet
connections.
•
Examine the folder \Windows\DumpFiles for crash logs when suspecting
an application or operating system crash.
The crash dump file is viewable offline, on a workstation, using common
Windows development or debugging tools, for example, Visual Studio or
WinDBG. At a minimum, the information in the crash dump file will
reveal the date and time of the exception, the exception type, the name of
the offending process and the register state, including the program counter.
•
Store Autorun.exe utilities on an SD card that can be easily run by inserting
the card in the SD card slot of the terminal.
•
Know useful keyboard shortcuts so that you can navigate around the
system without a mouse or touch screen.
•
Check the system event log in the Hardware Monitor control panel
application or under Terminal Settings>System Event Log in FactoryTalk
View ME Station. Look for error conditions or reasons that might cause
unexpected behaviors or restarts.
•
Check the configuration settings in the desktop control panel applications
or in FactoryTalk View ME Station.
