EyezOn Forum

These are questions for the Eyez-on folks.....

I have the EVL3 working with this panel and I'll post the exact instructions on how I did it later but I have a few questions first....

When Eyez-on instructions say "Communicator is address 3 and cannot be changed" do you mean it can't be changed in the panel or that EVL3 requires that it be address 3?

On later high-end panels ANY address can be programmed as an LRR and in many configurations address 3 is used for wireless expansion modules this too can be changed but I wanted to ask is there is some EVL3 requirement before I change things around.

Second question I've noticed that once the EVL3 starts a TCP session it seems to take a very long time for it to forget that session and begin a new session to a different IP address. I noticed here in the forum that some others have also said even with a board reboot they've found that the original TCP session was still active. If this is the case, it would be useful to be able to easily tell the EVL3 to completely forget about a session. It should, at a minimum forget the session on reboot. Am I missing something or is this truly a problem?

Lastly, and related to the above question, can the EVL3 do both a TPI session and an Eyez-on portal session simultaneously?

Thanks,
Ron

Wingspinner wrote:These are questions for the Eyez-on folks.....

When Eyez-on instructions say "Communicator is address 3 and cannot be changed" do you mean it can't be changed in the panel or that EVL3 requires that it be address 3?

On later high-end panels ANY address can be programmed as an LRR and in many configurations address 3 is used for wireless expansion modules this too can be changed but I wanted to ask is there is some EVL3 requirement before I change things around.

Unfortuntely the Envisalink is hardcoded to Address 3 for the external communicator

Second question I've noticed that once the EVL3 starts a TCP session it seems to take a very long time for it to forget that session and begin a new session to a different IP address. I noticed here in the forum that some others have also said even with a board reboot they've found that the original TCP session was still active. If this is the case, it would be useful to be able to easily tell the EVL3 to completely forget about a session. It should, at a minimum forget the session on reboot. Am I missing something or is this truly a problem?

Lastly, and related to the above question, can the EVL3 do both a TPI session and an Eyez-on portal session simultaneously?

I honestly haven't a clue what you're referring to. The Envisalink only uses TCP for three things: firmware updates, HTTP, and TPI. Communications with the Eyezon alerting servers uses the Envislerts protocol which uses UDP for transport. The TPI and Envisalerts are unrelated.

GrandWizard wrote: I honestly haven't a clue what you're referring to. The Envisalink only uses TCP for three things: firmware updates, HTTP, and TPI. Communications with the Eyezon alerting servers uses the Envislerts protocol which uses UDP for transport. The TPI and Envisalerts are unrelated.

Thanks for the answer on the LRR thing. That's an easy fix on the higher end panels.

WRT my question.... I should have made the question more clear. Basically, I was asking if the card drops TPI sessions when it's communicating to Eyezon servers. You say they are unrelated so I'm taking that as a no. Please correct me if that's not the case.

The problem I was having is your card would stop communicating to my Vera shortly after a TPI session was started. The TCP session appeared to be intact but the card wasn't sending any data. Not really sure what the problem is but it sounds similar to something I read about in another post somewhere here on the forum. I solved the problem by having the EVL3 connected directly to the Vera. It doesn't seem to like having a wireless connection to the vera. At this point I've spent far too much time troubleshooting it so I'm going to re-architect my network topology so the EVL3 is connected directly to the Vera.

Thanks for your help.

One last thing, in your instructions you appear to call the EVL3 the "communicator" which it is but the LRR is also referred to as a "communicator" which creates some confusion. It would be good to clarify the wording.

Thanks again,
Ron