JP1 Remotes

Graham,

Thanks very much. I copied the RDF into the relevant folder and downloaded the remote. As you explained, I did not get the type mismatch error.

Rob,

Thank you as well. To confirm, the type of device upgrade I create (e.g., TV, VCR) and the designation on the remote to which I assign it (e ...

OK. Thanks for posting the link. Apologies for not doing that before.

I created a new upgrade for the TV and uploaded it to Cable and used the built in code for Samsung TV for TV. This looks like it may have solved the problem, but I still need to test it. Thanks again!

Thanks very much. I uploaded the remote to the diagnosis area. Please let me know if you also would like me to reset all values and upload a new copy. (If so, could you remind me what code to use to reset the remote?)

I think that the remote is a URC-1058 based on the blink signature and the remote ...

Thanks very much for adding support for JP1.1 remotes and explaining how to interface with them! This is really great. I was able to communicate with what I believe is a Comcast URC-1058 and to load an update file to it using the board linked to earlier in this thread and the JP11USB interface ...

Thanks for the quick reply! I will experiment with key moves to see what I can do.

I have a few questions about about the 1056B03 extender and JP1 generally.

1. Is the 1.0 version the latest version of this extender?

2. Do I need to copy the RDF from the extender into the RDF directory or can I just use the version that comes with the latest version of RMIR?

3. I would like to ...

You might be able to use a Microsoft MCE remote, which I believe already has an UEI code, by telling the box to look for those commands. Look at http://forum.kodi.tv/showthread.php?tid=210987&pid=2291663#pid2291663 steps 1 and 1.5. The MCE remote probably has more buttons than what you're working ...

Sounds like this are all the functions. For buttons that don't work, it doesn't reallly matter what they're called unless you can find a way to map them to something new in an application. FWIW, you might look on your box for a Vendor_0001_Product_0001.kl file. It's possible that the missing button ...

OK. I missed that you had already found the following new keys:

Page Up: 48
Page Down: 51
Plus Sign: 53
Minus Sign:56
Unknown*:3
Unknown*:17
Unknown*:54

Does OBC 234 do anything?

Also, can you remap F9, F10, and F11 (OBCs 56, 53, and 54) to other functions in Kodi using the keymap editor? See ...

Does the remote.conf file that you posted on the first page come from your device? Or is it just a guess from some other type of Xiaomo box or someone else who has rooted the same box?

That file lists factory_code = 0x00860001. The first four diigits of this code are the subdevice and device codes ...

This thread is a little hard to follow, but my post in the following thread might be helpful: http://hifi-remote.com/forums/viewtopic.php?t=15536

Basically, I was able to create an upgrade for an android TV box based on the remote.conf file from the box that specified device, subdevice, and OBC ...

Thanks!

I created a bug report in the RemoteMaster sourceforge project. Thanks.

The problem turned out to be that there was an extra return in the RDF file that apparently kept Remotemaster from parsing some of the button definitions.

It might help to clarify which A&T remotes work. The link to the ebay auction above ( http://www.ebay.com/itm/282013112313 ) is (at least now) for an S10-S3 (manual at https://www.att.com/support_media/images/pdf/uverse/S10-S3+User+Manual+of+CY-RC105C-AT+HD.pdf ), which does not have a four pin ...