I just emailed you the output from MakeHex which is the first 512 possible XMP signals with the same device code as your power toggle signal.
To generate that, I used the follwing XMP.irp file:
That .irp file plus MakeHex is all you would have needed to generate the .hex file yourself, but I decided to email it to reduce confusion.
The next problem is to identify which signals do what.
For code sets with just 256 signals, one way to do that is to paste the set of 256 signals into IrPanels.exe to produce a CCF file with 256 numbered buttons. Then merge that CCF into your own config with ProntoEdit, then test each of those 256 buttons and see what it does. With the codes I emailed, you could select and copy the block of functions from the beginning through function 255 to paste into IrPanels and do that test. It's even possible to tweak the .irp file to produce the second set of 256 in a form IrPanels can use. I'll explain later if you decide to go that way.[Link: remotecentral.com]
Another approach is to decode your existing imperfect learned signals, the way I decoded the one you posted to find that it is function 68. For that you need the JP1 version of IrTool.exe plus DecodeIR.dll[Link: remotecentral.com][Link: john.fine.home.comcast.net]
I'm using a slightly better version of DecodeIR.dll that I'm not ready to release yet. I hope the one I just linked is good enough for you. Otherwise I might email my development copy.
Once IrTool and DecodeIr are in the same directory, you run IrTool and paste each learned signal into IrTool and press "Decode Hex" and you should get a pop up dialog of DecodeIR results.
Each XMP signal has two parts, each of which should appear in that pop up decode and each of which should contain the function number you need.
If one of those parts is fully understood by DecodeIR, the decode will contain the function number after the last : within a string of other information you don't need.
For one of those parts that is misunderstood, either because of flaws in DecodeIR or because it was learned too badly, the string will include a 16 digit hex dump, such as this one that I get from several of the parts of your learn of power toggle:
Often one or two of the digits will be wrong. Hopefully they won't be the digits containing the function number.
To get the function number: first take the second to last pair of digits (44 in that example). Convert that number from Hex to decimal (Windows Calculator in View/scientific mode if you don't have a hex to decimal conversion you prefer to that). 44 hex is 68 decimal.
Next look at the last two digits. If they are 00, the number you just converted is the function number. If they are 01, you must add 256 to get the function number. If they are anything else, tell me the Pronto Hex string and I'll figure it out.
Since few function numbers above 127 are used and they aren't easy to look for with IrPanels, I manually checked them in the XMP CCF files I have. They are:
128 = enter
131 = ticker
132 = << back
133 = clear
The function names were created by whoever made the CCF file. Hopefully you have a better guess at what they mean than I do.
XMP function numbering is fairly consistent across a wide range of devices using XMP, but that doesn't mean every function matches, so those might not even be valid for your device.
Also, function 81 is labeled "buy". If you want to bulk test functions from IrPanels, you might need to be careful of that one.
Last edited by johnsfine
on October 2, 2007 09:32.