DRAFT - 11 December 2014DRAFT - 11 December 2014INM MTL4850_54 Rev4 29!Background diagnostics not running Return to MTL if alarm persists.!RAM test not running Return to MTL if alarm persists.!Bad call to diagnostic monitor Return to MTL if alarm persists.!RAM test copy address corrupted Return to MTL if alarm persists.!RAM corruption of TQ data in diag Return to MTL if alarm persists.!Incremental CPU test failed Return to MTL if alarm persists.Diagnostic session counter corrupted Return to MTL if alarm persists.!EEPROM Group1 CRC error Return to MTL if alarm persists.!EEPROM Group2 CRC error Return to MTL if alarm persists.!RAM corruption in TQ data in EHS Return to MTL if alarm persists.!An unused interrupt has occured Return to MTL if alarm persists.!PLL out of lock Return to MTL if alarm persists.!An illegal instruction has been encountered Return to MTL if alarm persists.!Cold start CPU test failed Return to MTL if alarm persists.!Bad call to program monitor Return to MTL if alarm persists.!Stack pointer corrupted Return to MTL if alarm persists.!Sequence error: Main initialisation Return to MTL if alarm persists.!Sequence error: Main startup Return to MTL if alarm persists.!Sequence error: First Field I/O Return to MTL if alarm persists.!Sequence error: Timer Queue Return to MTL if alarm persists.!Sequence error: Second Field I/O Return to MTL if alarm persists.!Sequence error: Event handler Return to MTL if alarm persists.!Sequence error: Diagnostic processing Return to MTL if alarm persists.!Module state corrupted Return to MTL if alarm persists.!RAM corruption of TQ data in main Return to MTL if alarm persists.!The 1ms timer ISR executed late Return to MTL if alarm persists.!The 1ms timer ISR executed early Return to MTL if alarm persists.!Program monitor failed to report Return to MTL if alarm persists.!Diagnostic monitor failed to report Return to MTL if alarm persists.!Cancelled timer can’t be found Return to MTL if alarm persists.!TQ Run out of sequence Return to MTL if alarm persists.Single or occasional occurrence of these events may be due to noise or interruptions of thepower supply, but multiple or frequent events might indicate problems with the installation,or with the module, in which case it should be returned to MTL for investigation.