JP1 Remotes

Oppo has provided this spreadsheet...

http://www.oppodigital.com/dv980h/downl ... dv980h.xls

Can anyone tell me what the following hex code columns on that sheet mean?
Pronto TSU3000 Code
Pronto Classic Hex Code

Those columns contain the hex code required for programming these high end remote controls:Pronto Remotes

Typically, they are found in user created CCF files - of which many are available at RemoteCentral: RC File Section

CCF files can be useful for JP1 if you cannot find a JP1 upgrade which contains the codes you are searching for, and you don't have a learning remote, or are searching for a code not on your OEM remote, such as a discrete.

There is a tool provided in the File Section of this site to help decode these CCFs for JP1 use: Decode CCF

But in this case you don't appear to need any of that, because the Excel sheet gives you Protocol and Device Numbers along with command codes, in Hex and Decimal.

There are about a dozen Oppo upgrades in the file section here also.

They all seem to use NEC1 Device 73

except for one which uses NEC2, Device 73, Subdevice 182

Just a question, from reading your previous posts.

Did you get a working JP1/JP1.x interface yet ?


If not, these UEI codes are all NEC1, device 73

(although they may not be in your remote - you'd need to try them)
If any of those are present, and work to control anything on your device, they could be used to build keymoves using the data in the .xls sheet.

jimdunn wrote:Just a question, from reading your previous posts.

Did you get a working JP1/JP1.x interface yet ?


If not, these UEI codes are all NEC1, device 73

(although they may not be in your remote - you'd need to try them)

Code: Select all

Cable  0248
Sat    0358
DVD    0862
DVD    1084
DVD    1224

If any of those are present, and work to control anything on your device, they could be used to build keymoves using the data in the .xls sheet.

I have working JP1 and JP1.x interfaces. The big problem for me was a lack of parallel and serial ports. The JP1.3 remote I'm getting should work with a USB serial dongle.

Question: Why do all those codes provide matches for the specific device/protocol?

IBNobody wrote:Question: Why do all those codes provide matches for the specific device/protocol?

UEI decide which codes from their huge library to include in each remote.

There can be 1000 or so preprogrammed codes in each remote.

Even if a code wasn't intended for your device, it may use the same protocol and device number purely because another manufacturer used it in another device. (a happy "co-incidence" if you like).

So basically, whatever device(s) UEI built these upgrades for - it happened to use NEC1/73 too.

More than likely, though - if the code is for a different device, the keys will be mapped differently and/or use different EFC values (the codes the remote sends to initiate specific functions/commands). Some of them may still make your device do something, though - because the Protocol/Device is the same.

The good folks here have reverse engineered many of these built in codes, and in this spreadsheet is a pretty comprehensive collection of them (enormous thanks are due to The Robman for compiling it):Devices.xls
Tip: In Excel, use Data - Filter - Autofilter from the menu to give you pull down combo boxes at the top of each column for filtering the results to find what you want ...


If you do find a built in code like this, the chances are the keys will not be set up to control your device - but you can use keymoves to fix this - you actually have all the info you would need to do it in the .xls you linked.

But first you'd have to find a built in code which works, and then there would still be a fair bit of effort, whereas with a cable, you can just create the upgrade as you want it - MUCH simpler, quicker and convenient