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.
Released for: Schneider Electric Canada
Need help?
Product Selector
Quickly and easily find the right products and accessories for your applications.
Get a Quote
Start your sales inquiry online and en expert will connect with you.
Where to buy?
Easily find the nearest Schneider Electric distributor in your location.
Help Center
Find support resources for all your needs, in one place.