confusing protocol

lucindrea · Post by **lucindrea** » Tue Oct 12, 2004 7:07 am

ok i have a creative labs speaker system and i have gotten the vol controls in my replay remote .. BUT there are 1 or 2 things i just cannot figure out ..

one or 2 of the keys i have learned on my RS 15-2104 use both NEC and NEC1 .. i havent worked out how to send both signals at the same time , but i havent really looked for that part yet .. i got one key that uses some protocol i have never hear of , according to ir.exe it's
Gap-530-1367-32? with c1.44.8f.70 under misc .. ( i could put the entire "sent when key pressed " if ya want ) ... anyone have a clue what this is?

anyone got any clues?

johnsfine · Post by **johnsfine** » Tue Oct 12, 2004 7:22 am

The Gap decode means the signal couldn't be decoded, and the decoder is dumping out internal data to help an expert guess what is wrong.

In this case, it's clear that you have a bad learn of an NEC1 signal, with OBC number 143. So you shouldn't need to get a clean learn and redecode, just use that OBC number in KM or RM.

There is an NEC variant that consistently produces an NEC decode followed by an NEC1 decode for each key. I think there is a parm value for an NEC1 upgrade that will reproduce that. However, I'm not convinced that's what you really have. More likely you just have a bad learn. In which case just ignore the extra NEC decode and use the NEC1 decode.

johnsfine · Post by **johnsfine** » Tue Oct 12, 2004 7:29 am

I checked a couple CCF files
www.remotecentral.com/.../greg-brezinski_pro.zip
and
www.remotecentral.com/.../pete-hillyer_ccf.zip

Both show that this device does use that rare version of NEC that generates an NEC decode and an NEC1 decode for each key. (And one of them lists OBC 143 as the "CMSS 5.1" command).

Probably NEC1 will work well enough, but probably Rob remembers what parm value you need in an upgrade to get it exactly right (two regular frames before switching to NEC1 like repeat frames).

lucindrea · Post by **lucindrea** » Tue Oct 12, 2004 7:32 am

ya i was scratching my head for a little while trying to work out why just that one key produced that .. i was thinking all was ine because the learned button does what it should .. then i looked at the volume controls that i allready got working a long long time ago .. they just use NEC1 and nothing else ..
i went with just plain NEC1 on all 4 of the buttons i wanted and they all work

... i can fiinnaly put the creative remote into a drawer somewhere ...

heh i allways seem to try to work somthing out .. get frustrated , spend 20 mins searching forums , post my question , then before somone replys ( or in this case a few mins after ) i figure it out myself **shrug**

Post by **The Robman** » Tue Oct 12, 2004 9:26 am

For single device code signals you should use a parm value of "0A". For two device code signals the parm value should be "2A".

I have called this variation of the protocol NEC1-X2 in my new Devices.xls spreadsheet. Maybe we can update KM and protocol.ini to use this name for this variation also.