Node device, system, control method of node device, control method of system, method of manufacturing article, control program, and recording medium

Abstract

To provide a technology that enables data to be sent from node devices to gateway devices and bi-directional information communication between the node devices and the gateway devices, and reduces power consumption of node devices compared to conventional methods.SOLUTION: A node device includes a communication unit that can be connected to a sensor and can communicate with a gateway device, and a control unit. The control unit performs a first task of transmitting data acquired from the sensor to the gateway device using the communication unit, and a second task of transmitting, to the gateway device, information pertaining to synchronization with the gateway device using the communication unit at a timing different from when the first task was performed.SELECTED DRAWING: Figure 11

Description

Technical Field

[0005] ,

[0001] The present invention relates to a node device or the like used for acquiring information related to the state of, for example, production equipment or the like.

Background Art

[0002] Generally, in production equipment or the like, even if the equipment has changed from its original normal state, it has been difficult to detect an abnormality as long as there is no problem with the operation. Therefore, preventive maintenance such as inspection, repair, and parts replacement is performed at regular intervals, and there is a problem that regular inspections and the associated man-hours are required.

[0003] In response to such problems, attempts have been made to provide sensors to production equipment, collect and analyze measurement data, and perform necessary parts replacement, repair, and update according to the state of the production equipment, thereby realizing reduction of unnecessary parts replacement and labor costs. For example, an information processing system in which measurement data of a sensor is transmitted to a gateway device using a node device equipped with communication means, the gateway device stores the received measurement data in a database, and a computer analyzes the stored measurement data.

[0004] In order to appropriately operate such an information processing system, not only one-way communication for transmitting measurement data from the node device to the gateway device but also the necessity of two-way communication for information exchange between the node device and the gateway device may arise. If the receiver of the node device is always kept on to maintain a standby state in order to enable two-way communication, the power consumption of the node device will increase.

[0005] Patent Document 1 describes a communication method in which, after data transmission from a node device to a gateway device is completed, the node device is maintained so that information transmitted from the gateway device can be received for a predetermined period. According to the communication method described in Patent Document 1, when the node device receives a data request signal from the gateway device during this predetermined period, the node device transmits the requested data to the gateway device. [Prior art documents] [Patent Documents]

[0006] [Patent Document 1] Japanese Patent Publication No. 2015-203926 [Overview of the Initiative] [Problems that the invention aims to solve]

[0007] According to the method described in Patent Document 1, it is possible to reduce the power consumption of the node device compared to keeping the receiver of the node device constantly on. However, if data transmission from the node device to the gateway device occurs frequently, for example, the total waiting time performed by the node device will increase accordingly. Therefore, in the method described in Patent Document 1, if the number of data requests from the gateway device is small compared to the number of data transmissions from the node device to the gateway device, the node device is likely to perform unnecessary waiting.

[0008] Therefore, there was a need for a technology that could transmit data from a node device to a gateway device, enable bidirectional information communication between the node device and the gateway device, and reduce the power consumption of the node device compared to conventional methods. [Means for solving the problem]

[0009] A first aspect of the present invention is a node device comprising a communication unit that is connectable to a sensor and can communicate with a gateway device, and a control unit, wherein the control unit performs a first task of transmitting data acquired from the sensor to the gateway device using the communication unit, and performs a second task of transmitting information related to synchronization with the gateway device to the gateway device using the communication unit at a timing different from the timing at which the first task was performed.

[0010] Furthermore, a second aspect of the present invention is a control method for a node device comprising a communication unit that is connectable to a sensor and can communicate with a gateway device, and a control unit, wherein the control unit performs a first task of transmitting data acquired from the sensor to the gateway device using the communication unit, and performs a second task of transmitting information related to synchronization with the gateway device to the gateway device using the communication unit at a timing different from the timing at which the first task was performed. [Effects of the Invention]

[0011] According to the present invention, it is possible to provide a technology that enables data transmission from a node device to a gateway device, enables bidirectional information communication between the node device and the gateway device, and reduces the power consumption of the node device. [Brief explanation of the drawing]

[0012] [Figure 1] A schematic diagram of a production facility to which the information processing system according to Embodiment 1 is applied. [Figure 2] A schematic diagram showing the block configuration of the node device according to Embodiment 1. [Figure 3] A schematic diagram showing the block configuration of the gateway device according to Embodiment 1. [Figure 4] A state transition diagram showing the operation sequence of the node device according to Embodiment 1. [Figure 5] A state transition diagram showing the operation sequence of the gateway device according to Embodiment 1. [Figure 6] A diagram illustrating a task table stored in a node device. [Figure 7] A diagram illustrating a table index stored in a gateway device. [Figure 8] A diagram illustrating a node hash value table stored in a gateway device. [Figure 9](a) Diagram illustrating the configuration of transmission data from the node device in the measurement task. (b) Diagram illustrating the configuration of transmission data from the node device in the synchronization task. [Figure 10] (a) Diagram illustrating the configuration of transmission data of the gateway device when performing time synchronization. (b) Diagram illustrating the configuration of transmission data of the gateway device when performing setting synchronization. [Figure 11] Flowchart showing the process flow executed by the node device when monitoring the state of the production equipment. [Figure 12] Flowchart showing the process flow of the gateway device collecting measurement data and performing processes such as registration for monitoring the production equipment. [Figure 13] Diagram exemplifying the radio intensity threshold table stored in the gateway device according to Embodiment 2. [Figure 14] Diagram exemplifying the synchronization time table stored in the gateway device according to Embodiment 2. [Figure 15] Diagram exemplifying the synchronization setting screen displayed on the display screen when the management device according to Embodiment 2 executes an application. [Figure 16] Flowchart showing the processing procedure executed by the gateway device according to Embodiment 3. [Figure 17] Diagram exemplifying the synchronization setting screen displayed on the display screen when the management device according to Embodiment 3 executes an application. [Figure 18] Diagram exemplifying the task table of the node device before synchronization with the gateway device according to Embodiment 4. [Figure 19] Diagram exemplifying the battery voltage threshold table stored in the gateway device according to Embodiment 5. [Figure 20] Diagram exemplifying the synchronization time table stored in the gateway device according to Embodiment 5. [Figure 21] Diagram exemplifying the operation state table stored in the gateway device according to Embodiment 6. [Figure 22]A diagram illustrating a synchronous time table stored in a gateway device according to Embodiment 6. [Figure 23] A flowchart showing the processing procedure executed by the gateway device according to Embodiment 7. [Modes for carrying out the invention]

[0013] With reference to the drawings, embodiments of the present invention, such as a node device and a system, will be described. The embodiments described below are illustrative, and for example, those skilled in the art may modify the detailed configuration as appropriate without departing from the spirit of the present invention. In the drawings referenced in the following descriptions of embodiments and examples, elements indicated by the same reference numeral have the same function unless otherwise specified.

[0014] Events requiring bidirectional information communication between a node device and a gateway device include, for example, information communication related to the synchronization of both devices. Specifically, examples include clock synchronization between the node device and the gateway device (sometimes referred to as time synchronization), and information communication to share changes in settings related to the collection and transmission of measurement data performed by the node device (sometimes referred to as setting synchronization). Below, we will describe a mode of information communication related to the synchronization of both devices, separate from one-way communication in which data is sent from the node device to the gateway device.

[0015] [Embodiment 1] (Information Processing System) Figure 1 is a schematic diagram of a production facility to which an information processing system, an embodiment of the present invention, is applied. The production facility 101 is equipped with sensors 102 and 103 used to acquire the status of the production facility. Sensors 102 and 103 are, for example, vibration sensors, acceleration sensors, pressure sensors, optical sensors, torque sensors, and temperature sensors, and measure the status of the production facility 101 and quantify it as a physical quantity. This is an information processing system or production system that acquires the status of the equipment using these sensors and performs equipment monitoring, etc.

[0016] To acquire the status of the production equipment, one or more sensors 102 and 103 can be connected to the node device 104. Sensors 102 and 103 may be built into the node device. One or more node devices 104 are installed in the production equipment 101 as needed. The node device 104 is equipped with a communication means 109, and the gateway device 105 is equipped with a communication means 110, and the node device 104 and the gateway device 105 can communicate with each other. The communication means can be one or more communication methods appropriately selected from wireless communication such as LPWA (Low Power Wide Area) or wireless LAN, or wired communication such as Ethernet or field network.

[0017] Measurement data obtained using sensors is collected from node device 104 to gateway device 105 via communication means 109 and 110. Gateway device 105 is connected to network 106. Network 106 may be a dedicated network within the factory or a wide-area network such as the internet. Gateway device 105 is installed within range of node device 104 and communication means 109 and 110.

[0018] The measurement data collected by the gateway device 105 is stored in the database 107 of a data storage device on the network 106. Some of the functions of the gateway device 105 may be implemented as software within the database 107 or in the storage of a computer. The database 107 may also be a storage device or storage medium.

[0019] The administrator can check the results stored in the database 107 via the computer-equipped management device 108. The management device 108 can perform various processes using the measurement data stored in the database 107 and analyze the status of the production equipment 101. If an abnormality is detected in the production equipment 101, the management device 108 may notify the administrator by issuing an alert or sending an email, as necessary.

[0020] (Node device configuration) Figure 2 is a schematic diagram showing the block configuration of the node device 104 shown in Figure 1. Note that in Figure 2, functional elements necessary to explain the features of this embodiment are represented as functional blocks, but general functional elements not directly related to the problem-solving principle of the present invention are omitted. Furthermore, each functional element shown in Figure 2 is a functional concept and does not necessarily need to be physically configured as shown. For example, the specific forms of distribution and integration of each functional block are not limited to the illustrated examples, and all or part of them can be functionally or physically distributed and integrated in any unit depending on the usage situation. Each functional block can be configured using hardware or software. That is, some of these functional blocks can be configured, for example, by the CPU 212, acting as the control unit, reading and executing a control program stored in a memory device or non-temporary recording medium. Alternatively, some or all of the functional blocks may be configured using hardware such as an ASIC.

[0021] The node device 104 is equipped with a CPU 212 that controls the overall operation sequence and task execution. The CPU 212 can read and execute control programs and control information from the storage unit 208 or a computer-readable recording medium (not shown). As recording media, for example, ROM, flexible disks, optical disks, magneto-optical disks, magnetic tapes, non-volatile memory such as USB memory, SSDs, etc. can be used.

[0022] The node device 104 is configured to be connectable to one or more sensors 203 installed on the production equipment 101. The node device 104 includes a signal input unit 204 capable of converting analog signals output by the sensors 203 into digital signals. The signal input unit 204 includes an A / D converter that converts one or more analog input signals into digital signals. Alternatively, the signal input unit 204 may be built into the sensor 203, and the sensor may be configured to output a digital signal.

[0023] The node device 104 includes a battery 210 as a power source and a temperature sensor 211 for measuring the internal temperature of the device. The battery 210 may be a primary battery, a secondary battery, or a capacitor that stores energy obtained by generating electricity, and is equipped with a sensor for monitoring the remaining charge. The output signals of the battery 210 sensor and the temperature sensor 211 are processed as needed by the signal input unit 204 and the processing unit 205, and are stored in the storage unit 208 or transmitted to the outside from the input / output unit 206.

[0024] The signal digitized by the signal input unit 204 is processed by the processing unit 205 as needed. The processing unit 205 combines, for example, one or more of the following: no processing, FFT processing, partial overall processing, envelope processing, frequency filtering, differentiation processing, integration processing, wavelet processing, mean processing, standard deviation processing, maximum value processing, minimum value processing, peak-to-peak processing, peak hold processing, RMS processing, crest factor processing, form factor processing, impulse coefficient processing, and margin coefficient processing, and executes them in a determined order.

[0025] For example, in the no-processing case, the digitized input signal is transmitted to the input / output unit 206 without processing. If FFT processing is performed, the digitized input signal is decomposed into frequency components. If partial overall processing is performed, the sum of products is calculated for the FFT-processed frequency components within a limited frequency range. If envelope processing is performed, envelope processing is applied to the input signal. If frequency filtering is performed, unwanted signals are removed by passing the input signal through a low-pass filter, high-pass filter, or band-pass filter at a set frequency, thereby obtaining the desired signal.

[0026] Furthermore, when performing differentiation, the signal is differentiated with respect to the input signal. When performing integration, the signal is integrated with respect to the input signal. When performing wavelet processing, the digitized input signal is decomposed into frequency and time components. When performing averaging, the mean value is calculated for the input signal. When performing standard deviation processing, the standard deviation of the input signal is calculated. When performing maximum value processing, the maximum value is calculated for the input signal. When performing minimum value processing, the minimum value is calculated for the input signal. When performing peak-to-peak processing, the difference between the maximum and minimum values ​​of the input signal is calculated. When performing peak hold processing, measurements are taken continuously for a predetermined period to obtain the maximum value within that period. When performing RMS value processing, the RMS value is calculated for the input signal.

[0027] Furthermore, when performing crest factor processing, the crest factor is calculated by dividing the maximum value of the input signal by its RMS value. When performing form factor processing, the form factor is calculated by dividing the RMS value of the input signal by its mean value. When performing impulse coefficient processing, the impulse coefficient is calculated by dividing the maximum value of the input signal by the absolute mean value of the input signal. When performing margin coefficient processing, the margin coefficient is calculated by dividing the maximum value of the input signal by the square of the square root mean value of the input signal. When performing machine learning model inference processing, training data is loaded into a computer or similar device beforehand, and the data is analyzed to generate a machine learning model with defined classification and identification rules. The machine learning model is then incorporated into the node device, and the output is calculated based on the input signal and the machine learning model. The various signal processing operations described above are performed by the processing unit 205, but may be carried out by dedicated hardware such as PLA in some cases.

[0028] The node device 104 is equipped with an input / output unit 206 for inputting and outputting information to and from the outside. Through the input / output unit 206, the node device 104 can, for example, output signals or data processed by the processing unit 205 to the outside, or input and output synchronization-related information with the gateway device 105. The input / output unit 206 can operate under the control of the CPU 212, for example, in cooperation with the processing unit 205. The input / output unit 206 is equipped with wireless communication means 207 (communication unit) corresponding to the communication means 109 shown in Figure 1. Preferably, the input / output unit 206 is further equipped with a general-purpose input / output unit 209 that can communicate with a network or external devices via a wired connection.

[0029] The input / output unit 206 can input and output information to and from the storage unit 208. For example, the node device 104 associates the measurement data output from the processing unit 205 with the node number (node ​​identification information) and the measurement task number (task identification information) as identification information to identify the individual node device 104, and stores this information in the storage unit 208. Subsequently, the input / output unit 206 can read the information from the storage unit 208 and transmit it to the gateway device 105 via the wireless communication means 207. Alternatively, synchronization-related information, such as parameter values ​​of the task table, can be obtained from the gateway device 105 via the wireless communication means 207 and stored in the storage unit 208.

[0030] The node device 104 is equipped with an event generation unit 202. The event generation unit 202 generates trigger events to start various tasks, such as a measurement task that uses a sensor 203 to take measurements and transmit the measurement data to the gateway device 105, and a synchronization task that inputs and outputs synchronization-related information with the gateway device 105. Depending on the type of task, the event generation unit 202 can, for example, autonomously generate trigger events at predetermined intervals, or generate trigger events as needed based on information input from the outside via the input / output unit 206. Possible trigger event conditions include, for example, time intervals, time specifications, external trigger input signals, changes in the state of the node device such as temperature and battery level, calls from other tasks within the node, calls from the gateway device, calls from other node devices, etc. The event generation unit 202 may be configured with dedicated hardware such as a PLA, or it may be configured with software control programs that control the operation of the CPU 212.

[0031] For example, when a measurement task is to be performed at predetermined time intervals, the event generation unit 202 refers to a built-in timer and generates a trigger event (trigger signal) that causes the CPU 212 to start executing the measurement task. Also, when a synchronization task is performed to synchronize the timer built into the node device with the timer built into the gateway device, a trigger event (trigger signal) can be generated at a time interval longer than the time interval of the measurement task. Since timer synchronization errors usually occur after a longer period than the execution interval of the measurement task, extending the execution interval of the synchronization task can suppress the depletion of the node device's battery 210.

[0032] For example, when executing a measurement task at a specified time, the event generation unit 202 refers to its built-in clock and generates a trigger event (trigger signal) that causes the CPU 212 to start executing the measurement task. Furthermore, when executing a synchronization task to synchronize the clock built into the node device with the clock built into the gateway device, the trigger event (trigger signal) can be generated a predetermined time before the specified time for executing the measurement task. This ensures that the measurement task is executed at the specified time, and because the synchronization task is executed only when necessary, the battery consumption of the node device 210 can be suppressed.

[0033] For example, when controlling task execution according to the internal temperature of the device or the remaining battery level, the event generation unit 202 generates a trigger event (trigger signal) based on the measurement value from the temperature sensor 211 or the remaining battery level measurement value of the battery 210. By controlling the execution of, for example, a synchronous task according to the state of the device, it is possible to ensure stable operation of the node device while suppressing the consumption of the battery 210.

[0034] The event generation conditions of the event generation unit 202, the signal input conditions of the signal input unit 204, the signal processing conditions of the processing unit 205, and the input / output conditions of the input / output unit 206 are all stored in the task table within the storage unit 208. Alternatively, the task table may be stored in a separate storage device instead of the storage unit 208.

[0035] (Gateway device configuration) Figure 3 is a schematic diagram showing the block configuration of the gateway device 105 shown in Figure 1. Note that in Figure 3, functional elements necessary to explain the features of this embodiment are represented as functional blocks, but general functional elements not directly related to the problem-solving principle of the present invention are omitted. Furthermore, each functional element shown in Figure 3 is a functional concept and does not necessarily need to be physically configured as shown. For example, the specific forms of distribution and integration of each functional block are not limited to the illustrated examples, and all or part of them can be functionally or physically distributed and integrated in any unit depending on the usage situation. Each functional block can be configured using hardware or software. That is, some of these functional blocks can be configured, for example, by the CPU 304 reading and executing a control program stored in a memory device or non-temporary recording medium. Alternatively, some or all of the functional blocks may be configured using hardware such as an ASIC.

[0036] The gateway device 105 is equipped with a CPU 304 that controls the overall operation sequence and task execution. The CPU 304 can read and execute control programs and control information from the storage device 303 or a computer-readable recording medium (not shown). Examples of recording media that can be used include ROM, flexible disks, optical disks, magneto-optical disks, magnetic tapes, non-volatile memory such as USB memory, and SSDs.

[0037] The gateway device 301 is equipped with wireless communication means 302, which corresponds to the communication means 110 shown in Figure 1, and can communicate wirelessly with the node device 104. The gateway device 301 can process measurement data received from the node device using a table index stored in the storage device 303. The table index contains information showing the relationship between a node number that identifies a node device in the information processing system, a task number that identifies a measurement task, and a table in the database 107 that stores the measurement data for each measurement task.

[0038] When the gateway device 301 receives measurement data, which includes a node number and task number, from a node device via wireless communication means 302, it refers to a table index to determine which table in database 107 should store the measurement data. Then, it connects to the network 106 via wired communication means 305 and stores the measurement data in the predetermined table in database 107.

[0039] (Operation sequence of node devices) Figure 4 is a state transition diagram showing the operation sequence of the node device 104. When power is turned on, the node device 104 enters state ST11 and performs initialization and reads setting information from the storage unit 208. If a measurement event occurs as the first task after state ST11, the node device 104 transitions to state ST12, and if a synchronization event occurs as the second task, it transitions to state ST14. If no measurement event (first task) or synchronization event (second task) occurs, the node device 104 transitions to state ST13 and enters a sleep state in which the communication unit is suspended. After transmitting information in the synchronization event as the second task, the node device 104 terminates the synchronization task after a predetermined time has elapsed or after receiving a signal from the gateway device notifying it of the end of the synchronization task.

[0040] If a measurement event occurs while the node device 104 is in sleep state ST13, it transitions to the measurement state ST12. If there is no synchronization event after the measurement is complete, the node device 104 transitions to the sleep state ST13. If there is a synchronization event after the measurement is complete, the node device 104 transitions to the synchronization state ST14. If a synchronization event occurs while the node device 104 is in sleep state ST13, it transitions to the synchronization state ST14. If there is no measurement event after synchronization is complete, the node device 104 transitions to the sleep state ST13. If a measurement event occurs after synchronization is complete, the node device 104 transitions to state ST12. If both a measurement event and a synchronization event occur while the node device 104 is in sleep state ST13, it transitions to the measurement state (state ST12), and then transitions to the synchronization state ST14 after the measurement process is complete.

[0041] (Gateway device operation sequence) Figure 5 is a state transition diagram showing the operation sequence of the gateway device 105. When power is turned on, the gateway device 301 enters state ST21 and performs initialization and reads setting information from the storage device 303. If the wireless communication means 302 receives measurement data from the node device after state ST21, the gateway device 105 transitions to measurement processing (state ST22). On the other hand, if the wireless communication means 302 receives synchronization data from the node device after state ST21, the gateway device 105 transitions to synchronization processing (state ST24). If the wireless communication means 302 has not received any data, the gateway device 105 transitions to the standby state ST23. If the wireless communication means 302 receives measurement data from the node device while in the standby state ST23, the gateway device 105 transitions to measurement processing (state ST22). If the wireless communication means 302 receives synchronization data from the node device while in the standby state ST23, the gateway device 105 transitions to synchronization processing (state ST24). If the wireless communication means 302 receives synchronization data from the node device 104 after the measurement process in state ST22, the gateway device 105 transitions to the synchronization process (state ST24). Also, if the wireless communication means 302 receives measurement data from the node device 104 after the synchronization process in state ST24, the gateway device 105 transitions to the measurement process (state ST22).

[0042] (Task table provided by the node device) Figure 6 shows the task table 601 stored in the memory unit 208 of the node device 104. The task table 601 consists of a task number 602 assigned to each task, an event type 603 to identify whether the task is a measurement event or a synchronization event, an event condition 604 for the event generation unit 202, a signal input condition 605 for the signal input unit 204, a signal processing condition 606 for the processing unit 205, and an output condition 607 for the input / output unit 206. In addition, a node number 608 to identify the node device storing the task table 601 and a unique hash value 609 to identify the task table are stored in the memory unit 208, linked to the task table 601. Depending on the monitoring target and the connected sensors, one or more tasks are pre-registered in the task table 601 of the node device 104. Each task in the task table 601 is executed sequentially, starting with the task whose event condition 604 is met. Tasks for which event condition 604 is met are executed according to signal input condition 605, signal processing condition 606, and output condition 607. Figure 6 shows the contents of the task table 601 stored in the memory unit 208, and also illustrates the configuration of the display image when the task table 601 is displayed on the screen of the display device.

[0043] (Table index provided by the gateway device) Figure 7 shows the table index 701 stored in the storage device 303 of the gateway device 105. The table index 701 consists of the node number 702 of the node device 104, the task number 703 corresponding to the task number 602 in the task table 601 of the node device 104, a database 704 indicating the destination for the received measurement data, and a table 705 defining the area in the database where the data is to be inserted. The gateway device 105 pre-registers the table index 701 corresponding to the task table 601 of each node device 104 that it can communicate with in the storage device 303. When the gateway device 105 receives measurement data from the node device 104, it searches for the node number and task number sent with the measurement data among the node number 702 and task number 703 stored in the table index 701. If a node number 702 and task number 703 that match the received node number and task number are found in the table index 701, the measurement data is stored in the location specified in the database 704 and table 705. Figure 7 shows the contents of the table index 701 stored in the storage device 303, and also illustrates the configuration of the display image when the table index 701 is displayed on the screen of the display device.

[0044] (Node hash value table provided by the gateway device) Figure 8 shows the node hash value table 801 stored in the storage device 303 of the gateway device 105. The gateway device 105 has the task table 601 of each communicationable node device 104 and the node hash value table 801 in its storage device 303. The node hash value table 801 consists of node number 802 and hash value 803. Node number 802 corresponds to node number 608 shown in Figure 6, and hash value 803 corresponds to hash value 609 shown in Figure 6. This information is registered from the management device 108 to the gateway device 105 when the management device 108 hashes the information in the task table 601 of each node. Figure 8 shows the contents of the node hash value table 801 stored in the storage device 303, and also illustrates the configuration of the display image when the node hash value table 801 is displayed on the screen of the display device.

[0045] (Configuration of data transmitted by node devices) Figures 9(a) and 9(b) are schematic diagrams illustrating the configuration of transmission data transmitted by the node device 104 to the wireless communication means 302 of the gateway device 105 using the wireless communication means 207. Figure 9(a) illustrates the configuration of transmission data in a measurement task, and Figure 9(b) illustrates the configuration of transmission data in a synchronization task.

[0046] For a measurement task, the node device 104 sends a set of measurement data 905, which includes the node number 901 for identifying the individual, the task number 902 for identifying the task, the measurement time 903 when the measurement was performed using the sensor, and the measured value 904. For a synchronization task, the node device 104 sends a set of node information 911, which includes the node number 901 for identifying the individual, the task number 902 for identifying the task, the measurement time 903 when the temperature was measured by the temperature sensor 211 or the remaining battery level of the battery 210 was measured, a flag indicating that it is a synchronization event, the individual number, battery voltage, internal temperature, hash value of setting information, etc., as synchronization data 912. In the illustrated example, the measurement data 905 or synchronization data 912 is sent as a single data group, but the data group may be divided and sent as needed.

[0047] (Configuration of data transmitted by the gateway device) Figures 10(a) and 10(b) are schematic diagrams illustrating the configuration of transmission data transmitted by the gateway device 105 to the wireless communication means 207 of the node device 104 using the wireless communication means 302, which contains information related to the synchronization task. Figure 10(a) illustrates the configuration of transmission data when performing time synchronization, and Figure 10(b) illustrates the configuration of transmission data when performing configuration synchronization.

[0048] When performing time synchronization processing, the gateway device 105 receives the synchronization data 912 shown in Figure 9(b) from the node device 104 and then transmits information related to time synchronization to the node device 104. Specifically, after receiving the synchronization data 912 via the wireless communication means 302, the gateway device 105 sets a data type flag 1001 indicating the type of synchronization data, the current time 1002, and a flag 1003 indicating the end of the time synchronization process, and transmits it from the wireless communication means 302 as time synchronization data 1004.

[0049] When performing the configuration synchronization process, the gateway device 105 receives the synchronization data 912 shown in Figure 9(b) from the node device 104 and then transmits information related to the configuration synchronization to the node device 104. Specifically, it transmits to the node device, via the wireless communication means 302, a set of data type flag 1001 indicating the type of synchronization data, configuration data 1011, and a flag 1003 indicating the completion of the configuration synchronization process, as configuration synchronization data 1012. In this example, the time synchronization data 1004 or the configuration synchronization data 1012 is transmitted as a single data group, but it may be divided and transmitted as needed.

[0050] (Node device operation flow) Figure 11 is a flowchart showing the processing flow performed by the node device 104 when monitoring the status of the production equipment 101. Here, we will explain the process by which the node device 104 monitors the status of the production equipment 101 based on the task table 601 shown in Figure 6.

[0051] First, the node device 104 starts monitoring the production equipment 101 in step S101, and in step S102 determines whether the monitoring task for the node device 104 is set up, that is, whether the CPU 212 is able to execute it. If it is determined in step S102 that it is not set up (S102: NO), the process proceeds to step S103, where the monitoring task is read from the task table 601 in the storage unit 208, and the CPU 212 is made ready to execute.

[0052] In the following step S104, based on the event conditions 604 of each task registered in the task table 601, it is checked whether the conditions such as the specified time, specified interval, and external input are met, that is, whether or not a measurement event has occurred.

[0053] If a measurement event occurs (S104: YES), a task is executed based on the registered contents of the task table 601. Specifically, in step S105, the signal input unit 204 is configured by selecting registered signal input conditions 605 such as the physical quantity input channel, sampling frequency, input range, number of samples, and amplification factor, and signal input processing such as analog-to-digital conversion is performed based on the configured signal input conditions 605. Furthermore, in step S106, the processing unit 205 performs output processing (i.e., signal processing on the digitally converted measurement data) as necessary according to the signal processing conditions 606.

[0054] In step S107, the signal-processed measurement data is transmitted from the wireless communication means 207 of the input / output unit 206 based on the output conditions 607 registered in the task table 601. If no other measurement event or synchronization event occurs immediately after transmission, the node device 104 lowers the clock or power supply voltage of the signal input unit 204, processing unit 205, and wireless communication means 207 to enter a sleep state until the next measurement event or synchronization event occurs, thereby suppressing the consumption of the battery 210. Then, while in the sleep state, it returns to step S104 and determines whether a measurement event has occurred.

[0055] If no measurement event occurred in step S104 (S104:NO), proceed to step S111 to check if a synchronization event occurred. If no synchronization event occurred (S111:NO), return to step S104 and determine again whether a measurement event occurred.

[0056] If a synchronization event has occurred in step S111 (S111:YES), or if it is determined in step S102 that the monitoring task for node device 104 has been set up (registered) (S102:YES), proceed to step S112.

[0057] In step S112, the node device 104 performs internal signal processing to acquire node information such as the remaining charge of the battery 210, the internal temperature measured by the temperature sensor 211, and the hash value of the setting information. In the following step S113, the node device 104 transmits the acquired node information to the gateway device 105 using the wireless communication means 207. After transmitting in step S113, the node device 104 does not enter a sleep state in step S114, but maintains a state in which it can receive synchronization information from the gateway device 105 via the wireless communication means 207.

[0058] In step S115, the system determines whether the necessary synchronization process has been completed using the received synchronization information. If it has not been completed (S115: NO), the system returns to step S114. If the necessary synchronization process has been completed (S115: YES), the node device 104 reduces the clock or power supply voltage of the signal input unit 204, the processing unit 205, and the wireless communication means 207, and enters a sleep state until the next measurement event or synchronization event occurs, thereby suppressing the consumption of the battery 210. Then, while remaining in the sleep state, the system returns to step S104 and determines whether a measurement event has occurred.

[0059] (Gateway device operation flow) Figure 12 is a flowchart illustrating the process by which the gateway device 105 collects and registers measurement data in order to monitor the production equipment 101. This section describes the process by which the gateway device 105 registers the measurement data sent from the node device 104 to the database 107 in order to monitor the production equipment 101.

[0060] First, the gateway device 105 starts monitoring the production equipment 101 in step S201 and reads the table index 701, which has been pre-registered in the storage device 303, in step S202. In step S203, the CPU 304 checks with the wireless communication means 302 whether or not it has received wireless communication from the node device 104.

[0061] When the gateway device 105 receives data from the node device 104 (S203:YES), it extracts the node number and task number transmitted along with the measurement data in step S204. In the following step S205, the CPU 304 compares the extracted node number and task number with node number 702 and task number 703 in the table index 701 to search for the corresponding index.

[0062] In step S206, the system checks whether the received data is related to a measurement event or a synchronization event. If it is a measurement event, the system proceeds to step S207. In step S207, the system determines table 705 in the database 704 where the measurement data is stored from the records of table index 701 found in step S205, and generates a query to register the measurement data. In the following step S208, the gateway device 105 executes the query generated in step S207 and records the measurement data in the database table.

[0063] On the other hand, if it is determined in step S206 that the data is related to a synchronization event, the process proceeds to step S211, and time information is transmitted from the gateway device 105 to the node device 104. The time information to be transmitted may be obtained from the clock built into the gateway device 105, or from a device on the network via the wired communication means 305.

[0064] Next, in step S212, the hash value 609 of the task table 601 of node device 104 in the received data is compared with the hash value 803 in the node hash value table 801 stored by the monitoring gateway. If the two hash values ​​do not match (S212: NO), the process proceeds to step S213, where the node task in the gateway device is sent to node device 104, and upon completion, step S214 notifies node device 104 of the end of synchronization. Then, the process moves to step S207, where a query is generated to register node information. In step S208, gateway device 105 executes the query and records the node information in the database table. Note that if the hash values ​​match in step S212 (S212: YES), there is no change in the task table of node device 104, so the process proceeds to step S214 without sending the task table, and node device 104 is notified of the end of synchronization.

[0065] According to this embodiment, even when a synchronization event is set separately from the measurement event in an autonomous sensor system, the synchronization event can be independently executed by the node device at the required timing. Therefore, it is possible to reduce power consumption and provide a method for synchronizing a node device with communication timing constraints with a higher-level system.

[0066] [Embodiment 2] Embodiment 2 of the present invention will be described with reference to the drawings. Matters common to Embodiment 1 will be simplified or omitted from the description. As Embodiment 2, a procedure for determining synchronization event conditions based on the radio wave strength when the gateway device 105 and the node device 104 communicate wirelessly will be described. The wireless communication means 302 provided in the gateway device 105 of this embodiment is capable of not only sending and receiving data with the node device 104, but also of acquiring the radio wave strength of the wireless communication from the node device 104.

[0067] Figure 13 shows an example of a radio wave intensity threshold table 1301 stored in the memory device 303 by the gateway device 105. In the radio wave intensity threshold table 1301, the radio wave intensity column 1302 defines the strength levels of the radio wave intensity, and for each strength level, the minimum interval column 1303 sets the time interval at which the synchronization task should be executed. Figure 13 shows the contents of the radio wave intensity threshold table 1301 stored in the memory unit 308, and also illustrates the configuration of the display image when the radio wave intensity threshold table 1301 is displayed on the screen of the display device.

[0068] Figure 14 shows the synchronization time table 1401 stored in the storage device 303 by the gateway device 105. The synchronization time table 1401 includes a node number column 1402 for distinguishing node devices that are wireless communication partners, a synchronization time column 1403 related to the timing of executing synchronization tasks with each node device, and a radio wave strength column 1404 related to the strength of radio waves received from each node device. The gateway device 105 manages the timing of executing synchronization tasks for individual node devices based on the synchronization time table 1401. Figure 14 shows the contents of the synchronization time table 1401 stored in the storage unit 308, and also illustrates the configuration of the display image when the synchronization time table 1401 is displayed on the screen of the display device. The gateway device 105 determines the synchronization time 1403 of the synchronization time table 1401 based on the radio wave strength threshold table 1301 and the radio wave strength measurement values ​​of radio waves received from each node device.

[0069] If the gateway device 105 determines in step S206 of the flowchart shown in Figure 12 that a synchronization event has occurred, it proceeds to step S211, reflects the measured radio wave strength from the gateway device in the synchronization time table 1401, and determines the synchronization time 1403 based on the radio wave strength threshold table 1301. For example, if the radio wave strength from a node device (first node device) is strong, even if communication related to a synchronization event is performed at a timing close to communication with another node device (second node device), the possibility of communication failure is small, so the minimum interval can be set small. The gateway device can adjust the interval between the timing when the first node device performs a synchronization task and the timing when the second node device performs a synchronization task.

[0070] In this example, for node devices with node numbers 1402, numbers 101 and 102, the radio signal strength is -60 or higher, so based on the radio signal strength threshold table 1301, the execution times for the synchronization task are set with a 5-minute interval. For node device with node number 1402, number 103, the radio signal strength is in the range of -70 to -61, so the execution times for the synchronization task are set with a 10-minute interval. For node devices with node numbers 1402, numbers 104 and 105, the radio signal strength is in the range of -71 or lower, so the execution times for the synchronization task are set with a 20-minute interval. In this way, by setting different, non-overlapping synchronization timing intervals for each node device according to the measured radio signal strength, problems such as radio interference and congestion of the wireless communication means 302 can be reduced, and unnecessary power consumption can be suppressed.

[0071] Figure 15 is an example of the synchronization settings screen 1501 that is displayed on the screen when the management device 108 executes an application to configure the operation of the gateway device 105 and the node device 104.

[0072] When setting the radio wave intensity threshold table 1301 on the gateway device, the management device 108 application may be run in advance to create the radio wave intensity threshold table 1301, and then loaded into the gateway device's storage device 303 via a computer-readable recording medium or network. Alternatively, the management device 108 and the gateway device may be connected to communicate using the wired communication means 305, and the management device 108 application may be used to create or edit the radio wave intensity threshold table 1301 on the gateway device.

[0073] When an update occurs in the synchronization time table 1401, the gateway device 105 updates the event condition 604 of the synchronization event (in this case, the event where task number 602 is 0) in the task table 601 of the node device 104. Along with the update of the task table 601, hash values ​​609 and 803 are updated. In this example, at step S212 of the flowchart in Figure 12 above, it is determined that the hash value included in the node information of the node device 104 and the hash value shown in the task table 601 of the node device 104 within the gateway device are different. Therefore, in step S213, the gateway device 105 transmits the task table 601, updates the task of the node device 104, and updates the synchronization time for the next time and beyond. The timing for updating the minimum interval according to the radio wave strength and the timing for updating the task table may be updated together at each synchronization timing, or they may be updated together at different timings.

[0074] In this embodiment, the event conditions for the node device's synchronization task are determined based on the radio wave strength of the node device's wireless communication received by the gateway device. This allows the gateway device to perform processing without overlapping with synchronization events with other node devices, even when retransmissions or error handling occur during synchronization with a node device with weak radio wave strength, thus providing a synchronization method that reduces unnecessary power consumption.

[0075] [Embodiment 3] Embodiment 3 of the present invention will be described with reference to the drawings. Matters common to the previously described embodiments will be simplified or omitted. In Embodiment 3, the procedure for the gateway device notifying the management device of an abnormality in the node device when the gateway device does not receive synchronization event data from the node device despite the date and time being the event condition for the synchronization task is described.

[0076] Figure 16 is a flowchart showing the processing procedure executed by the gateway device 105. In step S203, the gateway device uses the wireless communication means 302 to check whether or not it has received wireless communication from the node device 104. If there is no received data (step S203: NO), the process proceeds to step S221, where the gateway device 105 checks if the current time matches the synchronization time 1104 in the synchronization time table 1101. If the times match (step S221: YES), the process proceeds to step S222 to check if a synchronization event has already been received.

[0077] If a synchronization event is received (step S222: YES), the process proceeds to step S223 to check node information such as battery level and signal strength. If the node information is deemed acceptable (step S223: YES), the synchronization time table 1101 is updated in step S224. If the time matches but no synchronization event is received (step S222: NO), the process checks whether a measurement event has been received in step S231. If a measurement event has been received (step S231: YES), the process proceeds to step S203 to perform the reception process.

[0078] Figure 17 illustrates the synchronization settings screen 1501 displayed on the screen when the management device 108 executes an application to configure the operation of the gateway device 105 and the node device 104. If neither a synchronization event nor a measurement event is received when the times match, it is possible that an abnormality has occurred in the node device 104 and it cannot be transmitted to the gateway device 105. In this case, the gateway device 105 notifies the node device 104 of the abnormality in step S232 using symbols 1511, notifications 1512, or messages 1513 from the synchronization settings screen 1501 of the application on the management device 108. Note that, considering time errors such as time differences and communication delays between the node device 104 and the gateway device 105, the determination of time matching in step S221 may be made with redundancy in the time range.

[0079] Node device 104 is controlled to prioritize the execution of the measurement event in step S104 over the synchronization event in step S111. Therefore, if the timing of the measurement task and the synchronization task overlap, the measurement task is executed first, followed by the synchronization task. In this case, since gateway device 105 receives the measurement event first in step S231 and then the synchronization task, it does not issue an abnormality notification in step S232.

[0080] According to this embodiment, if the gateway device does not receive synchronization event data from the node device at a predetermined time, it can detect that the node device is abnormal and provide a method for notifying the management device of the abnormality.

[0081] [Embodiment 4] Embodiment 4 of the present invention will be described with reference to the drawings. Matters common to the previously described embodiments will be simplified or omitted. Embodiment 4 will describe the procedure for obtaining the synchronization timing and task table from the gateway device when introducing a node device.

[0082] Figure 18 shows the task table 1801 of the node device 104 before synchronization with the gateway device 105. Since synchronization has not yet occurred, no measurement tasks are registered in the task table 1801. When the node device 104 is started in step S101 of the flowchart in Figure 11, it is determined to be unconfigured in step S102 because no measurement tasks are registered. When it is determined in step S111 that a synchronization event has occurred, node information such as the battery voltage, internal temperature, and hash value of the configuration information of the node device 104 is acquired in step S112, and transmitted from the wireless communication means 207 via the input / output unit 206 in step S113.

[0083] In step S211 of the flowchart in Figure 12, the gateway device 105 sends the time to the node device 104, and then in step S212, it compares the hash value in the gateway device 105's node hash value table 801 with the hash value in the node information. In this example, since the node device 104 does not have a measurement task registered, the hash values ​​do not match. Therefore, the gateway device 105 proceeds to step S213 and sends the task table 601.

[0084] Then, in step S114 of the flowchart in Figure 11, the node device 104 receives the task table 601 and performs synchronization processing to reflect the settings. In step S214, the gateway device 105 notifies the node device 104 that synchronization is complete, and in response, the node device determines in step S115 that synchronization is complete. After synchronization, if there are no measurement events or synchronization events, the clock of the signal input unit 204 and processing unit 205 of the node device 104 is reduced and it enters a sleep state until the next measurement event or synchronization event occurs. According to this embodiment, when introducing a node device, the synchronization timing and task table can be obtained from the gateway device to synchronize the settings.

[0085] [Embodiment 5] Embodiment 5 of the present invention will be described with reference to the drawings. Matters common to the previously described embodiments will be simplified or omitted. Embodiment 5 describes a procedure for extending battery life by changing the synchronization timing interval when the battery voltage of the node device decreases.

[0086] Figure 19 shows an example of a battery voltage threshold table 1901 stored in the storage device 303 of the gateway device 105. The battery voltage threshold table 1901 consists of columns for setting the battery voltage 1902 and the corresponding synchronization interval 1903. When setting the battery voltage threshold table 1901 in the gateway device, the battery voltage threshold table 1901 may be created in advance by running the application on the management device 108 and then loaded into the storage device 303 of the gateway device via a computer-readable recording medium or network. Alternatively, the management device 108 and the gateway device may be connected communicatively using the wired communication means 305, and the battery voltage threshold table 1901 may be created or edited in the gateway device using the application on the management device 108.

[0087] Figure 20 shows an example of a synchronization time table 1401 stored in the memory device 303 by the gateway device 105. When a synchronization event occurs in step S112 of the flowchart in Figure 11, the node device 104 performs internal signal processing to obtain the voltage value of the battery 210 and transmits it to the gateway device 105 as node information in step S113.

[0088] In step S211 of the flowchart in Figure 12, the gateway device 105 updates the information in the synchronization time table 1401 along with the time transmission. For example, if the battery voltage of node device 104 falls below 2.2V, the gateway device 105 updates the event condition 604 of the synchronization task in the task table 601 of node device 104 from daily to every other day, based on the battery voltage threshold table 1901. By setting a longer synchronization interval, battery consumption can be reduced and the battery life of node device 104 can be extended.

[0089] When the task table 601 is updated, the gateway device 105 determines in step S212 that the hash values ​​of the node device 104 do not match. Therefore, the gateway device 105 transmits the task table 601 in step S213. The node device 104 receives the task table 601 in step S114 and performs synchronization processing to reflect it in the settings. The gateway device 105 notifies the node device 104 of the end of synchronization in step S214 and terminates the synchronization. The node device terminates the synchronization in step S115, and if there are no measurement events or synchronization events, it lowers the clock of the signal input unit 204 and the processing unit 205 and enters a sleep state until the next measurement event or synchronization event occurs. In this embodiment, when the battery voltage of the node device drops, the synchronization timing interval can be widened to reduce battery consumption and extend battery life.

[0090] [Embodiment 6] Embodiment 6 of the present invention will be described with reference to the drawings. Matters common to the previously described embodiments will be simplified or omitted. Embodiment 6 describes a procedure for synchronizing with a node device while improving usability and reducing power consumption by changing the synchronization timing according to the operating status of the node device. For example, the gateway device acquires information on whether the node device is in operation or undergoing adjustment, and if it is undergoing adjustment, it sets a shorter interval until the node device next executes a synchronization task than when it is in operation.

[0091] Figure 21 shows an example of an operation status table 2101 stored in the storage device 303 of the gateway device 105. The operation status table 2101 includes a column related to the operation status 2102 and a column for setting the corresponding synchronization interval 2103. For example, if parameter adjustments are frequent immediately after the introduction of a node device, the user can pre-set the synchronization interval according to the operation status 2102. When setting the operation status table 2101, the operation status table 2101 may be created by running the application on the management device 108 in advance and then loaded into the storage device 303 of the gateway device via a computer-readable recording medium or network. Alternatively, the management device 108 and the gateway device may be connected to communicate using the wired communication means 305, and the operation status table 2101 may be created or edited on the gateway device using the application on the management device 108. In the example in Figure 21, an example is shown where synchronization occurs twice when the operation status 2102 is "adjustment," but it may be two or more times.

[0092] Figure 22 shows the synchronization time table 1401 stored in the storage device 303 of the gateway device 105. The user changes the contents of the operation status 1406 according to the operation status of the node device 104. Here, we will explain the case where node device 104, node number 1402, is operated in the "adjustment" state. When the gateway device 105 receives node information from node device 104 via a synchronization event, it updates the information in the synchronization time table 1401 along with the time transmission at step S211 of the flowchart in Figure 12. Based on the operation status table 2101, since the operation status of node 101, node number 1402, is "adjustment", the gateway device 105 updates the event condition 604 of the synchronization task in the task table 601 of node device 104, node number 101, to synchronize at 12:00 and 15:00. When the update is performed, the hash value of the node device 104 does not match in step S212, so the gateway device 105 sends the task table 601 in step S213. The node device 104 receives the task table 601 in step S114 and performs synchronization processing to reflect the settings. The gateway device 105 notifies the node device 104 of the end of synchronization in step S214, and the node device ends synchronization in step S115. After the end of synchronization, if there are no measurement events or synchronization events, the clock of the signal input unit 204 and processing unit 205 of the node device 104 is reduced and it enters a sleep state until the next measurement event or synchronization event occurs. After the task table 601 is updated, synchronization events occur twice a day, at 12:00 and 15:00.

[0093] According to this embodiment, by changing the execution interval of the synchronization task depending on the operating state of the node device, it is possible to synchronize with the node device while improving usability and reducing power consumption.

[0094] [Embodiment 7] Embodiment 7 of the present invention will be described with reference to the drawings. Matters common to the previously described embodiments will be simplified or omitted from the explanation. Embodiment 7 describes a procedure for resetting a different synchronization time when the communication time becomes insufficient due to wireless communication retransmission or the like during synchronization between the node device and the gateway device.

[0095] Figure 23 is a flowchart showing the processing flow performed by the gateway device 105. In step S211, the gateway device 105 sends the time to the node device 104, and then in step S212, it compares the hash value in the gateway device 105's node hash value table 801 with the hash value in the node information. If the hash value does not match that of the node device 104, the gateway device 105 checks in step S216 whether there is enough remaining synchronization time for the amount of data to be sent to the node device 104. Here, the remaining synchronization time is the synchronization interval with other node devices relative to the synchronization time allocated to each node device in the synchronization time table 1401. If the synchronization process overlaps with another synchronization time while one node device is synchronizing, delays in the synchronization process or radio interference may occur, so it is desirable to avoid overlapping synchronization processes. Therefore, in step S216, the gateway device 105 checks the remaining synchronization time from the current time and the next synchronization time, and if there is sufficient synchronization time, it sends the configuration information in step S213. On the other hand, if the synchronization time is insufficient in step S216, the gateway device 105 determines a different synchronization time. It transmits the updated synchronization time in step S217 and sends a synchronization completion message to the node device 104 in step S214. The node device 104 generates a synchronization event again at the updated synchronization time in step S217 and synchronizes with the gateway device 105.

[0096] According to this embodiment, the gateway device can synchronize with a node device by resetting a different synchronization time if the time interval between it and the synchronization time of another node device becomes insufficient during synchronization with the node device, thereby reducing the effects of delays in the synchronization process and radio interference.

[0097] [Other embodiments] It should be noted that the present invention is not limited to the embodiments and examples described above, and many modifications are possible within the technical concept of the present invention. For example, the different embodiments described above may be combined and implemented.

[0098] The information processing method and information processing device of the present invention can be applied to the management of various machines and equipment, such as industrial robots, service robots, and processing machines operated by computer numerical control, in addition to production equipment. For example, it can be applied to machines and equipment that can automatically perform movements such as extension and retraction, bending and straightening, vertical movement, horizontal movement, or rotation, or combinations thereof, based on information stored in a memory device provided in the control device.

[0099] Furthermore, an embodiment of the present invention may also include a method for manufacturing articles using a node device implementing the present invention, a gateway device capable of communicating with the node device, a management device, and a manufacturing device. When manufacturing articles, the input unit of the node device is connected to a sensor that acquires information related to the status of the manufacturing device, and in the measurement task, data acquired from the sensor is transmitted from the node device to the gateway device using the communication unit. Articles can be manufactured while monitoring the status of the manufacturing device over a long period of time without excessively draining the battery of the node device. An embodiment of the present invention also includes a manufacturing method in which articles are manufactured using production equipment while acquiring the status of the production equipment using the information processing system of the present invention.

[0100] Embodiments of the present invention also include a control program capable of executing the above-described information processing method or control method, and a recording medium readable by a computer storing the control program.

[0101] The present invention can also be realized by supplying a program that implements one or more of the functions of the embodiments to a system or device via a network or storage medium, and by having one or more processors in the computer of that system or device read and execute the program. It can also be realized by a circuit (e.g., an ASIC) that implements one or more functions. [Explanation of Symbols]

[0102] 101...Production equipment / 102, 103...Sensors / 104...Node devices / 105...Gateway devices / 106...Network / 107...Database / 108...Management devices / 109, 110...Communication means / 202...Event generation unit / 204...Signal input unit / 205...Processing unit / 206...Input / Output unit / 207...Wireless communication means / 208...Storage unit / 209...General-purpose input / output unit / 210...Battery / 211...Temperature sensor / 212...CPU / 302...Wireless communication means / 303...Storage device / 304...CPU / 305...Wired communication method / 601...Task table / 701...Table index / 801...Node hash value table / 905...Measurement data / 912...Synchronization data / 1004...Time synchronization data / 1012...Setting synchronization data / 1301...Radio wave strength threshold table / 1401...Synchronization time table / 1501...Synchronization settings screen / 1801...Task table / 1901...Battery voltage threshold table / 2101...Operation status table

Claims

1. A communication unit that can be connected to the sensor and can communicate with the gateway device, and a control unit; the control unit executes a first task of transmitting data acquired from the sensor to the gateway device using the communication unit, and executes a second task of transmitting information related to synchronization with the gateway device to the gateway device using the communication unit at a timing different from a timing at which the first task is executed. A node device comprising:

2. the control unit, after executing the first task, suspends the communication unit until executing the second task; 2. The node device according to claim 1,

3. The control unit controls the communication unit to a state in which a signal from the gateway device can be received after transmitting the information in the second task.

3. The node device according to claim 1, wherein the first and second nodes are connected to each other.

4. the control unit, after transmitting the information in the second task, acquires, from the gateway device via the communication unit, one or more of information related to a timing for executing the second task, time information, and a signal notifying completion of the second task.

4. The node device according to claim 1, wherein the first and second nodes are connected to each other.

5. the control unit ends the second task after a predetermined time has elapsed or after receiving a signal notifying the end of the second task from the gateway device after transmitting the information in the second task.

5. The node device according to claim 1, wherein the first and second nodes are connected to each other.

6. The control unit pauses the communication unit after the second task is completed.

6. The node device according to claim 1, wherein the first and second nodes are connected to each other.

7. the information to be transmitted in the second task includes one or more of a flag indicating that it is the second task, identification information of the node device, information related to a remaining battery level of the node device, information related to an internal temperature of the node device, and a hash value of the information; 7. The node device according to claim 1, wherein the first and second nodes are connected to each other.

8. the control unit executes the first task and the second task in accordance with an event condition included in a task table stored in a storage unit included in the node device.

8. The node device according to claim 1, wherein the first and second nodes are connected to each other.

9. the control unit, when the event condition related to the first task or the second task is not set in the task table, requests the gateway device to transmit the event condition using the communication unit.

9. The node device according to claim 8.

10. A node device according to any one of claims 1 to 9, A gateway device capable of communicating with the node device; A management device. A system characterized by:

11. When the gateway device does not receive the data at the timing when the first task is executed, or when the gateway device does not receive the information related to synchronization at the timing when the second task is executed, the gateway device notifies the management device. The system of claim 10.

12. The information transmitted by the node device in the second task includes a hash value of the information, The gateway device compares a hash value of the information received from the node device with a hash value stored in a storage unit of the gateway device; If they do not match, the setting information stored in the storage unit of the gateway device is transmitted to the node device, and the setting information stored in the node device is updated; If there is a match, a signal is transmitted to the node device to notify the completion of the second task.

12. The system according to claim 10 or 11.

13. the gateway device sets a timing for the node device to next execute the second task based on radio wave intensity at the time when the gateway device receives information related to synchronization from the node device; 13. The system according to any one of claims 10 to 12.

14. when the gateway device receives information related to a remaining battery level of the node device as information related to synchronization from the node device, the gateway device sets a timing for the node device to next execute the second task in accordance with the remaining battery level.

14. The system according to any one of claims 10 to 13.

15. the gateway device acquires information on whether the node device is in operation or adjustment, and sets an interval until the node device next executes the second task to be shorter when the node device is in adjustment than when the node device is in operation; 15. The system according to any one of claims 10 to 14.

16. A first node device and a second node device, each of which is a node device according to any one of claims 1 to 9, the gateway device adjusts an interval between a timing at which the first node device executes the second task and a timing at which the second node device executes the second task.

15. The system according to any one of claims 10 to 14.

17. A method for controlling a node device including a communication unit connectable to a sensor and capable of communicating with a gateway device, and a control unit, comprising: the control unit executes a first task of transmitting data acquired from the sensor to the gateway device using the communication unit, and executes a second task of transmitting information related to synchronization with the gateway device to the gateway device using the communication unit at a timing different from a timing at which the first task is executed. A method for controlling a node device comprising the steps of:

18. 10. A method for controlling a system including the node device according to claim 1, the gateway device capable of communicating with the node device, and a management device, comprising: When the gateway device has not received the data at the time when the first task is executed, or when the gateway device has not received the information related to synchronization at the time when the second task is executed, the gateway device notifies the management device.

23. A method for controlling a system comprising:

19. 10. A method for manufacturing an article using the node device according to claim 1, the gateway device capable of communicating with the node device, a management device, and a manufacturing device, the node device is connected to a sensor that acquires information related to a state of the manufacturing apparatus, and the node device transmits data acquired from the sensor in the first task to the gateway device using the communication unit; A method for producing an article comprising the steps of:

20. A control program for causing the control unit to execute the control method according to claim 17 or 18.

21. A computer-readable recording medium having the control program according to claim 20 recorded thereon.

Images