Frequency converter fault time synchronization method and related equipment

Abstract

The invention discloses a frequency converter fault time synchronization method and related equipment, and relates to the technical field of frequency converters, and the method comprises the steps: determining frequency conversion fault operation time based on frequency conversion starting time and frequency conversion fault time; determining a frequency conversion fault time difference based on the frequency conversion fault operation time and the frequency conversion operation time; and determining the frequency conversion fault actual time based on the frequency conversion fault time difference and the current time.

Description

Technical Field

[0001] The present application relates to the technical field of frequency converters, and in particular to a frequency converter fault time synchronization method and related equipment. Background Art

[0002] With the rapid development of industrial automation technology, frequency converters have been widely used in various industrial applications. However, during the operation of the frequency converter, fault alarms often occur, and the recorded time data is usually based on the system start time. All fault records use this as a reference to calculate the relative operating time. This time recording method makes it difficult to quickly trace back to the exact time of the fault in the actual fault handling and fault cause analysis process, which brings great inconvenience to the operation and maintenance management of the equipment.

[0003] At present, in order to solve the problem of inconsistency between the inverter system time and the actual time, the usual practice is to adjust the system time by modifying the parameters inside the control unit to keep it synchronized with the actual time. However, this method has multiple defects: each device needs to be configured with parameters separately, which increases the operation and maintenance costs; the parameters cannot be saved during power outages and need to be reset frequently. In addition, for scenarios with a large number of inverter devices, this method is obviously inefficient and difficult to meet actual needs. Therefore, how to accurately synchronize the actual time of inverter failure has become one of the key technical problems to improve equipment maintenance efficiency. Summary of the invention

[0004] A series of simplified concepts are introduced in the Summary of the Invention section, which will be further described in detail in the Detailed Description of the Invention section. The Summary of the Invention section of this application does not mean to attempt to define the key features and essential technical features of the claimed technical solution, nor does it mean to attempt to determine the scope of protection of the claimed technical solution.

[0005] In a first aspect, the present application provides a method for synchronizing a frequency converter fault time, comprising:

[0006] Determine the frequency conversion fault operation time based on the frequency conversion start time and the frequency conversion fault time;

[0007] Based on the above frequency conversion fault operation time and frequency conversion operation time, determine the frequency conversion fault time difference;

[0008] Based on the above frequency conversion fault time difference and the current time, the actual time of the frequency conversion fault is determined.

[0009] In a feasible implementation manner, the above-mentioned determination of the frequency conversion fault operation time based on the frequency conversion start time and the frequency conversion fault time includes:

[0010] Calculate the number of days between the frequency conversion fault time and the frequency conversion start time, add the number of hours, minutes and seconds in the frequency conversion fault time, and determine the frequency conversion fault operation time, wherein the frequency conversion fault time is determined based on the frequency conversion start time.

[0011] In a feasible implementation manner, determining the frequency conversion fault time difference based on the frequency conversion fault operation time and the frequency conversion operation time includes:

[0012] The difference between the frequency conversion operation time and the frequency conversion fault operation time is calculated as the frequency conversion fault time difference, wherein the frequency conversion operation time is determined based on the frequency conversion start time.

[0013] In a feasible implementation manner, the actual time of the above frequency conversion fault is determined based on the following formula:

[0014]

[0015] Among them, Now() is the current time, d is the number of days of the frequency conversion fault time difference, h is the number of hours of the frequency conversion fault time difference, m is the number of minutes of the frequency conversion fault time difference, and s is the number of seconds of the frequency conversion fault time difference.

[0016] In a feasible implementation manner, after determining the frequency conversion fault time difference, the method includes:

[0017] Based on the ROUNDDOWN function in Excel, the above frequency conversion failure time difference is converted into the format of days, hours, minutes and seconds.

[0018] In a feasible implementation, it also includes:

[0019] Based on the Excel table, the actual time of the frequency conversion fault is automatically calculated when the above frequency conversion fault time and the above frequency conversion running time are input.

[0020] In a feasible implementation, it also includes:

[0021] Automatically correct the offset error of the above frequency conversion start time.

[0022] In a second aspect, the present application proposes a frequency converter fault time synchronization device, comprising:

[0023] A frequency conversion fault operation time determination unit, used to determine the frequency conversion fault operation time based on the frequency conversion start time and the frequency conversion fault time;

[0024] A frequency conversion fault time difference determining unit, used to determine the frequency conversion fault time difference based on the frequency conversion fault operation time and the frequency conversion operation time;

[0025] The frequency conversion fault actual time determining unit is used to determine the frequency conversion fault actual time based on the frequency conversion fault time difference and the current time.

[0026] In a third aspect, an electronic device comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor is configured to implement the steps of any one of the inverter fault time synchronization methods of the first aspect when executing the computer program stored in the memory.

[0027] In a fourth aspect, the present application further proposes a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the inverter fault time synchronization method of any one of the first aspects is implemented.

[0028] In summary, the embodiment of the present application accurately derives the actual time when the fault occurs by calculating the association between the start time, fault time, operating time and current time of the frequency converter. Specifically, the present invention obtains the operating time of the fault by performing a difference calculation on the start time and fault time of the frequency conversion; then, the fault time difference is further calculated in combination with the frequency conversion operating time; and finally, the actual time of the fault is reversed based on the current time. The calculation method of the present invention not only supports time recording accurate to the millisecond level, but also fully considers the time span problem of multi-day operation, so that the time calculation is more accurate and has good robustness. The method of the present invention can simplify the operation steps of the equipment operation and maintenance personnel. Only the operation data of the equipment needs to be input to quickly obtain the accurate actual time of the fault, reducing the complexity of manually adjusting the system time or using external tools to calculate. In addition, by adopting a unified time synchronization logic, the present invention can be widely applied to the scenarios of single equipment and multi-equipment collaborative work, improving the efficiency of industrial equipment maintenance and the timeliness of fault handling, and significantly enhancing the stability and reliability of the system. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] Various other advantages and benefits will become apparent to those of ordinary skill in the art by reading the detailed description of the preferred embodiments below. The accompanying drawings are only for the purpose of illustrating the preferred embodiments and are not to be considered as limiting the present specification. Also, the same reference symbols are used throughout the accompanying drawings to represent the same components. In the accompanying drawings:

[0030] Figure 1 A schematic flow chart of a method for synchronizing a frequency converter fault time provided in an embodiment of the present application;

[0031] Figure 2 A schematic diagram of test results based on Excel provided in an embodiment of the present application;

[0032] Figure 3 A schematic diagram of code test results provided for an embodiment of the present application;

[0033] Figure 4 A schematic diagram of data reading based on the Starter software provided in an embodiment of the present application;

[0034] Figure 5 A schematic diagram of the structure of a frequency converter fault time synchronization device provided in an embodiment of the present application;

[0035] Figure 6 A schematic diagram of the structure of a frequency converter fault time synchronization device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0036] The terms "first", "second", "third", "fourth", etc. (if any) in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments described herein can be implemented in an order other than that illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices. The technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all of the embodiments.

[0037] See also Figure 1 , is a flow chart of a method for synchronizing a frequency converter fault time provided by an embodiment of the present application, which may specifically include:

[0038] S110, determining the frequency conversion fault operation time based on the frequency conversion start time and the frequency conversion fault time;

[0039] For example, the frequency conversion fault operation time is determined based on the frequency conversion start time and the frequency conversion fault time, which mainly utilizes the time recording characteristics of the Siemens frequency converter, that is, all fault and alarm times are based on the system default start time. By calculating the difference between the frequency conversion fault time and the start time, the operation time when the fault occurs can be obtained.

[0040] The fault time recorded by Siemens inverters is an offset from the default start time, not the actual occurrence time. For example, when a fault occurs, the inverter will record the number of days, hours, minutes, and seconds of operation starting from the start time. To determine the operating time of the fault, first subtract the fault time from the start time to get the total number of seconds the fault occurred. For scenarios with multiple days of operation, the number of days the fault occurred must also be converted to seconds and added to the hours, minutes, and seconds to accurately calculate the total operating time.

[0041] This method fully combines the fixed time timing logic of the Siemens inverter. It does not need to adjust the system start time and avoids complex manual configuration or parameter modification operations. It can obtain the operating time when the fault occurs through precise time calculation within the established time recording framework, thereby providing basic support for the calculation of the actual fault time.

[0042] S120, determining a frequency conversion fault time difference based on the frequency conversion fault operation time and the frequency conversion operation time;

[0043] Exemplarily, the frequency conversion fault time difference is determined based on the frequency conversion fault operation time and the frequency conversion operation time. The core principle is to use the timing logic of the Siemens frequency converter operation time to derive the relative time difference between the fault occurrence and the current operation time through difference calculation.

[0044] Specifically, the variable frequency running time is the total running time of the inverter from the start time, including days, hours, minutes and seconds; while the variable frequency fault running time represents the cumulative time from the same start time to the occurrence of the fault. Since both are based on a fixed start time, the fault time difference can be calculated by simple subtraction.

[0045] This time difference directly reflects the relative time interval between the fault occurrence and the current moment. To ensure the accuracy of the calculation, the operating time and the fault operating time need to be converted into a unified unit. This method makes full use of the consistency of the timing logic of the Siemens inverter, avoids the time calculation error caused by the adjustment of the system start time, ensures the simplicity and reliability of the fault time difference calculation, and lays the foundation for further calculation of the actual fault time.

[0046] S130: Determine the actual time of the frequency conversion fault based on the frequency conversion fault time difference and the current time.

[0047] Exemplarily, the actual time of the frequency conversion fault is determined based on the frequency conversion fault time difference and the current time. The core is to use the time difference calculation result of the Siemens frequency converter to map the relative time of the fault to the actual time.

[0048] Specifically, the frequency conversion fault time difference indicates the time interval between the fault occurrence and the current time. By subtracting this time difference from the current system time, the actual time of the fault can be accurately traced back.

[0049] The current time is usually obtained by the real-time clock provided by the device or system, and the frequency conversion fault time difference is the precise time interval calculated in the previous steps. In the calculation process, in order to ensure the consistency of the time unit, the time difference needs to be based on seconds, while supporting higher precision.

[0050] This process makes full use of the relativity of Siemens inverter recording time and the real-time nature of system time, and quickly obtains the actual time of fault occurrence through simple mathematical operations. This method does not require adjusting the default time setting inside the inverter, which not only ensures the simplicity of calculation, but also improves the accuracy of time synchronization, providing a reliable time basis for inverter fault analysis and location.

[0051] In some examples, determining the frequency conversion fault operation time based on the frequency conversion start time and the frequency conversion fault time includes:

[0052] Calculate the number of days between the frequency conversion fault time and the frequency conversion start time, add the number of hours, minutes and seconds in the frequency conversion fault time, and determine the frequency conversion fault operation time, wherein the frequency conversion fault time is determined based on the frequency conversion start time.

[0053] For example, the difference in days between the frequency conversion fault time and the frequency conversion start time is first calculated and converted into seconds; then the hours, minutes and seconds in the frequency conversion fault time are converted into seconds and accumulated, and finally the total running time (in seconds) when the fault occurs is obtained. Since the frequency conversion fault time is calculated based on the fixed frequency conversion start time, this method ensures the consistency and accuracy of time calculation, simplifies the calculation process of the time span across days, and provides a basis for the subsequent derivation of the time difference and the actual fault time.

[0054] In some examples, determining the frequency conversion fault time difference based on the frequency conversion fault operation time and the frequency conversion operation time includes:

[0055] The difference between the frequency conversion operation time and the frequency conversion fault operation time is used as the frequency conversion fault time difference, wherein the frequency conversion operation time is determined based on the frequency conversion start time.

[0056] Exemplarily, the frequency conversion fault time difference is obtained by calculating the difference between the frequency conversion operation time and the frequency conversion fault operation time. Since the frequency conversion operation time and the frequency conversion fault operation time are both calculated based on the same frequency conversion start time, their values ​​are the difference in seconds accumulated from the start time, so the method for calculating the difference is simple and accurate. This method ensures the reliability of the fault time difference calculation and provides an accurate time interval basis for further determining the actual occurrence time of the fault.

[0057] In some examples, it also includes: the above-mentioned variable frequency operation time and the above-mentioned variable frequency fault operation time are converted into seconds for calculation.

[0058] Exemplarily, the above-mentioned variable frequency operation time and variable frequency fault operation time are converted into seconds for calculation to ensure the consistency and accuracy of time operations. Specifically, the days, hours, and minutes in the operation time are converted into seconds respectively, and added to the original seconds to obtain the total seconds of the operation time. This conversion method can uniformly handle different time units and avoid complex cross-unit calculations, and is particularly suitable for time scenarios that run across days. By unifying all times into seconds, it is convenient to directly perform accurate calculations of the fault time difference, providing a reliable basis for the derivation of the subsequent actual fault time.

[0059] In some examples, the actual time of the frequency conversion fault is determined based on the following formula:

[0060]

[0061] Among them, Now() is the current time, d is the number of days of the frequency conversion fault time difference, h is the number of hours of the frequency conversion fault time difference, m is the number of minutes of the frequency conversion fault time difference, and s is the number of seconds of the frequency conversion fault time difference.

[0062] In some examples, after determining the frequency conversion fault time difference, the following steps are performed:

[0063] Based on the ROUNDDOWN function in Excel, the above frequency conversion failure time difference is converted into the format of days, hours, minutes and seconds.

[0064] For example, the frequency conversion fault time difference is calculated in seconds, so the ROUNDDOWN function is used to convert it into a format that is easier to understand and operate. In the Excel table, the seconds are divided by the corresponding units and the obtained seconds are split into days, hours, minutes and seconds. The use of the ROUNDDOWN function ensures that even if there is a decimal part, the time difference can be accurately converted by rounding down, avoiding errors caused by floating decimals, so that the final result is more stable and reliable.

[0065] Through this process, the specific time difference between the occurrence of the frequency conversion fault and the current time can be clearly seen, which helps to quickly calculate the actual time of the frequency conversion fault. The advantage of this method lies in its simplicity and efficiency, especially in the long-term operation of the frequency converter system, it can ensure that no matter how large the time difference is, the time conversion and calculation can be performed accurately, providing accurate data support for fault analysis and equipment maintenance.

[0066] In some examples, it also includes:

[0067] Based on the Excel table, the actual time of the frequency conversion fault is automatically calculated when the above frequency conversion fault time and the above frequency conversion running time are input.

[0068] For example, the inverter fault time and inverter operation time are recorded based on the system default start time, rather than the actual current time. By entering the inverter fault time and inverter operation time in the Excel table, the system will first calculate the difference in days between the inverter fault time and the start time through the DAYS function, and then convert the time difference to seconds and minutes. Then, the current system time is obtained based on the NOW() function in the Excel table, and the actual occurrence time of the inverter fault is calculated by adding and subtracting logic through the calculation of the time difference.

[0069] This method ensures the automatic calculation of the inverter fault time without manual intervention, greatly improving the calculation efficiency. Through the real-time calculation function of the Excel table, users can directly obtain the actual time when the inverter fault occurs, avoiding manual conversion and errors. This automated calculation method not only simplifies the troubleshooting process, but also improves the accuracy of fault time analysis, especially in scenarios with long-term operation and across time units, and can efficiently solve the complexity caused by time differences.

[0070] In some examples, it also includes:

[0071] Automatically correct the offset error of frequency conversion start time;

[0072] Use multi-device synchronization logic to achieve consistency of time data of multiple inverters;

[0073] The time synchronization algorithm is improved through data analysis models to enhance the calculation accuracy under special working conditions.

[0074] Exemplarily, by monitoring the deviation between the time record of the frequency converter and the actual time, the reference benchmark of the start time is dynamically adjusted to ensure the accuracy of the start time. This correction mechanism can effectively reduce the time error caused by clock drift or system abnormality during long-term operation. In a multi-frequency converter system, by introducing time synchronization logic, the time records of each device are kept consistent, eliminating the fault timing analysis deviation caused by the inconsistent time benchmarks of different devices. The synchronization logic can be implemented based on the Network Time Protocol (NTP) or other distributed time synchronization algorithms. Using historical time data and equipment operating status, the time calculation algorithm is optimized through a data analysis model. For complex working conditions (such as high load or frequent power outages), this method can dynamically adjust the time synchronization strategy to improve the accuracy and robustness of time records.

[0075] In some examples, the frequency conversion start time is a system default time of the frequency converter control unit, wherein the system default time is 0 hours, 0 minutes, 0 seconds on January 1, 2000.

[0076] For example, this time setting is used as a unified reference benchmark for the cumulative recording of all operating time and fault time. During the operation of the inverter, all time data is calculated and recorded based on this start time rather than the actual time. By keeping the start time fixed, the system time record can be ensured to be consistent and predictable, avoiding the complex time calculation problems caused by system time adjustment or error, thereby simplifying fault analysis and operating time management.

[0077] This application is specifically designed for the time management problem of Siemens inverters. Since the system time of Siemens inverters is fixed to the default start time, the fault time and operation time are recorded relative to the start time. Therefore, when analyzing the time when the fault occurred, the relative time must be converted to the actual time through complex time difference calculations. To solve this problem, the solution utilizes the fixed time reference characteristics of the Siemens inverter, combined with precise time calculation logic, including second-level and millisecond-level time conversion and time difference calculation, to effectively push back the actual time when the fault occurred. This method not only simplifies operation and maintenance work, but also improves the accuracy of fault analysis, and can adapt to the complex scenarios of Siemens inverters in long-term operation and cross-time unit calculations.

[0078] In this embodiment, the above content can be implemented using Excel-based tools and Python codes.

[0079] In Excel, enter the frequency conversion start time (such as 0:00 on January 1, 2000) and the frequency conversion fault time. Use the DAYS function to calculate the difference in days between the two, expressed as =DAYS (fault time, start time). Extract the hours, minutes and seconds in the fault time and convert them into seconds, add them to the difference in days, and get the total running time at the time of the fault (in seconds). Enter the frequency conversion running time (the total cumulative time with the start time, in seconds). After converting both the running time and the fault running time to seconds, calculate the difference, expressed as time difference (seconds) = running time (seconds) - fault running time (seconds), and use the ROUNDDOWN function to decompose the time difference in seconds into days, hours, minutes and seconds. Use the current system time and the NOW() function to get the current time. Subtract the time difference from the current time in days to get the actual time of the fault.

[0080] In Python, the actual time of the fault and its related parameters are calculated through the start time, fault time, running time and current time of the inverter.

[0081] Import the datetime and timedelta classes from the datetime module. datetime is used to process dates and times, and timedelta is used to represent time differences, expressed as from datetime import datetime,timedelta.

[0082] Define a function calculate_fault_running_time_and_actual_time, which accepts five parameters, namely the inverter start time start_time, inverter fault time fault_time, running time days run_days, running time hours, minutes, seconds run_time and current time current_time, where the inverter start time and inverter fault time are in string format str, expressed as "YYYY-MM-DD HH:MM:SS.fff", the running time days are integers int, and the running time hours, minutes, seconds are in string format str, expressed as "HH:MM:SS.fff".

[0083] Use the datetime.strptime method to parse the start_time and fault_time strings into datetime objects, supporting milliseconds for easy calculation, expressed as: start_time_dt = datetime.strptime(start_time, "%Y-%m-%d %H:%M:%S.%f"); fault_time_dt = datetime.strptime(fault_time, "%Y-%m-%d %H:%M:%S.%f").

[0084] Calculate the number of seconds (floating point) of operation during which the fault occurred between the variable-frequency fault time and the start time, expressed as: fault_time_seconds = (fault_time_dt - start_time_dt).total_seconds().

[0085] Parse the running time run_time into hours, minutes, and seconds (supporting floating-point seconds), expressed as: try: run_time_parts = run_time.split(':'); run_hours = int(run_time_parts[0]); run_minutes = int(run_time_parts[1]); run_seconds = float(run_time_parts[2]); except ValueError: raise ValueError("The running time format is incorrect, it should be 'HH:MM:SS.fff'"). Split the run_time string by :, extract hours, minutes, and seconds, and convert them to integers and floating-point numbers. If the format is incorrect, raise a ValueError exception.

[0086] Calculate the total number of seconds of the running time, converting days, hours, minutes, and seconds to seconds, expressed as: run_time_seconds = run_days * 86400 + run_hours * 3600 + run_minutes * 60 + run_seconds, ensuring consistent units.

[0087] Check if the total number of seconds of the running time is greater than or equal to the number of seconds of the fault time. If it is less, raise an exception, expressed as: if run_time_seconds < fault_time_seconds: raise ValueError("The total number of seconds of the running time cannot be less than the total number of seconds of the fault time. Please check the input data!").

[0088] The difference in seconds from the fault time to the current time is obtained by subtracting the fault time from the running time, which is expressed as: time_difference_seconds=run_time_seconds-fault_time_seconds.

[0089] Use the timedelta function to subtract the difference in seconds between the fault occurrence and the current time from the current time to obtain the actual fault occurrence time, which is expressed as: actual_fault_time=current_time-timedelta(seconds=time_difference_seconds).

[0090] Returns the running time fault_time_seconds (seconds, with decimals) when the frequency converter faults, the actual fault occurrence time actual_fault_time, and the time difference from the fault to the present time time_difference_seconds (seconds).

[0091] In the test code, the input start time, fault time, running days and running time are defined as: start_time_input = "2000-01-01 00:00:00.000", fault_time_input = "2000-09-2705:31:16.918", run_days_input = 277 and run_time_input = "01:51:27.855".

[0092] Get the current time, expressed as: current_time = datetime.now().

[0093] Call the calculate_fault_running_time_and_actual_time function, pass in the input data, and get the three returned values, fault_run_seconds, actual_fault_time, time_difference_seconds = calculate_fault_running_time_and_actual_time(start_time_input, fault_time_input, run_days_input, run_time_input, current_time).

[0094] Print the current time, the running time when the frequency conversion fault occurs, the time difference between the fault and the present, and the actual fault occurrence time. Use the strftime method to format the time string, retaining milliseconds, expressed as print(f"Current time:{current_time.strftime('%Y-%m-%d%H:%M:%S.%f')[:-3]}");print(f"Running time when the frequency conversion fault occurs (seconds):{fault_run_seconds:.3f}");print(f"Time difference between the frequency conversion fault and the present (seconds):{time_difference_seconds:.3f}");print("Actual time of the frequency conversion fault:",actual_fault_time.strftime("%Y-%m-%d%H:%M:%S.%f")[:-3]).

[0095] The above code mainly calculates the actual occurrence time of the inverter fault; it parses the input time and running time, calculates the difference between the fault time and the start time, and then combines the current time to calculate the actual occurrence time of the fault. The test results of the embodiment of the present application in Excel and Python environment are as follows: Figure 2 and Figure 3 In actual operation, each time you use it, you only need to read the inverter fault time and inverter operation time in the fault history through the Starter software, and then calculate it through the above code. The Starter software data is as follows Figure 4 shown.

[0096] Starter software is a debugging and configuration tool for Siemens drive systems (such as SINAMICS series inverters), which is used to read the operating data and fault history of the equipment, including information such as inverter fault time and inverter operation time. These data are the basis for fault time analysis, and our code deduces the actual occurrence time of the fault by processing these basic data. Therefore, the relationship between Starter software and code is the relationship between data provision and processing, that is, Starter software is responsible for collecting and outputting the relevant time data of the inverter, and the code calculates and analyzes these data.

[0097] In actual operation, first use the Starter software to read the fault history records from the inverter and export these records as files (such as CSV files). Write a Python script to read the exported CSV files and extract the fault time and running time of the inverter. Use the function calculate_fault_running_time_and_actual_time in the above Python code to pass in the data extracted from the CSV file to calculate the actual occurrence time of the inverter fault. Output the calculation results to a new file or display them directly on the console for technicians to view and use.

[0098] The Starter software provides the code with accurate fault records and operating data. The code solves the defect of relative time recording in the Siemens inverter system through efficient time calculation logic, converts relative time into actual time, and provides direct support for fault location and analysis. This mode not only simplifies the complexity of fault time derivation, but also enhances the practical application value of the Starter software, making it no longer limited to a data display tool, but becoming one of the important auxiliary means of fault analysis. Through this combination, the efficiency and accuracy of operation and maintenance have been significantly improved, which is suitable for Siemens inverter maintenance scenarios under various complex working conditions.

[0099] See also Figure 5 , is a schematic diagram of the structure of a frequency converter fault time synchronization device provided in an embodiment of the present application, comprising:

[0100] A frequency conversion fault operation time determination unit 21, used to determine the frequency conversion fault operation time based on the frequency conversion start time and the frequency conversion fault time;

[0101] A frequency conversion fault time difference determination unit 22, configured to determine the frequency conversion fault time difference based on the frequency conversion fault operation time and the frequency conversion operation time;

[0102] The frequency conversion fault actual time determining unit 23 is used to determine the frequency conversion fault actual time based on the frequency conversion fault time difference and the current time.

[0103] See also Figure 6 The embodiment of the present application also provides an electronic device 300, including a memory 310, a processor 320, and a computer program 311 stored in the memory 310 and executable on the processor. When the processor 320 executes the computer program 311, the steps of any method for inverter fault time synchronization are implemented.

[0104] Since the electronic device introduced in this embodiment is the device used to implement the inverter fault time synchronization device in the embodiment of the present application, based on the method introduced in the embodiment of the present application, the technical personnel in this field can understand the specific implementation mode of the electronic device of this embodiment and its various variations. Therefore, how the electronic device implements the method in the embodiment of the present application is not introduced in detail here. As long as the equipment used by the technical personnel in this field to implement the method in the embodiment of the present application is within the scope of protection of this application.

[0105] During the specific implementation process, when the computer program 311 is executed by a processor, any implementation method in the embodiments corresponding to the first aspect can be implemented.

[0106] It should be noted that in the above embodiments, the description of each embodiment has its own emphasis, and for parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0107] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-readable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-readable program code.

[0108] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded computer, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0109] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0110] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process in the computer or other programmable device. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0111] The present application also provides a computer program product, which includes computer software instructions. When the computer software instructions are executed on a processing device, the processing device executes Figure 1 The process of the inverter fault time synchronization method in the corresponding embodiment.

[0112] The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website site, a computer, a server or a data center to another website site, a computer, a server or a data center by wired or wireless means. The computer-readable storage medium can be any available medium that a computer can store or a data storage device such as a server or a data center that includes one or more available media integration. The available medium can be a magnetic medium, an optical medium, or a semiconductor medium, etc.

[0113] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0114] In the several embodiments provided in the present application, it should be understood that the disclosed devices, apparatuses and methods can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of units is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0115] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0116] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0117] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for a computer device to execute all or part of the steps of each embodiment method of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory, random access memory, disk or optical disk and other media that can store program code.

[0118] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application.

[0119] Although the preferred embodiments of this specification have been described, those skilled in the art may make additional changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of this specification.

[0120] Obviously, those skilled in the art can make various changes and modifications to this specification without departing from the spirit and scope of this specification. Thus, if these modifications and variations of this specification fall within the scope of the claims of this specification and their equivalents, this specification is also intended to include these modifications and variations.

Claims

1. A frequency converter fault time synchronization method, characterized in that: The method comprises: Determine the frequency conversion fault operation time based on the frequency conversion start time and the frequency conversion fault time; Determine a frequency conversion fault time difference based on the frequency conversion fault operation time and the frequency conversion operation time; Based on the frequency conversion fault time difference and the current time, the actual time of the frequency conversion fault is determined.

2. The inverter fault time synchronization method according to claim 1, characterized in that: Determining the frequency conversion fault operation time based on the frequency conversion start time and the frequency conversion fault time includes: Calculate the number of days between the frequency conversion fault time and the frequency conversion start time, add the number of hours, minutes and seconds in the frequency conversion fault time, and determine the frequency conversion fault operation time, wherein the frequency conversion fault time is determined based on the frequency conversion start time.

3. The inverter fault time synchronization method according to claim 1, characterized in that: The determining of the frequency conversion fault time difference based on the frequency conversion fault operation time and the frequency conversion operation time includes: The difference between the frequency conversion running time and the frequency conversion fault running time is calculated as the frequency conversion fault time difference, wherein the frequency conversion running time is determined based on the frequency conversion start time.

4. The inverter fault time synchronization method according to claim 1, characterized in that: The actual time of the frequency conversion fault is determined based on the following formula: Where, Now ( ) is the current time, d is the number of days of the frequency conversion fault time difference, h is the number of hours of the frequency conversion fault time difference, m is the number of minutes of the frequency conversion fault time difference, and s is the number of seconds of the frequency conversion fault time difference.

5. The inverter fault time synchronization method according to claim 3, characterized in that: After determining the frequency conversion fault time difference, the method includes: Based on the ROUNDDOWN function in the Excel table, the frequency conversion fault time difference is converted into the format of days, hours, minutes and seconds.

6. The inverter fault time synchronization method according to claim 1, characterized in that: Also includes: Based on the Excel table, the actual time of the frequency conversion fault is automatically calculated when the frequency conversion fault time and the frequency conversion running time are input.

7. The inverter fault time synchronization method according to claim 1, characterized in that: Also includes: Automatically correct the offset error of the frequency conversion start time.

8. A frequency converter fault time synchronization device, characterized in that: include: A frequency conversion fault operation time determination unit, used to determine the frequency conversion fault operation time based on the frequency conversion start time and the frequency conversion fault time; A frequency conversion fault time difference determining unit, configured to determine the frequency conversion fault time difference based on the frequency conversion fault operation time and the frequency conversion operation time; The frequency conversion fault actual time determining unit is used to determine the frequency conversion fault actual time based on the frequency conversion fault time difference and the current time.

9. An electronic device, comprising: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor is used to implement the steps of the inverter fault time synchronization method as described in any one of claims 1 to 7 when executing the computer program stored in the memory.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the inverter fault time synchronization method according to any one of claims 1 to 7 is implemented.

Images