WO2018210007A1

WO2018210007A1 - Configuration debugger implementation method for use with virtual controller

Info

Publication number: WO2018210007A1
Application number: PCT/CN2018/074904
Authority: WO
Inventors: 吴波; 卢海松; 牛洪海; 徐卫峰; 臧峰
Original assignee: 南京南瑞继保电气有限公司
Priority date: 2017-05-18
Filing date: 2018-02-01
Publication date: 2018-11-22
Also published as: CN108959058A; CN108959058B

Abstract

Provided in the present invention is a configuration debugger implementation method for use with a virtual controller, the method comprising: storing algorithm logic of a virtual controller as a logic configuration page and a sequence which is sequentially stored by a module in the page, and accordingly defining a configuration breakpoint data structure; defining a logic configuration page file on the basis of a modular storage structure, and monitoring real-time data of a virtual controller; on the basis of the foregoing, implementing a breakpoint configuration function of a debugger by means of issuing configuration breakpoint information; at the same time, defining a configuration breakpoint list in the virtual controller, storing the configuration breakpoint information, and when executing a control algorithm simulation, determining whether a breakpoint is hit by means of traversing the configuration breakpoint list, and deciding whether the simulation is paused; the virtual controller converting page-by-page, module-by-module, and next-step debugging instruction information which is issued by debugging software into a temporary configuration breakpoint, and implementing said debugging instruction functions according to breakpoint hit logic; when debugging ends, the debugging software issuing an instruction to clear the configuration breakpoint list in the virtual controller.

Description

Configuration method of virtual controller configuration debugger

Technical field

The invention belongs to the field of industrial automation control, and in particular relates to simulation debugging of a virtual controller used in an industrial process control system.

Background technique

In the field of industrial process control, the virtual controller functions as a functional simulation software for industrial process controllers, and has the functions of logic configuration and basic debugging in the simulation controller. However, for the simulation debugging of complex control logic, only by real-time monitoring the trend of variable changes of its operation, often the debugging efficiency is low, and it is impossible to accurately and effectively locate the defects of the logic.

In order to solve this problem, consider adding a new development debugger function to the virtual controller software. By introducing single-step debugging functions such as breakpoint setting and single-step execution, single-step and breakpoint debugging of the control algorithm logic is realized, the debugging efficiency is improved, and the defects of the search logic are more effectively located.

At present, some manufacturers have designed and developed an implementation method of the logic breakpoint debugging function of the industrial control system in the actual controller, and realized some functions of the debugger. The method is based on the compiler execution mechanism of the algorithm configuration. When the algorithm is compiled, the pile point information is inserted into each atomic operation instruction, so that when the upper and lower machines are jointly debugged, the pile point information is used to realize the run to the breakpoint Run to, Single step Step In and single step Step out three types of debugging instructions. The debugger function implemented by this method is not comprehensive, and the insertion of the pile point information causes the algorithm configuration source program to have large changes before and after debugging. The inconsistency of the algorithm configuration source program not only causes the algorithm debugging results to be completely different, but also causes a large disturbance to the controller's operation.

In addition, in the virtual controller software of existing industrial control manufacturers, the debugger function is often not supported.

Summary of the invention

The invention provides a configuration debugger implementation method of a virtual controller, which is based on an explanation execution mechanism of the algorithm configuration, and uses the modularity of the algorithm logic to store it as a series of logical configuration pages, each The logical configuration page consists of common module classes arranged according to the logical sequence of the algorithm. On this basis, the logical configuration page number and the in-page module sequence number are encapsulated into configuration breakpoint information, so as to design the configuration breakpoint technology and implement a series of debugging functions of the debugger.

The method is applicable to the virtual controller of the interpreted simulation, and can be implemented on the logic of the control algorithm configured by any programming language such as the sequential function diagram, the function block, the ladder diagram, the structured text and the instruction list, and specifically includes the following step:

a) defining a modular storage structure, storing the control algorithm logic in the virtual controller as a sequence of logical configuration pages and sequential storage of modules within the page;

b) define the logical configuration page number and the in-page module sequence number as the data structure of the configured breakpoint;

c) generating a logical configuration page file based on the modular storage structure, and after downloading to the virtual controller, the real-time operation monitoring function can be realized by periodically reading the module data set of the logic configuration page;

d) Based on the premise of real-time running monitoring, the breakpoint setting function of the debugger is realized by setting the configuration breakpoint information;

e) Define a list of configured breakpoints and store configuration breakpoint information; when the virtual controller performs control algorithm simulation, determine whether the breakpoint is hit or not by traversing the configured breakpoint list to determine whether the simulation is paused;

f) When the debugging software issues the page-by-page, module-by-module, and next-step debugging instruction information, the debugger in the virtual controller converts it into a temporary configuration breakpoint, and implements the relevant debugging command function according to the breakpoint hit condition;

g) The debug software sends the delete breakpoint command, deletes the specified breakpoint in the configuration breakpoint list; delivers all breakpoint instructions, deletes all breakpoints in the configured breakpoint list.

The modular storage structure as described in the foregoing step a) supports one or more programming languages in a sequential function diagram, a function block diagram, a ladder diagram, a structured text, and/or an instruction list.

The sequence of logical configuration pages and in-page module sequential storage as described in the foregoing step a), in other programming languages other than the function block diagram, is equivalent to the logical POU number and the logical instruction label in the POU.

The logical configuration pages in the above step b) are numbered sequentially, and there may be empty pages in the middle. The modules in each logical configuration page are numbered sequentially, and there is no empty module in the middle.

When a breakpoint hit in step e) above, the logic simulation will suspend execution while refreshing the start information of the simulation execution.

If the debugger in step f) above converts the page-by-page, module-by-module, and next-step debugging instructions into temporary configuration breakpoint information storage, or after the debugger receives the execution instruction, it will start from the new simulation start information. Continue the simulation.

When the temporary breakpoint in step f) is hit, the debugger will automatically delete the temporary configuration breakpoint from the configured breakpoint list, and the logic simulation pauses execution, refreshing the start information of the simulation execution.

Step g) further includes: when all the breakpoints are cleared, the debugger receives the instruction to continue executing, the debugger debugging function ends, and the virtual controller enters the continuous cycle simulation running state.

Compared with the prior art method, the beneficial effects of the present invention are: based on the algorithmic explanation execution mechanism, using its inherent modularity, designing the configuration storage structure, implementing the configuration breakpoint technology, and succeeding in the virtual controller The debugger function is implemented. The invention does not change the source file of the algorithm configuration, and maintains the consistency before and after the logic debugging of the algorithm, not only ensures the reliability of the debugging result, but also minimizes the running disturbance of the virtual controller.

DRAWINGS

Figure 1 Schematic diagram of the configuration structure of the control logic;

Figure 2 is a schematic diagram of a list of configuration breakpoint information;

Figure 3 is a preprocessing flowchart of the debug instruction;

Figure 4 shows the simulation task flow diagram embedded in the debugger.

detailed description

The detailed description of the embodiments of the present invention will be described in detail with reference to the accompanying drawings.

According to the modular method, the control algorithm logic based on the interpretation execution mechanism in the virtual controller is organically organized into a structure based on the logical configuration page and the in-page module storage. On this basis, the configuration breakpoint information structure is defined, and a technical method of configuring breakpoints is proposed to realize the debugger function in the virtual controller.

The whole method is defined from the design and implementation process, and mainly contains three parts, which are described as follows.

First, the configuration structure of the control logic

The control algorithm logic in the virtual controller is generally similar to the implementation mechanism of the industrial controller. Therefore, its configuration logic is usually implemented in five programming languages based on the IEC61131-3 standard, namely sequential function diagram, function block diagram, ladder diagram, structured text and instruction list.

Taking the logic of the function block diagram as an example, due to the complexity of the configuration logic, the configuration algorithm logic usually contains thousands or even tens of thousands of algorithm function blocks and connections, so in order to facilitate management editing, it is generally divided. Configure pages for multiple logics.

Each logical configuration page is usually composed of a wired configuration and an algorithm function block configuration. The line connecting the input of the algorithm function block, indicating the reference source of its input variable. Therefore, the "input connection + algorithm function block" package can be defined as a whole modular storage structure.

Based on this method, each logical configuration page can be divided into sequential queues of a series of modular storage structures according to the execution order of the algorithm function blocks.

As shown in Figure 1, there can be hundreds of pages of logical configuration per virtual controller, which may contain empty pages. There are 0 to hundreds of modular storage structures in each logical configuration page. When the virtual controller performs logic simulation, it executes the sequence of the cycle trigger algorithm logic according to the clock interrupt. That is, according to the increasing order of the logical configuration page numbers, the empty pages are automatically skipped, and each logical configuration page is sequentially interpreted in the order of the modular storage structure.

In several other programming languages, the logical configuration page can be similar to the logical POU number, and the in-page module number is similar to the logical instruction label in the POU.

Second, configure breakpoint technology

The virtual controller describes the control algorithm logic according to the foregoing configuration structure, which is executed in order from the front to the back of the module and the logical configuration page from small to large. Therefore, the logical configuration page number and the in-page module sequence number package are defined as the data structure for configuring the breakpoint information.

Based on the data structure of the configuration breakpoint information, a list of configured breakpoint information is defined in the virtual controller, as shown in Figure 2. The debug software adds and removes breakpoints by managing the list of configured breakpoint information.

On the other hand, when performing a logic simulation, the virtual controller executes a modular storage structure for each interpretation, and traverses the query configuration breakpoint information list according to its number to determine whether to interrupt the interrupt point, and then determines whether it needs to enter the simulation pause state. .

In addition, in order to implement the page-by-page, module-by-module, and next-step debugging functions in the debugger, a temporary configuration breakpoint information list is specifically defined. When the debugger unit receives the instructions of the debug software, it converts it into configuration breakpoint information and stores it in the temporary configuration breakpoint information list.

As a result, the execution of these debug instructions is converted to the implementation of the configuration breakpoint hit rule. The only difference is that the breakpoints in the temporary configuration breakpoint information list are automatically deleted once they are hit.

Third, the debugger implementation method

The virtual controller's debugger function implementation can be divided into two sub-functions: debug instruction pre-processing and debugging functions. The debugging instruction preprocessing mainly refers to that the debugger receives the debugging instruction information sent by the debugging software, and converts the preprocessing into the configuration breakpoint information and the simulation task control information.

According to the configuration breakpoint technology, the debugger's various debugging instructions can be divided into the following four categories:

(1) Single step execution;

(2) page-by-page, module-by-module execution;

(3) Breakpoint setting, deletion, and deletion;

(4) Continue to execute.

As shown in FIG. 3, the debugging instruction preprocessing mainly includes the following method steps: First, the debugger receives the debugging instruction information through network communication, and completes step 301. Then, according to step 302, it is judged whether it is a single step execution instruction. If the instruction is stepped, the process proceeds to step 303, otherwise, the process proceeds to step 304.

In step 303, according to the single-step execution instruction, the simulation start position is set as the first module of the first logical configuration page, and then proceeds to step 312 to set the debug status flag, and the pre-processing of the instruction ends.

In step 304, it is determined whether the debug instruction is a page-by-page, module-by-module execution instruction. If yes, go to step 305, otherwise go to step 306.

In step 305, according to the position information of the last simulation exit, the instructions are executed page by page and module by module, converted into temporary configuration breakpoint information, and stored in the temporary configuration breakpoint queue. Then, proceeding to step 312, the debug status flag is set, and the pre-processing of the instruction ends.

Step 306 is taken to determine whether the debug command is a breakpoint setting, deletion, or all delete command. If yes, go to step 307, otherwise go to step 308.

In step 307, according to the content of the instruction, the configuration breakpoint queue is fixedly added, deleted or cleared. Then proceed to step 312 to set the debug flag, and the pre-processing of this instruction ends.

Step 308 is taken to determine whether the debug instruction is to continue executing the instruction. If yes, go to step 309, otherwise it is another illegal debugging instruction, and the pre-processing of this instruction ends.

In step 309, according to the execution of the instruction, it is determined whether the configuration breakpoint information queue is empty. If it is empty, proceed to step 313, the single-step debugging process ends, and the debug status flag is cleared. Otherwise, proceed to step 312 to set the debug status flag, and the pre-processing of this instruction ends.

After the debug command pre-processing is completed, the virtual controller's simulation task will be interrupted by the debug function interrupt. The detailed flow chart is shown in Figure 4. The simulation operation task flow diagram embedded with the debugger function includes the following method steps: First, proceed to step 401 to start the loop from the simulation start position.

Next, proceeding to step 402, the virtual controller interprets and executes the algorithm block function according to the modular storage structure information. After the execution of the explanation is completed, the process proceeds to step 403 to determine whether or not the configuration breakpoint is hit. If it hits, it proceeds to step 407, otherwise it proceeds to step 404.

Following step 407, after hitting the configuration breakpoint, the simulation task exits the execution state, and records the exit location information, and the simulation ends.

In step 404, if the configuration breakpoint is missed, it is further determined whether the temporary configuration breakpoint is hit. If it hits, it proceeds to step 405, otherwise it proceeds to step 406.

In step 405, the hit temporary configuration breakpoint in the temporary configuration breakpoint information queue is deleted, and then the exit location information is recorded, and the simulation task exits the execution state, and the simulation ends.

In step 406, if the temporary configuration breakpoint is not hit, it is further determined whether the logic simulation of the current control algorithm is executed to the last module. If the simulation has executed the last module, then step 408 is entered, otherwise proceeds to step 402 to continue the simulation execution of the next module.

In step 408, it is determined whether the simulation needs to be continued after the simulation, in order to satisfy the page-by-page, module-by-module, and continuous execution after setting the breakpoint, the debugger can automatically jump from the last page configuration to the first time as needed. A one-page configuration continues to execute.

According to the judgment result, if it is necessary to continue the simulation, the process jumps to step 401, and the above steps are repeated. Otherwise, the simulation task exits the execution state and the simulation ends.

Claims

A configuration controller implementation method for a virtual controller, characterized in that the method comprises the following steps:

a) defining a modular storage structure, storing the control algorithm logic in the virtual controller as a sequence of logical configuration pages and sequential storage of modules within the page;

b) define the logical configuration page number and the in-page module sequence number as the data structure of the configured breakpoint;

c) generating a logical configuration page file based on the modular storage structure, downloading to the virtual controller, and periodically reading the module data set of the logical configuration page to realize real-time operation monitoring;

d) Based on the real-time running monitoring, the breakpoint setting of the debugger is realized by setting the configuration breakpoint information;

e) Define a list of configured breakpoints and store configuration breakpoint information; when the virtual controller performs control algorithm simulation, determine whether the breakpoint is hit or not by traversing the configured breakpoint list to determine whether the simulation is paused;

f) When the debugging software issues the page-by-page, module-by-module, and next-step debugging instruction information, the debugger in the virtual controller converts it into a temporary configuration breakpoint, and implements the relevant debugging command function according to the breakpoint hit condition;

g) The debug software sends the delete breakpoint command, deletes the specified breakpoint in the configuration breakpoint list; delivers all breakpoint instructions, deletes all breakpoints in the configured breakpoint list.
The method for implementing a configuration debugger of a virtual controller according to claim 1, wherein: the modular storage structure in step a) supports sequential function diagram, function block diagram, ladder diagram, and structure One or more programming languages in the text and/or instruction list.
The method for implementing a configuration debugger of a virtual controller according to claim 1 or 2, wherein the logical configuration page in step a) and the sequence stored in the module in the page are sequentially used in the function block. Among other programming languages outside the figure, it is equivalent to the logical POU number and the logical instruction label in the POU.
The method for implementing a configuration debugger of a virtual controller according to claim 1, wherein the logical configuration page of step b) is sequentially numbered, and an empty page exists in the middle, and each logical configuration page is The modules are numbered sequentially, and there are no empty modules in the middle.
The configuration debugger implementation method of a virtual controller according to claim 1, wherein when the breakpoint of step e) is hit, the logic simulation suspends execution and refreshes the start information of the simulation execution.
A configuration debugger implementation method for a virtual controller according to claim 1, wherein the debugger in step f) converts the page-by-page, module-by-module, and next-step debug instructions into temporary configuration breaks. After the point information is stored, or after the debugger receives the execution instruction, the simulation will continue from the new simulation start information.
The method for implementing a configuration debugger of a virtual controller according to claim 1, wherein when the temporary configuration breakpoint in step f) is hit, the debugger automatically deletes the list of configured breakpoints. The temporary breakpoint, while the logic simulation pauses execution, refreshes the start information of the simulation execution.
The configuration debugger implementation method of a virtual controller according to claim 1, wherein the step g) further comprises: when all the breakpoints are cleared, the debugger receives the instruction to continue executing. After the debugger debugging ends, the virtual controller enters the continuous cycle simulation running state.