Perbaikan Fire Alarm

TN51482e<0>
Trouble Shooting Manual
HEAD OFFICE
7-3, Kudan-Minami 4-chome, Chiyoda-ku,
Tokyo 102-8277, Japan
INTERNATIONAL DIVISION
Phone: (81) 3-3265-0231 Fax: (81) 3-3265-5348
URL http://www.nohmi.co.jp
Integlex Multicrest S508 Trouble Shooting Manual-Rev.0
To Users
This manual is intended to clear trouble easily at your side. If you have any trouble that
cannot be cleared at your side, please contact us.
Document History
Integlex Multicrest S508 Trouble Shooting Manual (Document no. TN51482e)
Revision Status Revision Date Reason For Change
<0> 2012.01.16 Initial Release
<1>
<2>
<3>
Page 2 of 23
Contents
To Users .........................................................................................................................................2
Document History ...........................................................................................................................2
1. System Trouble ................................................................................................................. 5

1.1. AC Power Fault ....................................................................................................................5
1.2. Battery Fault .........................................................................................................................5
1.3. Pos GND Fault .....................................................................................................................5
1.4. Neg GND Fault .....................................................................................................................5
1.5. SLC2 Board TBL ..................................................................................................................6
1.6. SLC3 Board TBL ..................................................................................................................6
1.7. SLC4 Board TBL ..................................................................................................................6
1.8. Annunc #nn TBL ...................................................................................................................6
1.9. SLC1 Open ..........................................................................................................................7
1.10. SLC2 Open ........................................................................................................................7
1.11. SLC3 Open .........................................................................................................................7
1.12. SLC4 Open ........................................................................................................................7
1.13. SLC1 Short .........................................................................................................................7
1.14. SLC2 Short .........................................................................................................................8
1.15. SLC3 Short .........................................................................................................................8
1.16. SLC4 Short .........................................................................................................................8
1.17. SLC1+ GND Fault ..............................................................................................................8
1.18. SLC1- GND Fault ...............................................................................................................8
1.19. SLC2+ GND Fault ..............................................................................................................9
1.20. SLC2- GND Fault ...............................................................................................................9
1.21. SLC3+ GND Fault ..............................................................................................................9
1.22. SLC3- GND Fault ...............................................................................................................9
1.23. SLC4+ GND Fault ..............................................................................................................9
1.24. SLC4- GND Fault .............................................................................................................10
1.25. Fire Drill ............................................................................................................................10
1.26. Signal Silence ..................................................................................................................10
1.27. Config Data DL .................................................................................................................10
1.28. Config Data UL .................................................................................................................10
1.29. Program Data DL ............................................................................................................. 11
1.30. Evnt Log Data UL ............................................................................................................. 11
1.31. Mainten Data UL .............................................................................................................. 11
1.32. NAC Bypass ..................................................................................................................... 11
1.33. Suppres Bypass ............................................................................................................... 11
1.34. Other Bypass ...................................................................................................................12
1.35. Printer Bypass ..................................................................................................................12
1.36. SLC1 Bypass ...................................................................................................................12
1.37. SLC2 Bypass ...................................................................................................................12
1.38. SLC3 Bypass ...................................................................................................................12
1.39. SLC4 Bypass ...................................................................................................................13
1.40. ZONE #nnn Bypass..........................................................................................................13
1.41. Line1 TBL .........................................................................................................................13
1.42. Line2 TBL .........................................................................................................................13
Page 3 of 23
1.43. DACT TBL ........................................................................................................................13

1.44. ACCT1 MaxAttempt..........................................................................................................14
1.45. ACCT2 MaxAttempt..........................................................................................................14
1.46. ACCT1 Trouble .................................................................................................................14
1.47. ACCT2 Trouble .................................................................................................................14
1.48. Line 1 Call Fail .................................................................................................................15
1.49. Line 2 Call Fail .................................................................................................................15
1.50. ACCT1 PHN 1 Fail ...........................................................................................................15
1.51. ACCT1 PHN 2 Fail ...........................................................................................................15
1.52. ACCT2 PHN 1 Fail ...........................................................................................................16
1.53. ACCT2 PHN 2 Fail ...........................................................................................................16
2. Device Trouble ................................................................................................................ 17

2.1. Missing Device ...................................................................................................................17
2.2. Multiple Address .................................................................................................................17
2.3. Device Mismatch ................................................................................................................17
2.4. Device Fault .......................................................................................................................17
2.5. Device Dirty ........................................................................................................................18
2.6. Fire alarm control panel ......................................................................................................19
2.7. Addressable modules .........................................................................................................20
2.8. Annunciators ......................................................................................................................23
2.9. PCCP .................................................................................................................................23
Page 4 of 23
1. System Trouble
1.1. AC Power Fault

AC◦Power◦Fault [Trouble details]
The AC power is off, and the system is being operated by batteries.
ALM000◦SUP000◦TBL001
[Countermeasure]
Check and supply the AC power.
1.2. Battery Fault

Battery◦Fault [Trouble details]
No battery has been connected, or the connected batteries have
some trouble.
[Countermeasure]
If no battery has been connected, connect batteries.
If batteries have been connected, check the polarity.
If no trouble is found in the battery connection, check the FE fuse of main board.
If no cause can be found after checking above items, replace batteries.
1.3. Pos GND Fault

Pos◦GND◦Fault [Trouble details]
A positive ground fault has been detected.
[Countermeasure]
Check + terminal line of NAC circuit, Auxiliary Power circuit and annunciator circuit. And then, fix the
ground fault.
1.4. Neg GND Fault

Neg◦GND◦Fault [Trouble details]
A negative ground fault has been detected.
[Countermeasure]
Check - terminal line of NAC circuit, Auxiliary Power circuit and annunciator circuit. And then, fix the
ground fault.
Page 5 of 23
1.5. SLC2 Board TBL

SLC2◦Board◦Trouble [Trouble details]
The ALE whose rotary switch has been set to 2 does not respond.
[Countermeasure]
Check the connection of cable between main board and ALE (i.e. power cable and communication
cable).
If no cause is found in the cable connection, check if the ALE rotary switch has been set to 2. If it has
not been 2, turn off the FACP power, set the rotary switch to 2, and turn on the FACP power.
1.6. SLC3 Board TBL

[Countermeasure]
cable).
1.7. SLC4 Board TBL

cable).
1.8. Annunc #nn TBL

Annunc◦#nn◦TBL [Trouble details]
The remote annunciator nn (i.e. one of 01 to 31) has some trouble or
cannot establish communication.
[Countermeasure]
Check if the annunciator is connected to the FACP correctly.
If no cause is found in the connection to FACP, check if the baud rate has been set as same as the rate
set in FACP. (i.e. check the setting of baud rate at the annunciator.)
If the trouble cannot be cleared after checking above items, replace the printed circuit assembly of the
annunciator.
Page 6 of 23
1.9. SLC1 Open

SLC1◦Open [Trouble details]
An open circuit has been detected in the wiring of main board’s SLC
(i.e. SLC1).
[Countermeasure]
Fix the open circuit, and operate [System Reset] at FACP.
1.10. SLC2 Open

An open circuit has been detected in the wiring of ALE No.2’s SLC
(i.e. SLC2).
[Countermeasure]
1.11. SLC3 Open

(i.e. SLC3).
[Countermeasure]
1.12. SLC4 Open

(i.e. SLC4).
[Countermeasure]
1.13. SLC1 Short

SLC1◦Short [Trouble details]
A short circuit has been detected in the wiring of main board’s SLC
(i.e. SLC1).
[Countermeasure]
Fix the short circuit. (It may take about 30 seconds maximum for recovery from the short circuit
condition.)
Page 7 of 23
1.14. SLC2 Short

A short circuit has been detected in the wiring of ALE No.2’s SLC (i.e.
SLC2)
[Countermeasure]
condition.)
1.15. SLC3 Short

SLC3)
[Countermeasure]
condition.)
1.16. SLC4 Short

SLC4)
[Countermeasure]
condition.)
1.17. SLC1+ GND Fault

SLC1+◦GND◦Fault [Trouble details]
[Countermeasure]
Check + terminal line of SLC1. And then, fix the ground fault.
1.18. SLC1- GND Fault

SLC1-◦GND◦Fault [Trouble details]
[Countermeasure]
Check - terminal line of SLC1. And then, fix the ground fault.
Page 8 of 23

[Countermeasure]

[Countermeasure]

[Countermeasure]

[Countermeasure]

[Countermeasure]
Page 9 of 23

[Countermeasure]
1.25. Fire Drill

Fire◦Drill [Trouble details]
The FACP has been under the Fire Drill On condition.
[Countermeasure]
Operate the System Reset switch to make the system reset.
1.26. Signal Silence

Signal◦Silence [Trouble details]
The FACP has been under the Signal Silence On condition.
[Countermeasure]
Operate the Signal Silence switch to make the Silence Off condition.
Operate the Drill switch to make the Drill On condition.
Operate the System Reset switch to make the system reset..
1.27. Config Data DL

Config◦Data◦DL [Trouble details]
The configuration data download is on-going.
[Countermeasure]
This trouble is cleared when the configuration data download is completed.
Operating the System Reset switch cancels the download. (i.e. The download is aborted.)
1.28. Config Data UL

Config◦Data◦UL [Trouble details]
The configuration data upload is on-going.
[Countermeasure]
This trouble is cleared when the configuration data upload is completed.
Operating the System Reset switch cancels the upload. (i.e. The upload is aborted.)
Page 10 of 23
1.29. Program Data DL

Program◦Data◦DL [Trouble details]
The operating program data download is on-going.
[Countermeasure]
This trouble is cleared when the operating program data download is completed.
Operating the System Reset switch cancels the download. (i.e. The download is aborted.)
1.30. Evnt Log Data UL

Evnt◦Log◦Data◦DL [Trouble details]
The event log data upload is on-going.
[Countermeasure]
This trouble is cleared when the event log data upload is completed.
1.31. Mainten Data UL

Mainten◦Data◦UL [Trouble details]
The maintenance list data upload is on-going.
[Countermeasure]
This trouble is cleared when the maintenance list data upload is completed.
1.32. NAC Bypass

NAC◦Bypass [Trouble details]
NAC device has been bypassed.
[Countermeasure]
The NAC device can be enabled by operating the [Bypass] menu.
1.33. Suppres Bypass

Suppres◦Bypass [Trouble details]
Suppression device has been bypassed.
[Countermeasure]
The suppression device can be enabled by operating the [Bypass] menu.
Page 11 of 23
1.34. Other Bypass

Other◦Bypass [Trouble details]
Other device has been bypassed.
[Countermeasure]
The other device can be enabled by operating the [Bypass] menu.
1.35. Printer Bypass

Printer◦Bypass [Trouble details]
If printer is connected, printer has been bypassed.
[Countermeasure]
The printer can be enabled by operating the [Bypass] menu.
1.36. SLC1 Bypass

SLC1◦Bypass [Trouble details]
SLC1 has been bypassed.
[Countermeasure]
The SLC1 can be enabled by operating the [Bypass] menu.
1.37. SLC2 Bypass

[Countermeasure]
1.38. SLC3 Bypass

[Countermeasure]
Page 12 of 23
1.39. SLC4 Bypass

[Countermeasure]
1.40. ZONE #nnn Bypass

ZONE◦#nnn◦Bypass [Trouble details]
ZONE #nnn has been bypassed.
[Countermeasure]
The Zone #nnn can be enabled by operating the [Bypass] menu.
1.41. Line1 TBL

Line1◦TBL [Trouble details]
An open circuit or a short circuit has been detected in the wiring of
DACT Line 1.
[Countermeasure]
Check the telephone line 1 connection to the DACT circuit.
1.42. Line2 TBL

Line2◦TBL [Trouble details]
An open circuit or a short circuit has been detected in the wiring of
DACT Line 2.
[Countermeasure]
1.43. DACT TBL

DACT◦TBL [Trouble details]
The internal DACT circuit of main board has some trouble.
[Countermeasure]
Replace the main board.
Page 13 of 23
1.44. ACCT1 MaxAttempt

ACCT1◦MaxAttempt [Trouble details]
Account 1 has reached it’s maximum number of attempts to complete
a successful call. The trouble may be due to incorrect account
configuration data.
[Countermeasure]
Check both telephone numbers of “Account 1” in the configuration data.
If the telephone numbers are correct, there may be a problem at the DACR side. So, contact the DACR
side.
The “Manual Test Call” function may be used as an attempt to test or clear this trouble.
1.45. ACCT2 MaxAttempt

ACCT2◦MaxAttempt [Trouble details]
Account 2 has reached it’s maximum number of attempts to complete
a successful call. The trouble may be due to incorrect account
configuration data.
[Countermeasure]
Check both telephone numbers of “Account 2” in the configuration data.
side.
1.46. ACCT1 Trouble

ACCT1◦Trouble [Trouble details]
An “Account 1 Trouble” signal has been detected. This is the generic
trouble set for Account 1 after reaching the maximum number of
attempts to complete a successful call.
[Countermeasure]
Check the telephone numbers of “Account 1” in the configuration data.
side.
1.47. ACCT2 Trouble

ACCT2◦Trouble [Trouble details]
An “Account 2 Trouble” signal has been detected. This is the generic
trouble set for Account 2 after reaching the maximum number of
attempts to complete a successful call.
[Countermeasure]
Check the telephone numbers of “Account 2” in the configuration data.
side.
Page 14 of 23
1.48. Line 1 Call Fail

Line◦1◦Call◦Fail [Trouble details]
The DACT has failed to complete a call using Line 1. The DACT was
unable to successfully dial out and detect a dial tone.
[Countermeasure]
1.49. Line 2 Call Fail

Line◦2◦Call◦Fail [Trouble details]
The DACT has failed to complete a call using Line 2. The DACT was
unable to successfully dial out and detect a dial tone.
[Countermeasure]
1.50. ACCT1 PHN 1 Fail

ACCT1◦PHN◦1◦Fail [Trouble details]
The DACT has failed to complete a call using the primary phone
number of account 1.
[Countermeasure]
Check the primary telephone number of “Account 1” in the configuration data.
If the telephone number is correct, there may be a problem at the DACR side. So, contact the DACR
side.

The DACT has failed to complete a call using the secondary phone
[Countermeasure]
Check the secondary telephone number of “Account 1” in the configuration data.
side.
Page 15 of 23

The DACT has failed to complete a call using the primary phone
[Countermeasure]
Check the primary telephone number of “Account 2” in the configuration data.
side.

The DACT has failed to complete a call using the secondary phone
[Countermeasure]
Check the secondary telephone number of “Account 2” in the configuration data.
side.
Page 16 of 23
2. Device Trouble
2.1. Missing Device

Missing◦Device Missing◦Device [Trouble details]
User◦Custom◦Message Jan/01/2011◦09:00AM An addressable device does not
[INFO] respond. (i.e. An addressable device
User◦Custom◦Message -> Analog◦Smk◦Det◦◦1001 programmed in the configuration data
ALM000◦SUP000◦TBL001 ALM000◦SUP000◦TBL001 cannot be found.)
[Countermeasure]
Connect the addressable device. If the addressable device has been connected already, check the wiring of
signal line (i.e. there may be short or open circuit.)
2.2. Multiple Address

Multiple◦Device Multiple◦Device [Trouble details]
User◦Custom◦Message Jan/01/2011◦09:00AM There may be multiple addressable
[INFO]
User◦Custom◦Message -> Analog◦Smk◦Det◦◦1001 devices that have a same address
number.
ALM000◦SUP000◦TBL001 ALM000◦SUP000◦TBL001
[Countermeasure]
Check and change the address numbers of addressable devices.
2.3. Device Mismatch

Device◦Mismatch Device◦Mismatch [Trouble details]
User◦Custom◦Message Jan/01/2011◦09:00AM The address number has not been
[INFO] programmed in the configuration data.
User◦Custom◦Message -> Analog◦Smk◦Det◦◦1001 Otherwise, the classification of the
ALM000◦SUP000◦TBL001 ALM000◦SUP000◦TBL001 addressable devices is different from
the one in the configuration data.
[Countermeasure]
If the address number has been programmed in the configuration data, check the classification of the connected
device with the classification of the address in configuration data.
If the address number has not been programmed in the configuration data, modify the configuration data.
Otherwise, if the address number should not be used, the address number set to the addressable device is wrong.
2.4. Device Fault

Device◦Fault Device◦Fault [Trouble details]
User◦Custom◦Message Jan/01/2011◦09:00AM An open circuit (or a short circuit if it
[INFO]
User◦Custom◦Message -> Alarm◦Zone◦◦◦◦◦◦1001 is the FRRU004-MOM4) has been
detected in the wiring of connected
ALM000◦SUP000◦TBL001 ALM000◦SUP000◦TBL001 device.
[Countermeasure]
Check the wiring between the addressable module and the connected device. If it is the addressable module for
initiating device, the system reset is required after fixing the wiring.
Page 17 of 23
2.5. Device Dirty

Device◦Dirty Device◦Dirty [Trouble details]
User◦Custom◦Message [INFO] Jan/01/2011◦09:00AM Dirty level from analog smoke
User◦Custom◦Message -> Analog◦Smk◦Det◦◦1001 detector is higher than dirty
ALM000◦SUP000◦TBL001 ALM000◦SUP000◦TBL001 threshold.
[Countermeasure]
Please set alarm threshold level more higher.
Please replace analog smoke detector.
Page 18 of 23
Fast Answer Question

2.6. Fire alarm control panel
Trouble All trouble signals have been acknowledged, therefore, the audible device for the
trouble signals have been deactivated.
The audible device was activated suddenly, but there was no new trouble signal.
Cause & If the trouble signals have not been cleared, the audible device is activated when 24
Counter- hours passed since the audible device is deactivated.
measure
Trouble The fuse FE of main board was replaced, but was blown soon.
Cause & The fuse FE is blown when the polarity of battery is wrong. Check the polarity of
Counter- battery.
measure
Trouble The FACP is not operated. (i.e. The FACP powered on.)
Cause & Check if the correct AC power (i.e. 120V or 240VAC) has been supplied to TB1 of
Counter- PSM.
measure Check if the CNT1, CNT2 of the main board has been connected to the transformaer
correctly.
Check if CNDC of the main board have been connected to TB1 of the PS board.
Trouble The trouble [SLCn Short] cannot be cleared. (n: 1 to 4)
Cause & Check the short circuit in the wiring of signal line (i.e. S+ and S-).
Counter- Check if an end-of-line device has been connected to the signal line incorrectly.
measure
Trouble No signal is received from the terminal for printer when any event occurs.
Cause & Check if the dip-switch of the main board have been set correctly.
Counter- DSW 1: ON for printer enable, OFF for disable
measure Checking the wiring between main board and the connected device, especially the
wiring between the terminal TxD of main board’s TB1 and the receiving terminal of
connected device, and the terminal RxD of main board’s TB1 and the transmission
terminal of connected device. (TxD: Transmission, RxD: Receipt）
*Note: If the connected device has Dsub 25-pin or Dsub 9-pin, the wiring shall be as
follows;
Page 19 of 23
2.7. Addressable modules

Trouble Occurrence and recovery of multiple address are made repeatedly.
Cause & There may be multiple addressable devices that are set for the same address number.
Counter- Check if there is(are) any device(s) that does not respond (i.e. No Answer On). If there
measure is(are), check if the device(s) is(are) connected to the signal line correctly. If the
connection is OK, check the address number (and it should not be same as that of any
addressable device).
Trouble The LED of connected detector does not blink.
Cause & Check if it is a conventional smoke detector connected to the signal line (i.e. S+ and
Counter- S-) directly. Any conventional detector cannot be connected to the signal line directly.
measure Check if it is an analog detector connected to an addressable module for conventional
detector. Any analog detector cannot be connected to the addressable module for
conventional detector.
When it is a conventional detector connected to an addressable module for
conventional detector, check if the power has been supplied to the terminals 24+ and
24- of the addressable module. Also, check the polarity and the voltage. (If the cause
is the power supply trouble, it can be identified as a “Device Fault” on main board.)
When it is an analog detector, check if the LED blinking has been disabled in the
configuration data.
Trouble A conventional detector is activated, and so the LED of the conventional detector was
turned on as intended. However, the fire alarm signal was not received by the FACP.
Cause & Check if a “Missing Device” or a “Device Mismatch” for the addressable module to
Counter- which the conventional detector is connected has been received. If so, the FACP has
measure not identified the addressable module. Clear the “Missing Device” or the “Device
Mismatch” according to the section 2.1 or 2.3.
Check if the addressable module has been bypassed. Any signal received from the
bypassed addressable device is not displayed on main board.
Trouble The trouble signal “Device Fault” from an addressable module for conventional detector
of wiring to the connected device cannot be cleared.
Cause & Check if an end-of-line resistor (5.1 K) has been connected to the initiating device
Counter- circuit correctly.
measure
Trouble The trouble signal “Fault On” from an addressable monitored output module of wiring to
the connected device cannot be cleared.
Cause & Check if an end-of-line resistor (5.1 K) has been connected to the wiring of the
Counter- connected device correctly.
measure Check if there is a short circuit in the wiring of the connected device.
Trouble The trouble signal “Fault On” from an addressable monitored output module of wiring to
the connected device cannot be received by the FACP.
Cause & Check if the address number of the addressable module has been bypassed. If it has
Counter- been bypassed, remove the bypass and check if the trouble signal can be received.
measure Check if the jumper (JP1) of the addressable module has been selected DC. If the
jumper (JP1) has been selected AC, the detection functionality for the power supply
wiring (i.e. 24+ and 24-) of the addressable module has been disabled.
Page 20 of 23
Trouble Wiring of signal line (i.e. S+ and S-) was made in NFPA style 4, and some short circuit
isolators were used. However, the addressable devices connected after a SCI does not
respond.
Cause & Check if a LED of the SCI is turned on for notifying the short circuit status. If so, check
Counter- the wiring, and fix the short circuit.
measure Check the polarity of wiring for the SCI in both before and after the SCI.
Check if there is an end-of-line resistor connected after the SCI. If there is, remove it,
as it is not required.
When any LED of the SCI has not been on, check if any voltage (i.e. around 24V) is
given to the wiring after the SCI. If there is, check if the wiring of 24VDC power has
been mixed with the wiring of signal line for the SCI.
When any LED of the SCI has not been on, check if any voltage (i.e. around 24V) is
given to the wiring after the SCI. If there is, check if the wiring of the signal line for the
SCI has been mixed with the wiring of another signal line (i.e. another loop).
Check if there are more than 50 addressable devices connected after the SCI. The
maximum quantity of addressable device connectable after a SCI (including the case
of “between a SCI and another SCI) is 50.
Trouble Wiring of signal line (i.e. S+ and S-) was made in NFPA style 7. However, the
addressable devices connected between a SCI and another SCI do not respond. Also,
the FACP received a trouble signal “SLCn Open” from the loop concerned.
Cause & Check the polarity of wiring for both SCIs.

Counter- Check if there is a short circuit in wiring between the SCIs.
measure Check if branch wiring was made in the wiring between the SCIs.
Check if the wiring between the SCIs has been mixed with the wiring of 24VDC power
supply
Check if the wiring between the SCIs has been mixed the wiring of another signal line
(i.e. another loop).
Trouble All addressable devices connected to the loop(s) do not respond (i.e. Missing Device).
Cause & Check if the wiring of 24VDC power supply has been mixed with the wiring of signal
Counter- line.
measure If the “Missing Device” addressable devices are connected to multiple loops, check if
the wiring of signal line has been mixed with the wiring of another signal line.
Trouble A fire alarm signal is received from an addressable module for conventional detector,
but any conventional detector connected to the addressable module has not been
activated. The fire alarm signal is received again right after clearing the status by the
operation of System Reset switch.
Cause & Check if wiring for initiating device circuit of the addressable module has a short circuit.
Counter- Check if an end-of-line resistor has been connected to the initiating device circuit
measure instead of an end-of-line device.
Trouble An input signal was given to an addressable module input type (e.g. A switch connected
to the addressable module was activated), but no signal is displayed on the FACP.
Cause & The signal is not displayed on the FACP if it has been configured for “Monitor Point” in
Counter- the configuration data.
measure Check if the addressable module has been bypassed. Otherwise, check if the
addressable module is under ”Missing Device” condition.
Page 21 of 23
Trouble During Walk Test, a detector was activated to check the activation of output devices in
the same zone. However, the output type addressable module(s) was(were) not
activated.
Cause & The output type addressable module is not activated while any of “NAC Bypass”, “SPR
Counter- Bypass” , “Other Bypass” , “Zone Bypass” , “SLCn Bypass” is conducted. It is required
measure to end the “Bypass” if the module should be activated.
The addressable module is not activated if it has been under “Bypass”, “Missing
Device”.
Any output is activated in the case of Silent Walk Test.
Trouble Walk Test and Alarm Simulation are ended forcibly.
Cause & Walk Test and Alarm Simulation are ended when any of Pre-Alarm, Verify Alarm, and
Counter- Alarm occurs in the addresses out of the test range.
measure
Page 22 of 23
2.8. Annunciators
Trouble Only [Transmission Trouble] is displayed on the LCD of a LCD-type remote annunciator.
(FIRU006-LCD)
Cause & Check the connection between the FACP and the FIRU006-LCD.
Counter- Check the baud rate set in the FIRU006-LCD is same as the one programmed in the
measure configuration data of the FACP. Note that they should be same.
Trouble When multiple annunciators are connected, “Remote Annunciator #nn Trouble” signals
from some annunciators are received and cleared repeatedly.
Cause & Check if the jumpers for end-of-line resistor in multiple annunciators are set to ON.
Counter- Note that the jumper of only the farthest annunciator shall be set to ON, and others
measure shall be set to OFF.
Check if an annunciator number is duplicated by multiple annunciators.
Check if the feed wiring has been made in the connection between the annunciators
and the FACP.
2.9. PCCP
Trouble The Configuration data download/upload cannot be implemented due to Log-On failure.
Cause & This trouble occurs when the FACP declined the Log-On.
Counter- Check if the FACP is having any pre-alarm or alarm signal. If so, all kinds of operation
measure from PCCP are declined. In this case, the pre-alarm or alarm signal should be cleared
and acknowledged.
Trouble The configuration data download/upload was started, and so the download/upload
dialog came up on the PCCP. However, the progress bar was not moved, and
download/upload was failed at last.
Cause & This trouble occurs when the communication between the FACP and the PCCP has not
Counter- been established.
measure Check if the serial port of the PC being used for the PCCP is same as the one set in
the PCCP.
Page 23 of 23

Perbaikan Fire Alarm

Încărcat de

Informații document

Descriere originală:

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Perbaikan Fire Alarm

Încărcat de

Drepturi de autor:

Formate disponibile

TN51482e<0>

Trouble Shooting Manual

1. System Trouble ................................................................................................................. 5

1.43. DACT TBL ........................................................................................................................13

2. Device Trouble ................................................................................................................ 17

1.1. AC Power Fault

1.2. Battery Fault

1.3. Pos GND Fault

1.4. Neg GND Fault

1.5. SLC2 Board TBL

1.6. SLC3 Board TBL

1.7. SLC4 Board TBL

1.8. Annunc #nn TBL

1.9. SLC1 Open

1.10. SLC2 Open

1.11. SLC3 Open

1.12. SLC4 Open

1.13. SLC1 Short

1.14. SLC2 Short

1.15. SLC3 Short

1.16. SLC4 Short

1.17. SLC1+ GND Fault

1.18. SLC1- GND Fault

1.19. SLC2+ GND Fault

1.20. SLC2- GND Fault

1.21. SLC3+ GND Fault

1.22. SLC3- GND Fault

1.23. SLC4+ GND Fault

1.24. SLC4- GND Fault

1.25. Fire Drill

1.26. Signal Silence

1.27. Config Data DL

1.28. Config Data UL

1.29. Program Data DL

1.30. Evnt Log Data UL

1.31. Mainten Data UL

1.32. NAC Bypass

1.33. Suppres Bypass

1.34. Other Bypass

1.35. Printer Bypass

1.36. SLC1 Bypass

1.37. SLC2 Bypass

1.38. SLC3 Bypass

1.39. SLC4 Bypass

1.40. ZONE #nnn Bypass

1.41. Line1 TBL

1.42. Line2 TBL

1.43. DACT TBL

1.44. ACCT1 MaxAttempt

1.45. ACCT2 MaxAttempt

1.46. ACCT1 Trouble

1.47. ACCT2 Trouble

1.48. Line 1 Call Fail

1.49. Line 2 Call Fail

1.50. ACCT1 PHN 1 Fail

1.51. ACCT1 PHN 2 Fail

1.52. ACCT2 PHN 1 Fail

1.53. ACCT2 PHN 2 Fail

2.1. Missing Device

2.2. Multiple Address

2.3. Device Mismatch

2.4. Device Fault

2.5. Device Dirty