Andromeda

Partial
Completion13%

Game Plan1985game-plan.andromeda.1985 Updated 2026-08-30

Wire it up

what an authoring tool needs first
Bind this ROM
andromed

2 ROM sets resolve to this machine. Clones share the definition unless a hardware difference is listed.

Controller platform
Not determined
Displays

No display inventory recorded yet.

Address space
Switches
4–39 (20)
Solenoids
15–32 (2)

Coverage

Partial

Real evidence exists, but authoring requirements are still missing or in conflict. Verify before shipping a table.

Completion13%

Progress is derived from the fixed author-readiness requirements. It helps rank unfinished work, but only a 100% author-ready definition passes the publication gate.

Catalog Identity
validated
Address Enumeration
unknown
Semantic Naming
unknown
Physical Wiring
unknown
Mechanisms
unknown
Variant Coverage
candidate
Recreation Knowledge
unknown
Still missing · 14
Driver MappingController PlatformInput EnumerationInput SemanticsOutput EnumerationOutput SemanticsDisplay InventoryMechanism InventoryMechanism BehaviorPolarityVariant DifferencesRecreation NotesProvenanceSpatial Placement

Switches

The addresses PinMAME reports as closed. Numbers are the public API values, not matrix hardware pins.

20 addresses

Switch map

Sequential addresses, grouped in columns of eight.

used unused
 
+0
+1
+2
+3
+4
+5
+6
+7
1–8
9–16
17–24
25–32
33–40
Hover or tap an address to identify it.
20 shown
# Name Device ID Evidence
4
Sw4
switch.sw4 candidate
9
Rubber Band004
switch.rubber-band004 candidate
11
Drain
switch.drain candidate
12
Bumper2
switch.bumper2 candidate
13
Bumper3
switch.bumper3 candidate
14
Bumper4
switch.bumper4 candidate
15
Bumper1
switch.bumper1 candidate
16
Right Sling Shot
switch.right-sling-shot candidate
25
Sw25
switch.sw25 candidate
27
Sw27
switch.sw27 candidate
28
Sw28
switch.sw28 candidate
29
Sw29
switch.sw29 candidate
30
Sw30
switch.sw30 candidate
31
Sw31
switch.sw31 candidate
32
Sw32
switch.sw32 candidate
35
Sw35
switch.sw35 candidate
36
Sw36
switch.sw36 candidate
37
Sw37
switch.sw37 candidate
38
Sw38
switch.sw38 candidate
39
Sw39
switch.sw39 candidate

Controlled devices

Everything the ROM can energise, grouped the way a table author builds it.

Coils, magnets & motors

2
2 shown
# Name Device ID Evidence
15
Sol Shift
coil.sol-shift candidate
32
Sol Gi
coil.sol-gi candidate

Recreation notes

Working knowledge that has no schema field yet — edition differences, tuning values, pitfalls.

Coverage: partial - machine identity plus candidate-only I/O attachments. Playfield devices, wiring, mechanisms, and behavior are evidenced only as unverified candidates.

This record was promoted from the generated catalog stub stub.pinmame.andromed by the catalog-wide identity pass of 2026-08-29. The promotion resolves machine identity and carries the catalog's residual driver grouping over unchanged, the platform and device attachments below were added by the 2026-08-29/30 candidate passes and assert nothing beyond candidate provenance. Every requirement in the definition's coverage.missing is genuinely outstanding.

Identity

  • PinMAME catalog: root driver andromed, description "Andromeda", manufacturer "Game Plan", catalog year "1985".
  • OPDB record GrXOZ-MLyb0 (IPDB 73) names this machine "Andromeda" (Game Plan, manufacture date 1985-01-09); the resolved identity rests on the agreement of the PinMAME catalog and this reviewed mapping.
  • The definition's driver list is exactly the clone tree PinMAME declares under andromed; whether every listed driver really runs on this physical machine is unverified.

Drivers this record holds

  • andromea (1985, Game Plan, clone of andromed).
  • andromed (1985, Game Plan).

VPX script candidates (candidate)

  • 1 retained community table script(s) declare this machine's driver; their extracted switch/lamp/solenoid/GI candidates are carried as 22 candidate devices. When curator work weighs sources, a retained script outranks emulator-derived candidates for runtime semantics, but every device here is still a candidate until a known-working table is verified against this exact physical machine.

What a curator must establish next

Controller platform from the pinned PinMAME driver source; full input, output, and display enumeration with semantic names; physical wiring and polarity; mechanism inventory and behavior; variant differences across the clone tree; recreation knowledge from a manual, schematic, or known-working table; runtime provenance; and a normalized spatial placement for every physical device. No manual, schematic, or runtime-harness evidence is retained for this machine yet; the candidate sections above are the only retained I/O evidence so far.

ROM sets

Every driver that resolves to this physical machine.

ROM set Description Year Parent Hardware
andromedAndromeda 1985——
andromeaAndromeda (alternate set) 1985andromed—

Parent set: andromed — clones share this definition unless a hardware difference is noted.

Evidence

Every claim above traces to one of these. When they disagree: a known-working VPX script wins on controller addresses and causality, the manual wins on wiring and construction, pinned PinMAME wins on emulator routing and display layout.

  • PinMAME catalog

    BSD-3-Clause

    pinmame.catalog.8371478a7640

    PinmameGetGames

    by
    PinMAME contributors
    rev
    8371478a7640
  • VPX script

    vpx-script.e042333ad7ba8e96

    vpx-standalone-scripts: Andromeda (Game Plan 1985) v4/Andromeda (Game Plan 1985) v4.vbs

    by
    Authors credited in Andromeda (Game Plan 1985) v4/Andromeda (Game Plan 1985) v4.vbs and repository contributors
    rev
    15d112648a1b
    sha256
    e042333ad7ba…

Something wrong or missing?

This definition still has 14 unmet requirements, listed under Missing data below. Fixes belong in the definition itself — editing on GitHub forks it for you and opens the pull request.

Cite a source for anything you change — a manual page, a line in a working VPX script, PinMAME source, or a reading from the machine's own service menu. Claims without provenance cannot be validated.

Missing data

What this game definition still needs to reach 100% and become author-ready.

  • ROM compatibility

    Verify which PinMAME drivers and firmware variants belong to this physical machine.

  • Controller hardware

    Identify the controller platform and validate its public address and routing rules.

  • Complete input inventory

    Account for every switch, service input and diagnostic address, including unused positions.

  • Input functions

    Validate which physical sensor or cabinet control each input represents and when it activates.

  • Complete output inventory

    Account for every coil, motor, lamp, flasher and general-illumination circuit, including unused addresses.

  • Output functions

    Validate the physical device, function and fitted quantity behind each output binding.

  • Displays

    Verify every display, its layout and its controller bindings.

  • Mechanism inventory

    Document every mechanism, its moving parts, actuators, sensors and connections.

  • Mechanism behavior

    Validate mechanism operation, ball paths, home positions, startup and reset behavior.

  • Switch construction and polarity

    Verify normally open or closed contacts and how PinMAME delivers their active states.

  • Edition and firmware differences

    Document supported hardware and firmware differences without combining incompatible editions.

  • Recreation knowledge

    Complete the source-backed behavior and assembly notes needed to recreate the machine.

  • Evidence and sources

    Back the remaining claims with attributable sources, exact locators, retained excerpts and verified hashes.

  • Physical device locations

    Establish validated playfield locations for every physical sensor, actuator and light emitter, including bulb counts and justified projections.