The fact is that I realy need discrete ON and OFF for my whole system to work.
(macro for power ON and power OFF home cinema system)
After some reaserch, I found that this protocol use toggle bit.
So, I made the following test.
I learn the 1st power depress on the 1 Key and the 2nd power depress on the 2 Key.
And tadaaaa! It works!
The 1 Key is now a discrete ON and the 2 Key is now a discrete OFF.

My problem is the following:
How include the both learned signal in the protocol given by alanrichey.
When I go to the Learned Signals tab in IR, this is what I have:

As you can see, EFC 050/OBC 12/Hex 0C are the same for both Discrete ON and Discrete OFF.
The only thing that change is T=1 for Discrete ON and T=0 for Discrete OFF.
I don' see were I can put this info back to remotemaster the modify the rmdu file.

Ouch! That's a HSC08 remote, and I'm not familiar with the assembler. Still, I'll try to look a the S3F80 executor, which should attempt to do the same things as the HSC08 executor. Maybe we can see away to get what you want.

Yes, you are right Vicky!
I just move the two learned signals to Phantom14 and Phantom15 keys and it works like a charm.
Sometimes the things seems harder than they really are.

Just for my personal knowledge, is it easy, hard or impossible to build an RMDU file that include all the original keys plus the two learned signals.
I think that it could be usefull if I want to share my VU+Solo2 file to someone that have an different remote control.
(Simply copy and paste the protocol in IR.)

Otherwise, would it be possible to use the RC6-M-32 protocol instead with the appropriate toggle settings to suppress the toggle? I'm thinking you'd have a total of 3 upgrades and combine them with device combiner. Upgrade 1 would be standard MCE with all commands except discrete power. Upgrade 2 would be RC6-M-32 with just the discrete off as the only function, toggle off, and subdevice matching the value required for T=0. Upgrade 3 would be like 2 except for discrete on and T=1.

In RM, just pick "Device Combiner" in the protocol drop down. Then you get a new Device Combiner tab where you can add your 3 devices. You'll have to read the protocol notes for each to get the right settings.

I was throwing the RC6 protocol option out there as a possibility. I'm not certain it would actually work, but it's worth a try. You can test it by skipping the combiner part for now and just making a device upgrade with settings I described, in order to test the concept for your discrete power commands.

Just for my personal knowledge, is it easy, hard or impossible to build an RMDU file that include all the original keys plus the two learned signals.
I think that it could be usefull if I want to share my VU+Solo2 file to someone that have an different remote control.

In this case it just doesn't seem to be worth the effort. You can transfer the learn to most remotes. Sometimes it's hard to do because you need to delve into assembler. In this case it is a different language than the majority so to share it you would need to do both languages. If you had needed the signals for a non-learner or a remote using an extender there would have been more incentive to get it done. And before trying an executor approach, testing all possible obc's to see if there already is a discrete would be a better option. Or had you already done that.

There is a lot we can do with custom executors._________________Remember to provide feedback to let us know how the problem was solved and share your upgrades.

Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.

After a lot of tests, it works !
I do exactly as mdavej told me but have some difficulties to find the right settings.
Summary:
* In SETUP tab, choose Device combiner (Protocol 01 44).
* In DEVICE COMBINER tab, add 3 protocols

- The 1st is MCE (Protocol 01 2A) with Device=16 and OEM2=82.
I use this protocol for all functions except discrete power.
- The 2nd is RC6-M-32 (Protocol 01 2A) with Device=128, Sub-device=21008 (16+256*82+0), M=6, RC6 T-bit=0, MCE toggle=no.
I use this protocol for Discrete ON (EFC=050).
- The 3rd is RC6-M-32 (Protocol 01 2A) with Device=128, Sub-device=21136 (16+256*82+128), M=6, RC6 T-bit=0, MCE toggle=no.
I use this protocol for Discrete OFF (EFC=050).

* In FUNCTION tab, create all function choosing the right device and the right EFC.

I'm thinking you'd have a total of 3 upgrades and combine them with device combiner. Upgrade 1 would be standard MCE with all commands except discrete power. Upgrade 2 would be RC6-M-32 with just the discrete off as the only function, toggle off, and subdevice matching the value required for T=0. Upgrade 3 would be like 2 except for discrete on and T=1._________________Download high quality Pass4sure 640-554 dumps to prepare and pass wikipedia with oracle certification dumps certification. Also get free demos of University of Pennsylvania for review of jncia training.