JP1 Remotes Forum Index JP1 Remotes


FAQFAQ SearchSearch 7 days of topics7 Days MemberlistMemberlist UsergroupsUsergroups RegisterRegister
ProfileProfile Log in to check your private messagesLog in to check your private messages Log inLog in

Need help with Nokia32 protocol

 
Post new topic   Reply to topic    JP1 Remotes Forum Index -> Slingbox
View previous topic :: View next topic  
Author Message
T-Rex



Joined: 02 Jan 2007
Posts: 4

                    
PostPosted: Wed Jan 31, 2007 2:16 pm    Post subject: Need help with Nokia32 protocol Reply with quote

I can seem to find the right protocol for my AT&T STB. In ir.exe, it learned the protocol: Mokia32, Device: 34 and Sub-Device: 208 ( http://yen.zapto.org/MySTB.ir ). But in RM there's no such protocol. I tried Nokia Quad but it does not seem to work. Please help....
Back to top
View user's profile Send private message
cyroc



Joined: 11 Jan 2006
Posts: 4

                    
PostPosted: Tue Mar 13, 2007 4:20 am    Post subject: Reply with quote

Hi T-Rex

The Nokia32 protocol is a little bit tricky to get into RemoteMaster. You will have to dig a little deeper in the world of IR remotes and codes.

A good introduction into how IR codes are structured can be found here: http://www.hifi-remote.com/infrared/index.shtml

Jon Armstrong has put together a nice little text how to convert the encoding from the Nokia32 format into raw format. Here is his recipe:

jon_armstrong wrote:
I put together a device and protocol upgrade using Protocol Builder (PB). Since you did a lot of research here is what I did:

In this case the fixed data according to the method of converting 00,01,10,and 11 ==> 0,01,011, and 0111 is:

00011101010100000110
That is 20 bits

The maximum value for OBC (255) is
0111011101110111 (16 bits)


But we must end with a 0 to get the on pulse of the lead out and we have to do it that way since the number of bits varies. (You must then pad after the 0 with sufficient 1's to get 16 bits). Fortunately, all OBC's will begin with a zero so we can add the zero to the last bit of fixed data. That way we can still do what we need in 16 variable bits or two bytes. since all the 1's after the final on pulse are just off times, we use a feature of PB that allows us to set a constant frame length in this case 100,516 uS.

We could have three 7-bit fixed bytes (if you have >2 bytes of fixed or >2 bytes of variable data then the fixed or varaible bytes must all be the same byte width), but I originally miscounted and and decided to use 24 bits of fixed data and put in 3 leading 111 (all off time so they are ignored) and used a mid frame burst after bit three as the lead-in.

My testing shows it to be decoding correctly so I think it will work. To convert the other OBC's that you decode use Excel and convert OBC to 8-bit binary, then convert each 2 bits as mentioned above. Then drop the most significant bit add a 0 as the least significant bit and then enough ones to make 16 bits and convert to two hex bytes.

For fixed data:

00011101010100000110
111 00011101010100000110 0 add three leading 1's and one trailing 0
11100011 10101010 00001100 rearranging
0xE3 0xAA 0x0C

For variable data:
OBC=1
00000001
00 00 00 01 ==> 0 0 0 01
00001 without the spaces
x00010 Drop the first msb 0 add lsb 0
00010 11111111111 add eleven 1's
00010111 11111111
0x17 0xFF


I will try to dig up my old conversion that I did for the Motorola DVI3000 cable box to give some more insights on how to get these codes working into Remotemaster
Back to top
View user's profile Send private message
cyroc



Joined: 11 Jan 2006
Posts: 4

                    
PostPosted: Tue Mar 13, 2007 10:06 am    Post subject: Reply with quote

I suggest to try the following:

- Download the Remotemaster file for the Motorola DVI3000 (or the Galaxis sat receiver KM file) from here:

DVI3000: http://www.hifi-remote.com/forums/dload.php?action=file&file_id=2691
Galsxis Easy: http://www.hifi-remote.com/forums/dload.php?action=file&file_id=1065

They both have a custom protocol defined (I tweaked the Galaxis one to work with 23bit device/subdevice codes).

- Open the file in Remotemaster (for KM files change the file type in the open dialog box)

- Do the encoding conversion for the device/subdevice code and the OBCs (a little bit of hex/binary knowledge is needed) as described

What you need to do is to convert your device/subdevice code into the 'Fixed Data' on the first tab like this:

Device/Subdevice (Fixed Data) 37/0

Code:

Decimal:   37           0
Hex:       25           0
Binary:    00100101     00000000
           00 10 01 01  00 00 00 00
N32 raw:   0 011 01 01  0  0  0  0
N32 added: 11111111111 001101010000 0
           11111111 11100110 10100000
N32 Hex:   FF       E6       A0


So the fixed code for the protocol should be FF E6 A0

- For the OBCs you follow similar procedure (see quote from jon_armstrong)

Code:

OBC 12

Decimal:   12
Hex:       0C
Binary:    00001100
           00 00 11 00
N32 raw:   0  0  0111 0
N32 fixed: 0011100 111111111
           00111001 11111111
N32 Hex:   39       FF


Fill these hex codes for the OBC in the HEX column for the function in on Functions tab. The OBC column will now display something different than your actual OBC because of the Nokia32 way of encoding data.

- Repeat for all important keys/functions
- Export Binary Update and cross fingers that it works
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic       JP1 Remotes Forum Index -> Slingbox All times are GMT - 5 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


 

Powered by phpBB © 2001, 2005 phpBB Group
Top 7 Advantages of Playing Online Slots The Evolution of Remote Control