 |
JP1 Remotes
|
| View previous topic :: View next topic |
| Author |
Message |
zesta
Joined: 10 Dec 2003
Posts: 2
|
 Posted: Wed Dec 10, 2003 9:29 pm Post subject: advanced button codes for Pioneer receiver? |
 |
|
I have a Scientific Atlanta Explorer 8000 DVR cable box that originally came with an AllTouch AT8400 remote. It controlled my devices just fine, but only had 4 devices. My cable company recently gave me the new UEI Atlas DVR 5-device remote instead. It seems to work fine, except for my Pioneer VSX-D812K receiver. The 1023 device code makes the power button function, as well as the volume. Also, the number buttons choose certain inputs. However, unlike the old AllTouch (And my Radio Shack 15-1994 before it) there is no button to cycle through the inputs on the receiver. I cannot find any advanced codes listed for the 1023 device code. Does anyone know how I can find one? I would actually like to program the number buttons to specific inputs as well, but a button like the "INPUT SEL" on the original remote would suffice.
thanks,
-Randy |
|
| Back to top |
|
 |
Mark Pierson
Expert
Joined: 03 Aug 2003
Posts: 3017
Location: Connecticut, USA
|
| Posted: Wed Dec 10, 2003 9:35 pm Post subject: |
|
|
I think the 1023 code is a combo and thus uses 2-byte commands. That precludes the use of advanced codes, at least from the remote itself. You can still set them up in IR using the Hex Cmd setting in the Key Moves dialog.
Browse the Device Codes folders in the Files section to see if there's any Pioneer files for or close to your device... they may contain the codes you're looking for. You may also want to check the Pronto files over at RemoteCentral.
_________________
Mark |
|
| Back to top |
|
|
zesta
Joined: 10 Dec 2003
Posts: 2
|
| Posted: Wed Dec 10, 2003 11:38 pm Post subject: |
|
|
I don't yet have a JP1 cable. I was hoping to be able to enter n advanced code on the remote to at least test the functionality before getting the cable.
I found a code file in he files section. How exactly do I interpret that information to see if there will be a code that will work?
thanks,
-Randy |
|
| Back to top |
|
|
dethbunny
Joined: 06 Jan 2004
Posts: 8
Location: Macomb, IL
|
| Posted: Tue Jan 06, 2004 3:40 pm Post subject: Any luck? |
|
|
I have the same receiver and the OFA-8810 remote, and am now learning the software. People around here talk like it's the most simple thing in the world, but the software is far from intuitive 
I suppose much of that is because the process itself is far from intuitive, but c'est la vie.
I'll let you know how much luck I have. I'm already on this pretty well, I think. |
|
| Back to top |
|
|
e34m5
Joined: 14 Oct 2003
Posts: 675
Location: Atlanta
|
| Posted: Tue Jan 06, 2004 3:58 pm Post subject: |
|
|
I have just learned, very painfully I might add, that setup code 1023 you can't use the push button method to test functionality because 1023 does not support EFC's.
So the easiest thing would be to learn the commands onto the new remote (if it supports learning) and then create some macors around those learned commands.
Good luck. |
|
| Back to top |
|
|
mr_d_p_gumby
Expert
Joined: 03 Aug 2003
Posts: 1370
Location: Newbury Park, CA
|
| Posted: Tue Jan 06, 2004 4:24 pm Post subject: |
|
|
| zesta and dethbunny wrote: | | ...Pioneer VSX-D812K receiver... |
| e34m5 wrote: | | So the easiest thing would be to learn the commands onto the new remote (if it supports learning) and then create some macors around those learned commands. |
Well, actually, I would think the easiest thing would be to start by loading this upgrade for Pioneer receivers into KM...
_________________
Mike England |
|
| Back to top |
|
|
dethbunny
Joined: 06 Jan 2004
Posts: 8
Location: Macomb, IL
|
| Posted: Wed Jan 07, 2004 1:15 am Post subject: Explains a lot |
|
|
(still a new new new newbie, so take that into account if I say something rediculous)
I was starting to wonder if there was a problem with this receiver and EFCs, I decoded the learned buttons in IR and found the right EFCs, compared them with the OBC/EFC cross-reference available on this site, and tried to add commands to buttons...no worky. I knew it was the same command, so I was about to get frustrated really quick
Could this have to do with the Pioneer receivers using 2-byte commands? That would explain to me why the one-byte decoding algorithm gets a one-byte command that doesn't do anything as a result, while the learned commands faithfully spit out the original (correct) command.
I had downloaded that KM file and parsed it a bit in my head, but with no Excel on this computer I don't know exactly how to use the protocol upgrade portion.
<strike> | Quote: | | ((had quoted much of file here)) |
How should I enter that into IR?
I tried stripping the commas (and adding the appropriate spaces) but it didn't look right in IR. A million lines (rounded up =P) in the protocol information field with only two lines in the data addresses field. I ignored the three lines after 'End.'
What goes in the 'protocol id' field, while we're at it?</strike>
Nevermind, I'm a genius. Well, I think so. I figured out how to copy that info to IR at least.
The only problem is the device entry looks like this:
| Quote: | Audio: 1023
# Key Name Hex Command EFC
1 0 00 00 018* (Use Hex)
2 1 80 00 018* (Use Hex)
3 2 40 00 018* (Use Hex)
4 3 C0 00 018* (Use Hex)
5 4 20 00 018* (Use Hex)
6 5 A0 00 018* (Use Hex)
7 6 60 00 018* (Use Hex)
8 7 E0 00 018* (Use Hex)
9 8 10 00 018* (Use Hex)
10 9 90 00 018* (Use Hex)
11 VOL+ 50 40 016* (Use Hex)
12 VOL- D0 40 016* (Use Hex)
13 Mute 48 40 016* (Use Hex)
14 CH+ 08 00 018* (Use Hex)
15 CH- 88 00 018* (Use Hex)
16 Power 38 40 016* (Use Hex)
17 Down 81 40 016* (Use Hex)
18 FWD 59 80 014* (Use Hex)
19 Guide [Not Mapped] [Not Mapped]
20 Left C1 40 016* (Use Hex)
21 Pause F9 80 014* (Use Hex)
22 Play 79 80 014* (Use Hex)
23 REC [Not Mapped] [Not Mapped]
24 REW D9 80 014* (Use Hex)
25 Right 41 40 016* (Use Hex)
26 Select 21 40 016* (Use Hex)
27 Stop 19 80 014* (Use Hex)
28 Up 01 40 016* (Use Hex)
29 Enter C2 00 018* (Use Hex)
30 PREV [Not Mapped] [Not Mapped]
31 TV/VID C8 00 018* (Use Hex)
32 F.FWD 39 80 014* (Use Hex)
33 F.REW B9 80 014* (Use Hex) |
Those buttons are eerily similar to the entries for the TiVo remote that is the only other custom device, if you didn't notice. How do I fix that? |
|
| Back to top |
|
|
dethbunny
Joined: 06 Jan 2004
Posts: 8
Location: Macomb, IL
|
| Posted: Wed Jan 07, 2004 1:18 am Post subject: |
|
|
Can we turn on HTML, pleeeeeease?
=) |
|
| Back to top |
|
|
mr_d_p_gumby
Expert
Joined: 03 Aug 2003
Posts: 1370
Location: Newbury Park, CA
|
| Posted: Wed Jan 07, 2004 2:14 am Post subject: Re: Explains a lot |
|
|
| dethbunny wrote: | | Could this have to do with the Pioneer receivers using 2-byte commands? That would explain to me why the one-byte decoding algorithm gets a one-byte command that doesn't do anything as a result, while the learned commands faithfully spit out the original (correct) command. |
It's not the Pioneer receiver, it's UEI's implementation of the Pioneer setup code that's at the heart of the problem. You cannot control this setup code with EFCs. It needs two bytes for each command.
| dethbunny wrote: | People around here talk like it's the most simple thing in the world, but the software is far from intuitive
...
I had downloaded that KM file and parsed it a bit in my head, but with no Excel on this computer I don't know exactly how to use the protocol upgrade portion. |
Since you are only using half of the software needed to accomplish the task, it's no wonder you find it unintuitive. If you don't have Excel, then you could try to see if RM works for you. But to save you the trouble, go to the Devices tab in IR, click on the Add button, and paste this into it:
| Code: | Upgrade Code 0 = 23 FF (Tuner/1023)
6A 00 FC EE EF C5 A5 25 00 00 80 00 40 00 C0 00
20 00 A0 00 60 00 E0 00 10 00 90 00 50 40 D0 40
48 40 08 00 88 00 38 40 81 40 59 80 C1 40 F9 80
79 80 D9 80 41 40 21 40 19 80 01 40 C2 00 C8 00
39 80 B9 80
KeyMoves
21 F4 23 FF D9 4D 18 F4 23 FF C8 52 24 F4 23 FF
BA 52
End |
Without KM or RM, you'll have to accept the function mapping that is in this file. Here are the Notes in the file:
The list of functions in the Functions sheet is (hopefully) the complete list of functions available for Pioneer Receivers. I have only mapped the more obvious functions, so it's up to you to decide which of the remaining functions you need and which buttons you would like them assigned to.
Here's a complete list of the functions in that upgrade, not all of which will work on your model receiver:
| Code: | Function HexCmd
==================== ======
Tuner 0/10 00 00
Tuner 1 80 00
Tuner 2 40 00
Tuner 3 C0 00
Tuner 4 20 00
Tuner 5 A0 00
Tuner 6 60 00
Tuner 7 E0 00
Tuner 8 10 00
Tuner 9 90 00
Tuner Station + 08 00
Tuner Station - 88 00
Tuner Band am/fm C8 00
MPX return 78 00
class 02 00
Tuner Direct Access C2 00
Text/RDS 52 00
Tuner Scan B2 00
Tuner HITS 72 00
Tuner Frequency + 6A 00
Tuner Frequency - EA 00
tuner edit 1A 00
Tuner Custom 3A 00
Volume + 50 40
Volume - D0 40
TV/SAT 30 40
input: LD B0 40
input: VCR2 70 40
input: VCR2 F0 40
input: TAPE1 F0 40
input: VCR1 F0 40
input: SAT 08 40
input: TAPE2 88 40
mute 48 40
display C8 52
video 68 40
Power on discrete 58 40
Power off discrete D8 40
Power toggle 38 40
input: TAPE3 B8 40
DSP 02 40
Rcvr Rear Level + 82 40
*bass/treb + 82 4C
effect + 82 54
channel level - 82 5C
surr ch- 82 5C
Rcvr Rear Level - 42 40
*bass/treb - 42 4C
effect - 42 54
channel level + 42 5C
surr ch+ 42 5C
loudness 22 40
Tuner E2 40
Rcvr Sleep 12 40
CD 32 40
Phono B2 40
DVD F2 40
mute on 8A 40
mute off 4A 40
video select 2A 40
input AA 40
speaker a/b 6A 40
test tone 6A 50
signal select 6A 58
channel select 6A 44
effect/ch sel 6A 44
dimmer 6A 4C
*bass + EA 40
bass - EA 50
*tone EA 40
*bass/treble EA 48
treble + EA 48
treble - EA 58
sur mode + EA 42
sur mode - EA 52
hi-bit 9A 4C
dnr 9A 5C
*sur movie 5A 5C
*sur music 5A 42
Rcvr Delay Time 5A 58
Rcvr Simulated Stereo 5A 54
Direct BA 42
exit BA 52
multi ch input 7A 40
5.1/7.1 7A 4C
Input ATT 7A 5C
DD/DTS 7A 42
effect - 06 54
up arrow 01 40
down arrow 81 40
right arrow 41 40
left arrow C1 40
select/enter 21 40
DVD A1 40
CDR/Tape 11 40
menu D9 4D
Status D9 57
stereo/direct F9 40
midnight F9 5A
THX F9 51
sb ch mode F9 45
acoustic eq F9 47
Power off discrete C7 40
Power on discrete A7 40
play 79 80
pause F9 80
rewind D9 80
fast fwd 59 80
stop 19 80
dvd/cd trk/chpt + 39 80
dvd/cd trk/chpt - B9 80 |
| dethbunny wrote: | | Can we turn on HTML, pleeeeeease? |
I wouldn't hold my breath waiting on that one.
_________________
Mike England |
|
| Back to top |
|
|
dethbunny
Joined: 06 Jan 2004
Posts: 8
Location: Macomb, IL
|
| Posted: Fri Jan 09, 2004 3:57 am Post subject: lack of KM |
|
|
I have (and have used) RM, but at the moment it doesn't seem like RM wants to do anything with Pioneer-Master-List.txt. I tried it in conjunction with the "Import KM file..." command, but that got me nowhere. On the other hand, your posting of the hex codes is much appreciated. I'll take those and enter them into RM manually, I guess, then make a mapping that works for me. (Then I'll post to the files, of course. )
I still think IR is far from intuitive, but as I said before, that may be because the process as a whole is far from intuitive. Ah well, I have a good enough grasp on it now anyway.
::insert the trying of things here::
Ah...IR is letting me do this just fine. I fixed up the volume and mute buttons for the 'sat' button to control the receiver, and it's working just fine. Your hex commands have already been useful!
On the other hand, RM is telling me "The hex command must contain exactly 1 bytes." in bold red letters when I try to give it the 2-byte codes. Is there a fix, or does RM not support 2-byte codes yet? Software always lacks the one feature I need. =)
Okay, problem solved. I found I needed to use the "Pioneer 2CMD" protocol instead of straight "Pioneer" to avoid the error. (Why did I leave all the text above, then? To help those later who use the search engine to find answers, of course! That, and to understand how I got where I am.)
I'll check in eventually to let you know how this is going... |
|
| Back to top |
|
|
johnsfine
Site Admin
Joined: 10 Aug 2003
Posts: 4766
Location: Bedford, MA
|
| Posted: Fri Jan 09, 2004 9:19 am Post subject: Re: lack of KM |
|
|
| dethbunny wrote: | | I have (and have used) RM, but at the moment it doesn't seem like RM wants to do anything with Pioneer-Master-List.txt. I tried it in conjunction with the "Import KM file..." |
1) RM really should be better about reporting errors to the user. In a few cases it does report an error, but normally some action you request seems to simply not happen (as in your example). Then you need to dig through the rmaster.err file for a hint (in this case, that findNearestProtocol failed, though you still need to guess why, which is that protocols.ini has nothing for Pioneer 3DEV protocol, used in that file).
2) RM really should give you more flexibility to make some use of an imported or opened file that isn't perfectly compatible with the current protocols.ini and/or RDF files. There is some attempt at that, but mostly what you read in either fits or you can't use it at all.
3) Someone ought to add more of the Pioneer Protocols to protocols.ini and make the existing ones more RM style (like the existing Pioneer DVD) and less KM style (like Pioneer 2CMD). I tend to wait until I have the time and understanding needed to do the job the way I think is right, rather than recognise that done badly is usually better than waiting to be done right. I don't know if I'll ever have time to understand the Pioneer stuff well enough to do those "right".
Of course I'm probably the one who ought to be doing much of the above. (None of this should be read as a complaint about the quality or quantity of Greg's work). But I probably don't have time, so other volunteers are requested.
| dethbunny wrote: |
Okay, problem solved. I found I needed to use the "Pioneer 2CMD" protocol instead of straight "Pioneer" to avoid the error. (Why did I leave all the text above, then? To help those later who use the search engine to find answers, of course! |
I thought you left it in because, even though you found a work around, it reminds us of three aspects of RM that seriously need improvement. |
|
| Back to top |
|
|
dethbunny
Joined: 06 Jan 2004
Posts: 8
Location: Macomb, IL
|
| Posted: Fri Jan 09, 2004 2:21 pm Post subject: |
|
|
::coughs:: yeah, that's why. =)
So, your opinion, should I post a RM file that includes all the commands (from the master list, and already done) or a list specific to the VSX-D812? I'm going through the effort to find all the codes the receiver reacts to, so I suppose I may as well make both files.
By the way, random observation, RM gets really slow when many buttons are defined. At least, it gets slow at mapping, through either the "buttons" or "layout" tab. |
|
| Back to top |
|
|
dethbunny
Joined: 06 Jan 2004
Posts: 8
Location: Macomb, IL
|
| Posted: Fri Jan 09, 2004 3:30 pm Post subject: |
|
|
Okay, I uploaded my rendition of themaster list to the files section. Good deed for the day done.
The next problem is updating my VSX-812-specific version. I'm trying to do that by learning all the receiver buttons and looking at them in IR, but I'm not entirely sure DecodeIR supports the two-byte (two-part?) commands correctly. First off, the learned functions for input selection give me OBCs identical to what RM shows (from the old pioneer master list), but where does DecodeIR show the 2nd byte? I know it's '2' for those buttons, but with other buttons it's probably not.
After that, what about buttons that give me two lines as the output from DecodeIR? Do I have to create macros for them to work properly as defined commands?
Below is the learned "midnight/loudness" button as an example.
| Code: | | +8506 -4262 +546 -1576 +546 -522 +546 -1576 +546 -522 +546 -522 +546 -1576 +546 -522 +546 -1576 +546 -522 +546 -1576 +546 -522 +546 -1576 +546 -1576 +546 -522 +546 -1576 +546 -522 +546 -1576 +546 -1576 +546 -1576 +546 -1576 +546 -1576 +546 -522 +546 -522 +546 -1576 +546 -522 +546 -522 +546 -522 +546 -522 +546 -522 +546 -1576 +546 -1576 +546 -522 +546 -25394 +8506 -4262 +546 -1576 +546 -522 +546 -1576 +546 -522 +546 -522 +546 -1576 +546 -522 +546 -1576 +546 -522 +546 -1576 +546 -522 +546 -1576 +546 -1576 +546 -522 +546 -1576 +546 -522 +546 -1576 +546 -1576 +546 -522 +546 -1576 +546 -522 +546 -522 +546 -1576 +546 -1576 +546 -522 +546 -522 +546 -1576 +546 -522 +546 -1576 +546 -1576 +546 -522 +546 -522 +546 -25394 |
(I figure you're the expert on how DecodeIR behaves, after all.  ) |
|
| Back to top |
|
|
johnsfine
Site Admin
Joined: 10 Aug 2003
Posts: 4766
Location: Bedford, MA
|
| Posted: Fri Jan 09, 2004 4:08 pm Post subject: |
|
|
| dethbunny wrote: | | First off, the learned functions for input selection give me OBCs identical to what RM shows (from the old pioneer master list), but where does DecodeIR show the 2nd byte? |
| dethbunny wrote: |
After that, what about buttons that give me two lines as the output from DecodeIR? |
Those two questions are two sides of one coin.
The special Pioneer signals are all compound signals. A normal signal has the base device and a single OBC. IIRC a compound signal has a special OBC in the base device followed by another frame, usually with a different device, with the meaningful OBC.
DecodeIR simply sees that as two commands.
The various Pioneer protocols have various (documented in files with KM) rules for how one or two bytes of hex command (and the fixed data) can specify whether or not each signal is compound and what the second OBC is (and maybe what the second device is or what the first OBC is).
| dethbunny wrote: |
Do I have to create macros for them to work properly as defined commands?
|
No.
| dethbunny wrote: |
(I figure you're the expert on how DecodeIR behaves, after all. ) |
Yes, but what matters here is that Rob is the expert on how Pioneer misbehaves. |
|
| Back to top |
|
|
dethbunny
Joined: 06 Jan 2004
Posts: 8
Location: Macomb, IL
|
| Posted: Fri Jan 09, 2004 4:17 pm Post subject: |
|
|
So, what would be the way to go from learned codes to defined codes and a custom device entry?
Ask Rob? |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
File Section
Wiki
