Pinball Makers (Staging) - User contributions [en]

File:Font CC 20px az.dmd.zip

2016-02-10T13:02:52Z

Steveshoyer:

File:Font CC 17px score.dmd.zip

2016-02-10T13:02:33Z

Steveshoyer:

File:Font CC 15px az.dmd.zip

2016-02-10T13:02:14Z

Steveshoyer:

File:Font CC 13px wide score.dmd.zip

2016-02-10T13:01:51Z

Steveshoyer:

File:Font CC 13px score.dmd.zip

2016-02-10T13:01:30Z

Steveshoyer:

File:Font CC 13px thin score.dmd.zip

2016-02-10T13:01:00Z

Steveshoyer:

File:Font CC 13px extra thin score.dmd.zip

2016-02-10T13:00:33Z

Steveshoyer:

File:Font CC 12px az.dmd.zip

2016-02-10T13:00:09Z

Steveshoyer:

File:Font CC 9px az.dmd.zip

2016-02-10T12:59:38Z

Steveshoyer:

File:Font CC 7px bold az.dmd.zip

2016-02-10T12:59:17Z

Steveshoyer:

File:Font CC 7px az.dmd.zip

2016-02-10T12:58:52Z

Steveshoyer:

File:Font Custom 6px inverted AZ.dmd.zip

2016-02-10T12:58:26Z

Steveshoyer:

Fonts

2016-02-10T12:57:55Z

Steveshoyer: /* Fonts */

===Fonts===

This is a collection of pixel fonts in .DMD format for use with PyProcgame.

'''Naming conventions:'''
* Font_(identifier)_(pixel height)_(additional details)_(scope)
** The identifier is just a name to allow grouping of fonts that go together
** Since the widths of the characters vary, I identify them all by height
** Additional details like "bold" or "thin" or "inverse"
** The Scope can be: score (digits only), AZ (all digits and upper case alphabet), az (all digits and all characters)

----

<CENTER>
{| width=85% class="wikitable" style="text-align:center;"
| '''Preview Image'''
| '''Description'''
| '''File (Right-Click/Save-As)'''
|-
| [[File:Font_CC_5px_AZ.png]] || Recreated 5 pixel font from Cactus Canyon || [[Media:Font_CC_5px_AZ.dmd.zip]]
|-
| [[File:Font_CC_5px_bold_AZ.png]] || Recreated 5 pixel font from Cactus Canyon Bold Version. || [[Media:Font_CC_5px_bold_AZ.dmd.zip]]
|-
| [[File:Font_CC_6px_az.png]] || Recreated 6 pixel font from Cactus Canyon || [[Media:Font_CC_6px_az.dmd.zip]]
|-
| [[File:Font_Custom_6px_inverted_AZ.png]] || Custom 6px Inverted Font. Font Height is actually 8 pixels with background. < and > can be used to cap the string. || [[Media:Font_Custom_6px_inverted_AZ.dmd.zip]]
|-
| [[File:Font_CC_7px_az.png]] || Recreated 7 pixel font from Cactus Canyon || [[Media:Font_CC_7px_az.dmd.zip]]
|-
| [[File:Font_CC_7px_bold_az.png]] || Recreated 7 pixel font from Cactus Canyon Bold Version. || [[Media:Font_CC_7px_bold_az.dmd.zip]]
|-
| [[File:Font_CC_9px_az.png]] || Recreated 9 pixel font from Cactus Canyon || [[Media:Font_CC_9px_az.dmd.zip]]
|-
| [[File:Font_CC_12px_az.png]] || Recreated 12 pixel font from Cactus Canyon || [[Media:Font_CC_12px_az.dmd.zip]]
|-
| [[File:Font_CC_13px_extra_thin_score.png]] || Recreated 13 pixel score font from Cactus Canyon Extra thin Version. || [[Media:Font_CC_13px_extra_thin_score.dmd.zip]]
|-
| [[File:Font_CC_13px_thin_score.png]] || Recreated 13 pixel score font from Cactus Canyon Thin Version. || [[Media:Font_CC_13px_thin_score.dmd.zip]]
|-
| [[File:Font_CC_13px_score.png]] || Recreated 13 pixel score font from Cactus Canyon || [[Media:Font_CC_13px_score.dmd.zip]]
|-
| [[File:Font_CC_13px_wide_score.png]] || Recreated 13 pixel score font from Cactus Canyon Wide Version. || [[Media:Font_CC_13px_wide_score.dmd.zip]]
|-
| [[File:Font_CC_15px_az.png]] || Recreated 15 pixel score font from Cactus Canyon || [[Media:Font_CC_15px_az.dmd.zip]]
|-
| [[File:Font_CC_17px_score.png]] || Recreated 17 pixel score font from Cactus Canyon || [[Media:Font_CC_17px_score.dmd.zip]]
|-
| [[File:Font_CC_20px_az.png]] || Recreated 20 pixel font from Cactus Canyon || [[Media:Font_CC_20px_az.dmd.zip]]
|}
</CENTER>

File:Font CC 6px az.dmd.zip

2016-02-10T12:56:11Z

Steveshoyer:

File:Font CC 5px bold AZ.dmd.zip

2016-02-10T12:55:46Z

Steveshoyer:

File:Font CC 5px AZ.dmd.zip

2016-02-10T12:54:44Z

Steveshoyer:

Vendor List

2016-02-08T06:20:12Z

Steveshoyer: /* Controllers */

A list of businesses that cater to the custom pinball community or provide goods and services relevant to garage builders.

=== General ===

* [http://www.pbresource.com/ Pinball Resource]
* [http://www.marcospec.com/ Marco Specialties]
* [http://www.pinbits.com/index.php?main_page=index&cPath=10 PinBits]
* [http://www.mad-amusements Mad Amusements]
* [http://www.pinballcenter.eu Pinball Center (Germany)]
* [http://www.pinballlife.com Pinball Life]
* [http://www.bayareaamusements.com Bay Area Amusements]
* [http://www.planetarypinball.com Planetary Pinball]
* [http://www.lakesidepinballparts.com Lakeside Parts]
* [http://virtuapin.net/index.php?main_page=product_info&cPath=3&products_id=9 VirtuaPin - Cabinet parts]
* [http://www.xtremepinball.com/index.php?main_page=index&cPath=65 Xtreme Pinball DIY Cabinets]
* [https://greatplainselectronics.com/ Great Plains Electronics - Connectors, Molex, etc...]
* [http://www.greatpinball.com/ Great Pinball]
* [http://www.foremostplastic.com/Page9.html Foremost Plastics]

=== Displays ===

* [http://xpinpinball.com/ X-PIN]
* [http://www.pinscore.com/products/pinball-displays Pinscore]
* [http://www.pinled.de/shop/index.php PinLED]
* [http://www.adafruit.com/categories/103 Adafruit]
* [http://shop.evilmadscientist.com/productsmenu/tinykitlist/75-peggy2 Evil Mad Scientist]
* [http://www.embeddedadventures.com/led_matrix_displays_category.html Embedded Adventures]

=== Lighting ===

* [http://shop.cointaker.com Cointaker]
* [http://www.titanpinball.com Titan Pinball]
* [http://pinballbulbs.com Pinball Bulbs]
* [http://www.cometpinball.com Comet Pinball]
* [http://www.pinballlife.com/index.php?p=catalog&parent=192&pg=1 Pinball Life]
* [http://www.niftyled.com Nifty LED]

=== Controllers ===

* [http://www.pinballcontrollers.com/index.php/products/p-roc Multimorphic / P-ROC]
** [[P-ROC_Main_Page | Wiki pages for P-ROC game development]]
* [http://fastpinball.com/ FAST Pinball]

=== Sound ===

* [https://www.sparkfun.com/products/11029 MP3 Trigger]
* [http://www.pinsound.org/pinsound/pinsound-board Pinsound]
* [http://makezine.com/2012/10/22/a-halloween-sound-trigger-with-raspberry-pi-and-arduino Arduino]
* [https://www.sparkfun.com/products/12897 WAV Trigger]

=== Power Supplies ===

* [http://www.antekinc.com/ps-4n70-400w-70v-power-supply/ AnTek]
* [http://www.circuitspecialists.com/stepper-motor-power-supplies/page-2 Circuit Specialties]

=== Wireforms ===

* [http://www.rollingballsculpture.com/ Rolling Ball Sculpture]

=== Playfields ===

* [http://www.spookypinball.com Spooky Pinball - CNC + Direct art printing]
* [http://www.xtremepinball.com/index.php?main_page=product_info&products_id=184 Xtreme Pinball]
*[http://www.greatpinball.com/ Great Pinball - CNC + UV Inkjet printing]

=== Plastics ===

* [http://www.spookypinball.com Spooky Pinball]
*[http://www.greatpinball.com/ Great Pinball]

=== Translites ===

* [http://www.spookypinball.com Spooky Pinball]
*[http://www.greatpinball.com/ Great Pinball]

=== Artwork Screenprinting / Vinyl Printing ===

* [http://thisoldgame.com This Old Game]
* [http://www.bannerbuzz.com BannerBuzz]
* [http://pinballbuilders.com Pinball Builders]

=== Sheetmetal ===

* [http://www.mcmaster.com/#standard-stainless-steel-sheets/=ve62im McMaster-Carr]
* [http://www.grainger.com/category/stainless-steel-blanks-flats-bars-plates-and-sheet-stock/stainless-steel/raw-materials/ecatalog/N-c22?bc=y#nav=%2Fcategory%2Fstainless-steel-blanks-flats-bars-plates-and-sheet-stock%2Fstainless-steel%2Fraw-materials%2Fecatalog%2FN-c22Z1z0o8uzZ1z0nmq0 Grainger]
* [http://www.onlinemetals.com Online Metals]

=== Plating ===

* [http://www.caswellplating.com/electroplating-anodizing.html Caswell]
* [http://www.eastwood.com/paints/electroplating.html Eastwood]

=== Powder Coating ===

* [http://www.caswellplating.com/powder-coating.html Caswell]
* [http://www.eastwood.com/paints/hotcoat-powder-coating.html Eastwood]

=== Laser Cutting Tools ===

* [https://www.epiloglaser.com/ Epilog]
* [http://www.ulsinc.com/ Universal]
* [http://fslaser.com/products/lasers/hobby-lasers/newhobby Full Spectrum Laser]

=== Laser Cutting Services ===

* [http://www.laseriffic.com/ Laseriffic Inc.]
* [https://www.ponoko.com Ponoko]
*[http://www.greatpinball.com/ Great Pinball]

=== Waterjet Cutting Services ===

* [http://www.chicagowaterjet.com Chicago Waterjet]

=== CNC Machines ===

* [http://www.shopbottools.com/mProducts/prSstandard.htm ShopBOT]
* [http://mechmate.com/ MechMate]
* [http://www.generalcnc.ca/home GeneralCNC]
* [http://www.joescnc.com Joe's CNC]

=== 3D Printers ===

* [http://printrbot.com/shop/simple-metal-kit-with-heated-bed/ Printr]
* [http://www.makerbot.com Makerbot]
* [http://cubify.com/en/Cube Cubify]
* [https://reprappro.com RepRap]
* [http://formlabs.com FormLabs]

=== 3D Printing Services ===

* [http://www.thingiverse.com/ Thingverse]
* [http://www.spookypinball.com Spooky Pinball]
* [http://www.pinballlife.com Pinball Life]
* [http://www.shapeways.com Shapeways]
* [https://www.ponoko.com Ponoko]
* [https://www.3dhubs.com 3dHubs]
* [http://www.makexyz.com MakeXYZ]

File:Stereo to Mono 1.jpg

2016-02-08T06:16:52Z

Steveshoyer: Steveshoyer uploaded a new version of File:Stereo to Mono 1.jpg

File:Stereo to Mono 1.jpg

2016-02-08T06:15:41Z

Steveshoyer:

File:Audio Board Connection.jpg

2016-02-08T06:15:07Z

Steveshoyer:

File:Stereo to Mono 2.jpg

2016-02-08T06:14:36Z

Steveshoyer:

File:Audio mod.jpg

2016-02-08T06:13:39Z

Steveshoyer:

File:Wpc-95.jpg

2016-02-08T06:13:09Z

Steveshoyer:

Modifying a WPC-95 board for Audio Input old

2016-02-08T06:10:54Z

Steveshoyer: Created page with "NOTE: This modification, as described on this page, is not universal. Once modified in this manner, the board does not work for regular WPC95 system use until un-modified. I..."

NOTE: This modification, as described on this page, is not universal. Once modified in this manner, the board does not work for regular WPC95 system use until un-modified. It would be possible to do the modification with some built in switches to allow changing back and forth, but these directions do not provide details on that.

Refer to the image below for the location of the items mentioned.

==Install a pin header at J509==
* Find connector J509 (the component is probably not populated on your board).
* This is where a line-out connector can go. We're going to reuse this as our line-in.
* Install a 2-pin 0.100" molex (or similar type) header/connector.
* With the board facing in such a way that the J509 is right side up, pin 1 is on the right.

==Remove Resistor R84==
* Find resistor R84.
* You'll remove this completely. In this example, it is then used as a jumper point to connect to C18.

==Connect J509 to the amp==
* Find capacitor C18
* This may be a bit tricky to do with the present cap - but you have to pull the positive leg out of the board, leave the negative leg in.
* Alternately, remove C18 and get a new 4.7uF cap so you have longer legs for easier connection.
* With the negative side connected to the board, you'll need to connect your audio in to the positive side.
* In this example, a jumper wire goes '''FROM''' the point where pin 1 from J509 connects to the (now removed) R84 '''TO''' the positive leg of C18 (white wire)

==Create a cable to hook things up==
* You can now create a cable to go between your computer and your new line in.
* If you're using a stereo source, you'll want to wire them together via 1k resistors before connecting to pin 1 of your line in connector (pin 2 is ground). [[media:audio-cable.jpg | crude diagaram]]

==Diagram: The board before modification:==
[[File:Wpc-95.jpg]]

==Diagram: The board after modification:==
[[File:audio_mod.jpg]]

Modifying a WPC-95 board for Audio Input

2016-02-08T06:10:21Z

Steveshoyer: Created page with "The P-ROC board does not handle audio in any way. If you'd like to use the built in WPC-95 hardware to playback the sound, you'll have to do some small modifications to the s..."

The P-ROC board does not handle audio in any way. If you'd like to use the built in WPC-95 hardware to playback the sound, you'll have to do some small modifications to the sound board, and connect it to to the output of the computer that is running the code.

'''Warning - Pinballcontrollers.com is not responsible for any damage that occurs as a result of this or any hardware modification you make.'''

Note: This modification was updated to this version on August 10, 2013. The previous description was a little more complicated and can be found here: [[Modifying_a_WPC-95_board_for_Audio_Input_old | Old mod description]]

Convert the stereo output from your computer to mono. Example:

* Step 1 - Add a stereo connector to the WPC-95 A/V board.

I used a female 1/8" inline phone jack from Radio Shack (part#274-0274), soldered a 1k resistor to each lug, connected the other ends of the resistors together, and soldered the "signal" red wire to them. The "ground", purple wire, was soldered to the ground lug on the jack. See pics. Finally, A mini-alligator clip was soldered to each wire. The red/signal wire/alligator clip clips to the top of C9, and the purple/ground wire/alligator clip clips to the bottom of C35. See pic. If you accidentally reverse the connections or touch the top of R14 you won't damage anything. The mini-alligator clips seem to hold fine.

[[Image:Stereo_to_Mono_1.jpg]]
[[Image:Stereo_to_Mono_2.jpg]]

* Step 2 - Connect a stereo cable between your computer and the connector from step 1.

I used the following 10ft double shielded VGA cable with built in 3.5mm stereo cable from amazon (it has an extra long 3.5mm wire to attach to a laptop):
[http://www.amazon.com/gp/product/B0015AAYZA/ref=oh_details_o00_s00_i00?ie=UTF8&psc=1]. I used this because I am also using an LCD in my backbox instead of a DMD. Any 3.5mm male/male stereo cable should work (recommend shielded). One end of this cable plugs into the computer. The other end plugs into:

[[Image:Audio_Board_Connection.jpg]]

Sound is good without much hum. There seems to be plenty of adjustment range using the computer to set an initial volume and the coin door buttons to adjust around this level.

Pyprocgame vp

2016-02-08T06:09:17Z

Steveshoyer: Created page with "This page outlines how to set interface pyprocgame to Visual Pinball so you can run your custom software on virtual tables. === Install pyprocgame and dependencies === * Inst..."

This page outlines how to set interface pyprocgame to Visual Pinball so you can run your custom software on virtual tables.

=== Install pyprocgame and dependencies ===
* Install the P-ROC software libraries. Use the libpinproc installer on [http://www.pinballcontrollers.com/index.php?option=com_content&view=article&id=61&Itemid=63 this page] or [http://www.pinballcontrollers.com/wiki/Windows_build_instructions compile from source].

* Install Python 2.6
* Install the following python 2.6 modules:
** PyWin32
** PyGame
** PIL
** PyYAML
** pypinproc (the self-installing executable resides in <libpinproc>\ext\python\)
* Install [http://github.com/preble/pyprocgame/tree pyprocgame]

* Install Visual Pinball (Available on [http://www.vpforums.org vpforums.org] in the Getting Started menu).
** Download [http://www.pinballcontrollers.com/files/pyprocgame_vp_scripts_v1.zip these VP scripts] and put them in VP's 'Scripts' subdir. These are slightly modified from the original VP scripts so that VP will work with pyprocgame.
** Download VP's sound samples from [http://www.vpforums.org vpforums.org] (in the Getting Started menu) and put them in VP's 'samples' subdir.
** Find and download/unzip the VP tables you want from [http://www.vpforums.org vpforums.org] (in the Desktop Tables menu).

=== Set up pyprocgame/VP environment ===
* Add the following to your pyprocgame config.yaml file (~\.pyprocgame\config.yaml): ([http://www.pinballcontrollers.com/files/config.yaml Sample here])

<code>
pinproc_class: procgame.fakepinproc.FakePinPROC

log_destination: /P-ROC/pyprocgame/log.text # Change this to where you want the log to go.

vp_game_map_file: /P-ROC/pyprocgame/vp_game_map.yaml # Change this to where you create your map file
</code>

* Create a vp_game_map.yaml file and put it where you said it would be in your config.yaml file. ([http://www.pinballcontrollers.com/files/vp_game_map.yaml Sample here])

=== Run pyprocgame games in VP ===
* Register the pyprocgame/VP interface:
<code>
python.exe tools\register_vpcom.py
</code>
* Run VP, open the desired table, click play.

Note - You only need to register the pyprocgame/VP interface once. (unless you are using VP with both pyprocgame and pinmame. Then you need to re-register the interface after using pinmame.)

JD rules

2016-02-08T06:08:26Z

Steveshoyer: Created page with "== Introduction == The JD rules describe the operation of custom JD game software that runs on a PC connected to a Judge Dredd pinball machine through a [http://www.pinballcon..."

== Introduction ==
The JD rules describe the operation of custom JD game software that runs on a PC connected to a Judge Dredd pinball machine through a [http://www.pinballcontrollers.com P-ROC] board. The game software is free and open-source and can be found [http://github.com/preble/JD-pyprocgame/ here]. Running the software requires the installation of the libpinproc P-ROC interface library, the pypinproc python extension, and the pyprocgame pinball software framework. Refer to the [http://www.pinballcontrollers.com/index.php?option=com_content&view=article&id=61&Itemid=63 P-ROC software page] for more information about them.

JD was developed primarily by the following people:
*Gerry Stellenberg - Rules/Gameplay
*Adam Preble - Tools/Framework
*Rob Keller - Sound/Music
*Travis Highrise - Dots

Discussion forums for this and other P-ROC based projects can be found at [http://www.pinballcontrollers.com/forum http://www.pinballcontrollers.com/forum].

A list of music / sound effects / voice calls is [[JD sound here|here]].

The media package contained all of the sound and video can be downloaded from [http://www.pinballcontrollers.com/files/jd_media_02.tar.gz here].

== Chain Features ==

There are 9 chain features, corresponding to the 9 inserts in the center of the playfield. Each feature represents a mode. The left and right Fire buttons change the next mode, as do the slingshots. The upper right 'build chain feature' shot is active when not already in a mode or in multiball. Shooting that shot starts the next mode. A video intro provides directions before the ball is put back into play. The video can be cancelled with the flipper buttons.

Every time a mode is completed successfully, the player is a 10-second hurryup countdown begins, and the D drop target is lowered to expose the subway shot. Shooting into the subway before the timer expires presents the player with a Pick-A-Prize selection. Two awards are presented, and the player can select one using the flipper button corresponding to the desired choice. If the hurryup is collected during multiball, both prizes are awarded immediately.

Pick-A-Prize awards:
*100,000 points
*Advance Crimescenes

The modes are timed. Hitting the Mystery target when lit while in a mode extends the mode timer. Hitting the Mystery target when lit during the hurry-up countdown extends the hurry-up timer.

==== Pursuit ====
Left and Right ramps are lit with Pursuit flashers flashing.

==== Blackout ====
GI turns off. Left center ramp is lit with Blackout flasher flashing. If ramp is hit once, it re-lights for a double award (2x Blackout flasher also flashes). The double award is required for mode completion.

==== Sniper ====
Random shot lights. Shoot the shoot to locate the 'bad guy' sniper. Then shoot the upper right VUK to position the 'good guy' sniper. Then shoot the random shot again to kill the 'bad guy' sniper.

==== Battle Tank ====
3 shots:
* Left outer loop
* Center target bank
* Left center ramp

==== Bad Impersonator ====
Rotating Judge targets

==== Meltdown ====
Captured Balls - requires 3 switches to be hit (all at once or with multiple shots)

==== Safecracker ====
Shoot the subway 3 times

==== Manhunt Millions ====
Left ramp is lit. Shoot it 3 times

==== Stakeout ====
Right ramp is light. Shoot it 3 times

== Crimescenes ==

There are 16 levels of crimescenes. Each level corresponds to a 'block' of crimes. At each level, one or more of the crimescene inserts scattered around the playfield is lit as determined by user configurable difficulty settings. Shooting the 3 target bank in the center of the playfield 3 times during a single crimescene level also advances the level. Each shot to an active crimescene target awards 1000 points, and each time a level is a completed 10,000 points are awarded. An extra ball is lit after completing 3 levels. Completing all 16 levels is required before Ultimate Challenge can be lit. The crimescene levels restart at 1 after Ultimate Challenge is attempted.

Each completed crimescene level contributes 2000 points into the bonus. This bonus contribution is not reset between balls.

Difficulty settings determine how many and which crimescene targets are set at each level.

The 16 crimescene levels are tracked in groups of 4. The 4 crimescene inserts in the front-center of the playfield indicate which group is active. Within each group of 4, the specific level number is indicated by the color of the crimescene shot inserts:

{| border="1"
|align="center" | '''Group'''
|align="center" | '''Insert Color'''
|align="center" | '''Level'''
|-
|align="center" | Warning
|align="center" | White
|align="center" | 1
|-
|align="center" | Warning
|align="center" | Red
|align="center" | 2
|-
|align="center" | Warning
|align="center" | Yellow
|align="center" | 3
|-
|align="center" | Warning
|align="center" | Green
|align="center" | 4
|-
|align="center" | Misdemeanor
|align="center" | White
|align="center" | 5
|-
|align="center" | Misdemeanor
|align="center" | Red
|align="center" | 6
|-
|align="center" | Misdemeanor
|align="center" | Yellow
|align="center" | 7
|-
|align="center" | Misdemeanor
|align="center" | Green
|align="center" | 8
|-
|align="center" | Felony
|align="center" | White
|align="center" | 9
|-
|align="center" | Felony
|align="center" | Red
|align="center" | 10
|-
|align="center" | Felony
|align="center" | Yellow
|align="center" | 11
|-
|align="center" | Felony
|align="center" | Green
|align="center" | 12
|-
|align="center" | Class X Felony
|align="center" | White
|align="center" | 13
|-
|align="center" | Class X Felony
|align="center" | Red
|align="center" | 14
|-
|align="center" | Class X Felony
|align="center" | Yellow
|align="center" | 15
|-
|align="center" | Class X Felony
|align="center" | Green
|align="center" | 16
|}

=== Block War MB ===

After every 4th level of crimescenes is completed, a 2-ball Block War multiball begins. This progressive multiball mode starts with the White crimescene insert lamps lit. When all 5 crimescene shots are completed, a rotating jackpot shot is lit. If the jackpot shot is lit, the crimescene shots light again with two color lamps lit, White and Red. The 3rd time, 3 color lamps are lit, and all 4 color lamps are lit the 4th time and any subsequent time.

== Deadworld Multiball ==

Locks are lit by completing all of the JUDGE drop targets. Each time the targets are completed, another lock is lit. (after the first multiball, it becomes increasingly difficult to light lock.) When lock is lit, shots to the left ramp are diverted into the Deadworld and locked. 3 lock shots are required to start multiball, which starts with 3 balls. An additional ball can be added with a shot to the Mystery target, when it is lit.

How to light jackpot: TBD
Shoot the subway to collect jackpot

Note - Deadworld MB can be started while a Chain Feature mode is active. When that happens, both the Chain Feature mode and MB continue simultaneously.

== Missile Launch Award ==

Missile launch is fed via the center ramp. When missile launch is lit and the ball is in the left shooter lane, the DMD scrolls through a set of award. When the left shooter button is pressed, the active award is awarded. Missile launch is lit when the ball enters the left shooter lane if Deadworld Multiball is not active. When lit, the Air Raid lamp flashes in front of the center ramp.

Awards include:
* Light extra ball
* Advance crime scene level
* 30,000 Points
* Increase bonus multiplier
* Hold bonus multiplier
* Video mode

After light extra ball is collected, it is replaced with 10,000 points. After hold bonus multiplier is collected, it is replaced with 50,000 points. The other awards can be collected more than once.

If Missile Launch is activated during a mode, the mode timer is paused until the award is collected.

== Video Mode ==

Video Mode is activated from a Missile Launch Award, which can only happen when a single ball is in play. When video mode is awarded, the ball stays in the left shooter lane while the player plays through the mode on the DMD using the flipper/fire buttons.

The mode is a shooting gallery. There are 12 targets, including 6 friends and 6 enemies:

Friends:
*Anderson
*Hershey
*Tweak
*Walter
*Johnny Alpha
*Vienna

Enemies:
*Pa Angel
*Mean Machine Angel
*Judge Cal
*Satanus
*Rico
*Child Mutant

At speeds that increase as the mode goes on, targets are randomly displayed on the screen. The objective is to shoot enemies and not shoot friends. The flipper buttons are used to move a scope target to the desired location, and either fire button will shoot the targeted location. If a friend is shot, the mode immediately ends in failure. Otherwise the mode ends after a certain amount of time (30 seconds)? If all enemies are shot, the player is awarded an extra ball.

After Video Mode ends, the ball is automatically launched back into play.

== Miscellaneous Features ==
Consecutive shots to the right loop from the upper left flipper are counted and awarded progressively higher points per shot. The player to achieve the most consecutive shots is the 'Outer Loop Champion'. X consecutive shots lights extra ball. X is a user configurable setting.

Consecutive shots to the inner left loop from the upper right flipper are counted and awarded progressively higher points per shot. The player to achieve the most consecutive shots is the 'Inner Loop Champion'. Y consecutive shots lights extra ball. Y is a user configurable setting.

Full shots to the captive balls, resulting in the 3rd switch being hit, light the Mystery shot and increase the Bonus multiplier by 1X.

Skill shot - Shoot the right loop from the upper flipper. Continue loop to receive increasing point awards.

== Ultimate Challenge ==

Ultimate Challenge is a multi-stage wizard mode representing final battles with each of the Dark Judges. Ultimate Challenge is lit when the following requirements are met:

* All 9 Chain Feature modes attempted (completion not required)
* All 16 Crimescene levels completed
* At least one Deadworld Multiball jackpot collected

Once Ultimate Challenge is lit, a shot to the upper right 'build chain feature' shot initiates it. The player is presented with an Ultimate Challenge introduction with instructions before Level 1 begins. Each time a level is successfully completed, the machine goes dead, allowing all of the balls to drain. Then the player is presented with an intro and instructions for the next level before any balls are re-launched and put back into play. If all balls drain before the player completes a level, the player's ball ends and Ultimate Challenge is aborted. Re-lighting Ultimate Challenge requires the player to complete the 3 major requirements again. Subsequent Ultimate Challenge attempts begin at the first level not yet completed by the player. In other words, previously completed levels do not need to be completed again.

=== Level 1: Fire ===

All 5 crimescene shots are lit, representing fires that Judge Dredd needs to extinguish. This level begins with a 4-ball multiball and no ball save. It is completed successfully when the last fire is extinguished.

=== Level 2: Mortis ===

This level begins with a 2-ball multiball and has 5 shots that each need to be hit twice. The shots are: Mystery, Left Loop, Upper Right VUK, Right Ramp, and the 3rd Captive Ball. Each shot's insert lamps blink slowly to indicate 2 shots are required, blink quickly to indicate 1 shot is required, and are turned off when the shot is complete.

=== Level 3: Fear ===

Fear uses timed shots to force the player to be accurate. The begins with only 1 ball in play, and each of the following shots must be hit, in order, before a shot timer (20 seconds) expires: Left Ramp, Right Ramp, Left Ramp, Right Ramp, D drop tarter, Subway. If the timer expires before a shot is hit, the game goes dead forcing the balls to drain and ending the player's turn.

=== Level 4: Death ===

Judge Dredd's final challenge is a single ball mode requiring all 5 of the crimescene shots to be cleared. The player has 3 minutes to clear all 5 shots. Every few seconds, a previously cleared shot is relit. If the 3 minute timer expires, the game goes dead forcing the balls to drain and ending the player's turn.

=== Final Level: The Long Walk ===

The Long Walk begins with a video clip showing the Dark Judges taking their walk of shame now that they've been defeated and banished. This is followed by all 6 balls being launched into player for a 6-ball Long Walk Multiball. During this multiball, all switches award points (values TBD). This mode (and subsequently the entire Ultimate Challenge) ends when there is only 1 ball remaining in play. The game then begins anew.

== SuperGame ==

Pressing the SuperGame button to start a game instead of the regular Start button initiates an Ultimate Challenge only game. Each ball begins with Ultimate Challenge lit. Shooting the upper right VUK starts Ultimate Challenge at whichever level has not yet been completed by the player during the game in progress.

== High Scores ==

The following high scores are tracked:
* 5 highest regular game scores
* 5 highest supergame scores
* Last player to achieve The Long Walk in regular game
* Last player to achieve The Long Walk in supergame
* Max inner loop combos (upper right flipper loops)
* Max outer loop combos (upper left flipper loops)
* Max number of crimescene levels completed

File:Lamp 2x2 wiring.jpg

2016-02-08T06:07:11Z

Steveshoyer:

Controlling A Lamp Matrix

2016-02-08T06:06:39Z

Steveshoyer: Created page with "As shown in the diagram below, a single PD-8x8 board can control an 8x8 lamp matrix, providing individual control of 64 lamps (or LEDs). Image:Power-Driver-Matrix-8x8_examp..."

As shown in the diagram below, a single PD-8x8 board can control an 8x8 lamp matrix, providing individual control of 64 lamps (or LEDs).

[[Image:Power-Driver-Matrix-8x8_example_use.jpg]]

The [http://www.pinballcontrollers.com/index.php/products/driver-boards/power-driver-matrix-8x8 PD-8x8's] source outputs (Bank A - J7) switch on/off your lamp voltage to the columns, and the PD-8x8's sink outputs (Bank B - J11) switch on/off ground to the rows. To turn a lamp on, both the voltage (source) and ground (sink) need to be on. When using a [http://www.pinballcontrollers.com/index.php/products/p-roc P-ROC] as your main controller, the [http://www.pinballcontrollers.com/index.php/products/p-roc P-ROC] tells the [http://www.pinballcontrollers.com/index.php/products/driver-boards/power-driver-matrix-8x8 PD-8x8] to turn on each source output, one at a time. Each time a source output is on, the [http://www.pinballcontrollers.com/index.php/products/p-roc P-ROC] tells the [http://www.pinballcontrollers.com/index.php/products/driver-boards/power-driver-matrix-8x8 PD-8x8] to turn on ground for the active lamps in the corresponding rows. By cycling through each column fairly quickly, your eyes don't realize each lamp is only on for a maximum of 1/8th the cycle time.

Notice in the illustration that no power output connector is used on the [http://www.pinballcontrollers.com/index.php/products/driver-boards/power-driver-matrix-8x8 PD-8x8] board. Power is sourced to each lamp column through J7.

=== Lamp Voltage ===

[http://www.pinballcontrollers.com/index.php/products/driver-boards/power-driver-matrix-8x8 PD-8x8] boards can source between 5V and 20V DC. The voltage on your matrix is determined by what you connect to the [http://www.pinballcontrollers.com/index.php/products/driver-boards/power-driver-matrix-8x8 PD-8x8] power input connectors (J2 and J6).

Note [http://www.pinballcontrollers.com/index.php/products/driver-boards/power-driver-matrix-8x8 PD-8x8's] will only work with DC voltage, not AC.

=== Matrix Sizes ===

A single [http://www.pinballcontrollers.com/index.php/products/driver-boards/power-driver-matrix-8x8 PD-8x8] board can control an 8x8 lamp matrix.

To control a smaller matrix, don't use all of the outputs. For example, if you want a 2x2 matrix, you would connect only 2 columns (source) and 2 rows (sink) as shown in the following image:

[[Image:Lamp_2x2_wiring.jpg|300px]]

To control a larger matrix, you can use additional 'sink' banks, either by using a Bank B from another [http://www.pinballcontrollers.com/index.php/products/driver-boards/power-driver-matrix-8x8 PD-8x8] or by using either bank from a [http://www.pinballcontrollers.com/index.php/products/driver-boards/power-driver-16 PD-16]. Theoretically, you could add as many additional sink banks as you need, though the [http://www.pinballcontrollers.com/index.php/products/p-roc P-ROC] can only automatically control 224 matrix elements (assuming no other features, like coils, are under the [http://www.pinballcontrollers.com/index.php/products/p-roc P-ROC's] control). To control more than 224 matrix elements, you'll have to issue the matrix column and row commands in software.

Another way to control a larger matrix is to use multiple PD-8x8 source banks, though the [http://www.pinballcontrollers.com/index.php/products/p-roc P-ROC] can automatically control only 2 lamp matrix source banks automatically. To control more than 2 lamp matrix source banks, you'll have to issue the matrix column and row commands in software.

=== Diodes ===

Due to the wiring configuration in a matrix, it's theoretically possible for current flowing through one 'on' lamp to leak through an 'off' lamp in the same row. This is typically avoided with the use of a diode. If a diode is wired in series with each lamp, as shown in the 2x2 matrix image above, current flowing through another lamp can't leak back through.

LED's ARE diodes; so it's generally not necessary to use a separate diode for each LED in an LED matrix. However, some LED bulbs are designed to be bi-directional, allowing the bulb to be plugged in in either orientation. Since current can flow through these bi-directional LED bulbs in either direction, a separate diode is necessary to avoid having current leak through 'off' LEDs, which would result in ghosting.

File:P-Coil.jpg

2016-02-08T06:05:32Z

Steveshoyer:

Controlling Coils

2016-02-08T06:05:05Z

Steveshoyer: /* Controlling coils */

== Hardware ==

The usual way to control coils is to connect power to one side of the coil and to connect the other side to a low-side transistor circuit, such as an n-channel MOSFET. When the transistor is activated, the source voltage has a path to ground through the coil and through the transistor, thereby activating the coil.

Coils are typically controlled with a [http://www.pinballcontrollers.com/index.php/products/driver-boards/power-driver-16 PD-16] board. It's best to connect the power side of the coil to the fused power output connector on the [http://www.pinballcontrollers.com/index.php/products/driver-boards/power-driver-16 PD-16]. This will cause only the [http://www.pinballcontrollers.com/index.php/products/driver-boards/power-driver-16 PD-16]'s fuse to blow if there's ever a serious problem with the coil circuit, rather than taking out various other things on the machine. The other side of the coil is then connected to one of the eight transistor circuits the [http://www.pinballcontrollers.com/index.php/products/driver-boards/power-driver-16 PD-16] provides in each bank.

As shown in the diagram below, banks A and B of the [http://www.pinballcontrollers.com/index.php/products/driver-boards/power-driver-16 PD-16] are completely independent. The voltages used to feed each bank can be the same, but they don't have to be. This diagram is showing how to use bank A to control high power coils and bank B to control low power coils or flashlamps.

[[Image:Power-Driver-16-example-use.jpg|500px]]

=== Controlling coils ===

Coils are used for a variety of features in most pinball machines. Common features with coils are flippers, slingshots, pop bumpers, drop targets, diverters, etc. Most coils are simply a long wire wrapped around a hollow core. When current flows through through the wire, a magnetic field is created in the core. This magnetic field pulls in metal objects. Typically, a steel rod (plunger) is connected to the playfield feature. When the coil is activated (current applied), the steel rod is pulled into the core due to the magnet field. The movement of the rod translates to movement of the feature. For instance, a pop bumper typically has a metal ring attached to the plunger that gets pulled down toward the playfield when the coil activates. This downwards motion pushes the ball away from the pop bumper.

As shown in the picture below, a coil generally has two lugs, sometimes with a diode wired between them.

[[Image:P-Coil.jpg|300]]

To connect a coil to a [http://www.pinballcontrollers.com/index.php/products/driver-boards/power-driver-16 PD-16] board, simply wire power out from the desired bank (J3 or J4) to one lug, and one of the bank's 8 transistor circuits (J7 or J11) to the other lug.

'''Important''': If the coil has diode, you MUST wire power out to the bar end of the diode and the transistor circuit to the non-bar end of the diode. Otherwise, bad things ensue (blown diodes, blown transistors, blown fuses, etc). The [http://www.pinballcontrollers.com/index.php/products/driver-boards/power-driver-16 PD-16] boards have their own diodes on each circuit; so diodes on the coils are unnecessary.

=== Controlling Flippers ===

[[Controlling Flippers|Click here for a more detailed description of flipper control.]]

== Software ==

=== P-ROC ===

The P-ROC can be configured to automatically control your chain of driver boards, allowing you to issue higher level commands (pulse, schedule, patter, etc). If you're using libpinproc (C) or pyprocgame (Python), you'll first need to configure the P-ROC to work with your chain of driver boards. Instructions for doing this are [[Configuring Driver Boards|found here]].

==== libpinproc ====

To activate the coils in a C program using libpinproc, you simply need to call the desired PRDriver... libpinproc function, passing in the handle to your P-ROC, the coil number, and the desired activation params. For instance, to pulse coil 32 for 40 milliseconds:

PRDriverPulse(PRHandle, 32, 40)

Other available driver commands include:

PRDriverSchedule() - Issue a defined pattern that repeats every second
PRDriverPatter() - Issue a repeating pitter-patter style pattern where the coil repeatedly turns on for X ms and off for Y ms.
PRDriverPulsedPatter() - Same as above except the pattern ends after Z ms.
PRDriverDisable() - Turn off the coil

Refer to the [https://github.com/preble/libpinproc libpinproc code] for implementation details.

'''Warning - It's best to use only PRDriverPulse() and PRDriverDisable() commands for high power coils. This will help to eliminate errors that could result in coils staying on too long and burning up or blowing fuses.'''

==== pyprocgame ====

Your machine's YAML file will need to contain coil definitions so that pyprocgame will know know which coils exist on your machine. Here's an example YAML with only the relevant coil items:

PRGame:
machineType: custom

PRCoils:
coil0:
number: PD-16 circuit number for coil0 (0 for board 0, bank A, output 0)
coil1:
number: PD-16 circuit number for coil1 (1 for board 0, bank A, output 1)
coil2:
number: PD-16 circuit number for coil2 (8 for board 0, bank B, output 0)
coil3:
number: PD-16 circuit number for coil3 (16 for board 1, bank A, output 0)

Once your YAML file is loaded into pyprocgame, you can activate your coils by calling:

game.coils.coil0.pulse(40) - Drives coil0 for 40ms

Other available driver methods include:

schedule()
patter()
pulsedpatter()
disable()
enable()

Refer to the [http://pyprocgame.pindev.org/ref/game.html#driver pyprocgame] docs more detailed information.

'''Warning - It's best to use only pulse() and disable() commands for high power coils. This will help to eliminate errors that could result in coils staying on too long and burning up or blowing fuses.'''

==== Direct Control ====

If you'd rather use software to write to the driver board directly, which is possible though eliminates the possibility of using the pulse, schedule, patter, etc functions the P-ROC provides, you can issue direct register writes to the P-ROC that, in turn, get sent to the appropriate driver board. Refer to the [http://www.pinballcontrollers.com/index.php/products/p-roc/documentation P-ROC FPGA documentation] for more details (register addresses and data format)

=== Other controller (non - P-ROC) ===

If you are using a microcontroller such as an Arduino or Parallax Propeller to control your flippers through a [http://www.pinballcontrollers.com/index.php/products/driver-boards/power-driver-16 PD-16], you'll need to do everything in software. Refer to the [http://www.pinballcontrollers.com/index.php/products/driver-boards/power-driver-16 PD-16] documentation for a description of the PDB Protocol used for sending commands to the driver board.

File:WPC coil.jpg

2016-02-08T06:02:50Z

Steveshoyer:

Controlling Flippers

2016-02-08T06:02:19Z

Steveshoyer: Created page with "== Hardware == The usual way to control flipper coils is to connect power (typically a relatively high DC voltage like 70V) to one side of the coil and to connect the other..."

== Hardware ==

The usual way to control flipper coils is to connect power (typically a relatively high DC voltage like 70V) to one side of the coil and to connect the other side to a low-side transistor circuit, such as an n-channel MOSFET. When the transistor is activated, the source voltage has a path to ground through the coil and through the transistor, thereby activating the coil.

Another way to hook up the flipper coils is to connect them to power through flipper buttons and use end-of-stroke switches to to govern how current flows through dual-wound coils. This is how 70V flipper circuits were implemented before the early 90's. If this is how you want to proceed, you don't need a P-ROC or a [http://www.pinballcontrollers.com/index.php/products/driver-boards/power-driver-16 PD-16] for your flipper circuits. You can refer to an early WPC (pre-fliptronics) machine manual for wiring diagrams showing this implementation.

The rest of this page describes how flipper circuits have been implemented since the early 90's and how you could do the same with a P-ROC and [http://www.pinballcontrollers.com/index.php/products/driver-boards/power-driver-16 PD-16], using software controlled (or P-ROC controlled) transistors to activate the flippers when button presses are detected on the appropriate P-ROC switch inputs. Implemented flippers this way affords the designer a lot more control. Because the transistors are controlled programmatically, it is very easy to increase or decrease the flip strength by simply varying the pulse times. A creative designer could even implement modes in their game that intentionally make the flippers weaker or stronger. Other reasons to control flippers programmatically are to have the flexibility to deactivate them at times, enable only one at a time, reverse the button/flipper relationship, only allow them to be held on for specific lengths of time, etc, etc. One other important advantage is that the flipper buttons can be used while the flippers are deactivated (for video modes, entering high score initials, etc).

Flipper coils, like most individual features on a pinball machine, can be controlled with a [http://www.pinballcontrollers.com/index.php/products/driver-boards/power-driver-16 PD-16] board. It's best to connect the power side of the coil to the fused power output connector on the [http://www.pinballcontrollers.com/index.php/products/driver-boards/power-driver-16 PD-16]. This will cause only the [http://www.pinballcontrollers.com/index.php/products/driver-boards/power-driver-16 PD-16]'s fuse to blow if there's ever a serious problem with the coil circuit, rather than taking out various other things on the machine. The other side of the coil is then connected to one of the eight transistor circuits the [http://www.pinballcontrollers.com/index.php/products/driver-boards/power-driver-16 PD-16] provides in each bank.

=== Dual-wound Flipper Coils (WPC-style) ===

Dual-wound coils are essentially two coils in one, for each flipper. One winding is called 'power', and the other is called 'hold'. That's why the coils have 3 terminals. One terminal is a common terminal that brings in power from the driver board. The other two terminals get connected to 2 of the 8 transistor circuits so they can be controlled by the P-ROC. Controlling two dual-wound flipper assemblies will therefore use 4 of the transistor circuits on one bank of a [http://www.pinballcontrollers.com/index.php/products/driver-boards/power-driver-16 PD-16].

The power winding is used to pulse the coil, which is when the flipper flips. That winding should measure about 4 ohms on a resistance meter.

The hold winding is used to hold the coil up after flipping. It can keep the coil active indefinitely, and it only draws about 0.5A because it's about 127 Ohms.

OK... now on to the actual wiring. Refer picture below. The center terminal is the power winding. It should be wired back to one of the transistor circuits. You can use a resistance meter to figure out the other two terminals. Put one probe on the center terminal and the other on one of the others. If it reads about 4 ohms, you've found the common terminal that you'll connect to the [http://www.pinballcontrollers.com/index.php/products/driver-boards/power-driver-16 PD-16]'s power output (J3 or J4 depending on the back you're using). If it reads 131 ohms or so, you've found the 'hold' winding terminal, which also goes to a transistor circuit.

<center>[[Image: WPC_coil.jpg]]</center>

Note - Flipper assemblies with dual wound coils typically include and end-of-stroke (EOS) switch. Before flippers were controlled programmatically, the EOS switch was used to switch power from the power coil to the hold coil. With programmatically controlled flippers, the EOS switch is no longer necessary. Software controls each coil individually and can therefore shut off the power coil whenever necessary. Therefore, the EOS switch doesn't even need to be wired to the P-ROC.

=== Single-wound Flipper Coils (Stern-style) ===

Single-wound flipper coils are much simpler than dual-wound coils, at least electrically, because they have only two terminals. One terminal is connected directly to the power source (power output from a [http://www.pinballcontrollers.com/index.php/products/driver-boards/power-driver-16 PD-16]). The other terminal gets connected to one of the transistor circuits so it can be controlled by the P-ROC. Controlling two single-wound flipper assemblies will therefore use only 2 of the transistor circuits on one bank of a [http://www.pinballcontrollers.com/index.php/products/driver-boards/power-driver-16 PD-16].

The single-wound coil is a high power coil. It draws a lot of current so that the flipper will have enough power to flip the ball. If the coil remains active for longer than a short pulse, though, it will blow the fuse on the [http://www.pinballcontrollers.com/index.php/products/driver-boards/power-driver-16 PD-16]. Otherwise it would destroy either the [http://www.pinballcontrollers.com/index.php/products/driver-boards/power-driver-16 PD-16]'s transistor or the coil itself, maybe even both. To keep this from happening, games with single-wound coils use software (or a P-ROC) to activate the coil for a long flip pulse (30 milliseconds or so) and immediately follow that with short pulses (maybe 2 milliseconds every 20 milliseconds) to keep the flipper active until the flipper button is released.

'''Important''': If your coil has a diode on it, you must wire power to the bar end of the diode and the desired transistor circuit to the non-bar end.

== Software ==

=== P-ROC ===

==== Switch Rules ====

When using a P-ROC with the [http://www.pinballcontrollers.com/index.php/products/driver-boards/power-driver-16 PD-16] to control flippers, the best thing to do is configure P-ROC switch rules. Doing this will configure the P-ROC to automatically drive the flippers appropriately when the flipper buttons are pressed. This is better than trying to activate the flippers programmatically in response to button presses because it eliminates the latency of the switch event getting to software and the coil activation request getting back to the P-ROC.

Whether you're using libpinproc (C) or pyprocgame (Python), your machine's YAML file will need to contain flipper definitions so the software will know which switches to link to link to which coils. Here's an example YAML with only the relevant flipper items:

PRGame:
machineType: custom

PRFlippers:
- flipperLwR
- flipperLwL

PRSwitches:
flipperLwR:
number: P-ROC input number for the Lower Right flipper button
flipperLwL:
number: P-ROC input number for the Lower Left flipper button

PRCoils:
flipperLwRMain:
number: PD-16 circuit number for the LwR main flipper
flipperLwRHold:
number: PD-16 circuit number for the LwR hold flipper - if using dual-wound coils. If not, delete this Hold entry
flipperLwLMain:
number: PD-16 circuit number for the LwL main flipper
flipperLwLHold:
number: PD-16 circuit number for the LwL hold flipper - if using dual-wound coils. If not, delete this Hold entry

===== Configuring the P-ROC =====

You'll need to configure the P-ROC to work with your chain of driver boards. If you're using libpinproc (C) or pyprocgame (Python), instructions for doing this are [[Configuring Driver Boards|found here]].

===== libpinproc =====

For setting up the switch rules, see ConfigureWPCFlipperSwitchRule() (for dual-wound coils) and ConfigureSternFlipperSwitchRule() (for single-wound coils) in the [https://github.com/preble/libpinproc/blob/master/examples/pinproctest/switches.cpp libpinproc pinproctest example code].

===== pyprocgame =====

For setting up the switch rules, refer to the code that already does this for WPC and Stern flippers in pyprocgame. It's done in the enable_flippers() method of the GameController class in [https://github.com/preble/pyprocgame/blob/master/procgame/game/game.py game.py]. Use the WPC method for dual-wound coils and the Stern method for single-wound coils.

==== Software Control ====

If you're dead-set on activating the flippers in your software instead of using P-ROC switch rules, you can do this easily enough.

===== Software control using P-ROC functions =====
If you've configured the P-ROC to control your chain of driver boards, you can simply issue the appropriate pulse or patter commands when the appropriate switch events occur.

====== Dual-wound (WPC-style) Flippers ======
For software control of dual-wound WPC-style flippers, it's recommended to issue both a pulse command (30ms or so) to the power coil and an indefinite pulse (0ms) to the hold coil when the flipper button is pushed. Then deactivate both coils when the flipper button is released.

====== Single-wound (Stern-style) Flippers ======
For single-wound Stern-style flippers, it's recommend to issue a patter command when the flipper button is pushed. Use an on/off cycle time of about 2ms/18ms, respectively, and give it an original_on_time of 30 ms or so for the initial flip. Then deactivate the coil when the flipper button is released.

===== Software control without using P-ROC functions =====

If you'd rather use software to write to the driver board directly, which is possible though eliminates the possibility of using the pulse, schedule, patter, etc functions the P-ROC provides, you can issue direct register writes to the P-ROC that, in turn, get sent to the appropriate driver board. Refer to the [http://www.pinballcontrollers.com/index.php/products/p-roc/documentation P-ROC FPGA documentation] for more details.

=== Other controller (non - P-ROC) ===

If you're using a microcontroller such as an Arduino or Parallax Propeller to control your flippers through a [http://www.pinballcontrollers.com/index.php/products/driver-boards/power-driver-16 PD-16], you'll need to do everything in software. Refer to the [http://www.pinballcontrollers.com/index.php/products/driver-boards/power-driver-16 PD-16] documentation for a description of the PDB Protocol used for sending commands to the driver board.

Controlling Coils

2016-02-08T06:01:11Z

Steveshoyer: Created page with "== Hardware == The usual way to control coils is to connect power to one side of the coil and to connect the other side to a low-side transistor circuit, such as an n-channe..."

== Hardware ==

The usual way to control coils is to connect power to one side of the coil and to connect the other side to a low-side transistor circuit, such as an n-channel MOSFET. When the transistor is activated, the source voltage has a path to ground through the coil and through the transistor, thereby activating the coil.

Coils are typically controlled with a [http://www.pinballcontrollers.com/index.php/products/driver-boards/power-driver-16 PD-16] board. It's best to connect the power side of the coil to the fused power output connector on the [http://www.pinballcontrollers.com/index.php/products/driver-boards/power-driver-16 PD-16]. This will cause only the [http://www.pinballcontrollers.com/index.php/products/driver-boards/power-driver-16 PD-16]'s fuse to blow if there's ever a serious problem with the coil circuit, rather than taking out various other things on the machine. The other side of the coil is then connected to one of the eight transistor circuits the [http://www.pinballcontrollers.com/index.php/products/driver-boards/power-driver-16 PD-16] provides in each bank.

As shown in the diagram below, banks A and B of the [http://www.pinballcontrollers.com/index.php/products/driver-boards/power-driver-16 PD-16] are completely independent. The voltages used to feed each bank can be the same, but they don't have to be. This diagram is showing how to use bank A to control high power coils and bank B to control low power coils or flashlamps.

[[Image:Power-Driver-16-example-use.jpg|500px]]

=== Controlling coils ===

Coils are used for a variety of features in most pinball machines. Common features with coils are flippers, slingshots, pop bumpers, drop targets, diverters, etc. Most coils are simply a long wire wrapped around a hollow core. When current flows through through the wire, a magnetic field is created in the core. This magnetic field pulls in metal objects. Typically, a steel rod (plunger) is connected to the playfield feature. When the coil is activated (current applied), the steel rod is pulled into the core due to the magnet field. The movement of the rod translates to movement of the feature. For instance, a pop bumper typically has a metal ring attached to the plunger that gets pulled down toward the playfield when the coil activates. This downwards motion pushes the ball away from the pop bumper.

As shown in the picture below, a coil generally has two lugs, sometimes with a diode wired between them.

[[Image:Coil.jpg|300]]

To connect a coil to a [http://www.pinballcontrollers.com/index.php/products/driver-boards/power-driver-16 PD-16] board, simply wire power out from the desired bank (J3 or J4) to one lug, and one of the bank's 8 transistor circuits (J7 or J11) to the other lug.

'''Important''': If the coil has diode, you MUST wire power out to the bar end of the diode and the transistor circuit to the non-bar end of the diode. Otherwise, bad things ensue (blown diodes, blown transistors, blown fuses, etc). The [http://www.pinballcontrollers.com/index.php/products/driver-boards/power-driver-16 PD-16] boards have their own diodes on each circuit; so diodes on the coils are unnecessary.

=== Controlling Flippers ===

[[Controlling Flippers|Click here for a more detailed description of flipper control.]]

== Software ==

=== P-ROC ===

The P-ROC can be configured to automatically control your chain of driver boards, allowing you to issue higher level commands (pulse, schedule, patter, etc). If you're using libpinproc (C) or pyprocgame (Python), you'll first need to configure the P-ROC to work with your chain of driver boards. Instructions for doing this are [[Configuring Driver Boards|found here]].

==== libpinproc ====

To activate the coils in a C program using libpinproc, you simply need to call the desired PRDriver... libpinproc function, passing in the handle to your P-ROC, the coil number, and the desired activation params. For instance, to pulse coil 32 for 40 milliseconds:

PRDriverPulse(PRHandle, 32, 40)

Other available driver commands include:

PRDriverSchedule() - Issue a defined pattern that repeats every second
PRDriverPatter() - Issue a repeating pitter-patter style pattern where the coil repeatedly turns on for X ms and off for Y ms.
PRDriverPulsedPatter() - Same as above except the pattern ends after Z ms.
PRDriverDisable() - Turn off the coil

Refer to the [https://github.com/preble/libpinproc libpinproc code] for implementation details.

'''Warning - It's best to use only PRDriverPulse() and PRDriverDisable() commands for high power coils. This will help to eliminate errors that could result in coils staying on too long and burning up or blowing fuses.'''

==== pyprocgame ====

Your machine's YAML file will need to contain coil definitions so that pyprocgame will know know which coils exist on your machine. Here's an example YAML with only the relevant coil items:

PRGame:
machineType: custom

PRCoils:
coil0:
number: PD-16 circuit number for coil0 (0 for board 0, bank A, output 0)
coil1:
number: PD-16 circuit number for coil1 (1 for board 0, bank A, output 1)
coil2:
number: PD-16 circuit number for coil2 (8 for board 0, bank B, output 0)
coil3:
number: PD-16 circuit number for coil3 (16 for board 1, bank A, output 0)

Once your YAML file is loaded into pyprocgame, you can activate your coils by calling:

game.coils.coil0.pulse(40) - Drives coil0 for 40ms

Other available driver methods include:

schedule()
patter()
pulsedpatter()
disable()
enable()

Refer to the [http://pyprocgame.pindev.org/ref/game.html#driver pyprocgame] docs more detailed information.

'''Warning - It's best to use only pulse() and disable() commands for high power coils. This will help to eliminate errors that could result in coils staying on too long and burning up or blowing fuses.'''

==== Direct Control ====

If you'd rather use software to write to the driver board directly, which is possible though eliminates the possibility of using the pulse, schedule, patter, etc functions the P-ROC provides, you can issue direct register writes to the P-ROC that, in turn, get sent to the appropriate driver board. Refer to the [http://www.pinballcontrollers.com/index.php/products/p-roc/documentation P-ROC FPGA documentation] for more details (register addresses and data format)

=== Other controller (non - P-ROC) ===

If you are using a microcontroller such as an Arduino or Parallax Propeller to control your flippers through a [http://www.pinballcontrollers.com/index.php/products/driver-boards/power-driver-16 PD-16], you'll need to do everything in software. Refer to the [http://www.pinballcontrollers.com/index.php/products/driver-boards/power-driver-16 PD-16] documentation for a description of the PDB Protocol used for sending commands to the driver board.

Driver Board hardware installation

2016-02-08T06:00:11Z

Steveshoyer: Created page with "== PD-Master == * Install the Master near the P-ROC (or other controller). *Master board J8 connects to P-ROC J34 header via the 16-pin ribbon cable that came with the board...."

== PD-Master ==
* Install the Master near the P-ROC (or other controller).

*Master board J8 connects to P-ROC J34 header via the 16-pin ribbon cable that came with the board.
**If you're not using a P-ROC, connect your controller's serial data pin to pin 1 on the Master board's ribbon cable header and at least one ground pin from your controller to an even numbered pin on ribbon cable header.
**Note, the Master board's data input pin (pin 1 on the ribbon cable header) is a 3.3V input. It is NOT 5V tolerant. If you are using a 5V controller, be sure to level translate the signal before it reaches the Master board. Simply using a current limiting resistor is NOT sufficient.

*Connect the Master board's Serial Output connector (J10) to next board's Serial Input connector (J9).

*Connect 5V to J1.

Note - These instructions also apply to the master portion of master-combo boards.

== PD-16 ==

*Connect 5V to J1.

*Connect the the Serial Input connector (J9) to previous board's Serial Ouptut connector (J10) (unless this is a master-combo board)

*Connect the the Serial Output connector (J10) to next board's Serial Input connector (J9).

*Set the address (dipswitches 4 through 1) to a unique address. Dipswitches 4:1 map to board address 3:0. Switch ON is 1, switch OFF is 0.
**Note, P-ROC drivers can be configured into driver groups for the first 8 board addresses (0-7). When using a P-ROC, boards with addresses greater than 7 must be accessed directly by software by writing the appropriate data to Module 3, Address 0xC00. Refer to the [http://www.pinballcontrollers.com/index.php/p-roc/documentation P-ROC FPGA specs] for more details on the command format.

=== Bank A ===

*Connect your voltage source (5V-80V) to the Bank A Power Input connector (J5)

*Use the Bank A Power Output connector (J3) to supply power to the devices you want to control with this board/bank.

*Connect each of your devices to the desired pin in J7. J7 connects to the Bank A transistors, which complete the path to ground when activated.

*Ensure F1 has a properly rated fuse for your application

=== Bank B ===

*Connect your voltage source (5V-80V) to the Bank B Power Input connector (J6)

*Use the Bank B Power Output connector (J4) to supply power to the devices you want to control with this board/bank.

*Connect each of your devices to the desired pin in J11. J11 connects to the Bank B transistors, which complete the path to ground when activated.

*Ensure F2 has a properly rated fuse for your application

=== Example Illustration ===

[[Image:Power-Driver-16-example-use.jpg]]

== PD-8x8 ==

*Connect 5V to J1.

*Connect the the Serial Input connector (J9) to previous board's Serial Ouptut connector (J10) (unless this is a master-combo board)

*Connect the the Serial Output connector (J10) to next board's Serial Input connector (J9).

*Set the address (dipswitches 4 through 1) to a unique address. Dipswitches 4:1 map to board address 3:0. Switch ON is 1, switch OFF is 0.
**Note, P-ROC drivers can be configured into driver groups for the first 8 board addresses (0-7). When using a P-ROC, boards with addresses greater than 7 must be accessed directly by software by writing the appropriate data to Module 3, Address 0xC00. Refer to the [http://www.pinballcontrollers.com/index.php/p-roc/documentation P-ROC FPGA specs] for more details on the command format.

=== Bank A ===

*Connect your voltage source (5V-20V) to the Bank A Power Input connector (J5)

*Use the Bank A Power Output connector (J3) to supply power to the devices you want to control with this board/bank.

** Note: If using this board to drive a lamp/led matrix, leave J3 unconnected.

*Connect each of your devices to the desired pin in J7. J7 connects to the Bank A transistors, which complete the path to ground when activated.

** Note: If using this board to drive a lamp/led matrix, connect J7 to the anode side of your LED matrix (or the input power side of your lamp matrix).

*Ensure F1 has a properly rated fuse for your application

=== Bank B ===

*Connect your voltage source (5V-80V) to the Bank B Power Input connector (J6)

*Use the Bank B Power Output connector (J4) to supply power to the devices you want to control with this board/bank.

** Note: If using this board to drive a lamp/led matrix, leave J4 unconnected.

*Connect each of your devices to the desired pin in J11. J11 connects to the Bank B transistors, which complete the path to ground when activated.

** Note: If using this board to drive a lamp/led matrix, connect J11 to the cathode side of your LED matrix (or the return side of your lamp matrix).

*Ensure F2 has a properly rated fuse for your application

=== Example Illustration ===

[[Image:Power-Driver-Matrix-8x8_example_use.jpg]]

== Cabling Guide ==

=== Connectors ===

These boards use the following molex connectors:

{| border="1"
!colspan="2"|Molex Connectors
|-
!scope="col"|0.100"
!scope="col"|0.156"
|-
|2-pin: J9 - Serial In||2-pin: J1 - 5V
|-
|2-pin: J10 - Serial Out||3-pin: J2 - Bank A Source In
|-
| ||3-pin: J3 - Bank A Sink Out
|-
| ||3-pin: J4 - Bank B Out
|-
| ||3-pin: J5 - Bank A Sink In
|-
| ||3-pin: J6 - Bank B In
|-
| ||9-pin: J7 - Bank A
|-
| ||9-pin: J11 - Bank B
|}

*Note: Not all connectors are used on all boards.

==== Tips ====

*Get a good crimp tool. Crimping a lot of pins with a hard to use tool isn't fun!
*Buy connector housings with ramps. Not only do they hold the header in place, but they also make it obvious which way to plug on the header.
*Use keying plugs on the key pins. The board connector's use different key patterns to differentiate the various types of connections (ie. power in vs power out). Using keying plugs in your connector housings will help you avoid accidentally plugging housings onto the wrong headers.
*Buy a few extra housings with the largest number of pins you foresee needing. You can always cut them down if you ever need smaller ones.

=== Vendors ===

Molex connectors/pins/housings: [http://www.greatplainselectronics.com Great Plains Electronics]*, [http://www.digikey.com Digikey], [http://www.mouser.com Mouser]

* [http://www.greatplainselectronics.com Great Plains Electronics] primarily supports pinball hobbyists. His prices are comparable (and sometimes lower) than [http://www.digikey.com Digikey] and [http://www.mouser.com Mouser]. It's also much easier to browse his selection to find the most appropriate parts.

File:Power-Driver-Matrix-8x8 example use.jpg

2016-02-08T05:58:57Z

Steveshoyer:

File:Power-Driver-16-example-use.jpg

2016-02-08T05:58:22Z

Steveshoyer:

Driver Board functionality

2016-02-08T05:57:24Z

Steveshoyer: Connecting driver boards to a P-ROC

[http://www.pinballcontrollers.com/index.php/driver-boards PinballControllers.com Driver Boards] contain circuits that turn on/off external devices, such as those commonly found on pinball machines.

Unlike with traditional pinball machine power/driver boards, multiple [http://www.pinballcontrollers.com/index.php/driver-boards PinballControllers.com Driver Boards] can be used at the same time in a machine. They were designed with a 2-wire [http://en.wikipedia.org/wiki/EIA-485 RS-485] serial interface so that they can be chained together and located anywhere in the machine (in the backbox, under the playfield, or even somewhere else in the cabinet).

Each board contains a set of dipswitches, four of which are used to set a board address. Further, each board is logically divided into two banks of 8 circuits, bank A and bank B. The P-ROC, or other device controlling the chain of boards, can individually address each bank on each of the 16 possible board addresses. Refer to the [http://www.pinballcontrollers.com/index.php/p-roc/documentation documentation] for each board for more details on the addressing.

== [http://www.pinballcontrollers.com/index.php/driver-boards/power-driver-16 Power-Driver-16 Driver Boards] ==

The [http://www.pinballcontrollers.com/index.php/driver-boards/power-driver-16 Power-Driver-16] boards contain 16 [[Current Sourcing and Sinking|current sink]] circuits and can therefore control up to 16 individual features.

Each bank of 8 [[Current Sourcing and Sinking|current sink]] circuits contains a 3-pin power input header, a fuse, a 3-pin power output header, 8 n-channel [http://en.wikipedia.org/wiki/MOSFET MOSFETs], and a 9-pin header used to connect external devices to the board. The power input header can accept between 5VDC and 80VDC. This power goes through the fuse and then to the power output header. All 8 devices controlled by each bank should be powered from this power output header so that the fuse protects the 8 devices from over-current conditions without affecting other circuits. The other side of the 8 devices should connect back to the 9-pin header so that the board can activate each circuit individual.

Here's a diagram of one way this board can be used:

[[Image:Power-Driver-16-example-use.jpg]]

== [http://www.pinballcontrollers.com/index.php/driver-boards/power-driver-matrix-8x8 Power-Driver-Matrix-8x8 Driver Boards] ==

[http://www.pinballcontrollers.com/index.php/products/driver-boards/power-driver-matrix-8x8 Power-Driver-Matrix-8x8] boards contain 8 [[Current Sourcing and Sinking|current source]] circuits and 8 [[Current Sourcing and Sinking|current sink]] circuits and are therefore good for controlling 8 columns and 8 rows, respectively, of a lamp/led matrix.

The bank of 8 [[Current Sourcing and Sinking|current sink]] circuits works exactly like the bank of [[Current Sourcing and Sinking|current sink]] circuits on the [http://www.pinballcontrollers.com/index.php/driver-boards/power-driver-16 Power-Driver-16] boards. Each bank of 8 [[Current Sourcing and Sinking|current source]] circuits contains a 3-pin power input header, a fuse, 8 p-channel [http://en.wikipedia.org/wiki/MOSFET MOSFETs], and a 9-pin header used to connect external devices to the board. The power input header can accept between 5VDC and 20VDC. This power goes through the fuse and then to 8 [http://en.wikipedia.org/wiki/MOSFET MOSFETs]. The drain side of the [http://en.wikipedia.org/wiki/MOSFET MOSFETs] are then connected to the 9-pin header from which 8 external devices or matrix columns can be powered.

Here's a diagram of one way this board can be used:

[[Image:Power-Driver-Matrix-8x8_example_use.jpg]]

List of P-ROC Open Source projects

2016-02-08T05:56:24Z

Steveshoyer: P-ROC projects with available source files

The best way to learn how to write custom pinball machine code is to look at existing projects. Here's a list of existing projects with source code that you can take a look at. Many of these are not complete, but it's a starting point for understanding how to write code for the P-ROC system.

* There's a game called "Starter" which comes in the P-ROC software download package. It's not complete, but a nice starting point.
* [https://github.com/preble/JD-pyprocgame Judge Dredd], by Gerry Stellenberg
* [https://github.com/epthegeek/cactuscanyon/ Cactus Canyon], by forum user Epthegeek
* [https://github.com/Compy/TAF The Addams Family], by forum user Compy
* [https://github.com/mypinballs/indianajones Indiana Jones, The Pinball Adventure], by Jim from http://mypinballs.co.uk
* [https://github.com/mypinballs/whirlwind Whirlwind], by Jim from http://mypinballs.co.uk
* [https://github.com/preble/creature Creature from the Black Lagoon], by Adam Preble
* [https://github.com/Snux/F14SecondSortie F-14 Tomcat Second Sortie], by forum user Snux
* [https://https://github.com/scottdanesi/earthshaker-aftershock Earthshaker Aftershock], by Scott Danesi
* [https://github.com/koenheltzel/thexfiles The X Files], by forum user Koen
* [https://missionpinball.com/framework The Mission Pinball Framework], a work-in-progress by forum users Brian Madden and Gabe Knuth (This is not a single game, but rather a game framework alternative to pyprocgame that also works with the P-ROC)

There's a discussion in the [http://www.pinballcontrollers.com/forum/index.php?topic=861.0 forum] about which of these games you should look at first in order to understand them. The general consensus is you should start with Creature from the Black Lagoon, then dig into The Addams Family. Eric's Cactus Canyon is complete with a lot of modes and very complex (including support for color DMDs), so it's not something a newbie should jump into right away.

File:Font CC 20px az.png

2016-02-08T05:52:26Z

Steveshoyer:

File:Font CC 17px score.png

2016-02-08T05:52:02Z

Steveshoyer:

File:Font CC 15px az.png

2016-02-08T05:51:34Z

Steveshoyer:

File:Font CC 13px wide score.png

2016-02-08T05:51:10Z

Steveshoyer:

File:Font CC 13px score.png

2016-02-08T05:50:41Z

Steveshoyer:

File:Font CC 13px thin score.png

2016-02-08T05:50:13Z

Steveshoyer:

File:Font CC 13px extra thin score.png

2016-02-08T05:49:44Z

Steveshoyer:

File:Font CC 12px az.png

2016-02-08T05:49:10Z

Steveshoyer:

File:Font CC 9px az.png

2016-02-08T05:48:42Z

Steveshoyer:

File:Font CC 7px bold az.png

2016-02-08T05:48:19Z

Steveshoyer:

File:Font CC 7px az.png

2016-02-08T05:47:52Z

Steveshoyer: