JMM Posted December 13, 2014 Posted December 13, 2014 I am trying to link a dual-band LampLimp dimmer (2457D2) into an new installation with no other devices installed.I had no success with the device placed where I want it, so I moved it to a socket adjacent to the one into which the PLM is plugged. In addition, I put an access point in the same room. With the dimmer as close to the PLM as is physically possible, the linking process still fails. In my house, all the florescent lights have been replaced by led lights and all the major electronic gadgets (computers and a/v stuff) are connected to power via FilterLincs and AF120s. When I try to link the dimmer, I get the following log: [23 65 f4 ] Added to list of devices to link to ISY [iNST-TX-I1 ] 02 62 23 65 F4 0F 0D 00 [iNST-ACK ] 02 62 23.65.F4 0F 0D 00 06 (00) [iNST-SRX ] 02 50 23.65.F4 30.DC.20 AF 0D FF (FF) [std-Direct Nack] 23.65.F4-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 [iNST-TX-I2CS] 02 62 23 65 F4 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 [iNST-ACK ] 02 62 23.65.F4 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 06 LNK-ON (01) [iNST-SRX ] 02 50 23.65.F4 30.DC.20 2F 09 01 LNK-ON (01) [std-Direct Ack] 23.65.F4-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 [LNK-BGN ] 02 64 01 00 06 [LNK-STAT ] 02 53 M(01) gid=00 23.65.F4 010E 41 [iNST-TX-I1 ] 02 62 23 65 F4 0F 0D 00 [LNK-END ] 02 65 06 [std MH ] Unexpected Ack imCmd=65 cmd1= 0xF4 [iNST-ACK ] 02 62 23.65.F4 0F 0D 00 06 (00) [iNST-TX-I1 ] 02 62 23 65 F4 0F 0D 00 [iNST-ACK ] 02 62 23.65.F4 0F 0D 00 06 (00) [iNST-SRX ] 02 50 23.65.F4 30.DC.20 2F 0D 02 (02) [std-Direct Ack] 23.65.F4-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 [iNST-TX-I1 ] 02 62 23 65 F4 0F 10 00 [iNST-ACK ] 02 62 23.65.F4 0F 10 00 06 ID-REQ (00) [iNST-SRX ] 02 50 23.65.F4 30.DC.20 23 0D 02 (02) [std-Direct Ack] 23.65.F4-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 [iNST-DUP ] Previous message ignored. [iNST-SRX ] 02 50 23.65.F4 30.DC.20 2F 10 00 ID-REQ (00) [std-Direct Ack] 23.65.F4-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 [iNST-SRX ] 02 50 23.65.F4 30.DC.20 23 10 00 ID-REQ (00) [std-Direct Ack] 23.65.F4-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 [iNST-TX-I1 ] 02 62 23 65 F4 0F 10 00 [iNST-ACK ] 02 62 23.65.10 00 10 00 06 ID-REQ (00) [iNST-TX-I1 ] 02 62 23 65 F4 0F 10 00 [iNST-ACK ] 02 62 23.65.F4 0F 10 00 06 ID-REQ (00) [23 65 F4 0 ] Calibrating engine version [iNST-TX-I2CS] 02 62 23 65 F4 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 [iNST-ACK ] 02 62 23.65.F4 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) [iNST-SRX ] 02 50 23.65.F4 30.DC.20 2F 2F 00 (00) [std-Direct Ack] 23.65.F4-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 [iNST-SRX ] 02 50 23.65.F4 30.DC.20 23 2F 00 (00) [std-Direct Ack] 23.65.F4-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 [iNST-TX-I2CS] 02 62 23 65 F4 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 [iNST-ACK ] 02 62 23.65.F4 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) [iNST-SRX ] 02 50 23.65.F4 30.DC.20 2F 2F 00 (00) [std-Direct Ack] 23.65.F4-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 [iNST-SRX ] 02 50 23.65.F4 30.DC.20 23 2F 00 (00) [std-Direct Ack] 23.65.F4-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 [iNST-TX-I2CS] 02 62 23 65 F4 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 [iNST-ACK ] 02 62 23.65.F4 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) [23 65 F4 0 ] Failed to add device, reason 9 [All ] Writing 0 bytes to devices [ Time] 14:42:27 0(0) [iNST-SRX ] 02 50 23.65.F4 30.DC.20 2F 2F 00 (00) [std-Direct Ack] 23.65.F4-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 [iNST-DUP ] Previous message ignored. Reason 9 has to do with the device link table in the dimmer, if I understand correctly. I don't understand why the linking process would terminate after having gone on for so long. Also is there documentation on the meaning of the log messages (short of becoming an Insteon developer by paying $200)? Why would the communication process be so unreliable when the communicating devices are as physically close as they can be? Any help on this problem would be greatly appreciated. Thanks.
LeeG Posted December 14, 2014 Posted December 14, 2014 There are two issues with the command responses. The ox10 ID_REQ fails to return the message in Red. Finally the 0x2F command which is asking for the link database address does not get the Blue message response which has the link database address. Suggest doing a Factory Reset of LampLinc and try adding again. Sat 12/13/2014 07:41:36 PM : [1c fd d5 ] Added to list of devices to link to ISY Sat 12/13/2014 07:41:36 PM : [iNST-TX-I1 ] 02 62 1C FD D5 0F 0D 00 Sat 12/13/2014 07:41:36 PM : [iNST-ACK ] 02 62 1C.FD.D5 0F 0D 00 06 (00) Sat 12/13/2014 07:41:36 PM : [iNST-SRX ] 02 50 1C.FD.D5 22.80.0B 2B 0D 02 (02) Sat 12/13/2014 07:41:36 PM : [std-Direct Ack] 1C.FD.D5-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 12/13/2014 07:41:36 PM : [iNST-TX-I1 ] 02 62 1C FD D5 0F 10 00 Sat 12/13/2014 07:41:36 PM : [iNST-ACK ] 02 62 1C.FD.D5 0F 10 00 06 ID-REQ (00) Sat 12/13/2014 07:41:36 PM : [iNST-SRX ] 02 50 1C.FD.D5 22.80.0B 2B 10 00 ID-REQ (00) Sat 12/13/2014 07:41:36 PM : [std-Direct Ack] 1C.FD.D5-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 12/13/2014 07:41:37 PM : [iNST-SRX ] 02 50 1C.FD.D5 07.00.41 8B 01 00 (00) Sat 12/13/2014 07:41:37 PM : [std-Broadcast] 1C.FD.D5-->07.00.41, Max Hops=3, Hops Left=2 Sat 12/13/2014 07:41:37 PM : [1C FD D5 0 ] Calibrating engine version Sat 12/13/2014 07:41:37 PM : [iNST-TX-I2CS] 02 62 1C FD D5 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Sat 12/13/2014 07:41:37 PM : [iNST-ACK ] 02 62 1C.FD.D5 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Sat 12/13/2014 07:41:37 PM : [iNST-SRX ] 02 50 1C.FD.D5 22.80.0B 2B 2F 00 (00) Sat 12/13/2014 07:41:37 PM : [std-Direct Ack] 1C.FD.D5-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 12/13/2014 07:41:38 PM : [iNST-ERX ] 02 51 1C FD D5 22 80 0B 11 2F 00 01 01 0F FF 20 A2 00 22 80 0B FF 1F 01 33 Sat 12/13/2014 07:41:38 PM : [Ext-Direct ] 1C.FD.D5-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Sat 12/13/2014 07:41:38 PM : [1C FD D5 0 ] Using Database Link Table offset 0x0FF8 (reported 0x0FF8)
Recommended Posts
Archived
This topic is now archived and is closed to further replies.