I have the MX-810 remote, a Mitsubishi HC-3000U projector, and the usual other components (receiver, dvd players, etc.).

I've set up a macro in the MX-810 software to "Watch HD DVD" and it works very well when I engage it - all devices turn on, the correct inputs are selected, etc. However, when I use the hard "Off" red button on the remote to end the Activity Macro, it turns off every component except for the projector. Not only does the projector not turn off, but it doesn't even register one of the two required button pushes (if it did, I would see a "power off" confirmation message on the screen).

I've gone into the "On/Off Automation" screen in the software to set up the "Turn Off Automation" settings appropriately (two pushes of the same button), but to no avail. I can't find any other screens in the software that allow me to make any adjustments that would improve my situation.

Is anyone else having this problem, and more importantly, does anyone know of a fix for this issue? I've tried re-recording the activity macro and that yields the same results. I've gone over the software several times looking for other ways to fix the problem, but have been unable to find any. Help!

Thanks,

Scott

I haven't programed an MX-810 yet but, on other remotes it helps to put the projector 1st in the 'off' macro with a .2 second pause between the two off commands.

Thanks for your response.

Hmm, not sure what you mean about putting it in the "Off" macro first. It would already be turned off before engaging the macro.

I also have no idea if it is possible to add a delay between two steps of the "Off" portion of the activity. I know you can add a delay to the "Power On" portion, but as for the "Off" portion, I haven't yet found a way to customize it that way.

On my MX-700 the OFF button is scheduled first for my projector and then a 1 second delay, then I power off the Audio and DVD... another 1 second delay... and then I have to program the SELECT button to confirm the powering off of the projector.

I just ordered a couple of 810's... I hope this is not going to be an issue. If it is, I may as well send them back and go another route.

The Power Off button is sort of a mystery.

I am guessing that you have the projector setup as a TOAD. If that is correct, I would try making it Discrete (Tune Up > Solve Automated Activity Problems > Change Power Method for a Component). Set the Power On to the Power On; set the Power Off to the Power Off button. Next head into the Browser. Select the projector in the Devices with a double click. Select the Power Off from the hard buttons. Open the WZR file you are using with Browse in the lower-left corner. Find the projector in the import tree. Copy the IR for the power from the Imported Action List to the MX-810 Action. So you should have two power commands on the off button for the projector. Put a delay between the two if needed.

It's not really intuitive, given the other MX architecture, but it should work.

If you just need a delay between two of the same power commands that can be done in solve activity menus. If the second key press is a different key than the first for confirmation of power down that needs to be programmed in the universal browser under the devices 'off' key.

Bob

Here is how you fix the Projector issue:

If you open an existing file it starts from the programming menu.

1. Select TUNE UP, then choose
2. ‘SOLVING AUTOMATED ACTIVITY PROBLEMS’ and hit next.
3. Next select ‘CHANGE POWER METHOD” and choose the device you want.
4. You will then select the Power On / Off...........then next
5. You should arrive at the ‘TEST ON / OFF AUTOMATION” page.

****If you intentionally FAIL THE TEST it will lead you to SL042. There you will be able to alter the button push for the projector***

Now when you add the on or off for the projector in a macro the remote will have no problem doing it.

Let us know if it helps...........cheers

Thanks for all the advice, everyone. Unfortunately, I don't yet have a solution to the problem.

[quote]I am guessing that you have the projector setup as a TOAD.[/quote]The PJ has discrete On and Off buttons on the original remote, and I've "taught" the MX-810 those power commands. If I use the hard power on and off buttons on the MX-810 outside of an activity macro, they work perfectly.

[quote]If you just need a delay between two of the same power commands that can be done in solve activity menus. If the second key press is a different key than the first for confirmation of power down that needs to be programmed in the universal browser under the devices 'off' key.[/quote]It's more than just a delay, since neither of the two required pushes of the "Off" button seem to be registering.

[quote]Here is how you fix the Projector issue:

If you open an existing file it starts from the programming menu.

1. Select TUNE UP, then choose
2. ‘SOLVING AUTOMATED ACTIVITY PROBLEMS’ and hit next.
3. Next select ‘CHANGE POWER METHOD” and choose the device you want.
4. You will then select the Power On / Off...........then next
5. You should arrive at the ‘TEST ON / OFF AUTOMATION” page.

****If you intentionally FAIL THE TEST it will lead you to SL042. There you will be able to alter the button push for the projector***

Now when you add the on or off for the projector in a macro the remote will have no problem doing it.[/quote]I thought this was the solution as well, but I had tried it last weekend and set up the "Off" option correctly, and yet I still have had no luck. Again, everything else turns off perfectly, while the PJ stays fully on (neither of the two required pushes of the "Off" button seem to work.

I'm wondering if the Browser isn't the place to go to fix this problem; unfortunately, I am not sure how to use it.

Do you have to push the button twice in the device menu? You might try deleting the activity and starting again fresh, if you have not already.

Yes, you do have to push the button twice in the device menu, and yes, I already tried recreating the activity. No luck.

I tested creating a macro on the off power button for a tv in the devices. The macro turned the tv off, then 3 secs later turned it back on. It worked in the activities as well. I did this using the browser.

First, I would change the pj back to a single press device in the power options menu under Tune Up, just so it doesn't send the power button twice.

Next, open up the browser. Double click the pj on the devices screen (if you don't double click, it won't open the pj). Select POWER OFF from the Hard Buttons box on the right. The MX-810 action list should have one command in it, like "Preprogrammed" or "XX.429.POWER". Add the delay.

Next, click the "Browse" button in the lower-left of the screen. Open up the WZR file you are working on. Find the pj in the Imported Tree View and select Hard Buttons. Locate and click on the Power Off button on Imported Panel View (Top-right). Select the item in the Imported Action List. Drag it to the MX-810 action list. It should look something like this:



You can simply close the Browser after you are done. Test the button on the device first. You should only have to hit the power off button once. Then try it on your activities. If the pj does not respond in the activites, but does when you're in the device, I can only think of one additional place to check: Tune Up > Solve Problems > Edit Off Button. Make sure that the projector is set to off.

Good luck. Sounds like a frustrating problem.

DSP81,

Thank you very much for your informative post. Using that information, as well as a lot of random attempts at fixing the problem, I've managed to get it to work...but only occasionally.

My model of projector (Mitsubishi HC-3000U) is not in the IR code database, so I had to select another model and then "teach" the MX-810 the correct codes when I initially set up the remote file. The other day, I deleted the device and selected a different device, just to make sure nothing funny was going on. I had heard rumors of "random" reliability in cases such as this, so I thought it was a prudent step.

Then, I used the Browser to add a "Power Off" command followed by a 1.5 second delay in front of the "Off sequence" for my macro (giving it, in essence, two "Power Off" commands).

Lastly, I noticed that every other component controlled by the MX-810 seems to have rock-solid IR reception / 100% functionality except for the projector. So, I messed around with the gain on the IR emitter for the projector. Right now, it's set on about 75% gain, whereas before it was much lower than that.

I also went into the Power Input Method section of Tune Up and changed the Power Off section to "Single Push."

After making all of these changes, it actually worked, but only one of the three times I tried it. Very frustrating and bizarre.

The funny thing is that after the macro is done turning everything off (except for the projector), I will go back to the devices menu, select the PJ, and then hit the "Off" button myself. The reliability on this is about 95%; usually the commands "take." Why would it work that way, but not as part of the macro? Doesn't seem to make sense to me.

Oddly, I've also noticed that the same thing seems to happen with the "On" sequence. when I select the macro, sometimes the PJ turns on, and sometimes it doesn't.

I even tried going back into the browser and adding 2 or 3 more "Power Off" commands to the macro, using the Browser. Still no luck. Sometimes one of the "Off" commands registers, sometimes none of them, and occasionally - when all the planets align - two of them register, and the PJ is turned off by the macro.

Long story short, I have no confidence that the PJ can/will be turned off during activity usage. I will keep plugging away, hoping to find a solution, and if anyone else comes up with ideas, I'd love to hear them.

Thanks again for all of the help everyone, and Happy Holidays!

You folks all probably understand the issues more than me. But in some very simple programming where the behind the scenes activities macros failed, my installer needed to code in an extra power ON step, for the power OFF to effectively trigger. Maybe some variation of this theme would be of value in your testing.

Make your own system off command. Really the only way to get it to turn off reliably.