Printer, method for processing information on printer, program and information processing system

Abstract

To enable a user at a site to properly solve a failure occurring on a device in a printer.SOLUTION: A printer according to one embodiment in the present invention comprises: a storing part that stores a data base in which events occurring in the past on a device loaded on the printer are associated with information on occurrence times; a processor that executes self-diagnosis processing to the device in accordance with user operation; and a display part that displays an executed result of the self-diagnosis processing. The self-diagnosis processing includes steps of obtaining event history information including information on one or more events in the past occurring on the device and on occurrence times of the events and of obtaining failure information relating to presence or absence of a temporal failure occurring on the device, on the basis of the event history information and operation information showing a current operation state of the device.SELECTED DRAWING: Figure 8

Description

[Technical Field]

[0001] The present invention relates to information processing in a printer. [Background technology]

[0002] Printers equipped with a self-diagnosis function have been known for some time. For example, Patent Document 1 describes a printer that has a function for storing diagnostic results obtained by a self-diagnosis function in a storage means. This printer is configured to print out when a predetermined switch is operated, and to print out an indication of the abnormality in the printout of the diagnostic results if abnormal data is detected in the diagnostic results. [Prior art documents] [Patent documents]

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

[0004] The self-diagnostic function provided in conventional printers is configured to output self-diagnostic results indicating the presence or absence of a current malfunction in devices within the printer, such as information on broken wires in the printer, sensor output information, etc. However, the self-diagnostic result information indicating the presence or absence of a current malfunction may not be sufficient for on-site users, such as service personnel or operators, to properly resolve the malfunction (troubleshoot).

[0005] SUMMARY OF THE INVENTION It is therefore an object of the present invention to enable a user on-site to properly resolve a malfunction that occurs in a device within a printer. [Means for solving the problem]

[0006] According to one aspect of the present invention, there is provided a printer including: a storage unit that stores a database in which events that have occurred in the past are associated with information on the time of occurrence for a device installed in the printer; a processor that executes a self-diagnosis process for the device in response to a user operation; a display unit that displays the execution result of the self-diagnosis processing, The self-diagnosis process includes: obtaining, from the database, event history information including one or more past events that have occurred in the device and information on the time of occurrence of each event; and acquiring failure information regarding the presence or absence of a failure of the device over time based on the event history information and operation information indicating the current operation state of the device; It is a printer. [Effects of the Invention]

[0007] According to one aspect of the present invention, a user in the field can appropriately solve a malfunction that occurs in a device within a printer. [Brief explanation of the drawings]

[0008] [Figure 1] 1 is a perspective view of a printer according to an embodiment. [Figure 2] FIG. 1 illustrates an internal mechanism of a printer according to an embodiment. [Figure 3] 10 is an example of a transition of a screen displayed on a printer according to an embodiment. [Figure 4] 10 is an example of a transition of a screen displayed on a printer according to an embodiment. [Figure 5] 10 is an example of a transition of a screen displayed on a printer according to an embodiment. [Figure 6] FIG. 1 is a functional block diagram of a printer according to an embodiment. [Figure 7] FIG. 2 illustrates an example of a data structure of an event database. [Figure 8] FIG. 2 is a functional block diagram of software related to a self-diagnosis function in the printer of the embodiment. [Figure 9]10 is a flowchart illustrating a device information accumulation process of a printer according to an embodiment. [Figure 10] 10 is a flowchart illustrating an example of an alarm issuing process of the printer according to an embodiment. [Figure 11] 4 is a flowchart illustrating a self-diagnosis process of a printer according to an embodiment. [Figure 12] 12 is a flowchart in the case where the self-diagnosis process shown in FIG. 11 is applied to a cutter unit. [Figure 13] 12 is a flowchart in the case where the self-diagnosis process shown in FIG. 11 is applied to a cutter unit. [Figure 14] FIG. 2 illustrates an example of the data configuration of a failure log database; DETAILED DESCRIPTION OF THE INVENTION

[0009] The embodiments described below are not limited to the drawings described by the brief description of the drawings. In this specification, the term "apparatus" is used to refer to an individual part, device, or unit installed in a printer.

[0010] A first aspect of the present invention is a printer including: a storage unit that stores a database in which events that have occurred in the past are associated with information on the time of occurrence for a device installed in the printer; a processor that executes a self-diagnosis process for the device in response to a user operation; a display unit that displays the execution result of the self-diagnosis processing, The self-diagnosis process includes: obtaining, from the database, event history information including one or more past events that have occurred in the device and information on the time of occurrence of each event; and acquiring failure information regarding the presence or absence of a failure of the device over time based on the event history information and operation information indicating the current operation state of the device; It is a printer.

[0011] According to a first aspect of the present invention, it becomes possible for on-site users to appropriately resolve malfunctions that occur in devices within a printer, taking into account the current operating status of the device and the history of past events.

[0012] In a second aspect of the present invention, the self-diagnosis process includes identifying a date and time when an event that has occurred in the device has changed based on the event history information, In the printer according to the first aspect, the malfunction information includes information relating to the specified date and time.

[0013] According to a second aspect of the present invention, in the self-diagnosis process, for example, the date on which a failure occurred in the target device in the past is identified, thereby enabling the user to appropriately estimate the cause of the failure.

[0014] In a third aspect of the present invention, the self-diagnosis process includes calculating a statistical value based on the number of times a predetermined event has occurred in the device based on the event history information, In the printer according to the first or second aspect, the failure information includes information relating to the statistical value.

[0015] According to a third aspect of the present invention, in the self-diagnosis process, statistical values ​​related to failures, such as the frequency of failures and the probability of failures occurring, are obtained for the target device, allowing the user to understand the trends in failures and appropriately estimate the cause of the failure.

[0016] In a fourth aspect of the present invention, the processor Each time an event occurs in the device, the event is recorded in the database in association with information on the time of occurrence; The printer according to any one of the first to third aspects obtains, from the database, event history information including one or more past events that have occurred to the device and information on the time at which each event occurred, and determines whether to output a warning based on the obtained event history information.

[0017] According to a fourth aspect of the present invention, a user can receive a warning about a device at an appropriate timing as needed, based on the history of events that have occurred in the device in the past.

[0018] A fifth aspect of the present invention is a printer according to any of the first to fourth aspects, wherein the processor periodically acquires an output value of a sensor that detects the state of the device or a measurement value related to the operation of the device as an event that occurs to the device, and records the acquired output value or measurement value in the database.

[0019] According to a fifth aspect of the present invention, the state and operation of the target device can be periodically monitored.

[0020] A sixth aspect of the present invention is a printer described in any of the first to fifth aspects, wherein the processor records the failure information in the memory unit in association with individual identification information of the device.

[0021] According to a sixth aspect of the present invention, traceability for individual devices can be ensured. For example, even if a device is replaced with a different printer, the history of events that have occurred in the device and information on failures can be obtained.

[0022] A seventh aspect of the present invention is a printer described in any of the first to sixth aspects, wherein the processor, as a result of executing the self-diagnostic process, causes the display unit to display, together with the fault information, text indicating actions that the user should take regarding the device.

[0023] According to a seventh aspect of the present invention, the user can visually recognize the failure information and the action that the user should take.

[0024] In an eighth aspect of the present invention, the processor By executing a boot loader immediately after starting the printer, a test process is performed on the device, and the results of the test process are recorded; The printer according to any one of the first to seventh aspects, wherein the result of the inspection process is recorded in the database after the system software of the printer becomes executable.

[0025] According to an eighth aspect of the present invention, even if the device cannot be inspected after the printer is put into operation, the device can be inspected before the printer is put into operation.

[0026] A ninth aspect of the present invention is an information processing method for a printer, comprising: a step of recording events that have occurred in the past with respect to a device installed in the printer in association with information on the time of occurrence in a database of a storage unit of the printer; acquiring, from the database in response to a user operation, event history information including one or more events that have occurred in the past with respect to the device and information on the time at which each event occurred; acquiring failure information regarding whether or not the device has failed over time based on the event history information and operation information indicating the current operation state of the device; displaying the fault information on a display unit of the printer; The present invention relates to an information processing method for a printer, including:

[0027] According to a ninth aspect of the present invention, it becomes possible for on-site users to appropriately resolve malfunctions that occur in devices within a printer, taking into account the current operating status of the device and the history of past events.

[0028] A tenth aspect of the present invention is a program installed in a printer, comprising: a step of recording events that have occurred in the past with respect to a device installed in the printer in a database of a storage unit of the printer in association with information on the time of occurrence; a step of acquiring, in response to a user operation, event history information from the database, the event history information including information on one or more past events that have occurred in the device and the time at which each event occurred; a step of acquiring failure information regarding the presence or absence of a failure of the device over time based on the event history information and operation information indicating the current operation state of the device; a step of displaying the failure information on a display unit of the printer; It is a program for causing a computer to execute the above.

[0029] According to a tenth aspect of the present invention, it becomes possible for on-site users to appropriately resolve malfunctions that occur in devices within a printer, taking into account the current operating status of the device and the history of past events.

[0030] An eleventh aspect of the present invention is an information processing system including a server capable of communicating with a printer, and an information processing terminal capable of communicating with the server, The server a storage unit that stores a database in which events that have occurred in the past with respect to a device installed in the printer are associated with information on the time of occurrence; a processor that executes a self-diagnosis process for the device in response to a request from the information processing terminal; The self-diagnosis process includes: obtaining, from the database, event history information including one or more past events that have occurred in the device and information on the time of occurrence of each event; and acquiring failure information regarding the presence or absence of a failure of the device over time based on the event history information and operation information indicating the current operation state of the device; the information processing terminal acquires the execution result of the self-diagnosis processing from the server and displays it. It is an information processing system.

[0031] According to an eleventh aspect of the present invention, an administrator or a help desk staff member can remotely solve a malfunction that occurs in a device within a printer.

[0032] Hereinafter, the embodiments will be described in detail with reference to the drawings. First, the configuration of an exemplary printer 1 will be described with reference to Figures 1 and 2. The printer 1 is a printer that prints information on labels and then issues the labels.

[0033] Fig. 1 is a perspective view showing the exterior of an exemplary printer 1. Fig. 2 is a diagram showing the internal mechanism of the printer 1. Note that the configuration of the printer shown in Fig. 1 is merely an example for describing the printer of one embodiment.

[0034] Referring to FIG. 1, the printer 1 has, on its front surface, a plurality of input buttons 2 (physical keys), a display panel 3 (an example of a display unit), and an issuing slot 4. The display panel 3 forms a GUI (Graphical User Interface) for configuring various settings for the printer 1. In one embodiment, the display panel 3 has a touch panel function and accepts touch inputs by the user. Labels issued by the printer 1 are ejected from the issuing slot 4. As will be described later, in response to a user operation, the printer 1 executes a self-diagnosis process for each device within the printer 1. At this time, the display panel 3 displays the results of the execution of the self-diagnosis process.

[0035] Next, the printer 1 will be described with reference to Fig. 2. Fig. 2 shows a schematic configuration of the printer 1. As shown in FIG. 2, the printer 1 contains roll paper R, which is continuous paper CP wound in a roll. The continuous paper CP includes, for example, a strip-shaped backing paper PM and a plurality of labels PL releasably arranged at equal intervals on the backing paper PM. In one embodiment, the labels PL have a thermosensitive coloring layer formed on the printable side and an adhesive applied to the side opposite the printable side. A release agent such as silicone is applied to the front surface of the backing paper PM (the surface on which the labels are placed). In one embodiment, a position detection mark M is printed on the back surface of the backing paper PM at a position corresponding to the edge of the label.

[0036] The printer 1 includes a cutter unit 5, a thermal head 7, a platen roller 8, an auxiliary roller 9, and a label position detection sensor 21. In the printer 1, continuous paper is pulled out from the roll paper R in response to the rotation of the platen roller 8, and is directed toward the paper outlet 4 via the auxiliary roller 9. The thermal head 7 has a plurality of heating elements arranged in a line, and prints information on labels on the continuous paper CP while clamping the continuous paper CP between itself and a platen roller 8. A label position detection sensor 21 detects the label edge based on the detection result of the position detection mark M. The printer 1 adjusts the feed amount of the continuous paper based on the detection result of the label edge so that printing can start from a predetermined position on the label.

[0037] The cutter unit 5 includes a fixed blade 51 and a movable blade 52 for cutting the printed label. When the movable blade 52 moves toward the fixed blade 51, the label PL is cut by the movable blade 52 and the fixed blade 51. Although not shown, the cutter unit 5 has an elevator means for moving the movable blade 52 from the lowest first position (the position shown in FIG. 2) to the highest second position. This elevator means has a motor that drives the movable blade 52 itself or a mechanism (such as a gear) connected to the movable blade 52. When issuing a label PL, the elevator means moves the movable blade 52 from the first position to the second position to cut the label PL, and controls the motor to return from the second position to the first position after cutting.

[0038] In one embodiment, the rising time (the time it takes to move from the first position to the second position) and the falling time (the time it takes to return from the second position to the first position) of the movable blade 52 are measured. The rising time and the falling time of the movable blade 52 are correlated with the amount of glue accumulation (adhesion of adhesive on the label PL) on the movable blade 52, and are therefore monitored to appropriately notify the user of the timing to clean the movable blade 52. As the amount of glue accumulation increases, the rising time and / or the falling time of the movable blade 52 become longer (i.e., the cutting speed decreases), and the cutting ability of the label PL decreases, so cleaning of the movable blade 52 becomes necessary. In one embodiment, in order to measure the rising time and the falling time of the movable blade 52, a first cutter sensor that detects when the movable blade 52 is in the first position and a second cutter sensor that detects when the movable blade 52 is in the second position may be provided. The cutter sensors may be, for example, of a type that uses physical contact or an optical type.

[0039] Next, the self-diagnosis process executed in the printer 1 will be described. In response to a user's operation, the printer 1 is configured to execute a self-diagnostic process for each device installed in the printer 1. The results of the self-diagnostic process executed by the printer 1 are displayed on the display panel 3 and notified to the user. First, examples of displays on the display panel 3 related to the execution of the self-diagnosis process will be described below with reference to Figures 3 to 5. Figures 3 to 5 each show an example of the transition of screens displayed on the display panel 3 of the printer 1.

[0040] In Fig. 3, screen G1 is the home screen of the printer 1. Screen G1 has a settings button 102. When the user operates the settings button 102, screen G2 is displayed. Screen G2 presents a self-diagnosis menu that allows the user to selectively execute self-diagnosis processes related to various devices. It is possible to return to the home screen by operating the back button 104.

[0041] In the first example, the item "Cutter Unit Diagnostics" is selected on screen G2. In this case, the printer 1 starts a self-diagnosis process for the cutter unit 5, and screens G3 to G5 in FIG. 4 are displayed in sequence.

[0042] In the first example, diagnostic processing is sequentially executed for each of the items "connection check," "cutter counter," "number of cutter errors," and "cutting speed," which are predefined as diagnostic items for the cutter unit 5. Screens G3 and G4 sequentially display text 201 indicating whether or not a malfunction has occurred as the diagnostic processing results for each item. The diagnostic process for "Connection check" is to check whether there is an electrical connection of the cutter unit 5. The diagnostic process for "Cutter counter" is to determine whether there is a malfunction based on the number of times (cumulative value) that the cutter unit 5 has cut labels PL. The diagnostic process for "Number of cutter errors" is to determine whether there is a malfunction based on the number of errors that have occurred in the cutter unit 5. The diagnostic process for "Cutting speed" is to determine whether there is a malfunction based on the cutting speed calculated from the measured values ​​of the rising and falling times of the movable blade 52 of the cutter unit 5. In the example shown on screen G4, the cutter counter indicates a normal value, but the number of cutter errors and the cutting speed (speed reduction) indicate abnormal values.

[0043] The diagnostic processing results for each item shown by text 201 on screen G4 are the results of diagnostic processing based on operation information indicating the current operating state of the cutter unit 5 and information on events (phenomena) that have occurred in the past with respect to the cutter unit 5 (event history information, which will be described later). For example, the diagnostic processing for "connection check" is an example of operation information indicating the current operating state of the cutter unit 5. The diagnostic processing for "cut speed" is a diagnostic result based on, for example, information on past cut speeds that have been periodically monitored, and is an example of fault information regarding the presence or absence of faults over time.

[0044] When button b1 is operated on screen G4, screen G5 including text 202 is displayed. Based on the operation information and fault information of cutter unit 5 displayed on screen G4, text 202 presents the user with an action to take with respect to the cutter unit 5 being diagnosed (in this example, contacting service). This allows the user to visually recognize the fault information and the action that the user should take.

[0045] In the second example, the item "Interface Diagnosis" is selected on screen G2. In this case, the printer 1 starts a self-diagnosis process for the communication unit of the printer 1, and screens G13 to G15 in FIG. 5 are displayed in sequence. In the second example, diagnostic processing is sequentially executed for each of a plurality of communication unit items, namely "USB," "LAN," "Wi-Fi (registered trademark)," "Bluetooth (registered trademark)," "RS-232C," and "EXT I / F," which are predefined as diagnostic items for the communication unit. Screens G13 and G14 sequentially display text 203 indicating whether or not a malfunction has occurred as the diagnostic processing results for each item.

[0046] In the second example, as in the first example, the diagnostic processing results for each item shown by text 203 on screen G14 are the results of diagnostic processing based on operation information indicating the current operating status of each communication unit and information on events (phenomena) that have occurred in the past for each communication unit (event history information, described below). Screen G14 only shows the diagnostic results (normal or abnormal) for each communication unit, but in printer 1, the results are based not only on the current operating status of the communication unit, but also on the results of, for example, periodically monitoring the status of the communication unit.

[0047] When button b1 is operated on screen G14, screen G15 including text 204 is displayed. The content of text 204 is determined based on the operation information and fault history information of each communication unit, and includes the content of an action for the user related to the communication unit to be diagnosed (in this example, checking the connection with the PC). At that time, the date on which the fault occurred for the specific communication unit (the date on which the communication unit had a connection failure) is identified and displayed. This allows the user to visually recognize the fault information and the action that the user should take.

[0048] As shown in Figures 4 and 5, when the printer 1 executes a self-diagnosis process for a target device, it acquires operation information indicating the current operating status of the target device and history information of events that have occurred in the past for the target device, and displays the self-diagnosis results. Events that have occurred in the past for the target device include, for example, the output value of a sensor that detects the status of the device, and measurement values ​​related to the operation of the device. The printer 1 can acquire fault information regarding the presence or absence of faults over time based on the current operating status and the history of events that have occurred in the past, and present this information to the user.

[0049] Next, the system configuration of the printer 1 will be described with reference to FIGS. Fig. 6 is a functional block diagram of the printer 1. Fig. 7 is a diagram showing an example of the data configuration of an event database included in the printer 1. As shown in Fig. 6, the printer 1 is broadly divided into a control system 10, a sensor group 20, and a communication unit group 30.

[0050] The control system 10 is a part that controls the main functions of the printer 1, and includes a control unit 11, a display control unit 12, a printing unit 13, a conveying unit 14, and a user interface 15. The control unit 11 includes a CPU 111 , a memory 112 , and a storage 113 . The CPU 111 (an example of a processor) executes programs (firmware and application programs) stored in the memory 112 to realize various functions of the printer 1. The memory 112 includes a RAM (Random Access Memory) that is a temporary storage device for processing by the CPU 111, and a ROM (Read Only Memory) in which programs are stored. The storage 113 (an example of a storage unit) is a nonvolatile storage device with a relatively large capacity, such as a flash memory, and stores an event database.

[0051] The display control unit 12 causes the display panel 3 (see FIG. 1) to display an image based on the display data sent from the control unit 11. The screens shown in FIGS. The printing unit 13 includes a drive circuit for selectively heating the multiple heating resistors (heating elements) of the thermal head 7 based on the printing data sent from the control unit 11, and causes the label PL to color due to the heat generated by the heating elements, thereby printing on the label PL. The transport unit 14 includes a drive circuit that drives a motor (not shown) based on a transport command sent from the control unit 11, and transports the continuous paper CP by an amount and in a direction (forward or reverse) according to the transport command. The user interface 15 includes an interface circuit for accepting touch inputs to buttons displayed on the display panel 3 and for accepting inputs to the input buttons 2 (physical keys).

[0052] The sensor group 20 includes various sensors mounted on the printer 1. The sensors mounted on the sensor group 20 include, but are not limited to, the label position detection sensor 21 shown in FIG. 2 , a substrate temperature sensor, an internal housing temperature and humidity sensor, a thermal head thermistor, a cutter sensor (the first cutter sensor and second cutter sensor described above), etc. The substrate temperature sensor is a temperature sensor that measures the temperature of the control board (chip) on which the control unit 11 is mounted. The internal housing temperature and humidity sensor is a temperature and humidity sensor that measures the temperature and humidity inside the housing of the printer 1. The thermal head thermistor is a temperature sensor that measures the temperature of the thermal head 7. The output values ​​(detected values) of each sensor included in the sensor group 20 are transmitted to the control system 10 periodically or irregularly.

[0053] The communication unit group 30 includes communication units of multiple communication methods that are installed in the printer 1. The communication units installed in the communication unit group 30 include, but are not limited to, a wireless LAN unit, a Bluetooth (registered trademark) unit, a 4G / LTE unit (a unit for mobile communication), etc.

[0054] In the printer 1, events that occur in the printer 1 are managed. An event refers to any of the various occurrences that occur in the printer 1 or in each device installed in the printer 1 from when the printer 1 is started until the power is shut off. In the printer 1, each event is managed along with the event type and the time when the event occurred. The event type is predefined according to the content of the event, and is one of "Information," "Warning," or "Error." Examples of events include the following: - Power-on by operating the power button (Event type: Information) System reboot (Event type: Information) Print command received (Event type: Information) - A power-off request was received (Event type: Information) - The temperature or voltage of a specific device reaches a warning level (Event type: Warning) - The temperature or voltage of a specific device reaches a dangerous level (Event type: Error) - The temperature or voltage of a specific device has returned to normal (Event type: Information) An error occurred for a specific device (Event type: Error)

[0055] Events that occur in the printer 1 may include an event for periodically obtaining the output values ​​of each sensor of the sensor group 20 (periodic event). Events that occur in the printer 1 may include periodic events that periodically acquire measurement values ​​related to the operation of each device installed in the printer 1. Measurement values ​​related to the operation of the device include, for example, the measurement values ​​of the rising and falling times of the movable blade 52 described above, and / or the cutting speed value calculated based on the rising and falling times, or a value indicating whether each communication unit is connected.

[0056] FIG. 7 shows an example of the data structure of the event database stored in the control system 10. As shown in FIG. FIG. 7 shows an example in which a periodic event for acquiring the output value of a substrate temperature sensor is recorded in the event database. Each record in the event database corresponds to a single event that has occurred, and includes values ​​for the fields "Event Name," "Event Type," "Details," and "Time." The value in the "Details" field may vary depending on the nature of the event, but in the example shown in FIG. 7, it is the output value (temperature value) of the substrate temperature sensor. The value in the "Time" field is the value of the time when the event occurred.

[0057] Next, the configuration of the application program (self-diagnosis application) 114 related to the self-diagnosis function of the printer 1 will be described with reference to the software function block diagram of FIG. The self-diagnostic application 114 includes a system monitoring module 115 and a self-diagnostic module 116 .

[0058] The system monitoring module 115 sequentially receives (acquires) events from a plurality of program modules and executes device information accumulation processing to record the contents of the events in an event database. The program modules from which the system monitoring module 115 acquires data include, but are not limited to, various system modules Ma, various sensor modules Mb, and various communication unit modules Mc. The various system modules Ma are program modules that monitor the operating status of system resources and processes executed by the CPU 111. The various sensor modules Mb are program modules that monitor the output values ​​of the corresponding sensors. The various communication unit modules Mc are program modules that monitor the operation of the corresponding communication units.

[0059] For example, the system monitoring module 115 periodically acquires information related to system resources, such as CPU load, memory usage, storage usage, and network usage, from various system modules Ma, and records it in an event database. The system monitoring module 115 periodically acquires the output values ​​of the corresponding sensors from the various sensor modules Mb, or records values ​​calculated based on the output values ​​of the sensors in the event database. The system monitoring module 115 periodically acquires measurements related to the operation of the corresponding communication unit from various communication unit modules Mc and records them in an event database. Examples of measurements related to the operation of the communication unit include received signal strength indicator (RSSI) and network packet information. The frequency at which sensor output values ​​and measurement values ​​relating to the operation of the communication unit are acquired is, for example, every 1 to 15 minutes, but can be changed as appropriate.

[0060] In one embodiment, the device information accumulation process includes an alarm generation process, which is described below.

[0061] The self-diagnosis module 116 is configured to execute a self-diagnosis process and output a diagnosis result when it receives a diagnosis request for a selected item in response to, for example, a user's operation on a self-diagnosis menu (see screen G2 in FIG. 3). In one embodiment, the self-diagnosis process includes the following processes (i) and (ii): (i) A process of acquiring event history information (event history information) from an event database, the event history information including one or more events that have occurred in the past with respect to the device to be processed and information on the time when each event occurred. (ii) A process of acquiring (identifying) failure information regarding the presence or absence of failures over time of the device based on the acquired event history information and operation information indicating the current operation state of the device to be processed.

[0062] In one embodiment, in process (i), the self-diagnosis module 116 acquires event history information by extracting from the event database records corresponding to one or more events related to the device being processed. For example, in cutter unit diagnosis, which is a self-diagnosis targeting the cutter unit 5, event history information (cut speed history, described below) of one or more cutter error occurrence events and one or more cut speed acquisition events is acquired from the event database as information on events related to the cutter unit 5. In one embodiment, the event history information is obtained by extracting from the event database one or more events whose "time" field value falls within a predetermined period, such as within one week or two weeks from the present.

[0063] When executing self-diagnosis processing, the self-diagnosis module 116 acquires operation information indicating the current operation status of the device to be processed from the various modules Ma, Mb, and Mc shown in Fig. 8 as well as other program modules and the memory 112. The operation information may vary depending on the device to be processed, but may include, for example, the following information: - Continuous operation time of a specific device - Interface link status (Up or Down) of each communication unit - Number of bytes of data received by each communication unit after power-on ·Substrate temperature Thermal head temperature Thermal head voltage monitor signal - Power supply abnormality monitor signal for cutter unit connector -Cutter unit connection status -Current number of cuts by the cutter unit For example, in the cutter unit diagnosis, information on whether the cutter unit is connected or not and information on the current number of cuts made by the cutter unit are acquired as operation information.

[0064] In one embodiment, in process (ii), the self-diagnosis module 116 identifies the date and time when a change occurred in an event that occurred in the device being processed based on the event history information. In this case, as shown in screen G15 of Fig. 5, the failure information presented to the user includes information about the identified date and time. This allows, for example, the date on which a failure occurred in the target device in the past to be identified, allowing the user to appropriately estimate the cause of the failure.

[0065] In one embodiment, in process (ii), the self-diagnosis module 116 calculates a statistical value based on the number of times a predetermined event has occurred for the device being processed based on the event history information. In this case, as shown in screen G5 of Fig. 4, the failure information presented to the user includes information on the calculated statistical value. This allows the user to obtain statistical values ​​related to failures, such as the frequency of failures and the probability of failures occurring for the target device, thereby enabling the user to understand failure trends and appropriately estimate the cause of the failure. In the example shown on screen G5 in Fig. 4, the calculated statistical value is the frequency of a specific event, but is not limited to this and may be other statistical values ​​such as an average value or a probability. Also, as shown on screen G5 in Fig. 4, the statistical value may be calculated limited to a specific period (for example, the most recent week). For example, by limiting the period that forms the basis of the event history information to the most recent period, it is possible to grasp the recent tendency of occurrence of failures in the device to be processed. It is also preferable to display the calculated statistical values ​​as a statistical graph such as a histogram. For example, the number of failures occurring one week prior, two weeks prior, and three weeks prior may be displayed as a histogram.

[0066] Referring to FIG. 8, the boot loader 117 is executed immediately after the printer 1 is started, performs diagnostic processing on devices that cannot be diagnosed while the printer 1 is running, and stores the diagnostic results (test results) in the memory 112. For example, the display panel 3 and the temperature sensor themselves are occupied by a program module assigned to the operating system (OS; an example of system software) while the printer 1 is running, and therefore cannot be accessed by the self-diagnostic application. Therefore, immediately after the printer 1 is started, the boot loader 117 performs diagnostic processing on devices that cannot be diagnosed while the printer 1 is running, and stores the test results in the memory 112. The system monitoring module 115 records the test results in the event database after the OS is loaded into RAM and becomes executable. This allows devices that cannot be tested after the printer 1 is running to be tested before the printer 1 is started and the test results to be obtained. The results of the diagnosis performed by the boot loader 117 are recorded in the event database as diagnostic events in association with the time of the diagnosis.

[0067] Next, the processing executed by the self-diagnosis application 114 will be described in more detail with reference to the flowcharts of FIGS.

[0068] FIG. 9 is a flowchart showing the device information accumulation process executed by the system monitoring module 115. 9, the system monitoring module 115 sequentially receives events that occur in the printer 1 or in each device within the printer 1 from each of a plurality of program modules, including modules Ma, Mb, and Mc in FIG. 8 (step S10). The system monitoring module 115 may receive events periodically or irregularly, such as error events or print command reception. Next, the system monitoring module 115 records the received events together with the time of reception in an event database (step S20). Event types are predefined depending on the event. In step S20, a record containing the event name, event type, event details, and time (received time) is added to the event database.

[0069] In one embodiment, the system monitoring module 115 executes an alarm issuing process each time an event is received (step S30). In the alarm issuing process, the system monitoring module 115 acquires event history information corresponding to the event that has occurred from the event database, and determines whether to issue an alarm (output a warning) based on the acquired event history information. This allows the user to receive a warning for a specific device at an appropriate time, as needed, based on the history of events that have occurred in the past for that device.

[0070] A specific example of the alarm issuance process in step S30 will be described with reference to the flowchart in Fig. 10. Fig. 10 is a flowchart showing the alarm issuance process when the received event is a paper cut event. A paper cut event is an event in which the cutter unit 5 cuts the continuous paper CP. The system monitoring module 115 receives a paper cut event every time the cutter unit 5 cuts the continuous paper CP from a program module that monitors whether or not the cutter unit 5 has performed a paper cut operation.

[0071] 10, when the system monitoring module 115 receives a paper cut event (step S32: YES), it acquires the history of the cutting speed of the cutter unit 5 (cutting speed history) as event history information from the event database (event DB) (step S33). The system monitoring module 115 calculates the average cutting speed for each day from the acquired cutting speed history (step S34). If the cutting speed is equal to or less than a predetermined value, this means that the amount of glue accumulated on the movable blade 52 of the cutter unit 5 is large and that cleaning of the movable blade 52 is necessary. Therefore, if the cutting speed is equal to or less than the predetermined value (step S35: YES), the system monitoring module 115 issues an alarm (step S36). In this case, the system monitoring module 115 displays the alarm on the display panel 3, for example, so that the user can recognize it. By executing the alarm issuing process, the user can timely recognize whether or not a specific device (the cutter unit 5 in the example of FIG. 10) has malfunctioned over time, without having to perform any special operation.

[0072] FIG. 11 is a flowchart showing the self-diagnosis process executed by the self-diagnosis module 116. 11, the self-diagnosis module 116 executes self-diagnosis processing for an item selected by the user, for example, in response to an operation on the self-diagnosis menu (see screen G2 in FIG. 3) by the user. First, the self-diagnosis module 116 collects (obtains) event history information about events related to the device corresponding to the selected item from the event database (step S40). The self-diagnosis module 116 also collects (obtains) operation information indicating the current operation status of the device to be processed from at least one of a plurality of program modules including modules Ma, Mb, and Mc in FIG. 8 (step S50). In the self-diagnosis process, the order of steps S40 and S50 may be reversed from that shown in FIG.

[0073] Next, the self-diagnosis module 116 performs a counting process to count the event history information acquired in step S40 (step S60). The counting process includes counting the number of specific events and calculating statistical values ​​in order to determine whether or not the device being processed has malfunctioned over time. The self-diagnosis module 116 performs a malfunction determination process based on the data obtained by the counting process (e.g., the number of specific events and statistical values) (step S70), and generates text indicating the self-diagnosis result based on the result of the malfunction determination process and outputs it to the display panel 3 (step S80).

[0074] Next, a specific application example of the self-diagnosis processing of FIG. 11 will be described with reference to FIGS. 12 and 13 are flowcharts showing the self-diagnosis process for performing cutter unit diagnosis, and show the correspondence between each process and steps S40, S50, S60, and S70 in FIG.

[0075] The self-diagnosis module 116 first obtains event history information (cutter error history) about error events of the cutter unit 5 from the event database (step S42), and then obtains event history information (cutting speed history) about the cutting speed of the cutter unit 5 (step S44). Next, the self-diagnosis module 116 acquires operation information for the cutter unit 5. Specifically, the self-diagnosis module 116 checks whether the cutter unit 5 is connected (step S52), and reads the current number of cuts made by the cutter unit 5 (step S54). Here, the information on whether the cutter unit 5 is connected may be acquired from another program module. For example, the other program module may sequentially write the number of cuts made by the cutter unit 5 to the memory 112 while the printer 1 is operating, and the self-diagnosis module 116 may read the number of cuts from the memory 112.

[0076] The self-diagnosis module 116 performs the following process as an event counting process. The self-diagnosis module 116 counts the number of cutter errors (cumulative value) from the cutter error history acquired in step S42 (step S62), and also counts the number of cutter errors from one week ago and two weeks ago (step S64). Furthermore, the self-diagnosis module 116 calculates the average cutting speed per day from the cutting speed history acquired in step S44 (step S66).

[0077] Next, the self-diagnosis module 116 executes the following process as a fault determination process on the data obtained in steps S62 to S64. If the check result of step S52 is "connected" (step S72: YES), the self-diagnostic module 116 determines that the connection status is acceptable (step S73a), and if the check result is "not connected" (step S72: NO), the self-diagnostic module 116 determines that the connection status is unacceptable (step S73b). If the current number of cuts acquired in step S54 is equal to or less than a predetermined value (step S74: YES), the self-diagnosis module 116 determines that the number of cuts is acceptable (step S75a), and if it exceeds the predetermined value (step S74: NO), it determines that the number of cuts is unacceptable (step S75b).

[0078] Based on the number of cutter errors acquired in steps S62 and S64, if the current number of cutter errors is equal to or less than a predetermined value and has not increased within two weeks (step S76: YES), the self-diagnosis module 116 determines that the number of cutter errors is pass (step S77a). Conversely, if the current number of cutter errors exceeds the predetermined value or has increased within two weeks (step S76: NO), the self-diagnosis module 116 determines that the number of cutter errors is fail (step S77b). Note that "if it has not increased within two weeks" means that the current number of cutter errors has not increased compared to the number of cutter errors two weeks ago. If the average value of the cutting speed obtained in step S66 is equal to or greater than a predetermined value (step S78: YES), the self-diagnosis module 116 determines that the cutting speed is acceptable (step S79a), and if it is less than the predetermined value (step S78: NO), it determines that the cutting speed is unacceptable (step S79b).

[0079] Finally, the self-diagnosis module 116 generates text indicating the diagnosis result of the cutter unit diagnosis based on the failure determination processing result obtained in steps S72 to S79b, and outputs the generated text to the display panel 3 (step S80). For example, screens G4 and G5 in FIG. 4 display the respective determination results of steps S72, S74, S76, and S78. When generating the text 202 on screen G5, the values ​​acquired or calculated in steps S42 to S66 are appropriately processed according to the nature of the failure. For example, when generating the text 202 on screen G5 saying "35 increases in the past week," the number of cutter errors from one week ago is subtracted from the current number of cutter errors.

[0080] The above is the process when the cutter unit diagnosis is executed as the self-diagnosis process. In the self-diagnosis process of Fig. 11, it is preferable to adjust the content of the process for the event history information in the event counting process (step S60) so that an appropriate failure judgment can be made depending on the device to be processed. For example, in the interface diagnosis illustrated in Fig. 5, data such as the start date, frequency, probability, etc. of a state where there is no connection to an external device can be calculated based on event history information about connection events of a specific communication unit to an external device.

[0081] As described above, the printer 1 records in the event database events that have occurred in the past for devices installed in the printer 1 in association with information about the time of occurrence. Furthermore, in response to user operations, the printer 1 obtains event history information for the device to be diagnosed from the event database, and obtains and displays failure information regarding the presence or absence of failures over time for the device to be diagnosed based on the event history information and operation information indicating the current operating status of the device to be diagnosed. Therefore, on-site users such as service personnel and operators can determine the status of the device not only based on whether or not there is a current malfunction in the device, but also based on the current operating status of the device and the history of events that have occurred in the past, enabling them to appropriately resolve (troubleshoot) malfunctions that have occurred in the device. For example, if an error has been occurring on a specific device since a certain date, or if the frequency of errors has increased over the past two weeks, it may be possible to efficiently resolve malfunctions that have occurred in the device by correlating the occurrence of the error with information about the operating status and environment of the printer 1 that is known to on-site users.

[0082] In one embodiment, the CPU 111 records the processing result (fault determination processing result) of step S70 in FIG. 11 in the storage 113 as a fault log database in association with the individual identification information of the device being processed. FIG. 14 shows an example of the data configuration of the fault log database. In the fault log database shown in FIG. 14, an individual ID (an example of individual identification information) and a fault log (a past fault determination processing result) are associated with each device. In FIG. 14, the number of fault logs for one device is not limited to one, and multiple fault logs may exist. Recording the fault log database ensures traceability for individual devices. For example, even if a device (e.g., thermal head 7) is replaced with another printer, the user can read the fault log database to understand the history of events that have occurred in the device and fault information.

[0083] Many devices within the printer 1 are assigned individual IDs during the manufacturing stage or before being incorporated into the printer 1, and these individual IDs can be managed directly by the printer 1. For example, individual IDs are set for the control board, thermal head, and cutter unit during the manufacturing stage, and unique identification information (such as a MAC (Media Access Control) address, BD (Bluetooth (registered trademark) Device) address, or IMEI (International Mobile Equipment Identity)) is also assigned to the communication unit.

[0084] In one embodiment, the printer 1 is communicably connected via a network to a management server that manages the printer 1. In this case, the management server sequentially obtains the results of the self-diagnosis process or the failure log from the printer 1 as needed. The management server may also sequentially obtain and store the event database from the printer 1. By centrally managing the results of the self-diagnosis process and the failure log of the printer 1 in the management server, it becomes possible to grasp with greater accuracy the tendency of device failures that tend to occur in specific models of printers. In particular, when associating an individual ID with a failure log for each device, it is preferable that the failure log database shown in Fig. 14 be managed centrally by a management server. By configuring multiple printers to be able to communicate with the management server, even if a specific device is replaced from one printer to another, the user of the other printer can easily access past failure information, etc. for that device from the management server.

[0085] In one embodiment, a help desk terminal or a host computer terminal is communicably connected to the printer 1 via a network. In this case, the help desk terminal or the host computer terminal is configured to issue a request via the network to execute a self-diagnosis process for any item in the self-diagnosis menu of the printer 1, and to obtain and display the results of the self-diagnosis process from the printer 1. This allows remote support for the user of the printer 1 regarding a malfunction that occurs in the printer 1.

[0086] One embodiment is an information processing system including an information processing terminal such as a help desk terminal or a host computer terminal that can communicate with the printer 1 via a network. In this case, the printer and the information processing terminal may exchange data via a server rather than communicating directly. As shown in FIGS. 3 to 5, an application is installed in the information processing terminal to implement a GUI that instructs the execution of a self-diagnostic function and displays the execution results of the self-diagnostic function. The information processing terminal displays a self-diagnostic menu and requests the printer 1 to execute self-diagnostic processing for an item selected in response to a user operation. In response to the request from the information processing terminal, the CPU of the printer 1 executes self-diagnostic processing for the device corresponding to the selected item. The content of the self-diagnostic processing is the same as that shown in FIGS. 9 to 13. The information processing terminal receives the execution results of the self-diagnostic processing from the printer 1 and displays them. The above-described system allows an administrator or a help desk staff member to remotely resolve any malfunctions that occur in the devices within the printer.

[0087] One embodiment is an information processing system including a server capable of communicating with the printer 1 via a network, and an information processing terminal such as a help desk terminal or a host computer terminal capable of communicating with the server via the network. In this system, an event database is managed in a server. That is, the server has a storage unit that stores the event database. The printer 1 transmits events to the server by uploading the event to the server every time an event occurs in a device within the printer 1, or by uploading events that occur in a device within the printer to the server at predetermined intervals. When the server receives an event from the printer 1, it records the received event in the event database in order. As shown in Figs. 3 to 5, an application for realizing a GUI that instructs execution of a self-diagnostic function and displays the execution results of the self-diagnostic function is installed in the information processing terminal. The information processing terminal displays a self-diagnostic menu and requests the server to execute self-diagnostic processing for an item selected in response to a user operation. In response to the request from the information processing terminal, the processor of the server executes self-diagnostic processing for the device corresponding to the selected item. The content of the self-diagnostic processing is the same as that shown in Figs. 9 to 13. The information processing terminal receives the execution results of the self-diagnostic processing from the server and displays them. The above-mentioned system allows administrators and help desk staff to remotely resolve malfunctions that occur in devices within a printer, and has the advantage of improving the accuracy of malfunction information because events that occur in devices within each of multiple printers can be centrally managed on a server.

[0088] In one embodiment, a method for processing information in a printer 1 is disclosed, comprising the following steps. (I) A step of recording events (phenomena) that have occurred in the past for devices installed in the printer 1 in the event database of the storage 113 of the printer 1 in association with information on the time of occurrence. (II) acquiring, in response to a user operation, event history information from an event database, the event history information including information on one or more past events that have occurred in the device and the time at which each event occurred; (III) A step of acquiring failure information regarding the presence or absence of a failure of the device over time based on the event history information and operation information indicating the current operation state of the device. (IV) a step of displaying the failure information on the display panel 3 of the printer 1;

[0089] In one embodiment, a program for causing a computer to execute the above steps (I) to (III) is disclosed. Such a program is implemented as a self-diagnostic application executed by the CPU 111 of the printer 1, for example.

[0090] Although the printer, printer information processing method, and program according to the present invention have been described above, the present invention is not limited to the above-described embodiments. Furthermore, various improvements and modifications can be made to the above-described embodiments without departing from the spirit and scope of the present invention. [Explanation of symbols]

[0091] 1...Printer 2...Input button 3...Display panel 4...Issuing port 5...Cutter unit 51…Fixed blade 52…Movable blade 7...Thermal head 8...Platen roller 9...Auxiliary roller 10...Control system 11...Control unit 111...CPU, 112...memory, 113...storage, 114...self-diagnostic application, 115...system monitoring module, 116...self-diagnostic module, 117...boot loader 12...Display control unit 13...Printing section 14...Transport section 15...User Interface 20...Sensor group 21...Label position detection sensor 30...Communication units 102...Settings button 201, 202, 203, 204...Text CP...Continuous paper PL…Label PM…Paper R...Roll paper

Claims

1. a storage unit that stores a database in which events that have occurred in the past with respect to devices installed in the printer are associated with information on the time of occurrence; a processor that executes a self-diagnosis process for the device in response to a user operation; a display unit that displays the execution result of the self-diagnosis processing, The self-diagnosis process includes: obtaining, from the database, event history information including one or more past events that have occurred on the device and information on the time of occurrence of each event; and acquiring failure information regarding the presence or absence of a failure of the device over time based on the event history information and operation information indicating the current operation state of the device; Printer.

2. the self-diagnosis process includes identifying a date and time when an event that occurred in the device changed based on the event history information; The failure information includes information regarding the specified date and time. The printer according to claim 1 .

3. the self-diagnosis processing includes calculating a statistical value based on the number of times a predetermined event has occurred in the device based on the event history information; the failure information includes information about the statistical value; The printer according to claim 1 .

4. The processor: Each time an event occurs in the device, the event is recorded in the database in association with information on the time of occurrence; acquiring, from the database, event history information including one or more events that have occurred in the past with respect to the device and information on the time of occurrence of each event, and determining whether to output a warning based on the acquired event history information; The printer according to claim 1 .

5. the processor periodically acquires an output value of a sensor that detects a state of the device or a measurement value related to the operation of the device as an event occurring in the device, and records the acquired output value or the measurement value in the database; A printer according to any one of claims 1 to 4.

6. The processor records the failure information in the storage unit in association with individual identification information of the device. A printer according to any one of claims 1 to 4.

7. the processor causes the display unit to display, as a result of the execution of the self-diagnosis process, text indicating an action that a user should take with respect to the device together with the fault information. A printer according to any one of claims 1 to 4.

8. The processor: By executing a boot loader immediately after starting the printer, a test process is performed on the device, and the results of the test process are recorded; After the printer system software is enabled, recording the results of the inspection process in the database. A printer according to any one of claims 1 to 4.

9. An information processing method for a printer, comprising: a step of recording events that have occurred in the past with respect to a device installed in the printer in association with information on the time of occurrence in a database of a storage unit of the printer; acquiring, from the database in response to a user operation, event history information including one or more events that have occurred in the past with respect to the device and information on the time at which each event occurred; acquiring failure information regarding whether or not the device has failed over time based on the event history information and operation information indicating the current operation state of the device; displaying the fault information on a display unit of the printer; and a printer information processing method.

10. A program to be installed in a printer, a step of recording events that have occurred in the past with respect to a device installed in the printer in a database of a storage unit of the printer in association with information on the time of occurrence; a step of acquiring, in response to a user operation, event history information from the database, the event history information including information on one or more past events that have occurred in the device and the time at which each event occurred; a step of acquiring failure information regarding the presence or absence of a failure of the device over time based on the event history information and operation information indicating the current operation state of the device; a step of displaying the failure information on a display unit of the printer; A program that causes a computer to execute the following.

11. An information processing system including a server capable of communicating with a printer and an information processing terminal capable of communicating with the server, The server a storage unit that stores a database in which events that have occurred in the past with respect to a device installed in the printer are associated with information on the time of occurrence; a processor that executes a self-diagnosis process for the device in response to a request from the information processing terminal; The self-diagnosis process includes: obtaining, from the database, event history information including one or more past events that have occurred on the device and information on the time of occurrence of each event; and acquiring failure information regarding the presence or absence of a failure of the device over time based on the event history information and operation information indicating the current operation state of the device; the information processing terminal acquires the execution result of the self-diagnosis processing from the server and displays it. Information processing system.

Images