JPS58154042A - Control device - Google Patents

Abstract

PURPOSE:To reduce the program capacity and to simplify the constitution of a controller, by providing a common control parameter area in addition to plural individual control parameters corresponding to subordinate devices, as a result, unifying control programs corresponding to said devices. CONSTITUTION:An adaptor 21 of a controller of microprogram system is connected to an interface I and then to a host device. A micro-CPU22 fetches a control program CP provided within a control memory 23 and decodes and executes the program to control the adaptor 21. Then the CPU22 reads the buffer memory 23 and a control register 25 and performs writing. The control memory 25 includes areas of a control parameter A for device A, a control parameter B for device B and a control parameter C for device C in addition to a control program CP area. A buffer memory 24 and the register 25 are divided into areas for devices A and B respectively.

Description

DETAILED DESCRIPTION OF THE INVENTION Object of the Invention The present invention relates to a microprogram type control device for controlling a plurality of lower-level devices, and particularly to a control device suitable for providing means for reducing control programs by sharing parameter management. Regarding.

Prior Art It is a well-known fact that in recent years, with the advancement of large-scale integrated circuit technology, a microprogram control method has been adopted for Shimiko devices.
Furthermore, as hardware capacity has steadily decreased, integrated control systems have been increasingly adopted in which part (buffer memory, control registers, etc.) or all of the hardware of lower-level devices to be controlled is incorporated into the control device.

If an integrated control method is adopted, the power supply, housing, memory access mechanism, etc. required for each lower-level device are integrated into the control device, which is extremely helpful in reducing the cost of the system.

However, due to the integration, the amount of microprograms (control programs) of the control device increases, and it becomes necessary to manage buffers, control registers, etc. for lower-level devices.

Since buffers and control registers are expanded and used with separate addresses, the management parameters used in the control program, such as the start point address, end point address, address information to be accessed, flags, etc., are also divided into addresses corresponding to lower-level devices. It needs to be stored and managed.

Therefore, even when controlling lower-level devices with the same or similar software specifications, since the management parameters differ as mentioned above, the control program must be modularized or routineized to correspond to the lower-level devices, and the microprogram capacity is limited. Conventional control devices have drawbacks that increase and complicate the process.

OBJECTS OF THE INVENTION The purpose of the present invention is to eliminate the above-mentioned problems with conventional control devices, and to provide a control system that allows management parameters to be used without being aware of which lower device is being controlled. An object of the present invention is to provide a control device that reduces program capacity and is simplified.

The present invention is characterized by providing a new common management parameter area in addition to the plurality of individual management parameter areas corresponding to lower-level devices provided in conventional control devices, and providing common management between individual management parameters and with individual management parameters. Arrange the parameters between the parameters in the same order, move the corresponding individual management parameters to the common parameter area when starting control of the lower device, return the common management parameters to the individual management parameter area when the control ends, and By making it necessary to use only common management parameters in the middle, the control programs that were previously separated for lower-level devices were unified into one, thereby reducing and simplifying the program capacity.

Embodiment of the Invention An embodiment of the present invention will be described below with reference to FIGS. 1 to 7. :'i'' FIGS. 4 and 5 show conventional control operations for comparing the effects of the present invention.

FIG. 1 is an example of a system configuration including a control device to which the present invention is applied.

The control device 2 is connected to the higher-level device 1 through an interface, and receives commands from the higher-level device 1 to control the lower-level device 5 (device A) and the lower-level device 4 (device B).

In this description, the number of lower-order devices (hereinafter referred to as devices) is assumed to be two to simplify the description.

FIG. 2 is an example of an internal program diagram of the microprogram type control device 2 according to the present invention.

The adapter 21 is connected to the interface I, performs signal exchange with the host device 1, and controls operations such as startup, data transfer, and termination.

The micro CPU 22 fetches, decodes, and executes the control program CP in the control memory 25 to control the adapter 21, reads the buffer memory 23, and the control register 25, and
Write.

In addition to the control program CP area, the control memory 25 includes:
Each area of management parameter A for device A, management parameter B for device B, and common management parameter C are prepared.

Buffer memory 24! Vise required 2. Control registers 25 are also divided into registers A for device A, registers A for device B, and registers BK for device B.

The management parameters, parameters, and control registers are referred to below as follows.

Parameter ^, balata, -? ri B1 co-spring parameter C,
Buffa A1 Ba, Fa B Luzistan.

Register B1, parameter A1, register A constitutes a device, and parameter B1, buffer B, register B constitutes device B.

Next, one conventional control operation using the control device having the above configuration will be explained.

However, in the conventional control device, the common parameter C area is not prepared in the control memory 23, and the management parameters are only the device-compatible parameters A and B.

FIG. 4 shows an example of a control operation in a conventional control device.

The prerequisites for this example are as follows.

t Both devices A and B accept the same write command.

2. If both devices A and B accept the data code,
Using the buffer address stored in the management parameters, write the data code to the corresponding buffer address.

& If device A accepts the control code, it writes the same code to register A.

If device B accepts the control code, it does nothing and discards the code.

4. For both devices A and B, if the buffer address exceeds the end point address of each buffer, return the buffer address to the start point address.

5. The sizes of buffer A1 and buffer B are different.

Next, using Fig. 4, explain each operation step B.
,,,,.

do.

For device A, Step 1A: Judgment of startup When device A starts → Step 2A In other cases → Step 1B ・Step 2A: Judgment of command For write command → Step 3A For other cases → Other Steps (not shown) - Step 5A: Judgment of termination If termination is instructed from the host device → Step 11A In other cases → Step 4A - Step 4A: Receive data 1 byte of data is received from the host device. , Step, Pu 5A
fart.

・Step, F5A: Data judgment control code → Step, F10A and other cases (
Data code) → Step 6A, Pro A: Deni:,
, Write data to the evening write buffer A using the buffer A address information to step 7.

Step 7A; Add 1 to the value of the update buffer address of the address and step.

Go to P8A.

Step 8A: Update the determination of the buffer address If the buffer address exceeds the end point address of buffer A → Step 9 If it does not exceed A → Step 5
Step A, Step 9A: Set the buffer address. Set the buffer person's address to the start address of buffer A. Go to step 5A.

Step 10A: Set the register Set the received control code to register A.
Go to step 3A.

Step 11A: Send the completion report status of device A to the host device and return to Step 1A.

In the case of device B, Step 1B: Startup judgment When device B starts → Step, Step 2B Other cases → Step 1 person Step, Step 2B to Step 11B, except for the following, Step 2A to Step 11A is the same as

Step 1: Replace 1 person # in 2A to 11A with 1B#.

Step, 5B: Data judgment control code → Step, 7'5B and other cases
→As is clear from the explanation of the operation above, Step 168, the operation in Device Person and the operation in Device B are narrow but the same K, but Step, Pro A, 6B
~9A, 9B use different management parameters (and their storage addresses) such as the buffer address, buffer end point address, buffer start point address, register address, device address, etc. in other steps. As shown, the control program is for device A,
It has no choice but to become a two-pronged version for B.

Furthermore, regarding the reason why the control program is dual-pronged, the fifth
Explain using diagrams.

- Step 4A: The control device sends the device address (DEW ADR) to the host device and receives 1 byte of data from the host device.

As DEV A ADR, 1 immediate value l is normally used in conventional devices.

In Step 4B, different immediate values (DEVB ADR/
...) is used, so there are two parts to this step.

ΦSte, Pro A: From parameter A area, buffer A address (BF
BFF
A ADR ni Shiba.

Specify the address of F A and write 1 byte of data.

Step and Pro B use different parameters (BFF B ADR from parameter B area...not shown), so this step also consists of two steps.

・Ste, Pu 7 A % 8 A -, 9 A: Same as Ste, professional, BFF A from parameter A area
Use ADR parameters and update the same parameters (+1
), the buffer end address (BFF A E
BP'F compares the buffer start point address (BFF A TOP...immediate value) with ND...immediate value)
A Toshitashi to ADR.

In steps 7B, 8B, and 9B, the BFF B ADH (not shown) from the parameter B area and the
The immediate value, that is, the buffer B end point address (BFF B
END...not shown) and the buffer B start point address (BFF B TOP...not shown) must be used, so these steps also consist of two parts.

・Step 11A: The control device sends the device address (DEv A ADR...immediate value) to the host device, and then fetches the number of devices (Dgv A 5TATUS) from the parameter A area. and send this.

In step 11B, different immediate values (DEV BADH,
...not shown) and parameters (DIV B 5
Since TATU8 (not shown) must be used, this step also consists of two parts.

The above explanation explains why the control program of the conventional control device is
It has now become clear that he had no choice but to become a hondachi.

Therefore, if the number of devices is N, the control program will be N.
However, this will lead to an increase in the number of control programs and make them more complex.

Now, the most distinctive feature of the present invention is that the common parameter C area is added to the new nine in FIG.

FIG. 3 shows an example of the arrangement of parameters in the parameter A, parameter B, and common parameter C areas.

The characteristic feature here is the following.

t The device address, buffer start point address, buffer end point address, register address, etc., which have conventionally been treated as immediate values, are also defined as parameters in the parameter area.

2. Arrange the parameters in each parameter area in the same order.

Next, the arrangement order and contents of each parameter will be explained.

In the circle, A is entered for device A (parameter person), B is entered for device B (parameter 4B), and nothing is entered for common parameters.

t DEV OADR: Device address 2, BFF Q ADR Buffer address to be accessed next 5, BFF Q TOP Buffer start point address 4, BFF Q END Buffer end point address 5, REG Q ADR Register address & DEV Q 5TATUS Device Status parameter At or parameter B to common parameter C
Parameter movement to the area and return of the parameter from the common parameter C to the parameter A or parameter B area is performed in the order in which the parameters are arranged.

Therefore, if you move parameter A to parameter C and fetch DEV ADR of parameter C, DEV A
ADR will be obtained, and after moving parameter B to parameter C, BFFEND will be obtained.

FIG. 6 is a detailed operational diagram of a control device having a common parameter C.

Next, each operation step will be explained.

・Step 1: Startup determination If device A is activated 4 steps 101 In other cases →Step 12 ・Step 12
: Activation judgment When device B is activated → Step 121 In other cases → Step 1 - Step 101: Move parameter Move parameter A to common parameter C area and go to Step 2.

- Step 121: Move parameter Move parameter B to common parameter C area and proceed to step 2.

Step 2: Judgment of the command In the case of a read command → Step 5 In the case of other commands → Other steps, Step 5 (not shown) ・Step 5: Judgment of end Termination is instructed from the host device → Step 11 Other cases → Step 4 ・Step 4: Data and reception, 11 Receive 1 byte of data from the host device and go to Step 5 ・Step 5: Data judgment control code In the case of → Stellaf 10 In other cases (data code) → Ste, Pro 0 Ste, Pro: Write data to the buffer address of the corresponding buffer and go to step 7.

・Step 7: Add 1 to the update buffer address of step 7 and go to step 8.

・Step 8: Judgment of P and F addresses If the updated buffer address exceeds the buffer end address →
If step 9 is not exceeded → Step 3/Step 9: Setting the buffer address Set the buffer address to the buffer start address, then go to Step 3.

ΦStep, Step 10: Set the register. Set the received control code in the register, and go to Step 3.

・Step 11: Completion report Send the device status to the host device and proceed to step 111.

Step 111: Returning parameters Determine which device was operating and return the contents of parameter C to the corresponding parameter (parameter Am and parameter B) area.

Comparing FIG. 6 and FIG. 4, it can be seen that the effects of the present invention are great.

That is, the number of operation steps is reduced, and the control step, step 4: common parameter 1c! #) Fetch DEV ADR, send it to the higher-level device as a device address, and receive 1 byte of data from the higher-level device.

DEV ADR of common parameter C includes device A
DEW AADR is already stored when device B is activated, and DEv B ADH is stored when device B is activated, so in this step, DEV ADR of parameter C is used as the device address without being aware of the activated device. It can be used as

Therefore, this step is integrated into one regardless of the device.

Additionally, by checking DEV ADR parameter 4, it is also possible to know which device has been activated. (See step 111) Fist Ste, Pro: Fetch BFF ADR from common parameter C,
Specify the buffer address by BFF ADR,
Write received data.

BFF ADR has B corresponding to the activated device.
Since FF A ADR or BFFB ADR has already been stored, if the υ address is constant as BFFADRK, the buffer address to be accessed by the activated device will be automatically determined.

Therefore, this step and step are also unified regardless of the device.

・Step 7.8,9: BFF ADR in common para/-IC.

By fetching and using the BFF END and BFF TOPO parameters, these steps are combined into one.

- Step 11: Fetch DEV ADR from common parameter C and send it as a device address to the host device. D.E.V.
Since the address of the activated device is already stored in the ADR as described above, the address of the activated device is sent to the higher-level device.

Next, DEv 5 TATU 8 is fetched from 1 common parameter C, and this is used as a status byte to report the completion of transmission to the higher-level device. 1°:: ,X? -fis A4) (DEV 5TATUS)
indicates a type of termination (channel end, device end) or a device state such as an error state.
Set when the applicable condition occurs. (Not shown) This step and step also operate using only the common parameter C, so they are integrated into one.

・Step 10: This step differs in operation from device AXB.

That is, when the received data is a control byte, the control byte is set in register A for device A, and nothing is done for device B.

Therefore, in this example, we have devised the following method.

・Parameter A's RAG A ADH is the address of register A, parameter B's REG B AD
R has an address 'FF't that is not used in device A1B.
-Set it.

At the beginning of this step, the common parameter C is RE(,AD
Fetch H and check its value.

If %FFl, device B is started but does nothing. % p p If it is other than #, its value (R
Select the register and set the control byte using EG ADR).

Therefore, these steps are also unified regardless of the device.

It is easily understood that in another method of this step, K and DEVADR may be used instead of determining REG ADR.

・Step 111 Fetch DEV ADR from common parameter C,
If DEV ADR is A (device A), the content of the common parameter is placed in the parameter A area. Otherwise, it is returned to the parameter B area.

Therefore, it has been further clarified that one drawing (control program) is integrated into one program in this step and step regardless of the device.

In addition, in the above explanation, a control device that has a higher-level device and a lower-level device was taken as an example, but even if the control device itself becomes the highest-level or lower-level device, if there are a large number of identical or similar control operations, It can be easily understood that the effects of the present invention can be obtained.

Effects of the Invention According to the present invention, the control program for a control device that controls a plurality of lower-level devices can be integrated into one, so that the following effects can be obtained.

t The capacity of the control program can be reduced, the control memory capacity can be reduced, and the cost of the device can be reduced.

Or, it is possible to control more lower-level equipment and fj1m...
”・r.

2. The control program structure is simplified and the potential for bugs to occur is reduced.

[Brief explanation of drawings]

FIG. 1 is a system configuration diagram including a control device to which the present invention is applied, FIG. 2 is an internal block diagram of the control device according to the present invention, FIG. 5 is an arrangement diagram of management parameters according to the present invention, and FIG.
5 and 5 are detailed operation diagrams. 1... Upper device, 2... Control device, 3...
Device A, 4...Technology B. 21...Adapter, 22...Micro CPU. 25... Control memory, 24... Buffer memory, 2
5...Control register. Il. Fang 1 Kaisai 4 Illustrations Said 5 Fatty C [=D zuP Otsu Diagram off En

Claims (1)

[Claims] t In a microprogram type control device that controls multiple lower-level devices that perform the same or similar operations,
The management parameters necessary for control are held in the individual management parameter area prepared for each device, and one common management parameter area is provided, and the arrangement order of each parameter is the same among the management parameters, and when starting control The relevant individual management parameters are moved to the common management parameter area, and when the control ends, the contents in the common management parameter area are returned to the individual management parameter area. During the control, the common management parameters are accessed and controlled. A control device characterized in that: