JPH06266540A - Module input/output sharing system - Google Patents

Abstract

PURPOSE:To provide the module I/O sharing system without the I/O program preparation for each module data and the debugging operation by performing the library processing so as to share the input/output processing of data on the disk data of each module of a controller by computer control and the ROM data. CONSTITUTION:The system consists of a controller program developed by the control of a computer or personal computer CPT1 and data 2. A module processing means 21 divides the unit of job in the hardware structure to be controlled as a module. A data format registering means 22 decides the data format in a module unit. An I/O sharing means 23 shares the I/O processing of initializing data and data required for operation in module units. A processing program preparation means 24 prepares the processing program in module units.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a module I / O sharing system, and more particularly to a module I / O sharing system in software development of a control device.

[0002]

2. Description of the Related Art Conventionally, in software development of a control device controlled by a computer or a personal computer, the unit of work in the hardware to be controlled is divided into modules, and the initial data relating to the data input / output of this module and the data required during operation are classified. Etc. in the program, the disk, the ROM individually in module units,
I was developing software.

[0003]

In the conventional software development of the control device, since the input processing and output processing programs of each module in the hardware are individually created, the development efficiency and speed can be reduced. There was a problem that it did not exist.

An object of the present invention is to store disk data and ROM of each module of a control device under computer control.
The purpose of the present invention is to provide a module input / output sharing method that does not require the input / output program creation and debug work for each module data by creating a library so that the data input / output processing can be shared.

[0005]

According to the module input / output sharing method of the present invention, when a program of a control device is developed by computer control, a unit of work in the hardware to be controlled is divided into modules, and each module is Is characterized in that a portion relating to data input / output processing is made into a library, and when this library is used, input / output processing of disk data or ROM data is performed by specifying a format of module data including a control name and a file name. .

Then, the mode set data of the controller is registered, and if the module data format of the program of the controller is created, the data format of each module is registered, and the data file name of the program of the controller is registered. Is created, the data file name of the control device program is registered, and if the data of the control device program is created, the control name is selected and the item identifier of the module to be used is registered in the auto module. It is characterized in that initialization data of each module and data necessary for operation are registered.

[0007]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Next, the present invention will be described with reference to the drawings.

FIG. 1 is a diagram showing a software configuration of an embodiment of the present invention, and FIG. 2 is a block diagram showing a device configuration of a module input / output sharing system by the software development of FIG.

Referring to FIG. 1, the module input / output sharing method by software development of the control device of this embodiment is as follows.
Computer or personal computer (CPT) 1 and control device program and data 2 developed by controlling it
And a controller program and data 2
Is a modularization unit 21 that divides the unit of work in the hardware configuration to be controlled as a module, a data format registration unit 22 that determines the data format of the module unit, and input / output processing of initial data and data necessary for operation. And an input / output sharing means 23 for sharing each module in a module unit, and a processing program creating means 24 for creating a processing program in a module unit.

A processing program for each module is created by the control device program and the data 2.
Furthermore, this is combined to create one controller program.

Referring to FIG. 2, a personal computer (for example, PC9801 manufactured by NEC) of this embodiment comprises a CRT 11, a main body 12 with a fixed disk, and a keyboard 13, and the main body 1
2 includes a mouse 14, a printer 15, and a ROM writer 1.
6 is connected. Further, a disk storing a system program of the module input / output sharing system and a disk storing the control device program and data 2 shown in FIG. 1 are mounted. The ROM writer 16 inputs the control device program and data 2 into the main body 12 as a ROM program and ROM data.

FIG. 3 is a flow chart showing the system operation flow in FIG.

Referring to FIG. 3, the mode set data of the control device set when the system is started up is registered (step 301). Next, it is checked whether the module data format of the control device program is created (step 302), and if Yes, the module data format is registered. That is, the item identifier (ID) is added to the module data and the condition of the module data structure is input to the disc (step 303).

If No in step 302, it is checked whether the data file name of the control device program is created (step 304). If Yes, the data file name of the control device program is registered in the disk (step 30).
5).

Here, the data file name of the control program is composed of a control name, a data file name and a program name.

If No in step 304, it is checked whether the control program data is created (step 30).
6) If Yes, select the control name (step 30
7) Register the controller program data in the disk. That is, data is input / output according to the format of the module data, and the item ID and other items are registered in the AUTO module (step 30).
8).

If No in step 306, it is checked whether the control program under personal computer control is stored in ROM (step 309). If Yes, the control name is selected (step 310), and the data is automatically converted into the Intel HEX format. Is input to the disk (step 311), the data is further transferred to the ROM writer (step 312), and then the ROM writer writes the data to the ROM (step 313). The control device program ROM and the control device data ROM thus created are attached to the main body of the personal computer and controlled.

Next, the computer controlled control device program, if No in step 309, checks whether control is started (step 314), and if Yes, selects the control name (step 315), and then the control device program. Is read from the disk / ROM and the controller data is A
Control is performed by reading with the item ID of the UTO module (step 316). Here, the control device program corresponding to the item ID registration of the AUTO module is selected.

In step 316, processing is performed according to the control device program and data read from the disk / ROM (step 317), and when this processing is not completed, the processing returns to step 317 (step 318). If No in step 314, it is checked whether the processing is completed (step 319).

When the format registration of the module data is completed in step 303, the registration of the data file name of the control device program is completed in step 305, the data registration of the control device program is completed in step 308, and the step 313 is executed. When the writing of data to the ROM is completed, the process is completed in step 318, and the process is not completed in step 319,
Both return to step 301.

The difference between the operation under the control of the personal computer and the operation under the control of the computer is that the former selects the control program to be controlled and puts the target hardware module in ROM, and the other operations are Is the same.

Further, since debugging of the control device program is performed by a computer, in this embodiment, ICE is used.
(In Circuit Emulator) is not used. In this case, the CPU of the computer and personal computer
Targets mutual relationships.

Next, a specific application example of the present invention will be described with reference to FIGS.

FIG. 4 is a block diagram showing a hardware configuration of a keyboard test apparatus according to an application example of the present invention.

In the keyboard test apparatus of this example of use, a computer keyboard is used as a keyboard under test 410, a solenoid keying section 49 for setting the keyboard 410, an operation box 48 having operation buttons, and an operation box interface for interfacing with the operation box 48. Department (IFA)
44 and a keyboard serial interface unit (IFB) 45 for interfacing with the keyboard under test 410
And solenoid drivers (DRV) 46a, 46b, 46c and 46d connected to the solenoid keystroke unit 49.
, A solenoid driver interface unit (IFC) 46 that interfaces with the DRVs 46a to 46d, a power supply unit (POW) 47, and an IFA 44, through a bus 43.
The bus interface unit (IFD) 42 is connected to the IFB 45, IFC 46, and POW 47.

By setting the keyboard 410 to be tested on the solenoid key-pressing section 49 and turning on the start button of the operation box, the CPT 41 is set to IFD 42 and bus 43.
And the keyboard under test 4 automatically through IFB45
Ten functional tests are performed, and each unit 42 to 410 of this keyboard test device is divided into modules to develop a control device program.

Next, as an example, the power supply unit (P
The processing operation of the voltage processing module input / output sharing method relating to (OW) DPS control will be described with reference to FIGS. 5 and 6.

FIG. 5 is a diagram for explaining the format registration process of the module data in FIG. 3, and FIG. 6 is a diagram for explaining the data creation process for the control name by the control device program in FIG.

In step 303 shown in FIG. 3, first, the voltage processing program is designed as a data change type program, and along with this, the data format is determined by looking at the screen shown in FIG. Register for the format. In this case, the voltage processing structure is as shown in FIG.
The C language structure shown in (b) is input as it is.

In step 306 shown in FIG. 3, the control name is selected by selecting the control name "DPS TES" from the control program (screen shown in FIG. 6A) containing the voltage processing program.
The module data (voltage setting condition) is input by selecting T ". The module can be selected regardless of the control name.

The JOB ID "3" corresponding to the voltage processing data from the screen shown in FIG. 6B and the module item ID "010" from the screen shown in FIG. 6C are registered in the AUTO module to control the controller. Complete data entry.

FIG. 7 is a flow chart for explaining the operation of the control device program of this application example.

The actual operation of the control program is AUTO
Data is automatically input to each module data structure by the module item ID registered in the module (steps 71 to 73) (step 74), and the test is started by the AUTO program (step 75). The test is performed by calling a function with the module item ID, the result of the voltage test is displayed on the screen (step 76), and the test is completed.

As described above, according to this embodiment, only the processing program for each module needs to be developed using the module input / output sharing method.

[0035]

As described above, according to the present invention, the unit of work of the control device under computer control is divided into modules, and a library is formed so that the input / output processing of disk data and ROM data can be shared. Can input and output data only by specifying the data format.

Therefore, it is not necessary to create and debug a module input / output program, and there is an effect that efficiency and shortening of program development can be achieved.

[Brief description of drawings]

FIG. 1 is a diagram showing a software configuration of an embodiment of the present invention.

FIG. 2 is a block diagram showing a device configuration of a module input / output sharing method by software development of FIG.

FIG. 3 is a flowchart showing a system operation flow in FIG.

FIG. 4 is a block diagram showing a hardware configuration of a keyboard test apparatus according to an application example of the present invention.

5 is a diagram illustrating a process of creating a format of module data in the present example illustrated in FIG.

FIG. 6 is a diagram for explaining data creation and processing for a control name by the control device program in the present example shown in FIG.

FIG. 7 is a flowchart illustrating an operation of a control device program according to an application example of the present invention.

[Explanation of symbols]

1,41 Computer or personal computer (CPT) 2 Control device program and data 11 CRT 12 Main body 13 Keyboard 14 Mouse 15 Printer 16 ROM writer 17 Module input / output sharing system program 21 Modularization means 22 Data format registration means 23 Input / output sharing Means 24 Processing program creation means 42 Bus interface unit (IFD) 43 Bus 44 Operation box interface unit (IFA) 45 Keyboard serial interface unit (IF
B) 46 Solenoid driver interface section (IF
C) 46a, 46d Solenoid driver (DRV) 47 Power supply unit (POW) 48 Operation box 49 Solenoid keying unit 410 Keyboard under test

Claims (2)

[Claims] 1. When a program of a control device is developed by computer control, a unit of work in the hardware to be controlled is divided into modules, and each module is made into a library for a portion related to data input / output processing, and this library is A module I / O sharing method characterized by performing input / output processing of disk data or ROM data by specifying a format of module data including a control name and a file name when used. 2. The mode set data of the control device is registered, and if the format of the module data of the program of the control device is created, the data format of each module is registered, and the data file name of the program of the control device is registered. Is created, the data file name of the control device program is registered, and if the data of the control device program is created, the control name is selected and the item identifier of the module to be used is registered in the auto module. 2. The module input / output sharing method according to claim 1, wherein initialization data of each module and data necessary for operation are registered.