<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[📟 Meter & scope: the 20% that solves 80%]]></title><description><![CDATA[<p dir="auto">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.</p>
<h3>Multimeter: measure, don't guess</h3>
<ul>
<li><strong>Continuity beep</strong> finds broken wires, cold solder joints, and short circuits. Power off first — beeping a live circuit lies to you and risks the meter.</li>
<li><strong>DC volts on the rail, under load.</strong> 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.</li>
<li><strong>Current in series.</strong> 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.</li>
<li><strong>Resistance unpowered.</strong> Verify pull-ups are actually pulling, dividers divide, and nothing is shorted to ground. Never measure resistance on a powered board.</li>
</ul>
<h3>Scope: see the signal in time</h3>
<ul>
<li><strong>Probe on ×10, compensated, ground clip short.</strong> 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.</li>
<li><strong>Trigger deliberately.</strong> 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.</li>
<li><strong>UART debugging:</strong> 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.</li>
<li><strong>PWM check:</strong> 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.</li>
</ul>
<h3>What to capture when asking for help</h3>
<p dir="auto">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.</p>
<p dir="auto"><em>Post your captures with settings visible. Tag with oscilloscope, multimeter or debugging.</em></p>
]]></description><link>https://forum.grapesiot.com/topic/84/meter-scope-the-20-that-solves-80</link><generator>RSS for Node</generator><lastBuildDate>Thu, 19 Nov 2026 13:02:49 GMT</lastBuildDate><atom:link href="https://forum.grapesiot.com/topic/84.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 03 Oct 2026 11:40:25 GMT</pubDate><ttl>60</ttl></channel></rss>