1. Loop Fault
A loop fault indicates a break in the wiring or a failure in the RET on the board to detect the signal. It may also result from a short circuit on the line.
Solution:
Disconnect the RET cable and identify where devices start to disappear; the break is likely at that point.
If the fault occurs after an alarm, the loop's signal/voltage may have dropped due to excessive current consumption.
Reduce current draw by lowering loop-powered sounder levels or consider dividing the loop.
Use the loop calculator during system design to prevent this issue.
Note: Low loop voltage can also cause missing devices or unresponsive commands.
2. Expansion Board Missing
This fault occurs when the expansion board is unresponsive, missing, incorrectly set, or damaged.
Solution:
Ensure jumper J12 is placed on the correct side; improper placement may keep the board in firmware update mode.
Connect expansion boards only when the system is powered off to prevent damage.
3. 700-NET Card Missing/Not Responding
This indicates the 700-NET card is not powered, disconnected, or faulty.
Solution:
Verify the board is powered (typically via AUX – GND pins) and that its flat cable is properly connected.
Refer to the Toccare installation manual for correct installation procedures.
4. Onekbd Missing/Not Responding
Possible causes include:
Missing power supply.
Dipswitch on the board set incorrectly (must be positioned towards the RS485 pins).
Absence of common ground if powered externally.
Solution: Ensure proper power supply and correct dipswitch settings.
5. Power Missing
This fault suggests an issue with the main power supply unit (PSU), such as a blackout, blown fuse, or PSU in protection mode (possibly due to a short circuit).
Solution: Inspect and rectify the PSU as needed.
6. Batteries Missing
The system does not detect the batteries.
Solution: Check battery connections to ensure they are properly installed.
7. Batteries Faulty
This fault may be due to damaged batteries.
Solution:
Disconnect the power supply and allow the system to run for over 15 minutes.
After this period, measure the voltage of each battery.
Healthy batteries should have similar voltages; a significant difference indicates a faulty battery requiring replacement.
Note: The panel checks battery status approximately every 15 minutes by measuring internal resistance.
8. Device Missing
A device does not respond to the panel.
Possible Causes:
Device disconnected.
Device not addressed.
Incorrect protocol used on the panel.
Solution: Verify connections, addressing, and protocol settings.
9. Device Conflict
Two or more devices share the same address.
Solution: Identify and resolve address conflicts; affected devices will have illuminated LEDs for easy identification.
10. Device Mismatch
A device is programmed incorrectly (e.g., an optical/thermal detector programmed as optical only).
Solution: Adjust settings or, if possible, erase and auto-program the device again.
11. Device Fault
A device is malfunctioning.
Possible Causes:
For detectors or call points: device damage.
For modules: missing end-of-line resistance or lack of external power for monitored outputs.
Solution: Inspect and replace faulty devices as necessary.
12. Apollo Device Parameters
When designing a system with Apollo devices, it's crucial to know which devices will be used. Mixing XP95 and Soteria devices on the same loop can cause address conflicts due to differing address bit requirements.
Addressing Details:
XP95/Discovery devices use a maximum of 126 addresses (7 bits).
Soteria devices use a maximum of 254 addresses (8 bits).
Conflict Example:
An XP95 device at address 1 and a Soteria device at address 129 would conflict because the XP95 device can only interpret 7 bits, leading to misinterpretation of addresses.
Solution: Ensure that for every 10 XP95 addresses used, the corresponding 8-bit addresses (e.g., 129, 130) are left unassigned to avoid conflicts.
13. Detector High Drift/Dirty
An optical detector may signal a fault if it is too dirty.
Solution: Clean the detector or replace it if necessary.
14. 700-NET Line Cut
This fault results from a break in the 700-NET connections between boards or misplaced wires.
Solution: Check and correct the 700-NET connections as per the installation manual.
15. Noise Problems
External signals can interfere with the loop, causing issues like mismatches, conflicts, missing devices, high drift, or false alarms.
Solution:
Use shielded cables with the shield connected to ground to protect against electromagnetic interference.
Ensure the shield is continuous, insulated
Contact Information
For further assistance or if you have any questions regarding this procedure, please contact the Eurotech Technical Team:
Email: technical@eurotechfire.com
Phone: +44 (0) 203 141 0982