JP1 Remotes

When I first ran KM I didn't have VBA insdtalled, so I installed it. Then when I opened the KM excel sheet it still didn't work - it turned out that excel had saved it without the macos enabled, and they wouldn't fire up.

I just downloaded it again ad all was well.

That said - I'm with greg ...

OK, I don't have anything more to report except extended befuddlement.

I have 4 EFC's that are different between Silrons original file, and my 8910 learned codes.

Box Office: Silron = 169 Me = 100
Interactive/Active: Silron = 101 Me = 165
Planner: Silron = NA (maybe 193) Me = 109
AV: Silron = 238 ...

<chuckle>

So am I lucky or is it just that you guys are smarter than me?

I am finding a quirk or two now that I look into it, but it could well be my imagination...

Ok, first things first - R6-6-20n is the correct protocol, tyvm. It all works like a charm.

Second - I have learned 90% of the codes from the OEM remote (It happens to be a URC-1633B00-00 btw) and they ALL decode as Nokia32 See Diagnosis File

The only other thing from my POV is that I have now ...

thanks mark - I was working on it when you did that.

The fixed data of E0 00 corresponds to default values on all three protocol parameters: M=6, Device=0, Subdevice=0.
John, what are the rules for decoding the 2-byte and 6-byte versions of the fixed data for this protocol?

Also, where did the 6-byte version come from, is it home made or did it ...

I just assumed this was a not_yet_supported protocol in the .ini file. But it sure looks like Rob is right that it's RC6-M-20n, which would be quite easy to set up in RM (and probably matches and .rmdu file already posted).

So what is the Nokia32 decode about?

I dunno - when I asked you about ...

PID 0020 is the RC6-M-20n protocol, which is already defined in protocols.ini. Fixed data "E0 00" matches setup code SAT/0847.

ahhh, I see. Decodeir picks it up as nokia32 then...

Just FYI, according to my files, this protocol only gets pre-loaded into certain European remotes, it's not present ...

you guys have gone way over my head.

1. Is there a known PID used for this protocol in any remotes?
2. How many bytes of fixed data is there?
3. What are the device parameters, and what are the rules for storing them in the fixed data?
4. How many bytes is the hex command?
5. What are the ...

Thanks, Greg - looks about right...

So do you just paste the KM generated protocol code to the notes in KM?

What do you need to know about Nokia32 to put it in protocol.ini?

Is there a guide on setting up new protocols for remote master? I have a KM Foxtel/sky upgrade that works (which is why I'm not posting to code search) that I would prefer to use in RM. Because it uses manual settings it fails to load in RM, and I can't add the protocol manually, probably because I ...

well, I'm a beginner and I worked it out.

for anyone who comes after me:

Here is my complete JVC TH-A5R device upgrade

Ok. So on the whole - if someone learns 10 NEC signals that are predisposed to badness (is that the OEM remote, Learning remote or tecnique at fault?) will they get all NECx2 or a mixture of both.

If they get both then Mark might make a note to suggest trying NEC or NECx2. Where I'm going is that ...

hokay.

It's even weirder now - I'll detail in the email.

hehe...

I guessed it was NECX2 on the basis that NEC2 didn't work, and that the device4.xls said the 67:83 code was NECX2. So I flipped it over and it all worked.

I have not disabled decodeir.dll, and it is in the c:\windows\system32 folder.