16

I think these guidelines generally make sense. However, this part needs some adjustment: Parts that were obfuscated (e.g. the board manufacturer sanded off the part number) will not be considered. This also includes chip-on-board with an opaque epoxy, and parts that are burned beyond recognition. We've had some legitimate questions where a part was burned ...


13

Ask a new question, and link to the old one. Be sure to upvote and accept the answers that solved that particular problem for you.


13

One thing that I think should be a requirement: The question title should be a short description of the component Instead of What is this component? the title should be What is this blue plastic cylinder with two wires?. The former is very annoying on the front page, because every identification question looks the same so it is difficult to remember if ...


11

Go ahead and post your questions. We've had a good number of questions about ce, IEC, ul, fcc requirements. They weren't badly received, typically.


10

Is it expected that I should stop by the ever-changing Wikipedia before posting a question? Yes, absolutely. Or at least something where the answer might be, e.g. doing a google search. And really, is that too much to ask? The stackexchange networks goal isn't to be an answer machine for anything you might want to know, let me quote from the tour: With ...


10

HDL is on-topic on electronics.stackexchange.com. There is no line. StackExchange can do what it wants with HDL questions, but there is no need to have a "line" that strictly sorts where a question goes. This is a case where there is some overlap between sites, and this is OK. You could ask that question here, or there, (but not both please) and both ...


9

If you were to edit your original, answered question, then either: the original answers would no longer make sense, which is undesirable because it makes the page less useful and takes away from the answerers' efforts, or you would be asking two questions in one post, which is undesirable because then the answers are likely to answer one and miss the other, ...


9

The purpose of this site is not to give you the equivalent of a college education in electrical engineering. Do NOT dump a large series of lengthy questions on us. As a beginner, you will find that many of your questions have already been answered here (or elsewhere). Please take the time to do the research, both on this site and on the Internet in general, ...


7

In addition to what W5VO said (ask new question, link to old), make sure the new question contains enough information to stand on its own. The old question should only be used for background information, not essential information needed to answer the new question. It's really annoying when it would require following links to get basic necessary information ...


7

I would say that questions about cell phone CPUs are subject to the same rules as every other type of CPU - shopping questions are off-topic, but design questions are fine.


7

One week is too long for a fix-it period. Even one day is too long. An hour or two is about right amount of time. After posting, the asker should monitor their post for about an hour. They should tend to their question. Language aside, there is a very good reason for doing that. Clarification questions will be asked in the comments. If the asker can ...


6

With the tools we have at our disposal now I still think we should be closing questions that we don't understand or have significant issues. The reason for this is that there is no easy way to make sure bad questions get taken care of after a period of time. However, We should try to give feedback as to why questions are closed, or what issues exist with ...


6

What are the components I need for assembling a hobby mobile phone? Way too broad. Do you mean individual parts, like specific ICs, etc? Or do you mean high level, block diagrams? A hobby device is exactly like a commercial device. How would I go about assembling such a hobby device? Again too broad. There is no one way except "Soldering" Are there ...


6

Those, simply, are not valuable questions. The answer can change at a moments notice, and due diligence on the part of the asker can make these better questions with a few hours work on their own. "There are thousands of parts available, which is best for me?" -- which is what all three of your example questions boil down to -- really doesn't help you, ...


5

You have asked this before, and apparently learned nothing from the answers. You just asked another question on the main site, and it's full of the same things you were told not to do. I did give a brief answer, but with so many wrong statements, invalid assumptions, and overall sloppiness, it's no surprise it is getting downvoted. All the problems make ...


5

The closed statement on the iphone question puts it well: "Questions on the use of electronic devices are off-topic as this site is intended specifically for questions on electronics design." The reason why the GPS question is ok is because it is related to design. The question is essentially, "why is x designed this way?". The iphone one is not a ...


5

I agree 100% with Stacey's analysis, but when you say "I flagged wrong?" the best thing to do is just flag how you see fit at the time. As long as you're doing your best to try and improve the site at the time for a lot of things like that there's not really a wrong / right decision. Even when you get direct close / re-open votes I've seen questions closed ...


5

Your question was flawed from the start. It made the assumption that all brushless motors are more efficient than all brushed motors, and then asked for reasons than this might be true. This is far too broad for a question-and-answer site like StackExchange. Furthermore, it seemed to be based on the assertions made by the marketing department of a consumer ...


5

You need to be careful with homework questions. They can be acceptable, but are held to a higher standard. You must: State that it is a homework (or other assigned or contrived) problem. The important point for us is that you have been given this problem to help you learn electronics, not because you actually faced this problem in the real world. People ...


5

Your perceptions seem to be somewhat skewed by the organization in which you're working. In the projects in which I've been involved, it's the hardware guys that are writing the HDL and the firmware guys that are writing the microprocessor code — sometimes for microprocessors that are embedded inside the FPGAs. And I disagree that an HDL is "in ...


5

The first example would be off-topic, because it's too broad and also the internet is riddled with advise about car electronics (not as easy as wall adapter power, even though instructables makes you think it is) and 12V (9V~36V+) to 5V generation. So some personal research should give you more than enough to start with and ask specific questions about if ...


5

Asking for product recommendations is off topic (for all of SE). If you need to ask these types of questions, the chat feature will be the best way, but YMMV. https://stackoverflow.blog/2010/11/23/qa-is-hard-lets-go-shopping/


5

If you can phrase it as a design question it's acceptable. I personally find the restriction on asking genuine design questions which have good technical content and instructional value to be an excessive limitation on what could be useful questions. The aim is to avoid generic "where can I buy an xxx" type questions but in the process I consider ...


4

Questions about an app will probably get closed as off-topic → not about electronics design. Microcontroller questions should be alright. Arduino questions should be posted to the Arduino stack.


4

It will depend very much on what the questions are and how you define "very similar". I don't think it's possible to give an exact answer yes/no answer. Consider the following (fictional) examples: I'm building this super 555 timer circuit I found online! How can I work out where pin 1 is on the 555? What should the value of R1 be for a ...


4

IMO the treatment of 'bad' questions (bad in one form or another) is is OK, but sometimes the canned reason for closing is not very informative or accurate. My personal contribution is that I never vote to close a question without writing or seconding an explanatory comment.


4

Yes, it would be too broad. Consider just the range of use cases that apply to yourself, and the kind of answer it would require to cover the issues related to those cases. Then multiply that by all possible use cases, and it's obvious that the answer would fill a book. That kind of question is just not a good fit for the StackExchange format.


4

Low-level programming, especially programming related to interfacing with external circuits is very appropriate for EE. Topics related to real-time systems are also appropriate. We also handle some DSP here, but there's also a separate DSP.SE for the more application-specific questions.


4

No, such a question would be far too broad. You need to narrow things down to the point where you can ask a specific design question that can be answered succinctly. Can you give a general description of the kind of device you're talking about here?


4

I recommend making the photography instructions contain more specific guidance, since many people don't have experience with taking good technical photos. I would say: Well lit. Details should be crisp, not noisy from lack of light. There should be no overexposure (white blobs) hiding colors and details. (Using a basic photo editor to improve contrast ...


Only top voted, non community-wiki answers of a minimum length are eligible