Author |
|
TonyNo Moderator Group
Joined: December 05 2001 Location: United States
Online Status: Offline Posts: 2889
|
Posted: June 29 2007 at 11:55 | IP Logged
|
|
|
Dave,
Oops! Thanks for the pointer!
You know, the board did not flag this thread as updated this morning when I logged on. I've noticed this before with other threads.
I await the UDP docs with baited breath! I've already been monitoring the broadcasts. Very interesting!
|
Back to Top |
|
|
MrGibbage Super User
Joined: October 23 2006 Location: United States
Online Status: Offline Posts: 513
|
Posted: June 29 2007 at 13:03 | IP Logged
|
|
|
Dave, I have the Elk trigger working--thanks for the help. One more question. The trigger seems to fire every minute and poll the current arm status, rather than have instantaneous response to changes in arming status. Once a minute would be fine, but I was hoping to do some things based on the exit delay, which is only 30 seconds or so, therefore the exit delay variable may not have been set yet. Is there a way to decrease the polling interval, or have PH know instantly when the arming status changes? Perhaps I've set something up incorrectly???
Skip
|
Back to Top |
|
|
MrGibbage Super User
Joined: October 23 2006 Location: United States
Online Status: Offline Posts: 513
|
Posted: June 29 2007 at 14:22 | IP Logged
|
|
|
*&*%$#@!!! I'm so stupid. The every minute update was happening because I used an old macro that was on a one-minute timer.... **sigh**
I have set up a trigger as you described, and it never fires though. No amount of arming or disarming has made this thing fire.
I'm quite certain that I have something set up incorrectly somewhere.
Skip
|
Back to Top |
|
|
MrGibbage Super User
Joined: October 23 2006 Location: United States
Online Status: Offline Posts: 513
|
Posted: June 29 2007 at 17:37 | IP Logged
|
|
|
SOLVED. I needed to enable global option 35 on the Elk.
Edited by MrGibbage - June 29 2007 at 17:37
|
Back to Top |
|
|
dhoward Admin Group
Joined: June 29 2001 Location: United States
Online Status: Offline Posts: 4447
|
Posted: June 29 2007 at 23:51 | IP Logged
|
|
|
Skip,
Excellent. I read your first post and knew it had to be something such as a macro or timed event since Elk module doesnt do any polling except for the analog inputs.
Glad to hear though that you figured out about option 35. I may not have remembered that one myself.
Dave.
|
Back to Top |
|
|
Manny Senior Member
Joined: March 23 2003 Location: United States
Online Status: Offline Posts: 172
|
Posted: June 30 2007 at 16:30 | IP Logged
|
|
|
This is great
I'm renaming my PC after you.
Sure beats naming it HAL
|
Back to Top |
|
|
guerrand Senior Member
Joined: December 18 2005 Location: United States
Online Status: Offline Posts: 106
|
Posted: July 02 2007 at 16:13 | IP Logged
|
|
|
dhoward wrote:
Beachbum / Wasdvd,
It looks like version 235 is probably the better choice. I defaulted the install to have 308 active, but will change it for the next go around.
Also...version 11 has both SDM 235 and SDM 308. For those that havent figured out how to switch, navigate to the Device Manager directory beneath the PowerHome directory. You'll see a coupld of BAT files, 235.bat and 308.bat. Shut PowerHome down and make sure that the SDM is shutdown as well and then just run the BAT file for the version you want. After changing versions, manually launch the SDM3.exe, let it start and connect to PLC, and then shut it down before launching PowerHome. This insures that everything is registered properly
Also, the multiple SDM problem is caused by this as well. I need to make a note that after upgrading, before launching PowerHome, manually launch the SDM3.exe file, connect, and close (as above) before launching PowerHome. This will keep multiple copies from launching.
Glad to hear that everything is performing well otherwise.
Dave.
|
|
|
Before I switched to 235 the insteon was spazzing out. In the insteon explorer log window it was doing a never ending loop of "getlinks" downloads, none of which ever seemed to complete correctly. This has that cleared up. It also seems to have no trouble reconnecting after a reboot. I was having intermittent trouble with having a mapnotloaded problem. All seems to be in order now though.
__________________ VuMe
|
Back to Top |
|
|
MrGibbage Super User
Joined: October 23 2006 Location: United States
Online Status: Offline Posts: 513
|
Posted: July 02 2007 at 20:55 | IP Logged
|
|
|
For the next EQOTD (that's "Elk Question Of The Day"), I am trying to figure out the messages that are sent from the Elk to PH. Looking over the Elk help page, I see that there are several messages that can fire PH triggers, including valid user codes, arm status messages, key pad changes, etc. Most require certain global variables set on the Elk. Looking through the Elk RS232 manual gives a lot of additional help as well. But here's what I am trying to figure out. Right now I have two Elk triggers set up, namely Elk Arm status messages, and Valid user codes. I have those set up on Command 5 and 4 respectively, option 1 for both (Dave, is there anything significant about what command number each of these messages end up with? Just wondering.) But I see that my valid user code trigger gets fired every time I press one of my F-keys. I do currently have global option 40 set to send those key presses, but I am not looking for that trigger, so I'm not sure why it would be firing. Also, according to the Elk RS232 manual, there should be data returned in the IC message. Where is it stored in PH?
Dave, one last request. I looked through the RS232 manual and don't see any provision for setting global options over the RS232, so I don't think it is possible, but it would be really cool to be able to have PH change the volume of the voice announcements, for instance. Obviously it is possible, because it is done with ElkRP, but it is probably proprietary.
Edited by MrGibbage - July 02 2007 at 20:57
|
Back to Top |
|
|
seattlechris Groupie
Joined: June 29 2002 Location: United States
Online Status: Offline Posts: 49
|
Posted: July 04 2007 at 16:18 | IP Logged
|
|
|
Has anyone successfully used the COM control (serial port) functions in this new beta? My caller ID function causes powerhome and sometimes even windows to freeze up, but it works fine if I disable the com control functions (which prevents caller ID functionality). This could easily be unrelated to powerhome because I'm using a new modem.
|
Back to Top |
|
|
TonyNo Moderator Group
Joined: December 05 2001 Location: United States
Online Status: Offline Posts: 2889
|
Posted: July 04 2007 at 17:08 | IP Logged
|
|
|
In checking your serial issue, I found, for the second time, the SDM hung and PH hung saying it was restarting the SDM. The count-down timer was stuck at 5 and the button did not work. After filling out the SDM error email info, PH came back. Still trying to restart the SDM with no success...
ProgressStart
ProgressMax=1024
Progress=0%,0,1024
ProgressError=0%,0,1024
ProgressError=0%,0,1024
ProgressError=0%,0,1024
ProgressEnd=False
This kept scrolling by for a few minutes, then it worked.
Now that that's out of the way...
Yup, my CID still works.
|
Back to Top |
|
|
nadler Super User
Joined: February 25 2006 Location: United States
Online Status: Offline Posts: 354
|
Posted: July 04 2007 at 19:12 | IP Logged
|
|
|
I MIGHT be having a similar issue to seattlechris. I run a CID reinitialization macro every hour just to make sure the Com port is listening. I think TonyNo runs a similar macro. It runs at :17 minutes after the hour. At 6:17 am PH closed. When I noticed that it wasn't running later in the morning there were absolutely no error messages just a closed PH. The event log showed the last macro to run was the CID setup (reinitialization) macro. BUT, this macro runs once every hour and had run at least 23 times before this shut down with no problem. So, I turned off the reinitialization macro to see what happens. It also may no longer be necessary. CID worked the rest of the day.
|
Back to Top |
|
|
bhlonewolf Senior Member
Joined: March 29 2007
Online Status: Offline Posts: 198
|
Posted: July 04 2007 at 21:58 | IP Logged
|
|
|
Hmmm ... I've had a few mysterious crashes w/ the latest PH ... nothing I can repro quite yet. (On W2k3 Server)
|
Back to Top |
|
|
MrGibbage Super User
Joined: October 23 2006 Location: United States
Online Status: Offline Posts: 513
|
Posted: July 05 2007 at 16:25 | IP Logged
|
|
|
Right now, my most common problem is PH forgetting that it is connected via serial port to the Elk. I'll notice that all of a sudden, things aren't working. Check the file menu and see that "what do you know?", the Controller is disconnected. If I try to connect the controller, I get this message:
A critical error occurred at 2007-07-05 16:23:08.828.
PowerHome Version: 1.03.4.11
Error Number: 39
Error Message: Error accessing external object property commport at line 32 in function f_controllerconnect of object uo_controller_elkm1.
Window: uo_controller_elkm1
Object: uo_controller_elkm1
Event: f_controllerconnect
Line: 32
I can then close PH and fire up ElkRP and it works fine, so it's not the computer or a cable or something wrong with the Elk. I then have to restart PH a few times, and eventually it takes. Strange.
Skip
|
Back to Top |
|
|
MrGibbage Super User
Joined: October 23 2006 Location: United States
Online Status: Offline Posts: 513
|
Posted: July 05 2007 at 16:31 | IP Logged
|
|
|
Also, trying to re-initialize PH is a guaranteed lock-up for me. I always have to shut PH down and restart it, or worse, reboot. Whenever I try to re-initialize, it looks like everything is going great, see the SDM stop and restart, but the red message box that say "PowerHome is reinitializing. Please wait..." never goes away.
Skip
|
Back to Top |
|
|
bhlonewolf Senior Member
Joined: March 29 2007
Online Status: Offline Posts: 198
|
Posted: July 05 2007 at 16:54 | IP Logged
|
|
|
Ah poop.
3rd crash in 3 days -- dialog box that says:
The exception Breakpoint
A Breakpoint has been reached.
(0x80000003) occurred in the application at location 0x10daa9dc.
OK to terminate/cancel to debug.
|
Back to Top |
|
|
MrGibbage Super User
Joined: October 23 2006 Location: United States
Online Status: Offline Posts: 513
|
Posted: July 05 2007 at 20:02 | IP Logged
|
|
|
And now I'm getting a "System is seriously low on virtual memory" WinDoze error. It seems to be related to when I edit a certain macro. **sigh**
|
Back to Top |
|
|
TonyNo Moderator Group
Joined: December 05 2001 Location: United States
Online Status: Offline Posts: 2889
|
Posted: July 05 2007 at 21:00 | IP Logged
|
|
|
Skip, now that you mention it, I've been seeing this, too.
|
Back to Top |
|
|
Dean Senior Member
Joined: August 21 2003 Location: United States
Online Status: Offline Posts: 109
|
Posted: July 06 2007 at 01:11 | IP Logged
|
|
|
Yeah, my W2K3 server has been crashing and rebooting about once a day since I installed the latest PowerHome. Crashes with both versions of the SDM included in the latest PH beta. At the moment, PowerHome has my W2K3 server so screwed up I can't close down PowerHome and I can't even reboot my server, no matter what I do. Looks like a walk to my basement to press the reset button is in order. I can see the PH icon on my task bar in the lower-right of Windows, but I can't access it. I was able to shut the SDM and SQL server down though.
bhlonewolf wrote:
Hmmm ... I've had a few mysterious crashes w/ the latest PH ... nothing I can repro quite yet. (On W2k3 Server) |
|
|
|
Back to Top |
|
|
Dean Senior Member
Joined: August 21 2003 Location: United States
Online Status: Offline Posts: 109
|
Posted: July 06 2007 at 09:51 | IP Logged
|
|
|
Dave,
What is the NT port library driver? I tried uninstalling the .11 version of PH and it could not uninstall the NT Port Library Driver. Is this something new you have in .11? Is it from this company: http://www.zealsoftstudio.com/ntport/?
I'm going back to .9 (I never went to .10) to see if my W2K3 crashing and rebooting goes away. I'll let you know.
-Dean
|
Back to Top |
|
|
dhoward Admin Group
Joined: June 29 2001 Location: United States
Online Status: Offline Posts: 4447
|
Posted: July 06 2007 at 13:53 | IP Logged
|
|
|
Just wanted to give everyone a quick note that Ive sent the latest PowerBuilder runtimes to some brave souls for alpha testing.
Hopefully in a day or so, we'll know if they have any effect on the current instability issues.
Dave.
|
Back to Top |
|
|