Oh I see what you mean, you want to know how I did what I did. First I copied all of the timing info from your learned signals into a text file. Then I looked at the data to see if I could spot the logical burst pairs, in this case the pairs are "+540 -1600" and "+1600 -540". Then I used the Protocol Builder spreadsheet to create the basic protocol.
There is a help document that describes how to use Protocol Builder here:
http://www.hifi-remote.com/files/help/P ... uilder.zip
http://www.hifi-remote.com/wiki/index.p ... ol_Builder
And you can download PB itself from here:
http://www.hifi-remote.com/forums/dload ... le_id=3591
However, PB has changed since I wrote that doc as it now includes an assembler, which is a very cool addition.
Your signals have 15 bits of fixed data and 9 bits of variable data. Here's the binary pattern...
101010101010101 011110011
101010101010101 111101011
101010101010101 111111100
101010101010101 111001111
101010101010101 111110011
101010101010101 111111111
101010101010101 100111111
101010101010101 000111111
101010101010101 011001111
101010101010101 011111100
Normally, we like to see 8 bits of variable data as this fits nicely into 1 byte, but looking at the above patterns you'll notice that the last bit is always a repeat of the previous bit, so I programmed the upgrade to use 8 variable bits and to generate the final bit itself.
In PB, I set the code to use 2 device code bytes, one of 8 bits and another of 7 bits. I then set it to use 2 variable bytes, one of 8 bits and another of just 1 bit.
Then, in the new Assembler sheet, I used the "Load Generated Code" button to convert what I had done so far into assembler. I then converted the format from 2-2 (ie, 2 device codes, 2 command codes) to 2-1 by editing the 3rd byte from 22 to 21.
I then added logic in assembler to do the following:
1. Copy the variable byte to a scratch register (LD RC0,R05)
2. Rotate the scratch register right in the CARRY bit (RRC RC0)
3. Rotate the carry bit into the 2nd command byte (RRC R06)
4. Increase the number of command bytes from 1 to 2 (INC R11)
5. Jump to the IR engine to send the signal (JP $0146)
You can look at what I did either by opening the PB file I created using the PB spreadsheet, or just by looking at the disassembled version of the protocol in IR.exe.
As you can see, this is a little bit above what we can expect a beginner, or even a mid-level JP1 user to be able to do, that's why the experts are usually more than happy to jump in and take care of this sort of stuff for you.