Hakko Electronics Monitouch S8 Series, Спецификация аппаратного обеспечения

Страница: 72 / 79

6
2. Troubleshooting 6-5
Error Handling
2. Troubleshooting
In the Event of an Error
Perform the steps below:
1. If the current error matches a symptom in the following table, correct it by following the instructions
provided.
2. If the error does not match the symptoms in the table, contact your local distributor.
Please provide the distributor with the information on the MONITOUCH model, serial number,
symptom of the error, error message, etc.
Probable Symptoms
Symptom Cause Solution
MONITOUCH is connected to
controllers; however,
communication fails.
“Communication Error:
Time-Out” appears on the
screen. Probable causes are:
1) Cables are not connected correctly or
any cable is disconnected.
2) Parameter settings in the controller are
not correct or disagree with the
S8-series settings.
3) The MONITOUCH is faulty.
Solutions are:
1) Check the cable connection.
2) Recheck the parameter settings in the
controller.
3) Perform a self-loop test on the I/O Test
screen (page 5-13).
If the test is not successful, please return
MONITOUCH to your local distributor
immediately.
Communications have been
successful. However, opening a
certain page always causes a
“Communication Error: Error
Code received” error. The error code denotes a controller error
(NAK).
1) When the error code appears only on a
certain screen, a memory address that
does not exist on the controller may be
set on the S8-series screen.
2) When the error code appears at
power-on, the memory address set for
buffering area or initial macro or in the
[Read/Write Area] tab window ([System
Setting]
→
[Device Connection Setting])
may not exist in the controller.
1) Check if any address outside the
allowable range for controller memory is
set on the screen.
2) Check if the address set for buffering
area or initial macro or in the [Read/Write
Area] tab window ([System Setting]
→
[Device Connection Setting]) is outside
the allowable range for the controller
memory.
Communications have been
successful. However,
“Communication Error: Parity” or
“Communication Error: Framing”
suddenly occurs. Noise may cause the error. Check if appropriate measures are taken
against noise.
Example:
Check if communication and power cables
are bundled together.
Try to attach a ferrite core to the
communication cable.
Try to attach a noise filter to the power
supply, etc.