Jump to content

Com Failure then KPL failures


Recommended Posts

KPL Buttons flicker then execute ON/OFF

 

  • Apparent bad KPL-6, dual band, dimmer.  Absolutely dead, no button LEDs, no communication with ISY, no recognition of button press in the Admin Console
  • Removed failed device
  • Put new KPL in a table top holder and plugged into an outlet
  • Did a factory RESET
  • Changed from 8 button to 6 button configuration
  • Did a REPLACE
  • Successful completion, ie no errors. But did not test buttons in the table top configuration.  (The Load of the KPL in the table top unit was not wired to the ceiling lamp anyway, so I skipped this test.  In hindsight, maybe I should have tested it.) 
  • Did a Device Links Read and Compare:  PASSED
  • Installed new KPL in wall, where failed KPL was.
  • Screwy results testing buttons.  Buttons did not reflect status of the scenes.  In particular, sometimes the MAIN button was ON, but the ceiling lamp was NOT ON. 
  • Did a factory reset, changed to 6 button configuration, then RESTORE.  No errors. 
  • Again, some screwy results.  Then with about the 3rd press of the MAIN button ON, all the buttons flashed on, the KPL BEEPED, then the ceiling light flickered in apparent sync with flickering of the buttons LEDs.  Then the ceiling light came ON solid. 
  • Press the MAIN OFF button, flickering, flashing, as before, then after about 2 seconds the ceiling light went OFF. 
  • Now everytime I press one of the MAIN buttons (ON or OFF that is), I get the same results. 
  • Did a Read Device Links, “Failed Reading Device Link”
  • Attempted a RESTORE, it failed “Cannot Communicate with Device”. 
  • Query seems OK, but that is about it. 

 

I have attached two separate event viewer logs, one from the Device Link Read failure and the second when I press the MAIN ON button. 

 

As a matter of note: This appears to be the third dual band KPL dimmer to fail in the last month.  Failure 1 was about 4 weeks ago.  I was using it to replace a bad non-dual band KPL and discovered it was bad.  The second failure, which kicked off this exercise, is totally dead.  The third failure, the replacement for failed KPL #2, appears to have the same symptoms as the first failure, ie some coms, unreliable, flashing / flickering LEDs, etc etc. 

 

Is the KPL really bad? 

Am I doing something wrong?

Is anyone else experiencing a lot of failures of these devices?  2334-2xx

 

EDIT:  Attached Event Log

ISY-Events-Log.v4.2.66__Tue 2015.01.06 02.24.pdf

Event View Tue 2015.01.06.Link Read Fail.pdf

Link to comment
Share on other sites

I had a similar issue once with a KPL and a factory reset fixed it. Are you sure you're getting a factory reset, pulling out the set button, then pushing in the set button until the long beep stops then releasing the set tab. This is best done with the KPL installed.

Link to comment
Share on other sites

Lee,

 

Sorry about that, files now attached.

 

Techman,

 

Failure #1 was an 8 button that was used to replace an 8 button. 

 

Failure #2 was a 8 button, reconfigured to a 6 button and used to replace a 6 button.

 

Failure #3 (possible failure, jury is still out)  was also an 8 button used to replace a 6 button. 

 

All were dual band dimmer KPL's.

 

Justin

Link to comment
Share on other sites

Info only if you use a TableTop enclosure: The neutral wire (wide blade) of lamp cord has a rib running its entire length. The line side (narrow blade) is smooth. It doesn't matter for correct operation of the device if there is no load.

Link to comment
Share on other sites

The interaction with the KPL is losing Standard Definition (SD)  messages.  The display of link records would expect to see an SD message ( 02 50 ......) followed by an Extended message (02 51 .....) containing the actual link record.  The missing SD records when the Extended message is received is strange.   It could be a KPL failure but I would look at the type of load the KPL is controlling or something on that powerline generating interference.  I tried posting trace sample but have not found a way of extracting lines of a .pdf file.   Would have been better to post the original event .txt file.

 

I suggest putting the KPL back in the desktop box and plugging it into same circuit PLM is on.   See if the display of the link records works that way.   If the SD messages are there then look for load issues or some form of interference on the normal install circuit.  

Link to comment
Share on other sites

Lee,

 

I understand you recommendation and will proceed.  However, could interference of this nature, ie missing SD records, cause the consistent flickering of all the KPL button LEDs?  And the flickering of the ceiling light that is the load? 

 

I am also a bit perplexed because this load / ceiling lamp and the other items on this branch have not changed since I installed the KPL in Jan of 2014.  However, that said I will double check for new items that my daughters may have plugged into this branch.....

 

Justin

Link to comment
Share on other sites

Lee, 

 

4.2.66 was a special download I was given by Univ Dev in July 2014.  I had been on vacation and had a power fail.  When the system came back on the ISY-994 was "hung" and stayed that way for the next 2 weeks, until I returned and did a reboot.  I have both Sonos and DirecTV and if I remember correctly, I was told that they could cause that hang because of their high ENET traffic.  I have been reluctant to go onto the next set of firmware (4.2.18 I believe) until I get some of my latest ssues resolved. 

 

PS:  For some reason the .txt extension got deleted on my files earlier and the system wouldn't let me upload it.  I have put the .txt back on and it is uploaded now. 

 

Justin

ISY-Events-Log.v4.2.66__Tue 2015.01.06 02.28.59 PM Device Link Read Fail 2.txt

ISY-Events-Log.v4.2.66__Tue 2015.01.06 02.24.41 PM Main ON 1.txt

Link to comment
Share on other sites

The 02 50 ..... message is missing in this sequence.  See the next sequence for correct message flow. 

 

 

Tue 01/06/2015 02:26:37 PM : [iNST-TX-I2CS] 02 62 2A 05 D7 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 C2
 
Tue 01/06/2015 02:26:37 PM : [iNST-ACK    ] 02 62 2A.05.D7 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 C2 06        (00)
 
Tue 01/06/2015 02:26:41 PM : [iNST-ERX    ] 02 51 2A 05 D7 28 CD 8E 17 2F 00 00 01 0F FF 20 A2 54 28 CD 8E FF 1F 05 06 
 
Tue 01/06/2015 02:26:41 PM : [Ext-Direct  ] 2A.05.D7-->ISY/PLM Group=0, Max Hops=3, Hops Left=1
 
This is how the message sequence should look like.  02 50 .... followed by 02 51 ......
 
Tue 01/06/2015 02:26:41 PM : [iNST-TX-I2CS] 02 62 2A 05 D7 1F 2F 00 00 00 0F F7 01 00 00 00 00 00 00 00 00 CA
 
Tue 01/06/2015 02:26:41 PM : [iNST-ACK    ] 02 62 2A.05.D7 1F 2F 00 00 00 0F F7 01 00 00 00 00 00 00 00 00 CA 06        (00)
 
Tue 01/06/2015 02:26:45 PM : [iNST-SRX    ] 02 50 2A.05.D7 28.CD.8E 27 2F 00           (00)
 
Tue 01/06/2015 02:26:45 PM : [std-Direct Ack] 2A.05.D7-->ISY/PLM Group=0, Max Hops=3, Hops Left=1
 
Tue 01/06/2015 02:26:46 PM : [iNST-ERX    ] 02 51 2A 05 D7 28 CD 8E 12 2F 00 00 01 0F F7 20 A2 54 28 CD 8E FF 1F 03 10 
 
Tue 01/06/2015 02:26:46 PM : [Ext-Direct  ] 2A.05.D7-->ISY/PLM Group=0, Max Hops=2, Hops Left=0
Link to comment
Share on other sites

Archived

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


×
×
  • Create New...