Wireless Monitoring for Existing Industrial Sensors with LoRaWAN and 4G Connectivity
Many industrial sites already have good pressure, level, flow and air-quality sensors in place. The problem is not the sensor. The problem is that its signal often stops at a local gauge, controller, chart recorder or isolated panel.
Replacing every field instrument to get online data is expensive, slow and hard to justify when the existing devices still work. A more practical path is to add a wireless analogue-input device beside the sensor, read the same signal, then send that data to an online platform using LoRaWAN or 4G.
That simple idea can turn legacy instrumentation into a live monitoring system without disturbing the process.
Existing sensors often have more value than people realise
A pressure transmitter on a water main, a level sensor on a chemical tank, a flow meter on a process line or an air-quality probe in a workshop may already measure exactly what the site needs to know.
The missing part is usually communication.
Many older or standalone instruments provide a standard output such as:
4 to 20 mA analogue signal
Common for pressure, level, flow, temperature and gas detection instruments.
0 to 10 V or 0 to 5 V signal
Often found on environmental sensors, HVAC equipment and some monitoring probes.
Pulse output
Common on flow meters and totalisers.
Relay or switch output
Useful for high-level alarms, pump status, door contacts or fault states.
When these signals are only wired into local systems, the data stays on site. A technician may need to visit the location to check a reading. Operators may only find out about a drift, blockage, leak or overfill after it becomes visible.
A wireless input device changes the flow of information. It reads the sensor signal, converts it into engineering units and sends it to a cloud platform where it can be graphed, logged and used for alerts.
This is the key benefit of wireless monitoring for existing industrial sensors with LoRaWAN and 4G connectivity. The field instrument keeps doing its job, while a new communication layer makes its data available anywhere it is needed.
How analogue-input wireless devices connect to existing instruments
An analogue-input wireless device is a small data acquisition unit with one or more input channels. It connects to the same type of signal your instrument already produces.
In a typical setup, the existing sensor remains installed in the pipe, tank, duct or room. The wireless unit is mounted nearby in a suitable enclosure. Its input terminals connect to the sensor output or to a parallel signal point in a panel. The device then samples the reading on a schedule and transmits it wirelessly.
The online platform receives that data and displays it as a live value, trend line, alarm state or exportable history.
A pressure sensor example
A 4 to 20 mA pressure transmitter on a remote pumping station may already feed a local controller. If the controller has no internet connection, the site still has no easy way to view pressure trends from a central location.
A wireless input device can be connected to the pressure signal, often through an isolated input or signal splitter when needed. The platform then scales the signal, for example:
Signal | Scaled reading |
4 mA | 0 bar |
12 mA | 5 bar |
20 mA | 10 bar |
Once the scaling is set, the platform can show pressure in bar, kPa or psi. It can also trigger an alarm if the reading falls below a pump operating threshold or rises above a safe limit.
A tank level example
Many tank level sensors already produce a continuous output. Adding wireless monitoring means the same level reading can support automatic replenishment, overflow prevention or usage tracking.
This is especially useful where tanks sit in unmanned areas, yards, farms, utility sites or satellite production areas. A daily visit to check a level can become a dashboard check and an exception-based visit.
A flow meter example
Some flow meters provide a pulse output for total volume or a 4 to 20 mA output for flow rate. A wireless device can count pulses, measure rate or report totals at set intervals.
That can help track water usage, compressed air demand, chemical dosing or wastewater discharge without running new communication cables across the site.
LoRaWAN works well for low-power site-wide monitoring
LoRaWAN is designed for long-range, low-power sensor communication. It suits applications where devices send small packets of data rather than continuous high-bandwidth streams.
That makes it a good fit for readings such as:
Tank level every 15 minutes
Pressure every 5 minutes
Flow total every hour
Air-quality values every few minutes
Battery voltage once per day
Alarm state as soon as it changes
A LoRaWAN system usually includes field devices, one or more gateways and a network server or platform. The field device sends data to a gateway, and the gateway passes it to the internet using Ethernet, Wi-Fi or cellular backhaul.
The strengths of LoRaWAN are clear.
LoRaWAN is a strong fit when | 4G is often better when |
Many sensors sit across one site | Each device is in a separate location |
Battery life matters | Mains power is available |
Data packets are small | More frequent data is needed |
A gateway can cover the area | No gateway can be installed |
The site wants a private network | Public mobile coverage is reliable |
LoRaWAN can be cost-effective when there are many monitoring points within coverage. One gateway might support a large number of devices, depending on site layout, distance, antenna position and duty cycle limits.
It also works well where power is limited. Many LoRaWAN input devices can run from batteries if they wake up, read the sensor, transmit and return to sleep. Battery life depends on the sensor power demand, sample rate, transmit interval, signal strength and temperature.
The main design task is coverage. Industrial sites contain metalwork, tanks, vessels, reinforced concrete, machinery and electrical noise. A gateway placed high and clear will usually perform better than one hidden in a control room cabinet.
A site survey or trial installation can prevent guesswork. Even a short test with a gateway and sample device can reveal whether readings arrive reliably from basements, yards, plant rooms and remote corners.
4G is better for standalone and remote assets
4G monitoring devices use the mobile network directly. They suit remote equipment, temporary assets and locations where installing a LoRaWAN gateway does not make sense.
Common examples include:
Isolated pumping stations
Construction site tanks
Environmental monitoring points
Remote air-quality sensors
Agricultural water systems
Mobile process skids
Small unmanned utility sites
With 4G, each device can send data straight to the online platform as long as it has mobile coverage and a suitable SIM or data plan. There is no local gateway to install.
That independence makes 4G simple for single assets or widely spread locations. The trade-off is power use. Cellular transmission usually needs more energy than LoRaWAN, so 4G devices often use mains power, solar power or larger batteries.
Data volume also matters. Most industrial sensor readings are small, so bandwidth is rarely the issue. The bigger questions are signal strength, power supply, antenna selection and how often the device wakes up to report.
For remote applications, an external antenna can make a major difference. A device inside a steel cabinet, underground chamber or metal kiosk may struggle, while an antenna mounted outside can provide stable communication.
The online platform turns raw signals into useful information
Wireless hardware collects the reading, but the platform makes it useful.
At a basic level, the platform should show the latest value from each sensor. For industrial monitoring, it should also support scaling, units, alarms, history and export.
A practical platform will usually include:
Device status
Last report time, battery level, signal strength and device health.
Engineering unit scaling
Conversion from 4 to 20 mA or voltage into bar, metres, litres per second, ppm or another useful unit.
Trend graphs
Historical readings over hours, days, weeks or months.
Alarms
High, low, rate-of-change or no-data alerts by email, SMS or platform notification.
User access
Different views for operators, maintenance teams, managers or service contractors.
Data export
CSV downloads, API connection or integration with SCADA, CMMS or reporting tools.
Scaling deserves special care. The device may only see a current or voltage value. The platform needs to know what that value means.
For a 4 to 20 mA level sensor, 4 mA may mean an empty tank and 20 mA may mean a full tank. For an air-quality device, 0 to 10 V may represent a specific gas concentration range. If the scaling is wrong, the dashboard will look precise but show the wrong value.
Alarm settings also need thought. If a pressure reading briefly spikes during pump start-up, a simple high alarm may create nuisance alerts. A better setup might require the value to stay above the threshold for a set time before sending a warning.
Good monitoring does not flood people with messages. It sends the right alert early enough to act.
Installation should protect the existing control system
The safest retrofit is one that does not interfere with the instrument or the process control loop.
Before connecting anything, check how the existing sensor is powered and where its signal goes. A 4 to 20 mA loop may be powered by a PLC, local display, barrier, isolator or separate supply. Adding another device without understanding the loop can create errors or dropouts.
In many cases, an isolated input, loop splitter or signal conditioner is the right approach. These devices allow the wireless monitor to read the signal while reducing the risk of affecting the existing control system.
Also check practical site details.
Power supply
Decide whether the wireless device will use batteries, solar, mains or the sensor loop.
Ingress protection
Use an enclosure suited to washdown, dust, rain, chemicals or outdoor exposure.
Hazardous areas
If the location has explosive gas, vapour or dust risks, use equipment and installation methods approved for that zone.
Antenna location
Keep antennas clear of metal obstructions where possible.
Cable routing
Keep signal wiring tidy, protected and separated from noisy power cables.
Maintenance access
Mount devices where batteries, terminals and labels can be reached safely.
A retrofit should also include documentation. Record the sensor range, scaling values, wiring point, device ID, antenna type, reporting interval and alarm thresholds. That record saves time when someone needs to service the system later.
Security and reliability need to be designed in from the start
Wireless monitoring often carries operational data, so security matters even when the readings are not commercially sensitive.
LoRaWAN uses device authentication and encryption as part of its normal design. 4G devices rely on mobile network security, SIM management and secure communication to the platform. In both cases, the project should use strong device credentials, controlled user access and encrypted platform connections.
Reliability is just as important.
A useful system should make gaps visible. If a device stops reporting, the platform should show a no-data state rather than leaving the last reading on screen as if it were current. For critical points, the alert for missing data can be as important as the high or low process alarm.
Think about what happens during:
Mobile network outages
Gateway power loss
Battery depletion
Sensor failure
Cable damage
Cloud service interruption
Some devices can buffer readings and forward them later. Others only send live values. The right choice depends on whether the site needs a complete historical record or only current status and alarms.
Where this approach makes the biggest difference
Wireless retrofits work best where the cost of cabling or site visits is higher than the cost of adding a wireless input.
That often includes spread-out, hard-to-reach or low-density monitoring points. A few examples show the pattern.
Application | Existing sensor | Wireless value |
Water network pressure | 4 to 20 mA pressure transmitter | Detect low pressure and pump issues sooner |
Bulk chemical storage | Ultrasonic or radar level transmitter | Track stock and prevent overfill risk |
Compressed air system | Flow meter or pressure sensor | Find unusual demand and possible leaks |
Workshop air quality | Gas or particulate sensor | Log exposure trends and trigger ventilation alerts |
Wastewater lift station | Level transmitter or float switch | Reduce emergency visits and missed alarms |
The strongest cases are usually not about collecting data for its own sake. They are about reducing manual checks, spotting faults earlier, improving compliance records or giving maintenance teams better evidence before they travel to site.
A sensible rollout starts small
The best way to prove the concept is to choose a small group of sensors that already cause manual work or operational uncertainty.
Pick points where a live reading would clearly help. A remote tank that often runs low, a pressure point that operators check by hand, or an air-quality monitor with no central logging can make a good first candidate.
A simple rollout plan looks like this:
List the existing instruments
Record sensor type, output signal, range, power and location.
Choose the communication method
Use LoRaWAN for clustered site monitoring and 4G for standalone or remote points.
Confirm wiring and isolation needs
Protect the existing loop before adding the wireless input.
Set the reporting interval
Match the interval to the process. Slow tank levels do not need second-by-second updates.
Scale the readings
Convert raw signals into clear engineering units.
Set alarm rules
Include sensible delays or deadbands to avoid alert fatigue.
Test against known readings
Compare the dashboard with a local display or calibrated reference.
Document the installation
Keep wiring, configuration and device records up to date.
Once the first points prove reliable, the same pattern can expand across a site or across multiple locations.
Wireless monitoring does not have to start with replacing field instruments, redesigning controls or installing long cable runs. In many cases, the fastest improvement is to keep the sensors that already work and add a wireless path for their signals.
LoRaWAN and 4G analogue-input devices make that practical. They give older pressure, level, flow and air-quality sensors a route to modern dashboards, alarms and records, while leaving the process hardware in place. The result is a clearer view of the site with less disruption and a lower barrier to getting started.
Comments