From: Eloy P. <pe...@ch...> - 2013-05-09 14:16:42
|
Hello, I see this error message ("Warn! Unable to locate object for source: xxxxxx") every now and then. An example of such a message, which happened while scanning an ALDB, is below. A couple of questions related to this: 1. Does anyone know why such a message would be generated? I think it's caused by bit corruption but isn't there a CRC byte in an INSTEON message that would cause a corrupted message like this to be dropped? Or the CRC is only for i2CS devices? But if that is the case, then what is the "Message Integrity Byte" present in INSTEON messages since day 1 used for? This part has always confused me about INSTEON... I've always seen bit corruption, even with this CRC byte that is supposed to cause corrupted messages to be dropped (see this 3-year old discussion that I started on the Smarthome forums: http://www.smarthome.com/forum/topic.asp?TOPIC_ID=7006). 2. In the particular case of the transactions below, at 09:44:00 there's the incoming message that causes the warning to be generated. But then a few milliseconds later, there's another incoming message, and then the link table scan is confirmed to be successful. Would that second message be a "good" (non-corrupted) version, received through some other repeater, of the message that caused the warning to be generated? I'm guessing that could be the case but I thought I'd ask just to be sure. Things seem to be working wonderfully even with the sporadic corrupted message, but I thought I'd ask about these things to further my understanding of how things are supposed to work. Cheers, Eloy Paris.- ------------------------------------------------ 05/09/13 09:43:58 AM [Scan all link tables] Now scanning: $appliance_linc (2 of 17) 05/09/13 09:43:58 AM [Insteon::ALDB_i2] $appliance_linc reading ALDB at location: 0x0000 05/09/13 09:43:58 AM [Insteon_PLM] DEBUG2: Sending obj=$appliance_linc; command=read_write_aldb; extra=000000000001000000000000000000 incurred delay of 0.00 seconds; starting hop-count: 3 05/09/13 09:43:59 AM [Insteon::BaseInterface] DEBUG: PLM command:insteon_ext_received; Device command:read_write_aldb; type:direct; group: 05/09/13 09:43:59 AM [Insteon::ALDB_i2] $appliance_linc reading ALDB at location: 0x0ff7 05/09/13 09:43:59 AM [Insteon_PLM] DEBUG2: Sending obj=$appliance_linc; command=read_write_aldb; extra=0000000ff701000000000000000000 incurred delay of 0.51 seconds; starting hop-count: 3 05/09/13 09:44:00 AM [Insteon::BaseInterface] Warn! Unable to locate object for source: 10f91a and group: 05/09/13 09:44:00 AM [Insteon::BaseInterface] DEBUG: PLM command:insteon_ext_received; Device command:read_write_aldb; type:direct; group: 05/09/13 09:44:00 AM [Insteon::ALDB_i2] $appliance_linc completed link memory scan: status: good 05/09/13 09:44:01 AM [Insteon_PLM] DEBUG2: Sending obj=$appliance_linc; command=status_request incurred delay of 0.50 seconds; starting hop-count: 3 05/09/13 09:44:01 AM [Insteon::BaseObject] received status for $appliance_linc with on-level: 0%, hops left: 2 05/09/13 09:44:01 AM [Insteon::BaseObject] The Link Table Version for $appliance_linc has been updated to version number 01 |