This is something strange and can not find the reason... I get error messages that Philips Yamaha IR codes removed from the buttons action list when I upload a project to TSU9600. Only these IR libraries, nothing more.

Seems simple, but it does not for me. I added them into MyDatabase from Philips Database, then Added the Component to Project. The codes have been tested successfully from MyDatabase (function test by PEP2 via TSU9600), the equipment did respond. There are green ticks against all the codes in component...

When I upload the project to TSU 9600 I get the message that the IR codes have been removed from buttons and, yes, RFX9600 IR port shows no activity as I press the button).

I also noticed, that these IR libraries got invalid in Component list (there is a warning triangle sign against every IR code for the component) when I close the project/exit from PEP2 and open the project again. Of course, I can swap the libraries from MyDatabase or Philips to repair (this is what I do) but that helps until I close the project again...

Indeed this drives me a bit crazy as I cannot use those Yamaha libraries at all and cannot tell what causing that!

Here is my environment:

TSU9600 v2, App v6.0.21., IR firmware 3.0.11.
PEP2 v2.0.34.0, build June 26 2008, WinXP SP3

"Problematic" IR libraries (Philips Database):

Yamaha - Amplifier - AX596
Yamaha - AV Receiver - TX497

Any advise what to do?

There's probably more to this problem than I am seeing in your post: Your reference to the 'conflict triangles' on the component functions looks to be one of the root causes of problem. Each component function with a triangle is in conflict between 'MyDatabase' and the XCF project. Basically PEP2 is saying: "which IR code do you want to use for this function: your project IR code differs from what is stored for the same device in MyDatabase".

If you click on the traingle on each conflict function, you should get a window that allows you to update MyDatabase from the project or the other way around; depending on which version of the code is the correct one.

Once you have resolved all of the conflicts, try uploading the fixed version to your TSU: If it is just a project vs. database code conflict you should be green to go.

What are the error messages that you are getting?

Also, it is called "downloading" when loading a configuration into your Pronto.

I think this an many other database related problem like this are solved by upgrading to the latest editor #2,118.

nimnul,

Thank you. Upgrading to 2.1.18 helped. Obviously, bugs (or as Pronto team prefers to say "an important problem") in the PEP2 or related software. Up to date software is the first thing that should have come into my mind, strangle it is that I missed that...

Peter -- My thought exactly, but I do recall that URC started out with that sort of terminology - "Downloading" from the remote and "Uploading" to the remote. I think that have changed, and suspect the original terminology comes from some other area of computerspeak.

No holy war, but I find it inconvenient the way PEP uses the "upload/download" terminology .

I fully agree what is said in Wiki on the terminology:

Technically if the user uses the receiving device to initiate the transfer then it would be a download and if they used the sending device to initiate it would be an upload.

Since the PEP is the side that initiates the transfer it would be more logical (and naturally enough) to call the process as uploading...

It's not really PEP terminology - this has always been the terminology used at RemoteCentral.

In Client/Server terms going from client to server is always uploading and from server to client is always downloading. The Pronto is the Client and your PC is the Server. The PC is called the server for lots of reasons but mostly because it holds the master copy of the configuration.