Electronic Alarms and Home Security Devices - FA120C Programming Woes
Doityourself.com community forum was created to provide answers to all questions related to home improvement and home repair. Doityourself community can help you find information about how-to topics on small fixes to large remodeling projects. With comprehensive how-to content and expertly moderated community forums DoItYourself.com makes it easy to tackle even the most complex home improvement projects.View Full Version : FA120C Programming Woes
CybrPNK
02-15-07, 06:05 PM
I just moved into a new house with a FA120C panel with a FA250KP keypad. In the panel was a copy of the FA120C programming form, conveniently filled out by the installer. However, when programming the fields don't seem to match up. For example on the form, *31 - *37 are for the zone response types and all for a single digit entry. When programming *31 - *34 all are single digit, but from there on it seems to be expecting a multiple digit entry. Also, the values I fill in for these fields don't seem to get the expected response from the system.
Is it possible that there is a different form for programming the FA120C?
Is it possible that there is a different form for programming the FA120C?
MrRonFL
02-16-07, 04:15 PM
The value will display with 2 digits (if you press #31, for example, it will read back 0 X), but if you truely have a FA-120 all you should have to enter is the location number and the setting.
To change zone 5 to an entry/exit zone, you would enter *35 1.
Take a look at the PC board. If it's a FA-120 there should be a part number with 4110 in it somewhere.
To change zone 5 to an entry/exit zone, you would enter *35 1.
Take a look at the PC board. If it's a FA-120 there should be a part number with 4110 in it somewhere.
CybrPNK
02-25-07, 01:58 PM
Hmmm, it definately says FA-120 on the PC board. Really what my problem is that I want the chime to sound when any of the doors are opened, currently the chimes only sounds when the motion sensor is activated - really annoying.
MrRonFL
02-25-07, 02:39 PM
It sounds like either your zones are programmed with the wrong zone type, or the motion detector is mixed in with a perimeter type zone.
Go through the zone programming using # [location number] and record what each zone is programmed as. Then you can compare that to what openings/devices are actually on each zone.
If you don't have an accurate zone list, you may have to have someone go through the place and open each door and window, one by one, while you make a list of what openings correspond to which zone. (this is why service calls can get expensive, there's not really a _fast_ way to do this).
Go through the zone programming using # [location number] and record what each zone is programmed as. Then you can compare that to what openings/devices are actually on each zone.
If you don't have an accurate zone list, you may have to have someone go through the place and open each door and window, one by one, while you make a list of what openings correspond to which zone. (this is why service calls can get expensive, there's not really a _fast_ way to do this).