CARGA - teoría (Ric)

Main ideas / lessons (what the video teaches)

• USB charging standards (USB-IF) are the foundation of how charging works.

  • Charging behavior is governed by documentation/standards, not arbitrary engineering.
  • To diagnose or repair charging problems, you must understand:
    1. electronics fundamentals, and
    2. official USB/charging documentation (voltages, currents, pin functions, and protocols).

• Charging system mastery is built from “layers.”

  • Physical layer: which USB port exists (Type A/B/C; on phones mainly Micro-USB vs USB-C), connector/pins, and hardware variations.
  • Protocol/logic layer: what standard is negotiated (standard charging vs fast charging; SDP/CDP/DCP; BC vs Power Delivery).
  • Power conversion layer: the adapter converts AC to regulated DC (e.g., 5V VBUS externally, then onboard charging IC regulates to ~3.8–4.2V battery targets).
  • Safety/monitoring layer: protections like OVP (over-voltage protection), and monitoring like fuel gauge.
  • Control/communication layer: negotiation and supervision using lines such as data, CC, and internal interfaces (often I²C).

• USB ports and versions matter.

  • The video lists USB types (A, B, C) and smartphone-relevant subtypes (micro USB, mini USB, etc.).
  • It stresses that USB “versions” (e.g., 2.0/3.0/3.1) can be physically similar but may differ internally (hardware + software capabilities).

• Adapters regulate AC → DC and include circuitry beyond “just voltage reduction.”

  • The adapter’s job includes:
    • transforming and rectifying (AC→DC),
    • filtering,
    • switching regulation,
    • producing VBUS (commonly 5V for standard),
    • and containing charging management/load-management circuitry.

• Charging protocol types (standard vs fast)

  • Standard charging
    • Described via USB Battery Charging concepts (BC) and phone-port subtypes:
    • SDP / CDP / DCP correspond to different allowed voltage/current behaviors.
  • Fast charging
    • For USB standards: Power Delivery (PD).
    • PD is more than “higher voltage”—it requires extra negotiation lines (CC lines on USB-C: CC1/CC2).
    • It also mentions manufacturer-specific protocols (e.g., Qualcomm Quick Charge, Samsung AFC, Huawei SuperCharge, Motorola TurboPower), which may not rely on PD’s CC mechanism in the same way.

---

Methodology / diagnostic approach implied by the video

Step-by-step conceptual “warm-up” for diagnosing charging (as taught)

1. Start from the standards/documentation

   • Look up what USB-IF defines for the charging method: standard charging vs fast charging (Power Delivery).

2. Confirm the hardware basics

   • Identify whether the port is Micro-USB or USB-C.
   • Identify relevant connector/pin layout:
     • VBUS and GND,
     • data lines (D+ / D−),
     • USB-C CC lines (CC1 / CC2).

3. Understand the adapter output and internal behavior

   • The adapter must convert AC to stable VBUS (typical 5V) and include internal regulation.
   • Fault concept: if adapter regulation fails, it can over/under-supply and damage the phone battery path.

4. Trace the phone-side protection path

   • The video repeatedly returns to OVP as an early checkpoint:
     • If VBUS is too high, OVP should block it before the charging IC.

5. Trace negotiation for fast charging

   • For PD fast charging over USB-C:
     • The phone must detect a fast-charging-capable adapter via CC pull-up / pull-down logic.
     • There is an initial detection “pulse”/voltage that allows the phone’s PD controller to negotiate higher voltages (e.g., 9V, 12V, 20V…).
   • If detection never happens (fault in CC/adapter/cable logic), the phone defaults to standard charging.

6. Use measurement logic specific to signals

   • Data lines are high-frequency and can be corrupted by interference.
   • CC lines are part of negotiation and must show proper voltage behavior.
   • VBUS may appear “correct” on a multimeter even when it has switching spikes—use an oscilloscope for waveform truth.

7. Consider cable type

   • Passive vs active cables:
     • Passive cable: mostly just copper conductors.
     • Active cable: includes an internal chip (“Maker”), which requires power/data and can affect PD/CC/data negotiation.
   • Fault concept: using a passive cable that lacks required internal behavior can prevent fast charging.

8. Validate current monitoring and battery protection

   • Fuel gauge / FG measures charging current by using voltage drop across a shunt resistor.
   • If FG/shunt is wrong (resistance drift, sulfation, damage), the phone may throttle/stop charging or behave erratically.

9. Cross-check with real schematics/board diagrams

   • The video uses a Samsung A13 example to map conceptual blocks to real circuits.

---

Detailed concepts and “how it works” (organized)

A) Physical USB basics (what connects to what)

• Phone side connector hardware

  • Micro-USB: non-reversible, fewer pins.
  • USB-C: reversible, more pins (the video uses a conceptual count of 12 top + 12 bottom).

• Pin roles on charging path

  • VBUS: provides power to the phone charging IC.
  • GND: common reference/return.
  • Data lines (D+/D−): used for negotiation in standard charging and for data exchange.
  • CC1 / CC2 (USB-C only):
    • Used for Power Delivery / USB-C negotiation and detection of adapter capability.
    • Only one CC line is active at a time depending on cable orientation.

---

B) Why fast charging is not just “more amps”

• Standard charging example: ~5V and up to ~2A → more heat/loss in cables.
• Fast charging (PD):
  • increases VBUS to higher voltages and reduces current to keep delivered power similar while reducing I²R losses in the cable.
• Core taught principle:
  • power loss in cables scales with current squared: loss ∝ I² · R.
• Result:
  • Less loss → more power reaches the phone → faster charging.

---

C) PD negotiation sequence (as described)

• When USB-C fast charging is attempted:
  • Adapter and phone communicate via CC lines.
  • Phone requests a voltage (e.g., 9V) within the adapter’s capabilities.
  • After negotiation, the adapter raises VBUS from 5V to the agreed PD voltage.
• Key diagnostic idea:
  • If CC detection fails, the system never enters PD mode → it stays in standard charging.

---

D) Safety and protection: OVP + measurement logic

• OVP (Over-Voltage Protection):

  • Implemented using a divisor + regulator + comparator concept.
  • It only lets voltage through if the compared value is within allowed bounds.

• Beyond “UV/OV” (Ublo/Oblo idea)

  • Some protection behavior uses minimum/maximum thresholds:
    • Ublo: lower threshold behavior.
    • Oblo: upper threshold behavior.
  • If protections or divider resistances drift/fail:
    • OVP can either block when it shouldn’t or let harmful voltages through.

---

E) Charging IC operation (simplified, as explained)

• The phone’s integrated charging stage uses internal switching elements:

  • MOSFET switching + a control mechanism (video describes a conceptually simplified “Fed type transistor” / MOSFET gating).

• Switching + capacitor role

  • Switching is controlled so the effective battery charging voltage is regulated (e.g., ~4V).
  • Multimeter vs oscilloscope:
    • multimeter sees average/effective voltage,
    • oscilloscope can show fast peaks.

---

F) Current measurement: Fuel gauge and shunt resistor

• Fuel gauge (FG) monitors current by measuring:

  • voltage drop across a shunt resistor (very low resistance, so drop is small),
  • then applying Ohm’s law conceptually to estimate current.

• FG reports to:

  • the charging controller and/or application processor,
  • which adjusts charging current/voltage or stops charging if abnormal.

---

Speakers / sources featured

• Speaker (main): Ricardo (referred to as “Ricardo” throughout)
• Named person(s) referenced (not necessarily speaking):
  • “Oto” (course host/partner mentioned as teaching/handling practice components and diagnostics)
  • Qualcomm (referenced via Quick Charge)
  • USB-IF / USB Implementers Forum (source of standards)
• External organization mentioned: USB-IF (non-profit standards body)