I've been messing with my new Slingbox and have been creating upgrades for it. To do this, I've been using RM with a fake RDF that I created.

Once the upgrade is created, I then use a spreadsheet that I wrote called UPGRADE-to-BIN.xls to format the data ready to be converted back to binary. (Just FYI, I'm using the binconvert program to convert the binary files to text, and vice versa).

So, how much work do you think it would be for RM to be able to import a Slingbox binary file as an upgrade so the user could edit it? Then, once the new upgrade has been formatted, would it be possible for the user to be able to export the upgrade as a pre-formatted binary file?

There's another twist though, there are 2 formats for the binary files, the "PL" version is encrypted whereas the "JU" version is not.

Just FYI, I haven't determined which protocols are built into the Slingbox's UEI chip yet, so the [Protocols] section of the fake RDF that I created is still blank.

The Slingbox is still a very new product, but I can see it gaining popularity quite quickly, so it would be cool to be able to offer JP1 functionality to the Slingbox users as I know some of them are frustrated by the "remote control" functionality offered, as they don't have the ability to program keymoves or anything like that, so if a button is missing, or incorrectly programmed, they are SOL._________________Rob
www.hifi-remote.comPlease don't PM me with remote questions, post them in the forums so all the experts can help!

Last edited by The Robman on Sat Aug 27, 2005 9:23 am; edited 1 time in total

Under the advanced menu, there is an "Import Binary Upgrade..." item. It displays a File Open Dialog, allowing you to select the Binary upgrade you want to import. There are three allowed file types:

All binary upgrade files (*.bin)

Unencrypted binary files (*_ju.bin)

Encrytped binary upgrade files (*_pl.bin)

Note that it will use the currently selected remote when importing a binary upgrade, since the binary upgrade doesn't specify what remote it is for.

BTW, the fact that these binary upgrade files can include both the device upgrade and the protocol upgrade, got me thinking about how RM/KM and IR work together. One of the little things beginners sometimes get stuck on is that they forget to add the protocol upgrade along with the device upgrade. It occurs to me that we could maybe cut down on these problems if the protocol upgrade were included with the device upgrade, in much the same way that we currently bundle keymoves with the device upgrade. This would allow the user to transfer everything to IR in one step.

It occurs to me that we could maybe cut down on these problems if the protocol upgrade were included with the device upgrade, in much the same way that we currently bundle keymoves with the device upgrade. This would allow the user to transfer everything to IR in one step.

I actually suggested this to Mark Pauker back when we were working on the combined Key Moves. He said that IR would require some significant modifications to allow for the inclusion of protocol upgrade code in the same data block, so we let it die._________________Mark

I actually suggested this to Mark Pauker back when we were working on the combined Key Moves. He said that IR would require some significant modifications to allow for the inclusion of protocol upgrade code in the same data block, so we let it die.

Thanks Greg, I will try this as soon as I get home. Regarding the selected remote, I hate hard-coding, but since the Slingbox is the only "remote" that uses these binary files (at this time, at least) is there anyway to force RM to select the Slingbox RDF? Of course, if we discover other devices that have similar UEI chips on board (and therefore use similar binary files) we would need to come up with something morre elaborate down the road.

Regarding the protocol upgrades, I do see your point and pretty much agree with it, though if IR were to be modified to support this feature, it would also have to handle the fact that the protocol may already be installed.

My long term vision is to have one integrated application that will handle all the functionality of KM, RM and IR, so if and when that is ever realized, this will become a moot point._________________Rob
www.hifi-remote.comPlease don't PM me with remote questions, post them in the forums so all the experts can help!

Regarding the selected remote, I hate hard-coding, but since the Slingbox is the only "remote" that uses these binary files (at this time, at least) is there anyway to force RM to select the Slingbox RDF?

It would not be difficult to hard-code this. Probably not even 5 lines of code.

Quote:

Of course, if we discover other devices that have similar UEI chips on board (and therefore use similar binary files) we would need to come up with something more elaborate down the road.

It seems reasonable to me that the user should select the correct remote before importing the binary upgrade. If, however, you really think that we need something more elaborate, I have an idea that might work and be reasonable easy to code.

Regarding the selected remote, I hate hard-coding, but since the Slingbox is the only "remote" that uses these binary files (at this time, at least) is there anyway to force RM to select the Slingbox RDF? Of course, if we discover other devices that have similar UEI chips on board (and therefore use similar binary files) we would need to come up with something morre elaborate down the road.

Sounds like a new RDF entry might be best. It could be something in the General section like "UseBinary=Yes|No"._________________Mark

It seems reasonable to me that the user should select the correct remote before importing the binary upgrade. If, however, you really think that we need something more elaborate, I have an idea that might work and be reasonable easy to code.

I'm concerned about how RM would import the code if anything other than the Slingbox remote was selected. There will be way too many button codes than there are buttons to associate them with if any other remote was selected.

In the short term, I am going to be the only user, so it's no problem for me to pre-select the Slingbox remote, but once we open this up to Slingbox users, I'd like to have something in place where the Slingbox RDF is automatically selected._________________Rob
www.hifi-remote.comPlease don't PM me with remote questions, post them in the forums so all the experts can help!

I'm concerned about how RM would import the code if anything other than the Slingbox remote was selected. There will be way too many button codes than there are buttons to associate them with if any other remote was selected.

Of course the upgrade will be imported incorrectly (meaning functions will have the wrong names, and be assigned to the wrong keys, and some functions and buttons won't be imported), but it won't cause any serious problems.

RM retrieves the keymap from the remote definition based on the device type index. The it uses that keymap definition to parse the bitmap and builds a list of keys from that keymap are present in the upgrade, in order. RM determins where the bitmap ends by looking for a byte with the right-most bit cleared. That means that if the bitmap is too long for the keymap, RM won't use part of the bitmap for the hex cmds.

Then it cycles through that list of keys. For each key, it

creates a function with the same name as the key.

Sets the hex command ( using the size of the hex cmd from the protocol)

But would I be right in saying that if the user just happens to have the wrong remote selected when they import the binary file, selecting the right remote after the fact won't do them any good?

I've just had a thought. Maybe the "JU" and "PL" tags are unique to Slingbox? So, if we come across some other device that has a chip similar to the Slingbox's chip installed, maybe their binary files would have a different tag in their names?

With that in mind, what would it take to have RM use the tag to select the RDF? Maybe we could add an entry into the RDF that would tie the RDF to the right tag._________________Rob
www.hifi-remote.comPlease don't PM me with remote questions, post them in the forums so all the experts can help!

I have a message into UEI asking them about the JU/PL tags, but I'm totally OK with hard coding this for now, it's certainly better than risking having the wrong remote selected.

I don't recall what the format of WAV files is, but it's probably similar._________________Rob
www.hifi-remote.comPlease don't PM me with remote questions, post them in the forums so all the experts can help!