It's your place to connect with experts and peers, get continuous support, and share knowledge.
Contact SchneiderCommunity.Support@se.com if you have any questions.
A support forum for AVEVA Plant SCADA (formerly Citect SCADA). Share new and exciting product information, connect, learn, and collaborate with the ecosystem of Plant SCADA Users. AVEVA Plant SCADA a reliable, flexible and high-performance Supervisory Control and Data Acquisition software solution for industrial process customers. This forum is to connect, share, learn and collaborate new and exciting product information. Feel free to join and share to your Ecosystem of Plant SCADA Users.
You can subscribe to this forum after you log in or create your free account..
Posted: 2021-01-21 05:43 AM
I'm working with Citect 2016 (update 38).
We need to establish a Modbus TCP communication with a PLC in plant. Nevertheless, the SCADA never gets to communicate to this PLC. After running many tests, we found out that the SCADA never sends any kind of request to the mentioned PLC (we used wireshark). In order to rule out any kind network problem, we run a ModbusTCP Server in a PC which was at reach of the SCADA, but the results were the same. After that we proceed to create an empty new project pointing just to the same testing ModbusTCP Server. But to our surprise, it worked perfectly well, even though the parameters (port, protocol, device, variable addresses) were the same as the ones in our original project.
It is the first time something like this happend to us. We have many Schneider M340 using ModbusTCP without any kind of problems.
Any ideas?? Thanks in advance
Posted: 2021-01-21 05:42 PM
This section of the Community website is for the ClearSCADA / GeoSCADA product. For CitectSCADA / Plant SCADA product discussions try https://community.exchange.se.com/t5/Industry-Automation-and-Control/bd-p/industry-automation-contro...
Someone here might know, but you'll have more success at the Automation and Control section.
Posted: 2021-01-22 03:11 AM
Yes, you're totally right.
The new project has only one device, which is the pc running the testing ModbusTCP server. With this simple configuration, the project is able to reach the test pc.
On the other hand, when the parameters of the pc are loaded to the original project, citect doesn't even send a modbus tcp frame to request data to this device, even when the parameters (device, port, protocol) are the same.
We're completely lost because we have many Schneider M340 running in plant with ModbusTCP without any issues.
Posted: 2021-01-25 03:50 AM
.... i have addressed that in https://community.exchange.se.com/t5/Industry-Automation-and-Control/Citect-2016-ModbusTCP-communica...
Did it work ?
Posted: 2021-01-26 03:12 AM
It's a good guess. But it's not the case either. We run a a ModbusTCP client to simulate the SCADA on a computer to poll the remote device(PLC). The PLC always sent a response back. We did this first to make sure the PLC was working well but at the same time we checked the network