Thanks for the update. As an owner of a 3000, I am looking forward to addressing the only real problem, requiring double-presses of the hard buttons. I was dismayed to see this only being addressed on the 7000. Any information on why there is this discrepency?

Dave,

I was wrong...it is not just firmware but hardware as well. I just got off a mail exchange with the pronto team and it seems the current hardware will not support long codes exceeding a certain number of burst pairs. Bottomline...I will not be able to use my pronto for that particular device. Jeez!

Hellfire, what email address do you use to write to the prontoteam. I used: [email protected] and got a canned go away message --
Dear Peter,

Thank you for your enquiry.

Our technical support desk is in place.

Please click the following link and provide the necessary details to get the help you need as fast as possible.

[Link: pronto.philips.com]

You have following options:
- questions regarding software : [Link: pronto.philips.com]
- questions regarding the device : [Link: pronto.philips.com]

Note : you need to be logged in to be able to use these options.

Thanks and regards,

Prontoteam.

And of course when you log into the locations they suggest, and enter the information, they do not respond at all.

Anyone know how to get through to a reall person or CSR or tech support that is useful?

Ti,

It's mailto:[email protected] (you used 2 'l's) but I'll check it out anyway.

Which device? What code?

I used the address you quote but typed it in wrong above.

The Daikin air-conditioner I was trying to put on the pronto some time back if you recall. The command consists of 2 separate commands that resulted in it exceeding the limit of 105 burst pairs. Just in case you are still wondering, code is below.

0000 007b 006a 0000 00a8 0048 000c 003b 000c 0017
000c 0017 000c 0017 000c 003b 000c 0017 000c 0017
000c 0017 000c 0017 000c 003b 000c 0017 000c 003b
000c 003b 000c 0017 000c 003b 000c 003b 000c 003b
000c 003b 000c 003b 000c 0017 000c 0017 000c 003b
000c 0017 000c 0017 000c 0017 000c 0017 000c 0017
000c 0017 000c 0017 000c 0017 000c 0017 000c 0017
000c 003b 000c 003b 000c 0017 000c 0017 000c 003b
000c 0017 000c 003b 000c 003b 000c 003b 000c 0017
000c 0017 000c 0017 000c 003b 000c 003b 000c 0017
000c 0017 000c 003b 000c 0017 000c 0017 000c 0017
000c 003b 000c 003b 000c 0017 000c 0017 000c 0017
000c 0017 000c 0017 000c 0017 000c 0017 000c 0017
000c 0017 000c 0017 000c 0017 000c 0017 000c 0017
000c 0017 000c 0017 000c 0017 000c 0017 000c 0017
000c 0017 000c 0017 000c 0017 000c 0017 000c 003b
000c 0017 000c 0017 000c 0017 000c 0017 000c 003b
000c 0017 000c 003b 000c 0017 000c 0017 000c 0017
000c 0017 000c 0017 000c 0017 000c 0017 000c 003b
000c 0017 000c 0017 000c 0017 000c 0017 000c 003b
000c 0017 000c 0017 000c 003b 000c 0017 000c 003b
000c 003b 000c 0017 000c 0048

I had 2 separate communications with Philips. The first was through the feedback link on the pronto website. This was when they acknowledged there was a problem. The second was to the pronto team via the mail addy Lyndel posted. I forwarded my earlier communications to them to see if the problem was going to be resolved by the new firmware.

I dropped out of that thread at that point as I have no direct experience with the AC unit. It seems that several remotely controlled AC units use very lengthy codes.

But I'm surprised they say the hardware cannot handle this one. There are only 106 burst pairs and the code is only 150ms long. A Pioneer double code has a longer total length (180ms).

The phone number I've used with success is the one given on the warranty.

I second that concern. Most of us 3000 users have begged and pleaded for that feature. The current firmware has some buttons turning on the LCD and some not. Most buttons now perform actions on first press, but the four below the LCD do not. All we want is the ability to configure which buttons work on first press and which activate the LCD. Philips seems to think we can't handle that much responsibility.

This requested functionality would probably require an update to both PE-NG and the firmware.

This message was edited by onward on 09/21/04 17:41 ET.

Yes, I am just as surprised. I wonder if anyone else has encountered similar problems to mine with other equipment?