CJVann Posted October 26, 2012 Share Posted October 26, 2012 I received a defective EZIO2x4 that continuously sent On/Off signals when it was plugged in (not connected to anything yet), causing all Insteon devices on the network to flash from powerline traffic. There were no replacements in stock at the time for exchange, so I had to wait for a new batch of units to arrive. I've now had 2 units from this new batch, both with an identical, but new, problem. They won't link to my ISY99i (the first one linked perfectly, no issues). The ISY99i detects them during linking: "Adding Compacta EZIO 2x4: INSTEON I/O Controller v.FF", then says "The following devices could not be added: xx.xx.xx Compacta EZIO 2x4: INSTEON I/O Controller v.FF - Cannot determine device link table address" The only other notable message is "May not fully support i2, reverting to i1". Although it says "v.FF", the back of the unit says V1.7. Is this a defective lot? SmartHome had me upgrade ISY from V3.3.2 to V3.3.3, but it still does the same thing. SmartHome has said there's no point in sending a replacement because it probably won't work either. Is there anything else to try before I sent back for refund? Link to comment Share on other sites More sharing options...
Xathros Posted October 26, 2012 Share Posted October 26, 2012 Lets start by running the event viewer at level 3 while attempting to add one. Post the trace. -Xathros Link to comment Share on other sites More sharing options...
CJVann Posted October 26, 2012 Author Share Posted October 26, 2012 Thank you - Level 3 Event log follows: Fri 10/26/2012 02:48:50 PM : Start Insteon Device Linking Mode Fri 10/26/2012 02:48:50 PM : [LNK-BGN ] 02 64 01 00 06 Fri 10/26/2012 02:49:07 PM : [LNK-STAT ] 02 53 M(01) gid=00 1E.79.49 0703 FF Fri 10/26/2012 02:49:07 PM : [1E.79.49 00] Linked device type=07.03 fw=FF Fri 10/26/2012 02:49:07 PM : [1E 79 49 0 ] Added to list of devices to link to ISY Fri 10/26/2012 02:49:07 PM : [LNK-BGN ] 02 64 01 00 06 Fri 10/26/2012 02:49:21 PM : Stop Insteon Device Linking Mode, Final processing to follow Fri 10/26/2012 02:49:21 PM : [LNK-END ] 02 65 06 : : Unexpected, ignored (65) Fri 10/26/2012 02:49:21 PM : [iNST-TX-I1 ] 02 62 1E 79 49 0F 0D 00 Fri 10/26/2012 02:49:22 PM : [iNST-ACK ] 02 62 1E.79.49 0F 0D 00 06 (00) Fri 10/26/2012 02:49:22 PM : [iNST-SRX ] 02 50 1E.79.49 19.74.BC 2B 0D 01 (01) Fri 10/26/2012 02:49:22 PM : [std-Direct Ack] 1E.79.49-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 10/26/2012 02:49:22 PM : [1E 79 49 0 ] Calibrating engine version Fri 10/26/2012 02:49:22 PM : [1E 79 49 0 ] May not fully support i2, reverting to i1 Fri 10/26/2012 02:49:22 PM : [iNST-TX-I1 ] 02 62 1E 79 49 0F 28 0F Fri 10/26/2012 02:49:22 PM : [iNST-ACK ] 02 62 1E.79.49 0F 28 0F 06 SET-MSB(0F) Fri 10/26/2012 02:49:22 PM : [iNST-SRX ] 02 50 1E.79.49 19.74.BC 2B 28 0F SET-MSB(0F) Fri 10/26/2012 02:49:22 PM : [std-Direct Ack] 1E.79.49-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 10/26/2012 02:49:22 PM : [iNST-TX-I1 ] 02 62 1E 79 49 0F 2B FF Fri 10/26/2012 02:49:23 PM : [iNST-ACK ] 02 62 1E.79.49 0F 2B FF 06 PEEK (FF) Fri 10/26/2012 02:49:23 PM : [iNST-SRX ] 02 50 1E.79.49 19.74.BC 2B 2B 01 PEEK (01) Fri 10/26/2012 02:49:23 PM : [std-Direct Ack] 1E.79.49-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 10/26/2012 02:49:23 PM : [iNST-TX-I1 ] 02 62 1E 79 49 0F 28 1F Fri 10/26/2012 02:49:23 PM : [iNST-ACK ] 02 62 1E.79.49 0F 28 1F 06 SET-MSB(1F) Fri 10/26/2012 02:49:23 PM : [iNST-SRX ] 02 50 1E.79.49 19.74.BC 2B 28 1F SET-MSB(1F) Fri 10/26/2012 02:49:23 PM : [std-Direct Ack] 1E.79.49-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 10/26/2012 02:49:23 PM : [iNST-TX-I1 ] 02 62 1E 79 49 0F 2B FF Fri 10/26/2012 02:49:24 PM : [iNST-ACK ] 02 62 1E.79.49 0F 2B FF 06 PEEK (FF) Fri 10/26/2012 02:49:24 PM : [iNST-SRX ] 02 50 1E.79.49 19.74.BC 2B 2B 00 PEEK (00) Fri 10/26/2012 02:49:24 PM : [std-Direct Ack] 1E.79.49-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 10/26/2012 02:49:24 PM : [iNST-TX-I1 ] 02 62 1E 79 49 0F 28 3F Fri 10/26/2012 02:49:24 PM : [iNST-ACK ] 02 62 1E.79.49 0F 28 3F 06 SET-MSB(3F) Fri 10/26/2012 02:49:24 PM : [iNST-SRX ] 02 50 1E.79.49 19.74.BC 2B 28 3F SET-MSB(3F) Fri 10/26/2012 02:49:24 PM : [std-Direct Ack] 1E.79.49-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 10/26/2012 02:49:24 PM : [iNST-TX-I1 ] 02 62 1E 79 49 0F 2B FF Fri 10/26/2012 02:49:25 PM : [iNST-ACK ] 02 62 1E.79.49 0F 2B FF 06 PEEK (FF) Fri 10/26/2012 02:49:25 PM : [iNST-SRX ] 02 50 1E.79.49 19.74.BC 2B 2B 00 PEEK (00) Fri 10/26/2012 02:49:25 PM : [std-Direct Ack] 1E.79.49-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 10/26/2012 02:49:25 PM : [iNST-TX-I1 ] 02 62 1E 79 49 0F 28 0F Fri 10/26/2012 02:49:25 PM : [iNST-ACK ] 02 62 1E.79.49 0F 28 0F 06 SET-MSB(0F) Fri 10/26/2012 02:49:26 PM : [iNST-SRX ] 02 50 1E.79.49 19.74.BC 2B 28 0F SET-MSB(0F) Fri 10/26/2012 02:49:26 PM : [std-Direct Ack] 1E.79.49-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 10/26/2012 02:49:26 PM : [iNST-TX-I1 ] 02 62 1E 79 49 0F 2B FF Fri 10/26/2012 02:49:26 PM : [iNST-ACK ] 02 62 1E.79.49 0F 2B FF 06 PEEK (FF) Fri 10/26/2012 02:49:26 PM : [iNST-SRX ] 02 50 1E.79.49 19.74.BC 2B 2B 01 PEEK (01) Fri 10/26/2012 02:49:26 PM : [std-Direct Ack] 1E.79.49-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 10/26/2012 02:49:26 PM : [iNST-TX-I1 ] 02 62 1E 79 49 0F 29 01 Fri 10/26/2012 02:49:26 PM : [iNST-ACK ] 02 62 1E.79.49 0F 29 01 06 POKE (01) Fri 10/26/2012 02:49:26 PM : [iNST-SRX ] 02 50 1E.79.49 19.74.BC 2B 29 01 POKE (01) Fri 10/26/2012 02:49:26 PM : [std-Direct Ack] 1E.79.49-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 10/26/2012 02:49:26 PM : [iNST-TX-I1 ] 02 62 1E 79 49 0F 28 1F Fri 10/26/2012 02:49:27 PM : [iNST-ACK ] 02 62 1E.79.49 0F 28 1F 06 SET-MSB(1F) Fri 10/26/2012 02:49:27 PM : [iNST-SRX ] 02 50 1E.79.49 19.74.BC 2B 28 1F SET-MSB(1F) Fri 10/26/2012 02:49:27 PM : [std-Direct Ack] 1E.79.49-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 10/26/2012 02:49:27 PM : [iNST-TX-I1 ] 02 62 1E 79 49 0F 2B FF Fri 10/26/2012 02:49:27 PM : [iNST-ACK ] 02 62 1E.79.49 0F 2B FF 06 PEEK (FF) Fri 10/26/2012 02:49:27 PM : [iNST-SRX ] 02 50 1E.79.49 19.74.BC 2B 2B 00 PEEK (00) Fri 10/26/2012 02:49:27 PM : [std-Direct Ack] 1E.79.49-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 10/26/2012 02:49:27 PM : [iNST-TX-I1 ] 02 62 1E 79 49 0F 29 02 Fri 10/26/2012 02:49:28 PM : [iNST-ACK ] 02 62 1E.79.49 0F 29 02 06 POKE (02) Fri 10/26/2012 02:49:28 PM : [iNST-SRX ] 02 50 1E.79.49 19.74.BC 2B 29 02 POKE (02) Fri 10/26/2012 02:49:28 PM : [std-Direct Ack] 1E.79.49-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 10/26/2012 02:49:28 PM : [iNST-TX-I1 ] 02 62 1E 79 49 0F 28 3F Fri 10/26/2012 02:49:28 PM : [iNST-ACK ] 02 62 1E.79.49 0F 28 3F 06 SET-MSB(3F) Fri 10/26/2012 02:49:28 PM : [iNST-SRX ] 02 50 1E.79.49 19.74.BC 2B 28 3F SET-MSB(3F) Fri 10/26/2012 02:49:28 PM : [std-Direct Ack] 1E.79.49-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 10/26/2012 02:49:28 PM : [iNST-TX-I1 ] 02 62 1E 79 49 0F 2B FF Fri 10/26/2012 02:49:29 PM : [iNST-ACK ] 02 62 1E.79.49 0F 2B FF 06 PEEK (FF) Fri 10/26/2012 02:49:29 PM : [iNST-SRX ] 02 50 1E.79.49 19.74.BC 2B 2B 02 PEEK (02) Fri 10/26/2012 02:49:29 PM : [std-Direct Ack] 1E.79.49-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 10/26/2012 02:49:29 PM : [iNST-TX-I1 ] 02 62 1E 79 49 0F 29 03 Fri 10/26/2012 02:49:29 PM : [iNST-ACK ] 02 62 1E.79.49 0F 29 03 06 POKE (03) Fri 10/26/2012 02:49:29 PM : [iNST-SRX ] 02 50 1E.79.49 19.74.BC 2B 29 03 POKE (03) Fri 10/26/2012 02:49:29 PM : [std-Direct Ack] 1E.79.49-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 10/26/2012 02:49:29 PM : [iNST-TX-I1 ] 02 62 1E 79 49 0F 28 0F Fri 10/26/2012 02:49:30 PM : [iNST-ACK ] 02 62 1E.79.49 0F 28 0F 06 SET-MSB(0F) Fri 10/26/2012 02:49:30 PM : [iNST-SRX ] 02 50 1E.79.49 19.74.BC 2B 28 0F SET-MSB(0F) Fri 10/26/2012 02:49:30 PM : [std-Direct Ack] 1E.79.49-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 10/26/2012 02:49:30 PM : [iNST-TX-I1 ] 02 62 1E 79 49 0F 2B FF Fri 10/26/2012 02:49:30 PM : [iNST-ACK ] 02 62 1E.79.49 0F 2B FF 06 PEEK (FF) Fri 10/26/2012 02:49:30 PM : [iNST-SRX ] 02 50 1E.79.49 19.74.BC 2B 2B 01 PEEK (01) Fri 10/26/2012 02:49:30 PM : [std-Direct Ack] 1E.79.49-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 10/26/2012 02:49:30 PM : [iNST-TX-I1 ] 02 62 1E 79 49 0F 28 1F Fri 10/26/2012 02:49:31 PM : [iNST-ACK ] 02 62 1E.79.49 0F 28 1F 06 SET-MSB(1F) Fri 10/26/2012 02:49:31 PM : [iNST-SRX ] 02 50 1E.79.49 19.74.BC 2B 28 1F SET-MSB(1F) Fri 10/26/2012 02:49:31 PM : [std-Direct Ack] 1E.79.49-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 10/26/2012 02:49:31 PM : [iNST-TX-I1 ] 02 62 1E 79 49 0F 2B FF Fri 10/26/2012 02:49:31 PM : [iNST-ACK ] 02 62 1E.79.49 0F 2B FF 06 PEEK (FF) Fri 10/26/2012 02:49:32 PM : [iNST-SRX ] 02 50 1E.79.49 19.74.BC 2B 2B 03 PEEK (03) Fri 10/26/2012 02:49:32 PM : [std-Direct Ack] 1E.79.49-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 10/26/2012 02:49:32 PM : [1E 79 49 0 ] Failed to add device Link to comment Share on other sites More sharing options...
LeeG Posted October 26, 2012 Share Posted October 26, 2012 CJVann Not being able to add an EZIOxx device is a known problem which is resolved in 3.3.4. The original symptom of generating a series of On/Off commands is normally the result of not locking Inputs 3 & 4 to GND or to +5V through pullup resisters. These inputs can optionally be run in Analog mode which prevents them from having an internal pullup resister. When left floating Inputs 3 & 4 can generate a series of On/Off Insteon messages. Link to comment Share on other sites More sharing options...
CJVann Posted October 26, 2012 Author Share Posted October 26, 2012 Excellent news - Any idea when 3.3.4 will be released? Thank you both for your help! Link to comment Share on other sites More sharing options...
LeeG Posted October 26, 2012 Share Posted October 26, 2012 I have not seen an estimate or target for 3.3.4. We thought 3.3.3 fixed the problem (which it did fix the one that was known). Only after that fix was in place was the second problem visible. I have tested a 3.3.4 Alpha adding several different variants of EZIOxx devices successfully. It is a good idea to connect Inputs 3&4 to GND before plugging in the EZIO2X4. Of course if those Inputs will be used immediately connecting them to +5V with pullup resisters is the better approach. Link to comment Share on other sites More sharing options...
CJVann Posted October 26, 2012 Author Share Posted October 26, 2012 Thank you very much - very helpful! Link to comment Share on other sites More sharing options...
CJVann Posted October 31, 2012 Author Share Posted October 31, 2012 BTW - any idea why one of these units will link okay to the ISY, but the two new ones will not? Link to comment Share on other sites More sharing options...
LeeG Posted October 31, 2012 Share Posted October 31, 2012 Different PLM chips. The one that works has an I2CS PLM, the other two have an I2 PLM. Does not make any difference in the function of the EZIO2X4. The same situation with a SwitchLinc or KeypadLinc for example. The path in the ISY is different depending on whether the SwitchLinc or KeypadLinc has an I2CS PLM or not. The I2CS PLM dropped the Standard Peek/Poke commands which forces the ISY to have a different logic path for link database management depending on whether an I2CS device or not. Link to comment Share on other sites More sharing options...
CJVann Posted November 11, 2012 Author Share Posted November 11, 2012 Ah, thank you for the explanation! I got the 3.3.4 update, and the two newer units now link perfectly. I appreciate your guidance through this... VERY much! Link to comment Share on other sites More sharing options...
LeeG Posted November 11, 2012 Share Posted November 11, 2012 You're welcome. Thanks for taking the time to post back the results. Link to comment Share on other sites More sharing options...
prak7121 Posted December 18, 2012 Share Posted December 18, 2012 I am running 3.3.6 and had the exact same error....tried at least 6 different times with the EZIO2x4 and still got the error. On the 7th time I did the install and it added it but the Write to Device green did not disappear. Rebooted the ISY and the device was added successfully, the GUI showed the correct tan coloured arrows instead of the Write to device green arrows. Could it be that 3.3.6 also still has issues adding EZIO2x4 though? Here is the level 3 diagnostics log: Failed to add device Tue 12/18/2012 08:15:30 AM : [1E 7D 30 ] Added to list of devices to link to ISY Tue 12/18/2012 08:15:30 AM : [iNST-TX-I1 ] 02 62 1E 7D 30 0F 0D 00 Tue 12/18/2012 08:15:30 AM : [iNST-ACK ] 02 62 1E.7D.30 0F 0D 00 06 (00) Tue 12/18/2012 08:15:32 AM : [iNST-SRX ] 02 50 1E.7D.30 1E.46.BF 27 0D 02 (02) Tue 12/18/2012 08:15:32 AM : [std-Direct Ack] 1E.7D.30-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Tue 12/18/2012 08:15:32 AM : [iNST-TX-I1 ] 02 62 1E 7D 30 0F 10 00 Tue 12/18/2012 08:15:32 AM : [iNST-ACK ] 02 62 1E.7D.30 0F 10 00 06 ID-REQ (00) Tue 12/18/2012 08:15:33 AM : [iNST-SRX ] 02 50 1E.7D.30 1E.46.BF 2B 10 00 ID-REQ (00) Tue 12/18/2012 08:15:33 AM : [std-Direct Ack] 1E.7D.30-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 12/18/2012 08:15:33 AM : [iNST-SRX ] 02 50 1E.7D.30 07.03.FF 87 01 00 (00) Tue 12/18/2012 08:15:33 AM : [std-Broadcast] 1E.7D.30-->07.03.FF, Max Hops=3, Hops Left=1 Tue 12/18/2012 08:15:33 AM : [1E 7D 30 0 ] Calibrating engine version Tue 12/18/2012 08:15:33 AM : [iNST-TX-I2CS] 02 62 1E 7D 30 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Tue 12/18/2012 08:15:33 AM : [iNST-ACK ] 02 62 1E.7D.30 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Tue 12/18/2012 08:15:42 AM : [iNST-TX-I2CS] 02 62 1E 7D 30 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Tue 12/18/2012 08:15:42 AM : [iNST-ACK ] 02 62 1E.7D.30 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Tue 12/18/2012 08:15:43 AM : [iNST-SRX ] 02 50 1E.7D.30 1E.46.BF 27 2F 00 (00) Tue 12/18/2012 08:15:43 AM : [std-Direct Ack] 1E.7D.30-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Tue 12/18/2012 08:15:52 AM : [iNST-TX-I2CS] 02 62 1E 7D 30 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Tue 12/18/2012 08:15:52 AM : [iNST-ACK ] 02 62 1E.7D.30 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Tue 12/18/2012 08:15:56 AM : [1E 7D 30 0 ] Failed to add device Tue 12/18/2012 08:16:24 AM : [1E 7D 30 ] Added to list of devices to link to ISY Tue 12/18/2012 08:16:24 AM : [iNST-TX-I1 ] 02 62 1E 7D 30 0F 0D 00 Tue 12/18/2012 08:16:24 AM : [iNST-ACK ] 02 62 1E.7D.30 0F 0D 00 06 (00) Tue 12/18/2012 08:16:26 AM : [iNST-SRX ] 02 50 1E.7D.30 1E.46.BF 27 0D 02 (02) Tue 12/18/2012 08:16:26 AM : [std-Direct Ack] 1E.7D.30-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Tue 12/18/2012 08:16:26 AM : [iNST-TX-I1 ] 02 62 1E 7D 30 0F 10 00 Tue 12/18/2012 08:16:26 AM : [iNST-ACK ] 02 62 1E.7D.30 0F 10 00 06 ID-REQ (00) Tue 12/18/2012 08:16:26 AM : [iNST-SRX ] 02 50 1E.7D.30 1E.46.BF 23 10 00 ID-REQ (00) Tue 12/18/2012 08:16:26 AM : [std-Direct Ack] 1E.7D.30-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Tue 12/18/2012 08:16:27 AM : [iNST-SRX ] 02 50 1E.7D.30 07.03.FF 8B 02 FF (FF) Tue 12/18/2012 08:16:27 AM : [std-Broadcast] 1E.7D.30-->07.03.FF, Max Hops=3, Hops Left=2 Tue 12/18/2012 08:16:27 AM : [1E 7D 30 0 ] Calibrating engine version Tue 12/18/2012 08:16:27 AM : [iNST-TX-I2CS] 02 62 1E 7D 30 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Tue 12/18/2012 08:16:27 AM : [iNST-ACK ] 02 62 1E.7D.30 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Tue 12/18/2012 08:16:36 AM : [iNST-TX-I2CS] 02 62 1E 7D 30 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Tue 12/18/2012 08:16:36 AM : [iNST-ACK ] 02 62 1E.7D.30 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Tue 12/18/2012 08:16:45 AM : [iNST-TX-I2CS] 02 62 1E 7D 30 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Tue 12/18/2012 08:16:45 AM : [iNST-ACK ] 02 62 1E.7D.30 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Tue 12/18/2012 08:16:46 AM : [iNST-SRX ] 02 50 1E.7D.30 1E.46.BF 23 2F 00 (00) Tue 12/18/2012 08:16:46 AM : [std-Direct Ack] 1E.7D.30-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Tue 12/18/2012 08:16:50 AM : [1E 7D 30 0 ] Failed to add device Link to comment Share on other sites More sharing options...
prak7121 Posted December 18, 2012 Share Posted December 18, 2012 Just as a note, the revision number of the EZIO2x4 is now v.FF whereas it was just v.00 before. Is this a correct version? I know the question was posted by us about whether this is relevant to proper operation and we found out via a reply from the forum that the version number does not affect performance but it interests me to know if the new 3.3.6 firmware is doing a better job of adding devices by capturing the product version code. Link to comment Share on other sites More sharing options...
Michel Kohanim Posted December 18, 2012 Share Posted December 18, 2012 Hi Paul, It all depends on the EZxxx device and what firmware they use. If EZIO was successfully added to your ISY, then 3.3.6 is not going to be any better. With kind regards, Michel Link to comment Share on other sites More sharing options...
LeeG Posted December 19, 2012 Share Posted December 19, 2012 prak7121 The communication between the EZIO2X4 location and the ISY PLM is not reliable. The Hops Left=x count is not consistent and the required 02 51 response to the command to determine the link database size fails to get a response after 3 attempts. Tue 12/18/2012 08:15:32 AM : [std-Direct Ack] 1E.7D.30-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Tue 12/18/2012 08:15:33 AM : [std-Direct Ack] 1E.7D.30-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 12/18/2012 08:15:33 AM : [std-Broadcast] 1E.7D.30-->07.03.FF, Max Hops=3, Hops Left=1 Tue 12/18/2012 08:15:33 AM : [1E 7D 30 0 ] Calibrating engine version Tue 12/18/2012 08:15:33 AM : [iNST-TX-I2CS] 02 62 1E 7D 30 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Tue 12/18/2012 08:15:33 AM : [iNST-ACK ] 02 62 1E.7D.30 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Tue 12/18/2012 08:15:42 AM : [iNST-TX-I2CS] 02 62 1E 7D 30 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Tue 12/18/2012 08:15:42 AM : [iNST-ACK ] 02 62 1E.7D.30 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Tue 12/18/2012 08:15:43 AM : [iNST-SRX ] 02 50 1E.7D.30 1E.46.BF 27 2F 00 (00) Tue 12/18/2012 08:15:43 AM : [std-Direct Ack] 1E.7D.30-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Tue 12/18/2012 08:15:52 AM : [iNST-TX-I2CS] 02 62 1E 7D 30 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Tue 12/18/2012 08:15:52 AM : [iNST-ACK ] 02 62 1E.7D.30 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Tue 12/18/2012 08:15:56 AM : [1E 7D 30 0 ] Failed to add device These are the trace entries from may add of an I2CS EZIO2X4 using 3.3.6. Note the 02 51 response is missing from your trace Tue 12/18/2012 07:43:42 PM : [17 6F 77 0 ] Calibrating engine version Tue 12/18/2012 07:43:42 PM : [iNST-TX-I2CS] 02 62 17 6F 77 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Tue 12/18/2012 07:43:42 PM : [iNST-ACK ] 02 62 17.6F.77 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Tue 12/18/2012 07:43:42 PM : [iNST-SRX ] 02 50 17.6F.77 19.70.06 2B 2F 00 (00) Tue 12/18/2012 07:43:42 PM : [std-Direct Ack] 17.6F.77-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 12/18/2012 07:43:42 PM : [iNST-ERX ] 02 51 17 6F 77 19 70 06 11 2F 00 00 01 1F FF 00 62 09 19 70 06 FF 1F 09 91 Tue 12/18/2012 07:43:42 PM : [Ext-Direct ] 17.6F.77-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Tue 12/18/2012 07:43:42 PM : [17 6F 77 0 ] Using Database Link Table offset 0x1FF8 (reported 0x1FF8) Tue 12/18/2012 07:43:43 PM : [17 6F 77 1 ] Start : Adding device to ISY Tue 12/18/2012 07:43:43 PM : [17 6F 77 1 ] Finish : Adding device to ISY was Successful Link to comment Share on other sites More sharing options...
prak7121 Posted December 19, 2012 Share Posted December 19, 2012 Hello Lee, are you saying that although I was successful in adding the EZIO2x4 that in fact it was not 100% successful? Or that the communication is still not 100%? We are considering running the network cable out to the EZIO2x4 so the PLM can be on the same electrical line. Right now they do not share the same electrical line as there is a different transformer on the line that feeds the EZIO. We are solely relying on communicating via the RF, not through electrical lines. Link to comment Share on other sites More sharing options...
LeeG Posted December 19, 2012 Share Posted December 19, 2012 I took from the posted trace that the EZIO2X4 did not add successfully. Tue 12/18/2012 08:16:50 AM : [1E 7D 30 0 ] Failed to add device EDIT: sorry, I went back over the post sequence and see where on the 7th attempt it did add. There is poor comm when trace was taken. If dependent on RF only moving the Access Point in the garage to a more line of site position may help. Also running power that is not on a separate transformer should help. Link to comment Share on other sites More sharing options...
ELA Posted December 19, 2012 Share Posted December 19, 2012 prak7121, Is this this install or another? http://forum.universal-devices.com/viewtopic.php?p=76861#p76861 Link to comment Share on other sites More sharing options...
prak7121 Posted December 19, 2012 Share Posted December 19, 2012 This is the same install. We raised all the Access Points to a 10 foot height above so they are all line of sight with the PLM. Here is a to scale graphic of what we have done. I am very, very much interested in having you look at this graphic layout to see if you see any issues in terms of locations for the access points. As I wrote earlier, the access points in the building do not share the same electrical lines. We did bridge phase the 2 access points closest to the PLM to bridge all 3 phases. But we could not do it for all the items on the other end by the EZIO2x4 as they are not on the same 3 phases. Link to comment Share on other sites More sharing options...
Brian H Posted December 19, 2012 Share Posted December 19, 2012 Looks like an Industrial site. Are you using three phase power? Link to comment Share on other sites More sharing options...
ELA Posted December 19, 2012 Share Posted December 19, 2012 Yes Brian this is 3 phase, If you look at the link to Prak7121's previous post there are more details there about this install. Thanks for the diagram as that is helpful. Is it correct then that you are attempting to go all RF->RF and only use powerline comm between the IOlincs/EZIO and the nearest Access point? If so Ideally you would want all RF from the PLM to the I/O device to complete requiring routing through only one access pt along the way. If one access pt. has to repeat to another access pt. in between you start to use/loose too many hops. This may be difficult in an Industrial environment due to reflections and multi-path signals. How long is the cable from the ISY to the PLM as that is a serial connection and that length has limits (~ max 50ft), but I would keep it as short as possible. I put the ISY with the PLM and ran a long Ethernet cable to the router. Then maybe you can move the PLM closer to a central location near all the IOlinc/EZIO's. You can also use the 4 tap test between the PLM and each intended (IOLINC/EZIO & nearest access pt. pairing) to check/confirm RF comms. Not caring so much about light color or phase as you are that the light blinking showing an RF reception. You could repeat this testing with the PLM in various locations to test for the best possible RF linking to all IO devices. Link to comment Share on other sites More sharing options...
prak7121 Posted December 19, 2012 Share Posted December 19, 2012 Hello ELS, you stated: "Is it correct then that you are attempting to go all RF->RF and only use powerline comm between the IOlincs/EZIO and the nearest Access point?" The answer is we are using the same power line for the EZIO and one access point (on map access point 5) but not the IOLincs...those are on another power line powered through a different transformer. With respect to the limit on cable length.....if we use an Ethernet cable from the Router (in same room as the ISY currently) out to the EZIO so we can move the PLM and ISY there, is there a limit on the Ethernet cable that we need to consider for the sake of the ISY/PLM? Between the ISY and PLM currently we are using a 50ft long Ethernet cable as we are not using the serial port. Link to comment Share on other sites More sharing options...
prak7121 Posted December 19, 2012 Share Posted December 19, 2012 By the way we really appreciate all the help from all of you! It is very helpful. Paul and Wilf at VeriGreen in Cambridge, Ontario Link to comment Share on other sites More sharing options...
LeeG Posted December 19, 2012 Share Posted December 19, 2012 The ISY to PLM is a Serial connection, not an Ethernet connection. Absolute limit would be 50' with much shorter, like 3-4 feet, preferred. Link to comment Share on other sites More sharing options...
ELA Posted December 19, 2012 Share Posted December 19, 2012 prak7121, Keep the cable between the PLM and the ISY short ( this is a RS232 connection). Move the PLM & ISY pair closer to intended receivers using a long Ethernet connection from ISY to router. From what I read there is a 100meter limit on that cable length (depending upon speed). Being an Industrial environment it sounds like you have confirmed that there are internal step-down transformers. Insteon powerline signals will not travel between transformers well if at all. I am not sure I understand your setup completely. Sounds like you need to assure that you pair an access pt. with each Iolinc ( like you did for the EZIO). Preferably on the same circuit, but at least on the same transformer with all used phases coupled ( on each transformer used). This is a complicated install. Your diagram helped a beginning understanding. If you could add more detail as to the transformers involved, and which device is on what transformer, and what phase, would go a long way. That should help you envision the path the signal would need to take to go from the PLM to the intended receiver. Then assure that that path does not require more than the max available, three hops. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.