Data processing device and data processing program

Abstract

Provided is a data processing device and a data processing program that can reduce the amount of missing data to be acquired and prevent the occurrence of problems due to a target number of data not being reached. [Solution] A data processing device 10A of this embodiment starts execution of a data acquisition process for acquiring data from an external source at a normal start timing that is repeated in a first cycle, and is capable of completing execution of the data acquisition process in less than half the first cycle. As a result, usually more than half of each cycle (more than half the cycle) is a blank period during which the data acquisition process is not executed. Then, the data processing device 10A of this embodiment detects a non-execution abnormality in which the data acquisition process is not started at the normal start timing, and executes the data acquisition process that has not been started due to the non-execution abnormality during the blank period following the non-execution abnormality.

Description

[Technical field]

[0001] The present disclosure relates to a data processing device and a data processing program. [Background technology]

[0002] 2. Description of the Related Art Known conventional data processing devices are those that periodically acquire data from the outside (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 11-202932 (Paragraph

[0030] ) Summary of the Invention [Problem to be solved by the invention]

[0004] However, in the conventional data processing device, even if data is acquired over a prescribed number of periods (e.g., 60 seconds) at a predetermined period (e.g., 1 second), a "data target number not reached defect" may occur in which only a smaller number of data items than the target number (e.g., 60 items) for the prescribed number of periods can be acquired. The causes of this include a temporary communication failure between the data processing device and the data acquisition source, a temporary delay in measurement processing by the data acquisition source, for example, a measurement device, and the like.

[0005] The present application has been made in consideration of the above circumstances, and provides a data processing device and a data processing program that can reduce the amount of missing data to be acquired and prevent the occurrence of problems such as a target number of data not being reached. [Means for solving the problem]

[0006] A first aspect of the present disclosure made to solve the above problems is a data processing device comprising: a data acquisition unit that executes a data acquisition process for acquiring data from an external source every first period; an abnormality detection unit that detects either or both of non-execution abnormalities in which the data acquisition process is not executed or is forcibly terminated during execution; and a data acquisition completion unit that, when the non-execution abnormality is detected, starts execution of the data acquisition process that has not been started or has not been terminated due to the non-execution abnormality during a period after the end of the data acquisition process in a subsequent period.

[0007] A second aspect of the present disclosure is a data processing program that causes a computer to function as a data acquisition unit that executes a data acquisition process to acquire data from an external source every first period; an abnormality detection unit that detects non-execution abnormalities, such as either the data acquisition process not being executed or being forcibly terminated during execution, or both; and a data acquisition completion unit that, when the non-execution abnormality is detected, starts execution of the data acquisition process that has not been started or has not been terminated due to the non-execution abnormality during a period after the end of the data acquisition process in a subsequent period. Effect of the Invention

[0008] The data processing device and the computer executing the data processing program of the present disclosure execute a data acquisition process for acquiring data from an external source for each first period. The data processing device and the computer executing the data processing program of the present disclosure detect one or both of the non-execution abnormalities of the data acquisition process not being started or being forcibly terminated during execution, and execute the data acquisition process that has not been started or not finished due to the non-execution abnormality during the period after the non-execution abnormality, after the end of the data acquisition process, in the period after the non-execution abnormality. In this way, the data processing device and the data processing program of the present disclosure execute the data acquisition process that has not been started or not finished so as to complement it later, so that the number of data losses when data acquisition is performed over a predetermined number of periods is reduced, and the occurrence of a malfunction in which the target number of data is not reached is reduced. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a block diagram showing an electrical configuration of a data processing device according to a first embodiment of the present disclosure. [Diagram 2] FIG. 2A is a time chart showing the execution timing of the acquisition command process, FIG. 2B is a time chart showing the execution timing of the complement command process, FIG. 2C is a time chart showing the execution timing of each process, and FIG. 2D is a time chart showing the execution timing of each process. [Diagram 3] FIG. 3 is a flowchart of a program executed by the acquisition command process. [Figure 4] FIG. 4 is a flowchart of the program executed by the command execution process. [Diagram 5] FIG. 5 is a flowchart of a program executed by the abnormality detection process. [Figure 6] FIG. 6 is a flowchart of a program executed by the complement command processing. [Figure 7] Figure 7 is a flowchart of the program executed by the statistical processing. [Figure 8] FIG. 8 is a flowchart of a program executed by the abnormality detection process according to the second embodiment. [Figure 9] FIG. 9 is a flowchart of a program executed by the complement command processing. [Figure 10] FIG. 10 is a flowchart of a program executed by a command execution process according to the third embodiment. [Figure 11] FIG. 11 is a time chart showing the execution timing of a supplementary command process according to the fourth embodiment. [Figure 12] FIG. 12 is a flowchart of a program executed by a supplementary command process according to the fifth embodiment. [Figure 13] FIG. 13 is a flowchart of a program executed by an acquisition command process according to the sixth embodiment. [Figure 14] FIG. 14 is a flowchart of a program executed by the command execution process. [Figure 15] FIG. 15 is a flowchart of a program executed by the abnormality detection process. [Figure 16]FIG. 16 is a flowchart of a program executed by the complement command process. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] [First embodiment] A data processing device 10A and a data processing program according to a first embodiment of the present disclosure will be described with reference to Fig. 1 to Fig. 7. As shown in Fig. 1, the data processing device 10A is connected to, for example, a power meter 81 in a factory via a communication network 100 including the Internet. The power meter 81 measures, for example, the power consumption of equipment 80 in the factory. The power meter 81 also has a communication circuit, and in response to a request from the outside via the communication network 100, transmits the power consumption of the equipment 80 measured at the time of the request as measurement data to the request source.

[0011] Although the data processing device 10A is connected to the power meter 81 via the communication network 100, it may be connected to the power meter 81 without via the communication network. Furthermore, the data processing device 10A is a terminal connected to the communication network 100, but it may be a cloud server in the communication network 100.

[0012] The data processing device 10A includes, for example, an MCU 11, an auxiliary storage device 12, a communication circuit 13, an RTC 14, and an interrupt circuit 15.

[0013] The RTC 14 provides time information to an interrupt circuit 15 and a CPU (not shown) included in the MCU 11. The interrupt circuit 15 is also connected to an interrupt terminal of the CPU, and provides an interrupt signal of a predetermined period, which is generated based on the time information from the RTC 14, to the CPU.

[0014] The auxiliary storage device 12 stores data processing programs including an acquisition command process PG1, a command execution process PG2, an abnormality detection process PG3, a supplementary command process PG4, and a statistical process PG5 (see Figs. 3 to 7), which will be described later. The MCU 11 (more specifically, the CPU of the MCU 11) repeatedly executes each of the processes PG1 to PG5 at each set period, whereby the MCU 11 functions as a data acquisition unit 21, a data acquisition and supplement unit 22, an abnormality detection unit 23, an abnormality counter 24, a data storage unit 25, a statistical processing unit 26, and the like, which are shown in the block diagram of Fig. 1.

[0015] The data acquisition unit 21 and the data acquisition complement unit 22 share the data acquisition processing unit 20. In addition to these, the data acquisition unit 21 has a data acquisition command unit 21A, while the data acquisition complement unit 22 has a data acquisition complement command unit 22A.

[0016] The data acquisition processing unit 20 is connected to the data acquisition command unit 21A and the data acquisition supplement command unit 22A. When the data acquisition processing unit 20 receives a start command from the data acquisition command unit 21A or the data acquisition supplement command unit 22A, the data acquisition processing unit 20 starts executing a data acquisition process to acquire measurement data from the power meter 81.

[0017] Specifically, the start command received by the data acquisition processing unit 20 includes, for example, time data that specifies the date and time. When the data acquisition processing unit 20 receives a start command from the data acquisition command unit 21A or the data acquisition supplement command unit 22A, it starts the execution of the data acquisition process and outputs a data request signal that requests the power meter 81 to transmit measurement data to the communication circuit 13. Then, the communication circuit 13 transmits the data request signal to the power meter 81 in accordance with the communication protocol of a general communication network. In response to this, when the power meter 81 transmits the measurement data, the data acquisition processing unit 20 buffers the measurement data in a buffer (not shown) provided in the data acquisition processing unit 20 itself and acquires the measurement data. Then, when the data acquisition processing unit 20 receives an EOF (END OF FILE) code that indicates the end of the transmission data from the power meter 81, it associates the buffered measurement data with the time data included in the start command and stores the result in the data storage unit 25. Then, the data acquisition processing unit 20 deletes all data in the buffer and ends the data acquisition process.

[0018] Here, under normal circumstances when no malfunction such as a communication failure occurs, the data acquisition process is completed within an execution time (hereinafter, referred to as the "normal execution time") that is, for example, equal to or shorter than half the first cycle described below. However, when a malfunction such as a communication failure occurs, the data acquisition processing unit 20 does not terminate the process until it acquires the EOF code, and allows the execution time of the data acquisition process to become longer than one cycle of the first cycle, which is a prolonged abnormality.

[0019] The data acquisition command unit 21A issues a start command to the data acquisition processing unit 20 in a first cycle based on the time information from the RTC 14. Specifically, the time information from the RTC 14 is updated in increments of 1 / 100 [seconds], for example. Then, as shown in the conceptual diagram of FIG. 2A, the data acquisition command unit 21A outputs a start command to the data acquisition processing unit 20 at the timing when the value of the one-second range of the time information from the RTC 14 changes (hereinafter referred to as "normal start timing"). As a result, when the data acquisition processing unit 20 starts execution of the data acquisition process for all start commands output by the data acquisition command unit 21A and ends execution of the data acquisition process within the normal execution time, each of the time data linked to the multiple measurement data stored in the data storage unit 25 becomes continuous with a shift of one second.

[0020] In this embodiment, if a prolonged abnormality occurs and the data acquisition processing unit 20 is executing data acquisition processing at the normal start timing when the data acquisition command unit 21A outputs a start command, the data acquisition command unit 21A does not output a start command. As a result, measurement data linked to the time data of the start command that was not output is not acquired, and thus multiple time data stored in the data storage unit 25 have missing parts with intervals of 2 seconds or more.

[0021] The abnormality detection unit 23 detects an abnormality where the execution of the data acquisition process does not start at the normal start timing due to the above-mentioned prolonged abnormality (hereinafter, this is referred to as a "non-execution abnormality"). Then, the abnormality detection unit 23 increments the abnormality counter 24 every time it detects a non-execution abnormality.

[0022] The abnormality detection process by the abnormality detection unit 23 is performed during the time from the normal start timing when the data acquisition command unit 21A outputs a start command to the time when the data acquisition processing unit 20 starts executing the data acquisition process in response to the normal start timing. Specifically, the execution time of the abnormality detection process is shorter than the time obtained by subtracting the variation in the data acquisition process from a half cycle of the first cycle (specifically, for example, 4 / 5 or less of the half cycle of the first cycle).

[0023] The data acquisition complementary command unit 22A acquires time information from the RTC 14, acquires the value of the abnormality counter 24 at a timing delayed by half a first cycle from the timing when the data acquisition command unit 21A outputs a start command (i.e., at a timing delayed by 0.5 seconds from the switching of the 1-second value of the time information from the RTC 14), and if the value of the abnormality counter 24 is not "0", acquires information on whether or not data acquisition processing is being executed from the data acquisition processing unit 20. Then, if the value of the abnormality counter 24 is not "0" and the data acquisition processing is not being executed, the data acquisition complementary command unit 22A outputs a start command to the data acquisition processing unit 20 and then decrements the abnormality counter 24.

[0024] As a result, as shown in the conceptual diagram of Figure 2B, when a non-execution abnormality occurs, one or more data acquisition processes for which a non-execution abnormality occurred are executed so as to be supplemented during a blank period, which is the latter half of the first cycle that is not normally used for data acquisition processes, in each cycle of the first cycle (hereinafter, this is referred to as "supplementary execution").

[0025] Also, the time until the data acquisition supplement command unit 22A starts the data acquisition process is shorter than the time obtained by subtracting the normal execution time of the data acquisition process from the half cycle of the first cycle. More specifically, it is shorter than the time obtained by subtracting the variation of the data acquisition process from the half cycle of the first cycle (specifically, for example, it is 4 / 5 or less of the half cycle of the first cycle).

[0026] The statistical processing unit 26 acquires time information from the RTC 14, and starts, for example, 0.5 seconds before the value of the one-minute portion of the time information changes (i.e., before a half cycle of the first cycle), and stops before the value of the one-minute portion of the time information changes. Then, when the statistical processing unit 26 starts, it issues a special command to the data acquisition processing unit 20 and the abnormality detection unit 23. When the data acquisition processing unit 20 receives the special command, if the data acquisition processing unit 20 is executing a data acquisition process, it forcibly terminates the execution and deletes all data in the buffer described above without outputting the measurement data to the data storage unit 25. Also, if the data acquisition processing unit 20 receives the special command when the data acquisition processing unit 20 is not executing a data acquisition process, it does not react to the special command. When the abnormality detection unit 23 receives the special command, it does not detect the non-execution abnormality described above, and resets the abnormality counter 24 to 0.

[0027] After the special command is given, the statistical processing unit 26 acquires all the measurement data stored in the data storage unit 25 and deletes all the data in the data storage unit 25. Then, it counts the number of all acquired measurement data and calculates statistical data (e.g., average value) related to all the acquired measurement data. Then, it generates log data that links the statistical data with the time information of the start of the statistical processing unit 26 and the number of measurement data, and stores the log data in the auxiliary storage device 12, while also transmitting the log data to a predetermined terminal 82 connected to the communication network 100 via the communication circuit 13.

[0028] The acquisition command process PG1, command execution process PG2, abnormality detection process PG3, supplementary command process PG4, and statistical process PG5 included in the above-mentioned data processing program are shown in Figures 3 to 7. In these processes PG1 to PG5, "FLG1, FLG2, FLG3" are flags, and "i" is an abnormality counter, all of which are set to "0" by default. Also, Figure 2C shows the execution timing of processes PG1 to PG5.

[0029] The acquisition command process PG1 is repeatedly executed for each first period at the timing when the value of the one-second portion of the time information from the RTC 14 is switched (see FIG. 2C), and as shown in FIG. 3, first, it is determined whether or not FLG1 is "1" (S10). FLG1 being "1" means that acquisition of measurement data is being executed (step S24 of command execution process PG2 described later). If FLG1 is not "1" (YES in S10), a start command for executing acquisition of measurement data is output (S11), FLG2 is set to "1", and the process exits from the acquisition command process PG1 (S12). On the other hand, if FLG1 is "1" (NO in S10), a start command is not output, FLG3 is set to "1", and the process exits from the acquisition command process PG1 (S13). Here, the MCU 11 when executing steps S10 to S13 corresponds to the data acquisition command unit 21A described above, and setting FLG2 to "1" means that a start command has been output, while setting FLG3 to "1" means that the start command was not output at the normal start timing (a non-execution abnormality was detected).

[0030] The command execution process PG2 is repeatedly executed, for example, every 1 / 10 [seconds] based on time information from the RTC 14 (see FIG. 2C). As shown in FIG. 4, when FLG2 is 1, that is, when a start command is output (NO in S20 and YES in S21), FLG1 is set to "1" (S22) and FLG2 is reset to "0" (S23), and acquisition of measurement data from the power meter 81 is started and the acquired measurement data is stored in a buffer (S24). Then, the process of storing the measurement data in the buffer (S24) is repeatedly executed until an EOF code indicating the end of the transmission data is acquired from the power meter 81 (YES in S20, NO in S24 and S25). Then, when the EOF code is acquired (YES in S25), the measurement data stored in the buffer is linked to the time data included in the start command and moved to the data storage unit 25 (S26), FLG1 is reset to "0", and the command execution process PG2 is exited (S27). On the other hand, when FLG2 is 0, that is, when the start command is not output (NO in S20 and NO in S21), the process of acquiring the measurement data is not executed. Here, the MCU 11 during the execution of steps S20 to S27 corresponds to the data acquisition processing unit 20 described above.

[0031] The abnormality detection process PG3 is repeatedly executed every first period, for example, at the timing after the execution of the acquisition command process PG1 (see FIG. 2C), and as shown in FIG. 5, it determines whether FLG3 is 1 or not, that is, whether the start command is output at the normal start timing or not (S30), and if the start command is output at the normal start timing, it exits from the abnormality detection process PG3 (NO in S30), and if the start command is not output at the normal start timing (YES in S30), it increments the value of the counter i by one and exits from the abnormality detection process PG3 (S31). Here, the MCU 11 executing steps S30 and S31 corresponds to the abnormality detection unit 23 described above, and the counter i corresponds to the abnormality counter 24 that counts the number of non-execution abnormalities in which the start command is not output at the normal start timing.

[0032] The complementary command processing PG4 is repeatedly executed for each first period at a timing delayed by 0.5 seconds from the timing when the value of the 1-second portion of the time information from the RTC 14 is switched (see FIG. 2C), and as shown in FIG. 6, first, it is determined whether the counter i is not 0, that is, whether there is a non-execution abnormality (S40), and if there is no non-execution abnormality (YES in S40), the complementary command processing PG4 is terminated, but if there is a non-execution abnormality (NO in S40), it is further determined whether FLG1 is 1, that is, whether measurement data is being acquired (S41), and if measurement data is not being acquired (NO in S41), a start command for complementary execution of the measurement data acquisition processing is output (S42), FLG2 is set to "1" (S43), the value of the counter i is decremented by one, and the complementary command processing PG4 is terminated (S43). Then, in response to FLG2 being set to "1", the above-mentioned command execution processing PG2 performs the measurement data acquisition processing. On the other hand, even if there is a non-execution abnormality (NO in S40), if measurement data is being acquired (YES in S41), a start command for complementary execution of the measurement data acquisition process is not output. In this case, when the subsequent complementary command process PG4 is executed, if measurement data is not being acquired (NO in S41), a start command is output (S42), and the measurement data acquisition process is performed by command execution process PG2. Here, the MCU 11 when executing steps S40 to S44 corresponds to the above-mentioned data acquisition complementary command unit 22A.

[0033] The statistical processing PG5 is repeatedly executed at a timing of 0.5 seconds before the value of the one-minute value of the time information from the RTC 14 is switched (see FIG. 2C). As shown in FIG. 7, first, in step S50, the execution of the command execution processing PG2 and the complementary command processing PG4 is forcibly terminated, the value of the counter i is set to 0, and all measurement data stored in the buffer is deleted (S51). Then, all measurement data stored in the data storage unit 25 is acquired and statistical data is calculated (S52). Then, log data is generated by linking the statistical data with the time information of the start of the statistical processing PG5 and the number of measurement data, and the log data is stored in the auxiliary storage device 12. At the same time, the log data is transmitted to a predetermined terminal 82 and the statistical processing PG5 is exited (S53). Here, the MCU 11 when executing steps S50 to S53 corresponds to the statistical processing unit 26 described above.

[0034] The configuration of this embodiment has been described above. Next, the effects of this embodiment will be described. The data processing device 10A of this embodiment starts the execution of a data acquisition process for acquiring data from the outside at a normal start timing that is repeated in a first cycle, and is capable of completing the execution of the data acquisition process in less than a half cycle of the first cycle. As a result, usually, more than half of each cycle (more than a half cycle) is a blank period in which the data acquisition process is not executed. Then, the data processing device 10A of this embodiment detects a non-execution abnormality in which the data acquisition process is not started at the normal start timing, and executes the data acquisition process that has not been started due to the non-execution abnormality during the blank period after the non-execution abnormality. In this way, in the data processing device 10A of this embodiment, the data acquisition process that has not been started is executed later to complement it, so that the number of missing data is reduced when data is acquired over a predetermined number of cycles, and the occurrence of a malfunction in which the target number of data is not reached is reduced.

[0035] In addition, even if multiple non-execution abnormalities occur during one prolonged abnormality, for example, when the prolonged abnormality exceeds multiple periods of the first period as shown in Fig. 2D, in the data processing device 10A of this embodiment, the fact that the start command is not output at the normal start timing and the execution of the data acquisition process is not started is counted as a non-execution abnormality by the abnormality counter, so that multiple non-execution abnormalities can be counted without omission. Furthermore, with this configuration, even if a prolonged abnormality occurs during the complementary execution of the data acquisition process and the data acquisition process cannot be executed at the normal start timing, the non-execution abnormality can be detected.

[0036] In the data processing device 10A of this embodiment, the data acquisition process is complementarily executed until the abnormality counter becomes 0, so that it can also handle the case where non-execution abnormalities occur consecutively and the number of occurrences of unstarted data acquisition processes is greater than the number of complement executions. Specifically, the complement execution is normally performed during a blank period not used for data acquisition processes, and if the blank period is during execution of data acquisition processes due to a prolonged abnormality, it is shifted to the subsequent blank period and executed, so that the number of missing data can be reduced by performing the complement execution as needed while executing the normal data acquisition process over multiple cycles.

[0037] Furthermore, since statistical data is calculated for each of the predetermined number of cycles of the first period based on data for the predetermined number of cycles, highly reliable statistical data can be obtained.

[0038] [Second embodiment] The data processing device 10B of the present disclosure includes a flag section instead of the abnormality counter 24 in Fig. 1 described in the first embodiment, and the flag section is set when an execution failure abnormality occurs and is reset when the data acquisition supplement command section 22A outputs a start command (i.e., when execution of the data acquisition process is started). Also, in this embodiment, an abnormality determination flag FLG4 is used as shown in Figs. 8 and 9 instead of the counter i (see Fig. 5) described in the first embodiment.

[0039] The data processing device 10B of this embodiment can also perform complementary execution of unstarted data acquisition processing at a later time, thereby reducing the amount of data loss when data acquisition is performed over a predetermined number of periods, and reducing the occurrence of problems such as not reaching the target number of data.

[0040] [Third embodiment] In the data processing device 10A of the first embodiment, even if the prolonged abnormality continues, the data acquisition processing unit 20 is configured not to terminate the data acquisition process until the EOF code is acquired. However, in the data processing device 10C of the present disclosure, the data acquisition processing unit 20 is configured to tolerate a prolonged abnormality in the data acquisition process exceeding three cycles of the first period, but to forcibly terminate the data acquisition process midway in the event of a prolonged abnormality exceeding four cycles of the first period.

[0041] Specifically, the command execution process PG2C shown in FIG. 10 is executed. "T1" is a counter for counting time. The command execution process PG2C is repeatedly executed every 1 / 10 [second] like the command execution process PG2 of the first embodiment, and when FLG2 is 1 (YES in S61), that is, when a start command is output, in step S63, the counter T1 is incremented by one, and the measurement data is stored in the buffer (S64) is repeated until an EOF code is acquired (YES in S66). However, in this embodiment, these processes are repeated during a period in which the count number of the counter T1 does not exceed 30 (30×1 / 10 [second]=3 [seconds]), that is, until a period of three cycles of the first cycle has elapsed since the data acquisition process was started (NO in S65), and after the period of three cycles has elapsed (YES in S65), the measurement data stored in the buffer is deleted (S71), and the execution of the measurement data acquisition is forcibly terminated (S68 and S69). Furthermore, whether the EOF code is obtained (YES in S66) and the data acquisition process is completed to the end (S67) or terminated midway (YES in S65), the counter T1 is reset to "0" and the command execution process PG2C is terminated (S70).

[0042] According to the data processing device 10C of this embodiment, it is possible to prevent a situation in which the number of occurrences of unstarted data acquisition processes increases as a result of the prolonged abnormality, while the corresponding amount of complementation cannot be executed and the number of missing data cannot be reduced. Note that, in this embodiment, a prolonged abnormality in the data acquisition process exceeding three first cycles is tolerated, but a configuration that tolerates a longer or shorter period may be acceptable, or a configuration that does not tolerate a prolonged abnormality exceeding the first cycle may be acceptable.

[0043] [Fourth embodiment] In the data processing device 10A of the first embodiment, when a non-execution abnormality is detected, complementary execution of the data acquisition process that has not been started due to the non-execution abnormality is performed during a subsequent blank period when the data acquisition process is not being executed. However, in the data processing device 10D of the present disclosure, complementary execution is possible at any time during the period when the data acquisition process is not being executed after the non-execution abnormality.

[0044] In the data processing device 10D of this embodiment, the data acquisition complementary command unit 22A, for example, acquires time information from the RTC 14 and operates every 1 / 10 [seconds], and when the abnormality detection unit 23 detects a non-execution abnormality, acquires information on whether the data acquisition process is being executed from the data acquisition processing unit 20, and outputs a start command if the data acquisition process is not being executed. That is, for example, as shown in FIG. 11, when the prolonged abnormality ends immediately after the normal start timing, the data acquisition complementary command unit 22A outputs a start command for complementary execution without waiting for the latter half of the first period to arrive, and the data acquisition process is complemented. Also, with this configuration, it is possible to output a start command for complementary execution during the first period, and it is possible to complement multiple data acquisition processes.

[0045] [Fifth embodiment] In the data processing device 10D of the fourth embodiment, when an non-execution abnormality is detected, if the data acquisition process is not currently being executed, the data acquisition process is executed as a complement. However, in the data processing device 10E of the present disclosure, the data acquisition process is executed as a complement only if the data acquisition process is not currently being executed and the period until the next normal start timing is longer than the normal execution time of the data acquisition process.

[0046] In the data processing device 10E of this embodiment, the data acquisition supplement command unit 22A has a remaining time determination unit that calculates the remaining time from the current time until the next normal start timing and determines whether the remaining time is equal to or longer than the normal execution time. When the abnormality detection unit 23 detects a non-execution abnormality, the remaining time determination unit 27 of the data acquisition supplement command unit 22A obtains information on whether or not the data acquisition process is being executed from the data acquisition processing unit 20, and obtains the determination result by the remaining time determination unit (S45 in FIG. 12), and outputs a start command if the data acquisition process is not being executed and the normal execution time of the data acquisition process or more remains until the next normal start timing.

[0047] According to the data processing device 10E of this embodiment, it is possible to prevent a new non-execution abnormality from occurring at the normal start timing due to complementary execution.

[0048] [Sixth embodiment] In the data processing device 10A of the first embodiment, the command execution process PG2 is repeatedly executed every 1 / 10 [second], but in the data processing device 10F of the present disclosure, the command execution process PG2F is started when a start command is output by the acquisition command process PG1F or the complement command process PG4F, and is not started when the start command is not output. When a start command is output, the command execution process PG2F is repeatedly executed until the EOF code is acquired. Below, referring to Figs. 13 to 16, the configuration different from the first embodiment will be mainly described.

[0049] 13, the acquisition command process PG1F is repeatedly executed every first period at the timing when the value of the one-second portion of the time information from the RTC 14 switches, as in the first embodiment, and if FLG1, which indicates that measurement data is not being acquired, is not "1" (YES in S10), a start command is output and the acquisition command process PG1F is exited (S11). In this embodiment, the configuration is such that FLG2, which means that a start command has been output, and FLG3, which means that an execution failure has occurred, are not set.

[0050] Then, when a start command is output by the acquisition command process PG1F, the command execution process PG2F is started. As shown in Fig. 14, the command execution process PG2F first sets FLG1, which indicates that measurement data is being acquired, to 1 (S22), and then repeatedly executes acquisition of measurement data until an EOF code is acquired (NO in S22, S24, and S25), and when the EOF code is acquired (YES in S25), moves the measurement data stored in the buffer to the data storage unit 25 (S26). When the acquisition of the measurement data is completed in this manner, FLG1 is reset to "0" and the process exits from the command execution process PG2F (S27).

[0051] Furthermore, as shown in FIG. 15, the abnormality detection process PG3F in this embodiment is repeatedly executed every first period at the timing when the command execution process PG2F is started after the execution of the acquisition command process PG1F, and determines whether or not measurement data is being acquired (S30). If measurement data is being acquired (YES in S30), it determines that there is an non-execution abnormality, increments the value of counter i by 1, and exits from the abnormality detection process PG3 (S31).

[0052] The complementary command processing PG4F of this embodiment is repeatedly executed for each first period at a timing delayed by 0.5 seconds from the timing at which the value of the 1-second portion of the time information from the RTC 14 switches, as in the first embodiment, and as shown in Fig. 16, if there is a non-execution abnormality (NO in S40) and measurement data is not being acquired (NO in S41), a start command for complementary execution of the measurement data acquisition process is output (S42), the value of the counter i is decremented by 1, and the complementary command processing PG4 is exited (S43). Then, in response to the complementary command processing PG4F outputting the start command, the command execution processing PG2F is started as described above to perform the measurement data acquisition process.

[0053] [Other embodiments] In the above embodiment, at the normal start timing when the data acquisition command unit 21A outputs a start command, if the data acquisition processing unit 20 is executing data acquisition processing, the data acquisition command unit 21A is configured not to output a start command. However, even if the data acquisition processing unit 20 is executing data acquisition processing, the data acquisition command unit 21A may be configured to always output a start command at the above timing, and the data acquisition processing unit 20 may be configured not to receive a new start command while executing data acquisition processing.

[0054] In this case, for example, the data acquisition processing unit 20 is connected to the data acquisition command unit 21A and the data acquisition supplement command unit 22A via a switch, and the switch is normally in an on state. When the data acquisition processing unit 20 receives a start command via the switch from the data acquisition command unit 21A or the data acquisition supplement command unit 22A, it turns the switch to an off state and then starts executing the data acquisition process. When the data acquisition process is completed, the switch is turned to an on state. While the data acquisition process is being executed, the switch is in an off state, and the data acquisition processing unit 20 does not receive a start command.

[0055] In the data processing devices 10A to 10F of the above embodiments, the statistical processing unit 26 calculates an average value as statistical data for all acquired measurement data, but this is not limited to this, and the statistical data may be, for example, a variance or multivariate analysis.

[0056] The data processing devices 10A to 10F of the above-described embodiments are connected to a power meter 81 of a facility 80 in a factory and are applied to acquire measurement data of the power consumption of the facility 80, but are not limited to this and may be applied to acquire other measurement data. Also, they may be applied to acquire simple communication data instead of measurement data.

[0057] <Additional Notes> The following describes the feature groups extracted from the above-described embodiments, while indicating their effects, etc., as necessary. Note that, in the following, for ease of understanding, the corresponding configurations in the above-described embodiments are appropriately indicated in parentheses, but these feature groups are not limited to the specific configurations indicated in parentheses.

[0058] [Feature 1] A data processing device (10A to 10F) comprising: a data acquisition unit (21) that executes a data acquisition process for acquiring data from an external device (81) every first period; an abnormality detection unit (23) that detects either or both of a non-execution abnormality that the data acquisition process is not executed or is forcibly terminated during execution; and a data acquisition completion unit (22) that, when the non-execution abnormality is detected, starts execution of the data acquisition process that has not been started or has not been terminated due to the non-execution abnormality during a period after the end of the data acquisition process in a subsequent period.

[0059] [Feature 2] The data processing device (10A, 10C to 10F) according to feature 1 further comprises an abnormality counter (24) that counts the number of data acquisition processes waiting to be executed by the data acquisition complement unit (22), and the data acquisition complement unit (22) starts executing the data acquisition processes until the abnormality counter (24) reaches 0.

[0060] [Feature 3] A data processing device (10B) according to feature 1, further comprising a flag section which is set when the non-execution abnormality occurs and which is reset when the data acquisition completion section (22) starts to execute the data acquisition process, and the data acquisition completion section (22) executes the data acquisition process on the condition that the flag section is set.

[0061] [Feature 4] The data processing device (10A to 10F) according to any one of features 1 to 3, wherein the data acquisition unit (21) tolerates a prolonged abnormality in which the execution time of the data acquisition process is longer than one cycle of the first cycle, and the abnormality detection unit (23) detects the non-execution abnormality in which the data acquisition process is not executed in the subsequent consecutive cycles due to the prolonged abnormality.

[0062] [Feature 5] A data processing device (10A to 10F) according to any one of features 1 to 4, further comprising a statistical processing unit (26) that calculates statistical data based on the data for each of a predetermined number of periods of the first cycle.

[0063] [Feature 6] A data processing program (PG1 to PG4, PG3B, PG4B, PG2C, PG4E) that causes a computer (10A to 10F) to function as a data acquisition unit (21) that executes a data acquisition process for acquiring data from an outside (81) every first period, an abnormality detection unit (23) that detects non-execution abnormalities, such as either the data acquisition process not being executed or being forcibly terminated during execution, or both, and a data acquisition completion unit (22) that, when the non-execution abnormality is detected, starts execution of the data acquisition process that has not been started or has not been terminated due to the non-execution abnormality during a period after the end of the data acquisition process in a subsequent period.

[0064] [Feature 7] The data processing program (PG3, PG4, PG4E) described in feature 6 causes the computer (10A) to function as an abnormality counter (24) that counts the number of data acquisition processes waiting to be executed by the data acquisition completion unit (22), and causes the computer (10A, 10C to 10F) to function so that the data acquisition completion unit (22) starts executing the data acquisition processes until the abnormality counter (24) reaches 0.

[0065] [Feature 8] The data processing program (PG3B, PG4B) described in feature 6 causes the computer (10A) to function as a flag unit that is set when the non-execution abnormality occurs and is reset when the data acquisition completion unit (22) starts execution of the data acquisition process, and the data acquisition completion unit (22) causes the computer (10B) to function to execute the data acquisition process on the condition that the flag unit is set.

[0066] [Feature 9] The data processing program (PG1 to PG4, PG3B, PG4B, PG2C, PG4E) described in any one of features 6 to 8, wherein the data acquisition unit (21) tolerates a prolonged abnormality in which the execution time of the data acquisition process is longer than one cycle of the first cycle, and the abnormality detection unit (23) causes the computer (10A to 10F) to function to detect a non-execution abnormality in which the data acquisition process is not executed in the subsequent consecutive cycles due to the prolonged abnormality.

[0067] [Feature 10] The data processing program (PG5) according to any one of features 6 to 9, which causes the computer (10A to 10F) to function as a statistical processing unit (26) that calculates statistical data based on the data for a predetermined number of periods of the first cycle, for each of the predetermined number of periods of the first cycle.

[0068] The data processing device of feature 1 and the computer executing the data processing program of feature 6 execute a data acquisition process to acquire data from an external source for each first period. The data processing device of feature 1 and the computer executing the data processing program of feature 6 detect either or both of the non-execution abnormalities of the data acquisition process not being started or being forcibly terminated during execution, and execute the data acquisition process that has not been started or not finished due to the non-execution abnormality during the period after the data acquisition process is finished in the period after the non-execution abnormality. In this way, the data processing device of feature 1 and the data processing program of feature 6 execute the data acquisition process that has not been started or not finished so as to complement it later (hereinafter, this is referred to as "complementary execution"), so that the number of data losses when data is acquired over a predetermined number of periods is reduced, and the occurrence of a malfunction in which the target number of data is not reached is reduced.

[0069] In the data processing device of feature 2 and the data processing program of feature 7, the number of data acquisition processes waiting for complementary execution is counted by an abnormality counter, and the data acquisition processes are complementarily executed until the abnormality counter reaches 0, so that it is possible to deal with a case where non-execution abnormalities occur consecutively and the number of occurrences of unstarted or unfinished data acquisition processes is greater than the number of complementary executions. Also, when the number of occurrences of unstarted or unfinished data acquisition processes is not greater than the number of complementary executions, it is possible to deal with a case where a flag unit is provided that is set by the occurrence of a non-execution abnormality and reset by complementary execution of the data acquisition processes, as in feature 3 and feature 8, and the data acquisition processes are complementarily executed on the condition that the flag unit is set.

[0070] In addition, cases in which the number of occurrences of unstarted or unfinished data acquisition processes can be greater than the number of complementary executions include cases, such as Features 4 and 9, where a prolonged anomaly in which the execution time of a data acquisition process is longer than one cycle of the first cycle is permitted, and a non-execution anomaly in which the data acquisition process does not start at the normal start timing due to the prolonged anomaly is detected.

[0071] Furthermore, in Features 5 and 10, since statistical data is calculated for each of the predetermined number of cycles of the first period based on data for the predetermined number of cycles, highly reliable statistical data can be obtained.

[0072] In addition, although this specification and drawings disclose specific examples of the technology included in the scope of the claims, the technology described in the claims is not limited to these specific examples, but includes various modifications and variations of the specific examples, as well as parts of the specific examples taken alone. [Explanation of symbols]

[0073] 10A~10F Data processing device (computer) 21 Data Acquisition Section 22 Data Acquisition Completion Section 23 Anomaly detection section 24 Abnormality Counter 26 Statistical Processing Unit 81 Power meter (external) PG1 Acquisition command processing program (data processing program) PG2,PG2C Command execution processing program (data processing program) PG3,PG3B Anomaly detection processing program (data processing program) PG4, PG4B, PG4E Complementary command processing program (data processing program) PG5 Statistical processing program (data processing program)

Claims

1. a data acquisition unit that starts execution of a data acquisition process for acquiring data from an external device at each fixed first cycle, and ends the process while leaving a blank period of a predetermined length or longer before the start of the next cycle if no abnormality is detected; an abnormality detection unit that detects one or both of non-execution abnormalities, that is, the data acquisition process is not executed and / or is forcibly terminated during execution; a data acquisition complementing unit that, when the non-execution abnormality is detected, starts the execution of the data acquisition process that has not been started or finished due to the non-execution abnormality during the subsequent blank period, and ends the execution during the blank period if no abnormality is detected; A data processing device comprising:

2. A data acquisition unit that executes a data acquisition process for acquiring data from an external device every first period; an abnormality detection unit that detects one or both of non-execution abnormalities, that is, the data acquisition process is not executed and / or is forcibly terminated during execution; a data acquisition complementing unit that, when the non-execution abnormality is detected, starts execution of the data acquisition process that has not been started or finished due to the non-execution abnormality during a period after the end of the data acquisition process in the subsequent period; an abnormality counter that counts the number of the data acquisition processes waiting to be executed by the data acquisition complementing unit; The data acquisition complementing unit is a data processing device that starts executing the data acquisition process until the abnormality counter becomes zero.

3. A data acquisition unit that executes a data acquisition process for acquiring data from an external device every first period; an abnormality detection unit that detects one or both of non-execution abnormalities, that is, the data acquisition process is not executed and / or is forcibly terminated during execution; a data acquisition complementing unit that, when the non-execution abnormality is detected, starts execution of the data acquisition process that has not been started or finished due to the non-execution abnormality during a period after the end of the data acquisition process in the subsequent period; a flag unit that is set when the non-execution abnormality occurs and is reset when the data acquisition complement unit starts executing the data acquisition process; The data acquisition complementing unit executes the data acquisition process on condition that the flag unit is set.

4. A data acquisition unit that executes a data acquisition process for acquiring data from an external device every first period; an abnormality detection unit that detects one or both of non-execution abnormalities, that is, the data acquisition process is not executed and / or is forcibly terminated during execution; a data acquisition complementing unit that, when the non-execution abnormality is detected, starts execution of the data acquisition process that has not been started or finished due to the non-execution abnormality during a period after the end of the data acquisition process in the subsequent period; The data acquisition unit tolerates a prolonged abnormality in which an execution time of the data acquisition process is longer than one cycle of the first cycle, The abnormality detection unit detects the non-execution abnormality in which the data acquisition process is not executed in the subsequent consecutive periods due to the long-term abnormality.

5. 5. The data processing device according to claim 1, further comprising a statistical processing unit that calculates statistical data based on the data for a predetermined number of periods of the first period for each of the predetermined number of periods.

6. A data processing device as described in any one of claims 1 to 4, wherein execution of the data acquisition process is forcibly terminated before the period is crossed if the data cannot be acquired from the outside.

7. A computer comprising: a data acquisition unit that starts execution of a data acquisition process for acquiring data from an external device at each fixed first cycle, and ends the process while leaving a blank period of a predetermined length or longer before the start of the next cycle if no abnormality is detected; an abnormality detection unit that detects one or both of non-execution abnormalities, that is, the data acquisition process is not executed and / or is forcibly terminated during execution; a data acquisition complementing unit that, when the non-execution abnormality is detected, starts the execution of the data acquisition process that has not been started or finished due to the non-execution abnormality during the subsequent blank period, and ends the execution during the blank period if no abnormality is detected; A data processing program that functions as a

8. A computer comprising: a data acquisition unit that executes a data acquisition process for acquiring data from an external device every first period; an abnormality detection unit that detects one or both of non-execution abnormalities, that is, the data acquisition process is not executed and / or is forcibly terminated during execution; a data acquisition complementing unit that, when the non-execution abnormality is detected, starts execution of the data acquisition process that has not been started or finished due to the non-execution abnormality during a period after the end of the data acquisition process in the subsequent period, causing the computer to function as an anomaly counter that counts the number of the data acquisition processes waiting to be executed by the data acquisition complementing unit; The data processing program causes the computer to function such that the data acquisition complementing unit continues to execute the data acquisition process until the abnormality counter reaches 0.

9. A computer comprising: a data acquisition unit that executes a data acquisition process for acquiring data from an external device every first period; an abnormality detection unit that detects one or both of non-execution abnormalities, that is, the data acquisition process is not executed and / or is forcibly terminated during execution; a data acquisition complementing unit that, when the non-execution abnormality is detected, starts execution of the data acquisition process that has not been started or finished due to the non-execution abnormality during a period after the end of the data acquisition process in the subsequent period, a flag unit that is set when the non-execution abnormality occurs and that is reset when the data acquisition complement unit starts executing the data acquisition process; The data acquisition complementing unit is a data processing program that causes the computer to function so as to execute the data acquisition process on condition that the flag unit is set.

10. A computer comprising: a data acquisition unit that executes a data acquisition process for acquiring data from an external device every first period; an abnormality detection unit that detects one or both of non-execution abnormalities, that is, the data acquisition process is not executed and / or is forcibly terminated during execution; a data acquisition complementing unit that, when the non-execution abnormality is detected, starts execution of the data acquisition process that has not been started or finished due to the non-execution abnormality during a period after the end of the data acquisition process in the subsequent period, The data acquisition unit tolerates a prolonged abnormality in which an execution time of the data acquisition process is longer than one cycle of the first cycle, The data processing program causes the computer to function, wherein the abnormality detection unit detects the non-execution abnormality in which the data acquisition process is not executed in successive subsequent periods due to the prolonged abnormality.

11. A data processing program described in any one of claims 7 to 10, which causes the computer to function as a statistical processing unit that calculates statistical data based on the data for a predetermined number of periods of the first cycle, for each of the predetermined number of periods.

12. A data processing program described in any one of claims 7 to 10, which causes the computer to function such that execution of the data acquisition process is forcibly terminated before the period is crossed if the data cannot be acquired from the outside.

Images