JP2018170882A - Power supply control method, distributed power supply, and control apparatus - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a power supply control method, a distributed power supply, and a control apparatus, capable of probably updating a firmware.SOLUTION: A power supply control method comprises: a step A of updating firmware of a control apparatus that controls a distributed power supply used for stabilizing an electric power system; and a step B of parallel-offing the distributed power supply from the electric power system when a communication blackout time between the distributed power supply and the control apparatus exceeds a timeout time. The step B includes a step B1 that extends the timeout time from a first time out time to a second timeout time longer than the first timeout time.SELECTED DRAWING: Figure 9

Description

  The present invention relates to a power supply control method, a distributed power supply, and a control device.

  2. Description of the Related Art In recent years, in order to maintain the power supply / demand balance of a power system, a technique for suppressing a tidal flow from the power system to the facility or a reverse flow from the facility to the power system is known (for example, Patent Documents 1 and 2). . Specifically, the tidal flow rate or the reverse tidal flow rate is suppressed by transmitting a control message from the power management server to the control device.

JP 2013-169104 A JP 2014-128107 A

  In recent years, studies are underway to use distributed power sources for power system stabilization. For example, such a study relates to a VPP (Virtual Power Plant) using a distributed power source.

  In such a case, there is a need to update the firmware of the distributed power source and the control device, but the firmware of the distributed power source and the firmware of the control device are not always updated at the same time. That is, a case where the firmware version of the distributed power source and the firmware version of the control device are different can be considered.

  SUMMARY An advantage of some aspects of the invention is that it provides a power supply control method, a distributed power supply, and a control device that can appropriately update firmware.

  A power supply control method according to a first feature includes a step A for updating firmware of a control device that controls a distributed power source used for stabilizing a power system, and a communication interruption time between the distributed power source and the control device. Step B of disconnecting the distributed power source from the power system when a time-out period is exceeded. The step B includes a step B1 of extending the timeout period from the first timeout period to a second timeout period longer than the first timeout period during the execution of the step A.

  The distributed power supply according to the second feature is used for stabilizing the power system. The distributed power supply includes a control unit that disconnects the distributed power supply from the power system when a communication interruption time between the distributed power supply and the control device that controls the distributed power supply exceeds a timeout time. The controller extends the timeout period from the first timeout period to a second timeout period longer than the first timeout period during execution of firmware update of the control device that controls the distributed power supply.

  The control device according to the third feature controls the distributed power source used for stabilizing the power system. A control unit that updates firmware of the control device; and a transmission unit that transmits a start message notifying update start of the firmware of the control device to the distributed power source. The distributed power supply is configured to be disconnected from the power system when a communication interruption time between the distributed power supply and the control device exceeds a timeout time. The timeout period is extended from the first timeout period to a second timeout period longer than the first timeout period during execution of the firmware update of the control device.

  According to one aspect, it is possible to provide a power supply control method, a distributed power supply, and a control device that can appropriately update firmware.

FIG. 1 is a diagram illustrating a power supply control system 100 according to the embodiment. FIG. 2 is a diagram illustrating a facility 300 according to the embodiment. FIG. 3 is a diagram illustrating the remote controller 320 according to the embodiment. FIG. 4 is a diagram illustrating the PCS 332 according to the embodiment. FIG. 5 is a diagram illustrating an example of the second protocol according to the embodiment. FIG. 6 is a diagram illustrating an example of the second protocol according to the embodiment. FIG. 7 is a diagram illustrating an example of the second protocol according to the embodiment. FIG. 8 is a diagram illustrating an example of the second protocol according to the embodiment. FIG. 9 is a diagram illustrating a power control method according to the embodiment.

  Embodiments will be described below with reference to the drawings. In the following description of the drawings, the same or similar parts are denoted by the same or similar reference numerals.

  However, it should be noted that the drawings are schematic and ratios of dimensions may be different from actual ones. Therefore, specific dimensions and the like should be determined in consideration of the following description. Moreover, it is a matter of course that portions having different dimensional relationships or ratios are included between the drawings.

[Embodiment]
(Power control system)
Hereinafter, a power supply control system according to the embodiment will be described.

  As shown in FIG. 1, the power supply control system 100 includes a power management server 200 and a facility 300. In FIG. 1, facilities 300 </ b> A to 300 </ b> C are illustrated as the facility 300.

  Each facility 300 is connected to the power system 110. In the following, the flow of power from the power system 110 to the facility 300 is referred to as tidal current, and the flow of power from the facility 300 to the power system 110 is referred to as reverse power flow.

  The power management server 200 and the facility 300 are connected to the network 120. The network 120 may provide a line between the power management server 200 and the facility 300. The network 120 is, for example, the Internet. The network 120 may provide a dedicated line such as a VPN (Virtual Private Network).

  The power management server 200 is a server managed by a business operator such as a power generation business, a power transmission / distribution business, or a retail business.

  The power management server 200 transmits, to the local control device 360 provided in the facility 300, a control message instructing control of a distributed power source (for example, a solar cell device, a storage battery device, and a fuel cell device) provided in the facility 300. . For example, the power management server 200 may transmit a power flow control message (for example, DR; Demand Response) that requests control of power flow, or may transmit a reverse power flow control message that requests control of reverse power flow. Furthermore, the power management server 200 may transmit a power control message for controlling the operating state of the distributed power. The degree of control of the tidal current or the reverse tidal current may be represented by an absolute value (for example, OO kW) or a relative value (for example, OO%). Or the control degree of a tidal current or a reverse tidal current may be represented by two or more levels. The degree of control of power flow or reverse power flow may be represented by a power rate (RTP; Real Time Pricing) determined by the current power supply / demand balance, or a power rate (TOU; Time Of Use) determined by a past power supply / demand balance. May be represented by

  The facility 300 includes a router 500 as shown in FIG. The router 500 is connected to the power management server 200 via the network 120. The router 500 forms a local area network and is connected to each device (for example, the PCS 331, the PCS 332, the PCS 333 load 350, the local control device 360, etc.). In FIG. 2, a solid line indicates a power line, and a dotted line indicates a signal line. The embodiment is not limited to this, and a signal may be transmitted through a power line.

  The facility 300 includes a solar cell 311, a storage battery 312, a fuel cell 313, a hot water supply device 314, a remote controller 320, a PCS 331, a PCS 332, a PCS 333, a distribution board 340, a load 350, and a local control device. 360.

  The solar cell 311 is a device that generates power in response to light reception. The solar cell 311 outputs the generated DC power. The amount of power generated by the solar cell 311 changes according to the amount of solar radiation applied to the solar cell 311.

  The storage battery 312 is a device that stores electric power. The storage battery 312 outputs the accumulated DC power. The storage battery 312 may be a power source used for VPP (Virtual Power Plant).

  The fuel cell 313 is a battery that generates electric power using fuel. The fuel may be, for example, a material containing hydrogen or a material containing alcohol. The fuel cell 313 includes, for example, a solid oxide fuel cell (hereinafter referred to as SOFC), a solid polymer fuel cell (hereinafter referred to as PEFC), a phosphoric acid fuel cell (hereinafter referred to as PAFC). : Phosphoric Acid Fuel Cell) or molten carbonate fuel cell (hereinafter referred to as MCFC: Molten Carbonate Fuel Cell).

  The hot water supply device 314 has a hot water storage tank, and uses the exhaust heat of the fuel cell 313 to maintain or increase the amount of water (hot water) stored in the hot water storage tank, or to store water in the hot water storage tank. Maintain or increase the temperature of (hot water). Such control may be referred to as boiling water stored in the hot water tank.

  The remote controller 320 is an example of a control device that controls a distributed power source used for stabilizing the power system 110. Specifically, the remote controller 320 transmits a command for controlling the distributed power source to the distributed power source in response to a command received from the local control device 360. The remote controller 320 may transmit a command to the distributed power source in response to a user operation. The remote controller 320 may transmit the command to the distributed power source regardless of the command received from the local control device 360 and the user operation. The command may be, for example, a command (Ping command) for confirming whether communication between the remote controller and the distributed power source is maintained. The Ping command is a command that is transmitted periodically.

  The PCS 331 is a power conversion system (PCS; Power Conditioning System) connected to the solar cell 311. The PCS 331 converts DC power from the solar cell 311 into AC power.

  The PCS 332 is a power conversion device connected to the storage battery 312. The PCS 332 converts DC power from the storage battery 312 to AC power, and converts AC power to the storage battery 312 into DC power. The storage battery 312 and the PCS 332 are examples of a distributed power source (storage battery device) used for stabilizing the power system 110.

  The PCS 333 is a power conversion device connected to the fuel cell 313. The PCS 333 converts DC power from the fuel cell 313 into AC power.

  Distribution board 340 is connected to main power line 10L. The distribution board 340 includes a first distribution board 340A and a second distribution board 340B. The first distribution board 340A is connected to the power system 10 via the main power line 10LA. The first distribution board 340A is connected to the solar cell 311 via the PCS 331, is connected to the storage battery 312 via the PCS 332, and is connected to the fuel cell 313 via the PCS 333. The first distribution board 340A supplies the power output from the PCS 331 to PCS 333 and the power supplied from the power system 10 to the second distribution board 340B via the main power line 10LB. The second distribution board 340B distributes the power supplied via the main power line 10LB to each device (here, the load 350 and the local control device 360).

  The load 350 is a device that consumes power supplied through the power line. For example, the load 350 includes devices such as an air conditioner, a lighting device, a refrigerator, and a television. The load 350 may be a single device or may include a plurality of devices.

  The local control device 360 is a device (EMS; Energy Management System) that manages power information indicating power in the facility 300. The power in the facility 300 is the power flowing through the facility 300, the power purchased by the facility 300, or the power sold from the facility 300. Therefore, the local control device 360 manages at least the PCS 331 to PCS 333.

  In the embodiment, communication between the power management server 200 and the local control device 360 is performed according to the first protocol. On the other hand, communication between the local control device 360 and the distributed power supply or the remote controller 320 is performed according to a second protocol different from the first protocol. As the first protocol, for example, a protocol compliant with Open ADR (Automated Demand Response) or a unique dedicated protocol can be used. As the second protocol, for example, a protocol conforming to ECHONET Lite, SEP (Smart Energy Profile) 2.0, KNX, or an original dedicated protocol can be used. Note that the first protocol and the second protocol only need to be different. For example, even if both are unique dedicated protocols, they may be protocols created according to different rules.

  In the embodiment, communication between the remote controller 320 and the storage battery device may be performed according to a protocol different from the first protocol and the second protocol described above. Such a protocol may be, for example, a unique dedicated protocol. Communication between the remote controller 320 and the storage battery device may be performed according to the second protocol.

(Remote controller)
Hereinafter, the remote controller according to the embodiment will be described. As illustrated in FIG. 3, the remote controller 320 includes a communication unit 321 and a control unit 322. The remote controller 320 is an example of a control device that controls a storage battery device used for stabilizing the power system 110.

  The communication unit 321 includes a communication module, and may communicate with the power management server 200 via the network 120. The communication unit 321 performs communication according to the first protocol. For example, the communication unit 321 may receive a message from the power management server 200 according to the first protocol. The communication unit 321 may transmit a message response to the power management server 200 according to the first protocol.

  In the embodiment, the communication unit 321 communicates with the PCS 332. The communication unit 321 performs communication according to a unique dedicated protocol, for example. Here, the communication unit 321 transmits a start message notifying the update start timing of the firmware of the remote controller 320. The communication unit 321 transmits an end message notifying the update end timing of the firmware of the remote controller 320.

  Here, the start message may notify the update start timing of the firmware. Therefore, the start message may be transmitted at the firmware update start timing, or may be transmitted before the firmware update start timing. In the case where the start message is transmitted before the firmware update start timing, the start message may include information indicating the firmware update start timing. The information indicating the update start timing of the firmware may be an absolute time indicating the update start timing itself, or may be a relative time with respect to the start message transmission timing.

  Similarly, the end message may notify the firmware update end timing. Therefore, the end message may be transmitted at the firmware update end timing or may be transmitted before the firmware update end timing. In a case where the end message is transmitted before the firmware update end timing, the end message may include information indicating the firmware update end timing. The information indicating the firmware update end timing may be an absolute time indicating the update end timing itself, or may be a relative time with respect to the end message transmission timing.

  The control unit 322 includes a memory, a CPU, and the like, and controls each component provided in the remote controller 320. Specifically, the control unit 322 instructs the communication unit 321 to transmit a command to the PCS 332 based on a command received from the local control device 360 or a user operation. The control unit 322 may instruct the communication unit 321 to transmit a command to the PCS 332 based on a message received from the power management server 200.

  In the embodiment, the control unit 322 updates the firmware of the remote controller 320 (step A). The control unit 322 may instruct the communication unit 321 to stop sending commands to the PCS 332 during the period when the firmware of the remote controller 320 is being updated. Thereby, a deficiency defect can be suppressed. The firmware update may be performed by a server (for example, the power management server 200) or the local control device 360 connected to the network 120. The firmware update may be performed in response to a periodic inquiry from the remote controller 320 to the server or the local control device 360, or may be performed by the server when firmware update is necessary, and may be performed manually by the user. It may be done at.

(PCS)
Hereinafter, the PCS according to the embodiment will be described. As illustrated in FIG. 4, the PCS 332 includes a communication unit 332-1 and a control unit 332-2. The PCS 332 constitutes a storage battery device used for stabilizing the power system 110.

  The communication unit 332-1 includes a communication module, and communicates with the remote controller 320. The communication unit 332-1 performs communication according to a unique dedicated protocol, for example. Here, the communication unit 332-1 receives a start message that notifies the update start timing of the firmware of the remote controller 320. The communication unit 332-1 receives an end message that notifies the update end timing of the firmware of the remote controller 320.

  The control unit 332-2 includes a memory and a CPU, and controls each component provided in the PCS 332. Specifically, the control unit 332-2 controls conversion from DC power to AC power, conversion from AC power to DC power, and the like based on a command received from the remote controller 320. In other words, the control unit 332-2 controls the operation (charging operation, discharging operation, or standby operation) of the storage battery 312 based on the command received from the remote controller 320.

  In the embodiment, the control unit 332-2 updates the firmware of the PCS 332. The control unit 332-2 may instruct the communication unit 321 to stop sending commands to the remote controller 320 during a period in which the firmware of the PCS 332 is being updated. Thereby, a deficiency defect can be suppressed. The firmware update may be performed by a server (for example, the power management server 200) or the local control device 360 connected to the network 120. The firmware update may be performed in response to a periodic inquiry from the PCS 332 to the server or the local control device 360, or may be performed at the initiative of the server or the local control device 360 when a firmware update is necessary. It may be performed manually by the user.

  The control unit 332-2 disconnects the PCS 332 from the power system 110 when the communication interruption time between the PCS 332 and the remote controller 320 exceeds the timeout time (step B). The disruption of communication may be determined based on, for example, whether or not the above-described Ping command that is periodically transmitted can be received. The disruption of communication may be determined based on, for example, the quality of a command received from the remote controller 320 (for example, SNR; Signal to Noise Ratio).

  While executing the firmware update of the remote controller 320, the control unit 332-2 changes the timeout period from the first timeout period (for example, 10 seconds) to the second timeout period (for example, 1 minute) longer than the first timeout period. (Step B1). That is, the first timeout period is a timeout period applied during a period when the firmware of the remote controller 320 is not updated, and the second timeout period is a period when the firmware of the remote controller 320 is being updated. The timeout period to be applied.

  Here, it is assumed that the timeout time is extended when the firmware of the PCS 332 is updated after the firmware update of the remote controller 320 is executed. However, the embodiment is not limited to this. When the firmware of the remote controller 320 and the PCS 332 is updated at the same time, the timeout time may be extended. Similarly, in the case where the firmware of the PCS 332 is updated before the update of the firmware of the remote controller 320 is performed, the timeout time may be extended.

  The control unit 332-2 may determine whether or not the firmware of the remote controller 320 is being updated based on the start message and the end message. In other words, the control unit 332-2 may extend the timeout period from the first timeout period to the second timeout period based on the start message. Similarly, the control unit 332-2 may shorten the timeout period from the second timeout period to the first timeout period based on the end message.

(Example of second protocol)
Hereinafter, an example of the second protocol according to the embodiment will be described. Here, a case where the second protocol is a protocol conforming to ECHONET Lite is illustrated.

  As shown in FIG. 5, a command for requesting setting of the operation state of the device (hereinafter, SET command M510) includes a header M511, a code M512, and a target property M513. In the embodiment, the SET command M510 is an example of a setting command for instructing each device to set or operate the device, and is a command transmitted from the EMS 160 to the device. The header M511 is information indicating the destination of the SET command M510. The code M512 is information indicating the type of command including the code M512. Here, the code M512 is information indicating that the command including the code M512 is a SET command. The target property M513 includes an information element (property) indicating a setting or operation that the EMS 160 instructs the device.

  As shown in FIG. 6, the command response to the command (hereinafter, SET response command M520) includes a header M521, a code M522, and a response content M523. In the embodiment, the SET response command M520 is an example of a command transmitted from the device to the EMS 160 in response to a command received from the EMS 160.

  The header M521 is information indicating the destination of the SET response command M520. The code M522 is information indicating the type of command including the code M522. Here, the code M522 is information indicating that the command including the code M522 is a SET response command. The response content M523 includes information indicating that the SET command has been received. Such information may be a copy of the property included in the SET command, or may be an acknowledgment (ACK). Such information is not limited to this, and may be a response (Selective ACK) intended to correctly receive only a part of the data.

  As shown in FIG. 7, a command for requesting reporting of device information (hereinafter, GET command M610) includes a header M611, a code M612, and a target property M613. In the embodiment, the GET command M610 is an example of a request command for requesting each device to report device information, and is an example of a command transmitted from the EMS 160 to the device. The header M611 is information indicating the destination of the GET command M610. The code M612 is information indicating the type of command including the code M612. Here, the code M612 is information indicating that the command including the code M612 is a GET command. The target property M613 includes an information element (property) that the EMS 160 requests to report.

  As shown in FIG. 8, the command response to the command (hereinafter, GET response command M620) includes a header M621, a code M622, and a response content M623. In the embodiment, the GET response command M620 is an example of a command transmitted from the device to the EMS 160 in response to a command received from the EMS 160.

  The header M621 is information indicating the destination of the GET response command M620. The code M622 is information indicating the type of command including the code M622. Here, the code M622 is information indicating that the command including the code M622 is a GET response command. The response content M623 includes an information element (property) requested by the GET command.

  Here, the information element (property) may be shared between commands. For example, in the case where the information element is the operation state of the device, the SET command including the operation state as the information element functions as a command that instructs the device to set the operation state. On the other hand, the GET command including the operation state as an information element functions as a command for requesting a report of the operation state of the device.

  Information elements (properties) include information elements used only for SET commands (SET response commands), information elements used only for GET commands (GET response commands), SET commands (SET response commands), and GET commands (GET response commands). Information elements used for both are listed. In addition to the SET command and the GET command, there may be an information notification command (INF command) for autonomously reporting device information from each device.

(Power control method)
Hereinafter, a power control method according to the embodiment will be described.

  As illustrated in FIG. 9, in step S <b> 10, the PCS 332 updates the firmware of the PCS 332. The firmware update may be performed according to a command received from the local control device 360. For example, when the firmware version of the PCS 332 is different from the firmware version of the remote controller 320, the local control device 360 may transmit a command to instruct the PCS 332 to update the firmware to the PCS 332. However, updating the firmware of the PCS 332 may be attempted periodically or manually by the user.

  In step S <b> 11, the remote controller 320 transmits a start message notifying the update start timing of the firmware of the remote controller 320 to the PCS 332.

  In step S <b> 12, the remote controller 320 starts updating the firmware of the remote controller 320. The firmware update may be performed according to a command received from the local control device 360 or may be performed manually by the user.

  In step S13, the PCS 332 extends the timeout time from the first timeout time to the second timeout time.

  In step S <b> 14, the remote controller 320 finishes updating the firmware of the remote controller 320.

  In step S <b> 15, the remote controller 320 transmits an end message notifying the update end timing of the firmware of the remote controller 320 to the PCS 332.

  In step S16, the PCS 332 reduces the timeout time from the second timeout time to the first timeout time.

  Although not particularly mentioned in FIG. 9, the PCS 332 is configured to disconnect the PCS 332 from the power system 110 when the communication interruption time between the PCS 332 and the remote controller 320 exceeds the timeout time.

  FIG. 9 illustrates the case where the start message is transmitted at the update start timing of the PCS 332 firmware. However, the embodiment is not limited to this. The start message may be transmitted in advance before the update start timing of the PCS 332 firmware. Similarly, the case where the end message is transmitted at the update end timing of the PCS 332 firmware is illustrated. However, the embodiment is not limited to this. The end message may be transmitted in advance before the firmware update end timing of the PCS 332. The start message and the end message may be transmitted in one message. One message may include information indicating both the update start timing and the update end timing.

(Function and effect)
In the embodiment, the PCS 332 extends the timeout period from the first timeout period to the second timeout period longer than the first timeout period during execution of the firmware update of the remote controller 320. According to such a configuration, disconnection of the PCS 332 can be suppressed in a period in which communication interruption is predicted in advance (that is, a period in which the firmware of the remote controller 320 is updated). That is, it is possible to appropriately update the firmware while ensuring the user's merit by suppressing the PCS 332 disconnection.

[Other Embodiments]
Although the present invention has been described with reference to the above-described embodiments, it should not be understood that the descriptions and drawings constituting a part of this disclosure limit the present invention. From this disclosure, various alternative embodiments, examples and operational techniques will be apparent to those skilled in the art.

  In the embodiment, the storage battery device (storage battery 312 and PCS 332) is illustrated as a distributed power source used for stabilizing the power system 110. However, the embodiment is not limited to this. The distributed power source used for stabilizing the power system 110 may be a solar cell device (solar cell 311 and PCS 331) or a fuel cell device (fuel cell 313 and PCS 333). Alternatively, the distributed power source used for stabilizing the power system 110 may be a distributed power source that uses natural energy such as wind power or geothermal heat.

  For example, when the distributed power source is a solar cell device, the firmware of the solar cell device may be updated during a period when the solar cell device is not generating power (for example, at night). When the distributed power source is a storage battery device or a fuel cell device, at a timing when the operation mode or the operation state of the storage battery device or the fuel cell device is switched during a period when the solar cell device is not generating power (for example, at night), Updating the firmware of the storage battery device or the fuel cell device may be executed.

  In the embodiment, the remote controller 320 is provided as a control device that controls the storage battery device. However, the embodiment is not limited to this. A remote controller may be provided as a control device that controls the solar cell device or the fuel cell device.

  In the embodiment, the remote controller 320 is exemplified as a control device that controls the distributed power supply. However, the embodiment is not limited to this. The control device that controls the distributed power supply may be a local control device 360 (EMS).

  In the embodiment, the case where the protocol used in the communication between the remote controller 320 and the PCS 332 is a unique dedicated protocol is illustrated. However, the embodiment is not limited to this. The protocol used for communication between the remote controller 320 and the PCS 332 may be the second protocol.

  In the embodiment, each distributed power supply is provided with a PCS individually. However, the embodiment is not limited to this. One PCS may be provided for two or more distributed power sources.

  In the embodiment, the case where the PCS 332 (distributed power supply) and the remote controller 320 (control device) are separate devices is illustrated. However, the embodiment is not limited to this. The first functional block included in the PCS 332 and the second functional block included in the remote controller 320 may be provided in one apparatus. The first functional block and the second functional block may be realized in hardware by different CPUs provided on different boards, or may be realized in hardware by different CPUs provided on the same board, and the same The software may be realized by a CPU. In these cases, “communication”, “transmission”, and “reception” may be appropriately read as “interface”, “output”, “input”, and the like.

  Although not specifically mentioned in the embodiment, the local control device 360 provided in the facility 300 may not necessarily be provided in the facility 300. For example, some of the functions of the local control device 360 may be provided by a cloud server provided on the Internet. That is, it may be considered that the local control device 360 includes a cloud server.

  In the embodiment, the case where the firmware update of the remote controller 320 (control device) is executed after the firmware update of the PCS 332 (distributed power supply) is executed is illustrated. However, the embodiment is not limited to this. The firmware of the remote controller 320 (control device) may be updated at an arbitrary timing. For example, the firmware update of the remote controller 320 (control device) may be performed before the firmware update of the PCS 332 (distributed power supply). Alternatively, the firmware update of the remote controller 320 (control device) may be suspended until the firmware update of the PCS 332 (distributed power supply) is executed.

  DESCRIPTION OF SYMBOLS 10L ... Main power line, 100 ... Power supply control system, 110 ... Power system, 120 ... Network, 200 ... Power management server, 300 ... Facility, 311 ... Solar cell, 312 ... Storage battery, 313 ... Fuel cell, 314 ... Hot water supply device, 320 ... Remote controller, 321 ... Communication part, 322 ... Control part, 331 ... PCS, 332 ... PCS, 332-1 ... Communication part, 332-2 ... Control part, 333 ... PCS, 340 ... Distribution board, 350 ... Load, 360 ... local control device, 500 ... router

Claims (9)

Step A for updating the firmware of the control device that controls the distributed power source used for stabilizing the power system;
A step B of disconnecting the distributed power source from the power system when a disruption time of communication between the distributed power source and the control device exceeds a timeout time;
The step B includes a step B1 of extending the timeout period from the first timeout period to a second timeout period longer than the first timeout period during the execution of the step A.   The power supply control method according to claim 1, wherein the step B1 is performed when the step A is performed after execution of firmware update of the distributed power supply.   3. The power supply control method according to claim 1, wherein the step A includes a step of transmitting a start message for notifying the update start timing of firmware of the control device from the control device to the distributed power supply. 4.   The power supply control method according to claim 3, wherein the step B1 includes a step of extending the timeout time from the first timeout time to the second timeout time based on the start message.   5. The power supply control method according to claim 1, wherein the step A includes a step of transmitting an end message for notifying update end timing of firmware of the control device from the control device to the distributed power source. .   6. The power supply control method according to claim 5, wherein the step B1 includes a step of shortening the timeout period from the second timeout period to the first timeout period based on the end message.   The power supply control method according to claim 1, wherein the distributed power supply is a storage battery device. A distributed power source used for power system stabilization,
A control unit that disconnects the distributed power source from the power system when a communication interruption time between the distributed power source and the control device that controls the distributed power source exceeds a timeout time;
The distributed power supply, wherein the control unit extends the timeout time from a first timeout time to a second timeout time longer than the first timeout time during execution of firmware update of a control device that controls the distributed power supply. A control device for controlling a distributed power source used for stabilizing a power system,
A control unit for updating firmware of the control device;
A transmission unit that transmits a start message to notify the start of firmware update of the control device to the distributed power source,
The distributed power source is configured to be disconnected from the power system when a communication interruption time between the distributed power source and the control device exceeds a timeout time,
The control device, wherein the time-out time is extended from a first time-out time to a second time-out time longer than the first time-out time during execution of firmware update of the control device.

Images