Cheap oscilloscope showing 16 MHz square waveCheap 1MHz oscilloscopeOscilloscope trace not quite squareWhat can be the reason that oscilloscope is showing voltages 10 times more than expected?Why would a 150 MHz probe work fine for a 100 MHz oscilloscope?Bouncing at some points in square waveOscilloscope displaying two voltage levels (on the same channel) for square wave

“all of who” or “all of whom”?

In Endgame, wouldn't Stark have remembered Hulk busting out of the stairwell?

Are sweatpants frowned upon on flights?

Can authors email you PDFs of their textbook for free?

Don't look at what I did there

Strange behavior of std::initializer_list of std::strings

When is it a good idea to capture the fianchettoed bishop?

Is Borg adaptation only temporary?

Printing a list as "a, b, c." using Python

Simply connected compact Lie groups have even dimension - Where is the mistake?

Where could I find a math pen pal?

Does the telecom provider need physical access to the SIM card to clone it?

Can I leave a large suitcase at TPE during a 4-hour layover, and pick it up 4.5 days later when I come back to TPE on my way to Taipei downtown?

Why do IR remotes influence AM radios?

Eshet Chayil in the Tunisian service

Eliminate key lookup in execution plan

What was Captain Marvel supposed to do once she reached her destination?

Moscow SVO airport, how to avoid scam taxis without pre-booking?

Is the word 'mistake' a concrete or abstract noun?

Was a six-engine 747 ever seriously considered by Boeing?

Small RAM 4 KB on the early Apple II?

Is it possible for a person to be tricked into becoming a lich?

An ant walks on a cube over the diagonals of little cubes. Can it visit all little faces exactly once?

Why does the U.S. military maintain their own weather satellites?



Cheap oscilloscope showing 16 MHz square wave


Cheap 1MHz oscilloscopeOscilloscope trace not quite squareWhat can be the reason that oscilloscope is showing voltages 10 times more than expected?Why would a 150 MHz probe work fine for a 100 MHz oscilloscope?Bouncing at some points in square waveOscilloscope displaying two voltage levels (on the same channel) for square wave






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








2












$begingroup$


I own a cheap oscilloscope Hantek DSO4102C. It's rated bandwidth is 100 MHz, and sample rate is 1 GSa/s. Some info about the tool can be found here: http://hantek.com/en/ProductDetail_3_4163.html

Now I have an Atmega328P MCU running from an external quartz at 16 MHz, without any code it it (chip erased by usbasp), only CKOUT fuse bit is set. So I supposed to see a square wave at PB0 pin, but my scope shows it quite distorted:

MCU's datasheet doesn't mention a pin rise time, which was a big surprise to me, so I cannot check if measured 9.5 ns is a valid value. But judging by Pk-Pk voltage exceeding 6 volts (and even going below zero for a good 560 mV), I believe there's a problem with the scope. Am I right?










share|improve this question









$endgroup$













  • $begingroup$
    Are your probes compensated correctly? Also, can you try with a different probe?
    $endgroup$
    – Steve G
    7 hours ago










  • $begingroup$
    Could you add a photo of how you're probing the signal? That is, how exactly your probe is connected to the circuit.
    $endgroup$
    – marcelm
    5 hours ago










  • $begingroup$
    Make sure your probe is in the x10 position, compensation adjustment is done and the ground lead is connected to a plane very close to the MCU ground. You can also run probe wizard and self cal routines.
    $endgroup$
    – Spehro Pefhany
    5 hours ago


















2












$begingroup$


I own a cheap oscilloscope Hantek DSO4102C. It's rated bandwidth is 100 MHz, and sample rate is 1 GSa/s. Some info about the tool can be found here: http://hantek.com/en/ProductDetail_3_4163.html

Now I have an Atmega328P MCU running from an external quartz at 16 MHz, without any code it it (chip erased by usbasp), only CKOUT fuse bit is set. So I supposed to see a square wave at PB0 pin, but my scope shows it quite distorted:

MCU's datasheet doesn't mention a pin rise time, which was a big surprise to me, so I cannot check if measured 9.5 ns is a valid value. But judging by Pk-Pk voltage exceeding 6 volts (and even going below zero for a good 560 mV), I believe there's a problem with the scope. Am I right?










share|improve this question









$endgroup$













  • $begingroup$
    Are your probes compensated correctly? Also, can you try with a different probe?
    $endgroup$
    – Steve G
    7 hours ago










  • $begingroup$
    Could you add a photo of how you're probing the signal? That is, how exactly your probe is connected to the circuit.
    $endgroup$
    – marcelm
    5 hours ago










  • $begingroup$
    Make sure your probe is in the x10 position, compensation adjustment is done and the ground lead is connected to a plane very close to the MCU ground. You can also run probe wizard and self cal routines.
    $endgroup$
    – Spehro Pefhany
    5 hours ago














2












2








2





$begingroup$


I own a cheap oscilloscope Hantek DSO4102C. It's rated bandwidth is 100 MHz, and sample rate is 1 GSa/s. Some info about the tool can be found here: http://hantek.com/en/ProductDetail_3_4163.html

Now I have an Atmega328P MCU running from an external quartz at 16 MHz, without any code it it (chip erased by usbasp), only CKOUT fuse bit is set. So I supposed to see a square wave at PB0 pin, but my scope shows it quite distorted:

MCU's datasheet doesn't mention a pin rise time, which was a big surprise to me, so I cannot check if measured 9.5 ns is a valid value. But judging by Pk-Pk voltage exceeding 6 volts (and even going below zero for a good 560 mV), I believe there's a problem with the scope. Am I right?










share|improve this question









$endgroup$




I own a cheap oscilloscope Hantek DSO4102C. It's rated bandwidth is 100 MHz, and sample rate is 1 GSa/s. Some info about the tool can be found here: http://hantek.com/en/ProductDetail_3_4163.html

Now I have an Atmega328P MCU running from an external quartz at 16 MHz, without any code it it (chip erased by usbasp), only CKOUT fuse bit is set. So I supposed to see a square wave at PB0 pin, but my scope shows it quite distorted:

MCU's datasheet doesn't mention a pin rise time, which was a big surprise to me, so I cannot check if measured 9.5 ns is a valid value. But judging by Pk-Pk voltage exceeding 6 volts (and even going below zero for a good 560 mV), I believe there's a problem with the scope. Am I right?







oscilloscope






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked 8 hours ago









ZhenekZhenek

596 bronze badges




596 bronze badges














  • $begingroup$
    Are your probes compensated correctly? Also, can you try with a different probe?
    $endgroup$
    – Steve G
    7 hours ago










  • $begingroup$
    Could you add a photo of how you're probing the signal? That is, how exactly your probe is connected to the circuit.
    $endgroup$
    – marcelm
    5 hours ago










  • $begingroup$
    Make sure your probe is in the x10 position, compensation adjustment is done and the ground lead is connected to a plane very close to the MCU ground. You can also run probe wizard and self cal routines.
    $endgroup$
    – Spehro Pefhany
    5 hours ago

















  • $begingroup$
    Are your probes compensated correctly? Also, can you try with a different probe?
    $endgroup$
    – Steve G
    7 hours ago










  • $begingroup$
    Could you add a photo of how you're probing the signal? That is, how exactly your probe is connected to the circuit.
    $endgroup$
    – marcelm
    5 hours ago










  • $begingroup$
    Make sure your probe is in the x10 position, compensation adjustment is done and the ground lead is connected to a plane very close to the MCU ground. You can also run probe wizard and self cal routines.
    $endgroup$
    – Spehro Pefhany
    5 hours ago
















$begingroup$
Are your probes compensated correctly? Also, can you try with a different probe?
$endgroup$
– Steve G
7 hours ago




$begingroup$
Are your probes compensated correctly? Also, can you try with a different probe?
$endgroup$
– Steve G
7 hours ago












$begingroup$
Could you add a photo of how you're probing the signal? That is, how exactly your probe is connected to the circuit.
$endgroup$
– marcelm
5 hours ago




$begingroup$
Could you add a photo of how you're probing the signal? That is, how exactly your probe is connected to the circuit.
$endgroup$
– marcelm
5 hours ago












$begingroup$
Make sure your probe is in the x10 position, compensation adjustment is done and the ground lead is connected to a plane very close to the MCU ground. You can also run probe wizard and self cal routines.
$endgroup$
– Spehro Pefhany
5 hours ago





$begingroup$
Make sure your probe is in the x10 position, compensation adjustment is done and the ground lead is connected to a plane very close to the MCU ground. You can also run probe wizard and self cal routines.
$endgroup$
– Spehro Pefhany
5 hours ago











2 Answers
2






active

oldest

votes


















10













$begingroup$


I believe there's a problem with the scope. Am I right?




Don't think so. Overshoot is a perfectly normal phenomenon when measuring a fast-edge signal with a high-impedance probe. (Also, these signals look about as sharp as I'd expect them to be.)



There's many tutorials on sensing high-speed signals: this is the perfect time to read one!



Oh, and there's Gibb's phenomenon, which says that any band-limited observation of a theoretical perfect (or far less band-limited) edge will have some 9% of overshoot; to understand that, I'd recommend looking at the cosine series representation of the square wave and consider what you'll cut off when you get rid of anything above 5× 16 MHz (=the fundamental frequency of your square wave).






share|improve this answer











$endgroup$










  • 1




    $begingroup$
    On OP's measure function: I'd believe 16.00MHz frequency (these 'scopes use a crystal time-base). But 9.500 ns risetime? That's suspect, especially with 1ps resolution? And 6.16V Pk-Pk often goes through the entire sample record to find the maximum extent...(I make out about 5.2V, after settling). So Marcus' verdict is reasonable - more careful probing likely gives different results - learn to trust some measure functions, dis-trust others.
    $endgroup$
    – glen_geek
    7 hours ago


















1













$begingroup$

Keep in mind that if you have a 100MHz brick-wall filter (ideal case) with a perfect 16MHz square wave in, the only harmonics you'll see are 1 (16MHz), 3 (48MHz) and 5 (80MHz). That's an ideal case, but if you do the calculations, you'll see the result isn't too far from what you're seeing.



In the nonideal case, of course, probe loading and compensation will have further distorting effects, and the waveform isn't going to be perfectly square to start with.






share|improve this answer









$endgroup$

















    Your Answer






    StackExchange.ifUsing("editor", function ()
    return StackExchange.using("schematics", function ()
    StackExchange.schematics.init();
    );
    , "cicuitlab");

    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "135"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader:
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    ,
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













    draft saved

    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2felectronics.stackexchange.com%2fquestions%2f455356%2fcheap-oscilloscope-showing-16-mhz-square-wave%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    10













    $begingroup$


    I believe there's a problem with the scope. Am I right?




    Don't think so. Overshoot is a perfectly normal phenomenon when measuring a fast-edge signal with a high-impedance probe. (Also, these signals look about as sharp as I'd expect them to be.)



    There's many tutorials on sensing high-speed signals: this is the perfect time to read one!



    Oh, and there's Gibb's phenomenon, which says that any band-limited observation of a theoretical perfect (or far less band-limited) edge will have some 9% of overshoot; to understand that, I'd recommend looking at the cosine series representation of the square wave and consider what you'll cut off when you get rid of anything above 5× 16 MHz (=the fundamental frequency of your square wave).






    share|improve this answer











    $endgroup$










    • 1




      $begingroup$
      On OP's measure function: I'd believe 16.00MHz frequency (these 'scopes use a crystal time-base). But 9.500 ns risetime? That's suspect, especially with 1ps resolution? And 6.16V Pk-Pk often goes through the entire sample record to find the maximum extent...(I make out about 5.2V, after settling). So Marcus' verdict is reasonable - more careful probing likely gives different results - learn to trust some measure functions, dis-trust others.
      $endgroup$
      – glen_geek
      7 hours ago















    10













    $begingroup$


    I believe there's a problem with the scope. Am I right?




    Don't think so. Overshoot is a perfectly normal phenomenon when measuring a fast-edge signal with a high-impedance probe. (Also, these signals look about as sharp as I'd expect them to be.)



    There's many tutorials on sensing high-speed signals: this is the perfect time to read one!



    Oh, and there's Gibb's phenomenon, which says that any band-limited observation of a theoretical perfect (or far less band-limited) edge will have some 9% of overshoot; to understand that, I'd recommend looking at the cosine series representation of the square wave and consider what you'll cut off when you get rid of anything above 5× 16 MHz (=the fundamental frequency of your square wave).






    share|improve this answer











    $endgroup$










    • 1




      $begingroup$
      On OP's measure function: I'd believe 16.00MHz frequency (these 'scopes use a crystal time-base). But 9.500 ns risetime? That's suspect, especially with 1ps resolution? And 6.16V Pk-Pk often goes through the entire sample record to find the maximum extent...(I make out about 5.2V, after settling). So Marcus' verdict is reasonable - more careful probing likely gives different results - learn to trust some measure functions, dis-trust others.
      $endgroup$
      – glen_geek
      7 hours ago













    10














    10










    10







    $begingroup$


    I believe there's a problem with the scope. Am I right?




    Don't think so. Overshoot is a perfectly normal phenomenon when measuring a fast-edge signal with a high-impedance probe. (Also, these signals look about as sharp as I'd expect them to be.)



    There's many tutorials on sensing high-speed signals: this is the perfect time to read one!



    Oh, and there's Gibb's phenomenon, which says that any band-limited observation of a theoretical perfect (or far less band-limited) edge will have some 9% of overshoot; to understand that, I'd recommend looking at the cosine series representation of the square wave and consider what you'll cut off when you get rid of anything above 5× 16 MHz (=the fundamental frequency of your square wave).






    share|improve this answer











    $endgroup$




    I believe there's a problem with the scope. Am I right?




    Don't think so. Overshoot is a perfectly normal phenomenon when measuring a fast-edge signal with a high-impedance probe. (Also, these signals look about as sharp as I'd expect them to be.)



    There's many tutorials on sensing high-speed signals: this is the perfect time to read one!



    Oh, and there's Gibb's phenomenon, which says that any band-limited observation of a theoretical perfect (or far less band-limited) edge will have some 9% of overshoot; to understand that, I'd recommend looking at the cosine series representation of the square wave and consider what you'll cut off when you get rid of anything above 5× 16 MHz (=the fundamental frequency of your square wave).







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited 3 hours ago

























    answered 8 hours ago









    Marcus MüllerMarcus Müller

    40.4k3 gold badges66 silver badges110 bronze badges




    40.4k3 gold badges66 silver badges110 bronze badges










    • 1




      $begingroup$
      On OP's measure function: I'd believe 16.00MHz frequency (these 'scopes use a crystal time-base). But 9.500 ns risetime? That's suspect, especially with 1ps resolution? And 6.16V Pk-Pk often goes through the entire sample record to find the maximum extent...(I make out about 5.2V, after settling). So Marcus' verdict is reasonable - more careful probing likely gives different results - learn to trust some measure functions, dis-trust others.
      $endgroup$
      – glen_geek
      7 hours ago












    • 1




      $begingroup$
      On OP's measure function: I'd believe 16.00MHz frequency (these 'scopes use a crystal time-base). But 9.500 ns risetime? That's suspect, especially with 1ps resolution? And 6.16V Pk-Pk often goes through the entire sample record to find the maximum extent...(I make out about 5.2V, after settling). So Marcus' verdict is reasonable - more careful probing likely gives different results - learn to trust some measure functions, dis-trust others.
      $endgroup$
      – glen_geek
      7 hours ago







    1




    1




    $begingroup$
    On OP's measure function: I'd believe 16.00MHz frequency (these 'scopes use a crystal time-base). But 9.500 ns risetime? That's suspect, especially with 1ps resolution? And 6.16V Pk-Pk often goes through the entire sample record to find the maximum extent...(I make out about 5.2V, after settling). So Marcus' verdict is reasonable - more careful probing likely gives different results - learn to trust some measure functions, dis-trust others.
    $endgroup$
    – glen_geek
    7 hours ago




    $begingroup$
    On OP's measure function: I'd believe 16.00MHz frequency (these 'scopes use a crystal time-base). But 9.500 ns risetime? That's suspect, especially with 1ps resolution? And 6.16V Pk-Pk often goes through the entire sample record to find the maximum extent...(I make out about 5.2V, after settling). So Marcus' verdict is reasonable - more careful probing likely gives different results - learn to trust some measure functions, dis-trust others.
    $endgroup$
    – glen_geek
    7 hours ago













    1













    $begingroup$

    Keep in mind that if you have a 100MHz brick-wall filter (ideal case) with a perfect 16MHz square wave in, the only harmonics you'll see are 1 (16MHz), 3 (48MHz) and 5 (80MHz). That's an ideal case, but if you do the calculations, you'll see the result isn't too far from what you're seeing.



    In the nonideal case, of course, probe loading and compensation will have further distorting effects, and the waveform isn't going to be perfectly square to start with.






    share|improve this answer









    $endgroup$



















      1













      $begingroup$

      Keep in mind that if you have a 100MHz brick-wall filter (ideal case) with a perfect 16MHz square wave in, the only harmonics you'll see are 1 (16MHz), 3 (48MHz) and 5 (80MHz). That's an ideal case, but if you do the calculations, you'll see the result isn't too far from what you're seeing.



      In the nonideal case, of course, probe loading and compensation will have further distorting effects, and the waveform isn't going to be perfectly square to start with.






      share|improve this answer









      $endgroup$

















        1














        1










        1







        $begingroup$

        Keep in mind that if you have a 100MHz brick-wall filter (ideal case) with a perfect 16MHz square wave in, the only harmonics you'll see are 1 (16MHz), 3 (48MHz) and 5 (80MHz). That's an ideal case, but if you do the calculations, you'll see the result isn't too far from what you're seeing.



        In the nonideal case, of course, probe loading and compensation will have further distorting effects, and the waveform isn't going to be perfectly square to start with.






        share|improve this answer









        $endgroup$



        Keep in mind that if you have a 100MHz brick-wall filter (ideal case) with a perfect 16MHz square wave in, the only harmonics you'll see are 1 (16MHz), 3 (48MHz) and 5 (80MHz). That's an ideal case, but if you do the calculations, you'll see the result isn't too far from what you're seeing.



        In the nonideal case, of course, probe loading and compensation will have further distorting effects, and the waveform isn't going to be perfectly square to start with.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered 6 hours ago









        Cristobol PolychronopolisCristobol Polychronopolis

        2,2403 silver badges10 bronze badges




        2,2403 silver badges10 bronze badges






























            draft saved

            draft discarded
















































            Thanks for contributing an answer to Electrical Engineering Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid


            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.

            Use MathJax to format equations. MathJax reference.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2felectronics.stackexchange.com%2fquestions%2f455356%2fcheap-oscilloscope-showing-16-mhz-square-wave%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Canceling a color specificationRandomly assigning color to Graphics3D objects?Default color for Filling in Mathematica 9Coloring specific elements of sets with a prime modified order in an array plotHow to pick a color differing significantly from the colors already in a given color list?Detection of the text colorColor numbers based on their valueCan color schemes for use with ColorData include opacity specification?My dynamic color schemes

            Invision Community Contents History See also References External links Navigation menuProprietaryinvisioncommunity.comIPS Community ForumsIPS Community Forumsthis blog entry"License Changes, IP.Board 3.4, and the Future""Interview -- Matt Mecham of Ibforums""CEO Invision Power Board, Matt Mecham Is a Liar, Thief!"IPB License Explanation 1.3, 1.3.1, 2.0, and 2.1ArchivedSecurity Fixes, Updates And Enhancements For IPB 1.3.1Archived"New Demo Accounts - Invision Power Services"the original"New Default Skin"the original"Invision Power Board 3.0.0 and Applications Released"the original"Archived copy"the original"Perpetual licenses being done away with""Release Notes - Invision Power Services""Introducing: IPS Community Suite 4!"Invision Community Release Notes

            François Viète Contents Biography Work and thought Bibliography See also Notes Further reading External links Navigation menup. 21Google Bookspp. 75–77Google BooksDe thou (from University of Saint Andrews)ArchivedGoogle BooksGoogle BooksGoogle BooksGoogle booksGoogle Bookscc-parthenay.frL'histoire universelle (fr)Universal History (en)ArchivedAdsabs.harvard.eduPagesperso-orange.frArchive.orgChikara Sasaki. Descartes' mathematical thought p.259Google BooksGoogle BooksGoogle Bookspp. 152 and onwardGoogle BooksGoogle BooksScribd.comGoogle Books1257-7979Google BooksGoogle BooksGoogle BooksGoogle BooksGoogle BooksGoogle BooksGallica.bnf.frGoogle BooksGoogle Books"François Viète"Francois Viète: Father of Modern Algebraic NotationThe Lawyer and the GamblerAbout TarporleySite de Jean-Paul GuichardL'algèbre nouvelle"About the Harmonicon"cb120511976(data)1188044800000 0001 0913 5903n82164680ola2013766880073431702w6vt1sb70287374827140948071409480