Try this one:
0000 006D 0012 0012 0008 0022 0008 0051 0008 0027 0008 006A 0008 0032 0008 0032 0008 0027 0008 0051 0008 020D 0008 0022 0008 0037 0008 001D 0008 0027 0008 0032 0008 0032 0008 001D 0008 001D 0008 0BF2 0008 0022 0008 0051 0008 0027 0008 006A 0008 0032 0008 0032 0008 0027 0008 0051 0008 020D 0008 0022 0008 0060 0008 0046 0008 0027 0008 0032 0008 0032 0008 001D 0008 001D 0008 0BF2
That is a very hard IR protocol for a learning remote to learn, and NG Prontos aren't great at learning. The samples you posted were much closer to correct than I would expect an NG Pronto to get.
I hope the one I posted is correct. I haven't yet worked out all the details to make my DecodeIR and MakeHex programs process this code type correctly, and I'm also unsure whether the usually innocuous translation glitches in ProntoEditNG will corrupt a pasted code of this type. I do not expect PENG to process this Pronto Hex string without changing it. I just hope that the changes it will make won't matter.
Once we get this one right, I can give you the method to construct the full set with MakeHex.
On September 30, 2007 at 18:38, marcelser said...
(seems to be 2 different codes):
No. All the samples you learned were the same code. Pronto Hex can look very different and still represent the same signal. That is even more true with a signal that is this difficult to learn.
