JP2019162787A - Information processing device, information processing system, screen display method, and program - Google Patents

Abstract

To rapidly switch a screen at occurrence of an error and cancellation of the error.SOLUTION: An information processing device includes: a body having at least one or more functions; and an operation unit that is operated by a user to execute control to the functions. The operation unit includes error management means for generating and displaying an error screen based on error information that is notified from the body based on the condition that an error occurs in the functions.SELECTED DRAWING: Figure 6

Description

  The present invention relates to an information processing apparatus, an information processing system, a screen display method, and a program.

  2. Description of the Related Art Conventionally, there has been known a multifunction peripheral that generates error image data including error information and displays it on an operation panel when an error occurs.

  In recent years, a multi-function peripheral has been developed that includes an operation unit equipped with a CPU and basic software (OS), and a main unit having an image forming function such as printing / scanning (see Patent Document 1). .

  In a multi-function machine configured with such an operation unit and main body, when an error occurs, the mechanism of the conventional multi-function machine is followed, and the main body generates error image data and transmits it to the operation unit. Then, the operation unit displays a conventional error screen to the user using an application (application) having an emulator function installed in the operation unit.

  However, in a multi-function peripheral that includes an operation unit and a main unit, for example, image data is exchanged between the main unit and the operation unit, and the image data needs to be emulated. For this reason, there is a problem that it takes time to switch the screen when an error occurs and the responsiveness is poor.

  The present invention has been made in view of the above, and an object of the present invention is to quickly switch screens when an error occurs.

  In order to solve the above-described problems and achieve the object, the present invention provides an information processing apparatus including a main body having at least one function and an operation unit operated by a user to execute control on the function. The operation unit includes an error management unit that generates and displays an error screen based on error information notified from the main body on condition that an error has occurred in the function.

  According to the present invention, it is possible to quickly switch screens when an error occurs.

FIG. 1 is a hardware configuration diagram of the MFP according to the embodiment. FIG. 2 is a diagram illustrating an example of the software configuration of the MFP. FIG. 3 is a diagram illustrating an example of software provided in the MFP. FIG. 4 is a functional block diagram of the error management application. FIG. 5 is a diagram illustrating an example of the screen generation table. FIG. 6 is a sequence diagram showing the flow of operation of each unit when an error occurs. FIG. 7 is a diagram illustrating an example of an error screen when a plotter jam occurs. FIG. 8 is a diagram illustrating an example of screen transition at the time of error resolution. FIG. 9 is a sequence diagram showing the flow of operation of each unit when the error is resolved.

  Exemplary embodiments of an information processing apparatus, an information processing system, a screen display method, and a program will be described below in detail with reference to the accompanying drawings.

  FIG. 1 is a hardware configuration diagram of a MFP (Multifunction Peripheral) 1 according to the embodiment. The MFP 1 is an example of an information processing apparatus. As shown in FIG. 1, the MFP 1 includes a main body 10 that is an image processing unit having various image processing functions such as a copy function, a scanner function, a facsimile function, and a printer function, and an operation for receiving an input corresponding to a user operation. Part 20.

  The main body 10 and the operation unit 20 are connected via a dedicated communication path 30 so that they can communicate with each other. The communication path 30 may be, for example, a USB (Universal Serial Bus) standard. The communication path 30 may be of any standard regardless of wired or wireless. Further, the main body 10 may have one function or a plurality of functions among image forming functions such as a copy function, a scanner function, a facsimile function, and a printer function.

  As the operation unit 20, an electronic device capable of executing complete information processing independently can be used. As an example, an information processing terminal such as a smartphone or a tablet terminal can be used as the operation unit 20. In this case, the information processing terminal used as the operation unit 20 functions as the operation unit of the MFP 1.

  More specifically, conventionally, a dedicated operation panel is fixed and installed as an operation unit in the MFP 1. In contrast, the information processing terminal used as the operation unit 20 of the MFP 1 according to the first embodiment can be attached to and detached from the main body 10 of the MFP 1. That is, the information processing terminal used as the operation unit 20 can be removed from a predetermined position such as a position where the operation panel of the MFP 1 is disposed (separable), but can be installed integrally with the MFP 1. ing. Therefore, the information processing terminal and the MFP 1 used as the operation unit 20 are grasped as a single device. When the information processing terminal used as the operation unit 20 is removed from the MFP 1, the information processing terminal performs wireless communication such as Bluetooth (registered trademark) or infrared communication with the MFP 1 and functions as an operation unit of the MFP 1.

  The main body 10 performs an operation according to the input received by the operation unit 20. The main body 10 can also communicate with an external device such as a client PC (personal computer), and performs an operation according to an instruction received from the external device.

(Hardware configuration of the main unit)
Next, the hardware configuration of the main body 10 will be described. As shown in FIG. 1, the main body 10 includes a CPU (Central Processing Unit) 11, a ROM (Read Only Memory) 12, a RAM (Random Access Memory) 13, and an HDD (Hard Disk Drive) 14. The main body 10 includes a communication I / F (Interface) 15, a connection I / F 16, an engine 17, and a facsimile modem (FAX modem) 19. The units 11 to 17 and the FAX modem 19 are connected to each other via a system bus 18.

  The CPU 11 comprehensively controls the operation of the main body 10. The CPU 11 controls the overall operation of the main body 10 by executing a program stored in the ROM 12 or the HDD 14 or the like using the RAM 13 as a work area (work area), and the above-described copy function, scanner function, facsimile function, printer function, etc. Various image forming functions are realized. The HDD 14 of the main body 10 can be similarly realized even if a flash memory is used.

  The communication I / F 15 is an interface for communicating with an external device such as a client PC (Personal Computer), a Web server device, or an authentication server device on the network 40. The connection I / F 16 is an interface for communicating with the operation unit 20 via the communication path 30. 1 and FIG. 2 described below, the communication path 30 is illustrated in a wired manner, but the operation unit 20 can be attached to and detached from the main body 10 of the MFP 1 as described above. ing. Therefore, it is understood that the communication path 30 functions as a wired communication path when the operation unit 20 is attached to the MFP 1, and the communication path 30 functions as a wireless communication path when the operation unit 20 is detached from the MFP 1. I want.

  The engine 17 is hardware that performs general-purpose information processing and processing other than communication for realizing a copy function, a scanner function, a facsimile function, a printer function, and the like. The engine 17 includes, for example, a scanner that scans and reads an image of a document, a plotter that performs printing on a sheet material such as paper, and a facsimile communication unit that performs facsimile communication. Further, a specific option such as a finisher for sorting printed sheet materials and an ADF (Auto Document Feeder) for automatically feeding a document may be provided.

(Hardware configuration of operation unit)
Next, the hardware configuration of the operation unit 20 will be described. As shown in FIG. 1, the operation unit 20 includes a CPU 21, a ROM 22, a RAM 23, a flash memory 24, a communication I / F 25, a connection I / F 26, an operation panel 27, and an IC card I / F 29. These are connected to each other via a system bus 28. It should be noted that the flash memory 24 of the operation unit 20 can be similarly realized using an HDD.

  The CPU 21 comprehensively controls the operation of the operation unit 20. The CPU 21 controls the operation of the entire operation unit 20 by executing a program stored in the ROM 22 or the like using the RAM 23 as a work area (work area). Further, the CPU 21 performs a user authentication process by executing a user authentication program stored in the ROM 22 or the like. The communication I / F 25 is an interface for communicating with the server device 60 on the network 40, for example. The connection I / F 26 is an interface for communicating with the main body 10 via the communication path 30.

  The IC card I / F 29 is connected to the card reader 6 via, for example, a USB cable. The card reader 6 performs non-contact wireless communication with the IC card 5 that has been operated in proximity (non-contact operation) by the user at the time of login operation to the MFP 1, and the card ID stored in the IC card 5 and the user Read authentication information such as information. In addition to the non-contact operation, the authentication information may be read from the IC card 5 by a contact operation.

  In addition, as an example, the card reader 6 and the operation unit 20 are physically connected to each other via a USB cable or the like. However, even if the operation unit 20 includes the card reader 6, Good. That is, the operation unit 20 and the card reader 6 may be integrally formed (may be formed as a single device).

  In addition, even if there is a difference in the name of an IC card or an ID card, the present invention can be applied to any storage medium as long as it is a storage medium. Is not limited. The same applies to a card reader device, and any device that can read user information from such a storage medium can be used.

  The operation panel 27 includes a liquid crystal display (LCD) having a touch sensor. The operation panel 27 receives various types of input in accordance with user operations, and displays various types of information such as information in accordance with the received input, information indicating the operation status of the MFP 1, information indicating a setting state, and the like. The operation panel 27 may be configured by an organic EL (Organic Light-Emitting Diode: OLED) display device provided with a touch sensor. Further, in addition to or instead of this, an operation unit such as a hardware key or a display unit such as a light emitting unit may be provided.

(Software configuration of MFP)
FIG. 2 is a diagram illustrating an example of the software configuration of the MFP 1. As shown in FIG. 2, the main body 10 includes an application layer 101, a service layer 102, and an OS (Operating System) layer 103. The entities of the application layer 101, the service layer 102, and the OS layer 103 are various software stored in the ROM 12, the HDD 14, or the like. Various functions are provided by the CPU 11 executing these software.

  The software of the application layer 101 is a control application for operating a hardware resource to provide a predetermined function (in the following description, it may be simply referred to as “application”). For example, the application includes a copy application for providing a copy function, a scanner application for providing a scanner function, a FAX application for providing a facsimile function, a printer application for providing a printer function, and the like.

  The software of the service layer 102 is software that is interposed between the application layer 101 and the OS layer 103 and provides an interface for using hardware resources included in the main body 10 for the application. Specifically, it is software for providing a function of accepting an operation request for a hardware resource and arbitrating the operation request. The operation request accepted by the service layer 102 is, for example, a request for reading by a scanner or printing by a plotter.

  Note that the interface function by the service layer 102 is provided not only to the application layer 101 of the main body 10 but also to the application layer 201 of the operation unit 20. That is, the application layer 201 (application) of the operation unit 20 can also realize a function using hardware resources (for example, the engine 17) of the main body 10 via the interface function of the service layer 102.

  The software of the OS layer 103 is basic software (operating system) for providing a basic function for controlling hardware included in the main body 10. The software of the service layer 102 converts a hardware resource use request from various applications into a command interpretable by the OS layer 103 and passes the command to the OS layer 103. Then, when the command is executed by the software of the OS layer 103, the hardware resource performs an operation according to the request of the application.

  Similarly, the operation unit 20 includes an application layer 201 and an OS layer 203. The application layer 201 and the OS layer 203 included in the operation unit 20 are the same as the main body 10 in terms of the hierarchical structure. However, the types of operation requests that can be accepted by the functions provided by the applications in the application layer 201 are different from those on the main body 10 side. The application of the application layer 201 is software for operating a hardware resource included in the operation unit 20 and providing a predetermined function. For example, it is software for providing a UI (user interface) function for performing operations and displays related to functions (copy function, scanner function, facsimile function, printer function) provided in the main body 10.

  In the case of the MFP 1 of the first embodiment, the software of the OS layer 103 on the main body 10 side and the software of the OS layer 203 on the operation unit 20 side are different from each other in order to maintain the independence of functions. As an example, Linux (registered trademark) is installed as software of the OS layer 103 on the main body 10 side, and Android (registered trademark) is installed as software of the OS layer 203 on the operation unit 20 side. As a result, the main body 10 and the operation unit 20 operate independently of each other with different operating systems.

  By operating the main body 10 and the operation unit 20 with different operating systems, communication between the main body 10 and the operation unit 20 is performed as communication between different devices, not communication between processes in a common device. . An operation (command communication) for transmitting the input (instruction content from the user) received by the operation unit 20 to the main body 10 and an operation for the main body 10 notifying the operation unit 20 of an event correspond to this. Here, the function of the main body 10 can be used when the operation unit 20 performs command communication with the main body 10. Further, the event notified from the main body 10 to the operation unit 20 includes the execution status of the operation in the main body 10 and the contents set on the main body 10 side.

  In the example of the first embodiment, the power supply to the operation unit 20 is performed from the main body 10 via the communication path 30, so that the power control of the operation unit 20 is the power control of the main body 10. Can be done separately (independently).

  In this example, the main body 10 and the operation unit 20 are electrically and physically connected via the communication path 30, but the operation unit 20 can be detached from the main body 10 as described above. In this case, the main body 10 and the operation unit 20 are provided with a short-range wireless communication unit such as an infrared communication unit, an RF communication unit, or a Bluetooth (registered trademark) communication unit. RF is an abbreviation for “Radio Frequency”. Alternatively, the main body 10 and the operation unit 20 are provided with a wireless LAN communication function such as Wi-Fi (registered trademark), and communicate with each other via the wireless LAN access point (wireless LANAP) 41 and the network 40 as shown in FIG. It may be possible. LAN is an abbreviation for “Local Area Network”. When the operation unit 20 can be removed from the main body 10, the operation unit 20 stores the power supplied from the main body 10 via the communication path 30 in the secondary battery, and when the operation unit 20 is removed from the main body 10, It operates with the power stored in the secondary battery and communicates with the main body 10.

(Software provided in MFP)
FIG. 3 is a diagram illustrating an example of software provided in the MFP 1. As described above, the main body 10 is divided into the application layer 101, the service layer 102, and the OS layer 103. Among these, the application layer 101 stores an application that controls the engine 17 shown in FIG. Specifically, the application layer 101 stores a copy application 111, a scanner application 112, a printer application 113, and a FAX application 114. The copy application 111 to FAX application 114 are standard job execution function applications, and are examples of control applications.

  Further, the service layer 102 stores various programs corresponding to processing commonly performed by each application, such as an energy saving management program (energy saving management program) 121, a memory management program 122, and a controller control program 123. The service layer 102 performs processing commonly performed by each application, such as energy saving management and memory management.

  The controller control program 123 has a table in which an error type and an application affected by the error are associated with each other and stored. The controller control program 123 determines an application corresponding to the type of error that has occurred as an error notification destination. For example, when a plotter jam occurs, the controller control program 123 determines a printer application 134 and a copy application 131 described later as notification destinations. If a scanner jam occurs, the controller control program 123 determines a scanner application 133 and a copy application 131 (to be described later) as notification destinations. Further, the controller control program 123 determines an error management application 140 described later as a notification destination regardless of the type of error.

  On the other hand, the operation unit 20 is divided into an application layer 201 and an OS layer 203. The difference between the main body application and the operation unit application is that the main body application controls the functions of the image forming apparatus such as reading and printing by performing engine control by the controller control program 123, whereas the operation unit application controls the UI. It is carried out. That is, a user operation is received by performing screen display with the operation unit application, and the main body application (controller control program 123) performs engine control based on the user operation.

  The operation unit application includes a vendor application 137 developed by a development vendor for the scanner application 133 and the like.

  Further, in order to simplify the development of the vendor application 137, the operation section application is provided with a function providing application 136 that provides the vendors with functions equivalent to the copy application 131 to the FAX application 135 of the operation section 20. .

  That is, the application layer 201 of the operation unit 20 stores an application that accepts a user operation via the user interface. Specifically, the application layer 201 stores a home application 130, a copy application 131, a scanner application 133, a printer application 134, a FAX application 135, a function providing application 136, a vendor application 137, and an error management application 140.

  The home application 130 displays a main screen (initial screen) on which icons and the like for specifying a desired operation are arranged. Then, the application designated by the user via the icon operation is activated. The copy application 131 is an application that accepts a user's copy operation via an operation button and a setting button. The scanner application 133 is an application that receives a user's scanner operation via an operation button, a setting button, and the like. The printer application 134 is an application that accepts a user's printer operation via an operation button, a setting button, and the like. The FAX application 135 is an application that receives a user's facsimile transmission / reception operation via an operation button, a setting button, and the like.

  The function providing application 136 is an example of an image processing program. Further, the function providing application 136 is stored in a storage unit such as the ROM 22, the RAM 23, or the flash memory 24 of the operation unit 20 as an example.

  The function providing application 136 provides development vendors with functions equivalent to the copy application 131 to the FAX application 135 of the operation unit 20 in order to facilitate the development of the vendor application 137 as described above.

  The vendor application 137 is an example of a request application. The vendor application 137 calls the function providing application 136 related to the printer application 134, for example, when setting or executing printing.

  That is, when the function providing application 136 is an application corresponding to the scanner application 133, for example, the function providing application 136 provides a function for displaying a user interface such as a normal operation menu and a setting menu to the development vendor. When the function providing application 136 is an application corresponding to the printer application 134, for example, the function providing application 136 provides a function for displaying a user interface such as a normal operation menu and a setting menu to the development vendor.

  As described above, the operation unit 20 of the MFP 1 is provided with a function providing application 136 for providing a function equivalent to that of the copy application 131 to the FAX application 135 to a vendor or the like. An API (Application Programming Interface) that realizes the function of the function providing application 136 is disclosed to the vendor of the vendor application 137.

  For example, when a plotter jam occurs as an error in the main body 10 during operation of the copy application 131, the error management application 140 is notified of an error (plotter jam) from the controller control program 123 together with the copy application 131. The error management application 140 notified of the error (plotter jam) constructs an error screen corresponding to the error content, waits for an app switching OK response from the controller control program 123, and displays the constructed error screen.

  When the error management application 140 is notified of the error (plotter jam) cancellation from the controller control program 123 of the main body 10 together with the copy application 131, the error management application 140 waits for an error non-display request from the copy application 131 and displays an error screen. close. The error screen is a screen for notifying the user that an error has occurred, and may be generated and displayed as a “warning screen” or a “notification screen”.

(Function of error management application 140)
FIG. 4 is a functional block diagram of the error management application 140. The CPU 21 of the operation unit 20 executes the error management application 140 stored in a storage unit such as the ROM 22, RAM 23, or flash memory 24, thereby realizing the error management unit 150 shown in FIG.

  Based on the screen generation table T (see FIG. 5), the error management unit 150 identifies screen parts corresponding to the error type and detailed error information (for example, jam position, toner color, etc.) Generate an error screen. Here, FIG. 5 is a diagram showing an example of the screen generation table T. As shown in FIG. As shown in FIG. 5, the screen generation table T configures an error screen in association with an error type, an information type (fixed information, fluctuation information), and detailed error information (for example, a jam position). Parts (images, message files) are stored.

  In this example, the error management unit 150 is realized by software. However, part or all of the error management unit 150 may be realized by hardware such as an IC (Integrated Circuit).

  The error management application 140 may be provided as a file in an installable or executable format recorded on a recording medium readable by a computer device such as a CD-ROM or a flexible disk (FD). Further, the program may be provided by being recorded on a recording medium readable by a computer device such as a CD-R, a DVD (Digital Versatile Disk), a Blu-ray Disc (registered trademark), or a semiconductor memory. Further, the error management application 140 may be provided by being installed via a network such as the Internet. The error management application 140 may be provided by being incorporated in advance in a ROM or the like in the device.

(Error screen display operation of the error management application)
Next, an error screen display operation of the error management application 140 will be described. FIG. 6 is a sequence diagram showing the flow of operation of each unit when an error occurs.

  As shown in FIG. 6, when an error occurs (for example, a plotter jam during copying), the controller control program 123 stores a table in which the error type and the application affected by the error are associated with each other and stored. The application corresponding to the type of error that has occurred is determined as an error notification destination (step S1). When plotter jam occurs, the controller control program 123 determines the printer application 134 and the copy application 131 as notification destinations. Further, the controller control program 123 determines the error management application 140 as a notification destination regardless of the type of error.

  Next, the controller control program 123 transmits an error notification including the error type and detailed error information to the error management application 140 (step S2).

  The error management application 140 generates an error screen based on the error type and the detailed error information in the error notification (step S3). Specifically, based on the screen generation table T, the error screen part corresponding to the error type, the information type, and the detailed error information is specified, and the error screen is generated.

  Further, the controller control program 123 broadcasts an error notification including the error type and detailed error information to the copy application 131 and the printer application 134 (steps S4 and S5).

  The copy application 131 stores information indicating that an error has occurred, and determines that an error display request is required when the application itself is being displayed on the screen (that is, being used by the user) If the screen is not being displayed, it is determined that an error display request is not required (step S6).

  When it is determined that an error display request is necessary, the copy application 131 stores information indicating that an error display request has been made, and also stores screen information currently being displayed (screen ID, screen user settings, etc.). (Step S7). This is for returning to the screen at the time of error occurrence based on the screen information when the error is resolved.

  On the other hand, the printer application 134 stores information indicating that an error has occurred, and determines that an error display request is necessary when the printer application 134 is displaying the screen (ie, being used by the user). If the screen is not being displayed, it is determined that an error display request is not required (step S8). Here, since the copy screen is not being displayed and the print screen is not being displayed, it is determined that an error display request is not required, and the printer application 134 does not store the screen information being displayed and does not perform subsequent processing.

  Next, the copy application 131 makes an error display request to the error management application 140 (step S9). The error management application 140 acquires the application (here, the copy application 131) that requested the error display request.

  The error management application 140 requests the controller control program 123 of the main body 10 to switch from the copy application 131 to the error management application 140 (error display request) (step S10).

  The controller control program 123 of the main body 10 stores the request source of the error display request (step S11). Note that if the request source of the error display request has already been stored, the controller control program 123 updates the stored information (step S11). In the present embodiment, the copy application 131 is stored.

  The controller control program 123 of the main body 10 requests the requesting copy application 131 that is displaying the screen to release the screen (step S12).

  In response to the screen release request, the copy application 131 responds to the controller control program 123 with a screen release OK (step S13).

  The controller control program 123 of the main body 10 responds to the error management application 140 with an OK to switch the application to the error management application 140 (step S14).

  When the error management application 140 receives an OK response for application switching, the error management application 140 displays the error screen generated in advance in step S3 (step S15).

  Here, FIG. 7 is a diagram showing an example of an error screen E when plotter jam occurs. As shown in FIG. 7, when an error notification (type: plotter jam, details: jam position A, B, C, Z) is received, the error screen E displays an image corresponding to the error notification and an image at the jam position. It is generated by synthesis.

  Here, a case where the user desires to shift the operation to printing will be described.

  While the error screen is displayed, the user presses a home button (not shown) to display the home screen, selects the printer application 134 from the application list on the home screen, and displays the screen of the printer application 134. (Step S16).

  When the user displays the screen of the printer application 134, the printer application 134 stores information indicating that an error has occurred in step S8. Based on this information, the printer application 134 determines that an error display request is necessary. (Step S17). This is because the printer application 134 cannot be used normally because an error (plotter jam) affecting the printer application 134 has occurred.

  In this case, the printer application 134 makes an error display request to the error management application 140 (step S18). The error management application 140 acquires the application (here, the printer application 134) that requested the error display request.

  The error management application 140 requests the controller control program 123 of the main body 10 to switch from the printer application 134 to the error management application 140 (error display request) (step S19).

  The subsequent processing is the same as steps S12 to S15, but the controller control program 123 stores the printer application 134 as a request source of the error display request.

  On the other hand, a case where the user desires to shift the operation to scanning will be described.

  While the error screen is displayed, the user presses the home button to display the home screen, selects the scanner application 133 from the application list on the home screen, and displays the screen of the scanner application 133 (step). S20).

  When the user displays the screen of the scanner application 133, the scanner application 133 does not store information indicating that an error has occurred, and therefore determines that an error display request is unnecessary (step S21).

(Modification 1 when an error occurs)
In step S11, instead of the controller control program 123 storing (updating) the request source of the error display request, the error management application 140 may store (update) the request source of the error display request after step S9. Good.

(Modification 2 when an error occurs)
In steps S9 to S10, the copy application 131 makes an application switching request directly to the controller control program 123 without going through the error management application 140, omits the processing in steps S12 to S13, and performs error management in step S14. It may be controlled to send an error screen display request to the application 140.

(Operations for error management application error resolution)
Next, the operation of the error management application 140 when the error is resolved will be described.

  Here, FIG. 8 is a diagram showing an example of screen transition at the time of error resolution. Regarding the screen transition at the time of error elimination, a use case as shown in FIG. 8 can be considered.

From the use case shown in FIG. 8, it is necessary to control as shown below.
・ Conditions for screen transition when an error is resolved An error screen is displayed when the error is resolved.
・ Destination from the error screen The screen of the first application that requested the display of the error screen For example, in (d), the error screen display request was made from “Print” in the middle. Copy ".

  Next, the operation of the error management application 140 when the error is resolved will be described. FIG. 9 is a sequence diagram showing the flow of operation of each unit when the error is resolved.

  As shown in FIG. 9, when the error is resolved (for example, a plotter jam being copied), the controller control program 123 stores a table in which the error type and the application affected by the error are associated with each other. The application corresponding to the type of error that has occurred is determined as a notification destination for error resolution (step S31). When the plotter jam is resolved, the controller control program 123 determines the printer application 134 and the copy application 131 as notification destinations. Further, the controller control program 123 determines the error management application 140 as a notification destination regardless of the type of error.

  Next, the controller control program 123 transmits an error solution notification including the resolved error type to the error management application 140 (step S32).

  The controller control program 123 broadcasts and transmits an error elimination notification including the type of error eliminated to the copy application 131 and the printer application 134 (steps S33 and S34).

  The copy application 131 determines whether or not an error non-display request is necessary (step S35). Specifically, the copy application 131 determines that it is necessary if information indicating that an error display request has been made is stored, and determines that it is unnecessary if information is not stored. In the case of the present embodiment, information indicating that an error display request has been made is stored in step S6 of the sequence diagram at the time of occurrence of an error shown in FIG. Then, the copy application 131 deletes the information indicating that the stored error has occurred.

  On the other hand, the printer application 134 also determines whether an error non-display request is necessary (step S36). Specifically, the printer application 134 determines that it is necessary if information indicating that an error display request has been made is stored, and determines that it is unnecessary if information is not stored. In the case of the present embodiment, the printer application 134 determines that it is unnecessary because it does not store information indicating that an error display request has been made. Then, the printer application 134 deletes the information indicating that the stored error has occurred. The printer application 134 does not perform subsequent processing.

  Next, the copy application 131 makes an error non-display request to the error management application 140 (step S37).

  The error management application 140 closes the error screen on condition that an error resolution notification and an error non-display request are received (step S38).

  Next, the error management application 140 determines whether or not application switching is necessary based on whether or not the application itself is being displayed on the screen (step S39). The error management application 140 determines that it is necessary if the screen is being displayed, and is not necessary if the screen is not being displayed (that is, if the screen of another application such as the scanner application 133 or the home application 130 is displayed). to decide. Even if printing and copying are displayed on the screen according to a user instruction, in step S17 of the sequence diagram when an error occurs in FIG. 6, it is determined that an error display request is necessary, and the error application screen is immediately switched. While the screen of the application 134 is being displayed, the error cannot be eliminated.

  If the error management application 140 determines in step S39 that it is not necessary, the processing ends here. In step S39, when the error management application 140 determines that it is necessary, the error management application 140 executes the processing from step S40.

  The error management application 140 transmits an application switching request to the controller control program 123 to return the screen to the copy application 131 (step S40).

  Since the controller control program 123 of the main body 10 stores the request source of the error display request when an error occurs, the controller 10 determines that the request source is the switching destination application (step S41).

  The controller control program 123 requests the error management application 140 to release the screen in order to switch the screen display to the copy application 131 (step S42).

  In response to the screen release request, the error management application 140 responds to the controller control program 123 with a screen release OK (step S43).

  When the controller control program 123 receives permission to release the screen, it makes a display request to the copy application 131 (step S44).

  Upon receiving the application display request, the copy application 131 generates and displays the screen that was displayed when an error occurred based on the stored screen information (screen ID, screen user settings, etc.) (step S45). ). If not stored, for example, the top screen (initial screen) of the copy application 131 is displayed.

  Thereafter, the controller control program 123 notifies the error management application 140 of an application switching OK response (step S46).

  If the error management application 140 stores (updates) the request source of the error display request in response to the first modification when an error occurs, the stored request is determined when switching is determined in step S39. The source may be determined as the switching destination application, and the controller control program 123 may be requested to switch to the determined application in step S40. Thereby, the process of step S41 becomes unnecessary.

  Instead of executing the processing after step S38 in response to the non-display request from the copy application 131 in step S37, the processing after step S38 may be executed in response to the error resolution notification in step S32. Then, it is not necessary to make an error non-display request from the copy application 131 to the error management application 140. Further, in step S5 when an error occurs, it is not necessary to store information indicating that an error display request has been made. Furthermore, Steps S42, S43 and Step S46 may be omitted.

  Thus, in order to realize the use case shown in FIG. 8, the controller control program 123 (or error management application 140) stores (updates) the request source application for each error display request. Based on this, the transition destination from the error screen can be determined.

  As described above, according to the present embodiment, the error management application 140 that manages errors occurring in the main body 10 and generates an error screen based on the error information notified from the main body 10 is installed in the operation unit 20. . Then, an error screen E is generated in response to an error notification from the main body 10, and the error screen E that has been generated in advance is displayed in response to an application switching request relating to the currently displayed error. . As a result, there is no exchange of image data between the main body 10 and the operation unit 20, and it is not necessary to emulate the image data, so that the screen can be switched quickly when an error occurs and when the error is released. Can do.

  Further, when a plurality of apps for realizing one or a plurality of functions of the main body 10 are installed in the operation unit 20, the error management application 140 centrally manages errors generated by the main body 10, thereby Each of the apps no longer needs to have an error management function.

  Further, in the above-described embodiment, an example of a multifunction peripheral in which one application is installed for one function, such as a copy application for providing a copy function and a scanner application for providing a scanner function, will be described. However, it is also applicable to a multi-function peripheral in which a plurality of applications are installed for one function (for example, a multi-function peripheral in which a copy application 137 and a vendor application 137 providing a copy function are installed for the copy function). can do.

  In the above embodiment, the information processing apparatus according to the present invention is described by taking an example in which the information processing apparatus is applied to a multifunction machine having at least two functions among a copy function, a printer function, a scanner function, and a facsimile function. The present invention can be applied to any image forming apparatus such as a printer, a scanner apparatus, and a facsimile apparatus.

  The information processing apparatus of the present invention can also be applied to various electronic devices such as an electronic blackboard and a projector. The information processing apparatus of the present invention can also be applied to a system in which an operating device is connected as an operating unit to an electronic device to be operated via a network.

DESCRIPTION OF SYMBOLS 1 Information processing apparatus 10 Main body 20 Operation part 150 Error management means

JP2015-108939A

Claims (10)

In an information processing apparatus comprising: a main body having at least one function; and an operation unit operated by a user to execute control on the function.
The operation unit includes error management means for generating and displaying an error screen based on error information notified from the main body on condition that an error has occurred in the function.
An information processing apparatus characterized by that. The error management means includes
Generate the error screen according to the error information notified from the main body,
The error screen is displayed in response to the switching request notified from the main body, on the condition that the screen relating to the function in which an error has occurred is being displayed.
The information processing apparatus according to claim 1. The error management means is an application provided in the operation unit for realizing the function, and when any one of the plurality of applications related to the function in which an error has occurred is being displayed. , Switch from the application screen to the error screen,
The information processing apparatus according to claim 2. The error management means does not display the error screen when none of the screens of the plurality of applications provided in the operation unit is related to the function in which an error has occurred.
The information processing apparatus according to claim 3. The error management means generates the error screen common to a plurality of the functions.
The information processing apparatus according to claim 1, wherein the information processing apparatus is an information processing apparatus. The error management means includes
Closes the error screen based on the error cancellation notification notified from the main body on condition that the error that occurred in the function has been resolved,
The information processing apparatus according to claim 1, wherein the information processing apparatus is an information processing apparatus. The error management means includes
An application provided in the operation unit for realizing the function, provided that a request for non-display of the error screen is received from the application displaying the screen related to the function in which an error has occurred. , Closing the error screen in response to the error resolution notification notified from the main body, and displaying the screen of the application,
The information processing apparatus according to claim 6. An information processing system in which a main body device having at least one function and an operation device operated by a user to execute control on the function are connected via a network,
The operating device includes error management means for generating and displaying an error screen based on error information notified from the main body device via the network on the condition that an error has occurred in the function.
An information processing system characterized by this. A screen display method in an information processing system in which a main body device having at least one function and an operation device operated by a user to execute control on the function are connected via a network,
An error management step of generating and displaying an error screen based on error information notified from the main body device via the network on the condition that an error has occurred in the function in the operating device;
A screen display method characterized by that. A computer that controls the operation unit of the information processing apparatus, comprising: a main body having at least one function; and an operation unit operated by a user to execute control on the function.
A program for functioning as error management means for generating and displaying an error screen based on error information notified from the main body on condition that an error has occurred in the function.

Images