Attached is the latest TPI documentation for the Envisalink 2DS, Envisalink 3, Envisalink 4, Envisalink 4MAX, and the DUO.
Note that the TPI protocols are different for DSC and Honeywell. Make sure you have the correct version for your panel.
NOTE: Envisacor has released a new version of the DSC version of the TPI Jun 9, 2024.
NOTE: In firmware versions 1.12.180 and 1.0.102 the TPI has an IPtable rule to close all connections that don't originate on the same LAN as the Envisalink. This can be overridden by changing the default user password.
NOTE: The Envisalink 4MAX and the DUO both support the TPI but be aware the default password is not "user", it is the last six HEX numbers of the MAC address of the device
Envisalink - TPI Documentation
Moderators: EyezOnRich, GrandWizard
-
GrandWizard
- Posts: 2319
- Joined: Tue Nov 16, 2010 4:08 pm
Envisalink - TPI Documentation
- Attachments
-
EnvisaLinkTPI-1-09.pdf- (299 KiB) Downloaded 495 times
-
- EnvisaLinkTPI-ADEMCO-1-03.pdf
- (104.96 KiB) Downloaded 10236 times
Re: Envisalink 2DS - TPI Documentation
Oh great GrandWizard... 
Is there a command missing from the TPI? I'm not able to find an application command that matches the "reset" function available in the web portal. Sending '#' doesn't seem to work with 070 nor 071.
Is there a command missing from the TPI? I'm not able to find an application command that matches the "reset" function available in the web portal. Sending '#' doesn't seem to work with 070 nor 071.
DscServer for android/linux/windows: https://sites.google.com/site/mppsuite/dscserver
-
GrandWizard
- Posts: 2319
- Joined: Tue Nov 16, 2010 4:08 pm
Re: Envisalink 2DS - TPI Documentation
Do you mean reboot or just sending a # key?
Re: Envisalink 2DS - TPI Documentation
Reset I think. Not sure I would use "reboot", and I wasn't able to send "#".
On the portal, when I click the "Commands" link for my device, on of the button choices is "Send Reset (#)".
I was playing with my interface and sent "*8xxxx" through the 2DS which put the alarm system into installers mode. After that the 2DS would not accept any more key commands through the TPI whether I used 070# or 0711# (I was trying to send # to exit from installer mode). I couldn't find a matching "send reset" command in the API.
Once in installer mode the 2DS responds to all commands (that I tried) with 502 017 - Keybus Busy – Installers Mode (Panel is in installers mode, most functions are unavailable), and I was not able to do anything to clear it. Which by the way, is another feature request - can we keep the key related TPI commands active when in installer mode, and pass back the DSC's responses? This would allow the security system to be programmed through the 2ds.
Mike
On the portal, when I click the "Commands" link for my device, on of the button choices is "Send Reset (#)".
I was playing with my interface and sent "*8xxxx" through the 2DS which put the alarm system into installers mode. After that the 2DS would not accept any more key commands through the TPI whether I used 070# or 0711# (I was trying to send # to exit from installer mode). I couldn't find a matching "send reset" command in the API.
Once in installer mode the 2DS responds to all commands (that I tried) with 502 017 - Keybus Busy – Installers Mode (Panel is in installers mode, most functions are unavailable), and I was not able to do anything to clear it. Which by the way, is another feature request - can we keep the key related TPI commands active when in installer mode, and pass back the DSC's responses? This would allow the security system to be programmed through the 2ds.
Mike
DscServer for android/linux/windows: https://sites.google.com/site/mppsuite/dscserver
Re: Envisalink 2DS - TPI Documentation
Mike, this would be an omission in the docs. You can't operate the the TPI in installers mode as none of the installer's feedback mechanisms (these passthroughs you talk of) are supported.
I will add a feature to our bug tracker to allow you to get out of installers with a #. That should prevent you from being stranded in "installers". This is problematic because DSC doesn't "time out" when in installers.
Eventually, when the pile of work stops getting bigger, we inted to offer a virtual keypad but it is not going to be soon.
I will add a feature to our bug tracker to allow you to get out of installers with a #. That should prevent you from being stranded in "installers". This is problematic because DSC doesn't "time out" when in installers.
Eventually, when the pile of work stops getting bigger, we inted to offer a virtual keypad but it is not going to be soon.
Re: Envisalink 2DS - TPI Documentation
I understand about the keypad. Thanks, the reset function will be very handy.
DscServer for android/linux/windows: https://sites.google.com/site/mppsuite/dscserver
Re: Envisalink 2DS - TPI Documentation
Hi guys, another doc question if I may.
I don't see a way to send a function key to the panel, am I right to assume it's not possible? Or can I send a function key the same way I did on the IT100 - characters a-f were function key 1-5, and I could also send the Fire/Ambulance/Police keys that way (though I know I could use code 060 instead).
Code 070 says that I could send the character "A" while 071 does not, is that a typo. Or a secret feature?
Mike
I don't see a way to send a function key to the panel, am I right to assume it's not possible? Or can I send a function key the same way I did on the IT100 - characters a-f were function key 1-5, and I could also send the Fire/Ambulance/Police keys that way (though I know I could use code 060 instead).
Code 070 says that I could send the character "A" while 071 does not, is that a typo. Or a secret feature
?Mike
DscServer for android/linux/windows: https://sites.google.com/site/mppsuite/dscserver
Re: Envisalink 2DS - TPI Documentation
Its been so long I needed to look at the code to answer this one.
The reason that you can't send function keys is that these are somewhat meaningless as keypad function keys are mapped to other "real" functions like "arm stay" and "arm away". You would need to program the Envisalink with what function you would like F1 to do. Which is a little silly, and a waste of perfectly good code space!
As for the A, yes, this is a secret feature.
The reason that you can't send function keys is that these are somewhat meaningless as keypad function keys are mapped to other "real" functions like "arm stay" and "arm away". You would need to program the Envisalink with what function you would like F1 to do. Which is a little silly, and a waste of perfectly good code space!
As for the A, yes, this is a secret feature.
Re: Envisalink 2DS - TPI Documentation
Makes sense, thanks. I'll have to check out that "eh" key. A truly Canadian version should contact Tim Horton's . Mike
. MikeDscServer for android/linux/windows: https://sites.google.com/site/mppsuite/dscserver
Re: Envisalink 2DS - TPI Documentation
Hi!
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.
Also, I don't know if new features have been implemented, but I do not see any forum topic or specific TPI documentation for the Envisalink 3 which is the one I have. I imagine the only difference between the 2DS and the 3 is the support for Honeywell Vista systems?
Thanks!
James
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.
Also, I don't know if new features have been implemented, but I do not see any forum topic or specific TPI documentation for the Envisalink 3 which is the one I have. I imagine the only difference between the 2DS and the 3 is the support for Honeywell Vista systems?
Thanks!
James