JP1 Remotes

LMolland · Joined: 17 Apr 2005 Posts: 21 Location: Midlands, UK

Hi, I have learned all the buttons from my new Toshiba TV (42VL863) and created a device upgrade which works fine in my URC-8060 1st Gen UK Kameleon.

When I then modify the upgrade to use it with my URC-8206 2nd Gen UK Kameleon, it does not work correctly. Some of the buttons operate the wrong functions and some do nothing.

The upgrade for the 8060 needed a protocol upgrade, but the upgrade for the 8206 did not... I assume the required protocol is already present on the 8206.

The remote signatures seem correct, KAMEKAM0 for the 8060 and 10211021 for the 8206.

Can anyone suggest anything I might have done wrong? I can provide the IR.exe files and of course the KM files if they help. (I tried the 8206 upgrade from both Keymap Master and in Remote Master without success.)

Thanks, Lester

3FG · Expert Joined: 19 May 2009 Posts: 3371

Yes,
Please upload both the KM and IR files.

LMolland · Joined: 17 Apr 2005 Posts: 21 Location: Midlands, UK

Hi 3FG,
I've Zipped the two IR files and the two KM files.

I've also added another URC-8206 IR file just to show a few "learned" items; the item on button "C" is a different sub-device but I think my choice of protocol for the original URC-8060 upgrade was right because it works OK? (I found it interesting that this button is the 3D/2D button for my 3D television and it has the Hex command 3D.)

I hope this is the link to the file:-
http://www.hifi-remote.com/forums/dload.php?action=file&file_id=9854

It's named... URC-8060 vs URC-8206.zip

Thanks very much
Lester

3FG · Expert Joined: 19 May 2009 Posts: 3371

Lester,
By loading the 8060 and 8206 IR files in to RMIR, it is easy to see that all of the OBCs are in the 8206 are shifted by 2 buttons from where they should be.

For example, button "1" should have OBC=1, but it actually has OBC=3. Button "8" should have OBC=8, but it actually has OBC=26, which is Vol+. Vol+ is 2 buttons lower in the list of buttons.

I suspect that KM9.21 doesn't handle the 8206 correctly. For example, it thinks that the 8206 has NEC 2DEV Combo built in, and doesn't have NEC 4DEV Combo. The opposite is actually true. So I speculate that the button scan codes may also be incorrect.

I think the simplest fix is to load the 8060 KM file into RM. That should tell you the OBC for each function. Open a second instance of RM, set the remote type to 8206, setup the NEC 4DEV Combo, then copy and paste the OBCs onto the function tab. You'll need to make the OBC line up with the correct function names. Then you can copy the upgrade from the Output tab to IR. I would have just done this for you, but I don't know how you want to assign the various functions to the buttons on the 8206.

A few of the long-time users here will probably strongly disagree, but in my opinion, most of us should be using RMIR to work with our remotes. It's a heck of a lot easier.

vickyg2003 · Posted: Sat Aug 20, 2011 7:24 pm Post subject:

LMolland · Joined: 17 Apr 2005 Posts: 21 Location: Midlands, UK

Thanks for your help 3FG!

I tried RMIR and could see exactly what you meant regarding the 2 button offset. I had the original list of OBC's in KM, so I just decided to just enter all the correct OBC details directly in the RMIR editor and then uploaded it to the URC-8206 remote.

It worked a treat! I think I'll play around with RMIR some more too, because I suspect it may prove to be a more straightforward "All-in-one" tool. I'll see how I get on.

I'm glad you and Vickyg2003 were able to find the bug... I was baffled but couldn't see what was wrong.

I've now got several models of the Kameleons (+ parallel & USB JP* cables) because I wanted to "future-proof" myself regarding JP*; I find it so useful.

It's great to know (and much appreciated) that you experts will spare the time to help relative beginners so thanks again.

Lester (PS... I'll upload the Device Upgrades.)

vickyg2003 · Posted: Sat Aug 20, 2011 10:02 pm Post subject:

3FG · Expert Joined: 19 May 2009 Posts: 3371

Vicky,
When I said RMIR is easier to use, I wan't referring to bugs. I'm pretty sure that RMIR has more bugs than KM. Anyway, the issue Lester saw with buttons sending the wrong signals isn't caused by the 2DEV/4DEV bug.

But the situation that Lester ran into (OBCs on the wrong buttons) was trivial to see when I compared his IR files in RMIR. I had already spent some time comparing the two files in KM and IR to try to find the problem, and it wasn't apparent. It also isn't apparent if the KM files are loaded into RM, although the executor confusion can be noticed on the output tab, since RM knows that a 8206 doesn't have a NEC 2DEV built in.

Basically, the integrated nature of RMIR made it easy to see the discrepency.

vickyg2003 · Posted: Sun Aug 21, 2011 12:03 am Post subject:

LMolland · Joined: 17 Apr 2005 Posts: 21 Location: Midlands, UK

I suppose the key is that KM offers the NEC 2DEV for the URC-8206 without creating a protocol upgrade to go with it?

For what it's worth (and probably very obvious to those who know what they're doing), I went back to KM out of interest and changed the protocol name from NEC 2DEV Combo to NEC 4DEV Combo.

Copying the resultant Device and Protocol upgrades into IR and uploading to remote gives a working upgrade.

Very Happy

vickyg2003 · Posted: Sun Aug 21, 2011 8:27 am Post subject:

Yes the 4dev Combo would have worked, even if there was no 011A protocol in the E2 area because the protocol already is built into the remote, KM just thinks the other version is built in.

3FG · Expert Joined: 19 May 2009 Posts: 3371

Vicky,
Thanks for the explanation. It's clear to me now.