Different protocol ID listed with RM vs. KM

jayerndl · Post by **jayerndl** » Sat Apr 28, 2007 1:45 pm

I am using the Pioneer DV-578a DVD player device upgrade in the files section. When I load the upgrade into KM v9.06 it displays protocol ID "00 7E" and no upgrade protocol required. BTW I have used this device upgrade and all functions seem to work fine. Since I have been trying to switch over to using RM, I loaded this same file into RM v1.77. It displays protocol ID "01 7E" and "Upgrade protocol Code ***REQUIRED***". Does anyone know what is going on? Why would the protocol ID's be different and why is an upgrade required for one but not the other? I have just started to use RM and I like it so far. Thanks.

Jay

Post by **ElizabethD** » Sat Apr 28, 2007 9:17 pm

I don't know much about Pioneer protocols, but in RM protocols.ini indicates that there are several of these Pioneer protocols and one name can well be an alias for another. I think KM does the same. I've seen it once.
BTW the current KM is 9.0.8.

mr_d_p_gumby · Post by **mr_d_p_gumby** » Sun Apr 29, 2007 12:56 pm

You don't mention which remote you are using, and that is relevant here. Because there are multiple incompatible versions of the 007E protocol executor in various remotes, and because it is likely that a user with several pieces of Pioneer equipment might need to use more than one version at the same time, Robman requested that the upgrade logic for this executor be handled in a special manner.

A simplified description of the logic is: if the target remote has a built-in 007E executor that is a different version and a protocol upgrade is required, then the protocol ID for the upgrade will be changed to 017E or 017F so that it will not conflict with another possible device upgrade that might be using the built-in executor.

The KM device upgrade in your link is set for the URC-8811, which indeed does show a required protocol upgrade using an ID of 017E. If you change the remote in KM to (for example) the URC-7200, you'll see that the ID changes back to 007E, and a protocol upgrade is not required. In this case, the URC-7200 has the correct (older) executor built-in.

Post by **The Robman** » Sun Apr 29, 2007 3:57 pm

But none the less, if RM and KM are in sync, they should create similar upgrades (ie, using the same PIDs).

Please do tell which remote you had selected in KM and confirm that you had the same remote selected in RM.

jayerndl · Post by **jayerndl** » Mon Apr 30, 2007 9:16 pm

The Robman wrote:But none the less, if RM and KM are in sync, they should create similar upgrades (ie, using the same PIDs).

Please do tell which remote you had selected in KM and confirm that you had the same remote selected in RM.

I am using a RS 15-1994 with both. Here's what I notcied. When I initially load the upgrade into both programs they both state: Protocol ID "01 7E". When I change the remote to the RS 1994 in KM the Protocol ID changes to "00 7E". When I change the remote to the RS 1994 in RM the Protocol ID stays the same. Just for kicks I tried several other remotes in RM and none of them changed the Protocol ID. BTW I am using the extender 5. RM allows me to specify extender 5, but KM does not (the drop down is grayed out). I haven't tried using the upgrade produced by RM (w/ the upgrade protocol). I have been using the upgrade produced by KM (w/out the upgrade protocol) with no apparent problems. It's a mystery. Thanks.

Jay

Post by **The Robman** » Mon Apr 30, 2007 9:24 pm

The version of $007E that's in the 15-1994 remote is the right one for DVD players, it's the one that you get when you select "Pioneer DVD" in KM. So, you shouldn't need a protocl upgrade for the 15-1994.

The version that's in newer remotes is called "Pioneer MIX".

jayerndl · Post by **jayerndl** » Tue May 01, 2007 7:43 am

The Robman wrote:The version of $007E that's in the 15-1994 remote is the right one for DVD players, it's the one that you get when you select "Pioneer DVD" in KM. So, you shouldn't need a protocl upgrade for the 15-1994.

The version that's in newer remotes is called "Pioneer MIX".

Can I just use the device upgrade code from RM, paste it into IR and ignore the upgrade protocol code? I am trying to get all my device upgrades converted over to RM and not use KM anymore. Thanks.

Jay

Post by **The Robman** » Tue May 01, 2007 7:48 am

If you use the upgrade generated by RM, you'll either need to also use the protocol upgrade that it gives you, or you'll need to manually edit the upgrade code so that it uses $007E rather than $017E or whatever PID it uses.

The other alternative is to review the protocols.ini file to make it in sync with KM.

jayerndl · Post by **jayerndl** » Tue May 01, 2007 7:58 am

The Robman wrote:If you use the upgrade generated by RM, you'll either need to also use the protocol upgrade that it gives you, or you'll need to manually edit the upgrade code so that it uses $007E rather than $017E or whatever PID it uses.

The other alternative is to review the protocols.ini file to make it in sync with KM.

How do you manually edit the upgrade code? Do you just change the protocol ID field on the device tab of IR after you paste the device?

Jay

Post by **ElizabethD** » Tue May 01, 2007 8:29 am

The Robman wrote:The other alternative is to review the protocols.ini file to make it in sync with KM.

I may regret meddling in this one, but here's my take:
KM and RM: except for remote-specific jumps, 017E for 88xx (upgrade required) is byte for byte identical to 007e for 15-1994 (upgrade not required)
[Pioneer DVD]
PID=00 7E
VariantName=1
AlternatePID=01 7E

MIX protocol translator are different, so the protocol is different anyway
[Pioneer MIX]
PID=00 7EAlternatePID=01 7F
VariantName=2

gfb107 · Post by **gfb107** » Tue May 01, 2007 9:29 am

OK, the issue here is between protocols.ini and the 15-1994 RDFs (and probably many others).

The 15-1994 RDFs state that the PID 007E with no variant name is built in.

In protocols.ini, the following protocols with PID 007E are defined:

Code: Select all

[Pioneer DVD]
PID=00 7E
VariantName=1
AlternatePID=01 7E
...

[Pioneer DVD2]
PID=00 7E
VariantName=2
...

[Pioneer MIX]
PID=00 7E
AlternatePID=01 7F
VariantName=2
...

[Pioneer MIX]
PID=00 7E
VariantName=3
AlternatePID=01 7F
...

Either the 1994 RDFs (and probably others) need to be updated to show that 007E:1 is builtin, or we need to change protocols.ini to remove make the variant current called 1 have no variant name.

Capn Trips · Post by **Capn Trips** » Tue May 01, 2007 10:57 am

jayerndl wrote:How do you manually edit the upgrade code? Do you just change the protocol ID field on the device tab of IR after you paste the device?

Jay

Whilst the experts debate/discuss how to correct the software to bring it into alignment/consistency, the answer to YOUR question is "Yes".

When you import the device upgrade, in IR's Add Device screen, after pasting in the upgrade code, manually alter the $01 $7E bytes at the beginning to $00 $7E. Import NO protocol upgrade, and you should be good to go.

Post by **The Robman** » Tue May 01, 2007 11:57 am

I've just checked all the RDFs that have variant 1 and they all have the $007E exec listed without a variant, so the easiest way to get this corrected would be to make variant 1 the "no variant" version.

On the other hand, there aren't that many remotes with variant1 installed, so it might be better in the long run to make variant 3 the "no variant" version as all future remotes will most likely have this version. If we go with this option, the RDFs for the var1 remotes will need to be updated.

Here's the way this exec is distributed among our remotes:

version1 (DVD - RM variant1):
15-1994
Cat48 (Outlaw, Anthem, etc)
Mil4 (B00, B01)
Replay (4dev)
URC-5650
URC-7200
URC-7560 B00
URC-7800

version2 (MIX - RM variant2):
Dreambox v1
Force EPG
RCU810
REM400 B00
URC-7541

version3 (MIX - RM variant2):
15-2103
15-2104
15-2107
15-2116
15-2133
Atlas4
Balboa Dolphin
Dreambox v2
Mil4 BJ8
Mundial4
REm400 B01
Replay 5000
Toshiba
URC-4080
URC-8060
URC-8811
URC-8910

version4 (4CMD - RM variant3):
15-2138
Atlas5
Dreambox Keyboard
URC-3440
URC-6131
URC-7562 B01
URC-8040
URC-9960 B00

version5 (4CMD - RM variant3):
URC-9960 B01

mr_d_p_gumby · Post by **mr_d_p_gumby** » Tue May 01, 2007 1:47 pm

The Robman wrote:IOn the other hand, there aren't that many remotes with variant1 installed, so it might be better in the long run to make variant 3 the "no variant" version as all future remotes will most likely have this version. If we go with this option, the RDFs for the var1 remotes will need to be updated.

It's not etched in stone, but I think the convention we've been following in the RDF files is to allow the first-discovered variant to be the "no variant" version. That's the rule I've been using when I generate updated [Protocols] sections, so I'd vote we change protocols.ini to make variant 1 be the "no variant" version.

Here's what my data shows:

Code: Select all

KM Ver  PID:variant  Remote                        CPU
    1   007E    Anthem                             S3C8
    2   007E:2  Atlas 4-Device                     S3C8+
    3   007E:3  Atlas DVR-PVR 5-Device             S3C8+
    3   007E:3  Atlas XL URC-1047                  SST
    1   007E    Ayre                               S3C8
    2   007E:2  Balboa Dolphin                     S3C8+
    3   007E:3  Comcast URC-1058                   SST
    3   007E:3  Comcast URC-1068                   SST
    2   007E:2  DirecTV Version 1                  M6805-RC16/18
    2   007E:2  DirecTV Version 2                  M6805-RC16/18
    2   007E:2  Dreambox - 1k version              S3C8
    2   007E:2  Dreambox V2                        S3C8
    3   007E:3  Dreambox V4                        HCS08
    2   007E:2  Force - 2k version                 S3C8
    2   007E:2  HT Pro                             S3C8+
    1   007E    Millenium 4-B00                    S3C8
    1   007E    Millenium 4-B01                    S3C8
    1   007E    Millenium 4-B04                    S3C8
    1   007E    Millennium 4-B00                   S3C8
    1   007E    Millennium 4-B01                   S3C8
    1   007E    Millennium 4-B02                   S3C8
    1   007E    Millennium 4-B04                   S3C8
    1   007E    Millennium4-4MXXXBJ8XXX            S3C8+
    2   007E:2  Mundial 4                          S3C8+
    1   007E    Outlaw Audio                       S3C8
    2   007E:2  Philips REM400                     S3C8
    2   007E:2  Philips REM400-B01                 S3C8+
    2   007E:2  RCA RCU810                         S3C8+
    2   007E:2  Replay 5000                        S3C8+
    1   007E    ReplayTV Version1                  S3C8
    1   007E    ReplayTV Version2                  S3C8
    1   007E    RS 15-1934 7-in-1                  P8/740
    1   007E    RS 15-1935 7-in-1                  P8/740
    1   007E    RS 15-1994 6-in-1 Smart            S3C8
    1   007E    RS 15-1995 7-in-1                  P8/740
    2   007E:2  RS 15-2103 1K Version              S3C8+
    2   007E:2  RS 15-2104 6-In-One AV             S3C8+
    2   007E:2  RS 15-2107 8-In-One Touchscreen    S3C8+
    2   007E:2  RS 15-2116                         S3C8+
    2   007E:2  RS 15-2117                         S3C8+
    2   007E:2  RS 15-2133 Kameleon 0.5k           S3C8+
    3   007E:3  RS 15-2138 Kameleon                S3C8+
    3   007E:3  RS 15-2144                         HCS08
    2   007E:2  Scientific-Atlanta AT2000          M6805-RC16/18
    2   007E:2  Toshiba CT90047 128b               S3C8
    3   007E:3  URC-3440 One for All 4             S3C8+
    2   007E:2  URC-4080 Video Expert              S3C8
    1   007E    URC-5650                           S3C8
    2   007E:2  URC-601x                           S3C8+
    3   007E:3  URC-6131 PVR Remote                S3C8+
    3   007E:3  URC-6690                           HCS08
    1   007E    URC-6800 Cinema                    S3C8
    3   007E:3  URC-6820                           HCS08
    3   007E:3  URC-6960                           S3C8+
    1   007E    URC-7200 Cinema 7                  S3C8
    2   007E:2  URC-7541 1K Version                S3C8+
    2   007E:2  URC-7544 1K Version                S3C8+
    1   007E    URC-7550 One for All               S3C8+
    1   007E    URC-7550-B00 One for All           S3C8+
    1   007E    URC-7552 One for All               S3C8+
    3   007E:3  URC-7555                           HCS08
    1   007E    URC-7560 One for All               S3C8+
    1   007E    URC-7560-B00 One for All           S3C8+
    1   007E    URC-7562 One for All               S3C8+
    3   007E:3  URC-7562-B01 One for All           S3C8+
    3   007E:3  URC-7780                           HCS08
    1   007E    URC-7800 Cinema                    S3C8
    2   007E:2  URC-801x                           S3C8+
    3   007E:3  URC-8040 4 Device Kameleon         S3C8+
    2   007E:2  URC-8060 Kameleon                  S3C8+
    1   007E    URC-8080-B02 Producer 8            P8/740
    1   007E    URC-8090-B02 Producer 8            P8/740
    3   007E:3  URC-8203                           HCS08
    3   007E:3  URC-8206                           HCS08
    1   007E    URC-8780 Producer 8                P8/740
    1   007E    URC-8800 Producer 8                P8/740
    2   007E:2  URC-881x                           S3C8+
    3   007E:3  URC-8820                           HCS08
    2   007E:2  URC-8910                           S3C8+
    1   007E    URC-9800 Producer 8                P8/740
    2   007E:2  URC-9910                           S3C8+
    3   007E:3  URC-9960 One For All Kameleon      S3C8+
    3   007E:3  URC-9960 B01 One For All Kameleon  S3C8+
    3   007E:3  URC-10820                          HCS08
    1   007E    Zap Station                        S3C8

gfb107 · Post by **gfb107** » Tue May 01, 2007 2:13 pm

OK, let's change protocols.ini

Look for a new RM release in the near future.