#20: Post edited
by
Olin Lathrop
·
2020-11-28T14:03:29Z (about 4 years ago)
This site is about <i>Electrical Engineering</i> (opamps, microcontrollers, etc) and <i>Electric Power Engineering</i> (utility-scale power generation, transmission, etc). These names may be somewhat different around the world, but the concepts are the same.
<h1>On-topic</h1>
Most questions that arise in the course of performing such engineering (with a few exceptions, see below) are on topic. This includes, for example:<ul>
<li>The design of circuits.
<li>The diagnosing of circuits.
<li>Physical construction of circuits or electrical products, within limits. This is generally on topic when there is some engineering aspect, or engineering tradeoffs that need to be made to accommodate manufacturing processes. If an electrical engineer needs to be aware of it, or needs to specify it to manufacturing, then it is on topic. How to wire a light socket in your house, for example, is off topic.
<li>Tools and techniques used in the course of the above.
Tools can be both hardware (soldering iron, oscilloscope) and software (schematic capture, simulation).
<li>The theory of circuits.
<li>Components used in a circuit.
<li>The physics behind how circuits and circuit components work, and the physics of related phenomena.
<li>Signal processing.
<li>Control theory.
<li>Power generation and transmission.
<li>Microcontrollers, FPGAs.
<li>Firmware and software.
This must be relevant to specific hardware, or about issues due to hardware limitations.
<li>Component identification, within strict guidelines. See the <a href="https://electrical.codidact.com/help/compid">Component ID Questions</a> help topic for more information.
</ul>
This isn't meant to be an exhaustive list, but hopefully you get the idea. Stay within the spirit of the above, and you'll generally be fine. We have no interest in engaging with rules-lawyers.
Sometimes there are legitimate gray areas. These are discussed in meta to find the consensus of the users.
<h1>Off-topic</h1>
The question and answer format of this site means it's not suited for certain topics or types of questions. Other topics are not allowed to keep the site focused on its purpose and reduce what most users would consider noise:<ul>
<li>Shopping questions.
What parts are available and where they are available changes too fast, and there is no single right answer. Answers are often opinion-based and devolve to popularity contests. As a result, we don't allow such questions.
We recognize that sourcing parts is an important part of engineering, but regardless, we're just not going to get into that here.
<li>High-level use of electrical devices.
If your question treats a device like a black box and isn't about its theory of operation or its design tradeoffs, then it's likely off topic.
There are some exceptions with the techniques of using tools specific to electronics, but don't go too far with this. We are not the help desk for your oscilloscope, but asking about how to use a scope to see a particular waveform might be OK.
<li>Consumer "electronics".
This is really a special case of the previous item, but it happens often enough to point out explicitly. This is not the place to ask how to set the clock in your microwave oven.
<li>No interest in understanding or learning, <i>"Just gimme da anser!"</i>
There has to be some element of engineering, theory, underlying physics, etc, in every question. This is why most <a href="https://electrical.codidact.com/help/arduino">Arduino</a> questions are off topic.
<li>URGENT!!!
Not our problem.
<li>What's the answer to this homework?
Again, this site is about learning. Just giving you the answer to a homework question defeats that, and is not allowed.
It is possible to ask about a homework question, explain what your thought process is, and where exactly you are stuck. If done right, we can try to guide you to discover the solution yourself. This is tricky. Be careful.
Always be honest about it being a homework problem. Most people you are asking have taken the same course you're taking and have done the homework. We know what homework looks like. Trying to disguise it is a great way to eliminate any good will that might have come your way.
</ul>
This site is about <i>Electrical Engineering</i> (opamps, microcontrollers, etc) and <i>Electric Power Engineering</i> (utility-scale power generation, transmission, etc). These names may be somewhat different around the world, but the concepts are the same.
<h1>On-topic</h1>
Most questions that arise in the course of performing such engineering (with a few exceptions, see below) are on topic. This includes, for example:<ul>
<li>The design of circuits.
<li>The diagnosing of circuits.
<li>Physical construction of circuits or electrical products, within limits. This is generally on topic when there is some engineering aspect, or engineering tradeoffs that need to be made to accommodate manufacturing processes. If an electrical engineer should be aware of it, or should specify it to manufacturing, then it is on topic. How to wire a light socket in your house, for example, is off topic.
<li>Tools and techniques used in the course of the above.
Tools can be both hardware (soldering iron, oscilloscope) and software (schematic capture, simulation).
<li>The theory of circuits.
<li>Components used in a circuit.
<li>The physics behind how circuits and circuit components work, and the physics of related phenomena.
<li>Signal processing.
<li>Control theory.
<li>Power generation and transmission.
<li>Microcontrollers, FPGAs.
<li>Firmware and software.
This must be relevant to specific hardware, or about issues due to hardware limitations.
<li>Component identification, within strict guidelines. See the <a href="https://electrical.codidact.com/help/compid">Component ID Questions</a> help topic for more information.
</ul>
This isn't meant to be an exhaustive list, but hopefully you get the idea. Stay within the spirit of the above, and you'll generally be fine. We have no interest in engaging with rules-lawyers.
Sometimes there are legitimate gray areas. These are discussed in meta to find the consensus of the users.
<h1>Off-topic</h1>
The question and answer format of this site means it's not suited for certain topics or types of questions. Other topics are not allowed to keep the site focused on its purpose and reduce what most users would consider noise:<ul>
<li>Shopping questions.
What parts are available and where they are available changes too fast, and there is no single right answer. Answers are often opinion-based and devolve to popularity contests. As a result, we don't allow such questions.
We recognize that sourcing parts is an important part of engineering, but regardless, we're just not going to get into that here.
<li>High-level use of electrical devices.
If your question treats a device like a black box and isn't about its theory of operation or its design tradeoffs, then it's likely off topic.
There are some exceptions with the techniques of using tools specific to electronics, but don't go too far with this. We are not the help desk for your oscilloscope, but asking about how to use a scope to see a particular waveform might be OK.
<li>Consumer "electronics".
This is really a special case of the previous item, but it happens often enough to point out explicitly. This is not the place to ask how to set the clock in your microwave oven.
<li>No interest in understanding or learning, <i>"Just gimme da anser!"</i>
There has to be some element of engineering, theory, underlying physics, etc, in every question. This is why most <a href="https://electrical.codidact.com/help/arduino">Arduino</a> questions are off topic.
<li>URGENT!!!
Not our problem.
<li>What's the answer to this homework?
Again, this site is about learning. Just giving you the answer to a homework question defeats that, and is not allowed.
It is possible to ask about a homework question, explain what your thought process is, and where exactly you are stuck. If done right, we can try to guide you to discover the solution yourself. This is tricky. Be careful.
Always be honest about it being a homework problem. Most people you are asking have taken the same course you're taking and have done the homework. We know what homework looks like. Trying to disguise it is a great way to eliminate any good will that might have come your way.
</ul>
#19: Post edited
by
Olin Lathrop
·
2020-11-24T14:44:36Z (about 4 years ago)
This site is about <i>Electrical Engineering</i> (opamps, microcontrollers, etc) and <i>Electric Power Engineering</i> (utility-scale power generation, transmission, etc). These names may be somewhat different around the world, but the concepts are the same.
<h1>On-topic</h1>
Most questions that arise in the course of performing such engineering (with a few exceptions, see below) are on topic. This includes, for example:<ul>
<li>The design of circuits.
<li>The diagnosing of circuits.
<li>Tools and techniques used in the course of the above.
Tools can be both hardware (soldering iron, oscilloscope) and software (schematic capture, simulation).
<li>The theory of circuits.
<li>Components used in a circuit.
<li>The physics behind how circuits and circuit components work, and the physics of related phenomena.
<li>Signal processing.
<li>Control theory.
<li>Power generation and transmission.
<li>Microcontrollers, FPGAs.
<li>Firmware and software.
This must be relevant to specific hardware, or about issues due to hardware limitations.
<li>Component identification, within strict guidelines. See the <a href="https://electrical.codidact.com/help/compid">Component ID Questions</a> help topic for more information.
</ul>
This isn't meant to be an exhaustive list, but hopefully you get the idea. Stay within the spirit of the above, and you'll generally be fine. We have no interest in engaging with rules-lawyers.
Sometimes there are legitimate gray areas. These are discussed in meta to find the consensus of the users.
<h1>Off-topic</h1>
The question and answer format of this site means it's not suited for certain topics or types of questions. Other topics are not allowed to keep the site focused on its purpose and reduce what most users would consider noise:<ul>
<li>Shopping questions.
What parts are available and where they are available changes too fast, and there is no single right answer. Answers are often opinion-based and devolve to popularity contests. As a result, we don't allow such questions.
We recognize that sourcing parts is an important part of engineering, but regardless, we're just not going to get into that here.
<li>High-level use of electrical devices.
If your question treats a device like a black box and isn't about its theory of operation or its design tradeoffs, then it's likely off topic.
There are some exceptions with the techniques of using tools specific to electronics, but don't go too far with this. We are not the help desk for your oscilloscope, but asking about how to use a scope to see a particular waveform might be OK.
<li>Consumer "electronics".
This is really a special case of the previous item, but it happens often enough to point out explicitly. This is not the place to ask how to set the clock in your microwave oven.
<li>No interest in understanding or learning, <i>"Just gimme da anser!"</i>
There has to be some element of engineering, theory, underlying physics, etc, in every question. This is why most <a href="https://electrical.codidact.com/help/arduino">Arduino</a> questions are off topic.
<li>URGENT!!!
Not our problem.
<li>What's the answer to this homework?
Again, this site is about learning. Just giving you the answer to a homework question defeats that, and is not allowed.
It is possible to ask about a homework question, explain what your thought process is, and where exactly you are stuck. If done right, we can try to guide you to discover the solution yourself. This is tricky. Be careful.
Always be honest about it being a homework problem. Most people you are asking have taken the same course you're taking and have done the homework. We know what homework looks like. Trying to disguise it is a great way to eliminate any good will that might have come your way.
</ul>
This site is about <i>Electrical Engineering</i> (opamps, microcontrollers, etc) and <i>Electric Power Engineering</i> (utility-scale power generation, transmission, etc). These names may be somewhat different around the world, but the concepts are the same.
<h1>On-topic</h1>
Most questions that arise in the course of performing such engineering (with a few exceptions, see below) are on topic. This includes, for example:<ul>
<li>The design of circuits.
<li>The diagnosing of circuits.
<li>Physical construction of circuits or electrical products, within limits. This is generally on topic when there is some engineering aspect, or engineering tradeoffs that need to be made to accommodate manufacturing processes. If an electrical engineer needs to be aware of it, or needs to specify it to manufacturing, then it is on topic. How to wire a light socket in your house, for example, is off topic.
<li>Tools and techniques used in the course of the above.
Tools can be both hardware (soldering iron, oscilloscope) and software (schematic capture, simulation).
<li>The theory of circuits.
<li>Components used in a circuit.
<li>The physics behind how circuits and circuit components work, and the physics of related phenomena.
<li>Signal processing.
<li>Control theory.
<li>Power generation and transmission.
<li>Microcontrollers, FPGAs.
<li>Firmware and software.
This must be relevant to specific hardware, or about issues due to hardware limitations.
<li>Component identification, within strict guidelines. See the <a href="https://electrical.codidact.com/help/compid">Component ID Questions</a> help topic for more information.
</ul>
This isn't meant to be an exhaustive list, but hopefully you get the idea. Stay within the spirit of the above, and you'll generally be fine. We have no interest in engaging with rules-lawyers.
Sometimes there are legitimate gray areas. These are discussed in meta to find the consensus of the users.
<h1>Off-topic</h1>
The question and answer format of this site means it's not suited for certain topics or types of questions. Other topics are not allowed to keep the site focused on its purpose and reduce what most users would consider noise:<ul>
<li>Shopping questions.
What parts are available and where they are available changes too fast, and there is no single right answer. Answers are often opinion-based and devolve to popularity contests. As a result, we don't allow such questions.
We recognize that sourcing parts is an important part of engineering, but regardless, we're just not going to get into that here.
<li>High-level use of electrical devices.
If your question treats a device like a black box and isn't about its theory of operation or its design tradeoffs, then it's likely off topic.
There are some exceptions with the techniques of using tools specific to electronics, but don't go too far with this. We are not the help desk for your oscilloscope, but asking about how to use a scope to see a particular waveform might be OK.
<li>Consumer "electronics".
This is really a special case of the previous item, but it happens often enough to point out explicitly. This is not the place to ask how to set the clock in your microwave oven.
<li>No interest in understanding or learning, <i>"Just gimme da anser!"</i>
There has to be some element of engineering, theory, underlying physics, etc, in every question. This is why most <a href="https://electrical.codidact.com/help/arduino">Arduino</a> questions are off topic.
<li>URGENT!!!
Not our problem.
<li>What's the answer to this homework?
Again, this site is about learning. Just giving you the answer to a homework question defeats that, and is not allowed.
It is possible to ask about a homework question, explain what your thought process is, and where exactly you are stuck. If done right, we can try to guide you to discover the solution yourself. This is tricky. Be careful.
Always be honest about it being a homework problem. Most people you are asking have taken the same course you're taking and have done the homework. We know what homework looks like. Trying to disguise it is a great way to eliminate any good will that might have come your way.
</ul>
#18: Post edited
by
Olin Lathrop
·
2020-06-16T20:55:51Z (over 4 years ago)
This site is about <i>Electrical Engineering</i> (opamps, microcontrollers, etc) and <i>Electric Power Engineering</i> (utility-scale power generation, transmission, etc). These names may be somewhat different around the world, but the concepts are the same.
<h1>On-topic</h1>
Most questions that arise in the course of performing such engineering (with a few exceptions, see below) are on topic. This includes, for example:<ul>
<li>The design of circuits.
<li>The diagnosing of circuits.
<li>Tools and techniques used in the course of the above.
Tools can be both hardware (soldering iron, oscilloscope) and software (schematic capture, simulation).
<li>The theory of circuits.
<li>Components used in a circuit.
<li>The physics behind how circuits and circuit components work, and the physics of related phenomena.
<li>Signal processing.
<li>Control theory.
<li>Power generation and transmission.
<li>Microcontrollers, FPGAs.
<li>Firmware and software.
This must be relevant to specific hardware, or about issues due to hardware limitations.
</ul>
This isn't meant to be an exhaustive list, but hopefully you get the idea. Stay within the spirit of the above, and you'll generally be fine. We have no interest in engaging with rules-lawyers.
Sometimes there are legitimate gray areas. These are discussed in meta to find the consensus of the users.
<h1>Off-topic</h1>
The question and answer format of this site means it's not suited for certain topics or types of questions. Other topics are not allowed to keep the site focused on its purpose and reduce what most users would consider noise:<ul>
<li>Shopping questions.
What parts are available and where they are available changes too fast, and there is no single right answer. Answers are often opinion-based and devolve to popularity contests. As a result, we don't allow such questions.
We recognize that sourcing parts is an important part of engineering, but regardless, we're just not going to get into that here.
<li>High-level use of electrical devices.
If your question treats a device like a black box and isn't about its theory of operation or its design tradeoffs, then it's likely off topic.
There are some exceptions with the techniques of using tools specific to electronics, but don't go too far with this. We are not the help desk for your oscilloscope, but asking about how to use a scope to see a particular waveform might be OK.
<li>Consumer "electronics".
This is really a special case of the previous item, but it happens often enough to point out explicitly. This is not the place to ask how to set the clock in your microwave oven.
<li>No interest in understanding or learning, <i>"Just gimme da anser!"</i>
There has to be some element of engineering, theory, underlying physics, etc, in every question. This is why most <a href="https://electrical.codidact.com/help/arduino">Arduino</a> questions are off topic.
<li>URGENT!!!
Not our problem.
<li>What's the answer to this homework?
Again, this site is about learning. Just giving you the answer to a homework question defeats that, and is not allowed.
It is possible to ask about a homework question, explain what your thought process is, and where exactly you are stuck. If done right, we can try to guide you to discover the solution yourself. This is tricky. Be careful.
Always be honest about it being a homework problem. Most people you are asking have taken the same course you're taking and have done the homework. We know what homework looks like. Trying to disguise it is a great way to eliminate any good will that might have come your way.
</ul>
This site is about <i>Electrical Engineering</i> (opamps, microcontrollers, etc) and <i>Electric Power Engineering</i> (utility-scale power generation, transmission, etc). These names may be somewhat different around the world, but the concepts are the same.
<h1>On-topic</h1>
Most questions that arise in the course of performing such engineering (with a few exceptions, see below) are on topic. This includes, for example:<ul>
<li>The design of circuits.
<li>The diagnosing of circuits.
<li>Tools and techniques used in the course of the above.
Tools can be both hardware (soldering iron, oscilloscope) and software (schematic capture, simulation).
<li>The theory of circuits.
<li>Components used in a circuit.
<li>The physics behind how circuits and circuit components work, and the physics of related phenomena.
<li>Signal processing.
<li>Control theory.
<li>Power generation and transmission.
<li>Microcontrollers, FPGAs.
<li>Firmware and software.
This must be relevant to specific hardware, or about issues due to hardware limitations.
<li>Component identification, within strict guidelines. See the <a href="https://electrical.codidact.com/help/compid">Component ID Questions</a> help topic for more information.
</ul>
This isn't meant to be an exhaustive list, but hopefully you get the idea. Stay within the spirit of the above, and you'll generally be fine. We have no interest in engaging with rules-lawyers.
Sometimes there are legitimate gray areas. These are discussed in meta to find the consensus of the users.
<h1>Off-topic</h1>
The question and answer format of this site means it's not suited for certain topics or types of questions. Other topics are not allowed to keep the site focused on its purpose and reduce what most users would consider noise:<ul>
<li>Shopping questions.
What parts are available and where they are available changes too fast, and there is no single right answer. Answers are often opinion-based and devolve to popularity contests. As a result, we don't allow such questions.
We recognize that sourcing parts is an important part of engineering, but regardless, we're just not going to get into that here.
<li>High-level use of electrical devices.
If your question treats a device like a black box and isn't about its theory of operation or its design tradeoffs, then it's likely off topic.
There are some exceptions with the techniques of using tools specific to electronics, but don't go too far with this. We are not the help desk for your oscilloscope, but asking about how to use a scope to see a particular waveform might be OK.
<li>Consumer "electronics".
This is really a special case of the previous item, but it happens often enough to point out explicitly. This is not the place to ask how to set the clock in your microwave oven.
<li>No interest in understanding or learning, <i>"Just gimme da anser!"</i>
There has to be some element of engineering, theory, underlying physics, etc, in every question. This is why most <a href="https://electrical.codidact.com/help/arduino">Arduino</a> questions are off topic.
<li>URGENT!!!
Not our problem.
<li>What's the answer to this homework?
Again, this site is about learning. Just giving you the answer to a homework question defeats that, and is not allowed.
It is possible to ask about a homework question, explain what your thought process is, and where exactly you are stuck. If done right, we can try to guide you to discover the solution yourself. This is tricky. Be careful.
Always be honest about it being a homework problem. Most people you are asking have taken the same course you're taking and have done the homework. We know what homework looks like. Trying to disguise it is a great way to eliminate any good will that might have come your way.
</ul>
#17: Post edited
by
Olin Lathrop
·
2020-06-16T20:53:29Z (over 4 years ago)
This site is about <i>Electrical Engineering</i> (opamps, microcontrollers, etc) and <i>Electric Power Engineering</i> (utility-scale power generation, transmission, etc). These names may be somewhat different around the world, but the concepts are the same.
<h1>On-topic</h1>
Most questions that arise in the course of performing such engineering (with a few exceptions, see below) are on topic. This includes, for example:<ul>
<li>The design of circuits.
<li>The diagnosing circuits.
<li>Tools used in the course of the above.
Tools can be both hardware (soldering iron, oscilloscope) and software (schematic capture, simulation).
<li>The theory of circuits.
<li>Components used in a circuit.
<li>The physics behind how circuits and circuit components work.
<li>Signal processing.
<li>Control theory.
<li>Power generation and transmission.
<li>Microcontrollers, FPGAs.
<li>Firmware and software.
This must be relevant to specific hardware, or about issues due to hardware limitations.
</ul>
This isn't meant to be an exhaustive list, but hopefully you get the idea. Stay within the spirit of the above, and you'll generally be fine. We have no interest in engaging with rules-lawyers.
Sometimes there are legitimate gray areas. These are discussed in meta to find the consensus of the users.
<h1>Off-topic</h1>
The question and answer format of this site means it's not suited for certain topics or types of questions. Other topics are not allowed to keep the site focused on its purpose and reduce what most users would consider noise:<ul>
<li>Shopping questions.
What parts are available and where they are available changes too fast, and there is no single right answer. Answers are often opinion-based and devolve to popularity contests. As a result, we don't allow such questions.
We recognize that sourcing parts is an important part of engineering, but regardless, we're just not going to get into that here.
<li>High-level use of electrical devices.
If your question treats a device like a black box and isn't about its theory of operation or its design tradeoffs, then it's likely off topic.
There are some exceptions with the techniques of using tools specific to electronics, but don't go too far with this. We are not the help desk for your oscilloscope, but asking about how to use a scope to see a particular waveform might be OK.
<li>Consumer "electronics".
This is really a special case of the previous item, but it happens often enough to point out explicitly. This is not the place to ask how to set the clock in your microwave oven.
<li>No interest in understanding or learning, <i>"Just gimme da anser!"</i>
There has to be some element of engineering, theory, underlying physics, etc, in every question. This is why most <a href="https://electrical.codidact.com/help/arduino">Arduino</a> questions are off topic.
<li>URGENT!!!
Not our problem.
<li>What's the answer to this homework?
Again, this site is about learning. Just giving you the answer to a homework question defeats that, and is not allowed.
It is possible to ask about a homework question, explain what your thought process is, and where exactly you are stuck. If done right, we can try to guide you to discover the solution yourself. This is tricky. Be careful.
Always be honest about it being a homework problem. Most people you are asking have taken the same course you're taking and have done the homework. We know what homework looks like. Trying to disguise it is a great way to eliminate any good will that might have come your way.
</ul>
This site is about <i>Electrical Engineering</i> (opamps, microcontrollers, etc) and <i>Electric Power Engineering</i> (utility-scale power generation, transmission, etc). These names may be somewhat different around the world, but the concepts are the same.
<h1>On-topic</h1>
Most questions that arise in the course of performing such engineering (with a few exceptions, see below) are on topic. This includes, for example:<ul>
<li>The design of circuits.
<li>The diagnosing of circuits.
<li>Tools and techniques used in the course of the above.
Tools can be both hardware (soldering iron, oscilloscope) and software (schematic capture, simulation).
<li>The theory of circuits.
<li>Components used in a circuit.
<li>The physics behind how circuits and circuit components work, and the physics of related phenomena.
<li>Signal processing.
<li>Control theory.
<li>Power generation and transmission.
<li>Microcontrollers, FPGAs.
<li>Firmware and software.
This must be relevant to specific hardware, or about issues due to hardware limitations.
</ul>
This isn't meant to be an exhaustive list, but hopefully you get the idea. Stay within the spirit of the above, and you'll generally be fine. We have no interest in engaging with rules-lawyers.
Sometimes there are legitimate gray areas. These are discussed in meta to find the consensus of the users.
<h1>Off-topic</h1>
The question and answer format of this site means it's not suited for certain topics or types of questions. Other topics are not allowed to keep the site focused on its purpose and reduce what most users would consider noise:<ul>
<li>Shopping questions.
What parts are available and where they are available changes too fast, and there is no single right answer. Answers are often opinion-based and devolve to popularity contests. As a result, we don't allow such questions.
We recognize that sourcing parts is an important part of engineering, but regardless, we're just not going to get into that here.
<li>High-level use of electrical devices.
If your question treats a device like a black box and isn't about its theory of operation or its design tradeoffs, then it's likely off topic.
There are some exceptions with the techniques of using tools specific to electronics, but don't go too far with this. We are not the help desk for your oscilloscope, but asking about how to use a scope to see a particular waveform might be OK.
<li>Consumer "electronics".
This is really a special case of the previous item, but it happens often enough to point out explicitly. This is not the place to ask how to set the clock in your microwave oven.
<li>No interest in understanding or learning, <i>"Just gimme da anser!"</i>
There has to be some element of engineering, theory, underlying physics, etc, in every question. This is why most <a href="https://electrical.codidact.com/help/arduino">Arduino</a> questions are off topic.
<li>URGENT!!!
Not our problem.
<li>What's the answer to this homework?
Again, this site is about learning. Just giving you the answer to a homework question defeats that, and is not allowed.
It is possible to ask about a homework question, explain what your thought process is, and where exactly you are stuck. If done right, we can try to guide you to discover the solution yourself. This is tricky. Be careful.
Always be honest about it being a homework problem. Most people you are asking have taken the same course you're taking and have done the homework. We know what homework looks like. Trying to disguise it is a great way to eliminate any good will that might have come your way.
</ul>
#16: Post edited
by
Olin Lathrop
·
2020-06-11T15:33:06Z (over 4 years ago)
This site is about <i>Electrical Engineering</i> (opamps, microcontrollers, etc) and <i>Electric Power Engineering</i> (utility-scale power generation, transmission, etc). These names may be somewhat different around the world, but the concepts are the same.
<h1>On-topic</h1>
Most questions that arise in the course of performing such engineering (with a few exceptions, see below) are on topic. This includes, for example:<ul>
<li>The design of circuits.
<li>The diagnosing circuits.
<li>Tools used in the course of the above.
Tools can be both hardware (soldering iron, oscilloscope) and software (schematic capture, simulation).
<li>The theory of circuits.
<li>Components used in a circuit.
<li>The physics behind how circuits and circuit components work.
<li>Signal processing.
<li>Control theory.
<li>Power generation and transmission.
<li>Microcontrollers, FPGAs.
<li>Firmware and software.
This must be relevant to specific hardware, or about issues due to hardware limitations.
</ul>
This isn't meant to be an exhaustive list, but hopefully you get the idea. Stay within the spirit of the above, and you'll generally be fine. We have no interest in engaging with rules-lawyers.
Sometimes there are legitimate gray areas. These are discussed in meta to find the consensus of the users.
<h1>Off-topic</h1>
The question and answer format of this site means it's not suited for certain topics or types of questions. Other topics are not allowed to keep the site focused on its purpose and reduce what most users would consider noise:<ul>
<li>Shopping questions.
What parts are available and where they are available changes too fast, and there is no single right answer. Answers are often opinion-based and devolve to popularity contests. As a result, we don't allow such questions.
We recognize that sourcing parts is an important part of engineering, but regardless, we're just not going to get into that here.
<li>High-level use of electrical devices.
If your question treats a device like a black box and isn't about its theory of operation or its design tradeoffs, then it's very likely off topic.
There are some exceptions with the techniques of using tools specific to electronics, but don't go too far with this. We are not the help desk for your oscilloscope, but asking about how to use a scope to see a particular waveform might be OK.
<li>Consumer "electronics".
This is really a special case of the previous item, but it happens often enough to point out explicitly. This is not the place to ask how to set the clock in your microwave oven.
<li>No interest in understanding or learning, <i>"Just gimme da anser!"</i>
There has to be some element of engineering, theory, underlying physics, etc, in every question. This is why most <a href="https://electrical.codidact.com/help/arduino">Arduino</a> questions are off topic.
<li>URGENT!!!
Not our problem.
<li>What's the answer to this homework?
Again, this site is about learning. Just giving you the answer to a homework question defeats that, and is not allowed.
It is possible to ask about a homework question, explain what your thought process is, and where exactly you are stuck. If done right, we can try to guide you to discover the solution yourself. This is tricky. Be careful.
Always be honest about it being a homework problem. Most people you are asking have taken the same course you're taking and have done the homework. We know what homework looks like. Trying to disguise it is a great way to eliminate any good will that might have come your way.
</ul>
This site is about <i>Electrical Engineering</i> (opamps, microcontrollers, etc) and <i>Electric Power Engineering</i> (utility-scale power generation, transmission, etc). These names may be somewhat different around the world, but the concepts are the same.
<h1>On-topic</h1>
Most questions that arise in the course of performing such engineering (with a few exceptions, see below) are on topic. This includes, for example:<ul>
<li>The design of circuits.
<li>The diagnosing circuits.
<li>Tools used in the course of the above.
Tools can be both hardware (soldering iron, oscilloscope) and software (schematic capture, simulation).
<li>The theory of circuits.
<li>Components used in a circuit.
<li>The physics behind how circuits and circuit components work.
<li>Signal processing.
<li>Control theory.
<li>Power generation and transmission.
<li>Microcontrollers, FPGAs.
<li>Firmware and software.
This must be relevant to specific hardware, or about issues due to hardware limitations.
</ul>
This isn't meant to be an exhaustive list, but hopefully you get the idea. Stay within the spirit of the above, and you'll generally be fine. We have no interest in engaging with rules-lawyers.
Sometimes there are legitimate gray areas. These are discussed in meta to find the consensus of the users.
<h1>Off-topic</h1>
The question and answer format of this site means it's not suited for certain topics or types of questions. Other topics are not allowed to keep the site focused on its purpose and reduce what most users would consider noise:<ul>
<li>Shopping questions.
What parts are available and where they are available changes too fast, and there is no single right answer. Answers are often opinion-based and devolve to popularity contests. As a result, we don't allow such questions.
We recognize that sourcing parts is an important part of engineering, but regardless, we're just not going to get into that here.
<li>High-level use of electrical devices.
If your question treats a device like a black box and isn't about its theory of operation or its design tradeoffs, then it's likely off topic.
There are some exceptions with the techniques of using tools specific to electronics, but don't go too far with this. We are not the help desk for your oscilloscope, but asking about how to use a scope to see a particular waveform might be OK.
<li>Consumer "electronics".
This is really a special case of the previous item, but it happens often enough to point out explicitly. This is not the place to ask how to set the clock in your microwave oven.
<li>No interest in understanding or learning, <i>"Just gimme da anser!"</i>
There has to be some element of engineering, theory, underlying physics, etc, in every question. This is why most <a href="https://electrical.codidact.com/help/arduino">Arduino</a> questions are off topic.
<li>URGENT!!!
Not our problem.
<li>What's the answer to this homework?
Again, this site is about learning. Just giving you the answer to a homework question defeats that, and is not allowed.
It is possible to ask about a homework question, explain what your thought process is, and where exactly you are stuck. If done right, we can try to guide you to discover the solution yourself. This is tricky. Be careful.
Always be honest about it being a homework problem. Most people you are asking have taken the same course you're taking and have done the homework. We know what homework looks like. Trying to disguise it is a great way to eliminate any good will that might have come your way.
</ul>
#15: Post edited
by
Olin Lathrop
·
2020-06-11T15:31:38Z (over 4 years ago)
This site is about <i>Electrical Engineering</i> (opamps, microcontrollers, etc) and <i>Electric Power Engineering</i> (utility-scale power generation, transmission, etc). These names may be somewhat different around the world, but the concepts are the same.
<h1>On-topic</h1>
Most questions that arise in the course of performing such engineering (with a few exceptions, see below) are on topic. This includes, for example:<ul>
<li>The design of circuits.
<li>The diagnosing circuits.
<li>Tools used in the course of the above.
Tools can be both hardware (soldering iron, oscilloscope) and software (schematic capture, simulation).
<li>The theory of circuits.
<li>Components used in a circuit.
<li>The physics behind how circuits and circuit components work.
<li>Signal processing.
<li>Control theory.
<li>Power generation and transmission.
<li>Microcontrollers, FPGAs.
<li>Firmware and software.
This must be relevant to specific hardware, or about issues due to hardware limitations. General software questions are off topic.
</ul>
This isn't meant to be an exhaustive list, but hopefully you get the idea. Stay within the spirit of the above, and you'll generally be fine. We have no interest in engaging rules-lawyers.
Sometimes there are legitimate gray areas. These are discussed in meta to find the consensus of the users.
<h1>Off-topic</h1>
The question and answer format of this site means it's not suited for certain topics or types of questions. Other topics are not allowed to keep the site focused on its purpose and reduce what most users would consider noise:<ul>
<li>Shopping questions.
What parts are available and where they are available changes too fast, and there is no single right answer. Answers are often opinion-based and devolve to popularity contests. As a result, we don't allow such questions.
We recognize that sourcing parts is an important part of engineering, but regardless, we're just not going to get into that here.
<li>High-level use of electrical devices.
If your question treats a device like a black box and isn't about its theory of operation or its design tradeoffs, then it's very likely off topic.
There are some exceptions with the techniques of using tools specific to electronics, but don't go too far with this. We are not the help desk for your oscilloscope, but asking about how to use a scope to see a particular waveform might be OK.
<li>Consumer "electronics".
This is really a special case of the previous item, but it happens often enough to point out explicitly. This is not the place to ask how to set the clock in your microwave oven.
<li>No interest in understanding or learning, <i>"Just gimme da anser!"</i>
There has to be some element of engineering, theory, underlying physics, etc, in every question. This is why most <a href="https://electrical.codidact.com/help/arduino">Arduino</a> questions are off topic.
<li>URGENT!!!
Not our problem.
<li>What's the answer to this homework?
Again, this site is about learning. Just giving you the answer to a homework question defeats that, and is not allowed.
It is possible to ask about a homework question, explain what your thought process is, and where exactly you are stuck. If done right, we can try to guide you to discover the solution yourself. This is tricky. Be careful.
Always be honest about it being a homework problem. Most people you are asking have taken the same course you're taking and have done the homework. We know what homework looks like. Trying to disguise it is a great way to eliminate any good will that might have come your way.
</ul>
This site is about <i>Electrical Engineering</i> (opamps, microcontrollers, etc) and <i>Electric Power Engineering</i> (utility-scale power generation, transmission, etc). These names may be somewhat different around the world, but the concepts are the same.
<h1>On-topic</h1>
Most questions that arise in the course of performing such engineering (with a few exceptions, see below) are on topic. This includes, for example:<ul>
<li>The design of circuits.
<li>The diagnosing circuits.
<li>Tools used in the course of the above.
Tools can be both hardware (soldering iron, oscilloscope) and software (schematic capture, simulation).
<li>The theory of circuits.
<li>Components used in a circuit.
<li>The physics behind how circuits and circuit components work.
<li>Signal processing.
<li>Control theory.
<li>Power generation and transmission.
<li>Microcontrollers, FPGAs.
<li>Firmware and software.
This must be relevant to specific hardware, or about issues due to hardware limitations.
</ul>
This isn't meant to be an exhaustive list, but hopefully you get the idea. Stay within the spirit of the above, and you'll generally be fine. We have no interest in engaging with rules-lawyers.
Sometimes there are legitimate gray areas. These are discussed in meta to find the consensus of the users.
<h1>Off-topic</h1>
The question and answer format of this site means it's not suited for certain topics or types of questions. Other topics are not allowed to keep the site focused on its purpose and reduce what most users would consider noise:<ul>
<li>Shopping questions.
What parts are available and where they are available changes too fast, and there is no single right answer. Answers are often opinion-based and devolve to popularity contests. As a result, we don't allow such questions.
We recognize that sourcing parts is an important part of engineering, but regardless, we're just not going to get into that here.
<li>High-level use of electrical devices.
If your question treats a device like a black box and isn't about its theory of operation or its design tradeoffs, then it's very likely off topic.
There are some exceptions with the techniques of using tools specific to electronics, but don't go too far with this. We are not the help desk for your oscilloscope, but asking about how to use a scope to see a particular waveform might be OK.
<li>Consumer "electronics".
This is really a special case of the previous item, but it happens often enough to point out explicitly. This is not the place to ask how to set the clock in your microwave oven.
<li>No interest in understanding or learning, <i>"Just gimme da anser!"</i>
There has to be some element of engineering, theory, underlying physics, etc, in every question. This is why most <a href="https://electrical.codidact.com/help/arduino">Arduino</a> questions are off topic.
<li>URGENT!!!
Not our problem.
<li>What's the answer to this homework?
Again, this site is about learning. Just giving you the answer to a homework question defeats that, and is not allowed.
It is possible to ask about a homework question, explain what your thought process is, and where exactly you are stuck. If done right, we can try to guide you to discover the solution yourself. This is tricky. Be careful.
Always be honest about it being a homework problem. Most people you are asking have taken the same course you're taking and have done the homework. We know what homework looks like. Trying to disguise it is a great way to eliminate any good will that might have come your way.
</ul>
#14: Post edited
by
Olin Lathrop
·
2020-06-11T15:30:54Z (over 4 years ago)
This site is about <i>Electrical Engineering</i> (opamps, microcontrollers, etc) and <i>Electric Power Engineering</i> (utility-scale power generation, transmission, etc). These names may be somewhat different around the world, but the concepts are the same.
<h1>On-topic</h1>
Most questions that arise in the course of performing such engineering (with a few exceptions, see below) are on topic. This includes, for example:<ul>
<li>The design of circuits.
<li>The diagnosing circuits.
<li>Tools used in the course of the above.
Tools can be both hardware (soldering iron, oscilloscope) and software (schematic capture, simulation).
<li>The theory of circuits.
<li>Components used in a circuit.
<li>The physics behind how circuits and circuit components work.
<li>Signal processing.
<li>Control theory.
<li>Power generation and transmission.
<li>Microcontrollers, FPGAs.
<li>Firmware and software.
This must be relevant to specific hardware, or about issues due to hardware limitations.
</ul>
This isn't meant to be an exhaustive list, but hopefully you get the idea. Stay within the spirit of the above, and you'll generally be fine. We have no interest in engaging rules-lawyers.
Sometimes there are legitimate gray areas. These are discussed in meta to find the consensus of the users.
<h1>Off-topic</h1>
The question and answer format of this site means it's not suited for certain topics or types of questions. Other topics are not allowed to keep the site focused on its purpose and reduce what most users would consider noise:<ul>
<li>Shopping questions.
What parts are available and where they are available changes too fast, and there is no single right answer. Answers are often opinion-based and devolve to popularity contests. As a result, we don't allow such questions.
We recognize that sourcing parts is an important part of engineering, but regardless, we're just not going to get into that here.
<li>High-level use of electrical devices.
If your question treats a device like a black box and isn't about its theory of operation or its design tradeoffs, then it's very likely off topic.
There are some exceptions with the techniques of using tools specific to electronics, but don't go too far with this. We are not the help desk for your oscilloscope, but asking about how to use a scope to see a particular waveform might be OK.
<li>Consumer "electronics".
This is really a special case of the previous item, but it happens often enough to point out explicitly. This is not the place to ask how to set the clock in your microwave oven.
<li>No interest in understanding or learning, <i>"Just gimme da anser!"</i>
There has to be some element of engineering, theory, underlying physics, etc, in every question. This is why most <a href="https://electrical.codidact.com/help/arduino">Arduino</a> questions are off topic.
<li>URGENT!!!
Not our problem.
<li>What's the answer to this homework?
Again, this site is about learning. Just giving you the answer to a homework question defeats that, and is not allowed.
It is possible to ask about a homework question, explain what your thought process is, and where exactly you are stuck. If done right, we can try to guide you to discover the solution yourself. This is tricky. Be careful.
Always be honest about it being a homework problem. Most people you are asking have taken the same course you're taking and have done the homework. We know what homework looks like. Trying to disguise it is a great way to eliminate any good will that might have come your way.
</ul>
This site is about <i>Electrical Engineering</i> (opamps, microcontrollers, etc) and <i>Electric Power Engineering</i> (utility-scale power generation, transmission, etc). These names may be somewhat different around the world, but the concepts are the same.
<h1>On-topic</h1>
Most questions that arise in the course of performing such engineering (with a few exceptions, see below) are on topic. This includes, for example:<ul>
<li>The design of circuits.
<li>The diagnosing circuits.
<li>Tools used in the course of the above.
Tools can be both hardware (soldering iron, oscilloscope) and software (schematic capture, simulation).
<li>The theory of circuits.
<li>Components used in a circuit.
<li>The physics behind how circuits and circuit components work.
<li>Signal processing.
<li>Control theory.
<li>Power generation and transmission.
<li>Microcontrollers, FPGAs.
<li>Firmware and software.
This must be relevant to specific hardware, or about issues due to hardware limitations. General software questions are off topic.
</ul>
This isn't meant to be an exhaustive list, but hopefully you get the idea. Stay within the spirit of the above, and you'll generally be fine. We have no interest in engaging rules-lawyers.
Sometimes there are legitimate gray areas. These are discussed in meta to find the consensus of the users.
<h1>Off-topic</h1>
The question and answer format of this site means it's not suited for certain topics or types of questions. Other topics are not allowed to keep the site focused on its purpose and reduce what most users would consider noise:<ul>
<li>Shopping questions.
What parts are available and where they are available changes too fast, and there is no single right answer. Answers are often opinion-based and devolve to popularity contests. As a result, we don't allow such questions.
We recognize that sourcing parts is an important part of engineering, but regardless, we're just not going to get into that here.
<li>High-level use of electrical devices.
If your question treats a device like a black box and isn't about its theory of operation or its design tradeoffs, then it's very likely off topic.
There are some exceptions with the techniques of using tools specific to electronics, but don't go too far with this. We are not the help desk for your oscilloscope, but asking about how to use a scope to see a particular waveform might be OK.
<li>Consumer "electronics".
This is really a special case of the previous item, but it happens often enough to point out explicitly. This is not the place to ask how to set the clock in your microwave oven.
<li>No interest in understanding or learning, <i>"Just gimme da anser!"</i>
There has to be some element of engineering, theory, underlying physics, etc, in every question. This is why most <a href="https://electrical.codidact.com/help/arduino">Arduino</a> questions are off topic.
<li>URGENT!!!
Not our problem.
<li>What's the answer to this homework?
Again, this site is about learning. Just giving you the answer to a homework question defeats that, and is not allowed.
It is possible to ask about a homework question, explain what your thought process is, and where exactly you are stuck. If done right, we can try to guide you to discover the solution yourself. This is tricky. Be careful.
Always be honest about it being a homework problem. Most people you are asking have taken the same course you're taking and have done the homework. We know what homework looks like. Trying to disguise it is a great way to eliminate any good will that might have come your way.
</ul>
#13: Post edited
by
Olin Lathrop
·
2020-06-11T15:30:00Z (over 4 years ago)
This site is about <i>Electrical Engineering</i> (opamps, microcontrollers, etc) and <i>Electric Power Engineering</i> (utility-scale power generation, transmission, etc). These names may be somewhat different around the world, but the concepts are the same.
<h1>On-topic</h1>
Most questions that arise in the course of performing such engineering (with a few exceptions, see below) are on topic. This includes, for example:<ul>
<li>The design of circuits.
<li>Diagnosing circuits.
<li>Tools used in the course of the above.
Tools can be both hardware (soldering iron, oscilloscope) and software (schematic capture, simulation).
<li>The theory of circuits.
<li>Components used in a circuit.
<li>The physics behind how circuits and circuit components work.
<li>Signal processing.
<li>Control theory.
<li>Power generation and transmission.
<li>Microcontrollers, FPGAs.
<li>Firmware and software.
This must be relevant to specific hardware, or about issues due to hardware limitations.
</ul>
This isn't meant to be an exhaustive list, but hopefully you get the idea. Stay within the spirit of the above, and you'll generally be fine. We have no interest in engaging rules-lawyers.
Sometimes there are legitimate gray areas. These are discussed in meta to find the consensus of the users.
<h1>Off-topic</h1>
The question and answer format of this site means it's not suited for certain topics or types of questions. Other topics are not allowed to keep the site focused on its purpose and reduce what most users would consider noise:<ul>
<li>Shopping questions.
What parts are available and where they are available changes too fast, and there is no single right answer. Answers are often opinion-based and devolve to popularity contests. As a result, we don't allow such questions.
We recognize that sourcing parts is an important part of engineering, but regardless, we're just not going to get into that here.
<li>High-level use of electrical devices.
If your question treats a device like a black box and isn't about its theory of operation or its design tradeoffs, then it's very likely off topic.
There are some exceptions with the techniques of using tools specific to electronics, but don't go too far with this. We are not the help desk for your oscilloscope, but asking about how to use a scope to see a particular waveform might be OK.
<li>Consumer "electronics".
This is really a special case of the previous item, but it happens often enough to point out explicitly. This is not the place to ask how to set the clock in your microwave oven.
<li>No interest in understanding or learning, <i>"Just gimme da anser!"</i>
There has to be some element of engineering, theory, underlying physics, etc, in every question. This is why most <a href="https://electrical.codidact.com/help/arduino">Arduino</a> questions are off topic.
<li>URGENT!!!
Not our problem.
<li>What's the answer to this homework?
Again, this site is about learning. Just giving you the answer to a homework question defeats that, and is not allowed.
It is possible to ask about a homework question, explain what your thought process is, and where exactly you are stuck. If done right, we can try to guide you to discover the solution yourself. This is tricky. Be careful.
Always be honest about it being a homework problem. Most people you are asking have taken the same course you're taking and have done the homework. We know what homework looks like. Trying to disguise it is a great way to eliminate any good will that might have come your way.
</ul>
This site is about <i>Electrical Engineering</i> (opamps, microcontrollers, etc) and <i>Electric Power Engineering</i> (utility-scale power generation, transmission, etc). These names may be somewhat different around the world, but the concepts are the same.
<h1>On-topic</h1>
Most questions that arise in the course of performing such engineering (with a few exceptions, see below) are on topic. This includes, for example:<ul>
<li>The design of circuits.
<li>The diagnosing circuits.
<li>Tools used in the course of the above.
Tools can be both hardware (soldering iron, oscilloscope) and software (schematic capture, simulation).
<li>The theory of circuits.
<li>Components used in a circuit.
<li>The physics behind how circuits and circuit components work.
<li>Signal processing.
<li>Control theory.
<li>Power generation and transmission.
<li>Microcontrollers, FPGAs.
<li>Firmware and software.
This must be relevant to specific hardware, or about issues due to hardware limitations.
</ul>
This isn't meant to be an exhaustive list, but hopefully you get the idea. Stay within the spirit of the above, and you'll generally be fine. We have no interest in engaging rules-lawyers.
Sometimes there are legitimate gray areas. These are discussed in meta to find the consensus of the users.
<h1>Off-topic</h1>
The question and answer format of this site means it's not suited for certain topics or types of questions. Other topics are not allowed to keep the site focused on its purpose and reduce what most users would consider noise:<ul>
<li>Shopping questions.
What parts are available and where they are available changes too fast, and there is no single right answer. Answers are often opinion-based and devolve to popularity contests. As a result, we don't allow such questions.
We recognize that sourcing parts is an important part of engineering, but regardless, we're just not going to get into that here.
<li>High-level use of electrical devices.
If your question treats a device like a black box and isn't about its theory of operation or its design tradeoffs, then it's very likely off topic.
There are some exceptions with the techniques of using tools specific to electronics, but don't go too far with this. We are not the help desk for your oscilloscope, but asking about how to use a scope to see a particular waveform might be OK.
<li>Consumer "electronics".
This is really a special case of the previous item, but it happens often enough to point out explicitly. This is not the place to ask how to set the clock in your microwave oven.
<li>No interest in understanding or learning, <i>"Just gimme da anser!"</i>
There has to be some element of engineering, theory, underlying physics, etc, in every question. This is why most <a href="https://electrical.codidact.com/help/arduino">Arduino</a> questions are off topic.
<li>URGENT!!!
Not our problem.
<li>What's the answer to this homework?
Again, this site is about learning. Just giving you the answer to a homework question defeats that, and is not allowed.
It is possible to ask about a homework question, explain what your thought process is, and where exactly you are stuck. If done right, we can try to guide you to discover the solution yourself. This is tricky. Be careful.
Always be honest about it being a homework problem. Most people you are asking have taken the same course you're taking and have done the homework. We know what homework looks like. Trying to disguise it is a great way to eliminate any good will that might have come your way.
</ul>
#12: Post edited
by
Olin Lathrop
·
2020-06-11T15:29:06Z (over 4 years ago)
This site is about <i>Electrical Engineering</i> (opamps, microcontrollers, etc) and <i>Electric Power Engineering</i> (utility-scale power generation, transmission, etc). These names may be somewhat different around the world, but the concepts are the same.
<h1>On-topic</h1>
Most questions that arise in the course of performing such engineering (with a few exceptions, see below) are on topic. This includes, for example:<ul>
<li>The design of circuits.
<li>The theory of circuits.
<li>Tools used in the course of the above.
Tools can be both hardware (soldering iron, oscilloscope) and software (schematic capture, simulation).
<li>Components used in a circuit.
<li>The physics behind how circuits and circuit components work.
<li>Signal processing.
<li>Control theory.
<li>Power generation and transmission.
<li>Microcontrollers, FPGAs.
<li>Firmware and software.
This must be relevant to specific hardware, or about issues due to hardware limitations.
</ul>
This isn't meant to be an exhaustive list, but hopefully you get the idea. Stay within the spirit of the above, and you'll generally be fine. We have no interest in engaging rules-lawyers.
Sometimes there are legitimate gray areas. These are discussed in meta to find the consensus of the users.
<h1>Off-topic</h1>
The question and answer format of this site means it's not suited for certain topics or types of questions. Other topics are not allowed to keep the site focused on its purpose and reduce what most users would consider noise:<ul>
<li>Shopping questions.
What parts are available and where they are available changes too fast, and there is no single right answer. Answers are often opinion-based and devolve to popularity contests. As a result, we don't allow such questions.
We recognize that sourcing parts is an important part of engineering, but regardless, we're just not going to get into that here.
<li>High-level use of electrical devices.
If your question treats a device like a black box and isn't about its theory of operation or its design tradeoffs, then it's very likely off topic.
There are some exceptions with the techniques of using tools specific to electronics, but don't go too far with this. We are not the help desk for your oscilloscope, but asking about how to use a scope to see a particular waveform might be OK.
<li>Consumer "electronics".
This is really a special case of the previous item, but it happens often enough to point out explicitly. This is not the place to ask how to set the clock in your microwave oven.
<li>No interest in understanding or learning, <i>"Just gimme da anser!"</i>
There has to be some element of engineering, theory, underlying physics, etc, in every question. This is why most <a href="https://electrical.codidact.com/help/arduino">Arduino</a> questions are off topic.
<li>URGENT!!!
Not our problem.
<li>What's the answer to this homework?
Again, this site is about learning. Just giving you the answer to a homework question defeats that, and is not allowed.
It is possible to ask about a homework question, explain what your thought process is, and where exactly you are stuck. If done right, we can try to guide you to discover the solution yourself. This is tricky. Be careful.
Always be honest about it being a homework problem. Most people you are asking have taken the same course you're taking and have done the homework. We know what homework looks like. Trying to disguise it is a great way to eliminate any good will that might have come your way.
</ul>
This site is about <i>Electrical Engineering</i> (opamps, microcontrollers, etc) and <i>Electric Power Engineering</i> (utility-scale power generation, transmission, etc). These names may be somewhat different around the world, but the concepts are the same.
<h1>On-topic</h1>
Most questions that arise in the course of performing such engineering (with a few exceptions, see below) are on topic. This includes, for example:<ul>
<li>The design of circuits.
<li>Diagnosing circuits.
<li>Tools used in the course of the above.
Tools can be both hardware (soldering iron, oscilloscope) and software (schematic capture, simulation).
<li>The theory of circuits.
<li>Components used in a circuit.
<li>The physics behind how circuits and circuit components work.
<li>Signal processing.
<li>Control theory.
<li>Power generation and transmission.
<li>Microcontrollers, FPGAs.
<li>Firmware and software.
This must be relevant to specific hardware, or about issues due to hardware limitations.
</ul>
This isn't meant to be an exhaustive list, but hopefully you get the idea. Stay within the spirit of the above, and you'll generally be fine. We have no interest in engaging rules-lawyers.
Sometimes there are legitimate gray areas. These are discussed in meta to find the consensus of the users.
<h1>Off-topic</h1>
The question and answer format of this site means it's not suited for certain topics or types of questions. Other topics are not allowed to keep the site focused on its purpose and reduce what most users would consider noise:<ul>
<li>Shopping questions.
What parts are available and where they are available changes too fast, and there is no single right answer. Answers are often opinion-based and devolve to popularity contests. As a result, we don't allow such questions.
We recognize that sourcing parts is an important part of engineering, but regardless, we're just not going to get into that here.
<li>High-level use of electrical devices.
If your question treats a device like a black box and isn't about its theory of operation or its design tradeoffs, then it's very likely off topic.
There are some exceptions with the techniques of using tools specific to electronics, but don't go too far with this. We are not the help desk for your oscilloscope, but asking about how to use a scope to see a particular waveform might be OK.
<li>Consumer "electronics".
This is really a special case of the previous item, but it happens often enough to point out explicitly. This is not the place to ask how to set the clock in your microwave oven.
<li>No interest in understanding or learning, <i>"Just gimme da anser!"</i>
There has to be some element of engineering, theory, underlying physics, etc, in every question. This is why most <a href="https://electrical.codidact.com/help/arduino">Arduino</a> questions are off topic.
<li>URGENT!!!
Not our problem.
<li>What's the answer to this homework?
Again, this site is about learning. Just giving you the answer to a homework question defeats that, and is not allowed.
It is possible to ask about a homework question, explain what your thought process is, and where exactly you are stuck. If done right, we can try to guide you to discover the solution yourself. This is tricky. Be careful.
Always be honest about it being a homework problem. Most people you are asking have taken the same course you're taking and have done the homework. We know what homework looks like. Trying to disguise it is a great way to eliminate any good will that might have come your way.
</ul>
#11: Post edited
by
Olin Lathrop
·
2020-06-11T15:27:53Z (over 4 years ago)
This site is about <i>Electrical Engineering</i> (opamps, microcontrollers, etc) and <i>Electric Power Engineering</i> (utility-scale power generation, transmission, etc). These names may be somewhat different around the world.
<h1>On-topic</h1>
Most questions that arise in the course of performing such engineering (with a few exceptions, see below) are on topic. This includes, for example:<ul>
<li>The design of circuits.
<li>The theory of circuits.
<li>Tools used in the course of the above.
Tools can be both hardware (soldering iron, oscilloscope) and software (schematic capture, simulation).
<li>Components used in a circuit.
<li>The physics behind how circuits and circuit components work.
<li>Signal processing.
<li>Control theory.
<li>Power generation and transmission.
<li>Microcontrollers, FPGAs.
<li>Firmware and software.
This must be relevant to specific hardware, or about issues due to hardware limitations.
</ul>
This isn't meant to be an exhaustive list, but hopefully you get the idea. Stay within the spirit of the above, and you'll generally be fine. We have no interest in engaging rules-lawyers.
Sometimes there are legitimate gray areas. These are discussed in meta to find the consensus of the users.
<h1>Off-topic</h1>
The question and answer format of this site means it's not suited for certain topics or types of questions. Other topics are not allowed to keep the site focused on its purpose and reduce what most users would consider noise:<ul>
<li>Shopping questions.
What parts are available and where they are available changes too fast, and there is no single right answer. Answers are often opinion-based and devolve to popularity contests. As a result, we don't allow such questions.
We recognize that sourcing parts is an important part of engineering, but regardless, we're just not going to get into that here.
<li>High-level use of electrical devices.
If your question treats a device like a black box and isn't about its theory of operation or its design tradeoffs, then it's very likely off topic.
There are some exceptions with the techniques of using tools specific to electronics, but don't go too far with this. We are not the help desk for your oscilloscope, but asking about how to use a scope to see a particular waveform might be OK.
<li>Consumer "electronics".
This is really a special case of the previous item, but it happens often enough to point out explicitly. This is not the place to ask how to set the clock in your microwave oven.
<li>No interest in understanding or learning, <i>"Just gimme da anser!"</i>
There has to be some element of engineering, theory, underlying physics, etc, in every question. This is why most <a href="https://electrical.codidact.com/help/arduino">Arduino</a> questions are off topic.
<li>URGENT!!!
Not our problem.
<li>What's the answer to this homework?
Again, this site is about learning. Just giving you the answer to a homework question defeats that, and is not allowed.
It is possible to ask about a homework question, explain what your thought process is, and where exactly you are stuck. If done right, we can try to guide you to discover the solution yourself. This is tricky. Be careful.
Always be honest about it being a homework problem. Most people you are asking have taken the same course you're taking and have done the homework. We know what homework looks like. Trying to disguise it is a great way to eliminate any good will that might have come your way.
</ul>
This site is about <i>Electrical Engineering</i> (opamps, microcontrollers, etc) and <i>Electric Power Engineering</i> (utility-scale power generation, transmission, etc). These names may be somewhat different around the world, but the concepts are the same.
<h1>On-topic</h1>
Most questions that arise in the course of performing such engineering (with a few exceptions, see below) are on topic. This includes, for example:<ul>
<li>The design of circuits.
<li>The theory of circuits.
<li>Tools used in the course of the above.
Tools can be both hardware (soldering iron, oscilloscope) and software (schematic capture, simulation).
<li>Components used in a circuit.
<li>The physics behind how circuits and circuit components work.
<li>Signal processing.
<li>Control theory.
<li>Power generation and transmission.
<li>Microcontrollers, FPGAs.
<li>Firmware and software.
This must be relevant to specific hardware, or about issues due to hardware limitations.
</ul>
This isn't meant to be an exhaustive list, but hopefully you get the idea. Stay within the spirit of the above, and you'll generally be fine. We have no interest in engaging rules-lawyers.
Sometimes there are legitimate gray areas. These are discussed in meta to find the consensus of the users.
<h1>Off-topic</h1>
The question and answer format of this site means it's not suited for certain topics or types of questions. Other topics are not allowed to keep the site focused on its purpose and reduce what most users would consider noise:<ul>
<li>Shopping questions.
What parts are available and where they are available changes too fast, and there is no single right answer. Answers are often opinion-based and devolve to popularity contests. As a result, we don't allow such questions.
We recognize that sourcing parts is an important part of engineering, but regardless, we're just not going to get into that here.
<li>High-level use of electrical devices.
If your question treats a device like a black box and isn't about its theory of operation or its design tradeoffs, then it's very likely off topic.
There are some exceptions with the techniques of using tools specific to electronics, but don't go too far with this. We are not the help desk for your oscilloscope, but asking about how to use a scope to see a particular waveform might be OK.
<li>Consumer "electronics".
This is really a special case of the previous item, but it happens often enough to point out explicitly. This is not the place to ask how to set the clock in your microwave oven.
<li>No interest in understanding or learning, <i>"Just gimme da anser!"</i>
There has to be some element of engineering, theory, underlying physics, etc, in every question. This is why most <a href="https://electrical.codidact.com/help/arduino">Arduino</a> questions are off topic.
<li>URGENT!!!
Not our problem.
<li>What's the answer to this homework?
Again, this site is about learning. Just giving you the answer to a homework question defeats that, and is not allowed.
It is possible to ask about a homework question, explain what your thought process is, and where exactly you are stuck. If done right, we can try to guide you to discover the solution yourself. This is tricky. Be careful.
Always be honest about it being a homework problem. Most people you are asking have taken the same course you're taking and have done the homework. We know what homework looks like. Trying to disguise it is a great way to eliminate any good will that might have come your way.
</ul>
#10: Post edited
by
Olin Lathrop
·
2020-06-11T13:28:47Z (over 4 years ago)
#9: Post edited
by
Olin Lathrop
·
2020-06-09T16:20:12Z (over 4 years ago)
This site is about <i>Electrical Engineering</i> (opamps, microcontrollers, etc) and <i>Electric Power Engineering</i> (utility-scale power generation, transmission, etc). These names may be somewhat different around the world.
<h1>On-topic</h1>
Most questions that arise in the course of performing such engineering (with a few exceptions, see below) are on topic. This includes, for example:<ul>
<li>The design of circuits.
<li>The theory of circuits.
<li>Tools used in the course of the above.
Tools can be both hardware (soldering iron, oscilloscope) and software (schematic capture, simulation).
<li>Components used in a circuit.
<li>The physics behind how circuits and circuit components work.
<li>Signal processing.
<li>Control theory.
<li>Power generation and transmission.
<li>Microcontroller, FPGAs.
<li>Firmware and software.
This must be relevant to specific hardware, or about issues due to hardware limitations.
</ul>
This isn't meant to be an exhaustive list, but hopefully you get the idea. Stay within the spirit of the above, and you'll generally be fine. We have no interest in engaging rules-lawyers.
Sometimes there are legitimate gray areas. These are discussed in meta to find the consensus of the users.
<h1>Off-topic</h1>
The question and answer format of this site means it's not suited for certain topics or types of questions. Other topics are not allowed to keep the site focused on its purpose and reduce what most users would consider noise:<ul>
<li>Shopping questions.
What parts are available and where they are available changes too fast, and there is no single right answer. Answers are often opinion-based and devolve to popularity contests. As a result, we don't allow such questions.
We recognize that sourcing parts is an important part of engineering, but regardless, we're just not going to get into that here.
<li>High-level use of electrical devices.
If your question treats a device like a black box and isn't about its theory of operation or its design tradeoffs, then it's very likely off topic.
There are some exceptions with the techniques of using tools specific to electronics, but don't go too far with this. We are not the help desk for your oscilloscope, but asking about how to use a scope to see a particular waveform might be OK.
<li>Consumer "electronics".
This is really a special case of the previous item, but it happens often enough to point out explicitly. This is not the place to ask how to set the clock in your microwave oven.
<li>No interest in understanding or learning, <i>"Just gimme da anser!"</i>
There has to be some element of engineering, theory, underlying physics, etc, in every question. This is why most <a href="https://electrical.codidact.com/help/arduino">Arduino</a> questions are off topic.
<li>URGENT!!!
Not our problem.
<li>What's the answer to this homework?
Again, this site is about learning. Just giving you the answer to a homework question defeats that, and is not allowed.
It is possible to ask about a homework question, explain what your thought process is, and where exactly you are stuck. If done right, we can try to guide you to discover the solution yourself. This is tricky. Be careful.
Always be honest about it being a homework problem. Most people you are asking have taken the same course you're taking and have done the homework. We know what homework looks like. Trying to disguise it is a great way to eliminate any good will that might have come your way.
</ul>
This site is about <i>Electrical Engineering</i> (opamps, microcontrollers, etc) and <i>Electric Power Engineering</i> (utility-scale power generation, transmission, etc). These names may be somewhat different around the world.
<h1>On-topic</h1>
Most questions that arise in the course of performing such engineering (with a few exceptions, see below) are on topic. This includes, for example:<ul>
<li>The design of circuits.
<li>The theory of circuits.
<li>Tools used in the course of the above.
Tools can be both hardware (soldering iron, oscilloscope) and software (schematic capture, simulation).
<li>Components used in a circuit.
<li>The physics behind how circuits and circuit components work.
<li>Signal processing.
<li>Control theory.
<li>Power generation and transmission.
<li>Microcontrollers, FPGAs.
<li>Firmware and software.
This must be relevant to specific hardware, or about issues due to hardware limitations.
</ul>
This isn't meant to be an exhaustive list, but hopefully you get the idea. Stay within the spirit of the above, and you'll generally be fine. We have no interest in engaging rules-lawyers.
Sometimes there are legitimate gray areas. These are discussed in meta to find the consensus of the users.
<h1>Off-topic</h1>
The question and answer format of this site means it's not suited for certain topics or types of questions. Other topics are not allowed to keep the site focused on its purpose and reduce what most users would consider noise:<ul>
<li>Shopping questions.
What parts are available and where they are available changes too fast, and there is no single right answer. Answers are often opinion-based and devolve to popularity contests. As a result, we don't allow such questions.
We recognize that sourcing parts is an important part of engineering, but regardless, we're just not going to get into that here.
<li>High-level use of electrical devices.
If your question treats a device like a black box and isn't about its theory of operation or its design tradeoffs, then it's very likely off topic.
There are some exceptions with the techniques of using tools specific to electronics, but don't go too far with this. We are not the help desk for your oscilloscope, but asking about how to use a scope to see a particular waveform might be OK.
<li>Consumer "electronics".
This is really a special case of the previous item, but it happens often enough to point out explicitly. This is not the place to ask how to set the clock in your microwave oven.
<li>No interest in understanding or learning, <i>"Just gimme da anser!"</i>
There has to be some element of engineering, theory, underlying physics, etc, in every question. This is why most <a href="https://electrical.codidact.com/help/arduino">Arduino</a> questions are off topic.
<li>URGENT!!!
Not our problem.
<li>What's the answer to this homework?
Again, this site is about learning. Just giving you the answer to a homework question defeats that, and is not allowed.
It is possible to ask about a homework question, explain what your thought process is, and where exactly you are stuck. If done right, we can try to guide you to discover the solution yourself. This is tricky. Be careful.
Always be honest about it being a homework problem. Most people you are asking have taken the same course you're taking and have done the homework. We know what homework looks like. Trying to disguise it is a great way to eliminate any good will that might have come your way.
</ul>
#8: Post edited
by
Olin Lathrop
·
2020-06-09T15:46:18Z (over 4 years ago)
This site is about <i>Electrical Engineering</i> (opamps, microcontrollers, etc) and <i>Electric Power Engineering</i> (utility-scale power generation, transmission, etc). These names may be somewhat different around the world.
<h1>On-topic</h1>
Most questions that arise in the course of performing such engineering (with a few exceptions, see below) are on topic. This includes, for example:<ul>
<li>The design of circuits.
<li>The theory of circuits.
<li>Tools used in the course of the above.
Tools can be both hardware (soldering iron, oscilloscope) and software (schematic capture, simulation).
<li>Components used in a circuit.
<li>The physics behind how circuits and circuit components work.
<li>Signal processing.
<li>Control theory.
<li>Power generation and transmission.
<li>Microcontroller, FPGAs.
<li>Firmware and software.
This must be relevant to specific hardware, or about issues due to hardware limitations.
</ul>
This isn't meant to be an exhaustive list, but hopefully you get the idea. Stay within the spirit of the above, and you'll generally be fine. We have no interest in engaging rules-lawyers.
Sometimes there are legitimate gray areas. These are discussed in meta to find the consensus of the users.
<h1>Off-topic</h1>
The question and answer format of this site means it's not suited for certain topics or types of questions. Other topics are not allowed to keep the site focused on its purpose and reduce what most users would consider noise:<ul>
<li>Shopping questions.
What parts are available and where they are available changes too fast, and there is no single right answer. Answers are often opinion-based and devolve to popularity contests. As a result, we don't allow such questions.
We recognize that sourcing parts is an important part of engineering, but regardless, we're just not going to get into that here.
<li>High-level use of electrical devices.
If your question treats a device like a black box and isn't about its theory of operation or its design tradeoffs, then it's very likely off topic.
There are some exceptions with the techniques of using tools specific to electronics, but don't go too far with this. We are not the help desk for your oscilloscope, but asking about how to use a scope to see a particular waveform might be OK.
<li>Consumer "electronics".
This is really a special case of the previous item, but it happens often enough to point out explicitly. This is not the place to ask how to set the clock in your microwave oven.
<li>No interest in understanding or learning, <i>"Just gimme da anser!"</i>
There has to be some element of engineering, theory, underlying physics, etc, in every question. This is why most Arduino questions (see below) are off topic.
<li>URGENT!!!
Not our problem.
<li>What's the answer to this homework?
Again, this site is about learning. Just giving you the answer to a homework question defeats that, and is not allowed.
It is possible to ask about a homework question, explain what your thought process is, and where exactly you are stuck. If done right, we can try to guide you to discover the solution yourself. This is tricky. Be careful.
Always be honest about it being a homework problem. Most people you are asking have taken the same course you're taking and have done the homework. We know what homework looks like. Trying to disguise it is a great way to eliminate any good will that might have come your way.
</ul>
This site is about <i>Electrical Engineering</i> (opamps, microcontrollers, etc) and <i>Electric Power Engineering</i> (utility-scale power generation, transmission, etc). These names may be somewhat different around the world.
<h1>On-topic</h1>
Most questions that arise in the course of performing such engineering (with a few exceptions, see below) are on topic. This includes, for example:<ul>
<li>The design of circuits.
<li>The theory of circuits.
<li>Tools used in the course of the above.
Tools can be both hardware (soldering iron, oscilloscope) and software (schematic capture, simulation).
<li>Components used in a circuit.
<li>The physics behind how circuits and circuit components work.
<li>Signal processing.
<li>Control theory.
<li>Power generation and transmission.
<li>Microcontroller, FPGAs.
<li>Firmware and software.
This must be relevant to specific hardware, or about issues due to hardware limitations.
</ul>
This isn't meant to be an exhaustive list, but hopefully you get the idea. Stay within the spirit of the above, and you'll generally be fine. We have no interest in engaging rules-lawyers.
Sometimes there are legitimate gray areas. These are discussed in meta to find the consensus of the users.
<h1>Off-topic</h1>
The question and answer format of this site means it's not suited for certain topics or types of questions. Other topics are not allowed to keep the site focused on its purpose and reduce what most users would consider noise:<ul>
<li>Shopping questions.
What parts are available and where they are available changes too fast, and there is no single right answer. Answers are often opinion-based and devolve to popularity contests. As a result, we don't allow such questions.
We recognize that sourcing parts is an important part of engineering, but regardless, we're just not going to get into that here.
<li>High-level use of electrical devices.
If your question treats a device like a black box and isn't about its theory of operation or its design tradeoffs, then it's very likely off topic.
There are some exceptions with the techniques of using tools specific to electronics, but don't go too far with this. We are not the help desk for your oscilloscope, but asking about how to use a scope to see a particular waveform might be OK.
<li>Consumer "electronics".
This is really a special case of the previous item, but it happens often enough to point out explicitly. This is not the place to ask how to set the clock in your microwave oven.
<li>No interest in understanding or learning, <i>"Just gimme da anser!"</i>
There has to be some element of engineering, theory, underlying physics, etc, in every question. This is why most <a href="https://electrical.codidact.com/help/arduino">Arduino</a> questions are off topic.
<li>URGENT!!!
Not our problem.
<li>What's the answer to this homework?
Again, this site is about learning. Just giving you the answer to a homework question defeats that, and is not allowed.
It is possible to ask about a homework question, explain what your thought process is, and where exactly you are stuck. If done right, we can try to guide you to discover the solution yourself. This is tricky. Be careful.
Always be honest about it being a homework problem. Most people you are asking have taken the same course you're taking and have done the homework. We know what homework looks like. Trying to disguise it is a great way to eliminate any good will that might have come your way.
</ul>
#7: Post edited
by
Olin Lathrop
·
2020-06-09T15:42:54Z (over 4 years ago)
This site is about <i>Electrical Engineering</i> (opamps, microcontrollers, etc) and <i>Electric Power Engineering</i> (utility-scale power generation, transmission, etc). These names may be somewhat different around the world.
<h1>On-topic</h1>
Most questions that arise in the course of performing such engineering (with a few exceptions, see below) are on topic. This includes, for example:<ul>
<li>The design of circuits.
<li>The theory of circuits.
<li>Tools used in the course of the above.
Tools can be both hardware (soldering iron, oscilloscope) and software (schematic capture, simulation).
<li>Components used in a circuit.
<li>The physics behind how circuits and circuit components work.
<li>Signal processing.
<li>Control theory.
<li>Power generation and transmission.
<li>Microcontroller, FPGAs.
<li>Firmware and software.
This must be relevant to specific hardware, or about issues due to hardware limitations.
</ul>
This isn't meant to be an exhaustive list, but hopefully you get the idea. Stay within the spirit of the above, and you'll generally be fine. We have no interest in engaging rules-lawyers.
Sometimes there are legitimate gray areas. These are discussed in meta to find the consensus of the users.
<h1>Off-topic</h1>
The question and answer format of this site means it's not suited for certain topics or types of questions. Other topics are not allowed to keep the site focused on its purpose and reduce what most users would consider noise:<ul>
<li>Shopping questions.
What parts are available and where they are available changes too fast, and there is no single right answer. Answers are often opinion-based and devolve to popularity contests. As a result, we don't allow such questions.
We recognize that sourcing parts is an important part of engineering, but regardless, we're just not going to get into that here.
<li>High-level use of electrical devices.
If your question treats a device like a black box and isn't about its theory of operation or its design tradeoffs, then it's very likely off topic.
There are some exceptions with the techniques of using tools specific to electronics, but don't go too far with this. We are not the help desk for your oscilloscope, but asking about how to use a scope to see a particular waveform might be OK.
<li>Consumer "electronics".
This is really a special case of the previous item, but it happens often enough to point out explicitly. This is not the place to ask how to set the clock in your microwave oven.
<li>No interest in understanding or learning, <i>"Just gimme da anser!"</i>
There has to be some element of engineering, theory, underlying physics, etc, in every question. This is why most Arduino questions (see below) are off topic.
<li>URGENT!!!
Not our problem.
<li>What's the answer to this homework?
Again, this site is about learning. Just giving you the answer to a homework question defeats that, and is not allowed.
It is possible to ask about a homework question, explain what your thought process is, and where exactly you are stuck. If done right, we can try to guide you to discover the solution yourself. This is tricky. Be careful.
Always be honest about it being a homework problem. Most people you are asking have taken the same course you're taking and have done the homework. We know what homework looks like. Trying to disguise it is a great way to eliminate any good will that might have come your way.
</ul>
<h1>Arduinos</h1>
Everything in this section follows from the general rules above. However, this is such a common case that we mention it explicitly.
The point of Arduinos is to add layers of abstraction above a microcontroller so that you can get some results quickly without having to know what is really going on. That's fine and quite useful by itself. We don't have a problem with Arduinos (and similar platforms directly).
However, this site is about learning and understanding. Many Arduino users are Arduino users specifically to avoid that learning and understanding, to get results quickly. That's fine, but not here.
Wanting to drive a car without being bothered with how the engine works or the design tradeoffs of the braking system is fine by itself, but that's not what <i>this</i> site is about. Asking about how to accomplish something with an Arduino is off topic because it's not about electronics or its theory, and is generally not aimed at understanding.
If you've tinkered with Arduinos a bit and want to understand what's going on underneath, then your question may be on topic. However, then it's not about the Arduino part, but the underlying microcontroller and circuit around it. That's what we're looking for.
If you want to ask something related to an Arduino, here is a checklist to follow first:<ol>
<li>Does it matter that it's an Arduino versus some other microcontroller development board?
If yes, STOP. If you can replace "Arduino" in your question with "microcontroller development board", then do so and you may proceed.
<li>Is this about getting the Arduino to do a particular thing?
If yes, STOP. This is a "gimme da answer" question. If instead you are looking for insight <i>how</i> or <i>why</i> it works, then you may proceed.
<li>Is this about what "shield" to use?
STOP. Just STOP.
<li>Does your question use the word "shield" to mean a daughter board specific to the Arduino ecosystem?
Replace "shield" with "daughter board". If the question no longer makes sense, STOP.
<li>Does your question use the word "sketch" to refer to firmware?
Replace "sketch" with "firmware". If the question no longer makes sense, STOP.
<li>Congratulations, you may actually have a valid Arduino-motivated question for this site.
<ul>
This site is about <i>Electrical Engineering</i> (opamps, microcontrollers, etc) and <i>Electric Power Engineering</i> (utility-scale power generation, transmission, etc). These names may be somewhat different around the world.
<h1>On-topic</h1>
Most questions that arise in the course of performing such engineering (with a few exceptions, see below) are on topic. This includes, for example:<ul>
<li>The design of circuits.
<li>The theory of circuits.
<li>Tools used in the course of the above.
Tools can be both hardware (soldering iron, oscilloscope) and software (schematic capture, simulation).
<li>Components used in a circuit.
<li>The physics behind how circuits and circuit components work.
<li>Signal processing.
<li>Control theory.
<li>Power generation and transmission.
<li>Microcontroller, FPGAs.
<li>Firmware and software.
This must be relevant to specific hardware, or about issues due to hardware limitations.
</ul>
This isn't meant to be an exhaustive list, but hopefully you get the idea. Stay within the spirit of the above, and you'll generally be fine. We have no interest in engaging rules-lawyers.
Sometimes there are legitimate gray areas. These are discussed in meta to find the consensus of the users.
<h1>Off-topic</h1>
The question and answer format of this site means it's not suited for certain topics or types of questions. Other topics are not allowed to keep the site focused on its purpose and reduce what most users would consider noise:<ul>
<li>Shopping questions.
What parts are available and where they are available changes too fast, and there is no single right answer. Answers are often opinion-based and devolve to popularity contests. As a result, we don't allow such questions.
We recognize that sourcing parts is an important part of engineering, but regardless, we're just not going to get into that here.
<li>High-level use of electrical devices.
If your question treats a device like a black box and isn't about its theory of operation or its design tradeoffs, then it's very likely off topic.
There are some exceptions with the techniques of using tools specific to electronics, but don't go too far with this. We are not the help desk for your oscilloscope, but asking about how to use a scope to see a particular waveform might be OK.
<li>Consumer "electronics".
This is really a special case of the previous item, but it happens often enough to point out explicitly. This is not the place to ask how to set the clock in your microwave oven.
<li>No interest in understanding or learning, <i>"Just gimme da anser!"</i>
There has to be some element of engineering, theory, underlying physics, etc, in every question. This is why most Arduino questions (see below) are off topic.
<li>URGENT!!!
Not our problem.
<li>What's the answer to this homework?
Again, this site is about learning. Just giving you the answer to a homework question defeats that, and is not allowed.
It is possible to ask about a homework question, explain what your thought process is, and where exactly you are stuck. If done right, we can try to guide you to discover the solution yourself. This is tricky. Be careful.
Always be honest about it being a homework problem. Most people you are asking have taken the same course you're taking and have done the homework. We know what homework looks like. Trying to disguise it is a great way to eliminate any good will that might have come your way.
</ul>
#6: Post edited
by
Olin Lathrop
·
2020-06-09T15:36:17Z (over 4 years ago)
This site is about <i>Electrical Engineering</i> (opamps, microcontrollers, etc) and <i>Electric Power Engineering</i> (utility-scale power generation, transmission, etc). These names may be somewhat different around the world.
<h1>On-topic</h1>
Most questions that arise in the course of performing such engineering (with a few exceptions, see below) are on topic. This includes, for example:<ul>
<li>The design of circuits.
<li>The theory of circuits.
<li>Tools used in the course of the above.
Tools can be both hardware (soldering iron, oscilloscope) and software (schematic capture, simulation).
<li>Components used in a circuit.
<li>The physics behind how circuits and circuit components work.
<li>Signal processing.
<li>Control theory.
<li>Power generation and transmission.
<li>Microcontroller, FPGAs.
<li>Firmware and software.
This must be relevant to specific hardware, or about issues due to hardware limitations.
</ul>
This isn't meant to be an exhaustive list, but hopefully you get the idea. Stay within the spirit of the above, and you'll generally be fine. We have no interest in engaging rules-lawyers.
Sometimes there are legitimate gray areas. These are discussed in meta to find the consensus of the users.
<h1>Off-topic</h1>
The question and answer format of this site means it's not suited for certain topics or types of questions. Other topics are not allowed to keep the site focused on its purpose and reduce what most users would consider noise:<ul>
<li>Shopping questions.
What parts are available and where they are available changes too fast, and there is no single right answer. Answers are often opinion-based and devolve to popularity contests. As a result, we don't allow such questions.
We recognize that sourcing parts is an important part of engineering, but regardless, we're just not going to get into that here.
<li>High-level use of electrical devices.
If your question treats a device like a black box and isn't about its theory of operation or its design tradeoffs, then it's very likely off topic.
There are some exceptions with the techniques of using tools specific to electronics, but don't go too far with this. We are not the help desk for your oscilloscope, but asking about how to use a scope to see a particular waveform might be OK.
<li>Consumer "electronics".
This is really a special case of the previous item, but it happens often enough to point out explicitly. This is not the place to ask how to set the clock in your microwave oven.
<li>No interest in understanding or learning, <i>"Just gimme da anser!"</i>
There has to be some element of engineering, theory, underlying physics, etc, in every question. This is why most Arduino questions (see below) are off topic.
<li>URGENT!!!
Not our problem.
<li>What's the answer to this homework?
Again, this site is about learning. Just giving you the answer to a homework question defeats that, and is not allowed.
It is possible to ask about a homework question, explain what your thought process is, and where exactly you are stuck. If done right, we can try to guide you to discover the solution yourself. This is tricky. Be careful.
Always be honest about it being a homework problem. Most people you are asking have taken the same course you're taking and have done the homework. We know what homework looks like. Trying to disguise it is a great way to eliminate any good will that might have come your way.
</ul>
<h1>Arduinos</h1>
Everything in this section follows from the general rules above. However, this is such a common case that we mention it explicitly.
The point of Arduinos is to add layers of abstraction above a microcontroller so that you can get some results quickly without having to know what is really going on. That's fine and quite useful by itself. We don't have a problem with Arduinos (and similar platforms directly).
However, this site is about learning and understanding. Many Arduino users are Arduino users specifically to avoid that learning and understanding, to get results quickly. That's fine, but not here.
Wanting to drive a car without being bothered with how the engine works or the design tradeoffs of the braking system is fine by itself, but that's not what <i>this</i> site is about. Asking about how to accomplish something with an Arduino is off topic because it's not about electronics or its theory, and is generally not aimed at understanding.
If you've tinkered with Arduinos a bit and want to understand what's going on underneath, then your question may be on topic. However, then it's not about the Arduino part, but the underlying microcontroller and circuit around it. That's what we're looking for.
If you want to ask something related to an Arduino, here is a checklist to follow first:<ol>
<li>Does it matter that it's an Arduino versus some other microcontroller development board?
If yes, STOP. If you can replace "Arduino" in your question with "microcontroller development board", then you may proceed.
<li>Is this about getting the Arduino to do a particular thing?
If yes, STOP. This is a "gimme da answer" question. If instead you are looking for insight <i>how</i> or <i>why</i> it works, then you may proceed.
<li>Is this about what "shield" to use?
STOP. Just STOP.
<li>Does your question use the word "shield" to mean a daughter board specific to the Arduino ecosystem?
Replace "shield" with "daughter board". If the question no longer makes sense, STOP.
<li>Does your question use the word "sketch" to refer to firmware?
Replace "sketch" with "firmware". If the question no longer makes sense, STOP.
<li>Congratulations, you may actually have a valid Arduino-motivated question for this site.
<ul>
This site is about <i>Electrical Engineering</i> (opamps, microcontrollers, etc) and <i>Electric Power Engineering</i> (utility-scale power generation, transmission, etc). These names may be somewhat different around the world.
<h1>On-topic</h1>
Most questions that arise in the course of performing such engineering (with a few exceptions, see below) are on topic. This includes, for example:<ul>
<li>The design of circuits.
<li>The theory of circuits.
<li>Tools used in the course of the above.
Tools can be both hardware (soldering iron, oscilloscope) and software (schematic capture, simulation).
<li>Components used in a circuit.
<li>The physics behind how circuits and circuit components work.
<li>Signal processing.
<li>Control theory.
<li>Power generation and transmission.
<li>Microcontroller, FPGAs.
<li>Firmware and software.
This must be relevant to specific hardware, or about issues due to hardware limitations.
</ul>
This isn't meant to be an exhaustive list, but hopefully you get the idea. Stay within the spirit of the above, and you'll generally be fine. We have no interest in engaging rules-lawyers.
Sometimes there are legitimate gray areas. These are discussed in meta to find the consensus of the users.
<h1>Off-topic</h1>
The question and answer format of this site means it's not suited for certain topics or types of questions. Other topics are not allowed to keep the site focused on its purpose and reduce what most users would consider noise:<ul>
<li>Shopping questions.
What parts are available and where they are available changes too fast, and there is no single right answer. Answers are often opinion-based and devolve to popularity contests. As a result, we don't allow such questions.
We recognize that sourcing parts is an important part of engineering, but regardless, we're just not going to get into that here.
<li>High-level use of electrical devices.
If your question treats a device like a black box and isn't about its theory of operation or its design tradeoffs, then it's very likely off topic.
There are some exceptions with the techniques of using tools specific to electronics, but don't go too far with this. We are not the help desk for your oscilloscope, but asking about how to use a scope to see a particular waveform might be OK.
<li>Consumer "electronics".
This is really a special case of the previous item, but it happens often enough to point out explicitly. This is not the place to ask how to set the clock in your microwave oven.
<li>No interest in understanding or learning, <i>"Just gimme da anser!"</i>
There has to be some element of engineering, theory, underlying physics, etc, in every question. This is why most Arduino questions (see below) are off topic.
<li>URGENT!!!
Not our problem.
<li>What's the answer to this homework?
Again, this site is about learning. Just giving you the answer to a homework question defeats that, and is not allowed.
It is possible to ask about a homework question, explain what your thought process is, and where exactly you are stuck. If done right, we can try to guide you to discover the solution yourself. This is tricky. Be careful.
Always be honest about it being a homework problem. Most people you are asking have taken the same course you're taking and have done the homework. We know what homework looks like. Trying to disguise it is a great way to eliminate any good will that might have come your way.
</ul>
<h1>Arduinos</h1>
Everything in this section follows from the general rules above. However, this is such a common case that we mention it explicitly.
The point of Arduinos is to add layers of abstraction above a microcontroller so that you can get some results quickly without having to know what is really going on. That's fine and quite useful by itself. We don't have a problem with Arduinos (and similar platforms directly).
However, this site is about learning and understanding. Many Arduino users are Arduino users specifically to avoid that learning and understanding, to get results quickly. That's fine, but not here.
Wanting to drive a car without being bothered with how the engine works or the design tradeoffs of the braking system is fine by itself, but that's not what <i>this</i> site is about. Asking about how to accomplish something with an Arduino is off topic because it's not about electronics or its theory, and is generally not aimed at understanding.
If you've tinkered with Arduinos a bit and want to understand what's going on underneath, then your question may be on topic. However, then it's not about the Arduino part, but the underlying microcontroller and circuit around it. That's what we're looking for.
If you want to ask something related to an Arduino, here is a checklist to follow first:<ol>
<li>Does it matter that it's an Arduino versus some other microcontroller development board?
If yes, STOP. If you can replace "Arduino" in your question with "microcontroller development board", then do so and you may proceed.
<li>Is this about getting the Arduino to do a particular thing?
If yes, STOP. This is a "gimme da answer" question. If instead you are looking for insight <i>how</i> or <i>why</i> it works, then you may proceed.
<li>Is this about what "shield" to use?
STOP. Just STOP.
<li>Does your question use the word "shield" to mean a daughter board specific to the Arduino ecosystem?
Replace "shield" with "daughter board". If the question no longer makes sense, STOP.
<li>Does your question use the word "sketch" to refer to firmware?
Replace "sketch" with "firmware". If the question no longer makes sense, STOP.
<li>Congratulations, you may actually have a valid Arduino-motivated question for this site.
<ul>
#5: Post edited
by
Olin Lathrop
·
2020-06-09T15:35:04Z (over 4 years ago)
This site is about <i>Electrical Engineering</i> (opamps, microcontrollers, etc) and <i>Electric Power Engineering</i> (utility-scale power generation, transmission, etc). These names may be somewhat different around the world.
<h1>On-topic</h1>
Most questions that arise in the course of performing such engineering (with a few exceptions, see below) are on topic. This includes, for example:<ul>
<li>The design of circuits.
<li>The theory of circuits.
<li>Tools used in the course of the above.
Tools can be both hardware (soldering iron, oscilloscope) and software (schematic capture, simulation).
<li>Components used in a circuit.
<li>The physics behind how circuits and circuit components work.
<li>Signal processing.
<li>Control theory.
<li>Power generation and transmission.
<li>Microcontroller, FPGAs.
<li>Firmware and software.
This must be relevant to specific hardware, or about issues due to hardware limitations.
</ul>
This isn't meant to be an exhaustive list, but hopefully you get the idea. Stay within the spirit of the above, and you'll generally be fine. We have no interest in engaging rules-lawyers.
Sometimes there are legitimate gray areas. These are discussed in meta to find the consensus of the users.
<h1>Off-topic</h1>
The question and answer format of this site means it's not suited for certain topics or types of questions. Other topics are not allowed to keep the site focused on its purpose and reduce what most users would consider noise:<ul>
<li>Shopping questions.
What parts are available and where they are available changes too fast, and there is no single right answer. Answers are often opinion-based and devolve to popularity contests. As a result, we don't allow such questions.
We recognize that sourcing parts is an important part of engineering, but regardless, we're just not going to get into that here.
<li>High-level use of electrical devices.
If your question treats a device like a black box and isn't about its theory of operation or its design tradeoffs, then it's very likely off topic.
There are some exceptions with the techniques of using tools specific to electronics, but don't go too far with this. We are not the help desk for your oscilloscope, but asking about how to use a scope to see a particular waveform might be OK.
<li>Consumer "electronics".
This is really a special case of the previous item, but it happens often enough to point out explicitly. This is not the place to ask how to set the clock in your microwave oven.
<li>No interest in understanding or learning, <i>"Just gimme da anser!"</i>
There has to be some element of engineering, theory, underlying physics, etc, in every question. This is why most Arduino questions (see below) are off topic.
<li>URGENT!!!
Not our problem.
<li>What's the answer to this homework?
Again, this site is about learning. Just giving you the answer to a homework question defeats that, and is not allowed.
It is possible to ask about a homework question, explain what your thought process is, and where exactly you are stuck. If done right, we can try to guide you to discover the solution yourself. This is tricky. Be careful.
Always be honest about it being a homework problem. Most people you are asking have taken the same course you're taking and have done the homework. We know what homework looks like. Trying to disguise it is a great way to eliminate any good will that might have come your way.
</ul>
<h1>Arduinos</h1>
Everything in this section follows from the general rules above. However, this is such a common case that we mention it explicitly.
The point of Arduinos is to add layers of abstraction above a microcontroller so that you can get some results quickly without having to know what is really going on. That's fine and quite useful by itself. We don't have a problem with Arduinos (and similar platforms directly).
However, this site is about learning and understanding. Many Arduino users are Arduino users specifically to avoid that learning and understanding, to get results quickly. That's fine, but not here.
Wanting to drive a car without being bothered with how the engine works or the design tradeoffs of the braking system is fine by itself, but that's not what <i>this</i> site is about. Asking about how to accomplish something with an Arduino is off topic because it's not about electronics or its theory, and is generally not aimed at understanding.
If you've tinkered with Arduinos a bit and want to understand what's going on underneath, then your question may be on topic. However, then it's not about the Arduino part, but the underlying microcontroller and circuit around it.
If you want to ask something related to an Arduino, here is a checklist to follow first:<ol>
<li>Does it matter that it's an Arduino versus some other microcontroller development board?
If yes, STOP. If you can replace "Arduino" in your question with "microcontroller development board", then you may proceed.
<li>Is this about getting the Arduino to do a particular thing?
If yes, STOP. This is a "gimme da answer" question. If instead you are looking for insight <i>how</i> or <i>why</i> it works, then you may proceed.
<li>Is this about what "shield" to use?
STOP. Just STOP.
<li>Does your question use the word "shield" to mean a daughter board specific to the Arduino ecosystem?
Replace "shield" with "daughter board". If the question no longer makes sense, STOP.
<li>Does your question use the word "sketch" to refer to firmware?
Replace "sketch" with "firmware". If the question no longer makes sense, STOP.
<li>Congratulations, you may actually have a valid Arduino-motivated question for this site.
<ul>
This site is about <i>Electrical Engineering</i> (opamps, microcontrollers, etc) and <i>Electric Power Engineering</i> (utility-scale power generation, transmission, etc). These names may be somewhat different around the world.
<h1>On-topic</h1>
Most questions that arise in the course of performing such engineering (with a few exceptions, see below) are on topic. This includes, for example:<ul>
<li>The design of circuits.
<li>The theory of circuits.
<li>Tools used in the course of the above.
Tools can be both hardware (soldering iron, oscilloscope) and software (schematic capture, simulation).
<li>Components used in a circuit.
<li>The physics behind how circuits and circuit components work.
<li>Signal processing.
<li>Control theory.
<li>Power generation and transmission.
<li>Microcontroller, FPGAs.
<li>Firmware and software.
This must be relevant to specific hardware, or about issues due to hardware limitations.
</ul>
This isn't meant to be an exhaustive list, but hopefully you get the idea. Stay within the spirit of the above, and you'll generally be fine. We have no interest in engaging rules-lawyers.
Sometimes there are legitimate gray areas. These are discussed in meta to find the consensus of the users.
<h1>Off-topic</h1>
The question and answer format of this site means it's not suited for certain topics or types of questions. Other topics are not allowed to keep the site focused on its purpose and reduce what most users would consider noise:<ul>
<li>Shopping questions.
What parts are available and where they are available changes too fast, and there is no single right answer. Answers are often opinion-based and devolve to popularity contests. As a result, we don't allow such questions.
We recognize that sourcing parts is an important part of engineering, but regardless, we're just not going to get into that here.
<li>High-level use of electrical devices.
If your question treats a device like a black box and isn't about its theory of operation or its design tradeoffs, then it's very likely off topic.
There are some exceptions with the techniques of using tools specific to electronics, but don't go too far with this. We are not the help desk for your oscilloscope, but asking about how to use a scope to see a particular waveform might be OK.
<li>Consumer "electronics".
This is really a special case of the previous item, but it happens often enough to point out explicitly. This is not the place to ask how to set the clock in your microwave oven.
<li>No interest in understanding or learning, <i>"Just gimme da anser!"</i>
There has to be some element of engineering, theory, underlying physics, etc, in every question. This is why most Arduino questions (see below) are off topic.
<li>URGENT!!!
Not our problem.
<li>What's the answer to this homework?
Again, this site is about learning. Just giving you the answer to a homework question defeats that, and is not allowed.
It is possible to ask about a homework question, explain what your thought process is, and where exactly you are stuck. If done right, we can try to guide you to discover the solution yourself. This is tricky. Be careful.
Always be honest about it being a homework problem. Most people you are asking have taken the same course you're taking and have done the homework. We know what homework looks like. Trying to disguise it is a great way to eliminate any good will that might have come your way.
</ul>
<h1>Arduinos</h1>
Everything in this section follows from the general rules above. However, this is such a common case that we mention it explicitly.
The point of Arduinos is to add layers of abstraction above a microcontroller so that you can get some results quickly without having to know what is really going on. That's fine and quite useful by itself. We don't have a problem with Arduinos (and similar platforms directly).
However, this site is about learning and understanding. Many Arduino users are Arduino users specifically to avoid that learning and understanding, to get results quickly. That's fine, but not here.
Wanting to drive a car without being bothered with how the engine works or the design tradeoffs of the braking system is fine by itself, but that's not what <i>this</i> site is about. Asking about how to accomplish something with an Arduino is off topic because it's not about electronics or its theory, and is generally not aimed at understanding.
If you've tinkered with Arduinos a bit and want to understand what's going on underneath, then your question may be on topic. However, then it's not about the Arduino part, but the underlying microcontroller and circuit around it. That's what we're looking for.
If you want to ask something related to an Arduino, here is a checklist to follow first:<ol>
<li>Does it matter that it's an Arduino versus some other microcontroller development board?
If yes, STOP. If you can replace "Arduino" in your question with "microcontroller development board", then you may proceed.
<li>Is this about getting the Arduino to do a particular thing?
If yes, STOP. This is a "gimme da answer" question. If instead you are looking for insight <i>how</i> or <i>why</i> it works, then you may proceed.
<li>Is this about what "shield" to use?
STOP. Just STOP.
<li>Does your question use the word "shield" to mean a daughter board specific to the Arduino ecosystem?
Replace "shield" with "daughter board". If the question no longer makes sense, STOP.
<li>Does your question use the word "sketch" to refer to firmware?
Replace "sketch" with "firmware". If the question no longer makes sense, STOP.
<li>Congratulations, you may actually have a valid Arduino-motivated question for this site.
<ul>
#4: Post edited
by
Olin Lathrop
·
2020-06-09T15:34:37Z (over 4 years ago)
This site is about <i>Electrical Engineering</i> (opamps, microcontrollers, etc) and <i>Electric Power Engineering</i> (utility-scale power generation, transmission, etc). These names may be somewhat different around the world.
<h1>On-topic</h1>
Most questions that arise in the course of performing such engineering (with a few exceptions, see below) are on topic. This includes, for example:<ul>
<li>The design of circuits.
<li>The theory of circuits.
<li>Tools used in the course of the above.
Tools can be both hardware (soldering iron, oscilloscope) and software (schematic capture, simulation).
<li>Components used in a circuit.
<li>The physics behind how circuits and circuit components work.
<li>Signal processing.
<li>Control theory.
<li>Power generation and transmission.
<li>Microcontroller, FPGAs.
<li>Firmware and software.
This must be relevant to specific hardware, or about issues due to hardware limitations.
</ul>
This isn't meant to be an exhaustive list, but hopefully you get the idea. Stay within the spirit of the above, and you'll generally be fine. We have no interest in engaging rules-lawyers.
Sometimes there are legitimate gray areas. These are discussed in meta to find the consensus of the users.
<h1>Off-topic</h1>
The question and answer format of this site means it's not suited for certain topics or types of questions. Other topics are not allowed to keep the site focused on its purpose and reduce what most users would consider noise:<ul>
<li>Shopping questions.
What parts are available and where they are available changes too fast, and there is no single right answer. Answers are often opinion-based and devolve to popularity contests. As a result, we don't allow such questions.
We recognize that sourcing parts is an important part of engineering, but regardless, we're just not going to get into that here.
<li>High-level use of electrical devices.
If your question treats a device like a black box and isn't about its theory of operation or its design tradeoffs, then it's very likely off topic.
There are some exceptions with the techniques of using tools specific to electronics, but don't go too far with this. We are not the help desk for your oscilloscope, but asking about how to use a scope to see a particular waveform might be OK.
<li>Consumer "electronics".
This is really a special case of the previous item, but it happens often enough to point out explicitly. This is not the place to ask how to set the clock in your microwave oven.
<li>No interest in understanding or learning, <i>"Just gimme da anser!"</i>
There has to be some element of engineering, theory, underlying physics, etc, in every question. This is why most Arduino questions (see below) are off topic.
<li>URGENT!!!
Not our problem.
<li>What's the answer to this homework?
Again, this site is about learning. Just giving you the answer to a homework question defeats that, and is not allowed.
It is possible to ask about a homework question, explain what your thought process is, and where exactly you are stuck. If done right, we can try to guide you to discover the solution yourself. This is tricky. Be careful.
Always be honest about it being a homework problem. Most people you are asking have taken the same course you're taking and have done the homework. We know what homework looks like. Trying to disguise it is a great way to eliminate any good will that might have come your way.
</ul>
<h1>Arduinos</h1>
Everything in this section follows from the general rules above. However, this is such a common case that we mention it explicitly.
The point of Arduinos is to add layers of abstraction above a microcontroller so that you can get some results quickly without having to know what is really going on. That's fine and quite useful by itself. We don't have a problem with Arduinos (and similar platforms directly).
However, this site is about learning and understanding. Many Arduino users are Arduino users specifically to avoid that learning and understanding, to get results quickly. That's fine, but not here.
Wanting to drive a car without being bothered with how the engine works or the design tradeoffs of the braking system is fine by itself, but that's not what <i>this</i> site is about. Asking about how to accomplish something with an Arduino is off topic because it's not about electronics or its theory, and is generally not aimed at understanding.
If you've tinkered with Arduinos a bit and want to understand what's going on underneath, then your question probably is on topic. However, then it's not about the Arduino part, but the underlying microcontroller and circuit around it.
If you want to ask something related to an Arduino, here is a checklist to follow first:<ol>
<li>Does it matter that it's an Arduino versus some other microcontroller development board?
If yes, STOP. If you can replace "Arduino" in your question with "microcontroller development board", then you may proceed.
<li>Is this about getting the Arduino to do a particular thing?
If yes, STOP. This is a "gimme da answer" question. If instead you are looking for insight <i>how</i> or <i>why</i> it works, then you may proceed.
<li>Is this about what "shield" to use?
STOP. Just STOP.
<li>Does your question use the word "shield" to mean a daughter board specific to the Arduino ecosystem?
Replace "shield" with "daughter board". If the question no longer makes sense, STOP.
<li>Does your question use the word "sketch" to refer to firmware?
Replace "sketch" with "firmware". If the question no longer makes sense, STOP.
<li>Congratulations, you may actually have a valid Arduino-motivated question for this site.
<ul>
This site is about <i>Electrical Engineering</i> (opamps, microcontrollers, etc) and <i>Electric Power Engineering</i> (utility-scale power generation, transmission, etc). These names may be somewhat different around the world.
<h1>On-topic</h1>
Most questions that arise in the course of performing such engineering (with a few exceptions, see below) are on topic. This includes, for example:<ul>
<li>The design of circuits.
<li>The theory of circuits.
<li>Tools used in the course of the above.
Tools can be both hardware (soldering iron, oscilloscope) and software (schematic capture, simulation).
<li>Components used in a circuit.
<li>The physics behind how circuits and circuit components work.
<li>Signal processing.
<li>Control theory.
<li>Power generation and transmission.
<li>Microcontroller, FPGAs.
<li>Firmware and software.
This must be relevant to specific hardware, or about issues due to hardware limitations.
</ul>
This isn't meant to be an exhaustive list, but hopefully you get the idea. Stay within the spirit of the above, and you'll generally be fine. We have no interest in engaging rules-lawyers.
Sometimes there are legitimate gray areas. These are discussed in meta to find the consensus of the users.
<h1>Off-topic</h1>
The question and answer format of this site means it's not suited for certain topics or types of questions. Other topics are not allowed to keep the site focused on its purpose and reduce what most users would consider noise:<ul>
<li>Shopping questions.
What parts are available and where they are available changes too fast, and there is no single right answer. Answers are often opinion-based and devolve to popularity contests. As a result, we don't allow such questions.
We recognize that sourcing parts is an important part of engineering, but regardless, we're just not going to get into that here.
<li>High-level use of electrical devices.
If your question treats a device like a black box and isn't about its theory of operation or its design tradeoffs, then it's very likely off topic.
There are some exceptions with the techniques of using tools specific to electronics, but don't go too far with this. We are not the help desk for your oscilloscope, but asking about how to use a scope to see a particular waveform might be OK.
<li>Consumer "electronics".
This is really a special case of the previous item, but it happens often enough to point out explicitly. This is not the place to ask how to set the clock in your microwave oven.
<li>No interest in understanding or learning, <i>"Just gimme da anser!"</i>
There has to be some element of engineering, theory, underlying physics, etc, in every question. This is why most Arduino questions (see below) are off topic.
<li>URGENT!!!
Not our problem.
<li>What's the answer to this homework?
Again, this site is about learning. Just giving you the answer to a homework question defeats that, and is not allowed.
It is possible to ask about a homework question, explain what your thought process is, and where exactly you are stuck. If done right, we can try to guide you to discover the solution yourself. This is tricky. Be careful.
Always be honest about it being a homework problem. Most people you are asking have taken the same course you're taking and have done the homework. We know what homework looks like. Trying to disguise it is a great way to eliminate any good will that might have come your way.
</ul>
<h1>Arduinos</h1>
Everything in this section follows from the general rules above. However, this is such a common case that we mention it explicitly.
The point of Arduinos is to add layers of abstraction above a microcontroller so that you can get some results quickly without having to know what is really going on. That's fine and quite useful by itself. We don't have a problem with Arduinos (and similar platforms directly).
However, this site is about learning and understanding. Many Arduino users are Arduino users specifically to avoid that learning and understanding, to get results quickly. That's fine, but not here.
Wanting to drive a car without being bothered with how the engine works or the design tradeoffs of the braking system is fine by itself, but that's not what <i>this</i> site is about. Asking about how to accomplish something with an Arduino is off topic because it's not about electronics or its theory, and is generally not aimed at understanding.
If you've tinkered with Arduinos a bit and want to understand what's going on underneath, then your question may be on topic. However, then it's not about the Arduino part, but the underlying microcontroller and circuit around it.
If you want to ask something related to an Arduino, here is a checklist to follow first:<ol>
<li>Does it matter that it's an Arduino versus some other microcontroller development board?
If yes, STOP. If you can replace "Arduino" in your question with "microcontroller development board", then you may proceed.
<li>Is this about getting the Arduino to do a particular thing?
If yes, STOP. This is a "gimme da answer" question. If instead you are looking for insight <i>how</i> or <i>why</i> it works, then you may proceed.
<li>Is this about what "shield" to use?
STOP. Just STOP.
<li>Does your question use the word "shield" to mean a daughter board specific to the Arduino ecosystem?
Replace "shield" with "daughter board". If the question no longer makes sense, STOP.
<li>Does your question use the word "sketch" to refer to firmware?
Replace "sketch" with "firmware". If the question no longer makes sense, STOP.
<li>Congratulations, you may actually have a valid Arduino-motivated question for this site.
<ul>
#3: Post edited
by
Olin Lathrop
·
2020-06-09T15:33:29Z (over 4 years ago)
This site is about <i>Electrical Engineering</i> (opamps, microcontrollers, etc) and <i>Electric Power Engineering</i> (utility-scale power generation, transmission, etc). These names may be somewhat different around the world.
<h1>On-topic</h1>
Most questions that arise in the course of performing such engineering (with a few exceptions, see below) are on topic. This includes, for example:<ul>
<li>The design of circuits.
<li>The theory of circuits.
<li>Tools used in the course of the above.
Tools can be both hardware (soldering iron, oscilloscope) and software (schematic capture, simulation).
<li>Components used in a circuit.
<li>The physics behind how circuits and circuit components work.
<li>Signal processing.
<li>Control theory.
<li>Power generation and transmission.
<li>Microcontroller, FPGAs.
<li>Firmware and software.
This must be relevant to specific hardware, or about issues due to hardware limitations.
</ul>
This isn't meant to be an exhaustive list, but hopefully you get the idea. Stay within the spirit of the above, and you'll generally be fine. We have no interest in engaging rules-lawyers.
Sometimes there are legitimate gray areas. These are discussed in meta to find the consensus of the users.
<h1>Off-topic</h1>
The question and answer format of this site means it's not suited for certain topics or types of questions. Other topics are not allowed to keep the site focused on its purpose and reduce what most users would consider noise:<ul>
<li>Shopping questions.
What parts are available and where they are available changes too fast, and there is no single right answer. Answers are often opinion-based and devolve to popularity contests. As a result, we don't allow such questions.
We recognize that sourcing parts is an important part of engineering, but regardless, we're just not going to get into that here.
<li>High-level use of electrical devices.
If your question treats a device like a black box and isn't about its theory of operation or its design tradeoffs, then it's very likely off topic.
There are some exceptions with the techniques of using tools specific to electronics, but don't go too far with this. We are not the help desk for your oscilloscope, but asking about how to use a scope to see a particular waveform might be OK.
<li>Consumer "electronics".
This is really a special case of the previous item, but it happens often enough to point out explicitly. This is not the place to ask how to set the clock in your microwave oven.
<li>No interest in understanding or learning, <i>"Just gimme da anser!"</i>
There has to be some element of engineering, theory, underlying physics, etc, in every question. This is why most Arduino questions (see below) are off topic.
<li>URGENT!!!
Not our problem.
<li>What's the answer to this homework?
Again, this site is about learning. Just giving you the answer to a homework question defeats that, and is not allowed.
It is possible to ask about a homework question, explain what your thought process is, and where exactly you are stuck. If done right, we can try to guide you to discover the solution yourself. This is tricky. Be careful.
Always be honest about it being a homework problem. Most people you are asking have taken the same course you're taking and have done the homework. We know what homework looks like. Trying to disguise it is a great way to eliminate any good will that might have come your way.
</ul>
<h1>Arduinos</h1>
Everything in this section follows from the general rules above. However, this is such a common case that we mention it explicitly.
The point of Arduinos is to add layers of abstraction above a microcontroller so that you can get some results quickly without having to know what is really going on. That's fine and quite useful by itself. We don't have a problem with Arduinos (and similar platforms directly).
This site is about learning and understanding. Many Arduino users are Arduino users specifically to avoid that learning and understanding, to get to results more quickly. That's fine, but not here.
Wanting to drive a car without being bothered with how the engine works or the design tradeoffs of the braking system is fine by itself, but that's not what <i>this</i> site is about. Asking about how to accomplish something with an Arduino is off topic because it's not about electronics or its theory, and is generally not aimed at understanding.
If you've tinkered with Arduinos a bit and want to understand what's going on underneath, then your question probably is on topic. However, then it's not about the Arduino part, but the underlying microcontroller and circuit around it.
If you want to ask something related to an Arduino, here is a checklist to follow first:<ol>
<li>Does it matter that it's an Arduino versus some other microcontroller development board?
If yes, STOP. If you can replace "Arduino" in your question with "microcontroller development board", then you may proceed.
<li>Is this about getting the Arduino to do a particular thing?
If yes, STOP. This is a "gimme da answer" question. If instead you are looking for insight <i>how</i> or <i>why</i> it works, then you may proceed.
<li>Is this about what "shield" to use?
STOP. Just STOP.
<li>Does your question use the word "shield" to mean a daughter board specific to the Arduino ecosystem?
Replace "shield" with "daughter board". If the question no longer makes sense, STOP.
<li>Does your question use the word "sketch" to refer to firmware?
Replace "sketch" with "firmware". If the question no longer makes sense, STOP.
<li>Congratulations, you may actually have a valid Arduino-motivated question for this site.
<ul>
This site is about <i>Electrical Engineering</i> (opamps, microcontrollers, etc) and <i>Electric Power Engineering</i> (utility-scale power generation, transmission, etc). These names may be somewhat different around the world.
<h1>On-topic</h1>
Most questions that arise in the course of performing such engineering (with a few exceptions, see below) are on topic. This includes, for example:<ul>
<li>The design of circuits.
<li>The theory of circuits.
<li>Tools used in the course of the above.
Tools can be both hardware (soldering iron, oscilloscope) and software (schematic capture, simulation).
<li>Components used in a circuit.
<li>The physics behind how circuits and circuit components work.
<li>Signal processing.
<li>Control theory.
<li>Power generation and transmission.
<li>Microcontroller, FPGAs.
<li>Firmware and software.
This must be relevant to specific hardware, or about issues due to hardware limitations.
</ul>
This isn't meant to be an exhaustive list, but hopefully you get the idea. Stay within the spirit of the above, and you'll generally be fine. We have no interest in engaging rules-lawyers.
Sometimes there are legitimate gray areas. These are discussed in meta to find the consensus of the users.
<h1>Off-topic</h1>
The question and answer format of this site means it's not suited for certain topics or types of questions. Other topics are not allowed to keep the site focused on its purpose and reduce what most users would consider noise:<ul>
<li>Shopping questions.
What parts are available and where they are available changes too fast, and there is no single right answer. Answers are often opinion-based and devolve to popularity contests. As a result, we don't allow such questions.
We recognize that sourcing parts is an important part of engineering, but regardless, we're just not going to get into that here.
<li>High-level use of electrical devices.
If your question treats a device like a black box and isn't about its theory of operation or its design tradeoffs, then it's very likely off topic.
There are some exceptions with the techniques of using tools specific to electronics, but don't go too far with this. We are not the help desk for your oscilloscope, but asking about how to use a scope to see a particular waveform might be OK.
<li>Consumer "electronics".
This is really a special case of the previous item, but it happens often enough to point out explicitly. This is not the place to ask how to set the clock in your microwave oven.
<li>No interest in understanding or learning, <i>"Just gimme da anser!"</i>
There has to be some element of engineering, theory, underlying physics, etc, in every question. This is why most Arduino questions (see below) are off topic.
<li>URGENT!!!
Not our problem.
<li>What's the answer to this homework?
Again, this site is about learning. Just giving you the answer to a homework question defeats that, and is not allowed.
It is possible to ask about a homework question, explain what your thought process is, and where exactly you are stuck. If done right, we can try to guide you to discover the solution yourself. This is tricky. Be careful.
Always be honest about it being a homework problem. Most people you are asking have taken the same course you're taking and have done the homework. We know what homework looks like. Trying to disguise it is a great way to eliminate any good will that might have come your way.
</ul>
<h1>Arduinos</h1>
Everything in this section follows from the general rules above. However, this is such a common case that we mention it explicitly.
The point of Arduinos is to add layers of abstraction above a microcontroller so that you can get some results quickly without having to know what is really going on. That's fine and quite useful by itself. We don't have a problem with Arduinos (and similar platforms directly).
However, this site is about learning and understanding. Many Arduino users are Arduino users specifically to avoid that learning and understanding, to get results quickly. That's fine, but not here.
Wanting to drive a car without being bothered with how the engine works or the design tradeoffs of the braking system is fine by itself, but that's not what <i>this</i> site is about. Asking about how to accomplish something with an Arduino is off topic because it's not about electronics or its theory, and is generally not aimed at understanding.
If you've tinkered with Arduinos a bit and want to understand what's going on underneath, then your question probably is on topic. However, then it's not about the Arduino part, but the underlying microcontroller and circuit around it.
If you want to ask something related to an Arduino, here is a checklist to follow first:<ol>
<li>Does it matter that it's an Arduino versus some other microcontroller development board?
If yes, STOP. If you can replace "Arduino" in your question with "microcontroller development board", then you may proceed.
<li>Is this about getting the Arduino to do a particular thing?
If yes, STOP. This is a "gimme da answer" question. If instead you are looking for insight <i>how</i> or <i>why</i> it works, then you may proceed.
<li>Is this about what "shield" to use?
STOP. Just STOP.
<li>Does your question use the word "shield" to mean a daughter board specific to the Arduino ecosystem?
Replace "shield" with "daughter board". If the question no longer makes sense, STOP.
<li>Does your question use the word "sketch" to refer to firmware?
Replace "sketch" with "firmware". If the question no longer makes sense, STOP.
<li>Congratulations, you may actually have a valid Arduino-motivated question for this site.
<ul>
#2: Post edited
by
Olin Lathrop
·
2020-06-09T15:32:21Z (over 4 years ago)
This site is about <i>Electrical Engineering</i> (opamps, microcontrollers, etc) and <i>Electric Power Engineering</i> (utility-scale power generation, transmission, etc). These names may be somewhat different around the world.
<h1>On-topic</h1>
Most questions that arise in the course of performing such engineering (with a few exceptions, see below) are on topic. This includes, for example:<ul>
<li>The design of circuits.
<li>The theory of circuits.
<li>Tools used in the course of the above.
Tools can be both hardware (soldering iron, oscilloscope) and software (schematic capture, simulation).
<li>Components used in a circuit.
<li>The physics behind how circuits and circuit components work.
<li>Signal processing.
<li>Control theory.
<li>Power generation and transmission.
<li>Microcontroller, FPGAs.
<li>Firmware and software.
This must be relevant to specific hardware, or about issues due to hardware limitations.
</ul>
This isn't meant to be an exhaustive list, but hopefully you get the idea. Stay within the spirit of the above, and you'll generally be fine. We have no interest in engaging rules-lawyers.
Sometimes there are legitimate gray areas. These are discussed in meta to find the consensus of the users.
<h1>Off-topic</h1>
The question and answer format of this site means it's not suited for certain topics or types of questions. Other topics are not allowed to keep the site focused on its purpose and reduce what most users would consider noise:<ul>
<li>Shopping questions.
What parts are available and where they are available changes too fast, and there is no single right answer. Answers are often opinion-based and devolve to popularity contests. As a result, we don't allow such questions.
We recognize that sourcing parts is an important part of engineering, but regardless, we're just not going to get into that here.
<li>High-level use of electrical devices.
If your question treats a device like a black box and isn't about its theory of operation or its design tradeoffs, then it's very likely off topic.
There are some exceptions with the techniques of using tools specific to electronics, but don't go too far with this. We are not the help desk for your oscilloscope, but asking about how to use a scope to see a particular waveform might be OK.
<li>Consumer "electronics".
This is really a special case of the previous item, but it happens often enough to point out explicitly. This is not the place to ask how to set the clock in your microwave oven.
<li>No interest in understanding or learning, <i>"Just gimme da anser!"</i>
There has to be some element of engineering, theory, underlying physics, etc, in every question. This is why most Arduino questions (see below) are off topic.
<li>URGENT!!!
Not our problem.
<li>What's the answer to this homework?
Again, this site is about learning. Just giving you the answer to a homework question defeats that, and is not allowed.
It is possible to ask about a homework question, explain what your thought process is, and where exactly you are stuck. If done right, we can try to guide you to discover the solution yourself. This is tricky. Be careful.
Always be honest about it being a homework problem. Most people you are asking have taken the same course you're taking and have done the homework. We know what homework looks like. Trying to disguise it is a great way to eliminate any good will that might have come your way.
</ul>
This site is about <i>Electrical Engineering</i> (opamps, microcontrollers, etc) and <i>Electric Power Engineering</i> (utility-scale power generation, transmission, etc). These names may be somewhat different around the world.
<h1>On-topic</h1>
Most questions that arise in the course of performing such engineering (with a few exceptions, see below) are on topic. This includes, for example:<ul>
<li>The design of circuits.
<li>The theory of circuits.
<li>Tools used in the course of the above.
Tools can be both hardware (soldering iron, oscilloscope) and software (schematic capture, simulation).
<li>Components used in a circuit.
<li>The physics behind how circuits and circuit components work.
<li>Signal processing.
<li>Control theory.
<li>Power generation and transmission.
<li>Microcontroller, FPGAs.
<li>Firmware and software.
This must be relevant to specific hardware, or about issues due to hardware limitations.
</ul>
This isn't meant to be an exhaustive list, but hopefully you get the idea. Stay within the spirit of the above, and you'll generally be fine. We have no interest in engaging rules-lawyers.
Sometimes there are legitimate gray areas. These are discussed in meta to find the consensus of the users.
<h1>Off-topic</h1>
The question and answer format of this site means it's not suited for certain topics or types of questions. Other topics are not allowed to keep the site focused on its purpose and reduce what most users would consider noise:<ul>
<li>Shopping questions.
What parts are available and where they are available changes too fast, and there is no single right answer. Answers are often opinion-based and devolve to popularity contests. As a result, we don't allow such questions.
We recognize that sourcing parts is an important part of engineering, but regardless, we're just not going to get into that here.
<li>High-level use of electrical devices.
If your question treats a device like a black box and isn't about its theory of operation or its design tradeoffs, then it's very likely off topic.
There are some exceptions with the techniques of using tools specific to electronics, but don't go too far with this. We are not the help desk for your oscilloscope, but asking about how to use a scope to see a particular waveform might be OK.
<li>Consumer "electronics".
This is really a special case of the previous item, but it happens often enough to point out explicitly. This is not the place to ask how to set the clock in your microwave oven.
<li>No interest in understanding or learning, <i>"Just gimme da anser!"</i>
There has to be some element of engineering, theory, underlying physics, etc, in every question. This is why most Arduino questions (see below) are off topic.
<li>URGENT!!!
Not our problem.
<li>What's the answer to this homework?
Again, this site is about learning. Just giving you the answer to a homework question defeats that, and is not allowed.
It is possible to ask about a homework question, explain what your thought process is, and where exactly you are stuck. If done right, we can try to guide you to discover the solution yourself. This is tricky. Be careful.
Always be honest about it being a homework problem. Most people you are asking have taken the same course you're taking and have done the homework. We know what homework looks like. Trying to disguise it is a great way to eliminate any good will that might have come your way.
</ul>
<h1>Arduinos</h1>
Everything in this section follows from the general rules above. However, this is such a common case that we mention it explicitly.
The point of Arduinos is to add layers of abstraction above a microcontroller so that you can get some results quickly without having to know what is really going on. That's fine and quite useful by itself. We don't have a problem with Arduinos (and similar platforms directly).
This site is about learning and understanding. Many Arduino users are Arduino users specifically to avoid that learning and understanding, to get to results more quickly. That's fine, but not here.
Wanting to drive a car without being bothered with how the engine works or the design tradeoffs of the braking system is fine by itself, but that's not what <i>this</i> site is about. Asking about how to accomplish something with an Arduino is off topic because it's not about electronics or its theory, and is generally not aimed at understanding.
If you've tinkered with Arduinos a bit and want to understand what's going on underneath, then your question probably is on topic. However, then it's not about the Arduino part, but the underlying microcontroller and circuit around it.
If you want to ask something related to an Arduino, here is a checklist to follow first:<ol>
<li>Does it matter that it's an Arduino versus some other microcontroller development board?
If yes, STOP. If you can replace "Arduino" in your question with "microcontroller development board", then you may proceed.
<li>Is this about getting the Arduino to do a particular thing?
If yes, STOP. This is a "gimme da answer" question. If instead you are looking for insight <i>how</i> or <i>why</i> it works, then you may proceed.
<li>Is this about what "shield" to use?
STOP. Just STOP.
<li>Does your question use the word "shield" to mean a daughter board specific to the Arduino ecosystem?
Replace "shield" with "daughter board". If the question no longer makes sense, STOP.
<li>Does your question use the word "sketch" to refer to firmware?
Replace "sketch" with "firmware". If the question no longer makes sense, STOP.
<li>Congratulations, you may actually have a valid Arduino-motivated question for this site.
<ul>
#1: Post edited
by
Olin Lathrop
·
2020-06-09T15:03:41Z (over 4 years ago)
This site is about <i>Electrical Engineering</i> (opamps, microcontrollers, etc) and <i>Electric Power Engineering</i> (utility-scale power generation, transmission, etc). These names may be somewhat different around the world.
<h1>On-topic</h1>
Most questions that arise in the course of performing such engineering (with a few exceptions, see below) are on topic. This includes, for example:<ul>
<li>The design of circuits.
<li>The theory of circuits.
<li>Tools used in the course of the above.
Tools can be both hardware (soldering iron, oscilloscope) and software (schematic capture, simulation).
<li>Components used in a circuit.
<li>The physics behind how circuits and circuit components work.
<li>Signal processing.
<li>Control theory.
<li>Power generation and transmission.
<li>Microcontroller, FPGAs.
<li>Firmware and software.
This must be relevant to specific hardware, or about issues due to hardware limitations.
</ul>
This isn't meant to be an exhaustive list, but hopefully you get the idea. Stay within the spirit of the above, and you'll generally be fine. We have no interest in engaging rules-lawyers.
Sometimes there legitimate are gray areas. These are discussed in meta to find the consensus of the users.
<h1>Off-topic</h1>
The question and answer format of this site means it's not suited for certain topics or types of questions. Other topics are not allowed to keep the site focused on its purpose and reduce what most users would consider noise:<ul>
<li>Shopping questions.
What parts are available and where they are available changes too fast, and there is no single right answer. Answers are often opinion-based and devolve to popularity contests. As a result, we don't allow such questions.
We recognize that sourcing parts is an important part of engineering, but regardless, we're just not going to get into that here.
<li>High-level use of electrical devices.
If your question treats a device like a black box and isn't about its theory of operation or its design tradeoffs, then it's very likely off topic.
There are some exceptions with the techniques of using tools specific to electronics, but don't go too far with this. We are not the help desk for your oscilloscope, but asking about how to use a scope to see a particular waveform might be OK.
<li>Consumer "electronics".
This is really a special case of the previous item, but it happens often enough to point out explicitly. This is not the place to ask how to set the clock in your microwave oven.
<li>No interest in understanding or learning, <i>"Just gimme da anser!"</i>
There has to be some element of engineering, theory, underlying physics, etc, in every question. This is why most Arduino questions (see below) are off topic.
<li>URGENT!!!
Not our problem.
<li>What's the answer to this homework?
Again, this site is about learning. Just giving you the answer to a homework question defeats that, and is not allowed.
It is possible to ask about a homework question, explain what your thought process is, and where exactly you are stuck. If done right, we can try to guide you to discover the solution yourself. This is tricky. Be careful.
Always be honest about it being a homework problem. Most people you are asking have taken the same course you're taking and have done the homework. We know what homework looks like. Trying to disguise it is a great way to eliminate any good will that might have come your way.
</ul>
This site is about <i>Electrical Engineering</i> (opamps, microcontrollers, etc) and <i>Electric Power Engineering</i> (utility-scale power generation, transmission, etc). These names may be somewhat different around the world.
<h1>On-topic</h1>
Most questions that arise in the course of performing such engineering (with a few exceptions, see below) are on topic. This includes, for example:<ul>
<li>The design of circuits.
<li>The theory of circuits.
<li>Tools used in the course of the above.
Tools can be both hardware (soldering iron, oscilloscope) and software (schematic capture, simulation).
<li>Components used in a circuit.
<li>The physics behind how circuits and circuit components work.
<li>Signal processing.
<li>Control theory.
<li>Power generation and transmission.
<li>Microcontroller, FPGAs.
<li>Firmware and software.
This must be relevant to specific hardware, or about issues due to hardware limitations.
</ul>
This isn't meant to be an exhaustive list, but hopefully you get the idea. Stay within the spirit of the above, and you'll generally be fine. We have no interest in engaging rules-lawyers.
Sometimes there are legitimate gray areas. These are discussed in meta to find the consensus of the users.
<h1>Off-topic</h1>
The question and answer format of this site means it's not suited for certain topics or types of questions. Other topics are not allowed to keep the site focused on its purpose and reduce what most users would consider noise:<ul>
<li>Shopping questions.
What parts are available and where they are available changes too fast, and there is no single right answer. Answers are often opinion-based and devolve to popularity contests. As a result, we don't allow such questions.
We recognize that sourcing parts is an important part of engineering, but regardless, we're just not going to get into that here.
<li>High-level use of electrical devices.
If your question treats a device like a black box and isn't about its theory of operation or its design tradeoffs, then it's very likely off topic.
There are some exceptions with the techniques of using tools specific to electronics, but don't go too far with this. We are not the help desk for your oscilloscope, but asking about how to use a scope to see a particular waveform might be OK.
<li>Consumer "electronics".
This is really a special case of the previous item, but it happens often enough to point out explicitly. This is not the place to ask how to set the clock in your microwave oven.
<li>No interest in understanding or learning, <i>"Just gimme da anser!"</i>
There has to be some element of engineering, theory, underlying physics, etc, in every question. This is why most Arduino questions (see below) are off topic.
<li>URGENT!!!
Not our problem.
<li>What's the answer to this homework?
Again, this site is about learning. Just giving you the answer to a homework question defeats that, and is not allowed.
It is possible to ask about a homework question, explain what your thought process is, and where exactly you are stuck. If done right, we can try to guide you to discover the solution yourself. This is tricky. Be careful.
Always be honest about it being a homework problem. Most people you are asking have taken the same course you're taking and have done the homework. We know what homework looks like. Trying to disguise it is a great way to eliminate any good will that might have come your way.