Canasta '86'

Partial

Inder (Spain)1986inder-spain.canasta-86.1986

inder-spain/canasta-86-1986.mdinder-spain/canasta-86-1986.json

Wire it up

what an authoring tool needs first
Bind this ROM
canasta

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
2–97 (24)
Solenoids
2–4 (3)

Coverage

Partial

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

Completion6%

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 · 15
IdentityDriver 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.

24 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
49–56
57–64
65–72
73–80
81–88
89–96
97–104
Hover or tap an address to identify it.
24 shown
# Name Device ID Evidence
2
Sw2a
switch.sw2a candidate
61
Sw61a
switch.sw61a candidate
62
Sw62
switch.sw62 candidate
63
Sw63
switch.sw63 candidate
66
Sw66
switch.sw66 candidate
67
Sw67
switch.sw67 candidate
71
Sw71
switch.sw71 candidate
72
Sw72
switch.sw72 candidate
73
Spinner1
switch.spinner1 candidate
76
Bumper1
switch.bumper1 candidate
77
Sw77
switch.sw77 candidate
80
Sw80
switch.sw80 candidate
81
Sw81
switch.sw81 candidate
82
Sw82
switch.sw82 candidate
83
Sw83
switch.sw83 candidate
86
Bumper2
switch.bumper2 candidate
87
Sw87
switch.sw87 candidate
90
Sw90a
switch.sw90a candidate
91
Drain
switch.drain candidate
92
Sw92a
switch.sw92a candidate
93
Sw93
switch.sw93 candidate
94
Sw94
switch.sw94 candidate
96
Bumper3
switch.bumper3 candidate
97
Sw97
switch.sw97 candidate

Controlled devices

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

Coils, magnets & motors

3
3 shown
# Name Device ID Evidence
2
Sol Left Target Reset
coil.sol-left-target-reset candidate
3
Sol Right Target Reset
coil.sol-right-target-reset candidate
4
Sol Release
coil.sol-release 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.canasta 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 canasta, description "Canasta '86'", manufacturer "Inder (Spain)", catalog year "1986".
  • No OPDB record is mapped for this driver in machines/opdb_id.csv, so the name above comes from the PinMAME catalog alone and is unverified.
  • The definition's driver list is exactly the clone tree PinMAME declares under canasta; whether every listed driver really runs on this physical machine is unverified.

Drivers this record holds

  • canasta (1986, Inder (Spain)).
  • canastfp (1986, Inder (Spain), clone of canasta).

VPX script candidates (candidate)

  • 2 retained community table script(s) declare this machine's driver; their extracted switch/lamp/solenoid/GI candidates are carried as 27 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
canastfpCanasta '86' (Free Play) 1986canasta—
canastaCanasta '86' 1986——

Parent set: canasta — 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

    8371478a7640
    by
    PinMAME contributors
    rev
    8371478a7640

  • VPX script

    vpx-script.d1cafa9363876b7f

    vpxtable-scripts: Canasta 86 (Inder 1986) v600.vbs

    0c036bb61b4b
    by
    Authors credited in Canasta 86 (Inder 1986) v600.vbs and repository contributors
    rev
    0c036bb61b4b
    sha256
    d1cafa936387…

  • VPX script

    vpx-script.50174a2794a5ff5f

    vpxtable-scripts: Canasta 86 (Inder 1986)2.0.1.vbs

    0c036bb61b4b
    by
    Authors credited in Canasta 86 (Inder 1986)2.0.1.vbs and repository contributors
    rev
    0c036bb61b4b
    sha256
    50174a2794a5…

Something wrong or missing?

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