惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

J
Java Code Geeks
Google DeepMind News
Google DeepMind News
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
小众软件
小众软件
Blog — PlanetScale
Blog — PlanetScale
腾讯CDC
A
About on SuperTechFans
Vercel News
Vercel News
I
InfoQ
阮一峰的网络日志
阮一峰的网络日志
月光博客
月光博客
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
人人都是产品经理
人人都是产品经理
S
SegmentFault 最新的问题
V
Visual Studio Blog
T
Tailwind CSS Blog
大猫的无限游戏
大猫的无限游戏
M
MIT News - Artificial intelligence
博客园 - 【当耐特】
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
Microsoft Azure Blog
Microsoft Azure Blog
Apple Machine Learning Research
Apple Machine Learning Research
GbyAI
GbyAI
美团技术团队

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
Advanced Component-Level Diagnostics: Pinpointing Trace a...
Apex · 2026-06-26 · via DEV Community

Apex

Introduction: The Challenge of Liquid Damage

Liquid damage to electronic components, especially sensitive logic board designs like those found in a Nintendo Switch Lite motherboard, presents one of the most complex diagnostic challenges in hardware repair. Unlike simple component failures, liquid intrusion introduces unpredictable shorts, corrosion, and latent electrical faults that manifest intermittently or only under specific load conditions. This guide provides a masterclass approach to systematically diagnose, isolate, and repair these complex failures.

Phase 1: Initial Assessment and Safety Protocol

Before any physical work begins, the paramount concern is safety and preventing further damage.

Safety First

• Power Down: Ensure the device is completely powered off and disconnected from any power source before inspecting or probing components.
• Static Discharge: Always work on a grounded, anti-static mat. Grounding is non-negotiable when dealing with potential shorts introduced by moisture.
• Visual Inspection: Examine the board under high magnification (at least 10x) for visible signs of corrosion (white/green residue), delamination, or physical damage to solder points, trace lines, and component casings.

Initial System Check

Start with non-invasive checks: check fuses, test basic power rail continuity, and inspect the area immediately surrounding the suspected water entry point.

Phase 2: Component-Level Diagnostics – Voltage Line Mapping

Liquid damage often targets critical voltage rails, leading to catastrophic failures. The following table outlines key areas to inspect for shorts, corrosion, or open circuits. Note: Specific traces depend heavily on the exact PCB revision and location of the leak.

Power Rail / Component Expected Voltage (V) Critical Check Points Common Liquid Damage Symptom Cleaning Protocol
VCORE/VBUS (CPU/GPU) 1.0V - 1.8V VCC pins, surrounding MOSFETs Shorted lines, component burnouts IPA wipe, flux application
VCC_MAIN (Main Power) 3.3V - 5.0V Input capacitors, regulator ICs Corrosion on traces, IC damage Gentle cleaning, flux
VCC_IO (I/O Power) 1.8V - 3.3V USB controller lines, peripheral chips Pin corrosion, trace bridging Focus on solder points
Ground Planes (GND) 0V Reference Entire plane integrity Bridging of adjacent traces High-purity solvent wipe
Peripheral ICs Varies Microcontroller pins, memory chips Internal chip damage due to short Visual inspection under scope

Phase 3: Trace Path Tracing and Fault Isolation

When voltage readings are erratic or a component is clearly damaged (e.g., a MOSFET is melted), you must trace the path of the fault.

  1. Identify the Point of Failure: Locate the physical symptom (e.g., no power, intermittent behavior).
  2. Trace Backwards from the Symptom: Trace the electrical path backwards from the failure point to identify the immediate preceding component or trace that is compromised.
  3. Map the Fault Path: Use a multimeter in continuity mode to check for shorts between adjacent traces (e.g., VCC and GND). For complex, multi-layer PCBs, focus on testing known good reference points and tracing high-current paths.
  4. Differential Testing: If possible, test differential pairs (like those used for high-speed data lines) to see if the short affects both sides symmetrically.

Phase 4: Decontamination and Restoration
Complete the restoration by thoroughly cleaning the affected zones with 99% Isopropyl Alcohol (IPA) using an ultrasonic cleaner or a soft ESD-safe brush. Reflow any oxidized solder joints using high-quality flux, and verify all core power rails are clear of shorts before reconnecting the battery wrapper line.