Mixing
How to interpret a schematic in terms of input/output
Clash Royale CLAN TAG#URR8PPP
up vote
5
down vote
favorite
I am programmer who studies electronics for hobby (but a serious one, not just for fun). I consider myself to have a reasonable knowledge on digital electronics. For instance, I already described processors, simple GPUs, network cards, RAM controllers etc in VHDL and then to a FPGA. Regarding digital electronics, this is the kind of knowledge that I have so far.
Now, I want to improve my knowledge in analog electronics. So far, I have studied: transistors, bjt amplifiers, opamps, RLC circuits, passive and active filters, simple linear fonts and some classical ICs such as 555 for instance.
But what I still missing is the ability to read and understand an anolog circuit schematic in the following sense: when I see a digital circuit schematic, it is easy to identify where are the inputs and the outputs, how data flow through the circuit and how each stage transforms the input signal. For instance, the following image is easy to reason in terms of inputs and output.
But when reading an analog circuitry schematic, I can't, yet, divide the schematic in blocks/parts by myself even with careful studying. For instance, the following schematic (a SPMS):
Because of so many in series and parallel conections and because current can flow in both ways in some parts of circuits it is hard to me reason in terms of input and output.
So here is my question: is there a way to read and interpret analog circuit schematics in terms of input/output in the same way that is possible to digital schematics (logic gates, for instance)? Or for analog circuitry there is another way of reasoning about the circuit? In other words: is there a systematic way, an algorithmic way, to read and interpret analog schematics or each circuit requires an ad-hoc analysis? Is there an abstraction that electrical engineers use?
What I have tried so far: to reason about a circuit using the abstraction of signals; try to split a circuit in terms of buffers (because of the input/output impedance) but this hasn't worked well so far because: not all circuits have buffers or work with signals. I've also tried to split a circuit by first looking at the IC's and then the discrete components around it. Then I would go on the IC's datasheet and read for instructions there. But this also didn't work for all cases because not all circuits have ICs.
My goals are: given a schematic, try to identify functional blocks: filters, amplifiers etc and; to be able to design (for me this is the most important goal) schematics of such complexity as the SPMS above. So for both cases I need to understand how one stage is connected to another.
I beg your pardon if my question is a little vague. As I said, I am a programmer, not an electrical engineer and I still lack keywords and concepts. If possible, please help me to improve my question.
analog schematics
asked 2 hours ago
Hadley Siqueira
261
New contributor
Hadley Siqueira is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |Â
up vote
5
down vote
favorite
I am programmer who studies electronics for hobby (but a serious one, not just for fun). I consider myself to have a reasonable knowledge on digital electronics. For instance, I already described processors, simple GPUs, network cards, RAM controllers etc in VHDL and then to a FPGA. Regarding digital electronics, this is the kind of knowledge that I have so far.
Now, I want to improve my knowledge in analog electronics. So far, I have studied: transistors, bjt amplifiers, opamps, RLC circuits, passive and active filters, simple linear fonts and some classical ICs such as 555 for instance.
But what I still missing is the ability to read and understand an anolog circuit schematic in the following sense: when I see a digital circuit schematic, it is easy to identify where are the inputs and the outputs, how data flow through the circuit and how each stage transforms the input signal. For instance, the following image is easy to reason in terms of inputs and output.
But when reading an analog circuitry schematic, I can't, yet, divide the schematic in blocks/parts by myself even with careful studying. For instance, the following schematic (a SPMS):
Because of so many in series and parallel conections and because current can flow in both ways in some parts of circuits it is hard to me reason in terms of input and output.
So here is my question: is there a way to read and interpret analog circuit schematics in terms of input/output in the same way that is possible to digital schematics (logic gates, for instance)? Or for analog circuitry there is another way of reasoning about the circuit? In other words: is there a systematic way, an algorithmic way, to read and interpret analog schematics or each circuit requires an ad-hoc analysis? Is there an abstraction that electrical engineers use?
What I have tried so far: to reason about a circuit using the abstraction of signals; try to split a circuit in terms of buffers (because of the input/output impedance) but this hasn't worked well so far because: not all circuits have buffers or work with signals. I've also tried to split a circuit by first looking at the IC's and then the discrete components around it. Then I would go on the IC's datasheet and read for instructions there. But this also didn't work for all cases because not all circuits have ICs.
My goals are: given a schematic, try to identify functional blocks: filters, amplifiers etc and; to be able to design (for me this is the most important goal) schematics of such complexity as the SPMS above. So for both cases I need to understand how one stage is connected to another.
I beg your pardon if my question is a little vague. As I said, I am a programmer, not an electrical engineer and I still lack keywords and concepts. If possible, please help me to improve my question.
analog schematics
asked 2 hours ago
Hadley Siqueira
261
New contributor
Hadley Siqueira is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
This question is really too broad to answer effectively, other than "Go get a BS in EE". What might work is to pick a specific schematic and ask us to explain the thought process in trying to understand what it does.
– Olin Lathrop
1 hour ago
Thank you, @OlinLathrop. Let's suppose that I take a BS in EE. What courses are linked to my question? I don't intend to take an actual BS in EE now (maybe in the future), but I have time to read the literature that you may recommend
– Hadley Siqueira
1 hour ago
1
There is no specific "read a schematic" course. You gain experience, recognize blocks and possible simplifications, what can be ignored and what can not, and so on. There is no single answer to your question, it is a case by case thing. The only way to learn how to read schematics is... Read schematics, fail, learn, repeat.
– Vladimir Cravero
1 hour ago
@OlinLathrop, would you mind give me an example regarding, for instance, the Q1 transistor at the top-middle of the SPMS schematic? It is the Q1 whose base is connected to resistors R6, R7 and R8. There also a diode D3 and a capacitor C9. This is an example of a topology that I haven't see so far in my reading.
– Hadley Siqueira
1 min ago
add a comment |Â
up vote
5
down vote
favorite
up vote
5
down vote
favorite
I am programmer who studies electronics for hobby (but a serious one, not just for fun). I consider myself to have a reasonable knowledge on digital electronics. For instance, I already described processors, simple GPUs, network cards, RAM controllers etc in VHDL and then to a FPGA. Regarding digital electronics, this is the kind of knowledge that I have so far.
Now, I want to improve my knowledge in analog electronics. So far, I have studied: transistors, bjt amplifiers, opamps, RLC circuits, passive and active filters, simple linear fonts and some classical ICs such as 555 for instance.
But what I still missing is the ability to read and understand an anolog circuit schematic in the following sense: when I see a digital circuit schematic, it is easy to identify where are the inputs and the outputs, how data flow through the circuit and how each stage transforms the input signal. For instance, the following image is easy to reason in terms of inputs and output.
But when reading an analog circuitry schematic, I can't, yet, divide the schematic in blocks/parts by myself even with careful studying. For instance, the following schematic (a SPMS):
Because of so many in series and parallel conections and because current can flow in both ways in some parts of circuits it is hard to me reason in terms of input and output.
So here is my question: is there a way to read and interpret analog circuit schematics in terms of input/output in the same way that is possible to digital schematics (logic gates, for instance)? Or for analog circuitry there is another way of reasoning about the circuit? In other words: is there a systematic way, an algorithmic way, to read and interpret analog schematics or each circuit requires an ad-hoc analysis? Is there an abstraction that electrical engineers use?
What I have tried so far: to reason about a circuit using the abstraction of signals; try to split a circuit in terms of buffers (because of the input/output impedance) but this hasn't worked well so far because: not all circuits have buffers or work with signals. I've also tried to split a circuit by first looking at the IC's and then the discrete components around it. Then I would go on the IC's datasheet and read for instructions there. But this also didn't work for all cases because not all circuits have ICs.
My goals are: given a schematic, try to identify functional blocks: filters, amplifiers etc and; to be able to design (for me this is the most important goal) schematics of such complexity as the SPMS above. So for both cases I need to understand how one stage is connected to another.
I beg your pardon if my question is a little vague. As I said, I am a programmer, not an electrical engineer and I still lack keywords and concepts. If possible, please help me to improve my question.
analog schematics
asked 2 hours ago
Hadley Siqueira
261
New contributor
Hadley Siqueira is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I am programmer who studies electronics for hobby (but a serious one, not just for fun). I consider myself to have a reasonable knowledge on digital electronics. For instance, I already described processors, simple GPUs, network cards, RAM controllers etc in VHDL and then to a FPGA. Regarding digital electronics, this is the kind of knowledge that I have so far.
Now, I want to improve my knowledge in analog electronics. So far, I have studied: transistors, bjt amplifiers, opamps, RLC circuits, passive and active filters, simple linear fonts and some classical ICs such as 555 for instance.
But what I still missing is the ability to read and understand an anolog circuit schematic in the following sense: when I see a digital circuit schematic, it is easy to identify where are the inputs and the outputs, how data flow through the circuit and how each stage transforms the input signal. For instance, the following image is easy to reason in terms of inputs and output.
But when reading an analog circuitry schematic, I can't, yet, divide the schematic in blocks/parts by myself even with careful studying. For instance, the following schematic (a SPMS):
Because of so many in series and parallel conections and because current can flow in both ways in some parts of circuits it is hard to me reason in terms of input and output.
So here is my question: is there a way to read and interpret analog circuit schematics in terms of input/output in the same way that is possible to digital schematics (logic gates, for instance)? Or for analog circuitry there is another way of reasoning about the circuit? In other words: is there a systematic way, an algorithmic way, to read and interpret analog schematics or each circuit requires an ad-hoc analysis? Is there an abstraction that electrical engineers use?
What I have tried so far: to reason about a circuit using the abstraction of signals; try to split a circuit in terms of buffers (because of the input/output impedance) but this hasn't worked well so far because: not all circuits have buffers or work with signals. I've also tried to split a circuit by first looking at the IC's and then the discrete components around it. Then I would go on the IC's datasheet and read for instructions there. But this also didn't work for all cases because not all circuits have ICs.
My goals are: given a schematic, try to identify functional blocks: filters, amplifiers etc and; to be able to design (for me this is the most important goal) schematics of such complexity as the SPMS above. So for both cases I need to understand how one stage is connected to another.
I beg your pardon if my question is a little vague. As I said, I am a programmer, not an electrical engineer and I still lack keywords and concepts. If possible, please help me to improve my question.
analog schematics
analog schematics
asked 2 hours ago
Hadley Siqueira
261
New contributor
Hadley Siqueira is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 2 hours ago
Hadley Siqueira
261
New contributor
Hadley Siqueira is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 2 hours ago
Hadley Siqueira
261
New contributor
Hadley Siqueira is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 2 hours ago
Hadley Siqueira
261
asked 2 hours ago
Hadley Siqueira
261
261
New contributor
Hadley Siqueira is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Hadley Siqueira is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Hadley Siqueira is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
This question is really too broad to answer effectively, other than "Go get a BS in EE". What might work is to pick a specific schematic and ask us to explain the thought process in trying to understand what it does.
– Olin Lathrop
1 hour ago
Thank you, @OlinLathrop. Let's suppose that I take a BS in EE. What courses are linked to my question? I don't intend to take an actual BS in EE now (maybe in the future), but I have time to read the literature that you may recommend
– Hadley Siqueira
1 hour ago
1
There is no specific "read a schematic" course. You gain experience, recognize blocks and possible simplifications, what can be ignored and what can not, and so on. There is no single answer to your question, it is a case by case thing. The only way to learn how to read schematics is... Read schematics, fail, learn, repeat.
– Vladimir Cravero
1 hour ago
@OlinLathrop, would you mind give me an example regarding, for instance, the Q1 transistor at the top-middle of the SPMS schematic? It is the Q1 whose base is connected to resistors R6, R7 and R8. There also a diode D3 and a capacitor C9. This is an example of a topology that I haven't see so far in my reading.
– Hadley Siqueira
1 min ago
add a comment |Â
This question is really too broad to answer effectively, other than "Go get a BS in EE". What might work is to pick a specific schematic and ask us to explain the thought process in trying to understand what it does.
– Olin Lathrop
1 hour ago
Thank you, @OlinLathrop. Let's suppose that I take a BS in EE. What courses are linked to my question? I don't intend to take an actual BS in EE now (maybe in the future), but I have time to read the literature that you may recommend
– Hadley Siqueira
1 hour ago
1
There is no specific "read a schematic" course. You gain experience, recognize blocks and possible simplifications, what can be ignored and what can not, and so on. There is no single answer to your question, it is a case by case thing. The only way to learn how to read schematics is... Read schematics, fail, learn, repeat.
– Vladimir Cravero
1 hour ago
@OlinLathrop, would you mind give me an example regarding, for instance, the Q1 transistor at the top-middle of the SPMS schematic? It is the Q1 whose base is connected to resistors R6, R7 and R8. There also a diode D3 and a capacitor C9. This is an example of a topology that I haven't see so far in my reading.
– Hadley Siqueira
1 min ago
This question is really too broad to answer effectively, other than "Go get a BS in EE". What might work is to pick a specific schematic and ask us to explain the thought process in trying to understand what it does.
– Olin Lathrop
1 hour ago
This question is really too broad to answer effectively, other than "Go get a BS in EE". What might work is to pick a specific schematic and ask us to explain the thought process in trying to understand what it does.
– Olin Lathrop
1 hour ago
Thank you, @OlinLathrop. Let's suppose that I take a BS in EE. What courses are linked to my question? I don't intend to take an actual BS in EE now (maybe in the future), but I have time to read the literature that you may recommend
– Hadley Siqueira
1 hour ago
Thank you, @OlinLathrop. Let's suppose that I take a BS in EE. What courses are linked to my question? I don't intend to take an actual BS in EE now (maybe in the future), but I have time to read the literature that you may recommend
– Hadley Siqueira
1 hour ago
1
1
There is no specific "read a schematic" course. You gain experience, recognize blocks and possible simplifications, what can be ignored and what can not, and so on. There is no single answer to your question, it is a case by case thing. The only way to learn how to read schematics is... Read schematics, fail, learn, repeat.
– Vladimir Cravero
1 hour ago
There is no specific "read a schematic" course. You gain experience, recognize blocks and possible simplifications, what can be ignored and what can not, and so on. There is no single answer to your question, it is a case by case thing. The only way to learn how to read schematics is... Read schematics, fail, learn, repeat.
– Vladimir Cravero
1 hour ago
@OlinLathrop, would you mind give me an example regarding, for instance, the Q1 transistor at the top-middle of the SPMS schematic? It is the Q1 whose base is connected to resistors R6, R7 and R8. There also a diode D3 and a capacitor C9. This is an example of a topology that I haven't see so far in my reading.
– Hadley Siqueira
1 min ago
@OlinLathrop, would you mind give me an example regarding, for instance, the Q1 transistor at the top-middle of the SPMS schematic? It is the Q1 whose base is connected to resistors R6, R7 and R8. There also a diode D3 and a capacitor C9. This is an example of a topology that I haven't see so far in my reading.
– Hadley Siqueira
1 min ago
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
3
down vote
It's all about pattern identification, and you get that by looking at simpler schematics and then building up from there. Generally, people pick design patterns from a fairly limited set of options and so once you recognise a few you can start to get a sense of what parts of the design do. After that, you can "ignore" those and concentrate your efforts on understanding bits you don't know.
I often find a challenge is the actual layout of the schematic. For example, in your SMPS schematic, it's clearly made to fit tightly into a rectangular space so some patterns are not in their textbook arrangement. Practice, practice, practice, and ask here when you need some help :)
answered 2 hours ago
awjlogan
3,0181825
There is a lot more to it than pattern recognition. Patterns help to get you started when a schematic is well laid out, but in the end you still have to follow the signal paths and visualize the voltages pushing and the currents flowing.
– Olin Lathrop
1 hour ago
@OlinLathrop Absolutely, but as I said, it's about being able to reduce the "noise" and focus your attention on bits you don't understand.
– awjlogan
1 hour ago
add a comment |Â
up vote
2
down vote
The context to the schematic gives you the initial route into the circuit.
For instance, you have illustrated an SMPS. By definition, this takes a power input, and delivers a regulated DC output. You now have to scan the schematic, until you find the words 'INPUT FILTER' at the top left, and 'DC OUTPUT at the top right.
Within that circuit, there will be many blocks which individually have an input and an output, and are strung together to perform the overall function. Here the part identification is your friend, and after googling them a few times, you will get used to the numbers quickly. The TL494 and the 78L05 are a switch mode controller and a low power voltage regulator respectively. You read the data sheets for those, and they tell you what the parts do, and what the pin functions are.
The examples you've chosen for digital versus analogue are somewhat extreme. If you'd posted the schematic of an MCU, with busses going between RAM and ALU and peripherals and ... you get the general idea, no inputs or outputs obvious unless you know what you're looking for. The analogue equivalent in complexity for your ABC logic function would be somewhere between the TL494 and the 78L05. The SMPS equivalent would be the MCU.
Get used to the numbers, use google for the datasheets, decompose into functional blocks (like an SPI peripheral), start simple, and lots and lots of practice. It's perfectly normal for your head to explode when you get into a new field.
You might have studied opamps and 555s, but have you built anything from them? Electronics really is a practical discipline. If you don't want to get a breadboard and a DMM, then at least play with a circuit simulator. I read programming manuals and think I understand, but it's not until I've got something well beyond 'Hello World' working that I realise I didn't understand, and do now.
answered 1 hour ago
Neil_UK
70.1k273155
Thank you. I know the examples I gave differ on difficulty, but it is because it wasn't the main point. Regarding your example about MCU and RAM connection I am considering this part to be an analog one because of the usage of capacitors for filtering, for instance. Also, I agree with your suggestion but it doesn't always work to look for information in the schematic itself for named parts because it isn't always the case as is in this question: electronics.stackexchange.com/questions/387497/…)
– Hadley Siqueira
9 mins ago
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
It's all about pattern identification, and you get that by looking at simpler schematics and then building up from there. Generally, people pick design patterns from a fairly limited set of options and so once you recognise a few you can start to get a sense of what parts of the design do. After that, you can "ignore" those and concentrate your efforts on understanding bits you don't know.
I often find a challenge is the actual layout of the schematic. For example, in your SMPS schematic, it's clearly made to fit tightly into a rectangular space so some patterns are not in their textbook arrangement. Practice, practice, practice, and ask here when you need some help :)
answered 2 hours ago
awjlogan
3,0181825
There is a lot more to it than pattern recognition. Patterns help to get you started when a schematic is well laid out, but in the end you still have to follow the signal paths and visualize the voltages pushing and the currents flowing.
– Olin Lathrop
1 hour ago
@OlinLathrop Absolutely, but as I said, it's about being able to reduce the "noise" and focus your attention on bits you don't understand.
– awjlogan
1 hour ago
add a comment |Â
up vote
3
down vote
It's all about pattern identification, and you get that by looking at simpler schematics and then building up from there. Generally, people pick design patterns from a fairly limited set of options and so once you recognise a few you can start to get a sense of what parts of the design do. After that, you can "ignore" those and concentrate your efforts on understanding bits you don't know.
I often find a challenge is the actual layout of the schematic. For example, in your SMPS schematic, it's clearly made to fit tightly into a rectangular space so some patterns are not in their textbook arrangement. Practice, practice, practice, and ask here when you need some help :)
answered 2 hours ago
awjlogan
3,0181825
There is a lot more to it than pattern recognition. Patterns help to get you started when a schematic is well laid out, but in the end you still have to follow the signal paths and visualize the voltages pushing and the currents flowing.
– Olin Lathrop
1 hour ago
@OlinLathrop Absolutely, but as I said, it's about being able to reduce the "noise" and focus your attention on bits you don't understand.
– awjlogan
1 hour ago
add a comment |Â
up vote
3
down vote
up vote
3
down vote
It's all about pattern identification, and you get that by looking at simpler schematics and then building up from there. Generally, people pick design patterns from a fairly limited set of options and so once you recognise a few you can start to get a sense of what parts of the design do. After that, you can "ignore" those and concentrate your efforts on understanding bits you don't know.
I often find a challenge is the actual layout of the schematic. For example, in your SMPS schematic, it's clearly made to fit tightly into a rectangular space so some patterns are not in their textbook arrangement. Practice, practice, practice, and ask here when you need some help :)
answered 2 hours ago
awjlogan
3,0181825
It's all about pattern identification, and you get that by looking at simpler schematics and then building up from there. Generally, people pick design patterns from a fairly limited set of options and so once you recognise a few you can start to get a sense of what parts of the design do. After that, you can "ignore" those and concentrate your efforts on understanding bits you don't know.
I often find a challenge is the actual layout of the schematic. For example, in your SMPS schematic, it's clearly made to fit tightly into a rectangular space so some patterns are not in their textbook arrangement. Practice, practice, practice, and ask here when you need some help :)
answered 2 hours ago
awjlogan
3,0181825
edited 2 hours ago
answered 2 hours ago
awjlogan
3,0181825
answered 2 hours ago
awjlogan
3,0181825
answered 2 hours ago
awjlogan
3,0181825
3,0181825
There is a lot more to it than pattern recognition. Patterns help to get you started when a schematic is well laid out, but in the end you still have to follow the signal paths and visualize the voltages pushing and the currents flowing.
– Olin Lathrop
1 hour ago
@OlinLathrop Absolutely, but as I said, it's about being able to reduce the "noise" and focus your attention on bits you don't understand.
– awjlogan
1 hour ago
add a comment |Â
There is a lot more to it than pattern recognition. Patterns help to get you started when a schematic is well laid out, but in the end you still have to follow the signal paths and visualize the voltages pushing and the currents flowing.
– Olin Lathrop
1 hour ago
@OlinLathrop Absolutely, but as I said, it's about being able to reduce the "noise" and focus your attention on bits you don't understand.
– awjlogan
1 hour ago
There is a lot more to it than pattern recognition. Patterns help to get you started when a schematic is well laid out, but in the end you still have to follow the signal paths and visualize the voltages pushing and the currents flowing.
– Olin Lathrop
1 hour ago
There is a lot more to it than pattern recognition. Patterns help to get you started when a schematic is well laid out, but in the end you still have to follow the signal paths and visualize the voltages pushing and the currents flowing.
– Olin Lathrop
1 hour ago
@OlinLathrop Absolutely, but as I said, it's about being able to reduce the "noise" and focus your attention on bits you don't understand.
– awjlogan
1 hour ago
@OlinLathrop Absolutely, but as I said, it's about being able to reduce the "noise" and focus your attention on bits you don't understand.
– awjlogan
1 hour ago
add a comment |Â
up vote
2
down vote
The context to the schematic gives you the initial route into the circuit.
For instance, you have illustrated an SMPS. By definition, this takes a power input, and delivers a regulated DC output. You now have to scan the schematic, until you find the words 'INPUT FILTER' at the top left, and 'DC OUTPUT at the top right.
Within that circuit, there will be many blocks which individually have an input and an output, and are strung together to perform the overall function. Here the part identification is your friend, and after googling them a few times, you will get used to the numbers quickly. The TL494 and the 78L05 are a switch mode controller and a low power voltage regulator respectively. You read the data sheets for those, and they tell you what the parts do, and what the pin functions are.
The examples you've chosen for digital versus analogue are somewhat extreme. If you'd posted the schematic of an MCU, with busses going between RAM and ALU and peripherals and ... you get the general idea, no inputs or outputs obvious unless you know what you're looking for. The analogue equivalent in complexity for your ABC logic function would be somewhere between the TL494 and the 78L05. The SMPS equivalent would be the MCU.
Get used to the numbers, use google for the datasheets, decompose into functional blocks (like an SPI peripheral), start simple, and lots and lots of practice. It's perfectly normal for your head to explode when you get into a new field.
You might have studied opamps and 555s, but have you built anything from them? Electronics really is a practical discipline. If you don't want to get a breadboard and a DMM, then at least play with a circuit simulator. I read programming manuals and think I understand, but it's not until I've got something well beyond 'Hello World' working that I realise I didn't understand, and do now.
answered 1 hour ago
Neil_UK
70.1k273155
Thank you. I know the examples I gave differ on difficulty, but it is because it wasn't the main point. Regarding your example about MCU and RAM connection I am considering this part to be an analog one because of the usage of capacitors for filtering, for instance. Also, I agree with your suggestion but it doesn't always work to look for information in the schematic itself for named parts because it isn't always the case as is in this question: electronics.stackexchange.com/questions/387497/…)
– Hadley Siqueira
9 mins ago
add a comment |Â
up vote
2
down vote
The context to the schematic gives you the initial route into the circuit.
For instance, you have illustrated an SMPS. By definition, this takes a power input, and delivers a regulated DC output. You now have to scan the schematic, until you find the words 'INPUT FILTER' at the top left, and 'DC OUTPUT at the top right.
Within that circuit, there will be many blocks which individually have an input and an output, and are strung together to perform the overall function. Here the part identification is your friend, and after googling them a few times, you will get used to the numbers quickly. The TL494 and the 78L05 are a switch mode controller and a low power voltage regulator respectively. You read the data sheets for those, and they tell you what the parts do, and what the pin functions are.
The examples you've chosen for digital versus analogue are somewhat extreme. If you'd posted the schematic of an MCU, with busses going between RAM and ALU and peripherals and ... you get the general idea, no inputs or outputs obvious unless you know what you're looking for. The analogue equivalent in complexity for your ABC logic function would be somewhere between the TL494 and the 78L05. The SMPS equivalent would be the MCU.
Get used to the numbers, use google for the datasheets, decompose into functional blocks (like an SPI peripheral), start simple, and lots and lots of practice. It's perfectly normal for your head to explode when you get into a new field.
You might have studied opamps and 555s, but have you built anything from them? Electronics really is a practical discipline. If you don't want to get a breadboard and a DMM, then at least play with a circuit simulator. I read programming manuals and think I understand, but it's not until I've got something well beyond 'Hello World' working that I realise I didn't understand, and do now.
answered 1 hour ago
Neil_UK
70.1k273155
Thank you. I know the examples I gave differ on difficulty, but it is because it wasn't the main point. Regarding your example about MCU and RAM connection I am considering this part to be an analog one because of the usage of capacitors for filtering, for instance. Also, I agree with your suggestion but it doesn't always work to look for information in the schematic itself for named parts because it isn't always the case as is in this question: electronics.stackexchange.com/questions/387497/…)
– Hadley Siqueira
9 mins ago
add a comment |Â
up vote
2
down vote
up vote
2
down vote
The context to the schematic gives you the initial route into the circuit.
For instance, you have illustrated an SMPS. By definition, this takes a power input, and delivers a regulated DC output. You now have to scan the schematic, until you find the words 'INPUT FILTER' at the top left, and 'DC OUTPUT at the top right.
Within that circuit, there will be many blocks which individually have an input and an output, and are strung together to perform the overall function. Here the part identification is your friend, and after googling them a few times, you will get used to the numbers quickly. The TL494 and the 78L05 are a switch mode controller and a low power voltage regulator respectively. You read the data sheets for those, and they tell you what the parts do, and what the pin functions are.
The examples you've chosen for digital versus analogue are somewhat extreme. If you'd posted the schematic of an MCU, with busses going between RAM and ALU and peripherals and ... you get the general idea, no inputs or outputs obvious unless you know what you're looking for. The analogue equivalent in complexity for your ABC logic function would be somewhere between the TL494 and the 78L05. The SMPS equivalent would be the MCU.
Get used to the numbers, use google for the datasheets, decompose into functional blocks (like an SPI peripheral), start simple, and lots and lots of practice. It's perfectly normal for your head to explode when you get into a new field.
You might have studied opamps and 555s, but have you built anything from them? Electronics really is a practical discipline. If you don't want to get a breadboard and a DMM, then at least play with a circuit simulator. I read programming manuals and think I understand, but it's not until I've got something well beyond 'Hello World' working that I realise I didn't understand, and do now.
answered 1 hour ago
Neil_UK
70.1k273155
The context to the schematic gives you the initial route into the circuit.
For instance, you have illustrated an SMPS. By definition, this takes a power input, and delivers a regulated DC output. You now have to scan the schematic, until you find the words 'INPUT FILTER' at the top left, and 'DC OUTPUT at the top right.
Within that circuit, there will be many blocks which individually have an input and an output, and are strung together to perform the overall function. Here the part identification is your friend, and after googling them a few times, you will get used to the numbers quickly. The TL494 and the 78L05 are a switch mode controller and a low power voltage regulator respectively. You read the data sheets for those, and they tell you what the parts do, and what the pin functions are.
The examples you've chosen for digital versus analogue are somewhat extreme. If you'd posted the schematic of an MCU, with busses going between RAM and ALU and peripherals and ... you get the general idea, no inputs or outputs obvious unless you know what you're looking for. The analogue equivalent in complexity for your ABC logic function would be somewhere between the TL494 and the 78L05. The SMPS equivalent would be the MCU.
Get used to the numbers, use google for the datasheets, decompose into functional blocks (like an SPI peripheral), start simple, and lots and lots of practice. It's perfectly normal for your head to explode when you get into a new field.
You might have studied opamps and 555s, but have you built anything from them? Electronics really is a practical discipline. If you don't want to get a breadboard and a DMM, then at least play with a circuit simulator. I read programming manuals and think I understand, but it's not until I've got something well beyond 'Hello World' working that I realise I didn't understand, and do now.
answered 1 hour ago
Neil_UK
70.1k273155
answered 1 hour ago
Neil_UK
70.1k273155
answered 1 hour ago
Neil_UK
70.1k273155
answered 1 hour ago
Neil_UK
70.1k273155
70.1k273155
Thank you. I know the examples I gave differ on difficulty, but it is because it wasn't the main point. Regarding your example about MCU and RAM connection I am considering this part to be an analog one because of the usage of capacitors for filtering, for instance. Also, I agree with your suggestion but it doesn't always work to look for information in the schematic itself for named parts because it isn't always the case as is in this question: electronics.stackexchange.com/questions/387497/…)
– Hadley Siqueira
9 mins ago
add a comment |Â
Thank you. I know the examples I gave differ on difficulty, but it is because it wasn't the main point. Regarding your example about MCU and RAM connection I am considering this part to be an analog one because of the usage of capacitors for filtering, for instance. Also, I agree with your suggestion but it doesn't always work to look for information in the schematic itself for named parts because it isn't always the case as is in this question: electronics.stackexchange.com/questions/387497/…)
– Hadley Siqueira
9 mins ago
Thank you. I know the examples I gave differ on difficulty, but it is because it wasn't the main point. Regarding your example about MCU and RAM connection I am considering this part to be an analog one because of the usage of capacitors for filtering, for instance. Also, I agree with your suggestion but it doesn't always work to look for information in the schematic itself for named parts because it isn't always the case as is in this question: electronics.stackexchange.com/questions/387497/…)
– Hadley Siqueira
9 mins ago
Thank you. I know the examples I gave differ on difficulty, but it is because it wasn't the main point. Regarding your example about MCU and RAM connection I am considering this part to be an analog one because of the usage of capacitors for filtering, for instance. Also, I agree with your suggestion but it doesn't always work to look for information in the schematic itself for named parts because it isn't always the case as is in this question: electronics.stackexchange.com/questions/387497/…)
– Hadley Siqueira
9 mins ago
add a comment |Â
Hadley Siqueira is a new contributor. Be nice, and check out our Code of Conduct.
Hadley Siqueira is a new contributor. Be nice, and check out our Code of Conduct.
Hadley Siqueira is a new contributor. Be nice, and check out our Code of Conduct.
Hadley Siqueira is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2felectronics.stackexchange.com%2fquestions%2f397218%2fhow-to-interpret-a-schematic-in-terms-of-input-output%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
This question is really too broad to answer effectively, other than "Go get a BS in EE". What might work is to pick a specific schematic and ask us to explain the thought process in trying to understand what it does.
– Olin Lathrop
1 hour ago
Thank you, @OlinLathrop. Let's suppose that I take a BS in EE. What courses are linked to my question? I don't intend to take an actual BS in EE now (maybe in the future), but I have time to read the literature that you may recommend
– Hadley Siqueira
1 hour ago
1
There is no specific "read a schematic" course. You gain experience, recognize blocks and possible simplifications, what can be ignored and what can not, and so on. There is no single answer to your question, it is a case by case thing. The only way to learn how to read schematics is... Read schematics, fail, learn, repeat.
– Vladimir Cravero
1 hour ago
@OlinLathrop, would you mind give me an example regarding, for instance, the Q1 transistor at the top-middle of the SPMS schematic? It is the Q1 whose base is connected to resistors R6, R7 and R8. There also a diode D3 and a capacitor C9. This is an example of a topology that I haven't see so far in my reading.
– Hadley Siqueira
1 min ago