D25 Failure Procedures

Background Information Required

Project number, purchase order number, serial number, or Z-number of the D25 that failed
Firmware (SALXXXX.YY) loaded on the D25
Config Pro 4 .zip archive of the configuration
Log of failure dates including steps required to recover the D25 to normal operation (reboot or
download configuration); approximate dates are sufficient for past failures

Recognizing a Crash
A D25 crash is characterized by no activity on the RUN LED, and the absence of the Wesmaint
welcome screen when you are connected to the Wesmaint port. Typically, when connecting to the
Wesmaint port of a crashed D25, you can see the Login: prompt in the top left corner of the screen,
which logs you directly into the D25 Application Monitor (>D25A).

Information to Capture Before Rebooting

To determine the cause of failure, we require that certain information be logged or captured from the
D25 before rebooting or downloading the configuration.

D25 Application Monitor Error Log

In the D25, the Application Monitor contains an error log that contains useful information about the
crash, including the exception vector information. Open the Application Monitor (D25A), type EL /P to
print the error log and capture the output of this command to a text file using Microsoft
HyperTerminal or equivalent serial software, or saving the print screen. Send this information to GE
Customer Service for analysis.

Check the Error Log for a Bus Error

If the error log contains an exception bus error (BusErr), only the error log is required. The typical
format of this error is shown below. The key words to look for are Exception and (BusErr).

Exception #002.(BusErr), Appl:B101, PC:002E2B2A, ADDR:01081268

If There Is No Bus Error, Collect Additional Diagnostic Data

While in the D25 Application Monitor, type the following commands while capturing the data to a text
file using Microsoft HyperTerminal or equivalent serial software:

a) QR /V - Displays the free RAM in the RTU

b) QR /N - Displays the free NVRAM in the RTU
c) QX - Displays the content of all message exchanges

Clear the Error Log and Reboot the D25

After you have collected all of the data, clear the error log (D25A>el/p) and reboot the RTU. If the
RTU resumes normal operation, proceed to collect diagnostic data (see below).

If the Default Configuration Is Loaded, Download the Correct Configuration

If the D25 loads the default configuration, the default Wesmaint login screen is shown as follows, and
the Wesmaint year is incorrect:

GE HARRIS
ENERGY CONTROL SYSTEMS
WESDAC 68K SYSTEM
LOGIN
If the D25 loaded the default configuration, download your configuration to recover the D25 to normal
operation.

Collect Diagnostic Data While the D25 Is Running

When investigating the repeatability of the crash, it is very important to gather information on the
RTU resources. We can look for trends in the resources to see if it could be related. When the D25 is
running normally again type the following commands in the Application Monitor, using the Microsoft
HyperTerminal text capture feature, or equivalent serial software to capture the data.

a) QR /V - Displays the free RAM in the RTU

b) QR /N - Displays the free NVRAM in the RTU
c) PR /P - Displays the CPU profile
d) EL /P - Displays the current monitor error log
e) QP - Displays which processes are suspended
f) QX - Displays the contents of all message exchanges

Continue to Monitor the Diagnostic Data

Depending on what we see from the initial captures and failure report, we may ask you to captures
this information intermittently between RTU failures.