Maintenance notification system and control method

Abstract

To provide a technique for easily making a maintenance plan.SOLUTION: A maintenance notification system comprises a notification unit, a notification counter, a unit counter, and a control unit. The control unit comprises a first notification control unit. When the count value counted by the unit counter is greater than or equal to a prescribed value and the time counted by the notification counter indicates a notification timing, the first notification control unit causes the notification unit to execute the maintenance guidance of the unit. When the count value counted by the unit counter is greater than or equal to the prescribed value and the time counted by the notification counter does not indicate the notification timing, the first notification control unit causes the notification unit not to execute the maintenance guidance of the unit.SELECTED DRAWING: Figure 3

Description

Technical Field

[0001] This specification relates to a maintenance notification system that notifies guidance for maintenance of units used in an implementation device.

Background Art

[0002] Patent Document 1 discloses a component mounting device that mounts electronic components on a substrate. The head unit of the component mounting device is replaceable, and a plurality of head units can be mounted on the component mounting device. The component mounting device stores operation time data for each of the plurality of head units. The user grasps the usage frequency of each head unit and performs maintenance on each head unit.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In order to suppress non-implementation of maintenance, a system that notifies guidance for maintenance is desired. For example, it is assumed that the component mounting device of Patent Document 1 is configured to notify maintenance of each head unit when the operation time of each head unit is longer than a predetermined period.

[0005] In this configuration, the timing at which the operating time of the first head unit among the multiple head units exceeds a predetermined period is determined independently of the timing at which the operating time of the second head unit among the multiple head units exceeds a predetermined period. In other words, the timing of the maintenance notification for the first head unit is independent of the timing of the maintenance notification for the second head unit. For this reason, it is difficult for the user to predict when maintenance notifications will be issued for each of the multiple head units. When it is difficult to predict when maintenance notifications will be issued, it becomes difficult for the user to plan maintenance.

[0006] This specification provides techniques to facilitate maintenance planning. [Means for solving the problem]

[0007] The maintenance notification system disclosed herein comprises: a notification unit (14) that notifies of maintenance instructions for at least one unit among a plurality of units used in a mounting device for mounting components onto a substrate; a notification counter (34) that counts the time for measuring the notification timing, which occurs repeatedly at predetermined intervals and for which the notification unit notifies the instructions; a unit counter (36) that counts a count value for each of the plurality of units, indicating the usage status of the unit while it is being used in the mounting device; and a control unit (32) that controls the notification unit, wherein the control unit counts the unit counter The system includes a first notification control unit (32) which, if the count value is greater than or equal to a predetermined value indicating that maintenance of the unit corresponding to the unit counter is recommended, and the time counted by the notification counter indicates the notification timing, causes the notification unit to execute the notification for maintenance of the unit corresponding to the unit counter; and if the count value counted by the unit counter is greater than or equal to the predetermined value, and the time counted by the notification counter does not indicate the notification timing, does not cause the notification unit to execute the notification for maintenance of the unit corresponding to the unit counter.

[0008] Furthermore, this specification also discloses a control method for controlling a notification unit (14) that notifies the user of maintenance instructions for at least one of a plurality of units used in a mounting device for mounting components onto a substrate. The control method includes a notification counter (34) that counts the time for measuring the notification timing at which the notification unit notifies the guidance, wherein the notification timing occurs repeatedly at a predetermined cycle, and a unit counter (36) that counts a count value for each of the plurality of units that indicates the usage status of the unit while the unit is being used in the mounting device, wherein the control method includes the step of causing the notification unit to execute the guidance for maintenance of the unit corresponding to the unit counter when the count value counted by the unit counter is greater than or equal to a predetermined value indicating that maintenance of the unit corresponding to the unit counter is recommended, and the time counted by the notification counter indicates the arrival of the predetermined cycle, and not causing the notification unit to execute the guidance for maintenance of the unit corresponding to the unit counter when the count value counted by the unit counter is greater than or equal to the predetermined value, and the time counted by the notification counter does not indicate the arrival of the predetermined cycle.

[0009] With the above configuration, maintenance notifications for each of the multiple units are sent at predetermined intervals and not at any other time. Therefore, users can easily predict when they will be notified of maintenance for each of the multiple units, making it easier for them to plan their maintenance. [Brief explanation of the drawing]

[0010] [Figure 1] A schematic diagram of a component mounting device is shown. [Figure 2] A block diagram of the component mounting device is shown. [Figure 3] This shows a specific case C1 that can be realized by a component mounting device. [Figure 4] This section shows a specific case C2 that can be realized using a component mounting device. [Figure 5] A comparative example is shown. [Modes for carrying out the invention]

[0011] The main features of the embodiments described below are listed below. Note that the technical elements described below are independent technical elements that exhibit technical usefulness individually or in various combinations, and are not limited to the combinations described in the claims at the time of filing.

[0012] (Feature 1) The control unit may further include a second notification control unit (32) that, when there is a unit whose count value counted by the unit counter exceeds a predetermined upper limit which is greater than the predetermined value, causes the notification unit to execute the notification for maintenance of the unit corresponding to the unit counter, regardless of whether the time counted by the notification counter indicates the notification timing.

[0013] A counter value exceeding the upper limit indicates that the unit has not undergone maintenance for a relatively long period of time. The above configuration can prevent the unit from remaining without maintenance for an extended period.

[0014] (Feature 2) For each of the multiple maintenance items, a predetermined value is set to indicate that the maintenance indicated by that maintenance item is recommended. If the count value is greater than or equal to the predetermined value set for a specific maintenance item among the plurality of maintenance items, and the time counted by the notification counter indicates the notification timing, the notification unit may be instructed to execute the maintenance guidance indicated by the specific maintenance item.

[0015] According to the above configuration, it is possible to execute a notification suitable for a situation where there are a plurality of maintenance items (for example, a situation where there is maintenance at a first location within the unit and maintenance at a second location different from the first location within the unit).

Embodiment

[0016] (Component mounting device 2; FIGS. 1 and 2) The component mounting device 2 is a device that manufactures a circuit board by mounting electronic components on a substrate. The component mounting device 2 includes a mounting mechanism 12, a cassette 16, a notification unit 14, a control device 30, and a support base 40.

[0017] The cassette 16 is detachable from the component feeder 100. The component feeder 100 accommodates a plurality of electronic components. An ID "f01" is assigned to the component feeder 100.

[0018] The cassette 16 is detachable from the component feeder 100 and can be replaced with a component feeder 102. An ID "f02" is assigned to the component feeder 102. One of a plurality of component feeders including the component feeders 100 and 102 is mounted on the cassette 16. When a specific component feeder (for example, 100) is mounted on the cassette 16, the component mounting device 2 acquires an ID (for example, "f01") from the specific component feeder. The component mounting device 2 recognizes the component feeder mounted on the cassette 16 based on the acquired ID. Although a plurality of cassettes including the cassette 16 are provided in the component mounting device 2, only one cassette 16 is shown in the figure, and the description of other cassettes is omitted. In the production of a circuit board, some of the plurality of cassettes may be used, or all of the plurality of cassettes may be used.

[0019] The mounting mechanism 12 mounts the electronic components supplied from a component feeder (e.g., 100) onto the substrate on the support base 40. At the tip of the mounting mechanism 12, a nozzle 12a for adsorbing the electronic components supplied from the component feeder is attached. There are various types of nozzles 12a. Depending on the type of the electronic component to be adsorbed, a specific type of nozzle 12a is selected from among the various nozzles 12a.

[0020] The notification unit 14 notifies various guides. The notification unit 14 is, for example, a display. In a modification, the notification unit 14 may be, for example, a speaker that outputs voice guidance, a lamp that lights up a warning lamp, or the like.

[0021] The control device 30 controls each part 12, 14, 16, 40, etc. of the component mounting device 2. The control device 30 is composed of a CPU, a memory, etc. The control device 30 further includes a notification counter 34 and a unit counter 36, and a notification program 32 and an upper limit period 38 are stored in the memory of the control device 30. The notification counter 34 counts the time for the notification unit 14 to notify the maintenance guide. When the time counted by the notification counter 34 arrives at the notification timing that repeats at a predetermined cycle (e.g., 100 hours), the control device 30 causes the notification unit 14 to execute the maintenance guide. In other words, the notification counter 34 counts the time for measuring the notification timing. The counting of the time by the notification counter 34 is started, for example, together with the start of the use of the component mounting device 2. Also, for example, the counting of the time by the notification counter 34 may be started together with the initialization of the component mounting device 2.

[0022] The unit counter 36 counts the usage period of a parts feeder (e.g., 100). The usage period represents the total period during which the parts feeder is mounted on the cassette 16 and is actually in operation after maintenance has been performed on the parts feeder. The usage period is reset when maintenance is performed on the parts feeder. In a modified example, the usage period represents the total period during which the parts feeder is mounted on the cassette 16, and may include periods during which the parts feeder is mounted on the cassette 16 but temporarily stopped. The unit counter 36 may also be linked to a system (not shown) that manages whether or not maintenance is performed. The component mounting device 2 may also manage whether or not maintenance is performed.

[0023] For example, if part feeder 100 is mounted on cassette 16 among multiple part feeders, the unit counter 36 of part feeder 100 (i.e., the counter indicating the usage period of ID "f01") and the notification counter 34 will perform counting. The notification counter 34 will perform counting regardless of which of the multiple part feeders is mounted on cassette 16.

[0024] The CPU of the control device 30 performs the following processing according to the notification program 32. The CPU determines whether or not to notify the maintenance of the parts feeder when the time counted by the notification counter 34 indicates a notification timing. Specifically, the CPU determines for each of the multiple unit counters 36 corresponding to multiple parts feeders whether the usage period counted by the unit counter 36 is greater than or equal to a predetermined period (e.g., 100 hours). The predetermined period is the period during which maintenance of the parts feeder is recommended. If the CPU determines that the usage period counted by a particular unit counter 36 (e.g., the unit counter 36 of parts feeder 100) is greater than or equal to the predetermined period, it causes the notification unit 14 to execute a maintenance notification for the unit corresponding to the particular unit counter 36 (e.g., parts feeder 100). On the other hand, if the CPU determines that the usage period counted by a particular unit counter 36 is less than the predetermined period, it does not cause the notification unit 14 to execute a maintenance notification for the unit corresponding to the particular unit counter 36. Here, the "predetermined period" is set in advance by the vendor of the parts mounting device 2. The "specified period" may be set by the user.

[0025] Furthermore, the upper limit period 38 indicates the upper limit for each usage period, for example, 180 hours. The CPU of the control device 30 forcibly notifies the user of maintenance for the component feeder if the usage period exceeds the upper limit period, regardless of whether the time counted by the notification counter 34 indicates the notification timing. The upper limit period 38 is set in advance by the vendor of the component mounting device 2.

[0026] (Specific case C1; Figure 3) A specific case C1 in which the CPU of the control device 30 executes according to the notification program 32 will be described below. In the following, the process executed by the CPU of the control device 30 according to the notification program 32 will be described with the notification program 32 as the main focus.

[0027] In this case, after the parts feeder 100 (i.e., ID "f01") operates for 70 hours, the parts feeder 102 (i.e., ID "f01") is mounted on the cassette 16, and the parts feeder 102 operates for 80 hours. Subsequently, the parts feeders 100 and 102 are mounted on the cassette 16 alternately, with the parts feeder 100 operating for 60 hours and then another 60 hours, and the parts feeder 102 operating for 90 hours and then another 80 hours.

[0028] The notification program 32 determines whether the usage period of unit counter 36 with ID "f01" (hereinafter referred to as "usage period "f01"") is 100 hours or longer, when the time counted by the notification counter 34 indicates the notification timing of "100 hours". Currently, the usage period "f01" is 70 hours, which is less than the predetermined period of "100 hours". The notification program 32 decides not to notify the notification unit 14 of the maintenance of parts feeder 100. Furthermore, the notification program 32 determines whether the usage period of unit counter 36 with ID "f02" (hereinafter referred to as "usage period "f02"") is 100 hours or longer. Currently, the usage period "f02" is 30 hours, which is less than the predetermined period of "100 hours". The notification program 32 decides not to notify the notification unit 14 of the maintenance of parts feeder 102.

[0029] Next, the notification program 32 determines whether the usage period "f01" is greater than or equal to the predetermined period "100 hours" when the time counted by the notification counter 34 indicates the next notification timing "200 hours". At this point, the usage period "f01" is 120 hours (i.e., 70 + 50 hours), which is greater than or equal to the predetermined period "100 hours". The notification program 32 decides to notify the notification unit 14 of the maintenance of the parts feeder 100. Then, the notification program 32 resets the usage period "f01" when the maintenance of the parts feeder 100 is performed. Furthermore, the notification program 32 determines whether the usage period "f02" is greater than or equal to the predetermined period "100 hours". At this point, the usage period "f02" is 80 hours, which is less than the predetermined period "100 hours". The notification program 32 decides not to notify the notification unit 14 of the maintenance of the parts feeder 102.

[0030] Next, the notification program 32 determines whether the usage period "f01" is greater than or equal to the predetermined period "100 hours" when the time counted by the notification counter 34 indicates the next notification timing "300 hours". The usage period "f01" was reset when maintenance was performed at the notification timing "200 hours". Therefore, the notification program 32 determines that the usage period "f01" is less than the predetermined period "100 hours" and decides not to notify the notification unit 14 of the maintenance of the parts feeder 100. Furthermore, the notification program 32 determines whether the usage period "f02" is greater than or equal to the predetermined period "100 hours". At this point, the usage period "f02" is 170 hours (80 + 90 hours), which is greater than or equal to the predetermined period "100 hours". The notification program 32 decides to notify the notification unit 14 of the maintenance of the parts feeder 102. Then, the notification program 32 resets the usage period "f02" when maintenance is performed on the parts feeder 102.

[0031] For example, a comparative example without a notification counter 34 can be considered. In this comparative example, the notification program 32 notifies the user of maintenance for parts feeder 100 when the usage period "f01" exceeds a predetermined period of "100 hours", and notifies the user of maintenance for parts feeder 102 when the usage period "f02" exceeds a predetermined period of "100 hours". Figure 5 shows a specific case of the comparative example, in which parts feeders 100 and 102 are used according to the same schedule as in Figure 3.

[0032] As shown in Figure 5, in the comparative example, maintenance of parts feeder 100 is announced at 180 hours. Next, maintenance of parts feeder 102 is announced at 230 hours, and then again at 390 hours. As shown in Figure 5, in the comparative example, the maintenance announcements are disorganized. Users have to deal with the disorganized maintenance announcements, and there is a possibility that users may have to stop the production line. In addition, the disorganized maintenance announcements make it difficult for users to plan maintenance.

[0033] As shown in Figure 3, according to the configuration of this embodiment, maintenance for each of the multiple parts feeders is announced when the time counted by the notification counter 34 indicates a notification timing. On the other hand, if the time counted by the notification counter 34 does not indicate a notification timing, maintenance for any of the multiple parts feeders is not announced. Therefore, users can prepare for maintenance in advance in accordance with the maintenance announcements that are notified according to a predetermined cycle, making it easier to plan maintenance.

[0034] The maintenance notified by the notification program 32 is, for example, cleaning of the component feeder or the nozzle 12a that picks up electronic components, and is maintenance that should be performed at relatively short intervals. Even if such maintenance is performed a little later than the predetermined period of "100 hours", it will not have a significant impact on the manufacturing of circuit boards by the component mounting device 2. In this embodiment, the ease with which the user can plan maintenance is prioritized over strict notification within the predetermined period of "100 hours".

[0035] Furthermore, maintenance that should be performed at relatively long intervals (e.g., 1000 hours), such as refueling, inspection, and parts replacement, may have a significant impact on the manufacturing of circuit boards by the component mounting device 2. Therefore, instead of the notification in this embodiment, a stricter notification like that shown in the comparative example in Figure 5 may be adopted. In the modified example, the notification in this embodiment may also be adopted for refueling, parts replacement, etc.

[0036] (Specific case C2; ​​Figure 4) A specific case C2 implemented by the notification program 32 will be described. In this case as well, parts feeders 100 and 102 are alternately loaded onto the cassette 16. Parts feeder 100 operates for 99 hours, then for 91 hours and 80 hours thereafter, while parts feeder 102 operates for 10 hours, then for 40 hours thereafter.

[0037] The notification program 32 determines whether the usage period "f01" is equal to or greater than the predetermined period "100 hours" when the time counted by the notification counter 34 indicates the notification timing "100 hours". Currently, the usage period "f01" is 99 hours, which is less than the predetermined period "100 hours". The notification program 32 decides not to notify the notification unit 14 of the maintenance notice for the parts feeder 100. Furthermore, the notification program 32 determines whether the usage period "f02" is equal to or greater than the predetermined period "100 hours". Currently, the usage period "f02" is 1 hour, which is less than the predetermined period "100 hours". The notification program 32 decides not to notify the notification unit 14 of the maintenance notice for the parts feeder 102.

[0038] In this case, the parts feeder 102 is installed for only 10 hours, and immediately afterward, the parts feeder 100 is installed again. The usage period "f01" exceeds the upper limit period "180 hours" before the time counted by the notification counter 34 indicates the next predetermined notification timing "200 hours". Therefore, the notification program 32 causes the notification unit 14 to execute a maintenance notification for the parts feeder 100 even if the time counted by the notification counter 34 does not indicate a notification timing.

[0039] In this case, it is possible to prevent situations where maintenance notices for the parts feeder 100 are not sent for a relatively long period, such as when the usage period exceeds the maximum period of 38. In other words, it is possible to prevent situations where maintenance of the parts feeder 100 is not performed for a relatively long period.

[0040] (Correspondence) The component mounting device 2 is an example of a "maintenance notification system." The component mounting device 2, multiple component feeders, notification unit 14, notification counter 34, unit counter 36, and upper limit period 38 are examples of a "mounting device," "multiple units," "notification unit," "notification counter," "unit counter," and "predetermined upper limit," respectively. The predetermined cycle "100 hours" and predetermined period "100 hours" are examples of a "predetermined cycle" and "predetermined period," respectively. The CPU operating according to the notification program 32 is an example of a "control unit," "determination unit," "first notification control unit," and "second notification control unit."

[0041] The following points should be noted regarding the image processing apparatus described in the embodiment. The "multiple units" may be, for example, multiple other units (e.g., nozzle 12a, camera, etc.) that can be attached to and detached from the component mounting apparatus 2. Furthermore, the "multiple units" may not be units that are repeatedly attached to and removed from the component mounting apparatus 2, but rather units that are built into the component mounting apparatus 2. Such units may be, for example, a transport device that transports a substrate to the support base of the component mounting apparatus 2, or an actuator that drives the mounting mechanism 12 in the horizontal direction.

[0042] At least a portion of the "notification unit," "notification counter," "unit counter," and "control unit" may be an external device different from the component mounting device 2 (for example, a PC or system that manages the component mounting device 2). Also, the "unit counter" may be built into the unit (for example, the component feeder 100).

[0043] The "predetermined period" is not limited to "100 hours" in the embodiment. The "predetermined period" may be set appropriately by the user in accordance with the maintenance plan, or it may be predetermined by the vendor of the component mounting device 2.

[0044] The notification counter 34 may stop when the component mounting device 2 is stopped, or it may continue even when the component mounting device 2 is stopped. In modified example A, where the notification counter 34 stops when the component mounting device 2 is stopped, the user can plan maintenance according to the actual operating status of the component mounting device 2. On the other hand, in modified example B, where the notification counter 34 continues even when the component mounting device 2 is stopped, the user can plan maintenance according to the date and time. In other modified examples, the user may be allowed to choose between the count in modified example A and the count in modified example B.

[0045] The "count value" is not limited to the unit's usage period, but may also be the number of times the unit has been used. For example, if the unit is a nozzle 12a, the number of times the nozzle 12a has attracted an electronic component may be counted as the number of uses. Since the number of times the nozzle 12a attracts components per unit time varies, the number of uses can more appropriately indicate the usage status of the nozzle 12a than the usage period. In other modifications, the user may be allowed to select either the usage period or the number of uses as the count value for the unit counter 36.

[0046] Furthermore, maintenance items vary widely, including cleaning, inspection, and replacement, and the maintenance locations also vary, such as the top, bottom, and interior. For example, there may be a difference in the recommended maintenance period between the item "cleaning the top" and the item "cleaning the bottom." To address such situations, a predetermined period may be set for each of the multiple maintenance items to indicate that the maintenance indicated by that item is recommended. The notification program 32 may then cause the notification unit 14 to execute a maintenance notification for a specific maintenance item if the usage period is longer than or equal to the predetermined period set for a particular maintenance item among the multiple maintenance items, and the time counted by the notification counter 34 indicates a notification timing.

[0047] The "predetermined period" may be a different time than 100 hours (for example, 120 hours). The embodiment is an example where the "predetermined period" is the same as the "predetermined period," but the above modification is an example where the "predetermined period" is different from the "predetermined period."

[0048] Case C2 in Figure 4 does not need to be executed. In this modified example, the "second notification control unit" can be omitted.

[0049] Furthermore, the technical elements described herein or in the drawings demonstrate technical usefulness individually or in various combinations, and are not limited to the combinations described in the claims at the time of filing. In addition, the technologies illustrated herein or in the drawings achieve multiple objectives simultaneously, and achieving even one of these objectives constitutes technical usefulness in itself. [Explanation of symbols]

[0050] 2: Component mounting equipment 12: Implementation Mechanism 12a: Nozzle 14:Notification section 16: Cassette 30: Control device 32: Notification Program 34: Timing counter 36: Unit Counter 38: Upper limit period 40: Support stand 100: Parts feeder 102: Parts feeder

Claims

1. A notification unit that notifies the maintenance of at least one of several units used in a mounting device for mounting components onto a circuit board, A notification counter that counts the time for notifications, For each of the aforementioned plurality of units, a unit counter is provided that counts a count value indicating the usage status of the unit while it is being used in the mounting device, A control unit that controls the notification unit, A maintenance notification system comprising, During the time counted by the notification counter, the notification timing at which the notification unit notifies the guidance occurs repeatedly at predetermined intervals. Each of the aforementioned plurality of units is set to a predetermined value that indicates that maintenance of the unit is recommended, relative to the count value counted by the unit counter. The control unit, The system includes a first notification control unit which, when the time counted by the notification counter indicates the notification timing, causes the notification unit to execute the maintenance notification for one or more of the plurality of units, where the count value of each of the unit is equal to or greater than the predetermined value set for that unit, and when the time counted by the notification counter does not indicate the notification timing, does not cause the notification unit to execute the maintenance notification for any of the plurality of units. Maintenance notification system.

2. The maintenance notification system according to claim 1, wherein the control unit further comprises a second notification control unit that, when there is a unit whose count value counted by the unit counter exceeds a predetermined upper limit which is greater than the predetermined value, causes the notification unit to execute the notification for maintenance of the unit corresponding to the unit counter, regardless of whether the time counted by the notification counter indicates the notification timing or not.

3. For each of the multiple maintenance items, a predetermined value is set to indicate that the maintenance indicated by that maintenance item is recommended. The maintenance notification system according to claim 1 or 2, wherein the first notification control unit further causes the notification unit to execute the notification guidance for maintenance indicated by a specific maintenance item among the plurality of maintenance items, where the count value is equal to or greater than the predetermined value set for the specific maintenance item, when the time counted by the notification counter indicates the notification timing.

4. A control method for controlling a notification unit that notifies a maintenance notice for at least one of several units used in a mounting device for mounting components onto a circuit board, In the aforementioned control method, A notification counter that counts the time for notifications, For each of the aforementioned plurality of units, a unit counter is provided that counts a count value indicating the usage status of the unit while it is being used in the mounting device, It was used, During the time counted by the notification counter, the notification timing at which the notification unit notifies the guidance occurs repeatedly at predetermined intervals. Each of the aforementioned plurality of units is set to a predetermined value that indicates that maintenance of the unit is recommended, relative to the count value counted by the unit counter. The control method described above is The process includes the following steps: when the time counted by the notification counter indicates the notification timing, the notification unit is instructed to execute the maintenance notification for one or more of the plurality of units, where the count value of each of the unit is equal to or greater than the predetermined value set for that unit; and when the time counted by the notification counter does not indicate the notification timing, the notification unit is not instructed to execute the maintenance notification for any of the plurality of units. Control method.

5. A notification unit that notifies the maintenance of at least one of several units used in a mounting device for mounting components onto a circuit board, A notification counter that counts the time for measuring the notification timing, which occurs repeatedly at predetermined intervals and for which the notification unit notifies the notification; For each of the aforementioned plurality of units, a unit counter is provided that counts a count value indicating the usage status of the unit while it is being used in the mounting device, A control unit that controls the notification unit, A maintenance notification system comprising, The control unit, A first notification control unit, which, when the count value counted by the unit counter is greater than or equal to a predetermined value indicating that maintenance of the unit corresponding to the unit counter is recommended, and the time counted by the notification counter indicates the notification timing, causes the notification unit to execute the notification for maintenance of the unit corresponding to the unit counter, and when the count value counted by the unit counter is greater than or equal to the predetermined value, and the time counted by the notification counter does not indicate the notification timing, does not cause the notification unit to execute the notification for maintenance of the unit corresponding to the unit counter, A second notification control unit causes the notification unit to execute the notification notification for maintenance of the unit corresponding to the unit counter, regardless of whether the time counted by the notification counter indicates the notification timing, if there is a unit whose count value, counted by the unit counter, exceeds a predetermined upper limit that is greater than the predetermined value, A maintenance notification system equipped with the following features.

Images