68
4. MSEL
4.7 Troubleshooting
1) In case it is not possible to connect the network, check the current condition on the display of monitoring
LEDs of DeviceNet Board. [Refer to Section 4.2]
Check the settings of the MSEL and the settings of the master unit referring to the instruction manuals of
the master unit.
2) When an alarm is issued, an alarm code gets output to the panel window.
(1) Find the alarm code that you see on the window from the alarm code list shown below.
Deal with it based on the description for the alarm code in question.
(2) In case the alarm code is not found in the following list, search in the alarm contents list contained in
MSEL Instruction Manual. Deal with it based on the description for the alarm code in question.
Alarm Code (Fieldbus related items are chosen below)
No.
Error name
Contents and Treatment
A6B Fieldbus error
(FBRS link error)
MSEL starts up faster than the host (master unit).
Change the setting in I/O Parameter No. 121 Bit 16 to23 to have the
time extended before timeout.
D56 Fieldbus error
(MinACK Timeout)
A communication error was detected.
Check the condition of PLC, and reboot the MSEL
unless there is an error. If the same error occurs again,
please contact us.
D59 Fieldbus error
(DPRAM writing and reading)
The writing and reading error was detected in the internal
memory.
MSEL reboot the controller. If the same error
occurs again, please contact us.
D5A Fieldbus error
(TOGGLE Timeout)
A communication error was detected.
MSEL reboot the controller. If the same error
occurs again, please contact us.
D5B Fieldbus error
(Access right retry over)
A communication board error was detected.
MSEL reboot the controller. If the same error
occurs again, please contact us.
D5D Fieldbus error
(FBRS link error)
This occurs when the network connection is not established.
1) Check the station number, the parameters for communication speed
and parameters on higher-order side.
2) It is concerned the startup of MSEL is faster than that of PLC.
Change the settings in I/O Parameter No. 121.
[Refer to Section 4.4 [7] for the details.]
D5E Fieldbus error
(Mail BOX response)
A communication error was detected.
Reboot the MSEL. If the same error occurs again,
please contact us.
D5F Network I/F Module Class Mismatch
Error
The setting of I/O Parameter No. 225 Network I/F Module
Class does not match with that of the communication board
mounted.
Check the contents of the settings in I/O Parameter No. 225, and in
case no doubt is found, please contact us.
D75 Fieldbus Parameter Error
There is an error in a parameter.
Check I/O Parameter No. 226, 227 and 237, 238.
Example) • A node address out of the range was set.
•
A communication speed out of the range is set.
D76 Fieldbus Module Unmounted Error
DeviceNet board is not mounted.
D77 Fieldbus error (Exception)
A communication board error was detected.
Reboot the MSEL. If the same error occurs again,
please contact us.
E1F I/O Assignment Parameter Error
It is a parameter setting error.
Check to see that a number out of the I/O port number (except for -1)
is not set to I/O Parameters No. 2 to 9, a number out of indication is
not input to I/O port start number, or a number out of indication is not
input to I/O Parameters No. 14 to 17.
[Refer to MSEL Instruction Manual.]
Summary of Contents for DeviceNet MSEL Series
Page 1: ...Operation Manual Twenty Fourth Edition XSEL TT MSEL TTA SSEL SCON C ASEL E Con PSEL RCS C ...
Page 2: ......
Page 16: ...8 8 ...
Page 93: ...85 5 Tabletop Robot TTA 㻌 ...
Page 142: ...134 ...
Page 143: ......