claude-haiku-4-5-20251001 · $0.029
Frank Lindenmuth teaches systematic pinball repair diagnostics through real case studies.
A shorted capacitor on a switch line was the entire problem with a Centipede board where a tech had replaced every single chip.
high confidence · Frank directly describes this repair experience he personally conducted, explaining the tech overlooked the debouncing capacitor.
A bad diode on a magnet control board near the 30C was causing random resets on a WPC game during magnet test sequences.
high confidence · Frank describes methodically isolating the magnet control board section and identifying the failed diode through systematic coil test isolation.
An LED socket in a Congo machine was leaning over and touching a switch line, preventing the start button from working in attract mode but functioning in test mode.
high confidence · Frank explains the root cause: the computer doesn't pulse the lamp matrix in test mode, so there's no interference.
Diodes on pinball coils exist to prevent flyback voltage spikes that would otherwise damage transistors or board traces, similar to spark plug ignition coils in cars.
high confidence · Frank provides technical explanation with automotive analogy and discusses placement differences between System 11, PPB board, and WPC architectures.
A Stern Star Wars machine refused code updates due to a network cable failure, not the node board itself, discovered only after swapping the network cable from Guardians of the Galaxy.
high confidence · Frank describes a two-month troubleshooting saga where Stern tech support blamed the node board; swapping the network cable resolved the update issue.
“somewhere between what the customer tells you and what's wrong with the game is the truth”
Frank Lindenmuth@ 0:35 — Sets the tone for why systematic diagnosis is essential; customers often don't know what they did or what's actually broken.
“experience knows no substitute”
Frank Lindenmuth@ 20:32 — Core philosophy: you can read books and forums, but hands-on practice is the only way to truly learn pinball repair.
“I know what the problem was. I didn't even have to look at the board”
Frank Lindenmuth@ 4:13 — Demonstrates how deep technical knowledge allows experienced techs to diagnose from context clues before physical inspection.
“before you buy any parts, you want to check and see if the game's not seeing the ball sit there, or it is seeing it sit there and it can't do anything about it”
Frank Lindenmuth@ 19:25 — Key diagnostic framework: isolate whether the problem is sensor recognition or actuator response before purchasing anything.
“I didn't write this for you. I wrote this for the guy that doesn't know about Pinwiki. Pinside, who doesn't know anything about it.”
Frank Lindenmuth@ 23:51 — Explains his philosophy of creating beginner-friendly content rather than catering to experienced technicians who already know advanced resources.
community_signal: Frank Lindenmuth actively shares repair knowledge through Facebook (No Quarters Arcade page), tech articles, and in-person events, tailoring content for beginners rather than experienced technicians.
high · Frank states: 'I wrote this for the guy that doesn't know about Pinwiki. Pinside, who doesn't know anything about it' and encourages audience members to follow his Facebook page for ongoing support.
community_signal: Frank demonstrates commitment to helping newer technicians and hobby players through education, real-time troubleshooting assistance, and accessible documentation.
high · Frank offers to message audience member about Valley's Truck Stop findings on Facebook, walks through diagnostic process step-by-step, emphasizes that experience comes from hands-on learning.
product_concern: Multiple case studies demonstrate poor repair quality from previous technicians: replacing all chips instead of diagnosing a capacitor, damaging board traces during repair, using cheap sockets with bad contacts. Frank emphasizes systematic approach as solution.
high · Centipede case where tech replaced every chip; F-14 Tomcat where tech damaged blanking circuit trace; diner situation where tech used cheap socket causing contact issues.
technology_signal: Stern Spike network cable failures and node board diagnostics reveal either inadequate support protocols or misdiagnosis by manufacturer tech support. Two-month troubleshooting saga suggests either poor documentation or communication.
high · Star Wars case study: Stern blamed node board, refused warranty replacement, provided no intermediate update versions, and didn't acknowledge network cable as potential failure point. Frank discovered root cause only through systematic swapping.
youtube_groq_whisper · $0.146