<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: probeo</title>
    <description>The latest articles on DEV Community by probeo (@probeo).</description>
    <link>https://dev.to/probeo</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4181837%2F69f69bd4-7300-49de-8480-f0a3f2593419.png</url>
      <title>DEV Community: probeo</title>
      <link>https://dev.to/probeo</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/probeo"/>
    <language>en</language>
    <item>
      <title>What I check when a trace looks wrong on my handheld scope</title>
      <dc:creator>probeo</dc:creator>
      <pubDate>Tue, 13 Oct 2026 09:54:14 +0000</pubDate>
      <link>https://dev.to/probeo/how-i-use-a-10-mhz-handheld-oscilloscope-for-quick-checks-23bd</link>
      <guid>https://dev.to/probeo/how-i-use-a-10-mhz-handheld-oscilloscope-for-quick-checks-23bd</guid>
      <description>&lt;p&gt;My handheld oscilloscope is a quick-check tool, and most of the time it does exactly that. When the screen shows something odd, though, I want to know whether the fault is in the circuit, in my setup, or simply beyond what the instrument can show. These notes are how I sort that out, plus how I look after it.&lt;/p&gt;

&lt;h2&gt;
  
  
  First checks on a strange trace
&lt;/h2&gt;

&lt;p&gt;I run through these in order before I trust anything on the display:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;The ground clip is on the circuit's ground. Without it, the trace tells me very little.&lt;/li&gt;
&lt;li&gt;The BNC probe or the alligator-clip lead is in the right-hand input.&lt;/li&gt;
&lt;li&gt;I press AUTO again so the scope rescales the waveform.&lt;/li&gt;
&lt;li&gt;If AUTO lands on an awkward scale, I use the direction keys to set timebase and volts per division myself.&lt;/li&gt;
&lt;li&gt;The battery still has charge. It's a built-in 3.7 V 1200 mAh cell, and a top-up over USB Type-C takes care of that.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Is the signal inside its limits?
&lt;/h2&gt;

&lt;p&gt;This is the question that saves me the most time. The BSIDE OT3 has 10 MHz bandwidth, samples at 48 MSa/s and has one analogue channel. If a fast digital signal looks soft or rounded, the scope may simply be out of its depth, so I don't read anything into that shape. Slower work suits it: PWM, injectors, and crank or cam sensors on a car.&lt;/p&gt;

&lt;p&gt;It isn't a 50 or 100 MHz bench instrument. When a job needs two signals compared at once, I accept straight away that it's the wrong tool rather than trying to juggle the probe between points.&lt;/p&gt;

&lt;h2&gt;
  
  
  When saving or menus go wrong
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;No image saved: the start/pause key has to be held, not tapped.&lt;/li&gt;
&lt;li&gt;Images not coming across: they export over USB Type-C, so I check the cable is seated in that port.&lt;/li&gt;
&lt;li&gt;Firmware: updates go through the same port, and I keep the scope charged while doing one.&lt;/li&gt;
&lt;li&gt;Menus in the wrong language: the on-screen menus come in Chinese and English, and I switch back to English.&lt;/li&gt;
&lt;li&gt;Anything I'm unsure of: the oscilloscope manual from the box lives with the scope.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Care and storage
&lt;/h2&gt;

&lt;p&gt;The 3.2" TFT screen is the part I'm most careful with, so the scope never goes in a bag loose among tools. After a session I long-press the power key to switch it off, put it on charge so it isn't left flat, and coil the probe and clip lead beside it. One cable handles charging, screenshots and firmware, which keeps the kit small.&lt;/p&gt;

&lt;p&gt;The handheld I keep these notes for is described on &lt;a href="https://probeo.co.uk/" rel="noopener noreferrer"&gt;probeo.co.uk&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>hardware</category>
      <category>testing</category>
      <category>tools</category>
    </item>
  </channel>
</rss>
