Search found 3 matches
- Tue Oct 08, 2013 11:06 pm
- Forum: EnvisaLink ( IP100D, IP170D, 2DS, 3, 4)
- Topic: My solution for local monitoring
- Replies: 0
- Views: 5384
My solution for local monitoring
Wanted to share my work, so far. Automating access to the TPI for monitoring data seems to be too cumbersome, for little gain. (I got timing issues with all the telnet and socket libraries i found) The easiest way I found to get all the info I need is to scrape the internal webpage on the EVL-3 ...
- Tue Oct 08, 2013 11:26 am
- Forum: EnvisaLink ( IP100D, IP170D, 2DS, 3, 4)
- Topic: Zone CLOSED 0 seconds ago
- Replies: 2
- Views: 4697
Re: Zone CLOSED 0 seconds ago
Update: I checked through the command line interface, via telnet: - The sensor is physically CLOSED. - The Keypad shows it closed - Command 001 shows it OPEN - Command 008 shows counter as FFFF (0 seconds) Data shown for all other sensors is correct. Any idea on how to solve this will be much ...
- Mon Oct 07, 2013 2:29 pm
- Forum: EnvisaLink ( IP100D, IP170D, 2DS, 3, 4)
- Topic: Zone CLOSED 0 seconds ago
- Replies: 2
- Views: 4697
Zone CLOSED 0 seconds ago
Hi
I have an EVL-3 connected to my DSC PC 1864, and most of it works ok.
The only problem is that in the EVL own web page 2 zones have a status of "CLOSED 0 seconds ago" and the counter never goes up.
The DSC keypad shows the correct status.
Is this a firmware issue?
Thanks
I have an EVL-3 connected to my DSC PC 1864, and most of it works ok.
The only problem is that in the EVL own web page 2 zones have a status of "CLOSED 0 seconds ago" and the counter never goes up.
The DSC keypad shows the correct status.
Is this a firmware issue?
Thanks