NJ301 slave issue
Resolve error code:
Slave Application Error (84280000 hex) event
Slave Initialization Error (84230000 hex) event
Summary/Issue Description
This note addresses some of the most common errors that can occur in an EtherCAT master-slave network.
Root Cause
The following errors may occur when the slave enters to the Safe-Operational state.
• Slave Application Error (84280000 hex) event
• Slave Initialization Error (84230000 hex) event
• Slave State Transition Failed (84300001 hex) event
• Slave AL Status Error Detected (84360000 hex) event
Solution
Power down and re-seat the NX modules since vibration may have caused them to separate from the din rail. Then Compare and Merge again to see if configuration has changed.
Implement the following part of code, using functions :
GetECError
ResetECError
Date/Revision History
First review 08/22/2024.
2nd review 01/10/2025 v1.1
Author:
Javier Romo, Technical Support Engineer.
References
NJ/NX series CPU Unit Built-in EtherCAT Port User’s Manual (W505-E1-25)
https://edata.omron.com.au/eData/NJ/W505-E1-25.pdf
NJ/NX Series Troubleshooting Manual (W503-E1-27)
https://edata.omron.com.au/eData/NJ/W503-E1-27.pdf
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article