Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- TekScopes
- Messages
Search
Re: 485 super weak brightness control
What mine does is following
toggle quoted message
Show quoted text
1 2 5 they get shorter 10 is reset to the length of 1 20 is reset to the length of 2 50 is reset to the length of 5 100 is again rest to the length of 1 200 is reset to the length of 2 Could you measure for me width of B gate for each time setting? Say from 1ms to 1ns ? On Tue, 23 Mar 2021, 19:12 Raymond Domp Frank, <hewpatek@...> wrote:
On Tue, Mar 23, 2021 at 06:51 PM, Raymond Domp Frank wrote:should |
Re: 485 super weak brightness control
On Tue, Mar 23, 2021 at 06:51 PM, Raymond Domp Frank wrote:
From what I can see in your video, all B-gate times are ok from 1 ns/div down to 100ns/div. At longer times, B-gate is too long (belonging to 10x faster B-times). Raymond |
Re: 485 super weak brightness control
On Tue, Mar 23, 2021 at 06:58 PM, Ondrej Pavelka wrote:
Yeah, you used the 2467B (top one) for the latest video. I find the 2467B far less convenient for general use, especially re. brightness settings. Raymond |
Re: How to explain how negative feedback lowers noise?
Hi Keith,
toggle quoted message
Show quoted text
Don't conflate my being didactic with being angry. Email is a lousy medium because the reader will attach an emotion track based on scant clues. That is a noisy, error-prone process. That said, I would refer you to my initial response to the OP. Not surprisingly, I prefer my example to yours. I have taught feedback to a large collection of quite diverse audiences, and have settled on a particular set of explanations as a result of many pedagogical experiments.? I craft the particulars to match the background of the intended listener. It is very tricky to provide simple answers that also do not introduce fundamental errors. The reason I began my response with the quote, "You cannot control what you do not measure," is that many folks have heard it before, although likely in other contexts. Even if they are unfamiliar with it, it makes intuitive sense, and it captures the essence of what negative feedback is about: You need to measure the variable to be controlled. That's necessary (but not sufficient). So in that likely familiar quote is the notion of control based on some sort of measurement of the thing to be controlled, which also then implies the existence of some sort of reference that conveys when that control is successfully achieved. The example I offered was the thermostat. Everyone has one in the home. Everyone knows what it's supposed to do, even if the particulars of how it does what it does may be mysterious. It's a commonly encountered negative feedback system. All you have to do is point out a few of its features, and how they map to features of the quote. This simple answer to the OP's first question has all of the attributes that you enumerate, and has the added distinction of not introducing fundamental errors in the process. I teach a freshman class that has many non-EE/non-STEM students. They all grasp negative feedback's essence from the thermostat example. I had an occasion to test that explanation again this past term. And it triggers the right set of follow-on questions. The discussion about noise wasn't a digression unrelated to the first. A proper description of negative feedback, simple or not, should set one up for answering more sophisticated questions. A poor simple explanation will align neurons in a way that actively militates against an intuitive understanding of the OP's second question (or is it the first?). Once you've got the right block diagram implicitly or explicitly implanted in their crania, adding a couple more inputs (noise or signal) to the system poses no cognitive problem. If you haven't given them the right block diagram, answering the noise question becomes nigh impossible. So, mere simplicity is not a virtue. There's a lot of engineering that should go into crafting an answer that is both simple and correct. That kind of simple answer is scalable to address more sophisticated questions. I would go further and argue that a good simple answer stimulates precisely those types of question. A random simple answer is often a "lie that we tell to children" to get them to stop asking questions. That's bad enough, but even worse is that answering the more sophisticated questions that do get asked requires undoing the simple explanation. Why do this when there are demonstrably better alternatives? -- Cheers Tom -- Prof. Thomas H. Lee Allen Ctr., Rm. 205 350 Jane Stanford Way Stanford University Stanford, CA 94305-4070 On 3/23/2021 06:04, Keith wrote:
re: Negative Feedback example, etc. |
Re: 485 super weak brightness control
I have 2445B and 2467B
toggle quoted message
Show quoted text
I used 2445B thus far, less messing with intensity to take pictures On Tue, 23 Mar 2021, 18:56 Raymond Domp Frank, <hewpatek@...> wrote:
On Tue, Mar 23, 2021 at 06:51 PM, Raymond Domp Frank wrote:Just realised that's a 2467B..... |
Re: 485 super weak brightness control
On Tue, Mar 23, 2021 at 06:02 PM, Ozan wrote:
Gentlemen, First of all, in order to make life as easy as possible, it would help me/us if we would "standardise" our settings: - A-ramp at top - A-gate below that - B-gate below that again - Variable timebase knob in the "calibrated" position (pushed in) - Delay Time Position to minimum (0) - Observation 'scope (2465B?) in non-delayed mode - Trigger on A- gate trace My observations match Ozan's latest ones. Ondrej, Your observations re. B-gate in 1, 2, 5, 10 ns positions are as they should be. I guess at positions 5ns/div and faster, it says "A only" on the front plate but I guess it actually shows B. Raymond |
Re: 485 super weak brightness control
Take a look at the posted pictures:
toggle quoted message
Show quoted text
/g/TekScopes/album?id=262059 Latest 5 pictures for B sweep in 1ns/div to 20ns/div. As expected no change in B-gate from 1ns/div to 2ns/div, then B gate time increases. When B gate is more than 10ns/div, A gate also increases (as expected, A gate time >= B gate time). Ozan
|
Re: 485 super weak brightness control
On Tue, Mar 23, 2021 at 09:27 AM, Ondrej Pavelka wrote:
As far as I remember B-gate time stays the same from 1ns to 2ns (because of the reason I mentioned before) then increases at 5ns. I will look at what happens on my scope but I expect it should continue increasing. Ozan |
Re: 485 super weak brightness control
Here is a odd thing I observing with B gate. Is this normal? Basically I expect the pulse to be shortest at 1nS and gradually widen. What happens here it basically goes in circles instead. Looking at the width on your picture my B gate pulse width is correct at 1ns, corect at 2 and 5 but at 10ns us again the same length as 1nS and that can't be right? On Tue, 23 Mar 2021, 16:57 Ondrej Pavelka, <info@...> wrote: B cannot rotate any further, it's rock solid against lock. |
Re: How to explain how negative feedback lowers noise?
Here is my attempt to explain in a real-world example the concepts of negative feedback and whether or not it lowers noise.
toggle quoted message
Show quoted text
The is for my buddy Keith. I came up with a simple real-world example of negative feedback and noise. Imagine you are driving your car. There is a control system involved with keeping the car on the road. Your vision is the sensor that keeps track of whether or not you are driving on the road. If your car starts to deviate from the center of your lane, let¡¯s say you start to head toward the edge of the road on the right, you pick that up as you see the car headed toward the stripe on the right side of the road. Your control system, consisting of your eyes and your arms through the steering wheel, applies a correction in the OPPOSITE direction of the current output (wheel direction) which is negative feedback. Now let¡¯s say you are in your 4-wheel drive Jeep and the road is full of very large potholes which can have a tendency to throw the vehicle from one side to the other as you travel along. The potholes represent noise or distortion in your system. Now you can ignore the potholes and not correct for them, but your vehicle might go off the road as a result. Or, you can steer to correct for each pothole as you hit it (no anticipatory correction), applying negative feedback to your vehicle in an attempt to keep it on the road. By doing this, you are lowering the noise in terms of the path that the vehicle will take. Note that the potholes are essentially noise within the steering control loop and the effect on your vehicle¡¯s path will be reduced as corrections are applied ¨C negative feedback lowers noise in the loop. Let¡¯s get off the road with the potholes and back onto a smooth paved road. Now let¡¯s say your spouse is in the passenger seat and is ¡°helping¡± to navigate by giving you directions on where to go. Any errors in her directions that you follow essentially are noise on the input of your control system. Let¡¯s say your spouse told you to make a ¡°wrong¡± turn (or multiple wrong turns), which constitutes noise in the steering system input and none of your steering control system will lower that noise. So negative feedback in our steering control system won¡¯t help to lower noise because the noise is not in the control loop. Matt -----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Keith Sent: Tuesday, March 23, 2021 9:04 AM To: [email protected] Subject: Re: [TekScopes] How to explain how negative feedback lowers noise? re: Negative Feedback example, etc. Folks tell me that a gentle answer turns away wrath, so I hope this is a gentle reply. I mean it in that spirit. Tom, with respect to your criticism of my example, I would suggest that you do a quick review of the original post #1. Here is the pertinent part of it, for your convenience: Hi all, I'm trying to explain to people at my company (none of whom are EEs or statisticians) how negative feedback works in a system. That's one thing that I'm trying to get across, and I can't come up with an explanation of it in every day terms. All the examples I find in biology etc seem kind of dubious and not very straightforward - there's a lot of "trust me on this" as to why it's actually negative feedback and not some form of other regulation. What's a simple /physical/ negative feedback? This is question 1 in the OP...period. The core of it is simple. "...how negative feedback works in a system..." Only in the next sentence (not quoted above) does the OP then use the word "another", and only then does he bring up a second question about feedback and noise. So, the original post is really two questions. Question 1 is the issue of a real world example of negative feedback in a system. Question 2 is the interaction of feedback and noise. Nothing in my example is intended or stated to address that second question. I had nothing to add to that discussion, and so attempted to provide the OP with his example for question one. Now I admit that the use of the word "noise" in my example does unintentionally blur the line - since I say "noisy happy children". I see how that might cause confusion, so I will attempt to edit my post to remove that word. Thanks for that. But, to be clear here, my example was only intended to apply to question #1 in the OP. Question #1 was the only part for which I felt I had an example that met his requirements, specifically that it be; 1. "non technical" - (which I admit I assumed would mean for persons who have no electronic background) 2. use "everyday terms" (everyday means things that average people from all walks of life could grasp) 3. provide a "simple / physical / negative feedback" example. Of course every analogy breaks down at some point, but in learning and teaching, it is quite common to go from the simple to the complex in a series of stepped examples - first simple and familiar, and therefore necessarily incomplete at some level. Then more subtle, complex, and therefore more narrow and demanding in proofs and adherence to reality. Thanks for reading my reply in a mild spirit. I mean no disrespect, but at the moment I stand by my example (modified to remove the word "noisy" of course) as meeting the requirements of OP's question one only. Of course, if you see it differently, then perhaps we'll just have to agree to disagree on this one? In any case, thanks for your contributions to the forum. You're a valuable resource here. Warmly, Keith |
Re: 485 super weak brightness control
B cannot rotate any further, it's rock solid against lock.
toggle quoted message
Show quoted text
On Tue, 23 Mar 2021, 16:23 Ozan, <ozan_g@...> wrote:
Hi Ondrej, |
Re: 485 super weak brightness control
I can replicate your picture at free running BNC cables 50Ohm termination On Tue, 23 Mar 2021, 16:23 Ozan, <ozan_g@...> wrote:
Hi Ondrej, |
Re: 485 super weak brightness control
On Tue, Mar 23, 2021 at 04:23 PM, Ozan wrote:
If the B-switch setting is faster than the B-knob indicates and the switch is mechanically blocked beyond the 1ns/div setting, it wouldn't be possible to set the B-speed switch to indicate 1ns/div. In my earlier msg I was trying to say that it is easy to achieve an A/B interlocked situation with either A faster or slower than B: Loosen the B knob, lift it slightly, turn it either CW or CCW and tighten. Next, rotate switch position by B-knob, loosen it, put into interlocked position, push B knob down and tighten. Done! Ondrey correctly said that because of (highly likely) mechanical limits, while interlocked, the slowest and fastest A- and B-setting could not be chosen then though. Raymond |
Re: 485 super weak brightness control
Hi Ondrej,
Videos are very useful. I was surprised sweep and gate signals are not aligned but I think you are using different probes for each. Using a BNC cable for all of them will eliminate any mismatch. Just for reference here is what I had observed: /g/TekScopes/photo/262059/0?p=Created,,,20,2,0,0 Setup: Inputs were set to 50-ohm (used BNC-T plus termination for CH3). No signal input, free running. Raymond's question reminded me my earlier message: I read your reply about timebases being locked. You may already know that but you can pull the time/div knob and rotate clockwise to speed up B timebase compared to A timebase. In that position B is not locked to A, and you can check if B can be rotated past the 1ns/div setting. There is a lock mechanism that won't allow B slower than A, so don't force in that direction.Are you sure B sweep shaft is not rotated out of alignment? You can look at J1 (relay signal) and check it switches at .1us/.2us boundary. I will look at the video again an reply later, I wanted to catch you while it is still earlier in the evening. Ozan |
Re: 485 super weak brightness control
On Tue, Mar 23, 2021 at 02:48 PM, Ondrej Pavelka wrote:
Probably, didn't check that. You probably run against end points. I didn't check any further. You obviously know what you're doing... Raymond |
Re: 485 super weak brightness control
Wouldn't it correct itself at max and min setting? Both my shafts A and B
toggle quoted message
Show quoted text
can move from 0.5second to 1nS and no further and neither can rotate freely all the way around. There is a locking mechanism in the switch itself On Tue, 23 Mar 2021, 14:21 Raymond Domp Frank, <hewpatek@...> wrote:
On Tue, Mar 23, 2021 at 02:04 PM, Ondrej Pavelka wrote:Sorry to insist and no idea whether it matches any of your other symptoms |
Re: How to explain how negative feedback lowers noise?
As? a non-EE, maybe my take on this could be useful, because the OP was looking for a non-technical analogy or explanation. But it should still be accurate.
toggle quoted message
Show quoted text
The kids going into the house example does not work because the kids are the input - they are already noisy, so negative feedback that compares input to output would not eliminate it. Another way to say it is: nice quiet kids come into the house, other kids already in there yell at them and makes the once-quiet house noisy. The dad asks the noisy kids to stop and be just like the quiet kids, and the house stays quiet. I don't think this is such a simple, easy analogy, but it seems more accurate (the feedback is not truly instantaneous, for one thing). The key is that negative feedback makes a comparison between input and output, and subtracts what is not in the input. Unteaching is very difficult - as a researcher dealing with managers, I deal with that almost everyday. I hope I was gentle enough. On 3/23/2021 7:04 AM, Keith wrote:
re: Negative Feedback example, etc. |
Re: 485 super weak brightness control
On Tue, Mar 23, 2021 at 02:04 PM, Ondrej Pavelka wrote:
Sorry to insist and no idea whether it matches any of your other symptoms but on my 485, it's no problem repositioning the knob on its shaft so B runs 10x as fast as A while A and B knobs are interlocked. Raymond |
Re: How to explain how negative feedback lowers noise?
re: Negative Feedback example, etc.
Folks tell me that a gentle answer turns away wrath, so I hope this is a gentle reply. I mean it in that spirit. Tom, with respect to your criticism of my example, I would suggest that you do a quick review of the original post #1. Here is the pertinent part of it, for your convenience: Hi all, I'm trying to explain to people at my company (none of whom are EEs or statisticians) how negative feedback works in a system. That's one thing that I'm trying to get across, and I can't come up with an explanation of it in every day terms. All the examples I find in biology etc seem kind of dubious and not very straightforward - there's a lot of "trust me on this" as to why it's actually negative feedback and not some form of other regulation. What's a simple /physical/ negative feedback? This is question 1 in the OP...period. The core of it is simple. "...how negative feedback works in a system..." Only in the next sentence (not quoted above) does the OP then use the word "another", and only then does he bring up a second question about feedback and noise. So, the original post is really two questions. Question 1 is the issue of a real world example of negative feedback in a system. Question 2 is the interaction of feedback and noise. Nothing in my example is intended or stated to address that second question. I had nothing to add to that discussion, and so attempted to provide the OP with his example for question one. Now I admit that the use of the word "noise" in my example does unintentionally blur the line - since I say "noisy happy children". I see how that might cause confusion, so I will attempt to edit my post to remove that word. Thanks for that. But, to be clear here, my example was only intended to apply to question #1 in the OP. Question #1 was the only part for which I felt I had an example that met his requirements, specifically that it be; 1. "non technical" - (which I admit I assumed would mean for persons who have no electronic background) 2. use "everyday terms" (everyday means things that average people from all walks of life could grasp) 3. provide a "simple / physical / negative feedback" example. Of course every analogy breaks down at some point, but in learning and teaching, it is quite common to go from the simple to the complex in a series of stepped examples - first simple and familiar, and therefore necessarily incomplete at some level. Then more subtle, complex, and therefore more narrow and demanding in proofs and adherence to reality. Thanks for reading my reply in a mild spirit. I mean no disrespect, but at the moment I stand by my example (modified to remove the word "noisy" of course) as meeting the requirements of OP's question one only. Of course, if you see it differently, then perhaps we'll just have to agree to disagree on this one? In any case, thanks for your contributions to the forum. You're a valuable resource here. Warmly, Keith |
to navigate to use esc to dismiss