Show Notes
Thanks to our Partners, Pico Technology, and Autel Watch Full Video Episode In this episode of Diagnosing the Aftermarket A to Z, Matt Fanslow starts with a case study on a 2000 Ford Excursion with a 7.3L Power Stroke that came in with a severe lack of power. What began as a fuel delivery problem turned into a more interesting diagnostic puzzle involving a P1280 injection control pressure sensor code, an aftermarket ICP sensor, and a fault that appeared to happen not during cranking or running, but after key-off. The case becomes a practical example of why testing under actual operating conditions matters. Static tests can pass, scan data can look normal, and a meter may never show the event. In this case, the scope captured something the rest of the tools could easily miss. Matt then shifts into a listener question about artificial intelligence, especially large language models like ChatGPT, Gemini, Claude, Grok, and others. The concern is not simply whether AI is good or bad, but whether people, especially kids, may begin outsourcing too much thinking, writing, problem-solving, and confidence to these tools. The episode lands on a recurring theme: tools are not the problem by themselves. The question is how they are used, what skills may atrophy when they are overused, and whether individuals, families, businesses, industries, and society are willing to think more carefully and evidence-first about the long-term effects. Topics Covered 2000 Ford Excursion 7.3L Power Stroke Case Study Matt discusses a 7.3L Power Stroke with a major lack-of-power concern. The initial issue was tied to the low-pressure fuel supply side. A basic fuel pressure test had passed, but it had not been tested under the actual conditions where the symptom occurred. That led to a larger point: testing at idle, key-on, or during cranking is not the same as testing under load. The vehicle ultimately had damaged pickup screens and debris in the fuel tank. Cleaning the tank and replacing the failed components solved the fuel supply issue, but another problem remained. The P1280 ICP Sensor Problem After the fuel supply repair, the truck began setting a P1280 code, related to the injection control pressure sensor circuit reading low. The strange part was that the voltage looked normal: Key-on engine-off voltage looked normal. Cranking voltage did not drop. Five-volt reference stayed stable. Sensor ground stayed stable. The signal looked fine while running. The meter never really caught the failure. The scope eventually revealed the important event: after key-off, the ICP signal voltage would sometimes dip nearly to zero. That appeared to be enough for the PCM to set the code on the next key cycle. Scope vs. Meter vs. Scan Tool This case is a useful reminder that each tool has limits. A scan tool may not refresh fast enough or may stop collecting data after key-off. A meter may technically sample quickly, but the display may not show a short event clearly. The oscilloscope was the tool that made the failure visible. The point is not that one tool is always better. The point is knowing which tool fits the question being asked. Aftermarket Sensor Behavior The aftermarket ICP sensor appeared to produce a rebound effect after shutdown. Matt compares the behavior to something like inertial rebound, a concept familiar from certain pressure pulse sensors and piezo-style tools. The OE Motorcraft sensor did not reproduce the same behavior. Replacing the aftermarket sensor with the OE sensor corrected the issue. Main Diagnostic Takeaways Testing has to match the failure condition. A fuel pressure test that passes at idle does not prove the fuel system can keep up under load. A sensor can create a failure outside the moment most people are watching. In this case, the important event seemed to occur after key-off. A scope can reveal details that a scan tool or meter may miss, especially when the event is brief, intermittent, or happens outside normal observation windows. A
More from Automotive Field Theory
Watch Full Video Episode What happens when a customer decides to take their business elsewhere? Do you make it easy for them to leave, or do you make sure they never want to come back? In this episode of Automotive Field Theory, Matt Fanslow shares a frustrating experience switching internet service providers at Riverside Automotive. What started as a fairly straightforward decision to upgrade the shop's internet and phone service turned into an unexpected lesson in customer relationships, business strategy, and understanding the game we're actually playing. Along the way, Matt discusses the challenges of building a reliable shop network, the importance of upload speeds for modern automotive training and communication, and how a properly designed network helped solve years of connectivity problems. But the bigger question isn't about internet service. It's about what happens when a business takes a customer's decision to leave personally. How do we respond when a customer decides our repair estimate is too expensive? What happens when they choose another shop? Are we preserving the possibility of a future relationship, or are we so focused on the immediate transaction that we destroy it? Drawing on game theory and the concept of infinite games, Matt explores why the way we handle these situations can have consequences far beyond a single repair order. Topics discussed: Why Riverside Automotive switched from cable internet to fiber Shop networking, Wi-Fi access points, and the value of reliable infrastructure How a routine service cancellation became a lesson in poor customer relations Why customer retention isn't always about discounts or lower prices Handling customers who choose a competing repair facility The difference between losing a transaction and losing a relationship How negative experiences influence word of mouth and future business Finite versus infinite games and why the distinction matters in business Why the same principles apply to employees who decide to leave
Watch Full Video Episode What does sexual health have to do with automotive repair? More than you might think. Margaret Light, licensed marriage and family therapist and certified sex therapist, returns to Automotive Field Theory for a conversation that begins with a simple question about chemical exposure in the workplace and develops into a much broader discussion about sexual health, relationships, misinformation, shame, and communication. Matt and Margaret explore how little many of us actually understand about our own bodies, how cultural expectations shape our understanding of sex, and how misinformation can create unnecessary conflict within relationships. They also discuss the relationship between physical and psychological health, differences in sexual desire between partners, the role of shame when our bodies or relationships change, and why sexual health deserves more thoughtful attention from both healthcare professionals and individuals. As the conversation unfolds, Matt brings his automotive diagnostic perspective to the discussion: Are we addressing underlying problems, or simply treating symptoms? And what happens when we approach complicated human problems with the same assumptions we've always had? Topics discussed include: Chemical exposure in automotive repair and potential implications for personal and sexual health The limitations of traditional sex education and the prevalence of misinformation Pelvic floor health and the importance of understanding our own anatomy Finding credible sexual health information and distinguishing evidence from cultural assumptions Why sexual health concerns often involve both physical and psychological factors Treating symptoms versus identifying underlying causes Differences in sexual desire and how couples navigate them Shame, aging, changing bodies, and expectations within relationships Cultural attitudes toward sexual entitlement and obligation Ethical non-monogamy, jealousy, and different relationship structures Redefining intimacy when physical abilities or circumstances change Developing the communication skills necessary to discuss difficult or uncomfortable subjects Leading with curiosity instead of assumptions, judgment, or defensiveness
Watch Full Video Episode Recorded live at ASTA 2026 in Raleigh, North Carolina, Matt Fanslow sits down with Tim Iezzi, Ira Waldman, and Chris Farley for a conversation about diagnostic training, module programming, and the realities of fixing cars. The group shares wrong turns, software headaches, and those uncomfortable moments when a vehicle drove into the bay but suddenly won’t start. They discuss why effective training includes the mistakes along with the successful repair, and why a repeatable diagnostic process matters more than an unusual case study. From frozen progress bars and constantly changing software to wiring diagrams and working in an icy parking lot, there’s plenty here that technicians will recognize. Topics discussed Teaching diagnostic process through real cases, including the steps that went wrong. No-start diagnosis and getting sidetracked by an assumed immobilizer problem. Power probes, testing mistakes, and understanding what your test actually proves. Programming anxiety, patience, and the temptation to interrupt a stalled-looking session. Changing OEM software, authentication requirements, and the challenge of keeping procedures current. Software conflicts, dedicated laptops, updates, and backup equipment. Printing and marking wiring diagrams to make complex circuits easier to follow. Preparing for mobile diagnostic calls and adapting to conditions outside the shop. Remote programming, internet latency, and connection reliability.
Watch Full Video Episode What if the same technology we blame for weakening mechanical aptitude could help rebuild it? In this episode of Automotive Field Theory, Matt considers whether YouTube, internet access, and large language models could help address the automotive industry’s skill gap. Younger generations may be less likely to grow up around parents, grandparents, or neighbors who routinely repair cars, appliances, and homes—but they now have immediate access to demonstrations, explanations, and step-by-step guidance. These tools can certainly become a crutch. Much like GPS can get someone to a destination without teaching them how to read a map, an instructional video or AI-generated procedure can help someone complete a task without necessarily understanding the underlying system. But that may not be the whole story. For someone without a mechanically inclined mentor, a YouTube video or AI assistant may provide the encouragement and initial guidance needed to attempt a repair. The result will not always be successful, and professional shops regularly see the aftermath of DIY repairs gone wrong. Still, taking something apart, getting stuck, finding additional information, asking for help, and eventually working through the problem can begin developing real mechanical aptitude. That raises an interesting possibility: some of the people who eventually enter the automotive profession may trace their interest not to holding a flashlight for a parent or grandparent, but to repairing their own vehicle with help from a screen. In this episode: How mechanical aptitude was traditionally developed Why fewer young people grow up around hands-on repair The similarity between diagnostic databases, AI, and GPS The difference between following instructions and understanding a system Why unsuccessful DIY repairs may still create useful experience The limits of translating personal repair experience into professional work How YouTube and AI could provide a new entry point into the trades Whether technology is eliminating mechanical aptitude—or cultivating it in a different way
Watch Full Video Episode Oscilloscopes are becoming more powerful, accessible, and common in repair shops—but choosing the right scope is only part of the equation. You also need to understand how your particular scope captures, stores, and displays its data. Matt Fanslow answers listener questions about automotive oscilloscopes, including the new eight-channel PicoScope, how many channels a shop actually needs, and whether beginners should start with an inexpensive scope or jump directly into a more capable platform. He also explains the distinctly different way Snap-on scopes handle their sample buffer, and why misunderstanding that behavior can cause a technician to lose the exact event they were trying to capture. Topics discussed include: What we currently know about Pico’s new eight-channel automotive scope How Pico BNC+ powers and automatically identifies compatible probes and transducers Why current probes, pressure sensors, and microphones are all transducers Where a single-channel AESwave uScope remains extremely useful Why two channels are helpful but a four-channel scope should now be considered a shop necessity When five, six, or eight channels become valuable Using crankshaft, camshaft, ignition, and other signals together Why the Snap-on Vantage Pro remains an excellent and affordable starting point Whether a PicoScope is really too advanced for a first-time scope user How modern scope hardware can compensate for less-than-perfect setup choices Why capable modern scopes resemble modern supercars: approachable in ordinary use, with substantial performance available when needed Why oscilloscopes of this caliber should generally be considered shop equipment How Snap-on scope screens differ from the displays used by many other scopes Understanding the Snap-on screen as a window into a continuously moving buffer Why Snap-on scopes allow technicians to zoom out after a capture—but not zoom in Setting the time base correctly when looking for details such as injector pintle movement How a captured event can disappear from the buffer even though the display appears frozen When to save a screenshot instead of relying only on the scope-data file The difference between Snap-on’s Graphing Meter and Lab Scope modes Common setup mistakes made by Snap-on scope users The practical limitations of older Snap-on sample rates and memory configurations How descriptive filenames make saved waveforms far easier to find years later What vehicle, engine, system, signal, and operating-condition information should accompany a saved waveform?