Troubleshooting, In the event of an error, Probable symptoms – Fuji Bikes FEH381 User Manual

Page 117: Troubleshooting -5, In the event of an error -5 probable symptoms -5

Advertising
background image

7

2. Troubleshooting

7-5

Error Co

rrecti
on

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 POD model, serial number, symptom of
the error, error message (if shown), etc.

Probable Symptoms

Symptom

Cause

Solution

POD is connected to the
PLC; however,
communication fails.
“Communication Error:
Time-Out” appears on the
screen.

Probable causes are:

Solutions are:

1) Cables are not connected correctly or any

cable is disconnected.

1) Check the cable connection.

2) PLC parameter settings are not correct or

disagree with the POD settings.

2) Recheck the PLC parameter settings.

3) The POD is faulty.

3) Perform a self-loop test on the “I/O Test”

screen (page 6-7).
If the test is not successful, please return
the POD 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 PLC error (NAK).

1) When the error code appears only on a

certain screen, a memory address that
does not exist on the PLC may be set on
the POD screen.

1) Check if any address outside the allowable

range for PLC memory is set on the screen.

2) When the error code appears at power-on,

a memory address that does not exist on
the PLC may be set for communication
parameters, buffering area, initial macro,
etc.

2) Check if any address outside the allowable

range for PLC memory is set for
communication parameters, buffering area,
initial macro, etc.

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.

Advertising
This manual is related to the following products: