Page 1 of 1
Trouble decoding IR signal from Pioneer Remote for Plasma TV
Posted: Wed Sep 07, 2005 12:20 am
by mvgossman
I need to keymove the DTV button of my Pioneer Plasma remote on the 6131 PVR. None of the JP1 files have an upgrade with this button. Learning with the 8810 yields, on anaylisis with IR:
# Protocol Device Subdevice OBC Hex CMD EFC
1 Pioneer 170 ----- 211 34 115
2 Pioneer 175 ----- 126 81 006
I see in Rob's notes that this indicates difficulty decoding the IR signal and not some sort of dual output, and that to properly decode this is difficult, best handled by searching the Keymaster archives, but unfortunately, nothing out there.
Anyone have a solution?
Mitch
P. S. Here is the raw data if it helps:
Freq 40000
Sent Repeatedly:
+8524 -4290 +524 -548 +524 -1608 +524 -548 +524 -1608 +524 -548 +524 -1608 +524 -548 +524 -1608 +524 -1608 +524 -548 +524 -1608 +524 -548 +524 -1608 +524 -548 +524 -1608 +524 -548 +524 -1608 +524 -1608 +524 -548 +524 -548 +524 -1608 +524 -548 +524 -1608 +524 -1608 +524 -548 +524 -548 +524 -1608 +524 -1608 +524 -548 +524 -1608 +524 -548 +524 -548 +524 -25484 +8524 -4290 +524 -1608 +524 -1608 +524 -1608 +524 -1608 +524 -548 +524 -1608 +524 -548 +524 -1608 +524 -548 +524 -548 +524 -548 +524 -548 +524 -1608 +524 -548 +524 -1608 +524 -548 +524 -548 +524 -1608 +524 -1608 +524 -1608 +524 -1608 +524 -1608 +524 -1608 +524 -548 +524 -1608 +524 -548 +524 -548 +524 -548 +524 -548 +524 -548 +524 -548 +524 -1608 +524 -25484
Re: Trouble decoding IR signal from Pioneer Remote for Plasm
Posted: Wed Sep 07, 2005 1:41 am
by Capn Trips
mvgossman wrote:I see in Rob's notes that this indicates difficulty decoding the IR signal and not some sort of dual output,
Actually, this appears to be a perfectly fine and normal Pioneer decode, since Pioneer chooses to use one of the more complex coding systems in which two-part signals are not at all uncommon. Not knowing whether the rest of your device upgrade uses possibly a third device code, you may need either the Pioneer Mix (2-byte) protocol or the Pioneer 3DEV (2-byte) protocol, but you can certainly reproduce this signal in a device upgrade using KM or RM. From the KM protocols read-me:
Pioneer MIX (2-byte):
---------------------
Pioneer has started creating new devices that use a similar mix of
codes as the Pioneer DVD protocols, but they don't follow the same
rules, so these need to be entered manually using the Pioneer MIX
protocol. If using the DVD/DVD2 version doesn't work, try this one
instead.
On the [Setup] sheet, enter the device details:
device1 = the device code found in both the single-style signals
and the first half of the double-style signals.
device2 = the device code found in the second half of the double-
style signals.
cmd1 = the OBC command code used in the first half of most of the
double-style signals.
cmd2 = the OBC command code used in the rest of the double-style
signals (if present)
Then on the [Functions] sheet, you indicate which style of signal
to use for each function. Do this by entering one of the following
values in the byte2 column:
0 = single-style signal (using device code 1)
1 = double-style signal (using dev1/cmd1 in the first half)
3 = double-style signal (using dev1/cmd2 in the first half)
Pioneer 3DEV (2-byte):
----------------------
If the functions for your device use one of up to three different
device codes, and some of the functions even send a two-part
signal as described above, then you need to use the "Pioneer 3DEV"
protocol.
Enter the three device codes, and then, on the Functions sheet,
enter the command codes in the regular OBC/EFC column.
In the byte2 column enter a "1", "2", or "3" to indicate which
device code to use. If this particular function uses a two-part
signal, put a space after the device code number and then enter
the EFC or OBC.
For example, if device code 1 is 130, and the ENTER button sends a
two-part signal where the first part is device 130, command 123,
and the second part is device 130, command 133, you would enter
"123" in the OBC/EFC column, and then "1 133" in the byte2 column.
NOTE: While this protocol supports both OBC's and EFC's, this
version is LSB, where most of the other Pioneer protocols are LSB-
COMP, so the EFC's will be different. Therefore, it is STONGLY
recommended that you use OBC's when setting up the Pioneer 3DEV
protocol.
Posted: Wed Sep 07, 2005 11:43 am
by mvgossman
Thanks, worked like a charm, but when using Pioneer Mix, I'm unable to do a keymove within KM ("Key Moves: NOT ALLOWED" and buttons in red italics. Is this an insurmountable barrier to doing a keymove of this dual code to other buttons in KM? How about IR keymove? I tried doing a 994 OFA 6131 remote manual transfer and it's rejected, too. I can limp along if necessary with the DTV Plasma TV button mapped to a functional Keymaster button if I have to, but would rather not.
Mitch
Posted: Wed Sep 07, 2005 12:41 pm
by johnsfine
The normal method of KeyMove for the 6131 is key to key rather than hex command to key.
I don't think it can do keymoves of two byte hex commands. If it can then our software doesn't know the right encoding.
The usual workaround is to make a second device upgrade with the desired extra functions, then do key to key KeyMoves.
Posted: Wed Sep 07, 2005 1:12 pm
by The Robman
John is correct, the URC-6131 can't handle 2-byte keymoves, so you would need to create key-to-key keymoves from a 2nd upgrade.
You can program the key-to-key keymoves using IR.exe or on the remote itself.
Posted: Wed Sep 07, 2005 1:58 pm
by Mark Pierson
The Robman wrote:the URC-6131 can't handle 2-byte keymoves
It can do 2-byte key moves with the extender.
Posted: Wed Sep 07, 2005 2:40 pm
by The Robman
Mark Pierson wrote:It can do 2-byte key moves with the extender.
True, I am making the assumption that he isn't using the extender.
Posted: Wed Sep 07, 2005 4:13 pm
by mvgossman
True, I do not use the Extender but perhaps that would simplify matters?
For now, I am confused about key-to-key and a second upgrade. Do you mean to put in another device attached to, say, dev7, identical to this TV upgrade I am working on, and do a conventional keymove from dev7/DTV function to the button of my choice on the TV device via IR or manual 994 keymove? If so, what do I enter in IR for the EFC/Hex Cmd since in this case, we're talking about two EFCs, namely the Device1 170 with Cmd1=211 and the second half of the double-style signal Device 175, Cmd2=OBC 126 in this case?
Posted: Wed Sep 07, 2005 6:24 pm
by The Robman
Here's the scoop with the 2nd upgrade. In the un-extended state, the URC-6131 doesn't support 2-byte keymoves, but it does support key-to-key moves (ie, when you copy the MENU button to the GUIDE button, for example). So, what we're suggesting is that you create a 2nd upgrade that contains all of the buttons that are missing from your first upgrade. Then, you would program keymoves from this upgrade to the buttons of your choice.
The easiest way to program the keymoves is using IR, in which case you wouldn't need to assign the 2nd upgrade to a device button at any stage of the process. If you want to program the keymoves using the remote itself, you would first assign the 2nd upgrade to the TV button, then you could copy the functions from the buttons that they are assigned to, to the buttons that you want to use for them.
For example, let's say that the WIDE button is one of the buttons in question. In the 2nd upgrade you might have assigned this function to the "number 1" button but you would ultimately like it to be on the PVR-MENU button, so you would use the 994 command to copy the function from the "1" button to the "PVR-MENU" button. Etc, etc.
When you have finished copying all of these buttons, you would then re-assign the 1st upgrade back to the TV button.
Posted: Wed Sep 07, 2005 6:54 pm
by mvgossman
I think I already did this - I added the DTV button to the KM upgrade based upon the Pioneer Plasma Generic, creating a new upgrade containing that button assigned to an unused button as you suggested. I think I had trouble doing the keymove because I was doing the 994 on the remote itself with the wrong button
. Works now. Do I understand?
What puzzles me is, how to make IR do this. What do I enter in IR for the EFC/Hex Cmd since in this case, we're talking about two numbers, namely the Device1 170 with Cmd1=211 and the second half of the double-style signal Device 175, Cmd2=OBC 126 in this specific case?
I'd rather do this in IR for simplicity's sake and documentation.
Mitch
Posted: Wed Sep 07, 2005 7:01 pm
by The Robman
In IR, when the add keymove screen pops-up, you should notice that there's a radio button with the following 3 choices:
EFX
Hex Command
Key
You want to select the latter one. Then, the data entry cell will transform into a drop-down menu which you can use to select the key that you're coping FROM.
Posted: Wed Sep 07, 2005 7:14 pm
by mvgossman
I needed to move to the new IR for that, should work out fine.
Why does KM for this device not allow these and other codes to be assigned to certain buttons such as rewind, play, etc. and therefore forcing these machinations?
Is there a way to assign the new code in the upgrade to anything other than the eligible buttons in the spreadsheet, some sort of virtual button similar in concept to dev7 as a virtual device?
Mitch
Posted: Wed Sep 07, 2005 8:08 pm
by The Robman
mvgossman wrote:Why does KM for this device not allow these and other codes to be assigned to certain buttons such as rewind, play, etc. and therefore forcing these machinations?
KM merely enforces the rules that are built into the remote itself. If you had been using a protocol that uses 1-byte commands, KM would have let you assign functions to buttons that are not part of the keymap, and it would have generated the keymoves for you. But to expect KM to not only create a 2nd upgrade, but to also assign all the necessary keymoves for your 2-byte upgrade is asking a little bit much of a spreadsheet. Heck, even RM won't do that for you!
