| Author |
|
bmil
Newbie
Joined: April 03 2006
Location: United States
Online Status: Offline
Posts: 13
|
| Posted: April 03 2006 at 22:43 | IP Logged
|
|
|
Installing PowerHome for the first time and can't get past setting up my 2814UB as the Insteon controller.
Followed instructions in phinsteon document up to the point where I have to select "download core app" from the Insteon Device Manager Control window. When selected, it indicates "Downloading Core App, please wait..." That's where the program appears to stop responding (left it for over an hour).
Since that particular window has no window controls to close it, I eventually had to end PowerHome from the Task Manager.
I tried several more times and even tried removing and reinstalling PowerHome (now I even started getting a page fault error when shutting down PowerHome).
The SDM log shows the PLC status query going through OK but then a whole bunch of "the application called for an interface that was marshalled for another thread."
Later, I installed SmartHome's Essential Timer App. that comes with the 2814UB and it worked with the PLC with no problems.
Any help greatly appreciated as I'm dying to get PH up and running. Thanks all...
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: April 04 2006 at 18:01 | IP Logged
|
|
|
Bmil,
Sorry to hear that you're having such problems, but hopefully we can work through them.
Make sure that you've got a clean install of PowerHome. Don't install on top of itself. Rename the current directory if necessary and reinstall into a fresh location.
With that done, launch PowerHome. The SDM should automatically launch and will appear as a yellow "T" in your system tray. Click on that icon to bring the SDM window up. Check the title and make sure that it's version 163. Go into the "Insteon DM Control" screen and try downloading the core application again. Switch over to the SDM and watch the screen. You should see a lot of "Progress" messages counting up to 100% (the last number on each line should be 4165) followed by the progress messages starting over and going up to 100% a second time. There will be a couple more messages following but control should be returned to PowerHome.
The error message you're getting sounds as if the SDM is being used by another application and PowerHome cant get control. Make sure that the SDM is not already running when launching PowerHome. You can use the "Task Manager" to search for "SDM3.exe".
If it still does it, copy and paste the SDM (or email) logs for me so I can try to analyze the problem.
Thanks,
Dave.
|
| Back to Top |
|
| |
bmil
Newbie
Joined: April 03 2006
Location: United States
Online Status: Offline
Posts: 13
|
| Posted: April 05 2006 at 00:43 | IP Logged
|
|
|
Thanks for responding Dave..
OK, I did a clean install in a new location. Defined a new Insteon DM controller in Setup,Controllers and exited PowerHome.
(By the way, PowerHome exited normally with no error).
I Verified SDM was not running before restarting PowerHome. Restarted PowerHome..
PowerHome started up with no problems and it started up the SDM along with it.
Before doing anything else in PowerHome I brought up the SDM window and found the following:
downloadTimer started
timerActivate enabled
SDM:DM=active,1.01.26.163,4/4/06 10:34:07 PM,responded,00.D5.1C,2.12
UIERR:OnDMIsReadyChange: The application called an interface that was marshalled for a different thread
UIERR:OnText: The application called an interface that was marshalled for a different thread
ui:getplcstatus
PLC:getPLCstatus=beginlist
port=USB4
connected=True
firmware=2.12
id=00.D5.1C
devicetype=InsteonPLC-USB
lastErrorMsg=#0:
endlist
UIERR:OnText: The application called an interface that was marshalled for a different thread
I got the same results when again attempting to download the core app. The SDM log showed all the progress lines you mentioned but between each progress line was that "The application called an interface that was marshalled for a different thread" error message.
By the way, I watched the progress lines in the SDM go from 1-100% (with the error lines in between) then a second time from 1% up to 75% where it stopped displaying any more progress lines for over 5 minutes. That's where I aborted it from Task Manager.
When I had to abort PowerHome again from Task Manager I got a pwrhome caused an invalid page fault in module<unknown> error.
Now, any attempt to restart PowerHome, the opening logo appears but locks up right away at "connecting to database"..
Aborting it from Task Manager generates an error message and then pops up the "ODBC Configuration for Adaptive Server Anywhere" dialog box.
Sorry for all the nightmares and your help is really appreciated..
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: April 05 2006 at 22:51 | IP Logged
|
|
|
Definately wierd. Im not sure what else to try at this point except possibly a new version of the SDM. Try deleting the SmartHome directory beneath the PowerHome directory (default: c:\program files\powerhome\smarthome). Then download and unzip this file http://www.power-home.com/download/sdm191.zip.
Install it in the same location as the old SmartHome directory (beneath PowerHome).
Give this a try and see where it gets us.
Dave.
|
| Back to Top |
|
| |
bmil
Newbie
Joined: April 03 2006
Location: United States
Online Status: Offline
Posts: 13
|
| Posted: April 07 2006 at 13:10 | IP Logged
|
|
|
Gave it a shot Dave but didn't even get as far as when using 163.
- Uninstalled Powerhome completely and deleted the remaining Powerhome subdir.
- Reinstalled Powerhome from scratch.
- Deleted powerhome\smarthome subdir and replaced it with the contents of sdm191.zip.
- Started PH and setup controller. Exited PH.
- Restarted PH.. PH began to load but I then got an error window from SDM itself. I will email you SDM3_Error.zip containing a screen capture of the error window.
Just for the heck of it I tried having SDM3 running *before* starting PH (after controller had already been defined in PH)...
- Started up SDM3. No errors in SDM log window.
- Started up PH. Seemed to load ok.
- Told PH to download core app.
PH still locked up at this point but watching the SDM log window, this time there was only one instance of the "the application called an interface.." error. This error did not appear between each of the "progress xx%" entries in the SDM log as it did when I used v163. I will email you SDM191_log.txt.
Becoming desperate to try anything I decided to replace the 2814U USB with a serial 2414S I also had.
- I uninstalled PH completely again and reinstalled it. I did not replace the smarthome 163 subdir contents this time.
- Ran PH and setup the controller. Exited PH.
- Restarted PH. Got the error msg. that the PLC wasn't responding.
- Exited from PH. Followed phinsteon instructions to tell SDM to use COM1. SDM found it correctly as described in phinsteon.
- When I restarted PH I immediately got a window for "ODBC Configuration for Adaptive Server Anywhere". I hit cancel in the window and it prompted "name is required for the data source". Hitting OK exited the window, aborted PH and left the error msg "Database connection error 100, No Data was found to satisfy the request".
Since others don't seem to be having these problems I'm starting to think it's something with this particular PC setup. I'm using an old Win98SE machine I brought up here to my vacation home just to get some basic lighting control for security purposes. When I move up here full-time in about 6 months it will be replaced with a new maching or one of my XP machines from home.
If you can think of anything else to try Dave I'll be glad to give it another shot but I'm heading back home Sunday. If I can't get PH going by then I'll just use this Smarthome Essential timer software which seems to be working ok or give an Elk M1 I have sitting in the box a shot with it's very limited Insteon functionality. That will give me basic lighting security timers for now and I'll give PH another shot when I get a new machine up here.
Thanks for all your assistance. I'd really like to get PH going eventually..
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: April 07 2006 at 17:15 | IP Logged
|
|
|
Brian,
What a mess. But I think were making progress. Concerning the "ODBC Configuration"...whenever you get this type of error, it's usually because the Adaptive Server Anywhere is already running. What usually happens is that PowerHome had an error, it exits (or appears to) but residue is still running (you can see it in Task Manager as "pwrhome.exe") and it keeps the ASA running. When you launch it again, you'll get the above error. In this case, just exit PowerHome, open the Task Manager and kill the pwrhome.exe process. Watch your tray and you should see the ASA "SQL" icon disappear shortly. You'll then be safe to restart.
I checked out your logs and did some research on the web and no-one else has reported the "marshalling" problem with the SDM. It does appear to be a common problem with Windows applications and seems to have something to do with the way the code is compiled. Im starting to wonder if it has anything to do with Win98SE. If anyone is successfully using PowerHome and Insteon on Win98SE, please report back here, I would appreciate it.
That said, I tested the 191 on my machine here (XP) and didnt encounter any of your problems. Based upon the log you sent me, it appears that the "Download Core App" is completing successfully. Once you get past this, does it seem to work or does it still have problems (it doesnt look like it's locking up like previously)?
The Smarthome Essential timer software...does it use the SDM? You say it works Ok and if it uses the SDM, Im sure it installed in a different location. If it does use the SDM, I would try "copying" the directory structure from it's default location to beneath the PowerHome directory (rename the 191 location). You shouldnt have to keep uninstalling and reinstalling PowerHome either. That will get old real quick. Once you've copied the Essential Timer SDM to the PowerHome directory, manually launch it by double-clicking the SDM3.exe. If it does use the SDM, let me know what version it is. Try launching PowerHome and lets see if we still get the error.
The next thing we can try as well is an older version of the SDM. Version 146 is apparently stable and some uses are getting good results with it. If you want to try this route, you can download it from http://www.power-home.com/download/phsdm146.zip.
I appreciate all the effort in trying to get PowerHome working and hopefully we'll get this solved soon.
Let me know,
Dave.
|
| Back to Top |
|
| |
|
|
Active Topics 
Memberlist 
Search 
Help
Register 
Login
PowerHome Messageboard : PowerHome General
Topic: Install Problems - Insteon PLC Setup
