Support forum for Schneider Electric SCADA systems, radios and RTUs. From commissioning integration devices and software, to enhancing existing installations or troubleshooting.
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send InviteCancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2019-11-0501:41 PM
[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.
_______
**_Peman1365: 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?_**
_______
bevanweiss: 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.