301/Bullseye

Partial

Grand Products Inc.1986grand-products-inc.301-bullseye.1986

Wire it up

what an authoring tool needs first
Bind this ROM
bullseye

4 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
4–40 (25)

Coverage

Partial

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

Completion13%

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 · 14
Driver 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.

25 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
Hover or tap an address to identify it.
25 shown
# Name Device ID Evidence
4
Sw4
switch.sw4 candidate
5
Sw5
switch.sw5 candidate
8
Sw8
switch.sw8 candidate
15
Sw15
switch.sw15 candidate
17
Sw17
switch.sw17 candidate
18
Sw18
switch.sw18 candidate
19
W19a
switch.w19a candidate
20
T20
switch.t20 candidate
21
T21
switch.t21 candidate
22
T22
switch.t22 candidate
23
T23
switch.t23 candidate
24
T24
switch.t24 candidate
25
Sw25
switch.sw25 candidate
26
Sw26
switch.sw26 candidate
28
T28
switch.t28 candidate
29
T29
switch.t29 candidate
30
T30
switch.t30 candidate
31
T31
switch.t31 candidate
32
T32
switch.t32 candidate
35
Sw35
switch.sw35 candidate
36
Right Sling Shot
switch.right-sling-shot candidate
37
Left Sling Shot
switch.left-sling-shot candidate
38
Bumper1
switch.bumper1 candidate
39
Bumper2
switch.bumper2 candidate
40
Spinner001
switch.spinner001 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.bullseye 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 bullseye, description "301/Bullseye", manufacturer "Grand Products Inc.", catalog year "1986".
  • OPDB record G4kE2-MBRzN (IPDB 403) names this machine "301/Bullseye" (Grand Products, manufacture date 1986-05-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 bullseye; whether every listed driver really runs on this physical machine is unverified.

Drivers this record holds

  • bullsen2 (2021, Grand Products Inc. / Quench, clone of bullseye).
  • bullsey2 (2021, Grand Products Inc. / Quench, clone of bullseye).
  • bullseye (1986, Grand Products Inc.).
  • bullseyn (1986, Grand Products Inc., clone of bullseye).

PinMAME source contract (candidate)

  • The pinned PinMAME source declares bullseye at src/wpc/by35games.c:1952 with machine module by35_GP; no platform is declared (no reviewed profile covers that module yet).

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 25 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
bullsey2301/Bullseye (MOD rev. 12) 2021bullseye
bullsen2301/Bullseye (Normal pinball scoring MOD rev. 13) 2021bullseye
bullseyn301/Bullseye (Normal pinball scoring) 1986bullseye
bullseye301/Bullseye 1986

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

    by
    PinMAME contributors
    rev
    8371478a7640
  • VPX script

    vpx-script.7463016b3174e1f3

    vpxtable-scripts: 301 Bullseye (Grand Products 1986) v600.vbs

    by
    Authors credited in 301 Bullseye (Grand Products 1986) v600.vbs and repository contributors
    rev
    0c036bb61b4b
    sha256
    7463016b3174…

Something wrong or missing?

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