Jump to content

IBM 5110 Troubleshooting Guide

From RetroTechCollection

This guide documents fault diagnosis for the IBM 5110 Computing System. The 5110 inherits the IBM 5100's PALM processor and integrated 5-inch CRT, so much of the troubleshooting practice translates directly from the 5100. The 5110 adds the external IBM 5114 Diskette Unit (8-inch floppy drives), IEEE-488 (HP-IB) bus, RS-232 channels, and EBCDIC encoding, each with their own diagnostic surface.

Reference Documents

[edit | edit source]
  • SY31-0553-2 โ€” IBM 5110 System Maintenance Analysis Procedures (MAP), January 1979 โ€” the per-symptom troubleshooting decision tree.[1]
  • SY31-0550-2 โ€” IBM 5110 Computer Maintenance Information Manual (MIM), February 1979 โ€” theory of operation and diagnostic procedures.
  • SY31-0551-1 โ€” IBM 5114 Diskette Unit Maintenance, January 1979 โ€” 8-inch floppy drive diagnostics.
  • SY31-0557-0 โ€” IBM 5110 Async Communications, January 1978 โ€” comms adapter diagnostics.
  • SA21-9311-1 โ€” Customer Support Functions, October 1978 โ€” operator-level acceptance test.

Initial Diagnosis Workflow

[edit | edit source]

5110 power-on sequence:

  1. Power LED on rear illuminates.
  2. PSU rails stabilise (5110 + 5114 if attached).
  3. Executable ROS self-test runs.
  4. Language interpreter loads from Language ROS.
  5. Language banner ("BASIC READY" or "APL READY") appears on the 5-inch CRT.

If any of these does not occur, stop and diagnose at that stage.

Stage 1 โ€” No Power

[edit | edit source]
  • Mains lead, switch, fuse check on the 5110.
  • If a 5114 is attached, check the 5114 mains lead and switch separately โ€” they have independent power.
  • Verify PSU rails at the planar power connector.

Stage 2 โ€” Power But No Display

[edit | edit source]

Same diagnostic surface as the IBM 5100:

  • Front-panel "Display Registers / RAM Hex" switch โ€” confirms video chain.
  • Reseat ROS / RWS / PALM cards.
  • Check CRT anode HV.

Stage 3 โ€” Banner Wrong / Garbled

[edit | edit source]
  • Language ROS bit error โ€” reseat Language ROS.
  • Toggle APL / BASIC โ€” if one banner is clean and the other garbled, isolated to the failed Language ROS.
  • On the 5110 the EBCDIC character set is in use โ€” verify that the garble isn't actually correct EBCDIC characters being read as 5100 encoding.

Stage 4 โ€” System Won't Read / Write Diskettes (5114)

[edit | edit source]
  • No drive activity at all โ€” cable between 5110 and 5114 unseated, or 5114 PSU dead.
  • Drive spins but won't read โ€” head dirty; head alignment; drive belt slipping.
  • Read OK, write produces unreadable diskettes โ€” head alignment, write-protect sensor stuck.
  • Sporadic CRC errors โ€” drive belt aged, oxide shedding from old diskettes, head dirty.

Stage 5 โ€” IEEE-488 Bus Not Working

[edit | edit source]
  • Cable unseated.
  • Terminator missing or failed.
  • IEEE-488 controller card on 5110 reseat.
  • Test with a known-good instrument.

Diagnostic ROS

[edit | edit source]

Same keyboard sequence at power-on as the IBM 5100; enters Diagnostic ROS for read / write access to RAM, video memory, PALM registers, interrupt vectors and clock counter.[2]

The 5110 MIM SY31-0550 documents the Diagnostic ROS error codes specific to the 5110 (Section IV).

Customer Acceptance Test

[edit | edit source]

The Customer Acceptance Test (CAT) for the 5110 is documented in SA21-9311-1 (Customer Support Functions). It uses a customer test diskette (on Model 2 or 3) or test tape cartridge (on Model 1) and exercises:

  • RAM (full pattern test).
  • Tape drive (Model 1).
  • Diskette drives (5114, if attached).
  • IEEE-488 bus (if cable + terminator present).
  • RS-232 channels (loopback or external).
  • Communications Adapter (if fitted).
  • CRT and keyboard.

PALM Diagnosis

[edit | edit source]

Same as the IBM 5100 โ€” PALM gate arrays are unobtainium. Reseat the PALM edge connector before suspecting failure. PALM-specific check-stop codes in the MIM identify which gate array has failed when a failure is real.

ROS / RWS Memory Faults

[edit | edit source]
  • Garbled banner โ€” Language ROS bit error.
  • Refusal to complete Executable ROS self-test โ€” Executable ROS bit error or PALM fault.
  • RAM size mismatch on banner โ€” RWS card failure; reseat each 16 KB module.

Tape Drive Faults (Model 1)

[edit | edit source]

Same procedure as IBM 5100 Troubleshooting Guide. Belt, capstan, head, alignment, in that order.

8-Inch Floppy Drive Faults (5114)

[edit | edit source]
  • No drive activity โ€” 5114 PSU dead, or cable to 5110 unseated.
  • Drive spins but won't read โ€” head dirty, alignment drift, drive belt slipping.
  • Won't load head โ€” head load solenoid fatigued or stuck.
  • Write errors โ€” write-protect sensor, head alignment.
  • CRC errors โ€” drive belt aged, oxide shedding from old Diskette 2D media, head dirty.
  • Spindle won't spin โ€” motor brushes worn.

The 5114 MIM SY31-0551 documents per-symptom diagnosis with FRU swap decision tree.

CRT Faults

[edit | edit source]

Same as the IBM 5100 โ€” flyback, deflection, cathode emission.

IEEE-488 Bus Diagnosis

[edit | edit source]
  • Bus hung โ€” terminator missing or failed.
  • Controller initialisation timeout โ€” PALM IEEE-488 controller card; reseat or replace.
  • Single instrument not responding โ€” instrument address conflict; verify dipswitch settings on the instrument.
  • All instruments timing out โ€” cable, terminator, or 5110 IEEE-488 interface failure.

RS-232 / Async Communications Faults

[edit | edit source]

The Async Communications Feature (SY31-0557) carries common RS-232 faults:

  • Wrong baud rate โ€” verify dipswitch settings on the adapter and target.
  • Garbled output โ€” parity, stop bits, character set mismatch.
  • No output โ€” cable; pin 2 / pin 3 swap.
  • Cable wired straight-through vs crossed (null modem) โ€” verify the target device's pinout.

Common Field Symptoms and Resolutions

[edit | edit source]
  • Won't power on โ€” Mains, fuse, switch, PSU primary.
  • Power LED but no display โ€” PSU bulk filter caps shot; see IBM 5110 Capacitor Replacement Guide.
  • Banner appears, system hangs on keystroke โ€” keyboard or PALM input handling.
  • Garbled banner โ€” Language ROS or socket oxidation.
  • Tape works on 5110 but data won't transfer to a 5100 โ€” EBCDIC vs 5100-specific encoding mismatch (not a fault).
  • 5114 floppy not detected โ€” cable or 5114 PSU.
  • Floppy reads OK but writes corrupt โ€” head alignment; or aged diskette media.
  • IEEE-488 instrument not responding โ€” addressing, terminator, cable.
  • Random reboots / hangs โ€” bulk filter cap ESR rising; recap PSU.

Diagnostic Workflow Summary

[edit | edit source]
  1. Power on; observe LED, fan, display chain.
  2. If no power on 5110, suspect 5110 PSU. If no power on 5114, suspect 5114 PSU.
  3. If power but no display, suspect Executable ROS, PALM, or CRT chain.
  4. If display but garbled banner, reseat ROS and try the other language.
  5. Enter Diagnostic ROS and run the documented self-tests.
  6. Run the Customer Acceptance Test from diskette (Model 2/3) or tape (Model 1).
  7. Cross-reference any check-stop code against MAP document SY31-0553.
[edit | edit source]

References

[edit | edit source]