WO2022190501A1

WO2022190501A1 - Network apparatus and network system

Info

Publication number: WO2022190501A1
Application number: PCT/JP2021/046562
Authority: WO
Inventors: 寛仁水本
Original assignee: オムロン株式会社
Priority date: 2021-03-08
Filing date: 2021-12-16
Publication date: 2022-09-15
Also published as: JP2022136796A

Abstract

Provided is a network apparatus with which, when an anomaly has occurred in a slave device, it is possible to easily identify the scope of influence of the slave device experiencing the anomaly. A control unit (24) of a network apparatus (2N), upon receiving a reply from another slave apparatus (2) indicating the presence of an anomaly, or when an anomaly is detected by an anomaly detection unit (22), causes an anomaly notification unit (23) to execute anomaly notification, and sends, to another slave device (2) registered in a configuration list, an instruction to execute anomaly notification.

Description

Network equipment and network system

The present disclosure relates to network equipment and network systems using the same.

In the field of Factory Automation (FA), various types of devices are controlled that share work processes. In order to operate various controllers, remote I/O, and manufacturing equipment used for work in a certain area such as a factory facility in cooperation with each other, an industrial network, also called a field network, is constructed to connect these equipment. there is

　General industrial networks adopt a master-slave system consisting of various slave devices and master devices. A slave device is a device that controls equipment installed in a factory or collects data. The master device is a device called (PLC: Programmable Logic Controller) that centrally manages these slave devices.

A conventional slave device has a signal light, and there is a known technology for notifying a user such as a person in charge of manufacturing of the operating state of the slave device by lighting the signal light (see, for example, Patent Document 1).

Japanese Patent Publication JP 2019-68239

However, in a network system having conventional slave devices as described above, when an abnormality occurs in a slave device, it is difficult to identify other slave devices that cooperate with the slave device. That is, in the conventional network system, when an abnormality occurs in a slave device, there is a problem that it is difficult to specify the affected range of the slave device in which the abnormality has occurred.

SUMMARY OF THE INVENTION The present disclosure has been made in view of the above problems, and provides a network device and a network system that can easily identify the range of influence of a slave device that has caused an abnormality, even when an abnormality occurs in the slave device. intended to provide

The present disclosure adopts the following configuration in order to solve the above problems.

A network device according to one aspect of the present disclosure is a network device, which is the slave device used in a network system in which a master device and a plurality of slave devices controlled by the master device are connected, wherein the other slave devices A group including a communication unit that transmits and receives data to and from a device, an anomaly detection unit that detects anomalies, an anomaly reporting unit that reports an anomaly, the network device, and at least one other slave device. and a control unit for controlling each unit of the network device, wherein the control unit communicates with the other slave devices registered in the configuration list through the communication unit If there is a reply from another slave device that there is an abnormality, or if the abnormality detection unit detects an abnormality, the abnormality notification unit is caused to perform abnormality notification. In addition, a configuration is provided for transmitting, through the communication unit, an instruction to execute anomaly notification to the other slave devices registered in the configuration list.

According to the present disclosure, it is possible to provide a network device and a network system that can easily identify the influence range of a slave device that has caused an abnormality even when an abnormality occurs in the slave device.

1 is an explanatory diagram illustrating a configuration example of a network system according to Embodiment 1 of the present disclosure; FIG. 1 is a schematic configuration diagram showing a network device (slave device) according to Embodiment 1 of the present disclosure; FIG. 4 is a flow chart showing a setting operation of a control group configuration list in the network system; 2 is a diagram showing a specific example of a configuration list that is set on the information processing apparatus side shown in FIG. 1; FIG. FIG. 4 is a diagram showing a specific example of a configuration list set on the network device side; FIG. 4 is a diagram showing a specific example of a configuration list set on another network device side; 4 is a flowchart for explaining an operation example of the network device; FIG. 10 is a flowchart illustrating an operation example of a network device according to Embodiment 2 of the present disclosure; FIG.

[Embodiment 1]
Hereinafter, an embodiment (hereinafter also referred to as "this embodiment") according to one aspect of the present invention will be described based on the drawings.

§1 Application Example First, an example of a scene to which the present disclosure is applied will be described with reference to FIGS. 1 and 2. FIG. FIG. 1 is an explanatory diagram illustrating a configuration example of a network system according to Embodiment 1 of the present disclosure. FIG. 2 is a schematic configuration diagram showing a network device (slave device) according to Embodiment 1 of the present disclosure.

In the following description, the network device of this embodiment, which is a slave device, has the same configuration as other slave devices as shown in FIG. In the network system 100 of this embodiment, for example, eight

slave devices

2A, 2B, 2C, 2D, 2E, 2F, 2G, and 2H (hereinafter collectively referred to as "2") are used as a plurality of slave devices. A case of connection will be described as an example. Also, when the slave device is a network device according to this embodiment, it may be expressed as a network device 2N.

The network system 100 of this embodiment is a network system in which a master device 1 and a plurality of slave devices 2 controlled by the master device 1 are connected. Also, the network device 2N of this embodiment is connected to the network system 100 as one slave device 2 described above. At least one network device 2N is connected as a slave device 2 in the network system 100 of the present embodiment.

Also, the network system 100 of this embodiment includes an information processing device 3 . An administrator of the network system 100 can execute various settings of the master device 1 and the slave devices 2, acquire data, and the like through the information processing device 3. FIG. Furthermore, the network system 100 of the present embodiment has a display device 4, which can display the operation status of the network system 100 and the like.

Further, the network device 2N of this embodiment includes a communication unit 21 that transmits and receives data to and from other slave devices 2, an abnormality detection unit 22 that detects an abnormality, and an abnormality notification unit 23 that performs abnormality notification. , a storage unit 25 that stores in advance a configuration list of a control group (group) including the network device 2N and at least one other slave device 2, and a control unit that controls each part (component) of the network device 2N. 24. In the storage unit 25, the configuration list of the above-described control groups is set in advance by the information processing device 3. FIG.

The control unit 24, through the communication unit 21, inquires of the other slave devices 2 registered in the configuration list whether there is an abnormality. Then, the control unit 24 causes the abnormality notification unit 23 to perform abnormality notification when there is a response from another slave device 2 that there is an abnormality, or when the abnormality detection unit 22 detects an abnormality. Furthermore, the control unit 24 transmits an instruction to execute the anomaly notification to the other slave devices 2 registered in the configuration list.

Therefore, according to the present embodiment, even when an abnormality occurs in the slave device 2, the network device 2N and the network using the network device 2N can easily identify the affected range of the slave device 2 in which the abnormality has occurred. System 100 can be configured.

§2 Configuration example <Network system>
In the example of FIG. 1, the network system 100 of this embodiment includes a master device 1, a plurality of slave devices 2 connected to the master device 1 via communication devices (communication hubs) 5A and 5B, and a communication device 5A. It includes an information processing device 3 and a display device 4 which are connected to the master device 1 via. Also, in the network system 100 of the present embodiment, for example, a network system conforming to the ETHERNET/IP standard is used (ETHERNET: registered trademark). Further, in the network system 100 of the present embodiment, for example, communication cables are used to connect the master device 1, the slave device 2, the information processing device 3, the display device 4, and the

communication devices

5A and 5B as illustrated in FIG. , and communication is performed via a communication cable.

The master device 1 includes, for example, a PLC (Programmable Logic Controller). Also, the master device 1 is configured to control each of the plurality of slave devices 2 by operating according to a predetermined program that can be set from the information processing device 3 or the like.

For example, four

slave devices

2A, 2B, 2C, and 2D are sequentially connected to the communication device 5B, and four

slave devices

2E, 2F, 2G, and 2H are sequentially connected to the communication device 5B. Further, in the slave device 2, based on the control group configuration list set by the information processing device 3, for example, the slave devices are grouped into two control groups C1 and C2 as encircled by a dotted line in FIG. That is, control group C1 includes six

slave devices

2A, 2B, 2C, 2D, 2E and 2F, and control group C2 includes two slave devices 2G and 2H.

Furthermore, in each of the control groups C1 and C2, at least one slave device 2 holds the configuration list from the information processing device 3 in advance, thereby configuring the network device 2N in the control groups C1 and C2. ing. In each of the control groups C1 and C2, the network device 2N monitors the occurrence of an abnormality in the slave device 2, and when an abnormality occurs in the slave device 2, the control groups C1 and C2 are notified of the occurrence of an abnormality. It is configured to display (details will be described later).

For example, when the network system 100 of the present embodiment is applied to a manufacturing facility in a factory, the slave devices 2 included in the control group can detect an abnormality in a production line unit or a production processing unit of a product included in the manufacturing facility. is preferably determined in consideration of the range of influence of the slave device 2 that caused the In other words, in such a case, it is possible to quickly confirm the slave device 2 in which an abnormality has occurred and the slave device 2 cooperating with it, and furthermore, it is possible to quickly take measures against the abnormality. It becomes possible to easily prevent the production efficiency of things from declining.

The information processing device 3 is configured using a computer (PC), for example, and controls each part of the master device 1, the slave device 2, and the display device 4 by being operated by the user. In addition, the information processing device 3 presets, for example, the configuration list of the control group C1 for the slave devices 2A and 2E included in the control group C1 according to the user's operation, and sets these slave devices 2A. , 2E be the network device 2N in the control group C1. As described above, in the network system 100 of the present embodiment, the configuration of the slave devices 2 and the settings of the network devices 2 in each of the control groups C1 and C2 can be freely configured by appropriately operating the information processing device 3 by the user. can be changed.

The display device 4 is configured using, for example, a liquid crystal panel, an organic EL panel, or the like that has a touch panel function. The display device 4 operates based on, for example, an HMI (Human Machine Interface) to display predetermined information and perform input operations such as instructions.

<Network equipment>
In the example of FIG. 2, the network device 2N of this embodiment includes a communication section 21, an abnormality detection section 22, an abnormality notification section 23, a control section 24, and a storage section 25. FIG. Further, the network device 2N of the present embodiment communicates with another slave device 2 of the control group based on the configuration list of the control group stored in advance in the storage unit 25, thereby monitor the slave device 2 of

The communication unit 21 is a functional block that performs two-way communication with other devices of the network system 100. In other words, the network device 2N transmits and receives data such as an inquiry and a reply to the inquiry with the above-mentioned other devices through the communication unit 21 .

The anomaly detection unit 22 is a functional block that detects an anomaly that has occurred in the network device 2N. Specifically, the abnormality detection unit 22 detects, for example, an abnormality in the operation of the network device 2N itself or an abnormality in the operation of devices controlled by the network device 2N. When detecting an abnormality, the abnormality detection section 22 notifies the control section 24 of the occurrence of the abnormality.

The abnormality notification unit 23 has, for example, an LED (Light Emitting Diode) 23L as a first light emitting element. An abnormality is notified by turning on the light. Thereby, the user can visually recognize the range of influence when an abnormality occurs in the slave device 2 (including the network device 2N) in the control group. The abnormality notification unit 23 is not limited to the LED (light emitting element) 23L as long as it can notify the user of abnormality. Specifically, for example, it has a speaker and has an audio output unit that emits a predetermined beep sound or siren sound, and an image display that has a liquid crystal panel, an organic EL panel, a micro LED, or the like and displays a predetermined image. The anomaly notification unit 23 can be configured by an appropriate combination of these units.

In the above description, an abnormality notification is performed by lighting the LED 23L, but the method of abnormality notification by the abnormality notification unit 23 is not limited to this. There is no particular limitation as long as it is lit in a pattern. For example, the configuration may be such that the LED 23L is turned on when no abnormality has occurred (in a normal state), and the light emission state and the light emission period of the LED 23L are changed, such as blinking when an abnormality occurs. Further, this abnormality notification method is the same for a second light emitting element (LED) provided in the slave device 2, which will be described later.

The storage unit 25 is, for example, an auxiliary storage device such as a hard disk drive or solid state drive, and stores various processing programs executed by the control unit 24. The storage unit 25 also stores in advance a control group configuration list set by the information processing device 3 .

The control unit 24 is a functional block that includes, for example, a CPU (Central Processing Unit), RAM (Random Access Memory), ROM (Read Only Memory), etc., and controls each component according to information processing. Also, the control unit 24 performs a monitoring operation of monitoring each slave device 2 of a control group preset in the storage unit 25 .

Further, when the control unit 24 receives a determination result indicating that an abnormality has occurred from the abnormality detection unit 22, the control unit 24 turns on the abnormality notification unit 23, and transmits the above configuration stored in the storage unit 25 through the communication unit 21. An instruction to execute anomaly notification is transmitted to other slave devices 2 included in the list. As a result, in the other slave device 2, for example, an LED as a second light emitting element, which is included in the anomaly notification unit of the other slave device 2, lights up, and the slave devices 2 (including the network device 2N) included in the control group turn on. It is reported that an abnormality has occurred.

Further, the control unit 24 inquires of the other slave devices 2 registered in the configuration list about the presence or absence of an abnormality via the communication unit 21, and receives a reply from the other slave device 2 that there is an abnormality. In this case, the anomaly notification unit 23 is turned on, and the other slave devices 2 included in the configuration list stored in the storage unit 25 are notified via the communication unit 21 to the effect that the anomaly notification should be executed. Send instructions. As a result, in the other slave device 2, for example, an LED as a second light emitting element, which is included in the anomaly notification unit of the other slave device 2, lights up, and the slave devices 2 (including the network device 2N) included in the control group turn on. It is reported that an abnormality has occurred.

Furthermore, after the control unit 24 inquires about the presence or absence of an abnormality to the other slave devices 2 registered in the configuration list through the communication unit 21, there are other slave devices 2 that do not reply to the inquiry. In this case, the anomaly notification unit 23 is turned on, and an instruction is given to the other slave devices 2 included in the configuration list stored in the storage unit 25 via the communication unit 21 to execute an anomaly notification. to send. As a result, in the other slave device 2, for example, an LED as a second light emitting element, which is included in the anomaly notification unit of the other slave device 2, lights up, and the slave devices 2 (including the network device 2N) included in the control group turn on. It is reported that an abnormality has occurred.

Thus, even if the network device 2N cannot communicate with the other slave device 2, the network device 2N determines that an abnormality has occurred in the other slave device 2 and It is possible to easily identify the range of influence of the slave device 2 that caused the error. In other words, the network device 2 of the present embodiment can be used even in the case of a communication failure caused by poor connection, disconnection, noise, etc. in the communication cable between the network device 2 and the other slave device 2, or when the slave device 2 is replaced. Even in the event of a communication interruption, it is possible to determine that an abnormality has occurred and notify the slave devices 2 (including the network device 2N) of the control group that an abnormality has occurred.

§3 Operation example <Setting operation>
First, referring also to FIGS. 3 to 6, the setting operation of the control group configuration list will be described. FIG. 3 is a flow chart showing the setting operation of the control group configuration list in the network system. FIG. 4 is a diagram showing a specific example of a configuration list that is set on the information processing apparatus side shown in FIG. FIG. 5 is a diagram showing a specific example of a configuration list set on the network device side. FIG. 6 is a diagram showing a specific example of a configuration list set on another network device side. In the following description of the operation example, the configuration lists Ls1 and Ls2 are set for the slave devices 2A and 2E among the slave devices 2 of the control group C1 shown in FIG. A case where 2A and 2E are network devices 2N will be described as an example.

First, in step S101, the information processing device 3 selects the slave device 2 to be included in the control group C1 and the network device 2N in the control group C1 based on the user's operation. A configuration list Ls is created. That is, in the configuration list Ls, as shown in FIG. 4, information (for example, IP addresses) for identifying the

slave devices

2A, 2B, 2C, 2D, 2E, and 2F included in the control group C1, and network device Information indicating that it has been selected as 2N is described in a table format.

Next, in step S102, the information processing device 3 transfers the created configuration list Ls to the slave devices 2A and 2E selected as the network device 2N. As a result, the slave device 2A stores the configuration list Ls1 shown in FIG. 2D, 2E, and 2F are slave devices 2 to be monitored. Also, in this configuration list Ls1, information (for example, IP addresses) for specifying the

slave devices

2A, 2B, 2C, 2D, 2E, and 2F included in the control group C1 and their own devices or other devices to be monitored is described in a table format.

Similarly, the slave device 2E stores the configuration list Ls2 shown in FIG. , 2D and 2F are slave devices 2 to be monitored. In addition, in this configuration list Ls2, information (for example, IP addresses) for specifying the

slave devices

Thus, in this embodiment, by setting two or more network devices 2N in the control group C1, each network device 2N can be monitored by other network devices 2N, and one network device 2N can be monitored. Even if an abnormality occurs in the network device 2N and the network device 2N cannot perform the abnormality notification in the control group, the other network device 2N can perform the abnormality notification in the control group C1.

In addition to the above description, the HMI function, that is, the touch panel function of the display device 4 may be used to set the configuration lists Ls1 and Ls2 to the slave devices 2A and 2E, respectively.

<Monitoring operation>
Next, referring also to FIG. 7, the monitoring operation of the network device 2N of this embodiment will be specifically described. FIG. 7 is a flowchart for explaining an operation example of the network device. In the following description, the operation of the slave device 2A as the network device 2N will be described as an example.

First, in step S1, the control unit 24 determines whether or not the abnormality detection unit 22 has detected an abnormality based on whether or not the abnormality detection unit 22 has notified the abnormality detection result. If an abnormality is detected (YES in S1), the process proceeds to step S3, otherwise (NO in S1), the process proceeds to step S2 (step S1).

In step S2, the control unit 24 determines whether or not an operation instruction for the LED 23L of the abnormality notification unit 23 has been received from another network device 2N (that is, the slave device 2E) of the control group C1. If no operation instruction has been received (NO in S2), proceed to step S6; otherwise (YES in S2), proceed to step S3 (step S2).

At step S3, the control unit 24 sets the abnormal status of the network device 2N to an abnormal state. The flow then proceeds to step S4. As for the abnormal status, for example, an abnormal state or a normal state is written and held in a predetermined setting area (not shown) of the RAM provided in the control section 24 .

At step S4, the control unit 24 sets the light emission status of the network device 2N to an abnormal pattern. As with the abnormal status, the light emission status is stored by writing an abnormal pattern or a normal pattern in the setting area. That is, the light emission status is information indicating whether or not there is an abnormality, like the abnormality status, and the light emission status of the abnormality pattern is an example of an abnormality reply (signal).

Subsequently, in step S5, the control unit 24 lights (operates) the LED 23L of the abnormality notification unit 23 in an abnormal pattern. The flow then proceeds to step S6.

In step S6, the control unit 24 determines whether or not the configuration list Ls1 is stored in the storage unit 25. If the configuration list Ls1 is not stored (NO in S6), the control unit 24 determines that the slave device 2 to be monitored is not set and terminates the processing of the monitoring operation. YES), go to step S7 (step S6).

Note that the other slave devices 2 not selected as the network device 2N in the control group C1 also execute the processing procedure shown in steps S1 to S6 in the same manner, but the monitoring operation processing ends next. (NO in S6).

In step S7, the control unit 24 reads, via the communication unit 21, the abnormal status and the light emission status of the LED (the second light emitting element) from the other slave devices 2 registered in the configuration list Ls1. That is, the control unit 24 of the network device 2N inquires about the presence or absence of an abnormality to the other slave devices 2 (including the other network device 2N (that is, the slave device 2E)) of the control group C1.

Subsequently, in step S8, the control unit 24 determines whether or not the abnormality status and the light emission status of the LED could be read from the other slave device 2. That is, the control unit 24 of the network device 2N determines whether or not there is a reply to the inquiry from another slave device 2 of the control group C1. If the abnormality status and light emission status can be read from all other slave devices 2 registered in the configuration list Ls1 (YES at S8), proceed to step S9; otherwise (NO at S8), proceed to step S11. (Step S8).

In step S9, the control unit 24 determines whether or not there is a reply from another slave device 2 indicating that the abnormal status is abnormal. Furthermore, the control unit 24 also reads out the abnormal status of its own machine set in the setting area of the RAM, and determines whether or not the abnormal status of its own machine is in an abnormal state. If the abnormal statuses of all the other slave devices 2 registered in the configuration list Ls1 and of the device itself are not abnormal (NO in S9), proceed to step S10; otherwise (YES in S9), proceed to step S11. (Step S9).

In step S10, the control unit 24 determines whether or not there is a reply from another slave device 2 that the light emission status of the LED is an abnormal pattern. Furthermore, the control unit 24 also reads out the light emission status of the device itself, which is set in the setting area of the RAM, and determines whether or not the light emission status of the device itself indicates an abnormal pattern. If the light emission statuses of all the other slave devices 2 registered in the configuration list Ls1 and of the self device are not abnormal patterns (NO in S10), all the slave devices 2 in the control group C1 (the self device and other devices to be monitored) ), the process of the monitoring operation is terminated, and in other cases (YES in S10), the process proceeds to step S11 (step S10).

By performing the processing operations of steps S7 to S10 described above, the control unit 24 determines whether or not there is an abnormality in the slave device 2 that made the inquiry. That is, if NO is determined in step S10, the control unit 24 determines that there is no abnormality in the slave device 2 to be inquired, and if NO is determined in step S8, YES is determined in step S9. If yes, or if YES is determined in step S10, it is determined that an abnormality has occurred in the slave device 2 to which the inquiry is made (an abnormality in the slave device 2 is detected).

In the above description, the case where the abnormality is detected by reading the abnormality status and the light emission status in step S8 has been described. There is no particular limitation as long as at least one of them is read out to detect an abnormality.

In step S11, the control unit 24 transmits, via the communication unit 21, an instruction to execute an anomaly notification to other slave devices 2 in the control group C1 other than the slave device 2 that has detected an anomaly. That is, the control unit 24 transmits to the other slave device 2 an operation instruction to light (operate) the LED (the second light emitting element) in an abnormal pattern.

As described above, in the network device 2N and the network system 100 of the present embodiment, when an abnormality occurs in any of the slave devices 2 registered in the configuration list Ls1, all the slave devices included in the configuration list Ls1 In the device 2, the lighting operation is performed in an abnormal pattern. As a result, in the network device 2N and the network system 100 of the present embodiment, even when an abnormality occurs in the slave device 2, it is possible to easily identify the influence range of the slave device 2 in which the abnormality has occurred. Further, in the network device 2N and the network system 100 of the present embodiment, by storing the configuration list Ls1 of the control group C1 in the storage unit 25 of the network device 2N, the program change in the master device 1 and the display device 4 can be changed. It is possible to easily identify the aforementioned influence range (the control group C1) without changing the display content.

Further, for example, in the case of the conventional example above, in which only the slave device in which an abnormality occurs in a factory where a large number of slave devices are used reports an abnormality, the administrator (user) can determine whether the slave device or the slave device It was difficult to find the process to which it belongs. On the other hand, in the present embodiment, it is possible to easily identify the influence range of the slave device 2 in which an abnormality has occurred. and the process to which the slave device 2 belongs can be quickly notified, and the processing for the abnormality can be quickly performed, thereby preventing the productivity of the factory from being lowered.

In addition, in the present embodiment, the network device 2N (slave device 2) monitors the occurrence of an abnormality within the control group. processing can be distributed. Furthermore, in this embodiment, the processing load on the master device 1 does not increase, and there is no need to improve the performance or increase the cost of the master device 1 .

[Embodiment 2]
Other embodiments of the invention are described below. For convenience of description, members having the same functions as those of the members described in the above embodiments are denoted by the same reference numerals, and description thereof will not be repeated.

The main difference between this embodiment and the above-described embodiment is that the control unit 24 controls the LED (the LED of the abnormality notification unit 23) when the abnormality detection unit 22 detects an abnormality and when it does not detect an abnormality. 1 light emitting element) 23L are different from each other in at least one of the light emitting state, the light emitting color, and the light emitting period.

In the network device 2N of the present embodiment, for example, the LED 23L of the abnormality notification unit 23 emits light of two different colors, green light and red light, for example. In addition, the LED 23L flashes in green in accordance with the first abnormality notification instruction from the control unit 24. FIG. In addition, the LED 23L blinks in red according to the second abnormality notification instruction from the control unit 24, which is different from the first abnormality notification. In addition, when there is no abnormality in any of the slave devices 2 in the control group C1, the light emitting state of the LED 23L is, for example, turned off.

For the slave devices 2 other than the slave devices 2 that responded that there was an abnormality when the above inquiry was made, the control unit 24 confirms through the communication unit 21 that there is an abnormality in the slave devices 2 other than the slave devices 2 concerned. , and transmits an instruction to the effect that the first abnormality notification should be executed. As a result, in the designated slave device 2, the LED (second light-emitting element) of the anomaly notification section blinks in green.

Next, referring also to FIG. 8, the operation of the network device 2N of this embodiment will be specifically described. FIG. 8 is a flowchart illustrating an operation example of a network device according to Embodiment 2 of the present disclosure. In the following description, as in the first embodiment, the operation of the slave device 2A as the network device 2N will be described as an example.

In step S21, the control unit 24 determines whether or not the abnormality detection unit 22 has detected an abnormality based on whether or not the abnormality detection unit 22 has notified the abnormality detection result. If an abnormality is detected (YES in S21), the process proceeds to step S25; otherwise (NO in S21), the process proceeds to step S22 (step S21).

Next, in step S22, the control unit 24 receives an instruction to operate the LED 23L of the abnormality notification unit 23 (first abnormality notification instruction) from the other network device 2N (that is, the slave device 2E) of the control group C1. Determine whether or not If no operation instruction has been received (NO in S22), the process proceeds to step S28; otherwise (YES in S22), the process proceeds to step S23 (step S22).

In step S23, the control unit 24 sets the light emission status of the network device 2N to the first operating state (green blinking operating state).

In step S24, the control unit 24 instructs the abnormality notification unit 23 to perform the first abnormality notification, and the abnormality notification unit 23 operates with its LED 23L in the first operating state. That is, the LED 23L performs green flashing operation.

At step S25, the control unit 24 sets the abnormal status of the network device 2N to an abnormal state.

In step S26, the control unit 24 sets the light emission status of the network device 2N to the second operating state (red blinking operating state).

In step S27, the control unit 24 instructs the abnormality notification unit 23 to perform the second abnormality notification, and the abnormality notification unit 23 operates with its LED 23L in the second operating state. That is, the LED 23L performs a red blinking operation.

In step S28, the control unit 24 determines whether or not the configuration list Ls1 is stored in the storage unit 25. If the configuration list Ls1 is not stored (NO in S28), the control unit 24 determines that the slave device 2 to be monitored is not set and terminates the processing of the monitoring operation. YES), go to step S29 (step S28).

Note that the other slave devices 2 that are not selected as the network devices 2N in the control group C1 also execute the processing procedure shown in steps S21 to S28 in the same manner, but the monitoring operation processing is terminated next. (NO in S28). Therefore, when an abnormality occurs in the other slave device 2, the abnormality status is set to the abnormal state and the light emission status is set to the second operating state in the other slave device 2. As a result, the LED of the anomaly notification section flashes in red.

In step S29, the control unit 24 reads, via the communication unit 21, the abnormal status and the light emission status of the LED (second light emitting element) from the other slave devices 2 registered in the configuration list Ls1. That is, the control unit 24 of the network device 2N inquires about the presence or absence of an abnormality to the other slave devices 2 (including the other network device 2N (that is, the slave device 2E)) of the control group C1.

Subsequently, in step S30, the control unit 24 determines whether or not the abnormality status and the light emission status of the LED could be read from the other slave device 2. That is, the control unit 24 of the network device 2N determines whether or not there is a reply to the inquiry from another slave device 2 of the control group C1. If the abnormality status and light emission status can be read from all other slave devices 2 registered in the configuration list Ls1 (YES at S30), proceed to step S31; otherwise (NO at S30), proceed to step S33. (Step S30).

In step S31, the control unit 24 determines whether or not there is a reply from another slave device 2 indicating that the abnormal status is abnormal. Furthermore, the control unit 24 also reads out the abnormal status of its own machine set in the setting area of the RAM, and determines whether or not the abnormal status of its own machine is in an abnormal state. If the abnormal statuses of all the other slave devices 2 registered in the configuration list Ls1 and of the device itself are not abnormal (NO in S31), proceed to step S32; otherwise (YES in S31), proceed to step S33. .

In step S32, the control unit 24 determines whether or not there is a reply from another slave device 2 that the light emission status of the LED is in the second operating state. Furthermore, the control unit 24 also reads out the light emission status of its own device, which is set in the setting area of the RAM, and determines whether or not the light emission status of its own device is in the second operating state. If the light emission statuses of all other slave devices 2 registered in the configuration list Ls1 and of the device itself are not in the second operating state (NO in S32), all the slave devices 2 in the control group C1 (self device and monitoring target If it is determined that no abnormality has occurred in the other machine), the process of the monitoring operation is terminated, and in other cases (YES in S32), the process proceeds to step S33.

By performing the processing operations of steps S29 to S32 described above, the control unit 24 determines whether or not the slave device 2 that made the inquiry has an abnormality. That is, if NO is determined in step S32, the control unit 24 determines that there is no abnormality in the slave device 2 that is the inquiry destination, and if NO is determined in step S30, YES is determined in step S31. If yes, or if YES is determined in step S32, it is determined that an abnormality has occurred in the slave device 2 to which the inquiry is made (an abnormality in the slave device 2 is detected).

In step S33, the control unit 24 causes the LEDs (second light emitting elements) of the abnormality notification units of the slave devices 2 other than the slave device 2 that has detected the abnormality to operate in the first operating state. Send instructions. That is, in this other slave device 2, its LED blinks in green. As a result, in the slave device 2 that has detected the abnormality, the LED of the abnormality annunciator operates in the second operating state and flashes in red, and the other slave devices 2 in the control group C1 operate in the anomaly annunciator. LED operates in the first operating state and becomes a green blinking operating state.

As described above, in this embodiment, the same effects as in the first embodiment are obtained.

Furthermore, in the network device 2N of the present embodiment, when an abnormality occurs in any of the slave devices 2 registered in the configuration list, all the slave devices 2 in which no abnormality has occurred are made to perform the first abnormality notification. . Further, in the slave device 2 in which the abnormality has occurred, the second abnormality notification is performed by the abnormality notification section. As a result, in the network device 2N and the network system 100 of the present embodiment, as in the first embodiment, even when an abnormality occurs in the slave device 2, the influence range of the slave device 2 in which the abnormality has occurred can be easily specified. be able to. In addition, in the network device 2N and the network system 100 of the present embodiment, the first abnormality notification and the second abnormality notification are different from each other. can be discriminated.

In the above description, the case where the LED (first light emitting element) 23L capable of emitting light in two colors is used in the abnormality notification unit 23 has been described as an example, but the present embodiment is limited to this. Instead, for example, LEDs emitting the same color of light may be used, and at least one of the light emitting state and the light emitting cycle may be different from each other.

Further, in the above description, the case where the network device 2N and the slave device 2 have the same configuration has been described. may be configured. However, it is preferable that the network device 2N and the slave device 2 have the same configuration because the network device 2N can be easily selected and changed in the control group.

[Example of realization by software]
The functional blocks (especially the control unit 24) of the network device 2N may be implemented by a logic circuit (hardware) formed in an integrated circuit (IC chip) or the like, or may be implemented by software.

In the latter case, the control unit 24 is provided with a computer that executes program instructions, which are software that implements each function. This computer includes, for example, one or more processors, and a computer-readable recording medium storing the program. In the computer, the processor reads the program from the recording medium and executes it, thereby achieving the object of the present disclosure.

As the processor, for example, a CPU (Central Processing Unit) can be used. As the recording medium, a "non-temporary tangible medium" such as a ROM (Read Only Memory), a tape, a disk, a card, a semiconductor memory, a programmable logic circuit, etc. can be used. In addition, a RAM (Random Access Memory) or the like for developing the above program may be further provided.

Also, the program may be supplied to the computer via any transmission medium (communication network, broadcast waves, etc.) capable of transmitting the program. Note that one aspect of the present invention can also be implemented in the form of a data signal embedded in a carrier wave in which the program is embodied by electronic transmission.

〔summary〕
A network device according to one aspect of the present disclosure is a network device, which is the slave device used in a network system in which a master device and a plurality of slave devices controlled by the master device are connected, wherein the other slave devices A group including a communication unit that transmits and receives data to and from a device, an anomaly detection unit that detects anomalies, an anomaly reporting unit that reports an anomaly, the network device, and at least one other slave device. and a control unit for controlling each unit of the network device, wherein the control unit communicates with the other slave devices registered in the configuration list through the communication unit If there is a reply from another slave device that there is an abnormality, or if the abnormality detection unit detects an abnormality, the abnormality notification unit is caused to perform abnormality notification. In addition, a configuration is provided for transmitting, through the communication unit, an instruction to execute anomaly notification to the other slave devices registered in the configuration list.

According to the above configuration, it is possible to construct a network device that can easily identify the affected range of a slave device that has caused an abnormality even when an abnormality occurs in the slave device.

In the network device according to the above aspect, if there is another slave device that does not reply to the inquiry, the control unit causes the abnormality notification unit to perform abnormality notification, A configuration may be provided in which an instruction to execute an anomaly notification is transmitted to the other registered slave devices.

According to the above configuration, even if communication with another slave device registered in the configuration list cannot be performed, it is determined that an abnormality has occurred in the other slave device, and the slave device in which the abnormality has occurred The area of influence of the device can be easily identified.

In the network device according to the above aspect, the anomaly notification unit may have a first light emitting element, and the anomaly notification may be performed by lighting the first light emitting element.

According to the above configuration, it is possible to visually recognize the range of influence of the slave device in which an abnormality has occurred, and to more easily identify the range of influence.

In the network device according to the above aspect, the control unit, of the other slave devices registered in the configuration list, to the slave devices other than those that have responded that there is an abnormality, as the instruction, A configuration may be provided for transmitting an instruction to execute a first anomaly notification indicating that an anomaly has occurred in the slave device other than the slave device.

According to the above configuration, the slave device in which no abnormality has occurred executes an abnormality notification different from that of the slave device in which an abnormality has occurred, and the other slave devices registered in the configuration list notify the slave device in which an abnormality has occurred. can be determined more easily.

In the network device according to the above aspect, the other slave device has a second light-emitting element, and receives an instruction to execute the first anomaly notification; may be provided so that at least one of the light emitting state, the light emitting color, and the light emitting period of the second light emitting element is made different from the case of not receiving the .

According to the above configuration, in the other slave device registered in the configuration list, based on at least one of the light emitting state, the light emitting color, and the light emitting period of the second light emitting element, the abnormality in the other slave device is detected. can be easily determined whether or not

In the network device according to the above aspect, the control unit controls the light emission state, light emission color, and at least one of the light emission periods may be different from each other.

According to the above configuration, in the network device, it is possible to easily determine whether or not the network device has an abnormality based on at least one of the light emitting state, the light emitting color, and the light emitting period of the first light emitting element. be able to.

Further, a network system according to one aspect of the present disclosure is a network system in which a master device and a plurality of slave devices controlled by the master device are connected, wherein any one of the above network devices serves as the slave device. At least one connected configuration.

According to the above configuration, it is possible to construct a network system in which even when an abnormality occurs in a slave device, it is possible to easily identify the affected range of the slave device in which the abnormality has occurred.

The present disclosure is not limited to the above-described embodiments, and various modifications are possible within the scope of the claims, and embodiments obtained by appropriately combining technical means disclosed in different embodiments is also included in the technical scope of the present disclosure.

1 master device 2 slave device 2N network device 21 communication unit 22 abnormality detection unit 23 abnormality notification unit 23L LED (light emitting element)
24 control unit 25 storage unit 100 network system

Claims

A network device that is a slave device used in a network system in which a master device and a plurality of slave devices controlled by the master device are connected,
a communication unit that transmits and receives data to and from other slave devices;
an anomaly detection unit that detects an anomaly;
an anomaly reporting unit that performs anomaly reporting;
a storage unit for pre-storing a group configuration list including the network device and at least one other slave device;
a control unit that controls each unit of the network device,
The control unit
Inquiring about the presence or absence of an abnormality to the other slave devices registered in the configuration list through the communication unit, and receiving a reply that there is an abnormality from the other slave devices, or
When the anomaly detection unit detects an anomaly, the anomaly notification unit is caused to perform an anomaly notification, and the anomaly notification is performed to the other slave devices registered in the configuration list through the communication unit. A network device that sends an instruction to do something.
The control unit
When there is another slave device that does not reply to the inquiry, the abnormality notification unit is caused to perform abnormality notification, and the abnormality notification is sent to the other slave devices registered in the configuration list through the communication unit. 2. The network device of claim 1, transmitting an instruction to perform a.
The network device according to claim 1 or 2, wherein the anomaly notification unit has a first light emitting element, and the anomaly notification is performed by lighting the first light emitting element.
The control unit
Of the other slave devices registered in the configuration list,
For the slave devices other than those that have responded that there is an abnormality, the instruction is to indicate that an abnormality has occurred in the slave devices other than the slave device, that is, to execute the first abnormality notification. 4. A network device as claimed in any one of claims 1 to 3, adapted to send an indication.
The other slave device has a second light emitting element,
When receiving the instruction to execute the first abnormality notification and when not receiving the first abnormality notification, at least the light emitting state, the light emitting color, and the light emitting period of the second light emitting element 5. A network device according to claim 4, operable to make any of them different from each other.
The control unit
At least one of the light emission state, light emission color, and light emission period of the first light emitting element is made different between when the abnormality detection unit detects an abnormality and when it does not detect an abnormality. 6. The network device according to any one of 3 to 5.
A network system in which a master device and a plurality of slave devices controlled by the master device are connected,
A network system to which at least one network device according to any one of claims 1 to 6 is connected as said slave device.