Hi, I found an old CCF on my work PC. Looks like the mapping from D-Pad to Pronto buttons is as follows;

D-PAD Pronto (TSU-6000)

Down Vol-
Up Vol+
Left Channel-
Right Channel+
Select Mute

So looking at my CCF (in Tonto) on the properties for my Sky+ satellite/PVR (which has an arrow keypad (with appropriately named buttons), Vol- is aliased to Sky+ Down, etc.

Don, is this what you were asking for?

AH! I was just ignorant to the options supported in a CCF. We have a TSU2000, which does not have a D-Pad like a PPC.

Also, our Pronto is broken so not a lot of comparisons get made any more. :)

So, how should this work? Since all PPCs will have different button assignments, and all CCFs will have different button assignments, and all Prontos have different button options... ?

fair point. All I've gone by is the limited range of Prontos supported by Pronto. given the capabilities of a PDA screen, it's not unreasonable to expect an emulator to support the full colour prontopro. An emulator should allow the same degree of key alignment as the emulated device. The mapping of the PDA keys is not something you cannot control, so it's up to each user to find it for himself (I think)

Anyone have more comments on this?

I'm trying to decide between Total Remote and PDAWin, has TR come out ahead at this point?

-Michael

Heh. This should be good. :)

--Don, Senior Engineer, Total Remote

Also here in this thread I have seen mention of Netremote IR-version for PPC.
Well, it's out! Let's start testing! (www.proximis.com)
Now we have PDAWin, Total Remote and Netremote IR.

I would have thought that the main reason for going with a Total Remote was for the dongle to extend the capabilities of an IPAQ (etc) standard IR port.

Each post in the thread seems to have missed pointing this out.

Maybe I am missing something, like are there any other remote control solutions that will work on a PPC with the Griffin dongle?

Surely the implementation of a CCF is of little consequence so long as it reflects the fuctionality of that CCF. Therefore the native software that provides that functionality becomes academic.

So, in answer to the question, and it was the reason for me choosing Total Remote, is go for TR if you intend using the dongle. Failing that, go for the least expensive solution. If you really want to be able to make use of all the buttons on your phone/pda then choose the software that does that.

I love the TR solution. I wanted it to extend the range, and it just does that.
I do have an issue with setting up one piece of kit, but that is the topic of a seperate thread.

Sorry Don, this was in reply to you but turned into a reply to everyone :)

Cheers

Sean

You are missing something; critical information. The Total Remote transmitter module, while a marvel of engineering trickery, cannot POSSIBLY be compatible with all types of infrared signals. This is almost always due to the signal in question being "faster" than the audio hardware could ever possibly hope to reproduce. I have 7 pieces of AV gear I use with Total Remote, and ALL 7 of them work with the audio transmitter... so I am a lucky bastard. I would guess at the compatibility as being around 70-80% overall, which brings up a problem; ALL my gear works with it so you could say MY compatibility is 100%, but someone who has a component that falls into that 20-30% would fairly and accurately say it is 100% incompatible if they are unable to control a critical compnent such as the TV or stereo. Another classic case of YMMV (Your Mileage May Vary).


Were THAT true, sure. But I think it is VERY VERY fair to say that not one single PDA app with CCF support has managed 100% compatibility, for a variety of reasons ranging from hardware limitations on the PDA to just plain crappy programming. Bear in mind that ALL of us were forced to reverse-engineer our CCF engines, with absolutely no support from Philips, so it is not surprising that we would all be lacking in some fashion. :/


Most of the time. For most people. Mostly. ;)


Hey, everyone benefits! Thanks for the comments!


--Don

Don,

Sorry if i missed this somewhere else. is there a way to map the hard buttons of my ipaq with a ccf file? i see that you can assign them in native mode but...

I am using ccf because i found the png files really difficult to work with. Im not a graphics person and they seemed really impracticle to me. I just want to configure someone elses graphics to do what i want.

Really enjoying it so far. Ipaq 4150. I almost didnt get it because the site said it was incompatible. i think the ipaq must recieve thru the irDA and tx thru the griffin device. So the site is a little misleading.

thanks

Can anyone tell me if PDAWin supports the Ultramote IR card? I currently have one of the Electric Dog cards in my current PDA remote, but I am going to buy a second one and cannot find the Electric Dog card anywhere. Thanks in advance!

Don:

Does the dongle widen the bean any or is it just as narrow as the iR on the Dell x50v? What I have observed is the it is just as narrow and the PDA needs to be pointed directly at the components they are to control.

Having a wide beam would have been more flexible for me instead of a beam that I could control my next door neighbors equipment from my chair, ha....

Am I missing something?

Steve