Hi John,

Happy Holidays!

I keep trying to get this IR stuff through my thick head but despite trying, I am just not getting it!

I have a doc from Teac, giving me codes for a device I need to program.

It says "NEC format custom code 8520H" (which I assume is hex.)

The doc gives me simple 2-digit hex codes for each of the functions, Hex 00 thru 5F. For example Play is Function 01, within the doc.

What is the best way to go about putting this together?

Just for study, I learned a Teac code for Play, from another remote. Here it is. Does this tell you anything with regard to the above info?


Play
0000 006C 0018 0000 0030 0010 0030 0010 0030 0010 0010 0031 0030 0010 0010 0031 0010 0031 0030 0010 0010 0031 0010 0031 0010 0031 0010 054B 0030 0010 0030 0010 0030 0010 0010 0031 0030 0010 0010 0031 0010 0031 0030 0010 0010 0031 0010 0031 0010 0031 0010 C938


Many thx Dave

0000 Learned Pronto Code
006C 38,381 Khz
0018 24 burst once #
0000 0 repeated #
0 = 0030 0010
1 = 0010 0030
0 0 0 1 0 1 1 0 1 1 1
code between repeats 0010 054b
0 0 0 1 0 1 1 0 1 1 1
lead out 0010 c938

So the only interesting thing is the reversed 0 0 0 1 0 1 1 0 1 1 1 which gives 00010010111 this should be a combination of device and function, a second learned code and 2-digit hex code could explain it.

Dave, if this is supposed to be NEC protocol, are you sure it's a clean learn?

The code is device 0x85 (85H) which is 128 +5 = 133 in decimal.

The function for Play is 20H or 0x20 which is 32 in decimal.

So, you might try Makehex NEC1.irp after editing the irp file to say device = 133. Then, use Function 32 of the generated .hex file.

Lyndel

HI Guys,

Thanks for the help!

I made a mistake on this. The pasted code is function 01 not 00. Here is another learn, which looks the same. FYI, this came from the Nevo SL, learned into the 9600:

0000 006C 0018 0000 0030 0010 0030 0010 0030 0010 0010 0031 0030 0010 0010 0031 0010 0031 0030 0010 0010 0031 0010 0031 0010 0031 0010 054B 0030 0010 0030 0010 0030 0010 0010 0031 0030 0010 0010 0031 0010 0031 0030 0010 0010 0031 0010 0031 0010 0031 0010 C938

Does this make any more sense?

I tried using NEC.irp set to Device 133 and here is what it gave me for function 1, which is Play:

0000 006D 0022 0002 0157 00AC 0015 0040 0015 0015 0015 0040 0015 0015 0015 0015 0015 0015 0015 0015 0015 0040 0015 0015 0015 0040 0015 0015 0015 0040 0015 0040 0015 0040 0015 0040 0015 0015 0015 0040 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0040 0015 0040 0015 0040 0015 0040 0015 0040 0015 0040 0015 0040 0015 0689 0157 0056 0015 0E94

Thx Dave

That code is the same: 0 0 0 1 0 1 1 0 1 1 1

Swords,

Please tell me more. Which code is the same? The new learn is the same as the old learn...yes. Just that both learned codes are for function 01, not 00.

Is the Nec.irp code the same as the learned code?

Thx Dave

.

No I need a second learned code to compare them. Does the nec.rip code works on your device?

This is not NEC protocol or to be more precise, not any NEC protocol I have ever seen. NEC protocol has always contained 32 data bits, 16 bits of device or mfg code (assigned by NEC) followed by 16 bits of function code. In the early days each 16 bit field was composed of 2 8 bit fields the second being the one's compliment of the first (zeros become ones, ones become zeros). NEC then ran out of device/manufacturer codes (256 posibilities in 8 bits) and made the device code a 16 bit field with no error checking allowing for approximately 65000 codes. The function code still was 2 8 bit fileds with redundancy (compliments) to allow for some limited error detection. Device/manufacturer code was sent first followed by function code. The timing parameters for NEC code are in the paper I wrote many years ago on this forum regarding IR coding and HEX reporesentations of the Pronto remotes.

Hope that helps

I don't normally check this forum. Just happened to today. But I'm not on a real computer, so I can't check any details beyond agreeing that the learned signal is not nec protocol

...

The code you learned is not for the device that the doc from Teac describes. I don't know whether you or Teac is confused about which model uses which signals, but one of you must be.

I've seen a bunch of examples where manufacturers said "NEC format" and it wasn't true. But in this case, even if they were wrong about "NEC", there is no way they would say "custom code 8520h" if they were talking about the signal you learned. It must be a different device with an unrelated set of IR signals.

Thank all for the help.

I think the learn might have been bad.

If I were to start from scratch and make the codes via MakeHex, how do I set it up for "NEC Format Custom Code 8520H" ???

I do have the 2 digit functions codes in hex.

Thx Dave