Hi,

I have problems using my Panasonic TV with the Pronto NG. In order to switch on the TV, I have to press the 'Power On' key for 1-2 seconds.

I learnd the following code for 'power on':

0000 0071 0000 0032 0080 003F 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0030 0010 0030 0010 0030 0010 0030 0010 0010 0010 0010 0010 0010 0010 0030 0010 0030 0010 0030 0010 0030 0010 0030 0010 0010 0010 0030 0010 0AAB

When I hold the button 1-2 seconds manually, everything works fine, so I used the same code in a macro with a duration of 1,5 secs.

But this doesn't work. The signal is send only for a few msec. It doesn't matter which duration (up to 5 sec) I choose for the code.

Is there a possibility to repeat the signal in order to send it for 2 secs?

I heard that this is a known problem with the Pronto NG.

You can actually change the duration in the code itself. Is this what you mean? because this certainly works on my satellite box for slow motion (hold down pause on the original remote, I have a separate button with a 1 or so second duration

That should have worked. I'm not an expert on that aspect of the NG Pronto firmware, so I'm not sure what possible problems there may be.

I expect an expert (hopefully one will read this thread soon) would want to know which model of Pronto NG, you have; What version of the firmware it has (maybe it needs a firmware update); and which version of ProntoEditNG you're using.

Maybe you should also describe more detail of where/how in the macro definition you specified the duration.


I'm pretty sure it isn't possible. You can't stop an NG Pronto from inserting a significant delay between steps in a macro. That delay is almost always enough to cause the device receiving the IR signal to decide the signal is over.

I have a RU950. My config screen told me:

Application: v3.1.15
Database: v2.60E
Boot: v3.44


I could reduce the problem to a minimum. What I did:

1. Created a new button
2. Created a new IR Code Action
3. Used code from universal Database (TV/Panasonic/Codeset 1677/Power on)
4. Set 'Duration minimum' to 1.5

When I test the configuration with my PC using 'Test IR', everthing works fine. TV's status LED blinks for 1.5 sec and TV turns on.
When I tap the button on the remote, I can only see a short flash of the status light. Shows me that the duration is much lower than 1.5 sec and nothing happens.
When I hold the button for 1.5 sec manually, I see my TV's status LED blinking for 1.5 sec and the TV turns on.

It doesn't matter if I use a code from the universal database or a learnd code.

your firmware is way out of date, update to the latest version then try again.
[Link: pronto.philips.com]
What's new in TSU3500/RU960?
Pronto NG Firmware Update
The Pronto NG firmware update is packed in a download tool that automatically installs the latest firmware in your device. It works independently from ProntoEdit NG, and is easy to install.

New in version 3.9.12

In this release, the following issues are solved:

the issue that the Pronto became unresponsive after a longer period using the remote. This issue only occured when the configuration file contained database codes.
the problem with the LCD backlight always turning on a keypress.


New in version 3.9.8

Control the screen activation yourself
Additional options are added to the settings mode to allow for configuration of screen activation rules. You can enable and disable the tiltsensor and pick from three different activation modes for the buttons below the LCD and the cursor.

New model support
Support for the new TSU3500 and RU960 Pronto touch screen remotes

Solved the following problems:

Previously, with accidental double button press, macro execution was stopped. This could result in getting stuck on a page after a jump, if this page had no navigation possibility to get out of the page. Now a double press will not have an effect on the macro execution. As a result, when started, macros cannot be interrupted anymore.
Problem fix for the situation where sometimes an accidental double press would result in a freeze of the product. This could be demonstrated by continuously sending out IR code or a never-ending beep.
If your text on a button is too long, the end of the text would be replaced by ‘…’. This could sometimes result in unexpected behavior. This is now fixed.
Problem with sending out some IR codes, example Sony DVD codes now solved. These codes were terminated too quickly when a short button press was used.
In relation to editor, testing IR codes with set duration, will respect the duration setting. Previously, up to 150ms deviation could occur.


New in version 3.6.7

Faster and more reliable up- and downloading
Due to improvements of the communication protocol, up- and downloading is improved. Depending on the pcf, this can be more than 40% times faster.

Support for new IR protocols

Dedicated support for Windows Media Center Edition codes, with the addition of a Media Center device in the default configuration.
Dedicated support for Somfy codes.
Possibility to enter RC5, RC6, RCMM directly in the ProntoEdit NG.


More reliable RF
Due to the implementation of a new RF protocol, the communication between the RF Extender and the Pronto NG is more reliable.

User defineable IR code duration
You can now specify the minimal time that an IR code will be sent out. This allows support of e.g. projectors that need to receive an infrared signal for minimally 1 sec before switching off.

Faster PCF loading
Depending on the PCF, this can be up to 2 times faster.

Last, but not least, the gallery will also open a lot faster.

New in version 3.1.15

Smart surf and navigation mode buttons now send out IR code directly. Double press is not needed anymore.

Those details are very helpful. Even though I don't really understand how duration is processed in the NG firmware, I have a good guess based on what you just described.

The purpose of the duration setting is use in a sequence. Maybe it only works in a sequence.

When a learned signal or alias of a learned signal is the only action in a button's action list, the actual press of the button can control the duration of the signal.

If there is more than one action in the action list, the button press can't control the duration, so you need a programmed duration.


So that tells me the signal is the only action in the action list. Try adding another action. Even an insignificant delay action after the signal is enough that the button press can't control the duration. Maybe then the programmed duration will take effect.

Edit: I typed the above before seeing post 5 of this thread. Now it seems more likely that post 5 is correct, meaning you have mixed a version of ProntoEditNG that supports the duration feature with a version of the NG firmware that doesn't support the duration feature.

That's it !!! The new firmware.

I was sure that I had a new fireware on my pronto.

Thank all for your very fast help :)