JP1 Remotes

Hi All,

I captured my Channel Master remote and got NEC1-f16 IR protocol (please look at this .ict file: http://www.hifi-remote.com/forums/dload ... e_id=12073). Can you please help choose proper IR protocol in the Remote Master? Now I see there only NEC1-f16 fixed and NEC1-f16 official, but these IR protocols don't work with my box.

Thanks,
Vladimir

I "think" I have the most up to date tools. I loaded the ICT file, and I am seeing Nec1-rnc (reversed nibble component signals)

I see that the description of Nec1-RNC has the last two nibbles of the signal reversed.

-rnc: D:8,S:8,~F:4:4,~F:4 (complement F and reverse the nibbles)

I don't see any way to create that in RemoteMaster, so apparently my protocols.ini is not the correct one.

We can always create a custom, but I'd like to have the protocol.ini that has this.

vickyg2003
Hi Vicky,

Thanks for your reply!
Do you know approximate Remote Master (protocol.ini) release date? When will we be able to create binary files?

Thank you,
Vladimir

Vicky,
I don't think we have ever had a version of protocols.ini with an entry for NEC-rnc. However, the SlingCatcher uses this protocol, so the executor shuold already exist, at least for Samsung processors.
http://www.hifi-remote.com/forums/dload ... ingCatcher

Thanks Dave, the I couldn't find that post to save my life.

Volodymyr, I'm going to guess with a name like that you can probably do the hex math necessary to do the conversion

Open Rob's SlingCatcher RM file from 3FG's link

Change the name

Enter your decoded device as the first device.
Second device = 255-first device.

On functions tab enter your functions and OBCs

Calculate byte 2 by complementing the first byte of hex, and then transposing the hex digits.

If you need more help, let us know.


Remember to post your upgrade.

Thanks Dave and Vicky!

I've changed several OBC codes in the RMDU file and tested on the box. Everything works filne.
Working rmdu file is here (http://www.hifi-remote.com/forums/dload ... e_id=12078).

Thanks again!