EyezOn Forum

I tried to wait for the ready cmd 650 to issue *1#. But this makes the panel go briefly into non-ready which then causes an infinite loop between ready and non-ready. The main reason to issue the bypass status request after disarming is to get an "actual" response from the panel about what...

EVL-4 with fw 1.2.130 on a DSC 1864 system The latest firmware upgrade seems to have changed how the Envisalink-4 responds to a bypass command in a script. In the past I was able to request bypass status (cmd 616 response) by sending cmd 0711*1# immediately after receiving cmd 655, 750 or 751 (disar...

Bypassed zones for partitions 2 and higher

Is there anyway to have the DSC panel communicate to EVL4 the bypass status of zones in partitions other than 1? The cmd 616 gets only triggered from partition 1 zone bypass changes. Something that should also be mentioned in the TPI.

I am trying to send cmd 200 ([200][Access Code]) after the panel sends cmd 900 due to an access code being required for a bypass action. However, I am always getting the error "IT-100/Envisalink Error (026): API User Code not Required." According to the TPI manual: The application will hav...

That's a bummer. I thought we finally would get complete bypass zone monitoring.

Also, I think the zones in each 8-byte section of the hex dump are reversed once you do the binary conversion, i.e. the order is zones 8-1; 16-9; 24-17 etc

I am testing out the new cmd 616 hexdump for bypassed zones. But it does seem to work only for partition One zones. Sending command 0711*1# gives me the hex dump but only bypassed zones in partition One are shown as bypassed. 0712*1# does not trigger a hex dump via cmd 616 at all. So there seems to ...