Eaton KEY-KPZ01 rapid red flashing

[AutomationEng]

I programmed an i-onG2SM, in my office. PIRs door contacts, KEY-KPZ01 and network access. Everything worked OK.

II then connected it to the actual system, replacing an old Ademco Galaxy. The only thing I didn't connect was the  bell box. I also only had the keypad on a short wire, local to the box, while I tested everything else for a few days. This also worked.

I have now connected the bell/ strobe and used the old wires to replace the Galaxy keypad with my KEY-KPZ01.

For some reason the keypad will only constantly display the Eaton logo and an old date, and the navigation button rapidly flashes red.

Pressing any key just causes a beep but does nothing else. 

The system still works through the Secureconnect app. but I can't do anything with the keypad.

 

Any ideas would be much appreciated.

 

Thanks in advance

[al-yeti]

3 hours ago, AutomationEng said:

I programmed an i-onG2SM, in my office. PIRs door contacts, KEY-KPZ01 and network access. Everything worked OK.

II then connected it to the actual system, replacing an old Ademco Galaxy. The only thing I didn't connect was the  bell box. I also only had the keypad on a short wire, local to the box, while I tested everything else for a few days. This also worked.

I have now connected the bell/ strobe and used the old wires to replace the Galaxy keypad with my KEY-KPZ01.

For some reason the keypad will only constantly display the Eaton logo and an old date, and the navigation button rapidly flashes red.

Pressing any key just causes a beep but does nothing else. 

The system still works through the Secureconnect app. but I can't do anything with the keypad.

 

Any ideas would be much appreciated.

 

Thanks in advance

Cable fault, I assume it worked on the bench with short cable or check there's no strand shorting out where you connect wires, if spare cores try them instead to keypad 

[james.wilson]

Agreed sounds like a keypad comms issue. However I'd thought you would get faults reported / logged

[al-yeti]

1 hour ago, james.wilson said:

Agreed sounds like a keypad comms issue. However I'd thought you would get faults reported / logged

Maybe then keypad issue 

[al-yeti]

14 hours ago, AutomationEng said:

I programmed an i-onG2SM, in my office. PIRs door contacts, KEY-KPZ01 and network access. Everything worked OK.

II then connected it to the actual system, replacing an old Ademco Galaxy. The only thing I didn't connect was the  bell box. I also only had the keypad on a short wire, local to the box, while I tested everything else for a few days. This also worked.

I have now connected the bell/ strobe and used the old wires to replace the Galaxy keypad with my KEY-KPZ01.

For some reason the keypad will only constantly display the Eaton logo and an old date, and the navigation button rapidly flashes red.

Pressing any key just causes a beep but does nothing else. 

The system still works through the Secureconnect app. but I can't do anything with the keypad.

 

Any ideas would be much appreciated.

 

Thanks in advance

Althought have you managed to delete the keypad? And need to add it back as a device 

 

Does the app allow a virtual keypad? Go through it and see if it sees keypad or not as a wired device