Page 1 of 2
@ttone3 sat receiver
Posted: Fri Dec 28, 2012 8:50 pm
by kalug11
Hello,
I have had several Slingboxes along the years. This is my 7th I believe, so I am no newb. I have set up several different cable boxes, DVD players, etc. But I am really struggling with this new satellite receiver I got. it is called @ttone3 and for some reason I cannot get any of the included remotes to work on it. I have managed to get my Harmony 650 to learn all the buttons, but I can't seem to figure out, if there is a way, how to get the codes out of it.
I don't know if anyone else have this box, but if you do, please share the .Bin file.
if anyone know how to get the codes out of Logitech internet database that my Harmony 650 will save it too, I would deeply appreciate it as well.
Thanks in advance.
KG

Posted: Sat Dec 29, 2012 7:24 am
by alanrichey
I can do it for you but I need access to your learned entry on the Harmony. The easy option, if you don't mind, is to PM me with your Harmony login details and I can install it on my 659. If you don't want to give me your login details you need to rebuild it on my account so I can install it. The account is:
Username: slingboxes
Password: password
Al
Thanks Alanrichey!
Posted: Sat Dec 29, 2012 7:50 am
by kalug11
Alanrichey,
I have sent you my log in info for Harmony on PM. If you didn't get it, please let me know.
can't thank you enough,
KG
Posted: Sat Dec 29, 2012 11:13 am
by alanrichey
OK, partial success. Most of the buttons decoded as using the NEC1 protocol, Device 125:55, but the 'Player' buttons (Play/Pause/Rewind..) decoded using a different protocol, Sejin-1-56. Unfortunately Sling Remotes can operate only one protocol.
So as a starter, I have created the remote for everything except the player buttons at
https://www.hifi-remote.com/forums/dload ... e_id=11626 (I had to guess the Red button as it didn't learn correctly, but I am fairly confident I got it right)
So first check that works.
Now, when it comes to the player buttons, here are my thoughts:
1. They may also react to a NEC1 code but I have no way of knowing that except through trial and error. That is unless one of the 'real' experts here know if there is a fixed correlation between the 2 protocols so I could convert the Sejin-1-56 OBC to a NEC1 code ?
2. You could install a different Custom Remote on one of your unused inputs (S-Video), and switch to that if you wanted to operate the player. Downside of that is that you would be doing it blind unless your box also has an S-video or component video output as well ?
Posted: Sat Dec 29, 2012 12:01 pm
by vickyg2003
Alan, can you recheck you Nec1 decodes. I'm thinking that you'll find the frequency is off for the Nec Decodes. Nec's run at a frequency of 38.4 k, the Sejin 1- 56 runs and 56k. I'm betting that the Nec's are not really Necs, but something that looks like Nec but runs at a higher frequency.
Posted: Sat Dec 29, 2012 12:22 pm
by alanrichey
Sorry, bet lost

The buttons that are decoding as NECs are showing as 38.4K, and the 'player' buttons are showing as 56K.
So I guess that means the manufacturer has intentionally decided to implement 2 different protocols in their device ?
Posted: Sat Dec 29, 2012 1:31 pm
by 3FG
Al,
We have 3 upgrades that decode as NEC1 device 125.55. All are for SonicView satellite, and they are all the similar.
Here's one with a pretty good set of notes.
Maybe this will match this current box and give you the transport signals.
I doubt that Seijin would be actually be used, and I have to wonder if the Logitech learns are really correct.
Posted: Sat Dec 29, 2012 1:49 pm
by alanrichey
OK, for 'kalug11'. I know when you do learns on the Harmony it initially tries to match with the database. Can you re-learn the player buttons using the Raw Custom option ? Let's see if they are different.
Posted: Sat Dec 29, 2012 1:55 pm
by alanrichey
Actually that sent me looking as well

I had a SonicView SV-HD8000 that seemed to fit the bill. A few of the OBCs were different but the majority were the same. So I have installed a second version of the BIN files, with the player buttons filled in at
https://www.hifi-remote.com/forums/dload ... e_id=11627
Give that one a try.
Posted: Sat Dec 29, 2012 2:04 pm
by alanrichey
And following on from that I see that a new box had appeared in my account called 'Satellite' and that had the player buttons decoding as expected with the NEC1 protocol.
I guess that second upload is the one to go for ?
Posted: Sat Dec 29, 2012 5:08 pm
by kalug11
Alan,
Sorry I went MIA this afternoon. the box I put on your account is the @TTONET3. On that one, I input all of the commands by learning the IR (I didn't want to trust the codes they matched up with my remote). The play buttons (play, pause, stop, etc) I did not match because they are not used on my box, so I didn't learned their IRs. I am not sure what the box called Satellite is.
Let me know which set of bin files should I use on my Slingbox,
Thanks
KG
Posted: Sat Dec 29, 2012 5:13 pm
by alanrichey
Eiher, doesn't matter
Posted: Sat Dec 29, 2012 5:50 pm
by kalug11
Alan,
I am having trouble uploading the files to the slingbox web player. It keep on telling me that I have an "Invalid custom bin file, click here for more help." I see you named the file with starting with a C, so I am assuming that you coded for a cable box. I then choose Custom for the manufacture. I have placed the files on C:/ to make it easy, but I also tried on other folders. I also tried using satellite and changing the first letter on the file to "S" but all in vain, I get the same message all the time.
I have a "Slingbox Pro" bought in the US.
any ideas?
KG
Posted: Sat Dec 29, 2012 6:32 pm
by kalug11
Also,
I have tried to install the stand alone player, but it does not want to work with the windows 8.
very frustrating, so close but yet so far. lol
as always, thanks for the support
Posted: Sat Dec 29, 2012 6:32 pm
by alanrichey
What are you typing in ? It needs the full path and filename, i.e. C:\C2010_PL.bin. If that doesn't work then use C:\C2010_PL.bin.
Or even better follow my recommendation in the instructions and use the standalone player to install it.