espann Posted January 11, 2016 Posted January 11, 2016 I have an issue with my outlet dimmer 2472DWH. it suddenly stopped being recognized in the administrative console, and doesn't respond to the triggers anymore. I've tried Link Management>Start linking, but it isn't recognized, and I tried deleting the device and then >New Insteon Device, but it still isn't recognized. However before I deleted this device, I was able to turn it on and off from the administrative console. Any help would be greatly appreciated.
LeeG Posted January 11, 2016 Posted January 11, 2016 Try a Factory Reset of OutletLinc Dimmer before using New INSTEON Device to add it back. Do not have a load plugged into OutletLinc in case it is causing interference. The command to access Insteon Engine is the first command sent to the OutletLinc Dimmer by New INSTEON Device. If familiar with Event Trace at LEVEL 3 it will show command issued. Mon 01/11/2016 01:18:21 PM : [1a 84 bb ] Added to list of devices to link to ISY Mon 01/11/2016 01:18:21 PM : [iNST-TX-I1 ] 02 62 1A 84 BB 0F 0D 00 Mon 01/11/2016 01:18:21 PM : [iNST-ACK ] 02 62 1A.84.BB 0F 0D 00 06 (00) Mon 01/11/2016 01:18:21 PM : [iNST-SRX ] 02 50 1A.84.BB 22.80.0B 2B 0D 01 (01) Mon 01/11/2016 01:18:21 PM : [std-Direct Ack] 1A.84.BB-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 01/11/2016 01:18:21 PM : [iNST-TX-I1 ] 02 62 1A 84 BB 0F 10 00 Mon 01/11/2016 01:18:21 PM : [iNST-ACK ] 02 62 1A.84.BB 0F 10 00 06 ID-REQ (00) Mon 01/11/2016 01:18:21 PM : [iNST-SRX ] 02 50 1A.84.BB 22.80.0B 2B 10 00 ID-REQ (00) Mon 01/11/2016 01:18:21 PM : [std-Direct Ack] 1A.84.BB-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 01/11/2016 01:18:22 PM : [iNST-SRX ] 02 50 1A.84.BB 01.21.40 8B 01 00 (00) Mon 01/11/2016 01:18:22 PM : [std-Broadcast] 1A.84.BB-->01.21.40, Max Hops=3, Hops Left=2 Mon 01/11/2016 01:18:22 PM : [1A 84 BB 0 ] Calibrating engine version
espann Posted January 11, 2016 Author Posted January 11, 2016 Try a Factory Reset of OutletLinc Dimmer before using New INSTEON Device to add it back. Do not have a load plugged into OutletLinc in case it is causing interference. The command to access Insteon Engine is the first command sent to the OutletLinc Dimmer by New INSTEON Device. If familiar with Event Trace at LEVEL 3 it will show command issued. Mon 01/11/2016 01:18:21 PM : [1a 84 bb ] Added to list of devices to link to ISY Mon 01/11/2016 01:18:21 PM : [iNST-TX-I1 ] 02 62 1A 84 BB 0F 0D 00 Mon 01/11/2016 01:18:21 PM : [iNST-ACK ] 02 62 1A.84.BB 0F 0D 00 06 (00) Mon 01/11/2016 01:18:21 PM : [iNST-SRX ] 02 50 1A.84.BB 22.80.0B 2B 0D 01 (01) Mon 01/11/2016 01:18:21 PM : [std-Direct Ack] 1A.84.BB-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 01/11/2016 01:18:21 PM : [iNST-TX-I1 ] 02 62 1A 84 BB 0F 10 00 Mon 01/11/2016 01:18:21 PM : [iNST-ACK ] 02 62 1A.84.BB 0F 10 00 06 ID-REQ (00) Mon 01/11/2016 01:18:21 PM : [iNST-SRX ] 02 50 1A.84.BB 22.80.0B 2B 10 00 ID-REQ (00) Mon 01/11/2016 01:18:21 PM : [std-Direct Ack] 1A.84.BB-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 01/11/2016 01:18:22 PM : [iNST-SRX ] 02 50 1A.84.BB 01.21.40 8B 01 00 (00) Mon 01/11/2016 01:18:22 PM : [std-Broadcast] 1A.84.BB-->01.21.40, Max Hops=3, Hops Left=2 Mon 01/11/2016 01:18:22 PM : [1A 84 BB 0 ] Calibrating engine version thanks LeeG, I did try a factory reset but that gave the error "Cannot determine Insteon engine" And I couldn't do the factory reset as described in manual for the OutletLinc dimmer which says to turn off the circuit breaker; I just unplugged the lamp then held the setup button until it blinked green. I also tried to do it while it was blinking red, same result. Is there a way to factory reset without turning off the circuit breaker? If not I'll do that.
LeeG Posted January 11, 2016 Posted January 11, 2016 My User Guide lists two methods for Factory Reset. The first does not require turning breaker off. 1) If possible, remove all scene memberships prior to performing Factory Reset 2) Pess & hold the Set button on OutletLinc until it beeps LED will blink GREEN 3) Press & hold the OutletLinc’s Set button until it beeps again OutletLinc’s LED will blink RED 4) Double-tap the Set button, then immediately press & hold it for 3 seconds, and then release OutletLinc’s LED and plugged-in lamp will turn Off OutletLinc will emit a long ((((((beep)))))) followed by a single (Beep) As you begin to press & hold, OutletLinc will (Beep) There is additional information in 4) but could not Copy into post.
espann Posted February 2, 2016 Author Posted February 2, 2016 I'm still having problems installing new devices, this time I have a new LampLinc Dimmer that I cant install, it just gives back: "Cannot determine Insteon engine", whether I try installing near the PLM or far away. I'm wondering if it's somehow due to my new Windows 7 install on a new computer..
LeeG Posted February 2, 2016 Posted February 2, 2016 I run Windows 7 with no comm issues at 4.3.26 nor 4.4.2 where I am now. What is the PLM type, 2412 or 2413, and what is the PLM firmware? \What does Help | About display for Firmware level an UI level? Suggesting posting an Event Trace at LEVEL 3 taken while attempting to add device that will not add.
espann Posted February 2, 2016 Author Posted February 2, 2016 I run Windows 7 with no comm issues at 4.3.26 nor 4.4.2 where I am now. What is the PLM type, 2412 or 2413, and what is the PLM firmware? \What does Help | About display for Firmware level an UI level? Suggesting posting an Event Trace at LEVEL 3 taken while attempting to add device that will not add. Hi LeeG, my PLM is 2413S V 1.5, 1122, I don't know how to determine it's firmware, the ISY 994i shows Firmware v.4.3.26 (2015-10-13-11:35:11) Insteon UI:UD994 v4.3.26 (2015-10-13-11:35:11) Event Trace Level 3: Mon 02/01/2016 07:45:53 PM : [ELK ] Connect Failed Mon 02/01/2016 07:46:08 PM : [ELK ] Connect Mon 02/01/2016 07:46:18 PM : [ELK ] Connect Failed Mon 02/01/2016 07:46:33 PM : [ELK ] Connect Mon 02/01/2016 07:46:38 PM : [2e b4 ab ] Added to list of devices to link to ISY Mon 02/01/2016 07:46:38 PM : [iNST-TX-I1 ] 02 62 2E B4 AB 0F 0D 00 Mon 02/01/2016 07:46:38 PM : [iNST-ACK ] 02 62 2E.B4.AB 0F 0D 00 06 (00) Mon 02/01/2016 07:46:38 PM : [iNST-SRX ] 02 50 28.B4.AB 19.71.94 AB 0D FF (FF) Mon 02/01/2016 07:46:38 PM : [std-Direct Nack] 28.B4.AB-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 02/01/2016 07:46:38 PM : [iNST-DUP ] Previous message ignored. Mon 02/01/2016 07:46:39 PM : [iNST-SRX ] 02 50 28.B4.AB 19.71.94 AB 0D FF (FF) Mon 02/01/2016 07:46:39 PM : [std-Direct Nack] 28.B4.AB-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 02/01/2016 07:46:39 PM : [iNST-DUP ] Previous message ignored. Mon 02/01/2016 07:46:39 PM : [iNST-SRX ] 02 50 28.B4.AB 19.71.94 AB 0D FF (FF) Mon 02/01/2016 07:46:39 PM : [std-Direct Nack] 28.B4.AB-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 02/01/2016 07:46:39 PM : [iNST-DUP ] Previous message ignored. Mon 02/01/2016 07:46:39 PM : [iNST-SRX ] 02 50 28.B4.AB 19.71.94 AB 0D FF (FF) Mon 02/01/2016 07:46:39 PM : [std-Direct Nack] 28.B4.AB-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 02/01/2016 07:46:39 PM : [iNST-DUP ] Previous message ignored. Mon 02/01/2016 07:46:40 PM : [iNST-SRX ] 02 50 28.B4.AB 19.71.94 AB 0D FF (FF) Mon 02/01/2016 07:46:40 PM : [std-Direct Nack] 28.B4.AB-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 02/01/2016 07:46:40 PM : [iNST-DUP ] Previous message ignored. Mon 02/01/2016 07:46:43 PM : [ELK ] Connect Failed Mon 02/01/2016 07:46:49 PM : [iNST-TX-I1 ] 02 62 2E B4 AB 0F 0D 00 Mon 02/01/2016 07:46:49 PM : [iNST-ACK ] 02 62 2E.B4.AB 0F 0D 00 06 (00) Mon 02/01/2016 07:46:49 PM : [iNST-SRX ] 02 50 28.B4.AB 19.71.94 AB 0D FF (FF) Mon 02/01/2016 07:46:49 PM : [std-Direct Nack] 28.B4.AB-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 02/01/2016 07:46:49 PM : [iNST-DUP ] Previous message ignored. Mon 02/01/2016 07:46:50 PM : [iNST-SRX ] 02 50 28.B4.AB 19.71.94 AB 0D FF (FF) Mon 02/01/2016 07:46:50 PM : [std-Direct Nack] 28.B4.AB-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 02/01/2016 07:46:50 PM : [iNST-DUP ] Previous message ignored. Mon 02/01/2016 07:46:50 PM : [iNST-SRX ] 02 50 28.B4.AB 19.71.94 AB 0D FF (FF) Mon 02/01/2016 07:46:50 PM : [std-Direct Nack] 28.B4.AB-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 02/01/2016 07:46:50 PM : [iNST-DUP ] Previous message ignored. Mon 02/01/2016 07:46:50 PM : [iNST-SRX ] 02 50 28.B4.AB 19.71.94 AB 0D FF (FF) Mon 02/01/2016 07:46:50 PM : [std-Direct Nack] 28.B4.AB-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 02/01/2016 07:46:50 PM : [iNST-DUP ] Previous message ignored. Mon 02/01/2016 07:46:51 PM : [iNST-SRX ] 02 50 28.B4.AB 19.71.94 AB 0D FF (FF) Mon 02/01/2016 07:46:51 PM : [std-Direct Nack] 28.B4.AB-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 02/01/2016 07:46:51 PM : [iNST-DUP ] Previous message ignored. Mon 02/01/2016 07:46:58 PM : [ELK ] Connect Mon 02/01/2016 07:47:00 PM : [iNST-TX-I1 ] 02 62 2E B4 AB 0F 0D 00 Mon 02/01/2016 07:47:00 PM : [iNST-ACK ] 02 62 2E.B4.AB 0F 0D 00 06 (00) Mon 02/01/2016 07:47:00 PM : [iNST-SRX ] 02 50 28.B4.AB 19.71.94 AB 0D FF (FF) Mon 02/01/2016 07:47:00 PM : [std-Direct Nack] 28.B4.AB-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 02/01/2016 07:47:00 PM : [iNST-DUP ] Previous message ignored. Mon 02/01/2016 07:47:01 PM : [iNST-SRX ] 02 50 28.B4.AB 19.71.94 AB 0D FF (FF) Mon 02/01/2016 07:47:01 PM : [std-Direct Nack] 28.B4.AB-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 02/01/2016 07:47:01 PM : [iNST-DUP ] Previous message ignored. Mon 02/01/2016 07:47:01 PM : [iNST-SRX ] 02 50 28.B4.AB 19.71.94 AB 0D FF (FF) Mon 02/01/2016 07:47:01 PM : [std-Direct Nack] 28.B4.AB-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 02/01/2016 07:47:01 PM : [iNST-DUP ] Previous message ignored. Mon 02/01/2016 07:47:01 PM : [iNST-SRX ] 02 50 28.B4.AB 19.71.94 AB 0D FF (FF) Mon 02/01/2016 07:47:01 PM : [std-Direct Nack] 28.B4.AB-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 02/01/2016 07:47:01 PM : [iNST-DUP ] Previous message ignored. Mon 02/01/2016 07:47:02 PM : [iNST-SRX ] 02 50 28.B4.AB 19.71.94 AB 0D FF (FF) Mon 02/01/2016 07:47:02 PM : [std-Direct Nack] 28.B4.AB-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 02/01/2016 07:47:02 PM : [iNST-DUP ] Previous message ignored. Mon 02/01/2016 07:47:06 PM : [2E B4 AB 0 ] Failed to add device, reason 3 Mon 02/01/2016 07:47:06 PM : [All ] Writing 25 bytes to devices Mon 02/01/2016 07:47:06 PM : [iNST-TX-I1 ] 02 62 2D 3E 42 0F 0D 00 Mon 02/01/2016 07:47:06 PM : [iNST-ACK ] 02 62 2D.3E.42 0F 0D 00 06 (00) Mon 02/01/2016 07:47:08 PM : [ELK ] Connect Failed Mon 02/01/2016 07:47:15 PM : [iNST-TX-I1 ] 02 62 2D 3E 42 0F 0D 00 Mon 02/01/2016 07:47:15 PM : [iNST-ACK ] 02 62 2D.3E.42 0F 0D 00 06 (00) Mon 02/01/2016 07:47:22 PM : [ELK ] Connect Mon 02/01/2016 07:47:24 PM : [iNST-TX-I1 ] 02 62 2D 3E 42 0F 0D 00 Mon 02/01/2016 07:47:24 PM : [iNST-ACK ] 02 62 2D.3E.42 0F 0D 00 06 (00) Mon 02/01/2016 07:47:32 PM : [ELK ] Connect Failed Mon 02/01/2016 07:47:47 PM : [ELK ] Connect
LeeG Posted February 2, 2016 Posted February 2, 2016 The PLM Firmware is displayed by Tools | Diagnostics | PLM Info/Status. The PLM is near 5 years old. The Event Trace is showing either the device is malfunctioning or the PLM. Note the Insteon address of the device response does not match the command issued. The command is sent to 2E.B4.AB, the device response shows 28.B4.AB. Mon 02/01/2016 07:46:38 PM : [2e b4 ab ] Added to list of devices to link to ISY Mon 02/01/2016 07:46:38 PM : [iNST-TX-I1 ] 02 62 2E B4 AB 0F 0D 00 Mon 02/01/2016 07:46:38 PM : [iNST-ACK ] 02 62 2E.B4.AB 0F 0D 00 06 (00) Mon 02/01/2016 07:46:38 PM : [iNST-SRX ] 02 50 28.B4.AB 19.71.94 AB 0D FF (FF) Mon 02/01/2016 07:46:38 PM : [std-Direct Nack] 28.B4.AB-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 02/01/2016 07:46:49 PM : [iNST-TX-I1 ] 02 62 2E B4 AB 0F 0D 00 Mon 02/01/2016 07:46:49 PM : [iNST-ACK ] 02 62 2E.B4.AB 0F 0D 00 06 (00) Mon 02/01/2016 07:46:49 PM : [iNST-SRX ] 02 50 28.B4.AB 19.71.94 AB 0D FF (FF) Mon 02/01/2016 07:46:49 PM : [std-Direct Nack] 28.B4.AB-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 The general comm (Hops Left) is good. Try the other device that will not add to see if it's response Insteon address is also wrong. If both devices have similar symptoms I would Factory Reset the PLM, followed by a File | Restore Modem (PLM).
espann Posted February 2, 2016 Author Posted February 2, 2016 I run Windows 7 with no comm issues at 4.3.26 nor 4.4.2 where I am now. What is the PLM type, 2412 or 2413, and what is the PLM firmware? \What does Help | About display for Firmware level an UI level? Suggesting posting an Event Trace at LEVEL 3 taken while attempting to add device that will not add. Also since moving to my new computer I haven't been able to connect the ELK M1XEP either.
espann Posted February 2, 2016 Author Posted February 2, 2016 The PLM Firmware is displayed by Tools | Diagnostics | PLM Info/Status. The PLM is near 5 years old. The Event Trace is showing either the device is malfunctioning or the PLM. Note the Insteon address of the device response does not match the command issued. The command is sent to 2E.B4.AB, the device response shows 28.B4.AB. Mon 02/01/2016 07:46:38 PM : [2e b4 ab ] Added to list of devices to link to ISY Mon 02/01/2016 07:46:38 PM : [iNST-TX-I1 ] 02 62 2E B4 AB 0F 0D 00 Mon 02/01/2016 07:46:38 PM : [iNST-ACK ] 02 62 2E.B4.AB 0F 0D 00 06 (00) Mon 02/01/2016 07:46:38 PM : [iNST-SRX ] 02 50 28.B4.AB 19.71.94 AB 0D FF (FF) Mon 02/01/2016 07:46:38 PM : [std-Direct Nack] 28.B4.AB-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 02/01/2016 07:46:49 PM : [iNST-TX-I1 ] 02 62 2E B4 AB 0F 0D 00 Mon 02/01/2016 07:46:49 PM : [iNST-ACK ] 02 62 2E.B4.AB 0F 0D 00 06 (00) Mon 02/01/2016 07:46:49 PM : [iNST-SRX ] 02 50 28.B4.AB 19.71.94 AB 0D FF (FF) Mon 02/01/2016 07:46:49 PM : [std-Direct Nack] 28.B4.AB-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 The general comm (Hops Left) is good. Try the other device that will not add to see if it's response Insteon address is also wrong. If both devices have similar symptoms I would Factory Reset the PLM, followed by a File | Restore Modem (PLM). Tried another NEW LampLinc, same result. BTW, how do I reset the PLM? Here's the Event Trace for the new device: Mon 02/01/2016 08:48:53 PM : [ELK ] Connect Mon 02/01/2016 08:49:03 PM : [ELK ] Connect Failed Mon 02/01/2016 08:49:18 PM : [ELK ] Connect Mon 02/01/2016 08:49:21 PM : [2E AE 5C ] Added to list of devices to link to ISY Mon 02/01/2016 08:49:21 PM : [iNST-TX-I1 ] 02 62 2E AE 5C 0F 0D 00 Mon 02/01/2016 08:49:21 PM : [iNST-ACK ] 02 62 2E.AE.5C 0F 0D 00 06 (00) Mon 02/01/2016 08:49:21 PM : [iNST-SRX ] 02 50 16.AE.5C 19.71.94 AB 0D FF (FF) Mon 02/01/2016 08:49:21 PM : [std-Direct Nack] 16.AE.5C-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 02/01/2016 08:49:21 PM : [iNST-DUP ] Previous message ignored. Mon 02/01/2016 08:49:21 PM : [iNST-SRX ] 02 50 16.AE.5C 19.71.94 AB 0D FF (FF) Mon 02/01/2016 08:49:21 PM : [std-Direct Nack] 16.AE.5C-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 02/01/2016 08:49:21 PM : [iNST-DUP ] Previous message ignored. Mon 02/01/2016 08:49:22 PM : [iNST-SRX ] 02 50 16.AE.5C 19.71.94 AB 0D FF (FF) Mon 02/01/2016 08:49:22 PM : [std-Direct Nack] 16.AE.5C-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 02/01/2016 08:49:22 PM : [iNST-DUP ] Previous message ignored. Mon 02/01/2016 08:49:22 PM : [iNST-SRX ] 02 50 16.AE.5C 19.71.94 AB 0D FF (FF) Mon 02/01/2016 08:49:22 PM : [std-Direct Nack] 16.AE.5C-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 02/01/2016 08:49:22 PM : [iNST-DUP ] Previous message ignored. Mon 02/01/2016 08:49:23 PM : [iNST-SRX ] 02 50 16.AE.5C 19.71.94 AB 0D FF (FF) Mon 02/01/2016 08:49:23 PM : [std-Direct Nack] 16.AE.5C-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 02/01/2016 08:49:23 PM : [iNST-DUP ] Previous message ignored. Mon 02/01/2016 08:49:28 PM : [ELK ] Connect Failed Mon 02/01/2016 08:49:32 PM : [iNST-TX-I1 ] 02 62 2E AE 5C 0F 0D 00 Mon 02/01/2016 08:49:32 PM : [iNST-ACK ] 02 62 2E.AE.5C 0F 0D 00 06 (00) Mon 02/01/2016 08:49:32 PM : [iNST-SRX ] 02 50 16.AE.5C 19.71.94 AB 0D FF (FF) Mon 02/01/2016 08:49:32 PM : [std-Direct Nack] 16.AE.5C-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 02/01/2016 08:49:32 PM : [iNST-DUP ] Previous message ignored. Mon 02/01/2016 08:49:32 PM : [iNST-SRX ] 02 50 16.AE.5C 19.71.94 AB 0D FF (FF) Mon 02/01/2016 08:49:32 PM : [std-Direct Nack] 16.AE.5C-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 02/01/2016 08:49:32 PM : [iNST-DUP ] Previous message ignored. Mon 02/01/2016 08:49:33 PM : [iNST-SRX ] 02 50 16.AE.5C 19.71.94 AB 0D FF (FF) Mon 02/01/2016 08:49:33 PM : [std-Direct Nack] 16.AE.5C-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 02/01/2016 08:49:33 PM : [iNST-DUP ] Previous message ignored. Mon 02/01/2016 08:49:33 PM : [iNST-SRX ] 02 50 16.AE.5C 19.71.94 AB 0D FF (FF) Mon 02/01/2016 08:49:33 PM : [std-Direct Nack] 16.AE.5C-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 02/01/2016 08:49:33 PM : [iNST-DUP ] Previous message ignored. Mon 02/01/2016 08:49:34 PM : [iNST-SRX ] 02 50 16.AE.5C 19.71.94 AB 0D FF (FF) Mon 02/01/2016 08:49:34 PM : [std-Direct Nack] 16.AE.5C-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 02/01/2016 08:49:34 PM : [iNST-DUP ] Previous message ignored. Mon 02/01/2016 08:49:43 PM : [iNST-TX-I1 ] 02 62 2E AE 5C 0F 0D 00 Mon 02/01/2016 08:49:43 PM : [ELK ] Connect Mon 02/01/2016 08:49:43 PM : [iNST-ACK ] 02 62 2E.AE.5C 0F 0D 00 06 (00) Mon 02/01/2016 08:49:43 PM : [iNST-SRX ] 02 50 16.AE.5C 19.71.94 AB 0D FF (FF) Mon 02/01/2016 08:49:43 PM : [std-Direct Nack] 16.AE.5C-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 02/01/2016 08:49:43 PM : [iNST-DUP ] Previous message ignored. Mon 02/01/2016 08:49:43 PM : [iNST-SRX ] 02 50 16.AE.5C 19.71.94 AB 0D FF (FF) Mon 02/01/2016 08:49:43 PM : [std-Direct Nack] 16.AE.5C-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 02/01/2016 08:49:43 PM : [iNST-DUP ] Previous message ignored. Mon 02/01/2016 08:49:44 PM : [iNST-SRX ] 02 50 16.AE.5C 19.71.94 AB 0D FF (FF) Mon 02/01/2016 08:49:44 PM : [std-Direct Nack] 16.AE.5C-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 02/01/2016 08:49:44 PM : [iNST-DUP ] Previous message ignored. Mon 02/01/2016 08:49:44 PM : [iNST-SRX ] 02 50 16.AE.5C 19.71.94 AB 0D FF (FF) Mon 02/01/2016 08:49:44 PM : [std-Direct Nack] 16.AE.5C-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 02/01/2016 08:49:44 PM : [iNST-DUP ] Previous message ignored. Mon 02/01/2016 08:49:45 PM : [iNST-SRX ] 02 50 16.AE.5C 19.71.94 AB 0D FF (FF) Mon 02/01/2016 08:49:45 PM : [std-Direct Nack] 16.AE.5C-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 02/01/2016 08:49:45 PM : [iNST-DUP ] Previous message ignored. Mon 02/01/2016 08:49:49 PM : [2E AE 5C 0 ] Failed to add device, reason 3 Mon 02/01/2016 08:49:49 PM : [All ] Writing 25 bytes to devices Mon 02/01/2016 08:49:49 PM : [iNST-TX-I1 ] 02 62 2D 3E 42 0F 0D 00 Mon 02/01/2016 08:49:49 PM : [iNST-ACK ] 02 62 2D.3E.42 0F 0D 00 06 (00) Mon 02/01/2016 08:49:53 PM : [ELK ] Connect Failed Mon 02/01/2016 08:49:58 PM : [iNST-TX-I1 ] 02 62 2D 3E 42 0F 0D 00 Mon 02/01/2016 08:49:58 PM : [iNST-ACK ] 02 62 2D.3E.42 0F 0D 00 06 (00) Mon 02/01/2016 08:50:06 PM : [iNST-TX-I1 ] 02 62 2D 3E 42 0F 0D 00 Mon 02/01/2016 08:50:07 PM : [iNST-ACK ] 02 62 2D.3E.42 0F 0D 00 06 (00) Mon 02/01/2016 08:50:07 PM : [ELK ] Connect Mon 02/01/2016 08:50:17 PM : [ELK ] Connect Failed Mon 02/01/2016 08:50:32 PM : [ELK ] Connect
LeeG Posted February 2, 2016 Posted February 2, 2016 From PLM Quick Start guide To reset PowerLinc Modem to its original factory settings, unplug from wall outlet and wait 10 seconds. Press and hold Set button; while continuing to press and hold, plug back in. A long beep will sound; continue holding Set button until beep stops, then release. After several seconds, status LED will turn on to indicate reset is complete. This is an odd symptom I don't remember seeing before. Is there other Insteon or X10 traffic going to some other Insteon controller? Is the cable between PLM and ISY short, 4 feet?
MWareman Posted February 2, 2016 Posted February 2, 2016 Also since moving to my new computer I haven't been able to connect the ELK M1XEP either.Windows 10? If so - that's a well known issue. You'll have to find a <Windows 8.1 machine to upgrade the firmware on the M1XEP to one that will work with Windows 10. Basically, Microsoft removed SSL3 from Windows 10, and the older firmware only supports SSL3.
espann Posted February 2, 2016 Author Posted February 2, 2016 From PLM Quick Start guide To reset PowerLinc Modem to its original factory settings, unplug from wall outlet and wait 10 seconds. Press and hold Set button; while continuing to press and hold, plug back in. A long beep will sound; continue holding Set button until beep stops, then release. After several seconds, status LED will turn on to indicate reset is complete. This is an odd symptom I don't remember seeing before. Is there other Insteon or X10 traffic going to some other Insteon controller? Is the cable between PLM and ISY short, 4 feet? no other Insteon traffic that I know of. The cable is short, about 4-5 feet. Windows 10? If so - that's a well known issue. You'll have to find a <Windows 8.1 machine to upgrade the firmware on the M1XEP to one that will work with Windows 10. Basically, Microsoft removed SSL3 from Windows 10, and the older firmware only supports SSL3. No it's Windows 7 x64, SP1
LeeG Posted February 2, 2016 Posted February 2, 2016 Okay. Try the PLM Factory Reset and Restore Modem (PLM). MWareman See post #5, he is on Windows 7.
espann Posted February 2, 2016 Author Posted February 2, 2016 From PLM Quick Start guide To reset PowerLinc Modem to its original factory settings, unplug from wall outlet and wait 10 seconds. Press and hold Set button; while continuing to press and hold, plug back in. A long beep will sound; continue holding Set button until beep stops, then release. After several seconds, status LED will turn on to indicate reset is complete. This is an odd symptom I don't remember seeing before. Is there other Insteon or X10 traffic going to some other Insteon controller? Is the cable between PLM and ISY short, 4 feet? Now I can't even reset the PLM! After doing what you suggested above, the Administrative console is showing all red exclamations. Somehow I think this PLM may have failed..
jerlands Posted February 2, 2016 Posted February 2, 2016 Now I can't even reset the PLM! After doing what you suggested above, the Administrative console is showing all red exclamations. Somehow I think this PLM may have failed.. Remove power from ISY, unplug PLM and follow reset instructions, wait for PLM to settle out (20 seconds) then power up ISY. Jon...
LeeG Posted February 2, 2016 Posted February 2, 2016 Was the File | Restore Modem (PLM) issued to rebuild PLM link database after Factory Reset?
Brian H Posted February 2, 2016 Posted February 2, 2016 The 2413S PLMs have a history of failing. Usually anytime after the two year warranty. My V1.5 failed in two years four months. So another possibility is it has failed. If the restore works for awhile and then the Link Database is almost empty or it works for a short time after a power cycle. That is another indication it is failing. There is a long thread here on how some of us have rebuilt them. http://forum.universal-devices.com/topic/13866-repair-of-2413s-plm-when-the-power-supply-fails/
espann Posted February 3, 2016 Author Posted February 3, 2016 Was the File | Restore Modem (PLM) issued to rebuild PLM link database after Factory Reset? Yes the File | Restore Modem (PLM) was issued to rebuild PLM link database after Factory Reset. So now if the PLM will not allow itself to be reset, (meaning it does not emit a long beep while holding the Set button) does that mean conclusively that it is dead? And the ISY does not show any lights except the Power light but I assume that could be because of faulty PLM too.. I did buy the ISY less than 2 years ago so maybe it's still under warranty. I'm about to look for another way to program these devices!
stusviews Posted February 3, 2016 Posted February 3, 2016 The ISY should have only the power LED lit unless there's an active transmission which is usually brief. The most likely culprit is the PLM, not the ISY.
Brian H Posted February 3, 2016 Posted February 3, 2016 The PLM is a more likely candidate to have failed. Over the ISY994i. The strange behavior it is showing. Could be the power supply that is known to fail causing all kinds of strange happenings. If the LED on the side is out, flickering or real dim. The power supply has probably failed. The 2413S should have a two year warranty but your hardware revision sounds like it is older than two years old.
LeeG Posted February 3, 2016 Posted February 3, 2016 espann I found an old 2413S PLM, about 1.5 years older than yours, and it does not beep. That is one of the issues running a device years older than current documentation. The PLM may have failed being 5 years old but the lack of a beep is not an indication of problem.
Brian H Posted February 3, 2016 Posted February 3, 2016 I have a hardware V1.5 2413S PLM and a Factory Reset does not sound the internal beeper. My hardware V1.5 is one of the ones that failed for me and I rebuilt the power supply.
espann Posted February 3, 2016 Author Posted February 3, 2016 The PLM is a more likely candidate to have failed. Over the ISY994i. The strange behavior it is showing. Could be the power supply that is known to fail causing all kinds of strange happenings. If the LED on the side is out, flickering or real dim. The power supply has probably failed. The 2413S should have a two year warranty but your hardware revision sounds like it is older than two years old. Thanks Brian, the light on the PLM is not dim, but the unit just does not reset, probably causing everything else to not function. I don't remember if I got the PLM with the new ISY994i upgrade or not. I'll probably end up having to buy another PLM. I see them on eBay and elsewhere.
Techman Posted February 3, 2016 Posted February 3, 2016 Thanks Brian, the light on the PLM is not dim, but the unit just does not reset, probably causing everything else to not function. I don't remember if I got the PLM with the new ISY994i upgrade or not. I'll probably end up having to buy another PLM. I see them on eBay and elsewhere. I would suggest buying it directly from Smarthome, that way you're assured to get the most current hardware and firmware versions along with the 2 year warranty
Recommended Posts
Archived
This topic is now archived and is closed to further replies.