Jump to content

Help:Writing a repair guide

From RetroTechCollection
Revision as of 22:11, 26 March 2026 by Josh (talk | contribs) (Created Help:Writing a repair guide)
(diff) โ† Older revision | Latest revision (diff) | Newer revision โ†’ (diff)
๐Ÿ”ง Writing a Repair Guide
Templates and Best Practices for RTC Wiki Repair Articles



Repair guides are the heart of the RetroTechCollection Wiki. This page explains how to write high-quality maintenance, troubleshooting, and capacitor replacement guides.

Article Types

[edit source]

We use three standard guide types for each device:

Type Purpose Naming Convention
General Maintenance Preventive care, cleaning, inspection, common failure points Device Name General Maintenance
Troubleshooting Systematic fault diagnosis with symptoms, causes, and actions Device Name Troubleshooting Guide
Capacitor Replacement Complete cap lists, replacement procedures, post-recap checks Device Name Capacitor Replacement Guide

General Maintenance Guide Template

[edit source]

A maintenance guide should cover:

  1. Regular Cleaning โ€” external case, internal components, connectors
  2. Power Supply Checks โ€” voltage measurements, PSU health
  3. Connector & Socket Maintenance โ€” cleaning, DeoxIT, contact care
  4. Common Failure Points โ€” what breaks most often and why
  5. Cooling System โ€” fans, heatsinks, thermal material
  6. Recommended Tools โ€” what you need for maintenance
  7. Preventive Maintenance Checklist โ€” periodic tasks

Key Principles

[edit source]
  • Be specific โ€” include exact voltages, temperatures, and part numbers
  • Include measurements โ€” expected voltage ranges with tolerances (e.g., "4.9โ€“5.1 V")
  • Reference board revisions โ€” note when procedures differ between hardware versions
  • Warn about dangers โ€” CRT discharge, mains voltage, ESD sensitivity

Troubleshooting Guide Template

[edit source]

A troubleshooting guide should use diagnostic tables with three columns:

{| class="wikitable styled-table" style="width:100%; text-align:center;"
|+ '''Problem Category'''
|-
! Symptom !! Probable Cause !! Recommended Action
|-
| Description of what the user sees || What's likely wrong || What to do about it
|}

Standard sections:

  1. Preliminary Checks โ€” basic power and visual inspection
  2. Voltage Reference Table โ€” all power rails with expected values
  3. No Power / Dead Unit โ€” power supply chain faults
  4. No Video / Display Issues โ€” video output problems
  5. No Audio โ€” sound faults
  6. Input Device Issues โ€” controller/keyboard faults
  7. Disc/Media Errors โ€” optical drive or floppy issues (if applicable)
  8. Component-Level Tests โ€” clock frequencies, oscilloscope readings, chip-level diagnostics
  9. Quick-Fix Flowcharts โ€” decision trees for common problems

Writing Good Diagnostic Tables

[edit source]
  • Start with the most common cause โ€” list probable causes in priority order
  • Be actionable โ€” every "Recommended Action" should tell the reader exactly what to do
  • Include test values โ€” "Measure 5V at pin 21" is better than "Check the power supply"
  • Cross-reference โ€” link to the maintenance guide and capacitor guide

Capacitor Replacement Guide Template

[edit source]

A capacitor replacement guide needs:

  1. Visual Inspection Signs โ€” what failing caps look like
  2. Complete Capacitor List โ€” table with designator, value, voltage, type, and location
  3. Board Revision Differences โ€” note where cap layouts change between revisions
  4. Replacement Procedure โ€” step-by-step desoldering and soldering instructions
  5. Post-Recap Voltage Checks โ€” expected values and acceptable ripple
  6. Recommended Tools & Parts โ€” specific equipment needed

Capacitor Table Format

[edit source]
{| class="wikitable styled-table" style="width:80%; text-align:center;"
|+ '''Board Name Capacitor Specifications'''
|-
! Designator !! Capacitance !! Voltage !! Type !! Notes
|-
| C1 || 100 ยตF || 6.3 V || SMD || Power filtering
|}

Writing Style

[edit source]

Follow the RTC Wiki style guidelines:

  • Factual and specific โ€” state what it IS, not what it MEANS
  • Dry technical writing โ€” let the facts speak; skip commentary
  • No AI writing patterns โ€” avoid "pivotal", "crucial", "testament to", "enduring legacy"
  • Direct โ€” subject-verb-object, no fluff
  • Source everything โ€” use <ref>{{cite web ...}}</ref>

Using Styled Tables

[edit source]

Add this at the top of your article for consistent table styling:

<templatestyles src="Template:StyledTable/styles.css" />

Then use class="wikitable styled-table" on your tables.

Cross-Linking

[edit source]

Every repair guide should link to:

  • The main article for the device
  • The other two guide types (maintenance โ†” troubleshooting โ†” capacitor guide)
  • Relevant common pages (e.g., CRT Discharge Procedure, Sad Mac Error Codes)

See Also

[edit source]