teamvc wrote: 
OK
OK
!
I found a bug where I am stuck again!
I upload my IR file an the corresponding RFD to ask for your help.
Searching the forum, I managed to figure out that you had created your own extender 2 and 3, but even knowing this, the file you uploaded uses a further new extender, extender 4, apparently. Stating this information up front would probably have been useful.
It is a little difficult to determine what you are attempting to accomplish, and what you are asking. It is clear you have gotten pretty far with JP1 - writing your own extenders - but you are providing information that is difficult to understand, so it's hard to help. It is also not clear what advice or information from previous posts you have used, and what you have not used. I understand that english is not likely your first language, and I am trying to determine what you are asking.
Well, the first question one should ask is how have you implemented this extender? I am neither an extender writer nor an extender expert, although I do fancy myself an advanced user, of sorts. The way you modified the extender, although it apparently accomplished your immedate goal, makes it hard to use with the other tools (IR and RM).
(1) Your use of the same ID (CPT0CPx1) leads to confusion with extender 1 - with the same ID;
(2) There are OTHER modifications required for this extender to interface with IR the way others do, activating the Special Protocol Functions tab, for example. I don't know what changes need to be made to accomodate this, but doing so, will make it easier to troubleshoot your Special Protocol functions.
(3) This comment is only my personal observation, but your IR file is really not organized in a manner that is easy to analyze. Usually one tries to group Keymoves and macros such that either all of the functions of the same type (Power LKPs, Custom Mode names, etc) are grouped together, or all of the Keymoves for one device (SAT, TV, etc.) are grouped together. In your case, it's very hard to trudge through and identify all of the related functions. Perhaps youare unaware, but you can simply click-and-drag any Keymove or Macro to a new position on the list. I would recommend doing so for ease of analysis.
I'm not sure what this means. Does this mean tha the Power function is sent for a short press? Or that there is no difference between short and long press?
teamvc wrote:If I again press power it is working so I guess that there is something not in the state it should be after pressing ten TV-device key.
It's not a state thing, as far as I can see. I think you have too many keymoves trying to do too much and conflicting with one another.
When you press the Power button, the hierarchy of commands that the remote looks for is as follows:
FIRST PRIORITY: a Keymove assigned to that button for the current device mode (the mode to which you have assigned the "other" keyset);
SECOND PRIORITY: a Macro assigned to that button;
THIRD PRIORITY: The natural function assigned to that button in the device map (or upgrade)
You also seem to be confusing "shifted" buttons, with "X-shifted" buttons. They are NOT the same.
You can have THREE completely different functions assigned - One to the "bare" button (i.e. Power), one to the "shifted" button (i.e. shift-Power), and one to the x-shifted button (i.e. xShift-Power) They are NOT the same nor interchangeable. Shifted and xShifted buttons can ONLY be assigned functions by keymove or macro, not in a device code (neither built-in NOR upgrade)
This is COMPLETELY UNRELATED to "shift-cloaking". "Shift-cloaking" is a phenomenon by which, if you call on a "shifted" button BUT HAVE NOT ASSIGNED A FUNCTION TO THAT BUTTON VIA A KEYMOVE OR MACRO it will execute the underlying NATURAL FUNCTION assigned to that button in the device setup (or upgrade), IGNORING ANY KEYMOVE OR MACRO THAT MAY BE ASSIGNED TO THAT BUTTON. (More below when we look at YOUR file)
Theoretical example (not necessarily matching your remote setup): Your device upgrade has the normal Power toggle function assigned to the Power button, BUT you have written a macro on the Power button that will turn off all of your equipment. Also, you have NOT assigned any function to the shift-Power function. If you push Power, the macro will run, BUT if you push Shift followed by Power (on the 8910, the green p button is normally your shift-button, although the extenders allow you define ANY button as you shift button), the remote will FIRST look for a keymove or macro on this shifted-button. If it finds none, it will then execute the UNDERLYING BARE BUTTON's function, in this case - a power toggle to the active device. Thereby, even though you have assigned a MACRO to the Power button, you can still access the underlying function using "shift"-cloaking! This also works if you USE a shifted function in an LKP or Macro.
Now on to YOUR IR setup. You have the following functions assigned to (or associated with) the various incarnations of the Power button:
(1) DVD/Power - runs an LKP (shift-1 for short, shift-2 for long)
PROBLEM 1: You have no functions assigned to DVD shift-1 and shift-2 (although you have functions assigned to DVD xshift-1 and xshift-2, those are DIFFERENT buttons!)
PROBLEM 2: Since you have this keymove, when the "other" keyset is assigned to DVD mode, it will override your MACRO on the POWER button (the one that calls DEV-SAT, xs-phantom 2), so in DVD mode, you won't get a press of the Power button to execute your "global" Power LKP. It will send a "1" to your DVD player for short and "2" for long (via shift-cloaking!);
(2) AUX/Power - runs another LKP (calling shift-1 for short and shift-2 for long)
PROBLEM 1: The DEV-Cancel commands do nothing but consume memory, since that sequence has no DEV commands prior to that point
PROBLEM 2: Just as above for DVD mode, you have no functions assigned to AUX shift-1 and shift-2 (although you have functions assigned to AUX xshift-1 and xshift-2, those are DIFFERENT buttons!)
PROBLEM 3: Just as above for DVD mode, since you have this keymove, when you are in AUX mode ("other" keys assigned to AUX), it will override your MACRO on the POWER button (the one that calls DEV-SAT, xs-phantom 2), so in AUX mode, you won't get a press of the Power button to execute your "global" Power LKP. It will send a "1" to your Amplifier for short and "2" for long (via shift-cloaking!)
(3) The POWER Macro (LKP calling nothing for short press, DEV-SAT, xs-Phantom2 {DEV-Cancel, shift-Power} for long press).
THIS WILL ONLY EXECUTE IF THE "OTHER" KEYSET IS NOT ASSIGNED TO AUX or DVD, since those keymoves discussed above will override the macro.In ANY other mode, a short press should do nothing, whilst a long press should send whatever function you have assigend to the "power" button for that device (using shift-cloaking, as you have assigned nothing to the shift-power buttons.)
All of the "Power" functions you have assigned to xs-Power seem to serve no purpose other than to eat up memory.
I don't know if any of my rambling above helps, but I hope it gives you something to consider.
)
Success!!!! 
)
)