How to Use a Multimeter to Test an FPV Drone

Updated

To test an FPV drone with a multimeter, you mainly need three modes: continuity (beep) to check for shorts and broken connections, DC voltage to confirm power is reaching the right places, and resistance to trace faults when continuity alone isn't clear. The workflow that matters most is checking for shorts before you plug in a battery, then verifying voltage after. Oscar Liang's tutorial on this calls a multimeter "one of the first tools you should get when getting into FPV," and frames it as a roughly $10 investment — cheap relative to the parts it protects.

This guide covers what each mode does, the specific test points on a typical quad, and the mistakes that turn a quick check into a fried flight controller.

The three modes you actually use

Mode Symbol What it tells you When to use it
Continuity Diode/speaker icon Whether two points are electrically connected Short checks, broken wires, solder joints
DC voltage V with a straight line The voltage difference between two points After power-up: battery, BEC rails, receiver
Resistance Ω Exact resistance between two points Tracing partial faults, checking motors

You will not need AC voltage, current (A), or capacitance for routine FPV checks. If your meter has an auto-range function, use it; if not, start on the highest range and step down.

Before you power anything: the short check

This is the single most valuable habit. A short between battery positive and negative will destroy components the instant you connect a battery — and it is invisible to the eye.

  1. Set the meter to continuity mode.
  2. Touch the probes together to confirm it beeps (this verifies the meter and leads work).
  3. On the drone, with no battery connected, place one probe on the main positive pad (or battery connector positive pin) and the other on the main negative pad.
  4. Expected result: no beep, or a very high resistance reading. A continuous beep means a short — find it before going further.

Repeat the same check across the positive and negative rails of your ESC, and across any 5V or 9V BEC output pads if you can reach them.

If it beeps

Do not connect a battery. Common causes:

  • Solder bridge between adjacent pads (look under magnification)
  • A wire strand shorting across two pads
  • A damaged component or a connector inserted backwards
  • Conductive debris or excess flux bridging a gap

Clean the area, re-inspect, and re-test. Only proceed when the beep is gone.

After power-up: voltage checks

Once the short check passes, connect a battery (props off, ideally on a bench with nothing flammable nearby) and switch to DC voltage.

Battery input: probe the main positive and negative pads. You should read close to the battery's nominal charged voltage — a fully charged 6S LiPo reads about 25.2V, a 4S about 16.8V. A reading far below that points to a bad connector, a damaged cell, or high resistance in the wiring.

Regulated rails: most flight controllers and VTXs run on 5V, and some on 9V or 12V. Probe the relevant pad against ground. If a 5V rail reads 3V or fluctuates, the regulator is failing or being overloaded — a common cause of receivers dropping out mid-flight.

Receiver and GPS: confirm they see the voltage they expect. A receiver rated for 5V fed 9V is a dead receiver.

Continuity checks on the bench

With the battery disconnected, continuity mode answers "is this connection intact?":

  • Motor wires to ESC: each motor phase should show continuity from the motor pad to the ESC output. No beep means a broken joint or a broken wire inside the insulation.
  • Signal wires: check that a signal pad connects to the correct pin on the connector or FC pad. This catches swapped or misrouted wires before they cause a confusing bench test.
  • Grounds: all grounds should be common. If two ground points don't show continuity, you have a floating ground, which causes erratic behaviour.

Note that continuity mode on some meters also reads through components, so a beep doesn't always mean a direct wire — it can mean a path through a resistor or diode. When in doubt, switch to resistance and compare the value against what you expect.

Common mistakes and how to avoid them

  • Probing a live circuit in continuity or resistance mode. You can get false readings and, on some meters, damage the meter. Always disconnect power for these modes.
  • Forgetting to zero the leads. Touch the probes together first. A meter with damaged leads may never beep, giving you a false "no short" result.
  • Assuming no beep means no short. A short through a high-resistance path may not trigger the beeper. Use resistance mode to check the actual value.
  • Testing with props on. Never. A motor that spins unexpectedly during a voltage check is a serious injury risk.
  • Chasing a fault with the battery connected. Most diagnosis happens unpowered. Power up only to confirm a fix, not to hunt for it.

A practical order of operations

  1. Visual inspection and cleaning.
  2. Continuity check across main power rails — no battery.
  3. Continuity check on motor phases and signal wires — no battery.
  4. Connect battery, props off.
  5. DC voltage check on battery input, then each regulated rail.
  6. Disconnect, fix anything out of spec, repeat from step 2.

This sequence catches the failures that cost the most money (shorts, reversed polarity) before they can do damage, and it uses only the modes a basic meter provides. Oscar Liang's framing is worth repeating: the tool is inexpensive, but the habit of checking before powering is what actually protects your build.