Alternate PIDs in RM

gfb107 · Post by **gfb107** » Wed May 26, 2004 7:44 am

I'm working on this now, and I've got some questions about the Panansonic Combos.

In my version of protocols.ini, I see the following combo executors:

Code: Select all

[Panasonic MIX Combo (*)]
PID=01 1F
...
Code.S3C80=45 91 82 8B 12 8F 45 08 08 00 DA 00 C6 00 DA 02 \
           7B 90 C9 06 D0 03 54 B0 C2 B0 C3 08 0C 90 C0 FB \
           07 87 43 03 97 42 03 2E 3E 37 25 05 37 37 02 8B EC \
           E6 10 04 E4 0B 07 E4 05 08 B4 06 08 B4 07 08 8D 01 \
           46

Code: Select all

[Panasonic VCR Combo]
PID=00 1F
...
Code.S3C80=45 91 42 8B 12 8F 45 08 08 00 DA 00 C6 00 DA 02 \
           7B 90 C9 06 D0 03 54 08 08 37 0E 06 18 05 77 17 \
           19 05 37 0C 06 18 06 77 1E 19 06 08 05 54 06 C0 \
           60 C0 B4 07 C0 09 08 8D 01 46
Code.740=0B 1B 42 80 0E C1 72 10 08 00 01 7D 02 9F 5F 02 \
         80 03 35 F7 62 02 6F 5F D7 62 02 FF 60 3C 06 69 \
         A5 60 45 5F 45 61 85 62 4C 00 FF
Code.6805-RC16/18=10 26 42 20 10 8F 45 08 08 00 6B 6E 01 6B 48 48 \
                  67 00 31 61 B4 0F 5F 02 16 5C 0D 5F 02 1F 5D B6 \
                  5C B8 5D B8 5E B7 5F CC 01 AF

Code: Select all

[Panasonic VCR Combo]
PID=00 1F
VariantName=8
...

Code: Select all

[Panasonic Mixed Combo]
PID=00 1F
VariantName=8
...
Code.S3C80=45 91 82 8B 12 8F 45 08 08 00 DA 00 C6 00 DA 02 \
           7B 90 C9 06 D0 03 54 0C 03 1C 02 93 C0 C2 04 0C \
           0C FB 03 83 C1 C2 EB F3 E4 0B 07 E4 05 08 B4 06 \
           08 B4 07 08 E0 10 8D 01 46

How do these 4 map to the 2 in Mike's truth table?

mr_d_p_gumby · Post by **mr_d_p_gumby** » Wed May 26, 2004 9:56 am

Here is what I think you should have, based on KM v8.22.
First, the original 001F version that uses 4 fixed bytes, and is only used by the VCR Combo

Code: Select all

[Panasonic VCR Combo] 
PID=00 1F 
... 
Code.S3C80=45 91 42 8B 12 8F 45 08 08 00 DA 00 C6 00 DA 02 \
           7B 90 C9 06 D0 03 54 08 08 37 0E 06 18 05 77 17 \
           19 05 37 0C 06 18 06 77 1E 19 06 08 05 54 06 C0 \
           60 C0 B4 07 C0 09 08 8D 01 46
Code.740=0B 1B 42 80 0E C1 72 10 08 00 01 7D 02 9F 5F 02 \
         80 03 35 F7 62 02 6F 5F D7 62 02 FF 60 3C 06 69 \
         A5 60 45 5F 45 61 85 62 4C 00 FF
Code.6805-RC16/18=10 26 42 20 10 8F 45 08 08 00 6B 6E 01 6B 48 48 \
                  67 00 31 61 B4 0F 5F 02 16 5C 0D 5F 02 1F 5D B6 \
                  5C B8 5D B8 5E B7 5F CC 01 AF

Next, the second 001F version (VariantName = 8 ) that uses 8 fixed bytes

Code: Select all

[Panasonic VCR Combo] 
PID=00 1F 
VariantName=8
... 
Code.S3C80=45 91 82 8B 12 8F 45 08 08 00 DA 00 C6 00 DA 02 \
           7B 90 C9 06 D0 03 54 B0 C2 B0 C3 08 0C 90 C0 FB \
           07 87 43 03 97 42 03 2E 3E 37 25 05 37 37 02 8B \
           EC E6 10 04 E4 0B 07 E4 05 08 B4 06 08 B4 07 08 \
           8D 01 46
Code.740=0B 1B 82 80 0E C1 72 10 08 00 01 7D 02 9F 5F 02 \
         80 03 35 A2 00 A0 00 06 66 90 06 B9 5D 00 95 5D \
         E8 C8 8A 43 03 98 73 EF 46 69 A5 65 85 61 45 60 \
         45 5F 85 62 4C 00 FF
Code.6805-RC16/18=10 26 82 20 12 8F 45 08 08 00 6B 6E 01 6B 48 48 \
                  67 00 31 61 B4 00 00 38 63 24 0A BE_76 E6 5A \
                  BE_75 E7 5A 3C_75 3C_76 04_75 03 07_76 EA 34_66 \
                  B6 62 B7 5E B8 5D B8 5C B7 5F CC 01 AF

And last, the same second 8-fixed-byte version used by the MIX Combo

Code: Select all

[Panasonic MIX Combo] 
PID=00 1F 
VariantName=8
AlternatePID=01 1F
... 
Code.S3C80=45 91 82 8B 12 8F 45 08 08 00 DA 00 C6 00 DA 02 \
           7B 90 C9 06 D0 03 54 B0 C2 B0 C3 08 0C 90 C0 FB \
           07 87 43 03 97 42 03 2E 3E 37 25 05 37 37 02 8B \
           EC E6 10 04 E4 0B 07 E4 05 08 B4 06 08 B4 07 08 \
           8D 01 46
Code.740=0B 1B 82 80 0E C1 72 10 08 00 01 7D 02 9F 5F 02 \
         80 03 35 A2 00 A0 00 06 66 90 06 B9 5D 00 95 5D \
         E8 C8 8A 43 03 98 73 EF 46 69 A5 65 85 61 45 60 \
         45 5F 85 62 4C 00 FF
Code.6805-RC16/18=10 26 82 20 12 8F 45 08 08 00 6B 6E 01 6B 48 48 \
                  67 00 31 61 B4 00 00 38 63 24 0A BE_76 E6 5A \
                  BE_75 E7 5A 3C_75 3C_76 04_75 03 07_76 EA 34_66 \
                  B6 62 B7 5E B8 5D B8 5C B7 5F CC 01 AF

I'm not sure where the p-code for your 4th item came from, but it appears to be a different coding of the second 001F version (3rd byte is 82). It probably is a duplicate of, or an early attempt at, the MIX Combo.

johnsfine · Post by **johnsfine** » Wed May 26, 2004 10:36 am

I put a bit of care and thought into constructing the protocols.ini entries for those Panasonic combos with the intent of using the built-in one whenever practical, but using the best available protocol upgrade when nothing built-in was available.

I hope I have time to review/explain what I did before one of you makes changes that may break it (but of course I'm not sure when I'll have time, and as usual I only focussed on the S3C80 models).

My first reaction is that I think it's a bad idea (assuming other factors leave you a choice) to have protocols.ini entries for two different versions of the same protocol name both provide code for the same CPU. Typically one version provides code for the single variant that should be used whenever no acceptable variant is present. The EARLIER entries should then provide info but not code for the inferior variants that should be used only if present.

gfb107 · Post by **gfb107** » Thu May 27, 2004 12:45 pm

OK, I'll leave the Panasonic entries alone, and we can come back to address those once you have more time to review/explain. For now, RM will not provide alternate PIDs for the Panasonic Combos.

gfb107 · Post by **gfb107** » Thu May 27, 2004 8:42 pm

Just to make sure.

Pioneer DVD2 and Pioneer MIX are really the same executor, but they should be handled differently in KM/RM. If one is present in a remote, the other is too. The difference is in how the device and command parms are presented to the user.

DVD2 should only be available when built into the remote.
MIX can be offered as a protocol upgrade, in which case PID 017F should be used.

For the new 007E:3 (KM versioning) that has been identified in the 9960 and Atlas remotes, is this also going to be offered in 2 flavors, or only as a MIX?

mr_d_p_gumby · Post by **mr_d_p_gumby** » Fri May 28, 2004 9:06 am

gfb107 wrote:For the new 007E:3 (KM versioning) that has been identified in the 9960 and Atlas remotes, is this also going to be offered in 2 flavors, or only as a MIX?

Presently in KM, 007E:3 is used interchangeably with 007E:2, so, yes, it is in both, and used when built-in in place of 007E:2. As I mentioned before, no one has had the time to see if this actually works, but then, no one has complained, either.

johnsfine wrote:Typically one version provides code for the single variant that should be used whenever no acceptable variant is present. The EARLIER entries should then provide info but not code for the inferior variants that should be used only if present.

I'm not exactly sure how you go about deciding which of the two Panasonic 001F versions is inferior, but based on what KM does, and what RM currently does, it looks like version 1 (4 fixed bytes) is preferred. So, simply omit the protocol code from the second VCR Combo, and RM will do what it does now. I checked this on remotes with both built-in versions (URC-8810, URC-9960 [RDF w/001F:8 added] ), and one with neither (Replay 5000).

One other issue between RM & KM is that KM calls the mix combo Panasonic MIX Combo, while RM calls it Panasonic Mixed Combo. In my previous message, I show the last item using KM's description, but perhaps it should retain RM's current description. (Also, Greg please note that I included updated protocol code in my post.)

Nils_Ekberg · Post by **Nils_Ekberg** » Tue Jun 01, 2004 5:40 pm

I just got back from my daughters wedding so I will sort out what Greg and Mike sent me plus this thread and will upload the complete set of RDF's shortly. Probably tomorrow.

Nils_Ekberg · Post by **Nils_Ekberg** » Wed Jun 02, 2004 6:12 pm

Gentlemen, I have a problem. I was going Through the RDF's that Mike and Greg sent me to incorporate the additional notes that I have from Mike and ran into some problems. For example I have 2 RDF's for the "6_80_2x2 (URC-881x_801x_601x x2 2k).RDF" with different entries for 007E and I am not sure who wins. It looks like every RDF that has 007E has the same difference. I have not come across anything else but will watch closely as I go through them.

Code: Select all

Greg's update

[Protocols]
0000, 0002:2, 000C, 000D, 0011, 0013, 0014, 001A, 001C, 001D,
001E, 001F, 0021, 0022, 0027:old, 0029, 002A, 0034, 0037, 0039,
003F, 0045, 0058, 005A, 005B, 005C, 005D, 005E:2, 005F, 0061,
0065, 006A, 0073, 007E:2, 0092, 009C, 009E, 00A4, 00AF, 00B6,
00C4, 00C5, 00C9, 00CA, 00CD, 00D0, 00DB, 00DE, 00E2, 00E8,
010F, 0111:2byte, 0114, 0184

Code: Select all

Mike's update

[Protocols]
0000, 0002:2, 000C, 000D, 0011, 0013, 0014, 001A, 001C, 001D,
001E, 001F, 0021, 0022, 0027, 0029, 002A, 0034, 0037, 0039,
003F, 0045, 0058, 005A, 005B, 005C, 005D, 005E:2, 005F, 0061,
0065, 006A, 0073, 007E:MIX, 0092, 009C, 009E, 00A4, 00AF, 00B6,
00C4, 00C5, 00C9, 00CA, 00CD, 00D0, 00DB, 00DE, 00E2, 00E8,
010F, 0111:2byte, 0114, 0184

Mark Pierson · Post by **Mark Pierson** » Wed Jun 02, 2004 6:53 pm

Just a guess, but since protocols.ini is using numeric values in the VariantName field, I'd say Greg's update wins!

johnsfine · Post by **johnsfine** » Wed Jun 02, 2004 6:59 pm

I think protocols.ini uses pretty arbitrary content in that field. It just happens that I named many of the variants for RM and I chose numbers in many cases.

I'm not sure which is (or should be) right.

gfb107 · Post by **gfb107** » Wed Jun 02, 2004 7:40 pm

The important thing is that the RDF entries match protocols.ini which means use my numeric values

I kept waffling back and forth, but I ended going with variant names that are consistent with KM's version numbers.

mr_d_p_gumby · Post by **mr_d_p_gumby** » Thu Jun 03, 2004 12:05 am

gfb107 wrote:The important thing is that the RDF entries match protocols.ini which means use my numeric values
I kept waffling back and forth, but I ended going with variant names that are consistent with KM's version numbers.

I went with what you posted earlier in this very thread regarding 007E. I don't have a preference for which variants you use. My RDFs had 007E:MIX and 007E:MIX6 as versions 2 and 3, respectively, because I thought your post meant that you were going to use those varant names in protocols.ini.

Sorry, Nils! Didn't mean to make extra work for you. I guess Greg & I got our wires (& RDFs) crossed...

mr_d_p_gumby · Post by **mr_d_p_gumby** » Thu Jun 03, 2004 12:50 am

I don't think you'll find any other PIDs that have different variant names between the two sets of RDFs. The ones I updated were:

0002 variants 2 and 5
001F variant 8
0027 variants 'old' and 'new'
005E variant 2
007E (which we've covered)
00CD variants 2 and 'sony' (which I explained in my notes)
00F8 variants 2 and 3
0111 variant 2

In my RDFs, 0027:old was omitted as it was considered the default, but there's no problem if the 'old' variant name is used.

Nils_Ekberg · Post by **Nils_Ekberg** » Fri Jun 04, 2004 7:01 pm

I uploaded version 1.17 of the RDF's and Images which includes the alternate PID support.

Hopefully after I sorted out the multiple changes and added Mike's additional changes I got it right. Could someone (Mike or Greg) check them out and let me know if I missed or messed up anything.

mr_d_p_gumby · Post by **mr_d_p_gumby** » Sun Jun 06, 2004 11:47 am

I haven't had the time to go through them in detail yet, but here are a few preliminary things.

1) You need to add the 00CD:sony variant to RS70RS70 (RS 15-1995 7 in 1 wTime & Extender Support).rdf

2) You've got two sets of Millennium 4 RDFs, with spelling as 'Millenium' and 'Millennium'.

3) A while ago, Rob posted his replacements for the Replay remotes. There still seems to be a lot of Replay RDFs, so maybe Rob can take a look & comment as to the validity of them.

4) The WAVUpgrade=Yes item will be interpreted in IR as applying to all remotes covered by the RDF, while not all of the remotes in the RDF will necessarily have the (mo)dem. For example, the 15-1925 has the capability, while I think the 15-1918 & 15-1919 do not. Since IR does not care which of the 3 remotes is actually connected, this might mean we need to create another RDF for the two remotes that don't have a (no-mo)dem.