Why can't I see bouncing of a switch on an oscilloscope?Can't observe DC offset in a simple RC circuit with an oscilloscopeWhy I cannot see SPI signal properly with oscilloscope?See if signal is amplified without an oscilloscopeTiming diagram of circuit involving switch debouncingMy “audio oscilloscope” can't measure static/constant voltages but only changesHow to add bouncing to a switch in LTspice?Oscilloscope saving data unexpectedlyWhy do I see multiple waveforms on my oscilloscope in normal trigger mode?Bouncing at some points in square waveFrequency of contact bouncing

Is it legal for company to use my work email to pretend I still work there?

Languages that we cannot (dis)prove to be Context-Free

Can a vampire attack twice with their claws using Multiattack?

tikz convert color string to hex value

Client team has low performances and low technical skills: we always fix their work and now they stop collaborate with us. How to solve?

What's the output of a record needle playing an out-of-speed record

When a company launches a new product do they "come out" with a new product or do they "come up" with a new product?

Why does Kotter return in Welcome Back Kotter?

Can I ask the recruiters in my resume to put the reason why I am rejected?

Meaning of に in 本当に

Maximum likelihood parameters deviate from posterior distributions

What does it mean to describe someone as a butt steak?

Definite integral giving negative value as a result?

Malcev's paper "On a class of homogeneous spaces" in English

How to efficiently unroll a matrix by value with numpy?

NMaximize is not converging to a solution

Why "Having chlorophyll without photosynthesis is actually very dangerous" and "like living with a bomb"?

How to format long polynomial?

How does quantile regression compare to logistic regression with the variable split at the quantile?

How much of data wrangling is a data scientist's job?

Does detail obscure or enhance action?

Doing something right before you need it - expression for this?

Why can't I see bouncing of a switch on an oscilloscope?

Paid for article while in US on F-1 visa?



Why can't I see bouncing of a switch on an oscilloscope?


Can't observe DC offset in a simple RC circuit with an oscilloscopeWhy I cannot see SPI signal properly with oscilloscope?See if signal is amplified without an oscilloscopeTiming diagram of circuit involving switch debouncingMy “audio oscilloscope” can't measure static/constant voltages but only changesHow to add bouncing to a switch in LTspice?Oscilloscope saving data unexpectedlyWhy do I see multiple waveforms on my oscilloscope in normal trigger mode?Bouncing at some points in square waveFrequency of contact bouncing






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








8












$begingroup$


I'm trying to view the bouncing of a simple switch on an oscilloscope.



I have prepared a simple breadboard circuit (power->switch->resistor->ground). The problem is, it is displayed as a perfect square/rectangle on the scope. I have attached a photo of the scope screen and the circuit.



Please help me understand why I can't catch the bouncing of the switch on the scope. I don't think it this is a non-bouncing switch.



oscilloscope



circuit




Edit: Here is a photo showing a zoomed-in time scale (50us/div). As you can see it is rising from 0V to 9V within 150us and staying there. I have tried a few different switches. The resistor in the picture is 220-Ohm, 0.5-Watt.



enter image description here









share









New contributor




Deniz is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.







$endgroup$







  • 10




    $begingroup$
    Have you tried adjusting the time base / horizontal scale?
    $endgroup$
    – NMF
    9 hours ago







  • 1




    $begingroup$
    If you don't succeed on the first try, try again.
    $endgroup$
    – StainlessSteelRat
    9 hours ago






  • 9




    $begingroup$
    I have a hard time believing that your zoomed in version is actually a new trig. Nothing would look like that except the scope's internal interpolation. An clean break with an RC-filter created by the scope would show an exponential clean rise - nothing linear. I bet that you just zoomed in on the stored waveform.
    $endgroup$
    – pipe
    9 hours ago






  • 2




    $begingroup$
    My zoomed photo is from another capture with battery instead of power supply. But as @pipe sait I have captured on zoomed out view and then zoomed on the rising edge after that. Now I understand that changing time scale before the capture and after the capture is different things? I didn't know that. I will need to figure out how to capture when time scale is set to uSec range.
    $endgroup$
    – Deniz
    9 hours ago






  • 2




    $begingroup$
    @Deniz Set the time base reasonably fast (maybe 1ms), the scope trigger to "single" and "rising edge", then press the button. That should be OK. You might also want to look at the display settings, and either change the points to just show dots for each point, or to step to each point (giving a ”staircase" effect). That'll stop you getting fooled when you zoom in too far.
    $endgroup$
    – Graham
    8 hours ago

















8












$begingroup$


I'm trying to view the bouncing of a simple switch on an oscilloscope.



I have prepared a simple breadboard circuit (power->switch->resistor->ground). The problem is, it is displayed as a perfect square/rectangle on the scope. I have attached a photo of the scope screen and the circuit.



Please help me understand why I can't catch the bouncing of the switch on the scope. I don't think it this is a non-bouncing switch.



oscilloscope



circuit




Edit: Here is a photo showing a zoomed-in time scale (50us/div). As you can see it is rising from 0V to 9V within 150us and staying there. I have tried a few different switches. The resistor in the picture is 220-Ohm, 0.5-Watt.



enter image description here









share









New contributor




Deniz is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.







$endgroup$







  • 10




    $begingroup$
    Have you tried adjusting the time base / horizontal scale?
    $endgroup$
    – NMF
    9 hours ago







  • 1




    $begingroup$
    If you don't succeed on the first try, try again.
    $endgroup$
    – StainlessSteelRat
    9 hours ago






  • 9




    $begingroup$
    I have a hard time believing that your zoomed in version is actually a new trig. Nothing would look like that except the scope's internal interpolation. An clean break with an RC-filter created by the scope would show an exponential clean rise - nothing linear. I bet that you just zoomed in on the stored waveform.
    $endgroup$
    – pipe
    9 hours ago






  • 2




    $begingroup$
    My zoomed photo is from another capture with battery instead of power supply. But as @pipe sait I have captured on zoomed out view and then zoomed on the rising edge after that. Now I understand that changing time scale before the capture and after the capture is different things? I didn't know that. I will need to figure out how to capture when time scale is set to uSec range.
    $endgroup$
    – Deniz
    9 hours ago






  • 2




    $begingroup$
    @Deniz Set the time base reasonably fast (maybe 1ms), the scope trigger to "single" and "rising edge", then press the button. That should be OK. You might also want to look at the display settings, and either change the points to just show dots for each point, or to step to each point (giving a ”staircase" effect). That'll stop you getting fooled when you zoom in too far.
    $endgroup$
    – Graham
    8 hours ago













8












8








8


3



$begingroup$


I'm trying to view the bouncing of a simple switch on an oscilloscope.



I have prepared a simple breadboard circuit (power->switch->resistor->ground). The problem is, it is displayed as a perfect square/rectangle on the scope. I have attached a photo of the scope screen and the circuit.



Please help me understand why I can't catch the bouncing of the switch on the scope. I don't think it this is a non-bouncing switch.



oscilloscope



circuit




Edit: Here is a photo showing a zoomed-in time scale (50us/div). As you can see it is rising from 0V to 9V within 150us and staying there. I have tried a few different switches. The resistor in the picture is 220-Ohm, 0.5-Watt.



enter image description here









share









New contributor




Deniz is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.







$endgroup$




I'm trying to view the bouncing of a simple switch on an oscilloscope.



I have prepared a simple breadboard circuit (power->switch->resistor->ground). The problem is, it is displayed as a perfect square/rectangle on the scope. I have attached a photo of the scope screen and the circuit.



Please help me understand why I can't catch the bouncing of the switch on the scope. I don't think it this is a non-bouncing switch.



oscilloscope



circuit




Edit: Here is a photo showing a zoomed-in time scale (50us/div). As you can see it is rising from 0V to 9V within 150us and staying there. I have tried a few different switches. The resistor in the picture is 220-Ohm, 0.5-Watt.



enter image description here







switches oscilloscope debounce





share









New contributor




Deniz is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.










share









New contributor




Deniz is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.








share



share








edited 3 hours ago









bitsmack

11.9k73678




11.9k73678






New contributor




Deniz is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked 9 hours ago









DenizDeniz

1414




1414




New contributor




Deniz is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





Deniz is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






Deniz is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.







  • 10




    $begingroup$
    Have you tried adjusting the time base / horizontal scale?
    $endgroup$
    – NMF
    9 hours ago







  • 1




    $begingroup$
    If you don't succeed on the first try, try again.
    $endgroup$
    – StainlessSteelRat
    9 hours ago






  • 9




    $begingroup$
    I have a hard time believing that your zoomed in version is actually a new trig. Nothing would look like that except the scope's internal interpolation. An clean break with an RC-filter created by the scope would show an exponential clean rise - nothing linear. I bet that you just zoomed in on the stored waveform.
    $endgroup$
    – pipe
    9 hours ago






  • 2




    $begingroup$
    My zoomed photo is from another capture with battery instead of power supply. But as @pipe sait I have captured on zoomed out view and then zoomed on the rising edge after that. Now I understand that changing time scale before the capture and after the capture is different things? I didn't know that. I will need to figure out how to capture when time scale is set to uSec range.
    $endgroup$
    – Deniz
    9 hours ago






  • 2




    $begingroup$
    @Deniz Set the time base reasonably fast (maybe 1ms), the scope trigger to "single" and "rising edge", then press the button. That should be OK. You might also want to look at the display settings, and either change the points to just show dots for each point, or to step to each point (giving a ”staircase" effect). That'll stop you getting fooled when you zoom in too far.
    $endgroup$
    – Graham
    8 hours ago












  • 10




    $begingroup$
    Have you tried adjusting the time base / horizontal scale?
    $endgroup$
    – NMF
    9 hours ago







  • 1




    $begingroup$
    If you don't succeed on the first try, try again.
    $endgroup$
    – StainlessSteelRat
    9 hours ago






  • 9




    $begingroup$
    I have a hard time believing that your zoomed in version is actually a new trig. Nothing would look like that except the scope's internal interpolation. An clean break with an RC-filter created by the scope would show an exponential clean rise - nothing linear. I bet that you just zoomed in on the stored waveform.
    $endgroup$
    – pipe
    9 hours ago






  • 2




    $begingroup$
    My zoomed photo is from another capture with battery instead of power supply. But as @pipe sait I have captured on zoomed out view and then zoomed on the rising edge after that. Now I understand that changing time scale before the capture and after the capture is different things? I didn't know that. I will need to figure out how to capture when time scale is set to uSec range.
    $endgroup$
    – Deniz
    9 hours ago






  • 2




    $begingroup$
    @Deniz Set the time base reasonably fast (maybe 1ms), the scope trigger to "single" and "rising edge", then press the button. That should be OK. You might also want to look at the display settings, and either change the points to just show dots for each point, or to step to each point (giving a ”staircase" effect). That'll stop you getting fooled when you zoom in too far.
    $endgroup$
    – Graham
    8 hours ago







10




10




$begingroup$
Have you tried adjusting the time base / horizontal scale?
$endgroup$
– NMF
9 hours ago





$begingroup$
Have you tried adjusting the time base / horizontal scale?
$endgroup$
– NMF
9 hours ago





1




1




$begingroup$
If you don't succeed on the first try, try again.
$endgroup$
– StainlessSteelRat
9 hours ago




$begingroup$
If you don't succeed on the first try, try again.
$endgroup$
– StainlessSteelRat
9 hours ago




9




9




$begingroup$
I have a hard time believing that your zoomed in version is actually a new trig. Nothing would look like that except the scope's internal interpolation. An clean break with an RC-filter created by the scope would show an exponential clean rise - nothing linear. I bet that you just zoomed in on the stored waveform.
$endgroup$
– pipe
9 hours ago




$begingroup$
I have a hard time believing that your zoomed in version is actually a new trig. Nothing would look like that except the scope's internal interpolation. An clean break with an RC-filter created by the scope would show an exponential clean rise - nothing linear. I bet that you just zoomed in on the stored waveform.
$endgroup$
– pipe
9 hours ago




2




2




$begingroup$
My zoomed photo is from another capture with battery instead of power supply. But as @pipe sait I have captured on zoomed out view and then zoomed on the rising edge after that. Now I understand that changing time scale before the capture and after the capture is different things? I didn't know that. I will need to figure out how to capture when time scale is set to uSec range.
$endgroup$
– Deniz
9 hours ago




$begingroup$
My zoomed photo is from another capture with battery instead of power supply. But as @pipe sait I have captured on zoomed out view and then zoomed on the rising edge after that. Now I understand that changing time scale before the capture and after the capture is different things? I didn't know that. I will need to figure out how to capture when time scale is set to uSec range.
$endgroup$
– Deniz
9 hours ago




2




2




$begingroup$
@Deniz Set the time base reasonably fast (maybe 1ms), the scope trigger to "single" and "rising edge", then press the button. That should be OK. You might also want to look at the display settings, and either change the points to just show dots for each point, or to step to each point (giving a ”staircase" effect). That'll stop you getting fooled when you zoom in too far.
$endgroup$
– Graham
8 hours ago




$begingroup$
@Deniz Set the time base reasonably fast (maybe 1ms), the scope trigger to "single" and "rising edge", then press the button. That should be OK. You might also want to look at the display settings, and either change the points to just show dots for each point, or to step to each point (giving a ”staircase" effect). That'll stop you getting fooled when you zoom in too far.
$endgroup$
– Graham
8 hours ago










7 Answers
7






active

oldest

votes


















10












$begingroup$

First, "zoom in" to that rising edge by adjusting the time base. When you start getting close, you will start to see the rising slope of the signal.



As you do this, you will start to lose resolution on your captured signal. You can capture new samples of that rising edge using the scope's triggering mechanism.



Once you can see the rising slope, capture a new sample. Any bouncing/overshoot/noise should become apparent.






share|improve this answer











$endgroup$












  • $begingroup$
    I have added 50uSec zoomed time scale photo. As you can see no bounce. I will also try to read button with a micro controller to see whether it is actually bouncing or not.
    $endgroup$
    – Deniz
    9 hours ago






  • 7




    $begingroup$
    If you zoom a stored waveform it may not have intermediate samples and just interpolate. You may see the edge sharper if you store a new sample at the higher timebase setting. As mentioned, good or new switches may have very little detectable bounce.
    $endgroup$
    – KalleMP
    9 hours ago







  • 4




    $begingroup$
    @Deniz no switch closure is going to result in a piecewise linear pulse -- that has to be a zoom-in of something sampled at a lower rate (probably 150$mu$s, because that's how long it's taking to rise up).
    $endgroup$
    – TimWescott
    8 hours ago






  • 1




    $begingroup$
    @Deniz To convince oneself, switch the scope display mode to points if possible
    $endgroup$
    – crasic
    3 hours ago


















6












$begingroup$

This is an issue with scope setup and misunderstanding of how to interpret scope captures. You must capture the rising edge of a single pulse at a reasonably small resolution by using a single trigger. Good news is that this is exactly what oscilloscopes are designed to do



The generic procedure is:



  1. Set trigger to edge (up) and trigger level at approximately half scale of your button voltage

  2. (Optional) Move the trigger (horizontal) offset to the left hand of screen to maximize the portion of capture after trigger

  3. Switch trigger to "normal" and "single mode" to arm the trigger for a single capture

  4. Press your button

  5. If you use continuous trigger you will get a new capture with every button press

  6. If you don't use normal mode you may lose the captured signal due to preview refresh (typically triggered at 60 Hz to have a simulated "live signal" mode), "single-normal" mode freezes the scope after capture


Most digital capture scopes record a fixed number of points at all time base, so the sample rate is determined by a combination of time base and capture depth (which may be configured) and limited by the maximum sampling rate. On my Tektronix oscilloscope the scope displays both the time per div and effective sample rate.



What is displayed may also be "windowed" depending on the mode, so it may not always be clear what your sample rate actually is. For example, 100K points into 1-second timebase with 10 divisions on screen would be 10 kS/sec. 100k points into a 10 µs timebase with 10 divisions on screen would be 1 GS/sec. Typically this is near the limit for common digital scopes, so time bases below 10 µs are often "zoomed in" divisions at 10 µs (e.g. 100k points into 10 divisions at 10 µs, but display one division with 1 µs time base on the screen).



Also note that analog bandwidth (for example, "100 MHz") does not directly relate to the digital sample rate.



An additional quirk, triggering is not done on the (digital) sampled signal, but directly on the input through a dedicated trigger system. This means that you can trigger (sometimes) on a pulse that is too short to be resolved in the digital signal. Or you can add a trigger delay much much longer than the sample depth (for example, display the capture at 10 µs resolution, but 1 second after the trigger). This is also why there is often an "aux" or "external trigger" port that can be used to trigger, but never displayed or captured.



The scope is effectively sampling continuously into a ring buffer and the trigger comes along and tells the sampling systems to store the buffer. This is a large amount of data, so it requires some time to store the data and to rearm the sample system. The electronics and suitable memory to process a gigabit stream continuously is very expensive so scopes are designed to make use of limited storage depth and digital bandwidth through triggering schemes.






share|improve this answer











$endgroup$












  • $begingroup$
    +1! Much more informative than my answer :)
    $endgroup$
    – bitsmack
    3 hours ago


















4












$begingroup$

enter image description here



Figure 1. The guys down at photo-forensics found this.



There are several factors:



  • You have a nice new clean switch that bounces very little.

  • Your scope is loading the circuit and the 15 pF is enough to help. This is unlikely, though, with what appears to be a resistor with a value in the hundreds of ohms. (The colour rendition of your photo is poor.)

  • Timebase is too fast - but your comments say you've checked this.

I'd go with the first and second option.






share|improve this answer









$endgroup$












  • $begingroup$
    I have added 50uSec zoomed time scale photo. As you can see no bounce. I will also try to read button with a micro controller to see whether it is actually bouncing or not.
    $endgroup$
    – Deniz
    9 hours ago






  • 3




    $begingroup$
    So you think the 15pF is loading the 220 Ohms with a 3.3ns RC asymptote resulting in a 150us linear ramp? Ask the forensic guys to check again. My forensic guy said it smelt like 220 ohm i.stack.imgur.com/xEwUo.png
    $endgroup$
    – Sunnyskyguy EE75
    8 hours ago



















4












$begingroup$

Assuming that the pull-down resistor is a reasonable value (1k - 10k), the very next thing that I would check is to see if there is a filter active on that channel. I wouldn't be looking for signal averaging - this is a single-event occurrence and the trace shows that single event. But it is entirely possible that there is a very-low frequency low-pass filter that is turned ON in the scope.



Another way to find out if it is a scope problem is to simply plug a pair of wires into the busses for the switch contacts. Then brush the two switch wires together and look at the noise (or lack thereof). Noise means scope is probably okay. Smooth ramp says that the scope isn't displaying the full bandwidth of the input signal.






share|improve this answer









$endgroup$




















    2












    $begingroup$

    Here is a test I did with my 200MHz Tek scope. You should be able to get similar results with the Rigol, this is an older scope with a modest 2Gs/s capture frequency.



    My circuit is just a standard 10:1 probe connected across a 6mm tact switch with a 1K pullup to +5V supply.



    enter image description here



    Not all the captures were this messy, some were pretty ideal looking. Pushing it hard seemed to lead to more messiness. There's a bit of ringing despite a bypass across the power supply- that falling edge due to the switch contacts closing is very fast.



    If I set the sweep too slow (and then expand) I just get interpolation between samples, which might be misleading. There's no information there so the scope fakes it.



    Capture was single event, triggered by falling edge on the active channel, set relatively close to the 5V level (the yellow arrow on the right indicates the trigger level of 3.68V). The center of the screen is at -96ns (moved to view a bit more of the pre-trigger data since most of the action is pre-trigger).






    share|improve this answer









    $endgroup$




















      -1












      $begingroup$

      Use an old switch or store your new switch in a mixture of salt water and vinegar for a few hours. That will corrode the contacts and increase the bounce.






      share|improve this answer










      New contributor




      ron is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






      $endgroup$




















        -2












        $begingroup$

        I have gone thru the answers mentioned above.



        But First, please change your oscilloscope.



        The scope you are using would have a shallow memory.(Acquisition Memory ...may be 1K or a few K memory).
        Try with Deep Memory Scopes.Tektronix TDS 3000 or 4000 series , Keysight DSOx 3000 to 6000 series or many more brands and models are available.



        You will definitely get a beautiful contact bounce ringing at the top the vertical rising/ falling edges.



        The number of ringing edges is proportional to the length of your grounding wire length.Less the length, less ringing.The more the length, more ringing.



        The Deep Memory scopes will contain record length or Acquisition memory in terms of Mb ....say 2Mb , 4Mb, 8Mb etc......Don't worry about Sampling rates. Deep memory will control to sustain the sampling rate.



        I have captured enough time these switching circuits,in Deep memory scopes.



        Try ...



        Best Regards
        A Senthil






        share|improve this answer








        New contributor




        A Senthil is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.






        $endgroup$








        • 10




          $begingroup$
          The instrument in use is orders or magnitude more than sufficient if used properly. Recommending the purchase of new gear over learning to use the ordinary and suitable gear at hand is the mark of those who do not know what they are doing. There exists a capture rate, within the capability of that scope where the bouncing of the actual contacts is easily represented on the screen alone, nevermind any off-screen memory.
          $endgroup$
          – Chris Stratton
          4 hours ago










        protected by Nick Alexeev 2 hours ago



        Thank you for your interest in this question.
        Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



        Would you like to answer one of these unanswered questions instead?














        7 Answers
        7






        active

        oldest

        votes








        7 Answers
        7






        active

        oldest

        votes









        active

        oldest

        votes






        active

        oldest

        votes









        10












        $begingroup$

        First, "zoom in" to that rising edge by adjusting the time base. When you start getting close, you will start to see the rising slope of the signal.



        As you do this, you will start to lose resolution on your captured signal. You can capture new samples of that rising edge using the scope's triggering mechanism.



        Once you can see the rising slope, capture a new sample. Any bouncing/overshoot/noise should become apparent.






        share|improve this answer











        $endgroup$












        • $begingroup$
          I have added 50uSec zoomed time scale photo. As you can see no bounce. I will also try to read button with a micro controller to see whether it is actually bouncing or not.
          $endgroup$
          – Deniz
          9 hours ago






        • 7




          $begingroup$
          If you zoom a stored waveform it may not have intermediate samples and just interpolate. You may see the edge sharper if you store a new sample at the higher timebase setting. As mentioned, good or new switches may have very little detectable bounce.
          $endgroup$
          – KalleMP
          9 hours ago







        • 4




          $begingroup$
          @Deniz no switch closure is going to result in a piecewise linear pulse -- that has to be a zoom-in of something sampled at a lower rate (probably 150$mu$s, because that's how long it's taking to rise up).
          $endgroup$
          – TimWescott
          8 hours ago






        • 1




          $begingroup$
          @Deniz To convince oneself, switch the scope display mode to points if possible
          $endgroup$
          – crasic
          3 hours ago















        10












        $begingroup$

        First, "zoom in" to that rising edge by adjusting the time base. When you start getting close, you will start to see the rising slope of the signal.



        As you do this, you will start to lose resolution on your captured signal. You can capture new samples of that rising edge using the scope's triggering mechanism.



        Once you can see the rising slope, capture a new sample. Any bouncing/overshoot/noise should become apparent.






        share|improve this answer











        $endgroup$












        • $begingroup$
          I have added 50uSec zoomed time scale photo. As you can see no bounce. I will also try to read button with a micro controller to see whether it is actually bouncing or not.
          $endgroup$
          – Deniz
          9 hours ago






        • 7




          $begingroup$
          If you zoom a stored waveform it may not have intermediate samples and just interpolate. You may see the edge sharper if you store a new sample at the higher timebase setting. As mentioned, good or new switches may have very little detectable bounce.
          $endgroup$
          – KalleMP
          9 hours ago







        • 4




          $begingroup$
          @Deniz no switch closure is going to result in a piecewise linear pulse -- that has to be a zoom-in of something sampled at a lower rate (probably 150$mu$s, because that's how long it's taking to rise up).
          $endgroup$
          – TimWescott
          8 hours ago






        • 1




          $begingroup$
          @Deniz To convince oneself, switch the scope display mode to points if possible
          $endgroup$
          – crasic
          3 hours ago













        10












        10








        10





        $begingroup$

        First, "zoom in" to that rising edge by adjusting the time base. When you start getting close, you will start to see the rising slope of the signal.



        As you do this, you will start to lose resolution on your captured signal. You can capture new samples of that rising edge using the scope's triggering mechanism.



        Once you can see the rising slope, capture a new sample. Any bouncing/overshoot/noise should become apparent.






        share|improve this answer











        $endgroup$



        First, "zoom in" to that rising edge by adjusting the time base. When you start getting close, you will start to see the rising slope of the signal.



        As you do this, you will start to lose resolution on your captured signal. You can capture new samples of that rising edge using the scope's triggering mechanism.



        Once you can see the rising slope, capture a new sample. Any bouncing/overshoot/noise should become apparent.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited 8 hours ago

























        answered 9 hours ago









        bitsmackbitsmack

        11.9k73678




        11.9k73678











        • $begingroup$
          I have added 50uSec zoomed time scale photo. As you can see no bounce. I will also try to read button with a micro controller to see whether it is actually bouncing or not.
          $endgroup$
          – Deniz
          9 hours ago






        • 7




          $begingroup$
          If you zoom a stored waveform it may not have intermediate samples and just interpolate. You may see the edge sharper if you store a new sample at the higher timebase setting. As mentioned, good or new switches may have very little detectable bounce.
          $endgroup$
          – KalleMP
          9 hours ago







        • 4




          $begingroup$
          @Deniz no switch closure is going to result in a piecewise linear pulse -- that has to be a zoom-in of something sampled at a lower rate (probably 150$mu$s, because that's how long it's taking to rise up).
          $endgroup$
          – TimWescott
          8 hours ago






        • 1




          $begingroup$
          @Deniz To convince oneself, switch the scope display mode to points if possible
          $endgroup$
          – crasic
          3 hours ago
















        • $begingroup$
          I have added 50uSec zoomed time scale photo. As you can see no bounce. I will also try to read button with a micro controller to see whether it is actually bouncing or not.
          $endgroup$
          – Deniz
          9 hours ago






        • 7




          $begingroup$
          If you zoom a stored waveform it may not have intermediate samples and just interpolate. You may see the edge sharper if you store a new sample at the higher timebase setting. As mentioned, good or new switches may have very little detectable bounce.
          $endgroup$
          – KalleMP
          9 hours ago







        • 4




          $begingroup$
          @Deniz no switch closure is going to result in a piecewise linear pulse -- that has to be a zoom-in of something sampled at a lower rate (probably 150$mu$s, because that's how long it's taking to rise up).
          $endgroup$
          – TimWescott
          8 hours ago






        • 1




          $begingroup$
          @Deniz To convince oneself, switch the scope display mode to points if possible
          $endgroup$
          – crasic
          3 hours ago















        $begingroup$
        I have added 50uSec zoomed time scale photo. As you can see no bounce. I will also try to read button with a micro controller to see whether it is actually bouncing or not.
        $endgroup$
        – Deniz
        9 hours ago




        $begingroup$
        I have added 50uSec zoomed time scale photo. As you can see no bounce. I will also try to read button with a micro controller to see whether it is actually bouncing or not.
        $endgroup$
        – Deniz
        9 hours ago




        7




        7




        $begingroup$
        If you zoom a stored waveform it may not have intermediate samples and just interpolate. You may see the edge sharper if you store a new sample at the higher timebase setting. As mentioned, good or new switches may have very little detectable bounce.
        $endgroup$
        – KalleMP
        9 hours ago





        $begingroup$
        If you zoom a stored waveform it may not have intermediate samples and just interpolate. You may see the edge sharper if you store a new sample at the higher timebase setting. As mentioned, good or new switches may have very little detectable bounce.
        $endgroup$
        – KalleMP
        9 hours ago





        4




        4




        $begingroup$
        @Deniz no switch closure is going to result in a piecewise linear pulse -- that has to be a zoom-in of something sampled at a lower rate (probably 150$mu$s, because that's how long it's taking to rise up).
        $endgroup$
        – TimWescott
        8 hours ago




        $begingroup$
        @Deniz no switch closure is going to result in a piecewise linear pulse -- that has to be a zoom-in of something sampled at a lower rate (probably 150$mu$s, because that's how long it's taking to rise up).
        $endgroup$
        – TimWescott
        8 hours ago




        1




        1




        $begingroup$
        @Deniz To convince oneself, switch the scope display mode to points if possible
        $endgroup$
        – crasic
        3 hours ago




        $begingroup$
        @Deniz To convince oneself, switch the scope display mode to points if possible
        $endgroup$
        – crasic
        3 hours ago













        6












        $begingroup$

        This is an issue with scope setup and misunderstanding of how to interpret scope captures. You must capture the rising edge of a single pulse at a reasonably small resolution by using a single trigger. Good news is that this is exactly what oscilloscopes are designed to do



        The generic procedure is:



        1. Set trigger to edge (up) and trigger level at approximately half scale of your button voltage

        2. (Optional) Move the trigger (horizontal) offset to the left hand of screen to maximize the portion of capture after trigger

        3. Switch trigger to "normal" and "single mode" to arm the trigger for a single capture

        4. Press your button

        5. If you use continuous trigger you will get a new capture with every button press

        6. If you don't use normal mode you may lose the captured signal due to preview refresh (typically triggered at 60 Hz to have a simulated "live signal" mode), "single-normal" mode freezes the scope after capture


        Most digital capture scopes record a fixed number of points at all time base, so the sample rate is determined by a combination of time base and capture depth (which may be configured) and limited by the maximum sampling rate. On my Tektronix oscilloscope the scope displays both the time per div and effective sample rate.



        What is displayed may also be "windowed" depending on the mode, so it may not always be clear what your sample rate actually is. For example, 100K points into 1-second timebase with 10 divisions on screen would be 10 kS/sec. 100k points into a 10 µs timebase with 10 divisions on screen would be 1 GS/sec. Typically this is near the limit for common digital scopes, so time bases below 10 µs are often "zoomed in" divisions at 10 µs (e.g. 100k points into 10 divisions at 10 µs, but display one division with 1 µs time base on the screen).



        Also note that analog bandwidth (for example, "100 MHz") does not directly relate to the digital sample rate.



        An additional quirk, triggering is not done on the (digital) sampled signal, but directly on the input through a dedicated trigger system. This means that you can trigger (sometimes) on a pulse that is too short to be resolved in the digital signal. Or you can add a trigger delay much much longer than the sample depth (for example, display the capture at 10 µs resolution, but 1 second after the trigger). This is also why there is often an "aux" or "external trigger" port that can be used to trigger, but never displayed or captured.



        The scope is effectively sampling continuously into a ring buffer and the trigger comes along and tells the sampling systems to store the buffer. This is a large amount of data, so it requires some time to store the data and to rearm the sample system. The electronics and suitable memory to process a gigabit stream continuously is very expensive so scopes are designed to make use of limited storage depth and digital bandwidth through triggering schemes.






        share|improve this answer











        $endgroup$












        • $begingroup$
          +1! Much more informative than my answer :)
          $endgroup$
          – bitsmack
          3 hours ago















        6












        $begingroup$

        This is an issue with scope setup and misunderstanding of how to interpret scope captures. You must capture the rising edge of a single pulse at a reasonably small resolution by using a single trigger. Good news is that this is exactly what oscilloscopes are designed to do



        The generic procedure is:



        1. Set trigger to edge (up) and trigger level at approximately half scale of your button voltage

        2. (Optional) Move the trigger (horizontal) offset to the left hand of screen to maximize the portion of capture after trigger

        3. Switch trigger to "normal" and "single mode" to arm the trigger for a single capture

        4. Press your button

        5. If you use continuous trigger you will get a new capture with every button press

        6. If you don't use normal mode you may lose the captured signal due to preview refresh (typically triggered at 60 Hz to have a simulated "live signal" mode), "single-normal" mode freezes the scope after capture


        Most digital capture scopes record a fixed number of points at all time base, so the sample rate is determined by a combination of time base and capture depth (which may be configured) and limited by the maximum sampling rate. On my Tektronix oscilloscope the scope displays both the time per div and effective sample rate.



        What is displayed may also be "windowed" depending on the mode, so it may not always be clear what your sample rate actually is. For example, 100K points into 1-second timebase with 10 divisions on screen would be 10 kS/sec. 100k points into a 10 µs timebase with 10 divisions on screen would be 1 GS/sec. Typically this is near the limit for common digital scopes, so time bases below 10 µs are often "zoomed in" divisions at 10 µs (e.g. 100k points into 10 divisions at 10 µs, but display one division with 1 µs time base on the screen).



        Also note that analog bandwidth (for example, "100 MHz") does not directly relate to the digital sample rate.



        An additional quirk, triggering is not done on the (digital) sampled signal, but directly on the input through a dedicated trigger system. This means that you can trigger (sometimes) on a pulse that is too short to be resolved in the digital signal. Or you can add a trigger delay much much longer than the sample depth (for example, display the capture at 10 µs resolution, but 1 second after the trigger). This is also why there is often an "aux" or "external trigger" port that can be used to trigger, but never displayed or captured.



        The scope is effectively sampling continuously into a ring buffer and the trigger comes along and tells the sampling systems to store the buffer. This is a large amount of data, so it requires some time to store the data and to rearm the sample system. The electronics and suitable memory to process a gigabit stream continuously is very expensive so scopes are designed to make use of limited storage depth and digital bandwidth through triggering schemes.






        share|improve this answer











        $endgroup$












        • $begingroup$
          +1! Much more informative than my answer :)
          $endgroup$
          – bitsmack
          3 hours ago













        6












        6








        6





        $begingroup$

        This is an issue with scope setup and misunderstanding of how to interpret scope captures. You must capture the rising edge of a single pulse at a reasonably small resolution by using a single trigger. Good news is that this is exactly what oscilloscopes are designed to do



        The generic procedure is:



        1. Set trigger to edge (up) and trigger level at approximately half scale of your button voltage

        2. (Optional) Move the trigger (horizontal) offset to the left hand of screen to maximize the portion of capture after trigger

        3. Switch trigger to "normal" and "single mode" to arm the trigger for a single capture

        4. Press your button

        5. If you use continuous trigger you will get a new capture with every button press

        6. If you don't use normal mode you may lose the captured signal due to preview refresh (typically triggered at 60 Hz to have a simulated "live signal" mode), "single-normal" mode freezes the scope after capture


        Most digital capture scopes record a fixed number of points at all time base, so the sample rate is determined by a combination of time base and capture depth (which may be configured) and limited by the maximum sampling rate. On my Tektronix oscilloscope the scope displays both the time per div and effective sample rate.



        What is displayed may also be "windowed" depending on the mode, so it may not always be clear what your sample rate actually is. For example, 100K points into 1-second timebase with 10 divisions on screen would be 10 kS/sec. 100k points into a 10 µs timebase with 10 divisions on screen would be 1 GS/sec. Typically this is near the limit for common digital scopes, so time bases below 10 µs are often "zoomed in" divisions at 10 µs (e.g. 100k points into 10 divisions at 10 µs, but display one division with 1 µs time base on the screen).



        Also note that analog bandwidth (for example, "100 MHz") does not directly relate to the digital sample rate.



        An additional quirk, triggering is not done on the (digital) sampled signal, but directly on the input through a dedicated trigger system. This means that you can trigger (sometimes) on a pulse that is too short to be resolved in the digital signal. Or you can add a trigger delay much much longer than the sample depth (for example, display the capture at 10 µs resolution, but 1 second after the trigger). This is also why there is often an "aux" or "external trigger" port that can be used to trigger, but never displayed or captured.



        The scope is effectively sampling continuously into a ring buffer and the trigger comes along and tells the sampling systems to store the buffer. This is a large amount of data, so it requires some time to store the data and to rearm the sample system. The electronics and suitable memory to process a gigabit stream continuously is very expensive so scopes are designed to make use of limited storage depth and digital bandwidth through triggering schemes.






        share|improve this answer











        $endgroup$



        This is an issue with scope setup and misunderstanding of how to interpret scope captures. You must capture the rising edge of a single pulse at a reasonably small resolution by using a single trigger. Good news is that this is exactly what oscilloscopes are designed to do



        The generic procedure is:



        1. Set trigger to edge (up) and trigger level at approximately half scale of your button voltage

        2. (Optional) Move the trigger (horizontal) offset to the left hand of screen to maximize the portion of capture after trigger

        3. Switch trigger to "normal" and "single mode" to arm the trigger for a single capture

        4. Press your button

        5. If you use continuous trigger you will get a new capture with every button press

        6. If you don't use normal mode you may lose the captured signal due to preview refresh (typically triggered at 60 Hz to have a simulated "live signal" mode), "single-normal" mode freezes the scope after capture


        Most digital capture scopes record a fixed number of points at all time base, so the sample rate is determined by a combination of time base and capture depth (which may be configured) and limited by the maximum sampling rate. On my Tektronix oscilloscope the scope displays both the time per div and effective sample rate.



        What is displayed may also be "windowed" depending on the mode, so it may not always be clear what your sample rate actually is. For example, 100K points into 1-second timebase with 10 divisions on screen would be 10 kS/sec. 100k points into a 10 µs timebase with 10 divisions on screen would be 1 GS/sec. Typically this is near the limit for common digital scopes, so time bases below 10 µs are often "zoomed in" divisions at 10 µs (e.g. 100k points into 10 divisions at 10 µs, but display one division with 1 µs time base on the screen).



        Also note that analog bandwidth (for example, "100 MHz") does not directly relate to the digital sample rate.



        An additional quirk, triggering is not done on the (digital) sampled signal, but directly on the input through a dedicated trigger system. This means that you can trigger (sometimes) on a pulse that is too short to be resolved in the digital signal. Or you can add a trigger delay much much longer than the sample depth (for example, display the capture at 10 µs resolution, but 1 second after the trigger). This is also why there is often an "aux" or "external trigger" port that can be used to trigger, but never displayed or captured.



        The scope is effectively sampling continuously into a ring buffer and the trigger comes along and tells the sampling systems to store the buffer. This is a large amount of data, so it requires some time to store the data and to rearm the sample system. The electronics and suitable memory to process a gigabit stream continuously is very expensive so scopes are designed to make use of limited storage depth and digital bandwidth through triggering schemes.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited 47 mins ago









        Peter Mortensen

        1,60031422




        1,60031422










        answered 6 hours ago









        crasiccrasic

        3,104926




        3,104926











        • $begingroup$
          +1! Much more informative than my answer :)
          $endgroup$
          – bitsmack
          3 hours ago
















        • $begingroup$
          +1! Much more informative than my answer :)
          $endgroup$
          – bitsmack
          3 hours ago















        $begingroup$
        +1! Much more informative than my answer :)
        $endgroup$
        – bitsmack
        3 hours ago




        $begingroup$
        +1! Much more informative than my answer :)
        $endgroup$
        – bitsmack
        3 hours ago











        4












        $begingroup$

        enter image description here



        Figure 1. The guys down at photo-forensics found this.



        There are several factors:



        • You have a nice new clean switch that bounces very little.

        • Your scope is loading the circuit and the 15 pF is enough to help. This is unlikely, though, with what appears to be a resistor with a value in the hundreds of ohms. (The colour rendition of your photo is poor.)

        • Timebase is too fast - but your comments say you've checked this.

        I'd go with the first and second option.






        share|improve this answer









        $endgroup$












        • $begingroup$
          I have added 50uSec zoomed time scale photo. As you can see no bounce. I will also try to read button with a micro controller to see whether it is actually bouncing or not.
          $endgroup$
          – Deniz
          9 hours ago






        • 3




          $begingroup$
          So you think the 15pF is loading the 220 Ohms with a 3.3ns RC asymptote resulting in a 150us linear ramp? Ask the forensic guys to check again. My forensic guy said it smelt like 220 ohm i.stack.imgur.com/xEwUo.png
          $endgroup$
          – Sunnyskyguy EE75
          8 hours ago
















        4












        $begingroup$

        enter image description here



        Figure 1. The guys down at photo-forensics found this.



        There are several factors:



        • You have a nice new clean switch that bounces very little.

        • Your scope is loading the circuit and the 15 pF is enough to help. This is unlikely, though, with what appears to be a resistor with a value in the hundreds of ohms. (The colour rendition of your photo is poor.)

        • Timebase is too fast - but your comments say you've checked this.

        I'd go with the first and second option.






        share|improve this answer









        $endgroup$












        • $begingroup$
          I have added 50uSec zoomed time scale photo. As you can see no bounce. I will also try to read button with a micro controller to see whether it is actually bouncing or not.
          $endgroup$
          – Deniz
          9 hours ago






        • 3




          $begingroup$
          So you think the 15pF is loading the 220 Ohms with a 3.3ns RC asymptote resulting in a 150us linear ramp? Ask the forensic guys to check again. My forensic guy said it smelt like 220 ohm i.stack.imgur.com/xEwUo.png
          $endgroup$
          – Sunnyskyguy EE75
          8 hours ago














        4












        4








        4





        $begingroup$

        enter image description here



        Figure 1. The guys down at photo-forensics found this.



        There are several factors:



        • You have a nice new clean switch that bounces very little.

        • Your scope is loading the circuit and the 15 pF is enough to help. This is unlikely, though, with what appears to be a resistor with a value in the hundreds of ohms. (The colour rendition of your photo is poor.)

        • Timebase is too fast - but your comments say you've checked this.

        I'd go with the first and second option.






        share|improve this answer









        $endgroup$



        enter image description here



        Figure 1. The guys down at photo-forensics found this.



        There are several factors:



        • You have a nice new clean switch that bounces very little.

        • Your scope is loading the circuit and the 15 pF is enough to help. This is unlikely, though, with what appears to be a resistor with a value in the hundreds of ohms. (The colour rendition of your photo is poor.)

        • Timebase is too fast - but your comments say you've checked this.

        I'd go with the first and second option.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered 9 hours ago









        TransistorTransistor

        88.3k785189




        88.3k785189











        • $begingroup$
          I have added 50uSec zoomed time scale photo. As you can see no bounce. I will also try to read button with a micro controller to see whether it is actually bouncing or not.
          $endgroup$
          – Deniz
          9 hours ago






        • 3




          $begingroup$
          So you think the 15pF is loading the 220 Ohms with a 3.3ns RC asymptote resulting in a 150us linear ramp? Ask the forensic guys to check again. My forensic guy said it smelt like 220 ohm i.stack.imgur.com/xEwUo.png
          $endgroup$
          – Sunnyskyguy EE75
          8 hours ago

















        • $begingroup$
          I have added 50uSec zoomed time scale photo. As you can see no bounce. I will also try to read button with a micro controller to see whether it is actually bouncing or not.
          $endgroup$
          – Deniz
          9 hours ago






        • 3




          $begingroup$
          So you think the 15pF is loading the 220 Ohms with a 3.3ns RC asymptote resulting in a 150us linear ramp? Ask the forensic guys to check again. My forensic guy said it smelt like 220 ohm i.stack.imgur.com/xEwUo.png
          $endgroup$
          – Sunnyskyguy EE75
          8 hours ago
















        $begingroup$
        I have added 50uSec zoomed time scale photo. As you can see no bounce. I will also try to read button with a micro controller to see whether it is actually bouncing or not.
        $endgroup$
        – Deniz
        9 hours ago




        $begingroup$
        I have added 50uSec zoomed time scale photo. As you can see no bounce. I will also try to read button with a micro controller to see whether it is actually bouncing or not.
        $endgroup$
        – Deniz
        9 hours ago




        3




        3




        $begingroup$
        So you think the 15pF is loading the 220 Ohms with a 3.3ns RC asymptote resulting in a 150us linear ramp? Ask the forensic guys to check again. My forensic guy said it smelt like 220 ohm i.stack.imgur.com/xEwUo.png
        $endgroup$
        – Sunnyskyguy EE75
        8 hours ago





        $begingroup$
        So you think the 15pF is loading the 220 Ohms with a 3.3ns RC asymptote resulting in a 150us linear ramp? Ask the forensic guys to check again. My forensic guy said it smelt like 220 ohm i.stack.imgur.com/xEwUo.png
        $endgroup$
        – Sunnyskyguy EE75
        8 hours ago












        4












        $begingroup$

        Assuming that the pull-down resistor is a reasonable value (1k - 10k), the very next thing that I would check is to see if there is a filter active on that channel. I wouldn't be looking for signal averaging - this is a single-event occurrence and the trace shows that single event. But it is entirely possible that there is a very-low frequency low-pass filter that is turned ON in the scope.



        Another way to find out if it is a scope problem is to simply plug a pair of wires into the busses for the switch contacts. Then brush the two switch wires together and look at the noise (or lack thereof). Noise means scope is probably okay. Smooth ramp says that the scope isn't displaying the full bandwidth of the input signal.






        share|improve this answer









        $endgroup$

















          4












          $begingroup$

          Assuming that the pull-down resistor is a reasonable value (1k - 10k), the very next thing that I would check is to see if there is a filter active on that channel. I wouldn't be looking for signal averaging - this is a single-event occurrence and the trace shows that single event. But it is entirely possible that there is a very-low frequency low-pass filter that is turned ON in the scope.



          Another way to find out if it is a scope problem is to simply plug a pair of wires into the busses for the switch contacts. Then brush the two switch wires together and look at the noise (or lack thereof). Noise means scope is probably okay. Smooth ramp says that the scope isn't displaying the full bandwidth of the input signal.






          share|improve this answer









          $endgroup$















            4












            4








            4





            $begingroup$

            Assuming that the pull-down resistor is a reasonable value (1k - 10k), the very next thing that I would check is to see if there is a filter active on that channel. I wouldn't be looking for signal averaging - this is a single-event occurrence and the trace shows that single event. But it is entirely possible that there is a very-low frequency low-pass filter that is turned ON in the scope.



            Another way to find out if it is a scope problem is to simply plug a pair of wires into the busses for the switch contacts. Then brush the two switch wires together and look at the noise (or lack thereof). Noise means scope is probably okay. Smooth ramp says that the scope isn't displaying the full bandwidth of the input signal.






            share|improve this answer









            $endgroup$



            Assuming that the pull-down resistor is a reasonable value (1k - 10k), the very next thing that I would check is to see if there is a filter active on that channel. I wouldn't be looking for signal averaging - this is a single-event occurrence and the trace shows that single event. But it is entirely possible that there is a very-low frequency low-pass filter that is turned ON in the scope.



            Another way to find out if it is a scope problem is to simply plug a pair of wires into the busses for the switch contacts. Then brush the two switch wires together and look at the noise (or lack thereof). Noise means scope is probably okay. Smooth ramp says that the scope isn't displaying the full bandwidth of the input signal.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered 6 hours ago









            Dwayne ReidDwayne Reid

            18.2k21949




            18.2k21949





















                2












                $begingroup$

                Here is a test I did with my 200MHz Tek scope. You should be able to get similar results with the Rigol, this is an older scope with a modest 2Gs/s capture frequency.



                My circuit is just a standard 10:1 probe connected across a 6mm tact switch with a 1K pullup to +5V supply.



                enter image description here



                Not all the captures were this messy, some were pretty ideal looking. Pushing it hard seemed to lead to more messiness. There's a bit of ringing despite a bypass across the power supply- that falling edge due to the switch contacts closing is very fast.



                If I set the sweep too slow (and then expand) I just get interpolation between samples, which might be misleading. There's no information there so the scope fakes it.



                Capture was single event, triggered by falling edge on the active channel, set relatively close to the 5V level (the yellow arrow on the right indicates the trigger level of 3.68V). The center of the screen is at -96ns (moved to view a bit more of the pre-trigger data since most of the action is pre-trigger).






                share|improve this answer









                $endgroup$

















                  2












                  $begingroup$

                  Here is a test I did with my 200MHz Tek scope. You should be able to get similar results with the Rigol, this is an older scope with a modest 2Gs/s capture frequency.



                  My circuit is just a standard 10:1 probe connected across a 6mm tact switch with a 1K pullup to +5V supply.



                  enter image description here



                  Not all the captures were this messy, some were pretty ideal looking. Pushing it hard seemed to lead to more messiness. There's a bit of ringing despite a bypass across the power supply- that falling edge due to the switch contacts closing is very fast.



                  If I set the sweep too slow (and then expand) I just get interpolation between samples, which might be misleading. There's no information there so the scope fakes it.



                  Capture was single event, triggered by falling edge on the active channel, set relatively close to the 5V level (the yellow arrow on the right indicates the trigger level of 3.68V). The center of the screen is at -96ns (moved to view a bit more of the pre-trigger data since most of the action is pre-trigger).






                  share|improve this answer









                  $endgroup$















                    2












                    2








                    2





                    $begingroup$

                    Here is a test I did with my 200MHz Tek scope. You should be able to get similar results with the Rigol, this is an older scope with a modest 2Gs/s capture frequency.



                    My circuit is just a standard 10:1 probe connected across a 6mm tact switch with a 1K pullup to +5V supply.



                    enter image description here



                    Not all the captures were this messy, some were pretty ideal looking. Pushing it hard seemed to lead to more messiness. There's a bit of ringing despite a bypass across the power supply- that falling edge due to the switch contacts closing is very fast.



                    If I set the sweep too slow (and then expand) I just get interpolation between samples, which might be misleading. There's no information there so the scope fakes it.



                    Capture was single event, triggered by falling edge on the active channel, set relatively close to the 5V level (the yellow arrow on the right indicates the trigger level of 3.68V). The center of the screen is at -96ns (moved to view a bit more of the pre-trigger data since most of the action is pre-trigger).






                    share|improve this answer









                    $endgroup$



                    Here is a test I did with my 200MHz Tek scope. You should be able to get similar results with the Rigol, this is an older scope with a modest 2Gs/s capture frequency.



                    My circuit is just a standard 10:1 probe connected across a 6mm tact switch with a 1K pullup to +5V supply.



                    enter image description here



                    Not all the captures were this messy, some were pretty ideal looking. Pushing it hard seemed to lead to more messiness. There's a bit of ringing despite a bypass across the power supply- that falling edge due to the switch contacts closing is very fast.



                    If I set the sweep too slow (and then expand) I just get interpolation between samples, which might be misleading. There's no information there so the scope fakes it.



                    Capture was single event, triggered by falling edge on the active channel, set relatively close to the 5V level (the yellow arrow on the right indicates the trigger level of 3.68V). The center of the screen is at -96ns (moved to view a bit more of the pre-trigger data since most of the action is pre-trigger).







                    share|improve this answer












                    share|improve this answer



                    share|improve this answer










                    answered 1 hour ago









                    Spehro PefhanySpehro Pefhany

                    213k5162429




                    213k5162429





















                        -1












                        $begingroup$

                        Use an old switch or store your new switch in a mixture of salt water and vinegar for a few hours. That will corrode the contacts and increase the bounce.






                        share|improve this answer










                        New contributor




                        ron is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                        Check out our Code of Conduct.






                        $endgroup$

















                          -1












                          $begingroup$

                          Use an old switch or store your new switch in a mixture of salt water and vinegar for a few hours. That will corrode the contacts and increase the bounce.






                          share|improve this answer










                          New contributor




                          ron is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                          Check out our Code of Conduct.






                          $endgroup$















                            -1












                            -1








                            -1





                            $begingroup$

                            Use an old switch or store your new switch in a mixture of salt water and vinegar for a few hours. That will corrode the contacts and increase the bounce.






                            share|improve this answer










                            New contributor




                            ron is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                            Check out our Code of Conduct.






                            $endgroup$



                            Use an old switch or store your new switch in a mixture of salt water and vinegar for a few hours. That will corrode the contacts and increase the bounce.







                            share|improve this answer










                            New contributor




                            ron is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                            Check out our Code of Conduct.









                            share|improve this answer



                            share|improve this answer








                            edited 2 hours ago









                            Peter Mortensen

                            1,60031422




                            1,60031422






                            New contributor




                            ron is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                            Check out our Code of Conduct.









                            answered 4 hours ago









                            ronron

                            1




                            1




                            New contributor




                            ron is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                            Check out our Code of Conduct.





                            New contributor





                            ron is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                            Check out our Code of Conduct.






                            ron is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                            Check out our Code of Conduct.





















                                -2












                                $begingroup$

                                I have gone thru the answers mentioned above.



                                But First, please change your oscilloscope.



                                The scope you are using would have a shallow memory.(Acquisition Memory ...may be 1K or a few K memory).
                                Try with Deep Memory Scopes.Tektronix TDS 3000 or 4000 series , Keysight DSOx 3000 to 6000 series or many more brands and models are available.



                                You will definitely get a beautiful contact bounce ringing at the top the vertical rising/ falling edges.



                                The number of ringing edges is proportional to the length of your grounding wire length.Less the length, less ringing.The more the length, more ringing.



                                The Deep Memory scopes will contain record length or Acquisition memory in terms of Mb ....say 2Mb , 4Mb, 8Mb etc......Don't worry about Sampling rates. Deep memory will control to sustain the sampling rate.



                                I have captured enough time these switching circuits,in Deep memory scopes.



                                Try ...



                                Best Regards
                                A Senthil






                                share|improve this answer








                                New contributor




                                A Senthil is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                Check out our Code of Conduct.






                                $endgroup$








                                • 10




                                  $begingroup$
                                  The instrument in use is orders or magnitude more than sufficient if used properly. Recommending the purchase of new gear over learning to use the ordinary and suitable gear at hand is the mark of those who do not know what they are doing. There exists a capture rate, within the capability of that scope where the bouncing of the actual contacts is easily represented on the screen alone, nevermind any off-screen memory.
                                  $endgroup$
                                  – Chris Stratton
                                  4 hours ago
















                                -2












                                $begingroup$

                                I have gone thru the answers mentioned above.



                                But First, please change your oscilloscope.



                                The scope you are using would have a shallow memory.(Acquisition Memory ...may be 1K or a few K memory).
                                Try with Deep Memory Scopes.Tektronix TDS 3000 or 4000 series , Keysight DSOx 3000 to 6000 series or many more brands and models are available.



                                You will definitely get a beautiful contact bounce ringing at the top the vertical rising/ falling edges.



                                The number of ringing edges is proportional to the length of your grounding wire length.Less the length, less ringing.The more the length, more ringing.



                                The Deep Memory scopes will contain record length or Acquisition memory in terms of Mb ....say 2Mb , 4Mb, 8Mb etc......Don't worry about Sampling rates. Deep memory will control to sustain the sampling rate.



                                I have captured enough time these switching circuits,in Deep memory scopes.



                                Try ...



                                Best Regards
                                A Senthil






                                share|improve this answer








                                New contributor




                                A Senthil is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                Check out our Code of Conduct.






                                $endgroup$








                                • 10




                                  $begingroup$
                                  The instrument in use is orders or magnitude more than sufficient if used properly. Recommending the purchase of new gear over learning to use the ordinary and suitable gear at hand is the mark of those who do not know what they are doing. There exists a capture rate, within the capability of that scope where the bouncing of the actual contacts is easily represented on the screen alone, nevermind any off-screen memory.
                                  $endgroup$
                                  – Chris Stratton
                                  4 hours ago














                                -2












                                -2








                                -2





                                $begingroup$

                                I have gone thru the answers mentioned above.



                                But First, please change your oscilloscope.



                                The scope you are using would have a shallow memory.(Acquisition Memory ...may be 1K or a few K memory).
                                Try with Deep Memory Scopes.Tektronix TDS 3000 or 4000 series , Keysight DSOx 3000 to 6000 series or many more brands and models are available.



                                You will definitely get a beautiful contact bounce ringing at the top the vertical rising/ falling edges.



                                The number of ringing edges is proportional to the length of your grounding wire length.Less the length, less ringing.The more the length, more ringing.



                                The Deep Memory scopes will contain record length or Acquisition memory in terms of Mb ....say 2Mb , 4Mb, 8Mb etc......Don't worry about Sampling rates. Deep memory will control to sustain the sampling rate.



                                I have captured enough time these switching circuits,in Deep memory scopes.



                                Try ...



                                Best Regards
                                A Senthil






                                share|improve this answer








                                New contributor




                                A Senthil is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                Check out our Code of Conduct.






                                $endgroup$



                                I have gone thru the answers mentioned above.



                                But First, please change your oscilloscope.



                                The scope you are using would have a shallow memory.(Acquisition Memory ...may be 1K or a few K memory).
                                Try with Deep Memory Scopes.Tektronix TDS 3000 or 4000 series , Keysight DSOx 3000 to 6000 series or many more brands and models are available.



                                You will definitely get a beautiful contact bounce ringing at the top the vertical rising/ falling edges.



                                The number of ringing edges is proportional to the length of your grounding wire length.Less the length, less ringing.The more the length, more ringing.



                                The Deep Memory scopes will contain record length or Acquisition memory in terms of Mb ....say 2Mb , 4Mb, 8Mb etc......Don't worry about Sampling rates. Deep memory will control to sustain the sampling rate.



                                I have captured enough time these switching circuits,in Deep memory scopes.



                                Try ...



                                Best Regards
                                A Senthil







                                share|improve this answer








                                New contributor




                                A Senthil is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                Check out our Code of Conduct.









                                share|improve this answer



                                share|improve this answer






                                New contributor




                                A Senthil is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                Check out our Code of Conduct.









                                answered 4 hours ago









                                A SenthilA Senthil

                                1




                                1




                                New contributor




                                A Senthil is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                Check out our Code of Conduct.





                                New contributor





                                A Senthil is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                Check out our Code of Conduct.






                                A Senthil is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                Check out our Code of Conduct.







                                • 10




                                  $begingroup$
                                  The instrument in use is orders or magnitude more than sufficient if used properly. Recommending the purchase of new gear over learning to use the ordinary and suitable gear at hand is the mark of those who do not know what they are doing. There exists a capture rate, within the capability of that scope where the bouncing of the actual contacts is easily represented on the screen alone, nevermind any off-screen memory.
                                  $endgroup$
                                  – Chris Stratton
                                  4 hours ago













                                • 10




                                  $begingroup$
                                  The instrument in use is orders or magnitude more than sufficient if used properly. Recommending the purchase of new gear over learning to use the ordinary and suitable gear at hand is the mark of those who do not know what they are doing. There exists a capture rate, within the capability of that scope where the bouncing of the actual contacts is easily represented on the screen alone, nevermind any off-screen memory.
                                  $endgroup$
                                  – Chris Stratton
                                  4 hours ago








                                10




                                10




                                $begingroup$
                                The instrument in use is orders or magnitude more than sufficient if used properly. Recommending the purchase of new gear over learning to use the ordinary and suitable gear at hand is the mark of those who do not know what they are doing. There exists a capture rate, within the capability of that scope where the bouncing of the actual contacts is easily represented on the screen alone, nevermind any off-screen memory.
                                $endgroup$
                                – Chris Stratton
                                4 hours ago





                                $begingroup$
                                The instrument in use is orders or magnitude more than sufficient if used properly. Recommending the purchase of new gear over learning to use the ordinary and suitable gear at hand is the mark of those who do not know what they are doing. There exists a capture rate, within the capability of that scope where the bouncing of the actual contacts is easily represented on the screen alone, nevermind any off-screen memory.
                                $endgroup$
                                – Chris Stratton
                                4 hours ago






                                protected by Nick Alexeev 2 hours ago



                                Thank you for your interest in this question.
                                Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



                                Would you like to answer one of these unanswered questions instead?



                                Popular posts from this blog

                                Magento 2 duplicate PHPSESSID cookie when using session_start() in custom php scriptMagento 2: User cant logged in into to account page, no error showing!Magento duplicate on subdomainGrabbing storeview from cookie (after using language selector)How do I run php custom script on magento2Magento 2: Include PHP script in headerSession lock after using Cm_RedisSessionscript php to update stockMagento set cookie popupMagento 2 session id cookie - where to find it?How to import Configurable product from csv with custom attributes using php scriptMagento 2 run custom PHP script

                                Can not update quote_id field of “quote_item” table magento 2Magento 2.1 - We can't remove the item. (Shopping Cart doesnt allow us to remove items before becomes empty)Add value for custom quote item attribute using REST apiREST API endpoint v1/carts/cartId/items always returns error messageCorrect way to save entries to databaseHow to remove all associated quote objects of a customer completelyMagento 2 - Save value from custom input field to quote_itemGet quote_item data using quote id and product id filter in Magento 2How to set additional data to quote_item table from controller in Magento 2?What is the purpose of additional_data column in quote_item table in magento2Set Custom Price to Quote item magento2 from controller

                                How to solve knockout JS error in Magento 2 Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?(Magento2) knockout.js:3012 Uncaught ReferenceError: Unable to process bindingUnable to process binding Knockout.js magento 2Cannot read property `scopeLabel` of undefined on Product Detail PageCan't get Customer Data on frontend in Magento 2Magento2 Order Summary - unable to process bindingKO templates are not loading in Magento 2.1 applicationgetting knockout js error magento 2Product grid not load -— Unable to process binding Knockout.js magento 2Product form not loaded in magento2Uncaught ReferenceError: Unable to process binding “if: function()return (isShowLegend()) ” magento 2