JP1 Remotes

[microhof]

I posted my initial struggle with the Netgear MP101 in the software forum, thinking that maybe that was the appropriate place to ask any protocol questions.

I think that may have been a mistake, plus I wanted to generalize the question more. But here's that original thread...
http://www.hifi-remote.com/forums/viewtopic.php?t=2188

Anyway, basically it looks like my Netgear MP101 is using RC6-6-32 after looking at the learned keys from my URC-8910. All I could find after searching that looked useful was an upgrade for the windows media center remote that sounded like it was also hacking together the 6-6-32 protocol. I looked at the upgrade in KM but was immediately confused and overwhelmed. I did notice similarities, though, such as numerical buttons, vol+/- and power buttons had the same OBC as my remote. Trying to just use the upgrade as-is didn't work though.

Is there any amount of data I could gather that might enable one of the resident experts to give me a hint or a hand? Anyone else trying to crack this remote?

Thanks

[Mark Pierson]

[microhof]

Well, I tried this. However I'm not actually trying to use the windows media center, this is another device from netgear. So I believe part of the problem is that inherent to the design of that custom protocol must be the device code in which this bit toggling is taking place, and that is probably different between my device and the windows media center. However I don't have any clue how one might change that since I can't read the protocol and don't know the windows media center device code(s).

[johnsfine]

Sorry, I didn't realize the posted upgrade directly specifies the fixed data rather than computing it from device and subdevice.

IIUC, you have the same protocol as Media center RC6-6-32 and the same device number (128) and the same incorrect toggle bit (it toggles by adding 128 to the subdevice number), and even many of your OBC numbers are the same, BUT you have a different subdevice number

Media center has a subdevice number 3844 and you have a subdevice number 5414.

I'll see if I can make a protocols.ini entry to let RemoteMaster compute the fixed data for this protocol.

But try something simpler first in case I'm delayed in doing that.

I notice the last two bytes of fixed data 0F 04 are the hex for the subdevice number 3844. The hex for 5414 is 15 26. I haven't checked the details to see how the whole fixed data is computed but I think that changing the fixed data (cell C12 in KM's setup sheet) from E2 80 0F 04 to E2 80 15 26 ought to change the subdevice number.

Or you could edit those bytes directly in the upgrade posted above, changing it to

Upgrade Code 0 = 7C F8 (SAT/1272)
2A 12 7E FE DE EF E2 80 15 26 10 11 0E 12 13 0C
23 47 1E 1F 20 21 22 24 26 0A 1A 23 16 18 15 14
19 17 0B 4A 49 46
End

[microhof]

Well I tried that, and sure enough, it worked!
I'm going to try fixing all the functions now, as first I just uploaded the media center functions+mappings to see if those that were the same OBC as mine worked.

Thanks a ton!

So, once I finish the upgrade, I would like to create an upgrade file for it to help future generations. Should I just base it off the MC upgrade and change those two bytes plus the function codes, or should I wait until you've made a fancier way to specify the device code -- and is it better to post the upgrade in KM or RM form?