Service Manual 3-7PEST (Print Engine Self Test)These tests occur after the POST tests have been run and postscript has beeninitialized. Error codes for the PEST tests are displayed on the front panel and are allin the 37,xxx series. Definitions for the PEST tests are provided in the Error CodeDefinition Table beginning on page 3-8.Fault CodesFault Code Definition TableThe following paragraphs will assist you in decoding the information contained in thefault codes:■ Failing system (XX,yyy.zz)■ Failing subsystem (xx,YYY.zz)■ Type of problem (xx,yyy.Zx)■ Print engine copy count (xx,yyy.zz:123) when the error occurredProgram faults are indicated by a 6 in the tenths place of the fault code(xx,yyy.6z). Unfortunately, there are too many program faults to enumerate them alland most program faults will not mean anything unless you are intimately familiarwith the code base. Some of the more common program faults are documented in thissection.CPU exceptions are indicated by a 7 in the tenths place of the fault code(xx,yyy.7z). The error code indicates both the PowerPC exception number and theregion of firmware that was executing when the exception occurred; Engine,PostScript, Network, or Operating System.NoteA CPU exception can either be caused by hardware or firmware error. Refer tothe infoSMART knowledge base for descriptions of the most common faults.Device faults are indicated by a 4 in the tenths place of the fault code(xx,yyy.4z). Indicates a hardware problem. Some of the more common device faultsare documented in this section.NoteIn customer mode, the printer will reboot each time an error occurs. If three ofthe same errors occur within 72 hours, or 1000 pages, then the fault will bedisplayed on the printers front panel. The fault codes are saved into non-volatilememory and can be retrieved from the fault history.
