X10 Community Forum
🖥️ActiveHome Pro => ActiveHome Pro General => Help & Troubleshooting => Topic started by: oneeye on August 05, 2006, 07:17:33 PM
-
I just hooked up a CM15A with Active Home Pro. everything looked good untill I sent a command to turn on a module on house code N, the CM15A started sending RF M8 Off signals constantly
I unplugged every module in the house removed batteries from all palm pads and left only the CM15A plugged in and the RF M8 Off signal still continuasly transmits.
Has anyone else had such an experience? If so how did they fix it?
-
Well you may want to try the reset trick that some have used when their cm15a goes crazy.
Unplug from power and the USB cable
Remove Batteries
Wait a minute
Reinstall batteries
plug in
reconnect USB
download all your timers.
-
Tried that, even left it unplugged without batteries 24 hours. Same results.
-
Not positive if this is CM15A or x10nets.exe causing the prob, I notice the memory being used by x10nets.exe growing real fast and never being freed while it is sending the RF M8 Off command
-
Oneeye,
When you say you "sent a command...", how did you send it? Did you click something in AHP? Did you press a button on a remote? Did you send a command with a program other than AHP?
Also, what version of AHP do you have installed?
Specifics REALLY HELP to find an answer.
-
I have tried sending with ahp by clicking a module both ways off or on, and a palmpad remote to turn on a module and a plug in controller.
The version of ahp is 3.204
My replacement x10 devices arrived today so I have even replaced every device in the house except the cm15a
-
Much better! :)
What happens if you unplug the CM15A from the wall (but not the computer) and send that "N whatever" command?
-
the same thing happens.
-
Go into AHP and under "Tools" - "Hardware Configuration..." - "Transceived House Code(s)" (lower right on mine) click the circle by "Specific" and then clear the check box by "M".
Then, click the "Update Interface" button.
Once the changes have been sent to the interface, see if you still have the problem.
-
Same problem.
-
On the same setup screen, is the "Monitored House Code" set to "M"?
-
No the monitored house code is N which is what my house code is
-
I have tried none, auto and specified for Transceived House Code(s)
-
*Stumped* ???
The best I can tell you is I'm using AHP Version 3.203 and although I haven't noticed that problem with it, I did notice a similar (though not as drastic) problem when I wrote a control program with the SDK that monitored the received RF codes.
Whenever an RF code was transmitted, the monitor reported the correct device and command, but then also showed 1 or 2 RF commands (that had never been sent) on similar but slightly different House/Unit codes.
I think it's a software glitch.
-
I am experiencing a similar problem. For some reason when the camera F3 is shut off through a macro, the AHP send s multiple F3 OFF commands. A second problem I am seeing is that these multiple F3 OFF seem to turn off the camera F1 right after it gets activated from the same macro. I solved the problem with a new macro which is triggered by F3 OFF and it simply turns F1 back on. After reading these posts, I am going to reset the AHP with the steps described by Brian H.
-
ok now I feel real stupid. I unpacked the box my x10 cameras were in and found a remote set to house code m and pulled it from the box and the problem went away. The cameras have been packed away for over a year since we moved. I installed a cctv system in the new house and forgot about the x10 cameras.
Thanks for all the help.
-
WOW good batteries in that sucker. ::) Glad you found that unique trouble maker.
-
WOW good batteries in that sucker. ::) Glad you found that unique trouble maker.
We all know the remote's range would of been about 10 ft if he had been trying to use it. ;)
-
Actually the range was about 5 feet. The cm15a wason one side of desk the box was on the other side of desk. The batterries did last a long time. But I moved the box into the office a week ago and I would bet something in the box shifted and started hitting the button.
-
An important lesson for all! ;D
It's not always X10's bad software / hardware! :o :P