Custom .bin for slingbox 350 from a 7962 remote???

This is the JP1 beginners forum. There's no such thing as a stupid question in here, so post away, but this forum is just for JP1 users and people considering JP1, non-JP1 users please use the appropriate forum above!

Moderator: Moderators

Post Reply
nitramsen
Posts: 6
Joined: Fri Feb 07, 2014 9:52 am

Custom .bin for slingbox 350 from a 7962 remote???

Post by nitramsen »

Hi,

I am trying to make a custom .bin for a IP cablebox that is not supported directly by slingbox.

I have learned the remote signals into a URC-7962 and I managed (With some help from gurus on this board) to download the IR learned signals into RMIR.

I then tried to follow the http://www.hifi-remote.com/wiki/index.p ... moteMaster. But the learned signals I get in RMIR does not look like the ones described in that document.

The learned signals look like this:

2 TV 36585 Nokia32 35 176 0 00 X=21 T=0
3 TV 36363 Nokia32 35 176 0 00 X=22 T=1

The hex signal data for 2 is
01 48 06 00 61 06 AE 00 60 02 42 00 60 01 C6 00 F0 00 D3 00 60 01 4B 00 60 00 D0 92 35 25 12 15 55 44 45 55 50

As fare as I understand I would normally just need to put in the OBC code in RM for each button and the rest would be generated based upon the protocol selected in setup. Since OBC is always 0 I assume that RM thinks it is the same code ???

So, I need to somehow add the timing (Or whatever the X=21 T=0 Means) to the RM Slingbox device upgrade to create a working device upgrade, I assume. But I have checked everywhere and I cannot find anything on how to do this.

Can these signals be turned into a slingbox .bin or are they to complex?

If yes, please give me a hint on how to do this.
vickyg2003
Site Admin
Posts: 7109
Joined: Sat Mar 20, 2004 12:19 pm
Location: Florida
Contact:

Post by vickyg2003 »

Could we see the actual captures? The decodes look funny and the posted hex has an "inconsistent length" So we can't see what is going on.

Post the file with the learns in it so we can open it up with the JP1 tools. Add a link to the file here.
nitramsen
Posts: 6
Joined: Fri Feb 07, 2014 9:52 am

Post by nitramsen »

I have uploaded the rmir file to: https://www.hifi-remote.com/forums/dload ... e_id=12339.

Thanks
Martin
vickyg2003
Site Admin
Posts: 7109
Joined: Sat Mar 20, 2004 12:19 pm
Location: Florida
Contact:

Post by vickyg2003 »

That box has a Nokia32 variant where sometimes the X changes instead of the OBC. I modified the protocol and uploaded a test file in the diagnosis section.


https://www.hifi-remote.com/forums/dload ... e_id=12340

Are there any more functions that we need to add?

How do I categorize this box?

Does this work?
nitramsen
Posts: 6
Joined: Fri Feb 07, 2014 9:52 am

Post by nitramsen »

Thanks, I will test it and let you know.
nitramsen
Posts: 6
Joined: Fri Feb 07, 2014 9:52 am

Post by nitramsen »

The cable box is a Swisscom TV-Box KMM3010-SC-B.

The remote is not complete as I only learned a few buttons.
Can you add the functions and update our files, or report the functions back here.


I would like to be able to do this myself in the future so if it is not to much trouble can you explain how you manages to do this ?

How did you convert the rmir file to a rmdu file?
90% of the time, we just open RemoteMaster, select the remote model and protocol and fill in the fields.

This time was different because the buttons were not decoding properly.

So it was a minor bit of assembly.

I learned how to do this by following the_Robman's examples in the Protocol Decodes forum. Then by trying to get to where he got. Then finally by asking very specific questions. It took him a Long, Long time to train me.
vickyg2003
Site Admin
Posts: 7109
Joined: Sat Mar 20, 2004 12:19 pm
Location: Florida
Contact:

Post by vickyg2003 »

:oops: Whoops sorry nitramse, I edited your post instead of quoted your post, and made it sound like you were quite crazy, when it was me. I need to handle my "powers" more responsibly.

Sorry. :oops:
Remember to provide feedback to let us know how the problem was solved and share your upgrades.

Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
Post Reply