Service Manual: 4010 Fire Alarm
Service Manual: 4010 Fire Alarm
Service Manual: 4010 Fire Alarm
Service Manual
579-081
Rev. A
• Same as UL above
Local Approvals
• CSFM
• MEA
N2 Comm Diagnostics..................................................................................C-2
Procedure ..................................................................................................C-2
IDNet Diagnostics.........................................................................................C-3
Procedure ..................................................................................................C-3
Duplicate Devices .....................................................................................C-3
Weak Answer Devices..............................................................................C-3
Network Diagnostics.....................................................................................C-5
Network Diagnostics.................................................................................C-5
Walk Test......................................................................................................C-6
Overview...................................................................................................C-6
Using Walk Test .......................................................................................C-6
Important Notes ........................................................................................C-6
TrueTest........................................................................................................C-7
Overview...................................................................................................C-7
Using TrueTest .........................................................................................C-8
vi
Overview...................................................................................................... D-2
Introduction.............................................................................................. D-2
Index
vii
Introduction This chapter contains two flowcharts, one containing the 4010’s power up
sequence and one that can be used to troubleshoot AC power problems.
• You can skip these flowcharts if your system has powered up correctly
and is displaying a trouble message on the LCD. Refer to Chapter 2 for
descriptions of the 4010’s trouble messages.
1-1
NO See
AC Power LED ON AC Power
Flowchart
YES
System Displays:
NO System Displays: NO System Displays:
Any other
Crash Code A?
"1.02.xx" Crash Code
See Note 1
YES YES
YES
Check cable running from keypad to
SFIO Board. Replace SFIO Board
System Displays:
NO System Displays: NO System Displays:
YES Refer to
Crash Codes
CFIG Format Mismatch in Chapter 3
"Warm Start Trouble" Crash Codes
(~ 10 Seconds)
YES YES
Versions of Programmer
Press ACK Key and BIN File do not match.
See Note 3 Below.
No Other Troubles or
NO NO
Do Additional Troubles
Crash Codes Present Do Crash Codes Appear?
Appear?
System Displays:
"System is Normal"
1-2
Note 1: When the system displays “1.02.xx”, this indicates the revision level of the boot software and does not
indicate the revision level of the panel’s BIN file. Refer to “Determining the BIN File Software Revision,” in
Appendix C of this manual for additional information.
Note 2: Revision 1 systems containing greater than 175 TrueAlarm isolator devices may reboot at this point. If this
occurs, upgrade the BIN file and programmer software to Rev. 2. Refer to Appendix A.
Note 3: Keep the following in mind about mismatched CFIG and BIN files:
- If a Rev. 2 job (CFIG) is downloaded to an SFIO board containing a Rev. 1 BIN file, the system reverts to a
Rev. 1 factory default job.
- If a Rev. 1 job (CFIG) is downloaded to an SFIO board containing a Rev. 2 BIN file, the system reverts to a
Rev. 2 factory default job.
Note 4: The SFIO board must be factory adjusted, tested, and loaded with the latest version of BIN file prior to
shipment. If a new SFIO board is received in the field and there is no BIN file loaded on it (i.e., a system with a
new SFIO enters a continuous link scan/code scan loop), this indicates that the board has not been factory adjusted
and tested. Order a new SFIO board, call Service Support to report the problem, and refer to Appendix B of this
manual for information on brownout potentiometer adjustment.
Note 5: The BIN file is available on the FTP site, the Technical Services Intranet site, or by ordering
Simplex Part # 741-108.
1-3
Meter AC Power
@ Panel's AC
NO
Contact Individual / Organization
Terminal Block.
Responsible for Building Electrical
System
AC Power Less
than 103 VAC?
YES
Brownout Adjustment
NO
Adjust Brownout Potentiometer.
Potentiometer Correctly
Note: Read Appendix B for
Positioned? Refer to
Adjustment Procedure.
Appendix B.
YES
Meter DC Power
NO
Check and Replace (if necessary)
@ Terminals H1 and H2
Transformer and Bridge Rectifier.
Refer to Appendix B.
DC Power 21-32 VDC?
1-4
Introduction Trouble messages are the primary means by which the system indicates that a
problem has occurred.
2-1
Check the baud rate set on the SFIO. This trouble indicates that the
baud rate may be set to some value other than 9600, which is required
for normal operation.
Set the baud rate to 9600, as shown below.
Missing Card
OFF LINE
9600
19,200
This trouble indicates that the NAC card returned a card type as
NAC something other than a NAC card type. Indicates either:
Card
Troubles Wrong Card • Another slave card (LCD Annunciator, 24 Point I/O, RS-232, DACT,
or 4120 Network) has a card address of 1.
2-2
• Check the load on the NAC in question while it is in the alarm state.
The load on each NAC must not exceed 2A. The SFIO board has
overcurrent protection for each NAC. An overloaded NAC trips this
protection and displays a NAC Signal Power Trouble for the circuit.
Unless the circuit is grossly overloaded, you should have several
seconds to measure the voltage before the protection trips. Measure
the current in either one of the following ways:
- Current Draw for a Single NAC. Use a DC ammeter, connected
in series with the load, to measure the load.
- Current Draw for all NACs. Measure the voltage across R150,
which is located above the LCD on the left-hand side of the SFIO.
Divide the measured voltage by .025. The result is the sum of all
NAC and auxiliary power loads.
• If the problem is with NAC 3 or 4, and they are powered by the 4010’s
Expansion Power Supply (EPS), check the following:
- Verify that the red shunt has been removed from connector P13
NAC 1 Signal Power on the SFIO board.
NAC NAC 2 Signal Power - Verify that the red (power) harness is connected to P1 on the
Card EPS and P13 on the SFIO board. Verify the white harness
Troubles NAC 3 Signal Power
(communication) is connected to P14 on the SFIO and P2 on the
NAC 4 Signal Power EPS.
- Remove the harness and visually inspect each female pin on
both harness connectors. Make sure that none of the pins is
pushed back into the connector. Gently tug on each wire at the
back of the connector. If a wire pulls out from the connector,
re-insert it until the pin clicks back into place. Meter each wire for
continuity.
- Verify that no circuit draws more than 2A.
+ - + -
- +
2 1
2-3
• Check the baud rate set on the SFIO. This trouble may indicate
that the baud rate is set to some value other than 9600, which is
required for normal operation.
Set the baud rate to 9600, as shown below.
OFF LINE
Power
Supply 9600
Card
19,200
Indicates that the Power Supply card returned a card type as something
other than a Power Supply Card type. Indicates either:
Wrong Card • Another slave card (LCD Annunciator, 24 Point I/O, RS-232, DACT,
or 4120 Network) has a card address of 2.
• The SFIO board is bad.
Indicates AC line voltage is too low for proper system operation. Use a
meter to verify that the AC circuit is supplying power to the panel. This
circuit’s voltage must be 120 VAC +10% / -15%.
AC Power
If the circuit supplying power to the panel has sufficient voltage, check
the adjustment of the AC Voltage Brownout Potentiometer. See
Appendix B of this document.
Indicates an Expansion Power Supply (EPS) problem. Try the
following:
Power • Verify that the AC circuit to which the power supply connects is
Supply supplying 120 VAC (+ 10% / - 15%).
Points
- If voltage is present, suspect the EPS transformer, the EPS
bridge rectifier, the connectors, or the harness running from the
Expansion Power Supply EPS to the SFIO. Refer to Appendix B for information on
troubleshooting these components of the EPS.
- If no voltage is present, check the AC circuit feeding the panel.
• Verify that the black battery wire on the EPS connects to the – Batt
terminal on the 4010. Even if you are not using battery backup for
the EPS, you must connect the black wire to the – Batt terminal.
2-4
+ - + -
- +
2 1 RED BLACK
BLACK
RED
2-5
2-6
P9
P10
R256
2-7
9600
19,200
• If, when adding a 4009 IDNet NAC extender, this trouble occurs
and then clears about every 10 to 20 seconds, you need to
upgrade the 742-147 / U25 chip on the SFIO board. The revision
IDNet of this chip required to support the 4009 is Rev 2.x.
Card
This trouble indicates a channel failure on the IDNet line. Try
replacing the 742-146 PCC chip to see if the problem clears.
1. Remove the four torx screws that secure the LCD to the SFIO
board. Carefully lift the LCD from the SFIO board.
2. Use a PLCC chip puller (553-763) to remove the PCC chip.
Carefully insert the new PCC chip in the socket and reassemble
the LCD.
Channel Failure
PCC Chip
2-8
Indicates either:
IDNet • Another slave card (LCD Annunciator, 24 Point I/O, RS-232,
Wrong Card
Card DACT, or 4120 Network) has a card address of 3.
• The SFIO board is bad.
Indicates a problem with the point associated with the Custom_Label.
Specific troubles include:
Troubles for All Devices
• No Answer. The problem is most likely with the field wiring, the
device itself, or (if connected to one) the ZAM to which the device
is connected.
- Remove the suspect device from the field wiring and connect
it directly to the IDNet channel at the panel. Use Quick CFIG
to auto-detect the device. If the panel recognizes the device,
the problem is with the field wiring. Check the field wiring for
shorts, opens, and grounds.
- If the suspect device is an IAM, check the device’s wiring. A
damaged IAM, which most commonly results from backward
wiring, does not communicate with the IDNet channel.
Replace the IAM.
- Make sure that the suspect device is not a MAPNET II ZAM,
IAM, and/or pull stations. These devices are not compatible
IDNet IDNet Device: with the 4010. Only IDNet-compatible devices can be used.
Point Custom_Label - If an isolator base is installed and programmed as a regular
base, IDNet voltage will not pass through the base.
• Wrong Device. Indicates that the device is programmed with an
incorrect hardware device type. For example, if you program a
Quick Connect Photo device with the device type of PHOTO
instead of QPHOTO, this trouble occurs. This same scenario
also causes a Bad Answer trouble.
• Duplicate Device. Two or more devices are set to the same
address. The LED on each duplicate device turns ON, allowing
you to locate the problem device(s). Readdress the device(s),
ensuring that each device has a unique address.
• Manual Disable. Indicates that the device has been manually
disabled from the front panel.
• Bad Answer. Indicates that the device is programmed with an
incorrect hardware device type. For example, if you program a
Quick Connect Photo device with the device type of PHOTO
instead of QPHOTO, this trouble occurs. This same scenario
also causes a Wrong Device trouble.
2-9
2-10
2-11
2-12
2-13
2-14
2-15
The 4009 IDNet NAC Extender Card (4009) has 40 card status points associated with it. Since an actual card does
not exist at address 17, the card status points on the 4009 “card” do not actually provide information on the card
itself. Instead, the 4009 Card Status points are used to provide information on the 4009 devices configured in the
system. The 4010 can have up to five 4009 devices programmed into the system. There are 8 card status points
associated with each possible 4009 that can be added to the system (5 devices multiplied by 8 points per device
equals 40 points). The following table describes the card status points for the 4009 card.
2-16
2-17
Introduction This chapter lists the 4010 FACP’s “crash codes.” A crash code indicates that
an unrecoverable error (a crash) has occurred to the software executing on the
4010 FACP.
The exact troubleshooting information that you can gather from a crash depends
on whether you are at the panel at the time of the crash.
The crash message appears similar to the following. Make sure to record
all information, including program counter, bank number, and task number.
CRASH # xx
• If You Are Not at the Panel When a Crash Occurs. The Crash Code and
the Task Number (see above for descriptions) are stored in a historical log
entry.
3-1
3-3
Introduction This appendix lists the 4010 FACP’s features and indicates whether a specific
hardware or software component is required to support a specific feature or set
of features.
A-1
• 4010 Phase 1 features are compatible with any mix of SFIO card, SFIO
firmware, BIN file, and programmer software (BIN and programmer
software must be same revision level).
• The Rev. C SFIO board provides improved overload protection for the U9
voltage regulator.
• QuickAlert functionality for the 4010 SFIO’s NACs requires the Rev. C
SFIO board, Version 2 SFIO firmware, and Version 2 of the BIN file and
programmer application.
• 4009 IDNet NAC Extenders require the Rev. B or Rev. C SFIO board,
Version 2 SFIO firmware, and Version 2 of the BIN file and programmer
application.
• All other 4010 Version 2 features are supported by either version of the
SFIO card and SFIO firmware, but you must have Version 2 of the BIN
file and programmer application.
Programmer Programmer
SFIO Board SFIO Board SFIO FW SFIO FW and BIN File and BIN File
Feature Rev. B Rev. C Version 1 Version 2 Version 1 Version 2
565-736 (565-736) 742-147 742-147 741-108 & 741-108 &
107 107
Phase 1
Yes Yes Yes Yes Yes Yes
Features
IDNet U9
Yes
Overload
Protection
4010 SFIO
Yes Yes Yes
QuickAlert
NACs
FM Battery
Yes Yes Yes
Charger TBL
4009 IDNet
Yes Yes Yes Yes
Interface
Other Version 2
Yes Yes Yes Yes Yes
Features
A-2
Using the Version 2.x Using the programmer to edit jobs on a panel containing older versions of the
Programmer with Version 1.x SFIO chip and board has the following effect:
Jobs
• After saving the job, the panel tags the job as a Phase II job.
• Subsequent editing of the job cannot take advantage of the full set of Phase
II features, despite the job’s Phase II designation.
A-3
Introduction This appendix provides basic troubleshooting procedures related to the 4010
FACP’s power supply.
B-1
Overview The AC Power Supply Brownout Potentiometer (R252) is factory adjusted and
should not require field adjustment. The exception to this is when an SFIO
board is received in the field without a BIN file downloaded to it. This indicates
that the board may not have been factory adjusted and tested. In this case, you
should download a BIN file to the SFIO and adjust the brownout. This allows
you to use the system until a new SFIO board can be ordered and installed.
Figure B-1 shows the proper position for this potentiometer. The slot on the
potentiometer should be positioned such that an imaginary, perpendicular line
extends from the middle of the slot to the 1:00 position. In Figure B-1, the
dashed line represents this imaginary line.
R252
+ - + -
- +
2 1
12 1
2
Screw Slot 3
Imaginary Line
Using a Variac to Adjust the The following procedure describes using a variac to adjust the brownout circuit.
Brownout Potentiometer The brownout potentiometer is R252, which is located just above the AUX
PWR terminal strip and just below the Exit/Clear button. Remove the LCD
display prior to performing this adjustment.
As adjusted above, a lightly loaded system (no alarm current – just normal
standby) will not transfer to batteries until about 80 VAC. It will return at the
same point under load or not load. When returning from brownout, the system
may take up to 30 seconds after the voltage has stabilized at 107.8 –108 VAC
before switching from batteries to AC line voltage.
B-2
Checking DC Voltage at H1 The 4010 line voltage transformer and bridge rectifier convert 120 VAC to the
and H2 DC voltage required by the 4010.
1. Meter the DC voltage across the crimped base of H1 and H2, just at the
point where the wires attach to the PC board. Refer to Figure B-2. These
terminals connect to the bridge rectifier mounted on the 4010 chassis, which
in turn connects to the line voltage transformer. DC Voltage across these
terminals should be within the range of 21-32 VDC.
• If there is no power at H1 and H2, there may be a problem with the line
voltage transformer, bridge rectifier, or one of the connectors.
P9 P10
EPS (P13
and P14)
Harness
Location of
H1 and H2
Checking Connectors A series of plastic connectors link the 4010 PC board, the line voltage
transformer, and the bridge rectifier to the building’s AC power circuit.
Checking the integrity of these connectors allows you to eliminate these
components as a possible cause for AC power problems.
2. Remove the four Torx screws that secure the panel’s electronics to the
chassis.
3. Disconnect the External Power Supply harness from connectors P13 and
P14 on the 4010 PC board.
B-3
Checking Connectors 4. Disconnect connectors P9 and P10, located on the left side of the panel’s
(continued) PC board. Label the wires to make reattachment easier. See Figure B-2.
5. Lift the panel’s electronics from the chassis, and visually inspect the four
connectors attached to the bridge rectifier. See Figure B-3. Remove each
connector one at a time and check the crimped connection between the
connector and the wire. Gently pull on the wires to make sure that they are
firmly attached to the connector.
7. Reattach all connectors and reapply AC power. If the green LED still does
not light, replace the transformer and bridge rectifier. Refer to “Replacing
the Line Voltage Transformer and Bridge Rectifier” later in this section for
information on doing this.
Bridge
Rectifier
AC Power
Bulkhead
Connector
B-4
Replacing the Line Voltage If there is no voltage at H1 and H2 and a visual inspection of the connectors
Transformer and Bridge does not reveal any obvious problems, you should replace the line voltage
Rectifier transformer and the bridge rectifier, using the following instructions.
2. Remove the four Torx screws that secure the panel’s electronics to the
chassis.
3. Disconnect the External Power Supply harness from connectors P13 and
P14 on the 4010 PC board.
4. Disconnect connectors P9 and P10, located on the left side of the panel’s
PC board. Label the wires to make reattachment easier. See Figure B-3.
5. Lift the panel’s electronics from the chassis, and disconnect the four
connectors attached to the bridge rectifier.
6. Unbolt the bridge rectifier and transformer from the 4010 chassis and
replace.
BLU
BRN
+
BRIDGE AC
RECTIFIER - AC
RED
H1
BLK
H2
ORG
P9
YEL
P10
TRANSFORMER
B-5
Introduction If the initial troubleshooting indicates that the EPS is receiving adequate 120
VAC from the AC circuit, the next step is to verify the integrity of the EPS
transformer, bridge rectifier, and their connectors.
Checking DC Voltage from 1. Meter the DC voltage across the terminals marked RED1 and BLK1 on the
EPS Bridge Rectifer EPS. Meter the terminals at the crimp, just at the point where the wires
attach to the PC board. Refer to Figure B-5. These terminals connect to the
bridge rectifier mounted on the rear of the EPS, which in turn connects to
the EPS line voltage transformer. DC Voltage across these terminals should
be within the range of 21-32 VDC.
2. If there is no power at RED1 and BLK1, there may be a problem with the
EPS line voltage transformer, bridge rectifier, or one of the connectors.
BLK1
RED1
Bridge
Rectifier
B-6
Checking Connectors A series of plastic connectors link the EPS’s line voltage transformer and bridge
rectifier to the building’s AC power circuit. Checking the integrity of these
connectors allows you to eliminate these components as a possible cause for
EPS power problems.
2. Remove the two Torx screws that secure the EPS to the chassis.
3. Disconnect the EPS harness from connectors P1 and P2 on the EPS module.
4. Disconnect and visually inspect the AC power connector on the side of the
EPS. This connector mounts to the bottom of the panel chassis, and
connects the incoming AC Power wiring to the input wiring of the EPS line
voltage transformer. Disconnect and check the connectors and wires.
Gently pull on the wires to make sure that they are firmly attached to the
connector. Refer to Figure B-6 for the location of the bulkhead connector.
5. Lift the EPS assembly from the chassis, and visually inspect the four
connectors attached to the bridge rectifier. See Figure B-5 for their
location. Remove each connector one at a time and check the crimped
connection between the connector and the wire. Gently pull on the wires to
make sure that they are firmly attached to the connector.
6. Reattach all connectors and reapply AC power. Check the voltage at RED1
and BLK1. If there still is no voltage, replace the EPS’s line voltage
transformer and bridge rectifier. Refer to “Replacing the EPS Line Voltage
Transformer and Bridge Rectifier” later in this chapter for information on
doing this.
EPS
Bulkhead
Connector
B-7
Replacing the EPS Line If there is no voltage at RED1 and BLK1 and a visual inspection of the
Voltage Transformer and connectors does not reveal any obvious problems, you should replace the line
Bridge Rectifier voltage transformer and the bridge rectifier on the EPS, using the following
instructions.
2. Remove the two Torx screws that secure the EPS assembly to the chassis.
3. Disconnect the External Power Supply harness from connectors P1 and P12
on the 4010 PC board.
4. Lift the EPS assembly from the chassis, and disconnect the four connectors
attached to the bridge rectifier.
6. Unbolt the bridge rectifier and transformer from the 4010 chassis and
replace.
- The bridge rectifier contains two terminals marked AC. Connect the
Brown and Blue wires to these terminals. It is not important which
wire goes to which AC terminal.
- Connect the RED1 wire to the terminal labeled +
- Connect the BLK1 wire to the terminal labeled -
- The orange and yellow wires are not connected and should be neatly
tucked within the enclosure.
B-8
Introduction Running the 4010’s built-in diagnostic utilities is the easiest way to ensure
proper communication between the FACP and its various devices. To use the
Diagnostics, you must be logged in at a Level 4.
C-1
Procedure Use the N2 Comms Diagnostics to check for noisy N2 comm lines and other N2
comm errors
1. Press <MENU>.
2. Press <NEXT> or <PREVIOUS> until [Diagnostics] is displayed and
then press <ENTER>.
3. Press <NEXT> or <PREVIOUS> until [N2 COMM] is displayed and
then press <ENTER>.
4. Press Press <NEXT> or <PREVIOUS> until [ON] is displayed and then
press <ENTER>.
Pressing <NEXT> or <PREVIOUS> scrolls through the available cards that are
communicating on the N2 lines and displays that card’s N2 diagnostic information.
C-2
Duplicate Devices To detect devices set to the same address you can activate the IDNet Diagnostics
- Duplicate Device option. Once activated, there is a trouble in the panel
indicating that you have activated the option. The two devices set to the same
address then come in as a duplicate device trouble for that address.
Acknowledge the trouble and view the point information to determine the
address that the devices are set to and correct the problem.
Duplicate devices are also detected during a Quick CFIG. If a duplicate device
is detected during a Quick CFIG, the Quick CFIG terminates and the following
occurs:
• If the duplicate address is a smoke detector, the panel turns ON the LEDs of
the devices.
• If the device is not a detector with an LED, program the device types and
point types of all points, download the job to the panel, and use the NO
Answer Trouble messages to determine which devices have duplicate
addresses.
Weak Answer Devices When receiving a Weak Answer Trouble you can determine which device is
causing the trouble by activating the IDNet Diagnostics - Weak Answer option.
When activated there is a trouble in the panel informing you that the option is
active. Acknowledge the trouble and wait. Any device that is weak will then
report NO ANSWER when the Weak Answer Diagnostic is run.
C-3
Procedure Use the IDNet Earth Fault Search Diagnostics to locate an “earth” between the
panel and the first IDNet isolator device or to another isolator device. Note that
the 4010 FACP does not function as a fire panel for the duration of an Earth
Fault search.
1. Press <MENU>.
2. Press <NEXT> or <PREVIOUS> until [Diagnostics] is displayed and
then press <ENTER>.
3. Press <NEXT> or <PREVIOUS> to select [IDNET EARTH FAULT
SEARCH] and then press <ENTER>.
4. Press <NEXT> or <PREVIOUS> to select [ON] and then press
<ENTER>.
If the “earth” is isolated between the first isolator and the FACP, the 4010
returns a “Earth Fault Between Panel and 1st Device” message.
If the “earth” is isolated to any other device, the 4010 returns a “Earth Fault
Isolated to Device M1-X” where X is the isolator address.
C-4
Network Diagnostics Network diagnostics allow you to check the node number of the 4010, the
network topology, and network attendance.
C-5
Overview Walk Test allows one person to test the functionality of the 4010. Once the
panel is placed into Walk Test mode, any device can be tested in any order. For
each device, you should simulate both an alarm and trouble. If an audible or
visible indication is used, wait for the indication before moving on to the next
device. Walk Test options are viewed by selecting the WalkTest entry at the
main menu. The Walk Test screens allow you to customize the Walk Test
operation. The signals (if enabled) annunciate device coding for Walk Test.
Earth Faults on both the front panel display/tone-alert and by activating audible
and visible notification circuits for 4 seconds. Suppression release outputs are
NOT activated by Walk Test.
Walk Test automatically aborts after eight hours and restores the panel to normal
operation.
1. Press <MENU>.
2. From the High-Level Status screen, press <MENU>.
3. Press <NEXT> or <PREVIOUS> until [WalkTest] is displayed and then
press <ENTER>.
4. Press < > or < > to move the focus brackets to the desired option.
5. Press <NEXT> or <PREVIOUS> to scroll through the following choices:
• On/Off Walk Test mode.
• Log/No Log allows events to be recorded to the Historical Logs.
• Signal/Silent activate/deactivate Signals.
6. Press <ENTER> to activate Walk Test.
Figure C-4 shows an example of the Walk Test screen with the default values.
Focus Brackets
<ENTER> to Accept <ARROW KEYS> to Change
[Off] Log Silent
Important Notes • Smoke detector LEDs do not activate in Walk Test when the 4010 BIN file
is at Version 1.
• Walk Test does not sound signals that are controlled via Custom Control
programming.
C-6
Overview The TrueTest feature provides a simple method of testing the application
specific software in the FACP without the need to manually activate the
initiating device circuits. In other words, TrueTest provides an easy method of
testing the Input/Output programming to verify that the programming is written
as the customer specified.
Once the panel is in TrueTest mode, you can modify a point’s status by selecting
the desired point at the front panel and pressing <NEXT> or <PREVIOUS>
until the TrueTest screen is displayed. The point’s custom label and device
address are displayed along with an option select box allowing you to select the
desired TrueTest physical state.
The choices for the TrueTest state depend on the currently selected point’s
attributes. For monitor hardware device type points, the options are NORMAL,
ABNORMAL, OPEN, and SHORT. For TrueAlarm sensors, the sensitivity
threshold possibilities available for the selected device are presented. Press
<NEXT> or <PREVIOUS> to scroll through the possible choices for that point
type.
Once you have selected the desired state, pressing <ENTER> forces the state
change as a TrueTest simulated event. Pressing <EXIT/CLR> exits the
TrueTest menu without making any changes.
When a TrueTest simulated event occurs, the system responds as if that point
had actually entered the specified state up to the point of activating control
outputs if NoCTRL is selected. If CTRL is selected, selected outputs activate.
Any control point activation, DACT reporting, printing, and logging is selected
in the TrueTest menu (refer to Table C-1 for options). Any LEDs programmed
to track any point also operate (there is no way to disable this).
• Table C-1. TrueTest Menu Options
C-7
Using TrueTest Use Steps 1 through 5 and Figures C-5 to activate TrueTest.
1. Press <MENU>.
2. Press <NEXT> or <PREVIOUS> until [TrueTest] is displayed and then
press <ENTER>.
3. Press < > or < > to move the focus brackets to the desired option.
4. Press <NEXT> or <PREVIOUS> to enable the options shown in the figure
below.
5. Once all options are set, press <ENTER> to activate TrueTest.
• On/Off
• Log/NoLog
• Print/NoPrint
• DACT/NoDACT
• NoCTRL/CTRL
Figure C-6 shows an example of the TrueTest screen with the default values.
Focus Brackets
<ENTER> to Accept <ARROW KEYS> to Change
[Off] Log Print NoDACT NoCTRL
C-8
Restoring the 4010’s Default The following procedure returns the 4010 CFIG (job) loaded on the panel to a
Programming factory default state. This includes all system options, custom labels, custom
control, etc. This procedure only works for a Rev. 2.01 or higher system.
Determining the BIN File The 4010’s software revision is actually the revision level of the BIN file
Software Revision downloaded to the panel. Use the following procedure to determine this
information:
1. Press <MENU>.
2. Press <NEXT> or <PREVIOUS> to scroll through the options until
[SOFTWARE REVISION] is displayed and then press <ENTER>.
3. Press <ENTER>. Information similar to the following appears. The
number following Sys Rev. is the revision level of the panel’s BIN file.
Disabling the Piezo on a Disable the piezo on a 4606-9101 Remote LCD Annunciator by turning ON
Remote LCD Annunciator digital pseudo point P48 (LCD Annunciator Sounder Disable). To do this from
the front panel, follow these steps.
1. Press <MENU>.
2. Press <NEXT> or <PREVIOUS> until [Control/View Points] is displayed
and then press <ENTER>.
3. Press <NEXT> or <PREVIOUS> to scroll through the point types until the
[Digital Pseudo Points] appears and press <ENTER>.
4. Press <NEXT> or <PREVIOUS> to scroll through the points until [P48]
appears and press <ENTER>.
5. Press <NEXT> or <PREVIOUS> to toggle the state of the point.
Clearing an Event Overflow Anytime the panel receives in excess of 127 events per second, the event queue
Trouble overflows and the panel indicates this by generating an Event Queue Overflow
Trouble. This trouble can be cleared in one of two ways:
C-9
Clearing an Event Overflow Follow these steps to turn off P47 from the front panel.
Trouble (continued)
1. Press <MENU>.
2. Press <NEXT> or <PREVIOUS> until [Control/View Points] is displayed
and then press <ENTER>.
3. Press <NEXT> or <PREVIOUS> to scroll through the point types until the
[Digital Pseudo Points] appears and press <ENTER>.
4. Press <NEXT> or <PREVIOUS> to scroll through the points until P48
appears and press <ENTER>.
5. Press <NEXT> or <PREVIOUS> to toggle the state of the point.
C-10
Supervisory Point Type and The supervisory point type, when used with system outputs such relays, does not
Output Devices work in Revision 1 of the 4010. (Assigning a Supervisory point type to an
output should automatically turn the output ON when a Supervisory event
occurs.)
• Replace Version 1.x software with Version 2.x BIN file and programmer
software. Version 2.x of the 4010 resolves this problem. Refer to
Appendix A for compatibility guidelines.
• If you must use Version 1.x software, use custom control to program the
operation of the output. Monitor the state of analog pseudo point A2, which
is the analog pseudo that counts supervisory conditions in the system.
Input
ON state of A2
Output
Track ON Relay
In this case, the relay turns off when the supervisory condition clears.
Incorrect Operation of IDNet The 4010 does not properly control IDNet devices at addresses 124 and 24.
Device 124 and 24 This includes TrueAlarm device LEDs, relays, sounder bases, and relay IAMs.
Incoming status (i.e., Alarm and Trouble) report properly, but the device output
does not activate.
Replace Version 1.x software with Version 2.x BIN file and programmer
software. Version 2.x of the 4010 resolves this problem. Refer to Appendix A
for compatibility guidelines.
Remote LED Connected to a Remote LEDs connected to a duct sensor do not illuminate when the duct sensor
Duct Sensor goes into alarm. This is a Version 1.x problem that has been fixed by Version
2.x.
SDACT Conversion Errors When used in conjunction with the 4010, the SDACT programmer must be at
Revision 1.04 or higher.
Problems Downloading to the If you are unable to download to the SDACT, move the SDACT’s switch to the
SDACT OFF position and then back to the ON position while the programmer is
attempting to download the file.
C-11
24-Point I/O Incorrect Relay / In cases where the relay or LED connected to a 24 point I/O output does not
LED Operation pick or light, check the field wiring to make sure voltage is wired to TB2.
System Reset Problems -- A 4010, containing a Revision 1.x BIN file, does not reset when the following
IDNet Class A Trouble conditions are true:
This problem has been corrected by Version 2.x of the 4010 software.
System Reset Problems -- The 4010 reset duration -- the amount of time required by the 4010 to perform a
Lengthening Reset Timer for reset -- is self-adjusting based on the number of IDNet devices attached to the
Networked Systems system. If the 4010 has a large number of devices (approximately 200), the
4010’s reset duration may exceed the reset timer of a networked panel, causing
reset problems.
If this occurs, lengthen the reset timer on every networked panel that
annunciates 4010 alarms.
IN:
THE ON STATE OF
A34 TIMER “SYSTEM STARTUP PULSE TIMER
OUT:
SET TO VALUE 40 (SECS) THE ANALOGS
A15 ANALOG “SYSTEM RESET WINDOW TIMER SETPOINT”
END:
Custom Control Problems – Points with a valid device type of IPHOTO or RPHOTO may receive an
Invalid Opcode for IPHOTO or “Invalid Device Type for this Opcode” message, when used within a Custom
RPHOTO Control output statement.
If this occurs, either include the points in a list and add them to the output
statement, or upgrade the programmer to Rev. 2.
C-12
Introduction This appendix provides basic troubleshooting procedures related to fiber optic
transmitters and receivers.
D-1
Introduction Figure D-1 shows the locations of the connectors and LEDs for the 4009 IDNet
Fiber Optic cards, which can be used to link the 4010 to a remote 4009 IDNet
NAC extender.
IDNet INTERFACE
TB1
FIBER TRANSMIT
LED1 FIBER TRANSMIT
(SEE NOTE 1) LED2
(SEE NOTE 1)
FIBER OPTIC
TRANSMITTER
U19
FIBER OPTIC
IDNet TERMINAL BLOCK RECEIVER
TB2 U20
FIBER OPTIC
TRANSMITTER
POWER TERMINAL BLOCK
U21
TB2
(SEE NOTE 2)
FIBER OPTIC
RECEIVER
U22
CLASS A FIBER TRANSMIT (SEE NOTE 2)
LED3
(SEE NOTE 1) FIBER TRANSMITTER CARD
Notes:
1. LEDs 1-3 indicate the following conditions:
• Green LED1 flashes when data is being transmitted out fiber.
• Red LED2 flashes when data is being received from fiber.
• Red LED3 flashes when data is being received on the Class A fiber receiver.
2. Shown equipped with optional Class A Receiver/Transmitter Card components.
D-2
Indicates a problem with the Class A connection between U17 on the fiber optic
receiver card and U22 on the fiber optic transmitter card. Check the following:
LED 1 LED 2 LED 3
• Check the U17 and U22 connectors. Make sure that they are securely
RX attached to the receiver or transmitter card. A problem with either of these
connectors causes this LED pattern.
TX
• Check the integrity of the fiber connection running between U17 and U22.
A break or defect in the fiber running between these connectors causes this
LED pattern.
Indicates a problem with the Class A connection between U18 on the fiber optic
receiver card and U19 on the fiber optic transmitter card. Check the following:
LED 1 LED 2 LED 3 • Check the U18 and U19 connectors. Make sure that they are securely
RX attached to the receiver or transmitter card. A problem with either of these
connectors causes this LED pattern.
TX
• Check the integrity of the fiber connection running between U18 and U19.
A break or defect in the fiber running between these connectors causes this
LED pattern.
Indicates a problem with the Class A connection between U19 on the fiber optic
receiver card and U21 on the fiber optic transmitter card. Check the following:
LED 1 LED 2 LED 3 • Check the U19 (the one on the fiber optic receiver card) and U21
RX connectors. Make sure that they are securely attached to the receiver or
transmitter card. A problem with either of these connectors causes this
LED pattern.
TX
• Check the integrity of the fiber connection running between U19 and U21.
A break or defect in the fiber running between these connectors causes this
LED pattern.
Indicates a problem with the Class A connection between U16 on the fiber optic
receiver card and U20 on the fiber optic transmitter card. Check the following:
LED 1 LED 2 LED 3 • Check the U16 and U20 connectors. Make sure that they are securely
RX attached to the receiver or transmitter card. A problem with either of these
connectors causes this LED pattern.
TX
• Check the integrity of the fiber connection running between U16 and U20.
A break or defect in the fiber running between these connectors causes this
LED pattern.
D-3
Indicates a problem with connectors U16 and U18 on the fiber optic receiver
card. Check the following:
LED 1 LED 2 LED 3
RX • Check to see if U16 and U18 are crossed. U16 must connect to U20 on the
fiber optic transmitter card, and U18 must connect to U19 on the transmitter
card.
TX
• This LED pattern also occurs if both U16 and U18 on the receiver card are
unconnected.
Indicates a problem with connectors U19 and U18 on the fiber optic receiver
card. Check the following:
LED1 LED2 LED3
• Check to see if U19 and U18 are crossed. U19 on the receiver card must
RX
connect to U21 on the fiber optic transmitter card, and U18 must connect to
U19 on the transmitter card.
TX
• This LED pattern also occurs if both U19 and U18 on the receiver card are
unconnected.
Indicates a problem with connectors U17 and U18 on the fiber optic receiver
card. Check the following:
LED1 LED2 LED3
• Check to see if U17 and U18 are crossed. U17 on the receiver card must
RX
connect to U22 on the fiber optic transmitter card, and U18 must connect to
U19 on the transmitter card.
TX
• This LED pattern also occurs if both U17 and U18 on the receiver card are
unconnected.
D-4
Introduction The following table identifies the two possible LED displays for a Class B fiber
optic circuit.
LED3, which is the Class A Fiber LED does not have significance for a Class B
circuit.
LED1 LED2
RX Indicates a problem (damage, break, bad connectors) with the fiber running
between connectors U16 on the receiver and U20 on the transmitter card.
TX
D-5
Misc. D
24 point I/O card troubles DB version mismatch trouble
missing card trouble, 2-14 for SDACT card, 2-12
specific point troubles, 2-14 diagnostics
4009 IDNet NAC Extender network diagnostics, C-5
and intermittent IDNet missing card trouble, 2-8 digital pseudo point troubles, 2-17
4009 IDNet NAC Extender troubles, 2-16 duct sensor
4010 programmer problems with remote LED, C-11
features for different revisions, A-2 duplicate device trouble, 2-9
A E
AC power flowchart, 1-4 Earth ground troubles
AC power supply and dual RS-232 card, 2-5
checking, B-3 and power supply card, 2-5
replacing transformer/bridge rectifier, B-5 intermittent, 2-5
AC power trouble EPS battery trouble, 2-5
for power supply card, 2-4 EPS transformer
checking, B-6
replacing, B-8
B EPS trouble
bad answer trouble, 2-9 for power supply card, 2-4
basic service procedures, C-9 event queue overflow trouble, C-9
battery charger trouble
for power supply card, 2-7 F
battery depleted disconnected trouble
for power supply card, 2-6 fiber optic media card
battery low cutout trouble class A LED displays, D-3
for power supply card, 2-6 class B LED displays, D-5
battery low trouble overview of components, D-2
for power supply card, 2-6
battery terminals
and EPS trouble, 2-4
I
checking, 2-7 IAM
baud rate and no answer trouble, 2-9
and missing card trouble for IDNet card, 2-8 IDNet device # 124 or # 24, C-11
and missing card trouble for NAC, 2-2 IDNet diagnostics, C-3
and missing card trouble for power supply, 2-4 IDNet Earth fault search diagnostics, C-4
BIN file IDNet troubles
availability of, 1-3 and 4009 IDNet NAC Extender, 2-8
corrupt, damaged, or missing, 1-2 and isolator bases, 2-8
determining software revision, C-9 and monitor IAMs, 2-10
features for different revisions, A-2 and pull stations, 2-10
new SFIO has none, B-2 and RIAMs, 2-10
bridge rectifier and TrueAlarm devices, 2-10
checking, B-3, B-6 and ZAMs, 2-10
replacing, B-5, B-8 bad answer, 2-9
brownout, 1-4 channel failure trouble, 2-8
adjusting, B-2 Class A status trouble, 2-10
duplicate device, 2-9
C extra device trouble, 2-10
ground fault status trouble, 2-10
central station trouble missing card trouble, 2-8
for SDACT card, 2-12 no answer, 2-9
CFIG format mismatch, 1-2, 1-3 power supply status trouble, 2-10
class A trouble short status trouble, 2-10
for a NAC, 2-2 wrong card troubles, 2-9
code scan/link scan loop, 1-2, 1-3 wrong device, 2-9
crash codes, 3-2
IN-1
O T
output devices trouble messages
problems with supervisory point type, C-11 NAC troubles, 2-2
TrueAlarm isolator devices, 1-3
IN-2
W Z
Walk Test, C-6 ZAM
and Custom Control, C-6 and no answer trouble, 2-9
and head missing trouble, C-6
smoke detector LEDs don't light, C-6
IN-3