JP4043374B2 - Image forming apparatus and conversion function management method - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to management of hardware for converting image data, and more particularly to an image forming apparatus and a conversion function management method.
[0002]
[Prior art]
In recent years, there has been known an image forming apparatus (hereinafter referred to as a multifunction peripheral) in which functions of apparatuses such as a facsimile machine, a printer, a copy machine, and a scanner are housed in a single casing. In this multi-function apparatus, a display unit, a printing unit, an imaging unit, and the like are provided in one casing, and four types of applications corresponding to a facsimile, a printer, a copy, and a scanner are provided. Operates as a printer, copy and scanner.
[0003]
As described above, the fusion machine performs image data format conversion in order to handle different types of image data, and in order to save hardware resources of the image forming apparatus, image data compression / decompression Compression / decompression is also a format conversion).
[0004]
[Problems to be solved by the invention]
These conversions may be performed by hardware that converts the format of the image data. In this case, when there is an abnormality in part or all of the conversion function of the hardware, for example, when the operator turns off the power of the fusion machine and turns on the power again to use it, It cannot be used and an error occurs, which is not convenient.
[0005]
In addition, for example, when a service person who performs maintenance replaces abnormal hardware, whether or not any conversion function of the replaced hardware operates normally can be determined not to actually convert. could not.
[0006]
As described above, in the conventional multi-function apparatus, management of the hardware conversion function for converting the format of the image data is often inconvenient and inefficient.
[0007]
SUMMARY An advantage of some aspects of the invention is that it provides an image forming apparatus and a conversion function management method for efficiently managing a hardware conversion function for converting the format of image data.
[0008]
[Means for Solving the Problems]
In order to solve the above problems, the present invention provides one or more conversion functions for converting the format of image data in an image forming apparatus having hardware resources used in image forming processing and a program related to image formation. One or more conversion hardware having: Non-volatile storage means for storing conversion function information related to the conversion function of the conversion hardware, and verification means for verifying whether the conversion function of the conversion hardware is abnormal, Said conversion hardware Manage Conversion hardware management means And Yes The nonvolatile storage means further stores verification item information indicating a verification item of a conversion function to be verified, and verification level information indicating a verification level of the verification item, The verification means includes first image data which is verification image data or verification image data having a smaller data amount than the first image data in accordance with the verification level information stored in the nonvolatile storage means. One of the second image data is converted by the conversion function, and it is verified whether the conversion function is abnormal based on the conversion result It is characterized by doing.
[0009]
In order to solve the above problems, the present invention provides a hardware resource used in image forming processing, a program related to image formation, and one having one or more conversion functions for converting the format of image data. A conversion function management method for an image forming apparatus having the above-described conversion hardware, wherein the conversion function is a target for verifying whether or not there is an abnormality in the conversion function according to conversion function information related to the conversion function. A verification target conversion function determination stage to be determined, and the converter that is the verification target Noh A conversion function verification stage for performing verification, and a verification result storage stage for storing the verified result in a nonvolatile storage device. And The conversion function verification step includes: The amount of data from the first image data, which is image data for verification, or from the first image data, in accordance with verification level information indicating the verification level of the conversion function to be verified that is stored in advance One of the second image data, which is image data for verification with a small amount, is converted by the conversion function that is the object of verification, and whether the conversion function that is the object of verification is abnormal based on the conversion result Verify It is characterized by doing.
[0010]
As described above, according to the present invention, it is possible to obtain an image forming apparatus and a conversion function management method that efficiently manage a hardware conversion function for converting the format of image data.
[0011]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, embodiments of the present invention will be described with reference to the drawings.
[0012]
FIG. 1 shows a block diagram of an embodiment of a compound machine according to the present invention. The multi-function apparatus 1 is configured to include a software group 2, a multi-function apparatus activation unit 3, and hardware resources 4.
[0013]
The compound machine starting unit 3 is executed first when the power of the compound machine 1 is turned on, and activates the application layer 5 and the platform 6. For example, the multi-function apparatus activation unit 3 reads the programs of the application layer 5 and the platform 6 from a hard disk device (hereinafter referred to as HD) and transfers each read program to a memory area and activates it. The hardware resources 4 include a monochrome laser printer (B & W LP) 25, a color laser printer (Color LP) 26, an MLC (Media Link Controller) 45 corresponding to conversion hardware, and hardware resources 24 such as a scanner and a facsimile. Including. Note that the MLC 45 converts the format of the image data at high speed by hardware, and a plurality of MLCs 45 may be mounted as necessary for the multi-function apparatus 1.
[0014]
The software group 2 includes an application layer 5 and a platform 6 activated on an operating system (hereinafter referred to as OS) such as UNIX (registered trademark). The application layer 5 includes programs that perform processing unique to user services related to image formation such as printers, copies, faxes, and scanners.
[0015]
The application layer 5 includes a printer application 9 that is a printer application, a copy application 10 that is a copy application, a fax application 11 that is a fax application, and a scanner application 12 that is a scanner application.
[0016]
The platform 6 also interprets a processing request from the application layer 5 and generates a hardware resource 4 acquisition request, and manages one or more hardware resources 4 to control the control service layer 7. A system resource manager (hereinafter referred to as SRM) 21 that arbitrates acquisition requests from the SRM 21 and a handler layer 8 that manages the hardware resources 4 in response to the acquisition requests from the SRM 21.
[0017]
The control service layer 7 includes a network control service (hereinafter referred to as NCS) 13, a delivery control service (hereinafter referred to as DCS) 14, an operation panel control service (hereinafter referred to as OCS) 15, and a fax control service (hereinafter referred to as FCS) 16. , Engine control service (hereinafter referred to as ECS) 17, memory control service (hereinafter referred to as MCS) 18, user information control service (hereinafter referred to as UCS) 19, system control service (hereinafter referred to as SCS) 20, etc. The service module is configured to be included.
[0018]
The platform 6 is configured to have an API 28 that can receive a processing request from the application layer 5 using a predefined function. The OS executes the software of the application layer 5 and the platform 6 in parallel as processes.
[0019]
The process of the NCS 13 provides a service that can be commonly used for applications that require network I / O. Data received from the network side according to each protocol is distributed to each application, and data from each application. Mediation when sending to the network side.
[0020]
For example, the NCS 13 controls data communication with a network device connected via a network by HTTP (HyperText Transfer Protocol Daemon) by HTTP (HyperText Transfer Protocol).
[0021]
The process of the DCS 14 performs control such as distribution of stored documents. The process of the OCS 33 controls an operation panel serving as information transmission means between the operator and the main body control. The FCS16 process provides APIs for sending and receiving faxes from the application layer 5 using the PSTN or ISDN network, registering / quoting various fax data managed in the backup memory, reading faxes, receiving faxes, etc. To do.
[0022]
The process of the ECS 17 controls engine units such as the black and white laser printer 25, the color laser printer 26, and the hardware resource 24. The process of the MCS 18 performs memory control such as acquisition and release of memory and use of HD. The UCS 19 manages user information.
[0023]
The process of the SCS 20 performs processing such as application management, operation unit control, system screen display, LED display, hardware resource management, and interrupt application control.
[0024]
The process of the SRM 21 controls the system and manages the hardware resources 4 together with the SCS 20. For example, the process of the SRM 21 performs arbitration in accordance with an acquisition request from an upper layer that uses the hardware resource 4 such as the black and white laser printer 25 and the color laser printer 26, and controls execution.
[0025]
Specifically, the process of the SRM 21 determines whether or not the requested hardware resource 4 is available (whether it is not used by another acquisition request). The higher layer is notified that the resource 4 is available. In addition, the process of the SRM 21 performs scheduling for using the hardware resource 4 in response to an acquisition request from an upper layer, and requests (for example, paper conveyance and image forming operation by the printer engine, memory allocation, file generation, etc.) Has been implemented directly.
[0026]
The handler layer 8 is a fax control unit handler (hereinafter referred to as FCUH) 24 that manages a fax control unit (hereinafter referred to as FCU), which will be described later, and an image for allocating memory to the process and managing the memory allocated to the process. And a memory handler (hereinafter referred to as IMH) 23. The SRM 39 and the FCUH 40 make a processing request for the hardware resource 4 using the engine I / F 27 that enables transmission of the processing request for the hardware resource 4 by a predefined function. The MEU 44 corresponding to the conversion hardware management means converts the image data using the MLC 43. The MEU 44 can also convert the format of image data by software. Then, the MEU 44 converts the format of the image data in response to a conversion request from the application notified via the SRM 21 and the IMH 23 corresponding to the image data conversion management means.
[0027]
The multi-function apparatus 1 can process the processing commonly required for each application by the platform 6. Next, a hardware configuration of the multifunction machine 1 will be described.
[0028]
FIG. 2 is a hardware configuration diagram of an embodiment of the compound machine according to the present invention. The multi-function apparatus 1 includes a controller 30, an operation panel 39, an FCU 40, a USB device 41, an IEEE 1394 device 42, an engine unit 43, and an MLC 45.
[0029]
The controller 30 includes a CPU 31, a system memory (MEM-P) 32, a north bridge (hereinafter referred to as NB) 33, a south bridge (hereinafter referred to as SB) 34, an ASIC 36, and a local memory (MEM-C). ) 37, HD 38, and NV-RAM (Nonvolatile RAM) 46 corresponding to the nonvolatile storage means.
[0030]
The operation panel 39 is connected to the ASIC 36 of the controller 30. The MLC 45, FCU 40, USB device 41, IEEE 1394 device 42, and engine unit 43 are connected to the ASIC 36 of the controller 30 via a PCI bus.
[0031]
In the controller 30, a local memory 37, an HD 38, and the like are connected to the ASIC 36, and the CPU 31 and the ASIC 36 are connected to each other via the NB 33 of the CPU chip set. In this way, if the CPU 31 and the ASIC 36 are connected via the NB 33, it is possible to cope with a case where the interface of the CPU 31 is not disclosed.
[0032]
The ASIC 36 and the NB 33 are not connected via a PCI bus, but are connected via an AGP (Accelerated Graphics Port) 35. In this way, in order to control execution of one or more processes forming the application layer 5 and the platform 6 in FIG. 1, the ASIC 36 and the NB 33 are connected via the AGP 35 instead of the low-speed PCI bus to prevent performance degradation. It is out.
[0033]
The CPU 31 performs overall control of the compound machine 1. The CPU 31 starts and executes NCS13, DCS14, OCS15, FCS16, ECS17, MCS18, UCS19, SCS20, SRM21, FCUH22, and IMH23 as processes on the OS, and also executes a printer application 9 and a copy application that form the application layer 5 10. Start and execute the fax application 11 and the scanner application 12.
[0034]
The NB 33 is a bridge for connecting the CPU 31, the system memory 32, the SB 34 and the ASIC 36. The system memory 32 is a memory used as a drawing memory or the like of the multifunction machine 1. The SB 34 is a bridge for connecting the NB 33 to the ROM, the PCI bus, and peripheral devices. The local memory 37 is a memory used as a copy image buffer and a code buffer.
[0035]
The ASIC 36 is an IC for use in image processing having hardware elements for image processing. The HD 38 is a storage for storing image data, document data, programs, font data, forms, and the like. The operation panel 39 is an operation unit that accepts an input operation from an operator and performs display for the operator.
[0036]
The MLC 45 is hardware that converts the format of image data as described above. The inside of the MLC 45 will be described with reference to FIG. The MLC 45 includes a PCI interface 61, a Basic 63, an option P64, an option Q65, and a presence / absence determination register 62. The PCI interface 61 is an interface for connecting to a PCI bus.
[0037]
The Basic 63 is a basic conversion unit provided in the MLC 45 in advance, and can convert image data in binary, 4-value, 8-value, MH / MR / MMR, JPEG, RGB / sRGB, NFC1, and TIFF formats. It has become. NFC1 is one of the compression formats.
[0038]
Option P64 and option Q65 are additional conversion units to which a conversion function is added. Among these, the option P64 has a conversion function called Ri10 that performs conversion for improving the image quality of the image data. The option Q65 has a conversion function called Ri2000 that converts the JPEG2000 format, which is a format of image data that cannot be converted by the Basic63. In FIG. 3, these options are two, but can be increased or decreased by adding or removing options.
[0039]
The presence / absence determination register 62 corresponding to the hardware information represents MLC information related to basic and options included in the MLC 45. Specifically, the presence / absence determination register 62 is information indicating the presence / absence of a basic and an added option.
[0040]
Next, a software block diagram relating to conversion of the format of image data will be described with reference to FIG. FIG. 4 shows the upper application 66, the SRM 21, the IMH 23, the image conversion unit 67, the image conversion device management module 68 corresponding to the conversion management means, the image conversion device driver 69, and the MLC 45. .
[0041]
The upper application 66 comprehensively shows the printer, copy, fax, and scanner applications shown in FIG. Further, the SRM 21 makes a config request to notify the IMH 23 of a conversion request from the application. The config request is a request including information indicating that the conversion is from a certain format to a certain format.
[0042]
The IMH 23 obtains a memory used for the conversion of the image data format and requests the MEU 44 surrounded by the broken line to convert the image data format.
[0043]
The MEU 44 converts the format of the image data using the MLC 45 or a conversion library that converts the format of the image data by software. The image conversion module 67 includes the conversion library and a function group for operating the image conversion device driver 69. The image data conversion device driver 69 controls the MLC 45.
[0044]
Next, an outline of the processing of the image conversion module 67, the image conversion device driver 69, and the MLC 45 when the image data format is converted or an abnormality occurs in the MLC 45 will be described with reference to the drawings.
[0045]
FIG. 5 shows an image conversion module 67, an image conversion device driver 69, and an MLC 45a. Further, the MLC 45a in FIG. 5 is operating normally at the present time. In this case, when the image conversion module 67 makes an image data format conversion request (Req) to the image conversion device driver 69, the image conversion device driver 69 issues an image data format conversion request (Req) to the MLC 45a. When the conversion of the format of the image data is completed, the MLC 45a notifies the image conversion device driver 69 of conversion completion (OK), and the image conversion device driver 69 also notifies the image conversion module 67 of conversion completion (OK).
[0046]
In this way, processing when the MLC 45a is normal is performed. Next, processing when an abnormality of the MLC 45a is detected will be described with reference to FIG.
[0047]
When the image conversion module 67 makes an image data format conversion request (Req) to the image conversion device driver 69, the image conversion device driver 69 issues an image data format conversion request (Req) to the MLC 45a.
[0048]
Here, NG is notified from the MLC 45 a to the image conversion device driver 69. This NG is a result determined by the image conversion module 67 or the image conversion device driver 69 as a result. In FIG. 6, this NG is an expression for facilitating understanding. The process for determining this abnormality will be described in detail later.
[0049]
As described above, when the MLC 45a becomes abnormal, it is impossible to convert the format of the image data as shown in FIG. Therefore, as shown in FIG. 8, the abnormal MLC 45a is replaced with a normal MLC 45b. This exchange may be performed by the operator of the multi-function apparatus 1, or when two MLC 45 a and MLC 45 b are connected to the multi-function apparatus 1, they may be switched by the multi-function apparatus 1 itself.
[0050]
When the MLC 45b is started after being replaced or switched, as shown in FIG. 9, the image conversion module 67 and the image conversion device driver 69 check the MLC 45b (CheckReq), and confirm that the MLC 45b is normal (Check OK). To do. As described above, when it is confirmed that the MLC 45b is normal as a result of the check, the format of the image data can be converted as shown in FIG.
[0051]
Details of the above-described processing will be described below. First, the overall process flow will be described with reference to the outline flowchart of FIG. In step S101, the image conversion module 67 checks the connection status of the MLC. Next, SRM21 memorize | stores the condition of all the hardware connected to the compound machine 1 containing MLC by step S102. The next step S103 corresponds to the verification target conversion function determination stage. In step S103, the image conversion module 67 creates an item to be checked in the SP mode, which is a mode for checking the MLC 45 described above, based on a setting level and a conversion device operation disable management flag described later. Check the flag.
[0052]
The next step S104 corresponds to the conversion function verification stage. In step S104, the image conversion module 67 checks the function item checked in the SP mode check function item flag with respect to the MLC 45. In step S105, the image conversion module 67 switches the SP mode. This is a change in the level of the content to be checked.
[0053]
Next, in step S106, the image conversion module 67 converts the image data for determination into the MLC 45, performs abnormality determination, and sets a conversion device operation disabled management flag. In the process of step S106, the image conversion module 67 performs a process corresponding to the verification result storage stage. In step S107, the image conversion module 67 sets the SP mode, and ends the processing related to the MLC 45 check.
[0054]
The following description will be made according to the order of the steps described above. First, the process for checking the connection status of the MLC 45 in step S101 will be described.
[0055]
In describing this process, the conversion device management flag used by the image conversion module 67 for checking the connection status of the MLC will be described first.
[0056]
A bit string 70 shown in FIG. 12 is a conversion device management flag, and is an 8-bit bit string. As shown in the figure, information on the presence / absence of Basic, Option P, and Option Q is assigned to this bit string from the lowest order.
[0057]
First, the presence / absence of Basic is indicated by the least significant bit as shown in FIG. When there is Basic, the least significant bit sets a bit as shown in the bit string 71, and when there is no Basic, no bit is set as shown in the bit string 72.
[0058]
The presence / absence of option P is indicated by the second least significant bit as shown in FIG. If the option P is present, the second least significant bit is set as shown in the bit string 73, and if not, the bit is not set as shown in the bit string 72.
[0059]
The presence or absence of the option Q is indicated by the third bit from the least significant bit. As shown in FIG. 15, when the option Q is present, the least significant bit is set as shown in the bit string 75, and when it is not present, the bit is set as shown in the bit string 76. Absent.
[0060]
In this way, the image conversion module 68 has a conversion device management flag based on the presence / absence determination register. In addition, these bits are not limited to three and increase or decrease according to the number of options.
[0061]
Next, the process for setting the conversion device management flag described above will be described with reference to the flowchart of FIG. Note that the flowchart in FIG. 16 is a detailed process of step S101 in FIG. 11 as described above.
[0062]
Step S 201 is activation of the image conversion module 67. In the next step S202, the image conversion module 67 acquires information of the MLC 45 through the image conversion device driver 69.
[0063]
From the acquired information of the MLC 45, the image conversion module 67 first determines whether there is an MLC 45 in step S203. If there is no MLC 45, the image conversion module 67 ends the process without setting the conversion device management flag in step S204.
[0064]
If it is determined in step S203 that there is an MLC 45, the image conversion module 67 sets the conversion device management flag of the MLC 45 in step S205. In step S206, the image conversion module 67 checks the number of options attached to the MLC 45.
[0065]
In the next step S207, the image conversion module 67 determines whether there is an attached option. If not, the image conversion module 67 ends the process. If there are options, the image conversion module 67 checks the number of all attached options in step S208.
[0066]
Next, the image conversion module 67 initializes n for option check in step S209. This n is used for a loop counter of processing starting from the next step.
[0067]
In step S210, the image conversion module 67 determines whether option n is connected. The option n indicates a number determined in advance for each option, for example, option P is first and option Q is second.
[0068]
If option n is not connected in step S210, the image conversion device management module 68 proceeds to step S215 without setting the n-th option management flag in step S211.
[0069]
If option n is connected in step S210, the image conversion module 67 sets an option management flag corresponding to the nth in step S212.
[0070]
In the next step S213, the image conversion module 67 counts the number of checked options that have been confirmed to be attached. This is a process for obtaining a simple sum of the number of options that have been confirmed so far.
[0071]
Next, the image conversion module 67 calculates a total for each option type. This total is, for example, a total of three options P and two options Q.
[0072]
In the next step S215, the image conversion module 67 determines whether all options have been checked. When the check is finished, the image conversion module 67 finishes the process, and when the check is not finished, the image conversion module 67 performs the process of step S210 again.
[0073]
The above is the process of step S101 in FIG. Next, details of the processing in step S102 of FIG. 11 will be described. Step S102 in FIG. 11 is processing in which the SRM 21 checks the connection status of all hardware. Among these checks, the MLC 45 check is performed based on information based on the conversion device management flag notified from the image conversion module 67.
[0074]
Next, a hardware management flag used in this process for checking the connection status of all hardware by the SRM 21 will be described.
[0075]
A bit string 77 shown in FIG. 17 is a hardware management flag, and is a 32-bit bit string. As shown in the figure, information on the presence / absence of Basic, Option P, and Option Q is assigned to this bit string from the lowest order.
[0076]
Further, the hardware management flag is different from the conversion device management flag described above in the bit string length. The reason why the number of bits of the hardware management flag is large is that the SRM 21 manages resources of other hardware.
[0077]
Hereinafter, the hardware management flag will be described with reference to FIGS.
[0078]
First, the presence / absence of Basic is indicated by the least significant bit as shown in FIG. When the Basic is present, the least significant bit is set as shown in the bit string 78, and when it is not present, the bit is not set as shown in the bit string 79.
[0079]
The presence / absence of option P is indicated by the second least significant bit as shown in FIG. When the option P is present, the second least significant bit is set as shown in the bit string 80, and when there is no option P, the bit is not set as shown in the bit string 80.
[0080]
The presence or absence of the option Q is indicated by the third bit from the least significant bit. As shown in FIG. 20, when the option Q is present, the least significant bit is set as shown in the bit string 82, and when not, the bit is set as shown in the bit string 83. Absent.
[0081]
Next, details of the processing in step S103 in FIG. 11 will be described. In this process, two flags are used: a check function item flag corresponding to the verification item information and a conversion operation disabled management flag corresponding to the operation disabled management information.
[0082]
Among these, the check function item flag indicates a conversion function to be verified for the conversion function of the MLC, and is used for verifying the conversion function. The inoperable management information indicates a conversion function that does not operate due to an abnormality in MLC.
[0083]
The format of these flags is the same as described below.
[0084]
FIG. 21 is a diagram showing a format of a flag. This format is divided into Basic, Option P, Q, and Composite. Corresponding to the conversion function of each, a number is assigned to the portion indicated by “0” in FIG.
[0085]
For example, FIG. 21 shows that Basic has six conversion functions, and options P and Q each have three conversion functions. In this format, these conversion functions are associated with image data formats A to J to be converted.
[0086]
For example, when converting format B, it is understood that two conversion functions are required: a conversion function corresponding to the second from the right of Basic and a conversion function corresponding to the right end of option Q. .
[0087]
As described above, since the flag format corresponds to the MLC conversion function and the conversion format, the MEU can determine which format cannot be converted due to the individual abnormality of the MLC conversion function. ing.
[0088]
Therefore, the flag of this format can be used as an MLC check function item flag and a conversion device operation disabled management flag.
[0089]
When used as a conversion device operation disable management flag, for example, as shown in FIG. 22, “1” is assigned to a portion corresponding to a conversion function having an abnormality. In the conversion device operation disable management flag of FIG. 22, it can be seen that there are two abnormalities in Basic, and there is one abnormality in each of options P, Q, and composite. A conversion function to which “1” is not assigned is an operating conversion function.
[0090]
Also, this conversion device operation disabled management flag is provided for each MLC when there are a plurality of MLCs. That is, when there are three MLCs, for example, three conversion device operation disabled management flags are also provided.
[0091]
Further, the conversion device inoperability management flag is stored in the NV-RAM 46 in order to retain the conversion device 1 even when power is not supplied to the MFP 1. Therefore, when power is supplied again, the MEU can refer to the conversion device operation disabled management flag.
[0092]
When used as a check function item flag, for example, as shown in FIGS. 23 and 24, any value of “0”, “1”, and “2” is substituted. These numbers to be substituted are determined by the SP mode level shown in FIG. This FIG. 25 will be described. FIG. 25 shows the SP mode level corresponding to the verification level, and the check contents to be performed at the level, NG_Funk setting, and Good_Func setting.
[0093]
First, NG_Funk setting and Good_Func setting will be described. The NG_Funk setting is a setting of the SP mode level for the conversion function determined to be inoperable stored in the conversion device inoperability management flag. The Good_Funk setting is an SP mode level setting for the conversion function determined to be operable stored in the conversion device operation impossibility management flag.
[0094]
In this way, for the check function item flag, the verification level verified for the conversion function can be set for each of the conversion function that does not operate and the conversion function that operates as indicated in the inoperable management information. .
[0095]
Next, the check contents will be described. The contents of the check are in each of the NG_Funk setting and the Good_Func setting, but in FIG. 25, both contents are the same. The contents of this check may be changed as necessary.
[0096]
The level 0 check content “Do not check” does not check anything. The level 1 “small amount data conversion check” is a check for converting the format of image data having a relatively small amount of data into MLC and verifying the conversion result. Since this check has a small amount of data, it can be checked in a relatively short time.
[0097]
Level 2 “data conversion check” is a check for converting the format of image data having a data amount larger than “small amount data conversion check” into MLC and verifying the conversion result.
[0098]
The levels 0, 1, and 2 described above correspond to the check function item flags “0”, “1”, and “2”.
[0099]
As described above, the check function item flag has verification level information “0”, “1”, and “2” indicating a plurality of verification levels that are different in the method of verifying whether the conversion function is abnormal.
[0100]
The verification level is determined according to the size of the image data that requires the MLC to convert the format.
[0101]
The SP mode check function item flag check process performed using these flags will be described with reference to the flowchart of FIG.
[0102]
In step S301, the image conversion module 67 initializes the check function item flag with “0”. Next, the image conversion module 67 determines whether or not the SP level mode of NG_Funk is 1 or more. If it is not 1 or more, that is, 0, the process proceeds to step S306.
[0103]
If the SP level mode is 1 or more, the image conversion module 67 determines in step S303 whether the SP level mode of NG_Funk is 2, and if not, that is, if 1, the process proceeds to step S304.
[0104]
In step S <b> 304, the image conversion module 67 sets 1 in the conversion function for which the flag is set in the conversion device operation disable management flag stored in the NV-RAM 46 and the same conversion function in the check function item flag. In other words, this process is a process for checking the conversion function determined to be abnormal in SP mode level 1.
[0105]
As an example of the check function item flag set by this processing, when the conversion device operation disabled management flag is the flag shown in FIG. 22, the check function item flag is the flag shown in FIG.
[0106]
In step S303, it is determined whether or not the SP level mode of NG_Funk is 2. In the case of 2, the image conversion module 67 advances the process to step S305. Then, the image conversion module 67 sets 2 in the conversion function in which the flag is set in the conversion device operation disable management flag stored in the NV-RAM 46 and the same conversion function in the check function item flag.
[0107]
From the next step, the processing related to Good_Func is performed. In step S306, the image conversion module 67 determines whether or not the SP level mode of Good_Funk is 1 or more. If it is not 1 or more, that is, 0, the process proceeds to step S310.
[0108]
If the SP mode levels of Good_Func and NG_Funk are both 0 in step S310, the image conversion module 67 initializes the check function item flag and the conversion device operation disabled management flag in step S311, and ends the processing. If the SP mode levels of Good_Func and NG_Funk are not 0 in step S310, the image conversion module 67 ends the process.
[0109]
The process returns to step S306. If the SP level mode is 1 or more in step S306, the image conversion module 67 determines in step S307 whether the SP level mode of Good_Funk is 2, and if not, that is, if 1, the process proceeds to step S309. To proceed.
[0110]
In step S309, the image conversion module 67 sets 1 in the conversion function that is not set in the conversion device operation disable management flag stored in the NV-RAM 46 and the same conversion function in the check function item flag. The process is terminated. That is, this process is a process for checking the conversion function determined to be normal in SP mode level 1.
[0111]
In step S307, it is determined whether or not the SP level mode of Good_Funk is 2. In the case of 2, the image conversion module 67 advances the processing to step S308. Then, the image conversion module 67 sets the conversion function not flagged in the conversion device operation disable management flag stored in the NV-RAM 46 and sets the same conversion function in the check function item flag to 2 for processing. finish.
[0112]
The process described above is the SP mode check function item flag check process. Next, details of the processing in step S104 in FIG. 11 will be described. This process is a process of checking the check function item according to the check function item flag set in step S103. As described with reference to FIG. 9, this process may be performed when the MLC is exchanged and the MLC is activated or when the multi-function apparatus 1 is activated.
[0113]
This process will be described using a sequence diagram and a flowchart. First, the abnormality of the MLC to be checked will be described. There are two main possibilities for abnormalities in MLC. One is an abnormality of the MLC main body due to an abnormality of an IC or the like mounted on the MLC, and the other is a bus error which is an abnormality of a PCI bus used as an interface.
[0114]
Among these, what is verified in the present embodiment is when the MLC main body is abnormal. In this case, the MEU 44 verifies whether the MLC conversion function is abnormal based on the data content of the image data converted by the MLC that requested the conversion, and the MEU 44 requests that the MLC convert the format of the image data. There are two patterns for verifying whether the conversion function of the MLC is abnormal based on the time when measurement was started.
[0115]
Of these two patterns, the sequence diagram shown in FIG. 27 is a pattern in which the MEU 44 verifies the conversion result. In step S <b> 1, the image conversion module 67 sends a conversion request to the image conversion device driver 69. In the next step S2, the image conversion device driver 69 makes a conversion request to the MLC 45.
[0116]
When the conversion of the image data format is completed, the MLC 45 notifies the image conversion device driver 69 of the completion in step S3. The image conversion device driver 69 notifies the image conversion module 67 of an end notification in step S4. The image conversion module 67 that has received the end notification verifies the conversion result by the MLC 45. With this verification, the MEU 44 detects an abnormality in the MLC 45.
[0117]
The next sequence diagram shown in FIG. 28 is a pattern to be verified based on the time at which measurement was started. In step S <b> 5, the image conversion module 67 sends a conversion request to the image conversion device driver 69. In the next step S6, the image conversion device driver 69 makes a conversion request to the MLC 45.
[0118]
However, since the end notification is not notified from the MLC 45 even when a predetermined time elapses after the conversion request is made, the image conversion device driver 69 determines that a time-out has occurred, and in step S7, This is notified to the image conversion module 67. With this notification, the MEU 44 detects an abnormality in the MLC 45.
[0119]
Next, processing for checking items of the check function will be described with reference to FIG. In step S401, the MEU 44 initializes the loop counter N used in the subsequent processing. This N is counted by the number of formats that can be converted by the check function item flag. For example, in the case where the check function item flag is FIG. 21, since there are ten formats that can be converted, N is counted from 1 to 10 or from 0 to 9.
[0120]
From step S402, the function item of the Nth format determined by the counter N is checked. In step S403, the MEU 44 determines whether the SP mode level of the Nth form is 1 or more. If the SP mode level is not 1 or higher, the SP mode level is 0, so no check is made and the process ends.
[0121]
If the SP mode level of the Nth function item is 1 or more, the MEU 44 converts the Nth function item to the MLC 45 in step S406 if the SP mode level of the Nth function item is 1. When the end of conversion is notified, the sum value of the converted image data is checked. This image data is check image data, and the MEU 44 prepares a sum value of the image data when normal conversion is performed.
[0122]
Similarly, if the SP mode level of the Nth function item is not 1 in step S404, the MLC 45 is caused to convert the format of the image data using the conversion function of the Nth function item in step S405, and the conversion is completed. When notified, the sum value of the converted image data is checked.
[0123]
In step S407, the MEU 44 determines whether the conversion execution result of the MLC 45 is a timeout or an abnormal sum value. If it is not determined that time-out or abnormality has occurred, the MEU 44 advances the processing to step S410.
[0124]
If it is determined in step S407 that a timeout or an abnormality has occurred, in step S408, the MEU 44 sets 1 to a flag corresponding to the conversion function used by the format among the conversion device operation disabled flags. In step S409, the MEU 44 sets 0 to the flag corresponding to the conversion function used by the format determined to be timed out or abnormal among the check function item flags.
[0125]
When one type of check is completed in this way, the MEU 44 counts the loop counter N in step S410 in order to check the next type. Next, the MEU 44 determines whether or not all the check function item flags are checked by the loop counter N in step S411. If all are checked, the MEU 44 ends the process, and if not checked yet, performs the process of step S402 again.
[0126]
In the processing described above, how the conversion device operation disabled flag is actually set will be described with reference to the drawings. FIG. 30 shows a conversion device operation disabled flag when it is determined by Basic that a timeout or an abnormality has occurred when format B converted by Basic and option Q is converted to MLC45. In this case, since a timeout or abnormality is caused by Basic, 1 is set only for Basic.
[0127]
FIG. 31 shows a conversion device operation disable flag when a timeout or an error is determined by option P when the format C converted by the Basic function and the option P conversion function is converted to MLC45. Yes. In this case, since timeout or anomaly is caused by option P, 1 is set only for option P.
[0128]
Next, FIG. 32 shows a conversion device operation disable flag when it is determined that a timeout or an abnormality has occurred when the format H converted by the Basic conversion function and the option Q conversion function is converted to MLC45. In this case, since it is a composite, 1 is set in the flag corresponding to the format H.
[0129]
After completing the MLC check in this way, the SP mode switching process in step S105 of FIG. 11 is performed next. The SP mode switching process is a process of switching the SP mode level for the next MLC check. The Change setting for switching the SP mode level will be described with reference to FIG. As shown in FIG. 33, there is also a level in the Change setting corresponding to the verification level change information, Level 0 is no switching, Level 1 is Level Up switching, and Level 2 is Level Down switching.
[0130]
The process of switching the SP mode level according to this level will be described with reference to the flowchart of FIG.
In step S501, the MEU 44 determines whether the Change setting is equal to or higher than Level 1. If the change setting is less than Level 1, that is, Level 0, the processing ends without switching the SP mode levels of NG_Func and Good_Func.
[0131]
If the change setting is determined to be Level 1 or higher in step S501 and the change setting is determined to be level 1 in step S502, the MEU 44 increases the SP mode levels of both NG_Func and Good_Func by 1.
[0132]
If it is determined in step S501 that the Change setting is equal to or higher than Level 1, and it is determined in Step S502 that the Change setting is different from Level 1, that is, Level 2,
Decrease both SP modes of NG_Func and Good_Func by 1.
[0133]
Next, the execution of image data format conversion and failure determination, which are the processing of step S106 in FIG. 11, will be described in detail with reference to FIG.
[0134]
In step S601, the conversion request from the higher-level application requests the IMH 23 to convert the image data format via the SRM 21. In the next step S602, the IMH 23 issues a conversion request to the MEU 44.
[0135]
In step S603, when the MEU 44 is requested by the IMH 23 to convert the format of the image data, the MEU 44 determines whether or not the format of the received image data can be converted based on the conversion function disabled management flag. This is determined by whether or not the conversion function flag used for executing the conversion is set in the conversion function disabled management flag.
[0136]
If it is not set, the image data format can be converted, and the image conversion module 67 of the MEU 44 issues a conversion request to the image conversion device driver 69 in step S604.
[0137]
Next, the MEU 44 determines whether the conversion end response to the conversion request has ended normally without time-out or abnormality. In the case of timeout or abnormality, the MEU 44 sets a conversion function and a conversion device operation flag used for conversion of the format of the requested image data in step S608, and stores them in the NV-RAM 46.
[0138]
Next, if a plurality of MLCs are mounted in step S609, the MEU 44 may have other conversions that can convert the format of the requested image data, and the conversion function disabled flag is not set. Judge whether. If there is another MLC, the MEU 44 designates another MLC in which the conversion function disabled flag is not set in step S611 to the IMH 23, and the IMH 23 performs the process of step S603 again.
[0139]
As described above, when the format of the image data received from the IMH 23 cannot be converted by one MLC, the MEU 44 determines whether or not it can be converted by another MLC.
[0140]
If there is no other MLC in step S609, the MEU 44 notifies the IMH 23 that conversion is impossible in step S610, and the process proceeds to step S607.
[0141]
The process returns to step S605. If the conversion of the format of the image data is normally completed in step S605, the MEU 44 notifies the result of the conversion request to the IMH 23 in step S606.
[0142]
In step S607, the IMH 23 notifies the result of the conversion request to the upper application through the SRM 21, and ends the process.
[0143]
The above is the process of step S106 in FIG. Next, the process of step S107 in FIG. 11 will be described.
[0144]
The processing in step S107 is SP mode level setting. This SP mode level is a level indicating the contents to be verified, as shown in FIG.
[0145]
The setting of the SP mode level is a process performed after a series of processes such as the failure determination in steps S101 to S106 described so far is completed and the multi-function apparatus 1 enters a normal operating state. By this process, the operator can change the SP mode level as necessary, and can arbitrarily set the SP mode level.
[0146]
【The invention's effect】
As described above, according to the present invention, an image forming apparatus and a conversion function management method that efficiently manage a hardware conversion function for converting the format of image data can be obtained.
[Brief description of the drawings]
FIG. 1 is a configuration diagram of an embodiment of a compound machine according to the present invention.
FIG. 2 is a hardware configuration diagram of an embodiment of a compound machine according to the present invention.
FIG. 3 is a diagram showing the inside of an MLC.
FIG. 4 is a software block diagram related to image data format conversion.
FIG. 5 is a diagram showing processing in a state where MLC is normal.
FIG. 6 is a diagram showing processing when an abnormality occurs in MLC.
FIG. 7 is a diagram illustrating a process when an abnormality occurs in the MLC.
FIG. 8 is a diagram showing a state of exchanging MLCs.
FIG. 9 is a diagram illustrating a process of checking an MLC.
FIG. 10 is a diagram illustrating a state in which the MLC has returned to a normal state.
FIG. 11 is a schematic flowchart showing overall processing.
FIG. 12 is a diagram showing a conversion device management flag.
FIG. 13 is a diagram showing a conversion device management flag.
FIG. 14 is a diagram showing a conversion device management flag.
FIG. 15 is a diagram illustrating a conversion device management flag.
FIG. 16 is a flowchart illustrating processing for setting a conversion device management flag.
FIG. 17 is a diagram illustrating a hardware management flag.
FIG. 18 is a diagram illustrating a hardware management flag.
FIG. 19 is a diagram illustrating a hardware management flag.
FIG. 20 is a diagram illustrating a hardware management flag.
FIG. 21 is a diagram illustrating a format of a flag.
FIG. 22 is a diagram showing a conversion device operation disable management flag.
FIG. 23 is a diagram illustrating check function item flags.
FIG. 24 is a diagram showing check function item flags.
FIG. 25 is a diagram illustrating check contents.
FIG. 26 is a flowchart showing SP mode check function item flag check processing;
FIG. 27 is a sequence diagram illustrating processing for verifying a conversion result;
FIG. 28 is a sequence diagram showing processing in the case of timeout.
FIG. 29 is a flowchart illustrating processing for checking items of a check function.
FIG. 30 is a diagram illustrating a state in which a conversion device operation disabled flag is set.
FIG. 31 is a diagram illustrating a state in which a conversion device operation disabled flag is set.
FIG. 32 is a diagram illustrating a state in which a conversion device operation disabled flag is set.
FIG. 33 is a diagram showing levels of Change setting.
FIG. 34 is a flowchart showing processing for switching the SP mode level;
FIG. 35 is a flowchart illustrating conversion processing of image data format and failure determination processing.
[Explanation of symbols]
1 ... Fusion machine
2 ... Software group
3 ... Fusion machine start-up part
4 ... Hardware resources
5. Application layer
6 ... Platform
7. Control service layer
8 ... Handler layer
9. Printer app
10 ... Copy application
11 ... Fax application
12 ... Scanner application
13 ... Network Control Service (NCS)
14 ... Delivery Control Service (DCS)
15 ... Operation Panel Control Service (OCS)
16. Fax control service (FCS)
17 ... Engine Control Service (ECS)
18 ... Memory Control Service (MCS)
19 ... User Information Control Service (UCS)
20. System control service (SCS)
21 ... System Resource Manager (SRM)
22. Fax control unit handler (FCUH)
23 ... Image memory handler (IMH)
24 ... Hardware resources
25 ... Monochrome laser printer (B & W LP)
26 ... Color laser printer (Color LP)
27 ... Application Program Interface (API)
28 ... Engine I / F
30 ... Controller
31 ... CPU
32 ... System memory (MEM-P)
33 ... North Bridge (NB)
34 ... South Bridge (SB)
35 ... AGP (Accelerated Graphics Port)
36 ... ASIC
37 ... Local memory (MEM-C)
38 ... Hard disk drive (HD)
39 ... Operation panel
40. Fax control unit (FCU)
41 ... USB device
42 ... IEEE1394 device
43. Engine part
44 ... MEU
45, 45a, 45b ... MLC
46 ... NV-RAM
61 ... PCI interface
62: Presence / absence judgment register
63 ... Basic
64 ... Option P
65 ... Option Q
66 ... Top apps
67. Image conversion module
69: Image conversion device driver
70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83 ... bit string

Claims (18)

In an image forming apparatus having hardware resources used in image forming processing and a program related to image formation,
One or more conversion hardware having one or more conversion functions for converting the format of the image data;
Nonvolatile storage means for storing conversion function information relating to the conversion function of the conversion hardware;
The conversion function of the conversion hardware and a verification means for verifying whether abnormal, have a conversion hardware management means for managing the conversion hardware,
The nonvolatile storage means includes
Further, verification item information indicating a verification item of a conversion function to be verified, and verification level information indicating a verification level of the verification item are stored,
The verification means includes
According to the verification level information stored in the non-volatile storage means, first image data that is image data for verification, or second image data for verification that has a smaller data amount than the first image data. One of the image data is converted by the conversion function, and whether or not the conversion function is abnormal is verified based on a conversion result .   The image forming apparatus according to claim 1, wherein the conversion hardware management unit includes, as the conversion function information, inoperability management information indicating a conversion function that does not operate due to an abnormality of the conversion hardware.   The image forming apparatus according to claim 2, wherein the inoperable management information further includes information indicating an operating conversion function.   The image forming apparatus according to claim 2, wherein the inoperability management information is provided for each of the conversion hardware.   5. The image forming apparatus according to claim 2, wherein the conversion hardware management unit determines a format of image data that cannot be converted by the conversion hardware based on the operation disable management information. . The image forming apparatus according to claim 1 , wherein the conversion hardware management unit performs the verification when the image forming apparatus is activated. The translation hardware management means, an image forming apparatus according to claim 1, characterized in that the verification at the start of the conversion hardware. The translation hardware management means by requesting the conversion of format of image data to the conversion hardware, the image forming apparatus according to any one of claims 1 to 7, characterized in that said verification . The translation hardware management means to claim 8, wherein the conversion hardware that requested the conversion based on the data contents of the image data conversion, the conversion function of the conversion hardware, characterized in that to verify whether abnormal The image forming apparatus described. The conversion hardware management means verifies whether or not the conversion function of the conversion hardware is abnormal based on the time when measurement was started when the conversion hardware requested to convert the format of image data. The image forming apparatus according to claim 8 . The verify level to be validated against the conversion function, the a disablement management does not work shown in the information conversion function, claim 1, characterized in that it is settable to the respective conversion functions operating 1 The image forming apparatus according to any one of 0 . The image forming apparatus according to convert verify level change information for hardware management means changes the verify level, any one of claims 1 to 1 1, characterized in that it further comprises. Image data conversion management means for requesting the conversion hardware management means to convert the format of the image data;
When the conversion hardware management means is requested by the image data conversion management means to convert the format of the image data, the conversion hardware management means determines whether the requested format of the image data can be converted based on the inoperable management information. The image forming apparatus according to claim 2 , wherein the determination is made. The conversion hardware management means, when the format of the image data received from the image data conversion management means cannot be converted by a single conversion hardware,
The image forming apparatus according to claim 1 3, characterized in that determining whether convertible by other translation hardware. The hardware in addition to the basic conversion portion that comes in advance, any one of claims 1 1 4, characterized in that the additional converter for adding conversion function can be added one or more The image forming apparatus described in 1. Wherein the conversion function provided in the additional conversion unit, an image forming apparatus according to claim 1 5, characterized in that the conversion function to improve the image quality of the image data. The additional conversion unit conversion function provided in the image forming apparatus according to claim 1 5 or 16, characterized in that a conversion function for converting the format of image data that can not converted by the basic transformation unit. Conversion function of an image forming apparatus having hardware resources used in image forming processing, a program related to image formation, and one or more conversion hardware having one or more conversion functions for converting the format of image data A management method,
In accordance with the conversion function information related to the conversion function, a verification target conversion function determination step for determining the conversion function to be verified as to whether or not the conversion function is abnormal,
A conversion function verification step of performing verification of the conversion function as a target of the verification,
Have a verification result storing step of storing the result of the verification in the non-volatile memory device,
The conversion function verification step includes:
The amount of data from the first image data, which is image data for verification, or from the first image data, in accordance with verification level information indicating the verification level of the conversion function to be verified that is stored in advance One of the second image data, which is image data for verification with a small amount, is converted by the conversion function that is the object of verification, and whether the conversion function that is the object of verification is abnormal based on the conversion result The conversion function management method characterized by verifying .

Images