JP1 Remotes

Doing my first device upgrade in KM, I've found that when I paste the code into IR the EFC's don't correspond to what I'd previously entered.

KM settings :-
Remote: URC-7560/7562,
Type: PVR, Setup code: 1284,
Protocol: RC-5, Device1: 8

Then I define a minimal set of keys to show the problem I'm having - just the digits 0-9. The EFC's are :-
173,205,109,141,045,077,237,013,172,204

This gives me :-
Upgrade Code 0 = 25 04 (PVR/1284) keymap-master Device Upgrade (KM v9.06)
E8 06 01 17 17 17
End

Then I run IR selecting remote "URC-7562-B01". Pasting the upgrade code I get this :-
VCR/DVD: 1284

# Key Name Hex Command EFC
1 0 50 144
2 1 80 014
3 2 40 016
4 3 C0 012
5 4 20 019
6 5 A0 015
7 6 60 017
8 7 E0 013
9 8 10 146
10 9 90 142
11 VOL+{Color+} [Not Mapped] [Not Mapped]
etc...

Observation one - if I change a single EFC, e.g. digit0 to 172 instead of 173, the upgrade string changes to this :-
Upgrade Code 0 = 25 04 (PVR/1284) keymap-master Device Upgrade (KM v9.06)
E8 00 81 17 17 17 DC F8 F4 F0 EC E8 E4 E0 DC D8
End
and that goes into IR just fine.

Observation two - If I select IR remote type "URC-7550/7552/7560-B01/7562 Silver" (signature EBV0EBV1) the first upgrade string also works fine. I've not tried uploading that to the remote as it's definetly a B01 - signature EM60EM60.

Thanks to anyone who can shed some light on this please?

Try this in IR It could be the 7562 in KM refers to the one with the EBV0EBV1 signature.

binky123 wrote:It could be the 7562 in KM refers to the one with the EBV0EBV1 signature.

Yes, the URC-7560 / 7562 selection in KM refers to the one with the EBV0EVB1 signature. KM never had the version with the EM60EM60 signature added.

RoboRat wrote:Observation one - if I change a single EFC, e.g. digit0 to 172 instead of 173, the upgrade string changes to this :-
Upgrade Code 0 = 25 04 (PVR/1284) keymap-master Device Upgrade (KM v9.06)
E8 00 81 17 17 17 DC F8 F4 F0 EC E8 E4 E0 DC D8
End
and that goes into IR just fine.

I'm sure the digit map tables are different between the two remotes, so KM is telling the upgrade to use the wrong one. Try binky's upgrade.

binky123 wrote:Try this in IR

Code: Select all

Upgrade Code 0 = 25 04 (PVR/1284) keymap-master Device Upgrade (KM v9.06)
E8 02 01 17 17 17
End 

It could be the 7562 in KM refers to the one with the EBV0EBV1 signature.

Thank you (and Mike), this does indeed work.

However..., that was a cut down version of the upgrade I'm attempting. When I paste the full thing, having edited the 06 into a 02 as above, there are other problems. I've uploaded the upgrade to the diag area :-
https://www.hifi-remote.com/forums/dload ... le_id=4240

The problem keys are :- Not as bad as before, these are just swapped around rather than completely wrong values. Is it possible for me to fix this in Keymap I wonder? What do I need to do?

Your remote sems to have a different keymap as the 7562 with the EBV0EVB1 signature. Therefor, the buttons are scrambled.

One solution is to go to the buttons sheet and sort the assignments by hand. Assign the function UP to the button PLAY, the function +10 to the button PAUSE and so on.

Uwe

I think I've got it! I had a look at the various hidden sheets within KM (not recommended I know, but true to the spirit of hacking, yes?) and discovered the instructions for adding new remotes in 'DevTypes'. I probably wouldn't have got much further if not for the fact there was already an entry for the very similar 7560/7562-B00.

In brief, I followed as much of the instructions as possible (a couple of the sheets are actually password protected) and created a new entry for 7562-B01, modifying this on the 'Buttons2' and 'URC' sheets to reflect the Buttons/ButtonMaps info in EM60EM60.rdf. Under 'DevTypes' I had to change KeyMoveStyle to 1. Under 'DigitMaps' I noticed the highlighted row on the sheet, row 95 (or row 92 according to column A) was value '06'. Changing that to '02' as per the originally suggested edit of the upgrade string had the same effect. I have no idea what the rest of this column does - is it documented anywhere? For now other than the change above it's the same as for the original 7560 entry.

And incredibly it all seems to work. The only deficency found so far is KM seems certain the RC5 protocol needs adding to the remote (it dosen't). I suspect that is something to do with the passworded sheets, but is otherwise causing no harm.

So the next question is, would anyone like a copy of these mods, and if so where and in what format? (zipped the .xls file is still over 800K)

And of course, many thanks to those responsible for these lovely tools!

You might want to give RM a try as it can handle new remotes by just reading the info from the RDF.

RoboRat wrote:So the next question is, would anyone like a copy of these mods, and if so where and in what format? (zipped the .xls file is still over 800K)

Put the (zipped) file in the Diagnostics file area, and post a link to it here. I'll take a look at what you've done and see if it is complete enough for me to integrate into the next release of KM.

mr_d_p_gumby wrote:

RoboRat wrote:So the next question is, would anyone like a copy of these mods, and if so where and in what format? (zipped the .xls file is still over 800K)

Put the (zipped) file in the Diagnostics file area, and post a link to it here. I'll take a look at what you've done and see if it is complete enough for me to integrate into the next release of KM.

Done. Link here :-
https://www.hifi-remote.com/forums/dload ... le_id=4245

binky123 wrote:You might want to give RM a try as it can handle new remotes by just reading the info from the RDF.

Thanks binky. I would have already except for the large download of the Java runtime I'll need (well, for dial-up access it is). Certainly looks like it would have side-stepped this problem.