PaulRiley Posted November 5, 2013 Posted November 5, 2013 Hello, I'm wondering if anyone else has seen the problem of a full restore to device only working after several attempts? In the log, it appears that the difference between a successful attempt and a failure is the ISY "Writing 0 bytes to devices". Any idea what is going on? Here is the log of a failed restore Tue 11/05/2013 10:35:48 AM : [ 24 DF F3 1] Preparing Device 'Kitchen:Hall Lights ' for Restore Tue 11/05/2013 10:35:48 AM : [ 24 DF F3 1] Device 'Kitchen:Hall Lights ' ready for Full Restore Tue 11/05/2013 10:35:48 AM : [All ] Writing 0 bytes to devices Tue 11/05/2013 10:35:59 AM : [ 24 DF F3 1] ERR 0 Tue 11/05/2013 10:35:59 AM : [ 24 DF F3 1] ST 255 Tue 11/05/2013 10:35:59 AM : [ 24 DF F3 1] OL 255 Tue 11/05/2013 10:35:59 AM : [ 24 DF F3 1] RR 27 Followed by a successful restore Tue 11/05/2013 10:36:37 AM : [ 24 DF F3 1] Preparing Device 'Kitchen:Hall Lights ' for Restore Tue 11/05/2013 10:36:37 AM : [ 24 DF F3 1] Device 'Kitchen:Hall Lights ' ready for Full Restore Tue 11/05/2013 10:36:37 AM : [All ] Writing 115 bytes to devices Tue 11/05/2013 10:36:56 AM : [24 DF F3 1 ] Link 0 : 0FF8 [A20025150BFF1F01] Writing [A20025150BFF1F01] Tue 11/05/2013 10:36:56 AM : [PLM ] Group 0 : Writing Controller Link matching [24 DF F3 1 ] Link 0 : 0FF8 [A20025150BFF1F01] Tue 11/05/2013 10:36:57 AM : [24 DF F3 1 ] Link 1 : 0FF0 [A20124A1B7FF1B01] Writing [A20124A1B7FF1B01] Tue 11/05/2013 10:36:58 AM : [24 DF F3 1 ] Link 2 : 0FE8 [A2012921F8FF1B01] Writing [A2012921F8FF1B01] Tue 11/05/2013 10:36:58 AM : [24 DF F3 1 ] Link 3 : 0FE0 [A203256BBDFF1F01] Writing [A203256BBDFF1F01] Tue 11/05/2013 10:36:59 AM : [24 DF F3 1 ] Link 4 : 0FD8 [A2032921F8FF1B01] Writing [A2032921F8FF1B01] Tue 11/05/2013 10:37:00 AM : [24 DF F3 1 ] Link 5 : 0FD0 [A2042921F8FF1B01] Writing [A2042921F8FF1B01] Tue 11/05/2013 10:37:00 AM : [24 DF F3 1 ] Link 6 : 0FC8 [A2062921F84C1B01] Writing [A2062921F84C1B01] Tue 11/05/2013 10:37:01 AM : [24 DF F3 1 ] Link 7 : 0FC0 [A21325150BFF1B01] Writing [A21325150BFF1B01] Tue 11/05/2013 10:37:02 AM : [PLM ] Group 19 : Writing Controller Link matching [24 DF F3 1 ] Link 7 : 0FC0 [A21325150BFF1B01] Tue 11/05/2013 10:37:02 AM : [24 DF F3 1 ] Link 8 : 0FB8 [A21625150BFF1201] Writing [A21625150BFF1201] Tue 11/05/2013 10:37:03 AM : [PLM ] Group 22 : Writing Controller Link matching [24 DF F3 1 ] Link 8 : 0FB8 [A21625150BFF1201] Tue 11/05/2013 10:37:03 AM : [24 DF F3 1 ] Link 9 : 0FB0 [A21925150BFF1F01] Writing [A21925150BFF1F01] Tue 11/05/2013 10:37:04 AM : [PLM ] Group 25 : Writing Controller Link matching [24 DF F3 1 ] Link 9 : 0FB0 [A21925150BFF1F01] Tue 11/05/2013 10:37:04 AM : [24 DF F3 1 ] Link 10 : 0FA8 [A21A25150BFF1B01] Writing [A21A25150BFF1B01] Tue 11/05/2013 10:37:05 AM : [PLM ] Group 26 : Writing Controller Link matching [24 DF F3 1 ] Link 10 : 0FA8 [A21A25150BFF1B01] Tue 11/05/2013 10:37:05 AM : [24 DF F3 1 ] Link 11 : 0FA0 [E20124A1B7010001] Writing [E20124A1B7010001] Tue 11/05/2013 10:37:06 AM : [24 DF F3 1 ] Link 12 : 0F98 [E20125150B010001] Writing [E20125150B010001] Tue 11/05/2013 10:37:06 AM : [PLM ] Group 1 : Writing Responder Link matching [24 DF F3 1 ] Link 12 : 0F98 [E20125150B010001] Tue 11/05/2013 10:37:07 AM : [24 DF F3 1 ] Link 13 : 0F90 [E2012921F8010001] Writing [E2012921F8010001] Tue 11/05/2013 10:37:08 AM : [24 DF F3 1 ] Link 14 : 0F88 [0000000000000000] Writing [00..............] Tue 11/05/2013 10:37:08 AM : [24 DF F3 1 ] Link 15 : 0F80 : Writing High Water Byte Tue 11/05/2013 10:37:11 AM : [24 DF F3 1 ] Memory : Write dbAddr=0x0032 [FF] cmd1=0x2E cmd2=0x00 Tue 11/05/2013 10:37:12 AM : [24 DF F3 1 ] Memory : Write dbAddr=0x0021 [1B] cmd1=0x2E cmd2=0x00
LeeG Posted November 5, 2013 Posted November 5, 2013 The Event Trace has to be run at LEVEL 3 to be useful in this situation. The Err 0 indicates an error happened. Likely an intermittent comm problem but an event trace at LEVEL 3 (which shows commands issued and device response) is needed to be sure.
PaulRiley Posted November 5, 2013 Author Posted November 5, 2013 Hmm... I don't see any difference in the logging when there is a restore failure. Do I need to do something else to set the logging level besides choosing it the Event Viewer dropdown? Restore not working at level 3 Tue 11/05/2013 11:24:30 AM : [ 24 DF F3 1] Preparing Device 'Kitchen:Hall Lights ' for Restore Tue 11/05/2013 11:24:30 AM : [ 24 DF F3 1] Device 'Kitchen:Hall Lights ' ready for Full Restore Tue 11/05/2013 11:24:30 AM : [All ] Writing 0 bytes to devices But if I do a query, it seems to reset the ISY which then attempts a restore (which fails with an error) Query: Tue 11/05/2013 11:24:36 AM : [iNST-TX-I1 ] 02 62 24 DF F3 0F 19 00 Tue 11/05/2013 11:24:36 AM : [iNST-ACK ] 02 62 24.DF.F3 0F 19 00 06 LTSREQ (LIGHT) Tue 11/05/2013 11:24:45 AM : [iNST-TX-I1 ] 02 62 24 DF F3 0F 19 00 Tue 11/05/2013 11:24:45 AM : [iNST-ACK ] 02 62 24.DF.F3 0F 19 00 06 LTSREQ (LIGHT) Tue 11/05/2013 11:24:54 AM : [iNST-TX-I1 ] 02 62 24 DF F3 0F 19 00 Tue 11/05/2013 11:24:54 AM : [iNST-ACK ] 02 62 24.DF.F3 0F 19 00 06 LTSREQ (LIGHT) Tue 11/05/2013 11:24:56 AM : [iNST-SRX ] 02 50 24.DF.F3 25.15.0B 2B 11 FF LTONRR (FF) Tue 11/05/2013 11:24:56 AM : [std-Direct Ack] 24.DF.F3-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 11/05/2013 11:24:56 AM : [ 24 DF F3 1] ERR 0 Tue 11/05/2013 11:24:56 AM : [ 24 DF F3 1] ST 255 Tue 11/05/2013 11:24:56 AM : [ 24 DF F3 1] OL 255 Tue 11/05/2013 11:24:56 AM : [ 24 DF F3 1] RR 27 Restore attempt started but failed Tue 11/05/2013 11:25:02 AM : [ 24 DF F3 1] Preparing Device 'Kitchen:Hall Lights ' for Restore Tue 11/05/2013 11:25:02 AM : [ 24 DF F3 1] Device 'Kitchen:Hall Lights ' ready for Full Restore Tue 11/05/2013 11:25:02 AM : [All ] Writing 115 bytes to devices Tue 11/05/2013 11:25:02 AM : [iNST-TX-I1 ] 02 62 24 DF F3 0F 0D 00 Tue 11/05/2013 11:25:02 AM : [iNST-ACK ] 02 62 24.DF.F3 0F 0D 00 06 (00) Tue 11/05/2013 11:25:04 AM : [iNST-SRX ] 02 50 24.DF.F3 25.15.0B 2B 0D 02 (02) Tue 11/05/2013 11:25:04 AM : [std-Direct Ack] 24.DF.F3-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 11/05/2013 11:25:04 AM : [24 DF F3 0 ] Calibrating engine version Tue 11/05/2013 11:25:04 AM : [iNST-TX-I2CS] 02 62 24 DF F3 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Tue 11/05/2013 11:25:04 AM : [iNST-ACK ] 02 62 24.DF.F3 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Tue 11/05/2013 11:25:13 AM : [iNST-TX-I2CS] 02 62 24 DF F3 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Tue 11/05/2013 11:25:13 AM : [iNST-ACK ] 02 62 24.DF.F3 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Tue 11/05/2013 11:25:22 AM : [iNST-TX-I2CS] 02 62 24 DF F3 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Tue 11/05/2013 11:25:22 AM : [iNST-ACK ] 02 62 24.DF.F3 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Tue 11/05/2013 11:25:26 AM : [ 24 DF F3 1] ERR 1
LeeG Posted November 5, 2013 Posted November 5, 2013 There is comm problem of some kind. The device may have been marked with a Red !. The Query cleared that and then the Restore tried to run. First, the Query took 3 attempts before the device answered. Look at the Query trace, there are three Query commands issued with only the third attempt getting a device response. After the Query the Restore worked for the standard command that asked for the Insteon Engine level. The device responded with an I2CS indicator. The next three Extended messages asked for the link database start address. The device did not respond to any of the three Extended messages sent to the device. When the device responds it responds with Hops Left=2 which is as good as comm gets. However, it takes several attemps before the device responds to a command and in the case of the Extended messages the device did not respond at all. Start with the PLM location and circuit. Are there other electonics powered from the same circuit that are not on a FilterLinc. If the PLM location is okay look for something on the circuit that is powering the device.
LeeG Posted November 20, 2013 Posted November 20, 2013 bevlin761 Sorry, I don't understand the last post.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.