Why can't I see bouncing of a switch on an oscilloscope? The 2019 Stack Overflow Developer Survey Results Are Inoscilloscope dead?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?Why do I see multiple waveforms on my oscilloscope in normal trigger mode?Bouncing at some points in square waveFrequency of contact bouncing
Dropping list elements from nested list after evaluation
Flight paths in orbit around Ceres?
Why can't devices on different VLANs, but on the same subnet, communicate?
Is it possible for absolutely everyone to attain enlightenment?
Is it okay to consider publishing in my first year of PhD?
Did the UK government pay "millions and millions of dollars" to try to snag Julian Assange?
What is the meaning of Triage in Cybersec world?
What is the most efficient way to store a numeric range?
What's the name of these plastic connectors
Button changing its text & action. Good or terrible?
Did any laptop computers have a built-in 5 1/4 inch floppy drive?
Can there be female White Walkers?
Is an up-to-date browser secure on an out-of-date OS?
writing variables above the numbers in tikz picture
Straighten subgroup lattice
Is one supposed to eat the zero'ah (shank bone) from the Seder plate?
How to translate "being like"?
Did Scotland spend $250,000 for the slogan "Welcome to Scotland"?
Is bread bad for ducks?
If I can cast sorceries at instant speed, can I use sorcery-speed activated abilities at instant speed?
Can you cast a spell on someone in the Ethereal Plane, if you are on the Material Plane and have the True Seeing spell active?
Is it safe to harvest rainwater that fell on solar panels?
Why isn't the circumferential light around the M87 black hole's event horizon symmetric?
How to type a long/em dash `—`
Why can't I see bouncing of a switch on an oscilloscope?
The 2019 Stack Overflow Developer Survey Results Are Inoscilloscope dead?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?Why 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;
$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.
Why can't I catch bouncing of the switch on the scope? I don't think it this is a non-bouncing switch.
Here is a photo showing a zoomed-in time scale (50 µs/div). As you can see, it is rising from 0 V to 9 V within 150 µs and staying there. I have tried a few different switches. The resistor in the picture is 220 ohm, 0.5 watt.
switches oscilloscope debounce
edited Apr 6 at 8:01
Peter Mortensen
1,60031422
asked Apr 5 at 19:27
DenizDeniz
19816
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$
|
show 16 more comments
$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.
Why can't I catch bouncing of the switch on the scope? I don't think it this is a non-bouncing switch.
Here is a photo showing a zoomed-in time scale (50 µs/div). As you can see, it is rising from 0 V to 9 V within 150 µs and staying there. I have tried a few different switches. The resistor in the picture is 220 ohm, 0.5 watt.
switches oscilloscope debounce
edited Apr 6 at 8:01
Peter Mortensen
1,60031422
asked Apr 5 at 19:27
DenizDeniz
19816
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$
13
$begingroup$
Have you tried adjusting the time base / horizontal scale?
$endgroup$
– NMF
Apr 5 at 19:31
22
$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
Apr 5 at 20:12
3
$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
Apr 5 at 20:21
5
$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
Apr 5 at 21:18
2
$begingroup$
Related: A Guide to Debouncing (PDF). (As HTML - part 1 and part 2). "Bounces of under 100 nsec were common"
$endgroup$
– Peter Mortensen
Apr 6 at 2:10
|
show 16 more comments
$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.
Why can't I catch bouncing of the switch on the scope? I don't think it this is a non-bouncing switch.
Here is a photo showing a zoomed-in time scale (50 µs/div). As you can see, it is rising from 0 V to 9 V within 150 µs and staying there. I have tried a few different switches. The resistor in the picture is 220 ohm, 0.5 watt.
switches oscilloscope debounce
edited Apr 6 at 8:01
Peter Mortensen
1,60031422
asked Apr 5 at 19:27
DenizDeniz
19816
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.
Why can't I catch bouncing of the switch on the scope? I don't think it this is a non-bouncing switch.
Here is a photo showing a zoomed-in time scale (50 µs/div). As you can see, it is rising from 0 V to 9 V within 150 µs and staying there. I have tried a few different switches. The resistor in the picture is 220 ohm, 0.5 watt.
switches oscilloscope debounce
switches oscilloscope debounce
edited Apr 6 at 8:01
Peter Mortensen
1,60031422
asked Apr 5 at 19:27
DenizDeniz
19816
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.
edited Apr 6 at 8:01
Peter Mortensen
1,60031422
asked Apr 5 at 19:27
DenizDeniz
19816
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.
edited Apr 6 at 8:01
Peter Mortensen
1,60031422
edited Apr 6 at 8:01
Peter Mortensen
1,60031422
edited Apr 6 at 8:01
Peter Mortensen
1,60031422
1,60031422
asked Apr 5 at 19:27
DenizDeniz
19816
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 Apr 5 at 19:27
DenizDeniz
19816
asked Apr 5 at 19:27
DenizDeniz
19816
19816
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.
13
$begingroup$
Have you tried adjusting the time base / horizontal scale?
$endgroup$
– NMF
Apr 5 at 19:31
22
$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
Apr 5 at 20:12
3
$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
Apr 5 at 20:21
5
$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
Apr 5 at 21:18
2
$begingroup$
Related: A Guide to Debouncing (PDF). (As HTML - part 1 and part 2). "Bounces of under 100 nsec were common"
$endgroup$
– Peter Mortensen
Apr 6 at 2:10
|
show 16 more comments
13
$begingroup$
Have you tried adjusting the time base / horizontal scale?
$endgroup$
– NMF
Apr 5 at 19:31
22
$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
Apr 5 at 20:12
3
$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
Apr 5 at 20:21
5
$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
Apr 5 at 21:18
2
$begingroup$
Related: A Guide to Debouncing (PDF). (As HTML - part 1 and part 2). "Bounces of under 100 nsec were common"
$endgroup$
– Peter Mortensen
Apr 6 at 2:10
13
13
$begingroup$
Have you tried adjusting the time base / horizontal scale?
$endgroup$
– NMF
Apr 5 at 19:31
$begingroup$
Have you tried adjusting the time base / horizontal scale?
$endgroup$
– NMF
Apr 5 at 19:31
22
22
$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
Apr 5 at 20:12
$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
Apr 5 at 20:12
3
3
$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
Apr 5 at 20:21
$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
Apr 5 at 20:21
5
5
$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
Apr 5 at 21:18
$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
Apr 5 at 21:18
2
2
$begingroup$
Related: A Guide to Debouncing (PDF). (As HTML - part 1 and part 2). "Bounces of under 100 nsec were common"
$endgroup$
– Peter Mortensen
Apr 6 at 2:10
$begingroup$
Related: A Guide to Debouncing (PDF). (As HTML - part 1 and part 2). "Bounces of under 100 nsec were common"
$endgroup$
– Peter Mortensen
Apr 6 at 2:10
|
show 16 more comments
5 Answers
5
active
oldest
votes
$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.
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).
answered Apr 6 at 3:43
Spehro PefhanySpehro Pefhany
213k5162432
$endgroup$
1
$begingroup$
Setting trigger level close to 5v really helped. It triggers early and allow capturing more of what happened just after first contact.
$endgroup$
– Deniz
Apr 7 at 13:57
1
$begingroup$
@Deniz you may find in some situations that triggering near the steady state voltage can cause mistriggers depending on electrical noise. since the transition is quick, an alternative is to move the trigger offset (horizontal offset) to the left. On a pre-existing capture this has the effect of "clipping" the signal horizontally and may look undesirable, but on retrigger the scope starts shifts the capture so the trigger point is at say 10% instead of strictly halfway. On certain captures sacrificing half your buffer to the pretrigger is undesirable
$endgroup$
– crasic
Apr 8 at 0:14
add a comment |
$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.
answered Apr 5 at 19:36
bitsmackbitsmack
12k73678
$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
Apr 5 at 19:59
12
$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
Apr 5 at 20:04
12
$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
Apr 5 at 20:22
3
$begingroup$
@Deniz To convince oneself, switch the scope display mode to points if possible
$endgroup$
– crasic
Apr 6 at 2:16
add a comment |
$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:
- Set trigger to edge (up) and trigger level at approximately half scale of your button voltage
- (Optional) Move the trigger (horizontal) offset to the left hand of screen to maximize the portion of capture after trigger
- Switch trigger to "normal" and "single mode" to arm the trigger for a single capture
- Press your button
- If you use continuous trigger you will get a new capture with every button press
- 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.
edited Apr 6 at 4:34
Peter Mortensen
1,60031422
answered Apr 5 at 22:37
crasiccrasic
3,194927
$endgroup$
$begingroup$
+1! Much more informative than my answer :)
$endgroup$
– bitsmack
Apr 6 at 1:41
add a comment |
$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.
answered Apr 5 at 23:01
Dwayne ReidDwayne Reid
18.2k21949
$endgroup$
add a comment |
$begingroup$
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.
answered Apr 5 at 19:35
TransistorTransistor
88.5k785190
$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
Apr 5 at 19:59
5
$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
Apr 5 at 20:25
add a comment |
protected by Nick Alexeev♦ Apr 6 at 3:18
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?
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
$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.
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).
answered Apr 6 at 3:43
Spehro PefhanySpehro Pefhany
213k5162432
$endgroup$
1
$begingroup$
Setting trigger level close to 5v really helped. It triggers early and allow capturing more of what happened just after first contact.
$endgroup$
– Deniz
Apr 7 at 13:57
1
$begingroup$
@Deniz you may find in some situations that triggering near the steady state voltage can cause mistriggers depending on electrical noise. since the transition is quick, an alternative is to move the trigger offset (horizontal offset) to the left. On a pre-existing capture this has the effect of "clipping" the signal horizontally and may look undesirable, but on retrigger the scope starts shifts the capture so the trigger point is at say 10% instead of strictly halfway. On certain captures sacrificing half your buffer to the pretrigger is undesirable
$endgroup$
– crasic
Apr 8 at 0:14
add a comment |
$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.
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).
answered Apr 6 at 3:43
Spehro PefhanySpehro Pefhany
213k5162432
$endgroup$
1
$begingroup$
Setting trigger level close to 5v really helped. It triggers early and allow capturing more of what happened just after first contact.
$endgroup$
– Deniz
Apr 7 at 13:57
1
$begingroup$
@Deniz you may find in some situations that triggering near the steady state voltage can cause mistriggers depending on electrical noise. since the transition is quick, an alternative is to move the trigger offset (horizontal offset) to the left. On a pre-existing capture this has the effect of "clipping" the signal horizontally and may look undesirable, but on retrigger the scope starts shifts the capture so the trigger point is at say 10% instead of strictly halfway. On certain captures sacrificing half your buffer to the pretrigger is undesirable
$endgroup$
– crasic
Apr 8 at 0:14
add a comment |
$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.
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).
answered Apr 6 at 3:43
Spehro PefhanySpehro Pefhany
213k5162432
$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.
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).
answered Apr 6 at 3:43
Spehro PefhanySpehro Pefhany
213k5162432
answered Apr 6 at 3:43
Spehro PefhanySpehro Pefhany
213k5162432
answered Apr 6 at 3:43
Spehro PefhanySpehro Pefhany
213k5162432
answered Apr 6 at 3:43
Spehro PefhanySpehro Pefhany
213k5162432
213k5162432
1
$begingroup$
Setting trigger level close to 5v really helped. It triggers early and allow capturing more of what happened just after first contact.
$endgroup$
– Deniz
Apr 7 at 13:57
1
$begingroup$
@Deniz you may find in some situations that triggering near the steady state voltage can cause mistriggers depending on electrical noise. since the transition is quick, an alternative is to move the trigger offset (horizontal offset) to the left. On a pre-existing capture this has the effect of "clipping" the signal horizontally and may look undesirable, but on retrigger the scope starts shifts the capture so the trigger point is at say 10% instead of strictly halfway. On certain captures sacrificing half your buffer to the pretrigger is undesirable
$endgroup$
– crasic
Apr 8 at 0:14
add a comment |
1
$begingroup$
Setting trigger level close to 5v really helped. It triggers early and allow capturing more of what happened just after first contact.
$endgroup$
– Deniz
Apr 7 at 13:57
1
$begingroup$
@Deniz you may find in some situations that triggering near the steady state voltage can cause mistriggers depending on electrical noise. since the transition is quick, an alternative is to move the trigger offset (horizontal offset) to the left. On a pre-existing capture this has the effect of "clipping" the signal horizontally and may look undesirable, but on retrigger the scope starts shifts the capture so the trigger point is at say 10% instead of strictly halfway. On certain captures sacrificing half your buffer to the pretrigger is undesirable
$endgroup$
– crasic
Apr 8 at 0:14
1
1
$begingroup$
Setting trigger level close to 5v really helped. It triggers early and allow capturing more of what happened just after first contact.
$endgroup$
– Deniz
Apr 7 at 13:57
$begingroup$
Setting trigger level close to 5v really helped. It triggers early and allow capturing more of what happened just after first contact.
$endgroup$
– Deniz
Apr 7 at 13:57
1
1
$begingroup$
@Deniz you may find in some situations that triggering near the steady state voltage can cause mistriggers depending on electrical noise. since the transition is quick, an alternative is to move the trigger offset (horizontal offset) to the left. On a pre-existing capture this has the effect of "clipping" the signal horizontally and may look undesirable, but on retrigger the scope starts shifts the capture so the trigger point is at say 10% instead of strictly halfway. On certain captures sacrificing half your buffer to the pretrigger is undesirable
$endgroup$
– crasic
Apr 8 at 0:14
$begingroup$
@Deniz you may find in some situations that triggering near the steady state voltage can cause mistriggers depending on electrical noise. since the transition is quick, an alternative is to move the trigger offset (horizontal offset) to the left. On a pre-existing capture this has the effect of "clipping" the signal horizontally and may look undesirable, but on retrigger the scope starts shifts the capture so the trigger point is at say 10% instead of strictly halfway. On certain captures sacrificing half your buffer to the pretrigger is undesirable
$endgroup$
– crasic
Apr 8 at 0:14
add a comment |
$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.
answered Apr 5 at 19:36
bitsmackbitsmack
12k73678
$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
Apr 5 at 19:59
12
$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
Apr 5 at 20:04
12
$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
Apr 5 at 20:22
3
$begingroup$
@Deniz To convince oneself, switch the scope display mode to points if possible
$endgroup$
– crasic
Apr 6 at 2:16
add a comment |
$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.
answered Apr 5 at 19:36
bitsmackbitsmack
12k73678
$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
Apr 5 at 19:59
12
$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
Apr 5 at 20:04
12
$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
Apr 5 at 20:22
3
$begingroup$
@Deniz To convince oneself, switch the scope display mode to points if possible
$endgroup$
– crasic
Apr 6 at 2:16
add a comment |
$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.
answered Apr 5 at 19:36
bitsmackbitsmack
12k73678
$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.
answered Apr 5 at 19:36
bitsmackbitsmack
12k73678
edited Apr 5 at 20:30
answered Apr 5 at 19:36
bitsmackbitsmack
12k73678
answered Apr 5 at 19:36
bitsmackbitsmack
12k73678
answered Apr 5 at 19:36
bitsmackbitsmack
12k73678
12k73678
$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
Apr 5 at 19:59
12
$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
Apr 5 at 20:04
12
$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
Apr 5 at 20:22
3
$begingroup$
@Deniz To convince oneself, switch the scope display mode to points if possible
$endgroup$
– crasic
Apr 6 at 2:16
add a comment |
$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
Apr 5 at 19:59
12
$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
Apr 5 at 20:04
12
$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
Apr 5 at 20:22
3
$begingroup$
@Deniz To convince oneself, switch the scope display mode to points if possible
$endgroup$
– crasic
Apr 6 at 2:16
$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
Apr 5 at 19:59
$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
Apr 5 at 19:59
12
12
$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
Apr 5 at 20:04
$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
Apr 5 at 20:04
12
12
$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
Apr 5 at 20:22
$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
Apr 5 at 20:22
3
3
$begingroup$
@Deniz To convince oneself, switch the scope display mode to points if possible
$endgroup$
– crasic
Apr 6 at 2:16
$begingroup$
@Deniz To convince oneself, switch the scope display mode to points if possible
$endgroup$
– crasic
Apr 6 at 2:16
add a comment |
$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:
- Set trigger to edge (up) and trigger level at approximately half scale of your button voltage
- (Optional) Move the trigger (horizontal) offset to the left hand of screen to maximize the portion of capture after trigger
- Switch trigger to "normal" and "single mode" to arm the trigger for a single capture
- Press your button
- If you use continuous trigger you will get a new capture with every button press
- 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.
edited Apr 6 at 4:34
Peter Mortensen
1,60031422
answered Apr 5 at 22:37
crasiccrasic
3,194927
$endgroup$
$begingroup$
+1! Much more informative than my answer :)
$endgroup$
– bitsmack
Apr 6 at 1:41
add a comment |
$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:
- Set trigger to edge (up) and trigger level at approximately half scale of your button voltage
- (Optional) Move the trigger (horizontal) offset to the left hand of screen to maximize the portion of capture after trigger
- Switch trigger to "normal" and "single mode" to arm the trigger for a single capture
- Press your button
- If you use continuous trigger you will get a new capture with every button press
- 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.
edited Apr 6 at 4:34
Peter Mortensen
1,60031422
answered Apr 5 at 22:37
crasiccrasic
3,194927
$endgroup$
$begingroup$
+1! Much more informative than my answer :)
$endgroup$
– bitsmack
Apr 6 at 1:41
add a comment |
$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:
- Set trigger to edge (up) and trigger level at approximately half scale of your button voltage
- (Optional) Move the trigger (horizontal) offset to the left hand of screen to maximize the portion of capture after trigger
- Switch trigger to "normal" and "single mode" to arm the trigger for a single capture
- Press your button
- If you use continuous trigger you will get a new capture with every button press
- 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.
edited Apr 6 at 4:34
Peter Mortensen
1,60031422
answered Apr 5 at 22:37
crasiccrasic
3,194927
$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:
- Set trigger to edge (up) and trigger level at approximately half scale of your button voltage
- (Optional) Move the trigger (horizontal) offset to the left hand of screen to maximize the portion of capture after trigger
- Switch trigger to "normal" and "single mode" to arm the trigger for a single capture
- Press your button
- If you use continuous trigger you will get a new capture with every button press
- 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.
edited Apr 6 at 4:34
Peter Mortensen
1,60031422
answered Apr 5 at 22:37
crasiccrasic
3,194927
edited Apr 6 at 4:34
Peter Mortensen
1,60031422
edited Apr 6 at 4:34
Peter Mortensen
1,60031422
edited Apr 6 at 4:34
Peter Mortensen
1,60031422
1,60031422
answered Apr 5 at 22:37
crasiccrasic
3,194927
answered Apr 5 at 22:37
crasiccrasic
3,194927
answered Apr 5 at 22:37
crasiccrasic
3,194927
3,194927
$begingroup$
+1! Much more informative than my answer :)
$endgroup$
– bitsmack
Apr 6 at 1:41
add a comment |
$begingroup$
+1! Much more informative than my answer :)
$endgroup$
– bitsmack
Apr 6 at 1:41
$begingroup$
+1! Much more informative than my answer :)
$endgroup$
– bitsmack
Apr 6 at 1:41
$begingroup$
+1! Much more informative than my answer :)
$endgroup$
– bitsmack
Apr 6 at 1:41
add a comment |
$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.
answered Apr 5 at 23:01
Dwayne ReidDwayne Reid
18.2k21949
$endgroup$
add a comment |
$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.
answered Apr 5 at 23:01
Dwayne ReidDwayne Reid
18.2k21949
$endgroup$
add a comment |
$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.
answered Apr 5 at 23:01
Dwayne ReidDwayne Reid
18.2k21949
$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.
answered Apr 5 at 23:01
Dwayne ReidDwayne Reid
18.2k21949
answered Apr 5 at 23:01
Dwayne ReidDwayne Reid
18.2k21949
answered Apr 5 at 23:01
Dwayne ReidDwayne Reid
18.2k21949
answered Apr 5 at 23:01
Dwayne ReidDwayne Reid
18.2k21949
18.2k21949
add a comment |
add a comment |
$begingroup$
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.
answered Apr 5 at 19:35
TransistorTransistor
88.5k785190
$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
Apr 5 at 19:59
5
$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
Apr 5 at 20:25
add a comment |
$begingroup$
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.
answered Apr 5 at 19:35
TransistorTransistor
88.5k785190
$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
Apr 5 at 19:59
5
$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
Apr 5 at 20:25
add a comment |
$begingroup$
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.
answered Apr 5 at 19:35
TransistorTransistor
88.5k785190
$endgroup$
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.
answered Apr 5 at 19:35
TransistorTransistor
88.5k785190
answered Apr 5 at 19:35
TransistorTransistor
88.5k785190
answered Apr 5 at 19:35
TransistorTransistor
88.5k785190
answered Apr 5 at 19:35
TransistorTransistor
88.5k785190
88.5k785190
$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
Apr 5 at 19:59
5
$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
Apr 5 at 20:25
add a comment |
$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
Apr 5 at 19:59
5
$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
Apr 5 at 20:25
$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
Apr 5 at 19:59
$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
Apr 5 at 19:59
5
5
$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
Apr 5 at 20:25
$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
Apr 5 at 20:25
add a comment |
protected by Nick Alexeev♦ Apr 6 at 3:18
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?
13
$begingroup$
Have you tried adjusting the time base / horizontal scale?
$endgroup$
– NMF
Apr 5 at 19:31
22
$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
Apr 5 at 20:12
3
$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
Apr 5 at 20:21
5
$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
Apr 5 at 21:18
2
$begingroup$
Related: A Guide to Debouncing (PDF). (As HTML - part 1 and part 2). "Bounces of under 100 nsec were common"
$endgroup$
– Peter Mortensen
Apr 6 at 2:10