How to Connect Existing Industrial Sensors to the Cloud with IoT Gateways and ProSight

Many industrial sites already have good sensors in the field. The pressure transmitter on a pump line, the tank level probe, the pulse output from a flow meter, the RS485 energy meter, and the float switch in a sump may all be working well. The problem is not the sensor. The problem is that the data is trapped in a local panel, PLC, chart recorder, or operator round sheet.

Cloud monitoring does not need to start with a full instrumentation replacement. In many cases, existing transmitters and devices can stay in place. By selecting the right IoT controller or industrial IoT gateway, those field signals can be read, converted, scaled, timestamped, and displayed in ProSight.

That gives teams a practical path to remote visibility without pulling out working equipment.

Existing field sensors can often be connected without changing the process hardware.

Why keeping existing sensors often makes sense

Replacing a working transmitter can cost more than the device itself. There is installation labour, plant isolation, cable testing, loop checks, calibration, documentation updates, and possible downtime. If the sensor already measures the right process value and produces a standard signal, it is often better to connect that signal to cloud-ready hardware.

This is common across:

• Water and wastewater pump stations

• Irrigation systems and bore fields

• Food and beverage production lines

• Quarry and mining support assets

• Cold rooms and storage facilities

• Fuel, chemical, and liquid storage tanks

• Remote power, generator, and energy systems

  
  

The key is to separate two questions.

The first question is whether the sensor measures what matters. The second is whether there is a practical way to read its output. If both answers are yes, an IoT controller can often bridge the gap between the field device and ProSight.

That does not mean every old installation is ready for cloud monitoring. Some wiring may be undocumented. Some signals may be shared with a PLC and need electrical isolation. Some instruments may need re-ranging or calibration. Still, the starting point should be assessment, not replacement.

A site with 4–20 mA pressure transmitters, 0–10 V level sensors, pulse flow meters, Modbus RS485 meters, and dry contact alarms already has most of the ingredients needed for cloud-based monitoring.

Match the sensor output to the right IoT input

Industrial sensors use different output types because they solve different problems. A current loop is good for long cable runs. A voltage signal is common in panels and short wiring runs. Pulses are simple and reliable for totalisers. Modbus can carry many values over one pair of wires. Digital inputs are ideal for on and off status.

The IoT controller must support the signal type directly, or through a suitable signal conditioner.

Sensor or device output	Common field example	What the IoT controller needs
4–20 mA analogue current	Pressure, level, flow, temperature transmitters	Analogue current input with the correct range and scaling
0–10 V analogue voltage	Level probes, VSD references, panel signals	Analogue voltage input with suitable impedance and range
Pulse output	Flow meters, energy meters, production counters	High-speed or counter input suited to pulse rate and voltage
Modbus RS485	Energy meters, VSDs, instruments, multi-channel devices	RS485 port and Modbus RTU support
Digital signal	Float switches, run status, fault relays, door switches	Digital input matched to dry contact, PNP, NPN, or voltage signal

The phrase “compatible IoT controller” matters. It is not enough for a device to be cloud-capable. It must be electrically and logically compatible with the field signals. That includes voltage ranges, input type, resolution, isolation, sampling rate, and communications protocol.

For example, to connect 4–20mA sensor to cloud, the controller needs a current input, or a suitable resistor and voltage input arrangement designed for that purpose. The value then needs to be scaled so that 4 mA equals the low engineering value and 20 mA equals the high engineering value.

A pressure transmitter might be ranged from 0 to 1,000 kPa. In ProSight, the raw input should appear as a clear engineering value, not as an unexplained milliamp reading.

Correct terminal selection is the foundation of reliable cloud monitoring.

How common industrial signals are brought online

Each signal type has its own practical details. Getting these right early avoids false alarms, unstable trends, and confusing dashboards.

4–20 mA transmitters

The 4–20 mA current loop is one of the most common industrial signal types. It is widely used because it is reliable over long cable runs and gives a simple fault indication when the signal drops below the normal live-zero range.

A typical connection involves:

• Confirming whether the transmitter is loop-powered or separately powered

• Checking whether the IoT controller provides loop power

• Wiring the current input in series with the loop where required

• Maintaining the correct loop burden

• Scaling the value into engineering units in ProSight

  
  

Care is needed when the existing signal already feeds a PLC or display. Adding another device into the loop can affect the measurement if the loop burden becomes too high. In those cases, an isolated signal splitter may be the right choice.

0–10 V transmitters

Voltage signals are common in short cable runs and control panels. They are simple to read, but they are more sensitive to voltage drop and electrical noise than current loops.

A 0–10 V input should share the correct reference with the controller input. The controller must also have an input range that suits the signal. If a 0–10 V level transmitter represents 0 to 5 metres, the cloud value should be scaled to show metres, percentage, or volume, depending on what the operator needs.

Shielded cable and clean earthing practices can make a large difference with voltage signals, especially near motors, VSDs, contactors, and long parallel power runs.

Pulse outputs

Pulse outputs are commonly used for flow meters, water meters, gas meters, energy meters, and production counters. The pulse may represent a fixed amount, such as one litre, ten litres, one cubic metre, or one kilowatt-hour.

The IoT controller needs a counter input that can handle the pulse type and rate. Some pulses are dry contacts. Others are open collector, PNP, NPN, or voltage pulses. The input must match the electrical behaviour of the device.

Once connected, ProSight can display totals, rates, and usage over time. For example, a pulse water meter can show daily consumption, pump station flow trends, or unexpected overnight usage.

Modbus RS485 devices

Modbus RTU over RS485 is common in industrial equipment because it can carry many values over a simple two-wire bus. One energy meter might provide voltage, current, power, power factor, frequency, import energy, and alarms.

For Modbus cloud monitoring, the IoT gateway needs an RS485 interface and Modbus master capability. It polls the connected devices, reads selected registers, applies the correct data type and scaling, then sends the results to ProSight.

The setup usually includes:

• Device address

• Baud rate

• Parity and stop bits

• Register address

• Function code

• Data format

• Multiplier or scaling factor

  
  

RS485 wiring also needs attention. Cable type, polarity, termination, biasing, and network layout all affect reliability. A short bench test may work even when the field network is wrong, so it is worth checking the whole bus carefully.

Digital signals

Digital inputs are used for simple status points. They answer yes or no questions.

Is the pump running? Has a high-level float switched? Is the generator in fault? Is a door open? Has a filter differential pressure switch operated?

These signals are easy to understand, but the input type still matters. Some are dry contacts. Some switch DC voltage. Some circuits use PNP or NPN sensors. The controller input must suit the source, and the logic must be set correctly so that “open” and “closed” mean the right thing in ProSight.

Remote assets can send process data to ProSight through a suitable IoT controller.

Build the data path from field signal to ProSight

A cloud monitoring project works best when the data path is mapped from end to end. The signal does not simply “go to the cloud”. It moves through several stages, and each stage needs to be right.

A typical path looks like this:

1. Field sensor

   
   

   The transmitter or device measures pressure, level, flow, temperature, status, energy, or another process value.

   
   

2. Wiring and protection

   
   

   The signal travels through field cable, junction boxes, marshalling terminals, surge protection, fuses, or isolators.

   
   

1. IoT controller or gateway

   
   

   The controller reads the analogue, pulse, Modbus, or digital signal. It may also buffer data if the network drops out.

   
   

2. Communications network

   
   

   The controller sends data using Ethernet, Wi-Fi, cellular, or another available connection.

   
   

1. ProSight

   
   

   ProSight receives the data and presents it as dashboards, trends, status indicators, alerts, reports, or exported records.

   
   

The engineering work sits in the details between those steps.

Sampling rate is one example. A tank level might only need an update every few minutes. A fast machine counter may need much more frequent reading. A pump fault input should report quickly, but a slow-changing temperature does not need constant updates.

Naming is another detail that matters. “AI1” is useful during commissioning, but not in daily operation. “Bore 2 Discharge Pressure” or “Main Tank Level” is far easier to read in ProSight.

Good naming also helps later when the system grows. A site may start with six points, then expand to dozens across multiple assets.

Set up ProSight so the data is useful

The purpose of connecting sensors is not just to collect values. The purpose is to make those values useful.

In ProSight, each point should be set up with clear engineering units, sensible display names, and practical limits. Analogue data should be scaled correctly. Pulse data should show rates and totals in units that make sense. Modbus registers should be labelled so no one has to remember what a register number means.

A useful ProSight display may include:

• Live values for pressure, level, flow, temperature, or energy

• Status tiles for run, fault, trip, high level, low level, or door open

• Trend charts that show changes across hours, days, or weeks

• Alarm notifications for values outside normal limits

• Usage totals for water, power, gas, or production counts

• Simple comparisons between assets or sites

  
  

A pump station example might show wet well level, pump run status, pump fault, discharge pressure, flow total, and daily inflow. A cold room display might show temperature, door status, compressor run, alarm state, and historical trends.

The best screens are simple. They show what someone needs to know, not everything that can be measured.

Clear cloud monitoring starts with clear field data. If the signal is poorly wired, poorly scaled, or poorly named, the dashboard will inherit the confusion.

Check power, isolation, and site conditions before commissioning

Industrial sites are not clean laboratory environments. Panels may contain mixed voltages, long cable runs, electrical noise, moisture, heat, and lightning exposure. A cloud monitoring installation should respect that.

Before commissioning, check the basics.

Confirm that the controller has a suitable power supply and backup if needed. Remote sites may need battery or solar support, depending on the application and update rate.

Check whether analogue inputs need isolation from existing PLC loops. Shared signals can cause measurement errors if connected without planning.

Use surge protection where field wiring is exposed, especially on long outdoor cable runs. This is common for tanks, bores, pump stations, and remote metering.

Confirm that the communications method suits the site. Cellular may be the simplest option in many regional locations, but coverage should be tested at the enclosure, not assumed from a phone reading nearby. Antenna placement can decide whether the system is stable.

Security also matters. Cloud-connected equipment should use controlled access, suitable credentials, and a managed method for sending data. Avoid exposing industrial devices directly to the internet.

Electrical work should be designed and carried out by qualified people who understand the site, the voltages involved, and applicable Australian requirements.

Commissioning checks help confirm that cloud values match real field measurements.

A practical commissioning checklist

A simple commissioning process can prevent many problems after handover.

Start at the sensor and work towards ProSight. Do not assume a cloud value is correct until it has been checked against the field signal.

Use a process like this:

1. Confirm the instrument tag, range, and output type.

2. Check the wiring drawing against the actual panel wiring.

3. Verify signal polarity and terminal allocation.

4. Measure the real signal with a suitable meter or calibrator.

5. Confirm the IoT input reads the same signal.

6. Apply scaling into engineering units.

7. Compare the ProSight value with a known local display or test value.

8. Check alarm thresholds and notification behaviour.

9. Confirm trend logging and data history.

10. Record the final settings for maintenance.

For Modbus devices, read more than one known register during testing. If voltage, current, and energy all look sensible, the address and format are more likely to be correct. If one value is wildly wrong, check byte order, word order, signed values, and scaling.

For pulse inputs, test both total and rate. A counter may increment correctly but calculate an incorrect flow rate if the pulse factor or time base is wrong.

For digital inputs, test both states. A fault alarm that reads backwards can create unnecessary callouts or hide a real issue.

When replacement still makes sense

Keeping existing sensors is often the best starting point, but it is not always the final answer. Some instruments are too old, damaged, inaccurate, or poorly suited to the job.

Replacement may be sensible when:

• The sensor has no usable output

• The signal is unstable or affected by noise

• The process range has changed

• Calibration cannot be trusted

• The device is no longer safe or serviceable

• The cost of adapting the signal is higher than replacing it

• The existing wiring is beyond repair

  
  

Even then, the gateway and ProSight approach still helps. New and old signals can often share the same monitoring platform, which lets a site upgrade in stages instead of forcing one large change.

The takeaway

Cloud monitoring does not have to begin with a blank slate. Many installed instruments already provide the signals needed for useful remote visibility. With the right IoT controller, 4–20 mA, 0–10 V, pulse, Modbus RS485, and digital signals can be connected, scaled, and displayed in ProSight.

The best results come from careful signal matching, clean wiring, sensible scaling, and clear dashboards. Start with the assets that matter most, prove the data path, then expand from there. Existing instrumentation can keep doing its job while ProSight makes the information easier to see, share, and act on.