Visual configuration method and system for multi-protocol industrial data acquisition process

Abstract

The present invention belongs to the technical field of network data transmission. Provided are a visual configuration method and system for a multi-protocol industrial data acquisition process. The method comprises: performing acquisition protocol communication process logical topology configuration, generating an acquisition protocol communication logical topology diagram, and editing a data acquisition process in a data acquisition protocol on the basis of a graphical configuration module; compiling the acquisition protocol communication logical topology diagram to generate an instruction code; and in response to data acquisition software loading the instruction code in a driver mode and configuring communication parameters, acquiring data of the corresponding data acquisition protocol. By using the system and method provided in the present invention, on-site engineering implementation personnel can directly create an instruction code of a corresponding acquisition protocol to acquire data, and developers no longer need to develop data acquisition drivers for different data acquisition protocols, thereby reducing development costs and improving the efficiency of industrial data acquisition.

Description

A multi-protocol industrial data acquisition process visualization configuration method and system TECHNICAL FIELD

[0001] The present application belongs to the technical field of network data transmission, and particularly relates to a multi-protocol industrial data acquisition process visualization configuration method and system. BACKGROUND

[0002] In industrial data acquisition, the traditional data acquisition process needs to develop different data acquisition drivers for different protocols. There are many industrial data acquisition protocol standards at present, such as OPC DA, OPC UA, Modbus, 101-104 power protocol, and various data acquisition protocols based on 232 / 485 serial port, TCP, UDP communication protocol, and self-developed protocols provided by some manufacturers. Because a new data acquisition driver needs to be developed for each supported data acquisition protocol, a large amount of development, testing and implementation costs are required for data acquisition work. Supporting new data acquisition protocols also requires development, testing and engineering implementation personnel in the project team to learn and understand the data acquisition protocol to deal with possible data acquisition failure scenarios in the project. The learning cost of the data acquisition protocol is high, especially for some complex data acquisition protocols. SUMMARY

[0003] The present application aims to solve the problem of high time and labor cost in existing industrial data acquisition, and provides a multi-protocol industrial data acquisition process visualization configuration method and system. For special new data acquisition protocols, the system and method provided by the present application can be used by field engineering implementation personnel to directly produce instruction codes corresponding to the acquisition protocol to collect data. The developer no longer needs to develop data acquisition drivers for different data acquisition protocols, saving development costs and improving the efficiency of industrial data acquisition.

[0004] To achieve the above-mentioned purpose, the technical scheme adopted by the present application is:

[0005] The first object of the present application is to provide a multi-protocol industrial data acquisition process visualization configuration system, comprising:

[0006] A protocol communication process logic topology configuration module is used for new data acquisition protocols and visual graphical editing of data formats and interaction processes in the protocol. After editing, a protocol logic topology graph is generated.

[0007] A protocol management module is used to provide naming, saving and importing methods for existing data acquisition protocols. The protocol is stored in a custom text format.

[0008] A protocol logic topology graph compiling module is configured to provide a compiling function to compile the protocol communication flow logic topology graph generated by the protocol communication flow logic topology configuration module, and to generate executable instruction codes;

[0009] A running environment module is configured to provide a running environment for the data acquisition software to load the instruction codes in a driving mode through a fixed interface and to control the start and stop of the instruction codes corresponding to the acquisition protocol.

[0010] Further, the application further comprises:

[0011] A basic communication library module is configured to provide encapsulation of TCP, UDP network communication and 232 / 485 serial port communication;

[0012] A logic operation library module is configured to provide encapsulation of logic operations;

[0013] A mathematical operation library module is configured to provide encapsulation of mathematical operations;

[0014] A check algorithm library module is configured to provide data check algorithms and support custom check algorithm extension;

[0015] A packetization / depacketization library module is configured to provide dynamic arrays and packetization / depacketization algorithms in the communication flow;

[0016] A graphical configuration module is configured to provide a graphical configuration method and support creation and attribute editing of common graphics such as rectangles, ellipses, straight lines and arrows.

[0017] A second object of the application is to provide a multi-protocol industrial data acquisition flow visual configuration method, comprising the following steps:

[0018] Acquisition protocol communication flow logic topology configuration is performed, and an acquisition protocol communication logic topology graph is generated, and data acquisition flows in the data acquisition protocol are edited based on the graphical configuration module;

[0019] The acquisition protocol communication logic topology graph is compiled to generate instruction codes;

[0020] In response to the data acquisition software loading the instruction codes in a driving mode and configuring communication parameters, data corresponding to the data acquisition protocol is acquired.

[0021] As a further improvement of the application, the generation of the acquisition protocol communication logic topology graph is based on the graphical library and the basic algorithm library to edit packetization / depacketization logic topology of the acquisition protocol data sending / receiving flow, and to form the acquisition communication logic topology graph.

[0022] As a further improvement of the application, the data acquisition protocol contains multiple data acquisition flows, and different data acquisition flows can be defined by the user according to different acquisition protocols, and the acquisition protocol communication logic topology graph can be saved in a custom text format.

[0023] As a further improvement of the present application, the collection protocol communication logic topology graph is compiled to generate instruction code, including generating intermediate code according to the collection protocol communication logic topology graph, and optimizing the intermediate code to generate instruction code.

[0024] As a further improvement of the present application, the collection protocol communication logic topology graph is compiled to generate instruction code, including generating intermediate code according to the collection protocol communication logic topology graph, and optimizing the intermediate code to generate instruction code.

[0025] Step S201: new collection protocol configuration, new or import existing collection protocol text, set the collection protocol trigger period;

[0026] Step S202: select the collection protocol basic communication library, communication protocol basic parameter variable definition;

[0027] Step S203: add new data collection flow, the collection flow is divided into two types of data sending flow and data receiving flow;

[0028] Step S204: if the selected collection flow is data sending flow, the data packet flow is edited, the packet header is edited using the packet library, the data is filled according to the protocol requirement, the data check field is added according to the protocol requirement, and the data packet tail is added according to the protocol requirement;

[0029] Step S205: if the selected collection flow is data receiving flow, the data unpacking flow is edited, the data packet header is parsed using the unpacking library, the data is parsed according to the protocol requirement, the data check field is parsed according to the protocol requirement, and the data packet tail is parsed according to the protocol requirement;

[0030] Step S206: determine whether the data collection protocol flow is finished, if the protocol flow is not finished, add the data collection flow according to the collection protocol sequence, repeat steps S203, S204 and S205, if the protocol flow is finished, then go to the next step;

[0031] Step S207: complete the collection protocol configuration, the user checks the data and flow of the collection protocol based on the graphical configuration module, generates the collection protocol communication logic topology graph, names and saves the collection communication logic topology graph, and supports saving the data collection protocol in a custom text format;

[0032] Step S208: the protocol logic topology graph compilation module generates intermediate code according to the collection protocol communication logic topology graph, and optimizes the intermediate code to generate instruction code.

[0033] As a further improvement of the present application, in response to the data collection software loading the instruction code in a driving mode and configuring communication parameters, the start and stop of the instruction code are controlled through a pre-defined interface to complete the data collection of the corresponding data collection protocol.

[0034] As a further improvement of the present application, in response to the data acquisition software loading the instruction code in a driving mode and configuring the communication parameters, data corresponding to the data acquisition protocol is acquired, including the following steps:

[0035] Step S301: loading the instruction code, the data acquisition software loads the instruction code through a preset interface in a specified path;

[0036] Step S302: loading the basic algorithm library, the basic algorithm library includes: a basic communication library, a logical operation library, a mathematical operation library, an algorithm verification library, and a packet assembly / deassembly library;

[0037] Step S303: determining whether the acquisition period has arrived, if the time has not arrived at the acquisition period, delaying a fixed interval time and then continuing to determine, if the time has arrived at the acquisition period, entering the data acquisition process;

[0038] Step S304: loading a data acquisition process and determining the type of the currently loaded data acquisition process;

[0039] Step S305: if the data acquisition process is a data sending process, the instruction code enters a packet assembly process, filling a data packet header according to the data format in the instruction code, filling a data field, if there are multiple pieces of data, then cyclically filling, assembling a verification field, assembling a data packet tail, after the data packet is assembled, calling a sending interface to send the data;

[0040] Step S306: if the data process is a data receiving process, determining the basic protocol type, if the basic protocol is TCP, first receiving a data packet header, analyzing the data packet header, then receiving the remaining data according to the data length defined in the packet header or the instruction code protocol, if the basic protocol is UDP or 232 / 485 serial port, then receiving one complete piece of data at a time; each protocol analyzes the data packet header according to the format, and according to the protocol optional analysis data, if there are multiple pieces of data, then cyclically analyzing, according to the protocol analyzing a data verification field and verifying, according to the protocol optional analyzing a packet tail;

[0041] Step S307: if the data is correctly received and analyzed and the current data packet contains the final data to be acquired, then forwarding the data to a business interface of the acquisition software;

[0042] Step S308: if the data receiving or analysis is abnormal, giving a corresponding prompt and then entering the next acquisition period;

[0043] Step S309: determining whether all the data acquisition processes are loaded, if not, then continuing to load the next acquisition process, repeatedly executing steps S304-S308, if all the data acquisition processes are loaded, then determining whether the next acquisition period needs to be executed to continue to acquire data;

[0044] Step S310: if the next acquisition cycle needs to be executed to continue data acquisition, steps S303-S309 are repeatedly executed, otherwise the protocol data acquisition corresponding to the instruction code is completed.

[0045] A third object is to provide a multi-protocol industrial data acquisition process visualization configuration system, comprising:

[0046] A graphical configuration unit is configured to acquire protocol communication process logic topology configuration and generate an acquisition protocol communication logic topology graph, and edit data acquisition process in the data acquisition protocol based on the graphical configuration module;

[0047] A compiling unit is configured to compile the acquisition protocol communication logic topology graph to generate an instruction code;

[0048] A data acquisition unit is configured to load the instruction code in a driving mode and configure communication parameters in response to data acquisition software, and acquire data corresponding to the data acquisition protocol.

[0049] Compared with the prior art, the present application has the following technical effects:

[0050] The present application provides a system comprising a graphical configuration module, a basic communication library, a logic operation library, a mathematical operation library, an algorithm verification library, a packet assembly / deassembly library, protocol communication process logic topology configuration, a protocol management module, a protocol logic topology graph compiling module, and a running environment module. When a data acquisition protocol is added or modified, a user configures a data acquisition protocol communication process by using the data acquisition process visualization configuration system provided by the present application, generates an acquisition protocol communication logic topology graph, and the protocol logic topology graph compiling module compiles the acquisition protocol communication logic topology graph into an instruction code. The instruction code can be run in acquisition software to complete data acquisition of the corresponding protocol.

[0051] In industrial data acquisition, for a special new data acquisition protocol, a field engineering implementer can directly make an instruction code corresponding to the acquisition protocol to acquire data by using the method provided by the present application. A developer no longer needs to develop a data acquisition driver program for different data acquisition protocols, thereby saving development cost and improving the efficiency of industrial data acquisition. At the same time, the data acquisition protocol is displayed in a graphical manner, so that the data acquisition protocol is easy to understand, and the learning cost of a project team is reduced. When a data acquisition protocol is added, a user defines the data acquisition protocol by using a visualization graphical configuration method. The present application can compile a user-defined data acquisition protocol text to generate an instruction code which can be directly used for data acquisition of the corresponding data acquisition protocol under the support of data acquisition software. The method is also applicable when a standard protocol is slightly modified. After a user imports a standard protocol text, the user edits and saves a process that needs to be modified in a visual manner, and generates a data acquisition instruction code of an adapted non-standard protocol. BRIEF DESCRIPTION OF DRAWINGS

[0052] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiments or prior art description will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor.

[0053] Fig. 1 is a schematic diagram of software module architecture in the embodiments of the present application;

[0054] Fig. 2 is a flow chart of new data acquisition protocol to protocol data acquisition operation in the embodiments of the present application;

[0055] Fig. 3 is a flow chart of data acquisition protocol communication flow logic topology configuration and generation instruction code in the embodiments of the present application;

[0056] Fig. 4 is a flow chart of generation instruction code operation in the embodiments of the present application; DETAILED DESCRIPTION

[0057] In order to make the purpose, technical solutions and advantages of the present application more clear and explicit, the present application will be further described in detail below in combination with specific embodiments and drawings. The present application can also be implemented or applied by other different specific embodiments, and each detail in the present description can be modified or changed based on different views and applications without departing from the spirit of the present application. It should be noted that the following embodiments and features in the embodiments can be combined with each other without conflict.

[0058] Term explanation:

[0059] TCP, Transmission Control Protocol, Transmission Control Protocol;

[0060] UDP, User Datagram Protocol, User Datagram Protocol.

[0061] Modbus protocol is a general language applied to electronic controllers, which is used to realize communication between controllers, controllers and networks and other devices. It has become a general industrial standard, and control devices produced by different manufacturers can be connected into an industrial network for centralized control through the protocol.

[0062] OPC UA protocol, Open Platform Communications Unified Architecture, full name "open production control and unified architecture", is a technical specification for communication between different devices and systems. It is an open technical standard that can be applied to different devices and systems. As long as it supports OPC UA, various devices (such as sensors, controllers, industrial devices, etc.) can communicate with each other to achieve seamless integration.

[0063] CRC16: Cyclic Redundancy Check 16, 16-bit cyclic redundancy check.

[0064] CRC32: Cyclic Redundancy Check 32, 32-bit cyclic redundancy check.

[0065] BCC: Block Check Character, block check character.

[0066] LRC: Longitudinal Redundancy Check, longitudinal redundancy check.

[0067] MD5: Message-Digest Algorithm 5, Message-Digest Algorithm 5.

[0068] Referring to FIG. 1, the present application provides a multi-protocol industrial data acquisition process visualization configuration system, comprising: a graphical configuration module, a basic communication library, a logic operation library, a mathematical operation library, an algorithm verification library, a packet / decoding library, a protocol communication process logic topology configuration, a protocol management module, a protocol logic topology graph compilation module, and a running environment module.

[0069] The graphical configuration module is used to provide a graphical configuration method, supporting the creation and attribute editing of common graphics such as rectangles, ellipses, straight lines, and arrows;

[0070] The basic communication library module is used to provide encapsulation of TCP, UDP network communication and 232 / 485 serial port communication;

[0071] The logic operation library module is used to provide encapsulation of common logic operations, such as loop operations, branch judgments, logical and, logical or, and logical not operations;

[0072] The mathematical operation library module is used to provide encapsulation of common mathematical operations, such as addition, subtraction, multiplication, division, and remainder operations;

[0073] The verification algorithm library module is used to provide common data verification algorithms and support custom verification algorithm extensions;

[0074] A pack / unpack library module is configured to provide a dynamic array and a pack / unpack algorithm in a communication flow;

[0075] A protocol communication flow logical topology configuration module is configured to newly create a data acquisition protocol and visually edit a data format and an interactive flow in the protocol by using a graphical form, and generate a protocol logical topology graph after the editing is completed.

[0076] A protocol management module is configured to provide naming, saving and importing methods for an existing data acquisition protocol, and store the protocol in a self-defined text format.

[0077] A protocol logical topology graph compiling module is configured to provide a compiling function, compile a protocol logical topology graph generated by the protocol communication flow logical topology configuration module, and generate executable instruction codes.

[0078] A running environment module is configured to provide a running environment for the instruction codes by a fixed interface in a driving mode, load the instruction codes, and control the instruction codes to start and stop the corresponding acquisition protocol.

[0079] The system can visually display the data format and the data interactive flow in the protocol based on the graphs provided by the graphical configuration module, and allow a user to edit the data acquisition protocol in a graphical editing mode.

[0080] The multi-protocol industrial data acquisition flow visual configuration system can realize visual editing, configuration, verification, compilation and running management of the data acquisition protocol by integrating multiple modules, and greatly improves flexibility and maintainability of the industrial data acquisition system. The following describes the modules.

[0081] A graphical configuration module is a user interface basis of the system, and can make a user intuitively create and edit various graphical elements (such as a rectangle, an ellipse, a straight line, an arrow and the like) by providing graphical tools, and the graphical elements represent different components or steps in the data acquisition protocol. The graphical configuration module supports editing of properties of the graphical elements, such as color, size, label and the like, to more clearly express a logical structure and a data flow direction of the protocol.

[0082] A basic communication library module encapsulates TCP, UDP, 232 / 485 basic communication protocols, and provides underlying communication support for data transmission in a data acquisition process. By calling the encapsulated communication interfaces, a user can conveniently perform data transmission between different devices and systems without deeply understanding details of the underlying communication protocols.

[0083] The logic operation library provides basic logic operation functions such as loop, branch judgment, logical AND, logical OR, logical NOT, and the mathematical operation library supports common mathematical operations such as addition, subtraction, multiplication, division and remainder. The two libraries provide strong support for data processing in the data acquisition protocol, allowing users to perform complex logic and mathematical operations on data as needed.

[0084] The check algorithm library module provides a variety of common check algorithms and supports user-defined check algorithm extensions. This helps to discover and correct data errors in time during data acquisition, improving data reliability.

[0085] The packing / unpacking library module provides dynamic array and packing / unpacking algorithms in communication processes, supporting users to pack and unpack data according to the requirements of communication protocols, ensuring that data can be correctly transmitted and parsed.

[0086] The protocol communication flow logical topology configuration module allows users to create new data acquisition protocols and visually edit the data format and interaction flow in the protocol through a graphical interface. After editing, the system will automatically generate a protocol logical topology diagram to intuitively display the structure and flow of the protocol.

[0087] The protocol management module provides naming, saving, importing and other functions for existing data acquisition protocols. Protocols are stored in a custom text format, making it easy for users to version control and backup.

[0088] The protocol logical topology diagram compilation module is responsible for compiling the protocol logical topology diagram generated by the protocol communication flow logical topology configuration module to generate executable instruction code. These instruction codes will be loaded and executed by the runtime environment module to implement the functions of the data acquisition protocol.

[0089] The runtime environment module, as the core execution module of the system, provides a runtime environment for the data acquisition software. Through a fixed interface in drive mode, the instruction code is loaded and the start and stop of the instruction code corresponding to the acquisition protocol is controlled, realizing the automation and intelligent management of the data acquisition process.

[0090] Therefore, the multi-protocol industrial data acquisition process visual configuration system of the present application realizes efficient, flexible and visual configuration and management of data acquisition protocols through advanced technical means such as graphical configuration, modular design, instruction code compilation and automated operation.

[0091] Referring to FIG. 2, the application provides a multi-protocol industrial data acquisition process visualization configuration method, protocol configuration and operation including the following steps:

[0092] Step S101: a graphical configuration environment, a basic communication library, a verification algorithm library, a logical operation library, a mathematical operation library, and a packet assembly / depacket library basic running environment are provided;

[0093] Step S102: an acquisition protocol communication process logical topology configuration is performed, and an acquisition protocol communication logical topology graph is generated; a data acquisition process in a data acquisition protocol is edited based on a visualization graphical configuration module; the data acquisition protocol can include multiple data acquisition processes; different data acquisition processes can be defined by a user according to different acquisition protocols; and the acquisition protocol communication logical topology graph can be saved in a self-defined text format;

[0094] Step S103: the acquisition protocol communication logical topology graph is compiled, and instruction codes are generated; the application provides a built-in protocol logical topology graph compilation module, which is used for acquisition protocol communication logical topology graph intermediate code generation, optimization and instruction code generation;

[0095] Step S104: a data acquisition software loads the instruction codes generated in step S103 in a driving mode and configures communication parameters; the data acquisition software starts and stops the instruction codes through a pre-defined interface to acquire data corresponding to the data acquisition protocol.

[0096] The multi-protocol industrial data acquisition process visualization configuration method provided by the application is characterized in that a graphical interface and a modular design are used to realize rapid configuration, compilation and operation of a data acquisition protocol.

[0097] Firstly, a graphical configuration environment, a basic communication library, a verification algorithm library, a logical operation library, a mathematical operation library and a packet assembly / depacket library are provided as basic running environments. These environments provide necessary support and tools for subsequent protocol configuration and compilation. A user can edit a data acquisition process in a data acquisition protocol through a visualization graphical configuration module. This step allows the user to define multiple data acquisition processes and perform individualized configuration according to different requirements of the acquisition protocol. After editing, the system generates an acquisition protocol communication logical topology graph, which visually shows the structure and process of the protocol and can be saved in a self-defined text format for version control and backup. A built-in protocol logical topology graph compilation module is responsible for converting the acquisition protocol communication logical topology graph into executable instruction codes. This step includes intermediate code generation, optimization and final instruction code generation. The compiled instruction codes will be used in subsequent data acquisition processes. A data acquisition software loads the compiled instruction codes in a driving mode and configures corresponding communication parameters. Through a pre-defined interface, the software can control the start and stop of the instruction codes, thereby realizing data acquisition of the corresponding data acquisition protocol.

[0098] The application greatly reduces the technical threshold and complexity by editing and configuring data acquisition protocols through a graphical interface. The graphical method is used to display the data acquisition protocol, which is convenient for users to understand the data acquisition protocol. The definition of multiple data acquisition processes and protocols is supported, and users can perform personalized configuration according to actual needs. At the same time, the saving and backup of custom text format are supported, which is convenient for version control and historical tracing.

[0099] The built-in compiling module can automatically generate and optimize instruction codes, improving the efficiency and accuracy of data acquisition. At the same time, the automation of the compiling process reduces the possibility of human intervention and errors. The data acquisition software controls the start and stop of the instruction codes in real time through a predefined interface, ensuring the real-time and accuracy of data acquisition. This is particularly important for industrial scenarios that require real-time monitoring and control.

[0100] The multi-protocol industrial data acquisition process visualization configuration method provided by the application has the advantages of visual editing, high flexibility, compilation optimization, easy integration and expansion, and strong real-time performance, which can significantly improve the efficiency and accuracy of industrial data acquisition.

[0101] Referring to FIG. 3, the application embodiment provides a method for configuring and generating instruction codes of a data acquisition protocol communication process logic topology, including the following steps:

[0102] Step S201: New acquisition protocol configuration, new or import existing acquisition protocol text, set acquisition protocol trigger period;

[0103] Step S202: Select acquisition protocol basic communication library, which can support TCP, UDP, 232 / 485 serial port, communication protocol basic parameter variable definition, such as IP, port, serial port parameter;

[0104] Step S203: Add one data acquisition process, which includes data sending process and data receiving process;

[0105] Step S204: If the selected acquisition process is data sending process, edit the topology of data packet assembly process, use packet assembly library to edit packet header, optionally fill data according to protocol requirements, optionally add data check field according to protocol requirements, and optionally add packet tail according to protocol requirements;

[0106] Step S205: If the selected acquisition process is data receiving process, edit the topology of data packet disassembly process, use packet disassembly library to parse packet header, optionally parse data according to protocol requirements, optionally parse data check field according to protocol requirements, and optionally parse packet tail according to protocol requirements;

[0107] Step S206: judging whether the data acquisition protocol flow is finished, if the protocol flow is not finished, adding the data acquisition flow according to the acquisition protocol sequence, repeating the execution of step S203, step S204 and step S205, if the protocol flow is finished, entering the next step;

[0108] Step S207: completing the acquisition protocol configuration, the user checks the data and flow of the acquisition protocol based on the graphic configuration module, generates the acquisition protocol set communication logic topology graph, names and saves the acquisition communication logic topology graph, and supports saving the data acquisition protocol in a self-defined text format.

[0109] Step S208: the protocol logic topology graph compiling module generates the intermediate code according to the acquisition protocol set communication logic topology graph, and optimizes the intermediate code to generate the instruction code.

[0110] Referring to FIG. 4, the embodiment of the application provides a method for running the instruction code, the data acquisition software loads the instruction code and the basic algorithm library in a driving mode, after the communication parameters are configured, the start and stop of the instruction code are controlled through a pre-defined interface to complete the data acquisition of the corresponding data acquisition protocol, including the following steps:

[0111] Step S301: loading the instruction code, the data acquisition software loads the instruction code through a pre-set interface in a specified path;

[0112] Step S302: loading the basic algorithm library, the basic algorithm library includes: a basic communication library, a logic operation library, a mathematical operation library, an algorithm verification library, a packet assembling / depacket library;

[0113] Step S303: judging whether the acquisition period is reached, if the time has not reached the acquisition period, delaying a fixed interval time and then continuing to judge, if the time has reached the acquisition period, entering the data acquisition flow;

[0114] Step S304: loading a data acquisition flow and judging the type of the currently loaded data acquisition flow;

[0115] Step S305: if the data acquisition flow is a data sending flow, the instruction code enters a packet assembling flow, filling a packet header, an optional data field according to the data format in the instruction code, if there are multiple data, cyclically filling, assembling a verification field, a packet tail, after the data packet is assembled, calling a sending interface to send the data;

[0116] Step S306: If the data flow is a data receiving flow, the base protocol type needs to be judged. If the base protocol is TCP, the data packet header is received first, the data packet header is parsed, and the remaining data is received according to the data length defined in the packet header or instruction code protocol. If the base protocol is UDP or 232 / 485 serial port, one complete data is received at a time. Each protocol parses the data packet header according to the format, and according to the protocol optional analysis data, if there are multiple data, the data is parsed in a loop, the data verification field is parsed according to the protocol optional analysis data, and the packet tail is parsed according to the protocol optional analysis data;

[0117] Step S307: If the data is correctly received and parsed and the final data to be collected is contained in the current data packet, the data is forwarded to the collection software business interface.

[0118] Step S308: If the data receiving or parsing is abnormal, the corresponding prompt is given, and the next collection cycle is entered.

[0119] Step S309: It is judged whether all data collection flows are loaded. If not, the next collection flow is loaded, and steps S304-S308 are repeatedly executed. If all data collection flows are loaded, it is judged whether the next collection cycle needs to be executed to continue collecting data.

[0120] Step S310: If the next collection cycle needs to be executed to continue collecting data, steps S303-S309 are repeatedly executed, otherwise the protocol data collection corresponding to the instruction code is completed.

[0121] The instruction code can be stopped by the interface control to end the running data collection flow.

[0122] The embodiment of the application provides a common data verification algorithm module and an interface for user to extend the verification algorithm. The verification algorithm includes parity check, CRC16, CRC32, BCC, LRC, MD5, etc.

[0123] The following is an introduction to several verification algorithms:

[0124] Parity check is a simple verification method. In the data transmission process, it is verified by calculating whether the number of “1” in the data is odd or even. If the number of “1” in the data is odd, it is called odd parity check; if it is even, it is called even parity check.

[0125] CRC16 (cyclic redundancy check 16 bits) is an algorithm for calculating the check value by polynomial. It performs a specific mathematical operation on the data to generate a 16-bit check code. The receiver can recalculate the check code according to the received data, and compare it with the received check code to judge whether the data has error in the transmission process.

[0126] CRC32 (Cyclic Redundancy Check 32-bit) is similar to CRC16, and CRC32 generates a 32-bit check code.

[0127] BCC (Block Check Character) is usually the result of a bitwise XOR operation on a group of data. It processes data byte by byte, and performs an XOR operation on the value of each byte to obtain a check byte.

[0128] LRC (Longitudinal Redundancy Check) is an XOR operation on the same bit of each byte of a group of data to obtain a check byte. It is usually used in serial communication.

[0129] MD5 (Message Digest Algorithm 5) is a widely used hash algorithm that compresses messages of any length into a 128-bit hash value. MD5 is irreversible, that is, it is impossible to reverse the original message from the hash value.

[0130] Support user extension check algorithm, user can use logical operation library and mathematical operation library to perform logical operation and mathematical operation on specified data bits, and define the expected output result. Through the data check module, the user can flexibly use and replace the data check method in the data acquisition process.

[0131] The embodiment of the present application supports naming and saving of the data acquisition protocol, and supports importing of existing data acquisition protocols in a custom text format. Definitions of common data acquisition protocols are provided in advance, including power 102 protocol, power 104 protocol, Modbus, OPC UA protocol.

[0132] In addition to supporting common standard data acquisition protocols, the embodiment of the present application can also be used for extended and changed protocols of industrial data acquisition protocols. By importing standard protocols, protocol communication flow logical topology configuration is performed to support changed protocols of standard protocols, such as extensions of power 102 protocol by different industrial data providers.

[0133] In addition to supporting common standard data acquisition protocols, the embodiment of the present application can also be used for TCP and UDP protocols in different custom formats and processes.

[0134] A third object of the present application is to provide a multi-protocol industrial data acquisition process visualization configuration system, characterized in that it comprises:

[0135] A graphical configuration unit is used for acquiring protocol communication flow logical topology configuration and generating acquisition protocol communication logical topology graph, and is used for editing data acquisition process in the data acquisition protocol based on a graphical configuration module;

[0136] A compiling unit is used for compiling the acquisition protocol communication logical topology graph to generate instruction code.

[0137] a data acquisition unit for acquiring data corresponding to a data acquisition protocol in response to the data acquisition software loading the instruction code in a drive mode and configuring communication parameters.

[0138] A fourth object of the embodiments of the present application is to provide an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the above-mentioned multi-protocol industrial data acquisition process visualization configuration method when executing the computer program.

[0139] A fifth object of the embodiments of the present application is to provide a computer readable storage medium, wherein the computer readable storage medium stores a computer program, and the computer program is executed by a processor to implement the above-mentioned multi-protocol industrial data acquisition process visualization configuration method.

[0140] A sixth object of the embodiments of the present application is to provide a computer program product, wherein the computer program product comprises computer instructions, and the computer instructions instruct a computer to execute the above-mentioned multi-protocol industrial data acquisition process visualization configuration method.

[0141] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system, or a computer program product. Therefore, the present application can adopt a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can adopt a computer program product implemented on one or more computer usable storage media (including but not limited to disk storage, readable storage media, optical storage, etc.) containing computer usable program codes.

[0142] The present application is described with reference to flowcharts and / or block diagrams of the method, device (system), and computer program product according to the embodiments of the present application. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, and the combination of the flows and / or blocks in the flowcharts and / or block diagrams can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing devices produce a device for implementing the functions specified in one or more flows in the flowcharts and / or one or more blocks in the block diagrams.

[0143] These computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instructions which implement the function specified in the flowchart or flowsheets and / or block or blocks of the block diagrams.

[0144] These computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart or flowsheets and / or block or blocks of the block diagrams.

[0145] Finally, it should be noted that the above-mentioned embodiments are merely used to illustrate the technical solutions of the present application, but not to limit it. Although the present application has been described in detail with reference to the above-mentioned embodiments, those skilled in the art should understand that the specific embodiments of the present application can be modified or replaced equivalently without departing from the spirit and scope of the present application, and any modification or equivalent replacement without departing from the spirit and scope of the present application should be covered in the protection scope of the claims of the present application.

Claims

1. A multi-protocol industrial data acquisition process visualization configuration system, characterized in that, Comprise: Protocol communication flow logical topology configuration module, for new data acquisition protocol and the data format and interactive process in the protocol are visualized graphical editing, after editing, generate protocol logical topology graph; Protocol management module, for providing the naming of existing data acquisition protocol, save, import method, protocol storage in custom text format; Protocol logical topology graph compilation module, for providing compilation function, compile the protocol logical topology graph generated by the protocol communication flow logical topology configuration module, generate executable instruction code; Run-time environment module, for data acquisition software for the run-time environment provided by the instruction code, through the fixed interface to drive mode loading instruction code, and control instruction code corresponding to the start and stop of the acquisition protocol.

2. The multi-protocol industrial data acquisition process visualization configuration system of claim 1, wherein, Also include: Basic communication library module, for providing TCP, UDP network communication and 232 / 485 serial communication package; Logical operation library module, for providing the encapsulation of logical operation; Mathematical operation library module, for providing the encapsulation of mathematical operation; Verification algorithm library module, for providing data verification algorithm, and supporting custom verification algorithm extension; Packaging / unpacking library module, for providing dynamic array, communication flow group package / unpack algorithm; Graph configuration module, for providing the method of graphical configuration, supporting the creation and attribute editing of graphical shape.

3. A method for visualizing a multi-protocol industrial data acquisition process configuration, the method comprising: receiving a process configuration file; and displaying a graphical representation of the process configuration file. Comprise the following steps: Acquisition protocol communication flow logical topology configuration, and generate acquisition protocol communication logical topology graph, based on the graph configuration module, edit the data acquisition process in the data acquisition protocol; Compile the acquisition protocol communication logical topology graph, generate instruction code; In response to the data acquisition software in drive mode loading the instruction code and configuring the communication parameters, collect the data corresponding to the data acquisition protocol.

4. The method of claim 3, wherein: The generation of acquisition protocol communication logical topology graph is based on the graph library and the basic algorithm library to edit the package / unpack logical topology of the acquisition protocol data sending / receiving process, forming the acquisition communication logical topology graph.

5. The method of claim 3, wherein the method further comprises: The data acquisition protocol contains multiple data acquisition processes, according to the different acquisition protocols, users can define different data acquisition processes; 6. The method of claim 3, wherein the process visualization configuration method is a multi-protocol industrial data acquisition process visualization configuration method. Compile the acquisition protocol communication logical topology graph to generate instruction code, including generating intermediate code according to the acquisition protocol communication logical topology graph, and optimizing the intermediate code to generate instruction code.

7. The method of claim 3, wherein the process visualization configuration method is a multi-protocol industrial data acquisition process visualization configuration method. Acquisition protocol communication flow logical topology configuration, and generate acquisition protocol communication logical topology graph, based on the graph configuration module, edit the data acquisition process in the data acquisition protocol, comprising the following steps: Step S201: new acquisition protocol configuration, new or import existing acquisition protocol text, set the acquisition protocol trigger period; Step S202: select acquisition protocol basic communication library, communication protocol basic parameter variable definition; Step S203: add new data acquisition process, the acquisition process is divided into two types of data sending process and data receiving process; Step S204: if the acquisition process is selected as data sending process, edit the topology of data packaging process, use the package library to edit the data packet header, fill in the data according to the protocol requirement, add data verification field according to the protocol requirement, and add data packet tail according to the protocol requirement; Step S205: If the selected acquisition process is a data receiving process, the data unpacking process is topologically edited, the data packet header is parsed using the unpacking library, the data is parsed according to the protocol requirement, the data verification field is parsed according to the protocol requirement, and the data packet tail is parsed according to the protocol requirement; Step S206: It is judged whether the data acquisition protocol process is completed. If the protocol process is not completed, the data acquisition process is added in sequence according to the acquisition protocol, and steps S203, S204 and S205 are repeatedly executed. If the protocol process is completed, the next step is entered; Step S207: The acquisition protocol configuration is completed. The user checks the data and process of the acquisition protocol based on the graphical configuration module, generates the acquisition protocol set communication logic topology graph, names and saves the acquisition communication logic topology graph, and supports saving the data acquisition protocol in a self-defined text format.

8. The method of claim 3, wherein the process visualization configuration method is a multi-protocol industrial data acquisition process visualization configuration method. In response to the data acquisition software loading the instruction code in a driver mode and configuring the communication parameters, the start and stop of the instruction code are controlled through a pre-defined interface to complete the data acquisition of the corresponding data acquisition protocol.

9. The method of claim 3, wherein the process visualization configuration method is a multi-protocol industrial data acquisition process visualization configuration method. In response to the data acquisition software loading the instruction code in a driver mode and configuring the communication parameters, the data of the corresponding data acquisition protocol is acquired, including the following steps: Step S301: The instruction code is loaded. The data acquisition software loads the instruction code in a specified path through a pre-set interface; Step S302: The basic algorithm library is loaded. The basic algorithm library includes: a basic communication library, a logic operation library, a mathematical operation library, an algorithm verification library, and a packet assembling / unpacking library; Step S303: It is judged whether the acquisition period is reached. If the time has not reached the acquisition period, the fixed interval time is delayed, and the judgment is continued. If the time has reached the acquisition period, the data acquisition process is entered; Step S304: A data acquisition process is loaded, and it is judged whether the current loaded data acquisition process type is; Step S305: If the data acquisition process is a data sending process, the instruction code enters the packet assembling process, the packet header is filled according to the data format in the instruction code, the data field is filled, if there are multiple data, the cycle is filled, the packet verification field is assembled, the packet tail is assembled, after the data packet is assembled, the sending interface is called to send the data; Step S306: If the data process is a data receiving process, it is judged whether the basic protocol type is TCP. If the basic protocol is TCP, the packet header is received first, the packet header is parsed, the remaining data is received according to the data length defined in the packet header or the instruction code protocol, if the basic protocol is UDP or 232 / 485 serial port, one complete data is received at a time; each protocol parses the packet header according to the format, and parses the data according to the protocol, if there are multiple data, the cycle is parsed, the data verification field is parsed according to the protocol and verified, and the packet tail is parsed according to the protocol; Step S307: If the data is correctly received and parsed, and the final data to be acquired is contained in the current data packet, the data is forwarded to the acquisition software business interface; Step S308: If the reception or parsing of the data is abnormal, a corresponding prompt is given, and the next period of acquisition is entered; Step S309: judging whether all data collection processes are loaded, if not, loading the next collection process, repeating step S304-step S308, if all data collection processes are loaded, judging whether the next collection cycle needs to be executed to continue collecting data; Step S310: if the next collection cycle needs to be executed to continue collecting data, repeating step S303-step S309, otherwise completing the protocol data collection corresponding to the instruction code.

10. A multi-protocol industrial data acquisition process visualization configuration system, characterized in that, Comprise: A graphical configuration unit is configured to collect protocol communication process logic topology configuration and generate a collection protocol communication logic topology graph, and edit data collection processes in the data collection protocol based on a graphical configuration module; A compiling unit is configured to compile the collection protocol communication logic topology graph to generate an instruction code; A data collection unit is configured to respond to the data collection software to load the instruction code in a driving mode and configure communication parameters to collect data corresponding to the data collection protocol.

Images