WAGO 2789-9023, Manual

Page: 26 / 94

2789-9023 Fieldbus Description
26 Product manual | Version: 1.0.0
EtherNet/IP Communication Module
4.2.2.2 General Services
This object supports the following common services.
Table 20: Common Services
Service Code Service Available Service Name Description
Class Instance
0x0E Yes Yes Get_Attribute_All Returns the content of all attributes
0x10 No Yes Get_Attribute_Single Returns the content of the respec-
tive attribute
4.2.3 Connection Object
Because the connections are established and terminated via the Connection Manager,
the class and instance attributes of this object (class 0x05) are not visible.
4.2.4 Connection Manager Object
The Connection Manager object (Class 0x06) provides the internal resources required for
the input and output data and explicit messages. In addition, this object is responsible for
managing these resources. For each connection (input and output data or explicit data),
another instance of the Connection class is created. The connection parameters are ex-
tracted from the “Forward Open” service, which is responsible for establishing a connec-
tion.
The following services are supported for the first instance: Forward_Open, Uncon-
nected_Send and Forward_Close.
No class and instance attributes are visible.
4.2.5 TCP/IP Interface Object
The TCP/IP Interface object (Class 0xF5) provides for the configuration of the TCP/IP
network interface. Examples of configurable objects include the IP address, the network
mask and the gateway address of the product.
The underlying physical communication interface linked to the TCP/IP interface object
can be any interface supported by the TCP/IP protocol. Examples of components that
can be linked to a TCP/IP interface object include the following: an Ethernet 802.3 inter-
face, an ATM (Asynchronous Transfer Mode) interface or a serial interface for protocols
such as PPP (Point-to-Point Protocol). The TCP/IP Interface object provides an attribute,
which is identified by the link-specific object for the connected physical communication in-
terface. The link-specific object should typically provide link-specific counters, as well as
any link-specific configuration attributes.
Each device must support exactly one instance of the TCP/IP Interface object for each
TCP/IP-compatible communication interface.
4.2.5.1 Instances
Table 21: TCP/IP Interface Object – Instance 0
Attribute
ID Access Name Data type Description Factory setting
1 Get Revision UINT16 Version of this object 4
2 Get Max Instance UINT16 Maximum number of instances 1