Why do some questions go unanswered? Isn't there a moderator or somebody that can at least make some kind of response?
The Arduino TROUBLESHOOTING page suggests that asking questions on this site is an important step to take for help with Arduino problems. That, obviously, is not always the case. 
the questions that get answered on this forum are the kind of questions that are articulated clearly with examples of code, without being nasty.
I've watched my posts die but that doesn't make me give up, maybe I wasn't asking properly, or asking too much or not understanding what has been said. Also people have their own agendas and are not obligated to do anything.
I feel your frustration about not getting a reply though but don't loose faith or get frustrated with others.
Or maybe buy a book maybe like making things talk by tom igoe, or physical computing, or massimo banzi's getting startde with arduino.
It may just be that your problem gets overlooked in the mass of problems listed.
The more details, the better. Start with the subject - you've only got a short line, but you can make it count. Don't assume we know what your circuit looks like, what your code looks like, etc. Don't assume that parts of your code/circuit are not the problem - you may be way off base, so include everything.
The farther off topic you are, the less help you can reasonably expect. This is the arduino forum; questions about a really popular arduino clone may get answered, while WinAVR or PIC questions may not get a response at all.
No one may know the answer, at least based on the info you provide. There could be lots of people reading your question, but a bunch of "I don't know" replies aren't particularly useful.
It may be that people are just busy. The person with the answer may be on the other side of the planet, too. I've participated in discussions where responses average 12 hours apart, since my daytime is the other party's nighttime.
It may be that a lengthy discussion on that topic was just concluded yesterday, and everyone is too tired to tell you to go read that thread. 
There can be volume issues, too. If it doesn't get answered in a day or so, you may reply to your own post to bump it up - hopefully with additional info to help your would-be troubleshooters.
-j
For me the questions that don't get an answer are the ones that go, "I have a splurge splodge, has anyone written a library for it?"
It is very specific so if you haven't got one there is nothing to say. Also asking for advice on how to write interface code for the splurge splodge is a lot more active and shows a willingness to learn and more likely to prompt a response especially if there are some links where I can find out about the splurge splodge.
Also I will always look at a question with 0 replies so if you add a "is no one going to answer" it looks like their is a reply and I don't always look at it.
It helps if you post to the right board, read the definitions and decide where it should go, their are some boards I hardly ever look at. For example some posts are in Software->Interfacing which would be much better in Hardware->Interfacing. Again read the definitions.
Finally a post during the week is often better than a post at weekends when it is busy.
Hope that helps.
I try to answer any questions I can, or have the ability to answer.
Unless you want to send all day reading every post with how busy this forum can be, I think you do a little selective filtering.
For example if you post is a XP only problem and you are running Vista, or haven`t an insight into the subject, it just gets over looked with the amount of posts each day.
So far I have been lucky with my attempt for helps; I guess I believe in karma
If you help others, others will help you when needed.
Just keep trying and don`t give up.
I don't tends to answer questions that I feel would be better answered by having the poster READ THE DOCUMENTATION. Looking at the OP's history, several of his questions are in that category. I mean "what does 'sketch' mean?"
I figure silence is better than snide "RTFM" answers.
In another thread, halley posted a link to this document with lots of advice about how to ask smart questions : How To Ask Questions The Smart Way
Thanks halley
thanks for the info guys
Another thing to remember is the title or subject line of your question; if you write a subject like "Please help me" or "N00b seeks help", then there is nothing to attract the interest of a reader. If you ask "How can I interface a relay?" or "What's the best way to control a motor?", readers who have an interest or expertise in the subject will spot it.
I would also agree with the previous postings where people have mentioned a clear description of the problem, and a full disclosure of what you're trying to do. Often, I've read questions where it seems that the writer is trying to get us to play a guessing game. Such questions need a few rounds of "what are you really trying to do" and "in what way does your circuit not work" before we get the complete facts.
I generally don't click on the vague messages like "please help me" either.
I try to help people, but if there's not enough detail in the question, it becomes more about trying to figure out what the person is trying to do or what the problem is that trying to solve it.
So even if you ask "How can I interface a relay?", if I'm board, I'll point you to the playground link, otherwise I won't answer. But if you're actually trying to get it to work and have a specific problem and explain how it's wired or post the part of the code that should be driving it, it's a lot easier to give a useful answer.
Also asking for advice on how to write interface code for the splurge splodge is a lot more active and shows a willingness to learn and more likely to prompt a response especially if there are some links where I can find out about the splurge splodge.
Mike, I would be interested in advice on how to best interface the splurge splodge. Unfortunately Google doesn't seem to reveal any data sheets--although your post seems to be the top hit for it, so you seem to be the expert.
If you could even suggest how to find out if it is SPI or I2C based it could be helpful.
Thanks.
--Phil.
</smartalec >
Neither, it's SpSpI which uses two and a half wires for communication, pulled to -j and +j through insistors.
Neither, it's SpSpI which uses two and a half wires for communication, pulled to -j and +j through insistors.
I tried that but it doesn't work rite. can tell me how to fix it?
I tried that but it doesn't work rite. can tell me how to fix it?
It depends on if you have version 1 or version 1.1, version 1.0.0.1 is too rare to consider. In place of insistors try a jump.
Now a jump is a device to put surprise into a circuit measured in Boos. Like the Farad the basic unit of the Boo is too big to use in practice. This is because it is the standard unit of surprise that will just kill a man. Therefore in practice most components are rated in 1E-12 of a boo or a pico boo.
So, instead of the two insistors, I can just make a small boo boo?
Yes, remember three boo boos make one Yogi
Four of them properly aligned make a stacked yogi.
Wait, wait, is it a Maxwell yogi or a Faraday yogi?
I can't bear this anymore...