Here's one that has me scratching my head.

In my latest config, I've got a pair of macros bound to my left and right buttons on my TSU-2000. One brings the level of my lights up, the other down, via a series of commands bound to a macro.

They work GREAT... most of the time.

However, if the screen is sleeping, and I press one of the buttons, the macro will activate, but then, I can't wake the screen up. I either need to hit the reset button, or, more likely the case because I'm too lazy to get off of my ass, I need to pop the battery pack for a few seconds, and reinsert it. Then it works.

Crazy, huh? Anyone else ever witness anything like this?

-ElvisBeefcake

That's a strange one... what devices/commands are doing this? Do you have beeps enabled?

No beeps enabled. The commands bound to the hard left and right buttons are simple macros which select codes a2 and a3, and then several dim or brighten commands in a row on my X10. These codes I downloaded from someone elses's CCF file.

It works fine if I tap the screen and wake it up, but locks after triggering the macro and executing it when the screen is sleeping. Its not a biggy, i just tap the screen before hitting it and all is good. It's just a quirk.

-ElvisBeefcake

Have you checked your Dilithium Crystals?


"Just an 'ANNOYING' Quirk"???!!!!!

WooHooooo!!!!!!!!

That's ME!!!!!!!


JTK

I had the same problem.

I had the lower hard buttons aliased to a series of X10 dim/brighten commands. However, in my case it would sometimes lock up even when I had the screen activated. I had to remove the batteries for a few seconds in order for the Pronto TSU2000 to respond again.

What seemed to happen was that the screen would turn off before the macro finished executing causing the Pronto to lockup.

The bug seems occur when the length of the macro being executed is longer than the timeout for the LCD.

I lengthened my LCD timeout value and the problem has gone away.

Do you have a relatively short LCD timeout? Try making it longer than the amount of time it takes the macro to execute.

-MikeJ

Actually, now that you mention it, I *DID* have it set relatively short, but recently I bought the charger and docking station and have the timeouts about 3 times as long as I did.

It doesn't happen much anymore, now. Instead of once or twice daily, as I sat there scratching my head, it happens maybe once a week if I accidentally hit the button while the screen is in sleep mode.

I'm glad to know it just isn't me that this has happened to :)

-ElvisBeefcake
www.beef-cake.com

Hmm. When this happen, does the macro run all the way, part way, not at all?

It runs all the way for me. It complete it ok.

Then its locked up hard.

-ElvisBeefcake

Yes, the macro did run all the way through.

After that, I would notice that the screen was blank. It would not turn back on until I removed the batteries for a few seconds.

-MikeJ