JP2008238549A - Image formation device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To minimize the restoration time of a printer 100 connected to a network 300. <P>SOLUTION: A sensor 1 detects the status of the printer 100. A memory 2 memorizes two or more transmitting addresses connected to the network 300. If the sensor 1 detects the abnormality of the status of the device, an estimation demanding section 3 transmits the abnormality information for showing the abnormality of the device status to two or more the transmitting addresses memorized in the memory 2 and demands the reply of the restoration information to make the abnormality restored. A selector 4 chooses one from the two or more restoration information received by the estimation demanding section 3. A maintenance request transmitting section 5 outputs the maintenance requesting information to the address of reply origin chosen by the selector 4 in order to make the abnormality of the device status restored. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to an image forming apparatus that is connected to a network and forms an image based on input image information.

Conventionally, when an abnormal state such as running out of toner is detected in a network printer as an image forming apparatus, an error notification indicating the abnormal state is transmitted to a computer or the like that has transmitted print data. On the other hand, Patent Document 1 discloses a technique in which an error notification is transmitted to a maintenance request destination registered in advance when an abnormal state such as toner out is detected by a network printer.
JP 09-305334 A

  However, in the above-mentioned Patent Document 1, there is a problem to be solved that recovery is delayed when a maintenance request destination registered in advance is busy or cannot be handled immediately for some reason. It was.

  The present invention provides an image forming apparatus that is connected to a network and forms an image based on input image information, a detection unit that detects an apparatus state of the image forming apparatus, and a plurality of transmission destinations connected to the network When the detection unit detects an abnormality in the device state, the abnormality information indicating the abnormality in the device state is transmitted to the plurality of transmission destinations stored in the storage unit. A recovery information request unit that requests a return of recovery information for recovery, a selection unit that selects one of the plurality of recovery information received by the recovery information request unit, and the recovery information selected by the selection unit The main feature is that a maintenance request information output unit for outputting maintenance request information is provided for the reply source to recover the abnormality of the apparatus state.

  An image forming apparatus according to the present invention stores a plurality of transmission destinations in a storage unit in advance, transmits abnormality information detected inside the image forming apparatus to the plurality of transmission destinations, and transmits the plurality of transmission destinations from the plurality of transmission destinations. The time information necessary for recovery of the above abnormalities is collected, the destination that can be recovered in the shortest time is selected, and the recovery of the abnormal state of the device status is requested, so that the recovery time can be minimized. Get.

  Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings.

Description of (Configuration) FIG. 1 is a block diagram of a configuration of a printer according to the first embodiment.
As shown in the figure, a printer 100 as an image forming apparatus in this embodiment includes a sensor 1, a memory 2, an estimation request unit 3, a selector 4, a maintenance request transmission unit 5, a timer 6, and an interface 7. , Receiving section 8, printing mechanism section 9, CPU 10, and internal bus 500.

  The sensor 1 is a part that shares a role as a detection unit that detects an abnormal state of the printer 100. The memory 2 is a part that shares a role as a storage unit that stores print data, a maintenance request destination list, a reply to estimate, and a control program. That is, the memory 2 stores print data, a maintenance request destination list, an estimate reply, and a control program executed by the CPU 10, and further, data from the request source is written via the internal bus 500 in response to a request, or This is the part where data is read from the request source. Here, the contents of the maintenance request destination list will be described.

FIG. 2 is an explanatory diagram of a maintenance request destination list according to the first embodiment.
This figure explains the state of the maintenance request destination list on the memory 2. As shown in the figure, in the maintenance request destination list, the network addresses of the maintenance request destination PCs are stored as one record, and this record is arranged by the number of maintenance request destinations. The number of records is managed separately as the number of maintenance request destinations.

  Returning to FIG. 1, the estimate request unit 3 is a part that transmits an estimate request 503 necessary for the printer 100 to recover from an abnormal state to a maintenance request destination connected to the network 300 via the interface 7.

  The selector 4 is a part that shares the role of a selection unit that selects an estimate that can be recovered the fastest from among the estimate responses. In other words, the selector 4 is a part that reads the estimated answer from the estimated answer area on the memory 2 and outputs the optimum estimated answer source address to the maintenance request transmitting unit 5 as the request destination address 504. The maintenance request transmission unit 5 is a part that shares a role as a maintenance request information output unit that transmits a maintenance request to a maintenance request destination that has returned an estimate that can be recovered earliest. That is, the maintenance request transmission unit 5 is a part that transmits the maintenance request 505 to the maintenance request destination connected to the network 300 via the interface 7 with the request destination address 504 as the destination.

  The timer 6 is a part that shares the role as a time measuring unit that measures the estimated response waiting time. That is, the timer 6 outputs the elapsed time from the operation ON instruction by the CPU 10 upon request. The interface 7 is a part that connects the printer 100 and the network 300 and performs an interface function for managing data transmission / reception.

  The receiving unit 8 is a part that receives received data from the network 300 via the interface 7. The type of the received data 501 input from the network 300 via the interface 7 is determined by the receiving unit 8 and written to an appropriate area on the memory 2. If the receiving unit 8 determines that the received data 501 is an estimated answer that is a response to the estimate request 503, the receiving unit 8 writes the received data 501 into the estimated answer area on the memory 2.

  The printing mechanism unit 9 is a part that reads the print data on the memory 2 and forms an image. The state 502 of the printing mechanism unit 9 is output to the sensor 1, and the sensor 1 outputs detection information upon request.

  The CPU 10 is a microprocessor that executes a control program on the memory 2 and controls each block connected to the internal bus 500. The internal bus 500 is a bus that connects the sensor 1, the memory 2, the estimate request unit 3, the selector 4, the maintenance request transmission unit 5, the timer 6, the reception unit 8, the printing mechanism unit 9, and the CPU 10 to each other.

FIG. 3 is a system configuration diagram of a printing system to which the present invention is applied.
As shown in the figure, the printer 100 is connected to a maintenance request destination PC 200, a maintenance request destination PC 201, and a maintenance request destination PC 202 via a network 300. Here, the maintenance request destination PC is a consumables store, a printer repair shop, or the like. The network 300 may be a public line or the Internet.

Description of (Operation) The printer 100 of the first embodiment described above operates as follows.
FIG. 4 is a flowchart illustrating the operation of the first embodiment.
This flowchart is started when the printer 100 accepts print data. Hereinafter, the operation of the printer 100 from step S001 to step S023 will be described with reference to FIG.

Step S001
First, when receiving the print data, the receiving unit 8 writes the received data 501 as print data in the area of the print data on the memory 2 and accumulates it until it is received.

Step S002
The printing mechanism unit 9 reads the print data from the print data area of the memory 2 and starts the printing operation.

Step S003
When the printing operation is started in the printing mechanism unit 9, the CPU 10 monitors the sensor 1 and determines whether or not the apparatus indicates an abnormal state. If the detection information read from the sensor 1 does not indicate an abnormal state of the apparatus, the process proceeds to step S004, and if it indicates an abnormal state, the process proceeds to step S006.

Step S004
The CPU 10 determines whether or not the printing mechanism unit 9 has completed the printing work. If the printing work has been completed, the process proceeds to step S005, and if not completed, the process returns to step S003 to determine the detection information of the sensor 1. Repeat from (Step S003).

Step S005
When the CPU 10 detects the completion of the printing operation of the printing mechanism unit 9, this flowchart started by reception of the print data ends.

Step S006
When the CPU 10 determines that the apparatus is in an abnormal state from the detection information read from the sensor 1, the CPU 10 causes the estimate request unit 3 to generate an estimate request. The contents of the estimate request will be described here.

FIG. 5 is an explanatory diagram of the contents of the estimate request.
As shown in the figure, the estimate request includes an address indicating the destination request destination, a printer address, an identification code indicating the type of this notification, a unique code, an error number indicating the number of items in an abnormal state, and each error code. The network address of the printer 100 is set to the printer address of the estimation request. Here, the contents of the identification code will be described.

FIG. 6 is an explanatory diagram of the contents of the identification code.
As shown in the figure, the identification code is an identifier assigned so as not to be duplicated for each notification content. In this embodiment, the estimation request is defined as 0x5555 (hexadecimal notation), and the estimation response is defined as 0xAAAAA. Returning to FIG. 5, the unique code is an identifier generated every time an abnormal state is detected, and is generated so that a unique code having the same value does not exist at the same time. The number of errors indicates the number of items in an abnormal state detected by the sensor 1, and indicates the number of items of subsequent error codes. Here, the contents of the error code will be described.

FIG. 7 is an explanatory diagram of the contents of the error code according to the first embodiment.
As shown in the figure, the error code is an identifier indicating the specific contents of the abnormal state, and the error codes are defined so as not to overlap each other. Returning to the flowchart (FIG. 4).

Step S007
The estimate request unit 3 reads one record from the maintenance request destination list on the memory 2.

Step S008
The estimate request unit 3 sets the network address described in the read maintenance request destination record to the maintenance request destination address of the previously generated estimate request, and transmits it as the estimate request 503.

Step S009
It is determined whether all the maintenance request destination lists have been read. If the last record in the maintenance request destination list has not been read, the process returns to step S007 to set and transmit the network address described in the read records as the transmission destination. If repeated until the last record is read, the process proceeds to step S010.

Step S010
The CPU 10 initializes the value of the timer 6 in order to measure the reception waiting time.

Step S011
The receiving unit 8 checks whether or not an estimate reply has been received. If received, the process proceeds to step S012, and if not received, the process proceeds to step S013.

Step S012
When receiving the estimated response, the receiving unit 8 writes the received data 501 as an estimated response in the estimated response area on the memory 2. Here, the contents of the estimate answer will be described.

FIG. 8 is a diagram for explaining the contents of an estimate reply.
As shown in the figure, the estimate response includes a printer address, a maintenance request destination address, an identification code, a unique code, and time information necessary for recovery. The printer address of the estimate reply is the network address of the printer 100. The maintenance request destination address indicates the network address of the transmission destination of the estimate reply. As shown in FIG. 6, the estimated answer is defined as 0xAAAA in this embodiment. The unique code indicates the same value as the unique code assigned to the quote request, and the quote request and the quote answer are associated with each other. The required time information is defined as the maintenance time required to recover from the abnormal state indicated by the error code transmitted in the estimate request, and is determined from the maintenance request destination schedule, the preparation period of the members required for recovery, and the like. The contents of the estimated answer area on the memory 2 will be described.

FIG. 9 is an explanatory diagram of an estimation response area according to the first embodiment.
As shown in the figure, the estimated response area is an area in which the network address of the maintenance request destination PC and time information necessary for recovery are stored as one record, and this record is arranged by the number of received estimated responses. The number of records is managed separately as the number of estimated responses received. This estimation response area is secured until the printer 100 recovers from the abnormal state after the printer 100 detects the abnormal state. When the receiving unit 8 receives the estimate response, it sets the maintenance request destination address of the estimate response to the network address of the maintenance request destination PC, generates a record in which the time information required for the estimate response is set to the time information necessary for recovery, and estimates Add to the response area, and add the number of estimated responses received. Returning to the flowchart (FIG. 4).

Step S013
The CPU 10 determines whether or not the reception waiting time set by the timer 6 has elapsed. If it has elapsed, the process proceeds to step S014, and if it has not elapsed, the process returns to step S011 and repeats waiting for an estimate response. . When the reception waiting time set by the timer 6 elapses, the reception of the estimated response by the receiving unit 8 is stopped, and the estimated response received thereafter is ignored. This prevents the maintenance from being delayed due to a slow answer reply.

Step S014
The CPU 10 determines the number of estimate responses received on the memory 2.
If the estimated number of received responses is 0, the process proceeds to step S015, and if the received number is not 0, the process proceeds to step S016.

Step S015
The CPU 10 determines that there is no maintenance request destination within the range that can be answered within the set reception waiting time, increases the setting of the reception waiting time, returns to step S007, and starts again from the transmission of the estimate request.

Step S016
When the CPU 10 determines the number of received estimate responses in the memory 2 and determines that the number of received responses is one or more, the CPU 10 performs initialization by substituting the maximum value into the minimum time variable in the selector 4 in order to select the estimated response. To do.

Step S017
The selector 4 reads one estimate answer record from the estimate answer area on the memory 2.

Step S018
The selector 4 compares whether or not the required time of the estimated reply record read is shorter than the minimum time variable. If it is smaller, the process proceeds to step S019, and if larger, the process proceeds to step S021. In the first estimate response record, the value of the minimum time variable is the maximum, so this condition is always met, and thereafter the comparison is made with the required time for the estimate response that matched earlier.

Step S019
If the comparison condition is met, the required time for the estimated response record is set in the minimum time variable.

Step S020
The network address of the maintenance request destination PC of the estimate response record is set in the request destination address 504.

Step S021
It is determined whether or not all estimated response records on the memory 2 have been compared. If all estimated values have been determined, the process proceeds to step S022, and if there is an estimated response record that has not been compared yet, the process returns to step S017. Repeat from reading estimate response record. In the initialization of the minimum time variable by the previous CPU 10 (step S016), by substituting a predetermined threshold value for the minimum time variable and initializing it, an estimated answer that requires a time longer than the threshold value may be excluded. . In this case, it is necessary to provide a procedure for reviewing the setting and starting over from the request for quotation when there is no corresponding request destination because all quotation responses are excluded.

Step S022
When the comparison of all the quotation response records is completed, the maintenance request transmission unit 5 generates a maintenance request 505 according to an instruction from the CPU 10 and transmits it to the maintenance request destination. The contents of the maintenance request will be described here.

FIG. 10 is an explanatory diagram of the contents of the maintenance request.
The maintenance request includes a maintenance request destination address, a printer address, an identification code, and a unique code. The maintenance request destination address indicates the transmission destination network address of the maintenance request, and the request destination address indicated by the selector 4 is set. As the printer address, the network address of the printer 100 is set. As shown in FIG. 6, the identification code is defined as maintenance request 0xFFFF in this embodiment. The unique code has the same value as the unique code of the estimate request and the estimate answer, and is associated with the estimate request and the estimate answer. Returning to the flowchart (FIG. 4).

Step S023
After transmitting the maintenance request 505, the UPU 10 reads the detection information from the sensor 1 and determines whether the printer 100 has recovered from the abnormal state. As long as the detection information of the sensor 1 indicates an abnormal state, the printer 100 is abnormal. Repeat the determination of whether or not the state has recovered. When it is determined that the printer 100 has recovered from the abnormal state based on the detection information of the sensor 1, the printing operation is resumed by the printing mechanism unit 9, and the CPU 10 reads the detection information from the sensor 1 until the printing operation is completed. It repeats from the determination (step S003) whether the abnormal state is not shown. In this way, the flow finally reaches step S005 and ends.

FIG. 11 is a time-series change explanatory diagram of the printing system according to the first embodiment.
The time series of operations in the printer 100 (FIG. 3) is shown in the vertical direction of the leftmost column in the figure, and is connected to the network 300 (FIG. 3) in correspondence with the time series of the printer 100 (FIG. 3). The time series of operations in the maintenance request destination PC 200, the maintenance request destination PC 201, and the maintenance request destination PC 202 are shown. The operation of each maintenance request destination will be described below in relation to the time series of the operation of the printer 100.

Timing t001
Black toner runs out while the printer 100 is printing.

Timing t002 to timing t004
The printer 100 changes the estimate request to the maintenance request destination PCs 200, 201, and 202 described in the maintenance request destination list on the memory 2 in order, and transmits the estimate request. When transmission to all maintenance request destinations is completed, the printer 100 starts measurement by the timer 6 (FIG. 1) (answer waiting time in the figure). Each maintenance request destination PC has necessary time information for each error code included in the estimate request, and the required time information is obtained in association with the error code included in the estimate request. Here, the contents of the necessary time information will be described.

FIG. 12 is a diagram for explaining the contents of necessary time information for each error code.
In the figure, (a) shows necessary time information possessed by the maintenance request destination PC 200, (b) shows necessary time information possessed by the maintenance request destination PC 201, and (c) shows necessary time information possessed by the maintenance request destination PC 202. , Respectively. In this case, since the black toner has run out in the printer 100, the error code is 0x01, the required time of the maintenance request destination PC 200 is 60 minutes, the required time of the maintenance request destination PC 201 is 30 minutes, and the maintenance request destination PC 202 The required time is 120 minutes. Returning to FIG. 11, the time-series change will be described. Hereinafter, the process returns to the time series (FIG. 11).

Timing t005 to timing t006
The maintenance request destination PCs 200 and 201 receive the request for quotation, and automatically reply with a quotation response, and the printer 100 receives the response.

Timing t007
At this point, it is assumed that the reply waiting time of the timer 6 (FIG. 1) has timed out.

Timing t008
The maintenance request destination PC 202 receives the estimate request and automatically responds with the estimate response. However, since the estimate response of the maintenance request destination PC is received by the timer 6 of the printer 100, the response waiting time is reached. The received estimated response of the maintenance request destination PC 202 is ignored.

Timing t009
The printer 100 compares the required times of the maintenance request destinations 200 and 201 received during the reply waiting time. In this case, the maintenance request destination 201 shows a short time of 30 minutes (FIG. 12), so the maintenance request destination 201 Send the maintenance request and end the sequence.

FIG. 13 is an explanatory diagram of a notification flow according to the first embodiment.
This figure shows the correlation between the contents of the request for quotation (FIG. 5), the reply for quotation (FIG. 8), and the maintenance request (FIG. 10). Details of the contents will be described below.

  First, the transmission destination of the quotation request is acquired from the maintenance request destination list on the memory 2 and transmitted (R001). Each maintenance request destination PC (200, 201, and 202) that has received the estimate request derives the required time from a table having the error code (R002) included in the estimate request for each maintenance request destination PC.

  In the case of the maintenance request destination PC 200, a value of 60 minutes, which is the time of the error code 0x01 of black toner out, is obtained (R003), and is set to the time required for the estimate reply. If there are a plurality of error codes, the total time of each error code is set as the time required for the estimated response.

  Similarly, the required time is also generated in the maintenance request destination PCs 201 (R005) and 202 (R006). The unique code included in the quote answer is set as is. When the estimate reply is completed, it is transmitted to the printer 100.

  For the estimate response from the maintenance request destination 200 received first by the printer 100, the transmission source address (R007) is set to the maintenance request destination network address of the new estimate response record, and the required time information (R008) is set to the required time. Is done.

  Next, for the estimate response from the maintenance request destination 201 received by the printer 100, the transmission source address (R009) is set to the maintenance request destination network address of the new estimate response record, and the required time information (R010) is set to the required time. To do.

  Since the estimate reply from the maintenance request destination 202 is not received within the reply waiting time of the timer 6, it is ignored. The unique code for the maintenance request is the same as the unique code for the quotation request (R011).

  As the transmission destination of the maintenance request, the maintenance request destination 201 is shorter than the time required for the estimate response, so the maintenance request destination 201 is selected (R012) and transmitted. In the above embodiment, the time required for the recovery is determined in selecting the estimated answer, but the cost required for the recovery may be included in the estimated answer, and the determination may be made by determining the cost required for the recovery.

Description of (Effect) As described above, according to the first embodiment, printer abnormality information detected by a sensor is transmitted to a plurality of maintenance request destinations stored in advance, and is necessary for recovery for each maintenance request destination. Since time information is collected and maintenance is requested to the maintenance request destination that can be recovered in the shortest time, the recovery time can be minimized.

Description of (Configuration) FIG. 14 is a block diagram of the configuration of the printer of the second embodiment.
As shown in the figure, a printer 101 as an image forming apparatus in this embodiment includes a sensor 1, a memory 2, an estimate request unit 11, a selector 4, a maintenance request transmission unit 5, a timer 6, and an interface 7. , Receiving unit 8, printing mechanism unit 9, CPU 10, destination filter 12, and internal bus 500. Only differences from the first embodiment will be described below. The same parts as those in the first embodiment are denoted by the same reference numerals as those in the first embodiment, and the description thereof is omitted.

  The destination filter 12 is a part (destination selection unit) that shares the role of selecting the transmission destination address 506 of the maintenance request transmitted from the estimation request unit 11 based on the maintenance request destination list on the memory 2 and the abnormality information. The estimate request unit 11 shares the role of a recovery information request unit that transmits to a destination address input from the outside, and is replaced with the estimate request unit 3 (FIG. 1) of the first embodiment. The estimate request unit 11 and the destination filter 12 are connected to the internal bus 500.

Further, a maintenance request list of the second embodiment different from the maintenance request list of the first embodiment (FIG. 2) is held on the memory 2. The contents will be described.
FIG. 15 is an explanatory diagram of a maintenance request destination list according to the second embodiment.
The maintenance request destination list of the second embodiment as shown in the figure is an area where the network address of the maintenance request destination PC and the error mask are stored as one record, and this record is arranged by the number of maintenance request destinations. The number of records is managed separately as a maintenance request destination. Here, the contents of the error mask will be described.

FIG. 16 is an explanatory diagram of the contents of the error mask.
As shown in the figure, the error mask is composed of a 10-bit bit string associated with the error content. When the corresponding bit is 1, it means that the maintenance request destination can resolve the corresponding error content. For example, bit 0 corresponds to error code 0x00 (no printing paper), bit 1 corresponds to error code 0x01 (no black toner), bit 2 corresponds to error code 0x02 (no yellow toner),.

Description of (Operation) FIG. 17 is a flowchart (part 1) illustrating the operation of the second embodiment.
FIG. 18 is a flowchart (part 2) illustrating the operation of the second embodiment.
This flowchart is started when the printer 100 accepts print data. Hereinafter, the operation of the printer 101 from step S101 to step S123 (including steps S141 to S147 in the middle) will be described with reference to FIG.

  Since the operation from the reception of the print data to the completion of the printing operation (step S101 to step S105) is the same as the operation of the first embodiment (step S001 to step S105), the description is omitted. Further, since the CPU 10 determines that the state is abnormal from the detection information of the sensor 1 and generates an estimation request (step S103 to step S106), the operation is the same as that of the first embodiment (step S003 to step S006), and thus description thereof is omitted. Then, the process proceeds to step S141.

Step S141
The destination filter 12 reads one record from the maintenance request destination list on the memory 2 when an estimate request is generated by the estimate request unit 11.

Step S142
The destination filter 12 compares the read maintenance request destination record with the abnormal state indicated by the detection information of the sensor 1 (see FIG. 16).

Step S143
As a result of this comparison, if the bit of the error mask corresponding to the abnormal state is not 1, the maintenance request destination in the read record is determined to be inappropriate for requesting recovery from the abnormal state, and the next record is read. Return to (Step S141). If it is determined that the error mask bit corresponding to the abnormal state is 1 and that it is suitable for requesting recovery from the abnormal state, the process proceeds to step S144.

Step S144
The destination filter 12 outputs the network address described in the read maintenance request destination record as the transmission destination address 506.

Step S145
The estimate request unit 11 sets the transmission destination address 506 as the maintenance request destination address of the previously generated estimate request, and transmits it as the estimate request 503.

Step S146
Next, it is determined whether the destination filter 12 has read all the records in the maintenance request destination list. If the last record in the maintenance request destination list has not been read, the process returns to step S141 to read the next record from the maintenance request destination list. . If all records have been read, the process proceeds to step S110.

Step S110
Since it is the value of the timer 6 and is the same as the operation of the first embodiment (step S010), the description is omitted and the process proceeds to step S111.

Step S111
Next, as in the first embodiment, the receiving unit 8 checks whether or not an estimate reply has been received. If received, the process proceeds to step S147. If not received, the process proceeds to step S113.

Here, the contents of the estimate answer will be described.
FIG. 19 is a diagram for explaining the contents of an estimate reply according to the second embodiment.
As shown in the drawing, the maintenance request destination coordinate X and the maintenance request destination coordinate Y are newly added to the estimation response as shown in the figure. The maintenance request destination coordinate X and the maintenance request destination coordinate Y indicate the physical installation location of the maintenance request destination expressed on the same basis as the request source coordinates where the printer 101 on the memory 2 is installed. Returning to the flowchart (FIG. 18).

・・・式（１）

即ち、保守依頼先座標とプリンタ１０１が設置された依頼元座標の差の絶対値からスカラーベクトル演算を行って直線距離を求め、設定された平均移動時間で除算した結果を見積もり回答の必要時間に加算する。この求めた必要時間を実施例１と同様にメモリ２上の見積もり回答の領域へ書き込む。 Step S147
When the receiving unit 8 receives the estimated answer, the CPU 10 obtains the estimated travel time by an arithmetic expression as shown in Expression (1) and adds it to the necessary time.

... Formula (1)

That is, a scalar vector calculation is performed from the absolute value of the difference between the maintenance request destination coordinates and the request source coordinates where the printer 101 is installed to obtain a straight line distance, and the result obtained by dividing by the set average moving time is set as the required time for the estimated response. to add. The obtained required time is written in the area of the estimated answer on the memory 2 in the same manner as in the first embodiment.

  Thereafter, an estimate answer is selected, a maintenance request is transmitted to the selected maintenance request destination, and the printer 101 waits until the printer 101 recovers from the abnormal state (from step S112 to step S123). Since this is the same as step S012 to step S023), the description is omitted.

Description of (Effect) As described above, according to the present embodiment, an abnormal state can be solved by providing a destination filter for selecting a transmission destination address for transmitting an estimation request to the first embodiment. It is now possible to select an appropriate request destination before sending, so only an abnormal condition that requires a maintenance request can be requested to the maintenance request destination, and the maintenance request can be kept to the minimum necessary level. The effect that you can do it. In addition, by mixing maintenance request destinations and general administrators in the maintenance request destination list and assigning a person in charge of recovery for each abnormal state using an error mask, minor abnormal states can be recovered by the general administrator. The effect is obtained. Furthermore, by adding the maintenance request destination coordinates to the estimated response, the travel time can be estimated at the required time for the estimated response, so that the determination accuracy of the time required for recovery can be improved.

Description of (Configuration) FIG. 20 is a block diagram of the configuration of the printer according to the third embodiment.
As shown in the figure, a printer 102 as an image forming apparatus in this embodiment includes a sensor 1, a memory 2, an estimate request unit 3, a selector 4, a maintenance request transmission unit 5, a timer 6, and an interface 7. , Receiving unit 8, printing mechanism unit 9, CPU 10, counter 13, and internal bus 500. Only differences from the first embodiment will be described below. The same parts as those of the first embodiment are denoted by the same reference numerals as those of the first embodiment, and the description thereof is omitted.

  The counter 13 is a counting unit that counts the number of print data received by the printer 102. Only the counter 13 is added to the configuration of the printer 102 in the first embodiment, and all other parts are the same as those of the printer 100 of the first embodiment.

Description of (Operation) FIG. 21 is a flowchart (part 1) illustrating the operation of the third embodiment.
FIG. 22 is a flowchart (part 2) illustrating the operation of the third embodiment.
This flowchart is started when the printer 102 accepts print data. Hereinafter, the operation of the printer 102 from step S201 to step S223 (including steps S261 to S272 in the middle) will be described with reference to FIG.

Step S201
First, when the receiving unit 8 receives print data, the received data 501 is written as print data in the area of the print data on the memory 2 as in the operation of the first embodiment, and is accumulated until all are received.

Step S261
Next, the counter 13 is incremented by 1 when one print data is received.

Step S202
The printing mechanism unit 9 reads the print data from the print data area of the memory 2 and starts the printing operation.

Step S203
When the printing operation is started in the printing mechanism unit 9, the CPU 10 monitors the sensor 1 and determines whether or not the apparatus indicates an abnormal state. If the detection information read from the sensor 1 does not indicate an abnormal state of the apparatus, the process proceeds to step S262, and if it indicates an abnormal state, the process proceeds to step S006.

Step S262
When the detection information of the sensor 1 is not determined to be an abnormal state, the receiving unit 8 checks whether new print data has been received. If new print data is received, the process proceeds to step S263. Then, the process proceeds to step S204.

Step S263
When receiving the estimated response, the receiving unit 8 writes the received data 501 as an estimated response in the estimated response area on the memory 2.

Step S264
The counter 13 is incremented by 1 when one print data is received.

Step S204
When the addition of the counter 13 is completed or no new print data is detected, the CPU 10 determines whether or not the printing mechanism unit 9 has completed the printing operation as in the first embodiment, and the printing operation is completed. If so, the process proceeds to step S265, and if not completed, the process returns to step S203 to repeat the determination of the detection information of the sensor 1.

Step S265
When the completion of the printing operation of the printing mechanism unit 9 is detected, the counter 13 is decremented by 1.

Step S266
It is determined by subtraction of the counter 13 whether or not the value of the counter 13 has become 0. If the counter 13 is 0, it is determined that there is no print data that has been received and is not being printed, and the process proceeds to step S205. If the counter 13 is 1 or more, it is determined that there is print data on the memory 2 that is not being printed while being received, and the process returns to the start of the printing work by the printing mechanism unit 9 (step S202).

Step S205
When the CPU 10 detects the completion of the printing operation of the printing mechanism unit 9, the present flowchart started by receiving the print data ends.

  When the CPU 10 determines that the detection information read from the sensor 1 is abnormal (step S203), the operation from the generation of the estimation request to the value of the timer (step S206 to step S210) is the same as that of the first embodiment ( Since this is the same as step S006 to step S010), the description is omitted and the process proceeds to step S211.

Step S211
Next, the receiving unit 8 checks whether or not an estimate response has been received as in the first embodiment. If it has been received, the process proceeds to step S212. If not, the process proceeds to step S213.

Step S212
The receiving unit 8 writes the received data 501 as an estimated response in the estimated response area on the memory 2. That is, when the receiving unit 8 receives the estimated response, the estimated response is set to the network address of the maintenance request destination PC, the required time for the estimated response is set to the time information necessary for the recovery, and the necessary cost for the estimated response is required for the recovery. A record set in the cost information is generated, an estimate response area is added, the number of estimate responses received is added, and the process proceeds to step S213. Here, the contents of the estimate answer will be described.

FIG. 23 is an explanatory diagram of the contents of an estimate reply according to the third embodiment.
As shown in the figure, cost information necessary for recovery is added to the estimated response in the first and second embodiments in the estimated response in the third embodiment. Details of cost information necessary for recovery will be explained.

FIG. 24 is an explanatory diagram of an estimated answer area according to the third embodiment.
The necessary cost information is defined as the maintenance cost required to recover from the abnormal state indicated by the error code transmitted in the estimate request. As shown in the figure, the estimate response area of the third embodiment is the maintenance request destination PC. The network address, time information necessary for recovery, and cost information necessary for recovery are stored as one record, and this record is arranged in the number corresponding to the number of estimated responses received. The number of records is managed separately as in the first embodiment. Cost information necessary for recovery is determined for each error code. One example will be described.

FIG. 25 is an explanatory diagram of required time and required cost for each error code.
Each maintenance request has the required time information and required cost information for each error code included in the estimate request. As shown in the figure, the required time and required cost are calculated in association with the error code included in the estimate request. It is done. Returning to the flowchart (FIGS. 21 and 22).

  The operation (steps S213 to S215) from the determination of whether or not the next timer 6 has passed the reception waiting time until there is no estimated response until the return is made to increase the reception waiting time and transmit the estimation request is the same as in the first embodiment. Since this is the same as the operation (from step S013 to step S015), the description is omitted and the process proceeds to step S267.

Step S267
When it is determined that there are one or more estimated answers on the memory 2, initialization is performed by substituting the maximum value into the minimum cost variable in the selector 4.

Step S217
Next, as in the first embodiment, the selector 4 reads one estimate response record from the estimate response area on the memory 2.

Step S268
Next, it is determined whether or not the value of the counter 13 is equal to or greater than the threshold value. If the value is equal to or greater than the threshold value, the process proceeds to step S271. If the value is less than the threshold value, the process proceeds to step S269.

Step S271
The selector 4 compares whether or not the required time of the read estimate response record is shorter than the minimum cost variable. If it is smaller, the process proceeds to step S272. Otherwise, the process proceeds to step S221.

Step S272
The required time of the read estimate response record is set in the minimum cost variable, and the process proceeds to step S220.

Step S220
The network address of the maintenance request destination PC of the estimate response record is set in the request destination address 504 as in the case where the required times are compared.

Step S269
Since the value of the counter 13 is less than the threshold value, the selector 4 compares whether or not the required cost of the read estimate response record is smaller than the minimum cost variable. If it is smaller than the minimum cost variable, the process proceeds to step S270. Advances to step S221.

Step S221
It is determined whether or not all estimated response records on the memory 2 have been compared. If all estimated values have been determined, the process proceeds to step S222. If there is an estimated response record that has not been compared yet, the estimated response record is read. Repeat from.

  Thereafter, the operation of transmitting a maintenance request and determining whether or not the printer 102 has recovered from the abnormal state (step S222 to step S223) is the same as the operation of the first embodiment (step S022 to step S023). Is omitted.

Description of (Effects) As described above, according to the third embodiment, compared to the first embodiment, a counter that counts the number of received print data that has not been completed, and a printer error in the estimated response. Since the cost required for recovery from the state is set, the time required for recovery is compared if the number of counters exceeds the threshold, and the cost required for recovery is compared if the number of counters is less than the threshold. If it is used frequently, it is possible to recover quickly, otherwise it is possible to recover more cheaply.

  In the embodiment, a printer is used as the image forming apparatus. In the embodiment, the estimate request is transmitted to the registered transmission destination, but it may be replaced with the print data transmission source in the print history or the print data transmission source waiting for the printing work.

1 is a block diagram of a configuration of a printer according to Embodiment 1. FIG. FIG. 6 is an explanatory diagram of a maintenance request destination list according to the first embodiment. 1 is a system configuration diagram of a printing system to which the present invention is applied. 3 is a flowchart showing the operation of the first embodiment. It is a content explanatory view of an estimate request. It is content explanatory drawing of an identification code. FIG. 6 is an explanatory diagram of contents of an error code according to the first embodiment. It is a content explanatory view of an estimate reply. It is explanatory drawing of the estimate reply area | region of Example 1. FIG. It is content explanatory drawing of a maintenance request. FIG. 3 is a time-series change explanatory diagram of the printing system according to the first exemplary embodiment. It is content explanatory drawing of the required time information for every error code. FIG. 6 is an explanatory diagram of a notification flow according to the first embodiment. FIG. 6 is a block diagram of a configuration of a printer according to a second embodiment. It is explanatory drawing of the maintenance request destination list | wrist of Example 2. FIG. It is content explanatory drawing of an error mask. 6 is a flowchart (part 1) illustrating an operation of the second embodiment. 10 is a flowchart (part 2) illustrating the operation of the second embodiment. FIG. 10 is an explanatory diagram of content of an estimate reply according to a second embodiment. FIG. 10 is a block diagram of a configuration of a printer according to a third embodiment. 12 is a flowchart (part 1) illustrating an operation of the third embodiment. 10 is a flowchart (part 2) illustrating the operation of the third embodiment. FIG. 10 is an explanatory diagram of a content of an estimate reply according to a third embodiment. It is explanatory drawing of the estimate reply area | region of Example 3. FIG. It is explanatory drawing of the required time and required cost for every error code.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Sensor 2 Memory 3 Estimation request part 4 Selector 5 Maintenance request transmission part 6 Timer 7 Interface 8 Reception part 9 Printing mechanism part 10 CPU
100 Printer 300 Network 500 Internal bus 501 Received data 502 Status 503 Estimate request 504 Request destination address 505 Maintenance request

Claims (6)

In an image forming apparatus connected to a network and forming an image based on input image information,
A detection unit for detecting an apparatus state of the image forming apparatus;
A storage unit for storing a plurality of transmission destinations connected to the network;
When the detection unit detects an abnormality in the device state, the abnormality information indicating the abnormality in the device state is transmitted to the plurality of transmission destinations stored in the storage unit, and the recovery information is returned for recovery of the abnormality. A recovery information requesting unit that requests
A selection unit that selects one of the plurality of recovery information received by the recovery information request unit;
An image forming apparatus comprising: a maintenance request information output unit configured to output maintenance request information to recover an abnormality in the apparatus state with respect to a recovery information return source selected by the selection unit. When the detection unit detects an abnormality in the device state, the device further comprises a destination selection unit that selects at least one transmission destination corresponding to the content of the device state from a plurality of transmission destinations stored in the storage unit,
The recovery information request unit transmits abnormality information indicating abnormality of the device state to the transmission destination selected by the destination selection unit, and requests a return of recovery information aiming at recovery of the abnormality. The image forming apparatus according to claim 1.   The image forming apparatus according to claim 1, wherein the recovery information includes at least one of time information required to recover from the apparatus state and cost information required to recover. . A counting unit that counts the number of the image information to be held waiting for image formation of the image forming apparatus;
A switching unit that outputs at least one of the time information and the cost information as a reference for comparison according to the number of suspensions of the counting unit,
The image forming apparatus according to claim 3, wherein the selection unit performs selection according to an output of the switching unit. A timing unit for measuring a response period from transmission of abnormality information to reception of the recovery information by the recovery information request unit;
The image forming apparatus according to claim 1, wherein the selection unit performs selection based on the response period of the timing unit. The recovery information includes installation location information of a recovery information request destination connected to the network,
A position storage unit that stores installation location information of the image forming apparatus;
The image forming apparatus according to claim 1, wherein the selection unit performs selection based on the installation location information and the installation location information of the coordinate storage unit.

Images