ABB FENA-11 User Manual

328 PROFINET IO – Communication protocol
 Header and frame structures
PROFINET IO uses the DCE RPC (Distributed Computing
Environment Remote Procedure Call) protocol for acyclic read and
write services. I/O controllers and supervisors take care of
formulating most of the request frames. However, it is possible that
handling the PROFIdrive request and response headers must be
performed in the application logic. The acyclic frame structure,
headers and error codes are described further below.
Dest addr. and Src addr. are the destination and the source of the
communication relationship. The addresses are in hexadecimal
format, for example, 00-30-11-02-57-AD.
Ether type is 0x800 for non-real-time communication.
IP and UDP fields contain the IP address of the source and the
destination as well as the communication ports and length of the
message.
RPC contains, for example, the read or write service ID, interface
description and selected objects.
NDR request block describes the length of the following data block.
The response block also contains bytes ErrorCode, ErrorDecode,
ErrorCode1 and ErrorCode2 for presenting the status of the
request. The response error codes are listed in the table below.
Frames Dest
addr.
Src
addr.
Ether
type
IP
UDP
RPC NDR Read
or
Write
Data
Bytes 6 6 2 28 80 20 64 …
Byte Value and meaning
ErrorCode 0xDF (Error Write)
0xDE (Error Read)
ErrorDecode 0x80 (PNIORW) ErrorCode1 decoded as shown in section
ErrorCode1 on page 329. ErrorCode2 is 0.
0x81 (PNIO) ErrorCode1 and ErrorCode2 decoded as
shown in section ErrorCode1 on page 329.
ErrorCode1 Error class and error code. See section ErrorCode1 on
page 329.
ErrorCode2 Not described here

ABB FENA-11 Specifications

General

Brand	ABB
Model	FENA-11
Category	Adapter
Language	English