• Replies 7 replies
  • Subscribers 582 subscribers
  • Views 539 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
  • Without having looked at your attachments yet, I can explain why Modnet tries to read other registers than you have configured.
    Modnet (and all other modbus drivers in Citect too) tries to read modbus registers in blocks to increase performance.
    With most brands of PLCs this is no problem because all addresses exist in PLC memory, but with some brands, especially with some RTU brands, only the configured addresses exist in the device, so you get an illegal data address error.

    To prevent Citect reading addresses in blocks, you should prefix all modbus addresses with the capital letter 'G' in your variable tag definitions. Examples: G7254 or G401190.
Reply
  • Without having looked at your attachments yet, I can explain why Modnet tries to read other registers than you have configured.
    Modnet (and all other modbus drivers in Citect too) tries to read modbus registers in blocks to increase performance.
    With most brands of PLCs this is no problem because all addresses exist in PLC memory, but with some brands, especially with some RTU brands, only the configured addresses exist in the device, so you get an illegal data address error.

    To prevent Citect reading addresses in blocks, you should prefix all modbus addresses with the capital letter 'G' in your variable tag definitions. Examples: G7254 or G401190.
Children
No Data
© 2025 AVEVA Group Limited or its subsidiaries. All Rights Reserved.