NRC17 (old and new)

General JP1 chit-chat. Developing special protocols, decoding IR signals, etc. Also a place to discuss Tips, Tricks, and How-To's.

Moderator: Moderators

Post Reply
spock
Posts: 39
Joined: Tue May 17, 2005 11:40 am
Location: Germany

NRC17 (old and new)

Post by spock »

old...

A friend of mine bought a NOKIA "Mediamaster 150 T" (DVB-T receiver) at ebay without remote control (for 1 Euro 8-) ) .

I discovered that it uses the NRC17 protocol, but I couldn't get the NRC17 (=00 BD) in RM to work.

After doing some research I found that (at least for some older S3C80 remotes with 00BD built in)
I had to change the RM protocol as follows:

[NRC17 (old)]
#Nokia Remote Control protocol
PID=00 BD
FixedData=00
DevParms=Device:7,OBC>127:bool
DeviceTranslator=Translator(lsb,0,7,1,0) Translator(1,1,0,0)
DefaultCmd=80
CmdParms=OBC:7
CmdTranslator=TranslatorWithDevBool(lsb,1,0,7,1)

#code section from 00 BD
Code.S3C80=...
Code.6805-RC16/18=...

After that change the programmed remotes (URC-7541 & 7552) generate NRC17 signals that fully
correspond with the DecodeIR "learned signals" protocol/device/OBC output.
(And they do work with the "Mediamaster 150 T".)

I know however, that this 00BD protocol is not 100% NRC17 according to
http://www.sbprojects.com/knowledge/ir/nrc17.htm
(supporting only half of the OBC range with one upgrade and only 7 bits of the device address - devices 0..127)

btw...
There are 2 entries for PID=00 BD in protocols.ini.
The latter has the same code section for S3C80 and 6805..., but in addition a code for HCS08.
Shouldn't the entries be merged or does the code for HCS08 work different?
spock
Posts: 39
Joined: Tue May 17, 2005 11:40 am
Location: Germany

Post by spock »

... and new

I found a new NRC17 version here
http://hifi-remote.com/forums/dload.php ... le_id=3367
(also called 00 BD).

This one has a different code section (there is only one for S3C80).

If I understand it right, this version is built into newer remotes,
<edit> SAT 1723 </edit>
but it also works with
my older ones (inserting the code into the remotes' protocols upgrade section).

This protocol seems to be "100% NRC17" (supporting 0..255 devices and the whole range of OBCs
in one upgrade).

There was no entry for that in protocols.ini, so I created one:

[NRC17 (new)]
PID=00 BD
VariantName=new
FixedData=80 00
DevParms=Device
DeviceTranslator=Translator(lsb,0,8,8,0)
DefaultCmd=00
CmdParms=OBC:8
CmdTranslator=Translator(lsb,0)
Code.S3C80=43 8B 21 8B 19 8D 84 90 20 01 08 00 FA 00 E6 00 FA 00 E6 26 FC 00 FA 04 CE 00 00 00 9C 2C 68 05 E4 04 05 69 04 E4 03 06 E6 07 7F E6 08 FF 20 11 F6 FF 3E B0 01 E6 10 01 46 29 01 F6 01 46 E6 01 03 E6 10 04 56 29 FE 8D 01 46

To distinguish between the old and new 00BD I inserted a "VariantName=new". But I'm not sure
if that is the best way to do it.


I'd appreciate some experts taking a look at that work, testing it and/or making corrections if required.


At last:
Can someone tell me the full parameter list of the TranslatorWithDevBool() command?
I couldn't find it anywhere...
Post Reply