EyezOn Forum

Environment - Microsoft Visual Studio C#, TPI - TCP/IP connection
Issue:
(1) I successfully connect using my IP and port 4025
(2) I get the "Login:" message
(3) I respond with the current password successfully used with HTTP interface
(4) The response I'm getting is "FAILED"
(5) If I don't send the password, I get the "Time-Out" message
What is the correct format for the password? What am I missing?
Regards,

Did you send <CR><LF> after? It looks for that

I tried everything include "/r/n", null term, case changes as well as sentinels.
I get the "Login:" from the server, respond with the password with CRLF and then get a FAILED response.
Thank you for your response.

Forgot to mention, Putty has identical results (connection type Raw).
Putty -> Session request successful
Envisa -> "Login:"
Putty -> password as used with the HTTP interface
Envisa -> FAILED
Before putting the Envisa on a subnet that doesn't have internet visibility, is the active IP session with Eyez-on creating the problem with an additional request for a TCP/IP session?

Are you sure you have the correct password? Reset the password back to "user" and see if that works.

There is no interaction between the TPI and Envisalerts. They are two different software modules within the Envisalink.

Thank you for the update on the interaction. HTTP works fine with user and my password.
Yes, I'm sure I have the right password with CRLF having entered in on multiple PC's. Am I correct that the HTTP password is the same as the TPI?
I tried changing the password to "user" and it worked. The TPI status shows "ONLINE".
I changed the password back and it FAILED. I then tried removing the single numeric digit from the password and TPI not accepts it. I guess the TPI password doesn't like a numeric digit.

As far as I know it is supposed to take any alphanumeric characters.

Submit a support request with the details as you may have found a bug.

EnvisaLink firmware 01.11.135A (EVL3-Ademco)
I will submit a support request.
Thanks for all of your help. Now the fun begins.

From support:
A password can not be greater than 6 characters for the TPI interface where it can be for the HTTP sessions.
Not documented.
Issue is closed.