- Home
- Home security & automation
- Security access control systems
- Schneider Electric
- FX 3NET
- Datasheet
advertisement
Installation Instruction 66571764GB3 Fire Detection
26
MAINTENANCE 67: (r)
MAINTENANCE 68: (r)
MAINTENANCE 69: (r)
FAULT 70: (r)
FAULT 71: (r)
FAULT 72: (r)
FAULT 73: (r)
FAULT 74: (r)
FAULT 75: (r)
FAULT 76: (r)
FAULT 77: (r)
FAULT 78: (r)
FAULT 79: (r)
FAULT 80: (r)
FAULT 81: (r)
FAULT 82: (r)
FAULT 83: (r)
FAULT 84: (r)
FAULT 85: (r,s)
FAULT 86: (r)
FAULT 87: (?) show it as fault warning.
− Saturation of infrared detector at CoPTIR/PTIR sensor
− 80% of drift limit (when “report dirty detector” requested)
− 99% of drift limit (when “report dirty detector” requested)
− Undefined fault code from ALC/SySeAp device.
− Memory write operation of the device failed
− Memory read operation of the device failed
− Communication troubles with device.
− Self test of the detector failed.
− Beam sensor CPU fault
− Beam sensor align targeting
− Beam sensor general fault
− Beam sensor signal too high
− cell life expiration of CoPTIR sensor
− The SW of ALC board is not compatible for desired sounder mode
− Input module has been configured as "fire router fault". When module alarms FX show it as fault warning.
− Input module has been configured as "VACIE fault". When module alarms FX show it as fault warning.
− Unsupported address device has been configured to the loop of LC board
(The SW of LC is older than configuration made with WinFXNet).
− Power failure of supervised output circuit of a module
− The OEM code of the device is not Esmi/Pelco code.
− The control of output of SySeAp device did not work
MAINT 88: (?)
MAINT 89: (?)
FAULT 90: (r,s)
− Unacceptable device
ALC: detector is not Intellia, device is XP95 but not configured
MAINTENANCE 91: (r)
FAULT 92: (r)
FAULT 93: (r)
FAULT 94: (r)
FAULT 95: (r)
FAULT 96: (?)
MAINTENANCE 98: (r)
FAULT 99: (r)
− break in input line of the CLC unit
− short circuit in input line of the CLC unit
− voltage problem in input line of the CLC unit
− Voice evacuation mute input active time expired
−
− simulated maintenance (service command)
− simulated fault (service command)
s = start up phase when scanning devices (after panel (re)start or when is loop connected by user)
r = running time when device is normally monitored
c = loop is configured with PC
n = loop is not configured
Note !
Fault delays / timeouts
Reason for Fault 52 ( no PW1 received) must be active for 99sec. before the fault is shown.
Delay for fault 63 (PW4 out of limits) is 30 sec. if any good pulses are received, counter will stop, and if no bad pulses with in 10sec, the counter is reset
Schneider Electric Pelco Finland Oy Kalkkipellontie 6, 02650 Espoo, Finland Telephone: +358 10 446 511 Fax: +358 10 446 5103 www.pelco.com/nordic
Document Number 66571764GB3 16 2012
Installation Instruction 66571764GB3
12. Conventional detector lines
12.1 Measuring the Cables
1. Disconnect all power from the control panel.
2. Measure the resistance between the wires of the conventional line cable. Set the meter to low voltage resistance measurement
(not diode measurement).
Depending on connected devices the result should be:
- If all devices are normally open (NO) types and no EOL resistor is connected the meter should indicate a break in the line
- If all devices are normally open (NO) types and an EOL resistor is connected the meter should indicate the value of the EOL resistor.
- If some devices are normally closed (NC) types the meter should indicate the parallel connection of the series resistances of those devices
If the resistance meter indicates other values, the cause of the fault must be located. (It may be a detector connected the wrong way or a short circuit in the conductors).
3. Short-circuit the wires of the conventional detection line cable at the control panel during measuring.
4. Disconnect the end-of-line resistors from those conventional detection line terminals to which the cables are to be connected.
5. Take the end-of-line resistor with you and walk to the end of the line and measure the resistance between the wires of the cable.
The maximum allowed resistance is 100
Ω (50 Ω if the line goes through an Exi barrier). If the resistance is higher, there is a break in the line (did you remember short-circuit the cable wires at the control panel). Locate the breaks and eliminate them.
6. Connect the end-of-line resistors to their respective places (the last detector or manual call point of the line or the end-of-line unit box connected after the last device).
Fire Detection
27
Schneider Electric Pelco Finland Oy Kalkkipellontie 6, 02650 Espoo, Finland Telephone: +358 10 446 511 Fax: +358 10 446 5103 www.pelco.com/nordic
Document Number 66571764GB3 16 2012
advertisement
Related manuals
advertisement
Table of contents
- 1 FX 3NET FIRE ALARM SYSTEM
- 1 Installation and commissioning manual
- 1 Read this manual carefully before installation and commissioning!
- 2 Contents
- 4 NOTE: If SLC loop controller is configured to LC protocol, please read document.O1771GB0
- 4 FX cabinet
- 5 FXL cabinet
- 5 FXM cabinet
- 5 FXS cabinet
- 6 AX/FX/IX-BAT battery cabinet
- 6 FXM-BAT battery cabinet
- 7 FX-CAB mounting cabinet
- 7 FXM-CAB mounting cabinet
- 8 FXM-RMFW mounting frame
- 9 FX-RMFW mounting frame
- 15 8. Preliminary checks
- 15 MC2 jumper settings
- 16 SLC jumper settings
- 16 CLC jumper settings
- 16 ALC jumper settings
- 16 IOC jumper settings
- 17 OCA jumper settings
- 17 Note! The panel is in access level 2 when the cover is removed.
- 23 Each FX-SLC and FX–ALCB board has connectors for two loops, FX-ALCA board has only one loop.
- 26 Note !
- 26 Fault delays / timeouts
- 28 12.2.1 Conventional line
- 28 Conventional line 4k7
- 28 Conventional line 2k94
- 29 12.2.2 Input line
- 29 End of line resistance: 4k7, 5%
- 30 Each CLC board has 16 conventional lines (detection circuits).
- 31 Conventional Line
- 31 Input Line
- 33 The FX-MC board has one monitored output line connector.
- 33 The FX-IOC board has four monitored output line connectors.
- 37 X = 0; Info configured to RS232 service port
- 37 Picture 1. Connection between FX-panel and FMPX
- 38 Picture 2. Connection between FX-panel and DAPX
- 38 Picture 3. Connection between FX-panel and REPX
- 38 Note! If REPX-OB is installed in FX: rack, only INFO line needs to be connected.
- 39 Picture 4. Connection between FX-panel and MCOX
- 39 Note! If MCOX-OB is installed in FX: rack, only INFO line needs to be connected
- 42 System 1(S1) and System 2 (S2) = serial communication line
- 42 Picture 5. Example: FX 3NET communication network
- 42 Picture 6. Communication grounding in the FX NET system
- 43 Picture 7. Max. two modem pairs between two panels