Rechercher
Fermer ce champ de recherche.

Case study: SCADA – MODBUS – SMC PHANTOM

Case Study: SCADA – MODBUS – SMC PHANTOM

Introduction:

The application of different communication protocols in industrial processes is of great relevance nowadays for the interaction of condition monitoring and automation systems. These systems have sensors and actuators, which are used as means to interact with their environment. Most of these devices have wired or wireless communication systems, which help us to collect information about the condition status of the machines, number of repetitions in a process or for some cost analysis.

For this reason, the Phantom condition monitoring system meets most of the above mentioned characteristics, since it allows us to know information about the machines, their condition, their repeatability and subsequently reduce costs in maintenance and production stoppages. In addition to these virtues, with the Phantom system we can integrate the different parameters to an industrial communication network via Modbus TCP/IP.

In this document we will show an application of the different sensors installed in a plant located in Merida, Yucatan. These sensors are in charge of measuring Vibration, Temperature and Current in machines such as Milling Machine, Lathe, CNC Machining Center and Compressor. This paper presents the application of a SCADA system using RapidSCADA software to show the communication via MODBUS TCP/IP.

Approach:

As a first instance we have our Phantom system Installed in a machine manufacturing shop. In this workshop we have installed 6 Triaxial Vibration Phantoms, 3 Current Phantoms and 3 Contact Temperature Phantoms. This system can currently be reviewed in detail through the EI Analytics platform. In order to have an easier way to appreciate the status of the machines, it will be applied in a SCADA system, as it allows to visualize the health of each machine as a traffic light.

Development:

To develop this system, we made an internal configuration in our Gateway to allocate information in a memory space the data coming from each one of the sensors, in such a way that we have reserved 12 memory spaces. These memory spaces are distributed as follows:

IDStart ByteSensor
11Triaxial Vibration 
251Triaxial Vibration 
3101Triaxial Vibration 
4151Triaxial Vibration 
5201Triaxial Vibration 
6251Triaxial Vibration 
7301Current
8351Current
9401Current
10451Temperature
11501Temperature
12551Temperature

With this configuration, we will be able to have the sensor’s information through the Gateway using MODBUS TCP/IP.

For the SCADA system, we proceed to make our distribution for the interface, indicating each sensor and its corresponding token.

Once we have our graphic distribution, we proceed to process the information. To do so, we first store each value obtained by the sensor in a memory space assigned according to the offset provided by the Phantom system data sheet. We take sensors 1, 7 and 10 as an example.

ByteDescription
1Node ID
3Sensor Type
4RMS channel 1
6RMS channel 2
8RMS channel 3
10Battery voltage
12Sensor Temp.
14Firmware Version
ByteDescription
301Node ID
303Sensor Type
304Battery Voltage
306Sensor Temp.
308Firmware Version
310sequence
311Average current ch 1
312Average current Ch 2
313Average current Ch 3
314Average current Ch 4
ByteDescription
450Node ID
452Temp. Channel 1
454Battery voltage
456Sensor Temp.
458Firmware version
460Temp. Channel 2
462Temp. Channel 3

This configuration can be seen in RapidSCADA:

It should be noted that the sensor data format is Little Endian.

When we finish implementing the data logs, we link the RapidScada software to our Gateway through the IP address:

Results:

As results we can appreciate in the images the monitoring of certain machines through the SCADA system with several indicators, which help us to know their current status. Each sensor has a witness for each channel, vibration in the 3 axes, 3 phases of current, in addition to the temperature sensor with 2 channels.

As a first approximation, values were established with which the green, yellow or red indicators would be activated, in order to know the condition of the machinery according to its operations. Next, we present 3 images of the SCADA system in 3 different days.

On day 1, some machines are observed in alert status, it was verified that the machines with this condition were working properly and adjustments were made with the parameters to display each of these witnesses.

Illustration 1 – Day 1 of Measurements

Illustration 2 – Measurement Day 2

On day 2, the alarm condition indicators of each sensor are observed in good condition and some machines in warning status, the machines were checked again until the limits of each sensor status were adjusted again.

Illustration 3 – Day 3 of measurements

About the author

Dr. Thierry Erbessd, a prominent Mexican entrepreneur, and graduate of the National Polytechnic Institute has revolutionized the field of Vibration Analysis, Dynamic Balancing, and Condition Monitoring. Through his innovative software DigivibeMX®, DragonVision®, and WiSER Vibe®, he has set a before and after in the industry. As president of Erbessd Instruments®, he has not only led the company to the top of the global industrial maintenance industry but has also expanded its influence with strategically located offices in America, Europe, and Asia, establishing himself as an undisputed reference in industrial maintenance solutions worldwide.

ERBESSD INSTRUMENTS® is a leading manufacturer of Vibration Analysis Equipment, Dynamic Balancing Machines, and Condition Monitoring with facilities in Mexico, the USA, England, and India