Error Histories - Omron FQ2-S/CH Series User Manual

8-1

Error Histories

FQ2-S1 FQ2-S2
Error histories are stored with the PC Tool and in the Sensor and in the Touch Finder.
Up to 100 errors will be stored in the error history in the Sensor or Touch Finder.
Errors Stored in the Error History
Error in error history
TRIG Input Error
(Error code: 01040302)
IN Input Error
(Error code: 11020900)
Scene Data Error
(Error code: 01030800)
Model Error
(Error code: 01050405 or
01050500)
Logging Error
(Error code: 02160702 or
02160703)
Communication error
(Error code: 01010100)
EtherNet/IP communica-
tions error (Error code:
01010101)
Output buffer error
(Error code: 01010701)
SD card output error
(Error code: 01050300)
Note: If an error that is indicated by this icon occurs, the ERROR operation indicator will light and the ERROR signal will turn ON.
Note
You cannot check the error codes from the Touch Finder. Use the command to acquire the most recent error infor-
mation for the connection method.
FQ2-S/CH Series User's Manual for Communications Settings (Cat. No. Z338)
296
Error Histories
FQ2-S3 FQ2-S4 FQ2-CH
Cause
A TRIG signal was input when
the BUSY signal for Sensor
measurement was ON.
A no-protocol command or PLC
link command was input when
the BUSY signal was ON.
The scene data to switch to is
corrupted.
A model was re-registered with
an image with low contrast.
Some data was not saved when
logging data to files on an SD
card.
After EtherNet/IP communica-
tion or PROFINET communica-
tion was established, normal
communication could not be
performed.
A timeout occurred in process-
ing to output the measurement
results via EtherNet/IP, PROFI-
NET.
An output data buffer overflow
occurred during output process-
ing of measurement results for
PLC Link or EtherNet/IP,
PROFINET.
A write to the SD card failed.
An attempt was made to save
more data than the available
space on the SD card.
Points to check
• Check the program in the PLC
or other host to see if an inter-
lock or similar measure has
been implemented.
• If a relay or other device with
contacts is being used as the
input device, see if chattering
has occurred.
• Is an interlock or other counter-
measure provided, e.g., in a
ladder program in the PLC?
---
Check the image to see if the
contrast is too low to register the
model.
Check to see if the BUSY output
parameter is set to Measurement.
Check to see if communications
were cut off with the data link
partner device and to see if a
cable is broken.
Make sure that handshake pro-
cessing is being performed by the
master. Also, make sure that the
measurement interval is long
enough.
• Check the measurement inter-
val to see if it is long enough.
• Make sure that handshake pro-
cessing is being performed by
the master.
Check to see if the SD card is
locked. Check to see if there is
sufficient space available on the
SD card.
Measures to perform
• Program interlocks to control
the TRIG so that they do not
turn ON while the BUSY signal
is ON.
• Switch from a device with con-
tacts (e.g., relay) to a device
without contacts (e.g., SSR or
PLC transistor output).
• Program interlocks, such as in
a ladder program, so that no-
protocol commands and PLC
link commands are not input
while the BUSY signal is ON.
The scene data to be switched
to is corrupted.
Reset the scene data from the
beginning.
Increase the image contrast and
try again to register the model.
Set a sufficiently long measure-
ment interval or set the BUSY
output condition to [Data logging]
or [Image logging].
Check the cable connection to the
data link partner device.
Check the measurement interval
and handshake processing.
Change the timeout time so that it
is suitable for the ladder program
processing time.
Check the measurement interval
and handshake processing.
Unlock the SD card. Delete
unnecessary files from the SD
card.
FQ2-S/CH User's Manual