Your Universal Remote Control Center
RemoteCentral.com
Original Equipment Remotes Forum - View Post
Previous section Next section Up level
Up level
The following page was printed from RemoteCentral.com:

Login:
Pass:
 
 

Topic:
Pioneer XV-DV313 IR Codes/Commands
This thread has 9 replies. Displaying all posts.
Post 1 made on Monday March 1, 2010 at 10:12
hyp0crisy88
Lurking Member
Joined:
Posts:
March 2010
5
Hi everyone :)
Just registered, been reading for a while though :)
I have searched just about everywhere for IR codes for my Pioneer system XV-DV313. I have an Logitech Harmony 515 and it works for switching between lines and such, Audio and Surround settings also work, but I cannot change the bass level and channel lvl on every speaker, I could when I had the original one. Does anyone here know of where to download a complete IR Code package for this system/remote?

best regards, hyp0crisy
Post 2 made on Tuesday March 2, 2010 at 03:25
3FG
Select Member
Joined:
Posts:
August 2009
1,861
There is an upgrade file for this at hifi-remote.com.  The file is in the format used by RemoteMaster. A very large number of functions are listed.
OP | Post 3 made on Tuesday March 2, 2010 at 06:15
hyp0crisy88
Lurking Member
Joined:
Posts:
March 2010
5
3FG, thank u very very much!
How do I upload this to my Harmony Remote?
Again, thank u :D
Post 4 made on Tuesday March 2, 2010 at 11:46
3FG
Select Member
Joined:
Posts:
August 2009
1,861
I think there are two ways:
1) Convert all the codes to Pronto Hex (we can help with that), identify the functions that aren't already in the Harmony, and send the Pronto Hex for the new functions to Logitech, with a request that they add them to the setup for the XV-DV313.

2) Get a UEI manufactured remote, use setup code Audio 1384, and enter a 5 digit EFC to assign each new function to a button. Then teach the functions to the Harmony. Suitable remotes include any Comcast, Atlas remotes used by many other cable companies, many OneForAlls, high end Vizio remotes, some Radio Shack, and some RCA. The EFCs are listed below.

The DV313 uses a the Pioneer two command IR protocol, in which many functions require sending two commands. In the below table, those functions are listed as having a prefix device and prefix command.  See if any of these are likely to help.  Sorry about the formatting -- the EFC is 5 digits, and there's no space between it and the prefix device. 

FunctionEFCprefix deviceprefix commandmain devicemain comman
Aroow UP01222166160175228
Arrow DOWN02246166160175229
Arrow LEFT01734166160175230
Arrow RIGHT02758166160175231
Angle55492166161175181
Audio22212166161175190
CD Mode6496416616117596
Ch Level49093nonenone166114
Clear57797nonenone16665
Condition55748166161175177
Disc 15370016616117549
Disc 25318816616117550
Disc 35421216616117551
Disc 45242016616117552
Disc 55344416616117553
Disc Skip16068166161175126
DSP07877nonenone16694
DVD/CD0429416616017537
DVD Display03012166161175227
DVD Setup54724166161175176
Enter48325nonenone166116
FL Dimmer14021nonenone166158
Last Memo50884166161175246
Menu22980166161175185
Mono43461nonenone166209
Mute11973nonenone16630
Num 0/1029125nonenone1669
Num 160869nonenone1660
Num 261893nonenone1661
Num 361381nonenone1662
Num 462405nonenone1663
Num 560613nonenone1664
Num 661637nonenone1665
Num 761125nonenone1666
Num 862149nonenone1667
Num 928101nonenone1668
Num >1056773nonenone16664
Open/Close54980166161175182
Pause38854166160175170
Play39366166160175169
Program33988166161175236
Random18116166161175254
Repeat01220166161175228
Repeat A-B34244166161175232
Return50372166161175244
Scan/Fast FWD48069nonenone166147
Scan/Fast REV46277nonenone166148
Search56260166161175179
Sleep12741nonenone16625
Sound10181nonenone166218
Standby/On21700166161175188
Step/Slow FWD56004166161175183
Step/Slow REV21956166161175184
Stop46533nonenone166144
Subtitle5293216616117554
Surround Mode42181nonenone166212
System Display14533nonenone166157
System Setup65221nonenone166102
Test Tone43205nonenone166213
Top Menu54468166161175180
Track/Chapter NEXT47557nonenone166145
Track/Chapter PREV47045nonenone166146
Tuner/Band06342166160175165
TV/AUX07110166160175163
Vol UP28613nonenone16610
Vol DOWN29637nonenone16611
line 1 205318166160175164
OP | Post 5 made on Friday March 5, 2010 at 17:09
hyp0crisy88
Lurking Member
Joined:
Posts:
March 2010
5
Hi again :)

I've been in contact with Logitech support, they asked for HEX/Pronto format, so what tools will I be needing to convert them to this format?

best regards, hyp0crisy 88
Post 6 made on Friday March 5, 2010 at 23:59
3FG
Select Member
Joined:
Posts:
August 2009
1,861
Well, this is going to take some work. First, download a couple of tools.

MakeHex
IRtool.exe

Use MakeHex to generate the Pronto Hex, and IRtool to check that it was done correctly.  Be sure to read the instructions with MakeHex--it has an unusual user interface.

EDIT: See Post #8 below for a simpler way to do this.

Since many of the IR signals actually contain two commands, this is a little tricky.
For MakeHex, edit Pioneer.irp so that the device is 166, and the functions are 0..255.  Save the resulting hex file.  Re-edit Pioneer.irp making device 175 and functions 0..255.  Save that file too.

In the above list, if there are any functions that you want to send to Logitech which have none as the prefix device/command, then you can use the device=166 file directly and use the Pronto hex associated with the function number.

For the functions which use two commands, you'll need to merge the Pronto Hex.  You'll be using either 166, command 160, or command 161.  Then append the Hex associated with device 175, and the appropriate command number.  However, before appending, delete the first four words, i.e. delete 0000 0068 0000 0022.

And in the first part (the 166 Hex, change the first 0022 to 0044.

Finally, open up IRtool, and copy the resulting Pronto Hex into the box and click on decode.  With any luck it will respond with the correct device and commands.

For example, Play is listed above as
Play39366166160175169
The Pronto Hex for 166 command 160 (obtained from MakeHex) is
0000 0068 0000 0022 0168 00B4 0016 0017 0016 0044 0016 0044 0016 0017 0016 0017 0016 0044 0016 0017 0016 0044 0016 0044 0016 0017 0016 0017 0016 0044 0016 0044 0016 0017 0016 0044 0016 0017 0016 0017 0016 0017 0016 0017 0016 0017 0016 0017 0016 0044 0016 0017 0016 0044 0016 0044 0016 0044 0016 0044 0016 0044 0016 0044 0016 0017 0016 0044 0016 0017 0016 06DA

For 175 command 169 it is
0000 0068 0000 0022 0168 00B4 0016 0044 0016 0044 0016 0044 0016 0044 0016 0017 0016 0044 0016 0017 0016 0044 0016 0017 0016 0017 0016 0017 0016 0017 0016 0044 0016 0017 0016 0044 0016 0017 0016 0044 0016 0017 0016 0017 0016 0044 0016 0017 0016 0044 0016 0017 0016 0044 0016 0017 0016 0044 0016 0044 0016 0017 0016 0044 0016 0017 0016 0044 0016 0017 0016 06DA

The four groups in italics should be deleted, and the 0022 in bold should be doubled to 0044.

Combining,
0000 0068 0000 0044 0168 00B4 0016 0017 0016 0044 0016 0044 0016 0017 0016 0017 0016 0044 0016 0017 0016 0044 0016 0044 0016 0017 0016 0017 0016 0044 0016 0044 0016 0017 0016 0044 0016 0017 0016 0017 0016 0017 0016 0017 0016 0017 0016 0017 0016 0044 0016 0017 0016 0044 0016 0044 0016 0044 0016 0044 0016 0044 0016 0044 0016 0017 0016 0044 0016 0017 0016 06DA 0168 00B4 0016 0044 0016 0044 0016 0044 0016 0044 0016 0017 0016 0044 0016 0017 0016 0044 0016 0017 0016 0017 0016 0017 0016 0017 0016 0044 0016 0017 0016 0044 0016 0017 0016 0044 0016 0017 0016 0017 0016 0044 0016 0017 0016 0044 0016 0017 0016 0044 0016 0017 0016 0044 0016 0044 0016 0017 0016 0044 0016 0017 0016 0044 0016 0017 0016 06DA

This is the Pronto Hex to send to Logitech.
IRTool shows this as device 166, OBC 160 plus device 175, OBC 169.

Simple, right?
 

Last edited by 3FG on March 6, 2010 13:03.
OP | Post 7 made on Saturday March 6, 2010 at 07:47
hyp0crisy88
Lurking Member
Joined:
Posts:
March 2010
5
Hehehe, yeah, very simple x] For those who know what they're doing :)

But anyways, I downloaded both programs, read the ReadMe and edited the Pioneer.irp, but I have 2 files in the MakeHEX folder called pioneer.irp and pioneer2.irp, should I edit them both?

best regards, hyp0crisy
Post 8 made on Saturday March 6, 2010 at 12:34
3FG
Select Member
Joined:
Posts:
August 2009
1,861
The above instructions are for Pioneer.irp. However, your question made me look more closely and Pioneer2.irp can be used to do this more easily.

So here's an alternate (and simpler) set of instructions.

Edit Pioneer2.irp. The first 3 lines should look like:
Device=166.175
Define P=160
Function=0..255
Now you can drag this file onto MakeHex.exe and get the file Pioneer2.hex. Rename this to 166_160.hex or something like that, because MakeHex will overwrite unless it is renamed.

Edit Pioneer2.irp again and change the 160 to 161.
After running MakeHex on that, you'll have a second Hex file.

There's no need to combine codes, or delete lines. For Play, which is command 166 function 160 plus 175, function 169, just use the Hex code from the first hex file, at function 169. For other functions, which use a prefix function of 161, use the second Hex file.

Do make sure to use IRTool to check your work

Last edited by 3FG on March 6, 2010 13:01.
OP | Post 9 made on Saturday March 6, 2010 at 17:14
hyp0crisy88
Lurking Member
Joined:
Posts:
March 2010
5
Those two HEX files I get out of MakeHEX, could I just mail them to Logitech?
As they hold all the available commands for the remote, right?
Post 10 made on Saturday March 6, 2010 at 22:41
3FG
Select Member
Joined:
Posts:
August 2009
1,861
I have never dealt with Logitech, but I wouldn't expect that approach would work at all. The two *.hex files contain device numbers and function numbers, without any indication of the actual function that they are supposed to perform.
Maybe if you made one file that excised the unused functions, and included the function name next to each function number, perhaps they would work with that.

I guess you should include only a few functions that already work, clearly marked as already working. In that way, they don't need to sort through much, but would have some confidence that the code are correct if the already functioning codes match their database. Have you thought about which keys they should map the functions to? Is there a straightforward way to do that, and one that other users would find intuitive? If not, they may not be too responsive in setting this up--it's not clear how populating obscure functions helps their bottom line.

Frankly, if Logitech were really interested in populating their database, they would accept just a device number and function number, and not require Pronto Hex.


Jump to


Protected Feature Before you can reply to a message...
You must first register for a Remote Central user account - it's fast and free! Or, if you already have an account, please login now.

Please read the following: Unsolicited commercial advertisements are absolutely not permitted on this forum. Other private buy & sell messages should be posted to our Marketplace. For information on how to advertise your service or product click here. Remote Central reserves the right to remove or modify any post that is deemed inappropriate.

Hosting Services by ipHouse