Data acquisition terminal and system data interaction method based on data acquisition terminal

Abstract

The invention relates to the field of data acquisition, in particular to a data acquisition terminal and a system data interaction method based on the data acquisition terminal. The data acquisition terminal comprises a control unit used for scheduling each module to work; the communication module is used for establishing network connection with a far-end cloud platform; the serial communication interface is used for connecting field industrial equipment; the configuration management module is used for locally or remotely configuring network parameters and serial port parameters; the data transparent transmission module is used for executing a transparent transmission function. The system data interaction method based on the data acquisition terminals comprises the steps that a cloud platform creates a device file for each data acquisition terminal and binds a protocol analysis template; the data acquisition terminal reads an original data packet sent by the industrial equipment from a serial port, and transparently transmits the original data packet to the cloud platform through a network; the cloud platform receives the original data packet and analyzes the original data packet, and structured data obtained after analysis is stored in a database; the cloud platform generates a control instruction, sends the control instruction to a specified terminal through a network, and transmits the control instruction to industrial equipment through the terminal.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of data collection, in particular to a data collection terminal and a system data interaction method based on the data collection terminal. BACKGROUND

[0002] Currently, there are two kinds of data collection schemes in the field of industrial Internet of Things. One is a centralized collection gateway with a built-in protocol library. This kind of gateway has multiple industrial protocols (such as Modbus, Profibus, OPCUA, etc.) built-in. After analyzing the device data on site, the data is uploaded to the cloud platform. The disadvantage is that the protocol has poor expandability. Each time a new protocol or device variant is added, the gateway firmware needs to be upgraded, which has high maintenance cost and is not flexible to deploy. The gateway has limited processing capacity and is difficult to handle a large number of different protocols. The hardware cost of the gateway is relatively high. The other is a pure transparent terminal (DTU) that forwards the serial port data to the network. The disadvantage is that all protocol analysis work is on the cloud. The cloud needs to develop a large number of private protocols, which is a huge workload. The cloud cannot automatically identify the protocol corresponding to the data source, and needs to be manually configured, which is prone to errors. SUMMARY

[0003] In order to solve the technical problems existing in the centralized collection gateway with a built-in protocol library and the pure transparent terminal, one purpose of the present application is to provide a data collection terminal and a system data interaction method based on the data collection terminal.

[0004] To achieve the above-mentioned purpose, the embodiment of the present application provides a data collection terminal, comprising: a control unit for scheduling the work of each module; a communication module for establishing a network connection with a remote cloud platform; a serial communication interface for connecting field industrial devices; a configuration management module for locally or remotely configuring network parameters and serial port parameters; a data transparent transmission module for performing transparent transmission function.

[0005] To achieve the above-mentioned purpose, the embodiment of the present application provides a system data interaction method based on the data collection terminal, comprising: S1. The cloud platform creates a device file for each data collection terminal and binds a protocol analysis template to it; S2. The data collection terminal reads the original data frame sent by the industrial device from the serial port and packs it, and transmits it to the cloud platform through network transparent transmission; S3. The cloud platform receives the original data packet and analyzes it, and stores the structured data obtained after analysis into the database; S4. The cloud platform generates control instructions and sends them to the designated terminal through the network, and the terminal transmits them to the industrial equipment.

[0006] In the technical solution, the template in the step S1 includes rules and scripts for analyzing the data of the equipment connected to the terminal.

[0007] In the technical solution, the data packet in the step S2 implicitly or explicitly contains the unique identifier of the terminal.

[0008] In the technical solution, the step S3 specifically includes: S31. The cloud platform receives the data packet and retrieves the bound protocol analysis template according to the unique identifier; S32. The cloud platform calls the built-in script engine to execute the analysis script in the protocol analysis template, and the analysis script takes the raw data byte stream as input and outputs the required data after analysis; S33. The analyzed data is stored in the database for use by the upper-layer application.

[0009] Additional aspects and advantages of the present application will become apparent from the following description, or will be learned by practice of the present application. BRIEF DESCRIPTION OF DRAWINGS

[0010] The above and / or additional aspects and advantages of the present application will become apparent and be readily understood from the following description, taken in conjunction with the accompanying drawings, in which: Figure 1 is a system architecture diagram of the present application; Figure 2 is a hardware architecture diagram of the terminal of the present application; Figure 3 is a data interaction flowchart of the present application; Figure 4 is a cloud protocol adaptation flowchart of the present application; Figure 5 is a protocol analysis script flowchart of the present application; DETAILED DESCRIPTION In order to more clearly understand the above-mentioned purposes, features and advantages of the present application, the present application will be further described in detail below in conjunction with the drawings and specific embodiments. It should be noted that the embodiments of the present application and the features in the embodiments can be combined with each other without conflict.

[0011] In the following description, many specific details are set forth in order to provide a thorough understanding of the present application, however, the present application can also be implemented in other ways different from those described herein, therefore, the scope of protection of the present application is not limited by the specific embodiments disclosed below.

[0012] The following description refers to the accompanying drawings that show embodiments of the present application. Figures 1 to 5A data acquisition terminal and a system data interaction method based on the data acquisition terminal are described according to some embodiments of the present application.

[0013] As shown in Figures 1 to 2 , the embodiments of the present application provide a data acquisition terminal, comprising: a control unit for scheduling the work of each module; a communication module for establishing a network connection with a remote cloud platform; a serial communication interface for connecting field industrial devices (such as flow meters, pressure sensors); a configuration management module for locally or remotely configuring network parameters (APN, server address) and serial port parameters (baud rate, data bits), the configuration management module being a common prior art, and the working principle thereof will not be described in detail here; a data transparent transmission module for performing a transparent transmission function, i.e., directly packing and sending the original data byte stream received from the serial port to a designated remote cloud platform through a 4G network without any protocol analysis or processing, and forwarding the original instruction data stream from the cloud platform to the serial port, the data transparent transmission module being a common prior art, and the working principle thereof will not be described in detail here.

[0014] The core feature of the data acquisition terminal is its "functional limitation", the data acquisition terminal itself does not have and perform any industrial communication protocol analysis function, and its only responsibility is to establish a reliable and transparent data channel between the device serial port and the cloud platform.

[0015] Compared with the existing network management with complex functions, the function of the DTU is intentionally limited and reduced to pure transparent transmission, and any form of protocol analysis on the terminal side is excluded.

[0016] As shown in Figures 1 to 5 , the embodiments of the present application provide a system data interaction method based on a data acquisition terminal, comprising: S1. The cloud platform creates a device profile for each data acquisition terminal and binds a protocol analysis template to it, the protocol analysis template including rules and scripts for analyzing the data of the connected devices of the corresponding terminal.

[0017] S2. The data acquisition terminal reads the original data frame sent by the industrial device from the serial port and packs the original data frame to form a data packet, which is transparently transmitted to the cloud platform through a 4G network; the data packet implicitly or explicitly contains a unique identifier (such as IMEI) of the terminal.

[0018] S3. The cloud platform receives the original data packet and analyzes it, and stores the structured data obtained after the analysis into a database, the specific steps being as follows: S31. The cloud platform receives the data packet and retrieves the bound protocol parsing template according to the unique identifier; S32. The cloud platform invokes the built-in script engine to execute the parsing script in the protocol parsing template, wherein the parsing script takes the raw data byte stream as input and outputs structured data (such as JSON format) with clear engineering significance after parsing; S33. The parsed structured data is stored in the database for use by upper-layer applications (such as visualization, data analysis, and alarm).

[0019] Through the three-step data interaction method of "terminal transparent transmission + cloud fingerprint identification + script-based dynamic parsing", the seemingly meaningless raw data stream is accurately and automatically associated with the large protocol script library in the cloud through the "device unique identifier" as a bridge, realizing plug-and-play and automatic parsing of heterogeneous devices.

[0020] The protocol is managed in the form of an executable script template (such as JS), making it a "resource" that can be dynamically loaded, edited, tested, and deployed, rather than a firmware hard-coded in the terminal or platform core code, greatly improving the flexibility and scalability of the system.

[0021] S4. The cloud platform generates a downlink control instruction (encoded as a raw byte stream recognizable by the device) and sends it to the designated terminal through the network, which is then transmitted to the industrial device by the terminal.

[0022] Next, the above steps are further explained with specific examples: 1. Hardware implementation: The data acquisition terminal uses an industrial-grade ARMCortex-M4 chip as the control unit and is externally connected to a domestic 4G Cat.1 communication module. It provides 1 RS-485 and 1 RS-232 interface, uses DC 12-36V wide voltage power supply, and is installed on the DIN rail.

[0023] 2. Software implementation: The terminal runs the FreeRTOS real-time operating system; the software main body has two task threads: one thread monitors serial port data and stores it directly into the sending queue after receiving; the other thread monitors network connection and queue and sends data to the cloud platform `devices / {IMEI} / data` topic through the MQTT protocol.

[0024] 3. Cloud implementation: The cloud platform uses JavaSpringCloud microservices architecture; the protocol adaptation service is the core and is embedded with a JavaScript engine (such as Rhino or Nashorn). The device management module records that the protocol template bound to the device `IMEI-123456` is `MODBUS_RTU_FLOWMETER`.

[0025] 4. Working process: 41. A Modbus flow meter (slave address 01) outputs a data frame: `010304412000007B3C`; 42. The terminal receives the frame data through RS-485 and packages the frame data into a data packet for MQTT publishing; 43. The cloud platform MQTT server receives the message, and according to the IMEI = `123456` in the Topic, queries the JS script `parse_modbus.js` under the `MODBUS_RTU_FLOWMETER` template; 44. The engine executes the script, and the input is the original byte array. The script parses the register value according to the Modbus RTU protocol specification and converts it to a floating point number `10.00`; 45. The output result is: `{"deviceId":"123456","data":{"flowRate":10.00,"unit":"m³ / h"}}`, which is stored in the time series database; 46. The user can see the flow value as 10.00 m³ / h on the platform webpage in real time.

[0026] The present application has the following advantages: 1. Terminal simplification and high reliability: The terminal eliminates the complex protocol stack, has small firmware size, simple logic, low failure rate, and high stability, and is suitable for long-term operation in industrial environments; 2. Infinite protocol expansion: Supporting new protocols only requires developing a new parsing script / template on the cloud, without any upgrade to the terminal firmware, achieving "one-time deployment of the terminal and unlimited expansion of protocols"; 3. Reduce overall cost: The terminal hardware requirement is low, the cost is reduced, the cloud parsing resources can be flexibly expanded, and the protocol development can be reused by all similar devices, reducing the development and operation cost; 4. Convenient deployment and efficient operation and maintenance: On-site personnel only need to complete wiring and network configuration without worrying about protocol details; all protocol maintenance and updates are completed on the cloud, which is very efficient; 5. Improve data parsing accuracy: Automatically match the correct parsing script through "device fingerprint" (unique ID), avoid protocol selection errors caused by manual configuration, and ensure the accuracy of data parsing.

[0027] In the present application, the terms "mounting", "connecting", "connecting", "fixing" and the like should be understood broadly, for example, "connecting" can be fixedly connected, or detachably connected, or integrally connected; "connecting" can be directly connected, or indirectly connected through an intermediate medium. For those skilled in the art, the specific meaning of the above terms in the present application can be understood according to the specific circumstances.

[0028] In the description of the present application, it should be understood that the positions or position relationships indicated by the terms "inner", "outer" and the like are based on the positions or position relationships shown in the drawings, and are only for the convenience of describing the present application and simplifying the description, and do not indicate or imply that the devices or units referred to must have a particular direction, be constructed and operated in a particular position, therefore, it cannot be understood as a limitation on the present application.

[0029] In the description of the present application, the description of the terms "one embodiment", "some embodiments", "a specific embodiment" and the like means that the specific features, structures, materials or characteristics described in connection with the embodiment or example are included in at least one embodiment or example of the present application. In the present application, the illustrative description of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described can be combined in any one or more embodiments or examples in a suitable manner.

[0030] The above is only the preferred embodiment of the present application, and is not intended to limit the present application. For those skilled in the art, the present application can have various modifications and changes. Any modification, equivalent replacement, improvement, etc. within the spirit and principles of the present application shall be included in the protection scope of the present application.

Claims

1. A data acquisition terminal, characterized in that, include: The control unit is used to schedule the work of each module. The communication module is used to establish a network connection with the remote cloud platform; Serial communication interface for connecting to field industrial equipment; The configuration management module is used to configure network parameters and serial port parameters locally or remotely. The data pass-through module is used to perform transparent transmission functions.

2. A system data interaction method based on a data acquisition terminal, characterized in that, include: S1. The cloud platform creates a device profile for each data acquisition terminal and binds a protocol parsing template to it; S2. The data acquisition terminal reads the raw data frames sent by the industrial equipment from the serial port, packages them, and transmits them transparently to the cloud platform via the network; S3. The cloud platform receives the raw data packets, parses them, and stores the resulting structured data into the database; S4. The cloud platform generates control commands, which are sent to designated terminals via the network and then transmitted to industrial equipment.

3. The data acquisition terminal and the system data interaction method based on the data acquisition terminal according to claim 2, characterized in that, The template in step S1 includes rules and scripts for parsing data from the devices connected to the corresponding terminal.

4. The data acquisition terminal and the system data interaction method based on the data acquisition terminal according to claim 2, characterized in that, The data packet in step S2 implicitly or explicitly contains the terminal's unique identifier.

5. The data acquisition terminal and the system data interaction method based on the data acquisition terminal according to claim 2, characterized in that, Step S3 specifically includes: S31. The cloud platform receives data packets and retrieves the bound protocol parsing template based on the unique identifier; S32. The cloud platform calls its built-in script engine to execute the parsing script in the protocol parsing template. The parsing script takes the raw data byte stream as input, parses it, and outputs the required data. S33. Store the parsed data in the database for use by upper-layer applications.

Images