Welcome to the new Schneider Electric Community

It's your place to connect with experts and peers, get continuous support, and share knowledge.

  • Explore the new navigation for even easier access to your community.
  • Bookmark and use our new, easy-to-remember address (community.se.com).
  • Get ready for more content and an improved experience.

Contact SchneiderCommunity.Support@se.com if you have any questions.

Invite a Co-worker
Send a co-worker an invite to the Exchange portal.Just enter their email address and we’ll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel

[Imported] Modbus tcp conection too slow

Remote Operations Forum

Collaborate and share knowledge on the extensive range of remote systems and devices, including SCADA radios and RTUs, on the Schneider Electric Exchange Remote Operations (formerly SCADA & Telemetry) forum. From commissioning SCADA integration devices and software, to enhancing existing installations or troubleshooting, connect with a global community of experts and users. Subscribe today.

Janeway Janeway

[Imported] Modbus tcp conection too slow

>>Message imported from previous forum - Category:Communications Products <<
User: mchartrand, originally posted: 2018-10-25 17:37:56 Id:256
This is a re-posting from the obsoleted (October 2018) "Schneider Electric Telemetry & SCADA" forum.


In a project we should control 24 AC drive(VFD-B), 12 drives connect to one SE plc via modbus serial and other 12 drives connect to another SE plc via modbus serial and 2 SE plc's connect to one SA2 plc+Ethernet module via Data exchange which configured in Delta DCI-SOFT software, the registers and coils collect in master plc(SA2) and i can visit them in plc master(SA2) in WPL-SOFT(online mode) but we have a SCADA software from Schneider company clear SCADA and when we set scanners to tag collected data in clear SCADA for 6 drive every thing is normal but when we set more scanners,scanner stat change to offline we set 3 scanners for each drive and we have only 10 registers and 16 coil for each drive,my question is the problem is for master plc( DELTA DVP-SA2) or from SCADA?_**


My suspicion is that this is a Delta PLC issue, not allowing multiple TCP connections for the ModbusTCP sessions that you're launching.

If you only have a single Master ModbusTCP PLC, then you should only have one ModbusTCP Outstation (if using the Advanced Modbus driver).

If you're using the Simple Modbus driver, then you should only have one Scanner for the one Master ModbusTCP PLC.