This behavior can also occur if you're using a version older than V1.14 on a Palm IIIx or Palm V which use the new Dragonball EZ microprocessor.

Also keep in mind that some PalmOS PDAs have better range than others. Check out our IR Range Measurements page for an idea of the range we observed in our lab with various PalmOS devices.

If you still can't get OmniRemote™ to give you the range you want, there are a couple of products that re-transmit the IR signal via radio to a base unit which sits near the TV. Supposedly, the signal will go very far, even through walls.

An excellent site for more specific information on a couple of IR/RF converters is http://www.pro-bono.net/palm/.

The second screen, which says "press button on remote," is the training screen. This time when you press the button on your remote, the signal is saved and the button is trained. If you abort out of this screen, the training is not completed.

Alternately, GAKworx has posted two OmniRemote™ databases, TV Uni-Remote and CBox Uni-Remote, which contain the IR codes for many different TVs and Cable boxes.

We have not tested these databases yet.

If you can't get auto to work, the five buttons have the most common frequencies on them. You might want to just try each of them manually (remember you need to re-train the button after you change the frequency).

Put the stylus down on the screen in the upper left of where you want the button to be. Don't lift the stylus, but instead, drag it down and to the right until the button is the size you want it. Then lift the stylus.

Don't worry too much about getting the button in the right place, you can always move the button later using Move Buttons mode.

Your results may improve if you re-define a hard key to the repeating button and use the hard key instead of the on-screen button. If so, this may be the result of a bug. Please let us know if you experience this behavior.

Because this type of device is (as far as I can tell) quite rare, I was unaware of it when I wrote OmniRemote™, and as such OmniRemote™ does not support this behavior. We are looking into solving this problem in the future. At the moment there are only two solutions I have come up with. You can create two buttons for each number, one for the first press and one for the second. Or you can create each number button as a macro that sends a sequence like:

1 - Volume up - Volume Down

Because the volume code will cause it to reset and expect the first code for "1" the next time you press it.

For extra safety, you can even make a copy of this file, later you can re-install it manually if your setting are changed by accident.

If your Palm loses its data for any reason, you will need to re-install the application (Remote.PRC) but your layouts and training will be restored automatically. Do not re-install the OmniRemote™.PDB file that came in the .ZIP file or your settings will be lost.

For older OmniRemote versions: You can export all of your categories together and make an exact clone of all of your layouts and training.

First HotSync the Palm you want to copy from. Then find the file:
C:\Palm\PayneC\Backup\OmniRemote.PDB
(replace PayneC with your username)

Make a copy of this file and install it on the other Palm using the standard Palm install tool.

Warning, this will delete all buttons and training from the Palm you are installing the file on.

Also include the information listed in the previous question, so we can verify your original order quickly.

If you continue to experience difficulties, e-mail us, and we will send you instructions on how to mail or fax in your order.

Warning! Do not install the file named "OmniRemote.pdb"; doing so will overwrite all previous programming.

However, older versions of OmniRemote are less compatible. OmniRemote v1.171 has been tested with the following PalmOS hardware:

• PalmPilot Personal
• PalmPilot Professional
• All Pilot models with an OS3.0 Upgrade Card
• Palm III, IIIe, IIIe SE, IIIx, IIIxe, IIIc, V, Vx, VII
• Some versions of the Palm VIIx
• Handspring Visor Basic, Edge, Prism, Platinum, Pro, Neo
• IBM Workpad 20x, 30x, c3, 50u, 50J
• Symbol SPT1500, SPT1700, SPT1700-2D
• TRG Pro

There is a remote control for Windows that connects to the parallel port called CIR. It can be found at:
http://www.ziplabel.com/cir/index.html

There are a few IR devices which don't work with OmniRemote™ also. Devices that use a frequency of 455KHz such as some Kenwood receivers and devices made by Bang and Olufsen do not work because the Palm is too slow to reproduce their carrier. (These devices may work with an OmniRemote™ Springboard module connected to a Visor handheld.) There are a few other devices as well, but OmniRemote™ does work with most IR devices.

When you train OmniRemote™ make sure you point your remote at the IR receiver on the side of your Visor. The IR LED on the Springboard Module only sends a signal, it does not receive.

If you've already tried retraining using different frequencies and that didn't work, there is another feature for Springboard Module users only that you can try. In the training settings dialogue, try setting the IR sample rate to "fast". With some devices fast works better, but with others slow works better, so be sure to try both rather than always using fast.

If you have a different PalmOS device as well as your Visor, you can use OmniRemote™ on both if you own both the software and the Springboard Module.

If you encounter problems with macros, timers or hard keys in version 1.16, download the latest version of OmniRemote™.

If clicking the find button in version 1.16 of the online manual crashes your Visor, you can download the latest version of the online manual. (Remember, if your Visor won't turn off, you can reset it by pushing an open paperclip into the reset hole on the back.)

For "non-PRO" versions of OmniRemote, a HackMaster hack called FlipHack is available. It lets you rotate your screen to the left, right, or upside-down, and it stays flipped, even when you use the menu bar in older versions of OmniRemote™.

Ironically, because of a bug in OmniRemote™ V1.11, turning beam receive off can actually draw more power. If you have this version, see the question "How do I fix the battery bug in version 1.1?" below.

Other versions of OmniRemote™ do not have this problem. While it is true that the power consumption of the Palm quadruples when it is sending IR, because this happens for only a fraction of a second, no change in battery life will be noticed.

There are two times when OmniRemote™ disables the Palm's internal power switch. This is necessary for technical reasons. It is disabled during training (when the screen says, "Press button on Remote") and auto frequency detection (when the screen says, "Auto Frequency Test"). While the power switch is disabled it is possible to accidentally leave the Palm's power turned on because the normal auto power-off feature cannot operate.

If the auto power-off timer does expire during one of these modes you may notice the power go off unexpectedly when you leave that mode. This is normal behavior and is nothing to worry about.

1. Using the Palm's Prefs program, turn beam receive on (you may turn it back off again if you wish). Install V1.11 (It is not necessary to remove V1.1 before installing V1.11)

or

2. Remove V1.1, then using the Palm's Prefs program, turn beam receive on. (you may turn it back off again if you wish)

or

3. Remove V1.1, then reset the Palm with a paper clip.

Because we are continually writing updates, V1.11 is no longer on the web page, the latest version will work just as well. To download the latest version, click here.

For more info, click here.