JP1 Remotes Wiki - User contributions [en]

How to Install a Custom Remote onto the Slingbox

2019-08-03T08:43:02Z

Alanrichey: /* Installing a Remote BIN file on the Slingbox M1/M2 */

''Written by: Al Richey''

The Slingbox comes with several hundred remote control codes to operate thousands of different devices. Unfortunately, there are times that you may have a device that they do not support, or you have a remote control for a special device, like a surveillance camera. In that case you need to install a custom remote code on the Slingbox to control your device. This article explains how to install custom remote BIN files on the Slingbox It has 3 sections, one for the Slingbox M1 & M2, one for the Slingbox 350 & 500 (Now called SlingTV) and one for the older Slingboxes (Classic, AV, Pro, Solo, & Pro-HD), as they all use slightly different methods.

==Introduction==
If you are not familiar with custom remote bin files they are specially made files that you can install onto your Slingbox for controlling devices that are not included in the supplied Slingbox remote controls. We have hundreds of them available, in our Download Pages for all sorts of devices. If you have tried the Slingbox supplied ones and can’t find one that works we recommend you search or list and try one available here. If you do not see one for your device in the list you can check the JP1 forums that also carry a large number of Custom Remotes.

The remote files are called BIN files because the file-name extension ends in .bin (on may Windows machines they will show as being associated with VLC, you can ignore this). When downloading remote codes you may find several different ones contained in a Zip file. For example: S2010_PL.BIN and S2010_RV.BIN. For most devices you will need only the xxxx_PL.BIN file. The xxxx_RV.BIN file is used for older European Slingbox Solo models. So if you have one of those you need to try both files just in case. Note that you must NOT rename these files, it is essential the file name stays as issued.

'''If you have any problems installing these files please do NOT just report back it ‘doesn’t work’, that is totally useless for someone trying to understand what is going on. So please report all of the following:'''

#What model Slingbox do you have?
#Was there any error message after you typed in the Code and tapped the Test button (or selected the file and tapped ‘Continue’ on the M1 & M2)?
#Did you give the commands plenty of time to react? (I have a DVR that takes about 6-8 seconds to power up/down)
#If you are using a Solo did you try both BIN files?
#After completing the setup do any of the buttons work?
#If you are installing on a Solo or Pro-HD or older box that uses an external IR Blaster, have you used a Digital Camera or Mobile Phone Camera to confirm the IR Blaster is actually firing when you tap the Power button? (Watch the tip of the IR Blaster through the viewfinder while you tap a button. You should see a white (not red) flash. Test it on a real remote so you know what you are looking for). If you are using a 350/500/M1/M2 have you tried using the external blaster?
#Have you experimented with the placement of the IR Blaster? On some devices this is critical so don’t give up too quickly. Try shining a flashlight at the front of the receiver and see if you can see the IR receiver behind the smoked glass.
#Are you sure the device is working correctly using the real remote?
#Are you sure your device is set to use IR ? Many boxes can operate on RF or IR and if it is set to RF then the Slingbox will not affect it.
#If you have a device that supports multiple remote addresses (DirecTV, Dish Network, Tivo…) are you sure the remote address is set to the default ?
#Have you tried resetting the Slingbox. ? This has been found to help.
#Do you have access to a Logitech Harmony Universal Remote? If so let me know.

Once the BIN file has been downloaded to your Slingbox it is not required anymore and can be deleted. The fact that it now resides inside your Slingbox means that any viewing system you use (Slingplayer, newwatch.slingbox.com, SlingCatcher, Facebook, SPMobile….) will use that remote.

If you have any recommendations to improve this guide, just let us know.

Now go the appropriate set of instructions:

==Installing a Remote BIN file on the Slingbox M1/M2==

After obtaining an XXXXX_PL.BIN remote bin file and putting it somewhere on your Hard Drive (I recommend the root folder C: to make life easier), you should open up the Desktop Slingplayer. Once it is running select the ‘Standard’ View and then click on Settings and the Reconfigure Video Input.

[[Image:Slingbox-01.jpg]] 

Then select the Input you wish to configure and click on the Change Device Link

[[Image:Slingbox-02.jpg]] 

You will be taken through the Slingbox Naming, Location and TV Provider screens again. Seems unnecessary to ask the Name and Location but that is how it is designed, hopefully it will be improved in later versions.

Note: These questions are purely for the TV Guide, they have absolutely nothing to do with the Remote. If you are somewhere other than the USA and Canada where the TV Guide is not supported just put random values in. I use USA and 90210 (Beverly Hills)

Now, on the next screen select the ‘Pick’ option.

[[Image:Slingbox-03.jpg]] 

This brings you here

[[Image:Slingbox-04.jpg]] 

First select the Device Type.

[[Image:Slingbox-04.jpg]] 

That is not necessarily the type of your device, it is defined by the first letter of the BIN file. If it is a ‘C’ then select Cable TV, ‘S’ select Satellite and ‘V’ select PVR. NEVER select Miscellaneous, there is a bug in that selection that disables the colour buttons, and NEVER select DVD Player as that gives you a very poor remote image without many of the buttons.

Now Select the Manufacturer. If the code you are installing is between 2000-2047 then just scroll to the bottom and select Custom and then Continue. (This is because they use the default remote image).

[[Image:Slingbox-06.jpg]] 

If the code is between 0000-1999 then select the Manufacturer of your device and when the Model Number drop down appears again scroll to the bottom of the list and select Custom and then Continue. With a bit of luck this will give you a realistic remote image.

[[Image:Slingbox-07.jpg]] 

So that brings you to this screen.

[[Image:Slingbox-08.jpg]] 

Just click on the Choose File and you will be presented with a standard File Selector box. Just navigate to where you stored the BIN file and select it.

Note: There is no error checking done on this file so if you select the wrong one, or do not select a file the system will try and install it and then crash, so make sure you select the right file.

The file name will appear next to the box and you can then press Continue.

After a bit you should get a picture and the request to test your remote, so tap on Continue and follow the instructions.

[[Image:Slingbox-09.jpg]] 

And if you test the buttons you should find it now operates your device. And if you right-click on the image and select Custom you might find other buttons defined. What each one represents will be covered in the Readme file you downloaded.

[[Image:Slingbox-10.jpg]] 

If the remote does not work go back to the checks I suggested at the beginning of this guide and see if they help. Otherwise confirm the Remote is working and tap the Watch TV button.

==Installing a Remote BIN file on the Slingbox 350/500 (SlingTV)==

After obtaining an XXXXX_PL.BIN remote bin file and putting it somewhere on your Hard Drive (I recommend the root folder C: to make life easier), you should open up your web browser and navigate to newwatch.slingbox.com. Once there select the Slingbox you wish to setup then click on Settings.

[[Image:Slingbox-11.jpg]] 

On the next page click on Configure Inputs.

[[Image:Slingbox-12.jpg]] 

Now select the Input you wish to configure (The radio button with a black centre). If the input has been previously configured then you will need to tap the ‘X’ next to the input to reset it or the Reset button at the bottom.

[[Image:Slingbox-13.jpg]] 

In this case I am going to configure the Composite input so I selected that, tapped the Reset button and then tapped the Next button.

[[Image:Slingbox-14.jpg]] 

Now work through the ZIP code and TV Provider screens. Please note this has NOTHING to do with the remote, this is to setup your Program Guide. For any non-US owners, these screens are irrelevant but you still have to complete them. I use a ZIP code of 90210 (Beverly Hills) and select the ‘No provider’ option. Then you move onto the next screen to actually setup the Remote.

[[Image:Slingbox-15.jpg]] 

So click on the Pick option to get the next screen.

First select the type of device.

[[Image:Slingbox-16.jpg]] 

This is NOT the type of device you are installing. To get the right one, look at the BIN file code. If it starts with an ‘S’ select Satellite, if it starts with a ‘C’ select Cable TV Box and if it starts with a ‘V’ select PVR. NEVER select DVD, even if you have a DVD as this will result in a very poor Remote image.

The next step depends on the code number. If your BIN file has a code between 2000-2047 (which will use the Default Remote image) then open the ‘Select Manufacturer’ drop down box, scroll down to the bottom and select Custom.

[[Image:Slingbox-17.jpg]] 

If the code is between 0000-1999 then open the ‘Select Manufacturer’ drop down box, select your Manufacturer or TV Provider, then when the ‘Select Model’ drop down appears scroll down to the bottom and select Custom. This should give you a realistic remote image for the Manufacturer/TV provider

[[Image:Slingbox-18.jpg]] 

Then press Next.

Now type in the FULL pathname and filename for the BIN file you wish to install. You can see now why I suggest putting the BIN file into the root directory, so you don’t have to type in a long file path with the possibility of making mistakes.

[[Image:Slingbox-19.png]] 

Ensure you get the backslash correct (not a forward slash) and that everything is in upper case.

Now tap the TEST button to download the BIN file to the Slingbox.

If you get this error message then the first thing to realise is that it does not mean ‘Invalid Custom BIN file’. It actually should read ‘Custom Remote BIN file not found’, so the likelihood is that you have not typed in the file path and file name correctly.

[[Image:Slingbox-20.png]] 

(Amazingly, the setup does not check the validity of the BIN file so I have no idea why Sling used this message, it makes no sense. I have complained about it for months but they don’t seem to be interested).

Once you have the correct location typed in the system should now install the BIN file and then download the Sling Remote image as shown in the next screenshot. (That is the default image, for codes between 0000-1999 you should get your realistic image)

[[Image:Slingbox-21.png]] 

And if you test the buttons you should find it now operates your device. And if you right-click on the image and select Custom you might find other buttons defined. What each one represents will be covered in the Readme file you downloaded.

[[Image:Slingbox-22.png]] 

If the remote does not work go back to the checks I suggested at the beginning of this guide and see if they help. Otherwise tap Next and then Watch and you are complete.

==Installing a Remote BIN file on legacy Slingboxes==

Remember: If you are installing on a Pro-HD you need only the XXXXX_PL.BIN file. If you are installing on other boxes you may have to try both the XXXXX_PL.BIN (USA) and the XXXXX_RV.BIN (European) files (And ignore your actual location, many European Slingboxes were actually manufactured in the USA).

After obtaining the remote bin file and putting it somewhere on your Hard Drive (I recommend the root folder C: to make life easier), you should open up your web browser and navigate to setup.slingbox.com. Once there click on the ‘Get Started’, select the Slingbox you wish to setup then select Configure Inputs.

[[Image:Slingbox-23.jpg]] 

After selecting which input you are using, you will be brought to the ‘Remote Control Setup’ page. On this page click on the ‘supported devices’ link at the bottom (I know this is illogical, as you are installing an unsupported device, but that was how Sling decided to implement it).

[[Image:Slingbox-24.jpg]] 

Now select the type of device.

[[Image:Slingbox-25.jpg]] 

This is NOT the type of device you are installing. To get the right one, look at the BIN file code. If it starts with an ‘S’ select Satellite, if it starts with a ‘C’ select Cable TV Box and if it starts with a ‘V’ select PVR. NEVER select DVD, even if you have a DVD as this will result in a very poor Remote image.

Now open the ‘Select Manufacturer’ drop down box, scroll down to the bottom and select Custom.

[[Image:Slingbox-26.jpg]] 

Then press Next.

Now type in the FULL pathname and filename for the BIN file you wish to install. You can see now why I suggest putting the BIN file into the root directory, so you don’t have to type in a long file path with the possibility of making mistakes.

Ensure you get the backslash correct (not a forward slash) and that everything is in upper case.

[[Image:Slingbox-27.jpg]] 

You can then test the remote. If it does not work you can go back and try the other RV or PL BIN file.

If you get this error message there are 2 possibilities. The first is that you are using the wrong (RV or PL) file for your Slingbox, so try the other. For the other possibility you have to realise that it does not mean ‘Invalid Custom BIN file’. It actually should read ‘Custom Remote BIN file not found’, so the likelihood is that you have not typed in the file path and filename correctly. Not sure why Sling did not use a more appropriate message in this case.

[[Image:Slingbox-28.jpg]] 

Once you have the correct location typed in the system should now install the BIN file and then download the Sling Remote image as shown in the next screenshot. (That is the default image, for codes between 0000-1999, you might get your realistic image).

[[Image:Slingbox-29.jpg]] 

And if you right-click on the image and select Custom you might find other buttons defined. What each one represents will be covered in the Readme file you downloaded.

[[Image:Slingbox-30.jpg]] 

If all is good you can now control the device connected to your Slingbox. You may be taken through a few more setup screens before it completes. One thing worthy of note is that non-US/Canada customers sometimes get asked to input ZIP codes and TV Providers. The service provider information is used ONLY for the Electronic Program Guide and is not needed for viewing or controlling your Slingbox. So just ‘lie’ to the system. I tend to use a ZIP code of 90210 (Beverly Hills) and a random TV Provider.

If the remote does not work go back to the checks I suggested at the beginning of this guide and see if they help. Otherwise tap the Watch Live TV and you should be good to go.

How to Create Custom Remote Controls and use them on your Slingbox

2016-04-17T16:49:37Z

Alanrichey: /* Getting the Codes onto your PC. */

Written by: Al Richey 

=='''Background information'''==
One of the most common posts on the support site is about remote codes for unsupported devices. So if you find yourself in this situation I hope this will help. Before detailing the steps to go through there are some basic things you need to understand (this isn‟t essential reading but everything will make much more sense if you do know the details)
==='''Different UEI Chips'''===
: There were five different chips used in Slingboxes. These are designated as JU, PK, PL, RV & JB. If you want to check your type you can verify your IR blaster version in the Slingbox Properties dialog. Then match the IR version number with the chip type using the chart below.
#JU (VERY old US boxes)
#PL (current US boxes)
#PK (never used)
#RV (old European boxes)
#JB (All modern Slingboxes, but compatible with PL files)

So unless you have an old European Solo all you need is the PL file.

==='''Slingplayer Compatibility'''===
: In older versions of Slingplayer it was possible to change the look of the Custom Remote skin‟. Since Slingplayer V1.5 this functionality has been removed and as far as the look of the Remote is concerned you are stuck with the Generic design produced by Sling Media. All we can do is change the codes that are sent when a specific button is pressed. One drawback of the Generic Remote is that it has only the main buttons, so extra buttons on other remotes (such as Audio/Setup…) can not be mapped directly. What we have to do is put them into a Custom Menu which is accessed by tapping on the Menu button on the Generic Remote or right-clicking on the image. (Note: If a remote image has already been produced by Sling it is possible to use that image instead of the generic image, just contact me at alan@rmrsoft.com)
:

==='''Setup Code Nomenclature'''===
: When you run the Configure Inputs routines in the various Slingplayers and select a supported device, what actually happens is that a Binary Code is downloaded to the Slingbox. 
: This Binary Code details the IR codes that are sent when a specific button is pressed on the remote. Unfortunately the native Slingbox software doesn't use separate binary files that we can edit, their codes are apparently compressed and packaged into special files that we can't do anything with (that I know of). But what we can do instead of editing the built-in codes is to use a separate external upgrade code file. These files have the format such as "C1234_PL.BIN". 
: The first letter of the file describes the type of device, the main ones we are interested in are:

::V which is for VCRs, which encompasses PVRs, DVRs and other recorders
::S which is for Satellite and FTA set top boxes
::C which is for Cable boxes
::Y which is for DVD Players

:This is followed by a 4-digit code number. For Slingboxes the code numbers can be between 0000-2047 (actually higher in newer Slingboxes but to stay safe we are better staying below 2047). In general, codes below 2000 actually relate to specific boxes, for example V0618 is the code for a TIVO and D0032 is the code for a Pioneer CD Player. But we can feel fairly safe using 2000-2047 for our own codes. The final part of the filename defines the chip for which it will run. 
: So if you were looking for the binary file for a PVR with a code number allocated 1234, designed to run on a PL-equipped Slingbox, you would be searching for a file called V1234_PL.BIN. Note: You must NEVER change the name of the file, as the letter, code number and chip type are also defined inside the file itself.

==='''JP1'''===
:You will hear a lot about "JP1". Basically this is a process whereby people using "One For All‟ (OFA) remote controls can add new codes to their remotes from their PC. The remote control processor inside the Slingbox is made by the same company that makes OFA remotes, so the upgrades are similar. The JP1 tools have been upgraded so that we can now use them to create and modify upgrades for the Slingbox.

=='''The Basic Procedure.'''==
The official procedure to follow is to report the [http://support.slingmedia.com/get/KB-005640.html Lack of a Supported Remote] to SlingMedia and they will add it to the database. In practice, they are not quick at doing this (I have been asking for a remote for over 4 years now), and the updated remote list seems to be only occasionally updated. That may change in the future but for now it is really not a practical quick solution. So for a short term fix what you need to do is to create or acquire the correct Binary code file for your A/V device, and then install it into your Slingbox. This installation process is covered in detail in [[#Installing_the_Binary_file_to_the_Slingbox|Section 4]], so first let‟s see where you can look for these files. 

=='''Obtaining the Binary file for the Custom Remote'''==

#Before starting, make sure in the setup wizard you have tried all the devices by that same manufacturer, even if the model number does not match, and all the associated code numbers. It's also worth trying your TV Provider in case they have 'badged' someone else's box. You might be lucky and find one that works and that will save a lot of work. If that doesn't solve the problem here is the step by step approach to getting hold of your binary file: 
#Go to the JP1 forum. This has a specific Download area for [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=87 Slingbox Custom Remotes], so go through all those to see if your device has already been done. 
#If it isn‟t there the JP1 forum also has a more general [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=4 File Download Area]. From this page you select the download area for the specific type of device and check there. If you are lucky you will find a source file for using in the program RemoteMaster (RM or KM files), the use of which is discussed in [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]]. 
#Have a look on the Hava forums. They are also using the same chips and the files might be there. Check out this [http://www.myhava.com/forum/viewforum.php?f=17&st=0&sk=t&sd=d&start=0 forum]. You‟re looking for a PK or PL file. They can be imported into Remote Master and then converted to the PK, PL, RV or JU files for the Slingbox. Again this is discussed in [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]]. 
#Do it yourself by buying a Nevo C2, or an IR Widget, and learn the codes needed to control the device. How to do this is covered in [[#Learning_the_IR_codes_from_your_own_remote|Section 5]] & [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]]. 
#Ask someone else to do the work for you. You can try this by posting a request for help in either:
##The [https://community.sling.com/content Slingbox Answers Forum].
##The [http://www.hifi-remote.com/forums/viewforum.php?f=19 JP1 forum]. 
I can normally install your device on my Harmony Universal Remote to mimic the original Remote and learn the codes for you (unless I am away on holiday). 

=='''Installing the Binary file to the Slingbox.'''==
 I have written a comprehensive Installation Guide at

http://placeshiftingenthusiasts.com/how-to-install-a-custom-remote-onto-the-slingbox/

Once you have completed the setup and the BIN files have been downloaded to the Slingbox they are not used any more and can be deleted.

=='''Learning the IR codes from your own remote.'''==
==='''Requirements'''===
Assuming you have decided to create the Remote Binary File yourself, the first stage is to learn the codes from your original Remote. This is what you need:
====Hardware====
#A computer with a USB port. 
#A A Nevo C2 Learning Remote (Available on E-Bay for $20 or so) or alternatively

:An IR learning "widget". I got mine from Tommy Tyler through https://www.tindie.com/products/TommyTyler/ir-widget-infrared-remote-control-signal-recorderanalyzer/ (My preferred solution). 

====Software====
:If you are using the Nevo C2: [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=81 RM/RMIR.EXE] [http://www.hifi-remote.com/forums/dload.php?action=file&file_id=7201 RDF Files] These are support files for the program. If you are using an IR Widget: [http://www.compendiumarcana.com/irwidget/irscope.zip IRSCOPE.EXE] [http://www.ftdichip.com/Drivers/VCP.htm The drivers] [http://www.hifi-remote.com/forums/dload.php?action=file&file_id=922 The IR decode DLL] Or download [http://rmrsoft.com/remote.zip my full IRSCOPE/REMOTEMASTER package]. Much of the JP1 software needs the java runtime environment (JRE) as well. A lot of computers will already have it installed already, but if you need it you can [http://java.sun/j2se/1.4.2/download.html download] Now we can learn the codes. First we will cover the procedure using a Learning Remote, then cover it using an IR Widget. 

===USING A LEARNING REMOTE===
====Getting the Codes from your Remote====
Follow the instructions to learn your remote codes so the Nevo C2 operates your device. Then download the settings file onto your PC.

====Getting the Codes onto your PC.====
 
:#Install RMIR.EXE onto your PC. It comes as a ZIP file rather than an installation package, which you need to unzip to your PC. The files can actually go anywhere but as a bit of tidy person (geek?) I created a C:\Program Files\IR\ folder and put the files in there. Now go into the folder and click on Setup.vbs and that will produce shortcuts to run RMIR and RM (Full instructions are at http://www.hifi-remote.com/wiki/index.php?title=JP1_-_Just_How_Easy_Is_It%3F_-_RM-IR_Version)
:#You will need to create a sub folder called \RDF\ in whatever folder you have put the IR program and extract the RDF support files into that folder. Again, refer to the instructions. 

Now plug your Nevo into the PC and start RMIR. Use the '''Remote > Download Remote''' menu option to get the data from the Nevo to the PC.

Under the '''Devices Tab''' you should now see the device. Select it, then use the Edit Device button and then the Save As button to produce the required RMDU file.

You can now post that file to the forum where you requested the remote, or if you want to do it yourself then go to the next Section.

===USING AN IR WIDGET===
If you are using an IR Widget there is an excellent guide [http://freepdfhosting.com/6ea1213d67.pdf here] on the Tindle site. So I suggest you download that and read it thoroughly. There is no point in repeating it here, but just to emphasise a few points: 
:#You will want to regularly check for updates to the decodeir.dll. As new protocols are recognized, this dll will change. 
:#There is no way to save the learned values for importing into RemoteMaster (where you will make the remote) so you will need to write them down. 
:#Although I tend to put programs into C:\Program Files\.... this can be a bit dodgy in Windows as programs cannot save files to this area because of security limitations. So it might be safer to install it under \Documents\ 
:#The Guide has a very useful section comparing using a Learning Remotes and the IR Widget and highlighting the differences, (For example "Key" is equivalent to "OBC") so you could check out the previous sub-section covering using IR.EXE and the Learning Remote. And then you will understand this section. When complete you can move onto [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]] to create the Binary file. 

=='''Creating your own Binary files using RemoteMaster'''==
:#To make life easier I have packaged a full set of the latest files required and uploaded them to my site. Just download them from [http://www.rmrsoft.com/remote.zip here] and unzip them onto your computer. 
:#Start RemoteMaster.EXE. You may be promoted to highlight the folder the folder that contains the RDF files (Highlight the \RDF\ folder in the folder where you placed Remotemaster). You may also have to do the same for the Images folder. The display will now look something like this:[[Image:RM-setup.jpg]] 
:#If you have obtained an .rmdu file then use the File > Open menu option to load the file. If you have obtained a .bin file then use the Advanced > Import Binary Upgrade to load up the details. If you have not obtained a file then you will have to input the codes manually. 
:#Now to explain the main Setup Tab: '''Description ''': Use anything you like, I tend to use the device name. '''Remote''': Select the one appropriate for your chip. '''Device Type''': Should be set to the correct type of device (as covered in Paragraph 3 of Section 1). '''Setup Code''': This is where you put the 4-digit code. In theory it can be any number between 0000 and 2047, but as explained in Section 1 Paragraph 3, numbers below 2000 may actually be already allocated to specific devices, so to be safe I personally use 2010. Fell free to use your own value. '''Protocol''': From the dropdown list select the Protocol you discovered when you used IR.EXE/IRSCOPE.EXE. '''Device''': Type in the Device code you recorded from IR.EXE/IRSCOPE.EXE. '''Sub-Device''': If applicable type in the Sub-Device code you recorded from IR.EXE/ IRSCOPE.EXE. 
:#Now tap on the Functions Tab [[Image:RM-functions.jpg]] This picture shows the program with an .rmdu file or .bin file already imported; otherwise the code columns will be blank. The entries are fully configurable, so if there are pre-defined functions that you do not need (pip swap, pipmove..) then you highlight them and tap the "Delete" button. If you have a function that is not pre-defined (Audio, Setup…) then tap the "New" button and enter them. Now fill in the codes for each button that you recorded. You just put in the OBC value and press <Enter>, the other 2 values will be generated automatically based on the protocol you selected. Also, if you used a JP1 learning remote, there's a way to cut and paste all the codes which saves needing to enter them all. In IR, if you select File > Summary you get a page listing lots of stuff. If you scroll down, you'll see a list of learn decodes. You can cut and paste this list into Excel, then you can re-arrange the columns and just select the button names and OBC codes to cut and paste into RM. You can move the RM columns, so if the OBC column isn't the one next to the button names, you can move it there. 
:#Now tap on the Buttons Tab [[Image:RM-buttons.jpg]] This is where you map the defined functions onto the available buttons. Simply tap the Auto-Assign button which should allocate most of the buttons. For any buttons left in red drag the function name from the table on the left to the function column on the right. But note that not all these buttons are available on a Slingplayer Generic Remote. For example the 'Slow' and 'Eject' buttons do not exist on a Generic Remote. So only map the functions onto the buttons that actually exist (You will see that when you check out the Layout Tab, and from experience when you have done this a few times). The important ones to note are the Custom 10-29 buttons. These are the ones you use for the functions you need that aren't on the generic remote and they subsequently appear in the drop down menu of the remote as Custom options (except for Custom 22-26 which are pre-allocated to the colour buttons). 
:#Now tap on the Layout Tab. [[Image:RM-layout.jpg]] This shows the generic Slingplayer remote and shows the buttons you can actually use in the Buttons Tab. If a button shows yellow then that means it is in use. If it shows black (the PgUp/PgDn in the picture) then has not been allocated a function. Again you can drag and drop functions onto a button. 
:#Once you have finished experimenting go back to the Setup tab. Select the appropriate Slingbox remote, go to the 'Advanced' menu at the top and select 'Export Binary Upgrade'. This will produce the BIN file that we have discussed in previous Sections. If you aren‟t sure which Slingbox Chip you have then create a BIN file for the main 2 chips, so that would give you something like 
:::C2010_PL.BIN
:::C2010_RV.BIN

So now you can go back to [[#Installing_the_Binary_file_to_the_Slingbox.|Section 4]] and install the new Custom Remote onto your Slingbox. 
====Finding Missing Codes====
You can often find yourself in the position where the Custom Remote generally works OK but some of the functions are missing or some are sending the wrong code. This is relatively easy to fix by trial and error. The OBC codes must lie between 0-255, so the first thing to do is make a list of the OBC codes that are not being used in the Remote Control. Now use Remotemaster to allocate those codes to the 0-9 buttons and the 15 Custom buttons. Now build a new BIN files, replace the one in your \SBAV\ folder and rerun the "Setup Video Sources" routine. Now try those buttons and see if any of them action the missing function. If you find the missing codes then you can update the original remote file. You may have to repeat this operation 10 times to cover all the missing codes, although you can cut down the number of times by also using the Transport buttons (Play/Pause…) and Channel, Page +/- buttons as well. 

=='''Give your Binary file back to the Community'''==
Finally, remember that it is good to payback. If you find a remote file that works for you then upload it to the JP1 Forums. The way to do this is: 
#Put the 4 Binary files and the Remote Master RMDU file into a ZIP file. I also tend to add a Readme file in case users are unsure how to use the files. Although hopefully they will have read this article and will know what to do. 
#To be really helpful, you should upload your files in 3 different places:
##Upload your ZIP file to the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=87 Slingbox Binary Files] area.
##Upload the Remote Master RMDU source file to the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=98 Slingbox RM Files] area.
##Upload the RMDU file to the appropriate area in the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=4 Device Upgrades] area.
 
I hope these instructions have been helpful. If you have any suggestions for changes or improvements please E-mail me at '''alan (at) rmrsoft (dot) com'''

How to Create Custom Remote Controls and use them on your Slingbox

2016-04-07T16:21:05Z

Alanrichey: /* Getting the Codes onto your PC. */

Written by: Al Richey 

=='''Background information'''==
One of the most common posts on the support site is about remote codes for unsupported devices. So if you find yourself in this situation I hope this will help. Before detailing the steps to go through there are some basic things you need to understand (this isn‟t essential reading but everything will make much more sense if you do know the details)
==='''Different UEI Chips'''===
: There were five different chips used in Slingboxes. These are designated as JU, PK, PL, RV & JB. If you want to check your type you can verify your IR blaster version in the Slingbox Properties dialog. Then match the IR version number with the chip type using the chart below.
#JU (VERY old US boxes)
#PL (current US boxes)
#PK (never used)
#RV (old European boxes)
#JB (All modern Slingboxes, but compatible with PL files)

So unless you have an old European Solo all you need is the PL file.

==='''Slingplayer Compatibility'''===
: In older versions of Slingplayer it was possible to change the look of the Custom Remote skin‟. Since Slingplayer V1.5 this functionality has been removed and as far as the look of the Remote is concerned you are stuck with the Generic design produced by Sling Media. All we can do is change the codes that are sent when a specific button is pressed. One drawback of the Generic Remote is that it has only the main buttons, so extra buttons on other remotes (such as Audio/Setup…) can not be mapped directly. What we have to do is put them into a Custom Menu which is accessed by tapping on the Menu button on the Generic Remote or right-clicking on the image. (Note: If a remote image has already been produced by Sling it is possible to use that image instead of the generic image, just contact me at alan@rmrsoft.com)
:

==='''Setup Code Nomenclature'''===
: When you run the Configure Inputs routines in the various Slingplayers and select a supported device, what actually happens is that a Binary Code is downloaded to the Slingbox. 
: This Binary Code details the IR codes that are sent when a specific button is pressed on the remote. Unfortunately the native Slingbox software doesn't use separate binary files that we can edit, their codes are apparently compressed and packaged into special files that we can't do anything with (that I know of). But what we can do instead of editing the built-in codes is to use a separate external upgrade code file. These files have the format such as "C1234_PL.BIN". 
: The first letter of the file describes the type of device, the main ones we are interested in are:

::V which is for VCRs, which encompasses PVRs, DVRs and other recorders
::S which is for Satellite and FTA set top boxes
::C which is for Cable boxes
::Y which is for DVD Players

:This is followed by a 4-digit code number. For Slingboxes the code numbers can be between 0000-2047 (actually higher in newer Slingboxes but to stay safe we are better staying below 2047). In general, codes below 2000 actually relate to specific boxes, for example V0618 is the code for a TIVO and D0032 is the code for a Pioneer CD Player. But we can feel fairly safe using 2000-2047 for our own codes. The final part of the filename defines the chip for which it will run. 
: So if you were looking for the binary file for a PVR with a code number allocated 1234, designed to run on a PL-equipped Slingbox, you would be searching for a file called V1234_PL.BIN. Note: You must NEVER change the name of the file, as the letter, code number and chip type are also defined inside the file itself.

==='''JP1'''===
:You will hear a lot about "JP1". Basically this is a process whereby people using "One For All‟ (OFA) remote controls can add new codes to their remotes from their PC. The remote control processor inside the Slingbox is made by the same company that makes OFA remotes, so the upgrades are similar. The JP1 tools have been upgraded so that we can now use them to create and modify upgrades for the Slingbox.

=='''The Basic Procedure.'''==
The official procedure to follow is to report the [http://support.slingmedia.com/get/KB-005640.html Lack of a Supported Remote] to SlingMedia and they will add it to the database. In practice, they are not quick at doing this (I have been asking for a remote for over 4 years now), and the updated remote list seems to be only occasionally updated. That may change in the future but for now it is really not a practical quick solution. So for a short term fix what you need to do is to create or acquire the correct Binary code file for your A/V device, and then install it into your Slingbox. This installation process is covered in detail in [[#Installing_the_Binary_file_to_the_Slingbox|Section 4]], so first let‟s see where you can look for these files. 

=='''Obtaining the Binary file for the Custom Remote'''==

#Before starting, make sure in the setup wizard you have tried all the devices by that same manufacturer, even if the model number does not match, and all the associated code numbers. It's also worth trying your TV Provider in case they have 'badged' someone else's box. You might be lucky and find one that works and that will save a lot of work. If that doesn't solve the problem here is the step by step approach to getting hold of your binary file: 
#Go to the JP1 forum. This has a specific Download area for [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=87 Slingbox Custom Remotes], so go through all those to see if your device has already been done. 
#If it isn‟t there the JP1 forum also has a more general [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=4 File Download Area]. From this page you select the download area for the specific type of device and check there. If you are lucky you will find a source file for using in the program RemoteMaster (RM or KM files), the use of which is discussed in [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]]. 
#Have a look on the Hava forums. They are also using the same chips and the files might be there. Check out this [http://www.myhava.com/forum/viewforum.php?f=17&st=0&sk=t&sd=d&start=0 forum]. You‟re looking for a PK or PL file. They can be imported into Remote Master and then converted to the PK, PL, RV or JU files for the Slingbox. Again this is discussed in [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]]. 
#Do it yourself by buying a Nevo C2, or an IR Widget, and learn the codes needed to control the device. How to do this is covered in [[#Learning_the_IR_codes_from_your_own_remote|Section 5]] & [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]]. 
#Ask someone else to do the work for you. You can try this by posting a request for help in either:
##The [https://community.sling.com/content Slingbox Answers Forum].
##The [http://www.hifi-remote.com/forums/viewforum.php?f=19 JP1 forum]. 
I can normally install your device on my Harmony Universal Remote to mimic the original Remote and learn the codes for you (unless I am away on holiday). 

=='''Installing the Binary file to the Slingbox.'''==
 I have written a comprehensive Installation Guide at

http://placeshiftingenthusiasts.com/how-to-install-a-custom-remote-onto-the-slingbox/

Once you have completed the setup and the BIN files have been downloaded to the Slingbox they are not used any more and can be deleted.

=='''Learning the IR codes from your own remote.'''==
==='''Requirements'''===
Assuming you have decided to create the Remote Binary File yourself, the first stage is to learn the codes from your original Remote. This is what you need:
====Hardware====
#A computer with a USB port. 
#A A Nevo C2 Learning Remote (Available on E-Bay for $20 or so) or alternatively

:An IR learning "widget". I got mine from Tommy Tyler through https://www.tindie.com/products/TommyTyler/ir-widget-infrared-remote-control-signal-recorderanalyzer/ (My preferred solution). 

====Software====
:If you are using the Nevo C2: [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=81 RM/RMIR.EXE] [http://www.hifi-remote.com/forums/dload.php?action=file&file_id=7201 RDF Files] These are support files for the program. If you are using an IR Widget: [http://www.compendiumarcana.com/irwidget/irscope.zip IRSCOPE.EXE] [http://www.ftdichip.com/Drivers/VCP.htm The drivers] [http://www.hifi-remote.com/forums/dload.php?action=file&file_id=922 The IR decode DLL] Or download [http://rmrsoft.com/remote.zip my full IRSCOPE/REMOTEMASTER package]. Much of the JP1 software needs the java runtime environment (JRE) as well. A lot of computers will already have it installed already, but if you need it you can [http://java.sun/j2se/1.4.2/download.html download] Now we can learn the codes. First we will cover the procedure using a Learning Remote, then cover it using an IR Widget. 

===USING A LEARNING REMOTE===
====Getting the Codes from your Remote====
Follow the instructions to learn your remote codes so the Nevo C2 operates your device. Then download the settings file onto your PC.

====Getting the Codes onto your PC.====
 
:#Install RMIR.EXE onto your PC. It comes as a ZIP file rather than an installation package, which you need to unzip to your PC. The files can actually go anywhere but as a bit of tidy person (geek?) I created a C:\Program Files\IR\ folder and put the files in there and then created a shortcut on the Desktop. 
:#Now click the "Import" in RMIR

'''(Under construction)
'''

===USING AN IR WIDGET===
If you are using an IR Widget there is an excellent guide [http://freepdfhosting.com/6ea1213d67.pdf here] on the Tindle site. So I suggest you download that and read it thoroughly. There is no point in repeating it here, but just to emphasise a few points: 
:#You will want to regularly check for updates to the decodeir.dll. As new protocols are recognized, this dll will change. 
:#There is no way to save the learned values for importing into RemoteMaster (where you will make the remote) so you will need to write them down. 
:#Although I tend to put programs into C:\Program Files\.... this can be a bit dodgy in Windows as programs cannot save files to this area because of security limitations. So it might be safer to install it under \Documents\ 
:#The Guide has a very useful section comparing using a Learning Remotes and the IR Widget and highlighting the differences, (For example "Key" is equivalent to "OBC") so you could check out the previous sub-section covering using IR.EXE and the Learning Remote. And then you will understand this section. When complete you can move onto [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]] to create the Binary file. 

=='''Creating your own Binary files using RemoteMaster'''==
:#To make life easier I have packaged a full set of the latest files required and uploaded them to my site. Just download them from [http://www.rmrsoft.com/remote.zip here] and unzip them onto your computer. 
:#Start RemoteMaster.EXE. You may be promoted to highlight the folder the folder that contains the RDF files (Highlight the \RDF\ folder in the folder where you placed Remotemaster). You may also have to do the same for the Images folder. The display will now look something like this:[[Image:RM-setup.jpg]] 
:#If you have obtained an .rmdu file then use the File > Open menu option to load the file. If you have obtained a .bin file then use the Advanced > Import Binary Upgrade to load up the details. If you have not obtained a file then you will have to input the codes manually. 
:#Now to explain the main Setup Tab: '''Description ''': Use anything you like, I tend to use the device name. '''Remote''': Select the one appropriate for your chip. '''Device Type''': Should be set to the correct type of device (as covered in Paragraph 3 of Section 1). '''Setup Code''': This is where you put the 4-digit code. In theory it can be any number between 0000 and 2047, but as explained in Section 1 Paragraph 3, numbers below 2000 may actually be already allocated to specific devices, so to be safe I personally use 2010. Fell free to use your own value. '''Protocol''': From the dropdown list select the Protocol you discovered when you used IR.EXE/IRSCOPE.EXE. '''Device''': Type in the Device code you recorded from IR.EXE/IRSCOPE.EXE. '''Sub-Device''': If applicable type in the Sub-Device code you recorded from IR.EXE/ IRSCOPE.EXE. 
:#Now tap on the Functions Tab [[Image:RM-functions.jpg]] This picture shows the program with an .rmdu file or .bin file already imported; otherwise the code columns will be blank. The entries are fully configurable, so if there are pre-defined functions that you do not need (pip swap, pipmove..) then you highlight them and tap the "Delete" button. If you have a function that is not pre-defined (Audio, Setup…) then tap the "New" button and enter them. Now fill in the codes for each button that you recorded. You just put in the OBC value and press <Enter>, the other 2 values will be generated automatically based on the protocol you selected. Also, if you used a JP1 learning remote, there's a way to cut and paste all the codes which saves needing to enter them all. In IR, if you select File > Summary you get a page listing lots of stuff. If you scroll down, you'll see a list of learn decodes. You can cut and paste this list into Excel, then you can re-arrange the columns and just select the button names and OBC codes to cut and paste into RM. You can move the RM columns, so if the OBC column isn't the one next to the button names, you can move it there. 
:#Now tap on the Buttons Tab [[Image:RM-buttons.jpg]] This is where you map the defined functions onto the available buttons. Simply tap the Auto-Assign button which should allocate most of the buttons. For any buttons left in red drag the function name from the table on the left to the function column on the right. But note that not all these buttons are available on a Slingplayer Generic Remote. For example the 'Slow' and 'Eject' buttons do not exist on a Generic Remote. So only map the functions onto the buttons that actually exist (You will see that when you check out the Layout Tab, and from experience when you have done this a few times). The important ones to note are the Custom 10-29 buttons. These are the ones you use for the functions you need that aren't on the generic remote and they subsequently appear in the drop down menu of the remote as Custom options (except for Custom 22-26 which are pre-allocated to the colour buttons). 
:#Now tap on the Layout Tab. [[Image:RM-layout.jpg]] This shows the generic Slingplayer remote and shows the buttons you can actually use in the Buttons Tab. If a button shows yellow then that means it is in use. If it shows black (the PgUp/PgDn in the picture) then has not been allocated a function. Again you can drag and drop functions onto a button. 
:#Once you have finished experimenting go back to the Setup tab. Select the appropriate Slingbox remote, go to the 'Advanced' menu at the top and select 'Export Binary Upgrade'. This will produce the BIN file that we have discussed in previous Sections. If you aren‟t sure which Slingbox Chip you have then create a BIN file for the main 2 chips, so that would give you something like 
:::C2010_PL.BIN
:::C2010_RV.BIN

So now you can go back to [[#Installing_the_Binary_file_to_the_Slingbox.|Section 4]] and install the new Custom Remote onto your Slingbox. 
====Finding Missing Codes====
You can often find yourself in the position where the Custom Remote generally works OK but some of the functions are missing or some are sending the wrong code. This is relatively easy to fix by trial and error. The OBC codes must lie between 0-255, so the first thing to do is make a list of the OBC codes that are not being used in the Remote Control. Now use Remotemaster to allocate those codes to the 0-9 buttons and the 15 Custom buttons. Now build a new BIN files, replace the one in your \SBAV\ folder and rerun the "Setup Video Sources" routine. Now try those buttons and see if any of them action the missing function. If you find the missing codes then you can update the original remote file. You may have to repeat this operation 10 times to cover all the missing codes, although you can cut down the number of times by also using the Transport buttons (Play/Pause…) and Channel, Page +/- buttons as well. 

=='''Give your Binary file back to the Community'''==
Finally, remember that it is good to payback. If you find a remote file that works for you then upload it to the JP1 Forums. The way to do this is: 
#Put the 4 Binary files and the Remote Master RMDU file into a ZIP file. I also tend to add a Readme file in case users are unsure how to use the files. Although hopefully they will have read this article and will know what to do. 
#To be really helpful, you should upload your files in 3 different places:
##Upload your ZIP file to the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=87 Slingbox Binary Files] area.
##Upload the Remote Master RMDU source file to the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=98 Slingbox RM Files] area.
##Upload the RMDU file to the appropriate area in the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=4 Device Upgrades] area.
 
I hope these instructions have been helpful. If you have any suggestions for changes or improvements please E-mail me at '''alan (at) rmrsoft (dot) com'''

How to Create Custom Remote Controls and use them on your Slingbox

2016-04-07T16:19:48Z

Alanrichey: /* Hardware */

Written by: Al Richey 

=='''Background information'''==
One of the most common posts on the support site is about remote codes for unsupported devices. So if you find yourself in this situation I hope this will help. Before detailing the steps to go through there are some basic things you need to understand (this isn‟t essential reading but everything will make much more sense if you do know the details)
==='''Different UEI Chips'''===
: There were five different chips used in Slingboxes. These are designated as JU, PK, PL, RV & JB. If you want to check your type you can verify your IR blaster version in the Slingbox Properties dialog. Then match the IR version number with the chip type using the chart below.
#JU (VERY old US boxes)
#PL (current US boxes)
#PK (never used)
#RV (old European boxes)
#JB (All modern Slingboxes, but compatible with PL files)

So unless you have an old European Solo all you need is the PL file.

==='''Slingplayer Compatibility'''===
: In older versions of Slingplayer it was possible to change the look of the Custom Remote skin‟. Since Slingplayer V1.5 this functionality has been removed and as far as the look of the Remote is concerned you are stuck with the Generic design produced by Sling Media. All we can do is change the codes that are sent when a specific button is pressed. One drawback of the Generic Remote is that it has only the main buttons, so extra buttons on other remotes (such as Audio/Setup…) can not be mapped directly. What we have to do is put them into a Custom Menu which is accessed by tapping on the Menu button on the Generic Remote or right-clicking on the image. (Note: If a remote image has already been produced by Sling it is possible to use that image instead of the generic image, just contact me at alan@rmrsoft.com)
:

==='''Setup Code Nomenclature'''===
: When you run the Configure Inputs routines in the various Slingplayers and select a supported device, what actually happens is that a Binary Code is downloaded to the Slingbox. 
: This Binary Code details the IR codes that are sent when a specific button is pressed on the remote. Unfortunately the native Slingbox software doesn't use separate binary files that we can edit, their codes are apparently compressed and packaged into special files that we can't do anything with (that I know of). But what we can do instead of editing the built-in codes is to use a separate external upgrade code file. These files have the format such as "C1234_PL.BIN". 
: The first letter of the file describes the type of device, the main ones we are interested in are:

::V which is for VCRs, which encompasses PVRs, DVRs and other recorders
::S which is for Satellite and FTA set top boxes
::C which is for Cable boxes
::Y which is for DVD Players

:This is followed by a 4-digit code number. For Slingboxes the code numbers can be between 0000-2047 (actually higher in newer Slingboxes but to stay safe we are better staying below 2047). In general, codes below 2000 actually relate to specific boxes, for example V0618 is the code for a TIVO and D0032 is the code for a Pioneer CD Player. But we can feel fairly safe using 2000-2047 for our own codes. The final part of the filename defines the chip for which it will run. 
: So if you were looking for the binary file for a PVR with a code number allocated 1234, designed to run on a PL-equipped Slingbox, you would be searching for a file called V1234_PL.BIN. Note: You must NEVER change the name of the file, as the letter, code number and chip type are also defined inside the file itself.

==='''JP1'''===
:You will hear a lot about "JP1". Basically this is a process whereby people using "One For All‟ (OFA) remote controls can add new codes to their remotes from their PC. The remote control processor inside the Slingbox is made by the same company that makes OFA remotes, so the upgrades are similar. The JP1 tools have been upgraded so that we can now use them to create and modify upgrades for the Slingbox.

=='''The Basic Procedure.'''==
The official procedure to follow is to report the [http://support.slingmedia.com/get/KB-005640.html Lack of a Supported Remote] to SlingMedia and they will add it to the database. In practice, they are not quick at doing this (I have been asking for a remote for over 4 years now), and the updated remote list seems to be only occasionally updated. That may change in the future but for now it is really not a practical quick solution. So for a short term fix what you need to do is to create or acquire the correct Binary code file for your A/V device, and then install it into your Slingbox. This installation process is covered in detail in [[#Installing_the_Binary_file_to_the_Slingbox|Section 4]], so first let‟s see where you can look for these files. 

=='''Obtaining the Binary file for the Custom Remote'''==

#Before starting, make sure in the setup wizard you have tried all the devices by that same manufacturer, even if the model number does not match, and all the associated code numbers. It's also worth trying your TV Provider in case they have 'badged' someone else's box. You might be lucky and find one that works and that will save a lot of work. If that doesn't solve the problem here is the step by step approach to getting hold of your binary file: 
#Go to the JP1 forum. This has a specific Download area for [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=87 Slingbox Custom Remotes], so go through all those to see if your device has already been done. 
#If it isn‟t there the JP1 forum also has a more general [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=4 File Download Area]. From this page you select the download area for the specific type of device and check there. If you are lucky you will find a source file for using in the program RemoteMaster (RM or KM files), the use of which is discussed in [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]]. 
#Have a look on the Hava forums. They are also using the same chips and the files might be there. Check out this [http://www.myhava.com/forum/viewforum.php?f=17&st=0&sk=t&sd=d&start=0 forum]. You‟re looking for a PK or PL file. They can be imported into Remote Master and then converted to the PK, PL, RV or JU files for the Slingbox. Again this is discussed in [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]]. 
#Do it yourself by buying a Nevo C2, or an IR Widget, and learn the codes needed to control the device. How to do this is covered in [[#Learning_the_IR_codes_from_your_own_remote|Section 5]] & [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]]. 
#Ask someone else to do the work for you. You can try this by posting a request for help in either:
##The [https://community.sling.com/content Slingbox Answers Forum].
##The [http://www.hifi-remote.com/forums/viewforum.php?f=19 JP1 forum]. 
I can normally install your device on my Harmony Universal Remote to mimic the original Remote and learn the codes for you (unless I am away on holiday). 

=='''Installing the Binary file to the Slingbox.'''==
 I have written a comprehensive Installation Guide at

http://placeshiftingenthusiasts.com/how-to-install-a-custom-remote-onto-the-slingbox/

Once you have completed the setup and the BIN files have been downloaded to the Slingbox they are not used any more and can be deleted.

=='''Learning the IR codes from your own remote.'''==
==='''Requirements'''===
Assuming you have decided to create the Remote Binary File yourself, the first stage is to learn the codes from your original Remote. This is what you need:
====Hardware====
#A computer with a USB port. 
#A A Nevo C2 Learning Remote (Available on E-Bay for $20 or so) or alternatively

:An IR learning "widget". I got mine from Tommy Tyler through https://www.tindie.com/products/TommyTyler/ir-widget-infrared-remote-control-signal-recorderanalyzer/ (My preferred solution). 

====Software====
:If you are using the Nevo C2: [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=81 RM/RMIR.EXE] [http://www.hifi-remote.com/forums/dload.php?action=file&file_id=7201 RDF Files] These are support files for the program. If you are using an IR Widget: [http://www.compendiumarcana.com/irwidget/irscope.zip IRSCOPE.EXE] [http://www.ftdichip.com/Drivers/VCP.htm The drivers] [http://www.hifi-remote.com/forums/dload.php?action=file&file_id=922 The IR decode DLL] Or download [http://rmrsoft.com/remote.zip my full IRSCOPE/REMOTEMASTER package]. Much of the JP1 software needs the java runtime environment (JRE) as well. A lot of computers will already have it installed already, but if you need it you can [http://java.sun/j2se/1.4.2/download.html download] Now we can learn the codes. First we will cover the procedure using a Learning Remote, then cover it using an IR Widget. 

===USING A LEARNING REMOTE===
====Getting the Codes from your Remote====
Follow the instructions to learn your remote codes so the Nevo C2 operates your device. Then download the settings file onto your PC.

====Getting the Codes onto your PC.====
 
:#Install RMIR.EXE onto your PC. It comes as a ZIP file rather than an installation package, which you need to unzip to your PC. The files can actually go anywhere but as a bit of tidy person (geek?) I created a C:\Program Files\IR\ folder and put the files in there and then created a shortcut on the Desktop. 
:#Now click the "Import" in RMIR

(Under construction)

However, if you see a screen like this, it means that the protocol used by your remote is not recognised by the system. That means that you cannot create the Remote yourself but will have to ask the people on the JP1 forum to help you out. They have a much deeper understanding of the IR formats, and can often dig deeper into the signals and figure out the codes. [[Image:IR-learned2.jpg]] 
The procedure to do this is to use the File > Save As menu option to save the IR source file(s) (I tend to ZIP them up if there are more than one). Now upload them to the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=35 Diagnosis Area] in the File Section of the JP1 Forum. 
Check the file has been added, and make a record of it‟s location by right-clicking on it and select „Copy Link Location‟. 
Now create a new topic in the [http://www.hifi-remote.com/forums/viewforum.php?f=20 Protocol Decode Forum] and plead for some help, quoting the device Manufacturer and Model Number and the link to the IR source files. Offer incentives (money, beer, everlasting gratitude….) and you might be lucky. The experts may produce the RemoteMaster source file or even the Remote Binary files themselves. Now you can move on to [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]] for building the Remote BIN files. 

===USING AN IR WIDGET===
If you are using an IR Widget there is an excellent guide [http://freepdfhosting.com/6ea1213d67.pdf here] on the Tindle site. So I suggest you download that and read it thoroughly. There is no point in repeating it here, but just to emphasise a few points: 
:#You will want to regularly check for updates to the decodeir.dll. As new protocols are recognized, this dll will change. 
:#There is no way to save the learned values for importing into RemoteMaster (where you will make the remote) so you will need to write them down. 
:#Although I tend to put programs into C:\Program Files\.... this can be a bit dodgy in Windows as programs cannot save files to this area because of security limitations. So it might be safer to install it under \Documents\ 
:#The Guide has a very useful section comparing using a Learning Remotes and the IR Widget and highlighting the differences, (For example "Key" is equivalent to "OBC") so you could check out the previous sub-section covering using IR.EXE and the Learning Remote. And then you will understand this section. When complete you can move onto [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]] to create the Binary file. 

=='''Creating your own Binary files using RemoteMaster'''==
:#To make life easier I have packaged a full set of the latest files required and uploaded them to my site. Just download them from [http://www.rmrsoft.com/remote.zip here] and unzip them onto your computer. 
:#Start RemoteMaster.EXE. You may be promoted to highlight the folder the folder that contains the RDF files (Highlight the \RDF\ folder in the folder where you placed Remotemaster). You may also have to do the same for the Images folder. The display will now look something like this:[[Image:RM-setup.jpg]] 
:#If you have obtained an .rmdu file then use the File > Open menu option to load the file. If you have obtained a .bin file then use the Advanced > Import Binary Upgrade to load up the details. If you have not obtained a file then you will have to input the codes manually. 
:#Now to explain the main Setup Tab: '''Description ''': Use anything you like, I tend to use the device name. '''Remote''': Select the one appropriate for your chip. '''Device Type''': Should be set to the correct type of device (as covered in Paragraph 3 of Section 1). '''Setup Code''': This is where you put the 4-digit code. In theory it can be any number between 0000 and 2047, but as explained in Section 1 Paragraph 3, numbers below 2000 may actually be already allocated to specific devices, so to be safe I personally use 2010. Fell free to use your own value. '''Protocol''': From the dropdown list select the Protocol you discovered when you used IR.EXE/IRSCOPE.EXE. '''Device''': Type in the Device code you recorded from IR.EXE/IRSCOPE.EXE. '''Sub-Device''': If applicable type in the Sub-Device code you recorded from IR.EXE/ IRSCOPE.EXE. 
:#Now tap on the Functions Tab [[Image:RM-functions.jpg]] This picture shows the program with an .rmdu file or .bin file already imported; otherwise the code columns will be blank. The entries are fully configurable, so if there are pre-defined functions that you do not need (pip swap, pipmove..) then you highlight them and tap the "Delete" button. If you have a function that is not pre-defined (Audio, Setup…) then tap the "New" button and enter them. Now fill in the codes for each button that you recorded. You just put in the OBC value and press <Enter>, the other 2 values will be generated automatically based on the protocol you selected. Also, if you used a JP1 learning remote, there's a way to cut and paste all the codes which saves needing to enter them all. In IR, if you select File > Summary you get a page listing lots of stuff. If you scroll down, you'll see a list of learn decodes. You can cut and paste this list into Excel, then you can re-arrange the columns and just select the button names and OBC codes to cut and paste into RM. You can move the RM columns, so if the OBC column isn't the one next to the button names, you can move it there. 
:#Now tap on the Buttons Tab [[Image:RM-buttons.jpg]] This is where you map the defined functions onto the available buttons. Simply tap the Auto-Assign button which should allocate most of the buttons. For any buttons left in red drag the function name from the table on the left to the function column on the right. But note that not all these buttons are available on a Slingplayer Generic Remote. For example the 'Slow' and 'Eject' buttons do not exist on a Generic Remote. So only map the functions onto the buttons that actually exist (You will see that when you check out the Layout Tab, and from experience when you have done this a few times). The important ones to note are the Custom 10-29 buttons. These are the ones you use for the functions you need that aren't on the generic remote and they subsequently appear in the drop down menu of the remote as Custom options (except for Custom 22-26 which are pre-allocated to the colour buttons). 
:#Now tap on the Layout Tab. [[Image:RM-layout.jpg]] This shows the generic Slingplayer remote and shows the buttons you can actually use in the Buttons Tab. If a button shows yellow then that means it is in use. If it shows black (the PgUp/PgDn in the picture) then has not been allocated a function. Again you can drag and drop functions onto a button. 
:#Once you have finished experimenting go back to the Setup tab. Select the appropriate Slingbox remote, go to the 'Advanced' menu at the top and select 'Export Binary Upgrade'. This will produce the BIN file that we have discussed in previous Sections. If you aren‟t sure which Slingbox Chip you have then create a BIN file for the main 2 chips, so that would give you something like 
:::C2010_PL.BIN
:::C2010_RV.BIN

So now you can go back to [[#Installing_the_Binary_file_to_the_Slingbox.|Section 4]] and install the new Custom Remote onto your Slingbox. 
====Finding Missing Codes====
You can often find yourself in the position where the Custom Remote generally works OK but some of the functions are missing or some are sending the wrong code. This is relatively easy to fix by trial and error. The OBC codes must lie between 0-255, so the first thing to do is make a list of the OBC codes that are not being used in the Remote Control. Now use Remotemaster to allocate those codes to the 0-9 buttons and the 15 Custom buttons. Now build a new BIN files, replace the one in your \SBAV\ folder and rerun the "Setup Video Sources" routine. Now try those buttons and see if any of them action the missing function. If you find the missing codes then you can update the original remote file. You may have to repeat this operation 10 times to cover all the missing codes, although you can cut down the number of times by also using the Transport buttons (Play/Pause…) and Channel, Page +/- buttons as well. 

=='''Give your Binary file back to the Community'''==
Finally, remember that it is good to payback. If you find a remote file that works for you then upload it to the JP1 Forums. The way to do this is: 
#Put the 4 Binary files and the Remote Master RMDU file into a ZIP file. I also tend to add a Readme file in case users are unsure how to use the files. Although hopefully they will have read this article and will know what to do. 
#To be really helpful, you should upload your files in 3 different places:
##Upload your ZIP file to the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=87 Slingbox Binary Files] area.
##Upload the Remote Master RMDU source file to the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=98 Slingbox RM Files] area.
##Upload the RMDU file to the appropriate area in the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=4 Device Upgrades] area.
 
I hope these instructions have been helpful. If you have any suggestions for changes or improvements please E-mail me at '''alan (at) rmrsoft (dot) com'''

How to Create Custom Remote Controls and use them on your Slingbox

2016-04-07T16:18:41Z

Alanrichey:

Written by: Al Richey 

=='''Background information'''==
One of the most common posts on the support site is about remote codes for unsupported devices. So if you find yourself in this situation I hope this will help. Before detailing the steps to go through there are some basic things you need to understand (this isn‟t essential reading but everything will make much more sense if you do know the details)
==='''Different UEI Chips'''===
: There were five different chips used in Slingboxes. These are designated as JU, PK, PL, RV & JB. If you want to check your type you can verify your IR blaster version in the Slingbox Properties dialog. Then match the IR version number with the chip type using the chart below.
#JU (VERY old US boxes)
#PL (current US boxes)
#PK (never used)
#RV (old European boxes)
#JB (All modern Slingboxes, but compatible with PL files)

So unless you have an old European Solo all you need is the PL file.

==='''Slingplayer Compatibility'''===
: In older versions of Slingplayer it was possible to change the look of the Custom Remote skin‟. Since Slingplayer V1.5 this functionality has been removed and as far as the look of the Remote is concerned you are stuck with the Generic design produced by Sling Media. All we can do is change the codes that are sent when a specific button is pressed. One drawback of the Generic Remote is that it has only the main buttons, so extra buttons on other remotes (such as Audio/Setup…) can not be mapped directly. What we have to do is put them into a Custom Menu which is accessed by tapping on the Menu button on the Generic Remote or right-clicking on the image. (Note: If a remote image has already been produced by Sling it is possible to use that image instead of the generic image, just contact me at alan@rmrsoft.com)
:

==='''Setup Code Nomenclature'''===
: When you run the Configure Inputs routines in the various Slingplayers and select a supported device, what actually happens is that a Binary Code is downloaded to the Slingbox. 
: This Binary Code details the IR codes that are sent when a specific button is pressed on the remote. Unfortunately the native Slingbox software doesn't use separate binary files that we can edit, their codes are apparently compressed and packaged into special files that we can't do anything with (that I know of). But what we can do instead of editing the built-in codes is to use a separate external upgrade code file. These files have the format such as "C1234_PL.BIN". 
: The first letter of the file describes the type of device, the main ones we are interested in are:

::V which is for VCRs, which encompasses PVRs, DVRs and other recorders
::S which is for Satellite and FTA set top boxes
::C which is for Cable boxes
::Y which is for DVD Players

:This is followed by a 4-digit code number. For Slingboxes the code numbers can be between 0000-2047 (actually higher in newer Slingboxes but to stay safe we are better staying below 2047). In general, codes below 2000 actually relate to specific boxes, for example V0618 is the code for a TIVO and D0032 is the code for a Pioneer CD Player. But we can feel fairly safe using 2000-2047 for our own codes. The final part of the filename defines the chip for which it will run. 
: So if you were looking for the binary file for a PVR with a code number allocated 1234, designed to run on a PL-equipped Slingbox, you would be searching for a file called V1234_PL.BIN. Note: You must NEVER change the name of the file, as the letter, code number and chip type are also defined inside the file itself.

==='''JP1'''===
:You will hear a lot about "JP1". Basically this is a process whereby people using "One For All‟ (OFA) remote controls can add new codes to their remotes from their PC. The remote control processor inside the Slingbox is made by the same company that makes OFA remotes, so the upgrades are similar. The JP1 tools have been upgraded so that we can now use them to create and modify upgrades for the Slingbox.

=='''The Basic Procedure.'''==
The official procedure to follow is to report the [http://support.slingmedia.com/get/KB-005640.html Lack of a Supported Remote] to SlingMedia and they will add it to the database. In practice, they are not quick at doing this (I have been asking for a remote for over 4 years now), and the updated remote list seems to be only occasionally updated. That may change in the future but for now it is really not a practical quick solution. So for a short term fix what you need to do is to create or acquire the correct Binary code file for your A/V device, and then install it into your Slingbox. This installation process is covered in detail in [[#Installing_the_Binary_file_to_the_Slingbox|Section 4]], so first let‟s see where you can look for these files. 

=='''Obtaining the Binary file for the Custom Remote'''==

#Before starting, make sure in the setup wizard you have tried all the devices by that same manufacturer, even if the model number does not match, and all the associated code numbers. It's also worth trying your TV Provider in case they have 'badged' someone else's box. You might be lucky and find one that works and that will save a lot of work. If that doesn't solve the problem here is the step by step approach to getting hold of your binary file: 
#Go to the JP1 forum. This has a specific Download area for [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=87 Slingbox Custom Remotes], so go through all those to see if your device has already been done. 
#If it isn‟t there the JP1 forum also has a more general [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=4 File Download Area]. From this page you select the download area for the specific type of device and check there. If you are lucky you will find a source file for using in the program RemoteMaster (RM or KM files), the use of which is discussed in [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]]. 
#Have a look on the Hava forums. They are also using the same chips and the files might be there. Check out this [http://www.myhava.com/forum/viewforum.php?f=17&st=0&sk=t&sd=d&start=0 forum]. You‟re looking for a PK or PL file. They can be imported into Remote Master and then converted to the PK, PL, RV or JU files for the Slingbox. Again this is discussed in [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]]. 
#Do it yourself by buying a Nevo C2, or an IR Widget, and learn the codes needed to control the device. How to do this is covered in [[#Learning_the_IR_codes_from_your_own_remote|Section 5]] & [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]]. 
#Ask someone else to do the work for you. You can try this by posting a request for help in either:
##The [https://community.sling.com/content Slingbox Answers Forum].
##The [http://www.hifi-remote.com/forums/viewforum.php?f=19 JP1 forum]. 
I can normally install your device on my Harmony Universal Remote to mimic the original Remote and learn the codes for you (unless I am away on holiday). 

=='''Installing the Binary file to the Slingbox.'''==
 I have written a comprehensive Installation Guide at

http://placeshiftingenthusiasts.com/how-to-install-a-custom-remote-onto-the-slingbox/

Once you have completed the setup and the BIN files have been downloaded to the Slingbox they are not used any more and can be deleted.

=='''Learning the IR codes from your own remote.'''==
==='''Requirements'''===
Assuming you have decided to create the Remote Binary File yourself, the first stage is to learn the codes from your original Remote. This is what you need:
====Hardware====
#A computer with a USB port. 
#A A Nevo C2 Learning Remote (Available on E-Bay for $20 or so)

:or alternatively

:An IR learning "widget". I got mine from Tommy Tyler through https://www.tindie.com/products/TommyTyler/ir-widget-infrared-remote-control-signal-recorderanalyzer/ (My preferred solution). 

====Software====
:If you are using the Nevo C2: [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=81 RM/RMIR.EXE] [http://www.hifi-remote.com/forums/dload.php?action=file&file_id=7201 RDF Files] These are support files for the program. If you are using an IR Widget: [http://www.compendiumarcana.com/irwidget/irscope.zip IRSCOPE.EXE] [http://www.ftdichip.com/Drivers/VCP.htm The drivers] [http://www.hifi-remote.com/forums/dload.php?action=file&file_id=922 The IR decode DLL] Or download [http://rmrsoft.com/remote.zip my full IRSCOPE/REMOTEMASTER package]. Much of the JP1 software needs the java runtime environment (JRE) as well. A lot of computers will already have it installed already, but if you need it you can [http://java.sun/j2se/1.4.2/download.html download] Now we can learn the codes. First we will cover the procedure using a Learning Remote, then cover it using an IR Widget. 

===USING A LEARNING REMOTE===
====Getting the Codes from your Remote====
Follow the instructions to learn your remote codes so the Nevo C2 operates your device. Then download the settings file onto your PC.

====Getting the Codes onto your PC.====
 
:#Install RMIR.EXE onto your PC. It comes as a ZIP file rather than an installation package, which you need to unzip to your PC. The files can actually go anywhere but as a bit of tidy person (geek?) I created a C:\Program Files\IR\ folder and put the files in there and then created a shortcut on the Desktop. 
:#Now click the "Import" in RMIR

(Under construction)

However, if you see a screen like this, it means that the protocol used by your remote is not recognised by the system. That means that you cannot create the Remote yourself but will have to ask the people on the JP1 forum to help you out. They have a much deeper understanding of the IR formats, and can often dig deeper into the signals and figure out the codes. [[Image:IR-learned2.jpg]] 
The procedure to do this is to use the File > Save As menu option to save the IR source file(s) (I tend to ZIP them up if there are more than one). Now upload them to the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=35 Diagnosis Area] in the File Section of the JP1 Forum. 
Check the file has been added, and make a record of it‟s location by right-clicking on it and select „Copy Link Location‟. 
Now create a new topic in the [http://www.hifi-remote.com/forums/viewforum.php?f=20 Protocol Decode Forum] and plead for some help, quoting the device Manufacturer and Model Number and the link to the IR source files. Offer incentives (money, beer, everlasting gratitude….) and you might be lucky. The experts may produce the RemoteMaster source file or even the Remote Binary files themselves. Now you can move on to [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]] for building the Remote BIN files. 

===USING AN IR WIDGET===
If you are using an IR Widget there is an excellent guide [http://freepdfhosting.com/6ea1213d67.pdf here] on the Tindle site. So I suggest you download that and read it thoroughly. There is no point in repeating it here, but just to emphasise a few points: 
:#You will want to regularly check for updates to the decodeir.dll. As new protocols are recognized, this dll will change. 
:#There is no way to save the learned values for importing into RemoteMaster (where you will make the remote) so you will need to write them down. 
:#Although I tend to put programs into C:\Program Files\.... this can be a bit dodgy in Windows as programs cannot save files to this area because of security limitations. So it might be safer to install it under \Documents\ 
:#The Guide has a very useful section comparing using a Learning Remotes and the IR Widget and highlighting the differences, (For example "Key" is equivalent to "OBC") so you could check out the previous sub-section covering using IR.EXE and the Learning Remote. And then you will understand this section. When complete you can move onto [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]] to create the Binary file. 

=='''Creating your own Binary files using RemoteMaster'''==
:#To make life easier I have packaged a full set of the latest files required and uploaded them to my site. Just download them from [http://www.rmrsoft.com/remote.zip here] and unzip them onto your computer. 
:#Start RemoteMaster.EXE. You may be promoted to highlight the folder the folder that contains the RDF files (Highlight the \RDF\ folder in the folder where you placed Remotemaster). You may also have to do the same for the Images folder. The display will now look something like this:[[Image:RM-setup.jpg]] 
:#If you have obtained an .rmdu file then use the File > Open menu option to load the file. If you have obtained a .bin file then use the Advanced > Import Binary Upgrade to load up the details. If you have not obtained a file then you will have to input the codes manually. 
:#Now to explain the main Setup Tab: '''Description ''': Use anything you like, I tend to use the device name. '''Remote''': Select the one appropriate for your chip. '''Device Type''': Should be set to the correct type of device (as covered in Paragraph 3 of Section 1). '''Setup Code''': This is where you put the 4-digit code. In theory it can be any number between 0000 and 2047, but as explained in Section 1 Paragraph 3, numbers below 2000 may actually be already allocated to specific devices, so to be safe I personally use 2010. Fell free to use your own value. '''Protocol''': From the dropdown list select the Protocol you discovered when you used IR.EXE/IRSCOPE.EXE. '''Device''': Type in the Device code you recorded from IR.EXE/IRSCOPE.EXE. '''Sub-Device''': If applicable type in the Sub-Device code you recorded from IR.EXE/ IRSCOPE.EXE. 
:#Now tap on the Functions Tab [[Image:RM-functions.jpg]] This picture shows the program with an .rmdu file or .bin file already imported; otherwise the code columns will be blank. The entries are fully configurable, so if there are pre-defined functions that you do not need (pip swap, pipmove..) then you highlight them and tap the "Delete" button. If you have a function that is not pre-defined (Audio, Setup…) then tap the "New" button and enter them. Now fill in the codes for each button that you recorded. You just put in the OBC value and press <Enter>, the other 2 values will be generated automatically based on the protocol you selected. Also, if you used a JP1 learning remote, there's a way to cut and paste all the codes which saves needing to enter them all. In IR, if you select File > Summary you get a page listing lots of stuff. If you scroll down, you'll see a list of learn decodes. You can cut and paste this list into Excel, then you can re-arrange the columns and just select the button names and OBC codes to cut and paste into RM. You can move the RM columns, so if the OBC column isn't the one next to the button names, you can move it there. 
:#Now tap on the Buttons Tab [[Image:RM-buttons.jpg]] This is where you map the defined functions onto the available buttons. Simply tap the Auto-Assign button which should allocate most of the buttons. For any buttons left in red drag the function name from the table on the left to the function column on the right. But note that not all these buttons are available on a Slingplayer Generic Remote. For example the 'Slow' and 'Eject' buttons do not exist on a Generic Remote. So only map the functions onto the buttons that actually exist (You will see that when you check out the Layout Tab, and from experience when you have done this a few times). The important ones to note are the Custom 10-29 buttons. These are the ones you use for the functions you need that aren't on the generic remote and they subsequently appear in the drop down menu of the remote as Custom options (except for Custom 22-26 which are pre-allocated to the colour buttons). 
:#Now tap on the Layout Tab. [[Image:RM-layout.jpg]] This shows the generic Slingplayer remote and shows the buttons you can actually use in the Buttons Tab. If a button shows yellow then that means it is in use. If it shows black (the PgUp/PgDn in the picture) then has not been allocated a function. Again you can drag and drop functions onto a button. 
:#Once you have finished experimenting go back to the Setup tab. Select the appropriate Slingbox remote, go to the 'Advanced' menu at the top and select 'Export Binary Upgrade'. This will produce the BIN file that we have discussed in previous Sections. If you aren‟t sure which Slingbox Chip you have then create a BIN file for the main 2 chips, so that would give you something like 
:::C2010_PL.BIN
:::C2010_RV.BIN

So now you can go back to [[#Installing_the_Binary_file_to_the_Slingbox.|Section 4]] and install the new Custom Remote onto your Slingbox. 
====Finding Missing Codes====
You can often find yourself in the position where the Custom Remote generally works OK but some of the functions are missing or some are sending the wrong code. This is relatively easy to fix by trial and error. The OBC codes must lie between 0-255, so the first thing to do is make a list of the OBC codes that are not being used in the Remote Control. Now use Remotemaster to allocate those codes to the 0-9 buttons and the 15 Custom buttons. Now build a new BIN files, replace the one in your \SBAV\ folder and rerun the "Setup Video Sources" routine. Now try those buttons and see if any of them action the missing function. If you find the missing codes then you can update the original remote file. You may have to repeat this operation 10 times to cover all the missing codes, although you can cut down the number of times by also using the Transport buttons (Play/Pause…) and Channel, Page +/- buttons as well. 

=='''Give your Binary file back to the Community'''==
Finally, remember that it is good to payback. If you find a remote file that works for you then upload it to the JP1 Forums. The way to do this is: 
#Put the 4 Binary files and the Remote Master RMDU file into a ZIP file. I also tend to add a Readme file in case users are unsure how to use the files. Although hopefully they will have read this article and will know what to do. 
#To be really helpful, you should upload your files in 3 different places:
##Upload your ZIP file to the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=87 Slingbox Binary Files] area.
##Upload the Remote Master RMDU source file to the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=98 Slingbox RM Files] area.
##Upload the RMDU file to the appropriate area in the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=4 Device Upgrades] area.
 
I hope these instructions have been helpful. If you have any suggestions for changes or improvements please E-mail me at '''alan (at) rmrsoft (dot) com'''

How to Create Custom Remote Controls and use them on your Slingbox

2016-01-14T08:27:59Z

Alanrichey: /* USING AN IR WIDGET */

Written by: Al Richey 

With acknowledgements to Matt Whitlock, BrandonC, The Robman, Nuke12 and AndyBBB, who actually wrote much of this article. All I did was update and combine all the information into one document. 

=='''Background information'''==
One of the most common posts on the support site is about remote codes for unsupported devices. So if you find yourself in this situation I hope this will help. Before detailing the steps to go through there are some basic things you need to understand (this isn‟t essential reading but everything will make much more sense if you do know the details)
==='''Different UEI Chips'''===
: There were five different chips used in Slingboxes. These are designated as JU, PK, PL, RV & JB. If you want to check your type you can verify your IR blaster version in the Slingbox Properties dialog. Then match the IR version number with the chip type using the chart below.
#JU (VERY old US boxes)
#PL (current US boxes)
#PK (never used)
#RV (old European boxes)
#JB (All modern Slingboxes, but compatible with PL files)

So unless you have an old European Solo all you need is the PL file.

==='''Slingplayer Compatibility'''===
: In older versions of Slingplayer it was possible to change the look of the Custom Remote skin‟. Since Slingplayer V1.5 this functionality has been removed and as far as the look of the Remote is concerned you are stuck with the Generic design produced by Sling Media. All we can do is change the codes that are sent when a specific button is pressed. One drawback of the Generic Remote is that it has only the main buttons, so extra buttons on other remotes (such as Audio/Setup…) can not be mapped directly. What we have to do is put them into a Custom Menu which is accessed by tapping on the Menu button on the Generic Remote or right-clicking on the image. (Note: If a remote image has already been produced by Sling it is possible to use that image instead of the generic image)
:

==='''Setup Code Nomenclature'''===
: When you run the Configure Inputs routines in the various Slingplayers and select a supported device, what actually happens is that a Binary Code is downloaded to the Slingbox. 
: This Binary Code details the IR codes that are sent when a specific button is pressed on the remote. Unfortunately the native Slingbox software doesn't use separate binary files that we can edit, their codes are apparently compressed and packaged into special files that we can't do anything with (that I know of). But what we can do instead of editing the built-in codes is to use a separate external upgrade code file. These files have the format such as "C1234_PL.BIN". 
: The first letter of the file describes the type of device, the main ones we are interested in are:
::V which is for VCRs, which encompasses PVRs, DVRs and other recorders
::S which is for Satellite and FTA set top boxes
::C which is for Cable boxes
::Y which is for DVD Players
::R which is for Tuners
:This is followed by a 4-digit code number. For Slingboxes the code numbers can be between 0000-2047 (actually higher in newer Slingboxes but to stay safe we are better staying below 2047). In general, codes below 2000 actually relate to specific boxes, for example V0618 is the code for a TIVO and D0032 is the code for a Pioneer CD Player. But we can feel fairly safe using 2000-2047 for our own codes. The final part of the filename defines the chip for which it will run. 
: So if you were looking for the binary file for a PVR with a code number allocated 1234, designed to run on a PL-equipped Slingbox, you would be searching for a file called V1234_PL.BIN. Note: You must NEVER change the name of the file, as the letter, code number and chip type are also defined inside the file itself.

==='''JP1'''===
:You will hear a lot about "JP1". Basically this is a process whereby people using "One For All‟ (OFA) remote controls can add new codes to their remotes from their PC. The remote control processor inside the Slingbox is made by the same company that makes OFA remotes, so the upgrades are similar. The JP1 tools have been upgraded so that we can now use them to create and modify upgrades for the Slingbox.

=='''The Basic Procedure.'''==
The official procedure to follow is to report the [http://support.slingmedia.com/get/KB-005640.html Lack of a Supported Remote] to SlingMedia and they will add it to the database. In practice, they are not quick at doing this (I have been asking for a remote for over 2 years now), and the updated remote list seems to be only occasionally updated. That may change in the future but for now it is really not a practical quick solution. So for a short term fix what you need to do is to create or acquire the correct Binary code file for your A/V device, and then install it into your Slingbox. This installation process is covered in detail in [[#Installing_the_Binary_file_to_the_Slingbox|Section 4]], so first let‟s see where you can look for these files. 

=='''Obtaining the Binary file for the Custom Remote'''==

#Before starting, make sure in the setup wizard you have tried all the devices by that same manufacturer, even if the model number does not match, and all the associated code numbers. You might be lucky and find one that works and that will save a lot of work. If that doesn‟t solve the problem here is the step by step approach to getting hold of your binary file: 
#Go to the JP1 forum. This has a specific Download area for [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=87 Slingbox Custom Remotes], so go through all those to see if your device has already been done. 
#If it isn‟t there the JP1 forum also has a more general [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=4 File Download Area]. From this page you select the download area for the specific type of device and check there. If you are lucky you will find a source file for using in the program RemoteMaster (RM or KM files), the use of which is discussed in [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]]. 
#Have a look on the Hava forums. They are also using the same chips and the files might be there. Check out this [http://www.myhava.com/forum/viewforum.php?f=17&st=0&sk=t&sd=d&start=0 forum]. You‟re looking for a PK or PL file. They can be imported into Remote Master and then converted to the PK, PL, RV or JU files for the Slingbox. Again this is discussed in [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]]. 
#Find a friend with a Pronto remote. They have a very nice update system and can generate .ccf files that can be used with the tools on the JP1 site to generate the .bin file used by a Slingbox. However, this is not easy, and you will probably need help from the experts on the JP1 forum, but if you want to have a go on your own then you will need the [http://www.hifi-remote.com/forums/dload.php?action=file&file_id=1887 DecodeCCF] program, and [http://www.remotecentral.com/files/index.html .ccf] files. Note that the Pronto can also make .pcf files, but unfortunately we cannot decode those. 
If all of this fails, and you cannot get hold of a BIN file then the Remote will have to be built from scratch. You have 2 options here: 
#Do it yourself by buying a JP1.x learning remote (plus a JP1.x cable), or an IR Widget, and learn the codes needed to control the device. How to do this is covered in [[#Learning_the_IR_codes_from_your_own_remote|Section 5]] & [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]]. 
#Ask someone else to do the work for you. You can try this by posting a request for help in either:
##The [https://community.sling.com/content Slingbox Answers Forum].
##The [http://www.hifi-remote.com/forums/viewforum.php?f=19 JP1 forum]. 
I can normally install your device on my Harmony Universal Remote to mimic the original Remote and learn the codes for you (unless I am away on holiday). 

=='''Installing the Binary file to the Slingbox.'''==
 I have written a comprehensive Installation Guide at

http://placeshiftingenthusiasts.com/how-to-install-a-custom-remote-onto-the-slingbox/

Once you have completed the setup and the BIN files have been downloaded to the Slingbox they are not used any more and can be deleted.

=='''Learning the IR codes from your own remote.'''==
==='''Requirements'''===
Assuming you have decided to create the Remote Binary File yourself, the first stage is to learn the codes from your original Remote. This is what you need:
====Hardware====
#A computer with a USB port (or you can use older serial ports). 
#A Learning Remote and an appropriate JP Cable. Almost any "One For All" or "Radio Shack" remote that has learning will work for this but examples are: 
::URC-6820 (JP1.2)
::URC-8820 (JP1.2)
::URC-10820 (JP1.2)
::Radio Shack Gamer 15-133 (JP1.3)
::Radios Shack Satelite15-134 (JP1.3) 

:Note that some remotes need a JP1.2 cable and some need a JP1.3 cable (and some older, discontinued remotes such as the URC-9810 use a JP1 cable). Make sure the Cable and Remote match. Again the [http://www.hifi-remote.com/forums/viewforum.php?f=10 JP1 forum] is a mine of information. 
:If you are not sure there is a [http://www.hifi-remote.com/forums/dload.php?action=file&file_id=2981 chart of remotes] where you can look up a specific remote to see which format it uses. If you want to buy a cable try [http://www.diygadget.com/ DIYgadget] for the cheaper serial JP1.2/3 cables.

:Although an easy solution is to get a Nevo C2, which has it's own built-in cable. These are available on E-Bay.

:or alternatively

:An IR learning "widget". I got mine from Tommy Tyler through https://www.tindie.com/products/TommyTyler/ir-widget-infrared-remote-control-signal-recorderanalyzer/ (My preferred solution). 

====Software====
:If you are using a Learning Remote: [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=81 RM/RMIR.EXE] [http://www.hifi-remote.com/forums/dload.php?action=file&file_id=7201 RDF Files] These are support files for the program. If you are using an IR Widget: [http://www.compendiumarcana.com/irwidget/irscope.zip IRSCOPE.EXE] [http://www.ftdichip.com/Drivers/VCP.htm The drivers] [http://www.hifi-remote.com/forums/dload.php?action=file&file_id=922 The IR decode DLL] Or download [http://rmrsoft.com/remote.zip my full IRSCOPE/REMOTEMASTER package]. Much of the JP1 software needs the java runtime environment (JRE) as well. A lot of computers will already have it installed already, but if you need it you can [http://java.sun/j2se/1.4.2/download.html download] Now we can learn the codes. First we will cover the procedure using a Learning Remote, then cover it using an IR Widget. 

===USING A LEARNING REMOTE===
====Getting the Codes from your Remote====
(These steps are based on using the older URC9810, the procedure will be slightly different for other Remotes so you will need to refer to the manuals.) 
:# Tap one of the buttons on the Learning Remote at the top which applies to the device you wish to create the bin file for. (eg. TV, DVD, Satellite). This is not totally necessary, you can always use TV, as it makes no difference to you, but if you subsequently upload the file for other users, it really ought to be for the correct type of device. 
:# At the bottom there will be a button called 'Set'. Keep your finger pushed on that until the LCD changes so you can modify your remote control. 
:# Click down until you come to an option called 'IR LEARN' and click select. 
:# Click one of the buttons on the remote control. For example, the '1' key, the LCD will say "Learning" and the red light will come on. 
:# Put your remote control in front of the learning remote and click the 1 key - if it is added correctly it should say 'Success'. If it fails (shows “Error”) then try again. There are a lot of different techniques for this procedure, the safest bet seems to be press the button on the Learning Remote, wait for 2 seconds then hold the equivalent key on the original Remote until the red light goes on. If you get a bad „learn‟, try just tapping quickly on the original key. A full description of these options is [http://www.hifi-remote.com/forums/viewtopic.php?t=3943 here]. 
:# Repeat this step for each of the keys you want to learn and have on your Slingbox Remote. If you get the "Memory Full" message then you will have to repeat this operation for the remaining keys after you have uploaded the first set of codes to your PC. 

====Getting the Codes onto your PC.====
 
:#Install IR.EXE onto your PC. It comes as a ZIP file rather than an installation package, which you need to unzip to your PC. The files can actually go anywhere but as a bit of tidy person (geek?) I created a C:\Program Files\IR\ folder and put the files in there and then created a shortcut on the Desktop. Important Note: For Windows VISTA users, I have found that I need to run the program in Windows XP Compatibility Mode to make it recognise the JP1 interface. Just right-click on IR.EXE, select Properties, then the Compatibility Tab and check the appropriate box. 
:#Create a sub folder called \RDF\ in whatever folder you have put the IR program and extract the RDF support files into that folder. 
:#Get your JP1 cable out and turn your remote control over, open the battery compartment and plug the JP1 6 pin connector into the Learning remote (you will see 6 needles where it plugs into). There are 2 ways to plug it in, but don‟t worry, you won‟t cause any damage by plugging it in the wrong way. Try them both if the first one fails. 
:#Plug the USB plug into your computer. As with any external piece of hardware you will need to install the drivers. There are drivers for the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=81 JP1 Remotes] and the [http://www.ftdichip.com/Drivers/VCP.htm JP1.2/3 Remotes]. Personally I use the JP1 ones dated 12 Feb 2008 and they work fine in Windows XP and also in Vista as long as the Windows XP Compatibility flag is set. 
:#Now open IR.exe. If you get told your RDF directory isn't valid, click OK and ignore this for now. It will look something like this: (Note this is a screenshot of V8.0. If that version hasn‟t been released yet, V7.15 looks very similar but does not have the icons at the top. [[Image:IR-general.jpg]] 
:#Go to File > Set Directory > RDF Path >. Select your RDF directory. You need to double click the RDF directory or it won't take. 
:#For peace of mind go to Interface > Check Driver... it should say the interface is connected. If it does then that's fine, if it gives an error message “Unable to open device, check connection” then it is not seeing the JP1 cable so you need to check the cable and the drivers. If it gives the error message “The remote is not acknowledging signals from the interface” then the cable is working fine but it is not seeing the remote. Try reversing the cable connection to the remote and hopefully that will cure the problem. 
:#Now click the "Download From Remote" button. 
:#Then click the "Learned Signals" tab (second from last one). It will look something like this: [[Image:IR-learned1.jpg]] 
:#On the left hand side there should be a list with the device type and the keys - eg "TV: 1". Click on it and details should show up in the right hand side listview. 
:#The first thing we need to make a note of is the Protocol (JVC) in this case, then the Device Number (239 in this case) and if it is displayed, the Sub-Device number. Then for each of the learned keys note down the OBC, Hex Code and EFC numbers. 
:#If you get the "MEM FULL" message on the Remote then Use File > Save As to keep a copy then tap the "Delete All" button, go back to the General Tab and tap the "Upload To remote" button to clear the Remote. Then learn the remaining buttons and follow the same procedure. Once they are all done, use the use the File > Save As command to save a copy of the final results. 
However, if you see a screen like this, it means that the protocol used by your remote is not recognised by the system. That means that you cannot create the Remote yourself but will have to ask the people on the JP1 forum to help you out. They have a much deeper understanding of the IR formats, and can often dig deeper into the signals and figure out the codes. [[Image:IR-learned2.jpg]] 
The procedure to do this is to use the File > Save As menu option to save the IR source file(s) (I tend to ZIP them up if there are more than one). Now upload them to the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=35 Diagnosis Area] in the File Section of the JP1 Forum. 
Check the file has been added, and make a record of it‟s location by right-clicking on it and select „Copy Link Location‟. 
Now create a new topic in the [http://www.hifi-remote.com/forums/viewforum.php?f=20 Protocol Decode Forum] and plead for some help, quoting the device Manufacturer and Model Number and the link to the IR source files. Offer incentives (money, beer, everlasting gratitude….) and you might be lucky. The experts may produce the RemoteMaster source file or even the Remote Binary files themselves. Now you can move on to [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]] for building the Remote BIN files. 

===USING AN IR WIDGET===
If you are using an IR Widget there is an excellent guide [http://freepdfhosting.com/6ea1213d67.pdf here] on the Tindle site. So I suggest you download that and read it thoroughly. There is no point in repeating it here, but just to emphasise a few points: 
:#You will want to regularly check for updates to the decodeir.dll. As new protocols are recognized, this dll will change. 
:#There is no way to save the learned values for importing into RemoteMaster (where you will make the remote) so you will need to write them down. 
:#Although I tend to put programs into C:\Program Files\.... this can be a bit dodgy in Windows as programs cannot save files to this area because of security limitations. So it might be safer to install it under \Documents\ 
:#The Guide has a very useful section comparing using a Learning Remotes and the IR Widget and highlighting the differences, (For example "Key" is equivalent to "OBC") so you could check out the previous sub-section covering using IR.EXE and the Learning Remote. And then you will understand this section. When complete you can move onto [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]] to create the Binary file. 

=='''Creating your own Binary files using RemoteMaster'''==
:#To make life easier I have packaged a full set of the latest files required and uploaded them to my site. Just download them from [http://www.rmrsoft.com/remote.zip here] and unzip them onto your computer. 
:#Start RemoteMaster.EXE. You may be promoted to highlight the folder the folder that contains the RDF files (Highlight the \RDF\ folder in the folder where you placed Remotemaster). You may also have to do the same for the Images folder. The display will now look something like this:[[Image:RM-setup.jpg]] 
:#If you have obtained an .rmdu file then use the File > Open menu option to load the file. If you have obtained a .bin file then use the Advanced > Import Binary Upgrade to load up the details. If you have not obtained a file then you will have to input the codes manually. 
:#Now to explain the main Setup Tab: '''Description ''': Use anything you like, I tend to use the device name. '''Remote''': Select the one appropriate for your chip. '''Device Type''': Should be set to the correct type of device (as covered in Paragraph 3 of Section 1). '''Setup Code''': This is where you put the 4-digit code. In theory it can be any number between 0000 and 2047, but as explained in Section 1 Paragraph 3, numbers below 2000 may actually be already allocated to specific devices, so to be safe I personally use 2010. Fell free to use your own value. '''Protocol''': From the dropdown list select the Protocol you discovered when you used IR.EXE/IRSCOPE.EXE. '''Device''': Type in the Device code you recorded from IR.EXE/IRSCOPE.EXE. '''Sub-Device''': If applicable type in the Sub-Device code you recorded from IR.EXE/ IRSCOPE.EXE. 
:#Now tap on the Functions Tab [[Image:RM-functions.jpg]] This picture shows the program with an .rmdu file or .bin file already imported; otherwise the code columns will be blank. The entries are fully configurable, so if there are pre-defined functions that you do not need (pip swap, pipmove..) then you highlight them and tap the "Delete" button. If you have a function that is not pre-defined (Audio, Setup…) then tap the "New" button and enter them. Now fill in the codes for each button that you recorded. You just put in the OBC value and press <Enter>, the other 2 values will be generated automatically based on the protocol you selected. Also, if you used a JP1 learning remote, there's a way to cut and paste all the codes which saves needing to enter them all. In IR, if you select File > Summary you get a page listing lots of stuff. If you scroll down, you'll see a list of learn decodes. You can cut and paste this list into Excel, then you can re-arrange the columns and just select the button names and OBC codes to cut and paste into RM. You can move the RM columns, so if the OBC column isn't the one next to the button names, you can move it there. 
:#Now tap on the Buttons Tab [[Image:RM-buttons.jpg]] This is where you map the defined functions onto the available buttons. Simply tap the Auto-Assign button which should allocate most of the buttons. For any buttons left in red drag the function name from the table on the left to the function column on the right. But note that not all these buttons are available on a Slingplayer Generic Remote. For example the 'Slow' and 'Eject' buttons do not exist on a Generic Remote. So only map the functions onto the buttons that actually exist (You will see that when you check out the Layout Tab, and from experience when you have done this a few times). The important ones to note are the Custom 10-29 buttons. These are the ones you use for the functions you need that aren't on the generic remote and they subsequently appear in the drop down menu of the remote as Custom options (except for Custom 22-26 which are pre-allocated to the colour buttons). 
:#Now tap on the Layout Tab. [[Image:RM-layout.jpg]] This shows the generic Slingplayer remote and shows the buttons you can actually use in the Buttons Tab. If a button shows yellow then that means it is in use. If it shows black (the PgUp/PgDn in the picture) then has not been allocated a function. Again you can drag and drop functions onto a button. 
:#Once you have finished experimenting go back to the Setup tab. Select the appropriate Slingbox remote, go to the 'Advanced' menu at the top and select 'Export Binary Upgrade'. This will produce the BIN file that we have discussed in previous Sections. If you aren‟t sure which Slingbox Chip you have then create a BIN file for the main 2 chips, so that would give you something like 
:::C2010_PL.BIN
:::C2010_RV.BIN

So now you can go back to [[#Installing_the_Binary_file_to_the_Slingbox.|Section 4]] and install the new Custom Remote onto your Slingbox. 
====Finding Missing Codes====
You can often find yourself in the position where the Custom Remote generally works OK but some of the functions are missing or some are sending the wrong code. This is relatively easy to fix by trial and error. The OBC codes must lie between 0-255, so the first thing to do is make a list of the OBC codes that are not being used in the Remote Control. Now use Remotemaster to allocate those codes to the 0-9 buttons and the 15 Custom buttons. Now build a new BIN files, replace the one in your \SBAV\ folder and rerun the "Setup Video Sources" routine. Now try those buttons and see if any of them action the missing function. If you find the missing codes then you can update the original remote file. You may have to repeat this operation 10 times to cover all the missing codes, although you can cut down the number of times by also using the Transport buttons (Play/Pause…) and Channel, Page +/- buttons as well. 

=='''Give your Binary file back to the Community'''==
Finally, remember that it is good to payback. If you find a remote file that works for you then upload it to the JP1 Forums. The way to do this is: 
#Put the 4 Binary files and the Remote Master RMDU file into a ZIP file. I also tend to add a Readme file in case users are unsure how to use the files. Although hopefully they will have read this article and will know what to do. 
#To be really helpful, you should upload your files in 3 different places:
##Upload your ZIP file to the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=87 Slingbox Binary Files] area.
##Upload the Remote Master RMDU source file to the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=98 Slingbox RM Files] area.
##Upload the RMDU file to the appropriate area in the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=4 Device Upgrades] area.
 
I hope these instructions have been helpful. If you have any suggestions for changes or improvements please E-mail me at '''alan (at) rmrsoft (dot) com'''

How to Create Custom Remote Controls and use them on your Slingbox

2015-12-22T19:34:03Z

Alanrichey: /* Software */

Written by: Al Richey 

With acknowledgements to Matt Whitlock, BrandonC, The Robman, Nuke12 and AndyBBB, who actually wrote much of this article. All I did was update and combine all the information into one document. 

=='''Background information'''==
One of the most common posts on the support site is about remote codes for unsupported devices. So if you find yourself in this situation I hope this will help. Before detailing the steps to go through there are some basic things you need to understand (this isn‟t essential reading but everything will make much more sense if you do know the details)
==='''Different UEI Chips'''===
: There were five different chips used in Slingboxes. These are designated as JU, PK, PL, RV & JB. If you want to check your type you can verify your IR blaster version in the Slingbox Properties dialog. Then match the IR version number with the chip type using the chart below.
#JU (VERY old US boxes)
#PL (current US boxes)
#PK (never used)
#RV (old European boxes)
#JB (All modern Slingboxes, but compatible with PL files)

So unless you have an old European Solo all you need is the PL file.

==='''Slingplayer Compatibility'''===
: In older versions of Slingplayer it was possible to change the look of the Custom Remote skin‟. Since Slingplayer V1.5 this functionality has been removed and as far as the look of the Remote is concerned you are stuck with the Generic design produced by Sling Media. All we can do is change the codes that are sent when a specific button is pressed. One drawback of the Generic Remote is that it has only the main buttons, so extra buttons on other remotes (such as Audio/Setup…) can not be mapped directly. What we have to do is put them into a Custom Menu which is accessed by tapping on the Menu button on the Generic Remote or right-clicking on the image. (Note: If a remote image has already been produced by Sling it is possible to use that image instead of the generic image)
:

==='''Setup Code Nomenclature'''===
: When you run the Configure Inputs routines in the various Slingplayers and select a supported device, what actually happens is that a Binary Code is downloaded to the Slingbox. 
: This Binary Code details the IR codes that are sent when a specific button is pressed on the remote. Unfortunately the native Slingbox software doesn't use separate binary files that we can edit, their codes are apparently compressed and packaged into special files that we can't do anything with (that I know of). But what we can do instead of editing the built-in codes is to use a separate external upgrade code file. These files have the format such as "C1234_PL.BIN". 
: The first letter of the file describes the type of device, the main ones we are interested in are:
::V which is for VCRs, which encompasses PVRs, DVRs and other recorders
::S which is for Satellite and FTA set top boxes
::C which is for Cable boxes
::Y which is for DVD Players
::R which is for Tuners
:This is followed by a 4-digit code number. For Slingboxes the code numbers can be between 0000-2047 (actually higher in newer Slingboxes but to stay safe we are better staying below 2047). In general, codes below 2000 actually relate to specific boxes, for example V0618 is the code for a TIVO and D0032 is the code for a Pioneer CD Player. But we can feel fairly safe using 2000-2047 for our own codes. The final part of the filename defines the chip for which it will run. 
: So if you were looking for the binary file for a PVR with a code number allocated 1234, designed to run on a PL-equipped Slingbox, you would be searching for a file called V1234_PL.BIN. Note: You must NEVER change the name of the file, as the letter, code number and chip type are also defined inside the file itself.

==='''JP1'''===
:You will hear a lot about "JP1". Basically this is a process whereby people using "One For All‟ (OFA) remote controls can add new codes to their remotes from their PC. The remote control processor inside the Slingbox is made by the same company that makes OFA remotes, so the upgrades are similar. The JP1 tools have been upgraded so that we can now use them to create and modify upgrades for the Slingbox.

=='''The Basic Procedure.'''==
The official procedure to follow is to report the [http://support.slingmedia.com/get/KB-005640.html Lack of a Supported Remote] to SlingMedia and they will add it to the database. In practice, they are not quick at doing this (I have been asking for a remote for over 2 years now), and the updated remote list seems to be only occasionally updated. That may change in the future but for now it is really not a practical quick solution. So for a short term fix what you need to do is to create or acquire the correct Binary code file for your A/V device, and then install it into your Slingbox. This installation process is covered in detail in [[#Installing_the_Binary_file_to_the_Slingbox|Section 4]], so first let‟s see where you can look for these files. 

=='''Obtaining the Binary file for the Custom Remote'''==

#Before starting, make sure in the setup wizard you have tried all the devices by that same manufacturer, even if the model number does not match, and all the associated code numbers. You might be lucky and find one that works and that will save a lot of work. If that doesn‟t solve the problem here is the step by step approach to getting hold of your binary file: 
#Go to the JP1 forum. This has a specific Download area for [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=87 Slingbox Custom Remotes], so go through all those to see if your device has already been done. 
#If it isn‟t there the JP1 forum also has a more general [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=4 File Download Area]. From this page you select the download area for the specific type of device and check there. If you are lucky you will find a source file for using in the program RemoteMaster (RM or KM files), the use of which is discussed in [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]]. 
#Have a look on the Hava forums. They are also using the same chips and the files might be there. Check out this [http://www.myhava.com/forum/viewforum.php?f=17&st=0&sk=t&sd=d&start=0 forum]. You‟re looking for a PK or PL file. They can be imported into Remote Master and then converted to the PK, PL, RV or JU files for the Slingbox. Again this is discussed in [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]]. 
#Find a friend with a Pronto remote. They have a very nice update system and can generate .ccf files that can be used with the tools on the JP1 site to generate the .bin file used by a Slingbox. However, this is not easy, and you will probably need help from the experts on the JP1 forum, but if you want to have a go on your own then you will need the [http://www.hifi-remote.com/forums/dload.php?action=file&file_id=1887 DecodeCCF] program, and [http://www.remotecentral.com/files/index.html .ccf] files. Note that the Pronto can also make .pcf files, but unfortunately we cannot decode those. 
If all of this fails, and you cannot get hold of a BIN file then the Remote will have to be built from scratch. You have 2 options here: 
#Do it yourself by buying a JP1.x learning remote (plus a JP1.x cable), or an IR Widget, and learn the codes needed to control the device. How to do this is covered in [[#Learning_the_IR_codes_from_your_own_remote|Section 5]] & [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]]. 
#Ask someone else to do the work for you. You can try this by posting a request for help in either:
##The [https://community.sling.com/content Slingbox Answers Forum].
##The [http://www.hifi-remote.com/forums/viewforum.php?f=19 JP1 forum]. 
I can normally install your device on my Harmony Universal Remote to mimic the original Remote and learn the codes for you (unless I am away on holiday). 

=='''Installing the Binary file to the Slingbox.'''==
 I have written a comprehensive Installation Guide at

http://placeshiftingenthusiasts.com/how-to-install-a-custom-remote-onto-the-slingbox/

Once you have completed the setup and the BIN files have been downloaded to the Slingbox they are not used any more and can be deleted.

=='''Learning the IR codes from your own remote.'''==
==='''Requirements'''===
Assuming you have decided to create the Remote Binary File yourself, the first stage is to learn the codes from your original Remote. This is what you need:
====Hardware====
#A computer with a USB port (or you can use older serial ports). 
#A Learning Remote and an appropriate JP Cable. Almost any "One For All" or "Radio Shack" remote that has learning will work for this but examples are: 
::URC-6820 (JP1.2)
::URC-8820 (JP1.2)
::URC-10820 (JP1.2)
::Radio Shack Gamer 15-133 (JP1.3)
::Radios Shack Satelite15-134 (JP1.3) 

:Note that some remotes need a JP1.2 cable and some need a JP1.3 cable (and some older, discontinued remotes such as the URC-9810 use a JP1 cable). Make sure the Cable and Remote match. Again the [http://www.hifi-remote.com/forums/viewforum.php?f=10 JP1 forum] is a mine of information. 
:If you are not sure there is a [http://www.hifi-remote.com/forums/dload.php?action=file&file_id=2981 chart of remotes] where you can look up a specific remote to see which format it uses. If you want to buy a cable try [http://www.diygadget.com/ DIYgadget] for the cheaper serial JP1.2/3 cables.

:Although an easy solution is to get a Nevo C2, which has it's own built-in cable. These are available on E-Bay.

:or alternatively

:An IR learning "widget". I got mine from Tommy Tyler through https://www.tindie.com/products/TommyTyler/ir-widget-infrared-remote-control-signal-recorderanalyzer/ (My preferred solution). 

====Software====
:If you are using a Learning Remote: [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=81 RM/RMIR.EXE] [http://www.hifi-remote.com/forums/dload.php?action=file&file_id=7201 RDF Files] These are support files for the program. If you are using an IR Widget: [http://www.compendiumarcana.com/irwidget/irscope.zip IRSCOPE.EXE] [http://www.ftdichip.com/Drivers/VCP.htm The drivers] [http://www.hifi-remote.com/forums/dload.php?action=file&file_id=922 The IR decode DLL] Or download [http://rmrsoft.com/remote.zip my full IRSCOPE/REMOTEMASTER package]. Much of the JP1 software needs the java runtime environment (JRE) as well. A lot of computers will already have it installed already, but if you need it you can [http://java.sun/j2se/1.4.2/download.html download] Now we can learn the codes. First we will cover the procedure using a Learning Remote, then cover it using an IR Widget. 

===USING A LEARNING REMOTE===
====Getting the Codes from your Remote====
(These steps are based on using the older URC9810, the procedure will be slightly different for other Remotes so you will need to refer to the manuals.) 
:# Tap one of the buttons on the Learning Remote at the top which applies to the device you wish to create the bin file for. (eg. TV, DVD, Satellite). This is not totally necessary, you can always use TV, as it makes no difference to you, but if you subsequently upload the file for other users, it really ought to be for the correct type of device. 
:# At the bottom there will be a button called 'Set'. Keep your finger pushed on that until the LCD changes so you can modify your remote control. 
:# Click down until you come to an option called 'IR LEARN' and click select. 
:# Click one of the buttons on the remote control. For example, the '1' key, the LCD will say "Learning" and the red light will come on. 
:# Put your remote control in front of the learning remote and click the 1 key - if it is added correctly it should say 'Success'. If it fails (shows “Error”) then try again. There are a lot of different techniques for this procedure, the safest bet seems to be press the button on the Learning Remote, wait for 2 seconds then hold the equivalent key on the original Remote until the red light goes on. If you get a bad „learn‟, try just tapping quickly on the original key. A full description of these options is [http://www.hifi-remote.com/forums/viewtopic.php?t=3943 here]. 
:# Repeat this step for each of the keys you want to learn and have on your Slingbox Remote. If you get the "Memory Full" message then you will have to repeat this operation for the remaining keys after you have uploaded the first set of codes to your PC. 

====Getting the Codes onto your PC.====
 
:#Install IR.EXE onto your PC. It comes as a ZIP file rather than an installation package, which you need to unzip to your PC. The files can actually go anywhere but as a bit of tidy person (geek?) I created a C:\Program Files\IR\ folder and put the files in there and then created a shortcut on the Desktop. Important Note: For Windows VISTA users, I have found that I need to run the program in Windows XP Compatibility Mode to make it recognise the JP1 interface. Just right-click on IR.EXE, select Properties, then the Compatibility Tab and check the appropriate box. 
:#Create a sub folder called \RDF\ in whatever folder you have put the IR program and extract the RDF support files into that folder. 
:#Get your JP1 cable out and turn your remote control over, open the battery compartment and plug the JP1 6 pin connector into the Learning remote (you will see 6 needles where it plugs into). There are 2 ways to plug it in, but don‟t worry, you won‟t cause any damage by plugging it in the wrong way. Try them both if the first one fails. 
:#Plug the USB plug into your computer. As with any external piece of hardware you will need to install the drivers. There are drivers for the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=81 JP1 Remotes] and the [http://www.ftdichip.com/Drivers/VCP.htm JP1.2/3 Remotes]. Personally I use the JP1 ones dated 12 Feb 2008 and they work fine in Windows XP and also in Vista as long as the Windows XP Compatibility flag is set. 
:#Now open IR.exe. If you get told your RDF directory isn't valid, click OK and ignore this for now. It will look something like this: (Note this is a screenshot of V8.0. If that version hasn‟t been released yet, V7.15 looks very similar but does not have the icons at the top. [[Image:IR-general.jpg]] 
:#Go to File > Set Directory > RDF Path >. Select your RDF directory. You need to double click the RDF directory or it won't take. 
:#For peace of mind go to Interface > Check Driver... it should say the interface is connected. If it does then that's fine, if it gives an error message “Unable to open device, check connection” then it is not seeing the JP1 cable so you need to check the cable and the drivers. If it gives the error message “The remote is not acknowledging signals from the interface” then the cable is working fine but it is not seeing the remote. Try reversing the cable connection to the remote and hopefully that will cure the problem. 
:#Now click the "Download From Remote" button. 
:#Then click the "Learned Signals" tab (second from last one). It will look something like this: [[Image:IR-learned1.jpg]] 
:#On the left hand side there should be a list with the device type and the keys - eg "TV: 1". Click on it and details should show up in the right hand side listview. 
:#The first thing we need to make a note of is the Protocol (JVC) in this case, then the Device Number (239 in this case) and if it is displayed, the Sub-Device number. Then for each of the learned keys note down the OBC, Hex Code and EFC numbers. 
:#If you get the "MEM FULL" message on the Remote then Use File > Save As to keep a copy then tap the "Delete All" button, go back to the General Tab and tap the "Upload To remote" button to clear the Remote. Then learn the remaining buttons and follow the same procedure. Once they are all done, use the use the File > Save As command to save a copy of the final results. 
However, if you see a screen like this, it means that the protocol used by your remote is not recognised by the system. That means that you cannot create the Remote yourself but will have to ask the people on the JP1 forum to help you out. They have a much deeper understanding of the IR formats, and can often dig deeper into the signals and figure out the codes. [[Image:IR-learned2.jpg]] 
The procedure to do this is to use the File > Save As menu option to save the IR source file(s) (I tend to ZIP them up if there are more than one). Now upload them to the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=35 Diagnosis Area] in the File Section of the JP1 Forum. 
Check the file has been added, and make a record of it‟s location by right-clicking on it and select „Copy Link Location‟. 
Now create a new topic in the [http://www.hifi-remote.com/forums/viewforum.php?f=20 Protocol Decode Forum] and plead for some help, quoting the device Manufacturer and Model Number and the link to the IR source files. Offer incentives (money, beer, everlasting gratitude….) and you might be lucky. The experts may produce the RemoteMaster source file or even the Remote Binary files themselves. Now you can move on to [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]] for building the Remote BIN files. 

===USING AN IR WIDGET===
If you are using an IR Widget there is an excellent guide [http://freepdfhosting.com/2da0b92e8c.pdf here] on the Tindle site. So I suggest you download that and read it thoroughly. There is no point in repeating it here, but just to emphasise a few points: 
:#You will want to regularly check for updates to the decodeir.dll. As new protocols are recognized, this dll will change. 
:#There is no way to save the learned values for importing into RemoteMaster (where you will make the remote) so you will need to write them down. 
:#Although I tend to put programs into C:\Program Files\.... this can be a bit dodgy in Windows as programs cannot save files to this area because of security limitations. So it might be safer to install it under \Documents\ 
:#The Guide has a very useful section comparing using a Learning Remotes and the IR Widget and highlighting the differences, (For example "Key" is equivalent to "OBC") so you could check out the previous sub-section covering using IR.EXE and the Learning Remote. And then you will understand this section. When complete you can move onto [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]] to create the Binary file. 

=='''Creating your own Binary files using RemoteMaster'''==
:#To make life easier I have packaged a full set of the latest files required and uploaded them to my site. Just download them from [http://www.rmrsoft.com/remote.zip here] and unzip them onto your computer. 
:#Start RemoteMaster.EXE. You may be promoted to highlight the folder the folder that contains the RDF files (Highlight the \RDF\ folder in the folder where you placed Remotemaster). You may also have to do the same for the Images folder. The display will now look something like this:[[Image:RM-setup.jpg]] 
:#If you have obtained an .rmdu file then use the File > Open menu option to load the file. If you have obtained a .bin file then use the Advanced > Import Binary Upgrade to load up the details. If you have not obtained a file then you will have to input the codes manually. 
:#Now to explain the main Setup Tab: '''Description ''': Use anything you like, I tend to use the device name. '''Remote''': Select the one appropriate for your chip. '''Device Type''': Should be set to the correct type of device (as covered in Paragraph 3 of Section 1). '''Setup Code''': This is where you put the 4-digit code. In theory it can be any number between 0000 and 2047, but as explained in Section 1 Paragraph 3, numbers below 2000 may actually be already allocated to specific devices, so to be safe I personally use 2010. Fell free to use your own value. '''Protocol''': From the dropdown list select the Protocol you discovered when you used IR.EXE/IRSCOPE.EXE. '''Device''': Type in the Device code you recorded from IR.EXE/IRSCOPE.EXE. '''Sub-Device''': If applicable type in the Sub-Device code you recorded from IR.EXE/ IRSCOPE.EXE. 
:#Now tap on the Functions Tab [[Image:RM-functions.jpg]] This picture shows the program with an .rmdu file or .bin file already imported; otherwise the code columns will be blank. The entries are fully configurable, so if there are pre-defined functions that you do not need (pip swap, pipmove..) then you highlight them and tap the "Delete" button. If you have a function that is not pre-defined (Audio, Setup…) then tap the "New" button and enter them. Now fill in the codes for each button that you recorded. You just put in the OBC value and press <Enter>, the other 2 values will be generated automatically based on the protocol you selected. Also, if you used a JP1 learning remote, there's a way to cut and paste all the codes which saves needing to enter them all. In IR, if you select File > Summary you get a page listing lots of stuff. If you scroll down, you'll see a list of learn decodes. You can cut and paste this list into Excel, then you can re-arrange the columns and just select the button names and OBC codes to cut and paste into RM. You can move the RM columns, so if the OBC column isn't the one next to the button names, you can move it there. 
:#Now tap on the Buttons Tab [[Image:RM-buttons.jpg]] This is where you map the defined functions onto the available buttons. Simply tap the Auto-Assign button which should allocate most of the buttons. For any buttons left in red drag the function name from the table on the left to the function column on the right. But note that not all these buttons are available on a Slingplayer Generic Remote. For example the 'Slow' and 'Eject' buttons do not exist on a Generic Remote. So only map the functions onto the buttons that actually exist (You will see that when you check out the Layout Tab, and from experience when you have done this a few times). The important ones to note are the Custom 10-29 buttons. These are the ones you use for the functions you need that aren't on the generic remote and they subsequently appear in the drop down menu of the remote as Custom options (except for Custom 22-26 which are pre-allocated to the colour buttons). 
:#Now tap on the Layout Tab. [[Image:RM-layout.jpg]] This shows the generic Slingplayer remote and shows the buttons you can actually use in the Buttons Tab. If a button shows yellow then that means it is in use. If it shows black (the PgUp/PgDn in the picture) then has not been allocated a function. Again you can drag and drop functions onto a button. 
:#Once you have finished experimenting go back to the Setup tab. Select the appropriate Slingbox remote, go to the 'Advanced' menu at the top and select 'Export Binary Upgrade'. This will produce the BIN file that we have discussed in previous Sections. If you aren‟t sure which Slingbox Chip you have then create a BIN file for the main 2 chips, so that would give you something like 
:::C2010_PL.BIN
:::C2010_RV.BIN

So now you can go back to [[#Installing_the_Binary_file_to_the_Slingbox.|Section 4]] and install the new Custom Remote onto your Slingbox. 
====Finding Missing Codes====
You can often find yourself in the position where the Custom Remote generally works OK but some of the functions are missing or some are sending the wrong code. This is relatively easy to fix by trial and error. The OBC codes must lie between 0-255, so the first thing to do is make a list of the OBC codes that are not being used in the Remote Control. Now use Remotemaster to allocate those codes to the 0-9 buttons and the 15 Custom buttons. Now build a new BIN files, replace the one in your \SBAV\ folder and rerun the "Setup Video Sources" routine. Now try those buttons and see if any of them action the missing function. If you find the missing codes then you can update the original remote file. You may have to repeat this operation 10 times to cover all the missing codes, although you can cut down the number of times by also using the Transport buttons (Play/Pause…) and Channel, Page +/- buttons as well. 

=='''Give your Binary file back to the Community'''==
Finally, remember that it is good to payback. If you find a remote file that works for you then upload it to the JP1 Forums. The way to do this is: 
#Put the 4 Binary files and the Remote Master RMDU file into a ZIP file. I also tend to add a Readme file in case users are unsure how to use the files. Although hopefully they will have read this article and will know what to do. 
#To be really helpful, you should upload your files in 3 different places:
##Upload your ZIP file to the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=87 Slingbox Binary Files] area.
##Upload the Remote Master RMDU source file to the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=98 Slingbox RM Files] area.
##Upload the RMDU file to the appropriate area in the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=4 Device Upgrades] area.
 
I hope these instructions have been helpful. If you have any suggestions for changes or improvements please E-mail me at '''alan (at) rmrsoft (dot) com'''

How to Create Custom Remote Controls and use them on your Slingbox

2015-12-22T19:33:30Z

Alanrichey: /* Software */

Written by: Al Richey 

With acknowledgements to Matt Whitlock, BrandonC, The Robman, Nuke12 and AndyBBB, who actually wrote much of this article. All I did was update and combine all the information into one document. 

=='''Background information'''==
One of the most common posts on the support site is about remote codes for unsupported devices. So if you find yourself in this situation I hope this will help. Before detailing the steps to go through there are some basic things you need to understand (this isn‟t essential reading but everything will make much more sense if you do know the details)
==='''Different UEI Chips'''===
: There were five different chips used in Slingboxes. These are designated as JU, PK, PL, RV & JB. If you want to check your type you can verify your IR blaster version in the Slingbox Properties dialog. Then match the IR version number with the chip type using the chart below.
#JU (VERY old US boxes)
#PL (current US boxes)
#PK (never used)
#RV (old European boxes)
#JB (All modern Slingboxes, but compatible with PL files)

So unless you have an old European Solo all you need is the PL file.

==='''Slingplayer Compatibility'''===
: In older versions of Slingplayer it was possible to change the look of the Custom Remote skin‟. Since Slingplayer V1.5 this functionality has been removed and as far as the look of the Remote is concerned you are stuck with the Generic design produced by Sling Media. All we can do is change the codes that are sent when a specific button is pressed. One drawback of the Generic Remote is that it has only the main buttons, so extra buttons on other remotes (such as Audio/Setup…) can not be mapped directly. What we have to do is put them into a Custom Menu which is accessed by tapping on the Menu button on the Generic Remote or right-clicking on the image. (Note: If a remote image has already been produced by Sling it is possible to use that image instead of the generic image)
:

==='''Setup Code Nomenclature'''===
: When you run the Configure Inputs routines in the various Slingplayers and select a supported device, what actually happens is that a Binary Code is downloaded to the Slingbox. 
: This Binary Code details the IR codes that are sent when a specific button is pressed on the remote. Unfortunately the native Slingbox software doesn't use separate binary files that we can edit, their codes are apparently compressed and packaged into special files that we can't do anything with (that I know of). But what we can do instead of editing the built-in codes is to use a separate external upgrade code file. These files have the format such as "C1234_PL.BIN". 
: The first letter of the file describes the type of device, the main ones we are interested in are:
::V which is for VCRs, which encompasses PVRs, DVRs and other recorders
::S which is for Satellite and FTA set top boxes
::C which is for Cable boxes
::Y which is for DVD Players
::R which is for Tuners
:This is followed by a 4-digit code number. For Slingboxes the code numbers can be between 0000-2047 (actually higher in newer Slingboxes but to stay safe we are better staying below 2047). In general, codes below 2000 actually relate to specific boxes, for example V0618 is the code for a TIVO and D0032 is the code for a Pioneer CD Player. But we can feel fairly safe using 2000-2047 for our own codes. The final part of the filename defines the chip for which it will run. 
: So if you were looking for the binary file for a PVR with a code number allocated 1234, designed to run on a PL-equipped Slingbox, you would be searching for a file called V1234_PL.BIN. Note: You must NEVER change the name of the file, as the letter, code number and chip type are also defined inside the file itself.

==='''JP1'''===
:You will hear a lot about "JP1". Basically this is a process whereby people using "One For All‟ (OFA) remote controls can add new codes to their remotes from their PC. The remote control processor inside the Slingbox is made by the same company that makes OFA remotes, so the upgrades are similar. The JP1 tools have been upgraded so that we can now use them to create and modify upgrades for the Slingbox.

=='''The Basic Procedure.'''==
The official procedure to follow is to report the [http://support.slingmedia.com/get/KB-005640.html Lack of a Supported Remote] to SlingMedia and they will add it to the database. In practice, they are not quick at doing this (I have been asking for a remote for over 2 years now), and the updated remote list seems to be only occasionally updated. That may change in the future but for now it is really not a practical quick solution. So for a short term fix what you need to do is to create or acquire the correct Binary code file for your A/V device, and then install it into your Slingbox. This installation process is covered in detail in [[#Installing_the_Binary_file_to_the_Slingbox|Section 4]], so first let‟s see where you can look for these files. 

=='''Obtaining the Binary file for the Custom Remote'''==

#Before starting, make sure in the setup wizard you have tried all the devices by that same manufacturer, even if the model number does not match, and all the associated code numbers. You might be lucky and find one that works and that will save a lot of work. If that doesn‟t solve the problem here is the step by step approach to getting hold of your binary file: 
#Go to the JP1 forum. This has a specific Download area for [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=87 Slingbox Custom Remotes], so go through all those to see if your device has already been done. 
#If it isn‟t there the JP1 forum also has a more general [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=4 File Download Area]. From this page you select the download area for the specific type of device and check there. If you are lucky you will find a source file for using in the program RemoteMaster (RM or KM files), the use of which is discussed in [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]]. 
#Have a look on the Hava forums. They are also using the same chips and the files might be there. Check out this [http://www.myhava.com/forum/viewforum.php?f=17&st=0&sk=t&sd=d&start=0 forum]. You‟re looking for a PK or PL file. They can be imported into Remote Master and then converted to the PK, PL, RV or JU files for the Slingbox. Again this is discussed in [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]]. 
#Find a friend with a Pronto remote. They have a very nice update system and can generate .ccf files that can be used with the tools on the JP1 site to generate the .bin file used by a Slingbox. However, this is not easy, and you will probably need help from the experts on the JP1 forum, but if you want to have a go on your own then you will need the [http://www.hifi-remote.com/forums/dload.php?action=file&file_id=1887 DecodeCCF] program, and [http://www.remotecentral.com/files/index.html .ccf] files. Note that the Pronto can also make .pcf files, but unfortunately we cannot decode those. 
If all of this fails, and you cannot get hold of a BIN file then the Remote will have to be built from scratch. You have 2 options here: 
#Do it yourself by buying a JP1.x learning remote (plus a JP1.x cable), or an IR Widget, and learn the codes needed to control the device. How to do this is covered in [[#Learning_the_IR_codes_from_your_own_remote|Section 5]] & [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]]. 
#Ask someone else to do the work for you. You can try this by posting a request for help in either:
##The [https://community.sling.com/content Slingbox Answers Forum].
##The [http://www.hifi-remote.com/forums/viewforum.php?f=19 JP1 forum]. 
I can normally install your device on my Harmony Universal Remote to mimic the original Remote and learn the codes for you (unless I am away on holiday). 

=='''Installing the Binary file to the Slingbox.'''==
 I have written a comprehensive Installation Guide at

http://placeshiftingenthusiasts.com/how-to-install-a-custom-remote-onto-the-slingbox/

Once you have completed the setup and the BIN files have been downloaded to the Slingbox they are not used any more and can be deleted.

=='''Learning the IR codes from your own remote.'''==
==='''Requirements'''===
Assuming you have decided to create the Remote Binary File yourself, the first stage is to learn the codes from your original Remote. This is what you need:
====Hardware====
#A computer with a USB port (or you can use older serial ports). 
#A Learning Remote and an appropriate JP Cable. Almost any "One For All" or "Radio Shack" remote that has learning will work for this but examples are: 
::URC-6820 (JP1.2)
::URC-8820 (JP1.2)
::URC-10820 (JP1.2)
::Radio Shack Gamer 15-133 (JP1.3)
::Radios Shack Satelite15-134 (JP1.3) 

:Note that some remotes need a JP1.2 cable and some need a JP1.3 cable (and some older, discontinued remotes such as the URC-9810 use a JP1 cable). Make sure the Cable and Remote match. Again the [http://www.hifi-remote.com/forums/viewforum.php?f=10 JP1 forum] is a mine of information. 
:If you are not sure there is a [http://www.hifi-remote.com/forums/dload.php?action=file&file_id=2981 chart of remotes] where you can look up a specific remote to see which format it uses. If you want to buy a cable try [http://www.diygadget.com/ DIYgadget] for the cheaper serial JP1.2/3 cables.

:Although an easy solution is to get a Nevo C2, which has it's own built-in cable. These are available on E-Bay.

:or alternatively

:An IR learning "widget". I got mine from Tommy Tyler through https://www.tindie.com/products/TommyTyler/ir-widget-infrared-remote-control-signal-recorderanalyzer/ (My preferred solution). 

====Software====
:If you are using a Learning Remote: [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=81 RM/RMIR.EXE] [http://www.hifi-remote.com/forums/dload.php?action=file&file_id=7201 RDF Files] These are support files for the IR.EXE program. If you are using an IR Widget: [http://www.compendiumarcana.com/irwidget/irscope.zip IRSCOPE.EXE] [http://www.ftdichip.com/Drivers/VCP.htm The drivers] [http://www.hifi-remote.com/forums/dload.php?action=file&file_id=922 The IR decode DLL] Or download [http://rmrsoft.com/remote.zip my full IRSCOPE/REMOTEMASTER package]. Much of the JP1 software needs the java runtime environment (JRE) as well. A lot of computers will already have it installed already, but if you need it you can [http://java.sun/j2se/1.4.2/download.html download] Now we can learn the codes. First we will cover the procedure using a Learning Remote, then cover it using an IR Widget. 

===USING A LEARNING REMOTE===
====Getting the Codes from your Remote====
(These steps are based on using the older URC9810, the procedure will be slightly different for other Remotes so you will need to refer to the manuals.) 
:# Tap one of the buttons on the Learning Remote at the top which applies to the device you wish to create the bin file for. (eg. TV, DVD, Satellite). This is not totally necessary, you can always use TV, as it makes no difference to you, but if you subsequently upload the file for other users, it really ought to be for the correct type of device. 
:# At the bottom there will be a button called 'Set'. Keep your finger pushed on that until the LCD changes so you can modify your remote control. 
:# Click down until you come to an option called 'IR LEARN' and click select. 
:# Click one of the buttons on the remote control. For example, the '1' key, the LCD will say "Learning" and the red light will come on. 
:# Put your remote control in front of the learning remote and click the 1 key - if it is added correctly it should say 'Success'. If it fails (shows “Error”) then try again. There are a lot of different techniques for this procedure, the safest bet seems to be press the button on the Learning Remote, wait for 2 seconds then hold the equivalent key on the original Remote until the red light goes on. If you get a bad „learn‟, try just tapping quickly on the original key. A full description of these options is [http://www.hifi-remote.com/forums/viewtopic.php?t=3943 here]. 
:# Repeat this step for each of the keys you want to learn and have on your Slingbox Remote. If you get the "Memory Full" message then you will have to repeat this operation for the remaining keys after you have uploaded the first set of codes to your PC. 

====Getting the Codes onto your PC.====
 
:#Install IR.EXE onto your PC. It comes as a ZIP file rather than an installation package, which you need to unzip to your PC. The files can actually go anywhere but as a bit of tidy person (geek?) I created a C:\Program Files\IR\ folder and put the files in there and then created a shortcut on the Desktop. Important Note: For Windows VISTA users, I have found that I need to run the program in Windows XP Compatibility Mode to make it recognise the JP1 interface. Just right-click on IR.EXE, select Properties, then the Compatibility Tab and check the appropriate box. 
:#Create a sub folder called \RDF\ in whatever folder you have put the IR program and extract the RDF support files into that folder. 
:#Get your JP1 cable out and turn your remote control over, open the battery compartment and plug the JP1 6 pin connector into the Learning remote (you will see 6 needles where it plugs into). There are 2 ways to plug it in, but don‟t worry, you won‟t cause any damage by plugging it in the wrong way. Try them both if the first one fails. 
:#Plug the USB plug into your computer. As with any external piece of hardware you will need to install the drivers. There are drivers for the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=81 JP1 Remotes] and the [http://www.ftdichip.com/Drivers/VCP.htm JP1.2/3 Remotes]. Personally I use the JP1 ones dated 12 Feb 2008 and they work fine in Windows XP and also in Vista as long as the Windows XP Compatibility flag is set. 
:#Now open IR.exe. If you get told your RDF directory isn't valid, click OK and ignore this for now. It will look something like this: (Note this is a screenshot of V8.0. If that version hasn‟t been released yet, V7.15 looks very similar but does not have the icons at the top. [[Image:IR-general.jpg]] 
:#Go to File > Set Directory > RDF Path >. Select your RDF directory. You need to double click the RDF directory or it won't take. 
:#For peace of mind go to Interface > Check Driver... it should say the interface is connected. If it does then that's fine, if it gives an error message “Unable to open device, check connection” then it is not seeing the JP1 cable so you need to check the cable and the drivers. If it gives the error message “The remote is not acknowledging signals from the interface” then the cable is working fine but it is not seeing the remote. Try reversing the cable connection to the remote and hopefully that will cure the problem. 
:#Now click the "Download From Remote" button. 
:#Then click the "Learned Signals" tab (second from last one). It will look something like this: [[Image:IR-learned1.jpg]] 
:#On the left hand side there should be a list with the device type and the keys - eg "TV: 1". Click on it and details should show up in the right hand side listview. 
:#The first thing we need to make a note of is the Protocol (JVC) in this case, then the Device Number (239 in this case) and if it is displayed, the Sub-Device number. Then for each of the learned keys note down the OBC, Hex Code and EFC numbers. 
:#If you get the "MEM FULL" message on the Remote then Use File > Save As to keep a copy then tap the "Delete All" button, go back to the General Tab and tap the "Upload To remote" button to clear the Remote. Then learn the remaining buttons and follow the same procedure. Once they are all done, use the use the File > Save As command to save a copy of the final results. 
However, if you see a screen like this, it means that the protocol used by your remote is not recognised by the system. That means that you cannot create the Remote yourself but will have to ask the people on the JP1 forum to help you out. They have a much deeper understanding of the IR formats, and can often dig deeper into the signals and figure out the codes. [[Image:IR-learned2.jpg]] 
The procedure to do this is to use the File > Save As menu option to save the IR source file(s) (I tend to ZIP them up if there are more than one). Now upload them to the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=35 Diagnosis Area] in the File Section of the JP1 Forum. 
Check the file has been added, and make a record of it‟s location by right-clicking on it and select „Copy Link Location‟. 
Now create a new topic in the [http://www.hifi-remote.com/forums/viewforum.php?f=20 Protocol Decode Forum] and plead for some help, quoting the device Manufacturer and Model Number and the link to the IR source files. Offer incentives (money, beer, everlasting gratitude….) and you might be lucky. The experts may produce the RemoteMaster source file or even the Remote Binary files themselves. Now you can move on to [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]] for building the Remote BIN files. 

===USING AN IR WIDGET===
If you are using an IR Widget there is an excellent guide [http://freepdfhosting.com/2da0b92e8c.pdf here] on the Tindle site. So I suggest you download that and read it thoroughly. There is no point in repeating it here, but just to emphasise a few points: 
:#You will want to regularly check for updates to the decodeir.dll. As new protocols are recognized, this dll will change. 
:#There is no way to save the learned values for importing into RemoteMaster (where you will make the remote) so you will need to write them down. 
:#Although I tend to put programs into C:\Program Files\.... this can be a bit dodgy in Windows as programs cannot save files to this area because of security limitations. So it might be safer to install it under \Documents\ 
:#The Guide has a very useful section comparing using a Learning Remotes and the IR Widget and highlighting the differences, (For example "Key" is equivalent to "OBC") so you could check out the previous sub-section covering using IR.EXE and the Learning Remote. And then you will understand this section. When complete you can move onto [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]] to create the Binary file. 

=='''Creating your own Binary files using RemoteMaster'''==
:#To make life easier I have packaged a full set of the latest files required and uploaded them to my site. Just download them from [http://www.rmrsoft.com/remote.zip here] and unzip them onto your computer. 
:#Start RemoteMaster.EXE. You may be promoted to highlight the folder the folder that contains the RDF files (Highlight the \RDF\ folder in the folder where you placed Remotemaster). You may also have to do the same for the Images folder. The display will now look something like this:[[Image:RM-setup.jpg]] 
:#If you have obtained an .rmdu file then use the File > Open menu option to load the file. If you have obtained a .bin file then use the Advanced > Import Binary Upgrade to load up the details. If you have not obtained a file then you will have to input the codes manually. 
:#Now to explain the main Setup Tab: '''Description ''': Use anything you like, I tend to use the device name. '''Remote''': Select the one appropriate for your chip. '''Device Type''': Should be set to the correct type of device (as covered in Paragraph 3 of Section 1). '''Setup Code''': This is where you put the 4-digit code. In theory it can be any number between 0000 and 2047, but as explained in Section 1 Paragraph 3, numbers below 2000 may actually be already allocated to specific devices, so to be safe I personally use 2010. Fell free to use your own value. '''Protocol''': From the dropdown list select the Protocol you discovered when you used IR.EXE/IRSCOPE.EXE. '''Device''': Type in the Device code you recorded from IR.EXE/IRSCOPE.EXE. '''Sub-Device''': If applicable type in the Sub-Device code you recorded from IR.EXE/ IRSCOPE.EXE. 
:#Now tap on the Functions Tab [[Image:RM-functions.jpg]] This picture shows the program with an .rmdu file or .bin file already imported; otherwise the code columns will be blank. The entries are fully configurable, so if there are pre-defined functions that you do not need (pip swap, pipmove..) then you highlight them and tap the "Delete" button. If you have a function that is not pre-defined (Audio, Setup…) then tap the "New" button and enter them. Now fill in the codes for each button that you recorded. You just put in the OBC value and press <Enter>, the other 2 values will be generated automatically based on the protocol you selected. Also, if you used a JP1 learning remote, there's a way to cut and paste all the codes which saves needing to enter them all. In IR, if you select File > Summary you get a page listing lots of stuff. If you scroll down, you'll see a list of learn decodes. You can cut and paste this list into Excel, then you can re-arrange the columns and just select the button names and OBC codes to cut and paste into RM. You can move the RM columns, so if the OBC column isn't the one next to the button names, you can move it there. 
:#Now tap on the Buttons Tab [[Image:RM-buttons.jpg]] This is where you map the defined functions onto the available buttons. Simply tap the Auto-Assign button which should allocate most of the buttons. For any buttons left in red drag the function name from the table on the left to the function column on the right. But note that not all these buttons are available on a Slingplayer Generic Remote. For example the 'Slow' and 'Eject' buttons do not exist on a Generic Remote. So only map the functions onto the buttons that actually exist (You will see that when you check out the Layout Tab, and from experience when you have done this a few times). The important ones to note are the Custom 10-29 buttons. These are the ones you use for the functions you need that aren't on the generic remote and they subsequently appear in the drop down menu of the remote as Custom options (except for Custom 22-26 which are pre-allocated to the colour buttons). 
:#Now tap on the Layout Tab. [[Image:RM-layout.jpg]] This shows the generic Slingplayer remote and shows the buttons you can actually use in the Buttons Tab. If a button shows yellow then that means it is in use. If it shows black (the PgUp/PgDn in the picture) then has not been allocated a function. Again you can drag and drop functions onto a button. 
:#Once you have finished experimenting go back to the Setup tab. Select the appropriate Slingbox remote, go to the 'Advanced' menu at the top and select 'Export Binary Upgrade'. This will produce the BIN file that we have discussed in previous Sections. If you aren‟t sure which Slingbox Chip you have then create a BIN file for the main 2 chips, so that would give you something like 
:::C2010_PL.BIN
:::C2010_RV.BIN

So now you can go back to [[#Installing_the_Binary_file_to_the_Slingbox.|Section 4]] and install the new Custom Remote onto your Slingbox. 
====Finding Missing Codes====
You can often find yourself in the position where the Custom Remote generally works OK but some of the functions are missing or some are sending the wrong code. This is relatively easy to fix by trial and error. The OBC codes must lie between 0-255, so the first thing to do is make a list of the OBC codes that are not being used in the Remote Control. Now use Remotemaster to allocate those codes to the 0-9 buttons and the 15 Custom buttons. Now build a new BIN files, replace the one in your \SBAV\ folder and rerun the "Setup Video Sources" routine. Now try those buttons and see if any of them action the missing function. If you find the missing codes then you can update the original remote file. You may have to repeat this operation 10 times to cover all the missing codes, although you can cut down the number of times by also using the Transport buttons (Play/Pause…) and Channel, Page +/- buttons as well. 

=='''Give your Binary file back to the Community'''==
Finally, remember that it is good to payback. If you find a remote file that works for you then upload it to the JP1 Forums. The way to do this is: 
#Put the 4 Binary files and the Remote Master RMDU file into a ZIP file. I also tend to add a Readme file in case users are unsure how to use the files. Although hopefully they will have read this article and will know what to do. 
#To be really helpful, you should upload your files in 3 different places:
##Upload your ZIP file to the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=87 Slingbox Binary Files] area.
##Upload the Remote Master RMDU source file to the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=98 Slingbox RM Files] area.
##Upload the RMDU file to the appropriate area in the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=4 Device Upgrades] area.
 
I hope these instructions have been helpful. If you have any suggestions for changes or improvements please E-mail me at '''alan (at) rmrsoft (dot) com'''

How to Create Custom Remote Controls and use them on your Slingbox

2015-12-22T19:32:05Z

Alanrichey: /* Hardware */

Written by: Al Richey 

With acknowledgements to Matt Whitlock, BrandonC, The Robman, Nuke12 and AndyBBB, who actually wrote much of this article. All I did was update and combine all the information into one document. 

=='''Background information'''==
One of the most common posts on the support site is about remote codes for unsupported devices. So if you find yourself in this situation I hope this will help. Before detailing the steps to go through there are some basic things you need to understand (this isn‟t essential reading but everything will make much more sense if you do know the details)
==='''Different UEI Chips'''===
: There were five different chips used in Slingboxes. These are designated as JU, PK, PL, RV & JB. If you want to check your type you can verify your IR blaster version in the Slingbox Properties dialog. Then match the IR version number with the chip type using the chart below.
#JU (VERY old US boxes)
#PL (current US boxes)
#PK (never used)
#RV (old European boxes)
#JB (All modern Slingboxes, but compatible with PL files)

So unless you have an old European Solo all you need is the PL file.

==='''Slingplayer Compatibility'''===
: In older versions of Slingplayer it was possible to change the look of the Custom Remote skin‟. Since Slingplayer V1.5 this functionality has been removed and as far as the look of the Remote is concerned you are stuck with the Generic design produced by Sling Media. All we can do is change the codes that are sent when a specific button is pressed. One drawback of the Generic Remote is that it has only the main buttons, so extra buttons on other remotes (such as Audio/Setup…) can not be mapped directly. What we have to do is put them into a Custom Menu which is accessed by tapping on the Menu button on the Generic Remote or right-clicking on the image. (Note: If a remote image has already been produced by Sling it is possible to use that image instead of the generic image)
:

==='''Setup Code Nomenclature'''===
: When you run the Configure Inputs routines in the various Slingplayers and select a supported device, what actually happens is that a Binary Code is downloaded to the Slingbox. 
: This Binary Code details the IR codes that are sent when a specific button is pressed on the remote. Unfortunately the native Slingbox software doesn't use separate binary files that we can edit, their codes are apparently compressed and packaged into special files that we can't do anything with (that I know of). But what we can do instead of editing the built-in codes is to use a separate external upgrade code file. These files have the format such as "C1234_PL.BIN". 
: The first letter of the file describes the type of device, the main ones we are interested in are:
::V which is for VCRs, which encompasses PVRs, DVRs and other recorders
::S which is for Satellite and FTA set top boxes
::C which is for Cable boxes
::Y which is for DVD Players
::R which is for Tuners
:This is followed by a 4-digit code number. For Slingboxes the code numbers can be between 0000-2047 (actually higher in newer Slingboxes but to stay safe we are better staying below 2047). In general, codes below 2000 actually relate to specific boxes, for example V0618 is the code for a TIVO and D0032 is the code for a Pioneer CD Player. But we can feel fairly safe using 2000-2047 for our own codes. The final part of the filename defines the chip for which it will run. 
: So if you were looking for the binary file for a PVR with a code number allocated 1234, designed to run on a PL-equipped Slingbox, you would be searching for a file called V1234_PL.BIN. Note: You must NEVER change the name of the file, as the letter, code number and chip type are also defined inside the file itself.

==='''JP1'''===
:You will hear a lot about "JP1". Basically this is a process whereby people using "One For All‟ (OFA) remote controls can add new codes to their remotes from their PC. The remote control processor inside the Slingbox is made by the same company that makes OFA remotes, so the upgrades are similar. The JP1 tools have been upgraded so that we can now use them to create and modify upgrades for the Slingbox.

=='''The Basic Procedure.'''==
The official procedure to follow is to report the [http://support.slingmedia.com/get/KB-005640.html Lack of a Supported Remote] to SlingMedia and they will add it to the database. In practice, they are not quick at doing this (I have been asking for a remote for over 2 years now), and the updated remote list seems to be only occasionally updated. That may change in the future but for now it is really not a practical quick solution. So for a short term fix what you need to do is to create or acquire the correct Binary code file for your A/V device, and then install it into your Slingbox. This installation process is covered in detail in [[#Installing_the_Binary_file_to_the_Slingbox|Section 4]], so first let‟s see where you can look for these files. 

=='''Obtaining the Binary file for the Custom Remote'''==

#Before starting, make sure in the setup wizard you have tried all the devices by that same manufacturer, even if the model number does not match, and all the associated code numbers. You might be lucky and find one that works and that will save a lot of work. If that doesn‟t solve the problem here is the step by step approach to getting hold of your binary file: 
#Go to the JP1 forum. This has a specific Download area for [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=87 Slingbox Custom Remotes], so go through all those to see if your device has already been done. 
#If it isn‟t there the JP1 forum also has a more general [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=4 File Download Area]. From this page you select the download area for the specific type of device and check there. If you are lucky you will find a source file for using in the program RemoteMaster (RM or KM files), the use of which is discussed in [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]]. 
#Have a look on the Hava forums. They are also using the same chips and the files might be there. Check out this [http://www.myhava.com/forum/viewforum.php?f=17&st=0&sk=t&sd=d&start=0 forum]. You‟re looking for a PK or PL file. They can be imported into Remote Master and then converted to the PK, PL, RV or JU files for the Slingbox. Again this is discussed in [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]]. 
#Find a friend with a Pronto remote. They have a very nice update system and can generate .ccf files that can be used with the tools on the JP1 site to generate the .bin file used by a Slingbox. However, this is not easy, and you will probably need help from the experts on the JP1 forum, but if you want to have a go on your own then you will need the [http://www.hifi-remote.com/forums/dload.php?action=file&file_id=1887 DecodeCCF] program, and [http://www.remotecentral.com/files/index.html .ccf] files. Note that the Pronto can also make .pcf files, but unfortunately we cannot decode those. 
If all of this fails, and you cannot get hold of a BIN file then the Remote will have to be built from scratch. You have 2 options here: 
#Do it yourself by buying a JP1.x learning remote (plus a JP1.x cable), or an IR Widget, and learn the codes needed to control the device. How to do this is covered in [[#Learning_the_IR_codes_from_your_own_remote|Section 5]] & [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]]. 
#Ask someone else to do the work for you. You can try this by posting a request for help in either:
##The [https://community.sling.com/content Slingbox Answers Forum].
##The [http://www.hifi-remote.com/forums/viewforum.php?f=19 JP1 forum]. 
I can normally install your device on my Harmony Universal Remote to mimic the original Remote and learn the codes for you (unless I am away on holiday). 

=='''Installing the Binary file to the Slingbox.'''==
 I have written a comprehensive Installation Guide at

http://placeshiftingenthusiasts.com/how-to-install-a-custom-remote-onto-the-slingbox/

Once you have completed the setup and the BIN files have been downloaded to the Slingbox they are not used any more and can be deleted.

=='''Learning the IR codes from your own remote.'''==
==='''Requirements'''===
Assuming you have decided to create the Remote Binary File yourself, the first stage is to learn the codes from your original Remote. This is what you need:
====Hardware====
#A computer with a USB port (or you can use older serial ports). 
#A Learning Remote and an appropriate JP Cable. Almost any "One For All" or "Radio Shack" remote that has learning will work for this but examples are: 
::URC-6820 (JP1.2)
::URC-8820 (JP1.2)
::URC-10820 (JP1.2)
::Radio Shack Gamer 15-133 (JP1.3)
::Radios Shack Satelite15-134 (JP1.3) 

:Note that some remotes need a JP1.2 cable and some need a JP1.3 cable (and some older, discontinued remotes such as the URC-9810 use a JP1 cable). Make sure the Cable and Remote match. Again the [http://www.hifi-remote.com/forums/viewforum.php?f=10 JP1 forum] is a mine of information. 
:If you are not sure there is a [http://www.hifi-remote.com/forums/dload.php?action=file&file_id=2981 chart of remotes] where you can look up a specific remote to see which format it uses. If you want to buy a cable try [http://www.diygadget.com/ DIYgadget] for the cheaper serial JP1.2/3 cables.

:Although an easy solution is to get a Nevo C2, which has it's own built-in cable. These are available on E-Bay.

:or alternatively

:An IR learning "widget". I got mine from Tommy Tyler through https://www.tindie.com/products/TommyTyler/ir-widget-infrared-remote-control-signal-recorderanalyzer/ (My preferred solution). 

====Software====
:If you are using a Learning Remote: [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=81 IR.EXE] [http://www.hifi-remote.com/forums/dload.php?action=file&file_id=7201 RDF Files] These are support files for the IR.EXE program. If you are using an IR Widget: [http://www.compendiumarcana.com/irwidget/irscope.zip IRSCOPE.EXE] [http://www.ftdichip.com/Drivers/VCP.htm The drivers] [http://www.hifi-remote.com/forums/dload.php?action=file&file_id=922 The IR decode DLL] Or download [http://rmrsoft.com/remote.zip my full IRSCOPE/REMOTEMASTER package]. Much of the JP1 software needs the java runtime environment (JRE) as well. A lot of computers will already have it installed already, but if you need it you can [http://java.sun/j2se/1.4.2/download.html download] Now we can learn the codes. First we will cover the procedure using a Learning Remote, then cover it using an IR Widget. 

===USING A LEARNING REMOTE===
====Getting the Codes from your Remote====
(These steps are based on using the older URC9810, the procedure will be slightly different for other Remotes so you will need to refer to the manuals.) 
:# Tap one of the buttons on the Learning Remote at the top which applies to the device you wish to create the bin file for. (eg. TV, DVD, Satellite). This is not totally necessary, you can always use TV, as it makes no difference to you, but if you subsequently upload the file for other users, it really ought to be for the correct type of device. 
:# At the bottom there will be a button called 'Set'. Keep your finger pushed on that until the LCD changes so you can modify your remote control. 
:# Click down until you come to an option called 'IR LEARN' and click select. 
:# Click one of the buttons on the remote control. For example, the '1' key, the LCD will say "Learning" and the red light will come on. 
:# Put your remote control in front of the learning remote and click the 1 key - if it is added correctly it should say 'Success'. If it fails (shows “Error”) then try again. There are a lot of different techniques for this procedure, the safest bet seems to be press the button on the Learning Remote, wait for 2 seconds then hold the equivalent key on the original Remote until the red light goes on. If you get a bad „learn‟, try just tapping quickly on the original key. A full description of these options is [http://www.hifi-remote.com/forums/viewtopic.php?t=3943 here]. 
:# Repeat this step for each of the keys you want to learn and have on your Slingbox Remote. If you get the "Memory Full" message then you will have to repeat this operation for the remaining keys after you have uploaded the first set of codes to your PC. 

====Getting the Codes onto your PC.====
 
:#Install IR.EXE onto your PC. It comes as a ZIP file rather than an installation package, which you need to unzip to your PC. The files can actually go anywhere but as a bit of tidy person (geek?) I created a C:\Program Files\IR\ folder and put the files in there and then created a shortcut on the Desktop. Important Note: For Windows VISTA users, I have found that I need to run the program in Windows XP Compatibility Mode to make it recognise the JP1 interface. Just right-click on IR.EXE, select Properties, then the Compatibility Tab and check the appropriate box. 
:#Create a sub folder called \RDF\ in whatever folder you have put the IR program and extract the RDF support files into that folder. 
:#Get your JP1 cable out and turn your remote control over, open the battery compartment and plug the JP1 6 pin connector into the Learning remote (you will see 6 needles where it plugs into). There are 2 ways to plug it in, but don‟t worry, you won‟t cause any damage by plugging it in the wrong way. Try them both if the first one fails. 
:#Plug the USB plug into your computer. As with any external piece of hardware you will need to install the drivers. There are drivers for the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=81 JP1 Remotes] and the [http://www.ftdichip.com/Drivers/VCP.htm JP1.2/3 Remotes]. Personally I use the JP1 ones dated 12 Feb 2008 and they work fine in Windows XP and also in Vista as long as the Windows XP Compatibility flag is set. 
:#Now open IR.exe. If you get told your RDF directory isn't valid, click OK and ignore this for now. It will look something like this: (Note this is a screenshot of V8.0. If that version hasn‟t been released yet, V7.15 looks very similar but does not have the icons at the top. [[Image:IR-general.jpg]] 
:#Go to File > Set Directory > RDF Path >. Select your RDF directory. You need to double click the RDF directory or it won't take. 
:#For peace of mind go to Interface > Check Driver... it should say the interface is connected. If it does then that's fine, if it gives an error message “Unable to open device, check connection” then it is not seeing the JP1 cable so you need to check the cable and the drivers. If it gives the error message “The remote is not acknowledging signals from the interface” then the cable is working fine but it is not seeing the remote. Try reversing the cable connection to the remote and hopefully that will cure the problem. 
:#Now click the "Download From Remote" button. 
:#Then click the "Learned Signals" tab (second from last one). It will look something like this: [[Image:IR-learned1.jpg]] 
:#On the left hand side there should be a list with the device type and the keys - eg "TV: 1". Click on it and details should show up in the right hand side listview. 
:#The first thing we need to make a note of is the Protocol (JVC) in this case, then the Device Number (239 in this case) and if it is displayed, the Sub-Device number. Then for each of the learned keys note down the OBC, Hex Code and EFC numbers. 
:#If you get the "MEM FULL" message on the Remote then Use File > Save As to keep a copy then tap the "Delete All" button, go back to the General Tab and tap the "Upload To remote" button to clear the Remote. Then learn the remaining buttons and follow the same procedure. Once they are all done, use the use the File > Save As command to save a copy of the final results. 
However, if you see a screen like this, it means that the protocol used by your remote is not recognised by the system. That means that you cannot create the Remote yourself but will have to ask the people on the JP1 forum to help you out. They have a much deeper understanding of the IR formats, and can often dig deeper into the signals and figure out the codes. [[Image:IR-learned2.jpg]] 
The procedure to do this is to use the File > Save As menu option to save the IR source file(s) (I tend to ZIP them up if there are more than one). Now upload them to the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=35 Diagnosis Area] in the File Section of the JP1 Forum. 
Check the file has been added, and make a record of it‟s location by right-clicking on it and select „Copy Link Location‟. 
Now create a new topic in the [http://www.hifi-remote.com/forums/viewforum.php?f=20 Protocol Decode Forum] and plead for some help, quoting the device Manufacturer and Model Number and the link to the IR source files. Offer incentives (money, beer, everlasting gratitude….) and you might be lucky. The experts may produce the RemoteMaster source file or even the Remote Binary files themselves. Now you can move on to [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]] for building the Remote BIN files. 

===USING AN IR WIDGET===
If you are using an IR Widget there is an excellent guide [http://freepdfhosting.com/2da0b92e8c.pdf here] on the Tindle site. So I suggest you download that and read it thoroughly. There is no point in repeating it here, but just to emphasise a few points: 
:#You will want to regularly check for updates to the decodeir.dll. As new protocols are recognized, this dll will change. 
:#There is no way to save the learned values for importing into RemoteMaster (where you will make the remote) so you will need to write them down. 
:#Although I tend to put programs into C:\Program Files\.... this can be a bit dodgy in Windows as programs cannot save files to this area because of security limitations. So it might be safer to install it under \Documents\ 
:#The Guide has a very useful section comparing using a Learning Remotes and the IR Widget and highlighting the differences, (For example "Key" is equivalent to "OBC") so you could check out the previous sub-section covering using IR.EXE and the Learning Remote. And then you will understand this section. When complete you can move onto [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]] to create the Binary file. 

=='''Creating your own Binary files using RemoteMaster'''==
:#To make life easier I have packaged a full set of the latest files required and uploaded them to my site. Just download them from [http://www.rmrsoft.com/remote.zip here] and unzip them onto your computer. 
:#Start RemoteMaster.EXE. You may be promoted to highlight the folder the folder that contains the RDF files (Highlight the \RDF\ folder in the folder where you placed Remotemaster). You may also have to do the same for the Images folder. The display will now look something like this:[[Image:RM-setup.jpg]] 
:#If you have obtained an .rmdu file then use the File > Open menu option to load the file. If you have obtained a .bin file then use the Advanced > Import Binary Upgrade to load up the details. If you have not obtained a file then you will have to input the codes manually. 
:#Now to explain the main Setup Tab: '''Description ''': Use anything you like, I tend to use the device name. '''Remote''': Select the one appropriate for your chip. '''Device Type''': Should be set to the correct type of device (as covered in Paragraph 3 of Section 1). '''Setup Code''': This is where you put the 4-digit code. In theory it can be any number between 0000 and 2047, but as explained in Section 1 Paragraph 3, numbers below 2000 may actually be already allocated to specific devices, so to be safe I personally use 2010. Fell free to use your own value. '''Protocol''': From the dropdown list select the Protocol you discovered when you used IR.EXE/IRSCOPE.EXE. '''Device''': Type in the Device code you recorded from IR.EXE/IRSCOPE.EXE. '''Sub-Device''': If applicable type in the Sub-Device code you recorded from IR.EXE/ IRSCOPE.EXE. 
:#Now tap on the Functions Tab [[Image:RM-functions.jpg]] This picture shows the program with an .rmdu file or .bin file already imported; otherwise the code columns will be blank. The entries are fully configurable, so if there are pre-defined functions that you do not need (pip swap, pipmove..) then you highlight them and tap the "Delete" button. If you have a function that is not pre-defined (Audio, Setup…) then tap the "New" button and enter them. Now fill in the codes for each button that you recorded. You just put in the OBC value and press <Enter>, the other 2 values will be generated automatically based on the protocol you selected. Also, if you used a JP1 learning remote, there's a way to cut and paste all the codes which saves needing to enter them all. In IR, if you select File > Summary you get a page listing lots of stuff. If you scroll down, you'll see a list of learn decodes. You can cut and paste this list into Excel, then you can re-arrange the columns and just select the button names and OBC codes to cut and paste into RM. You can move the RM columns, so if the OBC column isn't the one next to the button names, you can move it there. 
:#Now tap on the Buttons Tab [[Image:RM-buttons.jpg]] This is where you map the defined functions onto the available buttons. Simply tap the Auto-Assign button which should allocate most of the buttons. For any buttons left in red drag the function name from the table on the left to the function column on the right. But note that not all these buttons are available on a Slingplayer Generic Remote. For example the 'Slow' and 'Eject' buttons do not exist on a Generic Remote. So only map the functions onto the buttons that actually exist (You will see that when you check out the Layout Tab, and from experience when you have done this a few times). The important ones to note are the Custom 10-29 buttons. These are the ones you use for the functions you need that aren't on the generic remote and they subsequently appear in the drop down menu of the remote as Custom options (except for Custom 22-26 which are pre-allocated to the colour buttons). 
:#Now tap on the Layout Tab. [[Image:RM-layout.jpg]] This shows the generic Slingplayer remote and shows the buttons you can actually use in the Buttons Tab. If a button shows yellow then that means it is in use. If it shows black (the PgUp/PgDn in the picture) then has not been allocated a function. Again you can drag and drop functions onto a button. 
:#Once you have finished experimenting go back to the Setup tab. Select the appropriate Slingbox remote, go to the 'Advanced' menu at the top and select 'Export Binary Upgrade'. This will produce the BIN file that we have discussed in previous Sections. If you aren‟t sure which Slingbox Chip you have then create a BIN file for the main 2 chips, so that would give you something like 
:::C2010_PL.BIN
:::C2010_RV.BIN

So now you can go back to [[#Installing_the_Binary_file_to_the_Slingbox.|Section 4]] and install the new Custom Remote onto your Slingbox. 
====Finding Missing Codes====
You can often find yourself in the position where the Custom Remote generally works OK but some of the functions are missing or some are sending the wrong code. This is relatively easy to fix by trial and error. The OBC codes must lie between 0-255, so the first thing to do is make a list of the OBC codes that are not being used in the Remote Control. Now use Remotemaster to allocate those codes to the 0-9 buttons and the 15 Custom buttons. Now build a new BIN files, replace the one in your \SBAV\ folder and rerun the "Setup Video Sources" routine. Now try those buttons and see if any of them action the missing function. If you find the missing codes then you can update the original remote file. You may have to repeat this operation 10 times to cover all the missing codes, although you can cut down the number of times by also using the Transport buttons (Play/Pause…) and Channel, Page +/- buttons as well. 

=='''Give your Binary file back to the Community'''==
Finally, remember that it is good to payback. If you find a remote file that works for you then upload it to the JP1 Forums. The way to do this is: 
#Put the 4 Binary files and the Remote Master RMDU file into a ZIP file. I also tend to add a Readme file in case users are unsure how to use the files. Although hopefully they will have read this article and will know what to do. 
#To be really helpful, you should upload your files in 3 different places:
##Upload your ZIP file to the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=87 Slingbox Binary Files] area.
##Upload the Remote Master RMDU source file to the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=98 Slingbox RM Files] area.
##Upload the RMDU file to the appropriate area in the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=4 Device Upgrades] area.
 
I hope these instructions have been helpful. If you have any suggestions for changes or improvements please E-mail me at '''alan (at) rmrsoft (dot) com'''

How to Create Custom Remote Controls and use them on your Slingbox

2015-12-22T19:31:31Z

Alanrichey: /* Hardware */

Written by: Al Richey 

With acknowledgements to Matt Whitlock, BrandonC, The Robman, Nuke12 and AndyBBB, who actually wrote much of this article. All I did was update and combine all the information into one document. 

=='''Background information'''==
One of the most common posts on the support site is about remote codes for unsupported devices. So if you find yourself in this situation I hope this will help. Before detailing the steps to go through there are some basic things you need to understand (this isn‟t essential reading but everything will make much more sense if you do know the details)
==='''Different UEI Chips'''===
: There were five different chips used in Slingboxes. These are designated as JU, PK, PL, RV & JB. If you want to check your type you can verify your IR blaster version in the Slingbox Properties dialog. Then match the IR version number with the chip type using the chart below.
#JU (VERY old US boxes)
#PL (current US boxes)
#PK (never used)
#RV (old European boxes)
#JB (All modern Slingboxes, but compatible with PL files)

So unless you have an old European Solo all you need is the PL file.

==='''Slingplayer Compatibility'''===
: In older versions of Slingplayer it was possible to change the look of the Custom Remote skin‟. Since Slingplayer V1.5 this functionality has been removed and as far as the look of the Remote is concerned you are stuck with the Generic design produced by Sling Media. All we can do is change the codes that are sent when a specific button is pressed. One drawback of the Generic Remote is that it has only the main buttons, so extra buttons on other remotes (such as Audio/Setup…) can not be mapped directly. What we have to do is put them into a Custom Menu which is accessed by tapping on the Menu button on the Generic Remote or right-clicking on the image. (Note: If a remote image has already been produced by Sling it is possible to use that image instead of the generic image)
:

==='''Setup Code Nomenclature'''===
: When you run the Configure Inputs routines in the various Slingplayers and select a supported device, what actually happens is that a Binary Code is downloaded to the Slingbox. 
: This Binary Code details the IR codes that are sent when a specific button is pressed on the remote. Unfortunately the native Slingbox software doesn't use separate binary files that we can edit, their codes are apparently compressed and packaged into special files that we can't do anything with (that I know of). But what we can do instead of editing the built-in codes is to use a separate external upgrade code file. These files have the format such as "C1234_PL.BIN". 
: The first letter of the file describes the type of device, the main ones we are interested in are:
::V which is for VCRs, which encompasses PVRs, DVRs and other recorders
::S which is for Satellite and FTA set top boxes
::C which is for Cable boxes
::Y which is for DVD Players
::R which is for Tuners
:This is followed by a 4-digit code number. For Slingboxes the code numbers can be between 0000-2047 (actually higher in newer Slingboxes but to stay safe we are better staying below 2047). In general, codes below 2000 actually relate to specific boxes, for example V0618 is the code for a TIVO and D0032 is the code for a Pioneer CD Player. But we can feel fairly safe using 2000-2047 for our own codes. The final part of the filename defines the chip for which it will run. 
: So if you were looking for the binary file for a PVR with a code number allocated 1234, designed to run on a PL-equipped Slingbox, you would be searching for a file called V1234_PL.BIN. Note: You must NEVER change the name of the file, as the letter, code number and chip type are also defined inside the file itself.

==='''JP1'''===
:You will hear a lot about "JP1". Basically this is a process whereby people using "One For All‟ (OFA) remote controls can add new codes to their remotes from their PC. The remote control processor inside the Slingbox is made by the same company that makes OFA remotes, so the upgrades are similar. The JP1 tools have been upgraded so that we can now use them to create and modify upgrades for the Slingbox.

=='''The Basic Procedure.'''==
The official procedure to follow is to report the [http://support.slingmedia.com/get/KB-005640.html Lack of a Supported Remote] to SlingMedia and they will add it to the database. In practice, they are not quick at doing this (I have been asking for a remote for over 2 years now), and the updated remote list seems to be only occasionally updated. That may change in the future but for now it is really not a practical quick solution. So for a short term fix what you need to do is to create or acquire the correct Binary code file for your A/V device, and then install it into your Slingbox. This installation process is covered in detail in [[#Installing_the_Binary_file_to_the_Slingbox|Section 4]], so first let‟s see where you can look for these files. 

=='''Obtaining the Binary file for the Custom Remote'''==

#Before starting, make sure in the setup wizard you have tried all the devices by that same manufacturer, even if the model number does not match, and all the associated code numbers. You might be lucky and find one that works and that will save a lot of work. If that doesn‟t solve the problem here is the step by step approach to getting hold of your binary file: 
#Go to the JP1 forum. This has a specific Download area for [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=87 Slingbox Custom Remotes], so go through all those to see if your device has already been done. 
#If it isn‟t there the JP1 forum also has a more general [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=4 File Download Area]. From this page you select the download area for the specific type of device and check there. If you are lucky you will find a source file for using in the program RemoteMaster (RM or KM files), the use of which is discussed in [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]]. 
#Have a look on the Hava forums. They are also using the same chips and the files might be there. Check out this [http://www.myhava.com/forum/viewforum.php?f=17&st=0&sk=t&sd=d&start=0 forum]. You‟re looking for a PK or PL file. They can be imported into Remote Master and then converted to the PK, PL, RV or JU files for the Slingbox. Again this is discussed in [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]]. 
#Find a friend with a Pronto remote. They have a very nice update system and can generate .ccf files that can be used with the tools on the JP1 site to generate the .bin file used by a Slingbox. However, this is not easy, and you will probably need help from the experts on the JP1 forum, but if you want to have a go on your own then you will need the [http://www.hifi-remote.com/forums/dload.php?action=file&file_id=1887 DecodeCCF] program, and [http://www.remotecentral.com/files/index.html .ccf] files. Note that the Pronto can also make .pcf files, but unfortunately we cannot decode those. 
If all of this fails, and you cannot get hold of a BIN file then the Remote will have to be built from scratch. You have 2 options here: 
#Do it yourself by buying a JP1.x learning remote (plus a JP1.x cable), or an IR Widget, and learn the codes needed to control the device. How to do this is covered in [[#Learning_the_IR_codes_from_your_own_remote|Section 5]] & [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]]. 
#Ask someone else to do the work for you. You can try this by posting a request for help in either:
##The [https://community.sling.com/content Slingbox Answers Forum].
##The [http://www.hifi-remote.com/forums/viewforum.php?f=19 JP1 forum]. 
I can normally install your device on my Harmony Universal Remote to mimic the original Remote and learn the codes for you (unless I am away on holiday). 

=='''Installing the Binary file to the Slingbox.'''==
 I have written a comprehensive Installation Guide at

http://placeshiftingenthusiasts.com/how-to-install-a-custom-remote-onto-the-slingbox/

Once you have completed the setup and the BIN files have been downloaded to the Slingbox they are not used any more and can be deleted.

=='''Learning the IR codes from your own remote.'''==
==='''Requirements'''===
Assuming you have decided to create the Remote Binary File yourself, the first stage is to learn the codes from your original Remote. This is what you need:
====Hardware====
#A computer with a USB port (or you can use older serial ports). 
#A Learning Remote and an appropriate JP Cable. Almost any "One For All" or "Radio Shack" remote that has learning will work for this but examples are: 
::URC-6820 (JP1.2)
::URC-8820 (JP1.2)
::URC-10820 (JP1.2)
::Radio Shack Gamer 15-133 (JP1.3)
::Radios Shack Satelite15-134 (JP1.3) 

:Note that some remotes need a JP1.2 cable and some need a JP1.3 cable (and some older, discontinued remotes such as the URC-9810 use a JP1 cable). Make sure the Cable and Remote match. Again the [http://www.hifi-remote.com/forums/viewforum.php?f=10 JP1 forum] is a mine of information. 
:If you are not sure there is a [http://www.hifi-remote.com/forums/dload.php?action=file&file_id=2981 chart of remotes] where you can look up a specific remote to see which format it uses. If you want to buy a cable try [http://www.diygadget.com/ DIYgadget] for the cheaper serial JP1.2/3 cables.

Although an easy solution is to get a Nevo C2, which has it's own built-in cable. These are available on E-Bay.

or alternatively

An IR learning "widget". I got mine from Tommy Tyler through https://www.tindie.com/products/TommyTyler/ir-widget-infrared-remote-control-signal-recorderanalyzer/ (My preferred solution). 

====Software====
:If you are using a Learning Remote: [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=81 IR.EXE] [http://www.hifi-remote.com/forums/dload.php?action=file&file_id=7201 RDF Files] These are support files for the IR.EXE program. If you are using an IR Widget: [http://www.compendiumarcana.com/irwidget/irscope.zip IRSCOPE.EXE] [http://www.ftdichip.com/Drivers/VCP.htm The drivers] [http://www.hifi-remote.com/forums/dload.php?action=file&file_id=922 The IR decode DLL] Or download [http://rmrsoft.com/remote.zip my full IRSCOPE/REMOTEMASTER package]. Much of the JP1 software needs the java runtime environment (JRE) as well. A lot of computers will already have it installed already, but if you need it you can [http://java.sun/j2se/1.4.2/download.html download] Now we can learn the codes. First we will cover the procedure using a Learning Remote, then cover it using an IR Widget. 

===USING A LEARNING REMOTE===
====Getting the Codes from your Remote====
(These steps are based on using the older URC9810, the procedure will be slightly different for other Remotes so you will need to refer to the manuals.) 
:# Tap one of the buttons on the Learning Remote at the top which applies to the device you wish to create the bin file for. (eg. TV, DVD, Satellite). This is not totally necessary, you can always use TV, as it makes no difference to you, but if you subsequently upload the file for other users, it really ought to be for the correct type of device. 
:# At the bottom there will be a button called 'Set'. Keep your finger pushed on that until the LCD changes so you can modify your remote control. 
:# Click down until you come to an option called 'IR LEARN' and click select. 
:# Click one of the buttons on the remote control. For example, the '1' key, the LCD will say "Learning" and the red light will come on. 
:# Put your remote control in front of the learning remote and click the 1 key - if it is added correctly it should say 'Success'. If it fails (shows “Error”) then try again. There are a lot of different techniques for this procedure, the safest bet seems to be press the button on the Learning Remote, wait for 2 seconds then hold the equivalent key on the original Remote until the red light goes on. If you get a bad „learn‟, try just tapping quickly on the original key. A full description of these options is [http://www.hifi-remote.com/forums/viewtopic.php?t=3943 here]. 
:# Repeat this step for each of the keys you want to learn and have on your Slingbox Remote. If you get the "Memory Full" message then you will have to repeat this operation for the remaining keys after you have uploaded the first set of codes to your PC. 

====Getting the Codes onto your PC.====
 
:#Install IR.EXE onto your PC. It comes as a ZIP file rather than an installation package, which you need to unzip to your PC. The files can actually go anywhere but as a bit of tidy person (geek?) I created a C:\Program Files\IR\ folder and put the files in there and then created a shortcut on the Desktop. Important Note: For Windows VISTA users, I have found that I need to run the program in Windows XP Compatibility Mode to make it recognise the JP1 interface. Just right-click on IR.EXE, select Properties, then the Compatibility Tab and check the appropriate box. 
:#Create a sub folder called \RDF\ in whatever folder you have put the IR program and extract the RDF support files into that folder. 
:#Get your JP1 cable out and turn your remote control over, open the battery compartment and plug the JP1 6 pin connector into the Learning remote (you will see 6 needles where it plugs into). There are 2 ways to plug it in, but don‟t worry, you won‟t cause any damage by plugging it in the wrong way. Try them both if the first one fails. 
:#Plug the USB plug into your computer. As with any external piece of hardware you will need to install the drivers. There are drivers for the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=81 JP1 Remotes] and the [http://www.ftdichip.com/Drivers/VCP.htm JP1.2/3 Remotes]. Personally I use the JP1 ones dated 12 Feb 2008 and they work fine in Windows XP and also in Vista as long as the Windows XP Compatibility flag is set. 
:#Now open IR.exe. If you get told your RDF directory isn't valid, click OK and ignore this for now. It will look something like this: (Note this is a screenshot of V8.0. If that version hasn‟t been released yet, V7.15 looks very similar but does not have the icons at the top. [[Image:IR-general.jpg]] 
:#Go to File > Set Directory > RDF Path >. Select your RDF directory. You need to double click the RDF directory or it won't take. 
:#For peace of mind go to Interface > Check Driver... it should say the interface is connected. If it does then that's fine, if it gives an error message “Unable to open device, check connection” then it is not seeing the JP1 cable so you need to check the cable and the drivers. If it gives the error message “The remote is not acknowledging signals from the interface” then the cable is working fine but it is not seeing the remote. Try reversing the cable connection to the remote and hopefully that will cure the problem. 
:#Now click the "Download From Remote" button. 
:#Then click the "Learned Signals" tab (second from last one). It will look something like this: [[Image:IR-learned1.jpg]] 
:#On the left hand side there should be a list with the device type and the keys - eg "TV: 1". Click on it and details should show up in the right hand side listview. 
:#The first thing we need to make a note of is the Protocol (JVC) in this case, then the Device Number (239 in this case) and if it is displayed, the Sub-Device number. Then for each of the learned keys note down the OBC, Hex Code and EFC numbers. 
:#If you get the "MEM FULL" message on the Remote then Use File > Save As to keep a copy then tap the "Delete All" button, go back to the General Tab and tap the "Upload To remote" button to clear the Remote. Then learn the remaining buttons and follow the same procedure. Once they are all done, use the use the File > Save As command to save a copy of the final results. 
However, if you see a screen like this, it means that the protocol used by your remote is not recognised by the system. That means that you cannot create the Remote yourself but will have to ask the people on the JP1 forum to help you out. They have a much deeper understanding of the IR formats, and can often dig deeper into the signals and figure out the codes. [[Image:IR-learned2.jpg]] 
The procedure to do this is to use the File > Save As menu option to save the IR source file(s) (I tend to ZIP them up if there are more than one). Now upload them to the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=35 Diagnosis Area] in the File Section of the JP1 Forum. 
Check the file has been added, and make a record of it‟s location by right-clicking on it and select „Copy Link Location‟. 
Now create a new topic in the [http://www.hifi-remote.com/forums/viewforum.php?f=20 Protocol Decode Forum] and plead for some help, quoting the device Manufacturer and Model Number and the link to the IR source files. Offer incentives (money, beer, everlasting gratitude….) and you might be lucky. The experts may produce the RemoteMaster source file or even the Remote Binary files themselves. Now you can move on to [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]] for building the Remote BIN files. 

===USING AN IR WIDGET===
If you are using an IR Widget there is an excellent guide [http://freepdfhosting.com/2da0b92e8c.pdf here] on the Tindle site. So I suggest you download that and read it thoroughly. There is no point in repeating it here, but just to emphasise a few points: 
:#You will want to regularly check for updates to the decodeir.dll. As new protocols are recognized, this dll will change. 
:#There is no way to save the learned values for importing into RemoteMaster (where you will make the remote) so you will need to write them down. 
:#Although I tend to put programs into C:\Program Files\.... this can be a bit dodgy in Windows as programs cannot save files to this area because of security limitations. So it might be safer to install it under \Documents\ 
:#The Guide has a very useful section comparing using a Learning Remotes and the IR Widget and highlighting the differences, (For example "Key" is equivalent to "OBC") so you could check out the previous sub-section covering using IR.EXE and the Learning Remote. And then you will understand this section. When complete you can move onto [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]] to create the Binary file. 

=='''Creating your own Binary files using RemoteMaster'''==
:#To make life easier I have packaged a full set of the latest files required and uploaded them to my site. Just download them from [http://www.rmrsoft.com/remote.zip here] and unzip them onto your computer. 
:#Start RemoteMaster.EXE. You may be promoted to highlight the folder the folder that contains the RDF files (Highlight the \RDF\ folder in the folder where you placed Remotemaster). You may also have to do the same for the Images folder. The display will now look something like this:[[Image:RM-setup.jpg]] 
:#If you have obtained an .rmdu file then use the File > Open menu option to load the file. If you have obtained a .bin file then use the Advanced > Import Binary Upgrade to load up the details. If you have not obtained a file then you will have to input the codes manually. 
:#Now to explain the main Setup Tab: '''Description ''': Use anything you like, I tend to use the device name. '''Remote''': Select the one appropriate for your chip. '''Device Type''': Should be set to the correct type of device (as covered in Paragraph 3 of Section 1). '''Setup Code''': This is where you put the 4-digit code. In theory it can be any number between 0000 and 2047, but as explained in Section 1 Paragraph 3, numbers below 2000 may actually be already allocated to specific devices, so to be safe I personally use 2010. Fell free to use your own value. '''Protocol''': From the dropdown list select the Protocol you discovered when you used IR.EXE/IRSCOPE.EXE. '''Device''': Type in the Device code you recorded from IR.EXE/IRSCOPE.EXE. '''Sub-Device''': If applicable type in the Sub-Device code you recorded from IR.EXE/ IRSCOPE.EXE. 
:#Now tap on the Functions Tab [[Image:RM-functions.jpg]] This picture shows the program with an .rmdu file or .bin file already imported; otherwise the code columns will be blank. The entries are fully configurable, so if there are pre-defined functions that you do not need (pip swap, pipmove..) then you highlight them and tap the "Delete" button. If you have a function that is not pre-defined (Audio, Setup…) then tap the "New" button and enter them. Now fill in the codes for each button that you recorded. You just put in the OBC value and press <Enter>, the other 2 values will be generated automatically based on the protocol you selected. Also, if you used a JP1 learning remote, there's a way to cut and paste all the codes which saves needing to enter them all. In IR, if you select File > Summary you get a page listing lots of stuff. If you scroll down, you'll see a list of learn decodes. You can cut and paste this list into Excel, then you can re-arrange the columns and just select the button names and OBC codes to cut and paste into RM. You can move the RM columns, so if the OBC column isn't the one next to the button names, you can move it there. 
:#Now tap on the Buttons Tab [[Image:RM-buttons.jpg]] This is where you map the defined functions onto the available buttons. Simply tap the Auto-Assign button which should allocate most of the buttons. For any buttons left in red drag the function name from the table on the left to the function column on the right. But note that not all these buttons are available on a Slingplayer Generic Remote. For example the 'Slow' and 'Eject' buttons do not exist on a Generic Remote. So only map the functions onto the buttons that actually exist (You will see that when you check out the Layout Tab, and from experience when you have done this a few times). The important ones to note are the Custom 10-29 buttons. These are the ones you use for the functions you need that aren't on the generic remote and they subsequently appear in the drop down menu of the remote as Custom options (except for Custom 22-26 which are pre-allocated to the colour buttons). 
:#Now tap on the Layout Tab. [[Image:RM-layout.jpg]] This shows the generic Slingplayer remote and shows the buttons you can actually use in the Buttons Tab. If a button shows yellow then that means it is in use. If it shows black (the PgUp/PgDn in the picture) then has not been allocated a function. Again you can drag and drop functions onto a button. 
:#Once you have finished experimenting go back to the Setup tab. Select the appropriate Slingbox remote, go to the 'Advanced' menu at the top and select 'Export Binary Upgrade'. This will produce the BIN file that we have discussed in previous Sections. If you aren‟t sure which Slingbox Chip you have then create a BIN file for the main 2 chips, so that would give you something like 
:::C2010_PL.BIN
:::C2010_RV.BIN

So now you can go back to [[#Installing_the_Binary_file_to_the_Slingbox.|Section 4]] and install the new Custom Remote onto your Slingbox. 
====Finding Missing Codes====
You can often find yourself in the position where the Custom Remote generally works OK but some of the functions are missing or some are sending the wrong code. This is relatively easy to fix by trial and error. The OBC codes must lie between 0-255, so the first thing to do is make a list of the OBC codes that are not being used in the Remote Control. Now use Remotemaster to allocate those codes to the 0-9 buttons and the 15 Custom buttons. Now build a new BIN files, replace the one in your \SBAV\ folder and rerun the "Setup Video Sources" routine. Now try those buttons and see if any of them action the missing function. If you find the missing codes then you can update the original remote file. You may have to repeat this operation 10 times to cover all the missing codes, although you can cut down the number of times by also using the Transport buttons (Play/Pause…) and Channel, Page +/- buttons as well. 

=='''Give your Binary file back to the Community'''==
Finally, remember that it is good to payback. If you find a remote file that works for you then upload it to the JP1 Forums. The way to do this is: 
#Put the 4 Binary files and the Remote Master RMDU file into a ZIP file. I also tend to add a Readme file in case users are unsure how to use the files. Although hopefully they will have read this article and will know what to do. 
#To be really helpful, you should upload your files in 3 different places:
##Upload your ZIP file to the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=87 Slingbox Binary Files] area.
##Upload the Remote Master RMDU source file to the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=98 Slingbox RM Files] area.
##Upload the RMDU file to the appropriate area in the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=4 Device Upgrades] area.
 
I hope these instructions have been helpful. If you have any suggestions for changes or improvements please E-mail me at '''alan (at) rmrsoft (dot) com'''

How to Create Custom Remote Controls and use them on your Slingbox

2015-12-22T19:28:19Z

Alanrichey:

Written by: Al Richey 

With acknowledgements to Matt Whitlock, BrandonC, The Robman, Nuke12 and AndyBBB, who actually wrote much of this article. All I did was update and combine all the information into one document. 

=='''Background information'''==
One of the most common posts on the support site is about remote codes for unsupported devices. So if you find yourself in this situation I hope this will help. Before detailing the steps to go through there are some basic things you need to understand (this isn‟t essential reading but everything will make much more sense if you do know the details)
==='''Different UEI Chips'''===
: There were five different chips used in Slingboxes. These are designated as JU, PK, PL, RV & JB. If you want to check your type you can verify your IR blaster version in the Slingbox Properties dialog. Then match the IR version number with the chip type using the chart below.
#JU (VERY old US boxes)
#PL (current US boxes)
#PK (never used)
#RV (old European boxes)
#JB (All modern Slingboxes, but compatible with PL files)

So unless you have an old European Solo all you need is the PL file.

==='''Slingplayer Compatibility'''===
: In older versions of Slingplayer it was possible to change the look of the Custom Remote skin‟. Since Slingplayer V1.5 this functionality has been removed and as far as the look of the Remote is concerned you are stuck with the Generic design produced by Sling Media. All we can do is change the codes that are sent when a specific button is pressed. One drawback of the Generic Remote is that it has only the main buttons, so extra buttons on other remotes (such as Audio/Setup…) can not be mapped directly. What we have to do is put them into a Custom Menu which is accessed by tapping on the Menu button on the Generic Remote or right-clicking on the image. (Note: If a remote image has already been produced by Sling it is possible to use that image instead of the generic image)
:

==='''Setup Code Nomenclature'''===
: When you run the Configure Inputs routines in the various Slingplayers and select a supported device, what actually happens is that a Binary Code is downloaded to the Slingbox. 
: This Binary Code details the IR codes that are sent when a specific button is pressed on the remote. Unfortunately the native Slingbox software doesn't use separate binary files that we can edit, their codes are apparently compressed and packaged into special files that we can't do anything with (that I know of). But what we can do instead of editing the built-in codes is to use a separate external upgrade code file. These files have the format such as "C1234_PL.BIN". 
: The first letter of the file describes the type of device, the main ones we are interested in are:
::V which is for VCRs, which encompasses PVRs, DVRs and other recorders
::S which is for Satellite and FTA set top boxes
::C which is for Cable boxes
::Y which is for DVD Players
::R which is for Tuners
:This is followed by a 4-digit code number. For Slingboxes the code numbers can be between 0000-2047 (actually higher in newer Slingboxes but to stay safe we are better staying below 2047). In general, codes below 2000 actually relate to specific boxes, for example V0618 is the code for a TIVO and D0032 is the code for a Pioneer CD Player. But we can feel fairly safe using 2000-2047 for our own codes. The final part of the filename defines the chip for which it will run. 
: So if you were looking for the binary file for a PVR with a code number allocated 1234, designed to run on a PL-equipped Slingbox, you would be searching for a file called V1234_PL.BIN. Note: You must NEVER change the name of the file, as the letter, code number and chip type are also defined inside the file itself.

==='''JP1'''===
:You will hear a lot about "JP1". Basically this is a process whereby people using "One For All‟ (OFA) remote controls can add new codes to their remotes from their PC. The remote control processor inside the Slingbox is made by the same company that makes OFA remotes, so the upgrades are similar. The JP1 tools have been upgraded so that we can now use them to create and modify upgrades for the Slingbox.

=='''The Basic Procedure.'''==
The official procedure to follow is to report the [http://support.slingmedia.com/get/KB-005640.html Lack of a Supported Remote] to SlingMedia and they will add it to the database. In practice, they are not quick at doing this (I have been asking for a remote for over 2 years now), and the updated remote list seems to be only occasionally updated. That may change in the future but for now it is really not a practical quick solution. So for a short term fix what you need to do is to create or acquire the correct Binary code file for your A/V device, and then install it into your Slingbox. This installation process is covered in detail in [[#Installing_the_Binary_file_to_the_Slingbox|Section 4]], so first let‟s see where you can look for these files. 

=='''Obtaining the Binary file for the Custom Remote'''==

#Before starting, make sure in the setup wizard you have tried all the devices by that same manufacturer, even if the model number does not match, and all the associated code numbers. You might be lucky and find one that works and that will save a lot of work. If that doesn‟t solve the problem here is the step by step approach to getting hold of your binary file: 
#Go to the JP1 forum. This has a specific Download area for [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=87 Slingbox Custom Remotes], so go through all those to see if your device has already been done. 
#If it isn‟t there the JP1 forum also has a more general [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=4 File Download Area]. From this page you select the download area for the specific type of device and check there. If you are lucky you will find a source file for using in the program RemoteMaster (RM or KM files), the use of which is discussed in [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]]. 
#Have a look on the Hava forums. They are also using the same chips and the files might be there. Check out this [http://www.myhava.com/forum/viewforum.php?f=17&st=0&sk=t&sd=d&start=0 forum]. You‟re looking for a PK or PL file. They can be imported into Remote Master and then converted to the PK, PL, RV or JU files for the Slingbox. Again this is discussed in [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]]. 
#Find a friend with a Pronto remote. They have a very nice update system and can generate .ccf files that can be used with the tools on the JP1 site to generate the .bin file used by a Slingbox. However, this is not easy, and you will probably need help from the experts on the JP1 forum, but if you want to have a go on your own then you will need the [http://www.hifi-remote.com/forums/dload.php?action=file&file_id=1887 DecodeCCF] program, and [http://www.remotecentral.com/files/index.html .ccf] files. Note that the Pronto can also make .pcf files, but unfortunately we cannot decode those. 
If all of this fails, and you cannot get hold of a BIN file then the Remote will have to be built from scratch. You have 2 options here: 
#Do it yourself by buying a JP1.x learning remote (plus a JP1.x cable), or an IR Widget, and learn the codes needed to control the device. How to do this is covered in [[#Learning_the_IR_codes_from_your_own_remote|Section 5]] & [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]]. 
#Ask someone else to do the work for you. You can try this by posting a request for help in either:
##The [https://community.sling.com/content Slingbox Answers Forum].
##The [http://www.hifi-remote.com/forums/viewforum.php?f=19 JP1 forum]. 
I can normally install your device on my Harmony Universal Remote to mimic the original Remote and learn the codes for you (unless I am away on holiday). 

=='''Installing the Binary file to the Slingbox.'''==
 I have written a comprehensive Installation Guide at

http://placeshiftingenthusiasts.com/how-to-install-a-custom-remote-onto-the-slingbox/

Once you have completed the setup and the BIN files have been downloaded to the Slingbox they are not used any more and can be deleted.

=='''Learning the IR codes from your own remote.'''==
==='''Requirements'''===
Assuming you have decided to create the Remote Binary File yourself, the first stage is to learn the codes from your original Remote. This is what you need:
====Hardware====
#A computer with a USB port (or you can use older serial ports). 
#A Learning Remote and an appropriate JP Cable. Almost any "One For All" or "Radio Shack" remote that has learning will work for this but examples are: 
::URC-6820 (JP1.2)
::URC-8820 (JP1.2)
::URC-10820 (JP1.2)
::Radio Shack Gamer 15-133 (JP1.3)
::Radios Shack Satelite15-134 (JP1.3) 
:Note that some remotes need a JP1.2 cable and some need a JP1.3 cable (and some older, discontinued remotes such as the URC-9810 use a JP1 cable). Make sure the Cable and Remote match. Again the [http://www.hifi-remote.com/forums/viewforum.php?f=10 JP1 forum] is a mine of information. 
:If you are not sure there is a [http://www.hifi-remote.com/forums/dload.php?action=file&file_id=2981 chart of remotes] where you can look up a specific remote to see which format it uses. If you want to buy a cable try [http://www.diygadget.com/ DIYgadget] for the cheaper serial JP1.2/3 cables.

or An IR learning "widget". I got mine from Tommy Tyler through https://www.tindie.com/products/TommyTyler/ir-widget-infrared-remote-control-signal-recorderanalyzer/ (My preferred solution). 

====Software====
:If you are using a Learning Remote: [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=81 IR.EXE] [http://www.hifi-remote.com/forums/dload.php?action=file&file_id=7201 RDF Files] These are support files for the IR.EXE program. If you are using an IR Widget: [http://www.compendiumarcana.com/irwidget/irscope.zip IRSCOPE.EXE] [http://www.ftdichip.com/Drivers/VCP.htm The drivers] [http://www.hifi-remote.com/forums/dload.php?action=file&file_id=922 The IR decode DLL] Or download [http://rmrsoft.com/remote.zip my full IRSCOPE/REMOTEMASTER package]. Much of the JP1 software needs the java runtime environment (JRE) as well. A lot of computers will already have it installed already, but if you need it you can [http://java.sun/j2se/1.4.2/download.html download] Now we can learn the codes. First we will cover the procedure using a Learning Remote, then cover it using an IR Widget. 

===USING A LEARNING REMOTE===
====Getting the Codes from your Remote====
(These steps are based on using the older URC9810, the procedure will be slightly different for other Remotes so you will need to refer to the manuals.) 
:# Tap one of the buttons on the Learning Remote at the top which applies to the device you wish to create the bin file for. (eg. TV, DVD, Satellite). This is not totally necessary, you can always use TV, as it makes no difference to you, but if you subsequently upload the file for other users, it really ought to be for the correct type of device. 
:# At the bottom there will be a button called 'Set'. Keep your finger pushed on that until the LCD changes so you can modify your remote control. 
:# Click down until you come to an option called 'IR LEARN' and click select. 
:# Click one of the buttons on the remote control. For example, the '1' key, the LCD will say "Learning" and the red light will come on. 
:# Put your remote control in front of the learning remote and click the 1 key - if it is added correctly it should say 'Success'. If it fails (shows “Error”) then try again. There are a lot of different techniques for this procedure, the safest bet seems to be press the button on the Learning Remote, wait for 2 seconds then hold the equivalent key on the original Remote until the red light goes on. If you get a bad „learn‟, try just tapping quickly on the original key. A full description of these options is [http://www.hifi-remote.com/forums/viewtopic.php?t=3943 here]. 
:# Repeat this step for each of the keys you want to learn and have on your Slingbox Remote. If you get the "Memory Full" message then you will have to repeat this operation for the remaining keys after you have uploaded the first set of codes to your PC. 

====Getting the Codes onto your PC.====
 
:#Install IR.EXE onto your PC. It comes as a ZIP file rather than an installation package, which you need to unzip to your PC. The files can actually go anywhere but as a bit of tidy person (geek?) I created a C:\Program Files\IR\ folder and put the files in there and then created a shortcut on the Desktop. Important Note: For Windows VISTA users, I have found that I need to run the program in Windows XP Compatibility Mode to make it recognise the JP1 interface. Just right-click on IR.EXE, select Properties, then the Compatibility Tab and check the appropriate box. 
:#Create a sub folder called \RDF\ in whatever folder you have put the IR program and extract the RDF support files into that folder. 
:#Get your JP1 cable out and turn your remote control over, open the battery compartment and plug the JP1 6 pin connector into the Learning remote (you will see 6 needles where it plugs into). There are 2 ways to plug it in, but don‟t worry, you won‟t cause any damage by plugging it in the wrong way. Try them both if the first one fails. 
:#Plug the USB plug into your computer. As with any external piece of hardware you will need to install the drivers. There are drivers for the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=81 JP1 Remotes] and the [http://www.ftdichip.com/Drivers/VCP.htm JP1.2/3 Remotes]. Personally I use the JP1 ones dated 12 Feb 2008 and they work fine in Windows XP and also in Vista as long as the Windows XP Compatibility flag is set. 
:#Now open IR.exe. If you get told your RDF directory isn't valid, click OK and ignore this for now. It will look something like this: (Note this is a screenshot of V8.0. If that version hasn‟t been released yet, V7.15 looks very similar but does not have the icons at the top. [[Image:IR-general.jpg]] 
:#Go to File > Set Directory > RDF Path >. Select your RDF directory. You need to double click the RDF directory or it won't take. 
:#For peace of mind go to Interface > Check Driver... it should say the interface is connected. If it does then that's fine, if it gives an error message “Unable to open device, check connection” then it is not seeing the JP1 cable so you need to check the cable and the drivers. If it gives the error message “The remote is not acknowledging signals from the interface” then the cable is working fine but it is not seeing the remote. Try reversing the cable connection to the remote and hopefully that will cure the problem. 
:#Now click the "Download From Remote" button. 
:#Then click the "Learned Signals" tab (second from last one). It will look something like this: [[Image:IR-learned1.jpg]] 
:#On the left hand side there should be a list with the device type and the keys - eg "TV: 1". Click on it and details should show up in the right hand side listview. 
:#The first thing we need to make a note of is the Protocol (JVC) in this case, then the Device Number (239 in this case) and if it is displayed, the Sub-Device number. Then for each of the learned keys note down the OBC, Hex Code and EFC numbers. 
:#If you get the "MEM FULL" message on the Remote then Use File > Save As to keep a copy then tap the "Delete All" button, go back to the General Tab and tap the "Upload To remote" button to clear the Remote. Then learn the remaining buttons and follow the same procedure. Once they are all done, use the use the File > Save As command to save a copy of the final results. 
However, if you see a screen like this, it means that the protocol used by your remote is not recognised by the system. That means that you cannot create the Remote yourself but will have to ask the people on the JP1 forum to help you out. They have a much deeper understanding of the IR formats, and can often dig deeper into the signals and figure out the codes. [[Image:IR-learned2.jpg]] 
The procedure to do this is to use the File > Save As menu option to save the IR source file(s) (I tend to ZIP them up if there are more than one). Now upload them to the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=35 Diagnosis Area] in the File Section of the JP1 Forum. 
Check the file has been added, and make a record of it‟s location by right-clicking on it and select „Copy Link Location‟. 
Now create a new topic in the [http://www.hifi-remote.com/forums/viewforum.php?f=20 Protocol Decode Forum] and plead for some help, quoting the device Manufacturer and Model Number and the link to the IR source files. Offer incentives (money, beer, everlasting gratitude….) and you might be lucky. The experts may produce the RemoteMaster source file or even the Remote Binary files themselves. Now you can move on to [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]] for building the Remote BIN files. 

===USING AN IR WIDGET===
If you are using an IR Widget there is an excellent guide [http://freepdfhosting.com/2da0b92e8c.pdf here] on the Tindle site. So I suggest you download that and read it thoroughly. There is no point in repeating it here, but just to emphasise a few points: 
:#You will want to regularly check for updates to the decodeir.dll. As new protocols are recognized, this dll will change. 
:#There is no way to save the learned values for importing into RemoteMaster (where you will make the remote) so you will need to write them down. 
:#Although I tend to put programs into C:\Program Files\.... this can be a bit dodgy in Windows as programs cannot save files to this area because of security limitations. So it might be safer to install it under \Documents\ 
:#The Guide has a very useful section comparing using a Learning Remotes and the IR Widget and highlighting the differences, (For example "Key" is equivalent to "OBC") so you could check out the previous sub-section covering using IR.EXE and the Learning Remote. And then you will understand this section. When complete you can move onto [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]] to create the Binary file. 

=='''Creating your own Binary files using RemoteMaster'''==
:#To make life easier I have packaged a full set of the latest files required and uploaded them to my site. Just download them from [http://www.rmrsoft.com/remote.zip here] and unzip them onto your computer. 
:#Start RemoteMaster.EXE. You may be promoted to highlight the folder the folder that contains the RDF files (Highlight the \RDF\ folder in the folder where you placed Remotemaster). You may also have to do the same for the Images folder. The display will now look something like this:[[Image:RM-setup.jpg]] 
:#If you have obtained an .rmdu file then use the File > Open menu option to load the file. If you have obtained a .bin file then use the Advanced > Import Binary Upgrade to load up the details. If you have not obtained a file then you will have to input the codes manually. 
:#Now to explain the main Setup Tab: '''Description ''': Use anything you like, I tend to use the device name. '''Remote''': Select the one appropriate for your chip. '''Device Type''': Should be set to the correct type of device (as covered in Paragraph 3 of Section 1). '''Setup Code''': This is where you put the 4-digit code. In theory it can be any number between 0000 and 2047, but as explained in Section 1 Paragraph 3, numbers below 2000 may actually be already allocated to specific devices, so to be safe I personally use 2010. Fell free to use your own value. '''Protocol''': From the dropdown list select the Protocol you discovered when you used IR.EXE/IRSCOPE.EXE. '''Device''': Type in the Device code you recorded from IR.EXE/IRSCOPE.EXE. '''Sub-Device''': If applicable type in the Sub-Device code you recorded from IR.EXE/ IRSCOPE.EXE. 
:#Now tap on the Functions Tab [[Image:RM-functions.jpg]] This picture shows the program with an .rmdu file or .bin file already imported; otherwise the code columns will be blank. The entries are fully configurable, so if there are pre-defined functions that you do not need (pip swap, pipmove..) then you highlight them and tap the "Delete" button. If you have a function that is not pre-defined (Audio, Setup…) then tap the "New" button and enter them. Now fill in the codes for each button that you recorded. You just put in the OBC value and press <Enter>, the other 2 values will be generated automatically based on the protocol you selected. Also, if you used a JP1 learning remote, there's a way to cut and paste all the codes which saves needing to enter them all. In IR, if you select File > Summary you get a page listing lots of stuff. If you scroll down, you'll see a list of learn decodes. You can cut and paste this list into Excel, then you can re-arrange the columns and just select the button names and OBC codes to cut and paste into RM. You can move the RM columns, so if the OBC column isn't the one next to the button names, you can move it there. 
:#Now tap on the Buttons Tab [[Image:RM-buttons.jpg]] This is where you map the defined functions onto the available buttons. Simply tap the Auto-Assign button which should allocate most of the buttons. For any buttons left in red drag the function name from the table on the left to the function column on the right. But note that not all these buttons are available on a Slingplayer Generic Remote. For example the 'Slow' and 'Eject' buttons do not exist on a Generic Remote. So only map the functions onto the buttons that actually exist (You will see that when you check out the Layout Tab, and from experience when you have done this a few times). The important ones to note are the Custom 10-29 buttons. These are the ones you use for the functions you need that aren't on the generic remote and they subsequently appear in the drop down menu of the remote as Custom options (except for Custom 22-26 which are pre-allocated to the colour buttons). 
:#Now tap on the Layout Tab. [[Image:RM-layout.jpg]] This shows the generic Slingplayer remote and shows the buttons you can actually use in the Buttons Tab. If a button shows yellow then that means it is in use. If it shows black (the PgUp/PgDn in the picture) then has not been allocated a function. Again you can drag and drop functions onto a button. 
:#Once you have finished experimenting go back to the Setup tab. Select the appropriate Slingbox remote, go to the 'Advanced' menu at the top and select 'Export Binary Upgrade'. This will produce the BIN file that we have discussed in previous Sections. If you aren‟t sure which Slingbox Chip you have then create a BIN file for the main 2 chips, so that would give you something like 
:::C2010_PL.BIN
:::C2010_RV.BIN

So now you can go back to [[#Installing_the_Binary_file_to_the_Slingbox.|Section 4]] and install the new Custom Remote onto your Slingbox. 
====Finding Missing Codes====
You can often find yourself in the position where the Custom Remote generally works OK but some of the functions are missing or some are sending the wrong code. This is relatively easy to fix by trial and error. The OBC codes must lie between 0-255, so the first thing to do is make a list of the OBC codes that are not being used in the Remote Control. Now use Remotemaster to allocate those codes to the 0-9 buttons and the 15 Custom buttons. Now build a new BIN files, replace the one in your \SBAV\ folder and rerun the "Setup Video Sources" routine. Now try those buttons and see if any of them action the missing function. If you find the missing codes then you can update the original remote file. You may have to repeat this operation 10 times to cover all the missing codes, although you can cut down the number of times by also using the Transport buttons (Play/Pause…) and Channel, Page +/- buttons as well. 

=='''Give your Binary file back to the Community'''==
Finally, remember that it is good to payback. If you find a remote file that works for you then upload it to the JP1 Forums. The way to do this is: 
#Put the 4 Binary files and the Remote Master RMDU file into a ZIP file. I also tend to add a Readme file in case users are unsure how to use the files. Although hopefully they will have read this article and will know what to do. 
#To be really helpful, you should upload your files in 3 different places:
##Upload your ZIP file to the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=87 Slingbox Binary Files] area.
##Upload the Remote Master RMDU source file to the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=98 Slingbox RM Files] area.
##Upload the RMDU file to the appropriate area in the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=4 Device Upgrades] area.
 
I hope these instructions have been helpful. If you have any suggestions for changes or improvements please E-mail me at '''alan (at) rmrsoft (dot) com'''

How to Create Custom Remote Controls and use them on your Slingbox

2015-04-13T15:12:41Z

Alanrichey:

Written by: Al Richey 

With acknowledgements to Matt Whitlock, BrandonC, The Robman, Nuke12 and AndyBBB, who actually wrote much of this article. All I did was update and combine all the information into one document. 

=='''Background information'''==
One of the most common posts on the support site is about remote codes for unsupported devices. So if you find yourself in this situation I hope this will help. Before detailing the steps to go through there are some basic things you need to understand (this isn‟t essential reading but everything will make much more sense if you do know the details)
==='''Different UEI Chips'''===
: There were five different chips used in Slingboxes. These are designated as JU, PK, PL, RV & JB. If you want to check your type you can verify your IR blaster version in the Slingbox Properties dialog. Then match the IR version number with the chip type using the chart below.
#JU (VERY old US boxes)
#PL (current US boxes)
#PK (never used)
#RV (old European boxes)
#JB (All modern Slingboxes, but compatible with PL files)

==='''Slingplayer Compatibility'''===
: In older versions of Slingplayer it was possible to change the look of the Custom Remote skin‟. Since Slingplayer V1.5 this functionality has been removed and as far as the look of the Remote is concerned you are stuck with the Generic design produced by Sling Media. All we can do is change the codes that are sent when a specific button is pressed. One drawback of the Generic Remote is that it has only the main buttons, so extra buttons on other remotes (such as Audio/Setup…) can not be mapped directly. What we have to do is put them into a Custom Menu which is accessed by tapping on the Menu button on the Generic Remote or right-clicking on the image.
:

==='''Setup Code Nomenclature'''===
: When you run the Configure Inputs routines in the various Slingplayers and select a supported device, what actually happens is that a Binary Code is downloaded to the Slingbox. 
: This Binary Code details the IR codes that are sent when a specific button is pressed on the remote. Unfortunately the native Slingbox software doesn't use separate binary files that we can edit, their codes are apparently compressed and packaged into special files that we can't do anything with (that I know of). But what we can do instead of editing the built-in codes is to use a separate external upgrade code file. These files have the format such as "C1234_PL.BIN". 
: The first letter of the file describes the type of device, the main ones we are interested in are:
::V which is for VCRs, which encompasses PVRs, DVRs and other recorders
::S which is for Satellite and FTA set top boxes
::C which is for Cable boxes
::Y which is for DVD Players
::R which is for Tuners
:This is followed by a 4-digit code number. For Slingboxes the code numbers can be between 0000-2047 (actually higher in newer Slingboxes but to stay safe we are better staying below 2047). In general, codes below 2000 actually relate to specific boxes, for example V0618 is the code for a TIVO and D0032 is the code for a Pioneer CD Player. But we can feel fairly safe using 2000-2047 for our own codes. The final part of the filename defines the chip for which it will run. 
: So if you were looking for the binary file for a PVR with a code number allocated 1234, designed to run on a PL-equipped Slingbox, you would be searching for a file called V1234_PL.BIN. Note: You must NEVER change the name of the file, as the letter, code number and chip type are also defined inside the file itself.

==='''JP1'''===
:You will hear a lot about "JP1". Basically this is a process whereby people using "One For All‟ (OFA) remote controls can add new codes to their remotes from their PC. The remote control processor inside the Slingbox is made by the same company that makes OFA remotes, so the upgrades are similar. The JP1 tools have been upgraded so that we can now use them to create and modify upgrades for the Slingbox.

=='''The Basic Procedure.'''==
The official procedure to follow is to report the [http://support.slingmedia.com/get/KB-005640.html Lack of a Supported Remote] to SlingMedia and they will add it to the database. In practice, they are not quick at doing this (I have been asking for a remote for over 2 years now), and the updated remote list seems to be only occasionally updated. That may change in the future but for now it is really not a practical quick solution. So for a short term fix what you need to do is to create or acquire the correct Binary code file for your A/V device, and then install it into your Slingbox. This installation process is covered in detail in [[#Installing_the_Binary_file_to_the_Slingbox|Section 4]], so first let‟s see where you can look for these files. 

=='''Obtaining the Binary file for the Custom Remote'''==

#Before starting, make sure in the setup wizard you have tried all the devices by that same manufacturer, even if the model number does not match, and all the associated code numbers. You might be lucky and find one that works and that will save a lot of work. If that doesn‟t solve the problem here is the step by step approach to getting hold of your binary file: 
#Go to the JP1 forum. This has a specific Download area for [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=87 Slingbox Custom Remotes], so go through all those to see if your device has already been done. 
#If it isn‟t there the JP1 forum also has a more general [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=4 File Download Area]. From this page you select the download area for the specific type of device and check there. If you are lucky you will find a source file for using in the program RemoteMaster (RM or KM files), the use of which is discussed in [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]]. 
#Have a look on the Hava forums. They are also using the same chips and the files might be there. Check out this [http://www.myhava.com/forum/viewforum.php?f=17&st=0&sk=t&sd=d&start=0 forum]. You‟re looking for a PK or PL file. They can be imported into Remote Master and then converted to the PK, PL, RV or JU files for the Slingbox. Again this is discussed in [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]]. 
#Find a friend with a Pronto remote. They have a very nice update system and can generate .ccf files that can be used with the tools on the JP1 site to generate the .bin file used by a Slingbox. However, this is not easy, and you will probably need help from the experts on the JP1 forum, but if you want to have a go on your own then you will need the [http://www.hifi-remote.com/forums/dload.php?action=file&file_id=1887 DecodeCCF] program, and [http://www.remotecentral.com/files/index.html .ccf] files. Note that the Pronto can also make .pcf files, but unfortunately we cannot decode those. 
If all of this fails, and you cannot get hold of a BIN file then the Remote will have to be built from scratch. You have 2 options here: 
#Do it yourself by buying a JP1.x learning remote (plus a JP1.x cable), or an IR Widget, and learn the codes needed to control the device. How to do this is covered in [[#Learning_the_IR_codes_from_your_own_remote|Section 5]] & [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]]. 
#Ask someone else to do the work for you. You can try this by posting a request for help in either:
##The [https://community.sling.com/content Slingbox Answers Forum].
##The [http://www.hifi-remote.com/forums/viewforum.php?f=19 JP1 forum]. 
I can normally install your device on my Harmony Universal Remote to mimic the original Remote and learn the codes for you (unless I am away on holiday). 

=='''Installing the Binary file to the Slingbox.'''==
 I have written a comprehensive Installation Guide at

http://placeshiftingenthusiasts.com/how-to-install-a-custom-remote-onto-the-slingbox/

Once you have completed the setup and the BIN files have been downloaded to the Slingbox they are not used any more and can be deleted.

=='''Learning the IR codes from your own remote.'''==
==='''Requirements'''===
Assuming you have decided to create the Remote Binary File yourself, the first stage is to learn the codes from your original Remote. This is what you need:
====Hardware====
#A computer with a USB port (or you can use older serial ports). 
#A Learning Remote and an appropriate JP Cable. Almost any "One For All" or "Radio Shack" remote that has learning will work for this but examples are: 
::URC-6820 (JP1.2)
::URC-8820 (JP1.2)
::URC-10820 (JP1.2)
::Radio Shack Gamer 15-133 (JP1.3)
::Radios Shack Satelite15-134 (JP1.3) 
:Note that some remotes need a JP1.2 cable and some need a JP1.3 cable (and some older, discontinued remotes such as the URC-9810 use a JP1 cable). Make sure the Cable and Remote match. Again the [http://www.hifi-remote.com/forums/viewforum.php?f=10 JP1 forum] is a mine of information. 
:If you are not sure there is a [http://www.hifi-remote.com/forums/dload.php?action=file&file_id=2981 chart of remotes] where you can look up a specific remote to see which format it uses. If you want to buy a cable try [http://www.diygadget.com/ DIYgadget] for the cheaper serial JP1.2/3 cables.

or An IR learning "widget". I got mine from Tommy Tyler through https://www.tindie.com/products/TommyTyler/ir-widget-infrared-remote-control-signal-recorderanalyzer/ (My preferred solution). 

====Software====
:If you are using a Learning Remote: [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=81 IR.EXE] [http://www.hifi-remote.com/forums/dload.php?action=file&file_id=7201 RDF Files] These are support files for the IR.EXE program. If you are using an IR Widget: [http://www.compendiumarcana.com/irwidget/irscope.zip IRSCOPE.EXE] [http://www.ftdichip.com/Drivers/VCP.htm The drivers] [http://www.hifi-remote.com/forums/dload.php?action=file&file_id=922 The IR decode DLL] Or download [http://rmrsoft.com/remote.zip my full IRSCOPE/REMOTEMASTER package]. Much of the JP1 software needs the java runtime environment (JRE) as well. A lot of computers will already have it installed already, but if you need it you can [http://java.sun/j2se/1.4.2/download.html download] Now we can learn the codes. First we will cover the procedure using a Learning Remote, then cover it using an IR Widget. 

===USING A LEARNING REMOTE===
====Getting the Codes from your Remote====
(These steps are based on using the older URC9810, the procedure will be slightly different for other Remotes so you will need to refer to the manuals.) 
:# Tap one of the buttons on the Learning Remote at the top which applies to the device you wish to create the bin file for. (eg. TV, DVD, Satellite). This is not totally necessary, you can always use TV, as it makes no difference to you, but if you subsequently upload the file for other users, it really ought to be for the correct type of device. 
:# At the bottom there will be a button called 'Set'. Keep your finger pushed on that until the LCD changes so you can modify your remote control. 
:# Click down until you come to an option called 'IR LEARN' and click select. 
:# Click one of the buttons on the remote control. For example, the '1' key, the LCD will say "Learning" and the red light will come on. 
:# Put your remote control in front of the learning remote and click the 1 key - if it is added correctly it should say 'Success'. If it fails (shows “Error”) then try again. There are a lot of different techniques for this procedure, the safest bet seems to be press the button on the Learning Remote, wait for 2 seconds then hold the equivalent key on the original Remote until the red light goes on. If you get a bad „learn‟, try just tapping quickly on the original key. A full description of these options is [http://www.hifi-remote.com/forums/viewtopic.php?t=3943 here]. 
:# Repeat this step for each of the keys you want to learn and have on your Slingbox Remote. If you get the "Memory Full" message then you will have to repeat this operation for the remaining keys after you have uploaded the first set of codes to your PC. 

====Getting the Codes onto your PC.====
 
:#Install IR.EXE onto your PC. It comes as a ZIP file rather than an installation package, which you need to unzip to your PC. The files can actually go anywhere but as a bit of tidy person (geek?) I created a C:\Program Files\IR\ folder and put the files in there and then created a shortcut on the Desktop. Important Note: For Windows VISTA users, I have found that I need to run the program in Windows XP Compatibility Mode to make it recognise the JP1 interface. Just right-click on IR.EXE, select Properties, then the Compatibility Tab and check the appropriate box. 
:#Create a sub folder called \RDF\ in whatever folder you have put the IR program and extract the RDF support files into that folder. 
:#Get your JP1 cable out and turn your remote control over, open the battery compartment and plug the JP1 6 pin connector into the Learning remote (you will see 6 needles where it plugs into). There are 2 ways to plug it in, but don‟t worry, you won‟t cause any damage by plugging it in the wrong way. Try them both if the first one fails. 
:#Plug the USB plug into your computer. As with any external piece of hardware you will need to install the drivers. There are drivers for the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=81 JP1 Remotes] and the [http://www.ftdichip.com/Drivers/VCP.htm JP1.2/3 Remotes]. Personally I use the JP1 ones dated 12 Feb 2008 and they work fine in Windows XP and also in Vista as long as the Windows XP Compatibility flag is set. 
:#Now open IR.exe. If you get told your RDF directory isn't valid, click OK and ignore this for now. It will look something like this: (Note this is a screenshot of V8.0. If that version hasn‟t been released yet, V7.15 looks very similar but does not have the icons at the top. [[Image:IR-general.jpg]] 
:#Go to File > Set Directory > RDF Path >. Select your RDF directory. You need to double click the RDF directory or it won't take. 
:#For peace of mind go to Interface > Check Driver... it should say the interface is connected. If it does then that's fine, if it gives an error message “Unable to open device, check connection” then it is not seeing the JP1 cable so you need to check the cable and the drivers. If it gives the error message “The remote is not acknowledging signals from the interface” then the cable is working fine but it is not seeing the remote. Try reversing the cable connection to the remote and hopefully that will cure the problem. 
:#Now click the "Download From Remote" button. 
:#Then click the "Learned Signals" tab (second from last one). It will look something like this: [[Image:IR-learned1.jpg]] 
:#On the left hand side there should be a list with the device type and the keys - eg "TV: 1". Click on it and details should show up in the right hand side listview. 
:#The first thing we need to make a note of is the Protocol (JVC) in this case, then the Device Number (239 in this case) and if it is displayed, the Sub-Device number. Then for each of the learned keys note down the OBC, Hex Code and EFC numbers. 
:#If you get the "MEM FULL" message on the Remote then Use File > Save As to keep a copy then tap the "Delete All" button, go back to the General Tab and tap the "Upload To remote" button to clear the Remote. Then learn the remaining buttons and follow the same procedure. Once they are all done, use the use the File > Save As command to save a copy of the final results. 
However, if you see a screen like this, it means that the protocol used by your remote is not recognised by the system. That means that you cannot create the Remote yourself but will have to ask the people on the JP1 forum to help you out. They have a much deeper understanding of the IR formats, and can often dig deeper into the signals and figure out the codes. [[Image:IR-learned2.jpg]] 
The procedure to do this is to use the File > Save As menu option to save the IR source file(s) (I tend to ZIP them up if there are more than one). Now upload them to the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=35 Diagnosis Area] in the File Section of the JP1 Forum. 
Check the file has been added, and make a record of it‟s location by right-clicking on it and select „Copy Link Location‟. 
Now create a new topic in the [http://www.hifi-remote.com/forums/viewforum.php?f=20 Protocol Decode Forum] and plead for some help, quoting the device Manufacturer and Model Number and the link to the IR source files. Offer incentives (money, beer, everlasting gratitude….) and you might be lucky. The experts may produce the RemoteMaster source file or even the Remote Binary files themselves. Now you can move on to [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]] for building the Remote BIN files. 

===USING AN IR WIDGET===
If you are using an IR Widget there is an excellent guide [http://freepdfhosting.com/2da0b92e8c.pdf here] on the Tindle site. So I suggest you download that and read it thoroughly. There is no point in repeating it here, but just to emphasise a few points: 
:#You will want to regularly check for updates to the decodeir.dll. As new protocols are recognized, this dll will change. 
:#There is no way to save the learned values for importing into RemoteMaster (where you will make the remote) so you will need to write them down. 
:#Although I tend to put programs into C:\Program Files\.... this can be a bit dodgy in Windows as programs cannot save files to this area because of security limitations. So it might be safer to install it under \Documents\ 
:#The Guide has a very useful section comparing using a Learning Remotes and the IR Widget and highlighting the differences, (For example "Key" is equivalent to "OBC") so you could check out the previous sub-section covering using IR.EXE and the Learning Remote. And then you will understand this section. When complete you can move onto [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]] to create the Binary file. 

=='''Creating your own Binary files using RemoteMaster'''==
:#To make life easier I have packaged a full set of the latest files required and uploaded them to my site. Just download them from [http://www.rmrsoft.com/remote.zip here] and unzip them onto your computer. 
:#Start RemoteMaster.EXE. You may be promoted to highlight the folder the folder that contains the RDF files (Highlight the \RDF\ folder in the folder where you placed Remotemaster). You may also have to do the same for the Images folder. The display will now look something like this:[[Image:RM-setup.jpg]] 
:#If you have obtained an .rmdu file then use the File > Open menu option to load the file. If you have obtained a .bin file then use the Advanced > Import Binary Upgrade to load up the details. If you have not obtained a file then you will have to input the codes manually. 
:#Now to explain the main Setup Tab: '''Description ''': Use anything you like, I tend to use the device name. '''Remote''': Select the one appropriate for your chip. '''Device Type''': Should be set to the correct type of device (as covered in Paragraph 3 of Section 1). '''Setup Code''': This is where you put the 4-digit code. In theory it can be any number between 0000 and 2047, but as explained in Section 1 Paragraph 3, numbers below 2000 may actually be already allocated to specific devices, so to be safe I personally use 2010. Fell free to use your own value. '''Protocol''': From the dropdown list select the Protocol you discovered when you used IR.EXE/IRSCOPE.EXE. '''Device''': Type in the Device code you recorded from IR.EXE/IRSCOPE.EXE. '''Sub-Device''': If applicable type in the Sub-Device code you recorded from IR.EXE/ IRSCOPE.EXE. 
:#Now tap on the Functions Tab [[Image:RM-functions.jpg]] This picture shows the program with an .rmdu file or .bin file already imported; otherwise the code columns will be blank. The entries are fully configurable, so if there are pre-defined functions that you do not need (pip swap, pipmove..) then you highlight them and tap the "Delete" button. If you have a function that is not pre-defined (Audio, Setup…) then tap the "New" button and enter them. Now fill in the codes for each button that you recorded. You just put in the OBC value and press <Enter>, the other 2 values will be generated automatically based on the protocol you selected. Also, if you used a JP1 learning remote, there's a way to cut and paste all the codes which saves needing to enter them all. In IR, if you select File > Summary you get a page listing lots of stuff. If you scroll down, you'll see a list of learn decodes. You can cut and paste this list into Excel, then you can re-arrange the columns and just select the button names and OBC codes to cut and paste into RM. You can move the RM columns, so if the OBC column isn't the one next to the button names, you can move it there. 
:#Now tap on the Buttons Tab [[Image:RM-buttons.jpg]] This is where you map the defined functions onto the available buttons. Simply tap the Auto-Assign button which should allocate most of the buttons. For any buttons left in red drag the function name from the table on the left to the function column on the right. But note that not all these buttons are available on a Slingplayer Generic Remote. For example the 'Slow' and 'Eject' buttons do not exist on a Generic Remote. So only map the functions onto the buttons that actually exist (You will see that when you check out the Layout Tab, and from experience when you have done this a few times). The important ones to note are the Custom 10-29 buttons. These are the ones you use for the functions you need that aren't on the generic remote and they subsequently appear in the drop down menu of the remote as Custom options (except for Custom 22-26 which are pre-allocated to the colour buttons). 
:#Now tap on the Layout Tab. [[Image:RM-layout.jpg]] This shows the generic Slingplayer remote and shows the buttons you can actually use in the Buttons Tab. If a button shows yellow then that means it is in use. If it shows black (the PgUp/PgDn in the picture) then has not been allocated a function. Again you can drag and drop functions onto a button. 
:#Once you have finished experimenting go back to the Setup tab. Select the appropriate Slingbox remote, go to the 'Advanced' menu at the top and select 'Export Binary Upgrade'. This will produce the BIN file that we have discussed in previous Sections. If you aren‟t sure which Slingbox Chip you have then create a BIN file for the main 2 chips, so that would give you something like 
:::C2010_PL.BIN
:::C2010_RV.BIN

So now you can go back to [[#Installing_the_Binary_file_to_the_Slingbox.|Section 4]] and install the new Custom Remote onto your Slingbox. 
====Finding Missing Codes====
You can often find yourself in the position where the Custom Remote generally works OK but some of the functions are missing or some are sending the wrong code. This is relatively easy to fix by trial and error. The OBC codes must lie between 0-255, so the first thing to do is make a list of the OBC codes that are not being used in the Remote Control. Now use Remotemaster to allocate those codes to the 0-9 buttons and the 15 Custom buttons. Now build a new BIN files, replace the one in your \SBAV\ folder and rerun the "Setup Video Sources" routine. Now try those buttons and see if any of them action the missing function. If you find the missing codes then you can update the original remote file. You may have to repeat this operation 10 times to cover all the missing codes, although you can cut down the number of times by also using the Transport buttons (Play/Pause…) and Channel, Page +/- buttons as well. 

=='''Give your Binary file back to the Community'''==
Finally, remember that it is good to payback. If you find a remote file that works for you then upload it to the JP1 Forums. The way to do this is: 
#Put the 4 Binary files and the Remote Master RMDU file into a ZIP file. I also tend to add a Readme file in case users are unsure how to use the files. Although hopefully they will have read this article and will know what to do. 
#To be really helpful, you should upload your files in 3 different places:
##Upload your ZIP file to the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=87 Slingbox Binary Files] area.
##Upload the Remote Master RMDU source file to the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=98 Slingbox RM Files] area.
##Upload the RMDU file to the appropriate area in the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=4 Device Upgrades] area.
 
I hope these instructions have been helpful. If you have any suggestions for changes or improvements please E-mail me at [mailto:alan@rmrsoft alan@rmrsoft].com.

How to Create Custom Remote Controls and use them on your Slingbox

2015-03-11T13:02:04Z

Alanrichey: /* Hardware */

Written by: Al Richey 

With acknowledgements to Matt Whitlock, BrandonC, The Robman, Nuke12 and AndyBBB, who actually wrote much of this article. All I did was update and combine all the information into one document. 

=='''Background information'''==
One of the most common posts on the support site is about remote codes for unsupported devices. So if you find yourself in this situation I hope this will help. Before detailing the steps to go through there are some basic things you need to understand (this isn‟t essential reading but everything will make much more sense if you do know the details)
==='''Different UEI Chips'''===
: There were five different chips used in Slingboxes. These are designated as JU, PK, PL, RV & JB. If you want to check your type you can verify your IR blaster version in the Slingbox Properties dialog. Then match the IR version number with the chip type using the chart below.
#JU (VERY old US boxes)
#PL (current US boxes)
#PK (never used)
#RV (old European boxes)
#JB (All modern Slingboxes, but compatible with PL files)

==='''Slingplayer Compatibility'''===
: In older versions of Slingplayer it was possible to change the look of the Custom Remote skin‟. Since Slingplayer V1.5 this functionality has been removed and as far as the look of the Remote is concerned you are stuck with the Generic design produced by Sling Media. All we can do is change the codes that are sent when a specific button is pressed. One drawback of the Generic Remote is that it has only the main buttons, so extra buttons on other remotes (such as Audio/Setup…) can not be mapped directly. What we have to do is put them into a Custom Menu which is accessed by tapping on the Menu button on the Generic Remote or right-clicking on the image.
:

==='''Setup Code Nomenclature'''===
: When you run the Configure Inputs routines in the various Slingplayers and select a supported device, what actually happens is that a Binary Code is downloaded to the Slingbox. 
: This Binary Code details the IR codes that are sent when a specific button is pressed on the remote. Unfortunately the native Slingbox software doesn't use separate binary files that we can edit, their codes are apparently compressed and packaged into special files that we can't do anything with (that I know of). But what we can do instead of editing the built-in codes is to use a separate external upgrade code file. These files have the format such as "C1234_PL.BIN". 
: The first letter of the file describes the type of device, the main ones we are interested in are:
::V which is for VCRs, which encompasses PVRs, DVRs and other recorders
::S which is for Satellite and FTA set top boxes
::C which is for Cable boxes
::Y which is for DVD Players
::R which is for Tuners
:This is followed by a 4-digit code number. For Slingboxes the code numbers can be between 0000-2047 (actually higher in newer Slingboxes but to stay safe we are better staying below 2047). In general, codes below 2000 actually relate to specific boxes, for example V0618 is the code for a TIVO and D0032 is the code for a Pioneer CD Player. But we can feel fairly safe using 2000-2047 for our own codes. The final part of the filename defines the chip for which it will run. 
: So if you were looking for the binary file for a PVR with a code number allocated 1234, designed to run on a PL-equipped Slingbox, you would be searching for a file called V1234_PL.BIN. Note: You must NEVER change the name of the file, as the letter, code number and chip type are also defined inside the file itself.

==='''JP1'''===
:You will hear a lot about "JP1". Basically this is a process whereby people using "One For All‟ (OFA) remote controls can add new codes to their remotes from their PC. The remote control processor inside the Slingbox is made by the same company that makes OFA remotes, so the upgrades are similar. The JP1 tools have been upgraded so that we can now use them to create and modify upgrades for the Slingbox.

=='''The Basic Procedure.'''==
The official procedure to follow is to report the [http://support.slingmedia.com/get/KB-005640.html Lack of a Supported Remote] to SlingMedia and they will add it to the database. In practice, they are not quick at doing this (I have been asking for a remote for over 2 years now), and the updated remote list seems to be only occasionally updated. That may change in the future but for now it is really not a practical quick solution. So for a short term fix what you need to do is to create or acquire the correct Binary code file for your A/V device, and then install it into your Slingbox. This installation process is covered in detail in [[#Installing_the_Binary_file_to_the_Slingbox|Section 4]], so first let‟s see where you can look for these files. 

=='''Obtaining the Binary file for the Custom Remote'''==

#Before starting, make sure in the setup wizard you have tried all the devices by that same manufacturer, even if the model number does not match, and all the associated code numbers. You might be lucky and find one that works and that will save a lot of work. If that doesn‟t solve the problem here is the step by step approach to getting hold of your binary file: 
#Go to the JP1 forum. This has a specific Download area for [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=87 Slingbox Custom Remotes], so go through all those to see if your device has already been done. 
#If it isn‟t there the JP1 forum also has a more general [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=4 File Download Area]. From this page you select the download area for the specific type of device and check there. If you are lucky you will find a source file for using in the program RemoteMaster (RM or KM files), the use of which is discussed in [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]]. 
#Have a look on the Hava forums. They are also using the same chips and the files might be there. Check out this [http://www.myhava.com/forum/viewforum.php?f=17&st=0&sk=t&sd=d&start=0 forum]. You‟re looking for a PK or PL file. They can be imported into Remote Master and then converted to the PK, PL, RV or JU files for the Slingbox. Again this is discussed in [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]]. 
#Find a friend with a Pronto remote. They have a very nice update system and can generate .ccf files that can be used with the tools on the JP1 site to generate the .bin file used by a Slingbox. However, this is not easy, and you will probably need help from the experts on the JP1 forum, but if you want to have a go on your own then you will need the [http://www.hifi-remote.com/forums/dload.php?action=file&file_id=1887 DecodeCCF] program, and [http://www.remotecentral.com/files/index.html .ccf] files. Note that the Pronto can also make .pcf files, but unfortunately we cannot decode those. 
If all of this fails, and you cannot get hold of a BIN file then the Remote will have to be built from scratch. You have 2 options here: 
#Do it yourself by buying a JP1.x learning remote (plus a JP1.x cable), or an IR Widget, and learn the codes needed to control the device. How to do this is covered in [[#Learning_the_IR_codes_from_your_own_remote|Section 5]] & [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]]. 
#Ask someone else to do the work for you. You can try this by posting a request for help in either:
##The [https://community.sling.com/content Slingbox Answers Forum].
##The [http://www.hifi-remote.com/forums/viewforum.php?f=19 JP1 forum]. 
I can normally install your device on my Harmony Universal Remote to mimic the original Remote and learn the codes for you (unless I am away on holiday). 

=='''Installing the Binary file to the Slingbox.'''==
 I have written a comprehensive Installation Guide at

http://placeshiftingenthusiasts.com/how-to-install-a-custom-remote-onto-the-slingbox/

Once you have completed the setup and the BIN files have been downloaded to the Slingbox they are not used any more and can be deleted.

=='''Learning the IR codes from your own remote.'''==
==='''Requirements'''===
Assuming you have decided to create the Remote Binary File yourself, the first stage is to learn the codes from your original Remote. This is what you need:
====Hardware====
#A computer with a USB port (or you can use older serial ports). 
#A Learning Remote and an appropriate JP Cable. Almost any "One For All" or "Radio Shack" remote that has learning will work for this but examples are: 
::URC-6820 (JP1.2)
::URC-8820 (JP1.2)
::URC-10820 (JP1.2)
::Radio Shack Gamer 15-133 (JP1.3)
::Radios Shack Satelite15-134 (JP1.3) 
:Note that some remotes need a JP1.2 cable and some need a JP1.3 cable (and some older, discontinued remotes such as the URC-9810 use a JP1 cable). Make sure the Cable and Remote match. Again the [http://www.hifi-remote.com/forums/viewforum.php?f=10 JP1 forum] is a mine of information. 
:If you are not sure there is a [http://www.hifi-remote.com/forums/dload.php?action=file&file_id=2981 chart of remotes] where you can look up a specific remote to see which format it uses. If you want to buy a cable try [http://www.diygadget.com/ DIYgadget] for the cheaper serial JP1.2/3 cables.

or An IR learning "widget". I got mine from Tommy Tyler through https://www.tindie.com/products/TommyTyler/ir-widget-infrared-remote-control-signal-recorderanalyzer/ (My preferred solution). 

====Software====
:If you are using a Learning Remote: [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=81 IR.EXE] [http://www.hifi-remote.com/forums/dload.php?action=file&file_id=7201 RDF Files] These are support files for the IR.EXE program. If you are using an IR Widget: [http://www.compendiumarcana.com/irwidget/irscope.zip IRSCOPE.EXE] [http://www.ftdichip.com/Drivers/VCP.htm The drivers] [http://www.hifi-remote.com/forums/dload.php?action=file&file_id=922 The IR decode DLL] Or download [http://rmrsoft.com/remote.zip my full IRSCOPE/REMOTEMASTER package]. Much of the JP1 software needs the java runtime environment (JRE) as well. A lot of computers will already have it installed already, but if you need it you can [http://java.sun/j2se/1.4.2/download.html download] Now we can learn the codes. First we will cover the procedure using a Learning Remote, then cover it using an IR Widget. 

===USING A LEARNING REMOTE===
====Getting the Codes from your Remote====
(These steps are based on using the older URC9810, the procedure will be slightly different for other Remotes so you will need to refer to the manuals.) 
:# Tap one of the buttons on the Learning Remote at the top which applies to the device you wish to create the bin file for. (eg. TV, DVD, Satellite). This is not totally necessary, you can always use TV, as it makes no difference to you, but if you subsequently upload the file for other users, it really ought to be for the correct type of device. 
:# At the bottom there will be a button called 'Set'. Keep your finger pushed on that until the LCD changes so you can modify your remote control. 
:# Click down until you come to an option called 'IR LEARN' and click select. 
:# Click one of the buttons on the remote control. For example, the '1' key, the LCD will say "Learning" and the red light will come on. 
:# Put your remote control in front of the learning remote and click the 1 key - if it is added correctly it should say 'Success'. If it fails (shows “Error”) then try again. There are a lot of different techniques for this procedure, the safest bet seems to be press the button on the Learning Remote, wait for 2 seconds then hold the equivalent key on the original Remote until the red light goes on. If you get a bad „learn‟, try just tapping quickly on the original key. A full description of these options is [http://www.hifi-remote.com/forums/viewtopic.php?t=3943 here]. 
:# Repeat this step for each of the keys you want to learn and have on your Slingbox Remote. If you get the "Memory Full" message then you will have to repeat this operation for the remaining keys after you have uploaded the first set of codes to your PC. 

====Getting the Codes onto your PC.====
 
:#Install IR.EXE onto your PC. It comes as a ZIP file rather than an installation package, which you need to unzip to your PC. The files can actually go anywhere but as a bit of tidy person (geek?) I created a C:\Program Files\IR\ folder and put the files in there and then created a shortcut on the Desktop. Important Note: For Windows VISTA users, I have found that I need to run the program in Windows XP Compatibility Mode to make it recognise the JP1 interface. Just right-click on IR.EXE, select Properties, then the Compatibility Tab and check the appropriate box. 
:#Create a sub folder called \RDF\ in whatever folder you have put the IR program and extract the RDF support files into that folder. 
:#Get your JP1 cable out and turn your remote control over, open the battery compartment and plug the JP1 6 pin connector into the Learning remote (you will see 6 needles where it plugs into). There are 2 ways to plug it in, but don‟t worry, you won‟t cause any damage by plugging it in the wrong way. Try them both if the first one fails. 
:#Plug the USB plug into your computer. As with any external piece of hardware you will need to install the drivers. There are drivers for the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=81 JP1 Remotes] and the [http://www.ftdichip.com/Drivers/VCP.htm JP1.2/3 Remotes]. Personally I use the JP1 ones dated 12 Feb 2008 and they work fine in Windows XP and also in Vista as long as the Windows XP Compatibility flag is set. 
:#Now open IR.exe. If you get told your RDF directory isn't valid, click OK and ignore this for now. It will look something like this: (Note this is a screenshot of V8.0. If that version hasn‟t been released yet, V7.15 looks very similar but does not have the icons at the top. [[Image:IR-general.jpg]] 
:#Go to File > Set Directory > RDF Path >. Select your RDF directory. You need to double click the RDF directory or it won't take. 
:#For peace of mind go to Interface > Check Driver... it should say the interface is connected. If it does then that's fine, if it gives an error message “Unable to open device, check connection” then it is not seeing the JP1 cable so you need to check the cable and the drivers. If it gives the error message “The remote is not acknowledging signals from the interface” then the cable is working fine but it is not seeing the remote. Try reversing the cable connection to the remote and hopefully that will cure the problem. 
:#Now click the "Download From Remote" button. 
:#Then click the "Learned Signals" tab (second from last one). It will look something like this: [[Image:IR-learned1.jpg]] 
:#On the left hand side there should be a list with the device type and the keys - eg "TV: 1". Click on it and details should show up in the right hand side listview. 
:#The first thing we need to make a note of is the Protocol (JVC) in this case, then the Device Number (239 in this case) and if it is displayed, the Sub-Device number. Then for each of the learned keys note down the OBC, Hex Code and EFC numbers. 
:#If you get the "MEM FULL" message on the Remote then Use File > Save As to keep a copy then tap the "Delete All" button, go back to the General Tab and tap the "Upload To remote" button to clear the Remote. Then learn the remaining buttons and follow the same procedure. Once they are all done, use the use the File > Save As command to save a copy of the final results. 
However, if you see a screen like this, it means that the protocol used by your remote is not recognised by the system. That means that you cannot create the Remote yourself but will have to ask the people on the JP1 forum to help you out. They have a much deeper understanding of the IR formats, and can often dig deeper into the signals and figure out the codes. [[Image:IR-learned2.jpg]] 
The procedure to do this is to use the File > Save As menu option to save the IR source file(s) (I tend to ZIP them up if there are more than one). Now upload them to the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=35 Diagnosis Area] in the File Section of the JP1 Forum. 
Check the file has been added, and make a record of it‟s location by right-clicking on it and select „Copy Link Location‟. 
Now create a new topic in the [http://www.hifi-remote.com/forums/viewforum.php?f=20 Protocol Decode Forum] and plead for some help, quoting the device Manufacturer and Model Number and the link to the IR source files. Offer incentives (money, beer, everlasting gratitude….) and you might be lucky. The experts may produce the RemoteMaster source file or even the Remote Binary files themselves. Now you can move on to [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]] for building the Remote BIN files. 

===USING AN IR WIDGET===
If you are using an IR Widget there is an excellent guide [http://www.txsat.net/IR%20Widget%20Rev%2014%20Final.pdf here] on the TXSat site. So I suggest you download that and read it thoroughly. There is no point in repeating it here, but just to emphasise a few points: 
:#You will want to regularly check for updates to the decodeir.dll. As new protocols are recognized, this dll will change. 
:#There is no way to save the learned values for importing into RemoteMaster (where you will make the remote) so you will need to write them down. 
:#Although I tend to put programs into C:\Program Files\.... this can be a bit dodgy in Windows as programs cannot save files to this area because of security limitations. So it might be safer to install it under \Documents\ 
:#The Guide has a very useful section comparing using a Learning Remotes and the IR Widget and highlighting the differences, (For example "Key" is equivalent to "OBC") so you could check out the previous sub-section covering using IR.EXE and the Learning Remote. And then you will understand this section. When complete you can move onto [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]] to create the Binary file. 

=='''Creating your own Binary files using RemoteMaster'''==
:#To make life easier I have packaged a full set of the latest files required and uploaded them to my site. Just download them from [http://www.rmrsoft.com/remote.zip here] and unzip them onto your computer. 
:#Start RemoteMaster.EXE. You may be promoted to highlight the folder the folder that contains the RDF files (Highlight the \RDF\ folder in the folder where you placed Remotemaster). You may also have to do the same for the Images folder. The display will now look something like this:[[Image:RM-setup.jpg]] 
:#If you have obtained an .rmdu file then use the File > Open menu option to load the file. If you have obtained a .bin file then use the Advanced > Import Binary Upgrade to load up the details. If you have not obtained a file then you will have to input the codes manually. 
:#Now to explain the main Setup Tab: '''Description ''': Use anything you like, I tend to use the device name. '''Remote''': Select the one appropriate for your chip. '''Device Type''': Should be set to the correct type of device (as covered in Paragraph 3 of Section 1). '''Setup Code''': This is where you put the 4-digit code. In theory it can be any number between 0000 and 2047, but as explained in Section 1 Paragraph 3, numbers below 2000 may actually be already allocated to specific devices, so to be safe I personally use 2010. Fell free to use your own value. '''Protocol''': From the dropdown list select the Protocol you discovered when you used IR.EXE/IRSCOPE.EXE. '''Device''': Type in the Device code you recorded from IR.EXE/IRSCOPE.EXE. '''Sub-Device''': If applicable type in the Sub-Device code you recorded from IR.EXE/ IRSCOPE.EXE. 
:#Now tap on the Functions Tab [[Image:RM-functions.jpg]] This picture shows the program with an .rmdu file or .bin file already imported; otherwise the code columns will be blank. The entries are fully configurable, so if there are pre-defined functions that you do not need (pip swap, pipmove..) then you highlight them and tap the "Delete" button. If you have a function that is not pre-defined (Audio, Setup…) then tap the "New" button and enter them. Now fill in the codes for each button that you recorded. You just put in the OBC value and press <Enter>, the other 2 values will be generated automatically based on the protocol you selected. Also, if you used a JP1 learning remote, there's a way to cut and paste all the codes which saves needing to enter them all. In IR, if you select File > Summary you get a page listing lots of stuff. If you scroll down, you'll see a list of learn decodes. You can cut and paste this list into Excel, then you can re-arrange the columns and just select the button names and OBC codes to cut and paste into RM. You can move the RM columns, so if the OBC column isn't the one next to the button names, you can move it there. 
:#Now tap on the Buttons Tab [[Image:RM-buttons.jpg]] This is where you map the defined functions onto the available buttons. Simply tap the Auto-Assign button which should allocate most of the buttons. For any buttons left in red drag the function name from the table on the left to the function column on the right. But note that not all these buttons are available on a Slingplayer Generic Remote. For example the 'Slow' and 'Eject' buttons do not exist on a Generic Remote. So only map the functions onto the buttons that actually exist (You will see that when you check out the Layout Tab, and from experience when you have done this a few times). The important ones to note are the Custom 10-29 buttons. These are the ones you use for the functions you need that aren't on the generic remote and they subsequently appear in the drop down menu of the remote as Custom options (except for Custom 22-26 which are pre-allocated to the colour buttons). 
:#Now tap on the Layout Tab. [[Image:RM-layout.jpg]] This shows the generic Slingplayer remote and shows the buttons you can actually use in the Buttons Tab. If a button shows yellow then that means it is in use. If it shows black (the PgUp/PgDn in the picture) then has not been allocated a function. Again you can drag and drop functions onto a button. 
:#Once you have finished experimenting go back to the Setup tab. Select the appropriate Slingbox remote, go to the 'Advanced' menu at the top and select 'Export Binary Upgrade'. This will produce the BIN file that we have discussed in previous Sections. If you aren‟t sure which Slingbox Chip you have then create a BIN file for the main 2 chips, so that would give you something like 
:::C2010_PL.BIN
:::C2010_RV.BIN

So now you can go back to [[#Installing_the_Binary_file_to_the_Slingbox.|Section 4]] and install the new Custom Remote onto your Slingbox. 
====Finding Missing Codes====
You can often find yourself in the position where the Custom Remote generally works OK but some of the functions are missing or some are sending the wrong code. This is relatively easy to fix by trial and error. The OBC codes must lie between 0-255, so the first thing to do is make a list of the OBC codes that are not being used in the Remote Control. Now use Remotemaster to allocate those codes to the 0-9 buttons and the 15 Custom buttons. Now build a new BIN files, replace the one in your \SBAV\ folder and rerun the "Setup Video Sources" routine. Now try those buttons and see if any of them action the missing function. If you find the missing codes then you can update the original remote file. You may have to repeat this operation 10 times to cover all the missing codes, although you can cut down the number of times by also using the Transport buttons (Play/Pause…) and Channel, Page +/- buttons as well. 

=='''Give your Binary file back to the Community'''==
Finally, remember that it is good to payback. If you find a remote file that works for you then upload it to the JP1 Forums. The way to do this is: 
#Put the 4 Binary files and the Remote Master RMDU file into a ZIP file. I also tend to add a Readme file in case users are unsure how to use the files. Although hopefully they will have read this article and will know what to do. 
#To be really helpful, you should upload your files in 3 different places:
##Upload your ZIP file to the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=87 Slingbox Binary Files] area.
##Upload the Remote Master RMDU source file to the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=98 Slingbox RM Files] area.
##Upload the RMDU file to the appropriate area in the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=4 Device Upgrades] area.
 
I hope these instructions have been helpful. If you have any suggestions for changes or improvements please E-mail me at [mailto:alan@rmrsoft alan@rmrsoft].com.

How to Create Custom Remote Controls and use them on your Slingbox

2014-11-12T10:46:24Z

Alanrichey:

Written by: Al Richey 

With acknowledgements to Matt Whitlock, BrandonC, The Robman, Nuke12 and AndyBBB, who actually wrote much of this article. All I did was update and combine all the information into one document. 

=='''Background information'''==
One of the most common posts on the support site is about remote codes for unsupported devices. So if you find yourself in this situation I hope this will help. Before detailing the steps to go through there are some basic things you need to understand (this isn‟t essential reading but everything will make much more sense if you do know the details)
==='''Different UEI Chips'''===
: There were five different chips used in Slingboxes. These are designated as JU, PK, PL, RV & JB. If you want to check your type you can verify your IR blaster version in the Slingbox Properties dialog. Then match the IR version number with the chip type using the chart below.
#JU (VERY old US boxes)
#PL (current US boxes)
#PK (never used)
#RV (old European boxes)
#JB (All modern Slingboxes, but compatible with PL files)

==='''Slingplayer Compatibility'''===
: In older versions of Slingplayer it was possible to change the look of the Custom Remote skin‟. Since Slingplayer V1.5 this functionality has been removed and as far as the look of the Remote is concerned you are stuck with the Generic design produced by Sling Media. All we can do is change the codes that are sent when a specific button is pressed. One drawback of the Generic Remote is that it has only the main buttons, so extra buttons on other remotes (such as Audio/Setup…) can not be mapped directly. What we have to do is put them into a Custom Menu which is accessed by tapping on the Menu button on the Generic Remote or right-clicking on the image.
:

==='''Setup Code Nomenclature'''===
: When you run the Configure Inputs routines in the various Slingplayers and select a supported device, what actually happens is that a Binary Code is downloaded to the Slingbox. 
: This Binary Code details the IR codes that are sent when a specific button is pressed on the remote. Unfortunately the native Slingbox software doesn't use separate binary files that we can edit, their codes are apparently compressed and packaged into special files that we can't do anything with (that I know of). But what we can do instead of editing the built-in codes is to use a separate external upgrade code file. These files have the format such as "C1234_PL.BIN". 
: The first letter of the file describes the type of device, the main ones we are interested in are:
::V which is for VCRs, which encompasses PVRs, DVRs and other recorders
::S which is for Satellite and FTA set top boxes
::C which is for Cable boxes
::Y which is for DVD Players
::R which is for Tuners
:This is followed by a 4-digit code number. For Slingboxes the code numbers can be between 0000-2047 (actually higher in newer Slingboxes but to stay safe we are better staying below 2047). In general, codes below 2000 actually relate to specific boxes, for example V0618 is the code for a TIVO and D0032 is the code for a Pioneer CD Player. But we can feel fairly safe using 2000-2047 for our own codes. The final part of the filename defines the chip for which it will run. 
: So if you were looking for the binary file for a PVR with a code number allocated 1234, designed to run on a PL-equipped Slingbox, you would be searching for a file called V1234_PL.BIN. Note: You must NEVER change the name of the file, as the letter, code number and chip type are also defined inside the file itself.

==='''JP1'''===
:You will hear a lot about "JP1". Basically this is a process whereby people using "One For All‟ (OFA) remote controls can add new codes to their remotes from their PC. The remote control processor inside the Slingbox is made by the same company that makes OFA remotes, so the upgrades are similar. The JP1 tools have been upgraded so that we can now use them to create and modify upgrades for the Slingbox.

=='''The Basic Procedure.'''==
The official procedure to follow is to report the [http://support.slingmedia.com/get/KB-005640.html Lack of a Supported Remote] to SlingMedia and they will add it to the database. In practice, they are not quick at doing this (I have been asking for a remote for over 2 years now), and the updated remote list seems to be only occasionally updated. That may change in the future but for now it is really not a practical quick solution. So for a short term fix what you need to do is to create or acquire the correct Binary code file for your A/V device, and then install it into your Slingbox. This installation process is covered in detail in [[#Installing_the_Binary_file_to_the_Slingbox|Section 4]], so first let‟s see where you can look for these files. 

=='''Obtaining the Binary file for the Custom Remote'''==

#Before starting, make sure in the setup wizard you have tried all the devices by that same manufacturer, even if the model number does not match, and all the associated code numbers. You might be lucky and find one that works and that will save a lot of work. If that doesn‟t solve the problem here is the step by step approach to getting hold of your binary file: 
#Go to the JP1 forum. This has a specific Download area for [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=87 Slingbox Custom Remotes], so go through all those to see if your device has already been done. 
#If it isn‟t there the JP1 forum also has a more general [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=4 File Download Area]. From this page you select the download area for the specific type of device and check there. If you are lucky you will find a source file for using in the program RemoteMaster (RM or KM files), the use of which is discussed in [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]]. 
#Have a look on the Hava forums. They are also using the same chips and the files might be there. Check out this [http://www.myhava.com/forum/viewforum.php?f=17&st=0&sk=t&sd=d&start=0 forum]. You‟re looking for a PK or PL file. They can be imported into Remote Master and then converted to the PK, PL, RV or JU files for the Slingbox. Again this is discussed in [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]]. 
#Find a friend with a Pronto remote. They have a very nice update system and can generate .ccf files that can be used with the tools on the JP1 site to generate the .bin file used by a Slingbox. However, this is not easy, and you will probably need help from the experts on the JP1 forum, but if you want to have a go on your own then you will need the [http://www.hifi-remote.com/forums/dload.php?action=file&file_id=1887 DecodeCCF] program, and [http://www.remotecentral.com/files/index.html .ccf] files. Note that the Pronto can also make .pcf files, but unfortunately we cannot decode those. 
If all of this fails, and you cannot get hold of a BIN file then the Remote will have to be built from scratch. You have 2 options here: 
#Do it yourself by buying a JP1.x learning remote (plus a JP1.x cable), or an IR Widget, and learn the codes needed to control the device. How to do this is covered in [[#Learning_the_IR_codes_from_your_own_remote|Section 5]] & [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]]. 
#Ask someone else to do the work for you. You can try this by posting a request for help in either:
##The [https://community.sling.com/content Slingbox Answers Forum].
##The [http://www.hifi-remote.com/forums/viewforum.php?f=19 JP1 forum]. 
I can normally install your device on my Harmony Universal Remote to mimic the original Remote and learn the codes for you (unless I am away on holiday). 

=='''Installing the Binary file to the Slingbox.'''==
 I have written a comprehensive Installation Guide at

http://placeshiftingenthusiasts.com/how-to-install-a-custom-remote-onto-the-slingbox/

Once you have completed the setup and the BIN files have been downloaded to the Slingbox they are not used any more and can be deleted.

=='''Learning the IR codes from your own remote.'''==
==='''Requirements'''===
Assuming you have decided to create the Remote Binary File yourself, the first stage is to learn the codes from your original Remote. This is what you need:
====Hardware====
#A computer with a USB port (or you can use older serial ports). 
#A Learning Remote and an appropriate JP Cable. Almost any "One For All" or "Radio Shack" remote that has learning will work for this but examples are: 
::URC-6820 (JP1.2)
::URC-8820 (JP1.2)
::URC-10820 (JP1.2)
::Radio Shack Gamer 15-133 (JP1.3)
::Radios Shack Satelite15-134 (JP1.3) 
:Note that some remotes need a JP1.2 cable and some need a JP1.3 cable (and some older, discontinued remotes such as the URC-9810 use a JP1 cable). Make sure the Cable and Remote match. Again the [http://www.hifi-remote.com/forums/viewforum.php?f=10 JP1 forum] is a mine of information. 
:If you are not sure there is a [http://www.hifi-remote.com/forums/dload.php?action=file&file_id=2981 chart of remotes] where you can look up a specific remote to see which format it uses. If you want to buy a cable try [http://www.diygadget.com/ DIYgadget] for the cheaper serial JP1.2/3 cables.

or An IR learning "widget". I got mine from Tommy Tyler through http://www.txsat.net/ (My preferred solution). 

====Software====
:If you are using a Learning Remote: [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=81 IR.EXE] [http://www.hifi-remote.com/forums/dload.php?action=file&file_id=7201 RDF Files] These are support files for the IR.EXE program. If you are using an IR Widget: [http://www.compendiumarcana.com/irwidget/irscope.zip IRSCOPE.EXE] [http://www.ftdichip.com/Drivers/VCP.htm The drivers] [http://www.hifi-remote.com/forums/dload.php?action=file&file_id=922 The IR decode DLL] Or download [http://rmrsoft.com/remote.zip my full IRSCOPE/REMOTEMASTER package]. Much of the JP1 software needs the java runtime environment (JRE) as well. A lot of computers will already have it installed already, but if you need it you can [http://java.sun/j2se/1.4.2/download.html download] Now we can learn the codes. First we will cover the procedure using a Learning Remote, then cover it using an IR Widget. 

===USING A LEARNING REMOTE===
====Getting the Codes from your Remote====
(These steps are based on using the older URC9810, the procedure will be slightly different for other Remotes so you will need to refer to the manuals.) 
:# Tap one of the buttons on the Learning Remote at the top which applies to the device you wish to create the bin file for. (eg. TV, DVD, Satellite). This is not totally necessary, you can always use TV, as it makes no difference to you, but if you subsequently upload the file for other users, it really ought to be for the correct type of device. 
:# At the bottom there will be a button called 'Set'. Keep your finger pushed on that until the LCD changes so you can modify your remote control. 
:# Click down until you come to an option called 'IR LEARN' and click select. 
:# Click one of the buttons on the remote control. For example, the '1' key, the LCD will say "Learning" and the red light will come on. 
:# Put your remote control in front of the learning remote and click the 1 key - if it is added correctly it should say 'Success'. If it fails (shows “Error”) then try again. There are a lot of different techniques for this procedure, the safest bet seems to be press the button on the Learning Remote, wait for 2 seconds then hold the equivalent key on the original Remote until the red light goes on. If you get a bad „learn‟, try just tapping quickly on the original key. A full description of these options is [http://www.hifi-remote.com/forums/viewtopic.php?t=3943 here]. 
:# Repeat this step for each of the keys you want to learn and have on your Slingbox Remote. If you get the "Memory Full" message then you will have to repeat this operation for the remaining keys after you have uploaded the first set of codes to your PC. 

====Getting the Codes onto your PC.====
 
:#Install IR.EXE onto your PC. It comes as a ZIP file rather than an installation package, which you need to unzip to your PC. The files can actually go anywhere but as a bit of tidy person (geek?) I created a C:\Program Files\IR\ folder and put the files in there and then created a shortcut on the Desktop. Important Note: For Windows VISTA users, I have found that I need to run the program in Windows XP Compatibility Mode to make it recognise the JP1 interface. Just right-click on IR.EXE, select Properties, then the Compatibility Tab and check the appropriate box. 
:#Create a sub folder called \RDF\ in whatever folder you have put the IR program and extract the RDF support files into that folder. 
:#Get your JP1 cable out and turn your remote control over, open the battery compartment and plug the JP1 6 pin connector into the Learning remote (you will see 6 needles where it plugs into). There are 2 ways to plug it in, but don‟t worry, you won‟t cause any damage by plugging it in the wrong way. Try them both if the first one fails. 
:#Plug the USB plug into your computer. As with any external piece of hardware you will need to install the drivers. There are drivers for the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=81 JP1 Remotes] and the [http://www.ftdichip.com/Drivers/VCP.htm JP1.2/3 Remotes]. Personally I use the JP1 ones dated 12 Feb 2008 and they work fine in Windows XP and also in Vista as long as the Windows XP Compatibility flag is set. 
:#Now open IR.exe. If you get told your RDF directory isn't valid, click OK and ignore this for now. It will look something like this: (Note this is a screenshot of V8.0. If that version hasn‟t been released yet, V7.15 looks very similar but does not have the icons at the top. [[Image:IR-general.jpg]] 
:#Go to File > Set Directory > RDF Path >. Select your RDF directory. You need to double click the RDF directory or it won't take. 
:#For peace of mind go to Interface > Check Driver... it should say the interface is connected. If it does then that's fine, if it gives an error message “Unable to open device, check connection” then it is not seeing the JP1 cable so you need to check the cable and the drivers. If it gives the error message “The remote is not acknowledging signals from the interface” then the cable is working fine but it is not seeing the remote. Try reversing the cable connection to the remote and hopefully that will cure the problem. 
:#Now click the "Download From Remote" button. 
:#Then click the "Learned Signals" tab (second from last one). It will look something like this: [[Image:IR-learned1.jpg]] 
:#On the left hand side there should be a list with the device type and the keys - eg "TV: 1". Click on it and details should show up in the right hand side listview. 
:#The first thing we need to make a note of is the Protocol (JVC) in this case, then the Device Number (239 in this case) and if it is displayed, the Sub-Device number. Then for each of the learned keys note down the OBC, Hex Code and EFC numbers. 
:#If you get the "MEM FULL" message on the Remote then Use File > Save As to keep a copy then tap the "Delete All" button, go back to the General Tab and tap the "Upload To remote" button to clear the Remote. Then learn the remaining buttons and follow the same procedure. Once they are all done, use the use the File > Save As command to save a copy of the final results. 
However, if you see a screen like this, it means that the protocol used by your remote is not recognised by the system. That means that you cannot create the Remote yourself but will have to ask the people on the JP1 forum to help you out. They have a much deeper understanding of the IR formats, and can often dig deeper into the signals and figure out the codes. [[Image:IR-learned2.jpg]] 
The procedure to do this is to use the File > Save As menu option to save the IR source file(s) (I tend to ZIP them up if there are more than one). Now upload them to the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=35 Diagnosis Area] in the File Section of the JP1 Forum. 
Check the file has been added, and make a record of it‟s location by right-clicking on it and select „Copy Link Location‟. 
Now create a new topic in the [http://www.hifi-remote.com/forums/viewforum.php?f=20 Protocol Decode Forum] and plead for some help, quoting the device Manufacturer and Model Number and the link to the IR source files. Offer incentives (money, beer, everlasting gratitude….) and you might be lucky. The experts may produce the RemoteMaster source file or even the Remote Binary files themselves. Now you can move on to [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]] for building the Remote BIN files. 

===USING AN IR WIDGET===
If you are using an IR Widget there is an excellent guide [http://www.txsat.net/IR%20Widget%20Rev%2014%20Final.pdf here] on the TXSat site. So I suggest you download that and read it thoroughly. There is no point in repeating it here, but just to emphasise a few points: 
:#You will want to regularly check for updates to the decodeir.dll. As new protocols are recognized, this dll will change. 
:#There is no way to save the learned values for importing into RemoteMaster (where you will make the remote) so you will need to write them down. 
:#Although I tend to put programs into C:\Program Files\.... this can be a bit dodgy in Windows as programs cannot save files to this area because of security limitations. So it might be safer to install it under \Documents\ 
:#The Guide has a very useful section comparing using a Learning Remotes and the IR Widget and highlighting the differences, (For example "Key" is equivalent to "OBC") so you could check out the previous sub-section covering using IR.EXE and the Learning Remote. And then you will understand this section. When complete you can move onto [[#Creating_your_own_Binary_files_using_RemoteMaster|Section 6]] to create the Binary file. 

=='''Creating your own Binary files using RemoteMaster'''==
:#To make life easier I have packaged a full set of the latest files required and uploaded them to my site. Just download them from [http://www.rmrsoft.com/remote.zip here] and unzip them onto your computer. 
:#Start RemoteMaster.EXE. You may be promoted to highlight the folder the folder that contains the RDF files (Highlight the \RDF\ folder in the folder where you placed Remotemaster). You may also have to do the same for the Images folder. The display will now look something like this:[[Image:RM-setup.jpg]] 
:#If you have obtained an .rmdu file then use the File > Open menu option to load the file. If you have obtained a .bin file then use the Advanced > Import Binary Upgrade to load up the details. If you have not obtained a file then you will have to input the codes manually. 
:#Now to explain the main Setup Tab: '''Description ''': Use anything you like, I tend to use the device name. '''Remote''': Select the one appropriate for your chip. '''Device Type''': Should be set to the correct type of device (as covered in Paragraph 3 of Section 1). '''Setup Code''': This is where you put the 4-digit code. In theory it can be any number between 0000 and 2047, but as explained in Section 1 Paragraph 3, numbers below 2000 may actually be already allocated to specific devices, so to be safe I personally use 2010. Fell free to use your own value. '''Protocol''': From the dropdown list select the Protocol you discovered when you used IR.EXE/IRSCOPE.EXE. '''Device''': Type in the Device code you recorded from IR.EXE/IRSCOPE.EXE. '''Sub-Device''': If applicable type in the Sub-Device code you recorded from IR.EXE/ IRSCOPE.EXE. 
:#Now tap on the Functions Tab [[Image:RM-functions.jpg]] This picture shows the program with an .rmdu file or .bin file already imported; otherwise the code columns will be blank. The entries are fully configurable, so if there are pre-defined functions that you do not need (pip swap, pipmove..) then you highlight them and tap the "Delete" button. If you have a function that is not pre-defined (Audio, Setup…) then tap the "New" button and enter them. Now fill in the codes for each button that you recorded. You just put in the OBC value and press <Enter>, the other 2 values will be generated automatically based on the protocol you selected. Also, if you used a JP1 learning remote, there's a way to cut and paste all the codes which saves needing to enter them all. In IR, if you select File > Summary you get a page listing lots of stuff. If you scroll down, you'll see a list of learn decodes. You can cut and paste this list into Excel, then you can re-arrange the columns and just select the button names and OBC codes to cut and paste into RM. You can move the RM columns, so if the OBC column isn't the one next to the button names, you can move it there. 
:#Now tap on the Buttons Tab [[Image:RM-buttons.jpg]] This is where you map the defined functions onto the available buttons. Simply tap the Auto-Assign button which should allocate most of the buttons. For any buttons left in red drag the function name from the table on the left to the function column on the right. But note that not all these buttons are available on a Slingplayer Generic Remote. For example the 'Slow' and 'Eject' buttons do not exist on a Generic Remote. So only map the functions onto the buttons that actually exist (You will see that when you check out the Layout Tab, and from experience when you have done this a few times). The important ones to note are the Custom 10-29 buttons. These are the ones you use for the functions you need that aren't on the generic remote and they subsequently appear in the drop down menu of the remote as Custom options (except for Custom 22-26 which are pre-allocated to the colour buttons). 
:#Now tap on the Layout Tab. [[Image:RM-layout.jpg]] This shows the generic Slingplayer remote and shows the buttons you can actually use in the Buttons Tab. If a button shows yellow then that means it is in use. If it shows black (the PgUp/PgDn in the picture) then has not been allocated a function. Again you can drag and drop functions onto a button. 
:#Once you have finished experimenting go back to the Setup tab. Select the appropriate Slingbox remote, go to the 'Advanced' menu at the top and select 'Export Binary Upgrade'. This will produce the BIN file that we have discussed in previous Sections. If you aren‟t sure which Slingbox Chip you have then create a BIN file for the main 2 chips, so that would give you something like 
:::C2010_PL.BIN
:::C2010_RV.BIN

So now you can go back to [[#Installing_the_Binary_file_to_the_Slingbox.|Section 4]] and install the new Custom Remote onto your Slingbox. 
====Finding Missing Codes====
You can often find yourself in the position where the Custom Remote generally works OK but some of the functions are missing or some are sending the wrong code. This is relatively easy to fix by trial and error. The OBC codes must lie between 0-255, so the first thing to do is make a list of the OBC codes that are not being used in the Remote Control. Now use Remotemaster to allocate those codes to the 0-9 buttons and the 15 Custom buttons. Now build a new BIN files, replace the one in your \SBAV\ folder and rerun the "Setup Video Sources" routine. Now try those buttons and see if any of them action the missing function. If you find the missing codes then you can update the original remote file. You may have to repeat this operation 10 times to cover all the missing codes, although you can cut down the number of times by also using the Transport buttons (Play/Pause…) and Channel, Page +/- buttons as well. 

=='''Give your Binary file back to the Community'''==
Finally, remember that it is good to payback. If you find a remote file that works for you then upload it to the JP1 Forums. The way to do this is: 
#Put the 4 Binary files and the Remote Master RMDU file into a ZIP file. I also tend to add a Readme file in case users are unsure how to use the files. Although hopefully they will have read this article and will know what to do. 
#To be really helpful, you should upload your files in 3 different places:
##Upload your ZIP file to the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=87 Slingbox Binary Files] area.
##Upload the Remote Master RMDU source file to the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=98 Slingbox RM Files] area.
##Upload the RMDU file to the appropriate area in the [http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=4 Device Upgrades] area.
 
I hope these instructions have been helpful. If you have any suggestions for changes or improvements please E-mail me at [mailto:alan@rmrsoft alan@rmrsoft].com.