60-806 help
|
|
Thread rating:  |
brihyn - 18 Apr 2009 22:30 GMT ok, so common story, we bought a house that had a GE 60-806 security alarm system, and previous owners claim to have no idea what the codes were. Last night I decided to start screwing around with it to see if I could make any guesses. Wife suggested the street address, and that didn't work, so I tried the address backwards (or so I think) and voila, I was suddenly armed in stay mode. Butttttt.... I can't turn the dang thing off. 1 <backwards address> (or anything resembling the backwards address...numbers out of order, partial numbers, etc) won't turn it off. Unplugged the unit and battery overnight, but as I feared, the armed status must stay in memory, as it is still armed 16 hours later when I plugged it in. Left a door open as it beeps down to arming thinking maybe that would suspend the arm mode, but yeah, just sounded the alarm (luckily there's no longer phone service to the unit) Soooo... any way to force this thing to disable? am i missing something and the code that i thought i entered last night just isn't working? (i enter one, it asks for code, i enter the 5 digits, nothing happens)
If I"m ultimately forced to push the thing back to factory defaults, is there an installer manual somewhere? and if I have to buy the programmer keypad for the panel itself, anyone have a cost and/or link? Frustrated and locked in, Brian
Frank Olson - 18 Apr 2009 22:35 GMT > ok, so common story, we bought a house that had a GE 60-806 security > alarm system, and previous owners claim to have no idea what the codes [quoted text clipped - 23 lines] > Frustrated and locked in, > Brian When you started pressing keys randomly I suggest that you entered the "quick arm" shortcut. The only way to turn the system off is via one of the user codes. You won't be able to enter programming until the system is disarmed. Unless some kind soul can provide you with the previous owners user code, you're hooped. Now... If some kind soul had programmed a keyfob for arm/disarm, you only have to find that. Good luck!!!
Crash Gordon - 19 Apr 2009 05:30 GMT I agree with Frank...you weren't even close to guessing the code...you quick armed it. Good luck getting it disarmed now.
There's two things you never, ever, ever do on a Friday night; one is attempt to "fix" your own computer, the other is push buttons on an alarm system you don't know the codes to.
 Signature **Crash Gordon**
> ok, so common story, we bought a house that had a GE 60-806 security > alarm system, and previous owners claim to have no idea what the codes [quoted text clipped - 23 lines] > Frustrated and locked in, > Brian Frank Olson - 19 Apr 2009 05:55 GMT > I agree with Frank...you weren't even close to guessing the code...you quick > armed it. [quoted text clipped - 3 lines] > attempt to "fix" your own computer, the other is push buttons on an alarm > system you don't know the codes to. There's nothing wrong with "fixing" your own computer as long as you know what you're doing, have "backups" for everything, and parts "on hand" for the time that your power supply suddenly decides to "go south".
As for "pushing buttons" randomly... That's just plain ignorance, which we can't fault the OP for. Most indivuals that buy a new house with a "built in" alarm system usually get the relevant codes from the previous owner/occupants. OTOH, most homeowners have ongoing monitoring contracts which may stipulate to a clause that they don't actually "own" the equipment they're using... all I can say is: "Let the games begin!" :-)
brihyn - 19 Apr 2009 06:09 GMT On Apr 18, 11:55 pm, Frank Olson <use-the-email- li...@yoursecuritysource.com> wrote:
> > I agree with Frank...you weren't even close to guessing the code...you quick > > armed it. [quoted text clipped - 3 lines] > > attempt to "fix" your own computer, the other is push buttons on an alarm > > system you don't know the codes to. Considering I'm a network engineer and manage around 150 servers myself, I don't really mind fixing my own computeer on a friday night. And having previously been in a position of qa'ing and doing component- level repairs on security and fire alarm circuit boards (read: I had to troubleshoot down to the individual integrated circuiit or circuite board trace), along with designing and implementing my own fully functional monitoring system at the previous house, this doesn't seem that bad to me. Again, if I can get the programmer board and installer manual, I can reset the thing back to original defaults and reprogram it myself. And really, is having it unplugged right now worse than having it plugged in but unusable, as it was prior to me "randomly pushing buttons"??? We've been here 6 months and up until now, the security system was useless. So thanks for the condescending attitude, but can we get back to actually answering my original question?
Frank Olson - 19 Apr 2009 06:52 GMT > Considering I'm a network engineer and manage around 150 servers > myself, I don't really mind fixing my own computeer on a friday night. [quoted text clipped - 4 lines] > functional monitoring system at the previous house, this doesn't seem > that bad to me. Well, you're "one up" on me... I would NEVER undertake to do a board level repair on a fire alarm system... But then, I run a service company that has obligations that go beyond "fat fingering" a part of a life safety system whereas you... manage servers... Gee... If my server goes "down", it means I can't get emails... Oh bliss!!! :-)
> Again, if I can get the programmer board and installer manual, I can > reset the thing back to original defaults and reprogram it myself. And [quoted text clipped - 4 lines] > So thanks for the condescending attitude, but can we get back to > actually answering my original question? "Programmer board"??? Where'd you get that notion?? And all the installer manual will tell you at this point is that you can't enter programming mode while the system is armed. There is no "east tunnel" and there is no "back door" into your system. What part of "hooped" don't you understand, "Mr. Network Engineer"??
You're back to "square one". You have to replace the common control board (easy for a Network Engineer that manages 150 servers), and then program your system "from scratch"... I won't say that'll be "easy" as you're having difficulty understanding the concept of being "hooped"... but I can hope! :-)
brihyn - 19 Apr 2009 07:14 GMT On Apr 19, 12:52 am, Frank Olson <use-the-email- li...@yoursecuritysource.com> wrote:
> > Considering I'm a network engineer and manage around 150 servers > > myself, I don't really mind fixing my own computeer on a friday night. [quoted text clipped - 31 lines] > you're having difficulty understanding the concept of being "hooped"... > but I can hope! :-) Frank- My comments were not meant towards you originally. Your first 2 replies were indeed helpful, and I don't doubt I messed up. And i worked for a fire/security alarm manufacturer as a QA tech. So I have a pretty thorough understanding of how the boards actually operate behind the scenes. I wasn't just seeing how sh.t worked. People's lives did actually depend on me knowing how to read a fire alarm's circuit board. But as for the rest your snarky reply, yeah, you don't get email. But there's a hell of a lot of critical systems that run on servers. An outage can cost a hell of a lot more money in 30 minutes of downtime in my company than someone walking away with everything in my house. And frankly, the fact that the security i put in place in my networks is securing a pretty large chunk of the nation's health insurance records seems a bit more risky than the chimp who installed the system in this house undertook. And where did i get the notion of an installer manual and programmer board helping me? from quite a few boards. Do a google on "reset 60-806" yourself and see where I might have gotten that idea. Yes, i could send this in so that they could reprogram the EEProm. Or I could simply short out the reset pins and reprogram the door, window, and glass break zones myself, just like the installer who original put the system in place had to do. Wow....you're right. I don't have the skills that most security installers get in their monkey training classes (and sure, there are quite a few decent installers out there. But I've run into a hell of a lot more who had absolutely no idea what security really means installing in corporate offices). So again, thanks for your first two replies. They WERE helpful, and I don't deny that I probably shouldn't have been jacking with the thing. But kiss my butt on your last email. You still haven't denied that I'm no worse off tonight than i was a day ago.
JoeRaisin - 19 Apr 2009 16:52 GMT > On Apr 19, 12:52 am, Frank Olson <use-the-email- > li...@yoursecuritysource.com> wrote: [quoted text clipped - 63 lines] > But kiss my butt on your last email. You still haven't denied that I'm > no worse off tonight than i was a day ago. So, we're all just a bunch of monkeys. What does that say about you coming here asking for help from us?
Did you bother to research the panel and it's operation before you started punching buttons? Maybe you should have looked for manual before you f.cked with it. Yeah - you're a rocket scientist alright.
We've had a couple of IT guys try their hand at our company and with only a few exceptions they couldn't cut it as alarm installers. Most of them are either too lazy to go into attics or crawl spaces or too arrogant to take advice.
For a follow-up are you going to go to the local tattoo parlor, call the guy an inbred ink-monkey and then ask for a tattoo?
Frank Olson - 19 Apr 2009 17:11 GMT > Frank- > My comments were not meant towards you originally. Your first 2 [quoted text clipped - 4 lines] > lives did actually depend on me knowing how to read a fire alarm's > circuit board. There are several things that you've stated that just plain don't make sense (not that I'm "counting"). As a "QA Tech", I don't quite understand how "people's lives" depended on your ability to be able to "read a fire alarm's circuit board". It either "works" or it doesn't. I've worked with several fire alarm manufacturers and their "QA Techs" did nothing more than plug the board in and ensure it passed the test parameters set by the guys that engineered the thing. If it didn't, the unit was "diverted" back to R&D. Now... If you'd told us you were into R&D that would be an entirely different kettle of fish.
> But as for the rest your snarky reply, yeah, you don't get email. It wasn't intended to be "snarky". Notice the smiley??
> But > there's a hell of a lot of critical systems that run on servers. An > outage can cost a hell of a lot more money in 30 minutes of downtime > in my company than someone walking away with everything in my house. I agree completely and I didn't intend to demean your work as a network engineer.
> And frankly, the fact that the security i put in place in my networks > is securing a pretty large chunk of the nation's health insurance > records seems a bit more risky than the chimp who installed the system > in this house undertook. Uh-huh... That "chimp" do a poor job?? Why blame your own stupidity (for pushing buttons at random on a system you have admitted you don't have the codes for) on the "chimp that installed your system?? And why demean the individual (and the people that participate in this forum) with the use of such derogatory remarks?? Do you intend to win us over? I don't think you're going about it in just quite the right way.
> And where did i get the notion of an installer manual and programmer > board helping me? from quite a few boards. Do a google on "reset [quoted text clipped - 7 lines] > But I've run into a hell of a lot more who had absolutely no idea what > security really means installing in corporate offices). Y'know... I'm not even going to go where you're going here. I'm just going to let your comments stand on their own. It demonstrates beyond measure what you think about the people in our industry. Why I even bothered to respond to such an arrogant, opinionated a.shole I'll never know. You should read up on Netiquette before participating in a message board such as this. The "smileys" I placed in several key parts of the response which has engendered such a reply on your part should have clued you in to the fact that what I said was in jest.
> So again, thanks for your first two replies. They WERE helpful, and I > don't deny that I probably shouldn't have been jacking with the thing. > But kiss my butt on your last email. You still haven't denied that I'm > no worse off tonight than i was a day ago. And why should I? You are no worse off than you were a day ago, unless of course, your system also employs smoke detectors, in which case, killing the panel circumvents their usefulness and places your family at risk (as Joe has already pointed out). Good job, Mr. Network Engineer!
Doug - 19 Apr 2009 17:37 GMT > brihyn wrote: > > Considering I'm a network engineer and manage around 150 servers [quoted text clipped - 3 lines] >records seems a bit more risky than the chimp who installed the system >in this house undertook. Its been said that if you give enough chimps, enough typewriters and enough time, they will eventually type the entire works of Shakespeare, so it shouldn't be too hard for a network engineer to stumble across the right code, of course it might take a little longer than the chimp with a typewriter, in part because the chimp has no grandiose attitude to get in the way.
So, my advice would to get off your high horse, grab yourself a chair and a banana, sit yourself down in front of the keypad and have at it.
Doug
brihyn - 19 Apr 2009 18:17 GMT just to make a few things clear: 1) I have never been on a high horse. I came here with my tail between my legs asking for help. 2)I've noted numerous times that I do agree that randomly pushing buttons wasn't necessarily a smart thing to do. At the same time, I had nothing to lose, as the alarm was just as useless before as it is now. 3) I never mentioned the network engineer side until Crash told me that what I was just dumb as "trying to fix your pc on a friday night". I merely mentioned that I have no problems fixing my pc on a friday night myself. 4) as for my experience with alarms...Just mentioning that I am not a run of a mill home owner. I *do* have experience on some level with alarms. In fact, I would rightly argue that I have more knowledge of how an alarm board works than 99% of installers because of this experience having to fix and repair them. Does that help me in this case? Unfortunately, not a bit. But it *is* a fact that I've worked on a level on these circuit boards that few here have. (if only it DID help resolve my mistake!) 5) Can you argue that a lot of installers really do know what they're doing and more importantly, why? An installer that truly understands the "why" of security beyond just the "how" of installing is worth his weight in gold. No argument.. But I found in hiring installers on the corporate side that frankly, my sales guy knew a lot more of how to actually keep a building safe then the installers. They knew how to run the wiring, etc, but failed the most critical piece...looking at the buiilding from the point of view of a thief, and alter their work accordingly. They were just doing what they were trained, and nothing beyond. Are all installers that way? thankfully no. Maybe "trained monkey" came off wrong, but it's the case in any career path. a trained monkey can do what they were trained, and can't look beyond. Installers can be that way, network engineers can be that way. And unfortunately, i've run into too many of both. (note, i refuse to use the annoying phrase here of "looking outside of the box". Maybe that wouldn't have ruffled the feathers quite so badly, but I just hate that phrase) 6)Do I respect someone to crawl into crawlspaces? more than I can express here. I had a stint of doing side-contracting of running network cabling. Great pay, and I'd do it again, but words can not express how much I hated the work. Again, thanks for the constructive answers. And I realize my original reply created the stir. It was meant directly at Crash. Re-read the thread again from the top. I simply asked how to fix my screw up, Frank gave me a great reply that what I did was worse than I had thought, and than Crash responded with the most snarky reply of all.
Crash Gordon - 20 Apr 2009 03:01 GMT btw...my use of "you" was generic...not necessarily you you.
 Signature **Crash Gordon**
> just to make a few things clear: > 1) I have never been on a high horse. I came here with my tail between [quoted text clipped - 41 lines] > Frank gave me a great reply that what I did was worse than I had > thought, and than Crash responded with the most snarky reply of all. Frank Olson - 20 Apr 2009 05:39 GMT > just to make a few things clear: > 1) I have never been on a high horse. I came here with my tail between > my legs asking for help. You asked politely and were told (equally politely) that you were "hooped". There was no reason to drag in the "chimp" and "monkey" comments.
> 2)I've noted numerous times that I do agree that randomly pushing > buttons wasn't necessarily a smart thing to do. At the same time, I > had nothing to lose, as the alarm was just as useless before as it is > now. Aux contraire (as they say in Quebec). You should never push "random buttons" on something you have no clue about. Imagine what could have happened had Bush decided to randomly push buttons on the football when he first stepped into office.
> 3) I never mentioned the network engineer side until Crash told me > that what I was just dumb as "trying to fix your pc on a friday > night". I merely mentioned that I have no problems fixing my pc on a > friday night myself. Check.
> 4) as for my experience with alarms...Just mentioning that I am not a > run of a mill home owner. I *do* have experience on some level with [quoted text clipped - 4 lines] > a level on these circuit boards that few here have. (if only it DID > help resolve my mistake!) You obviously don't have the knowledge you say you do. I'm thinking that if you did have the knowledge of how the board works, you wouldn't have been pushing buttons randomly now, would you?
> 5) Can you argue that a lot of installers really do know what they're > doing and more importantly, why? An installer that truly understands [quoted text clipped - 13 lines] > wouldn't have ruffled the feathers quite so badly, but I just hate > that phrase) Now you're saying an installer has to think like a thief... Most idiots that perform B&E's are on drugs and they're looking for a few bits of merchandise they can "hock" to pay for their next fix. They're "in" and "out" before the Police (or other local constabulary) can respond. All an installer will do is install the equipment you paid for. Most aren't going to try and "upsell" you, although if asked, most will tell you where they figure the "holes" in your security are. It's sort of like the guy that goes out and decides to protect his PC against viruses with "free" software he can get on the Internet. AVG is one such company that provides two levels of protection. The "free" version doesn't have all the features of the "paid" version. You get what you pay for. In your case, you purchased a house with a security system you knew nothing about. My first instinct would have been to call someone in to reset the codes if the original homeowner couldn't (or wouldn't) provide them. But then, I consider myself to be a reasonably prudent individual and not some "chimp" or "chump".
> 6)Do I respect someone to crawl into crawlspaces? more than I can > express here. I had a stint of doing side-contracting of running > network cabling. Great pay, and I'd do it again, but words can not > express how much I hated the work. Yeah... the "chimp" work sucks.
> Again, thanks for the constructive answers. And I realize my original > reply created the stir. It was meant directly at Crash. Re-read the > thread again from the top. I simply asked how to fix my screw up, > Frank gave me a great reply that what I did was worse than I had > thought, and than Crash responded with the most snarky reply of all. Crashes response wasn't as "snarky" as some get. I think you over reacted. And if what you've posted here is an attempt at apologizing, it falls far short of that too. To me, you're just trying to justify your response which was assinine in the extreme through "frenetic back-peddaling". A simple "I'm sorry" would have gone a lot further, but all of this is now "water under the bridge". My original response still stands. You're "hooped", buddy. Find yourself a friendly local alarm provider, keep the "chimp" and "monkey" comments to yourself, "bite the bullet" and pay for your bad judgement. Hopefully, the "ape" that responds to your plea for help won't charge you more than a couple of bananas.
Robert L Bass - 20 Apr 2009 05:51 GMT > Aux contraire (as they say in Quebec)... If both Quebec and Texas secede they can become the nation of Quebexas. They could even have a team called the Montreoilers.
Frank Olson - 20 Apr 2009 06:42 GMT >> Aux contraire (as they say in Quebec)... > > If both Quebec and Texas secede they can become the nation of Quebexas. > They could even have a team called the Montreoilers. Heh... Try saying "howdie partner" with a French accent... It just doesn't sound right... :-)
CH®IS - 21 Apr 2009 00:27 GMT "Frank Olson" wrote...
>>> Aux contraire (as they say in Quebec)... >> [quoted text clipped - 3 lines] > Heh... Try saying "howdie partner" with a French accent... It just > doesn't sound right... :-) As if the two accents on their own aren't bad enough already... don't mix them.
Haven't we gotten rid of Quebec yet? Someone should get on that.
Jim - 21 Apr 2009 04:39 GMT > "Frank Olson" wrote... > [quoted text clipped - 10 lines] > > Haven't we gotten rid of Quebec yet? �Someone should get on that. Get ON it?????????????
Jeeeeze you guys have been talking about that for the last 40 years.
CH®IS - 21 Apr 2009 07:19 GMT "Jim" wrote...
> > Haven't we gotten rid of Quebec yet? �Someone should get on that. > > Get ON it????????????? > > Jeeeeze you guys have been talking about that for the last 40 years. Exactly my point. You'd think something could have been accomplished by now.
How many more kids from all across Canada will we send to France to get laughed at when they realize they don't even know how to speak french after taking it in school for so many years. If they could keep their language issues to themselves they could possibly stay... or they could still just go away.
Petem - 21 Apr 2009 16:19 GMT "CH®IS" <sh@dy.ca> a écrit dans le message de groupe de discussion : lx7Hl.24550$PH1.898@edtnps82...
> "Frank Olson" wrote... >>>> [quoted text clipped - 10 lines] > > Haven't we gotten rid of Quebec yet? Someone should get on that. Need some help?
Robert L Bass - 22 Apr 2009 00:45 GMT > Heh... Try saying "howdie partner" with a French accent... It just doesn't > sound right... :-) About like trying to say "bonsoir, mon dieu" with a Texas drawl?
 Signature Regards, Robert L Bass
==============================> Bass Home Electronics DIY Alarm and Home Automation Store http://www.bassburglaralarms.com Sales & Service 941-870-2310 Fax 941-870-3252 ==============================>
Jim - 22 Apr 2009 17:46 GMT On Apr 21, 7:45�pm, "Robert L Bass" <Sa...@BassBurglarAlarms.com> wrote:
> > Heh... �Try saying "howdie partner" with a French accent... �It just doesn't > > sound right... �:-) > > About like trying to say "bonsoir, mon dieu" with a Texas drawl? > > -- Bone Sawyer .... man doo?
Robert L Bass - 23 Apr 2009 03:58 GMT > Bone Sawyer .... man doo? Nope. That's clearly a Nu-yawk accent. In Texas it's more like bow-uhn swah mayan dee-yew.
Jim - 24 Apr 2009 04:03 GMT On Apr 22, 10:58�pm, "Robert L Bass" <Sa...@BassBurglarAlarms.com> wrote:
> > Bone Sawyer � .... man doo? > > Nope. �That's clearly a Nu-yawk accent. �In Texas it's more like bow-uhn swah > mayan dee-yew. Since you're closer to Texas than I am ......... I defer.
Robert L Bass - 25 Apr 2009 04:57 GMT > Since you're closer to Texas than I am ......... I defer. I've been there a number of times. What I saw I didn't find particularly interesting. The northern part of the state (the "panhandle") is mostly dust and weeds, separated by occasional clumps of houses and run-down bars. DFW is an over-built, dirty area that's bone dry when it isn't flooded. The area around Austin is the only part I'd consider livable.
 Signature Regards, Robert L Bass
==============================> Bass Home Electronics DIY Alarm and Home Automation Store http://www.bassburglaralarms.com Sales & Service 941-870-2310 Fax 941-870-3252 ==============================>
G. Morgan - 22 Apr 2009 21:46 GMT >About like trying to say "bonsoir, mon dieu" with a Texas drawl? Easy: Bone-sore Mountain Dew.
alarman - 20 Apr 2009 04:48 GMT >Wow....you're right. I don't have the > skills that most security installers get in their monkey training > classes (and sure, there are quite a few decent installers out there. > But I've run into a hell of a lot more who had absolutely no idea what > security really means installing in corporate offices). Seems like your arrogance has made a monkey out of you.
 Signature js
Robert L Bass - 19 Apr 2009 07:12 GMT > Again, if I can get the programmer board and installer manual, I can reset > the thing back to original defaults and reprogram it myself. And really, is > having it unplugged right now worse than having it plugged in but unusable, > as it was prior to me "randomly pushing buttons"??? We've been here 6 months > and up until now, the security system was useless... TTBOMK, you can't get into programming while the system is disarmed even if you had the installer code. As someone else already pointed out, you're probably going to have to replace the main PCB and program the new one from scratch. The manuals you need to accomplish that come packed with the panel. GE doesn't make them available for download without a dealer username and password. If you want to try to get into the panel without replacing it, Jim Rojas, another of the regulars here, has an online archive of manuals for just about everything since the creation of the wheel. Jim's site is www.tech-man.com. If you decide you want to replace the board, several online stores, including mine, sell GE Security equipment direct to the public.
 Signature Regards, Robert L Bass
==============================> Bass Home Electronics DIY Alarm and Home Automation Store http://www.bassburglaralarms.com Sales & Service 941-870-2310 Fax 941-870-3252 ==============================>
Robert L Bass - 19 Apr 2009 07:14 GMT >> Again, if I can get the programmer board and installer manual, I can reset >> the thing back to original defaults and reprogram it myself. And really, is [quoted text clipped - 3 lines] > > TTBOMK, you can't get into programming while the system is disarmed... Oops! I meant to say, "while the system is armed..."
 Signature Regards, Robert L Bass
==============================> Bass Home Electronics DIY Alarm and Home Automation Store http://www.bassburglaralarms.com Sales & Service 941-870-2310 Fax 941-870-3252 ==============================>
mleuck - 27 Apr 2009 00:27 GMT > On Apr 18, 11:55 pm, Frank Olson <use-the-email- > [quoted text clipped - 23 lines] > So thanks for the condescending attitude, but can we get back to > actually answering my original question? I would say stick with networks and computers not alarm systems
Jim Rojas - 19 Apr 2009 12:48 GMT If you send me the board, I can disarm it, unlock it, and change the master code back to 1234, so you can change the code on your own. All zone programming will be saved.
Jim Rojas
> ok, so common story, we bought a house that had a GE 60-806 security > alarm system, and previous owners claim to have no idea what the codes [quoted text clipped - 23 lines] > Frustrated and locked in, > Brian brihyn - 19 Apr 2009 15:12 GMT > If you send me the board, I can disarm it, unlock it, and change the > master code back to 1234, so you can change the code on your own. All [quoted text clipped - 31 lines] > > - Show quoted text - Jim and Robert- Thanks much for the feedback. Jim- Watch your email.
JoeRaisin - 19 Apr 2009 16:39 GMT > ok, so common story, we bought a house that had a GE 60-806 security > alarm system, and previous owners claim to have no idea what the codes [quoted text clipped - 23 lines] > Frustrated and locked in, > Brian The most important thing I can think of is; are the smoke detectors in your home controlled from that panel or not?
If they are not then I refer you to panelguides.com for the relevant manuals (the site may or may not have them). Now that the system is armed I don't think you will have much luck getting into programming (that might make it a little easy for the crooks - don't you think?).
I would look at replacing the main panel control (and keypads if you go with a different make/model). That way you are starting with a fresh panel and can ensure that there aren't some other codes laying about in programming that a previous resident could use to get into your home.
Figuring out the wiring and zoning could be a PITA depending on the professionalism of the original installers. We always write the location of the device directly on the wire making such changeovers a breeze. Other companies use numbered wire labels but the legends are almost never available onsite. Still others (what may be referred to her as "trunk slammers") don't label in any way 'cause that would take a few extra minutes...
Now, if the smoke detectors ARE controlled by that panel then you need to get the system up and running (and controllable by you) as soon as possible.
Until it is fixed, do not allow your family to sleep in a house that is not protected by smoke detectors - ever. It only takes ONE night.
brihyn - 19 Apr 2009 19:27 GMT Good point. I admit, I hadn't even thought about the smoke alarms possibly being wired to the panel (old house had security only) I guess worse case scenario, I unplug the unit in the day, at night plug it in, until I get the unit fixed. And hell, even buy some cheap battery fire alarms as a temporary solution
G. Morgan - 20 Apr 2009 05:24 GMT >Good point. I admit, I hadn't even thought about the smoke alarms >possibly being wired to the panel (old house had security only) >I guess worse case scenario, I unplug the unit in the day, at night >plug it in, until I get the unit fixed. And hell, even buy some cheap >battery fire alarms as a temporary solution It's easy enough to check. Test your smoke detectors while the panel is powered down to make sure they are not operated by it.
If they are battery operated now would be a good time to change the batts. in them while you're thinking about it.
mleuck - 27 Apr 2009 00:26 GMT > ok, so common story, we bought a house that had a GE 60-806 security > alarm system, and previous owners claim to have no idea what the codes [quoted text clipped - 23 lines] > Frustrated and locked in, > Brian 2 problems here
1. There are 2 solder points on the main board however it is doubtful that will completely unlock the board especially if it is armed
2. Even if you defaulted it as you seem to know you would need a 60-746 or 60-983 alpha keypad, for that look up possible vendors in Google
|
|
|