Printing device and printing system

Abstract

To provide a technique that can prevent the other person from cancelling printing of inner data stored in a memory, during the printing.SOLUTION: A CPU 101 of an MFP 100 keeps on printing without canceling printing using a cancel key 105b3 when printing of inner data stored in an NVM 104 is performed in accordance with a printing instruction for a main body report received through a network IF 108, and cancels the printing using the cancel key 105b3, when the printing of the inner data is performed in accordance with a printing instruction received from a panel 105.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] This application relates to a technique for printing internal data stored in a memory. [Background technology]

[0002] Patent Document 1 describes an image forming apparatus that allows a user to issue a report printing instruction via an operation unit. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2012-101480 Summary of the Invention [Problem to be solved by the invention]

[0004] However, in the image forming device described in Patent Document 1, while a report is being printed in response to a print instruction from outside the image forming device, there is a risk that the printing may be canceled by someone other than the user who instructed the printing, such as the operator currently operating the image forming device.

[0005] The present application aims to provide a technique for preventing someone from canceling printing of internal data stored in memory while the printing is in progress. [Means for solving the problem]

[0006] In order to achieve the above object, the printing device of the present application is a printing device equipped with a communication interface, a user interface, a memory, and a controller, and the controller is capable of executing a printing process, a cancellation acceptance process that accepts an instruction to cancel printing by the printing process from the user interface, and a cancellation process that cancels printing in response to acceptance of the cancellation instruction by the cancellation acceptance process; when printing of internal data stored in memory by the printing process is being performed in response to a printing instruction accepted from the communication interface, the printing is not canceled by the cancellation process by accepting the cancellation instruction by the cancellation acceptance process, and printing continues; and when printing of internal data stored in memory by the printing process is being performed in response to a printing instruction accepted from the user interface, the printing is canceled by the cancellation process by accepting the cancellation instruction by the cancellation acceptance process. [Effects of the Invention]

[0007] According to the present invention, it is possible to prevent someone else from canceling printing of internal data stored in memory while the printing is in progress. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is a block diagram of a printing system according to an embodiment of the present application. [Figure 2] 2A and 2B are diagrams illustrating an example of a change in the state of a panel in response to a change in the internal state of the MFP in FIG. [Figure 3] 3A and 3B are diagrams showing an example of a change in the state of a panel different from that shown in FIG. 2. [Figure 4] 2 is a diagram showing an example of various data stored in the NVM of the MFP of FIG. 1. FIG. [Figure 5] FIG. 2 illustrates an example of a data configuration of a print job. [Figure 6] 10 is a flowchart showing the procedure of a reception and printing process. [Figure 7]7 is a flowchart showing a continuation of the reception and printing process of FIG. 6. [Figure 8] 10 is a flowchart showing a procedure for a panel operation process. [Figure 9] 10 is a flowchart showing a procedure for a display process. [Figure 10] 10 is a flowchart showing a procedure of a login process. [Figure 11] 2 is a flowchart showing the procedure of the browser process on the PC side and the main process on the MFP side in FIG. 1. DETAILED DESCRIPTION OF THE INVENTION

[0009] Hereinafter, an embodiment of the present application will be described in detail with reference to the drawings. FIG. 1 shows the control configuration of a printing system 1 including an MFP 100 (an example of a "printing device") according to an embodiment of the present application. The printing system 1 includes the MFP 100 and a PC 10 (an example of an "information processing device"). Note that MFP is an abbreviation for multifunction peripheral.

[0010] The MFP 100 is a multifunction peripheral with fax, copy, scan, and print functions. The MFP 100 includes a CPU 101, a ROM 102, a RAM 103, and an NVM 104. NVM is an abbreviation for non-volatile memory.

[0011] The CPU 101 controls the entire MFP 100. The ROM 102 is a memory that stores programs used at startup, such as a boot loader. The NVM 104 is a non-volatile memory that stores control programs (including programs for reception and printing processing (FIGS. 6 and 7), panel operation processing (FIG. 8), display processing (FIG. 9), and login processing (FIG. 10), which will be described later), as well as setting information and the like. The CPU 101 reads out the control programs stored in the NVM 104 and executes various processes. The RAM 103 is a memory that temporarily stores print jobs, image data, and the like. The RAM 103 is also used as a storage area that temporarily stores data, signals, and the like used by the CPU 101 when executing the control programs, or as a work area for data processing.

[0012] The MFP 100 also includes a panel 105 (which is an example of a "user interface" and also an example of a "display"). The panel 105 includes a display unit 105a and a key input unit 105b. In this embodiment, the display unit 105a is configured as a touch panel that allows touch operations, and various screens are displayed on the display unit 105a depending on the state of the MFP 100. A user of the MFP 100 can perform input operations by touching input buttons displayed on the screen. The key input unit 105b is configured with a plurality of keys (for example, three) and can be switched between an on state and an off state for each key, for example, by switching a backlight on and off.

[0013] Furthermore, the MFP 100 includes a network IF 108 (an example of a "communication interface"). The network IF 108 connects the MFP 100 to a communication network 40. In this embodiment, the PC 10 is connected to the communication network 40, and the MFP 100 can transmit and receive various data to and from the PC 10. The communication network 40 may be a network of various types. For example, it may be a wired or wireless LAN, a WAN, or the like.

[0014] The MFP 100 also includes a local IF 109. The local IF 109 is used for local connection to external devices such as the PC 10A, HDD, and CD-ROM drive at short distances. The connection method may be USB, NFC, or the like. NFC stands for near field communication. In this embodiment, the local IF 109 is a USB IF.

[0015] The MFP 100 also includes a print engine 111 and a read engine 112. The print engine 111 is an electrophotographic print engine. The print engine may be an inkjet type, a thermal type, or the like. The read engine 112 is a mechanism for reading an image from a document, and includes a sensor such as a CCD or CIS.

[0016] The CPU 101, the ROM 102, the RAM 103, the NVM 104, the panel 105, the network IF 108, the print engine 111, and the read engine 112 are interconnected by a bus 130.

[0017] In this specification, the term "data" basically refers to the processing of CPU 101 in accordance with instructions written in a program. In other words, processes such as "judging," "extracting," "selecting," "calculating," "deciding," "identifying," "acquiring," "receiving," "control," and "setting" in the following description refer to the processing of CPU 101. Processing by CPU 101 also includes hardware control via the OS. The term "acquiring" is used without necessarily requiring a request. In other words, the process of CPU 101 receiving data without a request is also included in the concept of "CPU 101 acquiring data." Furthermore, "data" in this specification is represented by a computer-readable bit string. Data with essentially the same meaning but different formats is treated as the same data. The same applies to "information" in this specification. Furthermore, processing such as "command," "response," and "request" is performed by communicating information indicating the "command," "response," and "request." Furthermore, terms such as "command," "response," and "request" may be used to mean the information itself indicating the "command," "response," and "request."

[0018] When the MFP 100 is powered on, the CPU 101 executes initialization processing (not shown) and starts panel operation processing (FIG. 8), display processing (FIG. 9), and reception and printing processing (FIGS. 6 and 7). Hereinafter, in the explanation of the procedure of each process, steps are represented as "S."

[0019] When the display process starts, the CPU 101 first displays a home screen on the display unit 105a (S51) in Fig. 9. Fig. 2(a) shows an example of a home screen (screen ID = 100) 105a1 displayed on the display unit 105a. The home screen 105a1 is a "Public" It is composed of button 105a11 and function selection area 105a12 for selecting one of the FAX function, copy function, and scan function of MFP 100. A screen ID is associated with each screen displayed on display unit 105a, and the screen display on display unit 105a is switched in response to switching of the screen ID. CPU 101 writes the screen ID into a screen ID storage area (not shown) provided on RAM 103 in step S3 of the receive and print process, which will be described later.

[0020] 8, when the panel operation process starts, CPU 101 first determines whether or not a panel operation on panel 105 has been detected (S31). If no panel operation has been detected (S31: NO), CPU 101 then determines whether or not the screen ID has changed (S38). If the screen ID has not changed (S38: NO), the process returns to S31. CPU 101 then repeats the determinations of S31 and S38 until a panel operation is detected (S31: YES) or the screen ID changes (S38: YES). Panel operations on panel 105 include touch operations on display unit 105a of panel 105 and key operations on key input unit 105b of panel 105.

[0021] For example, when the home screen 105a1 is displayed on the display unit 105a, When the "ic" button 105a11 is touched, the CPU 101 determines "YES" in S31 above, and then determines whether or not the panel operation is a key operation on the key input unit 105b (S32). Since the panel operation is currently a touch operation on the display unit 105a (S32: NO), the CPU 101 notifies the display processing of the touch operation (S37). This notification is performed, for example, by storing the notification in a touch operation storage area (not shown) provided on the RAM 103. The information stored in the touch operation notification storage area as the touch operation notification is, for example, the touch position on the display unit 105a.

[0022] In the display processing, after the processing of S51, the CPU 101 determines whether or not a key notification or a touch operation notification has been detected (S52). The key notification is performed in S35, which will be described later, in the panel operation processing. Specifically, like the touch operation notification, the key notification is performed by storing the key notification in a key notification storage area (not shown) provided on the RAM 103. However, unlike the touch operation notification, the information stored in the key notification storage area as the key notification is information that identifies the operated key among the three keys of the key input unit 105b. In this way, the key notification is stored in the key notification storage area, and the touch operation notification is stored in the touch operation notification storage area. Therefore, in S52, the CPU 101 determines whether or not a key notification or a touch operation notification is stored in the key notification storage area or the touch operation notification storage area.

[0023] If neither a key notification nor a touch operation notification is detected in the determination of S52 (S52: NO), CPU 101 determines whether the screen ID written in the screen ID storage area has changed (S59). If the determination of this result shows that the screen ID has not changed (S59: NO), CPU 101 further determines whether a home screen display notification has been detected (S61). If a home screen display notification has not been detected (S61: NO), CPU 101 returns the process to S52. Thus, after the process of S51, CPU 101 repeatedly makes the determinations of S52, S59, and S61 until a key notification or a touch operation notification is detected (S52: YES), until the screen ID changes (S59: YES), or until a home screen display notification is detected (S61: YES).

[0024] In the display processing, when the CPU 101 is repeatedly making the judgments of S52, S59, and S61, and is notified of a touch operation of the "Public" button 105a11 by the processing of S37, the CPU 101 judges "YES" in S52, and then judges whether the operation is a press operation of the home key 105b2 (see FIG. 2(a)) of the three keys of the key input unit 105b, and whether the pressability information of the home key 105b2 is "OK" (S53).

[0025] 4(b) shows an example of table data 104b indicating screens and key pressability according to the internal state of MFP 100. Table data 104b includes the internal state of MFP 100, a screen ID that identifies a screen to be displayed on display unit 105a of panel 105 in that internal state, and key pressability information that indicates whether to validate ("OK" in FIG. 4(b)) or invalidate ("NG" in FIG. 4(b)) the pressing of three keys provided on key input unit 105b of panel 105 in that internal state, specifically, back key 105b1, home key 105b2, and cancel key 105b3, when each key is pressed. The table data 104b is registered in NVM 104, for example. When the internal state of MFP 100 is "receiving print instructions," there is no screen ID (-). This is because the time during which MFP 100's internal state is "receiving print instructions" is extremely short, and there is little need to switch the screen of display unit 105a to the "receiving print instructions" screen. Of course, this is not limiting, and a screen ID that identifies the "receiving print instructions" screen may be determined and the "receiving print instructions" screen may be displayed. Furthermore, display screen data 104c is also stored in NVM 104 in association with each screen ID, as shown in FIG. 4(c).

[0026] The internal state of MFP 100 is determined by defining a plurality of internal states in advance and by CPU 101 selecting a state that matches the current state from the defined plurality of internal states and storing the selected state in, for example, an internal state storage area (not shown) provided on RAM 103. Therefore, the internal state of MFP 100 is the internal state stored in the internal state storage area on RAM 103. CPU 101 writes the internal state to the internal state storage area on RAM 103 as appropriate when it is necessary to switch from the current internal state to another internal state.

[0027] Returning to FIG. 9, since a touch operation notification, not a key notification, has been detected, CPU 101 determines "NO" in S53 and checks the currently displayed screen (S54). Specifically, this check is performed by checking the screen ID written in the screen ID storage area. CPU 101 then determines whether a process that should notify a panel operation is currently being executed based on the checked screen (S55). If the screen ID checked in S54 is 100, CPU 101 determines "NO," and if the screen ID is 101 to 105, CPU 101 determines "YES." In other words, if the screen ID is 101 to 105, CPU 101 determines that the above-mentioned receive and print process (FIGS. 6 and 7) is currently being executed as a process that should notify a panel operation. Since the current screen ID is 100, CPU 101 determines "NO" in S55 and notifies the start of a screen update and / or process corresponding to the key in the key notification or the touch position in the touch operation notification (S57). The touch operation on the "Public" button 105a11 is an instruction to start the login process (FIG. 10), so in S57 the CPU 101 updates the screen according to the touch position and notifies the user of the start of the login process.

[0028] In response to this, the CPU 101 starts the login process of FIG. 10 and displays a list of users on the display unit 105a (S71).

[0029] FIG. 2(c) shows an example of a user selection screen 105a3 displayed on the display unit 105a. The user selection screen 105a3 includes a display for instructing user selection (for example, "Select User The MFP 100 comprises a display area 105a31 that displays a list of users (such as "User ID") and a user list display area 105a32 that displays a list of users. The operator of the MFP 100 can proceed to login authentication by selecting his / her own user name from the users displayed in the user list display area 105a32.

[0030] 4(a) shows an example of a user DB 104a for login management and function restriction management. Note that DB is an abbreviation for database. The user DB 104a is created, for example, by an administrator who manages the MFP 100, and is stored in the NVM 104 of the MFP 100. The user DB 104a is composed of the following items: main body LoginUser name, PcUser name, PIN, and Function.

[0031] The main body LoginUser name is a user name used when logging in to the MFP 100. The PcUser name is an alias associated with the main body LoginUser name. In S71 above, the list of users displayed on the display unit 105a is a list of main body LoginUser names registered in the user DB 104a.

[0032] PIN is a personal identification number. The PIN is registered in advance together with the LoginUser name of the device and is used for login authentication to the MFP100.

[0033] Function is information for the above-mentioned function restriction management, and indicates whether or not a user with a registered main body LoginUser name can use the print function, scan function, and copy function (Print, Scan, and Copy in FIG. 4(a)). In other words, a user with a registered main body LoginUser name can use functions for which "OK" is registered, but cannot use functions for which "NG" is registered. For example, when a user with a main body LoginUser name of "suzuki" logs in to MFP100, he or she can use the print function and scan function of MFP100, but cannot use the copy function of MFP100.

[0034] Returning to FIG. 10, the CPU 101 waits, for example, until one of the users displayed in the user list display area 105a32 is selected (S72: NO), and when one of the users is selected (S72: YES), the CPU 101 displays a PIN entry screen on the display unit 105a (S73).

[0035] Next, CPU 101 waits until PIN entry is complete (S74: NO), and when PIN entry is complete (S74: YES), determines whether the entered PIN is correct (S75).

[0036] If the entered PIN is determined to be correct in S75 (S75: YES), CPU 101 saves the login user name, i.e., the selected main body LoginUser name, in RAM 103 (S76), and then determines whether image data stored by the login user has been stored (S77). Hereinafter, the selected main body LoginUser name will be referred to as the "selected LoginUser name." CPU 101 determines whether image data associated with a main body LoginUser name that matches the selected LoginUser name has been stored. In S6 of FIG. 6, CPU 101 stores the image data in association with the main body LoginUser name that indicates the user who sent the original print job. Details will be described later.

[0037] If it is determined in S77 that image data stored by the login user, i.e., the user indicated by the selected LoginUser name, has been accumulated (S77: YES), CPU 101 notifies the above-mentioned receiving and printing process of a print instruction for the accumulated image data (S78), and then terminates the login process.

[0038] When the process proceeds from S77 to S78, the logged-in user may have accumulated multiple pieces of image data. In this case, the file names of the multiple pieces of image data, for example, may be displayed on the display unit 105a, and the logged-in user may select the image data he or she wishes to print. Alternatively, all of the image data may be printed without requiring a selection. In this way, it is possible for the same user to accumulate multiple pieces of image data, but for the sake of convenience, it will be assumed below that each user accumulates only one piece of image data.

[0039] On the other hand, if the determination in S77 above is that there is no image data accumulated by the login user (S77: NO), CPU 101 executes the home screen display notification for display processing (S79) and then terminates the login processing. In S61 (FIG. 9) of the display processing, if CPU 101 detects this home screen display notification (S61: YES), the processing returns to S51 above and displays the home screen on display unit 105a (S51). At this time, CPU 101 determines whether the selected Login User name is stored in RAM 103. If the selected Login User name is stored, the logged-in home screen is displayed on display unit 105a. FIG. 3(b) shows an example of a logged-in home screen 105a6 displayed on display unit 105a. The logged-in home screen 105a6 is configured with a display area 105a61 that displays the selected Login User name and a function selection area 105a62. When the selected Login User name displayed in the display area 105a61 of the logged-in home screen 105a6 is touched and an operation to log out is performed, the CPU 101 deletes the selected Login User name saved in the RAM 103. The screen of the display unit 105a transitions to the home screen 105a1 shown in FIG. 2(a) above.

[0040] 11 shows the procedure for sending a main body report print instruction from PC 10 to MFP 100. In this embodiment, the main body report (an example of "internal data") is a report for managing MFP 100, such as a report for informing an administrator of the remaining toner amount, the number of pages printed, and the usage status of each function of MFP 100. As each function is executed, MFP 100 stores information indicating the usage status in NVM 104. MFP 100 may select the information to print according to information included in the main body report print instruction that indicates which usage status is to be printed as the main body report.

[0041] The browser processing in Fig. 11 starts when PC 10 is instructed to start a browser and a browser screen is displayed on the display of PC 10. When a logged-in user of PC 10, for example, an administrator of MFP 100, enters the URL of an EWS into the browser screen, PC 10 sends an EWS screen acquisition request to MFP 100 (S201). Note that EWS is an abbreviation for embedded web server, and is a web server built into MFP 100. The EWS is realized by processing of CPU 101 of MFP 100. At this time, the main processing in Fig. 11 is processing of CPU 101 as the EWS. The main processing is started when the power of MFP 100 is turned on.

[0042] When the CPU 101 of the MFP 100 receives an EWS screen acquisition request from the PC 10, it transmits EWS screen data corresponding to the request to the PC 10 (S101). The EWS screen is a type of web page data. When the PC 10 receives the EWS screen data from the MFP 100, it displays the EWS screen on the browser screen. The PC 10 waits until an administrator login password is entered in a login password input field provided in the EWS screen (S202: NO), and when the administrator login password is entered (S202: YES), it transmits an authentication request to the MFP 100 using the entered administrator login password (S203).

[0043] When the CPU 101 of the MFP 100 receives an authentication request from the PC 10, it performs the authentication (S102) and determines whether the entered administrator login password is correct (S103). If the entered administrator login password is incorrect (S103: NO), the CPU 101 sends a login denial notice to the PC 10. On the other hand, if the entered administrator login password is correct (S103: YES), the CPU 101 sends post-login page data of the EWS screen to the PC 10 (S104).

[0044] When PC 10 receives the post-login page data from MFP 100, it displays the post-login page on the browser screen. The post-login page displays an operator for sending a main body report print instruction to MFP 100, so when the administrator operates that operator, PC 10 sends a main body report print instruction to MFP 100 (S204).

[0045] When the CPU 101 of the MFP 100 receives the instruction to print a main body report from the PC 10, it notifies the reception and printing process (FIGS. 6 and 7) described next of the instruction to print a main body report from outside (S105).

[0046] 6 and 7 show the procedure for the receive and print process. In FIG. 6, CPU 101 first determines whether reception of a print job has started (S1). Specifically, CPU 101 determines whether data is stored in the receive buffer. If data is stored, CPU 101 determines whether the data is a print job. If the data is a print job, CPU 101 determines whether the beginning of the print job is stored. The receive buffer is provided, for example, on RAM 103 and is an area for storing data received from outside MFP 100 via network IF 108, local IF 109, etc. Note that the data stored in the receive buffer is not limited to data from outside MFP 100. Various notifications issued by CPU 101 for the receive and print process may also be stored in the receive buffer. For example, the notification in S78 (FIG. 10) may be performed by storing information identifying the image data to be printed, specifically, information indicating the location where the image data is stored, in the receive buffer. In this embodiment, print jobs are generated by PC 10, transmitted from PC 10 onto communication network 40, and received by MFP 100 via network IF 108, and also received by MFP 100 via local IF 109 from PC 10A (see FIG. 1) connected via local IF 109. Note that PC 10A basically has the same configuration as PC 10. In other words, hereinafter, the description of PC 10 is also the description of PC 10A.

[0047] FIG. 5 shows an example of the data structure of a print job 200. As shown in FIG. 5, the print job 200 is structured by enclosing a PDL in PJL. Note that PDL is an abbreviation for page description language, and PJL is an abbreviation for printer job language. The beginning of the print job 200 begins with " <esc>%-12345X@PJL" and the end of print job 200 is " <esc>%-12345X". Therefore, when the print job to be received in S1 is print job 200, CPU 101 determines whether reception of the print job has started by checking the received data. <esc>The determination is made based on whether "%-12345X@PJL" is detected. Print job 200 also includes information such as the print job name test.txt, the user name suzuki, and the creation date and time 20210413201010. Note that the data structure of a print job received by MFP 100 may differ from the data structure of print job 200, but for convenience of explanation in this embodiment, it is assumed that MFP 100 receives a print job with the same data structure as print job 200.

[0048] Returning to FIG. 6, when reception of a print job is started in the determination of S1 above (S1: YES), CPU 101 determines whether the print job corresponds to a registered main body LoginUser name (S2). Specifically, if the PcUser name included in the print job matches any of the main body LoginUser names registered in user DB 104a (FIG. 4(a)), the determination is "YES." Note that the same user may use different user names on MFP 100 and PC 10. For this reason, the main body LoginUser name used on MFP 100 and the PcUser name included in the print job and used on PC 10 are linked by user DB 104a. In this embodiment, it is assumed that a print job including the name of the user logged in to PC 10 as the PcUser name is created by the printer driver of PC 10. Therefore, even if the PcUser name included in the print job does not match any of the main body LoginUser names registered in the user DB 104a, the CPU 101 determines "YES" in S2 if the main body LoginUser name linked to the PcUser name included in the received print job is registered in the user DB 104a. For example, if the received print job includes "kato" as the PcUser name, the PcUser name "kato" and the main body LoginUser name "kat" are registered in the user DB 104a in association with each other, and therefore the CPU 101 determines "YES" in S2.

[0049] If it is determined in S2 that the print job that has started to be received is a print job corresponding to the registered main body LoginUser name (S2: YES), CPU 101 displays a receiving screen on display unit 105a of panel 105 (S3).

[0050] Table data 104b lists three internal states of MFP 100 indicating that a print job is being received: "Receiving a print job," "Receiving a print job (print instructor login)," and "Receiving a print job (via USB connection)." When print job reception is started (S1: YES), CPU 101 must determine which of these internal states the current internal state corresponds to before proceeding to S2. First, CPU 101 determines whether the print job that has started to be received is a print job from network IF 108 or a print job from local IF 109. Because print jobs from network IF 108 and local IF 109 are stored in different areas of the receive buffer, CPU 101 can determine whether the print job was received from network IF 108 or local IF 109. If the print job is received from network IF 108, CPU 101 further determines whether the print job started to be received during print instructor login. If a login user exists, as explained in S76 of the login process (FIG. 10), the selected LoginUser name is stored in RAM 103, and CPU 101 determines whether the selected LoginUser name matches the PcUser name included in the print job. If they do not match, CPU 101 determines whether the main body LoginUser name linked by user DB 104a to the PcUser name included in the print job matches the selected LoginUser name. If the selected LoginUser name matches the PcUser name included in the print job, CPU 101 writes "Receiving print job (print instructor Login)" to the internal state storage area. The same applies if the main body LoginUser name linked to the PcUser name matches the selected LoginUser name. On the other hand, if the selected LoginUser name does not match the PcUser name included in the print job, and the main body LoginUser name linked to the PcUser name does not match the selected LoginUser name, CPU 101 writes "print job being received" to the internal state storage area.Furthermore, if the print job is received from the local IF 109, the CPU 101 writes "print job being received (via USB connection)" to the internal state storage area. Note that, as described above, the local IF 109 in this embodiment employs a USB IF.

[0051] In S3 of FIG. 6, CPU 101 displays the receiving screen on display unit 105a. Specifically, CPU 101 writes screen ID "101" or "105" into the screen ID storage area. Here, whether "101" or "105" is to be written as the screen ID into the screen ID storage area is determined based on the internal state of MFP 100. That is, CPU 101 refers to table data 104b, and if the internal state of MFP 100 is "receiving a print job," CPU 101 writes screen ID "101" into the screen ID storage area. On the other hand, if the internal state of MFP 100 is "receiving a print job (print instructor login)," CPU 101 writes screen ID "105" into the screen ID storage area. If the internal state of MFP 100 is "receiving a print job (via USB connection)," CPU 101 writes screen ID "105" into the screen ID storage area.

[0052] In the above display process (FIG. 9), when CPU 101 detects neither a key notification nor a touch operation notification (S52: NO), it determines whether the screen ID written in the screen ID storage area has changed (S59), and if the screen ID has changed (S59: YES), CPU 101 reads out display screen data associated with the changed screen ID from NVM 104 and displays it on display unit 105a, thereby updating the screen (S60).

[0053] FIG. 2(b) shows an example of receiving screen (screen ID=101) 105a2 displayed on display unit 105a. Receiving screen 105a2 is configured with display area 105a21 that displays the internal state of MFP 100 and display area 105a22 that displays the operating state of MFP 100. FIG. 3(d) shows an example of receiving screen (screen ID=105) 105a8 displayed on display unit 105a. Like receiving screen 105a2, receiving screen 105a8 is configured with display area 105a81 that displays the internal state of MFP 100 and display area 105a82 that displays the operating state of MFP 100. Receiving screen 105a2 in FIG. 2(b) and receiving screen 105a8 in FIG. 3(d) have different screen IDs, but the display content of the screens is the same. However, the on / off states of the three keys 105b1 to 105b3 of the key input unit 105b are different between Figure 2(b) and Figure 3(d). The on / off control of the keys 105b1 to 105b3 is performed within the panel operation process (Figure 8).

[0054] 8, if no panel operation on panel 105 is detected (S31: NO), CPU 101 determines whether the screen ID written in the screen ID storage area has changed (S38), similar to S59 (FIG. 9). If the screen ID has changed (S38: YES), CPU 101 checks the internal state stored in the internal state storage area (S40), and, based on the key pressability information corresponding to this internal state in table data 104b, lights up keys that can be pressed and turns off keys that cannot be pressed (S41). That is, when the internal state is "receiving a print job," all three keys 105b1 to 105b3 are turned off, as shown in Fig. 2(b), and when the internal state is "receiving a print job (print instructor login)" or "receiving a print job (via USB connection)," only the cancel key 105b3 is turned on, and the other keys 105b1 and 105b2 are turned off, as shown in Fig. 3(d). In this way, the lighting / turning off of the keys 105b1 to 105b3 corresponds to the enabled / disabled status of each of the keys 105b1 to 105b3.

[0055] Returning to FIG. 6 , CPU 101 next determines whether the accumulated printing function is enabled (S4). The accumulated printing function is a function that accumulates a received print job in memory (RAM 103 in this embodiment, but is not limited thereto and may also be NVM 104 or a USB memory attached to the USBIF) and then prints the print job in response to a user's login. The accumulated printing function encompasses both accumulating a received print job in memory as is and then printing the print job in response to a user's login, as well as, as in this embodiment, performing RIP processing on the received print job, accumulating the generated image data in memory, and then printing the print job in response to a user's login. However, this embodiment describes an example in which the generated image data is accumulated in RAM 103 (see S5 and S6 below). Note that RIP is an abbreviation for raster image processor. The accumulated printing function may be enabled or disabled by selecting various settings on MFP 100, for example. The enabled or disabled state of the accumulated printing function may be selected and set by PC 10 via network IF 108.

[0056] If the determination in S4 above shows that the accumulated print function is enabled (S4: YES), CPU 101 RIPs the print data included in the print job (S5), and accumulates the RIP-processed image data in a predetermined area on RAM 103 in association with the user name of the user who sent the original print job (S6). Specifically, even if CPU 101 determines in S2 that the PcUser name included in the print job matches one of the main body LoginUser names registered in user DB 104a, or even if it determines in S2 that the main body LoginUser name linked to the PcUser name included in the received print job is registered in user DB 104a, CPU 101 stores the main body LoginUser name in association with the image data.

[0057] Next, CPU 101 determines whether the storage of image data in RAM 103 is complete (S7). If the storage of image data in RAM 103 is not yet complete (S7: NO), CPU 101 determines whether a cancel key notification has been received (S8). If the cancel key notification has not been received (S8: NO), CPU 101 returns the process to S7. On the other hand, if the determination in S8 shows that a cancel key notification has been received (S8: YES), CPU 101 cancels the storage of image data in RAM 103 midway (S9) and then proceeds to S16. Furthermore, if CPU 101 is RIP-processing a print job while receiving it and storing the image data, it not only cancels the storage but also cancels the reception of the print job. Here, the cancel key notification is issued in S56 of the display process (FIG. 9). Before that, whether or not the cancel key 105b3 can be pressed is determined in S34 of the panel operation process (FIG. 8) above, so the control of the cancel key notification will be explained below based on the related processes in the panel operation process and display process.

[0058] 8, if the detected panel operation is a key operation on the key input unit 105b (S32: YES), the CPU 101 checks the internal state stored in the internal state storage area (S33), similar to S40. Next, the CPU 101 refers to the table data 104b (FIG. 4(b)) and determines whether the key operation is a key operation that can be pressed in the current internal state (S34). In the table data 104b, if the current internal state is "receiving a print job," the pressability of the back key 105b1, home key 105b2, and cancel key 105b3 of the key input unit 105b is "NG." Therefore, in this case, the determination in S34 is "NO" regardless of the key operation of any of the keys 105b1 to 105b3. On the other hand, if the current internal state is "receiving a print job (print instructor login)" or "receiving a print job (via USB connection)," the determination in S34 is "NO." In this case, the determination as to whether the back key 105b1 and the home key 105b2 can be pressed is "NG", but the determination as to whether the cancel key 105b3 can be pressed is "OK", so in this case, if the cancel key 105b3 is pressed, the determination in S34 is "YES".

[0059] If it is determined in S34 that the key operation is an operation on a key that can be pressed in the current internal state (S34: YES), CPU 101 notifies the display process of the operated key (S35), and then returns the process to S31. On the other hand, if it is determined in S34 that the key operation is not an operation on a key that can be pressed in the current internal state (S34: NO), CPU 101 sounds a rejection sound to notify the operator that the key operation has been rejected (S36), and then returns the process to S31. In S35, as described above, CPU 101 stores information identifying the operated key in the key notification storage area.

[0060] Next, when the process proceeds to S52 of the display process (FIG. 9), a key notification may or may not be stored in the key notification storage area. That is, when the process proceeds from S34 to S35, a key notification is stored in the key notification storage area, but when the process proceeds from S34 to S36, no key notification is stored in the key notification storage area. If a key notification is currently stored in the key notification storage area, no touch operation notification is stored in the touch operation notification storage area. When the CPU 101 detects a key notification (S52: YES) and the detected key notification indicates that the enabled home key 105b2 has been pressed (S53: YES), the process returns to S51 and the home screen is displayed on the display unit 105a.

[0061] In the determination of S53 above, if an invalid home key 105b2 has been pressed or if the home key 105b2 itself has not been pressed (S53: NO), CPU 101 checks the currently displayed screen (S54). This check is performed by checking the screen ID written in the screen ID storage area, as described above. CPU 101 then determines whether a process that should be notified of a panel operation is currently being executed based on the confirmed screen (S55). As described above, if the screen ID is 101 to 105, CPU 101 determines that the receive and print process of FIG. 6 is currently being executed as a process that should be notified of a panel operation (S55: YES), and CPU 101 notifies the process that should be notified of a panel operation of the key notification key (S56). For example, as shown in FIG. 3(d) above, if the illuminated cancel key 105b3 in key input section 105b is pressed while receiving screen 105a8 is displayed on display section 105a, CPU 101 determines "YES" in S52 and also determines "YES" in S55, and therefore notifies the reception and printing process of information identifying cancel key 105b3 related to the key notification. In the reception and printing process, if CPU 101 receives this notification (S8: YES) before the accumulation of image data is completed (S7: NO), the accumulation of image data is canceled midway (S9). Although screen IDs are not specified, screen IDs are also assigned to the screens displayed in the login process (FIG. 10) and the menu screens described below. Therefore, when a list of users is displayed or when a PIN entry screen is displayed, the CPU 101 can determine that a panel operation should be notified to the login process, and when a menu screen is displayed and an operation is performed to instruct printing of a main body report, the CPU 101 can determine that a panel operation should be notified to the receive and print process.

[0062] The cancel key 105b3 can be pressed either briefly (an example of a "first cancel instruction") or long-pressed (an example of a "second cancel instruction"). For example, if the current internal state is "Receiving a print job (print instructor login)," one of the multiple transmitted jobs may be undergoing RIP processing and being stored. In this case, if the cancel key 105b3 is pressed briefly, the CPU 101 cancels the storage of the print job currently being stored. If the cancel key 105b3 is pressed long-pressed, the CPU 101 cancels the reception of the print job currently being stored and also cancels the reception of any remaining print jobs newly received during the long-press period. In other words, if multiple print jobs are received during the long-press period, the reception of those multiple print jobs is canceled. The determination of whether the cancel key 105b3 can be pressed in S34 applies to both a short press and a long press. As described above, when CPU 101 receives one job and stores image data based on that job, it also cancels the reception of that job whether the key is pressed briefly or pressed long.

[0063] On the other hand, as shown in FIG. 2B, if the unlit cancel key 105b3 on the key input unit 105b is pressed while the receiving screen 105a2 is displayed on the display unit 105a, the CPU 101 determines "NO" in S52 and does not proceed to S56. Therefore, the CPU 101 does not notify the reception and printing process of information identifying the cancel key 105b3 related to the key notification. As a result, in the reception and printing process, the CPU 101 does not receive this notification (S8: NO), and the accumulation of the image data is completed without being canceled midway (S7: YES). Thus, when the internal state is "receiving a print job," the reception of the print job "receiving a print job" cannot be canceled by the cancel key 105b3. This makes it possible for the MFP 100 of this embodiment to prevent anyone other than the user who sent the print job for storage printing from canceling the reception of the print job while the print job for storage printing, which was sent via the network from a PC 10 located far from the MFP 100, is being received. In this embodiment, when an unlit key is pressed, the key press operation itself is accepted (see S32 of the panel operation process), but no processing according to the pressed key is performed (see S34 of the panel operation process). However, this is not limiting, and when an unlit key is pressed, the key press operation itself may not be accepted.

[0064] On the other hand, if it is determined in S7 that the storage of image data in RAM 103 has been completed (S7: YES), CPU 101 advances the process to S16. In S16, CPU 101 displays the home screen on display unit 105a of panel 105. Specifically, CPU 101 writes screen ID "100" in the screen ID storage area on RAM 103. Note that before performing the process of S16, CPU 101 writes "operation completed" in the internal state storage area. As a result, in S16, CPU 101 refers to table data 104b and writes screen ID "100" when the internal state is "operation completed" in the screen ID storage area, and the home screen is displayed on display unit 105a in S60 of the display process. After the process of S16, CPU 101 returns the process to S1.

[0065] On the other hand, if the determination in S4 above shows that the storage printing function is disabled (S4: NO), CPU 101 performs RIP processing on the print data included in the print job in the same manner as in S5 above (S10). Then, CPU 101 displays a printing screen on display unit 105a of panel 105 (S11). Specifically, CPU 101 writes screen ID "102" to the screen ID storage area on RAM 103. Note that, before performing the processing of S11, CPU 101 writes "printing image data" to the internal state storage area. As a result, in S11, CPU 101 refers to table data 104b and writes screen ID "102" when the internal state is "printing image data" to the screen ID storage area, so that the printing screen is displayed on display unit 105a. FIG. 3(a) shows an example of a printing screen (screen ID=102, 103) 105a5 displayed on display unit 105a. Printing screen 105a5 is made up of display area 105a51 that displays the internal state of MFP 100 and display area 105a52 that displays the operating state of MFP 100. CPU 101 then starts printing by outputting the image data after RIP processing to print engine 111 (S12).

[0066] Next, CPU 101 determines whether printing is complete (S13). If printing is not complete (S13: NO), CPU 101 determines whether a cancel key notification has been received (S14), similar to S8 above. If a cancel key notification has not been received (S14: NO), CPU 101 returns the process to S13 above. On the other hand, if a cancel key notification has been received (S14: YES) in the determination of S14, CPU 101 cancels printing midway (S15) and then proceeds to S16.

[0067] FIG. 3(a) also shows the key input section 105b when the internal state is "printing image data." In this key input section 105b, only the cancel key 105b3 is lit, and the other keys 105b1 and 105b2 are off. In other words, the state of this key input section 105b is the same as the state of the key input section 105b in FIG. 3(d). Therefore, when the internal state is "printing image data," the cancel key 105b3 is enabled. Therefore, if the cancel key 105b3 is pressed when printing of the image data is incomplete (S13: NO), the CPU 101 receives a cancel key notification (S14: YES) and cancels the printing of the image data midway (S15). Thus, when the internal state is "printing image data," printing of the image data in progress can be canceled using the cancel key 105b3. In this case, the printing of the image data in progress is not printing using the storage printing function, so cancellation of the printing is permitted.

[0068] On the other hand, if it is determined in S13 that printing has been completed (S13: YES), the CPU 101 advances the process to S16.

[0069] On the other hand, if it is determined in step S2 that the print job that has started to be received is not a print job corresponding to the registered LoginUser name (S2: NO), the CPU 101 cancels the reception without RIP-processing the print job (S17), and then ends the reception and printing process. Note that instead of canceling the print job in step S17, printing based on the print job may be performed.

[0070] On the other hand, if the determination in S1 above indicates that the reception of a print job has not started (S1: NO), CPU 101 determines whether an external instruction to print a main body report has been received (S20 in FIG. 7). This determination is also made by CPU 101 depending on whether an external instruction to print a main body report has been stored in the receive buffer, specifically, whether the notification in S105 above (FIG. 11) has been received.

[0071] If it is determined in S20 that an external instruction to print a main body report has been received (S20: YES), CPU 101 displays a printing screen on display 105a of panel 105 (S21). Specifically, CPU 101 writes screen ID "104" to the screen ID storage area in RAM 103. Note that before performing the processing of S21, CPU 101 writes "Main body report printing by external instruction" to the internal status storage area. The timing of this write is not limited to this, and may be before or after CPU 101 notifies the receive and print process of the instruction (S105) in response to receiving the main body report print instruction sent by PC 10 in S204 (FIG. 11) above. As a result, in S21, CPU 101 refers to table data 104b and writes screen ID "104" when the internal state is "printing main body report by external instruction" into the screen ID storage area, so that in S60 of the display processing described above, a printing-in-progress screen is displayed on display unit 105a. FIG. 3(c) shows an example of printing-in-progress screen (screen ID=104) 105a7 displayed on display unit 105a. Like printing-in-progress screen 105a5 (FIG. 3(a)), printing-in-progress screen 105a7 is configured from display area 105a71 that displays the internal state of MFP 100 and display area 105a72 that displays the operating state of MFP 100. Next, CPU 101 generates image data for the instructed main body report and outputs it to print engine 111, thereby starting printing (S22), and then proceeds to the processing at S13 (FIG. 6) described above.

[0072] FIG. 3C also shows the key input section 105b when the internal state is "printing a main body report by external command." All three keys 105b1 to 105b3 of this key input section 105b are off. In other words, the state of this key input section 105b is the same as the state of the key input section 105b in FIG. 2B. Therefore, when the internal state is "printing a main body report by external command," the cancel key 105b3 is disabled. Therefore, even if the cancel key 105b3 is pressed when printing of the main body report is incomplete (S13: NO), the CPU 101 does not receive a cancel key notification (S14: NO), and printing of the main body report is completed without being canceled midway (S13: YES). Thus, when the internal state is "printing a main body report by external command," the printing of the main body report in progress cannot be canceled by the cancel key 105b3. This makes it possible to prevent a person other than the user of the PC 10 from canceling the printing of a main body report in response to an external instruction from the PC 10, for example.

[0073] On the other hand, if the determination in S20 above is that a main body report print instruction has not been received from an external source (S20: NO), the CPU 101 determines whether a main body report print instruction has been received from the panel 105 (S23). The main body report print instruction can be issued not only from the external source but also from the display unit 105a of the panel 105. Specifically, for example, when the home screen 105a1 (FIG. 2(a)) is displayed on the display unit 105a, if a menu button (not shown) on the home screen 105a1 is touched, the menu screen is displayed, and if the main body report print instruction is touched on the menu screen, the CPU 101 notifies the receive and print process of the main body report print instruction.

[0074] If the determination in S23 above indicates that a print instruction for a main body report has been issued from the panel 105 (S23: YES), the CPU 101 displays a print-in-progress screen on the display unit 105a of the panel 105 (S24). Specifically, the CPU 101 writes the screen ID "103" to the screen ID storage area in the RAM 103. Before performing the processing in S24, the CPU 101 writes "Main body report printing instructed by panel" to the internal status storage area. The timing of this write is not limited to this, and it may be before or after receiving a touch operation for a print instruction for a main body report from the menu screen and notifying the receive and print process of the print instruction for a main body report. As a result, in S24, the CPU 101 refers to the table data 104b and writes the screen ID "103" when the internal status is "Main body report printing instructed by panel" into the screen ID storage area. Therefore, the print-in-progress screen is displayed on the display unit 105a by S60 of the display processing. The printing screen 105a5 in FIG. 3(a) serves as both the printing screen with the screen ID "102" and the printing screen with the screen ID "103". Next, the CPU 101 advances the process to S22.

[0075] The key input section 105b in FIG. 3A serves both as the key input section 105b when the internal state is "printing image data" and as the key input section 105b when the internal state is "printing a main body report by panel instruction." Therefore, when the internal state is "printing a main body report by panel instruction," the cancel key 105b3 is valid, just as when the internal state is "printing image data." Therefore, if the cancel key 105b3 is pressed when printing of the main body report is incomplete (S13: NO), the CPU 101 receives a cancel key notification (S14: YES) and cancels the printing of the main body report (S15). In this way, when the internal state is "printing a main body report by panel instruction," the printing of the main body report in progress can be canceled by the cancel key 105b3. This is because the user who instructed printing of the main body report from the panel 105 is the one who is canceling the printing.

[0076] On the other hand, if the determination in S23 above is that the instruction to print the main body report has not been received from the panel 105 (S23: NO), the CPU 101 determines whether or not an instruction to print the accumulated image data has been received (S25). The instruction to print the accumulated image data is received in S78 of the login process.

[0077] If it is determined in S25 that a print instruction for the accumulated image data has been issued (S25: YES), CPU 101 displays a printing screen on display unit 105a of panel 105 (S26). Specifically, CPU 101 writes screen ID "102" to the screen ID storage area on RAM 103. Note that before performing the process of S26, CPU 101 writes "accumulated image data currently being printed" to the internal state storage area. The timing of this write is not limited to this, and it may be before or after CPU 101 notifies the receive and print process of the print instruction in S78 (FIG. 10). As a result, in S24, CPU 101 refers to table data 104b and writes screen ID "102" when the internal state is "accumulated image data currently being printed" into the screen ID storage area, so that the printing screen with screen ID "102" is displayed on display unit 105a. Next, CPU 101 starts printing by outputting the accumulated image data to print engine 111 (S27), and then proceeds to S13 (FIG. 6) above. Note that, since the image data to be printed has already been specified in the print instruction for the accumulated image data, in S26, CPU 101 only needs to output the specified image data to print engine 111. An example of the printing screen with screen ID "102" has already been shown as printing screen 105a5 in FIG. 3(a) above. Also, key input section 105b in FIG. 3(a) also shows key input section 105b when the internal state is "printing accumulated image data." Therefore, when the internal state is "printing stored image data," the cancel key 105b3 is valid, just as when "printing image data" and "printing a main unit report by panel instruction" are in progress. Therefore, if the cancel key 105b3 is pressed when printing of the stored image data is incomplete (S13: NO), the CPU 101 receives a cancel key notification (S14: YES) and cancels the printing of the stored image data midway (S15). In this way, when the internal state is "printing stored image data," printing of the image data in progress can be canceled by the cancel key 105b3. This allows the logged-in user to cancel the printing of image data for a stored print job that the user himself / herself instructed to PC 10A.

[0078] On the other hand, if it is determined in S25 that a print instruction for the accumulated image data has not been received (S25: NO), the CPU 101 returns the process to S1 (FIG. 6).

[0079] In this embodiment, if a cancel key notification is received while receiving a print job when the accumulated print function is enabled (S8: YES), the reception of the print job is canceled (S9 above), and the reception of a cancel key notification while receiving a print job when the accumulated print function is disabled is not taken into consideration. However, this is not limiting, and even when the accumulated print function is disabled, the reception of the print job may be canceled when a cancel key notification is received, just as when the accumulated print function is enabled. This allows MFP 100 of this embodiment to at least prevent someone other than the user who sent the print job for accumulated printing from canceling the reception of the print job while it is being received, the print job being sent from PC 10 located far from MFP 100 via the network.

[0080] Furthermore, in this embodiment, while receiving screen 105a2 is displayed on display unit 105a, pressing of the cancel key is not transmitted to the reception and printing process, but while receiving screen 105a8 is displayed on display unit 105a, pressing of the cancel key may also not be transmitted to the reception and printing process. This makes it possible for MFP 100 of this embodiment to prevent, at least, a user other than the user who sent the print job for stored printing from canceling the reception of the print job that was sent via the network from PC 10 located far from MFP 100 while the print job for stored printing is being received.

[0081] Furthermore, when the internal state is "print job receiving (print instructor login)", a receiving screen 105a2 with the screen ID 101 may be displayed on the display unit 105a.

[0082] In this embodiment, the key input unit 105b is configured with three keys 105b1 to 105b3, and each key can be switched between a lit state and an unlit state. However, the present invention is not limited to this, and buttons corresponding to the three keys 105b1 to 105b3 may be displayed on the display unit 105a, and the buttons may be displayed / hidden instead of the lit / unlit control in S41.

[0083] In addition, in this embodiment, a communication IF for local connection over a short distance is used as the local IF 109, but this is not limiting, and a communication IF that is primarily intended for one-to-one connection may be used as the local IF, in which case, for example, a communication IF using a Bluetooth (registered trademark) system or a Wi-Fi Direct system may be used as the local IF. Also, a communication IF that is primarily intended for temporary connection may be used as the local IF, in which case, for example, a communication IF using a Bluetooth system or a Wi-Fi Direct system may be used as the local IF.

[0084] The present invention is not limited to the above-described embodiment, and various modifications are possible without departing from the spirit of the present invention.

[0085] (1) In the above embodiment, the MFP 100 was used as an example of a printing device, but the printing device is not limited to the MFP 100 and may be a standalone printer.

[0086] (2) In the above embodiment, one CPU 101 is used as an example of a controller, but this is not limiting and a controller consisting of multiple CPUs may be used, or a controller including a CPU consisting of multiple cores may be used. Also, a controller may have a CPU and a dedicated circuit. Examples of the dedicated circuit include an ASIC and an FPGA. [Explanation of symbols]

[0087] 1...printing system, 10...PC, 40...communication network, 100...MFP, 101...CPU, 102...ROM, 103...RAM, 104...NVM, 105...panel, 105a...display unit, 105b...key input unit, 108...network IF, 109...local IF, 111...printing engine, 112...reading engine, 130...bus.< / esc> < / esc> < / esc>

Claims

1. a communication interface; A user interface; Memory and A controller; A printing device comprising: The controller The printing process, a cancellation reception process for receiving, from the user interface, an instruction to cancel printing performed by the printing process; a cancellation process for canceling the printing in response to the cancellation instruction being accepted by the cancellation acceptance process; is executable, When the printing of the internal data stored in the memory by the printing process is being performed in response to a print instruction received from the communication interface, the printing is continued without canceling the printing by the cancellation process due to the cancellation instruction being received by the cancellation receiving process, When the printing of the internal data stored in the memory by the printing process is being performed in response to a print instruction received from the user interface, the printing is canceled by the cancellation process by receiving the cancellation instruction through the cancellation receiving process. Printing device.

2. The controller When a print job including a user name is received from the communication interface, the print job is stored in the memory without being printed based on the print job, and thereafter, when the user name is input from the user interface and the user logs in, the print processing is performed based on the stored print job. It is possible to perform After the login, when the cancel instruction is received by the cancellation receiving process during execution of printing based on the stored print job, and when the cancel instruction is received by the cancellation receiving process while printing of internal data stored in the memory is being performed in accordance with a print instruction received from the user interface, the printing by the printing process is canceled; When the internal data stored in the memory is being printed in response to a print instruction received from the communication interface, if a cancel instruction is received by the cancel receiving process, the printing by the print process is not canceled, When the cancel instruction is received by the cancellation receiving process while the print job including the user name is being received by the printing process, the reception of the print job is continued without being canceled. The printing device of claim 1 .

3. The controller the user interface is switchable between a first state indicating that the cancel instruction can be accepted and a second state indicating that the cancel instruction cannot be accepted, When printing by the printing process is being performed in response to a print instruction received from the communication interface, the user interface is set to the second mode, and the cancel instruction is made unacceptable, thereby preventing the printing from being canceled by the cancellation process and continuing the printing; When printing by the printing process is being performed in response to a print instruction received from the user interface, the user interface is set to the first mode and made capable of receiving the cancel instruction, thereby canceling the printing by the cancellation process upon receiving the cancel instruction. The printing device of claim 1 .

4. user authentication for authorizing instructions to the printing device is performed by an external device connected via the communication interface; The controller When printing by the printing process is being performed in response to a print instruction sent by the external device after the user authentication and received from the communication interface, if the cancel instruction is received by the cancellation receiving process, the printing is not canceled by the cancellation process and the printing continues. The printing device of claim 1 .

5. The controller transmitting the web page data for user authentication from the communication interface to the external device; receiving the web page data for user authentication, and when printing is being performed by the print processing in response to a print instruction that was sent by the external device after user authentication was performed from a web page displayed based on the web page data and that was received from the communication interface, if the cancel instruction is received by the cancellation receiving process, the printing is not canceled by the cancellation process and the printing continues. The printing device according to claim 4 .

6. The controller transmitting the print instruction web page data from the communication interface to the external device; receiving the web page data for the print instruction, and when printing is being performed by the print processing in accordance with the print instruction made from the web page displayed based on the web page data, which print instruction was sent by the external device and accepted from the communication interface, if the cancel instruction is accepted by the cancellation acceptance processing, the printing is not canceled by the cancellation processing and the printing continues. The printing device of claim 1 .

7. a communication interface; A user interface; Memory and A controller; A printing device comprising: The controller a receiving process for receiving a print job from the communication interface; The printing process, is executable, determining whether to cancel the print job being received by accepting a cancel instruction from the user interface during reception of the print job by the reception process based on a first condition; determining whether to cancel the printing by the printing process based on a second condition by accepting a cancel instruction from the user interface during the printing by the printing process; Printing device.

8. The printing device further comprises: display Equipped with The controller When the cancel instruction is received from the user interface and it is determined based on the first condition whether or not to cancel, a first display is displayed on the display; When the cancel instruction is received from the user interface and it is determined based on the second condition whether to cancel, the display is displayed in a second manner. The printing device according to claim 7.

9. A printing system including an information processing device and a printing device connected to the information processing device, The information processing device includes: a communication interface; A controller; Equipped with The controller A print instruction can be sent to the printing device from the communication interface; The printing device a communication interface; A user interface; Memory and A controller; Equipped with The controller of the printing device The printing process, a cancellation reception process for receiving, from the user interface, an instruction to cancel printing performed by the printing process; a cancellation process for canceling the printing in response to the cancellation instruction being accepted by the cancellation acceptance process; is executable, When the printing of the internal data stored in the memory by the printing process is being performed in response to a print instruction transmitted by the information processing device and received from the communication interface, the printing is continued without canceling the printing by the cancellation process due to the cancellation instruction being received by the cancellation receiving process, When the printing of the internal data stored in the memory by the printing process is being performed in response to a print instruction received from the user interface, the printing is canceled by the cancellation process by receiving the cancellation instruction through the cancellation receiving process. Printing system.

Images