CN113325810B

CN113325810B - Automatic data interaction method

Info

Publication number: CN113325810B
Application number: CN202110434357.0A
Authority: CN
Inventors: 张翼; 兰永明
Original assignee: Fuzhou Hansi Information Technology Co ltd
Current assignee: Fuzhou Hansi Information Technology Co ltd
Priority date: 2021-04-22
Filing date: 2021-04-22
Publication date: 2022-05-17
Anticipated expiration: 2041-04-22
Also published as: CN113325810A

Abstract

The invention relates to an automatic data interaction method, which comprises the following steps: s1, creating a task for collecting data, wherein the task configuration step comprises: s11, task definition configuration: acquiring an OPC drive type list, a data source type list and an MQ type list which can be selected by a task, and selecting needed OPC drive, data source and MQ from the OPC drive type list, the data source type list and the MQ type list respectively; s12, OPC definition configuration: configuring an access IP address of an OPC service, connecting the OPC service according to the access IP address, reading an OPC label list of the OPC service, and selecting a required OPC label in the OPC label list; s13, data source definition configuration: configuring data source connection information and defining a data processing mode; s14, MQ defines configuration: defining the interaction mode of MQ; s15, job definition configuration: and configuring a field of an OPC label, binding the field and the OPC label, and configuring a timer/trigger, an exception handling mode and a transaction expression.

Description

Automatic data interaction method

Technical Field

The invention relates to the field of computer software, in particular to an automatic data interaction method.

Background

In an industrial manufacturing factory, the control logic of most of equipment runs in a PLC of the equipment, a production work order for managing production and manufacturing and a large number of process factors (people, materials and methods) are stored in a manufacturing management system MOM/MES, in order to realize intelligent manufacturing, information interaction between the equipment and the MOM/MES needs to be communicated, data acquisition and issuing control are realized, the cooperation between the manufacturing management system and workshop equipment is realized, the precision and the efficiency of production management are improved, and visual and transparent management is realized.

As shown in fig. 1, a conventional method for implementing equipment data acquisition and control issue is to respectively develop a plurality of different interfaces according to application scenarios and requirements, types of data, and interface requirements after completing configuration of an OPC Server on a plant network target PLC of a workshop, to implement information interaction (including 2 directions for data acquisition and control issue) between a manufacturing management system and the PLC, and to check a plurality of different program logs or monitor to determine an interface operation state or troubleshoot problems during system operation and maintenance and problem troubleshooting. The above conventional method has the following disadvantages:

disadvantage 1:

the factory equipment quantity is various, more is subdivided according to data classification, use scene, and every customer factory equipment, data use demand are different, consequently need develop many equipment information interface, and development work load is great, consumes more human cost.

And (2) a defect:

the OPC Server configuration software which is mature in the market has a plurality of brands, different technical bases need to be mastered in interface development, and specifications and style differences of interface programs developed by different programmers lead to increase of technical training time and cost consumed by the OPC interface development programmers and larger difficulty in later-stage modification.

Disadvantage 3:

after the traditional method is used for customizing and developing the OPC interface program, the running states of all programs cannot be integrally monitored, part of the interface program is often crashed to cause data abnormity of the whole system, but the abnormal interfaces cannot be accurately positioned, and only one-by-one inspection is performed, so that time and labor are wasted

Disadvantage 4:

the OPC interface program is customized and developed, a third party is required to release a container, the program is required to be modified and released for multiple times in a debugging stage, the process is complicated, artificial misoperation is easy to occur, and the interface debugging and deployment period is long

Disadvantage 5:

under the condition that the quantity of single factory equipment is large and the number of equipment data interaction scenes is large, the quantity of OPC interface programs which need to be developed and deployed is increased along with the increase of the equipment, the data quantity and the interaction scenes, the occupation of hardware resources of a data acquisition server is large, the scenes with data persistence requirements exist, and the occupation of database connection resources is also greatly increased.

Disclosure of Invention

Technical problem to be solved

In order to solve the above problems in the prior art, the present invention provides an automated data interaction method, which improves the work efficiency.

(II) technical scheme

In order to achieve the purpose, the invention adopts the technical scheme that: an automated data interaction method, comprising:

s1, creating a task for collecting data, wherein the task configuration step comprises:

s11, task definition configuration: acquiring an OPC drive type list, a data source type list and an MQ type list which are selectable by the task, and selecting needed OPC drive, data source and MQ from the OPC drive type list, the data source type list and the MQ type list respectively;

s12, OPC definition configuration: configuring an access IP address of an OPC service, connecting the OPC service according to the access IP address, reading an OPC label list of the OPC service, and selecting a required OPC label in the OPC label list;

s13, data source definition configuration: configuring data source connection information and defining a data processing mode;

s14, MQ defines configuration: defining the interaction mode of MQ;

s15, job definition configuration: and configuring a field of the OPC label, binding the field and the OPC label, and configuring a timer/trigger, an exception handling mode and a transaction expression.

(III) advantageous effects

The invention has the beneficial effects that: through the fixed configuration steps, data interaction processing between the data acquisition device and the OPC service can be realized, further, communication connection between the data acquisition device and the PLC is realized, the functions of data acquisition and data transmission are completed, a traditional interface is not required to be developed and deployed independently according to specific scenes, and the working efficiency is improved.

Drawings

Fig. 1 is a schematic structural diagram of a conventional manner for implementing device data acquisition and control delivery in the background art of the present invention;

FIG. 2 is a flow chart of an automated data interaction method of the present invention;

FIG. 3 is a schematic diagram of the interaction structure of a system (named SDTM) using the automated data interactor method of the present invention.

Detailed Description

To facilitate understanding of the invention, the english technical wording of the invention is explained:

1. and (3) OPC: (OLE for Process Control) OLE for Process Control;

2. MQ: (Message Queue) Message Queue;

3. PLC: (Programmable Logic Controller) a Programmable Logic Controller;

4. OPC Server: an OPC server;

5. task Service: task service;

6: OPC Service: an OPC service;

7. DB Service: a database service;

8. MQ Service, message queuing Service;

9. MQ Server: a message queuing server;

10. mail Service: a mail service;

11. mail Server: a mail server;

12、3^rdapplication: a third party application.

Example one

Referring to fig. 2 to 3, an automated data interaction method includes:

s11, task definition configuration: acquiring an OPC drive type list, a data source type list and an MQ type list which are selectable by the task, and selecting needed OPC drive, data source and MQ from the OPC drive type list, the data source type list and the MQ type list respectively; specifically, the name and storage path of the task can be configured; in addition, the OPC drivers in the OPC driver type list comprise RSlinx, WinCC and KEPServer, the data sources in the data source type list comprise Oracle, SQLServer, Mongo and MySQL, and the MQ in the MQ type list comprises ActiveMQ and MQTT;

s12, OPC definition configuration: configuring an access IP address of an OPC service, connecting the OPC service according to the access IP address, reading an OPC label list of the OPC service, and selecting a required OPC label in the OPC label list; information such as label modes, label groups, label group expressions, OPC group definitions and the like can also be configured;

the processing mode comprises table processing, storage process processing and the like, wherein the table processing can select the path of the table and select the mode of inserting/updating/inserting OPC data to process the table;

the storage process processing can select to cache locally and then upload to the database, or select to upload only to MQ without operating the data source;

s14, MQ defines configuration: defining an MQ interactive mode comprising basic configuration, connection configuration, sending configuration and receiving configuration;

the basic configuration comprises selection of interactive texts, wherein Xml texts, json books or custom texts can be selected;

the connection configuration comprises a configuration connection address, a user name and a password;

the sending configuration comprises a configuration destination and a destination type; and configuring a send OPC read data rule, the selectable rule comprising: sending only the latest data rules, not checking the expression rules (including job expression check and database check), executing requirement rules (executing before optionally accessing the database/executing after successfully accessing the database), sending data rules (optionally whether to read OPC data, whether to rewrite OPC data by the database, whether to rewrite OPC data by MQ, and whether to rewrite OPC feedback information by MQ);

the receiving configuration comprises: configuring a receiving address and a type of the receiving address;

s15, job definition configuration: and configuring a field of the OPC label, binding the field and the OPC label, and configuring a timer/trigger, an exception handling mode and a transaction expression. In addition, besides the standard timer configuration, the configuration of a custom timer, a timing period, a monitoring direction, external triggering and the like can be expanded and selected.

Wherein the S1 further comprises:

s16, verifying task configuration: defining a checking configuration for the steps S11-S15, verifying whether the steps S11-S15 have a configuration error according to the checking configuration, if so, prompting the step of the configuration error, and if not, executing S17;

s17, test configuration: defining a test configuration for the task, and testing whether the data transmission of the task is correct according to the test configuration;

s18, log configuration: and defining log configuration for the task, and recording the use condition of the task according to the log configuration.

When new system software is installed for data acquisition, configured tasks can be exported from old system software in batches, and then the tasks are imported into the new system software in batches, so that migration of the tasks is facilitated, and workload of repeated task configuration is reduced.

Wherein said S1 thereafter comprises:

and S2, starting the selected tasks, running the tasks according to the configuration content of the tasks, updating the execution times and success times of the tasks, and if the abnormal tasks exist, performing abnormal reminding on an information prompt column of the abnormal tasks. After the task is started, the task runs in the windows service, and the task execution cannot be influenced by closing the client interface of the method. The task starting can select single task starting, batch starting, starting all tasks and automatically starting all the tasks, and a user can select the tasks to be operated according to requirements.

Wherein said S2 thereafter comprises:

s3, monitoring the starting state, real-time running state, total execution times, success times and information prompt of all tasks, and sending the information prompt

Wherein the S3 includes: and submitting the monitoring content to a task detailed information interface. The main configuration information of the task, including OPC address, database address, MQ address and transaction triggering mode, can also be viewed in the monitoring interface of the client. The running log of a certain task can be directly opened through the log function of the monitoring interface, and possible abnormity can be analyzed.

S31, judging whether MQ information receiving task is configured in MQ definition configuration, if yes, automatically connecting MQ Server and monitoring communication channel, after MQ instruction information is monitored in the communication channel, automatically modifying the value of OPC label in OPC Server according to the received MQ instruction information, completing instruction issue, and returning to monitor the communication channel for next instruction information after the issue is completed;

s32, judging whether the task is configured with a timer or not, if yes, reading the tag value of the appointed OPC tag according to the timer configuration timing, executing step S34, and if not, executing step S33;

s33, judging whether the task is configured with a trigger or not, if so, monitoring the change of the label value of the appointed OPC label according to the trigger, and if the change accords with the data change action limited in the trigger, reading the change value of the changed OPC label;

s34, filtering the tag value of the OPC tag according to the rule of the transaction expression, and judging whether the communication state corresponding to the tag value of the OPC tag meets the requirement according to the configuration requirement of the communication quality;

if not, giving up the data acquisition task, and recording abnormal information according to log configuration;

if yes, executing S35, and recording the data information collected this time according to the log configuration;

s35, the data processing mode defined and configured by the data source comprises the following steps: persisting the acquired data to a processing rule of a database/sending the acquired data to a processing rule of an MQ Server;

if the task configures a processing rule for persisting the collected data to the database, executing step S36;

if the task configures a processing rule for sending the collected data to the MQ Server, executing the step S38;

s36, judging whether the network of the target database configured in the data source definition configuration is connected;

if yes, directly submitting the data to a target database;

if not, the acquired data is persisted to a local cache, and the data is submitted to the target database in sequence after the network of the target database is connected;

s37, judging whether the job definition configuration has label value configuration of an anti-write OPC label;

if not, go to S39;

if yes, modifying the tag value of the OPC tag according to the job definition configuration, and executing S39;

s38, judging whether the network of the MQ Server is connected;

if yes, sending the collected data to the target MQ Server;

if not, the acquired data is persisted to a local cache, and the data is submitted to the MQ Server in sequence after the network of the MQ Server is connected;

and S39, after the execution of the single acquisition task is finished, waiting for the next trigger/timer period to arrive, and starting the task again.

When the task is started, the data acquisition and the data transmission control are automatically executed, if the task is monitored to be abnormal or the task needs to be stopped due to network, power supply and other maintenance work, single task stop, batch task stop and all tasks stop can be carried out. After the task is stopped, the task can be restarted at any time.

In summary, when the method of the present invention is used to complete task configuration, after the operation starts the task, the following processes are executed:

1) and the software system automatically connects a target OPC Server according to OPC information configured by the task, starts task execution if the connection is successful, and prompts that the task is failed to start if the connection is failed.

2) And when the task is executed, judging whether the MQ has receiving configuration, namely control configuration for writing back the PLC, if the MQ has receiving configuration, automatically connecting the MQ Server, monitoring the configured communication channel of the MQ after connecting the MQ Server until instruction information is received in the communication channel, and rewriting the tag value of the corresponding OPC tag according to the received instruction information. After the rewriting of the tag value of the OPC tag is completed, the system is recovered to a state of continuously monitoring new messages.

3) When the collection task starts, firstly judging whether a timer or a trigger is configured for the operation in the task, and if the timer is configured, regularly reading the tag value of a target OPC tag according to a configured rule; and if the label value is the trigger, scanning whether the label value of the OPC label changes, and if the label value changes, triggering subsequent judgment.

4) After reading the tag value of the OPC tag, the system checks the communication quality of the OPC tag according to the configured abnormal judgment rule, and after passing the abnormal judgment rule, the system can perform subsequent processing, otherwise, the system directly discards the current read value.

5) If the data reading is subjected to expression configuration in the operation definition configuration, the system automatically filters the data according to the configured expression, and the subsequent actions of the task can be triggered only through the data judged by the filtering condition, wherein the subsequent actions comprise that the data is persistently stored in a database or is sent to a target MQ Server through a configured MQ; otherwise, the reading task is finished.

6) And the data filtered by the transaction expression rule is used as qualified data read at the current time and is used as subsequent data to be sent of a persistent database or MQ.

7) If the persistent database is configured, the system accesses the database according to the configured target database address, performs database connection and checks whether the network is connected. If the network states of the database are communicated, directly submitting the data to the database; if the database network is interrupted, selecting a local cache function according to the configuration, locally caching the acquired data, and automatically transmitting the data acquired during the network interruption period and locally cached to the database after the database network is restored to be connected.

8) After the data is submitted to the database, if the data has a signal value which is inversely written to the OPC data, the system receives an inverse writing signal and controls to modify the label value of the corresponding OPC label, thereby completing the inverse writing control of the OPC.

9) If the configured collected data is sent to the MQ Server, the system firstly carries out connection according to the configured MQ Server link and judges whether the network state of the system is communicated with the MQ Server. If the data is communicated, the data acquired at this time is directly sent to an MQ Server for a third-party program or a system to subscribe and receive; if the network is interrupted, the data collected this time is processed by local caching, and after the connection with the MQ Server network is recovered, the cached data collected is automatically sent to the MQ Server according to the caching sequence.

10) The configuration of persisting to the database, sending data to the MQ Server may exist simultaneously, or one of them may be selected. After the two data processing is completed, the single acquisition task is finished. If the network interruption condition is met, the breakpoint continuous transmission task is managed by the independent system service, and the ending of the collection task is not influenced.

In summary, according to the automated data interaction method provided by the invention, through fixed configuration steps, data interaction processing with an OPC service can be realized, so that communication connection with a PLC is realized, and functions of data acquisition and transmission are completed, without the need of conventionally developing and deploying an interface individually according to a specific scene. Tasks can be conveniently increased and migrated, and the workload of development and debugging is reduced; the functions of task monitoring and abnormal checking are unified, and the abnormal solving efficiency is improved; when a task is in an operation process, if the connection between the operation equipment and the database/third-party MQ Server is interrupted, if the local cache function is started, the limited amount of data can be stored at this time, and after the network is recovered, the data acquired during the network interruption period is automatically uploaded, so that the integrity of data acquisition is ensured; and meanwhile, a plurality of tasks are supported, so that under the condition of large equipment and data volume, the occupation of hardware resources is greatly reduced, the labor, the time and the hardware resources are saved, and the working efficiency is greatly improved.

The above description is only an embodiment of the present invention, and not intended to limit the scope of the present invention, and all equivalent changes made by using the contents of the present specification and the drawings, or applied directly or indirectly to the related technical fields, are included in the scope of the present invention.

Claims

1. An automated data interaction method, comprising:

s14, MQ defines configuration: defining the interaction mode of MQ;

s15, job definition configuration: configuring a field of the OPC label, binding the field and the OPC label, and configuring a timer/trigger, an exception handling mode and a transaction expression;

the S1 further includes:

s16, verifying task configuration: defining a check configuration for the steps S11-S15, verifying whether the steps S11-S15 have a configuration error step according to the check configuration, if yes, prompting the configuration error step, and if not, executing S17;

s18, log configuration: defining log configuration for the task, and recording the service condition of the task according to the log configuration;

said S1 then includes:

s2, starting the selected tasks, running the tasks according to the configuration content of the tasks, updating the execution times and success times of the tasks, and if the abnormal tasks exist, performing abnormal reminding on an information prompt column of the abnormal tasks;

said S2 then includes:

and S3, monitoring the starting state, the real-time running state, the total execution times, the success times and the information prompt of all tasks, and submitting the monitoring content to a task detailed information interface.

2. The automated data interaction method of claim 1, wherein the S3 comprises:

if yes, directly submitting the data to a target database;

if not, go to S39;

s38, judging whether the network of the MQ Server is connected;

if yes, sending the collected data to the target MQ Server;