I (and presumably other users) have been discouraged by the answers given on EE that don't really answer the question but dispute the method/solution to the problem. For example, in this question the OP clearly already has a communications system developed and wants help making it robust, however, in this highly up-voted answer the question seems to be avoided and the answer is "you don't have enough knowledge/practice to do what you're doing so don't try". Granted this might be true and another solution might be more practical. The practical trouble is this: no real answer can be accepted since the original question is not answered. Someone who might have the expertise & need, who visits our site later on will glean no valuable information from this question only an answer with a lot of up-votes saying "don't try it rookie". I've had this problem with my own questions, for example here and here. Even in situations in which it is acknowledged that the proposed solution is most likely not the best solution, but other constraints apply, answers seem to consistently dispute and try to re-engineer the approach rather than aid the solution. I notice this more on the EE site over any other SE sites. Can anything be done to help avoid this? Is this a problem at all?
This is completely allowed and expected:
I wouldn't say it is encouraged, but you should always speak your mind and be honest (but civil) in your answers -- even if that's not what the asker necessarily asked for.
Not all things are possible. How much the OP wishes they were possible or protests there not being alternatives is irrelevant.
How do I change a tire with this soup ladle? No, that's the only tool I have and I don't have time to run to the store to get something else. I need this tire changed now.
Then there are things that require too much knowledge and would be impossible to explain in the necessary depth in a post here.
My friend has these frequent headaches. I've heard snipping out the right part of the brain will help. How do I know which part is which, and what's the best style of wire cutters to use? Yes, I know everything needs to be sterile. Also, what's the best way to put the skull back together afterwards. I understand about stitching soft tissue, but couldn't find anything about stitching bone.
Certain things are over your head if you have to ask on a forum like this.
This is a tricky question to answer. My view is that the person who asked the question has full power in these situations. By that I mean you have full right to down vote answers that don't answer your question, which you haven't seemed to have done in yours. And if your question still isn't answered then say so and try to clarify what you want.
Many times the best answer is "don't try it" and as long as there is good reasoning given behind that answer then I have no problem with it. In fact I would be there would be cases that someone would be happy they received that answer because they were not aware of certain issues.
For the specific case of the communication system question, Olin didn't specify any information as to why it was out of his league which doesn't help with learning much. So in this case I do have a problem with the answer.
If the actual question is not answered, the poster is not obligated to accept any of the offered answers, no matter how much they are upvoted. If anyone starts to pressure them to do so with comments, they are free to point out with their own comment why the answers are not suitable for their purposes, or even just ignore them.
Certainly it could be wise to carefully read and contemplate comments from experienced engineers, but at the same time, answers that are arguably technically poor, off-target, or even simply insulting do occasional achieve undeserved vote totals. Voting up or down is ultimately an expression of personal opinion, and unlike voting to close it does not interfere with others' ability to express a contrary opinion or choose a different course of action.
And sometimes, the process of learning requires making your own mistakes, and learning from them.
I think this is the difference between answering the asker's question, and provide a general solution which is useful for everybody. "Don't try it" may be useful for the asker, but not a general solution. General solutions can get upvotes, the solution to the asker's problem can get an accept.