Hey,



I have a load of codes for my Pixel Magic MB200 which are this sort of length.

900A 006D 0000 0001 40BF 55AA

Now entering this under Nevo will not work. It says invalid HEX or something along those lines.

So how do I convert it to something this sorta length?

0000 0073 0000 001E 0070 0020 0010 0010 0010 0010 0010 0020 0010 0020 0020 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0AC6

I have tried Makehex but to no avail. I can't fitgure out how to use it. I can post all the first length codes if someone can help. Even a idiots step by step guide would be helpful, I just don't understand the readme file and how to get Makehex working. Not very good with command line apps.

Here they are...

Power: 900A 006D 0000 0001 40BF 43BC
Mute: 900A 006D 0000 0001 40BF 40BF
Menu: 900A 006D 0000 0001 40BF 4FB0
Title: 900A 006D 0000 0001 40BF 4EB1
Audio: 900A 006D 0000 0001 40BF 0AF5
Vol+: 900A 006D 0000 0001 40BF 08F7
Vol-: 900A 006D 0000 0001 40BF 09F6
TV Mode: 900A 006D 0000 0001 40BF 54AB
Up: 900A 006D 0000 0001 40BF 4DB2
Profile: 900A 006D 0000 0001 40BF 55AA
Left: 900A 006D 0000 0001 40BF 51AE
OK: 900A 006D 0000 0001 40BF 52AD
Right: 900A 006D 0000 0001 40BF 4CB3
Media: 900A 006D 0000 0001 40BF 4BB4
Down: 900A 006D 0000 0001 40BF 50AF
Info: 900A 006D 0000 0001 40BF 49B6
Subtitle: 900A 006D 0000 0001 40BF 0BF4
1: 900A 006D 0000 0001 40BF 03FC
2: 900A 006D 0000 0001 40BF 02FD
3: 900A 006D 0000 0001 40BF 01FE
4: 900A 006D 0000 0001 40BF 07F8
5: 900A 006D 0000 0001 40BF 06F9
6: 900A 006D 0000 0001 40BF 45BA
7: 900A 006D 0000 0001 40BF 07F8
8: 900A 006D 0000 0001 40BF 06F9
9: 900A 006D 0000 0001 40BF 05FA
Back: 900A 006D 0000 0001 40BF 5BA4
0: 900A 006D 0000 0001 40BF 4AB5
Setup: 900A 006D 0000 0001 40BF 5AA5
Repeat: 900A 006D 0000 0001 40BF 00FF
A-B:900A 006D 0000 0001 40BF 44BB
Zoom: 900A 006D 0000 0001 40BF 04FB
Angle: 900A 006D 0000 0001 40BF 48B7
Search: 900A 006D 0000 0001 40BF 56A9
Pause: 900A 006D 0000 0001 40BF 59A6
Play: 900A 006D 0000 0001 40BF 59A6
Forward: 900A 006D 0000 0001 40BF 5EA1
Reverse:900A 006D 0000 0001 40BF 5FA0
Stop: 900A 006D 0000 0001 40BF 58A7
Prev: 900A 006D 0000 0001 40BF 11EE
Next: 900A 006D 0000 0001 40BF 10EF
Power Off: 900A 006D 0000 0001 40BF 639C


Thanks.

What is a Pixel Magic MB200 and why does it use a rearranged version of the IR code set of a Toshiba TV?

There are obvious errors in your list of codes, such as the 4 and 7 buttons having the same signals. I suspect whoever learned these codes in the first place did a very sloppy job of keeping track of which original button went with which code. So once you get them all converted many of them will have the wrong function name and some will be missing.


That is a condensed form of Pronto Hex that most Pronto models understand, but most other programs that import Pronto Hex don't understand.

900A 006D 0000 0001
indicates that it is NEC1 protocol, so to use MakeHex you use the NEC1.irp file.

40BF indicates that it is device 64. So you must open NEC1.irp in a text editor, such as Windows Notepad, and change the device line to say
Device=64
(then save that modified .irp file from NotePad).

The 55AA means the function number is 55 hex, which is 85 decimal.


I don't know how to make the readme any clearer.

You don't need to use it as a command line app. You can simply drag the (edited) NEC1.irp file icon and drop it on the MakeHex.exe icon and MakeHex will run and exit leaving behind a new NEC1.hex file with all the Pronto Hex for this device.

You can open NEC1.hex in NotePad and find each Pronto Hex string labeled with a decimal function number. To pick out the ones you want you need to convert the hex function numbers you have to decimal (use Windows calculator in view/scientific mode).

Of course if you didn't have a problem with command line apps, you could run MakeHex that way (as described in it's readme) and use its -h command line option to label the output with hex function numbers.


In each one the first two digits of the last value are the function number in hex (43 hex is 67 decimal).

Thanks for the detailed post!

I have successfully made the .hex file. And when opening it comes up with a load of functions and long hex codes.

I dont understand this part though...

You can open NEC1.hex in NotePad and find each Pronto Hex string labeled with a decimal function number. To pick out the ones you want you need to convert the hex function numbers you have to decimal (use Windows calculator in view/scientific mode).

What am I looking for in the calculator? What do I insert, what button do I press and then what numbers etc do I look for what comes out in the calculator display with regards to the .hex file?

Thanks.

The data you started with looks like:

Power: 900A 006D 0000 0001 40BF 43BC

I marked a pair of digits in red. The pair of digits in that position is the function number in hex.

1) Start Windows calculator.
2) Pull down the view menu
3) Make sure "Scientific" is marked (and "Sandard is not marked). Otherwise click on "Scientific" to mark it.

4) Click the Hex button.
5) Type the hex number (43 in this example) into the number field.
6) Click Dec button
7) Read the number (67 in this example)
8) Find the line in the .hex file with "Funtion: 67"
9) Copy the Pronto Hex immediately below that line of the .hex file and use it for the named function ("Power" in this example).

Repeat steps 4 through 9 for the next line of original data.

Is this the right way to do this codes?:

900A 006D 0000 0001 EE87 09F2

900A 006D 0000 0001 => use NEC1.irp
EE87 => Device 238
09F2 => Funtion number 09

and this:

900A 006D 0000 0001 EE87 385E

900A 006D 0000 0001 => use NEC1.irp
EE87 => Device 238
385E => Funtion number 56

Close.


Usually correct.


No, Device=238.135


Oops! The function number is 09, but if it were really NEC1 protocol that would have been 09F6 not 09F2


Similarly that would have been 38C7

If the 5'th number had been EE11 that would be device 238.

NEC can have a one part device number, such as 238, or a two part device number, such as 238.135.

When it has a one part device number, the hex byte that would have held the second part is a check byte constructed so that the two hex bytes of device information add up to FF (EE + 11 = FF), (40 + BF = FF), etc.

NEC1 does not have two part function numbers. The two hex bytes of the function always add up to FF. Your examples don't.

There are a few devices such as Tivo that use a protocol similar to NEC1, but with different rules for those last two digits. To generate those signals you need a .irp file slightly different from NEC1.irp.

But with just the two samples you gave it already contradicts each of the possible alternate rules I recall for those last two digits. To generate more than one signal at a time with MakeHex you would need to know the rule for the last two digits. (For one signal at a time, you could replace the ~F in the .irp file with the decimal value of the last two digits).

Were those samples real? Or did you just make something up to test your understanding of the translation process?

Hey thanks, those samples are real for the Home Dock from DLO, the full code set follows:

900A 006D 0000 0001 EE87 09F2<<
900A 006D 0000 0001 EE87 06F2>>
900A 006D 0000 0001 EE87 05F2>
900A 006D 0000 0001 EE87 05F2stop
900A 006D 0000 0001 EE87 6E5E|<
900A 006D 0000 0001 EE87 A15E>|
900A 006D 0000 0001 EE87 385Epwr

is it possibel to make the new .irp with only this, what is the logic you use to make the irp?

Thanks again.

For that few it's easier to give you the results than the method:



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



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



? Two names for one hex code ?

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


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


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


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



I replaced the ~F in the NEC1.irp with the decimal value of the last byte. Needed two runs of MakeHex because you have two values there.