Your Universal Remote Control Center
RemoteCentral.com
Discrete Code Hunter Forum - View Post
Up level
Up level
The following page was printed from RemoteCentral.com:

Login:
Pass:
 
 

Original thread:
Post 20 made on Wednesday July 19, 2006 at 22:55
2nd rick
Super Member
Joined:
Posts:
August 2002
4,521
On July 19, 2006 at 18:46, johnsfine said...
Where is that utility available? I'm surprised
it would generate the crap you quoted, so I might
want to test to see what it is doing.

Well, it definitely respopnsible for the code that I posted...

I got it here: [Link: remotecentral.com]

Going back and looking at it, it was assuming Sharp codes. I can't believe that it generated anything. I was sent on a wild goose chase with that one...

Anyway, now I have the MakeHex working on my laptop, and I have the 255 codes from Device 64 (from the first hex #40 of the yet un-named file type).

I also have the decimal numbers for each of the codes I need from taking the third hex and converting it to decimal...

When I use MakeHex and change the device to 64, the converted hex is slightly off from what you posted above for the only known commands (power on = 7E and P-off = 7F)

This is what I got for the 7F conversion (function 127)

nec1.hex
Device Code: 64 Function: 127
0000 006D 0022 0002 0157 00AC 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0040 0015 0015 0015 0040 0015 0040 0015 0040 0015 0040 0015 0040 0015 0040 0015 0015 0015 0040 0015 0040 0015 0040 0015 0040 0015 0040 0015 0040 0015 0040 0015 0040 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0040 0015 0689 0157 0056 0015 0E94

vs. your command posted above for the same function number...

0000 006D 0022 0002 0157 00AC 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0041 0015 0016 0015 0041 0015 0041 0015 0041 0015 0041 0015 0041 0015 0041 0015 0016 0015 0041 0015 0041 0015 0041 0015 0041 0015 0041 0015 0041 0015 0041 0015 0041 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0041 0015 0689 0157 0056 0015 0E94

I see a lot of 0015 bytes in mine which are 0016 bytes ion yours... as well as 0040 bytes in my conversion which are 0041 bytes in your command...

John, any ideas on what went wrong??

Thanks in advance for your assistance.
Once I get the hang of MakeHex, I can convert and test the following commands...

Discrete inputs should respond to the following:
Vid 1 = 20 (32)
Vid 2 = 21 (33)
Vid 3 = 22 (34)
Vid 4 = 23 (35)
Vid 5 = 24 (36)
Vid 6 = 25 (37)
Vid 7 = 39 (57)
Vid 8 = 3A (58)
Vid 9 = 3B (59)
Vid 10 = 3C (60)
Ant 1 = 3D (61)
Ant 2 = 3E (62)

Discrete aspect controls should respond to the following:
Natural = C0 (192)
TheaterWide 1 = C1 (193)
TheaterWide 2 = C2 (194)
TheaterWide 3 = C3 (195)
Full = C4 (196)

Discrete video setting memories should respond to the following:
Sports = CD (205)
Standard = CE (206)
Movie = CF (207)
Preference = D0 (208)

John, what is the significance of the second and last hex numbers?? I saw your post relaying that this is a check byte inversely related to the third byte, and that was my first guess as well... but what is the second byte??

Please lighten up a little on the bashing. I don't get this kind of data very often, so I haven't invested a lot of time learning to interpret it.

I have shown you respect in every post....

Last edited by 2nd rick on July 19, 2006 23:14.
Rick Murphy
Troy, MI


Hosting Services by ipHouse