Home / 预测性维护中数据采集的工业网关:信号质量、边缘处理与网关选择
#新闻 #行业博客 · October 23, 2026 · About 12 minutes
views

Industrial Gateway for Data Acquisition in Predictive Maintenance: Signal Quality, Edge Processing, and Gateway Selection

Written By

Tespro

A centrifugal pump develops bearing wear, but its maintenance dashboard continues reporting normal operation. The vibration sensor detects mechanical changes, yet the PLC exposes only a periodically updated RMS value. By the time the trend crosses the alarm threshold, the fault may already be advanced.

Installing an Industrial Gateway for Data Acquisition will not recover vibration details that were never measured. Its role is to transfer available condition data without introducing excessive delay, incorrect scaling, or missing records.

At Tespro, we consider three questions before recommending a gateway for predictive maintenance: what failure signatures must be captured, how frequently the source equipment updates them, and what information the monitoring platform needs to distinguish deterioration from normal load variation.

1. Which Equipment Signals Are Worth Collecting?

Predictive maintenance data requirements depend on the physical failure mechanism. A temperature trend may reveal lubrication problems in a gearbox, but it cannot reliably identify every early-stage bearing defect.

The acquisition architecture should match the diagnostic method.

EquipmentDiagnostic signalsAcquisition limitation
Electric motorsCurrent, winding temperature, vibrationCurrent changes with mechanical load; temperature responds slowly
Centrifugal pumpsFlow, pressure, vibration, powerProcess changes can resemble equipment degradation
GearboxesVibration spectrum, temperature, shaft speedSpectral interpretation depends on operating speed
Air compressorsDischarge temperature, pressure, currentLoad/unload cycles distort simple trend thresholds

Raw Waveforms vs Processed Condition Data

High-frequency vibration analysis normally requires dedicated acquisition hardware with appropriate sampling, filtering, and signal conditioning.

A gateway polling Modbus registers can retrieve vibration RMS, peak values, or calculated frequency features if the connected instrument exposes them. It cannot reconstruct the original acceleration waveform from an RMS register.

For practical applications, determine if your monitoring solution needs:

•Raw measurements: Continuous waveforms

•Calculated features: Post-processed data like RMS or spectral features

•Operating context: Equipment status and maintenance info to interpret/resolve alarm conditions

In a large-scale (distributed) system, you might be able to trade-off some flexibility for retrospective data analysis by having the gateway do less data post-processing and feature extraction.

2. How Fast Does the Gateway Need to Collect Data?

In most Modbus-based condition monitoring applications, it is not the gateway's data collection speed that will slow things down. It is more likely to be the field device polling cycle.

Modbus RTU acquisition time is determined by the serial baud rate, the length of the register count, the response length, device turnaround time, and communication errors.

A multi-device RS485 network can become unbalanced update cycle if one of the devices becomes unresponsive.

Estimate Complete Polling Cycle

Consider the following when selecting an industrial gateway:

•Source update interval: How often does the controller update the measured value?

•Bus occupancy: How many requests are needed to collect data from all connected devices?

•Timeout behavior: Will continuous errors from one instrument lead to a timeout for the remaining instruments?

•Acquisition priorities: Will the gateway support polling for condition tags for critical assets more frequently than the default for secondary operating parameters?

A good initial estimate is:

Total scan time = Transaction time + Turn around delay + Timeout/Retry overhead.

This estimate needs to be verified against the actual device population.

For Modbus TCP, Ethernet enables more flexible communication, but loading of the PLC and the number of concurrent request need to be assessed as well.

A one-second cloud reporting interval, for example, does not ensure one-second measurement freshness.

3. Prevent Data Conversion Errors from Becoming False Faults

Protocol conversion makes heterogeneous equipment accessible to a common monitoring platform. It also introduces opportunities for data corruption if register definitions are incomplete.

We consider here a 32-bit floating-point temperature stored across two Modbus registers. Incorrect word order can result in an invalid value even if communication was successful.

Scaling issues and register offsets can cause similar problems.

Data Quality Controls

•Register mapping: Verify functions codes, addresses, data types, and byte order against device documentation.

•Timestamp: Differentiate the time a measurement was made from the time it was transmitted to the gateway and the time it was transmitted to the cloud.

•Stale data: Set an invalid flag on data upon loss of a good acquisition; do not send outdated measurements.

•Equipment context: Assign a measurement to a piece of equipment, machine identity, location on equipment, and the equipment operating mode.

•Data continuity: Upon restoration of the network identify duplicates and data gaps.

Data quality controls are important even when using technologies such as OPC UA and MQTT.

In predictive maintenance, data quality controls, time stamps and data flags can be as important as actual sensor data.

4. Should Fault Detection Run at the Edge or in the Cloud?

It is advantageous to do local processing for equipment operating over a cellular network and/or if it's not practical to send every measurement to the cloud. For example, measurement filters and equipment-specific alarm thresholds can be done at the edge. The edge can also be used to determine abnormal events and/or trends.

Similar to motor current, evaluation of motor current should be done in the context of load rather than assessing faults in isolation.

What Happens When Connectivity Fails?

If the cellular connection is lost, continuous data delivery stops unless the architecture provides local storage.

MQTT QoS 2 supports exactly-once message delivery at the protocol level, but this does not guarantee exactly-once application processing or unlimited offline data retention. Buffering and recovery must be designed separately.

Tespro gateways are designed to integrate communications and industrial edge computing within an application. Local analytics, buffering, replay, and filtering should be assessed against the configuration and firmware of the gateways.

5. Selecting a Tespro Industrial Gateway for Data Acquisition

The TG-324 and TG-325 gateways offer industrial connectivity, Gigabit Ethernet and other protocols for machine condition monitoring.

Their published specifications include Modbus RTU/TCP, MQTT, OPC UA, and TesproOS-based management.

Selection factorTG-324TG-325
Cellular connectivity2G/3G/4G2G/3G/4G/5G
EthernetGigabit WAN + LANGigabit WAN + LAN
Serial connectivity2 × RS485, 1 × RS2322 × RS485, 1 × RS232
Digital I/O4 configurable GPIO4 configurable GPIO
Industrial protocolsModbus, MQTT, OPC UAModbus, MQTT, OPC UA
Main selection distinction4G-based remote installationsSites requiring a compatible 5G uplink

Both are candidates for consolidating data from compatible PLCs, sensors, and monitoring instruments.

The choice between 4G and 5G should depend on available carrier coverage, reporting traffic, uplink reliability, and deployment requirements—not an assumption that higher cellular bandwidth improves sensor accuracy.

For installations with multiple RS485 devices, protocol compatibility and aggregate polling performance may be more decisive.

6. What Should the Acceptance Test Demonstrate?

MQTT provides a way to test communication to the broker. However, it does not verify the quality of the information provided or its diagnostic value.

It is suggested that the entire acquisition path be exercised to cover operating conditions and failures.

•Measurement accuracy: Measurements should be compared to actual readings from the PLC (or other measuring devices) or check measurements throughout the operating range.

•Polling performance: The actual polling time for given device counts and register configurations should be measured.

•Communication failures: The behavior of the system should be observed during the loss of a field device, including the behavior of the system during retry events and the handling of stale data.

•Network recovery: The logged data should be reviewed to check if data is missing, duplicated, or out of order, and check the function of buffering is working as expected.

•Time consistency: Data is time synchronized across devices.

•Security and isolation: Access control and VPN, as well as other isolation mechanisms, should be checked.

Acceptance testing of data freshness, completeness, recovery, and loss should be defined prior to deployment. Predictive-model performance should be tested against a representative set of equipment condition data.

Tespro can assist with assessment of data connectivity for existing PLCs/instruments and remote condition monitoring. Please send your equipment count and register maps to our team.

Check out available configurations of Tespro Industrial Gateway Solutions.

FAQs

Q1. What is the role of a Tespro industrial gateway in predictive maintenance?

Tespro industrial gateways collect equipment data from compatible PLCs, sensors, and monitoring devices, then transmit it to edge or cloud-based maintenance platforms.

Q2. Which Tespro industrial gateways are suitable for predictive maintenance?

The TG-324 and TG-325 are candidates for industrial data acquisition. The TG-324 supports 4G connectivity, while the TG-325 adds 5G support.

Q3. Which industrial protocols do Tespro gateways support?

The TG-324 and TG-325 support Modbus RTU/TCP, MQTT, and OPC UA, enabling data exchange between industrial equipment and monitoring systems.

Q4. Can Tespro gateways collect data from existing PLCs?

Yes, when the PLC uses a supported communication protocol. Register mapping, data formats, polling intervals, and device compatibility must be verified before deployment.

Q5. Can Tespro gateways collect vibration and temperature data?

Yes, from compatible instruments that expose these measurements through supported interfaces. High-frequency vibration waveform capture may require dedicated acquisition hardware.

Recent Articles

在Enlit Europe 2026预订您的免费BT-PLUS样品

公告 |Enlit欧洲2026 Enlit Europe 2026将于2026年11月10日至12日在奥地利维也纳举行。Tespro已准备了有限数量的免费BT-PLUS蓝牙光学探针样品面向展览参观者。 计划参加展览吗?如果您对我们的BT-PLUS光学探针感兴趣,请提前联系销售团队,预约您的免费样品! 展览详情 样品预订与收集 如有任何疑问或进一步帮助,欢迎随时联系我们的销售团队。 感谢您持续的支持。我们期待在2026年Enlit Europe与您见面! 特斯普罗——一世界一特斯普罗 www.tespro.com

icon_time

November 04, 2026

icon_Check

新闻

无线数据传输的DTU:4G Cat 1 与 NB-IoT

升级远程计量系统的公用事业运营商可能会发现最低成本的蜂窝DTU无法满足其远程轮询和维护需求。在这种配置中,电表或专用数据采集软件负责电表读数,而DTU则提供RS485连接和蜂窝数据传输。尽管预定的电表读数已成功传送到服务器,但远程轮询命令可能会出现延迟,反复连接可能增加功耗,固件更新可能超过可用维护窗口。任何额外的协议处理或自动数据采集能力取决于具体的TD-DTU型号,部署前应予以验证。 这些问题通常源于在LTE第一类和NB-IoT之间的选择。 这两种技术都支持蜂窝机器间通信。但它们在数据量管理、网络访问和电力方面存在差异。分析无线数据传输的DTU选项需要检查整个数据采集周期,而不仅仅是发送到服务器的字节数。 以Tespro工业计量为例,主要问题在于DTU是作为间歇性连接终端,还是作为现场仪器与远程管理系统之间的通信桥梁。 1. 4G Cat 1 和 NB-IoT 在技术上有何不同? LTE运营商在LTE第一类线路使用10 Mbps的下行峰值速率和5 Mbps的上行速率。通过使用其他技术以及在180 kHz载波上采用NB-IoT的窄带信令,可以提升网络覆盖范围。 NB-IoT设计用于小规模且不频繁的数据传输,并能长时间运行一次充电。 工程因素 LTE Cat 1 NB-物联网 无线电带宽 标准LTE运营商 180 kHz 峰值吞吐量 10 Mbps 下载 / ...

icon_time

October 30, 2026

icon_Check

新闻

行业博客

BACnet Modbus 和 OPC UA 工业协议转换器:工程集成指南

建筑管理系统将冷水机温度暴露为BACnet对象,但工厂PLC期望Modbus持有寄存器。设备共享以太网网络,但PLC无法解释BACnet对象标识符、属性或数据类型。 仅靠以太网连接无法解决这种不匹配。集成需要协议解释、地址映射、数据转换以及通信故障的受控处理。 在Tespro,我们评估BACnet Modbus和OPC UA的工业协议转换器与实际通信角色和点列表的关系。我们的TC-100支持这些协议家族,但选择正确的转换方向和数据表示仍是项目级工程决策。 1. 在选择硬件前确认协议方向 BACnet、Modbus 和 OPC UA 在组织和交换信息的方式上有所不同。即使两个设备支持相同的传输网络,它们的应用层数据也可能不兼容。 协议 数据结构 主积分约束 BACnet/IP 对象与属性 对象标识符、Present_Value、状态和命令优先级 BACnet MS/TP 通过RS485的BACnet对象 串行令牌传递拓扑与时序 Modbus RTU/TCP 线圈和16位寄存器 地址偏移、寄存器分组与数据解释 OPC UA 类型化节点与属性 命名空间标识符、访问权、时间戳和数据质量 ...

icon_time

October 29, 2026

icon_Check

新闻

行业博客

Request Your OEM/ODM Solution

Share your requirements, and our hardware and software experts will design a solution optimized for accuracy, reliability, and efficiency.