Download  Print this page

Method For Checking Error Codes - Mitsubishi Electric NZ2GN2B1-32D User Manual

Programmable controller cc-link ie tsn remote i/o module.
Hide thumbs

Advertisement

11.6

Method for Checking Error Codes

Error codes can be checked by any of the following methods:
• Checking with the engineering tool
• Checking by Error code (RWr1)
Checking with the engineering tool
The error history held in the I/O module can be read. Errors that occurred before powering-off can be checked as well.
The error history can be checked by using CC-Link IE TSN/CC-Link IE Field diagnostics.
• The error history records a maximum of 16 errors in reverse chronological order of occurrence. If more than
16 errors occur, errors are deleted from the oldest.
• If the same error occurs continuously, only the error that occurred first is stored to the error history.
• The error history is stored in the non-volatile memory in the I/O module. It is not lost when the power is cut
off. However, when the upper limit for the number of writes to the non-volatile memory is reached, the error
history cannot be stored in the non-volatile memory.
• "Occurrence Date" information in the error history is recorded after clock information is distributed from the
master station. When an error occurs before clock information is distributed from the master station,
"Occurrence Date" information is not recorded.
■Checking by using CC-Link IE TSN/CC-Link IE Field diagnostics
Operating procedure
1.
Connect the engineering tool to the CPU module.
2.
Start CC-Link IE TSN/CC-Link IE Field diagnostics from the menu.
[Diagnostics]
[CC-Link IE TSN/CC-Link IE Field Diagnostics]
3.
Right-click the slave station whose error history you want to check, and select "Error History".
4.
Follow the on-screen instructions and click the [Yes] button.
5.
The error history appears.
11 TROUBLESHOOTING
11.6 Method for Checking Error Codes

Advertisement

Table of Contents

   Related Manuals for Mitsubishi Electric NZ2GN2B1-32D

Comments to this Manuals

Symbols: 0
Latest comments: