Is there a set of "well defined" IR codes for the NEC 6121 (UPD6121G-001)?

Specifically I'm looking for IR codes created from the specifications - not learned with the IR read feature.

I've tried the IR learn and I can get it to work with the Pronto albeit not nearly as reliably as the original remote. I'm guessing it would work great with the proper set of programmed IR codes, and since the NEC 6121 is fairly common I would guess someone has already entered the codes from the NEC spec sheet to create the "perfect" Pronto emulation...

Thanks,
Peter

Hmmm... Looks like this is more of a Pronto limitation. Apparently the Pronto does not implement the NEC protocol? In addition to the RC5/6 and RC-MM we need a "NEC" button in ProntoEdit...

Hi , i have never had a problem capturing NEC codes, make sure there are new battries in the remote and that you are pointing to the right part of the TSU to capture the code. also you may need to have the remotes around 300mm away from each other.

Post the hex code so we can see what it looks like

Peter,

900A is the shortened NEC format. As GoPronto suggests, can you please post one of your learned codes?

Here are a few of the learned codes.

Menu left:

0000 006D 0022 0002 0157 00AB 0016 0015 0015 0015 0016 0015 0016 0015 0015 0040 0016 0015 0015 0015 0016 0015 0016 0040 0016 0040 0015 0040 0016 0040 0016 0015 0016 0040 0016 0040 0015 0040 0016 0040 0016 0015 0016 0040 0016 0040 0015 0015 0016 0015 0016 0015 0015 0015 0016 0015 0016 0040 0016 0015 0016 0015 0015 0040 0016 0040 0016 0040 0015 0040 0016 05EF 0157 0055 0015 0E4C

Menu right:

0000 006D 0022 0002 0156 00AC 0015 0015 0016 0015 0016 0015 0015 0015 0016 0040 0015 0015 0016 0015 0016 0015 0015 0040 0016 0040 0016 0040 0015 0040 0016 0015 0015 0040 0016 0040 0016 0040 0015 0015 0016 0015 0016 0040 0016 0040 0015 0015 0016 0015 0016 0015 0015 0015 0016 0040 0015 0040 0016 0015 0015 0015 0016 0040 0015 0040 0016 0040 0016 0040 0015 05F0 0156 0055 0016 0E4C

Menu up:

0000 006D 0022 0002 0157 00AB 0016 0015 0016 0015 0015 0015 0016 0015 0016 0040 0016 0015 0016 0015 0015 0015 0016 0040 0015 0040 0016 0040 0016 0040 0015 0015 0016 0040 0015 0040 0016 0040 0016 0015 0016 0040 0016 0015 0016 0040 0016 0015 0016 0015 0015 0015 0016 0015 0016 003F 0016 0015 0016 003F 0016 0015 0016 003F 0016
0040 0015 0040 0016 003F 0016 05EF 0157 0055 0016 0E4B

Menu down:

0000 006D 0022 0002 0157 00AB 0016 0015 0016 0015 0015 0015 0016 0015 0016 0040 0016 0015 0016 0015 0015 0015 0016 0040 0015 0040 0016 0040 0016 0040 0015 0015 0016 0040 0015 0040 0016 0040 0016 0040 0015 0040 0016 0015 0015 0040 0016 0015 0015 0015 0016 0015 0016 0015 0015 0015 0016 0015 0016 0040 0016 0015 0016 0040 0016 0040 0015 0040 0016 0040 0016 05EF 0157 0055 0016 0E4B

Peter,

Using IRTool.exe from the Classic Pronto Files section, I decoded the data above. IRTool says the codes are the Kenwood/Yamaha protocol which matches NEC1.irp for MakeHex tool.

Device = 16(decimal) or 10(hexadecimal)
The above functions are respectively
Menu Left = 13 (decimal) or 0D (hexadecimal)
Menu Right = 12 (decimal) or 0C (hexadecimal)
Menu Up = 10 (decimal) or 0A (hexadecimal)
Menu Down = 11 (decimal) or 0B (hexadecimal)

So, with this knowledge, you can use MakeHex to generate Raw Pronto Hex (0000 format as above) using NEC1.irp and supplying the device = 16 and specify Functions 0..255

You can also simply supply build the Pronto shorthand (search this or NG forum for posts by John Fine and/or 900A) as:

900A 006D 0000 0001 10EF 0DF2
900A 006D 0000 0001 10EF 0CF3
900A 006D 0000 0001 10EF 0AF5
900A 006D 0000 0001 10EF 0BF4

Now, let's analyze what is going on here with the shorthand format.

900A 006D 0000 0001 10EF 0DF2

10 is the device and the EF part that follows is in hexadecimal 255 - (device) or 255 - 16 = 239 (decimal) or EF (hexadecimal). Use Windows Calculator to figure out the magic number.

0D is the function and the F2 part that follows is hexadecimal 255 - (function) or 255 - 13 = 242 (decimal) or F2 (hexadecimal).

So, following this pattern you can build out your own functions to test:

functions 1-9
900A 006D 0000 0001 10EF 01FE
900A 006D 0000 0001 10EF 02FD
900A 006D 0000 0001 10EF 03FC
900A 006D 0000 0001 10EF 04FB
900A 006D 0000 0001 10EF 05FA
900A 006D 0000 0001 10EF 06F9
900A 006D 0000 0001 10EF 07F8
900A 006D 0000 0001 10EF 08F7
900A 006D 0000 0001 10EF 09F6

functions 10-13 are above

functions 14-17
900A 006D 0000 0001 10EF 0EF1
900A 006D 0000 0001 10EF 0FF0
900A 006D 0000 0001 10EF 10EF
900A 006D 0000 0001 10EF 11EE

etc...

Note that the above codes are just functions I generated. Not sure if they will work with your equipment but you can quickly try new functions if you are Shorthand-saavy and don't have to learn individual codes. Note that this particular protocol supports up to 255 functions for a single device. Some equipment utilizes more than a single device code but I doubt yours will be in this category. If you think it might, you can verify using IRtool and paste a learned suspect code to ascertain the Device and Command format.

I know this is likely not what you had in mind but knowing this information may help you in the future. Also note that the Pronto Hex IR code format (Raw 0000 format) is documented in a very nice document by Barry Gordon in the Classic Pronto Files Section under User Documentation. It is entitled "Pronto Hex IR Format", IIRC.

I find it strange that these codes don't work because there is nothing wrong with them but try what lyndel suggested.

Latest versions of MakeHex, MakeHex GUI, IRTools and DecodeIR.


Cheers
Jason

If they are not working, try adjusting the IR Duration from something other than Default to something that does work.

This trick is sometimes necessary if the codes are being used in a Macro and not actually being sent by a physical button press and hold.

:-)

Lyndel, thanks for the excellent description and the shorthand 900A codes. Those are much easier to use!

The codes I posted do work. The 900A codes also work. I just found out that the "reliability" issue I referred to in my first post is 100% repeatable: The problem is that when I press the same button repeatedly, *every second* button press (IR code) is lost.

I think a possible explanation is that my device is using "Toggle IR Codes", see page 2 [Link: hifi-remote.com]

Any idea to solve this? (Where is the parity bit?)

Thanks,
Peter

.deleted

There is a discussion of this, I think, in the Classic Pronto Forum where you basically have to learn 2 versions of the code and then append the IR code data together. There may be other ways around this. Eigeny (Eugene) Eulanov, once upon a time knew all the in's and out's of the Classic Pronto Firmware and wrote a document that is published alongside Barry's Classic Pronto Hex Format document in the Classic Pronto Files-User Documentation subsection.

Not sure if any of this will help but it is what I can offer.

If I understand it correctly, I might be able to work around this by sending an unused command code (function) together with every real command. For instance send 0D (Menu Left) and then FF (unused) when the Menu Left button is pressed. However, the parity bit of the FF command needs to be set differently. Not sure how I can accomplish this but maybe I'll figure it out if I read the docs...

Thanks,
Peter

I don't understand how this could be happening. NEC Protocol does not have a Toggle Bit (Parity Bit).

What is the actual device you are trying to learn the codes from?

Did you try increasing the duration as Lyndel suggested?

Maybe you could try NEC2 Protocol Codes. They are the same as NEC1 but repeat the entire pattern.

Try these,

Menu left:13

0000 006D 0000 0022 0157 00AC 0015 0016 0015 0016 0015 0016 0015 0016 0015 0041 0015 0016 0015 0016 0015 0016 0015 0041 0015 0041 0015 0041 0015 0041 0015 0016 0015 0041 0015 0041 0015 0041 0015 0041 0015 0016 0015 0041 0015 0041 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0041 0015 0016 0015 0016 0015 0041 0015 0041 0015 0041 0015 0041 0015 0689

Menu right:12

0000 006D 0000 0022 0157 00AC 0015 0016 0015 0016 0015 0016 0015 0016 0015 0041 0015 0016 0015 0016 0015 0016 0015 0041 0015 0041 0015 0041 0015 0041 0015 0016 0015 0041 0015 0041 0015 0041 0015 0016 0015 0016 0015 0041 0015 0041 0015 0016 0015 0016 0015 0016 0015 0016 0015 0041 0015 0041 0015 0016 0015 0016 0015 0041 0015 0041 0015 0041 0015 0041 0015 0689

Menu up:10

0000 006D 0000 0022 0157 00AC 0015 0016 0015 0016 0015 0016 0015 0016 0015 0041 0015 0016 0015 0016 0015 0016 0015 0041 0015 0041 0015 0041 0015 0041 0015 0016 0015 0041 0015 0041 0015 0041 0015 0016 0015 0041 0015 0016 0015 0041 0015 0016 0015 0016 0015 0016 0015 0016 0015 0041 0015 0016 0015 0041 0015 0016 0015 0041 0015 0041 0015 0041 0015 0041 0015 0689

Menu down:11

0000 006D 0000 0022 0157 00AC 0015 0016 0015 0016 0015 0016 0015 0016 0015 0041 0015 0016 0015 0016 0015 0016 0015 0041 0015 0041 0015 0041 0015 0041 0015 0016 0015 0041 0015 0041 0015 0041 0015 0041 0015 0041 0015 0016 0015 0041 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0041 0015 0016 0015 0041 0015 0041 0015 0041 0015 0041 0015 0689

Thanks Jason. Unfortunately those codes don't work any different.

The unit is a TacT Audio TCS MkIII. In this 3rd revision TacT removed all the RS-232 commands for menu control so now IR is required.

The TCS remote is a generic Taiwan/China remote with a NEC uPD 6121-001 chip. (I have opened up the remote, so I know this for a fact).

When I press Menu Right 4 times in a row (< 1 sec between presses) on the original remote, the cursor moves 4 steps.

When I do the same on the Pronto, I hear it beep 4 times but the cursor only moves 2 steps. Every second IR command is lost. (Since the Pronto is beeping 4 times, I would assume it sends the command 4 times).

If I press the button slowly (> 2 sec between presses), then the Pronto does work fine.

Thanks,
Peter

I have also tried using 0.01, 0.05, 0.10, 0.20, and 0.50 for the duration. No difference there. Can't see that a bigger value than 1/2 a second would make a difference here (any reason to try it?)