| Author |
|
JustAnotherJoe
Newbie
Joined: January 22 2007
Online Status: Offline
Posts: 16
|
| Posted: January 22 2007 at 00:59 | IP Logged
|
|
|
Long time X-10 user just getting started with Insteon. Downloaded PowerHome for the specific purpose of managing Insteon links, but can't get connected.
The 2414S Insteon Serial PLC is plugged in, and connected to the PC via the supplied cable. In PowerHome Explorer|Setup|Controllers, 'Insteon DM' is defined. Smarthome Device Manager is running; its startup log is as follows:
ui:getplcstatus
PLC:getPLCstatus=beginlist
port=COM2
connected=True
firmware=15.0
id=08.E2.0D
devicetype=InsteonPLC-COM
lastErrorMsg=#0:
endlist
uifinished:getplcstatus
ui:getlinks
uifinished:getlinks
ProgressStart
ProgressMax=1024
Progress=0%,0,1024
downloadTimer started
timerActivate enabled
ProgressError=0%,0,1024
ProgressError=0%,0,1024
ProgressError=0%,0,1024
ProgressEnd=False
ProgressStart
ProgressMax=1024
Progress=0%,0,1024
bad:E8 len=4
ProgressError=0%,0,1024
ProgressError=0%,0,1024
bad:15 len=41112
ProgressError=0%,0,1024
ProgressEnd=False
PLC:getlinks=false,failed for unknown reasons
A few commands yield the following results:
ui:port=?
PLC:disconnect=OK
PLC:port=true
uifinished:port=?
ui:getport
PLC:getport=COM2
uifinished:getport
ui:isResponding
PLC:isresponding=True
uifinished:isResponding
When the Insteon Explorer|Setup|PLC Setup 'Download' button is clicked, the SDM log shows:
ui:dl=timercoreapp12
uifinished:dl=timercoreapp12
bad:14 len=12
PLC:ERROR=012:MapNotLoaded-PLC not connected or no valid map. Try using isResponding first.
PLC:dl=-7
Two Icon Lamp Modules have been defined, but when trying to control them, the log shows:
ui:srir=00 00 00 07 B0 E9 0F 11 FF
si:08 E2 0D 07 B0 E9 0F 11 FF
PLC:ERROR=012:MapNotLoaded-PLC not connected or no valid map. Try using isResponding first.
PLC:SRIR=send failed
each time.
What shall I do now?
__________________
Just Another Joe
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: January 22 2007 at 15:26 | IP Logged
|
|
|
Joe,
Welcome to PowerHome!!
It would appear that something is wrong with your firmware. A firmware version of 15.0 is simply not right. Consequently, the SDM is unable to find a matching PLC map. Typical firmware values should be 2.13 which causes the SDM to load the plc3-2d.ump file found in the "Maps" directory in the SDM directory structure.
Ive seen this reported a couple of times and the only fix seems to be a new unit from SmartHome (the firmware itself cannot be field upgraded). I would probably contact them and see if they have anything else to offer.
Sorry for the bad news  .
Dave.
|
| Back to Top |
|
| |
JustAnotherJoe
Newbie
Joined: January 22 2007
Online Status: Offline
Posts: 16
|
| Posted: January 22 2007 at 18:04 | IP Logged
|
|
|
Hi Dave,
Thanks for the response and the welcome.
I have a new log to show you:
ui:getplcstatus
PLC:getPLCstatus=beginlist
port=COM1
connected=True
firmware=2.13
id=08.20.5C
devicetype=InsteonPLC-COM
lastErrorMsg=#0:
endlist
uifinished:getplcstatus
ui:getlinks
uifinished:getlinks
ProgressStart
ProgressMax=1024
Progress=0%,0,1024
Progress=12%,128,1024
Progress=25%,256,1024
Progress=37%,384,1024
Progress=50%,512,1024
Progress=62%,640,1024
Progress=75%,768,1024
Progress=87%,896,1024
ProgressEnd=True
PLC:getlinks=beginlist
id=07.B0.E9,mode=sla,addr=FC58,laddr=0000,g=1,cmds=00 00,d=00
id=07.B0.DE,mode=sla,addr=FC80,laddr=0000,g=1,cmds=00 00,d=00
id=05.BC.49,mode=sla,addr=FED8,laddr=0000,g=1,cmds=00 00,d=00
id=08.E2.0D,mode=sla,addr=FFC8,laddr=0000,g=1,cmds=00 00,d=00
endlist
downloadTimer started
timerActivate enabled
UI:ConnectedAndReady
SDM:DM=active,1.01.122.278,2007-01-22 16:15:26,responded,08.20.5C,2.13
starttime=00:06
ui:srir=00 00 00 07 B0 E9 0F 11 FF
uifinished:srir=00 00 00 07 B0 E9 0F 11 FF
si:08 20 5C 07 B0 E9 0F 11 FF
PLC:eventraw=03
PLC:eventraw=03
PLC:eventraw=05
2007-01-22 16:17:43:nakmsg
PLC:SRIR=05
ui:srir=00 00 00 07 B0 DE 0F 11 FF
uifinished:srir=00 00 00 07 B0 DE 0F 11 FF
si:08 20 5C 07 B0 DE 0F 11 FF
PLC:eventraw=04
PLC:receiveinsteonraw=04 07 B0 DE 08 20 5C AF 11 FE
2007-01-22 16:18:21:ackmsg=07.B0.DE:ON at OUT
PLC:eventraw=03
PLC:SRIR=03,07 B0 DE 08 20 5C AF 11 FE
ui:srir=00 00 00 07 B0 E9 0F 13 00
uifinished:srir=00 00 00 07 B0 E9 0F 13 00
si:08 20 5C 07 B0 E9 0F 13 00
PLC:eventraw=03
PLC:eventraw=03
PLC:eventraw=03
PLC:eventraw=04
PLC:receiveinsteonraw=04 07 B0 E9 08 20 5C 2B 13 00
2007-01-22 16:18:27:ackmsg=07.B0.E9:OFF at OFF
PLC:SRIR=04,07 B0 E9 08 20 5C 2B 13 00
ui:srir=00 00 00 07 B0 DE 0F 13 00
uifinished:srir=00 00 00 07 B0 DE 0F 13 00
si:08 20 5C 07 B0 DE 0F 13 00
PLC:eventraw=04
PLC:receiveinsteonraw=04 07 B0 DE 08 20 5C AB 13 FE
2007-01-22 16:18:55:ackmsg=07.B0.DE:OFF at OFF
PLC:SRIR=04,07 B0 DE 08 20 5C AB 13 FE
Does this look better; everything look okay here?
What happened is that I originally had the PLC on COM2 via a USB-Serial adaptor, and it did appear to be communicating (at least to some extent). Other serial devices have worked fine with the adaptor. But for some reason the PLC address shown in the log was different than the address on the back of the PLC. Thinking about it, I decided to try a direct connection to COM1 just to rule out the adaptor.
Well! As you can see, it now appears to be working fine  . With this running, I can now begin to install my keypads, switches, and modules, learn about PowerHome, and get them all linked together.
However, I regret having to use my only direct COM port, which was previously given to the Ocelot. I guess a solution would be to install a COM port PCI card.
EDIT: Oh, by the way, now that it is working, should I still download the core app from PowerHome, which wasn't successful before, or leave it alone since it is working?
Edited by JustAnotherJoe - January 22 2007 at 18:06
__________________
Just Another Joe
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: January 22 2007 at 18:33 | IP Logged
|
|
|
Joe,
Much better looking now  !! You've got the proper firmware returned and even the device address is different. The only thing that didnt really look good is when a direct command was issued to 07.B0.E9 (On at 255) was issued and you got a NAK message. Could be communications though.
Other than that, it's a perfectly normal looking SDM log. I would definately do the "Download Core App" though just to make sure that the proper core that PowerHome needs is in the PLC. Other cores have most of the functionality and can appear to work but may cause problems that are not immediately recognizable.
A COM PCI card is a great idea. Ive got 2 ports on my motherboard and a 4 port PCI COM card and everything works great. You could possibly try another USB to COM adaptor though. Some work better than others (Im using one on my notebook right now for the Elk development).
Good luck,
Dave.
|
| Back to Top |
|
| |
JustAnotherJoe
Newbie
Joined: January 22 2007
Online Status: Offline
Posts: 16
|
| Posted: January 22 2007 at 21:27 | IP Logged
|
|
|
Thanks, Dave.
Core App downloaded, and seems to be working fine.
__________________
Just Another Joe
|
| Back to Top |
|
| |
|
|
Active Topics 
Memberlist 
Search 
Help
Register 
Login
PowerHome Messageboard : PowerHome General
Topic: Can’t Connect Insteon PLC
