JP1 Remotes

Alan, I took the slingbox RDF's from 1.31 and updated all the protocols sections by hand. I also added an [Extender] Section so that these updates will be handled automatically from now on.

After doing that I wasn't sure that you'd didn't have anything pending over at source forge, so thought I should ask.

Also some software has an option of ignoring extenders, so I wasn't sure if adding the extender section was going to be okay with you. The disadvantage is that you see the complete list, the advantage is that the Sling RDF's will automatically get updated in the future.

Your call.

Edit: Files are in the RDF Development area.
https://www.hifi-remote.com/forums/dload ... &cat_id=44

Nothing pending on Sourceforge so that is fine. And I only use RM so I assume there will be no effect.

I've downloaded them and will use them from now on to confirm.

But I have also updated the old Axum one to fix a couple of bugs as well so can you do the same updates on that one ?

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

Alan, I've never seen the BINAuxum RDF before, I don't have any information on the protocols that sling contains.

vickyg2003 wrote:Alan, I've never seen the BINAuxum RDF before, I don't have any information on the protocols that sling contains.

The Axum RDF is actually for the Monsoon Media's Hava and Vulkano place-shifters. And technically, so is BINPK since there hasn't been a single confirmed Sling Media Slingbox that was released with PK chip. The PK chips have been sited on several Hava Titanium boxes.

Sorry, I thought I had posted a reply, but it hasn't appeared. Can't have hit the Submit button.

The Axum RDF is identical to the PL BIN file except it has an extra line:

2BytePid=Yes

in the [General} Tab at the beginning. I assume you know the reason for that. So actually I could make the change myself, but as you know what you are dong.....

Okay, PK or PL, I am confused. I don't know where the information got copied from in the first place.

I'm surprised that is says it says 2byte pids, and the PL didn't say that. I did some reading that said that the hava upgrades were the same format as the PL upgrades, so I can't understand the difference
https://www.hifi-remote.com/forums/viewt ... light=axum

I don't really know what I'm doing, I just know that I have an updated list of protocols that are in the various remotes. If you have the wrong protocol list some of your upgrades won't work.

vickyg2003 wrote:Okay, PK or PL, I am confused. I don't know where the information got copied from in the first place.

Sorry, too many cooks again. I keep nagging 'eferz' to stop complicating matters but he finds it irresistible

Here is the full background. There are 4 Slingbox RDFs

JU - VERY old US Slingboxes
PK - Never actually used on release versions
RV - non- US Slingboxes
PL - US Slingboxes

At the same time there were the Hava boxes that happened to also use the PK chip and also an Axum chip which seemed to have been almost PL compatible, And about 18 months ago Rob produced an RDF for the Axum chip. Not sure why he linked it with the Slingbox, maybe because it was so similar to the PL RDF. He will have to answer that.

Now, in the last couple of weeks Monsoon (the people behind Hava) have released a new box called the Volkano, and that uses the Axum chip (although I have seen suggestions it might also use the PK chip). So I updated Rob's AXUM RDF to fix the longstanding bugs in the [Buttons} and [Button Maps] sections. I asked him a couple of times if I should replace the old one but never got a reply. So now I have done it, as my corrected version has been proven to work by a couple of Vulkano owners.

Make sense now ?

vickyg2003 wrote:I'm surprised that is says it says 2byte pids, and the PL didn't say that. I did some reading that said that the hava upgrades were the same format as the PL upgrades, so I can't understand the difference
https://www.hifi-remote.com/forums/viewt ... light=axum

Rob will have to answer that, as he produced it. I haven't a clue.

I apologize for making it "confusing". Honestly, I thought that I was helping by clarifying the difference. Anyways, if you look at this thread: (http://www.myhava.com/forum/viewtopic.php?f=2&t=2662)

The four versions of the UEI chips supported by Monsoon Media:

• PK
• PL
• Gondar
• Axum

All four of these chips can been seen on different Hava models.

• Hava Titanium HD
• Hava Platinum HD
• Hava Wireless HD
• Hava Titanium HD WIFI

Their newest model, the Vulkano, has only been seen with an Axum chip.

If the Axum chip uses 2BytePid=Yes, then the PL chip and the Axum chip are different chips, even if they are otherwise similar. In fact, any chip with a different name is a different chip, even if it has similar properties to another chip.

Apart from the JU chip, all the others use encrypted data, so "similar" probably means that the chip uses the same encryption as the chip that it's similar to.

Encryption is handled by the following RDF entry, where the number is brackets is the "key" to the encryption.

EncDec=KeyedEncrypterDecrypter(120)

The list of protocols should be good for the JU, PL, PK and RV chips, for all others it's a best guess.

If we're working on a best guess, then copying the protocol section from the BINPL RDF would probably be a better starting point, since the current version of the RDF has old variants, but the 2 byte pid entry in the RDF, would mean it has the latest and greatest pids.

We don't want the protocol section to be automatically upgraded, we'll want to examine these on a 1 by 1 bases, as upgrades don't work. So no extender section.

For the Vulkano owners (or wanna-be owners) out there, read this.