I am trying to use a file I found that contains pronto codes for all the buttons on a new device I bought.

They don't work correctly.

Here is an excerpt from the file:

I-O DATA LinkPlayer2 Remote Control IR codes:

Keypad UP:

0000 0067 0000 0026 016e 00b3 0019 0014 001a 0014 001a 0013 0019 0042 001a 0013 0019 0014 001a 0014 001a 0013 0019 0014 001a 0041 0019 0042 001a 0013 0019 0014 001a 0041 0019 0042 001a 0041 001a 0014 001a 0013 0019 0042 001a 0013 0019 0042 001a 0013 0019 0014 001a 0014 001a 0041 001a 0041 0019 0014 001a 0041 0019 0014 001a 0041 0019 0042 001a 0041 001a 06a4 016e 0058 001a 0f27 016e 0058 001a 36e4

Keypad down:

0000 0067 0000 0027 016e 00b3 0019 0014 001a 0014 001a 0013 0019 0042 001a 0013 0019 0014 001a 0014 001a 0013 0019 0014 001a 0041 0019 0042 001a 0013 0019 0014 001a 0041 0019 0042 001a 0041 001a 0014 001a 0041 001a 0041 0019 0014 001a 0041 0019 0014 001a 0014 001a 0013 0019 0042 001a 0013 0019 0014 001a 0041 0019 0014 001a 0041 0019 0042 001a 0041 001a 06a4 016e 0058 001a 0f27 00d5 0005 0094 0058 001a 2dce

They all repeat. If I press down it goes down twice. If I press up it goes up twice.

Before I go through the trouble of learning each button my self I was wondering what I might have done wrong?

I have a TSU3000 updated to the most recent firmware and was using the most recent version of ProntoEdit.

I don't think YOU did anything wrong. I think the original learn of those signals was done with some device that doesn't get Pronto Hex quite right.

Or possibly, someone distorted the Pronto Hex on purpose to keep ProntoEdit from loosing the higher than typical frequency when recognising and translating to the condensed form of Pronto Hex for NEC1.

For at least some models, PPENG and the firmware now preserve this higher frequency in the condensed form. But I don't specifically know about the TSU3000 regarding that.

The condensed forms would be

900A 0068 0000 0001 08E6 14EB

and

900A 0068 0000 0001 08E6 16E9

The "Pronto for dummies" answer is for me to just relearn the buttons!

How would I go about converting from long to short? Is there a program or do you just think in HEX?

First make sure the short form really works.

I don't know whether your device really uses the higher frequency indicated by those long form signals.
I don't know whether the current TSU3000 firmware respects the higher frequency encoded in those short form signals (older TSU3000 firmware did not).
If the device really uses higher frequency and the TSU3000 doesn't do the right thing, I don't know whether that will break anything. Devices often ignore moderate size errors in frequency.

If it doesn't work, then I'd expect related problems with any really clean learn you make yourself (It would be automatically translated to short form).

As for programs, vs. thinking in hex. I do think in hex. There is a program to read the long form and translate it to protocol/device/subdevice/function (In this case NEC1 protocol device 8, subdevice 230, functions 20 and 22). But I don't know any program for translating from NEC1:8.230:20 to 900A form. I just do that in my head because I think in hex.

The first program is the JP1 version of IrTool.exe, which requires DecodeIr.DLL
[Link: remotecentral.com]
[Link: john.fine.home.comcast.net]

I just finished learning all the buttons.

They all ended up like the condensed version you showed.

They also all seem to work.

Thanks!

And, as you may have found, it is usually easier to learn the codes yourself, rather than stuff around with other people's PCFs.

Ditto!

Why do people find learning codes so daunting? When I get a new component, that is the first thing I do, and I do it with a TS1000. People have made fun of me for doing programming with a dinosaur, but it works every time.

I encourage all people who are new at this to just learn the codes. It is a lot easier than trying to use the database, and if you try to use other peoples' pcfs, you will have to basically install them, complete, before you can even verify that they work at all for your device. If you learn the codes, you are starting with a remote guaranteed to work: the component's own factory remote!