๐ Meter & scope: the 20% that solves 80%
-
Two instruments solve the overwhelming majority of hardware mysteries. You don't need a lab โ a basic multimeter and the cheapest scope (or logic analyser) you can borrow will do. Here's the 20% worth learning first.
Multimeter: measure, don't guess
- Continuity beep finds broken wires, cold solder joints, and short circuits. Power off first โ beeping a live circuit lies to you and risks the meter.
- DC volts on the rail, under load. A 3.3V rail that reads 3.28V idle and 2.9V when WiFi transmits is your random-reset culprit. Always measure while the device is doing the thing that fails.
- Current in series. Break the supply line and put the meter in the middle (correct jack, correct range, start high). Compare against expectations: tens of mA sleeping, hundreds transmitting. Way off in either direction is a clue.
- Resistance unpowered. Verify pull-ups are actually pulling, dividers divide, and nothing is shorted to ground. Never measure resistance on a powered board.
Scope: see the signal in time
- Probe on ร10, compensated, ground clip short. A long ground lead turns every fast edge into ringing that isn't really there. Compensate the probe on the scope's test output once, then trust what you see.
- Trigger deliberately. Free-running waveforms are soup. Trigger on the edge you care about โ the UART start bit, the PWM rising edge, the droop when the motor kicks โ and the picture stabilises.
- UART debugging: set the timebase to see individual bits, measure one bit width, invert to get the baud (1 รท width). If transmit and receive disagree by even a few percent at high baud, you get framing garbage.
- PWM check: duty cycle and frequency straight off the scope, in seconds. "The motor hums but doesn't turn" is usually 0% or 100% duty, or a frequency the driver can't follow.
What to capture when asking for help
One screenshot per mystery: the rail during the failure (is it power?), the signal in question with trigger point and timebase visible, and the meter reading that surprised you. A scope shot with no volts/div or timebase shown helps nobody โ include the settings.
Post your captures with settings visible. Tag with oscilloscope, multimeter or debugging.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better ๐
Register Login