1.Division by zero
2.Program Sequencing error.
3.Real Time Clock program processing error. This indicates that insufficient time was available to process control information.
4.Invalid internal car position (such as  zero).
5.Bus Time-Out. Indicates that there is an addressing failure on the Cpu bus. The probable cause is PMI or DAR board which is not addressed properly or a board malfunction.
6.Invalid Motion Control sequence parameter. This is related to the Digital drive system.
7.The calculated target to floor was negative during the Decel or leveling mode. Verify the 'TLM' and 'DTA' parameters.
8.The velocity is 25% in excess of the contract speed. Verify the tape and the DPP sensor/magnet alignment, & associated wiring.
9.  Panic motion fault error: This occurs when:
    a.     There is an opposite direction between demand and tach.
    b.     There is a demand direction but no tach.
    c.     There is a tach direction but no demand.
10.Digital Tach error: Too much differential between the “Demand velocity (digital speed pattern) and the Digital speed reference (from DPP).Possible problems:                          
    a.     Improper setting of the Regulator Tach scaling (“T” Pot) or the 7PC Proportional and Integral Gain pots (SCR Drive).               b.     A too sensitive regulator tach fault, causing DF’ to drop. The car will not restart if ‘DF’ relay is OUT.                 
    c.     Verify the connections to DPP’ and the perforated tape alignment.                                                            
    d.     The drive system’ response (Make sure that motor field is producing proper torque).
11.Limit position reference error: When a terminal slowdown limit switch first opens, its reference position ('ULR & 'DLR') is compared against the Digital Position Count (DPC). If it is greater than the setting of 'LPE', an emergency slowdown will occur. Remedy this problem by adjusting 'ULR' and 'DLR'. Note that 'LPE' should be adjusted to a maximum of 20 when setup is completed.
12.Floor preset parity error: The parity from the preset signals ('OP', 'R1' thru 'R16') is invalid. Verify the preset magnets if this occurs only at one floor, or the sensors and associated wiring if this occurs consistently.
13.Invalid Direction error. Mismatch between the up or down direction relay and the tach rotation as per UT or DT. Verify the tach connections for positive Tach voltage at terminal T+U for up direction.
14.Terminal limit position error. The position of the car was invalid at the bottom most or top most limit switch (SD1 or SU1). Check to see if there were preset errors prior to this.(See error 15)
15.Position preset error. Error 12 is when there is a parity error from the input signals, in that case the position of the car is not altered. When there is a preset position error, the car position is altered, and the DPP will be reset to the floor position reference when the car leaves the floor. run the car floor to floor to ascertain that the floor preset signals are valid. This error is more  likely to occur after an emergency stop, or from inspection to auto operation. It is also possible for DPP to go off but it is not  usualy the source of the problem. 
16. Dispatch communication time-out. verify the serial communication link connections to each controller, this is usually the problem the the dispatch controller or car 1 for duplex instalation is operational
17. Motion time out. This occurs when too much time elapsed during a run sequence. Verify the drive system and associated connections.
18. Control response time-out. this occurs when a start sequence is initiated from the computer  thru the Up or Down output modules, and BK relay fails to energise. Verify the connections to the Up and Down output modules, the DHT an the MC circuitry, and the connections to the ‘BK’ input module on PMI ~1. 11/7/84 Definition
19. Pilot direction sequence error.
20. Digital Tach loss time--out. No DPP input signal. This will  initiate an emergency slowdown. 
21.EEPROM Read/Write error. This will prevent the car to operate.Verify the content. of   PAR, .FCP ULR,DLR,&TSV with the terminal
22. Terminal limit switch emergency; slowdown. The velocity of the car was greater than the TSV  adjustment at the  terminal landing.Verify  the car velocity when the terminal limit switches open with ULB  and DLB, adjust either the distance (increase) of the limit from the floor to increase the “freeze” velocit.y (this will also change the limit position ULR &   DLR or increase the value of TSV (refer to adjustment manual).
23.DAR tach fault. if th.e analog demand velocity is greater than the  preset terminal slowdown velocity, a tach fault will occur and the     velocity of the car will be clamped to the FAULT pot setting. 
24.Drive fault. Indicates a tach fau1t from the. regulator (REG) board. This error occurs when there is too much difference between the analog demand velocity and the analog tach reference veiocity
25.  A Start Sequence Error. A start sequence was initiated, in auto or   inspection, while a drive fault from wither the DF relay or from   the DAR board. Remove the fault trip condition on the regulator board (REG-1) by pressing the button located behind the test points. Also verify the associated wiring.
26.Motion Fault error. Invalid Up or Down pilot.
27.BK or MC control failure. If either BK or Mc controls are closed when no directional relays are energised, the processor start .sequence from occuring.
28.The brake switch did not function after time (this is va1id on1y for  Jobs having a brake switch).
29.Slowdown Terminal Limit switch error.. This occurs when the. digital car position is greater than the respective setting of the up     terminal limits (ULR’). The reverse for the down limit 
30.The car is moving without a demand velocity from the. CPU.
31.Invalid Next Car Up signal from the dispatcher.
35.Invalid Next Car Up signal from the dispatcher.
36. Variable having wrong value
37.  ETS error. Thew car velocity was greater thans the ETS velocity but the ETS board did not activate the ETS speed check output  
38.  ETS error. The ETS velocity speed check output was activated indicating that the car was traveling faster than the ETS speed but the cars calculated velocity was less than ETS speed 
39.ETS error. The ETS speed check output was activated but the car was not moving. This indicates that the ETS speed check output failed on .
40.   Level velocity Too high when car reached the final leveling. The velocity of the car was greater than 70 fpm at the 2 inch point .
41. Trying to relevel in level mode. This is a software error and. should not occur.
42. Doing a final stop in wrong digitizer mode. This is a software error and shçuld not occur 
43.High velocity when doors are opened. The gate and lock opened when the car velocity was greater than the maximum level or re-level velocity.
44.The gate and lock (GLR) input did not make when the doors were fully closed
45.The door closed limit (DCL) input did not make when the doors closed
46.The door open limit (DOL) input did not make when then doors open.
50.The generator voltage increased when the CPU was not trying to run the car The SUF input was activated while the car was trying to move. The car CPU must be powered off and then on to allow the car to run.   .
51.The SUF input did not occur during a run. On cars with MG sets the SUF relay must pick-up each run to indicate that the relay  is working. .
52.  Car out of Mid level zone with gate and lock input not made (GLE). The car CPU must be powered off then on to allow the car to run.  
53.  Car out of Mid level zone with gate and lock input not made (GLE). The car CPU must be powered off then on to allow the car to run.  
54.Up or Down tach motion detected 1.5 seconds after the brake dropped
55.SCR tempature overload activated. 
56.Max run timer time-out during a run. Check the max run timer (MRT) adjustment. 
57. An interrupt error has occured in the processor, this error only applies to 18603 CPUs, the internal program  wfll compensate for the interrupt error. If the CPUs do not  lock up. there is no problem’and this error can be ignored.  Or. set bit 5,9 
58. An auto fault reset has occurred. A fault condition(DrivetMG or Trip/SCR) which was caused by the drive System has been reset by the CPU. If the fault occurs more than 3 times within an hour, the CPU will not reset automatically. After the 3rd time, the fault must be reset manually.