Did I killed my KeyPad with too many Writes?..

[Vipola]

I have some communication issue with my KeyPad and cannot reprogram it.. I tried to factory reset it, I'v tried to move it.. it just won't write to it anymore.. Is there a number or write you can do on a Keypad?.. I wonder if I killed it with too many write update from a little program I used to run..

 

http://forum.universal-devices.com/topic/14122-keypad/

 

 

My Girlfriend use to complain about the 'backlight' of the KeyPad been too bright during the night, so I wrote a program to close the backlight when the light is closed.. 

 

 

If

        Status  '2nd / BedRoom / LightWhite' is Off

 

Then

        Set '2nd / BedRoom / KeyPad / BedRoom A' On 15 / Off 0 (Backlight Level)

 

Else

        Set '2nd / BedRoom / KeyPad / BedRoom A' On 15 / Off 7 (Backlight Level)

 

 

Any Idea if this program is what killed my Keypad?..

[LeeG]

Backlight level changes all the button bright levels, not just button A.  To change a button LED assign the KPL button as a Responder in a Scene and turn the Scene On/Off.

 

There is a limit to which device memory can be updated but it is so large (a million) as to not be a concern. 

[Vipola]

Yes that's exactly what the code do.. sorry for the confusion, my keypad (and it's load) is named from it's A button..

The program does change the backlight level for all the button of the keypad so it is completely off at night..

 

So that program would reprogram the backlight level several times a day (over 10 times) for over 1 year.. now the keypad just throw error whenever I try to write to it.. 

[shannong]

I noticed in the logs it was writing a memory address rather than device control commands to accomplish this. I had this thought and concern as well since I switch LEDs backlights on/off on the KPLs in the master bedroom every night/morning. I couldn't find any info on what type of persistent storage is used and figured it was unlikely to be a short term problem and I figured my use of these devices will probably be 10 years or less due to technology changes and obsolescence.

[Brian H]

I can't say what EEPROM maybe used in the KPL. I do know the 2457D2 uses a Microchip 24LC32A and the 2413 PLM a 24FC64.

Both have a 1,000,000 guaranteed Erase Rewrite cycle.

[Vipola]

Note also that it's a older keypad: 2486D KeypadLinc Dimmer 6 Buttons v.35,

maybe less guaranteed rewrite cycles..

[LeeG]

10(per day)*365=3650 per year.    3650*10 (years)=36500

 

That activity is so small even if the cycles were 100,000 it is not important.  

 

More likely the age of the electronics than the memory updates.

[dstanley]

Note also that it's a older keypad: 2486D KeypadLinc Dimmer 6 Buttons v.35,

maybe less guaranteed rewrite cycles..

I have had three of these units fail on me in the last four weeks. They begin to act erratically and start to flash either the load or one of the linked scenes. Resetting the device does nothing. When power is reapplied they make a buzzing sound and you can hear the electronics clicking about once per second. One of them would even turn off the backlight by itself.

I believe that it is more a case of inferior capacitors than eprom writing though. All of these were purchased in April of 2011 and are the same as the original posters devices. I too would dim or extinguish the back lights overnight through a program. Dim or off at night and then back on in the morning.

 

So I have three of these if someone wants to take them apart to play with them (Brian!?)

 

Dwight

[Teken]

From personal experience these 2011 KPL devices exhibits a much different boot up / power on when compared to later releases.

 

They also function and act differently when a improper load is installed. Some also pulse, flicker, and buzz when very brief power outages are experienced.

 

Over the years quite a few features have been removed from the KPL.

 

I am eager to see what new features will be incorporated next year.

 

 

Encrypted By: Phoenix Security Solutions