Live Search |
---|
When troubleshooting a controller, do things in a methodical manner and take careful notes regarding status of ScramblePad LEDs, controller board LEDs, voltage levels, and so on. In DIGI*TRAC controllers, a printer is essential for troubleshooting. The only way to determine how the controller and system it controls is working is to review the printouts. Also, the only way in which a programmer can tell how the system is responding to instructions is to view the responses on the printer. Hirsch provides a comprehensive set of commands that can print out the setups and status of the entire DIGI*TRAC system.
Common Problems
Problems fall into two broad categories:
Hardware
Programming
Common hardware-related problems on initial system installation include:
Wiring not connected properly
ScramblePads not addressed correctly
Electric locks and power supplies not installed or wired properly
Door contacts not aligned or wired properly
RQE motion detectors not aligned, balanced, or wired properly
Wiring gauge or length is inappropriate
MOVs are not installed at electric locks
Common hardware problems encountered after a system has been up and running for a while are:
Loose wire connections or damaged splices
Spikes, surges, brownouts causing electrical damage
Noise on the primary AC input circuit
Common programming-related problems on initial system installation include:
System clock not accurately set so codes and automatic events do not work as expected
RQE inputs not programmed to unlock doors
User codes assigned to the wrong Access Zones
Common programming problems encountered after the system has been up and running for a while are:
Wrong user deleted from the system
Access Zones changed
New user added and is given the wrong code or Access Zone
Time Zones, Alarms, or Control codes affecting relays are in an unexpected or conflicting mode
System administrator forgets system code to get into programming
General Troubleshooting Procedures
The following things should always be checked in any system this is not operating properly:
1.Verify that the system is powered properly. Check AC input voltage and all fuses.
2. Verify that all wiring is terminated properly and that there is line continuity (no breaks or shorts).
3. Look for any visible signs of damage at the ScramblePad and controller.
4. Confirm system programming. Verify system clock is set accurately. Verify that all Time Zones, Access Zones, Access Codes, Control Codes, and so on are properly entered.
DIGI*TRAC Troubleshooting Guide
Table 1-33: DIGI*TRAC Troubleshooting Guide
Expand | ||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||
|
Troubleshooting the Controller Using Status LEDs
You can troubleshoot the controller board using the LED status lights on the right side of the controller board.
Table 1-34 describes what each of the LEDs mean:
Table 1-34: LED Status Chart
LED | Status | Condition |
---|---|---|
BOX TAMPER | Yellow ON | Box Tamper |
AC | Green ON | AC OK |
BAT | Green ON | Battery OK (24V-28V) |
SYS | Green ON | Controller OK |
KPD | Red Flash | Controller polling all attached ScramblePads/MATCH |
NET | Red Flash | Network polling all attached controllers |
TEST | Yellow ON | Controller in Self Test Mode |
ALARM | Yellow ON | Alarm events in the buffer |
The Controller board’s power circuits are all fused. The location of each fuse is clearly marked on the board and provides surge protection. If a fuse blows, replace it immediately.
On power-up, the system performs a series of tests. A failure is indicated by a steady red from SYS. A quick LED diagnostic is shown below.
Table 1-35: Status LED Configurations
In black and white, grey indicates steady green and black indicates steady red.
For more about troubleshooting the controller, refer to “DIGI*TRAC Troubleshooting Guide” on page 1-227.
ScramblePad Troubleshooting Guide
Table 1-36: ScramblePad Troubleshooting Guide
Expand | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||
|
Hardware Cold Start Procedure
There are rare occasions when you will have to perform the hardware cold start procedure. Normally, if you just want to reassign or relocate the panel or erase all codes and setups, use the 30-second RESET button procedure defined in “Resetting the Controller”.
This procedure only works for pre-CE CCM Version 6.X.X. boards manufactured more than three or four years ago. Newer CCM7 boards cannot use this procedure. The difference between these boards is shown in Figure 1-127.
Figure 1-127: CCM Version Comparisons
This procedure should only be performed when the red SYS LED on the controller board is lit and no action you take seems to affect this condition. This usually means that the controller is locked up and only a cold start will work. Performing this procedure under any other circumstances is highly discouraged.
Note |
---|
Using this procedure deletes all setups and configurations. |
To perform a cold start:
1.Ground yourself by touching the controller enclosure or power supply to remove any potential static electricity.
2. Turn all controller system power off by removing connectors for both AC power and the standby battery.
a. Disconnect the DC battery.
b. Disconnect the main power to the controller.
c. Remove the AC fuse located on the power supply in the lower left corner of the enclosure.
This procedure can only be performed with the power off.
3. Remove the CCM module.
4. Use a wire jumper, such as Radio Shack #278-016, to do this:
a. Attach the jumper to the pins 14 and 28 as shown in Figure 1-128.
Figure 1-128: Hardware Cold Start Jumper Setting
b. Wait 3 seconds.
c. Remove the jumper.
5. Plug the CCM module back into the controller.
6. Power up the controller.
Use this procedure only once or twice to see if the panel resumes normal operation after power-up. If the red SYS LED remains lit, it means there is a real hardware failure and the panel must be replaced and repaired.
Before You Call
If you are unable to diagnose a problem and take the necessary corrective action, contact your local dealer. The following steps should be performed to gather useful information:
1.Make a detailed description of the problem.
2. Make a detailed description of the system, including:
Controller type
Firmware version numbers (see “Getting Help” on page v)
Type and number of readers
Other system components (locks, door contacts, RQEs, and so on)
3. Specify how long the system has been installed and list any previous problems with the system.
4. Approximate the distance between system components, such as the distance between the controller and all readers.
Identiv recommends that all physical installations and cabling meet the specifications published in the appropriate electrical standard to ensure proper operation of all Identiv devices connected. When determining the required power delivery for connected devices, Installers should calculate cabling needs based on the power specifications of each connected device, the operational output of the power source and the voltage drop relative to the length of the cable. Identiv does not specify cable types or gauges due to the wide variance of available cable configurations, and similar wide variance in installation types and environmental conditions. All examples provided throughout this installation document are designed to provide guidance only and should be verified by a certified low voltage electrician or contractor on a per site basis.
If your dealer is not available, contact Technical Support directly. This can be done in a number of ways:
Internet: https://support.identiv.com/contact/
Email: support@identiv.com
Phone: 877-447-7249 toll-free
Mail: Identiv
1900-B Carnegie Avenue
Santa Ana, CA 92705-5520
Attn: Technical Support