Suggestion for a new "00 A5" protocols.ini entry

Discussion forum for JP1 software tools currently in use, or being developed, such as IR, KM, RemoteMaster, and other misc apps/tools.

Moderator: Moderators

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

Suggestion for a new "00 A5" protocols.ini entry

Post by spock »

My original RCs: Grundig TP 800, Grundig RP75LCD
Programmable RC: OFA URC-7552

Problem: DecodeIR says "Blaupunkt" but
RemoteMaster's "Blaupunkt" protocol "00 A5" does not work

I realized that
1. Device/EFC information taken from DecodeIR (IR 6.0) does not
match Device/EFC implementation of RemoteMaster's
"Blaupunkt" protocol "00 A5"
2.
Signals sent by my original RCs are almost 100% compatible
to signal shape defined in the Motorola Remote Control
Transmitter IC MC44107 technical data.
3.
Several original setups of my OFA RC (TV-0195, TV-0554,
VCR-0195, SAT-0173) send MC44107 compatible signals.
4.
Signals generated by "00 A5" protocol are almost identical to
the signals described in MC44107 technical data

Conclusion:
Most RCs detected as "Blaupunkt" do in fact send
MC44107 compatible signals...

... and I need a corresponding RemoteMaster protocol entry for it...
spock
Posts: 39
Joined: Tue May 17, 2005 11:40 am
Location: Germany

Suggestion for a new "00 A5" protocols.ini entry

Post by spock »

MC44107 specifies
{31.25,512}<-1,1|1,-1>(1,-5,511:9,1,-38,(1,-5,1,-1,F:6,D:3,-230)+,1,-5,511:9,1,-230)

I discovered that my OFA RC can - with "built-in" "00 A5" - send two types
of signals using that protocol
"Type 0":
{30.7k,512}<-1,1|1,-1>(486u,-5,511:9,1,-40,(1,-5,F:7,D:3,-240)+,486u,-5,511:9,1,-240)
This is almost MC44107 standard (only minor timing differences)
"Type 1":
{30.7k,512}<-1,1|1,-1>(486u,-5,511:9,1,-240,(1,-5,F:7,D:3,-240)+,486u,-5,511:9,1,-240)
(same data but "SST pause" is "non standard")

(My Grundig TP 800 sends
{30.5k,528}<-1,1|1,-1>(1,-5,511:9,1,-37,(1,-5,1,-1,F:6,D:3,-219)+,1,-5,511:9,1,-219)
that corresponds to "Type 0"

whereas my RP75 sends
{30.2k,528}<-1,1|1,-1>(1,-5,511:9,1,-210,(1,-5,1,-1,F:6,D:3,-210)+,1,-5,511:9,1,-247)
and that in fact is "Type 1" of "00 A5".)


So the only real difference is (...F:7...) to (...1,-1,F:6...)
But if in F:7 you set F:1:6 = 1 you can not distinguish between "Type 0" and MC44107 at all.


Protocol "00 A5" has one byte of "fixed data".
We take the D:3 in lsb order as MC44107 "pages" (well, in fact the protocol code does).

GHIxxxxT (fixed data byte)
--------
00000001 = Page 0
10000001 = Page 1
01000001 = Page 2
11000001 = Page 3
00100001 = Page 4
10100001 = Page 5
01100001 = Page 6
11100001 = Page 7

The T bit can select the timing variation (0 or 1).

The 4 remaining bits have no effect (at least I haven't noticed one).
spock
Posts: 39
Joined: Tue May 17, 2005 11:40 am
Location: Germany

Suggestion for a new "00 A5" protocols.ini entry

Post by spock »

So here is my suggestion for a new "00 A5" protocols.ini entry:


[Grundig]
OldNames=Blaupunkt
PID=00 A5
DevParms=Device (Page):0|1|2|3|4|5|6|7=0,Timing:bool=0
DeviceTranslator=Translator(0,3,0,lsb) Translator(1,1,7)
FixedData=00
CmdParms=OBC:6=0
CmdTranslator=Translator(0,6,1,lsb)
DefaultCmd=80
Notes=9 bit PCM signal (see technical data of Motorola MC44107 IR Remote Control Transmitter IC for details) \n\n\
"Timing" unchecked: {31k,512}<-1,1|1,-1>(1,-5,511:9,1,-38,(1,-5,1,-1,F:6,D:3,-230)+,1,-5,511:9,1,-230) \n\
"Timing" checked : {31k,512}<-1,1|1,-1>(1,-5,511:9,1,-230,(1,-5,1,-1,F:6,D:3,-230)+,1,-5,511:9,1,-230)
#(Insert code section from old "Blaupunkt" protocol here)


Choosing a new name for this "00 A5" implementation makes it possible to keep the
original "Blaupunkt" section (in case there really is a signal pattern matching
the "old" protocol).

I already was able to perfectly program my Grundig RCs using this modified
"00 A5" protocols.ini entry whereas I wasn't able to do so with original "Blaupunkt" protocol.

However, a little update to DecodeIR would be necessary, in order to let IR
display the correct Device/EFC values.
But current "Blaupunkt" decoding in DecodeIR is not compatible to RemoteMaster's
"old" "00 A5" protocol anyway.



Could some experts please examine my protocol update to tell me if
it contains any errors or if I missed an important part...

Thanks in advance.
Post Reply