How about a thread that replaces RTFM and RTFDataSheet:

[blainecf]

Rather than reply to a newbie: RTFM..., how 'bout a thread with a short primer on Data Sheets that outlines the sections of a DataSheet, and matches up the types of questions a new person would have to the appropriate section.

Why? Because RTFM is just an insult (doesn't really help), and the DataSheets are a bit overwhelming to someone just starting out.

Of course, doing someone else's thinking for them doesn't help either.

We all learn at different paces, in different ways, with VERY different motivations, limitations, and expectations.

A village/community/forum should be kind to everyone, even the (village) idiot.

An excellent quote: "The worst thing you can do for a person is doing something they can and should do for themself!!!"

[Archilochus]

Hi Blaine,
That's a fairly easy one - just start a thread with an appropriate title, and start adding ideas as they come up.
Problem is that after a while the thread will be as long as an average data sheet, most folks won't take the time to read it, and everyone will just start saying RTFT (Read The F*****g Thread) instead of RTFM.

Arch

[Acetronics2]

Hi, Blaine

As you will notice on this Forum, there are people decided to learn and people decided to wait for others to make the job ... newbie or not !!!

You will ALSO note a very high correlation ratio between the famous "RTFM" and the second kind of people.

So, I think it is not so stupid to explain them they are a "little" boring ...

I'm not the elder here, but for years, I've never found a gentle question, showing the author has already tried to find a solution, answered by one of those "terrible" words ( RTFM or RTFDS ).

That shows people answering generally try to read threads between the lines ...

Alain

PS: just try a while to understand what my signature means ... you'll be surprised !!!

[garryp4]

The manual comes in French? The data sheet does not always have the info needed. What is the minimum +vref for a 18F2520? After I RTFM I CNFTFA (could not find the 'french' answer). It is possible I may have missed it after looking 3 times. Maybe someone in this group knew. Microchips answer was 1.2v. But at supply voltage? Again CNFTFA.

[skimask]

The manual comes in French? The data sheet does not always have the info needed. What is the minimum +vref for a 18F2520? After I RTFM I CNFTFA (could not find the 'french' answer). It is possible I may have missed it after looking 3 times. Maybe someone in this group knew. Microchips answer was 1.2v. But at supply voltage? Again CNFTFA.

Yep, RTFM...
PIC18F2520 datasheet, Table 26-24, Parameter A20, A21, A22. If you do the math and factor in the minimum voltages for the chip, you'll come up with 1.2v, just like the datasheet says.

[Pic_User]

In addition to questions that NEED an answer like:
“look at the, easy to get information, before you ask THAT question”.

There seems to be a lot of minimally worded questions.
“When I turn my circuit on, why doesn’t it work the way I expected?”

Maybe we should post something, that gives an example, of what works best, to get the answer, the member wants.

This type of post:
++++++++++++++++++++++

Suggestions for a successful post.

The Forum category:
If the category is obvious and clear cut, try to post in the appropriate forum section.
If the subject is difficult to place in an existing category, post in the closest you can.
Just do not post the same question in more than one category (“cross-post”) .
The gurus that answer most of the questions, read all of the posts and get annoyed
when they see the same question spread across many posts. The same question,
asked again, causes the answers to be split between the posts and difficult to research.

The Subject line:
Try to make the subject descriptive enough to help people decide to view your post.
Many posts carry the title, “help”, “code doesn’t work”, or “PIC16F876”.
This may get you an answer, but is useless for someone, searching for help, in the future.

Content:
Try to include a short background on the project and a background on you.
The answer gods like to see that you have invested some “sweat equity” into the project.
They put in many hours a day, helping people solve PICBASIC problems.
They do not do the groundwork for you. That is your job.
At least do enough of the work to get stumped by a NOT so obvious problem.
Search the forum, search the internet look for the answer on your own.

About your project:
Describe what you want your project to do.
List what data sheets you have tried to read.
List what manuals you have read, to find your answer.
Tell that you have searched the forum.
Post what doesn’t work.
Tell what you have already tried.
Post your code.
Post your schematic.

About you:
Tell what have you checked already.
Tell about your ability. PIC experience, electronics experience.
What level answer are you expecting.

++++++++++++++++++++++
....anyway you guys get the idea, a “how to” for newbies.....
-Adam-