JP1 Remotes

I have two (2) sling boxes one with beta the other with out....

i used ju at rm...outputed to sbav however the sling player say,s the code is outdated or not working so here are the files ...

www.hifi-remote.com/forums/dload.php?ac ... le_id=2809
www.hifi-remote.com/forums/dload.php?ac ... le_id=2807
www.hifi-remote.com/forums/dload.php?ac ... le_id=2808

my correct code format

Hey, b1harlem,

Unfortunately, I am unable to offer you any useful suggestions at this point, other than suggesting you look VERY CAREFULLY at what greg suggested a few posts back regarding beta software and the PL/JU possible mixup.

Also, a suggestion: When you make a mistake in a post, you can go back and "edit" the post - look in the upper right hand corner of any of YOUR OWN posts - it offers you an "edit" (or delete if it's the latest post in the thread("X")) option. I'd recommend you go back and delete/clean up all of the posts in this thread that have errors/duplication in them to reduce confusion for anyone coming in late and trying to catch up and help.

b1harlem wrote:i dont have a ofa remote(is that a learning guy?) excuse my ignorance
does this mean that the file is missing something maybe???

"OFA" is "One for All". It is the company brand for remote controls made by Universal Electronics International Corporation (UEI or UEIC).

Not all OFA remotes are learning remotes, but SOME are;
Not all OFA remotes are JP1 capable, but SOME are;
Not all of the JP1-capable OFA remotes are JP1-READY, but SOME are;

What IS common amongst virtually ALL OFA remotes is they use the SAME CODESETS, so if you HAD an OFA remote, you could conceivably test using a built-in CODE to see if the manual protocol could be replaced by a built-in protocol (in case THAT is causing the problem with your upgrade not working correctly)

Your Slingbox internal IR remote control is manufactured by UEI, hence the presence of this sub-forum within the JP1 forum.

The description you provide for https://www.hifi-remote.com/forums/dload ... le_id=2808 is "exported ju bin file"

However, it isn't a .bin file at all, it's a copy of your SBAV.CFG file.

Is it possible that you are using File -> Save as... to save the .rmdu file to the SBAV folder, instead of Advanced -> Export Binary File.. ?

cap n
if i need to get a ofa remote to ascertain wheather manual codeset should be replaced i am all for it ...would you recomend a certain brand? ... and is that something that would allow me to get this thing working??....I really am getting into this "remote stuff" you guys are way cool thanks for the help so far i am thinking that i am getting closer to solving the problem

greg
I hope not.... this is file from rm

www.hifi-remote.com/forums/dload.php?ac ... le_id=2810

doug

b1harlem wrote:greg
I hope not.... this is file from rm

www.hifi-remote.com/forums/dload.php?ac ... le_id=2810

doug

OK, so you have an RM ("rmdu") file. You also have a SBAV.cfg file. What remains unclear is whether you have ever correctly created the "S2007_JU.bin" file and saved it in your Slingbox folder. As greg points out, when you're in RM, under the "Advanced" menu selection at the top of your screen, you need to select the "Export Binary File" option and save it to the right folder.

We've asked you to upload this .bin file several times and have not yet seen it, leading to the suspicion that you haven't created it yet.

this is the file i saved in sbav.... then in sbav.cfg

www.hifi-remote.com/forums/dload.php?ac ... le_id=2811
thanks for the help man i am honored/and learning as well
doug

OK, but you have not modified your SBAV.cfg file to RECOGNIZE that code. Did you read the directions linked in the FIRST post in this forum, about how to do this whole Slingbox upgrade business?

You must EDIT your SBAV.cfg file. It doesn't magically edit itself, nor can it guess that you have added a new BIN file to the folder. I recommend opening it with Wordpad. Then scroll WAY WAY DOWN to the [Satellite.codes] section. You will see there listed a WHOLE LOT of satellite box manufacturers and codes for their devices. In FACT, Next Level IS ON THE LIST with code S0869 - Have you tried this built-in code?

Anyways, to use YOUR added BIN file, you have you modify this SBAV.cfg file by adding an entry in the [Satellite.codes] section to include YOUR BIN file that you created in RM, so in the Next Level line, you would add in S2007. (check the format of other entries to ensure you have the right punctuation and spacing, etc.) - and SAVE the modified SBAV.cfg file.

Only after doing all of that, should you be able to assign code S2007 to your Slingbox.

Is that clear? And if you have done it, then you've provided us the WRONG SBAV.cfg file.

OK - I found "urban=S2007" at the bottom of your Satellite list. Is that what you're using for Next Level?

If that's all correct, then we're back to something unique about the Manual protocol's behaviour.

I don't know what else to recommend at this point.

Rob? Back from vacation yet? You're a Sling-kinda guy, aren't you?

capn
this is the sbav cfg. ju file...
www.hifi-remote.com/forums/dload.php?ac ... le_id=2812

capn i have tried the nextlevel code and it doesnt work...
i apologize if i am trying your patience i am trying to learn as i go and i realize how frustrating that is for someone who is an expert so please accept my apology....I have included the sbav cfg file... if you recall i did everything in pl first and then ju...I hope i have inserted things in the right location
thanks again for you help and time
doug

Sorry I was called away for a while.
Capn explained what I was thinking though way better then I could have.

I am still thinking it is with the bin being made from rm. I may very well be wrong.

If I export to bin with an upgrade that is not manual settings then the bin file can be imported back into rm.

If the exported bin is from a manual settings upgrade then it either will not import back into rm. Or if I get it to import back in, it is an upgrade with no functions at all.

I think the fact that RM can't import the BIN file is a bug in the import function, not the export function. I'll double check, though.

Yep, just as I thought, it's a very simple fix to the import code.
There's nothing wrong with the .bin file.

So, it's back to a JU/PL issue, or an SBAV.CFG issue.

First of all, lets make sure we only try it on the Slingbox that isn't using the beta firmware.

Now, double check that blaster version, to see if we need JU or PL.

I'm just looking at your SBAV 2007.CFG file, and I see a number of things that don't look right:

[SATELLITE.RCA.S1392]
Panels=layout.remote.ultimatetv1;layout.remote.ultimatetv2;layout.remote.ultimatetv3
[SATELLITE.URBAN].S2007
Panels=layout.remote.trickmode;layout.keypad[PVR.RCA.S1392]
Panels=layout.remote.ultimatetv1;layout.remote.ultimatetv2;layout.remote.ultimatetv3

should be

[SATELLITE.RCA.S1392]
Panels=layout.remote.ultimatetv1;layout.remote.ultimatetv2;layout.remote.ultimatetv3

[SATELLITE.URBAN.S2007]
Panels=layout.remote.trickmode;layout.keypad

[PVR.RCA.S1392]
Panels=layout.remote.ultimatetv1;layout.remote.ultimatetv2;layout.remote.ultimatetv3

Also,

Zenith=S1856,S0856
urban=S2007
[VCR.Codes]
ABS=V1972
Admiral=V0048,V0209

should be

Zenith=S1856,S0856
urban=S2007

[VCR.Codes]
ABS=V1972
Admiral=V0048,V0209

The last thing I can suggest is:

Capn Trips wrote:You must EDIT your SBAV.cfg file. ... I recommend opening it with Wordpad. ... (check the format of other entries to ensure you have the right punctuation and spacing, etc.)