7-6
Troubleshooting
7-1-3 Error code list
Code (hexadecimal) Message
Conditions
Procedure
1000
No Service generated
in ISDU handling
This occurs when the start code of
the ISDU handling response used to
access the parameters of the IO-Link
GHYLFHLV³´1R6HUYLFH
A setting value that is not supported by
the IO-Link device is being accessed
LQWKLVFDVH&RQ¿UPZKDW\RXDUH
WU\LQJWRDFFHVVLQGH[QXPEHUHWF
1001
IO-Link
communication has
stopped
This occurs when communication is
established with an IO-Link device
but then is disconnected.
This error does not occur if the I/O
power supply is shutdown. The error
is also automatically cleared if IO-
Link communication is restored.
Check the wiring between the IO-Link
device and this product. Check the
,2SRZHUVXSSO\&RQ¿UPZKHWKHU
the issue is resolved after changing
the connection to another channel for
this product or replacing the IO-Link
device and cable.
1100
Timeout generated in
ISDU handling
When using ISDU handling to access
an IO-Link device setting value, no
ISDU handling response is received
HYHQDIWHU¿YHVHFRQGVKDYHSDVVHG
&RQ¿UPZKDW\RXDUHWU\LQJWRDFFHVV
RQWKH,2/LQNGHYLFHLQGH[QXPEHU
write data, etc.).
Checksum error
generated in ISDU
handling
When using ISDU handling to access
an IO-Link device setting value, a
mismatch occurs when calculating
the checksum of the ISDU handling
response.
This could be caused by noise between
the IO-Link device and this product.
Resolve this through such means as
using a separate conduit for the power
line, or maintaining distance between
the C/Q wires of other IO-Link devices
GRQRWEXQGOHZLUHVWRJHWKHU&RQ¿UP
that the cable between the IO-Link
device and this product is not too long
RYHUP
Unregulated ISDU
handling data length
This occurs when the data length of
the ISDU handling response is either
³´RUWRRORQJZKHQXVLQJ,6'8
communication to access an IO-Link
device setting value.
Revision ID validation
error
The revision ID registered in this
product does not match the revision
ID of the connected IO-Link device.
Process data is not transferred and
parameters are not accessed.
Change the setting value for device
YDOLGDWLRQVHWWLQJYDOXHQXPEHU
0WR³1RQH´
8033
Setting value is too
long
This occurs when the data length is
too long, when using ISDU handling
to access an IO-Link device setting
value.
Write data using the data length
VSHFL¿HGIRUWKH,2/LQNGHYLFH
FF23
Storage data does not
match the connected
device vendor ID or
device ID
This occurs when the value of the vendor
ID or device ID of the connected IO-Link
GHYLFHGLႇHUVIURPWKHVWRUHGVWRUDJH
GDWDZKHQGHYLFHYDOLGDWLRQVHWWLQJ
YDOXHQXPEHU0LVVHWWR³1RQH´DQG
VWRUDJHGDWDH[LVWVKRZHYHUWKLVRQO\
occurs when power is turned ON).
If an IO-Link device with a vendor ID or
GHYLFH,'WKDWGLႇHUVIURPWKHVWRUDJHGDWDLV
connected, connect the correct IO-Link device.
If it is safe to delete the storage data stored
on this product by channel, write with device
SDUDPHWHUEDFNXSUHVWRUHVHWWLQJYDOXH
QXPEHU0VHWWR³'HOHWH´
FF24
6WRUDJHEXႇHU
overload
This occurs when setting value data
is too long and cannot be stored,
when backing up parameters from an
IO-Link device.
The data length stored during backup
ZLOOEH³E\WHVLQGH[PRGHO
name) number of parameters
to backup × 4 + total data length of
SDUDPHWHUVWREDFNXS´7KLVFDQEH
stored as long as it is 4,032 bytes or
less.
Backup cannot be performed for the
connected IO-Link device because
the storage data is too large.
Ramco Innovations www.optex-ramco.com (800) 280-6933