Industrial IoT basics: sensors, protocols and plant data
Plain explanations for the people who run plants, farms and warehouses and have been asked to add sensors: what a system is made of, how predictive maintenance actually works, and where OPC UA and MQTT each belong.
Industrial IoT articles
- What is SCADA? How supervisory control works
What SCADA is and how it works: field devices, RTUs and PLCs, communications, HMI and historian, polling, protocols, SCADA vs PLC vs DCS, and security.
- 4-20mA current loop: how the signal works
4-20mA explained: how a current loop carries a reading, why it starts at 4 mA, loop power and wiring, scaling, fault levels, HART, and reading it into IoT.
- IoT gateway: what it does and how to choose one
What an IoT gateway does: protocol translation from Modbus, Zigbee, BLE and LoRaWAN to MQTT, buffering when the uplink drops, security, and how to choose one.
- Modbus RTU explained: frames, registers and function codes
Modbus RTU explained: how a master polls devices over RS-485, the frame and CRC byte by byte, the four register tables, function codes, and RTU vs TCP.
- MTBF vs MTTR vs MTTF: reliability metrics explained
MTBF vs MTTR vs MTTF: what each failure metric measures, how to calculate them with a worked example, availability, and what an MTBF figure does not promise.
- RS-485 explained: wiring, termination and how the bus works
RS485 explained: differential signaling on a twisted pair, the A and B lines, termination and biasing, cable length against speed, and RS-485 vs RS-232.
- What is a PLC? Programmable logic controllers explained
What is a PLC: the parts of a programmable logic controller, the scan cycle, the IEC 61131-3 languages, and how PLC data reaches an industrial IoT system.
- Edge computing vs cloud computing for IoT: where the work should happen
Edge computing vs cloud computing for IoT systems: what each means, how latency, bandwidth, reliability and cost differ, and how to split the work.
- What an industrial IoT system is made of, from sensors to dashboard
What an industrial IoT system is made of: sensors and actuators, controllers, gateways, the plant network, a broker or historian, dashboards and alerts.
- Predictive maintenance with vibration and temperature sensors: how it works
How predictive maintenance sensors work: what vibration and temperature reveal about bearings, motors and pumps, where to mount them and how alerts work.
- OPC UA and MQTT in factories: where each fits
OPC UA and MQTT in factories: what each protocol does, how a client-server information model differs from publish-subscribe, and how plants use both.
Related guides
Shorter guides to the questions that come up around industrial IoT.
- 4-20mA current loop: how the signal works
4-20mA explained: how a current loop carries a reading, why it starts at 4 mA, loop power and wiring, scaling, fault levels, HART, and reading it into IoT.
- IoT gateway: what it does and how to choose one
What an IoT gateway does: protocol translation from Modbus, Zigbee, BLE and LoRaWAN to MQTT, buffering when the uplink drops, security, and how to choose one.
- What is SCADA? How supervisory control works
What SCADA is and how it works: field devices, RTUs and PLCs, communications, HMI and historian, polling, protocols, SCADA vs PLC vs DCS, and security.
What this topic covers
This topic covers connected sensing and data in industrial settings: the layers of a system from the sensor on the machine to the dashboard in the office, the sensors used for condition monitoring, and the two protocols most plants end up using to move data around. The articles are written for operations and engineering people rather than for software vendors.
It does not cover functional safety systems, machine control logic or the selection of a specific vendor platform. Those decisions need site-specific engineering and, in the case of safety, a certified process that no article can stand in for.
Start with the industrial IoT basics if the phrase is new to you: what a system is made of, which sensors do the useful work, where the data should be processed (the edge computing against cloud computing question), and which two protocols carry most plant data. Each has its own article below, and the sensors and hardware topic covers the parts themselves. The serial side, RS-485 wiring and the Modbus RTU protocol most meters and drives speak, has a pair of articles of its own.
Common industrial IoT questions
What is the difference between industrial IoT and a normal SCADA system?
A SCADA system supervises and controls a process: it reads from PLCs, shows operators what is happening, and lets them change setpoints or stop a line. It is built for control, sits on the plant network, and is usually engineered by the same people who installed the machines. Industrial IoT, as the term is normally used, adds sensing and data collection that is not part of the control loop: extra sensors on motors, gateways that publish machine data to a broker, and analysis that runs on a server or in the cloud rather than in the control room.
The two overlap and increasingly share hardware. A modern PLC may publish MQTT messages directly, and a SCADA historian may be the data source an analytics tool reads. The useful distinction is about purpose. If a signal is used to control the process, it belongs in the SCADA and safety world with all of that world's discipline. If it is used to understand, predict or report, it is IoT territory, and it can be added without touching the control system.
How does sensor data get from a machine to a dashboard?
Through a chain of hand-offs, each of which changes the data's shape. The sensor produces a voltage, a current or a digital reading. A controller or a small gateway reads it, timestamps it and turns it into a message. That message travels over the plant network, usually to a broker that other systems subscribe to, or to a historian that stores it against a tag name. A dashboard then queries the broker or the historian and draws the value.
The article on what an industrial IoT system is made of draws this chain layer by layer. The places where projects stall are almost always at the boundaries: a sensor with no controller to read it, a gateway on a network segment the broker cannot reach, or tag names that mean different things on different machines. Getting those boundaries agreed before buying sensors saves more time than any choice of dashboard.
Do I need to replace equipment to add sensors?
Usually not. Most condition monitoring is done by attaching sensors to the outside of existing machines: a vibration sensor bolted or glued to a bearing housing, a temperature sensor on a motor casing, a current clamp around a supply cable. None of these require opening the machine or changing its controls, and they can be fitted during a normal maintenance window.
Where replacement does come up is in the data path rather than the machine. An old PLC may have no spare communication port, or may speak a protocol nobody has a driver for, and then a gateway or a protocol converter is the answer rather than a new controller. The predictive maintenance article lists which sensor types are retrofit-friendly and where each is mounted. Treat any proposal that starts with replacing the machine as a separate capital decision, and keep the sensing project small enough to prove itself first.
Sponsor an article in Industrial IoT
Sponsored articles and in-article link placements for IoT vendors, agencies and SEO buyers. Every sponsored piece is labeled, edited to the same standard as the rest of the site, and placed in the hub its readers already visit. Rates on request.