JP2019176221A - Data collection system - Google Patents

Abstract

To appropriately process data read out from a controller while preventing erroneous viewing of an attribution of the data in a host device even if there are the plurality of host devices.SOLUTION: A controller 1 is provided with a counter CNT. In the controller 1, a count value of the counter CNT is updated in each timing of changing attribution information tied up with data stored in a memory M1 by using a management point P as a vector. In the controller 1, the count value of the counter CNT is added to the data as identification information (ID) when storing the collected data into the memory M1. A dedicated OI/2 confirms whether the ID added to the data of difference is changed in each reading of the data of the difference from the controller 1, and if the changing of the ID is confirmed, the attribution information stored in the controller 1 is read out, and it rewrites the attribution information stored by oneself.SELECTED DRAWING: Figure 2

Description

  The present invention collects data periodically from the management target, stores it in the memory of the controller, periodically reads the data stored in the memory of the controller, and accumulates the data in the memory of the host device About the system.

  Conventionally, a controller for monitoring and controlling the state of equipment has been used for various purposes such as building facility monitoring. This controller has a function of collecting data such as temperature and humidity, and periodically collects data of various management points determined as management targets.

  However, in order to record and store the collected data, it is often impossible to prepare a memory having a sufficient capacity in the controller itself. For this reason, data stored in the memory (small capacity memory) of the controller is regularly read out and stored in the memory (large capacity memory) of the host device (for example, widely used). , See Patent Document 1).

  FIG. 7 shows an outline of a conventional data collection system. In this data collection system, the controller 1 is connected to a management point P (P1 to PN). The controller 1 is provided with a small-capacity memory M1. Further, a dedicated operator interface (hereinafter referred to as “dedicated OI”) 2 having a large-capacity memory M2 is connected to the controller 1 as a host device.

  The controller 1 collects data from the management points P1 to PN periodically (for example, every minute) and stores the data in the memory M1. As shown in FIG. 8A, the memory M1 stores data collected from the management points P1 to PN with a time stamp. In this example, data for several days is overwritten and stored in the memory M1.

  As shown in FIG. 8B, attribute information representing the attribute of the data is associated with the data stored in the memory M1 in association with the management point P from which the data is collected. The attribute of data represents the nature and characteristics of the data. For example, information indicating whether the data indicates an analog sensor output or ON / OFF of a digital device is attribute information. In FIG. 8B, “D” and “A” both represent data types, and “D” indicates that the data is digital data representing, for example, ON / OFF of a digital device. "Is an example of attribute information indicating that the data is analog data, such as analog sensor output. Such attribute information is stored in the controller 1 as attribute information associated with data stored in the memory M1 through a management point P at which the data is collected.

  The dedicated OI 2 accesses the controller 1 periodically (for example, every day), reads the difference data from the previous time to the current time stored in the memory M 1, and accumulates it in the memory M 2. As shown in FIG. 9A, the difference data read from the controller 1 is accumulated in the memory M2, such as the previous difference data # 1 and the current difference data # 2. In this example, at least one year of data is stored in the memory M2.

  On the other hand, as shown in FIG. 9, data (FIG. 9 (a)) and attribute information (FIG. 9 (b)) are also transmitted to each other through the management point P, as shown in FIG. It is linked and memorized. By matching the association between such data and the attribute information of the data with the association in the controller 1, the same attribute information (see FIG. 8B) as the attribute information stored in the controller 1 (FIG. 8B). 9 (b)) is also set and stored in the dedicated OI 2. As a result, the association between the data stored in the memory M2 of the dedicated OI 2 and the attribute information is the same as the association between the data stored in the controller 1 and the attribute information. Examples of attribute information linked to data include information indicating the type of data, device number, IO number, and data unit (number of significant digits, unit (° C or F °, etc.)) And the name of the data.

  In general, in this type of data collection system, attribute information associated with data is diverse. Therefore, in order to reduce processing load, data read from the controller 1 and accumulated in the dedicated OI 2 does not include attribute information. Only difference data. For this reason, the same attribute information is stored in both the controller 1 and the dedicated OI 2 when setting the attribute information.

JP 2002-023812 A

  However, in the above-described data collection system, when there is a change in the attribute of data collected from each point P (P1 to PN), the attribute information is changed in both the controller 1 and the dedicated OI2, and the controller It is necessary to match the association between data and attribute information between 1 and the dedicated OI 2.

  In this case, if there is only one host device that can be connected to one controller, the attribute information stored in the host device is rewritten and read from the controller when the attribute information stored in the controller is changed. Data can be processed appropriately. For example, when the attribute information of data of a management point stored in the controller is changed from analog data to digital data, the attribute information of the data of the management point is also changed from analog data to digital data in the host device. Thus, the data read from the controller can be appropriately processed.

  However, if there are two or more host devices that can change the attribute information stored in the controller, the other host device that has not changed the attribute information stored in the controller should appropriately read the data read from the controller. Can no longer be processed. For example, if the attribute information of data of a management point stored in the controller is changed from analog data to digital data, the attribute information of the data of the management point remains analog data in the other host device. The data read from the controller cannot be properly processed.

  This problem will be specifically described with reference to FIG. In this example, a remote monitoring device 4 is connected as another host device via the network 3, and the remote monitoring device 4 also has a memory M3 (large capacity of difference data) read from the controller 1 in the same manner as the dedicated OI 2. It is assumed that data is stored in the memory.

  Here, it is assumed that the attribute information of the data in the controller 1 is changed from the remote monitoring device 4. In this case, in conjunction with the change of the attribute information in the controller 1, the remote monitoring device 4 also changes the attribute information in the device (remote monitoring device 4). For this reason, the attribute information in the controller 1 and the attribute information in the remote monitoring device 4 are the same, and the remote monitoring device 4 can appropriately process the data read from the controller 1.

  However, in the dedicated OI 2, even if the attribute information of the data in the controller 1 is changed from the remote monitoring device 4, it cannot be known and the attribute information in the dedicated OI 2 is not changed. For this reason, in the dedicated OI 2, even after the attribute information in the controller 1 is changed, the attribute information before the change remains, and the data read from the controller 1 cannot be appropriately processed.

  The present invention was made in order to solve such a problem, and the object of the present invention is to avoid misrecognizing data attributes even in the case where there are a plurality of higher-level devices. An object of the present invention is to provide a data collection system capable of appropriately processing data read from a controller.

  In order to achieve such an object, the present invention stores a data collection unit (11) configured to periodically collect data from a management target (P), and data collected by the data collection unit. First memory (M1), and a first attribute information storage unit (12) for storing attribute information associated with data stored in the first memory through a management target from which the data is collected And a difference data reading unit (21) configured to periodically access the controller and read difference data from the previous time to the current time stored in the first memory. And the second memory (M2) having a larger capacity than the first memory in which the difference data read by the difference data reading unit is stored, and the data stored in the second memory A data collection system including a plurality of higher-level devices (2, 4) including a second attribute information storage unit (22) for storing attribute information associated with a management target from which data is collected The controller (1) adds the identification information corresponding to the attribute information stored in the first attribute information storage unit to the data collected by the data collection unit in the first memory. And an identification information changing unit (13) configured to change the identification information every time the attribute information stored in the first attribute information storage unit is changed. Each time the difference data reading unit reads the difference data from the controller, the host device (2, 4) checks whether the identification information added to the difference data has been changed. And identification information When it is confirmed that the attribute information has been changed, the attribute information stored in the first attribute information storage unit in the controller is read, and the attribute information stored in the second attribute information storage unit is rewritten. The attribute information rewriting part (24) comprised is provided.

  In the present invention, the controller includes an identification information changing unit that changes the identification information added to the data stored in the first memory every time the attribute information stored in the first attribute information storage unit is changed. Yes. For example, a counter that changes the count value as identification information every time the attribute information stored in the first attribute information storage unit is changed is provided as the identification information changing unit. This identification information is added to the data collected from the management target when the data is stored in the first memory.

  In the present invention, each time the difference data reading unit reads the difference data from the controller, the higher-level device confirms whether or not the identification information added to the difference data is changed. Here, when it is confirmed that the identification information has been changed, the higher-level device reads out the attribute information stored in the first attribute information storage unit in the controller and stores it in the second attribute information storage unit. Rewrite the attribute information. That is, it is determined that the attribute information in the controller has been changed from another host device, and the attribute information in the host device is rewritten. As a result, the attribute information in the controller matches the attribute information in the host device.

  In the above description, as an example, constituent elements on the drawing corresponding to the constituent elements of the invention are indicated by reference numerals with parentheses.

  As described above, according to the present invention, every time the difference data is read from the controller, it is confirmed whether or not the identification information added to the difference data is changed, and the identification information is changed. Since the attribute information stored in the controller is read and the attribute information in the host device is rewritten, the attribute information in the controller can be changed even if there are multiple host devices. By matching the attribute information in the host device, the host device can appropriately process the data read from the controller without mistaking the data attribute.

FIG. 1 is a diagram showing an outline of a data collection system according to an embodiment of the present invention. FIG. 2 is a diagram showing how the attribute information in the controller is changed from the remote monitoring device in this data collection system. FIG. 3 is a flowchart for explaining the processing operation in the host device (dedicated OI, remote monitoring device). FIG. 4 is a flowchart for explaining the processing operation in the controller. FIG. 5 is a functional block diagram of the main part of the controller. FIG. 6 is a functional block diagram of the main part of the host device. FIG. 7 is a diagram showing an outline of a conventional data collection system. FIG. 8 is a diagram illustrating data stored in the memory of the controller and attribute information associated with the data. FIG. 9 is a diagram illustrating data stored in the dedicated OI memory and attribute information associated with the data. FIG. 10 is a diagram illustrating a problem when there are two or more higher-level devices.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. FIG. 1 is a diagram showing an outline of a data collection system according to an embodiment of the present invention. 10, the same reference numerals as those in FIG. 10 denote the same or equivalent components as those described with reference to FIG. 10, and the description thereof will be omitted.

  In this data collection system, the controller 1 includes a counter CNT whose count value is increased each time the attribute information stored in the controller 1 is changed.

  The count value counted by the counter CNT is used as identification information determined corresponding to the attribute information stored in the controller 1 when the data collected from the management points P1 to PN is stored in the memory M1. To be added. This identification information is used as information for determining whether or not the attribute information stored in the controller 1 has been changed. In this example, the count value (identification information) of the counter CNT is initially “0”. Hereinafter, the identification information added to the data is also referred to as ID.

  In this data collection system, the same attribute information as the attribute information stored in the controller 1 is set and stored in the dedicated OI 2 and the remote monitoring device 4. That is, in each of the dedicated OI 2 and the controller 1, attribute information (correspondence between data and attribute information) associated with data through the management point P is the same. For this reason, the same attribute information as that of the controller 1 is also associated with the data stored in the memory M2 of the dedicated OI 2 and the data stored in the memory M3 of the remote monitoring device 4 through the management point P.

  In the dedicated OI2, an ID corresponding to the attribute information stored in the dedicated OI2 is stored as the latest ID. The remote monitoring device 4 also stores the ID corresponding to the attribute information stored in the remote monitoring device 4 as the latest ID. In this example, “0” is stored as the latest ID in both the dedicated OI 2 and the remote monitoring device 4.

[Change of attribute information in the controller from the remote monitoring device]
Now, it is assumed that the attribute information in the controller 1 is changed from the remote monitoring device 4 (see FIG. 2). In this case, the user changes the attribute information in the remote monitoring device 4. The remote monitoring device 4 reads out the change contents of the attribute information from the user (FIG. 3: step S101) and confirms that there is a change (YES in step S102). (Step S103).

  When receiving the change contents of the attribute information from the remote monitoring device 4 (FIG. 4: YES in step S201), the controller 1 changes the attribute information in the remote monitoring device 4 (step S202). Then, the count value of the counter CNT is increased (step S203). In this case, the count value of the counter CNT is “1”.

  Then, the controller 1 returns the count value “1” of the counter CNT to the remote monitoring device 4 (step S204). When the count value “1” is returned from the controller 1, the remote monitoring device 4 rewrites the count value “1” as the latest ID (FIG. 3: step S104).

  At the data collection timing (YES in step S205), the controller 1 collects data from the management points P1 to PN (step S206), and stores the collected data in the memory M1. At this time, the controller 1 adds the count value of the counter CNT to the data stored in the memory M1 as an ID (step S207).

  The dedicated OI 2 reads the difference data from the previous time to the current time stored in the memory M 1 of the controller 1 at the data read timing (FIG. 3: YES in step S 105) (step S 106). Then, the ID added to the difference data is compared with the latest ID stored in the dedicated OI2, and there is data to which an ID different from the latest ID stored in the dedicated OI2 is added. It is confirmed whether or not (step S107).

  In the controller 1, after the attribute information is changed, the ID added to the data stored in the memory M1 is changed. For this reason, in step S107, the dedicated OI 2 determines that there is data to which an ID different from the latest ID stored in the dedicated OI 2 is present (detects a change in ID).

  When the change of ID is detected (YES in step S107), the dedicated OI 2 outputs the data before the ID change among the read data to the file (step S108), and counts the latest attribute information from the controller 1 and the counter CNT. The value is read (step S109), and the attribute information in the dedicated OI2 and the latest ID are rewritten (step S110). Then, the difference data read from the memory M1 of the controller 1 is accumulated in the memory M2 (step S111).

  In the dedicated OI2, after the attribute information in the dedicated OI2 and the latest ID are rewritten, the ID added to the difference data read from the controller 1 matches the latest ID stored in the dedicated OI2. (NO in step S107). Therefore, the dedicated OI 2 accumulates the difference data read from the controller 1 in the memory M2 without going through steps S108 to S110 (step S111).

  Thus, in this embodiment, when the attribute information in the controller 1 is changed from the remote monitoring device 4, the attribute information in the dedicated OI 2 is rewritten to the latest attribute information. The attribute information in the dedicated OI 2 matches the attribute information in the dedicated OI 2, and even in the dedicated OI 2, the data read from the controller 1 can be appropriately processed without mistaking the data attribute.

  In the above description, the case where the attribute information in the controller 1 is changed from the remote monitoring device 4 is described as an example. However, the remote monitoring is similarly performed when the attribute information in the controller 1 is changed from the dedicated OI 2. The attribute information stored in the device 4 is rewritten with the latest attribute information, and the attribute information in the controller 1 and the attribute information in the remote monitoring device 4 match. The data read from the controller 1 can be appropriately processed without misunderstanding the attribute.

  FIG. 5 shows a functional block diagram of the main part of the controller 1. The controller 1 is realized by hardware including a processor and a storage device, and a program that realizes various functions in cooperation with these hardware, and includes a data collection unit 11, a memory M1, an attribute information storage unit 12, , A counter CNT, an identification information adding unit 13, and an attribute information change content receiving unit 14.

  In the controller 1, the data collection unit 11 periodically collects data from the management points P1 to PN. The data collected by the data collection unit 11 is stored in the memory M1. The attribute information storage unit 12 stores attribute information associated with data stored in the memory M1 through a management point P at which the data is collected. The attribute information change content receiving unit 14 receives the attribute information change content sent from the host device (dedicated OI 2, remote monitoring device 4).

  The counter CNT increases the count value every time the attribute information change content receiving unit 14 receives the change content of the attribute information sent from the host device. When the data collected by the data collection unit 11 is stored in the memory M1, the identification information addition unit 13 adds the count value from the counter CNT as an ID to the data.

  FIG. 6 shows a functional block diagram of the main part of the host device (dedicated OI 2 and remote monitoring device 4). FIG. 6 shows a functional block diagram of the main part of the dedicated OI 2 on behalf of the host device. The remote monitoring device 4 has a similar function.

  The dedicated OI 2 includes a differential data reading unit 21, a memory M 2, an attribute information storage unit 22, an identification information storage unit 23, and an attribute information rewriting unit 24. Similar to the controller 1, the dedicated OI 2 is also realized by hardware including a processor and a storage device, and a program that realizes various functions in cooperation with these hardware.

  In the dedicated OI 2, the difference data reading unit 21 periodically accesses the controller 1 and reads the difference data from the previous time to the current time stored in the memory M 1. Difference data read by the difference data reading unit 21 is stored in the memory M2. The attribute information storage unit 22 stores attribute information associated with data accumulated in the memory M2 through a management point P at which the data is collected. In the identification information storage unit 23, identification information (ID) corresponding to the attribute information stored in the attribute information storage unit 22 is stored as the latest ID.

  Each time the difference data reading unit 21 reads the difference data from the controller 1, the attribute information rewriting unit 24 reads the ID added to the difference data and the latest ID stored in the identification information storage unit 23. If there is an ID different from the latest ID, the attribute information stored in the attribute information storage unit 12 in the controller 1 is read and the attribute information stored in the attribute information storage unit 22 is rewritten. At the same time, the latest ID stored in the identification information storage unit 23 is rewritten to an ID corresponding to the rewritten attribute information.

  In the present embodiment, the attribute information rewriting unit 24 reads the count value from the counter CNT in the controller 1, and uses the read count value as the newest latest ID to store the latest ID stored in the identification information storage unit 23. (FIG. 3: Steps S109 and S110), the latest ID stored in the identification information storage unit 23 may be rewritten with the ID determined to be changed in Step S107 as the new latest ID. .

  Further, in the above-described example, two upper devices, the dedicated OI 2 and the remote monitoring device 4, are used, but it goes without saying that the upper device is not limited to two. Further, the host device only needs to be able to detect the change of the ID added to the difference data, and the latest ID is not necessarily used to detect the change of the ID. For example, it may be detected that the ID has been changed by comparing the IDs added to the difference data.

[Extension of the embodiment]
The present invention has been described above with reference to the embodiment. However, the present invention is not limited to the above embodiment. Various changes that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the scope of the technical idea of the present invention.

  DESCRIPTION OF SYMBOLS 1 ... Controller, 2 ... Dedicated OI, 3 ... Network, 4 ... Remote monitoring apparatus, 11 ... Data collection part, 12 ... Attribute information storage part, 13 ... Identification information addition part, 14 ... Attribute information change content reception part, 21 ... Difference data reading unit, 22 ... attribute information storage unit, 23 ... identification information storage unit, 24 ... attribute information rewriting unit, CNT ... counter, M1-M3 ... memory, P (P1-PN) ... management point.

Claims (3)

A data collection unit configured to periodically collect data from the management target, a first memory in which data collected by the data collection unit is stored, and data stored in the first memory A controller including a first attribute information storage unit that stores attribute information associated with the management target from which the data is collected;
The difference data reading unit configured to periodically access the controller and read the difference data from the previous time to the current time stored in the first memory, and read by the difference data reading unit A second memory having a larger capacity than the first memory in which the difference data is stored, and an attribute associated with the data to be stored in the second memory via the management target from which the data is collected A data collection system comprising a plurality of higher-level devices comprising a second attribute information storage unit for storing information,
The controller is
When the data collected by the data collection unit is stored in the first memory, identification information corresponding to the attribute information stored in the first attribute information storage unit is added to the data. An identification information adding unit;
An identification information changing unit configured to change the identification information each time the attribute information stored in the first attribute information storage unit is changed,
The host device is
Each time the difference data reading unit reads the difference data from the controller, it is confirmed whether or not the identification information added to the difference data has been changed, and the identification information has been changed. Attribute information stored in the first attribute information storage unit in the controller is read, and the attribute information stored in the second attribute information storage unit is rewritten. A data collection system comprising a rewriting unit. The data collection system of claim 1, wherein
The host device is
An identification information storage unit that stores identification information corresponding to the attribute information stored in the second attribute information storage unit as the latest identification information;
The attribute information rewriting unit
Each time the difference data reading unit reads the difference data from the controller, the identification information added to the difference data is compared with the latest identification information stored in the identification information storage unit. When there is identification information different from the identification information, the attribute information stored in the first attribute information storage unit in the controller is read, and the attribute information stored in the second attribute information storage unit is read out. The data collection system characterized by rewriting and rewriting the newest identification information memorize | stored in the said identification information storage part to the identification information corresponding to the attribute information after rewriting. In the data collection system according to claim 1 or 2,
The identification information changing unit
The data collection system, wherein the attribute information stored in the first attribute information storage unit is a counter that changes the count value as the identification information each time the attribute information is changed.

Images