X10 Community Forum
🖥️ActiveHome Pro => ActiveHome Pro General => Help & Troubleshooting => Topic started by: schmuttis on February 02, 2011, 03:07:33 PM
-
I had AHP installed on two Windows 7 PCs.
I have the CM15A attached to my laptop and had AHP successfully working until I installed the AHSDK yesterday. Now when I go to start AHP, I get the message is it ok to allow AHP to make changes, then it crashes. I've rebooted and nothing helps.
On my second PC, a standard pc, I installed Vanguard Internet Control Center Software. Now when I try to start AHP on that pc, I immediately get a Windows message that AHP has stopped working. This also happened yesterday. I guess I should have given up after the first failure.
Does anyone have any idea how to fix these problems? Would it be best just to reinstall AHP or will I continue to have problems? If I reinstall, will my macros and timers be overwritten? Are there some files I should copy before reinstalling?
Thanks for your suggestions.
-
You might want to try re-installing AHP, making sure you get the latest version.
On the PC with the SDK, you need to make sure you have the latest version of the SDK, too.
-
I just checked that AHP was the most recent version yesterday and I downloaded AHSDK from the X10 site yesterday. They wouldn't have old versions posted would they?
-
Ok, then I'd suggest reinstalling AHP as a start.
For what it's worth, I get the "User Account Control" message whenever I start AHP on my Windows 7 PC.
-
Yes, I'm used to the Windows message. I just wanted to let you know that's all I get. On the other PC, I don't even get that.
Do I need to copy out files before I reinstall so my macros and timers aren't overwritten?
-
Make a backup copy of your AHX file. Put it in a safe place.
-
What version did you have install before you loaded the SDK?
Did you load the newest SDK?
There was a issue with loading the SDK that would stop AHP from working!
Is this the Case schmuttis ?
-
Noam - thanks for the info. Hopefully, I'll reinstall AHP tonight.
I don't know the answer to your question Tuicemen but I can tell you the following.
I can't open AHP so I can't confirm what exact number it is but I can tell you while in AHP yesterday I checked for new versions and was told I had the most recent. If I right click on activeHm.exe and check properties the file version/product version is 3.0.0.296.
The SDK I downloaded from here http://www.activehomepro.com/sdk/sdk-info.html (http://www.activehomepro.com/sdk/sdk-info.html) yesterday. The file version/product version of the various files are:
ahsdk_install.exe 1.0.0.0
ahscript_setup.exe 1.0.0.0
ahcmd.exe 3.0.0.305
ahscript.dll 3.0.0.305
activescript.exe 1.0.0.0
Do you have any other suggestions as to how to check the versions?
-
you might want to try this before you uninstall AHP
Go to Program files\common files\x10\common and delete the files then install AHP.
It will rewrite those files.
Since your not getting the error message
"Error Getting X10 net interface" A simple reinstall should work with those files removed.
>!
-
...while in AHP yesterday I checked for new versions and was told I had the most recent. If I right click on activeHm.exe and check properties the file version/product version is 3.0.0.296....
...The file version/product version of the various files are:
... ahscript.dll 3.0.0.305
Aha!
Looks like you had 3.296 before. The "Check for Updates" feature has been broken since version 3.228, so I'm not surprised that AHP couldn't find an update for you. The newest SDK that you installed broke the earlier AHP.
Download and install the newest AHP, 3.305, from here:
http://www.x10.com/support/support_soft1.htm
That should fix the issue with that PC.
Let us know how it goes.
-
Many thanks Noam. I'll download and install that tomorrow. Too many hours of shoveling ice cubes have me pooped out.
-
AHP is once again alive and kicking. Thank you all for your help - it was most appreciated!
-
AHP is once again alive and kicking. Thank you all for your help - it was most appreciated!
One thing about 3.305, you can't use your .ahx files from a previous version, they ALL have to be rebuilt. Non soft-start modules have to come from the "old style" modules or timers/macros won't work.
-
One thing about 3.305, you can't use your .ahx files from a previous version, they ALL have to be rebuilt. Non soft-start modules have to come from the "old style" modules or timers/macros won't work.
[/quote]
Not completely true Dan!
Only lamp modules need be reconfigured!
>!
-
One thing about 3.305, you can't use your .ahx files from a previous version, they ALL have to be rebuilt. Non soft-start modules have to come from the "old style" modules or timers/macros won't work.
Could you explain more? I have 2 aHP apps at 2 different locations and both seem to be working fine with 3.305 and my old files?
-
The "old modules" in 3.305 are for non-Soft-Start Lamp Modules and Wall Switches. The Lamps section is for soft-start modules and Wall Switches.
Understand?
-
The "old modules" in 3.305 are for non-Soft-Start Lamp Modules and Wall Switches. The Lamps section is for soft-start modules and Wall Switches.
Understand?
Sometime around 2007 or 2008, X10 decided to re-engineer the lamp modules and wall switches, but didn't change the model number. The newer ones are "SoftStart," (they slowly "ramp up" from an off state to full brightness, instead of instantly coming on at 100%), and can respond to "Extended Dim" commands.
Starting with version 3.302 of AHP, the newer, SoftStart modules are the default "Lamp Modules," and the older ones are in the "Old Lamps non-SoftStart" category. AHP will use "Extended Dim" codes to talk to those modules, but the older modules can't respond to those types of commands.
Therefore, if you have any lamp modules or wall switches that are of the older (pre 2007/8) vintage, they would have worked fine up until 3.302, but then not worked properly afterward, without re-defining them in AHP.
However, it seems that once you change the module type, everything starts working properly again.