CM15a Stops working after a while

macdots · November 05, 2010, 02:38:53 PM

Hi,
I recently purchased a CM15a and have it programmed to control two lamps as a test setup. The CM15a stops working after a day or so. It won't respond to commands from the palm remote and is not recognized by the computer when I plug it in by USB. I have to do a reset by unplugging and removing the batteries. It is then recognized by the computer and becomes functional once again. This has happened 3 times in the last 4 days.
Any troubleshooting tips would be appreciated.
Thank you.

Brandt · November 05, 2010, 02:44:48 PM

Does a computer going into sleep/suspend affect a cm15a?

macdots · November 05, 2010, 02:52:35 PM

I don't have the CM15a connected to the computer. I program it and then disconnect it from the computer and it is runs independently.

Brian H · November 05, 2010, 02:54:16 PM

Was the CM15A new or certified like new?
Is there a small white dot on it with a Date Code?

macdots · November 05, 2010, 02:58:28 PM

It was certified like new. I'll have to check on the "small white dot on it with a Date Code" and get back to you. Are certified like new boxes known to have some issues ?

Brian H · November 05, 2010, 03:09:54 PM

Most reports are certified like new items are fine. Some say they appear to be new.
Though if it takes a few days to act up. I guess it would be possible a hidden problem was missed.

macdots · November 05, 2010, 05:30:53 PM

Hi Brian,
Yes there is a small white sticker on it with what seems like a date code on it. What's the implication?

Brian H · November 05, 2010, 06:17:49 PM

I was just wondering about when it was made.
Not that we have inside information on any changes over the years.

HA Dave · November 06, 2010, 09:54:37 AM

Quote from: Brian H on November 05, 2010, 03:09:54 PM
I guess it would be possible a hidden problem was missed.

I am wondering if the problem could be with a marco that puts the CM15A in a loop. I've done that myself.

macdots · November 07, 2010, 11:57:44 AM

Not much chance of that. I'm not running any macros. Just a few timer commands for each of the units.Is there some debugging I can do to see what is leading to the unit shutting down? One thing I noticed that if I look at the log file after failure, it has some unrecognized RF commands. These are the result of some button presses on the palm remote that should have been recognized.

News:

CM15a Stops working after a while