JPH0452728A - Printer controller - Google Patents

Abstract

PURPOSE:To ensure the common use between a memory area which is used with an emulator for processing and a data storing area at the time of switching the emulators by providing a storage means, a decision means, a data input means, and an emulator switching means. CONSTITUTION:A decision means 19 checks the scales of the data to be reserved and the data to be returned, the size of an area to be secured by an emulator for processing, etc. When the means 19 decides that a normal area size cannot be secured for the execution of the selected emulator processing, an emulator switching means 14 limits the area down to a size smaller the normal one. Thus the common use is secured between a storage area used by an emulator and a data storing area. Then the total memory capacity is reduced.

Description

DETAILED DESCRIPTION OF THE INVENTION (Field of Industrial Application) The present invention relates to a control device for a printer equipped with a plurality of emulators.

(Prior Art) Recently, printers that can be connected to multiple hosts (host computers, etc.) have been used. Normally, printing control of a printer is performed by sending commands according to a certain protocol (command system) or format together with printing data from a host such as a host computer. Currently, this format is determined differently by each company, and if the host and printer use different formats, the printer will not be able to analyze the data received from the host. Therefore, printers that can be connected to multiple hosts are equipped with a function (emulator) that supports multiple types of 7-ohm printers, and can be configured by specifying them on the operation panel or by commands specifying the emulator sent from the host. , the specified emulator starts running.

(Problem to be Solved by the Invention) Generally, in a printer that can be connected to multiple hosts and is equipped with many emulators, when each emulator is activated, the memory map and data management method is different.

Therefore, when switching the application used on the host and specifying a printer emulator switch, in the past, memory was initialized for the switched emulator, and the previous state of the printer was lost. .

Clearing the memory through this initialization poses no problem if a person is using the blink system.

However, especially in a system connected to a plurality of hosts and used by a plurality of users, it may be better to maintain the previous state (usage environment) when switching emulators. For example, consider a case where multiple hosts and one printer are connected, and multiple users are using different emulators. If one user is downloading and using a font and another user switches the emulator to use the printer, the downloaded font data will be lost at this point, so the first user will have to download the downloaded font. When printing using the emulator, you not only have to switch emulators, you also have to download the fonts from the beginning.

Furthermore, any previously set values are reset and erased every time another user interrupts.

In this way, when multiple users use different emulators, there is a problem in that continuous work is interrupted.

Therefore, in the printer control device proposed in another application, the present applicant sets the current emulator usage environment stored in the first memory accessed by the emulator in executing processing when switching the emulator. Data (such as downloaded font data) is saved in another memory, and the saved data is restored when switching back to the previously used emulator. As a result, processing of print information can be started immediately without downloading new font data. Moreover, it does not destroy the usage environment of other users.

Here, if the first memory for emulator processing and the second memory for data storage are allocated and used in the same memory space, the boundaries of the area for data storage can be set floatingly, It is thought that the overall memory capacity can be reduced and memory can be used more efficiently.

However, when switching emulators, if there is a large amount of data to be saved, it may not be possible to secure the area necessary to run the new emulator. However, even if the area cannot be secured, it may be possible to execute the process in an area smaller than the size of the normally unnecessary area. In such cases, you may want to give priority to switching emulators, even if some functions are restricted.

SUMMARY OF THE INVENTION An object of the present invention is to provide a printer control device in which a memory area used by the emulators for executing processing and an area for data storage are shared when switching between emulators in a printer equipped with a plurality of emulators. .

(Means for Solving the Problems) A printer control device according to the present invention is a printer equipped with a plurality of emulators each processing a different protocol. A first storage area accessed during execution of the process and a second storage area for data storage.
a storage means comprising a storage area; a determination means for determining the usage status of the storage means; a data input means for receiving an instruction to switch the emulator; At the same time, data for setting the usage environment of the original emulator among the data stored in the first storage area is stored in the second storage area, and saved data for the switched emulator is stored in the second storage area. If the determination means determines that it is not possible to secure an area of normal size necessary for execution of the newly instructed emulator, the execution conditions of that emulator are stored. The present invention is characterized by comprising emulator switching means for restricting the area configuration of the means.

(Function) The first storage area that the emulator accesses when executing processing also stores data that sets the usage environment of the emulator. For example, 7-ont data downloaded by an emulator that performs processing centered on character printing is such data. When switching from another emulator to this emulator, if the downloaded font data is saved in the second storage area, printing information can be processed immediately by restoring the data to the first storage area. Therefore, when the data input means receives an emulator switching instruction from the host computer, operation panel, etc., the emulator switching means stores data for setting the current usage environment of the emulator in the second storage area. Further, the emulator switching means transfers the saved data for the designated emulator to the second emulator.
Return from the storage area to the first storage area.

Furthermore, the determining means determines the usage status of the storage means.

That is, the determining means checks the size of data to be saved, the size of data to be restored, the size of the area to be secured for execution of emulator processing, etc.

The emulator switching means limits the size of the area to be smaller than the normal size when the judging means judges that the normal area size for executing the process of the newly selected emulator cannot be secured.

For example, the cache area is limited to improve processing efficiency because there is no problem in program execution even if the size is limited to a certain extent. Also,
By limiting the size of the bitmap area on which dot images are drawn, the size of the paper on which to print is limited (from A4 size to B5 size, for example). This preserves the necessary data of the original emulator while
Ensure the newly selected emulator runs.

Margin below (Example) Embodiments of the present invention will be described below with reference to the drawings.

(a) General structure of printer FIG. 1 is a perspective view showing the external appearance of a laser printer 1 according to the present invention.

A laser printer l includes a photoreceptor, a developing device, a laser optical system for exposure, and
It also includes a print engine 4 including an image data processing section 10, which will be described later, an automatic paper feeding unit 5, and a sorter 6. The automatic paper feeding unit 5 has an upper paper feeding power set 51.
The middle paper feed cassette 52 and the lower paper feed cassette 53 are
Paper is supplied to the print engine 4 from one of the paper feed cassettes.

An operation panel 44 is provided on the upper front surface of the print engine 4 for user operation.

FIG. 2 is a front view of the operation panel 44.

Pr1nter Status of 7 segment LED
Display 3I displays a code indicating the operating status (including error display) of laser printer I. The size designation key 35 is provided to select one of the paper feed cassettes 51 to 53 that supplies paper, and a size display LED is displayed according to the size of the paper stored in the selected paper feed power cent. is lit. 37 is a reset key for initialization, 38 is a test key for test printing, and 39 is a form feed key for discharging internal image data.

The online key 40 is provided to temporarily stop the processing of each section, and when the processing is stopped, the display LED 40a turns off.

Further, 41 is an emulator selection key for selecting an emulator, and when the key 41 is pressed, a display 31 is displayed.
The emulator corresponding to the number displayed will be selected.

FIG. 3 is a block diagram showing the configuration of the image data processing section 10 of the laser printer 1. As shown in FIG. The image data processing unit 10
A CPU consisting of a microcomputer that controls the entire operation of the image data processing section 10 (Chuo-kuri device 1), a program ROM 12 that stores processing programs, and an operation panel interface 13 that is connected to an operation panel 44.
, a RAM 17 that is used as a bitmap memory and stores various data as described later, a font ROM 18 in which predetermined font data is written in advance, a memory controller 14 that controls these RAM 17 and 7ont ROM 18, and an external device. It consists of an external interface 15 connected to a host computer (hereinafter referred to as "host"), a dip switch 19, and a print engine interface 16 connected to a print engine control unit that controls the electrophotographic process in the print engine 4. ing.

Here, the dip switch 19 is set (used) to determine the default value of the printer operation method set by the user. The dip switch 19 can also be set to select whether to give priority to data storage or data abandonment (emulator switching priority) when there is insufficient memory capacity when switching emulators, which will be described later. Information is loaded upon power-on,
Default values are set. If emulator switching is given priority, the gard fdata flag is set to 0, and if emulator switching is given priority, the flag is set to 1.
(See Fig. 24(a) 584-S86)
.

The program ROM 12 contains a program (emulator) that analyzes and executes character data and a plurality of commands sent from the host. That is,
This printer has a function (emulator) that supports several types of formats, and can be specified on the operation panel 44,
Alternatively, each emulator starts responding in response to a command sent from the host.

When image data is input from the host via the external interface 15, the memory controller 14 draws image data in a bitmap area BM in the RAM 17, which will be described later, based on this image data. Image data drawing includes graphic drawing such as lines and circles, and font drawing performed by reading font data from the font ROM 18 or RAM 17.

Further, during a print operation, the memory controller 14 selects a bitmap area in the RAM 17 in response to a print start code sent from the host and in accordance with a synchronization signal from the print engine control section in the print engine 4. Image data is read from the BM in the order of pixel arrangement and output to the print engine control section.

The print engine control section uses a known electrophotographic process to blink a laser light source and form a latent image on a photoreceptor according to this image data.
Control is performed to form an image of a predetermined image size with a margin around the paper on the paper supplied from the paper.

The font data in the font ROM 18 (see Figure 10) includes pattern 7 ont data that represents the shapes of characters and symbols as dot patterns as shown in the image, and outline font (vector ont) data that represents only the outlines of characters. There is code 7 ont data (internal primary data) consisting of compressed font data with a reduced data length.

When outline font data is used for printing, images including high-quality deformed characters, enlarged characters, etc. can be easily formed.

In addition, if a font other than the font data in the 7-ont ROM 18 is required for printing, the necessary font data (external primary data) consisting of pattern font data or code font data is transferred from the host to the RAM 17.
(See Figures 8 and 11).

When drawing in the bitmap area of the RAM 17 based on the code font data, arithmetic processing such as filling and calculating the number of dots is required, which reduces the drawing speed. Therefore, in order to increase the drawing speed, the CPU 11 performs font conversion processing using the waiting time such as before the start of the printing operation, and converts code font data (internal or external primary data) into pattern font data in advance. , this is stored as secondary data in RAM 17 (11th
It may be stored in a 1m storage area, etc.).

(c) RAM Configuration and Emulator FIG. 4 shows the configuration of the memory area MA of the RAM 17. Memory area MA is composed of one or more RAM chips. The memory area MA is a memory space that can be accessed by one address system, and from the perspective of the type of data stored, it includes a system area SA for controlling various parts performed by the CPU II, a user area UA for image data, and It is divided into a data save area DS where downloaded font data and the like are saved when switching emulators.

The system area SA and user area UA are further divided and used depending on the purpose, and the details change each time the emulator is started. This is because the printer commands have different structures and functions in each emulator, and the emulator program also has a shape that reflects this, and the purpose of memory usage also changes depending on the emulator.

Note that the addresses of the user area UA and data save area DS change when the emulator is started, as will be explained later.

Note that the user area UA and data save area DS can be expanded by increasing the number of RAM chips.

Next, the memory spaces of the two emulators will be specifically explained. Here we will use two emulators: EMUl
, called EMU2.

First, the memory space for the emulator EMUI will be explained.

EMUI is an emulator that performs processing centered on character printing, and uses font RO when printing characters.
Only M18 pattern font data 181 is used. Internal information management is mainly done on a character-by-character basis.
Together with character information and print control commands, it is converted into a code called an intermediate code according to a defined format. When drawing, processing is performed based on the information in this intermediate code.

On the other hand, the EMU 2 is an emulator that performs processing mainly on graphical processing, and internally manages image data mainly on coordinate data. Text is also treated in a manner similar to image data, and is ultimately broken down into the same management data as image data. When printing characters, use font ROM18
Only code 7 ont data 182 is used. The code 7 ont data 182 is a collection of character outline information, and is basically information close to drawing figures.

In EMU1, memory arrangement of RAM17 is performed as shown in FIG. The system area SA of the RAM 17 includes a parameter area SAa that stores parameters for arithmetic processing by the CPU II, and a P-buffer area SAb that stores intermediate codes corresponding to instruction food for various controls input from the host. , and an R-buffer area SAc for communication with the host.

In EMU1, information for managing the entire program is stored in the parameter area SAa (directory management). The inside thereof is further divided into several blocks for management, as shown in FIG. For example, an emulator management block 5Aal that stores current operating information of the emulator, and a download data management block 5Aa that manages information such as downloaded fonts.
2. Data save area management block 5Aa3 that manages usage information of data save area DS, entire image information (
For example, several blocks such as an image information management block 5Aa4 for managing intermediate codes and table area data are provided.

As shown in FIG. 7, the data save area DS includes a data save area DSa and an emulator information save area DS.
As will be explained in detail later, the data storage area DSa consisting of .
56-563).

Furthermore, the contents of the above-mentioned emulator information management block 5Aal in the parameter area are copied to the emulator information storage area DSb in the data save area DS when the emulator is switched (see 5551 in FIG. 21). Then, the next time the original emulator is started up again, it is copied from the emulator information storage area DSb to the emulator information management block SAa1 (21st
(See Figure 5565).

This copying is performed to preserve the current operating information (usage environment) of the emulator, but the saving area DSb may not be placed in the data save area DS but may be placed in the parameter area SAa.

On the other hand, the user rear UA has the following information as shown in FIG.
A font load area FL for storing pattern data downloaded from the host as required for printing, and a bitmap area BM as a virtual screen for drawing image data are allocated. However, EMU
l handles only pattern font data and does not use code fonts.

As shown in Figure 9, when downloading, the font RO
The pattern font data from M18 is stored sequentially from the end of the user's rear UA (shaded area). This is 7
It is possible until the Ontrode area FL is used up, but
When the data is full in the area, the data that was downloaded later is discarded. On the other hand, the bitmap area BM is used from the opposite end of the user's rear UA.

As you can see from the figure, in the user area,
The font load area FL and bitmap area BM share a memory space, and the boundary indicated by the broken line is floating.

FIG. 1O shows the configuration of the font ROM 18.

EMUI uses only pattern font data 181 and does not use code font data 182 at all.

Next, the memory space in the case of EMU2 will be explained.

In the EMU 2, a system area SA and a user area UA are arranged as shown in FIG.

Furthermore, the data save area DS is arranged in the same manner as in FIG.

The system area SA is provided with a parameter area SAa for storing parameters and an R-buffer SAc for communication with the host, as well as a table area SAb.

In the case of the EMU 2, as already shown in FIG. 6, an image information storage block 5Aa5 is further created in the parameter area SAa. This is an area that stores information before the print control commands and coordinate data stored in table areas SA and b are created, and stores data that is in the middle of analysis or before analysis. Download font data and the like are also stored in this area SAa5. Therefore, 7 Ontrode Julia FL corresponds to a part of this area. This area is managed by the image information management block 5Aa4.

In this way, if you download the font, EM
Unlike the case of the UI, font data is stored inside the parameter area SAa. This is to treat font data in the same way as image data such as graphics, and parameters for generating an image are also stored within this parameter area SAa.

Since the EMU 2 uses only code fonts and does not handle pattern font data, only the code 7 ont data 182 is read from the ROM 18, and only the code font data is stored in the font load area FL.

Since the EMU2 does not use intermediate codes, the P-buffer area SAb for storing intermediate codes as in the case of EMUI is not provided. Instead, a table area SAb as shown in FIG. 12 is provided, and is used to store coordinate data necessary for drawing image data, intermediate data created in the process of generating coordinate data, or for managing programs. Necessary address information is collected and managed. Furthermore, since the image information is decomposed and divided into a number of tables, a t:-th table management table is created to manage the tables and collect pointers (addresses) pointing to these multiple tables. These are also placed within the table area SAb.

The user area UA is divided into a plurality of areas and used as shown in FIG. The bitmap area BM is used mostly as a virtual screen for drawing image data, but the other areas are cache areas FC for speeding up the drawing process.

Allotted to CA etc.

In the cache area, there is a font cache area FC.
There are cache area CAs such as halftone and halftone. E
The MU2 is an emulator that frequently performs graphic processing, or it takes a very long time to develop the parameters of graphic data into pattern data such as halftone data in a bitmap format. For this reason, pattern data such as halftone data that has been developed once is stored in the cache area CA, and when the same pattern is used, the pattern data is directly copied from the cache area CA.

(Do not go to the trouble of re-expanding the shape parameters.

) Second, in the case of fonts, data for each character (for example, A-Z) is stored in the font cache area FC. The data at this time corresponds to the secondary font data (pattern font data) described above.

In addition, the working buffer area WB of the user area UA is used when performing complex graphic processing, such as halftone processing, clipping processing, and superimposition processing.
- This is the area where temporary work is done. When performing this processing, a figure is created once on this area WB and then copied onto the bit map area 78M.

(d) Emulator switching and memory management In a printer equipped with many emulators, when multiple users use different emulators (application programs), when switching emulators, the previously set usage environment is saved in memory and each In order to enable continuous use by the user, data necessary for setting the usage environment is saved in memory when switching emulators (see FIG. 21).

FIG. 13 shows the configuration of the memory area when the emulator is switched from EMUI to EMU2 and then back to EMU again. When switching from EMU1 to EMU2, the 7-ont data (shaded area) that had been downloaded to the font load area FL of the user's rear UA of the EMUI is saved in the data save area DS described above.

When you return to the current emulator EMU1 again, download the downloaded font data (shaded area) saved in the data save area to the font load area PL.
to be restored. This allows the user to immediately run the application program without having to read external font data. Note that, to simplify the explanation, illustration and explanation of the saving and restoring of the emulator information data described above have been omitted.

In the case of EMU2, etc., if you have the downloaded code data (external primary data), you can return to the original usage environment, so when switching emulators, you can save only the primary data and discard the secondary data. Good too.

Furthermore, as shown in FIG. 14, when the emulator is switched, the data save area DS is made free so that the area used by the next emulator is expanded. For example, when switching from EMUI to EMU2 as explained earlier, from font load area FL to data save area D
Save to S.

At this time, only the used area (hatched area) is designated as the data save area DS, and the remaining space is designated as the user area U.
A and system area SA. This makes memory use more efficient (Fig. 22, 55554-555).
57. (See Figure 21 3566).

However, as shown in FIG. 15, depending on the size of the data save area DS, it may not always be possible to secure a normal size for the user area UA to be used in the next emulator. For example, as in case (a), there is little data to be saved (the shaded area), so the user's rear U
There is no problem if A can be larger than the normal size, but as in the case of (b), since the data save area DS is large, the cache area (
There are times when it is not possible to secure the normal size of the FC, CA) or working buffer area (WE).

In this case (NO at 55553 in FIG. 22), data preservation priority (GARD fdata 1) or data abandonment priority (GARD fdata.
ard fdata=o), that is, emulator switching is prioritized (see FIG. 22, 55558).

In case of data saving priority setting, 55561 in Fig. 22
As shown in -55566, the size of the cache area (FC, CA) and working buffer area (WB) is limited in the user area UA. These areas are areas to increase efficiency during processing, so
A certain degree of restriction does not pose a problem in program execution itself. For example, in the case of font cache (FC),
It is sufficient to have at least one character, and in the case of a halftone cache (CA), it is sufficient to have at least one halftone block.

In this way, when you cannot secure a normal user area after switching emulators, you can use the
- If the area up to Z cannot be secured, for example,
-N only), limits the size of the user area UA.

If the minimum memory area (FC, CA, WB) cannot be secured even after performing the above memory allocation operations,
Furthermore, the size of the bitmap area BM, that is,
Multiply the maximum printable paper size by fllll so that large paper sizes cannot be selected. As a result, it may be possible to print in a smaller size than the user desires, but it becomes possible to switch emulators. (Conversely, when switching from EMU2 to EMUI, you can limit the size of the font load area FL and bitmap area BM.The font load area FL can restore at least the data stored in the data save area DS. Printing can be performed as long as there is enough capacity, so limit the size to that size.Also, if the above minimum font load area cannot be secured, the bitmap area BM can be used as is when switching from EMU1 to EMU2. ) On the other hand, if the user sets data abandonment priority, that is, emulator switching priority, the data save area DS
Clear the , discard external primary data, etc., and switch the emulator.

In this embodiment, whether or not to give priority to emulator switching is selected in cases where a normal memory area cannot be secured, but other sizes such as paper size cannot be secured or the minimum memory cannot be secured. It may be selected depending on the case.

FIG. 16 shows an example of data movement when switching emulators. Here, LLll is the I-ni font data downloaded by EMUI, and m2 is the previously saved downloaded font data of EMU2. Furthermore, m3 is 7-ont data downloaded by another emulator EMU3. EMUI to EM
When switching the emulator to U2, the EMUI download font data ml is saved in the data save area DS.
Saved to EMU2 download font data m
2 returns to the system area SA from the data save area DS, but m3 for the other emulator EMU3 is unrelated to the switching from EMUI to EMU2, and is therefore saved as is in the data save area DS.

Here, the part indicated by M is the area that can be used as the user area UA, so the bitmap area BM, 7
Ontokiya FC, cache CA such as halftone, and working buffer WB are allocated to this area.

(e) Print control flow FIG. 17 shows the CPU II main 70-.

When the power is turned on, first the parameters in the parameter area SAa of the RAM 17 are initialized (step Sl
(hereinafter abbreviated as "step").

Next, receive buffer S Ac, bit map area BM
, font cache area FC, cache area C
A, working buffer WB, packet buffer SAb
Clear areas such as (S2). Furthermore, the setting of the dip switch 19 is checked to confirm the default value setting (S3). This set value is stored as information in the parameter area SAa.

The main 70- then performs a reception processing process (S5),
Drawing process (36), engine processing process (S7)
and the operation unit processing process (S8) are repeated.

Here, the reception processing process (S5) performs a process of adding necessary information to the print data sent from the host and converting it into a formant managed internally.

The drawing processing process (S6) is similar to the receiving processing process (S5).
) is further analyzed and drawn as an image to be actually printed on the bitmap area BM.

The engine processing process (S7) is the print engine 4
The printer monitors the status of the printer and performs the actual printing operation. This is a common process for all emulators.

The operation unit processing process (S8) checks and displays the contents set on the operation panel 44. This is a common process for all emulators.

The data full flag is a flag indicating that memory could not be secured in settings that give priority to data storage when switching emulators (see 55567 in FIG. 22). As will be described in detail later, when this flag is set (YES in S4), no processing can be performed, so the reception processing process (S5) and drawing processing process (S6) are not executed. However, the engine processing process (S7) and the operation unit processing process (S8) must constantly monitor their states, so these processes are executed. However, at this time, the engine processing process (S7) and the operation unit processing process (S7)
If the information in the parameter area SAa used by 8) is changed carelessly, the program may run out of control, so that area must not be changed.

FIG. 18 shows the flow of reception interrupt processing. In order to communicate with the host asynchronously with processing such as drawing,
An interrupt is generated when reception is received from the host, and the reception interrupt is processed. That is, data is read from the external interface 15 (S9) and its contents are
- Output to buffer SAC (S92). And then return.

i! FIG. 19 shows 70- (FIG. 17 53) for reading the settings of the dip switch 19. First, the setting of the dip switch 19 is confirmed (531). Next, according to the settings, a value is set in the parameter area SAa of the RAM 17, and the process returns. For example, check which emulator to start first (S32), and set the type of emulator to start to curr emu (S32-1-
532-n). Specifically, curr emu is located at a certain address within parameter area SAa. Also, when the memory is used up to save the downloaded data (external primary data), check the setting to discard the downloaded data (S33). When the user sets data abandonment priority, that is, emulator switching priority (YES in S33), gard
Set the fdata flag to 0 (534), and when the user sets data preservation priority to use by reducing cache area or paper size without discarding data, gardJdata
is set to 1 (S35). Here, gardJ
data is located at a certain address within the parameter area SAc. In this way, each value set with the dip switch I9 is checked to determine the specific setting, and is stored in the form of setting the value to a parameter. And then return.

FIG. 20 is a flowchart of the reception processing process (55 in FIG. 13). Data is stored in the R-buffer area SAc by a reception interrupt (Fig. 14), but the presence or absence of this data should be checked (551), and if there is data (S5
1: YES) Retrieve data from the R-buffer area SAc 552), and if there is no more data (551: No), this process ends.

The retrieved data is first checked to see if it is an emulator switching command (S53). If so
(S53: YES), then check which emulator and type to switch to (554), and set the value to curr emu according to each type.S5
4-1"554-n), and emulator switching processing is performed to save the operation information of the current emulator (S55, see FIG. 21).

Next, we have previously set the current emulator in currernu (see Figure 19), so check its value. Do it (S56
-1=356-n). The main process here is to convert the received data into an internally managed data format. Note that the format of internally managed data differs depending on the emulator, as described above. After completing the above processing, return.

21st [m is emulator switching processing (555 in Fig. 19)
) shows 70-. The emulator I'm currently using is
Since it may be used again in the future, it is necessary to save and save the current operating information. For this reason, the emulator information storage area DSb in the data save area DS
Save them together. Operation information is stored in the emulator information management block 5Aal in the parameter area SAc.
, so the actual process is to copy the contents of this area as is (5551). (If it can be stored within the parameter, it can be left as is.) Next, the length of the data used in the data save area DS is checked (S552). Since this is managed within the data save area management block 5Aa3, it can be checked by referring to the inside of the block.

Next, in order to restore and save the data, the data lengths of both the data to be restored and the data to be saved are determined, respectively (S553, 5554). When returning, just as before, open the data save area DS tube 3iJ 7”a tsuk 5
Aa3 is checked, and download data management block 5Aa2 is checked for saved data. When saving, not all information related to the downloaded data is necessarily saved, but the base 1 such as code font data is saved.
Save only the following data. All data in secondary caches is ignored.

Before actually starting the emulator, it is necessary to decide where to place the addresses of areas such as buffers used internally, so this is determined (see figure S555.822). :, Z-? 'HaS Perform calculations using the values found in 552.5553.5554.

Now that the memory layout has been decided, we will actually restore and save the data. It is determined whether save information regarding the emulator to be started next was previously written to the data save area management block 5Aa3 (S556), and if the data has been saved (YES in S556), which memory allocation process ( s 555), the font load area F
Now that L has been determined, data save management block S Aa
3. Determine the address of the original data to be copied (
S 557).

The saved data is then restored (5558).

When saving, in the same way as when returning above, check whether there is data to save (5561), check the address to copy (S562), and save the data (s536).
).

When you switch emulators, the bitmap area BM
data and table area SAb (for EMU2) and P
- Clear the data in the buffer emulator SAb (when in EMUl) because it is no longer needed (S564).

However, the data in the R-buffer SAC is not cleared because it will be used for the next process.

Then, the emulator information is restored from the emulator information storage area DSb (s565). Default values for using the emulator for the first time are stored in the emulator information storage area DSb in advance.

Although the above process has completed exchanging (saving and restoring) the information in the emulator, there may be some free space in the memory. Therefore, the data is finally moved to fill up the space <s 566). Also, when using previously used data as is, if the addresses do not match properly, make adjustments at this time.

FIG. 22 shows the process of determining memory placement (555 in FIG. 22).
5) 70- is shown. This is written about the case of switching the emulator from EMUI to EMU2, but it is almost the same when switching to other emulators. The sizes of the FC, CA, and WB of the user's rear UA have been changed, and when switching from EMU2 to EMUI, the font load area FL will change accordingly.

First, the size of the area that can be used as the user area UA is determined (S5551). This size can be calculated from the previously determined usage amount of the data save area DS (S552) and the data length to be restored (S553). Since the usage amount of the system area SA is determined for each emulator, the remaining amount becomes an area that can be used as the user area UA.

Next, each area allocated inside the user area (
For example, in the case of EMU2, bitmap area BM,
The sizes of the font cache area FC, other cache areas CA, and working buffer WB are checked (s5552).

This is stored as information in the parameter area SAa, so just check it.

Next, compare this with the current user area UA size to check whether the size can be secured (s5553
). If it does (S5553: YES), the remaining size is determined by the user's rear UA (S5554),
To allocate each area (FC, CA, WB)
) (S5555
). (However, there are cases where there is no point in increasing the size,
For example, it is not allocated to the bitmap area BM or areas where data above a certain value is not used. For example, even if it is a cache area, if graphic data larger than a certain cell size cannot be handled, there is no point in increasing the area. ) After this, the values (size, address) of each area are updated, but since each area is usually managed in units of words or blocks, it is necessary to round down the fractions etc. and make adjustments (S5556). Now that the size has been determined, we can allocate addresses from this (S 5
557). and return.

However, when the normal size of each area FC, CA, and WB cannot be secured (No in S5553), the settings of the dip switch 19 or the operation panel 44 can be set as described below. gard f
The value of the data flag is referenced (55558). (g2
rd fdata is located at a certain address inside the parameter area SAa. ) User instructions for discarding downloaded data if normal area size cannot be secured (GARD FD
When ata=O) (YES in S5558), the data save area DS is saved to give priority to emulator switching.
The contents of are cleared (abandoned) L (S5559), and the addresses of each area set inside the user's rear UA are calculated. This is the same procedure as steps S5554 to S55557.

On the other hand, if discarding data is prohibited in order to prioritize data preservation (preservation of usage environment) (GARD FD
ata-I XS 5558), FC, CA.

Check the minimum required size in areas such as WB from the parameter Naria SAa (55561). Then, check if you can use this data to enter the user area UA (55562), and if so (YES),
Addresses are allocated through the processes 55554 to 55557.

Furthermore, if the user does not enter UA (S
5562 Te No), request size (S5563),
Subtract the size from the bitmap area BM<(S
5564). At this time, check whether the minimum paper size can be secured (55565), and if possible, find the maximum paper length that can be secured (S5566). For example, let's say that legal size paper has been available up until now. At this time, if the above situation occurs, you can only select paper sizes such as letter size and A5 size (legal size>letter size>A5).

Then, addresses are allocated according to the steps 55554 to 55557.

If the memory size cannot be secured even after performing the above processing (
S5565: No), data cannot be saved, so data full is displayed to display an error on the operation panel 44.
The variable is set to 1 (S5567). And then return.

FIG. 23 shows the flow of the drawing process (56 in FIG. 13). First, check your current emulator
61), performs drawing processing corresponding to the type (S6
2-1"562-n). This is the focus map area BM
This is the process of drawing an image on top of the image, and image data is created from the internal data created in the reception process and then drawn. And then return.

FIGS. 24(a) and 24(b) show the operation unit processing process (
Fig. 13 shows the flow of 58). Basically, check the switches on the operation panel 44 and set the internal parameters (
The information is set in the parameter area 5Aa) and displayed accordingly. (This time we explained a case where it is executed periodically within a loop, but if this time cannot be secured, this process may be called by a timer interrupt.) Parameters corresponding to this explanation There are 3 steps to set
81 to S89. First, it is checked whether the switch has been pressed (581). Information as to whether the button has been pressed is notified through the operation panel interface 13. If not pressed, change internal parameters (881-5
89) and moves on to the next process (5891 steps). If pressed (YES in S81), the state of the switch is read (382). Then, if the data protection settings have been changed (YES in S83) , according to its contents (S84),
The gard fdata parameter indicating whether to discard the aforementioned data, ie, to switch emulators or to save the usage environment, is changed (585 and 586).

Next, when switching the emulator from the operation panel 44 (S87: YES), check which emulator to start (S88) and set the type in the curr emu parameter (589-1 to 589-n).
, performs the emulator switching process (S55) described above (5
90).

Next, in the memory allocation process (S555), da
S9 if ta full is set to 1.
1': YES), Pr1n on the operation panel shown in Figure 2
Display an error on the ter 5 status display 31 (
S92'). Next, it checks whether the reset switch (Reset switch 37 in Fig. 3) has been pressed, and if it has been pressed (YES in S93), the data in the data save area DS is discarded (S94) and the data full is turned off. 595), and performs memory allocation processing (S555) to determine the address again (S96).

Finally, display processing (S
97) and return.

As described above, the user can use the dip switch 19 to set in advance whether to give priority to downloaded fonts or to give priority to switching emulators. This prevents your environment from being unnecessarily destroyed when multiple users use it.

Moreover, it can be used without worrying about whether or not it will destroy the usage environment of others.

In the above explanation, the size of the system area SA does not change, but when switching emulators, the size of the system area SA may change. In this case, the top address of the user area changes.

In addition, if intermediate font data is generated during the conversion from code 7 ont data of the primary data stored in the font ROM to pattern 7 ont data, this intermediate data can also be restored as secondary data. It may be treated as

Also, in the above explanation, we have explained the case where pattern data and code font data cannot be used by each other's emulators, but even if the stored data is of the same type (for example, pattern data), either The same thing applies if you can't use it.

Furthermore, when saving data, the data may be compressed and saved.

In addition, in this embodiment, the explanation was made so that the settings are made from the dip switch 19, but the default values can be set from the operation panel 4.
4 may be set in advance.

In addition, in this example, when setting restrictions so that the downloaded fonts are not deleted, an error is displayed when memory cannot be secured and all analysis data is discarded. It may also be possible to specify this at this point.

(Effects of the Invention) When a plurality of users switch and use different emulators with different applications, this data is not destroyed by storing the minimum usage environment data in a second storage area at the time of switching. Therefore, even if you switch to the original emulator, the saved data can be restored and processing can be performed quickly. Also, by saving this data, you can use the printer without being aware of other users.

Since the storage area used by the emulator and the storage area for data storage can be shared, the overall memory capacity can be reduced, although some functions are limited.

[Brief explanation of drawings]

FIG. 1 is a perspective view of a laser printer. FIG. 2 is a front view of the operation panel. FIG. 3 is a block diagram of the image data processing section. FIG. 4 is a diagram showing the memory configuration of the RAM. FIG. 5 is a diagram showing the memory arrangement in EMUI. FIG. 6 is a diagram showing the configuration of the parameter area. FIG. 7 is a diagram showing the configuration of the data save area. FIG. 8 is a diagram showing the configuration of the user area. FIG. 9 is a diagram showing the usage status of the user area. FIG. 10 is a diagram showing the configuration of a 7-ont ROM. FIG. 11 is a diagram showing a part of the memory configuration in the EMU 2. As shown in FIG. FIG. 12 is a diagram showing the configuration of the table area. FIG. 13 is a diagram showing data storage and restoration. FIG. 14 is a diagram showing data storage and restoration. FIG. 15 is a diagram showing data storage when memory for normal storage cannot be secured. FIG. 16 is a diagram of data movement when switching emulators. FIG. 17 is a main flowchart of image data processing. FIG. 18 is a flowchart of reception interrupt processing. FIG. 19 is a flowchart of the dip switch setting reading process. FIG. 20 is a 70-chart of reception processing. FIG. 21 is a 70-chart of emulator switching processing. Figure 1g22 is a flowchart of memory allocation processing. FIG. 23 is a flowchart of the drawing process. FIGS. 24(a) and 24(b) are flowcharts of operation unit processing. IA, IB, IC...Host, 3...Printer controller, 4...Printer engine, IO...Printer system, 11...CPU of image data processing section, 17...RA
M. 19...Dip switch, 41...Emulator switching key 44...Operation panel. Patent Applicant Minolta Camera Co., Ltd. Representative Patent Attorney Aoyama Aoyama and 2 others Figure 1 Figure 2 Figure 4 Figure 5 @ Figure 9 Figure 11 Figure 17 Figure 18 Figure 23 Figure 24 Figure ia) Figure 24(b)

Claims (1)

[Claims] (1) In a printer equipped with multiple emulators that each process different protocols, the first storage area is used as a storage area or work area for data that sets the usage environment, and the first storage area is accessed by the emulator when executing processing. a second storage area; a determination means for determining the usage status of the storage means; a data input means for receiving an emulator switching instruction; and upon receiving the emulator switching instruction from the data input means, While switching to the emulator, the data that sets the usage environment of the original emulator among the data stored in the first storage area is saved in the second storage area, and the saved data for the switched emulator is stored in the second storage area. If the stored data has been stored, the saved data is restored to the first storage area, and if the determining means determines that it is not possible to secure an area of the normal size necessary for executing the newly specified emulator, the execution conditions of that emulator are restored. What is claimed is: 1. A printer control device comprising emulator switching means for restricting the area configuration of a storage means.