Re: programming an Ademco Vista

["Crash Gordon" <webmaster@xxxxxxxxxxxxxxxxxxxxx>]

cool...have fun!

--
**Crash Gordon**







<rickm@xxxxxxxxxxxxxx> wrote in message
news:be421883-fb07-41ef-9a11-486d0d26bceb@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> On Apr 23, 8:53 pm, "Crash Gordon" <webmas...@xxxxxxxxxxxxxxxxxxxxx>
> wrote:
>> *182 is for custom zones
>> just use *56 area and the zone types I gave or any of the standard ones
>> on
>> page 12
>>
>> --
>> **Crash Gordon**
>>
>> <ri...@xxxxxxxxxxxxxx> wrote in message
>>
>> news:93867c25-3c02-49f0-bb59-cdcd03d85e62@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>>
>> > On Apr 22, 10:08 pm, "Crash Gordon" <webmas...@xxxxxxxxxxxxxxxxxxxxx>
>> > wrote:
>> >> I hardly ever use customizable zone types.
>> >> Is there a reason you don't want to use normal zone types?
>>
>> >> 01 Entry/Exit #1 - delayed doors
>> >> 03 Perimeter - instant doors/windows
>> >> 04 Interior Follower - interior device (pir) that follows entry delay
>> >> if
>> >> delay zones are faulted first... but instant in other cases
>>
>> >> --
>> >> **Crash Gordon**
>>
>> >> <ri...@xxxxxxxxxxxxxx> wrote in message
>>
>> >>news:d3ddc02b-3c86-4da5-b671-44da1576e835@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>>
>> >> > Has anyone programmed an Ademco Vista 20P?  Whats a typical entry
>> >> > for
>> >> > *182:
>>
>> >> > 1)  door switches
>> >> > 2)  IR motion
>>
>> >> > thanks
>>
>> > Im after just a vanilla setup, the manual implies that *182 is
>> > required so thats what I was trying to get working.
>> > Sounds like that is not right so Im open.  Is *56 the right field?
>
> after *97 and *56, the Vista finally came up and showed some life.
> testing is next
>
> Thanks!!!