Re: Old Brinks equipment

[Hogan <napinc7@xxxxxxxxx>]

Hi Mark,

Well, if you really believe that to "standardize" programming on a mainboar=
d, means that only the central station telco is set in stone, go ahead and =
keep on believing that.

To really standardize programming, you would want to set other parts of the=
 board into non-changeable parameters.

It does not say much about that company's technicians, if they just cannot =
be trusted to input the correct telco number. I mean, they did send all the=
 zones to the central station anyway at the install, didn't they? If that c=
ompany was so concerned with 'standardization', they would have sent a sign=
al from each zone to the central station. Then, would they not have seen th=
at oops, no signals came in so I must have put in the wrong telco or accoun=
t number maybe???

Sorry, it sounds very hollow to hear that all that was "Standardized", was =
the central station number.

And was does that say about those techs who could not be trusted to use the=
 right telco number?=20

I think that it is time to face the truth, as it appears that you have been=
 in denial for quite a while. It's okay if you are not ready, at least just=
 think about it some. Perhaps in time you will see that it does not ring tr=
ue at all to everyone who has never been associated with Monitronics as lon=
g as you have.

ADT which is a much bigger company, they trusted their techs to input the r=
ight telco since they had very many different numbers. Gee wiz, if I could =
not trust a technician to use the right telco, I would not trust that tech =
to do anything right at all!!! He would be fired, and then, I guess he coul=
d go to work for Monitronics- and I would even give him a recommendation!

Also Mark, I do need to address your claim about the location of the inform=
ation. You see, years ago I discovered quite by accident about replacing th=
e chip in a Honeywell panel. A customer whom we had for years, needed a ser=
vice call and I had to get into the programming. The particular installer c=
ode for his system somehow did not work. I was very puzzled as normal proce=
dure before exiting programming for us is to do a final check on #88, as we=
ll as #20 to make sure. This system did not react, I was locked out. For so=
me reason that I do not remember, I somehow decided to just switch the chip=
 instead of changing out the board. I took a new board and carefully remove=
d the chip, and then inserted it into the locked board. Well, I was then ab=
le to easily get into power-up, then * and #, and voila, I was into program=
ming. So, I #20 and found that the installer somehow was corrupted as one o=
f the number was actually a letter. I changed it back to the original code =
for that system, powered down, and traded the chip back to the original tha=
t I had just taken out. And of course, everything worked just fine after th=
at.

So, the installer code is not on the removable chip, but somewhere on the b=
oard. That is why over the years, I have retrieved every installer code of =
every company that had previously monitored those systems. We have a very l=
arge list of competitor installer codes. I actually get a thrill when I go =
for a takeover and the previous company is unknown to me. I do not despair,=
 I just smile and get a chip off of a new board and install it on the exist=
ing system. That new competitor code is recorded and the whole thing might =
take 10 minutes. Ahh! Such a good feeling!

There are various other ways for other brands, some more time consuming, bu=
t always so rewarding. So, your line-by-line denunciations do not make a fa=
ct false, unless I thoroughly misinterpreted your comments.

You are aware that your name is plastered all over the internet on Monitron=
ics programming, don't you? That does make you appear to be a Monitronics g=
uy from way back at least to the early 2000s. You should make your readers =
aware of that fact though.

Well, I do hope that you have a good and safe day, sincerely. I am not tryi=
ng to marginalize you, it is just that I will not stand for incorrect infor=
mation. I would rather help folks as that is better. So now, anyone who rea=
ds this will know how to get into any Honeywell panel at takeover. We only =
lock them out while we are monitoring a system. We will even tell you the c=
ode of that system over the phone if we have to, since every one of our sys=
tems has a unique installer code anyway.=20

Hogan