Robocop

Partial

Data East1989DATAEASTdata-east.robocop.1989

OPDB IPDB data-east/robocop-1989.mddata-east/robocop-1989.json

Wire it up

what an authoring tool needs first
Bind this ROM
robo_a34

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

Controller platform
pinmame.dataeast

PinMAME already reports logical active state. Do not invert again in the table — normally-closed is a physical fact recorded per switch, not a runtime transform.

Displays

No display inventory recorded yet.

Address space
Switches
14–47 (15)
Solenoids
1–30 (16)

Coverage

Partial

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

Completion19%

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 · 13
Driver MappingInput 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.

15 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
41–48
Hover or tap an address to identify it.
15 shown
# Name Device ID Evidence
14
Sw14
switch.sw14 candidate
17
Sw17
switch.sw17 candidate
18
Sw18
switch.sw18 candidate
19
Sw19
switch.sw19 candidate
20
Sw20
switch.sw20 candidate
21
Left Sling Shot
switch.left-sling-shot candidate
22
Right Sling Shot
switch.right-sling-shot candidate
25
Sw25
switch.sw25 candidate
26
Sw26
switch.sw26 candidate
27
Sw27
switch.sw27 candidate
31
Sw31
switch.sw31 candidate
32
Sw32
switch.sw32 candidate
44
Sw44
switch.sw44 candidate
46
Bumper1
switch.bumper1 candidate
47
Bumper2
switch.bumper2 candidate

Controlled devices

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

Coils, magnets & motors

16
16 shown
# Name Device ID Evidence
1
Flash62
coil.flash62 candidate
2
Flash61
coil.flash61 candidate
3
Flash60
coil.flash60 candidate
4
Flash59
coil.flash59 candidate
5
Flash58
coil.flash58 candidate
6
Flash57
coil.flash57 candidate
7
Sol7
coil.sol7 candidate
8
Sol8
coil.sol8 candidate
9
Flash9
coil.flash9 candidate
11
Sol GIUpdate
coil.sol-giupdate candidate
12
Flash12
coil.flash12 candidate
13
Flash13
coil.flash13 candidate
14
Sol14
coil.sol14 candidate
15
Sol15
coil.sol15 candidate
16
Sol Kickback
coil.sol-kickback candidate
30
Sol Ball Popper
coil.sol-ball-popper 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.robo_a34 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 robo_a34, description "Robocop (3.4)", manufacturer "Data East", catalog year "1989".
  • OPDB record Grlxe-MJ916 (IPDB 1976) names this machine "Robocop" (Data East, manufacture date 1989-11-01); 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 robo_a34; whether every listed driver really runs on this physical machine is unverified.

Drivers this record holds

  • robo_a29 (1989, Data East, clone of robo_a34).
  • robo_a30 (1989, Data East, clone of robo_a34).
  • robo_a34 (1989, Data East).

PinMAME source contract (candidate)

  • The pinned PinMAME source declares robo_a34 at src/wpc/degames.c:279 with machine module de_mDEAS1; the definition declares controller platform pinmame.dataeast from it.

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 31 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

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
robo_a34Robocop (3.4) 1989——
robo_a30Robocop (3.0) 1989robo_a34—
robo_a29Robocop (2.9) 1989robo_a34—

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

Pinball memory maps

External source LGPL-3.0-only3 maps

RAM layouts published by an independent project and mirrored here at a pinned commit. They are not part of this machine’s definition: nothing below was used as evidence for the definition, and none of it counts towards coverage. Check claims against the upstream project.

Upstream
tomlogic/pinball-memory-maps
Commit
d8693b9

This program makes use of content from the Pinball Memory Maps project.

robo_a29.map.json

dataeastv5format 0.8

maps/dataeast/version2/robo_a29.map.json

Applies to ROMs
robo_a29
Sections
adjustmentsgame_statehigh_scoresmode_champions
Map JSONMap sourcePlatform JSONPlatform source

dataeast defines the RAM layout this map’s offsets are read against — the map is not interpretable without it.

robo_a30.map.json

dataeastv5format 0.8

maps/dataeast/version2/robo_a30.map.json

Applies to ROMs
robo_a30
Sections
adjustmentsgame_statehigh_scoresmode_champions
Map JSONMap sourcePlatform JSONPlatform source

dataeast defines the RAM layout this map’s offsets are read against — the map is not interpretable without it.

robo_a34.map.json

dataeastv6format 0.8

maps/dataeast/version2/robo_a34.map.json

Applies to ROMs
robo_a34
Sections
adjustmentsgame_statehigh_scoresmode_champions
Map JSONMap sourcePlatform JSONPlatform source

dataeast defines the RAM layout this map’s offsets are read against — the map is not interpretable without it.

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

    8371478a7640
    by
    PinMAME contributors
    rev
    8371478a7640

  • PinMAME source

    BSD-3-Clause

    pinmame.core.8371478a7640

    src/wpc/degames.c:279 (machine module de_mDEAS1)

    src/wpc/degames.c
    by
    PinMAME contributors
    rev
    8371478a7640

  • VPX script

    vpx-script.0c6ce7e4995bdf01

    vpx-standalone-scripts: Robocop (Data East 1989)_drakkon(mod_1.2)/Robocop (Data East 1989)_drakkon(mod_1.2).vbs

    15d112648a1b
    by
    Authors credited in Robocop (Data East 1989)_drakkon(mod_1.2)/Robocop (Data East 1989)_drakkon(mod_1.2).vbs and repository contributors
    rev
    15d112648a1b
    sha256
    0c6ce7e4995b…

Something wrong or missing?

This definition still has 13 unmet requirements, listed under Coverage above. 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.

Edit the definition Edit the note Report a problem
Before you startCONTRIBUTING.mdschemas/machine.schema.jsondocs/MACHINE_DEFINITIONS_PLAN.md How to read a definition

Same platform

Monday Night FootballData East · 1989Playboy 35th AnniversaryData East · 1989Back to the FutureData East · 1990King KongData East · 1990Phantom of the OperaData East · 1990The SimpsonsData East · 1990