File System Errors; Advanced Diagnostics - Allen-Bradley PanelView Plus 6 User Manual

File System Errors

Advanced Diagnostics

File system errors are rare as the internal file system is transaction safe. Always
stop applications before removing power so that data is cleanly flushed out to the
file system and the file system is brought to an orderly stop.
Do not remove the external USB or SD storage devices while writing to the
device is in progress. Although the FactoryTalk View Machine Edition (ME)
application runs from RAM, functions such as data logging, event logging, and
historical trending, write to nonvolatile memory and must be stopped before
removing power.
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.
Other diagnostic tips that can help include the following:
• 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, by using
common Windows development or debugging tools, for example, Visual
Studio or WinDBG. At a minimum, the information in the crash dump
file reveals 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 Configuration mode. Look for error conditions or reasons that
can cause unexpected behaviors or restarts.
• Check the configuration settings in the control panel on the terminal
desktop or in FactoryTalk View ME Configuration mode.
Rockwell Automation Publication 2711P-UM006E-EN-P - January 2017
Troubleshooting Chapter 8
171