Viper

Partial

Stern1981STERN-MPU200stern.viper.1981

Wire it up

what an authoring tool needs first
Bind this ROM
viper

2 ROM sets resolve to this machine. Clones share the definition unless a hardware difference is listed.

Controller platform
pinmame.stern-mpu200

PinMAME already reports logical active state. Do not invert again in the table — normally-closed is a physical fact recorded per switch, not a runtime transform.

Displays

No display inventory recorded yet.

Address space
Switches
5–40 (22)
Solenoids
5–20 (4)
Lamps
10–62 (44)

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
candidate
Recreation Knowledge
unknown
Still missing · 13
Driver MappingInput 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.

22 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.
22 shown
# Name Device ID Evidence
5
Sw5
switch.sw5 candidate
9
Sw9
switch.sw9 candidate
11
Sw11
switch.sw11 candidate
12
Sw12
switch.sw12 candidate
13
Bumper2
switch.bumper2 candidate
14
Bumper1
switch.bumper1 candidate
15
Right Sling Shot
switch.right-sling-shot candidate
16
Left Sling Shot
switch.left-sling-shot candidate
17
Sw17
switch.sw17 candidate
18
Sw18
switch.sw18 candidate
19
Sw19
switch.sw19 candidate
20
Sw20
switch.sw20 candidate
21
Sw21
switch.sw21 candidate
22
Sw22
switch.sw22 candidate
23
Sw23
switch.sw23 candidate
31
Awt1
switch.awt1 candidate
32
Awt2
switch.awt2 candidate
36
Sw36
switch.sw36 candidate
37
Sw37
switch.sw37 candidate
38
Awt4
switch.awt4 candidate
39
Awt3
switch.awt3 candidate
40
Sol Fire Missile
switch.sol-fire-missile candidate

Controlled devices

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

Coils, magnets & motors

4
4 shown
# Name Device ID Evidence
5
Sol Fire Missile
coil.sol-fire-missile candidate
17
Sol Ball Walker
coil.sol-ball-walker candidate
18
Sol Rotor Magnet
coil.sol-rotor-magnet candidate
20
Sol Rotor Relay
coil.sol-rotor-relay candidate

Lamps

44

Lamp 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
Hover or tap an address to identify it.
44 shown
# Name Device ID Evidence
10
L10
lamp.l10 candidate
11
L11
lamp.l11 candidate
12
L12
lamp.l12 candidate
14
L14
lamp.l14 candidate
15
L15
lamp.l15 candidate
17
L17
lamp.l17 candidate
18
L18
lamp.l18 candidate
19
L19
lamp.l19 candidate
20
L20
lamp.l20 candidate
21
L21
lamp.l21 candidate
22
L22
lamp.l22 candidate
23
L23
lamp.l23 candidate
24
L24
lamp.l24 candidate
25
L25
lamp.l25 candidate
26
L26
lamp.l26 candidate
27
L27
lamp.l27 candidate
28
L28
lamp.l28 candidate
29
L29
lamp.l29 candidate
30
L30
lamp.l30 candidate
31
L31
lamp.l31 candidate
33
L33
lamp.l33 candidate
34
L34
lamp.l34 candidate
35
L35
lamp.l35 candidate
36
L36
lamp.l36 candidate
37
L37
lamp.l37 candidate
38
L38
lamp.l38 candidate
39
L39
lamp.l39 candidate
40
L40
lamp.l40 candidate
41
L41
lamp.l41 candidate
43
L43
lamp.l43 candidate
44
L44
lamp.l44 candidate
46
L46
lamp.l46 candidate
47
L47
lamp.l47 candidate
50
L50
lamp.l50 candidate
51
L51
lamp.l51 candidate
52
L52
lamp.l52 candidate
53
L53
lamp.l53 candidate
54
L54
lamp.l54 candidate
55
L55
lamp.l55 candidate
56
L56
lamp.l56 candidate
57
L57
lamp.l57 candidate
59
L59
lamp.l59 candidate
60
L60
lamp.l60 candidate
62
L62
lamp.l62 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.viper 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 viper, description "Viper", manufacturer "Stern", catalog year "1981".
  • OPDB record G5vXB-MLEve (IPDB 2739) names this machine "Viper" (Stern Electronics, manufacture date 1981-01-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 viper; whether every listed driver really runs on this physical machine is unverified.

Drivers this record holds

  • viper (1981, Stern).
  • viperfp (1981, Stern, clone of viper).

PinMAME source contract (candidate)

  • The pinned PinMAME source declares viper at src/wpc/stgames.c:1210 with machine module by35_mST200; the definition declares controller platform pinmame.stern-mpu200 from it.

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 70 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

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
viperfpViper (Free Play) 1981viper
viperViper 1981

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

Commit
d8693b9

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

m200-7digit-B.map.json

stern-m200v3format 0.8

maps/stern/m200/m200-7digit-B.map.json

Applies to ROMs
viper
Also covers
freefalldragfistironmaidlightninsplitsec
Sections
adjustmentsauditsgame_statehigh_scores

stern-m200 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

    by
    PinMAME contributors
    rev
    8371478a7640
  • PinMAME source

    BSD-3-Clause

    pinmame.core.8371478a7640

    src/wpc/stgames.c:1210 (machine module by35_mST200)

    by
    PinMAME contributors
    rev
    8371478a7640
  • VPX script

    vpx-script.54a85cc8cb88cfac

    vpxtable-scripts: Viper (Stern 1981) v600.vbs

    by
    Authors credited in Viper (Stern 1981) v600.vbs and repository contributors
    rev
    0c036bb61b4b
    sha256
    54a85cc8cb88…
  • VPX script

    vpx-script.06bdc18180b0d68c

    vpxtable-scripts: Viper 1.1.1.vbs

    by
    Authors credited in Viper 1.1.1.vbs and repository contributors
    rev
    0c036bb61b4b
    sha256
    06bdc18180b0…

Something wrong or missing?

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

Same platform