Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle Zone Bypass Status Message TPI Code 616. #46

Closed
rct opened this issue Jul 1, 2016 · 1 comment
Closed

Handle Zone Bypass Status Message TPI Code 616. #46

rct opened this issue Jul 1, 2016 · 1 comment

Comments

@rct
Copy link
Collaborator

rct commented Jul 1, 2016

Recently TPI response 616 - Zone Bypass Status was added to the TPI. See See http://forum.eyez-on.com/FORUM/viewtopic.php?f=6&t=301&start=80. NOTE: Envisacor has released DSC TPI 1.07 on June 1st, 2016

Bypassed Zones Bitfield Dump
This command is issued upon leaving Zone Bypass programming (_1 on the keypad). It is a 16 character HEX string representing an 8 byte bitfield. This bitfield indicates which zones are currently in bypass. A “1” indicates the zone is in bypass. The lower 8 zones are in the first position of the bitfield. The developer can force this dump by using the keystring commands to enter and leave zone bypassing. i.e. “_1#”

That description isn't terribly clear. 1st byte is zones 1-8 bitmap, 2nd byte is 9-16,

00 00 00 00 00 00 00 00
00 00 62 06 00 00 00 00
|| || || || || || || ||
|| || || || || || || ||
|| || || || || || || 57-64
|| || || || || || ||
|| || || || || || 49-56
|| || || || || ||
|| || || || || 41-48
|| || || || ||
|| || || || 33-40
|| || || ||
|| || || 25-32
|| || ||
|| || 17-24
|| ||
|| 9-16
||
1-8

To trigger the Zone Bypass response for Partition 1 send 0711*1#

Note: this only works for partition 1.

@juggie
Copy link
Owner

juggie commented Jul 16, 2016

Patched by @rct

@juggie juggie closed this as completed Jul 16, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants