A few observations on using the Palm as a universal (and a tip for screen-flipping) . . .
Background:
Since (a) I meet the criteria in Marco's post for using a Palm as both an organizer and as a remote, and (b) none of the non-Pronto remotes I tried (including the One for All A/V Producer 8) came close to being flexible enough to control my system, and (c) I just can't bring myself to spend ~$400 for a device that does nothing more than control components, I decided to try my Palm Vx (which is always with me anyway) as my remote control. Except for a small mystery glitch (explained below), I'm very happy with the results.
Observations:
(a) The OmniRemote software has to be one of the great bargains for $20. It's extremely easy to set-up to your exact preferences and to label and/or use its icons for each function so you don't have to remember your esoteric key assignments (and, if you sync the Palm to your PC and use BackupBuddy, you always have a back-up of all your work).
(b) the built-in IR port on the Palm V was strong enough to control my Sony TV (KP48V80)from 12-14 feet away, but pretty hopeless from that distance for my other components (Denon AVR-3200; Denon DVD-2500; Pioneer LaserDisc CLD-M90; JVC VCR HR-S3500; Scientific-Atlanta Explorer 2000 cable box which has been customized by my digital cable supplier -- all of which are controlled by a single IR receiver through a Niles Audio IR extender).
I tried both the IR Blaster from Tech Center Labs (
[Link: members.aol.com] -- go to the order form for the Palm V version), and the RF converter from SmartHome (see PDD's posts).
Advantages of the RF converter:
(a) significantly greater range, and omni-directional;
(b) it fits over the existing IR port, so there's no need to flip screens;
(c) it frees my hot-sync port, and I can keep my palm connected to AC power using the travel kit AC adapter -- no auto-off hassels. Or, if I'm feeling particularly nerdy, I can attach my OmniSky/Minstrel wireless modem and get movie reviews, TV listings, or whatever, from the Web. (Try that, Pronto users!)
(d) makes it much easier to program/test various commands, since it uses the internal IR port. Using the blaster, you have to switch between internal and external ports for learning/testing, which gets old very quickly.
Disadvantages: more expensive, and requires the dreaded velcro to attach it to the Palm.
However, if you're using the external port and need to flip the screen, there's a terrific "flip hack" for this at
www.palmgear.comIt will rotate the screen left or right (Visor users take note) or flip it, and it stays rotated/flipped until the hack is disabled (unlike the OmniRemote flip setting, which is disabled if you use the category lists to change categories).
If you're using OmniRemote, be sure to notice that you can assign any keys to the Palm hardware buttons -- makes it very easy to access volume (just use the up/down button) and other frequently used functions. You also can set the Palm preferences so that a single swipe up the screen turns backlighting on/off.
It took just seconds create/label a button and to teach the Palm the command or macro. The only time-consuming part is deciding on your layout.
My Palm Vx now contains virtually every remote command available for each of my components, as well as several macros, using a total of 104k of its memory. The only disadvantage I see in using the Palm versus the Pronto is when it comes to commands that are toggled, or where the remote cycles through a number of choices -- it's hard/impossible to create a macro that contains one of these. Also, there is a certain lighting range (dim but not dark) in which the Palm's screen is difficult to read, with or without backlighting.
Now for the glitch: intermittently, some components (especially the Denon ones,
which are notorious for flaky remote control operations, but occasionally the cable converter as well) just don't respond. They all will work perfectly one day, and the next day . . . no command has any effect (the VCR and Laserdisc player have always worked fine).
I've tried positioning the Palm (without the RF converter) right in front of the component's IR receiver, and also experimented with changing the distance between the RF converter and the Niles IR receiver. Eventually, everything has started working correctly, but I haven't experimented enough to be able to tell where the problem is. Has anyone else using the Palm (or another remote, for that matter) had a similar problem?