X10 Community Forum

🖥️ActiveHome Pro => ActiveHome Pro General => Help & Troubleshooting => Topic started by: george skarpelos on February 12, 2005, 08:02:07 PM

Title: Win 2K Machine Stopped Recognizing the CM15A
Post by: george skarpelos on February 12, 2005, 08:02:07 PM

My WIN2K machine stopped recognizing the
CM15A. The USB port is working since it will
see other USB devices correctly. Whenever I
plug the CM15A the device manager does not
recognize the device. I have rebooted
numerous times and it still doesn't resolve
the issue. Is there a special USB driver that
I can use?

Title: Re: Win 2K Machine Stopped Recognizing the CM15A
Post by: joe s. on February 12, 2005, 08:31:00 PM

This is a common failure - many can restore
the USB connection by:
1) unplug the CM15a from the wall
2) unplug the USB from the Cm15a
3) extract the batteries

- after 10 seconds or so - reverse the steps
and reload it all over.

Title: Re: Win 2K Machine Stopped Recognizing the CM15A
Post by: roger1818 on February 12, 2005, 09:26:14 PM

I agree with Joe (though I suggest removing
the batteries first and installing them
again last).  I never had this problem
until I upgraded to 3.179.  Now I get it
every day or two.

Title: Re: Win 2K Machine Stopped Recognizing the CM15A
Post by: X10 Pro on February 14, 2005, 01:39:54 PM

George Skarpelos: Please send an e-mail to
ahpsupport@x10.com.

Title: Re: Win 2K Machine Stopped Recognizing the CM15A
Post by: kvarley on March 16, 2007, 08:59:02 PM

The battery removal and re-install fix also worked for my problem.  In my case, the CM15A stopped working entirely.  It would not send pre-programmed timer commands, and Win2K saw it as a new, unknown USB device.  The AHP program reported that the interface was not connected.  After unplugging the USB cable, unplugging the CM15A from the outlet, removing the batteries, re-installing the batteries, plugging the CM15A into the outlet and re-connecting the USB cable, everything worked normally.  Win2K did not report a new unknown USB device and the AHP program recognized the interface.  I re-loaded the timers just to be sure.  I was then able to control all my modules from the AHP program.  Only time will tell if the timers work and keep working.