Torneo

Partial
Completion19%

Recel1978recel.torneo.1978 Updated 2026-10-05

recel/torneo-1978.mdrecel/torneo-1978.json

Wire it up

what an authoring tool needs first
Bind this ROM
r_torneor_torneoa

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

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
validated
Recreation Knowledge
unknown
Still missing · 13
IdentityController PlatformInput EnumerationInput SemanticsOutput EnumerationOutput SemanticsDisplay InventoryMechanism InventoryMechanism BehaviorPolarityVariant DifferencesRecreation NotesProvenance

Recreation notes

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

Coverage: partial - grouping only. Machine identity beyond the PinMAME catalog, and everything about playfield devices, wiring, mechanisms and behaviour, is not evidenced yet.

Why one record holds two drivers

PinMAME declares both r_torneo and r_torneoa as direct clones of recel, the System III BIOS (machines/partial/recel/system-iii-1978.json), so the catalog's clone-root rule gives each its own root. They are one physical game: recelgames.c documents r_torneo as the circulating dump of the Torneo PROM with one wrong byte at 0x809, which makes the ball counter pass its limit on the first drain, and r_torneoa as the one-byte repair of that same PROM (0xF6 0x74 -> 0x72), after which the counter walks three balls like every sibling game. Both hashes are marked BAD_DUMP; the repair is a reconstruction, not a read of a physical PROM.

Drivers this record holds

  • r_torneo (1978, Recel, clone of recel).
  • r_torneoa (1978, Recel, clone of recel).

What a curator must establish next

IPDB/OPDB identity, the System III controller platform, full input, output and display enumeration with semantic names, wiring and polarity, mechanisms, and spatial placement. No manual, table, ROM analysis or harness evidence is retained.

Sources

  • PinMAME b7a60eb0dd9722f5397fc296987d94528ab111ff, src/wpc/recelgames.c:160-190.

ROM sets

Every driver that resolves to this physical machine.

ROM set Description Year Parent Hardware
r_torneoaTorneo (corrected dump, 3 balls)
PinMAME's one-byte repair of the same Torneo PROM (to_fixed.c5, 0xF6 0x74 -> 0x72), a reconstruction rather than a read of a physical PROM; the ball counter then walks three balls as every sibling game does. Same physical machine and the same System III board.
1978recelidentical
r_torneoTorneo
The circulating Torneo PROM dump (to.c5, BAD_DUMP). PinMAME's recelgames.c comment explains that one wrong byte at 0x809 makes the ball counter pass its limit on the first drain.
1978recelidentical

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

    b7a60eb0dd97
    by
    PinMAME contributors
    rev
    b7a60eb0dd97

  • PinMAME source

    BSD-3-Clause

    pinmame.core.b7a60eb0dd97

    src/wpc/recelgames.c:160-190 (Torneo comment blocks, r_torneo and r_torneoa ROM_START and CORE_CLONEDEFNV)

    src/wpc/recelgames.c
    by
    PinMAME contributors
    rev
    b7a60eb0dd97

Something wrong or missing?

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

  • Machine identity

    Verify the physical title, manufacturer, year and edition against attributable sources.

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