Real-Time Data Acquisition Systems (RTDAS): Improving Telemetry and Data Reliability

In industrial and environmental monitoring, the analyser or sensor is only the first step. The reading must then travel from the field to a receiving server, often through several devices and a communication network. A fault at any point can leave gaps in the record, which matters particularly for effluent, emission and water monitoring, where continuous data is expected. A Real-Time Data Acquisition System (RTDAS) is designed to manage this journey and improve the reliability of the data that arrives.

What Is a Real-Time Data Acquisition System (RTDAS) and What Does Each Part Do?

A Real-Time Data Acquisition System (RTDAS) connects field instruments to a receiving server, so that measurements can be viewed, stored and reported. It has four main parts, each with a different role:

  • Field instruments: sensors and analysers measure the process or environmental parameter and provide the result as an analogue signal (such as 4-20 mA) or a digital output.
  • Data logger: it reads the instruments, applies the configured scaling, adds an accurate timestamp, stores the data locally and prepares it in the format needed for sending.
  • Telemetry: the communication link, such as a 4G modem, LAN or satellite connection, that carries the data from the site.
  • Receiving server: it accepts the data, checks it, stores it and makes it available through dashboards, alerts and reports, or forwards it to another server such as a regulatory server.

The time taken for data to reach the server depends on how the system is configured, including the logging and transmission intervals, and on network conditions. Real-time in this context means regular, timely updates, not instantaneous delivery.

What Causes Data Gaps in an RTDAS?

Most data gaps can be traced to one of five areas:

  • Instrument to logger: incorrect wiring, wrong Modbus settings or electrical noise on the cable.
  • Logger configuration: wrong scaling, polling intervals or time settings.
  • Communication link: weak signal, SIM or data plan problems, or unstable LAN connections.
  • Receiving server: files rejected because of format, naming, protocol or credential mismatches.
  • Power: supply failures that restart the logger or switch off the modem.

How Can an RTDAS Reduce Data Loss?

No system can promise zero data loss, but good design reduces the chance and the impact of gaps. The main measures are:

  • Local storage and back-fill: the logger stores readings in its own memory and can re-send missing records once communication returns. How much it can hold depends on the logger’s memory capacity, and back-fill works only if the receiving server accepts delayed data in the way the logger sends it.
  • Accurate timestamps: readings should be time-stamped at the logger, and the clock kept synchronised, so that back-filled data is placed correctly in the record.
  • Backup power: a battery or UPS can keep the logger and modem running through short mains failures. This is an optional configuration, selected according to site conditions.
  • Redundant communication: a second SIM, a combination of LAN and 4G, or satellite backup may be added where the application and coverage justify it.
  • Monitoring of the system itself: alerts for communication failures or missing data help the support team to respond quickly.

Which Communication Interfaces and Protocols Should an RTDAS Support?

Interfaces and protocols are different things, and it helps to keep them separate:

  • Analogue 4-20 mA is an electrical signal interface used by many instruments.
  • RS485 is a physical (electrical) communication interface for serial connections over a cable.
  • Modbus RTU is a communication protocol, commonly carried over RS485.
  • Modbus TCP is a communication protocol carried over Ethernet networks.
  • Server communication methods, such as sending CSV or TXT files by FTP or using other methods defined by the receiving server, are agreed with the server owner.

The RTDAS should support the interfaces and protocols that the connected instruments and the receiving server actually use. Where instruments come from different manufacturers, custom interfacing and configuration are often needed.

How Do You Troubleshoot an RTDAS Step by Step?

  • Check the power supply to the logger and modem.
  • Confirm that the instrument shows a healthy reading on its own display.
  • Verify the wiring, addresses and communication settings between the instrument and the logger.
  • Check the logger’s local data to confirm that readings are being recorded with correct timestamps.
  • Test the signal strength and the SIM or network status.
  • Review the server log for rejected files or authentication errors.
  • Confirm that any missing data has been back-filled.

Working from the field towards the server separates instrument problems from communication and server problems.

How Does Aaxis Nano Engineer an RTDAS for Application-Specific Monitoring?

Aaxis Nano designs and delivers the complete RTDAS chain, rather than supplying individual components. Our engineering work covers instrument selection, interfacing, logger configuration, telemetry design and connection to the receiving server and SCADA or HMI, so that each part is matched to the application and to the others.

Our own platform, I-Telemetry, supports data acquisition, transmission, storage and reporting. Our OPTIMA NETLOG data loggers collect readings from field instruments, and the platform handles delivery to servers, dashboards, alerts and reports. Depending on the configuration, options can include local storage with back-fill, battery backup and several server destinations. See our telemetry and software page for more detail.

What differentiates our approach is:

  • Application-specific engineering: the design follows the site, the parameter and the receiving system.
  • Multi-vendor instrument integration: we connect instruments from different manufacturers into one data path.
  • Telemetry configuration: we select and configure communication links to suit local coverage and reliability needs.
  • Data continuity: storage, back-fill, timestamps and backup options are planned from the start.
  • Server integration: we work with the receiving server specification, whether it is a plant platform or a regulatory server.

We apply this across a range of applications, including river water monitoring for level and discharge, flood monitoring, groundwater monitoring, sewage and effluent monitoring and wider environmental data acquisition. For hydrological, level, discharge and flood applications, we work with technology partners such as OTT HydroMet, Sommer and Sutron. For groundwater applications, we work with In-Situ.

Talk to Our Experts About Your RTDAS

Talk to our experts at Aaxis Nano to evaluate your RTDAS requirements and design a reliable data acquisition and telemetry network for your plant, river or groundwater stations and discharge points, with the right instrument interfacing, data logger, communication link and server and SCADA integration for your site.

FAQs

What is the difference between an RTDAS and SCADA?

An RTDAS collects, stores and transmits data from field instruments to a server or dashboard. SCADA also provides supervisory control, so operators can monitor equipment and send commands. Many projects use both together.

How can data gaps be reduced when the network fails?

Use a data logger with local storage and back-filling, accurate timestamps and, where justified, backup power and a second communication path. The amount of data that can be stored depends on the logger, and the server must be able to accept delayed data.

Is RS485 the same as Modbus?

No. RS485 is a physical communication interface, while Modbus RTU is a protocol that is often carried over RS485. Modbus TCP is a different protocol that runs over Ethernet networks.

Scroll to Top