[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

Re: programming an Ademco Vista



On Apr 27, 11:23=A0am, Frank Olson
<use_the_email_li...@xxxxxxxxxxxxxxxxxxxxxx> wrote:
> ri...@xxxxxxxxxxxxxx wrote:
> > On Apr 26, 3:51 pm, JoeRaisin <joerai...@xxxxxxxxxxx> wrote:
> >> ri...@xxxxxxxxxxxxxx wrote:
> >>> On Apr 24, 3:31 pm, "Crash Gordon" <webmas...@xxxxxxxxxxxxxxxxxxxxx>
> >>> wrote:
> >>>> cool...have fun!
> >>>> --
> >>>> **Crash Gordon**
> >>>> <ri...@xxxxxxxxxxxxxx> wrote in message
> >>>>news:be421883-fb07-41ef-9a11-486d0d26bceb@xxxxxxxxxxxxxxxxxxxxxxxxxxxx=
...
> >>>>> 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@xxxxxxxxxxxxxxxxxxxxxxxxxx=
m...
> >>>>>>> On Apr 22, 10:08 pm, "Crash Gordon" <webmas...@xxxxxxxxxxxxxxxxxxx=
id>
> >>>>>>> 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 d=
elay
> >>>>>>>> if
> >>>>>>>> delay zones are faulted first... but instant in other cases
> >>>>>>>> --
> >>>>>>>> **Crash Gordon**
> >>>>>>>> <ri...@xxxxxxxxxxxxxx> wrote in message
> >>>>>>>>news:d3ddc02b-3c86-4da5-b671-44da1576e835@xxxxxxxxxxxxxxxxxxxxxxxx=
.com...
> >>>>>>>>> Has anyone programmed an Ademco Vista 20P? =A0Whats a typical en=
try
> >>>>>>>>> for
> >>>>>>>>> *182:
> >>>>>>>>> 1) =A0door switches
> >>>>>>>>> 2) =A0IR 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. =A0Is *56 the right fiel=
d?
> >>>>> after *97 and *56, the Vista finally came up and showed some life.
> >>>>> testing is next
> >>>>> Thanks!!!- Hide quoted text -
> >>>> - Show quoted text -
> >>> Something is still not right. =A0The system is up, will arm and both
> >>> pads are talking to the main box yet none of the sensors trip the
> >>> alarm.
> >>> The motion sensor is getting power and is functioning. =A0The door
> >>> switch worked on the old main box. =A0I tried "test" and "chime" mod a=
nd
> >>> they do nothing. =A0There are no error mesages or faults.
> >>> The old alarm had each connection wired with a series resistor. =A0Thi=
s
> >>> manual doesnt really say if the resister should be connected
> >>> door =A0 =A0-------------------------- HI
> >>> switch ---------------/\/\/\/\-----LO
> >>> IR =A0 =A0 =A0 -------------------------- HI
> >>> sensor ---------------/\/\/\/\-----LO
> >>> pwr =A0 =A0---------------------------aux +
> >>> gnd =A0 =A0---------------------------aux -
> >>> Is this correct? =A0any suggestion on what to check?
> >> turn on chime and remove one leg of a door circuit from the panel.
>
> >> If you don't hear the chime go back and review the programming for the
> >> zones to make sure that you have the zone programmed for the proper zon=
e
> >> type and not just zeroed out.
>
> >> If you do hear the chime then you need to meter your wire and the door
> >> contacts to find out which is malfunctioning.
>
> >> Motion detector zones won't chime but you can do those and the doors as=

> >> well using 'walk test' - its in manual...- Hide quoted text -
>
> >> - Show quoted text -
>
> > In the home stretch!!!....The doors were set to EOL instead of N/C so
> > they are now working. =A0The IR motion is not working
> > though. =A0Ive tried NO ever mode and it fails the walk test. =A0The oth=
er
> > zones report a fault and chime but the IR doesnt report
> > anything. =A0I enabled the sensor's LED and its getting power and
> > "see's" movement. =A0 =A0I have it set to TYPE4 and NC which
> > allows the system to come READY. =A0 =A0I have the inline resister on th=
e
> > LO side on the panel.
>
> > any thoughts?
>
> > Thanks
>
> You don't need the resistor if your loops are programmed N/C (no EOL).
> Set the IR loop as a perimeter/chime for testing after you remove the
> resistor. =A0I'd close by saying "RTFM", but the Ademco products are a bit=

> of a challenge to program for a novice. =A0Glad things are workin' out.
> Keep us posted on your progress.
>
> Regards,
> Frank Olson- Hide quoted text -
>
> - Show quoted text -

Im replacing an Ademco 4030 which required a series resistor on each
loop.  Do you
recommend removing the resistor on both the doors and IR?

Also, the documentation for the IR does not specify if its N/C or N/
O.   What the typical setting?
If N/O, is a resisor required?

THANKS!!!!!


alt.security.alarms Main Index | alt.security.alarms Thread Index | alt.security.alarms Home | Archives Home