Fleetz,

Thanks for your very detailed description and finally indicating that you are using Test IR function. I don't use it nor do I recommend it. I know it's available and tempting to use but in reality, it sometimes does not work like the real remote. Plus, it has indeed caused some problems in the past.

Lyndel

Hi Lyndel,

Can not believe that this is a deep rooted problem that appears to be going back years. Then again with my attempts to get Philips just to acknowledge that I am a customer over the past week or so shouldn't surprise me.

If this issue has been known and for Philips not to flag it is tottally irresponsible as a manufacturer. Maybe they have flagged it but I was unable to find any reference any where within Pronto Philips, documentation, FAQ etc, Is it somewhere that I missed?

It is disappointing as a new user of TSU7000 to have to go through what was I though a bug issue which from all accounts now was something was accepted. From a newbie's perspective knowing what I know now Philips should be force to come out and make a corrective action statement or accept their product has a bug and document it or take the feature out of the software and force the learn function to be done on the remote.

How does one get behind the the great wall of silence at Philips and communicate this?

Sorry to be sounding like I am on a soap box but this has kinda rild me a tad.

Thanks for your support thoughout this issue.

REgards,

Fleetz

Fleetz, the longing running problem with Test IR has not been one of hanging. It has been one of reliability.

Pressing Test IR is not the same as pushing a button on the Pronto. It can work using Test IR and not on the Pronto and vice-versa. That's why most of us don't trust it.

Philips does read this forum. They are now aware of your observation that there is another problem with Test IR.

Thanks Peter for enlighting me. As a newbie here I appreciate the comments and feedback from experienced Pronto users as your goodself.

I appreciate you passing onto Philips my issue of concern. I hope they take it on board and produce a more robust product for us all.

Do you have any suggestion on how I might be able to raise Philips customer support attention on a issue of a faulty Vol + button on my TSU7000? I have tried via Pronto website customer support to get a response nothing. Did you happen to pass on my comments from the detailed posting about Philips lack of customer support response?

Again thanks for your interest, suggestions and feedback.

Regards,

Fleetz

I uninstalled the previous version and then installed the newest version of ProntoProEdit NG. I had the same problems where the program would not communicate with the remote. I followed Lyndels directions and there was a problem with the device in Device Manager. Updating to the new driver fixed the issue.

Thanks for posting the info on how to fix it. I would have spent hours trying to resolve the problem otherwise.

These are the problems that I have:

1. USB driver had to be reinstalled. Had to go to hardware manager and reinstall.
2. MAJOR PROBLEM: Cannot download my .pcf files. Errors.

I had to back out the software, reload the old firmware and old editor to get my 7000 back up.

Any advise on what to do about my pcf files would be appreciated. They open fine in the new editor. But the new editor errors out after clearing memory during the download and tries to do a "conversion". It also errors out when trying to do a "save as". I went back one year with various other earlier pcf files and none would download or save. All error out upon "conversion". Re-downloaded, reinstalled. Firmware seems to be working. I am able to upload and download the new default pcf.

HELP!

Phillips technical support was of no help after over one hour of discussion.

It has now been a while since the firmware update was released, and there is no mention of a possible need to update the USB driver on the Pronto website. Nor is there any mention of new drivers being included with the editing software download. I had to update my Prointo driver and might never have found the new driver file if Lyndel hadn't mentioned it.

C'mon Philips, this is basic information that should be included in update instructions.

What does this mean??

"An error occured wshile converting this configuration file for use by the device."

And how can I avoid this????

It happens on everyone of my pcf files when trying to download to the 7000 using PPENG2 and the new firmware.

Are you sure you set the new editor for TSU7000?

if not sure, Try dropping down "tools" from the menu bar. No press the letter "o" then "c" to choose the correct remote.

When is the 7500 hitting the market?

Last word from Philips is still November on the new models. There distributors are still waiting for setup information and actual costs

Make sure you follow the install procedures outlined by Lyndel earlier in this thread to the letter.

Mike,

The error is in "conversion", not "connecting". My instructions won't help. More than likely, as Peter suggested, the wrong remote type was specified.

The beginning of this thread says that PPENG v2.1.1 adds support for the new remotes. The "what's new" links in Philip's Pronto website do not say what was changed in PPENG v2.1.1 and firmware version 3.8.11. Is there any other changes in PPENG v2.1.1 other than support for the new remotes? What was changed in 3.8.11 of the firmware? I have a TSU7000, and I don't see the point of upgrading the firmware and PPENG if there's no other advantages. However, it doesn't make sense why the TSU7000's firmware would have an update if it's only for PPENG to provide support for the new Prontos. I would think that there's some benefit to upgrading the firmware, but don't know what it is.

A possibility is that they might be using the same firmware for both models.