| Author |
|
RWCS
Senior Member
Joined: October 28 2002
Location: United States
Online Status: Offline
Posts: 102
|
| Posted: December 15 2005 at 17:19 | IP Logged
|
|
|
I have been getting these "Timeout communicating with X-10 controller" in recent weeks. I've changed controllers but it didn't change things. One sure way to get the system out of this mode is to unplug and reconnect the CM11A. These peroids of stupidity seem to occur at random times during the day. I have been unable to link it to any other event in the house. I can be assurted if some event fails to happen I'll check the log and there will be these "Time-Out" messages when the command was supposed to be sent. Anybody else have a CM-11A goes stupid problem, or know what causes it?
Bob 
|
| Back to Top |
|
| |
TonyNo
Moderator Group
Joined: December 05 2001
Location: United States
Online Status: Offline
Posts: 2889
|
| Posted: December 15 2005 at 18:05 | IP Logged
|
|
|
Could this be the old overheating problem?
|
| Back to Top |
|
| |
RWCS
Senior Member
Joined: October 28 2002
Location: United States
Online Status: Offline
Posts: 102
|
| Posted: December 15 2005 at 18:19 | IP Logged
|
|
|
Please tell me about "The Over Heating Problem", is there any info / fixes / additional info? 
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: December 15 2005 at 18:38 | IP Logged
|
|
|
Bob,
One thing you might try as well would be "reintializing" (under the File menu) PowerHome instead of unplugging the CM11A.
Also, I just reviewed the code for the CM11A and see two places where the phrase "timeout" may be used in the log. On is waiting for the "checksum" and the other is waiting "to play the X-10 code". Which version are you seeing?
Another possibility is that you have a lot of X-10 traffic on the line. When communicating with the CM11A, as soon as X-10 is received, it must be addressed before you can send. You may be partially into the middle of sending X-10 data and if incoming X-10 is detected, you must abort your send attempt, receive the X-10 and then startover. This is a retry. The default retry count I believe is 3. You may try increasing this value in your pwrhome.ini file (under the [CM11A] section) and restarting PowerHome.
Or, it could be something hardware related like Tony suggests.
Dave.
|
| Back to Top |
|
| |
RWCS
Senior Member
Joined: October 28 2002
Location: United States
Online Status: Offline
Posts: 102
|
| Posted: December 15 2005 at 18:56 | IP Logged
|
|
|
Thanks for the reply. The problem is definately in the "play the X-10 code" routine. There could be traffic, or noise. . . seems poorly designed to me if what you say is true. The only thing is when the controller(s) get in this funk it takes a while to get them out (if you don't pull their power). . . could be the next x-10 traffic that does it. Is there a way to reinit from a macro? Is there a way to detect the timeout and reinit? This is getting to be major problem here. cracked open on of my controllers here and I'm running it on the bench as we speak. . . I'll see what gets hot if anything. . . 
|
| Back to Top |
|
| |
RWCS
Senior Member
Joined: October 28 2002
Location: United States
Online Status: Offline
Posts: 102
|
| Posted: December 15 2005 at 19:03 | IP Logged
|
|
|
Dave
I know I don't like to "fix" things that aren't broken, hence my hesitation to "upgrade" everytime there is a release. To many instances of broke what WAS working. . . My powerhome.ini file looks like:
===================================
[CM17A]
Standby=100000
Signal=600
Wait=600
SendDelay=800000
[MR26A]
UpdateStatus=no
Echo=
EchoController=0
IgnoreCM17A=no
=====================================
No CM-11A section!
Bob
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: December 19 2005 at 21:36 | IP Logged
|
|
|
Bob,
Not sure what version you're running but it must be fairly old. I understand what you mean about upgrading though. Try as I might to make it seamless, sometimes it's just not doable. Since you don't have a CM11A section though, we wont be able to adjust the retry count.
Yep, it's true about the CM11A. It caused me a lot of problems when initially writing the code for it. You initially write data to the CM11A and then wait for a checksum. If the checksum is not correct, that usually means that X-10 data was received and your transmission was ignored. All communication at this point is ignored until you request the received X-10 data. After you've gotten the received data, you can attempt to send X-10 again. If more incoming X-10 was received during this attempt, you'll have to again read the received X-10 data before attempting to send again. It's like trying to get a work in edgewise.
Yes, you can reint from a macro using the ph_reinitialize command. Have you tested that a manual reinitialize clears the problem? Another possible way to clear it may be just disconnecting the controller and reconnecting (under the File menu). If this works, there are functions for this as well (this is assuming that your version is at least new enought to include the ph_reinitialize and the ph_connect and ph_disconnect functions).
As far as detecting a timeout, you could probably use SQL to view the eventlog. You could have a timed event that executes every five minutes and searches the eventlog for any timeouts within the last 5 minutes. If found, then you could launch the reinit or disconnect/connect.
Dave.
|
| Back to Top |
|
| |
RWCS
Senior Member
Joined: October 28 2002
Location: United States
Online Status: Offline
Posts: 102
|
| Posted: December 19 2005 at 22:59 | IP Logged
|
|
|
Many thanks Dave for your wonderful advice. To answer your first question 1.02.2. What you say makes sense up to a point. The problem I've seen is that this deaf peroid lasts much longer than any message. It is like the incomplete message time-out in the CM-11A is hughly long. My log often has multiple time-out messages over many seconds. One example is tonights log, My wife selects OFF for the home theater and I have four timeout messages in a row in the log over 47 seconds. I'm thinking I should start every Macro with a reinit. I'll do some experimintation and let you know how it comes out.
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: December 20 2005 at 10:41 | IP Logged
|
|
|
Bob,
I wouldnt think that you would want to do a reinitialize at the start of every macro. This is effectively the same as closing PowerHome and restarting it. I think if would be way overkill.
Version 1.02.2....I don't think I can even remember that far back  . If you would like to upgrade, I would be more than happy to do the upgrade for you. You could email me your pwrhome.db and pwrhome.ini files and I could work the upgrade through for you. You could then install the current beta into a different directory and test it to see if a newer version will help you out.
Dave.
|
| Back to Top |
|
| |
Deano
Groupie
Joined: February 19 2003
Location: United States
Online Status: Offline
Posts: 75
|
| Posted: August 12 2006 at 10:10 | IP Logged
|
|
|
Dave,
This thread seemed to end without a soultion.
I am running 1.03.4 with DB 1.03.2 and I haven't upgraded because I am still running Windows 95 
I have been stable for many months but about a week ago I started getting "timeout waiting to play the X-10 code"
Every time I send an X10 command weather addres or action, I get many "Incomming X10 received on controller 1 Byte Value 02 01 xx" where xx could be anything. Eventually the command does get thru and the action happens.
If I disconnect while this is goint on I get a Critical Error Dialog box
Error Number 39
Error Message: Error accessing external object property output at line 79 in function f_x10send of objectuo_controller_cm11a
Window: uo_controller_cm11a
Object: uo_controller_cm11a
Event: f_x10send
Line: 79
My CM11a retry was 5 and I bumped it to 8 with no effect
I have tried two different cm11a units with the same result.
|
| Back to Top |
|
| |
RWCS
Senior Member
Joined: October 28 2002
Location: United States
Online Status: Offline
Posts: 102
|
| Posted: August 13 2006 at 16:47 | IP Logged
|
|
|
Deano
I hope Dave can correct me if I'm in error, but the way I understand it is:
The problem is in PH. There is a buffer in the older versions which has no overflow check on it's pointer. When that buffer overflows, due to noise or garbled packets the process that receives the X-10 data from the CM-11 ceases to function.
The solution here was to upgrade PH. I also changed over to the USB controller, which also is no help to you if you are running W95.
I wish I could be of more help to you, but I'm thinking you are stuck between a rock and a hard place. . . Find out why you are getting bad data (collisions, noise etc.), and you may reduce the problem.
Bob
|
| Back to Top |
|
| |
Deano
Groupie
Joined: February 19 2003
Location: United States
Online Status: Offline
Posts: 75
|
| Posted: August 14 2006 at 08:29 | IP Logged
|
|
|
Bob,
Thanks for the insight. I think that I am running the latest version that will run on Win 95 but I am getting ready to upgrade this 1995 computer to 98se as soon as I can get over the trauma caused by a clean install on Win XP on this machine.
Can I see and empty this buffer?
For clarification: With the exception of my phase bridge/amp, CM11a is the only device that talks on power line. All my inputs come in on controller 2 thru com3 and a W800rf32.
Looking closer the problem seems to be isolated to addressing a device.
I have a very simple macro that addresses 3 lights (F11, F13, & F14) then sends a bright 100 command. When this runs, I get 8 incomming messages on controller 1 that decode to each of the addresses for a total of 24 before the command to brighten occurs. This results in 3 timeout system messages.
Possible related problem:
I have an old Firecracker program that at one time did use com 1 that I can't get rid of. When I try to uninstall, it says "Can't open INstall log". It's been there for a long time and has really only annoyed me when I try to reinstall Firecracker
|
| Back to Top |
|
| |
Deano
Groupie
Joined: February 19 2003
Location: United States
Online Status: Offline
Posts: 75
|
| Posted: August 14 2006 at 16:54 | IP Logged
|
|
|
Spent the day!
Format C:
INstall Win 98se
Upgrade to PH 1.03.4.4
Same Problem
|
| Back to Top |
|
| |
Deano
Groupie
Joined: February 19 2003
Location: United States
Online Status: Offline
Posts: 75
|
| Posted: August 15 2006 at 07:57 | IP Logged
|
|
|
Well now I'm up to 10347!
A critical error occurred at 2006-08-15 07:52:03.530.
PowerHome Version: 1.03.4.7
Error Number: 39
Error Message: Error accessing external object property commport at line 25 in function f_controllerconnect of object uo_controller_cm11a.
Window: uo_controller_cm11a
Object: uo_controller_cm11a
Event: f_controllerconnect
Line: 25
|
| Back to Top |
|
| |
RWCS
Senior Member
Joined: October 28 2002
Location: United States
Online Status: Offline
Posts: 102
|
| Posted: August 15 2006 at 11:40 | IP Logged
|
|
|
I also had to go to the USB power line interface. Since you are running W98SE you too should be able to go USB.
Bob
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: August 15 2006 at 20:23 | IP Logged
|
|
|
Deano,
The previous problem you were having with the incoming commands was most likely caused by your phase coupler. I had this exact same problem...everything was working fine and then out of the blue the CM11A just wouldnt work anymore until I got rid of the phase coupler (it was an active Leviton unit). I changed to a passive unit that plugged in at the dryer and everything started working.
If your phase coupler is an active unit of the the repeating/amplifier type, then this is most likely the culprit. I would try temporarily disconnecting it to see if the problem goes away.
However, the bigger problem now is that since upgrading to 1.03.4.7 you cant connect to the CM11A. Based upon the error message, it appears that the Microsoft COMM control did not register properly somehow. Did you follow the upgrade instructions of renaming your previous PowerHome installation directory and then installing new? Since it appears you've got a backup of your PowerHome data (pwrhome.db and pwrhome.ini), I would uninstall all versions of PowerHome and then reinstall. Make sure you have administrator privileges when installing. After reinstalling, copy over your pwrhome.ini and pwrhome.db files and let me know where that gets you.
Dave.
|
| Back to Top |
|
| |
Deano
Groupie
Joined: February 19 2003
Location: United States
Online Status: Offline
Posts: 75
|
| Posted: August 16 2006 at 10:11 | IP Logged
|
|
|
Dave,
Again, you hit the nail on the head!
Reinstall fixed the connect error. When I went to remove 10347 add/remove found both 10344 and 10347 so I removed both and re-installed 10347.
I think there might have been an .INI issue going from 1034 to 10344. I belive that 1034 was acutally using powerhome.1034.ini instead of powerhome.ini.
X10PRO XPCR phase coupler is definitly the cause of the timeout problem. Works fine for a couple of minutes until warmed up the starts with the garbage output - basicly repeating the address. I've been using this device for a couple of years with no problem - guess I just wore it out - so much for "solid state" electronics.
My problem now is gitting my code up to date since I skipped 3 or 4 PH upgrades.
found the ph_x10btn change and am currently working on why multix dosen't work anymore.
Found a reference to a search function in 10347 but now I can't find it
|
| Back to Top |
|
| |
Deano
Groupie
Joined: February 19 2003
Location: United States
Online Status: Offline
Posts: 75
|
| Posted: August 16 2006 at 10:17 | IP Logged
|
|
|
Found it under reports but don't know how to make it work - got to go ge acrobat so I can rtfm 
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: August 20 2006 at 20:38 | IP Logged
|
|
|
Deano,
You're correct. It's "Database Where Used" under the reports menu. It's pretty simple to use. If you wanted to search for all occurences of ph_x10btn in your code, just type %ph_x10btn% in the selection criteria window. The %(percent sign) is a wildcard character in SQL.
HTH,
Dave.
|
| Back to Top |
|
| |
Active Topics 
Memberlist 
Search 
Help
Register 
Login
PowerHome Messageboard : PowerHome General
Topic: CM-11A takes nap
