Contact

Partial
Completion13%

Williams1978williams.contact.1978 Updated 2026-08-30

OPDB IPDB williams/contact-1978.mdwilliams/contact-1978.json

Wire it up

what an authoring tool needs first
Bind this ROM
cntct_l1

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
9–38 (20)
Solenoids
1–23 (21)

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.

20 addresses

Switch map

Column × row matrix — the address is column·row.

used unused
 
1
2
3
4
5
6
7
8
1
2
3
Hover or tap an address to identify it.

Outside the matrix9 — dedicated, diagnostic or flipper-column addresses. See the table below.

20 shown
# Name Device ID Evidence
9
Sw9
switch.sw9 candidate
11
Sw11
switch.sw11 candidate
12
Sw12
switch.sw12 candidate
13
Sw13
switch.sw13 candidate
14
Sw14
switch.sw14 candidate
15
Sw15
switch.sw15 candidate
16
Sw16
switch.sw16 candidate
17
Sw17
switch.sw17 candidate
18
Right Sling Shot
switch.right-sling-shot candidate
22
Left Sling Shot
switch.left-sling-shot candidate
23
Sw23
switch.sw23 candidate
25
Sw25
switch.sw25 candidate
31
Sw31
switch.sw31 candidate
32
Sw32
switch.sw32 candidate
33
Bumper2
switch.bumper2 candidate
34
Bumper1
switch.bumper1 candidate
35
Bumper3
switch.bumper3 candidate
36
Sw36
switch.sw36 candidate
37
Sw5a
switch.sw5a candidate
38
Sw38
switch.sw38 candidate

Controlled devices

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

Coils, magnets & motors

21
21 shown
# Name Device ID Evidence
1
Ball Release
coil.ball-release candidate
2
Top Eject
coil.top-eject candidate
3
Left Reset
coil.left-reset candidate
4
Right Reset
coil.right-reset candidate
5
Left Eject
coil.left-eject candidate
6
Left Thrower
coil.left-thrower candidate
7
Right Thrower
coil.right-thrower candidate
8
Up Post
coil.up-post candidate
9
Sound1
coil.sound1 candidate
10
Sound2
coil.sound2 candidate
11
Sound3
coil.sound3 candidate
12
Sound4
coil.sound4 candidate
13
Sound5
coil.sound5 candidate
14
Knocker
coil.knocker candidate
15
Down Post
coil.down-post candidate
16
CLo
coil.clo candidate
17
Bumper2
coil.bumper2 candidate
18
Bumper1
coil.bumper1 candidate
19
Bumper3
coil.bumper3 candidate
22
Target
coil.target candidate
23
Enable
coil.enable 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.cntct_l1 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 cntct_l1, description "Contact (L-1)", manufacturer "Williams", catalog year "1978".
  • OPDB record G5v02-MDnyO (IPDB 558) names this machine "Contact" (Williams, manufacture date 1978-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 cntct_l1; whether every listed driver really runs on this physical machine is unverified.

Drivers this record holds

  • cntct_l1 (1978, Williams).

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 41 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
cntct_l1Contact (L-1) 1978——

Parent set: cntct_l1 — clones share this definition unless a hardware difference is noted.

Pinball memory maps

External source LGPL-3.0-only1 map

RAM layouts published by an independent project and mirrored here at a pinned commit. They are not part of this machine’s definition: nothing below was used as evidence for the definition, and none of it counts towards coverage. Check claims against the upstream project.

Upstream
tomlogic/pinball-memory-maps
Commit
d8693b9

This program makes use of content from the Pinball Memory Maps project.

cntct_l1.map.json

williams-system4v2format 0.8

maps/williams/system3/cntct_l1.map.json

Applies to ROMs
cntct_l1
Sections
adjustmentsauditsgame_statehigh_scores
Map JSONMap sourcePlatform JSONPlatform source

williams-system4 defines the RAM layout this map’s offsets are read against — the map is not interpretable without it.

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.4c4aa570aa9e2d46

    vpx-standalone-scripts: Contact (Williams 1978)_Bigus(MOD)1.0/Contact (Williams 1978)_Bigus(MOD)1.0.vbs

    15d112648a1b
    by
    Authors credited in Contact (Williams 1978)_Bigus(MOD)1.0/Contact (Williams 1978)_Bigus(MOD)1.0.vbs and repository contributors
    rev
    15d112648a1b
    sha256
    4c4aa570aa9e…

Something wrong or missing?

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

  • ROM compatibility

    Verify which PinMAME drivers and firmware variants belong to this physical machine.

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

  • Physical device locations

    Establish validated playfield locations for every physical sensor, actuator and light emitter, including bulb counts and justified projections.

Missing locations · 41