Rockwell Automation ControlFLASH Firmware Upgrade Kit User Manual - Manual (Page 34)

34 Rockwell Automation Publication 1756-UM105E-EN-E - October 2012
Chapter 5 Use the Command Line
Troubleshooting The first step to finding errors in your application is to use the ControlFLASH
software log file. This file provides details about why your flashing script or
command line request did not complete. This log file resides in the
ControlFLASH directory. Before you spend a lot of time analyzing the log file
however, make sure that you check the following:
· Target devices you are flashing have the correct firmware kit installed.
· ControlFLASH software has the correct RSLinx communication paths set
up.
· The catalog number in your application matches the number in the
ControlFLASH GUI.
Error Log
You can open the Error Log by clicking View Log on the ControlFLASH
software dialog boxes.
Aborted Script File
If you have to abort a script file before completion or if the ControlFLASH
software aborted the script because it received an error from a device, you can re-
start that script. ControlFLASH starts flashing from the beginning of the script.
You can, however, use the SkipOnFirmwareMatch switch to tell ControlFLASH
software to not flash any devices that are already at the requested revision.