menu button mystery

[mr_d_p_gumby]

2. The KM upgrade code reads: Upgrade Code 0 = 13 AC (TV/0940) keymap-master Device Upgrade (KM v8.39)
3. When the same NECx2 is being rebuilt in RM, Upgrade code resolves to: Upgrade code 0 = 03 AC (TV/0940) (RM v1.54)

I don't have time to dig into this now, but it does appear that KM is not in agreement with the RDF as to device numbering. Maybe try using RM until this is corrected.

And what does it mean in KM "DigitMap enabled" I can never remember that one.

It means that the upgrade is using a table of function codes built into the remote for the numeric buttons.

[Ube_Astard]

When you say "the numeric buttons don't work", does that mean they are sending the wrong signal (for example 0 sends 6, or 1 send 4, or 7 sends 9) or that you get no reaction from the device at all?

Some other thoughts on trouble shooting this:

• Use your 9910 to learn the signals being sent by the 7544, and examine those to see if they are what we think they should be.
• Convert your upgrade for use with the 9910 and install it there, and see if it works correctly.

The 7544 is sending signals from the numeric buttons. I tried learning the signals from the 7544 as you have suggested and very, very strange, the OBCs and EFCs have all changed. Why would that happen?
Next thing to do is try it in RM, but does anyone understand what is happening here?[/i]

[gfb107]

Have the OBCs/EFCs been changed, or just shuffled?

If they've been shuffled, it probably means that we don't have the button maps defined correctly in KM and/or the RDF (which both IR and RM use).

Please provide details as to which buttons send which OBC/EFC, as well as which OBC/EFC the button should be sending.

Are the numeric buttons the only ones that have been shuffled?

[The Robman]

The 7544 is sending signals from the numeric buttons. I tried learning the signals from the 7544 as you have suggested and very, very strange, the OBCs and EFCs have all changed. Why would that happen?[/i]

I'm betting that if you look on the Setup sheet in KM you will see the words "Digitmap Enabled".

Practically all JP1 remotes have a feature where you can use less memory by using a pre-defined set of codes for the numeric buttons. The codes that you have entered seem to have matched one of the pre-defined sets of codes, so KM has tried to use the preset code instead of the indivudual button codes.

However, either because of a bad remote selection on your part, or a bug in KM, the preset codes doesn't really match what you have entered.

As a temporary solution, change the function assigned to the "0" button. Make a note of what the hex code was before the change and what it is after the change, then after you've copied the upgrade code over to IR, look for the new hex code and change it to the old hex code.

[gfb107]

When I import the KM upgrade into RM, RM doesn't use a digitmap, even though KM does.

Here's the device upgrade code that RM generates:

Code: Select all

Upgrade code 0 = 13 AC (TV/0940) keymap-master Device Upgrade (RM v1.61)
 5A 00 F4 FE 4A 81 31 1F 1F 77 DF 5F 9F EF 6F AF
 CF 4F 8F 1F 2F 0F B7 F7 BF 3B A7 4B F9 79 59 B9
 E9 D7 57 C9 97
End

Here's the KM device upgrade:

Code: Select all

Upgrade Code 0 = 13 AC (TV/0940) keymap-master Device Upgrade (KM v8.40)
 5A 10 74 FE 4A 81 31 1F 1F 1F 2F 0F B7 F7 BF 3B
 A7 4B F9 79 59 B9 E9 D7 57 C9 97
End

[Ube_Astard]

Thanks gfb and Robman. Does that mean I should use KM to solve this?

[Capn Trips]

Thanks gfb and Robman. Does that mean I should use KM to solve this?

On the contrary, the indications from this thread would suggest that RM is the way to go.

[Ube_Astard]

On the contrary, the indications from this thread would suggest that RM is the way to go.

Sorry, thats what I meant. Will try it tonight.
Do I just load the upgrade in RM and save it, or do I have to build the upgrade from scratch in RM?

thanks

[Ube_Astard]

I tried loading it up in RM and saving it but it doesnt solve the problem. Does it have to be built in RM them?

[Capn Trips]

3. When the same NECx2 is being rebuilt in RM,

Well, based on the above, I think since KM is messing it up, you need to BUILD it in RM, not just open the faulty KM upgrade with RM.

[The Robman]

I tried loading it up in RM and saving it but it doesnt solve the problem. Does it have to be built in RM them?

I think we'd need to see some evidence. Greg has already demonstrated that KM does use the digitmap and RM doesn't, for this upgrade, so there shouldn't be a problem using RM.

Please...
1) Cut and paste the generated upgrade here.
2) Post the RM file, and
3) Post your IR file

[ElizabethD]

Perhaps it doesn't work because of trying to import the entire KM upgrade into RM? Importing KM upgrade in this instance doesn't seem good to me, but you still can save some typing.

Do I just load the upgrade in RM and save it, or do I have to build the upgrade from scratch in RM?

Assuming that the OBC numbers YOU entered in KM in the Functions sheet are correct, use copy/paste.
In KM, make sure OBC column is next to the function names.
Select just the two columns and just the rows where you have entries.
Copy and paste into Notepad.
Fire up RM, and paste the data onto the Functions sheet.
Make sure on the Setup sheet you have the correct remote, device type, protocol.

From RM Help file

Paste the contents of the clipboard into the selected cell. This can also be accomplished using the context menu, by right-clicking on the cell in which you want to pasted, and selecting Paste. This can be useful for copying columns of information from KM to RM.

[Ube_Astard]

Actually guys and thanks to Robman, I was about to post the upgrade when I noticed my RM figures were different to gfb107's. Then I noticed he was using a newer RM (I dont use it so never downloaded the latest one). I downloaded the new file and now everything works perfect. Thanks to all for looking at this and helping me solve it.