Operation Manual
28
11.3 Troubleshooting
The elimination of possible malfunctions listed below is made by the Client. If the fault persists, we
recommend you to contact one of the service centers of
PERCo
company. A list of service centers
is given in the Certificate.
Before the diagnostics the user should open the controller housing.
Each controller relay output is equipped with diagnostics LED indicator for convenience. The turn
on/off of LED indicators identifies that relay is activated/deactivated.
Possible faults:
11.3.1 The controller does not work
Possible causes of the controller malfunction:
1.
Loosening of the wires in the terminal blocks of the controller board
– tighten the screws
of the terminal blocks with a screwdriver.
2.
Power source
malfunction
of the controller – check the power source.
3.
Malfunction of connection lines
used to connect various devices (reader, indication block
with infrared detector, lock, turnstile, door sensor, RC-panel, siren, etc.) to the controller –
check connection lines.
4.
Identical addresses of connected devices are set
– set different addresses. Check the
connection of address lines.
5.
Failure of devices connected to the controller
– check the operation of the devices.
6.
Failure of radioelectronic components
, installed on the controller board – contact
PERCo
service in order to replace this board.
11.3.2 Communication failure between controller and PC
Possible causes of this malfunction:
1.
Network settings in the computer are missing
– set IP-address and subnet mask of the
computer. The controller should be connected either directly to network connector of network
card of the computer or to the same Hub / Switch the computer is connected to.
2.
Invalid password of the controller
. Check the password entered in the software.
3.
Malfunctions of the computer
(software, databases etc.).
To detect this malfunction, start the command:
ping x.x.x.x,
where
x.x.x.x
is the IP-address of the controller.
If there is communication, you will see lines similar to the following:
Reply from x.x.x.x: bytes=32 time<10ms TTL=128
If there is no communication (response), check router settings of your network.
4.
Malfunctions of equipment of Ethernet network
, installed between the computer and the
controller: hub, switch and other network equipment including communication cables.
To detect this malfunction, start the command:
ping x.x.x.x -l 576,
where
x.x.x.x
is the IP-address of the controller.
If there is communication and standard minimal packets (576 bytes) are not fragmented, you
will see lines similar to the following:
Reply from x.x.x.x: bytes=576 time<10ms TTL=128
In such case IP-packets are not fragmented to the size less than 576 bytes and the selected
connection must be operational.
If the positive answer is not received, the problem may be related to the network switching
equipment that fragments IP-packets to the size less than 576 bytes. Check settings of this
equipment, enlarge the size of
MTU
. This parameter is usually related to as
MaxMTU
or
IPMTU
.
5.
If several variants of switching are possible
, use command:
ping x.x.x.x -l 576 -t
Содержание CT/L-14
Страница 1: ...Controller CT L 14 ASSEMBLY AND OPERATION MANUAL...
Страница 2: ...CT L 14 Controller Assembly Operation Manual...
Страница 58: ...www perco com...
