３ Introduction The NJ/NX troubleshooter has the ability to monitor and reset the following events that are monitored with the NJ/NX event function on the NA screen; events occurred in the Controller, events defined to the Controller by the user, and these event logs. The troubleshooter has the following main functions. Monitors and resets events (active events). Monitors and clears event logs. Moves to the NA user page associated with user error. Ｃ aptures the page for active events/event logs. Outputs event logs in CSV file. ３ - １ Architecture You can check the active errors and event logs with the NJ/NX troubleshooter.
1 ． Controller error, Controller information This is an error or information that is monitored by the NJ/NX-series Controller. This can not be edited by the user. You can monitor errors in the CPU Unit, NX slave terminal, EtherCAT slave, and CJ Unit on the NA screen. ２． User error, User information This is an error or information that can be difined by the user with the Sysmac Studio. Detailed Information such as a troubleshooting method can be set. You can monitor user errors that are generated with “instruction to generate user errors (SetAlarm)”.
You can monitor user information that is generated with “instruction to generate user information (SetInfo)”, but only as an event log (be discussed later). The Sysmac Studio is used to set user errors/user information (refer to Section 8-1). User errors can be transferred to the associated NA user page with the Sysmac Studio (same as NS function). ３． Controller event log, User event log You can monitor the occurred controller error/controller information as a controller event log. You can also monitor the occurred user error/user information as a user event log. These event logs are retained until the user clears the logs or memory.
If the number of logs exceeds the maximum limit, the oldest log will be cleared. 9