System III

Partial
Completion38%

Recel1978recel.system-iii.1978 Updated 2026-10-05

recel/system-iii-1978.mdrecel/system-iii-1978.json

Wire it up

what an authoring tool needs first
Bind this ROM
recel

1 ROM set 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

Coverage

Partial

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

Completion38%

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
not_applicable
Mechanisms
not_applicable
Variant Coverage
validated
Recreation Knowledge
candidate
Still missing · 10
Input EnumerationInput SemanticsOutput EnumerationOutput SemanticsDisplay InventoryMechanism InventoryMechanism BehaviorPolarityRecreation NotesProvenance

Recreation notes

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

Coverage
partial system-software classification; not a physical game definition

Classification

PinMAME registers recel as GAMEX(1978,recel,0,RECEL,recel,recel,ROT0,"Recel","System III",NOT_A_DRIVER) in recelgames.c, and driver.c lists it as "System III (not a game)". Its romset holds only the two spider-chip dumps of the shared System III program (a2361.b1, a2362.b2); recel.h calls it the BIOS common to every machine, which ships no game PROM of its own. Every Recel, Interflip and Inder System III game (r_*) is a clone of it that adds its own game PROM.

It is therefore system software, not a playfield an author can recreate, and the catalog keeps every r_* game out of this record: since PinMAME b7a60eb0 a reported NOT_A_DRIVER parent ends clone-root resolution (resolve_root_driver in src/pinmame_game_defs/catalog.py), the same rule PinMAME's own drivers apply when they look for a game's root (while (rootDrv->clone_of && (rootDrv->clone_of->flags & NOT_A_DRIVER) == 0)), so each game is its own physical record.

Remaining documentation

The shared program's behaviour, the System III controller contract and the board hardware are not documented here. That keeps this record partial without affecting physical-game coverage.

Sources

  • PinMAME b7a60eb0dd9722f5397fc296987d94528ab111ff, src/wpc/recelgames.c:67-73, src/wpc/recel.h:103-126 and src/wpc/driver.c:1016.

ROM sets

Every driver that resolves to this physical machine.

ROM set Description Year Parent Hardware
recelSystem III 1978——

Parent set: recel — 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.b7a60eb0dd97

    PinmameGetGames: recel (flags 0x4000 NOT_A_DRIVER)

    b7a60eb0dd97
    by
    PinMAME contributors
    rev
    b7a60eb0dd97

  • PinMAME source

    BSD-3-Clause

    pinmame.core.b7a60eb0dd97

    Source locations

    src/wpc/recelgames.c:67-73 (INIT_RECEL(recel), RECEL_BIOS_ROMSTART(recel), GAMEX(...,"System III",NOT_A_DRIVER)); src/wpc/recel.h:103-126 (RECEL_BIOS_ROMSTART comment: the shared program common to every machine, no game PROM); src/wpc/driver.c:1016

    src/wpc/recelgames.csrc/wpc/recel.hsrc/wpc/driver.c
    by
    PinMAME contributors
    rev
    b7a60eb0dd97

Something wrong or missing?

This definition still has 10 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.

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

Missing data

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

  • 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.

  • 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.