How to Convert LIRC Code to Slingbox BIN?

donmark · Post by **donmark** » Sat Aug 18, 2012 7:34 pm

Hi,

Can someone let me know how to Convert LIRC Code of my remote control to Slingbox BIN?

Thanks in advance.

donmark

#
# This is a space encoded remote control.
# You need at least lirc-0.5.4 to use this config file
#
# contributed by
#
# brand: Movistar
# model: Movistar Remote Control
# supported devices: .
#
begin remote

name
bits 32

pre_data_bits 0
pre_data 0x0
post_data_bits 0
post_data 0x0
pre 0 0
post 0 0
gap 12937

begin codes
0 0x10001d0f
1 0x1000590f
2 0x10006900
3 0x10007901
4 0x10001c0e
5 0x10002c0f
6 0x10003c00
7 0x10004c01
8 0x10005c02
9 0x10006c03
CURSOR_LEFT 0x1000580e
CURSOR_RIGHT 0x1000680f
CURSOR_DOWN 0x1000480d
CURSOR_UP 0x1000380c
CHANNEL_UP 0x10007a02
CHANNEL_DOWN 0x10005a00
OK 0x10000f00
EXIT 0x10005b01
MENU 0x10002f02
EPG 0x10006a01
POWER 0x10000809
INFO 0x1000490e
MUTE 0x10006b02
BACK 0x10001b0d
NEXT 0x10009a04
PREVIOUS 0x10008a03
FASTFORWARD 0x10003a0e
REWIND 0x10002a0d
PLAYPAUSE 0x1000290c
RECORD 0x10002104
PVR 0x10001e00
STOP 0x10004a0f
FAVORITES 0x10008d06
VOLUME_UP 0x1000390d
VOLUME_DOWN 0x10007e06
AUDIO 0x10004f04
SUBTITLE 0x10005f05
RED 0x10004b00
GREEN 0x10003f03
YELLOW 0x10007800
BLUE 0x10001f01
DELETE 0x10008f08
CUSTOM1 0x10004d02
CUSTOM2 0x10001a0c
CUSTOM3 0x10007f07

end codes

end remote

Barf · Post by **Barf** » Sun Aug 19, 2012 2:10 am

Hi,
the posted LIRC file does not make sense. First the name is empty, which is easy to fix.
lircd barfs when it sees it, even if the empty name field is fixed. The reason is this

Code: Select all

pre_data_bits 0
pre_data 0x0
post_data_bits 0
post_data 0x0
pre 0 0
post 0 0

i.e., nothing to code the gaps and flashes on.

How did you arrive at the LIRC file?

Post by **vickyg2003** » Sun Aug 19, 2012 7:09 am

Barf wrote:Hi,
the posted LIRC file does not make sense. i.e., nothing to code the gaps and flashes on.

Thanks Barf. I took a look at this in the middle of the night, and couldn't make heads nor tails of this.

The checksum (adding all the previous nibbles together) reminded me of the zaptor description found in "interpreting IR Signals" but without the timing data there is no way to determine exactly what this is going to be.

Some UEI models list satelite codes 2527 and 2761 for the Movistar type PVR satelite box, but I don't have any remotes new enough to have the code to take a look at what comes out.

3FG · Post by **3FG** » Sun Aug 19, 2012 1:35 pm

Following Vicky's lead, I looked in JP1Master, and found that the Motorola 1980-9 Cable upgrade uses Zaptor. Comparing the LIRC data with the OBCs in the upgrade (this is a msb IR protocol, so the JP1 Hex data is the same as the LIRC hexadecimal representation) shows that the digitss, cursors, color buttons, and others are the same as the Motorola upgrade. So there is a pretty good chance that this is Zaptor. However, we have seen Zaptor at both 36 and 56 KHz.

Here's an upgrade (obviously untested) at 56KHz that may send the correct signals.

As before, I claim ignorance and incompetence to make a Slingbox bin file.

Post by **The Robman** » Sun Aug 19, 2012 7:01 pm

3FG wrote:Here's an upgrade (obviously untested) at 56KHz that may send the correct signals.

As before, I claim ignorance and incompetence to make a Slingbox bin file.

When you have the file open in RM...
1. Change the selected remote to "Slingbox with UEI RV Chip"
2. Check the button assignments (as the Slingbox has more buttons than most remotes), putting any leftover functions on the "Custom" buttons
3. Select Advanced > Export binary upgrade
4. save the RV file somewhere

5. Change the selected remote to "Slingbox with UEI PL Chip"
6. Select Advanced > Export binary upgrade
7. save the PL file somewhere

8. zip 'em together and load 'em up

I just did that and created a zip with your RMDU file and the Slingbox bins:
https://www.hifi-remote.com/forums/dload ... e_id=11217

donmark · Post by **donmark** » Sun Aug 19, 2012 9:15 pm

Thank you all so much for the help, I will try it tomorrow (I don't have the STB with me now) and let you know if it works.

alanrichey · Post by **alanrichey** » Mon Aug 20, 2012 5:20 am

I'm a bit confused here. Where did 'donmark' say the STB was a Motorola 1980-9 ? And the initial post talks about a MovieStar remote rather than a Moviestar STB ?

If Rob's doesn't work I'd be happy to try and build the BIN files if I knew the full details of the STB.

Post by **The Robman** » Mon Aug 20, 2012 6:09 am

alanrichey wrote:I'm a bit confused here. Where did 'donmark' say the STB was a Motorola 1980-9 ? And the initial post talks about a MovieStar remote rather than a Moviestar STB ?

Vicky suggested that the protocol could be Zaptor because it's been known to cause strange learns like those in the first post, so Dave must have searched for upgrades that use the Zaptor protocol and compared the OBCs to those shown in the first post and found a match with the Motorola box.

Do you see any MovieStar listings on your Harmony?

alanrichey · Post by **alanrichey** » Mon Aug 20, 2012 6:23 am

The Robman wrote:Do you see any MovieStar listings on your Harmony?

No, not a recognised manufacturer.

Post by **vickyg2003** » Mon Aug 20, 2012 7:23 am

The Robman wrote:Do you see any MovieStar listings on your Harmony?

That was my first mistake. Its Movistar not Moviestar. Movistar is a registered trademark of Telefónica.

alanrichey · Post by **alanrichey** » Mon Aug 20, 2012 7:59 am

Still not an STB manufacturer, looks like they do phones. Hence my original question, I think 'donmark' is talking about a remote control. We need him to confirm the Make and model of the STB.

Barf · Post by **Barf** » Mon Aug 20, 2012 11:23 am

... and I still think it would be interesting to know where he got the LIRC file from. It is flawed as it stands, but still contains numbers associated with the keys, that definitely looks meaningful.

donmark · Post by **donmark** » Mon Aug 20, 2012 3:34 pm

The BIN files didn't work.
It's a remote control for a development STB not a production STB.
Th lirc file is from the box, it works with the box. Is there a way to just convert this lirc file into the BIN files?
Thanks

Post by **vickyg2003** » Tue Aug 21, 2012 12:40 am

There isn't enough information in this lirc file to convert it.

All we can do is guess. I would have thought the zaptor was a good choice, especially since the OBC's all lined up with an existing zaptor upgrade. However I did re-read the comments in the file where it said it was "space encoded". I think that means that its the timeoff that differentiates between 0 and 1, where the zaptor is "phase encoded' Without any timing data, its pretty hard to guess at what is being done here.

There used to be a betaremotes site for building an upgrade from learns, for certain slingbox models. I think this has gone out of beta, but I am really not aware of what the current slingbox site allows. Since you are using a development box, I think you'll probably need the learning.

If you can get the the learned signals, we could use that timing data to build an upgrade.

Barf · Post by **Barf** » Tue Aug 21, 2012 11:56 am

donmark wrote: Th lirc file is from the box, it works with the box.

Can you elaborate upon that? What exactly is working? What is the lirc you are using? A lircserver running on the box, or a program running on a PC? There is a possibility that it is some sort of customized lircdaemon, that can make sense of the, in the normal sense, faulty LIRC file. Lirc is not lirc, unfortunately. (I read the mailing list, and it is amazing how people sometime wants to uses/misuse it.) Possibly you can upload the program to the diagnosis area?

Is there a way to just convert this lirc file into the BIN files?

Most likely yes, if you can provide us with the relevant information.

Another way would be to capture just a few actual IR signals: then we can probably reconstruct the rest on them from the "lirc file".