Nehtdx

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.

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 60hz 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 Tek the scope displays both the time per div and effective sample rate

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

Also note that analog bandwith (e..g "100Mhz ") does not directly related 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. What this means is 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 (e..g display the capture at 10us resolution but 1second after 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

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.

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.

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

Why would it bounce upon switching? Have u any L or C in your circuit that would cause damping, or say bouncing? No bouncing in pure resistive circuits when switched on.

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