Did you know that you can enjoy many members-only features simply by quickly registering (no CAPTCHA!)?
Registering gives you access to our giveaways, forum features, increased search performance, access to our Download Library, create your own blog & gallery, and more!
Once you have registered, stop by in 'Hello World', and introduce yourself.
Trouble with Essex Keypad and Elk M1
Posted 20 August 2012 - 07:34 PM
I've gone through the old tried and true several times... re-enrolling, powering down and back up, etc. I've also tried numerous combinations of user authorization options. I even thought possibly a code lockout from my early testing so I changed G12 to 99 (disabled) temporarily and have deleted the user and created new. No luck.
I have a suspicion there is something relativelly simple I am overlooking but I can't think of it and I've searched Cocoontech and also Google but I've not seen any similar problems (which really makes me think it may be something simple I'm not seeing).
Any advice would be greatly appreciated. Thanks in advance.
Posted 20 August 2012 - 07:45 PM
Assuming the users and panel have been sent/received and the calculator gave you the right values for the code, is this another valid code programmed within the system?
Maybe try a user code instead of the code you are trying?
It's getting the wiegand somehow, so it would come to the Essex in this case IMO.
How about throwing a rule in there, I'm wondering if the system is not seeing the data and tying the event to disarm.
Posted 20 August 2012 - 08:33 PM
The keypad is an Essex KTP-103-SN. The keypad it is wired to is an Elk M1KP via a W035A harness. My assumption is that the calculator did determine the correct code since it recognizes it to arm the system.
Yes, I wait for the exit delay to expire to try to disarm.
I've tried different test user codes, one is an existing code on the system, another is a new code created just for this testing. Both work to arm. Neither work to disarm.
I'd be happy to try putting in a rule. What could I trigger off of? There seems to be no activity that occurs on the Elk side when it is armed and I enter codes on the Essex side. However, the Elk keypad will occasionally beep when the # key is pressed on the Essex keypad which tells me it is receiving data but not acting on it. I thought perhaps there was some setting that I have not addressed on the M1 side which is causing it to accidentally or purposely ignore the attempts to disarm?
Posted 21 August 2012 - 01:39 AM
Also, I'm not sure about the KP as I'm using KP2's for my tests, but every time the reader sends a "read", the keypad beeps - regardless if it's a known code or not, it beeps to let you know there was some sort of read that it received.
I would check your user for the options. Just create a blank user and don't touch the options and it should work by default; but check on the Access, Arm, Disarm, and other permissions for that user. I don't have ElkRP in front of me right now, but the options were along those lines. I'd bet just about anything that's where your problem lies.
Posted 21 August 2012 - 08:05 AM
Posted 21 August 2012 - 08:28 AM
From here, I'm thinking I'll have to take the testing to the next level to try to narrow it down. I believe I have a spare KP keypad so I may try swapping it out and re-testing. A subsequent test could be to instead add the second KP elsewhere on the bus, then wire it up to the Essex instead and see what happens. Just a matter of finding the time -- it's frustrating being at work when I want to be home testing this!
Posted 21 August 2012 - 09:54 AM
DEL could be right, but my experience so far is that Wiegand 26 (what Elk has to use) has absolutely no room for extra codes or characters unlike Wiegand 37 which can have all sorts of extra identifiers. I guess that's worth mentioning too - you are sure the keypad is set for Wiegand 26 right?
Also, there aren't any areas at play are there? There's just one Area for the house and all keypads are assigned to that same area?
Posted 21 August 2012 - 10:49 AM
Yes, I'm only using area 1.
The documentation for the Essex keypad can be found here... http://www.keyless.c...6BitWiegand.pdf
According to this documentation, DEL is correct that the keypad will send an error message of 26 binary 1s if you hit the # without a code, a code of all zeros, or a code >= 65,535. If I press the # on the Essex without entering a code, the M1KP will beep. I'm tempted to buy a wiegand-usb reader to confirm what the Essex keypad is outputting each time but since the M1KP appears to be happy with the code as far as arming goes and I can't imagine how the Essex would know to send anything different from one sequence of 1-2-3-4-# versus another, I want to pursue several other possibilities first.
Posted 21 August 2012 - 04:48 PM
I attached a screenshot of the user screen as a reference.
Posted 21 August 2012 - 04:49 PM
Posted 21 August 2012 - 05:36 PM
Posted 21 August 2012 - 05:48 PM
Posted 21 August 2012 - 08:20 PM
Posted 21 August 2012 - 08:51 PM
Posted 21 August 2012 - 10:26 PM
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users