Module System

Abstract

To reduce failures in a form of system.SOLUTION: Modules 1-3 in a module system includes respectively: memories 15, 25, 35 storing data; memory map information storage units 143, 243, 344 storing memory map information; and data read units 142, 240, 340 for reading data from a lower module on the basis of the memory map information. The memory map information is configured so that information on areas of memories storing common data of the modules is common for the modules.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a modular system. To The present invention relates to a module system that can be used in, for example, a measurement system that collects data from a plurality of sensor modules and transmits the data to an external device. To This is related to. [Background technology]

[0002] 2. Description of the Related Art There has been proposed a measurement system that converts a measurement signal from a sensor into an analog-to-digital (AD) signal and transmits the AD-converted measurement data to an external device (see Patent Document 1). The system disclosed in Patent Document 1 is composed of multiple modules linked by connectors. The modules used in this system are assumed to be devices that can be used immediately by simply connecting them, and are required to use a standard connector (specifically, USB (Universal Serial Bus)). Such a system is suitable for the practical free entry of multiple companies.

[0003] If we were to assume that multiple companies would essentially freely enter the market, it would be possible to freely add a wide variety of modules, and so pre-shipment operation checks in the form of a system in which multiple modules are linked would be incomplete, unlike product supply from a single company or multiple companies in a business alliance. Therefore, improvements are needed to reduce the occurrence of defects in the form of systems. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2020-67856 A Summary of the Invention [Problem to be solved by the invention]

[0005] The present invention has been made to solve the above problems, and provides a module system that can reduce the occurrence of problems even when the system configuration is changed by adding or removing modules. M The purpose is to provide. [Means for solving the problem]

[0008] Further, the module system of the present invention is a module system including a plurality of modules connected in cascade, each module comprising a memory configured to store data, a memory map information storage unit configured to store memory map information, a data reading unit configured to read data from a lower module based on the memory map information and store it in the memory, and a flag control unit configured to control a read flag stored in the memory, wherein the memory map information is common to each module in terms of information relating to a dedicated area of ​​the memory for storing the read flag of each module, the data reading unit reads data from the lower module when the read flag of the lower module is a specified numerical value, and the flag control unit resets the read flag of the own device to the specified numerical value when the data stored in the memory of the own device is updated by reading by the data reading unit and when data stored in the memory of the own device is read from a higher module, and sets the read flag of the own device to a numerical value other than the specified numerical value.

[0009] Further, the module system according to the present invention is a module system including a plurality of modules connected in cascade, each module comprising a memory configured to store data, a memory map information storage unit configured to store memory map information, a data reading unit configured to read data from other modules based on the memory map information and store it in the memory, and a number control unit configured to control the memory numbers stored in the memory, wherein the memory map information is common to each module in terms of information relating to dedicated areas of the memory that store the memory numbers of each module, the data reading unit reads data from the lower module when the memory number of the lower module is the same as or greater than the memory number stored in the memory of the device itself, and the number control unit resets the memory number of the device itself to an initial value common to each module in an initial state, and updates the memory number of the device itself to a value greater than the memory number of the lower module when data is read from the lower module.

[0010] In one configuration example of the module system according to the present invention, each module performs a read operation based on the data stored in the memory of the module after the data read unit reads the data. The memory map information includes an area of ​​the memory that is assigned as a unique data area of ​​each module. The memory map information updating unit is further configured to update the memory map information. Furthermore, in one configuration example of the module system according to the present invention, the data reading unit is characterized in that it reads data from areas assigned as unique data areas of all modules from the lower module based on the memory map information.

[0011] Moreover, in a module system according to the present invention, in a module system including a plurality of modules connected in cascade, each module includes a memory configured to store data, a memory map information storage unit configured to store memory map information, a first data reading unit configured to read data from a lower module based on the memory map information and store the data in a first area of ​​the memory, a data copying unit configured to copy the data stored in the first area after reading by the first data reading unit to a second area of ​​the memory when the module is the most significant module, a second data reading unit configured to read data in the second area of ​​a higher module after reading by the first data reading unit and store the data in the second area of ​​the memory of the module when the module is other than the most significant module, and a data copying unit configured to copy the data stored in the second area of ​​the memory of the module after reading by the second data reading unit to a second area of ​​the memory of the module when the module is other than the most significant module. of In the first area of ​​the memory of the own device, copy and a data update unit configured to update the data.

[0012] In addition, in one configuration example of the module system according to the present invention, the first data reading unit, the data copying unit, the second data reading unit, and the data updating unit are each characterized by repeating processing multiple times. In one configuration example of the module system according to the present invention, when the module itself is a top-level module, the module performs the following operation based on the data stored in the first area of ​​the memory of the module itself after the data is read by the first data reading unit: The memory map information includes an area of ​​the memory that is assigned as a unique data area of ​​each module. updating memory map information, and when the own device is not the highest-level module, based on data stored in the first area of ​​the memory of the own device after the data update by the data update unit The memory map information includes an area of ​​the memory that is assigned as a unique data area of ​​each module. The memory map information updating unit is further configured to update the memory map information. In one configuration example of the module system according to the present invention, each module further includes a setting change unit configured to rewrite data of other modules that are targets of setting change among data stored in the second area of ​​the memory of the own device when the own device is the top module. The other module whose setting is to be changed is a module that needs to be rewritten with changed setting data sent from outside. It is characterized by the above. Furthermore, in one configuration example of the module system according to the present invention, the first data reading unit is characterized in that it reads data from the first area, which is assigned as a unique data area of ​​all modules from the lower module based on the memory map information. Effect of the Invention

[0015] According to the present invention, by making information regarding the memory area that stores the common data of each module common to each module, even if the system configuration is changed by adding or removing a module, there is no need to change the address settings, thereby reducing the occurrence of malfunctions.

[0016] Furthermore, in the present invention, by making the information regarding the dedicated areas of the memory that store the unique data of each module common to each module, even if the system configuration is changed by adding or removing a module, there is no need to change the address settings, thereby reducing the occurrence of malfunctions.

[0017] Furthermore, in the present invention, by providing a flag control unit in each module, even if the system configuration is changed by adding or removing a module, there is no need to change the address settings, thereby reducing the occurrence of malfunctions.

[0018] Furthermore, in the present invention, by providing a number control unit in each module, even if the system configuration is changed by adding or removing a module, there is no need to change the address settings, thereby reducing the occurrence of malfunctions.

[0019] Furthermore, in the present invention, by providing each module with a first data reading unit, a data copying unit, a second data reading unit, and a data updating unit, even if the system configuration is changed by adding or removing a module, it is not necessary to change the address settings, thereby reducing the occurrence of malfunctions.

[0020] Furthermore, in the present invention, by providing a setting change section in the highest-level module, the highest-level module can change the settings of lower-level modules. [Brief description of the drawings]

[0021] [Figure 1] FIG. 1 is a diagram showing an AD module, an extension module, and a network module according to a first embodiment of the present invention, and a diagram showing the configuration of a measurement system according to the first embodiment of the present invention. [Diagram 2] FIG. 2 is a block diagram showing a configuration of an AD module according to a first embodiment of the present invention. [Diagram 3] FIG. 3 is a block diagram showing a configuration of a network module according to the first embodiment of the present invention. [Figure 4] FIG. 4 is a block diagram showing a configuration of an extension module according to a first embodiment of the present invention. [Diagram 5] FIG. 5 is a diagram for explaining the operation of the measurement system according to the first embodiment of the present invention. [Figure 6] FIG. 6 is a diagram showing an example of a common memory map according to the first embodiment of the present invention. [Figure 7] FIG. 7 is a diagram showing an example of a common memory map according to the second embodiment of the present invention. [Figure 8] FIG. 8 is a diagram showing an example of a common memory map according to the second embodiment of the present invention. [Figure 9] FIG. 9 is a diagram illustrating data transfer in the second embodiment of the present invention. [Figure 10]FIG. 10 is a diagram illustrating data transfer in the third embodiment of the present invention. [Figure 11] FIG. 11 is a flowchart illustrating the operation of the upper module according to the third embodiment of the present invention. [Figure 12] FIG. 12 is a flowchart illustrating the operation of a lower module according to the third embodiment of the present invention. [Figure 13] FIG. 13 is a diagram showing another example of data transfer in the third embodiment of the present invention. [Figure 14] FIG. 14 is a diagram illustrating data transfer in the fourth embodiment of the present invention. [Figure 15] FIG. 15 is a flowchart illustrating the operation of the upper module according to the fourth embodiment of the present invention. [Figure 16] FIG. 16 is a flowchart illustrating the operation of a lower module according to the fourth embodiment of the present invention. [Figure 17] FIG. 17 is a diagram showing another example of data transfer in the fourth embodiment of the present invention. [Figure 18] FIG. 18 is a diagram illustrating data transfer in the fifth embodiment of the present invention. [Figure 19] FIG. 19 is a diagram illustrating data transfer in the fifth embodiment of the present invention. [Figure 20] FIG. 20 is a diagram illustrating data transfer in the fifth embodiment of the present invention. [Figure 21] FIG. 21 is a flowchart explaining the operation of each module except for the highest-level module according to the fifth embodiment of the present invention. [Figure 22] FIG. 22 is a flowchart illustrating the operation of the highest-level module according to the fifth embodiment of the present invention. [Figure 23] FIG. 23 is a flowchart explaining the operation of each module except for the highest-level module according to the sixth embodiment of the present invention. [Figure 24] FIG. 24 is a flowchart illustrating the operation of the highest-level module according to the sixth embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0022] [Principle of the invention] A particular problem that can easily occur in a module system is when a new module is developed that allows for the addition of any number of modules. Since the newly developed module is different from the basic essential modules such as power supplies and sensors that are limited in number, it becomes impossible to estimate the complete system. The inventors have focused on the occurrence of problems in such cases.

[0023] We also noticed that when a new module is added, the mapping of memory that stores the data transferred to the upper side becomes an issue. In other words, the conventional method of dealing with this issue requires the user to configure it based on specialized knowledge. However, configuring goes against the idea of ​​a module that can be used immediately by simply connecting it.

[0024] Therefore, the inventor came to the conclusion that it is essential to specify that the memory maps of each module are the same and that the procedure for reading data from the upper side is the same. On top of that, the inventor came to the conclusion that it is possible to reduce the occurrence of malfunctions by providing a dedicated area for cases where different data other than the same data needs to be transferred in each module, and by using a flag to prohibit overwriting when a new additional module is inserted.

[0025] [First Example] Hereinafter, embodiments of the present invention will be described with reference to the drawings. Fig. 1(A) is a diagram showing an AD module, an extension module, and a network module (hereinafter, referred to as a NW module) according to a first embodiment of the present invention, and Fig. 1(B) is a diagram showing the configuration of a measurement system (module system).

[0026] The AD module 1 is equipped with a communication / power-receiving female connector 10 for signal input and power supply from the sensor 4, which detachably fits with the communication / power-receiving connector of the sensor 4 on the lower side (left side in Figure 1), and a communication / power-receiving male connector 11 for data communication and power reception, which detachably fits with the communication / power-receiving connector of the module on the upper side (right side in Figure 1).

[0027] The AD module 1 has the function of converting an analog signal input from the communication / power-receiving female connector 10 into AD, further encrypting the digital data after AD conversion, and storing the encrypted digital data, the function of receiving power from the communication / power-receiving male connector 11 (or the communication / power-receiving female connector 10), and the function of supplying the received power to the outside via the communication / power-receiving female connector 10 (or the communication / power-receiving male connector 11).

[0028] The NW module 2 includes a communication / power-receiving female connector 20 for data communication and power supply that detachably fits with the communication / power-receiving connector of the lower module, a communication / power-receiving male connector 21 for receiving power from the power source 5 that detachably fits with the communication / power-receiving connector of the power source 5, an antenna 22 for wireless communication, and a communication connector 28 for wired communication.

[0029] The NW module 2 has the function of reading data from a module (expansion module 3) connected to the communication / power-receiving female connector 20 and transmitting the data wirelessly or wired to the outside via the network, the function of receiving power from the communication / power-receiving male connector 21 (or the communication / power-receiving female connector 20), and the function of supplying the received power to the outside via the communication / power-receiving female connector 20 (or the communication / power-receiving male connector 21).

[0030] The expansion module 3 is equipped with a communication / power supply / reception female connector 30 for data communication and power supply that detachably fits with the communication / power supply / reception connector of the lower module, a communication / power supply / reception male connector 31 for data communication and power reception that detachably fits with the communication / power supply / reception connector of the upper module, and a display 32.

[0031] In this embodiment, a case will be described where the extension module 3 is a monitor module. The monitor module has a function of accumulating data from a lower module (AD module 1), a function of displaying the data, a function of receiving power from the communication / power-receiving male connector 31 (or the communication / power-receiving female connector 30), and a function of supplying the received power to the outside via the communication / power-receiving female connector 30 (or the communication / power-receiving male connector 31). It goes without saying that the extension module 3 does not have to be a monitor module.

[0032] The sensor 4 has a communication / power-receiving male connector 40 for outputting signals and supplying power to the AD module 1, which detachably fits into the communication / power-receiving female connector 10 of the AD module 1. The sensor 4 has a function of detecting quantities to be measured, such as temperature, humidity, pressure, acceleration, seismic intensity, precipitation, and oxidation-reduction amount, and outputting an analog signal of the measurement result (e.g., a 4-20 mA current signal), and a function of receiving power from the communication / power-receiving male connector 40.

[0033] In this way, the AD module 1, the NW module 2, the extension module 3, the sensor 4, and the power source 5 each have a connector of the same standard, and by inserting the communication and power receiving male connector 40 of the sensor 4 into the communication and power receiving female connector 10 of the AD module 1, inserting the communication and power receiving male connector 11 of the AD module 1 into the communication and power receiving female connector 30 of the extension module 3, and inserting the communication and power receiving male connector 31 of the extension module 3 into the communication and power receiving female connector 20 of the NW module 2, it is possible to connect the sensor 4, the AD module 1, the extension module 3, and the NW module 2 as shown in Fig. 1(B). Furthermore, by inserting the communication and power receiving male connector 21 of the NW module 2 into the communication and power receiving female connector 50 of the power source 5, it is possible to connect the NW module 2 and the power source 5.

[0034] The NW module 2 operates by receiving power from a power source 5 , and supplies the power received from the power source 5 to the extension module 3 via the communication / power receiving female connector 20 . The extension module 3 operates by receiving power from the NW module 2 and can supply the power received from the NW module 2 to the AD module 1 via the communication / power-receiving female connector 30 .

[0035] The AD module 1 operates by receiving power from the expansion module 3, and can also supply the power received from the expansion module 3 to the sensor 4 via the communication / power receiving female connector 10. However, in the present invention, supplying power to the sensor 4 is not a required configuration, and the sensor 4 may operate using its own power source.

[0036] An example of the communication / power receiving / supplying female connectors 10, 20, 30, 50 and the communication / power receiving / supplying male connectors 11, 21, 31, 40 is a USB connector. It goes without saying that the connector is not limited to a USB.

[0037] Next, a more detailed description will be given of the configurations and operations of the AD module 1, the NW module 2, and the extension module 3. Fig. 2 is a block diagram showing the configuration of the AD module 1. The AD module 1 includes a communication / power-receiving female connector 10, a communication / power-receiving male connector 11, a USB controller 12 that controls transmission and reception of signals through the communication / power-receiving female connector 10 or the communication / power-receiving male connector 11, an AD conversion unit 13, a CPU (Central Processing Unit) 14, and a memory 15.

[0038] The power supply lines of AD module 1 include a positive power supply line 16 that connects the positive power supply terminal (VBUS) of communication / power receiving female connector 10 and the positive power supply terminal (VBUS) of communication / power receiving male connector 11, and a negative power supply line that connects the GND terminal of communication / power receiving female connector 10 and the GND terminal of communication / power receiving male connector 11, but the negative power supply line is omitted in Figure 2.

[0039] CPU 14 executes the processes described in this embodiment according to the programs stored in memory 15, and functions as encryption unit 140, data transmission unit 141, data reading unit 142 (first data reading unit), memory map information storage unit 143, memory map information update unit 144, data reading unit 145 (second data reading unit), data update unit 146, flag control unit 147, and number control unit 148. However, in this embodiment, memory map information update unit 144, data reading unit 145, data update unit 146, flag control unit 147, and number control unit 148 are not necessary.

[0040] The USB controller 12, the AD conversion unit 13, the CPU 14, and the memory 15 operate by receiving power supply from the communication / power receiving male connector 11 or the communication / power receiving female connector 10.

[0041] 3 is a block diagram showing the configuration of the NW module 2. The NW module 2 includes a communication / power-receiving female connector 20, a communication / power-receiving male connector 21, an antenna 22, a USB controller 23 that controls transmission and reception of signals through the communication / power-receiving female connector 20 or the communication / power-receiving male connector 21, a CPU 24, a memory 25, a communication circuit 26 for wireless communication, a communication connector 28, and a communication circuit 29 for wired communication.

[0042] As in the case of the AD module 1, the power lines of the NW module 2 include a positive power line 27 that connects the positive power terminal (VBUS) of the communication / power receiving female connector 20 and the positive power terminal (VBUS) of the communication / power receiving male connector 21, and a negative power line that connects the GND terminal of the communication / power receiving female connector 20 and the GND terminal of the communication / power receiving male connector 21, but the negative power line is not shown in Figure 3.

[0043] The CPU 24 executes the processes described in this embodiment according to the programs stored in the memory 25, and functions as a data reading unit 240, a communication unit 241, a data transmission unit 242, a memory map information storage unit 243, a memory map information update unit 244, a data copying unit 245, a setting change unit 246, a data receiving unit 247, a flag control unit 248, and a number control unit 249. However, in this embodiment, the memory map information update unit 244, the data copying unit 245, the setting change unit 246, the data receiving unit 247, the flag control unit 248, and the number control unit 249 are not necessary.

[0044] The USB controller 23 , CPU 24 , memory 25 and communication circuit 26 operate by receiving power supply from the communication / power receiving / receiving male connector 21 or the communication / power receiving / receiving female connector 20 .

[0045] 4 is a block diagram showing the configuration of the expansion module 3 (monitor module). The expansion module 3 includes a communication / power-receiving female connector 30, a communication / power-receiving male connector 31, a display 32, a USB controller 33 that controls reception of signals through the communication / power-receiving female connector 30 or the communication / power-receiving male connector 31, a CPU 34, and a memory 35.

[0046] As in the case of the AD module 1, the power lines of the expansion module 3 include a positive power line 36 that connects the positive power terminal (VBUS) of the communication / power receiving female connector 30 and the positive power terminal (VBUS) of the communication / power receiving male connector 31, and a negative power line that connects the GND terminal of the communication / power receiving female connector 30 and the GND terminal of the communication / power receiving male connector 31, but the negative power line is omitted in Figure 4.

[0047] CPU 34 executes the processes described in this embodiment according to the programs stored in memory 35, and functions as a data reading unit 340 (first data reading unit), a decryption unit 341, a data display unit 342, a data transmission unit 343, a memory map information storage unit 344, a memory map information update unit 345, a data reading unit 346 (second data reading unit), a data update unit 347, a flag control unit 348, and a number control unit 349. However, in this embodiment, memory map information update unit 345, data reading unit 346, data update unit 347, flag control unit 348, and number control unit 349 are not necessary.

[0048] The display 32 , the USB controller 33 , the CPU 34 and the memory 35 operate by receiving power supply from the communication / power receiving male connector 31 or the communication / power receiving female connector 30 .

[0049] 5 is a diagram for explaining the operation of the measurement system of this embodiment. The AD conversion unit 13 of the AD module 1 converts an analog signal (e.g., a 4-20 mA current signal) received from the sensor 4 via the communication / power receiving female connector 10 into digital data. The encryption unit 140 of the AD module 1 writes the digital data after AD conversion into the memory 15, further encrypts the digital data, and writes the encrypted digital data into the memory 15.

[0050] The data reading unit 340 of the expansion module 3 reads data from the AD module 1 by transmitting a data transfer request to the AD module 1 via the USB controller 33 and the communication / power supply / reception female connector 30 . When the data transmission unit 141 of the AD module 1 receives a data transfer request from the expansion module 3 via the communication / power receiving male connector 11 and the USB controller 12, it reads data from the memory 15 and transmits the read data to the expansion module 3 via the USB controller 12 and the communication / power receiving male connector 11.

[0051] The data reading unit 340 of the expansion module 3 writes data read from the AD module 1 via the communication / power receiving female connector 30 and the USB controller 33 to the memory 35. The decryption unit 341 of the expansion module 3 decrypts the encrypted digital data stored in the memory 35. The data display unit 342 of the expansion module 3 causes the display 32 to numerically display the value indicated by the digital data decrypted by the decryption unit 341.

[0052] Next, the data reading unit 240 of the NW module 2 transmits a data transfer request to the extension module 3 via the USB controller 23 and the communication / power supply / reception female connector 20 . When the data transmission unit 343 of the expansion module 3 receives a data transfer request from the NW module 2 via the communication / power receiving male connector 31 and the USB controller 33, it reads data from the memory 35 and transmits the read data to the NW module 2 via the USB controller 33 and the communication / power receiving male connector 31.

[0053] The data reading unit 240 of the NW module 2 writes data read from the expansion module 3 via the communication / power receiving female connector 20 and the USB controller 23 to the memory 25. The communication unit 241 of the NW module 2 retrieves the encrypted digital data from the memory 25 and passes it to the communication circuit 26. The communication circuit 26 converts the encrypted digital data passed from the communication unit 241 into a wireless signal and wirelessly transmits it from the antenna 22 to the cloud server 101 on the network 100.

[0054] The NW module 2 may perform wireless communication or wired communication. In the case of wired communication, the NW module 2 may be connected to the network 100 via a communication connector 28. The communication circuit 29 converts the encrypted digital data passed from the communication unit 241 into packets and transmits them from the communication connector 28 to the cloud server 101.

[0055] On the cloud server 101 side, the encrypted digital data is decrypted, and it becomes possible to store the decrypted digital data (measurement results of the sensor 4) and provide the measurement results of the sensor 4 to the user.

[0056] Next, a characteristic operation of this embodiment will be described. In the measurement system disclosed in Patent Document 1, for example, when an extension module 3 is added between an AD module 1 and a NW module 2, in order to realize data transfer from the lower side (FIGS. 1 and 5, left side) to the upper side (FIGS. 1 and 5, right side), it is necessary to change the module addresses and communication settings.

[0057] Therefore, in this embodiment, in order to realize data transfer from the lower side to the upper side, the memory map of each module is made the same, and the procedure for reading data from the lower side to the upper side is made the same for each module. Figure 6 is a diagram showing an example of a common memory map in this embodiment. However, in Figure 6, only the data and access authority stored in memories 15, 25, and 35 are shown, and the address of the area where the data is stored is omitted.

[0058] FIG. 6 shows that the address of area RD0 where the data of sensor 4 (Sensor Data) is stored is common to the memories 15, 25, and 35 of modules 1 to 3. "RD" indicates that the data is read by the upper module. "WR" indicates that the data is written by the upper module.

[0059] More specifically, the address of the area in which the data (Sensor raw Data #1 to Sensor raw Data #8) AD converted by the AD conversion unit 13 of the AD module 1 is stored and the address of the area in which the encrypted digital data (Sensor Cryptographic Data #1 to Sensor Cryptographic Data #8) encrypted by the encryption unit 140 of the AD module 1 is stored are common in the memories 15, 25, and 35 of each of the modules 1 to 3.

[0060] The memory map information is pre-stored in the memory map information storage units 143, 243, and 344 of the modules 1 to 3. The memory map information includes the addresses of areas of the memories 15, 25, and 35, the names of data stored in these areas, the data sizes, and information on access authority (RD / WR) to the data.

[0061] The encryption unit 140 of the AD module 1 writes the digital data after AD conversion and the encrypted digital data to an area of ​​the memory 15 defined by the memory map information stored in the memory map information storage unit 143 .

[0062] The data reading unit 340 of the extension module 3 reads data from the memory 15 of the AD module 1 by making a data transfer request to the lower-level AD module 1 based on the memory map information stored in the memory map information storage unit 344, and writes the read data to an area of ​​the memory 35 defined by the memory map information stored in the memory map information storage unit 344.

[0063] The data reading unit 240 of the NW module 2 reads data from the memory 35 of the expansion module 3 by making a data transfer request to the lower-level expansion module 3 based on the memory map information stored in the memory map information storage unit 243, and writes the read data to an area of ​​the memory 25 defined by the memory map information stored in the memory map information storage unit 243.

[0064] Thus, in this embodiment, by making the memory maps of each module identical for the common sensor data that is transferred sequentially from the lower side to the higher side, even if the configuration of the measurement system is changed by adding or removing a module, there is no need to change the address settings, thereby reducing the occurrence of malfunctions.

[0065] [Second Example] Next, a second embodiment of the present invention will be described. In the first embodiment, the transfer of sensor data common to each module has been described. On the other hand, if it is necessary to transfer data specific to each module other than the common data, this can be achieved by providing a dedicated area for each module in a memory map common to each module.

[0066] In this embodiment, the configuration of the measurement system is similar to that of the first embodiment, and therefore will be described using the symbols in Figures 1 to 5. However, in this embodiment, the memory map information update unit 144, data read unit 145, data update unit 146, flag control unit 147, and number control unit 148 of the AD module 1 are unnecessary, the memory map information update unit 244, data copy unit 245, setting change unit 246, data reception unit 247, flag control unit 248, and number control unit 249 of the NW module 2 are unnecessary, and the memory map information update unit 345, data read unit 346, data update unit 347, flag control unit 348, and number control unit 349 of the extension module 3 are unnecessary.

[0067] Figures 7 and 8 are diagrams showing an example of a common memory map in this embodiment. Of the memory map in Figure 7, Figure 8 shows only details of area RD2 where data specific to the AD module 1 is stored and area RD3 where data specific to the extension module 3 is stored. As in Figure 6, Figures 7 and 8 show only the data and access authority stored in memories 15, 25, and 35, and omit the description of the addresses of the areas where the data is stored.

[0068] The area RD0 in which the data of the sensor 4 (Sensor Data) is stored is as described with reference to FIG. Area RD1 stores data specific to the NW module 2. Specifically, area RD1 stores data such as an identification code of the NW module 2, an update counter indicating the number of times the data in area RD1 has been updated, a checksum, an ID of the NW module 2 in the measurement system, an address of the cloud server 101, an SSID (Service Set Identifier) ​​of a wireless router for connecting to the network 100, a password of the wireless router, the type of quantity measured by the sensor 4 (temperature, humidity, pressure, acceleration, seismic intensity, precipitation, oxidation-reduction amount, etc.), the unit of the quantity measured by the sensor 4, correction parameters (zero span, ratio, bias, temperature characteristics, etc.), the current consumption of the NW module 2, and the replacement cycle of the NW module 2. Note that since there is no module that reads out the data of the NW module 2, the access authority of area RD1 is indefinite ("-").

[0069] Area RD2 stores data specific to the AD module 1. Specifically, area RD2 stores data such as an identification code of the AD module 1, an update counter indicating the number of times the data in area RD2 has been updated, a checksum, the ID of the AD module 1 in the measurement system, the AD resolution, the AD conversion cycle, correction parameters (zero span, ratio, bias, temperature characteristics, etc.), the current consumption of the AD module 1, and the replacement cycle of the AD module 1.

[0070] Area RD3 stores data specific to the extension module 3 (extension #1). Specifically, area RD3 stores data such as an identification code of the extension module 3, an update counter indicating the number of times the data in area RD3 has been updated, a checksum, an ID of the extension module 3 in the measurement system, a current consumption of the extension module 3, and a replacement cycle of the extension module 3. Similarly, areas RD4 to RD9 store data of the six extension modules other than extension module 3 (extension #2 to extension #7).

[0071] Area WR1 stores data written from cloud server 101 to NW module 2. Area WR2 stores data written from an upper module to AD module 1. Area WR3 stores data written from an upper module to extension module 3. Areas WR4 to WR9 store data written to six extension modules (Extension #2 to Extension #7) other than extension module 3. Areas RD10 to RD16 store data (Storage Data #1 to Storage Data #7) accumulated by storage modules equipped with the function of storing data.

[0072] As in the first embodiment, memory map information common to the memories 15, 25, and 35 of the modules 1-3 is stored in advance in the memory map information storage units 143, 243, and 344 of the modules 1-3.

[0073] FIG. 9 is a diagram for explaining data transfer from the lower side (left side in FIG. 9) to the upper side (right side in FIG. 9) in this embodiment.

[0074] The data reading unit 340 of the extension module 3 reads data from the memory 15 of the AD module 1 by making a data transfer request to the lower-level AD module 1 based on the memory map information stored in the memory map information storage unit 344, and writes the read data to an area of ​​the memory 35 defined by the memory map information stored in the memory map information storage unit 344.

[0075] In this manner, the data of the sensor 4 (Sensor Data) is stored in the area RD0 of the memory 35, and the data specific to the AD module 1 (Mod information_RD_AD) is stored in the area RD2 of the memory 35. The data reader 340 prohibits the area RD3 of the memory 35 from being overwritten during data transfer. Therefore, the data specific to the extension module 3 (Mod information_RD_extension #1) is not overwritten.

[0076] The data reading unit 240 of the NW module 2 reads data from the memory 35 of the expansion module 3 by making a data transfer request to the lower-level expansion module 3 based on the memory map information stored in the memory map information storage unit 243, and writes the read data to an area of ​​the memory 25 defined by the memory map information stored in the memory map information storage unit 243.

[0077] In this way, data from sensor 4 (Sensor Data) is stored in area RD0 of memory 25, data specific to AD module 1 (Mod information_RD_AD) is stored in area RD2 of memory 25, and data specific to extension module 3 (Mod information_RD_Extension #1) is stored in area RD3 of memory 25. The data reader 240 prohibits the area RD1 of the memory 25 from being overwritten during data transfer. Therefore, data specific to the NW module 2 (Mod information_RD_NW) is not overwritten.

[0078] Thus, in this embodiment, not only the data of the sensor 4 but also data specific to each module can be transferred. The data stored in the memory 25 of the NW module 2 is transmitted from the NW module 2 to the cloud server 101, similarly to the first embodiment.

[0079] The cloud server 101 can perform settings related to the measurement function based on, for example, the information stored in area RD1 and the information stored in area RD2 of the memory 25 of the NW module 2. The measurement function includes a function of converting a value indicated by the digital data measured by the sensor 4 and AD converted by the AD module 1 into an amount to be measured using a conversion formula, a function of correcting the digital data based on a correction parameter, and the like. The cloud server 101 can also estimate the replacement time of each of the modules 1 to 3 based on the information on the replacement period stored in areas RD1 to RD3 of the memory 25 of the NW module 2.

[0080] Thus, in this embodiment, even if the configuration of the measurement system is changed by adding or removing a module, it is not necessary to change the address settings, so the occurrence of problems can be reduced. The transfer of common data (sensor data) from the lower side to the upper side is performed, for example, at regular intervals, but the unique data of each module only needs to be transferred at least once.

[0081] [Third Example] Next, a third embodiment of the present invention will be described. In the second embodiment, when a new additional module is inserted, the module information stored in the memory is overwritten. If the overwritten module information is information about a module essential to the system (such as an AD module), it is determined from the module identification code in the memory map information that the essential module is absent, resulting in a system error.

[0082] Therefore, in this embodiment, as in the first and second embodiments, the memory maps of each module are made identical for common sensor data, but the memory maps of each module are not made identical for data specific to a module, and the memory map information is updated as appropriate. In this embodiment, the configuration of the measurement system is similar to that in the first embodiment, so the description will be given using the reference numerals in FIGS.

[0083] Figures 10(A) to 10(C) are diagrams explaining data transfer from the lower side (left side of Figure 10) to the upper side (right side of Figure 10) in this embodiment, Figure 11 is a flowchart explaining the operation of the upper side module in this embodiment, and Figure 12 is a flowchart explaining the operation of the lower side module.

[0084] In this embodiment, as described above, the address of area RD0 in which common data (sensor data) is stored is common in memories 15, 25, and 35 of modules 1 to 3, but the memory map information of modules 1 to 3 is defined so that the address of area FL in which read flags are stored is also common in memories 15, 25, and 35 of modules 1 to 3.

[0085] When power supply from the other modules is started and the power is turned ON, each of the modules 1 to 3 performs an initial setting. As the initial setting, the flag control units 147, 248, and 348 of the modules 1 to 3 reset the read flags stored in the areas FL of the memories 15, 25, and 35, which are defined by the memory map information stored in the memory map information storage units 143, 243, and 344, to 0 (defined numerical value) (step S100 in FIG. 11, step S200 in FIG. 12).

[0086] Fig. 10(A) shows a state in which the read flags of modules 1 to 3 are reset to 0 by the initial setting. Also, as is clear from Fig. 10(A), areas RD1, RD2, and RD3 are not areas dedicated to modules 1 to 3, and data unique to each of modules 1 to 3 is stored in area RD1.

[0087] The data reading unit 340 of the extension module 3 reads the read flag from the AD module 1 by making a request for transfer of the read flag to the lower AD module 1 based on the memory map information stored in the memory map information storage unit 344 (FIG. 11, step S101).

[0088] In response to a read flag transfer request from the extension module 3, the data transmission unit 141 of the AD module 1 reads the read flag from the memory 15 and transmits it to the extension module 3 (steps S201 and S202 in FIG. 12).

[0089] When the read flag read from the AD module 1 is 0 (YES in step S102 in FIG. 11), the data reading unit 340 of the extension module 3 temporarily stores the unique data (Mod information_RD_extension #1) of the extension module 3 in a predetermined save area on the memory 35 based on the memory map information stored in the memory map information storage unit 344 before making a data transfer request to the lower AD module 1 (step S103 in FIG. 11). This data save is to prevent the unique data (Mod information_RD_extension #1) from being overwritten by the next data read.

[0090] The data reading unit 340 makes a data transfer request to the lower-level AD module 1 based on the memory map information stored in the memory map information storage unit 344, and reads data from all areas RD1, RD2, RD3, ... that are assigned as unique data areas of each module from the AD module 1 (FIG. 11, step S104).

[0091] In response to a data transfer request from the expansion module 3, the data transmission unit 141 of the AD module 1 reads out from the memory 15 the data stored in all areas assigned as unique data areas of each module and transmits it to the expansion module 3 (steps S203 and S204 in FIG. 12).

[0092] The data reading unit 340 of the extension module 3 writes the data read from the AD module 1 to areas RD1, RD2, RD3, ... of the memory 35 that are assigned as unique data areas of each module based on the memory map information stored in the memory map information storage unit 344 (Figure 11, step S105).

[0093] Then, the data reading unit 340 stores the extension module 3's unique data (Mod information_RD_extension #1) that was saved in the save area in an area different from the areas in which the unique data of the other modules is stored (FIG. 11, step S106). Since the data stored in the memory 35 is added with information such as the data name and access authority (RD / WR), it is possible to recognize the area in which the AD module 1's unique data (Mod information_RD_AD) is stored. Therefore, the extension module 3's unique data (Mod information_RD_extension #1) can be stored in an area different from the area in which the AD module 1's unique data (Mod information_RD_AD) is stored.

[0094] Next, the memory map information update unit 345 of the extension module 3 updates the memory map information of areas RD1, RD2, RD3, ... of the memory 35 that are assigned as unique data areas of each module, among the memory map information stored in the memory map information storage unit 344, based on the data stored in the memory 35 in steps S105 and S106 (FIG. 11, step S107). As described above, the data stored in the memory 35 is added with information such as the name of the data and access authority (RD / WR), so it is possible to update the memory map information based on this information and the address of the area where the data is stored.

[0095] The flag control unit 348 of the extension module 3 resets the read flag of the memory 35 to 0 because the data in the area assigned as the unique data area of ​​each module has been updated (step S108 in FIG. 11).

[0096] On the other hand, the flag control unit 147 of the AD module 1 sets the read flag of the memory 15 to 1 after data transmission in response to a data transfer request from the extension module 3 is completed and data reading by the extension module 3 is completed (FIG. 12, step S205). FIG. 10B shows a state in which the extension module 3 reads and updates data from the AD module 1, and the AD module 1 sets the read flag to 1.

[0097] The data reader 240 of the NW module 2 reads the read flag from the extension module 3 by making a transfer request of the read flag to the lower extension module 3 based on the memory map information stored in the memory map information storage unit 243 (FIG. 11, step S101).

[0098] The data transmission unit 343 of the extension module 3 reads the read flag from the memory 35 in response to a read flag transfer request from the NW module 2, and transmits the read flag to the NW module 2 (steps S201 and S202 in FIG. 12).

[0099] When the read flag read from the extension module 3 is 0 (YES in step S102 in FIG. 11), the data reading unit 240 of the NW module 2 temporarily stores the unique data of the NW module 2 (Mod information_RD_NW) in a predetermined save area on the memory 25 based on the memory map information stored in the memory map information storage unit 243 before making a data transfer request to the lower-level extension module 3 (step S103 in FIG. 11).

[0100] The data reading unit 240 makes a data transfer request to the lower-level expansion module 3 based on the memory map information stored in the memory map information storage unit 243, and reads data from all areas RD1, RD2, RD3, ..., assigned as unique data areas of each module, from the expansion module 3 (Figure 11, step S104).

[0101] In response to a data transfer request from the NW module 2, the data transmission unit 343 of the extension module 3 reads out from the memory 35 the data stored in all areas assigned as unique data areas of each module and transmits the data to the NW module 2 (steps S203 and S204 in FIG. 12).

[0102] The data reading unit 240 of the NW module 2 writes the data read from the extension module 3 to areas RD1, RD2, RD3, ... of the memory 25 that are assigned as unique data areas of each module based on the memory map information stored in the memory map information storage unit 243 (FIG. 11, step S105).

[0103] Then, the data reading unit 240 stores the unique data of the NW module 2 (Mod information_RD_NW) that was saved in the save area in an area different from the areas in which the unique data of the other modules is stored (step S106 in FIG. 11). Since the data stored in the memory 25 is added with information such as the name of the data and the access authority (RD / WR), it is possible to recognize the areas in which the unique data of the AD module 1 (Mod information_RD_AD) and the unique data of the extension module 3 (Mod information_RD_extension #1) are stored. Therefore, it is sufficient to store the unique data of the NW module 2 (Mod information_RD_NW) in an area different from the areas in which the unique data of the AD module 1 (Mod information_RD_AD) and the unique data of the extension module 3 (Mod information_RD_extension #1) are stored.

[0104] Next, the memory map information update unit 244 of the NW module 2 updates the memory map information of areas RD1, RD2, RD3, ... of the memory 25 that are assigned as unique data areas of each module, among the memory map information stored in the memory map information storage unit 243, based on the data stored in the memory 25 in steps S105 and S106 (FIG. 11, step S107).

[0105] The flag control unit 248 of the NW module 2 resets the read flag of the memory 25 to 0 because the data in the area assigned as the unique data area of ​​each module has been updated (Step S108 in FIG. 11).

[0106] On the other hand, the flag control unit 348 of the extension module 3 sets the read flag of the memory 35 to 1 after the data transmission in response to the data transfer request from the NW module 2 is completed and the data reading by the NW module 2 is completed (FIG. 12, step S205). FIG. 10C illustrates a state in which the NW module 2 reads and updates data from the extension module 3, and the extension module 3 sets the read flag to 1.

[0107] 13(A) to 13(D) are diagrams for explaining another example of data transfer in this embodiment. Fig. 13(B) shows a state in which the NW module 2 reads data from the extension module 3 before the extension module 3 reads data from the AD module 1. As a result of the NW module 2 reading the data from the extension module 3, the extension module 3 sets the read flag to 1.

[0108] FIG. 13C shows a state in which the extension module 3 has read data from the AD module 1, and as a result the extension module 3 has reset the read flag to 0, and the AD module 1 has set the read flag to 1.

[0109] 13D shows a state in which the NW module 2 re-reads the data of the extension module 3 as a result of the extension module 3 resetting the read flag to 0. As a result of the NW module 2 reading the data from the extension module 3, the extension module 3 sets the read flag to 1.

[0110] Thus, in this embodiment, even if the configuration of the measurement system is changed by adding or removing a module, the memory map information regarding the unique data of each module can be automatically updated, thereby reducing the occurrence of malfunctions.

[0111] Note that FIG. 11 describes only the transfer of unique data, and as described in the first and second embodiments, the transfer of common data (sensor data) is repeated, for example, at regular intervals.

[0112] [Fourth Example] Next, a fourth embodiment of the present invention will be described. In the third embodiment, if there is a module whose read flag is not reset due to, for example, a momentary power interruption, there is a possibility that memory map information cannot be created correctly.

[0113] Therefore, in this embodiment, the unique data is transferred without using a read flag as in the third embodiment. In this embodiment, the configuration of the measurement system is similar to that in the first embodiment, so the description will be given using the reference numerals in FIGS.

[0114] Figures 14(A) to 14(C) are diagrams explaining data transfer from the lower side (left side of Figure 14) to the upper side (right side of Figure 14) in this embodiment, Figure 15 is a flowchart explaining the operation of the upper side module in this embodiment, and Figure 16 is a flowchart explaining the operation of the lower side module.

[0115] In this embodiment, as described above, the address of area RD0 in which common data (sensor data) is stored is common to memories 15, 25, and 35 of modules 1 to 3, but the memory map information of modules 1 to 3 is defined so that the address of area ML in which memory numbers are stored is also common to memories 15, 25, and 35 of modules 1 to 3.

[0116] When power supply from the other modules is started and the power is turned ON, each of the modules 1 to 3 performs an initial setting. As the initial setting, the number control units 148, 249, and 349 of the modules 1 to 3 reset the memory No. stored in the area ML of the memories 15, 25, and 35 defined by the memory map information stored in the memory map information storage units 143, 243, and 344, respectively, to 1 (initial value) (step S300 in FIG. 15, step S400 in FIG. 16).

[0117] Fig. 14(A) shows a state in which the memory numbers of modules 1 to 3 are reset to 1 by the initial setting. Also, as is clear from Fig. 14(A), areas RD1, RD2, and RD3 are not areas dedicated to modules 1 to 3, and data specific to each of modules 1 to 3 is stored in area RD1.

[0118] The data reading unit 340 of the extension module 3 reads the memory number from the AD module 1 by making a transfer request of the memory number to the lower AD module 1 based on the memory map information stored in the memory map information storage unit 344 (FIG. 15, step S301).

[0119] In response to a transfer request for the memory number from the extension module 3, the data transmission unit 141 of the AD module 1 reads the memory number from the memory 15 and transmits it to the extension module 3 (steps S401 and S402 in FIG. 16).

[0120] If the memory number read from the AD module 1 is the same as or greater than the memory number stored in area ML of the memory 35 of the device itself (YES in step S302 of FIG. 15), the data reading unit 340 of the expansion module 3 temporarily stores the unique data of the expansion module 3 (Mod information_RD_extension #1) in a specified save area on the memory 35 based on the memory map information stored in the memory map information storage unit 344 before making a data transfer request to the lower AD module 1 (step S303 of FIG. 15).

[0121] The data reading unit 340 makes a data transfer request to the lower-level AD module 1 based on the memory map information stored in the memory map information storage unit 344, and reads data from all areas RD1, RD2, RD3, ... that are assigned as unique data areas of each module from the AD module 1 (Figure 15, step S304).

[0122] In response to a data transfer request from the expansion module 3, the data transmission unit 141 of the AD module 1 reads out from the memory 15 the data stored in all areas assigned as unique data areas of each module and transmits it to the expansion module 3 (steps S403 and S404 in FIG. 16).

[0123] The data reading unit 340 of the extension module 3 writes the data read from the AD module 1 to areas RD1, RD2, RD3, ... of the memory 35 that are assigned as unique data areas of each module based on the memory map information stored in the memory map information storage unit 344 (Figure 15, step S305).

[0124] Then, the data reading unit 340 stores the unique data of the extension module 3 (Mod information_RD_extension #1) that was saved in the save area in an area different from the areas in which the unique data of the other modules is stored (FIG. 15, step S306).

[0125] Next, the memory map information update unit 345 of the extension module 3 updates the memory map information of areas RD1, RD2, RD3, ... of the memory 35 that are assigned as unique data areas of each module from the memory map information stored in the memory map information storage unit 344 based on the data stored in the memory 35 by steps S305 and S306 (Figure 15 step S307).

[0126] As a result of updating the data in the area assigned as the unique data area of ​​each module, the number control unit 349 of the expansion module 3 updates the memory number stored in area ML of the memory 35 to a value obtained by adding 1 to the memory number read from the AD module 1 (Figure 15, step S308).

[0127] FIG. 14B shows a state in which the extension module 3 reads and updates data from the AD module 1, and updates the memory number to 2.

[0128] The data reading unit 240 of the NW module 2 reads the memory number from the extension module 3 by making a transfer request of the memory number to the lower-level extension module 3 based on the memory map information stored in the memory map information storage unit 243 (FIG. 15, step S301).

[0129] In response to a transfer request for the memory number from the NW module 2, the data transmission unit 343 of the extension module 3 reads the memory number from the memory 35 and transmits the memory number to the NW module 2 (steps S401 and S402 in FIG. 16).

[0130] When the memory number read from the extension module 3 is equal to or greater than the memory number stored in area ML of the memory 25 of the own device (YES in step S302 in FIG. 15), the data reading unit 240 of the NW module 2 temporarily stores the unique data of the NW module 2 (Mod information_RD_NW) in a predetermined save area on the memory 25 based on the memory map information stored in the memory map information storage unit 243 before making a data transfer request to the lower-level extension module 3 (step S303 in FIG. 15).

[0131] The data reading unit 240 makes a data transfer request to the lower-level expansion module 3 based on the memory map information stored in the memory map information storage unit 243, and reads data from all areas RD1, RD2, RD3, ..., assigned as unique data areas of each module, from the expansion module 3 (Figure 15, step S304).

[0132] In response to a data transfer request from the NW module 2, the data transmission unit 343 of the extension module 3 reads out from the memory 35 the data stored in all areas assigned as unique data areas of each module and transmits the data to the NW module 2 (steps S403 and S404 in FIG. 16).

[0133] The data reading unit 240 of the NW module 2 writes the data read from the extension module 3 to areas RD1, RD2, RD3, ... of the memory 25 that are assigned as unique data areas of each module based on the memory map information stored in the memory map information storage unit 243 (FIG. 15, step S305).

[0134] Then, the data reader 240 stores the unique data of the NW module 2 (Mod information_RD_NW) that has been saved in the save area in an area different from the areas in which the unique data of the other modules is stored (Step S306 in FIG. 15).

[0135] Next, the memory map information update unit 244 of the NW module 2 updates the memory map information of areas RD1, RD2, RD3, ... of the memory 25 that are assigned as unique data areas of each module, among the memory map information stored in the memory map information storage unit 243, based on the data stored in the memory 25 in steps S305 and S306 (FIG. 15, step S307).

[0136] As a result of updating the data in the area assigned as the unique data area of ​​each module, the number control unit 249 of the NW module 2 updates the memory number stored in area ML of the memory 25 to a value obtained by adding 1 to the memory number read from the extension module 3 (FIG. 15, step S308).

[0137] FIG. 14C shows a state in which the NW module 2 reads out data from the extension module 3 and updates the memory number to 3.

[0138] 17(A) to 17(D) are diagrams for explaining another example of data transfer in this embodiment. Fig. 17(B) shows a state in which the NW module 2 reads data from the extension module 3 before the extension module 3 reads data from the AD module 1. By reading the data from the extension module 3, the NW module 2 updates the memory No. stored in area ML of the memory 25 to 2.

[0139] FIG. 17C shows a state in which the extension module 3 has read data from the AD module 1, and thereby updated the memory number stored in area ML of the memory 35 to 2.

[0140] 17(D) shows a state in which the NW module 2 re-reads the data of the extension module 3 as a result of the extension module 3 updating the memory number to 2. By reading the data from the extension module 3, the NW module 2 updates the memory number stored in area ML of the memory 25 to 3.

[0141] Thus, in this embodiment, even if the configuration of the measurement system is changed by adding or removing a module, the memory map information regarding the unique data of each module can be automatically updated, thereby reducing the occurrence of malfunctions.

[0142] Note that only the transfer of unique data is described in FIG. 15, and as described in the first and second embodiments, the transfer of common data (sensor data) is repeated, for example, at regular intervals.

[0143] [Fifth Example] Next, a fifth embodiment of the present invention will be described. In the third and fourth embodiments, if the read flag or memory No. data has an abnormal value, there is a possibility that memory map information cannot be created correctly.

[0144] Therefore, in this embodiment, the unique data is transferred without using a read flag as in the third embodiment or a memory number as in the fourth embodiment. In this embodiment, the configuration of the measurement system is similar to that in the first embodiment, so the description will be given using the reference numerals in FIGS.

[0145] Figures 18(A), 18(B), 19(A), 19(B), 20(A), and 20(B) are diagrams explaining data transfer from the lower side to the upper side in this embodiment, Figures 21(A) and 21(B) are flow charts explaining the operation of each module except the top module, and Figures 22(A) and 22(B) are flow charts explaining the operation of the top module. Figures 21(A) and 22(A) show the operation of a module that reads unique data from a lower module, and Figures 21(B) and 22(B) show the operation in response to a data transfer request from a module on the upper or lower side.

[0146] First, the data reading units 240, 340 of each module 2, 3 make a data transfer request to the lower module based on the memory map information stored in the memory map information storage units 243, 344, respectively, and reads out from the lower module the data stored in all areas RD1, RD2, RD3, ... assigned as unique data areas of each module (step S500 in FIG. 21A, step S600 in FIG. 22A).

[0147] In response to a data transfer request from a higher-level module, the data transmission units 141 and 343 of modules 1 and 3 read out data stored in all areas assigned as unique data areas of each module from memories 15 and 35 and transmit the data to the higher-level module (steps S511 and S512 in FIG. 21B).

[0148] The data reading units 240, 340 of each module 2, 3 write the data read from the lower module to areas RD1, RD2, RD3, ... of the memory 25, 35 assigned as unique data areas of each module based on the memory map information stored in the memory map information storage units 243, 344, respectively (step S501 in FIG. 21A, step S601 in FIG. 22A).

[0149] At this time, the data reading unit 340 of the extension module 3 prohibits its own unique data (Mod information_RD_extension #1) from being overwritten. Similarly, the data reading unit 240 of the NW module 2 prohibits its own unique data (Mod information_RD_NW) from being overwritten. The data read from the lower module is stored in an area different from the area in which its own unique data is stored.

[0150] FIG. 18A shows a state in which the extension module 3 reads data from the AD module 1 and at the same time the NW module 2 reads data from the extension module 3 through the processing of steps S500, S501, S511, S512, S600, and S601 described above.

[0151] Next, the NW module 2 becomes the top module because no module is connected to the upper communication / power receiving male connector 21. Based on the memory map information stored in the memory map information storage unit 243, the data copying unit 245 of the NW module 2 copies data stored in areas RD1, RD2, RD3,... of the memory 25, which are assigned as unique data areas (first areas) of each module, to areas QD1, QD2, QD3,... of the memory 25, which are assigned as areas (second areas) from which lower modules perform reading (step S602 in FIG. 22A). In the process of step S602, only valid data is copied, and therefore invalid data is not copied. Areas QD1, QD2, QD3,... correspond to areas RD1, RD2, RD3,..., respectively.

[0152] The data reading units 145, 346 of modules 1, 3 make a data transfer request to the upper module based on the memory map information stored in the memory map information storage units 143, 344, respectively, and read the data stored in areas QD1, QD2, QD3, ..., which are assigned as areas for the lower module to read, from the upper module (step S502 in Figure 21(A)).

[0153] In response to a data transfer request from a downstream module, the data transmission units 242, 343 of modules 2, 3 respectively read out data stored in all areas QD1, QD2, QD3, ... that are assigned as areas for the downstream module to read from the memories 25, 35 and transmit the data to the downstream module (steps S513, S514 in FIG. 21B, steps S611, S612 in FIG. 22B).

[0154] The data reading units 145, 346 of the modules 1, 3 write the data read from the upper module to areas QD1, QD2, QD3, ... of the memories 15, 35 that are assigned as areas for the lower module to read, based on the memory map information stored in the memory map information storage units 143, 344, respectively (FIG. 21A, step S503). At this time, the data written to the memories 15, 35 may be overwritten and saved to update with the latest data.

[0155] FIG. 18(B) shows a state in which, through the processing of the above steps S602, S502, S513, S514, S611, S612, and S503, the NW module 2 copies the data in areas RD1 and RD2 of memory 25 to areas QD1 and QD2, the expansion module 3 reads data from the NW module 2 and writes the data to areas QD1 and QD2 of memory 35, and the AD module 1 reads data from the expansion module 3 and writes the data to areas QD1 and QD2 of memory 15.

[0156] Next, the data update units 146, 347 of the modules 1, 3 temporarily store their own unique data in a predetermined save area on the memory 15, 35 based on the memory map information stored in the memory map information storage units 143, 344, respectively (FIG. 21A, step S504).

[0157] Based on the memory map information stored in the memory map information storage units 143, 344, the data update units 146, 347 of the modules 1, 3 copy the data stored in the areas QD1, QD2, QD3,... of the memories 15, 35 that are assigned as areas for the lower modules to read from, to the corresponding areas RD1, RD2, RD3,... of the memories 15, 35 (step S505 in FIG. 21A). In the process of step S505, only valid data is copied, so that the data stored in the areas RD1, RD2, RD3,... is not overwritten with invalid data.

[0158] Then, the data update units 146, 347 of the modules 1, 3 compare their own unique data saved in the save areas of the memories 15, 35 with the data copied to the areas RD1, RD2, RD3, . . . of the memories 15, 35 (step S506 in FIG. 21A).

[0159] If there is no data whose name matches its own unique data in areas RD1, RD2, RD3, ... (NO in step S506), data update units 146, 347 store their own unique data in an area different from the areas storing the unique data of other modules (step S507 in FIG. 21(A)). As explained in the third embodiment, the data stored in memories 15, 35 is added with information such as the name of the data and access authority (RD / WR), so it is possible to determine whether the data matches or does not match, and to recognize the area in which the unique data of other modules is stored.

[0160] If data having a name matching the unique data of the device itself is already stored in areas RD1, RD2, RD3, . . . , there is no need to store the unique data of the device itself again.

[0161] FIG. 19A shows a state in which the AD module 1 has updated the data in areas RD1, RD2, and RD3 of the memory 15, and the extension module 3 has updated the data in areas RD1, RD2, and RD3 of the memory 35, through the processing in steps S504 to S507 described above.

[0162] Next, the memory map information update units 144, 244, 345 of modules 1 to 3 update the memory map information of areas RD1, RD2, RD3, ... of memories 15, 25, 35 assigned as unique data areas of each module from the memory map information stored in the memory map information storage units 143, 243, 344 based on the data stored in memories 15, 25, 35 by steps S504 to S507, S601 (step S508 in Figure 21(A), step S603 in Figure 22(A)).

[0163] If each of the modules 1 to 3 has not transferred its unique data a predetermined number of times (e.g., N times) (NO in step S509 in FIG. 21(A) or NO in step S604 in FIG. 22(A)), the process returns to steps S500 and S600. In this manner, the processes in FIGS. 21 and 22 are repeated. The predetermined number of times N may be any number equal to or greater than the maximum number of connections of modules determined in advance.

[0164] FIG. 19B shows a state in which the extension module 3 reads data from the AD module 1 and at the same time the NW module 2 reads data from the extension module 3 through the processing of steps S500, S501, S511, S512, S600, and S601.

[0165] FIG. 20(A) shows a state in which, through the processing of steps S602, S502, S513, S514, S611, S612, and S503, the NW module 2 copies the data in areas RD1, RD2, and RD3 of memory 25 to areas QD1, QD2, and QD3, the expansion module 3 reads data from the NW module 2 and writes the data to areas QD1, QD2, and QD3 of memory 35, and the AD module 1 reads data from the expansion module 3 and writes the data to areas QD1, QD2, and QD3 of memory 15.

[0166] FIG. 20A shows a state in which the AD module 1 updates the data in areas RD1, RD2, and RD3 of the memory 15, and the extension module 3 updates the data in areas RD1, RD2, and RD3 of the memory 35, through the processing in steps S504 to S507.

[0167] Thus, in this embodiment, even if the configuration of the measurement system is changed by adding or removing a module, the memory map information regarding the unique data of each module can be automatically updated, thereby reducing the occurrence of malfunctions.

[0168] 21 and 22, only the transfer of unique data is described, and as described in the first and second embodiments, the transfer of common data (sensor data) is repeated, for example, at regular intervals.

[0169] [Sixth Example] Next, a sixth embodiment of the present invention will be described. In this embodiment, as an application of the processing in the fifth embodiment, the setting of the lower module is changed by changing the data of the module that the top module wishes to change among the data stored in the area read by the lower module.

[0170] In this embodiment, the configuration of the measurement system is similar to that in the first embodiment, so the description will be given using the reference numerals in FIGS. Figures 23(A) and 23(B) are flow charts explaining the operation of each module except the top module, and Figures 24(A) and 24(B) are flow charts explaining the operation of the top module. Figures 23(A) and 24(A) show the operation of a module that reads unique data from a lower module, and Figures 23(B) and 24(B) show the operation in response to a data transfer request from a higher-level or lower-level module.

[0171] The processing of the NW module 2 in steps S600 to S604, S611, and S612 in FIG. 24(A) and FIG. 24(B) is as described in the fifth embodiment. When a setting change of the AD module 1 is required (YES in step S605 in FIG. 24A), the setting change unit 246 of the NW module 2 rewrites the data of the AD module 1 that is the target of the setting change among the data stored in areas QD1, QD2, QD3, ... of the memory 25 that are read by the lower-level module (step S606 in FIG. 24A).

[0172] Similarly, when a setting change of the expansion module 3 is required (YES in step S605), the setting change unit 246 rewrites the data of the expansion module 3 that is the target of the setting change among the data stored in areas QD1, QD2, QD3, etc. of the memory 25 (step S606).

[0173] A setting change is required, for example, when the data receiving unit 247 of the NW module 2 receives setting data from the cloud server 101. The data receiving unit 247 receives the setting data from the cloud server 101 via the antenna 22 and the communication circuit 26. Alternatively, the data receiving unit 247 receives the setting data from the cloud server 101 via the communication connector 28 and the communication circuit 29. The setting change unit 246 rewrites the data of the modules 1 and 3 that are the targets of the setting change with the setting data received by the data receiving unit 247.

[0174] The processes of modules 1 and 3 in steps S500 to S505, S508, S509, and S511 to S514 in FIGS. 23(A) and 23(B) are as described in the fifth embodiment. The data update units 146, 347 of the modules 1, 3 compare their own unique data saved in the save areas of the memories 15, 35 with the data copied to the areas RD1, RD2, RD3, . . . of the memories 15, 35 (step S506 in FIG. 23A).

[0175] If there is no data in areas RD1, RD2, RD3, etc. whose name matches that of its own unique data, the data update units 146, 347 store their own unique data in an area different from the areas storing the unique data of other modules (step S507 in FIG. 23A). If there is data in areas RD1, RD2, RD3, etc. whose name matches that of its own unique data, or if there is data whose name matches that of its own unique data but whose value does not match, the data update units 146, 347 determine that there is unique data whose name matches (YES in step S506 in FIG. 23) and do not update the data with their own unique data saved in the save area (step S507).

[0176] In this way, in this embodiment, the inherent data of the lower modules can be rewritten, and the settings of the lower modules can be changed from the top module.

[0177] Although the first to sixth embodiments use one extension module, a plurality of extension modules may be connected. In addition, in the first to sixth embodiments, a USB controller is used for communication between the communication / power supply / reception connector of each module and the CPU, but this is not limited to this, and communication between the communication / power supply / reception connector and the CPU may be achieved without going through a USB controller or by using means other than a USB controller. [Industrial Applicability]

[0178] The present invention can be applied to a module system such as a measurement system that collects data from a sensor module. [Explanation of symbols]

[0179] 1...AD module, 2...network module, 3...expansion module, 4...sensor, 5...power supply, 10,20,30,50...communication / power supply female connector, 11,21,31,40...communication / power supply male connector, 12,23,33...USB controller, 13...AD conversion section, 14,24,34...CPU, 15,25,35...memory, 16,27,36...power supply line, 22...antenna, 26,29...communication circuit, 28...communication connector, 32...display, 140...encryption section , 141, 242, 343...data transmitting unit, 142, 145, 240, 340, 346...data reading unit, 143, 243, 344...memory map information storage unit, 144, 244, 345...memory map information updating unit, 146, 347...data updating unit, 147, 248, 348...flag control unit, 148, 249, 349...number control unit, 241...communication unit, 245...data copying unit, 246...setting change unit, 247...data receiving unit, 341...decoding unit, 342...data display unit.

Claims

1. In a module system including a plurality of modules connected in series, Each module is a memory configured to store data; a memory map information storage unit configured to store memory map information; a data reading unit configured to read data from other modules based on the memory map information and store the data in the memory; a flag control unit configured to control a read flag stored in the memory; The memory map information is common to each module with respect to a dedicated area of ​​the memory for storing the read flag of each module, the data reading unit reads data from a lower-level module when the read flag of the lower-level module is a specified value; The flag control unit resets the read flag of the own device to the specified numerical value when the data stored in the memory of the own device is in an initial state and when the data stored in the memory of the own device has been updated by reading by the data reading unit, and sets the read flag of the own device to a numerical value other than the specified numerical value when data stored in the memory of the own device is read from a higher-level module.

2. In a module system including a plurality of modules connected in series, Each module is a memory configured to store data; a memory map information storage unit configured to store memory map information; a data reading unit configured to read data from other modules based on the memory map information and store the data in the memory; and a number control unit configured to control the memory number stored in the memory, The memory map information is information about a dedicated area of ​​the memory that stores the memory number of each module, and the information is common to each module; the data reading unit reads data from the lower module when the memory number of the lower module is equal to or greater than the memory number stored in the memory of the own device; said number control unit resets said memory number of its own device to an initial value common to each module in an initial state, and updates said memory number of its own device to a value larger than said memory number of the lower module when data is read from the lower module.

3. 3. The module system according to claim 1, a data read unit that reads the data from the data read unit and stores it in the memory of the module; a memory map information update unit that updates the memory map information of an area of ​​the memory that is assigned as a unique data area of ​​the module based on the data read by the data read unit and stored in the memory of the module;

4. 4. The module system according to claim 1, A module system, wherein the data reading unit reads data from areas assigned as unique data areas of all modules from lower level modules based on the memory map information.

5. In a module system including a plurality of modules connected in series, Each module is a memory configured to store data; a memory map information storage unit configured to store memory map information; a first data reading unit configured to read data from a lower module based on the memory map information and store the data in a first area of ​​the memory; a data copying unit configured to copy data stored in the first area after being read by the first data reading unit to a second area of ​​the memory when the device itself is a top-level module; a second data reading unit configured to read data from the second area of ​​a higher-level module after the first data reading unit reads data when the device is other than the highest-level module, and to store the data in the second area of ​​the memory of the device; and a data update unit configured to copy data stored in a second area of ​​the memory of the own device after reading by the second data reading unit to a first area of ​​the memory of the own device when the own device is other than the top module.

6. 6. The module system according to claim 5, A module system, characterized in that the first data reading section, the data copying section, the second data reading section and the data updating section each repeat the process a plurality of times.

7. 7. The module system according to claim 5, a memory map information updating unit configured to update, when the module is a top-level module, the memory map information of the area of ​​the memory assigned as the unique data area of ​​each module, based on the data stored in the first area of ​​the memory of the module after reading by the first data reading unit, and to update, when the module is other than the top-level module, the memory map information of the area of ​​the memory assigned as the unique data area of ​​each module, based on the data stored in the first area of ​​the memory of the module after data updating by the data updating unit.

8. 8. The module system according to claim 5, Each module further includes a setting change unit configured to rewrite data of another module that is a target of the setting change among data stored in the second area of ​​the memory of the module when the module itself is a top-level module; A module system, wherein the other module that is the target of the setting change is a module that needs to be rewritten with changed setting data transmitted from outside.

9. A module system according to any one of claims 5 to 8, A module system, characterized in that the first data reading unit reads data from the first area, which is assigned as a unique data area for all modules from a lower module based on the memory map information.

Images