| Author |
|
mustangcoupe
Super User
Joined: August 08 2003
Location: United States
Online Status: Offline
Posts: 308
|
| Posted: May 02 2006 at 11:07 | IP Logged
|
|
|
Ok, Dave thanks, the insteon lasted about 2 1/2 days befor it went to lunch 
ui:srq:srir=00 00 00 04 42 43 0F 19 00
ui:srq:srir=00 00 00 04 49 D6 0F 19 00
ui:srq:srir=00 00 00 04 41 6D 0F 19 00
Todd
__________________
Todd Hannemann
HA newbie 
 PowerHome - UPB - ELK
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: May 11 2006 at 16:53 | IP Logged
|
|
|
Todd,
Ok, Ive checked out your DB and logs. The DB didnt look that bad. I saw the extra PLCS and the one that has an address of 01.02.03 is the simulator. If you start the SDM without a PLC attached, it will sometimes load up the simulator (built into the SDM) and it's address is 01.02.03. So I wouldnt be too concerned about this. Just go ahead and delete this device. Anytime that PowerHome detects that a new PLC has been connected, it will create an Insteon device entry so that SQL joins can all be performed properly.
Now, the big problem is in your SDM log. I don't know what to make of it. The big problem is right at the beginning pasted below:
Code:
downloadTimer started
timerActivate enabled
bad:00 len=304
SDM:DM=active,1.01.58.202,4/27/2006 6:54:35 AM,responded,00.D6.9D,2.12
ui:getplcstatus
PLC:getPLCstatus=beginlist
port=USB4
connected=True
firmware=0.1
id=01.2C.06
devicetype=InsteonPLC-USB
lastErrorMsg=#0:
endlist
ui:srq:srir=00 00 00 04 41 6D 0F 19 00
si:01 2C 06 04 41 6D 0F 19 00
PLC:eventraw=03
PLC:srq:SRIR=send failed
|
|
|
You can see that the 4th line shows where it connects to the PLC and the address is 00.D6.9D. Then, just a few lines below that, PowerHome does a GETPLCSTATUS which includes fetching the PLC device ID and that returns 01.2C.06. What the heck is that? The PLC has two different device ID's? Another problem is the 3rd line with the bad:00 len=304. Ive never seen this before but it would appear to be a bad checksum self check routine.
At this point, it looks like your PLC is internally corrupt and may actually need to be sent back to SmartHome for a replacement. The only thing you could try before doing that would be to open the "Insteon DM Control" window and do a "Download Core Application".
In any event, I would say that this is most likely a big contributor to the problems that you are having.
Let me know,
Dave.
|
| Back to Top |
|
| |
mustangcoupe
Super User
Joined: August 08 2003
Location: United States
Online Status: Offline
Posts: 308
|
| Posted: May 15 2006 at 21:30 | IP Logged
|
|
|
Well Dave... I called Smarthome. they told me to reset the device and then reload all links and app code... and call back if I still have problems. I did that and still had problems and then it hit me that only happened on one computer (the real strange stuff) so I reloaded it with windows xp pro it had win 2000 advanced server.... hmmm it looks better (if we could only work on the controller getting "lost" and needing a reset or this dammn rain (New Hampshire has had 11+ inches in 24 or so hrs...and it is still coming) we have here and keep the power stable it would be great!
__________________
Todd Hannemann
HA newbie
PowerHome - UPB - ELK
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: May 15 2006 at 22:29 | IP Logged
|
|
|
One thing that seems to have come to light in just the past few days is that the serial version of the PLC lasts MUCH longer than the USB version. If you've got a USB version, then you may be able to get SmartHome to swap you for a serial version.
Dave.
|
| Back to Top |
|
| |
Active Topics 
Memberlist 
Search 
Help
Register 
Login
PowerHome Messageboard : PowerHome General
Topic: insteon problems
