JPH03161848A - Program checking device - Google Patents

Abstract

PURPOSE:To shorten a check time and to improve the productivity of software by down-loading a part of a program to a controller in each task to check it, and when an unregistered subroutine exists, deciding the driving state of the controller to process the unregistered subroutine. CONSTITUTION:The controller 1 capable of partially down-loading a program formed by a user in each task is used for executing the program check of only the partially down-loaded task subroutine. When a task subroutine using an unregistered subroutine is down-loaded, the driving state of the controller 1 is decided, and when the state is in an OFF line state, the down-loaded object is made effective and a warning text is transmitted to a tool 3. Consequently the time required for the program check is shortened, program resources are uniformly controlled and the productivity of software is improved.

Description

[Detailed Description of the Invention] [Object of the Invention] [Field of Industrial Application] The present invention is directed to a microcontroller (hereinafter referred to as "tool") from an engineering tool for a microcontroller (hereinafter referred to as "tool") used for program creation. This invention relates to an improvement in a program check device that checks a program when it is downloaded to a controller (abbreviated as a "controller").

[Conventional technology]

Conventionally, such a device downloads all tasks from a tool used for program creation to a controller at once, and then performs a program check on all tasks. Then, if there is an error as a result of the program check, the loaded object is invalidated. Further, if normal, a subroutine nesting check and a subroutine registration status check are performed for each task, and if there is an error or an unregistered subroutine, the loaded object is invalidated. Such processing was performed for all tasks.

By the way, recently, controllers that can perform partial downloading on a task-by-task basis and controllers that can perform downloading even during operation have been developed. However, because we had to download all the tasks that were not needed for the controller and roller and check the program for all tasks, we were not able to fully utilize the functions of the controller and it took a long time to check the program. It was necessary. Also, if the subroutines used by each task are not registered, an error will occur as described above and downloading may not be possible.
Alternatively, it was necessary to load the subroutine without performing a registration check.

[Problem to be solved by the invention]

Therefore, since conventional program checking devices download all tasks, it takes a long time to check the program.Moreover, if a subroutine is not registered, a program check error will occur and loading will not be possible, so software There was a problem that productivity deteriorated.

The present invention was made in view of the above circumstances, and
To provide a program check device capable of shortening the time required for program check, allowing partial loading of even unregistered subroutines, performing unified management of program resources, and improving software productivity. Let 1 be the target.

[Structure of the Invention] [Means for Solving the Problems] In a program check device that performs a program check by checking the program, there is provided a means for downloading a part of the created program to the controller in units of tasks; means for searching for subroutines related to the program and determining the registration status thereof, and when an unregistered subroutine is searched by this means, the controller means for determining the operating state of the controller and invalidating the loaded program object if the controller is online, and validating the loaded program object if the controller is offline. The configuration was as follows.

[Effect]

In the present invention, by taking the above-described measures, a part of the created program is downloaded to the controller in units of tasks, and the program check is performed only on that program, thereby reducing the time required for the program check. is shortened.

Further, subroutines related to the program downloaded to the controller are searched from the subroutine registration table in which the current registration status of subroutines is described. , its registration status is determined. If there is an unregistered subroutine, the operational status of the controller is further determined, and if the controller is online, the objects of that program are invalidated, and if the controller is offline, the objects of that program are validated. Ru. Therefore, even if there are unregistered subroutines, they can be downloaded depending on the operating state of the controller, and program resources can be centrally managed by the controller.

〔Example〕

Embodiments of the present invention will be described below with reference to the drawings.

FIG. 1 is a diagram showing a schematic hardware configuration of a program check device according to an embodiment. In this program check device, a controller 1 is connected to a tool 3 via a communication line 2, and a program portion in units of tasks is downloaded from the tool 3 to the controller 1 to perform a program check.

Inside the controller 1, there are two CPUs with different operations.
There is an A-CPUI1 and a B-CPU12.

The A-CPU II operates based on the flowcharts shown in FIGS. 2 and 3, receives text for downloading from the tool 3, and stores the text in the status memory 13.
Controller status (operating status) stored in
A program check is executed while referring to , and if it is normal, the downloaded object is stored in the program memory 14. The B-CPU 12 sets the operating state of the controller 1 in the status memory 13, sequentially executes objects in the program memory 14, and communicates with the input/output memory 15.

Next, the specific operation of this embodiment will be explained with reference to FIGS. 2 and 3. As shown in FIG. 2, when a program is downloaded from the tool 3 to the controller 1 in units of tasks, a program unit check of the downloaded task or subroutine is executed (step Sl). If there is an error in this check, send the error text containing the error information to Tool 3.
and invalidate the downloaded object. If the individual program check is normal, then it is determined whether the downloaded object is a subroutine (step S2). As a result, if the downloaded object is a subroutine, perform a subroutine nesting check (
Step S3). If there is an error in this check, the error text is sent to the tool 3 and the downloaded object is invalidated. Furthermore, if it is determined in step S2 that the loaded object is a task, a subroutine registration status check is executed (step S4).

The subroutine registration status check will be described in detail below. FIG. 3 is a flowchart showing the specific processing contents of the subroutine registration status check. The subroutine registration status check is performed using the subroutine registration table shown in FIG. This subroutine registration table is stored in the program memory 4 inside the controller.
The status of currently registered subroutines FNI to FNn is "Subroutine number", "Subroutine registration", "Call statement used", "Number of upper level tasks", "Number of upper level subroutines", and "Warning".
It is written as the presence or absence of.

In the subroutine registration status check, first, it is checked whether the downloaded task or subroutine is a modification of the old content or a new registration (step S11). As a result, in the case of a change to the old contents, the call statement of the downloaded object is searched, and if there is a subroutine in use, the area corresponding to the subroutine number in the subroutine registration table is searched. The "upper level number" is subtracted by one and the subroutine registration table is rewritten (step S12). In other words, when the old object is a task,
Subtract the "Number of upper level tasks", and if the old object is a subroutine, "Number of upper level subroutines"
Subtract.

Next, search for the call statement of the newly downloaded object, and if there is a subroutine in use, check the "upper level number" in the area corresponding to the subroutine number in the subroutine registration table. The subroutine registration table is rewritten (step S13). In other words, when the newly downloaded object is a task,
0 number of tasks. Also, when the new object is a subroutine, add the "Number of upper level subroutines" of the corresponding subroutine number, set "Subroutine registration" to "Yes", and if a call statement is used, "Use call statement". is “exist”.

Next, in the subroutine registration table, select "Number of upper level tasks"
For subroutines where the sum of "Number of Upper Level Subroutines" is not "O" and "Subroutine Registration" is "No", "Warning" is set to "Yes", and for other subroutines, "Warning" is set to "No". shall be. That is, if "subroutine registration" has not been performed even though there is a higher-level task or higher-level subroutine that uses the subroutine (if there is an unregistered subroutine), "warning" becomes "present". Therefore, we searched the subroutine registration table for all subroutines used by the downloaded object, and checked if "warning" was "present".
If there is no subroutine that is , it is determined that there is no unregistered subroutine 11, and if even one "warning" is "present", it is determined that there is an unregistered subroutine (step S14).
).

If "warning" is "absent" for all subroutines searched, the downloaded object is registered in the program memory 14 (step S15), and normal text is sent to the tool 3 (step S16).

On the other hand, if there is a "warning" in even one of the searched subroutines, it is assumed that the subroutine has not been registered, and the operating state of the controller 1 is checked (step S17).
. As a result, if the operating state of the controller 1 is online, an error text is sent to the tool 3 to invalidate the downloaded object (step S18). Furthermore, if the operating state of the controller 1 is offline, the downloaded object is not immediately invalidated but is registered in the program memory 14 (step 819), and a warning text is sent to the tool 3 (step 12 S20). ).

According to this embodiment, a controller that can partially download a user-created program in units of tasks is used to check the program only for partially downloaded tasks and subroutines. Compared to the conventional method of checking the registration status of subroutines used by all tasks, the time required for program checking can be significantly reduced.

Also, tasks that use unregistered subroutines. When the subroutine is downloaded, the operating state of controller 1 is determined, and if it is offline,
Since the downloaded object is enabled and the warning text is sent to the tool 3, even if the program configuration is incomplete, program resources can be unified within the controller 1 when offline. Therefore, since multiple operators can download objects at any time using multiple tools, software productivity can be improved.

[Effects of the Invention] As detailed above, according to the present invention, the time required for program checking can be shortened, partial downloading is possible even if there are unregistered subroutines, and program resources can be centrally managed. It is possible to provide a program check device that can improve software productivity.

[Brief explanation of the drawing]

FIG. 1 is a block diagram showing the hardware configuration of the embodiment.
2 is a flowchart showing the process of checking the program, FIG. 3 is a flowchart showing the process of checking the subroutine registration status, and FIG. 4 is a diagram showing the subroutine registration table arranged in the program memory. 1... Controller, 2... Communication line, 3...
Tools, 11.12... CPU, 13... Status memory, 14... Program memory, 15... Input/output memory.

Claims (1)

[Claims] A program check device that downloads a created program to a controller and checks the program, comprising means for downloading a part of the created program to the controller in units of tasks; means for creating a subroutine registration table in which a subroutine registration state of the subroutine is described; and means for searching the subroutine registration table for a subroutine related to a program downloaded to the controller in units of tasks, and determining the registration state thereof. If an unregistered subroutine is retrieved by this means, the operating state of the controller is determined, and if the controller is online, the object of the program downloaded to the controller is invalidated; A program checking device comprising: means for validating the downloaded program object if the controller is in an offline state.