PLC and field instruments are working fine, but suddenly SCADA workstation shows communication error. Several process values become frozen even though the PLC continues to receive valid field signals.
The PLC has no major diagnostic fault.
How should an automation engineer troubleshoot this SCADA communication failure?
If the PLC and field instruments are working properly but the SCADA values are frozen then the troubleshooting should be on the communication path between the PLC and SCADA.
Firstly check the PLC communication status. Check the PLC is working OK and that the process values are changing as they should. If the PLC values are healthy then it is unlikely that the field instruments and PLC are the source of the SCADA problem.
Check the industrial Ethernet between the PLC and the communication server. Check network switches, comms cables, link status and network diagnostics. A SCADA data interruption could occur if there is a bad switch port or an unstable network connection, but the PLC can still control locally.
If you are using an OPC server or a communication gateway, check the connection status and diagnostics. Verify that the server is getting real data from the PLC. Do not reboot communication software, that is the first thing you should not do. First find out the reason for failure.
If the communication server receives correct values and the SCADA is still frozen, then check the SCADA communication driver and tag configuration. Check tag quality, controller address, scan rate, communication time out and data source.
If only selected tags are affected, incorrect tag mapping or configuration should be investigated. If many unrelated tags fail simultaneously, the communication server, network or SCADA interface becomes more likely.
A practical troubleshooting sequence is:
PLC → Ethernet network → communication server or OPC → SCADA driver → SCADA tags.
Compare the same process value at each stage.
The most important principle is to identify the first point where valid data becomes unavailable. This prevents unnecessary changes to healthy PLCs and field instruments when the actual problem exists in the SCADA communication layer.
