We have two MX-780's set up for two different customers. Totally different equipment. Programs work fine 99% of the time. Problem the "on" macro. Macro is set up on the main page "on" button, the "on" button on the other devices executes the same macro via punch through.

Here's the problem.... 99% of the time everything goes fine. The other 1% of the time the remote will hang up on the "please wait" screen. It stays that way until the remote's batteries die, or you reset the remote by pulling the batteries and reinstalling.

It happened on one remote so we figured it was a defective unit, we replaced it and the problem repeated on the replacement. Now we have the same issue on a second system. Very frustrating.

Anybody seen this?

Have done 5-6 780s this year, all using a variable that sends user to a Please Wait screen anytime the TV has to power up.

Have not seen this problem or had any reports of such from customers. In one case I was testing the remote and system and turning the system on and off dozens of times...for a good 2 months at my house before it was installed.

I would send my file into URC right away and see if they can duplicate the problem. It should be easy for them considering all they need is a remote and your file.

For what its worth, anytime I have had anomiles with URC it usually comes back with a corrupt device in the system. Once I almost pulled my hair out...had to completely re-write a large program from scratch, testing along the way, and it did fix it, although the problems were not intermittent like yours they were steady. The problem program was very large one that I attempted to copy and tailor to a new customer to save time.. Seemed like there must have been too much remnants of something (after alot of deleting things) seemed to make the program "dirty" even though it looked good and tidy on the surface.

I only did one MX780 and have the issue of the remote hanging up.
Can you press any other button, or is the remote completely frozen?

I don't have details of what function causes the hangups, but I purchased another 780 just to test.

I also had issues where Denon AVR3313CI codes from DB didn't work, at all.
I had to use the xx11 codes to get things going.

I had a similarly manifesting issue with a Marantz RC5200 for which I never found an answer. This one was worse -- some time between one week and six months after programming the remote, it would revert to no program. I never could work out what was wrong, but several of us suspected some commands had been learned in a squirrely way that affected the remote. You may have a similar problem.

I relearned and relearned, never solving the problem until I changed the remote to a newer version that used different logic chips and different software, and so, in a completely random manner, was not susceptible to the problem. Which is still there.

I'll be you have a strangely learned command in the remote. First thing I would do is relearn the commands for the products that are involved in that macro. It's a complete balls-out sin that URC's sotwere doesn't let you look at the hex code here. There's software we could use to take learned codes, deduce their base information, and create perfect codes with zero errors or squirrelicity. You could always get an old Pronto, squirt the codes via IR out of the URC, learn them on the Pronto, then investigate from there, but that's another opportunity for a bad learn.

Best of luck. This is a killer.

Just a thought. Make sure you check all the macros and make sure that you have it jumping to the please wait page first and then to your device page. because if the please wait is second on the list, you will have this problem. it's a common mistake i've done if you cut and paste macros.

yes, I'm aware of the macro order. Checked it and all is good.

The issue I'm having is just like the one you describe, only it happens only 1% of the time.... Works without a problem the other 99% of the time.

So, some troubleshooting: what was the client doing when it froze? It's hard to get them to notice because all they care about is that the thing quit, and the page it came from might be important.

But first it's helpful to know whether the thing failed on a punchthrough, direct command, or both.

You should rotate through all the possibilities, trying each macro with a wait screen from each different input. Maybe it's when you choose the Ski Lift input after being on Rollerskates that is locks up, and they rarely use that combination. Say they have a cassette player and cassette to OFF kills the remote. Or cassette to DVD. Like that.

I just experienced the, "Please Wait" issue. It disappeared when the batteries were removed and reinstalled.

Are you using a variable? Is it attached to the power state of a particular component?

Whoops. I didn't realize how old this thread was.

Crazy this just popped up during training session for a two year old system.