JP7561674B2 - COMMUNICATION SYSTEM, SETTING DEVICE, SETTING METHOD, AND SETTING PROGRAM - Google Patents

Description

This disclosure relates to a communication system having multiple parent devices and multiple child devices that perform power line communication (PLC), a setting device, a setting method, and a setting program.

Conventionally, communication systems have been known in which a parent unit and a child unit transmit and receive data via power line carrier communication. For example, a centralized automatic meter reading system has become widespread in which a parent unit with power line carrier communication capability collects meter reading data indicating the amount of power usage measured by a watt-hour meter connected to a child unit with power line carrier communication capability from the child unit, and provides the collected meter reading data to a meter reader via a server.

Power line communication is a communication method that uses high frequencies by superimposing high frequency signals onto existing power lines. Therefore, with power line communication, communication across transformers is not possible, and the communication range is limited to within the same system. In addition, because power line communication uses existing power lines, the parent unit registers the child units that are allowed to communicate in order to prevent spoofing and eavesdropping.

The registration of a slave unit to a parent unit is performed, for example, when a communication system is introduced to a facility. When introducing a communication system to a facility, if a slave unit needs to be installed in each of multiple systems, the facility manager must register slave units of the same system to each parent unit, but there is a possibility that the parent unit may be mistakenly registered to a slave unit of a different system. For this reason, the facility manager must check whether communication is possible between the parent unit and the slave units registered to that parent unit for all combinations of parent units and slave units.

Therefore, in order to make it possible to visually check whether communication between the parent unit and the child unit is possible, Patent Document 1 proposes a technology that displays a screen on the display unit that shows the connection status between the parent unit and the child unit on a map.

JP 2019-180066 A

However, while the technology described in Patent Document 1 above can grasp the connection status between the parent unit and the child unit, if an incorrect child unit is registered to the parent unit, the registration details of the child unit on the parent unit must be corrected by checking the electrical system diagram of the installation location of the parent unit and the child unit against the registration details of the parent unit.

The contents of the parent unit are registered by, for example, checking the information obtained by accessing the parent unit using software that manages the parent unit's operations, and since an electrical system diagram must also be prepared in advance, correcting the contents of the child units registered in the parent unit takes time.

The present disclosure has been made in consideration of the above, and aims to provide a communication system that performs power line communication and that allows the parent unit to easily modify the registration details of the child unit.

In order to solve the above-mentioned problems and achieve the object, the communication system of the present disclosure includes a display control unit and a registration relationship change unit. The display control unit causes the display unit to display a display screen including information indicating the registration relationships of the multiple slave units with respect to multiple master units that each perform power line carrier communication with a registered slave unit among the multiple slave units, and an electrical system diagram of the installation location of the multiple master units and the multiple slave units, in a manner that allows the registration relationship to be changed. When the registration relationship is changed by an operation on the display screen, the registration relationship change unit performs processing to cause the master unit that is the target of the change in registration relationship to change the slave unit that is the target of communication.

The present disclosure has the advantage that it is easy to modify the registration details of a child device in a parent device in a communication system that uses power line carrier communication.

FIG. 1 is a diagram showing an example of an overall configuration of a PLC meter reading system according to a first embodiment. FIG. 13 is a diagram showing an example of generation of a screen for correcting registered contents of a PLC slave unit in a PLC master unit in the communication system according to the first embodiment; FIG. 13 is a diagram showing an example of a process for correcting registered contents of a PLC slave unit in a PLC master unit in the communication system according to the first embodiment; FIG. 1 is a diagram showing an example of a configuration of a PLC master unit according to a first embodiment; FIG. 1 is a diagram showing an example of a configuration of a PLC slave unit according to a first embodiment; FIG. 1 is a diagram illustrating an example of a configuration of a server according to a first embodiment. FIG. 1 is a diagram illustrating an example of a registration relationship list stored in a storage unit of a server according to a first embodiment; FIG. 1 is a diagram illustrating an example of a configuration of a terminal device according to a first embodiment; FIG. 1 is a diagram showing an example of a display screen displayed on a display unit of a terminal device according to a first embodiment; FIG. 1 is a diagram showing an example of a display screen in which an electrical system diagram is displayed as a background image in a drawing area according to the first embodiment; FIG. 13 is a diagram showing an example of a display screen in which registration relationship information is superimposed on an electrical system diagram in a drawing area according to the first embodiment; 1 is a flowchart showing an example of a process performed by a terminal device according to a first embodiment; 1 is a flowchart showing an example of a process performed by a server according to the first embodiment; A flowchart showing an example of a connection process by a PLC master unit according to the first embodiment. A flowchart showing an example of a connection update process by the PLC master according to the first embodiment. 1 is a flowchart showing an example of a connection process performed by a PLC slave unit according to a first embodiment. A flowchart showing a connection status determination process by a server according to the first embodiment. 11 is a flowchart showing another example of the process performed by the terminal device according to the first embodiment. A flowchart showing an example of a registration content correction operation by a user of the terminal device according to the first embodiment. FIG. 13 is a diagram showing another example of a display screen in which registration relationship information is superimposed on an electrical system diagram in a drawing area according to the first embodiment; FIG. 13 is a diagram showing an example of a pop-up screen including communication history information and communication statistics information according to the first embodiment; FIG. 13 is a diagram illustrating an example of a configuration of a server of a PLC meter reading system according to a second embodiment. FIG. 13 is a diagram showing an example of a device list according to the second embodiment; A flowchart showing an example of a process for automatically creating a registration relationship list by a server according to a second embodiment. 11 is a flowchart showing an example of a first communication state determination process performed by a server according to a second embodiment. 11 is a flowchart showing an example of a second communication state determination process by a server according to a second embodiment. FIG. 1 is a diagram showing a configuration example of a processing circuit in the case where the processing circuit included in each of the processing units according to the first and second embodiments is realized by a processor and a memory; FIG. 13 is a diagram showing an example of a processing circuit in a processing unit according to the first and second embodiments, in which the processing circuit is configured with dedicated hardware;

The following describes in detail the communication system, setting device, setting method, and setting program according to the embodiments with reference to the drawings.

Embodiment 1.
Fig. 1 is a diagram showing an example of the overall configuration of a PLC meter reading system according to a first embodiment. The PLC meter reading system 100 shown in Fig. 1 includes a plurality of electricity meters 1, a plurality of PLC slave units 2, a plurality of PLC master units 3, a plurality of servers 4, and a terminal device 5, and collects the amount of electricity used by a plurality of facilities 9. The PLC meter reading system 100 is an example of a communication system. The terminal device 5 is an example of a setting device. The PLC slave unit 2 is an example of a slave unit that performs power line carrier communication, and the PLC master unit 3 is an example of a master unit that performs power line carrier communication.

Each facility 9 is equipped with multiple electricity meters 1, multiple PLC slave units 2, multiple PLC master units 3, and a server 4. The facility 9 is, for example, a building, a factory, or a plant. Each electricity meter 1 is connected to one of the multiple PLC slave units 2, and the multiple PLC slave units 2 are connected to a power line 6, and data can be transmitted and received via the power line 6 by power line carrier communication with a PLC master unit 3 connected to the same power line 6. The power line 6 of the same system is a power line 6 that does not cross a transformer.

Meter reading data, which is data on the amount of electricity used measured by each electricity meter 1, is output from each electricity meter 1 to the PLC slave unit 2. The PLC slave unit 2 is connected to a power line 6, and transmits the meter reading data via the power line 6 to the PLC master unit 3 that is connected to the power line 6 of the same system.

The PLC master unit 3 has pre-registered slave units that are permitted to communicate in order to prevent spoofing or eavesdropping. The PLC master unit 3 communicates with pre-registered PLC slave units 2 among the PLC slave units 2 connected to the power line 6 of the same system via the power line 6, and receives meter reading data from the PLC slave units 2.

The server 4 collects meter reading data transmitted via the network 7 from each PLC master unit 3 installed in the same facility 9, processes the collected meter reading data, and stores the results of the data processing. The server 4 also obtains information on the PLC slave units 2 registered in the PLC master unit 3 via the network 7.

The terminal device 5 is a PC (Personal Computer) or a tablet, and is used by a user U of the PLC meter reading system 100. The user U is, for example, a meter reader, a manager of the facility 9, or a manager of the PLC meter reading system 100.

The terminal device 5 is communicatively connected to each server 4 via the network 8, acquires data from each server 4, and displays the acquired data on a display unit (not shown). This allows the user U of the terminal device 5 to easily understand the results of the meter reading data collection by the server 4.

The PLC meter reading system 100 is also configured to facilitate the correction of the registered contents of the PLC slave unit 2 in the PLC master unit 3. FIG. 2 is a diagram showing an example of the generation of a screen for correcting the registered contents of the PLC slave unit in the PLC master unit in the communication system according to the first embodiment, and FIG. 3 is a diagram showing an example of the process for correcting the registered contents of the PLC slave unit in the PLC master unit in the communication system according to the first embodiment.

As shown in FIG. 2, the server 4 collects a list of registered slave units from each PLC master unit 3 via the network 7 (step S1). The list of registered slave units includes, for example, the IDs (IDentifiers) of the PLC slave units 2 registered in the PLC master unit 3.

The server 4 transmits a registration relationship list including a list of multiple registered slave units collected from multiple PLC master units 3 to the terminal device 5 via the network 8 (step S2). Based on the registration relationship list acquired from the server 4, the terminal device 5 causes a display screen 50 including registration relationship information 91 indicating the registration relationship between the PLC master unit 3 and the PLC slave unit 2 and an electrical system diagram 92 of the facility 9 to be displayed in a changeable manner on a display unit (not shown) (step S3).

In the registration relationship information 91 shown in FIG. 2, a master icon 93 indicating the PLC master 3 and a slave icon 94 indicating the PLC slave 2 are shown, and the slave icon 94 of the PLC slave 2 registered in the PLC master 3 is connected by a connection line 95 to the master icon 93 of the PLC master 3 to which it is registered. In addition, in the electrical system diagram 92, figures 96 of PLC slaves 2 in the same system are connected by a connection line 97.

A user U of the terminal device 5 can easily determine whether there is an error in the registration relationship between the PLC master unit 3 and the PLC slave unit 2 by comparing the registration relationship information 91 on the display screen 50 with the electrical system diagram 92.

In addition, on the display screen 50, the registration relationship information 91 is displayed so as to be changeable by a GUI (Graphical User Interface) or the like, and the user U can change the registration relationship information 91 by operating an input unit (not shown). If there is an error in the registration relationship between the PLC master unit 3 and the PLC slave unit 2, the user U changes the registration relationship information 91 by operating an input unit (not shown).

3, when the registration relationship information 91 is changed, the terminal device 5 transmits a changed registration relationship list corresponding to the changed registration relationship information 91 to the server 4 (step S4). The server 4 updates the registered slave unit list based on the changed registration relationship information 91, and transmits the updated registered slave unit list to the PLC master unit 3 (step S5). In this way, in the PLC meter reading system 100, when the registration relationship information 91 is changed by an operation on the display screen 50, the PLC master unit 3 for which the registration relationship information 91 is to be changed can change the PLC slave unit 2 with which it communicates.

In this way, in the PLC meter reading system 100, the user U of the terminal device 5 can easily remotely modify the registration details of the PLC slave unit 2 in the PLC master unit 3 by changing the registration relationship information 91 while referring to the electrical system diagram 92.

The PLC meter reading system 100 will be described in more detail below. FIG. 4 is a diagram showing an example of the configuration of the PLC master unit according to the first embodiment. As shown in FIG. 4, the PLC master unit 3 includes a communication unit 10, a storage unit 11, and a control unit 12.

The communication unit 10 includes a first communication unit 101 that performs power line carrier communication with the PLC slave unit 2, and a second communication unit 102 that performs communication with the server 4. The first communication unit 101 has a function of converting various commands generated by the control unit 12 into data in a communication format that allows power line carrier communication, transmitting the converted data to the power line 6, and converting data received from the power line 6 into a data format that can be interpreted by the control unit 12.

The second communication unit 102 is connected to the network 7 via, for example, a LAN (Local Area Network) cable, and transmits and receives data to and from the server 4. The network 7 is, for example, a LAN, but is not limited to a LAN.

The memory unit 11 stores communication path information 111, a master unit ID 112, a registered slave unit list 113, and meter reading data 114. The communication path information 111 includes the slave unit ID of the PLC slave unit 2 that communicated with the PLC master unit 3, and communication information when the PLC slave unit 2 communicated.

The master ID 112 is a unique identifier that can uniquely identify the PLC master 3, and is used as an identifier to distinguish it from other PLC masters 3. The registered slave list 113 includes the slave IDs of the PLC slaves 2 that are permitted to connect to the PLC master 3. The slave ID is a unique identifier that can uniquely identify each PLC slave 2.

The PLC master 3 establishes communication with a PLC slave 2 whose slave ID is included in the registered slave list 113, but does not establish communication with a PLC slave 2 whose slave ID is not included in the registered slave list 113. The meter reading data 114 is data on the amount of electricity used collected from the electricity meter 1 via the PLC slave 2 connected to the power line 6 of the same system.

The control unit 12 includes a data collection unit 121, a slave registration management unit 122, and a communication path management unit 123. The data collection unit 121 collects data such as meter reading data 114 from the registered PLC slave units 2 via the power lines 6. The data collection unit 121 periodically collects data. For example, the data collection unit 121 performs power line carrier communication with the PLC slave units 2 via the communication unit 10 every 30 minutes to collect the meter reading data 114 of the electricity meter 1.

The slave registration management unit 122 permits connection to a PLC slave 2 having a slave ID included in the registered slave list 113, and denies connection to a PLC slave 2 having a slave ID not included in the registered slave list 113.

The communication path management unit 123 grasps the connection state with the PLC slave unit 2 whose slave unit ID is registered in the registered slave unit list 113 based on the communication path information 111 stored in the memory unit 11, and performs processing as necessary. For example, for a PLC slave unit 2 whose slave unit ID is registered in the registered slave unit list 113 and communication has failed, the communication path management unit 123 attempts to connect via another PLC slave unit 2 in the registered slave unit list 113. In the following, such another PLC slave unit 2 may be referred to as a transit terminal.

The relay terminal selected by the communication path management unit 123 controls the path based on the communication situation, such as selecting a PLC slave unit 2 with good communication conditions from among the PLC slave units 2 within communication range of the PLC slave unit 2 for which power line carrier communication has failed, or a PLC slave unit 2 with the fewest number of relays to the PLC parent unit 3.

The communication path from the PLC slave unit 2 to the PLC master unit 3 includes a multi-hop communication path in power line communication, and when data does not reach the PLC master unit 3 directly from the PLC slave unit 2, the PLC slave unit 2 automatically determines that the data should be relayed by another PLC slave unit 2 in the same system as a relay unit. If the data does not reach the PLC master unit 3 in one relay, a multi-hop operation in which the data is relayed multiple times establishes a communication path from the PLC slave unit 2 to the PLC master unit 3.

There is no need for the PLC master unit 3 to instruct the PLC slave unit 2 to perform relay operation. When the PLC slave unit 2 receives data from another PLC slave unit 2, it can determine the next PLC slave unit 2 to which it can transfer data and automatically transfer the data to that PLC slave unit 2.

Next, the PLC slave unit 2 will be described. FIG. 5 is a diagram showing an example of the configuration of the PLC slave unit according to the first embodiment. As shown in FIG. 5, the PLC slave unit 2 includes a communication unit 20, a storage unit 21, and a control unit 22.

The communication unit 20 includes a first communication unit 201 that communicates with the PLC master unit 3, and a second communication unit 202 that communicates with the watthour meter 1. The first communication unit 201 has a function of converting various commands generated by the control unit 22 into data in a communication format that allows power line communication, transmitting the converted data to the power line 6, and converting data received from the power line 6 into a data format that can be interpreted by the control unit 22. The second communication unit 202 communicates with the watthour meter 1, for example, by serial communication.

The storage unit 21 stores a slave ID 211 and communication path information 212. The slave ID 211 is a unique identifier that can uniquely identify each PLC slave 2. The communication path information 212 includes the device ID of the communication path from the PLC slave 2 to the PLC master 3. For example, if direct communication from the PLC slave 2 to the PLC master 3 is possible, the communication path information 212 includes the master ID of the PLC master 3 as the next communication destination. If direct communication to the PLC master 3 is not possible, the communication path information 212 includes the slave ID of the PLC slave 2 with which the source PLC slave 2 can directly communicate as the next communication destination.

The control unit 22 includes a data collection unit 221, a registration management unit 222, and a communication path management unit 223. The data collection unit 221 acquires data such as meter readings from the electricity meter 1 via the second communication unit 202 at regular intervals or when a command is received from the PLC parent unit 3. The electricity meter 1 measures the amount of electricity used, which is the amount of electricity used, and outputs current or past integrated measurement values in response to a request from the PLC child unit 2. The registration management unit 222 controls the connection process with the PLC parent unit 3.

The communication path management unit 223 controls the path to reach the PLC master unit 3. For example, the communication path management unit 223 transmits data acquired from the electricity meter 1 to the PLC master unit 3 or the PLC slave unit 2 based on the communication path information 212.

Next, the server 4 will be described. FIG. 6 is a diagram showing an example of the configuration of the server according to the first embodiment. As shown in FIG. 6, the server 4 includes a communication unit 30, a storage unit 31, and a control unit 32.

The communication unit 30 includes a first communication unit 301 that communicates with the PLC master unit 3, and a second communication unit 302 that communicates with the terminal device 5. The first communication unit 301 is connected to the network 7 via, for example, a LAN cable, and transmits and receives data to and from the PLC master unit 3. The second communication unit 302 is connected to the network 8 via, for example, a LAN cable, and transmits and receives data to and from the terminal device 5. The network 8 includes, for example, a WAN (Wide Area Network) such as the Internet, and a LAN.

The memory unit 31 stores a registration relationship list 311, communication path information 312, meter reading data 313, a master ID list 314, and a slave ID list 315. The registration relationship list 311 includes the master IDs of the PLC masters 3 present in the PLC meter reading system 100 and the slave IDs of the PLC slaves 2 connected to the same power line 6 as each PLC master 3.

Figure 7 is a diagram showing an example of a registration relationship list stored in the memory unit of the server according to the first embodiment. As shown in Figure 7, in the registration relationship list 311, the master ID of each PLC master 3 is linked to the slave ID of each PLC slave 2 connected to the same system as the PLC master 3.

The communication path information 312 shown in FIG. 6 includes the communication path information 111 stored in each PLC master unit 3. The meter reading data 313 includes the meter reading data 114 collected from each PLC master unit 3. The master unit ID list 314 includes the master unit IDs of all PLC master units 3 connected to the server 4, and these master unit IDs are used as destination information for the PLC master units 3 that communicate with the server 4. The master unit IDs included in the master unit ID list 314 are the same as the master unit IDs included in the registration relationship list 311.

The slave ID list 315 includes the slave IDs of all PLC slaves 2 that collect meter reading data 114 in the server 4. The slave IDs included in the slave ID list 315 are the same as the slave IDs included in the registration relationship list 311.

The control unit 32 includes a data collection unit 321, a communication path registration unit 322, a list management unit 323, and a display processing unit 324. The data collection unit 321 periodically acquires meter reading data 114 from a PLC master unit 3 whose master unit ID is included in the master unit ID list 314, and adds the data to the meter reading data 313 in the memory unit 31.

The communication path registration unit 322 periodically acquires the communication path information 111 stored in the PLC master unit 3, stores the acquired communication path information 111 in the memory unit 31, and stores the acquired communication path information 111 in the memory unit 31 for a certain period of time. For example, the communication path registration unit 322 acquires the communication path information 111 from the PLC master unit 3 every 30 minutes, and stores about 30 days' worth of communication path information 111 in the memory unit 31.

The list management unit 323 manages the registration relationship list 311. For example, the list management unit 323 acquires from the communication unit 30 the registration relationship list 311 transmitted from the terminal device 5 and received by the communication unit 30, and compares the acquired registration relationship list 311 with the registration relationship list 311 stored in the memory unit 31. If there is a difference in the comparison result, the list management unit 323 updates the registration relationship list 311 stored in the memory unit 31 with the registration relationship list 311 transmitted from the terminal device 5, and transmits the registered child unit list 113 included in the updated registration relationship list 311 to the PLC master unit 3 via the communication unit 30. The registered child unit list 113 may be created by the list management unit 323 based on the registration relationship list 311.

The display processing unit 324 generates drawing data, which is data for screen drawing, based on the registration relationship list 311 and communication path information 312 stored in the storage unit 31, and transmits the generated drawing data to the terminal device 5 via the second communication unit 302. Furthermore, when the display processing unit 324 determines that the drawing data needs to be changed based on the communication path information 312, it automatically transmits the changed drawing data to the terminal device 5 via the second communication unit 302.

Next, the terminal device 5 will be described. FIG. 8 is a diagram showing an example of the configuration of the terminal device according to the first embodiment. The terminal device 5 includes a communication unit 40, a display unit 41, an input unit 42, a file input unit 44, and a processing unit 47. The processing unit 47 includes an input processing unit 43, a display control unit 45, and a registration relationship change unit 46.

The communication unit 40 is connected to the network 8 and transmits and receives information to and from the server 4 via the network 8. The communication unit 40 is connected to the network 8, for example, by a wired LAN cable or wireless LAN communication.

The display unit 41 is, for example, an LCD (Liquid Crystal Display) or an organic EL (Electro-Luminescence) display. The display unit 41 displays the screen according to the control of the display control unit 45.

The input unit 42 is a user interface that is operated by the user U to operate the screen displayed on the display unit 41. The input unit 42 includes, for example, a keyboard, a mouse, a keypad, or a touch panel.

When the user U operates the screen displayed on the display unit 41 by the input unit 42, the input processing unit 43 creates a data format that can be processed by the display control unit 45 based on the information of the operation, and outputs the created data to the display control unit 45.

The file input unit 44 imports an electrical system diagram 92, such as a single-line diagram or a main line diagram, as electronic data. The data of the electrical system diagram 92 is image data in, for example, a PDF (Portable Document Format) format or a PNG (Portable Network Graphics) format.

The display control unit 45 causes the display unit 41 to display a screen corresponding to the drawing data acquired from the server 4 via the communication unit 40. The display control unit 45 also changes the data imported by the file input unit 44 to a data format and image size that can be displayed on the display unit 41, and displays an image corresponding to the changed data on the display unit 41.

The display control unit 45 also changes the screen information according to the data output from the input processing unit 43, and causes the display unit 41 to display a screen according to the changed screen information. Furthermore, the display control unit 45 transmits the screen information changed according to the data output from the input processing unit 43 to the server 4 via the communication unit 40.

When the registration relationship between the PLC parent unit 3 and the PLC child unit 2 is changed by an operation on the display screen 50, the registration relationship change unit 46 transmits the changed registration relationship list to the server 4, and causes the PLC parent unit 3 that is the subject of the change in the registration relationship to change the PLC child unit 2 that is the subject of communication.

Next, the initial registration process, connection-related process, and registration correction support process in the PLC meter reading system 100 will be described in detail. The initial registration process includes a process that supports various settings required for registration when the user U starts up the PLC meter reading system 100. The connection-related process includes a process of connecting the PLC master unit 3 and the PLC slave unit 2 based on registration by the initial registration process, and obtaining communication path information 111 from the PLC master unit 3 by the server 4. The registration correction support process includes a process of checking the connection status between the PLC master unit 3 and the PLC slave unit 2 by the server 4, and a process of supporting the user U in correcting the registration relationship between the PLC master unit 3 and the PLC slave unit 2.

First, the initial registration process will be described. FIG. 9 is a diagram showing an example of a display screen displayed on the display unit of the terminal device according to the first embodiment. The display screen 50 shown in FIG. 9 includes a background drawing selection area 51, a registration relationship list selection area 52, a drawing area 53, a device management area 54, and a print button 55.

The background drawing selection area 51 includes a file selection button 51a. The file selection button 51a is a button for selecting data for the electrical system diagram 92. When the user U presses the file selection button 51a by operating the input unit 42, the display control unit 45 causes the display unit 41 to display files in a folder accessible from the terminal device 5 in a selectable manner. By operating the input unit 42, the user U selects, for example, a main line system diagram as the electrical system diagram 92 for the facility 9 in which the PLC meter reading system 100 is to be installed.

When a file is selected by user U operating input unit 42, file input unit 44 acquires data of electrical system diagram 92 from the folder and outputs the acquired data of electrical system diagram 92 to display control unit 45. Based on the data of electrical system diagram 92 acquired from file input unit 44, display control unit 45 displays electrical system diagram 92 as a background image in drawing area 53 of display unit 41.

Fig. 10 is a diagram showing an example of a display screen in which an electrical system diagram is displayed as a background image in the drawing area according to the first embodiment. As shown in Fig. 10, an electrical system diagram 92 is displayed as a background image in the drawing area 53. In the electrical system diagram 92 shown in Fig. 10, figures 96 of PLC slave units 2 in the same system are connected by connection lines 97. User U can also trim and display a portion of the data of the electrical system diagram 92 that he or she wishes to display on the display screen 50. Such trimming is performed, for example, by the file input unit 44 based on an operation of the input unit 42 by user U.

The registration relationship list selection area 52 includes a file selection button 52a and an acquisition button 52b. The file selection button 52a is a button for selecting the registration relationship list 311. When the user U presses the file selection button 52a by operating the input unit 42, the display control unit 45 causes the display unit 41 to display selectable files in folders accessible from the terminal device 5.

When a file is selected by the user U operating the input unit 42, the display control unit 45 acquires the registration relationship list 311 via a recording medium (not shown) on which the registration relationship list 311 is recorded or the communication unit 40. Based on the acquired registration relationship list 311, the display control unit 45 superimposes and displays registration relationship information 91 indicating the registration relationship between the PLC master unit 3 and the PLC slave unit 2 on the electrical system diagram 92 in the drawing area 53 of the display unit 41 in a state that can be operated by the user U.

The obtain button 52b is a button for obtaining the registration relationship list 311 from the server 4. If the registration relationship list 311 is already stored in the server 4, the user U can obtain drawing data based on the registration relationship list 311 from the server 4 by operating the obtain button 52b.

When the user U presses the acquisition button 52b by operating the input unit 42, the display control unit 45 acquires drawing data based on the registration relationship list 311 from the server 4 via the communication unit 40. Based on the acquired drawing data, the display control unit 45 superimposes and displays registration relationship information 91 indicating the registration relationship between the PLC master unit 3 and the PLC slave unit 2 on the electrical system diagram 92 in the drawing area 53 of the display unit 41 in a state that the user U can operate. The display control unit 45 can also acquire the registration relationship list 311 from the server 4 and display the registration relationship information 91 on the display unit 41 based on the acquired registration relationship list 311.

Figure 11 is a diagram showing an example of a display screen in which registration relationship information is superimposed on an electrical system diagram in a drawing area according to the first embodiment. As shown in Figure 11, in the drawing area 53, registration relationship information 91 is superimposed on an electrical system diagram 92.

The registration relationship information 91 shown in FIG. 11 is a topology diagram showing the registration relationship between the PLC master unit 3 and the PLC slave unit 2, and shows a master unit icon 93 indicating the PLC master unit 3 and a slave unit icon 94 indicating the PLC slave unit 2. In addition, the slave unit icon 94 of the PLC slave unit 2 registered in the PLC master unit 3 is connected by a connection line 95 to the master unit icon 93 of the PLC master unit 3 to which it is registered.

The user U can modify the registration relationship information 91 by operating the input unit 42 to move the parent device icon 93 and the child device icon 94 so that they match the wiring shown in the electrical system diagram 92 displayed as a background image. The operation on the input unit 42 can be a drag-and-drop operation of the mouse or a touch operation on the touch panel. In the drawing area 53, only the parent device icon 93 and the child device icon 94 can be operated, but the connection line 95 can also be made editable.

In addition, when a range is selected by the user U operating the input unit 42, the display control unit 45 can also align the parent device icon 93 and the child device icon 94, such as by using an alignment function within the selected range or aligning to the left or right.

The display screen 50 shown in FIG. 11 includes an information display area 56, which includes an information display button 56a. When the user U presses the information display button 56a by operating the input unit 42, the display control unit 45 causes the drawing area 53 to display the parent unit ID corresponding to the parent unit icon 93 and the child unit ID corresponding to the child unit icon 94. This allows the user U to understand the correspondence between the actual layout on the wiring and the IDs.

When the user U clicks on the parent icon 93 by operating the input unit 42, the display control unit 45 can also display the parent ID corresponding to the parent icon 93 in the drawing area 53, and when the user U clicks on the child icon 94 by operating the input unit 42, the display control unit 45 can also display the child ID corresponding to the child icon 94 in the drawing area 53. The parent ID is arranged in a manner that makes its relationship with the parent icon 93 clear, and the child ID is arranged in a manner that makes its relationship with the child icon 94 clear.

The display screen 50 shown in FIG. 11 includes a device management area 54, which includes a registration information reflection button 54a. When the user U selects the registration relationship list 311 by pressing the file selection button 52a, or when the user U changes the registration relationship information 91, the user U presses the registration information reflection button 54a by operating the input unit 42.

When the registration information reflection button 54a is pressed, the display control unit 45 outputs the registration relationship information 91 displayed in the drawing area 53 to the registration relationship change unit 46. The registration relationship change unit 46 transmits the registration relationship between the PLC parent unit 3 and the PLC child unit 2 indicated by the registration relationship information 91 as a changed registration relationship list to the server 4 via the communication unit 40. This completes the initial registration of the registration relationship between the PLC parent unit 3 and the PLC child unit 2.

In addition, when the user U presses the print button 55 by operating the input unit 42, the display control unit 45 can transmit print data for the display screen 50 to a printer (not shown) via the communication unit 40. This causes the display screen 50 to be printed by the printer (not shown).

Fig. 12 is a flowchart showing an example of processing by the terminal device according to the first embodiment. As shown in Fig. 12, the processing unit 47 of the terminal device 5 determines whether or not a file selection operation for selecting data of the electrical system diagram 92 has been performed (step S10). When the processing unit 47 determines that a file selection operation has been performed (step S10: Yes), it causes the file input unit 44 to import the data of the electrical system diagram 92 (step S11), and causes the electrical system diagram 92 to be displayed as a background image in the drawing area 53 of the display screen 50 based on the data of the electrical system diagram 92 (step S12).

When the processing of step S12 is completed or when it is determined that there is no file selection operation (step S10: No), the processing unit 47 determines whether there is a list selection operation or a list acquisition operation for acquiring the registration relationship list 311 (step S13). When it is determined that there is a list selection operation or a list acquisition operation (step S13: Yes), the processing unit 47 acquires the registration relationship list 311 or drawing data (step S14), and displays the registration relationship information 91 in the drawing area 53 of the display screen 50 based on the acquired registration relationship list 311 or drawing data (step S15).

When the processing of step S15 is completed, or when it is determined that there is no list selection operation or list acquisition operation (step S13: No), the processing unit 47 determines whether or not there is a position change operation that changes the position of the parent device icon 93 or the child device icon 94 (step S16). When it is determined that there is a position change operation (step S16: Yes), the processing unit 47 changes the registration relationship information 91 (step S17).

When the processing of step S17 is completed or when it is determined that there is no position change operation (step S16: No), the processing unit 47 determines whether or not there is a registration operation (step S18). When it is determined that there is a registration operation (step S18: Yes), the processing unit 47 changes the registration relationship list 311 based on the changed registration relationship information 91, and causes the communication unit 40 to transmit the changed registration relationship list 311 to the server 4 (step S19).

When the processing of step S19 is completed or when it is determined that there is no registration operation (step S18: No), the processing unit 47 determines whether or not it is time to end the operation (step S20). For example, when it is determined that the power (not shown) of the terminal device 5 has been turned off or when it is determined that an operation to end the operation has been performed on the input unit 42, the processing unit 47 determines that it is time to end the operation. When it is determined that it is not time to end the operation (step S20: No), the processing unit 47 transitions to the processing of step S10, and when it is determined that it is time to end the operation (step S20: Yes), it ends the processing shown in FIG. 12.

Next, the connection-related processing will be described. The connection-related processing is the processing from when the server 4 acquires the registration relationship list 311 from the terminal device 5, when each PLC master unit 3 connects to the PLC slave unit 2 in a corresponding relationship according to the registration relationship list 311, until the server 4 acquires the communication path information 111 from each PLC master unit 3.

First, the process of the server 4 that acquires the registration relationship list 311 from the terminal device 5 will be described. FIG. 13 is a flowchart showing an example of the process by the server according to the first embodiment. As shown in FIG. 13, the list management unit 323 of the server 4 determines whether or not the registration relationship list 311 has been acquired from the terminal device 5 via the communication unit 30 (step S30).

When the list management unit 323 determines that the registration relationship list 311 has been acquired (step S30: Yes), it compares the registration relationship list 311 acquired from the terminal device 5 with the registration relationship list 311 in the memory unit 31 (step S31), and determines whether the registration relationship list 311 acquired from the terminal device 5 matches the registration relationship list 311 in the memory unit 31 (step S32).

If the list management unit 323 determines that the registration relationship list 311 acquired from the terminal device 5 does not match the registration relationship list 311 in the memory unit 31 (step S32: No), the list management unit 323 updates the registration relationship list 311 in the memory unit 31 with the registration relationship list 311 acquired from the terminal device 5 (step S33). Then, the list management unit 323 creates a registered child unit list 113 for each PLC parent unit 3 based on the updated registration relationship list 311 (step S34).

The list management unit 323 transmits the registered child unit list 113 created in step S34 to each PLC parent unit 3 via the communication unit 30 (step S35). When the processing of step S35 is completed, when it is determined that the registered relationship list 311 has not been acquired (step S30: No), or when it is determined that the registered relationship lists 311 match (step S32: Yes), the list management unit 323 determines whether it is time to end the operation (step S36).

The list management unit 323 determines that it is time to end the operation, for example, when it determines that the power supply (not shown) of the server 4 has been turned off or when it determines that an operation to end the operation has been performed on an input unit (not shown). When the list management unit 323 determines that it is not time to end the operation (step S36: No), it transitions to step S30, and when it determines that it is time to end the operation (step S36: Yes), it ends the process shown in FIG. 13.

Next, the operation of the PLC master 3 from when the PLC master 3 acquires the registered slave list 113 from the server 4 until when the PLC master 3 connects to the PLC slave 2 will be described. FIG. 14 is a flowchart showing an example of a connection process performed by the PLC master according to the first embodiment.

As shown in FIG. 14, the slave registration management unit 122 of the PLC master 3 monitors connection requests from the PLC slave 2 to the PLC master 3 (step S50) and determines whether or not there is a connection request from the PLC slave 2 (step S51). If the slave registration management unit 122 determines that there is no connection request from the PLC slave 2 (step S51: No), it proceeds to step S50 and continues monitoring the connection request.

When the slave registration management unit 122 determines that there is a connection request from the PLC slave 2 (step S51: Yes), it acquires the slave ID of the PLC slave 2 from the connection request (step S52). Then, the slave registration management unit 122 checks the slave ID acquired in step S52 against the registered slave list 113 (step S53). As a result of the check in step S53, the slave registration management unit 122 determines whether the slave ID acquired in step S52 is included in the registered slave list 113 (step S54).

If the slave registration management unit 122 determines that the slave ID acquired in step S52 is included in the registered slave list 113 (step S54: Yes), it transmits a connection permission response to the PLC slave 2 that originated the connection request (step S55). If the slave registration management unit 122 determines that the slave ID acquired in step S52 is not included in the registered slave list 113 (step S54: No), it transmits a connection refusal response to the PLC slave 2 that originated the connection request (step S56).

When the processing of step S55 is completed or when the processing of step S56 is completed, the child unit registration management unit 122 determines whether or not it is time to end the operation (step S57). For example, when it is determined that the power supply (not shown) of the PLC master unit 3 has been turned off, the child unit registration management unit 122 determines that it is time to end the operation. When the child unit registration management unit 122 determines that it is not time to end the operation (step S57: No), it transitions to step S50, and when it determines that it is time to end the operation (step S57: Yes), it ends the processing shown in FIG. 14.

Next, the operation of the PLC master unit 3 when the PLC master unit 3 acquires the updated registered slave unit list 113 from the server 4 will be described. FIG. 15 is a flowchart showing an example of a connection update process by the PLC master unit according to the first embodiment.

As shown in FIG. 15, the child unit registration management unit 122 of the PLC parent unit 3 monitors updates to the registered child unit list 113 at regular intervals (step S60) and determines whether the registered child unit list 113 has been updated (step S61). The child unit registration management unit 122 determines that the registered child unit list 113 has been updated when the communication unit 10 receives an updated registered child unit list 113 from the server 4. If the child unit registration management unit 122 determines that the registered child unit list 113 has not been updated (step S61: No), it proceeds to step S60 and continues monitoring for updates to the registered child unit list 113.

If the slave registration management unit 122 determines that the registered slave list 113 has been updated (step S61: Yes), it selects the slave ID of the connected PLC slave 2 from the communication path information 111 (step S62). Then, the slave registration management unit 122 compares the connected slave ID selected in step S62 with the slave ID included in the updated registered slave list 113 (step S63).

Based on the comparison result of step S63, the child device registration management unit 122 determines whether the connected child device ID is in the registered child device list 113 (step S64). If the child device registration management unit 122 determines that the connected child device ID is not in the registered child device list 113 (step S64: No), it transmits connection refusal information to the PLC child device 2 corresponding to the connected child device ID via the communication unit 10 (step S65).

When the processing of step S65 is completed or when it is determined that the connected handset ID is in the registered handset list 113 (step S64: Yes), the handset registration management unit 122 determines whether there is an unselected connected handset ID (step S66). When it is determined that there is an unselected connected handset ID (step S66: Yes), the handset registration management unit 122 transitions to the processing of step S62.

If the child device registration management unit 122 determines that there is no unselected connected child device ID (step S66: No), it determines whether or not it is time to end the operation, similar to the processing of step S57 (step S67). If the child device registration management unit 122 determines that it is not time to end the operation (step S67: No), it transitions to the processing of step S60, and if it determines that it is time to end the operation (step S67: Yes), it ends the processing shown in FIG. 15.

Next, the operation of the PLC slave unit 2 after the PLC master unit 3 acquires the registered slave unit list 113 until the PLC slave unit 2 is connected to the PLC master unit 3 will be described. FIG. 16 is a flowchart showing an example of a connection process by the PLC slave unit according to the first embodiment.

As shown in FIG. 16, the registration management unit 222 of the PLC slave unit 2 checks the connection status with the PLC master unit 3 (step S70) and determines whether or not the PLC slave unit 2 is connected to the PLC master unit 3 (step S71). If the registration management unit 222 determines that the PLC slave unit 2 is connected to the PLC master unit 3 (step S71: Yes), the registration management unit 222 proceeds to step S70 and continues checking the connection status with the PLC master unit 3.

If the registration management unit 222 determines that the PLC master unit 3 is not connected (step S71: No), it transmits a connection request to the PLC master unit 3 via the communication unit 20 (step S72). The registration management unit 222 then checks the response from the PLC master unit 3 (step S73) and determines whether the response from the PLC master unit 3 is a connection permission response (step S74).

If the registration management unit 222 determines that the response from the PLC parent unit 3 is a connection permission response (step S74: Yes), it executes a process to set the PLC parent unit 3 that sent the connection permission response as the connection destination (step S75). If the registration management unit 222 determines that the response from the PLC parent unit 3 is not a connection permission response (step S74: No), it transmits a connection request to another PLC parent unit 3 (step S76) and transitions to the process of step S73.

When the processing of step S75 is completed, the registration management unit 222 determines whether or not it is time to end the operation (step S77). For example, when the registration management unit 222 determines that the power supply (not shown) of the PLC child unit 2 has been turned off, the registration management unit 222 determines that it is time to end the operation. When the registration management unit 222 determines that it is not time to end the operation (step S77: No), the processing proceeds to step S70, and when the registration management unit 222 determines that it is time to end the operation (step S77: Yes), the processing shown in FIG. 16 is terminated.

Next, the sequence for collecting the communication path information 111 will be described. The PLC slave unit 2 and the PLC master unit 3 periodically communicate with each other via a power line carrier in response to a request sent by the data collection unit 121 of the PLC master unit 3 to the PLC slave unit 2 via the communication unit 10. Periodically means, for example, once every 30 minutes.

When the communication path management unit 123 of the PLC master unit 3 receives a signal from the PLC slave unit 2, it stores the communication result and communication quality together with the time when the communication was requested in the memory unit 11 as communication path information 111. The communication result is, for example, whether or not there is a response from the PLC slave unit 2 to the request from the PLC master unit 3, and the communication quality is, for example, the noise level and signal-to-noise ratio of the signal received from the PLC slave unit 2.

The data collection unit 321 of the server 4 periodically collects the communication path information 111 from the PLC master unit 3. The data collection unit 321 associates the communication path information 111 with the master unit ID of the PLC master unit 3 from which the communication path information 111 was collected and stores the information in the storage unit 31 as communication path information 312 for a certain period of time. The certain period of time is, for example, about 30 days.

Next, the registration correction support process executed in the PLC meter reading system 100 will be described. The registration correction support process includes a connection status determination process, a connection status reflection process, and a correction support process. The connection status determination process is a process executed by the server 4 to check the connection status between the PLC parent unit 3 and the PLC child unit 2. The connection status reflection process is a process in which the display control unit 45 of the terminal device 5 reflects the result of the connection status determination process executed by the server 4 on the display screen 50. The registration correction support process is a process in which the user U supports the correction of the registration relationship between the PLC parent unit 3 and the PLC child unit 2.

First, the connection status determination process by the server 4 and the connection status reflection process by the terminal device 5 will be described. In the connection status determination process, the display processing unit 324 of the server 4 determines the color of the child device icon 94 on the display screen 50 based on the communication path information 312 stored in the storage unit 31, and generates drawing data for drawing, on the display unit 41, the registration relationship information 91 including the child device icon 94 colored in the determined color.

Then, the display control unit 45 of the terminal device 5 causes the display unit 41 to display the registration relationship information 91 including the child device icons 94 colored in the color determined by the display processing unit 324 based on the drawing data generated in the connection status reflection process. When the registration relationship list 311 and color information that is information on the color determined by the display processing unit 324 are transmitted from the display processing unit 324 of the server 4 to the terminal device 5 via the communication unit 30, the display control unit 45 causes the display unit 41 to display the registration relationship information 91 in which each child device icon 94 is colored in the color determined by the display processing unit 324 based on the registration relationship list 311 and color information received by the communication unit 40.

Figure 17 is a flowchart showing the connection status determination process by the server according to the first embodiment. The process shown in Figure 17 is performed for each PLC slave unit 2 of the slave unit icon 94 included in the display screen 50. The PLC slave unit 2 that is the target of the process shown in Figure 17 may be referred to as the target slave unit.

As shown in FIG. 17, the display processing unit 324 of the server 4 acquires the communication result and communication quality of the target slave unit from the communication path information 312 stored in the memory unit 31 (step S80). Next, the display processing unit 324 determines whether the number of successful communications between the target slave unit and the PLC master unit 3 is zero (step S81). If the display processing unit 324 determines that the number of successful communications with the PLC master unit 3 is zero (step S81: Yes), it determines the color of the slave unit icon 94 of the target slave unit to a color indicating communication failure (step S82).

If the display processing unit 324 determines that the number of successful communications with the PLC parent unit 3 is not zero (step S81: No), it determines whether the number of successful communications with the PLC parent unit 3 is equal to or greater than the number of failed communications with the PLC parent unit 3 (step S83). If the display processing unit 324 determines that the number of successful communications is equal to or greater than the number of failed communications (step S83: Yes), it sets the color of the child unit icon 94 of the target child unit to a color indicating successful communication (step S84).

The method of determining whether communication is successful by the display processing unit 324 is not limited to comparing the number of successful communications with the number of unsuccessful communications. For example, the display processing unit 324 compares the number of communication failures allowed as the operation of the PLC meter reading system 100 with the number of communication failures, and determines that communication is successful if the number of communication failures is less than the number of allowed communication failures. For example, if up to three communication failures are allowed out of 12 communications performed over a six-hour period, and data can be recovered up to three communication failures, the display processing unit 324 can determine that communication is successful if the number of communication failures out of 12 communications performed over a six-hour period is three or less.

When the display processing unit 324 determines that the number of successful communications with the PLC master 3 is less than the number of failed communications with the PLC master 3 (step S83: No), it determines whether the signal level is less than the threshold (step S85). When the display processing unit 324 determines that the signal level is not less than the threshold (step S85: No), it determines whether the signal-to-noise ratio is less than the threshold (step S86). Here, the threshold can be a value with a margin as a communicable level with respect to a value theoretically determined from the number of system branches of the wiring actually installed and the communication distance, or a theoretically communicable value determined from the communication method used. Note that the signal level and the signal-to-noise ratio are the signal level and the signal-to-noise ratio of the signal of the PLC master 3 or the intermediate terminal received by the PLC slave 2, but may also be the signal level and the signal-to-noise ratio of the signal of the PLC slave 2 received by the PLC master 3 or the intermediate terminal.

If the display processing unit 324 determines that the signal level is below the threshold (step S85: Yes) or that the signal-to-noise ratio is below the threshold (step S86: Yes), it determines the color of the slave icon 94 of the target slave to a color indicating the possibility of a system error (step S87). A system error means that the target slave is connected to a system different from the PLC master 3 registered in the registration relationship list 311.

Even though the PLC slave unit 2 is connected to the PLC master unit 3 of a different system, when the PLC meter reading system 100 is started up, there are few devices connected to the power line 6 and the communication environment is good, so that communication between the different systems may be possible through the bundled wiring, although the signal is weak. Although there is no problem when checking the connection between the PLC master unit 3 and the PLC slave unit 2, an event occurs in which communication is not possible and data is lost when the equipment begins to operate after the PLC meter reading system 100 is put into operation. Therefore, the display processing unit 324 determines that a PLC slave unit 2 with a signal level below a threshold or a PLC slave unit 2 with a signal-to-noise ratio below a threshold is a PLC slave unit 2 that may be in a system error.

If the display processing unit 324 determines that the signal-to-noise ratio is not less than the threshold (step S86: No), it determines the color of the child device icon 94 of the target child device to a color indicating successful communication (step S88). If the processing of step S82, step S84, step S87, or step S88 is completed, the display processing unit 324 ends the processing shown in FIG. 17.

The process shown in FIG. 17 is automatically executed by the server 4 at regular intervals, or is executed at any timing in response to an instruction from the user U via the terminal device 5. The process shown in FIG. 17 is executed for all PLC slave units 2, or for selected PLC slave units 2.

Next, the correction support process will be described. FIG. 18 is a flowchart showing another example of the process by the terminal device according to the first embodiment. The processes of steps S90 to S93, S96 to S99, and S101 shown in FIG. 18 are the same as the processes of steps S10 to S13, and S16 to S20 shown in FIG. 12, and therefore will not be described.

18, when the processing unit 47 of the terminal device 5 determines that a list selection operation or a list acquisition operation has been performed (step S93: Yes), it acquires the registration relationship list 311 and color information from the server 4 or an external device (step S94) and displays the registration relationship information 91 in the drawing area 53 of the display screen 50 based on the acquired registration relationship list 311 and color information (step S95). Note that in the processing of steps S94 and S95, the processing unit 47 can also acquire drawing data from the server 4 instead of the registration relationship list 311 and color information and display the registration relationship information 91 in the drawing area 53 of the display screen 50 based on the drawing data.

After the processing unit 47 causes the communication unit 40 to transmit the changed registration relationship list 311 to the server 4 in the processing of step S99, the processing unit 47 acquires the registration relationship list 311 and color information from the server 4, and updates the registration relationship information 91 based on the acquired registration relationship list 311 and color information (step S100). Note that in the processing of step S100, the processing unit 47 can also acquire drawing data from the server 4 instead of the registration relationship list 311 and color information, and display the registration relationship information 91 in the drawing area 53 of the display screen 50 based on the drawing data.

Next, the flow of the registration content correction work in which user U checks the connection status of the power line carrier communication network and corrects the registration content will be explained. Figure 19 is a flowchart showing an example of the registration content correction work by the user of the terminal device according to the first embodiment.

The user U checks whether the colors of all the child device icons 94 on the display screen 50 displayed on the display unit 41 are colors that indicate successful communication (step S110). If the colors of any of the child device icons 94 do not indicate successful communication (step S110: No), the user U uses a drag-and-drop operation on the input unit 42 to move the child device icon 94 that is a color that indicates a communication failure or a color that indicates a possible system error to a connection position with another parent device icon 93 (step S111). If the colors of all the child device icons 94 are colors that indicate successful communication (step S110: Yes), the user U ends the registration content correction work shown in FIG. 19.

For example, when the information display button 56a shown in FIG. 11 is pressed or the slave icon 94 is clicked, the display control unit 45 can display the communication history information and communication statistics information of the PLC slave 2 on the display screen 50, and can display the communication ID of the PLC master 3 with which the PLC slave 2 attempted to communicate, etc. on the display screen 50. This allows the user U to easily identify a PLC master 3 that has not been registered.

Figure 20 is a diagram showing another example of a display screen in which registration relationship information is superimposed on an electrical system diagram in a drawing area according to the first embodiment. The registration relationship information 91 shown in Figure 20 differs from the registration relationship information 91 shown in Figure 11 in that a master icon 93 is placed at a position corresponding to the PLC master 3 in the electrical system diagram 92, and a slave icon 94 is placed at a position corresponding to the PLC master 3 in the electrical system diagram 92.

When the user U operates the input unit 42 to click on a child unit icon 94 for which he/she wishes to display communication history information and communication statistics information on the display screen 50 shown in FIG. 20, the display control unit 45 displays a pop-up screen including the communication history information and communication statistics information on the display screen 50. FIG. 21 is a diagram showing an example of a pop-up screen including communication history information and communication statistics information according to the first embodiment. In the pop-up screen 98 shown in FIG. 21, the communication history information includes the parent unit ID of the PLC parent unit 3 to be communicated with, the communication result with the PLC parent unit 3, the signal level, the signal-to-noise ratio, and the communication time.

The signal level and signal-to-noise ratio are the signal level and signal-to-noise ratio of the signal from the PLC master unit 3 or the intermediate terminal received by the PLC slave unit 2, but may also be the signal level and signal-to-noise ratio of the signal from the PLC slave unit 2 received by the PLC master unit 3 or the intermediate terminal.

In addition, in the pop-up screen 98 shown in FIG. 21, the communication statistics information includes, for each PLC master unit 3, the total number of communications, the number of successful communications, the number of unsuccessful communications, the signal level, and the signal-to-noise ratio. In the communication statistics information shown in FIG. 21, the signal level and the signal-to-noise ratio are shown as maximum, average, and minimum values.

Returning to FIG. 19, the description of the user U's registration content correction operation will be continued. After completing the process of step S111, the user U presses the registration information reflection button 54a shown in FIG. 21 by operating the input unit 42 (step S112). This causes the registration relationship change unit 46 of the terminal device 5 to transmit to the server 4 the registration relationship list 311 with the contents at the time the registration information reflection button 54a was pressed. The server 4 performs the processes shown in FIGS. 13 and 17, and the PLC master unit 3 and the PLC slave unit 2 automatically execute the processes of FIGS. 14 to 16 based on the registered slave unit list 113 in the changed registration relationship list 311.

As a result, in the PLC meter reading system 100, when there is an error in setting the registration relationship between the PLC master unit 3 and the PLC slave unit 2 during the initial registration process, or when the electrical system diagram 92 does not match the system that is actually wired, the registration relationship between the PLC master unit 3 and the PLC slave unit 2 can be easily corrected.

As described above, the PLC meter reading system 100 according to the first embodiment includes the display control unit 45 and the registration relationship change unit 46. The PLC meter reading system 100 is an example of a communication system. The display control unit 45 causes the display unit 41 to display a display screen 50 including information indicating the registration relationship between the PLC slave 2 and the PLC master units 3 that perform power line carrier communication with the registered PLC slave 2 among the multiple PLC slave units 2, and an electrical system diagram 92 at the installation location of the multiple PLC master units 3 and the multiple PLC slave units 2, in a changeable manner. The PLC slave unit 2 is an example of a slave unit, and the PLC master unit 3 is an example of a master unit. When the registration relationship is changed by an operation on the display screen 50, the registration relationship change unit 46 performs processing to change the PLC slave unit 2 that is the communication target to the PLC master unit 3 that is the target of the change in the registration relationship. As a result, in the PLC meter reading system 100, the registration relationship between the PLC master 3 and the PLC slave 2 and the electrical system diagram 92 are displayed on the same display screen 50, so there is no need to check the registration relationship between the PLC master 3 and the PLC slave 2 using a paper system diagram to confirm the registration relationship between the PLC master 3 and the PLC slave 2. Therefore, in the PLC meter reading system 100, the registration contents of the PLC slave 2 in the PLC master 3 can be easily corrected. In addition, in the PLC meter reading system 100, the registration relationship between the PLC master 3 and the PLC slave 2 is automatically reflected by editing the registration relationship on the display screen 50, so the user U can check and control the display on one screen without using separate software for registration.

The display control unit 45 also displays, on the display unit 41, a screen in which registration relationship information 91, which is information indicating the registration relationship, is superimposed on the electrical system diagram 92 as the display screen 50. This allows the PLC meter reading system 100 to display the electrical system diagram 92 as a background image on the display unit 41, allowing the user U to easily edit the registration relationship information 91.

The registration relationship information 91 also includes child unit icons 94 indicating each of the multiple PLC child units 2. The display control unit 45 displays the child unit icons 94 movably on the display screen 50. This allows the user U to easily edit the registration relationship information 91 in the PLC meter reading system 100.

The PLC meter reading system 100 also includes a display processing unit 324. The display processing unit 324 determines the color of the slave icon 94 based on the communication state between the PLC slave 2 corresponding to the slave icon 94 and the PLC master 3 associated with the PLC slave 2 corresponding to the slave icon 94 in the registration relationship information 91. The display control unit 45 displays the slave icon 94 on the display screen 50 in the color determined by the display processing unit 324. In this way, in the PLC meter reading system 100, the user U can easily determine whether or not there is an error in the registration relationship, and can easily edit the registration relationship information 91.

The display processing unit 324 also determines which of the multiple PLC slave units 2 may have a registration relationship error, and determines the color of the slave unit icon 94 of the PLC slave unit 2 determined to have a registration relationship error to be different from the color of the slave unit icon 94 of the PLC slave unit 2 other than the PLC slave unit 2 determined to have a registration relationship error. This allows the user U in the PLC meter reading system 100 to easily determine whether there is a system error in which pseudo communication has occurred, and to easily edit the registration relationship information 91.

When a slave icon 94 is selected, the display control unit 45 causes the display unit 41 to display the communication result and communication quality of the PLC slave 2 corresponding to the selected slave icon 94. This allows the user U in the PLC meter reading system 100 to know that there is an error in the registration relationship from the communication result and communication quality, etc.

The PLC meter reading system 100 also includes a list management unit 323 that manages a registration relationship list 311 that includes, for each PLC parent unit 3, a registered child unit list 113, which is information on PLC child units 2 that have a registration relationship among the multiple PLC child units 2. The registration relationship change unit 46 outputs the changed registration relationship list 311 to the list management unit 323. The list management unit 323 causes the PLC parent unit 3 to change the PLC 2 child unit with which it is to communicate by transmitting the registered child unit list 113 included in the changed registration relationship list 311 to the multiple PLC parent units 3. As a result, by editing the registration relationship on the display screen 50, the PLC meter reading system 100 can automatically change the registration relationship between the PLC parent unit 3 and the PLC child unit 2.

The display control unit 45 also causes the display unit 41 to display the slave unit ID of the PLC slave unit 2 and the master unit ID of the PLC master unit 3. The slave unit ID is identification information of the PLC slave unit 2, and the master unit ID is identification information of the PLC master unit 3. This allows the user U in the PLC meter reading system 100 to easily understand where the PLC slave unit 2 and the PLC master unit 3 are installed.

Each of the multiple PLC slave units 2 acquires meter reading data from a corresponding one of the multiple energy meters 1, and transmits the acquired meter reading data to a PLC master unit 3 with which it is registered among the multiple PLC master units 3. Each of the multiple PLC master units 3 collects meter reading data from a PLC slave unit 2 with which it is registered among the multiple PLC slave units 2. This allows the user U to easily edit the registration relationship information 91 in the PLC meter reading system 100.

Embodiment 2.
The PLC meter reading system according to the second embodiment differs from the PLC meter reading system 100 according to the first embodiment in that a registration relationship list is automatically generated based on an equipment list in which a registration relationship between a PLC master and a PLC slave is not set. In the following, components having the same functions as those in the first embodiment are denoted by the same reference numerals and description thereof is omitted, and the differences from the PLC meter reading system 100 according to the first embodiment are mainly described.

Fig. 22 is a diagram showing an example of the configuration of a server of the PLC meter reading system according to the second embodiment. As shown in Fig. 22, the server 4A of the PLC meter reading system according to the second embodiment differs from the server 4 according to the first embodiment in that it includes a memory unit 31A and a control unit 32A instead of the memory unit 31 and the control unit 32.

The storage unit 31A differs from the storage unit 31 in that it further stores a device list 316. The device list 316 includes the parent unit IDs of multiple PLC parent units 3 and the child unit IDs of multiple PLC child units 2, but the parent unit IDs are not associated with the child unit IDs. FIG. 23 is a diagram showing an example of a device list according to the second embodiment. As shown in FIG. 23, the device list 316 includes multiple parent unit IDs and multiple child unit IDs.

Control unit 32A differs from control unit 32 in that it includes list management unit 323A instead of list management unit 323. List management unit 323A differs from list management unit 323 in that it further includes a function of acquiring device list 316 from terminal device 5 or other device, and automatically creating registration relationship list 311 based on the acquired device list 316.

The list management unit 323A receives, for example, the device list 316 transmitted from the terminal device 5 or another device via the network 8 and the communication unit 30, and stores the received device list 316 in the storage unit 31A. The list management unit 323A then performs an automatic registration process to automatically create the registration relationship list 311 based on the device list 316.

In the automatic registration process, the list management unit 323A creates the registration relationship list 311 by changing the selected parent while excluding information about the PLC child units 2 registered in the child unit registration process, which registers the PLC child units 2 to the selected parent unit based on the communication results and communication quality between the selected parent unit, which is a parent unit selected from multiple PLC parent units 3, and each PLC child unit 2 shown in the device list 316, from the device list 316.

In this automatic registration process, the PLC slave units 2 are registered to the PLC master unit 3 while changing the PLC master unit 3 that transmits the device list 316. This requires time to establish a connection with the PLC slave unit 2 when registering it to the PLC master unit 3, and time to create the communication path information 111. Therefore, it may take a long time to register the PLC slave units 2 to all the PLC master units 3.

For example, suppose that the power line carrier communication used in the PLC meter reading system according to the second embodiment is low-speed power line carrier communication using a frequency band of 10 to 450 kHz, the PLC meter reading system according to the second embodiment includes four PLC master units 3 and 400 PLC slave units 2, there are 100 PLC slave units 2 connected to the same system as each PLC master unit 3, and it takes three hours for the PLC master unit 3 to collect the communication path information 111.

In this case, even if 50 PLC slave units 2 are registered for each slave unit registration process described above, the time required to register the PLC slave units 2 to all PLC master units 3 is 6 hours x 8 attempts = 48 hours. In an actual system startup, it may not be possible to secure the number of days between setting up and checking communication due to construction schedules, etc., and it may take a long time to complete the registration process if all PLC master units 3 and PLC slave units 2 are automatically registered.

The display control unit 45 of the terminal device 5 according to the second embodiment displays a registration setting screen on the display unit 41 based on the device list 316 so that the user U can register in advance the PLC slave units 2 whose connection systems are clear to the PLC master unit 3 by operating the input unit 42. The registration setting screen includes information on each of the PLC master unit 3 and the PLC slave units 2 whose master unit IDs and slave unit IDs are included in the device list 316, and includes, for example, the master unit icon 93 and slave unit icon 94 described above.

Then, the display control unit 45 creates a registered child unit list 113 including the parent unit ID of the PLC parent unit 3 to which the PLC child unit 2 is registered and the child unit ID of the PLC child unit 2 registered to the PLC parent unit 3, and transmits the generated registered child unit list 113 to the server 4A via the communication unit 40 and the network 8. The display control unit 45 also transmits an equipment list 316, which excludes the child unit IDs included in the created registered child unit list 113, to the server 4A via the communication unit 40 and the network 8.

As a result, in the PLC meter reading system of embodiment 2, the number of PLC slave units 2 to be registered to the PLC parent unit 3 during the automatic registration process can be reduced, and the time required to complete registration of the PLC slave units 2 to all PLC parent units 3 can be shortened.

For example, if the allocation of 10% of the PLC slave units 2 within the same system is unknown, the registration time can be shortened to 36 minutes. In a system with four PLC master units 3 and 100 PLC slave units 2 connected to each PLC master unit 3, if 50 PLC slave units 2 can be determined on each attempt, registration can be completed in 0.6 hours x 4 + 3 hours x 4 = 14.4 hours. This is effective in cases where the system is known to a certain extent, but expansion or replacement work for only some sections is not reflected in the drawings, leaving the system unknown, for example.

The list management unit 323A also updates the registration relationship list 311 each time the registration of one PLC child unit 2 is set or changed by the automatic registration process, and transmits the updated registration relationship list 311 to the terminal device 5 via the communication unit 30 and the network 8. The display control unit 45 of the terminal device 5 performs processing to display the registration relationship information 91 based on the updated registration relationship list 311 on the display unit 41 each time the registration relationship list 311 is updated.

As a result, in the PLC meter reading system according to the second embodiment, the registration-related information 91 is changed in conjunction with the automatic registration process, so that the current progress of the automatic registration can be visually communicated to the user U. Therefore, the user U can grasp from the screen the approximate time remaining until completion, and can efficiently coordinate the schedule with other processes when the system is introduced.

Figure 24 is a flowchart showing an example of a process for automatically creating a registration relationship list by a server according to the second embodiment. As shown in Figure 24, the list management unit 323A of the server 4A acquires a device list 316 from a terminal device 5 or another device via the network 8 and the communication unit 30, and stores the acquired device list 316 in the memory unit 31A (step S120).

Next, the list management unit 323A selects one unselected PLC master unit 3 from among the multiple PLC master units 3 whose master unit IDs are included in the device list 316 (step S121). The list management unit 323A transmits the registered slave unit list 113, which includes all slave unit IDs included in the device list 316, to the PLC master unit 3 selected in step S121 via the communication unit 30 and the network 7 (step S122).

Then, the list management unit 323A waits until the data collection unit 321 acquires a certain number of samples of communication path information 111 from the PLC parent unit 3 that is the destination of the registered child unit list 113 (step S123). The certain number of samples is, for example, 6 samples. If communication between the PLC parent unit 3 and the PLC child unit 2 is performed every 30 minutes, the list management unit 323A waits for 3 hours.

Next, the list management unit 323A performs a first communication status determination process (step S124). The first communication status determination process shown in step S124 is the process of steps S130 to S138 shown in FIG. 25, and will be described in detail later.

Next, the list management unit 323A determines whether or not there is a PLC slave unit 2 indicating a communication failure or a possible system error among the multiple PLC slave units 2 whose slave unit IDs are included in the communication path information 111 (step S125). If the list management unit 323A determines that there is a PLC slave unit 2 indicating a communication failure or a possible system error (step S125: Yes), it determines whether or not there is a PLC master unit 3 that has not been selected in step S121 (step S126).

If the list management unit 323A determines that there is an unselected PLC master unit 3 (step S126: Yes), it transmits the registered slave unit list 113 from which the slave unit IDs of the PLC slave units 2 indicating communication failure or the PLC slave units 2 indicating the possibility of a system error have been deleted to the selected PLC master unit 3 via the network 7 and the communication unit 30 (step S127). Even if the list management unit 323A determines that there is no unselected PLC master unit 3 (step S126: No), it can proceed to step S127 if the ratio of the number of PLC slave units 2 indicating communication failure or the number of PLC slave units 2 indicating the possibility of a system error to the number of slave unit IDs originally included in the device list 316 is equal to or greater than a preset value.

The list management unit 323A also selects one of the unselected PLC master units 3, and transmits the registered slave unit list 113, which includes the slave unit IDs of all PLC slave units 2 that indicate the possibility of communication failure or system error, to the selected PLC master unit 3 via the network 7 and the communication unit 30 (step S128), and then proceeds to step S123.

If the list management unit 323A determines that there is no unselected PLC master unit 3 (step S126: No), it performs a second communication status determination process (step S129). The second communication status determination process shown in step S129 is the process of steps S140 to S145 shown in FIG. 26, and will be described in detail later.

When the processing of step S129 is completed, or when it is determined that there is no PLC slave unit 2 indicating a communication failure or a possible system error (step S125: No), the list management unit 323A ends the processing shown in FIG. 24.

Figure 25 is a flowchart showing an example of the first communication state determination process by the server according to the second embodiment. The processes of steps S131, S132, S133, S135, and S136 shown in Figure 25 are the same as the processes of steps S80, S81, S83, S85, and S86 shown in Figure 17, and therefore will not be described. The list management unit 323A performs the process of Figure 25 for all PLC slave units 2 whose slave unit IDs are included in the communication path information 312.

As shown in FIG. 25, if the list management unit 323A determines that the number of successful communications with the PLC parent unit 3 is zero (step S131: Yes), it determines that the target child unit is a PLC child unit 2 that has failed to communicate (step S132).

If the list management unit 323A determines that the number of successful communications is equal to or greater than the number of failed communications (step S133: Yes), it determines that the target slave unit is a PLC slave unit 2 indicating successful communications (step S134). If the list management unit 323A determines that the signal level is less than the threshold (step S135: Yes) or that the signal-to-noise ratio is less than the threshold (step S136: Yes), it determines that the target slave unit is a PLC slave unit 2 indicating a possible system error (step S137).

In addition, if the list management unit 323A determines that the signal-to-noise ratio is not less than the threshold value (step S136: No), it determines that the target slave unit is a PLC slave unit 2 indicating successful communication (step S138).

Fig. 26 is a flowchart showing an example of the second communication state determination process by the server according to the second embodiment. As shown in Fig. 26, the list management unit 323A selects the PLC slave unit 2 indicating a communication failure or a PLC slave unit 2 indicating a possible system error as the target slave unit, and compares the signal levels of the PLC slave unit 2 indicating a communication failure or a PLC slave unit 2 indicating a possible system error at the time of registration with each PLC master unit 3 based on the communication path information 111 of each PLC master unit 3 acquired in step S123 (step S140).

The list management unit 323A determines whether or not there is a PLC parent unit 3 with a higher signal level than when it was registered, based on the result of the signal level comparison in step S140 (step S141). If the list management unit 323A determines that there is no PLC parent unit 3 with a higher signal level than when it was registered (step S141: No), it compares the signal-to-noise ratios of the PLC child units 2 indicating communication failure or the PLC child units 2 indicating the possibility of a system error at the time of registration to each PLC parent unit 3 (step S142).

As a result of comparing the signal-to-noise ratios in step S142, the list management unit 323A determines whether or not there is a PLC parent unit 3 with a higher signal-to-noise ratio than at the time of registration (step S143). If the list management unit 323A determines that there is no PLC parent unit 3 with a higher signal-to-noise ratio than at the time of registration (step S143: No), it changes the color of the child unit icon 94 of the PLC child unit 2 indicating a communication failure or a PLC child unit 2 indicating a possible system error to a color indicating that there is no difference in communication quality between the PLC parent units 3 (step S144).

When the list management unit 323A determines that another PLC master unit 3 has a higher signal level than at the time of registration (step S141: Yes), or when the list management unit 3 determines that another PLC master unit 3 has a higher signal-to-noise ratio than at the time of registration (step S143: Yes), the list management unit 323A determines the corresponding PLC master unit 3 as the registration destination for the PLC slave unit 2 indicating communication failure or the PLC slave unit 2 indicating the possibility of a system error (step S145). When the process of step S144 or step S145 is completed, the list management unit 323A ends the process shown in FIG. 26.

For PLC slave units 2 where there is no difference in communication quality between PLC master units 3, data collection continues as is and a judgment is made from more data, or the work is completed by user U determining the connection system through investigation, such as checking the electrical diagram and the placement of the actual unit, and checking continuity with a line checker.

As described above, the server 4A of the PLC meter reading system according to the second embodiment includes a list management unit 323A. Based on a device list 316 that includes information on a plurality of PLC masters 3 and information on a plurality of PLC slaves 2 and in which at least some of the registration relationships are not set, the list management unit 323A creates a registration relationship list 311 that registers each of the plurality of PLC slaves 2 with a PLC master 3 connected to the same system among the plurality of PLC masters 3, thereby indicating the registration relationships. In this way, the PLC meter reading system according to the second embodiment can reduce the workload of the user U.

The list management unit 323A also creates the registration relationship list 311 by changing the selected parent unit while excluding from the device list 316 the information of the PLC child unit 2 registered in the process of registering the PLC child unit 2 to the selected parent unit based on the communication results and communication quality between the selected parent unit, which is a PLC parent unit 3 selected from among the multiple PLC parent units 3, and each PLC child unit 2 shown in the device list 316. As a result, the PLC meter reading system according to the second embodiment can appropriately create the registration relationship list 311.

Note that some or all of the functions of the terminal device 5 may be located in the server 4 or the server 4A, and some or all of the functions of the server 4 may be located in the terminal device 5. Also, the server 4 or the server 4A may be composed of multiple devices.

The hardware configuration of the control units 12, 22, 32, 32A and the processing unit 47 described in the first and second embodiments will be described. The control units 12, 22, 32, 32A and the processing unit 47 are realized by a processing circuit. The processing circuit may be a processor and memory that executes a program stored in a memory, or may be dedicated hardware. The processing circuit is also called a control circuit.

27 is a diagram showing an example of the configuration of a processing circuit when the processing circuits provided in each of the processing units according to the first and second embodiments are realized by a processor and a memory. The processing circuit 60 shown in FIG. 27 is a control circuit and includes a processor 61 and a memory 62. When the processing circuit 60 is configured with the processor 61 and the memory 62, each function of the processing circuit 60 is realized by software, firmware, or a combination of software and firmware. The software or firmware is described as a program and stored in the memory 62. In the processing circuit 60, the processor 61 reads and executes the program stored in the memory 62 to realize each function. That is, the processing circuit 60 includes a memory 62 for storing a program that results in the processing of any of the control units 12, 22, 32, and 32A and the processing unit 47. This program can also be said to be a program for causing any of the control units 12, 22, 32, and 32A and the processing unit 47 to execute each function realized by the processing circuit 60. This program may be provided by a recording medium on which the program is recorded, or by other means such as a communication medium.

Here, the processor 61 is, for example, a CPU (Central Processing Unit), a processing device, an arithmetic device, a microprocessor, a microcomputer, or a DSP (Digital Signal Processor). The memory 62 is, for example, a RAM (Random Access Memory), a ROM (Read Only Memory), a flash memory, an EPROM (Erasable Programmable ROM), an EEPROM (Electrically EPROM), or other non-volatile or volatile semiconductor memory, a magnetic disk, a flexible disk, an optical disk, a compact disk, a mini disk, or a DVD (Digital Versatile Disc).

Figure 28 is a diagram showing an example of a processing circuit provided in the processing unit according to the first and second embodiments, configured with dedicated hardware. The processing circuit 63 shown in Figure 28 corresponds to, for example, a single circuit, a composite circuit, a programmed processor, a parallel programmed processor, an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or a combination of these. The processing circuit may be partially realized with dedicated hardware and partially realized with software or firmware. In this way, the processing circuit can realize each of the above-mentioned functions by dedicated hardware, software, firmware, or a combination of these.

The configurations shown in the above embodiments are merely examples, and may be combined with other known technologies, or the embodiments may be combined with each other. In addition, parts of the configurations may be omitted or modified without departing from the spirit of the invention.

1 Power meter, 2 PLC slave unit, 3 PLC master unit, 4, 4A Server, 5 Terminal device, 6 Power line, 7, 8 Network, 9 Facility, 10, 20, 30, 40 Communication unit, 11, 21, 31, 31A Memory unit, 12, 22, 32, 32A Control unit, 41 Display unit, 42 Input unit, 43 Input processing unit, 44 File input unit, 45 Display control unit, 46 Registration relationship change unit, 47 Processing unit, 50 Display screen, 51 Background drawing selection area, 51a, 52a File selection button, 52 Registration relationship list selection area, 52b Acquisition button, 53 Drawing area, 54 Device management area, 54a Registration information reflection button, 55 Print button, 56 Information display area, 56a Information display button, 91 Registration relationship information, 92 Electrical system diagram, 93 Master unit icon, 94 Child unit icon, 95, 97 Connection line, 96 Figure, 98 Pop-up screen, 100 PLC meter reading system, 101, 201, 301 First communication unit, 102, 202, 302 Second communication unit, 111, 212, 312 Communication path information, 112 Parent unit ID, 113 Registered child unit list, 114, 313 Meter reading data, 121, 221, 321 Data collection unit, 122 Child unit registration management unit, 123, 223 Communication path management unit, 211 Child unit ID, 222 Registration management unit, 311 Registration relationship list, 314 Parent unit ID list, 315 Child unit ID list, 316 Device list, 322 Communication path registration unit, 323, 323A List management unit, 324 Display processing unit.

Claims (14)

a display control unit that causes a display unit to display, on a display unit, a display screen including information indicating a registration relationship of a plurality of slave units with respect to a plurality of master units that respectively perform power line carrier communication with a registered slave unit among the plurality of slave units, and an electrical system diagram of an installation location of the plurality of master units and the plurality of slave units, in a changeable manner, the registration relationship;
A communication system comprising: a registration relationship change unit that performs processing to cause a parent unit that is the subject of the change in the registration relationship to change a child unit that is the subject of communication when the registration relationship is changed by an operation on the display screen. The display control unit is
The communication system according to claim 1 , wherein a screen in which the information indicating the registration relationship is superimposed on the electrical system diagram is displayed on the display unit as the display screen. The information indicating the registration relationship includes:
a child device icon indicating each of the plurality of child devices;
The display control unit is
3. The communication system according to claim 1, wherein the slave unit icon is displayed on the display screen in a movable manner. a display processing unit that determines a color of the child device icon based on a communication state of the child device corresponding to the child device icon;
The display control unit is
The communication system according to claim 3 , wherein the slave unit icon is displayed on the display screen in a color determined by the display processing unit. The display processing unit is
The communication system according to claim 4, characterized in that a handset among the plurality of handset units is determined to have a possible error in the registration relationship, and the color of the handset icon of the handset unit determined to have a possible error in the registration relationship is determined to be different from the color of the handset icon of the handset unit other than the handset determined to have a possible error in the registration relationship. The display control unit is
The communication system according to claim 3 , wherein when the handset icon is selected, the display unit displays a communication result and a communication quality of the handset corresponding to the selected handset icon. The display control unit is
The communication system according to claim 1 , wherein identification information of the child device and the parent device is displayed on the display unit. a list management unit that manages a registration relationship list including, for each of the parent devices, a registered child device list that is information on child devices having the registration relationship among the plurality of child devices;
The registration relationship change unit,
outputting the changed registration relationship list to the list management unit;
The list management unit
The communication system according to any one of claims 1 to 7, characterized in that the parent unit is caused to change the child unit with which it communicates by transmitting the registered child unit list contained in the changed registration relationship list to the plurality of parent units. The communication system according to any one of claims 1 to 8, further comprising a list management unit that creates a registration relationship list indicating the registration relationships by registering each of the plurality of child devices with a parent device among the plurality of parent devices that is connected to the same system, based on an equipment list that includes information on the plurality of parent devices and information on the plurality of child devices and in which at least some of the registration relationships are not set. The list management unit
The communication system according to claim 9, characterized in that the registration relationship list is created by changing the selected parent unit while excluding information of the registered child unit from the device list, and performing a process of registering the child unit to the selected parent unit based on communication results and communication quality between a selected parent unit, which is a parent unit selected from the multiple parent units, and each child unit shown in the device list. Each of the plurality of child devices
Obtaining meter reading data from a corresponding one of a plurality of watt-hour meters, and transmitting the obtained meter reading data to a parent unit having the registered relationship among the plurality of parent units;
Each of the plurality of parent devices
The communication system according to claim 1 , wherein the meter reading data is collected from a slave unit that is in the registered relationship among the plurality of slave units. a display control unit that causes a display unit to display, on a display unit, a display screen including information indicating a registration relationship of a plurality of slave units with respect to a plurality of master units that respectively perform power line carrier communication with a registered slave unit among the plurality of slave units, and an electrical system diagram of an installation location of the plurality of master units and the plurality of slave units, in a changeable manner, the registration relationship;
A setting device comprising: a registration relationship change unit that performs processing to cause a parent unit that is the subject of the change in the registration relationship to change a child unit that is the subject of communication when the registration relationship is changed by an operation on the display screen. 1. A computer implemented configuration method, comprising:
a first step of displaying, on a display unit, a display screen including information indicating a registration relationship of a plurality of slave units with respect to a plurality of master units each performing power line carrier communication with a registered slave unit among the plurality of slave units, and an electrical system diagram of an installation location of the plurality of master units and the plurality of slave units, in a changeable manner, the registration relationship;
a second step of performing processing to cause a parent unit that is the subject of the change in the registration relationship to change a child unit with which to communicate when the registration relationship is changed by an operation on the display screen. a first step of displaying, on a display unit, a display screen including information indicating a registration relationship of a plurality of slave units with respect to a plurality of master units each performing power line carrier communication with a registered slave unit among the plurality of slave units, and an electrical system diagram of an installation location of the plurality of master units and the plurality of slave units, in a changeable manner, the registration relationship;
a second step of performing processing to cause a parent unit that is the subject of the change in the registration relationship to change a child unit that is the subject of communication when the registration relationship is changed by an operation on the display screen.

Images