The most interesting part to me is the assigning of data to the buttons.
The spreadsheet (4*14) you get when you push the "add button" key was puzzeling to me.
It seems that when you add a button the default is to assign one of these buttons depending on the position where you place the button. Unfortunatly the program will not show you which one!
The result was that I ended up with two buttons assigned to the same "position".
After you learn a command to this button the other one got the same learned command assigned.
After I assigned a different value (even from another page in the spreadsheet) it did work.
After looking at the MDL database, you can see that only a value is assigned to the button. Normaly these are 7,9,11, etc. If you assign the first one of 4th page the number changes to 167 (yes that high).
So I believe that at this level of the software only a number is assigned to a key. In the remote this number is connected to 1. a learned command 2. the device default (after selecting a code)
The above also explains the "strange" hint in the manual about "redefining a button on same place as original" to get the default definition back.
A nice test (yes I will perform this one) is to assign value 35 to a new button. This value is connected to the previous page button. Lets see if this "new" button will skip pages.
Next step will be to see if in the LDT (learned commands) we can find the connection from button value to laerned command. I hope it is in this LDT, if not, whe need some other memory pages from the remote, which would be more difficult.
