Friedland Zone Settings Not Working? Alarm System Fixes
Properly configured zones are the foundation of an effective Friedland security system. They allow you to customise how your alarm behaves, such as allowing movement in downstairs areas at night while keeping the upstairs fully armed. When these zone settings are not working as expected, it can lead to false alarms, security vulnerabilities, or the inability to arm your system correctly.
This guide is designed to help you troubleshoot common problems with Friedland alarm zone settings in a professional and easy-to-understand manner, empowering you to ensure your property is properly protected.
### Understanding Alarm Zones
First, let's clarify what a 'zone' is. A zone is a specific area of your property monitored by one or more sensors. For example:
- Zone 1: Downstairs Doors (front door, back door contacts)
- Zone 2: Living Room (PIR motion sensor)
- Zone 3: Upstairs Landing (PIR motion sensor)
Programming these zones correctly allows you to part-arm your system (e.g., arming only the downstairs zones at night).
Common Zone Setting Problems and Solutions
Let's address the most frequent issues users experience with their Friedland alarm zones.
### Problem: A Zone is Not Being Detected or Triggering the Alarm
You've opened a window or walked past a sensor in an armed zone, but nothing happens.
- Check Sensor Power: For wireless systems, the most common cause is a dead battery in the sensor (the door contact or PIR). Replace the battery with a new one of the exact same type.
- Sensor/Magnet Alignment: For door and window contacts, check the alignment between the sensor and the magnet. They need to be very close (typically within 1-2 cm) to register as 'closed'. If they have been knocked out of alignment, the zone will always show as open.
- Incorrect Zone Programming: The sensor may have been accidentally programmed to a different zone number or a different zone type (e.g., programmed as a 24-hour tamper zone instead of a standard intruder zone). This requires checking the settings in the system's programming menu, which may require the installer or engineer code.
### Problem: False Alarms from a Specific Zone
Your alarm is being triggered, and the panel indicates the same zone every time.
- Environmental Triggers: For PIR motion sensors, look for non-human sources of movement or rapid temperature changes. This includes:
- Pets moving within the sensor's range.
- Curtains or plants moving due to draughts from vents or open windows.
- Direct sunlight hitting the sensor.
- Spiders or other insects crawling directly across the sensor lens.
- Faulty Sensor: If you have ruled out all environmental causes, the sensor itself may be developing a fault, causing it to trigger intermittently. It may need to be replaced.
### Problem: Cannot Arm or Set a Specific Zone
When you try to arm the system, the panel indicates a fault or prevents you from setting a particular zone.
- Open Sensor: The most likely cause is that a sensor in that zone is 'open'. Physically walk around and check every door and window in that zone to ensure they are securely closed. Check the alignment of the contacts as mentioned earlier.
- Zone Type Mismatch: You might be trying to perform an action that conflicts with the zone's programming. For example, if you have programmed a zone as an 'entry/exit' route, you may not be able to instantly arm it without an exit delay. Review your zone type settings in the user manual to ensure they match your intentions.
### Making Changes to Zone Settings
To add, remove, or change the behaviour of a zone, you will typically need to enter the 'Engineer' or 'Installer' menu. This requires a specific code that is different from your day-to-day user code. If you do not have this code, you may need to contact a professional installer. When making changes, always follow the instructions in your Friedland user manual carefully, as incorrect programming can make your system inoperable. Always test the system thoroughly after making any changes to ensure all zones are working as expected.