7
Ethernet Industrial Protocol (EtherNet/IP™)
Return codes for parameterization via "explicit messages"
Manual – MOVIPRO
®
with EtherNet/IP™ or Modbus/TCP Fieldbus Interface
85
7.5 Return codes for parameterization via "explicit messages"
If a parameter request via "explicit messages" fails, you can determine the cause via a
fault code.
An error is generated as follows:
• By EtherNet/IP™ master
EtherNet/IP™-specific return codes are returned in the error telegram if the data
format is not maintained during the transfer or if a service is performed that has not
been implemented.
Coding of the EtherNet/IP™-specific return code is described in the following
chapter: "General error codes"(→287). For further information about the Ether-
Net/IP™-specific return codes, refer to the EtherNet/IP™ specification.
The "General Error Code" of a manufacturer-specific return code is 1F
hex
.
• By EtherNet/IP™ slave
The return codes that are returned from the EtherNet/IP™ slave or lower-level
devices due to faulty parameterization are described in the following chapter:
"MOVILINK
®
-specific return codes"(→288).
• Due to timeout
The timeout behavior is described in the following chapter: "Timeout response of
"explicit messages""(→289).
The general error code (ERR) and the additional code (EXERR) can be read out from
the status registers of the message tags:
14310226443
[1] General Error Code (ERR): Value 16#001f
[2] Additional Code (EXERR): Value 16#0000_0810
The return codes are returned in the following format:
Byte offset Function Example: Parameter response telegram
0 General Error Codes
1F
hex
Vendor-specific
1
Additional code
Length (words)
01
hex
Only low word (word1)
2
Additional code
Word 1 (low byte)
10
hex
MOVILINK
®
Additional Error Code
16998413/EN – 12/2016