My EtherNet/IP adapter stops communicating when scanned by M241/M251
M241/251 opens 1 connection to check adapter identity and a second one for implicit exchanges.
The first connection is closed after 40 seconds as identity does not need to be checked continuously.
On some adapters (like ATV71 EtherNet/IP card VW3A3316), this first connection closure causes communication interruption of the second connection, too.
A workaround is to keep the first connection open by sending GetAttributeSingle requests for example every 5 seconds.
This can be done using function block EipDataExch from the EtherNet/IP Scanner library.
i_xMsgType input should be TRUE to use connected mode.
The first connection is closed after 40 seconds as identity does not need to be checked continuously.
On some adapters (like ATV71 EtherNet/IP card VW3A3316), this first connection closure causes communication interruption of the second connection, too.
A workaround is to keep the first connection open by sending GetAttributeSingle requests for example every 5 seconds.
This can be done using function block EipDataExch from the EtherNet/IP Scanner library.
i_xMsgType input should be TRUE to use connected mode.
Gepubliceerd voor: Schneider Electric Belgium
Hulp nodig?
Selecteer zelf het juiste product
Vind snel en eenvoudig de juiste producten en toebehoren voor uw toepassingen.
Offerte aanvragen
Dien uw aanvraag online in en een expert zal contact met u opnemen.
Verkooppunten
Vind eenvoudig de dichtstbijzijnde distributeur van Schneider Electric op uw locatie.
Help Center
Vind de antwoorden die u nodig heeft via bladeren door veelgestelde vragen over onderwerpen.