JP1 Remotes

Wanting to move the Power function on my receiver (code 1758) onto all 6 of the devices. I placed 1758 into dev7 on my 6131 using IR, and attempted to move the Power function (EFC 71, using the correct 00 xx hex conversion yada yada) from dev7 to the other 6. This works correctly for vol+, vol- but not for the Power!

Troubleshooting reveals (via using my learning remote to read how the Power key is being produced) that the Device number is being corrupted from the correct number to zero. Putting code 1758 on the remote does work.

IR File: http://groups.yahoo.com/group/jp1/files ... enttst.txt

Any other way? I'm in trouble with manual keymoves to circumvent this issue because I cannot access dev7 to do the move. Or can I??

Mitch

Unsure if this is barking up the wrong tree:

http://www.remotecentral.com/cgi-bin/mb ... d.cgi?4020

Apparently the remote mode for the receiver/remote must be set to AV1 for things to work right with OFA remotes, but wouldn't this keep my 6131 from working when entering the 1758 code directly on the remote and sending commands to my Sony 995 receiver??

Mitch

Do you have the 1758 code assigned to a device button for normal use? If so, do the keymove on the remote itself (as I keep suggesting). Not only will this method actually work but it will use less memory.

I do not have it assigned to a button because unfortunately, I have hogged those buttons with 4 TiVos, a TV, and a DVD!

Would a keymove via KeyMaster work? I am not using an upgrade definition here, so I would not at this point know how to go about it there.

Would there be a way to enter the EFC manually on the remote and assign it directly to the power buttons?

If there is no solution here, the power function is not critical. The volume keymove from the dev7 phantom device for some reason works properly, and that is far more important.

Have I come to a technical impasse getting the Keymove to work in IR here, what with the Device code being corrupted? Reminds me of the previous thread where you suggested changing the 1162 combo VCR/TV code to 0162 for the keymove in order to bypass a technical impasse there.

mvgossman wrote:I do not have it assigned to a button because unfortunately, I have hogged those buttons with 4 TiVos, a TV, and a DVD!

Temporarily assign it to the VCR device, do the keymove, then put the VCR device back to your original setup code.

When you are done, download to IR and examine the keymove; note the hex value for future reference.

Eureka, but why?

I assigned 1758 to the AUD key, did a keymove to VCR, downloaded and examined the keymove. I got $26 as a Hex Cmd. I went back to my own IR definition, changed the keymove to 026 EFC, and it works.

Why though? I though that to do Keymoves within IR, you had to use the "00 xx" convention where the EFC is converted to hex and entered as two bytes.

Mitch

Do a search on my recent posts because I just explained this to someone.

Rob: Is this it?

https://www.hifi-remote.com/forums/viewt ... hlight=efc

So putting it simplistically and perhaps blatantly inaccurately, there are two ways to do a keymove. One, using the EFC quirkily converted to a two byte hex converted code which allow IR to properly put the keymove into the remote. Two, by using the key number directly in a one byte move which requires reading the keymove code from the remote after doing so with a manual remote keymove.

I'm hampered by a lack of a deeper understanding of the overall way these work, terminology (EFC, OBC, key nuymber, advanced code, two-byte code, etc.) - I'm working on it.

Keymoves can be expressed in EFC or HEX. If is a multi byte command then it must be in HEX.

Notice that towards the bottom of the dialog ther is a choice.

mvgossman wrote:Rob: Is this it?

https://www.hifi-remote.com/forums/viewt ... hlight=efc

That's an older one, I was thinking of this one...
https://www.hifi-remote.com/forums/viewt ... ght=#p21624