JP1 Remotes

Posted: **Fri Oct 07, 2005 4:10 pm**

Hey Greg,
I just discovered that I had put a non-working beta version of my Lutron protocol code in KM, and that's probably what you copied for RM.

If so, you should replace it with the correct version.

This is the bad version that was in KM:

Upgrade Protocol 0 = 00 E7 (S3C8+)
3E 85 12 8B 12 8D 05 08 08 04 78 00 00 00 00 04
66 11 CB 23 C0 00 00 8D 01 46
End

This is the working version:

Upgrade Protocol 0 = 00 E7 (S3C8+)
3F 85 22 8B 0E 8F 01 08 08 04 78 00 00 00 00 04
66 11 CB 8D 01 46
End

Posted: **Sat Oct 08, 2005 10:36 am**

Yes, the bad version is in protocols.ini.

Are there corrected versions for the other processors?
Here are the current entries in protocols.ini:

Code: Select all

Code.S3C80=3E 85 12 8B 12 8D 05 08 08 04 78 00 00 00 00 04 66 11 CB 23 C0 00 00 8D 01 46
Code.740= 0B 17 22 80 0B E0 40 5B 08 08 01 01 03 E8 08 EF 4C 00 FF
Code.6805-C9=0B 18 22 20 0B E0 40 5B 08 08 01 01 03 E7 0C C3 3F 7D CC 01 83
Code.6805-RC16/18=10 22 22 20 11 8E 01 08 08 20 3B 00 F2 FF 3D 08 EF 00 00 00 00 00 CC 01 AF

Posted: **Sat Oct 08, 2005 10:46 am**

I see that they both use 2 fixed bytes, which is a good sign. That means that I created those using PB and they are the most recent versions.

Posted: **Sat Oct 08, 2005 10:47 am**

Posted: **Sun Oct 09, 2005 7:41 pm**

Hey Greg,
I think it would be a good idea to treat the Lutron exec as a mini-combo because of the 2 bits of the device code that end up in the variable data (after encrpytion). I took a look at the various device codes used by Lutron and the always come in groups of 4 where the two LSBs of the first device code are 00, so my thinking was to have the user enter the lowest device code number (from the group of 4) and then enter 1 thru 3 in the byte2 column to indicate that they want to use one of the other 3 device codes.

In RM you could get more creative. Regardless of which device code the user enters, you could use it to determine the correct group of 4 device codes and make them available via a drop down when the user enters the functions and OBCs.

What do you think?

Posted: **Mon Oct 10, 2005 5:23 pm**

Sounds good to me.

That'll take a custom translator, like the OBC>63 setting for RC-5.

So, on the Setup tab in RM, the user could choose 0-3, 4-7, etc.
Then, on the Functions, the user could choose from the 4 valid values 0, 1, 2, or 3 (for 0-3).

Posted: **Mon Oct 10, 2005 5:46 pm**

This isn't like the RC-5 thing. With RC-5 one of the bits of the OBC is buried in the fixed byte, whereas in this case, 2 of the device code bits end up in the variable data.

So what I'm suggesting is this: For KM, if the user enters a device code that is evenly divisable by 4, I will open up the byte2 column and let them type in a number in the range 0-3, then I'll add that number to the device code that was entered for that function. (In reality I'll simply get the last 2 bits of the device code from the byte2 column rather than from the entered device code).

For example, if the user enters 140 as the device code, they can use byte2 to get device codes 140 thru 143.

For the KM version, if the user were to enter 141 as the device code, as this is not evenly divisable by 4, I would turn off the byte2 column.

For the RM version, you should let the user enter any device code, and then RM can calculate the valid range, so if the user entered 141, RM could determine that the valid range is 14 thru 143 and offer this as a drop down menu choice for each function.

Posted: **Tue Oct 11, 2005 11:59 am**

Rob, here's a test version of RM to try.

Posted: **Tue Oct 11, 2005 12:17 pm**

Thanks Greg, I'll give it a whirl from home.

Posted: **Thu Oct 13, 2005 7:01 am**

Rob, did you get a change to try this out?

Posted: **Thu Oct 13, 2005 9:45 am**

Sorry no, I haven't had a chance yet. I haven't had time to make the KM changes either.

Posted: **Wed Oct 19, 2005 1:39 pm**

Bump.

Posted: **Wed Oct 19, 2005 3:51 pm**

I didn't forget about you Greg, I just spent all of my remote time over the weekend working on getting the final encryption formula for the PL Slingbox. Btw, did you see my note about the "export bin" function not working in RM v1.37? I checked it yesterday using v1.36 and it works, so it's a very recent bug. When I test the Lutron changes, I will verify whether it works in the beta version.

Posted: **Wed Oct 19, 2005 4:25 pm**

I've found the bug, and wanted to release the fix along with the Lutron changes.

Posted: **Wed Oct 19, 2005 7:44 pm**

Parent Teacher Conferences meant that I had no time this evening, hopefully tomorrow.