WSAENOTSOCK 10038 error on polling with Modnet driver

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
  • Hi,

    I have 2 I/O Servers in single node, first server is working with OPC, second with Modnet. I tried a modification with one  I\O server, it doesn't help to solve a problem.I analyze communication with WireShark.  Modnet periodically trying to access register with 7255 address. Device don't have such address in his address space, so  generate error (illegal data address).

    I can't realize what happening with  device polling in this situation and why Modnet is trying to reach this address.

    Screenshots and Wireshark capture file in sharing link 

Reply
  • Hi,

    I have 2 I/O Servers in single node, first server is working with OPC, second with Modnet. I tried a modification with one  I\O server, it doesn't help to solve a problem.I analyze communication with WireShark.  Modnet periodically trying to access register with 7255 address. Device don't have such address in his address space, so  generate error (illegal data address).

    I can't realize what happening with  device polling in this situation and why Modnet is trying to reach this address.

    Screenshots and Wireshark capture file in sharing link 

Children
No Data