Page 1 of 1

What does this ccf data mean?

Posted: Thu Feb 05, 2004 1:58 am
by jwkxneud
I noted that remotecentral has a file for my onkyo TX8211. So I ran it through the decoder. Here's the relevant bit. What's up with the protocol switching between NEC1 and NEC2? I don't know the difference between the two, but this output looks very odd to me. Could this be some error in the ccf decoding, or the learning? Do you think the OEM remote actually uses two protocols?

NEC1 210 109 93 232 Learned SLEEP TX8211 38.0289 34 2
NEC1 210 109 4 180 Learned POWER TX8211 38.0289 34 2
NEC2 210 109 3 187 Learned {Vol-} TX8211 38.0289 0 34
NEC2 210 109 2 183 Learned {Vol+} TX8211 38.0289 0 34
NEC1 210 109 5 184 Learned {Mute} TX8211 38.0289 34 2
NEC1 210 109 8 053 Learned TAPE-1 1 TX8211 38.0289 34 2
NEC1 210 109 7 186 Learned TAPE-2 1 TX8211 38.0289 34 2
NEC1 210 109 11 059 Learned TUNER 1 TX8211 38.0289 34 2
NEC1 210 109 9 057 Learned CD 1 TX8211 38.0289 34 2
NEC1 210 109 10 055 Learned PHONO 1 TX8211 38.0289 34 2
NEC2 210 109 0 181 Learned `Up_Arrow 1 TX8211 38.0289 0 34
NEC2 210 109 1 185 Learned `Down_Arrow 1 TX8211 38.0289 0 34
NEC1 210 109 74 039 Learned GROUP 1 TX8211 38.0289 34 2

Re: What does this ccf data mean?

Posted: Thu Feb 05, 2004 3:04 am
by wwwoholic
jwkxneud wrote:Do you think the OEM remote actually uses two protocols?
And two sub-devices as well. See Onkyo files at yahoo groups

Posted: Thu Feb 05, 2004 5:25 am
by johnsfine
They use NEC2 for keys, such as vol and arrows, that should repeat while held and NEC1 for keys that shouldn't.

The only difference between NEC1 and NEC2 is the way the key repeats while held. Maybe the device simply understands NEC2 style repeat while held for all keys. Then the remote must disable the repeat while held for most keys by not using NEC2.

I know that if you use NEC1 for VOL etc., the key will fail to repeat while held. I assume that if you use NEC2 for POWER etc., the key will repeat when it shouldn't.

Posted: Thu Feb 05, 2004 7:26 am
by The Robman
You can use the "NEC 2DEV Combo" protocol in KM to handle this.