IAI R-unit RSEL, Instruction Manual, Page: 651 / 844

Chapter
11 T
roubleshooting
11.3 Error List
11-11
ME0392-4C
Error
No.
Error name Content and Cause / Countermeasure
Me
ssa
ge
227
Character string → value
conversion error warning
[Content & Cause]
1) Noise.
[Countermeasure]
1) Take a counteraction to noise
228
Command sum check
error (while receiving IAI
Protocol)
[Content & Cause]
1) The header in the received message is invalid. Invalid header position
(message is 9 bytes or less) is suspected, among other reasons.
2) Noise.
[Countermeasure]
1) Check the sending message in the destination of connection
2) Take a counteraction to noise
229
Command header error
(while receiving IAI
Protocol)
[Content & Cause]
1) The station number in the received message is invalid.
2) Noise.
[Countermeasure]
1) Check the sending message in the destination of connection
2) Take a counteraction to noise
22A
Command node address
error (while receiving IAI
protocol)
[Content & Cause]
1) The ID in the received message is invalid.
2) Noise.
[Countermeasure]
1) Check the sending message in the destination of connection
2) ake a counteraction to noise
22B
Received command data
error
[Content & Cause]
1) The received message does not match the message format or
contains invalid data.
2) Noise.
[Countermeasure]
1) Check the sending message in the destination of connection
2) Take a counteraction to noise
22C
Motor drive control error
[Content & Cause]
1) The power input to the motor exceeded the upper overload warning
load level
2) Sliding resistance on the actuator is to high.
[Countermeasure]
1) Revise the following items;
• Velocity setting
• Acceleration/deceleration setting
• Payload
• Setting in Driver Unit Parameter No. 143 “Overload Warning Load
Level Ratio” (when a number other than 100 is set)
2) If there is no problem with the payload, cut off the power and check
sliding resistance by hand
22D
Driver unit related error
[Content & Cause]
1) Driver unit failure
2) Noise.
[Countermeasure]
1) Replace driver unit
2) Take a countermeasure to noise
11.3 Error List
ME0392-4C
11-12
Error
No.
Error name Content and Cause / Countermeasure
Me
ssa
ge
22E
Power supply unit
communication error
[Content & Cause]
1) Contact error on connector of PSA-24 communication cable
2) Cable breakage on PSA-24 communication cable
3) Error in setting of number of connected units of PSA-24
4) Setting error on PSA-24 communication address switch (duplicated
with another device)
5) Noise applied to PSA-24 communication cable
6) Malfunction on SEL unit
7) PSA-24 unit malfunction
[Countermeasure]
1) Check PSA-24 communication cable connection status and connect
again
2) Replace PSA-24 communication cable
3) Check the setting of the number of connected units in XSEL PC
software
4) Change the setting to avoid duplication to other devices
5) Take a countermeasure to noise on PSA-24 communication cable
(such as installing ferrite core)
6) REPLACE SEL UNIT
7) Replace PSA-24 unit
22F
Coordinate system type #
specification error
[Content & Cause]
1) A wrong number (other than 2) was indicated when indicating the
coordinate system type in Protocol B
0: Work Coordinate System, 1: Tool Coordinate System
2) Malfunction on SEL unit
[Countermeasure]
1) Check the sending message and indicate the number correctly
2) Replace SEL unit
230
Simple interference
check zone error
[Content & Cause]
1) A simple interference check zone number out of the range (number out
of 1 to 10) was indicated in IAI Protocol
[Countermeasure]
1) Check the sending message and set the simple interference check
zone number in the range.
231
Simple interference
check zone entry
detection
[Content & Cause]
1) The specified number of simple contact check zone data is invalid.
[Countermeasure]
1) Change the operation conditions or operation patterns to avoid irruption
to the simple interference check zone
232
Monitor/write prohibited
address area incorrect
access error
[Content & Cause]
1) Direct writing was conducted to the monitoring / writing prohibited
address domain
2) Direct monitoring was conducted to the monitoring / writing prohibited
address domain
[Countermeasure]
1) Do not attempt to conduct the direct writing to the monitoring / writing
prohibited address domain
2) Do not attempt to conduct the direct monitoring to the monitoring /
writing prohibited address domain