Hi guys, I'm new to the neighbourhood, but You've all been a great help already. I've been looking for the "ultimate remote" for a while now, and had already concluded that a PDA was probably the way to go. I had a look at Nevo, but it was too inflexible, and then found PDAWin, and this forum. I've since acquired an old iPAQ, I'm waiting for my CF jacket and IR extender to arrive, and I'm a fully paid up, registered PDAWin user (sorry, but I've just read the previos thread, and I didn't want anyone shouting at me!!!)

I'm busy learning the intricacies of ProntoEdit and gathering the data for my first CCF. I've not been able to get a 100% match in the files for my various bits of equipment, and although the "next best fit" approach is helping, I'm still getting some wierd results.

Ideally, I'd like to learn the IR codes from my original remotes, and then build them into my CCF files. But I can't seem the spot the simple way if doing it, and I hoped that you guys may have cracked this already. I gather that PDAWin will learn codes from remotes into its own templates, but how can I get them into a format that I can use for a CCF file.

Is there a utility to learn them directly into the IPAQ, or onto a PC (I have a USB IR adapter)?

ANy help you can give with this one would be much appreciated. Apologies if this duplicates an earlier thread, but I had a quick look and I couldn't spot anything.

One final question. Is their a way to amke the IPAQ load PDAWIN at start up?

Many thanks in anticipation.

STRICKO
I'm also new to using Pronto Edit,and the PDAWin software.
What I have been doing to build a ccf.file for my IPAQ
3650 is find a file with the graphics I would like to use for my remote,and download into Pronto Edit.
If the ir codes are not right for my equipment,I delete the learned commands in Pronto Edit.
After the codes have been deleted in Pronto Edit I download the ccf.file to my IPAQ.
I then manually train the buttons on the ccf.file with my orginal remotes.
After training AND testing the ir codes on the IPAQ I do a sync with the IPAQ and my computer.
After the sync, the codes that I need for my equipment are in the ccf. file with the graphics I wanted.
As I stated eariler I am new to both Pronto Edit and the PDAWIN software,so there might be an easier way of doing this.

Thanks for the quick response.

It's the "I then manually train the buttons on the ccf.file with my orginal remotes" bit that I didn't get. I assumed that PDAWin would only learn in "native" mode, not CCF. If learning works in CCF mode, then I'm fine. I just didn't think to try it!!!!!

I'll give it a try later on today.

I'm not a PDA owner, just a longtime Pronto Edit user. Probably the best way to handle codes from a Pronto Edit/ccf standpoint is as follows:

1 - Create a device in PE and call it IR codes (or whatever).

2 - Put a bunch of blank panels (one or two per piece of equipment) under this device and fill each of them up with fairly small plain looking buttons. These panels will not normally be seen by anyone using the remote.

3 - Label each button (as above) with the individual codes that your gear uses. This will probably result in a lot of buttons.

4 - Download your ccf to the PDA and learn the codes onto these buttons.

5 - In your ccf, everytime you need a code (or build a macro), alias to these buttons.

This approach has several advantages. You only have to learn each code once. If you need to troubleshoot, you don't have 12 instances of a code scattered around your ccf. If you replace a piece of gear, normally all you need to do is learn the new codes over the old codes. You're up and running quickly, without having to do a major redesign on your ccf. Pronto users have been using this method for a long time. On the Pronto forum it is referred to as an "alias ccf". A search on the Pronto forum will yield more information. Hope this helps.

Jim L

Many thanks, I'd started to go a similar way, as I had created a small dummy CCF to test out a couple of things. This has become my default capture mechanism. It ain't pretty but it helps. My outline CCF design replicates each of my original remotes (or at least the interesting bits), with a front end and commonly used functions section. This would fit in well my the aliasing approach.

Overall, the build of my first CCF is going slowly, as I learn my way around, but so far (touch wood) I've not hit any limitations that I would worry about.

Thanks for all the help.

Hi,
Having used PEdit quite a lot with my Pronto RU940 I can just say:
FOLLOW BOMBERJIMS ADVICE.
If you start off with the right design you can then continuously improve your CCF in the future (in your own pace)

An excellent example of this design is Dale Crawford's EasyTheater which you can download in the file section for ProntoPro. It's truely a very well thought through and verstile.

If you look at the design it's a perfect practical example of what bomberjim told you.

Have fun!

Thanks for the tip, I'll have a look at the one you suggested. The time pressure if off for the moment, my supplier can't get me a CF expansion pack until the end of next week!!!!! It should be cheaper (and quicker)for me to buy off eBay, but by the time the shipping has been added to get it me in the UK, it's hardly worth the bother, and it makes aftersales support more difficult.

In the meantime, see my new thread....

Hi Guys,
I'm having trouble getting my ipaq 3950 to learn codes in PDAWIN CCF mode. I've just bought a new Sony DVP-NS530 DVD player and whilst PDAWIN can learn its commands in native mode it doesn't seem to be able to do so in CCF mode. It "APPEARS" to work ie it goes through the process of learning but the commands just don't operate the player. Any ideas?