Industrial wireless system, network controller, and control method of them

Abstract

To improve an usability in an industrial wireless system.SOLUTION: A network controller collects state information indicating a communication state of each of a plurality of radio nodes, and makes a wireless network map that visually shows that each communication state of the plurality of radio nodes is a normal state that can executes a normal communication and a plurality of different abnormal states that cannot execute the normal communication on the basis of the state information to be displayed onto a display device. The network controller selects a candidate of a countermeasure for cancelling or releasing at least one abnormal state in the case where the communication state is corresponded to at least one abnormal state of the plurality of abnormal states, and displays the candidates of the countermeasure to the display device.SELECTED DRAWING: Figure 59

Description

[Technical field]

[0001] The present invention relates to an industrial wireless system, a network controller, and a control method thereof. [Background technology]

[0002] A plurality of industrial devices, such as machine tools, are installed in a factory, and the plurality of industrial devices are controlled by a programmable logic controller (PLC). By connecting the plurality of industrial devices or the plurality of PLCs with a wireless mesh network, it is possible to maintain the industrial network in the factory even if the layout of the industrial devices in the factory is changed. In a wireless mesh network, it is difficult to grasp which section between the plurality of wireless nodes maintains a wireless connection or which section has been disconnected. According to Patent Document 1, a technology for generating a visual display (visual network map) of a wireless mesh network is proposed. In the visual network map, icons indicating each wireless node and lines connecting the icons to each other to indicate the communication status between the wireless nodes are displayed. Then, when a wireless link connecting certain wireless nodes is disconnected, the connecting line corresponding to the wireless link is erased. In addition, network performance parameters such as the radio wave strength of the received wireless signal are also displayed as part of the visual network map. In addition, in the visual network map, a map indicating the plant layout is displayed, and icons and connecting lines are displayed superimposed thereon. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Special Publication No. 2009-523363 Summary of the Invention [Problem to be solved by the invention]

[0004] According to the invention disclosed in Patent Document 1, even a user who is not familiar with wireless communication can visually grasp which wireless link between wireless nodes has been disconnected. However, a user who is not familiar with wireless communication may not immediately come up with a method or measure for restoring the disconnected wireless link. Therefore, there is a demand for assistance that enables even a user who is not familiar with wireless communication to easily solve a failure occurring in a wireless node.

[0005] SUMMARY OF THE PRESENT EMBODIMENT An object of the present invention is to improve the usability of industrial wireless systems. [Means for solving the problem]

[0006] The present invention relates to, for example, a network controller that operates as a parent device; a plurality of wireless nodes each having a port for wired connection to an industrial device, the wireless nodes being managed by the network controller and operating as child devices; An industrial wireless system having a display device that displays communication states of the plurality of wireless nodes provided from the network controller, a collection unit for collecting state information indicating a communication state of each of the plurality of wireless nodes; a map display processing unit that causes the display device to display a wireless network map visually indicating whether a communication state of each of the plurality of wireless nodes is a normal state in which communication can be performed normally or a plurality of different abnormal states in which communication cannot be performed normally based on the state information collected by the collection unit; and a selection unit that selects, when the communication state corresponds to at least one of the plurality of abnormal states, a candidate countermeasure for eliminating or mitigating the at least one abnormal state; a candidate display processing unit that displays the candidate measures selected by the selection unit on the display device; The present invention provides an industrial wireless system having a Effect of the Invention

[0007] According to the present invention, the usability of industrial wireless systems 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 [Diagram 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] Diagram illustrating a PLC link built on an industrial wireless network [Figure 51] A diagram showing how mesh clusters are identified by different lighting colors. [Figure 52] A diagram explaining how to indicate the communication partner using an indicator light [Figure 53] A diagram explaining how to indicate the communication partner using an indicator light [Figure 54] A diagram explaining direct wave communication and indirect wave communication. [Figure 55] A diagram explaining how to create a layout map using a network camera. [Figure 56] Diagram explaining the functions of the parent unit [Figure 57] Diagram explaining the functions of the child unit [Figure 58] Flowchart showing the operation of the slave unit [Figure 59] Flowchart showing the operation of the parent unit [Figure 60] Diagram showing the UI for displaying wireless maps [Figure 61] Diagram showing the UI for displaying wireless maps [Figure 62] Diagram showing the UI for displaying wireless maps [Figure 63] Diagram explaining the suggestion dialog [Figure 64] Diagram showing the UI for displaying wireless maps [Figure 65] Diagram showing the UI for displaying wireless maps [Figure 66] Diagram showing the UI for displaying wireless maps [Figure 67] Diagram explaining the suggestion dialog [Figure 68] Diagram showing the UI for displaying wireless maps [Figure 69] Diagram explaining the suggestion dialog [Figure 70] Diagram explaining the suggestion dialog [Figure 71] Diagram showing the UI for editing wireless maps [Figure 72] Diagram showing the UI for editing wireless maps [Figure 73] Diagram showing the UI for editing wireless maps [Figure 74] Diagram showing the UI for editing wireless maps [Figure 75] Diagram showing the UI for displaying wireless maps [Figure 76] Diagram showing the UI for displaying wireless maps 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 by polling whether a notification has been issued in the PLC 1, 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 a waveform of a time-series device value acquired in real time from the PLC 1, or may display a waveform of a time-series device value included in the driving record.

[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 a 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 unique 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. 50.

[0234] FIG. 50 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. 50, 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 IP address) set in this way is stored in the project storage unit 35 of the PLC1.

[0236] In FIG. 50, 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 above-mentioned data request and data transmission at the above-mentioned 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 50) described above to an interval that takes into account delays caused by wireless communication, it becomes easy to smoothly repeat partial reading and partial playback 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] <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.

[0247] 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.

[0248] FIG. 51 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.

[0249] 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.

[0250] 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).

[0251] <Method of lighting the indicator light to show the communication partner> In FIG. 52, 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.

[0252] 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.

[0253] 53 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.

[0254] 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.

[0255] 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.

[0256] 52 and 53, 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.

[0257] <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.

[0258] Fig. 54 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 CPU 220 of the child device 202a can receive light from the indicator light 224 of the other child device 202b using the light receiving element 700, the CPU 220 determines that the child devices 202a and 202b can communicate with each other using direct waves. This is because light travels in a more rectilinear manner than radio waves.

[0259] 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.

[0260] 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.

[0261] 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.

[0262] 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.

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

[0264] <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, the user may manually rewrite the layout map, or the layout map may be automatically rewritten as described below.

[0265] 55 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.

[0266] 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.

[0267] 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.

[0268] 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.

[0269] 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.

[0270] 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.

[0271] 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.

[0272] <Wireless Network Map> Since radio waves are invisible to humans, it is difficult for a user to grasp the wireless status between multiple slave units 202. In addition, when a large number of slave units 202 are installed in a factory with a large site, it would be convenient for a user to know which slave units 202 have established wireless links with each other from a bird's-eye view. However, wireless links often become disconnected or unstable. In such cases, how quickly the wireless link is restored is important in an industrial wireless network. There are only a few users who have detailed knowledge about wireless communication. Therefore, if the wireless link can be restored quickly by assisting users who do not have detailed knowledge about wireless communication, the operating rate of the industrial wireless system will be improved.

[0273] 1. Parent unit configuration 56 shows an example of functions realized by the CPU 210 of the parent device 201 and information stored in the storage device 211. Note that the same reference numerals are used to designate parts that have already been described.

[0274] The status management unit 6500 collects and manages the status of the multiple child devices 202 belonging to the industrial wireless network 204. The status management unit 6500 includes a communication status collection unit 6501, a warning status collection unit 6502, and a disconnection detection unit 6503.

[0275] The communication status collection unit 6501 collects communication statuses from a plurality of child devices 202 belonging to the industrial wireless network 204, creates a communication status list 6521 including the collected communication statuses, and stores the list in the storage device 211. The communication status indicates, for example, the state of communication and wireless communication settings related to the child devices 202. The communication status includes, for example, the frequency (e.g., 2.4 GHz, 5 GHz, 6 GHz), the channel (e.g., ch1 to ch93), the bandwidth (20 / 40 / 80 MHz), the radio wave usage rate [%] by the industrial wireless network 204, the usage rate [%] by the child device 202 for transmission in the radio wave usage rate, the usage rate [%] by the child device 202 for reception in the radio wave usage rate, the usage rate [%] by other child devices 202 in the radio wave usage rate, the rate [%] of the radio wave usage rate occupied by noise, and the strength (reception strength) [%] of the wireless signal received from the other child device communicating with the child device 202. When the child device 202 also operates as an access point, the communication state may further include a state related to the access point. The state related to the access point includes, for example, whether the access point function is enabled / disabled, the frequency (2.4 / 5 GHz), the channel (ch1-ch11, ch36-ch48), the bandwidth (20 / 40 MHz), the radio wave usage rate [%] by the access point, the usage rate [%] by the child device 202 in transmitting the radio wave usage rate, the usage rate [%] by the child device 202 in receiving the radio wave usage rate, the usage rate [%] by other child devices 202 in the radio wave usage rate, the rate [%] of the radio wave usage rate occupied by noise in the radio wave usage rate, and the MAC address of the wireless LAN device connected to the access point.

[0276] The communication status collection unit 6501 may collect the communication status by performing polling on all the child devices 202 registered in the child device list 253. Alternatively, the communication status collection unit 6501 may collect the communication status by receiving the communication status periodically transmitted from each of the child devices 202 registered in the child device list 253.

[0277] The warning status collection unit 6502 collects warning statuses from multiple child devices 202 belonging to the industrial wireless network 204, creates a warning status list 6522 including the collected warning statuses, and stores the list in the storage device 211. Each child device 202 judges whether its own communication status (e.g., radio wave reception strength, noise) is a situation that is subject to a warning, and holds the judgment result as a warning status. For example, when the radio wave reception strength falls below a predetermined threshold (lower limit), a warning status called a radio wave strength drop warning occurs. This can occur when the distance between the child devices is too long or a radio wave shield is inserted between the child devices. Also, when the radio wave reception strength exceeds a predetermined threshold (upper limit), a warning status called a child device proximity warning occurs. This occurs when the distance between the child devices is too short. A wireless congestion warning is a warning status that occurs when the usage rate of wireless in the vicinity exceeds a predetermined usage rate threshold. A surrounding noise increase warning is a warning status that occurs when the surrounding noise exceeds a predetermined noise threshold. The temperature rise warning is a warning state that occurs when the temperature of the child device 202 exceeds a threshold temperature. The system program version warning is a warning state that occurs when the version of the system program of the child device 202 is older than a predetermined version. Here, the predetermined version is, for example, the function version of the parent device 201. If the function version of the parent device 201 and the version of the system program of the child device 202 do not match, it becomes impossible to use the predetermined function, and therefore a warning is necessary.

[0278] The warning status collection unit 6502 may collect warning statuses by performing polling on all child devices 202 registered in the child device list 253. Alternatively, the warning status collection unit 6502 may collect warning statuses by receiving warning statuses periodically transmitted from each child device 202 registered in the child device list 253.

[0279] In addition, among the faults occurring in the industrial wireless network 204, serious faults may be classified as errors, and minor faults may be classified as warnings.

[0280] The disconnection detection unit 6503 detects whether wireless communication between any one of the multiple slave units 202 registered in the slave unit list 253 and the industrial wireless network 204 has been disconnected. The disconnection detection unit 6503 periodically transmits an inquiry signal to each of the multiple slave units 202 registered in the slave unit list 253. If a response signal to the inquiry signal is returned, the disconnection detection unit 6503 determines that the target slave unit has not been disconnected. If a response signal to the inquiry signal is not returned, the disconnection detection unit 6503 determines that the target slave unit has been disconnected. Note that a state in which the target slave unit has been disconnected is a warning state called a slave unit loss. The disconnection detection unit 6503 also performs disconnection detection on the slave unit 202a that is connected to the master unit 201 by wire. Since the loss of the slave unit 202a is a serious failure, it is classified as a master unit slave unit loss error. The disconnection detection unit 6503 creates a disconnection status list 6523 including detection results of the disconnection status for the multiple child devices 202 registered in the child device list 253 , and stores the list in the storage device 211 .

[0281] The monitor screen management unit 6510 provides screen data (e.g., HTML file, CSS file, image data, etc.) for displaying the monitoring result related to the industrial wireless network 204 to the PC 2 functioning as a monitor. The monitor screen management unit 6510 has, for example, a map display processing unit 6511 and a suggestion management unit 6512. The map display processing unit 6511 creates a wireless map 6531 for displaying the position where the slave unit 202 is installed in a factory where multiple industrial devices are installed and the state of the slave unit 202, and provides it to the PC 2. Note that the storage device 211 may store a layout map 6532 in addition to the wireless map 6531. The layout map 6532 is image data showing one of multiple industrial devices arranged in the factory. The map display processing unit 6511 may provide the layout map 6532 and the wireless map 6531 superimposed on each other to the PC 2. This will make it easier for the user to determine the rearrangement of the slave unit 202, the movement of an obstacle, etc.

[0282] The suggestion management unit 6512 provides the PC 2 and the like with countermeasures (suggestions) that are useful for improving the status of the child device 202. The suggestion management unit 6512 acquires the status of each child device 202 registered in the child device list 253 from the communication status list 6521, the warning status list 6522, and the disconnection status list 6523, acquires suggestions corresponding to the acquired status from the suggestion collection 6541, and reflects them in the wireless map 6531. A user with little knowledge of wireless communication is often unable to immediately find an appropriate countermeasure just by looking at the status of the child device 202. Therefore, by the suggestion management unit 6512 presenting an appropriate countermeasure to the user, the user will be able to operate the industrial wireless network 204 appropriately.

[0283] 2. Configuration of child unit 57 shows an example of functions implemented by the CPU 220 of the child device 202 and information stored in the storage device 221. Note that the same reference numerals are used to designate parts that have already been described.

[0284] The status management unit 6600 has a communication status acquisition unit 6601 and an error warning determination unit 6602, and manages the status of the child device 202. The communication status acquisition unit 6601 acquires a communication status 6621 from the setting information 254 and the SDR 226 stored in the storage device 221, and stores the communication status 6621 in the storage device 221. The error warning determination unit 6602 determines whether an error event or a warning event has occurred based on the communication status 6621, and stores the determination result (error warning determination result 6622) in the storage device 221. The error warning determination result 6622 is information indicating the warning status described above. The communication status 6621 and the error warning determination result 6622 are examples of status information indicating the operating status of the child device 202.

[0285] The error warning determination unit 6602 may be mounted on the parent device 201. In this case, the status management unit 6600 transmits a communication status 6621 to the parent device 201, receives an error warning determination result 6622 obtained from the communication status 6621 of the parent device 201, and stores it in the storage device 221.

[0286] The indicator light management unit 6610 controls the lighting mode (lighting / non-lighting, continuous lighting / flashing, lighting color) of the indicator light 224. The indicator light management unit 6610 may work in cooperation with the indicator light operation unit 262, be a part of the indicator light operation unit 262, or be integrated into the indicator light operation unit 262. The display color change unit 6611 controls the display color of the indicator light 224 according to the error warning determination result 6622. For example, when the child device 202 has established a wireless link with the child device 202 at the hop destination, the indicator light 224 lights up in green. When the child device 202 has not established a wireless link with the child device 202 at the hop destination, the indicator light 224 lights up in red.

[0287] 3. Flowchart of child unit FIG. 58 shows a control method executed by the CPU 220 of the child device 202 in accordance with the program 280.

[0288] In S6701, the CPU 220 (communication status acquisition unit 6601) determines whether it is time to acquire the communication status, etc. The acquisition timing may be periodic, or may be a timing when a specific condition (for example, the occurrence of a specific event) is satisfied. When the acquisition timing arrives, the CPU 220 proceeds to S6702. If the acquisition timing has not arrived, the CPU 220 proceeds to S6706.

[0289] In S6702, the CPU 220 (communication status acquisition unit 6601) acquires the communication status. The communication status is acquired from the setting information 254 or the SDR 226 in the storage device 221. The setting information 254 holds, for example, a channel, a frequency band, and a bandwidth. The SDR 226 is configured to provide the reception strength of radio waves (wireless signals), a signal-to-interference-and-noise ratio (SINR), a communication speed, a radio wave utilization rate, an error rate, and the like.

[0290] In S6703, the CPU 220 (error warning determination unit 6602) executes a warning determination based on the acquired communication state. For example, it may be determined whether the radio wave reception strength is less than a predetermined threshold (lower limit) (radio wave strength drop warning). It may be determined whether the radio wave reception strength exceeds a predetermined threshold (upper limit) (child unit proximity warning). It may be determined whether the wireless usage rate in the vicinity exceeds a predetermined usage rate threshold (wireless congestion warning). It may be determined whether the surrounding noise exceeds a predetermined noise threshold (surrounding noise increase warning). It may be determined whether the temperature of the child unit 202 exceeds a threshold temperature (temperature rise warning). Note that the child unit 202 may have a built-in temperature sensor. It may be determined whether the version of the system program (program 280) of the child unit 202 is older than a predetermined version (system program version warning). The predetermined version may be the version of the system program of the parent unit 201.

[0291] In S6704, the CPU 220 (the communication status acquisition unit 6601, the error warning determination unit 6602) stores the acquired communication status 6621 and the error warning determination result 6622 in the storage device 221.

[0292] At S6705, the CPU 220 (display color change unit 6611) changes the display state of the indicator light 224 based on at least one of the communication state 6621 and the error / warning determination result 6622. S6705 is optional. The relationship between the classification of the communication state and the display state (lighting state) is stored in advance in the storage device 221 and may be referred to by the CPU 220. Similarly, the relationship between the type of error or warning and the display state (lighting state) is stored in advance in the storage device 221 and may be referred to by the CPU 220.

[0293] In S6706, the CPU 220 (status management unit 6600) determines whether the error warning determination result 6622 or a request to transmit the error warning determination result 6622 has been received from the parent device 201. If a request to transmit has been received, the CPU 220 proceeds to S6707. If a request to transmit has not been received, the CPU 220 proceeds to S6707.

[0294] In S6707, the CPU 220 (status management unit 6600) transmits the communication status 6621 and the error / warning determination result 6622 to the parent device 201. The communication status 6621 and the error / warning determination result 6622 are transmitted to the parent device 201 as status information.

[0295] 4. Flowchart of the parent unit FIG. 59 shows a control method executed by the CPU 210 of the parent device 201 in accordance with the program 250.

[0296] In S6801, the CPU 210 (communication status collection unit 6501, warning status collection unit 6502) determines whether the timing for collecting status information (communication status 6621 and error warning determination result 6622) has arrived. The timing for collecting the communication status 6621 and the timing for collecting the error warning determination result 6622 may be different. In this case, the communication status 6621 and the error warning determination result 6622 are collected separately. When the collection timing arrives, the CPU 210 proceeds to S6802. If the collection timing has not arrived, the CPU 210 proceeds to S6807.

[0297] In S6802, the CPU 210 (communication status collection unit 6501, warning status collection unit 6502) collects status information (communication status 6621 and error warning determination result 6622) by transmitting a transmission request to each child device 202 registered in the child device list 253. Note that at this timing, the disconnection detection unit 6503 may transmit an inquiry signal to each child device 202 registered in the child device list 253 to determine the disconnection status of each child device 202.

[0298] In S6803, the CPU 210 (suggestion management unit 6512) checks (analyzes) the communication status 6621 and the error / warning determination result 6622. For example, the suggestion management unit 6512 determines whether or not either the communication status 6621 or the error / warning determination result 6622 includes an event that requires a suggestion (countermeasure).

[0299] In S6804, the CPU 210 (suggestion management unit 6512) determines whether an event requiring a suggestion has occurred based on the confirmation result (analysis result) of the communication state 6621 and the error / warning determination result 6622. If a suggestion is required, the CPU 210 proceeds to S6805. If a suggestion is not required, the CPU 210 proceeds to S6806.

[0300] In S6805, the CPU 210 (suggestion management unit 6512) refers to the suggestion collection 6541 according to the type of event requiring a suggestion (for example, a drop in signal strength), and determines (selects) the suggestion content.

[0301] In S6806, the CPU 210 (map display processing unit 6511) updates the wireless map 6531 (display data) based on the communication status 6621, the error / warning determination result 6622, and the suggested content.

[0302] In S6807, the CPU 210 (map display processing unit 6511) determines whether or not a map request has been received from the PC 2. The map request may be, for example, an access to a Web page that provides the wireless map 6531. In other words, the map request may be an HTTP request.

[0303] In S6808, the CPU 210 (map display processing unit 6511) transmits display data of the wireless map 6531 to the PC 2. The display data may include an HTML file, a CSS file, an image file, a script file, etc. of a Web page that displays the wireless map 6531. Thereafter, the map display processing unit 6511 may update the display data of the wireless map 6531 in response to a request from the PC 2.

[0304] 5.Wireless Maps UI 5-1. Normal state Fig. 60 shows a UI 6900 displayed on the display unit 7 of the PC 2. The UI 6900 may be displayed on the display unit 7 by the Web browser 60 of the PC 2, or may be displayed on the display unit 7 by a dedicated display program. Fig. 60 shows a case where no error or warning has occurred.

[0305] The map display section 6901 is a display area that displays a wireless map 6531. In this example, a parent device icon 6951 indicating the parent device 201 and six child device icons 6952a to 6952f indicating the six child devices 202a to 202f are displayed. In addition, a connection line 6953 indicating a wired link between the parent device 201 and the child device 202a, and a connection line 6954 indicating a wireless link between the parent device 201 and the child devices 202b to 202f are displayed. The connection lines 6953 and 6954 are erased when the corresponding communication links are disconnected.

[0306] The status display section 6902 is a display area that displays the operating status of the industrial wireless network 204 (industrial wireless system). The system display section 6903 is a display area that displays the overall operating status of the industrial wireless network 204 (industrial wireless system). The master display section 6904 is a display area that displays the operating status of the master 201. The slave display sections 6911a to 6911f are display areas that display the operating status of each of the slaves 202a to 202f. The slave display sections 6911a to 6911f may display identification information of the slaves 202 (e.g., a number indicating the order of registration).

[0307] The menu 6905 is a selection section for selecting what information to display. In this example, displaying the operating status of the child device 202 is selected.

[0308] The layout edit button 6909 is a button for editing the display positions of the parent machine icon 6951 and the child machine icons 6952a to 6952f displayed on the map display section 6901. After pressing the layout edit button 6909, the user can edit the display positions of the parent machine icon 6951 and the child machine icons 6952a to 6952f by dragging the parent machine icon 6951 and the child machine icons 6952a to 6952f with the pointer 103 via the operation section 8. Note that the display positions of the parent machine icon 6951 and the child machine icons 6952a to 6952f may indicate the arrangement positions of the parent machine 201 and the child machine 202 in the factory. Note that the default display positions of the parent machine icon 6951 and the child machine icons 6952a to 6952f may be acquired by the network camera 801 as described above.

[0309] The add slave button 6907 is a button for adding a slave icon 6952 for a slave 202 that is to join the industrial wireless network 204 to the wireless map 6531. The delete slave button 6908 is a button for deleting from the wireless map 6531 a slave icon 6952 that corresponds to a slave 202 that is to be deleted from the industrial wireless network 204.

[0310] 5-2. Warning status FIG. 61 shows the UI 6900 when an event requiring a warning occurs. In this example, the child device 202c, which is indicated as child device 03, is in a warning state. Therefore, the outer frame of the child device icon 6952c is changed from a solid line to a broken line. In addition, the connection line 6954 indicating the wireless link connecting the child device 202a and the child device 202c is also changed from a solid line to a broken line. Note that the change from a solid line to a broken line may be a change from a first display color (e.g., white) indicating a normal state to a second display color (e.g., yellow) indicating a warning state. Also, a change from a static display to a blinking display may be adopted. Also, an animation indicating a warning may be displayed. A warning icon 7000 may be further displayed for the child device icon 6952c corresponding to the child device 202c.

[0311] When any warning or error occurs in the industrial wireless network 204, the system display unit 6903 displays a message corresponding to the warning or error. The child device display unit 6911c corresponding to the child device 202c may also display a message and an icon corresponding to the warning or error.

[0312] The user can display information about the specified child device icon 6952 by specifying one of the child device icons 6952a to 6952f with the pointer 103. Here, it is assumed that the child device icon 6952c of the child device 202c in the warning state is clicked.

[0313] FIG. 62 shows status information of the child unit 202c in a warning state in the UI 6900. Note that the order in which the information is displayed in the UI 6900 is merely an example. The child unit icon 6952c corresponding to the selected child unit 202c may be emphasized (e.g., highlighted). The child unit status display section 7100 is a display area that displays the status of the child unit 202 corresponding to the child unit icon 6952 specified by the pointer 103. The child unit name display section 7101 is a display area that displays the identification information (e.g., child unit 03) of the child unit 202 specified by the user. The light button 7102 is a button that requests the child unit 202 to blink the indicator light 224 of the child unit 202 specified by the user.

[0314] The warning state display section 7103 is a display area that displays that the designated child device 202c is in a warning state. The explanation button 7107a is a button for displaying explanation information about the warning state.

[0315] The radio wave usage rate display section 7104 is a display area that displays the radio wave usage rate included in the communication state. In this example, the radio wave usage rate is graphed, but a numerical value may be displayed. The explanation button 7107b is a button for displaying explanation information about the radio wave usage rate.

[0316] The signal strength display section 7105 is a display area that displays the reception strength of a wireless signal transmitted from a hop destination of the child device 202c. The explanation button 7107c is a button for displaying explanation information on the signal strength. The signal strength display section 7105 may be disposed above the signal usage rate display section 7104.

[0317] The detailed information button 7106 is a button for requesting the display of more detailed information about the communication status, warning status, and the like, of the child device 202c.

[0318] The designated child device icon 6952c may be highlighted (for example, by changing from a thin line to a thick line, changing the display color, or displaying an animation) in the map display portion 6901. The connection line 6954 may also be highlighted.

[0319] 63 shows a suggestion dialog 7200 indicating a signal strength reduction warning. The suggestion dialog 7200 is a UI that is displayed, for example, when an explanation button 7107a is pressed by the pointer 103. In this example, explanation information 7211 of the warning state is included. For example, explanation information 7211 of a signal strength reduction warning may include a message such as "The reception strength of the wireless signal between the child devices has decreased, causing a deterioration in wireless performance. Please implement one of the following measures to improve wireless performance."

[0320] Moreover, the suggestion dialog 7200 in this example includes suggestion contents 7212a to 7212c showing three types of suggestions (countermeasures) for improving the decrease in radio wave strength. The suggestion contents 7212a to 7212c may include an image (e.g., a still image, a video, an animation) showing the suggestion contents and an explanatory text. The suggestion content 7212a indicates that the radio wave strength will improve by shortening the distance between the child devices. The suggestion content 7212a may indicate a recommended distance between the child devices. The suggestion content 7212a may include an animation showing moving two child devices closer to each other.

[0321] The suggested content 7212b indicates that an obstacle (radio wave obstruction) between the child devices should be removed, and that the child device should be placed at a higher location, thereby ensuring a line of sight between the child devices. The suggested content 7212b may include an animation of removing the obstacle or an animation of raising the child device.

[0322] Suggested content 7212c indicates that a new child device is to be added between two child devices. The new child device will relay the two child devices. Suggested content 7212c may include an animation indicating that the new child device is being inserted between the two child devices.

[0323] The OK button 7201 is a button for closing the suggestion dialog 7200 and returning to the UI 6900.

[0324] FIG. 64 shows detailed information 7300 displayed when the detailed display button 7106 is pressed. The detailed information 7300 includes a communication status 6621 for the child device 202c acquired from the communication status list 6521. In this example, the detailed information includes model information of the child device 202c, communication status of the wired port (LAN port 38i) (e.g., state, reception speed, transmission speed of a wired link established with an industrial device), and information on communication between child devices acquired from the SDR 226. If the detailed information 7300 includes more information than the amount of information (display area) that can be displayed on the child device status display section 7100, a scroll bar may be displayed on the child device status display section 7100. The user can check the entire detailed information 7300 by operating the scroll bar with the pointer 103.

[0325] FIG. 65 shows the UI 6900 when a child unit loss occurs. In this example, the loss of the child unit 202c is detected by the disconnection detection unit 6503. The child unit icon 6952c corresponding to the child unit 202c is changed to an icon indicating the loss of the child unit. Furthermore, the connection line 6954 connecting the child unit icon 6952a and the child unit icon 6952c is erased. The system display unit 6903 displays a message indicating that a child unit loss has occurred. The child unit display unit 6911c also displays a message and a mark indicating that a child unit loss has occurred.

[0326] Fig. 66 shows a handset status display section 7100 that is displayed when the handset icon 6952c shown in Fig. 65 is clicked by the pointer 103. In particular, the warning status display section 7103 displays a message and a mark indicating that a handset loss has occurred. The radio wave usage rate display section 7104 and the radio wave strength display section 7105 cannot display data. This is because, when a handset loss occurs, it becomes impossible to obtain the latest communication status of the handset 202c from the handset 202c.

[0327] FIG. 67 shows a suggestion dialog 7200 that is displayed when the explanation button 7107a shown in FIG. 66 is pressed. Explanation information 7211 includes a message indicating that communication with the child device 202c is not possible. Suggestion contents 7212d to 7212e include suggestion information acquired from the suggestion collection 6541 when a child device loss occurs. Suggestion contents 7212d may include a message and an image (e.g., a still image, a video, an animation) suggesting that the power status of the child device 202c should be checked, and that the child device 202c should be deleted from a child device deletion screen when the use of the child device is to be ended. A child device deletion button 6908 (a link to a child device deletion screen) may also be provided in the suggestion dialog 7200. This allows the lost child device 202c to be deleted from the child device list 253 and the wireless map 6531.

[0328] The suggested content 7212e may include a message and an image (e.g., a still image, a video, an animation) suggesting that the communication conditions between the child devices 202c and 202a may be poor, that the distance between the child devices should be reviewed, or that line of sight between the child devices should be ensured.

[0329] 68 shows the UI 6900 when a system error occurs in the industrial wireless network 204. The parent machine icon 6951 has been changed to an icon indicating that an error unrelated to the wireless state (e.g., the system version is old) has occurred in the parent machine 201. In addition, an error mark 7700 is displayed near the parent machine icon 6951. This suggests that an error has occurred in the parent machine 201.

[0330] In this example, warnings have also occurred in child device 202c and child device 202d. Therefore, child device icons 6952c and 6952d are changed to icons indicating the occurrence of a warning. Child device icons 6952c and 6952d also display a warning icon 7000. Connection line 6954 is also changed to a dashed line indicating a warning.

[0331] The system display unit 6903 displays a message and a mark indicating that an error has occurred in the industrial wireless network 204. The child device display units 6911c and 6911d display a message and an icon indicating that the corresponding child devices 202c and 202d are in a warning state.

[0332] 69 shows a suggestion dialog 7200 corresponding to a child device proximity warning. Explanation information 7211 includes a message explaining the child device proximity warning, such as "The reception strength of the wireless signal between the child devices is extremely high, affecting wireless performance. Please implement the following measures."

[0333] The suggested content 7212f may include a message and an image (eg, a still image, a video, or an animation) indicating that the child devices should be spaced apart and that the recommended distance between the child devices is 1 meter or more.

[0334] 70 shows a suggestion dialog 7200 corresponding to a wireless congestion warning. Explanation information 7211 includes a message explaining the wireless congestion warning, such as "Wireless usage in the surrounding area is high, causing wireless performance to deteriorate. Please take the following measures."

[0335] The suggested content 7212g may include a message and an image (e.g., a still image, a video, an animation) indicating that the channel of the child device 202 should be changed and that the channels of other surrounding wireless devices should be changed. The suggested content 7212h may include a message and an image (e.g., a still image, a video, an animation) indicating that the amount of communication of the industrial devices connected to the child device 202 should be reduced and that a new parent device should be added to separate the industrial wireless network 204 into multiple wireless networks.

[0336] A child device setting button 7901 is a button for calling up a child device setting screen for changing the channel.

[0337] 5-3. Layout editing 71 shows a layout editing UI 8000 that is displayed when the layout editing button 6909 is pressed. The layout editing UI 8000 has a layout display section 8001 and a detailed editing section 8002. The map display processing section 6511 edits the wireless map 6531 in accordance with editing instructions input via the layout editing UI 8000.

[0338] The layout display section 8001 displays child device icons 6952 of all child devices 202 registered in the child device list 253, and a parent device icon 6951 of the parent device 201. The user can move the child device icon 6952 or the parent device icon 6951 with the pointer 103. The display positions of the child device icon 6952 and the parent device icon 6951 are reflected in the wireless map 6531 and saved.

[0339] The detailed editing section 8002 has an overall display section 8003 that reduces and displays the entire wireless map 6531. The background image setting section 8004 is a setting section for setting whether or not to display a background image superimposed (transparently) on the wireless map 6531. When setting a background image is selected in the background image setting section 8004, a dialogue for specifying an image file of the background image (e.g., layout map 6532) may be displayed. The transparency setting section 8005 is a slide bar for setting the transparency of the background image superimposed on the wireless map 6531. The icon display color menu 8006 is a menu for specifying the display color (e.g., light, dark, vivid) of the parent device icon 6951 and the child device icon 6952. The icon size setting section 8007 is a menu for specifying the display size (e.g., large, medium, small) of the parent device icon 6951 and the child device icon 6952.

[0340] The back button 8008 is a button for discarding the layout editing results and returning to the UI 6900. The initialization button 8009 is a button for discarding the layout editing results and returning the display positions of each icon to their initial positions. The exit button 8010 is a button for saving the layout editing results in the wireless map 6531 and returning to the UI 6900.

[0341] 72 shows an example in which a background image is superimposed on a wireless map 6531 in the layout editing UI 8000. By default, the transparency of the background image is set low, emphasizing the presence of the background image. As the background image, a map of the inside of a factory (a layout map 6532 showing the arrangement of multiple industrial devices) may be used.

[0342] 73 shows an example in which the transparency of the background image is increased in the layout editing UI 8000. Since the transparency of the background image is increased through the transparency setting section 8005, the density of the layout map 6532 is reduced.

[0343] FIG. 74 shows an example in which the display positions of the parent icon 6951 and the child icons 6952a to 6952f are adjusted in the layout editing UI 8000. The user associates the parent icon 6951 and the child icons 6952a to 6952f with a plurality of industrial devices in the layout map 6532. In particular, some industrial devices (e.g., press machine, drilling machine, lathe, sensor) are connected to the LAN ports 38i of the child devices 202a to 202f. Furthermore, the child devices 202a to 202f are installed on the top surface of the corresponding industrial device or on a pole or the like installed near the industrial device. Therefore, the user edits the display positions of the parent icon 6951 and the child icons 6952a to 6952f according to the installation positions of the industrial devices in the layout map 6532. This allows not only visually grasping which wireless devices are connected to which industrial devices, but also visually grasping the installation positions of the wireless devices.

[0344] FIG. 75 shows a UI 6900 displayed after the layout editing is completed. The map display unit 6901 displays a wireless map 6531 and a layout map 6532 in an overlapping manner. In particular, the layout map 6532 is displayed as a background image with a specified transparency. In the wireless map 6531, the display positions of the parent device icon 6951 and the child device icons 6952a to 6952f are changed by the layout editing. In addition, the connection line 6954 is arranged so as to connect the child devices registered in the child device list 253 as being in a connected relationship. In addition, as described above, when a warning or an error occurs, the display state of the parent device icon 6951 and the child device icons 6952a to 6952f is changed to a display state corresponding to the warning or error.

[0345] 5-4. Display of redundant routes 76 shows that a redundant route display button 8500 has been added to the UI 6900. When the industrial wireless network 204 is a mesh network, the hop destinations of the child devices 202a to 202f may be dynamically changed depending on the wireless conditions. This is called an automatic recovery function or a reroute function.

[0346] Therefore, when the display button 8500 is pressed on the PC2, the map display processing unit 6511 of the parent device 201 may add connection lines 8501a and 8501b indicating redundant routes to the wireless map 6531 in addition to the connection line 6954 indicating the main wireless section, and update the UI 6900 displayed on the PC2. In this example, when the display button 8500 is turned on, one of the child device icons 6952a to 6952f is designated by the pointer 103. In this example, because the child device icon 6952e is clicked, the connection lines 8501a and 8501b indicating the redundant route for the child device 202e are additionally displayed. When the display button 8500 is turned off, the connection lines 8501a and 8501b are also deleted. Also, redundant routes may be displayed for multiple child devices 202 at the same time. By checking the redundant paths, the user may change the placement of the child devices 202 so that more redundant paths are secured, or may add new child devices 202 so that more redundant paths are secured.

[0347] 5-5. Suggested content for other errors and warnings An increase in ambient noise is one type of warning state. In this case, the explanation information 7211 of the suggestion dialog 7200 includes a message indicating that there is a lot of ambient noise, and that this is causing a decrease in wireless performance (such as communication speed). The suggestion content 7212 may include a message or image indicating that the distance between the noise source and the child device should be increased.

[0348] A rise in temperature of the child device 202 is also one of the warning states. In this case, the explanation information 7211 of the suggestion dialog 7200 includes a message indicating that the internal temperature of the child device 202 is high, and that the communication speed is decreasing due to the high temperature. The suggestion content 7212 may include a message or an image indicating that the communication volume of the industrial equipment connected to the child device 202 should be reduced, that the temperature (room temperature) of the installation environment (ambient environment) should be lowered, that the child device 202 should not be exposed to direct sunlight, that airflow for the child device 202 should be ensured, and the like.

[0349] The system program version warning is a warning state that occurs when the version of the system program of the child device 202 is older than the version of the system program of the parent device 201. In this case, the explanation information 7211 of the suggestion dialog 7200 suggests that new functions cannot be used because the system program of the child device 202 is older, that the system program should be updated, etc.

[0350] The parent machine child machine loss error is a warning state that the child machine 202a connected to the parent machine 201 is lost. The comment information 7211 includes a message indicating that the child machine 202a connected to the parent machine 201 by wire is not found, that the entire industrial wireless network 204 will stop if the child machine 202a is lost, and the like. The suggested content 7212 includes a message and an image indicating that the power switch of the child machine 202a connected to the parent machine 201 by wire should be turned on. The suggested content 7212 may include a message and an image indicating that the child machine 202a should be connected to one of the LAN ports 38e to 38h of the parent machine 201.

[0351] When an unregistered child device is detected (warning state), the explanatory information 7211 includes a message suggesting that there is a child device 202 that is not officially registered in the parent device 201, and that this may cause the industrial wireless network 204 to not operate normally. The suggested content 7212 includes a message and an image suggesting that the child device 202 whose indicator light 224 is flashing red should be initialized by using a reset switch, and that the child device addition button 6907 should be used to transition to a child device addition screen and officially add the child device 202.

[0352] 6.Other The suggested content 7212 may include images. Images for more frequently occurring warning conditions may be video or animated, while images for less frequently occurring warning conditions may be still images.

[0353] Furthermore, multiple warning states or error states may occur in a superimposed manner for one child device 202. In this case, the CPU 210 (map display processing unit 6511) may display high-priority warning states or error states on the UI 6900 in a wired manner according to the display priorities associated with each of the multiple warning states or error states. For example, a warning state that disables wireless communication may have a high priority, and a warning state that reduces wireless performance may have a relatively low priority. In other words, the priority may be determined according to the seriousness of the warning. The priorities associated with the warning states and error states may be stored in the storage device 211.

[0354] [Point 1] A network controller that acts as a parent device (e.g., parent device 201), A plurality of wireless nodes (e.g., child device 202) each having a port (e.g., LAN port 38i) for wired connection to industrial equipment, managed by the network controller, and operating as child devices; and displaying, on a display device (e.g., a PC 2, a display, a Web browser 60), a communication status of the plurality of wireless nodes provided by the network controller, A collection unit (e.g., CPU 210, status management unit 6500) that collects status information (e.g., communication status 6621, error / warning determination result 6622, response signal to inquiry signal) indicating the communication status of each of the plurality of wireless nodes; a map display processing unit that causes the display device to display a wireless network map (e.g., a wireless map 6531) that visually indicates whether the communication status of each of the plurality of wireless nodes is a normal state in which communication can be performed normally or a plurality of different abnormal states (e.g., ) in which communication cannot be performed normally based on the status information collected by the collection unit; and A selection unit (e.g., the CPU 210, the suggestion management unit 6512) that selects candidates for countermeasures for eliminating or mitigating at least one of the plurality of non-normal states when the communication state corresponds to at least one of the non-normal states; a candidate display processing unit (e.g., CPU 210, map display processing unit 6511, suggestion management unit 6512) that displays the candidate countermeasures selected by the selection unit on the display device; An industrial wireless system having

[0355] As described above, according to the present embodiment, the user can not only visually grasp the state of the wireless network in the industrial wireless system, but also know how to deal with abnormal states. Furthermore, even a user with little knowledge of wireless communication can easily maintain the soundness and wireless performance of the industrial wireless system. Therefore, the usability of the industrial wireless system is improved.

[0356] [Point 2] the plurality of abnormal states include at least a first abnormal state (e.g., a lost child state) in which a communication link is disconnected for any of the plurality of wireless nodes, and a second abnormal state (e.g., a low radio wave strength warning state) in which a radio wave reception strength of any of the wireless nodes falls below a predetermined threshold, The candidate display processing unit When the communication state is the first abnormal state, displaying on the display device a first candidate countermeasure (e.g., removing radio wave obstructions, ensuring visibility) for mitigating or eliminating the first abnormal state; When the communication state is the second abnormal state, displaying on the display device a second countermeasure candidate (e.g., shortening the distance between the slave units) for mitigating or eliminating the second abnormal state; 2. An industrial wireless system as described in aspect 1.

[0357] In this way, appropriate corrective measures are suggested in response to abnormal conditions, making it easier for even users with little knowledge of wireless communications to maintain the health and wireless performance of their industrial wireless systems.

[0358] The first abnormal state does not need to be a state in which the communication link is disconnected, and it is sufficient that the degree of failure in the first abnormal state is higher than the degree of failure in the second abnormal state. For example, it is sufficient that the wireless performance (e.g., communication speed, radio wave strength, signal-to-interference-plus-noise ratio) realized in the first abnormal state is lower than the wireless performance realized in the second abnormal state.

[0359] [Point 3] The first candidate countermeasure is: Confirming that the power switch of the wireless node in the first abnormal state is turned on (e.g., suggestion content 7212d); Confirming a distance between the wireless node in the first abnormal state and another wireless node (e.g., suggestion content 7212e); Confirming a line of sight between the wireless node in the first abnormal state and the other wireless node (e.g., suggestion content 7212e); Checking radio interference with wireless devices present around the wireless node in the first abnormal state (e.g., suggestion content 7212g); Changing the channel of the wireless node (e.g., suggestion content 7212g) The industrial wireless system according to aspect 2, comprising at least one of:

[0360] This makes it possible to recover the child device 202 that is in a lost state due to the disconnection of the wireless link. Although the suggested content 7212g is not shown in Fig. 67, the suggested content 7212g may be selected and displayed even when the child device is lost. This is because the cause of the loss of the child device may be the contention of the wireless channel or the influence of radio noise.

[0361] [Point 4] The second candidate countermeasure is: shortening a distance between the first wireless node in the second abnormal state and another second wireless node communicating with the first wireless node (e.g., suggestion content 7212a); adding a third wireless node between the first wireless node and the second wireless node (e.g., suggestion content 7212c); moving at least one of the first wireless node and the second wireless node, or moving an obstacle between the first wireless node and the second wireless node, so that a line of sight is secured between the first wireless node and the second wireless node (e.g., suggestion content 7212b); The industrial wireless system according to aspect 2, comprising at least one of:

[0362] This allows the user to improve the radio wave reception strength.

[0363] [Point 5] The industrial wireless system according to Aspect 2, wherein when the communication state is the first non-normal state and the second non-normal state, the candidate display processing unit displays the first countermeasure candidate in priority over the second countermeasure candidate.

[0364] A plurality of countermeasures corresponding to a plurality of non-normal conditions may be displayed simultaneously or in parallel, and the countermeasures may be prioritized. For example, when a plurality of non-normal conditions occur simultaneously, a countermeasure for a non-normal condition having a higher urgency or priority may be displayed preferentially. This allows the user to easily understand which countermeasure should be immediately taken.

[0365] [Point 6] Each of the plurality of wireless nodes further includes an indicator light and a control unit (e.g., a CPU 220, an indicator light management unit 6610) that controls a display mode of the indicator light, In the industrial wireless system described in aspect 1, when the communication state of any of the wireless nodes among the plurality of wireless nodes is an abnormal state, the candidate display processing unit causes the display device to display candidate countermeasures for mitigating or eliminating the abnormal state of the wireless node, and the control unit changes the display mode (e.g., changing the lighting color) of the indicator light of the wireless node in the abnormal state.

[0366] This allows the user to know when an error or warning has occurred by checking the indicator light, and further allows the user to immediately resolve the error or warning by checking the countermeasures on the display device.

[0367] [Point 7] The plurality of abnormal conditions include: An error state in which communication of any one of the plurality of wireless nodes may be impaired relatively severely (e.g., loss of a child device, significant degradation of wireless performance); and A warning state in which communication of any one of the plurality of wireless nodes may be subject to a relatively minor impairment (e.g., a decrease in wireless performance); and Including, The industrial wireless system of aspect 6, wherein when the communication status of any of the plurality of wireless nodes is in the warning state, the candidate display processing unit causes the display device to display countermeasures for mitigating or resolving the warning state.

[0368] Generally, a warning condition will occur before an error condition, i.e., the warning condition is a precursor to the error condition, so the user will be able to prevent the transition from a warning condition to an error condition by taking appropriate action when the warning condition occurs.

[0369] [Point 8] the error state is a state in which a communication link of the wireless node is disconnected; The warning state is a state in which the communication link of the wireless node is maintained, but the reception strength of the radio wave received by the wireless node is lower than a threshold value. 8. An industrial wireless system as described in aspect 7.

[0370] In this way, when the radio signal strength drops below the threshold, it is a sign that the communication link is about to be disconnected. By taking appropriate measures when the radio signal strength drops below the threshold, the user can prevent the communication link from being disconnected.

[0371] [Point 9] The network controller includes: The industrial wireless system according to aspect 8, further comprising a monitoring unit that transmits an inquiry signal to a wireless node of interest among the plurality of wireless nodes, and monitors whether the communication link of the wireless node of interest is disconnected depending on whether a response signal to the inquiry signal is received.

[0372] In general, when a child device is lost, it becomes difficult to obtain status information from the child device. Therefore, the network controller (parent device 201) may execute keep-alive for each wireless node (child device 202). The parent device 201 selects one child device 202 from the multiple child devices 202 as a child device of interest and transmits an inquiry signal. The parent device 201 can determine whether the child device of interest has been lost depending on whether a response signal has been received from the child device of interest. In this way, even if the parent device 201 cannot obtain status information from the child device of interest, the parent device 201 can determine the communication status of the child device of interest.

[0373] [Point 10] When the communication state is the error state, both the display device and the indicator light execute a notification to a user. The industrial wireless system of Aspect 7, wherein, when the communication state is the warning state, the display device notifies a user, and the indicator light does not notify a user.

[0374] In this way, the notification method may be changed depending on the communication state. That is, when a fault with a high urgency is detected, notification is performed by more notification means, and when a fault with a low urgency is detected, notification is performed by fewer notification means.

[0375] [Point 11] The wireless network map includes: A node object (e.g., a child device icon 6952) visually representing each of the plurality of wireless nodes; A line object (e.g., a connection line 6954) visually representing the communication state of the plurality of wireless nodes; Including, The industrial wireless system according to aspect 1, wherein when a communication state of any one of the plurality of wireless nodes changes, the map display processing unit changes a display mode of at least one of the node objects or the line objects corresponding to the any one of the wireless nodes.

[0376] In this way, by changing the display mode of at least one of the node objects and the line objects, the user will be able to easily grasp the wireless node and its wireless section in which a problem is occurring.

[0377] [Point 12] The industrial wireless system described in aspect 1, wherein the map display processing unit causes the display device to display a layout diagram (e.g., layout map 6532) that visually represents the layout of multiple industrial devices in association with the wireless network map.

[0378] This allows the user to understand the relationship between the placement of wireless nodes and the placement of industrial equipment, and also makes it easier for the user to determine where to move the wireless nodes in relation to the industrial equipment.

[0379] [Point 13] The map display processing unit: by displaying the wireless network map transparently against the layout diagram; or The industrial wireless system of aspect 12, wherein the layout diagram is displayed on the display device in a transparent manner relative to the wireless network map.

[0380] Superimposing the wireless network map and the layout diagram may make it difficult for a user to see them, so by making one transparent to the other, the user may be able to more easily understand the wireless network map and the layout diagram.

[0381] [Point 14] the network controller includes a web server; The industrial wireless system according to aspect 1, wherein the map display processing unit causes a web browser running on the display device to display the wireless network map via the web server.

[0382] By adopting web technology in this way, it will become easier to use personal computers, tablet devices, smartphones, etc. as display devices.

[0383] [Point 15] The industrial wireless system includes a network controller that operates as a parent device, and a plurality of wireless nodes that each have a port for wired connection to an industrial device and are managed by the network controller and operate as child devices, and the network controller displays communication states of the plurality of wireless nodes provided by the network controller on a display device, a collection unit for collecting state information indicating a communication state of each of the plurality of wireless nodes; a map display processing unit that causes the display device to display a wireless network map visually indicating whether a communication state of each of the plurality of wireless nodes is a normal state in which communication can be performed normally or a plurality of different abnormal states in which communication cannot be performed normally based on the state information collected by the collection unit; and a selection unit that selects, when the communication state corresponds to at least one of the plurality of abnormal states, a candidate countermeasure for eliminating or mitigating the at least one abnormal state; a candidate display processing unit that displays the candidate measures selected by the selection unit on the display device; A network controller having:

[0384] [Point 16] a network controller that operates as a parent device; a plurality of wireless nodes each having a port for wired connection to an industrial device, the wireless nodes being managed by the network controller and operating as child devices; A control method for an industrial wireless system, comprising: displaying, on a display device, communication states of the plurality of wireless nodes provided from the network controller, the control method comprising: a collection step of collecting status information indicating a communication status of each of the plurality of wireless nodes; a map display processing step of displaying on the display device a wireless network map visually indicating whether the communication status of each of the plurality of wireless nodes is a normal status in which normal communication can be performed or a plurality of different abnormal statuses in which normal communication cannot be performed, based on the status information collected in the collection step; a selection step of selecting, when the communication state corresponds to at least one of the plurality of abnormal states, a candidate countermeasure for eliminating or mitigating the at least one abnormal state; a candidate display process for displaying the candidate measures selected in the selection process on the display device; 23. A method for controlling an industrial wireless system comprising:

[0385] 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. a network controller that operates as a parent device; a plurality of wireless nodes each having a port for wired connection to an industrial device, the wireless nodes being managed by the network controller and operating as child devices; An industrial wireless system comprising: a display device that displays communication states of the plurality of wireless nodes provided from the network controller, a collection unit for collecting state information indicating a communication state of each of the plurality of wireless nodes; a map display processing unit that causes the display device to display a wireless network map visually indicating whether a communication state of each of the plurality of wireless nodes is a normal state in which communication can be performed normally or a plurality of different abnormal states in which communication cannot be performed normally based on the state information collected by the collection unit; and a selection unit that selects, when the communication state corresponds to at least one of the plurality of abnormal states, a candidate countermeasure for eliminating or mitigating the at least one abnormal state; a candidate display processing unit that displays the candidate measures selected by the selection unit on the display device; An industrial wireless system having

2. the plurality of abnormal states include at least a first abnormal state in which a communication link is disconnected for any one of the plurality of wireless nodes, and a second abnormal state in which a radio wave reception strength of any one of the wireless nodes falls below a predetermined threshold; The candidate display processing unit when the communication state is the first abnormal state, displaying on the display device a first candidate countermeasure for mitigating or eliminating the first abnormal state; when the communication state is the second abnormal state, displaying on the display device a second countermeasure candidate for mitigating or eliminating the second abnormal state; 2. The industrial wireless system of claim 1.

3. The first countermeasure candidate is: confirming that a power switch of the wireless node in the first abnormal state is turned on; confirming a distance between the wireless node in the first abnormal state and another wireless node; confirming a line of sight between the wireless node in the first abnormal state and the other wireless node; checking radio interference with wireless devices present around the wireless node in the first abnormal state; changing the channel of the wireless node; 3. The industrial wireless system of claim 2, comprising at least one of:

4. The second countermeasure candidate is: shortening a distance between a first wireless node in the second abnormal state and another second wireless node communicating with the first wireless node; adding a third wireless node between the first wireless node and the second wireless node; moving at least one of the first wireless node and the second wireless node, or moving an obstacle between the first wireless node and the second wireless node, so that a line of sight is secured between the first wireless node and the second wireless node; 3. The industrial wireless system of claim 2, comprising at least one of:

5. 3. The industrial wireless system of claim 2, wherein when the communication state is the first abnormal state and the second abnormal state, the candidate display processing unit displays the first countermeasure candidate with priority over the second countermeasure candidate.

6. Each of the plurality of wireless nodes further includes an indicator light and a control unit that controls a display mode of the indicator light, 2. The industrial wireless system according to claim 1, wherein, when the communication state of any of the wireless nodes among the plurality of wireless nodes is an abnormal state, the candidate display processing unit causes the display device to display candidates for countermeasures for mitigating or eliminating the abnormal state of the wireless node, and the control unit changes a display mode of the indicator light of the wireless node in the abnormal state.

7. The plurality of abnormal conditions include: an error state in which communication of any one of the plurality of wireless nodes may be relatively seriously impaired; and a warning state in which communication of any one of the plurality of wireless nodes may be impaired to a relatively minor extent; and Including, 7. The industrial wireless system according to claim 6, wherein, when a communication state of any wireless node among the plurality of wireless nodes is in the warning state, the candidate display processing unit causes the display device to display countermeasures for mitigating or eliminating the warning state.

8. the error state is a state in which a communication link of the wireless node is disconnected; The warning state is a state in which the communication link of the wireless node is maintained, but the reception strength of the radio wave received by the wireless node is lower than a threshold value.

8. The industrial wireless system of claim 7.

9. The network controller includes:

9. The industrial wireless system according to claim 8, further comprising a monitoring unit that transmits an inquiry signal to a target wireless node among the plurality of wireless nodes, and monitors whether the communication link of the target wireless node is disconnected depending on whether a response signal to the matching signal is received.

10. When the communication state is the error state, both the display device and the indicator light execute a notification to a user. When the communication state is the warning state, the display device issues a notification to a user, and the indicator light does not issue a notification to the user.

8. The industrial wireless system of claim 7.

11. The wireless network map includes: a node object visually representing each of the plurality of wireless nodes; a line object visually representing a communication state of the plurality of wireless nodes; Including, 2. The industrial wireless system according to claim 1, wherein when a communication state of any one of the plurality of wireless nodes changes, the map display processing unit changes a display mode of at least one of the node object or the line object corresponding to the any one of the wireless nodes.

12. 2. The industrial wireless system according to claim 1, wherein the map display processing unit causes the display device to display a layout diagram visually representing a layout of a plurality of industrial devices in association with the wireless network map.

13. The map display processing unit: by displaying the wireless network map transparently against the layout diagram; or The industrial wireless system of claim 12 , wherein the layout diagram is displayed on the display device in a transparent manner relative to the wireless network map.

14. the network controller includes a web server; 2. The industrial wireless system according to claim 1, wherein the map display processing unit causes a Web browser running on the display device to display the wireless network map via the Web server.

15. The industrial wireless system includes a network controller that operates as a parent device, and a plurality of wireless nodes that each have a port for wired connection to an industrial device and are managed by the network controller and operate as child devices, and the network controller displays communication states of the plurality of wireless nodes provided by the network controller on a display device, a collection unit for collecting state information indicating a communication state of each of the plurality of wireless nodes; a map display processing unit that causes the display device to display a wireless network map visually indicating whether a communication state of each of the plurality of wireless nodes is a normal state in which communication can be performed normally or a plurality of different abnormal states in which communication cannot be performed normally based on the state information collected by the collection unit; and a selection unit that selects, when the communication state corresponds to at least one of the plurality of abnormal states, a candidate countermeasure for eliminating or mitigating the at least one abnormal state; a candidate display processing unit that displays the candidate measures selected by the selection unit on the display device; A network controller having:

16. a network controller that operates as a parent device; a plurality of wireless nodes each having a port for wired connection to an industrial device, the wireless nodes being managed by the network controller and operating as child devices; A control method for an industrial wireless system, comprising: displaying, on a display device, communication states of the plurality of wireless nodes provided from the network controller, the control method comprising: a collection step of collecting status information indicating a communication status of each of the plurality of wireless nodes; a map display processing step of displaying on the display device a wireless network map visually indicating whether the communication status of each of the plurality of wireless nodes is a normal status in which normal communication can be performed or a plurality of different abnormal statuses in which normal communication cannot be performed, based on the status information collected in the collection step; a selection step of selecting, when the communication state corresponds to at least one of the plurality of abnormal states, a candidate countermeasure for eliminating or mitigating the at least one abnormal state; a candidate display process for displaying the candidate measures selected in the selection process on the display device; 23. A method for controlling an industrial wireless system comprising:

Images