JP1 Remotes

Could someone do me a favour and compile a Slingbox JU BIN file from the RMDU file at
https://www.hifi-remote.com/forums/dload ... le_id=8198 ?

I have now had 2 people with JU Slingboxes report that the IR Code is 'not found'. I would like to find out if my JU RDF file is incorrect and is not producing the correct JU BIN file.

I have included a PROTOCOLS.INI in the ZIP file which contains the XMP(Protocol).

Thanks

Hi Alan, Its been over a week, so I thought I'd give your thread a little bump.

As you know I don't understand much about the slingbox.

I don't understand why placing the bin file in the proper folder would give you a message IR Code not found.

I do know that as of RM 1.98beta7 the users will get the following error message if they try to open the RDMU.

Protocol Name not found
XMP (Slingbox) ID=01 6C, variant name JP1 Slingbox.

I wonder if your users are telling you IR Code when they meant Protocol Name? Currently with RM 1.98beta7, if your users want to modify the RDMU file, they would need to patch the jar file and the protocols.ini.

Once the patch is in place, if you import your JU. Bin back into RDMU, the fixed data matches your RDMU file.

I am hoping someone with JU specific knowledge might help you further.

vickyg2003 wrote:Hi Alan, Its been over a week, so I thought I'd give your thread a little bump.

Thanks

vickyg2003 wrote:I don't understand why placing the bin file in the proper folder would give you a message IR Code not found.

At the moment there are 2 types of Slingbox in circulation, US-built, which use the PL file and non-US-based ones, which use the RV file. Now, if you had only the RV file in the folder and tried to access it with a US Slingbox you would get that message. So I normally recommend that both files are put in the folder so that either box will find the right file.

Now, there a very few old Slingboxes around that need the JU file, and this user had one, so when he tried to run the setup routine he understandably got the message because only the PL & RV BIN files were present in the folder.

So far so good The problem was that when we also added a JU BIN file he still got the message. So there appears to be something wrong with the format of the JU BIN file I produced so that this JU Slingbox did not recognise it as a valid upgrade file.

So I just wanted someone else to produce a BIN file to see if the problem lies with my setup (I have done a lot of tweaking to my RDF, Protocol and Image files) or whether the problem lies with his Slingbox.

vickyg2003 wrote:I do know that as of RM 1.98beta7 the users will get the following error message if they try to open the RDMU.

Protocol Name not found
XMP (Slingbox) ID=01 6C, variant name JP1 Slingbox.

That was why I included my PROTOCOLS.INI file in the downloads, as that includes the three new XMP protocols.

vickyg2003 wrote:I wonder if your users are telling you IR Code when they meant Protocol Name? Currently with RM 1.98beta7, if your users want to modify the RDMU file, they would need to patch the jar file and the protocols.ini. Once the patch is in place, if you import your JU. Bin back into RDMU, the fixed data matches your RDMU file.
with JU specific knowledge might help you further.

Nothing that complex. This user is simply telling me the JU BIN file I am building is not being recognised by his Slingbox (We know the new XMP Protocols basically work as I have had a number of users successfully adding PL & RV BIN upgrades)

Cheers

Al

alanrichey wrote:

vickyg2003 wrote:I do know that as of RM 1.98beta7 the users will get the following error message if they try to open the RDMU.

Protocol Name not found
XMP (Slingbox) ID=01 6C, variant name JP1 Slingbox.

That was why I included my PROTOCOLS.INI file in the downloads, as that includes the three new XMP protocols.

Yes, but the protocol INI file is not enough, you need to get some Class files into the remotemaster.jar See this thread, for information on how to modify the jar. I had a lot of problems with the procedure myself, so I'd advise reading the instructions carefully if you are not familiar with how to add files to a zip file with a specific path.

alanrichey wrote:

vickyg2003 wrote:Hi Alan, Its been over a week, so I thought I'd give your thread a little bump.

Thanks

vickyg2003 wrote:I don't understand why placing the bin file in the proper folder would give you a message IR Code not found.

At the moment there are 2 types of Slingbox in circulation, US-built, which use the PL file and non-US-based ones, which use the RV file. Now, if you had only the RV file in the folder and tried to access it with a US Slingbox you would get that message. So I normally recommend that both files are put in the folder so that either box will find the right file.

Now, there a very few old Slingboxes around that need the JU file, and this user had one, so when he tried to run the setup routine he understandably got the message because only the PL & RV BIN files were present in the folder.

So far so good The problem was that when we also added a JU BIN file he still got the message. So there appears to be something wrong with the format of the JU BIN file I produced so that this JU Slingbox did not recognise it as a valid upgrade file.

So I just wanted someone else to produce a BIN file to see if the problem lies with my setup (I have done a lot of tweaking to my RDF, Protocol and Image files) or whether the problem lies with his Slingbox.

My RDF is the old one from 2007. I know that I can open it fine in Remotemaster. I looked in the RDF folder and didn't see anything newer. I can't see anything obviously from within the RDMU file.

vickyg2003 wrote:Yes, but the protocol INI file is not enough, you need to get some Class files into the remotemaster.jar I had a lot of problems with the procedure myself, so I'd advise reading the instructions carefully if you are not familiar with how to add files to a zip file with a specific path.

Must admit I'd forgotten about that. Although I did it for mine a few weeks ago (couldn't produce the PL & RV BIN files otherwise) without any problem.

To be honest I think we might as well knock this on the head. The user involved has given up waiting and has decided to buy a new Slingbox. And he is only the second person I have found with a JU Slingbox (they are effectively pre-production models) so it might not happen again.

Thanks for thinking of me though

Al

Well if the user has moved on, and JU is rare I won't pursue this. I do think the next plan of action would be to obtain some official JU Bin files, and check to see if they import and export properly from remotemaster.

There's a problem with the link in the first thread, there's no file there when I try to look.

The JU boxes were real production boxes, it's just that by the time that the Slingbox started to catch on, they'd already upgraded to the PL box, so there aren't that many of them out there.

Hi Rob

Sorry, I took it off when no-one responded. I tend to clean up the Slingbox Work files section once a week to keep it tidy

I've put the RMDU file back up at https://www.hifi-remote.com/forums/dload ... le_id=8198

I just need a JU BIN file from it, although as Vicky has pointed out you need a version of RM (and PROTOCOLS.INI) that has been upgraded to accept the 3 new XMP protocols.

Cheers

Al

alanrichey wrote:Sorry, I took it off when no-one responded. I tend to clean up the Slingbox Work files section once a week to keep it tidy

Threads need to be bumped occasionally as there are so many that we sometimes miss them, or forget to come back to them.

alanrichey wrote:... as Vicky has pointed out you need a version of RM (and PROTOCOLS.INI) that has been upgraded to accept the 3 new XMP protocols.

I was part of that development, so I've got that covered.

Here's my attempt at a bin file:
https://www.hifi-remote.com/forums/dload ... le_id=8199

Great thanks. I'll send it to the user and hope he hasn't sold his box

Hello Gentlemen,

I am the "user" that Alan was trying to help. I want to thank him as well as everyone who posted in this thread. I did not sell my Slingbox Classic and would still very much like to get it going if at all possible.

Rob, I tried to load the JU file that you posted but my Slingbox gives me a message "Custom remote code not found. Please try a different code." even though the file is in the correct directory and should be picked up. I am not sure why it is doing that. Several people reported that selecting Comcast / DTA4 IR profile actually controls this DTA; but none of them had an Slingbox Classic with a JU version. When I select that profile - the remote picture looks identical to the stock remote that came with that box, but all buttons are grayed out and non functional in the UI. I also checked with a camera and confirmed that IR blaster does not blink at all. I verified that blaster and connector are functional by selecting another profile and checking that it does in fact blinks. I am not sure what else I can try so if anyone has additional suggestions I would appreciate it.

Thank you.

Hi Gorby, thanks for joining us over here. I guess the next step is to confirm whether your Slingbox can accept any upgrade at all.

To this end, maybe Alan can create a simple upgrade (that uses the NEC1 protocol perhaps) and see if you can get that to load. If that doesn't load as a JU file, let's try re-creating it in PL, PK and RV formats to see if it will load in one of the other formats. If we can't load a simple upgrade in any format, then there must be something wrong with your box (or you're doing something wrong that we're not detecting).

If we can get a simple upgrade to load, we can re-visit the XMP upgrade to see what's wrong with it.

OK, a simple Cable box upgrade using the NEC1 protocol. All 4 BIN files are at https://www.hifi-remote.com/forums/dload ... le_id=8218

Just try putting all of them into the \SBAV\ folder and see if the message still occurs.