Jump to content

KPL 2486 Comm. Issues (another one for the list)


Recommended Posts

One of my KPL's has been acting flaky lately, not responding to programs, not activating them.  Last night I decided to remove and restore it but now I'm unable to write anything to it.  It linked up just fine, initially, and will even show the proper status if I send a query.  But sending updates produces this:

Sun 11/23/2014 11:20:10 AM : [16 E6 9A 1  ] Link    1 : 0FF0 [A2311F249AFF1F08] Writing [A2311F249AFF1F08]
Sun 11/23/2014 11:20:10 AM : [iNST-TX-I1  ] 02 62 16 E6 9A 0F 28 0F
Sun 11/23/2014 11:20:10 AM : [iNST-ACK    ] 02 62 16.E6.9A 0F 28 0F 06          SET-MSB(0F)
Sun 11/23/2014 11:20:11 AM : [iNST-SRX    ] 02 50 16.E6.9A 1F.24.9A 23 28 0F    SET-MSB(0F)
Sun 11/23/2014 11:20:11 AM : [std-Direct Ack] 16.E6.9A-->ISY/PLM Group=0, Max Hops=3, Hops Left=0
Sun 11/23/2014 11:20:11 AM : [iNST-TX-I1  ] 02 62 16 E6 9A 0F 2B F0
Sun 11/23/2014 11:20:11 AM : [iNST-ACK    ] 02 62 16.E6.9A 0F 2B F0 06          PEEK   (F0)
Sun 11/23/2014 11:20:14 AM : CLI-HAMW: Connecting to api.aerisapi.com
Sun 11/23/2014 11:20:14 AM : CLI-HAMW: Successfully Processed HAMW Response
Sun 11/23/2014 11:20:14 AM : CLI-HAMW: Connecting to api.aerisapi.com
Sun 11/23/2014 11:20:15 AM : CLI-HAMW: Successfully Processed HAMW Response
Sun 11/23/2014 11:20:15 AM : CLI-HAMW: Connecting to api.aerisapi.com
Sun 11/23/2014 11:20:15 AM : CLI-HAMW: Successfully Processed HAMW Response
Sun 11/23/2014 11:20:20 AM : [iNST-TX-I1  ] 02 62 16 E6 9A 0F 28 0F
Sun 11/23/2014 11:20:20 AM : [iNST-ACK    ] 02 62 16.E6.9A 0F 28 0F 06          SET-MSB(0F)
Sun 11/23/2014 11:20:20 AM : [iNST-SRX    ] 02 50 16.E6.9A 1F.24.9A 2B 28 0F    SET-MSB(0F)
Sun 11/23/2014 11:20:20 AM : [std-Direct Ack] 16.E6.9A-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Sun 11/23/2014 11:20:20 AM : [iNST-TX-I1  ] 02 62 16 E6 9A 0F 2B F0
Sun 11/23/2014 11:20:21 AM : [iNST-ACK    ] 02 62 16.E6.9A 0F 2B F0 06          PEEK   (F0)
Sun 11/23/2014 11:20:21 AM : [iNST-SRX    ] 02 50 16.E6.9A 1F.24.9A 2B 2B A2    PEEK   (A2)
Sun 11/23/2014 11:20:21 AM : [std-Direct Ack] 16.E6.9A-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Sun 11/23/2014 11:20:21 AM : [iNST-TX-I1  ] 02 62 16 E6 9A 0F 28 0F
Sun 11/23/2014 11:20:21 AM : [iNST-ACK    ] 02 62 16.E6.9A 0F 28 0F 06          SET-MSB(0F)
Sun 11/23/2014 11:20:30 AM : [iNST-TX-I1  ] 02 62 16 E6 9A 0F 28 0F
Sun 11/23/2014 11:20:30 AM : [iNST-ACK    ] 02 62 16.E6.9A 0F 28 0F 06          SET-MSB(0F)
Sun 11/23/2014 11:20:31 AM : [iNST-SRX    ] 02 50 16.E6.9A 1F.24.9A 23 28 0F    SET-MSB(0F)
Sun 11/23/2014 11:20:31 AM : [std-Direct Ack] 16.E6.9A-->ISY/PLM Group=0, Max Hops=3, Hops Left=0
Sun 11/23/2014 11:20:31 AM : [iNST-TX-I1  ] 02 62 16 E6 9A 0F 2B F1
Sun 11/23/2014 11:20:31 AM : [iNST-ACK    ] 02 62 16.E6.9A 0F 2B F1 06          PEEK   (F1)
Sun 11/23/2014 11:20:40 AM : [iNST-TX-I1  ] 02 62 16 E6 9A 0F 28 0F
Sun 11/23/2014 11:20:40 AM : [iNST-ACK    ] 02 62 16.E6.9A 0F 28 0F 06          SET-MSB(0F)
Sun 11/23/2014 11:20:40 AM : [iNST-SRX    ] 02 50 16.E6.9A 1F.24.9A 2B 28 0F    SET-MSB(0F)
Sun 11/23/2014 11:20:40 AM : [std-Direct Ack] 16.E6.9A-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Sun 11/23/2014 11:20:40 AM : [iNST-TX-I1  ] 02 62 16 E6 9A 0F 2B F1
Sun 11/23/2014 11:20:40 AM : [iNST-ACK    ] 02 62 16.E6.9A 0F 2B F1 06          PEEK   (F1)
Sun 11/23/2014 11:20:44 AM : [16 E6 9A 1  ] Link    1 : 0FF0 [A2311F249AFF1F08] *Failed Writing [A2311F249AFF1F08]
Sun 11/23/2014 11:20:44 AM : [D2D EVENT   ] Event [16 E6 9A 1] [ERR] [1] uom=0 prec=-1
Sun 11/23/2014 11:20:44 AM : [  16 E6 9A 1]      ERR   1
 

 

It has run pretty well for a couple years but now I'm not sure what to do.  I've tried everything aside from pulling it from the wall.

Link to comment
Share on other sites

Look at the number of Max Hops=3, Hops Left=0. That is as poor as comm can be and still work.  At the end of the posted trace the KPL did not respond to a command at all which stops the update.

 

Since some of the commands have Hops Left=2 (as good as it gets) something is causing interference some of the time or the phases are not coupled, dependent on a 240v appliance to provide coupling. 

 

EDIT: Could also be a bad KPL

Link to comment
Share on other sites

Thanks, I'm guessing it's a bad unit, as it's worked with minimal issue for over two years (just over it's warranty, go figure).  I pulled it from the wall to double-check the wiring, kept it hanging out while I removed it from the ISY, but I get the same results.  I have a hard-wired filterlinc (?) on my main panel, filterlincs on all electronics outlets, as well as 5 access points to mitigate comm issues, so it looks like it's toast and I'll have to shell out even more and replace it (not too happy about that since our home is for sale).  Thanks again, LeeG, you always come to the rescue.  B)

Link to comment
Share on other sites

A factory reset requires removing power for at least 10 seconds before pushing the air-gap all the way in. Pulling out the air-gap until it clicks removes power B)

Link to comment
Share on other sites

It hadn't, but tried it again tonight and it seems to be operating normally.  This was after I left the air gap pulled over the weekend so there was no doubt that it had no residual charge remaining.  It seems to be communicating again, all updates written without error!  Will monitor over the next few days and see if it goes batty again.  Too bad I ordered a replacement already.... :?

Link to comment
Share on other sites

Update:  there's still a hum coming from the device, much more high-frequency than the usual hum when resetting.  I was able to add it back in to the ISY, however, it's completely unresponsive to commands and, aside from the main power button (A), no other buttons function.  Not surprising, since it will generally not communicate.  Strange thing is, though, the status of button A displays correctly.  No matter I guess since it's going to be in the trash next week.

Link to comment
Share on other sites

  • 2 weeks later...

One last post and then I'll let this thread die.  I replaced the KPL with a new dual-band version and what do you know, every device, even those that were giving me trouble, is working perfectly.  Status updates are correct, programs running flawlessly, wireless sensors acting like they should, no apparent comm issues anywhere.

 

This was a good lesson-learned for me and hopefully it will be for others, as well.  ONE stupid device malfunctioning can wreak havoc on an entire system.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...