The Robman, your Pioneer DVD Recorder DVR-520HS.txt file?

Wheelie4 · Post by **Wheelie4** » Thu Jan 27, 2005 3:35 pm

Hi Robman,

I just ordered the Pioneer DVR-420H from Costco (a 520 minus DV jack made exclusively for Costco by Pioneer). It will be here in a week. It uses the same remote and manual as the 520H. I decided to try setting up a device with your Pioneer DVD Recorder DVR-520HS file but ran into some confusion.

In KM the buttons listed as "program, repeat A/B, erase, edit" are not on remote.

Disc navigator and top menu is one button but in KM you listed them seperately with two different efc's.

menu and playlist is one button but listed seperately with two different efc's

ok and stop is one button but listed seperately with two different efc's

and whats "-/--"? I don't see it on the remote either.

I plan to learn the remotes codes into my old pronto and use decodeccf to create a spreadsheet of the codes but pioneer codes just blow my mind. I cannot figure them out. I never know which ecf to use, there's usually three efc's per button. My old pioneer cd changer's codes totally confused me. Any helps is appreciated.

gfb107 · Post by **gfb107** » Thu Jan 27, 2005 3:57 pm

In a KM/RM device upgrade, we always try to include all functions (actually commands) that the component responds to, which often includes commands that aren't on the original remote.

Also, the buttons sheet in RM/KM names the buttons availble on the JP1 remote you are trying to program, not the names of the buttons on the original remote.

On many remotes, some buttons are dual-purpose, and the command they send changes depending on the mode the remote is in at the time..

For many protocols, including Pioneer, you want to stick with OBCs and forget about EFCs.

Wheelie4 · Post by **Wheelie4** » Thu Jan 27, 2005 4:27 pm

In a KM/RM device upgrade, we always try to include all functions (actually commands) that the component responds to, which often includes commands that aren't on the original remote.

Understood that point.

Also, the buttons sheet in RM/KM names the buttons availble on the JP1 remote you are trying to program, not the names of the buttons on the original remote.

Understood that point.

On many remotes, some buttons are dual-purpose, and the command they send changes depending on the mode the remote is in at the time..

Understood that point.

It's just that I planned on assigning all the buttons from the remote to the device file. This will ofcourse create alot of keymoves. I'm running out of space. For example (two codes for the single button "Disc navigator and top menu" plus the other dual purpose buttons split to two seperate buttons adds up to several more keymoves.) I was hoping to narrow that back to one code for each dual purpose button.

And some names he's included aren't labeled on the remote as dual purpose use like "program, repeat A/B, erase, edit". I'm guessing I can just leave those out of the device due to there functionality being accessible through the menu's.

For many protocols, including Pioneer, you want to stick with OBCs and forget about EFCs

That I wasn't aware of. Appreciate that tip.

Post by **The Robman** » Thu Jan 27, 2005 6:39 pm

When you see a file that was created by me, don't assume that I actually have the device in question, because most of the time I don't. If you take a closer look you'll find a very large percentage of upgrade files are actually created by me, these are usually done by decoding CCF files or using data from some other source, and where usually done for someone who was asking about the device in question.

Therefore, I have no idea what the story is behind the buttons, etc.

Wheelie4 · Post by **Wheelie4** » Fri Jan 28, 2005 10:57 am

No Problem Robman. After I make a Excel sheel of the OEM remotes codes using prontoedit and decodeccf I'll get it straightened out.

Wheelie4 · Post by **Wheelie4** » Sun Jan 30, 2005 2:26 pm

Well, I decoded a ccf file of the Pioneer 520 and compared it to Rob's device file alot in RM and DecodeCCF Viewer and I figured out the differences between the OBC:Device and the Prefix Command:Prefix Device enabling me to make a RM file from scratch. But my intention was to create it in KM but if I open Rob's device file in KM it's slightly different on the Function sheet. There's a byte column thats making no since to me. I read the Protocol Help sheet to no avail. Any tip on something I'm missing?

Something off happens when I try to create the RM file though. On the Setup tab I input the same info Rob has if I open his in RM. But when I input the OBC it auto chooses the wrong Device (171) instead of 175 and wont let me change it.

Wheelie4 · Post by **Wheelie4** » Sun Jan 30, 2005 3:18 pm

I think I figured it out. In KM on the Setup sheet.

If:
Device1: 171
Device2: 175
Cmd1 (OBC): 42
Cmd2 (OBC): 44

and:
1 = double-style signal (using dev1/cmd1 in the first half)
3 = double-style signal (using dev1/cmd2 in the first half)

then:
171 + 42 = byte1

or:
171 + 44 = byte3

Am I figuring this right?