Wireless node

Abstract

To enhance visibility of a wireless node that is installed in a factory to connect industrial equipment to an industrial network.SOLUTION: A wireless node includes a circuit board on which a communication port for connection to an industrial device of an industrial network, a wireless module for connection to a wireless network, and a network control circuit for constructing the wireless network via the wireless module and transferring communication between the industrial device connected via the communication port and the wireless network are mounted, a housing for accommodating the vertically arranged circuit board, a first indicator light, and a control unit for controlling the lighting state of the first indicator light according to the state of the wireless network. The first indicator light outputs light in a first direction parallel to the normal direction of a first mounting surface of the circuit board, a second direction parallel to the normal direction of a second mounting surface of the circuit board, and a third direction parallel to the first mounting surface and the second mounting surface.SELECTED DRAWING: Figure 50

Description

[Technical field]

[0001] The present invention relates to a wireless node. [Background technology]

[0002] In a factory, multiple production devices such as machine tools are installed. By collecting and analyzing operation data from the multiple production devices, the production efficiency of the factory can be improved. According to Patent Document 1, a management server that wirelessly collects data from the multiple production devices is proposed. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2014-164598 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, in a factory, a large number of industrial devices are installed, pillars supporting the roof exist, and walls and the like are arranged to define a number of rooms. Furthermore, the inside of the factory may be dark. For this reason, it may not be easy to visually confirm where a number of wireless nodes are located in the factory.

[0005] Therefore, an object of the present invention is to improve the visibility of wireless nodes that are installed in a factory and connect industrial equipment to an industrial network. [Means for solving the problem]

[0006] The present invention relates to, for example, a communication port for connecting to an industrial device of an industrial network; a circuit board on which a wireless module for connecting to a wireless network and a network control circuit for constructing the wireless network via the wireless module and transferring communication between the industrial device connected via the communication port and the wireless network are mounted; a housing that houses the circuit board arranged vertically; a first direction parallel to a normal direction of the first mounting surface of the circuit board; a second direction parallel to a normal direction of the second mounting surface of the circuit board; a third direction parallel to the first mounting surface and the second mounting surface; a first indicator light that outputs light to the a control unit that controls a lighting state of the first indicator lamp in accordance with a state of the wireless network; The present invention provides a wireless node having a Effect of the Invention

[0007] According to the present invention, the visibility of wireless nodes that are installed in a factory and connect industrial devices to an industrial network is improved. [Brief description of the drawings]

[0008] [Figure 1] Diagram explaining a PLC system [Diagram 2] Diagram explaining PC hardware [Diagram 3] Diagram explaining PLC hardware [Figure 4] A diagram explaining the functions realized by a PC's CPU [Diagram 5] Diagram explaining the functions realized by the PLC CPU [Figure 6] Diagram explaining the user interface [Figure 7] Diagram explaining the user interface [Figure 8] Diagram explaining the notification dialog [Figure 9] Diagram explaining the analysis report [Figure 10] Diagram explaining the analysis report [Figure 11] Diagram explaining the user interface [Figure 12] Diagram explaining the analysis report [Figure 13] Diagram explaining the connection position of the master unit in an industrial wireless system [Figure 14] Diagram explaining industrial wireless systems [Figure 15] Diagram explaining the parent unit's hardware [Figure 16] Diagram explaining the functions of the parent unit [Figure 17] Diagram explaining the child unit hardware [Figure 18] Diagram explaining the functions of the child unit [Figure 19] Diagram explaining how to set up the parent unit [Figure 20] Flowchart explaining how to set up the parent unit [Figure 21] A diagram explaining the settings screen [Figure 22] A diagram explaining how a wired child unit is connected to a parent unit [Figure 23] Flowchart explaining how to register a wired device [Figure 24] Flowchart explaining the operation of the child unit [Diagram 25] A diagram showing the state in which wired child devices have created an industrial wireless network [Figure 26] A diagram showing the state before the wireless slave device is connected [Figure 27] A diagram explaining how to build a wireless network for adding a child device [Figure 28] A diagram explaining the addition of a wireless slave unit [Figure 29] A diagram illustrating an example in which multiple wireless slave devices are added at once. [Diagram 30] A diagram illustrating an example in which multiple wireless slave devices are added at once. [Diagram 31] A diagram explaining how multiple wireless slave devices have created a wireless network for adding additional slave devices. [Diagram 32]A diagram explaining how a wired device has joined a wireless network for adding devices [Diagram 33] Diagram explaining how multiple wireless slave devices join an industrial wireless network [Diagram 34] Flowchart explaining the operation of the parent unit [Diagram 35] Figure explaining the Add screen [Diagram 36] Figure explaining the Add screen [Figure 37] Diagram explaining the operation of existing child devices [Figure 38] Diagram explaining the operation of the child unit [Figure 39] Flowchart for explaining highlighting [Diagram 40] FIG. 1 shows a signal sequence for further processing. [Diagram 41] A diagram explaining the batch registration of multiple devices, including wired devices [Diagram 42] A diagram explaining the creation of an additional wireless network [Diagram 43] A diagram explaining the construction of an industrial wireless network [Diagram 44] FIG. 1 shows a signal sequence for further processing. [Diagram 45] Flowchart explaining the operation of the parent unit [Figure 46] Flowchart explaining the setting change process [Figure 47] Figure explaining the deletion screen [Figure 48] Flowchart for explaining deletion processing in the parent device [Figure 49] Flowchart for explaining the deletion process in the child device [Figure 50] FIG. 2 is a perspective view illustrating the housing of the child device. [Figure 51] Diagram explaining the bottom of the handset [Figure 52] Diagram explaining the structure of the indicator light [Figure 53] Diagram explaining the inside of the child unit [Figure 54] A diagram explaining the top surface of the inside of the handset [Figure 55] A cross-sectional view of the inside of the handset, illustrating the area around the indicator light [Figure 56] A diagram illustrating an attachment member for fixing the child unit. [Figure 57] A diagram illustrating an attachment member for fixing the child unit. [Figure 58] A diagram explaining the bottom surface of the child unit and the top panel of the mounting bracket. [Figure 59] FIG. 1 is a diagram illustrating a driver circuit for a plurality of light-emitting elements. [Figure 60] A diagram showing how mesh clusters are identified by different lighting colors. [Figure 61] A diagram explaining how to indicate the communication partner using an indicator light [Figure 62] A diagram explaining how to indicate the communication partner using an indicator light [Figure 63] A diagram explaining direct wave communication and indirect wave communication. [Figure 64] A diagram explaining how to create a layout map using a network camera. [Figure 65] Diagram illustrating a PLC link built on an industrial wireless network DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, the embodiments will be described in detail with reference to the accompanying drawings. Note that the following embodiments do not limit the invention according to the claims, and not all combinations of features described in the embodiments are essential to the invention. Two or more features among the multiple features described in the embodiments may be arbitrarily combined. In addition, the same reference numbers are used for the same or similar configurations, and duplicated descriptions are omitted.

[0010] A programmable logic controller (PLC) is a controller that controls industrial machines such as manufacturing equipment, conveying equipment, and inspection equipment in factory automation. PLCs control various extension units and controlled devices by executing user programs such as ladder programs created by programmers. In order to monitor the operation of a PLC, it has been proposed to collect data held by the PLC and monitor the data on a computer (PC) or HMI (human interface: display device) connected externally to the PLC (JP Patent Publication No. 2019-016325).

[0011] By the way, a user creates a user program using a program creation support device and transfers it to a PLC. The PLC actually executes the user program to manufacture various products. Here, a rare event that was not anticipated when the user program was created may occur, causing the production line to stop. Although the production line will not stop, an event that requires attention may occur. On the other hand, when a certain event occurs, the PLC reads out the device values ​​collected before and after the occurrence time from the buffer and records them. This may be called an operation record (operation log). The data utilization unit may analyze this record, create an analysis report, and provide it to a Web browser outside the PLC. Here, if the operation log can be played back together with the analysis report, the user will not only be able to easily understand the contents of the analysis report, but will also be able to easily identify the cause of the occurrence of the certain event. Therefore, the analysis report and the operation log will need to be linked. If the analysis report and the operation log are not linked, it will be difficult for the user to identify the operation log corresponding to the analysis report. Therefore, some of the following embodiments aim to appropriately maintain the relationship between the operation record and the analysis result in the PLC.

[0012] <System configuration> First, in order to allow those skilled in the art to better understand programmable logic controllers (PLCs, which may also be simply called programmable controllers), the configuration and operation of a typical PLC will be described.

[0013] FIG. 1 is a conceptual diagram showing an example of a configuration of a PLC system according to an embodiment of the present invention. As shown in FIG. 1, the PLC system includes a PC 2 for editing a user program such as a ladder program, and a PLC 1 for controlling various industrial machines installed in a factory or the like. PC is an abbreviation for personal computer. The user program may be created using a graphical programming language such as a ladder language or a motion program in a flow chart format such as SFC (Sequential Function Chart), or may be created using a high-level programming language such as C language. In the following, for convenience of explanation, it is assumed that the user program executed by the basic unit 3 is a ladder program. The PLC 1 includes a basic unit 3 with a built-in CPU, and one or more expansion units 4. One or more expansion units 4 are detachable from the basic unit 3.

[0014] The basic unit 3 includes a display unit 5 and an operation unit 6. The display unit 5 can display the operating status of the basic unit 3 or the expansion unit 4 attached to the basic unit 3. The display unit 5 switches the display content according to the operation content by the user on the operation unit 6. The display unit 5 usually displays the current value (device value) stored in the device in the PLC 1 and error information generated in the PLC 1. A device is a name (symbol) that indicates a storage area in memory provided to store device values ​​(device data), and may also be called a device memory. A device value is information that indicates the input state from an input device, the output state to an output device, and the state of an internal relay (auxiliary relay), timer, counter, data memory, etc. that are set on a user program. There are two types of device values: bit type and word type. A bit device stores a device value of 1 bit. A word device stores a device value of 1 word.

[0015] The expansion unit 4 is provided to expand the functions of the PLC 1. A field device (controlled device) 10 corresponding to the function of the expansion unit 4 may be connected to the expansion unit 4, and each field device 10 is thereby connected to the basic unit 3 via the expansion unit 4. The field device 10 may be an input device such as a sensor or a camera, or an output device such as an actuator. In addition, multiple field devices may be connected to one expansion unit 4.

[0016] For example, the extension unit 4b may be a positioning unit that drives a motor (field device 10) to position a workpiece, or may be a counter unit that counts signals from an encoder (field device 10) such as a manual pulsar.

[0017] The expansion unit 4a collects symbol values ​​from symbols (devices, variables, etc.) in the basic unit 3, analyzes the symbol values, and creates an analysis report including the analysis results. The expansion unit 4a may have a Web server that provides the analysis report to an external PC 2. The basic unit 3 may also be called a CPU unit. In this embodiment, an example is described in which the expansion unit (analysis unit) 4a has a collection unit that collects symbol values. However, the collection unit may be provided in the basic unit 3 or in another expansion unit. In addition, the expansion unit 4a may function as an analysis device that analyzes the collected data according to an instruction from the basic unit 3 or a predetermined timing. In this embodiment, an example is described in which the expansion unit 4a functions as an analysis device. However, there is no intention to limit the present invention. The basic unit 3 may function as the analysis device, or an external device such as the PC 2 may function as the analysis device. A system including the PLC 1 and the PC 2 may be called a programmable logic controller system.

[0018] The PC2 is a computer operated mainly by a programmer. The PC2 may be called a program creation support device (monitoring device). The PC2 is, for example, a portable notebook or tablet type personal computer or a smartphone, and is an external computer equipped with a display unit 7 and an operation unit 8. The external computer is a computer outside the PLC1. A ladder program, which is an example of a user program for controlling the PLC1, is created using the PC2. The created ladder program is converted into a mnemonic code in the PC2. The PC2 is connected to the basic unit 3 of the PLC1 via a communication cable 9a such as a USB (Universal Serial Bus) cable. However, the communication cable 9a may be a network cable similar to the communication cable 9b. The PC2 may be a programmable display whose screen is set by the user. In this case, the screen for displaying the analysis results and the like may be set by the user. The programmable display may be equipped with a Web browser function, and the analysis results and the like may be displayed by the Web browser function.

[0019] Although not shown in Fig. 1, the operation unit 8 of the PC 2 may include a pointing device such as a mouse connected to the PC 2. The PC 2 may be detachably connected to the base unit 3 or the expansion unit 4a of the PLC 1 via a communication cable 9b other than a USB cable. The communication cable 9b may be a so-called LAN cable. The PC 2 may be connected to the base unit 3 of the PLC 1 by wireless communication without using the communication cables 9a and 9b.

[0020] <Program creation support device> FIG. 2 is a block diagram for explaining the electrical configuration of the PC 2. As shown in FIG. 2, the PC 2 includes a CPU 11, a display unit 7, an operation unit 8, a storage device 12, and communication units 13a and 13b. The display unit 7, the operation unit 8, the storage device 12, and the communication units 13a and 13b are each electrically connected to the CPU 11. The storage device 12 includes a RAM, a ROM, an HDD, and an SSD, and may further include a removable memory card. CPU is an abbreviation for central processing unit. ROM is an abbreviation for read-only memory. RAM is an abbreviation for random access memory. HDD is an abbreviation for hard disk drive. SSD is an abbreviation for solid state drive.

[0021] A user of the PC 2 causes the CPU 11 to execute the project editing program 14a stored in the storage device 12, and edits the project data through the operation unit 8. In other words, the PC 2 is an engineering tool and also functions as a program creation support device. The project data includes one or more user programs (e.g., ladder program) and configuration information of the base unit 3 and the expansion unit 4. The configuration information includes information indicating the connection positions of the multiple expansion units 4 relative to the base unit 3, information indicating the functions of the base unit 3 (e.g., communication function and positioning function), information indicating the functions of the expansion unit 4 (e.g., photography function), and device allocation information. Here, editing of the project data includes creation and modification (re-editing) of the project data. The user reads out the project data stored in the storage device 12 as necessary, and modifies the project data using the project editing program 14a. The communication unit 13a communicates with the base unit 3 via the communication cable 9a. The CPU 11 transfers the project data to the base unit 3 via the communication unit 13a. The communication unit 13a includes a communication circuit capable of performing communication in accordance with the USB standard. The communication unit 13b communicates with the extension unit 4a via the communication cable 9b. The communication unit 13b includes a network communication circuit. The Web server program 14c is implemented as a part of the project editing program 14a. The Web browser program 14d receives an analysis report written in a Web format by the extension unit 4a via the communication unit 13a and displays it on the display unit 7. The Web browser program 14d may request the Web server program 14c to provide the analysis report. The Web server program 14c may access the extension unit 4a via the communication unit 13a and the basic unit 3, obtain the analysis report, and transfer it to the Web browser program 14d.

[0022] <plc> FIG. 3 is a block diagram for explaining the electrical configuration of the PLC 1. As shown in FIG. 3, the basic unit 3 includes a CPU 31, a display unit 5, an operation unit 6, a storage device 32, and a communication unit 33. The display unit 5, the operation unit 6, the storage device 32, and the communication unit 33 are each electrically connected to the CPU 31. The storage device 32 may include a RAM, a ROM, a memory card, and the like. The storage device 32 has a plurality of storage areas such as a device unit 34, a project storage unit 35, a ring buffer 36, and an operation record storage unit 37. The device unit 34 has a bit device, a word device, and the like, and each device stores a device value. The project storage unit 35 stores project data transferred from the PC 2. The ring buffer 36 periodically collects and stores device values ​​from the device unit 34. When a predetermined event occurs, the operation record storage unit 37 stores an event record including device values ​​collected around the time of occurrence (before, after, or around the time of occurrence) and the time of collection. An event means, for example, that an alarm condition or a caution condition set for each device is satisfied. An alarm condition means, for example, a condition that the control operation of the production line by the PLC1 should be stopped. An caution condition means, for example, a condition of a device value that the administrator should be careful about regarding the control operation of the production line by the PLC1. The CPU 41 transmits an event record to the PC2 in response to a request from the PC2. The CPU 31 may also provide the PC2 with a device value in real time. The storage device 32 also stores a control program executed by the CPU 31 of the basic unit 3. As shown in FIG. 3, the basic unit 3 and the expansion unit 4 are connected via a unit internal bus 90, which is a type of expansion bus. Note that a communication function related to the unit internal bus 90 is implemented in the CPU 31, but may be implemented as a part of the communication unit 33. The communication unit 33 may have a serial communication circuit conforming to the USB standard or the like. The CPU 31 receives project data from the PC2 via the communication unit 33. Note that the ring buffer 36 and the operation record storage unit 37 described above may be provided in the expansion unit 4a or 4b.In this case, the CPU 31 of the basic unit 3 may read out the device values ​​periodically updated by the device section 34 and transfer them to a ring buffer provided in the expansion unit 4a or 4b. If the expansion unit 4a or 4b is provided with an operation record storage section, the CPU 31 may transfer the device values ​​collected in the ring buffer to the expansion unit 4a or 4b and store them when a predetermined event occurs. In this way, some or all of the functions of the CPU 31 may be performed by the CPU 41a or CPU 41b.

[0023] Here, a supplementary explanation will be given about the unit internal bus 90. This unit internal bus 90 is a communication bus used for input / output refresh. Input / output refresh is a process for updating device values ​​between the basic unit 3 and the expansion unit 4. Input / output refresh is performed each time a ladder program is executed (i.e., each scan).

[0024] The operation record (such as device values ​​and their collection times) recorded in the operation record storage unit 37 may be a record of the operation state of the PLC1 at the scan time level. For example, the operation record may be a record of the symbol values ​​of all symbols related to the operation of the PLC1 and their collection times in chronological order for each scan. All symbols related to the operation may be, for example, all symbols used in a user program such as a ladder program, or all symbols included in a program unit or unit unit selected by the user. In this case, the symbols to be the subject of the operation record may be selected collectively in a significant unit such as a program unit or unit unit. The symbols to be the subject of the operation record may be added or removed individually. For example, when a trouble occurs, an operation record may be generated in which the symbol values ​​of all symbols related to the operation of the PLC1 around the time of the trouble occurrence and their collection times are recorded in chronological order for each scan. The user will be able to accurately grasp what happened when the trouble occurred based on the operation record even later. The operation record may contain a lot of information to reproduce the situation at that time. If there is a lot of information, the data volume of the driving record will be large, making it difficult to handle the driving record (data processing, etc.) and putting a burden on collecting the driving record. Therefore, the symbols to be collected can be selected by the user on a program or unit basis.

[0025] In addition to symbols, the operation record may also include a time series of camera images along with the time of capture. This allows the user to accurately grasp what happened around the time of the occurrence of a problem, for example, even after the problem has occurred. In particular, the inclusion of camera images showing the external changes of the equipment in the operation record will be useful in grasping the situation. For this reason, the camera images may be recorded in conjunction with the time series of the execution of the user program. The write history from external devices such as HMI (human machine interface) and PCs, and the write history from PLCs may also be included in the operation record as change point events. This allows the user to check, for example, what change point events occurred before and after the occurrence of a problem in chronological order.

[0026] From another perspective, the operation record may be called a collective term for data for each scan time, such as devices, buffer memory of the expansion unit 4, variables, etc., that are saved in response to the establishment of the save trigger condition. The operation record may include video data acquired by the expansion unit (camera unit) for each frame, that is saved in response to the establishment of the save trigger condition. The operation record may also include an event history, such as errors and device value changes, that is saved in response to the establishment of the save trigger condition. Furthermore, the operation record may include a ladder program (project data) that was being executed when the save trigger condition was established. By including the project data at the time when the operation record was generated in the operation record, even if there are multiple versions of the project data, the situation can be reproduced by the project data that was actually used when the operation record was generated. The operation record may also include an analysis report.

[0027] The expansion unit 4 includes a CPU 41 and a memory 42. The CPU 41b of the expansion unit 4b controls the field device 10 according to instructions (device values) from the basic unit 3 stored in the device. The CPU 41b also stores the control results of the field device 10 in a device called a buffer memory. The control results stored in the device are transferred to the basic unit 3 by input / output refresh. The control results stored in the device may also be transferred to the basic unit 3 in accordance with a read command from the basic unit 3, even at a timing different from the input / output refresh. The memory 42 includes a RAM, a ROM, and the like. In particular, a storage area used as a buffer memory is secured in the RAM. The memory 42 may include a buffer that temporarily holds data (e.g., still image data or video data) acquired by the field device 10.

[0028] The CPU 41a of the extension unit 4a functioning as a data utilization unit (analysis unit) communicates with the PC 2 via the communication unit 43 and the communication cable 9b. The communication unit 43 includes a communication circuit that executes network communication. The CPU 41a executes a data utilization program stored in the memory 42a, and creates an analysis report including the analysis results by analyzing device values ​​collected in the basic unit 3. When a driving record analysis application is set as a data utilization application, the CPU 41a creates an analysis report including the analysis results by analyzing device values ​​collected in the basic unit 3. For example, the CPU 41a analyzes symbol values ​​included in the driving record data to identify abnormal symbols and the time at which the symbols became abnormal, and creates an analysis report including analysis results in which the abnormal symbols are associated with the time at which the symbols became abnormal. The driving record data includes information for reproducing the situation around the time at which a driving record storage event occurred. Therefore, the driving record data may be managed in association with the analysis report. Furthermore, the driving record data includes symbol values ​​of many symbols for reproducing the situation around the time at which a driving record storage event occurred. Therefore, the data size of the driving record data is likely to be large. For example, the CPU 41a may read data necessary for an analysis report from the driving record data, and additionally store it as data for the analysis report in the driving record data. Here, additional storage refers to, for example, reading data necessary for the analysis report from the driving record data, copying it, and tagging the copied data to create data for the analysis report, and additionally storing it in the driving record data. Applying data processing such as tagging the data in this way makes it easier to create the analysis report.

[0029] The driving record data may include camera images. In this case, by playing back the camera images, the user can grasp the situation around the time when the driving record storage event occurred in more detail. The analysis report may include a UI (user interface) for playing back the camera images. The camera images have a large data size. Therefore, only the necessary camera image data may be partially downloaded when, for example, a click or scroll operation is accepted in the UI for playing back the camera images. For example, when creating the analysis report, the CPU 41a may process the camera images in accordance with the display order in the analysis report, or generate index information indicating the correspondence between the time and the storage position of the camera images. In this way, the CPU 41a may quickly and partially download the camera images corresponding to the display time (the time of the internal clock for playback).

[0030] In a narrow sense, the analysis report means the analysis result itself, but in a broad sense, it may mean a Web application that displays the analysis result and its user interface. For example, the CPU 41a judges whether the device value is within a normal range, whether the timing at which the device value changes is within a normal range, and the like. Whether the timing at which the device value changes is within a normal range may be, for example, whether the length of the period during which the device value is "1" (ON) is within a normal range. It may also be judged whether the number of times the device value changes in a certain process or cycle is within a normal range. If the device value collected from a certain device does not satisfy the normal condition, the device may be called an abnormal device as a device that behaves differently than usual. The CPU 41a may create an analysis report in a Web format and provide the analysis report to the Web browser of the PC 2 via the communication unit 43 and the communication cable 9b. If the CPU 31 has a protocol conversion function, the CPU 41a may transmit the analysis report to the PC 2 via the unit internal bus 90, the CPU 31, the communication unit 33, and the communication cable 9a. The analysis report may have a graph display component, a numerical value display component, and the like. These display components are realized by markup data (e.g. HTML data) that describes the front-end structure, style data (e.g. CSS data) that describes decoration, and code (e.g. JavaScript (registered trademark) code) that describes dynamic processing. HTML is an abbreviation for HyperText Markup Language. CSS is an abbreviation for Cascading Style Sheets.

[0031] FIG. 4 is a diagram for explaining functions realized by the CPU 11 of the PC 2. The project editing unit 50 is a function realized by the CPU 11 executing the project editing program 14a. The project editing unit 50 creates project data including a user program according to a user instruction input through the operation unit 8. The Web server 51 communicates with the Web browser 60 according to HTTP (Hypertext Transfer Protocol) and provides display components to the Web browser 60. The protocol conversion unit 52 converts HTTP into a predetermined communication protocol. The predetermined communication protocol is a communication protocol used in communication between the communication unit 13a and the communication unit 33. For example, when the Web browser 60 requests an analysis report by an HTTP request, the Web server 51 passes the HTTP request to the protocol conversion unit 52. The HTTP request includes a URL (Uniform Resource Locator) of the extension unit 4a (Web server) that is executed by the CPU 41a and provides the analysis report. The protocol conversion unit 52 encapsulates the HTTP request and converts it into a request signal (command) that can be transmitted by the predetermined communication protocol. This request signal is passed to the CPU 31 of the basic unit 3, and further to the CPU 41a of the extension unit 4a. The CPU 41a returns the analysis report to the CPU 11 via the CPU 31. The Web server 51 of the CPU 11 passes the analysis report to the Web browser 60. As a result, the Web browser 60 displays the analysis report on the display unit 7.

[0032] The download unit 53 downloads the operation records and the like from the basic unit 3 and stores them in the storage device 12. The debug unit 54 debugs the user program and displays the debug results on the display unit 7. The ladder monitor unit 56 acquires values ​​stored in symbols described in the user program from the operation records and highlights the values ​​for the symbols in the user program. For example, the device values ​​acquired from the operation records may be displayed in association with devices drawn in the ladder diagram of the ladder program. The relationship map unit 55 creates a relationship map showing devices related to abnormal devices displayed in the analysis report and displays it on the display unit 7. An abnormal device is a device whose device value does not satisfy the normal condition or whose device value change timing does not satisfy the normal condition. The relationship map is, for example, a UI that visually shows the relationship between a device (input device) that has an effect on an abnormal device and the abnormal device. The relationship map may also display the relationship between a device (output device) that is affected by the abnormal device and the abnormal device. The debug unit 54 acquires the abnormal device and its associated device by analyzing the ladder program and creates a relationship map.

[0033] The reception unit 57 receives an editing operation for a user program and an operation for a debug process. The notification processing unit 58 acquires whether a notification has been issued in the PLC 1 by polling, and displays the acquired notification on the display unit 7. An example of the notification is that the creation of an analysis report has been completed. The replay unit 59 causes the download unit 53 to download the driving record and store it in the storage device 12 in response to a replay request input from the reception unit 57 or the linking unit 64. The replay request may include, for example, identification information that can identify the driving record (e.g., unique identification information or a storage path name in the PLC 1). The replay unit 59 replays the driving record stored in the storage device 12 and displays it on the display unit 7. The replay unit 59 may have a ladder monitor unit 56 instead of the debug unit 54. Alternatively, the replay unit 59 may be included in the debug unit 54. The replay unit 59 may display the time-series device values ​​acquired in real time from the PLC 1 as waveforms, or may display the time-series device values ​​included in the driving record as waveforms.

[0034] The Web browser 60 may display the analysis report on the display unit 7 by executing the Web application 61. The Web application 61 is composed of, for example, HTML data, CSS data, and java(R) script. The Web application 61 may be provided from the extension unit 4a. The communication processing unit 62 processes communication with the Web server 51. The data acquisition unit 63 acquires the driving record to be displayed in the analysis report from the project editing unit 50. It is assumed that the driving record has already been saved in the storage device 12 by the download unit 53. The linking unit 64 passes designation information indicating the device or the like designated or selected by the user in the analysis report to the debugging unit 54 or the like. This enables the debugging unit 54 to display a relationship map of the non-normal device designated in the analysis report, or to display a portion in the ladder program in which the non-normal device is described. The user can easily edit the ladder program with respect to the non-normal device. The drawing unit 65 displays the analysis report on the display unit 7. Furthermore, the linking unit 64 performs time management so that the playback time (selection time) in the analysis report and the playback time of the driving record in the project editing unit 50 are synchronized.

[0035] FIG. 5 shows functions that are realized by the CPU 31 and the CPU 41a executing a control program in the PLC 1. In the CPU 31, the command processing unit 71 interprets a command received from the PC 2 and executes a process corresponding to the interpretation result. For example, when a request signal created by encapsulating an HTTP request is received, the command processing unit 71 transfers the request signal to the CPU 41a. When a response signal to the request signal is received from the CPU 41a, the command processing unit 71 transfers the response signal to the PC 2. The collection unit 72 collects symbol values ​​(device values ​​and values ​​stored in variables) from the basic unit 3 and the expansion unit 4b and stores them in the ring buffer 36. The logging unit 73 determines whether any error or trouble (abnormal event) has occurred in the PLC 1 based on the collected symbol values, etc. For example, the logging unit 73 may determine whether the collected symbol values ​​meet the recording conditions. When the collected symbol values ​​meet the recording conditions, the logging unit 73 saves the symbol values ​​as an operation log 76 in the operation record 74. For example, the logging unit 73 creates a folder for storing the driving record 74, and saves the operation log 76 therein. The logging unit 73 reads out from the project storage unit 35 the project data 75 that was being executed when the driving record was created, and saves it in the driving record 74. Furthermore, the logging unit 73 notifies the analysis unit 83 that the driving record 74 has been created.

[0036] The CPU 31 or the CPU 41a may have a setting unit for setting a control cycle to be used for generating a learning model, analysis, and generating an analysis report, which will be described later, according to an input from an operator. The control cycle is set by specifying a reference timing for the cycle. The setting of the control cycle may be called a cycle setting. For example, the cycle setting includes a symbol name that specifies the start timing of the cycle, and rising / falling edge information of the symbol value. The cycle setting may include setting information for the start timing of the cycle based on the symbol name that specifies the start timing of the cycle, and rising / falling edge information of the symbol value, and setting information for the end timing of the cycle based on the symbol name that specifies the end timing of the cycle, and rising / falling edge information of the symbol value. The setting of the control cycle by the setting unit may be provided to the PLC 1 in a file format such as CSV, and the setting unit may set the control cycle by reading the file such as CSV. For example, the control cycle set by the setting unit is used to classify devices that are synchronized with the cycle and add the classification information to a model as attribute information, to narrow down devices to be analyzed by the control cycle, and to generate an analysis report that is displayed in synchronization with the control cycle. A plurality of control cycles may be set. Also, the control cycle does not necessarily have to be set. For example, if possible values ​​of a symbol value in a normal state are predetermined, whether or not the symbol value is an abnormal symbol may be determined by determining whether or not the symbol value is one of the possible values ​​determined in advance.

[0037] In the CPU 41a, the protocol conversion unit 81 converts the protocol of the HTTP request encapsulated and transferred from the PC 2 via the CPU 31 and extracts it from the request signal. The protocol conversion unit 81 encapsulates response information transmitted from the Web server 82 in response to the HTTP request and passes it to the CPU 31. In the following, the Web browser 60 of the PC 2 and the Web server 82 of the extension unit 4a can also communicate indirectly via the Web server 51, the protocol conversion units 52 and 81, the command processing unit 71, and the like in the PC 2. The protocol conversion units 52 and 81 may provide a transparent tunnel (e.g., a TCP tunnel). The Web server 82 provides the PC 2 with an analysis report created by the analysis unit 83. The analysis unit 83 analyzes the operation log 76 in the driving record 74, creates an analysis result 77, and passes it to the logging unit 73. When the analysis unit 83 creates the analysis result 77, the logging unit 73 adds it to the driving record 74 including the analysis result 77 in addition to the project data 75 and the operation log 76. The driving record 74 is stored in the driving record storage unit 37. In this way, the operation record 74 stores the project data 75, the operation log 76, and the analysis result 77 associated with each other when an abnormal event occurs in the PLC1, so that the state of the PLC1 when the abnormal event occurs can be easily reproduced. For example, by visually reproducing the change in the device value on the ladder diagram, the user can easily debug the ladder program. In particular, when the project data stored in the PC2 is used, it may be difficult to accurately reproduce the state of the PLC1 when an abnormal event occurs. This is because the project data stored in the PC2 and the project data 75 executed in the PLC1 when the abnormal event occurs may not match. Therefore, the project data 75 executed in the PLC1 when the abnormal event occurs is stored in the operation record 74. When the analysis result 77 is issued, the notification issuing unit 84 issues a notification. This notification is sent to the CPU 11.

[0038] <User Interface (UI)> 6 and 7 show the UI 100 of the project editing program 14a displayed on the display unit 7 (the UI 100 is displayed on the display unit 7 by executing the project editing program 14a). The mode selection menu 101 displays a plurality of modes provided in the project editing program 14a in a selectable manner. The plurality of modes include an edit mode, a monitor mode, a replay mode (debug mode), and the like. The edit mode shown in FIG. 6 is a mode for editing a ladder program displayed in the program display area 104. The project display area 102 displays information constituting the project. This information includes specification information and setting information of the basic unit 3 and the extension unit 4 constituting the PLC 1, device allocation information, setting information of the operation record, a ladder program, and the like. In the edit mode, the program display area 104 displays the ladder program specified in the project display area 102 in an editable manner. In FIG. 6, a ladder program having program modules named an input unit, an output unit, and a machining unit state is displayed. In particular, a plurality of program modules can be selected by a tab 107, and in FIG. 6, the tab 107 corresponding to the input unit is selected.

[0039] The monitor mode is a mode that waits for a notification issued by the PLC 1. When the extension unit 4a issues a notification indicating that an analysis result has been created, the CPU 11 displays a dialog for displaying the notification on the display unit 7. The user interface of the monitor mode is basically the same as that of the edit mode.

[0040] 8 shows the notification dialog 108. The notification dialog 108 displays the name of the application or function that issued the notification, the content of the notification, the number of notifications that occurred, the date and time when the notification occurred, etc. The notification information for displaying the notification dialog 108 includes the URL of the analysis report. When the display button 109 is pressed, the CPU 11 passes the URL of the analysis report to the Web browser 60. As a result, the Web browser 60 accesses the Web server specified by the URL, obtains the display data of the analysis report (Web application 61), and displays the analysis report.

[0041] 7, the replay mode is a mode in which the operation record is reproduced on a ladder program and the operation record is displayed as a waveform. The pointer 103 moves in conjunction with a user operation on the operation unit 8, and is used to press down a button or to select an object. For example, when an analysis report displayed in the project display area 102 is double-clicked by the pointer 103, the CPU 11 causes the Web browser 60 to display the analysis report.

[0042] In replay mode, device values ​​included in the operation record are displayed on the ladder program in the program display area 104. In the case of a relay device (bit device), the device value is displayed so that it is visually distinguishable between 0 and 1. Visually distinguishable includes display in different colors or different icons. In the case of a word device, for example, the device value may be displayed after being decimalized. Other numeric display formats, such as device values ​​after being decimalized, may also be adopted.

[0043] Since the device values ​​are time-series data that may change over time, each device value is linked to time information that indicates the time at which it was collected. The seek bar 105a indicates the playback time of the device values, and may be operated by the pointer 103 to specify the playback time. During playback of the driving record, the seek bar 105a moves from left to right in conjunction with the passage of the playback time. The time specification unit 106a is a control object for instructing to advance or rewind the playback time, to start automatic playback, or to stop playback.

[0044] [Analysis Report] 9 shows an analysis report 110 displayed on the display unit 7 by the Web browser 60 executing the Web application 61. The analysis report 110 is displayed on the display unit 7 together with the UI 100 of the project editing program 14a. That is, the UI 100 and the analysis report 110 are displayed as separate windows. However, the UI 100 and the analysis report 110 may be displayed in a single window. The analysis report 110 may be displayed on the display unit 7, or on another display device such as a programmable display device, a tablet, or a smartphone.

[0045] The detection map 111 displays the start timing and end timing for each of a plurality of processes executed in the PLC1. In general, the period from the start timing to the end timing is called a cycle. In FIG. 9, a rectangle extending horizontally indicates a period (cycle) during which a process is being executed. The left of this rectangle indicates the older one, and the right indicates the newer one. The time bar 112a indicates the timing when a save trigger for the driving record data occurred. As described above, the driving record data holds data collected before the timing when the save trigger occurred and data collected after this timing. Therefore, data is shown before and after the time bar 112a. Meanwhile, the time bar 112e indicates the selected time, and can be moved to a desired time (left and right) by a drag operation or a drag-and-drop operation by the user. Instead of drag-and-drop, the time bar 112e may be configured to jump to a desired position when the user clicks on the desired position on the detection map. In this way, the user can update the display of the analysis result by operating the time bar 112e. In accordance with the operation of the time bar 112e, at least one or all of the detection list 114, the image display area 113, and the analysis comment 116, which will be described later, may be updated in conjunction with each other (time-synchronized) to display the corresponding analysis result. The time bars 112a and 112e may be drawn in different colors, or may be drawn with solid and dashed lines. This improves the distinguishability of the time bars 112a and 112e.

[0046] Here, two circles are written in step 1 of the detection map 111, which indicate the timing when the detection target devices became in an unusual state. The circle on the left indicates the timing when devices R001 and MR001 became in an unusual state (both at 14:50:45). The circle on the right indicates the timing when device R004 became in an unusual state (14:59:01). Fig. 9 shows a state in which the user has selected the device column for R004 in the detection list 114, and the time bar 112e of the detection map 111 is displayed at a position overlapping with the circle on the right.

[0047] The display position of the time bar 112e on the detection map 111 is linked to the user's device selection in the detection list 114. When the device field of MR001 is selected (clicked) in the state shown in Fig. 9, MR001 is highlighted as shown in Fig. 10, and the time bar 112e on the detection map 111 moves to a position overlapping with the leftmost circle of the two circles (the same applies when the device field of R001 is selected). In addition, in response to the movement of the time bar 112e, the time bar 112f on the detection list also moves up by one (linked).

[0048] An abnormal state is, for example, when a device value deviates from a normal range, or when the timing or frequency of a device value change deviates from the normal range. In a manufacturing factory, the same products are mass-produced every day. In other words, the same process is repeated many times. Therefore, detecting and displaying an abnormal state is very useful for improving a ladder program or reviewing production equipment. The normal range (normal condition) that defines the normal state (normal state) may be defined by master data or by the learning results of device values. In the detection map 111, the rectangle indicating the process moves from right to left as time passes (as described above, the left is older and the right is newer).

[0049] The image display area 113 displays the camera image acquired by the PLC1. The camera image may also be included in the driving record. In FIG. 9, the camera image of the master data and the current camera image are displayed so as to be contrasted. Since the camera image is also time-series data, the seek bar 105b indicates the playback time of the camera image and moves from left to right as the playback time progresses. The time bar 112b indicates the selected time, and in FIG. 9, indicates the timing when the detection target device R004 became in a different state from usual. The time designation unit 106b is a control object for instructing to advance the playback time of the camera image, to return the playback time, to start playback, and to stop playback. The link unit 64 and the playback unit 59 manage the playback time of the detection map 111, the playback time of the camera image, and the playback time in the UI 100 so as to be synchronized. As a result, the playback time in the UI 100 and the playback time in the analysis report 110 match.

[0050] The detection list 114 indicates the device that has become in an unusual state and the time when the state occurred (the time when the device value was collected). When the CPU 11 detects a click on a device displayed in the detection list 114, the CPU 11 may switch the operation mode of the project editing unit 50 to the replay mode. The CPU 11 passes the identification information of the clicked device, the playback time information (the time when the device value was collected), and the information (such as the storage path) that specifies the driving record that was the subject of analysis to the debugging unit 54. As a result, the replay mode is started using the driving record that was the subject of analysis, and at that time, the playback time of the analysis report 110 and the playback time information of the project editing unit 50 are synchronized. As a result, as shown in FIG. 7, the driving record 74 is played back in association with the ladder program. Note that FIG. 7 corresponds to a display screen when the replay mode of the UI 100 is started with the device R004 selected in the detection list 114 of FIG. 9. The seek bar 105a in FIG. 7 indicates the time (14:59:01) when the device R004 became in an unusual state. Furthermore, in the program display area 104, the state of each device at this time (14:59:01) is displayed so as to be visually distinguishable. Note that the project editing unit 50 may already be operating in the replay mode before the analysis report 110 is displayed. In this case, when an abnormal device is selected in the analysis report 110, the CPU 11 may pass the time at which the abnormal state (an event different from usual) occurred to the project editing unit 50, and the project editing unit 50 may read out the device value synchronized with that time from the storage device 12 and display the device value on the ladder program.

[0051] 9, the time bar 112c indicates the timing (14:59:06) when the drive record data save trigger occurred. As described above, the time bar 112f is linked to the time indicated by the time bar 112e in the detection map 111. For example, when the time bar 112e is moved leftward from the left circle, the time bar 112f in the detection list 114 moves to a position overlapping with the top line of the device column for R001.

[0052] 10 and 11 are explanatory diagrams for explaining how the analysis report 110 (FIG. 9) and the UI 100 (FIG. 7) of the project editing program 14a are linked together. As described above, FIG. 7 corresponds to the display screen when the replay mode of the UI 100 is started with the device R004 selected in the detection list 114 of FIG. 9.

[0053] 10, when the user selects (clicks) MR001 in the detection list 114, the time bar 112e moves accordingly in the detection map 111. As the time bar 112e moves, the time bar 112f also moves up by one. As the time bar 112e moves, the time bar 112b in the image display area 113 also moves to the left (linked display). Furthermore, the display of the analysis comment 116 described later also changes in response to the selection of MR001. Details will be described later.

[0054] On the other hand, as shown in Fig. 11, the seek bar 105a moves slightly to the left (earlier in time) than in Fig. 7. At this time, the seek bar 105a indicates the time (14:50:45) when the device MR001 became in an unusual state. In this way, the linking unit 64 displays the time specified by the time bar 112e and the time bar 112f of the analysis report 110 in synchronization with the playback time of the driving record (the time specified by the seek bar 105a).

[0055] Note that Figures 10 and 11 explain the linked display when the UI100 of the project editing program 14a has been launched in advance. However, for example, if the UI100 is launched after the device column for MR001 has been selected in the detection list 114 of the analysis report 110, the UI100 will be launched in the changed state shown in Figures 10 and 11.

[0056] Also, in FIG. 10, the user selects one device from the detection list 114, but multiple devices may be selected. In this case, the same process as when the topmost device (the oldest device in terms of time) is selected is performed. That is, for example, when the replay mode of the UI 100 is started with both MR001 and R004 selected, the UI 100 is started in the changed state shown in FIG. 11. The concept of time synchronous playback in this specification includes synchronous playback of the time index specified by the time bar 112f and the playback time index of the driving record. In other words, it is also possible to synchronously play back indexes representing time, instead of the time itself.

[0057] 12, the CPU 11 may read the name of the abnormal device and its device comment 115 from the project data and display them in the detection list 114. The device comment 115 indicates the use of the device, etc. Thus, the user can easily understand the use of the abnormal device, etc.

[0058] The analysis comment 116 displays the comment included in the analysis result, the master data, and the time series data of the current device value for the device selected in the detection list 114. The data displayed in the analysis comment 116 is data for one control cycle. The time bar 112d indicates the timing when an unusual state occurred.

[0059] 9 and 12 show data for one control cycle in which an unusual state occurred for device R004. More specifically, in one control cycle, the master data shows two changes, OFF→ON and ON→OFF, whereas the current data shows no changes at all. Therefore, the time bar 112d is displayed at the timing of the unusual state, i.e., OFF→ON.

[0060] Here, when the user selects (clicks) MR001 in the detection list 114 in the analysis comment 116 shown in Fig. 9 and Fig. 12, the display switches to that shown in Fig. 10. Fig. 10 shows that an unusual state has occurred in the device of MR001. Note that in this embodiment, each of the time bars 112e, 112b, and 112f all show the same timing.

[0061] <Data collection from other PLCs, etc.> In the above embodiment, data is collected from the field device 10 connected to the PLC 1 and the data is analyzed. However, this is merely an example. The PLC 1 may collect and analyze data from other PLCs, field devices, etc. connected via a network. To do this, the PLC 1 must be able to communicate with devices (hereinafter, target devices) from which data is to be collected, such as other PLCs 1, via an industrial network.

[0062] 13 shows network devices required to connect the PLC 1 to an industrial wireless network. The industrial wireless system 200 includes, for example, the PLC 1, a master unit 201, and an industrial wireless network 204 (FIG. 14).

[0063] The master device 201 is a management device that manages the settings of a plurality of wireless slave devices, etc. The master device 201 has a WAN port (LAN port 38d) and LAN ports 38e to 38h.

[0064] The LAN port 38d is an Ethernet port for connecting to a higher-level network such as the Internet or an intranet. The LAN ports 38e to 38h are Ethernet ports for connecting to at least one of the wireless slave devices that form the industrial network. In this example, the LAN port 38e is connected to the LAN port 38a of the basic unit 3.

[0065] The expansion unit 4c is an expansion unit for increasing the number of network devices that can be connected to the basic unit 3. The expansion unit 4c has multiple LAN ports 38b, 38c, and is sometimes called an Ethernet (registered trademark) unit. As a result, the basic unit 3 has three LAN ports 38a, 38b, and 38c. The LAN ports 38b and 38c may be connected to the parent device 201, for example, or to a backbone server (e.g., a relational database server, a Web server, or an FTP server) or a display (a monitor device that displays device values ​​of PLC1).

[0066] 14 shows an industrial wireless network 204 connected to a master unit 201. The PLC 1 and master unit 201 are housed in a control panel 208, which is a shielded case.

[0067] The slave devices 202 (slave devices 202a to 202f) are an example of a wireless slave device. The slave devices 202a to 202f are the same network devices, but their roles in the industrial wireless network 204 may differ depending on their connection positions in the network topology and the settings made by the master device 201. The slave devices 202a to 202f may be called wireless nodes.

[0068] The slave unit 202a is connected to the LAN port 38e of the master unit 201 via a network cable. The slave unit 202a is connected to a target device 203a (e.g., another PLC1, a field device, etc.) via a network cable, and transfers operation data of the target device 203a to the PLC1. The target device 203a may be, for example, a power meter for measuring the power of a device (such as a flow meter or a processing device) used at an FA site. In this case, examples of the operation data transferred from the power meter to the PLC1 include data such as integrated active power, current, voltage, power factor, frequency, and integrated reactive power. An Ethernet-compatible communication unit may be provided as a part of the PLC1, and various operation data may be transferred from a power meter wired to any of the slave units 202a to 202f to the Ethernet-compatible communication unit via the industrial wireless network 204. It is not essential that the target device 203a is connected to the slave unit 202a. Furthermore, the child device 202a can wirelessly communicate with one or more other child devices 202b, 202d. When the child device 202a receives a request (including a transfer request) from the PLC 1 via the parent device 201, the child device 202a operates according to the request, transfers the request to the other child devices 202b to 202f, and transfers responses from the other child devices 202b to 202f to the PLC 1 via the parent device 201.

[0069] The child device 202b is a network device that performs wireless communication with the child devices 202a and 202c, and performs wired communication with the target device 203b. The target device 203b does not have to be connected. The child device 202b relays communication signals between the child devices 202a and 202c, and transfers operation data of the target device 203b to the PLC1 via the child device 202a and the parent device 201. When the child device 202b receives a request from the PLC1 via the parent device 201, the child device 202b operates according to the request, transfers the request to another child device 202c, and transfers a response from the other child device 202c to the PLC1 via the parent device 201.

[0070] The child device 202c is a network device that performs wireless communication with the child device 202b and wired communication with the target device 203c. The target device 203c may not be connected. The child device 202c transfers operation data of the target device 203c to the PLC 1 via the child device 202b, the child device 202a, and the parent device 201. When the child device 202c receives a request from the PLC 1 via the parent device 201 and the child devices 202a and 202b, it operates according to the request, creates a response to the request, and transfers it to the PLC 1 via the child devices 202a and 202b and the parent device 201.

[0071] The child device 202d is a network device that performs wireless communication with the child devices 202a, 202e, and 202f. A target device may also be connected to the child device 202d. The child device 202d relays communication signals between the child devices 202a and 202e, and relays communication signals between the child devices 202a and 202f. When the child device 202d receives a request from the PLC1 via the parent device 201 and the child device 202a, the child device 202d operates according to the request, transfers the request to the other child devices 202e and 202f, and transfers responses from the other child devices 202e and 202f to the PLC1 via the parent device 201.

[0072] The slave device 202e is a network device that performs wireless communication with the slave device 202d and wired communication with the target device 203e. The target device 203e does not have to be connected. The slave device 202e transfers operation data of the target device 203e to the PLC 1 via the slave device 202d, the slave device 202a, and the master device 201. When the slave device 202e receives a request from the PLC 1 via the master device 201 and the slave devices 202a and 202d, it operates according to the request, creates a response to the request, and transfers it to the PLC 1 via the slave devices 202a and 202d and the master device 201.

[0073] The slave device 202f is a network device that performs wireless communication with the slave device 202d and wired communication with the target device 203f. The target device 203f does not have to be connected. The slave device 202f transfers operation data of the target device 203f to the PLC 1 via the slave device 202d, the slave device 202a, and the master device 201. When the slave device 202f receives a request from the PLC 1 via the master device 201 and the slave devices 202a and 202d, it operates according to the request, creates a response to the request, and transfers it to the PLC 1 via the slave devices 202a and 202d and the master device 201.

[0074] In this way, by constructing the industrial wireless network 204, PLC1 can not only collect operation data from the expansion units 4 and field devices 10 connected to it, but also collect operation data from target devices including other PLC1s connected via the industrial wireless network 204.

[0075] Each of the child devices 202a to 202f may be connected to another PC2 and relay communication between the other PC2 and the PLC1. The other PC2 may function as a simple display (simple monitor) that displays operation data of the PLC1. Here, the industrial wireless network 204 may be a wireless mesh network. In general, a wireless mesh network is a network in which a plurality of child devices 202a to 202f are connected to each other by wireless communication and packets are forwarded in a multi-hop manner. In other words, it is a network in which a mesh-like topology is formed in the entire network by wirelessly connecting adjacent child devices that can communicate with each other, and packets are forwarded in a bucket brigade manner across one or more child devices. A wireless mesh network is characterized in that it is more resistant to communication failures than other wireless networks because it can switch to an alternative route even if communication is disabled on a specific route. Below, a supplementary explanation will be given using FIG. 14.

[0076] In FIG. 14, the child devices 202a to 202f may store, for example, a "destination table" and a "next hop table." The "destination table" is a table in which destination terminals such as the parent device 201 and the target devices 203a to 203f (their MAC addresses) are associated with wireless nodes (child devices 202a to 202f) connected by wire. When constructing a wireless mesh network, the parent device 201 grasps the existence (MAC addresses, etc.) of all the target devices 203a to 203f included in the wireless mesh network by, for example, transmitting a broadcast packet, and distributes information on the wireless nodes connected by wire to the target devices 203a to 203f to the child devices 202a to 202f. The "destination table" may be updated by transmitting a broadcast packet at the timing of first communication with a specific target device.

[0077] The "next hop table" is a table stored individually in each of the child devices 202a to 202f, and determines to which nearby child device the packet should be forwarded next (i.e., the next forwarding destination of the packet). When the parent device 201 constructs the industrial wireless network 204, it determines a packet forwarding path (e.g., a tree shape) and a next hop table assuming that path, and also determines next hop tables for the child devices 202a to 202f and distributes them to each child device. For example, the next hop table stored in the child device 202e includes information such as the next forwarding destination of a packet whose destination node is set to "child device 202a" is "child device 202d."

[0078] In this embodiment, the parent device 201 has the function of determining the packet forwarding path and the next hop table, but for example, the child device 202a connected to the parent device 201 by wire may have the function. In other words, when the child device 202a is not connected to the parent device 201 by wire, it has the same function as the other child devices 202b to 202f, while when it is connected to the parent device 201 by wire, it may have a function different from the other child devices 202b to 202f (for example, the function of determining the above-mentioned packet forwarding path and the next hop table). For example, a specific program may be executed only in the child device 202a connected to the parent device 201 by wire in order to perform the function of determining the above-mentioned packet forwarding path and the next hop table.

[0079] An example of packet forwarding will be described. Considering packet forwarding from the target device 203e to the parent device 201, the target device 203e first forwards the packet to the child device 202e connected to itself by wire. The child device 202e refers to the destination table and recognizes that the packet should be delivered to the child device 202a connected to the parent device 201 by wire. Next, the child device 202e refers to the next hop table and recognizes that in order to deliver the packet to the child device 202a, the packet should be sent to the child device 202d as the next forwarding destination. Then, the child device 202e forwards the packet to the child device 202d, which is the next packet forwarding destination. After that, the same process is repeated in the child device 202d, and the packet arrives at the child device 202a. The child device 202a refers to the destination table and recognizes that the packet addressed to the parent device 201 has arrived at itself, and forwards the packet to the parent device 201 connected by wire. In this way, packets are transferred in a bucket brigade fashion.

[0080] Another example of packet forwarding will be described. Considering packet forwarding from the target device 203e to the target device 203f, the target device 203e first forwards the packet to the child device 202e connected to itself by wire. The child device 202e refers to the destination table and recognizes that the packet should be delivered to the child device 202f connected to the target device 203f by wire. Next, the child device 202e refers to the next hop table and recognizes that in order to deliver the packet to the child device 202f, the packet should be sent to the child device 202d as the next forwarding destination. Then, the child device 202e forwards the packet to the child device 202d, which is the next packet forwarding destination. The child device 202d repeats the same process, and the packet arrives at the child device 202f. The child device 202f refers to the destination table and recognizes that the packet addressed to the target device 203f has arrived at itself, and forwards the packet to the target device 203f connected to it by wire. In this way, by using the "next hop table", it is possible to perform wireless communication without going through the child device 202a connected to the parent device 201.

[0081] The parent device 201 (or the child device 202a) may dynamically optimize the network configuration in the industrial wireless network 204 by periodically monitoring the communication state between the child devices in the industrial wireless network 204 (for example, packet delay time, number of hops, radio wave congestion, radio wave strength, etc.). In other words, the parent device 201 (or the child device 202a) may dynamically generate and update the next hop table. For example, when deterioration of the communication state between the child device 202d and the child device 202e is recognized due to some reason (such as the placement of an object that causes radio wave interference or radio wave disturbance), the child device 202e searches for other child devices with which wireless communication is possible. For example, when the child device 202b is found, a route that passes through the child device 202b is determined and updated as a packet transfer route from the child device 202e to the child device 202a. Then, parent device 201 (or child device 202a) determines and updates a next hop table assuming the updated packet forwarding route, and also determines and updates next hop tables for child devices 202a to 202f, and distributes the updated next hop table to each child device.

[0082] In addition, the function of periodically monitoring the communication state between the child devices, as well as the function of determining the packet forwarding path and the next hop table, may be provided in the child device 202a connected to the parent device 201 by wire, rather than in the parent device 201. In the above example, the packet forwarding using both the "destination table" and the "next hop table" has been described, but this is merely one example.

[0083] (1) Structure of the parent unit FIG. 15 shows the electrical structure of the parent device 201. The CPU 210 controls the LAN module 212 according to a program stored in the storage device 211. The LAN module 212 is a wired communication circuit (network communication circuit) that performs wired communication with other network devices connected to the multiple LAN ports 38d to 38h. The CPU 210 has at least one processor core (processing circuit). The storage device 211 has a read-only memory (ROM) and a random access memory (RAM). The ROM is an example of a non-volatile memory. The RAM is an example of a volatile memory.

[0084] 16 shows the functions of the CPU 210. The CPU 210 realizes various functions according to a program 250 stored in the storage device 211. All or part of these various functions may be implemented by a separate logic circuit (ASIC, FPGA) different from the CPU 210. ASIC is an abbreviation for application specific integrated circuit. FPGA is an abbreviation for field programmable gate array.

[0085] The memory management unit 230 reads predetermined data from the storage device 211 and writes predetermined data to the storage device 221 .

[0086] The slave management unit 231 manages the slaves 202a to 202f connected to the industrial wireless network 204. In particular, the request transmission unit 232 may request a specific slave 202 to turn on an indicator light or to change the lighting state of the indicator light. The slave search unit 233 searches for the slave 202a that is directly connected to the master 201 via a network cable. Such a slave 202a may be called a direct node or a root node. The slave registration unit 234 registers slave-specific information (e.g., product serial number, MAC address) of a slave newly added to the industrial wireless network 204 in the slave list 253 via the memory management unit 230.

[0087] The communication management unit 235 is an instance of a program module for the parent device 201 to communicate with the child device 202. The communication management unit 235 processes communication packets between the parent device 201 and the child device 202 in accordance with a predetermined communication protocol. The child device management unit 231 described above communicates with the child device 202 through the parent device / child device communication unit 236 of the communication management unit 235. The NAT unit 237 is an address conversion module that converts the address of a communication packet. For example, the NAT unit 237 converts the network address and port number of a packet transmitted and received between the LAN port 38d, which is a port for WAN, and the LAN ports 38e to 38h, which are ports for LAN. The communication management unit 235 may generate an IPv6 address based on its own MAC address.

[0088] The setting screen management unit 238 provides various setting screens to the PC 2 connected to the LAN ports 38e to 38h or the PC 2 connected to the child device 202. The setting screen may be realized by a Web user interface. The setting screen may be, for example, a setting screen for setting the industrial wireless network 204 and a setting screen for setting the indicator light of the child device 202. The user input receiving unit 239 receives user input from the PC 2 connected to the LAN ports 38e to 38h or the PC 2 connected to the child device 202. The screen providing unit 240 provides a setting screen (e.g., a Web page) to the PC 2 connected to the LAN ports 38e to 38h or the PC 2 connected to the child device 202. The screen providing unit 240 may be, for example, a Web server.

[0089] In addition to the program 250, various information is stored in the storage device 211. The parent device specific information 251 is network identification information (e.g., MAC address) or a serial number assigned to the parent device 201. The mesh network identifier 252 is a network identifier of the industrial wireless network 204 constructed as a wireless mesh network. The child device list 253 is a list of child device specific information of the child devices 202 permitted by the parent device 201 to participate in the industrial wireless network 204. The setting information 254 includes a wireless frequency band, a wireless channel, an IP address, and the like used in the industrial wireless network 204. The mesh network identifier 252 may be included in the setting information 254.

[0090] (2) Structure of the handset FIG. 17 shows an electrical structure of the child device 202. The CPU 220 controls the WLAN modules 223a to 223c and the LAN module 222 according to a program stored in the storage device 221. The CPU 220 has at least one processor core (processing circuit). The WLAN modules 223a to 223c are wireless communication circuits (wireless network communication circuits) that perform wireless communication with other wireless network devices. The WLAN modules 223a to 223c may be independent wireless communication circuits, or may be wireless communication circuits virtually realized by the SDR 226. In the case of a virtually realized wireless communication circuit, the antennas 225a, 225b, and 225c may be shared. SDR is an abbreviation for software radio. The SDR 226 realizes various wireless communication circuits by rewriting the contents of the software. The WLAN modules 223a to 223c communicate with other child devices 202 and the PC 2 through the antennas 225a, 225b, and 225c, respectively. In this example, the WLAN modules 223a to 223c and the antennas 225a, 225b, and 225c are connected one-to-one, but this is merely an example. For example, by interposing a multiplexer, the WLAN modules 223a to 223c and the antenna 225a may share an antenna prepared for each wireless band (e.g., 2.4 GHz, 5 GHz). Amplifiers, filters, frequency conversion circuits, and the like are arranged between the SDR 226 and 225a, 225b, and 225c, but are not shown here. The LAN module 222 is a wired communication circuit (network communication circuit) that performs wired communication with other network devices (e.g., the parent device 201, industrial devices) connected to the LAN port 38i. The indicator light 224 includes one or more light-emitting elements (e.g., light-emitting diodes, organic EL) that indicate the state of the child device 202 and a lighting control circuit. The storage device 221 has a ROM and a RAM.

[0091] The WLAN module 223a is, for example, a wireless local area network module for backhaul communication between the child devices 202. The network identifier (e.g., SSID) of the WLAN module 223a is the mesh network identifier 281 of the industrial wireless network 204. The WLAN module 223a operates as an access point (AP) and also as a station (STA).

[0092] The WLAN module 223b is, for example, a module for performing communication to wirelessly communicate with other child devices 202 to add the other child devices 202 to the industrial wireless network 204. Alternatively, the WLAN module 223b is, for example, a module for performing communication to wirelessly communicate with other child devices 202 to have the other child devices 202 add the WLAN module 223b to the industrial wireless network 204 in which the other child devices 202 are participating. In this case, an initial mesh network identifier 282 (dedicated to the adding process) is set in the WLAN module 223b. If the child device 202 has already participated in the industrial wireless network 204, the WLAN module 223b of the child device 202 functions as a second access point. If the child device 202 is about to participate in the industrial wireless network 204, the WLAN module 223b of the child device 202 functions as a second station. In FIG. 17, the WLAN module 223b and the other WLAN modules 223a and 223c appear to be physically separate modules, but this is merely an example. The present invention is not limited to this, and these modules may be physically configured in a single module (e.g., an integrated circuit) and logically configured as separate modules. In other words, they may be physically configured as one module by using a virtual AP technology or the like.

[0093] The WLAN module 223c is a module used to connect an external terminal (e.g., a notebook PC2, a tablet terminal, or a smartphone) to the industrial wireless network 204. The WLAN module 223c may function as a third access point, for example. It should be noted that the WLAN modules to be connected to the networks can be freely combined.

[0094] FIG. 18 shows the functions of the CPU 220. The CPU 220 realizes various functions according to the program 280 stored in the storage device 221. The storage management unit 260 reads out predetermined data from the storage device 221 and writes predetermined data to the storage device 221. When updating the program 280, an update file may be wirelessly transferred from the parent device 201 to the child device 202. Specifically, the user may instruct the program of the child device 202 to be updated via a Web screen provided by the parent device 201, for example, a screen of the PC2. The parent device 201 may hold the program 280 (system program) of the child device 202, and may update the program by transferring the program 280 held in the parent device 201 to the child device 202 upon receiving a user instruction (instruction signal) from the PC2.

[0095] The child unit management unit 261 manages various functions of the child unit 202. The indicator light operation unit 262 controls the display color and lighting mode (blinking, continuous lighting, etc.) of the indicator light 224. The additional child unit connection unit 263 is a module that establishes a communication link with other child units 202 that wish to be added to the industrial wireless network 204. The additional child unit connection unit 263 assigns an initial (dedicated for addition processing) mesh network identifier 282 to the WLAN module 223b, and connects the other child units 202 to a network dedicated to adding child units. Note that the mesh network identifier 282 is a mesh network identifier dedicated to addition processing that is known to all child units 202. The additional child unit connection unit 263 may operate only when the parent unit 201 permits or instructs the addition of the child unit 202. The request reception unit 264 receives a request from the parent unit 201 through the parent unit / child unit communication unit 266 of the communication management unit 265 and the WLAN module 223a. These requests include a request to transition from normal mode to child unit addition mode, an acquisition request to acquire the unique information 283 from the child unit 202 to be added, and a request to highlight the indicator light 224 of the child unit 202 to be added.

[0096] The communication management unit 265 manages and controls communication through the WLAN modules 223a to 223c and the LAN module 222. The parent / child communication unit 266 is an instance of a program module for the child device 202 to communicate with the parent device 201 in accordance with a predetermined communication protocol. The existing child device / additional child device communication unit 267 is an instance of a program module for controlling the WLAN module 223b in accordance with a predetermined communication protocol and for executing communication between the existing child device and the additional child device. The communication management unit 265 generates an IPv6 address based on its own MAC address and sets it in the network management unit 268.

[0097] The network management unit 268 manages the industrial wireless network 204. The network construction unit 269 constructs the industrial wireless network 204 as a wireless mesh network. For example, the network construction unit 269 sets the mesh network identifier 281 and setting information 254 set by the master unit 201 in the WLAN module 223a, and constructs the industrial wireless network 204. The setting information 254 includes a wireless frequency band, a wireless channel, an IP address, and the like used in the industrial wireless network 204.

[0098] The storage device 221 stores unique information 283. The unique information 283 is a network identifier (e.g., MAC address) assigned to the WLAN modules 223a to 223c and the LAN module 222. Hereinafter, the unique information 283 will be described as the network identifier assigned to the WLAN module 223a. When a child device 202 is newly added, the unique information 283 of the child device 202 is transmitted to the parent device 201 via the industrial wireless network 204. The parent device 201 determines whether to permit the addition of the child device 202 based on the unique information 283 of the child device 202.

[0099] <Adding master and slave devices to an industrial wireless network> 1. Initial setup of the parent unit The connection of the master unit 201 and the slave unit 202 to the industrial wireless network 204 is performed, for example, in the following procedure.

[0100] -Connection between PLC1 and master unit 201 Initial settings for parent unit 201 Addition of handset 202 There are various methods for adding the child device 202. For example, it is possible to first register the child device 202a, which is a wired child device connected by a LAN cable, to the parent device 201, and then register the other child devices 202b to 202h to the parent device 201. Alternatively, it is possible to register not only the child device 202a, which is a wired child device, but also the child devices 202b to 202h, which are wireless child devices, to the parent device 201 in parallel at the same time. In any case, initial settings are first performed on the parent device 201.

[0101] 19 is a diagram showing how the parent device 201 connected to the PLC 1 is initially set by the PC 2, which is a setting device. The PLC 1 and the parent device 201 are connected by a LAN cable. The PC 2 and the parent device 201 are also connected by a LAN cable. These LAN cables are connected to any of the LAN ports 38e to 38h.

[0102] 20 shows the setting information saving process executed by the parent device 201. The CPU 210 of the parent device 201 executes the following procedure in accordance with the program 250.

[0103] In S1, the CPU 210 (screen providing unit 240) determines whether or not a setting screen request has been received from the PC 2, which is a setting device. For example, a request from the PC 2 to access a setting page of a Web server that is part of the screen providing unit 240 is an example of a setting screen request. When the setting screen request is received, the CPU 210 proceeds from S1 to S2.

[0104] In S2, the CPU 210 provides a setting screen to the setting device, PC 2. For example, the CPU 210 transmits to PC 2 parts of a Web page (e.g., an HTML file, an image file, a CSS file, etc.) for displaying the setting screen.

[0105] FIG. 21 is an example of a setting screen 300 displayed on the display device 7 of the PC 2. In this example, the network identifier (e.g., SSID), frequency, and channel of the industrial wireless network 204 to be stored in the setting information 254 are input. The text box 301 accepts the network identifier input by the user. The frequency list 302 accepts the input or selection of a frequency band by the user. The channel list 303 accepts the input or selection of a channel by the user. The cancel button 304 is a button for instructing the CPU 210 to cancel the initial setting of the parent device 201. The save button 305 is a button for instructing the CPU 210 to save the network identifier, frequency, and channel in the setting information 254. Other settings, such as an encryption method for the wireless section, may be accepted through the setting screen 300. The network identifier may be saved in the mesh network identifier 252. Although the network identifier is input in FIG. 21, either the backhaul or the external AP may be selectively input.

[0106] In S3, the CPU 210 (user input receiving unit 239) receives user input regarding network settings (initial settings of the parent device 201). As described above, the network identifier, frequency, channel, and the like are received.

[0107] In S4, the CPU 210 (user input receiving unit 239) determines whether a save request has been input. A save request is, for example, pressing the save button 305 with the pointer 103. When a save request is input, the CPU 210 proceeds to S5. In S5, the CPU 210 (storage management unit 230) stores the setting information 254 input by the user in the storage device 211. On the other hand, if a save request has not been input, the CPU 210 proceeds from S4 to S6. In S6, the CPU 210 determines whether the cancel button 304 has been pressed. If the cancel button 304 has not been pressed, the CPU 210 proceeds from S6 to S3. On the other hand, if the cancel button 304 has been pressed, the CPU 210 closes the setting screen 300 and ends the save process.

[0108] 2. Adding a child unit 2-1. Adding a wired device 2-1-1. Parent unit processing 22 shows that a child device 202a, which is a direct child device (wired child device), is added to a parent device 201. In this example, other child devices 202b to 202h are added later.

[0109] 23 shows the operation of CPU 210 of parent device 201 when a wired child device (child device 202a) is connected. It is assumed that communication between child device 202a and parent device 201 is encrypted using an encryption key known to both child device 202a and parent device 201. Here, the simplest example in which PC2, which is a setting device, is not involved, is described, but as described later, parent device 201 may be permitted by PC2 to connect a wired child device (child device 202a).

[0110] In S11, CPU 210 (e.g., child device search unit 233) broadcasts a child device search request, and determines whether or not a connection request has been received from a wired child device in response to the search request. For example, CPU 210 determines whether or not a connection request has been received from child device 202a connected to any of LAN ports 38e to 38h via a LAN cable. If there is a connection request from a wired child device, CPU 210 proceeds from S11 to S12. Note that, although the connection request is assumed to be from a wired child device here, it may be from parent device 201.

[0111] In S12, CPU 210 (slave unit search section 233) acquires unique information (unique information 283) from the wired slave unit.

[0112] In S13 , the CPU 210 (slave unit registration unit 234 ) registers the unique information of the wired slave unit in the slave unit list 253 .

[0113] In S14, the CPU 210 (slave registration unit 234) reads out the setting information 254 from the storage device 211, and transmits the setting information 254 to the wired slave device. As a result, the slave device 202a, which is a wired slave device, obtains the setting information 254 and establishes the industrial wireless network 204.

[0114] 2-1-2. Processing of wired child devices 24 shows the process executed by the CPU 220 of the wired slave unit. When the power is turned on, the CPU 220 executes the following process.

[0115] In S21, the CPU 220 (network construction unit 269) determines whether the setting information 254 has not been acquired from the parent device 201. This corresponds to the process of determining whether the wired child device has yet been registered in the parent device 201. If the wired child device has not yet been registered in the parent device 201 and the industrial wireless network 204 cannot be constructed, the CPU 220 proceeds from S21 to S22. On the other hand, if the wired child device has already been registered in the parent device 201 and has been stored in the storage device 221 based on the setting information 254, the CPU 220 proceeds from S22 to S28.

[0116] In S22, the CPU 220 (indicator light operation unit 262) causes the indicator light 224 to flash orange. Flashing orange means setting the display color of the indicator light 224 to orange and setting the display mode to flash the indicator light 224 at regular intervals. Note that in this embodiment, the indicator light is turned on orange in S22, but it may also be turned on orange when communication is established, for example.

[0117] In S23, CPU 220 (parent device / child device communication unit 266) transmits a request to parent device 201 to acquire setting information 254. Note that, although a request to acquire setting information 254 is transmitted to parent device 201 here, the present invention is not limited to this, and for example, a request may always be issued from parent device 201 to the child device.

[0118] In S24, the CPU 220 (parent device / child device communication unit 266) receives the setting information 254 from the parent device 201.

[0119] In S25, the CPU 220 (memory management unit 260) stores the setting information 254 in the storage device 221.

[0120] In S26, the CPU 220 (network construction unit 269) starts up the WLAN module 223a in accordance with the setting information 254, and constructs the industrial wireless network 204, which is a wireless mesh network.

[0121] In S27, the CPU 220 (indicator light operation unit 262) causes the indicator light 224 to light up in green. Lighting up in green means setting the display color of the indicator light 224 to green and the display mode to continuous lighting.

[0122] In S28, the CPU 220 (additional slave connection unit 263) distributes (propagates) the setting information 254 to the wireless slaves (slave units 202b to 202h) connected to the mesh network for adding a slave unit constructed by the WLAN module 223b. Note that S28 is an option that is executed when other wireless slave units are present. The other wireless slave units acquire the setting information 254 from the wired slave unit directly connected to the master unit 201, store it in their own storage device 221, and join the industrial wireless network 204 according to the setting information 254.

[0123] 2-2. Adding a wireless adapter 25 shows that the parent device 201 and the child device 202a, which is a wired child device, are connected via a network cable 600, and the child device 202a acquires setting information 254 from the parent device 201 to construct an industrial wireless network 204. However, the child device 202a is the only wireless child device participating in the industrial wireless network 204. Note that, in FIG. 25, a case will be described in which the child device 202a is added once, and then a wireless child device is added, but the present invention is not limited to this, and the child device 202a and at least one of the other child devices 202b to 202f may be added at the same time.

[0124] 26 shows that the power of the child device 202d, which has not yet been registered in the parent device 201, has been turned on and started up. Since the child device 202d has not yet been registered in the parent device 201, the child device 202d cannot join the industrial wireless network 204.

[0125] FIG. 27 shows the wireless network for addition 209 constructed to register the child device 202d to the parent device 201. Since the child device 202d to be added does not have the setting information 254 of the industrial wireless network 204, the mesh network identifier 282 of the wireless network for addition 209 is set to the WLAN module 223b. The child device 202a, which is a wired child device, sets the mesh network identifier 282 of the wireless network for addition 209 to the WLAN module 223b based on a transition instruction to a child device addition mode (child device addition permitted state) transmitted from the PC2 through the parent device 201. As a result, the child devices 202a and 202d construct and participate in the wireless network for addition 209. That is, the child device 202a becomes capable of propagating the setting information 254 to the child device 202d. The child device 202d saves the setting information 254 in the storage device 221.

[0126] 28 shows that the slave device 202d has joined the industrial wireless network 204. The CPU 220 of the slave device 202d sets the setting information 254 stored in the storage device 221 in the WLAN module 223a, and joins the industrial wireless network 204. It is assumed that the setting information 254 is stored in a non-volatile memory area.

[0127] FIG. 29 shows an example in which a plurality of other child devices 202d, 202e, and 202f are added to the parent device 201. In this state, the parent device 201 and the child device 202a have not yet transitioned to the child device addition mode and are in the normal mode. Therefore, as shown in FIG. 30, the unregistered child device 202d sets the mesh network identifier 282 in the WLAN module 223b and constructs the addition wireless network 209. Similarly, the other child devices 202e and 202f do not have the setting information 254. Therefore, as shown in FIG. 31, the child devices 202e and 202f also set the mesh network identifier 282 in the WLAN module 223b and join the addition wireless network 209.

[0128] 32, when the parent device 201 and the child device 202a transition to the child device addition mode through the setting device 2, the child device 202a sets the mesh network identifier 282 in the WLAN module 223b and participates in the addition wireless network 209. This enables the child devices 202a, 202d, 202e, and 202f to communicate wirelessly. The child device 202a distributes the setting information 254 to the child devices 202d, 202e, and 202f. The child devices 202d, 202e, and 202f store the setting information 254 in the storage device 221.

[0129] 33, the slave devices 202d, 202e, and 202f join the industrial wireless network 204 in accordance with the setting information 254. Note that the slave devices 202a, 202d, 202e, and 202f each deactivate the WLAN module 223b and withdraw from the additional wireless network 209.

[0130] 2-2-1. Parent unit processing 34 shows the addition process of the child device 202 executed by the CPU 210 of the parent device 201. Here, it is assumed that the parent device 201 has already stored the setting information 254 in the storage device 221.

[0131] In S41, the CPU 210 (setting screen management unit 238) determines whether or not an additional screen request has been received from the PC 2. Here, the additional screen is an additional screen (e.g., a Web page) provided to the PC 2 in order to add the child device 202. When the additional screen request is received, the CPU 220 proceeds from S41 to S42.

[0132] In S42, the CPU 210 (setting screen management unit 238) provides an additional screen (for example, a Web page) to the PC 2.

[0133] FIG. 35 shows an example of an addition screen 310 displayed on the display device 7 of the PC 2. The addition screen 310 has a list 311 of wireless slave units to be added and a list 315 of slave units already connected to the industrial wireless network 204. The lists 311 and 315 each include a unit name 312 and a serial number 314, which are unique information of the slave unit. The check box 317 is a control object for selecting a slave unit that the user wishes to add from among multiple slave units to be added found by the search. The button 313 is a button for instructing to highlight the indicator light 224 of the slave unit 202. When the button 313 is pressed by the pointer 103, a request for highlighting is transmitted to the slave unit 202 corresponding to the pressed button 313. The indicator light operation unit 262 of the slave unit 202 highlights the indicator light 224 in accordance with the request for highlighting. The highlighting may include, for example, increasing brightness beyond normal. In addition, on the addition screen 310, the list 315 of connected child devices may be omitted.

[0134] The targets of the highlighted lighting may include not only the child unit 202 to be added, but also the child unit 202 that is already connected. A large number of child units 202 may be installed throughout a factory. A user can press the button 313 to identify a specific child unit 202 from among the multiple child units 202.

[0135] When the addition approval button 316 is pressed by the pointer 103, the slave unit management unit 231 transmits an addition approval to the slave unit 202 that has been checked by the check box 317. When the wired slave unit receives the addition approval, it transmits the setting information 254 to the slave unit 202 that is the target of the addition approval. When the slave unit 202 that is the target of the addition approval receives the setting information 254, it stores it in the storage device 221.

[0136] In S43, the CPU 210 (request transmission unit 232, parent / child communication unit 236) transmits an addition instruction to the wired child device.

[0137] In S44, the CPU 210 (parent device / child device communication unit 236) receives the unique information of the child device to be added. When the CPU 210 receives a notification from the parent device 201 indicating that the added child device has been found, the CPU 210 may transmit an instruction to the parent device 201 to obtain the unique information of the added child device.

[0138] In S45, the CPU 210 (screen providing unit 240) displays the unique information of the additional child device on the display device 7 of the PC 2.

[0139] 36 shows the addition screen 310 reflecting the unique information of the discovered added child device. The parent device 201 updates the addition screen 310 upon acquiring the unique information of the added child device.

[0140] In S46, the CPU 210 (user input receiving unit 239) determines whether or not a request for highlighting has been input from the PC 2. If a request for highlighting has not been input, the CPU 210 proceeds from S46 to S50.

[0141] In S47, the CPU 210 (request transmission unit 232, parent / child unit communication unit 236) transmits a request for highlighting to the child unit that is to be highlighted.

[0142] In S48, the CPU 210 (user input receiving unit 239) determines whether or not an emphasis removal instruction has been input from the PC 2. If an emphasis removal instruction has been input, the CPU 210 proceeds from S48 to S49. Note that the CPU 210 also proceeds from S48 to S49 if an emphasis removal instruction has not been input even after a predetermined time has elapsed.

[0143] In S50, the CPU 210 (child unit registration unit 234) determines whether approval for addition has been obtained from the parent unit 201. If approval for addition has been obtained, the CPU 210 proceeds from S50 to S51. In S51, the CPU 210 (child unit registration unit 234) registers the unique information in the child unit list 253 and transmits approval for addition to the wired child unit. As a result, the wired child unit transmits setting information 254, which has been stored in advance in the storage device 221, to the added child unit that is the target of approval for addition. On the other hand, if approval for addition has not been obtained from PC2, the CPU 210 proceeds from S50 to S52. In S52, the CPU 210 (child unit registration unit 234) transmits an addition refusal to the parent unit 201. As a result, the parent unit 201 does not transmit setting information 254 to the child unit 202 that was the target of addition.

[0144] 2-2-2. Processing of wired devices (or existing devices) FIG. 37 shows a slave unit addition process executed by the CPU 220 of a wired slave unit or a slave unit 202 already participating in the industrial wireless network 204.

[0145] In S61, the CPU 220 (request receiving unit 264) determines whether or not an instruction to transition to the child unit addition mode has been received from the parent unit 201. When an instruction to transition to the child unit addition mode has been received, the CPU 220 transitions from the normal mode to the child unit addition mode, and proceeds from S61 to S62.

[0146] In S62, the CPU 220 (network construction unit 269) sets the mesh network identifier 282 in the WLAN module 223b, and constructs the additional wireless network 209. The additional slave unit also holds the mesh network identifier 282, and can therefore connect to the additional wireless network 209.

[0147] In S63, the CPU 220 (additional child device connection unit 263) determines whether or not an additional child device has connected to the additional wireless network 209. When an additional child device has connected to the additional wireless network 209, the CPU 210 advances from S63 to S64.

[0148] In S64, the CPU 220 (additional child device connection unit 263) notifies (reports) to the parent device 201 that the additional child device has been connected.

[0149] In S65, the CPU 220 (additional child device connection section 263) determines whether or not a request to acquire unique information about the added child device has been received from the parent device 201. If a request to acquire unique information has been received, the CPU 220 proceeds from S65 to S66.

[0150] In S66, the CPU 220 (additional child device connection unit 263) acquires unique information from the added child device. For example, the added child device connection unit 263 transmits an acquisition request to the added child device.

[0151] In S67, the CPU 220 transmits to the parent device 201 the unique information of the added child device (eg, unit name, serial number).

[0152] In S68, the CPU 220 (additional child unit connection unit 263) determines whether or not an addition approval for the additional child unit has been received from the parent unit. If an addition approval has not been received (for example, if an addition refusal has been received), the CPU 220 returns from the child unit addition mode to the normal mode and ends the child unit addition process. On the other hand, if an addition approval has been received, the CPU 220 proceeds from S68 to S69.

[0153] In S69, the CPU 220 (additional child device connection section 263) reads out the setting information 254 stored in the storage device 221, and transfers the setting information 254 to the additional child device.

[0154] In S70, the CPU 220 (network construction unit 269) releases the addition wireless network 209. In addition, the CPU 220 returns from the child unit addition mode to the normal mode.

[0155] 2-2-3. Processing additional handsets 38 shows a slave unit adding process executed by the added slave unit. The CPU 220 executes the following process in accordance with the program 280.

[0156] In S81, the CPU 220 (network construction unit 269) determines whether the parent device 201 does not exist or is not registered with the parent device 201. For example, if the setting information 254 is stored in the storage device 221, the network construction unit 269 determines that the parent device 201 is registered. In this case, the CPU 220 proceeds from S81 to S91, and joins the industrial wireless network 204, which is a wireless mesh network, based on the setting information 254. On the other hand, if the setting information 254 is not stored in the storage device 221, the network construction unit 269 determines that the parent device 201 is not registered. In this case, the CPU 220 proceeds from S81 to S82.

[0157] In S82, the CPU 220 (indicator light operation unit 262) causes the indicator light 224 to flash orange.

[0158] In S83, the CPU 220 (additional child device connection unit 263) determines whether or not there is an additional wireless network 209 (existing child device). The additional child device connection unit 263 searches for an additional wireless network 209 having the same network identifier as the mesh network identifier 282 that the additional child device connection unit 263 holds. If the additional wireless network 209 already exists, the CPU 220 proceeds from S83 to S84. In S84, the CPU 220 (network construction unit 269) joins the additional wireless network 209 constructed by the existing child device. On the other hand, if the additional wireless network 209 does not exist, the CPU 220 proceeds from S83 to S93. In S93, the CPU 220 (network construction unit 269) constructs the additional wireless network 209 by itself. As a result, a plurality of additional child devices join the additional wireless network 209. Details of this example will be described later.

[0159] In S85, the CPU 220 (indicator lamp operation unit 262) lights the indicator lamp 224 in orange. Lighting in orange means setting the lighting color of the indicator lamp 224 to orange and setting the lighting mode to continuous lighting.

[0160] In S86, the CPU 220 (request receiving unit 264) determines whether or not a request to acquire unique information has been received from the parent device 201 via the additional wireless network 209. When a request to acquire unique information has been received, the CPU 220 proceeds from S86 to S87.

[0161] In S 87 , the CPU 220 (request receiving unit 264 ) reads out the unique information 283 from the storage device 221 and transmits it to the parent device 201 .

[0162] In S88, the CPU 220 (parent device / child device communication unit 266) receives the setting information 254 from the wired child device or another existing child device via the additional wireless network 209.

[0163] In S89, the CPU 220 (memory management unit 260) stores the setting information 254 in the storage device 221.

[0164] In S90, the CPU 220 (network construction unit 269) releases the additional wireless network 209.

[0165] In S91, the CPU 220 (network construction unit 269) joins the industrial wireless network 204, which is a wireless mesh network, in accordance with the setting information 254.

[0166] In S92, the CPU 220 (indicator lamp operation unit 262) turns on the indicator lamp 224 in green.

[0167] In this manner, the slave device becomes able to participate in the industrial wireless network 204 .

[0168] 2-3. Highlighting FIG. 39 shows the highlight lighting process executed by the CPU 220 of the child device 202.

[0169] In S121, the CPU 220 (request receiving unit 264) determines whether or not a highlight lighting instruction (highlight lighting request) has been received from the parent device 201. When a highlight lighting instruction has been received, the CPU 220 proceeds from S121 to S122.

[0170] In S122, the CPU 220 (indicator lamp operation unit 262) lights up the indicator lamp 224 in an emphasized manner.

[0171] In S123, the CPU 220 (request receiving unit 264) determines whether or not a highlighting cancellation instruction (highlighting cancellation request) has been received from the parent device 201. When a highlighting cancellation instruction has been received, the CPU 220 proceeds from S123 to S124.

[0172] In S124, the CPU 220 (indicator lamp operation unit 262) cancels the highlighted illumination of the indicator lamp 224.

[0173] Here, the highlighted lighting is cancelled based on the instruction to cancel the highlighted lighting, but this is merely an example. When a timer or counter has timed a certain period of time, the CPU 220 may cancel the highlighted lighting.

[0174] 2-4.Signal sequence Fig. 40 shows a signal sequence in the slave unit addition process. Here, it is assumed that when a wired slave unit is already connected to the master unit 201, another wireless slave unit will join the industrial wireless network 204. In Fig. 40, WNW is an abbreviation for wireless network.

[0175] In Sq1, the PC2 transmits an add screen request to the parent device 201, and the parent device 201 receives the add screen request. The add screen request is an implicit instruction to switch to a child device addition mode.

[0176] In Sq2, the parent device 201 transmits an instruction to the wired child device (child device 202a) to switch to the child device addition mode, and the child device 202a receives the instruction. As a result, the child device 202a switches to the child device addition mode and establishes an addition wireless network 209.

[0177] In Sq3, the parent device 201 transmits display information (such as an HTML file) for the additional screen 310 to the PC 2, which receives it. The PC 2 displays the additional screen 310 (FIG. 35) on the display device 7 using a Web browser. Note that the order of Sq2 and Sq3 may be reversed.

[0178] In Sq4, the additional child devices (child devices 202b to 202h, etc.) discover the additional wireless network 209 and join the additional wireless network 209.

[0179] In Sq5, the child device 202a discovers an additional child device that has joined the additional wireless network 209, and transmits a notification indicating that the additional child device has been discovered to the parent device 201. The parent device 201 receives the notification.

[0180] In Sq6, the parent device 201 transfers the notification to the PC 2. Sq6 may be omitted.

[0181] In Sq7, the parent device 201 transmits an acquisition request for requesting unique information 283 of the added child device to the child device 202a, and the child device 202a receives the acquisition request.

[0182] In Sq8, the child device 202a transfers the acquisition request to the additional child device. The additional child device receives the acquisition request.

[0183] In Sq9, the added child device transmits its own unique information 283 to the child device 202a as a response to the acquisition request. The child device 202a receives the unique information 283 of the added child device.

[0184] In Sq10, the child device 202a transfers unique information 283 of the added child device to the parent device 201. The parent device 201 receives unique information 283 of the added child device.

[0185] In Sq11, the parent unit 201 creates (updates) an addition screen 310 that reflects the unique information 283 of the added child unit, and transmits the updated addition screen 310 to the PC2. The PC2 receives the updated addition screen 310 (FIG. 36) and displays it on the display device 7. This allows the user to check the unique information (e.g., unit name and serial number) of the added child unit. The unique information is generally printed on the box in which the child unit 202 is packed, the instruction manual, and the warranty card, and the user can check the unique information. In other words, the user can check through the addition screen 310 whether the child unit that the user wishes to have join the industrial wireless network 204 has actually been detected as an added child unit.

[0186] In Sq12, PC2 transmits approval for addition to parent device 201 based on a user operation, and parent device 201 receives the approval for addition. The approval for addition may include unique information of child device 202 approved for addition. This allows a distinction to be made between child device 202 approved for addition and child device 202 rejected for addition. Parent device 201 registers unique information 283 of child device 202 approved for addition in child device list 253.

[0187] In Sq13, the parent device 201 transfers the addition approval to the child device 202a. The child device 202a receives the addition approval.

[0188] In Sq14, the parent device 201 transmits the setting information 254 to the additional child device whose addition has been approved. The additional child device whose addition has been approved receives the setting information 254 (including the mesh network identifier 281) and stores it in the storage device 221.

[0189] In Sq15, the additional slave device joins the industrial wireless network 204 according to the setting information 254.

[0190] In Sq16, the parent device 201 transmits an instruction to end the child device addition mode to the existing child devices (child device 202a) including the wired child devices. The existing child devices (child device 202a) including the wired child devices return (transition) from the child device addition mode to the normal mode.

[0191] <Other examples of adding child units (bulk registration)> In the above example, the wired slave unit is first registered in the parent device 201, and then the wireless slave unit is added. However, as shown in Fig. 41, a plurality of slave units 202a, 202e, and 202f including a wired slave unit may be registered in the parent device 201 in parallel at the same time.

[0192] In this case, as shown in Fig. 42, the multiple child devices 202a, 202e, and 202f do not have the setting information 254, and therefore establish an addition wireless network 209. The multiple child devices 202a, 202e, and 202f acquire the setting information 254 from the parent device 201 through the addition wireless network 209. Then, as shown in Fig. 43, the multiple child devices 202a, 202e, and 202f join the industrial wireless network 204 based on the setting information 254.

[0193] Fig. 44 is a sequence diagram of this example. Since the child devices 202a, 202e, and 202f are not yet registered, the indicator lights 224 may blink orange. When the parent device 201 is accessed by the PC2, the parent device 201 may execute user authentication by having the PC2 input a login ID and a password.

[0194] In Sq21, PC2 transmits a request for an additional screen to parent device 201, and parent device 201 receives the request for an additional screen.

[0195] In Sq22, the parent device 201 transmits a network construction instruction to the child device 202a.

[0196] In Sq23, the parent device 201 transmits display information (such as an HTML file) for the additional screen 310 to the PC 2, which receives it. The PC 2 displays the additional screen 310 (FIG. 35) on the display device 7. The order of Sq32 and Sq23 may be reversed.

[0197] In Sq24, the child devices 202a, 202e, and 202f construct an additional wireless network 209 based on the NW construction instruction. This allows not only the child device 202a, which is a wired child device, but also the child devices 202e and 202f, which are wireless child devices, to communicate with the parent device 201. The child devices 202a, 202e, and 202f may each turn on an indicator light 224 in orange.

[0198] In Sq25, parent device 201 broadcasts a search packet for searching for child devices 202a, 202e, and 202f.

[0199] In Sq26, the child devices 202a, 202e, and 202f transmit the unique information 283 to the parent device 201 as a response to the search packet.

[0200] In Sq27, the parent device 201 updates the added screen 310 with the unique information 283 of the discovered child devices 202a, 202e, and 202f. This causes the PC 2 to display the updated added screen 310 on the display device 7.

[0201] In Sq28, PC2 transmits approval for addition to parent device 201 based on a user operation, and parent device 201 receives the approval for addition. The approval for addition may include unique information of child devices 202a, 202e, and 202f approved for addition. This allows a distinction to be made between child devices 202 approved for addition and child devices 202 rejected for addition. Parent device 201 registers unique information 283 of child devices 202a, 202e, and 202f approved for addition in child device list 253.

[0202] In Sq29, the parent device 201 transmits the setting information 254 to the child devices 202a, 202e, and 202f whose addition has been approved. The child devices 202a, 202e, and 202f whose addition has been approved receive the setting information 254 (including the mesh network identifier 281) and store it in the storage device 221.

[0203] In Sq30, the slave units 202a, 202e, and 202f join the industrial wireless network 204 in accordance with the setting information 254. The slave units 202a, 202e, and 202f may each turn on the indicator light 224 in green.

[0204] In Sq31, the parent device 201 updates the addition screen 310 to indicate that the child devices 202a, 202e, and 202f have been connected. The PC 2 displays the updated addition screen 310 on the display device 7.

[0205] In this manner, a plurality of child devices 202 may be registered simultaneously in parallel. Note that the child device 202 that has received a request for emphasis lighting from the PC 2 may emphasize lighting (e.g., increase brightness) the indicator lamp 224 in accordance with the request for emphasis lighting.

[0206] <Settings change process> The PC2 can connect to the parent device 201 and change the setting information 254. In this case, the changed setting information 254 must be propagated (distributed) to each child device 202 participating in the industrial wireless network 204.

[0207] Fig. 45 shows the setting change process executed in the parent device 201. The difference between Fig. 45 and Fig. 20 is that S6 is added after S5. In S6, the CPU 210 (request transmission unit 232, parent device / child device communication unit 236) detects that the setting information 254 has been changed, and transmits (broadcasts) a setting change request including the changed setting information 254 to the industrial wireless network 204. Note that the CPU 210 may wait for a response to the setting change request before transmitting the setting information 254 to the child device 202.

[0208] 46 shows the setting change process of the child device 202. Here, it is assumed that the setting change request and the setting information 254 are received separately. Of course, the setting change request and the setting information 254 may be received together.

[0209] In S101, the CPU 220 (request receiving unit 264, parent / child device communication unit 266) determines whether or not a setting change request has been received. When a setting change request has been received, the CPU 220 proceeds from S101 to S102.

[0210] In S102, the CPU 220 (request receiving unit 264, parent / child device communication unit 266) receives the setting information 254 from the parent device 201.

[0211] In S103, the CPU 220 (memory management unit 260) stores the received setting information 254 in the storage device 221.

[0212] In S104, the CPU 220 judges whether or not there is another child device 202 connected to the self device. Each child device 202 holds the network address (e.g., MAC address, etc.) of the child device 202 that is the next hop in the storage device 221, and knows whether or not there is another child device 202 connected to the self device. If the parent device 201 does not broadcast the setting information, the setting information 254 needs to be propagated to the other child devices 202 in S104 and S105. Therefore, in the case where the setting information 254 is broadcast, S104 and S105 are unnecessary. If there is no other child device 202 connected to the self device, the CPU 220 proceeds from S104 to S106. If there is another child device 202 connected to the self device, the CPU 220 proceeds from S104 to S105.

[0213] In S105, the CPU 220 distributes the setting information 254 to the other child devices 202. The other child devices 202 store the distributed setting information 254 in the storage device 221.

[0214] In S106, the CPU 220 reconstructs the wireless mesh network (industrial wireless network 204) based on the updated setting information 254. As a result, the updated setting information 254 is reflected in the industrial wireless network 204.

[0215] The setting change request may be used when writing the setting information 254 to the added child device in the child device addition process.

[0216] <Removal of child device> FIG. 47 shows a deletion screen 320 for deleting any of the slave units 202 connected to the industrial wireless network 204. As already described, the list 315 is a list of the connected slave units 202. The unit name 312 and the serial number 314 are listed for each slave unit 202. The button 313 is a button for highlighting and lighting the indicator light 224 of the corresponding slave unit 202. The check box 317 is a control object for selecting the slave unit 202 to be deleted. Note that, if a wired slave unit is deleted, the industrial wireless network 204 is disconnected from the master unit 201, so deletion of the wired slave unit may be prohibited. For example, the check box 317 corresponding to the wired slave unit may not be displayed or may be made unselectable. The delete button 318 is a button for instructing the CPU 210 to delete the selected slave unit.

[0217] FIG. 48 shows the deletion process executed by the CPU 220 of the parent device 201.

[0218] In S161, the CPU 210 (screen providing unit 240) determines whether or not a delete screen request has been received from the PC 2. The delete screen request may be an access request to the URL of a Web page corresponding to the delete screen 320. When the delete screen request is received, the CPU 210 proceeds from S161 to S162.

[0219] In S162, the CPU 210 (screen providing unit 240) provides the deletion screen 320 (HTML file, CSS file, image file) to the PC 2 which is the setting device.

[0220] In S163, the CPU 210 (user input receiving unit 239) receives the selection of the child unit to be deleted. As described above, the child unit 202 with the check box 317 checked is the child unit to be deleted.

[0221] In S164, the CPU 210 (user input receiving unit 239) determines whether or not a delete instruction has been input by the user. If a delete instruction has been input, the CPU 210 proceeds from S164 to S165.

[0222] In S165, the CPU 210 (child unit registration unit 234) deletes the selected child unit 202 from the child unit list 253.

[0223] In S166 , the CPU 210 (request transmission unit 232 ) transmits a deletion request to the selected child device 202 .

[0224] FIG. 49 shows the deletion process executed by the CPU 220 of the child device 202 .

[0225] In S181, the CPU 220 (request receiving unit 264) determines whether or not a deletion request has been received from the parent device 201. If a deletion request has been received, the CPU 220 proceeds from S181 to S182.

[0226] In S182, the CPU 220 (memory management unit 260) deletes the setting information 284 (and the mesh network identifier 281) from the storage device 221.

[0227] In S183, the CPU 220 (network management unit 268) turns off the WLAN module 223a and leaves the industrial wireless network 204.

[0228] In S184, the CPU 220 (indicator light operation unit 262) blinks the indicator light 224 in orange. This allows the user to easily understand which child device 202 has become unregistered. In the child device deletion process described above, it is assumed that the child device to be deleted is powered on when the deletion request is issued. There may be a case where the child device to be deleted is powered off when the deletion request is issued. In this case, for example, the parent device may store a unique identifier of the target child device. After the target child device is powered on next time, the parent device may be configured to automatically transmit a deletion request to the target child device at the timing specified by the user or when the parent device recognizes that the target child device is powered on. When the target child device receives the deletion request from the parent device, it withdraws from the industrial wireless network 204.

[0229] <Other> Although the case where the additional slave unit is connected to the wired slave unit has been mainly described, the additional slave unit may be connected to a wireless slave unit connected to the wired slave unit. In this case, a plurality of slave units 202 relay communication between the parent unit 201 and the additional slave unit.

[0230] When an additional handset is connected to an existing handset, the existing device may apply authentication processing to the additional handset, such as a 4-way handshake.

[0231] The next hop can be dynamically changed for each of the multiple child devices 202 participating in the industrial wireless network 204. For example, the next hop of the child device 202e in Fig. 14 is the child device 202d, but the next hop of the child device 202e may be changed to the child device 202b. This is because when the wireless environment changes, the next hop that allows more stable communication also changes.

[0232] A plurality of blinking methods may be provided. The first blinking method is a method in which the brightness gradually increases and gradually decreases, repeatedly. The first blinking method may be applied, for example, to a state in which a connection to the additional wireless network 209 is being attempted (orange blinking) and a state in which a connection to the industrial wireless network 204 is being attempted (green blinking). The second blinking method is a method in which lighting at a first brightness (e.g., 100%) and lighting at a second brightness (e.g., 0%) are repeated. The cycle of the first blinking method may be longer than the cycle of the second blinking method. That is, the first blinking method may be a method in which the brightness changes gradually. On the other hand, the second blinking method may be a method in which the brightness changes more quickly. The second blinking method may be adopted for the highlighted lighting described above.

[0233] <First Use Case> The industrial wireless network 204 described above can be used for various purposes and applications in the FA field. For example, as the first use case, it can be used in the generation phase of the operation record, which has been described in detail using Figs. 1 to 12. This will be described with reference to Fig. 65.

[0234] FIG. 65 is a sequence diagram for explaining a case where data of the target device 203c is included as data periodically collected in the ring buffer 36 of the PLC1 (FIG. 3). As described above, various data are collected in the ring buffer 36 of the PLC1 to generate an operation record. For example, data obtained from the field device 10 connected to the extension unit 4b of the PLC1 by wire, that is, data obtained without going through the industrial wireless network 204 (through a wire), is collected at a scan period (for example, several ms or less) as a preset period. However, when trying to obtain data from the target device 203c through the industrial wireless network 204, it may be difficult to collect data at the scan period due to a delay (for example, several tens to several hundreds ms) caused by wireless communication.

[0235] Therefore, as shown in FIG. 65, an "update interval" is set, which determines the interval at which the PLC1 requests data from the target device 203c. Specifically, the user sets the update interval via the PC2, and the set update interval is stored in the project storage unit 35 of the PLC1. In addition, the user may set an IP address for identifying the location of the target device 203c via the PC2, or set information for identifying data to be collected in the target device 203c. For example, if another PLC is considered as the target device 203c (when the so-called PLC link function is used), an IP address for identifying the location of the other PLC may be set, and a device type, device number, number of words from the first device number, etc. to be collected in the other PLC may be set. Various information (such as an IP address) set in this way is stored in the project storage unit 35 of the PLC1.

[0236] In FIG. 65, the CPU 31 of the PLC1 communicates with the target device 203c based on the contents stored in the project storage unit 35. That is, the CPU 31 transmits a data request to the target device 203c via the master device 201, the slave device 202a, the slave device 202b, and the slave device 202c, which are connected to the CPU 31 by wire. The target device 203c that receives the data request transmits the data previously specified (set) as described above to the PLC1 via the slave device 202c, the slave device 202b, the slave device 202a, and the master device 201. The PLC1 stores the received data in the ring buffer 36. By repeating the data request and data transmission as described above at the predetermined update interval, the time series data from the target device 203c is collected in the ring buffer 36 of the PLC1. In this case, in the ring buffer 36, data collected at the scan period (data obtained from the field device 10) and data collected at the predetermined update interval (target device 203c) are mixed. Thereafter, when the storage trigger condition is satisfied, data for a predetermined period of time out of the data stored in the ring buffer 36 is stored in the driving record storage unit 37, and a driving record is generated. Note that the predetermined period for determining the data to be stored may be set by the user via the PC 2, and stored in the project storage unit 35 of the PLC 1.

[0237] In this way, according to the first use case, it is possible to include data from the target device 203c in the operation record via the industrial wireless network 204. In this embodiment, the ring buffer 36 for generating the operation record is provided in the PLC 1, but the present invention is not limited to this, and may be provided, for example, in the master unit 201. In the industrial wireless system according to this embodiment, the master unit (management unit) and the slave unit (wireless communication circuit) are separated, so that such functional expansion of the master unit 201 can be easily performed.

[0238] <Second Use Case> As a second use case, the industrial wireless network 204 can also be used to check the analysis report of the driving record generated in the first use case.

[0239] Specifically, as described above, the expansion unit (analysis unit) 4a of the PLC1 creates an analysis report of the driving record stored in the driving record storage unit 37, and provides it to a web browser outside the PLC. An example of a device having a web browser is the PC2. As shown in FIG. 14 and FIG. 28, the PC2 may be wirelessly connected not only to the master unit 201, but also to any of the slave units 202a to 202f constituting the industrial wireless network 204. For example, the PC2 connected to the slave unit 202c reads out and plays back the analysis report from a memory in which the analysis report is stored (the driving record storage unit 37 if the analysis report is included in the driving record. A memory in which the analysis report is stored other than the driving record storage unit 37 may be provided separately) via the master unit 201, the slave units 202a, the slave units 202b, and the slave units 202c.

[0240] In this case, by setting the update interval (Figure 65) as described above to an interval that takes into account delays caused by wireless communication, it becomes easy to smoothly repeat the repeated reading and playing of parts of the analysis report, like so-called streaming playback. Of course, it is also possible to first download the entire analysis report to PC2, and then play the analysis report on PC2.

[0241] <Third Use Case> As another example, as a third use case, the industrial wireless network 204 can also be used to monitor time-series device values ​​acquired in real time from the PLC 1.

[0242] As described above, the PC2 may be wirelessly connected to any one of the slave units 202a to 202f constituting the industrial wireless network 204. As in the second use case, when connected to the slave unit 202c, data must pass through the slave units 202c, 202b, 202a, and the master unit 201 in order to monitor the time-series device values ​​recorded in the PLC1. By setting an appropriate update interval, it is possible to monitor the time-series device values ​​recorded in the PLC1. As described above, the PC2 may be replaced with a programmable display.

[0243] <Fourth Use Case> As another example, as a fourth use case, the industrial wireless network 204 can also be used for debugging a ladder program executed in the PLC1.

[0244] Conventionally, in order to debug a ladder program, the system designer had to go to the location where the PLC 1 is installed, connect the PC 2 to the ladder program, and debug while verifying the operation of the PLC 1. However, by utilizing the industrial wireless network 204 according to this embodiment, it is possible to debug the ladder program without going to the location where the PLC 1 is installed.

[0245] Specifically, a user may edit a ladder program on PC2 connected to the slave unit 202c, and transfer the edited ladder program to PLC1 via the industrial wireless network 204, or send an operation trial command to PLC1.

[0246] <Handset case and indicator light> FIG. 50 shows the housing 400 of the child device 202. The housing 400 has a substantially rectangular parallelepiped shape. Between the top surface 401 and the bottom surface 402, there are a side surface 403 and an exhaust port 404. The exhaust port 404 is provided at the upper part of the side surface 403 or between the top surface 401 and the side surface 403. The side surface 403 includes four side surfaces 403a to 403d. The exhaust port 404 may be provided over the entire circumference above the side surfaces 403a to 403d. The exhaust port 404 may have a structure with multiple slits in order to support the top surface 401 and to increase the efficiency of exhausting air.

[0247] The indicator light 224a is disposed across the three side surfaces 403a, 403c, and 403d so that the indicator light 224a can be seen from a distance within the factory.

[0248] The optional second indicator light 224b is positioned across three sides 403b, 403c, and 403d, again so that the indicator light 224b can be seen from a distance within the factory.

[0249] Such an arrangement of the indicator lights 224a, 224b will help to visually confirm the child unit 202 from almost all directions.

[0250] FIG. 51 is a diagram showing the bottom surface 402 of the child unit 202. The bottom surface 402 has a LAN port 38i, a power connector 412, and an air inlet 411. A LAN cable from an industrial device (e.g., a machine tool) or the parent unit 201 is connected to the LAN port 38i. A power cable is connected to the power connector 412. A number of air inlets 411 are provided on the bottom surface 402. Air taken into the housing 400 from the air inlets 411 passes through the inside of the housing 400 and is exhausted from the exhaust outlet 404. This allows the electrical components arranged inside the housing 400 to be efficiently cooled. In other words, the air inlets 411 are provided on the bottom surface 402 and the exhaust outlet 404 are provided near the top surface 401 in order to enhance cooling performance by the chimney effect. Particularly, in this embodiment, air passes along the longitudinal direction of the housing 400 having a shape of a substantially rectangular parallelepiped. In other words, the air flow path is relatively long. Therefore, by utilizing the chimney effect, air can easily flow inside the housing 400 having a substantially rectangular parallelepiped shape.

[0251] FIG. 52 shows LEDs 431-434 and a diffusion member 420 constituting the indicator light 224. Indicator light 224a and indicator light 224b have the same structure, and are therefore described as indicator light 224. LEDs 431 and 432 are mounted on a first mounting surface 438 of a circuit board 430 that is vertically placed in the housing 400. LEDs 433 and 434 are mounted on a second mounting surface 439 of the circuit board 430. Here, LEDs 431 and 433 are side-emitting light-emitting diodes that emit light in a direction parallel to the circuit board 430 (in the -Y direction). Here, the light emission direction refers to the direction in which the light intensity is at its peak in the light radiation distribution. LEDs 432 and 432 are vertical-emitting light-emitting diodes that emit light in a direction parallel to the normal direction of the circuit board 430 (in the -X direction or +X direction). That is, the light emission direction (peak intensity direction) of LED 432 is parallel to the normal direction of first mounting surface 438. The light emission direction (peak intensity direction) of LED 434 is parallel to the normal direction of second mounting surface 439.

[0252] The diffusion member 420 includes a diffusion plate 421 and a diffusion plate 422. A space is provided between the diffusion plates 421 and 422, making it possible to reduce unevenness in the amount of light.

[0253] FIG. 53 shows a state in which the housing 400 is removed. The circuit board 430 is vertically disposed in the approximate center inside the housing 400. Two heat sinks, 452b and 452c, are disposed on the second mounting surface 439 side of the circuit board 430. The heat sink 452b and the heat sink 452c may be integrated. Two heat sinks, 452a and 452d, are disposed on the first mounting surface 438 side of the circuit board 430. The heat sinks 452a to 452d have at least two bent portions 453. That is, the heat sinks 452a to 452d with a large heat dissipation area are formed by bending a metal plate at least in two places. In FIG. 53, the heat sinks 452a and 452d are difficult to see, but have almost the same structure as the heat sinks 452b and 452c.

[0254] Arrow F indicates the flow of air. The air entering from intake port 411 rises due to the chimney effect, removes heat from heat sinks 452a to 452d, and is exhausted from exhaust port 404 provided above. This makes it possible to efficiently cool the inside of child device 202 without providing an air fan. Note that at least one of an intake air fan or an exhaust air fan may be provided.

[0255] The frame 454 is a supporting member made of resin that supports the circuit board 430. The frame 454 may be integrated with the bottom surface 402.

[0256] Four antennas 451 are disposed near top surface 401 inside housing 400. Each of the four antennas 451 faces in a different direction by 90 degrees. This allows child device 202 to cover almost all directions.

[0257] 54 is a schematic side view for explaining the circuit boards 430a, 430b, and 461. In this example, the circuit boards 430a, 430b, and 461 are independent of each other, but may be realized by a single circuit board. The circuit board 461 is mounted with the CPU 220, the storage device 221, the SDR 226 (WLAN modules 223a to 223c), and the LAN module 222. These are protected by a metallic shield cover 465. In other words, the shield cover 465 reduces external noise. The circuit board 461 is provided with antenna connectors 464 corresponding to the four antennas 451, one by one.

[0258] The indicator lamp 224a is composed of diffusion plates 421a and 422a, a circuit board 430a, and LEDs 431a, 432a, 433a, and 434a. In Fig. 54, the LEDs 431a and 432a are omitted.

[0259] The indicator lamp 224b is composed of diffusion plates 421b, 422b, a circuit board 430b, and LEDs 431b, 432b, 433b, and 434b. In Fig. 54, the LEDs 433b and 434b are omitted from the illustration.

[0260] FIG. 55 is a horizontal cross-sectional view of the child device 202 near the indicator lamps 224a and 224b. In this example, light guide members 423a and 423b are provided. The light emitted from the LEDs 431a and 433a is guided by the light guide member 423a, enters the diffusion plate 422a, and is diffused. In addition, a plurality of grooves and peaks extending parallel to the Z direction are formed on the opposing surfaces of the light guide member 423a and the diffusion plate 422a, and the grooves of the light guide member 423a and the peaks of the diffusion plate 422a engage with each other, and the peaks of the light guide member 423a and the grooves of the diffusion plate 422a engage with each other. This increases the diffusion rate of light and reduces unevenness in the amount of light. In addition, it is possible to reduce the distance from the LEDs 431a and 433a to the diffusion plates 422a and 421a. The LEDs 432a and 434a are not provided with a light guide member 423a. This is because a sufficient distance is secured between the LEDs 432a and 434a and the diffusion plates 422a and 421a. When a sufficient distance is secured, light can be expected to be diffused by the atmosphere.

[0261] The light emitted from the LED 431b and the LED 433b is guided by the light guide member 423b, enters the diffusion plate 422b, and is diffused. In addition, a plurality of grooves and peaks extending parallel to the Z direction are formed on the opposing surfaces of the light guide member 423b and the diffusion plate 422b, and the grooves of the light guide member 423b and the peaks of the diffusion plate 422b engage with each other, and the peaks of the light guide member 423b and the grooves of the diffusion plate 422b engage with each other. This further increases the diffusion rate of light and reduces unevenness in the amount of light. In addition, it is possible to reduce the distance from the LED 431b and the LED 433b to the diffusion plates 422b and 421b. In addition, the light guide member 423b is not provided for the LED 432b and 434b. This is because the distance from the LED 432b and 434b to the diffusion plates 422b and 421b is sufficiently secured.

[0262] <Attachment member for child unit 202> The slave unit 202 is assumed to be installed in a factory, and is therefore required to be easily attached to a metal frame, a square pillar, a pole, or the top surface of an industrial device (or a control box) present in the factory.

[0263] 56 shows an L-shaped mounting member 500 for fixing child unit 202 to aluminum frame 510. Mounting member 500 is a bracket having a top panel 501 and a side panel 502. Side panel 502 is provided with a plurality of through holes 503. Side panel 502 is fixed to aluminum frame 510 by inserting screws 504 into through holes 503 and screwing them into aluminum frame 510. Note that if a pole is present instead of aluminum frame 510, a U-bolt is used instead of screw 504.

[0264] When aluminum frame 510 is replaced with an iron square pillar, a plate-shaped magnet may be used for side panel 502. In this case, side panel 502 can be fixed to the iron square pillar without using screws 504. Such a magnet is useful for changing the installation position of child device 202 many times in order to optimize the installation position of child device 202.

[0265] 57 shows a mounting member 550 for fixing the slave unit 202 to a top surface or the like of an industrial device. The mounting member 550 is a bracket including a top panel 551, a side panel 552, and a bottom panel 554. The bottom panel 554 has through holes 553 for screwing to a top surface or the like of the industrial device. The top panel 551 supports the bottom surface 402 of the slave unit 202. The side panel 552 is connected to the top panel 551 and the bottom panel 554. In order to increase the rigidity of the side panel 552, the horizontal cross section of the side panel 552 is U-shaped.

[0266] 57, a resin adapter 506 is provided between top panel 551 and bottom surface 402. Adapter 506 is fixed by fitting into or screwing to top panel 551 and bottom surface 402, respectively. Adapter 506 may be screwed to top panel 551 by screws 507.

[0267] If the top surface of the industrial equipment is made of iron, a plate-shaped magnet may be attached to the bottom plate 554. In this case, it becomes possible to fix the bottom plate 554 to an iron plate (such as the top surface of the industrial equipment) without using screws.

[0268] FIG. 58 shows a communication space 555 provided in a top panel 551. The communication space 555, which is an opening, is provided in the approximate center of the top panel 551. As described above, in the present invention, the LN port 38i, the power connector 412, and the air intake 411 are all disposed on the bottom surface 402. Furthermore, the bottom surface 402 is supported by the top panels 501, 551 of the mounting members 500, 550. Thus, the communication space 555 is formed in the top panels 501, 551 of the mounting members 500, 550. This makes it easier for air to be taken in through the air intake 411. In addition, a power cable can be connected to the power connector 412. In addition, it is easier to connect a LAN cable to the LAN port 38i.

[0269] In order to facilitate the connection of the power cable to the power connector 412 and the connection of the LAN cable to the LAN port 38i, it is required that a human hand can easily reach between the top plate 551 and the bottom plate 554. For example, the bottom plate 554 is not provided as in the mounting member 500, or a sufficient distance is required to be secured between the top plate 551 and the bottom plate 554 of the mounting member 550. Alternatively, a structure that allows the child unit 202 to be easily detached from the mounting members 500 and 550 may be adopted. In this example, a resin adapter 506 having four claws 562 is provided. The top plates 501 and 551 have four notches 561 into which the four claws 562 are inserted. The adapter 506 is screwed to the bottom surface of the child unit 202. Thereafter, the four claws 562 are inserted into the corresponding four notches 561, and the adapter 506 is rotated horizontally together with the child unit 202 (broken line arrow). As a result, the four claws 562 engage with the top panels 501 and 551 .

[0270] In this way, the slave unit 202 may be fixed to the top plates 501 and 551 by the claws 562 of the adapter 506. In addition, in order to suppress the rotation of the adapter 506 with respect to the top plates 501 and 551, a screw 507 may be screwed into the top plates 501 and 551 through the adapter 506.

[0271] <LED Connection Form> When the LEDs 431 to 434 have the same light emission amount respectively, since the LEDs 431 and 433 are facing in the same direction, the light amount in this direction will increase. On the other hand, in order to individually control the LEDs 431 to 434 by the CPU 220, the peripheral circuit will increase. In particular, when the LEDs 431 to 434 respectively have a red light emitting diode, a blue light emitting diode, and a green light emitting diode, the peripheral circuit can be tripled. Therefore, in this embodiment, a circuit configuration that can simplify the peripheral circuit is proposed.

[0272] FIG. 59 shows the drive circuit of the LEDs 431 to 434. A current source 560 that is controlled by the CPU 220 to generate a drive current i is connected to the LEDs 431 to 434. The drive current i flows through the LEDs 431 to 434.

[0273] The LEDs 431 and 433 that emit light in the same direction are connected in parallel. That is, the LEDs 431 and 433 are connected in parallel to the current source 560. If the LEDs 431 and 433 are the same product, their internal resistances are equal (manufacturing variations are ignored). Therefore, the drive current flowing through the LEDs 431 and 433 is i / 2. There may be a significant difference between the internal resistance of the LED 431 and the internal resistance of the LED 433. In this case, by introducing a current mirror circuit, it is possible to make the current flowing through the LED 431 and the current flowing through the LED 433 equal. For example, the current mirror circuit may generate a current equal to the current flowing through the LED 431 and pass the generated current through the LED 431. Alternatively, the current mirror circuit may generate a current equal to the current flowing through the LED 433 and pass the generated current through the LED 433. The current mirror circuit is generally formed by at least two bipolar transistors. Although a variation corresponding to the variation between the two bipolar transistors occurs in the current generated by the current mirror circuit, this does not become a big problem because the variation between the two bipolar transistors is small compared to the variation between the internal resistance of the LED 431 and the internal resistance of the LED 433. In addition, the current mirror circuit makes it possible to make the current flowing through the LED 431 and the current flowing through the LED 433 approximately 1 / n (n is a positive integer). The value of n is set so that the luminance unevenness of the LED 433 formed by the LEDs 431 to 434 is reduced. n may be, for example, 3.

[0274] The LED 432 and the LED 434 are connected in series to a parallel circuit made up of the LEDs 431 and 433. That is, the LEDs 431 and 433 are connected in series to the current source 560. Therefore, the drive current flowing through the LEDs 432 and 434 is i.

[0275] Generally, the amount of light emitted by the LEDs 431 to 434 correlates with the drive current, so that unevenness in the amount of light in each radiation direction is reduced.

[0276] The driving circuit shown in Fig. 59 may be required for each of the red light emitting diode, the blue light emitting diode, and the green light emitting diode. The CPU 220 controls the three driving circuits individually, so that the LEDs 431 to 434 can realize various lighting colors, brightness, and lighting forms. For example, the CPU 220 can realize any lighting color according to a user's instruction by changing the ratio of the driving current flowing through the red light emitting diode, the blue light emitting diode, and the green light emitting diode.

[0277] <Grouping of child devices> In a large factory, multiple child machines 202 may be grouped (e.g., mesh cluster). In this case, it would be convenient to visually distinguish which child machine 202 belongs to which group in the factory.

[0278] The CPU 210 of the parent device 201 may store the child device list 253 for each mesh cluster in the storage device 211. Furthermore, the CPU 210 may store a lighting setting for each child device list 253 in the storage device 211. For example, the lighting setting may be part of the setting information 254.

[0279] FIG. 60 shows an example in which the lighting color of the indicator lamp 224 is different for each mesh cluster. The first group 601 is composed of the child devices 202a, 202b, and 202c. For example, the first child device list 253 for the first group 601 stored in the storage device 211 stores the identification information of the child devices 202a, 202b, and 202c. The parent device 201 sets the lighting color of the first group 601 to blue lighting in response to a user input. For example, the parent device 201 may set the lighting setting included in the setting information 254 linked to the first child device list 253 to blue lighting.

[0280] The second group 602 is composed of the child devices 202d, 202e, and 202f. For example, the second child device list 253 for the second group 602 stored in the storage device 211 stores identification information for each of the child devices 202d, 202e, and 202f. The parent device 201 sets the lighting color of the second group 602 to green lighting in response to a user input. For example, the parent device 201 may set the lighting setting included in the setting information 254 linked to the second child device list 253 to green lighting.

[0281] The CPU 210 distributes, to the desired child device 202, the setting information 254 associated with the child device list 253 to which the desired child device 202 belongs, according to the setting change process shown in Fig. 46. The CPU 220 of the desired child device 202 controls the lighting color of the indicator light 224 according to the lighting setting included in the setting information 254 received from the parent device 201. Specifically, the CPU 220 of the child devices 202a, 202b, and 202c performs blue lighting according to the lighting setting included in the setting information 254. The CPU 220 of the child devices 202d, 202e, and 202f performs green lighting according to the lighting setting included in the setting information 254. This makes it possible to change the lighting color for each mesh cluster (group).

[0282] <Method of lighting the indicator light to show the communication partner> In FIG. 61, the indicator lights 224a and 224b are turned on or off depending on the child device 202 that is the wireless communication partner. The CPU 210 of the parent device 201 sets the lighting conditions of the indicator lights 224a and 224b according to the wireless communication state (network connection state) according to the user input, and stores the lighting conditions in the setting information 254 of each child device 202. The setting information 254 of the child device 202a includes a setting condition such that, when the child device 202a is connected to the child device 202b, the indicator light 224a is turned off and the indicator light 224b is turned on. Of the two indicator lights 224a and 224b of the child device 202a, the indicator light 224b facing the child device 202b is turned on, and the indicator light 224a not facing the child device 202b is turned off. This makes it possible to visually indicate in which direction the child device 202a is connected to.

[0283] The setting information 254 of the child device 202b includes a setting condition such that, when the child device 202b is connected to the child device 202a, the indicator light 224b is turned off and the indicator light 224a is turned on. Of the two indicator lights 224a and 224b of the child device 202b, the indicator light 224a facing the child device 202a is turned on and the indicator light 224b not facing the child device 202a is turned off. This makes it possible to visually indicate in which direction the child device 202b is connected to.

[0284] 62 shows yet another example. In this example, the setting information 254 of the child device 202b further includes a setting condition that, when the child device 202b is connected to the child device 202c, the indicator light 224b is turned on. Of the two indicator lights 224a and 224b of the child device 202b, the indicator light 224b facing the child device 202c is turned on.

[0285] The setting information 254 of the child device 202c includes a setting condition such that when the child device 202c is connected to the child device 202b, the indicator light 224b is turned off and the indicator light 224a is turned on. Of the two indicator lights 224a and 224b of the child device 202c, the indicator light 224a facing the child device 202b is turned on and the indicator light 224b not facing the child device 202b is turned off. This makes it possible to visually indicate in which direction the child device 202a, the child device 202b, and the child device 202c are connected to the child device 202 located.

[0286] In this way, which indicator light 224 is turned on when which child unit 202 is connected is set based on a user input. The setup operator knows the relative positions of each child unit 202 when installing the child units 202 in a factory. This is because the setup operator can visually grasp the relative positions of each child unit 202 by forcibly turning on the child units 202 during setup work.

[0287] 61 and 62, the direction in which the communication partner is located is indicated by turning on and off the indicator light 224, but this is merely an example. For example, when the child device 202a and the child device 202b are connected, the lighting color (or blinking cycle) of the indicator light 224 of the child device 202a and the lighting color (or blinking cycle) of the indicator light 224 of the child device 202b may be controlled to be the same. This allows the user to visually grasp which child device 202 is connected to which child device 202.

[0288] <Distinguishing between direct and indirect waves> When arranging a large number of slave units 202 in a factory, it is not easy to optimize the installation positions of each slave unit 202. This is because a large number of industrial devices are installed in a factory, and they may move. From experience, communication by direct waves has fewer communication errors and is more stable than communication by indirect waves. Therefore, an installation worker desires that communication between each slave unit 202 be by direct waves as much as possible. However, in a factory, it is not easy to distinguish whether each slave unit 202 is communicating by direct waves. In general, each slave unit 202 monitors the signal strength of the signal received from the surrounding slave units 202. When a certain slave unit 202 detects that the slave unit 202 transmitting the strongest signal strength has changed, it changes the connection partner to the slave unit 202 transmitting the strongest signal strength, and reconstructs the wireless mesh network. In this way, it is possible to reconstruct the wireless mesh network based on the signal strength, but if the direct wave or the indirect wave is taken into consideration, a more stable network can be constructed.

[0289] Fig. 63 shows a method for distinguishing between direct waves and indirect waves. The child device 202 has a light receiving element 700. For example, if the light receiving element 700 can receive light from the indicator light 224 of the other child device 202b, the CPU 220 of the child device 202a determines that the child devices 202a and 202b can communicate with each other by direct waves. This is because light travels in a more straight line than radio waves.

[0290] However, in a case where there are many child devices 202, it may be impossible to distinguish which child device 202 the light receiving element 700 is receiving light from. Therefore, the CPU 220 of the other child device 202 sets the lighting cycle of the indicator light 224 to a unique cycle. In other words, the lighting cycle of the other child device 202 is different from the lighting cycle of yet another child device 202. In this way, the CPU 220 of the child device 202 may measure the lighting cycle of the light received by the light receiving element 700, and identify the other child device 202 that can communicate by direct wave based on the lighting cycle.

[0291] The CPU 210 of the parent device 201 may store the lighting cycle of each child device 202 in the child device list 253 or may store it in the setting information 254 for each child device 202. The parent device 201 may receive an inquiry signal of another child device 202 corresponding to the lighting cycle from any of the child devices 202. The CPU 210 replies by including in a reply signal the identification information of the other child device 202 corresponding to the lighting cycle contained in the received inquiry signal. The child device 202 that has made the inquiry may identify the other child device 202 that can communicate by direct waves based on the reply signal from the parent device 201. Alternatively, each child device 202 may hold the child device list 253 in the storage device 221. In this case, the CPU 220 may identify the identification information of the other child device 202 corresponding to the lighting cycle from the child device list 253 stored in the storage device 221.

[0292] This allows the CPU 220 of each child device 202 to change the priority of the child device 202 that will be a partner when establishing a wireless mesh network. For example, the CPU 220 may increase the priority of other child devices 202 that can receive direct waves and decrease the priority of other child devices 202 that cannot receive direct waves.

[0293] Note that the WLAN module 223 may have a function for measuring a round trip time (RTT). In this case, the CPU 220 may measure the RTT using the WLAN module 223, and distinguish whether the wave is a direct wave or an indirect wave based on the RTT. For example, the WLAN module 223 may have location information of the slave device 202 that is the communication partner, or information on the line-of-sight distance X_LOS between the slave device 202 equipped with the WLAN module 223 and another slave device 202 that is the communication partner. In this case, if the distance X calculated from the RTT is approximately equal to the line-of-sight distance X_LOS, the WLAN module 223 can determine that the measured RTT is due to a direct wave. If the distance X calculated from the RTT is longer than the line-of-sight distance X_LOS, the WLAN module 223 can determine that the measured RTT is due to an indirect wave.

[0294] The light receiving element 700 may be, for example, a photodiode, a photoelectric sensor, or an image sensor.

[0295] <Creating a layout map> In order to manage equipment (e.g., industrial equipment, child devices 202, etc.) installed in a factory, a layout map of the equipment may be created. At this time, the installation position of the child device 202 may be changed to stabilize wireless communication or for other reasons. In this case, it may be troublesome for the user to manually rewrite the layout map.

[0296] 64 shows network cameras 801a to 801c for creating a layout map. Generally, the installation positions of the network cameras 801a to 801c are fixed in a factory. In other words, the installation positions of the network cameras 801a to 801c in the layout map are unchanging.

[0297] The parent device 201 can communicate with the network cameras 801a to 801c and acquires images (moving images or still images) from each of them. The parent device 201 analyzes the three images acquired from the network cameras 801a to 801c and calculates the installation position of each child device 202. If a specific child device 202 is captured in the three images, the direction from the network cameras 801a to 801c to the specific child device 202 is determined. As described above, the installation positions of the network cameras 801a to 801c are fixed. Therefore, the CPU 210 of the parent device 201 draws three lines from the installation positions of the network cameras 801a to 801c to the specific child device 202 on the layout map. The CPU 220 determines the position where the three lines intersect and specifies that position as the installation position of the specific child device 202. The CPU 210 writes the installation position of the specific child device 202 in the layout map. This makes it possible to dynamically reflect the installation positions of multiple child devices 202 on the layout map.

[0298] In order to identify a specific child unit 202 in the three images, the parent unit 201 may light up the indicator light 224 of the specific child unit 202 in a unique lighting mode (e.g. lighting color, lighting cycle). The lighting mode of each child unit 202 may be stored in the child unit list 253. This allows the CPU 210 to identify the lighting mode of the indicator light 224 in the image, and obtain the identification information of the child unit 202 corresponding to that lighting mode from the child unit list 253. This allows the CPU 210 to identify the child unit 202 that appears in common in the three images.

[0299] In this example, three network cameras 801a to 801c are used, but more network cameras 801 may be installed. The CPU 210 of the parent unit 201 can analyze the installation position of a specific child unit 202 by analyzing at least three images in which the specific child unit 202 appears, among the N images acquired from the N network cameras 801.

[0300] If some degree of error is allowed, the CPU 210 can analyze the installation position of a particular child unit 202 by analyzing at least two images.

[0301] Furthermore, if the size of the housings 400 of the child units 202 is the same, the CPU 210 can analyze the installation position of a specific child unit 202 by analyzing at least one image. The CPU 210 can calculate the distance and direction from the network camera 801 to the child unit 202 from the size and position of the housing 400 of the child unit 202 captured in the image. The CPU 210 can determine the installation position of the child unit 202 from the installation position of the network camera 801 and the distance and direction of the child unit 202.

[0302] The slave unit 202 may be attached to an automated guided vehicle that moves around in a factory. In this case, the master unit 201 can obtain the installation position of the slave unit 202 as the current position of the automated guided vehicle.

[0303] <Technical ideas derived from the embodiment> [Perspective A1] A network controller that acts as a parent device (e.g., parent device 201), A plurality of wireless nodes (e.g., child device 202) managed by the network controller and operating as child devices; 1. An industrial wireless system comprising: The network controller includes: a first port (e.g., LAN port 38e) that is wired to a first wired network; a plurality of second ports (e.g., LAN port 38h) connected by wire to at least one wireless node that operates as a root node among the plurality of wireless nodes; The plurality of wireless nodes include a third port (e.g., LAN port 38i) that is connected to an industrial device by wire or that is connected to the second port of the network controller by wire when the third port operates as the root node; a wireless module (e.g., a WLAN module 223) that wirelessly connects to another wireless node that is a next hop among the plurality of wireless nodes; The network controller further comprises: The wireless network may further include a management unit (e.g., a CPU 210) that manages a wireless network formed by the plurality of wireless nodes. The management unit searches for a wireless node (e.g., child device 202a) to be operated as the root node connected to the second port, and when the wireless node is found, sets configuration information (e.g., setting information 254) for constructing the wireless network among the plurality of wireless nodes in the wireless node, and the wireless node operating as the root node transfers the configuration information to at least one of the other wireless nodes among the plurality of wireless nodes excluding the root node, in an industrial wireless system.

[0304] In this way, by separating the master unit (management section) and the slave unit (wireless communication circuit), the flexibility of constructing an industrial wireless system is increased. For example, it becomes easier to replace a slave unit. Replacing a slave unit can be realized, for example, by deleting the old slave unit and adding a new slave unit. Since the master unit 201 holds the setting information 254 of the old slave unit, the new slave unit can be added to the industrial wireless network 204 by transferring the setting information 254 to the new slave unit. This will reduce the effort and time required by the user to replace a slave unit.

[0305] [Perspective A2] Further comprising a setting device (e.g., PC2) connected to the network controller; The setting device instructs the network controller to add a new child device (S41, Sq1), In response to receiving the instruction, the network controller sets each of the wireless nodes to a child device addition mode (e.g., Sq2); When the wireless nodes are set to the child device addition mode, they start detecting access of the new child device (e.g., Sq4), and when access of the new child device is detected, they report unique identification information of the new child device to the network controller (e.g., Sq5); The industrial wireless system described in aspect A1, wherein when the reported addition of the new child device is approved by the setting device (Sq12), the network controller transfers the configuration information to the new child device (e.g., Sq13, Sq14).

[0306] In this manner, the user may instruct the addition of a new child device via the PC 2. When the parent device 201 and the existing child devices transition from the normal mode to the child device addition mode, they enter a state in which addition of a new child device 202 is permitted. When the addition of a new child device is approved by the setting device, the setting information 254 is transferred to the new child device, and the new child device becomes able to participate in the industrial wireless network 204. This allows the user to manage the child device 202 to be added to the industrial wireless network 204.

[0307] [Perspective A3] The industrial wireless system of aspect A2, wherein the setting device is wired to the network controller or is connected to the network controller via at least one wireless node among the plurality of wireless nodes.

[0308] PC2 may be connected to parent device 201 with a LAN cable, or may be connected to any of child devices 202 via a LAN cable, or may be connected to any of child devices 202 via a WLAN module 223. In any case, PC2 is capable of communicating with parent device 201. Parent device 201 may function as a DHCP server that assigns an IP address to PC2. PC2 may be any of a notebook computer, a tablet terminal, a smartphone, and the like.

[0309] [Perspective A4] The industrial wireless system according to aspect A2 or A3, wherein the network controller has a screen providing means for providing a child device addition screen (e.g., addition screen 310) to the setting device.

[0310] By viewing the addition screen 310, the user can easily perform the task of adding a child unit.

[0311] [Point of View A5] The child device addition screen displays the wireless node detected as the new child device in a selectable manner (e.g., a check box 317), The industrial wireless system of aspect A4, wherein the network controller transfers the configuration information only to the wireless node selected on the child device addition screen.

[0312] This allows only the child devices 202 selected by the user to join the industrial wireless network 204. As a result, it is possible to prevent child devices 202 that are not intended by the user from joining the industrial wireless network 204. Such selective addition is also useful when multiple independent industrial wireless networks 204 are constructed in parallel at the same time within a factory.

[0313] [Point of View A6] Each of the wireless nodes has one or more indicator lights (e.g., indicator light 224); The industrial wireless system described in any one of viewpoints A1 to A5, wherein the management unit is configured to control the lighting of one or more indicator lights provided in each of the multiple wireless nodes.

[0314] As described above, the CPU 210 can highlight or turn off the indicator light 224. Furthermore, the CPU 210 can control the indicator light 224 to light up in green instead of orange by approving the addition of the child unit 202. In the above embodiment, one indicator light 224 is shown, but multiple indicator lights 224 may be provided in the child unit 202. In this case, the CPU 210 and the CPU 220 may collectively manage the lighting modes of the multiple indicator lights 224 through the addition screen 310.

[0315] [Point of View A7] The industrial wireless system of aspect A6, wherein the lighting settings of the one or more indicator lights include at least one of a lighting color (e.g., orange, green, red, yellow, etc.) and a lighting form (e.g., continuous lighting, flashing, increased brightness, etc.).

[0316] In this way, the lighting setting (lighting style) of the indicator lamp 224 may include the lighting color and the lighting style. Note that only the lighting color or only the lighting style may be changed.

[0317] [Point of View A8] The industrial wireless system described in Viewpoint A6 or Viewpoint A7, wherein the management unit accepts selection of at least one wireless node among the plurality of wireless nodes, and lights up the one or more indicator lights provided on the at least one wireless node in a lighting color or lighting form different from the one or more indicator lights provided on other wireless nodes among the plurality of wireless nodes excluding the at least one wireless node.

[0318] As described with reference to FIG. 36 and FIG. 47, the selection of the child device 202 and the control of the indicator light 224 may be realized through the button 313. As described above, the indicator light 224 of an existing child device, which is a child device 202 that has already joined the industrial wireless network 204, lights up green. On the other hand, the indicator light 224 of an additional child device that has not yet joined the industrial wireless network 204 lights up orange or blinks orange. Furthermore, the indicator light 224 can also be highlighted. This allows the user to visually distinguish the various child devices 202. Generally, a large number of industrial devices and child devices 202 may be installed in a factory. Therefore, it may be important for the user to be able to visually distinguish the child devices 202.

[0319] [Point of View A9] The industrial wireless system of any one of points A1 to A8, wherein the wireless network is a mesh network.

[0320] The industrial wireless network 204 and the additional wireless network 209 may be mesh networks, but this is merely an example, and wireless networks of other topologies may be constructed.

[0321] [Point of View A10] The wireless module includes: a first wireless connection means (e.g., a WLAN module 223a) that is assigned a first network identifier based on the configuration information set by the parent device and connects to the wireless network; A second wireless connection means (e.g., a WLAN module 223b) that is assigned a second network identifier for adding a child device, which is known to the new child device, and wirelessly connects to the new child device; An industrial wireless system according to any one of points A1 to A9, comprising:

[0322] In this way, by providing a plurality of wireless connection means, it is possible to construct an additional wireless network 209 and add a child device 202 while maintaining the industrial wireless network 204. For example, it is possible to add a new child device 202 while maintaining communication between a plurality of industrial devices and the PLC 1 through the industrial wireless network 204. In other words, it is possible to add a new child device 202 without stopping the production line in the factory.

[0323] [Point of View A11] A network controller that operates as a master unit in an industrial wireless system, comprising: a first port for wired connection to a first wired network; a plurality of second ports connected by wire to at least one wireless node operating as a root node among a plurality of wireless nodes operable as child devices; a management unit for managing a wireless network formed by the plurality of wireless nodes, The management unit searches for a wireless node to be operated as the root node connected to the second port, and when the wireless node is found, sets configuration information for constructing the wireless network among the multiple wireless nodes in the wireless node, thereby causing the wireless node operating as the root node to transfer the configuration information to at least one other wireless node among the multiple wireless nodes excluding the root node.

[0324] [Point of View A12] A wireless node managed by a network controller that operates as a master for a plurality of wireless nodes in an industrial wireless system, A LAN port (e.g., LAN port 38i) that is connected to an industrial device by wire or that can be connected to the network controller by wire; a storage unit (e.g., a storage device 221) for storing configuration information acquired from the network controller through the LAN port when the network controller is connected to the LAN port; A first wireless module (e.g., a WLAN module 223a) that constructs an industrial wireless network in the industrial wireless system based on the configuration information and wirelessly connects to another wireless node that is a next hop among the plurality of wireless nodes; a second wireless module (e.g., a WLAN module 223b) that, when the network controller is not connected to the LAN port, constructs a wireless network for acquiring the configuration information required to construct the industrial wireless network based on prior knowledge, acquires the configuration information through the wireless network, and stores the configuration information in the storage means; A wireless node having a

[0325] [Point of View A13] A method for constructing an industrial wireless network in an industrial wireless system, comprising: The network controller acting as the parent device stores configuration information required to construct the industrial wireless network in a storage means (e.g., S5), The network controller searches for a root node, which is a wireless node connected to the network controller by wire (e.g., S11); When the root node is found, the parent device transfers the configuration information to the root node; The root node transfers the configuration information to a wireless node to be added as a child in the industrial wireless system (e.g., S14); The root node and the wireless node to be added as a child device construct the industrial wireless network based on the configuration information (e.g., S26). How to build an industrial wireless network.

[0326] The parent device 201 may transmit a search packet for searching for the child device 202a (root node) connected by wire through the LAN port 38. When the child device 202a is found, the parent device 201 transfers the setting information 254 to the child device 202a. At this time, the user may approve the addition of the child device 202a through the addition screen 310.

[0327] [Perspective B1] A network controller that acts as a parent device (e.g., parent device 201), A plurality of wireless nodes (e.g., child device 202) managed by the network controller and operating as child devices; 1. An industrial wireless system comprising: The network controller includes: a first port (e.g., LAN port 38d) that is wired to a first wired network; a plurality of second ports (e.g., LAN ports 38e to 38h) connected by wire to at least one wireless node that operates as a root node among the plurality of wireless nodes; Each of the plurality of wireless nodes a third port (e.g., LAN port 38i) that is connected to an industrial device by wire or that is connected to the second port of the network controller by wire when the third port operates as the root node; A wireless module (e.g., a WLAN module 223) that wirelessly connects to another wireless node that is a next hop among the plurality of wireless nodes; and an indicator light (e.g., indicator light 224); The network controller further comprises: The wireless network may further include a management unit (e.g., a CPU 210) that manages a wireless network formed by the plurality of wireless nodes. when an addition instruction for adding a new wireless node to the wireless network is input, the management unit sets the plurality of wireless nodes to a child unit addition mode, acquires unique identification information of the new wireless node from a wireless node that has found the new wireless node among the plurality of wireless nodes, and when an approval instruction for the new wireless node is input, allows the new wireless node to participate in the wireless network; The indicator light of the new wireless node among the plurality of wireless nodes is The new wireless node is not connected to any wireless network (e.g., blinking orange); A state in which the new wireless node is wirelessly connected to another auxiliary wireless network for acquiring configuration information for connecting to the wireless network (e.g., orange light); A state in which the device is connected to the wireless network according to the configuration information (e.g., a green light is on), An industrial wireless system with different lighting formats.

[0328] In this way, the industrial wireless system is installed in a factory where some kind of product is manufactured. In the factory, the layout of multiple industrial devices may be changed depending on the product being manufactured. In this case, it may be necessary to add a child device 202 or change the installation position. In such cases, being able to visually check the connection status of the child device 202 will be extremely useful for the worker who is building the industrial wireless system.

[0329] [Perspective B2] Further comprising a setting device (e.g., PC2) connected to the network controller; The setting device instructs the network controller to add a new child device (e.g., Sq1), In response to receiving the instruction, the network controller sets each of the wireless nodes to the child device addition mode (e.g., Sq2); When the plurality of wireless nodes are set to the child device addition mode, they construct the other auxiliary wireless network (e.g., Sq2, Sq4), start detecting access of the new child device to the other auxiliary wireless network, and when access of the new child device is detected, report unique identification information of the new child device to the network controller (e.g., Sq5); The industrial wireless system of aspect B1, wherein when additional approval is obtained for the reported new child device (e.g., Sq12), the network controller transfers the configuration information to the new child device (e.g., Sq13, Sq14).

[0330] [Perspective B3] When the management unit receives a deletion instruction for deleting at least one wireless node from the wireless network among the plurality of wireless nodes participating in the wireless network (e.g., S164), the management unit transmits a deletion request to the at least one wireless node (e.g., S166), The industrial wireless system of aspect B1 or B2, wherein the at least one wireless node is configured, upon receiving the deletion request (e.g., S181), to delete the configuration information and withdraw from the wireless network (e.g., S182).

[0331] In a factory, a manufacturing line is modified. At that time, some industrial equipment must be stopped or moved, and the slave units 202 connected to the industrial equipment must be stopped. In this case, the master unit 201 controls the deletion process, so that the desired slave unit 202 can be smoothly removed from the industrial wireless network 204.

[0332] [Perspective B4] the plurality of wireless nodes set to the child device addition mode are configured to construct the auxiliary other wireless network based on identification information (e.g., a mesh network identifier 282) dedicated to the child device addition mode, which is prior knowledge; The industrial wireless system of any one of aspects B1 to B3, wherein the new wireless node is configured to search for and attempt access to other auxiliary wireless networks that use the prior knowledge, which is identification information exclusive to the child device addition mode, as network identification information.

[0333] By using another wireless network for adding a child device in this manner, the security of the industrial wireless network 204 can be improved.

[0334] [Point of View B5] The industrial wireless system described in any one of aspects B1 to B4, wherein when the new wireless node joins the wireless network, the management unit configures each of the multiple wireless nodes to not allow other wireless nodes to join the wireless network (e.g., Sq16).

[0335] For example, by switching the slave unit 202 from the slave unit addition mode to the normal mode, it is possible to prevent an unintended slave unit 202 from accessing the wireless network. This will further improve the security of the industrial wireless network 204.

[0336] [Point of View B6] The industrial wireless system described in point B5, wherein the management unit does not allow other wireless nodes to join the wireless network by sending an instruction to terminate the child unit addition mode to the multiple wireless nodes (e.g., Sq16).

[0337] [Point of View B7] The indicator light of the new wireless node: When the new wireless node is not connected to either the wireless network or the auxiliary other wireless network, the new wireless node flashes in a first color (e.g., flashes orange); When the new wireless node is connected to the auxiliary other wireless network, the first color changes to a continuous light (e.g., orange light); An industrial wireless system according to any one of aspects B1 to B6.

[0338] This allows the construction worker to visually grasp the wireless status of the additional handset. For example, if the additional handset continues to flash in the first color and does not switch to a constant light, the cause may be that the distance between the additional handset and the existing handset is too far, there is too much noise, the existing handset has not been able to switch to the handset addition mode, etc. The construction worker will be able to easily solve the problem depending on the connection status of the additional handset.

[0339] [Point of View B8] The indicator light of the new wireless node: The industrial wireless system of aspect B7, wherein when the new wireless node connects to the wireless network, it lights up in a second color different from the first color (e.g., green).

[0340] Because the wireless environment is invisible, it may not be possible to immediately know whether the added slave unit has been successfully connected to the industrial wireless network 204. Therefore, by making it possible to know the status of the added slave unit by an indicator light, it will be possible to quickly confirm that the added slave unit has been successfully connected.

[0341] [Point of View B9] The industrial wireless system of any of aspects B1 to B8, wherein the indicator light of the new wireless node is configured to light up in a lighting format corresponding to the lighting request when it receives a lighting request from the network controller (e.g., highlight lighting).

[0342] This allows the construction worker to visually confirm whether the child unit he or she sees is the same as the child unit recognized by the system. Note that multiple types of highlighting may be prepared, and the user may select the type on the setting screen 300, the addition screen 310, or the deletion screen 320. For example, the type of highlighting may be changed cyclically each time the button 313 is pressed. In this case, it would be possible to switch between highlighting of multiple shells with one control object. Note that the icon of the button 313 may also change depending on the lighting format. By comparing the icon of the button 313 with the indicator light 224, the user would be able to know whether the request for highlighting is correct and has been transmitted to the child unit.

[0343] [Point of View B10] The industrial wireless system according to aspect B2, wherein the network controller has a screen providing means (e.g., CPU 210, screen providing unit 240) for providing a child unit addition screen to the setting device.

[0344] The screen providing means may be realized by a Web server. Incidentally, a part or all of the setting functions of parent device 201 may be implemented in PC2 by installing a setting program in PC2. In this case, parent device 201 may be implemented with software that transfers requests from PC2 to other child devices 202. However, even in this case, setting information 254 may be stored in parent device 201. This will make it more difficult for setting information 254 to be leaked to the outside.

[0345] [Point of View B11] The slave device addition screen displays the new wireless node in a selectable manner (e.g., FIG. 36 ), The industrial wireless system of aspect B10, wherein the network controller transfers the configuration information only to the wireless node selected on the child device addition screen.

[0346] For example, when multiple slave devices 202 are started up at the same time, it is possible that a slave device 202 that is not intended by the construction worker may connect to the additional wireless network 209. In this regard, if the construction worker specifies the transfer destination of the setting information 254, it will be possible to prevent an unintended slave device 202 from connecting to the industrial wireless network 204.

[0347] [Point of View B12] the screen providing means provides a child unit deletion screen (e.g., deletion screen 320) to the setting device; displaying the slave unit deletion screen in a selectable manner a plurality of wireless nodes registered in the wireless network; The industrial wireless system according to aspect B10 or B11, wherein the network controller transmits a request to delete the configuration information to a wireless node selected on the slave unit deletion screen.

[0348] By providing the slave unit deletion screen in this manner, the construction worker will be able to easily delete the slave unit 202 from the industrial wireless network 204. In particular, since configuration information (e.g., setting information 254) is deleted, it will be difficult for the deleted slave unit 202 to unintentionally access the industrial wireless network 204 again.

[0349] [Point of View B13] A network controller that operates as a master unit in an industrial wireless system, comprising: a first port for wired connection to a first wired network; a plurality of second ports connected by wire to at least one wireless node operating as a root node among a plurality of wireless nodes operable as child devices; a management unit for managing a wireless network formed by the plurality of wireless nodes, The management unit searching for a wireless node to be operated as the root node connected to the second port, and when the wireless node is found, setting configuration information for constructing the wireless network among the plurality of wireless nodes in the wireless node, thereby causing the wireless node operating as the root node to transfer the configuration information to at least one other wireless node among the plurality of wireless nodes excluding the root node; A network controller that controls an indicator light of the at least one other wireless node when the network controller is able to communicate with the at least one other wireless node via the root node.

[0350] In this way, by preparing a network controller separated from the wireless communication circuit, it will be easy to upgrade only the wireless node in which the wireless communication circuit is implemented. The wireless communication circuit often enables faster and more stable communication by updating the wireless standard. On the other hand, when replacing the wireless node, it is necessary to connect the PC2 to each wireless node and install the settings for the industrial wireless network 204. This was a very troublesome task. Because the wireless node is installed near the top surface of the industrial equipment or even higher, it is troublesome to connect a LAN cable to connect the PC2 there. In this embodiment, since the parent machine 201 holds the setting information 254, it will be possible to easily transfer the setting information 254 to the wireless node. This will make the factory manager proactive in updating the wireless node.

[0351] [Point of View B14] A wireless node managed by a network controller that operates as a master for a plurality of wireless nodes in an industrial wireless system, A LAN port that is connected to an industrial device by wire or that can be connected to the network controller by wire; a storage means for storing configuration information acquired from the network controller through the LAN port when the network controller is connected to the LAN port; a first wireless module that constructs an industrial wireless network in the industrial wireless system based on the configuration information and wirelessly connects to another wireless node that is a next hop among the plurality of wireless nodes; a second wireless module that, when the network controller is not connected to the LAN port, constructs a wireless network for acquiring the configuration information required to construct the industrial wireless network based on prior knowledge, acquires the configuration information through the wireless network, and stores the configuration information in the storage means; and an indicator light; The indicator light is a state in which the wireless node is not connected to any wireless network; A state in which the wireless node is wirelessly connected to another auxiliary wireless network for acquiring configuration information for connecting to the wireless network; a state in which the wireless network is connected in accordance with the configuration information; Each wireless node lights up in a different way.

[0352] In this way, the slave 202 connected to the master 201 by wire can obtain the setting information 254 from the master 201 via the wired connection. On the other hand, other slaves 202 not connected to the master 201 by wire can obtain the setting information 254 via the slave 202 connected to the master 201 by wire. In this way, since the slave 202 has both obtaining functions, the industrial wireless network 204 can be constructed without distinguishing between wired and wireless slaves. For example, it will be easy to convert a wired slave into a wireless slave, or a wireless slave into a wired slave. Suppose that the wired slave and the wireless slave are different products. In this case, if the wired slave breaks down, the industrial wireless network 204 will stop until a new wired slave is ordered and received. On the other hand, in this embodiment, other wireless slaves can be converted into wired slaves, so that the industrial wireless network 204 can be restored immediately.

[0353] [Point of View B15] A method for constructing an industrial wireless network in an industrial wireless system, comprising: A network controller operating as a master device stores configuration information required for constructing the industrial wireless network in a storage means, an indicator light of a wireless node to be added as a slave to the industrial wireless network is lit in a first lighting mode; The network controller searches for a wireless node that is wired connected to the network controller; When the wired wireless node is discovered, the master transfers the configuration information to the wired wireless node; The wired wireless node functions as a root node in the industrial wireless system, thereby transferring the configuration information to a wireless node to be added as a child device in the industrial wireless system; The root node and the wireless node to be added as the child device construct the industrial wireless network based on the configuration information, When the wireless node to be added as the child device joins the industrial wireless network, the indicator light of the wireless node is lit in a second lighting format. How to build an industrial wireless network.

[0354] [Point of View C1] A communication port (e.g. LAN port 38i) for connecting to industrial equipment on an industrial network, A circuit board (e.g., circuit board 461) on which a wireless module (e.g., WLAN module 223) for connecting to a wireless network and a network control circuit (e.g., CPU 220) for constructing the wireless network via the wireless module and transferring communication between the industrial device connected via the communication port and the wireless network are mounted; A housing (e.g., housing 400) that houses the vertically arranged circuit board; A first direction (e.g., −X direction) parallel to a normal direction of the first mounting surface of the circuit board; A second direction (e.g., +X direction) parallel to the normal direction of the second mounting surface of the circuit board; a third direction (e.g., −Y direction) parallel to the first mounting surface and the second mounting surface; a first indicator light (e.g., indicator light 224) that outputs light to the a control unit (e.g., an indicator light operation unit 262) that controls the lighting state of the first indicator light in accordance with the state of the wireless network; A wireless node (e.g., child device 202) having the following configuration:

[0355] By configuring the wireless node in this way, the visibility of the indicator light that lights up according to the status of the wireless network is improved. In particular, even if the wireless node is installed in a factory where many industrial devices are installed, it will be easy to check the indicator light. In other words, the visibility of the indicator light will be ensured.

[0356] For example, communication between multiple child devices 202 includes a backhaul section and a normal wireless communication section (between an access point and a station (wireless LAN terminal)). Of these, the backhaul section is a section where a larger number of packets are transmitted and received, and higher communication quality is required. A network administrator can easily understand the communication quality of each wireless section by visually checking the lighting status of the wireless nodes. For example, if the communication quality between multiple child devices 202 forming a backhaul section is low, it may be possible to move the position of the child device 202 or move obstacles to improve the communication quality.

[0357] The child device 202 dynamically repairs the wireless mesh network. For example, in FIG. 14, when the child device 202e cannot connect to the child device 202d, the child device 202e connects to another child device 202b, and dynamically repairs the wireless mesh network. In this way, when any child device 202 causes a communication error, the child device 202 may turn on the error indicator light 224 (e.g., blinking red). This allows the network administrator or operator to change the installation position of the child device 202 that is turning on the error indicator light, thereby assisting in the dynamic repair of the wireless mesh network.

[0358] [Perspective C2] The first indicator light (e.g., indicator light 224a) is A first light emitting element (e.g., LED 432) that outputs light in the first direction; A second light emitting element (e.g., LED 434) that outputs light in the second direction; A third light-emitting element (e.g., LED 431) that outputs light in the third direction; a first diffusing member (e.g., diffusing member 420) that diffuses the light from the first light emitting element, the light from the second light emitting element, and the light from the third light emitting element; The wireless node according to aspect C1,

[0359] By using a diffusing member in this way, it is possible to output light with less unevenness from the indicator lamp with a small number of light emitting elements. This will make the indicator lamp easier to see from various directions. In addition, since the circuit board is vertically oriented, this can be advantageous in terms of heat dissipation from the circuit board.

[0360] [Perspective C3] The first indicator lamp further includes a fourth light-emitting element (e.g., LED 433) that outputs light in the third direction, the first light emitting element is a vertical emission type light emitting element that is disposed on the first mounting surface and emits light in a normal direction to the first mounting surface, the second light-emitting element is a vertical emission type light-emitting element that is disposed on the second mounting surface and emits light in a normal direction of the second mounting surface, the third light-emitting element is a side-emitting light-emitting element that is disposed on the first mounting surface and emits light in a direction parallel to the first mounting surface, The wireless node according to viewpoint C2, wherein the fourth light-emitting element is a side-emitting light-emitting element that is arranged on the second mounting surface and emits light in a direction parallel to the second mounting surface.

[0361] As shown in the example of Figure 52, by arranging at least four light-emitting elements on the mounting surface, uneven diffusion of light can be reduced, making it possible to light the indicator light efficiently, and further improving the visibility of the indicator light.

[0362] [Perspective C4] The first diffusion member is A first diffusion plate (e.g., diffusion plate 421) facing the outside of the housing; A second diffusion plate (e.g., diffusion plate 422) disposed inside the housing; The wireless node according to aspect C2 or C3, comprising:

[0363] As shown in Figures 52 and 55, the diffusion member may be formed from a plurality of diffusion plates. This will reduce unevenness in light diffusion and improve visibility of the indicator light in various directions.

[0364] [Point of View C5] The housing has at least four sides (e.g., 403a to 403d), A wireless node according to any one of viewpoints C1 to C4, wherein the first indicator light is arranged across three of the at least four sides.

[0365] This will improve the visibility of the indicator light from three directions, each at 90 degrees apart.

[0366] [Point of View C6] The first direction; The second direction; a fourth direction opposite to the third direction; The wireless node of aspect C1 further includes a second indicator light (e.g., indicator light 224b) that outputs light to.

[0367] By providing a second indicator light in this manner, it will be possible to visually confirm the indicator light of the wireless node from almost all directions (at least four directions).

[0368] [Point of View C7] The second indicator light (e.g., indicator light 224b) is A fifth light emitting element (e.g., LED 434 of indicator light 224b) that outputs light in the first direction; A sixth light-emitting element (e.g., LED 432b of indicator light 224b) that outputs light in the second direction; A seventh light-emitting element (e.g., LED 433 of indicator light 224b) that outputs light in the fourth direction; a second diffusion member (e.g., diffusion member 420 of indicator light 224b) that diffuses the light from the fifth light-emitting element, the light from the sixth light-emitting element, and the light from the seventh light-emitting element; The wireless node according to aspect C6,

[0369] In this way, the multiple indicator lights may each have the same or similar structure, which is advantageous in terms of cost. In addition, redundancy can be realized in case an LED fails.

[0370] [Point of View C8] The second indicator light further includes an eighth light-emitting element (e.g., LED 431b of indicator light 224b) that outputs light in the fourth direction, the fifth light emitting element is a vertical emission type light emitting element that is disposed on the first mounting surface and emits light in a normal direction of the first mounting surface, the sixth light-emitting element is a vertical emission type light-emitting element that is disposed on the second mounting surface and emits light in a normal direction of the second mounting surface, the seventh light-emitting element is a side-emitting light-emitting element that is disposed on the first mounting surface and emits light in a direction parallel to the first mounting surface, The wireless node according to aspect C7, wherein the eighth light-emitting element is a side-emitting light-emitting element that is arranged on the second mounting surface and emits light in a direction parallel to the second mounting surface.

[0371] This will enable a small number of light-emitting elements to be arranged in a small housing, and the small number of light-emitting elements to emit light in various directions.

[0372] [Point of View C9] The second diffusion member (e.g., diffusion member 420) may be a third diffusion plate (e.g., diffusion plate 421b) facing the outside of the housing; A fourth diffusion plate (e.g., diffusion plate 422b) disposed inside the housing; The wireless node according to aspect C7 or C8, comprising:

[0373] By arranging multiple diffusion plates in this manner, it will be possible to emit light efficiently and with less unevenness in various directions.

[0374] [Point of View C10] The housing has at least four sides; A wireless node according to any one of viewpoints C7 to C9, wherein the second indicator light is arranged across three of the at least four sides.

[0375] This will improve the visibility of the indicator light from three directions, each at 90 degrees apart.

[0376] [Point of View C11] The housing has a top surface and a bottom surface, The bottom surface has a first ventilation hole (e.g., an intake port 411), A wireless node described in any of viewpoints C1 to C10, having a second ventilation hole (e.g., exhaust port 404) on the top surface or a side of the housing at a position higher than the first indicator light and lower than the top surface.

[0377] By adopting such an arrangement of ventilation holes, it is possible to improve the cooling efficiency inside the housing by using the chimney effect.

[0378] In FIG. 50 and the like, the exhaust port 404 is not provided on the top surface 401, but the exhaust port 404 may be provided on the top surface 401. However, by providing the exhaust port 404 on the side surface of the housing 400, dust in the factory will be less likely to enter the housing 404. On the other hand, although the exhaust port 404 is provided in this embodiment, there is a need to block the exhaust port 404 in a factory where dust and powder fly around. This is, for example, when IP67 compliance is required indoors. In this case, the heat dissipation performance of the entire wireless node is reduced. Therefore, for example, the housing 400 may be made larger to suppress the reduction in heat dissipation performance. Also, the shape of the heat sink 452b and the heat sink 452c may be devised (by increasing the surface area) to suppress the reduction in heat dissipation performance.

[0379] Furthermore, since the indicator light 224 is disposed near the top surface 401, the indicator light 224 is separated from the CPU 220, etc. and the WLAN module 223. This reduces the thermal effect of the indicator light 224 on the CPU 220, etc. and the WLAN module 223. As shown in Fig. 52, by disposing the light-emitting element at the end of the board, the indicator light 224 reduces the thermal effect on the CPU 220, etc. and the WLAN module 223. This also reduces the effect on the wiring of other circuits (including high-frequency signal circuits).

[0380] [Point of View C12] Further, a mounting fixture (e.g., mounting member 500, 550) is attached to the bottom surface, The wireless node according to aspect C11, wherein the mounting fixture has a ventilation space (e.g., communication space 555) that connects the first ventilation hole to the outside of the housing.

[0381] This will make it easier to draw cooling air (outside air) into the case from the bottom.

[0382] The mounting fixture may be an L-shaped mounting member 500 or a mounting member 550 having a U-shaped horizontal cross section.

[0383] [Point of View C13] The wireless node according to viewpoint C11, wherein the bottom surface has the communication port. As illustrated in Fig. 58, a communication space 555 having a size that allows the communication port to be opened is provided, so that a LAN cable can be easily inserted into and removed from the communication port through the communication space 555. As illustrated in Figs. 56 to 58, the mounting members 500 and 550 may provide a space that allows the cable to be inserted into and removed from the communication port. This makes it even easier to insert and remove the cable into and from the communication port.

[0384] [Point of View C14] The wireless node of aspect C11, wherein the bottom surface has a power connector to which a power cable is connected.

[0385] As shown in Fig. 58, communication space 555 is provided that is sized to enable power connector 412 to be opened, which will make it easier to insert and remove the power cable from power connector 412 through communication space 555. As shown in Figs. 56 to 58, mounting members 500, 550 may provide a space that allows the power cable to be inserted and removed from power connector 412. This will make it even easier to insert and remove the power cable from power connector 412.

[0386] [Point of View C15] a first heat sink provided on the first mounting surface side of the housing; a second heat sink provided on the second mounting surface side of the housing; The wireless node according to aspect C1, further comprising:

[0387] As shown in FIG. 53, heat sinks are provided on both sides of circuit board 461, making it possible to efficiently cool heat dissipating components within a small housing.

[0388] [Point of View C16] A wireless node according to aspect C15, wherein the first heat sink and the second heat sink each have one or more curved surfaces (e.g., curved portion 453) bent along the inner surface of the housing.

[0389] 53, the heat sink 452 may be bent along the inner surface of the housing 400. This will make it possible to increase the heat dissipation area.

[0390] [Point of View C17] A wireless node according to any one of points C1 to C16, further comprising a shielding cover (e.g., shielding cover 465) for shielding the network control circuit.

[0391] This will make it possible to reduce the emission of unnecessary radio waves and external radio waves.

[0392] [Point of View C18] A first antenna disposed parallel to a first side surface of the housing; A second antenna disposed parallel to a second side surface of the housing; a third antenna disposed parallel to a third side surface of the housing; a fourth antenna disposed parallel to a fourth side surface of the housing; A wireless node according to any one of points C1 to C17, further comprising:

[0393] As shown in FIG. 53, by employing at least four antennas 451, it will be possible to communicate with all other wireless nodes located in various directions.

[0394] [Point of View C19] The wireless node according to any one of viewpoints C1 to C18, wherein the first indicator light is lit in a color and a form according to an instruction from a parent device that manages the wireless node.

[0395] 39 and the like, the lighting color and lighting form of the indicator light 224 may be controlled by the parent unit 201. This would enable the user to control the indicator lights 224 of multiple child units 202 through the parent unit 201.

[0396] [Point of View C20] The wireless node according to any one of viewpoints C1 to C19, wherein at least one of a lighting color and a lighting form of the first indicator light is changed depending on an occupancy rate of a frequency resource of the wireless node.

[0397] The CPU 220 (e.g., the child device management unit 261) may monitor the occupancy rate of the frequency resource and store the occupancy rate in the storage device 221. For example, the occupancy rate L is calculated from the number M of channels currently in use among the total number N of all channels in the 2.4 GHz band (L=M / N). The storage device 221 may also store a table or setting information that associates the relationship between the lighting color and the lighting form for each of a plurality of occupancy rates. The occupancy rate may be associated with the lighting color, such as lighting blue when the occupancy rate is low, lighting yellow when the occupancy rate is medium, and lighting red when the occupancy rate is high. Also, when all channels are occupied or about to be occupied, a flashing red light may be adopted. The occupancy rate may be calculated taking into account the number of channels in the 5 GHz band.

[0398] [Point of View C21] The wireless node according to any one of viewpoints C1 to C20, wherein the first indicator light is turned on to indicate the direction of a partner wireless node that is wirelessly communicating with the wireless node.

[0399] As shown in Figures 61 and 62, each child device 202 may be lit up to point in the direction of the child device 202 with which it is wirelessly communicating. This allows the user to visually understand which child devices 202 are communicating with each other.

[0400] [Point of View C22] A wireless node according to any one of viewpoints C1 to C21, wherein the first indicator light is lit in the same color as the indicator lights of other wireless nodes that form a mesh cluster with the wireless node.

[0401] As shown in Figures 60, 61 and 62, the indicator light 224 of each child device 202 and the indicator light 224 of the child device 202 with which it is wirelessly communicating may be lit in the same color. This will make it possible to visually understand the multiple child devices 202 that form a mesh cluster.

[0402] [Point of View C23] The wireless node further includes a light receiving element (e.g., light receiving element 700) for receiving light from an indicator lamp of a wireless node that is wirelessly communicating with the wireless node, A wireless node described in any of viewpoints C1 to C22, wherein the control unit determines whether the wireless node and the other wireless node are communicating by direct waves or by indirect waves based on whether the light receiving element receives light from an indicator light of the other wireless node.

[0403] As described in relation to FIG. 63, after multiple child devices 202 are installed in a factory, industrial equipment may move or workers may pass by so as to block the line of sight. Therefore, it is desirable for multiple child devices 202 capable of communicating by more direct waves to establish wireless links in the wireless mesh network. The CPU 210 or the CPU 220 may set a high priority to a child device 202 that has a strong signal strength or a low communication error and is capable of communicating by direct waves, and reconstruct the communication link according to the priority. This will allow the wireless mesh network to be stably maintained.

[0404] [Point of View C24] The wireless node further includes a measuring means (e.g., a distance measuring function in the WLAN module 223 or the CPU 220) for measuring a distance from the wireless node to the other wireless node based on radio waves of the other wireless node that is wirelessly communicating with the wireless node, The wireless node according to aspect C1, wherein the control unit determines whether the wireless node and the counterpart wireless node are communicating by direct waves or indirect waves based on the distance acquired by the measurement means.

[0405] The CPU 220 can measure the distance from the own device (e.g., the slave device 202a) to the other device (e.g., the slave device 202b). For example, if the WLAN module 223 complies with IEEE802.11mc, the CPU 220 can obtain distance measurement data from the WLAN module 223. The CPU 220 may distinguish between direct waves and indirect waves by comparing the measured distance with a theoretical distance pre-stored in the storage device 221. For example, if the measured distance is approximately equal to the theoretical distance, the CPU 220 determines that the own device and the other device are communicating by direct waves. If the measured distance is longer than the theoretical distance, the CPU 220 determines that the own device and the other device are communicating by indirect waves. Since communication by direct waves is an index of the stability of wireless communication, the installer can review the installation positions of the slave devices 202 so as to increase the number of slave devices 202 communicating by direct waves.

[0406] [Point of View C25] The wireless node according to aspect C23 or 24, wherein the first indicator light has a different lighting color or lighting form depending on whether the wireless node and the other wireless node are communicating by direct waves or by indirect waves.

[0407] The indicator lights 224a, 224b may be lit blue when the user's device and the other party are communicating by direct waves, and may be flashing yellow when the user's device and the other party are communicating by indirect waves. Note that the combination of lighting color and lighting form is merely an example. In short, it is sufficient that the combination of lighting color and lighting form when the user's device and the other party are communicating by direct waves is different from the combination of lighting color and lighting form when the user's device and the other party are communicating by indirect waves.

[0408] [Point of View C26] The wireless node described in aspect C1, wherein the control unit (e.g., CPU 220) changes at least one of the lighting color, brightness, and lighting form of the first indicator light in response to an instruction from a parent unit that manages the wireless node.

[0409] As described with reference to Figures 39, 45, and 46, parent unit 201 may change at least one of the lighting color, brightness, and lighting form of indicator light 224 of each child unit 202. This makes it possible to change the lighting color, brightness, and lighting form of indicator light 224 according to the user's preference. For example, in a factory that handles photoconductors, parent unit 201 may set indicator light 224 to be turned off or to be lit very dimly.

[0410] [Point of View C27] The third light emitting element and the fourth light emitting element are connected in parallel to a driving current source (e.g., current source 560); The wireless node according to aspect C3, wherein the first light-emitting element and the fourth light-emitting element are connected in series to the driving current source.

[0411] This makes it possible to reduce the scale of the circuitry for driving and controlling the light-emitting elements. For example, four light-emitting elements can be controlled by a single current source 560, so that the scale of the circuitry for driving and controlling the light-emitting elements can be reduced.

[0412] [Point of View C28] The seventh light emitting element and the eighth light emitting element are connected in parallel to a driving current source (e.g., current source 560); The wireless node according to aspect C8, wherein the fifth light-emitting element and the sixth light-emitting element are connected in series to the driving current source.

[0413] This makes it possible to reduce the scale of the circuitry for driving and controlling the light-emitting elements. For example, four light-emitting elements can be controlled by a single current source 560, so that the scale of the circuitry for driving and controlling the light-emitting elements can be reduced.

[0414] [Point of View C29] a network controller that operates as a parent device; A plurality of wireless nodes that are managed by the network controller and operate as child devices; 1. An industrial wireless system comprising: The network controller includes: a first port for wired connection to a first wired network; a plurality of second ports connected by wire to at least one wireless node that operates as a root node among the plurality of wireless nodes; Each of the plurality of wireless nodes a communication port for connecting to an industrial device of an industrial network; a circuit board on which a wireless module for connecting to a wireless network and a control circuit for constructing the wireless network via the wireless module and transferring communication between the industrial device connected via the communication port and the wireless network are mounted; a housing that houses the circuit board arranged vertically; a first direction parallel to a normal direction of the first mounting surface of the circuit board; a second direction parallel to a normal direction of the second mounting surface of the circuit board; a third direction parallel to the first mounting surface and the second mounting surface; and an indicator light for outputting light to the The control circuit further controls the lighting state of the indicator light according to the state of the wireless network.

[0415] [Point of View C30] The industrial wireless system described in point C28, wherein the network controller is configured to acquire images from a plurality of network cameras arranged within the factory premises together with the plurality of wireless nodes, and create a layout map indicating where the plurality of wireless nodes are located within the factory premises based on the installation positions of each network camera and the lighting state of the indicator light of any of the plurality of wireless nodes included in the images.

[0416] As described in relation to FIG. 64, a plurality of network cameras 801a to 801c are arranged within the factory site. The CPU 210 of the parent unit 201 sets the lighting state of the indicator light 224 for a specific child unit 202. Furthermore, the CPU 210 acquires images from the plurality of network cameras 801a to 801c and identifies the position of a specific child unit 202 that is in a specific lighting state. The CPU 210 repeats the process of identifying the installation positions of the plurality of child units 202. As a result, the CPU 210 creates a layout map indicating where the child units 202 are arranged within the factory site. This will allow the network administrator to easily obtain the layout map. In particular, when the child unit 202 is fixed to an automatic guided vehicle or the like, the CPU 210 will be able to recognize the position of the automatic guided vehicle according to the position of the specific child unit 202.

[0417] The invention is not limited to the above-described embodiment, and various modifications and variations are possible within the scope of the gist of the invention.< / plc>

Claims

1. Communication ports for connecting industrial equipment to an industrial network, A circuit board on which a wireless module for connecting to a wireless network and a network control circuit for constructing the wireless network via the wireless module and transferring communication between the industrial equipment connected via the communication port and the wireless network are implemented, A housing for the vertically positioned circuit board, A first direction parallel to the normal direction of the first mounting surface of the circuit board, A second direction parallel to the normal direction of the second mounting surface of the circuit board, A third direction parallel to the first mounting surface and the second mounting surface, The first indicator light emits light, A control unit that controls the illumination state of the first indicator light according to the state of the wireless network. A wireless node having

2. The aforementioned first indicator light is A first light-emitting element that outputs light in the first direction, A second light-emitting element that outputs light in the second direction, A third light-emitting element that outputs light in the third direction, A first diffusion member that diffuses the light from the first light-emitting element, the light from the second light-emitting element, and the light from the third light-emitting element, A wireless node according to claim 1, having the following features.

3. The housing has at least four sides, The wireless node according to claim 1, wherein the first indicator light is arranged across three of the at least four sides.

4. The first direction and, The second direction and, A fourth direction opposite to the third direction, The wireless node according to claim 1, further comprising a second indicator light that emits light.

5. The aforementioned housing has a top surface and a bottom surface. The bottom surface has a first ventilation hole, The wireless node according to claim 1, wherein the top surface or the side surface of the housing has a second ventilation hole at a position higher than the first indicator light and lower than the top surface.

6. The mounting device is further attached to the bottom surface, The wireless node according to claim 5, wherein the mounting fixture has a ventilation space that connects the first ventilation hole to the outside of the housing.

7. The wireless node according to claim 5, wherein the bottom surface has the communication port and a power connector to which a power cable is connected.

8. A first heat sink provided on the first mounting surface side of the housing, A second heat sink provided on the second mounting surface side of the housing, The wireless node according to claim 1, further comprising:

9. A first antenna is positioned parallel to the first side surface of the aforementioned housing, A second antenna is positioned parallel to the second side of the aforementioned housing, A third antenna is positioned parallel to the third side of the aforementioned housing, A fourth antenna is positioned parallel to the fourth side surface of the housing, The wireless node according to claim 1, further comprising:

10. The wireless node according to claim 1, wherein the first indicator light lights up in a color and pattern corresponding to instructions from a master unit that manages the wireless node.

11. The wireless node according to claim 1, wherein the first indicator light changes at least one of its illumination color and illumination pattern according to the frequency resource occupancy rate of the wireless node.

12. The wireless node according to claim 1, wherein the first indicator light lights up to indicate the direction of the other wireless node communicating wirelessly with the wireless node.

13. The wireless node according to claim 1, wherein the first indicator light illuminates in the same color as the indicator lights of other wireless nodes that form a mesh cluster with the wireless node.

14. The wireless node further includes a light-receiving element that receives light from an indicator light of a wireless node that is communicating wirelessly with the aforementioned wireless node, The control unit determines whether the wireless node and the other wireless node are communicating via direct waves or indirect waves, based on whether the light receiving element is receiving light from the indicator light of the other wireless node, according to claim 1.

15. The system further includes a measuring means for measuring the distance from the wireless node to the other party's wireless node based on the radio waves of the other party's wireless node that is communicating wirelessly with the aforementioned wireless node. The control unit determines, based on the distance obtained by the measuring means, whether the wireless node and the other wireless node are communicating by direct waves or by indirect waves, according to claim 1.

16. A network controller that acts as the master unit, Multiple wireless nodes, managed by the aforementioned network controller and operating as slave devices, An industrial wireless system having, The aforementioned network controller The first wired network and the first port for wired connection, It has a plurality of second ports that are wired to at least one wireless node that acts as the root node among the plurality of wireless nodes, Each of the aforementioned multiple wireless nodes is: Communication ports for connecting industrial equipment to an industrial network, A circuit board on which a wireless module for connecting to a wireless network and a control circuit that constructs the wireless network via the wireless module and transfers communication between the industrial equipment connected via the communication port and the wireless network are implemented, A housing for the vertically positioned circuit board, A first direction parallel to the normal direction of the first mounting surface of the circuit board, A second direction parallel to the normal direction of the second mounting surface of the circuit board, A third direction parallel to the first mounting surface and the second mounting surface, It has an indicator light that emits light, The control circuit further controls the illumination state of the indicator light according to the state of the wireless network, in an industrial wireless system.

17. The industrial wireless system according to claim 16, wherein the network controller is configured to acquire images from a plurality of network cameras located on the factory premises together with the plurality of wireless nodes, and to create a layout map showing where the plurality of wireless nodes are located on the factory premises based on the installation location of each network camera and the illumination status of any of the indicator lights of the plurality of wireless nodes included in the image.

Images