printer

The printing device addresses the issue of memory interface disablement by using a controller to manage interface disabling, ensuring continued functionality through alternative storage methods or function disabling, thus maintaining seamless operation.

JP2024157263APending Publication Date: 2024-11-07BROTHER KOGYO KK
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2023071517
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-04-25
Publication Date
2024-11-07

AI Technical Summary

Technical Problem

Existing printing devices face issues when the memory interface of a portable memory is disabled, leading to adverse effects on the functionality and usability.

Method used

The printing device includes a controller that can specify the disabling of a specific interface via a user interface, allowing it to perform countermeasure processing to mitigate the adverse effects of disabling the memory interface, enabling continued use by switching to alternative storage methods or disabling the affected function.

Benefits of technology

The device can continue to function without adverse effects even when the memory interface is disabled, preventing malfunctions and ensuring seamless operation by switching to alternative storage options or disabling the affected function.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024157263000001_ABST
    Figure 2024157263000001_ABST
Patent Text Reader

Abstract

To provide a printer which enables continuous use without causing harmful effect even in a state that a memory interface of a portable type memory is invalidated.SOLUTION: A multifunction peripheral (MFP) 10 includes a plurality of interfaces. A controller 11 may receive a setting operation for invalidating a specific interface of the plurality of interfaces. The controller 11 performs handling processing for dealing with harmful effect on a function of storage print when receiving the setting operation for invalidating a memory interface 19.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 printing device having an interface. [Background technology]

[0002] Patent Document 1 describes a printing device equipped with multiple interfaces, including an interface related to a portable memory. [Prior art documents] [Patent documents]

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

[0004] The inventors have considered making it possible to set a specific interface to be enabled or disabled, and to continue to use the printing device with the specific interface set to disabled. However, it has been found that there is room for improvement in the operation of the printing device when the memory interface of a portable memory is disabled as a specific interface in the printing device.

[0005] The present invention has been made in consideration of the above problems, and aims to provide a printing device that can be used continuously without any adverse effects even when the memory interface of a portable memory is disabled. [Means for solving the problem]

[0006] In order to solve the above problems, the printing device disclosed in this embodiment includes a printer, a user interface, multiple interfaces, and a controller. The multiple interfaces include a memory interface to which a portable memory can be attached, and the controller is capable of storing acquired print data in the portable memory attached to the memory interface, and performing a first accumulated printing in which the printer prints the print data stored in the portable memory in response to an instruction received via the user interface. The controller is capable of designating the disablement of a specific interface among the multiple interfaces via the user interface, and is configured to execute a countermeasure process that is a process for dealing with adverse effects on the first accumulated printing when the disablement of the memory interface is designated via the user interface.

[0007] In the printing device having the above configuration, when the disablement of the memory interface is designated from among the multiple interfaces via the user interface, the controller executes a process for dealing with adverse effects on the first stored print. This makes it possible to suppress adverse effects on the first stored print that uses the memory interface even when the disablement of the memory interface is designated. Effect of the Invention

[0008] According to the present invention, it is possible to provide a printing device that can be used continuously without any adverse effects even when the memory interface of a portable memory is disabled. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a block diagram of an MFP. [Diagram 2] 11 is a timing chart illustrating a process executed between a controller and a browser. [Diagram 3] FIG. 2 is a diagram illustrating a Web page displayed in a browser. [Figure 4]FIG. 2 is a diagram illustrating a Web page displayed in a browser. [Diagram 5] 13 is a flowchart illustrating a processing procedure when an interface is disabled. [Figure 6] 13 is a flowchart illustrating a processing procedure when an interface is disabled. [Figure 7] FIG. 2 is a diagram illustrating management information. [Figure 8] FIG. 13 is a diagram illustrating a setting confirmation screen. [Figure 9] FIG. 13 is a diagram illustrating the state of the function “storage print.” [Figure 10] FIG. 13 is a diagram illustrating a copy confirmation screen. [Figure 11] 7 is a flowchart illustrating the procedure of a process executed in S24 of FIG. 6. [Figure 12] FIG. 13 is a diagram illustrating a data list screen. [Figure 13] 10 is a flowchart showing the procedure of a process executed by a controller when print data is received. [Figure 14] 11 is a flowchart illustrating a process procedure when a function "storage print" is executed. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] (First embodiment) The printing device according to this embodiment will be described using an MFP (abbreviation of multifunction peripheral) as an example. The MFP 10 shown in FIG. 1 is connected to a network and can communicate with a PC 70 through the network. The network is a LAN or the Internet. Note that the Internet may be connected wirelessly or by wire. The network may be a USB cable connecting the MFP 10 and the PC 70.

[0011] The MFP 10 comprises a controller 11, a main body memory 12, a printer 13, a FAX IF 14, a scanner 15, a user IF 16, a communication IF 17, and memory IFs 18 and 19. Each of these parts is connected to a bus and can communicate with each other. Note that "IF" is an abbreviation for Interface.

[0012] The user IF 16 is an interface between the user who directly operates the MFP 10 and the controller 11, and has, for example, a touch panel or operation keys which are physical keys. The communication IF 17 is an interface that connects the MFP 10 to a network. As described above, the communication IF 17 may be an interface that connects to a USB wiring. The printer 13 prints an image on a recording medium such as a sheet or a disk. The recording method of the printer 13 may be an inkjet method, an electrophotographic method, or the like. The MFP 10 may also be capable of executing a composite operation that combines a plurality of operations.

[0013] The memory IFs 18 and 19 are interfaces that perform communication in accordance with the USB (abbreviation for Universal Serial Bus) standard. The memory IFs 18 and 19 have ports 18A and 19A that are detachable from a USB memory 80. The USB standard is not particularly limited, but the USB 2.0 standard or the USB 3.0 standard may be adopted. The USB memory 80 may be a portable memory that is detachable from the MFP 10 via the ports 18A and 19A. For example, the USB memory 80 may be a HDD that can be connected via USB. For example, the memory IFs 18 and 19 may be a memory card that can communicate with the MFP 10 via a card reader that is USB-connected to the ports 18A and 19A. The memory IFs 18 and 19 may also have a card slot that is detachable from a memory card as the ports 18A and 19A.

[0014] In this embodiment, the port 18A of the memory IF 18 is located in the front part of the housing of the MFP 10, which is a part on the side where the user IF 16 is arranged. Specifically, when the side of the housing where the user IF 16 is arranged is the front side, the front part is a part including this front side and a front part of the side of the housing. In other words, the front part is a part where the user can easily see that the USB memory 80 is attached to the port 18A when the user is positioned facing the user IF 16 of the MFP 10. The port 19A of the memory IF 19 is located in the rear part of the housing of the MFP 10, which is an area on the opposite side to the front part when the user IF 16 is used as a reference. Specifically, the rear part can be said to be a part including the side opposite to the front part of the housing, that is, the back part, and the part of the side that contacts the front part and is not included in the front part. In other words, the rear portion is an area where it is difficult for a user to visually confirm that the USB memory 80 is attached to the port 19A while facing the user IF 16 of the MFP 10.

[0015] The controller 11 is configured with a CPU, an ASIC (an abbreviation for Application Specific Integrated Circuit), etc. The main body memory 12 is a so-called built-in memory built into the MFP 10, and may be configured by combining a RAM, a ROM, an SSD, an HDD, etc. Buffers provided in the controller 11 and used when various programs are executed may also be considered as part of the main body memory 12.

[0016] Note that the MFP 10 may include a storage medium readable by the controller 11 in addition to the main body memory 12. The storage medium readable by the controller 11 is a non-transitory medium. In addition to the above examples, the non-transitory medium also includes recording media such as CD-ROMs and DVD-ROMs. Furthermore, the non-transitory medium is also a tangible medium. On the other hand, an electrical signal carrying a program downloaded from a server on the Internet is a computer-readable signal medium, which is a type of computer-readable medium, but is not included in the non-transitory computer-readable storage medium.

[0017] The main memory 12 stores firmware as a program executable by the controller 11. In this embodiment, the process of the controller 11 according to the instructions written in the program is mainly shown. That is, the processes of the controller 11 such as "judging", "selecting", "calculating", "deciding", "identifying", "obtaining", "receiving", and "controlling" in the following description represent the processes of the controller 11. Note that "obtaining" is used as a concept that does not require a request. In other words, the process of the controller 11 receiving data without a request is also included in the concept of "the controller 11 obtaining data". In addition, "data" in this specification is represented by a bit string that can be read by the controller. Data with the same substantial meaning but different formats are treated as the same data. The same applies to "information" in this specification.

[0018] By executing the firmware, the controller 11 also functions as a web server for displaying a predetermined web page on the PC 70. The controller 11 transmits web page data for displaying the web page to the PC 70, thereby causing a browser 71 (described later) of the PC 70 to display the web page.

[0019] Next, the configuration of the PC 70 will be described. The PC 70 includes a communication IF, a memory, a controller, a display, and a user IF (not shown). An OS and a browser 71 are stored in the memory of the PC 70. The browser 71 is an abbreviation for a browser program. The controller of the PC 70 operates according to the browser 71 to display a Web page corresponding to Web page data transmitted from the MFP 10 on the display. In this embodiment, the Web page that the controller 11 displays on the browser 71 of the PC 70 as a Web server, and the PC 70 that displays this Web page are also examples of a user IF. The terminal is not limited to the PC 70, and may be a mobile terminal such as a smartphone, as long as it is a device that can perform wireless communication with the MFP 10 via a network.

[0020] Next, the procedure of the process for enabling / disabling various interfaces of MFP 10 will be described with reference to Fig. 2. In this embodiment, the enabling / disabling of various interfaces of MFP 10 is performed using the function of the Web server of controller 11. That is, controller 11 supplies Web page data to browser 71 to display a Web page shown in Fig. 4, which will be described later, and can accept operations for specifying whether various interfaces are enabled or disabled by operations on this Web page.

[0021] The user operates the PC 70 to input a URL for identifying the Web server of the MFP 10 into the browser 71. The browser 71 transmits a GET request of HTTPS communication including the input URL at timing 10 (hereinafter, timing will also be referred to as "T"). When the controller 11 receives the GET request from the browser 71, it transmits an HTTPS response corresponding to the GET request.

[0022] The response returned at T11 includes web page data for displaying the pre-login home screen shown in Fig. 3. Upon receiving the web page data, the browser 71 uses the web page data to display the pre-login home screen on the display at T12.

[0023] The home screen 30 shown in FIG. 3 includes a page display field 31 configured by a menu 32 and a content display section 33. The menu 32 displays options for receiving an operation to instruct display on the content display section 33. The home screen 30 may include a URL display field above the page display field 31 for displaying the URL of a registered site. This example shows a state in which a user selects an option "Status" 32A of the menu 32 on the home screen 30 before login. The option "Status" 32A is a sub-option of the option "Home", and is also an option corresponding to the current status of the MFP 10 and the display of the setting contents on the content display section 33. The content display section 33 includes a field for specifying whether "Automatic Refresh" is enabled "On" or disabled "Off" as the status of the MFP 10, a field for indicating the remaining toner capacity, a field for receiving the setting of the language to be displayed on the Web page, and the like.

[0024] When a selection operation is performed on any of the options in the menu 32, the browser 71 transmits a GET request requesting Web page data corresponding to the selected option to the controller 11. In response to the request, the controller 11 transmits a response including the Web page data to the PC 70. This allows the browser 71 to display a Web page corresponding to the selected item on the content display unit 33. Note that instead of a configuration in which the controller 11 transmits Web page data as a response to the browser 71, a configuration may be adopted in which the controller 11 transmits only data indicating a screen to be displayed on the content display unit 33 to the browser 71, and the browser 71 uses the data to change the display on the content display unit 33.

[0025] When the user inputs a password in the password input field 34 displayed in the menu 32 on the home screen 30 and operates the login icon 35, in T13 the browser 71 transmits a POST request including the login password to the controller 11. When the controller 11 receives the POST request including the login password, in T14 it performs an authentication process using the login password included in the POST request. In the authentication process executed in T14, the controller 11 determines whether or not the input password included in the POST request matches an administrator password that is a login password of an administrator registered in the MFP 10. The controller 11 compares the input password included in the POST request with the registered administrator password, and permits login to a Web server included in the MFP 10 if the two passwords completely match. In addition to this, the controller 11 may permit login to the MFP 10 if the input password and the administrator password partially match.

[0026] When the input password and the administrator password match as a result of the authentication process in T14, the controller 11 generates a response for when the authentication process is successful, and transmits the response to the MFP 10 in T15. This response includes Web page data for displaying a Web page, which is a home screen after the administrator logs in. When the browser 71 receives the response from the MFP 10, in T16, the browser 71 causes the user IF 16 to display a Web page, which is a home screen after the administrator logs in. Note that, even on the home screen after login, when a selection operation is performed on any of the menu options, the browser 71 transmits a GET request to the controller 11 in T17, which requests Web page data corresponding to the selected option. When the controller 11 receives the GET request, it transmits a response including the Web page data to the PC 70 in response to the GET request.

[0027] FIG. 4 shows the IF setting screen 40, which is a Web page that the browser 71 displays at T19 based on Web page data supplied by the controller 11 at T18 when the user selects the option "Connection Interface" 42A subordinate to the option "Administrator" in the menu 42.

[0028] In the IF setting screen 40, the content display section 43 includes items 43A, 43B, 43C, and 43D that accept enable / disable operations for various IFs "Wired LAN", "Wireless LAN", "USB Port (Front)", and "USB Port (Rear)". The item "Wired LAN" 43A is an item that accepts an instruction to enable / disable an IF related to a wired LAN included in the communication IF 17. The item "Wireless LAN" 43B is an item that accepts an instruction to enable / disable an IF related to a wireless LAN included in the communication IF 17. The item "USB Port (Front)" 43C is an item that accepts an instruction to enable / disable the memory IF 18. The item "USB Port (Rear)" 43D is an item that accepts an instruction to enable / disable the memory IF 19. In addition, if MFP 10 is equipped with an IF for connecting to a telephone line, or if communication IF 17 includes an IF for connecting to a USB wiring, IF setting screen 40 may include an item for receiving instructions to enable or disable these IFs.

[0029] When the user checks the check box "Enabled" included in each of items 43A to 43D on IF setting screen 40, the corresponding IF is enabled, and when the user checks the check box "Disabled," the corresponding interface is disabled. In this example, it is assumed that the user checks the check box "Disabled" for item "USB Port (Rear)" 43D included in content display section 43 of IF setting screen 40, checks the check boxes "Enabled" for the other items, and operates an approval button (not shown). Browser 71 transmits a POST request including information indicating that USBIF 19 has been disabled to MFP 10 at T20.

[0030] When the controller 11 receives a POST request including information indicating that the USBIF 19 is disabled among the multiple IFs, at T21, the controller 11 updates the contents of the setting information 20 stored in the main body memory 12. The setting information 20 is information that registers various functions that the MFP 10 can execute and the enabled / disabled setting states of the various IFs.

[0031] Next, the details of the process executed by the controller 11 at T21 will be described with reference to Figs. 5 and 6. At step 10 (hereinafter, "step" will be simply abbreviated as "S"), it is determined whether or not the administrator has already logged in. In this example, since the authentication process at T14 in Fig. 2 was successful and the administrator has already logged in (S10: YES), the process proceeds to S11. Note that if the administrator is not logged in, the controller 11 does not execute the processes following S11.

[0032] In S11, the controller 11 determines whether or not the POST request received from the PC 70 includes information instructing to disable the USBIF 19. In this example, since the POST request received from the PC 70 includes information specifying to disable the USBIF 19 (S11: YES), the controller 11 proceeds to S12. However, if the POST request from the PC 70 does not include information specifying to disable the USBIF 19 (S11: NO), the controller 11 ends the processing in FIG. 5.

[0033] In S12, the controller 11 refers to the setting information 20 and judges whether the function "storage print" is set to be valid. The function "storage print" is a function that accumulates and saves print data in the USB memory 80 attached to the port 19A, and causes the printer 13 to print the accumulated and saved print data in response to an operation on the user IF 16. If the function "storage print" is registered as valid in the setting information 20, the execution of the function "storage print" by the MFP 10 is permitted, whereas if the function "storage print" is registered as invalid, the execution of the function "storage print" by the MFP 10 is not permitted. In this embodiment, the description will be given on the assumption that the USB memory 80 attached to the port 19A is used in the function "storage print". In other words, the USBIF 18 and the port 18A are not used in the function "storage print".

[0034] First, it is assumed that the function "storage print" is registered as enabled in the setting information 20 (S12: YES), and the process proceeds to S13. In S13, the controller 11 determines whether or not the USB memory 80 is attached to the port 19A. Here, it is assumed that the USB memory 80 is attached to the port 19A (S13: YES), and the controller 11 proceeds to S14.

[0035] In S14, the controller 11 judges whether print data is stored in the USB memory 80 connected to the port 19A. The controller 11 judges whether print data is stored in the USB memory 80 by referring to the management information 21 stored in the main body memory 12. The USB memory 80 used in the function "storage print" stores the management information 21 shown in FIG. 7. In this management information 21, a record for each print data stored in the USB memory 80 is registered. In the record, values ​​"job name", "user name", "reception date and time", and "data name" are registered in association with each other. The value "job name" indicates the name of the job when the job including the print data is transmitted from the PC 70 to the MFP 10. The value "user name" is information indicating the user who executes the function "storage print". The value "reception date and time" is information indicating the date and time when the MFP 10 receives the job including the print data. The value "data name" is an identification name for managing the print data in the function "storage print". When management information 21 is stored in the USB memory 80 and one or more records are registered in the management information 21, the controller 11 determines that print data is accumulated and stored in the USB memory 80 connected to the port 19A.

[0036] First, the controller 11 will explain the case where print data is not stored in the USB memory 80 connected to the port 19A (S14: NO). In this case, the controller 11 proceeds to S15. In S15, the controller 11 causes the user IF 16 to display the setting confirmation screen 50 shown in Fig. 8. Note that in this embodiment, the controller 11 transmits Web page data for displaying a Web page corresponding to the setting confirmation screen 50 to the PC 70, thereby causing the browser 71 of the PC 70 to display the Web page corresponding to the setting confirmation screen 50.

[0037] FIG. 8 shows a setting confirmation screen 50 displayed on the browser 71. The setting confirmation screen 50 includes text suggesting to the user whether or not to change the storage print to disabled, a YES button 51, and a NO button 52. The YES button 51 is a button that is operated when the user instructs the MFP 10 to disable the function "storage print". The NO button 52 is a button that is operated when the user does not instruct the MFP 10 to disable the function "storage print", that is, when the user instructs the MFP 10 to enable the function "storage print". When the USBIF 19 is set to disabled, the controller 11 cannot access the USBIF 19 when executing the function "storage print", which may cause adverse effects. Therefore, in order to avoid such adverse effects, when the USBIF 19 is set to disabled, the controller 11 disables the function "storage print" or changes the save destination.

[0038] In this embodiment, it is possible to set three states shown in FIG. 9 for the function "storage print" according to whether the USBIF 19 is enabled or disabled. The states of the function "storage print" shown in FIG. 9 correspond to the registered contents of the setting information 20 stored in the main body memory 12. Specifically, there are three states related to the function "storage print", namely, "storage print disabled", "storage print enabled (save in main body memory)", and "storage print enabled (save in USB)". Of these, "storage print disabled" is the state when the function "storage print" is set to disabled. "storage print enabled (save in main body memory)" and "storage print enabled (save in USB)" are the states when the function "storage print" is set to enabled. The difference between the two states is whether the designated save destination of the print data is "main body memory" or "USB memory".

[0039] When the user operates the YES button 51 on the setting confirmation screen 50 to instruct to disable the function "storage print", the browser 71 transmits a POST request including information indicating that the function "storage print" is disabled to the MFP 10. When the controller 11 receives the POST request including information indicating that the function "storage print" is disabled (S16: YES), the process proceeds to S17, where the controller 11 sets the function "storage print" to be disabled in the setting information 20 stored in the main body memory 12. When setting the function "storage print" to be disabled, the controller 11 makes the function "storage print" inoperable by hiding the icon corresponding to the function "storage print" displayed on the user IF 16.

[0040] In S19, the controller 11 changes the setting of the USBIF 19 from enabled to disabled, and ends the processing in Fig. 5. Specifically, the controller 11 disables access to the USBIF 19 by stopping the supply of power to the IC chip constituting the USBIF 19. This makes it impossible for the controller 11 to communicate with the USBIF 19. In addition, even if the controller 11 has accepted an interrupt process from the USBIF 19 when the USBIF 19 is set to disabled, the controller 11 may disable the USBIF 10 by disabling the interrupt process.

[0041] If USBIF19 is disabled, the controller 11 will not be able to access the USB memory 80 via USBIF19. Therefore, adverse effects are suppressed by disabling the function "Storage Print" on the condition that an instruction to disable the function "Storage Print" is received from the user.

[0042] On the other hand, when the user operates the NO button 52 on the setting confirmation screen 50 (S16: NO), the controller 11 proceeds to S18 and sets the storage destination of the print data in the function "storage print" to the main memory 12. That is, the state of the function "storage print" is set to "storage print enabled (save in main memory)" shown in FIG. 9. In S19, the controller 11 changes the setting of the USBIF 19 from enabled "On" to disabled "Off". Then, the controller 11 ends the processing in FIG. 5. When the USBIF 19 is set to disabled, the controller 11 cannot access the USB memory 80 via the USBIF 19. Therefore, adverse effects are suppressed by changing the storage destination of the print data in the function "storage print" to the main memory 12 on the condition that an instruction to enable the function "storage print" is received from the user.

[0043] On the other hand, in S12, if the function "storage print" is registered as disabled in the setting information 20 (S12: NO), the controller 11 disables the USBIF 19 by the process in S19 already described. Also, in S13, if the USB memory 80 is not attached to the port 19A (S13: NO), the controller 11 proceeds to S17 and disables the function "storage print". Then, the controller 11 disables the USBIF 19 by the process in S19 already described.

[0044] In this embodiment, the function "storage print" when the destination for saving print data is designated as the USB memory 80 attached to the port 19A is an example of the first accumulated print. The function "storage print" when the destination for saving print data is designated as the main body memory 12 is an example of the second accumulated print.

[0045] On the other hand, if print data is stored in the USB memory 80 attached to the port 19A (S14: YES), disabling the USBIF 19 will prevent the user from accessing the print data stored in the USB memory 80. Therefore, the controller 11 executes the processes of S20 to S35 in FIG. 6 to suppress adverse effects caused by the inability to access the print data stored in the USB memory 80.

[0046] 6, the controller 11 causes the browser 71 of the PC 70 to display the copy confirmation screen 55 shown in Fig. 10. In this example, the controller 11 also causes the browser 71 to display a Web page corresponding to the copy confirmation screen 55 by transmitting Web page data for displaying the Web page corresponding to the copy confirmation screen 55 to the PC 70. The copy confirmation screen 55 includes text for confirming whether or not the user wants to copy (store) the print data stored in the USB memory 80 to the main body memory 12, a YES button 56, and a NO button 57.

[0047] When the user operates the YES button 56 on the copy confirmation screen 55 to instruct saving of the print data accumulated and saved in the USB memory 80 to the main body memory 12, the browser 71 transmits to the MFP 10 a POST request including information indicating saving of the print data to the main body memory 12. When the controller 11 receives the POST request (S21: YES), it proceeds to S22 and acquires the amount of data stored in the USB memory 80 by the function "storage print".

[0048] In S23, the controller 11 determines whether or not the amount of data acquired in S22 exceeds the free space of the main body memory 12. If the amount of data in the USB memory 80 does not exceed the free space of the main body memory 12 (S23: NO), the controller 11 proceeds to S25 and copies the print data stored in the USB memory 80 and the management information 21 that manages this print data to the main body memory 12. By copying the management information 21 to the main body memory 12, the controller 11 can thereafter access the main body memory 12 and use the management information 21 when executing the function "storage print".

[0049] In S26, the controller 11 causes the user IF 16 to display a data deletion confirmation screen for confirming with the user whether or not to delete the copied print data stored in the USB memory 80. The data deletion confirmation screen includes text for confirming with the user whether or not to delete the print data stored in the USB memory 80, a YES button, and a NO button. When the user operates the YES button on the data deletion confirmation screen, the browser 71 transmits a POST request including information indicating that the print data is to be deleted to the MFP 10. When the controller 11 receives the POST request including information indicating that the print data is to be deleted (S27: YES), the controller 11 proceeds to S28 and deletes the print data accumulated and stored in the USB memory 80. In S29, the controller 11 deletes the management information 21 accumulated and stored in the USB memory 80.

[0050] In S30, the controller 11 changes the destination for saving print data in the function "storage print" to the main body memory 12. In S31, the controller 11 disables the USBIF 19 by processing similar to that of S19 already described. When the USBIF 19 is disabled, the controller 11 suppresses adverse effects by changing the destination for saving print data in the function "storage print" from the USB memory 80 to the main body memory 12, on condition that an instruction to enable the function "storage print" is received from the user.

[0051] When the user operates the NO button on the data deletion confirmation screen (S27: NO), the controller 11 proceeds to S30, and as already described, changes the destination for saving print data in the function "storage print" to the main body memory 12. Then, the controller 11 sets the USBIF 19 to disabled in S31. That is, in this example, when the USBIF 19 is set to disabled, the copied print data saved in the USB memory 80 is not deleted, and the destination for saving print data in the function "storage print" is changed from the USB memory 80 to the main body memory 12.

[0052] Returning to S23 in FIG. 6, if the amount of data stored in the USB memory 80 exceeds the free space in the main body memory 12 (S23: YES), the controller 11 proceeds to S24 and executes processing for the case where all of the print data stored in the USB memory 80 cannot be copied.

[0053] 11 is a flowchart explaining the procedure of the process executed by the controller 11 in S24. In S40, the controller 11 transmits Web page data for displaying a data selection confirmation screen, which is a Web page, to the browser 71 of the PC 70. The data selection confirmation screen is a Web page for allowing the user to select whether or not to copy only specific data from the print data accumulated and saved in the USB memory 80.

[0054] When the user performs an instruction operation to copy only specific data on the data selection confirmation screen displayed on the user IF 16 (S41: YES), the controller 11 proceeds to S42 and displays a data list screen 58 shown in FIG. 12. The data list screen 58 includes a selection field 59 that accepts a selection operation for print data accumulated and saved in the USB memory 80. In each selection field 59, a value "data name" related to the print data registered in the management information 21 is displayed. For example, in the data list screen 58 shown in FIG. 12, the selection field 59A corresponds to the print data identified by the data name "data001" which is a value stored in the management information 21. The selection field 59B corresponds to the print data identified by the data name "data002" which is a value stored in the management information 21. When the user checks the check box of the selection field 59A or the check box of the selection field 59B, the print data identified by the data name of the selection field 59 among the print data stored in the USB memory 80 is designated as the target to be copied to the main body memory 12. It should be noted that, on the data list screen 58, it is also possible to display other selection fields 59 by operating the scroll button.

[0055] When the user operates the OK button 60 on the data list screen 58, the browser 71 sends a post request including information indicating the print data selected as the target for copying on the data list screen 58 to the MFP 10. When the controller 11 of the MFP 10 receives the post request including information indicating the print data to be copied (S43: YES), the process proceeds to S44, and the controller 11 copies, from the print data accumulated and saved in the USB memory 80, the print data selected on the data list screen 58 to the main body memory 12.

[0056] In S45, the controller 11 transmits to the PC 70 Web page data for displaying on the browser 71 a data deletion confirmation screen for confirming with the user whether or not to delete the print data copied to the main body memory 12 among the print data stored in the USB memory 80. The data deletion confirmation screen displayed in S45 is a Web page that can accept the selection of the print data to be deleted among the print data stored in the USB memory 80. When the browser 71 accepts an operation indicating that the print data is not to be deleted on the data deletion confirmation screen, the browser 71 transmits to the MFP 10 a POST request including information indicating that the print data copied to the main body memory 12 among the print data stored in the USB memory 80 is not to be deleted. When the controller 11 receives this POST request (S46: NO), the process proceeds to S30 in FIG. 6. That is, the controller 11 proceeds to S30 without deleting the print data stored in the USB memory 80.

[0057] On the other hand, when the browser 71 accepts a selection operation of the print data to be deleted on the data deletion confirmation screen, the browser 71 transmits a POST request including information indicating the print data to be deleted to the MFP 10. When the controller 11 receives this POST request (S46: YES), the process proceeds to S47. In S47, the controller 11 transmits to the PC 70 Web page data for displaying a data deletion confirmation screen that accepts an instruction as to whether or not to delete the print data that has not been copied to the main body memory 12 among the print data accumulated and stored in the USB memory 80. When the browser 71 of the PC 70 accepts a selection operation of deleting the print data that has not been copied to the main body memory 12 on the data deletion confirmation screen displayed by the process in S47, the browser 71 transmits to the MFP 10 a POST request including information indicating the deletion of all the print data accumulated and stored in the USB memory 80. When the controller 11 receives this POST request (S48: YES), the process proceeds to S49, where the controller 11 deletes all the print data accumulated and stored in the USB memory 80. The controller 11 erases all of the management information 21 stored in the USB memory 80 in S50.

[0058] On the other hand, if the browser 71 of the PC 70 does not accept a selection operation for erasing the print data that has not been copied to the main body memory 12 from among the print data stored in the USB memory 80 on the data erasure confirmation screen displayed by the process in S47, the browser 71 of the PC 70 sends to the MFP 10 a POST request including information indicating that only the print data copied to the main body memory 12 is to be erased. When the controller 11 of the MFP 10 receives the POST request (S48: NO), the process proceeds to S51, where it erases only the print data that has been copied to the main body memory 12 from among the print data stored in the USB memory 80. In S52, the controller 11 erases only the records related to the print data erased in S51 from the management information 21 stored in the USB memory 80.

[0059] 6, in S30, as already described, the controller 11 changes the save destination of the print data in the function "storage print" to the main body memory 12. Then, in S31, as already described, the controller 11 sets the USBIF 19 to be disabled.

[0060] Returning to S21 in FIG. 6, if the controller 11 receives a POST request from the PC 70 including information indicating that the print data stored in the USB memory 80 should not be copied to the main body memory 12 (S21: NO), the controller 11 proceeds to S32.

[0061] In S32, the controller 11 transmits to the PC 70 Web page data for displaying a data deletion confirmation screen for confirming with the user whether or not to delete the print data accumulated and stored in the USB memory 80. The data deletion confirmation screen has already been described in S26. When the controller 11 receives from the browser 71 a POST request including information for deleting all print data accumulated and stored in the USB memory 80 (S33: YES), the controller 11 proceeds to S34 and deletes all print data accumulated and stored in the USB memory 80. In S35, the controller 11 deletes all values ​​from the management information 21 stored in the USB memory 80. Note that when the controller 11 receives from the browser 71 a POST request including information indicating that the print data accumulated and stored in the USB memory 80 is not deleted (S33: NO), the controller 11 proceeds to S15 in FIG. 5 without deleting the print data accumulated and stored in the USB memory 80.

[0062] In S15 of FIG. 5, the controller 11 transmits to the PC 70 Web page data for displaying the setting confirmation screen 50 on the browser 71. The setting confirmation screen 50 has already been described with reference to FIG. 8. As already described, when the controller 11 receives a POST request including information specifying the function "storage print" to be disabled from the PC 70 (S16: YES), the controller 11 registers the function "storage print" as disabled in the setting information 20 in S17. On the other hand, as already described, when the controller 11 receives a POST request including information specifying the function "storage print" to be enabled from the PC 70 (S16: NO), the controller 11 sets the function "storage print" to be enabled in the setting information 20 in S18, and changes the save destination of the print data to the main body memory 12. In S19, the controller 11 changes the USBIF 19 from enabled to disabled, and ends the process of FIG. 5.

[0063] In this embodiment, the processes executed by the controller 11 in S17 and S18 in FIG. 5 and the processes executed in S24, S25 to S31, S34, and S35 in FIG. 6 are examples of handling processes.

[0064] Next, the procedure of the process when the MFP 10 receives print data (job data) including print data will be described with reference to Fig. 13. In S60, the controller 11 determines whether the function "storage print" is set to active. As described above, the controller 11 refers to the setting information 20 stored in the main body memory 12 to determine whether the function "storage print" is registered as active.

[0065] First, a case will be described in which the memory IF 19 is set to be disabled and the function "storage print" is set to be disabled in the setting information 20. Since the function "storage print" is set to be disabled (S60: NO), the controller 11 proceeds to S61 and executes RIP processing on the received print data. The controller 11 rasterizes the PDL data included in the print data by the RIP processing executed in S61, thereby converting the print data into data that can be processed by the printer 13. In S62, the controller 11 causes the printer 13 to print the converted print data. That is, since the function "storage print" is disabled, the controller 11 cannot access the USB memory 80, and therefore the print data is output by printing without being stored in the USB memory 80 or the main body memory 12. Then, the controller 11 ends the processing of FIG. 13.

[0066] On the other hand, if the function "storage print" is enabled (S60: YES), the controller 11 proceeds to S63, where it determines whether the save destination of the print data is set to a USB memory by referring to the setting information 20. If an affirmative decision is made in S63, it proceeds to S64, where it determines whether a USB memory 80 is attached to port 19A. If it determines that a USB memory 80 is attached to port 19A (S64: YES), the controller 11 proceeds to S65, where it compresses and then encrypts the received print data.

[0067] In S67, the controller 11 determines whether the free space of the USB memory 80 is greater than the amount of encrypted print data. If the free space of the USB memory 80 is equal to or greater than the amount of encrypted print data (S67: YES), the controller 11 proceeds to S70 and accumulates and stores the encrypted print data in the USB memory 80. In S71, the controller 11 reads and decrypts the management information 21 stored in the USB memory 80, and additionally registers a record related to the currently received print data in the decrypted management information 21. Note that the management information 21 has already been described. Then, the controller 11 ends the processing of FIG. 13.

[0068] On the other hand, if the free space in the USB memory 80 is less than the amount of encrypted print data (S67: NO), the controller 11 proceeds to S68 and notifies a storage full error indicating that the free space in the USB memory 80 is insufficient. In S69, the controller 11 erases the encrypted print data and ends the processing in Fig. 13. Note that instead of erasing the print data in S69, the encrypted print data may be stored in the main body memory 12 in response to an instruction from the user. Alternatively, the encrypted print data may be printed by the printer 13.

[0069] On the other hand, if the USB memory 80 is not attached to the port 19A (S64: NO), the controller 11 notifies in S66 a non-connection error indicating that the USB memory 80 is not attached to the port 19A. Then, in S69, the controller 11 erases the encrypted print data, and ends the processing in FIG.

[0070] Next, a case will be described where the function "storage print" is enabled, but the storage destination of the print data is set to the main body memory 12. In this case, the memory IF 19 is disabled by the process described in FIG. 5 and FIG. 6. Since the storage destination of the print data is set to the main body memory 12 (S63: NO), the controller 11 proceeds to S72 and executes the RIP process already described on the print data. The controller 11 accumulates and saves the print data converted by the RIP process in the main body memory 12 set as the storage destination. In S74, the controller 11 registers a value related to the newly accumulated and saved print data in the management information 21 already copied to the main body memory 12, and ends the process of FIG. 13.

[0071] Next, the procedure of the process when the user operates the user IF 16 of the MFP 10 and the controller 11 executes the function "storage print" will be described with reference to Fig. 14. As already described, when the USBIF 19 is set to disabled, the controller 11 cannot execute the function "storage print". Therefore, the controller 11 executes the process shown in Fig. 14 when the function "storage print" is enabled and the destination for saving the print data is set to the USB memory 80 or the main body memory 12.

[0072] In S80, the controller 11 refers to the setting information 20 and determines whether or not the destination to save the print data is set to the USB memory 80. If "Storage print enabled (USB save)" described with reference to FIG. 9 is set in the setting information 20, the controller 11 determines that the destination to save the print data is set to the USB memory 80 (S80: YES), and proceeds to S82. In S82, the controller 11 determines whether or not the USB memory 80 is attached to the port 19A. If the controller 11 determines that the USB memory 80 is not attached to the port 19A (S82: NO), in S90, the controller 11 notifies the non-connection error already described in S66. Then, the controller 11 ends the processing of FIG. 14.

[0073] On the other hand, if the controller 11 determines that the USB memory 80 is attached to the port 19A (S82: YES), the process proceeds to S83, where it decrypts and reads out the management information 21 stored in the USB memory 80. If the controller 11 determines in S84, based on the value registered in the management information 21, that print data is stored in the USB memory 80 (S84: YES), the process proceeds to S85. Because the destination for storing the print data is the USB memory 80 (S85: YES), the controller 11 proceeds to S87, where it decrypts the print data accumulated and stored in the USB memory 80, and causes the printer 13 to execute the print process using the decrypted print data.

[0074] In S88, the controller 11 deletes the print data used for printing in S86 from the USB memory 80. In S89, the controller 11 updates the management information 21 by deleting the record related to the print data used for printing in S86 from the management information 21 stored in the USB memory 80. The controller 11 returns to S84, and if there is print data that has not been printed among the print data specified by the operation for the function "storage print" (S84: YES), the controller 11 executes the processes of S85 to S89 again. If the controller 11 determines that there is no print data that has not been printed remaining in the USB memory 80 (S84: NO), the process of FIG. 14 ends.

[0075] On the other hand, if "storage print enabled (main body memory storage)" is set in the setting information 20, the controller 11 determines that the storage destination of the print data is set to the main body memory 12 (S80: NO), and proceeds to S81. The controller 11 decrypts and reads out the management information 21 stored in the main body memory 12.

[0076] As already explained, in S84, the controller 11 determines from the value registered in the management information 21 that the print data is stored in the main body memory 12 (S84: YES), and proceeds to S85. Because the storage destination of the print data is the main body memory 12 (S85: NO), the controller 11 proceeds to S86, where it decrypts the print data accumulated and stored in the main body memory 12, and causes the printer 13 to execute printing using the decrypted print data.

[0077] In S88, the controller 11 deletes the print data used in the printing in S86 from the main body memory 12. In S89, the controller 11 updates the management information 21 by deleting records related to the print data used in the printing in S86 from the management information 21 stored in the main body memory 12.

[0078] The present embodiment described above can provide the following advantages. The controller 11 of the MFP 10 can execute the function "storage print." The controller 11 can specify the disabling of a specific IF among multiple IFs via the user IF 16, and executes processing to deal with adverse effects on the function "storage print" when the disabling of the USBIF 19 is specified. This makes it possible to suppress adverse effects on the function "storage print" even when the disabling of the USBIF 19 is specified.

[0079] When the user specifies disabling of the USBIF 19, if the function "storage print" is set to enabled, the controller 11 sets the function "storage print" to disabled. As a result, since the function "storage print" is disabled when the USBIF 19 is disabled, it is possible to prevent, for example, the user from continuing to use the function "storage print" and erroneously recognizing the inability to access the USB memory 80 due to the disabling of the USBIF 19 as a malfunction of the MFP 10.

[0080] The controller 11 displays a screen suggesting to disable the function "storage print" on the user IF 16, and disables the function "storage print" in response to an operation corresponding to the screen. This allows the function "storage print" to be enabled or disabled in response to an operation by the user when the USBIF 19 is disabled.

[0081] When the controller 11 has disabled the USBIF 19, it can execute the function "storage print" of storing and saving print data in the main body memory 12. This makes it possible to avoid a situation in which the function "storage print" cannot be executed due to the USBIF 19 being disabled, and thus to suppress adverse effects.

[0082] When the controller 11 disables the function "storage print", it outputs or erases the print data stored in the USB memory 80. As a result, the USBIF 19 is disabled and before access to the USB memory 80 becomes impossible, the data stored in the USB memory 80 is output, thereby suppressing adverse effects caused by being unable to access the data stored in the USB memory 80.

[0083] When the USBIF 19 is disabled, the controller 11 copies the print data stored in the USB memory 80 to the main body memory 12. This allows the controller 11 to access the data from the main body memory 12 even after the controller 11 is no longer able to access the USB memory 80.

[0084] The controller 11 causes the browser 71 to display a screen suggesting that the print data be copied to the main body memory 12, and in response to an operation corresponding to this screen, copies the print data accumulated and saved in the USB memory 80 to the main body memory 12. This makes it possible to switch between copying the print data to the main body memory 12 and not copying, reflecting the user's intention.

[0085] After setting the main body memory 12 as the storage destination for the print data, the controller 11 uses the function "storage print" to print the print data copied from the USB memory 80 to the main body memory 12 together with the print data stored in the main body memory 12. This makes it possible to prevent the print data that has already been stored from becoming unable to be printed due to the memory IF 19 being disabled.

[0086] When the free space in the main memory 12 is insufficient, the controller 11 causes the browser 71 to display a screen for selecting print data to be copied to the main memory 12, and copies the selected print data to the main memory 12 in accordance with operations on the screen for selecting print data. This allows the print data that the user considers necessary to be copied to the main memory 12 and used for subsequent processing, even in situations where the free space in the main memory 12 is insufficient.

[0087] The controller 11 accepts an operation indicating whether or not to leave in the USB memory 80 the print data that was not selected as the print data to be copied to the main body memory 12 via a Web page displayed on the browser 71, and leaves or deletes the print data in the USB memory 80 according to the accepted operation. In this way, when the storage capacity of the main body memory 12 is insufficient, the user can select whether to leave in the USB memory 80 or delete the print data that is not copied to the main body memory 12.

[0088] When print data is stored in the USB memory 80 attached to the port 19A, the controller 11 erases the print data stored in the USB memory 80. After the USBIF 19 is disabled, the print data stored in the USB memory 80 is less likely to be used, so by erasing this print data, the free space of the USB memory 80 can be increased and used more effectively.

[0089] (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. The MFP 10 may be configured without the USBIF 18 and the port 18A. The MFP 10 may be configured to use a USB memory 80 attached to port 18A as a portable memory to be used with the function "storage print." In this case, when the check box "Disabled" is checked for the item "USB Port (Front)" 43C on the IF setting screen 40 shown in Fig. 4, the browser 71 of the PC 70 sends a POST request including information indicating that the user IF 16 is disabled to the MFP 10 at T20. When the controller 11 of the MFP 10 receives the POST request, it sets whether the function "storage print" is enabled or disabled, and further sets the destination to save the print data if the function is enabled, according to the processes shown in Figs. 5 and 6.

[0090] In the above embodiment, when the memory IF 19 is disabled, the user's operation can change the destination for saving print data by the function "storage print" to the main body memory 12. Alternatively, when the memory IF 19 is disabled, the controller 11 can set the destination for saving print data by the function "storage print" to a server connected to the network in response to a user's operation.

[0091] When the memory IF 19 is set to disabled, if print data is stored in the USB memory 80, the controller 11 enables copying to the main body memory 12. Alternatively, when the memory IF 19 is set to disabled, the controller 11 may disable copying to the main body memory 12 even if print data is stored in the USB memory 80. In this case, S14 in FIG. 5 and the process in FIG. 6 are omitted. When the memory IF 19 is set to disabled, if print data is accumulated and stored in the USB memory 80 (S14: YES in FIG. 5), the controller 11 may cause the printer 13 to print the print data accumulated and stored in the USB memory 80 in S25 (FIG. 6) and S44 (FIG. 11).

[0092] The controller 11 may uniformly disable the function "storage print" when the memory IF 19 is disabled. In this case, when the USB IF 19 is disabled in S11 of Fig. 5 (S11: YES), the controller 11 proceeds to S17 after going through the processes of S12 to S14, and disables the function "storage print". In this case, the processes of S15 and S16 are omitted.

[0093] In the above-described embodiment, the controller 11, using its function as a Web server, displays a Web page on the browser 71 of the PC 70 and accepts a user's operation to enable or disable the USBIF 19. Alternatively, the controller 11 may display, on the user IF 16, a screen for accepting a user's operation to enable or disable the USBIF 19, and accept a user's operation to enable or disable the USBIF 19 in response to an operation on this screen.

[0094] The printing device is not limited to the MFP 10, but may be a device equipped with only the printer 13. [Explanation of symbols]

[0095] 10...MFP, 11...controller, 12...main body memory, 13...printer, 16...user IF, 19...memory IF, 70...PC, 71...browser

Claims

1. A printer; A user interface; Multiple interfaces and A controller; Equipped with the plurality of interfaces includes a memory interface to which a portable memory can be attached; The controller: a first storage printing process is executed in which the acquired print data is stored in the portable memory attached to the memory interface, and the print data stored in the portable memory is printed by the printer in response to an instruction received via the user interface; The controller: via the user interface, it is possible to specify disabling of a specific interface among the plurality of interfaces; A printing device characterized in that it is configured to execute a countermeasure process, which is a process for dealing with adverse effects on the first stored printing, when the disablement of the memory interface is specified via the user interface.

2. The controller: The printing device according to claim 1, characterized in that, when the memory interface is specified to be disabled, if the first accumulated printing is set to enabled, the countermeasure processing is to disable the execution of the first accumulated printing.

3. The controller: The printing device according to claim 2, characterized in that, as the countermeasure processing, a screen suggesting that the first accumulated printing be disabled is displayed on the user interface, and the first accumulated printing is set to disabled in response to an operation corresponding to the screen.

4. A built-in memory is provided in the printing device, The controller, as the handling process, The first storage printing is set to be invalid, and the acquired print data is stored in the built-in memory; The printing device according to claim 2, further comprising a configuration for storing acquired print data in the built-in memory, and enabling a second stored printing mode in which the print data stored in the built-in memory is printed by the printer in response to an instruction via the user interface.

5. The controller: The printing device according to claim 2, characterized in that, as the countermeasure processing, when the execution of the first accumulated printing is set to be disabled, the printing device is configured to output or erase the data stored in the portable memory.

6. A built-in memory is provided in the printing device, 6. The printing device according to claim 5, wherein the controller is configured to copy print data stored in the portable memory to the built-in memory as an output of the data stored in the portable memory.

7. The controller: The printing device according to claim 6, characterized in that, as the response process, a screen is displayed on the user interface suggesting that print data be copied to the built-in memory, and the print data stored in the portable memory is copied to the built-in memory in response to an operation corresponding to the screen.

8. A built-in memory is provided in the printing device, The controller, as the handling process, setting the first stored printing to be invalid, and copying the acquired print data from the portable memory to the built-in memory; a second storage printing mode is enabled for storing the acquired print data in the built-in memory and printing the print data stored in the built-in memory by the printer in response to an instruction via the user interface; The controller: The printing device according to claim 6, characterized in that after the second accumulated printing is enabled, the print data copied from the portable memory to the built-in memory is printed using the second accumulated printing together with the print data accumulated in the built-in memory.

9. The controller: As the countermeasure processing, management information that is stored in the portable memory and is used in the first storage printing is copied to the built-in memory; The controller: The printing device according to claim 8, characterized in that the management information copied from the portable memory to the built-in memory is used to print the second stored printing together with the print data stored in the built-in memory.

10. The management information is This is information associated with each piece of print data, 10. The printing device according to claim 9, further comprising at least one of information for identifying the corresponding print data and authentication information used when printing the corresponding print data.

11. The controller: As the countermeasure processing, If the storage capacity of the built-in memory is insufficient, a screen for selecting print data to be copied to the built-in memory is displayed on the user interface; 7. The printing device according to claim 6, further comprising a configuration in which the selected print data is copied to the built-in memory in accordance with an operation on a screen for selecting the print data.

12. The controller: The printing device according to claim 11, characterized in that, as the handling process, an operation indicating whether or not to leave the print data that was not selected as print data to be copied to the built-in memory in the portable memory via the user interface is accepted, and the print data is left in the portable memory or erased in accordance with the accepted operation.

13. The controller, as the handling process, 6. The printing device according to claim 5, further comprising a configuration in which, when print data is stored in the portable memory attached to the memory interface, the data stored in the portable memory is erased.

14. The controller: displaying a screen showing the content of the handling process on the user interface; 2. The printing device according to claim 1, wherein the printing device is configured to be capable of executing the countermeasure process shown on the screen in accordance with an operation on the displayed screen.

15. Equipped with a communication interface, The controller is capable of communicating with a terminal via the communication interface; The controller: The terminal is capable of functioning as a web server that transmits web page data for displaying a predetermined web page to a browser in response to an instruction from the browser, 15. The printing apparatus according to claim 14, wherein the controller is configured to cause the browser to display a Web page as the user interface.

Citation Information

Patent Citations

  • Blowout port unit

    JP2023015685A