Resolving the 'Slave Application Error' on the NX-ECC
The 'Slave Application Error' on the NX-ECC can have various causes. One common reason is an inconsistency between the software and hardware NX-IO configuration—including NX Safety IO. As a result, users may find that simply power cycling the system or executing a general error reset does not clear the error.
Fortunately, there is a solution to remove the 'Slave Application Error' message and restore the coupler to normal operation.
Due to an inconsistency between the software and hardware configuration the NX-ECC may contain the ‘Slave Application Error’. The error message can be read from Sysmac Studio and shows the following error message:

Resetting the Error
Normally, errors can be cleared by using the ‘Reset All’ button in Sysmac Studio. However, it's important to first resolve the root cause before attempting a reset. For example, in the case of a configuration mismatch, the software configuration must be corrected to match the actual hardware setup. Once corrected, download the updated configuration to the master.
If the error persists after correcting the configuration and performing a reset, proceed with the 'Clear All Memory' procedure to fully reset the NX-ECC and its connected NX Units.
1. Open the ‘EtherCAT’ tab via the ‘Configurations and Setup’ menu.

2. Select ‘Edit Slave Terminal Configuration’ for the designated NX-ECC to open the configuration window of the slave device.

3. Select ‘Clear All Memory’.

4. Select ‘Coupler + NX Units’ and press the execute button. The NX-ECC shall be initialized to default settings and the ‘Slave Application Error’ is removed.

The ‘Clear All Memory’ cannot be executed while working offline. Please go online directly onto the coupler or via the NJ using Sysmac Studio.