Active TopicsActive Topics  Display List of Forum MembersMemberlist  Search The ForumSearch  HelpHelp
  RegisterRegister  LoginLogin
PowerHome General
 PowerHome Messageboard : PowerHome General
Subject Topic: Stuck in Scan Link loop Post ReplyPost New Topic
Author
Message << Prev Topic | Next Topic >>
lizaoreo
Groupie
Groupie


Joined: February 11 2013
Location: United States
Online Status: Offline
Posts: 75
Posted: February 12 2013 at 08:25 | IP Logged Quote lizaoreo

I've just started setting up PH, got all my devices added
yesterday. One of my devices just keeps doing a scan
link though and nothing else happens (such as the poll
status). I tried turning off status scan and link scan,
which stopped everything except for the scan link. I
disabled the device in the Insteon devices tab and it
just moved to a different device and did the same. I re-
enabled and let it sit all night as I had seen someone
else mention it can take a while to do whatever it's
doing. Today, it's still doing it, been about 9-12 hours
now.

The device is a 2876S ICON On/Off Switch. So far as I
know it doesn't have the new I2CS stuff.

The Completed Operations has:
SCAN LINK: Record 1, Device <Name> (xx.xx.xx)
over and over and over, same thing, exactly. Doesn't
increment the record or anything. No errors anywhere,
the Clear COMMs and Clear Failed haven't gone red, I've
even tried checking them anyways and doing a Save/Refresh
to no avail.

I don't know how to copy the Insteon Raw Log data and
that's a lot of data, but will gladly do so if needed.
Essentially I get the same 4 lines over and over.
A TX
A RX SENTINSTEONEXT
A RX RECEIVEINSTEONRAW
A RX RECEIVEINSTEONEXT

So, that's what I got, hopefully I provided everything
you guys need to help me (and everything I've tried so
far), if not, just let me know what else you need.
Back to Top View lizaoreo's Profile Search for other posts by lizaoreo
 
grif091
Super User
Super User


Joined: March 26 2008
Location: United States
Online Status: Offline
Posts: 1357
Posted: February 12 2013 at 09:13 | IP Logged Quote grif091

Using PowerHome Explorer select Setup | Controllers | Settings button for Controller. Set Echo Log File to a fully qualified name ex c:\temp\phlog.txt click Done.

To generate the Insteon Raw Log check Echo Raw Log to File check box. It is the right most check box under Insteon Explorer. Let it trace a few iterations of the repeated Scan of the one link record.   Uncheck Echo Raw Log to File to stop logging.   Edit the file with WordPad, copy/paste the traced commands to the forum.    

Not likely an ICON is I2CS. They were discontinued before the most of the firmware was updated to I2CS.


Edited by grif091 - February 12 2013 at 09:15


__________________
Lee G
Back to Top View grif091's Profile Search for other posts by grif091
 
lizaoreo
Groupie
Groupie


Joined: February 11 2013
Location: United States
Online Status: Offline
Posts: 75
Posted: February 12 2013 at 09:31 | IP Logged Quote lizaoreo

Thanks Lee :)

Quote:
2013-02-12 10:26:52.546     TX     02 62 17 CC C0 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 C2
2013-02-12 10:26:52.601     RX    &n bsp;SENTINSTEONEXT=18   D3 0C 17 CC C0 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 C2 06
2013-02-12 10:26:53.168     RX     RECEIVEINSTEONRAW=17 CC C0 18 D3 0C 27 2F 00
2013-02-12 10:26:53.495     RX     RECEIVEINSTEONEXT=17 CC C0 18 D3 0C 11 2F 00 01 01 00 FF 01 A2 00 18 D3 0C FF 1F 01 C2
2013-02-12 10:27:03.579     TX     02 62 17 CC C0 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 C2
2013-02-12 10:27:03.634     RX     SENTINSTEONEXT=18 D3 0C 17 CC C0 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 C2 06
2013-02-12 10:27:04.199     RX     RECEIVEINSTEONRAW=17 CC C0 18 D3 0C 27 2F 00
2013-02-12 10:27:04.529     RX     RECEIVEINSTEONEXT=17 CC C0 18 D3 0C 11 2F 00 01 01 00 FF 01 A2 00 18 D3 0C FF 1F 01 C2
2013-02-12 10:27:14.598     TX     02 62 17 CC C0 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 C2
2013-02-12 10:27:14.648     RX     SENTINSTEONEXT=18 D3 0C 17 CC C0 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 C2 06
2013-02-12 10:27:15.215     RX     RECEIVEINSTEONRAW=17 CC C0 18 D3 0C 27 2F 00
2013-02-12 10:27:15.544     RX     RECEIVEINSTEONEXT=17 CC C0 18 D3 0C 11 2F 00 01 01 00 FF 01 A2 00 18 D3 0C FF 1F 01 C2


Edited by lizaoreo - February 12 2013 at 09:34
Back to Top View lizaoreo's Profile Search for other posts by lizaoreo
 
dhoward
Admin Group
Admin Group
Avatar

Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
Posted: February 12 2013 at 09:42 | IP Logged Quote dhoward

lizaoreo,

The first thing that caught my eye was that it was an Icon device and you were sending extended commands. I didnt think any of the Icon devices supported extended but apparently Im wrong since your log is showing (at first glance) properly formatted extended records being received.

The first thing I'd need to know is the version of PowerHome you're running. If you're not on 2.1.4 with the I2CS patch, I would definitely upgrade as the Insteon extended command processing changed significantly and several bugs were fixed.

Another thing you may want to try is for the particular device in question, on the devices tab, scroll all the way to the right and uncheck the Use Ext for ALDB column and save your changes.

Let me know,

Dave.
Back to Top View dhoward's Profile Search for other posts by dhoward Visit dhoward's Homepage
 
lizaoreo
Groupie
Groupie


Joined: February 11 2013
Location: United States
Online Status: Offline
Posts: 75
Posted: February 12 2013 at 10:21 | IP Logged Quote lizaoreo

I knew I'd forget something, I meant to include I am indeed running the 2.1.4 version with the I2CS patch :)

I'll give that a shot, I don't know what the extended stuff is and I didn't turn it on, must have been default,
I had to set up the devices myself, used a spreadsheet someone on here linked :)

The Spreadsheet: http://www.madreporite.com/insteon/Insteon_device_list.htm

Thanks Dave :)
Back to Top View lizaoreo's Profile Search for other posts by lizaoreo
 
lizaoreo
Groupie
Groupie


Joined: February 11 2013
Location: United States
Online Status: Offline
Posts: 75
Posted: February 12 2013 at 10:34 | IP Logged Quote lizaoreo

Oddly enough, only 3 devices had that option checked, I unchecked it on all three, two of them were
2876s and one was an Icon Lamp Dimmer.

After that it went through, no problem. Though it seemed to like turning the option on for other
devices, I had to wait as it did it's Scan Link thing for each one because it go hung on them and a
refresh of the devices screen showed the device in question with it's "Use Ext for ALDB" option
checked.

The SwitchLinc's and KeypadLinc's didn't seem to care though, so I left them checked. What do the
extended commands do/provide?
Back to Top View lizaoreo's Profile Search for other posts by lizaoreo
 
dhoward
Admin Group
Admin Group
Avatar

Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
Posted: February 12 2013 at 12:13 | IP Logged Quote dhoward

lizaoreo,

Good to know you're on the latest version. I checked out your raw Insteon log and found the problem. PH is requesting the first record of the database based upon the Mem Top setting in the Insteon device types table (on the Types tab) for this particular device. Based upon what what sent (address 0FFF) I know this setting is 4096. The problem is that the device is replying in the extended command with 0100 which doesnt match the sent command so the record retries endlessly. Since its a valid response (not a timeout), the device is never flagged.

This is a current problem with Insteon where the protocol doesnt seem to be "standardized". I'll have to research how to handle this for the next release. The problem is I don't have any devices that actually exhibit this behaviour so it'll be hard to test.

Extended commands are quicker than standard commands so if your device supports it, I would leave it checked for as many as you can. In order to use it though, you must have the IEngine set to I2 and the Use Ext for ALDB checked. If you check it for a particular device and you start seeing timeouts when extended commands are sent, then its likely that your device doesnt support and you'll need to uncheck it.

Lee,

Just wondering if you've encountered any devices that exhibit this behavior where the sent ext command is for address 0FFF and the reply is for something else, in this case 0100?

Dave.
Back to Top View dhoward's Profile Search for other posts by dhoward Visit dhoward's Homepage
 
lizaoreo
Groupie
Groupie


Joined: February 11 2013
Location: United States
Online Status: Offline
Posts: 75
Posted: February 12 2013 at 12:38 | IP Logged Quote lizaoreo

Yeah, it's all good now. Only the ICON devices gave me
issues with the extended commands, the rest are still
checked and have I2 set except for one SwitchLinc which
seems to be new enough to be I2CS.

Now it's rolling through Poll Status for each device like
it should be :)

Thanks for the help, made my first macro now to kill all
the lights and I'm well on my way to driving my wife nuts
again with a new system. This is looking very promising
towards surpassing what HL2 gave me ^_^
Back to Top View lizaoreo's Profile Search for other posts by lizaoreo
 
grif091
Super User
Super User


Joined: March 26 2008
Location: United States
Online Status: Offline
Posts: 1357
Posted: February 12 2013 at 15:46 | IP Logged Quote grif091

Dave

The ICON is one of the later units that physically supports only 30 link records.   The ICON spec always indicated 30 link records but the devices were shipped for years with PLMs that had memory large enough to contain the standard 400+ links.

This ICON is returning the true link record address of 00FF in response to the 0FFF request. That is what indicates it physically supports only 30 link records. 00FF is the true starting address of the link database for ICONS that support 30 links. This is the last variant I know of before the ICONs were discontinued.

lizaoreo

Thanks for posting the Raw Log file. It provided the key information in understanding this specific ICON device.


Edited by grif091 - February 12 2013 at 15:47


__________________
Lee G
Back to Top View grif091's Profile Search for other posts by grif091
 
dhoward
Admin Group
Admin Group
Avatar

Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
Posted: February 12 2013 at 16:56 | IP Logged Quote dhoward

Lee,

Appreciate the info. I'll either have to add some code to handle or possibly the below might work.

lizaoreo,

If you're willing, could you change the Mem Top value from 4096 to 256 only for the 2876S device (this would be on the Types tab). Save the changes and then on the Devices tab for one of the switches (probably the one with the fewest links), recheck the Use Ext for ALDB and click the Scan DB column and then save. This will cause PH to rescan the links for this device using extended commands and hopefully will work with the new top of memory address.

Thanks,

Dave.
Back to Top View dhoward's Profile Search for other posts by dhoward Visit dhoward's Homepage
 
lizaoreo
Groupie
Groupie


Joined: February 11 2013
Location: United States
Online Status: Offline
Posts: 75
Posted: February 12 2013 at 19:05 | IP Logged Quote lizaoreo

Of course, no problem at all :)

Looks to have done the trick ^_^ It did it's think quick
and we're back to polling statuses after the scan link
finished. I'll set the option for the rest of the 2876S
devices and go change that memory value for the other ICON
devices :)

EDIT: And it worked for everything, now I've got all my
stuff set for the extended codes. The only other device
was a 2856D2 Icon Lamp Dimmer.

Edited by lizaoreo - February 12 2013 at 19:09
Back to Top View lizaoreo's Profile Search for other posts by lizaoreo
 
dhoward
Admin Group
Admin Group
Avatar

Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
Posted: February 13 2013 at 15:34 | IP Logged Quote dhoward

lizaoreo,

Thats awesome news. Glad to hear changing the Mem Top fixes the problem so code changes arent necessary. Appreciate you testing that out for me.

Dave.
Back to Top View dhoward's Profile Search for other posts by dhoward Visit dhoward's Homepage
 

If you wish to post a reply to this topic you must first login
If you are not already registered you must first register

  Post ReplyPost New Topic
Printable version Printable version

Forum Jump
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot delete your posts in this forum
You cannot edit your posts in this forum
You cannot create polls in this forum
You cannot vote in polls in this forum