Re: Vista 20P not allowing program re-entry

[RTS <gafa@xxxxxxxxxxxxx>]

On 4/1/2021 8:10 AM, ABLE1 wrote:
> On 4/1/2021 4:27 AM, Airdorn wrote:
>>
>> Hiya all fellow alarm geeks :)
>>
>> Consider the following scenario:
>>
>>
>> 1. You install a Honeywell Vista 20P system, including finishing all
>> programming.
>>
>> 2. Months later, you return for whatever reason and attempt to access
>> programming using the installer code + 800. Instead of entering
>> program, you get the long high-pitched error beep disallowing
>> programming mode entry. The only solution is to cuss the original
>> installer for exiting with *98, cycle power, and re-entering program
>> with * & #.
>>
>> Only, it turns out that the installer, in fact, used *99 as normal,
>> and it turns out that a random fair amount of Vista 20P's since
>> firmware version 9.12 display this (errant ?) behavior.
>>
>> I have run into this randomly over the past years. Each time it
>> happens, I want to cuss the installers. But, really, they don't even
>> know about exiting program with *98... they are hardwired to use *99
>> as normal, for decades, because they are sheep-like.
>>
>> The more reasonable explanation is that there is some kind of bug in
>> the Vista firmware that is disallowing re-entry into program, as if
>> last exit from programming was with *98. (It wasn't -- they used *99)
>>
>> I am forced to wonder, what are the situations that would disallow
>> entry into the program using installer code + 800. I can think of two
>> situations:
>>
>> 1. Previous use of programming mode was exited with *98.
>>
>> 2. Auto-arm is used, and a schedule is programmed to use it.
>>
>>
>> Are there other configurations where installer code + 800 is
>> specifically disabled forgood reason, or is this a bug I have run into
>> for quite a while now?
>>
>> This is a potential problem beecause certain devices, like the
>> Alarm.com SEM, cannot function properly if they can't readily access
>> the Vista 20P system programming.
>>
>> Thanks!
>>
>
> Hi Airdorn,
>
> First let me say that the number of Vista systems that I have installed
> in the past 30 years could be counted on two hands.  I really never
> liked the programming structure.  That being said, what I am missing
> in reading your typing is, was your experience with just one panel
> install or multiple installs??  The difference could paint a different
> picture.  One would gather that it is multiple "over the years" but
> not sure. Also if it is multiple then is it 5 or 55??
>
> As for your installers not knowing the *98, it would seem to me that
> it is possible that one or two when exiting programming were just
> sloppy and hit *98 and did not realize the mistake.  At that point
> it was too late and since they did not know at the time how could
> they have corrected??  And if they did realize would they have
> remembered years later when asked by the boss??
>
> The other question would be is it repeatable??  With a particular
> panel that was "locked" can you then enter and exit multiple times
> with *99 and possibly get a repeat at some point??
>
> If it is multiple then it might be a thought to check the serial
> numbers of the boards.  If they are a close match then maybe, just
> maybe it is a bad batch that YOU only YOU managed to get a few
> and are experiencing the mystery!!
>
> As has happened to me of the years when I call Tech Support and
> describe my particular problem with a panel, the Tech Guy says;
> "Never heard that before!!"Â  And may comment back is; "Really??
> So that would mean that I am the very first guy on the planet
> that finds the problem first!! Multiple times!!  How it that
> possible??"Â  Sorry I could not raise the volume of my text!!
> But, I am sure you got it.  Which brings me to my next suggest
> have you call the guys at Ademco Tech Support to ask the question??
>
> Ok, I am tapped out for thoughts.  Hope they helped in some way!!
>
> Les
>
>


   what Les said..

but,  We have had your problem also,
What we found was if your panel is set for partitions,
and your on the wrong keypad, you'll get that behavior...

(program only from the partition 1 keypad...)

We also had a panel that would not revert back to *99
even when remotely changed to *99 in programming..

Never did figure out what was it's problem....
(trash canned that one...)

Les,  tech support isn't what it use to be back in the day....

Last time I had to call them,  I went through their whole
stable of reps, and not 1 could figure out what was happening..
Just luck I guess, after a nights sleep  I saw immediately
what was  wrong...

RTS
--

*Rocky T. Squirrel, esq.*