Adding Slingbox support to RM

gfb107 · Post by **gfb107** » Mon Nov 28, 2005 1:02 pm

The Robman wrote:Greg, would you have any interest in expanding the binary capabilities of RM to also format "OBJ" files for the old 2000/3000 series ReplayTV units?

It's not as easy to add an OBJ file to your Replay as it is to add a bin file to your Slingbox, but the question just surfaced over at AVS so I thought I'd ask. If you're willing to do the RM part, I'll create the RDF.

The format of the binary file is very slightly different to the Slingbox format (probably because this is a much older UEI chip).

bytes function
0-0: offset of protocol code (zero if no protocol upgrade needed)
1-2: setup code in hex format
3+: standard JP1 device upgrade
??: optional protocol upgrade - S3C8(old)

The files have names like "S1005_OBJ" with no suffix.

Rob,

I'm finally going to have some time to work on this, so I wonder if you have some sample files I can use.

gfb107 · Post by **gfb107** » Fri Dec 02, 2005 6:28 am

I've upload a version of RM with OBJ file support at https://www.hifi-remote.com/forums/dload ... le_id=2502
From a user's perspective, it works just like the binary files for Slingbox.
You'll need to create an RDF with signature "BINOBJ" to try it out. Make sure to double check that I didn't break the slingbox-style binary support.

I decided not to use File->Open and File->Save for this, because RM wouldn't be able to save a different path for binary files.

Post by **The Robman** » Fri Dec 02, 2005 7:07 am

Thanks Greg, I'll try to get the RDF done soon and try it out.

Btw, did you ever get your Slingbox and if so, have you tried it out? Do you have any interest in adding a 6-pin connector? If you do, I'll write up how best to do it.

gfb107 · Post by **gfb107** » Fri Dec 02, 2005 7:58 am

No, I never did get a SlingBox. I do appreciate the effort you and Jeremy made to make one available, though.

I travel very rarely, and already use modulators for distributing my TiVos throughout the house, so decided I don't really have a use for it.

gfb107 · Post by **gfb107** » Tue Jan 17, 2006 8:34 am

Rob, you need to update the SlingBox RDFs with correct values for MaxCombinedUpgradeLength
Support for this has been in place since RM v1.37.

Post by **The Robman** » Fri May 19, 2006 9:32 am

Hey Greg,
I've just started work on a new version of the Slingbox that uses the "RV" chip from UEI. They're using a different encryption key than what they used for the "PL" chip. At first glance it appears that the only difference is the offset number that gets added into the mix. The number used for the PL box was 111 (as mentioned here) and the number used for the new RV box is 102.

I haven't verified how the "twist" is handled (ie, the two values that we ended up hard coding for). My guess is that one half of the pair will still be valid.

So, would it be possible to re-work your encryption class so that the offset number can be passed into it as an RDF parameter?

Here's how I think the "twist" should be handled. Let's pass in a hex value and a bit position as additional parms to the encyption routine.

So, the PL RDF entry would look something like this...

EncDec=EncrypterDecrypter(111,7D,1)

The first parm is the numeric password. This is the number that gets added to the result in the encryption process.

The second parm is the un-encrypted value that needs to have a bit flipped.

The third parm is the bit that needs to be flipped. (zero based)

So, when the encryption routine finds an un-encrypted value where all the bits, except the bit specified in parm3, match the value specified in parm2, the routine should flip the bit specified in parm3.

Thefore if un-encrypted hex codes 7D or 7F are found, bit1 should be flipped before the value is passed into the encryption routine.

The same is true in reverse. If you are decrypting a "PL" hex code and the result matches 7D or 7F, you should flip bit1 in the final result.

Post by **The Robman** » Fri May 19, 2006 4:48 pm

As a stop gap I have created a RVEncrypterDecrypter.java file, does anyone know how I can convert it into a class and include it with RM?

https://www.hifi-remote.com/forums/dload ... le_id=3230

gfb107 · Post by **gfb107** » Sun May 21, 2006 2:55 pm

I'll assume you have the Java SDK installed.
Open a command line, and cd to the folder in which you've installed RM.

Code: Select all

mkdir com\hifiremote\jp1
set classpath=.;RemoteMaster.jar
move RVEncrypterDecrypter.java com\hifiremote\jp1
javac com\hifiremote\jp1\RVEncrypterDecrypter.java
jar -uf RemoteMaster.jar com\hifiremote\jp1\RVEncrypterDecrypter.class

Post by **The Robman** » Sun May 21, 2006 3:19 pm

gfb107 wrote:I'll assume you have the Java SDK installed.
Open a command line, and cd to the folder in which you've installed RM.

I don't yet, but I will to see if I can get this working. In the meantime, what do you think of the idea of making the Encryption routine parm driven?

gfb107 · Post by **gfb107** » Sun May 21, 2006 4:11 pm

Making the encryption routine parm driven is fine with me.

Post by **The Robman** » Sun May 21, 2006 4:13 pm

OK, I've installed jdk1.5.0_06, do I need to do anything to run it? I ask because when I try to follow those steps, it doesn't recognize "javac" as a program.

gfb107 · Post by **gfb107** » Sun May 21, 2006 4:54 pm

You've got to add the bin folder to your path.

Post by **The Robman** » Sun May 21, 2006 5:47 pm

How do I do that?

gfb107 · Post by **gfb107** » Sun May 21, 2006 6:07 pm

Here are some different ways:

From the command line, for just one session:
set PATH=%path%;c:\j2sdk1.4.2_08\bin

OR
Control Panel -> System (or right click My Computer and select Properties)
Advanced tab
Environment Settings
Decide if you want to add it to just the current user, or make it system wide.
The variable name is PATH and you want to add it at the end of the current value (if there is one), using a semi-colon to separate it from the current value.

Post by **The Robman** » Sun May 21, 2006 7:30 pm

Thanks. Back in the days of AUTOEXEC.BAT I knew how to do that. I'm guessing that I need to reboot to make it take effect as it didn't make any difference right off the bat.