Omron NX701-17 Series User Manual page 205

Event name Input Process Data Invalid Error
Meaning Because the EtherCAT master could not perform process data communications normally when it was in the Opera-
tional state, the Input Data Invalid state continued for the following period.
• When the task period is 10 ms or shorter: 100 ms
• When the task period is longer than 10 ms: 10 periods of the task
Source EtherCAT Master Function Module
Error attributes Level
Effects User program
Indicators EtherCAT NET RUN
---
System- Variable
_EC_IndataInvalidErr
defined variables
_EC_InDataInvalid
_EC_InData1Invalid
_EC_InData2Invalid
Cause and Assumed cause
correction
Hardware failure of EtherCAT slave
Noise
Attached Attached information 1: System-defined variables that changed to TRUE for a certain period. The value is 1 for a sys-
information tem-defined variable that changed to TRUE for a certain period.
Precautions/ None
Remarks
*1 This event code occurs for unit version 1.13 or later of the CPU Unit.
NJ/NX-series CPU Unit Built-in EtherCAT Port User's Manual (W505)
Source details
Minor fault Recovery
Continues. Operation
EtherCAT NET ERR
Flashes at 1-s intervals.
Data type
BOOL
BOOL
BOOL
BOOL
Correction
While disconnecting the slaves from
the network one by one, correct the
error until the _EC_InDataInvalid
(Input Data Invalid), _EC_InData1In-
valid (Input Data1 Invalid), and
_EC_InData2Invalid (Input Data2
Invalid) system-defined variables
change to FALSE. When any of these
variables changes from TRUE to
FALSE, the slave disconnected at
that time is considered as failed.
Replace the slave.
In addition, program the _EC_InData-
Invalid (Input Data Invalid), _EC_In-
Data1Invalid (Input Data1 Invalid),
and _EC_InData2Invalid (Input Data2
Invalid) system-defined variables as
an interlock condition in the user pro-
gram to ensure that invalid input data
does not cause unexpected opera-
tion.
Check the number of error frames in
the slave diagnostic and statistical
information. It is considered that the
slave was affected by noise in each
location where an error frame was
counted. Implement appropriate noise
countermeasures for all locations
considered to be affected by noise.
Then, make sure that error frames
are no longer counted in the slave
diagnostic and statistical information.
1st bit from the least-significant bit: _EC_InDataInvalid (Input Data Invalid), _EC_InData1Invalid
(Input Data1 Invalid)
2nd bit from the least-significant bit: _EC_InData2Invalid (Input Data2 Invalid)
9 Troubleshooting
Event code
842F0000 hex
Master Detection
timing
Error reset Log category
Not affected.
EtherCAT LINK/ACT
---
Name
Input Process Data Invalid Error
Input Data Invalid
Input Data1 Invalid
Input Data2 Invalid
Prevention
None
If error frames are still counted in the
master diagnostic and statistical infor-
mation, before you start operation,
remove the noise source or imple-
ment noise countermeasures while
checking the slave diagnostic and
statistical information.
*1
During communi-
cations
System
9
9-35