I found this old video the other day and realized I didn’t have a post on my main site showcasing this video so I wanted to add it (also, this was before I learned the proper pronunciation of “Bally” LOL…. bah-lee).
Category Archives: Circuit Board
Prototyping A Brand New Mata Hari Ruleset!
I’ve been working on a new project that I’m very excited about. There’s been a movement to create an inexpensive, non-destructive and simple way to mod early Bally/Stern solid state games and add more features. In this video, I demonstrate an early prototype of the system used to modify a Bally Mata Hari pinball machine to include new features such as a skill shot, modes and even a wizard mode.
Want to learn more about this project? Visit: https://github.com/BallySternOS
Repairing/Replacing a Stern/Bally Power Supply/Rectifier Board
As part of the ongoing restoration of a 1979 Stern “Trident” pinball machine, here’s a series of videos outlining how to replace the rectifier board on these games. This varies a bit between Stern and Bally due to wire color codes. References are here.
WPC game doesn’t boot up? Let’s diagnose this Gilligan’s Island.
You turn on your game and… “BLECH!” that’s what you get? That’s not good. Let’s try to figure out what exactly is happening:
Armed with more information, later on I have some time to pull the driver board and diagnose things further:
Tracking down drop targets that won’t reset – Bally-35 “Mystic”
This is a game that’s been sitting in the back for awhile at my place that I keep meaning to get to, so I finally jumped back into to figure out what was wrong. It’s weird to go over notes you made 6+ months ago and try to pick back up where you left off — remind me not to do that.. LOL But the issue was relatively simple: The center bank of drop targets was not resetting.
In this series of videos, I go over, step-by-step the process of how to figure out what’s causing this problem, how to read schematics and manual diagrams, and the various points of failure, and once again, we are reminded of “Ockham’s Razor” which suggests the most obvious cause is the most likely… OR IS IT?
Interestingly enough, once I figured out where the problem was, rather than solve it the traditional way, I choose to do a “hack”… basically just to see if I could do it. The choice was, do you replace an entire 16-pin IC that’s only using one small part of it (involving adding a socket and a new chip that is pretty expensive and hard to find) or do you “hack” the damaged chip and piggyback a new component on top of it? Normally I don’t do these kinds of MacGuyver stuff on system boards, but it was a fun trick to try and it cost a few cents and about 10 minutes verses a lot more time than would have been used to replace a whole IC.
One reason why this hack job is particularly sloppy is because I had to work on the board in the game due to the previous owner having hard-soldered some wires to one of the connectors – that’ll be another future project to clean up all that mess, but for now, I needed to get this back working.
To understand what I did, here is a substitute circuit board showing the position of various individual 2N4401 transistors overlaid on the CA3081 IC package. Using this you can figure out where to insert a transistor manually on the IC pinouts if one of them fails:
How to test bridge rectifiers (in pinball machines and elsewhere)
The other day I was working on a game and traced the problem back to a blown bridge rectifier, so I thought it might be nice to produce a short little video on how to test/check bridge rectifiers in pinball machines, as well as a little info on what they do.
Diagnosing problems with Mist Multiball mechanism on Bram Stoker’s Dracula
Diagnosing problems with the mist multi-ball assembly on a Bally/WMS Bram Stoker’s Dracula pinball machine. In this case, we were not getting power to the motor, which is supplied from the 20vdc circuit on the power driver board (which also powers the flash lamps). In this series of videos I show how to test the mist motor, and where you check for power and back-trace it to the driver board, then identify which components are related to this problem and how to fix it.