problem on HP Media Center for URC9960 B01

[cavourahpong]

Dear all,

My using remote is OneForAll URC9960 B01.

And I have a HP PC:
Model : HP Pavilion m7168hk
OS: Microsoft® Windows® XP Media Center Edition

I have tried to use my URC9960 remote to learn my HP PC's "hp media center", but some problems found.

I have tried to using my IR learnt with my URC9960, it works.
But after IR.exe Key master to gen a device code for the URC9960, the code doesn't work.

1. IR.exe program to read the learnt
Protocol = RC6-6-32
Device Code=128
Sub Device = 3972
OBC: yes, with Hex code
EFC: No, NULL, there is no any Hex code
Misc = 0
"There is no value in EFC"

2. Using Keymaster
I cannot find the protocol:"RC6-6-32" from the list for selection,
therefore, I chose "RC6"
But I cannot find any input box that I can input the value of "Sub Device"
So, I ignore inputing the sub device value.

After, I upload my created code to my URC9960 remote, it doesn't work.

Remark: This HP remote should simular to Microsoft Media Center's remote.

Regards,
Cavour

[whompus]

Just FYI. Rm will handle that protocol now. Km will most likely on the next update.

I suggest you get rm and give it a go. Not to say its better or worse. It does get updated more often.

I see there is a new version of rm being worked on as we type.

[johnsfine]

You might want to get a newer version of DecodeIr.dll

I'm pretty sure those signals should decode as "MCE", which is a specific form of "RC6-6-32".

RM has both RC6-6-32 and MCE. give the correct (different) device and subdevice numbers both would generate the same upgrade.

There are some custom upgrades posted somewhere for KM for RC6-6-32 (if you have some big problem with switching to RM).
In your other thread
http://www.hifi-remote.com/forums/viewt ... 7532#37532
lharles posted a link to a good KM based custom upgrade for this.
There are a few different sets of device numbers in use for MCE, so other users of that custom upgrade may need to get expert help changing the "Raw Fixed Data" field. But your HP version of MCE seems to use exactly the same Fixed Data values as the one in that KM custom upgrade.


Also, I'm confused by what you say about "with Hex code" and "EFC: no". DecodeIr should give IR.EXE the hex cmds for this protocol, and IR.EXE should display EFC numbers for any protocol where it gets hex cmds.

[cavourahpong]

Dear all,

I have tried to use IR.exe to upload my created codes.
But doesn't work, and an error message appears, "This section terminator in the keymove section does not match the one specified in the RDF. It will be loaded, but it may not save property."

a.
1. I used my URC9960 to learn My HP PC (Media Center) remote
2. Used IR.exe (V615) to download learnts with RDF (v1.23)
3. Key mapping with using Remote Master (v1.4)
4. After mapping, I copied the result and created device code in IR.exe
But when I pressed Ok to add this code, the error message appears. And I found this code doesn't work.
<My files reference>
IR learnt: http://www.bill.com.hk/ahpong/remote_pr ... _learnt.IR
Key Mapping with using Remote Master: http://www.bill.com.hk/ahpong/remote_pr ... earnt.rmdu

b.
I also have downloaded the existing code from http://www.hifi-remote.com/forums/dload ... le_id=1015
Then I use Keymap Master (v8.35) to convert it for supporting URC9960B01. After mapping, I copied the result and created device code in IR.exe
But when I pressed Ok to add this code, the error message appears. And I found this code doesn't work.

<My File Reference>
Keymap Master: http://www.bill.com.hk/ahpong/remote_pr ... center.xls

Who can help me?
Thanks

Regards,
Cavour Ahpong

[whompus]

Open that rmdu file in rm and change the protocol to mce, make device=4 and oem2=15

[Capn Trips]

Although you already have an answer, I would suggest it's better to post your KM upgrade (*.txt file) rather than the entire KM program (*.xls spreadsheet), since the entire spreadsheet is VERY BIG and challenging to download. In my case, I couldn't download it without errors that prevented manipulating the upgrade.

[johnsfine]

4. After mapping, I copied the result and created device code in IR.exe

That's the step you gave the least clear description of, and some of the steps before that are obviously correct (from the rmdu you posted). So that is the step that is likely wrong.

That step has several parts:

A) Select the ouput tab in RM

B) Select the devices tab in IR
C) Click the Device Upgrade COPY button in RM
D) Click the ADD button in IR
E) Paste with either ^V or the right-click menu
F) Click OK in IR

G) Select the protocols tab in IR
H) Click the Upgrade Protocol COPY button in RM
I) Click the ADD button in IR
J) Paste with either ^V or the right-click menu
K) Click OK in IR

You don't need that exact SEQUENCE of steps, but you need all those actions in some reasonable sequence.

Open that rmdu file in rm and change the protocol to mce, make device=4 and oem2=15

That doesn't matter. RC6-6-32 with device 128.3844 produces the same upgrade as MCE with device 4.15

[whompus]

I thought there was a slight change in the protocol upgrade.

It was most likely me not the apps. I could not get some of the toggles to work with upgrade build from a compaq mce remote with rc6-6-32 but did with mce.