Control device, control method, and computer program product

Abstract

The invention provides a control apparatus, a control method, and a computer program product. Even if there is a power-off period, more natural growth can be performed. The control device includes a control unit that executes a process of updating a virtual post-birth day number of the machine if an elapsed time from a start-up time of the machine satisfies a predetermined condition; if the power supply of the machine is turned off, keeping the virtual number of days after birth at the time point; and if the machine is restarted, restarting updating of the virtual number of days after birth by taking the held virtual number of days after birth as a starting point.

Description

[0001] Cross-references to related applications

[0002] This application claims the benefit of priority to Japanese Patent Application No. 2024-043836, filed on Mar. 19, 2024. The entire specification, claims, and drawings of Japanese Patent Application No. 2024-043836 are incorporated herein by reference. Technical Field

[0003] The present invention relates to a control device, a control method and a computer program product. Background Art

[0004] In recent years, robots designed to communicate with users have been developed. In such robots, the time elapsed since initial activation is sometimes used as a parameter to represent the robot's virtual growth (see, for example, Japanese Patent Application Laid-Open No. 2003-285286). Summary of the Invention

[0005] -Problems to be solved by the invention-

[0006] In the aforementioned robots, the main power supply may be disconnected for extended periods. In Patent Document 1, even when the robot's main power supply is disconnected for an extended period, the robot continues to grow by counting based on the built-in clock. Consequently, when the user turns the power back on, they see the robot's growth, creating a significant sense of disharmony.

[0007] Therefore, an object of the present invention is to express the virtual growth of a robot more naturally even during power outage.

[0008] -Methods for solving the problem-

[0009] The control device involved in the present invention includes a control unit, which performs the following processing: if the time elapsed from the start of the machine satisfies a given condition, the virtual number of days after birth of the machine is updated; if the power of the machine becomes disconnected, the virtual number of days after birth at that time point is maintained; and if the machine is restarted, the updating of the virtual number of days after birth is restarted with the maintained virtual number of days after birth as the starting point.

[0010] The control method involved in the present invention is a control method based on the control part of the machine, including the following steps: if the time elapsed from the startup of the machine satisfies a given condition, the virtual number of days after birth of the machine is updated; if the power supply of the machine is disconnected, the virtual number of days after birth at that time point is maintained; and if the machine is restarted, the update of the virtual number of days after birth is restarted with the maintained virtual number of days after birth as the starting point.

[0011] The computer program product involved in the present invention enables a computer of a machine having a control unit to implement the following functions: an update function, if the time elapsed from the startup of the machine satisfies a given condition, then the virtual number of days after birth of the machine is updated; a maintain function, if the power of the machine becomes disconnected, then the virtual number of days after birth at that time point is maintained; and a restart function, if the machine is restarted, the updating of the virtual number of days after birth is restarted with the maintained virtual number of days after birth as the starting point.

[0012] -Effects of the Invention-

[0013] According to the present invention, a more natural growth can be exhibited even during a power outage. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Figure 1 This is a block diagram showing the functional configuration of a robot according to the first embodiment of the present invention.

[0015] Figure 2 This is a flowchart for explaining the operation of the process of counting the number of days after birth of the robot according to the first embodiment.

[0016] Figure 3 This is a state transition diagram for explaining the operation of the process of counting the number of days after birth of the robot according to the first embodiment.

[0017] Figure 4 This is a block diagram showing the functional configuration of a robot according to a second embodiment of the present invention.

[0018] Figure 5 This is a flowchart for explaining the process of counting the number of days after birth of the robot according to the second embodiment.

[0019] Figure 6 This is a state transition diagram for explaining the operation of the process of counting the number of days after birth of the robot according to the second embodiment. DETAILED DESCRIPTION

[0020] <First embodiment>

[0021] Referring to the accompanying drawings, the control device of the machine of the present invention is applied to Figure 1 The first embodiment of the robot 200 shown in FIG. Figure 1As shown, robot 200 includes a machine control device 100, a sensor unit 210, a drive unit 220, an operating unit 230, and a power supply control unit 240. Furthermore, machine control device 100 includes a processing unit 110, a storage unit 120, and a communication unit 130. Storage unit 120 also contains emotion data 121, emotion change data 122, a growth table 123, an action content table 124, an exercise table 125, growth day data 126, and a day count value 127. The basic structure and motion control of robot 200 are substantially similar to those known in, for example, Japanese Patent No. 7192905, and therefore detailed descriptions are omitted. The following describes how to update growth day data 126, which indicates the number of days since the birth of robot 200.

[0022] The processing unit 110 controls the robot 200's movements via the drive unit 220 in accordance with motion control data corresponding to movements determined based on external stimuli detected by the sensor unit 210 and the robot 200's growth rate (growth days). For example, the number of selectable movements increases as the number of days after the robot 200's birth increases. The processing unit 110 includes an RTC (real-time clock) 111 and a timer 112. The RTC 111 keeps track of the actual date and time ("Western calendar," "month," "day," "hour," "minute," and "second"). Hereinafter, "day," "hour," and "minute" will be referred to as calendar date and time. This calendar date and time is used to calculate the day count value 127, described below. The timer 112 generates interrupts at predetermined intervals (e.g., every 10 minutes) starting from the time the robot 200 is started (including initial startup and restart). Whenever an interrupt is generated from the timer 112 at 10-minute intervals, the processing unit 110 obtains the calendar date and time (day, hour, minute) from the RTC 111, and calculates the current day count value Dnum (described later) based on the calendar date and time using a given calculation formula described later, and controls the update of the growth day data 126 based on the comparison result of the current day count value Dnum and the previous day count value 127.

[0023] Growth day data 126 is a parameter representing the virtual number of days since the robot 200 was born (a virtual number of growth days updated during the power-on period starting from the initial startup). In the first embodiment, growth day data 126 has an initial value of 0. It increments by 1 to 1 (day) at the time the power is turned on. It is then updated (+1) based on a comparison between the current day count value Dnum calculated based on the aforementioned calendar date and time and the previous day count value 127. Growth day data 126 can, for example, increment by 1 every time a real day passes. Alternatively, as in the case of small animals that grow faster than humans, the data can be incremented by 1 (+1 day) every half day or quarter day, rather than every day. Alternatively, as in the case of slow-growing animals, the data can be incremented by 1 (+1 day) every 4th or 10th day, for example. Day count value 127 is a count value used to determine the timing for updating (+1) the growth day data 126. The day count value 127 has an initial value of 0 and is calculated based on the calendar date and time of the RTC 111 every time 10 minutes elapse while the robot 200 is powered on.

[0024] The robot 200's movements are determined based on detection signals of external stimuli from the sensor unit 210, the value of the growth day data 126, and other factors. Therefore, if the robot 200's growth progresses while the power is off (if the growth day data 126 is simply updated based on the calendar date and time of the RTC 111), the user will perceive the robot 200 as having grown suddenly when the power is turned back on (restarted), causing the robot 200's movements to feel unnatural. Therefore, in this first embodiment, control is implemented so that the growth day data 126 is not updated while the power is off. Upon restart, a virtual day is counted starting from the value of the growth day data 126 at the time of power off. This prevents the robot 200's growth from progressing while the power is off.

[0025] <Operation of the First Embodiment>

[0026] When the user turns on the power of the robot 200, the processing unit 110 follows Figure 2 The process of counting days since birth is executed according to the flowchart shown. The processing unit 110 reads the previous day count value 127 from the storage unit 120 (step S10). Furthermore, the processing unit 110 obtains the calendar date and time from the RTC 111 (step S12). Based on the calendar date and time, the processing unit 110 calculates the current day count value Dnum according to the following formula 1 (step S14).

[0027] Dnum={(dd×24×60)+(hh×60)+mm} / R……(Formula 1)

[0028] Here, Dnum (decimals are rounded down) represents the current day count value, dd represents the day of the calendar date and time, hh represents the hour of the calendar date and time, mm represents the minute of the calendar date and time, and R represents the count unit (R = 1440; "minutes" represent the value of a virtual day for the robot 200). In this first embodiment, an actual day (1440 minutes) is set to R = 1440, thus representing a virtual day for the robot 200. Therefore, the day count value Dnum increases by "1" every time 1440 minutes (i.e., a day) passes.

[0029] In other words, the frequency of increments in the day count can be changed by changing the value of R. For example, setting R = 2880 can increase the count by 1 every 2 days, or setting R = 5760 can increase the count by 1 every 4 days. Conversely, setting R = 720 can increase the count by 1 every half day, or setting R = 360 can increase the count by 1 every quarter day. Furthermore, when changing R, the value of "24" in the formula (dd × 24 × 60) must also be changed based on the value of R. For example, if R = 2880 (2 days), change "24" to "48." If R = 720 (1 / 2 day), change "24" to "12." In other words, simply set the value of "24" to R / 60.

[0030] Next, processing unit 110 determines whether the previous day count value 127 and the current day count value Dnum do not match (step S16). If the previous day count value 127 and the current day count value Dnum do not match (step S16: "Yes"), the growth day data 126 indicating the number of days since birth is updated (+1) (step S18), and the previous day count value 127 is updated with the current day count value Dnum (step S20). The inconsistency between the previous day count value 127 and the current day count value Dnum indicates that one day has passed since the virtual birth of robot 200; in other words, it is time to update the number of days since the birth of robot 200 (+1). Processing unit 110 then terminates this process.

[0031] For example, Figure 3As shown, the user turns on the power at 10:00 AM on January 1st. In this case, day count value 127 is not set to "0." Because the day count value Dnum ({(1×24×60)+(10×60)+0} / 1440=1.416...→"1") calculated based on the calendar date and time (dd=1, hh=10, mm=0) obtained from RTC 111 according to Formula 1 above is "1" and does not match the previous day count value 127 ("0"), processing unit 110 updates growth day data 126 by (+1), thus updating day count value 127 to "1."

[0032] On the other hand, if the previous day count value 127 and the current day count value Dnum are consistent (step S32 "No"), the processing unit 110 ends the processing. The fact that the previous day count value 127 and the current day count value Dnum are consistent means that the date has not changed from the previous time, that is, it means that it is the same day as the previous time. For example, Figure 3 As shown, when the restart is performed at 10:00 on January 8, since "4" is already set to the day count value 127, the day count value 127 is not updated and the processing ends.

[0033] The above Figure 2 The illustrated post-birth days counting process is repeatedly executed at 10-minute intervals, interrupted by timer 112. Furthermore, the following process is repeated: Each time the process is executed, the previous day count value 127 is compared with the current day count value Dnum. If the two values ​​do not match, the growth day data 126 is updated (+1), and the previous day count value 127 is updated with the current day count value Dnum. Thus, each time the virtual number of days after birth passes one day, the growth day data 126 is updated (+1). Furthermore, if the user powers off (operates) the robot 200 during the execution of the above post-birth days counting process, the power is turned off, while the growth day data 126 and day count value 127 at that time are stored in the storage unit 120.

[0034] For example, Figure 3As shown, at 10:10 on January 1, the previous day count value 127, "1," matches the current day count value Dnum, "1 (rounded down)" calculated from the calendar date and time (dd=1, hh=10, mm=10). Therefore, neither the growth day data 126 nor the day count value 127 is updated. Similarly, at 10:20 on January 1, 10 minutes later, the previous day count value 127, "1," matches the current day count value Dnum, "1 (rounded down)" calculated from the calendar date and time (dd=1, hh=10, mm=20). Therefore, neither the growth day data 126 nor the day count value 127 is updated. Furthermore, at 23:50 on January 1, similarly, because the previous day count value 127 ("1") matches the current day count value Dnum ("1 (rounded down)") calculated based on the calendar date and time (dd = 1, hh = 23, mm = 50), neither the growth day data 126 nor the day count value 127 are updated. In other words, the growth day data 126, which represents the virtual number of days since the birth of robot 200, which was activated on January 1, remains at 1 (day) on January 1.

[0035] Then, at 00:00 on January 2nd, the previous day count value 127 ("1" at 23:50) and the current day count value Dnum ("2" calculated based on the calendar date and time (dd = 2, hh = 0, mm = 0) no longer match. Therefore, the growth day data 126 representing the virtual number of days since birth is updated (+1) to "2," and the day count value 127 is updated to the day count value Dnum ("2"). That is, the growth day data 126 representing the virtual number of days since birth of robot 200, which was activated on January 1st, is updated to 2 (day) at 00:00 on January 2nd. Furthermore, at 11:50 PM on January 2nd, because the previous day count value 127 ("2") matches the current day count value Dnum ("2") calculated based on the calendar date and time (dd = 2, hh = 23, mm = 50), neither the growth day data 126 nor the day count value 127 are updated, and the above-described post-birth day counting process is repeated until 11:50 PM on January 2nd. In other words, the growth day data 126 indicating the virtual number of days since the birth of robot 200, which was activated on January 1st, remains at 2 (days) at 11:50 PM on January 2nd.

[0036] Then, 10 minutes later, from 23:50 on January 2nd to 00:00 on January 3rd, the previous day count value 127 ("2") and the current day count value Dnum ("3") calculated based on the calendar date and time (dd=3, hh=0, mm=0) become inconsistent. Therefore, the growth day data 126 indicating the number of days since birth is updated (+1) to "3," and the previous day count value 127 is updated to the current day count value Dnum ("3"). In other words, the growth day data 126 indicating the virtual number of days since birth of robot 200 activated on January 1st is updated to 3 (day) at 00:00 on January 3rd. Furthermore, if the user powers off (operates) robot 200 on January 4th, the "4" in day count value 127 and the "4" in growth day data 126 remain unchanged.

[0037] Then, if robot 200 is restarted at 10:00 AM on January 8th, four days after the power was turned off, the previous day count value 127 ("4") and the current day count value Dnum ("8") calculated based on the calendar date and time (dd=8, hh=10, mm=0) will no longer match. Therefore, the growth day data 126 indicating the number of days since birth is updated (+1) to "5," and the day count value 127 is updated to the day count value Dnum ("8"). In other words, the growth day data 126 indicating the virtual number of days since birth for robot 200, which was started on January 1st and powered on from January 1st to January 4th, is updated to 5 (days) at the time of restart. In this manner, when the robot 20 restarts, the previous day count value at the time of power outage is compared with the current count value Dnum at the time of restarting. If the two do not match, it is determined that a date has been crossed, and the growth day data 126 representing the virtual number of days since birth is updated (+1) regardless of the date. On the other hand, if the previous day count value and the current count value Dnum match, it is determined that a date has not been crossed, and the growth day data 126 representing the virtual number of days since birth is not updated but retained.

[0038] If 10 minutes have passed since the restart, and it is 10:10 on the same day, then because the previous day count value 127, "8," matches the current day count value Dnum, "8" calculated based on the calendar date and time (dd=8, hh=10, mm=10), the growth day data 126 indicating the number of days since birth and the day count value 127 are not updated, and the same operation continues. Thus, by controlling not to update growth day data 126 while the power is off, it is possible to prevent the robot 200 from making any false progress in growth during the power-off period.

[0039] According to the first embodiment described above, if the updating of the growth day data 126 indicating the virtual number of days after the birth of the robot 200 is stopped during the power-off period, when the system is restarted, the value of the day count value 127 at the time of the power-off period and the value of the growth day data 126 indicating the virtual number of days after the birth are used as starting points, and based on the comparison between the day count value Dnum calculated based on the calendar date and time of the RTC 111 and the previous day count value 127, the growth day data 126 indicating the virtual number of days after the birth from the time of the initial startup is updated. Therefore, for example, even in a case where the power must be disconnected after playing with the robot 200 for 5 hours, or the power is disconnected for charging, the growth of the robot 200 felt by the user is consistent with the growth of the robot 200 automatically updated, and a more natural growth that does not cause a sense of disharmony to the user can be expressed.

[0040] For example, even if the battery voltage of robot 200 decreases and the power supply of robot 200 is cut off, or even if the battery voltage becomes below a certain level and RTC111 is reset so that the calendar date and time returns to the initial value, or even if the calendar date and time of RTC111 is corrected to the actual time by connecting robot 200 to the user's smartphone, the growth of robot 200 felt by the user and the growth of robot 200 automatically updated are consistent, and a more natural growth that does not cause a sense of disharmony to the user can be expressed.

[0041] <Second embodiment>

[0042] Referring to the accompanying drawings, the control device of the machine of the present invention is applied to Figure 5 The second embodiment of the robot 200 shown in FIG. Figure 1 The corresponding parts are marked with the same reference numerals and their descriptions are omitted. Figure 4In the illustrated robot 200, the storage unit 120 includes a growth counter 128 in place of the day counter 127. The processing unit 110 controls the robot 200 so that the elapsed time from the timer 112 is obtained and the growth counter 128 is incremented by 1 every 10 minutes. When the growth counter 128 reaches a predetermined value (for example, 144 (10 minutes x 144 = 1440 minutes = 24 hours, hereinafter referred to as 144), assuming that the actual day is used as the virtual day after birth), the growth day data 126 indicating the number of days since the birth of the robot 200 is updated (by +1). In this way, the growth counter 128 indicates the virtual number of days since the birth of the robot 200 from the time of its activation. By changing the value of 144, the update frequency (growth rate) of the growth day data 126 indicating the virtual number of days since the birth of the robot 200 can be controlled. For example, if 144 is half 72, the growth day data 126 is updated (+1 (day)) every 12 hours (10 minutes × 72 = 720 minutes = 12 hours). In the actual half day, the virtual number of days after birth passes by 1 day.

[0043] <Operation of the Second Embodiment>

[0044] When the user turns on the power of the robot 200, the processing unit 110 follows Figure 5 The growth day counting process is executed according to the flowchart shown. When the power is first turned on, i.e., at initial startup, timer 112 is set to "0 (initial value)", growth count value 128 is set to "0 (initial value)", and growth day data 126, indicating the virtual number of days since birth, is set to "1 (initial value)". Furthermore, when the power is turned on, timer 112 begins counting the elapsed time from the time of startup (including initial startup and restart).

[0045] When the user turns on the power of robot 200, processing unit 110 first determines whether the power has been turned off (operated) (step S40). If the power has not been turned off (operated) (step S40: No), processing unit 110 obtains the elapsed time from the start-up timer 112 (step S42). Next, processing unit 110 determines whether 10 minutes have passed since the start-up time (step S44). If not (step S44: No), processing unit 110 returns to step S40 and repeats the above process until 10 minutes have passed. If 10 minutes have passed since the start-up time (step S44: Yes), processing unit 110 increments growth counter 128 by 1 (step S46) and determines whether growth counter 128 has reached 144 (1 day) (step S48). Furthermore, when the growth count value 128 has not reached 144, that is, when the virtual number of days since startup has not reached 1 day (step S48 "No"), the processing unit 110 returns to step S42 and repeats the above steps S40 to S46, incrementing the growth count value 128 by 1 every time 10 minutes have passed.

[0046] If the growth counter 128 subsequently reaches 144, meaning that the virtual number of days since the start-up has reached one (step S48: "Yes"), the processing unit 110 updates the growth day data 126 indicating the number of days since birth by adding one (step S50) and resets the growth counter 128 to "0" (step S52). The processing unit 110 then returns to step S42 and repeats steps S40-S52, updating the growth day data 126 indicating the virtual number of days since birth by adding one each time the growth counter 128 reaches 144 (one day has passed).

[0047] On the other hand, in the above-mentioned update process of the growth day data 126 , when the user turns off the power (operates) (step S40 : Yes), the processing unit 110 resets the timer 112 to 0 (step S54 ) and ends the process.

[0048] Afterwards, when the robot 200 is restarted by the user, the processing unit 110 follows Figure 5 The above-described post-birth day counting process is executed again according to the flowchart shown. Upon restart, the growth day data 126 and growth count value 128 retain the values ​​at the time of power failure. Therefore, in the post-birth day counting process after restart, the growth day data 126 and growth count value 128 retained at the time of power failure are used as the starting point, and the growth day data 126 is updated (+1). Each time the growth day data 126 reaches 144 (one day has passed), the growth day data 126 indicating the number of days since birth is updated (+1).

[0049] For example, Figure 6 As shown, if the system is first activated at 3:00 PM on March 10, timer 112 begins counting the elapsed time since activation. At the initial activation, growth counter 128 is initialized to "0," and growth day data 126 is initialized to "1." Next, at 3:10 PM, 10 minutes after activation, growth counter 128 increments by 1, reaching "1." However, since it has not yet reached "144," growth day data 126 remains at "1" and is not updated. Furthermore, at 3:20 PM, 10 minutes after activation, growth counter 128 increments by 1, reaching "2." However, since it has not yet reached "144," growth day data 126 remains at "1" and is not updated. Similarly, growth counter 128 increments by 1 every 10 minutes until it reaches "144," at which point growth day data 126 remains at "1." That is, the growth day data 126 indicating the virtual number of days after birth of the robot 200 activated on March 10 is maintained at 1 (day) on March 10.

[0050] Afterwards, at 3 / 11, 3:00 PM, while the power remains on, the growth counter value 128 reaches "144" because 1440 minutes have passed since the start-up. When the growth counter value 128 reaches "144", the growth day data 126 is updated (+1), becoming 1+1→"2". That is, the growth day data 126 indicating the virtual number of days after birth of the robot 200 that was started on 3 / 10 is updated to 2 (day) at 3 / 11, 3:00 PM, one day later. Furthermore, at this point in time, the growth counter value 128 is reset to "1". Furthermore, if the user turns off the power (operates) the robot 200 on 3 / 11, 3:11 PM, the timer 112 is reset (0), and the "1" of the growth counter value 128 and the "2 (day)" of the growth day data 126 indicating the number of days after birth remain unchanged.

[0051] Then, at 2:00 PM on March 15th, four days after the power outage, the user turns robot 200 back on, effectively restarting it. At this point, growth counter 128 remains at "1," and growth day data 126 remains at 2 (days). Therefore, at 2:10 PM on the same day, 10 minutes after the restart, growth counter 128 increments by 1, reaching "2." However, since it has not yet reached "144," growth day data 126 remains at "2" and is not updated. Growth day data 126 remains at "2" until growth counter 128 reaches 144, that is, at 1:50 PM on March 16th, until 1430 minutes have passed since the restart (1440 minutes if the 10 minutes before the power outage are included). That is, there was no growth during the four days of power outage. The virtual number of days since birth is 1 (day) from 3:00 PM on March 10th to 2:50 PM on March 11th, the initial startup, and 1 (day) from 3:00 PM on March 11th to 1:40 PM on March 15th, the restart, for a total of 2 (days). Furthermore, since it is actually 1:50 PM on March 16th, the third day since the initial startup, the growth days data 126 is updated to 3 (days).

[0052] According to the second embodiment described above, every time 10 minutes have passed since the start of the robot 200, the growth count value 128 is incremented by 1, and every time the growth count value 128 reaches a given value (for example, 1 day = 144), the growth day data 126 indicating the virtual number of days after the birth of the robot 200 is updated (+1). During the period when the power is off, the updating of the growth day data 126 indicating the virtual number of days after the birth of the robot 200 is stopped. If the robot is restarted, the value of the growth count value 128 at the time of power off and the value of the growth day data 126 indicating the virtual number of days after the birth of the robot 200 are used as starting points, and the growth day data 126 indicating the virtual number of days after the birth of the robot 200 from the initial start-up is updated (+1) based on the value of the growth count value 128. Therefore, the growth of the robot 200 perceived by the user is consistent with the automatically updated growth of the robot 200, and a more natural growth that does not cause a sense of disharmony to the user can be expressed.

[0053] Furthermore, the detailed structures and detailed operations of the various components of the robot 200 in the above-described embodiment can, of course, be appropriately modified without departing from the spirit of the present invention. While the embodiments of the present invention have been described, the scope of the present invention is not limited to the above-described embodiments but encompasses the scope of the invention set forth in the claims and their equivalents.

Claims

1. A control device, characterized in that: A control unit is provided, and the control unit performs the following processing: If the time elapsed since the machine's startup satisfies a given condition, the virtual number of days since the machine's birth is updated; If the power supply of the machine is disconnected, the virtual number of days after birth at that point in time is maintained; and If the machine is restarted, the update of the virtual number of days after birth is restarted with the maintained virtual number of days after birth as the starting point.

2. The control device according to claim 1, wherein: The control unit performs the following processing: While the machine is powered on, a count value corresponding to the elapsed time from the start-up is calculated based on the actual date and time information. If it is determined that the timing for updating the virtual number of days after birth has been reached based on the change in the count value, the given condition is determined to be satisfied, thereby updating the virtual number of days after birth.

3. The control device according to claim 2, wherein: The control unit performs the following processing: The count value calculated a predetermined time ago is compared with the count value calculated at the current time point. If the count value and the count value do not match, it is determined that the timing for performing the update has arrived.

4. The control device according to claim 3, wherein: The control unit performs the following processing: If the machine is restarted, the count value at the time when the power is disconnected and the count value when it is moved again are compared. If the two are inconsistent, it is determined that the date has been crossed, and the virtual number of days after birth is updated regardless of the number of days. If the two are consistent, it is determined that the date has not been crossed, and the virtual number of days after birth is maintained.

5. The control device according to claim 1, wherein: The control unit performs the following processing: If it is determined that the count value obtained by counting the elapsed time from the activation at given time intervals reaches a given value, it is determined that the given condition is satisfied, and the virtual number of days after birth is updated.

6. A control method based on a control unit of a machine, characterized in that: The following steps are included: If the time elapsed since the startup of the machine satisfies a given condition, the virtual number of days after the birth of the machine is updated; If the power supply of the machine is disconnected, the virtual number of days after birth at that point in time is maintained; and If the machine is restarted, the update of the virtual number of days after birth is restarted with the maintained virtual number of days after birth as the starting point.

7. A computer program product, characterized in that Enable the computer of the machine with the control unit to realize the following functions: An update function, which updates the virtual number of days after the birth of the machine if the time elapsed since the machine was started satisfies a given condition; A hold function, if the power supply of the machine is disconnected, then the virtual number of days after birth at that point in time is held; and The restart function restarts the updating of the virtual number of days after birth by taking the maintained virtual number of days after birth as the starting point if the machine is restarted.

Images