Issue with learned codes

e34m5 · Post by **e34m5** » Mon Jan 05, 2004 7:59 am

Using 8810w and JP1 here is my situation.

Leraned the code for selecting discrete inputs on my receiver. Using the EFC's that IR reported I converted these into keymoves and assigned them to the number buttons under the RCVR device.

Oddly then these do not work when pressing the buttons. Also when trying the EFC's directly (using the set key) they do not work either).

I've converted other learned codes with success...bit this one has me baffled...

johnsfine · Post by **johnsfine** » Mon Jan 05, 2004 8:22 am

Are you basing those KeyMoves on a built in setup code (whch one)? or on an upgrade (what protocol, device, subdevice, etc.)?

Are the device and subdevice numbers in the decodes of the signals that didn't work (as KeyMoves) the same as those in the decodes of the ones that did work?

e34m5 · Post by **e34m5** » Mon Jan 05, 2004 8:32 am

I am basing the keymoves on the built in setup code (RCVR0013). So I am assuming the device, subdevice, etc would follow suit.

BTW, this is a Pioneer receiver...I seem to recall there is something strange in their EFC behavior????

Post by **The Robman** » Mon Jan 05, 2004 11:07 am

e34m5 wrote:I am basing the keymoves on the built in setup code (RCVR0013). So I am assuming the device, subdevice, etc would follow suit.

In order for us to determine if your assumption is correct, we would need to know what protocol, device code (and maybe sub-device code) IR reported this signal as using.

e34m5 · Post by **e34m5** » Mon Jan 05, 2004 11:47 am

From the learned tab -

Protocol: NEC2(1 Device)
Device: 165
Sub Device: Blank
OBC: 133
Hex CMD : 5E
EFC: 192

and

Protocol: NEC2(1 Device)
Device: 165
Sub Device: Blank
OBC: 12
Hex CMD : CF
EFC: 052

usblipitor · Post by **usblipitor** » Mon Jan 05, 2004 11:56 am

from devices4.xls:
052 is the digit "8"
192 isn't listed

can you post your files? maybe ZIP them together and post the ZIP file in the diagnostics folder?

Maybe one IR file with the learned codes in it, another IR file without the learned codes but with the keymoves in it?

e34m5 · Post by **e34m5** » Mon Jan 05, 2004 12:02 pm

ok..look for PaulR2.txt...tx

Post by **The Robman** » Mon Jan 05, 2004 12:15 pm

The fact that IR is displaying "NEC2(1 Device)" tells me that you are either using an out of date version of IR.exe or you don't have the current DecodeIR stored.

This protocol is really "Pioneer", with device code 165.

But even so, the keymoves should have worked.

jon_armstrong · Post by **jon_armstrong** » Mon Jan 05, 2004 12:16 pm

Those seem like good commands:

EFC 052 OBC 012 Tv Input
EFC 192 OBC 133 Dvd/Ld Input

Steve, don't forget the numerals for receivers on OFA remotes are ususally the discrete input commands.

Paul/e34m5,

The simplest troubleshooting is to save your existing configuration in IR. Then do a 981 reset. Then try these keymoves again. They really SHOULD work.

BTW, is that an Zenith HD receiver that you have? If so what model? There is a device upgrade in the files for one including discrete power comamnds but I think it is only the SAT-520 and newer (although the file is titled as the 1080).

e34m5 · Post by **e34m5** » Mon Jan 05, 2004 12:18 pm

Yep it's a SAT520, the Zenith 1080 update works almost everything..I had to learn a few things. The discrete codes did not work for me.

Now the funny thing on those other commands is that when I try Set+052 nothing happens either...

So a generic question: when testing a code directly from the remote I assume that the device currently selected has no effect on this..or does it.

usblipitor · Post by **usblipitor** » Mon Jan 05, 2004 12:23 pm

Do you have the current versions of all the software? Maybe that would be a good start if you have older versions.

johnsfine · Post by **johnsfine** » Mon Jan 05, 2004 12:24 pm

e34m5 wrote: Now the funny thing on those other commands is that when I try Set+052 nothing happens either...

So a generic question: when testing a code directly from the remote I assume that the device currently selected has no effect on this..or does it.

It sure does have an effect. The current device mode selects the setup code from which the remote gets the protocol and the fixed data. The 052 is just the EFC number.

usblipitor · Post by **usblipitor** » Mon Jan 05, 2004 12:25 pm

e34m5 wrote:when testing a code directly from the remote I assume that the device currently selected has no effect on this..or does it.

IT has every effect on it. The currently selected device tells the remote which protocol to use when sending the EFC you are keying in.

e34m5 · Post by **e34m5** » Mon Jan 05, 2004 12:27 pm

ok, ok...I tried it that way as well and still no joy...the learned buttons work...but invoking the EFC does not...

BTW, I tried it with two different remotes and no results..(7800 and 8810)

I'm downloading new IR now...

johnsfine · Post by **johnsfine** » Mon Jan 05, 2004 12:29 pm

e34m5 wrote:ok..look for PaulR2.txt...tx

That answered a few questions.:

You said built-in setup code RCVR/0013 and you said 8810w, but the 8810w doesn't have that setup code. You're actually using a URC7800.

You have RCVR/0013 properly defined as the setup code for the RCVR key.

You have EFC 192 properly defined as a KeyMove on the '1' key.

You have a clean learn of EFC 192 on the 1L key and a clean learn of 052 on the 2L key.

None of this explains what is going wrong. That 1 key and the 1L key should both do exactly what the original remote's key (whichever one you learned) did.