pinmame.sam
PinMAME reports logical active state on this platform. A consumer must not invert again. Whether a real switch is normally closed stays recorded per device as a physical fact, so a recreation can build the right hardware without changing what the emulator reports.
pinmame.input.switch
SAM uses sequential public switch numbering. Matrix switches are 1-64; dedicated D1-D8 are 65-72; D17-D24 are -7 through 0; flipper D9-D16 are exposed in PinMAME's flipper column as 81-88 with right/left and EOS ordering.
pinmame.input.dip
physical.output.ticket
No stable transport — these are physical identities the public API does not carry.
Physical service-diagnostic identities for optional ticket hardware. They are deliberately not LibPinMAME solenoid addresses: SAM public solenoid 33 is PinMAME's synthetic game-on state, and the stable API does not expose these cabinet functions.
pinmame.output.solenoid
SAM main-driver and game-specific auxiliary outputs share PinMAME's public solenoid address space. Addresses 1-32 are the base driver outputs; address 33 is PinMAME's synthetic game-on/fast-flip state and is never a physical transistor. Most six-transistor games expose addresses through 56; games such as Mustang configure sixteen custom outputs and expose the full 51-66 range, including deliberately unused public holes.
pinmame.output.lamp
The 1-80 range is the conventional matrix. SAM node-board games expose additional LED channels through backward-compatible ChangedLamps addresses. Star Trek configures four node boards and reaches public address 339; the deliberate compatibility gaps at 145, 210, and 275 are not device addresses.
pinmame.output.gi
src/wpc/sam.c; src/wpc/core.c; src/libpinmame/libpinmame.cpp
src/wpc/sam.c; src/wpc/core.c; src/libpinmame/libpinmame.cpp
src/libpinmame/libpinmame.cpp SetupMsgApi group definitions
src/libpinmame/libpinmame.cpp SetupMsgApi group definitions
Address ranges, transports and normalisation rules live in one profile file. If PinMAME exposes a group this profile does not describe — or describes wrongly — the fix belongs there.
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.