JP7051755B2 - Failure data recording system and failure data transmitter - Google Patents

Description

The present invention relates to a failure data recording system and a failure data transmission device when a failure occurs, such as a power conversion device.

In a power conversion device or the like, when a failure occurs, various operating conditions before and after the failure of the power conversion device are recorded in order to investigate the cause, and the so-called traceback data is used for investigating the cause of the failure. If the power converter is located in a remote location, the traceback data of the power converter may be transferred and obtained using a communication means. However, depending on the failure mode of the power conversion device, the power of the communication device may be rapidly lost, and there is a demand for high-speed transfer of traceback data before the power is lost when a failure occurs.

By the way, as a high-speed communication method, a communication protocol such as UDP (User Datagram Protocol) that does not guarantee the arrival of communication data is known. Japanese Unexamined Patent Publication No. 2008-211682 (Patent Document 1) discloses a communication system in which transmission routes are multiplexed as a technique for enhancing the reliability of data transmission by UDP.

Japanese Unexamined Patent Publication No. 2008-211682

In the communication system described in Patent Document 1, it is shown that transmission order information is added to the UDP packet to be transmitted, and the receiving side transmits a reception completion notification each time the UDP packet is received. ..

However, in the configuration of Patent Document 1, since the transmitting side does not transmit the next UDP packet until the reception completion notification is received, it takes time to transmit one packet, and there is a concern that the transmission efficiency will decrease. Will be done. As a result, there is concern that the high speed, which is an advantage of UDP, will decrease.

The present invention has been made to solve such a problem, and an object thereof is a failure data recording system capable of transferring trace back data of a power converter or the like at high speed while ensuring reliability. And to provide a failure data transmitter.

In one aspect of the invention, the fault data recording system comprises a first device and a second device. The second device is configured to control the first device by transmitting a control command to the first device to the first device. The first device is configured to transmit traceback data of the first device before and after the time of failure to the second device when a failure occurs in the first device. When the failure of the first device is a serious failure, the first device uses the first communication protocol that does not guarantee the arrival of data, and the occurrence of a serious failure including information on the failure type of the serious failure occurs. The data of the operation status of the first device before and after is transmitted as a trace back. The traceback data includes a type 1 packet and a type 2 packet. The first-class packet includes the time when a major failure occurs and bit information of the failure type of the major failure. The second-class packet includes the operation status data of the first device in the collected time unit and a plurality of packets assigned in the time unit in which the consecutive identifiers are collected. When the first device receives the reception completion notification of the first-class packet after transmitting the first-class packet to the second device, or when the number of times the first-class packet is transmitted reaches the first allowable value. If the reception completion notification of the first-class packet is not received, the second-class packet is transmitted to the second device.

According to the present invention, it is possible to provide a failure data recording system and a failure data transmission device capable of transferring trace back data of a power conversion device or the like at high speed while ensuring reliability.

It is a schematic block diagram which shows the whole structure of the failure data recording system which concerns on 1st Embodiment. It is a figure which shows the structural example of the trace back data schematically. It is a block diagram which shows the hardware composition of a main trunk board and a power conversion device. It is a sequence diagram explaining the flow of the processing of the data communication between a main board and a power conversion device. It is a figure which shows the structural example of the UDP packet in 1st Embodiment. It is a figure which shows the configuration example of the reception completion notification packet in 1st Embodiment. It is a partial diagram of the flowchart explaining the processing procedure at the time of transmitting the trace back data when a serious failure occurs in the power conversion apparatus in 1st Embodiment. It is a partial diagram of the flowchart explaining the processing procedure at the time of transmitting the trace back data when a serious failure occurs in the power conversion apparatus in 1st Embodiment. It is a partial diagram of the flowchart explaining the processing procedure at the time of transmitting the trace back data when a serious failure occurs in the power conversion apparatus in 1st Embodiment. It is a partial diagram of the flowchart explaining the processing procedure at the time of transmitting the trace back data when a serious failure occurs in the power conversion apparatus in 1st Embodiment. It is a partial diagram of the flowchart explaining the processing procedure when the trace back data is received by the main trunk board in 1st Embodiment. It is a partial diagram of the flowchart explaining the processing procedure when the trace back data is received in the main trunk board in 1st Embodiment. It is a flowchart explaining the processing procedure when the reception completion notification is received by the power conversion apparatus in 1st Embodiment. It is a figure which shows typically the configuration example of the reception confirmation map of the power conversion apparatus in 1st Embodiment. It is a figure which shows typically the configuration example of the received data map of the main trunk board in 1st Embodiment. It is a partial diagram of the flowchart explaining the processing procedure at the time of transmitting the trace back data when a serious failure occurs in the power conversion apparatus in 2nd Embodiment. It is a partial diagram of the flowchart explaining the processing procedure at the time of transmitting the trace back data when a serious failure occurs in the power conversion apparatus in 2nd Embodiment. It is a partial diagram of the flowchart explaining the processing procedure at the time of transmitting the trace back data when a serious failure occurs in the power conversion apparatus in 2nd Embodiment. It is a partial diagram of the flowchart explaining the processing procedure at the time of transmitting the trace back data when a serious failure occurs in the power conversion apparatus in 2nd Embodiment. It is a partial diagram of the flowchart explaining the processing procedure when the trace back data is received in the main trunk board in 2nd Embodiment. It is a partial diagram of the flowchart explaining the processing procedure when the trace back data is received in the main trunk board in 2nd Embodiment. It is a partial diagram of the flowchart explaining the processing procedure when the trace back data is received in the main trunk board in 2nd Embodiment. It is a partial diagram of the flowchart explaining the processing procedure at the time of transmitting the trace back data when a serious failure occurs in the power conversion apparatus in 3rd Embodiment. It is a partial diagram of the flowchart explaining the processing procedure at the time of transmitting the trace back data when a serious failure occurs in the power conversion apparatus in 3rd Embodiment. It is a schematic block diagram which shows the whole structure of the failure data recording system which concerns on 4th Embodiment.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. In the following, the same or corresponding parts in the figure are designated by the same reference numerals and the explanations will not be repeated in principle.

[First Embodiment]
<Overall configuration of failure data recording system>
FIG. 1 is a schematic block diagram showing an overall configuration of a failure data recording system according to the first embodiment. As shown in FIG. 1, the failure data recording system 100 according to the present embodiment can be applied to, for example, transmission / reception of data between a main board 10 and a power conversion device 30.

With reference to FIG. 1, the failure data recording system 100 includes a main trunk board 10 and a power conversion device 30. The power conversion device 30 has an inverter and is configured to convert DC power supplied from a DC power source (not shown) into AC power and supply it to a load (not shown). For example, an AC motor is applied to the load. The power conversion device 30 is an example of a “first device” and a “fault data transmission device”.

The main board 10 controls the power conversion in the power conversion device 30. In the example of FIG. 1, the main trunk board 10 is configured to control one power conversion device 30, but it is also possible to control a plurality of power conversion devices 30. The main trunk board 10 is an example of a "second device".

The main board 10 and the power conversion device 30 are connected to each other so as to be able to communicate with each other by wire, wireless or a combination thereof. In the example of FIG. 1, the main board 10 and the power conversion device 30 are configured to be capable of transmitting and receiving data in both directions by wireless communication.

Specifically, the main trunk board 10 and the power conversion device 30 are communicated and connected by a plurality of communication paths. In the example of FIG. 1, the main trunk board 10 and the power conversion device 30 are communicated and connected by two communication paths 101 and 102. By multiplexing the communication paths in this way, the transmitting side can transmit the same data to the receiving side via a plurality of communication paths 101 and 102. According to this, even if any one of the plurality of communication paths 101 and 102 fails, it is possible to reliably deliver the data to the receiving side via the other communication path. ..

On the other hand, when the plurality of communication paths 101 and 102 are all normal, the data will be duplicated and delivered to the receiving side via the plurality of communication paths 101 and 102. Therefore, the receiving side is configured to determine the duplication of the received data and discard the duplicated received data. The processing of the received data on the receiving side will be described later.

<Functional configuration of power converter 30>
The power conversion device 30 includes a main circuit 32, an inverter control unit 34, a detection data storage unit 36, a communication control unit 38, communication I / F 40, 42, and a control power supply 44.

The main circuit 32 converts a DC voltage into an AC voltage in response to a control signal from the inverter control unit 34 to drive an AC motor. Specifically, the main circuit 32 has a plurality of switching elements (not shown), and each of the plurality of switching elements is switched in response to a control signal from the inverter control unit 34.

The main circuit 32 is provided with a detector 33 for detecting the state of the main circuit 32. The detector 33 has, as an index indicating the state of the main circuit 32, for example, an alternating current supplied from the main circuit 32 to the AC motor (hereinafter, also referred to as an output current), an output frequency of the main circuit 32, and an alternating current from the main circuit 32. The AC voltage applied to the motor (hereinafter, also referred to as output voltage), the DC voltage input from the DC power supply to the main circuit 32 (hereinafter, also referred to as input voltage), and the temperature of the cooler for cooling the main circuit 32. It is configured to detect (such as the temperature of the refrigerant that cools the main circuit 32 and / or the temperature of the heat sink that dissipates heat from the main circuit 32). The detector 33 outputs the detected value of the state of the main circuit 32 to the inverter control unit 34.

The inverter control unit 34 receives a control command including a rotation speed command value of the AC motor from the main trunk board 10, and also receives a detection value from the detector 33 of the main circuit 32 or rotation from a speed detector connected to the AC motor (not shown). Upon receiving the speed detection value, the operation of the main circuit 32 is controlled so that the AC motor operates according to the rotation speed command value based on the control command and these various detection values.

During the operation of the main circuit 32, the inverter control unit 34 transfers a part or all of the detection value of the detector 33, the internal control value of the inverter control unit 34, the rotation speed detection value of the AC motor, etc. to the communication control unit 38. do. The communication control unit 38 transmits the transferred value to the main trunk board 10 via the communication paths 101 and 102 in a predetermined cycle or by a request from the main trunk board 10.

Further, the inverter control unit 34 is referred to as a part or all values such as a detection value from the detector 33, an internal control value of the inverter control unit 34, and a rotation speed detection value of the AC motor (hereinafter, "operation status numerical data"). The detection data storage unit 36 stores the bit data (hereinafter referred to as “failure type bit data”) representing the failure type generated by the power conversion device 30 (hereinafter referred to as “failure type bit data”) in the detection data storage unit 36 at a predetermined recording cycle. As will be described later, the operation status numerical data and the failure type bit data stored in the detection data storage unit 36 are the behavior of the main circuit 32 before and after the failure occurrence time when the failure occurs in the power conversion device 30. As trace back data for knowing the above, it can be used in the failure search process of the power conversion device 30 performed after the failure occurs.

The inverter control unit 34 determines whether or not a failure has occurred in the power conversion device 30 based on the detection value from the detector 33 or other signals during the operation of the main circuit 32. The failure of the power conversion device 30 is a "serious failure" which is a failure at a level that requires the operation of the main circuit 32 to be stopped immediately, and a "light failure" which is a failure at a level at which the operation of the main circuit 32 can be continued. It is stratified as "failure".

The serious failure is, for example, an overcurrent caused by a short-circuit failure of a plurality of switching elements constituting the main circuit 32.

On the other hand, a minor failure is, for example, an increase in the refrigerant temperature of the main circuit 32 by a predetermined value or more. In such a case, it may be possible to continue the operation of the device by performing the output reduction operation of the main circuit 32.

Since the detection data storage unit 36 has a limited storage capacity, the detection data storage unit 36 erases the above-mentioned operation status numerical data and failure type bit data in order from the oldest data and overwrites them with new data to obtain a predetermined cycle (dT). The Trec data is stored for a predetermined period.

When the detection data storage unit 36 determines that a failure (minor failure or major failure) has occurred in the power conversion device 30, the detection data storage unit 36 stores new data for the recording period Taft after the failure occurrence, which is determined from the failure occurrence. That is, the detection data storage unit 36 stores the operation status numerical data and the failure type bit data of the pre-trigger period Trec-Taft in the recording period Trec as traceback data.

After that, the communication control unit 38 reads out the operation status numerical data and the failure type bit data stored in the detection data storage unit 36 before and after the failure occurrence time, and reads the read data via the communication paths 101 and 102 on the main trunk panel. Send to 10. As described above, since the detection data before and after the failure occurrence time is used for the failure search process of the power conversion device 30, in the following description, the operation status numerical data and the failure type before and after the failure occurrence time as traceback data. Bit data is also referred to as "failure data".

FIG. 2 is a diagram schematically showing a configuration example of failure data (traceback data) stored in the detection data storage unit 36.

In FIG. 2, t1 to tN represent the time when each data is detected. The first failure type, the second failure determination type, the third failure determination type, and the fourth failure determination type are failure type bit data. Here, for example, "0" indicates that a failure of the type has not occurred, and "1" indicates that a failure has occurred.

The first operating status value, the second operating status value, the third operating status value, and the fourth operating status value represent the types of the operating status numerical data. Here, the values A1, B1, C1, and D1 represent the first operating status value, the second operating status value, the third operating status value, and the fourth operating status value, respectively, at time t1. The values A2, B2, C2, and D2 represent the values of the first operating condition value, the second operating condition value, the third operating condition value, and the fourth operating condition value at time t2, respectively. The same applies hereinafter.

Here, for example, the first failure type is an output overcurrent, the second failure type is an output overvoltage, the third failure type is a DC overvoltage, and the fourth failure type is a DC undervoltage. For example, the first operating condition value is the output current, and A1 indicates the output current value at time t1. For example, the second operating condition value is the output voltage, and B1 indicates the output voltage value at time t1.

In FIG. 2, dT is set as the recording cycle of the detection data storage unit 36. The recording period dT is, for example, 0.1 s. The recording cycle may be the same as the control cycle of the power conversion device 30, may be shorter than the control cycle, or may be longer than the control cycle.

In FIG. 2, for the sake of simplification, four types of failure type bit data and four types of operation status numerical data are used, but the present invention is not limited to this, and more types may be used. Further, in FIG. 2, the number of recorded times is set to N points.

Each column of the first failure type, the second failure determination type, the third failure determination type, and the fourth failure determination type indicates the failure type bit data at each time. Each column of the first operation status value, the second operation status value, the third operation status value, and the fourth operation status value shows the numerical data of each operation status at each time.

FIG. 2 shows an example in which the second failure type (for example, output overvoltage) occurs after the time tF-1 and before the time tF. That is, the total number of recording time points is N points, the number of recording time points before failure is F-1, the total recording period Trec is dT × (N-1), and the pre-trigger period is dT × F. That is, the time tF is a time representing a trigger point. Here, N and F are natural numbers, and N is a natural number greater than or equal to F. F is a number representing the number of recording time points from the start of failure recording to the trigger point.

Before the time tF-1, the bit data of all the first failure types, the second failure determination type, the third failure determination type, and the fourth failure determination type is "0". Further, after the time tF, all the bit data of the second failure type are "1". In general, many devices are configured to retain the corresponding failure information until a recovery operation is performed when a serious failure occurs, and this example also follows this.

In general, many devices employ a so-called first fault lock that locks the display of secondary failure information that occurs when a serious failure occurs to prevent confusion. Therefore, also in FIG. 2. Similarly, the bit data other than the first failure type that first occurred after the time tF is set to "0".

By constructing the failure data with the operation status numerical data before and after the failure occurrence time and the failure type bit data in this way, the user can determine whether or not the value of the operation status numerical data changes before and after the failure occurrence and the degree of the change. It is possible to search for the cause of the failure based on.

Returning to FIG. 1, the communication I / F 40, 42 is an interface for communicating with the main trunk board 10, and is, for example, a NIC (Network Interface Card). The communication I / F 40 communicates with the communication I / F 18 of the main trunk board 10 via the communication path 101, and exchanges various data. The communication I / F 42 communicates with the communication I / F 20 of the main trunk board 10 via the communication path 102 to exchange various data.

The communication control unit 38 controls communication between the power conversion device 30 and the main board 10. The communication control unit 38 has two types of communication protocols for communication between the power conversion device 30 and the main board 10, and selects and uses an appropriate communication protocol according to the type of data to be transmitted. Can be done. The first communication protocol is a protocol that does not guarantee that data will reach the destination. The first communication protocol is, for example, UDP (User Datagram Protocol). The second communication protocol is a protocol that guarantees that the data reaches the destination. The second communication protocol is, for example, TCP (Transmission Control Protocol). The communication control unit 38 and the communication I / F 40, 42 are examples of the “communication unit”.

<Functional configuration of the main board 10>
The main trunk board 10 has a control circuit 12, a storage device 14, a communication control unit 16, and communication I / F 18 and 20. The control circuit 12 controls the entire main trunk board 10. The control circuit 12 generates a control command for controlling the power conversion device 30. When the load is an AC motor, the control command includes an operation permission command for the power conversion device 30, an operation stop command, a rotation speed command value for the AC motor, and the like. The control circuit 12 transfers the generated control command to the communication control unit 16. The communication control unit 16 transmits the transferred control command to the power conversion device 30 via the communication paths 101 and 102.

Further, the control circuit 12 receives data such as the output current and the output frequency of the main circuit 32 via the communication paths 101 and 102 while the power conversion device 30 is in operation. Further, when a failure occurs in the power conversion device 30, the control circuit 12 receives the failure data via the communication paths 101 and 102.

The control circuit 12 stores these received data in the storage device 14. Since the storage device 14 is composed of a non-volatile memory, the stored contents are retained even when the power of the main trunk board 10 is turned off. The storage device 14 is, for example, an HDD (Hard Disk Drive).

The communication I / F 18 and 20 are interfaces for communicating with the power conversion device 30, and are, for example, a NIC. The communication I / F 18 communicates with the communication I / F 40 of the power conversion device 30 via the communication path 101, and exchanges various data. The communication I / F 20 communicates with the communication I / F 42 of the power conversion device 30 via the communication path 102 to exchange various data.

The communication control unit 16 controls communication between the main board 10 and the power conversion device 30. Like the communication control unit 38, the communication control unit 16 has the above-mentioned first and second protocols, and selects and uses an appropriate communication protocol according to the type of data to be transmitted or data to be received. be able to.

<Hardware configuration of failure data recording system 100>
FIG. 3 is a block diagram showing a hardware configuration of the main trunk board 10 and the power conversion device 30.

With reference to FIG. 3, the main trunk board 10 has a control device 15 for controlling the entire device, a display unit 58, and an input unit 59. The control device 15 includes a CPU (Central Processing Unit) 50, communication I / Fs 18 and 20 connected to the CPU 50, a memory, and an I / O (Input / Output) interface 56.

The memory includes a ROM (Read Only Memory) 52 which is a memory for storing a program executed by the CPU 50, a RAM (Random Access Memory) 54 which is a memory which is a work area when the program is executed by the CPU 50, and a memory. , HDD as an example of the storage device 14. The main trunk board 10 can be configured to have a function equivalent to that of a general computer.

The I / O interface 56 is an interface for input to the control device 15 or output from the control device 15. A display unit 58 and an input unit 59 are connected to the I / O interface 56. The display unit 58 displays data such as images and texts according to the control of the CPU 50. The display unit 58 is composed of, for example, a liquid crystal display or an organic EL (Electro-Luminescence) display. The input unit 59 receives an operation input from the user and sends a signal indicating the accepted operation to the CPU 50. The input unit 59 is, for example, a mouse, a keyboard, a touch panel, or a controller.

The power conversion device 30 has a main circuit 32, a control device 35 for controlling the main circuit 32, and a control power supply 44 for generating an operating power supply voltage of the control device 35. The control device 35 includes a CPU 60, communication I / F 40, 42 connected to the CPU 60, a memory, and an I / O interface 66. The memory includes a ROM 62, which is a memory for storing a program executed by the CPU 60, and a RAM 64, which is a memory for serving as a work area when the program is executed by the CPU 60. The I / O interface 66 is an interface for input to the main circuit 32 or output from the main circuit 32 (including the detector 33).

<Operation of failure data recording system 100>
Next, the operation of the failure data recording system 100 according to the present embodiment will be described.

FIG. 4 is a sequence diagram illustrating a flow of data communication processing between the main board 10 and the power conversion device 30.

With reference to FIG. 4, when the control power supply 44 is turned on by the process P20 and the operating power supply voltage is supplied to the control device 35, the power conversion device 30 performs the necessary initialization process by the process P21. The power conversion device 30 transmits an initialization signal with a time stamp to the main trunk board 10 via the communication paths 101 and 102 by the communication C10. Here, the initialization process performed in the process P21 also includes initialization of the sequence number and the confirmation flag described later.

When the main board 10 receives the initialization signal, the processing P10 initializes the sequence number and further initializes the received data map. After that, a control command for controlling the power conversion device 30 is generated. The main board 10 transmits the generated control command to the power conversion device 30 via the communication paths 101 and 102 by the communication C12. The control command includes an operation permission command, an operation stop command, a rotation speed command value, and the like of the power conversion device 30.

When the power conversion device 30 receives the control command by the communication C12, the power conversion device 30 controls the power conversion device 30 by the process P22. The control device 35 (inverter control unit 34) controls the main circuit 32 so that the AC motor operates according to the control command based on the control command, the detector 33, and various detected values. During the operation of the main circuit 32, the power conversion device 30 uses the communication C14 to transmit data indicating the state of the power conversion device 30 such as the output current and the output frequency (rotational speed of the AC motor) of the main circuit 32 to the communication path 101. It is transmitted to the main trunk board 10 via 102.

In the power conversion device 30, the operation status numerical data and the failure type bit data are stored in the detection data storage unit 36 by the process P24 during the operation of the main circuit 32. Further, during the operation of the main circuit 32, the inverter control unit 34 determines whether or not a failure has occurred in the power conversion device 30 based on the detection value from the detector 33 or other signals by the process P26. .. If no failure has occurred, the power conversion device 30 repeats the operation of the process P24 from the communication C12.

When it is determined in the process P26 that a minor failure has occurred, the power conversion device 30 reads out the detection data (failure data) before and after the time when the minor failure occurs from the detection data storage unit 36. The power conversion device 30 transmits the read failure data to the main board 10 via the communication paths 101 and 102 by the communication C16.

When the main board 10 receives the failure data, the communication C18 notifies that the reception of the failure data is completed (hereinafter, also referred to as "reception completion notification") by power conversion via the communication paths 101 and 102. It is transmitted to the device 30. Further, the main trunk board 10 stores the received failure data in the storage device 14 by the process P11. According to this, as shown in the process P12, the user can perform verification such as searching for the cause of a minor failure by using the failure data stored in the storage device 14. The main board 10 and the power conversion device 30 continue to operate by the communication C12 and the processing P22 even while the minor failure data is being transmitted by the communication C16 and C18.

The communication C10 to C18 between the main board 10 and the power conversion device 30 described above is performed using TCP (second communication protocol). As described above, by using TCP, it is possible to reliably transmit data to the destination.

In the power conversion device 30, it is determined by the process P30 together with the above-mentioned process P26 whether or not a serious failure has occurred in the power conversion device 30 during the operation of the main circuit 32. When it is determined in the process P30 that a serious failure has occurred, the power conversion device 30 performs a protection interlocking such as stopping the operation of the main circuit 32 in the process P32. Further, the power conversion device 30 reads the detection data (failure data) before and after the occurrence of a serious failure from the detection data storage unit 36 data, and transmits the read failure data to the main board 10 via the communication paths 101 and 102. ..

In addition, for example, the detection data storage unit 36 stores failure data for minor failures so that failure data at the time of major failure can be recorded even if a major failure occurs during transmission of traceback data at the time of minor failure. An area and a failure data storage area for a serious failure can be provided.

The power conversion device 30 according to the present embodiment is configured to transmit failure data to the main trunk board 10 by using UDP (first communication protocol) which is superior in speed to TCP when a serious failure occurs. Further, the power conversion device 30 according to the present embodiment transmits the detected data to the main trunk board 10 using the multiplexed communication paths 101 and 102 to prevent data loss while ensuring high speed.

On the other hand, by multiplexing the communication paths, the same data is duplicated and sent to the main trunk board 10 via different communication paths. Therefore, when all the received failure data in the main board 10 is stored in the storage device 14, the storage area of the storage device 14 is compressed by the duplicate failure data, and as a result, the detection data necessary for failure search is stored. There is concern that it will disappear. Therefore, in addition to the high speed and reliability in the transfer of the failure data, it is necessary to store the failure data in the storage device 14 of the main board 10 without duplication.

In the present embodiment, the power conversion device 30 uses the process P34 to set the time data of the failure occurrence time (failure occurrence time time stamp) and the failure type bit data at the failure occurrence time as one data unit, and sequentially sequentially thereof. Sequence number n + 1, which is a typical identifier, is assigned. Here, n is 0 or a natural number, and if the sequence number has not been reset by initialization, it is the final value of the sequence number at the time of the previous failure occurrence. When the sequence number is reset by the initialization, n = 0.

Further, as shown in the rightmost column of the table in FIG. 2, the power conversion device 30 divides the operation status numerical data into a plurality of recording time data units, and each data unit is a sequence which is a sequential identifier starting from n + 2. Give a number.

Further, the power conversion device 30 creates data that can be transmitted in UDP packet units in the process P36. Here, if necessary, the data unit is subdivided. Then, the first packet, which is a UDP packet to which the sequence number n + 1 is assigned, is transmitted to the main board 10 by the communication C20 via the communication paths 101 and 102. Hereinafter, the UDP packet may be simply referred to as a packet.

FIG. 5 is a diagram showing a configuration of a UDP packet according to the first embodiment. FIG. 5 shows an example in which the operation status numerical data in the recording time unit of the failure data shown in FIG. 2 is divided into two packets. In FIG. 5, the “first packet” means a packet that is first transmitted from the power conversion device 30 to the main trunk board 10 using UDP after the occurrence of a serious failure. The “second packet” means a packet that is secondly transmitted from the power conversion device 30 to the main board 10 using UDP after a serious failure occurs when the packet is not retransmitted. Similarly, the “second N + 1 packet” means a packet transmitted from the power conversion device 30 to the main board 10 using UDP at the 2N + 1th position after the occurrence of a serious failure when the packet is not retransmitted.

Each packet is composed of a header unit, a data unit, and a CRC check unit. The header unit is composed of an Ethernet header unit (ETH), an IP header unit (IPH), and a UDP header unit (UDPH). Since the structure of the header part is the same as that of a general UDP packet, the description thereof will be omitted. Further, since the configuration of the CRC check unit is the same as that of a general UDP packet, the description thereof will be omitted.

The data unit of the first packet is composed of a serious failure flag bit, a sequence number n + 1, a sub-sequence number, a failure occurrence time time stamp tm, and a failure type bit data. The serious failure flag bit is, for example, "1". The serious failure flag bit is a flag for identifying that the UDP packet transmitted from the power conversion device 30 to the main trunk board 10 is a packet for transmitting serious failure data. Instead of the serious failure flab bit, the port number that can be specified on the application in the UDP header may be used for identification.

The sequence number of the first packet is a value of n + 1, where n is the last sequence number at the time of the previous major failure. The sub-sequence number is 1. The time stamp tm of the first packet to be transmitted is the time tF recorded by the detection data storage unit 36 immediately after the occurrence of a serious failure. The failure type bit data of the first packet is the failure type bit data at time tF. The first packet is a packet containing time data and bit data. Since the amount of numerical data included in the first packet is small, it can be configured with the amount of data that does not need to be divided.

The second and subsequent packets are packets for transmitting the operation status numerical data. The data unit of the second and subsequent packets is composed of a serious failure flag bit, a sequence number, a sub-sequence number, and operation status numerical data corresponding to the sequence number.

FIG. 5 shows an example in which the operation status numerical data in the time unit shown in FIG. 2 is divided into two and transmitted as two UDP packets. That is, the packet of the sub-sequence number 1 is a packet of numerical data including the first operation status value and the second operation status value, and the packet of the sub-sequence number 2 is the third operation status value and the fourth operation status value. It is a packet of numerical data including and.

The reason for dividing the operation status numerical data in time units to form a UDP packet is as follows. In UDP, data reception is determined for each UDP packet. Therefore, the shorter the length of a single UDP packet, the higher the reception rate of the UDP packet. Therefore, it may be advantageous to divide the operation status numerical data in time units to shorten the length of one UDP packet, depending on the reliability of the communication path. In FIG. 5, the packet is divided into a packet having data of the first operation status value and the second operation status value and a packet having data of the third operation status value and the fourth operation status value, but the number of divisions is Any predetermined number of divisions may be used.

The major failure flag bits of the second packet and the third packet are the same as those of the first packet. The sequence number n + 2 of the second packet is a serial number from the first packet. The sub-sequence number is "1". This means that it is the first packet obtained by dividing the operation status numerical data in time units into two. Therefore, in the third packet, the sequence number n + 2 is the same value as the first packet, but the sub-sequence number is “2”, which is the second data obtained by dividing the operation status numerical data of the sequence number “2”. Shows.

Further, in FIG. 5, the fourth packet contains the data of the first operation status value and the second operation status value of the sequence number n + 3, and the fifth packet contains the data of the sequence number n + 3. The data of the 3 operation status value and the 4th operation status value are stored. Hereinafter, the same applies to the sixth and subsequent packets. The second N packet has a sequence number n + N + 1 and a sub-sequence number “1”, and contains data of the first operation status value and the second operation status value of the sequence number n + N + 1. The final second N + 1 packet is the sequence number n + N + 1, the sub-sequence number is “2”, and contains the data of the third operation status value and the fourth operation status value of the sequence number n + N + 1.

That is, the final sequence number at the time of the previous failure occurrence is n, the failure data is composed of N recording time points, and the operation status numerical data for each recording time unit (operation status numerical data for each sequence number) is Dd. When dividing into pieces, the sequence number of this failure data starts from n + 1 and ends at n + N + 1, the sub-sequence number starts from 1 and ends at Dd, and the total number of packets when there is no retransmission is Dd × N + 1. It becomes. Here, Dd is a natural number representing the number of divisions.

Returning to FIG. 4, the power conversion device 30 creates the data of the first packet in the process P36, and if necessary, divides one data unit of the operation status numerical data into a plurality of packets as shown in FIG. .. Then, the power conversion device 30 sequentially transmits a plurality of packets to the main board 10 according to the order of the identifiers by using UDP. Specifically, the power conversion device 30 first transmits the first packet (the first packet and the packet having the sequence number n + 1) to the main board 10 by the communication C20.

When the main board 10 receives the first packet (sequence number n + 1), the communication C22 transmits a reception completion notification of the packet to the power conversion device 30. Further, the main trunk board 10 restores the data included in the first received packet by the process P14 and stores it in the storage device 14.

After transmitting the first packet (sequence number n + 1) by the communication C20, the power conversion device 30 is in a state of waiting for reception of the reception completion notification from the main board 10. At this time, the power conversion device 30 uses a timer built in the communication control unit 38 to measure the elapsed time from the transmission time of the first packet. In the process P38, it is determined whether or not the reception completion notification is received within the reference time (set time 1) from the transmission time of the first packet based on the timed value of the timer. When the reception completion notification is received within the reference time, the power conversion device 30 transmits the second packet (sequence number n + 2) to the main board 10 by the communication C24.

If the reception completion notification is not received within the reference time from the transmission time of the first packet, the power conversion device 30 transmits the first packet to the main board 10 again and waits until the reception completion notification is received. repeat. However, when the reception completion notification is not received even if the number of times the first packet is transmitted reaches the first allowable value (set number of times 1), the power conversion device 30 gives up the transmission of the first packet and the second packet. Subsequent transmission of failure data (sequence number n + 2 or later) is performed. In addition, Dd packets, which is a predetermined number, are transmitted without confirmation of reception.

When the main board 10 receives the packet of the second packet (sequence number n + 2), the communication C26 transmits a reception completion notification of the packet to the power conversion device 30. The main board 10 restores the failure data included in the received second packet by the process P16 and stores it in the storage device 14.

FIG. 6 is a diagram showing a configuration example of a packet when the reception completion notification according to the first embodiment is transmitted as a UDP packet.

Each reception completion notification packet is composed of a header unit, a data unit, and a CRC check unit. Since the configuration of the header part and the CRC check part is the same as that of a general UDP packet, the description thereof will be omitted.

The data part of the reception completion notification packet is composed of a serious failure reception flag bit, a sequence number, and a sub-sequence number. The serious failure reception flag bit is, for example, "1". The serious failure reception flag bit is a flag for identifying that the UDP packet transmitted from the main trunk board 10 to the power conversion device 30 is a packet for transmitting a reception completion notification. Instead of the serious failure flab bit, the port number that can be specified on the application in the UDP header may be used for identification. The sequence number and sub-sequence number of the reception completion notification are the same numbers as those of the received failure data packet of the serious failure.

In the power conversion device 30, the processing P40 receives the reception completion notification for each packet within the reference time (set time 2) from the transmission time of each packet of the second and subsequent Dd packets transmitted by the communication C24. Whether or not it is determined. If the reception completion notification is not received within the reference time (set time 2), only the packet for which the reception completion notification has not been received is retransmitted. In this way, reception confirmation and retransmission are repeated. However, if the reception completion notification is not received even if the number of transmissions of the same data packet reaches the second allowable number (setting number 2), the transmission of the data is abandoned.

When either the reception completion notification is received or the reception completion notification is completed for the series of Dd second and subsequent packets transmitted by the processing P40, the power conversion device 30 completes a series of Dd with the next sequence number. The packets are transmitted to the main board 10 in the same manner as the communication C24.

When the main board 10 receives a packet, it transmits a reception completion notification of the packet to the power conversion device 30 in the same manner as the communication C26. Similar to the processing P16, the main trunk board 10 restores the failure data included in the received packet and stores it in the storage device 14. Similar to the processing P40, the power conversion device 30 determines whether or not reception is confirmed for each packet, and retransmits the packet if necessary. By repeating the above, the power conversion device 30 can transmit all the failure data to the main board 10.

In the main trunk board 10 that has received the packet, the detection data included in the received packet is sequentially stored in the storage device 14 by the processes P14, P16, .... However, in the processes P14, P16, ..., Duplicate of the received packets is determined based on the identifier. When a duplicate packet is received, the duplicate packet is discarded. As a result, after receiving N packets, as shown in the process P18, the user can perform verification such as searching for the cause of the serious failure by using the failure data stored in the storage device 14.

In the power conversion device 30, when the restoration process is performed by the process P42, the power conversion device 30 can be operated again. When the power conversion device 30 causes a serious failure again without the control power of the power conversion device 30 being turned off by this recovery measure or the like, the previous serious failure is made for a plurality of packets constituting the failure data. Sequence numbers are assigned sequentially from the last sequence number (n + N + 1) generated at the time of occurrence.

7 to 10 are flowcharts illustrating a processing procedure for transmitting failure data when a serious failure occurs in the power conversion device 30. The control processes shown in FIGS. 7 to 10 can be executed by the inverter control unit 34 and the communication control unit 38. It should be noted that FIGS. 7 to 10 are flowcharts in the case where the failure data in the recording time unit is divided into Dd packets and transmitted by UDP.

With reference to FIG. 7, the inverter control unit 34 determines in step S001 whether or not a serious failure has occurred in the power conversion device 30 by the detection data from the detector 33 or other failure detecting means. If it is determined that a serious failure has occurred (YES in S001), the process proceeds to step S002 and subsequent steps. If no serious failure has occurred (NO in S001), the transmission process in step S002 and subsequent steps is not started.

When a serious failure occurs (YES in S001), the inverter control unit 34 performs necessary protection interlocking measures (for example, stopping the operation of the main circuit 32) according to the failure type in step S002. Further, in step S003, the inverter control unit 34 reads out the detection data (failure data) before and after the time when the serious failure occurs from the detection data stored in the detection data storage unit 36, and transfers the detection data to the communication control unit 38.

In step S004, the communication control unit 38 searches the failure type bit data in ascending order in order to specify the time when the serious failure occurs, and the failure bit indicating the serious failure is first set to "1". The third time tf is set as the time data of the first packet.

In step S005, the communication control unit 38 sets the failure type bit data at time tf as the failure type bit data of the first packet.

In step S006, the communication control unit 38 sets the sequence number Sq of the first packet to n + 1. Here, n is the sequence number that was last transmitted when the power conversion device 30 had a serious failure last time. n is 0 or a natural number. When the sequence number, which will be described separately, is initialized, n becomes 0. Further, the sub-sequence number of the first packet is 1. If necessary, the sub-sequence number of the first packet may be omitted.

In step S007, the communication control unit 38 assigns operation status numerical data at the same recording time as one data unit, and assigns sequence numbers in ascending order from n + 2 in the recording time unit. When the number of recording times of the operation status numerical data is N, the sequence number Sq is assigned from n + 2 to n + N + 1.

In step S008, the communication control unit 38 divides one data unit into transmission units in UDP having a predetermined number of divisions Dd, and assigns a sub-sequence number from 1 to Dd to one sequence number. , Create the data of the second Dd × N + 1 packet from the second packet. Here, Dd is a natural number.

With reference to FIG. 8, the communication control unit 38 sets the transmission count counter Cp1 of the first packet to 1 in step S009.

In step S010, the communication control unit 38 transmits the first packet having the sequence number n + 1 to the main trunk board 10 via the communication paths 101 and 102 using UDP.

In step S011, the communication control unit 38 resets the timer T for measuring the elapsed time of the first packet in order to measure the elapsed time since the transmission of the first packet. The timer T measures the elapsed time from the execution of step S011.

In step S012, the communication control unit 38 checks the confirmation flag in which the sequence number of the reception confirmation map is n + 1, and determines whether or not the reception completion notification of the first packet has been received. When the reception completion notification of the first packet is received (YES in step S012), the process proceeds to step S016 shown in FIG. If the reception completion notification of the first packet has not been received (NO in step S012), the process proceeds to step 013. The writing to the confirmation flag of the reception confirmation map will be described later.

The communication control unit 38 determines in step S013 whether or not the time counting time by the timer T is set time 1 or more. If the time counting time of the timer T is less than the set time 1 (NO in S013), the communication control unit 38 returns the process to step S012.

On the other hand, when the time counting time of the timer T exceeds the set time 1 (YES in S013), the communication control unit 38 proceeds to step S014, and the number of times the first packet of the sequence number “n + 1” is transmitted is less than the set number of times 1. It is determined whether or not it is. If the number of transmissions is less than 1 (NO in S014), the communication control unit 38 increases the value of the transmission number counter Cp1 of the first packet by one in step S015. The communication control unit 38 further proceeds to step S010, and executes the processing after step S010 again. For example, the number of settings 1 is 3.

On the other hand, when the number of transmissions reaches an allowable value (YES in S014), the communication control unit 38 does not perform retransmission in step S010, gives up reception confirmation, and proceeds to step S015A. In step S015A, the communication control unit 38 sets the abandonment flag of the sequence number n + 1 and the sub-sequence number 1 of the reception confirmation map to 1, and proceeds to step S016 of FIG.

With reference to FIG. 9, the communication control unit 38 sets the counter Np to n + 2 in step S016. The counter Np represents the sequence number of the operation status numerical data unit in the unit of recording time to be transmitted next in the divided failure data of FIG.

The communication control unit 38 performs the following processing in step S017.
(1) The data of the transmission count counters Cpf (1) to FCpf (Dd) are set to 1.
(2) Set the sub-sequence number counter Cc to 1.

This is a kind of initialization process for each Dd piece for transmitting the operation status data for each time unit divided into Dd pieces as a UDP packet.

The loop composed of steps S018 to 021 is a loop that repeats Dd times for transmitting data in time units divided into Dd pieces.

Next, in step S018, the communication control unit 38 transmits the packets of the sequence number Np and the sub-sequence number Cc to the main trunk board 10 by UDP. In the first loop, since Np = n + 2 and Cc = 1, packets having sequence number n + 2 and sub-sequence number 1 are transmitted. That is, the second packet in FIG. 5 is transmitted.

Next, in step S019, the communication control unit 38 resets the elapsed time timer T (Cc) in order to measure the elapsed time since the packets of the sequence number Np and the sub-sequence number Cc are transmitted. Since Cc = 1 in the first loop, the timer T (1) measures the elapsed time from transmitting the second packet having the sequence number n + 2 and the sub-sequence number 1. Further, in the second loop, since Cc = 2, the timer T (2) measures the elapsed time from transmitting the third packet having the sequence number n + 2 and the sub-sequence number 2. The same applies hereinafter.

In step S020, the communication control unit 38 determines whether or not the sub-sequence number counter Cc is equal to or greater than the maximum value Dd of the sub-sequence number. When the sub-sequence number counter Cc is equal to or greater than the maximum value Dd of the sub-sequence number (YES in step S020), the communication control unit 38 is the sequence number Np and the first transmission of the packet from the sub-sequence numbers 1 to Dd is performed. It is determined that the process has been completed, and the process proceeds to step S022 in FIG. When the sub-sequence number counter Cc is less than the maximum value Dd of the sub-sequence number (NO in step S020), the communication control unit 38 proceeds to step S021, increases the value of the sub-sequence number counter Cc by one, and then increases the value of the sub-sequence number counter Cc by one. The process proceeds to step S018. In this way, packets with the same sequence number but different sub-sequence numbers are sequentially transmitted.

With reference to FIG. 10, the communication control unit 38 sets the sub-sequence number confirmation counter Cc of the reception confirmation map to 1 in step 022, and proceeds to step S023. In step S023, it is confirmed whether or not the confirmation flag of the sequence number Np and the sub-sequence number Cc is “1” on the reception confirmation map.

When the confirmation flag is "1" (YES in step S023), the communication control unit 38 determines that the packet of the sequence number Np and the sub-sequence number Cc has been received by the main trunk board 10, and shifts to step S031. When the confirmation flag is not "1" (NO in step S023), the communication control unit 38 determines that the packet of the sequence number Np and the sub-sequence number Cc has not been received by the main trunk board 10, and proceeds to step S024. ..

In step S024, the communication control unit 38 confirms whether or not the abandonment flag of the sequence number Np and the sub-sequence number Cc is “1” on the reception confirmation map. When the abandonment flag is "1" (YES in step S024), the communication control unit 38 determines that the packet of the sequence number Np and the sub-sequence number Cc is a packet that has abandoned retransmission to the main trunk board 10. , Move to step S031. If the abandonment flag is not "1" (NO in step S024), the process proceeds to step S025.

In step S025, the communication control unit 38 confirms whether or not the timer T (Cc) has a set value of 2 or more. That is, it is determined whether or not the elapsed time from transmitting the packet of the sequence number Np and the sub-sequence number Cc has elapsed the set value 2 or more. If the timer T (Cc) is less than the set value 2 (NO in step S025), the process proceeds to step S030. When the timer T (Cc) is set value 2 or more (YES in step S025), the process proceeds to step S026.

In step S026, the communication control unit 38 confirms whether or not the transmission count counter Cpf (Cc) has a set count of 2 or more. That is, it is determined whether or not the number of transmissions of the packets of the sequence number Np and the sub-sequence number Cc is the set number of times 2 or more. When the transmission count counter Cpf (Cc) is less than the set count 2 (NO in step S026), the process proceeds to step S28. When the transmission count counter Cpf (Cc) has a set count of 2 or more (YES in step S026), the process proceeds to step S027, and the abandonment flag of the sequence number Np and the sub-sequence number Cc of the reception confirmation map is set to “1”. Further, the process proceeds to step S030.

In step S028, the communication control unit 38 retransmits the packet of the sequence number Np and the sub-sequence number Cc to the main trunk board 10 by UDP. Further, in step S029, the communication control unit 38 resets the timer T (Cc) in order to measure the elapsed time after transmitting the packet of the sequence number Np and the sub-sequence number Cc. Further, in step S029, the value of the transmission count counter Cpf (Cc) is incremented by one.

In step S030, the communication control unit 38 determines whether or not the sub-sequence number counter Cc is equal to or greater than the maximum value Dd of the sub-sequence number. When the sub-sequence number counter Cc is equal to or greater than the maximum value Dd of the sub-sequence number (YES in step S030), the process proceeds to step S022 and the sub-sequence number is set to 1. When the sub-sequence counter Cd is less than the maximum value Dd of the sub-sequence number (NO in step S030), the communication control unit 38 proceeds to step S032, increases the value of the sub-sequence number counter Cc by one, and then steps. Move to S023.

In step S031, the communication control unit 38 confirms the reception confirmation map from the sub-sequence number 1 to the sub-sequence number Dd of the sequence number Np. The communication control unit 38 confirms that either the confirmation flag or the abandonment flag is "1" for each packet from the sub-sequence number 1 to the sub-sequence number Dd of the sequence number Np. When either the confirmation flag or the abandonment flag is "1" in the reception confirmation map of a certain packet, it means that the reception of the packet is confirmed or abandoned. Therefore, in step S031, for each packet from the sub-sequence number 1 to the sub-sequence number Dd of the sequence number Np, one of the confirmation flag and the abandonment flag is "1", that is, the sequence number Np. It means that the reception confirmation or the transmission abandonment has been confirmed for the Dd packets constituting the above.

In step S031, the communication control unit 38 sets neither the confirmation flag nor the abandonment flag to "1" for each packet from the sub-sequence number 1 to the sub-sequence number Dd of the sequence number Np (step S031). NO), the process proceeds to step S030. When either the confirmation flag or the abandonment flag is "1" for each packet from the sub-sequence number 1 to the sub-sequence number Dd of the sequence number Np (YES in step S031), the sequence number Np is set. Assuming that the reception confirmation or the transmission abandonment of all the constituent packets is confirmed, the process proceeds to step S33.

In step S033, the communication control unit 38 determines whether the sequence number Np is equal to or greater than the number obtained by adding the recording time points N and 1 of the recorder to the last sequence number n of the previous time. That is, the packet constituting the data of all the sequence numbers assigned in this serious failure is transmitted, and it is determined whether the reception completion confirmation or the reception completion confirmation is abandoned.

When the sequence number Np is less than n + N + 1 (NO in step S031), the communication control unit 38 determines that there is a sequence number that has not been confirmed, proceeds to step S034, adds 1 to the sequence number Np, and adds 1. Return to step S017. When the sequence number Np is n + N + 1 or more (YES in step S033), the communication control unit 38 determines that the confirmation is completed, and proceeds to step S035.

In step S035, the communication control unit 38 replaces the last sequence number n of the previous time with the sequence number Np (that is, n + N + 1) which is the last sequence number transmitted, and ends.

11 and 12 are flowcharts illustrating a processing procedure for receiving failure data in the main trunk board 10 when a serious failure occurs in the power conversion device 30. The control process shown in FIGS. 11 and 12 can be executed by the control circuit 12 and the communication control unit 16 in the main trunk board 10.

With reference to FIG. 11, the communication control unit 16 determines in step S041 whether or not a UDP packet of failure data of a serious failure has been received from the power conversion device 30. Whether or not the data is a serious failure is determined by the serious failure flag bit of the UDP packet. If the UDP packet of the serious failure is not received (NO in S041), the processing after step S042 is not started.

When a packet of the failure data of the serious failure is received from the power conversion device 30 (YES in S041), the communication control unit 16 receives the failure data of the serious failure first received by the power conversion device 30 after the recovery procedure in step S042. Check the serious failure reception flag to determine whether it is a packet. If the serious failure reception flag is not "0" (NO in step S042), the serious failure signal has already been received, so the process proceeds to step S050.

When the serious failure reception flag is "0" (YES in step S042), the process proceeds to step S043. The communication control unit 16 resets the time-out detection timer T10 in step S043, starts the measurement of the serious failure data reception timeout timer T10 from the power conversion device 30 on the main board 10, and proceeds to step S044. Further, in step S044, the serious failure reception flag is set to "1", and the process proceeds to step S045.

In step S045, the main trunk board 10 determines that the power conversion device 30 is a serious failure, implements the minimum protection interlocking measure if necessary, and proceeds to step S050.

In step S050, the main board 10 reads the sequence number L and the sub-sequence number Lsub of the received UDP packet, and in step S051 of FIG. 12, determines whether or not the sequence number L matches n + 1. Here, n corresponds to the sequence number of the last received UDP packet when a serious failure occurred in the power conversion device 30 last time.

With reference to FIG. 12, when the sequence number L matches n + 1 (YES in step S051), the main board 10 determines that the received UDP packet is the first packet described above, and proceeds to step S052. .. When the sequence number L does not match n + 1 (NO in step S051), the main board 10 determines that the received UDP packet is a packet after the second packet, and proceeds to step S061.

In step S052, the main board 10 confirms whether or not the reception flag of the sequence number L is 0 in the reception data map. If the reception flag is not 0 (NO in step S052), it is determined that the data of the sequence number L has already been received (data duplication), and the process proceeds to step S056.

When the reception flag is 0 (YES in step S052), the main board 10 proceeds to step S053, sets the reception flag of sequence number L (that is, n + 1) to 1, and further proceeds to step S054.

In step S054, the main trunk board 10 determines the type of a serious failure from the content of the failure bit included in the received UDP packet, and the necessary protection interlocking (for example, for example) to be performed by the main trunk board 10 according to the type of the serious failure. (Relocation of load sharing to power conversion devices other than the power conversion device 30) is performed. Here, F is the number of recording time points of the failure data from the start of recording to the trigger point, as shown in FIG. Further, tF is time data set in the packet (first packet) having the sequence number n + 1.

(1) The time data of the sequence number n + 2 is set to tF-dT × (F-1), and the failure data is restored to the storage device 14 as a value obtained by adding dT to the increase of the sequence number by 1 to the sequence number n + N + 1. Remember.

(2) All the failure type bit data from the time tF-dT × (F-1) to the time tF-dT are set to 0, and the data is restored to the storage device 14 as failure data.

(3) The failure type bit data of the sequence number n + 2 is restored and stored in the storage device 14 as the failure type bit data from the time tF to the time tF + dT × (NF).

By doing the above, the storage device 14 can restore the same failure type bit data as the failure recording bit data shown in FIG.

Next, in step S056, the main trunk board 10 transmits a reception completion notification of the received sequence number L (that is, sequence number n + 1) to the power conversion device 30. This corresponds to the communication C22 in FIG. After completing step S056, the main trunk board 10 shifts to step S071.

In step S061, the main trunk board 10 confirms whether or not the reception flag of the received sequence number L and the sub-sequence number Lsub is 0. When the reception flag is not 0 (NO in step S061), it is determined that the data of the sequence number L and the sub-sequence number Lsub have already been received (data duplication), and the process proceeds to step S064.

When the reception flag is 0 (YES in step S061), the main board 10 proceeds to step S062, sets the reception flag of the sequence number L and the sub-sequence number Lsub to 1, and further proceeds to step S063.

In step S063, the main board 10 determines the type of numerical data from the sub-sequence number and data sequence of the received UDP packet, and records it as the operation status numerical data of the corresponding sequence number L of the storage device 14. .. That is, when the sequence number L = n + 1 + K, it is restored and stored in the storage device 14 as the operation status numerical data of the corresponding type of time tF + dT × (K−F). Here, K is an integer from 1 to N. By repeating the process of step S063, the operation status numerical data of FIG. 2 can be restored to the storage device 14.

Next, the main trunk board 10 transmits the reception completion notification of the sequence number L and the sub-sequence number Lsub received in step S064 to the power conversion device 30. This corresponds to the communication C26 in FIG. After completing step S064, the main trunk board 10 shifts to step S071.

In step S071, the main board 10 determines whether or not the reception flag of the sequence number n + 1 of the reception data map and all the flags of the sequence numbers n + 2 to n + N + 1 and the sub-sequence numbers 1 to Dd are 1. When all the reception flags are 1 (YES in step S071), the process proceeds to step S073. If all the reception flags are not 1 (NO in step S071), the process proceeds to step S072.

In step S072, the main trunk board 10 determines whether or not the time-out detection timer T10 exceeds the predetermined set time 10. When the time-out detection timer T10 exceeds the set time 10 (YES in step S072), the main trunk board 10 determines that the serious failure reception process has timed out, and proceeds to step S073. If the time-out detection timer T10 does not exceed the set time 10 (NO in step S072), the serious failure data reception process is terminated because it waits until the next UDP packet is received. The set time 10 can be set in consideration of the amount of failure data transmitted from the power conversion device 30 to the main board 10 and the communication speed.

In step S073, the main trunk board 10 records the received data map in the storage device 14. By recording the received data map in the storage device 14, it becomes clear which part of the failure data is missing, the failure search in the process P18 shown in FIG. 4 becomes easy, and the missing part is timed if necessary. It is also possible to interpolate from the data before and after.

Next, in step S074, the main board 10 sets the serious failure flag of the power conversion device 30 to 0, and further, in step S075, the value of the final sequence number at the time of the previous serious failure is set to the value of the final sequence number in this serious failure. Update to the final sequence number n + 1 + N. This completes the serious failure data reception process. The processing after step S073 is executed when the timer T10 exceeds the set time 10 even if the packet of the failure data of the serious failure is not received.

FIG. 13 is a flowchart showing a process when the power conversion device 30 receives a reception completion notification from the main board 10. The control process shown in FIG. 13 can be executed by the inverter control unit 34 and the communication control unit 38.

When the power conversion device 30 receives the UDP packet from the main board 10, it determines in step S101 whether or not the packet is a reception completion notification. This determination can be made by using the above-mentioned serious failure reception flag bit or the like. If the UDP packet of the reception completion notification has not been received (NO in S101), the processing after step S102 is not started.

When the reception completion notification is received from the main trunk board 10 (YES in S101), the communication control unit 16 reads the sequence number and the sub-sequence number included in the reception completion notification in step S102. Next, in step S103, the power conversion device 30 sets the confirmation flag corresponding to the sequence number and the sub-sequence number read in step S102 of the reception confirmation map to 1. This completes the reception confirmation process of the power conversion device 30.

<Reception confirmation map>
FIG. 14 is a diagram showing a configuration image of a reception confirmation map of the communication control unit 38 of the power conversion device 30. The reception confirmation map has a confirmation flag unit indicating whether or not the reception completion notification has been received and an abandonment flag unit indicating that the reception of the reception completion notification has been abandoned for the sequence number and the sub-sequence number corresponding to the address. It consists of.

In the initialization process of the process P21 shown in FIG. 4, the reception confirmation map is initialized, and the confirmation flag and the abandonment flag are all cleared to “0”. Then, in step S103 shown in FIG. 13, "1" is written in the confirmation flag of the corresponding sequence number and sub-sequence number.

Further, in step S015A shown in FIG. 8 and step S027 shown in FIG. 10, "1" is written in the abandonment flag. The line before n represents the state of the flag at the time of the past major failure up to the previous time, and n + 1 to n + 1 + N represent the state of the flag at the time of the latest major failure. The example of FIG. 14 shows a situation in which no serious failure has occurred after the recovery from the previous serious failure.

FIG. 15 is a diagram showing a configuration image of a received data map of the main trunk board 10. The reception confirmation map consists of a flag unit indicating whether or not the UDP packet has been received for the sequence number and the sub-sequence number corresponding to the address, so to speak.

When the UDP packet is received, "1" is written in the flag portion of the sequence number and the sub-sequence number in steps S053 and S062 of FIG. The received data map is initialized by the procedure P10 in FIG. 4, that is, the values of the flag portions are all "0".

As described above, according to the first embodiment, the power conversion device uses the failure type bit data, which is the most important data indicating the time and the failure type at the time of the failure, as the first UDP packet at the time of the failure. Since the data is transmitted from 30 to the main board 10, even if the power supply of the communication device of the power conversion device 30 is lost during the traceback data transmission, the probability that the failure search can be performed is high.

Further, the operation status numerical data recorded in the detection data storage unit at the same time is divided into Dd packets, which are once continuously transmitted from the power conversion device 30 as one packet group, and then reception confirmation. Is performed, and only packets for which reception confirmation cannot be obtained are retransmitted, and the number of times of waiting for reception confirmation is reduced, so that traceback data can be transmitted at high speed.

Further, in the main board 10, UDP packets having duplicate data can be discarded and even lost UDP data can be determined, so that highly reliable traceback data can be obtained without squeezing the storage area. can.

The first packet is an example of a "first-class packet", and the second and subsequent packets are an example of a "second-class packet".

[Second Embodiment]
As a second embodiment of the present invention, a flowchart on the power conversion device 30 side is shown for a case where the capacity of the failure data in the recording time unit is relatively small and the failure data in the recording time unit is transmitted in one UDP packet. 16 to 19 show. The description of common points with the first embodiment such as the hardware configuration is omitted, and only the changes will be described below. Further, FIGS. 20 and 21 show flowcharts on the main board 10 side.

In FIG. 16, steps S001 to S007 are the same as in FIG. 7. In FIG. 16, instead of step S008 in FIG. 7, step S008A is performed. In step S008A, the communication control unit 38 creates data for the second N + 1 packet from the second packet, with one data unit to which the sequence number is assigned in step S007 as one UDP packet unit. Then, the process proceeds to step S009 in FIG.

In FIG. 17, steps S009 to S015 are the same as in FIG. In FIG. 17, instead of step S015A in FIG. 8, step S015B is used. The UDP packet transmitted in step S10 may have a configuration in which the sequence number is omitted from the configuration shown in FIG. 5A.

In FIG. 17, in step S015B, the abandonment flag of the sequence number n + 1 of the reception confirmation map is set to 1, and the process proceeds to step S016A of FIG. 18 (there is no sub-sequence number).

In FIG. 18, instead of steps S016, S017, and S018 in FIG. 9, steps S016A, S017A, and step S018A are used. In step S016A, the sequence number counter Np = n + 1. Next, the communication control unit 38 performs the following in step S017A.
(1) The data of the transmission count counters Cpf (1) to Cpf (Dd) are set to 1.
(2) Set the number counter Cc to 1.

The loop composed of steps S018A to 021A has a continuous packet set value Dd2 in order to continuously transmit two Dd data in a time unit from sequence number Np + 1 to sequence number Np + Dd2 without confirming reception. It is a loop that repeats many times.

In step S018A, the communication control unit 38 transmits the packet of the sequence number Np + Cc to the main trunk board 10 by UDP. In the first loop, Np = n + 1 and Cc = 1, so the packet with sequence number n + 2 is transmitted. Here, Dd2 is a natural number. The UDP packet transmitted in step S18A may have a configuration in which the sub-sequence number is omitted from the configuration shown in FIGS. 5 (b) and 5 (c).

In step S019A, the communication control unit 38 resets the timer T (Cc) in order to measure the elapsed time since the packet having the sequence number Np + Cc is transmitted. In the first loop, the timer T (1) measures the elapsed time since the second packet having the sequence number n + 2 is transmitted. Further, in the second loop, the timer T (2) measures the elapsed time after transmitting the third packet having the sequence number n + 3. The same applies hereinafter.

The communication control unit 38 determines in step S020A whether or not the counter Cc is equal to or higher than the continuous packet set value Dd2. When the counter Cc is the continuous packet set value Dd2 or more (YES in step S020A), the communication control unit 38 determines that the first transmission of the packet from the sequence number Np + 1 to the sequence number Np + Dd2 is completed, and FIG. The process proceeds to step S022A.

If the counter Cc is less than the continuous packet set value Dd (NO in step S020A), the process proceeds to step S021A, the value of the counter Cc is increased by one, and then the process proceeds to step S018A. In this way, the communication control unit 38 sequentially transmits UDP packets from the sequence number Np + 1 to the sequence number Np + Dd2.

With reference to FIG. 19, the communication control unit 38 sets the counter Cc to 1 for confirmation of the reception confirmation map in step S022A, and proceeds to step S023A. In step S023A, it is confirmed whether or not the confirmation flag of the sequence number Np + Cc is 1 on the reception confirmation map. When the confirmation flag is 1 (YES in step S023A), it is determined that the packet having the sequence number Np + Cc has been received by the main board 10, and the process proceeds to step S031A. If the confirmation flag is not "1" (NO in step S023A), it is determined that the packet with the sequence number Np + Cc has not been received by the main trunk board 10, and the process proceeds to step S024A.

In step S024A, the communication control unit 38 confirms whether or not the abandonment flag of the sequence number Np + Cc is “1” on the reception confirmation map. When the abandonment flag is "1" (YES in step S024A), the communication control unit 38 determines that the packet having the sequence number Np + Cc is a packet that has abandoned retransmission to the main board 10, and shifts to step S031A. do. If the abandonment flag is not "1" (NO in step S024A), the process proceeds to step S025A.

In step S025A, the communication control unit 38 confirms whether or not the timer T (Cc) has a set time of 3 or more. That is, it is determined whether or not the elapsed time from transmitting the packet of the sequence number Np + Cc has elapsed the set time 3 or more. When the timer T (Cc) is less than the set time 3 (NO in step S025A), the process proceeds to step S32A. When the timer T (Cc) has a set time of 3 or more (YES in step S025A), the process proceeds to step S026A.

In step S026A, the communication control unit 38 confirms whether or not the transmission count counter Cpf (Cc) has a set count of 3 or more. That is, it is determined whether or not the number of transmissions of the packet having the sequence number Np + Cc is 3 or more as the set number of times. When the transmission count counter Cpf (Cc) is less than the set count 3 (NO in step S026A), the process proceeds to step S28A. When the transmission count counter Cpf (Cc) has a set count of 3 or more (YES in step S026A), the process proceeds to step S027A, the abandonment flag of the sequence number Np + Cc of the reception confirmation map is set to “1”, and the process proceeds to step S30A. ..

In step S028A, the communication control unit 38 retransmits the packet of sequence number Np + Cc to the main board 10 by UDP. The UDP packet transmitted in step S28A may have a configuration in which the sub-sequence number is omitted from the configuration shown in FIGS. 5 (b) and 5 (c). Further, in step S029A. The timer T (Cc) is reset in order to measure the elapsed time since the packet of the sequence number Np + Cc retransmitted in the previous step is transmitted. Further, in step S029A, the communication control unit 38 increases the value of the transmission count counter Cpf (Cc) by one.

The communication control unit 38 determines in step S030A whether or not the counter Cc is equal to or greater than the continuous packet set value Dd2. When the value of the counter Cc is the continuous packet set value Dd2 or more (YES in step S030A), the process returns to step S022A. When the counter Cc is less than the continuous packet set value Dd2 (NO in step S030A), the communication control unit 38 proceeds to step S032A, increases the value of the counter Cc by one, and then returns to step S023A.

In step S031A, the communication control unit 38 confirms the reception confirmation map from the sequence number Np + 1 to the sequence number Np + Dd2, and for each packet from the sequence number Np + 1 to the sequence number Np + Dd2, either the confirmation flag or the abandonment flag is set. Confirm that it is 1.

If either the confirmation flag or the abandonment flag is 1 in the reception confirmation map of a certain packet, it means that the reception of the packet is confirmed or abandoned. Therefore, in step S031A, the fact that either the confirmation flag or the abandonment flag is "1" for each packet from the sequence number Np + 1 to the sequence number Np + Dd2 means that the sequence numbers Np + 1 to the sequence number Np + Dd2 are set. It means that reception confirmation or transmission abandonment was determined for two Dd packets.

In step S031A, the communication control unit 38 sets the confirmation flag or the abandonment flag to "1" for each packet from sequence number Np + 1 to sequence number Np + Dd2 (NO in step S031A). Move to S30A. When either the confirmation flag or the abandonment flag is 1 for each packet from the sequence number Np + 1 to the sequence number Np + Dd2 (YES in step S031A), reception confirmation of all packets in the packet group of the sequence number is confirmed. Alternatively, assuming that the transmission abandonment is confirmed, the process proceeds to step S033.

In FIG. 19, steps S033 and S035 are the same as steps S033 and S035 in FIG. Further, step S034 in FIG. 10 is replaced with step S034A in FIG.

When the sequence number Np is less than n + N + 1 in step S033 (NO in step S033), the communication control unit 38 determines that there is a sequence number that has not been confirmed, proceeds to step S034A, and continues to the sequence number Np. The packet set value Dd2 is added, and the process returns to step S017A.

As described above, even when the operation status numerical data for one time unit is transmitted as one UDP packet, the reception of the number of packets defined by the continuous packet setting value Dd2 is once confirmed as one packet group. It is possible to shorten the time for reception confirmation and speed up the transmission by continuously transmitting without any problems, then confirming the reception, and retransmitting only the unreceived packets of the reception completion notification. ..

20 and 21 are flowcharts illustrating a processing procedure for receiving failure data in the main trunk board 10 when a serious failure occurs in the power conversion device 30 in the second embodiment. Only the differences from FIGS. 11 and 12 will be described. Step S050 of FIG. 11 and steps S051, S061, S062, S063, S064, and S071 of FIG. 12 are replaced with steps S050A of FIG. 20 and steps S051A, S061A, S062A, S063A, S064A, and S071A of FIG. .. In the second embodiment, since the sub-sequence number is not defined, the procedure is based only on the sequence number.

The main board 10 reads the sequence number L of the received UDP packet in step S050A, and determines whether or not the sequence number L matches n + 1 in step S051A. Here, n corresponds to the sequence number of the last received UDP packet when a serious failure occurred in the power conversion device 30 last time.

When the sequence number L matches n + 1 (YES in step S051A), the main board 10 determines that the received UDP packet is the above-mentioned first packet, and proceeds to step S052. When the sequence number L does not match n + 1 (NO in step S051A), the main board 10 determines that the received UDP packet is a packet after the second packet, and proceeds to step S061A.

In step S061A, the main trunk board 10 confirms whether or not the reception flag of the received sequence number L is 0 by the reception data map. If the reception flag is not 0 (NO in step S061A), the main board 10 determines that the data of the sequence number L has already been received, and proceeds to step S064A. When the reception flag is 0 (YES in step S061A), the main board 10 proceeds to step S062A, sets the reception flag of the sequence number L of the reception data map to 1, and further proceeds to step S063A.

In step S063A, the main board 10 determines the type of numerical data from the data order of the received UDP packets, and records it as the operation status numerical data of the type at the corresponding time of the corresponding sequence number L of the storage device 14. ..

Next, in step S064A, the main trunk board 10 transmits a reception completion notification of the received sequence number to the power conversion device 30. This corresponds to the communication C26 in FIG. After completing step S064, the main trunk board 10 shifts to step S071A.

In step S071A, the main board 10 determines whether or not all the flags from the sequence number n + 1 to the sequence number n + N + 1 of the received data map are 1. When all the reception flags are 1 (YES in step S071A), the process proceeds to step S073. If all the reception flags are not 1 (NO in step S071A), the process proceeds to step S072.

As described above, in the main board according to the second embodiment, UDP packets having duplicate data can be discarded and even lost UDP data can be determined, so that the reliability is not squeezed in the storage area. Highly reliable traceback data can be obtained.

In the reception confirmation process according to the second embodiment, it may be read as if the process is performed only by the sequence number in steps S102 and S103 of FIG. Further, the packet of the reception completion notification according to the second embodiment may be configured by omitting the sub-sequence number in the data unit in FIG.

[Third Embodiment]
Next, a third embodiment of the present invention will be described. The description of common points with the first embodiment such as the hardware configuration is omitted, and only the changes will be described below.

In the first embodiment, the second and subsequent packets transmit numerical data of the operating status in the order of recording by the power conversion device 30. However, in general, the closer to the failure occurrence time among the numerical data of the operation status before the failure occurrence time, the more useful for the investigation of the failure cause and the higher the importance. In the third embodiment, the operation status numerical data after the second packet is recorded, and the data before the occurrence of the serious failure is recorded from the time when the serious failure is detected (that is, the time tF in FIG. 2) to the time when the recording starts (time t1 in FIG. 2). It is transmitted in order as if going back to, and the data after the occurrence of a serious failure is transmitted in the order of recording.

With such a configuration, the control power supply of the power conversion device 30 is lost and the transmission of the trace back data is interrupted before the traceback data from the power conversion device 30 to the main board 10 is completely transmitted. However, since it is highly possible that the transmission of the numerical data of the operating status immediately before the occurrence of the failure, which is of high importance, has been completed, the possibility of investigating the cause of the failure is also high.

22 to 24 show a flowchart illustrating a processing procedure for transmitting trace back data when a serious failure occurs in the power conversion device 30 according to the third embodiment of the present invention. The flowcharts of FIGS. 22 to 24 correspond to FIGS. 9 and 10 in the first embodiment.

The parts corresponding to FIGS. 7 and 8 according to the third embodiment of the present invention are the same as those of FIGS. 7 and 8, and thus the description thereof will be omitted. Further, the same parts as those in FIGS. 9 and 10 will be omitted, and only the different parts will be described.

Step S016 of FIG. 9 and steps S033 and S034 of FIG. 10 are replaced with steps S316 of FIG. 22 and steps S333 and S334 of FIG. 24, respectively. Further, steps S0335, S336, S337, S338, and S339 in FIG. 24 have been added. The process proceeds from step S012 or step S15A in FIG. 8 to step S316.

With reference to FIG. 22, the communication control unit 38 sets the counter Np to n + 1 + F and further sets the flag Cdec to 1 in step S316. Here, as described above, F is a number representing the number of recording time points from the failure recording start point to the trigger point. Therefore, n + 1 + F represents the sequence number of the data of the operation status of the trigger point. After the end of step S316, the process proceeds to step S017. In the steps after step S017, the process of sending the operation status numerical data at the trigger point is performed. The flag Cdec is a flag for determining whether to decrease or increase the counter Np indicating the sequence number.

Steps S017 to S032 are the same as those in the first embodiment. If YES in step S031, the process proceeds to step S333 in FIG. 24.

With reference to FIG. 24, the communication control unit 38 determines in step S333 whether or not the flag Cdec is 1. When the flag Cdec is 1 (YES in step S333), the communication control unit 38 proceeds to step S334, and further determines whether or not Np is n + 2 or less.

When Np is larger than n + 2 (NO in step S334), the communication control unit 38 determines that the transmission of data from the trigger point to the recording start point has not been completed, and proceeds to step S335. In step S335, the value of the counter Np is decremented by 1, and the process returns to step S017 in FIG. Through the above loop, the operation status numerical data from the trigger point to the recording start point is transmitted from the power conversion device 30 to the main board 10.

When Np is n + 2 or less (YES in step S334), the communication control unit 38 determines that the transmission of data from the trigger point to the recording start point has been completed, and proceeds to step S336. In step S336, the flag Dec is set to 0, the value of the counter Np is set to n + 1 + F, and the process proceeds to step S342.

If the flag Dec is not 1 in step S333 (NO in step S333), the communication control unit 38 shifts to step S341 and further determines whether or not Np is n + 1 + N or more. n + 1 + N represents a sequence number corresponding to the operation status numerical data at the end of recording.

If it is determined in step S341 that Np is smaller than n + 1 + N (NO in step S341), the communication control unit 38 determines that there is data with an untransmitted sequence number, and proceeds to step S342. In step 342, the value of the counter Np is incremented by 1, and the process returns to step S017. In the processing after step 17, the operation status numerical data from the trigger point to the recording end time is transmitted from the power conversion device 30 to the main board 10.

When it is determined in step S341 that Np is n + 1 + N or more (YES in step S341), the communication control unit 38 determines that there is no untransmitted sequence number data, and proceeds to step S035 to perform the second step. The same process as that of the first embodiment is performed.

As described above, according to the third embodiment, the control power supply of the power conversion device 30 is lost and the trace is performed before the trace back data from the power conversion device 30 to the main board 10 is completely transmitted. Even if the transmission of back data is interrupted, there is a higher possibility that the transmission of numerical data on the operating status immediately before the occurrence of a highly important failure has been completed, so that the possibility of investigating the cause of the failure is also high.

(Fourth Embodiment)
In the above-described embodiment, a configuration example of a failure data recording system in which communication paths between the main board 10 and the power conversion device 30 are multiplexed has been described, but the present invention has been described as shown in FIG. 25. Even in the failure data recording system in which the 10 and the power conversion device 30 are connected to the communication network 103, the same effects as those in the above-described embodiment can be obtained.

FIG. 25 is a schematic block diagram showing the overall configuration of the failure data recording system according to the fourth embodiment. In the example of FIG. 25, the main board 10 and the power conversion device 30 can transmit and receive data via the communication network 103. The communication network 103 is, for example, the Internet. A second communication protocol (TCP) is used for transmission / reception of normal data and communication of failure data when a minor failure occurs. On the other hand, since high speed is required for communication of failure data when a serious failure occurs, the first communication protocol (UDP) is used. When passing through the communication network 103, the packet transmitted from the power conversion device 30 is delivered to the main trunk board 10 via a plurality of different communication paths. As a result, as in the example of FIG. 1, duplicate packets are sent to the main trunk board 10 from a plurality of communication paths.

Also in FIG. 25, the power conversion device 30 and the main trunk board 10 transmit and receive failure data according to the flowcharts shown in the first embodiment, the second embodiment, and the third embodiment of the present invention. Thereby, it is possible to provide a failure data recording system and a failure data transmission device capable of transferring the trace back data of the power conversion device 30 at high speed while ensuring reliability.

In FIGS. 1 and 25, the first and second devices constituting the failure data recording system are described as the power conversion device 30 and the main trunk board 10, but the first and second devices are the power conversion device 30. And it is also possible to use other than the main trunk board 10.

It should be considered that the embodiments disclosed this time are exemplary in all respects and not restrictive. The scope of the present invention is shown by the scope of claims rather than the above description, and is intended to include all modifications within the meaning and scope equivalent to the scope of claims.

10 Main board, 12 Control circuit, 14 Storage device, 15 Control device, 16 Communication control unit, 18, 20, 40, 42 Communication I / F, 30 Power converter, 32 Main circuit, 33 Detector, 34 Inverter control unit , 35 control device, 36 detection data storage unit, 38 communication control unit, 44 control power supply, 50, 60 CPU, 52, 62 ROM, 54, 64 RAM, 56, 66 I / O interface, 58 display unit, 59 input unit. , 100 failure data recording system, 101, 102 communication paths, 103 communication networks.

Claims (7)

Equipped with a first device and a second device
The second device is configured to control the first device by transmitting a control command to the first device to the first device.
The first device is configured to transmit the traceback data of the first device to the second device in the event of a failure in the first device.
The first device uses a first communication protocol that does not guarantee the arrival of data when the failure of the first device is a serious failure, and includes information on the failure type of the serious failure. Data on the operating status of the first device before and after the occurrence of a serious failure is transmitted as the traceback data.
The traceback data is
A first-class packet containing the time of occurrence of the major failure and bit information of the failure type of the major failure, and
It includes the operation status data of the first device in the collected time unit and the second type packet including a plurality of packets in which consecutive identifiers are given in the collected time unit.
When the first device receives the reception completion notification of the first-class packet after transmitting the first-class packet to the second device, or the number of times the first-class packet is transmitted is the first. A failure data recording system that transmits the type 2 packet to the second device when the reception completion notification of the type 1 packet is not received when the allowable value is reached. The first device is
After transmitting a plurality of predetermined type 2 packets continuously to the second device without confirming the reception completion notification of the type 2 packet,
When the number of times the second type packet is transmitted does not reach the second allowable value and the reception completion notification of the second type packet is not received,
The failure data recording system according to claim 1, wherein only the packet for which the reception completion notification of the second type packet has not been received is transmitted to the second device. The first device is
From the failure time time point packet containing the operation status data recorded immediately after the occurrence of the serious failure to the second type packet, the packet containing the operation status data whose collection time is sequentially traced back to the second device in order. Send and
After transmitting the packet containing the operation status data at the collection start time, the packet containing the operation status data recorded after the time when the operation status data included in the failure time time packet is collected is sent to the second device. The failure data recording system according to claim 1, which is transmitted. The failure data recording system according to claim 1, wherein the first device transmits the traceback data by using a communication protocol that guarantees the arrival of data when the failure is a minor failure. It is a failure data transmission device that transfers the failure data of the first device to the second device.
When a failure occurs in the first device, the trace back data of the first device is configured to be transmitted to the second device.
When the failure of the first device is a serious failure, the first communication protocol that does not guarantee the arrival of data is used, and the above before and after the occurrence of the serious failure including information on the failure type of the serious failure. The operation status data of the first device is transmitted as the traceback data, and the data is transmitted.
The traceback data is
A first-class packet containing the time of occurrence of the major failure and bit information of the failure type of the major failure, and
It includes the operation status data of the first device in the collected time unit and the second type packet including a plurality of packets in which consecutive identifiers are given in the collected time unit.
When the first type packet is transmitted to the second device and then the reception completion notification of the first type packet is received, or when the number of times the first type packet is transmitted reaches the first allowable value. A failure data transmission device that transmits the second type packet to the second device when the reception completion notification of the first type packet is not received. The failure data transmission device is
After transmitting a plurality of predetermined type 2 packets continuously to the second device without confirming the reception completion notification of the type 2 packet,
When the number of times the second type packet is transmitted does not reach the second allowable value and the reception completion notification of the second type packet is not received, only the packet that has not received the reception completion notification of the second type packet. The failure data transmission device according to claim 5, wherein the packet is retransmitted to the second device. The failure data transmission device is
From the failure time time point packet containing the operation status data recorded immediately after the occurrence of the serious failure to the second type packet, the packet containing the operation status data whose collection time is sequentially traced back to the second device in order. Send and
After transmitting the packet containing the operation status data at the collection start time, the packet containing the operation status data recorded after the time when the operation status data included in the failure time time packet is collected is sent to the second device. The failure data transmission device according to claim 5, which is to be transmitted.

Images