Printing device

JP7639393B2Active Publication Date: 2025-03-05BROTHER KOGYO KK
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
JP2021028170
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2021-02-25
Publication Date
2025-03-05
Estimated Expiration
2041-02-25

AI Technical Summary

Benefits of technology

【0008】 本発明によれば、印刷装置において、ユーザクリーニングを適正に実行させることで、記録剤の不要な消費を低減することができる。

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007639393000001
    Figure 0007639393000001
  • Figure 0007639393000002
    Figure 0007639393000002
  • Figure 0007639393000003
    Figure 0007639393000003
Patent Text Reader

Abstract

To properly execute user cleaning.SOLUTION: A firm ware 40 of a printer 30 can execute printing until printing permission amount reaches a predetermined first threshold value. The firm ware 40, when receiving an instruction operation of user cleaning for cleaning a print head 38, if the printing permission amount does not reach a second threshold value, executes the user cleaning, and if the printing permission amount reaches the second threshold value, restricts the execution of the user cleaning.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a technique for cleaning a print head provided in a printing device. [Background technology]

[0002] Printing devices are known that can clean the print head by ejecting a recording agent from the print head. Patent Document 1 describes a printing device that ejects ink from the print head upon receiving a cleaning instruction from a user, thereby starting so-called user cleaning. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2013-163301 A Summary of the Invention [Problem to be solved by the invention]

[0004] Incidentally, there is known a printing device capable of printing within a range permitted by a print permission amount. The print permission amount is an amount different from the recording agent capacity, and is, for example, information related to the recording agent or sheets used by the printing device when the printing device executes printing. In such a configuration, for example, when the print permission amount is a value that does not allow printing to be executed, if user cleaning is executed, there is a concern that the recording agent consumed by the user cleaning will be wasted. In addition to this, there is a concern that the remaining amount of recording agent will be insufficient for the print pages that can be printed by the print permission amount due to execution of user cleaning.

[0005] The present invention has been made in consideration of the above-mentioned problems, and has an object to properly execute user cleaning. [Means for solving the problem]

[0006] In order to solve the above problems, the present invention relates to a printing device that includes a storage unit that stores a recording agent, a print head that can eject the recording agent, and a controller. The printing device can perform printing until a printable amount different from the remaining amount of recording agent reaches a predetermined first threshold, and the printable amount is information related to the amount of recording agent or sheet used in the printing device when printing, and the controller performs an instruction receiving process that receives an instruction to perform user cleaning that cleans the print head by discharging the recording agent from the print head, and a restriction process that, when the instruction to perform user cleaning is received, causes user cleaning to be performed if the printable amount has not reached the second threshold, and restricts the execution of user cleaning if the printable amount has reached the second threshold.

[0007] In the above configuration, when an instruction to perform user cleaning is received, if the printable amount does not reach the second threshold, user cleaning of the printing device is performed, and if the printable amount reaches the second threshold, execution of user cleaning of the printing device is restricted. Here, the printable amount reaching the second threshold includes a case where the printable amount decreases with printing by the printing device and falls below the second threshold, as well as a case where the printable amount increases with printing and exceeds the second threshold. As a result, when the printable amount is a value that is predicted to limit the number of printed sheets, execution of the user cleaning process is restricted even if an execution instruction from the user is received. As a result, user cleaning can be performed appropriately, and unnecessary consumption of recording agent can be reduced. Effect of the Invention

[0008] According to the present invention, by appropriately executing user cleaning in a printing device, unnecessary consumption of recording agent can be reduced. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram showing the configuration of a printing system. [Diagram 2]FIG. 4 is a diagram for explaining a management table. [Diagram 3] FIG. [Figure 4] FIG. 13 is a diagram illustrating a quantity selection screen. [Diagram 5] 11 is a timing chart illustrating a process for purchasing a charge amount. [Figure 6] FIG. 13 is a diagram illustrating a screen displayed after purchasing a charge amount. [Figure 7] 10 is a flowchart showing the procedure of a process that is executed when an instruction to perform user cleaning is accepted. [Figure 8] 10 is a flowchart showing the procedure of a process that is executed when an instruction to perform user cleaning is accepted in a second embodiment. [Figure 9] 10 is a flowchart showing the procedure of a process that is executed when an instruction to perform user cleaning is accepted. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] (First embodiment) A printing system according to the present embodiment will be described with reference to the drawings.

[0011] The printing system 100 shown in FIG. 1 includes a terminal 10, a printer 30, and a server 50. The terminal 10, the printer 30, and the server 50 are connected to a network 200. In this embodiment, the network 200 may be the Internet, a local area network (LAN), or a combination of a LAN and the Internet. The network 200 may be wired, wireless, or a combination of wired and wireless. In this embodiment, the terminal 10 is an example of an information processing device.

[0012] The terminal 10 is a smartphone or a tablet terminal. The terminal 10 includes a bus 11, a terminal-side CPU 12, a memory 13, a user IF 17, and a communication IF 20. These components are connected to each other via the bus 11 so as to be able to communicate with each other. IF is an abbreviation for Interface.

[0013] The user IF 17 includes operation keys 18 and a touch panel 19. The touch panel 19 has a touch sensor and outputs a signal according to the detection result by the touch sensor. In this embodiment, "touch" includes the general operation of bringing an input medium into contact with the display screen of the touch panel 19. In addition, the above-mentioned concept of "touch" may include bringing the input medium close to a position where the distance between the input medium and the touch panel 19 is very small. Furthermore, the input medium may be a user's finger, a touch pen, or the like.

[0014] The communication IF 20 connects the terminal 10 to the network 200 in accordance with a predetermined communication protocol. The communication IF 20 is capable of performing wireless communication of the Wi-Fi® (registered trademark) system based on the IEEE 802.11 standard and standards equivalent thereto. The communication IF 20 may also perform short-distance wireless communication with the printer 30 using Bluetooth (registered trademark) or the like. The communication IF 20 may also perform wireless communication using a mobile communication system via a base station.

[0015] The memory 13 stores a user ID, a device ID, an OS (abbreviation for Operating System), and an application program 14. The user ID and the device ID are information for identifying a user and a device when receiving a print service from the server 50, and will be described in detail later. The terminal side CPU 12 can receive a print service from the server 50 by executing the application program 14 under the execution of the OS. The print service will be described later. In the following, the application program is also simply described as an "application." In addition, the CPU that executes the program may also be simply described as the program name. For example, the description "application 14" may mean "terminal side CPU 12 that executes application 14." In addition, the memory 13 stores a user ID. The user ID is information for uniquely identifying the terminal 10.

[0016] In this embodiment, the processing of the CPU according to the instructions written in the program is mainly shown. That is, the processing of "judgment", "extraction", "selection", "calculation", "decision", "identification", "acquisition", "acceptance", "control" and the like in the following description represents the processing of the CPU and the controller. The processing by the CPU also includes hardware control via the OS 20. Note that "acquisition" is used as a concept that does not require a request. That is, the processing of receiving data without a request from each program is also included in the concept of "CPU acquiring data". In addition, "data" in this specification is expressed in a computer-readable format. And data with the same substantial meaning but different formats are treated as the same data. The same applies to "information" in this specification.

[0017] Next, a description will be given of the printer 30. The printer 30 includes a bus 31, a communication IF 32, a printing unit 33, a user IF 34, a controller 35, a memory 36, and an ink tank 37. The components constituting the printer 30 are connected via the bus 31 so as to be able to communicate with each other.

[0018] The communication IF 32 is similar to the communication IF 20 in the terminal 10. The user IF 34 is similar to the user IF 17 in the terminal 10, and includes a touch panel and operation keys as physical keys.

[0019] The printing unit 33 executes a printing operation to print an image on a recording medium such as a sheet or a disk. The printing unit 33 is an inkjet type unit that ejects ink as a recording medium onto the recording medium. An ink tank 37 that stores ink is connected to the printing unit 33. In this embodiment, there are four types of ink (cyan, magenta, yellow, and black), and a plurality of ink tanks 37 are provided for each type of ink. When the ink in the ink tank 37 runs short, a replacement application is made to the vendor to replace the printer 30. In this embodiment, the ink tank 37 is configured not to be refilled with ink. Furthermore, the ink tank 37 is fixed to the printer 30 and cannot be attached or detached.

[0020] The controller 35 is configured with a CPU, an ASIC (abbreviation of Application Specific Integrated Circuit), etc., and controls the operations of the print unit 33 and the user IF 34. The memory 36 stores various programs and data. The memory 36 may be configured, for example, by combining RAM, ROM, and flash memory. The memory 36 may also include a storage medium readable by the controller 35, which is a computer. The storage medium also includes recording media such as CD-ROM and DVD-ROM.

[0021] The memory 36 stores firmware 40. The controller 35 executes the firmware 40, which is a control program, to execute print processing. The memory 36 stores information used in the print service. Specifically, a "device ID" and a "printable number of sheets" are stored. The device ID is the same as the device ID stored in the memory 13 of the terminal 10. The printable number of sheets will be described later.

[0022] Furthermore, the memory 36 stores history information 43. The history information is information that records the printing mode in the printing process that the printer executed in the past. Specifically, the history information 43 stores the printing date and time, the print settings, and the print pages per job as the printing mode. The print settings include "print quality", "paper size", and "color setting". "Print quality" is information that indicates the quality of the image formed on the sheet, and for example, the quality increases in the order of "high speed", "normal", "high quality", and "highest quality". On the other hand, the amount of ink applied also increases in the order of "high speed", "normal", "high quality", and "highest quality". "Paper size" is information that sets the size of the sheet used for printing. There are combinations of "print quality" and "paper size", and the selectable "print quality" is limited depending on the selected "paper size".

[0023] Next, the configuration of the server 50 will be described. The server 50 includes a bus 51, a communication IF 52, a server-side CPU 53, and a memory 54. The components constituting the server 50 are connected to each other so as to be able to communicate with each other via the bus 51. The server 50 is capable of providing various services to the terminal 10. In this embodiment, the server 50 can provide a printing service to a user who operates the terminal 10.

[0024] A user applies for a printing service to a vendor by operating the terminal 10. When the vendor receives the application from the user, the vendor sends the printer 30 to the user. The printer 30 sent from the vendor to the user is filled with an amount of ink necessary to print more than the predetermined printable number (for example, 2000 sheets + α sheets) granted to the user. The printable number indicates the number of sheets of paper that can be printed by the printer 30, and is information indicating a value different from the amount of ink contained in the ink tank 37. Specifically, when receiving a printing service from the server 50, the terminal 10 obtains the current printable number from the server 50. The terminal 10 can cause the printer 30 to execute printing until the printable number reaches a first threshold TH1. In this embodiment, the first threshold TH1 is "0". Therefore, in this printing service, the user does not need to take the trouble of filling the printer 30 with ink or replacing the ink cartridges after obtaining the printer 30 and before printing the printable number granted by paying the initial fee. Furthermore, if the user wishes to print more than the predetermined number of printable sheets granted by paying the initial fee, the user can purchase additional sheets and increase the number of printable sheets by making a charge to the server 50. Hereinafter, the additional number of sheets purchased will be referred to as the charge number. Thereafter, if the amount of ink remaining in the printer 30 becomes low, the user applies to the server 50 for a replacement of the printer 30. This allows the user to continue the printing service using a new printer 30 sent by the vendor. In this embodiment, the number of printable sheets is an example of the permitted printing amount.

[0025] A management table KT is stored in the memory 54 of the server 50. As shown in FIG. 2, the management table KT is a table that stores information required to use the print service. The management table KT includes a user management table KT1 and a device management table KT2. The user management table KT1 is a table that stores information about users who use the print service. The user management table KT1 stores a user ID, a password, and the number of printable sheets in association with each other. The password is used when the user uses the application 14, and is registered in the server 50 when the printer 30 is initially set up.

[0026] The device management table KT2 is a table that stores information about devices, and stores a device ID, remaining ink amount, replacement application information, activation information, device replacement information, and device settings in association with each other.

[0027] The remaining ink level indicates the amount of ink remaining in the printer 30, and is transmitted from the printer 30 at a specified timing. The exchange application information is information indicating whether or not an exchange application for the printer 30 has been made to the server 50. When the exchange application information is set to the on state "◯", it indicates that an exchange application for the printer 30 has already been made, and when it is set to the off state "×", it indicates that an exchange application for the printer 30 has not yet been made.

[0028] The activation information is information indicating whether or not the initial settings of the printer 30 have been completed for the server 50. When the activation information is set to an on state "◯", printing by the printer 30 is permitted, and when the activation information is set to an off state "×", printing by the printer 30 is restricted.

[0029] The device replacement information is information indicating whether the printer 30 has already been replaced in response to a replacement application. When the device replacement information is set to an on state "◯", it indicates that the printer has already been replaced, and when the device replacement information is set to an off state "×", it indicates that the printer has not yet been replaced. The device settings indicate the functions of the printer 30 (copy, scan, etc.) and the settings of each function (paper size, color, magnification, etc.).

[0030] Next, a printing service using the printing system 100 will be described. When a user executes printing using the printing service, the user starts the application 14 to display a top screen 70 shown in FIG. 3 on the touch panel 19 of the terminal 10. The top screen 70 includes a print icon 71, a charge icon 72, and a main body setting icon 73. The print icon 71 is an icon that accepts an operation by the user when printing is executed by the printer 30 in the printing service. The charge icon 72 is an icon that accepts an operation by the user when purchasing a charge amount from the server 50. The main body setting icon 73 is an icon that accepts an operation by the user when changing various setting information for the printer 30.

[0031] When the application 14 detects that the print icon 71 has been operated on the top screen 70, it displays a print execution screen (not shown) on the touch panel 19. The application 14 can then accept input operations for print pages and print settings on the print execution screen. When the application 14 detects that a print instruction operation has been performed on the print execution screen, it transmits a print file to the printer 30 and starts printing. Specifically, the application 14 can perform printing with the printable number stored in the user management table KT1 as the upper limit. That is, the printable number is subtracted according to the number of sheets printed by the printer 30 in response to an instruction from the terminal 10.

[0032] Furthermore, when the application 14 detects that the charge icon 72 has been operated on the top screen 70, it displays a number selection screen 80 shown in Fig. 4. The number selection screen 80 is a screen that accepts a user's operation to select the number of charges, and will be described in detail later.

[0033] Next, a description will be given of the process executed by each device when purchasing a recharge amount from the server 50. The application 14 starts the process shown in FIG. 5 when the recharge icon 72 is operated on the top screen 70.

[0034] In step 10 (hereinafter, referred to as S10), the application 14 requests activation information from the server 50 along with the device ID stored in the memory 14. Alternatively, the application 14 may transmit to the server 50 a token capable of identifying the user ID of the terminal 10 that is the transmission source along with the request for activation information.

[0035] When the server-side CPU 53 of the server 50 receives a request for activation information from the terminal 10, it returns the activation information associated with the device ID transmitted from the terminal 10 on the management table KT in S11.

[0036] When the application 14 receives the activation information sent from the server 50, it determines in S12 whether activation has been completed for the printer 30 (i.e., whether printing is permitted for the printer 30). As described above, when the activation information is "◯", printing is permitted for the printer 30 specified by the device ID associated with the user ID. On the other hand, when the activation information is "×", printing is not permitted for the printer 30. When the application 14 makes a negative determination in S12, it ends the processing in FIG. 5. On the other hand, when the application 14 makes a positive determination in S12, it proceeds to S13.

[0037] In S13, the application 14 executes a charge process. In this charge process, the charge quantity to be purchased from the server 50 is set in response to an operation by the user. Specifically, in the charge process executed in S13, a quantity selection screen 80 shown in FIG. 4 is displayed on the touch panel 19.

[0038] The number selection screen 80 includes selection icons 81, 82, and 83 that accept selection operations for each of the predetermined recharge numbers (50, 500, and 2000). The user completes the selection of the recharge number by operating any of the selection icons 81, 82, and 83 and then operating the confirmation icon 84. In this embodiment, each selection icon 81, 82, and 83 displays the recharge number, as well as the charge fee for purchasing the recharge number and the amount per one.

[0039] When the application 14 accepts the user's selection of the charge quantity in the charge process of S13, the process proceeds to S14. In S14, a charge invoice including a charge fee corresponding to the charge quantity selected in S13 is sent to the server 50. The charge invoice is information requesting the server 50 to purchase the charge quantity. When the server 50 receives the charge invoice from the terminal 10, in S15 the server 50 sends a charge instruction to the terminal 10 indicating the charge quantity corresponding to the charge fee included in the charge invoice. The charge instruction is an instruction to add the charge quantity to the number of printable sheets.

[0040] In S16, the application 14 of the terminal 10 transfers the charge instruction sent from the server 50 to the printer 30. When the firmware 40 of the printer 30 receives the charge instruction, in S17, the firmware 40 adds the charge number to the printable number, thereby updating the printable number.

[0041] In S18, the firmware 40 transmits a completion notification to the terminal 10. In S19, the application 14 of the terminal 10 transfers the completion notification from the printer 30 to the server 50. Upon receiving the completion notification, the server 50 updates the printable number by increasing the printable number stored in the management table KT by the charge number in S20. In S21, the server-side CPU 53 transmits an update completion notification to the terminal 10. FIG. 6 shows a screen 90 that is displayed on the touch panel 19 after the application 14 receives the completion notification. The screen 90 shown in FIG. 6 includes a display image 91 that indicates the printable number updated by purchasing the charge number.

[0042] Next, the process executed when an instruction to execute user cleaning is received from the printer 30 will be described with reference to FIG. 7. User cleaning is a process for cleaning the print head 38 triggered by receiving an instruction operation from the user. Cleaning includes the execution of an operation to discharge ink from the print head and the execution of a wiping operation on the print head. Note that a "wiping operation" is an operation in which ink remaining on the nozzle surface of the print head is wiped away with a wiper. The process shown in FIG. 7 is executed when the user issues an instruction operation to execute user cleaning when the printer 30 is not receiving a print job, and is mainly executed by the firmware 40.

[0043] In S30, it is determined whether or not an instruction to perform user cleaning has been accepted. For example, by operating the main body setting icon 73 on the top screen 70, a screen capable of accepting an instruction operation for user cleaning is displayed, and when the application 14 detects an instruction operation for user cleaning on this screen, it transmits an instruction to perform user cleaning to the printer 30. In addition, when an instruction operation for user cleaning is accepted via the user IF 34 of the printer 30, a positive judgment may be made in S30. When a negative judgment is made in S30, the process waits. In this embodiment, the process executed by the firmware 40 in S30 is an example of an instruction acceptance process.

[0044] If an affirmative decision is made in S30, the process proceeds to S31. In S31, it is determined whether the printable number of sheets is greater than a second threshold value TH2. Specifically, the printable number of sheets is stored in the memory 36 of the printer 30, and the stored printable number of sheets is compared with the second threshold value TH2. In this embodiment, the second threshold value TH2 is set to "0", the same as the first threshold value TH1. That is, in S30, it is determined whether the printable number of sheets is greater than 0.

[0045] If S31 is judged as positive, the process proceeds to S34 and executes user cleaning. On the other hand, if S31 is judged as negative, the process proceeds to S32 and judges whether or not the purchase site where the charge amount can be purchased has been accessed. This is because if the purchase site has been accessed, the user is highly likely to subsequently purchase the charge amount from the server 50. In other words, if S32 is judged as positive, the number of printable sheets is highly likely to reach the second threshold value TH2 as a result of the subsequent purchase of the charge amount. Specifically, the process queries the terminal 10 as to whether or not the purchase site has been accessed, and judges S32 depending on the query result.

[0046] If an affirmative decision is made in S32, the process proceeds to S34, where user cleaning is executed, whereas if a negative decision is made in S32, the process proceeds to S33.

[0047] In S33, it is determined whether the start condition for regular cleaning is satisfied. Regular cleaning is a process of discharging ink from the print head 38 to clean the print head 38 or a process of performing a wiping operation on the print head when a predetermined time is reached or when a predetermined time has elapsed since the printer 30 was turned on. If a negative judgment is made in S33, the process returns to S31. In this case, user cleaning is suspended until the condition in S31 or S32 is satisfied. For example, if a charge instruction is received from the terminal 10 after a negative judgment is made in S33 (FIG. 5, S16), the number of printable sheets may increase by the number of charged sheets, and the number of printable sheets may become greater than the second threshold value TH2. In this case, an affirmative judgment is made in S31, and user cleaning is performed.

[0048] On the other hand, if the conditions for starting regular cleaning are met and an affirmative judgment is made in S33, the process proceeds to S35, where regular cleaning is executed. Then, in S36, execution of user cleaning that is currently on hold is canceled. This is because the print head 38 has been cleaned by regular cleaning, and so there is no need to execute user cleaning. Once the process of S36 has been executed, the process of FIG. 7 ends. In this embodiment, the processes of S31 to S36 executed by the firmware 40 are an example of restriction processing.

[0049] The above-described embodiment provides the following advantages. When the firmware 40 of the printer 30 receives an instruction to perform user cleaning, if the number of printable sheets is greater than the second threshold TH2, the firmware 40 executes user cleaning, and if the number of printable sheets is equal to or less than the second threshold TH2, the firmware 40 restricts the execution of user cleaning. This restricts the execution of cleaning even when an instruction to perform cleaning is received from a user when the number of printable sheets is a value that is predicted to limit the number of print pages. As a result, by appropriately executing user cleaning, unnecessary consumption of ink can be suppressed.

[0050] The firmware 40 can accept an increase in the number of printable sheets, and if the number of printable sheets is equal to or less than the second threshold TH2, it suspends execution of user cleaning, and then, if a charge is purchased and the number of printable sheets becomes greater than the second threshold TH2, it executes user cleaning. This allows user cleaning to be executed as much as possible when user cleaning is necessary.

[0051] When regular cleaning is to be performed while execution of user cleaning is on hold, the firmware 40 cancels the execution of the on-hold user cleaning. This makes it possible to prevent unnecessary consumption of ink by performing both regular cleaning and user cleaning at the same time.

[0052] The second threshold value TH2 is the same value as the first threshold value TH1. As a result, in situations where printing cannot be performed due to the printable number of sheets, user cleaning is restricted, making it possible to suppress unnecessary ink consumption.

[0053] In the above-described first embodiment, the second threshold value TH2 is set to 0. Alternatively, the second threshold value TH2 may be set to a value other than 0.

[0054] Second embodiment In the second embodiment, the configuration different from the first embodiment will be mainly described. In the second embodiment, the same components as those in the first embodiment are denoted by the same reference numerals, and the description thereof will not be repeated.

[0055] In the first embodiment described above, the second threshold value TH2 is a fixed value (0). Instead, in this embodiment, the second threshold value TH2 is a variable value that varies depending on the usage status of the printer 30 by the user.

[0056] 8 and 9, a process executed when the printer 30 receives a user cleaning instruction in this embodiment will be described. The firmware 40 mainly executes the process shown in FIGS.

[0057] In S30, it is determined whether an instruction to perform user cleaning has been received. If an affirmative decision is made in S30, the process proceeds to S40, where it is determined whether the printer 30 is in a malfunctioning state. If it is determined that the printer 30 is in a malfunctioning state, an affirmative decision is made in S40, the process proceeds to S41, and the user cleaning is canceled. In S40, the decision as to whether the printer 30 is in a malfunctioning state is based on the decision result in S48, which will be described later. Once the process of S41 has been executed, the process of FIG. 8 ends. This is because the printer 30 is in a malfunctioning state, and user cleaning is not executed.

[0058] If a negative judgment is made in S40, the process proceeds to S31, where it is judged whether or not the printable number of sheets is greater than the second threshold value TH2. In this embodiment, the second threshold value TH2 is a variable value depending on the usage status of the printer 30 by the user. Specifically, the firmware 40 calculates the average number of print pages per job stored in the history information 43, and sets the calculated average value as the second threshold value TH2. Therefore, the second threshold value TH2 is a value of 1 or more.

[0059] If S31 is judged as positive, the process proceeds to S42, where it is determined whether a predetermined time has elapsed since the start time of the abnormality judgment period, which will be described later. In this embodiment, the firmware 40 judges whether the print head 38 is in an abnormal state according to the number of times user cleaning has been performed during the abnormality judgment period, which is the predetermined time (S42 to S48, which will be described later). In other words, it determines whether the print head 38 is in an abnormal state based on the frequency with which user cleaning has been performed.

[0060] If the start time has not been set or if a predetermined time has passed since the start time, an affirmative judgment is made in S42, and the process proceeds to S43. In S43, the counter value is reset. The counter is a value that measures the number of times user cleaning has been performed during the abnormality judgment period, and its initial value is 0. In S44, the start time of the abnormality judgment period is stored. In S45, user cleaning is performed.

[0061] In S46, the counter is incremented by adding 1. In S47, it is determined whether the counter value is greater than an abnormality determination value TH3. The abnormality determination value TH3 is a value determined according to the expected number of times user cleaning is performed within the abnormality determination period when the print head 38 has broken down due to clogging or the like. If a negative determination is made in S47, the processing in FIG. 8 is terminated.

[0062] On the other hand, if the counter value is greater than the abnormality determination value TH3 and an affirmative decision is made in S47, the process proceeds to S48, in which it is determined that a malfunction has occurred in the printer 30 and the malfunction is notified on the display screen of the touch panel 19. Then, the process in FIG. 8 ends.

[0063] On the other hand, if the determination in S31 is negative, the process proceeds to S32, where it is determined whether or not the purchase site has been accessed. If the determination in S32 is negative, the process proceeds to S34, where it is determined whether or not the conditions for starting regular cleaning are met.

[0064] If a negative decision is made in S34, the process proceeds to S49. If the process of S36 is completed, the process of FIG. 8 is completed. In S49, it is determined whether or not a print job has been received from the terminal 10. If a negative decision is made in S49, the process returns to S40. On the other hand, if a positive decision is made in S49, the process proceeds to S51 (FIG. 9).

[0065] In S51, it is determined whether the number of print pages specified in one print job is greater than the current printable number. In other words, it is determined whether the current printable number makes it impossible to complete printing of all pages specified by the print job. If a negative determination is made in S51, the process proceeds to S52, where the pending user cleaning is executed. This is to execute the user cleaning to eliminate the ejection failure of the print head 38 before printing all pages. On the other hand, if a positive determination is made in S51, the process proceeds to S54. In S54, the execution of the currently received print job is canceled. When the process of S54 is completed, the process returns to S40 in FIG. 8. In this case, the user cleaning is continued to be held on hold. In this embodiment, the process of S54 executed by the firmware 40 is an example of a restriction process.

[0066] After S52, in S53, all printing included in the print job is executed, and the processing in Figs. 8 and 9 is then terminated.

[0067] The present embodiment described above can provide the following advantages. When the number of printable sheets has reached the second threshold value TH2, the firmware 40 executes user cleaning when a print job is received that specifies a print page that can be completed with the current number of printable sheets. On the other hand, the firmware 40 does not execute user cleaning when a print job is received that specifies a print page that cannot be completed with the current number of printable sheets. In this way, by restricting user cleaning for print jobs that specify print pages that cannot be completed with the current number of printable sheets, it is possible to maximize the number of sheets that can be completed. On the other hand, by not restricting cleaning for print jobs that specify print pages that can be completed with the current number of printable sheets, printing can be performed according to the user's intention.

[0068] The firmware 40 calculates the average number of pages printed per job based on the history information 43, and sets the calculated average number of pages printed as the second threshold value TH2. This makes it possible to predict a situation in which the number of pages printed will be restricted, based on the user's past usage.

[0069] In situations where user cleaning is performed frequently, there is a high possibility that the print head is broken, such as clogged. Therefore, the firmware 40 judges whether or not the print head 38 is in an abnormal state based on the frequency of user cleaning. As a result, if it is determined that the print head is in an abnormal state, a notification is issued, and the user can be prompted to stop printing or replace the printing device.

[0070] (Other embodiments) The technology disclosed in this specification is not limited to the above-described embodiments, and can be modified in various forms without departing from the spirit of the invention. For example, the following modifications are also possible. In the above-described embodiments, the printing system 100 uses the number of printable sheets as the permitted printing amount. Alternatively, the printing service may use the amount of ink available, the number of ink shots, or even the usable sheet length as the permitted printing amount. In this case, in the second embodiment, the average value of the amount of ink used per job, the number of ink shots, or the sheet length stored in the history information 43 may be calculated, and the calculated average value may be set as the second threshold value TH2.

[0071] In each of the above-described embodiments, the printable number of sheets is stored in the memory 36 of the printer 30. Alternatively, the printable number may not be stored in the memory 36 of the printer 30, and may be stored in the memory 13 of the terminal 10. In this case, the firmware 40 may obtain the printable number by requesting the current printable number from the terminal 10 in S31.

[0072] 5, if the application 14 stores information about whether the printer 30 has been activated, the application 14 may request activation information from the printer 30 in S10. In this case, the firmware 40 returns the activation information to the application 14 in S11.

[0073] 2, the printable number of sheets is associated with each user ID, but instead, the printable number of sheets may be associated with each printer 30. In this case, each item associated with the user management table KT1 is associated with a device ID in the device management table KT2.

[0074] In the above-described embodiment, the printer 30 is provided with an ink tank 37 that cannot be refilled with ink or replaced. Instead, the printer 30 may be provided with an ink cartridge that can be refilled with ink or replaced. In this case, the ink cartridge replacement can be requested from the vendor in the replacement application. The printing unit 33 provided in the printer 30 may be an electrophotographic unit that forms a toner image on a photoreceptor and transfers the formed toner image to a recording medium. In this case, a toner cartridge that stores toner is connected to the printing unit instead of the ink tank 38. [Explanation of symbols]

[0075] 10... terminal, 12... terminal side CPU, 14... application program, 17... user IF, 30... printer, 50... server

Claims

1. A printing device including a container for containing a recording material, a print head capable of ejecting the recording material, and a controller, the printing device is capable of printing until a printable amount, which is different from a remaining amount of recording agent, reaches a predetermined first threshold, and the printable amount is information regarding an amount of recording agent or a sheet used by the printing device during printing; The controller: an instruction receiving process for receiving an instruction to perform user cleaning to clean the print head by discharging the recording agent from the print head; a restriction process for performing the user cleaning when the instruction to perform the user cleaning is received and, if the print allowance amount has not reached a second threshold, performing the user cleaning, and, if the print allowance amount has reached the second threshold, restricting the execution of the user cleaning; A printing device that runs

2. An addition to the permitted printing amount is acceptable; A printing device as described in claim 1, wherein, in the restriction process, if the print allowable amount has reached the second threshold, execution of the user cleaning is put on hold, and then, by accepting an addition to the print allowable amount, if the print allowable amount after the addition has not reached the second threshold, the user cleaning is executed.

3. the controller is capable of executing regular cleaning, the regular cleaning being a process of discharging recording agent from the print head in order to clean the print head when a predetermined time is reached or when a predetermined period of time has elapsed; The printing device according to claim 2 , wherein, in the restriction process, if the regular cleaning is to be executed while the execution of the user cleaning is on hold, the execution of the user cleaning on hold is cancelled.

4. In the limiting process, when the print permission amount has reached the second threshold value, performing the user cleaning when a print job is received that indicates a print page that can be completed using the current print allowance amount; 4. The printing device according to claim 1, wherein the user cleaning is not executed when a print job is received that specifies a print page that cannot be printed completely based on the current permitted print amount.

5. The controller: When printing is performed, the number of printed pages per job is stored in memory as history information; A printing device according to any one of claims 1 to 4, wherein the restriction process calculates an average number of printed pages per job based on the history information, and sets the calculated average number of printed pages to the second threshold value.

6. The controller determines whether or not the print head is in an abnormal state based on the frequency of execution of the user cleaning, 6. The printing device according to claim 1, wherein when it is determined that the print head is in an abnormal state, a notification is given.

7. 7. The printing device according to claim 1, wherein the second threshold value is the same as the first threshold value.

Citation Information

Patent Citations

  • Recording material running-out method, recording material running-out alarm device and recording medium

    JP1999005300A

  • Print management device, print management method and print management program

    JP2012020492A

  • Inkjet printer and method for controlling inkjet printer

    JP2013163301A

  • Image recording device

    JP2018114725A

  • Controlling operation of a printer based on detection of an optical marker in a pigment ink

    US20170057267A1