250 c.c.

Partial

Inder (Spain)1992inder-spain.250-c-c.1992

inder-spain/250-c-c-1992.mdinder-spain/250-c-c-1992.json

Wire it up

what an authoring tool needs first
Bind this ROM
ind250cc

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
Switches
52–97 (26)

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.

26 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.
26 shown
# Name Device ID Evidence
52
Sw32
switch.sw32 candidate
60
Sw40
switch.sw40 candidate
61
Sw41
switch.sw41 candidate
62
Sw42
switch.sw42 candidate
63
Sw43
switch.sw43 candidate
64
Sw44
switch.sw44 candidate
65
Sw45
switch.sw45 candidate
66
Sw46
switch.sw46 candidate
67
Sw47
switch.sw47 candidate
70
Sw50
switch.sw50 candidate
71
Sw51
switch.sw51 candidate
72
Sw52
switch.sw52 candidate
73
Sw53a
switch.sw53a candidate
76
Sw56
switch.sw56 candidate
77
Sw57
switch.sw57 candidate
80
Sw60
switch.sw60 candidate
81
Sw61
switch.sw61 candidate
82
Sw62
switch.sw62 candidate
83
Sw63
switch.sw63 candidate
86
Bumper2
switch.bumper2 candidate
87
Sw67
switch.sw67 candidate
90
Sw70a
switch.sw70a candidate
92
Rubber Band2
switch.rubber-band2 candidate
93
Sw73a
switch.sw73a candidate
96
Bumper1
switch.bumper1 candidate
97
Sw77
switch.sw77 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.ind250cc 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 ind250cc, description "250 c.c.", manufacturer "Inder (Spain)", catalog year "1992".
  • 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 ind250cc; whether every listed driver really runs on this physical machine is unverified.

Drivers this record holds

  • ind250cc (1992, Inder (Spain)).

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 26 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
ind250cc250 c.c. 1992——

Parent set: ind250cc — 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.d7f944eea9b707f6

    vpxtable-scripts: 250cc (Inder - 1992) v600.vbs

    0c036bb61b4b
    by
    Authors credited in 250cc (Inder - 1992) v600.vbs and repository contributors
    rev
    0c036bb61b4b
    sha256
    d7f944eea9b7…

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