DecodeIR, RM and KM request: Yamaha extended NEC gap signals

[The Robman]

Keep in mind that the signals in my file were generated by hand, so it's possible that there's something that I did wrong, from DecodeIR's point of view. I'll download the DLL and test it out later.

Could you post the IR file that you created?

[The Robman]

Dave, I've tested the new version and it looks good. I used some valid NECx1 signals and they decode as NECx1, both normal versions and modified Yamaha versions.

I've also tracked down an NEC1/NEC2 issue.

The following Pronto hex (from Remote Central decodes as NEC2 even though it's clearly NEC1. The problem is the leadout time. The hex below has 00b1 as the final leadout, if you change this to something more realistic like "0EAB" then it decodes as NEC1.

0000 0069 0022 0002 0161 00b1 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0042 0016 0016 0016 0042 0016 0042 0016 0042 0016 0042 0016 0042 0016 0042 0016 0016 0016 0042 0016 0042 0016 0042 0016 0042 0016 0042 0016 0042 0016 0042 0016 0042 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0042 0016 0609 0161 0058 0016 00b1

Here are some hand generated samples that you can use to verify, if you like...

NECx1 (normal)
0000 006d 0022 0003 00ab 00ab 0015 0040 0015 0015 0015 0040 0015 0040 0015 0015 0015 0040 0015 0015 0015 0015 0015 0040 0015 0015 0015 0040 0015 0040 0015 0015 0015 0040 0015 0015 0015 0040 0015 0015 0015 0040 0015 0040 0015 0015 0015 0040 0015 0040 0015 0040 0015 0015 0015 0040 0015 0015 0015 0015 0015 0040 0015 0015 0015 0015 0015 0015 0015 0040 0015 06a3 00ab 00ab 0015 0015 0015 0e79

NECx1-y1
0000 006d 0022 0003 00ab 00ab 0015 0040 0015 0015 0015 0040 0015 0040 0015 0015 0015 0040 0015 0015 0015 0015 0015 0040 0015 0015 0015 0040 0015 0040 0015 0015 0015 0040 0015 0015 0015 0015 0015 0015 0015 0040 0015 0040 0015 0015 0015 0040 0015 0040 0015 0040 0015 0015 0015 0040 0015 0015 0015 0015 0015 0040 0015 0015 0015 0015 0015 0015 0015 0015 0015 06a3 00ab 00ab 0015 0015 0015 0e79

NECx1-y2
0000 006d 0022 0003 00ab 00ab 0015 0040 0015 0015 0015 0040 0015 0040 0015 0015 0015 0040 0015 0015 0015 0015 0015 0040 0015 0015 0015 0040 0015 0040 0015 0015 0015 0040 0015 0015 0015 0015 0015 0015 0015 0040 0015 0040 0015 0015 0015 0040 0015 0040 0015 0040 0015 0015 0015 0015 0015 0015 0015 0015 0015 0040 0015 0015 0015 0015 0015 0015 0015 0040 0015 06a3 00ab 00ab 0015 0015 0015 0e79

NECx1-y3
0000 006d 0022 0003 00ab 00ab 0015 0040 0015 0015 0015 0040 0015 0040 0015 0015 0015 0040 0015 0015 0015 0015 0015 0040 0015 0015 0015 0040 0015 0040 0015 0015 0015 0040 0015 0015 0015 0015 0015 0015 0015 0040 0015 0040 0015 0015 0015 0040 0015 0040 0015 0040 0015 0015 0015 0015 0015 0015 0015 0015 0015 0040 0015 0015 0015 0015 0015 0015 0015 0015 0015 06a3 00ab 00ab 0015 0015 0015 0e79

[3FG]

Could you post the IR file that you created?

I'm trying to think up a good excuse-- I didn't make one. Instead I repeatedly downloaded learned signals from a remote, and pasted in vaious Pronto Hex codes, some of which I modified on the fly.

[The Robman]

No worries, I found some NECx1 and NECx2 signals over at Remote Central. What I did was this, I looked up a device that uses NECx1 in my jp1 master 1.05 spreadsheet, then went and looked for discrete codes for that brand over at R/C.

[ElizabethD]

I have a Zenith DVD player and a remote plus an old IR file with NECx1 learned signals. Would any of this be of any use to you? They're not yamaha type of signals, just old, 2005 stuff.

[3FG]

Liz,
Thanks for the offer, but my plan is to only deal with NEC signal which differ from the traditional rule which defines the 4th data byte in terms of the 3rd. I don't intend to worry about the differences between NEC1/NEC2/NECx1/NECx2, which are concerned with lead times and repeat format, and which I suspect are handled well already.

[3FG]

Rob,
I think that the signal which you've labeled as NECx1-y1 is really -y2. The one labeled as -y2 is really -y1. I use IRv8.03 to keep track of this. The IRP form is shown in the learned signal section, and it includes, for example, this: {A=$B4B46E11,B=$0}. This is from the hex you've labeled -y1. Comparing the bit flip in this signal to that of Pronto Hex provided by Yamaha (which I think we agree should be called -y1), it's clear that 6E 11 is not a -y1 pair. 6E 90 is -y1.

As I mentioned to Liz, I don't intend to try to "improve" the resolution of the various NEC styles, and my ain in coding up the Yamaha styles is to not alter the logic which decides the flavor of NEC.

[The Robman]

You're right, I re-labeled them in IR but forgot to re-label then in notepad which is where I copied these from.