JPS63120303A - General-purpose controller - Google Patents

Abstract

PURPOSE:To improve maintenance, reliability and extension properties of a system as a whole by separating a standard software area from an optional software area. CONSTITUTION:A standard software area 5 and an optional software area 6 store various information and shift accesses with each other in accordance with an operating procedure. The area 5 consists of a program P1 which controls execution of the software and a subroutine group in addition to an operating system. While the area 6 includes three types of table elements T1-T3 and code parts Q1 and Q2. When an optional task is added to a system, the number of tasks registered in the table T1 is set at +1 with addition of the contact information on the task started in the table T2. In such a way, the area 5 has no change in terms of addition of tasks and therefore independence is secured between the standard software and the optional software.

Description

[Detailed description of the invention] [Objective of the invention] (Industrial application field) The present invention relates to a general-purpose controller comprising:

(Prior technology) In the general industrial field, FA field, etc., existing general-purpose controller devices equipped with standard software and hardware dedicated to data input/output, communication software, and graphic processing are used to adapt to each application field. In some cases, optional software may be added to realize the desired device.

FIG. 4 shows an example of a typical conventional software configuration in such a general-purpose controller. When incorporating optional software, it is difficult to completely separate it from the standard software, and in many cases, the standard software area 2 and optional software area 3 are configured to coexist in the same memory space (ROM > 1) within the system. .

(Problem to be solved by the invention) In such a configuration, for example, standard software area 2
Program a1 in the optional software area 3
If you want to execute task b1 in In addition, when calling another routine a2 in the standard software area 1-ware area 2 from the optional task b1, the pointer q1 indicating the execution start address of that routine must be known. It won't happen.

These pointers P+ and Q+ need to be adjusted each time the location of optional software changes within the memory space 1. In particular, as the scale of system software increases, the complexity increases and software bugs may occur. It may also be the cause.

Since both types of software i-ware are mixed and configured in the same memory space 1 within the system, their independence from each other is lost, and when registering or changing optional software, it is necessary to review the standard software or system There may be cases where it is necessary to reconfigure the entire Dem software, and when changing the developed optional software [Unij7 Test 1-], program failures may occur due to cumbersome procedures and connection errors between programs. It's also easy to wake up.

The present invention has been made in consideration of the above points, and aims to provide a general-purpose controller that can easily create and incorporate optional software by ensuring independence between standard software and optional software. It is.

[Structure of the Invention] <Means for Solving the Problems> In order to solve the problems, the present invention provides standard software P1 to 1-ware that can be commonly used for various control objects.
Extended memory space 6 different from memory space 5 storing P3
In addition, optional software Q+, Q2 and optional software Q+ specific to each type of ML control object are installed.
, Q2 and the standard software P1 to P3 are stored therein, and the standard software is provided with a processing program (FIG. 3) for controlling the execution of the optional software Q+ and Q2.

(Operation) Standard software and software are stored in separate memory spaces 5 and 6.
I set up Narusono 1 hardware and C separately.

This makes it easier to create and incorporate optional software.

In this case, independence cannot be obtained by using a pointer to read out the other party's code (-U1A) in the program itself, so use a code word and a code cap to store it in ObshiEpursono1heueno7areaii!6. The software is transferred to the other party's software 1 by referring to the information 1 to T3 that must be associated.

Therefore, 4? i! 1': There is no need for a pointer or the like in the software and optional software itself to directly read out the other party's software, and the independence of Sugimame can be maintained.

(Example) Below, a practical example of the present invention will be described in detail with reference to the drawings.

In Figure 1, U and CPIJ4 are standard software and A
The standard software area 5 stores programs for controlling the execution of the controller's standard software, operating system, and optional software. It is a memory area.

The optional software is stored as an extended memory in an optional software area 6 separate from the standard software area 5, and this area 6 includes several blocks 68.
It is divided into ~6d, and the size of the area can be selected according to the size of the optional software.
It is designed so that it can be implemented in block units so that M can be switched.

A common memory area 7 in the RAM configuration is a work area that can be used in common by both sonotools. These components 4 to 7 are interconnected by an internal bus 8.

The standard software area 5 and the optional software area 6 store various types of information as shown in FIG. 2, and access can be transferred to each other according to the operating procedure, for example, as shown in FIG. It is made to do. That is, the software area 5 includes, in addition to the operating system, a program P1 that controls the execution of the optional software, and a common subroutine group P2 and P3 called by the optional software. . Optional software area 6 consists of three types of table elements T+, T2.73 and code parts Q1, Q2 of the optional software itself.
It consists of The first table T1 includes system information of the optional software area 6, and this system information includes keywords indicating the validity of the optional software area 6 and the number of registered optional tasks. The second table T2 contains connection information from the standard rough 1 to software to the optional software, and this connection information includes the execution start address of each optional task, the priority of the task, the data area, and the base of the stack area. These include addresses, stack area sizes, initial values passed to each task when the task is started, etc. Third
Table T3 includes connection information from the optional software to the standard rough 1-ware, and this connection information includes the start address of each subroutine in the standard rough 1-ware. Note that all of this information included in table T+-T3 can be changed.

Next, a process for transferring execution from the standard software to optional software as necessary will be described with reference to FIG. Note that the program shown in FIG. 3 is stored in the standard software area 5.

When the program is started, the CPU 4 performs step S1).
, the extended memory area 6 is accessed, and the system information is first read to check whether optional software exists based on keywords (step 32). If a negative result is obtained due to non-existence, the processing of the program is immediately terminated (step 83).

On the other hand, if optional software is present, the number of registered optional tasks is read from table T+, and then it is checked whether the number of registered tasks has been activated (step 84).

Once the number of registered tasks has been activated, the processing of the program is ended (step S3). On the other hand, if there is an optional task that still needs to be started, read the contents of table T2 indicating the connection information from the standard software in the optional software area 6 to the optional software 1 to software, and read the information in the table. Based on this, the specified optional task is activated (step S5). As a result, each optional task is activated and starts its own processing. On the other hand, if it is necessary to execute each subroutine of the standard software within each optional task, the connection information (stored in table T3) to the standard software existing in the optional software area 6 is used. You can link to the necessary subroutines.

In addition, when adding a new optional task to the system, increase the number of task registrations in the table element by 1, add the connection information of the task to be started in the bottom 2 of the table, and add the standard rough 1 in the task. ~ If it is necessary to execute software, register the connection information in the table below 2, and save the actual code part of the task to the optional software area 6.
This can be achieved by placing it in If this method is adopted, there is no need to change the standard software area 5 in connection with the addition of tasks, and independence between the standard software and optional software is maintained.

According to the embodiment described above, since the standard software area and the optional software area are separated and independent, additions, changes, and registration of optional software can be performed without affecting the standard software, and the entire system It is possible to improve maintainability, reliability, and even expandability.

Note that the present invention can be applied not only to industrial general-purpose controllers, but also to consumer general-purpose controllers, and furthermore, to all general-purpose controllers equipped with standard software and optional software.

[Effects of the Invention] As mentioned above, according to the present invention, standard software and A" general software are made independent of each other, and it is possible to easily create and incorporate obscene software. You can get a controller.

[Brief explanation of the drawing]

Fig. 1 is a block diagram showing a general-purpose controller according to an embodiment of the present invention, Fig. 2 is a route diagram explaining the relationship between each software area, and Fig. 3 is a process for controlling the execution of obciconal software. A flowchart showing the program, and FIG. 4 is a route map showing a conventional general-purpose controller. 4...CPU 5...Standard software area 6...Optional software area 8...Internal bus

Claims (1)

[Claims] Optional software unique to each of the above-mentioned control objects and
A general-purpose controller, characterized in that information associating the optional software with the standard software is stored, and the standard software is provided with a processing program for controlling execution of the optional software.