We have a prox reader wired to an Elk keypad, and have a rule set up:
WHENEVER ACCESS KEYPAD x, TURN ON OUTPUT y FOR 4 SECONDS
Output y is a relay controlling an electric door strike. Earlier today (while I was away from the office unfortunately), it just stopped working. I got in and ran my keyfob across the prox reader several times, nothing happened. I went to the Elk panel and manually shorted the output contacts with a spare bit of wire, and the door triggered. I then went into the output control menu on the keypad, turned the output on and then off (which triggered the door), and now the keyfob works again. Has anyone ever seen anything like this? Any idea what happened? Is it likely to repeat? Looking in the Elk log, it appears it just stopped registering keyfob access events. I'm running the latest Elk M1G and keypad firmware. Using a HID prox reader.
WHENEVER ACCESS KEYPAD x, TURN ON OUTPUT y FOR 4 SECONDS
Output y is a relay controlling an electric door strike. Earlier today (while I was away from the office unfortunately), it just stopped working. I got in and ran my keyfob across the prox reader several times, nothing happened. I went to the Elk panel and manually shorted the output contacts with a spare bit of wire, and the door triggered. I then went into the output control menu on the keypad, turned the output on and then off (which triggered the door), and now the keyfob works again. Has anyone ever seen anything like this? Any idea what happened? Is it likely to repeat? Looking in the Elk log, it appears it just stopped registering keyfob access events. I'm running the latest Elk M1G and keypad firmware. Using a HID prox reader.