Problems with door access control systems are very common happened when you are processing access control system installation, even you can find a lot of problems with magnetic locks, electromagnetic door lock troubleshooting or card access troubleshooting, so here some troubleshooting methods and essential tools for you.
1，Multimeter, Purpose: To check if the voltage is normal and if the circuit is short-circuited or broken circuit.
Prepare a set of access control systems equipment:
485 and TCP communication mode controller*each one
ID and IC card reader*each one
Several ID cards and IC cards
NONC*1, 485 converter*1
Standard power supply (12V, above 5A)*1, Purpose: For the substitution test
2, Small flathead screwdriver, Purpose: Use to remove the wires off the terminals.
3, Cross screwdrivers
Purpose: Disassembly the controller plate, case and power supply, etc.
4, Notebook: Must be with a serial port or USB serial port converter and network port.
Purpose: For excluding test. Exclude the faults or operation systems problems of the user’s computer itself
5, Network HUB: (two or three directly connected cable with modular plugs)
Set up a small LAV environment to test if the TCP controller has communication problems
6, Test pencil: To check if there are electric leakage of the computer and controller case. To find out the location of the AC live wire.
7, 120Ohm terminal resistance, Improve the anti-jamming capability of 485 circuits on some special occasions. Preparing several pieces are enough.
8, Interphone, It used to provide convenience for people on different floors to check the faults and communicate. Not required, can be replaced by cellphones.
Common used methods
1, Software testing:
First, start the management software to enter the【Central console】and select the faulty gates. Then click 【Test】. The information from the running software will display relevant faults, and you can troubleshoot them accordingly. For example, the software set up some advanced settings, such as open the door with multiple cards were set up under the condition that the user know nothing about, this will cause failure to open the door with the cards.
【Real-time monitoring】method: Select the door need to【real-time monitor】in the【Central console】
Real-time monitoring corresponds to the corresponding punching card indicator lights to find out the faults of failure to punch the card.
The corresponding communication indicator lights can better help with finding out the communication faults.
【Searching.net】method: Select 【Controller】in the【Basic setup】
Can find out the communication faults in TCP/IP controller
Indicator light method:
CPU indicator light
The CPU indicator lights is flashing when it works normally. If keeps lighting or not bright, there’s the possibility that the CPU is connected with the wrong power supply, or the controller chip has been damaged.
CARD indicator light:
As long as punching in any card reader under the controller and pass through the card number,the indicator light flashes. If the indicator light doesn’t respond after punching, the problems may be:
The circuit from the card reader to the controller is broken, or the data wire is connected wrong or connected reversely.
The output format of the card reader is incorrect.
The card reader is broken
The card reader’s input port of the controller is broken.
ERR fault indicator light:
The light is not bright under normal condition. If the light flashes or keeps lighting, the problems may be:
The chips in the controller probably burn out, storage disorder needs to format, or other faults. Please contact the manufacturer’s technician.
Communication indicator light:
Rx light indicates the controller receives signals (including normal and interference signals)
Tx light indicates the controller emits signals.
Rx (Link) light, keep always lighting indicates there are no problems with wires connecting. (It is also possible that there are some special problems that have not been detected and can only be said to be basically normal.)
Tx light, flashing indicates being communicating.
Equipment substitution method:
Replace the faulty equipment with a device that is sure of good (usually tested, often used) to see if the malfunction is gone.
If it goes away, it’s possible that the device is broken. But it’s not entirely certain, because if it’s an environment or something that causes a failure, it doesn’t necessarily show up right away, or it’s going to hurt the new device for a while.
If the device in question, separate test no problem, this may be related to environmental problems such as wiring. One should actively continue to find out the fault source. Do not think that change the equipment means everything is all right.
Notebook substitution method.
Can check out if there are problems with the user’s computer or operating system or with the wrong setup.
If there are multiple devices, and only one device finds out with a problem, if it’s not the device problem, there must be something outside of it that causes this specificity.
If there is more than one equipped with the same problem, it is unlikely that all of the equipment will be broken, and there must be one and the same factor that causes all equipment to have the same failure characteristics. So finding the same point is the key to finding the source of the failure.
If there is more than one equipment in a system and you are concerned about the cause of the malfunction due to mutual influence, consider using dichotomy to evacuate all equipment, which helps to speed up troubleshooting. For example, A system has 8 controllers, consider disconnecting the back of 4, then disconnect the remaining 4 of the two