X10 Community Forum
🖥️ActiveHome Pro => ActiveHome Pro General => Topic started by: jagMan653 on January 05, 2019, 08:17:02 PM
-
Today I connect my new CM15A and downloaded and installedAHP 3.318. Everything went smoothly through the tests ... Appliance module neatly switching on and off etc. Then I created my Rooms, modules, etc. and set some timers, and saved the file to my HD. Then I made a few edits like renaming modules saved it again. At some point things stopped responding, and I discovered the "Interface not connected" message. Searching the forum I found reports of this problem, along with a fix... unplug the CM15A, remove & replace the batteries, and reconnect. No joy.
Any suggestions?
-
Have you tried rebooting the PC?
-
Today I connect my new CM15A and downloaded and installedAHP 3.318. Everything went smoothly through the tests ... Appliance module neatly switching on and off etc. Then I created my Rooms, modules, etc. and set some timers, and saved the file to my HD. Then I made a few edits like renaming modules saved it again. At some point things stopped responding, and I discovered the "Interface not connected" message. Searching the forum I found reports of this problem, along with a fix... unplug the CM15A, remove & replace the batteries, and reconnect. No joy.
Any suggestions?
The "unplug the CM15A, remove & replace the batteries, and reconnect" is a standard procedure.
Then I made a few edits like renaming modules saved it again. At some point things stopped responding
I never had much luck with such "edits". I have to delete a module (empty the trash/recycle bin... don't upload with trash in the trash bin) and create new module, room, macro, timer, etc.).
I'd start over with a proper naming protocol. I use year 19 month 1, day 5... then any revisions on the day 5 would be A,B,C, etc..
Create your first nice working macro name it 190105 and save it to the CM15A for testing.never edit or modify that file. Next create another macro, timer, room modules whatever and name it 190105A. So any screw ups only lose the very last file.... where the error occurred.
-
Have you tried rebooting the PC?
No. Is that a known issue or "on general principles?"
BTW, I'm using a Windows 10 machine. Tomorrow I'll try it on a Windows 7 machine.
-
I never had much luck with such "edits". I have to delete a module (empty the trash/recycle bin... don't upload with trash in the trash bin) and create new module, room, macro, timer, etc.).
I'd start over with a proper naming protocol. I use year 19 month 1, day 5... then any revisions on the day 5 would be A,B,C, etc..
Create your first nice working macro name it 190105 and save it to the CM15A for testing.never edit or modify that file. Next create another macro, timer, room modules whatever and name it 190105A. So any screw ups only lose the very last file.... where the error occurred.
Thanks. I'll try starting over.
Has anyone used this version with Windows 10?
-
…. Has anyone used this version with Windows 10?
I am pretty sure I've read here of people using windows 10. I have the software install on a couple XP's and a Visa.
-
Have you tried rebooting the PC?
No. Is that a known issue or "on general principles?"
BTW, I'm using a Windows 10 machine. Tomorrow I'll try it on a Windows 7 machine.
Sometimes the the USB ports get finnicky. I had some problems once where a reboot of the PC got things working again with the CM15 pluuged in before booting.
-
The mystery deepens. I installed 3.318 on my Windows 7 machine today. I was able to do the test with MyRoom and successfully turn a lamp on and off. (Full disclosure: having no working Lamp modules, I added a 3-prong Appliance module in place of the lamp module). I put a timer on it, and it worked. However, the "Interface not connected" icon soon appeared, just as it did on my Windows 10 machine. Tried uninstalling and reinstalling 3.318, nut no joy. So, I now have TWO computers that can't detect the CM15A!
The unplug R/R batteries fix did nothing.
What am I missing?
-
The mystery deepens. I installed 3.318 on my Windows 7 machine today...... the "Interface not connected" icon soon appeared.....................So, I now have TWO computers that can't detect the CM15A!
A mystery it is! I even did a search.... a forum search... and found nothing that appeared useful. Most of the old CM15A problem were just the same old problems.... over-and-over. I did find a link for Windows 8, Windows 7, Vista, XP X10 drivers (https://www.x10.com/activehome.html) (that might be helpful). And of course.... try another USB cable.
-
Thanks, Dave. Haven't tried a different cable. i think I have one like that around here somewhere. But, it seems unlikely to be the problem since it did connect the first time on the Win 7 machine, as it did on the Win10 machine.
BTW, I still have my MT10A Mini Timer connected. Could that be an issue?
-
Sounds like a Driver problem.
You might try uninstalling the driver. And re-install.
On Win 10, right click on Start > Computer Management > System Tools > Devices > Universal Serial Bus controllers. find the X10 drivers and uninstall. Reboot with CM15 plugged in. Win 10 should find new driver.
-
windows driver updates have messed with the USB connection since XP if your machines are set to auto update this is most likely what has caused the issue.
You need to tell windows to not auto update drivers and ask you first.
-
Since it work the first time on two different machine running different Windows versions, it's hard to believe it's a MS driver that got switched out.
Not sure I'm ready to tell Windows not to update things.
-
Windows can't update a driver that isn't installed.
I merely stated an observation one of which I myself experienced several times using XP and a couple of times in Win 7
-
Success on Windows 10! Not sure, but I think what fixed it was uninstalling it and running the installer again, selecting C:\ as the location of ActiveHome Pro.
BTW, all these changes in my X10 system were precipitated by gradual degradation of "controlability," i.e., things would turn on but not off, etc., probably due to added devices around the house. The biggest change was installation of an XTB-IIR. That required installation of a 240V outlet to allow boosting the signal and inserting it into both phases. That cost $365. The XTB-IIR was $200. Then shipwright's disease set in, resulting in buying the CB15A. Pretty expensive just to control a few lights around the house and yard! Then on top of all that was bothering everyone here with all my stumbling about.
Thanks to all.
-
Glad you got it sorted! :)% You'll be very pleased with the XTB-IIR as it will solve most if not all of your signal problems. When something will turn on but not off it's likely because what was turned on is causing the problem. It is quite likely an LED bulb misbehaving. In the event that still happens, a filter or hash choke will solve the problem. Read http://jvde.us/x10/x10_cfl.pdf
-
I remember some threads here. Indicating the programs location in Windows 10. Made a difference on its operation.
-
Yes, I read that too and it was one of the things I eventually did. Now the ActiveHome Pro folder is at C:\.
The order of doing things is also important. This point was driven home for me when I finally got my Windows 10 machine to to recognize the CM15A interface. The very last thing I did before it worked was plugging in the USB cable. Rather than intentional, this was by accident.
I had been trying to make it work on my Win 7 machine without success. Then I switched back to the Win 10 machine, uninstalled AHP, and reinstalled it at C:\. It still didn't recognize the interface. Then I realized I had forgotten to switch the cable back to the Win 10 machine. When I plugged it in, the Interface was recognized! This should be no surprise, since the the CM15A instructions says to install the AHP software before plugging in the interface.
-
This should be no surprise, since the the CM15A instructions says to install the AHP software before plugging in the interface.
Yes, that's critical and typical of most devices that have their own software/driver packages - not unique to X10. If you plug in the device first it'll get a driver from Windows instead of the needed one from the installed software. I've bought other devices that have a big red stickers covering the USB plug with a STOP sign saying not to plug it in till the s/w is installed.
-
I agree, requiring software installation before hardware has been with us for a very long time. And I did so with AHP. What perhaps happened here, though, is when I uninstalled AHP and reinstalled in C:\ the CM15A was already plugged in and configured to look for things in the original installation folder. I think if someone wanted to relocate AHP the procedure should be (a) unplug the CM15A, (b) uninstall/reinstall AHP, (c) plug in CM15A.