Philips TSU600099 - Manual (Page 69)

ProntoProEdit 3.0 - User Manual Troubleshooting
Philips Page 69 of 76
Macros seem to be programmed correctly in ProntoProEdit but
are not working on the ProntoPro
You may have to add delays between the different commands in the macro. A
device needs time to receive and execute the command. For example, when a
devices receives the Power on command, it takes some time to start up. So
the device will not be able to receive the next command.
See “ Setting a delay ” on page 51.
The function Test IR does not work properly
When you want to try out the IR code you have assigned, you have to
connect the ProntoPro to your computer.
The function Test IR works best when the ProntoPro’s touch screen is
active.
The function Test IR may not work optimally with timer actions or when
ProntoProEmulator is running.
The CCF on your ProntoPro is invalid or corrupt
“Invalid Configuration File Version”
“File is not a valid configuration”
“CCF file is invalid or corrupt”
See “ Downloading a CCF into Your ProntoPro ” on page 38 to download the
CCF from ProntoProEdit again.
ProntoPro sends out 4 beeps and cannot be activated
The ProntoPro software is corrupt.
See “ Updating Your ProntoPro Software ” on page 8 to update the software on
your ProntoPro.
The bitmap of a button is truncated
You can add four bitmaps to a button, one for each state:
inactive – unselected;
inactive – selected;
active – unselected;
active – selected.
The size of the button is defined by the smallest of the bitmaps used for
different states of the button. You cannot resize a button that contains
bitmaps. The best way to avoid the problem is using bitmaps with the same
size per button.
Buttons without bitmaps can be resized.