EVL3 + Safewatch 3000EN, cannot pass commands to panel

[Psmiraglia]

I have deployed an evl3 to a panel that came with the house I bought. Here is the situation:

- panel firmware chip reads 2005 Rev 4.2. Has a hard wired siren, 6150 keypad and RF transmitter
- evl wiring double-checked as correctly deployed
- programming for evl double checked. With the exception of option *48, locked out by adt, everything is correct
- the local web server accurately shows panel status (ready, armed, etc.) and I'm able to get alarms via email/SMS
-per support's request, I tried disconnecting the rf transmitter and keypad (leaving only the evl connected to the panel) and tried to send commands... Did not work either

Now the problem: no command I try to send from either the portal or the local web server (arm, disarm, test, etc) works. All I see the the backlight of the keypad lighting, like if I touched a key, indicating that "something" was sent, but nothing happens. I don't get any sort of error message on the portal, local web server or the keypad (no sounds either).

I have tried using the master code, a standard user, and a user specifically created for the evl (all these can arm/disarm from the keypad) with no success...

Both eyes-on support and myself ran out of ideas...

Any thoughts ?

[K-Man]

Sounds like you have a keypad conflict.

You have to make sure the address of your Envisalink is unique and not used by any other keypad.

For reasons that I can't remember right now, we made it such that in case of a conflict, the Envisalink would lose the "race" to send its command to the panel. The resultant behaviour is that the conflicting keypad operates normally and keystrokes from the Envisalink disappear into the ether.

[Psmiraglia]

K-man,

to test your theory, I focused on addresses #20 and #21. I enabled #20 (*193 10) and left #21 disabled (*194 00).
I then changed the partition 1 keypad address on the EVL3 to #20, reboot, tried to send a command and nothing...

I then changed the partition 1 keypad address on the EVL3 to #21, reboot, and get:" Error: Possible Keypad Conflict Or Keypad Programming Not Completed. Programming Guide
Error:*29 Programming on panel not completed properly. "

so it seems like the EVL3 is "detecting" a misconfiguration of keypad address. Though it is "possible" it may not detect a conflict, I only have one keypad hardwired to the panel, and it seems to be #16.

btw, enabling shadowing only lights the "trouble" signal up and makes my keypad beep insanely. I should not need this, but figured I should try in case I have a module I'm not aware of (which does not seem like, by looking at the panel)

ideas:
- is it possible fro a keypad to "claim" all addresses (hence creating a conflict" but only display a single address when checked by pressing 1&3 ?
is it possible that the codes I created are only limited to keypad #16 ?

Neither of these came as possible on my research, but you guys know better...
other thoughts ?

[K-Man]

The Envisalink watches for traffic for each of the keypad addresses and the error you see indicates that it hasn't seen any for the address you programmed for the Envisalink (ie 21).

The panel has no idea if there are two keypads using the same address so it will happily answer whichever keypad answers first to any address.

It is possible that a keypad could own "all" the addresses. This would be the case if you have an older keypad that doesn't use addressing.

To rule this out you should remove the keypad and leave everything else connected.

[Psmiraglia]

have just tested this again by disconnecting leads 4,5,6 and 7 to the only keypad I have and I still cannot pass commands from the EVL3.

Im strting to think there may be something wrong with the EVL3 HW I have...

[Psmiraglia]

I'd like to share that engineering helped me solve the problem with a SW fix. Thanks to Trs in support, engineering and the users on this forum for the help.