If you’ve been following with your SCADA Basics series, you’ve studied the components of the SCADA system, as well as how to pick your telemetry communication tool. We understand, however, that not everyone is searching for a new framework. Many of you still have SCADA systems, and the challenge is to keep them online. There is an installment for you.
Unfortunately, as in any system, there is rarely a 100% uptime for the SCADA system. Typically, when a challenge arises, we direct our customers first to check the simple material. Your on-site staff will also solve a dilemma fast. Often the problem with the SCADA mechanism can only be found by understanding where to look. The opportunity to do some simple troubleshooting on your SCADA system is very important, so the following is a very basic method to track problems in SCADA systems. And if you couldn’t solve the problem yourself, being able to provide input to outside or remote support workers can greatly speed up the response process.
- Check for the HMI
The human machine interface (HMI) can be anything from the front view of the control panel to the device to which the data is fed. The problem of a SCADA device that does not gather data or read correctly may also be a simple shift of settings. Check that the settings are set as they should be. Don’t forget the boring yet important elements of the HMI: limit lock, number lock, device power supply, etc. Get operators check and ensure that all HMI settings look the way they normally do.
- Confirm your contact
In the first place, the foundation and justification for SCADA systems to operate is the contact mechanism. Locate where Ethernet (or other communication) ports are situated and check that they are talking through a wire (this can often be confirmed by a blinking indicator light on the connector itself). If the light is out, there is no signal to get through the cable. Check the signal of your telemetry communication if you have the capability. Is the antenna being interfered with? Is the cellular network over there?
In addition, take the time to open the control panel to ensure that the signal is being transmitted to the right locations. Are there any lights on the controller? Is the programming up to date? Do all the wires seem to be well connected (no beams, not so many wires on the same contact, etc.)? Are the components on the panel connected to something in the first place? Another move is to review the right connections to the “as-built” sketches that follow the control panel.
- Verification of the sector
If all else seems to be in working order, then the next step is to make a trip to the data point. Once there, you’re going to want to verify a few items. Next, if you are using a terrestrial radio system, visually scan the antennas for lightning strikes. If you do not see any problems, review your RTU device to make sure it has power and seems to be running as planned. When you are using a mobile phone, ensure that the network is online. Don’t you see the issues? The next move is to search for your instrumentation.
The simplest (though not necessarily the most practical) way to verify accurate instrumentation readings is to manipulate the predicted value to the known quantity (usually zero) and to check the SCADA readings. For example, if a flow meter sends a flow signal from the pump through the controller and into the SCADA system, the best way to ensure that the readings are right is to turn the pump off and validate that the SCADA system still reads zero flow. If it doesn’t, even if it reads zero while the pump is already running, you probably have a poor flow meter. This move can be very labour-intensive depending on the procedure, so it is best to save this one before other potential problems have been ruled out.
For more information about Scada Systems Integrator, please visit https://www.hydrotrent.com
