Page 2 of 5

Posted: Fri Aug 04, 2006 7:46 pm
by jetskier
oops, forgot protocol.

RM upgrade

IR

Posted: Sat Aug 05, 2006 9:16 am
by jetskier
I also rebuilt the RECS80 (90) protocol and it responds to my device, but the button mapping doesn't match the response. I could just be that the protocol timing for th HCS08 is off.

I'm going to learn the commands in another remote and see what the mapping is.

zip files with IR and RM

The IR file contains only the learned signals from a second remote
The RM file contains the mapping on the 10820 transformed from my old 8810w.

Posted: Sat Aug 05, 2006 10:25 am
by gfb107
I don't know what "rebuilt the RECS80 (90) protocol" means.

There are only 2 ways for the buttons to get scrambled:

1. Maybe the versions of these protocols present in the JP1.2 remotes have a different number of fixed bytes.

2. Maybe we've made a mistake with the button maps as defined in the RDF file.

Posted: Sat Aug 05, 2006 10:51 am
by jetskier
Sorry. I didn't rebuild the protocol. I simply rebuilt the RM file using this protocol. My mistake.

Posted: Sat Aug 05, 2006 10:53 am
by jetskier
How are the button maps generated any way?

Posted: Sat Aug 05, 2006 11:57 am
by gfb107
I think the problem is that the 108020 (and probably other JP1.x remotes) uses a different version of these protocols. I say that because it looks like support for these new versions was added to KM v9.01, as stated here. I missed that.

Re: Issues w/ IR 7.0 beta 2

Posted: Sat Aug 05, 2006 12:02 pm
by gfb107
jkoopman wrote: 3) Can't include any Keymoves in a Device Upgrade. When I design an upgrade in KM-v9.01 and include some keymoves, and then attempt to add that Device to IR via an "Add" and Paste I get the following errors/overflows after pressing the "OK" button on the Device Upgrade Window:

"The Fav/Scan list contains too many entries. The will be truncated." (over and over again)

"Key Move/Macro overflow. There is more data in your key move/macro section than can be stored in the remote. You must remove some key moves, macros, or scans."

This is with no previous key moves stored, and the key moves that are loaded are badly scrambled.

Example Device Upgrade w/ Keymove:

Upgrade Code 0 = 57 24 (Misc Audio/1828) Roku Soundbridge (KM v9.01)
5A 00 9E 9C BA EF 00 09 00 19 85 05 F9 79 B9 39
D9 59 99 97 67 C7 27 A7 A7 27 07 17 47 57 D7 B7
37 F7 77 BD E7 87
KeyMoves
04 F4 50 0D 00 37«=amp/0013 vol+: Pioneer Amp V
olume Up»¦05 F4 50 0D 00 3B«=amp/0013 vol-: Pion
eer Amp Volume Down» ¦08 F4 50 0D 00 77«=amp/001
3 mute: Pioneer Amp Volume Mute» ¦BF F4 57 24 00
A4«discrete off: Discrete Power Off» ¦BC F4 57
24 00 AB«discrete on: Discrete Power On»
End
Looks to me like KM is formatting the keymoves incorrectly for this remote. JP1.x remotes use the long format for keymoves, where the keymove length is stored in its own byte, as described here.

Posted: Sat Aug 05, 2006 5:09 pm
by gfb107
Note that RM has a problem with this too. It handles keymoves generated because you've assigned functions to buttons outside the button map correctly. It does not handle keymoves generated because you've assigned external functions (from another setup code ) to buttons.

Posted: Sat Aug 05, 2006 8:23 pm
by gfb107
I'm working on fixes for these issues.

Here's an upgrade generated for the Dish Network PVR 942:

Code: Select all

Upgrade code 0 = 46 EF (PVR/1775) DishNetwork PVR 942 (RM v1.63a)
 02 62 3E FE FE EC E1 00 80 80 00 00 68 78 08 0C
 84 C4 C8 80 7C 2C 68 78 70 60 48 40 98 00 50 DC
 D8 6C 98 94 E4 EC E8 F4
KeyMoves
 83 F0 04 46 EF 00 52«power»¦
 23 F0 04 46 EF 00 B3«Page up»¦
 24 F0 04 46 EF 00 B2«Page down»¦
 3F F0 04 46 EF 00 F2«Discrete On»
End
Here's the Roku upgrade:

Code: Select all

Upgrade code 0 = 57 24 (Misc Audio/1828) Roku Soundbridge (RM v1.63a)
 5A 00 9E 9C BA EF 00 09 00 19 85 05 F9 79 B9 39
 D9 59 99 97 67 C7 27 A7 A7 27 07 17 47 57 D7 B7
 37 F7 77 BD E7 87
KeyMoves
 04 F0 04 50 0D 00 37«Pioneer Amp Vol+»¦
 05 F0 04 50 0D 00 3B«Pioneer Amp Vol-»¦
 08 F0 04 50 0D 00 77«Pioneer Amp Mute»¦
 BB F0 04 57 24 00 AB«discrete on: Discrete Power On»¦
 BF F0 04 57 24 00 A4«discrete off: Discrete Power Off»
End
Please let me know how these work for you.

Posted: Sat Aug 05, 2006 11:10 pm
by jetskier
gfb107 wrote:I'm working on fixes for these issues.

Here's an upgrade generated for the Dish Network PVR 942:

Code: Select all

Upgrade code 0 = 46 EF (PVR/1775) DishNetwork PVR 942 (RM v1.63a)
 02 62 3E FE FE EC E1 00 80 80 00 00 68 78 08 0C
 84 C4 C8 80 7C 2C 68 78 70 60 48 40 98 00 50 DC
 D8 6C 98 94 E4 EC E8 F4
KeyMoves
 83 F0 04 46 EF 00 52«power»¦
 23 F0 04 46 EF 00 B3«Page up»¦
 24 F0 04 46 EF 00 B2«Page down»¦
 3F F0 04 46 EF 00 F2«Discrete On»
End
It's a step in the right direction. The 942 responded to this upgrade, but the buttons were not mapped correctly. I.e. the 8 and 3 were swapped-all the other numbers worked. The guide button went to the dvr events screen. The PIP worked (on/off, swap, move). The record button initiated the info command. The list goes on.

The good thing is it responded. I wish I knew how a 40 byte upgrade translates to all these functions. Must be that fancy hex math. I must have missed that readme.

Thanks for working on this.

Posted: Sun Aug 06, 2006 5:49 am
by gfb107
I just realized that the upgrade you originally posted was a SAT mode upgrade, but I gave you a PVR mode upgrade. How did you handle that difference? If you changed the device type of the upgrade in IR, that would cause buttons to get shuffled.

Posted: Mon Aug 07, 2006 2:34 pm
by jkoopman
gfb107 wrote:I'm working on fixes for these issues.

Here's the Roku upgrade:

Code: Select all

Upgrade code 0 = 57 24 (Misc Audio/1828) Roku Soundbridge (RM v1.63a)
 5A 00 9E 9C BA EF 00 09 00 19 85 05 F9 79 B9 39
 D9 59 99 97 67 C7 27 A7 A7 27 07 17 47 57 D7 B7
 37 F7 77 BD E7 87
KeyMoves
 04 F0 04 50 0D 00 37«Pioneer Amp Vol+»¦
 05 F0 04 50 0D 00 3B«Pioneer Amp Vol-»¦
 08 F0 04 50 0D 00 77«Pioneer Amp Mute»¦
 BB F0 04 57 24 00 AB«discrete on: Discrete Power On»¦
 BF F0 04 57 24 00 A4«discrete off: Discrete Power Off»
End
Please let me know how these work for you.
This worked perfectly to load Keymoves as part of a device upgrade for a URC-10820 into IR.exe, sounds like this issue is resolved for RM.

Sorry for a newbie question, how do I communicate this fix to the current KM developer?

Thanks for the quick response!

Posted: Mon Aug 07, 2006 3:34 pm
by The Robman
jkoopman wrote:Sorry for a newbie question, how do I communicate this fix to the current KM developer?
You don't need to, he'll see it here.

Posted: Mon Aug 07, 2006 7:16 pm
by mr_d_p_gumby
jkoopman wrote:...for a URC-10820...
Sorry for a newbie question, how do I communicate this fix to the current KM developer?
Thanks for the concern. KM v9.01 does not support the new style of keymoves used in the URC-10820 (and in fact is generating old-style keymoves). We've been working on this, and it will be fixed in the next release.

Posted: Wed Aug 16, 2006 10:50 pm
by jetskier
Here's the fix for the Dish Network Protocol on my URC-10820. I changed the Fixed Data for the Dish Network PID=00 02 to 00 00 00 00 00 rather than 00 80 80 00 00 in the protocols.ini file. There are different variants of the Dish Network protocol in the file. I edited the first one listed. I don't know how it affects the other two variants. The code for the S3C80 is listed in all three, but the other code seems to address the other processors. On edit, I farted around with the Remote Address and ended up changing the DevParms, DeviceTranslator and the CmdTranslator to match the Dish Network with Variant Name=2. I don't know what I did, but it seems to work great on all three of my Sat boxes on three different addresses. All the buttons are mapped correctly for my upgrade. I can't say this works backwards on the older JP1 upgrades.

Updated Dish Network Section of my protocol file:

Code: Select all

[Dish Network] 
PID=00 02 
OldNames=Dishplayer (old) 
DevParms=Remote Address (1 to 32) :5=1,Device Code:5=0 
DeviceTranslator=Translator(lsb,0,5,0,0,-1)
CmdParms=OBC:6=0 
CmdTranslator=Translator(0,6)
Notes=Standard SAT/0775 is Unit 0 / Device 0 \ 
\n\n\ 
Device, Unit and OBC are all incompatible with KM (version 7.34) \ 
They are compatible with DecodeIR.dll as Device.Unit:OBC \ 
EFC values are compatible with KM within the same model remote. \ 
EFC values are compatible across models of remote for the default unit \ 
number and in some cases for other unit numbers. 
FixedData=00 00 00 00 00 
Code.S3C80=2B 5C 11 8B 12 B5 05 08 08 00 C5 03 32 00 C5 05 \ 
           73 00 00 00 C5 0B F2 8D 01 46 
Code.6805-C9=06 0E 21 20 12 B8 72 17 05 06 03 18 04 99 02 A3 \ 
             17 08 E9 00 04 01 29 07 5B 08 B6 75 B7 6E B6 76 \ 
             B7 6F 33 5A 3C 59 CC 01 83 
Code.6805-RC16/18=0B 18 11 20 10 B5 45 07 08 01 62 A3 02 62 C4 02 \ 
                  C4 00 06 62 03 CC 01 AF 
Code.740=06 0D 11 80 0E B0 72 17 08 07 03 19 04 9A 02 46 \ 
         17 08 EC 44 5D 4C 00 FF
Here's my working test upgrade on remote address 1 (default):

Code: Select all

Upgrade code 0 = 46 EF (PVR/1775) DishNetwork PVR 942 (RM v1.63)
 02 62 3E FE FE EC E1 00 00 00 00 00 68 78 08 0C
 84 C4 C8 80 7C 2C 68 78 70 60 48 40 98 00 50 DC
 D8 6C 98 94 E4 EC E8 F4
KeyMoves
 23 F0 04 46 EF 00 B3«Page up»¦
 24 F0 04 46 EF 00 B2«Page down»¦
 3F F0 04 46 EF 00 F2«Discrete On»¦
 40 F0 04 46 EF 00 AE«Discrete Off»
End
On another note, RM seems to be broke when trying to save preferred remotes in the list. It doesn't seem to save the list. Also, when you exit, it prompts to save as it should. If you click "cancel" rather than "yes" or "no", it exits without returning back to the program.