JP1 Remotes

Then some sort of tether would be the best solution.

SysTech_Larry wrote:

phb1342 wrote:Moderator note: TCL Roku master file is here:
http://www.hifi-remote.com/forums/dload ... e_id=26531
...
phil

What application opens an .rmdu file...?

I just looked at that file. The numbers it gives for hex are the mirror image of what my IR tester is getting from my remote (unless it is LSB first).

For instance, it says
the hex for Right Arrow = B4.
Binary = 1011 0100.
The mirror image = 0010 1101.
Hex = 2D.
That is what my tester reads when I press the Right Arrow key.

The OBCs from my remote remain <128. The mirror-image hex does not.

It is missing HDMI4, Home (duplicate) and three other keys.

Try OBC 36 for HDMI4 and OBC 3 for Home. You'll have to find the others by trial and error. Looks like the following OBCs are good candidates to try:
1-2,5-7,14,17-20,29,31,38-40,48-50,55-63,81,83,92,94,100,103,113,115,117-118,121-126

mdavej wrote:Try OBC 36 for HDMI4 and OBC 3 for Home.* You'll have to find the others by trial and error. Looks like the following OBCs are good candidates to try:
1-2,5-7,14,17-20,29,31,38-40,48-50,55-63,81,83,92,94,100,103,113,115,117-118,121-126

Thank you. I already have HDMI4 & HOME2.

I have three that are undefined (using the questionable hex format in the above file):

• 80 (01 at remote)
• 40 (02)
• 5C (3A)

The TV acknowledges them, but they do nothing obvious. I was hoping that file would give those functions a name.

*In the OP's file, HOME is Function #22 with an incorrect OBC = 192 [Hex = C0].

You are making a false equivalence between the hex column and OBC. The hex column is not the hex value of the OBC, it's the reverse, as you've discovered.

The OP's OBCs are correct. The hex is not limited to 128, the OBCs are. Hex C0 is equivalent to decimal OBC 3. There are no OBCs > 128 in the master file, so all are valid.

In your Right Arrow example, the OBC in the file is 45 decimal which is indeed 2D. So you need to equate your codes to the hex value of the OBC, NOT the hex shown in the hex column in Remote Master which is the OBC in reverse. That means your missing commands would have the following OBCs, none of which are in the current file:
So if you figure out what they do, we'll add to the file according to the OBCs above.

mdavej wrote:You are making a false equivalence between the hex column and OBC. The hex column is not the hex value of the OBC, it's the reverse, as you've discovered.

The OP's OBCs are correct. The hex is not limited to 128, the OBCs are. Hex C0 is equivalent to decimal OBC 3. There are no OBCs > 128 in the master file, so all are valid.

In your Right Arrow example, the OBC in the file is 45 decimal which is indeed 2D. So you need to equate your codes to the hex value of the OBC, NOT the hex shown in the hex column in Remote Master which is the OBC in reverse. That means your missing commands would have the following OBCs, none of which are in the current file:

Code: Select all

Larry 
Hex          OBC
01             01
02             02
3A             58

So if you figure out what they do, we'll add to the file according to the OBCs above.

Thanks for the clarification.
The hex for OBC numbers 1, 2 & 58 should be 80, 40 & 5C, then.
That is counterintuitive but I accept that at face value.

(The hex values that I reported are what my IR tester shows for OEM & URC remotes in my possession. They happen to be the hex values of stated OBCs.)

SysTech_Larry wrote:Thanks for the clarification.
The hex for OBC numbers 1, 2 & 58 should be 80, 40 & 5C, then.
That is counterintuitive but I accept that at face value.

(The hex values that I reported are what my IR tester shows for OEM & URC remotes in my possession. They happen to be the hex values of stated OBCs.)

Larry, please keep in mind that the JP1 hex codes are not designed to be intuitive, they are just the hex code that is required to make the executors work. If you want things to be intuitive, stick to OBCs, that's why we display them.

Normal JP1 users have no need to even deal with hex codes.

The Robman wrote: Normal JP1 users have no need to even deal with hex codes.

Understood, but I normally leave my OBCs in hex format (rather than convert it to dec each time) because that is the way my IR tester presents them. Should I call that HOBC so they will not be misconstrued as the other kind of hex?

I would prefer OBC (hex) or OBC in hex. HOBC would only baffle us.

But thanks for sharing your codes. As long as we eventually understand each other, its all good.

I know what OBC is mathematically speaking, but may I ask what it stands for?

mdavej wrote:...So if you figure out what they do, we'll add to the file according to the OBCs above.

I have two good candidates for 01 & 02,...
https://developer.roku.com/docs/referen ... .md#syntax

• Play (only) &
• Pause

But since they are exceptional functions, I cannot confirm them, nor which is which.

MTS is a good guess for 3A.

SysTech_Larry wrote:I know what OBC is mathematically speaking, but may I ask what it stands for?

Original Button Code

mdavej wrote:...So if you figure out what they do, we'll add to the file according to the OBCs above.

You should add them anyway, as

• Unknown function(01),
• Unknown function(02) &
• Unknown function(3A)

so more people can try them on a whim and, possibly, see them in action.

I notice that Roku does not have an Advance button. I know you can't advance into the future, and I realize there is instant replay, fast forward and fast reverse. My question is if I reverse a long way back is there a way to slowly advance forward to zero in on a specific frame instead of going back and forth with forward/reverse? Thanks