• Replies 7 replies
  • Subscribers 582 subscribers
  • Views 534 views
  • Users 0 members are here
Options
Related

WSAENOTSOCK 10038 error on polling with Modnet driver

MaratAbdullin5422

Hi,

we have a problem with connecting Citect with generic modbus device (standalone discrete I / O Module)

through Modnet driver. After Runtime restart we have a error WSAENOTSOCK 10038 error (syslog.IOServer.Cluster_1.IOServer_2 log file).

 After a few minutes connection is restored and system is working fine until next restart.

Connection parameters in .ini file:  MaxPending=2, Block=250, Retry=0, Delay=0, Timeout=1000, PollTime=0, WatchTime=30000.

Modbus Pool with this device works without problem. 

We are using  Version 7.50 Service Pack Patch 13[5].

Log in included file 

citect_logs.txt

Thanks.

Parents
  • I do see a pattern in your log file: the error seems to occur every 30 seconds, which corresponds to the WatchTime period. Are you communicating from a single Citect node? Or do you have a redundant setup (2 I/O servers)?

    It might be that the Modbus device is closing the TCP channel while Citect is still trying to communicate. You might be able to tell something more after analyzing the connection with WireShark.
Reply
  • I do see a pattern in your log file: the error seems to occur every 30 seconds, which corresponds to the WatchTime period. Are you communicating from a single Citect node? Or do you have a redundant setup (2 I/O servers)?

    It might be that the Modbus device is closing the TCP channel while Citect is still trying to communicate. You might be able to tell something more after analyzing the connection with WireShark.
Children
No Data
© 2025 AVEVA Group Limited or its subsidiaries. All Rights Reserved.