After reading hundreds (thousands?) of posts on this site, it seems that most newbies ask the same basic questions. I think most of these questions could be answered by providing the "big picture" in one short document. Don't get me wrong. I really like this site. But one short document would go a long way in helping the newbie.

We do have the FAQ. And it is a very useful document. But a lot of the issues covered in it are useful once you know what you are doing. Most people don't know where to start. The big picture is what is missing IMO.

Just a suggestion.

Bobusan

Have you tied reading the RC5000 Setup manual? It is far better than the ProntoEdit manual. Just watch out for the few minor differences.

Whilst I think you have a point, speaking from my own experience I'm glad such a document doesn't exist because I actually think I've learned more about the Pronto from using the forum & FAQ's on this site than I would have ever done if I just read one document to show me the basics.

Knowing that the RC5000 setup manual is written better would be a great addition to this document! Good one Peter. Paul, remember it's a high level document. You can't really accomplish anything with it alone. But it would help the newbie visualize the big picture better - and faster.

Thanks for the input.

Bobusan

For example, this is what I'd put in this high level document:

1. Connecting your Pronto to your PC.
2. Getting familiar with your Pronto.
3. Download a few CCF's to see how others do it.
4. Introduce Discrete codes.
5. Discuss ways to find codes. IR Tools, IR Panel, etc.
6. Working smarter in ProntEdit.
7. Optimizing. (Discuss clean codes, aliasing, etc.)

All of these short topics would link to more comprehensive docs. Again, very high level in nature.

Bobusan

Take a look at [Link: remotecentral.com]

Bobusan,

I see what you mean now. Yeah, that would help the newbie no end. I especially like the idea of having links throughout the document to other documents (FAQ's?) and other areas of this site. It would make your document an excellent central reference point, maybe for more advanced users as well.

My point of finding out for yourself refers to my experience of finding answers to questions that I hadn't even thought of....if you see what I mean!

Hi Paul,

I thought an example might help clarify the point a bit. This high level document wouldn't replace anything here. Just get people started quicker. The nuts and bolts would be covered with existing documents.

In really could be a very short document.

Bobusan

Hi Martin,

The FAQ is great. I found it (and still find it) very helpful. But in the first few hours, it didn't really help that much. A lot of answers to questions you don't understand the significance of. You have to put too many pieces together before the FAQ "kicks in". The FAQ is great once you get a little "traction" though.

If you read the posts here each day, a good percentage are of the "I'm lost" variety. A high level document that helps organize the newbie's efforts would be very useful IMO.

Thanks for the reply.

Bobusan

Daniel - any thoughts?

Just a quick thought on the proposed high level document. I just purchased a Pronto last week and am planning on taking the day tomorrow to begin my setup & testing. (You gotta love having excess vacation at the end of the year) I think a "Startup Guide" would be quite helpful.

My daytime job is designing computer HMIs for process control, so I have some similar experience (stretching a little), but I am still a little "confused" about where to start.

I have downloaded several different CCFs and played with ProntoEdit and the emulator. Perhaps a useful section in this document would be a list of CCFs that are good references. I remember seeing a few that have text files describing design methodology, tools used, etc. with some of the CCFs.

Just my two cents.
Brian

Brian,

Referencing good examples of CCFs is a good idea. A design philosophy is also helpful. What constitutes a good design? How to optimize memory usage.

A lot of that stuff is already here. But finding it "before you need it" is the trick.

I may start writing something today. If so, I'll post it so everyone can contribute. If anything, at least it's a post to point the newbie to.

Thanks for the reply.

Bobusan

This might be helpful
[Link: remotecentral.com]