You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a scan posted here http://marc.merlins.org/tmp/mh_scan_all1/scan_all by Marc, there are quite a few instances of a ghost timer expiry. They seem to be benign until one occurs while a command is queued after a PLM busy NACK (15) response. That halts the scan state machine. Need to figure out why a timer is either 1) inadvertently left running, or 2) not correctly matched to the device / message after it expires. I suspect 1). I created a nice timeline with the following egrep command after saving off the file:
egrep "timer expired but no transmission|Scan all link tables|[Insteon::ALDB_i1] DEBUG3:" scan_all
The text was updated successfully, but these errors were encountered:
In a scan posted here http://marc.merlins.org/tmp/mh_scan_all1/scan_all by Marc, there are quite a few instances of a ghost timer expiry. They seem to be benign until one occurs while a command is queued after a PLM busy NACK (15) response. That halts the scan state machine. Need to figure out why a timer is either 1) inadvertently left running, or 2) not correctly matched to the device / message after it expires. I suspect 1). I created a nice timeline with the following egrep command after saving off the file:
egrep "timer expired but no transmission|Scan all link tables|[Insteon::ALDB_i1] DEBUG3:" scan_all
The text was updated successfully, but these errors were encountered: