Test method of wind generating set

Abstract

The invention provides a testing method of a wind generating set. The test method comprises the following steps that: an upper computer responds to an operation which is executed on a unit test interface and is used for triggering continuous test, and sends a continuous test control signal to a test controller; the upper computer activates the timer under the condition that the received status word of the state machine fed back by the test controller in response to the continuous test control signal is inconsistent with the status word of the state machine received from the test controller last time, and sends the item identifier of the test item received from the test controller last time to the test controller; the test item is executed by the test controller; and under the condition that the timer is in the working state, if the upper computer receives test completion indication information indicating that any test item is completed from the test controller, the item identifier of the any test item is sent to the test controller, so that the test controller executes the next test item of the any test item.

Description

Technical Field

[0001] The present disclosure generally relates to the field of wind power generation technology, and more specifically, to a testing method for a wind power generator set. Background Art

[0002] During the factory inspection (also known as factory test and inspection) of wind turbine generator sets, the debugging-free platform realizes the automatic detection of unit equipment and unit signals. Its advantages are that on the one hand, it can avoid the omission of test items caused by manual inspection, and on the other hand, it can realize automatic detection, thereby reducing the workload and blind spots of manual inspection. For example, it may take at least 3 hours to complete the detection of all unit signals by manual testing, while it only takes 30 to 40 minutes to complete the detection of all signals by automated process detection; and for signals with short change time and signals with more associations with actuators, manual detection may not be complete (such as only detecting whether the motor is running, but not detecting whether the feedback signal is normal, etc.). On the other hand, the more complete the test items, the more content the corresponding test report (i.e., factory inspection report) will have, and it will take a certain amount of time to fill it out manually, while the automated report can be automatically generated by the program in just a few seconds.

[0003] However, the existing debugging-free platform has the following problems: the test is arranged by the host computer or the test interface runs in the host computer. When the host computer has an abnormality or crashes, or other problems cause the test interface to be accidentally closed, after opening the test interface again, the test can only be restarted from the beginning, resulting in duplication and rework of test work. Summary of the invention

[0004] An exemplary embodiment of the present disclosure provides a test method and platform for a wind turbine generator set, which can realize a breakpoint-resume test function.

[0005] According to a first aspect of an embodiment of the present disclosure, a test method for a wind turbine generator set is provided, the test method comprising: a host computer sends a continuation test control signal to a test controller in response to an operation for triggering continued testing performed on a unit test interface; when the status word of a state machine received by the host computer in response to the continuation test control signal is inconsistent with the status word of the state machine received from the test controller last time, the host computer activates a timer and sends a project identifier of a test item most recently received from the test controller to the test controller, so that the test controller executes the test item; when the host computer receives test completion indication information indicating that any test item has been completed from the test controller when the timer is in a working state, the host computer sends the project identifier of any test item to the test controller, so that the test controller executes the next test item of any test item; wherein the host computer is communicatively connected with the test controller.

[0006] Optionally, the testing method also includes: the test controller changes the state word of the state machine to a first preset value in response to a continuation test control signal received from the host computer, and sends the changed status word to the host computer; the test controller receives the project identifier of the test item sent by the host computer; and the test controller executes the test item if the project identifier received this time is consistent with the project identifier received last time.

[0007] Optionally, the testing method also includes: after the test controller completes the test of any test item, if the project identifier received from the host computer is inconsistent with the project identifier received last time, then the next test item of any test item is executed; after the test controller completes the test of any test item, if the project identifier of the test item is not received from the host computer, then the test process is stopped.

[0008] Optionally, the testing method also includes: the host computer activates the timer in response to an operation performed on the unit test interface to submit test configuration information, and sends the test configuration information to the test controller; when the host computer monitors that the unit test interface is not operating normally, the host computer controls the timer to stop working.

[0009] Optionally, the testing method also includes: the host computer writes the test results of the test items received in real time from the test controller into an array; after the host computer writes the test results into the array for the first time, the host computer sets the value of the write flag to a second preset value and sends the value of the write flag to the test controller; after the test results of all test items are written into the array, the host computer resets the write flag and sends the value of the write flag to the test controller; after the host computer establishes a communication connection with the test controller, if the host computer detects that the value of the write flag is the second preset value, the test configuration information is sent to the test controller; after the test controller completes power-on startup, if the test controller detects that the value of the write flag is the second preset value, the test item being executed when the test controller is powered off is executed based on the test configuration information.

[0010] Optionally, the test method further includes: the test controller sending the state word of the state machine, the project identifier of the current test project, test completion indication information and the test result to the host computer in real time.

[0011] Optionally, the operation for triggering continued testing includes operating a continued testing control on the unit test interface; wherein, the testing method further includes: when the test controller does not receive the project identifier of the test item sent by the host computer within a preset time period and the test mode is an automatic test mode, the test controller sends a continued testing permission signal to the host computer; when the host computer receives the continued testing permission signal sent by the test controller, the host computer puts the continued testing control in an operable state.

[0012] Optionally, the test controller is communicatively connected to the unit controller of the wind turbine generator set being tested; wherein the unit controller is used to receive unit signals and control the actions of actuators of multiple components of the unit, wherein the multiple components include an impeller, a nacelle, and a transmission chain, and the unit signals include sensor signals and switch signals; wherein multiple test items in the test process are used to test whether a fault is triggered in the unit controller, whether the actuator acts according to the control signal, and whether the unit signal is normal.

[0013] Optionally, the step of the test controller executing the next test item of any test item includes: the test controller determines whether a prompt dialog box needs to be displayed to the user for the next test item of any test item and whether the next test item has an associated test item; if the test controller determines that the prompt dialog box needs to be displayed, the test controller requests the host computer to display the prompt dialog box; if the test controller determines that the next test item has an associated test item, the test controller determines whether the test results of the test items associated with the next test item are all passed; if the test controller determines that the prompt dialog box needs to be displayed and has an associated test item, if the host computer receives a response to the prompt dialog box If the confirmation operation is performed and the test results of the test items associated with the next test item are all passed, the next test item will be executed; if the test controller determines that the prompt dialog box does not need to be displayed and there are associated test items, if the test results of the test items associated with the next test item are all passed, the next test item will be executed; if the test controller determines that the prompt dialog box needs to be displayed and there are no associated test items, if the host computer receives a confirmation operation on the prompt dialog box, the next test item will be executed; if the test controller determines that the prompt dialog box does not need to be displayed and there are no associated test items, the next test item will be executed.

[0014] Optionally, the test items associated with the no-load operation test items include: a first blade automatic pitch change emergency stop test item, a second blade automatic pitch change emergency stop test item, and a third blade automatic pitch change emergency stop test item; the test items associated with the safety chain pitch change emergency stop test item include: a maintenance handle forward pitch change test item and a maintenance handle backward pitch change test item.

[0015] Optionally, the test items on the pitch system include at least one of the following items: communication test item, power grid test item, software version test item, manual mode test item, cabinet manual pitch test item, proximity switch test item, limit switch test item, static temperature test item, heater test item, cooling fan test item, DC voltage test item, automatic emergency stop test item, maintenance handle pitch test item, safety chain system test item, no-load operation test item, temperature and greasing test item.

[0016] According to a second aspect of an embodiment of the present disclosure, a test platform for a wind turbine generator set is provided, the test platform comprising: a host computer and a test controller; wherein the host computer is configured to: in response to an operation executed on a unit test interface for triggering continued testing, send a continued test control signal to the test controller; when the state word of the state machine received by the test controller in response to the continued test control signal is inconsistent with the state word of the state machine received from the test controller last time, activate a timer, and send the project identifier of the test item most recently received from the test controller to the test controller, so that the test controller executes the test item; when the timer is in a working state, if a test completion indication information indicating that any test item has been completed is received from the test controller, the project identifier of any test item is sent to the test controller, so that the test controller executes the next test item of any test item; wherein the host computer is communicatively connected with the test controller.

[0017] Optionally, the test controller is configured to: in response to a continuation test control signal received from the host computer, change the state word of the state machine to a first preset value, and send the changed status word to the host computer; receive the project identifier of the test item sent by the host computer; and execute the test item if the project identifier received this time is consistent with the project identifier received last time.

[0018] Optionally, the test controller is also configured to: after completing the test of any test item, if the project identifier received from the host computer is inconsistent with the project identifier received last time, execute the next test item of any test item; after completing the test of any test item, if the project identifier of the test item is not received from the host computer, stop the test process.

[0019] According to a third aspect of an embodiment of the present disclosure, a computer-readable storage medium storing a computer program is provided. When the computer program is executed by a processor, the processor is prompted to execute the wind turbine generator test method as described above.

[0020] According to the wind turbine generator test method and platform of the exemplary embodiment of the present disclosure, after the unit test interface is accidentally closed and reopened, it is possible to perform breakpoint continuation testing, that is, to continue to execute the test process from the last executed test item, thereby avoiding repeated testing, reducing the test workload, and achieving the continuity of the test work. In addition, if the test controller is accidentally restarted, the test process can also be continued from the latest completed test item without starting the test from the beginning, thereby saving test time and improving test efficiency.

[0021] In the following description, some aspects and / or advantages of the general inventive concept will be set forth, and some other aspects and / or advantages will be known through the following description or the implementation of the general inventive concept. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] These and / or other aspects and advantages of the present application will become clearer and easier to understand from the following detailed description of the embodiments of the present application in conjunction with the accompanying drawings, in which:

[0023] Figure 1 A structural block diagram showing a test platform for a wind turbine generator set according to an exemplary embodiment of the present disclosure;

[0024] Figure 2 An example of partial display content of a unit test interface according to an exemplary embodiment of the present disclosure is shown;

[0025] Figure 3 A flow chart showing a method for testing a wind turbine generator system according to a first exemplary embodiment of the present disclosure;

[0026] Figure 4 A schematic diagram showing project identification interaction between a host computer and a test controller according to an exemplary embodiment of the present disclosure is shown;

[0027] Figure 5 A flow chart showing a method for testing a wind turbine generator system according to a second exemplary embodiment of the present disclosure;

[0028] Figure 6 A state transition diagram showing a state machine of a test controller according to an exemplary embodiment of the present disclosure;

[0029] Figure 7 A flow chart showing a method for testing a wind turbine generator system according to a third exemplary embodiment of the present disclosure;

[0030] Figure 8 A flow chart showing a method for testing a wind turbine generator system according to a fourth exemplary embodiment of the present disclosure;

[0031] Fig. 9 A flow chart showing a method for testing a wind turbine generator system according to a fifth exemplary embodiment of the present disclosure;

[0032] Fig.10 A flowchart showing a method for a test controller to execute a test item according to an exemplary embodiment of the present disclosure;

[0033] Fig.11 A test flow association example according to an exemplary embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0034] Reference will now be made in detail to the embodiments of the present disclosure, examples of which are illustrated in the accompanying drawings, wherein like reference numerals refer to like parts throughout. The embodiments will be described below with reference to the drawings in order to explain the present disclosure.

[0035] It should be noted that the terms "first", "second", etc. in the specification and claims of the present disclosure 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 interchanged where appropriate, so that the embodiments of the present disclosure described herein can be implemented in an order other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with some aspects of the present disclosure as detailed in the appended claims.

[0036] It should be noted that the phrase "at least one of the items" in the present disclosure includes three types of parallel situations: "any one of the items", "a combination of any number of the items", and "all of the items". For example, "including at least one of A and B" includes the following three parallel situations: (1) including A; (2) including B; (3) including A and B. Another example is "executing at least one of step 1 and step 2" which means the following three parallel situations: (1) executing step 1; (2) executing step 2; (3) executing step 1 and step 2.

[0037] Figure 1 A structural block diagram of a test platform for a wind turbine generator set according to an exemplary embodiment of the present disclosure is shown.

[0038] Reference Figure 1 According to an exemplary embodiment of the present disclosure, a test platform for a wind turbine generator set includes: a host computer 100 and a test controller 200 .

[0039] Specifically, the host computer 100 is connected to the test controller 200 by communication. The host computer 100 collects the data of the test controller 200 and sends a control instruction to the test controller 200 to monitor and control the test controller 200. The user can obtain the test progress, test status, test results, prompt information during the test process, etc. through the unit test interface displayed on the host computer 100, and can also control the test process through the unit test interface. As an example, the host computer 100 can be a computer device (e.g., PC), and the test controller 200 can be a programmable logic controller PLC. As an example, the host computer 100 and the test controller 200 can be connected to each other by communication via a wired network or a wireless network.

[0040] The test controller 200 is communicatively connected to the unit controller of the wind turbine generator set being tested. As an example, the test controller 200 and the unit controller can be communicatively connected via a distributed peripheral device of a process fieldbus (PROFIBUS DP) or Ethernet for control automation technology (ETHER CAT).

[0041] The unit controller is used to receive unit signals and control the actuator actions (e.g., start or stop) of multiple components of the unit. As an example, the multiple components may include but are not limited to impellers, nacelles, and transmission chains, and the unit signals may include but are not limited to sensor signals and switch signals. As an example, the unit controller may include but is not limited to at least one of the following items: a main controller, a pitch controller, a yaw controller, and a current controller. As an example, the sensor signal is the acquisition signal output by the sensor, and the switch signal is a signal used to reflect the connection and disconnection of the contact. For example, a switching device (e.g., a relay, a valve, a contactor) can output a switch signal.

[0042] As an example, the test process according to the exemplary embodiment of the present disclosure may include multiple test items, which can be used for but not limited to testing whether a fault is triggered in the unit controller, whether the actuator acts according to the control signal, and whether the unit signal is normal.

[0043] As an example, the test items for the pitch system may include but are not limited to at least one of the following items: communication test items, power grid test items, software version test items, manual mode test items, cabinet manual pitch test items, proximity switch test items, limit switch test items, static temperature test items, heater test items, cooling fan test items, DC voltage test items, automatic emergency stop test items, maintenance handle pitch test items, safety chain system test items, no-load operation test items, temperature and greasing test items. It should be understood that each of the above test items may include more detailed sub-items, for example, as shown in Table 1, where 1#, 2#, and 3# refer to the first blade, the second blade, and the third blade, respectively.

[0044] Table 1

[0045]

[0046]

[0047] Taking the test of the variable pitch system as an example, the specific test items are shown in Table 1. Among them, the test items such as the manual mode test, the manual variable pitch test, the proximity switch / limit switch test, and the safety chain system test require personnel to manually operate the three axes of the variable pitch system respectively (rotate the variable pitch bearing to the predetermined position) to realize the test and detection, which requires two people to cooperate to complete (one person operates and one person observes the interface data). Therefore, if there is a problem with the host computer, all the above processes need to be re-operated when retesting, which will cause a significant extension of the test time, affecting the test progress and the factory delivery time. After using the method disclosed in the present invention, the test items that have passed the test do not need to be retested, so the test efficiency and convenience can be greatly improved.

[0048] Figure 2 An example of partial display content of a unit test interface according to an exemplary embodiment of the present disclosure is shown.

[0049] like Figure 2 As shown, each box represents a test item, each test item has its own specific test logic, and each test item calls a test function block once. If the test item passes the test (i.e., meets the preset test conditions), the box background color can turn green. If the test item fails the test or the test is not enabled, the box background color can turn red. After each test item is tested (i.e., the test is over), the test process is executed downward in the direction indicated by the arrow. When the testing of all test items is completed (i.e., the test process is completed), a test report can be automatically generated.

[0050] The problem existing in the related technology is: if the unit test interface is accidentally closed (or the upper computer program needs to be replaced manually), when the unit test interface is closed and then reopened, since the control elements are in the initialization state, the test process cannot continue to test downward, and can only resubmit the configuration information and restart the test from the beginning. When there are many test items, a lot of time is wasted due to rework.

[0051] In the exemplary embodiment of the present disclosure, the test controller 200 interacts with the host computer 100 to test the project identification and test status, and the state machine status word of the test project. On the one hand, it is used to realize the host computer 100 to control the startup of each test project, and on the other hand, it is used to realize the breakpoint resumption function. Specifically, when the host computer 100 freezes, the unit test interface is stuck, or the host computer 100 loses power unexpectedly, after running the unit test interface again, the test of the test project reached last time can be resumed, avoiding the test process from the beginning, saving test time, so as to improve test efficiency, reduce time waste caused by rework, improve personnel experience, and at the same time ensure the requirements and quality of factory delivery time.

[0052] Figure 3A flow chart showing a method for testing a wind turbine generator system according to a first exemplary embodiment of the present disclosure is shown.

[0053] Reference Figure 3 In step S101, the host computer 100 sends a continuous test control signal to the test controller 200 in response to an operation performed by a user on the unit test interface to trigger a continuous test.

[0054] As an example, the operation for triggering continued testing may include, but is not limited to, an operation on a continued testing control on the unit test interface, such as a single-click or double-click operation on the continued testing control.

[0055] In step S102, when the status word of the state machine received by the upper computer 100 in response to the continuation control signal feedback from the test controller 200 is inconsistent with the status word of the state machine received from the test controller 200 last time, the upper computer 100 activates the timer and sends the project identifier of the test item most recently received from the test controller 200 to the test controller 200, so that the test controller 200 executes the test item.

[0056] As an example, the timer may be a pulse counter. As an example, after the timer works, the unit test related program (ie, the test program module) in the host computer 100 can be executed.

[0057] In step S103, when the timer is in working state, if the host computer 100 receives test completion indication information indicating that any test item has been completed from the test controller 200, the project identifier of any test item is sent to the test controller 200, so that the test controller 200 executes the next test item of any test item.

[0058] Accordingly, according to the first exemplary embodiment of the present disclosure, the test method for a wind turbine generator set may further include: after the test controller 200 completes the test of any test item, if the project identifier received from the host computer 100 is inconsistent with the project identifier received last time, then the next test item of any test item is executed; after the test controller 200 completes the test of any test item, if the project identifier of the test item is not received from the host computer 100, then the test process is stopped, that is, the test process is interrupted.

[0059] As an example, the test method of the wind turbine generator set according to the first exemplary embodiment of the present disclosure may also include: when the host computer 100 detects that the unit test interface is not operating normally, controlling the timer to stop working. For example, including but not limited to the unit test interface being stuck, the unit test interface being accidentally exited, and the like, the unit test interface may not operate normally. In addition, the host computer 100 crashes or unexpected power failures may also cause the timer to stop working.

[0060] According to an exemplary embodiment of the present disclosure, the host computer 100 receives the project identifier transmitted by the test controller 200, and feeds back the project identifier to the test controller 200 based on the test results. The host computer 100 can control the start of each test item for dual control of the process. When the unit test interface does not operate normally, the timer stops working and the project identifier will not be fed back to the test controller 200, causing the test controller 200 to stop the test process due to failure to receive the test item identifier.

[0061] As an example, the testing method of a wind turbine generator set according to the first exemplary embodiment of the present disclosure may also include: the test controller 200 sends the status word of the state machine, the project identification of the current test project, the test completion indication information and the test result to the host computer 100 in real time; the host computer 100 saves the status word of the state machine, the project identification of the current test project, the test completion indication information and the test result received from the test controller 200 in real time.

[0062] As an example, the types of test results may include, but are not limited to: test passed, test failed, and test disabled.

[0063] As an example, the operation for triggering the continued test includes the operation of the continued test control on the unit test interface. The test method of the wind turbine generator set according to the first exemplary embodiment of the present disclosure may also include: the test controller 200 does not receive the project identification of the test project sent by the host computer 100 within the preset time, and the test mode is the automatic test mode, and sends a continued test permission signal to the host computer 100; the host computer 100, when receiving the continued test permission signal sent by the test controller 200, puts the continued test control in an operable state (that is, an enabled state). That is, under normal circumstances, in the automatic test mode, the continued test control is in an inoperable state, for example, the "breakpoint continued test" button is gray, when the unit test interface is abnormally closed, if the project identification in the test controller 200 does not change for more than 30 seconds, and the test mode is automatic test, and there is no pause flag, then the "continued test" flag is set, and this flag (that is, the continued test permission signal) is reported to the host computer 100. After the host computer 100 detects this flag, it activates the "Breakpoint Resume Test" button, and the tester can click this button to implement the process resuming test. The advantage of this method is that it can avoid the influence of the test process on the "Breakpoint Resume Test" button caused by the personnel accidentally clicking or misoperating it during the normal test.

[0064] In order to realize the continuous test function, the present disclosure designs two types of data interaction between the test controller 200 and the host computer 100: project identification and status word. Figure 4 A schematic diagram of project identification interaction between the host computer 100 and the test controller 200 according to an exemplary embodiment of the present disclosure is shown.

[0065] like Figure 4 As shown, when the project identifier of the current test project on the test controller 200 side is project number n, the test controller 200 transmits this project number to the host computer 100, and transmits the test state to the host computer 100 at the same time. After the host computer 100 receives the test completion signal (that is, the test completion indication information), the project number is transmitted to the test controller 200. After the test controller 200 detects the completion mark and the project number received last time is not equal to the project number newly transmitted back by the host computer 100, the project number is increased by 1, and the detection of the next test project is prepared to be executed. The effect of this part is that if the unit test interface in the host computer 100 is abnormally closed, the timer will stop working, which makes the host computer 100 not return the project number to the test controller 200, and the project number in the test controller 200 is no longer accumulated, thereby automatically stopping the test process. According to an exemplary embodiment of the present disclosure, the stopping and continued testing of any test project can be realized without adversely affecting the test process.

[0066] In contrast, if the test controller is used to automatically implement the process detection (after one item is detected, the test controller automatically jumps to detect the next item), problems are likely to occur. This is because, for example, for the detection of the action of the actuator, or the detection that requires artificial triggering conditions, even if the external detection conditions are not met, the test process in the test controller is still running automatically, which will cause some test items to fail to pass the detection. If the test process is started and stopped by the heartbeat bit, its disadvantages are: if the communication between the test controller and the host computer is unstable, or the host computer program is stuck, it will affect the normal test process (the process will be accidentally suspended); and if the communication heartbeat bit detection time is extended (such as extended to 5 seconds) in order to avoid the unexpected interruption caused by the communication problem, the detection time of most test items is only about 1 second. Within 5 seconds after the unit test interface is accidentally closed, the test controller will still perform 5 / 1=5 test items downward. If these test items require external triggering conditions, the test will fail, and when the host computer is started again, multiple test items will be skipped, which ultimately leads to the failure of the report to be generated normally, and the skipped test items still need to be repeated.

[0067] Figure 5 A flow chart showing a method for testing a wind turbine generator system according to a second exemplary embodiment of the present disclosure is shown.

[0068] Reference Figure 5 In step S201, the host computer 100 sends a continuous test control signal to the test controller 200 in response to an operation performed by the user on the unit test interface to trigger the continued test.

[0069] In step S202 , the test controller 200 changes the state word of the state machine to a first preset value in response to the continuous test control signal received from the host computer 100 , and sends the changed state word to the host computer 100 .

[0070] In step S203, when the status word of the state machine received by the upper computer 100 in response to the continued test control signal feedback from the test controller 200 is inconsistent with the status word of the state machine received from the test controller 200 last time, the upper computer 100 activates the timer and sends the project identifier of the test item most recently received from the test controller 200 to the test controller 200.

[0071] In step S204 , the test controller 200 receives the project identifier of the test project sent by the host computer 100 .

[0072] In step S205 , if the project identifier received this time is consistent with the project identifier received last time, the test controller 200 executes the test item corresponding to the project identifier received this time.

[0073] As an example, the test method of the wind turbine generator set according to the second exemplary embodiment of the present disclosure may also include: before step S201, the host computer 100 responds to the operation performed by the user on the unit test interface for submitting the test configuration information, activates the timer, and sends the test configuration information to the test controller 200. When the host computer 100 starts the unit test interface for the first time, the pulse timer is in an inoperative state by default. After the user clicks the "Configuration Submission" button, the pulse timer starts working, and when the unit test interface is closed (or accidentally exited) and restarted, the pulse timer will also be in a default inoperative state. At this time, if the configuration is resubmitted, the process test will restart, the test results of the previous process will be cleared, and retesting will result in duplication of work and waste of time. The present disclosure detects the state machine status word of the test controller 200 in the host computer 100, and when it is detected that the state machine status word has changed, the pulse timer is reactivated separately.

[0074] As an example, the test configuration information may include, but is not limited to: crew number, tester identification, crew configuration information. The crew configuration information may include, for example, whether there is a laser radar, whether there is an ultrasonic sensor, etc.

[0075] As an example, the testing method of a wind turbine generator set according to the second exemplary embodiment of the present disclosure may also include: the upper computer 100 stores the test configuration information in a txt notepad in response to an operation performed by a user on the unit test interface to submit the test configuration information, and automatically reads the test configuration information pre-stored in txt once each time the upper computer 100 restarts the unit test interface, thereby ensuring the correctness of the test configuration information and the correctness of the continued test function.

[0076] Figure 6 The state transition diagram of the state machine of the test controller 200 according to the exemplary embodiment of the present disclosure is shown. The states of the state machine include: initialization state, test preparation state, test suspension state, automatic test state, each state has its own state word, and the first preset value is different from the state word of each state.

[0077] Reference Figure 6 After the test controller 200 is started, the state machine is in the initialization state. When the test controller 200 receives the test configuration information sent by the host computer 100, it saves the test configuration information and makes the state machine jump from the initialization state to the ready-to-test state; the test controller 200 responds to the start test instruction sent by the host computer 100, and makes the state machine jump from the ready-to-test state to the automatic test state.

[0078] As an example, the test controller 200 transmits the state machine status word to the host computer 100, and the host computer 100 receives this status word and judges the new and old status words. When it is detected that the current value of the state machine status word is not equal to the value received last time, the timer is restarted. For example, a "breakpoint continuation test" button is set in the host computer 100. After pressing this button, the host computer 100 writes the continuation test control bit (i.e., the continuation test control signal) to the test controller 200 under the condition of communication connection. After the test controller 200 receives this command bit, it sets the state machine status word to other values ​​and transmits it to the host computer 100. When the status word received by the host computer 100 is inconsistent with the default read status word, the timer is activated to make the unit test related program run, thereby realizing the continuation test function of the platform.

[0079] The advantage of this embodiment is that the function of continuing the test can be realized without affecting the normal test process or the previous test items. In contrast, if the logic is set to save the tested process and click "Configure Submit" and "Start Test" again to realize the continued test, the entire processing process will be very complicated and cause unknown problems. For example, after the process test is completed or the connection is interrupted, a certain flag is automatically set. When "Start Test" is clicked again, the tested process does not perform the test, which leads to the problem that it will not start normally when the test really needs to be restarted. At the same time, in order not to retain the last test result, an automatic reset function needs to be set, which is used to clear the last test result. The modification of these two situations requires setting a large number of detection flags, which affects the program structure. In addition, the program logic is too complicated, and it may even affect the normal process downward, and even require the reconstruction of the detection function, which is more disadvantageous than beneficial for the time requirement of factory inspection. Because factory inspection may sometimes require the test to be completed on the same day, the warehouse to be put into storage or even shipped on the same day, if the program reconstruction time is long, or there are functional problems, the program function inspection and repair will seriously affect the production progress. The exemplary embodiments of the present disclosure achieve complete decoupling of normal testing and continued testing functions without affecting each other, and can also indirectly improve the efficiency of production testing.

[0080] Figure 7 A flow chart showing a method for testing a wind turbine generator system according to a third exemplary embodiment of the present disclosure is shown.

[0081] Reference Figure 7 In step S301, the host computer 100 writes the test results of the test items received from the test controller 200 in real time into the array.

[0082] In step S302 , after writing the test result of the test item into the array for the first time, the host computer 100 sets the value of the write flag to a second preset value, and sends the value of the write flag to the test controller 200 .

[0083] As an example, when the test item passes the test, and is not triggered manually and there is no test completion flag, the test results uploaded by the test controller 200 are written into the sequence corresponding to the array, the write flag is set (that is, the write flag is set to the power-off retention type), and the value of the write flag is sent to the test controller 200.

[0084] In step S303 , after the test results of all the test items are written into the array, the host computer 100 resets the write flag and sends the value of the write flag to the test controller 200 .

[0085] That is, after all process tests are completed, the write flag is reset to test the power-on detection of the controller 200 .

[0086] In step S304 , after establishing a communication connection with the test controller 200 , the host computer 100 sends the test configuration information to the test controller 200 if the value of the write flag is the second preset value.

[0087] In step S305, after the test controller 200 completes the power-on startup, if it is detected that the value of the write flag is the second preset value, the test item being executed when the test controller 200 is powered off is executed based on the received test configuration information. Thus, after the test controller 200 is powered on again after being powered off and the communication connection with the host computer 100 is reestablished, the test continuation function can be automatically implemented.

[0088] The present disclosure takes into account that since the process test results are mainly stored in the test controller 200, when the test controller 200 is accidentally powered off, all test results will be cleared. However, the temporary variables inside the functional blocks in the test controller 200 cannot realize the function of power-off retention, so the power-off retention function cannot be relied on alone to achieve continued testing. According to an exemplary embodiment of the present disclosure, the variables that need to be maintained after power failure in the test controller 200 are only the write flag and the project identification before power failure. The purpose of setting the write flag is to distinguish it from the normal power-on and detection process. When the test controller 200 is powered on, if it is detected that the write flag is 1, the project identification when the test controller 200 is powered off is written into the detection function block, the state arrangement of the previous test process is completed in the upper computer 100, and the test configuration information is written to the test controller 200 again, and the test controller 200 starts the continued test function according to the project identification when the power is off.

[0089] Figure 8 A flow chart showing a method for testing a wind turbine generator system according to a fourth exemplary embodiment of the present disclosure is shown.

[0090] Reference Figure 8 In step S401, the configuration submission detection process is started.

[0091] In step S402, the host computer 100 writes the configuration information into the PLC (ie, the test controller 200), saves it locally, and automatically reads it each time it is run.

[0092] In step S403, the PLC transmits the current project number and test status to the host computer 100, and transmits the state machine status word at the same time.

[0093] In step S404, the current item test is completed and the item number is returned.

[0094] In step S405, the item number is incremented by 1, and preparation is made for testing the next test item.

[0095] In step S406, the item number remains unchanged for 30 seconds.

[0096] In step S407, the "continue measurement" flag is set and the "breakpoint resume measurement" button is activated.

[0097] In step S408, the status word changes.

[0098] In step S409 , the changed status word is transmitted to the host computer 100 .

[0099] In step S410, the host computer 100 detects that the status words are inconsistent.

[0100] In step S411, the pulse timer is activated and continues to feed back the project number to the PLC.

[0101] In step S412, the breakpoint resume function is implemented.

[0102] According to the exemplary embodiments of the present disclosure, the process continuation test function after the unit test interface is abnormally closed can be realized, so that the test process can be intelligent and automated, saving the test time, labor and other costs, and improving the potential benefits of the production enterprise.

[0103] Fig. 9 A flow chart showing a method for testing a wind turbine generator system according to a fifth exemplary embodiment of the present disclosure is shown.

[0104] Reference Fig. 9 In step S501, it is determined whether the automatic test is started and the communication is not interrupted.

[0105] In step S502, after each test item is detected, the status is written into the array element, and the write flag is sent to the PLC (ie, the test controller 200).

[0106] In step S503, it is determined whether the PLC is powered on and started up.

[0107] In step S504, it is determined that the write flag is 1.

[0108] In step S505, the project number when the PLC is powered off is written into the detection function block.

[0109] In step S506, it is detected whether the communication is re-established.

[0110] In step S507 , the host computer 100 completes the state arrangement of the previous test process.

[0111] In step S508, the configuration information is written to the PLC again.

[0112] In step S509, the PLC starts the continued measurement function according to the project number at the time of power failure. As an example, the continued measurement function can be started using Figure 8 The method shown.

[0113] According to an exemplary embodiment of the present disclosure, a continuous measurement function in the case of a PLC power outage is implemented.

[0114] Fig.10 The flowchart of the method for executing a test item by the test controller 200 according to the exemplary embodiment of the present disclosure is shown. Any test item can be executed according to the method.

[0115] Reference Fig.10 , in step S601, the test controller 200 determines whether it is necessary to display a prompt dialog box to the user for the current test item.

[0116] This prompt dialog box is used to prompt the user to perform operations related to the current test item. For example, for the test item "Generator cooling fan 1 low speed", the corresponding dialog box may be a prompt box of "Has the generator cooling fan been started?" or "Please start the generator cooling fan".

[0117] In step S602 , when determining that the prompt dialog box needs to be displayed, the test controller 200 requests the host computer 100 to display the prompt dialog box.

[0118] In step S603 , the test controller 200 determines whether the current test item has an associated test item.

[0119] In step S604, when the test controller 200 determines that the current test item has an associated test item, it determines whether the test results of the test items associated with the current test item are all passed. As an example, it can be confirmed based on the local test result or request the host computer 100 to confirm.

[0120] In step S605, when the test controller 200 determines that the prompt dialog box needs to be displayed and there are associated test items, if the host computer 100 receives the user's confirmation operation on the prompt dialog box and the test results of the test items associated with the current test item are all passed, the current test item is started to be executed.

[0121] In step S606, when the test controller 200 determines that the prompt dialog box does not need to be displayed and there are associated test items, if the test results of the test items associated with the current test item are all passed, the current test item is started to be executed.

[0122] In step S607, when the test controller 200 determines that the prompt dialog box needs to be displayed and there is no associated test item, if the host computer 100 receives a confirmation operation of the user on the prompt dialog box, it starts to execute the current test item;

[0123] In step S608 , if it is determined that the prompt dialog box does not need to be displayed and there is no associated test item, the test controller 200 starts executing the current test item.

[0124] As an example, the test items associated with the no-load operation test item may include, but are not limited to: a first blade automatic pitch change emergency stop test item, a second blade automatic pitch change emergency stop test item, and a third blade automatic pitch change emergency stop test item.

[0125] As an example, the test items associated with the safety chain pitch emergency stop test item may include, but are not limited to: a maintenance handle forward pitch test item and a maintenance handle backward pitch test item.

[0126] Fig.11 A test flow association example according to an exemplary embodiment of the present disclosure is shown.

[0127] Since there are many types of wind turbine signal, and in the process of wind turbine operation, each signal is interrelated and affects each other, in order to consider the safety of the test and ensure the test quality, the items pointed by the arrow can only be tested after the previous test items are passed. For example, item 20 must be tested before item 36 can be tested; item 20, item 36, item 41, item 59, item 62, and item 78 must all be tested before item 85 can be tested.

[0128] The present disclosure takes into account that in addition to testing each test item in order from top to bottom, there is also a certain logical relationship between each other. Therefore, during the test process, it is not possible to make a simple judgment based on whether the signal of a certain item is normal (for example, in the related art, a person manually triggers the proximity switch, or manually changes the pitch for a short time, and it is judged to be normal, which is one-sided: if only the proximity switch is manually triggered, but during the actual pitch change, the angle of the proximity switch is incorrect, or the installation distance of the block that automatically triggers the proximity switch is incorrect, it will cause the unit to trigger a fault shutdown during on-site debugging and operation). Therefore, the test process of this test platform needs to be tested step by step, and the test process and test items are indispensable.

[0129] The present disclosure takes into account the following problems existing in the related art: since the host computer arranges the test or the unit test interface to run in the host computer, when the host computer is abnormal or freezes, or other problems occur, causing the unit test interface to be accidentally closed, after the unit test interface is opened again, the test can only be restarted from the beginning, resulting in duplication and rework of the test work. However, in the related art, the continuous test function cannot generally be realized, because the usual HMI interface only has data and results display and simple control functions (start, stop, reset, etc.), and there is no interaction in process control. For simple and unchanged signals, this method can be automatically implemented by the test controller side according to the process detection (after detecting one item, the test controller automatically jumps to detect the next item). However, for the detection of the action of the actuator, or the detection that requires artificial triggering conditions, problems will arise. If the external detection conditions are not met, but the process in the test controller is still running automatically, it will cause the test item detection to fail. Therefore, for more complex detection items, logical or time control is required in the host computer.

[0130] In the relevant debugging-free platform, since the host computer program is running, the relevant controls need to be initialized and set. For example, the detection timer needs to be filled in and submitted after the unit configuration information is submitted before the detection can be realized, otherwise the test item will fail. For example, the actual equipment of the unit has a mechanical wind sensor and an ultrasonic wind sensor, and the configuration information submitted to the test controller only has a mechanical wind sensor, then the ultrasonic wind sensor will inevitably fail the detection. Therefore, when the unit test interface is accidentally closed and reopened, the relevant controls in the host computer program are in the initialized state, and the process cannot continue. If the configuration is submitted again, the test function can only be started from the beginning, resulting in unnecessary rework.

[0131] On the other hand, the method in which the test controller detects the connection with the host computer and the process automatically stops when the connection is disconnected, although the test controller side can work normally after reconnection, the program on the host computer side still cannot be activated and the continued test function cannot be realized.

[0132] In addition, based on the above description, if the logic is set to save the tested process, and re-click "Configure Submit" and "Start Test" to resume testing, the entire processing process will be very complicated and cause unknown problems. For example, after the process test is completed, or the connection is interrupted, a certain flag is automatically set. When you click "Start Test" again, the tested process will not be detected. The resulting problem is: when it is really necessary to restart the test, it will not start normally. At the same time, in order not to retain the last test results, the test function block is set with an automatic reset function, which is used to clear the last test results. Modifications in both cases require setting a large number of test flags, which affects the program structure.

[0133] In addition, in the related art, since the process test results are mainly stored in the test controller, all test results will be cleared when the test controller is accidentally powered off. However, the temporary variables inside the test function block cannot realize the power-off retention function, so the power-off retention function cannot be relied on alone to achieve continuous testing.

[0134] Based on the above reasons, the present disclosure proposes a breakpoint continuation test method for a debugging-free platform, optimizes the fault-tolerant function for the problems actually encountered by the debugging-free platform, realizes the continuity of the test work, and reduces the workload of the testers. Therefore, during the test process of the factory inspection of the wind turbine generator set, if the host computer test interface is abnormally closed or the test controller is unexpectedly restarted, the unfinished part can be tested from the completed test items, and there is no need to start the test from the beginning, thereby improving the test efficiency, avoiding repeated tests, and reducing the test workload. The automation of the detection of the main actuators of the wind turbine generator set is realized, the standardization of detection and compliance and judgment basis is ensured, the workload of personnel is reduced, and the factory quality is further guaranteed.

[0135] The advantages of the exemplary embodiments disclosed herein are that the continued testing function can be realized by only detecting information interaction, without the need for separate state storage or execution restrictions for each functional block, which can simplify the amount of program modification while ensuring the execution of normal test functions (such as automatically testing unqualified items, or situations where retesting is indeed necessary after manual confirmation).

[0136] One of the advantages of the present disclosure is that it can realize stopping and resuming testing of any test item without adversely affecting the test process. The second advantage of the present disclosure is that the resuming test function can be realized without affecting the normal test process and the previous test items. The third advantage of the present disclosure is that it realizes the complete decoupling of normal test and resuming test functions, and the two do not affect each other, which can indirectly improve the efficiency of production testing. The fourth advantage of the present disclosure is that the resuming test implementation method in the event of an unexpected power failure of the PLC can make up for the problem that the temporary variables inside the function block cannot be maintained during power failure. The variables that need to be maintained during power failure in the PLC only need two variables: "write flag" and "project number before power failure". There is no need for complex power failure maintenance, which can save PLC resources and simplify program logic.

[0137] An exemplary embodiment of the present disclosure provides a computer-readable storage medium storing a computer program, which, when executed by a processor, causes the processor to execute the test method of the wind turbine generator set as described in the above exemplary embodiment. The computer-readable storage medium is any data storage device that can store data read by a computer system. Examples of computer-readable storage media include: read-only memory, random access memory, read-only optical disk, magnetic tape, floppy disk, optical data storage device, and carrier wave (such as data transmission through the Internet via a wired or wireless transmission path).

[0138] Although some exemplary embodiments of the present disclosure have been shown and described, it will be appreciated by those skilled in the art that modifications may be made to these embodiments without departing from the scope and spirit of the present disclosure as defined by the claims and their equivalents.

Claims

1. A method for testing a wind turbine generator set, characterized in that: The test method includes: The host computer sends a continuous test control signal to the test controller in response to the operation for triggering the continued test performed on the unit test interface; When the state word of the state machine fed back by the test controller in response to the continuous test control signal received by the host computer is inconsistent with the state word of the state machine received from the test controller last time, the host computer activates the timer and sends the project identifier of the test project most recently received from the test controller to the test controller, so that the test controller executes the test project; When the timer is in the working state, if the host computer receives test completion indication information indicating that any test item has been completed from the test controller, the host computer sends the item identification of any test item to the test controller, so that the test controller executes the next test item of any test item; Wherein, the host computer is communicatively connected with the test controller.

2. The testing method according to claim 1, characterized in that: The test method also includes: The test controller changes the state word of the state machine to a first preset value in response to the continued test control signal received from the host computer, and sends the changed state word to the host computer; The test controller receives the project identification of the test project sent by the host computer; The test controller executes the test item when the item identifier received this time is consistent with the item identifier received last time.

3. The testing method according to claim 1, characterized in that: The test method also includes: After completing the test of any test item, the test controller executes the next test item of any test item if the project identifier received from the host computer is inconsistent with the project identifier received last time; After completing the test of any test item, if the test controller does not receive the project identifier of the test item from the host computer, the test controller stops the test process.

4. The testing method according to claim 1, characterized in that: The test method also includes: The host computer activates the timer in response to an operation for submitting test configuration information performed on the unit test interface, and sends the test configuration information to the test controller; When the host computer detects that the unit test interface is not operating normally, the host computer controls the timer to stop working.

5. The testing method according to claim 4, characterized in that: The test method also includes: The host computer writes the test results of the test items received from the test controller in real time into an array; After the host computer writes the test result into the array for the first time, the host computer sets the value of the write flag bit to a second preset value, and sends the value of the write flag bit to the test controller; After the test results of all the test items are written into the array, the host computer resets the write flag and sends the value of the write flag to the test controller; After the host computer establishes a communication connection with the test controller, if it is detected that the value of the write flag is the second preset value, the host computer sends the test configuration information to the test controller; After the test controller is powered on and started, if it is detected that the value of the write flag is the second preset value, the test item being executed when the test controller is powered off is executed based on the test configuration information.

6. The testing method according to claim 1, characterized in that: The test method also includes: The test controller sends the state word of the state machine, the project identification of the current test project, the test completion indication information and the test result to the host computer in real time.

7. The testing method according to claim 1, characterized in that: The operation for triggering the continued test includes operating the continued test control on the unit test interface; wherein the test method further includes: When the test controller does not receive the project identifier of the test project sent by the host computer within a preset time period and the test mode is an automatic test mode, the test controller sends a continuous test permission signal to the host computer; When the host computer receives the continued test permission signal sent by the test controller, the continued test control is put into an operable state.

8. The testing method according to claim 1, characterized in that: The test controller is communicatively connected with a unit controller of the wind turbine generator set being tested; The unit controller is used to receive unit signals and control the actions of actuators of multiple components of the unit, wherein the multiple components include an impeller, a nacelle, and a transmission chain, and the unit signals include sensor signals and switch signals; Among them, multiple test items in the test process are used to test whether a fault is triggered in the unit controller, whether the actuator acts according to the control signal, and whether the unit signal is normal.

9. The testing method according to claim 3, characterized in that: The step of the test controller executing the next test item of any test item comprises: The test controller determines whether a prompt dialog box needs to be displayed to the user for the next test item of any test item, and whether the next test item has an associated test item; When the test controller determines that the prompt dialog box needs to be displayed, the test controller requests the host computer to display the prompt dialog box; The test controller determines, when determining that the next test item has an associated test item, whether the test results of the test items associated with the next test item are all passed; When the test controller determines that the prompt dialog box needs to be displayed and has an associated test item, if the host computer receives a confirmation operation on the prompt dialog box and the test results of the test items associated with the next test item are all passed, the next test item is started to be executed; The test controller, when determining that the prompt dialog box does not need to be displayed and there are associated test items, starts executing the next test item if the test results of the test items associated with the next test item are all passed; When the test controller determines that the prompt dialog box needs to be displayed and there is no associated test item, if the host computer receives a confirmation operation on the prompt dialog box, the test controller starts to execute the next test item; The test controller starts executing the next test item when determining that the prompt dialog box does not need to be displayed and has no associated test item.

10. The testing method according to claim 9, characterized in that: The test items associated with the no-load operation test items include: the first blade automatic pitch change emergency stop test item, the second blade automatic pitch change emergency stop test item, and the third blade automatic pitch change emergency stop test item; The test items associated with the safety chain pitch emergency stop test item include: the maintenance handle forward pitch test item and the maintenance handle backward pitch test item.

11. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the processor is prompted to execute the wind turbine generator system testing method according to any one of claims 1 to 10.

Images