Page 12 of 13
Re: Envisalink - TPI Documentation
Posted: Tue Jan 29, 2019 8:47 pm
by lonewolf
With only SSH access,
Code: Select all
tcpdump -p -n -i <interface> -X -s0 -w capturefile.pcap host <ip address>
is my go-to, and then just scp/rsync the capturefile.pcap file to your computer and open in Wireshark.
Yeah, it's almost certainly the re-use of the source port which is causing it. Since the EVL never dropped the connection, seeing a SYN on what it considers an already established connection is confusing it. I don't think this is specific to the EVL/TPI, I'd expect a hung connection as a possibility on any TCP server this happens to.
Re: Envisalink - TPI Documentation
Posted: Wed Dec 04, 2019 9:11 am
by cmh31909
Have there been any updated documents released? The only one's I can find are in this thread which is dated 2012, seven years old.
Re: Envisalink - TPI Documentation
Posted: Wed Dec 04, 2019 10:30 pm
by lonewolf
cmh31909 wrote:Have there been any updated documents released? The only one's I can find are in this thread which is dated 2012, seven years old.
? Both of the PDFs in the first post of this thread are dated 2017-02-10.
Re: Envisalink 2DS - TPI Documentation
Posted: Fri Jun 07, 2024 9:17 am
by nick211
integris wrote: ↑Wed Sep 12, 2012 2:54 pm
I was busy creating a Visual Basic application to implement the TPI when I came across command 912 on page 8 of the TPI PDF. According to the document, the command returns 1 data byte. I assume this is a typo. Also, the descriptive text is exactly the same as command 900 which is not very helpful in determining what command 912 does different compared to 900.
Did you ever end up figuring out what the 912 command is actually for? The title says 'Command Output Pressed', but the description makes it sound like you need to send an access code after receiving the 912 command.
Re: Envisalink 2DS - TPI Documentation
Posted: Fri Jun 07, 2024 10:43 am
by lonewolf
nick211 wrote: ↑Fri Jun 07, 2024 9:17 am
integris wrote: ↑Wed Sep 12, 2012 2:54 pm
I was busy creating a Visual Basic application to implement the TPI when I came across command 912 on page 8 of the TPI PDF. According to the document, the command returns 1 data byte. I assume this is a typo. Also, the descriptive text is exactly the same as command 900 which is not very helpful in determining what command 912 does different compared to 900.
Did you ever end up figuring out what the 912 command is actually for? The title says 'Command Output Pressed', but the description makes it sound like you need to send an access code after receiving the 912 command.
My assumption is it reports when someone does a *7x command function on a keypad. The panel manual says
The description text for 912 is just a copy/paste error from 900.
Re: Envisalink 2DS - TPI Documentation
Posted: Sat Jun 08, 2024 7:27 pm
by nick211
lonewolf wrote: ↑Fri Jun 07, 2024 10:43 am
The description text for 912 is just a copy/paste error from 900.
It does look like a copy paste error to me too. Can we get official confirmation on this one. The developer of the Home Assistant add-on has programmed it so that Envisalink is requesting a user code after receiving a 912 command. If this is actually not the case we should clarify this.
https://github.com/ufodone/envisalink_n ... 2153942823
Re: Envisalink - TPI Documentation
Posted: Sun Jun 09, 2024 11:10 am
by GrandWizard
I have received the updated document and posted 1.09 version of the TPI.
It includes the 912 clarification as well as a new command for sensor low-bats.
Re: Envisalink - TPI Documentation
Posted: Sun Sep 08, 2024 5:46 am
by nuclear__
Can someone give me some help?
I'm trying to send keystrokes to bypass a zone but it has no affect.
From keypad (while its blank) i can press *115# to bypass zone 15 and i can continue with *116# for zone 16 etc....
But from tpi it doesnt work.
i send 071*115#7C System responds : 5020212A which means (API Command Partition Error (Requested Partition is out of bounds))
if i try 0711*115#AD then system responds 50201028 (Keybus Transmit Buffer Overrun)
then i break it down to 2 commands
0711*1158A
0711#EC
and then to 2 different commands
0711*124 (Response: 50201028)
07115#21 (Response: 5000712D)
i go with try and error.... any help appreciated!
Re: Envisalink - TPI Documentation
Posted: Mon Sep 09, 2024 9:18 am
by K-Man
Keybus Transmit Buffer Overrun means that the API already has data queued for the panel when this new command came in. So it is busy.
Try slowing down your commands to the API. The DSC key-bus is VERY slow, and was meant for human interactive timings, not M2M.
Re: Envisalink - TPI Documentation
Posted: Tue Sep 10, 2024 7:34 am
by nuclear__
Thanks BuxtonCalvin .
I will try. I had place 2 seconds delay between each zone bypass command ,may be needs more.