Manual de Servicios Simplex 4010
Manual de Servicios Simplex 4010
Copyright Simplex Time Recorder Co., 1999. All rights reserved. Printed in the United States of America. Information in this document is subject to change without notice. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written consent of Simplex Time Recorder Company. Walk Test is protected by US Patent No. 4,725,818. MAPNET addressable communications is protected by US Patent No.4,796,025. IDNet is patent pending. TrueAlarm Analog Detection is protected by US Patent No. 5,155,468. TrueAlarm Detector Base is protected by US Patent No. 5,173, 683.
SYSTEM REACCEPTANCE TEST AFTER SOFTWARE CHANGES - To ensure proper system operation, this product must be tested in accordance with NFPA72-1996, Chapter 7 after any programming operation or change in sitespecific software. Reacceptance testing is required after any change, addition or deletion of system components, or after any modification, repair or adjustment to system hardware or wiring. All components, circuits, system operations, or software functions known to be affected by a change must be 100% tested. In addition, to ensure that other operations are not inadvertently affected, at least 10% of initiating devices that are not directly affected by the change, up to a maximum of 50 devices, must also be tested and proper system operation verified. READ AND SAVE THESE INSTRUCTIONS. Follow the instructions in the installation, operating and programming manuals. These instructions must be followed to avoid damage to the control panel and associated equipment. Fire Alarm Control Panel (FACP) operation and reliability depend upon proper installation. DO NOT INSTALL ANY SIMPLEX PRODUCT THAT APPEARS DAMAGED. Upon unpacking your Simplex product, inspect the contents of the carton for shipping damage. If damage is apparent, immediately file a claim with the carrier and notify Simplex. ELECTRICAL HAZARD - Disconnect electrical power when making any internal adjustments or repairs. Servicing should be performed by qualified Simplex Representatives. RADIO FREQUENCY ENERGY - This equipment generates, uses, and can radiate radio frequency energy and if not installed and used in accordance with the instruction manual, may cause interference to radio communications. It has been tested and found to comply with the limits for a Class A computing device pursuant to Subpart J of Part 15 of FCC Rules, which are designed to provide reasonable protection against such interference when operated in a commercial environment. Operation of this equipment in a residential area may cause interference in which case the user at his own expense will be required to take whatever measures may be required to correct the interference.
The 4010 is listed for the following. UL 864 Listings for Type of System: UL 864 Power-Limited Fire Alarm Control Unit Local (formerly NFPA 72A) Requires the sounding of an alarm via listed notification appliance(s) Auxiliary (formerly NFPA 72B) Requires 4010-9809 City Circuit Module Remote Station - protected premise (formerly NFPA 72C) Requires 4010-9809 City Circuit Module or the 4010-9810 or -9816 DACT Proprietary - protected premise (formerly NFPA 72D) Requires 4010-9817 (with 4010-9818 or 4010-9819) or 4010-9821 Network Interface Modules Central Station - protected premise (formerly NFPA 71) Requires 4010-9810 or -9816 DACT Suppression Releasing Service Requires 4010-9814 Suppression Kit
UL 864 Listings for Type of Service: Automatic, Manual, Waterflow, and Sprinkler Supervisory
UL 864 Listings for Type of Signaling: Coded, Non-Coded, March-Time and DACT DACT requires the 4010-9810 or -9816
The installer should be familiar with the relevant codes listed below as well as any other applicable local codes and standards, when installing a fire alarm system. NFPA 72 NFPA 11 NFPA 11A NFPA 12 NFPA 12A NFPA 13 NFPA 14 NFPA 15 NFPA 16 NFPA 16A NFPA 17 NFPA 17A NFPA 25 NFPA 70 NFPA 80 NFPA 90A NFPA 90B NFPA 92A NFPA 92B NFPA 101 NFPA 170 NFPA 231C NFPA 1221 National Fire Alarm Code Standard for Low-Expansion Foam and Combined Agent Systems Standard for Medium- and High-Expansion Foam Systems Standard on Carbon Dioxide Extinguishing Systems Standard on Halon 1301 Fire Extinguishing Systems Standard for the Installation of Sprinkler Systems Standard for the Installation of Standpipe and Hose Systems Standard for Water Spray Fixed Systems for Fire Protection Standard for the Installation of Deluge Foam-Water Sprinkler and Foam-Water Spray Systems Standard for the Installation of Closed-Head Foam-Water Sprinkler Systems Standard for Dry Chemical Extinguishing Systems Standard for Wet Chemical Extinguishing Systems Standard for Inspection, Testing, and Maintenance of Water-Based Fire Protection Systems National Electrical Code Standard for Fire Doors and Fire Windows Standard for the Installation of Air Conditioning and Ventilation Systems Standard for the Installation of Warm Air Heating and Air Conditioning Systems Recommended Practice for Smoke-Control Systems Guide for Smoke Management Systems in Malls, Atria, and Large Areas Life Safety Code Standard for Fire Safety Symbols Standard for Rack Storage of Materials Standard on the Installation, Maintenance, and Use of Public Fire Service Communication Systems
Table of Contents
vi
Known Solutions.........................................................................................C-11 Supervisory Point Type and Output Devices ..........................................C-11 Incorrect Operation of IDNet Device 124 and 24 ...................................C-11 Remote LED Connected to a Duct Sensor ..............................................C-11 SDACT Conversion Errors .....................................................................C-11 Problems Downloading to the SDACT...................................................C-11 24-Point I/O Incorrect Relay / LED Operation .......................................C-12 System Reset Problems -- IDNet Class A Trouble .................................C-12 System Reset Problems -- Lengthening Reset Timer for Networked Systems ...................................................................................................C-12 Custom Control Problems Invalid Opcode for IPHOTO or RPHOTO...C-12
Index
vii
Introduction
This chapter contains two flowcharts, one containing the 4010s power up sequence and one that can be used to troubleshoot AC power problems. Be aware of the following when using these flowcharts. The power up sequence occurs quickly. On a properly functioning system, some phases of the power up sequence (for example, the span of time during which the boot software revision is displayed) appear on the Liquid Crystal Display (LCD) for only a few seconds. It may be necessary to run the power up sequence several times, as you read the flow chart, to properly interpret what is happening. 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 4010s trouble messages.
In this Chapter
This chapter discusses the following topics: Topic Initial Power Up Flowchart AC Power Flowchart See Page # 1-2 1-4
1-1
AC Power LED ON
NO
YES
NO
NO
See Note 1
YES
YES
Check cable running from keypad to SFIO Board.
YES
Replace SFIO Board
NO
YES
Bin File Corrupt, Damaged, or Missing Replace BIN File or Replace SFIO. See Note 4.
See Note 2
YES
NO
NO
YES
YES
Press ACK Key
YES
Versions of Programmer and BIN File do not match. See Note 3 Below.
NO
NO
Do Crash Codes Appear?
YES
YES
Refer to Trouble Descriptions in Chapter 2
YES
Refer to Crash Codes in Chapter 3
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 panels 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
AC Power Flowchart
Meter AC Power @ Panel's AC Terminal Block. AC Power Less than 103 VAC?
NO
Contact Individual / Organization Responsible for Building Electrical System
YES
NO
Adjust Brownout Potentiometer. Note: Read Appendix B for Adjustment Procedure.
YES
NO
Check and Replace (if necessary) Transformer and Bridge Rectifier. Refer to Appendix B.
1-4
2-1
NAC Troubles
Table 2-1. NAC Card and Point Troubles Type Trouble Message Possible Causes / Troubleshooting Remove the field wiring from the NAC. Connect a 10K EOL resistor to the NAC terminal on the panel and see if the trouble clears. Do one of the following depending on whether the trouble clears. If the trouble does not clear, replace the SFIO board. If the trouble clears, there is a short or open somewhere on the field wiring running between the NAC terminals on the SFIO and the notification appliances.
NAC Circuit: SIG1 NAC Circuit: SIG2 NAC Circuit: SIG3 NAC Circuit: SIG4
NAC Card Relay 1 status and configuration. NAC Card Relay 2 status and configuration. 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.
Black indicates switch position
Missing Card
OFF LINE 9600 19,200
This trouble indicates that the NAC card returned a card type as something other than a NAC 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 1. The SFIO board is bad.
Check the following: Verify that a Class A adapter card is actually installed. This error occurs if the NACs device type is Class A and the adapter card is not installed. Power down the panel, remove the Class A card and reseat it in the header on the NAC. Check to see that the pins of the Class A card are properly seated in the header on the NAC card and power on the panel. If the trouble does not clear, power down the panel again and swap another Class A card in place of the suspect card. If the problem still occurs, replace the SFIO board. Check the field wiring for opens and shorts. Continued on next page
2-2
If the problem is with NAC 3 or 4, and they are powered by the 4010s Expansion Power Supply (EPS), check the following:
NAC 1 Signal Power NAC Card Troubles NAC 2 Signal Power NAC 3 Signal Power NAC 4 Signal Power
Verify that the red shunt has been removed from connector P13 on the SFIO board. Verify that the red (power) harness is connected to P1 on the EPS and P13 on the SFIO board. Verify the white harness (communication) is connected to P14 on the SFIO and P2 on the 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.
+
+ 1
P1 (Red Harness)
P2 (White Harness)
2-3
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.
AC Power
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 circuits voltage must be 120 VAC +10% / -15%. 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:
Verify that the AC circuit to which the power supply connects is supplying 120 VAC (+ 10% / - 15%). If voltage is present, suspect the EPS transformer, the EPS bridge rectifier, the connectors, or the harness running from the 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
If the fault is intermittent, use the Earth Fault Latch, located in the Function menu, to silence the fault until the intermittent problem can be isolated and fixed. Note: After fixing the problem, you will need to perform a system reset to clear the Earth Fault Latch. If a negative ground is isolated to the dual RS-232 card and one port of this card attaches to a DC-powered printer and the other port connects to an AC-powered CRT, upgrade 565-810 to Revision A1 or greater. You can also remove jumpers P17 and P18 from this card, if ground detection is not required. Check the connection of the wires running from the battery to the expansion power supply, as shown in the illustration below.
+
+ 1
RED
BLACK
BLACK RED
2-5
Indicates the battery has a voltage less than 19.5 V. Do the following: Power Supply Points Battery Depleted/Disconnected
This trouble only occurs if the Depleted Battery system option is enabled. Indicates the battery has reached a depleted state, and the system will function in one of two ways: Battery Low Cutout Shut the system down. This is the ULC-required operation for Canada. Depleted Battery system option requires a special wiring harness to function in this way. When an alarm occurs, the system does not energize the panels NAC circuits. This functionality occurs when the Depleted Battery option is enabled, but the special harness is not used. Continued on next page
2-6
P9 P10
No Voltage at P9 / P10. Check the voltage across P9 and P10, as shown above. If no voltage is present, check the AC circuit supplying power to the 4010. If the circuit has power, the problem is probably with the AC power supply line voltage transformer. Refer to Checking the AC Power Supply Transformer / Bridge Rectifier in Appendix B for information on checking and replacing the line voltage transformer.
Voltage at Batt + and Batt - Terminals Less than 27.6 VDC. 1. Disconnect Battery. 2. Adjust Potentiometer R256. Turn the potentiometer a small amount at a time and then recheck the voltage. Adjust the potentiometer until the voltage across these terminals is 27.6 VDC. 3. Reconnect the batteries. At this point, you should expect that the voltage across these terminals is not 27.6, as the batteries may be charging. Do not readjust R256 if this is the case.
R256
2-7
IDNet Troubles
Table 2-3. IDNet Troubles Type Trouble Message Possible Causes / Troubleshooting This trouble indicates that the IDNet card is not communicating with the master.
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.
Black indicates switch position
Missing Card
IDNet Card
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 of this chip required to support the 4009 is Rev 2.x.
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.
Important Note: If your installation uses isolator bases, this trouble can occur in conjunction with IDNet device troubles. If this is the case, ignore this trouble until all other troubles are cleared. If it is still present, suspect the PCC chip or the SFIO board. Continued on next page
2-8
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 devices 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 with the 4010. Only IDNet-compatible devices can be used. 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. Continued on next page
2-9
This trouble indicates that there is a device answering that is not included in the configuration. Extra devices can be caused by: Installation of more devices than required for the installation. Device not programmed.
Open the trouble log to identify the address(es) of the extra devices. If this trouble occurs in conjunction with a No Answer Trouble, the problem is most likely a misaddressed device. Fix the address and warmstart the panel to clear the trouble. This trouble indicates a Class A trouble condition on the IDNet line. Check the following: Class A Status Power Supply Status Ground Fault Status Short Status Is there an open on the IDNet wire? Is the circuit wired for Class B, not Class A, but there is no jumper installed. The installation includes isolator bases and there is an output abnormal trouble on the isolator point.
This point indicates a power supply trouble on the IDNet card. Replace the SFIO board. This trouble indicates that there is a ground fault in the IDNet line. Check the field wiring. This trouble point indicates a short condition on the IDNet card. Check the field wiring.
2-10
Indicates that the RS-232 / Modem card returned a card type as something other than a RS-232 / Modem card. Wrong Card Ensure that no other N2 cards (LCD Annunciator, 24 Point I/O, RS-232, DACT, or 4120 Network) have a card address of 4. If the RS-232 / Modem card is addressed as Card 4, replace the SFIO card. Is the power to the attached device turned off? If so, turn it on and see if the trouble clears. Is the correct cable being used to attach the device to the serial port? Is the device connected? If the port is supervised, and you disconnect the device after using it, this trouble occurs. If the device is a printer, is it out of paper?
2-11
SDACT Troubles
Table 2-5. SDACT Troubles Trouble Message Possible Causes / Troubleshooting Indicates that the SDACT card is not communicating with the master. Missing Card Check the position of switch SW2 on the SDACT card. This switch must be in the normal position. Ensure that no other N2 cards (LCD Annunciator, 24 Point I/O, RS-232, DACT, or 4120 Network) have a card address of 8. If the SDACT Card is addressed as card 8, replace the SFIO card. Check the N2 harness (733-953). Make sure that all wires are attached to the correct terminals and all connectors are secure.
Indicates that the card at address 8 is some type other than an SDACT card. Wrong Card Ensure that no other N2 cards (LCD Annunciator, 24 Point I/O, RS232, DACT, or 4120 Network) have a card address of 8. If the SDACT Card is addressed as Card 8, replace the SFIO card. This trouble indicates that the SDACT attempted to dial the central station and communication was lost. Contact the central station to determine whether the problem is on the customer or central station end. This trouble indicates that the phone line has been disconnected. Swap a known working card in place of the SDACT and see if the problem corrects itself. Check the lines physical connections; contact the phone company for additional troubleshooting help. This trouble indicates that the on board SDACT card checksum test has failed. Use the SDACT programmer to reload the SDACT database. The database is either corrupt or was never loaded. This trouble indicates that the configuration loaded on the SDACT card differs from the configuration on the master. Make changes to the 4010, build and download the 4010, then merge the new .PTF file in the SDACT programmer and download the SDACT card.
Central Station
Program Checksum
DB Version Mismatch
2-12
Network Troubles
Table 2-6. Network Troubles Trouble Message Possible Causes / Troubleshooting Indicates that the network card is not communicating with the master. Missing Card Ensure that no other N2 cards (LCD Annunciator, 24 Point I/O, RS-232, SDACT, or 4120 Network) have a card address of 8. If the network card is addressed as card 8, replace the SFIO card. Check the N2 harness. Make sure that all wires are attached to the correct terminals and all connectors are secure. If the network card is reported as missing during a system reset, upgrade the 4010 BIN file and programmer to Rev. 2.
Indicates that the card at address 8 is some type other than a network card. Wrong Card Ensure that no other N2 cards (LCD Annunciator, 24 Point I/O, RS-232, SDACT, or 4120 Network) have a card address of 8. If the network card is addressed as Card 8, replace the SFIO card.
Version Mismatch
This trouble indicates that the configuration loaded on the network card differs from the configuration on the master. Either changes were made to the database and it was not rebuilt and reloaded, or the wrong job is loaded. This trouble indicates that communication was lost between the network card and the 4120 network.
Swap another 4120 card in place of the existing card to check whether the 4120 card is the source of the problem. Check all network field wiring for shorts and opens. Use the 4100 or GCC diagnostics to troubleshoot; examine the network attendance and topology screens to determine the location of the problem.
Ground Fault
If you are using a fiber optic transmitter/receiver module, examine the network cards supporting bracket to see if the module is touching the bracket. If it is, use a strip of insulating material to isolate the bracket from the fiber optic module. If you are using a fiber optic network card (565-818) and the ground fault is intermittent, check to see if resistor R62 is present. It should be a 10 K resistor. If the resistor is missing, replace the card with version Rev. A1. This trouble indicates that more than one node on the 4120 network is answering for the same address. (Note that this trouble is not presently supported.) This trouble indicates that the port-to-port network wiring is incorrect (i.e. left-to-left or right-to-right). Check the network wiring and swap if necessary.
Duplicate Node
Network Miswire
2-13
Indicates that the card within this address range is some type other than a 24 point I/O card. Wrong Card Ensure that no other N2 cards (LCD Annunciator, 24 Point I/O, RS-232, SDACT, or 4120 Network) have a card address of 8. If the 24 point I/O card is addressed within this range, replace the SFIO card.
Indicates a trouble on one of the 24 PT I/O cards points. Possible troubles include: 24 PT I/O Point Troubles I/O Card #, Point X (where X is a point from 1 to 24) Manual Override. Manual Disable. Short. Ensure that the power feeding the LEDs is installed on TB5. Open. Check field wiring.
2-14
LCD Troubles
Table 2-8. LCD Troubles Trouble Message Missing Card Possible Causes / Troubleshooting Indicates that the LCD card is not communicating with the master. Ensure that no other N2 cards (24 Point I/O, RS-232, SDACT, or 4120 Network) have a card address within the range of 9-14. If the LCD card is addressed within this range, replace the SFIO card. Check the N2 harness. Make sure that all wires are attached to the correct terminals and all connectors are secure.
Indicates that the card within this address range is some type other than a 24 point I/O card. Wrong Card Ensure that no other N2 cards (24 Point I/O, RS-232, SDACT, or 4120 Network) have a card address of within the range 9-14. If the LCD is addressed within this range, replace the SFIO card. This trouble indicates that there is a problem with the keypad on the LCD card. Reseat the LCD connectors and see if the problem clears. If the problem does not clear, replace the SFIO board. This trouble indicates that there is a problem with the display on the LCD card. Reseat the LCD connectors and see if the problem clears. If the problem does not clear, replace the SFIO board.
2-15
IDNet Device: M#-# Missing Option Card IDNet Device: M#-# Battery Fault IDNet Device: M#-# NAC Power IDNet Device: M#-# Missing Class A IDNet Device: M#-# IDNet Class A
2-16
D47
D48
2-17
Introduction
This chapter lists the 4010 FACPs 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. If You Are at the Panel When a Crash Occurs. Within 45 Seconds of a crash, the LCD clears, the LEDs flash, the piezo sounds, and a crash message displays for 45 seconds. After 45 seconds, the system attempts to reset itself and the crash information is cleared from the display. The crash message appears similar to the following. Make sure to record all information, including program counter, bank number, and task number. CRASH # xx PC = xxxx BANK # xx TASK xx
Crash # xx is a hexadecimal code corresponding to a specific unrecoverable error. Refer to Table 3-1 for a list of these codes and possible corrective actions. PC = xxxx is the hexadecimal address of the CPUs program counter. BANK # xx is the hexadecimal address of the active memory bank at the time of the crash. TASK xx is the active task number (in hexadecimal) at the time of the crash. 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.
In this Chapter
This chapter discusses the following topics: Topic Summary of Crash Codes See Page # 3-2
3-1
10
11 12 13 14 15 16 17 18 19 1A
3-3
blank
In this Appendix
A-1
Introduction
Keep the following in mind when reviewing this table: 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 SFIOs NACs requires the Rev. C SFIO board, Version 2 SFIO firmware, and Version 2 of the BIN file and programmer application. Discrete battery trouble reporting 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.
Table A-1. Compatibility Matrix for Versions 1 and 2 Programmer and BIN File Version 1 741-108 & 107 Yes Programmer and BIN File Version 2 741-108 & 107 Yes
Feature Phase 1 Features IDNet U9 Overload Protection 4010 SFIO QuickAlert NACs FM Battery Charger TBL 4009 IDNet Interface Other Version 2 Features
Yes Yes
Yes Yes
A-2
Using the programmer to edit jobs on a panel containing older versions of the SFIO chip and board has the following effect: 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 jobs Phase II designation.
Because this situation may become confusing, it is recommended that you upgrade the panels SFIO card and SFIO firmware before editing its job with the Phase II programmer.
A-3
Introduction
This appendix provides basic troubleshooting procedures related to the 4010 FACPs power supply. This appendix discusses the following topics: Topic Adjusting the AC Power Supply Brownout Potentiometer Checking AC Power Supply Transformer / Bridge Rectifier Checking EPS Transformer / Bridge Rectifier See Page # B-2 B-3 B-6
In this Appendix
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 3
Figure B-1. Correct Position AC Power Supply Brownout Potentiometer Using a Variac to Adjust the Brownout Potentiometer The following procedure describes using a variac to adjust the brownout circuit. 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. 1. 2. 3. 4. 5. Turn R252 counter-clockwise to its maximum resistance setting. Connect the system to nominal AC line voltage. Adjust the AC input voltage to place the system in brownout. Adjust the AC input voltage to 107.8 108 VAC. Adjust R252 until K8 energizes.
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
The 4010 line voltage transformer and bridge rectifier convert 120 VAC to the 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. Interpret the results of this test, as follows: If there is power at H1 and H2, the most likely cause is an incorrectly adjusted brownout potentiometer. Refer to the previous section in this appendix for information on setting this component. 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.
2.
P9
Location of H1 and H2
Figure B-2. Location of H1 and H2 and P9 and P10 Checking Connectors A series of plastic connectors link the 4010 PC board, the line voltage transformer, and the bridge rectifier to the buildings AC power circuit. Checking the integrity of these connectors allows you to eliminate these components as a possible cause for AC power problems. 1. 2. 3. REMOVE ALL POWER (AC and Battery) FROM THE PANEL. Remove the four Torx screws that secure the panels electronics to the chassis. Disconnect the External Power Supply harness from connectors P13 and P14 on the 4010 PC board. Continued on next page
B-3
4. 5.
Disconnect connectors P9 and P10, located on the left side of the panels PC board. Label the wires to make reattachment easier. See Figure B-2. Lift the panels 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. Remove and visually inspect the AC power bulkhead connector. This connector mounts to the bottom of the panel chassis, and connects the incoming AC Power wiring to the input wiring of the line voltage transformer. Check the crimped connection between the connector and the wires. Gently pull on the wires to make sure that they are firmly attached to the connector. Refer to Figure B-3 for the location of the bulkhead connector. 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.
6.
7.
Bridge Rectifier
Figure B-3. Visually Inspect the Condition of Terminals Continued on next page
B-4
If there is no voltage at H1 and H2 and a visual inspection of the connectors does not reveal any obvious problems, you should replace the line voltage transformer and the bridge rectifier, using the following instructions. 1. 2. 3. 4. 5. 6. 7. 8. REMOVE AC POWER FROM THE PANEL. Remove the four Torx screws that secure the panels electronics to the chassis. Disconnect the External Power Supply harness from connectors P13 and P14 on the 4010 PC board. Disconnect connectors P9 and P10, located on the left side of the panels PC board. Label the wires to make reattachment easier. See Figure B-3. Lift the panels electronics from the chassis, and disconnect the four connectors attached to the bridge rectifier. Unbolt the bridge rectifier and transformer from the 4010 chassis and replace. Reattach all wiring as shown in Figure B-4. Reconnect all connectors and reapply AC Power.
BLU BRN
BRIDGE RECTIFIER
AC
+
AC
H1 H2 P9 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. 1. Meter the DC voltage across the terminals marked RED1 and BLK1 on the 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. 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.
2.
BLK1
RED1
Bridge Rectifier
B-6
Checking Connectors
A series of plastic connectors link the EPSs line voltage transformer and bridge rectifier to the buildings AC power circuit. Checking the integrity of these connectors allows you to eliminate these components as a possible cause for EPS power problems. 1. 2. 3. 4. REMOVE POWER (AC and Battery) FROM THE PANEL. Remove the two Torx screws that secure the EPS to the chassis. Disconnect the EPS harness from connectors P1 and P2 on the EPS module. 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. 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. Reattach all connectors and reapply AC power. Check the voltage at RED1 and BLK1. If there still is no voltage, replace the EPSs 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.
5.
6.
EPS Bulkhead Connector Figure B-6. Visually Inspect the Condition of Terminals Continued on next page
B-7
If there is no voltage at RED1 and BLK1 and a visual inspection of the connectors does not reveal any obvious problems, you should replace the line voltage transformer and the bridge rectifier on the EPS, using the following instructions. 1. 2. 3. 4. 6. 7. REMOVE AC POWER FROM THE PANEL. Remove the two Torx screws that secure the EPS assembly to the chassis. Disconnect the External Power Supply harness from connectors P1 and P12 on the 4010 PC board. Lift the EPS assembly from the chassis, and disconnect the four connectors attached to the bridge rectifier. Unbolt the bridge rectifier and transformer from the 4010 chassis and replace. Reconnect wires to the bridge rectifier, as follows: 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 4010s 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. This appendix provides a summary of the built-in diagnostic utilities provided with the 4010 FACP.
In this Appendix
This appendix discusses the following topics: Topic N2 Comm Diagnostics IDNet Diagnostics IDNet Earth Fault Search Diagnostics Network Diagnostics WalkTest TrueTest Basic Service Procedures Known Solutions See Page # C-2 C-3 C-4 C-5 C-6 C-7 C-9 C-11
C-1
N2 Comm Diagnostics
Procedure
Use the N2 Comms Diagnostics to check for noisy N2 comm lines and other N2 comm errors 1. 2. 3. 4. Press <MENU>. Press <NEXT> or <PREVIOUS> until [Diagnostics] is displayed and then press <ENTER>. Press <NEXT> or <PREVIOUS> until [N2 COMM] is displayed and then press <ENTER>. Press Press <NEXT> or <PREVIOUS> until [ON] is displayed and then press <ENTER>.
The screen in Figure C-1 shows a typical N2 Communication Diagnostic screen. This screen informs you of the amount of messages sent, the amount of message retries and the amount of card failures. Note that these tallies are only kept while diagnostics are active.
Card Address
4010 Card 1, 4010 NAC/Relay Card Msgs Sent=0 Retries=0 Fails=0 Figure C-1. N2 Communication Diagnostic Screen Pressing <NEXT> or <PREVIOUS> scrolls through the available cards that are communicating on the N2 lines and displays that cards N2 diagnostic information. Pressing <ENTER> (while a particular cards information is displayed) prompts you to press <ENTER> again to clear the message counts for that card.
C-2
IDNet Diagnostics
Procedure
1. 2. 3. 4.
Press <MENU>. Press <NEXT> or <PREVIOUS> until [Diagnostics] is displayed and then press <ENTER>. Press <NEXT> or <PREVIOUS> to select [IDNET DIAGNOSTICS] and then press <ENTER>. Press <NEXT> or <PREVIOUS> to select either [DUPLICATE DEVICES] or [WEAK ANSWER DEVICES] and press [Enter].
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.
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. 2. 3. 4. Press <MENU>. Press <NEXT> or <PREVIOUS> until [Diagnostics] is displayed and then press <ENTER>. Press <NEXT> or <PREVIOUS> to select [IDNET EARTH FAULT SEARCH] and then press <ENTER>. Press <NEXT> or <PREVIOUS> to select [ON] and then press <ENTER>.
If an earth cannot be isolated or there are no isolators configured on the system, the 4010 returns a Unable to Isolate Earth Fault message. 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
Network diagnostics allow you to check the node number of the 4010, the network topology, and network attendance. Figure C-2 shows a typical Network Topology screen. Topology information shows how the network is physically wired and whether there are any breaks in the network loop. M2 4 (1) L5 6 7 R9
M = Monitor Node L = LEFT End Node R = RIGHT End Node (_) = This Node = Missing Node
Figure C-2. Network Topology Screen Attendance information shows if the network nodes are configured. Each position on the 4010s LCD represents a nodes address for a maximum of 80 nodes (only 80 nodes can be displayed because there are only 80 positions on the 2 by 40 character LCD). Each node can only be represented by one character. Figure C-3 is NOT a typical Attendance screen, it is shown for 1 = Node Number 1 reference only. M = Monitor Node (Node Number 2)
.= No node configured at this address 4 = Node Number 4 L = Node Number 5 (fifth position on the screen) and it is the Left End Node.
= Missing Node
7 = Node Number 7 R = Node Number 9 (ninth position on the screen and it is the Right End Node. 2 = Node Number 22 (twenty-second position on the screen) 3 = Node Number 43 (forty-third position on the screen) 9 = Node Number 79 (seventy-ninth position on the screen)
C-5
Walk Test
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. Using Walk Test To activate Walk Test, follow Steps 1 through 6. 1. 2. 3. 4. 5. Press <MENU>. From the High-Level Status screen, press <MENU>. Press <NEXT> or <PREVIOUS> until [WalkTest] is displayed and then press <ENTER>. Press < > or < > to move the focus brackets to the desired option. 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. Press <ENTER> to activate Walk Test.
6.
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 Figure C-4. Walk Test Screen Important Notes Smoke detector LEDs do not activate in Walk Test when the 4010 BIN file is at Version 1. A head missing trouble is not reported during Walk Test. Walk Test does not sound signals that are controlled via Custom Control programming.
C-6
TrueTest
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 points status by selecting the desired point at the front panel and pressing <NEXT> or <PREVIOUS> until the TrueTest screen is displayed. The points 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 points 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). TrueTest Option On/Off Log/NoLog Print/NoPrint DACT/NoDACT NoCTRL/CTRL Table C-1. TrueTest Menu Options Description Activates or deactivates TrueTest. Determines whether the TrueTest events are sent to the logs. Determines whether the TrueTest events are sent to a printer. Determines whether any events occurring in TrueTest are reported to the DACT. By default no control circuits of any kind are activated during the test. If desired, all control points may be activated during the test by selecting CTRL. this category includes all control points (audibles, visibles, and any other control points). Continued on next page
C-7
TrueTest, Continued
Using TrueTest Use Steps 1 through 5 and Figures C-5 to activate TrueTest. 1. 2. 3. 4. 5. Press <MENU>. Press <NEXT> or <PREVIOUS> until [TrueTest] is displayed and then press <ENTER>. Press < > or < > to move the focus brackets to the desired option. Press <NEXT> or <PREVIOUS> to enable the options shown in the figure below. Once all options are set, press <ENTER> to activate TrueTest.
Top Level Menus
Walk Test
TrueTest
Quick CFIG
Figure C-5. TrueTest Options 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 Figure C-6. TrueTest Screen
C-8
The following procedure returns the 4010 CFIG (job) loaded on the panel to a 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. To do this, follow these steps: 1. 2. Press the Warm Start button. Press and hold the Left and Right arrow keys.
The 4010s software revision is actually the revision level of the BIN file downloaded to the panel. Use the following procedure to determine this information: 1. 2. 3. Press <MENU>. Press <NEXT> or <PREVIOUS> to scroll through the options until [SOFTWARE REVISION] is displayed and then press <ENTER>. Press <ENTER>. Information similar to the following appears. The number following Sys Rev. is the revision level of the panels BIN file. Sys Rev 2.00.06 JOB REV: 1 12:00:00 am 4010 System Wed 27-Aug-97
Figure C-7. CFIG Properties Disabling the Piezo on a Remote LCD Annunciator Disable the piezo on a 4606-9101 Remote LCD Annunciator by turning ON digital pseudo point P48 (LCD Annunciator Sounder Disable). To do this from the front panel, follow these steps. 1. 2. 3. 4. 5. Clearing an Event Overflow Trouble Press <MENU>. Press <NEXT> or <PREVIOUS> until [Control/View Points] is displayed and then press <ENTER>. Press <NEXT> or <PREVIOUS> to scroll through the point types until the [Digital Pseudo Points] appears and press <ENTER>. Press <NEXT> or <PREVIOUS> to scroll through the points until [P48] appears and press <ENTER>. Press <NEXT> or <PREVIOUS> to toggle the state of the point.
Anytime the panel receives in excess of 127 events per second, the event queue overflows and the panel indicates this by generating an Event Queue Overflow Trouble. This trouble can be cleared in one of two ways: Restart the panel. Manually turn OFF Digital Pseudo Point P47. Continued on next page
C-9
Follow these steps to turn off P47 from the front panel. 1. 2. 3. 4. 5. Press <MENU>. Press <NEXT> or <PREVIOUS> until [Control/View Points] is displayed and then press <ENTER>. Press <NEXT> or <PREVIOUS> to scroll through the point types until the [Digital Pseudo Points] appears and press <ENTER>. Press <NEXT> or <PREVIOUS> to scroll through the points until P48 appears and press <ENTER>. Press <NEXT> or <PREVIOUS> to toggle the state of the point.
C-10
Known Solutions
The supervisory point type, when used with system outputs such relays, does not 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.) Two solutions exist for this problem: 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.
The 4010 does not properly control IDNet devices at addresses 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 LEDs connected to a duct sensor do not illuminate when the duct sensor goes into alarm. This is a Version 1.x problem that has been fixed by Version 2.x. When used in conjunction with the 4010, the SDACT programmer must be at Revision 1.04 or higher. If you are unable to download to the SDACT, move the SDACTs switch to the OFF position and then back to the ON position while the programmer is attempting to download the file. Continued on next page
C-11
24-Point I/O Incorrect Relay / LED Operation System Reset Problems -IDNet Class A Trouble
In cases where the relay or LED connected to a 24 point I/O output does not pick or light, check the field wiring to make sure voltage is wired to TB2. A 4010, containing a Revision 1.x BIN file, does not reset when the following conditions are true: A Class A IDNet trouble exists A device is in alarm
This problem has been corrected by Version 2.x of the 4010 software. System Reset Problems -Lengthening Reset Timer for Networked Systems The 4010 reset duration -- the amount of time required by the 4010 to perform a reset -- is self-adjusting based on the number of IDNet devices attached to the system. If the 4010 has a large number of devices (approximately 200), the 4010s 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 Invalid Opcode for IPHOTO or RPHOTO Points with a valid device type of IPHOTO or RPHOTO may receive an Invalid Device Type for this Opcode message, when used within a Custom 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. This appendix discusses the following topics: Topic Class A LED Displays Class B LED Displays See Page # D-3 D-5
In this Appendix
D-1
Overview
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.
FIBER TRANSMIT LED1 FIBER RECEIVE LED2 FIBER OPTIC TRANSMITTER U16 FIBER OPTIC RECEIVER U18
FIBER TRANSMIT LED2 (SEE NOTE 1) FIBER OPTIC TRANSMITTER U19 FIBER OPTIC RECEIVER U20 FIBER OPTIC TRANSMITTER U21 (SEE NOTE 2) FIBER OPTIC RECEIVER U22 (SEE NOTE 2)
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
Check the U17 and U22 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. 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 RX TX LED 2 LED 3
Check the U18 and U19 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. 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 RX TX LED 2 LED 3
Check the U19 (the one on the fiber optic receiver card) and U21 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. 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 RX TX LED 2 LED 3
Check the U16 and U20 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. 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. Continued on next page
D-3
LED 1 RX TX
LED 2 LED 3
LED 1 RX TX
LED 2 LED 3
Indicates a problem with connectors U16 and U18 on the fiber optic receiver card. Check the following: 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. This LED pattern also occurs if both U16 and U18 on the receiver card are unconnected.
LED1 RX TX
LED2 LED3
Indicates a problem with connectors U19 and U18 on the fiber optic receiver card. Check the following: Check to see if U19 and U18 are crossed. U19 on the receiver card must connect to U21 on the fiber optic transmitter card, and U18 must connect to U19 on the transmitter card. This LED pattern also occurs if both U19 and U18 on the receiver card are unconnected.
LED1 RX TX
LED2 LED3
Indicates a problem with connectors U17 and U18 on the fiber optic receiver card. Check the following: Check to see if U17 and U18 are crossed. U17 on the receiver card must connect to U22 on the fiber optic transmitter card, and U18 must connect to U19 on the transmitter card. 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. Table D-2. Class B LED Displays
LED Pattern
LED1 RX TX
LED2
There is a problem with the fiber running between U18 on the fiber receiver card and U19 on the fiber optic transmitter card. There is a problem with both fibers (i.e., both fibers are damaged or cut). The fiber cables were wired incorrectly (i.e., TX to TX and RX to RX). Make sure that U18 on the receiver connects to U19 on the transmitter. Likewise, make sure U16 on the receiver connects to U20 on the transmitter.
LED1 RX TX
LED2
Indicates a problem (damage, break, bad connectors) with the fiber running between connectors U16 on the receiver and U20 on the transmitter card.
D-5
Index
Misc.
24 point I/O card troubles missing card trouble, 2-14 specific point troubles, 2-14 4009 IDNet NAC Extender and intermittent IDNet missing card trouble, 2-8 4009 IDNet NAC Extender troubles, 2-16 4010 programmer features for different revisions, A-2
D
DB version mismatch trouble for SDACT card, 2-12 diagnostics network diagnostics, C-5 digital pseudo point troubles, 2-17 duct sensor problems with remote LED, C-11 duplicate device trouble, 2-9
A
AC power flowchart, 1-4 AC power supply checking, B-3 replacing transformer/bridge rectifier, B-5 AC power trouble for power supply card, 2-4
E
Earth ground troubles and dual RS-232 card, 2-5 and power supply card, 2-5 intermittent, 2-5 EPS battery trouble, 2-5 EPS transformer checking, B-6 replacing, B-8 EPS trouble for power supply card, 2-4 event queue overflow trouble, C-9
B
bad answer trouble, 2-9 basic service procedures, C-9 battery charger trouble for power supply card, 2-7 battery depleted disconnected trouble for power supply card, 2-6 battery low cutout trouble for power supply card, 2-6 battery low trouble for power supply card, 2-6 battery terminals and EPS trouble, 2-4 checking, 2-7 baud rate and missing card trouble for IDNet card, 2-8 and missing card trouble for NAC, 2-2 and missing card trouble for power supply, 2-4 BIN file availability of, 1-3 corrupt, damaged, or missing, 1-2 determining software revision, C-9 features for different revisions, A-2 new SFIO has none, B-2 bridge rectifier checking, B-3, B-6 replacing, B-5, B-8 brownout, 1-4 adjusting, B-2
F
fiber optic media card class A LED displays, D-3 class B LED displays, D-5 overview of components, D-2
I
IAM and no answer trouble, 2-9 IDNet device # 124 or # 24, C-11 IDNet diagnostics, C-3 IDNet Earth fault search diagnostics, C-4 IDNet troubles and 4009 IDNet NAC Extender, 2-8 and isolator bases, 2-8 and monitor IAMs, 2-10 and pull stations, 2-10 and RIAMs, 2-10 and TrueAlarm devices, 2-10 and ZAMs, 2-10 bad answer, 2-9 channel failure trouble, 2-8 Class A status trouble, 2-10 duplicate device, 2-9 extra device trouble, 2-10 ground fault status trouble, 2-10 missing card trouble, 2-8 no answer, 2-9 power supply status trouble, 2-10 short status trouble, 2-10 wrong card troubles, 2-9 wrong device, 2-9
C
central station trouble for SDACT card, 2-12 CFIG format mismatch, 1-2, 1-3 class A trouble for a NAC, 2-2 code scan/link scan loop, 1-2, 1-3 crash codes, 3-2
IN-1
isolator bases and IDNet channel failure trouble, 2-8 and no answer trouble, 2-9
P
PCC chip and channel failure trouble, 2-8 piezo disabling on LCD Annunciator,C-9 Port A/B disconnected trouble, 2-11 power supply troubles, 2-4 AC power trouble, 2-4 battery charger trouble, 2-7 battery depleted/disconnected trouble, 2-6 battery low cutout trouble, 2-6 battery low trouble, 2-6 Earth ground troubles, 2-5 EPS battery trouble, 2-5 EPS trouble, 2-4 missing card trouble, 2-4 wrong card trouble, 2-4 power up flow charts initial startup sequence, 1-2 power up flowcharts overview of, 1-1 printer troubleshooting, 2-11 program checksum trouble for SDACT card, 2-12 programming restoring default, C-9
K
known solutions, C-11
L
LCD Annunciator disabling piezo, C-9 LCD display trouble for LCD card, 2-15 LCD membrane trouble for LCD card, 2-15 LCD troubles LCD display trouble, 2-15 LCD membrane trouble, 2-15 missing card trouble, 2-15 wrong card trouble, 2-15 link scan/code scan loop, 1-2, 1-3
M
MAPNET II ZAM and no answer trouble, 2-9 missing card trouble and RS-232/modem card, 2-11 for 24 point I/O card, 2-14 for LCD card, 2-15 for NAC card, 2-2 for power supply card, 2-4 for SDACT card, 2-12
R
remote LED problems with, C-11 revision levels and boot software, 1-3 RS-232/modem card does not come on-line, 2-11 missing card trouble, 2-11 Port A/B disconnected trouble, 2-11 wrong card trouble, 2-11
N
N2 comm diagnostics, C-2 NAC determining current draw, 2-3 troubles for NAC 3 or 4, 2-3 NAC circuit trouble troubleshooting for, 2-2 NAC signal power trouble, 2-3 NAC troubles Class A, 2-2 missing card, 2-2 NAC circuit trouble, 2-2 signal power, 2-2 wrong card, 2-2 network. see diagnostics, network diagnostics network card troubles duplicate node trouble, 2-13 ground fault troubles, 2-13 missing card trouble, 2-13 net comm failure trouble, 2-13 network miswire, 2-13 version mismatch trouble, 2-13 wrong card trouble, 2-13 network diagnostics, C-5
S
SDACT conversion errors, 11 SDACT download problems, 11 SDACT troubles central station trouble, 2-12 DB version mismatch trouble, 2-12 missing card trouble, 2-12 phone line 1 or 2 trouble, 2-12 program checksum trouble, 2-12 wrong card trouble, 2-12 serial devices troubleshooting, 2-11 SFIO board features for different revisions, A-2 supervisory point type, C-11 system reset and Class A trouble, C-12 lengthening reset timer, C-12
O
output devices problems with supervisory point type, C-11
T
trouble messages NAC troubles, 2-2 TrueAlarm isolator devices, 1-3
IN-2
V
variac using to adjust brownout, B-2 version 1 and 2 compatibility, A-
using Walk Test, C-6 wrong card trouble for 24 point I/O card, 2-14 for a NAC, 2-2 for LCD card, 2-15 for power supply card, 2-4 for SDACT card, 2-12 wrong device trouble, 2-9
W
Walk Test, C-6 and Custom Control, C-6 and head missing trouble, C-6 smoke detector LEDs don't light, C-6
Z
ZAM and no answer trouble, 2-9
IN-3
Rev. A
Simplex Time Recorder Co., Simplex Plaza Gardner, Massachusetts 01441-0001 U.S.A. Simplex International Time Equipment, Co., LTD. Mississauga, Ontario, Canada
579-081