Communication Protocols
Copyright IXXAT Automation GmbH
104
IEM Manual, 1.5
5.2.6 Class 1 and class 3 connection handling
By registering EtherNet/IP specific events via the EMI_evtEventRegister()
function the host is capable of monitoring class 1 and class 3 EtherNet/IP con-
nections. The following indications / events are discussed in this section:
COM_k_EIP_CONNECTION_ESTABLISHED
Class3 connection established
COM_k_EIP_CONNECTION_CLOSED
Connection closed (class1/3)
COM_k_EIP_CONNECTION_TIMEOUT
Connection went into timeout (class1/3)
Additionally, to control incoming class1 ForwardOpen messages the Forward-
Open
verification
feature
can
be
unlocked
by
issuing
a
COM_k_EIP_VERIFY_CONNECTION
service request using the EMI_srvreqSend() func-
tion.
COM_k_EIP_VERIFY_CONNECTION
ForwardOpen verification (class1 only)
5.2.6.1 ForwardOpen verification
By issuing a
COM_k_EIP_VERIFY_CONNECTION
service request using the
EMI_srvreqSend() function, the host can control the acceptance or rejection of
incoming class 1 connection requests. After issuing this service request, the
host must check for
COM_k_EIP_CONNECTION_INFO
i
ndications. The indication’s
parameter holds the structure
COM_t_EIP_CONNECTION_INFO
which contains all
information of the received ForwardOpen request. This includes e. g. the re-
quested RPI or connection point as well as the configuration assembly data if
originally included in the ForwardOpen request. Possible use cases for this
feature would be e.g. the connection point specific acceptance of Run/Idle
headers or the validation of configuration data.
The host can then accept or reject the request generating a
COM_k_EIP_ACCEPT_CONNECTION
confirmation. This confirmation must include the
COM_t_EIP_ACCEPT_CONNECTION
structure with a General- and Extended Error
stating the reason for rejection of the connection and the connection ID re-
ceived with the
COM_k_EIP_CONNECTION_INFO
indication.
FordwardOpen requests which are unacceptable by reasons known to the
EtherNet/IP stack (e.g. containing not existent connection points/assemblies)
will not generate a
COM_k_EIP_VERIFY_CONNECTION
event but are rejected silently.
5.2.6.2 Connection established
As class 3 ForwardOpen requests are not covered by the method discussed in
section 5.2.6.1, the host can keep track of established class 3 connections via
the
COM_k_EIP_CONNECTION_ESTABLISHED
indication event. The host cannot reject
these connections.
An event handler can be registered for this event using the
EMI_evtEventRegister() function.